Help needed: sysMMC (with AMS) loading instead of emuMMC!

striser

Member
OP
Newcomer
Joined
Mar 7, 2020
Messages
9
Trophies
0
Age
46
XP
226
Country
Italy
Hi, I have a 2 emuMMC setup that has worked flawlessly for ages (I use the first emuMMC as the main one, and the second to test things).

I just updated everything to the latest version (system 13.0.0, Hekate 5.6.3., Atmosphere 1.1.1), and now, everytime I try lo load my second emuMMC it starts sysMMC (with Atmosphere) instead!

I already tried to do a clean install on another SD card, but nothing changes: the first emuMMC loads just fine, but instead of the the second one it keeps loading sysMMC (not stock but with AMS).

Any ideas about what's happening and how to fix it?
 

Draxzelex

Well-Known Member
Member
Joined
Aug 6, 2017
Messages
16,635
Trophies
1
Age
27
Location
New York City
XP
11,216
Country
United States
Hi, I have a 2 emuMMC setup that has worked flawlessly for ages (I use the first emuMMC as the main one, and the second to test things).

I just updated everything to the latest version (system 13.0.0, Hekate 5.6.3., Atmosphere 1.1.1), and now, everytime I try lo load my second emuMMC it starts sysMMC (with Atmosphere) instead!

I already tried to do a clean install on another SD card, but nothing changes: the first emuMMC loads just fine, but instead of the the second one it keeps loading sysMMC (not stock but with AMS).

Any ideas about what's happening and how to fix it?
Post your Hekate_ip.ini file
 

striser

Member
OP
Newcomer
Joined
Mar 7, 2020
Messages
9
Trophies
0
Age
46
XP
226
Country
Italy
Post your Hekate_ip.ini file
[config] autoboot=0 autoboot_list=0 bootwait=3 backlight=100 autohosoff=0 autonogc=1 updater2p=0 bootprotect=0 {------ Atmosphere ------} [Atmosphere CFW] payload=bootloader/payloads/fusee.bin icon=bootloader/res/icon_payload.bmp {-------- Stock ---------} ["Stock" SYSMMC] fss0=atmosphere/package3 stock=1 emummc_force_disable=1 icon=bootloader/res/icon_switch.bmp

No matter what I do, whenever I try to boot my second emummc (first one is ok!), it keeps loading my sysmmc with atmosphere.
I even tried to start fresh for a few times, and I still keep getting that error.
Please note that if I set up just one emummc it works correctly, but as soon as I reformat the SD card (using hekate/nyx built-in tool) with two emummc partitions, the previously working emummc goes in the second spot and stops to be loaded.
 

toroloco

Member
Newcomer
Joined
Oct 2, 2020
Messages
10
Trophies
0
Age
35
XP
44
Country
Mexico
try this :
[config] autoboot=0 autoboot_list=0 bootwait=0 autohosoff=0 autonogc=1 updater2p=1 backlight=100 [CFW - emuMMC] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 atmosphere=1 icon=bootloader/res/icon_payload.bmp [Stock - sysMMC] fss0=atmosphere/package3 emummc_force_disable=1 stock=1 icon=bootloader/res/icon_switch.bmp
 

striser

Member
OP
Newcomer
Joined
Mar 7, 2020
Messages
9
Trophies
0
Age
46
XP
226
Country
Italy
try this :
[config] autoboot=0 autoboot_list=0 bootwait=0 autohosoff=0 autonogc=1 updater2p=1 backlight=100 [CFW - emuMMC] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 atmosphere=1 icon=bootloader/res/icon_payload.bmp [Stock - sysMMC] fss0=atmosphere/package3 emummc_force_disable=1 stock=1 icon=bootloader/res/icon_switch.bmp
I didn't had time to touch my switch lately, but today I updated everything to the latest available version, and now my second emummc works again (without changing Hekate_ip.ini).
 
General chit-chat
Help Users
    Ophelia_Later @ Ophelia_Later: i agree tho there is some pretty revolting porn out there