Question How to update Atm emuMMC and sysNAND?

If you want to have clean sysNAND, you can't update it without burning fuses. If you want to update without burning fuses, you need to run cfw on sysNAND

 

1. If you want to stay clean on sysNAND - yes
2. You need to have latest FW to Play online and you need to Burn fuses if you want to stay clean and use sysNAND to Play online.

 

Burned fuses doesn't matter for emummc as atmosphere ignores checking burned efuses.

 

You can do with emummc whatever you want. It's Independent from hardware security measures.

 

You cannot even boot a sysNAND without burning fuses without running CFW. Disabling fuse checks is a CFW feature.

You can load the fusee-primary payload directly rather than through Hekate. Then it will autoboot CFW but if you want to chainload other payloads, backup NAND etc, that still has to be done through Hekate.
Don't boot "OFW" through Hekate or any CFW if you want to keep your sysNAND clean. It still has patches applied to it so it's not 100% stock. Just boot your console normally if you want to use OFW, it's the only way.

 

If your sysNAND is updated through official means the fuses are already burned. If your sysNAND is updated through unofficial means that means you have booted CFW and the NAND is not clean. There is really no way around this.

 

Of course. It's the only way you can have your warez and also be able to play your legit games online.
I don't know why people are so worried about burning fuses. It really doesn't matter.

 

Huh?

 

Just boot, go online and update your SysNAND to the latest version normally (if atmosphere supports it) without the microSD, and hekate-boot your EmuMMC using the microSD.

 

Yeah, that's the easiest way by far.

Indeed.

 

To avoid a bit of confusion for others that reach this thread in the future, I feel it's important to point out that upgrading sysMMC either by official methods or via ChoiDujourNX, neither way actually burns any of fuses on the console...

BOOTING stock firmware is what burns the fuses. This is an important distinction, though it doesn't really seem like it at first. The reason being that while the N can determine the latest OS you should be on from update downloads, compared to what you are on, just by comparing their own logs, they don't (as far as anybody is aware) actually check for a fuse mismatch on the local console via the stock firmware at this point.

So, the big difference is that if you were to officially upgrade your stock sysMMC, but then ONLY continue to boot it via RCM with a mod chip or the like via the "stock" mode, you can have an "unmodified" system which matches exactly what Ninty expects you to be running from their remote logging. So long as you never boot Homebrew or load any CFW extensions, there shouldn't ever be anything unauthorized written to the debug logging to ever be reported.

Unless they release a new update to the consoles which actually does a local fuse comparison between what you have and what your firmware expects, and then reports that back to them instead of just using it to determine if you're bootable, and of course doing all that without the Atmosphere guys catching on and producing a new module which fakes the switch's fuse data to hide it when they support booting that updated version, you're effectively safe to run it as-is without burning fuses on your "stock" firmware.