Props to jd200 for the news, and from the author: Hello guys, I'm working on a tool called PS3 ISO2JB.
This tool will allow your backed up PS3 .iso images to be extracted properly and automatically, then played via Backup Manager.
More news coming once tool is finished. Our forum for it check http://teknogods.com
1. Run tool
2. Open your backup .iso
3. Make folder called GAMEZ in your external USB HDD
4. Extract ISO in GAMEZ (do not make any subfolders!)
5. Run Backup Manager on PS3 with USB HDD plugged in
Required: Jailbreaked PS3 with backups enabled, External USB HDD.
This release is beta quality. If something breaks, review any
pertinent comments on teknogods.com, then email me as a last resort.
Include all log files and a detailed description of problem and
how to reproduce it.
Our community of course! Make sure you also check out our StarCraft2 and Red Alert 3 Progress!
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!
IDK know much about on how a PS3 works (specially because i don't own one ), but from what i understand, no one knows how to encrypt/decrypt the eboot.bin files - not even backup manager. What i believe that backup manager does is something like this:
lv2: Sends the encrypted eboot.bin to a PPU
PPU: does basic initialization
PPU: requests SPU to start up in isolation mode
SPU: decrypts lv0 and puts in somewhere PPU can access it
PPU: waits for SPU to finish decrypting lv0
PPU: executes decrypted lv0 code
PPU: lv0 sends message to still running metldr SPU to decrypt lv1
SPU: decrypts lv1 and puts in somewhere PPU can access it
PPU: waits for SPU to finish decrypting lv1
PPU: executes decrypted lv1 code
PPU: lv1 sends message to still running metldr SPU to decrypt lv2
SPU: decrypts lv2 and puts in somewhere PPU can access it
PPU: waits for SPU to finish decrypting lv2
PPU: executes decrypted lv2 code
So, in reality, backup manager isn't doing any decryption, but rather grabbing the already decrypted eboot.bin from somewhere on memory/hdd.
to decrypt (or encrypt) i believe that you would need to know the hardware root keys, which is something that no one knows and probably will never know.
It would seem like backup manager itself decrypts the eboot.bin as the file is dumped to the drive since playing an OLD Other OS dumped ISO doesn't work meaning it's not decrypting on the fly. Can't someone just reverse engineer the backup manager decrypt part of the code?