[$n!pR]

PS3HaX member $n!pR has updated his PKG Toolkit G... [Read More]

[Tcraw77813]

I'm glad to see all the great apps and appreciate the time you took to make this, but do we really need yet another signing tool. I mean everyone and their mother has now made one. Is there anything that sets this apart from other signing applications.

[2die4]

thanks man let me get this straight if i make the eboot.bin into a eboot.self i can use this app to sign it and turn it into a pkg right

[GregoryRasputin]

Awesome work $n!pR, front paged, thanks

[$n!pR]

Originally Posted by Tcraw77813 I'm glad to see all the great apps and appreciate the time you took to make this, but do we really need yet another signing tool. I mean everyone and their mother has now made one. Is there anything that sets this apart from other signing applications.

The other one's don't create the PKG file

Originally Posted by 2die4 thanks man let me get this straight if i make the eboot.bin into a eboot.self i can use this app to sign it and turn it into a pkg right

No, you create a self file or eboot.bin from an elf file.

[kenshindono]

you should do a version change and explain the feature :D
That way you will not get any weird question
That's an incredible work :D

It could be improved enough to decryt or sign eboot
Good job :D

[lisapower]

Gracias!

i don't have the knowledge to work with all of this Dev Tools, but i really appreciate all you do for the PS3 Scene!

Aighhhhhht!

[SaveU]

Originally Posted by 2die4 thanks man let me get this straight if i make the eboot.bin into a eboot.self i can use this app to sign it and turn it into a pkg right

Kind of.

You mean make an eboot.bin into and eboot.elf (an eboot.bin is a self )

But yes, this tool is great. Saves some command line stuff. All we need to do now is edit our elf, sfo, and gather stuff together.

Great job. This tool will be great when all the other funcitons are entered.
************* [ - Post Merged - ] *************
Just another question, how would one update the keys in this, or will you give new releases if updated keys are needed.

Does this have all the keys so far included?

[2die4]

ok i know how to turn an eboot.bin into an eboot.elf what do i do next then to sign it into a eboot.bin how to i repackage it can i use cygwin or do i have to use something else ???

[kenshindono]

before anyone ask weird question here is the readme

How to use Step 1 Signing Elf: 1. Select elf to sign. 2. Select output self (EBOOT.BIN). 3. Enter Content ID (see example). 4. Click Build. Example: Content ID - UP0001-XXXXYYYYY_00-0000111122223333 Change XXXX and YYYYY to Title ID of homebrew (Game ID's look like this - BLUS 12345). If you get an error make sure selected elf is in the right format! - That is, it is actually an elf and not a self. - Content ID should be the same as the one used when creating the elf. - Make sure the file isn't corrupted. Step 2 Creating PKG: 1. Use the sample folder as a reference (ABCD12345). - Rename folder using the same Title ID of homebrew, follow guide above (XXXXYYYYY). 2. Place the EBOOT.BIN created in step 1 into USRDIR. 3. Place all other files into the main PKG directory (should be the folder created in step 2.1). - Files can include ICON0.PNG, ICON1.PAM, PIC1.PNG, SND0.AT3 etc. 4. Edit PARAM.SFO in same directory with Title ID, Title, App Version, Data Type etc. of homebrew. 5. Edit or create a new package.conf following the sample file provided. - You can rename it the same as the Title ID of homebrew. 6. Select input folder created in previous steps (ie.ABCD12345/XXXXYYYYY). 7. Select the config file created in step 5. 8. Make sure the Content ID under Build PKG matches the one set in your package.conf file. - The Content ID should also match that of the one entered in Step 1. 9. Click Build. Thanks to geohot and Fail0verflow for the tools.

That would be great to add the source :D