[beketata]

Obfuscation is very timely , but what did you mean by: FileSystem.Kill("test_out");

************** Exception Text ************** System.IO.FileNotFoundException: No files found matching 'test_out'. at Microsoft.VisualBasic.FileSystem.Kill(String PathName) at PKG_Toolkit.Main.8AAAA(Object ᙂ, EventArgs 1AAAA) at System.Windows.Forms.Control.OnClick(EventArgs e) at System.Windows.Forms.Button.OnClick(EventArgs e) at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent) at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks) at System.Windows.Forms.Control.WndProc(Message& m) at System.Windows.Forms.ButtonBase.WndProc(Message& m) at System.Windows.Forms.Button.WndProc(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m) at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m) at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

[$n!pR]

lol. psn_package_npdrm.exe creates that file, so I do some cleanup after the program ends.

As for my program, I've made it so it automatically reads the second content id from the config file. Will update the links later.

EDIT: Download now online. Did a massive overhaul of the error handling.

[$n!pR]

Updated the tool to work with scetools. Please test and report back. I removed the old tools so if scetools doesn't work with older firmware I might add them back.

Edit: Made some slight changes. If you downloaded it, download again. If it gives an error installing on 3.55 run finalize_package from previous version.

[GOD_666]

AWSOME work much appreciated @$n!pR worked great with a psn game (Homefront) extracted the fix pkg for the game which was meant for 3.55 fixed the eboot and repackaged to work on 4.30 EASY tool

Thanks

[GregoryRasputin]

Originally Posted by $n!pR Updated the tool to work with scetools. Please test and report back. I removed the old tools so if scetools doesn't work with older firmware I might add them back. Edit: Made some slight changes. If you downloaded it, download again. If it gives an error installing on 3.55 run finalize_package from previous version.

Nice to see someone update one of their old applications, if only more people would do that.

Thank you

[sandungas]

Thx, i love the simplicity of the interface

If you admit suggerences... there is only one thing left (unpackage) to be able to:
unpackage--> unself --> reself ---> repackage
If you find a way to generate the config file automatically when unpackaging (based in the info of the original .pkg)... all the process can be automatized

Also, i think you can sign the files with the most older keyset (are not blacklisted so all keysets are valid)... and using the 4.21 format
This reduces the signing to only 1 type that includes all firmwares (CEX)
Other thoughts... you can add "fself" (for DEX)

[$n!pR]

Originally Posted by sandungas Thx, i love the simplicity of the interface If you admit suggerences... there is only one thing left (unpackage) to be able to: unpackage--> unself --> reself ---> repackage If you find a way to generate the config file automatically when unpackaging (based in the info of the original .pkg)... all the process can be automatized

Will look into that

Originally Posted by sandungas Also, i think you can sign the files with the most older keyset (are not blacklisted so all keysets are valid)... and using the 4.21 format This reduces the signing to only 1 type that includes all firmwares (CEX) Other thoughts... you can add "fself" (for DEX)

Do you mean when signing for firmware 3.60+? When the option 4.21/4.30 is checked it signs it using the 3.60 key revision. You can verify this if you look at the log by decrypting the file again.

[sandungas]

Originally Posted by $n!pR Do you mean when signing for firmware 3.60+? When the option 4.21/4.30 is checked it signs it using the 3.60 key revision. You can verify this if you look at the log by decrypting the file again.

No, i mean... when signing homebrew for 4.30+... you can use any of the keysets (all are valid)
Look at this table, the first line (0x00 revision used in 0.80 firmware)
http://www.ps3devwiki.com/wiki/Keys#Appldr
A homebrew signed with this key will work in all CEX firmwares (included ofw's and cfw's from 0.80 upto 4.30+ and all future ones)
The explain is simple... is because this key has not been revoked, official stuff (games or apps) signed with this key (back in 2005) are valid in 4.30 and all future firmwares of course

This reduces your actual version of the app to only 1 type of signing (in the options at the bottom)... you can replace all by "signing for CEX"
If you add the "fakeself" signing you can add another option... "signing for DEX"





Edit about npdrm specific keys:
The only keys that has been revoked in this list are the ones colored in grey (for npdrm)
The older npdrm key is "0x00 np" (line 4 of the table colored in grey) was introduced in 0.92 firmware and revoked in 3.30... this means we cant use it as a "legacy" key, doesnt works over 3.30
So for npdrm the older one working is "0x01 np" (introduced in 1.00 firmware and still valid up to 4.30+)

[soneco]

thanks 100% funcional!!!

[$n!pR]

Do you know of any commandline tool to unpack pkg files? All I found was AllUnpkg but it only does retail PS3/PSP pkgs. I currently have it implemented but have a couple of bugs, one of which you can't unpack homebrew signed with debug. If you ran the finalize tool on a homebrew debug pkg however you could unpack it...

EDIT:
Update Nov 8/2012.
Added the option for debug/retail and added AllUnpkg.



Download is now up.