Toggle search
Toggle menu
383
310
482
10,7 mil
Hacks Guide Wiki
Toggle preferences menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

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

From Hacks Guide Wiki
More actions
← Older edit
VisualWikitext
Aless (talk | contribs)
1,173 edits
// Translation //
Aless (talk | contribs)
1,173 edits
// Translation //
 
(13 intermediate revisions by the same user not shown)
Line 5: Line 5:
== Moviendo EmuNAND/RedNAND a la SysNAND ==
== Moviendo EmuNAND/RedNAND a la SysNAND ==


Sigue esta página [[3dsguide:move-emunand|Mover EmuNAND en 3DS Hacks Guide (página en inglés)]].
Sigue la página [[3dsguide:move-emunand|Mover EmuNAND en 3DS Hacks Guide (página en inglés)]].


<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Differences_between_EmuNAND_and_RedNAND"></span>
== Differences between EmuNAND and RedNAND ==
== Diferencias entre EmuNAND y RedNAND ==
</div>
{{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.]}}
<div lang="en" dir="ltr" class="mw-content-ltr">
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.
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.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
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).
RedNAND is an alternative type of NAND redirection that instead shifts all NAND reads and writes by one block when redirecting to the SD card. The advantage was that the RedNAND would only be as small as needed (~988 MiB for Old 3DS and ~1.2 GiB for New 3DS).
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Why_it_was_used_in_the_past"></span>
== Why it was used in the past ==
== Por qué se utilizaba en el pasado ==
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
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 [[3DS:menuhax|menuhax]].
Homebrew could originally only be launched by using an exploit within the 3DS firmware. Notable examples include DS Profile Settings in System Settings (also known as the "MSET exploit"), various game and Internet Browser exploits, and [[3DS:menuhax|menuhax]].
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
El problema con esta configuración es que Nintendo ha arreglado estas vulnerabilidades en actualizaciones. Nintendo requiere que la consola este actualizada para usar la eShop, y juegos nuevos también requerirían nuevas versiones del sistema.
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.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
Con EmuNAND y RedNAND, este problema podía ser evitado simplemente iniciando en una NAND alternativa que estaba actualizada, mientras se deja al sistema en un firmware viejo y vulnerable.
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.
</div>


<div lang="en" dir="ltr" class="mw-content-ltr">
<span id="Reasons_why_it&#039;s_no_longer_recommended"></span>
== Reasons why it's no longer recommended ==
== Razones por las que ya no se recomienda ==
</div>


<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.
* El redireccionamiento de la NAND no protegía ante los baneos, ya que los baneos rara vez eran motivo de preocupación. Históricamente, Nintendo no ha baneado a personas solo por usar homebrew/custom firmware.
</div>
* Ciertos softwares como TWiLight-Menu++ no funcionan del todo con EmuNAND o RedNAND.
* <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>
* Cambiar tarjetas SD es mas difícil con EmuNAND o RedNAND, ya que requieren formatear la nueva tarjeta SD específicamente para que sea compatible, y luego restaurar una copia de seguridad.
* <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>
* El redireccionamiento de la NAND no protege la memoria interna del sistema contra fallos debidos al uso. La cantidad de escrituras hechas a la memoria flash del sistema es relativamente muy pequeña la mayor parte del tiempo. Actualmente no hay casos reportados de fallos en la NAND de una 3DS debido a uso excesivo o prolongado.
* <span lang="en" dir="ltr" class="mw-content-ltr">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.</span>
* <span lang="en" dir="ltr" class="mw-content-ltr">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.</span>


[[Category:Nintendo 3DS information{{#translation:}}]]
[[Category:Nintendo 3DS information{{#translation:}}]]
Retrieved from "https://wiki.hacks.guide/wiki/3DS:EmuNAND_and_RedNAND/es"