Join Us and become a Member for a Verified Badge to access private areas with the latest PS4 PKGs.
Today I (@CyB1K on Github or Cyberpt1000 on Twitter) present PS4 Fake PKG Tools 3.87 including Fake PKG Generator for PS4 Version 3.87 (Build 3.87.7549.35163) Patched for PS4 FPKGs with a Custom PKG Key, Fake SELF Support and Online Checks Patched followed by some updates for Keystones, the fixed PS4 Fake PKG Tools 3.87 (V4 Patched), PS4 Fake PKG Tools 3.87 V5 and latest PS4 Fake PKG Tools 3.87 V6. :)

Download: PS4_Fake_PKG_Tools_3.87_V6.rar (6.36 MB - includes gengp4_app.exe, gengp4_patch.exe, orbis-pub-chk.exe, orbis-pub-cmd.exe, orbis-pub-gen.exe, orbis-pub-prx.dll, orbis-pub-sfo.exe, orbis-pub-trp.exe, di.exe, libatrac9.dll, sc.exe and pkg.exe) / GIT / Temp-Folder-Patcher.bat

Spoiler: Depreciated

For those who enjoy my PS4 Game Backports and related work, I have a PayPal Page set up for donations to help with disk and storage costs. <3

:note: Brief background: Many in the PlayStation 4 Scene sought to replace the outdated Fake PKG Generator v3.38 for generating PS4 FPKGs with an updated version, however, Fake PKG Generator for PS4 Version 3.70 (Build 3.70.7110.1152) was never released due to LM-based drama over DMs while the orbis-pub-prx.dll offsets of PS4_Fake_PKG_Tools_v3.87.rar from the PS4 DevKit Leak this summer weren't patched for use with PS4 Fake PKGs... until now!

And from my PS4 Fake PKG Tools 3.87 (Patched) Release Post:

I patched the latest 3.87 tools. Both pub gen and cmd works, I also patched the check on download data size that was required to backport apps. SELFs are also patched to work ofc (slowly I'm learning assembly and its exciting :D)

For now I will keep doing my best to try to find a way to patch it to use original keystones directly :)
Code:
_________        __________  ____ ____  __
\_   ___ \___ __ \______   \/_   |    |/ _|
/    \  \<   |  | |    |  _/ |   |      <
\     \___\___  | |    |   \ |   |    |  \
 \______  / ____| |______  / |___|____|__ \
        \/\/             \/              \/
From the README.md: PS4-Fake-PKG-Tools-3.87

Patched 3.87 Tools

V4 (All working now... maybeeee? ^-^"):


Patched sc.exe which wasnt patched and so games wouldnt work, big thanks to TheRadziu and my partner Arczi for the help!

Other fixes applied here and there, thanks to my friend Opoisso for the help! Thanks to Arczi for testing it all with me!

Let me know if you find anything else broken and ill fix (Forgive me for i am a mess with focusing on loads of files with same names) :D

Added a version of 3.87 to be used with PSX-FPKG and PS2-FPKG To PS4 PKG builders if you want. I didn't do much testing to that, tested obscure with jak2 emulator and it was working.

You need to always make sure your app/base files has a keystone on "sce_sys\keystone" before building a base pkg as it will build it without a keystone inside otherwise, which would cause the game to not work or save!

Use the gengp4's accordingly to make sure apps/bases are built with a keystone and avoid accidentally building patches/updates with keystones, which can happen if for example you move files from base's sce_sys into a patch sce_sys folder.

DONT use the old versions, as they wont work! Sorry!

V3 (Original keystone patch / No more fake file):

So i managed to reverse LMAN's legendary loader and managed to patch the keystone correctly now, it will no longer create a fake file inside and pkg will contain only the original keystone!

You need to always make sure your app/base files has a keystone on "sce_sys\keystone" before using these to build a pkg as it will not build a pkg with a keystone inside otherwise, which would cause the game to not work or save!

Use the gengp4's accordingly to make sure apps/bases are built with a keystone and avoid accidentally building patches/updates with keystones, which can happen if for example you move files from base's sce_sys into a patch sce_sys folder.

V2 (Original keystone patch):

This version uses a patched rename of keystone in the tools, so you can now build base games with original keystone directly from the tools without the need for a loader or gui.

The downside, you need to always make sure your app/base files has a keystone on "sce_sys\keystone" before using these to build a pkg as it will not build a pkg with a working keystone otherwise, which would cause the game to not work or save!

Pkgs will be created with a file named "fakekeys" which is the renamed generated fake keystone.

Use the gengp4's accordingly to make sure apps/bases are built with a keystone and avoid accidentally building patches/updates with keystones, which can happen if for example you move files from base's sce_sys into a patch sce_sys folder.

Instructions to build pkgs properly

Extracted Game (For repacks, ignore this one if its a dump):

  1. Extract all files from base or update.
  2. After extracting rename the folder from Image0 to CUSAXXXXX-app or CUSAXXXXX-patch, accordingly.
  3. Move the files from the folder "Sc0" to "CUSAXXXXX-app\sce_sys" or "CUSAXXXXX-patch\sce_sys" and delete the "Sc0" folder after.
  4. Continue the instructions the same as a dump.
Dumped Base Game:
  1. Generate gp4 project file with geng4_app.exe from CUSAXXXXX-app of your dump and save it.
  2. Open in orbis-pub-gen.exe that saved *.gp4 file and build pkg.
Dumped Update Game:
  1. Generate gp4 project file with geng4_patch.exe from CUSAXXXXX-patch of your dump and save it.
  2. Open in orbis-pub-gen.exe that saved *.gp4 file.
  3. Make sure that you have selected base game pkg in Command > Project Settings > Patch Tab > "Application Package" field.
  4. Build pkg.
Always make a copy of "param.sfo" from "sce_sys" to somewhere else before generating a gp4 as it can change and corrupt the param if the folders are not properly named.

If you are repacking a game made with this tools, you first need to delete the file "fakekeys" from sce_sys before creating a gp4 or it will fail and error when building the pkg!

XXXXX - Stands for the CUSA of the game you are packing.

Credits to flat_z, cfwprophet, SocraticBliss, TheRadziu and everyone else who worked on earlier tools patches!

Credits to LMAN for his patched gengp4 :)

Credits to Arczi for the help!

Enjoy

By CyB1K
PS4 Fake PKG Tools with Fake PKG Generator 3.87 Patched for FPKGs by CyB1K.png
 

Comments

If it says it cant access C either your windows has admin permission writting to C locked up or you ran out of space in your C temporary folder
 
@jwooh yes I selected the base PKG game I gets to about 85% then fails as I can't write to C\user ect

@CyB1K I will have a look at that today. Thanks to everyone who took the time to respond to my issues. (y)

here is the error log:
Code:
[Debug]    2022-07-21 11:09:48 Create image Process started.
[Debug]    nptitle.dat: NP Title file.
[Debug]    Custom patches thanks to flat_z and cfwprophet!   
[Warn]    Patched By CyB1K! Credits to SocraticBliss and TheRadziu
[Warn]    *** Version 05.050
[Debug]    Custom patches thanks to flat_z and cfwprophet!   
[Warn]    Patched By CyB1K! Credits to SocraticBliss and TheRadziu
[Warn]    Publishing Tools Version 3.87
[Debug]    icon0.png: 512x512/24bit.
[Debug]    pic0.png: 1920x1080/24bit.
[Debug]    pic1.png: 1920x1080/24bit.
[Debug]    (app) chunks=1, mchunks=1, scenarios=1, default_scenario=#0
[Debug]    (patch) chunks=1, mchunks=1, scenarios=1, default_scenario=#0
[Debug]    Scenario #0 Language Group #0 (patch): Initial Payload = 94MiB
[Debug]    Writing internal image.
[Debug]    Writing internal image.
[Debug]    Calculating image digest.
[Debug]    Check Integrity started.
[Error]    Format of the package file is not valid. (UP0700-CUSA28863_00-ELDENRING0000000-A0100-V0100-CyB1K.pkg, pfs extra digests mismatch)
[Debug]    Check Integrity ended.
[Error]    Could not create temp file. (C:\Users\john\AppData\Local\Temp\ps4pub\build00001cdc9cd2d067\ap.pi)
[Error]    2022-07-21 11:11:13 Create image Process finished with error(s).
I have changed permissions from %appdata% to C:\Temp still the same

Update: I’ve still not gave up on this error I have tried multiple things with no luck can any help. Thanks
 
you can get passcode only if devs forgot to remove it from ini file in already dumped by someone game, there is no other way or at least i never heard of it
 
@u53r or by a dev leaking it like the Unreal Password that works for games like tetris effect. I tried it on the latest update and they are still using the same key.
 
Version 5 is broken. Everytime I build a .gp4 file using the patch application... It resets my param.sfo back to a game application.

I've wasted countless hours with these tools people are coding today. How hard is it to code a c# application that works?
 
Back
Top