Hacking Question et another EmuMMC firmware update thread ... Updating EmuMMC while retaining SysNAND

[level42]

I have a switch on Firmware 3.0.0

I installed Atmosphere 0.9.4 and EmuMMC on a SD partition.

Question:

Can I simply boot the EmuMMC and run the factory firmware update? What would this do to my SysNAND, or Fuses?

OR:

Do I have to run ChoiDujourNX to update my EmuMMC?

---

Being new to ChoiDujourNX, is this something I'd have to run and update each time my EmuMMC boots?

 

[The Real Jdbye]

I have a switch on Firmware 3.0.0

I installed Atmosphere 0.9.4 and EmuMMC on a SD partition.

Question:

Can I simply boot the EmuMMC and run the factory firmware update? What would this do to my SysNAND, or Fuses?

OR:

Do I have to run ChoiDujourNX to update my EmuMMC?

---

Being new to ChoiDujourNX, is this something I'd have to run and update each time my EmuMMC boots?

Don't go online on your emuNAND, you have a high chance of getting banned.
Always use ChoiDujourNX. Works the same as a stock firmware update, just offline.

 

[level42]

Don't go online on your emuNAND, you have a high chance of getting banned.
Always use ChoiDujourNX. Works the same as a stock firmware update, just offline.

This is my second switch explicitly for modding

I will check out ChoiDujourNX. Thanks for the tips

 

[The Real Jdbye]

This is my second switch explicitly for modding

I will check out ChoiDujourNX. Thanks for the tips

Still no point in purposely banning yourself when it can be avoided.

 

[level42]

Still no point in purposely banning yourself when it can be avoided.

For sure, hence my initial concern.

Work day has started, so I wont be able to test this until lunch break, but I'll keep you posted.

Thanks again!

 

[level42]

Should I disable autoRCM?

It claims it would burn fuses then, but most of what I've read online says that with EmuMMC, you should disable AutoRCM mode.

 

[Noggerfragger]

AFAIK since you updated emummc fw and the check is done at boot, booting emummc trough hekate should be safe with or without autorcm.

I'm in a similar situation but every time I try updating with choidujour it crashes with the black error window, I'm looking forward to see your results, glhf.

 

[level42]

AFAIK since you updated emummc fw and the check is done at boot, booting emummc trough hekate should be safe with or without autorcm.

I'm in a similar situation but every time I try updating with choidujour it crashes with the black error window, I'm looking forward to see your results, glhf.

So, I simply updated to 9.0.0 and left autoRCM off, allowing it to burn fuses.

The result, my EmuMMC updated to 9.0.0, and my stock firmware remains on 3.0.0

My fuse count, still only shows 3 even after numerous reboot cycles ...

 

[Noggerfragger]

So, I simply updated to 9.0.0 and left autoRCM off, allowing it to burn fuses.

The result, my EmuMMC updated to 9.0.0, and my stock firmware remains on 3.0.0

My fuse count, still only shows 3 even after numerous reboot cycles ...

Very nice, that's because the fuses are burnt during the normale/non-hekate boot process, since the emummc passes from the cfw setup you have that's not a possibility it seems.
For future reference: I solved my problem by avoiding using a forwarder to get into homebrew menu.

 

[SpencerlyEverly]

Okay, I did learn about the other thing about SysNAND, but I'll recap about EmuNAND.

Use the DNS settings to block Nintendo's servers on EmuNAND. Even better, if you're using an NNID on the system, block them on SysNAND, then do RCM injection, and copy the SysNAND to EmuNAND. Haven't had a single ban yet from this.

Now, as for updating EmuMMC. ChoiDujourNX is a tool that can update the firmware without going online. But you need to get the firmware files, and even if it's free to retrieve (And copyright, according to here), I can't spare the details on getting the files.

Then, after copying the folder to your SD Card, use ChoiDujourNX to update the firmware. I might suggest using the ExFAT version, to support that format as well at FAT32.

When you update EmuMMC, it won't burn any fuses, since the MMC backup is not on your internal MMC.

I'm just giving you a recap here, so hopefully you do well updating the firmware!

 

[The Real Jdbye]

So, I simply updated to 9.0.0 and left autoRCM off, allowing it to burn fuses.

The result, my EmuMMC updated to 9.0.0, and my stock firmware remains on 3.0.0

My fuse count, still only shows 3 even after numerous reboot cycles ...

You should patch your emuNAND with this: https://gbatemp.net/threads/incognito_rcm-wipe-personal-information-to-reduce-risk-of-ban.549462/
Then you can safely connect online in homebrew without worrying about a ban