Cracked Samsung SDG-605B/616T/616F Firmware for Xbox 1 - V2

[dom0012]

as indicated by this:

Clipboard data, and "write".
It will paste the SS over the blank data previously there.

the red x marks the line which you might think to put the SS data but you shouldn't, the first 00 of the next line is probably where it should be placed.
[/quote]

ok so right below the red X, but what about the part where you subtract the full length of image from the offset? does dvdinfopro tell you both of these numbers?

[anarchy99]

you're mixing up 616 and 605 drives, twizter.
there's 605B and 605F, both which are original xbox 1 drives which use different hardware and are not compatible.
616 is the PC drive variations.

would it be easily modified to work with the 605f

[twizter]

it's clearly explained in Arakon's guide
....
Select "Media Info", and select "physical format information" in the Advanced dropdown menu. Click OK and note the last three bytes of the first line (they'll normally be in the range of Fx xx xx).
....
for this i have the MONSTER dvd9, open DvdInfoPro, and the last three bytes for this disc is "FC E7 45"  in Arakon's example his offset was "FC A6 FA".

Now:
"substract the Offset from the full length of the image that you figured out using dvdinfopro"
the offset hes talkin about is the offset thats written into the firmware, its where the fw will look for the SS data.

(i.e. FCA6FA - F9FA00 = 2ACFA)

for my DVD its
(FCE745 - F9FA00 = 2ED45)

Next:
"Now multiply your result by hex 800 (2ACFA x 800). The result (in this case 1567D000)"
mine would be (2ED45 x 800 = 176A2800)

Finally:
"... is how far you have to go from the END of the raw dump to find the location of where to put the security sector."
meaning if you really wanted you could do the math to find the actual location,
or just use WinHex's "Goto", and enter your result, and check the "end (back from)" option.

"It will jump to the position you need to insert the SS to.. however make sure it's at the beginning of the line, it may jump one byte too far up"
The line should start with 00 (blank data)




-

all credit goes to Arakon for making this detailed guide which can be found here: http://arakon.dyndns.org/backup.html

[darkfly]

The concept could be used to write firmware for the 605F, but Arakon mentions it uses a different chipset so no, it wouldn't be just an easy fix.

[dom0012]

it's clearly explained in Arakon's guide
....
Select "Media Info", and select "physical format information" in the Advanced dropdown menu. Click OK and note the last three bytes of the first line (they'll normally be in the range of Fx xx xx).
....
for this i have the MONSTER dvd9, open DvdInfoPro, and the last three bytes for this disc is "FC E7 45"  in Arakon's example his offset was "FC A6 FA".

Now:
"substract the Offset from the full length of the image that you figured out using dvdinfopro"
the offset hes talkin about is the offset thats written into the firmware, its where the fw will look for the SS data.

(i.e. FCA6FA - F9FA00 = 2ACFA)

for my DVD its
(FCE745 - F9FA00 = 2ED45)

Next:
"Now multiply your result by hex 800 (2ACFA x 800). The result (in this case 1567D000)"
mine would be (2ED45 x 800 = 176A2800)

Finally:
"... is how far you have to go from the END of the raw dump to find the location of where to put the security sector."
meaning if you really wanted you could do the math to find the actual location,
or just use WinHex's "Goto", and enter your result, and check the "end (back from)" option.

"It will jump to the position you need to insert the SS to.. however make sure it's at the beginning of the line, it may jump one byte too far up"
The line should start with 00 (blank data)




-

all credit goes to Arakon for making this detailed guide which can be found here: http://arakon.dyndns.org/backup.html

Ok, thanks man for the quick reply.  (i.e. FCA6FA - F9FA00 = 2ACFA)  so  F9FA00 is the part that stays the same then eh?

[twizter]

Security sector now read from  PSN $fd021e (originals) AND  PSN $f9fa00 (backups. This is the next sector after end of xbox game data.)
...
Added security secotr to image with hex editor at psn f9fa00

Ok, thanks man for the quick reply.  (i.e. FCA6FA - F9FA00 = 2ACFA)  so  F9FA00 is the part that stays the same then eh?

Yes, why F9FA00 stays the same is because it is the address which the firmware looks for the SS data at.

[dom0012]

ok i wont have my samsung till tommorow and when i test this i will give my results.. i have like 4 dual layer dvd's to play around with 

[dom0012]

does it matter if its + or - DL dvd? sorry if this question has already been answered...

[BlueCop]

i think it has to be DVD+R DL because it says you have to set the booktype to DVD-ROM. you can only set the booktype with the + media.

[stonersmurf]

does it matter if its + or - DL dvd? sorry if this question has already been answered...

I believe the SDG-605B will only read +, atleast thats the case for me.

[dom0012]

perfect because thats all i have 

[dom0012]

hey will the halo2-pal.bin SS work with halo2 NTSC?
Or do i have to use this method to dump my own:


"In case you need to dump your own SS, you have to flash the 605b0800.bin to your Samsung drive, and while it's hooked up to your PC, run DVDInfoPro again, go to Advanced dropdown menu, and select "Send custom command".
In the CDB fields enter the following sequence: AD 00 FF 02 FD FF FE 00 08 00 00 C0."

sorry for the noob questions.. 

[BlueCop]

dump your own SS. i can't tell you if it will work or not but i know thw ntsc ss is different from the pal(i have compared). so extract your own from the orginal disc.

edit: "I'm the Dude. So that's what you call me. You know, that or, uh, His Dudeness, or uh, Duder, or El Duderino if you're not into the whole brevity thing. "

[dom0012]

ok thanks duder 

[BlueCop]

i have been playing with xbdvdimg.exe from the XDK(don't ask me for it and don't ask where to get it)

It generates the Security Placeholder positions on a game disc. It uses a seed number to generate 16 locations. each location is 8MB in size or 1000h sectors. You can add your game files and select their placement on the disc between placeholders and even select which layer.

It would save so much ripping time if we could detect like 2 bad sectors in a row to skip the whole 8MB block and then continue ripping. I think this would improve ripping speed greatly.

how does the xbox know the security placeholder placement? can we predict this from something on the disc like the SS or something else that identifies the placeholders. does the XDVDFS file table just not point to any sectors of bad data if that is the case. perhaps the file table could be used to rip only the data portition of the disc with the correct placement thus avoiding bad sector areas all together.

I mainly want to be able to build my own images. i think using xbdvdimg.exe with the placeholder positions from my orginal disc i could rebuild an image.

I am still in search of a DVD Drive that will dump the second layer of my xbox dvd i hot swap. i keep having trouble with it crashing after the first layer.

[Interloper]

I opened up my 4 xboxs all of which are Sdg-605. I am assuming thats Sdg-605'A'  ?

[Arakon]

the red X marks where it SHOULD start, cause if you go up backwards, it will put the cursor in the last byte of the line above (which is wrong). the SS has to start at the beginning of the line.

@interloper: there'll be a small "revision:" at the bottom of the sticker, and it'll say A or F.

[Iriez]

On posting links to firmware:

Great work on the firmware guys. I am sure many people will want to take a look. However, due to legal reasons, I cannot allow links to be posted. The forums won't help anyone if they get taken down.

Back in the day, #xbins was a good place for people to find good homebrew software...

Please, no links. Things will end up in the "usual places" soon enough I am sure...

Back in the day? The day is still present my friend. The firmware is readily availble, but was withheld until I saw a few people play with it for a night without burning any drives up ; )

Thanks to com64 for the new idea's, and to TS [and friends] for all the original breakthrough's and hard effort. Im glad to see some 'public' headway being done about the 360, as I cannot wait to get my little bro's some action that wont break my wallet.

[xDREAM]

It would save so much ripping time if we could detect like 2 bad sectors in a row to skip the whole 8MB block and then continue ripping. I think this would improve ripping speed greatly.

What prevents you from doing this without knowing the locations?

[MacDennis]

It would save so much ripping time if we could detect like 2 bad sectors in a row to skip the whole 8MB block and then continue ripping. I think this would improve ripping speed greatly.

Try clonecd for a change. It seems to be much faster than isobuster.

how does the xbox know the security placeholder placement? can we predict this from something on the disc like the SS or something else that identifies the placeholders. does the XDVDFS file table just not point to any sectors of bad data if that is the case. perhaps the file table could be used to rip only the data portition of the disc with the correct placement thus avoiding bad sector areas all together.

No, the xbox and the drive do not need to know about the placeholders. Why? Because the placeholders are placed *in between* files. So, placeholders are never accessed.