No, sysMMC is indeed when you turn off your Switch and boot normally. However if you boot normally, then you will not be able to dump it with a homebrew save manager unless you are willing to make another emuMMC which will contain the save data that you wish to carry over in sysMMC.
Yes because as I told you, you have 2 options. The second option is to launch a homebrew save manager on sysMMC to dump the save data so you can then restore it in emuMMC.
This would make updating a whole lot easier because I don't actually need ChoiDujour to avoid burning fuses, as long as AutoRCM is active?
I had been using Atmosphère on firmware 6.1.0. One day I connected my Switch to the Internet by accident and it downloaded an OS update. I was too lazy to delete the downloaded update and one day I clicked install by mistake.. :\
I've now got my Switch up and running again after throwing the latest Atmosphere on my SD card. My Switch is now 9.1.0, but what I don't understand: why does Hekate only show 5 burnt fuses?
I initially updated from 4.1.0 to 6.1.0 with ChoiDujour to avoid burning fuses. But since I installed the 9.1.0 update through the regular update function, shouldn't this have burnt my fuses? According to this I think I should have 12 burnt fuses?
Or are fuses only burnt when booting stock FW and not during the upgrade?
Usage of any CFW or homebrew can lead to a ban. This is a verified fact so you will not be safe from the hammer even if you only use Retroarch.
...Well, using only retroarch in offline emuMMC or using lakka/android/linux won't (like with 99.99% chance) get you banned.
Just make sure to keep your sysNAND clean. I think the best way for you would be using lakka or android on switch since it provides the best emulation experience but requires quite some reading and setting up stuff. The easiest way is to create emuNAND (basically a copy of your sysNAND but on your sd card) and use switch RetroArch from there. it has great compatibility except for gamecube/wii and some specific dc games maybe...
You don't need to be concerned if the serial number is unpatched but even I will admit that it is quite peculiar it doesn't match the sticker. After all, the sticker serial number isn't important because that can easily be falsified. The important one is the one you verified via the system settings. If you want further proof, you can always try sending a payload in RCM to verify that it is unpatched. You should at least do that before considering a return of the console.
@
Psionic Roshambo:
@
Julie_Pilgrim:
@
Sonic Angel Knight:
