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.

 

[Euwlo]

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

I have SX OS, I tried but It says that can't find the cartridge when I press update.

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

but i don't see the point here. 4.0.1 and 4.1 exploitability wise, basically the same.

The point was to play newer games on SX OX.

 

[dragon926]

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?

yep!

 

[Draxzelex]

I have SX OS, I tried but It says that can't find the cartridge when I press update.

Well it seems there is a way, but it involves following another tricky guide. It turns out the exFAT update tutorials use the hidden game updates found on cartridges to update the system to that firmware with the exFAT update. Unfortunately, it doesn't seem like there is a way currently to extract that update onto an SD card or something and run it from the console (otherwise those tutorials would become obsolete).

 

[Pacote]

I can just update with the switch hooked on my computer and hold vol+ and when it restarts it would appear on the software and I can just boot hekate correct?

No actually need for a sx pro aye?

This is so risky that I wouldn't trust my magnet switch, will probably solder both pints together to be extra sure it will boot into rcm

 

[lordelan]

The question is, if I updated through rajkosto's tutorial to 5.1 and a higher FW comes out, can we simply update through official methods (online or cartridge) using your tutorial even if we did rajkosto's before?

 

[Draxzelex]

The question is, if I updated through rajkosto's tutorial to 5.1 and a higher FW comes out, can we simply update through official methods (online or cartridge) using your tutorial even if we did rajkosto's before?

Indeed. Rajkosto's method is less prone to user error

 

[Lacius]

Indeed. Rajkosto's method is just more foolproof and prone to error

More prone to error?

 

[Draxzelex]

More prone to error?

When you have a personalized Auto Correct (amended my post already)

 

[Maiken]

I just read above that it is possible to update the system and get exFAT at the same time. Just to make sure: installing exFAT doesn't format the microSD card?

 

[lordelan]

I just read above that it is possible to update the system and get exFAT at the same time. Just to make sure: installing exFAT doesn't format the microSD card?

No it's just a driver on your NAND.

 

[Ghassen-ga]

does this mean the fuses will be burnt if u ever decided to return to OFW and not boot hekate ?

 

[Draxzelex]

does this mean the fuses will be burnt if u ever decided to return to OFW and not boot hekate ?

If you don't boot through Hekate or SX OS V1.2+, your fuses will be permanently burnt.

 

[Beb0P]

If you don't boot through Hekate or SX OS V1.2+, your fuses will be permanently burnt.

Just so I'm clear, if I boot up SX OS main menu and then select boot original FW, then that won't burn any fuses right? I'm on 5.1.0 with only 5 burned. What we want to avoid is have autorcm off and forget to power on without the jig/dongle, which will start the stock horizon and do a fuse check and burn them.

 

[Draxzelex]

Just so I'm clear, if I boot up SX OS main menu and then select boot original FW, then that won't burn any fuses right? I'm on 5.1.0 with only 5 burned. What we want to avoid is have autorcm off and forget to power on without the jig/dongle, which will start the stock horizon and do a fuse check and burn them.

You can boot either OFW or CFW. As long as you're booting from SX OS or Hekate, you will be fine. If you boot up the console without going through either of those, your fuses will be permanently burnt.

 

[JoeBloggs777]

Just so I'm clear, if I boot up SX OS main menu and then select boot original FW, then that won't burn any fuses right? I'm on 5.1.0 with only 5 burned. What we want to avoid is have autorcm off and forget to power on without the jig/dongle, which will start the stock horizon and do a fuse check and burn them.

noob question, I'm on 4.10 and updated from 4.01 using a game cart. I've 5 burnt fuses, I take it the above posters switch came with 5.1.0 on his when he bought it as he has 5 burned fuses ?. unless i burnt a fuse upgrading from 4.01 to 4.1 which is a minor update.
thanks

 

[Beb0P]

You can boot either OFW or CFW. As long as you're booting from SX OS or Hekate, you will be fine. If you boot up the console without going through either of those, your fuses will be permanently burnt.

Thanks for the quick response! Also for those nervous about using this simpler method I wanted to add that it worked great for me. I was fine with the extra risk since I have another console I'm leaving unhacked and rajkosto's method was a bit complicated for me since I'm more of a hacking newbie.

 

[shchmue]

noob question, I'm on 4.10 and updated from 4.01 using a game cart. I've 5 burnt fuses, I take it the above posters switch came with 5.1.0 on his when he bought it as he has 5 burned fuses ?. unless i burnt a fuse upgrading from 4.01 to 4.1 which is a minor update.
thanks

5 fuses is the normal amount for 4.x. this user would have to have upgraded to 5.1.0 using one of these no-fuse methods.

 

[JoeBloggs777]

5 fuses is the normal amount for 4.x. this user would have to have upgraded to 5.1.0 using one of these no-fuse methods.

thanks shchmue

 

[Sonansune]

indeed risky.
today, i replaced my second backup loader switch sdhc with a sdxc and performed an update.
I was already on 5.1, so I thought it's just an exfat patch and wont remove autorcm, but that's not the case.

i guess no more downgrading on this one.
fuses 5 to 6, sad story. no more deja vu


i will stick with rajkosto's method for the main online switch then.

 

[JoeBloggs777]

indeed risky.
today, i replaced my second backup loader switch sdhc with a sdxc and performed an update.
I was already on 5.1, so I thought it's just an exfat patch and wont remove autorcm, but that's not the case.

i guess no more downgrading on this one.
fuses 5 to 6, sad story. no more deja vu


i will stick with rajkosto's method for the main online switch then.

from the very helpful Draxzelex.

You still need to insert an exFAT formatted SD card HOWEVER if you try to install the exFAT update officially, it will try to burn your fuses again so you will have to follow this guide again.