Abuse filter editor, Bureaucrats, Check users, Interface administrators, Staff, Suppressors, Administrators, Translation Reviewer
1,994
edits
(Created page with "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. == Differences between EmuNAND and RedNAND == {{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 ma...") |
No edit summary |
||
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
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. | ||
== Moving EmuNAND/RedNAND to SysNAND == | |||
Follow [[3dsguide:move-emunand|Move EmuNAND on 3DS Hacks Guide]]. | |||
== Differences between EmuNAND and RedNAND == | == Differences between EmuNAND and RedNAND == |