atmosphere don't boot with hekate

raging_chaos · Jul 1, 2022

alba93 said:
(After) replacing fss0=atmosphere/package3 (to) payload=/bootloader/payloads/fusee.bin when i apply a theme (in emunand) the theme is also modified in CFW sysnand (and stock)

Edited the quote to make it easier to follow, hope you don't mind. Don't use fusee to boot stock in this case. Use package3.

[Stock (SYSNAND)]
fss0=atmosphere/package3
kip1patch=nosigchk
stock=1
emummc_force_disable=1
icon=bootloader/res/icon_switch.bmp

The same goes for if you want to boot to sysnand using Atmosphere.

[CFW (SYSNAND)]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

Don't forget to update sigpatches if need to.

alba93 · Jul 1, 2022

raging_chaos said:
Edited the quote to make it easier to follow, hope you don't mind. Don't use fusee to boot stock in this case. Use package3.

The same goes for if you want to boot to sysnand using Atmosphere.

Don't forget to update sigpatches if need to.

my switch doesn't boot anymore with package3
This is my main concern

raging_chaos · Jul 1, 2022

So I ended up grabbing a spare SD card and I retried all of your steps from your original post. I can at least confirm there is nothing wrong with the latest hekate and atmosphere because it worked without issue. I even used the hekate_ipl.ini you had posted with fss0. The suggestion is always to start over from scratch by redownloading everything, reformatting with official SD Card Formatter tool, following the rentry guide or something similar, or just flat out using a different SD card. It's not easy figuring out why fss0 won't work for some users it could be anything.

As for how fusee works, it completely ignores whatever arguments are in hekate_ipl.ini so commands like emummcforce=1 are not necessary. Your hekate_ipl.ini should pretty much look like this since you can only boot fusee:

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

[Atmosphere Fusee]
payload=atmosphere/fusee.bin
icon=bootloader/res/icon_payload.bmp

To boot into sysnand with fusee you need to disable your emuMMC before launching by going into the "emuMMC" menu, then click "Change emuMMC" and then click "Disable" at the top. You'll have to reenable emuMMC using the same menu when you want to use CFW by selecting your Raw partition (SD Raw 1/2/3). Someone had brought up being able to use arguments but CTCaer pretty much said he's not interested.

binkinator · Jul 1, 2022

raging_chaos said:
As for how fusee works, it completely ignores whatever arguments are in hekate_ipl.ini so commands like emummcforce=1 are not necessary.

whah!?! I did not know this. Thank you.

raging_chaos said:
The suggestion is always to start over from scratch by redownloading everything, reformatting with official SD Card Formatter tool, following the rentry guide or something similar, and just flat out using a different SD card. It's not easy figuring out why fss0 won't work for some users it could be anything.

…for the record he has already started from scratch once before. I’m thinking it’s the card.

raging_chaos · Jul 1, 2022

binkinator said:
I’m thinking it’s the card.

Agreed, everything is pointing to a card incompatibility.

alba93 · Jul 1, 2022

thanks raging_chaos for your feedback

in my previous postes I've already made a clean installation of the system => issue not fixed
I've also tried to disable the emunand to boot on the CFW of the nand => it works but it is not very user friendly
I did not know that fusee doesn't take into account the hekate_ipl.ini parameters

By injecting fusee :

I always boot to the emunand
I need to disable the emunand to access the CFW from the nand
I need to turn off my switch to boot on the OFW of the nand

with hekate it was easier...

I've just ordered a new SD card hoping that it will fix my issues
i'll keep you informed

alba93 · Aug 15, 2022

sorry for this late update but I still have the same issue with my new sd card
I'll keep on using fusee but I do not understand what's wrong with package3

mario1992 · Aug 19, 2022

error code: 2168-0001 atmosphere, how do I fix it?

binkinator · Aug 19, 2022

mario1992 said:
error code: 2168-0001 atmosphere, how do I fix it?

Please stop cross posting. It makes a mess for everyone else.

atmosphere don't boot with hekate

Well-Known Member

Well-Known Member

Well-Known Member

Garfield’s Fitness Coach

Well-Known Member

Well-Known Member

Well-Known Member

Member

Garfield’s Fitness Coach

Similar threads

Popular threads in this forum