Commodore4eva's Xbox1 DVDROM hack discussion

[gerzand]

I followed Bluecops method using the Xbox 605B with the 605b0800 Firmware to rip Halo2 and to obtain the SS.bin. However,with both my PC and 605B drives, I still get "missing data" error in cloneCD which I then select the "replace with dummy data" option. Is this normal for the both PC drives and the 605b to throw this error? Also, when the cloneCD raw dump finishes, it tells me there was an error, and asks if I would i like to keep the files. I havent seen this error mentioned in Bluecop's or Arakon's tutorials. Is this also normal? Thanks to anyone who can help.

-Gerzand-

yes this is normal. there is unreadable sectors on the disc that you need to  select "replace with dummy data"

How about my second question about the error when creating the raw dump image? Anyone? Thanks

[Arakon]

that error simply says that there were bad sectors and normally that would mean the disk is defective, so you are asked if you want to delete the image. but since the bad sectors are there on purpose, you have to keep the image of course.

[john]

I followed Specialist instructions again and now the disc laods except dirty disc error immediately.  What gives.  What would cause a dirty disc error.  I verified that the game partition started in the correct position.  I'm baffled.  Qwix wouldn't do anything to the files, would it.  For more info on my situatio, refer to the pst by me at the end of 2 pages ago and Specialists post top of the previous page.  Thanks.

[blakcat]

i mean PSN 30000 to PSN 60600. the padded area of the iso. could you not put the SS in here. it would eliminate the PSN calculations because it will always be a certain offset from the begining and it would enable single layer media i think.

Can't think of a reason why this wouldn't work ... Are you sure you patched the adress correctly in the FW ? in other words: changed F9 into 60 and FA to 00 ? And did you make sure that you OVERWROTE bytes (the SS) and not 'inserted' bytes ? Does the unlocker work ?

i think the problem here is  that if you change F9 into 60 and FA to 00 samsung will read PSN 600000 , to read PSN 60000 you must change F9 into 06 and FA to 00 
 

[blakcat]

The  dvd structure data is empty, but it DID read SOMETHING, because it returned $664 bytes. This mean that the FW read an empty sector. This could indicate that you might have patched the wrong bytes in the FW. What bytes did you patch and what did you set them to ?

I patched FDB5: F9FA00 -> 060000

sorry, here is correct

[blakcat]

i have been looking at the xbox 1 samsung firmware and i think i might know how it sets the layer to read from.

i think the value of external memory location 803D determines which layer it reads from. if we set this to 0 then it will read from layer0 or 1 to read from layer 1.

I am not sure if this is correct but if someone wants to try it. you would need to insert code in fdaf to write 0 to 803d and patch the PSN at offset fdb4 from 00f9fa00 to a PSN in layer 0.

I would try this myself but i fried my samsung drive when a power sparked when i was pluging it into a live power supply by accident.  I was just looking at his patches in hopes it would help me understand my TS-H943A.

write 0 to external memory 803d

Code:

mov dptr,#X803d
clr a
movx @dptr,a

write 1 to external memory 803d

Code:

mov dptr,#X803d
mov a,#1
movx @dptr,a

If this is wrong please enlighten me on how the layer to read from is set.

If someone wants to hook me up with any broken or working 605b then pm me. i would like to try to bring mine back to life. maybe i will just a get a new one but most places way over charge for them.

i have tested and fail boot. it shows the video as when you use a nonpatched firm.
writed my tested ss to psn60000 (18000000h) and 1 sector before and after this one. And at PSN301B5 at the end of my video partition.
modifyied firm to read PSN60000 or PSN301B5 and inserted this bluecop code to set the layer to read from

There must be something more in this hack. Checksum?

[john]

Does anybosy have an idea why im getting a dirty disc error

[BlueCop]

john: it is not neccessary to repost the same question 3 posts below your orginal question. Its pretty rude to the forum and it motivates me not to help you. Anyway I would say it is your media. the first DL discs i used didn't read well in my drive and i had to get another brand before it worked.


blakcat: thanks for testing that. would you mind seting it to 1 and 0 with the orginal PSN then testing. I am just curious how it would react. Thanks

[gerzand]

Bluecop, im on disc attempt #6 and just wanted to try and clarify some things. Your help would be much appreciated


From your tutorial post, is the layerbreak of the IMAGE.dvd file you in your isobuilder.rar supposed to work for all concatenated images?, Or should I be making my own in cloneCD from my original Splinter cell disc that im attempting to copy? And if so, what FW should be used when dumping the .dvd file because the 605B0800.bin freezes for me when trying to unlock the drive in order to be able to "see" the whole disc

[stonersmurf]

Bluecop, im on disc attempt #6 and just wanted to try and clarify some things. Your help would be much appreciated


From your tutorial post, is the layerbreak of the IMAGE.dvd file you in your isobuilder.rar supposed to work for all concatenated images?, Or should I be making my own in cloneCD from my original Splinter cell disc that im attempting to copy? And if so, what FW should be used when dumping the .dvd file because the 605B0800.bin freezes for me when trying to unlock the drive in order to be able to "see" the whole disc

If you fallow bluecops method you don't have to worry about the layerbreak just use the same .dvd file everytime. Also use orignal firmware with the unlocker tool. XBINs has the orignal firmware if you need it.

Edit: Make sure your booktype is set to DVD-ROM

[gerzand]

If you fallow bluecops method you don't have to worry about the layerbreak just use the same .dvd file everytime. Also use orignal firmware with the unlocker tool. XBINs has the orignal firmware if you need it.

Edit: Make sure your booktype is set to DVD-ROM

Yeah, thats what I was banking on with the .dvd file. Thats what ive been doing. I even downloaded a booktype tool for my BenQ burner, and it was set to its default as DVD-rom so nothing wrong there. I'm still getting only the dvd video playing instead of booting the game. hmmmm, what could it be?

EDIT: It appears that when creating the final image with ss_patcher instead of the isobuilder batch file, the sizes are different by about 1 megabyte    - but on a brighter side, the layerbreak of the IMAGE.dvd file that ss_patcher spits out matches BlueCop's values. I'm burning this momentarily. I'll be back to report my findings.    -gerzand-

[gerzand]

It works 

But only 3 times out of 10. Anyone else have times when it resufes to load and keeps thinking its a movie until u eject it a few times?

[dom0012]

Bluecop, im on disc attempt #6 and just wanted to try and clarify some things. Your help would be much appreciated


From your tutorial post, is the layerbreak of the IMAGE.dvd file you in your isobuilder.rar supposed to work for all concatenated images?, Or should I be making my own in cloneCD from my original Splinter cell disc that im attempting to copy? And if so, what FW should be used when dumping the .dvd file because the 605B0800.bin freezes for me when trying to unlock the drive in order to be able to "see" the whole disc

you cannot unlock the drive with the 605b0800.bin you need the other hacked firmware (sdg605b.bin) to unlock drive, the 0800 is FOR DUMPING  SS from GAME disc ONLY. The image.dvd file works with any image, and every image you make will come out to 6.54 gigs.
Follow bluecops tutorial and use his package

[dom0012]

I followed Specialist instructions again and now the disc laods except dirty disc error immediately.  What gives.  What would cause a dirty disc error.  I verified that the game partition started in the correct position.  I'm baffled.  Qwix wouldn't do anything to the files, would it.  For more info on my situatio, refer to the pst by me at the end of 2 pages ago and Specialists post top of the previous page.  Thanks.

FOLLOW BLUECOPS TUTORIAL!!! geez why do people make this more complicated then it really is??
 

[BlueCop]

i have tested and fail boot. it shows the video as when you use a nonpatched firm.
writed my tested ss to psn60000 (18000000h) and 1 sector before and after this one. And at PSN301B5 at the end of my video partition.
modifyied firm to read PSN60000 or PSN301B5 and inserted this bluecop code to set the layer to read from

There must be something more in this hack. Checksum?

i think the checksum is just for the debug command for the xbox to compare to a value it has.

i have something else to try if you don't mind. try to clear bit 2ch.5 at fdc4 instead of
Xfdc4:   setb   2ch.5      ; fdc4   d2 65
just patch d2 to c2 and that should do it. try and see if you get results for reading from layer 0

Edit: lets keep it civil.

dom0012: it is funny that you are yelling at people. you were asking questions like a machine gun before. so much so that you were baned.

Edit2: I think we should look at the code at X8ddb. It is reading the Physical format information from PSN 02F200 in the control block. this is most definitely in the first layer so we find out what it is doing then maybe we can replicate it. This is in the lead in but i don't think that should matter

[blakcat]

sorry blue but now i'm away from home.

Monday i come back, then i'll test everything.

i`d like to take a look at some doc explaining in some way how works a original dvd reader firm (asm code) (Any link?)

[TheSpecialist]

FOLLOW BLUECOPS TUTORIAL!!! geez why do people make this more complicated then it really is??
 

Because he wanted to mod some files before burning them to disc.

@ John: How did you verify the correct start of the game partition ? What does the unlocker say ? Did you check the bitsetting ? How big is the size of all the files together (the first ISO you created) and how big is the final ISO you burned ?

[dom0012]

dom0012: it is funny that you are yelling at people. you were asking questions like a machine gun before. so much so that you were baned.

im not yelling at him just trying to get his attention... and the reason i was banned is cuz i flamed psilocybe for making a stupid comment, and he did not like that  .

[probutus]

sorry for interrupting your "discussion" but I have a general question about the dvdrom hack: is there a chance of getting this hack to read and unlock also 360 discs? I know that the disc offsets differ between the xbox1 and the 360 games; is there a chance to modify these offsets?

[BlueCop]

probutus: i was thinking about that myself. i am going to attempt to patch the code that reads the Physical format information from PSN 02F200 to replace the data zone allocation information to hardcoded values large enough to encompass the entire real data zone. this way i think we could just use WXRipper with the disk inserted like it was a hotswaped disc but without hotswaping. WxRipper automaticly detects and skips the bad sectors so this would make ripping really quick. I need to find out where it stores these values below when reading the sector and write the hardcoded values to those memory locations.

quote from http://www.ecma-international.org/publications/files/ECMA-ST/Ecma-267.pdf

Bytes 4 to 15 - Data Zone allocation
Byte 4 shall be set to (00).
Bytes 5 to 7 shall be set to (030000) to specify the Sector Number 196 608 of the first Physical Sector of the
Data Zone
Byte 8 shall be set to (00).
Bytes 9 to 11 shall specify the Sector Number of the last Physical Sector of the Data Zone
Byte 12 shall be set to (00)
Byte 13 to 15 shall be set to (00) on SL disks and DL disks in PTP mode, and to the Sector Number of the last
Physical Sector of Layer 0 on DL disks in OTP mode.

since my xbox drive is dead i was going to work with my TS 360 drive.

the 2 things that need patching are the Sector number of the last physical sector and the last physical sector of layer 0 and i think that should do it.