Originally Posted by enosrasun
start comparion original eboot from game with fix eboot released ,
and the right question if you don't have 3.60+ keys how you decrypt 3.60+ eboot?????? and modify it?????????
and the logical answer !!!!!! if you can decrypt 3.60+ ,you have 3.60+ keys!!!!!!!
and decrypt this eboot ,I have fail
Ok I downloaded the eboot.rar but the archive is corrupted. fails CRC check and I can't unpack it. maybe you could upload it again in it's original eboot.bin format or just tell me from what game it came and i'll get it 'somehow'.
as for the 3.60+ eboot's, All true blue Eboots are 3.55 encrypted.(And you would only be able to compare 3.60+ eboots if they are decrypted, otherwise when you open them they will just be gibrish and you would be comparing random charaters. no 3.60+ keys = not looking into 3.60 eboots)
Try to run a TB game trough multiman's eboot fixer and it will fail at converting sprx files, the eboot get converted just fine. The error that you get is an make_self_npdrm error witch has nothing to do with 3.60+ keys in my opinion. That has to do with the true blue's OWN DRM keys.
if you check the wiki you'll see that they manage to decrypt all DRM locked files from the dongle, even the payload that's on the dongle.
I think if you could ad the TB DRM keys to the eboot fixer, you could just run a TB game trough Multiman's eboot fixer and play it on any 3.55 CFW.
And please if I'm wrong, witch could very well be, explane where the fault is in the theory so that I learn and move along. I am learning as I go Along.