< 3DS:Error screens
Revision as of 22:48, 16 October 2022 by StarlitSkies (talk | contribs) (add solutions for a large number of the errors & major style fixes)
This page is a work in progress. Notes:
|
This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.
Note that the prefixes on file paths refer to the starting location. sdmc:/
refers to the SD card, and numbers in the format of [X:]
refer to GodMode9's drive numbers.
If the below fixes do not solve your issue or you are unsure of what to do, join the [Nintendo Homebrew Discord] for further assistance. |
Arm9
On boot
- Files on the SD are corrupted.
- To fix, verify that your card is not faulty. If it is verified working, make a backup of all intact files, format the SD card, and try again.
- A system save located on the NAND in
[1:]/data
has a problem. - System-unique files are missing from the NAND in
[1:]/rw/sys
.
Prefetch abort (svcBreak)
- The system's movable,
[1:]/private/movable.sed
, is 288 bytes but its flag indicates otherwise. SYSNAND CTRNAND
has bad CMACs.- To fix, press R+A on the
SYSNAND CTRNAND
drive andFix CMACs for drive
. Your system will act like it has been formatted after this, and this is intended.
- To fix, press R+A on the
Data abort
SYSNAND TWLN
's[2:]/shared2
folder is missing.- To fix, create this folder.
- System titles have been deleted.
- To fix, perform a Safe Mode update.
During use
- Files on the SD are corrupted.
- To fix, verify that your card is not faulty. If it is verified working, make a backup of all intact files, format the SD card, and try again.
Arm11
On boot
boss (0004013000003402), data abort
- The current firmware version is too old for SpotPass to work.
- To fix, perform a Safe Mode update. If this does not work, you may require a CTRTransfer.
fs (0000000000000000)
- Can be anything from SD card problems to hardware issues.
hid (0004013000001D02)
- Potential hardware problems.
- Broken HOME Menu theme.
- To fix, go into the folder
sdmc:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/
and delete the folder matching your region, one of the following:- USA:
000002cd
- EUR:
000002ce
- JPN:
000002cc
- USA:
- To fix, go into the folder
- Broken HOME Menu extra data.
- To fix, go into the folder
sdmc:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/
and delete the folder matching your region, one of the following:- USA:
0000008f
- EUR:
00000098
- JPN:
00000082
- KOR:
000000A9
- USA:
- To fix, go into the folder
- Broken HOME Menu application.
- To fix, perform a Safe Mode update.
- If this does not fix it, attempt to enter System Settings before the crash occurs and find the broken application in Data Management, if possible.
- If this does not fix it, you may try to enter GodMode9 and use its title list to find the broken application - this is risky, however, and should not be attempted without guidance unless you know exactly what you are doing. For guidance, join the Nintendo Homebrew Discord.
- The f000000b folder in
SYSNAND CTRNAND
is broken, its exact location being at[1:]/data/<ID0>/extdata/00048000/f000000b
.- To fix, backup that folder by pressing R+A while highlighting it, then select
Copy to 0:/gm9/out
. Once backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
- To fix, backup that folder by pressing R+A while highlighting it, then select
pm (0000000000000000), undefined instruction
- The installed version of Luma3DS does not support the current firmware version.
- To fix, update CFW.
During use
loader (0000000000000000)
If the hexadecimal number next to R0 starts with 'C' or 'D', search for it in 3DS:Error_screens/Luma3DS_ErrDisp.
These errors are usually due to corruption, such as a faulty SD card, dying game cartridge, or dirty cartridge reader.