92w ago - Following up on their previous 3.55 release, today the anonymous PlayStation 3 developers have shared details on remarrying PS3 Blu-ray drives on Firmware 3.15 and 3.50 without the need for downgrading the consoles.
4. Put the service mode JIG/dongle/PSGrade into port 0 (closest to the reader) and get into factory service mode.
5. Put the created USB Mass Storage device from step 3 into port 0 (closest to the reader) and run.
Drive Init Executing means it is starting the remarry process
Drive Init Failed with big pink letters 'NG' (No Good!) means the process failed. Most likely solved by fixing the communication issue with the drive.
6. After you run the initial remarry process, do not take it out of factory service mode.
7. Put a BD movie disc in and run it on the PS3. (This restores your DRL files!)
8. Then you can take it out of factory service mode.
9. Launch as normal.
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
I intentionally wrote wrong DRL and CRL hashes with VTRM service store_with_update.
After that i couldn't play my BD movies on GameOS.
Then i wrote correct hashes again and BD playback is working again
You will new decrypted EID2 data. How to get it on Linux is described here: (ps3devwiki.com/wiki/Spuisofs#Dumping_EID2_Key_with_spuisofs)
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. P-Block and S-Block DES-CBC IV and key:
IV: 00 00 00 00 00 00 00 00
key: 6C CA B3 54 05 FA 56 2C
P-Block is stored in BD buffer 2.
BD buffer 2 is of size 0x60 bytes.
P-Block is in decryoted 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.
Tested on my PS3 Slim with OtherOS++.
After writing P-Block to BD drive buffer 2, authenticate the BD drive with ps3dm.
# First enable writing BD buffer 2
sudo ./bd_enable_buffer_write -b 2
# Write P-Block to BD buffer 2
sudo ./bd_write_buffer -b 2 -i pblock.bin
# Authenticate the BD drive
sudo ps3dm -v sm drive_auth 0x29 # It should not fail !!!
ss status 0
S-Block is stored in BD buffer 3.
BD buffer 3 is of size 0x670 bytes.
S-Block is in decryoted EID2 at offset 0xa0 and of size 0x690.