3DS:Safe Mode: Difference between revisions
From Hacks Guide Wiki
More actions
m move bullet points outside translation tags |
misc editing + added more infos about patches being fixed earlier in NATIVE_FIRM (sources : usm readme and 3dbrew "3DS System Flaws" |
||
| Line 2: | Line 2: | ||
<translate> | <translate> | ||
<!--T:1--> | <!--T:1--> | ||
'''Safe Mode''', also known as '''SAFE_FIRM''', is a part of the 3DS' | '''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 alternate keycombo, so if one of the needed buttons is broken, you will be unable to access Safe Mode. | ||
| Line 10: | Line 10: | ||
<!--T:4--> | <!--T:4--> | ||
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. | |||
<!--T:5--> | <!--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><!--T:6--> [[3DS:Alternate Exploits/Installing boot9strap (safecerthax)|safecerthax]] was an exploit for original 3DS and original 3DS XL models that | *<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--> [https://github.com/TiniVi/safehax safehax] allowed the console to load a <code>.bin</code> payload after being loaded from Homebrew Launcher due to | *<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> | <translate> | ||
=== Redownloading system applications === <!--T:8--> | === Redownloading system applications === <!--T:8--> | ||
<!--T:9--> | <!--T:9--> | ||
Safe Mode reinstalls most deleted or corrupted system titles, | Safe Mode reinstalls most deleted or corrupted system titles, like a regular System Update, which can fix some related issues. | ||
=== Troubleshooting === <!--T:10--> | === Troubleshooting === <!--T:10--> | ||
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 [[<tvar name=1>3DS:ntrboot</tvar>|a flashcart compatible with ntrboot]] to fix the issue. | |||
</translate> | </translate> | ||
[[Category:Nintendo 3DS information{{#translation:}}]] | [[Category:Nintendo 3DS information{{#translation:}}]] | ||
Revision as of 02:22, 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
.binpayload 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.