Separate names with a comma.
Discussion in '3DS - Flashcards & Custom Firmwares' started by Suicuark, Mar 14, 2016.
All in the title.
Well, when you create an emuNAND, it is a 100% exact copy of your sysNAND. So pretty much everything going on in your sysNAND is unchanged in your emuNAND.
Yes but, while unlinking NAND's emunand data was formatted so...
What I would recommend is:
1.) Use EmuNAND9 to clone sysNAND to emuNAND.
2.) Boot a CFW into sysNAND mode, install TinyFormat here, and format sysNAND, effectively swapping what they are right now.
(OPTIONAL) 3.) Install arm9loaderhax so you never boot into sysNAND again, just emuNAND!
Well i don't understand, booting rxmode into sys then using tinyformat is something i've already done so why?
So you make a clone of the sysNAND, and then wipe the sysNAND and to unlink again.
You need booting into rxmode into sysNAND to run tinyformat on sysNAND. (sig patch)
You got it all backwards, you used tinyformat on emunand, wereas you should have used it in sysnand.
Clone your sysnand to emunand again, and use tinyformat on sysnand.
PS: Please correct me if the use of "wereas" was wrong. Still learning.
You used it correctly, I believe (I'm not exactly an expert), but pro tip: it should be spelled "whereas".
Thank you, i always forget about the "h".