Is there any reason for me to care about burning fuses?

[bribri]

With SX OS 2.3 adding the ability to store emuNAND data on the SD card, it means that I can leave my Switch's sysNAND in a nearly unmodified state. Because of that I'm considering running off of my sysNAND with original firmware, going online with it, and updating it the normal way. I will run custom firmware exclusively on emuNAND and keep it offline.


That of course will burn some fuses on my Switch. But I don't think I care. I can't think of any reason I'd want to downgrade the firmware on my sysNAND since the fusée gelée exploit will always work, and the number of burned fuses doesn't matter when you're loading custom firmware from the SX Pro anyway.

If I did this, I would make a new full backup of my sysNAND after successfully updating its firmware since I know that restoring my old sysNAND backup wouldn't work given that fuses will have been burned. Further, even though I want to try going online I don't particularly care if my Switch gets banned, so no need to warn me about that.


So given all that, is there any reason to avoid burning fuses that I may be unaware of?

 

[Superxeno]

It think if you always keep OFW and CFW both on the same version you dont rly have to worry about your fuses.I would only worrry if my OFW is a higher version than my cfw.That will cause issues i think.

 

[Fenny]

There is an exploit chain that devs are holding on to that would remove the need for RCM boot. It would be a persistent CFW. If you update, you may not be able to use that if/when it is released.

 

[Superxeno]

I think they can only appply to the new consoles tbh..I honestly think afterr 2019 nintendo is just gonna disband the hackable switches and focus on the newer ones..Its just because of the xmas hollydays now.

 

[bribri]

I would only worrry if my OFW is a higher version than my cfw.That will cause issues i think.

How so? I thought booting custom firmware from the SX Pro disabled the fuse check... is there something else that can cause issues?

There is an exploit chain that devs are holding on to that would remove the need for RCM boot. It would be a persistent CFW. If you update, you may not be able to use that if/when it is released.

I do like having options open to me, but I'd also be happy continuing to use the SX Pro going into the future. I really like being able to boot CFW on emunand so that it's totally separate from sysnand and so that the sysnand is untouched

 

[imprezgc8]

How so? I thought booting custom firmware from the SX Pro disabled the fuse check... is there something else that can cause issues?

Having a higher OFW than CFW can cause you to issue I believe if you burn the fuses and have to do a restore. I may also just being confusing the issues with people who have updated to 6.2 recently, burned their fuses and then tried to restore a lower sysnand. In any case there's really not a reason to have a higher OFW than CFW. Ideally you would have a lower OFW and higher CFW.

 

[ContainedBio]

The only real downside to having more burnt fuses on cfw, is that there's a fuse check on warmboot.
In short, you won't be able to boot older official firmware versions, and sleep mode won't work (Crashes system) on any firmware lower than your latest update in cfw.
Basically, OP is fine as long as they don't care about using sleep mode in cfw.

 

[bribri]

The only real downside to having more burnt fuses on cfw, is that there's a fuse check on warmboot.
In short, you won't be able to boot older official firmware versions, and sleep mode won't work (Crashes system) on any firmware lower than your latest update in cfw.
Basically, OP is fine as long as they don't care about using sleep mode in cfw.

Okay, this issue with sleep mode might be a reason to be careful about this. I've heard lots of people talking about sleep mode issues but I've never had it explained to me. So far it hasn't been an issue on my Switch.

But from what I gather, if my Switch has burned more fuses than what matches the CFW I'm running, then sleep mode will not work when running CFW. Instead it will crash my Switch. Is that correct?

 

[Hackerjac]

Okay, this issue with sleep mode might be a reason to be careful about this. I've heard lots of people talking about sleep mode issues but I've never had it explained to me. So far it hasn't been an issue on my Switch.

But from what I gather, if my Switch has burned more fuses than what matches the CFW I'm running, then sleep mode will not work when running CFW. Instead it will crash my Switch. Is that correct?

Yes and no, depend on what OFW you have, the sleep problem is something that was introduced in 6.2.0