3DS:Safe Mode: Difference between revisions

3DS:Safe Mode (view source)

Revision as of 23:08, 18 October 2022

180 bytes added , 2 years ago

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

StarlitSkies

Approver, confirmaccount

398

edits

@@ 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 ==
 === 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.