3DS:Safe Mode: Difference between revisions

Latest revision as of 02:24, 31 July 2026

Safe Mode, also known as SAFE_FIRM, is a part of the 3DS' firmware that allows the device to perform a System Update without loading the HOME Menu or most system functions. To access Safe Mode, hold L+R+↑+A and then power on the console. If successful, the 3DS will show the System Update screen.

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

Exploits

In 11.16.0, the recommended CFW method is unSAFE_MODE, which uses a flaw in Safe Mode's Internet Settings to install custom firmware. It uses a flaw that was already fixed in firmware 3.0, but 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:

safecerthax was an exploit for original 3DS and original 3DS XL models that exploited under Safe Mode the same SSLoth vulnerability available before 11.14.0 on NATIVE_FIRM. This was patched in 11.15 by patching SAFE_FIRM's SSLoth in the same way.
safehax allowed the console to load a .bin payload after being loaded from Homebrew Launcher due to SAFE_FIRM not being patched for firmlaunch-hax (while NATIVE_FIRM was patched since 9.5.0), and the console being able to load the Safe Mode firmware after 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

Safe Mode reinstalls most deleted or corrupted system titles, like a regular System Update, which can fix some related issues.

Troubleshooting

If a crash on boot is caused by corrupted/deleted system titles or extremely outdated firmware, Safe Mode will stay unaffected as its titles are different from the ones used by NATIVE_FIRM.

As written above, it may repair the titles causing the brick, but if the problem is still not fixed, you will need GodMode9, so keep the custom firmware installed. If you cannot in any way access GodMode9, you will most likely need a flashcart compatible with ntrboot to fix the issue.

@@ 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.
+<languages/>
+<translate>
+<!--T:1-->
+'''Safe Mode''', also known as '''SAFE_FIRM''', is a part of the 3DS' 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|R|Up|A}} and then power on the console. If successful, the 3DS will show the System Update screen.<br><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 == <!--T:2-->
-== Why it's useful ==
+=== Exploits === <!--T:3-->
-=== Exploits ===
+<!--T: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 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.
+In 11.16.0, the recommended CFW method is [[3DS:Alternate Exploits/Installing boot9strap (HBL-USM)|unSAFE_MODE]], which uses a flaw in Safe Mode's Internet Settings to install custom firmware. It uses a flaw that was already fixed in firmware 3.0, but 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.
-=== Redownloading system applications ===
+<!--T:5-->
+There are two other Safe Mode-based exploits that are now unusable:
+</translate>
+*<translate><!--T:6--> [[<tvar name=1>3DS:Alternate Exploits/Installing boot9strap (safecerthax)</tvar>|safecerthax]] was an exploit for original 3DS and original 3DS XL models that exploited under Safe Mode the same SSLoth vulnerability available before 11.14.0 on NATIVE_FIRM. This was patched in 11.15 by patching SAFE_FIRM's SSLoth in the same way.</translate>
+*<translate><!--T:7--> [<tvar name=1>https://github.com/TiniVi/safehax</tvar> safehax] allowed the console to load a <code>.bin</code> payload after being loaded from Homebrew Launcher due to SAFE_FIRM not being patched for firmlaunch-hax (while NATIVE_FIRM was patched since 9.5.0), and the console being able to load the Safe Mode firmware after 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 === <!--T:8-->
-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.
+<!--T:9-->
+Safe Mode reinstalls most deleted or corrupted system titles, like a regular System Update, which can fix some related issues.
-=== Unbricking ===
+=== Troubleshooting === <!--T:10-->
-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.
+<!--T:12-->
+If a crash on boot is caused by corrupted/deleted system titles or extremely outdated firmware, Safe Mode will stay unaffected as its titles are different from the ones used by NATIVE_FIRM.
+<!--T:13-->
+As written above, it may repair the titles causing the brick, but if the problem is still not fixed, you will need GodMode9, so keep the custom firmware installed. If you cannot in any way access GodMode9, you will most likely need [[<tvar name=1>3DS:ntrboot</tvar>|a flashcart compatible with ntrboot]] to fix the issue.
+</translate>
+[[Category:Nintendo 3DS information{{#translation:}}]]