Gateway doesn't have firm protection. Which means that a firmware update on sysNAND while in Gateway mode will either overwrite a9lh or brick. Luma doesn't have that problem, that's why everyone on Luma will tell you an emuNAND is useless.I thought I should post this here because it has to do with Gateway and I would really appreciate some help with this:
Hi guys, I could really use some help with a situation... I posted this part yesterday:
"Ok, I am worried...
I read in another thread that using Gateway can lose/erase A9LH. I followed the Palect guide to install A9LH and Luma, but later removed my EmuNAND because someone in another thread a while back said EmuNAND is no longer needed with a A9LH/Luma setup. I still use Gateway and I still have A9LH/Luma installed on my N3DS. I am also on FW 11.2 I think. Should I be worried/concerned about losing A9LH? Thoughts and help GREATLY appreciated..."
My question now is should I go ahead and create another EmuNAND to be safe? If yes, can someone please walk me through going about doing it? I removed previous EmuNAND because someone in another thread a while back said EmuNAND is no longer needed with a A9LH/Luma setup. Now, I hear it is recommended to do have an EmuNAND. Clarification and help greatly appreciated on all this
So your choice. If you're not careless, you can keep your sysNAND-only setup. If you really want to be safe though, an emuNAND would prevent these problems (a firmware update would only write to your emuNAND so your a9lh is safe).
If you decide to make one:
1) backup your SD card (the one in the 3DS, not the one in the red card) files on your PC
2) create an emuNAND using emuNAND9 (the menus should be self-explanatory, but be sure to choose "emuNAND" and not "redNAND")
3) copy your files back on your SD card
4) boot in Luma's config menu (hold SELECT at boot) and tell it to boot to emuNAND (so Gateway and Luma boot the same thing)
And yeah, your NANDs will be linked but that shouldn't be a problem with an a9lh setup, except if you play GBA VC games everyday (in which case you reboot to sysNAND when exiting and then when you're back to the emuNAND, all the software you installed since the creation of your emuNAND is in present packages).