This POC requires you to have a debug PlayStation 3 and is recommended for the more advanced user as it involves crashing your console/game in order to get the RAM dump and decrypted EBOOT.
Hello there my friends…as you may or may not know i have been looking into the possibility to get a full core dump from my ps3….a few hours ago i was sent a pm from ANON … here it is….
Yeah cfwprophet told something about the ram dump too. you can make a core dump on a Dex.
here is a quote from him:
“I say it now for the last time: There is NO fself for new games !! TrueBlue use the CoreDump function and a RSX exception to dump the games like i told the scene for over a half year.” Take MultiMan 04.02 which is a Retail NPDRM >> enable core dump function >> start MultiMan >> exit to XMB and be surprised. The Coredump function is a embended system of the debug FW and get handled of liblv2dbg. The send signal call aka send_signal_to_coredump_handler() and the trigger function are always running and CAN NOT be deactivated.”
He also said that you will get one 250MB file. there you have to search the decrypted file(s). It would be pretty sure that they use this method, because newer games wouldn’t have debug eboots or fselfs. If you open a tb eboot with a hex editor, you will see near at the end , that they stand right after the codes some passages with ‘liblv2′. if you open a original eboot , you cant find passages with ‘liblv2′. Like cfwprophet said, the core dump get handled of ‘liblv2dbg’ and you can find ‘liblv2′ passages in tb eboots. so they use coredump pretty sure.
But the problem is to trigger a crash or so. i really dont know. I’m not a dev and don’t have an idea. I just wanted to tell you this info’s because I saw your post about coredump.