Hacking CFW Update: SysCFW vs EmuCFW

[Olat]

Hello!

I have a lot of experience with modded consoles, but I am fairly new to the Switch modding scene and the Switch in general.

My Switch HAC -001(-01) has a modchip and I wanted to update it to the latest version of Atmosphere, Hekate and firmware version 18.1.0. I was on the previous versions of all of these, so it was not an ancient one.
I did so yesterday and my Switch works great. Now, I only updated the EmuCFW through Daybreak, but I didn't update SysCFW or the official firmware at all since I never use those. Will this cause troubles in the future for me? If so, what is my best option to update these now that EmuCFW is already on AMS 17.0.1, Hekate 6.2.1 and HOS 18.1.0? I would be glad if I don't have to change anything, but I'm open to suggestions from more experienced people here.

Also, I did not update fusee.bin as https://switch.hacks.guide/ didn't mention that. Do I need to update it, too? If so, is it a simple copy-paste to the correct location?

Finally, do I need to update sigpatches, if that's still a thing? All the games I tried load without issues, but I did read somewhere that sigpatches are no longer the recommended way forward, but rather syspatch.

Let me know if I can provide any further information.

Thanks in advance!

 

[Djakku]

Sigpatches are necessary if you run unsighed NSP like forwarded or converted XCI to NSP backup.
There is also a sys-patch module that does the patching and It might be what you refer to.

But since you're seem to have an clear idea of what you're doing the short answer is
as long as atmosphere and hekate are updated and support the latest firmware, and you are using daybreak to update your Emulated firmware, you're doing the right thing.

Ensure that if you have any other sys-modules installed, that they are compatible with the firmware that you want to update to.

and I would also always update fusee.bin when a new atmosphere releases.

 

[Olat]

Sigpatches are necessary if you run unsighed NSP like forwarded or converted XCI to NSP backup.
There is also a sys-patch module that does the patching and It might be what you refer to.

But since you're seem to have an clear idea of what you're doing the short answer is
as long as atmosphere and hekate are updated and support the latest firmware, and you are using daybreak to update your Emulated firmware, you're doing the right thing.

Ensure that if you have any other sys-modules installed, that they are compatible with the firmware that you want to update to.

and I would also always update fusee.bin when a new atmosphere releases.

Thanks for the update! If I make the update through EMUMMC will that also update the SYSMMC version of the software or do I need to do that separately? Thanks!

 

[Djakku]

The software that you put in the SD card won't be read by the SYSMMC if you boot it without a bootloader like hetake.
So technically it will NOT affect your system NAND and firmware.
If you boot the SYSMMC you should be on an older firmware version - which is whichever firmware it was when you initially made your emunand.

The difference between using daybreak as update tool versus the official nintendo method has to do with the FUSES for the gamecard reader and some other things that I'm not 100% sure about so won't waffle.
When those fuses are blown ( which is intended between FW upgrade ) you won't be able to downgrade.
you can't use the gamecard slot as there will be a fuse missmatch. (that's why there a NOGC option for Hekate)

EMUMMC and SYSMMC should not conflict anyway as most of the time.
When atmosphere or other tools recieve update, they ensure that they will be working with older firmware veriso - unless it's stated otherwise.

 

[Olat]

That makes perfect sense. I appreciate your help, friend!

 

[Djakku]

That makes perfect sense. I appreciate your help, friend!

No worries!

 

[miniadri]

Hi, @Djakku i've reviewed the topic as i had one problem with my SysNAND and i create a emuMMC (i haven't had one), now i get working my SysNAND again so, it's neccesary or is better have both or having only sysnand is enough?

 

[Djakku]

I would highly suggest to get the emummc working if you're going to mess around nsp files and install homebrew titles as otherwise you will taste Nintendo's wrath and ban hammer

Post automatically merged: Oct 8, 2024

If you have created your emunand, on hekate, you need to enable it.

 

[Hayato213]

Hi, @Djakku i've reviewed the topic as i had one problem with my SysNAND and i create a emuMMC (i haven't had one), now i get working my SysNAND again so, it's neccesary or is better have both or having only sysnand is enough?

If you got a clean NAND then use an emunand, if you have no interest in playing online then sysnand CFW is fine, just keep a NAND backup around.

 

[miniadri]

I would highly suggest to get the emummc working if you're going to mess around nsp files and install homebrew titles as otherwise you will taste Nintendo's wrath and ban hammer

Post automatically merged: Oct 8, 2024

If you have created your emunand, on hekate, you need to enable it.

i always have use sysnand without problems until now (i got crashes because of the WiFi, mitm, 90dns and so on...) but for the other things all ok. And about Nintndo ban hammer... i was victim of them so long ago so i have no problem with this.

If you got a clean NAND then use an emunand, if you have no interest in playing online then sysnand CFW is fine, just keep a NAND backup around.

So i can keep this emummc like backup or is better to do a NAND from SX Core/Hekate?

 

[Hayato213]

i always have use sysnand without problems until now (i got crashes because of the WiFi, mitm, 90dns and so on...) but for the other things all ok. And about Nintndo ban hammer... i was victim of them so long ago so i have no problem with this.

So i can keep this emummc like backup or is better to do a NAND from SX Core/Hekate?

You can use Sysnand if you are already banned, you can figure out what is causing your crashes to use your sysnand. As for backup use Hekate.

 

[dragonz]

Edit- I asked in the noob thread.