3DS:Movable Moveover/Manual

This article is for transferring data between systems without doing a system transfer, and usually should only be done if the console you are transferring from is nonfunctional or the source console is not in your possession.
If you do not have a specific reason to follow this guide (i.e. both consoles are usable), do a System Transfer instead.

Required Reading (Do NOT ignore)

This guide can potentially cause unexpected results if done wrong. Please ensure you read the steps carefully to prevent these unexpected results from happening.
Additionally, ensure you have read the following warnings to have a full understanding of the potential risks of this guide.

Do NOT use a movable.sed from Bruteforce Movable (in general, but especially not for this guide). Doing so may cause other issues with the system, and will result in a guaranteed brick if you uninstall CFW while using that movable. Always keep a backup of your original movable.sed if you do so.

Uninstalling CFW without undoing the moveover done in this guide WILL brick your console, as we have tampered with console-unique files which can have dangerous effects if stock (native.firm) is booted. This guide has you extract the original versions of those files so you are able to undo it if you need to - do not lose those files.

Any games/savedata/themes/DSiWare that was already on the destination console's SD card will become inaccessible once the guide is completed - only data transferred over from the source console will be usable. To access the destination console's data again, you must undo the moveover.

If the above two warnings will cause issues for you and you are willing to take extra steps to avoid them, you can instead use ninfs to merge the source console's encrypted files onto the destination console, then rebuild title.db to make any merged games/apps appear. However, note that even this method will not bypass the issues of using a Bruteforce Movable movable.sed.

If you are confused in any way, join the Nintendo Homebrew Discord and ask for help in the 3DS assistance channels.

What you need

• Two 3DS consoles, both modded with Luma3DS CFW
  • These will be referred to as the source console and destination console for this guide's purposes
  • If either console is not currently modded, stop and mod it with our custom firmware installation guide first
• The source console's essential.exefs, such as the one created in our guide's Finalizing Setup
  • If you already have the source console's movable.sed outside of a .exefs file, you can use that directly
• The latest version of faketik (the .3dsx file)
• The latest version of GodMode9 (the GodMode9 .zip file)

Prep Work

Follow this section on the destination console only.

1. Power off your console
2. Insert your SD card into your computer
3. Copy GodMode9.firm from the GodMode9 .zip to the /luma/payloads/ folder on your SD card
4. Copy the gm9 folder from the GodMode9 .zip to the root of your SD card
5. Create a folder named 3ds on the root of your SD card if it does not already exist
   • This folder stores homebrew applications and data; it is different from the Nintendo 3DS folder that the console automatically generates
6. Copy faketik.3dsx to the 3ds folder on the root of your SD card
7. Copy the source console's essential.exefs to the root of your SD card and rename it to old-essential.exefs
   • If you have the source console's movable.sed already, you can copy that to the root of the SD card instead
8. Reinsert your SD card into your console

Backing up the destination console's essential.exefs

If you do not back up the destination console's essential.exefs before following the remainder of the guide, you will be unable to undo the moveover - which means that console will never be able to uninstall custom firmware.

1. Press and hold START, and while holding START, power on your console. This will launch GodMode9
2. Enter the [S:] SYSNAND VIRTUAL drive
3. Press A on essential.exefs to select it
4. Press A on Copy to 0:/gm9/out
   • If you see Destination already exists, press A on Overwrite file(s)
5. Press A to continue
6. Press B until you return to the drive list

The destination console's original essential.exefs file will be in /gm9/out folder on its SD card. It is highly recommended to back up this file to a safe location.

Extracting the movable file

1. Enter the [0:] SDCARD drive
2. Select the old-essential.exefs, and press A on Mount as EXEFS image
   • If you instead copied movable.sed to the SD root, press Y on that file and skip to the next section
3. Look for a file named movable inside the old-essential.exefs image mount
4. Press Y on movable, then proceed to the next section

Replacing the movable.sed

1. Press B to return to the drive list
2. Enter the [1:] SYSNAND CTRNAND drive, then enter the private folder
3. Press X on the movable.sed file and press A
4. Unlock Writing to SysNAND (lvl1) when prompted, then input the given key combo
5. Press Y to paste from the clipboard, then rename the file to movable.sed if it is not named that already
6. Press B until you have returned to the drive list, press R + A on the [1:] SYSNAND CTRNAND drive, and then select Fix CMACs for drive
7. Once this finishes, press START to reboot your console
8. Your console will act like it has just been formatted - this is supposed to happen. Proceed through initial setup and get to the HOME Menu

Getting your apps back

1. Launch the Download Play application
2. Wait until you see the two buttons
   • Do not press either of the buttons
3. Press L + D-PAD DOWN + SELECT at the same time to open the Rosalina menu
4. Select Miscellaneous options
5. Select Switch the hb. title to the current app.
6. Press B to continue
7. Press B to return to the Rosalina main menu
8. Press B to exit the Rosalina menu
9. Press HOME, then close Download Play
10. Relaunch the Download Play application
11. Your console should load the Homebrew Launcher
12. Launch faketik from the list of homebrew
13. Wait until the process is completed
14. Press START to exit
15. Reboot your console

The moveover is complete. Congratulations for performing a complex procedure.