I'm nor really sure if i have understood. You talk about a program that (you mean) GeoHot has writen it and it can edit the params and flags of the system configuration. Beside that you want to bring back JB for 3.75 FW. Is that correct ?
Hmmm... but you talking about NPDRM games right ? For what i know ALL PSN games are encrypted with the NPDRM Key and no one ever hase discovered it. The other games are Hybried-Psydo games that mostly contains a Debug EBOOT of the same game. So we can play thoes games. But there's a lot of games without a download able Debug EBOOT. Thats means we cant play this game on CFW.
But DUPLEX have found out the NPDRM key and for that they are able to Decrypt the EBOOT's - Hack them - and resign them so we can use it on CFW's.
Guide to Compile PSN NPDRM Games for PS3 Custom Firmware
Following up on the previous PSN game decryption news, today mallory has made available the PS3Tools NPDRM source code for reactivating PSN content followed by a brief guide from the included ReadMe file below for PS3 Custom Firmware users.
Based off of gitbrew's 215d8903bc86539ca1da53519e2ac10eeafc4c27 ps3tools. .git folder not included to protect senstive info about the author. Sorry about the messed up tabs, TAB = 4 SPACES 4 LYFE!!!
Add the files in the npdrm_keystuff folder to your ps3 keys folder.
Create a file with your console's 16 byte IDPS in the 'idps' file in your ps3 keys folder (e.g. ~/.ps3/idps).
Copy your PS3's exdata folder containing your act.dat and rif files to your ps3 keys dir (e.g. ~/.ps3/exdata/act.dat). Compile and have fun with your LEGALLY purchased NPDRM games!
Also works on free games without exdata/idps.
Apologies for any existing bugs in unself. Adding these changes to unself2 is left as an exercise for the reader.
fail0verflow for the orginal tools
JuanNadie for figuring out NPDRM
euss for his endless hours of work on the wiki
Why didn't you beat me to the punch, Team PS360? I didn't need to reverse a single instruction! It isn't that hard...
Added npdrm magic to unself2 and readself2
unself2 doesn't like the metadata section with type 3 in my game.
This section looks to be some kind of linking information. Here is a snippet: crt0:p190002crt1:p190002libaudio_stub:p190002libau dio_stub:p190002
I haven't yet looked around to see if this is type of section is documented anywhere.
Unself2 now ignores metadata sections of type 3 instead of aborting. Additional help with any remaining bugs would be greatly appreciated.
I'm sorry if everyone got the impression that these unself/readself modifications can, by themselves, "reactivate" your NPDRM content. These are just the first steps in the process. To those who say this is useless because you need act.dat and rif files: unless you can get unencrypted (debug) or easily decrypted (free, demos) PSN content, the only way to get the unencrypted files is by decrypting it with act.dat and the content's rif file.
There are no "crypto fails" here, proper decryption with the true keys is the only way forward. Using the NPDRM algo with the right keys is the only way to decrypt unless you let GameOS do it for you and hook into GameOS to either grab intermediate keys or dump decrypted content. Using hacks to restore the NPDRM decryption info to jailbroken PS3s is only a partial fix.
For instance, unless you patch vsh or set the SRTC to some time in the past, some content (even non-demos and non-trials!) expires until you log into PSN and reauthenticate. Sorry about your "technical difficulties", Team PS360. You should L2IRC.
Finally, from granberro comes PS3Tools NPDRM PKG Tools Fix V2 (npdrm-fix_v2) which includes changes, as follows:
I'd like to share with you my fork of failoverfl0w and geohot tools. I have fixed some bugs on fl0w tools and added all NPDRM stuff as well as mallory did.
What's different then?
unself (unself2 should not skip type 3 section IMHO) is able to save the key/iv used to encrypt the NPDRM and patch the eboot.elf for 3.41 consoles.
make_self_npdrm2 is able to encrypt elfs with the key/iv extracted by unself and, theoretically being accepted by OFW>3.55
With those tools, I've been able to "downgrade" LBP2 updates 1-4 and install them on a CFW 3.41.