“Manual Backup”
For the first time in Sony console history, the PlayStation 3 has allowed the user to perform and restore a
system backup (using the "System Backup Utility"). Unfortunately, although this produces backups that
contain most of the data from the hard drive (completely unnecessary from the user's point of view, e.g. the estore cache…), it does not allow the user to restore the data in all circumstances, particularly when restoring
data on a different console or with a different motherboard. As such, the system backup is practically… useless.
The same applies to the "Transfer Data Utility" which, while theoretically allowing you to transfer everything
to another console, is limited in that it requires the same firmware version on both consoles, and in some cases
it will delete data from the source console that will not get restored on the target console…
Fortunately, with help from the so-called scene, i.e. the community focused around unofficial software, the user
is able to copy what they want, restore what they want, when they want, without intermediating with Sony
servers, without restrictions related to the firmware version, and with the possibility of re-signing data for
another user’s account.
***
This guide assumes that you are able to use a file manager and/or FTP client. That's why I’ve skipped the
descriptions of context menus, PC–PS3 connection configuration, installation and launching of programs, CFW
or HEN installing etc. so basically anything that is not directly related to the backup! In this guide, I have
focused solely on providing the paths for specific data and a brief description along with any notes that apply to
them.
The user’s directory is the user’s number in that console’s account creation order. If you find the phrase
"<user>" somewhere in a path, it means that you need to replace it with the user number. For example
"dev_hdd0/home/<user>/", for the first account created on that console would be "dev_hdd0/home/00000001/".
The XMB does not load most of the data in real time. Instead it uses a database that is populated during, among
other things, program installation, creating/updating save files, virtual memory cards, trophies, etc. Therefore,
after restoring, e.g. trophies, go to the so-called Recovery Menu (Sony calls it Service Mode, but the scene
uses a different term, so as not to be confused with Factory Service Mode) and rebuild the database (option
"4. Rebuild Database").
Console settings, IDs and keys
In addition to the stuff on the hard drive, it is also worth making a backup of important data from the console’s
flash memory, the place where the firmware is stored.
The first thing worth copying is the file "dev_flash2/etc/xRegistry.sys", which contains not only the PS3
settings but also the NP Account IDs of all console users, their numbers, logins, and SEN passwords. It is the
NPAID that identifies the user on the SEN network on all consoles, and it is involved in signing some data, so
it’s worth knowing. The "registry" can be edited by programs such as xRegistry.sys Editor.
The second most important thing to copy is the NAND/NOR memory image from which you can read the
IDPS, which is also involved in signing some data, but most importantly it allows you to save the PS3 in the
event of its "death". The flash can be dumped with e.g. with MemDump or Rebug Toolbox. The IDPS can also
be read directly on the console, and many programs, such as multiMAN, simply display it somewhere in their
menu.
Last, but not least, is the EID Root Key, which makes it possible to calculate the ATA Key and VFLASH Key,
which in turn will make it possible to read the encrypted hard drive on a computer (e.g. in case the console
dies of YLOD/RSOD). This key can be read, e.g. with the Rebug Toolbox program, unfortunately only on
CFW for now (it is not yet known how to do this on HEN).
Trophies
All trophies are located in "dev_hdd0/home/<user>/trophy/" and are signed. Each user has their own set stored
in their own directory.
Saves for PlayStation 3 games
PS3 game saves are all located in "dev_hdd0/home/<user>/savedata/". Admittedly, they can be exported within
the XMB to e.g. a flash drive, but not all of them. If the game developer decided to put the "Copy Prohibited"
attribute in the "PARAM.SFO" file, then CellOS will not allow them to be copied in the XMB menu like
"normal saves". Because of this, it can be more convenient to make a copy of all save files manually, e.g. with a
file manager, by simply copying the entire "savedata" folder or the save folder of a specific game. Also, the
XMB will not restore protected saves, so the same procedure can be used to restore protected saves.
Just like trophies, saves are also signed to a specific user. These can be modified using the programs PS3
Bruteforce Save Data (Windows) or Apollo Save Tool (PS3).
Saves for PlayStation 2 games
PS2 game saves are stored on virtual memory cards. Depending on the emulator used, these cards may be
unencrypted (*.VM2) or encrypted (*.VME). All card images contain ECC blocks, so you cannot use the same
VMC e.g. with Open PS2 Loader or PCSX2 without enriching them with data correction first.
•
Unencrypted VMCs can be created with the "Memory Card Utility (PS1/PS2)" from within XMB.
You’ll find them in "dev_hdd0/savedata/vmc/*.VM2". There, you will see all the saves that on that
memory card, and from there you can export them to a PSV container for external storage (eg flash
drive) ("dev_usb000/PS3/EXPORT/PSV/*.PSV").
•
Encrypted VMCs, in turn, are stored in:
"dev_hdd0/home/<user>/ps2emu2_savedata/<GameID>/SCEVMC0.VME". They can be exported to,
e.g. a flash drive from within the XMB, with the "Save Data Utility (PS2)", then they will be exported
to "dev_usb000/PS3/EXPORT/PS2SD/<GameID>/SCEVMC0.VME". In the case of so-called place
holders, e.g. PS2 ISO/Classics Launcher (by Habib) v1.03, the GameID will always be the same, i.e.
PS2U10000, but normally and for games purchased from the PlayStation Store, the GameID will be
unique for each individual title.
Saves for PlayStation 1 games
PS 1 game saves are stored on virtual memory cards, and are located in "dev_hdd0/savedata/vmc/*.VM1". Just
like the cards for PS2 games, they can be exported to a *.psv file ("dev_usb000/PS3/EXPORT/PSV/*.PSV").
Saves for PlayStation Portable games
Saves for PlayStation Portable games, both for Minis and Remasters, are saved in:
"dev_hdd0/home/<użytkownik>/minis_savedata/<GameID>/". They can be exported to, e.g. a flash drive from
within the XMB, in the "Save Data Utility (minis/PSP Remaster/PSP)" menu. They will export to
"dev_usb000/PSP/SAVEDATA/<GameID>/".
Licenses
All licenses (*.rif, *.edat, *.mln) for PlayStation Store purchases as well as the activation file (act.dat), can be
found in "dev_hdd0/home/<user>/exdata/". The data is signed.
Installed games, patches and add-ons
Games that install any data from the disc, and all games purchased from the PlayStation Store, as well as
patches for them, are stored in "dev_hdd0/game/<GameID>/". DLC almost always goes into the same folder
(sometimes the developer divides them into a separate folder, but this is rare). So all of this data is mixed
together and cannot be separated without knowing the contents of the PKG packages that they were extracted
from (the mix contains cache, patches and most often DLC).
Programs
The same as above. However, in this case, the GameIDs are made up by the developers, and some even pretend
to be other games (e.g. multiMAN is installed in "dev_hdd0/game/BLES80608/"). The emulator directories
may also contain games for the emulated consoles, e.g. ROMs for the Game Boy Advance.
Games copied from Disc
That is, disc content copied to folders, used by backup managers, i.e. jailbreak format (an idiotic term by-theway, but unfortunately it caught on).
Currently stored into the "dev_hdd0/GAMES/<GameID>/" folder, but previously also stored in:
•
"dev_hdd0/BDRIPS/"
•
"dev_hdd0/GAMEZ/"
•
"dev_hdd0/game/LAUN12345/GAMEZ/"
•
"dev_hdd0/game/OMAN67890/GAMEZ/"
Disc images
That is, dumps of relatively all the data from the optical medium to a file. Depending on the parent console,
they are loaded from several different places:
PS3 game images (unencrypted)
"dev_hdd0/PS3ISO/*.iso"
PS3 game images (encrypted)
not supported
PS2 game images (DVD)
"dev_hdd0/PS2ISO/*.iso"
mode 1 (2048)
PS2 game images (CD)
"dev_hdd0/PS2ISO/*.bin" + *.cue
mode 2 (2352)
PS2 game images (encrypted DVD)
"dev_hdd0/PS2ISO/*.iso.enc"
PS2 game images (encrypted CD)
"dev_hdd0/PS2ISO/*.bin.enc"
PS1 game images
"dev_hdd0/PSXISO/*.bin" + *.cue
"dev_hdd0/PSXISO/*.img" + *.sub + *.ccd + *.cue
PSP game images
"dev_hdd0/PSPISO/*.iso"
mode 2 (2352 i 2368)
In the case of PS3 disc images that are encrypted (i.e. in the form of a 1:1 copy made on a PC or console using
multiMAN with Direct Disc Access enabled), they must first be decrypted. At the moment, neither Cobra nor
Mamba support the encrypted *.iso. Trying to load such an image will result in error 0x80010017.
Encrypted ISOs can be made available to the console in decrypted form on the fly. However, this requires
ps3netsrv and a unique key ("*.dkey") for each title in the "REDKEY" folder.
PKG packages
Packages can be in "dev_hdd0/PKG/*.pkg" or "dev_hdd0/packages/*.pkg". Only the user or backup managers
can temporarily store patches there. This is not a rule, but by default none do.
PUP packages
These are installation packages for firmware. They can be in "dev_hdd0/updater/<number e.g. 01>/*.pup". In
order for the console to use these, the "Debug Updates" option in the debug XMB must be enabled.
Covers
These are cover artwork used by various backup managers instead of the standard icons. They should all be
named according to this scheme: "<GameID>_COV.PNG" (for PS3 games, e.g. "BLUS12345_COV.PNG")
and "<XXXX_YYY.YY>_COV.PNG" (for games from older Sony consoles, e.g. "SCES_123.45_COV.PNG").
Alternately, they can take their names from the corresponding disc image (e.g. "test.iso" cover could be named
"test.png").
•
For PS3:
"/dev_hdd0/game/BLES80608/USRDIR/covers/"
"/dev_hdd0/game/NPEA00374/USRDIR/covers/"
"/dev_hdd0/game/MANAGUNZ0/USRDIR/covers/"
"/dev_hdd0/GAMES/covers/"
"/dev_hdd0/GAMEZ/covers/"
•
For ancient consoles:
"/dev_hdd0/game/BLES80608/USRDIR/covers_retro/psx/"
Themes
XMB skins, both static and dynamic, free (*.p3t) and purchased (*.edat), are stored in "dev_hdd0/theme/".
Multimedia
For movies, music, and photos: "dev_hdd0/video/", "dev_hdd0/music/", "dev_hdd0/photo/".
Social crap
•
Last twenty chat conversations (or at least this was still the case on firmware 3.50):
"dev_hdd0/home/<user>/chat/room/".
•
Avatars for the user and friend list ("avatar/*.png"), sent ("imout/") and received ("imin/") messages
to/from users, as well as profile comments: "dev_hdd0/home/<user>/friendim/".
Berion
2020-04-19
You may distribute the guide on any site, only as an unmodified PDF.
All rights reserved, modification and/or copying prohibited.
English translation 2021-02-20 by AdamCatalyst with permission of Berion.
Original unmodified document by Berion is available here.