3DS:EmuNAND and RedNAND: Difference between revisions
From Hacks Guide Wiki
More actions
No edit summary |
translate tags |
||
| Line 1: | Line 1: | ||
<languages/> | |||
<translate> | |||
Historically, 3DS custom firmware required the use of NAND redirection to be safely used, commonly called EmuNAND or RedNAND. Before 2016, there was no method to boot directly into custom firmware. | Historically, 3DS custom firmware required the use of NAND redirection to be safely used, commonly called EmuNAND or RedNAND. Before 2016, there was no method to boot directly into custom firmware. | ||
| Line 6: | Line 8: | ||
== Differences between EmuNAND and RedNAND == | == Differences between EmuNAND and RedNAND == | ||
</translate> | |||
{{Section WIP|notes=When did RedNAND first appear? When did it start to be recommended over EmuNAND? I think this was when Old 2DSes started being produced with 1.8 GiB NANDs but there were issues accessing data past the 1 GiB mark. [https://github.com/d0k3/GodMode9/issues Check GodMode9 issues.]}} | {{Section WIP|notes=When did RedNAND first appear? When did it start to be recommended over EmuNAND? I think this was when Old 2DSes started being produced with 1.8 GiB NANDs but there were issues accessing data past the 1 GiB mark. [https://github.com/d0k3/GodMode9/issues Check GodMode9 issues.]}} | ||
<translate> | |||
EmuNAND first appeared with [[Gateway-3DS]]. All NAND reads and writes were redirected to the SD card at the same positions, except for the first block which was placed at the end of the EmuNAND to make space for the MBR header. The disadvantage of this was that consoles with large NAND sizes would require an equally large EmuNAND, with most of the space being unused. | EmuNAND first appeared with [[Gateway-3DS]]. All NAND reads and writes were redirected to the SD card at the same positions, except for the first block which was placed at the end of the EmuNAND to make space for the MBR header. The disadvantage of this was that consoles with large NAND sizes would require an equally large EmuNAND, with most of the space being unused. | ||
| Line 24: | Line 26: | ||
With the advent of permanent boot-time methods such as [[3DS:arm9loaderhax|arm9loaderhax]] and [[3DS:boot9strap|boot9strap]], the use of custom firmware purely on the internal system memory (also known as "SysNAND") became safer to use. The need for NAND redirection declined and soon it was unrecommended for new setups. | With the advent of permanent boot-time methods such as [[3DS:arm9loaderhax|arm9loaderhax]] and [[3DS:boot9strap|boot9strap]], the use of custom firmware purely on the internal system memory (also known as "SysNAND") became safer to use. The need for NAND redirection declined and soon it was unrecommended for new setups. | ||
</translate> | |||
* NAND redirection did not protect against bans, because bans were rarely a concern. Nintendo has historically not banned people just for using homebrew/custom firmware online. | <translate>* NAND redirection did not protect against bans, because bans were rarely a concern. Nintendo has historically not banned people just for using homebrew/custom firmware online.</translate> | ||
* Certain software such as TWiLight-Menu++ does not work at all with EmuNAND or RedNAND. | <translate>* Certain software such as TWiLight-Menu++ does not work at all with EmuNAND or RedNAND.</translate> | ||
* Switching SD cards is more difficult with EmuNAND or RedNAND, as it requires formatting the new SD card specifically to support it, then restoring a backup. | <translate>* Switching SD cards is more difficult with EmuNAND or RedNAND, as it requires formatting the new SD card specifically to support it, then restoring a backup.</translate> | ||
* NAND redirection does not protect the internal storage from failing due to use. The amount of writing done to the system's flash memory is relatively very small most of the time. There are currently no reported cases of a 3DS's NAND chip failing due to excessive or long-term use. | <translate>* NAND redirection does not protect the internal storage from failing due to use. The amount of writing done to the system's flash memory is relatively very small most of the time. There are currently no reported cases of a 3DS's NAND chip failing due to excessive or long-term use.</translate> | ||
[[Category:Nintendo 3DS information]] | [[Category:Nintendo 3DS information]] | ||