Hacks Guide Wiki - User contributions [en]

3DS:Error screens/Luma3DS ErrDisp

2024-12-16T15:55:57Z

Thepikachugamer: that is NOT supposed to say 1:

{{shortcut|3DS:ERRDISP}}
With Luma3DS installed, the 3DS error handler is modified to give significantly more information compared to [[3DS:Error screens/Nintendo error screen|the default error screens]]. These errors are also displayed by certain other applications such as [[3DS:FBI|FBI]].

This page lists various causes and solutions of Luma3DS ErrDisp errors.

==Reading a Luma3DS ErrDisp==

A Luma3DS ErrDisp error has several parts, but only two of them help in finding its cause. They are as follows:
[[File:Luma3DS ErrDisp.jpg|center]]
* '''Process name:''' The part of the system that is triggering the error. Can be helpful if the error code is generic.
* '''Error code:''' The specific reason the error occurred. This is almost always the most helpful part of the error.

==Known errors==

If your ErrDisp displays one of the processes in the first table, you do not need to look up its error code in the second one. The solutions for these processes are almost always the same.

----

{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Process Name
! style="font-size:125%;" | Problem & Solution
|-
| process: '''cam'''<br>process: '''qtm'''
| Your camera's hardware is damaged or dead.
:If the error code is <code>0xF96183FE</code>, you can open <code>sd:/luma/config.ini</code> and set the variable <code>enable_safe_firm_rosalina</code> to 1 to bypass this error.
:Otherwise, to fix, replace the camera with a new one. To avoid the error until then, or if you cannot get a new camera, disconnect the camera.
|-
| process: '''kernel'''
| Your system software is having a strange issue.
:To fix, diagnose further by reading the contents of the file <code>sd:/luma/errdisp.txt</code>. If you do not understand this file, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue there.
|-
| process: '''mcu'''
| Something related to power or the battery is having issues.
:To fix, check if your charger repeatedly disconnects and reconnects while it is inserted. If this is the case, you have a faulty charger port and need to replace it.
:If this is not the case, you have a deeper hardware issue that may not be fixable.
|-
| process: '''nwm'''
| Your WiFi chipset's hardware is damaged or dead.
:To fix, replace the WiFi chipset with a new one. To avoid this error until then or if you cannot get a new chipset, disable WiFi on the 3DS and do not turn it back on.
:If your 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on may allow you to access Rosalina before it can crash.
|}

{{info|In the following table, when <code>?</code> is in an error code, it is a wildcard.<br>This means any character can be in its position and the error code will remain the same.}}
{| class="wikitable" style="margin: auto"
! style="font-size:125%;" | Error Code
! style="font-size:125%;" | Problem & Solution
|-
| card removed
| Your SD card is faulty, or debris is interfering with its connection to the 3DS.
:To fix, clean the SD card and the SD reader in the 3DS with isopropyl alcohol. If this does not work, [[Checking SD card integrity|test the SD card for errors]].
|-
| 0xC86044D2
| Your NAND does not have enough free space available.
:To fix, join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and explain your issue in detail. Deleting files from the NAND without guidance is likely to cause additional issues.
|-
| 0xC8804464<br>0xC8804471<br>0xC8804497<br>0xC88044A?
| Some dependency of the app you are trying to open does not exist.
:Ensure your SD is inserted, especially if the code is C88044AB specifically. If it is, ensure you have all of the necessary files for what you are trying to do.
:If you are specifically getting 0xc8804471 when opening an out-of-region game, it means it needs [[3DS:Setting Game Locales|locale emulation]] to function properly.<br>If you do have the files and it is happening to a digital title, [[3DS:Safe Mode|do a Safe Mode update.]]<br>If you do have the files and it is happening to a cartridge, either your 3DS or the cartridge likely has a hardware issue.
|-
| 0xC8804478
| The app you tried to open or system software it relies on is missing.
:If this occurs when you open any DS game or DS Download Play, follow [[3DS:TWLFix|TWLFix]].
:If this occurs after doing a manual CTRTransfer, Lazarus3DS, or the nim module errors, check in GodMode9 whether the file path <code>1:/private/movable.sed</code> exists. If it does not, you will need to manually restore <code>movable.sed</code> from a backup. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask for help with this.
|-
| 0xC8A04573
| Your SD card is formatted strangely.
:To fix, [[Formatting an SD card|reformat the SD card.]] If this does not work, [[Checking SD card integrity|test the SD card for errors.]]
|-
| 0xC8A0802B
| If this happened while installing an application, your <code>title.db</code> does not exist or is corrupted.
:To fix, follow one of the two following sets of instructions. The second one will delete all installed games/apps as a side effect, but is significantly faster and simpler.
:#[[3DS:Rebuild Title Database|rebuild <code>title.db</code>]] and then try again.
:#Open GodMode9, go into the file path <code>[A:] SYSNAND SD/dbs/</code> and delete any existing <code>title.db</code>, then press {{B|R}}+{{B|Y}}, choose '''Create a dummy file''', and name this file <code>title.db</code> - leave the file size at 0. Once the file is created, press {{B|START}} to reboot, go into System Settings -> Data Management -> Nintendo 3DS -> Software, and choose '''Yes''' if a prompt about management information appears.
|-
|0xC8A11BEF
|Occurs when attempting to use DLP services with an out-of-region game. This issue is not fixable currently.
|-
| 0xC92044EB<br>0xC92044FA<br>0xC960454?
| Your SD card is set to read-only or is faulty.
:To fix, make sure the slider on the left side of the SD card is pushed up, use a different SD adapter if you are currently using one, and [[Checking SD card integrity|test the SD for errors]] if it is not read-only.
:If the error still happens, the SD card is likely faulty. If it is also read-only, it has permanently protected itself to prevent data corruption. Either way, back up its contents and get a new SD.
If the error is happening when launching a cartridge, especially if the error code is 0xC960454?, delete any updates or DLC to see if the cartridge works as they could be corrupt or faulty. If this succeeds, reinstall them from eShop and ensure the cartridge still works.
|-
| 0xD860446?
| You are attempting to use more processing power than the console currently has available.
:To fix, ensure you are not using a mod that is designed for an emulator rather than native hardware. If you are using such a mod, either toggle off any "Extra RAM" setting or use a different mod.
|-
| 0xD8E0806A
| You have developer UNITINFO enabled and are trying to install a retail game.
:To fix, go into the file <code>sd:/luma/config.ini</code> and set the variable <code>use_dev_unitinfo</code> to 0.
|-
| 0xD900458?
| The app you tried to open, its savedata, or an update file for it is corrupted.
:To fix, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
|-
| {{anchor|0xF9605002}}0xF9605002
| If attempting to use any camera features, your camera hardware is damaged or dead.
|}

[[Category:Unbricking]]
[[Category:Nintendo 3DS troubleshooting]]

3DS:Error screens/Luma3DS exception screen

2024-10-06T21:21:31Z

Thepikachugamer: LayeredFS is not the right word here

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.

== Reading a Luma3DS exception screen ==

A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
* '''Processor:''' What part of the system is causing the exception. The two processors are:
** '''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
** '''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
** '''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
** '''prefetch abort''': Caused by an attempt to execute a CPU instruction that was marked as invalid. Often related to conflicts between CFW and other software.
** '''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually halting because it tripped a pre-defined error condition. Often related to damage to NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
** '''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable error and forcibly halting to avoid causing damage. Can be related to any of several things, but hardware issues are the most likely.
** '''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software missing its required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
* '''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
* '''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
** '''fs''': The filesystem, i.e. either the SD card or the NAND.
** '''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
** '''loader''': The service that opens apps, meaning the app most recently opened has an issue.
** '''nwm''': Networking services, almost always Wi-Fi.
** '''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
* '''Registers (R0-R12/SP/LR/PC/CPSR/FPEXC)''': Usually just internal data that's not worth reading, though R0 is the most likely of them to contain useful data. There are certain notable exceptions that aren't mentioned in the list of known errors, however:
** If the value <code>000400??</code> (the ? marks can be any number) appears in any of the registers, it likely refers to the first half of a title ID - check the value of the register after it to ensure this. If it is a title ID, it can be used to narrow down the original cause of an error.
** If the value of any register starts with the letter C, D, E, or F (even if it isn't in R0) and doesn't look completely random, it may be an error code - this is more likely if the value starts with C or D. You may want to check it manually, as if it is an error code, it can likely help in troubleshooting.

== Known Errors ==

In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] for further assistance.}}
----

=== <big>Arm9</big> ===

Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
* A system save located on the NAND in <code>[1:]/data</code> has a problem.
* System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
* The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
** To fix, create this folder.
* System titles have been deleted.
** To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (svcBreak)</h5>
* The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
** To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
* <code>SYSNAND CTRNAND</code> has bad CMACs.
** To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
* The console likely has a hardware issue.

<h5>undefined instruction</h5>
* The console likely has a hardware issue, or corrupted sysmodules. Try performing a [[3DS:CTRTransfer|CTRTransfer]] to see if it resolves the issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

=== <big>Arm11</big> ===

All Arm11 errors are sorted by their '''current process'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>act</h5>
* Your NNID(s)' stored data is misconfigured or being interfered with.
** To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on [[3DS:Luma3DS/Configuration|the Luma configuration menu]].
*** If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
* The current firmware version is too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
** If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]

<h5>camera</h5>
* Potential hardware issues, or an instance of ShutTheCamUp is crashing.
** Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
*** If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>cfg</h5>
* Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
** To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
*** If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
* Potential hardware problems, or an instance of rehid is crashing.
** First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
*** If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation.

<h5>i2c/gsp/mcu/pxi/spi/</h5>
* The console has a serious hardware issue that is likely not easily fixable.
** Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

<h5>loader</h5>
* <h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.

<h5>menu</h5>
* <h6>data abort</h6>
** The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
** The HOME Menu's extra data is corrupted.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
** An installed application is corrupted or otherwise broken.
*** To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
* <h6>prefetch abort</h6>
** An installation of Menuhax is conflicting with the custom firmware.
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
* <h6>prefetch abort (svcBreak)</h6>
** If <code>R5</code> contains <code>D900458B</code>: The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
*** To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**System titles are missing. Perform a [[3DS:Safe Mode|Safe Mode update]].
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>ns</h5>
* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
** To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
* The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
** To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>3dsx_app</h5>
* The <code>.3dsx</code> file that was most recently opened is corrupted.
** To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**: If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>app/CtrApp</h5>
* If not <code>prefetch abort (svcBreak)</code>: The app most recently opened is trying to use broken software.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.
**: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
* If <code>prefetch abort (svcBreak)</code>: The app most recently opened is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

<h5>GARDEN</h5>
* Animal Crossing's game data or savedata is having issues.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
*** If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to recreate the error without the SD card inserted.<br>If the error stops after the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>Kujira/Joker/niji_loc</h5>
* The app most recently opened has an issue of some kind.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]]
*** If the error yet still happens, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>loader</h5>

* <h6>undefined instruction</h6>
** The app most recently opened has an issue. If the value of R0 starts with C or D, it is an error code, and has a chance of being an error code if the value starts with E or F. Here are some common values for R0:
*** <code>D9004587</code>: When trying to open a game: The game is corrupted, or it's seed is not imported.
**** See: [[3DS:Fixing corrupted games]]
*** <code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
**** To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
*** <code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
**** To fix, redownload the app you are trying to launch. If this happens when you try to open the Homebrew Launcher itself, see the error above.
*** Most of the other possible error codes that can appear here are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|the ErrDisp page]].
* <h6>prefetch abort (svcBreak)</h6>
**The code or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Redownload any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].

<h5>mset</h5>
* '''If not caused in Nintendo DS Profile:''' System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
* '''If caused in Nintendo DS Profile:''' Your NVRAM is either corrupted or damaged in hardware. Run [[3DS:ctrcheck|ctrcheck]] - if its results do not include <code>Critical: NVRAM is inaccessible</code>, then follow [[3DS:NVRAM|the Fix NVRAM guide]].

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pxi</h5>
* Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>pm</h5>
* The software you have launched may be missing required files. If the value in R0 is <code>E0E01BF5</code>, this is extremely likely to be the cause.

<h5>qtm/cam</h5>
* The camera's hardware is damaged or dead.
** To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>swkbd</h5>
* The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
[[Category:Unbricking]]
{{Short description|Guide to the CFW error handler}}

3DS:Movable Moveover

2024-10-06T20:34:34Z

Thepikachugamer: indentation

{{hatnote|This page is a guide to transferring data between systems without doing a System Transfer, and usually should only be done if the '''source console''' you are transferring from is nonfunctional or you only have its SD.
<br>If you do not have a specific reason to follow this guide (i.e. both consoles are usable), do [[3DS:System Transfer|a System Transfer]] instead.}}
{{shortcut|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.
<br>Additionally, ensure you have read the following three warnings to have a full understanding of the potential risks of this guide.

{{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 (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>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.
<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>
However, note that even this method will '''not''' bypass the issues of using a Bruteforce Movable <code>movable.sed</code>.}}

If you are confused in any way, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask for help in the 3ds-assistance channels.

== What You Need ==

* Two 3DS consoles, both modded with [[3DS:Luma3DS|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 [[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]]
** If you already have the '''source console's''' <code>movable.sed</code> outside of a <code>.exefs</code> file, you can use that directly
* 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 [https://raw.githubusercontent.com/nh-server/scripts/main/3DS/MovableMoveover.gm9 MovableMoveover.gm9]
** To download, right-click/long-press the link and select <code>Save link as...</code>, or similar, then rename the downloaded file to <code>MovableMoveover.gm9</code> if it is not named exactly that

== Instructions ==

=== Section I - Prep Work ===

{{info|Follow these instructions on the '''destination console''' only.}}

# Power off your console and insert your SD card into your computer
# 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>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>
#* 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 - Setup Script ===
# Hold {{B|Start}}, and while holding {{B|Start}}, power on your console
# 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
# 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
# Press {{B|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

{{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.}}

=== Section III - Reinstating Apps ===

# Launch the '''Download Play''' application
# Wait until you see the two buttons
#* Do not press either of the buttons
# Press {{B|L|DOWN|SELECT}} at the same time to open the Rosalina menu
# Select '''Miscellaneous options'''
# Select '''Switch the hb. title to the current app.'''
# Press {{B|B}} to continue
# Press {{B|B}} to return to the Rosalina main menu
# Press {{B|B}} to exit the Rosalina menu
# Press {{B|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 {{B|START}} to exit
# Reboot your console

{{success|text=The moveover is complete. Congratulations for performing a complex procedure.}}

[[Category:Nintendo 3DS guides]]

User:Thepikachugamer/Installing boot9strap (OldLoader)

2024-09-10T22:29:46Z

Thepikachugamer:

== What you Need ==

* The latest release of [https://github.com/d0k3/OldLoader/releases/latest OldLoader]
* The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9]
* The latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS]
* The latest release of [https://github.com/SciresM/boot9strap/releases/latest boot9strap]
* Something that launches Arm9 .bin payloads (eg. nimdsphax)
** For some exploits like MSET9 and arm9loaderhax, the file <code>SafeB9SInstaller.bin</code> should be named differently

== <big>'''Instructions'''</big> ==

=== Section I - Prep Work ===

# Power off your device
# Insert your SD card into your computer
# Copy <code>OldLoader.bin</code> from the OldLoader <code>.zip</code> to the root of your SD card, and rename it to <code>SafeB9SInstaller.bin</code>
# Copy <code>boot.firm</code> and <code>boot.3dsx</code> from the Luma3DS <code>.zip</code> to the root of your SD card, and rename <code>boot.firm</code> to <code>luma.firm</code>
# Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the root of your SD card, and rename it to <code>boot.firm</code>
# Create a folder named <code>boot9strap</code> on your SD card
# Copy <code>boot9strap.firm</code> and <code>boot9strap.firm.sha</code> to the newly-created <code>boot9strap</code> folder
# Safely eject your SD card from your computer
# Reinsert your SD card into your device
# Power on your device

=== Section II - Launching <s>SafeB9SInstaller</s> GodMode9 ===

# Launch <code>SafeB9SInstaller.bin</code> through any method
# If the exploit was successful, you will have booted into GodMode9

=== Section III - Installing boot9strap ===

# Navigate to <code>[0:] SDCARD</code> -> <code>boot9strap</code> inside GodMode9
# Press A on <code>boot9strap.firm</code>
# Select "Calculate SHA-256"
# The verification should pass.
# Press A on <code>boot9strap.firm</code> again
# Select <code>FIRM Image Options</code> -> <code>Install FIRM</code> -> <code>Install to both</code>
# Press A to unlock SysNAND (lvl3) writing, then input the given key combo
# Once the installation has succeeded, press A to continue
# Press B to return to <code>[0:] SDCARD</code>
# Press X on <code>boot.firm</code> to delete it
# Press R+X on <code>luma.firm</code>, and rename it to <code>boot.firm</code>
# Press START to reboot your console. Your console should boot to the Luma3DS configuration menu
#*Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
#*For the purpose of this guide, these settings will be left on default settings
#*If your device shuts down when you try to power it on, try re-copy <code>boot.firm</code> from the Luma3DS <code>.zip</code> to the root of your SD card
{{Luma3DS is default}}
-----<span style="font-size:200%;">Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]</span>

SD Clean/Linux

2024-08-25T18:31:35Z

Thepikachugamer: There's a difference between the partition table and the partition

This is an add-on section for completely recreating an SD card's filesystem using fdisk and mkfs. This should only be done if formatting does not fix your issue or is not possible for some reason.

This page is for Linux users only. If you are not on Linux, see the [[SD Clean/Windows|Windows]] and/or [[SD Clean/Mac|Mac]] pages instead.

== Instructions ==
{{warning|Before beginning these steps, copy all of your SD card's contents to a folder on your computer.}}

{{warning|The commands in this guide are case-sensitive. Enter them exactly as written, or there may be unintended consequences.}}

# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 29.7G 0 disk
└─mmcblk0p1 179:1 0 29.5G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Type <code>sudo umount /dev/<device name>*</code> (do not replace the <code>*</code>)
# Type <code>sudo fdisk /dev/<device name></code>.
# Enter <code>o</code>, then enter <code>n</code> and go through all the resulting prompts without changing settings.
#* If it asks whether to remove a VFAT signature, choose to remove it.
# Once you are back at fdisk's main menu, enter <code>t</code> and then enter <code>0c</code>
# Enter <code>a</code> and then <code>p</code> - observe the output, and make sure the device is now formatted correctly: : {{#tag:syntaxhighlight|
Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x########

Device Boot Start End Sectors Size Id Type
/dev/<partition name> 8192 62333951 62325760 29.7G c W95 FAT32 (LBA)
|lang=text}}
# If there are no issues, enter <code>w</code> - this will save changes and exit the fdisk prompt.
# Type <code>sudo mkfs.vfat /dev/<partition name> -s 64</code> to reformat the new partition.
#* If the SD card is over 32GB in size, change </code>64</code> to <code>128</code>
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card.
# Copy your data back onto the SD card.

Formatting an SD card/Linux

2024-08-25T18:22:27Z

Thepikachugamer: There's a difference between the partition table and the partition

This is an add-on section for formatting an SD card to FAT32.

This page is for Linux users only. If you are not on Linux, check out the [[Special:MyLanguage/Formatting an SD card/Windows|Windows]] or [[Special:MyLanguage/Formatting an SD card/Mac|Mac]] pages.

== Instructions ==
{{warning|Before beginning these steps, copy all of your SD card's contents to a folder on your computer.}}

{{warning|The commands in this guide are case-sensitive. Enter them exactly as written, or there may be unintended consequences.}}
<tabber>
|-|fdisk=

<span>
# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 29.7G 0 disk
└─mmcblk0p1 179:1 0 29.5G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Type <code>sudo umount /dev/<device name>*</code> (do not replace the <code>*</code>)
# Install the <code>fdisk</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo fdisk /dev/<device name></code>
# Enter <code>t</code> and then enter <code>0c</code>
# Enter <code>a</code> and then <code>p</code> - observe the output, and make sure the device is now formatted correctly: {{#tag:syntaxhighlight|
Disk /dev/mmcblk0: 29.72 GiB, 31914983424 bytes, 62333952 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x########

Device Boot Start End Sectors Size Id Type
/dev/<partition name> 8192 62333951 62325760 29.7G c W95 FAT32 (LBA)
|lang=text}}
# If there are no issues, enter <code>w</code> - this will save changes and exit the fdisk prompt
# Type <code>sudo mkfs.vfat /dev/<partition name> -s 64</code> to reformat the new partition
#* If the SD card is over 32GB in size, change <code>64</code> to <code>128</code>
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card
# Copy your data back onto the SD card
</span>

|-|cfdisk=

<span>
# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 29.7G 0 disk
└─mmcblk0p1 179:1 0 29.5G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Install the <code>cfdisk</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo cfdisk /dev/<device name></code>
# Choose the <code>Delete</code> option and delete any existing partitions
# Choose the <code>New</code> option, keep partition size at the recommended size, and choose primary partition type
# Choose the <code>Type</code> option, scroll up until you see <code>c W95 FAT32 (LBA)</code> and select it
# Finally, choose the <code>Write</code> option.
# Choose the <code>Quit</code> option
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card
# Copy your data back onto the SD card
</span>

|-|parted=

<span>
# Make sure your SD card is '''not''' inserted
# Open a terminal window and type <code>watch lsblk</code>
# Insert the SD card and watch for a new device appearing in lsblk
# Observe the output for the new device. It should match something like this: {{#tag:syntaxhighlight|
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT
mmcblk0 179:0 0 29.7G 0 disk
└─mmcblk0p1 179:1 0 29.5G 0 part /run/media/user/FFFF-FFFF
|lang=text}}
# Take note of the name of the device that now appears. In our example above, it was <code>mmcblk0</code>, but it could show up as <code>sda</code> or <code>sdb</code>, if you use a USB adapter
#* If <code>RO</code> is set to 1, make sure the lock switch is not slid down
# Hit CTRL + C to exit the menu
# Install the <code>parted</code> and <code>dosfstools</code> packages using your package manager of choice
# Type <code>sudo parted /dev/<device name> mklabel msdos</code>
# Type <code>sudo parted -a opt /dev/<device name> mkpart primary fat32 0% 100%</code>
# Type <code>sudo eject /dev/<device name></code>, then remove and reinsert the SD card.
# Copy your data back onto the SD card.
</span>
</tabber>
{{hg imported|Guide_3DS}}

[[Category:General guides]]

3DS:WINERROR234

2024-08-06T13:42:59Z

Thepikachugamer: Change redirect

#REDIRECT [[3DS:Troubleshooting/WinError 234]]

User:Thepikachugamer/WinError 234

2024-08-06T13:41:50Z

Thepikachugamer: Thepikachugamer moved page User:Thepikachugamer/WinError 234 to 3DS:Troubleshooting/WinError 234: Happens often enough by now

#REDIRECT [[3DS:Troubleshooting/WinError 234]]

3DS:Troubleshooting/WinError 234

2024-08-06T13:41:50Z

Thepikachugamer: Thepikachugamer moved page User:Thepikachugamer/WinError 234 to 3DS:Troubleshooting/WinError 234: Happens often enough by now

When injecting MSET9 on Windows 10 and up, the script sometimes crashes with this error:

<code>OSError: [WinError 234] More data is available: '[X]:\\Nintendo 3DS/################################/\uffff\ufaff餑䠇䚅敩 ꄈ∁䬅䞘䙨䙙ꫀᰗ䙃䰃䞠䞸退ࠊꁱࠅ캙ࠄsdmc退ࠊb9'</code>

This seems to happen because of the in-beta UTF-8 support in Windows. Instructions to disable it are as follows:

# Open Settings
# Navigate to "Time and Language" --> "Language and Region" --> "Administrative language settings"
# In the new dialog that pops up, select "Change system locale...."
# Ensure that "Beta: Use Unicode UTF-8 for worldwide language support is disabled"
# Press OK.
# If prompted to restart your computer, do so.

The injection should now work properly.

3DS:TWLFix

2024-07-11T18:26:45Z

Thepikachugamer: direct user to full Unable to update console page

== Required Reading ==
These instructions will fix your DS mode using [https://github.com/lifehackerhansol/TWLFix-3DS-nimhax/tree/nimhax TWLFix-3DS-nimhax] or [https://github.com/MechanicalDragon0687/TWLFix-CFW TWLFix-CFW]. Credits go to [https://github.com/MechanicalDragon0687 MechanicalDragon0687] for creating the apps.

It uninstalls all DS mode system titles and then reinstalls them using Nintendo's Servers by updating the console. Updating not only updates the version, but also repairs broken or missing system titles if the system finds them.

You need either custom firmware or Homebrew Launcher access to launch TWLFix.

== Instructions==
<tabber>
|-|Custom Firmware=
=== What You Need ===

* The Homebrew Launcher on your HOME menu
* The latest release of [https://github.com/MechanicalDragon0687/TWLFix-CFW/releases/ TWLFix-CFW]

=== Instructions ===

# Power off your console
# Insert your SD card into your computer
# Copy <code>TWLFix-CFW.3dsx</code> into the <code>/3ds/</code> folder on your SD card
# Reinsert your SD card into your console
# Power on your console
# Launch the '''Homebrew Launcher'''
# Launch ''TWLFix CFW Edition'' from the list of homebrew
# Press {{B|A}} to begin
# When the process is completed, press {{B|START}} to reboot
# '''''REQUIRED:''''' Update your console by opening '''System Settings''' -> '''Other Settings''', then going to the last page and selecting '''System Update'''
#* '''This step MUST be completed even if your console is already on the latest version'''
#* Updates while using B9S + Luma3DS (what you have) are safe
#* If the update gives you an error, see [[3DS:Troubleshooting#Unable to update console|Unable to update console]]
# When the process is completed, your DS mode should be working again
#* If it still does not work, follow the [[3DS:TWLFix/Alternate|alternate TWLFix]] page

|-|Userland (PicHaxx, Steelhax, etc.)=
=== What You Need ===

* A way to access the Homebrew Launcher
* The latest release of [https://github.com/lifehackerhansol/TWLFix-3DS-nimhax/releases/download/v1.1-nimhaxb1/TWLFix-3DS-nimhax.zip TWLFix-3DS-nimhax] (direct download)

=== Instructions ===

# Power off your console
# Insert your SD card into your computer
# Copy the <code>TWLFix-3DS</code> folder from the TWLFix-3DS-nimhax <code>.zip</code> into the <code>/3ds/</code> folder on your SD card
# Reinsert your SD card into your console
# Power on your console
# Open the '''Homebrew Launcher''' through your method of choice
# Launch ''TWLFixer'' from the list of homebrew
# Press {{B|A}} to begin
# When the process is completed, press {{B|START}} to reboot
# '''''REQUIRED:''''' Update your console by opening '''System Settings''' -> '''Other Settings''', then going to the last page and selecting '''System Update'''
#* '''This step MUST be completed even if your console is already on the latest version'''
#* If the update gives you an error, set both your DNS settings and Proxy settings to '''Auto'''
# When the process is completed, your DS mode should be working again
#* If it still does not work, you will need to [[3dsguide:index|install CFW]] in order to follow the [[3DS:TWLFix/Alternate|alternate TWLFix]] page
</tabber>

[[Category:Nintendo 3DS guides]]

3DS:Troubleshooting/WinError 234

2024-06-22T04:01:00Z

Thepikachugamer: Created page with "When injecting MSET9 on Windows 10 and up, the script sometimes crashes with this error: <code>OSError: [WinError 234] More data is available: '[X]:\\Nintendo 3DS/################################/\uffff\ufaff餑䠇䚅敩 ꄈ∁䬅䞘䙨䙙ꫀᰗ䙃䰃䞠䞸退ࠊꁱࠅ캙ࠄsdmc退ࠊb9'</code> This seems to happens because of Windows's in-beta UTF-8 support. Instructions to disable it are as follows: # Open Settings # Navigate to "Time and Language" --> "Language and..."

When injecting MSET9 on Windows 10 and up, the script sometimes crashes with this error:

<code>OSError: [WinError 234] More data is available: '[X]:\\Nintendo 3DS/################################/\uffff\ufaff餑䠇䚅敩 ꄈ∁䬅䞘䙨䙙ꫀᰗ䙃䰃䞠䞸退ࠊꁱࠅ캙ࠄsdmc退ࠊb9'</code>

This seems to happens because of Windows's in-beta UTF-8 support. Instructions to disable it are as follows:

# Open Settings
# Navigate to "Time and Language" --> "Language and Region" --> "Administrative language settings"
# In the new dialog that pops up, select "Change system locale...."
# Ensure that "Beta: Use Unicode UTF-8 for worldwide language support is disabled"
# Press OK.
# If prompted to restart your computer, do so.

The injection should now be working properly.

User:Thepikachugamer/Installing boot9strap (MSET9-Wii)/Troubleshooting

2024-06-05T20:25:10Z

Thepikachugamer:

=== Mounting SD card failed! (13) ===
Try [[Formatting an SD card|reformat your SD card to FAT32.]]

=== Error #01: Nintendo 3DS folder not found! ===
Ensure that your 3DS is recognizing your SD card. Since it's highly likely that your SD card FAT32 at this point, ensure that:

* The lock slider on your SD card is in the unlocked (up) position.
* You are inserting the SD card into the 3DS's SD card slot, and not a flashcart. ([https://en-americas-support.nintendo.com/app/answers/detail/a_id/271/~/how-to-insert-an-sd-card-or-microsd-card Nintendo Support: How to insert an SD card or microSD card])
* the 3DS's SD card slot is not dusty or clogged.

After that, try power on the console with the SD card inserted. If the Nintendo 3DS folder still does not exist, then the SD card slot may simply be broken.

=== Error #04: No HOME menu extdata found! ===
Hold {{Key press|L|R|Down|B}} while powering on your 3DS. When prompted to reset the HOME menu management info, select Reset.

=== Error #05: No Mii Maker extdata found! ===
Ensure that you are launching Mii Maker (not StreetPass Mii Plaza!) with your SD card inserted.

=== Error #06: Insufficient SD card space! ===
At minimum, 16 megabytes is required to make a copy of the files required to trigger MSET9. It is recommended to free up at least 2x that amount, so that you won't be barred from uninjecting MSET9.

The NAND backup created by Finalizing setup requires up to ~1.3GB of space, so you should ideally free up that much.

=== Error #07: You have multiple (#) ID0's! ===
This usually happens because the SD card has been use in multiple 3DS consoles (or the console has been formatted since you last used the SD card).

Consult: [[3DS:Troubleshooting/multiple ID0|3DS:Troubleshooing/Multiple ID0]]

=== Error #08: One or more files are missing or malformed! ===
Please re-download the [https://github.com/zoogie/MSET9/releases/latest MSET9 Release <code>.zip</code>] and extract the files to the root of your SD card. If you are prompted to replace any files or merge any folders, do so.

=== Information #10: No title database! ===
This usually happens when there is no eShop software on your SD card.

The visual guide to reset the title database is [[3dsguide:images/screenshots/database-reset.jpg|here.]]

=== Error #12: You have multiple (#) ID1's! ===
Consult: [[3DS:Troubleshooting/multiple ID1]]

User:Thepikachugamer/Installing boot9strap (MSET9-Wii)

2024-06-01T17:46:48Z

Thepikachugamer:

{{Page WIP}}

==What you Need==

*The latest release of [https://github.com/zoogie/MSET9/releases/latest MSET9] (the Release <code>.zip</code> file)
*The latest release of [https://github.com/Naim2000/MSET9-Wii/releases/latest MSET9-Wii] (the <code>.dol</code> file)
*a Wii with The Homebrew Channel installed

==Instructions==

===Section I - Prep Work===

#Power off your 3DS
#Insert your SD card into your computer
#Copy everything from the Release <code>.zip</code> file to the root of your SD card
#Create a folder named <code>apps</code> on your SD card (if it does not exist already)
#Create a folder named <code>MSET9-Wii</code> within the <code>/apps/</code> folder on your SD card
#Copy the MSET9-Wii <code>.dol</code> file to the <code>/apps/MSET9-Wii/</code> folder on your SD card, and rename it to <code>boot.dol</code>
#Safely eject your SD card from your computer, and insert it into your 3DS

===Section II - Creating Extra Data===

#Power on your 3DS with your SD card inserted
#Open Mii Maker
#Wait for your 3DS to reach the "Welcome to Mii Maker" screen, then exit Mii maker
##You may see a "Creating extra data..." prompt, which indicates that the necessary data has been created
##If you only reach the normal Mii maker screen, exit Mii Maker and continue to the next step
#Launch System Settings
#Navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Extra Data</code>
#Ensure that Mii Maker is in the list of extra data
#Eject your SD card from your 3DS
#Insert your SD card into your Wii
#On your Wii, launch the Homebrew Channel, and launch MSET9-Wii from the Homebrew Channel.
#*If you are using the grid view, the application will have no icon.
#Select the option that corresponds to your 3DS's model and system version
#If you are asked to <code>Inject MSET9 now?</code>, press {{Key press|B}} to cancel.
#*If you receive any errors in the sanity checks, follow the provided instructions, or consult the [[/Troubleshooting|troubleshooting]] page.
#Press {{Key press|HOME}} twice to exit the app
#Eject your SD card from your Wii

===Section III - MSET9===
{{Warning|text=Following these steps precisely is crucial to getting MSET9 to trigger. If you believe you made an error, restart this section.}}

#On the HOME menu, hover over System Settings ('''do not launch it!''')
#Power off your 3DS, then power it back on
#Press {{Key press|A}} to launch System Settings
#Navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Extra Data</code>
#'''Do not press any buttons or touch the screen.'''
#Eject your SD card from your 3DS
#Insert your SD card into your Wii
#Launch MSET9-Wii from the Homebrew Channel
#Select the option that corresponds to your 3DS's model and system version
#When prompted to <code>Inject MSET9 now?</code>, press {{Key press|A}} to confirm.
#You should see <code>[OK] MSET9 successfully injected, have fun!</code>
#*Do not turn your Wii off. We will be using it again soon.
#Eject your SD card from your Wii, and insert it into your 3DS
#If the exploit was successful, your 3DS will have booted into the SafeB9SInstaller.
#*If you get stuck on a loading screen for longer than 10 seconds, skip to Section V

===Section IV - Installing boot9strap===

#When prompted, input the key combo given on the top screen to install boot9strap
#Once it is complete, press (A) to reboot your 3DS
#Your 3DS should have rebooted into the Luma3DS configuration menu
#*Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
#*For the purpose of this guide, these settings will be left on default settings
#*If your 3DS shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the Luma3DS <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot
{{Luma3DS is default}}

===Section V - Removing MSET9===

#Power off your 3DS
#Eject your SD card from your 3DS, and insert it into your Wii
#Press {{Key press|A}} to continue
#You should see <code>[OK] MSET9 has been removed!</code>
#When prompted to <code>Try again?</code>, press {{Key press|B}} to cancel.
#Press {{Key press|Home}} to return to the Homebrew Channel.
#*If you were unable to boot into the SafeB9SInstaller, return to section III
----
<span style="font-size:200%;">Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]</span>

User:Thepikachugamer/Installing boot9strap (MSET9-Wii)/Troubleshooting

2024-06-01T17:13:58Z

Thepikachugamer:

=== Failed to mount SD card! (13) ===
Try [[Formatting an SD card|reformat your SD card to FAT32.]]

=== Error #01: Nintendo 3DS folder not found! ===
Ensure that your 3DS is recognizing your SD card. Since it's highly likely that your SD card FAT32 at this point, ensure that:

* The lock slider on your SD card is in the unlocked (up) position.
* You are inserting the SD card into the 3DS's SD card slot, and not a flashcart. ([https://en-americas-support.nintendo.com/app/answers/detail/a_id/271/~/how-to-insert-an-sd-card-or-microsd-card Nintendo Support: How to insert an SD card or microSD card])
* the 3DS's SD card slot is not dusty or clogged.

After that, try power on the console with the SD card inserted. If the Nintendo 3DS folder still does not exist, then the SD card slot may simply be broken.

=== Error #04: No HOME menu extdata found! ===
Hold {{Key press|L|R|Down|B}} while powering on your 3DS. When prompted to reset the HOME menu management info, select Reset.

=== Error #05: No Mii Maker extdata found! ===
Ensure that you are launching Mii Maker (not StreetPass Mii Plaza!) with your SD card inserted.

=== Error #06: Insufficient SD card space! ===
At minimum, 16 megabytes is required to make a copy of the files required to trigger MSET9. It is recommended to free up at least 2x that amount, so that you won't be barred from uninjecting MSET9.

The NAND backup created by Finalizing setup requires up to ~1.3GB of space, so you should ideally free up that much.

=== Error #07: You have multiple (#) ID0's! ===
This usually happens because the SD card has been use in multiple 3DS consoles (or the console has been formatted since you last used the SD card).

Consult: [[3DS:Troubleshooting/multiple ID0|3DS:Troubleshooing/Multiple ID0]]

=== Error #08: One or more files are missing or malformed! ===
Please re-download the [https://github.com/zoogie/MSET9/releases/latest MSET9 Release <code>.zip</code>] and extract the files to the root of your SD card. If you are prompted to replace any files or merge any folders, do so.

=== Information #10: No title database! ===
This usually happens when there is no eShop software on your SD card.

The visual guide to reset the title database is [[3dsguide:images/screenshots/database-reset.jpg|here.]]

=== Error #12: You have multiple (#) ID1's! ===
Consult: [[3DS:Troubleshooting/multiple ID1]]

User:Thepikachugamer/Installing boot9strap (MSET9-Wii)/Troubleshooting

2024-06-01T16:15:37Z

Thepikachugamer: (browser started lagging so i'm gonna reopen it)

User:Thepikachugamer/Installing boot9strap (MSET9-Wii)

2024-06-01T05:02:18Z

Thepikachugamer: Why did i make 5 sections instead of just 4

{{Page WIP}}

==What you Need==

*The latest release of [https://github.com/zoogie/MSET9/releases/latest MSET9] (the Release <code>.zip</code> file)
*The latest release of [https://github.com/Naim2000/MSET9-Wii/releases/latest MSET9-Wii] (the <code>.dol</code> file)
*a Wii with The Homebrew Channel installed

==Instructions==

===Section I - Prep Work===

#Power off your console
#Insert your SD card into your computer
#Copy everything from the Release <code>.zip</code> file to the root of your SD card
#Create a folder named <code>apps</code> on your SD card (if it does not exist already)
#Create a folder named <code>MSET9-Wii</code> within the <code>/apps/</code> folder on your SD card
#Copy the MSET9-Wii <code>.dol</code> file to the <code>/apps/MSET9-Wii/</code> folder on your SD card, and rename it to <code>boot.dol</code>
#Safely eject your SD card from your computer
#Insert your SD card into your console, and power it on

===Section II - Creating Extra Data===

#Power on your console with your SD card inserted
#Open Mii Maker
#Wait for your console to reach the "Welcome to Mii Maker" screen, then exit Mii maker
##You may see a "Creating extra data..." prompt, which indicates that the necessary data has been created
##If you only reach the normal Mii maker screen, exit Mii Maker and continue to the next step
#Launch System Settings
#Navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Extra Data</code>
#Ensure that Mii Maker is in the list of extra data
#Eject your SD card from your console
#Insert your SD card into your Wii
#On your Wii, launch the Homebrew Channel, and launch MSET9-Wii from the Homebrew Channel.
#*If you are using the grid view, the application will have no icon.
#Select the option that corresponds to your console's model and system version
#If you are asked to <code>Inject MSET9 now?</code>, press {{Key press|B}} to cancel.
#*If you receive any errors in the sanity checks, follow the provided instructions, or consult the [[User:Thepikachugamer/Installing boot9strap (MSET9-Wii)/Troubleshooting|troubleshooting]] page.
#Press {{Key press|HOME}} twice to exit the app
#Eject your SD card from your Wii

===Section III - MSET9===
{{Warning|text=Following these steps precisely is crucial to getting MSET9 to trigger. If you believe you made an error, restart this section.}}

#On the HOME menu, hover over System Settings ('''do not launch it!''')
#Power off your console, then power it back on
#Press {{Key press|A}} to launch System Settings
#Navigate to <code>Data Management</code> -> <code>Nintendo 3DS</code> -> <code>Extra Data</code>
#'''Do not press any buttons or touch the screen.'''
#Eject your SD card into your 3DS
#Insert your SD card into your Wii
#Launch MSET9-Wii from the Homebrew Channel
#Select the option that corresponds to your console's model and system version
#When prompted to <code>Inject MSET9 now?</code>, press {{Key press|A}} to confirm.
#You should see <code>[OK] MSET9 successfully injected, have fun!</code>
#Eject your SD card from your Wii, and insert it into your console
#If the exploit was successful, your console will have booted into the SafeB9SInstaller.
#*If you get stuck on a loading screen for longer than 10 seconds, skip to Section V

===Section IV - Installing boot9strap===

#When prompted, input the key combo given on the top screen to install boot9strap
#Once it is complete, press (A) to reboot your device
#Your device should have rebooted into the Luma3DS configuration menu
#*Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
#*For the purpose of this guide, these settings will be left on default settings
#*If your device shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the Luma3DS <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot
{{Luma3DS is default}}

===Section V - Removing MSET9===

#Insert your SD card back into your Wii
#Press {{Key press|A}} to continue
#You should see <code>[OK] MSET9 has been removed!</code>
#When prompted to <code>Try again?</code>, press {{Key press|B}} to cancel.
#Press {{Key press|Home}} to return to the Homebrew Channel.

3DS:Error screens/Luma3DS exception screen

2024-05-22T14:44:41Z

Thepikachugamer: typo on loader undefined instr

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.
==Reading a Luma3DS exception screen==
A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
* '''Processor:''' What part of the system is causing the exception. The two processors are:
**'''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
**'''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
**'''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
**'''prefetch abort''': Caused by an attempt to execute an invalid CPU instruction. Often related to conflicts between CFW and other software.
**'''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually terminating code because it matched a pre-defined condition. Often related to errors in NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
**'''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable fatal error and forcibly shutting down to avoid damage. Can be related to any of several things, but hardware issues are the most likely.
**'''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software not having the required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
*'''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
*'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
**'''fs''': The filesystem, i.e. either the SD card or the NAND.
**'''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
**'''loader''': The service that opens apps, meaning the app most recently opened has an issue.
**'''nwm''': Networking services, almost always Wi-Fi.
**'''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
*'''R0''': Usually just internal data that's not worth reading. There are two notable exceptions, however:
**'''Arm11 loader exception''': If R0's contents start with a C or D, R0 is an error code. This code usually gives the exact cause of the issue.
**'''Arm11 pm exception''': If R0's contents are <code>E0E01BF5</code>, <code>boot.firm</code> is guaranteed to be too outdated to work.

== Known Errors ==
In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] for further assistance.}}
----

=== <big>Arm9</big> ===
Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
* A system save located on the NAND in <code>[1:]/data</code> has a problem.
* System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
* The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
** To fix, create this folder.
* System titles have been deleted.
** To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (svcBreak)</h5>
* The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
** To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
* <code>SYSNAND CTRNAND</code> has bad CMACs.
** To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
* The console likely has a hardware issue.

<h5>undefined instruction</h5>
* The console likely has a hardware issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

=== <big>Arm11</big> ===
All Arm11 errors are sorted by their '''current process'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>act</h5>
* Your NNID(s)' stored data is misconfigured or being interfered with.
** To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on [[3DS:Luma3DS/Configuration|the Luma configuration menu]].
*** If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
* The current firmware version is too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
** If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]

<h5>camera</h5>
* Potential hardware issues, or an instance of ShutTheCamUp is crashing.
** Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
*** If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>cfg</h5>
* Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
** To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
*** If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|Ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|Ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
* Potential hardware problems, or an instance of rehid is crashing.
** First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
*** If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|Ctrcheck]] may help with fault isolation.

<h5>i2c/gsp/mcu/pxi/spi/</h5>
* The console has a serious hardware issue that is likely not easily fixable.
** Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.

<h5>menu</h5>
* <h6>data abort</h6>
** The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
** The HOME Menu's extra data is corrupted.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
** An installed application is corrupted or otherwise broken.
*** To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
* <h6>prefetch abort</h6>
** An installation of Menuhax is conflicting with the custom firmware.
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
* <h6>prefetch abort (svcBreak)</h6>
** If <code>R5</code> contains <code>D900458B</code>: The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
*** To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**System titles are missing. Perform a [[3DS:Safe Mode|Safe Mode update]].
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>ns</h5>
* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
** To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
* The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
** To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>3dsx_app</h5>
* The <code>.3dsx</code> file that was most recently opened is corrupted.
** To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**: If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>app/CtrApp</h5>
* If not <code>prefetch abort (svcBreak)</code>: The app most recently opened is trying to use broken software.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.
**: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
* If <code>prefetch abort (svcBreak)</code>: The app most recently opened is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

<h5>GARDEN</h5>
* Animal Crossing's game data or savedata is having issues.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
*** If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>Kujira/Joker/niji_loc</h5>
* The app most recently opened has an issue of some kind.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]]
*** If the error yet still happens, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>loader</h5>

* <h6>undefined instruction</h6>
** The app most recently opened has an issue. R0 is (most likely) an error code. Here are some common values for R0:
*** <code>D9004587</code>: When trying to open a game: The game is corrupted, or it's seed is not imported.
**** See: [[3DS:Fixing corrupted games]]
*** <code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
**** To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
*** <code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
**** To fix, redownload the app you are trying to launch. If this happens when you try open the Homebrew Launcher itself, see the error above.
*** Most of the other possible error codes for this are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|this page]].
* <h6>prefetch abort (svcBreak)</h6>
**The LayeredFS or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Re-download any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].
<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pxi</h5>
* Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>qtm/cam</h5>
* The camera's hardware is damaged or dead.
** To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>swkbd</h5>
* The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
[[Category:Unbricking]]
{{Short description|Guide to the CFW error handler}}

3DS:Error screens/Luma3DS exception screen

2024-05-22T14:23:50Z

Thepikachugamer: update to menu prefetch abort (svcBreak)

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.
==Reading a Luma3DS exception screen==
A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
* '''Processor:''' What part of the system is causing the exception. The two processors are:
**'''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
**'''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
**'''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
**'''prefetch abort''': Caused by an attempt to execute an invalid CPU instruction. Often related to conflicts between CFW and other software.
**'''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually terminating code because it matched a pre-defined condition. Often related to errors in NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
**'''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable fatal error and forcibly shutting down to avoid damage. Can be related to any of several things, but hardware issues are the most likely.
**'''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software not having the required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
*'''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
*'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
**'''fs''': The filesystem, i.e. either the SD card or the NAND.
**'''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
**'''loader''': The service that opens apps, meaning the app most recently opened has an issue.
**'''nwm''': Networking services, almost always Wi-Fi.
**'''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
*'''R0''': Usually just internal data that's not worth reading. There are two notable exceptions, however:
**'''Arm11 loader exception''': If R0's contents start with a C or D, R0 is an error code. This code usually gives the exact cause of the issue.
**'''Arm11 pm exception''': If R0's contents are <code>E0E01BF5</code>, <code>boot.firm</code> is guaranteed to be too outdated to work.

== Known Errors ==
In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] for further assistance.}}
----

=== <big>Arm9</big> ===
Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
* A system save located on the NAND in <code>[1:]/data</code> has a problem.
* System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
* The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
** To fix, create this folder.
* System titles have been deleted.
** To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (svcBreak)</h5>
* The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
** To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
* <code>SYSNAND CTRNAND</code> has bad CMACs.
** To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
* The console likely has a hardware issue.

<h5>undefined instruction</h5>
* The console likely has a hardware issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

=== <big>Arm11</big> ===
All Arm11 errors are sorted by their '''current process'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>act</h5>
* Your NNID(s)' stored data is misconfigured or being interfered with.
** To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on [[3DS:Luma3DS/Configuration|the Luma configuration menu]].
*** If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
* The current firmware version is too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
** If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]

<h5>camera</h5>
* Potential hardware issues, or an instance of ShutTheCamUp is crashing.
** Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
*** If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>cfg</h5>
* Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
** To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
*** If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|Ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|Ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
* Potential hardware problems, or an instance of rehid is crashing.
** First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
*** If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|Ctrcheck]] may help with fault isolation.

<h5>i2c/gsp/mcu/pxi/spi/</h5>
* The console has a serious hardware issue that is likely not easily fixable.
** Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.

<h5>menu</h5>
* <h6>data abort</h6>
** The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
** The HOME Menu's extra data is corrupted.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
** An installed application is corrupted or otherwise broken.
*** To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
* <h6>prefetch abort</h6>
** An installation of Menuhax is conflicting with the custom firmware.
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
* <h6>prefetch abort (svcBreak)</h6>
** If <code>R5</code> contains <code>D900458B</code>: The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
*** To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**System titles are missing. Perform a [[3DS:Safe Mode|Safe Mode update]].
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>ns</h5>
* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
** To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
* The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
** To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>3dsx_app</h5>
* The <code>.3dsx</code> file that was most recently opened is corrupted.
** To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**: If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>app/CtrApp</h5>
* If not <code>prefetch abort (svcBreak)</code>: The app most recently opened is trying to use broken software.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.
**: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
* If <code>prefetch abort (svcBreak)</code>: The app most recently opened is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

<h5>GARDEN</h5>
* Animal Crossing's game data or savedata is having issues.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
*** If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>Kujira/Joker/niji_loc</h5>
* The app most recently opened has an issue of some kind.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]]
*** If the error yet still happens, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>loader</h5>

* <h6>undefined instruction</h6>
** The app most recently opened has an issue. R0 is (most likely) contains an error code. Here are some common values for R0:
*** <code>D9004587</code>: When trying to open a game: The game is corrupted, or it's seed is not imported.
**** See: [[3DS:Fixing corrupted games]]
*** <code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
**** To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
*** <code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
**** To fix, redownload the app you are trying to launch. If this happens when you try open the Homebrew Launcher itself, see the error above.
*** Most of the other possible error codes for this are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|this page]].
* <h6>prefetch abort (svcBreak)</h6>
**The LayeredFS or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Re-download any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].
<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pxi</h5>
* Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>qtm/cam</h5>
* The camera's hardware is damaged or dead.
** To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>swkbd</h5>
* The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
[[Category:Unbricking]]
{{Short description|Guide to the CFW error handler}}

3DS:Error screens/Luma3DS exception screen

2024-05-16T16:27:18Z

Thepikachugamer: it was <h6> but anyways

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.
==Reading a Luma3DS exception screen==
A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
* '''Processor:''' What part of the system is causing the exception. The two processors are:
**'''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
**'''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
**'''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
**'''prefetch abort''': Caused by an attempt to execute an invalid CPU instruction. Often related to conflicts between CFW and other software.
**'''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually terminating code because it matched a pre-defined condition. Often related to errors in NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
**'''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable fatal error and forcibly shutting down to avoid damage. Can be related to any of several things, but hardware issues are the most likely.
**'''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software not having the required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
*'''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
*'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
**'''fs''': The filesystem, i.e. either the SD card or the NAND.
**'''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
**'''loader''': The service that opens apps, meaning the app most recently opened has an issue.
**'''nwm''': Networking services, almost always Wi-Fi.
**'''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
*'''R0''': Usually just internal data that's not worth reading. There are two notable exceptions, however:
**'''Arm11 loader exception''': If R0's contents start with a C or D, R0 is an error code. This code usually gives the exact cause of the issue.
**'''Arm11 pm exception''': If R0's contents are <code>E0E01BF5</code>, <code>boot.firm</code> is guaranteed to be too outdated to work.

== Known Errors ==
In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] for further assistance.}}
----

=== <big>Arm9</big> ===
Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
* A system save located on the NAND in <code>[1:]/data</code> has a problem.
* System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
* The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
** To fix, create this folder.
* System titles have been deleted.
** To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (svcBreak)</h5>
* The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
** To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
* <code>SYSNAND CTRNAND</code> has bad CMACs.
** To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
* The console likely has a hardware issue.

<h5>undefined instruction</h5>
* The console likely has a hardware issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

=== <big>Arm11</big> ===
All Arm11 errors are sorted by their '''current process'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>act</h5>
* Your NNID(s)' stored data is misconfigured or being interfered with.
** To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on [[3DS:Luma3DS/Configuration|the Luma configuration menu]].
*** If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
* The current firmware version is too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
** If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]

<h5>camera</h5>
* Potential hardware issues, or an instance of ShutTheCamUp is crashing.
** Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
*** If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>cfg</h5>
* Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
** To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
*** If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|Ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|Ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
* Potential hardware problems, or an instance of rehid is crashing.
** First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
*** If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|Ctrcheck]] may help with fault isolation.

<h5>i2c/gsp/mcu/pxi/spi/</h5>
* The console has a serious hardware issue that is likely not easily fixable.
** Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.

<h5>menu</h5>
* <h6>data abort</h6>
** The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
** The HOME Menu's extra data is corrupted.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
** An installed application is corrupted or otherwise broken.
*** To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
* <h6>prefetch abort</h6>
** An installation of Menuhax is conflicting with the custom firmware.
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
* <h6>prefetch abort (svcBreak)</h6>
** The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
*** To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>ns</h5>
* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
** To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
* The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
** To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>3dsx_app</h5>
* The <code>.3dsx</code> file that was most recently opened is corrupted.
** To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**: If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>app/CtrApp</h5>
* If not <code>prefetch abort (svcBreak)</code>: The app most recently opened is trying to use broken software.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.
**: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
* If <code>prefetch abort (svcBreak)</code>: The app most recently opened is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

<h5>GARDEN</h5>
* Animal Crossing's game data or savedata is having issues.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
*** If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>Kujira/Joker/niji_loc</h5>
* The app most recently opened has an issue of some kind.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]]
*** If the error yet still happens, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>loader</h5>

* <h6>undefined instruction</h6>
** The app most recently opened has an issue. R0 is (most likely) contains an error code. Here are some common values for R0:
*** <code>D9004587</code>: When trying to open a game: The game is corrupted, or it's seed is not imported.
**** See: [[3DS:Fixing corrupted games]]
*** <code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
**** To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
*** <code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
**** To fix, redownload the app you are trying to launch. If this happens when you try open the Homebrew Launcher itself, see the error above.
*** Most of the other possible error codes for this are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|this page]].
* <h6>prefetch abort (svcBreak)</h6>
**The LayeredFS or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Re-download any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].
<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pxi</h5>
* Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>qtm/cam</h5>
* The camera's hardware is damaged or dead.
** To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>swkbd</h5>
* The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
[[Category:Unbricking]]
{{Short description|Guide to the CFW error handler}}

3DS:Error screens/Luma3DS exception screen

2024-05-16T16:17:46Z

Thepikachugamer: add more details to loader exceptions (how do i <h5> in a bullet point)

{{shortcut|3DS:EXCEPTION}}
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.
==Reading a Luma3DS exception screen==
A Luma3DS exception has four (or five, in a few cases) different parts to it that help in finding its cause, as follows:
[[File:Luma3DS_exception.png|center]]
* '''Processor:''' What part of the system is causing the exception. The two processors are:
**'''Arm9:''' The 'security processor' of the system. These exceptions are usually raised because of errors in NAND data or hardware faults in either the 3DS or its SD card.
**'''Arm11:''' The 'userland' of the system. These exceptions have numerous causes but are more often related to broken software or user data.
* '''Exception type:''' The type of fault that caused the exception. These categories correspond to the ARM exceptions for the [https://developer.arm.com/documentation/ddi0201/d ARM9] and [https://developer.arm.com/documentation/ddi0360/f ARM11] CPUs, as follows:
**'''data abort''': Caused by a read or write to an invalid part of memory. Usually related to game mods/cheats/plugins, broken HOME Menu data, and/or broken CFW applications.
**'''prefetch abort''': Caused by an attempt to execute an invalid CPU instruction. Often related to conflicts between CFW and other software.
**'''prefetch abort (svcBreak)''': Caused by either Process9 or homebrew software manually terminating code because it matched a pre-defined condition. Often related to errors in NAND data, even when raised by Arm11. Can also happen when launching an out-of-region game that isn't [[3DS:SGL|locale emulated.]]
**'''prefetch abort (kernel panic)''': Caused by Kernel9 detecting an unrecoverable fatal error and forcibly shutting down to avoid damage. Can be related to any of several things, but hardware issues are the most likely.
**'''undefined instruction''': Caused by an attempt to execute a CPU instruction that was unimplemented, disallowed, or unusable. Often related to software not having the required files (if not on boot) or an outdated <code>boot.firm</code> (if on boot).
*'''Fault status:''' The specific type of ARM exception that was raised. Helpful for developers, but not so much for the end user.
*'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Some examples of processes are as follows:
**'''fs''': The filesystem, i.e. either the SD card or the NAND.
**'''menu''': Data that is opened either as a part of the HOME Menu or at the same time as it.
**'''loader''': The service that opens apps, meaning the app most recently opened has an issue.
**'''nwm''': Networking services, almost always Wi-Fi.
**'''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
*'''R0''': Usually just internal data that's not worth reading. There are two notable exceptions, however:
**'''Arm11 loader exception''': If R0's contents start with a C or D, R0 is an error code. This code usually gives the exact cause of the issue.
**'''Arm11 pm exception''': If R0's contents are <code>E0E01BF5</code>, <code>boot.firm</code> is guaranteed to be too outdated to work.

== Known Errors ==
In the following list, the file prefixes on file paths refer to the starting location. <code>sd:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] for further assistance.}}
----

=== <big>Arm9</big> ===
Arm9 errors are sorted by their '''exception type'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>Any Type</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that the SD card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try booting again.
* A system save located on the NAND in <code>[1:]/data</code> has a problem.
* System-unique files are missing from the NAND in <code>[1:]/rw/sys</code>.

<h5>data abort</h5>
* The <code>shared2</code> folder in <code>[2:] SYSNAND TWLN</code> is missing.
** To fix, create this folder.
* System titles have been deleted.
** To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].

<h5>prefetch abort (svcBreak)</h5>
* The system movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but a flag is enabled that expects a size of 320 bytes.
** To fix, boot into GodMode9 and select <code>SYSNAND CTRNAND</code>, then go into the <code>private</code> folder.<br>Inside this folder, you will see a file named <code>movable.sed</code>. Select it, and under the options menu, select '''Show in Hexeditor'''.<br>Green-colored numbers will appear in the middle of the screen - press {{B|A}} and then unlock '''writing to sysNAND (lvl2)'''.<br>At the beginning of the file, look for the set of numbers <code>53 45 45 44 00 01</code>. Once you find these numbers, hold {{B|A}} and press {{B|D-PAD DOWN}} while the <code>01</code> value is highlighted to change it to <code>00</code>. Press {{B|B}}, then {{B|A}}, then {{B|B}} to save changes and exit from the hexeditor, then press {{B|START}} to reboot your console.
* <code>SYSNAND CTRNAND</code> has bad CMACs.
** To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. The console will act like it has been formatted after this, and this is intended.
*If none of the above have worked, perform a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]].

<h5>prefetch abort (kernel panic)</h5>
* The console likely has a hardware issue.

<h5>undefined instruction</h5>
* The console likely has a hardware issue.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>data abort</h5>
* Files on the SD are corrupted.
** To fix, [[Checking_SD_card_integrity|verify that your card is not faulty.]] If it is verified working, make a backup of all intact files, [[Formatting_an_SD_card|format the SD card]], and try again.

=== <big>Arm11</big> ===
All Arm11 errors are sorted by their '''current process'''.

<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>

<h5>act</h5>
* Your NNID(s)' stored data is misconfigured or being interfered with.
** To fix, if [https://pretendo.network Pretendo] is installed, turn it off by disabling <code>Enable loading external FIRMs and modules</code> on [[3DS:Luma3DS/Configuration|the Luma configuration menu]].
*** If this does not help or Pretendo is not installed, then [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|restore a NAND backup]] - especially if you recently tried to [[3DS:GodMode9/Usage#Removing_an_NNID_without_formatting_your_device|log out an NNID]].

<h5>boss</h5>
* The current firmware version is too old for SpotPass to work. Perform a [[3DS:Safe Mode|Safe Mode update]].
** If this does not work, you may require [[3DS:CTRTransfer|a CTRTransfer.]]

<h5>camera</h5>
* Potential hardware issues, or an instance of ShutTheCamUp is crashing.
** Look for and delete <code>/luma/sysmodules/0004013000001602.ips</code> and <code>/luma/titles/0004013000001602/code.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the correct Old or New 3DS patch for [[udb:3ds/shut-the-cam-up|ShutTheCamUp]] if you wish to continue using it.
*** If these don't exist, or the error occurs when booting without an SD card, it's likely hardware issues. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>cfg</h5>
* Either the NAND [[3dbrew:Config Savegame|config savegame]] or part of your console-unique file(s) is damaged.
** To fix, first boot into GodMode9, press R+A while the cursor is on the folder <code>[1:]/data/<ID0>/sysdata/00010017</code>, choose to <code>Copy to 0:/gm9/out</code>, then delete the folder. After rebooting, the console will enter initial setup again; this is intended and not an issue.
*** If this does not help, delete the newly created <code>00010017</code> and copy the backup into its place, run [[3DS:ctrcheck|Ctrcheck]], and replace any console-unique files marked as invalid or missing with the copies from the <code>essentials.exefs</code> backup inside <code>[S:] SYSNAND VIRTUAL</code> in GodMode9.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|Fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|Ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>hid</h5>
* Potential hardware problems, or an instance of rehid is crashing.
** First look for and delete <code>/luma/titles/0004013000001D02</code>, <code>/luma/titles/0004013000003302</code>, <code>/luma/sysmodules/0004013000001D02.cxi</code> and <code>/luma/sysmodules/0004013000003302.ips</code>.
*** If this fixed the issue, then [[3dsguide:restoring-updating-cfw|update Luma3DS]] and reinstall the latest release of [[3DS:Rehid|rehid]] to continue using it.
*** If these don't exist, or rehid has never been installed on this console, it's likely hardware issues. [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|Ctrcheck]] may help with fault isolation.

<h5>i2c/gsp/mcu/pxi/spi/</h5>
* The console has a serious hardware issue that is likely not easily fixable.
** Run [[3DS:Hardware test|3ds_hw_test]]. If the test returns zero errors detected, join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.

<h5>menu</h5>
* <h6>data abort</h6>
** The installed [[3DS:Custom themes|theme]] is corrupted or otherwise broken.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
** The HOME Menu's extra data is corrupted.
*** To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
**: USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
** An installed application is corrupted or otherwise broken.
*** To fix, either perform a [[3DS:Safe Mode|Safe Mode update]], attempt to enter System Settings before the crash occurs and delete the application in Data Management, or [[Formatting an SD card|reformat the SD card]].
* <h6>prefetch abort</h6>
** An installation of Menuhax is conflicting with the custom firmware.
*** To fix, follow the directions [[3DS:Troubleshooting/removing_menuhax67|on this page]].
**If this occurs on boot, set '''Hbmenu autoboot''' in the [[3DS:Luma3DS/Configuration|Luma configuration menu]] to 3DS, then follow the above instructions and turn '''Hbmenu autoboot''' back off once it has been removed.
***Ensure in <code>sd:/luma/config.ini</code> that hbldr_3dsx_titleid is set to 000400000d921e00 and <code>boot.3dsx</code> is in the root.
* <h6>prefetch abort (svcBreak)</h6>
** The <code>f000000b</code> folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
*** To fix, backup <code>f000000b</code> by pressing R+A while highlighting it, then selecting <code>Copy to 0:/gm9/out</code>. Once it is backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
**If you have a recent NAND backup, try restoring it with [[3DS:GodMode9/Usage#Restoring_a_NAND_backup|this guide]]

<h5>ns</h5>
* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting '''Hbmenu autoboot''' is set to boot to a title that does not exist.
** To fix, disable the option, install an application with the title ID in <code>sd:/luma/config.ini</code>, or change the set title ID to match an application that does exist.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi using an external switch. New models do not have this switch disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pm</h5>
* The installed version of Luma3DS likely does not support the current firmware version. This is guaranteed to be true if the contents of R0 are <code>E0E01BF5</code>.
** To fix, [[3dsguide:restoring-updating-cfw|update CFW.]]

<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>

<h5>3dsx_app</h5>
* The <code>.3dsx</code> file that was most recently opened is corrupted.
** To fix, download a new copy of the <code>.3dsx</code> file. If this error happens when opening the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
**: If the error still happens, [[Checking SD card integrity|test the SD card for errors.]]

<h5>app/CtrApp</h5>
* If not <code>prefetch abort (svcBreak)</code>: The app most recently opened is trying to use broken software.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause.
**: If the error still happens, then the game itself is likely faulty. If it is a system app, [[3DS:CTRTransfer|perform a CTRTransfer]]. Otherwise, if it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
* If <code>prefetch abort (svcBreak)</code>: The app most recently opened is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

<h5>GARDEN</h5>
* Animal Crossing's game data or savedata is having issues.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, then the game itself may be faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it, if it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it, or if it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.
*** If the error yet still happens, ensure that you have not used a save editor before the error started happening. If you have used a save editor, the edits are broken and you will need to restore a backed-up save, or wipe the save and start over if you have no backup.

<h5>fs</h5>
* Could be an SD card problem, minor NAND problem, hardware issue, or anything in between.
** [[wikipedia:Fault isolation|fault isolation]] will likely be required to find the true cause of this error. Start by doing [[3DS:ctrcheck|ctrcheck]] and trying to trigger the error with the SD card removed from the console.<br>If the error stops when the SD card is removed, [[Formatting an SD card|reformat the SD card]], and if that doesn't help, [[Checking SD card integrity|test it for hardware damage]].

<h5>Kujira/Joker/niji_loc</h5>
* The app most recently opened has an issue of some kind.
** To fix, disable all game mods, cheat codes, and plugins to ensure they are not the cause. If the error still happens, ensure the game is the same region as the console - if it is not, [[3DS:SGL|activate locale emulation for the game.]]
*** If the error yet still happens, then the game itself is likely faulty. If it is a [[3DS:Dump titles and game cartridges#Dumping a Game Cartridge|cartridge dump]], redump it. If it is an eShop game, click the Repair button at the bottom of its eShop page or delete and reinstall it. If it is a cartridge, clean the cartridge and the 3DS cartridge reader with isopropyl alcohol.

<h5>loader</h5>

* undefined instruction
** The app most recently opened has an issue. R0 is (most likely) contains an error code. Here are some common values for R0:
*** <code>D9004587</code>: When trying to open a game: The game is corrupted, or it's seed is not imported.
**** See: [[3DS:Fixing corrupted games]]
*** <code>C8804478</code>: If trying to open the Homebrew Launcher: <code>boot.3dsx</code> is missing from the root of your SD card.
**** To fix: Download the latest Homebrew Launcher from [https://github.com/devkitPro/3ds-hbmenu/releases/latest here]
*** <code>D96077FA</code>/<code>FFFFFFFF</code>: The <code>.3dsx</code> that Luma3DS tried to load is corrupted.
**** To fix, redownload the app you are trying to launch. If this happens when you try open the Homebrew Launcher itself, see the error above.
*** Most of the other possible error codes for this are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|this page]].
* prefetch abort (svcBreak)
**The LayeredFS or sysmodule patch Luma3DS tried to load is invalid or corrupt.
***To fix: Re-download any recently installed patches (eg. Nimbus (Pretendo), Wumiibo, or anything else that goes in <code>/luma/titles</code> or <code>/luma/sysmodules</code>.) Alternatively, you may disable <code>loading external FIRMs and modules</code> as well as <code>Enable game patching</code> in the [[3DS:Luma3DS/Configuration|Luma3DS configuration menu]].
<h5>mset</h5>
* System Settings is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.

<h5>nwm</h5>
* The WiFi chipset's hardware is damaged or dead.
** To fix, replace the WiFi chipset with a new one. To avoid the error until then, disable WiFi on the 3DS and do not turn it back on.
*** If the 3DS is an old model, you can disable WiFi with an external switch. New models must instead disable it through the HOME Menu Settings or Rosalina. Repeatedly pressing the keycombo for Rosalina while powering on might let you access Rosalina before it can crash.

<h5>pxi</h5>
* Could be anything from a faulty cartridge to damaged internal components, but will almost always be some type of hardware issue.

<h5>qtm/cam</h5>
* The camera's hardware is damaged or dead.
** To fix, replace the camera with a new one. To avoid the error until then, disconnect the camera or avoid using anything that activates the camera.

<h5>swkbd</h5>
* The software keyboard is broken in some way - this may indicate that the console has a hardware issue.
** To fix, perform a [[3DS:CTRTransfer|CTRTransfer]], or a [[3DS:CTRTransfer/Manual|Manual CTRTransfer]] if that does not work.
*** If neither of these work, the console has a serious issue. Join the [https://discord.gg/nintendohomebrew Nintendo Homebrew Discord] and ask, in English, for help.
[[Category:Unbricking]]
{{Short description|Guide to the CFW error handler}}

3DS:Fastboot3DS to boot9strap

2024-05-16T02:52:02Z

Thepikachugamer: Created page with "==What you Need== *The latest release of [https://github.com/d0k3/SafeB9SInstaller/releases/latest SafeB9SInstaller] *The latest release of [https://github.com/SciresM/boot9strap/releases/latest boot9strap] *The latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS] ==Instructions== ===Section I - Prep Work=== #Power off your device #Insert your SD card into your computer #Copy <code>SafeB9SInstaller.firm</code> from the SafeB9SInstaller .zip..."

==What you Need==

*The latest release of [https://github.com/d0k3/SafeB9SInstaller/releases/latest SafeB9SInstaller]
*The latest release of [https://github.com/SciresM/boot9strap/releases/latest boot9strap]
*The latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS]

==Instructions==

===Section I - Prep Work===

#Power off your device
#Insert your SD card into your computer
#Copy <code>SafeB9SInstaller.firm</code> from the SafeB9SInstaller .zip to the root of your SD card
#Create a folder named <code>boot9strap</code> on your SD card
#Copy <code>boot9strap.firm</code> and <code>boot9strap.firm.sha</code> from the boot9strap <code>.zip</code> to the <code>/boot9strap/</code> folder on your SD card
#Copy <code>boot.firm</code> and <code>boot.3dsx</code> from the Luma3DS <code>.zip</code> to the root of your SD card
#Safely eject your SD card from your computer
#Reinsert your SD card into your device

===Section II - Launching SafeB9SInstaller===

#Press Home, and while holding Home, power on your device
#Select <code>[+] Boot from file...</code>
#Select <code>SafeB9SInstaller.firm</code>
#Your device will have booted into SafeB9SInstaller

===Section III - Installing boot9strap===

#When prompted, input the key combo given on the top screen to install boot9strap
#Once it is complete, press (A) to reboot your device
#Your device should have rebooted into the Luma3DS configuration menu
#*Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
#*For the purpose of this guide, these settings will be left on default settings
#*If your device shuts down when you try to power it on, ensure that you have copied <code>boot.firm</code> from the Luma3DS <code>.zip</code> to the root of your SD card
#Press (Start) to save and reboot
#*If you get an error, just continue to the next page
{{Luma3DS is default}}

----

<span style="font-size:200%;">Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]</span>

[[Category:Nintendo 3DS guides]]

User:Thepikachugamer/Installing boot9strap (OldLoader)

2024-05-07T01:27:24Z

Thepikachugamer: /* Section II - Launching SafeB9SInstaller GodMode9 */ would => will

== What you Need ==

* The latest release of [https://github.com/d0k3/OldLoader/releases/latest OldLoader]
* The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9]
* The latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS]
* The latest release of [https://github.com/SciresM/boot9strap/releases/latest boot9strap]
* Something that launches Arm9 .bin payloads (eg. nimdsphax)
** For some exploits like MSET9 and arm9loaderhax, the file `SafeB9SInstaller.bin` should be named differently

== <big>'''Instructions'''</big> ==

=== Section I - Prep Work ===

# Power off your device
# Insert your SD card into your computer
# Copy <code>OldLoader.bin</code> from the OldLoader <code>.zip</code> to the root of your SD card, and rename it to <code>SafeB9SInstaller.bin</code>
# Copy <code>boot.firm</code> and <code>boot.3dsx</code> from the Luma3DS <code>.zip</code> to the root of your SD card, and rename <code>boot.firm</code> to <code>luma.firm</code>
# Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the root of your SD card, and rename it to `boot.firm`
# Create a folder named <code>boot9strap</code> folder on your SD card
# Copy <code>boot9strap.firm</code> and <code>boot9strap.firm.sha</code> to the newly-created <code>boot9strap</code> folder
# Safely eject your SD card from your computer
# Reinsert your SD card into your device
# Power on your device

=== Section II - Launching <s>SafeB9SInstaller</s> GodMode9 ===

# Launch <code>SafeB9SInstaller.bin</code> through any method
# If the exploit was successful, you will have booted into GodMode9

=== Section III - Installing boot9strap ===

# Navigate to <code>[0:] SDCARD</code> -> <code>boot9strap</code> inside GodMode9
# Press A on <code>boot9strap.firm</code>
# Select "Calculate SHA-256"
# The verification should pass.
# Press A on <code>boot9strap.firm</code> again
# Select <code>FIRM Image Options</code> -> <code>Install FIRM</code> -> <code>Install to both</code>
# Press A to unlock SysNAND (lvl3) writing, then input the given key combo
# Once the installation has succeeded, press A to continue
# Press B to return to <code>[0:] SDCARD</code>
# Press X on <code>boot.firm</code> to delete it
# Press R+X on <code>luma.firm</code>, and rename it to <code>boot.firm</code>
# Press START to reboot your console. Your console should boot to the Luma3DS configuration menu
#*Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
#*For the purpose of this guide, these settings will be left on default settings
#*If your device shuts down when you try to power it on, try re-copy <code>boot.firm</code> from the Luma3DS <code>.zip</code> to the root of your SD card
{{Luma3DS is default}}
-----<span style="font-size:200%;">Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]</span>

User:Thepikachugamer/Installing boot9strap (OldLoader)

2024-05-07T01:13:44Z

Thepikachugamer: this is truly an Installing FIRM with GodMode9 Moment

== What you Need ==

* The latest release of [https://github.com/d0k3/OldLoader/releases/latest OldLoader]
* The latest release of [https://github.com/d0k3/GodMode9/releases/latest GodMode9]
* The latest release of [https://github.com/LumaTeam/Luma3DS/releases/latest Luma3DS]
* The latest release of [https://github.com/SciresM/boot9strap/releases/latest boot9strap]
* Something that launches Arm9 .bin payloads (eg. nimdsphax)
** For some exploits like MSET9 and arm9loaderhax, the file `SafeB9SInstaller.bin` should be named differently

== <big>'''Instructions'''</big> ==

=== Section I - Prep Work ===

# Power off your device
# Insert your SD card into your computer
# Copy <code>OldLoader.bin</code> from the OldLoader <code>.zip</code> to the root of your SD card, and rename it to <code>SafeB9SInstaller.bin</code>
# Copy <code>boot.firm</code> and <code>boot.3dsx</code> from the Luma3DS <code>.zip</code> to the root of your SD card, and rename <code>boot.firm</code> to <code>luma.firm</code>
# Copy <code>GodMode9.firm</code> from the GodMode9 <code>.zip</code> to the root of your SD card, and rename it to `boot.firm`
# Create a folder named <code>boot9strap</code> folder on your SD card
# Copy <code>boot9strap.firm</code> and <code>boot9strap.firm.sha</code> to the newly-created <code>boot9strap</code> folder
# Safely eject your SD card from your computer
# Reinsert your SD card into your device
# Power on your device

=== Section II - Launching <s>SafeB9SInstaller</s> GodMode9 ===

# Launch <code>SafeB9SInstaller.bin</code> through any method
# If the exploit was successful, you would have booted into GodMode9

=== Section III - Installing boot9strap ===

# Navigate to <code>[0:] SDCARD</code> -> <code>boot9strap</code> inside GodMode9
# Press A on <code>boot9strap.firm</code>
# Select "Calculate SHA-256"
# The verification should pass.
# Press A on <code>boot9strap.firm</code> again
# Select <code>FIRM Image Options</code> -> <code>Install FIRM</code> -> <code>Install to both</code>
# Press A to unlock SysNAND (lvl3) writing, then input the given key combo
# Once the installation has succeeded, press A to continue
# Press B to return to <code>[0:] SDCARD</code>
# Press X on <code>boot.firm</code> to delete it
# Press R+X on <code>luma.firm</code>, and rename it to <code>boot.firm</code>
# Press START to reboot your console. Your console should boot to the Luma3DS configuration menu
#*Luma3DS configuration menu are settings for the Luma3DS custom firmware. Many of these settings may be useful for customization or debugging
#*For the purpose of this guide, these settings will be left on default settings
#*If your device shuts down when you try to power it on, try re-copy <code>boot.firm</code> from the Luma3DS <code>.zip</code> to the root of your SD card
{{Luma3DS is default}}
-----<span style="font-size:200%;">Continue to [[3dsguide:finalizing-setup|Finalizing Setup]]</span>

Formatting an SD card/Windows

2024-01-30T04:03:10Z

Thepikachugamer: trying to inform the user that the instructions are not done

<languages/>
<translate>

This is an add-on section for formatting an SD card to FAT32.


This page is for Windows users only. If you are not on Windows, check out the [[Special:MyLanguage/Formatting an SD card/Linux|Linux]] or [[Special:MyLanguage/Formatting an SD card/Mac|Mac]] pages.
</translate>

== What You Need ==
*<translate> '''Required for all SD cards''': the latest version of <tvar name="sdformatter">[https://www.sdcard.org/downloads/formatter/sd-memory-card-formatter-for-windows-download/ SD Memory Card Formatter]</tvar></translate>
*<translate> '''For SD cards 64GB or larger''': The latest version of <tvar name="guiformat">[http://ridgecrop.co.uk/index.htm?guiformat.htm guiformat]</tvar></translate>

<translate>
== Instructions == 
</translate>

<tabber>
|-|<translate> 64GB or larger</translate>=

<ol>
<li><translate> Insert your SD card into your computer</translate></li>
<li><translate> If the SD card has any files and folders on it, copy everything to a folder on your computer</translate></li>
<li><translate>Run <code>SD Card Formatter Setup</code> (the <code>.exe</code> file) in the downloaded .zip file with Administrator privileges, then install the program</translate></li>
<li><translate>Run <code>SD Card Formatter</code> from the Start Menu</translate></li>
<li><translate>Select your SD card’s drive letter for "Select card"</translate>{{warning|<translate nowrap>Make sure you choose the correct drive letter, otherwise you might accidentally erase the wrong drive!</translate>}}</li>
<li><translate>Ensure that "Quick Format" is selected</translate></li>
<li><translate>Click "Format"</translate></li>
<li><translate>Click "OK"</translate></li>
<li><translate>Wait for the format to finish</translate></li>
<li><translate>Click "OK"</translate></li>{{info|<translate nowrap>Your SD card will be formatted to exFAT at this point. The following steps will format it to FAT32.</translate>}}
<li><translate>Close SD Card Formatter</translate></li>
<li><translate> Run <code>guiformat.exe</code></translate></li>
<li><translate> Select your SD card’s drive letter for "Drive"</translate>{{warning|<translate nowrap> Make sure you choose the correct drive letter, otherwise you might accidentally erase the wrong drive!</translate>}}</li>
<li><translate> Select a size for "Allocation unit size"</translate>
<ul>
<li><translate> If the SD card is 64GB, choose 32768</translate></li>
<li><translate> If the SD card is larger than 64GB, choose 65536</translate></li>
</ul></li>
<li><translate> Ensure that "Quick Format" is selected</translate></li>
<li><translate> Click "Start"</translate></li>
<li><translate> Click "OK"</translate></li>
<li><translate> Wait for the format to finish</translate></li>
<li><translate> Click "Close"</translate></li>
<li><translate> If the SD card had any files and folders on it before the format, copy everything back from your computer</translate></li>
</ol>

<translate>
=== Common errors with guiformat ===  </translate>
==== Failed to open device: GetLastError()=32 ====
<translate>

Close everything that may be using the SD card, such as any File Explorer windows. If it does not resolve the issue, try formatting the card to NTFS, then run GUIFormat again.
</translate>

==== GetLastError()=1117 ====
<translate>

Your SD card write-protection switch may be [https://3ds.hacks.guide/images/sdlock.png enabled]. The lock must be flipped upwards to allow writing to the SD card (including formatting).
</translate>

|-|<translate> 32GB or smaller</translate>=

<ol>
<li><translate> Insert your SD card into your computer</translate></li>
<li><translate> If the SD card has any files and folders on it, copy everything to a folder on your computer</translate></li>
<li><translate> Run <code>SD Card Formatter Setup</code> (the <code>.exe</code> file) in the downloaded .zip file with Administrator privileges, then install the program</translate></li>
<li><translate> Run <code>SD Card Formatter</code> from the Start Menu</translate></li>
<li><translate> Select your SD card’s drive letter for "Select card"</translate>{{warning|<translate nowrap> Make sure you choose the correct drive letter, otherwise you might accidentally erase the wrong drive!</translate>}}</li>
<li><translate> Ensure that "Quick Format" is selected</translate></li>
<li><translate> Click "Format"</translate></li>
<li><translate> Click "OK"</translate></li>
<li><translate> Wait for the format to finish</translate></li>
<li><translate> Click "OK"</translate></li>
<li><translate> Close SD Card Formatter</translate></li>
<li><translate> If the SD card had any files and folders on it before the format, copy everything back from your computer</translate></li>
</ol>
</tabber>

==SD Card not formatting or has some other issue.==
Refer to the [[SD Clean/Windows|SD Clean]] guide.

{{hg imported|Guide_3DS}}

[[Category:General guides]]

SD Clean/Windows

2024-01-28T00:06:09Z

Thepikachugamer: exFAT is sometimes not an option (!?)

This is an add-on section for completely recreating an SD card's filesystem using diskpart and Disk Management. This should only be done if formatting does not fix your issue or is not possible for some reason.

This page is for Windows users only. If you are not on Windows, see the [[SD Clean/Mac|Mac]] and/or [[SD Clean/Linux|Linux]] pages instead.

== Instructions ==

{{warning|Before beginning these steps, copy all of your SD card's contents to a folder on your computer.}}

<ol>
<li>Launch <code>diskpart</code> by searching for <code>diskpart</code> in the Windows search bar</li>
<li>Once diskpart is active in the new Command Prompt window, type <code>list disk</code></li>
<li>Find your SD card in the list of disks (hint: look for the size of your card), then type <code>select disk #</code>, where # is the disk number of your SD card {{info|text=Disk 0 will always be your main windows drive, so you'd select any disk after it.}}</li>
<li>Type <code>list disk</code> again. You should now see a * next to your SD card</li>
<li>Once you are absolutely sure that you have selected the right disk, type <code>clean</code>, then type <code>convert mbr</code></li>
# Close the diskpart window, and search for <code>diskmgmt.msc</code> in the windows search bar
# Once the disk management window loads, you should be able to see your SD card as a black 'unallocated' area in the bottom part of the window. You may have to scroll down the bottom part of the window to see it
# Right click on the black unallocated area and select <code>new simple volume</code>
# Click through all the prompts until the one about formatting - in that prompt, select "FAT32" or "exFAT" as the file system
# If FAT32 was not an option in step 4, [[Formatting an SD card/Windows|Reformat the SD card to FAT32]].
# Copy your data back onto your SD card.

[[Category:General guides]]