3DS:Safe Mode: Difference between revisions

Line 5:

=== Exploits ===

The custom firmware method recommended for 11.16.0, [[~~3dsguide~~:~~installing-~~boot9strap-(~~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).

The custom firmware method recommended for 11.16.0, [[3DS:Alternate Exploits/Installing boot9strap (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).

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

@@ Line 5: / Line 5: @@
 === Exploits ===
-The custom firmware method recommended for 11.16.0, [[3dsguide:installing-boot9strap-(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).
+The custom firmware method recommended for 11.16.0, [[3DS:Alternate Exploits/Installing boot9strap (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).
 There are two other Safe Mode-based exploits that are now unusable: