EBOOT.BIN Decryption

[Darth1701]

OK, I finally had the time to test the new decryption engine and I have a few thoughts:

1) On my machine the decryption process is rather long, about 10-20 secs. It would be good to save the decrypted eboot.bin in the TMP dir as well so when I run it again the emulator uses the already decrypted version. Of course I always can pre-decrypt the games (I still prefer it that way for now).

2) This would be true especially for the bigger data files (Kingdom Hearts is about 600 MB of crypted data files) once the PGD decrypting is in place.

3) This has not so much to do with the eboot.bin decrypting but more a general thing: The whole TMP situaton annoys me a bit: Every time I switch to a new revision I have to carry the new pre-decrypted data files with me while deleting the whole WAV files. I would prefer a setting for the TMP path (or whatever) so I can set it to a path I choose (much like the UMD path). Same goes for the save path.

[Hykem]

OK, I finally had the time to test the new decryption engine and I have a few thoughts:

1) On my machine the decryption process is rather long, about 10-20 secs. It would be good to save the decrypted eboot.bin in the TMP dir as well so when I run it again the emulator uses the already decrypted version. Of course I always can pre-decrypt the games (I still prefer it that way for now).

2) This would be true especially for the bigger data files (Kingdom Hearts is about 600 MB of crypted data files) once the PGD decrypting is in place.

3) This has not so much to do with the eboot.bin decrypting but more a general thing: The whole TMP situaton annoys me a bit: Every time I switch to a new revision I have to carry the new pre-decrypted data files with me while deleting the whole WAV files. I would prefer a setting for the TMP path (or whatever) so I can set it to a path I choose (much like the UMD path). Same goes for the save path.

1) Indeed. I was thinking about adding some sort of option to allow extraction of decrypted versions of data. Since this will be required for savedata, it may be a good idea to supply it too for PRX and avoid calling the CryptoEngine every time.

2) Same as 1.

3) Don't worry, I haven't forgot about this request.
I'm planning a total rewrite of the TMP working folder mechanics. It will have to support decrypted data saving for savedata, EBOOT and PGD stuff (and also, for a near future, certain user modules), so, I'll be adding these changes as soon as I get savedata encryption/decryption running perfectly.

[Darth1701]

OK, I finally had the time to test the new decryption engine and I have a few thoughts:

1) On my machine the decryption process is rather long, about 10-20 secs. It would be good to save the decrypted eboot.bin in the TMP dir as well so when I run it again the emulator uses the already decrypted version. Of course I always can pre-decrypt the games (I still prefer it that way for now).

2) This would be true especially for the bigger data files (Kingdom Hearts is about 600 MB of crypted data files) once the PGD decrypting is in place.

3) This has not so much to do with the eboot.bin decrypting but more a general thing: The whole TMP situaton annoys me a bit: Every time I switch to a new revision I have to carry the new pre-decrypted data files with me while deleting the whole WAV files. I would prefer a setting for the TMP path (or whatever) so I can set it to a path I choose (much like the UMD path). Same goes for the save path.

1) Indeed. I was thinking about adding some sort of option to allow extraction of decrypted versions of data. Since this will be required for savedata, it may be a good idea to supply it too for PRX and avoid calling the CryptoEngine every time.

2) Same as 1.

3) Don't worry, I haven't forgot about this request.
I'm planning a total rewrite of the TMP working folder mechanics. It will have to support decrypted data saving for savedata, EBOOT and PGD stuff (and also, for a near future, certain user modules), so, I'll be adding these changes as soon as I get savedata encryption/decryption running perfectly.

Ah, OK. I then just wait and see. BTW, are you planning on ENCRYPTING the savegames as well so I can use the saves from JPCSP on the PSP or is the feature more like decrypt the PSP savegame and then save it to a plain savegame file from there on with no way to going back?

[Hykem]

OK, I finally had the time to test the new decryption engine and I have a few thoughts:

1) On my machine the decryption process is rather long, about 10-20 secs. It would be good to save the decrypted eboot.bin in the TMP dir as well so when I run it again the emulator uses the already decrypted version. Of course I always can pre-decrypt the games (I still prefer it that way for now).

2) This would be true especially for the bigger data files (Kingdom Hearts is about 600 MB of crypted data files) once the PGD decrypting is in place.

3) This has not so much to do with the eboot.bin decrypting but more a general thing: The whole TMP situaton annoys me a bit: Every time I switch to a new revision I have to carry the new pre-decrypted data files with me while deleting the whole WAV files. I would prefer a setting for the TMP path (or whatever) so I can set it to a path I choose (much like the UMD path). Same goes for the save path.

1) Indeed. I was thinking about adding some sort of option to allow extraction of decrypted versions of data. Since this will be required for savedata, it may be a good idea to supply it too for PRX and avoid calling the CryptoEngine every time.

2) Same as 1.

3) Don't worry, I haven't forgot about this request.
I'm planning a total rewrite of the TMP working folder mechanics. It will have to support decrypted data saving for savedata, EBOOT and PGD stuff (and also, for a near future, certain user modules), so, I'll be adding these changes as soon as I get savedata encryption/decryption running perfectly.

Ah, OK. I then just wait and see. BTW, are you planning on ENCRYPTING the savegames as well so I can use the saves from JPCSP on the PSP or is the feature more like decrypt the PSP savegame and then save it to a plain savegame file from there on with no way to going back?

No, I'm also planning to allow saving encrypted savedata too, since there are specific savedata modes in sceUtility just for that and it could help testing some of the encryption schemes employed by the chnnlsv module in the PSP.

[avin4]

OK, I finally had the time to test the new decryption engine and I have a few thoughts:

1) On my machine the decryption process is rather long, about 10-20 secs. It would be good to save the decrypted eboot.bin in the TMP dir as well so when I run it again the emulator uses the already decrypted version. Of course I always can pre-decrypt the games (I still prefer it that way for now).

2) This would be true especially for the bigger data files (Kingdom Hearts is about 600 MB of crypted data files) once the PGD decrypting is in place.

3) This has not so much to do with the eboot.bin decrypting but more a general thing: The whole TMP situaton annoys me a bit: Every time I switch to a new revision I have to carry the new pre-decrypted data files with me while deleting the whole WAV files. I would prefer a setting for the TMP path (or whatever) so I can set it to a path I choose (much like the UMD path). Same goes for the save path.

1) Indeed. I was thinking about adding some sort of option to allow extraction of decrypted versions of data. Since this will be required for savedata, it may be a good idea to supply it too for PRX and avoid calling the CryptoEngine every time.

2) Same as 1.

3) Don't worry, I haven't forgot about this request.
I'm planning a total rewrite of the TMP working folder mechanics. It will have to support decrypted data saving for savedata, EBOOT and PGD stuff (and also, for a near future, certain user modules), so, I'll be adding these changes as soon as I get savedata encryption/decryption running perfectly.

Ah, OK. I then just wait and see. BTW, are you planning on ENCRYPTING the savegames as well so I can use the saves from JPCSP on the PSP or is the feature more like decrypt the PSP savegame and then save it to a plain savegame file from there on with no way to going back?

No, I'm also planning to allow saving encrypted savedata too, since there are specific savedata modes in sceUtility just for that and it could help testing some of the encryption schemes employed by the chnnlsv module in the PSP.

Well this is my first reply thread and I'd like to say...yes, using encrypted savedata on real PSP is the feture I want most....

[br222]

hi,
decrypted eboot whitout psp is it possible?

[Darth1701]

hi,
decrypted eboot whitout psp is it possible?

Not for downloaders

[Hykem]

As of r1993 PRX decryption has been restricted to boot modules, to avoid the crashes BlackDaemon was referring to.

Also, the TMP folder handling has been improved, as requested by Darth1701. It can now be changed to any other folder, plus, it also supports decrypted EBOOT.BIN extraction.

The EBOOT.BIN extraction has to be turned on under Options>Configuration>Crypto>"Extract decrypted EBOOT.BIN to TMP folder". Also, only one file at a time is extracted, because it's not possible to keep trace of the game's DISC ID during the Loader stages without some tough code changes. Fortunately, this also works as a great anti-piracy measure.

If you haven't figure out yet, JPCSP allows reading of unpacked boot modules, which means you can place your decrypted boot module in the working directory and it will be loaded instead of the ISO/CSO's original EBOOT.BIN/BOOT.BIN.
All you have to do is name it as [DISC ID].BIN and place it were you have your start batch file.

So, if you load a game with this option turned on, it's decrypted EBOOT.BIN will be stored in the current TMP folder in a EBOOT folder. All you have to do next is manually rename it to [DISC ID].BIN and copy it to the working directory to save the emulator a call to the CryptoEngine.

[Kai3213]

So with the option turned on the eboot will be extracted to the tmp folder and then you rename it to the disc ID and place it in the main jpcsp directory where the launching file (start-windows-x86 in my case) is located, right?

P.S You probably know this already but in rev 1993, the new "Enable saving GE screen to Texture" is missing.

[hyperspeedgx]

P.S You probably know this already but in rev 1993, the new "Enable saving GE screen to Texture" is missing.

That's right.