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

For those games you own a last update dumped, I'm testing that it looks just creating the Update Fixed should be enough and may not require the first base game fix. But I guess if the update wouldn't modify all required files existing in the base game could exists several libraries left not modified and may cause error.

But if you own the update you can try first with the update fixed package, and see if everything works.
 
Let's say I have Red Dead Redemption 2 + update 1.13, what steps do exactly I have to do to backport both the base game and the update? Sorry I'm a bit confused
 
@mehdialonso
Since the tool doesn't allow to backport only the update I think you can try backporting the game and the update v1.13 , after it's done you'll have the fix for the game + update fix for v1.13 , try install the base game (not the fix) and then install the fix update v1.13 and see if it works
 
i tried rdr2 before... game worked after backport with this app. unfortunately update 1.13 didn't work. resulted in corrupted game when trying to start. anyone had any luck with this app working for updates?
 
@ody1977 I did several updates fixed with AutoBackPort, for example 1.04 Resident Evil 2 Remake, and it worked. But that was not the case with CONTROL.

So as a reminder, if the developer has implemented any new feature available in firmwares above 5.05 it could be impossible to make a complete backport.

Cheers.
 
I am receiving this error when backporting RDR 2.
Code:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.

************** Exception Text **************
System.IO.IOException: Cannot create a file when that file already exists.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
at System.IO.Directory.InternalMove(String sourceDirName, String destDirName, Boolean checkHost)
at System.IO.Directory.Move(String sourceDirName, String destDirName)
at AutoBackPort.Form1.SetCusaFixFolder()
at AutoBackPort.Form1.Button3_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)


************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1055.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
----------------------------------------
AutoBackPort
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///D:/AutoBackport/AutoBackPort.exe
----------------------------------------
Microsoft.VisualBasic
Assembly Version: 10.0.0.0
Win32 Version: 12.0.20806.33440 built by: FX45W81RTMREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Microsoft.VisualBasic/v4.0_10.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualBasic.dll
----------------------------------------
System
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1055.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
----------------------------------------
System.Core
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1055.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Core/v4.0_4.0.0.0__b77a5c561934e089/System.Core.dll
----------------------------------------
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1055.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
----------------------------------------
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1055.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
----------------------------------------
System.Runtime.Remoting
Assembly Version: 4.0.0.0
Win32 Version: 4.6.1055.0 built by: NETFXREL2
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Runtime.Remoting/v4.0_4.0.0.0__b77a5c561934e089/System.Runtime.Remoting.dll
----------------------------------------

************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.

For example:

<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>

When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
 
I used the new version with Shenmue 1 and this time it worked and the base game fix worked. however, when i after that install the fixed update i get a "the game is corrupted" error. :(
 
Status
Not open for further replies.
Back
Top