Hacking Question about burning fuses

  • Thread starter Thread starter mugendc4
  • Start date Start date
  • Views Views 60,652
  • Replies Replies 40

mugendc4

Well-Known Member
Newcomer
Joined
Nov 6, 2007
Messages
49
Reaction score
5
Trophies
1
XP
556
Country
United States
Sorry for noob question but can someone clarify about the burning fuses situation. To my understand, the switch has a certain amount of fuses which can be upgrade and downgrade so many times before all fuses burn out unless following this guide which is a bit intimidating (https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/)

I'm currently on 4.1 and will get my SX OS Pro soon but I've read previous SX OS 1.1 used to burn fuses but SX OS 1.2 fix the issues. Does fuses get burnt everytime booting into CFW?
 
The Nintendo Switch's bootloader aka the part that controls the boot-up process for the console checks the number of fuses burnt and compares it to the current firmware. If they do not match, it will either prevent the console from turning on or it will burn them to compensate. While both Hekate and SX OS V1.2+ not only bypass the fuse check entirely as substitute bootloaders but also prevent fuses from being burnt, this is not enough protection against burning fuses during system updates. The reason for this is because when you update the Switch normally, it reboots the console so the Switch has a chance to burn fuses. Even if you initially boot the console with either Hekate or SX OS V1.2+, when you update normally within the Switch, the Switch's bootloader will take over when the console is rebooting after the update. Therefore, the guide not only has you install AutoRCM as a means to prevent you from accidentally booting the Switch normally which will burn fuses, but also has you install the update entirely offline. It should also be worth noting that updating removes any and all forms of AutoRCM which the guide has a section on how to recover it to prevent your Switch from trying to burn fuses.

In theory, you can update without following the tutorial and instead using the official way while not burning fuses IF you can stop the console from turning back on after it updates successfully. This is a very user-oriented window that if you miss will permanently burn the fuses and is a risk you can take should you acknowledge it. Another problem is that once you do manage to turn off the console with the correct timing, you have to ensure from that moment onwards that you will boot your console from RCM only because it will burn the fuses if you turn it on normally. This means you must have some means of inducing RCM with 100% confidence or you risk burning your fuses. AutoRCM cannot save you in this case as it will be removed during the system update and can only be re-installed via RCM.

Lastly, while the guide is rather lengthy, it is nearly 100% noob-proof and will prevent you from burning any fuses. It also details each and every step in such a way that anybody can follow it, even if they have no hacking experience whatsoever.
 
Last edited by Draxzelex,
The Nintendo Switch's bootloader aka the part that controls the boot-up process for the console checks the number of fuses burnt and compares it to the current firmware. If they do not match, it will either prevent the console from turning on or it will burn them to compensate. While both Hekate and SX OS V1.2+ not only bypass the fuse check entirely as substitute bootloaders but also prevent fuses from being burnt, this is not enough protection against burning fuses during system updates. The reason for this is because when you update the Switch normally, it reboots the console so the Switch has a chance to burn fuses. Even if you initially boot the console with either Hekate or SX OS V1.2+, when you update normally within the Switch, the Switch's bootloader will take over when the console is rebooting after the update. Therefore, the guide not only has you install AutoRCM as a means to prevent you from accidentally booting the Switch normally which will burn fuses, but also has you install the update entirely offline. It should also be worth noting that updating removes any and all forms of AutoRCM which the guide has a section on how to recover it to prevent your Switch from trying to burn fuses.

In theory, you can update without following the tutorial and instead using the official way while not burning fuses IF you can stop the console from turning back on after it updates successfully. This is a very user-oriented window that if you miss will permanently burn the fuses and is a risk you can take should you acknowledge it. Another problem is that once you do manage to turn off the console with the correct timing, you have to ensure from that moment onwards that you will boot your console from RCM only because it will burn the fuses if you turn it on normally. This means you must have some means of inducing RCM with 100% confidence or you risk burning your fuses. AutoRCM cannot save you in this case as it will be removed during the system update and can only be re-installed via RCM.

Lastly, while the guide is rather lengthy, it is nearly 100% noob-proof and will prevent you from burning any fuses. It also details each and every step in such a way that anybody can follow it, even if they have no hacking experience whatsoever.

So is it better for the OP do an official system update to 5.1 before using SX (1.4?) for the first time?
 
So is it better for the OP do an official system update to 5.1 before using SX (1.4?) for the first time?
If you mean in regards to being banned, I would say so but then his fuses would be burnt meaning he would no longer be able to downgrade. You cannot easily update without burning fuses while avoid being banned. Either you follow the long (but simple) tutorial on how to update without burning fuses which avoids connecting online or you use a jig with a 100% efficiency to enter RCM during a system update to take the risk and update without burning fuses.
 
  • Like
Reactions: Friko
The Nintendo Switch's bootloader aka the part that controls the boot-up process for the console checks the number of fuses burnt and compares it to the current firmware. If they do not match, it will either prevent the console from turning on or it will burn them to compensate. While both Hekate and SX OS V1.2+ not only bypass the fuse check entirely as substitute bootloaders but also prevent fuses from being burnt, this is not enough protection against burning fuses during system updates. The reason for this is because when you update the Switch normally, it reboots the console so the Switch has a chance to burn fuses. Even if you initially boot the console with either Hekate or SX OS V1.2+, when you update normally within the Switch, the Switch's bootloader will take over when the console is rebooting after the update. Therefore, the guide not only has you install AutoRCM as a means to prevent you from accidentally booting the Switch normally which will burn fuses, but also has you install the update entirely offline. It should also be worth noting that updating removes any and all forms of AutoRCM which the guide has a section on how to recover it to prevent your Switch from trying to burn fuses.

In theory, you can update without following the tutorial and instead using the official way while not burning fuses IF you can stop the console from turning back on after it updates successfully. This is a very user-oriented window that if you miss will permanently burn the fuses and is a risk you can take should you acknowledge it. Another problem is that once you do manage to turn off the console with the correct timing, you have to ensure from that moment onwards that you will boot your console from RCM only because it will burn the fuses if you turn it on normally. This means you must have some means of inducing RCM with 100% confidence or you risk burning your fuses. AutoRCM cannot save you in this case as it will be removed during the system update and can only be re-installed via RCM.

Lastly, while the guide is rather lengthy, it is nearly 100% noob-proof and will prevent you from burning any fuses. It also details each and every step in such a way that anybody can follow it, even if they have no hacking experience whatsoever.
If I use the guide to update my hackable switch from 4.1 to 6.1 and then turn on the switch without rcm will it still burn the fuses?
 
Nope. You need at least 5.x for that. Just use autorcm so you dont have to worry about forgetting.
 
From what I read Autorcm destroys your console and your battery and you cant turn off your console
the problem of auto rcm is that inevitably you'll think the console is off when in reality it's in rcm and the battery will drain completely, degrading it's lifespan if it happens multiple times. also when this happens it takes a long time for it to charge back up enough for you to be able to turn the switch back on. It can be a pain in the ass.
 
the problem of auto rcm is that inevitably you'll think the console is off when in reality it's in rcm and the battery will drain completely, degrading it's lifespan if it happens multiple times. also when this happens it takes a long time for it to charge back up enough for you to be able to turn the switch back on. It can be a pain in the ass.
Isnt there a way to understand if its in RCM mode or turned of?

--------------------- MERGED ---------------------------
 
Isnt there a way to understand if its in RCM mode or turned of?

--------------------- MERGED ---------------------------
if it's in rcm then you should be able to launch a payload. other than that the switch acts the same when in rcm or off.
 
if it's in rcm then you should be able to launch a payload. other than that the switch acts the same when in rcm or off.
So if I always try to launch a payload and nothing happens that means that my switch is off and my battery isnt getting sucked?
 
So if I always try to launch a payload and nothing happens that means that my switch is off and my battery isnt getting sucked?
either it's off or the battery is already dead. lol. but if in doubt hold the power button for 15 seconds to make sure it's off.
 

Site & Scene News

Popular threads in this forum