3DS: Modo Seguro
More actions
Modo Seguro, también conocido como SAFE_FIRM, es una parte del firmware de fábrica que permite al dispositivo realizar una Actualización del Sistema sin cargar el Menú HOME o la mayoría de las funciones del sistema. Para acceder al Modo Seguro, mantén L + R + (D-Pad Arriba) + A y después enciende la consola - si todo sale bien, la 3DS mostrará la pantalla de Actualización del Sistema.
No hay una combinación de botones alternativa, así que si alguno de los botones esta dañado, no podrás acceder al Modo Seguro.
Por qué es útil
Exploits
El método recomendado para instalar custom firmware para la versión 11.16.0, unSAFE_MODE, se aprovecha de un fallo en la Configuración de Internet del Modo Seguro que puede ser usado para instalar custom firmware. Esto se debe a que Nintendo es mas reacia para actualizar el Modo Seguro para parchear exploits (ya que una 3DS sin modificar no tendría manera de arreglar un brick realizando una actualización del sistema si SAFE_FIRM estuviera brickeado también)
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 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.
* safehax allowed the console to load a .bin 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
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 a flashcart compatible with ntrboot to fix the issue.