Search results

The arcade pkgs can now be decrypted, thanks to SSL and zecoxao. For this to work, you'll need to compile the fail0verflow tools (https://github.com/darkuncle/fail0verflow) with the . Then you can use the tool: ungpkg [--arcade] filename.pkg [target]

No problem, I've reversed how the update works: Either the game copies the game specific update data to /dev_hdd0/game/SCEEXE000/ARCDIR/INSTALLX.PKG (variable X) and resets the PS3 into update mode or the PS3 copies the data from /dev_usb000/game/SCEEXE000/ARCDIR/INSTALLX.PKG and then installs...

Thanks, that's interesting. The installation process is game specific. If you have the game, can you confirm if it follows the same naming convention for executable files like earlier titles: BOOT.SELF BOOT_XXX.SELF EBOOT.BIN GAME_XXX.SELF TEST_XXX.SELF TESTLIVE_XXX.SELF VERUD_XXX.SELF...

I didn't have time to check my assumptions yet, but did you try to install these *.BIN files on a arcade PS3 by renaming them to *.PKG and using the XMB option? This would ensure that these PKG files are not specially made for that game.

Hello, thanks for the files, I did some analysis on them. These files are "debug" pkgs which can be created using the make_package_npdrm tool and mostly comply with the standard. But there's one thing that's different: The key generation. The content of these pkgs is (like the retail...

That's weird. The official Sony tools supports debug packages and most of the scene based tools support retail packages. So either one of them should work except if the PKG type is somewhat special. The executable files (.self) inside the PKG are special, they're also marked as debug SELFs but...

Hello, did you try to use the official Sony tool for this? (make_package_npdrm -x)