Hacks Guide Wiki - User contributions [en]

3DS:Rebuild Title Database

2026-01-11T22:33:45Z

Mr. Burguers: Backslashes after drive letter

This page is a guide to rebuilding the <code>title.db</code> file in your SD card.

<code>title.db</code> is the name for two files - one on the 3DS' SD card, and one on its CTRNAND - which contain a list of all installed 3DS titles for its respective part of the filesystem (e.g. your SD card's <code>title.db</code> only has entries for titles installed to your SD card). For more information, check out [[3dbrew:Title Database|3dbrew]].

===What you need===

*Release of {{GitHub|wwylele/save3ds/releases/tag/v1.3.0|save3ds}} for your operating system
*A version of [https://www.python.org/downloads/ Python 3.8 or later]
*A 3DS console with custom firmware
*{{GitHub|ihaveamac/3DS-rom-tools/raw/master/seeddb/seeddb.bin|seeddb.bin}} (direct download link)
*boot9.bin (same for all consoles) and movable.sed (specific to yours only) - dump with [[3DS:Dump system files]]

===Section I - Preparing the files===

#Turn the 3DS off
#Insert your SD card into your computer
#Go to the {{GitHub|ihaveamac/rebuild-title-database|Rebuild Title Database}} repo's page
#Click the <big>Code</big> button, then click '''Download ZIP'''
#Extract the contents of the downloaded <code>.zip</code> into a folder
#*This folder will be referred to as the "rebuild folder" from now on
#Copy <code>movable.sed</code> and <code>boot9.bin</code> to the rebuild folder
#*If you had just dumped them from your console, both are most likely in <code>sd:/gm9/out</code>
#Copy <code>seeddb.bin</code> into the rebuild folder
#Copy the <code>save3ds_fuse</code> binary from the save3ds <code>.zip</code> file into the rebuild folder

===Section II - Rebuilding the database===
{{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.}}

#Navigate to the rebuild folder in file explorer
#Hold 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 -mpip install --user -r requirements.txt</code>
##<code>py -3 fix-titledb.py -b boot9.bin -m movable.sed -s X:\</code>
##*If you are on Windows, replace <code>X:\</code> with your SD card's drive letter. If you are not on Windows, replace <code>X:\</code> with your SD card's mount point.
##<code>py -3 rebuild-title-database.py -b boot9.bin -m movable.sed -S seeddb.bin -s X:\ -o out</code>
##<code>./save3ds_fuse.exe --db sdtitle out --import --boot9 boot9.bin --movable movable.sed --sd X:\</code>
##*If you are not on Windows, remove <code>.exe</code> from this command
#If you didn't get any errors, your apps should reappear on the HOME Menu immediately
#*If they only appear in '''System Settings''' -> '''Data Management''', follow '''one''' of these sets of steps based on how they appear.
#**Appear normally: Check the contents of <code>sd:/Nintendo 3DS/<id0>/<id1>/title/00040000</code>; there should only be more folders inside that folder.
#***If there is a file inside this folder, your apps are at least partially corrupted - backup your SD card to your PC, [[Formatting an SD card|reformat it]], and then try to move the backed-up files back to the SD. If this fails or the apps do not reappear afterward, [[Checking SD card integrity|check your SD card for hardware damage]].
#**Appear with a grey block count indicator and an X through their icons: Run [[3DS:Faketik|faketik]].
#**Appear with white/corrupted icons, 0 block count, and/or corrupted name: Whatever destroyed your <code>title.db</code> has also permanently corrupted your apps. Backup your SD card to your PC,[[Formatting an SD Card|reformat it]], and then [[Checking SD card integrity|check it for hardware damage]].
#*If they do not appear anywhere in the system, you may want to [[Checking SD card integrity|check your SD card for hardware damage]], as the apps are likely gone.

===Troubleshooting===

*<code>boot9.bin</code> is missing from <code>[M:] MEMORY VIRTUAL</code>
**Follow the steps to [[3DS:Dump system files|dump your system files]] for more in-depth instructions, including those for bootloaders other than [[3DS:boot9strap|boot9strap]].
*The first command in Section II gave the error <code>ERROR: Could not open requirements file: [Errno 2] No such file or directory: 'requirements.txt'</code>
**Make sure you are in the rebuild folder and that you extracted the contents of <code>rebuild-title-database-master.zip</code> into it.
***Once this is fixed, delete the <code>out</code> folder and try the command again.
*The third or fourth command in Section II failed
**Make sure you have <code>boot9.bin</code> and <code>movable.sed</code> in the rebuild folder.
**Make sure your SD card is inserted and you can view and edit its contents.
*The fifth command in Section II failed
**If you are on macOS, try installing {{GitHub|osxfuse/osxfuse/releases/latest|osxfuse}}, either via its GitHub page or via [https://brew.sh Homebrew].

====<code>Input/output error</code> on fourth command in Section II====
{{info|These instructions are for Linux users, and will not work on Windows.}}
#'''''Unmount''''' the SD card from your computer.
#Open up a terminal window, and enter the following commands one at a time:
##<code>watch lsblk</code>
##*After running this command, re-insert the SD card into your computer. The terminal window should now show a new partition of some kind. '''This is the SD card's partition'''. For example, <code>sda -> sda1</code> may have appeared after re-inserting the SD card. Keep this in mind, as you'll need it later.
##*Once you see what partition the SD card is, press <kbd><kbd>Ctrl</kbd> + <kbd>C</kbd></kbd> to stop monitoring the output of <code>lsblk</code>
##<code>fsck /dev/[partition]</code>
##*<code>[partition]</code> is the partition that showed up in the terminal, when you inserted the SD card into your computer. (e.g. <code>fsck /dev/sda1</code> if the SD card showed up under <code>sda -> sda1</code>)
##*If you see <code>fsck: command not found</code>, run the command with <code>sudo</code> (e.g. <code>sudo fsck ...</code>)

You should now be given a few prompts, containing some choices. Below are some possible prompts, and what you should answer with.
*<code>There are differences between boot sector and its backup.</code>
**Choose option 2 for "<code>copy backup to original</code>".
*<code>Orphaned long file name part "[folder name]"</code>
**Choose option 2 for "<code>leave it</code>".
*<code>Free cluster summary wrong <nowiki>(####### vs. really #######)</nowiki></code>
**Choose option 1 for "<code>correct</code>".

Eventually, you will see the following:

<nowiki>
*** Filesystem was changed ***
The changes have not yet been written, you can still choose to leave the
filesystem unmodified:
1) Write changes
2) Leave filesystem unchanged</nowiki>

If you are happy with the options you chose, and aren't scared something will break, choose option <kbd>1</kbd> to write changes. After the changes have been written, try re-running the fourth command in Section II and continuing on from there.

[[Category:Nintendo 3DS guides]]

3DS:Error codes

2022-09-25T15:26:21Z

Mr. Burguers: More error codes

This Page lists all currently known 3ds Error Codes. 
Error Codes (on 3ds and WiiU) are structured by a module identifier (exp:001) and a result code (exp:101). 
Please note that currently not all 3ds Error Codes are known. 
Any result code thats below 4 numbers here will be displayed with 0 before the actual code on the real systems. (exp: here:101 system:0101) 

{| class="wikitable" style="margin:auto;"
|-
! colspan="3" |001 Online Services
|-
|102
|Unexpected Disconnection from Network Services
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/17043 Nintendo Support Page]
|-
|721
|Online Access restricted by Parental Controls.
|
|-
|803
|Cannot connect to authentication servers.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|811
|Online Play server under maintenance. Refer to the link above for the Server Status and upcoming Maintenance.
|
|-
! colspan="3" |002 Account Related Errors
|-
|102
|Account Permanently Banned.
|
|-
|107
|Account Temporarily Banned.
|
|-
|110
|3DS Youtube was Discontinued.
|
|-
|119
|Friend Module out of Date, System Update Required.
|
|-
|120
|Game/Title out of Date, Update Required
|
|-
|121
|Invalid Local Friend SEED Signature, possibly Modified.
|
|-
|123
|Account Permanently Banned.
|
|-
|34xx
|Server returned a 4xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|35xx
|Server returned a 5xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
! colspan="3" |003 Network Connection Errors
|-
|299
|Disabled Wireless Connection.
|
|-
|399
|Accepted EULA version is too low.
|
|-
|1099
|Access Point with given SSID not found.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4249/kw/003-1099 Nintendo Support Page]
|-
|1101
|Access Point password incorrect or Incompatible Configuration.
|
|-
|2001
|DNS Error. If you are using a Custom DNS Server, recheck the settings.
|
|-
! colspan="3" |005 Network Installation Management
|-
|2008
|eShop download failed or invalid title ticket. Delete Ticket in FBI and install it from a legitimate source like the eShop or (if it's a cart dump) from the game's cartridge.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/41692 Nintendo Support Page]
|-
|4040
|eShop connection timeout.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4429 Nintendo Support Page]
|-
|4069
|eShop is unavailable. If the issue persists, the SD might need to be replaced.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/14413 Nintendo Support Page]
|-
|4240
|Cannot connect to eShop servers.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/28399 Nintendo Support Page]
|-
|4305
|Generic Connection Timeout Error, could also mean that you are unable to download software from the eShop.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4346 Nintendo Support Page]
|-
|4320
|Generic Error that displayed when formatting the console or performing a system transfer.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/48382 Nintendo Support Page]
|-
|5602
|eShop title(s) from another region are linked to this console. Caused by region change.
|
|-
|5687
|Generic Unable to connect to eShop error.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/26251/ Nintendo Support Page]
|-
|5704
|Same as 5687.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/26252 Nintendo Support Page]
|-
|5958
|Unknown eShop error, usually seen on region-changed Consoles.
|
|-
|5964
|NNID banned from accessing eShop, contact Nintendo Support if this is a mistake.
|
|-
|7545
|Same as 4069.
|
|-
|7550
|Same as 4069.
|
|-
|8025
|Same as 4069.
|
|-
|8026
|Same as 4069.
|
|-
|8029
|Same as 4069.
|
|-
! colspan="3" |006 Matchmaking Errors
|-
|112
|Issue connecting with Pokemon Bank.
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/4203/ Nintendo Support Page]
|-
|332
|Closed Ports when attempting Matchmaking.
|
|-
|501
|May indicate that the network is blocking traffic necessary for Online Play.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4204 Nintendo Support Page]
|-
|502
|Same as 502.
|
|-
|612
|Network is not optimal for peer-to-peer connections, possibly your network's NAT type.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/25881 Nintendo Support Page]
|-
|811
|Service Unavailable due to maintenance.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/25910/ Nintendo Support Page]
|-
|800
|Unable to connect to authentication servers during the matchmaking process.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4328/ Nintendo Support Page]
|-
|899
|Same as 800.
|
|-
! colspan="3" |007 eShop API Errors
|-
|200
|Could did not access the SD Card.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4234 Nintendo Support Page]
|-
|1221
|Download Code only redeemable in the relevant Software, not in the eShop.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/14600 Nintendo Support Page]
|-
|2001
|Error when attempting to access the eShop with a region-changed Console, fixed by changing back to the region of Origin.
|
|-
|2100
|Connection to eShop timed out, often caused by slow download times.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4432 Nintendo Support Page]or [https://support.nintendo.com/networkstatus Server Status and Maintenance]
|-
|2640
|Cannot connect to eShop/CDN servers.
|[https://support.nintendo.com/networkstatus Server Status and Maintenance]
|-
|2670
|Error while attempting to connect.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4383 Nintendo Support Page]
|-
|2705
|Cannot connect to Nintendo servers.
|[https://support.nintendo.com/networkstatus Server Status and Maintenance]
|-
|2720
|eShop SSL error.
|
|-
|2913
|The Server is probably down. Try again later.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/10425 Nintendo Support Page]
|-
|2916
|Typically displayed when attempting to download a title from the eShop.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/6557 Nintendo Support Page]
|-
|2920
|Same as 005-2008.
|
|-
|2924
|Invalid Language Setting when opening eShop.
|
|-
|3049
|The eShop is down for Maintenance.
|[https://support.nintendo.com/networkstatus/ Server Status and Maintenance]
|-
|6106
|Occurs when attempting to re-download the software from the shop with an invalid or fake ticket.
|
|-
! colspan="3" |009 eShop Application
|-
|1000
|System Update required.
|
|-
|1001
|Same as 007-3049
|
|-
|2001
|Same as 007-2001
|
|-
|2705
|Often caused by network timing out or losing connection with the eShop
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/17014 Nintendo Support Page]
|-
|2913
|eShop or in-game DLC failed to download (or the server is down).
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/7243 Nintendo Support Page]
|-
|2916
|Same as 007-2916.
|
|-
|2920
|Same as 007-2920.
|
|-
|2923
|Unable to use a function that requires Internet Services.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/17014 Nintendo Support Site]
|-
|2924
|Same as 007-2924.
|
|-
|2995
|Download Code is/was incorrect, not yet activated, expired, entered in the wrong place, or intended for another Region than your own.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/13515 Nintendo Support Site]
|-
|4077
|Download not started/aborted due to insufficient Space on the SD Card.
|
|-
|4079
|Unable to access the SD Card
|
|-
|4998
|Local Content is newer. Unknown what causes this.
|
|-
|6106
|AM error in NIM. Likely a bad ticket.
|
|-
|8401
|Corrupted Update Data. Delete it and reinstall.
|
|-
|9001
|Download Failed due to low battery.
|
|-
! colspan="3" |011 eShop Site
|-
|24xx
|Server returned a 4xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|25xx
|Server returned a 5xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|3010
|Server Timed due to inactivity.
|
|-
|3021
|eShop title not found (wrong region or non-existent).
|
|-
|3136
|eShop currently unavailable. Try again later.
|
|-
|5998
|eShop is currently under maintenance.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/24326/ Nintendo Support Page]
|-
|6901
|Console Permanently Banned (displayed in Japanese).
|
|-
! colspan="3" |012 Browser Errors
|-
|1004
|SSL Connection Failed.
|
|-
|1511
|Certificate Warning.
|
|-
! colspan="3" |014 Data Transfer Errors
|-
|13
|System Transfer failed due to Invalid Language Setting.
|
|-
|16
|Both Consoles have the same movable.sed, format the target console, and try again.
|
|-
|62
|Error during System Transfer occurred, move close to the router and try again.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/15664 Nintendo Support Page]
|-
! colspan="3" |022 More Account Errors
|-
|2452
|Tried to access the eShop with UNITINFO patch enabled. Turn it off in Luma\'s options.
|
|-
|2501
|NNID is already linked to another System. Could be caused by a System Transfer (which Transfers all associated NNID's whether linked or not, restoring the Source Systems NAND) and then attempting to use an Application that uses NNIDs.
|
|-
|2511
|System Update required (displayed by Miiverse).
|
|-
|2591
|Same as 2501.
|
|-
|2613
|Incorrect Email or Password when attempting to link an existing NNID. This can happen due to the NNID already being linked or when attempting to download a title from the eShop without having an NNID linked.
|
|-
|2631
|The NNID you are trying to use has been deleted or can't be used for a system transfer. A transferable NNID will only work on the target system.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4285/kw/022-2631 Nintendo Support Page]
|-
|2633
|NNID temporarily locked due to too many password attempts. Try again later.
|
|-
|2634
|NNID is not correctly linked to the system. To fix this follow these steps and afterwards reboot and sign into the NNID again.
|[https://3ds.hacks.guide/godmode9-usage#removing-an-nnid-without-formatting-your-device) Said Steps]
|-
|2812
|Console Permanently Banned for playing Pokemon Sun & Moon online before the release date.
|
|-
|2815
|Console Permanently Banned from accessing Miiverse by Nintendo.
|
|-
|5363
|NNID Setting failed to load due to an incorrect language setting.
|
|-
|5515
|Network Timeout.
|
|-
|5531
|Cannot connect to account servers.
|[https://support.nintendo.com/networkstatus Server Status and Maintenance]
|-
! colspan="3" |026 Account/eShop?
|-
|24xx
|Server returned a 4xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|25xx
|Server returned a 5xx HTTP error.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|3221
|Failed to unlink NNID during formatting, try again.
|
|-
! colspan="3" |032 More Browser Errors
|-
|1035
|Unable to display page.
|
|-
|1208
|Adress not supported.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/43018/~/error-code%3A-032-1208 Nintendo Support Page]
|-
|1820
|Displayed when the browser asks you if you want to visit a potentially dangerous website. Press yes if you feel it's safe to visit.
|
|-
! colspan="3" |090 In-Game Specific Errors
|-
|212
|The game is permanently banned from Pokemon Global Link for using altered or illegal save data.
|
|}

3DS:Error codes

2022-09-25T14:35:26Z

Mr. Burguers: Use table formatting

This Page lists all currently known 3ds Error Codes. 
Error Codes (on 3ds and WiiU) are structured by a module identifier (exp:001) and a result code (exp:101). 
Please note that currently not all 3ds Error Codes are known. 
Any result code thats below 4 numbers here will be displayed with 0 before the actual code on the real systems. (exp: here:101 system:0101) 

{| class="wikitable" style="margin:auto;"
|-
! colspan="3" |001 Online Services
|-
|102
|Unexpected Disconnection from Network Services
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/17043 Nintendo Support Page]
|-
|721
|Online Access restricted by Parental Controls.
|
|-
|803
|Online Play server is down.
|[https://www.nintendo.co.jp/netinfo/en_US/index.html Server Status and Maintenance]
|-
|811
|Online Play server under maintenance. Refer to the link above for the Server Status and upcoming Maintenance.
|
|-
! colspan="3" |002 Account Related Errors
|-
|102
|Account Permanently Banned.
|
|-
|107
|Account Temporarily Banned.
|
|-
|110
|3DS Youtube was Discontinued.
|
|-
|119
|Friend Module out of Date, System Update Required.
|
|-
|120
|Game/Title out of Date, Update Required
|
|-
|121
|Invalid Local Friend SEED Signature, possibly Modified.
|
|-
|123
|Account Permanently Banned.
|
|-
! colspan="3" |003 Network Connection Errors
|-
|299
|Disabled Wireless Connection.
|
|-
|399
|Accepted EULA version is too low.
|
|-
|1099
|Access Point with given SSID not found.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4249/kw/003-1099 Nintendo Support Page]
|-
|1101
|Access Point password incorrect or Incompatible Configuration.
|
|-
|2001
|DNS Error. If you are using a Custom DNS Server, recheck the settings.
|
|-
! colspan="3" |005 Network Installation Management
|-
|2008
|eShop download failed or invalid title ticket. Delete Ticket in FBI and install it from a legitimate source like the eShop or (if it's a cart dump) from the game's cartridge.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/41692 Nintendo Support Page]
|-
|4040
|eShop connection timeout.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4429 Nintendo Support Page]
|-
|4069
|eShop is unavailable. If the issue persists, the SD might need to be replaced.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/14413 Nintendo Support Page]
|-
|4240
|Temporary eShop Service issue.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/28399 Nintendo Support Page]
|-
|4305
|Generic Connection Timeout Error, could also mean that you are unable to download software from the eShop.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4346 Nintendo Support Page]
|-
|4320
|Generic Error that displayed when formatting the console or performing a system transfer.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/48382 Nintendo Support Page]
|-
|5602
|Unable to connect to the eShop due to region-changed Console, change it back to the region of Origin to fix it.
|
|-
|5687
|Generic Unable to connect to eShop error.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/26251/ Nintendo Support Page]
|-
|5704
|Same as 5687.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/26252 Nintendo Support Page]
|-
|5958
|Unknown eShop error, usually seen on region-changed Consoles.
|
|-
|5964
|NNID banned from accessing eShop, contact Nintendo Support if this is a mistake.
|
|-
|7545
|Same as 4069.
|
|-
|7550
|Same as 4069.
|
|-
|8025
|Same as 4069.
|
|-
|8026
|Same as 4069.
|
|-
|8029
|Same as 4069.
|
|-
! colspan="3" |006 Matchmaking Errors
|-
|112
|Issue connecting with Pokemon Bank.
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/4203/ Nintendo Support Page]
|-
|332
|Closed Ports when attempting Matchmaking.
|
|-
|501
|May indicate that the network is blocking traffic necessary for Online Play.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4204 Nintendo Support Page]
|-
|502
|Same as 502.
|
|-
|612
|Network is not optimal for peer-to-peer connections, possibly your network's NAT type.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/25881 Nintendo Support Page]
|-
|811
|Service Unavailable due to maintenance.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/25910/ Nintendo Support Page]
|-
|800
|Unable to connect to authentication servers during the matchmaking process.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4328/ Nintendo Support Page]
|-
|899
|Same as 800.
|
|-
! colspan="3" |007 eShop API Errors
|-
|200
|Could did not access the SD Card.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4234 Nintendo Support Page]
|-
|1221
|Download Code only redeemable in the relevant Software, not in the eShop.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/14600 Nintendo Support Page]
|-
|2001
|Error when attempting to access the eShop with a region-changed Console, fixed by changing back to the region of Origin.
|
|-
|2100
|Connection to eShop timed out, often caused by slow download times.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4432 Nintendo Support Page]or [https://support.nintendo.com/networkstatus Server Status and Maintenance]
|-
|2670
|Error while attempting to connect.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4383 Nintendo Support Page]
|-
|2720
|eShop SSL error.
|
|-
|2913
|The Server is probably down. Try again later.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/10425 Nintendo Support Page]
|-
|2916
|Typically displayed when attempting to download a title from the eShop.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/6557 Nintendo Support Page]
|-
|2920
|Same as 005-2008.
|
|-
|2924
|Invalid Language Setting when opening eShop.
|
|-
|3049
|The eShop is down for Maintenance.
|[https://support.nintendo.com/networkstatus/ Server Status and Maintenance]
|-
|6106
|Occurs when attempting to re-download the software from the shop with an invalid or fake ticket.
|
|-
! colspan="3" |009 eShop Application
|-
|1000
|System Update required.
|
|-
|1001
|Same as 007-3049
|
|-
|2705
|Often caused by network timing out or losing connection with the eShop
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/17014 Nintendo Support Page]
|-
|2913
|eShop or in-game DLC failed to download (or the server is down).
|[https://en-americas-support.nintendo.com/app/answers/detail/a%20id/7243 Nintendo Support Page]
|-
|2916
|Same as 007-2916.
|
|-
|2920
|Same as 007-2920.
|
|-
|2923
|Unable to use a function that requires Internet Services.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/17014 Nintendo Support Site]
|-
|2924
|Same as 007-2924.
|
|-
|2995
|Download Code is/was incorrect, not yet activated, expired, entered in the wrong place, or intended for another Region than your own.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/13515 Nintendo Support Site]
|-
|4077
|Download not started/aborted due to insufficient Space on the SD Card.
|
|-
|4079
|Unable to access the SD Card
|
|-
|4998
|Local Content is newer. Unknown what causes this.
|
|-
|6106
|AM error in NIM. Likely a bad ticket.
|
|-
|8401
|Corrupted Update Data. Delete it and reinstall.
|
|-
|9001
|Download Failed due to low battery.
|
|-
! colspan="3" |011 eShop Site
|-
|3010
|Server Timed due to inactivity.
|
|-
|3021
|eShop title not found (wrong region or non-existent).
|
|-
|3136
|eShop currently unavailable. Try again later.
|
|-
|5998
|eShop is currently under maintenance.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/24326/ Nintendo Support Page]
|-
|6901
|Console Permanently Banned (displayed in Japanese).
|
|-
! colspan="3" |012 Browser Errors
|-
|1004
|SSL Connection Failed.
|
|-
|1511
|Certificate Warning.
|
|-
! colspan="3" |014 Data Transfer Errors
|-
|13
|System Transfer failed due to Invalid Language Setting.
|
|-
|16
|Both Consoles have the same movable.sed, format the target console, and try again.
|
|-
|62
|Error during System Transfer occurred, move close to the router and try again.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/15664 Nintendo Support Page]
|-
! colspan="3" |022 More Account Errors
|-
|2452
|Tried to access the eShop with UNITINFO patch enabled. Turn it off in Luma\'s options.
|
|-
|2501
|NNID is already linked to another System. Could be caused by a System Transfer (which Transfers all associated NNID's whether linked or not, restoring the Source Systems NAND) and then attempting to use an Application that uses NNIDs.
|
|-
|2511
|System Update required (displayed by Miiverse).
|
|-
|2591
|Same as 2501.
|
|-
|2613
|Incorrect Email or Password when attempting to link an existing NNID. This can happen due to the NNID already being linked or when attempting to download a title from the eShop without having an NNID linked.
|
|-
|2631
|The NNID you are trying to use has been deleted or can't be used for a system transfer. A transferable NNID will only work on the target system.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/4285/kw/022-2631 Nintendo Support Page]
|-
|2633
|NNID temporarily locked due to too many password attempts. Try again later.
|
|-
|2634
|NNID is not correctly linked to the system. To fix this follow these steps and afterwards reboot and sign into the NNID again.
|[https://3ds.hacks.guide/godmode9-usage#removing-an-nnid-without-formatting-your-device) Said Steps]
|-
|2812
|Console Permanently Banned for playing Pokemon Sun & Moon online before the release date.
|
|-
|2815
|Console Permanently Banned from accessing Miiverse by Nintendo.
|
|-
|5363
|NNID Setting failed to load due to an incorrect language setting.
|
|-
|5515
|Network Timeout.
|
|-
! colspan="3" |032 More Browser Errors
|-
|1035
|Unable to display page.
|
|-
|1208
|Adress not supported.
|[https://en-americas-support.nintendo.com/app/answers/detail/a_id/43018/~/error-code%3A-032-1208 Nintendo Support Page]
|-
|1820
|Displayed when the browser asks you if you want to visit a potentially dangerous website. Press yes if you feel it's safe to visit.
|
|-
! colspan="3" |090 In-Game Specific Errors
|-
|212
|The game is permanently banned from Pokemon Global Link for using altered or illegal save data.
|
|}

3DS:Alternate Exploits/Preparing menuhax67 (kartdlphax)

2022-09-24T20:35:10Z

Mr. Burguers: Fix spacing without using br

== Required Reading ==
[https://github.com/PabloMK7/kartdlphax kartdlphax] is an exploit for the game "[[3DS:Mario Kart 7|Mario Kart 7]]", compatible with System Versions 1.0.0 through 11.16.0 for USA/EUR/JPN region consoles primarily made made by [https://github.com/PabloMK7 PabloMK7]. It was used to launch [https://github.com/TuxSH/universal-otherapp universal-otherapp] in the past, that got patched with the latest version, so this exploit can be used now to prepare the secondary exploits[https://github.com/zoogie/unSAFE_MODE unSAFE_MODE](you can find this on the [[3dsguide:index|main guide]]) or [https://github.com/zoogie/menuhax67 menuhax67] on 11.16.0-49X. Credits go to [https://github.com/zoogie zoogie] for both of these exploits. If you're on an older version(<=11.15.0-47X), you can use universal-otherapp instead. This page covers installing menuhax67 to access the Homebrew Launcher since accessing the Homebrew Launcher from kartdlphax directly not possible currently. To use these exploits, kartdlphax includes the [https://github.com/PabloMK7/3dsropxploitinjector 3DS ROP xPloit Injector]

To use this exploit, you need:

*A second 3DS with [[custom firmware]] (the '''source 3DS''') that is the same region as the 3DS you are trying to modify (the '''target 3DS''')
*A physical or digital copy of Mario Kart 7 that is the same region as both consoles
*An SD card for both devices

==What you need==
On the '''source 3DS''' (the 3DS with custom firmware):

*The latest release of [https://github.com/PabloMK7/kartdlphax/releases/latest kartdlphax] (<code>plugin.3gx</code>)
*The latest release of [https://github.com/Nanquitas/Luma3DS/releases/latest Luma3DS 3GX Loader Edition] (<code>boot.firm</code>)

On the '''target 3DS''' (the 3DS that you are trying to launch the Homebrew Launcher on):

*The latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest standard Luma3DS] (the Luma3DS <code>.zip</code> file)
*The latest release of [https://github.com/zoogie/menuhax67/releases/latest menuhax67] (the menuhax67 <code>.zip</code> file)

==Instructions==

===Section I - Prep Work===
On the '''source 3DS''' (the 3DS with custom firmware):

#Insert the SD card of your '''source 3DS''' in your computer
#Copy Luma 3GX Loader Edition’s <code>boot.firm</code> to the root of the '''source 3DS'''’s SD card, replacing any existing file
#*The root of the SD card refers to the initial directory on your SD card where you can see the Nintendo 3DS folder, but are not inside of it
#Copy kartdlphax’s <code>plugin.3gx</code> to the following directory on the '''source 3DS'''’s SD card, depending on the '''region of your copy of Mario Kart 7''':
#* USA: <code>luma/plugins/0004000000030800</code>
#* EUR: <code>luma/plugins/0004000000030700</code>
#*JPN: <code>luma/plugins/0004000000030600</code>
#*Create the <code>plugins</code> and <code>00040000...</code> folders if they do not already exist
# Eject the SD card and put it in the '''source 3DS'''

On the '''target 3DS''' (the 3DS that you are trying to launch the Homebrew Launcher on):

# Insert the SD card of your '''target 3DS''' in your computer
#Copy <code>boot.firm</code> and <code>boot.3dsx</code> from the standard Luma3DS <code>.zip</code> to the root of your SD card
#Copy the <code>Launcher.dat</code> for your region/version from the menuhax67 <code>.zip</code> to the root of your SD card

===Section II - kartdlphax ===

#Power on the '''source 3DS'''
#*If you are prompted to set up Luma3DS, just press START to save the configuration
#Once in the HOME Menu, press (Left Shoulder) + (Down D-Pad) + (Select) to bring up the Rosalina menu
#Select “Enable plugin loader”
#Press (B) to exit the Rosalina menu
#Launch Mario Kart 7
#*Ensure that wireless connectivity is enabled
#Navigate to <code>Local Multiplayer</code>. A menu should pop up
#* If the screen freezes, hold the power button for fifteen seconds to force power off your device, then try again
#*If you have launched kartdlphax previously, the last selected settings will be loaded. If they are correct, select <code>Use settings</code> and skip the next 3 steps. If they are incorrect, select <code>Change settings</code> and proceed.
# Select your '''target 3DS''' device type (Old 3DS family or New 3DS family)
# Select the exploit type <code>3DS ROP xPloit Injector</code>
#A confirmation menu will show up. If the settings shown on the top screen are correct, select <code>Use settings</code>
#*If the settings are not correct, press <code>Change settings</code> and modify them accordingly
#Select <code>Create Group</code>
#* If the source 3DS freezes at this point and you are using a cartridge, try installing the cartridge to the system
#Power on the '''target 3DS'''
#*Ensure that wireless connectivity is enabled
#On the '''target 3DS''', open the Download Play application (), then select “Nintendo 3DS”
#Join the group created by the '''source 3DS'''
#Select “Start” on the '''source 3DS''' once it has detected the '''target 3DS'''
#Once multiplayer has loaded, navigate to <code>Grand Prix</code> -> <code>50cc</code> -> (any driver) -> <code>Mushroom Cup</code> -> <code>OK</code>
#Wait a while (a percentage should be displayed on the '''source 3DS''')
#If the exploit was successful, the '''target 3DS''' will have booted into the 3DS ROP xPloit Injector
#*If the exploit was not successful, power off the '''source 3DS''' and '''target 3DS''' and start again from the beginning of <code>Section II - kartdlphax</code>
# Press (Y) to install menuhax67
# The '''target 3DS''' will automatically power off
{{Info|text=You will not need to use your source 3DS to complete any further steps on this guide. Any further steps should only be completed on the target 3DS.}}

===Section III - menuhax67 ===

#Power on your device(target 3DS)
#Press on the small home icon on the top left of the touch screen in the home menu
{{Info|text=If the exploit was successful, your device will have booted into the Homebrew Launcher}}

At this point, there are a number of processes you may follow. Continue to the next section of the guide based on what you have access to.

{| class="wikitable" style="text-align:center;"
!Method
! colspan="3" |Requirements
|-
| ---
!Working shoulder buttons
!Working DS mode
!System version
|-
|[[3DS:Alternate Exploits/Installing boot9strap (HBL-USM)|Installing boot9strap (HBL-USM)]]
| bgcolor="ffc8c8" |Yes
| bgcolor="c8ffc8" |No
| bgcolor="c8ffc8" |Latest
|-
|[[3DS:Alternate Exploits/Dumping movable.sed (nimhax)|Dumping movable.sed (nimhax)]]
| bgcolor="c8ffc8" |No
| bgcolor="ffc8c8" |Yes
| bgcolor="c8ffc8" |Latest
|-
|[[3DS:Alternate Exploits/Installing boot9strap (uloader)|Installing boot9strap (uloader)]]
| bgcolor="c8ffc8" |No
| bgcolor="c8ffc8" |No
| bgcolor="eee8aa" |11.15.0 or lower
|}

==Uninstall menuhax67==
This is an add-on section for people who successfully did what they needed to do in the Homebrew Launcher. This section describes uninstalling menuhax67 to make the small home icon usable again.

===Instructions===

#Create a folder called <code>3ds</code> on the root of your SD card
#Copy the menuhax67_installer.3dsx from the menuhax67 <code>.zip</code> to the root of your SD card
#Insert the SD card into the 3DS
#Launch the Homebrew Launcher with any method(normally with Rosalina & Download Play or from the home menu)
#Launch the menuhax67_installer.3dsx from the list of homebrew
#Select "REMOVE menuhax67"

3DS:Error screens/Luma3DS exception screen

2022-06-20T22:42:10Z

Mr. Burguers: Fix text inconsistency

This page lists possible causes of Luma3DS exception screens. They might not be applicable to every situation.

== Arm9 ==

=== On boot ===

* Files on the SD are corrupted.
* A system save inside <code>1:/data</code> has a problem.
* Files in <code>1:/rw/sys</code> are missing.

==== Prefetch abort (svcBreak) ====

* <code>1:/private/movable.sed</code> is only 288 bytes, but its flag indicates otherwise.
* SYSNAND CTRNAND has bad CMACs.

==== Data abort ====

* The <code>2:/shared2</code> folder is missing.

=== During use ===

* Files on the SD are corrupted.

== Arm11 ==

=== On boot ===

==== boss (0004013000003402), data abort ====

* Firmware version is too old to handle SpotPass. Perform a safe mode update.

==== fs (0000000000000000) ====

* Can be anything from SD card problems to hardware issues.

==== hid (0004013000001D02) ====

* Potential hardware problems.

==== menu (000400300000__02), data abort ====

* Broken HOME Menu theme.
* Broken HOME Menu extra data.
* Broken HOME Menu application.

==== pm (0000000000000000), undefined instruction ====

* Outdated Luma3DS that does not support the current firmware version.

=== During use ===

==== loader (0000000000000000) ====

If the hexadecimal number next to R0 starts with 'C' or 'D', search for it in [[3DS:Error_screens/Luma3DS_ErrDisp]].

[[Category:Unbricking]]

3DS:Error screens/Luma3DS exception screen

2022-06-20T22:35:02Z

Mr. Burguers: More Arm11 errors

This page lists possible causes of Luma3DS exception screens. They might not be applicable to every situation.

== Arm9 ==

=== On boot ===

* Files on the SD are corrupted.
* A system save inside <code>1:/data</code> has a problem.
* Files in <code>1:/rw/sys</code> are missing.

==== Prefetch abort (svcBreak) ====

* <code>1:/private/movable.sed</code> is only 288 bytes, but its flag indicates otherwise.
* SYSNAND CTRNAND has bad CMACs.

==== Data abort ====

* The <code>2:/shared2</code> folder is missing.

=== During regular use ===

* Files on the SD are corrupted.

== Arm11 ==

=== On boot ===

==== boss (0004013000003402), data abort ====

* Firmware version is too old to handle SpotPass. Perform a safe mode update.

==== fs (0000000000000000) ====

* Can be anything from SD card problems to hardware issues.

==== hid (0004013000001D02) ====

* Potential hardware problems.

==== menu (000400300000__02), data abort ====

* Broken HOME Menu theme.
* Broken HOME Menu extra data.
* Broken HOME Menu application.

==== pm (0000000000000000), undefined instruction ====

* Outdated Luma3DS that does not support the current firmware version.

=== During use ===

==== loader (0000000000000000) ====

If the hexadecimal number next to R0 starts with 'C' or 'D', search for it in [[3DS:Error_screens/Luma3DS_ErrDisp]].

[[Category:Unbricking]]

3DS:Error screens/Luma3DS exception screen

2022-06-20T21:28:23Z

Mr. Burguers: Example errors to demostrate layout

This page lists possible causes of Luma3DS exception screens. They might not be applicable to every situation.

== Arm9 ==

=== On boot ===

* Files on the SD are corrupted.
* A system save inside <code>1:/data</code> has a problem.
* Files in <code>1:/rw/sys</code> are missing.

==== Prefetch abort (svcBreak) ====

* <code>1:/private/movable.sed</code> is only 288 bytes, but its flag indicates otherwise.
* SYSNAND CTRNAND has bad CMACs.

==== Data abort ====

* The <code>2:/shared2</code> folder is missing.

=== During regular use ===

* Files on the SD are corrupted.

== Arm11 ==

=== On boot ===

==== boss (0004013000003402), data abort ====

* Firmware version is too old to handle SpotPass. Perform a safe mode update.

==== hid (0004013000001D02) ====

* Potential hardware problems.

==== pm (0000000000000000), undefined instruction ====

* Outdated Luma3DS that does not support the current firmware version.

[[Category:Unbricking]]

3DS:Error screens

2022-06-20T20:32:54Z

Mr. Burguers: Split troubleshooting into subpages

{{ambox
| type = content
| issue = This page needs screenshots of the error screens.
| text = This is hard to do as Luma3DS Rosalina is unable to take screenshots of these in most cases. So someone with a capture card needs to get these.
}}{{TOC right}}

There are multiple kinds of errors that can appear on the 3DS.

== Nintendo error screen ==

The stock error screen. This occurs on stock firmware or old Luma3DS versions without the custom ErrDisp.

See [[3DS:Error_screens/Nintendo_error_screen]] for known fixes to some of these.

== Luma3DS ErrDisp ==

Luma3DS replaces the stock ErrDisp to show more information about an error.

See [[3DS:Error_screens/Luma3DS_ErrDisp]] for known fixes to some of these.

== Luma3DS exception screen ==

See [[3DS:Error_screens/Luma3DS_exception_screen]] for known fixes to some of these.

[[Category:Unbricking]]