PS3 restoring PS3 saves from old local profile to a new one?

[ponytail]

So PSN was down today and I thought my profile was bugged as trophies weren't loading, so I backedup my local savedata:

/devhdd0/00000003/savedata/

Inside that folder is the game savedata folders like this:

And inside those folders, it looks like this:

So keep in mind, these PS3 saves are signed to a now deleted user profile called 00000003. Despite backing up the entire 00000003 folder (with the gamedata inside), I can't seem to restore it.

The backedup folder looks like this:

So I made a new account, the local user account has the exact same username. Obviously in the backend, the new local user account is signed as 00000007.

I'm wondering how to:

i) can I replicate the entire 00000003 folder to be used by the new 00000007 account?

ii) if not, can I replicate the savedata from 00000003 to the new 00000007 account?

iii) if all that fails, how can I restore the savedata via USB method using Apollo? I did this, and the saves above that it signs to be used by 00000007 all have strange names, and the Apollo photo as the icon and they don't work in game.

I would very much appreciate the help.

 

[ponytail]

I fixed it and so I will write it here in case anyone ever needs to do the same.


i) use a USB, for some reason the data has to be in PS3/SAVADATA/[folders] on the USB or else it won't work

ii) boot Apollo, convert and resign all the USB saves.

iii) goto XMB, go to Game Data folder and the USB will be there. Copy all the converted saves into the Game Data folder on the XMB.


Fixed.

 

[Berion]

Not Game Data but Save Data.

 

[bucanero]

I fixed it and so I will write it here in case anyone ever needs to do the same.


i) use a USB, for some reason the data has to be in PS3/SAVADATA/[folders] on the USB or else it won't work

ii) boot Apollo, convert and resign all the USB saves.

iii) goto XMB, go to Game Data folder and the USB will be there. Copy all the converted saves into the Game Data folder on the XMB.


Fixed.

yes, using Apollo + the native XMB copy is the best option on PS3.
Apollo can resign all saves on the USB drive, and then the XMB will copy (and verify) that all saves are properly signed to the current user.

If the XMB detects something wrong about the saves, it will report an error on screen and won't copy the corrupt save(s).

 

[ponytail]

yes, using Apollo + the native XMB copy is the best option on PS3.
Apollo can resign all saves on the USB drive, and then the XMB will copy (and verify) that all saves are properly signed to the current user.

If the XMB detects something wrong about the saves, it will report an error on screen and won't copy the corrupt save(s).

Do you possible know why Apollo Save Tool doesn't open Trophy manager now? Just says "No save-data" when opening Trophies, I've been playing PS3 all morning anyway so it should usually show my games

 

[Charles_n_town]

I can't really help with the question, but this reminded me of psn being down today. on my ps5, after I downloaded the ps+ monthly games, a message popped up with something like "psn will be right back." I had never seen that message before, even when psn was down due to a technical problem. must've been scheduled maintenance.

 

[ponytail]

Do you possible know why Apollo Save Tool doesn't open Trophy manager now? Just says "No save-data" when opening Trophies, I've been playing PS3 all morning anyway so it should usually show my games

I fixed it, lol. Tried a bunch of things like clearing cache etc, the thing that did it was to delete the Apollo Save data from my saves and create a new one with this new local profile.

 

[bucanero]

I fixed it, lol. Tried a bunch of things like clearing cache etc, the thing that did it was to delete the Apollo Save data from my saves and create a new one with this new local profile.

yes, you had the old Apollo settings from the previous user, to force re-detection of correct user/account-id data you could:
- opt1: erase the Apollo save (as you did)
- opt2: open Apollo -> "Settings" menu -> select "redetect account data"

Anyways, no need to do anything now since you already fixed it with option #1