Your IP address will be publicly visible if you make any edits.
3DS:Recover movable.sed
From Hacks Guide Wiki
More actions
Revision as of 00:00, 9 April 2023 by StarlitSkies(talk | contribs)(guide to obtaining a nonfunctional console's movable.sed, including through cleaninty if no backups are available)
If you require a console's movable.sed for some purpose but the console is not usable enough to obtain it directly, there are multiple potential methods to obtain the movable.sed in a usable format.
Ensure the Yes/No prompts are answered correctly before you read the solution the page returns. The solution changes drastically based on what you have available.
Instructions
Do you have a backup of the console, either essentials.exefs or a NAND backup (a name in the format of <date>_<serialnumber>_sysnand_###.bin)?
These files may be found in sd:gm9/out on the console's SD card, or on your PC in a place you keep backups.
Do you have access to a 3DS that can launch GodMode9?
Solution:
Copy your backup onto the 3DS that can access GodMode9, in the folder sd:/gm9/out.
Boot into GodMode9 (hold START while powering on), go into the SDCARD drive, then into the gm9/out folder.
Select the backup file and choose _____ image options..., then Mount image to drive. It will ask whether to enter the mount. Press A.
Select the movable.sed and choose to Copy to 0:/gm9/out. If it asks to overwrite a file, let it overwrite.
For an essentials.exefs, the movable that is immediately visible is the correct file.
For a NAND backup, the movable.sed inside the private folder is the correct file.
Press B until you have returned to the drive list, press R+X to unmount the image, and then power off. movable.sed will be in the folder gm9/out on the SD card.
Solution:
You will need to use ninfs to mount the backup on a PC and then pull the movable.sed out of the mount.
Ensure you have a copy of the file boot9.bin, as ninfs requires it to work. This file can be obtained through fastboot3DS or GodMode9 on any working 3DS that has CFW installed, or from the folder sd:/luma/backups on the SD card of a console that has previously been modded.
Do you have the console's otp.bin and know both its serial number & eShop region?
OTP: otp.bin may be found in sd:/luma/backups or sd:/gm9/out on the console's SD card, and can be dumped through GodMode9 or fastboot3DS even if most of the console is unusuable. Serial Number: The serial number can be found on the back side of the 3DS, except on a 2DS XL where it will be under the game card/SD card slot's cover. If the serial is not immediately visible, it may be under the backplate or under the battery. However, note that if the console's motherboard has been swapped at any point, this serial is likely to be incorrect. eShop Region: If you have never done a SOAP transfer before and your serial is accurate to your current motherboard, your console's eShop region will match its serial number. You can check what region this means on 3dbrew's serials page.
Solution:
You will need to install cleaninty. Once all constants are set up, attempt to run RecoverIVS and/or GetIVS. If the commands work as intended but cleaninty cannot obtain the correct movable.sed for your console, you will need another method.
Solution:
If you have the console on hand and its power LED lights up when you attempt to boot it, join the Nintendo Homebrew Discord and ask for help - there may be an alternate solution available.
If this is not the case, unfortunately, you cannot recover your movable.sed at this time. If you obtain more of the console's data, revisit this guide.
