Hacking Question SuperNag got me... What should I do now?

[Creatable]

I don't understand. The whole point of choidujour is to update your console without burning fuses and utilize autorcm to prevent stepping into official horizon. By returning to your former firmware, no fuses should be burned.

But updating your switch sometimes burns a fuse. In this case, a fuse was burnt when he updated, so now if he goes back with said burnt fuse, he'll have to boot into RCM to boot into the Switch OS (Horizon.) as the burnt fuse is detected by the console.
Hekate bypasses the detection, however, it does not autoboot with the console or remove the detection entirely. As soon as you use it and shut down, you have to use it again.
Using choi is pointless if the firmware you're going to has its fuse burnt via a system update.

 

[Pluupy]

But updating your switch sometimes burns a fuse. In this case, a fuse was burnt when he updated, so now if he goes back with said burnt fuse, he'll have to boot into RCM to boot into the Switch OS (Horizon.) as the burnt fuse is detected by the console.

Like I said, the whole point of choidujour is to update without burning fuses. It is literally the automated version of rajkosto's no-fuse-burning guide.

The idea behind downgrading is when you return to the former firmware, you console won't realize it was running a higher firmware because the fuse count is the same, even if in official horizon.

I've never hear of anyone burning "a fuse". The way the fuse system works isn't like that. Every update has a specific number of fuses relevant to them.

https://switchbrew.org/index.php?title=Fuses#Anti-downgrade

 

[Canna]

I was spamming "A" and fell victim to the SuperNag.

Now I'm part of the 5.1 club. The annoying SuperNag got me and I accidentally hit the update button. I don't know if I should be happy or sad right now that I lost 4.1.0 stock firmware. I guess the plus side is that I can finally play games larger than 4GB since I can use exFAT now.

No idea how it updated when I was on Airplane mode with my Wifi settings already deleted... sigh

Does anyone here know if the SuperNag issue will be gone forever now that I accidentally updated to 5.1? Like if a new update higher than 5.1 comes, will the SuperNag return? I'm so scared to accidentally update again if SuperNag returns.

It updated from a 5.1 update game.. by legit game cart he means you ever used a legit game cart in your system with a update of 5.1 on it or you run a backup with the update 5.1 still in that. Nevermind your on latest not much you can do now.
No point rolling back system update pointless really, can be done but need non stock bootloader to run everytime in order to boot downgraded os..

I don't understand. The whole point of choidujour is to update your console without burning fuses and utilize autorcm to prevent stepping into official horizon. By returning to your former firmware, no fuses should be burned.

Yes your right..
You may downgrade to any firmware /system version with choidujournx but you must use hekate non stock bootloader to boot,
When you update normally you burn fuses,once they are burned theres no way to unburn them bring them back. If you try boot older system with the wrong fuse count it will panic or error or just lock up,Im sure you know this and are just replying. but anyway...

 

[Mr. Wizard]

Like I said, the whole point of choidujour is to update without burning fuses. It is literally the automated version of rajkosto's no-fuse-burning guide.

The idea behind downgrading is when you return to the former firmware, you console won't realize it was running a higher firmware because the fuse count is the same, even if in official horizon.

I've never hear of anyone burning "a fuse". The way the fuse system works isn't like that. Every update has a specific number of fuses relevant to them.

https://switchbrew.org/index.php?title=Fuses#Anti-downgrade

You seem to be confused. He updated and then rebooted into the original bootloader, not hekate, not sxos, therefore poof. BBQ.

And you don't even need to use choidujour, you can just update normally as long as you manage to enter RCM after the the first reboot. It's tricky and many people have fucked up, but it's a valid way of updating without burning fuses if you can manage it.

 

[Pluupy]

You seem to be confused. He updated and then rebooted into the original bootloader, not hekate, not sxos, therefore poof. BBQ.

And you don't even need to use choidujour, you can just update normally as long as you manage to enter RCM after the the first reboot. It's tricky and many people have fucked up, but it's a valid way of updating without burning fuses if you can manage it.

I was not confused about OP's situation. I was confused why Curate said that choidujour was claimed to "sometimes burn a fuse" and didn't realize they were still talking about OP and not choidujour as a whole.

 

[The Real Jdbye]

I was spamming "A" and fell victim to the SuperNag.

Now I'm part of the 5.1 club. The annoying SuperNag got me and I accidentally hit the update button. I don't know if I should be happy or sad right now that I lost 4.1.0 stock firmware. I guess the plus side is that I can finally play games larger than 4GB since I can use exFAT now.

No idea how it updated when I was on Airplane mode with my Wifi settings already deleted... sigh

Does anyone here know if the SuperNag issue will be gone forever now that I accidentally updated to 5.1? Like if a new update higher than 5.1 comes, will the SuperNag return? I'm so scared to accidentally update again if SuperNag returns.

It must have had the update downloaded before you went into airplane mode.
As long as it stays offline the supernag should not return I think. Maybe trying to load a game that needs newer FW can trigger the supernag, not sure.
But you can still use RCM at least, all you're really losing out on is a confirmed warmboot solution that we have no idea when will be released, and we will likely get warmboot solutions for newer firmwares at some point anyway.

Instructions unclear. I forcefully inserted my switch into my PS4 and now neither are powering on.

You have to disassemble the PS4 so you can access the mainboard, place the Switch on top, then get your Switch into RCM and inject a CFW payload and it will be wirelessly transferred to your PS4 so you can play Switch roms on your PS4.

 

[Bellebite2000]

But updating your switch sometimes burns a fuse. In this case, a fuse was burnt when he updated, so now if he goes back with said burnt fuse, he'll have to boot into RCM to boot into the Switch OS (Horizon.) as the burnt fuse is detected by the console.
Hekate bypasses the detection, however, it does not autoboot with the console or remove the detection entirely. As soon as you use it and shut down, you have to use it again.
Using choi is pointless if the firmware you're going to has its fuse burnt via a system update.

"I don't burn fuses, because I am cool and 733T". Who cares about fuses, seriously... Update to 5.1, get a SX OS, and enjoy all the Switch games and homebrew... Case closed. Put your switch into sleep mode, and you will never have to worry about cold / warm / half hot boot.

 

[Mr. Wizard]

Put your switch into sleep mode, and you will never have to worry about cold / warm / half hot boot.

Every time I want to transfer something to my switch I have to reboot it since ftpd nukes shit. So ya I would say warm/cold boot would be convenient but since it's highly improbable to show up anytime soon, fuck it.