[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.

[Retrohelix]

thread closed?Aw man i thought you were on to something there!

[EX-OD-US]

Originally Posted by Retrohelix thread closed?Aw man i thought you were on to something there!

I have to had fixed the header.
************* [ - Post Merged - ] *************
I might as well post the un-revised header anyway;- I would sense some curiosity coming from some of you. Maybe an Eboot compatibility list would help as-well.

[capostef]

the same thread was yesterday closed by ps3iso because the Values are Vita aes keys....

[EX-OD-US]

Originally Posted by capostef the same thread was yesterday closed by ps3iso because the Values are Vita aes keys....

The "keys" that were posted on PS3ISO were not of AES-key derivation (Coming from the Vita). Those are the same keys that were posted by the other members of the team. The headers of both posts are un-revised; and only compatible with a few (If not listed/unlisted) games.

[Caddyroo]

Which games are compatible then, if you let me know this I'll test them all out

[EX-OD-US]

Originally Posted by Caddyroo Which games are compatible then, if you let me know this I'll test them all out

If we are to make a compatibility list (With only this un-revised version) it would most likely be deemed useless by users who are resorting to use the same Eboot fix for every game above firmware version 3.55. Think of this as only being a progressive. If you are willing to test the header with one of your games; by all means, please do it. The community may create a compatibility list of the current header;- for now.

[capostef]

which tool can change the header?

[H3avyRa1n]

can you give an example of a game in which you have done this and worked?

[capostef]

I think games where do you fix only the eboot.bin could work. Final Fantasy has 4 sprx files and eboot.bin.