SaveDataFiler

The SaveDataFiler binary is in the following location in the CTR-SDK.

$CTRSDK_ROOT/tools/TargetTools/CTR-TS/Release/SaveDataFiler.cia

Copy the above binary to an SD Card, and import it from DevMenu to the system's NAND memory. After that, it can be launched from the HOME Menu. (It can also be launched from DevMenu.)

Note 1: Handling Extended Save Data

The expanded save data specifications only allow access from the system that created the data. SaveDataFiler is no exception; it cannot access expanded save data that was created on another system. If you want to use expanded save data on another system, you must first export it to an SD Card (see Writing to SD Cards), and then import it once more to the system that you want to access it from. In other words, you must import the SaveDataFiler on both the original system, and the system you want to access the data from.

Note 2: Handling Save Data in Backup Memory

The save-data specifications prevent access if there is badly formatted ROM data (data that is not recognized as a valid CTR application) in the ROM area of the CTR card (or emulation memory). This applies to the emulation memory immediately after the debugger is powered on, as well as to CTR cards to which a System Updater has been written.


It also may not be possible to correctly import or export save data if the application written to the CTR card (or loaded into emulation memory) is different from the application that created the save data.
In other words, the save data may not be exported correctly if the procedure below is followed. (The same applies to importing data.)

1. Create save data with application A.
2. Write the .cci file for application B to the CTR card.
3. Launch SaveDataFiler and export the save data.

Due to the two reasons above, make sure that the CCI file of the application that created the save data is written to the CTR card (or loaded into emulation memory) when importing or exporting that save data.

You can also launch SaveDataFiler from a CTR card (or emulation memory).

$CTRSDK_ROOT/tools/TargetTools/CTR-TS/Release/SaveDataFiler.csu

Use the debugger to write the binary above to the CTR card (or to load it into emulation memory). You can also start it from the HOME or Test Menu.

Note: Handling Save Data in Backup Memory

Because SaveDataFiler itself does not store save data, it cannot access backup devices when it is launched from a CTR card (or emulation memory). An error such as the following is displayed on the screens.

<Upper Screen>

File Type    : broken user save data

Level  : -7
Summary: 9
Module : 17
Desc   : 230

<Lower Screen>

CTR Card -- broken --

Import the SaveDataFiler into system NAND memory, and use this information to import and export user save data to and from backup memory.

You can use SaveDataFiler to write save data and expanded save data to SD Cards.
The written data is saved to SD Cards in the following location. It can then be edited from a PC or other device.

sdmc:/filer/
        +--- UserSaveData/
        |       +--- <The date and time saved>/
        |                +--- <Unique ID>/         ←Data is saved below here.
        |                +--- <Unique ID& gt.dat       ← File that contains format parameters.
        +--- ExtData/
        |       +--- <The date and time saved>/
        |       +--- <expanded save data number>/      ←Data is saved below here.
        |       +--- <expanded save data number>.dat   ←File storing format parameters.
        +--- SecureValue/
                +--- <The date and time saved>/
                         +--- <expanded save data number>/      ←Data is saved below here.
                         +--- SecureValue.dat       ←File that stores format parameters.

Data saved in the previous locations can be restored from the SD Tab.

The goal of destroying files is to put them in a state where the nn::fs::ResultVerificationFailed error is returned when they are loaded using functions from the FS library. You can use this to test error processing for files that are damaged when a card is removed during a write or a when a file is illegally spoofed.
There are two features for destroying files:

- Thoroughly destroy the selected files (R+Y)

Can always destroy the selected files.

This action may destroy other files or directories as well.

- Only destroy the selected files (L+Y)

Not supported for redundant save data.

This may fail to destroy the selected files.

It will never affect other files or directories, regardless of whether the destruction is successful.

If destruction is successful, an error appears in the file list. (See User Tab)

You can write rollback prevention values to the SD Card and delete them for debugging purposes.

The following three features are related to rollback prevention values.

・ Write the selected title's rollback prevention values to the SD Card (R+Y)

Writes 64 bit values within the system save region.

・ Load the selected title's rollback prevention values from the SD Card (SD tab)

Overwrites 64 bit values within the system save region with content saved on SD Card.

・ Delete selected title's rollback prevention values (R+X)

Deletes 64 bit values within the system save region.

Usage of rollback prevention values will be different for each application.
When debugging applications that use rollback prevention values, save data and rollback prevention values must be handled as a pair.

When this tab is selected, a list showing the CTR Card and download applications appears.
In addition to "CTR Card," this list shows the unique IDs of the download applications imported to the SD Card.

CTR Card
F7FFF
FFFFF
   :

If an archive is corrupted, the corresponding Result value appears on the upper screen when it is mounted.

When an item is selected from the list, the content of its save data is displayed on the lower screen.

../
Dir1/
Dir2/
File1
File2 : Read Error (0-512)
File3
  :

When an error has occurred during file operations, such as a damaged file, the filename is displayed in red. To display the corresponding Result value on the upper screen, align the cursor with the filename.

In addition, the function that was called when the error occurred is displayed next to the filename.

View	Description
Open Error	nn::fs::FileStream::TryInitialize returned an error. There was a failure in opening the file.
Read Error	nn::fs::FileStream::TryRead returned an error. There was a failure when reading the file. At the same time, the byte at which the read error occurred in the file is also displayed. SaveDataFiler reads in units of 1 MB, so the actual region where the error occurs may be smaller than this. This may also appear when there is an unwritten area in the file. See the note to nn::fs::ResultVerificationFailed for details.
Size Error	nn::fs::FileStream::TryGetSize returned an error. There was a failure in getting the file size (metadata). However, if the system fails to get the metadata, it will also fail to open the file. Thus, an Open Error will generally be displayed.

When this tab is selected, the expanded save data on the SD Card is displayed in a list. The displayed numbers are the expanded save data numbers.

00000001
00000002  -- broken --
00000003
   :

When an archive is corrupt (when the nn::fs::MountExtSaveData function returns an error), the number is displayed in red. When the cursor is aligned above the filename, the result value is displayed in the upper screen.

When an archive is selected from the list, the content of the expanded save data are displayed. The displayed content is the same as for the User Tab.