I'm already banned and don't use emunand as you know, so I just backup my Nand, Boot0/1 each time I update, so If my Nand gets corrupted I can fall back on it. But will be different in your case, trying to preserve the fuse count, and running emunand. If you always use daybreak to update, you should never burn fuses, so fuse count will be same as day one. You can always verify this in hekate menu also, check burned fuse count.
Actually as long as your console is unpatched, you can load whatever firmware you want so fuses are irrelevant for that. However if you want to keep your console as clean as possible, then I suppose it may be ideal to have a backup that matches your fuse count.Well, i can update to any new firmware and incase of emergency I can load the backup of old firmware so i guess i should keep the autorcm on for that, right? The switch was almost on the newest firmware when I got it so I didn't have much to lose. The fuses are burnt if I ever decide to revert the autorcm off? I got a pretty good deal when I bought my switch, got it only for 150€. In good condition, the screen had protector on it.
Yes, you hit the nail right on the head.
As I stated to Dethil, fuses are irrelevant when it comes to restoring backups as long as the console isn't patched because the exploit bypasses the fuse check. So when it comes to updating your firmware, the only difference is if you want to preserve fuses or not. Preferably, homebrew apps are best to update without burning fuses while updating online keeps your console free of homebrew at the cost of burning fuses. Personally, I try to mix the best of both worlds by downloading system updates in OFW then installing them in CFW offline.
Well to be more precise in my case, I just haven't found a reason to update emuMMC yet. 10.2 gets you a lot farther than most people give it credit for.
Everything can be patched. Its just a matter of whether or not it will work.
Applet mode refers to as the name implies applets. Album for example is an applet hence why launching the homebrew menu from there would give you the warning screen "Applet Mode". Games however are not considered applets. If they were, they would definitely have trouble running as for some reason, the Switch limits the RAM to applets. Therefore when launching the homebrew menu after installing it as an .NSP file, much like any other Switch game, it will not display the "Applet Mode" message.
Not that I'm aware of since there is no software that ties the battery to the hardware.
Did you check to see if the SD card is fake or not? If you have't, you can use FakeFlashTest to test the validity of your card.
I see where the confusion lies. The guide misuses the term "NNID" which is, as you said, only for the Wii U and 3DS. The Switch uses the Nintendo Account system which I can assure you is different than your NNID despite how similar they sound. If I had a GitHub account, I would either open an issue or submit a PR to clarify the wording. Either way, I would still recommend linking an account as certain games will not work without one. One account is sufficient for an entire household provided you're willing to share it with your family.
