PS3 [Update] Apollo Save Tool v1.0.2 released

Discussion in 'PS3 Homebrew' started by bucanero, Feb 7, 2020.

By bucanero on Feb 7, 2020 at 2:49 PM
  1. 468

    bucanero Developer

    Jun 29, 2019
    Likes Received:
    Trophy Points:
    Home Page:
    Update v1.0.2 Released
    Original Introduction: PS3 development has been seeing an upkick lately and developer @bucanero has been one of the developer playing a part. The developer has recently updated Artemis with new support and also released PKGi (PS3) but now the developer shares a great utility that involves PS3 Game Saves called Apollo, built utilizing the Artemis GUI this homebrew capable of running on CFW and PS3HEN will allow you to Patch & Resign your Game Saves / Download Game Saves / Unlock Game Saves all from the convenience of your PS3 console and not PC tools are required. Below you can see the release thread from the developer himself: So i'll let @bucanero take it from here with another great release:

    It's summer and you're bored; what do you do with that amount of free time? You make "Apollo", a new homebrew app for the PS3! :D

    • you might wonder... why is it called Apollo?
      Apollo was the twin brother of Artemis, goddess of the hunt. Since this project was born using the Artemis-GUI codebase, I decided to respect that heritage by calling it Apollo.

      So, without further ado, let's present Apollo:

      Apollo Save Tool is an application to manage save-game files on the PlayStation 3.
      The apollo-ps3 homebrew app allows to download, unlock, patch and resign save-game files directly on your PS3.

      • Easy to use: no crypto-key configuration or advanced setup needed.
      • Standalone: no computer required, everything happens on the PS3.
      • Save files listing: quick access to all the save files on USB and the internal PS3 HDD (+ file details)
      • Save SFO unlocking: allows the user to remove the copy-lock flag, enabling transfer of Copying Prohibited save files.
      • Save files patching: supports Bruteforce Save Data and Game Genie cheat patches to enhance your save-games.
      • Save PFD resigning: allows the user to resign save files made by other users and consoles.
      • Save downloading: access to an Online Database of save-game files to download straight to your PlayStation.
      • Automatic settings: auto-detection of PSID and Account-ID settings.

    • v1.0.9

      • Support for compressed save-game file patching
      • Added insert, delete, compress, and decompress BSD patch commands
      • Improved save list browsing
      • Improved BSD patch code parsing
      • Reduced package installer size



      • Re-added resign/cheat options to HDD/USB
      • Added decrypt file option
      • Updated UI with custom font


      • Fixed game listing issue (when name has a \n)
      • Fixed custom CRC calculation bug (BSD patches)



      • Bruteforce Save Data cheat patch support
      • Changed save-game encryption/decryption method
      • Splash screen logo



      • Game Genie cheat patch support
      • Updated UI
      • Added Remove Console ID patch
      • Added Licenses backup to .Zip (/dev_hdd0/home/000000XX/exdata/)
      • Added bulk save-game copy to USB
      • Added Trophies backup to USB
      • Added owner.txt support to override auto-detected settings
      • Improved auto-update check/download

      • Solved issue when copying save-games from HDD to USB
      • Solved freeze bug when using Clear local cache
      • UI: Fixed improper titles and messages


      • Export save-game to .Zip file
      • Copy save-game to USB
      • New Settings option to clear local cache
      • New Settings option to update application data

      • Fixed patch when removing Account ID
      • Use internal PS3 fonts to fix issues with extended characters


      Hot fix release.


      • Fix unzip issue when unpacking online save files


      First public release.

      • Save file listing (+ details)
      • Save file SFO unlocking (remove lock flag)
      • Save file PFD resigning
      • Save file download from Online Database
      • Automatic detection of PSID/Account-ID settings

    • Using the application is simple and straight-forward:
      • Move UP/DOWN to select the save-game file you want to patch, and press :but x: . The patch screen will show the available fixes for the file. Select the patches and click Apply.
      • To see the item's details, press :but tri: . It will open the context menu on the screen. Press :but cir: to return to the list.
      • To reload the list, press :but square: .
      • Press left (L1/L2) or right trigger buttons (R1/R2) to move pages up or down.

    • No special setup is needed. Just download the latest apollo-ps3.pkg package and install it on your PlayStation 3. On first run, the application will detect and setup the required user settings.

    • screenshot_main.png screenshot_patches.png screenshot_savelist.png screenshot_settings.png screenshot_about.png screenshot_details.png

    • Credits

    See the full project's README for more information:
    feel free to share you comments and ideas! :cool2:

    Download link:
    As usual, full source code is available on GitHub :)
    Last edited: Apr 26, 2020
    swordzjj, aakkkyyy, Nano1993 and 39 others like this.


Discussion in 'PS3 Homebrew' started by bucanero, Feb 7, 2020.

    1. Ranma
      Thanks,very useful.I saw that there's the new Apollo Save Tools v1.0.2,do you think that I must put this version or Apollo Save Tools v1.0.0.?
    2. bucanero
      use the latest version (1.0.2), it includes improvements and fixes
      Algol likes this.
    3. craxyvirux
      Hello! Would like to ask if the cheat is going to work if i have psnpatch on my ps3?
    4. bucanero
      yes, it should work fine, it should have no issue with psnpatch or any other homebrew.

      save-game cheats are actually binary patches to the data stored in save-games. Apollo will patch the required files and resign the changes as needed.

      For safety, make a copy of your save-game before applying cheats. If everything works fine, then you can erase your backup afterwards.
    5. sandungas
      Im thinking in something, everything revolves around the idea of using a control file (it could be named APOLLO.LOG) stored in the same directory than the encrypted file, i guess the official functions are not going to complain about the additional file, are going to ignore it

      The idea is, the first time you add a cheat you can add a new action in the code in between reading the cheat data and patching it, this way:

      1) Read cheat data, decrypt savegame file, and find the target data (the original data in the savegame that is going to be patched in step 3)
      2) Store the target data in one "slot" of the the control file (i gues are going to be just a few bytes)
      3) Patch the savegame, encrypt it, etc...

      Later... if the user wants to add another cheat is needed to read the control file to compare new cheat with the other cheats that are already applyed, incase the new cheat is different his "target" data needs to be cummulated in the control file
      And so on... the point is the control file needs to store the original data of everything that was patched (with identifyers of every cheat)

      And if at some point the user disables all the cheats is needed to delete the control file, so we are back at the beginning with the original data recovered from the control file
      bucanero likes this.
    6. sandungas
      Ohh, i have an alternative idea easyer to implement :D
      Instead of using a custom APOLLO.LOG control file, you can create 1 file for every cheat applyed using exactly the same cheat format you already have implemented

      Lets say... we have a cheat file that patches the value 0x20 at offset 0xAA
      Then you decrypt the savegame, read offset 0xAA and find the original value that seems to be 0x40
      After that you "extract" the original cheat file to the savegame directory (with the value 0x20 at offset 0xAA).... and you replace the 0x20 by 0x40

      Is like making a copy of the cheat file... but replacing the patched data by the original
      This way the new cheat file generated by apollo is like a "reverter"
    7. bucanero
      you mean to keep a backup of the old file, or actually a binary .diff so you could actually "revert" a cheat one by one?

      also, is it useful for the general public? I assume that if someone is trying to cheat, he won't be seeking to "uncheat" later
    8. sandungas
      Yes, like a diff file, but a lot more simple, because by reading the original cheat file you know which offsets are going to be patched
      So you can create another cheat file (based in the one from the cheat database) containing the "reverse" data

      The result is you have the savegame directory with the rebuilt/encripted savedata + several "reverter" cheat files (containing all the original data that was patched)

      The good thing is the "reverter" cheat files are exactly the same format than the others, and the way how are applyed is the same

      When apollo opens the savegame directory you read the "reverter" files and you can inform the user how many patches are already applyed, and you can add an option to disable them

      *And when the user disables one cheat is really applying the "reverter" cheat file... and deleting it (to keep a record that indicates that it was removed)
      Last edited: Apr 6, 2020
      bucanero likes this.
    9. bucanero
      Apollo Save Tool v1.0.9 released:

      • Support for compressed save-game file patching
      • Added insert, delete, compress, and decompress BSD patch commands
      • Improved save list browsing
      • Improved BSD patch code parsing
      • Reduced package installer size
      Last edited: Apr 26, 2020
    10. kadorna2
      Just a heads-up, if there's corrupted saves in the device you are trying to load from, the app will hang in the loading screen forever
      Algol likes this.

Share This Page