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

3DS:Error screens/Luma3DS exception screen (view source)

Revision as of 14:44, 22 May 2024

2,235 bytes added , 5 months ago

m

typo on loader undefined instr

Thepikachugamer

24

edits

@@ Line 18: / Line 18: @@
 **'''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 WiFi.
+**'''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:
@@ Line 44: / Line 44: @@
 ** To fix, create this folder.
 * System titles have been deleted.
-** To fix, perform a [[3DS:Safe Mode|Safe Mode update]].<br>If this does not work, perform a [[3DS:CTRTransfer|CTRTransfer]].
+** 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>
@@ Line 78: / Line 78: @@
 * 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]], 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.
+*** 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]].
+** [[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.
+* Potential hardware problems, or an instance of rehid is crashing.
-** 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.
+** 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>.
-*** [[3DS:Hardware test|3ds_hw_test]] or [[3DS:ctrcheck|ctrcheck]] may help with fault isolation.
+*** 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>ic2/gsp/mcu/pxi/spi/</h5>
+<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.
@@ Line 118: / Line 125: @@
 ***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>.
+** 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]]
@@ Line 163: / Line 171: @@
 <h5>loader</h5>
-* 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]].
+* <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.