Editing Remarry Bluray Drive on Linux
Jump to navigation
Jump to search
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then publish the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 1: | Line 1: | ||
=Introduction= | =Introduction= | ||
=EID2= | =EID2= | ||
* You will need decrypted EID2 data. | * You will need decrypted EID2 data. | ||
* How to get it on Linux is described here: http://www. | * How to get it on Linux is described here: http://www.ps3devwiki.com/wiki/Spuisofs#Dumping_EID2_Key_with_spuisofs | ||
* EID2 contains encrypted P-Block and S-Block. | * EID2 contains encrypted P-Block and S-Block. | ||
* To get decrypted S-Block and P-Block first you have to decrypt EID2 with EID2 key and IV and then decrypt the blocks with DES-CBC. | * To get decrypted S-Block and P-Block first you have to decrypt EID2 with EID2 key and IV and then decrypt the blocks with DES-CBC. | ||
Line 22: | Line 15: | ||
key: 6C CA B3 54 05 FA 56 2C | key: 6C CA B3 54 05 FA 56 2C | ||
</pre> | </pre> | ||
=Writing P-Block= | =Writing P-Block= | ||
Line 89: | Line 22: | ||
* P-Block is in decrypted EID2 at offset 0x20 and of size 0x80. | * P-Block is in decrypted EID2 at offset 0x20 and of size 0x80. | ||
* Not all P-Block data is sent to BD drive. Only data starting at offset 0x10 and of size 0x60 bytes is written to BD drive buffer 2. | * Not all P-Block data is sent to BD drive. Only data starting at offset 0x10 and of size 0x60 bytes is written to BD drive buffer 2. | ||
==Test== | ==Test== | ||
Line 111: | Line 29: | ||
<pre> | <pre> | ||
# First enable writing BD buffer 2 | # First enable writing BD buffer 2 | ||
Line 123: | Line 38: | ||
# Authenticate the BD drive | # Authenticate the BD drive | ||
sudo ps3dm -v sm drive_auth 0x29 # It should not fail !!! | sudo ps3dm -v sm drive_auth 0x29 # It should not fail !!! | ||
Line 135: | Line 48: | ||
* BD buffer 3 is of size 0x670 bytes. | * BD buffer 3 is of size 0x670 bytes. | ||
* S-Block is in decryoted EID2 at offset 0xa0 and of size 0x690. | * S-Block is in decryoted EID2 at offset 0xa0 and of size 0x690. | ||
==Test== | ==Test== | ||
Line 144: | Line 54: | ||
<pre> | <pre> | ||
# First enable writing BD buffer 3 | # First enable writing BD buffer 3 | ||
sudo ./bd_enable_buffer_write -b 3 | sudo ./bd_enable_buffer_write -b 3 | ||
# Write | # Write P-Block to BD buffer 3 | ||
sudo ./bd_write_buffer -b 3 -i sblock.bin | sudo ./bd_write_buffer -b 3 -i sblock.bin | ||
Line 160: | Line 67: | ||
* HRL is stored in BD buffer 4. | * HRL is stored in BD buffer 4. | ||
* BD buffer 4 is of size 0x8000 bytes. | * BD buffer 4 is of size 0x8000 bytes. | ||
<pre> | <pre> | ||
Line 181: | Line 86: | ||
* You cannot just write a new HRL to BD drive buffer 4. You can actually but it will corrupt your current BD HRL. | * You cannot just write a new HRL to BD drive buffer 4. You can actually but it will corrupt your current BD HRL. | ||
* If you corrupt your HRL then nothing bad will happen but you won't be able to play BD movies. | * If you corrupt your HRL then nothing bad will happen but you won't be able to play BD movies. | ||
* First you have to send P-Block to BD drive, after that authenticate the BD drive and then write a new HRL. Only in this order will it work | * First you have to send P-Block to BD drive, after that authenticate the BD drive and then write a new HRL. Only in this order will it work. | ||
<pre> | <pre> | ||
# First enable writing BD buffer 4 | # First enable writing BD buffer 4 | ||
Line 209: | Line 110: | ||
00008000 | 00008000 | ||
</pre> | </pre> | ||