User:ItsCrocoSwine/3DS Error toolkit: Difference between revisions

User:ItsCrocoSwine/3DS Error toolkit (view source)

Revision as of 05:18, 11 November 2023

4,269 bytes added , 1 year ago

no edit summary

ItsCrocoSwine

Approver

518

edits

@@ Line 1: / Line 1: @@
-=Luma3DS error toolkit=
+=Luma3DS Error Toolkit=
-This page contains known errors for Luma3DS, all on one page in a handy tabber.
+This page lists possible causes and fixes of Luma3DS exception screens, and Luma3DS ErrDisp screens. They are not applicable to every situation, but cover most common known issues.
+==Known errors==
+In the following lists, 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.
+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.
+{{info|If the below fixes do not solve your issue or you are unsure of what to do, join the [[https://discord.gg/nintendohomebrew Nintendo Homebrew Discord]] for further assistance.}}
+----
 <tabber>
@@ Line 63: / Line 75: @@
 | fs || any
 | Can be anything from SD card problems to hardware issues.
+: [[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]].
 |-
 | hid || any
-| Potential hardware problems.
+| 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 dont exist, or you've never downloaded Rehid, its likely hardware issues.
+:: [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation.
 |-
 | ic2, spi || any
@@ Line 136: / Line 151: @@
 | fs || any
 | Can be anything from SD card problems to hardware issues.
+: [[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]].
 |-
 | Kujira<br>Joker<br>niji_loc || any
@@ Line 243: / Line 259: @@
 |}
 </tabber>
+==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 usually result from 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 often related to broken software or user data.
+* '''Exception type:''' How the system is causing the exception. These categories are often too broad to be helpful, but three of them are more precise:
+**'''data abort''': Oftentimes related to a broken mod or broken HOME Menu data. Occasionally related to custom firmware data being broken.
+**'''prefetch abort (svcBreak)''': Oftentimes an issue with data on the NAND, even when Arm11. Can also happen when launching an out-of-region game.
+**'''undefined instruction''': Usually either a broken piece of software (if not on boot) or outdated <code>boot.firm</code> (if on boot).
+*'''Fault status:''' Why the system is causing the exception. Normally not helpful except for developers.
+*'''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 you last tried to open 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.
+*'''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.
+==Reading a Luma3DS ErrDisp==
+With Luma3DS insa 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.