[H3avyRa1n]

Originally Posted by devilangelari So what you're saying is that we should put this custom header to the original (not TB) eboot.bin header and it will do the miracle right ? So what you're saying is that if we put this header then the unself tool will decrypt it properly to .elf then we can re-encrypt with 3.55 keys ? Or you think that this header it will make the original +3.60 eboot.bin playable straight away ? Gonna test it with PES2012 and Asura's wrath as I have these games with +3.60 keys and I have today alot of spare time.

please do and let us now. thanks

[Adamsville]

uploaded copy of eboot from US Spiderman Edge of Time in case someone wants to test Exodus work but didnt want to download big files...

http://pastebin.com/AFz0vp6J

edit it and I'll test it

[Adamsville]

Originally Posted by devilangelari EX-OD-US why did you write that ? So it's not a "complete" header ? How did you find this particular header in first place ?

damn didnt see that part... Im going to sleep

[rdgcrew]

has anyone test it? This will let us play any game? That is all we want..lol no need a 4.10 cfw

[furtsiv]

Originally Posted by EX-OD-US As you all probably know;- Eboots are what preventing 3.60+ games from loading/starting up on our most current of custom-firmware. Due to the most recent of "pop-ups" (Shall be kept without enunciation of exploits found;- to be announced later on) A couple of project-entrepreneurs (Including myself) have been working anonymously on the foundation of Eboot encryption. The mechanics didn't have much of a technical endeavoring (With already known knowledge;- it was practically common-sense in the end with Sony's past mistakes; and our prestige of research/study era/ethics). But we have gathered and retained our status in understanding how the Eboots of the past and in the now-- work. We have not pronounced any of our work-aesthetics (In the past);- it would and/or may have been subjected to critical/blatant controversy. To now rejoice;- the "culmination-technic" is here: 1.) Copy the original Eboot from BLUS-(Acquired Variables/Numeric)\PS3_Game\USRDIR\EBOOT.bin 2.) Replace the header of the Eboot with this: 0x33, 0x81, 0x8D, 0x70, 0x9B, 0x60, 0xE6, 0x2B 0x07, 0xF2, 0xC6, 0x82, 0x90, 0xB5, 0x0D, 0x2C 0x47, 0x51, 0xR6, 0x17, 0xF3, 0xC1, 0x9Z, 0x38 (This is the un-revised version of the header;- you may still be able to try it) 3.) Save and close;- copy the data back to an external HDD/Unit storage device (Overwrite the old Eboot) 4.) Launch the game in multiMAN (No other modifier/use of a backup-manager was interacted with);- change the parameter to 3.55 (You may do it manually) TO TAKE { WITHIN NOTICE: This may be patched by Sony in next firmware update, but at-least we get to play the most current/latest of games. This will not work on True-Blue Eboots because those contain a DRM-possesion;- preventing them from running without the dongle itself.

as we knows the only way to get games work is to find keys used on eboots(don't tell me that the ps3 could run somthing ho do no understand )
so the eboot must be decrypted to be logical to understand it
by your methode the ps3 will decrypt it if we change the header right ?
how could you explain all that (Mr Amro Azzam)??

[DzhoPS3HAX]

can you post a fixed eboot to proove?

[H3avyRa1n]

Originally Posted by DzhoPS3HAX can you post a fixed eboot to proove?

the header is "incomplete" as he says so I doubt he has anything working.

[pratiko]

Originally Posted by H3avyRa1n the header is "incomplete" as he says so I doubt he has anything working.

he said he fixed it, so he opened the thread again.
I'm gonna try this in the afternoon, 9am here atm.

[DzhoPS3HAX]

Originally Posted by H3avyRa1n the header is "incomplete" as he says so I doubt he has anything working.

i know already it
but can he upload a eboot with uncomplete header
it s interess me to show something,if you see what i am meaning

[Pockets69]

LOOOOOOOOOOL