PS3 [Update] Apollo Save Tool v1.8.4 released

Algol · Jun 16, 2020

@Coro, @bucanero.

Alors, pourquoi sous le Rebug-4.84.2-REX (console 2504B) cela fonctionne parfaitement ???

J'ai transféré d'un compte à un autre les SAVEs, modifiées puis re-signées celle-ci et tout est correct avec le Rebug mais pas sous le HFW-4.86.1/HEN-3.0.1 !!!
Je fais cela depuis très longtemps, je n'en suis pas à mon premier essai et notamment avec la série des jeux "Ratchet & Clank (1, 2 et 3)". C'est très sûrement un bug qui devrait être corrigé prochainement, je le souhaite fortement.

In English :

So, why under Rebug-4.84.2-REX (console 2504B) does it work perfectly ???

I transferred from one account to another the SAVEs, modified then re-signed this one and everything is correct with the Rebug but not under the HFW-4.86.1 / HEN-3.0.1 !!!
I have been doing this for a very long time, this is not my first try and in particular with the series of games "Ratchet & Clank (1, 2 and 3)". This is surely a bug which should be corrected soon, I strongly hope so.

Coro · Jun 16, 2020

Algol said:
@Coro, @bucanero.

Alors, pourquoi sous le Rebug-4.84.2-REX (console 2504B) cela fonctionne parfaitement ???

J'ai transféré d'un compte à un autre les SAVEs, modifiées puis re-signées celle-ci et tout est correct avec le Rebug mais pas sous le HFW-4.86.1/HEN-3.0.1 !!!
Je fais cela depuis très longtemps, je n'en suis pas à mon premier essai et notamment avec la série des jeux "Ratchet & Clank (1, 2 et 3)". C'est très sûrement un bug qui devrait être corrigé prochainement, je le souhaite fortement.

In English :

So, why under Rebug-4.84.2-REX (console 2504B) does it work perfectly ???

I transferred from one account to another the SAVEs, modified then re-signed this one and everything is correct with the Rebug but not under the HFW-4.86.1 / HEN-3.0.1 !!!
I have been doing this for a very long time, this is not my first try and in particular with the series of games "Ratchet & Clank (1, 2 and 3)". This is surely a bug which should be corrected soon, I strongly hope so.

on rebug, the "fake save data owner" is fixing any problems.

bucanero · Jun 16, 2020

Algol said:
So, why under Rebug-4.84.2-REX (console 2504B) does it work perfectly ???

I transferred from one account to another the SAVEs, modified then re-signed this one and everything is correct with the Rebug but not under the HFW-4.86.1 / HEN-3.0.1 !!!
I have been doing this for a very long time, this is not my first try and in particular with the series of games "Ratchet & Clank (1, 2 and 3)". This is surely a bug which should be corrected soon, I strongly hope so.

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 triangle on a savegame file (works on HEN) 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)

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.

If it works using brute force data, try to keep the files signed with Apollo so they can be compared.

bucanero · Jun 16, 2020

Coro said:
on rebug, the "fake save data owner" is fixing any problems.

exactly , when you use fake owner, that's a debug feature that disables any ownership validation.

Algol · Jun 16, 2020

bucanero said:
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 triangle on a savegame file (works on HEN) 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)

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.

If it works using brute force data, try to keep the files signed with Apollo so they can be compared.

Merci @bucanero ainsi qu'à @Coro pour vos réponses sincères et judicieuses. Demain matin je prendrai mes anciennes données, les signerai sur une clef USB puis les remettraient en place sur les comptes recevant les nouvelles SAVEs.

Merci beaucoup à vous deux ainsi qu'à TOUS les développeurs ici présents, un vieux monsieur de bientôt 62 ans vous remercie de tout coeur. Bien à vous.

English:
Thank you @bucanero and to @Coro for your sincere and judicious answers. Tomorrow morning I will take my old data, the signatories on a USB key then put them back in the accounts receiving the new SAVEs.

Thank you very much to both of you as well as to ALL the developers here, an old man of almost 62 years of age
thanks you very much. Yours.
Thank

Coro · Jun 16, 2020

Algol said:
Merci @bucanero ainsi qu'à @Coro pour vos réponses sincères et judicieuses. Demain matin je prendrai mes anciennes données, les signerai sur une clef USB puis les remettraient en place sur les comptes recevant les nouvelles SAVEs.

Merci beaucoup à vous deux ainsi qu'à TOUS les développeurs ici présents, un vieux monsieur de bientôt 62 ans vous remercie de tout coeur. Bien à vous.

English:
Thank you @bucanero and to @Coro for your sincere and judicious answers. Tomorrow morning I will take my old data, the signatories on a USB key then put them back in the accounts receiving the new SAVEs.

Thank you very much to both of you as well as to ALL the developers here, an old man of almost 62 years of age
thanks you very much. Yours.
Thank

N'oubliez pas de traduire.

English:
Don't forget to translate.

Algol · Jun 18, 2020

Bonsoir.

J'ai des réponses mais pas les solutions ...

Je viens de signer mes SAVEs par le "Brute Force Save Data v4.7.5" de Aldo (que je remercie au passage) et toutes les SAVEs que j'ai re-signé sont toutes acceptées par les comptes de destination. En faisant cela, j'ai découvert que c'est "Apollo Save Tool" qui rend les SAVEs, une fois re-signées par lui, incompatibles avec les jeux pour lesquels elles sont destinées. C'est regrettable.

Cela est en partie dû au fait que "Apollo" récupère je ne sais où le PSID de la console même si celui-ci n'est pas réel (masqué par webMAN-Mod) et le met dans le fichier re-signé. Il annule aussi le "Account ID" en y mettant des zéros.
J'ai éliminé les modifications faites sur les CID et PSID de ma console par webMAN-Mod (v1.47.28) et lui faisant re-forçer les bonnes valeurs (valeurs d'origines) mais seul le PSID ne revient pas à sa valeur d'origine dans "Apollo Save Tool v1.1.0". Il s'obstine à garder la valeur que j'avais forcé précédemment.
Je signale qu'en créant une SAVE même si webMAN est totalement actif, les signatures des SAVEs sont bonnes si je les visualise via APOLLO. C'est la re-signature qui crée le souci sur le PSID seul.

Question : comment obtenir le PSID d'origine lors de la re-signature d'une SAVE quelconque par "APOLLO Save Tool" ???

In English via G-Trad :

I have answers but not the solutions ...

I just signed my SAVEs with the "Brute Force Save Data v4.7.5" from Aldo (which I thank in passing) and all the SAVEs that I re-signed are all accepted by the destination accounts. By doing this, I discovered that it is "Apollo Save Tool" which makes SAVEs, once re-signed by it, incompatible with the games for which they are intended. It is unfortunate.

This is partly due to the fact that "Apollo" retrieves I do not know where the PSID of the console even if it is not real (hidden by webMAN-Mod) and puts it in the re-signed file. It also cancels the "Account ID" by putting zeros in it.
I eliminated the modifications made on the CID and PSID of my console by webMAN-Mod (v1.47.28) and making him re-force the good values (original values) but only the PSID does not return to its value d origin in "Apollo Save Tool v1.1.0". He insists on keeping the value that I had forced previously.
I note that by creating a SAVE even if webMAN is fully active, the signatures of the SAVEs are good if I view them via APOLLO. It is the re-signature that creates the concern on the PSID alone.

Question : how to obtain the original PSID when re-signing any SAVE with "APOLLO Save Tool" ???

Coro · Jun 18, 2020

Algol said:
Bonsoir.

J'ai des réponses mais pas les solutions ...

Je viens de signer mes SAVEs par le "Brute Force Save Data v4.7.5" de Aldo (que je remercie au passage) et toutes les SAVEs que j'ai re-signé sont toutes acceptées par les comptes de destination. En faisant cela, j'ai découvert que c'est "Apollo Save Tool" qui rend les SAVEs, une fois re-signées par lui, incompatibles avec les jeux pour lesquels elles sont destinées. C'est regrettable.

Cela est en partie dû au fait que "Apollo" récupère je ne sais où le PSID de la console même si celui-ci n'est pas réel (masqué par webMAN-Mod) et le met dans le fichier re-signé. Il annule aussi le "Account ID" en y mettant des zéros.
J'ai éliminé les modifications faites sur les CID et PSID de ma console par webMAN-Mod (v1.47.28) et lui faisant re-forçer les bonnes valeurs (valeurs d'origines) mais seul le PSID ne revient pas à sa valeur d'origine dans "Apollo Save Tool v1.1.0". Il s'obstine à garder la valeur que j'avais forcé précédemment.
Je signale qu'en créant une SAVE même si webMAN est totalement actif, les signatures des SAVEs sont bonnes si je les visualise via APOLLO. C'est la re-signature qui crée le souci sur le PSID seul.

Question : comment obtenir le PSID d'origine lors de la re-signature d'une SAVE quelconque par "APOLLO Save Tool" ???

In English via G-Trad :

I have answers but not the solutions ...

I just signed my SAVEs with the "Brute Force Save Data v4.7.5" from Aldo (which I thank in passing) and all the SAVEs that I re-signed are all accepted by the destination accounts. By doing this, I discovered that it is "Apollo Save Tool" which makes SAVEs, once re-signed by it, incompatible with the games for which they are intended. It is unfortunate.

This is partly due to the fact that "Apollo" retrieves I do not know where the PSID of the console even if it is not real (hidden by webMAN-Mod) and puts it in the re-signed file. It also cancels the "Account ID" by putting zeros in it.
I eliminated the modifications made on the CID and PSID of my console by webMAN-Mod (v1.47.28) and making him re-force the good values (original values) but only the PSID does not return to its value d origin in "Apollo Save Tool v1.1.0". He insists on keeping the value that I had forced previously.
I note that by creating a SAVE even if webMAN is fully active, the signatures of the SAVEs are good if I view them via APOLLO. It is the re-signature that creates the concern on the PSID alone.

Question : how to obtain the original PSID when re-signing any SAVE with "APOLLO Save Tool" ???

try uninstall and reinstall apollo.

bucanero · Jun 18, 2020

Algol said:
This is partly due to the fact that "Apollo" retrieves I do not know where the PSID of the console even if it is not real (hidden by webMAN-Mod) and puts it in the re-signed file. It also cancels the "Account ID" by putting zeros in it.

alright, that explains the mystery, you're spoofing IDs and Apollo is using wrong data to resign the savegames.

I eliminated the modifications made on the CID and PSID of my console by webMAN-Mod (v1.47.28) and making him re-force the good values (original values) but only the PSID does not return to its value d origin in "Apollo Save Tool v1.1.0". He insists on keeping the value that I had forced previously.
I note that by creating a SAVE even if webMAN is fully active, the signatures of the SAVEs are good if I view them via APOLLO. It is the re-signature that creates the concern on the PSID alone.

after disabling everything, you need to erase the Apollo Settings save file, and then run Apollo clean, to let the app re-detect all the user account values. (if not, the app will keep using the old values.)
Then check on the About screen, if the values detected are indeed the correct ones.

Question : how to obtain the original PSID when re-signing any SAVE with "APOLLO Save Tool" ???

If everything else fails due to the ID spoofing, you can always force the values using the owner.txt override file.

It's a simple text file, called owner.txt in /dev_hdd0/game/NP0APOLLO/USRDIR/ :

Code:

0011223344556677 8899AABBCCDDEEFF
AABBCCDD55667788
00000123

first line is the PSID
second line, account ID
third line, User ID

if you put the owner.txt file, Apollo will load whatever values are there, and use them to resign the saves. It's also useful if you want to resign saves for a different console that might be running OFW and can't use any homebrew.

Let me know your results

bucanero · Jun 18, 2020

Coro said:
try uninstall and reinstall apollo.

btw, user settings and IDs are stored in the "Apollo settings" save file, so you need to erase that savegame to force the app to re-detect ID values.

Algol · Jun 19, 2020

Comme conseillé plus haut, j'ai supprimé "Apollo" via le XMB et j'ai aussi supprimé le dossier "NP0APOLLO" par le gestionnaire de fichier de mmCM de chacun des 7 comptes (7 utilisateurs différents) de la console CECH-4204C sous "HEN-3.0.1".

J'ai ré-installé "APOLLO v1.1.0" et relancé. Il a relancé l'installation des "Cheat Codes" puis je lui ai fait refaire sa configuration pour le 1er compte. Problème, il ne peut plus sauver son fichier de configuration (ne trouve pas le chemin), il ne trouve plus le chemin des SAVEs non plus.

Pourquoi ??? Peut-on y remédier et comment ???

J'ai remis en place le dossier "NP0APOLLO" dans le premier compte (home/00000001/...) puis j'ai relancé APOLLO et là, ça re-fonctionne mais le PSID est toujours mauvais. Le "userID" est bon.

Questions : dois-je créer le fichier "owner.txt" pour chacun des comptes (dans /home/00000001, etc…) ou un seul fichier pour l'ensemble des 7 comptes de cette console ???

In English via G-trad :

As advised above, I deleted "Apollo" via the XMB and I also deleted the "NP0APOLLO" folder by the mmCM file manager of each of the 7 accounts (7 different users) of the CECH-4204C console under "HEN-3.0.1".

I reinstalled "APOLLO v1.1.0" and relaunched. He relaunched the installation of "Cheat Codes" then I made him redo his configuration for the 1st account. Problem, it can no longer save its configuration file (cannot find the path), it can no longer find the path of the SAVEs either.

Why ??? Can we fix it and how ???

I replaced the "NP0APOLLO" folder in the first account (home / 00000001 / ...) then I restarted APOLLO and there it works again but the PSID is still bad. The "userID" is good.

Questions: should I create the "owner.txt" file for each of the accounts (in / home / 00000001, etc…) or a single file for all of the 7 accounts on this console ???

@bucanero : pouvez-vous répondre à ces quelques questions s'il vous plait ? (in English : can you answer these few questions please?)

SpyroMancer · Jun 19, 2020

Great tool.. the only thing missing i would like to see, is a progress indicator... percent or bar

bucanero · Jun 19, 2020

SpyroMancer said:
Great tool.. the only thing missing i would like to see, is a progress indicator... percent or bar

most actions like patching a savegame with a cheat or resigning are quick

for which actions were you thinking about a progress bar?

bucanero · Jun 19, 2020

Algol said:
As advised above, I deleted "Apollo" via the XMB and I also deleted the "NP0APOLLO" folder by the mmCM file manager of each of the 7 accounts (7 different users) of the CECH-4204C console under "HEN-3.0.1".

the savegame settings shouldn't be deleted with Multiman or any file manager, they should be deleted using the XMB PS3 Save manager.
You are deleting the files, but some stuff might still be left on the internal XMB database, so any weird behavior can happen.

Try to rebuild the database just to clean up the data.

I reinstalled "APOLLO v1.1.0" and relaunched. He relaunched the installation of "Cheat Codes" then I made him redo his configuration for the 1st account. Problem, it can no longer save its configuration file (cannot find the path), it can no longer find the path of the SAVEs either.

Why ??? Can we fix it and how ???

I replaced the "NP0APOLLO" folder in the first account (home / 00000001 / ...) then I restarted APOLLO and there it works again but the PSID is still bad. The "userID" is good.

Questions: should I create the "owner.txt" file for each of the accounts (in / home / 00000001, etc…) or a single file for all of the 7 accounts on this console ???

with the spoofing and the mixed-up XMB database with multiple users, I guess that any weird behavior can be expected. You should try to start clean from scratch.

The owner.txt file is a single file, and must be placed in /dev_hdd0/game/NP0APOLLO/USRDIR/
(only 1 file, not one for each account)

Code:

/dev_hdd0/game/NP0APOLLO/USRDIR/owner.txt

that file will override any detected value, it's your best option right now.

Algol · Jun 19, 2020

Donc, et si j'ai bien compris, il me faut faire ce fichier "owner.txt" pour chaque compte au moins une fois et ainsi ils re-deviendront corrects. C'est sûr ???

So, and if I understood correctly, I must make this "owner.txt" file for each account at least once and thus they will become correct again. It's certain ???

bucanero · Jun 19, 2020

Algol said:
So, and if I understood correctly, I must make this "owner.txt" file for each account at least once and thus they will become correct again. It's certain ???

I'm not sure if settings will be saved... the owner.txt is loaded, but you might need to enter the Settings menu and change something to get the new values saved.

Algol · Jun 19, 2020

Je n'ai eu aucun besoin de créer le fichier "owner.txt". J'ai simplement détruit les SAVEs de chaque compte via le XMB puis j'ai lancé sur chaque compte "APOLLO", il a recréé ses paramètres mais cette fois-ci ils sont bons, le PSID est correct maintenant ...

Merci beaucoup pour ton aide très précieuse @bucanero, je ne t'oublierai pas ...

I had no need to create the "owner.txt" file. I simply destroyed the SAVEs of each account via the XMB then I launched on each account "APOLLO", it recreated its parameters but this time they are good, the PSID is correct now ...

Thank you very much for your very precious help @bucanero, I will not forget you ...

JDOGGOKUSSJ2 · Jun 26, 2020

JAPANBOY said:
Please be corresponding
The Last of us BCJS-37010
Skyrim BLJM-60413

I want God mode‼︎

Just fyi if your ps3 is modded you can play skyrim with mods all you do is place the mods in the folder with the dawnguard dlc either through ftp or multiman not all mods work but most basic ones do

bucanero · Jul 4, 2020

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

Changes

Export single .rif license to .rap file (User Backup menu)
Import single .rap file to user's .rif license (User Backup menu)
Bulk import .rap files to user's content .rif licenses (User Backup menu)

ashura · Jul 4, 2020

Hello bucanero i hope that you are having a wonderful day i was wondering maybe on the future you may add the change region save feature into apollo? thanks i will be looking foward for your answer

PS3 [Update] Apollo Save Tool v1.8.4 released

Algol

Coro

bucanero

bucanero

Algol

Coro

Algol

Coro

bucanero

bucanero

Algol

SpyroMancer

bucanero

bucanero

Algol

bucanero

Algol

JDOGGOKUSSJ2

bucanero

ashura

Similar threads

Featured content

Trending content

Latest posts