I'm having a go at using Toolkit GUI by $n!pR but for some reason i'm getting two eboot files built into my pkg
Entry list: [11 entries]
raw data: PARAM.SFO
raw data: ICON0.PNG
raw data: ICON1.PAM
raw data: PIC1.PNG
raw data: SND0.AT3
raw data: USRDIR/EBOOT.BIN
raw data: USRDIR/eboot.bin
raw data: TROPDIR/NPWR00772_00/TROPHY.TRP
also at the top of the info window i'm seeing PARAM.SFO: overwrite VERSION to 01.00. (from 01.01) but the sfo & config file read 01.00
I'm getting this at the end. Notice: raw data is NOT protected by DRM. please use NPDRM EDATA if you need to protect. it pkgs just fine but when i go install it, it errors.
I keep getting this error "Unable to build pkg file - The PARAM.SFO is from another game."
no matter what I do! The .sfo is from the move edition of resident evil. I lets me use the eboot from the move update an all the other files but it refuses to build the package because of the sfo? Come to think of it is there a pkg for resident evil 5 move edition for 3.55?
Did you take a look on the name, the game ID?
New version $n!pR PKG Toolkit GUI 1.03
1. Fixed a bug that prevented EBOOT from being signed properly.
- EBOOT.BIN is case sensitive!
2. Added option for creating 3.41 or 3.55 package files.
3. Added UnSELF tool.
The first public release had a bug, the newest version is much better.
i get this when trying to sign the mw2 pkg all i did was replace the patch_mp.ff with a modded one but it wont let me sign it and compress it and i didnt touch the param.sfo at all... ''/
[PARAM.SFO Check]: APP_VER entry cannot be included for GameData.
Illegal Package: PARAM.SFO check fail.
Did you check to make sure the vers. number in PARAM.SFO and your config file are the same?
So... are these still all signed by these tools using the known key inserted by geohot that can be easily be flagged, or are these all different so that Sony cannot easily blacklist them?