emuMMC is forced but not enabled | Update Kosmos 16.1 (2024)

Hi,
after Kosmos Update (15.2 to 16.1) I can't boot with the hekate launch option "CFW (EMUMMC)". I get the error:

emuMMC is forced but not enabled!
Failed to launch HOS!
Press any key..

I have always used "CFW (EMUMMC)" to launch. I never created an emuMMC. So the emuMMC is always been disabled und it used eMMC for boot.

What should I do to get this working again?

Thanks in advance!

If you don't use EmuMMC you have to use CFW (SYSNAND). You're missing sigpatches, just install both zips from this thread: https://gbatemp.net/threads/latest-fs-and-acid-patches-for-kosmos.562915/

Dragongray said:

thanks for your reply but that doesn't solve this problem.
How can it be that I can't use CFW (EMUMMC) anymore. I always used it before the update :/

Click to expand...

It now uses a new function in hekate (emummcforce) so you cannot accidentally boot into sysnand. you can read about it here https://github.com/CTCaer/hekate/blob/master/README.md#boot-entry-keyvalue-combinations

oh man, that's it! Thank you very much!

It worked for me to set emummcforce=1 to emummcforce=0. So it don't cause an error because of no emummc.ini.
I think my setup is not recommended but it works again.

tom2199 said:

No problem, but why don't you start with CFW (SysNAND)? It is the same thing afterall, so if it works for you go for it I just don't quite understand why.

Click to expand...

You generally dont want to boot in sysnand(cfw) to avoid getting your sysnand "dirty", so if eventually you want to legally play online with your sysnand partition you have less to worry about

Garant said:

You generally dont want to boot in sysnand(cfw) to avoid getting your sysnand "dirty", so if eventually you want to legally play online with your sysnand partition you have less to worry about

Click to expand...

If it's not starting with emummcforce then you have no emunand

SupaSmashBrotha said:

These other ****** are no help.

Boot hekate like you usually would, and click on CFW (SYSNAND). after you boot in to the switch homescreen, highlight album, and when you click it, hold the "A" button

Click to expand...

What would that accomplish?

Dragongray said:

oh man, that's it! Thank you very much!

It worked for me to set emummcforce=1 to emummcforce=0. So it don't cause an error because of no emummc.ini.
I think my setup is not recommended but it works again.

Click to expand...

Hi, I'm encountering a similar error as you. Can you please clarify for me how you set emummcforce=0? Whereabouts can you change that setting?
Thanks.

Edit: I figured it out with a bit of googling - just writing it down here in case it helps someone else.
I made the change manually in the file hekate_ipl.ini within the bootloader directory.
I can now boot into emummc like I used to. I don't know if this is now no longer recommended, but at least it's functional again.
Now if I could only get into the Homebrew menu I'd be able to change update the firmware which is what I set out to do in the first place!

NoAds said:

kantaroo thanks for the help, but I tried your methods and they don't work for me. When I change the hekate_ipl.ini within the bootloader directory, to emummcforce=1 to emummcforce=0. It just sends me back to the hekate menu. Please me with my issue. Thanks.

Click to expand...

I'm sorry to say I don't know much more than what I posted; it was a bit of trial and error for me as I'm not a real expert on these things. In fact I have just realised that some of my games do not work (but oddly, most do) after I upgraded. I've summed up my misadventures in this post in case it helps anyone:
https://gbatemp.net/threads/firmware-upgrade-problem-emummc-is-forced-but-not-enabled.567385/

Perhaps you should post in this thread that seems well populated with knowledgeable people, sorry I can't help more myself:
https://gbatemp.net/threads/switch-noob-paradise-ask-questions-here.488277/