[eddo]

So I have been using kmeaw for sometime now, and I was curious, what tells the ps3 what firmware is needed to run a game? Is it something in the eboot? Or is simply the keys from the game that tell the ps3 what firmware is needed?

I read on the forums quite a bit, and if anyone could point me the right direction, I will read it there. Thanks!

[itskamel]

Originally Posted by eddo So I have been using kmeaw for sometime now, and I was curious, what tells the ps3 what firmware is needed to run a game? Is it something in the eboot? Or is simply the keys from the game that tell the ps3 what firmware is needed? I read on the forums quite a bit, and if anyone could point me the right direction, I will read it there. Thanks!

i believe it is the eboot and the param.sfo

[eddo]

So the eboot contains the information regarding what firmware is needed? Seems a little odd, but couldn't you just edit the eboot then to tell it use whatever firmware you wanted?

[carldenning]

Originally Posted by eddo So the eboot contains the information regarding what firmware is needed? Seems a little odd, but couldn't you just edit the eboot then to tell it use whatever firmware you wanted?

we would beable to use eboot for higher firmware by signing it with 3.55 keys but the problem is we cant decypte it yet to be able to do that

[eddo]

Originally Posted by carldenning we would beable to use eboot for higher firmware by signing it with 3.55 keys but the problem is we cant decypte it yet to be able to do that

Ahh, I see, the information in the eboot is decrypted, and it is in the eboot that tells the ps3 what firmware is needed. Thanks!!

[Cheesethief]

The what firmware is needed part is the param.sfo, which can be easily changed. The problem really lies with the eboot. 3.60+ eboots are signed with different keys, keys which 3.55 does not have. Patches usually do something along the lines of repacking the eboot and signing it with 3.55 keys.

[eddo]

Originally Posted by Cheesethief The what firmware is needed part is the param.sfo, which can be easily changed. The problem really lies with the eboot. 3.60+ eboots are signed with different keys, keys which 3.55 does not have. Patches usually do something along the lines of repacking the eboot and signing it with 3.55 keys.

So then the keys in the 3.60+ are located (or not decrypted) in a different location of the eboot than those of the 3.55 and lower? Would it be easier then to decrypt the firmware of the eboot then creating a brand new CFW?

[KillerBug]

Originally Posted by eddo So then the keys in the 3.60+ are located (or not decrypted) in a different location of the eboot than those of the 3.55 and lower? Would it be easier then to decrypt the firmware of the eboot then creating a brand new CFW?

It would be easier to decrypt the eboot than to write a whole new CFW...but the keys are required to do either and we don't have them.

[eddo]

Just read that thread regarding the sfo building. How hard would it be to create a custom eboot and param.sfo?