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.

 

[Draxzelex]

Finally, I don't have to dig up your old quote on how to update without following the other tutorial XD

 

[TR_mahmutpek]

Looking useful, thx

 

[RednaxelaNnamtra]

Just thought about making a thread about this today, but kinda forgot about it later, so nice that finally somebody posted the easier method in a way that other are able to find it by searching.
I used this method a few week ago to update from 3.0.0 to 5.1.0, I just kept holding the vol-+ button while the update was running, just to be sure not to miss the right moment. xD

 

[wsdyleon]

will have a try

 

[MR_TeCKnO]

will updating through systems also add exfat functionality or do i need to format my micro sd card to exfat and see the message to update then update through that?

 

[Draxzelex]

will updating through systems also add exfat functionality or do i need to format my micro sd card to exfat and see the message to update then update through that?

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.

 

[quantumboy]

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.

I got the exfat working when I did the update, I didn't have to update separate but that was from 4.1, so maybe from 3.0.0 that would have been a problem

 

[MR_TeCKnO]

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.

So i need to do these steps twice?

I got the exfat working when I did the update, I didn't have to update separate but that was from 4.1, so maybe from 3.0.0 that would have been a problem

i am also on 4.1.0
so you you didn't need to do it twice?
you just went to systems and updated without seeing the exfat message?
did you format your micro sd card to exfat before update ?
do i need to format to exfat before update?

sorry for all the questions
thank you

 

[quantumboy]

So i need to do these steps twice?



i am also on 4.1.0
so you you didn't need to do it twice?
you just went to systems and updated without seeing the exfat message?
did you format your micro sd card to exfat before update ?
do i need to format to exfat before update?

sorry for all the questions
thank you

I can't say for certain, but I am pretty sure that if you try the exfat update it will restart just like before, you will need to hold vol + at the right time to make sure you can reinstall autorcm

 

[Draxzelex]

I got the exfat working when I did the update, I didn't have to update separate but that was from 4.1, so maybe from 3.0.0 that would have been a problem

Meaning you already had the exFAT update which is good for you.

So i need to do these steps twice?

Yes, you must do it twice because the console will restart after installing the exFAT update so be ready to enter RCM or turn off the console when it tries to reboot and burn fuses.

 

[MR_TeCKnO]

Meaning you already had the exFAT update which is good for you.
Yes, you must do it twice because the console will restart after installing the exFAT update so be ready to enter RCM or turn off the console when it tries to reboot and burn fuses.

so second time:
1-i will boot sx os menu choose OFW
2-after that i will remove the sd card from switch, format it to exfat and put boot.dat file in sd card
3-insert it and update
4-keep pressing +vol when near end of update
5-and it should recognize the exfat sd card with boot.dat and boot to sx os.

is this correct?
thanks so much for your help.

 

[Draxzelex]

so second time:
1-i will boot sx os menu choose OFW
2-after that i will remove the sd card from switch, format it to exfat and put boot.dat file in sd card
3-insert it and update
4-keep pressing +vol when near end of update
5-and it should recognize the exfat sd card with boot.dat and boot to sx os.

is this correct?
thanks so much for your help.

If you are following the guide and using the SX Pro jig, it should boot into SX OS while you hold volume + since rebooting the system this way can turn into RCM if the conditions are met.

 

[MR_TeCKnO]

If you are following the guide and using the SX Pro jig, it should boot into SX OS while you hold volume + since rebooting the system this way can turn into RCM if the conditions are met.

what i am trying to figure out is if it will boot to sx os if the micro sd is formatted to exfat after the update
what i am afraid of is the switch not recognizing the sd card which in turn will not boot into sx os

 

[Draxzelex]

what i am trying to figure out is if it will boot to sx os if the micro sd is formatted to exfat after the update
what i am afraid of is the switch not recognizing the sd card which in turn will not boot into sx os

SX OS supports exFAT and can support exFAT formatted SD cards because it boots outside of Horizon. In English, you don't need exFAT support on your console to boot SX OS on an exFAT formatted SD card.

 

[Sonansune]

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

 

[MR_TeCKnO]

SX OS supports exFAT and can support exFAT formatted SD cards because it boots outside of Horizon. In English, you don't need exFAT support on your console to boot SX OS on an exFAT formatted SD card.

thank you so much just the answer i was looking for
also i will try to do system update and exfat in one try
saw a video on youtube a guy did the update for exfat and it updated the FW at same time maybe this will work

Thanks again

 

[Draxzelex]

thank you so much just the answer i was looking for
also i will try to do system update and exfat in one try
saw a video on youtube a guy did the update for exfat and it updated the FW at same time maybe this will work

Thanks again

This is not just to you but to anyone attempting this in general: there seems to be evidence the console is aware that pin 10 is being shorted. Why does this matter? Well you grab the official system update by connecting online and when you connect online, you send a lot of information to Nintendo. This is one of them. Whether or not they ban people for this sort of thing is pure speculation (not to mention you're running SX OS in the first place) so be careful of an impending ban when updating the easy way.

 

[dragon926]

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

 

[Draxzelex]

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

Hold volume + when you send the payload/plug in the dongle to load the SX OS menu again. Its designed to auto-boot into CFW with an activated license. Honestly, it'd be nice if TX gave users the option to toggle this rather than force it upon them.