By running Atmosphere one time, you can update through the system settings without overwriting AutoRCM. This is unlikely to make the NAND dirty.
Yes, you can just restore your clean NAND backup to play Super Mario Maker 2 Online without any issues since you were using 90DNS to block all Nintendo traffic while using CFW/homebrew.
You do not have to burn fuses to play on the latest firmware however updating without burning fuses usually requires some type of CFW or homebrew running. Updating without burning fuses also requires AutoRCM but no one has been banned for only using AutoRCM or having a fuse mismatch. Regardless of how you update your firmware, you should restore your clean NAND dump before proceeding forward.
While updating without burning fuses usually requires some manner of CFW or homebrew, no one has been banned for having a mismatch of fuses or using AutoRCM (which is required for updating without burning fuses). There may have been people banned for using ChoiDujourNX to update their firmware but those bans could be due to those users updating to a firmware that was not available on a cartridge meaning they updated offline to a firmware not readily available.
You are correct that one should not use CFW on a clean NAND, and we define a clean NAND backup as one made before the use of CFW. However, using it one time to update without doing anything else is unlikely to dirty the NAND. As for logs, they should not be a problem if he's restoring a clean NAND backup beforehand.
The main point is to be able to play online with legitimately purchased games (if you have a clean NAND backup). It's not difficult to setup. You can move your games and saves to the emuNAND.
Installing Incognito to a dirty NAND makes it so it can't get the Switch banned.
Incognito is an applet/plugin thing to install? Pardon my noobness again, new to the whole Horizon/Atmosphere scene. And where do I get it from (if that's okay to say here)?
I know with retroarch you can, which is nice, if you're wanting emulation as well.
There is the homebrew application pPlay.
There is no way to check if a NAND is "clean" or not. But you can check how many fuses your console has burnt by using Hekate.
Fusee handles emuMMC slightly differently than Hekate in that it is managed by the emuMMC.ini file. If you do not have one, which I am assuming is the case, then Fusee booted CFW on your sysMMC. And there is no way to restore emuMMC to the sysMMC. You need to restore a clean NAND dump to revert the changes made to the sysMMC.
What I do is I boot into Hekate's Stock mode and download the system update online but I don't install it. Then I delete the Wi-Fi settings and reboot the console into CFW while making sure AutoRCM is enabled then install the system update. I have been doing this for months and have not been banned yet. The only safer way is riskier which you can try reading up on here.
No, you cannot burn fuses with emuNAND, since it has to be launched with a bootloader like Hekate or fusee-gulee.
Without AutoRCM, your Switch will coldboot into sysNAND when powered on, yes. If the sysNAND is so low that there's a fuse count mismatch, the Switch will refuse to boot unless you use a bootloader like Hekate or fusee-gulee. There is no reason for your sysNAND to be lower than its fuse count (5 fuses = 4.0.0-4.1.0). Anything lower than 4.0.0, and the Switch won't boot without Hekate/FG. Anything higher than 4.1.0, and you will burn fuses unless you use AutoRCM and a bootloader like Hekate/FG.
It is safe.
@
Psionic Roshambo:
@
Psionic Roshambo:
