Savegames

This page describes the format, de/encryption, etc. of savegames found in 3DS game cartridges/gamecards. You can find savegames from various 3DS games on the Games page.

Encryption

On the 3DS savegames are stored much like on the DS, that is on a FLASH chip in the gamecart. On the DS these savegames were stored in plain-text but on the 3DS a layer of encryption was added. This is highly likely a streamcipher, as the contents of several savegames exhibit the odd behavior that xor-ing certain parts of the savegame together will result in the plain-text appearing.

The reason this works is because the stream cipher used has a period of 512 bytes. That is to say, it will repeat the same keystream after 512 bytes. The way you encrypt with a stream cipher is you XOR your data with the keystream as it is produced. Unfortunately, if your streamcipher repeats and you are encrypting a known plain-text (in our case, zeros) you are basically giving away your valuable keystream.

So how do you use this to decrypt a savegame on a 3DS? First off, you chunk up the savegame into 512 byte chunks. Then, you bin these chunks by their contents, discarding any that contain only FF. Now look for the most common chunk. This is your keystream. Now XOR the keystream with your original savegame and you should have a fully decrypted savegame. XOR with the keystream again to produce an encrypted savegame.

Wear leveling

The 3DS employs a wear leveling scheme on the savegame FLASH chips. This is done through the usage of blockmaps and a journal. The blockmap is located at offset 0 of the flash chip, and is immediately followed by the journal. The initial state is dictated by the blockmap, and the journal is then applied to that.

First, there are 8 bytes whose purposes are currently unknown. Then comes the actual blockmap. The blockmap structure is simple:

struct header_entry {
        uint8_t phys_sec; // when bit7 is set, block has checksums, otherwise checksums are all zero
        uint8_t alloc_cnt;
        uint8_t chksums[8];
} __attribute__((__packed__));

There's one entry per sector, counting from physical sector 1 (sector 0 contains the blockmap/journal).

The 2 bytes that follow the blockmap are the CRC16 (with starting value 0xFFFF (like modbus)) of the first 8 bytes and the blockmap.

Then comes the journal. The journal structure is as follows:

struct sector_entry {
        uint8_t virt_sec;       // Mapped to sector
        uint8_t prev_virt_sec;  // Physical sector previously mapped to
        uint8_t phys_sec;       // Mapped from sector
        uint8_t prev_phys_sec;  // Virtual sector previously mapped to
        uint8_t phys_realloc_cnt;       // Amount of times physical sector has been remapped
        uint8_t virt_realloc_cnt;       // Amount of times virtual sector has been remapped
        uint8_t chksums[8];
} __attribute__((__packed__));

struct long_sector_entry{
        struct sector_entry sector;
        struct sector_entry dupe;
        uint32_t magic;
}__attribute__((__packed__));

With magic being a constant 0x080d6ce0.

The checksums in the blockmap/journal entries work as follows:

• each byte is the checksum of an encrypted 0x200 bytes large block
• to calculate the checksum, a CRC16 of the block (with starting value 0xFFFF) is calculated, and the two bytes of the CRC16 are XORed together to produce the 8bit checksum

Partitions

There can be multiple partitions on the chip. The partitions are represented by tables of DIFI blobs inside a DISA structure. The order of the DIFI blobs is the order of the partitions in the chip.

DISA

• If the uint32 @ 0x168 into the image in the DISA is a %1=1, then first table is is hashed, otherwise the second DIFI table is hashed.
• If the table has more then 1 DIFI then the uint32 @ 0x168 is the offset from the DATA partition to the file base (masked with 0xFFFFFFFE).

Start	Length	Description
0x00	4	Magic ("DISA")
0x04	4	Unknown
0x08	8	Unknown
0x10	8	Offset to first "DIFI" blob table in DISA (usually 0x0200)
0x18	8	Offset to second "DIFI" blob table in DISA (usually 0x0330)
0x20	8	Size of the "DIFI" blobs table
0x28	8	Unknown (padding?)
0x30	8	Size of data to be hashed
0x38	8*6	Unknown
0x68	4	Active table (and the offset to the filebase)
0x6C	0x20	Hashes
0x8C	4*29	Unknown

struct disa_header {
        char magic[4];
        u8 unknown0[0xC];
        u64 first_difi_table_offset;
        u64 second_difi_table_offset;
        u64 table_size;
        u64 Padding;
        u64 hash_size;
        u8 unknown1[0x30];
        u32 active_table;               // and the offset to the filebase
        u8 hash[0x20];
        u8 unknown2[0x74];
} __attribute__((__packed__));

• The hash in the DISA blob hashes 'hash_size' bytes of the 'active_table'.

The DIFIs table @ 0x200 (into the image) is written twice, (Meaning, if there's 4 DIFI blobs then the table is 2 DIFIs long).

The second table is for backup. The active table is mentioned at 0x13C into the image (1=First table, other=Second Table)

DIFI

These 0x130 large blobs describe the partitions. Every DIFI blob describes a partition. In order to find the partitions, you will need the uint32_t at 0x9C into the DIFI block, and the uint32_t at 0xA4. The uint32_t at 0x9C describes the length of the hash table at the start of the partition, the uint32_t at 0xA4 is the length of the filesystem. Partitions are catted together, so after the end of one partition is the beginning of the next (on the next 0x1000 block).

Actually DIFI blobs are 0x12C large because the last 4 are not used and appear 0xFFFFFFFF at the encrypted image.

For most games there's only 1 partition (The SAVE partition) and some (like Asphalt 3D and Steel Diver) has 2 partitions.

• 2 Partitions means that the files inside the SAVE partition is on the other partition (we would call it DATA partition).

• No more than 2 partitions have been seen yet.

Start	Length	Description
0x00	4	Magic ("DIFI")
0x04	4	Unknown
0x08	8	Offset to "IVFC" blob in DIFI (usually 0x44)
0x10	8	Size of "IVFC" blob
0x18	8	Offset to "DPFS" blob in DIFI (usually 0xBC)
0x20	8	Size of "DPFS" blob
0x28	8	Offset to the hashes in DIFI (usually 0x010C)
0x30	8	Size of this hashes
0x38	8	Unknown
0x40	4	Unknown (0x00 filled)

IVFC

Start	Length	Description
0x00	4	Magic ("IVFC")
0x04	0x3C	Unknown
0x40	8	Hash Table Offset
0x48	8	Hash Table Length
0x50	8	Unknown (=12?)
0x58	8	FileSystem Offset
0x60	8	FileSystem Length
0x68	8	Hashed Block Length
0x70	8	Unknown (usually 0x78=120)

DPFS

Start	Length	Description
0x00	4	Magic ("DPFS")
0x04	0x3C	Unknown
0x40	8	Offset To Next Partition (or to the end of this partiton)
0x48	8	Unknown

• The u64 at 0x40 is an offset because if you summarize the hashtable's length and the partition's length you'll get sometimes less then this value. so it isn't the length of the total partition but an offset.

The SAVE partition

Savefiles are stored on the FLASH in a custom filesystem called SAVE. SAVE has a header which describes where the various bits of the filesystem live.

The first partition starts at 0x2000. The hashtable at the start of the partition describe each in-use block in the partition with a SHA256 of the 0x200 sized block.

• The first two hashes don't seem to be associated with any 0x200 block.

Finding the file system file base:

• If there's no DATA partiton the file base will be at the uint32 @ 0x58 into the SAVE header.
• Otherwise the file base will be at ('active_table' & 0xFFFFFFFE) into the DATA partition.

Finiding the file system table:

• If the uint32 @ 0x58 and uint32 @ 0x6C into the SAVE header aren't 0 then the table is at [@0x58] + [@0x6C]*0x200.
• Otherwise, (meaning the files are at another partition) the exact offset into the SAVE is @ 0x68.

Once you've found the FST, parsing it is fairly straightforward.

 struct fs_entry {
     u32 node_cnt;
     u8  filename[0x10];
     u32 index;
     u32 unk1; // magic?
     u32 block_offset;
     u32 file_size;
     u32 unk2;
     u32 unk3; // flags and/or date?
     u32 unk4;
 }

The first entry is the root directory, easily identifiable by the node_cnt being larger than 1. The node_cnt includes the root directory itself, so there are node_cnt - 1 files in the root directory. The entries that follow after the root directory are the actual files. Reading them out is as simple as taking the file base offset and adding (block_offset * 0x200) to it.

Here's a follow-up example from the Legend of Zelda: Ocarina of Time 3D:

//FST entry = SAVE base + File base + (FST offset * 0x200) + (FST entry # * 0x30)
//0x2600    = 0x2000    + 0x400     + (0x1        * 0x200) + (0x0         * 0x30)

00002600: 03000000 09000000 00000000 00000000  ................
00002610: 00000000 00000000 00000000 00000000  ................
00002620: 00000000 00000000 00000000 00000000  ................
00002630: 01000000 73797374 656D2E64 61740000  ....system.dat..
00002640: 00000000 00000000 D57B1100 02000000  ........Õ{......
00002650: 22000000 00000000 E8121500 00000000  ".......è.......
00002660: 01000000 73617665 30302E62 696E0000  ....save00.bin..
00002670: 00000000 01000000 69921100 03000000  ........i’......
00002680: DC140000 00000000 04000000 00000000  Ü...............

Example for a different file with different SAVE structure:

00002400 53415645 00000400 20000000 00000000 SAVE.... ....... //Save from Steel Diver
00002410 28030000 00000000 00020000 00000000 (...............
00002420 00000000 00020000 88000000 00000000 ................
00002430 03000000 00020000 94000000 00000000 ................
00002440 43000000 00020000 A0010000 00000000 C...............
00002450 28030000 00020000 00000000 00000000 (............... //[0x58] = 0 and 
00002460 28030000 00020000 E81A0000 00000000 (............... //[0x6C] = 0, but
00002470 00000000 00020000 381B0000 00000000 ........8....... //On offset 0x68 There's an exact offset to the FST 
00002480 40000000 00020000 01000000 00000000 @............... //meaning a uint32_t at 0x68 into the SAVE struct
00002490 00000000 00000000 00000000 02000000 ................

00003F30 00000000 00000000 04000000 41000000 ............A... // first fs_entry '04 00 00 00'
00003F40 00000000 00000000 00000000 00000000 ................ //exectly 0x1B38 from the save header struct
00003F50 00000000 00000000 00000000 00000000 ................
00003F60 00000000 00000000 01000000 67686F73 ............ghos
00003F70 742E7374 30370000 00000000 00000000 t.st07..........
00003F80 D57B1100 00000000 7E290000 00000000 .{......~)......
00003F90 00000000 00000000 01000000 73617665 ............save
00003FA0 2E737562 00000000 00000000 01000000 .sub............
00003FB0 D57B1100 15000000 9C090000 00000000 .{..............
00003FC0 00000000 00000000 01000000 73617665 ............save
00003FD0 2E706572 69730000 00000000 02000000 .peris..........
00003FE0 D57B1100 1A000000 29070000 00000000 .{......).......
00003FF0 00000000 00000000 00000000 00000000 ................

known struct until now:

struct save_header {
        char magic[4];           //'SAVE'
        u8 unknown0[0x54];
        u32 file_base_offset;
        u8 unknown1[0x10];
        u32 fst_block_offset;    //FST is in [file_base_offset] * 0x200 + [fst_block_offset]
        u8 unknown2[8];          //or (if no filebase)
        uint32 fst_exact_offset; //The exact offset from the header start
}

Initialization

When a save EEPROM contains all xFFFF blocks it's assumed uninitialized by the game cartridges and it initializes default data in place, without prompting the user.

Japanese