3DS:Safe Mode/fr: Difference between revisions

(3 intermediate revisions by 2 users not shown)

Line 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''' (Mode sans échec), aussi appelé '''SAFE_FIRM''', est un composant du firmware d'usine de la 3DS qui permet à l'appareil d'effectuer une mise à jour du système sans charger le menu HOME ni la plupart des fonctions du système. Pour accéder au Safe Mode, maintenez {{B|L}} + {{B|R}} + {{B|(D-Pad Up)}} + {{B|A}} puis démarrez. Si ça a fonctionné, la 3DS affichera l'écran de Mise à jour du système.<br>

~~There is no alternate keycombo~~, ~~so if one of the needed buttons is broken~~, ~~you will be unable to access~~ Safe Mode.

Il n'y a pas de combinaisons de touches alternatives, donc si l'un des boutons nécessaires ne fonctionne pas, vous ne pourrez pas accéder au Safe Mode.

</div>

<~~div lang~~="~~en" dir="ltr" class="mw-content-ltr~~">

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

== Son utilité ==

~~</div>~~

~~<div lang="en" dir="ltr" class="mw-content-ltr">~~

=== Exploits ===

~~</div>~~

~~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).

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.

</div>

Line 20:

Line 17:

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

</div>

<span lang="en" dir="ltr" class="mw-content-ltr">* [[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~~.</span>

*<span lang="en" dir="ltr" class="mw-content-ltr">[[3DS:Alternate Exploits/Installing boot9strap (safecerthax)|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.</span>

<span lang="en" dir="ltr" class="mw-content-ltr">* [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.</span>

*<span lang="en" dir="ltr" class="mw-content-ltr">[https://github.com/TiniVi/safehax 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.</span>

=== Redownloading system applications ===

Line 27:

Line 24:

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, like a regular System Update, which can fix some related issues.

</div>

Line 35:

Line 32:

~~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.

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.

</div>

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 [[3DS:ntrboot|a flashcart compatible with ntrboot]] to fix the issue.

</div>

[[Category:Nintendo 3DS information{{#translation:}}]]