3DS:EmuNAND and RedNAND/es: Difference between revisions

Line 26:

== Razones por las que ya no se recomienda ==

~~<div lang="en" dir="ltr" class="mw-content-ltr">~~

Con la llegada de métodos permanentes de arranque como [[3DS:arm9loaderhax|arm9loaderhax]] y [[3DS:boot9strap|boot9strap]], el uso de custom firmware exclusivamente en la memoria interna del sistema (también conocida como "SysNAND") se volvió mas seguro. La necesidad de redireccionar la NAND disminuyó y pronto dejó de recomendarse para nuevas configuraciones.

~~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~~.

~~</div>~~

* <span lang="en" dir="ltr" class="mw-content-ltr">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.</span>

* <span lang="en" dir="ltr" class="mw-content-ltr">Certain software such as TWiLight-Menu++ does not work at all with EmuNAND or RedNAND.</span>