new 3ds does not go to 2.1.0
This commit is contained in:
parent
efde018681
commit
262d137f83
1 changed files with 1 additions and 1 deletions
|
@ -6,7 +6,7 @@ permalink: /9.2.0-ctrtransfer.html
|
||||||
If you started on 2.1.0 **on Old 3DS**, this guide is for you.
|
If you started on 2.1.0 **on Old 3DS**, this guide is for you.
|
||||||
{: .notice--success}
|
{: .notice--success}
|
||||||
|
|
||||||
If you downgraded to 2.1.0 **on Old 3DS, 2DS, or New 3DS** but for some reason have **no functional NAND backups**, this guide is for you.
|
If you downgraded to 2.1.0 **on Old 3DS or 2DS** but for some reason have **no functional NAND backups**, this guide is for you.
|
||||||
{: .notice--success}
|
{: .notice--success}
|
||||||
|
|
||||||
If you have already hacked your 3DS before and have a EmuNAND based CFW setup, this guide deals exclusively with SysNAND and you should follow all instructions from within or applying to SysNAND. Note that the terms EmuNAND and RedNAND refer to slightly different implementations of [the same concept](http://3dbrew.org/wiki/NAND_Redirection).
|
If you have already hacked your 3DS before and have a EmuNAND based CFW setup, this guide deals exclusively with SysNAND and you should follow all instructions from within or applying to SysNAND. Note that the terms EmuNAND and RedNAND refer to slightly different implementations of [the same concept](http://3dbrew.org/wiki/NAND_Redirection).
|
||||||
|
|
Loading…
Reference in a new issue