3DS:Safe Mode - Revision history

Ihaveahax: add {{#translation:}}

2025-08-07T23:40:24Z

add {{#translation:}}

← Older revision		Revision as of 23:40, 7 August 2025
Line 28:		Line 28:
	Because Safe Mode is in a unique partition of the 3DS' firmware (SAFE_FIRM), it can fix crashes on boot that are caused by corrupted/deleted system titles or extremely outdated firmware, as only NATIVE_FIRM is affected by these. The best way to avoid bricks is to keep custom firmware installed, however, and most crashes not in the above list will require access to GodMode9 to fix - if you have an issue that disables access to GodMode9, you will most likely need [[3DS:ntrboot\|a flashcart compatible with ntrboot]] to fix the issue.		Because Safe Mode is in a unique partition of the 3DS' firmware (SAFE_FIRM), it can fix crashes on boot that are caused by corrupted/deleted system titles or extremely outdated firmware, as only NATIVE_FIRM is affected by these. The best way to avoid bricks is to keep custom firmware installed, however, and most crashes not in the above list will require access to GodMode9 to fix - if you have an issue that disables access to GodMode9, you will most likely need [[3DS:ntrboot\|a flashcart compatible with ntrboot]] to fix the issue.
	</translate>		</translate>
	[[Category:Nintendo 3DS information]]		[[Category:Nintendo 3DS information{{#translation:}}]]

Ihaveahax: Marked this version for translation

2025-08-01T05:14:10Z

Marked this version for translation

← Older revision		Revision as of 05:14, 1 August 2025
Line 1:		Line 1:
	<languages/>		<languages/>
	<translate>		<translate>
			<!--T:1-->
	'''Safe Mode''', also known as '''SAFE_FIRM''', is a part of the 3DS' stock firmware that allows the device to perform a System Update without loading the HOME Menu or most system functions. To access Safe Mode, hold {{B\|L}} + {{B\|R}} + {{B\|(D-Pad Up)}} + {{B\|A}} and then powering on - if successful, the 3DS will show the System Update screen.<br>		'''Safe Mode''', also known as '''SAFE_FIRM''', is a part of the 3DS' stock firmware that allows the device to perform a System Update without loading the HOME Menu or most system functions. To access Safe Mode, hold {{B\|L}} + {{B\|R}} + {{B\|(D-Pad Up)}} + {{B\|A}} and then powering on - if successful, the 3DS will show the System Update screen.<br>
	There is no alternate keycombo, so if one of the needed buttons is broken, you will be unable to access Safe Mode.		There is no alternate keycombo, so if one of the needed buttons is broken, you will be unable to access Safe Mode.

	== Why it's useful ==		== Why it's useful == <!--T:2-->

	=== Exploits ===		=== Exploits === <!--T:3-->

			<!--T:4-->
	The custom firmware method recommended for 11.16.0, [[3DS:Alternate Exploits/Installing boot9strap (HBL-USM)\|unSAFE_MODE]], uses a flaw in Safe Mode's Internet Settings that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked).		The custom firmware method recommended for 11.16.0, [[3DS:Alternate Exploits/Installing boot9strap (HBL-USM)\|unSAFE_MODE]], uses a flaw in Safe Mode's Internet Settings that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked).

			<!--T:5-->
	There are two other Safe Mode-based exploits that are now unusable:		There are two other Safe Mode-based exploits that are now unusable:
	</translate>		</translate>
	<translate>* [[3DS:Alternate Exploits/Installing boot9strap (safecerthax)\|safecerthax]] was an exploit for original 3DS and original 3DS XL models that ran under Safe Mode, and used the SSLoth vulnerability that was still available under SAFE_FIRM. This was patched in 11.15 by patching SSLoth in a similar fashion to NATIVE.</translate>		<translate><!--T:6--> * [[3DS:Alternate Exploits/Installing boot9strap (safecerthax)\|safecerthax]] was an exploit for original 3DS and original 3DS XL models that ran under Safe Mode, and used the SSLoth vulnerability that was still available under SAFE_FIRM. This was patched in 11.15 by patching SSLoth in a similar fashion to NATIVE.</translate>
	<translate>* [https://github.com/TiniVi/safehax safehax] allowed the console to load a <code>.bin</code> payload after being loaded from Homebrew Launcher due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit was given a partial patch in version 11.3 and fully patched in version 11.4.</translate>		<translate><!--T:7--> * [https://github.com/TiniVi/safehax safehax] allowed the console to load a <code>.bin</code> payload after being loaded from Homebrew Launcher due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit was given a partial patch in version 11.3 and fully patched in version 11.4.</translate>
	<translate>		<translate>
	=== Redownloading system applications ===		=== Redownloading system applications === <!--T:8-->

			<!--T:9-->
	Safe Mode reinstalls most deleted or corrupted system titles, the same as a regular System Update, which can also help if you need one of those titles to fix another issue.		Safe Mode reinstalls most deleted or corrupted system titles, the same as a regular System Update, which can also help if you need one of those titles to fix another issue.

	=== Troubleshooting ===		=== Troubleshooting === <!--T:10-->

			<!--T:11-->
	Because Safe Mode is in a unique partition of the 3DS' firmware (SAFE_FIRM), it can fix crashes on boot that are caused by corrupted/deleted system titles or extremely outdated firmware, as only NATIVE_FIRM is affected by these. The best way to avoid bricks is to keep custom firmware installed, however, and most crashes not in the above list will require access to GodMode9 to fix - if you have an issue that disables access to GodMode9, you will most likely need [[3DS:ntrboot\|a flashcart compatible with ntrboot]] to fix the issue.		Because Safe Mode is in a unique partition of the 3DS' firmware (SAFE_FIRM), it can fix crashes on boot that are caused by corrupted/deleted system titles or extremely outdated firmware, as only NATIVE_FIRM is affected by these. The best way to avoid bricks is to keep custom firmware installed, however, and most crashes not in the above list will require access to GodMode9 to fix - if you have an issue that disables access to GodMode9, you will most likely need [[3DS:ntrboot\|a flashcart compatible with ntrboot]] to fix the issue.
	</translate>		</translate>
	[[Category:Nintendo 3DS information]]		[[Category:Nintendo 3DS information]]

Ihaveahax: translate tags

2025-08-01T05:02:00Z

translate tags

← Older revision		Revision as of 05:02, 1 August 2025
Line 1:		Line 1:
			<languages/>
			<translate>
	'''Safe Mode''', also known as '''SAFE_FIRM''', is a part of the 3DS' stock firmware that allows the device to perform a System Update without loading the HOME Menu or most system functions. To access Safe Mode, hold {{B\|L}} + {{B\|R}} + {{B\|(D-Pad Up)}} + {{B\|A}} and then powering on - if successful, the 3DS will show the System Update screen.<br>		'''Safe Mode''', also known as '''SAFE_FIRM''', is a part of the 3DS' stock firmware that allows the device to perform a System Update without loading the HOME Menu or most system functions. To access Safe Mode, hold {{B\|L}} + {{B\|R}} + {{B\|(D-Pad Up)}} + {{B\|A}} and then powering on - if successful, the 3DS will show the System Update screen.<br>
	There is no alternate keycombo, so if one of the needed buttons is broken, you will be unable to access Safe Mode.		There is no alternate keycombo, so if one of the needed buttons is broken, you will be unable to access Safe Mode.
Line 5:		Line 7:

	=== Exploits ===		=== Exploits ===

	The custom firmware method recommended for 11.16.0, [[3DS:Alternate Exploits/Installing boot9strap (HBL-USM)\|unSAFE_MODE]], uses a flaw in Safe Mode's Internet Settings that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked).		The custom firmware method recommended for 11.16.0, [[3DS:Alternate Exploits/Installing boot9strap (HBL-USM)\|unSAFE_MODE]], uses a flaw in Safe Mode's Internet Settings that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked).

	There are two other Safe Mode-based exploits that are now unusable:		There are two other Safe Mode-based exploits that are now unusable:
			</translate>
			<translate>* [[3DS:Alternate Exploits/Installing boot9strap (safecerthax)\|safecerthax]] was an exploit for original 3DS and original 3DS XL models that ran under Safe Mode, and used the SSLoth vulnerability that was still available under SAFE_FIRM. This was patched in 11.15 by patching SSLoth in a similar fashion to NATIVE.</translate>
			<translate>* [https://github.com/TiniVi/safehax safehax] allowed the console to load a <code>.bin</code> payload after being loaded from Homebrew Launcher due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit was given a partial patch in version 11.3 and fully patched in version 11.4.</translate>
			<translate>
			=== Redownloading system applications ===

	~~- [[3DS:Alternate Exploits/Installing boot9strap (safecerthax)\|safecerthax]] was an exploit for original 3DS and original 3DS XL models that ran under~~ Safe Mode, ~~and used~~ the ~~SSLoth vulnerability that was still available under SAFE_FIRM. This was patched in 11.15 by patching SSLoth in~~ a ~~similar fashion~~ to ~~NATIVE~~.		Safe Mode reinstalls most deleted or corrupted system titles, the same as a regular System Update, which can also help if you need one of those titles to fix another issue.

	- [https://github.com/TiniVi/safehax safehax] allowed the console to load a <code>.bin</code> payload after being loaded from Homebrew Launcher due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit was given a partial patch in version 11.3 and fully patched in version 11.4.		=== Troubleshooting ===

	~~===Redownloading system applications===~~
	~~Safe Mode reinstalls most deleted or corrupted system titles, the same as a regular System Update, which can also help if you need one of those titles to fix another issue.~~

	~~===Troubleshooting===~~
	Because Safe Mode is in a unique partition of the 3DS' firmware (SAFE_FIRM), it can fix crashes on boot that are caused by corrupted/deleted system titles or extremely outdated firmware, as only NATIVE_FIRM is affected by these. The best way to avoid bricks is to keep custom firmware installed, however, and most crashes not in the above list will require access to GodMode9 to fix - if you have an issue that disables access to GodMode9, you will most likely need [[3DS:ntrboot\|a flashcart compatible with ntrboot]] to fix the issue.		Because Safe Mode is in a unique partition of the 3DS' firmware (SAFE_FIRM), it can fix crashes on boot that are caused by corrupted/deleted system titles or extremely outdated firmware, as only NATIVE_FIRM is affected by these. The best way to avoid bricks is to keep custom firmware installed, however, and most crashes not in the above list will require access to GodMode9 to fix - if you have an issue that disables access to GodMode9, you will most likely need [[3DS:ntrboot\|a flashcart compatible with ntrboot]] to fix the issue.
			</translate>
	[[Category:Nintendo 3DS information]]		[[Category:Nintendo 3DS information]]

ToxicAven: Prefer HBL-USM over BB3 USM

2024-01-28T21:10:04Z

Prefer HBL-USM over BB3 USM

← Older revision		Revision as of 21:10, 28 January 2024
Line 5:		Line 5:

	=== Exploits ===		=== Exploits ===
	The custom firmware method recommended for 11.16.0, [[3DS:Alternate Exploits/Installing boot9strap (USM)\|unSAFE_MODE]], uses a flaw in Safe Mode's Internet Settings that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked).		The custom firmware method recommended for 11.16.0, [[3DS:Alternate Exploits/Installing boot9strap (HBL-USM)\|unSAFE_MODE]], uses a flaw in Safe Mode's Internet Settings that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked).

	There are two other Safe Mode-based exploits that are now unusable:		There are two other Safe Mode-based exploits that are now unusable:

ToxicAven: Use wiki USM instructions, guide 404s

2024-01-28T21:05:52Z

Use wiki USM instructions, guide 404s

← Older revision		Revision as of 21:05, 28 January 2024
Line 5:		Line 5:

	=== Exploits ===		=== Exploits ===
	The custom firmware method recommended for 11.16.0, [[~~3dsguide~~:~~installing-~~boot9strap-(~~usm~~)\|unSAFE_MODE]], uses a flaw in Safe Mode's Internet Settings that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked).		The custom firmware method recommended for 11.16.0, [[3DS:Alternate Exploits/Installing boot9strap (USM)\|unSAFE_MODE]], uses a flaw in Safe Mode's Internet Settings that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked).

	There are two other Safe Mode-based exploits that are now unusable:		There are two other Safe Mode-based exploits that are now unusable:

StarlitSkies: added Category:Nintendo 3DS information using HotCat

2023-01-24T07:28:02Z

added Category:Nintendo 3DS information using HotCat

← Older revision		Revision as of 07:28, 24 January 2023
Line 18:		Line 18:
	===Troubleshooting===		===Troubleshooting===
	Because Safe Mode is in a unique partition of the 3DS' firmware (SAFE_FIRM), it can fix crashes on boot that are caused by corrupted/deleted system titles or extremely outdated firmware, as only NATIVE_FIRM is affected by these. The best way to avoid bricks is to keep custom firmware installed, however, and most crashes not in the above list will require access to GodMode9 to fix - if you have an issue that disables access to GodMode9, you will most likely need [[3DS:ntrboot\|a flashcart compatible with ntrboot]] to fix the issue.		Because Safe Mode is in a unique partition of the 3DS' firmware (SAFE_FIRM), it can fix crashes on boot that are caused by corrupted/deleted system titles or extremely outdated firmware, as only NATIVE_FIRM is affected by these. The best way to avoid bricks is to keep custom firmware installed, however, and most crashes not in the above list will require access to GodMode9 to fix - if you have an issue that disables access to GodMode9, you will most likely need [[3DS:ntrboot\|a flashcart compatible with ntrboot]] to fix the issue.

			[[Category:Nintendo 3DS information]]

Lifehackerhansol: /* Exploits */

2022-11-15T03:28:20Z

Exploits

← Older revision		Revision as of 03:28, 15 November 2022
Line 5:		Line 5:

	=== Exploits ===		=== Exploits ===
	The custom firmware method recommended for 11.16.0, [[3dsguide:installing-boot9strap-(usm)\|unSAFE_MODE]], uses a flaw in Safe Mode that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked). There~~'s also an alternate CFW method for versions 11.14.0 and below called~~ [[3DS:Alternate Exploits/Installing boot9strap (safecerthax)\|safecerthax]] that ~~allows~~ the ~~user~~ to ~~install a modern CFW setup using SafeB9SInstaller~~.~~<br>Another exploit '''that is now unusable''' called~~ [https://github.com/TiniVi/safehax safehax] allowed the console to load a <code>.bin</code> payload after being loaded from Homebrew Launcher due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit was given a partial patch in version 11.3 and fully patched in version 11.4.		The custom firmware method recommended for 11.16.0, [[3dsguide:installing-boot9strap-(usm)\|unSAFE_MODE]], uses a flaw in Safe Mode's Internet Settings that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked).

			There are two other Safe Mode-based exploits that are now unusable:

			- [[3DS:Alternate Exploits/Installing boot9strap (safecerthax)\|safecerthax]] was an exploit for original 3DS and original 3DS XL models that ran under Safe Mode, and used the SSLoth vulnerability that was still available under SAFE_FIRM. This was patched in 11.15 by patching SSLoth in a similar fashion to NATIVE.

			- [https://github.com/TiniVi/safehax safehax] allowed the console to load a <code>.bin</code> payload after being loaded from Homebrew Launcher due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit was given a partial patch in version 11.3 and fully patched in version 11.4.

	===Redownloading system applications===		===Redownloading system applications===

Suazil: added mention to safecerthax (probably more important than adding safehax since this one actually allows you to get a modern CFW setup) and fixed a typo (unusuable => unusable)

2022-11-15T01:19:02Z

added mention to safecerthax (probably more important than adding safehax since this one actually allows you to get a modern CFW setup) and fixed a typo (unusuable => unusable)

← Older revision		Revision as of 01:19, 15 November 2022
Line 5:		Line 5:

	=== Exploits ===		=== Exploits ===
	The custom firmware method recommended for 11.16.0, [[3dsguide:installing-boot9strap-(usm)\|unSAFE_MODE]], uses a flaw in Safe Mode that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked).<br>Another exploit '''that is now ~~unusuable~~''' called [https://github.com/TiniVi/safehax safehax] allowed the console to load a <code>.bin</code> payload after being loaded from Homebrew Launcher due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit was given a partial patch in version 11.3 and fully patched in version 11.4.		The custom firmware method recommended for 11.16.0, [[3dsguide:installing-boot9strap-(usm)\|unSAFE_MODE]], uses a flaw in Safe Mode that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked). There's also an alternate CFW method for versions 11.14.0 and below called [[3DS:Alternate Exploits/Installing boot9strap (safecerthax)\|safecerthax]] that allows the user to install a modern CFW setup using SafeB9SInstaller.<br>Another exploit '''that is now unusable''' called [https://github.com/TiniVi/safehax safehax] allowed the console to load a <code>.bin</code> payload after being loaded from Homebrew Launcher due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit was given a partial patch in version 11.3 and fully patched in version 11.4.

	===Redownloading system applications===		===Redownloading system applications===

StarlitSkies: general overhaul: fix factual stuff, add links, style fixes, & condense wikitext

2022-10-18T23:08:10Z

general overhaul: fix factual stuff, add links, style fixes, & condense wikitext

← Older revision		Revision as of 23:08, 18 October 2022
Line 1:		Line 1:
	'''Safe Mode''' is ~~an option built into every~~ 3DS that allows the device to perform a System Update without ~~booting to~~ the HOME Menu. ~~You can~~ access Safe Mode ~~by holding (Left Shoulder)~~ + ~~(Right Shoulder)~~ + (D-Pad Up) + (A) on ~~boot. If you were~~ successful, the 3DS will show the System Update screen ~~and allow you to update~~.		'''Safe Mode''', also known as '''SAFE_FIRM''', is a part of the 3DS' stock firmware that allows the device to perform a System Update without loading the HOME Menu or most system functions. To access Safe Mode, hold {{B\|L}} + {{B\|R}} + {{B\|(D-Pad Up)}} + {{B\|A}} and then powering on - if successful, the 3DS will show the System Update screen.<br>
			There is no alternate keycombo, so if one of the needed buttons is broken, you will be unable to access Safe Mode.
	There is no ~~alternative key combination~~, so if one of the ~~necessary~~ buttons is broken, you will be unable to access Safe Mode.

	== Why it's useful ==		== Why it's useful ==

	=== Exploits ===		=== Exploits ===
	The custom firmware method recommended for 11.16.0, [[3dsguide:installing-boot9strap-(usm)\|unSAFE_MODE]], uses a flaw in Safe Mode that can be used to install custom firmware. This is ~~generally~~ because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no ~~other ways~~ to fix a brick ~~caused~~ by a system update). Another ~~outdated~~ exploit called [https://github.com/TiniVi/safehax safehax] allowed the console to load a ~~payload in the~~ .bin ~~format~~ after being loaded from Homebrew Launcher due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit ~~is '''OUTDATED''' and will not work~~ in ~~versions higher than~~ 11.3 ~~since Nintendo released a fix that made the console unable to boot SAFE_FIRM after a normal boot~~.		The custom firmware method recommended for 11.16.0, [[3dsguide:installing-boot9strap-(usm)\|unSAFE_MODE]], uses a flaw in Safe Mode that can be used to install custom firmware. This is because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no way to fix a brick by doing a system update if SAFE_FIRM were also bricked).<br>Another exploit '''that is now unusuable''' called [https://github.com/TiniVi/safehax safehax] allowed the console to load a <code>.bin</code> payload after being loaded from Homebrew Launcher due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit was given a partial patch in version 11.3 and fully patched in version 11.4.

	~~=== Redownloading system applications ===~~

	~~Just like a normal System Update, a Safe Mode update will redownload some system applications if they have been somehow lost, which can get you out of some tight situations~~.

	=== ~~Unbricking~~ ===		===Redownloading system applications===
			Safe Mode reinstalls most deleted or corrupted system titles, the same as a regular System Update, which can also help if you need one of those titles to fix another issue.

	Because Safe Mode is (~~somewhat~~) ~~separate from the normal firmware~~, it can ~~help save you from certain kinds of bricks (such~~ as ~~[[3DS:Keyboard Unbrick]], since the keyboard will work in Safe Mode even if it~~ is ~~broken in HOME Menu)~~. ~~That being said, the~~ best way to avoid bricks is to keep custom firmware installed.		===Troubleshooting===
			Because Safe Mode is in a unique partition of the 3DS' firmware (SAFE_FIRM), it can fix crashes on boot that are caused by corrupted/deleted system titles or extremely outdated firmware, as only NATIVE_FIRM is affected by these. The best way to avoid bricks is to keep custom firmware installed, however, and most crashes not in the above list will require access to GodMode9 to fix - if you have an issue that disables access to GodMode9, you will most likely need [[3DS:ntrboot\|a flashcart compatible with ntrboot]] to fix the issue.

Suazil: replaced "being loaded by another exploit" with "being loaded by homebrew launcher"

2022-10-18T20:54:17Z

replaced "being loaded by another exploit" with "being loaded by homebrew launcher"

← Older revision		Revision as of 20:54, 18 October 2022
Line 6:		Line 6:

	=== Exploits ===		=== Exploits ===
	The custom firmware method recommended for 11.16.0, [[3dsguide:installing-boot9strap-(usm)\|unSAFE_MODE]], uses a flaw in Safe Mode that can be used to install custom firmware. This is generally because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no other ways to fix a brick caused by a system update). Another outdated exploit called [https://github.com/TiniVi/safehax safehax] allowed the console to load a payload after being loaded ~~with another exploit~~ due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit is '''OUTDATED''' and will not work in versions higher than 11.3 since Nintendo released a fix that made the console unable to boot SAFE_FIRM after a normal boot.		The custom firmware method recommended for 11.16.0, [[3dsguide:installing-boot9strap-(usm)\|unSAFE_MODE]], uses a flaw in Safe Mode that can be used to install custom firmware. This is generally because Nintendo is more reluctant to update Safe Mode to patch exploits (since an unmodded 3DS would have no other ways to fix a brick caused by a system update). Another outdated exploit called [https://github.com/TiniVi/safehax safehax] allowed the console to load a payload in the .bin format after being loaded from Homebrew Launcher due to the Safe Mode firmware being outdated and the console being able to load SAFE_FIRM (the Safe Mode firmware) when the console was booted into normal firmware. This exploit is '''OUTDATED''' and will not work in versions higher than 11.3 since Nintendo released a fix that made the console unable to boot SAFE_FIRM after a normal boot.

	=== Redownloading system applications ===		=== Redownloading system applications ===