|
|
| (8 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| Removing custom firmware (CFW) from a 3DS is not recommended for most cases.
| | Moved here: https://wiki.hacks.guide/wiki/3DS:Why_not_to_remove_custom_firmware |
| | |
| == Fixing a broken game ==
| |
| Nearly all cases where a game doesn't work is not due to CFW alone. Most commonly, a corrupt game file or a corrupt save file. Removing CFW would it harder to diagnose the problems with a game. What Luma3DS does is expose more details about why a game doesn't work, allowing for more experienced people to figure it out, while stock would only show a generic "An error has occurred" screen.
| |
| | |
| Another possible case is due to a plugin or mod that is outdated or for the wrong version of the game. In this case, removing the plugin or mod would fix the game.
| |
| | |
| There are a few edge cases where games can break due to CFW settings. In particular, a few games crash on New 3DS if 804MHz and L2 cache are enabled. Usually these can be worked around by temporarily disabling the setting that is breaking the game.
| |
| | |
| == Fixing broken system applications ==
| |
| Sometimes a built-in part of the firmware might stop working for some reason. Assuming the system was not updated to a point where Luma3DS is currently not compatible, keeping CFW would mean you can fix the corruption, usually with a CTRTransfer. Removing CFW will probably keep the system in a broken state with no way to fix it without ntrboot.
| |
| | |
| == Concerns about bricks ==
| |
| CFW has become exceptionally safe to use on the 3DS over the years, both during and after setup. It is nearly impossible to brick on accident. GodMode9, the most common tool for interacting with the 3DS NAND, requires unlocking writing with a button combination when you are about to do something that could cause damage. The button combination requires deliberate inputs and is impossible to do by accident. (add something about corruption checks)
| |
| | |
| If Nintendo ever releases a new system update, there is a chance that Luma3DS will be incompatible with it. This is generally not regarded as a brick as it only breaks Luma3DS trying to boot into the firmware, it does not break running other tools such as GodMode9. Usually this is fixed in about a day and is fixed by replacing {{code|boot.firm}} on the SD card.
| |
| | |
| == Concerns about data loss ==
| |
| Like mentioned in the past section, CFW has very few risks associated with it, either when setting it up or using it. If you don't delete random files or titles using GodMode9, FBI, or similar tools, you are not likely to lose things such as game saves on the SD card.
| |
| | |
| CFW provides access to tools to make your own backups of your games, their saves, and the system's internal storage (aka NAND). These allow for better backups than what Nintendo normally allows. For example if your console is ever lost or broken, everything can be manually migrated to a replacement console. SD card data can be migrated if you have {{Code|movable.sed}} from the original console, which is inside {{Code|essential.exefs}} made during setup. NAND data (e.g. Friend List, Mii Maker, StreetPass Mii Plaza) can be transferred from a NAND backup.
| |
| | |
| == Concerns about bans ==
| |
| | |
| == Selling console ==
| |
| | |
| [[Category:Nintendo 3DS]]
| |
