Join Us and become a Member for a Verified Badge to access private areas with the latest PS4 PKGs.
Status
Not open for further replies.
The latest entry to the world of PS4 Backporting comes from developer @RetroGamer74 of RetroGamer Live following his Kill'em All 1.00 PS4 PKG Homebrew Game release via Twitter dubbed AutoBackPort tool for backporting 6.72 to 5.05 game PS4 FPKGs to play on a PS4 Jailbroken Console! :fire:

Download: AutoBackPort_1.11.rar (17.5 MB - includes AutoBackPort.exe)

Spoiler: Depreciated

This follows yesterday's PS4 Backporter v1.1 update and the previously released SELFUtil by Znullptr, PS4 RiPKiT/Modding/Cheat/BackPort Tool and EZ PS4 Downporter tool for Windows.

Here's a brief outline of the instructions from his Tweets below:

1. Select the Dumped 6.72 PKG
2. Select a temp folder for several files extraction
3. Select a folder to build the PKG fix
4. Press button

v0.35 Changelog:

Fixes:

  • Check target folders. Remember to use a different folder for each option. Do not use the ROOT folder.
  • Check when copying param.sfo.final file
v0.5 Changelog:
  • Performance improvements.
  • Folders clean when process finishes.
  • Popup showing folder containing final pkg at the end.
  • Other fixes reported.
v0.6 Changelog:
  • Performance Improvements in extraction procedure.
  • Performance Improvements in decrypt and downgrade.
  • Several fixes.
  • Fix to clean completely folders at the end.
v0.7 Changelog:
  • Fixed an issue that was building updates with the Damage Data message in PS4. i.e.: Update 1.51 for Days Gone is successfully built.
v0.8 Changelog:
  • Faster file processing
  • Fixed issue when PKG is missing at the end PKG built result monitored.
  • If error there will be a log.
  • Reduce height window size for ppl with low resolutions.
  • Better folders clean than before
v0.85 Changelog:
  • Fix index out of bounds error included in 0.8 by mistake
  • Fix CE-40745-5 Error
  • EA Patch games special implementation
  • Other incompatibility issues for ppl using Windows 7/8
v0.86 Changelog:
  • Fixed and issue that could make lost a file in the PKG.
Those interested can give it a try and as always feel free to share your results in the comments! (y)

v1.00 Changelog:
  • Faster than ever before
  • New progress bar for PKG Building process
  • Faster PKG creation without Delta
  • Just one folder as destination
  • Autosave & Autoload the last folder used
v1.01 Changelog:
  • Fixed an issue when trying to rebuild the same project two times.
  • Added a group of expert features
  • Expert feature for pausing the process just before the PKG build for adding, replacing, or removing files
v1.02 Changelog:
  • Fix small issue when building update with EA Patch checked
  • Pause check button moved to the right
v1.03 Changelog:
  • Fixed an issue that could extract unnecessary files
  • Added new feature to check if you're using the latest release
v1.04 Changelog:
  • Fixed an issue in the progress bar limit reported by several users.
  • Fixed an issue when moving the final package when repeating the procedure several times
  • Added a file counter in the extraction progress
  • Fixed an issue in expert mode.
v1.05 Changelog:
  • New feature to auto fix NP-32046-5 error
  • AutoBackPort will detect encrypted trophy files and will show you the procedure to fix it.
  • As much automatic as can be.
v1.06 Changelog:
  • Issue CE-40740-5 fixed. (I hope) :) This issue happened when decrypting files if destination folder contained blank spaces.
v1.07 Changelog:
  • Finally we got it. The full fix for the issue CE- 40740-5. Thanks everybody for the feedbacks. A missing line :)
Spoiler: Related Tweets


AutoBackPort 0.7 Successful Days Gone 1.51 Update Built.
EA Patch for PS4 Backups. AutoBackPort by RetroGamer_74
PS4 Hack - Do not use small size backport fix for updates. Why?
AutoBackPort 1.00
AutoBackPort 1.05 NP-32046-5 Built-in error fixer
AutoBackPort 0.3 Tool for Backporting 6.72 to 5.05 PS4 FPKGs by RetroGamer74.jpg
 

Comments

what about to create only a backport patch. I mean, no base game, and no update. Just backport patch, the good way to keep 6.72 backups pure for the future.
 
Remember adding PKG Game and adding and Update, don't do a mix of both things.
So Install your dumped game into the PS4.
Create a fix for the base game.
Install the fix for the base game into the PS4.

Again in AutoBackPort, add the PKG Game, and add the Update PKG.
Create a fixed update. In this case is the 1.03 update backported and fixed.
Install the fixed update.

That's the right path.

This has to be done in this way because the Base Game could have files not modified by the update that, anyway, needs to be fixed.

So by the way, this is not a mixed result. It is just a fix for Base Game, and if you add the update, a fixed for the update.
 
@RetroGamer74 if we have game and update 1.03 do we need create fix for game and for update (2 fixes as result) or just one fix for the update (which is mix of ported base game and update files)?

And install:
1. Main game
2. Update
3. Fix based on update and main game

Correct?
 
It works 100%. Several proven positions launched at 5.07 work smoothly. The time to create the package itself takes a while, but it's worth the wait.

@RetroGamer74 - I noticed there is a problem (and you wrote about it) with relocating the working pkg in separate folders and in the main folder. I have a small suggestion - in a future release, are you assuming the option of folders in the bundle of programs (e.g. input, work, exit) with default paths in the application? I know it's cosmetic, but maybe it will make life easier for some users.

Thanks for your work and brilliant program! BiG BEER!

@trutadolago = yes - with full working pkg "patch" to 5.05/5.07 release firmware.
 
1. Install main game.
2. AutoBackPort. Create fix for the game and Install it.
3. AutoBackPort. Create fixed update using the Dumped PKG Game and Dumped Update.
4. Install the new fixed update package created by AutoBackPort.

I guess the problem here is most of you are thinking that using the Dumped Game PKG with the Dumped Update PKG means a Resultant PKG with both of them. And that's not real. FakePkg Tools requires the Dumped Game Base as reference when you want to create the modifications for the Update Package.

So each step.

First step just fill the Game Base Location and get a fix for the game.
Second step fill Game Base and Update to build the full Update with the fixed files.
Then you install this update created by AutoBackPort. Not the dumped update, and then the fix for the update.

@logibeareu If you use my latest release, it should warn you when you select wrong paths. Anyway I'm currently focused in functionality. As soon everything is working well, we improve the look & feel, settings, and user friendly.
 
Wait I don't understand. I have to dump game again from my PS4 after instaling it? Or by dumped you mean downloaded/dumped pkg (like duplex scene release) and i always use those for install and making backported fixes?

PS. I don't install dumped update at all - just fixed update, right?
 
@RetroGamer74 - yeah I know it warning :)

I made the three folders I wrote about (I am a mess - prevention :)). In RC 0.3 there were messages about "lost sfo file" - since he works with files in this hierarchy, no error message appears, and files that previously generated this error are processed (successfully). So I don't really know where the cause of success or failure lies.
 
Status
Not open for further replies.
Back
Top