I have an issue with the hekate nyx / Kosmos configuration.
So I was on ReiNX and OFW 5.1 for a long time unbanned and I figured to start using emuMMC so I can start playing the new games like Fire Emblem. I restored my NAND backup 5.1 to go back to my pre-CFW state, then used a new bigger mSD to make a partition for emuMMC and placed the Kosmos files into it.
So emuMMC was setup properly, and I enabled it.
Now, emuMMC is (5.1 AMS 0.9.2) and i wanted to update it to 8.1.0.
I booted to emuMMC via Payloads > fusee-gelee.bin. It booted up with the Atmosphere (only) logo and I renamed my device "CFW" from the System Settings, then I used ChoidujourNX to update that partition to (8.1.0 AMS 0.9.2).
This of course activated AutoRCM.
I used emuMMC-toggler.nro to "deactivate emuMMC" which I thought would automatically let me boot into OFW.
I ran reboot-to-payload and turn off device from hekate.
I try to boot the Switch normally, and it won't boot (autorcm is still active).
Fine, I tried checking the fuses burnt using briccmii, and i see 6 fuses.
So I boot into hekate again and manually turned off AutoRCM then tried the Launch > Stock SysNAND option.
Now here's my confusion. What are "CFW SysNAND", "CFW EmuMMC" and "Stock SysNAND" in the launch options? The Stock SysNAND option boots and shows the Atmosphere SEPT and Kosmos screens, then boots into the OFW Horizon, but now in 8.1.0....
And my fuses have been burnt (9 fuses). Fine it was my mistake, can't go back to 5.1 anymore. I of course backed up a "stock" 8.1.0 NAND again.
When Stock SysNAND boots with the Atmosphere SEPT and Kosmos screens, is it considered not clean anymore as well? I can't back this NAND up for clean restoration in the future anymore? I stopped at that point. I haven't gone online but I will probably be banned soon.
Thanks