The developer Eliboa has released a new tool to facilitate the backup of the Nintendo Switch console Nand in NxNandManager with version 4.0 BETA. NxNandManager is a command line utility (and GUI) for Windows 7 and 10, whose main purpose is copy the contents of Nintendo Switch (full NAND or specific partition) from / to a file or physical drive.
- Full NAND backup and restore (BOOT0, BOOT1, RAWNAND)
- Copy to / from specific partition (RAWNAND)
- Dump integrity verification (MD5)
- Enable / Disable Automatic RCM (BOOT0)
All dumps performed with Hekate are supported by NxNandManager (and vice versa).
NxNM also supports split dumps (such as SX operating system NAND dumps (emu)).
The names of the divided files should be:
Set the first divided file as input
How to mount and open your Nintendo Switch NAND?
- Use memloader v3 to mount eMMC on your computer ( TegraRcmGUI provides an easy way to do it).
- Open NxNandManager (CLI: add topic – list to list all available physical drives, GUI: File> Open Drive).
- Select the mounted unit. Now you can perform backup / restore operations.
I use CLI
NxNandManager.exe [--list] [--info] [--enable_autoRCM] [--disable_autoRCM] -i inputFilename|\\.\PhysicalDriveX [-o outputFilename|\\.\PhysicalDriveX] [-part=nxPartitionName] [lFlags]
|-gui||Launch the graphical user interface (optional)||
|-Information||Displays detailed information about the input (-i) and output (-o) streams||
|-list||List compatible physical drives||
|-enable_autoRCM||Enable auto-RCM for the BOOT0 partition indicated with -i param||
|-disable_autoRCM||Disables auto-RCM for the BOOT0 partition indicated with -i param||
|-I||Path to insert the file or physical drive||
|-or||Path to output file or physical drive||
|-part =||Copy to / from a specific NAND partition (optional)||
|BYPASS_MD5SUM||Used to bypass all checks MD5
Dump / Restore is faster but less secure
|FORCE||The program will never ask for user confirmation|
Download the complete NAND on file
- From physical disk (first you need to mount NX eMMC with memloader (via TegraRcmGUI for ex):
.\NxNandManager.exe -i \\.\PhysicalDrive3 -o "C:\Users\Public\NAND dump\rawnand.bin"
- From the existing dump file:
.\NxNandManager.exe -i "C:\Users\Public\NAND dump\rawnand.bin" -o D:\rawnand2.bin
Dump specific partitions to file
- Dump the SYSTEM partition from the physical drive:
.\NxNandManager.exe -i \\.\PhysicalDrive3 -o "C:\Users\Public\NAND dump\SYSTEM.bin" -part=SYSTEM
- Extract the PRODINFOF partition from the existing dump file:
.\NxNandManager.exe -i "C:\Users\Public\NAND dump\rawnand.bin" -o D:\PRODINFOF.bin -part=PRODINFOF
Reset NAND dump
- Restore entire raw NAND memory to physical drive:
.\NxNandManager.exe -i "C:\Users\Public\NAND dump\rawnand.bin" -o \\.\PhysicalDrive3
- Restore raw NAND memory split into physical drive:
.\NxNandManager.exe -i "C:\Users\Public\NAND dump\full00.bin" -o \\.\PhysicalDrive3
- Restore specific partition to physical disk:
.\NxNandManager.exe -i "C:\Users\Public\NAND dump\rawnand.bin" -o \\.\PhysicalDrive3 -part=PRODINFO
.\NxNandManager.exe -i "C:\Users\Public\NAND dump\PRODINFO" -o \\.\PhysicalDrive3 -part=PRODINFO
Copy the partition from the file to the rawNand file
- Copy specific partition from rawNand file:
.\NxNandManager.exe -i "C:\Users\Public\NAND dump\rawnand.bin" -o "C:\Users\Public\NAND dump\rawnand2.bin" -part=BCPKG2-1-Normal-Main
- Copy specific partition from partition file:
.\NxNandManager.exe -i "C:\Users\Public\NAND dump\BCPKG2-1-Normal-Main" -o "C:\Users\Public\NAND dump\rawnand2.bin" -part=BCPKG2-1-Normal-Main
- New GUI layout
- New “advanced copy” function (zero passthrough, split output, zip output, etc.)
- The new “Emunand Creation Tool” (GUI only) provides an easy way to create a file based emuNAND or raw file based emuNAND on a micro SD card. NB: before you can launch the tool from the Options menu, you will need to open a valid RAWNAND or FULL NAND image.
- GUI: you can now choose to open any emuMMC partition, in case of multiple emuMMC on the same micro SD card (Open Drive, CTRL + D)
- many corrections and improvements.
PS: For personal reasons, I will have less time in the future to work on this project. You will need to be patient for the next version or error correction.
-dargument to decrypt,
Keys can be supplied
-keysetfrom the argument to the keyset file name.
The program can analyze keyset files created with biskeydump or lockpick:
BIS Key 0 (crypt): <16-byte hex key> BIS Key 0 (tweak): <16-byte hex key> ...
bis_key_00 = <32-byte hex key> bis_key_01 = <32-byte hex key> ...
Decipher complete rawn:
NxNandManager.exe -i rawnand.bin -o rawnand.dec -d -keyset keys.dat
Decrypting the single partition file:
NxNandManager.exe -i PRODINFO -o PRODINFO.dec -d -keyset keys.dat
Encrypt single partition files:
NxNandManager.exe -i PRODINFO.dec -o PRODINFO.enc -e -keyset keys.dat
Decrypt and restore a single partition file on the physical drive
NxNandManager.exe -i PRODINFO.dec -o \\.\PhysicalDrive3 -part=PRODINFO -e -keyset keys.dat
Encrypt and restore full rawnand
NxNandManager.exe -i rawnand.dec -o \\.\PhysicalDrive3 -e -keyset keys.dat
The GUI has been updated to support cryptographic operations.
Keys can be added via the “Configure keyset” item in the “Options” menu
An “incognito” option has been implemented. As the incognito of blawar does, it will erase all unique console IDs and certificates from CAL0. It can be useful because Atmosphere prevents writing to CAL0.
The program will need two keys to apply the unknown on encrypted files / drives
Using the CLI: to apply the unknown, use the
--incognitoargument (applies to the
-itype of input: RAWNAND or PRODINFO). For example :
NxNandManager.exe --incognito -i rawnand.bin -d -keyset keys.dat
GUI: use the appropriate item in the “Options” menu
- When the keys are provided or if the content is already decrypted, the program can retrieve additional information (CLI :,
--infoGUI: File> Properties)
- ExFat firmware and driver version (based on the names of the .nca and SYSTEM files, exactly like FVI , or from the journal / play reports in SYSTEM)
- Serial number (from PRODINFO or journal in SYSTEM)
- Last boot time (the
SYSTEM/save/8000000000000060same way FVI does)
- The bootloader version is now retrieved from BOOT0
- The program prevents the system from going into sleep mode when copying is in progress.