15
edits
added a mention to safehax, exploit that used SAFE_FIRM after a normal boot to make use of firmlaunchhax after it got patched
(initial content) |
(added a mention to safehax, exploit that used SAFE_FIRM after a normal boot to make use of firmlaunchhax after it got patched) |
||
| Line 6: | Line 6: | ||
=== Exploits === | === 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 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. | |||
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). | |||
=== Redownloading system applications === | === Redownloading system applications === | ||