PRXdecrypter 2.3 (6.10 EBOOT.BIN keys & user modules)

Contains all the 6.00/6.10 EBOOT.BIN keys, just like those in Yoshihiro's decrypter.

VERSION 2.3 DOES NOT NEED prxdecrypter_03g.prx

2.25 --> 2.3
- "Analyze files" option added to menu - displays info about the files without changing them
- User module keys up to 6.00, not sure if they're the ones used in the firmware though!
- Fixed decryption issue - extra data added to decrypted files
- Rewritten kernel modules for 2.XX+ allowing fewer external files and cleaner code
- Rewritten handling of compressions - 1.50 has RLZ with the correct file, 2.71 to 3.80 have RLZ, 3.80+ has KL3E, KL4E and may have RLZ depending on the exact firmware version

2.1 --> 2.25
- 2.2 - limited release, 5.00 keys
- 2.25 - EBOOT.BIN keys up to 6.00! (Many thanks to an anonymous friend)

There is another odd one not present in either decrypter: 0xD91612F0 (if you get an error message with this code, post here! I need to work out where this tag is being used. EDIT: Gran Turismo from PSN seems to be one of them)

To anyone on PSPGEN who accused Yoshihiro of copying/stealing my work: this is complete nonsense.

You should be able to decrypt any of the below EBOOT.BINs (except the last one) even on 5.00 M33 and below, as long as PRXdecrypter runs.

General EBOOT.BIN keytags info
The classics:
Tag 0x08000000 - 1.xx EBOOT.BIN
Tag 0xC0CB167C - 2.xx EBOOT.BIN

Unknown if these were ever used, but I found them ages ago - Sony were planning new EBOOT keys for a long time:
Tag 0x8004FD03 - 2.71 EBOOT.BIN
Tag 0xD91605F0 - 2.8X EBOOT.BIN
Tag 0xD91606F0 - 3.0X EBOOT.BIN
Tag 0xD91607F0 - ???
Tag 0xD91608F0 - 3.1X EBOOT.BIN

These are now being used:
Tag 0xD91609F0 - 5.00 EBOOT.BIN
Tag 0xD9160AF0 - 5.50 EBOOT.BIN
Tag 0xD9160BF0 - 5.55 EBOOT.BIN
Tag 0xD9160CF0 - 6.00 EBOOT.BIN (which game(s) use this?)
Tag 0xD91611F0 - 6.00 EBOOT.BIN (which game(s) use this?)
Tag 0xD91612F0 - 6.00 EBOOT.BIN (GTN USA - PSN edition, any others?) not decrypted!

Excellent work. I always prefer your decrypter cuz you allow set the folder and stuffs.

wow nice job mate!

Janson is BACk. Great work as always. Let me understand better...it don't decrypt totally 6.00 and 6.10. Yoshihiro has decrypted full 6.00 (I don't know on 6.10)...

No, you are correct, it doesn't decrypt 6.00/6.10 firmware - the keys are available but there is a consensus to not release them yet, until the PSPgo has been released.

fantastic

Thanks for the tool. The Go was already released so may i assume you mean the japanese launch which is around a month away?

Originally Posted by jas0nuk

the keys are available but there is a consensus to not release them yet, until the PSPgo has been released.

Do you mean Psp Go Hardware?. I remember same matter for 6.00GEN. But Pspgo is already released.

Janson you go away leaving all us with dilemma...

Pspgo release = key released = full Prxdecrypter.

I think that team Gen will leave 6.00GEN for 6.10GEN.

Team Gen said that would release 6.00GEN (Also it) after psp go gone out. This mean that 6.00GEn or 6.10GEN will be released soon?. Beside. until psp go not released, is a strange thing...Hardware and software are same from months. It was not produced yesterday or today. Then, this is a strange thing...

I have a small request to ask you jas0nuk.

See in the other decrypter it give a message that no need to decrypt older files so then we know the game don't need no fixings. But your decrypter decrypt everything which is better but then we dunno if it was really necessary.

But could you maybe add an option in your menus (Info). when click Info it does a test and only tells you what kinda encryption the file has. Like it would display 5.55 and what type of tag like in the read me.

Tag 0xD9160BF0 - 5.55 EBOOT.BIN

i dunno what you thinks? Thanks fer your good werks.

StonerCold sounds like he has a good idea...

Anyways thanx for the update. keep up the good work.

damn good ! good work jas0nuk !!

legends never die !

jas0uk guy. One more question for you if yah returns.

I hex compare decrypted EBOOT.BIN from undead knights with prxdecrypter vs the gamedecrypter. And the two eboots come out different in size slightly. You have extra stuff added to end of EBOOT. Or gamedecrypter has missing stuff. I not sure if it suppose to be missing or extra. I think you always had this extra stuff for all version prxdecrypter.

The tiny may matter because some game use LBA. What you think about this? Who is right extra data or missing data in the eboot? just curious you do nice job still.

stonercold for info , look into SYSDIR folder. u will c 2 files , EBOOT.BIN(encrypted) and BOOT.BIN(dummyed) . so after u decrypt EBOOT.BIN , the size of this file have to be identical with BOOT.BIN byte by byte !

i hope i dont have to explane why etc ?

use the logic next time buddy.

i can tell u for shure what Yoshihiro decrypter works 100% correctly

Originally Posted by DeathMan

stonercold for info , look into SYSDIR folder. u will c 2 files , EBOOT.BIN(encrypted) and BOOT.BIN(dummyed) . so after u decrypt EBOOT.BIN , the size of this file have to be identical with BOOT.BIN byte by byte !

i hope i dont have to explane why etc ?

use the logic next time buddy.

i can tell u for shure what Yoshihiro decrypter works 100% correctly

Yah i get it. But that's why i bring it up. Because the prxdecrypter don't produce a file the same exact size as boot.bin at least not for this game. It is oversized with prxdecrypter and correct size with gamedecrypter. But i like prxdecrypter

Great work. Superb, to be honest. Does this means a step foward towards a CFW? Forgive me if i got it wrong, i'm just trying to understand. Thanks and cheers!