To quote, roughly translated: Tools to fix your game 3.56 to 4.30 for CFW v1.71 by Attila
Here are some scripts to simplify the use of tools scetool and other tools to convert your games requiring a firmware higher than 4.30 to 3.55 until they walk firmware 3.40, 3.41, 3.55 or another by your own fix.
These windows allow for batch scripts from your game or your bluray update (pkg) to patch the files so that you can make your own fix your game and launch 3.40-3.55 3.60.
Warning: These tools can cause bugs in your PS3. If possible, have dumps done with E3 debricker order, or in case of incorrect handling.
extract_pkg.bat: extract it your PKG "NPDRM" containing updates to games, demos or content of PSN / SEN. Drag your file above.
eboot_self_sprx_decrypter_recrypter.bat: Decrypt EBOOT.BIN all your files, *. self, *. SPRX games or bluray from PKG NPDRM extract it, change all occurrences of 3.60 by 3.40 (sys_proc_param, keyset etc.) to re-encrypt the game so that it is compatible 3.40 / 3.55. Beware, some self / SPRX update klicense need a specific (see klicense_cracker). Drag the file to decrypt it.
BruteForce.exe: Tool by Aldostool, klicense can find the (unique key per set) to decrypt the files self / SPRX updates for certain games. Take the EBOOT. BIN file and a self SPRX or supplied with the game and place them in the program folder. If you found the key, use the notepad to edit "eboot_self_sprx_decrypter_recrypter.bat" KLICENSE1 line, replace the key with this one you found.
patch_paramsfo.bat: Slide your PARAM.SFO file to change the version number 3.40.
create_pkg.bat: You will need to add psn_package_npdrm.exe Sony SDK to create your PKG. Drag the folder containing the folder "USRDIR" of the bat file.
(Use instead Bruteforce.exe) klicense_cracker.bat: Allows you to find the klicense (unique key per set) to decrypt the files self / SPRX updates for certain games. You will need to put EBOOT.BIN decrypted (with the previous tool) and a file named EBOOT.BIN.elf or self SPRX patch.self named folder in the bat file.
Note: it may take a long time and several popups error can potentially occur. Ok done, and wait until you find the key. If you found the key, use the notepad to edit "eboot_self_sprx_decrypter_recrypter.bat" KLICENSE1 line, replace the key with this one you found.
Removed parameter t which caused problems with SCETool.
Update Tool FixELF.exe
Added key appldr until firmware 4.30.
Update to 2.2.0 bruteforce tool which adds support tool crack of klicense by MAGIC333X
Update key PS3.
No longer uses the file extension to determine whether the file is a SPRX or EXEC, use the "type" value in "ELF64 Header" instead.
Display the command line scetool used to encrypt the file.
Fixed parameter np-app-type, depending on the input file.
Update to version 0.2.9 scetool.
Using the "template" of scetool.
Integration of a ungpkg modified by myself to support and Edat sdat files when decryption of files pkg.
Use FixElf to patch instead of sys_proc_param binmay. The tool should be more effective.
Other minor changes.
Update bruteforcer with the addition of plugin testklic which is faster than scetool to check if the klicense is good.
Modification of the patcher PARAM.SFO to use another tool aldostools compatible with all PARAM.SFO (not just 3.60).
Removed unnecessary parameters scetool when the file is not npdrm.
Added a specific message when you try to decrypt a file that was not the key (3.65 +).
Added a bruteforcer of klicense v1.7.3 by aldostools to replace klicense_cracker.bat.
Fixed a bug with file extractor pkg.
Take your game or your bluray pkg.
If it is a pkg, drag the file to pkg extract_pkg.bat.
You have your folder with the game
Drag the file on PARAM.SFO patch_paramsfo.bat
Drag the file EBOOT.BIN on eboot_self_sprx_decrypter_recrypter.bat.
If it tells you: The file cannot be decrypted. Maybe it is unknown with a key, or you shoulds klicense add a key (for self / SPRX). Key Revision = [3.65] (3.65 or more), it is not worth continuing with these files, they are not decrypting.
If you see: SELF built. Data encrypted. continue thereafter.
If you see files or self SPRX, slide one on eboot_self_sprx_decrypter_recrypter.bat
If you see: "The file cannot be decrypted. Maybe it is unknown with a key, or you shoulds klicense add a key (for self / SPRX). Key Revision = [3.60 - 3.61]" You know we have the keys 3.60-3.61 and therefore it lacks the klicense file. We must try to crack the key, the next step.
(Step only if required to do) Take the file EBOOT.BIN file and your self / SRPX you have not managed to decrypt and copy both the folder or is BruteForce.exe. Start bruteForce.exe (if you get an error at launch, install it ) and click start. If you can not find the key, reduce and offset alignment and try again.
If you're lucky, you will find the key, like this: 496e66696e697479576172644b657900 (Example here with the key Modern Warfare 3).
Take the notepad and open the file and change the line eboot_self_sprx_decrypter_recrypter.bat with "set KLICENSE1 19089cbaf948487f9530832bf477b369 =" to put the key klicense found instead of 19089cbaf948487f9530832bf477b369.
For each file self / SPRX drag the game on eboot_self_sprx_decrypter_recrypter.bat. If everything is configured correctly, you should see:
If you have a game patch bluray (not PSN content), you can replace the EBOOT.BIN files, PARAM.SFO, and self / SPRX the game and start the game
Otherwise, if the game files from the PSN (PKG file), you can redo a PKG to simplify installation. Drag the folder that you extracted in step 2 to create_pkg.bat (attention, you will find yourself on the internet psn_package_npdrm.exe file to make it work). Pkg file is created and you can install it with install package file.
I thank her for Asure tool for cracking and klicense opoisso893 to change sys_proc_param aldostools and its tools.
Stay tuned for more PS3 Hacks and PS3 CFW news, follow us on Twitter and be sure to drop by the PS3 Hacks and PS3 Custom Firmware Forums for the latest PlayStation 3 scene updates and homebrew releases!
Following up on his previous revisions, today PlayStation 3 homebrew developer RazorX has updated the PS3 CFW EBOOT Resigner to version 1.07 followed by v1.08, v1.09, v1.10, v1.11, v1.12, v1.13, v1.14, v1.15, v1.16, v1.17, v1.18 and v1.19 for updating 3.55 and 3.41 CFW game files for use on 4.XX CFW.
added create pkg.
fixed a few code issues.
setup automatic contentid extraction from pkg files so it's now even easier to use this app.
added display after contentid extraction that shows you the pkgs contentid and titleid so you can make sure there correct before you try to repack pkg file.
Note: please use the exit on the app rather than hitting the [X] so it can cleanup the temp files and prevent errors.
fixed issue with unpacking pkg, patching eboot then repacking pkg in same session.
changed menu to make it easier to understand and more sensible.
updated various sections of code.
added the ability to change the param.sfo or contentid before repack incase of mismatched titleid and contentid.
removed some unneeded code and cleaned up some others.
tidied up some of the info screens to make them more clear and easy to understand.
removed timeouts to speed up the process.
fixed issue with exiting app after unpacking pkg, resigning eboot then repacking pkg.
fixed exiting app not removing some of the files.
added quick menu.
set (y) as default on eboot resigner so now you just need to hit enter or type (n) if the content id is wrong.
neatened up screens.
Version 1.10 Changelog:
Hey guys I've released v1.10 of my app this one is just a small update a few tweeks here and there i have also added FixELF for when resigning eboots to 3.60 and 4.20 you will be given the option of doing this so it's not something that will just happen so this may or may not fix any problems you may have with a resigned eboot but it's never 100% guaranteed but then what is hopefully it will help you i have also uploaded more pics for you so if your not familiar with this app you can see what it's all about.
For those of you who don't know what this is about it's all in the title of the app this is for unpacking, repacking pkg files and resigning eboots but it will also help you if all you want to do is alter a param.sfo in a pkg file or simply view the contentid of it here are some images for you.
Note: Please use the exit on the app rather than hitting the [X] so it can cleanup the temp files and prevent errors.
Version 1.11 Changelog:
updated repack pkg proccess to fix issue with packages that have large amounts of files such as PAC-MAN Championship Edition DX, now when creating a package file a new window pops up for the packing process don't close this or it will not create your package.
updated app to include more info so it's easier to understand and follow what it's doing every step of the way.
setup the app so when repacking games if it also contains the PARAM.SFO in C00 it will overwrite it with the PARAM.SFO in USRDIR after the step that allows you to alter it so if you do decide to alter the PARAM.SFO it will then be copied to C00 if it exists so you won't get a PARAM.SFO mismatch error when trying to repack the pkg file.
Version 1.12 Changelog:
added support for ps2 package files.
Version 1.13 Changelog:
updated the process for repacking ps2 package files.
added create license pkg.
removed first param editor screen since you have the option on the screen that follows it anyway.
when resigning an eboot it will automatically change the ps3 system version in the param.sfo if it exists in the root folder with the eboot.
when unpacking a mini, ps1 or ps2 game instead of having to then goto repack pkg it will do it automatically after you have unpacked it.
setup automatic retrieval of the title id from the content id itself so if the title id is wrong or you are doing a ps1 game were the title id is always different and prevents you from repacking it will automatically replace it for you so by the time you get to the info screen that tells you the games content id and title id for you to check it will have been changed to match the content id.
Version 1.16 Changelog:
fixed issues with gamedata.
fixed issues with dlc.
separated gamedata & dlc to separate options.
cleaned up some code.
Version 1.17 Changelog:
increased eboot compatibility, when booting app it will create a ps3 folder if you have your act.dat and idps or idps.bin simply copy them into this folder the folder will not be deleted on exiting.
added extras menu.
added the ability to convert ps2 isos or bins to ISO.BIN.ENC.
added the ability to create a ps2 classic pkgs from the newly created ISO.BIN.ENC this will create pkg files you can install on your ps3 at the same time not 1 pkg that will overwrite.
Version 1.18 Changelog:
updated PS2 classics code.
creates "custom" folder before making PKG for you to add ICON0.PNG, PIC0.PNG, PIC1.PNG and PIC2.PNG images if you want to customize your PS2 games.
speeded up the process of making PS2 classics.
added more info to screens so its easier to follow whats happening when making a PS2 classic.
Note: to better ensure your game will work have your ps2 game in iso format as ISO9660 MODE1/2048.
Version 1.19 Changelog:
updated PS2 classics code some more.
[Q] i really dont understand how to unpack a pkg
[A] all you do is put your pkg file in the same folder as my app then goto option 6 and then option 1 to unpack the pkg
[Q] how do you get content id?
[A] if the pkg file is a game/homebrew pkg file it will get it automatically and say is this your content id then you say yes but for the others you will have to enter it manually as far as getting that in the next version i will release tomorrow i will include an option in the package menu to boot up an app from aldostools that will tell you it then you just copy and paste it
[Q] how do you get package version?
[A] the package version is contained in the param.sfo but for the most part its 01.00 and even if its not and you set it to 01.00 nothing bad will happen it wont make any difference to the app
[Q] why there is a difference between ps1 games, homebrew, and data packages? how do i know what kind of package is mine?
[A] there is a difference because each package tells the ps3 what it is and how to deal with it and stuff as far as telling if you dont know what you pkg is then its probably not worth messing around with it till you learn more about pkgs and there functions etc