There are tiny microscopic fuses in your console that are burned every few system updates or so. These are random and decided completely by Nintendo. What isn't random is that the console checks the current number of burnt fuses with the current firmware and the console will refuse to boot if they don't match. And these fuses are hardware, not software, meaning you would have to physically replace them in order to get around it. The alternative is to boot a custom bootloader that does not burn fuses and ignores the fuse check which involves using RCM.
If you already updated to 5.1, then you have already burnt the fuses so you have nothing else to worry about until Nintendo releases another system update that burns another fuse.Thanks!
What isn't random is that the console checks the current number of burnt fuses with the current firmware and the console will refuse to boot if they don't match.
So basically it's a safety check, like say, CRC? But if the console boots, there shouldn't be any problems with the hardware? I updated my console to 5.1.0 before trying out SX OS (Pro) version 1.3.
Then I found this topic: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/
Which kind of jump scared me, as it seems SX OS itself (atleast up until 1.2) seems to burn fuses and screw with the internals. Don't know about 1.3 though..
Could this perhaps be a cause of bans? If people have burnt some odd fuses because of SX OS, and the fuses themselves serves as security measures and aren't tied to the actual hardware booting up?
I guess update is the best thing for now if your switch is not a patched version...
Well, you can update without burning fuses to maintain a path for downgrading as well as obtaining the exFAT update offline via one or two tutorials.
Disadvantages to staying on lower firmwares include having to wait for current exploits to work on those firmwares. However, since we can update without burning fuses and maintain a path to downgrade, the advantages and disadvantages instead become how well you can follow the tutorials that detail such methods.
Rajkosto's guide is fully intended for updating without burning fuses. If you remove certain parts of the guide (i.e. AutoRCM), you can use it just as a way to update to any firmware you want. You have to follow his guide regardless as the only other way to apply updates is via DevMenu which will not work unless you're on 5.1.I don't think this forum needs another "should I update thread" so I apologize for the thread hijack in advance
I'm currently on 3.0.2 and hekate shows 4 burnt fuses.
I want to get to 4.1.0 as I believe I won't lose any exploits shown HERE
Updating to 4.1.0 will blow one more fuse taking me to 5 (LINK) - should I care?
I know there is a great guide by rajkosto but it looks a little intimidating to me. Is there a simple way to update to 4.1.0 if fuses are not an issue (without the "Kirby Star Allies" cartridge)? I do have the files for 4.1.0 update (lots of NCA files).
