Atmosphere 1.2.5 Black screen when boot from hekate (Need Help 😅)

Krizeth

Member
OP
Newcomer
Joined
Jan 15, 2022
Messages
21
Trophies
0
Age
33
XP
61
Country
Italy
Hi guys !!! I state that I am new in these things and I would like some clarifications:

I have recently jailbroken my Nintendo switch, everything works fine and never got any problems, The only thing I do not understand is:

Atmosphere always boot perfect at the first time I launch it from Hekate, but if I turn the Nintendo switch off and on again, (connect to pc , shutdown switch, put Jig , open tegraRCM and inject hekate_5.6.5) once I'm in Hekate and launch fusee.bin from payloads, after the Atmosphere and Nintendo logo I get a black screen 🤷🏻‍♂️.

Basically every time to boot In atmosphere from Hekate I have to copy again Atmosphere folder and sigspatches (hekate & fusee) in my sdcard.
(I do a drag-and-drop "overwrite", but maybe the folders need to be deleted and replaced with clean version manually) 🤔
&
(I use atmosphere 1.2.5 and latest sigspatches, and ofw is 13.2.0).

However in a nutshell the problem is that:

To start atmosphere from hekate, every time I always have to copy again the Atmosphere and Sigspatches folders in the sdcard, otherwise I get a black screen 🤷🏻‍♂️

Someone has a solution to my problem ??

Thanks in advance ❤️
 
Last edited by Krizeth,

wiiNinja

Well-Known Member
Member
Joined
Jan 13, 2009
Messages
631
Trophies
0
XP
1,146
Country
United States
I don't have a solution, just some suggestions to check:
1) You launch AMS from hekate using payload; did you update fusee.bin to match the AMS version?
2) Check hekate_ipl.ini before and after the problem to see if there's a difference. Also check atmosphere/contents to make sure it does not have "old Atmosphere content" (as suggested in Hekate's release note)
 
  • Like
Reactions: impeeza and Krizeth

Badablek

Well-Known Member
Member
Joined
Jan 23, 2006
Messages
414
Trophies
0
Age
41
XP
2,021
Country
France
Hi,

Using hekate to chainload fusee.bin is not the good way to do it (you can directly use fusee.bin instead, Hekate does not add anything useful with this).
Try to use the fss0 method :

hekate_ipl.ini example (without and with emuMMC) :

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

[Atmosphere]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1

[Atmosphere_emummc]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummcforce=1

[Original]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1

if it works, then you can change autoboot=0 to autoboot=1 (it will automatically launch AMS without emuMMC). Autoboot can be bypassed by keeping Volume-, to go to Hekate.

If nothing changes, then you can try to change autohosoff=0 to autohosoff=2 (with this, instead of shutting down the Switch directly from Atmosphere, it will relaunch automatically Hekate, which will shut down properly the Switch). It seems to be related to this (bad) behavior, the same that can happens with some modchips or autoRCM (Horizon does NOT shut down properly the Switch, which is put in RCM, waiting for a payload injection. Result, when you try to power ON the Switch again, it doesn't work)
 
  • Like
Reactions: Krizeth

Krizeth

Member
OP
Newcomer
Joined
Jan 15, 2022
Messages
21
Trophies
0
Age
33
XP
61
Country
Italy
I don't have a solution, just some suggestions to check:
1) You launch AMS from hekate using payload; did you update fusee.bin to match the AMS version?
2) Check hekate_ipl.ini before and after the problem to see if there's a difference. Also check atmosphere/contents to make sure it does not have "old Atmosphere content" (as suggested in Hekate's release note)

Hi wiiNinja and thank you for reply !

1) Yes sure, i have update fusee.bin with the latest version

2) Ok, i will try this step: "hekate_ipl.ini before and after the problem" and check for some changes !

At the moment i have delete atmosphere folder, and bootloader folder and replaced both with a clean new one
After i do that, Atmosphere is booted normally without blackscreen.
I dont know if now the problem is fixed (i will check this at the next boot)
In anycase, i will post updated if the problem has been solved or not !

Thank you again for your support =)
 

Krizeth

Member
OP
Newcomer
Joined
Jan 15, 2022
Messages
21
Trophies
0
Age
33
XP
61
Country
Italy
Hi,

Using hekate to chainload fusee.bin is not the good way to do it (you can directly use fusee.bin instead, Hekate does not add anything useful with this).
Try to use the fss0 method :

hekate_ipl.ini example (without and with emuMMC) :

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

[Atmosphere]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1

[Atmosphere_emummc]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummcforce=1

[Original]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1

if it works, then you can change autoboot=0 to autoboot=1 (it will automatically launch AMS without emuMMC). Autoboot can be bypassed by keeping Volume-, to go to Hekate.

If nothing changes, then you can try to change autohosoff=0 to autohosoff=2 (with this, instead of shutting down the Switch directly from Atmosphere, it will relaunch automatically Hekate, which will shut down properly the Switch). It seems to be related to this (bad) behavior, the same that can happens with some modchips or autoRCM (Horizon does NOT shut down properly the Switch, which is put in RCM, waiting for a payload injection. Result, when you try to power ON the Switch again, it doesn't work)

Hi Badablek and thank you for reply !

Ok you say: "you can directly use fusee.bin"
You mean i can boot directly in Athmosphere without have to go trough hekate ??
Ok No problem with that, i can do this =)
When i jailbreak my switch I used hekate for backup eMMC BOOT0/BOOT1 and eMMC RAW GPP.
I always used hekate from boot amosphere from payloads only because i follow a recently video-tutorial for the latest 13.2.0 fw jailbreak and i see to launch atmosphere from hekate payload, but if you tell me that ther is no difference, i can boot always from fusee.bin =)

I Can do this: "change autohosoff=0 to autohosoff=2"
But i never try to edit hekate_ipl.ini because im a beginner and dont know what these values do
anyway,

My hekate_ipl.ini is:


[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/package3
stock=1
icon=bootloader/res/ofw.bmp
{}

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

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

Thats my current hekate_ipl.ini

I must add "fss0=atmosphere/package3" like your example config ??

Can you tell me if there is something wrong in my hekate_ipl.ini ??

Sorry but i did my first jailbreak in a week and i am quite new in this field !

I await your welcome responde,
or now, Thank you again for your support =)
 

Badablek

Well-Known Member
Member
Joined
Jan 23, 2006
Messages
414
Trophies
0
Age
41
XP
2,021
Country
France
if you want to keep Hekate, it's better to use fss0 instead of fusee, then you don't have to update fusee.bin everytime AMS is updated.

Hekate is used for MMC dumping and restoring. 99% of the time, you don't ever need hekate at all, except if you want to manage sysMMC+emuMMC, multiple emuMMC, android or linux partitions. For my part, I like Hekate and I'm using it (fss0 method) even to only boot AMS on sysMMC ;)

in your hekate_ipl.ini, remove payload=bootloader/payloads/fusee.bin and replace with fss0=atmosphere/package3
if everything works as intended, you're done, else, try to change autohosoff=0 to autohosoff=2
 
  • Like
Reactions: Krizeth

Krizeth

Member
OP
Newcomer
Joined
Jan 15, 2022
Messages
21
Trophies
0
Age
33
XP
61
Country
Italy
if you want to keep Hekate, it's better to use fss0 instead of fusee, then you don't have to update fusee.bin everytime AMS is updated.

Hekate is used for MMC dumping and restoring. 99% of the time, you don't ever need hekate at all, except if you want to manage sysMMC+emuMMC, multiple emuMMC, android or linux partitions. For my part, I like Hekate and I'm using it (fss0 method) even to only boot AMS on sysMMC ;)

in your hekate_ipl.ini, remove payload=bootloader/payloads/fusee.bin and replace with fss0=atmosphere/package3
if everything works as intended, you're done, else, try to change autohosoff=0 to autohosoff=2

First of all, thank you very much for all the support and explanations you are giving me, really appreciated! and I'm starting to understand =)


So if i understand correctly:

I have to replace this lines:
payload = bootloader / payloads / fusee.bin

with

fss0 = atmosphere / package3

both on [Atmosphere (CFW)] and also in {------ Atmosphere Emu ------} paragraphs, right ??

(sorry if i ask all of these explanations but i dont wont to be wrong) :unsure:

anyway, I will make both attempts first the "fss0" and then "change autohosoff=0 to autohosoff=2"

and post updates as soon as possible !

For Now Thanks again for all your availability !!:D
 

Badablek

Well-Known Member
Member
Joined
Jan 23, 2006
Messages
414
Trophies
0
Age
41
XP
2,021
Country
France
even if you make a mistake, the worst you can have is a black screen. You can't brick your Switch, or make anything that can hurt it.

Yes, you have to change these two lines, nothing else, nothing more ;)
 
  • Like
Reactions: Krizeth

Krizeth

Member
OP
Newcomer
Joined
Jan 15, 2022
Messages
21
Trophies
0
Age
33
XP
61
Country
Italy
even if you make a mistake, the worst you can have is a black screen. You can't brick your Switch, or make anything that can hurt it.

Yes, you have to change these two lines, nothing else, nothing more ;)
even if you make a mistake, the worst you can have is a black screen. You can't brick your Switch, or make anything that can hurt it.

Yes, you have to change these two lines, nothing else, nothing more ;)
Ok perfect !
Now everything is clear to me, In summary so first i will try to change the 2 lines payload=bootloader/payloads/fusee.bin to fss0 = atmosphere / package3

and

if even so i will get black screen i will also change autohosoff = 0 to autohosoff = 2

right ?

I will do try at the next reboot of my nintendo switch and post updates !!

For now thank you very much really, you took me away a lot of doubts and worries like the fear of getting a console brick, but now I'm less worried, thanks and thanks again =) :yay:^_^
 

QuinuS

Member
Newcomer
Joined
Jan 17, 2022
Messages
9
Trophies
0
Age
30
XP
29
Country
Italy
I ran into the same problem as krizeth, but deleting and a clean install of atmosphere seem to have solved it.
anyway, mine Hekate_ipl.ini is set with:

"payload = bootloader / payloads / fusee.bin", so if I inject with fusee.bin, AMS Boot direct with no problems !! Now I'm wondering: If I wanted to inject hekate and start AMS from the payload section of hekate I have to change fss0 = atmosphere / package3 to hekate_ipl.ini ?? or can I keep payload = bootloader / payloads / fusee.bin ???

I ask for clarification about it !! many thanks !
 
  • Like
Reactions: Krizeth

Badablek

Well-Known Member
Member
Joined
Jan 23, 2006
Messages
414
Trophies
0
Age
41
XP
2,021
Country
France
you can't use both, at least in the same [section]

you launch AMS from Hekate by chainloading fusee.bin OR by using fss0 method (without fusee.bin)
you can do something like this (but this is totally useless, both methods will have the exact same results, except in one case you chainload fusee, in the other you use fss0 to load directly package3) :

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

[OFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/ofw.bmp

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

[Atmosphere (fss0)]
fss0=atmosphere/package3
emummc_force_disable=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/sys_cfw_boot.bmp

[Atmosphere (fusee+emuMMC)]
payload=bootloader/payloads/fusee.bin
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/emummc_boot.bmp

[Atmosphere (fss0+emuMMC)]
fss0=atmosphere/package3
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/emummc_boot.bmp
 
  • Like
Reactions: Krizeth

Krizeth

Member
OP
Newcomer
Joined
Jan 15, 2022
Messages
21
Trophies
0
Age
33
XP
61
Country
Italy
you can't use both, at least in the same [section]

you launch AMS from Hekate by chainloading fusee.bin OR by using fss0 method (without fusee.bin)
you can do something like this (but this is totally useless, both methods will have the exact same results, except in one case you chainload fusee, in the other you use fss0 to load directly package3) :

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

[OFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/ofw.bmp

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

[Atmosphere (fss0)]
fss0=atmosphere/package3
emummc_force_disable=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/sys_cfw_boot.bmp

[Atmosphere (fusee+emuMMC)]
payload=bootloader/payloads/fusee.bin
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/emummc_boot.bmp

[Atmosphere (fss0+emuMMC)]
fss0=atmosphere/package3
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/emummc_boot.bmp
you can't use both, at least in the same [section]

you launch AMS from Hekate by chainloading fusee.bin OR by using fss0 method (without fusee.bin)
you can do something like this (but this is totally useless, both methods will have the exact same results, except in one case you chainload fusee, in the other you use fss0 to load directly package3) :

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

[OFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
stock=1
icon=bootloader/res/ofw.bmp

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

[Atmosphere (fss0)]
fss0=atmosphere/package3
emummc_force_disable=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/sys_cfw_boot.bmp

[Atmosphere (fusee+emuMMC)]
payload=bootloader/payloads/fusee.bin
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/emummc_boot.bmp

[Atmosphere (fss0+emuMMC)]
fss0=atmosphere/package3
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/emummc_boot.bmp
Hi !! i see the @QuinuS post and i tried to delete the entire atmosphere folder and put a clean install of atmosphere and seem to have solved it:

What i do?:

1. Delete the entire atmosphere folder from sdcard and replace with a clean new one
2. in hekate_ipl.ini I tried to leave "payload = bootloader / payloads / fusee.bin" as it was
3. Injcet directly fusee.bin from TegraRCM, and atmosphere boot without problems !!
4. To be safer, i tried switching off and on for 3 times and repeat:
Always injecting fusee.bin directly from TegraRCM and keeping "payload = bootloader / payloads / fusee.bin" settings in hekate_ipl.ini config.
it seems that keeping the "payload = bootloader / payloads / fusee.bin" setting and injecting fusee.bin directly from TegraRCM solved my problem !

With this method all works perfectly !!:grog:

Thank You very much for the help guys ! Especially thanks to @Badablek for the explanations and the great patience towards my inexperience :bow:

I have one last question:
If one day, instead of starting atmosphere directly from TegraRCM I wanted to launch the payload from hekate I would have to change from "payload = bootloader / payloads / fusee.bin" to "fss0 = atmosphere / package3 " in my hekate_ipl.ini and vice versa, Right ?? :unsure:

Thanks again for your support and patience !! (lol) :yay3ds:
 
Problem Solved

Krizeth

Member
OP
Newcomer
Joined
Jan 15, 2022
Messages
21
Trophies
0
Age
33
XP
61
Country
Italy
:toot: [PROBLEM SOLVED] :toot:

The problem has finally been resolved for good!

@QuinuS method work for me !!

what have I done:

clean installation of atmosphere and bootloader folder (delete and reinstall clean)

hekate_ipl.ini remained unchanged:

Re-post my current hekate_ipl.ini to clarify :teach::

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


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

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

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

Despite several tips from Hekate_ipl.ini (which I really appreciated) I still wanted to do a test with a clean installation of the 2 folders mentioned above and do a test with the stock configuration of hekate. (configuration above).

Now I can boot by directly injecting fusee.bin from:

TegraRCM > fusee.bin > AMS

And also with hekate_5.6.5 chainload from:

TegraRCM > hekate_5.6.5 > Payloads > fusee.bin > AMS

Still keep the stock hekate_ipl with "payload = bootloader / payloads / fusee.bin" in [Atmosphere (CFW)] & [Atmosphere (emuMMC)] , and " fss0=atmosphere/package3" only in [OFW (SYSNAND)] paragraph.
At this time everything is fine either way, no black screen encountered, everything works.:yay3ds:

I hope my configuration is fine as this way everything works and will result in both cases as "13.2.0|AMS 1.2.5|E" .
If i understand correctly, the final "E" stands for Emunand and I should be safe .

Thank you all for your help and your patience!
Special Greetings to @QuinuS , @Badablek , @wiiNinja for clarifications. :grog:

I leave the post open in case someone might need it.:bow:
 
General chit-chat
Help Users
  • No one is chatting at the moment.
    KenniesNewName @ KenniesNewName: Apple is the new Disney