3DS:Cleaninty

cleaninty is a PC tool used to communicate with Nintendo's SOAP servers. For a 3DS, these servers deal with managing eShop accounts, downloading eShop titles, and system transfers.

Features
When given the unique data ( and either   or the serial number & eShop region data) of a console and the required basic constants, cleaninty can act as the console it's given and do the following:


 * : Compiles the console's data into a single JSON file. This JSON is required for all other commands except.
 * : Obtains the console's eShop status and any titles attached to its eShop account, then updates the JSON file if any differences in the data are found.
 * : Moves the eShop titles of the source console to the target console. This is the secondary part of what is known informally as a "SOAP Transfer".
 * Using this command will trigger a 7-day cooldown on system transfers for both consoles, the same as a 'regular' transfer.
 * : (Still experimental. Use with caution.) Moves only the NNIDs of the source console to the target console. This is not affected by transfer cooldowns and does not trigger one.
 * : Provides the date&time of the given console's last system transfer, the number of transfers it has ever done, and the time at which the current transfer cooldown will expire if there is one.
 * : Obtains the console's  from the SOAP servers, if the servers have a stored copy.
 * : Uploads the JSON's stored  to the SOAP servers. This will overwrite the current stored movable.
 * : Tries to recover a console's  from only its raw   and eShop region data.
 * : Deletes the target console's eShop account.
 * : Deletes the target console's eShop account and attempts to create a new one in the entered region. This is the main part of a "SOAP Transfer" and is what grants eShop access again.
 * If this fails,  any conflicting titles off of the target console first.
 * / / : Lists all owned eShop tickets / downloads all tickets / downloads the titles attached to all tickets, respectively, from the given console's eShop account.

Installation
Instructions for installation & setup are, but the installation instructions may need to be interpreted for your OS.

A guide to legally deriving the AES Constant, "C", can be found on this page.

Windows
Don't bother trying to use cleaninty through Command Prompt or PowerShell. Windows has OpenSSL disabled in its, but cleaninty requires OpenSSL to function. Working around this issue manually is obnoxious and not worth the time spent.

Instead, install msys2 and install cleaninty from within there.

To install cleaninty once msys2 is installed, open the terminal  that is inside the msys2 installation folder, then run the following two commands one at a time:

Once this is completed, from here on out you will need to open the terminal  to use cleaninty.

macOS and Linux
First, ensure you have a python version of 3.7 or newer. You can check if your python version is new enough by opening a terminal and running the command.

For the method that involves, you can follow the instructions on the GitHub page with no modifications.

For the method that involves, it is recommended to obtain the source code via the command. This will guarantee the files are in the correct layout.

Usage
There is no graphical interface for cleaninty. All commands are ran through the command line.

Command line
The commands are the same on all operating systems. Run  for information on an individual command's syntax.

As an example, the minimum list of commands needed to set up two consoles' data and perform a SOAP transfer between them would be as follows:
 * 1) * The CheckReg commands are not necessary if you are already certain the donor and target are in the same region.
 * 2) * If this succeeds, stop here. The next two commands are only needed if this one fails.
 * 1) * The CheckReg commands are not necessary if you are already certain the donor and target are in the same region.
 * 2) * If this succeeds, stop here. The next two commands are only needed if this one fails.
 * 1) * The CheckReg commands are not necessary if you are already certain the donor and target are in the same region.
 * 2) * If this succeeds, stop here. The next two commands are only needed if this one fails.
 * 1) * If this succeeds, stop here. The next two commands are only needed if this one fails.