I am new to the 3DS scene. The last thing I messed with was on a DS lite and that was just using a cycloDS Evolution flashcart. That being said, I've fumbled through forums and did searches and ended up using Plailect's guide. That thing is top notch. This was my final result using the guide
https://plailect.github.io/Guide/installing-arm9loaderhax
I had an o3DS on 7.1 firmware before the install and used the Decypt9 Browser option in the guide to start out. Ive seen a lot about sysNand and EmuNand. Based on how i understood the guide, I am not running an EmuNand. It says I am running a CFW based SysNand. Im not entirely sure what that means.
Before you were running custom firmware (or a CFW) on emuNAND. That had many annoying issues. So now, the CFW runs on the systemNAND itself! I put CFW on my PSP back when that was a thing and updating through system settings was a bad thing and broke your CFW.
This does not seem to be the case with 3DS, because at the end of the guide it tells you to do a system update, so I am now on 11.2. Im just trying to wrap my head around all this and had a few questions. Mainly, what in the world do they mean by CFW based sysnand?
Let's try to explain further. SystemNAND refers to 3DS reading from its own memory (they use NAND, or Not AND. Named because they only use Not and AND gates. No OR gates) versus reading from emuNAND/redNAND, which redirected the system to read the SD card. When you had the emuNAND setup, you had to keep your systemNAND on 9.2. This was the last version to have the proper exploits. Your emuNAND was able to be updated as much as you wanted to. Well, that is a whole messy setup. You have two possible environments to boot from, and people very commonly updated the wrong environment. Now, we are able to run custom firmware at boot, prior to the system software loading. This allows us to essentially override aspects of the system software, such as only allowing legit content to be installed. You no longer have to install GBA/DSi titles to both sys and emu nand. You can always update your system software without fear that the hack will disappear. And always being able to update your system means you can always have eShop and online access.
1. Seeing as I have Luma installed along with hourglass9, Decrypt9 and arma9loaderhax, could I simply downgrade my sysnand firmware by restoring my orginal nand backup using hourglass9 or decrypt9? Seeing as I already have exploits in place this seems like it would work that way. I ask because all I can find about downgrading is on systems that are not yet on CFW. If not, am I restricted to downgrading the same way an unmodded console would be?
Sure, just make sure to use the option that says to Keep A9LH. I would recommend you not do this though, unless there is a specific hack that does not work with the new setup. Chances are your old exploits are no longer needed.
2. I want to set up the 3DS as a new system but didn't want to lose my CFW, if I did I'd be stuck on 11.2 with hardmod as my only option for downgrading, and that is just not my forte. I've seen posts about tinyformat and that it doesn't mess with your CFW. Is this a safe option? How should I proceed?
You cannot remove A9LH unless you specifically uninstall it via a program like SafeA9LHInstaller. As long as A9LH is in place, you cannot lose CFW access. Just put the arm9loaderhax.bin on the SD card and it'll load. In fact, it shouldn't load if that file isn't there. If you had a system on 11.2, you can DSiWareHax downgrade, as long as you had a second system that already had CFW. Anyways, if you want to reformat, just run TinyFormat. Go through setup, run TinyFormat again. Done.
3. If using tinyformat, I assume all my homebrew that I installed as cia will be deleted and I will have to inject FBI back into the health and safety app to reinstall them. Is this correct?
Yes. That is, unless FBI is still injected into H&S app. Then it will remain that way between the formats.
4. Should I be using an Emunand at all? It seems like if it was critical in any way, Plailect's guide would have you set one up. If you have a backup of your sysnand and you restore in case something went wrong, what would be the point of an Emunand? I assume it's used as a precautionary device to protect your sysNand from bricking or updating, but it seems that updating doesn't have any consequences and if you brick you could just restore your sysnand backup. So what is the purpose of it?
Again, no. EmuNAND is no longer needed/used, unless you have a very specific hack that no longer works with the new environment. Then what I would recommend is to keep your sysnand updated, and keep a 9.2 emunand for when you need to use that hack. Otherwise, keep with updated sysnand. As you pointed out, there is no longer a need/point for emunand since we can restore NAND images now. EmuNAND was the first method of installing non-legit content onto your system. It only become obsolete last year.
5. If I use hourglass9 to convert my ehsop titles to cia and go to reinstall them with FBI (after setting up my 3ds as a new console in my second question) will they reinstall them same way they did when I downloaded them from the eshop or would it try to install the entire title to my sysNand instead of my SD card. I would just like to be able to backup my eshop titles and reinstall them without having to go through the process of downloading them all over again. I've seen a drawn out process that involves a certain key that shall not be named, but don't know if this is outdated.
You do not seem to have an understanding of where titles get installed to. When you download from the eShop, the system installs to your SD card, not your internal NAND. However, yes, I believe you would be fine converting them to CIA and then reinstalling on the new system. I do not think saves would be backed up with this process. To backup saves that are not on your SD card, use JK's Save Manager (https://github.com/J-D-K/JKSM/releases) to backup to SD card. As for keys, you should have the aeskeydb.bin under SD:/files9. Those are the keys they talk about. Before this nice and neat file, we had to put each slot key in its own file on the root of the SD card. aeskeydb.bin takes care of that now.
I'm sorry if I've asked anything already asked (I'm sure I have). I know how it is to see the same questions asked over and over. I've been in the modding scene since 2004 and modded various game consoles and phones since then and I rarely ask questions on forums. You know how it is, if you come to the scene a few years late, there is a lot of dated material you have to sift through to find what is current and what had been outdated. I'm just looking for a little help sorting some things out and getting frustrated with the information I've gathered on my own.
I appreciate any insight anyone can offer.