3DS:EmuNAND y RedNAND
More actions
Históricamente, el custom firmware en la 3DS requería el uso de redireccionamiento de la NAND para poder utilizarse de forma segura, comúnmente denominado EmuNAND o RedNAND. Antes de 2016, no existía ningún método para iniciar directamente en el custom firmware.
Moviendo EmuNAND/RedNAND a la SysNAND
Sigue la página Mover EmuNAND en 3DS Hacks Guide (página en inglés).
Diferencias entre EmuNAND y RedNAND
 | This section is a work in progress. 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. Check GodMode9 issues. |
EmuNAND apareció por primera vez con Gateway-3DS. Todas las lecturas y escrituras de la NAND fueron redireccionadas a la tarjeta SD en las mismas posiciones, excepto por el primer bloque que fue puesto al final de la EmuNAND para hacer espacio para el encabezado del MBR. LA desventaja de esto es que las consolas con NANDs de grandes tamaños requerirían una EmuNAND de igual tamaño, con la mayor parte del espacio sin utilizar.
RedNAND es un tipo de redireccionamiento de NAND alternativo que en su lugar, desplaza todas las lecturas y escrituras de la NAND por un bloque cuando son redireccionadas a la tarjeta SD. La ventaja era que RedNAND solo ocuparía el espacio necesario (~988 MiB para la Old 3DS y ~1.2 GiB para la New 3DS).
Por qué se utilizaba en el pasado
Originalmente, el homebrew solo se podía iniciar usando un exploit en el firmware de la 3DS. Ejemplos notables incluyen la Configuración de perfil de DS en Configuración del sistema (también conocido como el "exploit MSET"), varios exploits de juegos y del Navegador de internet, y menuhax.
The problem with this setup is that Nintendo can and has fixed these vulnerabilities in updates. Nintendo requires that the console is updated to use the eShop, and newer games would also require newer system versions.
With EmuNAND and RedNAND, this problem could be worked around by instead booting into an alternative NAND that was up to date, while leaving the system on an older, vulnerable firmware.
Reasons why it's no longer recommended
With the advent of permanent boot-time methods such as arm9loaderhax and 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.
- 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.
- Certain software such as TWiLight-Menu++ does not work at all with EmuNAND or RedNAND.
- 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.
- 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.