An EASY(but a bit more risky) way to update Switch Firmware WITHOUT burning any fuses

So I know there is already a very detailed tutorial out there that is quite good and safer than what I am writing, but a number of people seem to be interested in the method I discovered and have tested.
If you are interested in the safer(perhaps) way please look at this thread:
https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

So the way I figured out basically sets up autoRCM or Brickmii right after the update, before any fuses can be burned. This is why this is potentially risky, if you do not boot into rcm after the update restart before the regular switch os boots the fuses will be burned and you will not be able to downgrade (at least without some other caveats)

DISCLAIMER: I believe this procedure is safe, but I take no responsibility if you somehow do burn fuses, get banned online, or other wise damage or break(brick) your switch console or connected hardware.3

NOTE: AutoRCM and Brickmii have a good chance of causing a small bug that prevents the system from staying powered completely off for more than 30 seconds, there may be a fix for this in the future. Also note that if your console boots to RCM without a payload device or computer sending it, it will appear to be off and can not charge, but will drain battery. I personal find this mildly annoying but most of the time I can keep it asleep in dock or powered on.

Also NOTE: this manner of updates may affect your cart slot firmware and may make the slot not read carts when loading an old fw version.

Things you will need:
  • a rcm jig, or other reliable way to enter rcm (not autorcm or brickmii as they get removed during updates)
  • A SX pro widget or similar product, or a realiable way to load a payload like sx os or hekate

Steps:
  1. Back up everything (boot, raw nand, sd card, you can't be too safe) and keep it someplace safe and labeled
  2. Check the fuse info using hekate, note how many are burned, so you know what you expect to see after the update
  3. Boot up switch in OFW or CFW or even just plain with no mods or loaders
  4. Once booted have your RCM jig inserted and ready to go ( be sure you have confirmed that this actually works)
  5. using either a cartridge or updating via system settings (assuming you are comfortable going online, but I think this is safe) begin updating your system
  6. *MOST IMPORTANT* When the update is almost done or the second you see the complete notification hold the [VOL +] button. And continue holding it till you get to hekate or sx os menu.
  7. When the system reboots it should be in RCM mode, if you have a widget plugged in it should boot to SX OS or Hekate
    IF ON SX OS: navigate to tools and enable auto RCM.
    IF ON HEKATE: navigate to tools and enable brickmii.
  8. Boot into CFW and you will be on the updated fw without having burned fuses
  9. Feel free to use hekate menu to view the fuse info to confirm the fuses are in the same state.

Hope you find this useful.
P.s. I may post a guide on how to downgrade using backup, and a way to protect your cart slot fw as well in the future.
 

Wurztha

Admìn MoFo :P
Member
Joined
Jul 7, 2015
Messages
158
Trophies
0
Age
43
Location
Behind you!
XP
171
Country
Just wanted to warn people, although I am new to this so may be confused! Just did this to update from 2.00 and Hekate originally reported 2 burnt fuses. System now at 5.1.0 and Hekate reports 6 burnt fuses. Ahh well XD

After update console booted directly to ReiNX. I then rebooted to Hekate 3.2 to check fuses and say 6 burnt. Don't know if Nintendo changed the way the update works or if some other unknown voodoo caused this but there you go.
 

mugendc4

Well-Known Member
Newcomer
Joined
Nov 6, 2007
Messages
49
Trophies
0
XP
545
Country
United States
Thanks for the guide.. Was on FW 4.1 with 5 burnt fuses and updated 5.1 and still have 5 burnt fuses :) (Wanted to play new games)... Just got to be careful because I'm not a fan with autoRCM draining battery and remember to always put my console in sleep mode and pray that I don't forget to boot into CFW.

Just wanted to warn people, although I am new to this so may be confused! Just did this to update from 2.00 and Hekate originally reported 2 burnt fuses. System now at 5.1.0 and Hekate reports 6 burnt fuses. Ahh well XD

After update console booted directly to ReiNX. I then rebooted to Hekate 3.2 to check fuses and say 6 burnt. Don't know if Nintendo changed the way the update works or if some other unknown voodoo caused this but there you go.

Weird... I just updated and it seems to work for me? Not sure if something is different from 2.00 but I came from 4.1 and still have 5 burnt fuses upgrading to 5.1
 

xfighter11

Well-Known Member
Newcomer
Joined
Oct 18, 2015
Messages
78
Trophies
0
Age
42
XP
616
Country
Gambia, The
I don't know why but unfortunately this method burnt a fuse :(. I wanted to update to 5.1.0 (from 4.1.0). Before fuse info said 5 fuses burnt and after update it said 6 fuses burnt. Does this mean I cannot downgrade my Switch anymore?
 

mugendc4

Well-Known Member
Newcomer
Joined
Nov 6, 2007
Messages
49
Trophies
0
XP
545
Country
United States
I don't know why but unfortunately this method burnt a fuse :(. I wanted to update to 5.1.0 (from 4.1.0). Before fuse info said 5 fuses burnt and after update it said 6 fuses burnt. Does this mean I cannot downgrade my Switch anymore?

unfortunately you won't be able to downgrade since you burnt 6 fuses :sad:... Not sure if this made a difference, I followed his steps and boot into SXOS CFW right after the update.. Fully powerdown the switch and inject hekate to verify fuses, then booted back to SXOS CFW.
 

alucard_xs

Well-Known Member
Member
Joined
Oct 31, 2012
Messages
703
Trophies
1
Age
113
XP
2,723
Country
Canada
unfortunately you won't be able to downgrade since you burnt 6 fuses :sad:... Not sure if this made a difference, I followed his steps and boot into SXOS CFW right after the update.. Fully powerdown the switch and inject hekate to verify fuses, then booted back to SXOS CFW.
is the autoRCM install mandatory in step 7 ?
I do not want it install, I prefer my JIG and dongle all the times but in the tuto, it tells to install autoRCM ...
 
Last edited by alucard_xs,

Mr. Wizard

Ending the spread of bullshit one thread at a time
Member
Joined
Mar 20, 2015
Messages
1,814
Trophies
0
Location
E8 lattice
XP
1,532
Country
Canada
Just wanted to warn people, although I am new to this so may be confused! Just did this to update from 2.00 and Hekate originally reported 2 burnt fuses. System now at 5.1.0 and Hekate reports 6 burnt fuses. Ahh well XD

After update console booted directly to ReiNX. I then rebooted to Hekate 3.2 to check fuses and say 6 burnt. Don't know if Nintendo changed the way the update works or if some other unknown voodoo caused this but there you go.
so jig and dongle is enough I guess.
Jig is a must, updating removes AutoRCM afaik. So if you don't catch it before the reboot say bye bye to your fuses.
 

mugendc4

Well-Known Member
Newcomer
Joined
Nov 6, 2007
Messages
49
Trophies
0
XP
545
Country
United States
is the autoRCM install mandatory in step 7 ?
I do not want it install, I prefer my JIG and dongle all the times but in the tuto, it tells to install autoRCM ...

the main reason the op recommended autorcm because just in case you accidentally rebooted your switch and it will reboot to the original FW. It's very easy for that to happen, for instance if you were careless and plug in the usb before putting the switch in RCM mode, the switch will autoboot on. I didn't turn it on but I just have to be extra careful.
 

Mr. Wizard

Ending the spread of bullshit one thread at a time
Member
Joined
Mar 20, 2015
Messages
1,814
Trophies
0
Location
E8 lattice
XP
1,532
Country
Canada
the main reason the op recommended autorcm because just in case you accidentally rebooted your switch and it will reboot to the original FW. It's very easy for that to happen, for instance if you were careless and plug in the usb before putting the switch in RCM mode, the switch will autoboot on. I didn't turn it on but I just have to be extra careful.
[Question for mugendc4]
So you would rather live with a very high risk of burning your fuses because of?
[/question]

[Rant]
I have not heard of anyone losing their switch because of autorcm.
It's dangerous because modifying anything in anyway comes with risk.
I could go and format my PCs drive right now and wipe everything, does that mean nobody should ever use the format command?
Any tool is potentially dangerous in the hands of an idiot.

What is all this misinformation about autorcm being the devil?
[/rant]
 
Last edited by Mr. Wizard,

mugendc4

Well-Known Member
Newcomer
Joined
Nov 6, 2007
Messages
49
Trophies
0
XP
545
Country
United States
So you would rather live with a very high risk of burning your fuses because of?
I have not heard of anyone losing their switch because of autorcm.
It's dangerous because modifying anything in anyway comes with risk.
I could go and format my PCs drive right now and wipe everything, does that mean nobody should ever use the format command?
Any tool is potentially dangerous in the hands of an idiot.

What is all this misinformation about autorcm being the devil?

I keep my switch 100% always on sleep mode and make sure the battery is usually charge. I never recommended not to put the switch into AutoRCM mode so don't put words into my mouth. I stated my reason a few post back because battery drain issue with AutoRCM so I don't use it. All I stated, if you're not going to use AutoRCM just be extra careful. Also the only thing that is being risked without having AutoRCM turned on is burning fuses, not sure how it got interpreted as bricking or losing a switch.
 
Last edited by mugendc4,

Mr. Wizard

Ending the spread of bullshit one thread at a time
Member
Joined
Mar 20, 2015
Messages
1,814
Trophies
0
Location
E8 lattice
XP
1,532
Country
Canada
I keep my switch 100% always on sleep mode and make sure the battery is usually charge. I never recommended not to put the switch into AutoRCM mode so don't put words into my mouth. I stated my reason a few post back because battery drain issue with AutoRCM when in sleep mode so I don't use it. All I stated, if you're not going to use AutoRCM just be extra careful.
Not everything in the world is about you. Where did I say you didn't recommend it? Basically the first sentence in my post was directed at you, the rest was a rant for everyone. I'll change my post to reflect that.

And you never answered why you aren't using autorcm and risking your fuses for no apparent reason. I can only assume it's because of all the bullshit you've read on here.
 
Last edited by Mr. Wizard,

Sephirosu

Well-Known Member
Member
Joined
Jan 28, 2015
Messages
266
Trophies
0
Age
34
Location
Boca Raton, Florida
XP
436
Country
I would like to comment that i have successfully updated my console to 5.1 and haven't burnt a fuse yet using this guide (even got the sdx update too!)

IMG_20180729_014539.jpg


IMG_20180729_013559.jpg


Imo it's 20000000 times easier than the other one and error free (except for human error).
 

magico29

Well-Known Member
Member
Joined
Aug 2, 2017
Messages
1,586
Trophies
0
XP
1,895
Country
United States
So I know there is already a very detailed tutorial out there that is quite good and safer than what I am writing, but a number of people seem to be interested in the method I discovered and have tested.
If you are interested in the safer(perhaps) way please look at this thread:
https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

So the way I figured out basically sets up autoRCM or Brickmii right after the update, before any fuses can be burned. This is why this is potentially risky, if you do not boot into rcm after the update restart before the regular switch os boots the fuses will be burned and you will not be able to downgrade (at least without some other caveats)

DISCLAIMER: I believe this procedure is safe, but I take no responsibility if you somehow do burn fuses, get banned online, or other wise damage or break(brick) your switch console or connected hardware.3

NOTE: AutoRCM and Brickmii have a good chance of causing a small bug that prevents the system from staying powered completely off for more than 30 seconds, there may be a fix for this in the future. Also note that if your console boots to RCM without a payload device or computer sending it, it will appear to be off and can not charge, but will drain battery. I personal find this mildly annoying but most of the time I can keep it asleep in dock or powered on.

Also NOTE: this manner of updates may affect your cart slot firmware and may make the slot not read carts when loading an old fw version.

Things you will need:
  • a rcm jig, or other reliable way to enter rcm (not autorcm or brickmii as they get removed during updates)
  • A SX pro widget or similar product, or a realiable way to load a payload like sx os or hekate

Steps:
  1. Back up everything (boot, raw nand, sd card, you can't be too safe) and keep it someplace safe and labeled
  2. Check the fuse info using hekate, note how many are burned, so you know what you expect to see after the update
  3. Boot up switch in OFW or CFW or even just plain with no mods or loaders
  4. Once booted have your RCM jig inserted and ready to go ( be sure you have confirmed that this actually works)
  5. using either a cartridge or updating via system settings (assuming you are comfortable going online, but I think this is safe) begin updating your system
  6. *MOST IMPORTANT* When the update is almost done or the second you see the complete notification hold the [VOL +] button. And continue holding it till you get to hekate or sx os menu.
  7. When the system reboots it should be in RCM mode, if you have a widget plugged in it should boot to SX OS or Hekate
    IF ON SX OS: navigate to tools and enable auto RCM.
    IF ON HEKATE: navigate to tools and enable brickmii.
  8. Boot into CFW and you will be on the updated fw without having burned fuses
  9. Feel free to use hekate menu to view the fuse info to confirm the fuses are in the same state.

Hope you find this useful.
P.s. I may post a guide on how to downgrade using backup, and a way to protect your cart slot fw as well in the future.
my fuses info says: burn fuses 1. why? my console is on 1.0.0i never update or use sx on this switch.
 

Sephirosu

Well-Known Member
Member
Joined
Jan 28, 2015
Messages
266
Trophies
0
Age
34
Location
Boca Raton, Florida
XP
436
Country
@quantumboy btw op (this is not a critic or me trying to be a smartass or anything) I would change the title of the thread to something more eye catching. I think a lot of people are discouraged from attempting this even though it's easier and "more user-friendly" than the other guide because of the title.
 

Wurztha

Admìn MoFo :P
Member
Joined
Jul 7, 2015
Messages
158
Trophies
0
Age
43
Location
Behind you!
XP
171
Country
I would like to comment that i have successfully updated my console to 5.1 and haven't burnt a fuse yet using this guide (even got the sdx update too!)
SNIP
Imo it's 20000000 times easier than the other one and error free (except for human error).

Glad to hear it's still working :) Don't know how mine went wrong and burnt them as after the update I booted straight into ReiNX then rebooted again into Hekate (I used NXLoader and had ReiNX loaded as the payload so swapped it back to Hekate to check)

Maybe you NEED to boot to Hekate after the update and not *any* payload?
 

Sephirosu

Well-Known Member
Member
Joined
Jan 28, 2015
Messages
266
Trophies
0
Age
34
Location
Boca Raton, Florida
XP
436
Country
Glad to hear it's still working :) Don't know how mine went wrong and burnt them as after the update I booted straight into ReiNX then rebooted again into Hekate (I used NXLoader and had ReiNX loaded as the payload so swapped it back to Hekate to check)

Maybe you NEED to boot to Hekate after the update and not *any* payload?


Yeah dunno what went wrong with you =\

I'll try to be as detailed as possible if anyone is also interested:

Disclaimer: I basically followed what was said in the guide in the first page.

1- Placed an exFAT formated Samsung 64gb SD card in my switch and tested my jig like 5 times by continously just booting (going into RCM and sending the payload) into Hekate.

2- While in hekate I checked my fuses (look at my picture) and did a backup of both the raw emmc and the boot partitions to be able to downgrade in the future.

3- Once the backup was done, I booted into OFW (with my jig still in place and the exFAT SD card still inserted but its contents were stored in my PC thus there was nothing in said card), entered my router's info and pressed the "there is an SDX update you must download" prompt and began to download both the SD slot update and the 5.1 update.

4- At around 80% I pressed the Vol+ button and didn't let go until the switch booted into RCM (until the screen was all black. Left it pressed like 30 secs to make sure it did).

5- Launched hekate, checked my fuses and I still had 2 burnt fuses!

6- Installed AutoRCM (my switch sits on its charger all day so I don't care about the battery problem that much).

7- Rebooted into RCM and launched ReiNX and checked the version number (look at my picture).

Everything seems to be working a-ok. Updated BOTW and deleted my internet settings right after.
 
Last edited by Sephirosu,

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Xdqwerty @ Xdqwerty: