Hacking Confused with all these hacks

[Huntereb]

Unfortunately being on the 3.0.0 bandwagon on my "CFW" switch, there's not many switch games we can play on it right now anyway without updating (HBL and retroarch stuff is fine so I don't confuse OP).

There's no excuse not to update and just enable auto-rcm so that the console cannot start normally and burn fuses. Just don't forget your backup!

 

[Draxzelex]

Thanks for the replies everyone just 1 more question.

Free games isn't really a big deal to me just needed some clarity. If I was to hack and install homebrew and emulators there would be no issue in playing the latest games via cartridge apart from online play?

If you mean without worrying about a ban, then no you are always at risk for a ban the moment you hack your console. Being banned does limit you from online play and accessing the eShop but not game or system updates.

 

[Maximilious]

There's no excuse not to update and just enable auto-rcm so that the console cannot start normally and burn fuses. Just don't forget your backup!

Yes there is. Coldboot potential with emuNAND availability, along with more exploits available on 3.0.0. And fuses are still burnt through auto-rcm. They are only not burnt when using R's lengthy method, and hopefully other methods down the road. TX's update was simply to not burn e-fuses when using that method, not to outright stop burning of e-fuses in general.

Ban or not it would be nice to not use a dongle during boot. Playing 1-2 switch last night with the wife, the game froze on one of the mini games twice requiring a full boot with dongle again.

 

[Huntereb]

Yes there is. Coldboot potential with emuNAND availability, along with more exploits available on 3.0.0. And fuses are still burnt through auto-rcm. They are only not burnt when using R's lengthy method, and hopefully other methods down the road. Ban or not it would be nice to not use a dongle during boot. Playing 1-2 switch last night with the wife, the game froze on one of the mini games twice requiring a full boot with dongle again.

As I mentioned, only launching the system using a RCM payload can avoid burning fuses! You also don't have to update using R's "lengthy" method, you can update the standard way as well without burning fuses. Just make sure you have a jig inserted, and when the device reboots after installing the update, hold Volume up! Then of course apply your auto-RCM and enjoy not having burned your fuses!

Can't disagree about having to launch the system using a payload every time, but it's better than missing out on new releases while waiting for a Warmboot/coldboot solution.

 

[Maximilious]

As I mentioned, only launching the system using a RCM payload can avoid burning fuses!

Do you have any proof this is the case? I haven't read that before but would love to be shown the way.

 

[Huntereb]

Do you have any proof this is the case? I haven't read that before but would love to be shown the way.

Surprised you've missed out on that info! @CTCaer's Hekate will bypass fuse checks, as well as SX if you're feeling brave to proprietary software. Just be sure to launch your Switch using one of them, and never normally. Hence the need for auto-RCM. I'm currently running 5.1 with 5 fuses burned, so I can downgrade back to 4.1 any time I want. Just... Keep a backup.

 

[Draxzelex]

Do you have any proof this is the case? I haven't read that before but would love to be shown the way.

Here is a detailed tutorial on how to perform this: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

 

[Huntereb]

Here is a detailed tutorial on how to perform this: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

Though, this method isn't required if you simply want to update, and not downgrade below a firmware your console has already been on.

 

[Maximilious]

Here is a detailed tutorial on how to perform this: https://gbatemp.net/threads/how-to-...nofficially-without-burning-any-fuses.507461/

Yes, but @Huntereb is stating that method is not needed and Hekate and SX OS support it out of the box. How can we check to see how many fuses we have burned? I'd like some more solid proof before attempting an update on my 3.0.0 unit.

Also this post, but again I'm not sure on validity now:
https://gbatemp.net/threads/can-you-update-with-sx-os-and-not-burn-fuses.510127/

Same principle, as long as it installs from Horizon the fuses get burned since it reboots into the NX bootloader. The only way is to manually insert a update into your own backup and restore it.

And again this post on reddit regarding fuses on the cart reader from an updated 1.0 console:
https://www.reddit.com/r/SwitchHaxi...x_os_will_burn_your_fuses_to_whatever/e101g9i

The caveat is that the cartridge port appears to have its own fuse set. So for those lucky early testers like myself, even though my system is stock 1.0 fw, if I restore it back to stock 1.0 from my current 5.1.0 state...the cartridge port wont work for any games. Its been "upgraded" permanantly to the highest fw I've ran on it. Hopefully rajkosto or someone else will fix this in the future.

I think the main issue is that, yes you can update to 5.1.0 in Horizon right now and your fuse won't get burned if you boot directly into SX OS or Hekate. But the moment you boot back into OFW when the next update arrives, your fuses will be burned by the NXLoader.

 

[morrison22]

There's a ridiculous amount of emulators available. For being so young, the Switch scene is very diverse.

Is there a web page or something that has all the emulators and other homebrew listed and organized? I use switchbrew but it doesn’t appear to update often.

 

[Draxzelex]

Yes, but @Huntereb is stating that method is not needed and Hekate and SX OS support it out of the box. How can we check to see how many fuses we have burned? I'd like some more solid proof before attempting an update on my 3.0.0 unit.

Briccmii V2 can display the current number of fuses burnt

 

[tbb043]

With a switch on 3.0 you can pretty much run all the emulators made/ported for the switch, and there are a lot of emulators for a console with such a young scene, check out the switchbru site for the emulators.

As for backups, yes you can run backups, but most don't save, most don't even work, isn't easy to get them running as it requires a lot of trial and error, you can go the route of piracy only software with team excuter's SX OS, but I don't see a reason why you should go this route because backup loading will be free and easy soon, check out the ReiNX cfw which will be free and apparently include a backup loader.

SOONTM vs the now of SXOS(pro)

 

[Maximilious]

Is there a web page or something that has all the emulators and other homebrew listed and organized? I use switchbrew but it doesn’t appear to update often.

The scene is expanding so quickly is probably why it hasn't been updated as of late. I'd suggest checking this section on the site and just browse for the Release tags https://gbatemp.net/forums/switch-emulation-homebrew-software-projects.292/

As for other site's, there's reddit.com/r/switchhaxing and a few others, but I believe GBATemp is likely the most prominent for Nintendo console's.

 

[gamecaptor]

My personal recommendation is to follow @Plailect guide(s). They are EXCELLENT!

https://switch.hacks.guide/

 

[ScarletDreamz]

My personal recommendation is to follow @Plailect guide(s). They are EXCELLENT!

https://switch.hacks.guide/

They are not up to date with the Switch Scene, as the speed of the scene its almost unreadable, so, for now, this forum is the best bet.

 

[gamecaptor]

They are not up to date with the Switch Scene, as the speed of the scene its almost unreadable, so, for now, this forum is the best bet.

This is true. Honestly I would tell most people to just sit back and wait a little longer. To your point it's evolving/changing so fast that it's only going to get easier/faster the more you wait. That's what I'm doing anyways

 

[Huntereb]

I think the main issue is that, yes you can update to 5.1.0 in Horizon right now and your fuse won't get burned if you boot directly into SX OS or Hekate. But the moment you boot back into OFW when the next update arrives, your fuses will be burned by the NXLoader.

This is exactly the case, I checked my fuse count immediately after updating to confirm it. I cannot stress enough that you must be certain you have made a proper backup, your jig is working properly, and that you hold volume up while it reboots after updating. If either of the latter two are missed, you're SOL.

I'm uncertain the method mentioned in that tutorial post can even be used to update to 5.1. Are there any games currently available that come with such firmware revision?

 

[Draxzelex]

I'm uncertain the method mentioned in that tutorial post can even be used to update to 5.1. Are there any games currently available that come with such firmware revision?

Nope so you either need a friend that has a dump of 5.1 or you pay extra attention to when rajkosto is coughing

 

[Maximilious]

This is exactly the case, I checked my fuse count immediately after updating to confirm it. I cannot stress enough that you must be certain you have made a proper backup, your jig is working properly, and that you hold volume up while it reboots after updating. If either of the latter two are missed, you're SOL.

OK, that's what I thought. So updating via OFW is not an option right now (or possibly ever) because of that problem. I just need to point out your comment that confused me and you may want to edit it for clarity if someone else happens upon it:

As I mentioned, only launching the system using a RCM payload can avoid burning fuses! You also don't have to update using R's "lengthy" method, you can update the standard way as well without burning fuses.

You can update to the latest firmware once and only once without burning any fuses, as long as you boot into RCM (or AutoRCM for safety) every time after that. Once the next update comes out you're SOL unless using Rajkosto's or any new method that arrives.

Unfortunately updating via cart dump is not possible in SX OS yet. If I try to launch a game that requires higher than 3.0.0 I receive a "Game Card could not be read" error instead of being prompted to update the console.

 

[Huntereb]

So updating via OFW is not an option right now (or possibly ever) because of that problem.

Well, it's still technically updating using the Official Firmware, you just have to boot it a different way every time.

You can update to the latest firmware once and only once without burning any fuses, as long as you boot into RCM (or AutoRCM for safety) every time after that. Once the next update comes out you're SOL unless using Rajkosto's or any new method that arrives.

You must be mistaken. You can update as many times as you want using this method. In fact, I plan on doing so as soon as a new firmware update is available. I'll just be certain my jig is working and that I'm holding volume up after the update completes and reboots. What makes you think it can only be performed once?