Hacking Update CFW with no issues when RCM off

[Sarek]

Got a 6.2.0 Switch and running RCM mode with Atmosphere fine with Hekate payload injection. Got the "old" games working, but want to play the new games (offline) which needs higher firmware. Want to keep the stock firmware and only update CFW.

Really need to have Auto-RCM off, and the reason for this i I previously had a Switch that had a faulty USB port, which made it impossible to inject payload. It was stuck in Auto-RCM. So this other Switch I will never put in auto-RCM.

What are my options here to safely update CFW firmware and still be able to boot up the stock firmware (sysnand) without any issues like burning fuses etc.
I keep the Switch always offline (airplane mode).

Many thx!

 

[Lacius]

First, AutoRCM is relatively safe, and I recommend it.

If AutoRCM is out of the question, then you need to setup an emuNAND that you can update while leaving your sysNAND low.

Alternatively, if you don't mind burning fuses, you can just update your sysNAND to 9.0.1. if you don't mind using fusee gelee forever, fuses aren't that important.

 

[Sarek]

First, AutoRCM is relatively safe, and I recommend it.

If AutoRCM is out of the question, then you need to setup an emuNAND that you can update while leaving your sysNAND low.

Alternatively, if you don't mind burning fuses, you can just update your sysNAND to 9.0.1. if you don't mind using fusee gelee forever, fuses aren't that important.

Thank you for quick reply.
I would prefer to go the first route you mention with low sysNAND and updated emuNAND. So there is more options in the future for other exploits.

But if I go this route, what will happen if I boot into sysNAND for any reason. Will it recognize the emuNAND fw and "punish" me, ie burn fuses or even brick? or are they completely separate from each other?

 

[NotACat]

Thank you for quick reply.
I would prefer to go the first route you mention with low sysNAND and updated emuNAND. So there is more options in the future for other exploits.

But if I go this route, what will happen if I boot into sysNAND for any reason. Will it recognize the emuNAND fw and "punish" me, ie burn fuses or even brick? or are they completely separate from each other?

From my knowledge, Emunand is on SD card and completely seperate from your sysnand. Your sysnand won't do anything like that, but nintendo might have a method to detect if you have those folders for hacking like "switch", "atmosphere", "emummc"....
I have a SD for playing on sysnand legitimately, and have emunand on another SD for overclock, howbrews, mod.... stuffs

 

[lolz5521]

same exact situation as me, i turn off autoRCM enabled from choidujour, but after reboot it just take me directly to hekate instead. is this normal? not that I'm complaining though

 

[Lacius]

Thank you for quick reply.
I would prefer to go the first route you mention with low sysNAND and updated emuNAND. So there is more options in the future for other exploits.

But if I go this route, what will happen if I boot into sysNAND for any reason. Will it recognize the emuNAND fw and "punish" me, ie burn fuses or even brick? or are they completely separate from each other?

emuNAND and sysNAND are completely separate. Booting one will not affect the other, and there is no risk of burning fuses unless you update your sysNAND without installing AutoRCM.

same exact situation as me, i turn off autoRCM enabled from choidujour, but after reboot it just take me directly to hekate instead. is this normal? not that I'm complaining though

Depending on which CFW you're using, rebooting will take you to an RCM payload instead of truly rebooting the system, which is by design. If you power the Switch off and then on, it should boot normally if you don't have AutoRCM installed.

 

[Sarek]

From my knowledge, Emunand is on SD card and completely seperate from your sysnand. Your sysnand won't do anything like that, but nintendo might have a method to detect if you have those folders for hacking like "switch", "atmosphere", "emummc"....
I have a SD for playing on sysnand legitimately, and have emunand on another SD for overclock, howbrews, mod.... stuffs

OK thanks. It is much clearer now

 

[Sarek]

First, AutoRCM is relatively safe, and I recommend it.

If AutoRCM is out of the question, then you need to setup an emuNAND that you can update while leaving your sysNAND low.

Alternatively, if you don't mind burning fuses, you can just update your sysNAND to 9.0.1. if you don't mind using fusee gelee forever, fuses aren't that important.

I might actually go on the second route you mentioned. Easier than setting up a emuNAND it feels. Also it is not a really big problem to use fusee gelee forever.

What is the best and safest way to update sysNAND to 9.0.1?
Guess it is not safe to go online and update from Nintendo servers?
Is my only option to update sysNAND by booting up Atmosphere/Kosmos and use ChoiDujourNX?

 

[Lacius]

I might actually go on the second route you mentioned. Easier than setting up a emuNAND it feels. Also it is not a really big problem to use fusee gelee forever.

What is the best and safest way to update sysNAND to 9.0.1?
Guess it is not safe to go online and update from Nintendo servers?
Is my only option to update sysNAND by booting up Atmosphere/Kosmos and use ChoiDujourNX?

If you don't care about online play or fuses, then there's no real use for emuNAND. Update your sysNAND to 9.0.1 using ChoiDujourNX. Make sure you disable the AutoRCM option if you don't want it.

 

[Sarek]

If you don't care about online play or fuses, then there's no real use for emuNAND. Update your sysNAND to 9.0.1 using ChoiDujourNX. Make sure you disable the AutoRCM option if you don't want it.

And after updating like mentioned, I might once in a while boot into normal mode (not via exploit). Will only fuses be burnt? no other issues?

 

[Lacius]

And after updating like mentioned, I might once in a while boot into normal mode (not via exploit). Will only fuses be burnt? no other issues?

If you boot normally without CFW and without AutoRCM installed, you will burn fuses. Other than that, there should be no issues.

 

[Sarek]

If you boot normally without CFW and without AutoRCM installed, you will burn fuses. Other than that, there should be no issues.

OK, thx for making that clear.