User:StarlitSkies/sandbox/WIP1 - Revision history

StarlitSkies: entry 4: what

2023-11-22T04:47:10Z

entry 4: what

← Older revision		Revision as of 04:47, 22 November 2023
Line 5:		Line 5:
	"a following of the following"		"a following of the following"
	----		----
			{{Special:AllPages/3DS\|hideredirects=1}}
			----
			{{Special:Recentchanges\|namespace=3010%3B3011\|limit=20\|days=14}}

StarlitSkies: entry two: cool, the basics work as expected. time for chaos

2023-11-22T04:37:22Z

entry two: cool, the basics work as expected. time for chaos

← Older revision	Revision as of 04:37, 22 November 2023
Line 1:	Line 1:
		{{User:StarlitSkies/sandbox}}
		----
		the following is a following of the following

		"a following of the following"
		----

StarlitSkies: i've learned my lesson about tables. your services are no longer required

2023-11-11T04:21:32Z

i've learned my lesson about tables. your services are no longer required

Show changes

StarlitSkies: at least 75% of all stairs accidents happen on stairs

2023-11-11T03:16:18Z

at least 75% of all stairs accidents happen on stairs

← Older revision		Revision as of 03:16, 11 November 2023
Line 30:		Line 30:
	Arm9 errors are sorted by their '''exception type'''.		Arm9 errors are sorted by their '''exception type'''.

	<span style="font-size:~~140~~%; display:flex; justify-content:center "><h4>Error On Boot</h4></span>		<span style="font-size:175%; display:flex; justify-content:center "><h4>Error On Boot</h4></span>
	{\| class="wikitable" style="margin: auto"		{\| class="wikitable" style="margin: auto"
	! style="font-size:~~120~~%;" \| Exception Type		! style="font-size:95%;" \| Exception Type
	! style="font-size:~~120~~%;" \| Problem & Solution		! style="font-size:95%;" \| Problem & Solution
	\|-		\|-
	\| rowspan="3" \| <h5>Any Type</h5>		\| rowspan="3" \| <h5>Any Type</h5>
Line 64:		Line 64:
	\|}		\|}

	<span style="font-size:~~140~~%; display:flex; justify-content:center"><h4>Error During Use</h4></span>		<span style="font-size:175%; display:flex; justify-content:center"><h4>Error During Use</h4></span>
	{\| class="wikitable" style="margin: auto"		{\| class="wikitable" style="margin: auto"
	! style="font-size:~~120~~%;" \| Exception Type		! style="font-size:95%;" \| Exception Type
	! style="font-size:~~120~~%;" \| Problem & Solution		! style="font-size:95%;" \| Problem & Solution
	\|-		\|-
	\| <h5>data abort</h5>		\| <h5>data abort</h5>
Line 77:		Line 77:
	All Arm11 errors are sorted by their '''current process'''.		All Arm11 errors are sorted by their '''current process'''.

	<span style="font-size:~~140~~%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>		<span style="font-size:175%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>
	{\| class="wikitable" style="margin: auto"		{\| class="wikitable" style="margin: auto"
	! style="font-size:~~120~~%;" \| Current Process		! style="font-size:95%;" \| Current Process
	! style="font-size:~~120~~%;" \| Exception Type		! style="font-size:95%;" \| Exception Type
	! style="font-size:~~120~~%;" \| Problem & Solution		! style="font-size:95%;" \| Problem & Solution
	\|-		\|-
	\| <h5>boss</h5> \|\| data abort		\| <h5>boss</h5> \|\| data abort
Line 104:		Line 104:
	\|-		\|-
	\| <h5>menu</h5>		\| <h5>menu</h5>
			\| data abort
	\| Your HOME Menu has an Albanian virus and is trying to delete itself.		\| Your HOME Menu has an Albanian virus and is trying to delete itself.
	:Help it by opening SafeMode9 on your 3DS and then throwing a brick at the console.		:Help it by opening SafeMode9 on your 3DS and then throwing a brick at the console.
Line 124:		Line 125:
	<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>		<span style="font-size:140%; display:flex; justify-content:center"><h4>Error During Use</h4></span>
	{\| class="wikitable" style="margin: auto"		{\| class="wikitable" style="margin: auto"
	! style="font-size:~~120~~%;" \| Current Process		! style="font-size:95%;" \| Current Process
	! style="font-size:~~120~~%;" \| Exception Type		! style="font-size:95%;" \| Exception Type
	! style="font-size:~~120~~%;" \| Problem & Solution		! style="font-size:95%;" \| Problem & Solution
	\|-		\|-
	\| <h5>3dsx_app</h5> \|\| any		\| <h5>3dsx_app</h5> \|\| any

StarlitSkies: help i'm being held hostage by mediawiki

2023-11-11T03:08:54Z

help i'm being held hostage by mediawiki

← Older revision		Revision as of 03:08, 11 November 2023
Line 103:		Line 103:
	::If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.		::If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.
	\|-		\|-
	~~\| rowspan="3"~~ \| <h5>menu</h5>		\| <h5>menu</h5>
	\| ~~<h6>data abort</h6>~~		\| Your HOME Menu has an Albanian virus and is trying to delete itself.
	~~\| One or more of the following issues:~~		:Help it by opening SafeMode9 on your 3DS and then throwing a brick at the console.
	~~Toast of the Peak~~
	\|-
	~~\| <h6>prefetch abort</h6>~~
	~~\| An installation of menuhax~~ is ~~conflicting with the custom firmware~~.
	:~~To fix, place the <code>menuhax67_installer.3dsx</code> file from [[https://github.com/zoogie/menuhax67/releases/download/v1.1/menuhax67_v1.1.zip this download]] into <code>sd:/3ds</code>, run~~ it ~~through Homebrew Launcher,~~ and ~~choose REMOVE.~~
	\|-
	~~\| <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>.~~
	~~: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~~.
	\|-		\|-
	\| <h5>ns</h5> \|\| prefetch abort (svcBreak)		\| <h5>ns</h5> \|\| prefetch abort (svcBreak)

StarlitSkies: Toast of the Peak

2023-11-11T03:03:21Z

Toast of the Peak

← Older revision		Revision as of 03:03, 11 November 2023
Line 106:		Line 106:
	\| <h6>data abort</h6>		\| <h6>data abort</h6>
	\| One or more of the following issues:		\| One or more of the following issues:
	~~Your installed theme is corrupted or broken.~~		Toast of the Peak
	~~:To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one~~ of the ~~following:~~
	~~::USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>~~
	~~The HOME Menu extra data is corrupted.~~
	~~:To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:~~
	~~::USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>~~
	~~An installed application is corrupted.~~
	: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>		\| <h6>prefetch abort</h6>

StarlitSkies: remove layered rowspan to fix formatting on mobile

2023-11-11T02:55:30Z

remove layered rowspan to fix formatting on mobile

← Older revision		Revision as of 02:55, 11 November 2023
Line 28:		Line 28:

	=== <big>Arm9</big> ===		=== <big>Arm9</big> ===
	~~All~~ Arm9 errors are sorted by their '''exception type'''.		Arm9 errors are sorted by their '''exception type'''.

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

	=== <big>Arm11</big> ===		=== <big>Arm11</big> ===
	All Arm11 errors are sorted ~~alphabetically~~ by their '''current process'''.		All Arm11 errors are sorted by their '''current process'''.

	<span style="font-size:140%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>		<span style="font-size:140%; display:flex; justify-content:center"><h4>Error On Boot</h4></span>
Line 103:		Line 103:
	::If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.		::If neither of these work, the console has a serious issue. Join the [https://discord.gg/C29hYvh Nintendo Homebrew Discord] and ask, in English, for help.
	\|-		\|-
	\| rowspan="5" \| <h5>menu</h5>		\| rowspan="3" \| <h5>menu</h5>
	~~\| rowspan="3"~~ \| <h6>data abort</h6>		\| <h6>data abort</h6>
	\| ~~Broken HOME Menu~~ theme.		\| One or more of the following issues:
			Your installed theme is corrupted or broken.
	:To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:		:To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
	::USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>		::USA: <code>000002cd</code><br>EUR: <code>000002ce</code><br>JPN: <code>000002cc</code>
	\|-		The HOME Menu extra data is corrupted.
	~~\| Broken~~ HOME Menu extra data.
	:To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:		:To fix, go into the folder <code>sd:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:
	::USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>		::USA: <code>0000008f</code><br>EUR: <code>00000098</code><br>JPN: <code>00000082</code><br>KOR: <code>000000A9</code>
	\|-		An installed application is corrupted.
	~~\| Broken HOME Menu~~ application.
	: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]].		: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]].
	\|-		\|-

StarlitSkies: test of a table of contents made via html tags

2023-11-11T02:17:40Z

test of a table of contents made via html tags

Show changes

StarlitSkies: this hasn't needed to exist for months now

2023-08-29T22:25:28Z

this hasn't needed to exist for months now

← Older revision		Revision as of 22:25, 29 August 2023
Line 1:		Line 1:
	~~This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.~~
	~~==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.
	**'''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. Common or unique processes are as follows:
	**'''fs''': Files on your SD card or NAND are having issues.
	**'''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.
	**'''pm''': Almost always, <code>boot.firm</code> is too outdated to work.
	**'''loader''': The app you last tried to run has an error.
	**'''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:
	**'''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.

	~~==Known Errors==~~
	~~Note that the prefixes on file paths refer to the starting location. <code>sdmc:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.~~
	~~{{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>~~
	~~\|-\|Arm9=~~

	~~{{#tag:tabber\|~~

	~~On Boot=~~
	~~{\| class="wikitable" style="margin: auto"~~
	~~!Exception Type !! Solution~~
	\|-
	~~\|Any~~
	\|
	*Files on the SD are corrupted.
	**To fix, [[Checking_SD_card_integrity\|verify that your 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>.
	\|-
	~~\|Data abort~~
	\|
	*<code>SYSNAND TWLN</code>'s <code>[2:]/shared2</code> folder is missing.
	**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]].
	\|-
	~~\| Prefetch abort (svcBreak)~~
	\|
	*The system's movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but its flag indicates otherwise.
	*<code>SYSNAND CTRNAND</code> has bad CMACs.
	**To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. Your system will act like it has been formatted after this, and this is intended.
	\|}
	~~{{!}}-{{!}}~~
	~~During Use=~~

	*Files on the SD are corrupted.
	**To fix, [[Checking_SD_card_integrity\|verify that your 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 again.

	}}

	~~\|-\|Arm11=~~

	~~{{#tag:tabber\|~~

	~~On Boot=~~
	{\|
	~~!Current Process !! Exception Type !! Error & Solution~~
	\|-
	\| boss \|\| data abort \|\| The current firmware version is too old for SpotPass to work. Perform a [[3DS:Safe Mode\|Safe Mode update]].<br>If this does not work, you may require [[3DS:CTRTransfer\|a CTRTransfer.]]
	\|-
	~~\|fs \|\| any \|\| Can be anything from SD card problems to hardware issues.~~
	\|-
	~~\|hid \|\| any \|\| Potential hardware problems.~~
	\|-
	\|ns \|\| prefetch abort (svcBreak) \|\| The [[3DS:Luma3DS/Configuration\|Luma configuration]] setting <code>Autoboot Homebrew</code> is set to boot to a title that does not exist.<br>To fix, disable the option or install an application that matches the title ID set in <code>sd:/luma/config.ini</code>.
	\|-
	~~\|rowspan="3"\|menu~~
	~~\|data abort~~
	\|
	Broken HOME Menu theme.<br>To fix, go into the folder <code>sdmc:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:<br>USA: <code>000002cd</code>, EUR: <code>000002ce</code>, JPN: <code>000002cc</code>
	Broken HOME Menu extra data.<br>To fix, go into the folder <code>sdmc:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:<br>USA: <code>0000008f</code>, EUR: <code>00000098</code>, JPN: <code>00000082</code>, KOR: <code>000000A9</code>
	Broken HOME Menu application.<br>To fix, 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]].
	\|-
	~~\|prefetch abort~~
	\|
	An installation of menuhax is conflicting with your custom firmware.<br>To fix, place the <code>menuhax67_installer.3dsx</code> file from [[https://github.com/zoogie/menuhax67/releases/download/v1.1/menuhax67_v1.1.zip this download]] into <code>sdmc:/3ds</code>, run it through Homebrew Launcher, and choose REMOVE.
	\|-
	~~\|prefetch abort (svcBreak)~~
	~~\|*The f000000b folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.~~
	**To fix, backup that folder by pressing R+A while highlighting it, then select <code>Copy to 0:/gm9/out</code>. Once backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
	\|-
	~~\|pm \|\| undefined instruction \|\| Your installed version of Luma3DS does not support the current firmware version.<br>To fix, [[3dsguide:restoring-updating-cfw\|update CFW.]]~~
	~~\|}<nowiki>}</nowiki>~~
	~~{{!}}-{{!}}~~

	~~During Use=~~
	{\|
	~~!Current Process !! Exception Type !! Solution~~
	\|-
	\|loader \|\| undefined instruction \|\| An app you loaded has an issue. If the contents of R0 start with C or D, R0 is an error code - most of these are present on [[3DS:Error_screens/Luma3DS_ErrDisp\|this page]], but common codes to find here are as follows:<br>C8804478/C80044AB: A file or app that is supposed to exist was not found.<br>D900458B/D9004587: The app you loaded has corrupted data, savedata, or update(s).<br>
	\|}
	}}
	~~</tabber>~~

StarlitSkies: table nonsense. why am i trying to use nested tabbers with tables, anyway?

2023-03-02T07:28:33Z

table nonsense. why am i trying to use nested tabbers with tables, anyway?

← Older revision	Revision as of 07:28, 2 March 2023
Line 1:	Line 1:
		This page lists possible causes and fixes of Luma3DS exception screens. They are not applicable to every situation, but cover most common known issues.
		==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.
		**'''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. Common or unique processes are as follows:
		**'''fs''': Files on your SD card or NAND are having issues.
		**'''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.
		**'''pm''': Almost always, <code>boot.firm</code> is too outdated to work.
		**'''loader''': The app you last tried to run has an error.
		**'''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:
		**'''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.

		==Known Errors==
		Note that the prefixes on file paths refer to the starting location. <code>sdmc:/</code> refers to the SD card, and numbers in the format of <code>[X:]</code> refer to GodMode9's drive numbers.
		{{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>
		\|-\|Arm9=

		{{#tag:tabber\|

		On Boot=
		{\| class="wikitable" style="margin: auto"
		!Exception Type !! Solution
		\|-
		\|Any
		\|
		*Files on the SD are corrupted.
		**To fix, [[Checking_SD_card_integrity\|verify that your 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>.
		\|-
		\|Data abort
		\|
		*<code>SYSNAND TWLN</code>'s <code>[2:]/shared2</code> folder is missing.
		**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]].
		\|-
		\| Prefetch abort (svcBreak)
		\|
		*The system's movable, <code>[1:]/private/movable.sed</code>, is 288 bytes but its flag indicates otherwise.
		*<code>SYSNAND CTRNAND</code> has bad CMACs.
		**To fix, press R+A on the <code>SYSNAND CTRNAND</code> drive and <code>Fix CMACs for drive</code>. Your system will act like it has been formatted after this, and this is intended.
		\|}
		{{!}}-{{!}}
		During Use=

		*Files on the SD are corrupted.
		**To fix, [[Checking_SD_card_integrity\|verify that your 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 again.

		}}

		\|-\|Arm11=

		{{#tag:tabber\|

		On Boot=
		{\|
		!Current Process !! Exception Type !! Error & Solution
		\|-
		\| boss \|\| data abort \|\| The current firmware version is too old for SpotPass to work. Perform a [[3DS:Safe Mode\|Safe Mode update]].<br>If this does not work, you may require [[3DS:CTRTransfer\|a CTRTransfer.]]
		\|-
		\|fs \|\| any \|\| Can be anything from SD card problems to hardware issues.
		\|-
		\|hid \|\| any \|\| Potential hardware problems.
		\|-
		\|ns \|\| prefetch abort (svcBreak) \|\| The [[3DS:Luma3DS/Configuration\|Luma configuration]] setting <code>Autoboot Homebrew</code> is set to boot to a title that does not exist.<br>To fix, disable the option or install an application that matches the title ID set in <code>sd:/luma/config.ini</code>.
		\|-
		\|rowspan="3"\|menu
		\|data abort
		\|
		Broken HOME Menu theme.<br>To fix, go into the folder <code>sdmc:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:<br>USA: <code>000002cd</code>, EUR: <code>000002ce</code>, JPN: <code>000002cc</code>
		Broken HOME Menu extra data.<br>To fix, go into the folder <code>sdmc:/Nintendo 3DS/<ID0>/<ID1>/extdata/00000000/</code> and delete the folder matching your region, one of the following:<br>USA: <code>0000008f</code>, EUR: <code>00000098</code>, JPN: <code>00000082</code>, KOR: <code>000000A9</code>
		Broken HOME Menu application.<br>To fix, 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]].
		\|-
		\|prefetch abort
		\|
		An installation of menuhax is conflicting with your custom firmware.<br>To fix, place the <code>menuhax67_installer.3dsx</code> file from [[https://github.com/zoogie/menuhax67/releases/download/v1.1/menuhax67_v1.1.zip this download]] into <code>sdmc:/3ds</code>, run it through Homebrew Launcher, and choose REMOVE.
		\|-
		\|prefetch abort (svcBreak)
		\|*The f000000b folder in <code>SYSNAND CTRNAND</code> is broken, its exact location being at <code>[1:]/data/<ID0>/extdata/00048000/f000000b</code>.
		**To fix, backup that folder by pressing R+A while highlighting it, then select <code>Copy to 0:/gm9/out</code>. Once backed up, delete the folder. If this does not fix the issue, copy the folder back where it was.
		\|-
		\|pm \|\| undefined instruction \|\| Your installed version of Luma3DS does not support the current firmware version.<br>To fix, [[3dsguide:restoring-updating-cfw\|update CFW.]]
		\|}<nowiki>}</nowiki>
		{{!}}-{{!}}

		During Use=
		{\|
		!Current Process !! Exception Type !! Solution
		\|-
		\|loader \|\| undefined instruction \|\| An app you loaded has an issue. If the contents of R0 start with C or D, R0 is an error code - most of these are present on [[3DS:Error_screens/Luma3DS_ErrDisp\|this page]], but common codes to find here are as follows:<br>C8804478/C80044AB: A file or app that is supposed to exist was not found.<br>D900458B/D9004587: The app you loaded has corrupted data, savedata, or update(s).<br>
		\|}
		}}
		</tabber>