Ho ho ho!
2 sdcards, 1 for sysNAND and 1 for emuNAND.
However that is not needed anymore thanks to the amazing Team-Xecuter team!
You can now have an emuNAND that makes a partition on your SD-card!
Wahoo!
They could easily recognize the emuNAND header on the SD card if they really wanted to.
I’m new to the scene and to the Nintendo Switch in general - I just got my console last week (a launch model that took almost two years to be delivered), and now I’m waiting for my SX Pro to arrive.
Because of that, I’ve been trying to educate myself as much as I can in these last few days, so I don’t mess up when I can finally “hack” the device.
SysNAND and EmuNAND are two concepts that still confuse me. I’m still not sure at what point should I update my Switch (as to not burn any eFuses) and minimize the risk of detection.
This is what I got, so far:
1. Start the device in RCM;
2. Inject a payload (Hekate) via USB while in RCM;
3. Backup the SysNAND using Hekate (preferrable over SX’s alternative), as it’s done before even booting up the console;
4? Update the firmware to the latest version without burning eFuses using ChoiDuJour (not NX), so it can be done while still in RCM and before even loading a CFW (somehow minimizing the risk of detection, according to some users);
OR
4? Load SX OS after backing up the SysNAND, but before updating the console (I’m on 1.0.0), create an EmuNAND and THEN update the EmuNAND’s firmware to the latest version (how, exactly, I’m not sure).
What’s the difference between updating the firmware via ChoiDuJour in RCM (before even loading a CFW for the first time) and doing that via ChoiDuJourNX after creating an EmuNAND in SX OS?
I’d like to go with the safest option, even if it’s not the most practical. Also, regardless of the method, I should NEVER boot into the OFW (Horizon) while not in RCM, or the eFuses WILL be burned, correct?
I want to keep the SysNAND at 1.0.0 until there’s a boot option that doesn’t require a jig or at least the injection of a payload via USB.