Contrairement à ce que l'on pensait au début, ce n'est pas via des EBOOT.BIN debug que l'équipe True Blue craque ses jeux, mais via une autre technique nécessitant de faire planter la console.
En effet, sur les consoles tournant sur firmware DEX (debug) (obligatoirement !), si vous chargez un jeu et que vous faites planter la console via un core dump que vous pourrez récupérer et qui contiendra toute la mémoire (250mo) de la PS3, y compris le jeu décrypté.
Ensuite le travail pour convertir le dump en un jeu lançable commence ...
‘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 wouldnt 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. im not a dev and dont have an idea.
i just wanted to tell you this infos because i saw your post about coredump.
Voici un dump et un fichier log :
http://letitbit.net/download/25578.24e4 ... p.rar.html
http://www.sendspace.com/file/6wd806
Source : http://www.ps3hax.net/2012/08/pwnage-ps3-full-core-dump/