Hacking How to update to 5.1 without getting banned

[waterboy92]

Hi people,

so I want to update to firmware 5.1. I am using SX OS 1.3 and I am on firmware 4.1 as for right now.
What is your suggestion to update safely with minimizing to get banned?

 

[Rudolf]

Do it like this: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/
(not for the faint of heart...)

 

[Kubas_inko]

Update itself can't get you banned. Going online in any way can get you banned.

 

[waterboy92]

Thank you a lot. I've actually found this thread already before but decided that this might be a bit too complicated for a noob like me. Besides that, it would probably take me hours and hours.

 

[Maximilious]

Thank you a lot. I've actually found this thread already before but decided that this might be a bit too complicated for a noob like me. Besides that, it would probably take me hours and hours.

You can update through OFW, just make sure you boot into RCM mode with your jig at next boot or your fuses will burn. Turn on AutoRCM afterwards to ensure your fuses don't burn next time you turn on your console. If you're using SX OS in offline mode only then being banned really shouldn't matter, but right now it appears the bans handed out are luck of the draw even for those trying to be "safe"

 

[mooglazer]

You can update through OFW, just make sure you boot into RCM mode with your jig at next boot or your fuses will burn. Turn on AutoRCM afterwards to ensure your fuses don't burn next time you turn on your console.

So am I understanding that correctly, that you can update normally but power-off before reboot, auto-rcm and your fuses are intact?

Assuming I have a NAND dump from the version before the update (say 4.1.0), I can restore back to it at a later date?

 

[Draxzelex]

So am I understanding that correctly, that you can update normally but power-off before reboot, auto-rcm and your fuses are intact?

Assuming I have a NAND dump from the version before the update (say 4.1.0), I can restore back to it at a later date?

When you update your firmware, it doesn't automatically burn the fuses. The fuses are burnt when a higher firmware is run as soon as the Switch is turned on. If you hijack this process and replace it with another bootloader (i.e. Hekate or SX OS V1.2+) then you can bypass the fuse process entirely. The problem is the timing as if your off, you risk burning the fuses the second you see the Nintendo logo. To double check your work, you would run briccmii V2 afterwards.

 

[quantumboy]

When you update your firmware, it doesn't automatically burn the fuses. The fuses are burnt when a higher firmware is run as soon as the Switch is turned on. If you hijack this process and replace it with another bootloader (i.e. Hekate or SX OS V1.2+) then you can bypass the fuse process entirely. The problem is the timing as if your off, you risk burning the fuses the second you see the Nintendo logo. To double check your work, you would run briccmii V2 afterwards.

can you not have brickmii or autorcm setup before the update process?

 

[mooglazer]

can you not have brickmii or autorcm setup before the update process?

I was about to ask the same question. Sounds like it can't fail if you're AutoRCM'd prior to the system update? Has anyone done this?

 

[quantumboy]

I was about to ask the same question. Sounds like it can't fail if you're AutoRCM'd prior to the system update? Has anyone done this?

basically I have a system on 4.1 I want to use my SX pro on (just got) and I figured I would back up the nand and boot, then install autorcm from sx menu, then update the firmware from horizon(the switch OS) settings menu (with auto rcm already setup) when the system restarts it should be protected automatically by auto rcm. then make a new back up before starting to get things like quest and such
Will that work?

 

[Lacius]

basically I have a system on 4.1 I want to use my SX pro on (just got) and I figured I would back up the nand and boot, then install autorcm from sx menu, then update the firmware from horizon(the switch OS) settings menu (with auto rcm already setup) when the system restarts it should be protected automatically by auto rcm. then make a new back up before starting to get things like quest and such
Will that work?

No, AutoRCM will be removed during the update process. It is highly recommended that anyone who doesn't want to burn efuses update following the above guide. Anything else is risky.
https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

 

[Draxzelex]

When you update officially (meaning from within the Switch console), it removes AutoRCM/briccmii. This means that you will risk the Switch booting normally which will burn the fuses unless you hijack the process (by powering down the console before it turns back on but after it has updated). This is also why the guide rajkosto made uses an offline means of updating so you can avoid taking this risk. That is not to say you can accomplish what his guide does with an official update, but it is certainly a lot riskier if you don't know the proper timing of events which can lead to user-error. Attempt to do it at your own risk.

EDIT: Ninja'd as usual, nothing to see here

 

[quantumboy]

When you update officially (meaning from within the Switch console), it removes AutoRCM/briccmii. This means that you will risk the Switch booting normally which will burn the fuses unless you hijack the process (by powering down the console before it turns back on but after it has updated). This is also why the guide rajkosto made uses an offline means of updating so you can avoid taking this risk. That is not to say you can accomplish what his guide does with an official update, but it is certainly a lot riskier if you don't know the proper timing of events which can lead to user-error. Attempt to do it at your own risk.

EDIT: Ninja'd as usual, nothing to see here

Sounds like you would have to hold down power button as soon as you see the update complete message, and hope that it actually shuts off before the Nintendo message comes up, also I think you would only have one chance of booting to rcm to enable autorcm

--------------------- MERGED ---------------------------

can help show you the timing

 

[Draxzelex]

Sounds like you would have to hold down power button as soon as you see the update complete message, and hope that it actually shuts off before the Nintendo message comes up, also I think you would only have one chance of booting to rcm to enable autorcm

--------------------- MERGED ---------------------------

can help show you the timing

Like I said, you are free to try it and no one will stop you. In theory, it definitely involves less steps than the other method but you sacrifice a lot of the guarantee of messing up for convenience. If (and I'm knocking on wood really hard here) it does not work out, at least don't hold us accountable and we won't say we told you so.

 

[dgr1592]

How to live without breathing?

 

[quantumboy]

GOOD NEWS! I can confirm that you can update through system settings here is what you need to do (and after I Can explain how i "safely tested this before doing it"
0.backup nand and boot and store on pc
1. have your sx dongle plugged in, as well as the rcm jig
2. boot up
3. go to system settings and start update
4. This is key watch closely, as soon as the update is done (or just before) hold VOL +
* you don't need to hold power just vol +
5. the system will auto reboot and due to jig and VOL+ it will go into rcm despite not pressing power (cool right)
6. when sx menu comes up reinstall rcm autoboot
7. boot fcfw

You should now have 5.1 or whatever you just updated to with auto rcm protecting you and fuses intact. I compared my fuses using other payload to be sure.

oh so how I figured this out:
I disabled rcm autoboot, and tested to make sure it wasn't there
then while powered up I put the jib and sx pro widget in, and held power button till power menu came up and I clicked restart and immediately held vol+ and the sx menu booted up, basically proving the power button was not necessary and that all that was needed was vol+ (and pin 10 grounded) at start up or even restart. Not only that I tested this with a charger too. YOu know how when you plug in a powered off switch it turns on, so I tried it with jig and plugged into my computer while holding vol + then with tegra rcm smash loaded a payload and it worked (no power button necessary)

 

[linuxares]

GOOD NEWS! I can confirm that you can update through system settings here is what you need to do (and after I Can explain how i "safely tested this before doing it"
0.backup nand and boot and store on pc
1. have your sx dongle plugged in, as well as the rcm jig
2. boot up
3. go to system settings and start update
4. This is key watch closely, as soon as the update is done (or just before) hold VOL +
* you don't need to hold power just vol +
5. the system will auto reboot and due to jig and VOL+ it will go into rcm despite not pressing power (cool right)
6. when sx menu comes up reinstall rcm autoboot
7. boot fcfw

You should now have 5.1 or whatever you just updated to with auto rcm protecting you and fuses intact. I compared my fuses using other payload to be sure.

oh so how I figured this out:
I disabled rcm autoboot, and tested to make sure it wasn't there
then while powered up I put the jib and sx pro widget in, and held power button till power menu came up and I clicked restart and immediately held vol+ and the sx menu booted up, basically proving the power button was not necessary and that all that was needed was vol+ (and pin 10 grounded) at start up or even restart. Not only that I tested this with a charger too. YOu know how when you plug in a powered off switch it turns on, so I tried it with jig and plugged into my computer while holding vol + then with tegra rcm smash loaded a payload and it worked (no power button necessary)

So you update with SXOS running? I always thought this would work since 1.2 it should stop fuses from popping. So it's confirmed then, it seems easier but at the same time risker.

 

[Draxzelex]

GOOD NEWS! I can confirm that you can update through system settings here is what you need to do (and after I Can explain how i "safely tested this before doing it"
0.backup nand and boot and store on pc
1. have your sx dongle plugged in, as well as the rcm jig
2. boot up
3. go to system settings and start update
4. This is key watch closely, as soon as the update is done (or just before) hold VOL +
* you don't need to hold power just vol +
5. the system will auto reboot and due to jig and VOL+ it will go into rcm despite not pressing power (cool right)
6. when sx menu comes up reinstall rcm autoboot
7. boot fcfw

You should now have 5.1 or whatever you just updated to with auto rcm protecting you and fuses intact. I compared my fuses using other payload to be sure.

oh so how I figured this out:
I disabled rcm autoboot, and tested to make sure it wasn't there
then while powered up I put the jib and sx pro widget in, and held power button till power menu came up and I clicked restart and immediately held vol+ and the sx menu booted up, basically proving the power button was not necessary and that all that was needed was vol+ (and pin 10 grounded) at start up or even restart. Not only that I tested this with a charger too. YOu know how when you plug in a powered off switch it turns on, so I tried it with jig and plugged into my computer while holding vol + then with tegra rcm smash loaded a payload and it worked (no power button necessary)

This would always work in theory but I guess few, if none, have actually tried updating this way or at the very least outlining the appropriate steps. Just some things I wanted to touch on:

• The reason you don't need to press the power button after the system reboots once it is done installing the system update is because, well, it pressed the power button for you. Can't exactly boot into RCM if the console is off. Holding volume + is still required though as this is what determines whether or not the console will enter RCM (along with pin 10 being shorted)
• This goes to show how well made the TX jigs really are so they may be useful for those who wish to update this way, but the drawback is they are behind a $40 paywall whereas most other jigs are much cheaper. The success of this update hinged on how well their jig can short pin 10 so any jig/hardmod that can tout an equivalent success rate can be substituted
• The dongle is the least necessary step in all this as the console will stay in RCM until you manually shut it down or send a payload. The ironic thing is that based off what I just said about the TX jig, you will already have the dongle if you are attempting it with their jig. This makes this whole point more or less moot

As a final check, not that I have any reason to distrust you, but I recommend running briccmii V2 in order to check that no fuses were burnt at all. If the number of fuses burnt is less than 6, than you updated correctly.

 

[linuxares]

This would always work in theory but I guess few, if none, have actually tried updating this way or at the very least outlining the appropriate steps. Just some things I wanted to touch on:

• The reason you don't need to press the power button after the system reboots once it is done installing the system update is because, well, it pressed the power button for you. Can't exactly boot into RCM if the console is off. Holding volume + is still required though as this is what determines whether or not the console will enter RCM (along with pin 10 being shorted)
• This goes to show how well made the TX jigs really are so they may be useful for those who wish to update this way, but the drawback is they are behind a $40 paywall whereas most other jigs are much cheaper. The success of this update hinged on how well their jig can short pin 10 so any jig/hardmod that can tout an equivalent success rate can be substituted
• The dongle is the least necessary step in all this as the console will stay in RCM until you manually shut it down or send a payload. The ironic thing is that based off what I just said about the TX jig, you will already have the dongle if you are attempting it with their jig. This makes this whole point more or less moot

As a final check, not that I have any reason to distrust you, but I recommend running briccmii V2 in order to check that no fuses were burnt at all. If the number of fuses burnt is less than 6, than you updated correctly.

I should give it a try to be honest, but then I would rather buy a third switch to try it on.

 

[sgt_bug]

Can we update using the bundled system update in game carts (or their backup XCI) when in SX OS?