Join Us and become a Member for a Verified Badge to access private areas with the latest PS4 PKGs.
PS4 CFW and Hacks       Thread starter PSXHAX       Start date Jul 22, 2020 at 8:43 AM       290      
Status
Not open for further replies.
Proceeding the 7.02 PS4 KEX, 6.72 PS4 Webkit Port, 6.72 PS4 Payloads and the 6.72 PS4JB Exploit today PlayStation 4 developer @MODDEDWARFARE returns via Twitter with PS4 Backporter v1.4 tool for backporting 6.72 to 5.05 FPKG Games alongside a new demo video below from his YouTube Channel and more updates! šŸ˜

Download: PS4 Backporter v1.4.zip (76.5 MB)

Spoiler: Depreciated

This comes following the PS4 6.72 to 5.05 Backporting Tutorial, SELFUtil by Znullptr, PS4 RiPKiT/Modding/Cheat/BackPort Tool and EZ PS4 Downporter utility for backporting 6.72 games to run on 5.05 Firmware with a Jailbroken console.

Here are some PS4 Backporter v1.0.exe notes from his Tweets below:
  • Still very much work in progress and has a few bugs. Will release a new version later. A known bug right now is that you can't set the output path to the root of the drive. If you do it wont save the final pkg file.

  • Also won't work with EA titles right now. Due to all the extra patching that's needed to get those games working.

  • Drag pkg file into "input pkg file". Click the button.
And from the Readme.txt: PS4 Backport Tool By Modded_Warfare

This tool includes and makes use of:
You must have installed:
These are required for the tool to work correctly ^^^
Installers are included in this zip file.

Backporting Tool
Backport 6.72 PS4 Games to 5.05 (Easy Method)
PS4 Backporter v1.0 for 6.72 to 5.05 FPKG Games by MODDED WARFARE.jpg
 

Comments

@Baku86
I understand what you are saying, but I think the approach to install game pkg, then update, then small fix is not valid. Small fix will overwrite update.

Patches are not incremental on PS4, in should contain all content from the previous patches as well, they work like an additional layer on top of the base game. To back this up look at patch history of CUSA03041 for example, sizes of patches, they keep getting bigger and bigger, so that next one contains all the files from the previous with some overwrites and extra additions: CUSA03041

So the correct way:
1. Install base game pkg
2. Install patch that contains all update files and needed files are backported

@MODDEDWARFARE
Due to my explanations above I think you should allow only "Backport Whole Pkg" in case of game patches. Small backport patch will overwrite the actual update so some files will be missing.
P.S. Thanks for your work, great tool.
 
So Variante 2 doesn't work (for me)

1.RDR2 Base.pkg
2.Backport Patch from Base.pkg

This will work

But if you install update 1.13 and the Backport Patch from this Update
Game Start but its come an error blue screen

NFS Heat can't save Game...
 
@kylum Thanks for this information, but how do you know that the game is really in v1.13 in-game?

For example, for Marvel's Spider-Man I can tell with the Photo Mode in-game (which was added as part of the update v1.17)
 
Can anyone tell me, windows 7\64 do everything according to the instructions, starts working and writes - An error while patching .sfo file see log for detalis
 
@Elenium, Modded WARFARE clearly said, that (game, update, backoprted patch for update) is the right way. So do you think, that he is wrong and we always have to backoprt whole pkg and small updates are in fact useless updates? So why those small updates works for base game?
 
Elenium is right, the small backport patch only works on base game. When there is an update involved, the only thing you can do is backporting the whole update file.
 
Status
Not open for further replies.
Back
Top