Hacking Question Proper SysNAND and EmuNAND setup - AutoRCM contingency

[Danttebayo]

Hi all,

I'm sure this has been asked a bunch of times but I can't seem to find the answers in one place and the guides focus on getting EmuNAND up and running; not what I'm looking for.

For background, I have a launch Switch with a backed up clean firmware of 7.0.1. with an EmuNAND of 9.2.0 that is for emulators, etc. and stays offline.
The advice I keep seeing is for people to have a 'clean' SysNAND which they use to go online and such and a 'dirty' EmuNAND for homebrew. This leads me to two questions:

1) Have people been successfully using this setup? If one were to follow this advice, how would SysNAND be updated? If you update via the official Nintendo mechanism, does it turn off AutoRCM? If not, you 100% have to run AutoRCM at all times because even one regular boot to SysNAND will result in burnt fuses and you can never go back to an older version, correct?

2) Is it still true that there is no such thing as an EmuNAND that could be considered clean (maybe called EmuSysNAND for lack of a better term)? To me that would be the ultimate setup, kind of like in the old 3DS days. SysNAND is your ultimate failsafe that you never log into and normally you'd boot into your one EmuNAND for homebrew and the other for official online. Then if AutoRCM fails for some reason and it boots into your default SysNAND, no harm because it's offline anyway and you'd just fix AutoRCM and reboot.

3) Assuming the answers to question 1 are positive, would I be able to keep the same EmuNAND through this process or would I have to restore SysNAND, update it, then create an EmuNAND and continue from there? Or restore SysNAND and create an EmuNAND and update via ChoiDujourNX?


Thanks!

 

[Ribena]

1) You would update the clean sysnand through nintendo servers and this would remove autorcm and burn fuses on the reboot. If you have an unpatched console you can downgrade even with burned fuses (you probably don't want to downgrade anyway) I boot my sysnand by turning my console on normally and emunand by injecting a payload.

2) I think some ipatched users actually use an emunand to play online since they must keep their sysnand at a low fw to do the exploit. With an unpatched console I think you should just use your sysnand for online and an emunand for homebrew though.

3) you will keep the same emunand.

 

[Danttebayo]

1) You would update the clean sysnand through nintendo servers and this would remove autorcm and burn fuses on the reboot. If you have an unpatched console you can downgrade even with burned fuses (you probably don't want to downgrade anyway) I boot my sysnand by turning my console on normally and emunand by injecting a payload.

So basically it's currently not possible to have a SysNAND updated to the latest version via official means but without having the fuses burnt, correct?

As for the other answers, I dug around a bit and found this bug report from M4XW's GitHub page regarding stock EmuMMC which looks like it's still not possible:
https://github.com/m4xw/emuMMC/issues/7

I'm still holding out hope that someday someone will release an untethered hack for Switches 7.0.1 and earlier so I'll leave my setup as is until either that happens or we can run stock EmuMMC, assuming it means what I think it means in that it would allow a person to run an EmuMMC as the 'official' Nintendo firmware that allows for online, etc.

Thanks for answering my questions!