Hacking After Atmosphere Update Emunand Disappeared?

[sli4]

I'm trying to get Emunand (and sysnand) to show up again after a recent update.

After updating atmosphere and sig patches I tried to launch emunand. The screen blinked at the hekate/sigpatch loading screen and then just went back to the launch menu. If I tried to load again it would just blink and go back to the launch menu without any of the loading screens.
After restarting the switch I was stuck in the black hekate load screen - the one you navigate with the volume buttons (as if i forgot to put my sd card in the Switch)

I had downloaded atmosphere 0.15.0 from /Atmosphere-NX/Atmosphere/releases
and sig patches from /ITotalJustice/patches/releases (the 0.15.0 patches obviously)
Did a drag and drop replace folders with the new atmosphere folders and then copied the sig patches into the atmosphere and bootloader folders (so it does not replace atmosphere and bootloader folders completely)
I also added the new fuse-primary.bin file to the atmosphere folder


I went back and updated Hekate by copying over the latest Hekate files to the bootloader folder from the latest release (CTCaer/hekate/releases) - I can now get into Hekate. First time it started again it asked me to update the clock (not HW clock) and date.

Now - when I click launch there are no options. no emunand, no sysnand - just a message that says " No main boot entries found.. you can use the following entry to boot stock, or use MORE CONFIGS button for more boot entries " and there's nothing there to click. If I check the more configs section there's nothing there but a message saying it does not see any ini files.
Considering I haven't updated since atmosphere 0.8 or 0.9ish is there anything else I'm missing?
Emunand is/was still on firmware 8ish as well. I was going to update that once I got everything loaded.
How can I get it to show emunand again?
Really hoping my emunand data hasn't been lost - The fact that it's not even seeing my system's nand like it usually does gives me hope since that's still fine.

I have no preference staying with hekate as long as I can keep my game data.

 

[sli4]

Update: If I select payloads and launch the fusee-primary.bin payload it automatically runs my emunand and everything seems to work fine (I have not tried playing a game yet)
So, it seems nothing is lost - but why can't I choose my emunand or sysnand from the launch menu anymore?

 

[drfunkenstein2k]

same problem here, with same solution fix

 

[sli4]

same problem here, with same solution fix

There has to be a fix for this. Like it doesn't know to use fusee-pimary on its own because some config is off?
Or what's the connection that's missing to add emunand and sysnand to the launch menu?

 

[HollowGrams]

There has to be a fix for this. Like it doesn't know to use fusee-pimary on its own because some config is off?
Or what's the connection that's missing to add emunand and sysnand to the launch menu?

Most likely cause your .ini

You can autoboot to sys or emummc in options you can set and save.

 

[sli4]

I just installed the latest version of tinfoil and it gave me an error message telling me to delete fsso if i'm using fusee-primary. I said Okay and it confirmed deletion of kosmos. So I remember i did set everything up with kosmos a looong time ago. Could that be the problem? If so, aside from tinfoil deleting it... how to fix?

 

[HollowGrams]

I just installed the latest version of tinfoil and it gave me an error message telling me to delete fsso if i'm using fusee-primary. I said Okay and it confirmed deletion of kosmos. So I remember i did set everything up with kosmos a looong time ago. Could that be the problem? If so, aside from tinfoil deleting it... how to fix?

Nope it deletes for you. Exit then re-enter and works for me.

 

[sli4]

Nope it deletes for you. Exit then re-enter and works for me.

Yeah, continuing seemed fine for tinfoil but I still can't get emunand or sysnand to show up in the launch menu. Seems it might be an ini file issue in the bootloader folder?

also - i tried updating my firmware to 10.2 from 8.x and it gave me the error "failed to get update information, result 0x00234a02"
I don't know if that's related to this.

 

[HollowGrams]

Yeah, continuing seemed fine for tinfoil but I still can't get emunand or sysnand to show up in the launch menu. Seems it might be an ini file issue in the bootloader folder?

also - i tried updating my firmware to 10.2 from 8.x and it gave me the error "failed to get update information, result 0x00234a02"
I don't know if that's related to this.

hekate_ipl.ini

[config]
autoboot=0
autoboot_list=0
bootwait=4
verification=1
backlight=100
autohosoff=0
autonogc=1
updater2p=1


{--- Nintendo Stock ---}
[OFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
stock=1
icon=bootloader/res/ofw.bmp
{}

[Atmosphere (CFW)]
payload=bootloader/payloads/fusee-primary.bin
emummc_force_disable=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/sys_cfw_boot.bmp
{}

{------Atmosphere Emu------}
[Atmosphere (emuMMC)]
payload=bootloader/payloads/fusee-primary.bin
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/emummc_boot.bmp
{}

 

[sli4]

okay - my ini file had nothing but the first config info. i tried this and everything showed up again BUT when i tried to load atmosphere emummc: the screen blinked.. went to a black screen and now it says "fatal error: failed to stat stage2 (atomsphere/fusee-secondary.bin)! press power to reboot"

... i press power and it just gives me the same screen. if i pull the sd card it says it can't initialize the sd...
edit: holding down power for 15 seconds turns it off. So something in that ini file is still not quite right though.

 

[sli4]

while my sig patches seem to work just fine if I manually launch the fusee-primary.bin payload - is it possible there's an issue where it's defaulting to fss0/fusee-secondary (even though your ini says primary for emummc) and therefore crashing because the sig patches I have are for primary?

 

[HollowGrams]

while my sig patches seem to work just fine if I manually launch the fusee-primary.bin payload - is it possible there's an issue where it's defaulting to fss0/fusee-secondary (even though your ini says primary for emummc) and therefore crashing because the sig patches I have are for primary?

Use hekate patches:
https://github.com/ITotalJustice/patches/releases

All working here

 

[sli4]

Turns out the fatal error was because i forgot to put fusee-secondary back where it belongs. I took it out to test something just before trying your ini file.
It's working! Thank you for your help Hologram!

Now if only I can get past this "failed to get update information, result 0x00234a02" when i try to install updated firmware via Daybreak

Tinfoil is also still giving me the error asking me to delete kosmos every time i open it. Even after letting it delete it.

 

[drfunkenstein2k]

Turns out the fatal error was because i forgot to put fusee-secondary back where it belongs. I took it out to test something just before trying your ini file.
It's working! Thank you for your help Hologram!

Now if only I can get past this "failed to get update information, result 0x00234a02" when i try to install updated firmware via Daybreak

Tinfoil is also still giving me the error asking me to delete kosmos every time i open it. Even after letting it delete it.

so what did you do to fix the emu boot issue?

 

[sli4]

so what did you do to fix the emu boot issue?

For me it was the hekate_ipl.ini file - The ini file that was in the hekate zip i got from hekate's github had nothing about the cfw configs written to it. So if you're having the same issue open yours with textedit and check it out. I copied Hologram's into mine line for line and it works. I took a look at the new hekate for 0.16.1 and it also seems to have all of the config information written in it with some slight differences. So that may work as well...

 

[drfunkenstein2k]

0.16.1 is still broke

i used holograms edit and i choose LAUNCH / CFW (emuMMC)
i get this:
Unknown pkg1 version
HOS version not supported
or emuMMC corrupt
failed to launch HOS

but if i choose fuse-primary it loads emuMMC just fine

 

[sli4]

oh I'm using 0.15.
Hologram's ini file may not be correct for 16. I noticed that when I looked at the bundled ini for 16 it was slightly different.
So maybe try to redownload the hekate_ipl.ini from hekate's git and replace yours?
Also, do you have fusee-primary.bin only in the payloads folder? or do you have it with fuse-secondary.bin and such as well? it should be with the others.

I stayed away from 16.1 because it's still prerelease so maybe there's some compatibility issue. There are also different variations of the hekate_ipl.ini that you could try - i think you can try changing some of the situations from fusee-secondary to primary and point it at the payload? That was my next move if using holograms didnt work. Though i really have no idea if that could mess things up worse so use caution. When I accidentally tried to boot without fusee-secondary i thought i bricked mine. (thankfully didnt)

 

[drfunkenstein2k]

Turns out the fatal error was because i forgot to put fusee-secondary back where it belongs. I took it out to test something just before trying your ini file.
It's working! Thank you for your help Hologram!

Now if only I can get past this "failed to get update information, result 0x00234a02" when i try to install updated firmware via Daybreak

Tinfoil is also still giving me the error asking me to delete kosmos every time i open it. Even after letting it delete it.

where does it belong?

 

[Draxzelex]

where does it belong?

It belongs wherever you indicated as such in your own hekate_ipl.ini file.

 

[FFTW]

I had a similar issue: after updating my firmware to 20.5 Emummc disappeared. I found this post on reddit and with some modification it helped me fix it, so I thought to share it here:

"ExJWubbaLubbaDubDub posted:

If you've updated Atmosphere and Hekate on your SD card, make sure you've also put the latest fusee.bin into bootloader/payloads.

Next, go into Hekate, click emuMMC and ensure it's enabled. Click Change emuMMC and choose the correct emuMMC (whether it was partition- or file-based).

Now, go back to Home > Launch and try Atmosphere again.

If that doesn't work (It thankfully worked for me), then you're emuNAND might be corrupt. Use NxNandManager to create a backup of your emuNAND and then create a new emuNAND. You might still be able to restore some things like saves from your old emuNAND to your new one."