Latest revision as of 21:32, 24 September 2024

3DS:MMM

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 three warnings to have a full understanding of the potential risks of this guide.

Do NOT use a movable.sed from Bruteforce Movable as your system 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.

If you have already done this guide at any time before the date 2024-08-11, then uninstalling CFW will brick your console, as FixupMovable (which is done by the script) is required to avoid crashing on stock firmware.
If this applies to you, you can fix stock firmware by booting into GodMode9, copying your movable.sed from 1:/private to the destination console's SD root, copying MovableMoveover.gm9 to the /gm9/scripts/ folder on the SD card, and then doing the instructions from Section II onward on the destination console only.

Any games/savedata/themes/DSiWare that was already on the destination console's SD card will become inaccessible once the guide is completed - you will only be able to use the data transferred over from the source console. To access the destination console's data again, you must undo the moveover.
The script extracts the original versions of those files so you are able to undo it if you need to - do not lose those files.

If the above warning will cause issues for you and you are willing to take extra steps to avoid it, 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
- 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 source console's Nintendo 3DS folder
- this should contain the data you are trying to transfer
The latest version of faketik (the .3dsx file)
The latest version of GodMode9 (the GodMode9 .zip file)
The latest version of MovableMoveover.gm9
To download, right-click/long-press the page and select Save page as... or similar, then rename the downloaded file to MovableMoveover.gm9 if it is not already named that

Instructions

Section I - Prep Work

Follow these instructions on the destination console only.

Power off your console and insert your SD card into your computer
Copy GodMode9.firm from the GodMode9 .zip to the /luma/payloads/ folder on your SD card
Copy the gm9 folder from the GodMode9 .zip to the root of your SD card
Copy MovableMoveover.gm9 to the /gm9/scripts/ folder on your SD card
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
Copy faketik.3dsx to the 3ds folder on the root of your SD card
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 in raw form, you can copy that file to the root of the SD card instead
Copy the source console's Nintendo 3DS folder the the root of your SD card
Reinsert your SD card into your console

Section II - Setup Script

Hold Start, and while holding Start, power on your console
Your console will have booted into GodMode9
If you are prompted to create an essential files backup, press A to do so, then press A to continue once it has completed
If you are prompted to fix the RTC date&time, press A to do so, then set the date and time, then press A to continue
Press Home to bring up the action menu
Select “Scripts…”
Select “MovableMoveover”
Follow the prompts in the script, answering any questions that you are asked
Once the script completes your console will have rebooted
Your console may act like it has just been formatted - this does not mean your data has been lost. If it does this, proceed normally through initial setup and get to the HOME Menu

The destination console's original essential.exefs and movable.sed files will be in sd:/gm9/out/MMM_Backup on its SD card. It is highly recommended to back up these files to a safe location.

Section III - Reinstating Apps

Launch the Download Play application
Wait until you see the two buttons
- Do not press either of the buttons
Press L+↓+SELECT at the same time to open the Rosalina menu
Select Miscellaneous options
Select Switch the hb. title to the current app.
Press B to continue
Press B to return to the Rosalina main menu
Press B to exit the Rosalina menu
Press HOME, then close Download Play
Relaunch the Download Play application
Your console should load the Homebrew Launcher
Launch faketik from the list of homebrew
Wait until the process is completed
Press START to exit
Reboot your console

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

@@ Line 10: / Line 10: @@
 {{critical|text=Do '''NOT''' use a <code>movable.sed</code> from Bruteforce Movable as your system 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 <code>movable.sed</code> if you do so.}}
-{{warning|text=If you have already done this guide at any time before the date 2024-08-11, then uninstalling CFW will brick your console, as FixupMovable is required to avoid crashing on stock firmware.
+{{warning|text=If you have already done this guide at any time before the date 2024-08-11, then uninstalling CFW will brick your console, as FixupMovable (which is done by the script) is required to avoid crashing on stock firmware.
-<br>If this applies to you, you can fix stock firmware by booting into [[3DS:GodMode9|GodMode9]], copying your <code>movable.sed</code> from <code>1:/private</code> to the '''destination console''''s SD root, copying <code>FixupMovable.py</code> to the SD root, and then doing the instructions from Section IV onward on the '''destination console''' only.}}
+<br>If this applies to you, you can fix stock firmware by booting into [[3DS:GodMode9|GodMode9]], copying your <code>movable.sed</code> from <code>1:/private</code> to the '''destination console''''s SD root, copying <code>MovableMoveover.gm9</code> to the <code>/gm9/scripts/</code> folder on the SD card, and then doing the instructions from Section II onward on the '''destination console''' only.}}
-{{warning|text=Any games/savedata/themes/DSiWare that was already on the destination console's SD card will become inaccessible once the guide is completed - you will only be able to use the data transferred over from the source console. To access the destination console's data again, you must undo the moveover by replacing.
+{{warning|text=Any games/savedata/themes/DSiWare that was already on the destination console's SD card will become inaccessible once the guide is completed - you will only be able to use the data transferred over from the source console. To access the destination console's data again, you must undo the moveover.
-<br>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.''}}
+<br>The script extracts the original versions of those files so you are able to undo it if you need to - ''do not lose those files.''}}
 {{info|If the above warning will cause issues for you and you are willing to take extra steps to avoid it, you can instead use [[ninfs]] to merge the source console's encrypted files onto the destination console, then [[3DS:Rebuild Title Database|rebuild title.db]] to make any merged games/apps appear.<br>
@@ Line 26: / Line 26: @@
 ** 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 [[3dsguide:|our custom firmware installation guide]] first
-* The '''source console''''s <code>essential.exefs</code>, such as the one created in [[3dsguide:finalizing-setup|our guide's Finalizing Setup]]
+* The '''source console's''' <code>essential.exefs</code>, such as the one created in [[3dsguide:finalizing-setup|our guide's Finalizing Setup]]
 ** If you already have the '''source console's''' <code>movable.sed</code> outside of a <code>.exefs</code> file, you can use that directly
-* A version of [https://www.python.org/downloads/ Python 3]
+* The '''source console's''' <code>Nintendo 3DS</code> folder
+**this should contain the data you are trying to transfer
 * The latest version of {{GitHub|/ihaveamac/faketik/releases/latest|faketik}} (the <code>.3dsx</code> file)
 * The latest version of {{GitHub|d0k3/GodMode9/releases/latest|GodMode9}} (the GodMode9 <code>.zip</code> file)
-* The latest version of {{GitHub|fox8091/FixupMovable/releases/latest|FixupMovable}} (the <code>FixupMovable.py</code> file)
+* The latest version of [https://gist.githubusercontent.com/ItsCrocoSwine/09ada32bdd6ab53dd061b56e3d2b661e/raw/MovableMoveover.gm9 MovableMoveover.gm9]
+* To download, right-click/long-press the page and select <code>Save page as...</code> or similar, then rename the downloaded file to <code>MovableMoveover.gm9</code> if it is not already named that
@@ Line 43: / Line 45: @@
 # Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the <code>/luma/payloads/</code> folder on your SD card
 # Copy the <code>gm9</code> folder from the GodMode9 <code>.zip</code> to the root of your SD card
-# Copy <code>FixupMovable.py</code> to the root of your SD card
+# Copy <code>MovableMoveover.gm9</code> to the <code>/gm9/scripts/</code> folder on your SD card
 # Create a folder named <code>3ds</code> 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 <code>Nintendo 3DS</code> folder that the console automatically generates
 # Copy <code>faketik.3dsx</code> to the <code>3ds</code> folder on the root of your SD card
-# Copy the '''source console''''s <code>essential.exefs</code> to the root of your SD card and rename it to <code>old-essential.exefs</code>
+# Copy the '''source console's''' <code>essential.exefs</code> to the root of your SD card and rename it to <code>old-essential.exefs</code>
 #* If you have the '''source console''''s <code>movable.sed</code> already in raw form, you can copy that file to the root of the SD card instead
+# Copy the '''source console's''' <code>Nintendo 3DS</code> folder the the root of your SD card
 # Reinsert your SD card into your console
-=== Section II - Backing up essential.exefs ===
+=== Section II - Setup Script ===
+# Hold {{B|Start}}, and while holding {{B|Start}}, power on your console
-{{warning|text=If you skip this section and do not have any other backups, then you will be unable to undo the moveover and the '''destination console''''s <code>movable.sed</code> will be permanently lost.}}
+# Your console will have booted into GodMode9
+# If you are prompted to create an essential files backup, press {{B|A}} to do so, then press {{B|A}} to continue once it has completed
-# Press and hold {{B|START}}, and while holding {{B|START}}, power on your console. This will launch GodMode9
+# If you are prompted to fix the RTC date&time, press {{B|A}} to do so, then set the date and time, then press {{B|A}} to continue
-# Enter the <code>[S:] SYSNAND VIRTUAL</code> drive
+# Press {{B|Home}} to bring up the action menu
-# Press {{B|A}} on <code>essential.exefs</code> to select it
+# Select “Scripts…”
-# Press {{B|A}} on '''Copy to 0:/gm9/out'''
+# Select “MovableMoveover”
-#* If you see '''Destination already exists''', press {{B|A}} on '''Overwrite file(s)'''
+# Follow the prompts in the script, answering any questions that you are asked
-# Press {{B|A}} to continue
+# Once the script completes your console will have rebooted
-# Press {{B|B}} until you return to the drive list
+# Your console may act like it has just been formatted - this does not mean your data has been lost. If it does this, proceed normally through initial setup and get to the HOME Menu
-{{info|text=The destination console's original <code>essential.exefs</code> file will be in <code>sd:/gm9/out</code> on its SD card. It is highly recommended to back up this file to a safe location.}}
-=== Section III - Extracting movable.sed ===
-# Navigate into the drive <code>[0:] SDCARD</code>
-# Press {{B|A}} on <code>old-essential.exefs</code>, and select '''Mount as EXEFS image'''
-#* If you instead copied <code>movable.sed</code> to the SD root, press {{B|Y}} on that file and skip to the next section
-# Find the file named <code>movable</code> inside the image mount, and press {{B|Y}} to copy it to the clipboard
-# Press {{B|B}} to exit from the image mount, then navigate back into the drive <code>[0:] SDCARD</code>
-# Press {{B|Y}} to paste <code>movable</code> in the root of the SD card
-# Press {{B|R|START}} to power off the console
-=== Section IV - FixupMovable ===
-{{info|If you are not on Windows, replace <code>py -3</code> with <code>python3</code> in all commands.}}
-{{warning|The commands in this section are case-sensitive. Enter them exactly as written, or there may be unintended consequences.}}
-# Insert the console's SD card into your PC
-# Open a file explorer window and navigate to the SD card's root
-# Rename <code>movable</code> to <code>movable.sed</code>
-# Hold {{B|SHIFT}} and right-click anywhere in the folder's empty space, then click the option that opens a terminal, PowerShell, or Command Prompt
-# In this new window, enter the following commands one at a time:
-## <code>py -3 -V</code>
-##* If this does not print the Python version, it is either not installed correctly, or the wrong command was used. Please read the note above.
-## <code>py -3 FixupMovable.py movable.sed</code>
-##* After this, <code>movable.sed</code> should be exactly 288 bytes in size. If it isn't, try the command again
-# Eject the SD card and reinsert it into the console
-=== Section V - Replacing movable.sed ===
+{{info|text=The destination console's original <code>essential.exefs</code> and <code>movable.sed</code> files will be in <code>sd:/gm9/out/MMM_Backup</code> on its SD card. It is highly recommended to back up these files to a safe location.}}
-# Press and hold {{B|START}}, and while holding {{B|START}}, power on your console. This will launch GodMode9
-# Navigate into the drive <code>[0:] SDCARD</code>
-# Press {{B|Y}} to copy <code>movable.sed</code> to the clipboard
-# Press {{B|B}} to return to the drive list
-# Navigate into the drive <code>[1:] SYSNAND CTRNAND</code>, then enter the <code>private</code> folder
-# Press {{B|X}} on <code>movable.sed</code> and press {{B|A}} to confirm deletion
-# Unlock '''Writing to SysNAND (lvl1)''' when prompted, then input the given key combo
-# Press {{B|Y}} to paste the new <code>movable.sed</code> from the clipboard
-# Press {{B|B}} until you have returned to the drive list
-# Press {{B|R|A}} on the drive <code>[1:] SYSNAND CTRNAND</code> and select '''Fix CMACs for drive'''
-# Once this finishes, press {{B|START}} to reboot your console
-# Your console may act like it has just been formatted - this does not mean your data has been lost. If it does this, proceed normally through initial setup and get to the HOME Menu
-=== Section VI - Reinstating Apps ===
+=== Section III - Reinstating Apps ===
 # Launch the '''Download Play''' application