Yes ok. I just saw both options were separate (ofw and another option for sysmmc), so I assumed ofw was for booting without anything at all, while sysmmc could have something if wanted.
In that case, i dont know how someone boots atmosphere with the sysmmc to prevent burning fuses.
{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}
[CFW (EMUMMC)]
emummcforce=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}
{--- Stock ---}
[Stock (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/icon_switch.bmp
{}
Let use this as example, so CFW( Sysnand) that is CFW on Sysnand, while Stock is without CFW on Sysnand, and Emummc is just the emulated emmc for emunand, you can use a custom bootloader to boot stock so it prevent fuse burn, if you boot sysnand without a custom bootloader it burn your fuse, as for updating via Nintendo server, if you let it finish updating and reboot without going to a custom bootloader the fuse get burned.
--------------------- MERGED ---------------------------
sysmmc, sysnand, emunand, emummc.... i'm confused because i don't know what these abbrevations mean.
sorry i don't want to make many spamposts, is there a wiki that explains these technical terms? i can read it myself.
is there no way to reset everything so nintendo can't detect anything or is not even worth trying?
Only if you have a clean NAND if you ran CFW on Sysnand which is the same NAND as your OFW.