As I said, I thought emunand was when we see the firmware version beginning with GW, in my case GW9.4.0-2.0J. And when in sysnand, it does not show the GW, so I see 9.1.0-20J.
When I boot into gw mode, title manager and devmenu2x icon appear on home screen. When I dont boot into gw mode, none of these 2 icons are on home screen.
Plus the fact that on new 3ds LL, when I go to settings to see the firmware version and I go back to home screen, it quits gw mode and goes to sysnand (none of these 2 icons are on home screen).
Think of "Gateway Mode" as a wrapper around a system, rather than its own system. So, if you have EmuNand set up, you can run the following things:
SysNand on its own - When you start the system from a fully powered off state, this is what you are running.
EmuNand in Gateway Mode - This is what you are used to running, and what the Launcher will run by default.
SysNand in Gateway Mode - This runs the SysNand but with the ability to run installed CIAs with the signature checks disabled, as well as run 3DS games off the red card. Get to this by entering the launcher's menu (holding L when performing an exploit), then hold B when highlighting "BOOT GATEWAY MODE" (the text will change to "BOOT GATEWAY SYSNAND MODE") and press A while holding B.
EmuNand in Classic Mode - This lets you run the EmuNand, so you can run things requiring the newer system versions, but without the signature checks. So you can run retail cards and other things.
SysNand in Classic Mode - I haven't actually done this, so I don't know what the difference between this and SysNand on its own would be.
When starting out with a n3DS, your entry point into the launcher is using OoT/CN. The goal is to make an easier entry point that doesn't rely on one of these games. This is my understanding of the process so far (I don't have a n3DS, so I haven't tried this personally).
- Boot into SysNand in Gateway Mode, so anything you do is happening to SysNand. While you're in the launcher menu, you might as well install NVRAM (the altered DS profile used to enter the launcher). If you don't do it now, you'll just have to come back here again to do it later.
- Use devmenu.3ds on the Gateway card, or use bigbluemenu.3ds on the Gateway card to install a devmenu.cia file. Now you have access to DevMenu.
- Install mset.cia to alter your "System Settings" application, replacing it with a version that will enter the launcher when it sees the altered DS profile. Now you've unlocked the door from the inside, basically.
- While you're here, install bluecardfix.cia, which will allow you to use the Gateway Blue card in the future.
Now that you have this installed, you should be able to enter the launcher by going into System Settings > Profile > Nintendo DS Profile. (If you're still in Gateway Mode, this will likely crash, so it's best to reboot the system before trying this.) Now you have another entry point that you can use. If you run a DS game or DS flash cart (such as the Gateway Blue card), the NVRAM profile will likely be lost. To restore it, you will have to either enter the Launcher menu (through OoT/CN) and redo the "Install NVRAM" option, or use the Gateway Blue card and run GW_INSTALLER.NDS (thanks to installing bluecardfix.cia earlier). Both of those options write the altered profile to NVRAM, reopening that door.
I hope this makes things more clear, and if I did get anything wrong or left anything out, I'd be grateful for any corrections.