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

noirmaru

Member
OP
Newcomer
Joined
May 19, 2023
Messages
23
Trophies
0
Age
41
XP
167
Country
France
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

Code:
[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:

Follow-up:

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

Code:
[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:

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

Code:
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
 
Last edited by noirmaru,

TomSwitch

Well-Known Member
Member
Joined
Jan 10, 2019
Messages
4,546
Trophies
1
Age
44
XP
14,704
Country
United States
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
 
Last edited by TomSwitch,

Mikado123

Member
Newcomer
Joined
Dec 2, 2023
Messages
11
Trophies
0
Age
24
XP
34
Country
Italy
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

Code:
[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:

Follow-up:

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

Code:
[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:

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

Code:
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
 

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
  • AncientBoi @ AncientBoi:
    I think that was "The great depression" time
  • BigOnYa @ BigOnYa:
    It like one of those fake guns, that shoot, then a flag comes out and says, "splash"
    +2
  • K3Nv2 @ K3Nv2:
    Yeah a world War wasn't going on or anything
  • K3Nv2 @ K3Nv2:
    Americans lied about camps for propaganda
  • Xdqwerty @ Xdqwerty:
    @AncientBoi, where is your gun at?
  • K3Nv2 @ K3Nv2:
    I thought he already showed you his gun
  • BigOnYa @ BigOnYa:
    "This is my rifle, this is my gun. This is for fighting, this is for fun." - Full Metal Jacket
    +1
  • AncientBoi @ AncientBoi:
    We actually said that in Boot Camp, waaay before the movie :mellow:
    +1
  • K3Nv2 @ K3Nv2:
    I gotta raid0 these m.2s yay
  • BigOnYa @ BigOnYa:
    Do a raid10
  • K3Nv2 @ K3Nv2:
    That's tomorrow
    +1
  • Xdqwerty @ Xdqwerty:
    Yawn
  • BigOnYa @ BigOnYa:
    Damn Wal-Mart has 42" 4k TVs for only $150
  • Xdqwerty @ Xdqwerty:
    @BigOnYa, i bet it will not fit inside your bedroom
  • BigOnYa @ BigOnYa:
    Yea here in North Korea, we are only allowed 1 19" tv per household. And the only channel we get is, MLT (Missile Launch Today)
    +1
  • K3Nv2 @ K3Nv2:
    @BigOnYa, doesn't fit in his bedroom he's American
    +1
  • BigOnYa @ BigOnYa:
    I hate ordering stuff online if I can go buy it somewhere close to me, and everywhere anymore will give you a discount only if you order it online, bs. Should be a discount if I go pick it up, not order online.
  • K3Nv2 @ K3Nv2:
    I love it for most things most stores you just shows the receipt online and they scan it
    +1
  • K3Nv2 @ K3Nv2:
    Makes it easy for incompetent restaurant staff that don't know how to hear an order
  • BigOnYa @ BigOnYa:
    Mostly for big purchases, I want it in my hands before I pay. Like a tv, I trust picking it up myself, before I'd trust it being sent thru mail/delivery. (Broken screen, etc) But yea if I can order online, then pickup at store is ok, but not all places offer that.
  • cearp @ cearp:
    > Like a tv, I trust picking it up myself, before I'd trust it being sent thru mail/delivery. (Broken screen, etc)

    Thing is, if you break it driving back to your house, it's your fault. But if the delivery driver damages it, it's not your fault.
    +1
  • K3Nv2 @ K3Nv2:
    Most people that haul big tvs have empty trucks or know enough not to set it face down
  • BigOnYa @ BigOnYa:
    Then I gotta send it back and wait another week or two. I have a pickup truck, with a extended cab, so no prob for me.
  • K3Nv2 @ K3Nv2:
    Most manufacturers pack it well enough where they aren't that dumb to let it happen
    K3Nv2 @ K3Nv2: Most manufacturers pack it well enough where they aren't that dumb to let it happen