73w ago - Below is a work-in-progress (WIP) of PS3 3.60+ games booting on PlayStation 3 Custom Firmware (CFW) 3.55 and 3.41 without a dongle for those interested in experimenting further with it.
What you need ?
1- PS3 3.55 CFW Rebug or 3.55/3.41 with Debug
2- Debug Dev_Flash (Also allow to have the debug options on retail)
3- Backup of your own CFW DEV_Flash (make a dev_flash path on your USB Device)
4- A File Manager
5- EBOOT.BIN of your games (also from Paradox)
What you need to know
Rebug normal in Debug mode 2
You need to put your PS3 in boot mode -> debugger mode (and not system software mode)
We're gonna use the debugger mode to debug the self execution we don't need to have NPDRM, anyway the debugger don't know how to Debug the Self NPDRM
Release mode -> Development mode
All the content type configuration -> Development mode
Dongle uses modified sprx/modules/lib related to the Debug files to be loaded when you boot the PS3 on CFW.
Almost all the EBOOT Paradox don't have NPDRM -> it's a simple self (fake sign header) renamed to EBOOT.BIN (like i was explaining many times) -> call function to the debugger -> sprx/modules loader.
Let's do a small test to be sure that you understand.. take whatever EBOOT Paradox, open with editeur hexa, check the first header ->
You can see that is a standard Self without NPDRM only have a fake sign header.
Rename this file EBOOT.SELF than .bin transfer your self on your usb stick/storage, launch a file manager, add the self to the path of your game and execute your self after that, self will load on the path APP_HOME of your XMB.
If you launch that with the debugger mode, it execute without problem and the debugger don't need to have NPDRM (anyway the debugger don't know how to read Self NPDRM)
Why we need debug_devflash
We need that to replace some specific temporary file to allow to boot on debugger mode and reload the XMB, also the backup of your dev_flash CFW it's here to put back your files (that allow to reboot without crash).
I don't put all now put this is one of the step and WIP of game 3.60+ boot on 3.55/3.41. Remember that the dongle use also standard Self to be load on a debugger mode.
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!
Yep for the reasons ps3hen mentoined and also for downgrading even up to latest fw and the abbility to use homebrew in case of we can decrypt the allready existing hb and fake sign them with actuall SDK's. A full dex converted console can be updated and then downgraded via special_downgrader.pup's.
Also sony changed something with the PS3GEN tool. On older versions you can't use retail selfs to gen a ISO img. Now the newer tools also accept retail signed and encrypted games. Maybe this is in case off that now also retail eboot's can be run with a generated ISO via streaming from pc or/and also as a bd-emu img.
And for the dex kernel. It can be run on retail conosole with QA flag, changed IDPS but thats still NOT a full debug console. There are still other things that need to be done.
I think it is because with full debug capabilities you can boot into modes other than "Release Mode", like "Debugger Mode" which supposedly is the key to using the ps2 emulator on non-BC ps3s and running debug eboot.bin files.
Or at least that's how I've interpreted it. As far as I know, to do this you flag your ps3 in the right places so the DEX lv2_kernel.self will run and give full debug capabilities. But where and with what is not fully known, well not publicly at least.
hi, i'm an italian members finally someone who gets something! time ago I tried to mix the firmware but no success clearly not a dev, but I progskeet so if you want to offer myself to test the firmware. what we are doing opens the way for many of the dev scene.
Thanks and keep up, do not listen to all those who say that this is false.. good job and not give up.