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.

 

[wsdyleon]

ON HEKATE: navigate to tools and enable brickmii.
for me “auto rcm”，not brickmii， on hectate3.2

 

[CanIHazWarez]

Hi great guide but one question. After updating and setting up auto rcm, are you able to go into rcm boot menu and boot ofw (not sxos) to update xcis/get future firmware updates/exfat or would that burn fuses? How do you get back into the sx boot menu when autorcm is installed?
Thanks

To answer your first question, you can load OFW without burning fuses if you do it through the sx menu (assuming your sx is above 1.1). You can update your xcis from here, but you still risk getting banned. You can also update the firmware from here but you must repeat the steps from this guide because updating the firmware will remove autoRCM and your console will boot into horizon when it starts, which will burn your fuses.

 

[Evered]

I ended up trying this because I couldn't find the time for the other method. I held Vol+ when the download was at 90%, and it booted right into RCM. I wasn't able to boot into OFW using SXOS 1.3, I just had to use Hekate. Verified with BriccMii that I didn't burn any new fuses

 

[LH1980]

What happens if I uninstall autorcm after the upgrade. Do I have to enable autorcm or can I just boot into sx os directly?

 

[Draxzelex]

What happens if I uninstall autorcm after the upgrade. Do I have to enable autorcm or can I just boot into sx os directly?

Then you risk burning fuses every time you turn your console on UNLESS you boot into RCM first. Since the jig managed to do it without AutoRCM, you just have to be extra careful the console is NEVER turned on without that jig inside which is extremely easy to do. Even plugging in something via USB connection will turn the console on and burn fuses.

Also, since you posted in the right thread this time, I would advise you to report your original posts to a mod so they can be removed.

 

[LH1980]

If I use a cart to update from 4.1.0 to 5.1.0 and never connect online, will the exFAT still be activated?

 

[Draxzelex]

If I use a cart to update from 4.1.0 to 5.1.0 and never connect online, will the exFAT still be activated?

The exFAT update can only be officially obtained by inserting an exFAT formatted SD card into the Switch.

 

[dragon926]

Successfully upgraded without burning fuses. Also getting to the latest firmware and getting exfat compatibility was done at the same time. Didn't need to go through it twice.

 

[JoeBloggs777]

am I right in thinking that you always have to use a jig to enter RCM everytime you power on your switch and if you dont and run OFW it will burn fuses ?

I'm on 4.10 and would like to update to 5.x and install exfat driver, even thou I have a SX pro I'm waiting to see what Atmos or other CFM have to offer, so would like the option of going back to 4.10

 

[Draxzelex]

am I right in thinking that you always have to use a jig to enter RCM everytime you power on your switch and if you dont and run OFW it will burn fuses ?

I'm on 4.10 and would like to update to 5.x and install exfat driver, even thou I have a SX pro I'm waiting to see what Atmos or other CFM have to offer.

Yes, you must use either a very high quality jig or AutoRCM to prevent your Switch from booting normally and instead into RCM to prevent fuses from being burnt. However, AutoRCM is removed upon an official system update so that is why this guide has you keep the jig inserted and holding volume + as the update is installed.

 

[JoeBloggs777]

Yes, you must use either a very high quality jig or AutoRCM to prevent your Switch from booting normally and instead into RCM to prevent fuses from being burnt. However, AutoRCM is removed upon an official system update so that is why this guide has you keep the jig inserted and holding volume + as the update is installed.

thanks Draxzelex , if i remember correctly the other longer way of doing it could also burn fuses?

Draxzelex your a stalwart member of this forum, I would like to thankyou for all your posts, I've not been on here long, but your always willing and helpful to anyone who asks a question or needs help.

 

[Lacius]

thanks Draxzelex , if i remember correctly the other longer way of doing it could also burn fuses?

Draxzelex your a stalwart member of this forum, I would like to thankyou for all your posts, I've not been on here long, but your always willing and helpful to anyone who asks a question or needs help.

Following the long guide by rajkosto won't burn your fuses. Unless you do something wrong, it's not possible.

Following this shorter guide carries a risk of burning fuses during the first reboot after the update.

 

[Draxzelex]

thanks Draxzelex , if i remember correctly the other longer way of doing it could also burn fuses?

Draxzelex your a stalwart member of this forum, I would like to thankyou for all your posts, I've not been on here long, but your always willing and helpful to anyone who asks a question or needs help.

The other way has you install the update 100% offline meaning there is no risk of fuses being burnt. It also uses a special version of AutoRCM that can still boot into RCM after the system update is installed. This method is tailored for those who have SX Pro and wish to do it using SX OS, not Hekate.

 

[JoeBloggs777]

thanks Draxzelex and Lacius, I think I'll hold out a bit longer and stay on 4.10 and hopefully Atmos or ReiNX will be released soon with emunand but then I'll still have the problem of getting the exfat driver.

 

[Rob Blou]

Great guide! I might try this but can anyone explain to me what issues AutoRCM will bring? I'm talking about the sleep/power off/ battery issue.

 

[Sonansune]

Great guide! I might try this but can anyone explain to me what issues AutoRCM will bring? I'm talking about the sleep/power off/ battery issue.

just some inconveniences.
1. only boot after u sent payload.
2. have to use power off in hekate(or other bootloader) to actually turn it off.

 

[Rob Blou]

just some inconveniences.
1. only boot after u sent payload.
2. have to use power off in hekate(or other bootloader) to actually turn it off.

Thanks for that! So you basically have to turn it off, turn it on again to the hekate or SX menu and use the power off option correct?

 

[Lush]

Successfully upgraded without burning fuses. Also getting to the latest firmware and getting exfat compatibility was done at the same time. Didn't need to go through it twice.

So to be clear, do you just insert an exfat card and when it prompts for the update, it installs the exfat driver AND the system update in one shot?

 

[Euwlo]

I have a question somewhat relative to the post, but also a bit different but I don't see a need for a new thread and I couldn't find any posts of it. I am on 4.0.1 and wish to update to 4.1.0, as I can imagine this can only be done using games that have 4.1.0 updates inside the cartridge. But, and that's my question, is there a way to rip an update from a xci and place somewhere on the switch memory without all that hassle from rajkosto method. I wouldn't be worried about burning fuses because it's a minor update and at least from what I know it's the same number of fuses in both versions.

TL-DR: Is there a method to update offline without a physical cart easier than rajkosto (at least in my case not worrying about fuses)?

 

[Draxzelex]

I have a question somewhat relative to the post, but also a bit different but I don't see a need for a new thread and I couldn't find any posts of it. I am on 4.0.1 and wish to update to 4.1.0, as I can imagine this can only be done using games that have 4.1.0 updates inside the cartridge. But, and that's my question, is there a way to rip an update from a xci and place somewhere on the switch memory without all that hassle from rajkosto method. I wouldn't be worried about burning fuses because it's a minor update and at least from what I know it's the same number of fuses in both versions.

TL-DR: Is there a method to update offline without a physical cart easier than rajkosto (at least in my case not worrying about fuses)?

Have you tried running a backup that contains the firmware update you seek?

 

[Sonansune]

I have a question somewhat relative to the post, but also a bit different but I don't see a need for a new thread and I couldn't find any posts of it. I am on 4.0.1 and wish to update to 4.1.0, as I can imagine this can only be done using games that have 4.1.0 updates inside the cartridge. But, and that's my question, is there a way to rip an update from a xci and place somewhere on the switch memory without all that hassle from rajkosto method. I wouldn't be worried about burning fuses because it's a minor update and at least from what I know it's the same number of fuses in both versions.

TL-DR: Is there a method to update offline without a physical cart easier than rajkosto (at least in my case not worrying about fuses)?

4.0.1 and 4.1 have the same burned fuses.(5) find a cartridge with 4.1 update.

but i dont see the point here. 4.0.1 and 4.1 exploitability wise, basically the same.