Thread: Question about Eboots?

So I realize that eboots are what tells the PS3 what firmware to use and how to load the games. So, basically, it's a set of instructions, correct. With that being said, the new games with newer eboots are signed up new keys (as my understanding goes).

My question being, what exactly is in the eboot, and is it possible to make your own? I would think having the ability to create your own eboot, you could sign it with whatever keys you want (I'm assuming this is what TB does).

Thoughts??

No idea hahaha, im noob

no you couldn't. it has most of the important files from the game.
making your own would be the same as making your own game.
and the TB fixes come from debug eboots.

a game eboot is like a a windows exe. It is responsible for booting up games and it doesn't tell your ps3 what fw to be used, this job is done by PARAM.sfo. New eboots are encrypted with sony's DRM, we cant exactly say keys until the encryption is broken

Originally Posted by Popman

no you couldn't. it has most of the important files from the game.
making your own would be the same as making your own game.
and the TB fixes come from debug eboots.

Actually, you can. EBOOT files just unite all resources from the game in one single memory process, it's not the entire game in there. It is possible what OP said, but very hard. First of all, you need a SDK (for the firmware required by the game) to be leaked from Sony, which is a very hard job to do. Then, you need to understand very good programming languages, such as C or ASM (to understand how the encrypted EBOOT works, and based on the leaked SDK, to create a new one in the same language, but decrypted, that's where ****'s getting serious and that's why you need to know programming languages very good). Finally, you can encrypt the new EBOOT with 3.50 keys and you're done. TB's using masterdiscs function, not debug EBOOTs. The only fix done with debug EBOOT is the Uncharted 3 one.

So you think the Eboot are based on an proprietary SDK..that makes some sense. I know we have the capabilities to edit some of the eboot files in the older games due to keys. I am curious as to the structure of these eboot files. I am thinking if you could remove the references to the FW requirement (this is then linked to the param.sfo) if it would be possible to play the newer games, regardless of fw. I don't know if this is key specific or not.

Yes, I do. That's actually the way an EBOOT is created in Sony's Labs.

my understanding is that the ps3 works by going through various security algorithms after which a key is derived and the previous algorithm is deleted before going to the next step. during this process the key is changed several times until it arrives at the proper key when decrypting the eboot of a game.

u could change the sfo firmware requirement, but it wouldn't work because the keys r different as is the encryption. if someone could discover the master key, sony could change the encryption, but it would be decrypted within hours using the master key. it would probably also lead to cfw regardless of ofw. I'm sure this will eventually happen or some other exploit will be discovered allowing full access to all of the ps3's functions.