3DS:Error screens/Luma3DS exception screen: Difference between revisions

Line 17:

**'''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 ~~you last tried to open~~ has an issue.

**'''loader''': The service that opens apps, meaning the app most recently opened has an issue.

**'''nwm''': Networking services, almost always WiFi.

**'''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.

Line 36:

* Files on the SD are corrupted.

** To fix, [[Checking_SD_card_integrity|verify that ~~your~~ 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.

** 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>.

Line 69:

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

* 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]].

* 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.]]

* 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]], 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.

* 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]], [[Formatting an SD card|~~formatting your~~ SD card]], and~~/or~~ [[Checking SD card integrity|~~testing your SD~~ for ~~errors~~]].

** [[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]].

* Potential hardware problems, or an outdated version of Rehid.

** First look for and delete <code>/luma/titles/0004013000001D02</code> and <code>/luma/titles/0004013000003302</code>. If these don't exist, or ~~you've~~ never ~~downloaded Rehid~~, it's likely hardware issues.

** First look for and delete <code>/luma/titles/0004013000001D02</code> and <code>/luma/titles/0004013000003302</code>. 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.

* The console has a serious hardware issue that is likely not easily fixable.

** ~~Join~~ [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.

** 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.

Line 104:

Line 113:

*** 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.

** 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, ~~enable hbmenu~~ autoboot in the Luma configuration menu to 3DS ~~mode~~, then follow above instructions

**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.

***Turn hbmenu autoboot back off when menuhax67 is removed

* <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>.

Line 115:

Line 123:

* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting ~~<code>Autoboot Homebrew</code>~~ is set to boot to a title that does not exist.

* 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 or install an application ~~that matches~~ the title ID ~~set~~ in <code>sd:/luma/config.ini</code>.

** 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.

* 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.

*** 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.

Line 130:

Line 138:

* The <code>.3dsx</code> file ~~you~~ opened is corrupted.

* 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 ~~you open~~ the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.

** 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 ~~your~~ SD for errors.]]

**: 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 ~~you last~~ opened is trying to use broken software.

* 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 ~~you are trying to open~~ is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.

* 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>

Line 147:

Line 155:

* 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]], [[Formatting an SD card|~~formatting your~~ SD card]], and~~/or~~ [[Checking SD card integrity|~~testing your SD~~ for ~~errors~~]].

** [[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 ~~you last~~ opened has an issue of some kind.

* 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>

* The app ~~you last~~ opened has an issue. If the contents of R0 start with C or D, R0 is an error code.<br>

* The app most recently opened has an issue. If the contents of R0 start with C or D, R0 is an error code.<br>

** Most of the possible error codes for this are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|this page]].

Line 169:

Line 177:

* Could be anything from a faulty cartridge to damaged internal components, but will almost always be hardware~~-related~~.

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

@@ Line 17: / Line 17: @@
 **'''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 you last tried to open has an issue.
+**'''loader''': The service that opens apps, meaning the app most recently opened has an issue.
 **'''nwm''': Networking services, almost always WiFi.
 **'''ns''': The <u>N</u>intendo User Interface <u>S</u>hell, which handles all apps/processes/services in 3DS mode.
@@ Line 36: / Line 36: @@
 <h5>Any Type</h5>
 * Files on the SD are corrupted.
-** To fix, [[Checking_SD_card_integrity|verify that your 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.
+** 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>.
@@ Line 69: / Line 69: @@
 <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>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]], 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]], [[Formatting an SD card|formatting your SD card]], and/or [[Checking SD card integrity|testing your SD for errors]].
+** [[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 outdated version of Rehid.
-** First look for and delete <code>/luma/titles/0004013000001D02</code> and <code>/luma/titles/0004013000003302</code>. If these don't exist, or you've never downloaded Rehid, it's likely hardware issues.
+** First look for and delete <code>/luma/titles/0004013000001D02</code> and <code>/luma/titles/0004013000003302</code>. 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>ic2/spi</h5>
+<h5>ic2/gsp/mcu/pxi/spi/</h5>
 * The console has a serious hardware issue that is likely not easily fixable.
-** Join [https://discord.gg/C29hYvh the Nintendo Homebrew Discord] and ask, in English, for help.
+** 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>
@@ Line 104: / Line 113: @@
 *** 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.
+** 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, enable hbmenu autoboot in the Luma configuration menu to 3DS mode, then follow above instructions
+**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.
-***Turn hbmenu autoboot back off when menuhax67 is removed
 * <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>.
@@ Line 115: / Line 123: @@
 <h5>ns</h5>
-* The [[3DS:Luma3DS/Configuration|Luma configuration]] setting <code>Autoboot Homebrew</code> is set to boot to a title that does not exist.
+* 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 or install an application that matches the title ID set in <code>sd:/luma/config.ini</code>.
+** 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 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.
+*** 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>
@@ Line 130: / Line 138: @@
 <h5>3dsx_app</h5>
-* The <code>.3dsx</code> file you opened is corrupted.
+* 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 you open the Homebrew Launcher, download a new copy of <code>boot.3dsx</code>.
+** 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 your SD for errors.]]
+**: 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 you last opened is trying to use broken software.
+* 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 you are trying to open is out-of-region and relies on locale-specific data. Activate [[3DS:SGL|locale emulation]] for it.
+* 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>
@@ Line 147: / Line 155: @@
 <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]], [[Formatting an SD card|formatting your SD card]], and/or [[Checking SD card integrity|testing your SD for errors]].
+** [[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 you last opened has an issue of some kind.
+* 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>
-* The app you last opened has an issue. If the contents of R0 start with C or D, R0 is an error code.<br>
+* The app most recently opened has an issue. If the contents of R0 start with C or D, R0 is an error code.<br>
 ** Most of the possible error codes for this are listed on [[3DS:Error_screens/Luma3DS_ErrDisp|this page]].
@@ Line 169: / Line 177: @@
 <h5>pxi</h5>
-* Could be anything from a faulty cartridge to damaged internal components, but will almost always be hardware-related.
+* 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>