eboot.bin - more comprehensive guide?

[ocat1979]

thanks for the advice, though I have one conflicting part which I cant for the life of me determine.

example is GT5, the highlighted section is located right after the first encrypted metadata area.

was comparing to prepatched eboot to make sure I was working along correctly

I don't understand where the highlighted section is coming from in the prepatched eboot, is this some type of checksum of the metadata which I need to insert back into the eboot as well?



edit: also, how do you deal with compressed meta data sections?

Yeah i'm seeing the same thing, i'm finding all the eboot.bin's i hack are slightly different to know working hacked eboot.bin's.

This leads me to believe the the unself eboot.bin eboot.elf is not decrypting properly. I'm using cygwin on Win 7

I'm at a roadblock now, i'd really like to do all this myself instead of relying on others.

Cheers

[Jewrye]

Yeah i'm seeing the same thing, i'm finding all the eboot.bin's i hack are slightly different to know working hacked eboot.bin's.

This leads me to believe the the unself eboot.bin eboot.elf is not decrypting properly. I'm using cygwin on Win 7

I'm at a roadblock now, i'd really like to do all this myself instead of relying on others.

Cheers

I'm also using the cygwin versions, that data is outside of the block the meta data should be in though, so I'm not sure where it's coming from. Hopefully someone can share some insight

[fullmetal172]

I'm also using the cygwin versions, that data is outside of the block the meta data should be in though, so I'm not sure where it's coming from. Hopefully someone can share some insight

same here, same thing lets hope someone could shed light on this and the only 2 guys that know are not even responding to their pm's or anything

[whodingy]

that's a very good question! whether it's some sort of 64bit hash or something for the block or something else, i don't know. maybe someone can shed some light on it cuz i certainly don't know.

[ocat1979]

Just found this quote on another site, seems my suspicions maybe correct:

"Can't edit the decrypted .elf file correctly because Unself for windows doesn't decrypt everything correctly. I think the working modded EBOOT.BINS are created by people using the linux version of the same tools."

[Jewrye]

Just found this quote on another site, seems my suspicions maybe correct:

"Can't edit the decrypted .elf file correctly because Unself for windows doesn't decrypt everything correctly. I think the working modded EBOOT.BINS are created by people using the linux version of the same tools."

interesting if true, though like I said, that extra data I highlighted is actually outside of the decrypted metadata block, so I'm still unsure where it's actually being pulled from to be written

[whodingy]

interesting if true, though like I said, that extra data I highlighted is actually outside of the decrypted metadata block, so I'm still unsure where it's actually being pulled from to be written

but are you finding this difference on multiple games or just this one? also, if you don't have those mysterious changed bytes (i.e. keep them as original) does it not work?

[mote]

I've compared all of my selfmade Eboot with the working one and they are always a few parts different like Jewrye mentioned above and its not working, always take me back to the xmb when loaded. I'm using cygwin with windows 7 too.

[ocat1979]

Here's a screen cap comparing the GT5 eboot.

I have the original untouched (bottom left), a know working cracked eboot (top left) and my elf that was generated form using the unself tool on the original eboot.

As you can see there is clearly a problem with the unself.exe tool not decrypting properly

[Katsuhiko]

Unself decrypts properly, the only thing is, you don't know what to do.

It was explained somewhere in this Thread http://psx-scene.com/forums/f6/ps3-v...v3-41-a-74338/ (PS3 v3.50 Game EBOOT's Rewritten for v3.41!)