Updating never burns efuses.Thanks to Caffeine, I managed to jailbreak my 4.0.0 Switch, and created an emummc. If I update the emummc, do the efuses get burned?
Do as @lordelan suggested above.Updating never burns efuses.
What does is the reboot after the update that boots into Nintendo's bootloader (right before Horizon boots up).
And that bootloader checks (and in case burns) fuses.
Long story short -> if you're always booting the EmuMMC through hekate you won't burn fuses (as hekate replaces the bootloader from Nintendo).
However, if you update via ChoiDujourNX be sure to uncheck the "enable AutoRCM" option or you end up bricked on an ipatched unit!
NEVER activate AutoRCM there!
If you didn't understand everything I wrote, rather keep asking instead of trying something. Ipatched Switches can be bricked easily by messing around.
What is usually suggested is to use a dark theme on emunand, and a white theme on sysnand (or the other way around). Then you know right away if you're in sysnand or not.How could one know that he is in emummc not sysnand when booted to cfw
That doesn't work for me. I set the white theme in emummc. But it is white in sysnand after rebooting to it. Now i don't know if i'm in sysnand or emunand.What is usually suggested is to use a dark theme on emunand, and a white theme on sysnand (or the other way around). Then you know right away if you're in sysnand or not.
That doesn't work for me. I set the white theme in emummc. But it is white in sysnand after rebooting to it. Now i don't know if i'm in sysnand or emunand.
This is not an indicator for emunand.It shows me 8.1.0 (AMS 0.9.2) so i know i'm on Atmosphere
The new version of choidujoirNX 1.0.2 has a built in option BY DEFAULT it DISABLE the AUTO RCM feature for iPatched switch.
But while upgrading any cfw we should pay close attention to these small details.
I do have iPatched switch with OFW 4.1.0 on which I used pegascape Web exploit to launch HEKATE.....
Through Hekate i created a emuMMC partition ( separate partition not the SD FILES )...And I have updated that emuMMC to 8.1.0 with the help of choidujoirNX)
Separate guides are available on choidjoirNX process of upgrading the fw.
So finally I have iPatched switch with synand at 4.1.0 and emuMMC at 8.1.0(and 0.92)
Till date nobody clarifies these things for noon like me.
You have no understanding on how the switch's bootloader worksyes it will, preventing burn efuses because you dont use RCM mode
Caffeine
Deja vu
The new version of choidujoirNX 1.0.2 has a built in option BY DEFAULT it DISABLE the AUTO RCM feature for iPatched switch.
But while upgrading any cfw we should pay close attention to these small details.
I do have iPatched switch with OFW 4.1.0 on which I used pegascape Web exploit to launch HEKATE.....
Through Hekate i created a emuMMC partition ( separate partition not the SD FILES )...And I have updated that emuMMC to 8.1.0 with the help of choidujoirNX)
Separate guides are available on choidjoirNX process of upgrading the fw.
So finally I have iPatched switch with synand at 4.1.0 and emuMMC at 8.1.0(and 0.92)
Till date nobody clarifies these things for noon like me.