Updated to 16.1 and now I get a black screen when launching emummc

[noirmaru]

Using Hekate and Atmosphere on my Nintendo Switch, I updated the firmware to 16.1 after updating atmosphere to 1.5.5 and hekate and 6.0.6 I updated sigpatches from sigmapatches.coomer.party.

All was fine, when rebooting to Atmosphere 1.5.5 before I ran daybreak.

I loaded the files using DBI FTP.

When I launch the cfw emummc from hekate, the screen says it is initialising atmosphere 1.5.5 patching kips, etc. and then in green Booting... then screen turns black and nothing more happens.

If I load fusee.bin directly from RCM, then I see the atmosphere logo for a second and then it is black screen.

In hekate, I notice that the time is wrong. Could that be the problem if the HW clock is wrong?

I was on 16.0.2 previously and have always updated without a problem. Not sure what to do now...

Here is my hekate_ipl.ini

[config]
autoboot=0
autoboot_list=0
bootwait=0
backlight=220
noticker=0
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
fss0=atmosphere/package3
kip1=atmosphere/kips/loader.kip
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

Post automatically merged: Aug 24, 2023

Follow-up:

I tried using the reentry guide hekate_ipl.ini and it shows the atmosphere logo for a second and then black screen...

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

Post automatically merged: Aug 24, 2023

Ok, after a lot of frustration changing the hekate_ipl.ini to this made everything work:

autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere EmuMMC]
emummcforce=1
fss0=atmosphere/package3
kip1patch=nosigchk
fss0experimental=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

 

[TomSwitch]

You only need to know a clean install of atmosphere is not the same as overwriting the files and keep the not compatible stuff

Clean install is known to be good. What stuff you have on your sd which might be bad with 16.1 only you may know.

A quick one is to delete contents directory or rename it. I would say it has a 90% chance of fixing your problem

 

[Mikado123]

dude how the fuck did you manage that

Using Hekate and Atmosphere on my Nintendo Switch, I updated the firmware to 16.1 after updating atmosphere to 1.5.5 and hekate and 6.0.6 I updated sigpatches from sigmapatches.coomer.party.

All was fine, when rebooting to Atmosphere 1.5.5 before I ran daybreak.

I loaded the files using DBI FTP.

When I launch the cfw emummc from hekate, the screen says it is initialising atmosphere 1.5.5 patching kips, etc. and then in green Booting... then screen turns black and nothing more happens.

If I load fusee.bin directly from RCM, then I see the atmosphere logo for a second and then it is black screen.

In hekate, I notice that the time is wrong. Could that be the problem if the HW clock is wrong?

I was on 16.0.2 previously and have always updated without a problem. Not sure what to do now...

Here is my hekate_ipl.ini

[config]
autoboot=0
autoboot_list=0
bootwait=0
backlight=220
noticker=0
autohosoff=0
autonogc=1
updater2p=1
bootprotect=0

[CFW - sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
fss0=atmosphere/package3
kip1=atmosphere/kips/loader.kip
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

Post automatically merged: Aug 24, 2023

Follow-up:

I tried using the reentry guide hekate_ipl.ini and it shows the atmosphere logo for a second and then black screen...

[config]
autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere CFW]
payload=bootloader/payloads/fusee.bin
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

Post automatically merged: Aug 24, 2023

Ok, after a lot of frustration changing the hekate_ipl.ini to this made everything work:

autoboot=0
autoboot_list=0
bootwait=3
backlight=100
autohosoff=0
autonogc=1
updater2p=0
bootprotect=0

[Atmosphere EmuMMC]
emummcforce=1
fss0=atmosphere/package3
kip1patch=nosigchk
fss0experimental=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp

[Stock SysNAND]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

dude how the fuck did you manage that i thank you so much i was stuck on that black screen for days i couldn't manage to understand in the slightest but i copypaster your hekate_ipl.ini settings and it went like butter thank you so much i'll do some testing to try and understang wich setting specifically was blocking the startup