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.

 

[Sephirosu]

Not trying to Necro the thread but I just wanted to point out that this way still works!

Restored back to 2.0, followed my previous steps and then updated to 6.2 using the switch's regular update and didn't burn a fuse.



I want to add that Im also using hekate as my bootloader and have autorcm activate to not screw myself over.



Still think this is the easiest way to update. Waaaaay easier than the other more complicated way.

 

[Lacius]

Not trying to Necro the thread but I just wanted to point out that this way still works!

Restored back to 2.0, followed my previous steps and then updated to 6.2 using the switch's regular update and didn't burn a fuse.

View attachment 156196 View attachment 156195

I want to add that Im also using hekate as my bootloader and have autorcm activate to not screw myself over.

View attachment 156194

Still think this is the easiest way to update. Waaaaay easier than the other more complicated way.

Nobody should use this method. ChoiDujourNX is just as easy but doesn't carry any risk.

 

[Sephirosu]

Nobody should use this method. ChoiDujourNX is just as easy but doesn't carry any risk.

You would need to find the firmware file to be able to update with choidujour.

It certainly is better to use that if youve installed NSPs or used retroarch for example since it would be suicide to connect to Nintendo's network but for someone who just wants keep their fuses intact this is the easier way.

Still haven't seen any risk unless you let go of the Vol + button before the switch restarts for example or your jig isn't working properly.

 

[Lacius]

You would need to find the firmware file to be able to update with choidujour.

It certainly is better to use that if youve installed NSPs or used retroarch for example since it would be suicide to connect to Nintendo's network but for someone who just wants keep their fuses intact this is the easier way.

Still haven't seen any risk unless you let go of the Vol + button before the switch restarts for example or your jig isn't working properly.

ChoiDujourNX is easier and carries no risk of accidentally burning your fuses.

 

[Sephirosu]

This method still works with 7.0.0 and 7.0.1 if anyone was curious.

Remember to have hekate as the custom bootloader and don't launch stock normally...

I'm using the contents of kosmos' SD package (bootloader + Sept + atmosphere) to launch stock by using atmosphere's fusee. Still only have my 2 burnt fuses!

What I have noticed is that on some of the switches I've used this method to update them is that their Gamecart slot might not work for some reason on 7.0.x when an SD card is present when updating from 2.0 (haven't tried on switches above 2.0). however, the Gamecart slot worked just fine on 6.2 and Bellow while said SD is in the switch.... Very odd (had Nand backups to test it out)

Basically what happened in this dude's thread:

https://gbatemp.net/threads/switch-game-card-could-not-be-read-error.527173/

 

[Neo_]

After I have done all the steps can I deactivate autorcm?

 

[DrDoctor]

Nobody should use this method. ChoiDujourNX is just as easy but doesn't carry any risk.

I'm planning on updating my sysNAND and from the information I gathered, using ChoiDujourNX requires using CFW on sysNAND and, while there are any cases of it, it's not impossible that it can lead to bans.

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).

To avoid any guesswork, I'm thinking of having my Switch connected to my PC with TegraRCMGUI running so I can tell exactly when it goes into RCM.

 

[Lacius]

I'm planning on updating my sysNAND and from the information I gathered, using ChoiDujourNX requires using CFW on sysNAND and, while there are any cases of it, it's not impossible that it can lead to bans.

Instead, I would recommend running vanilla Atmosphere (no homebrew, no signature patches) and updating your sysNAND in the system settings with AutoRCM already installed. The sysNAND will likely remain clean, and AutoRCM will be preserved.

 

[untipofeliz]

Sounds interesting and risky for users with short attention span

 

[DrDoctor]

Instead, I would recommend running vanilla Atmosphere (no homebrew, no signature patches) and updating your sysNAND in the system settings with AutoRCM already installed. The sysNAND will likely remain clean, and AutoRCM will be preserved.

How can I tell that I'm not running signature patches?
Is this how it should look in the hekate_ipl.ini?

[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
;kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

 

[Lacius]

How can I tell that I'm not running signature patches?
Is this how it should look in the hekate_ipl.ini?

[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
;kip1patch=nosigchk
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

I'd do it with fusee primary, not Hekate.

 

[DrDoctor]

• Back up everything (boot, raw nand, sd card, you can't be too safe) and keep it someplace safe and labeled

Isn't burning fuses the worst that could happen? What can the nand backup be used for?

 

[Draxzelex]

Isn't burning fuses the worst that could happen? What can the nand backup be used for?

A brick is the worst thing that can happen to your console. Burnt fuses only limit you to loading specific firmware versions without RCM. Burnt fuses mean nothing to a Fusee-Gelee vulnerable console.

 

[deSSy2724]

Can they even detect and ban us for fuse mismatch (higher firmware with not enough fuses burnt)? As far as I know, autoRCM is detectable and they can ban us.

 

[Draxzelex]

Can they even detect and ban us for fuse mismatch (higher firmware with not enough fuses burnt)? As far as I know, autoRCM is detectable and they can ban us.

While they can detect a fuse mismatch as well as AutoRCM, no one has been banned just for having AutoRCM and/or a fuse mismatch yet. This can change in the future but I think it is highly unlikely.

 

[deSSy2724]

While they can detect a fuse mismatch as well as AutoRCM, no one has been banned just for having AutoRCM and/or a fuse mismatch yet. This can change in the future but I think it is highly unlikely.

Can any homebrew (inside Horizon) read /check how many fuses are burnt or that the boot0 is corrupted (because of autorcm) or is only the bootrom / rcm mode capable of doing that?

 

[HideoKojima]

thought this before, never have the courage to try it.

Coward

 

[Sonansune]

Coward

 

[Draxzelex]

Can any homebrew (inside Horizon) read /check how many fuses are burnt or that the boot0 is corrupted (because of autorcm) or is only the bootrom / rcm mode capable of doing that?

While I am not sure if it is possible or not (more likely that it is possible), there is no homebrew application that can check burnt fuses or AutoRCM.

 

[HideoKojima]

But smart as u thought of it

 

[HideoKojima]

But smart as u thought of it

 

[HideoKojima]

But smart as u thought of it

 

[Sephirosu]

Just wanted to update people who still want to attempt this:

It still works with the latest switch update.