View Full Version : HD-DVD Control Data Zone raw reading
Geremia
27th April 2007, 13:25
Just if anyone is interested in looking at the control data zone of an HD-DVD (for study purpose), here is a crappy bat script (thanks awhitehead for the bat creator) that dumps it all.
You need an xbox360 SD-S802A
The script takes about 10minutes, and it will output all the complete control data zone (psn 1e400-1fbff)
and also single sections (refer to aacs spec for detail)
every sector is 2064 bytes lenght (16bytes of header + 2048 of data, refer to mmc6 spec for detail)
http://www.sendspace.com/file/htgrod
I first thought that VolumeID and KCD was hided into the RSV field of the header of sectors in CopyrightDataSegment, but at least for kingkong are empty.
Can anyone take a look at CopyrDS of a movie that has a complete VolumeID without the ending 002020202020 ?
for example
0401E600FB18000000000000BFAD7D99
this is from kingkong, RSV 6byte field is empty in 01E400 sector and ahead.
arnezami
27th April 2007, 13:49
Just wanted to confirm that it works. :) The complete CDZ is around 12 MB for me.
Of course I only have King Kong so I can't help you much further there.
[edit] For clarity: you need to run readCDZ.bat from the command promt using your drive letter. After 10 minutes there will be 6 files added. Open rawCopyrDS.bin with a hex editor and see what the first 16 bytes look like.
Btw: I can confirm the HRL record is in the CPSUS.bin file. In fact its in there 8 times.
arnezami
PepsiLee2001
27th April 2007, 16:38
I try to dump CDZ with SD-S802A and Last Samurai.
first sector of rawCopyrDS.bin are "0401E600FB18000000000000BFAD7D99" and 00 (00000010 h ~ 0000080f h).
arnezami
27th April 2007, 16:41
I try to dump CDZ with SD-S802A and Last Samurai.
first sector of rawCopyrDS.bin are "0401E600FB18000000000000BFAD7D99" and 00 (00000010 h ~ 0000080f h).
What is the Volume ID of that movie/disc?
PepsiLee2001
27th April 2007, 16:44
What is the Volume ID of that movie/disc?
Volume ID of Last Samurai is "400025061303183157474844564D0000".
I can't find it in rawCopyrDS.bin.
Fahzuu
27th April 2007, 17:28
Volume ID of Last Samurai is "400025061303183157474844564D0000".
I can't find it in rawCopyrDS.bin.
Maybe you should search for the part that really is the ID.
That would be 25061303183157474844564D.
The rest is just the "frame".
Geremia
27th April 2007, 18:31
the volumeID part that should be in the CopyrDS in your case is "57474844564D".
Can you search for it (and smaller part of it) into the:
-rawCopyrDS.bin
-rawCopyrDS_2.bin
-rawCDZ_complete.bin, just to be sure
thanks
awhitehead
28th April 2007, 00:51
Open rawCopyrDS.bin with a hex editor and see what the first 16 bytes look like.
Syriana, US, Warner Brothers.
Volume ID: 400029063205152657474844564D0000
First 16 bytes of rawCopyrDS.bin (block 1e600) are
0401E600FB18000000000000BFAD7D99
PepsiLee2001
28th April 2007, 02:03
the volumeID part that should be in the CopyrDS in your case is "57474844564D".
Can you search for it (and smaller part of it) into the:
-rawCopyrDS.bin
-rawCopyrDS_2.bin
-rawCDZ_complete.bin, just to be sure
thanks
Is it strange?
"57474844564D" does not exist in rawCopyrDS.bin, rawCopyrDS_2.bin and rawCDZ_complete.bin.
arnezami
28th April 2007, 07:03
Is it strange?
"57474844564D" does not exist in rawCopyrDS.bin, rawCopyrDS_2.bin and rawCDZ_complete.bin.
Not really. Finding this value in the bin is a long shot. But it had to be tried. Don't forget: the Volume ID (and KCD) is stored in a "confidential way" ;).
Anyway. What has to be done is to do this for two different movies (thus creating 6 files for each of them) and compare the files. (eg winhex can compare files).
If something is different then it is likely/possible it has to do something with the volume ID. :)
For some reason I have a feeling things are going to be exactly the same...
arnezami
PS. ah. wait. I see I have something in my pm regarding this... ok. there are definatly differences (a total of roughly 33000 bytes between two complete dumps). But no differences in rawCopyrDS.bin it seems (i'm not sure about their VIDs so).
Geremia
28th April 2007, 07:30
it's weird that 2 CopyrDS of different movie hare identical, ......and identical also in the EDC fields, so seems the sections are really equeal so really empty (no drive manipulation).
goin to work, thinking on the way :)
arnezami
28th April 2007, 07:37
it's weird that 2 CopyrDS of different movie hare identical, ......and identical also in the EDC fields, so seems the sections are really equeal so really empty (no drive manipulation).
goin to work, thinking on the way :)
Yeah. I guess the Volume ID is not (encoded) in the CopyrDS section. Meaning the other parts are now prime candidates.
I believe the CPSUS files had (only) about 350 differences...
SvT
28th April 2007, 17:32
Hello there, I just bought all equipment to play around and I'm trying some stuff over here. :helpful:
Don't know if this helps...
Bourne Supremacy (EU)
Volume ID: 40001027200607200020202020200000
First 16 bytes of rawCopyrDS.bin are 0401E600FB18000000000000BFAD7D99 (same again)
I think the Volume Unique Key for this disk isn't on the list yet so I'm gonna play around some more !
Let me know if there is anything else that needs to be tested !
Geremia
29th April 2007, 15:01
I was looking at some notes i've wrted before
this drive takes some debug log of some actions, i've not already tryied to spot out the serial port (maybe not used at all), anyway you can see part of this log in ram at address 0x670000
The volumeID is already in ram as soon the inserted disc is ready, and taking a look at this log i'm wondering what is the MMV that is readed after the CDZ and prior the P-MKB and BCA (btw, BCA is read at layer1?!?)
[30mT:0003CE5F Start SYS_IGN: HD-CDZ Read
T:0003CE5F Start PBA Read: PBA: 1E400h Layer: 0h OK
Mediatype: HD-ROM/OTP
T:0003CE70 [34m -Result: Good
[30mT:0003CE70 Start SYS_IGN: HD MMV Read
T:0003CE97 [34m -Result: Good
[30mT:0003CE97 Start SYS_IGN: HD MKB Read
T:0003CE97 Start PBA Read: PBA: 1E800h Layer: 0h OK
T:0003CEA1 [34m -Result: Good
[30mT:0003CEA1 Start SYS_IGN: Layer1 Adjust
[36mT:0003CEA1 Adjust Table: P_full_adjust_sequence_HD_Layer1
[30mT:0003CEA1 ADJ: jump_layer1
.....
.....
[30mT:0003CEF7 Start SYS_IGN: BCA Read
.....
then leaves system-leadin area and jumps to data area (presumibly based on the info it has read from phisicalformatinformation sector)
[30m Mediatype: HD-ROM/OTP
T:0003CF09 Start SYS_IGN: HD Servo Adjust for Data Area
[32mT:0003CF09 HD_PROFILE_4
[30m[36mT:0003CF09 Adjust Table: P_itbl_ign_focus_on
I'll try to go tracing back form the degub text messages to see what MMV is
awhitehead
29th April 2007, 23:03
this drive takes some debug log of some actions, i've not already tryied to spot out the serial port (maybe not used at all), anyway you can see part of this log in ram at address 0x670000
What CDB you using to read the RAM?
plscsi -v -p -x "DF 00 E2 00 00 67:00:00 67:07:ff" -i x800 -t log.bin
?
(Sorry, I am about 2 hour drive away from my drive right now,otherwise I'd just test)
Geremia
30th April 2007, 01:46
i use dump.exe by xt5
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.