3DS:EmuNAND and RedNAND: Difference between revisions
From Hacks Guide Wiki
More actions
Marked this version for translation |
move translate tags to within the bullet points |
||
| (One intermediate revision by the same user not shown) | |||
| Line 35: | Line 35: | ||
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> | </translate> | ||
<translate><!--T:13--> | * <translate><!--T:13--> 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> | ||
<translate><!--T:14--> | * <translate><!--T:14--> Certain software such as TWiLight-Menu++ does not work at all with EmuNAND or RedNAND.</translate> | ||
<translate><!--T:15--> | * <translate><!--T:15--> 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> | ||
<translate><!--T:16--> | * <translate><!--T:16--> 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{{#translation:}}]] | ||