Approver, confirmaccount
398
edits
StarlitSkies (talk | contribs) m (minor wording fixes. also, i know my info's not perfect here, i just can't tell what parts are wrong. so, uh, have fun fixing my mistakes? i guess?) |
StarlitSkies (talk | contribs) (add a couple more processes plus other misc. info // Edit via Wikitext Extension for VSCode) |
||
Line 11: | Line 11: | ||
**'''undefined instruction''': Usually either a broken piece of software (if not on boot) or outdated <code>boot.firm</code> (if on boot). | **'''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. | *'''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. Common or unique processes are as follows: | *'''Current process:''' Where the error is coming from in the system. Often the most helpful part of the exception. Common or unique processes are as follows: | ||
**'''fs''': Files on your SD card or NAND are having issues. | |||
**'''hid''': Potential hardware problems. | **'''hid''': Potential hardware problems. | ||
**'''menu''': Some of the data/extdata that's either associated with the HOME Menu or loaded at the same time is broken. | **'''menu''': Some of the data/extdata that's either associated with the HOME Menu or loaded at the same time is broken. | ||
**'''pm''': Almost always, <code>boot.firm</code> is too outdated to work. | **'''pm''': Almost always, <code>boot.firm</code> is too outdated to work. | ||
**'''loader''': The app you last tried to run has an error. | **'''loader''': The app you last tried to run has an error. | ||
**'''qtm''': Your camera has a hardware issue. | **'''qtm'''/'''cam''': Your camera has a hardware issue. | ||
**'''nwm''': Your WiFi chip is damaged, dying, or entirely dead. This always means you must disable WiFi to stop the errors. | |||
*'''R0''': Usually just internal data that's not worth reading. There are two notable exceptions, however: | *'''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 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. | ||
Line 41: | Line 43: | ||
**To fix, create this folder. | **To fix, create this folder. | ||
*System titles have been deleted. | *System titles have been deleted. | ||
**To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. | **To fix, perform a [[3DS:Safe Mode|Safe Mode update]]. If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]]. | ||
====During use==== | ====During use==== | ||
Line 95: | Line 97: | ||
=====loader (0000000000000000)===== | =====loader (0000000000000000)===== | ||
If the hexadecimal number next to R0 starts with 'C' or 'D', search for it as an error code or in [[3DS:Error_screens/Luma3DS_ErrDisp]].<br> | If the hexadecimal number next to R0 starts with 'C' or 'D', search for it as an error code or in [[3DS:Error_screens/Luma3DS_ErrDisp]].<br> | ||
These errors are usually due to corruption, such as a faulty SD card | These errors are usually due to corruption, such as a faulty/dirty SD card or game cartridge. | ||
[[Category:Unbricking]] | [[Category:Unbricking]] |