StarlitSkies (talk | contribs) (guide to obtaining a nonfunctional console's movable.sed, including through cleaninty if no backups are available) |
StarlitSkies (talk | contribs) (remove usage of godmode9, revise and expand section about finding otp + eshop region, wording fixes) |
||
| Line 1: | Line 1: | ||
If you require a console's <code>movable.sed</code> for some purpose but | If you require a console's <code>movable.sed</code> for some purpose but cannot obtain it directly from the NAND for some reason, there are still multiple potential ways to reobtain its <code>movable.sed</code>. | ||
{{warning|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.}} | {{warning|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 == | == Instructions == | ||
Do you have a backup of the console, either <code>essentials.exefs</code> or a NAND backup (a | Do you have a backup of the console, either <code>essentials.exefs</code> or a NAND backup (a <code>.bin</code> file between 0.9GB and 1.3GB that has '''nand''' in its name)?<br> | ||
These files may be found in <code>sd:gm9/out</code> on the console's SD card, or on your PC in a place you keep backups. | These files may be found in <code>sd:gm9/out</code> on the console's SD card, or on your PC in a place you keep backups. | ||
| Line 12: | Line 12: | ||
---- | ---- | ||
<big>Solution:</big> | <big>Solution:</big> | ||
You will need to use [[ninfs]] to mount the backup on a PC and then pull the <code>movable.sed</code> out of the mount. | |||
Ensure you have a copy of the file <code>boot9.bin</code>, as ninfs requires it to work. This file can be obtained through [[3DS:fastboot3DS|fastboot3DS]] or GodMode9 on any working 3DS that has CFW installed, or from the folder <code>sd:/luma/backups</code> on the SD card of a console that has previously been modded. | |||
< | |||
This may not work depending on how and when the backup was created, in which case you will need an alternate method. | |||
|-|No= | |-|No= | ||
---- | ---- | ||
Do you have the console's <code>otp.bin</code> and know | Do you have the console's <code>otp.bin</code> and know its eShop region? | ||
'''OTP:''' <code>otp.bin</code> file may be found on the console's SD card in <code>sd:/luma/backups</code> or <code>sd:/gm9/out</code>, and you may be able to dump it through either GodMode9 or [[3DS:fastboot3DS|fastboot3DS]] even if most of the console is unusuable.<br> | |||
'''eShop Region:''' If your console has never had a SOAP transfer or a motherboard swap before, there are several potential ways to find the serial number to determine it. | |||
* '''Serial Label:''' The serial label can be found on/under the backplate of the 3DS or under the battery, except on a 2DS XL where it will be under the game card/SD card slot cover. Once found, check its serial number against [[https://www.3dbrew.org/wiki/Serials this page]] to determine your region. | |||
* '''SecureInfo''': This file may be found on the console's SD card in <code>sd:/luma/backups</code>, or on its NAND in the folder <code>[1:]/rw/sys</code> if it can boot into GodMode9. When opened in the hexeditor, the end of this file contains the serial number. Check it against 3dbrew, as above. | |||
* '''inspect.log''': This file can normally only be found through GodMode9, and is on the NAND in the folder <code>[2:]/sys/log</code>. When opened in either the hexeditor or textviewer, this file contains the serial number. Check it against 3dbrew, as above. | |||
{{#tag:tabber| | {{#tag:tabber| | ||
If you require a console's movable.sed for some purpose but cannot obtain it directly from the NAND for some reason, there are still multiple potential ways to reobtain its movable.sed.
 |
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. |
Do you have a backup of the console, either essentials.exefs or a NAND backup (a .bin file between 0.9GB and 1.3GB that has nand in its name)?
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.
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 its eShop region?
OTP: otp.bin file may be found on the console's SD card in sd:/luma/backups or sd:/gm9/out, and you may be able to dump it through either GodMode9 or fastboot3DS even if most of the console is unusuable.
eShop Region: If your console has never had a SOAP transfer or a motherboard swap before, there are several potential ways to find the serial number to determine it.
sd:/luma/backups, or on its NAND in the folder [1:]/rw/sys if it can boot into GodMode9. When opened in the hexeditor, the end of this file contains the serial number. Check it against 3dbrew, as above.[2:]/sys/log. When opened in either the hexeditor or textviewer, this file contains the serial number. Check it against 3dbrew, as above.
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.