I don't know if it's useful to have anymore, or if it even makes a difference. Are there any pros or cons to NOT moving my emuNAND?
Hacking Should I move my emuNAND?
- Thread starter skullkeeper94
- Start date
- Views 1,559
- Replies 8
You really should just move your emuNAND to your sysNAND.
Pros to moving : Saves space since your clears up the 1-2GB used by the emuNAND. Coupled with not needing to install your GBA/DSi games twice. Actually that's really the best reason right there.
Pros to keeping the emuNAND: Less stress on your system's NAND. Although that's not really relevant since it takes years of stress to cause issues. Otherwise it's really just a waste of space on your SD card.
Pros to moving : Saves space since your clears up the 1-2GB used by the emuNAND. Coupled with not needing to install your GBA/DSi games twice. Actually that's really the best reason right there.
Pros to keeping the emuNAND: Less stress on your system's NAND. Although that's not really relevant since it takes years of stress to cause issues. Otherwise it's really just a waste of space on your SD card.
Well, my question was useless. I thought one of the older CFW guides (Before it became 3ds.guide and had a zillion steps) made an emuNAND since you had to have "Autoboot emuNAND" enables. I seem to misunderstand things quite often
Thanks for the super fast response though!
Yeah, I still remember back in the day when in required crazy stuff like formatting the NAND twice and backing up everything twice. Those were dark days.Well, my question was useless. I thought one of the older CFW guides (Before it became 3ds.guide and had a zillion steps) made an emuNAND since you had to have "Autoboot emuNAND" enables. I seem to misunderstand things quite often
But a lot has changed and now it's basically, turn on 3DS, hack it, hacked.
Does using a tool like Hourglass9 or Decrypt9 latest .firm binaries work to restore an emuNAND copy to sysNAND? And if so, do they affect the bootrom or is that entirely separate from where B9S is?
I can look, but I've heard that the .firm payloads run before anything else, including the OS (or home menu? Something important). That shouldn't make a difference since you can flash backups without the system being ON with a hardmod :b
I've heard an argument that continued use of your system puts stress or degrades the NAND chip over time. Basically using the system on sysNAND puts wear and tear on the NAND chip.
Which is mostly true, but takes literal years of continued usage to show signs of damage.
