Hacking Can I update emummc of an IPATCHed Switch?

[alevan]

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?

 

[lordelan]

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?

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.

 

[NoNAND]

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.

Do as @lordelan suggested above.
Still you should proceed with caution. ipatched switches are a bit tricky.
While updating ensure your switch has enough battery left. if not charge it beforehand and get around to updating it later on.

 

[Rimaahkehs]

How could one know that he is in emummc not sysnand when booted to cfw

 

[Dust2dust]

How could one know that he is in emummc not sysnand when booted to cfw

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.

 

[alevan]

Thank you.

 

[BaamAlex]

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.

 

[Sayern]

I don't have an ipatched switch but if you boot on emummc with a CFW you can check in main menu Options > Console > Version
It shows me 8.1.0 (AMS 0.9.2) so i know i'm on Atmosphere

 

[sharkie545]

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.

Then change one of the themes to a different color lol. I do this it works easy to differentiate between stock and cfw.

 

[BaamAlex]

It shows me 8.1.0 (AMS 0.9.2) so i know i'm on Atmosphere

This is not an indicator for emunand.

 

[darshangkolhe]

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.

 

[Shololo]

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.

Help brother on how you did this i also want to do the same i have a patched switch on 4.1.0

 

[Deleted User]

yes it will, preventing burn efuses because you dont use RCM mode

 

[Idontknowwhattoputhere]

yes it will, preventing burn efuses because you dont use RCM mode

You have no understanding on how the switch's bootloader works
Deja vu reboots to a payload of choice for example hekate
Hekate won't burn fuses dumbass

 

[Deleted User]

Caffeine

Deja vu

 

[Idontknowwhattoputhere]

Caffeine is just a implementation of deja vu

 

[2pacsawyer]

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.

Thank you for this. I've searched so many forums and websites for the past few weeks trying to find someone that has actually done this instead of someone without and ipatched switch just saying it should work. I was nervous that even if I upgraded the emuMMC firmware that somehow when the sysNAND booted up it would know that an update occurred and would refuse to boot. obviously, without booting into the sysNAND you wouldn't be able to launch the payload and boot into CFW or emuMMC