PS3 [Update] Apollo Save Tool v1.8.4 released

Ranma · Mar 29, 2020

bucanero said:
if you have more than 1 user on your PS3, just open Apollo from the desired user account, then the app will access the save-games from that user.

So, steps:

login to the ps3 with the right user

open Apollo

(optional) check on the About screen, you should see the right User ID there

go to HDD saves

resign/cheat/patch the save you want

As usual, my suggestion is to make a copy of the save-game before trying cheats or patches.

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.?

bucanero · Mar 29, 2020

Ranma said:
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.?

use the latest version (1.0.2), it includes improvements and fixes

craxyvirux · Apr 1, 2020

Hello! Would like to ask if the cheat is going to work if i have psnpatch on my ps3?

bucanero · Apr 1, 2020

craxyvirux said:
Hello! Would like to ask if the cheat is going to work if i have psnpatch on my ps3?

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.

sandungas · Apr 6, 2020

bucanero said:
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.

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

sandungas · Apr 6, 2020

Ohh, i have an alternative idea easyer to implement

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"

bucanero · Apr 6, 2020

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

sandungas · Apr 6, 2020

bucanero said:
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

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)

bucanero · Apr 26, 2020

Apollo Save Tool v1.0.9 released:
https://github.com/bucanero/apollo-ps3/releases/tag/v1.0.9

Changes

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

kadorna2 · May 16, 2020

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

bucanero said:
Apollo Save Tool v1.0.9 released:
https://github.com/bucanero/apollo-ps3/releases/tag/v1.0.9

Changes

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

arcadekidflo · May 31, 2020

Can a save be resigned to free , not to depend on console or user ?

ConsolemanDE · Jun 9, 2020

Hey... Maybe someone can help.
I try to use downloaded saves on my PS3.
Tried to resign them on usb-Stick or on internal HDD but no chance to use them.
The games always tell me the Savegame doesn't belong to me and I cannot use it.
What am I doing wrong?
I am on Rebug 4.86.1 with a Slim PS3

bucanero · Jun 9, 2020

ConsolemanDE said:
Hey... Maybe someone can help.
I try to use downloaded saves on my PS3.
Tried to resign them on usb-Stick or on internal HDD but no chance to use them.
The games always tell me the Savegame doesn't belong to me and I cannot use it.
What am I doing wrong?
I am on Rebug 4.86.1 with a Slim PS3

which save game are you trying?

just to be sure, you need to download a save game to USB, resign the save on the USB, and then copy the resigned save to the hard drive using the XMB.

I have tested it with lollipop chainsaw (among other games) and it works fine, but I don't know which file are you using

Berion · Jun 9, 2020

arcadekidflo said:
Can a save be resigned to free , not to depend on console or user ?

It cannot. Sony doesn't implement such possibility (for devs, they added only bypassing ownership checking in DEX/DECR models).

ConsolemanDE · Jun 9, 2020

bucanero said:
which save game are you trying?

just to be sure, you need to download a save game to USB, resign the save on the USB, and then copy the resigned save to the hard drive using the XMB.

I have tested it with lollipop chainsaw and it works fine, but I don't know which file are you using

I used several Savegames. Dirt 3, Need for Speed, Gran Turismo 6.
Downloaded them from a forum, copied them to the USB Stick and clicked on resign in Apollo.

bucanero · Jun 10, 2020

ConsolemanDE said:
I used several Savegames. Dirt 3, Need for Speed, Gran Turismo 6.
Downloaded them from a forum, copied them to the USB Stick and clicked on resign in Apollo.

some games do have additional security checks, and even after resigning they will be detected as saves from another player.

if you resigned the files on USB using Apollo, and then you were able to transfer the files to HDD, then the files are valid because the PS3 won't allow to copy the files if they're corrupt.
In apollo's about screen, you can also check that your account, PSID, and user ID are correctly detected and vaild.
as quick way to check, on XMB / Save Data utility (ps3) if you press :but tri:

on a savegame file (works on HEN too) you can see an "* Owner information" option. If you click on it, it will tell you if that savegame is owned by the current user or not.

If the screen says something like:
Owner (online) / Owner (local)
it means the save is resigned and is owned by the current user.

if the screen says
Not owner (....)
it means you're not the owner, and need to resign it. (resign it on USB, then copy it back to HDD or the database won't be updated)

if the savegame says you're the owner, but the game rejects it when loading, then the game has additional checks. In that case, probably you'll need to use Artemis to do in-memory cheat, or use Apollo to patch an original savegame if there's any patch available.

btw, if you want, you can also try to resign those files using aldo's Bruteforce data tool in your computer, and then copy the files to the PS3.

bucanero · Jun 14, 2020

Apollo Save Tool v1.1.0 released:
https://github.com/bucanero/apollo-ps3/releases/tag/v1.1.0

Changes

Exporting the user's content licenses to .RAP files (User Backup menu)

You can now export and backup your digital licenses (.rif) to .RAP files on USB.

Coro · Jun 14, 2020

bucanero said:
Apollo Save Tool v1.1.0 released:
https://github.com/bucanero/apollo-ps3/releases/tag/v1.1.0

Changes

Exporting the user's content licenses to .RAP files (User Backup menu)

You can now export and backup your digital licenses (.rif) to .RAP files on USB.

Awesome update! Resigning saves and backing up raps without needing pc is very handy.

Algol · Jun 16, 2020

Hello @bucanero.

J'ai un gros souci de mauvaise signature des SAVES sur ma console SuperSlim de modèle CECH-4204C sous le HFW-4.86.1/HEN-v3.0.1. Le jeu "Ratchet et Clank" me dit : "Cette sauvegarde n'appartient pas au joueur actuel, ..." après modification et signature de la SAVE.
Je possède une autre console de modèle CECH-2504B sous le CFW "Rebug-4.84.2-REX" qui a la fonctionnalité FSDO activée (Fake Save Data Owner) et j'ai utilisé la version 1.10 de APOLLO Save Tool et tout c'est bien passé, il est possible que le FSDO actif ai permis le bon fonctionnement des modifications.
Il me semble que ce problème existe depuis la version 1.0.2 mais je n'en suis pas très sûr.

Pourriez-vous corriger ce souci SVP ?

Très cordialement.

In English via G-Trad :

I have a big problem with bad SAVES signing on my SuperSlim console of model CECH-4204C under HFW-4.86.1 / HEN-v3.0.1. The game "Ratchet and Clank" tells me: "This backup does not belong to the current player, ..." after modification and signature of the SAVE.
I have another CECH-2504B model console under the CFW "Rebug-4.84.2-REX" which has the FSDO functionality activated (Fake Save Data Owner) and I used version 1.10 of APOLLO Save Tool and all this went well, it is possible that the active FSDO allowed the correct functioning of the modifications.
It seems to me that this problem has existed since version 1.0.2 but I am not very sure.
Could you please correct this concern ?

Very cordially.

Coro · Jun 16, 2020

Algol said:
Hello @bucanero.

J'ai un gros souci de mauvaise signature des SAVES sur ma console SuperSlim de modèle CECH-4204C sous le HFW-4.86.1/HEN-v3.0.1. Le jeu "Ratchet et Clank" me dit : "Cette sauvegarde n'appartient pas au joueur actuel, ..." après modification et signature de la SAVE.
Je possède une autre console de modèle CECH-2504B sous le CFW "Rebug-4.84.2-REX" qui a la fonctionnalité FSDO activée (Fake Save Data Owner) et j'ai utilisé la version 1.10 de APOLLO Save Tool et tout c'est bien passé, il est possible que le FSDO actif ai permis le bon fonctionnement des modifications.
Il me semble que ce problème existe depuis la version 1.0.2 mais je n'en suis pas très sûr.

Pourriez-vous corriger ce souci SVP ?

Très cordialement.

In English via G-Trad :

I have a big problem with bad SAVES signing on my SuperSlim console of model CECH-4204C under HFW-4.86.1 / HEN-v3.0.1. The game "Ratchet and Clank" tells me: "This backup does not belong to the current player, ..." after modification and signature of the SAVE.
I have another CECH-2504B model console under the CFW "Rebug-4.84.2-REX" which has the FSDO functionality activated (Fake Save Data Owner) and I used version 1.10 of APOLLO Save Tool and all this went well, it is possible that the active FSDO allowed the correct functioning of the modifications.
It seems to me that this problem has existed since version 1.0.2 but I am not very sure.
Could you please correct this concern ?

Very cordially.

Some games can detect if a save is resigned (even using pc tools). If it is only happening on this one game then i think it is not a bug or anything that can be fixed.

PS3 [Update] Apollo Save Tool v1.8.4 released

Ranma

bucanero

craxyvirux

bucanero

sandungas

sandungas

bucanero

sandungas

bucanero

kadorna2

arcadekidflo

ConsolemanDE

bucanero

Berion

ConsolemanDE

bucanero

bucanero

Coro

Algol

Coro

Similar threads

Featured content

Trending content

Latest posts