atmosphere don't boot with hekate

[alba93]

Hello,
I do need your help
My SD is broken and I try to reinstall atmosphere on another one.
I formated it in FAT32 and copied the hekate folders and the fusee payload into.
Then I injected the payload to boot with hekate
Under hekate i created the partition for the enunand and then created the emunand.
Then by the SD transfert tool I copied the atmosphere folder at the root of the SD card and i modified the hekate hekate_ipl.ini

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

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/package3
atmosphere=1
icon=bootloader/res/icon_payload.bmp
{}

[CFW (EMUMMC)]
emummcforce=1
fss0=atmosphere/package3
atmosphere=1
icon=bootloader/res/icon_payload.bmp
{}

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

After when I tried to start atmosphere with the CFW, the stock one or the emunand my screen is stuck on the hekate ipl screen
When I try to inject the fusee payload trough Hekate atmosphere is working
Do you have an idea to fix the problem
thanks

 

[binkinator]

Hello,
I do need your help
My SD is broken and I try to reinstall atmosphere on another one.
I formated it in FAT32 and copied the hekate folders and the fusee payload into.
Then I injected the payload to boot with hekate
Under hekate i created the partition for the enunand and then created the emunand.
Then by the SD transfert tool I copied the atmosphere folder at the root of the SD card and i modified the hekate hekate_ipl.ini


After when I tried to start atmosphere with the CFW, the stock one or the emunand my screen is stuck on the hekate ipl screen
When I try to inject the fusee payload trough Hekate atmosphere is working
Do you have an idea to fix the problem
thanks

Feels like something wrong w/ package3? Hmmm. Dunno.

Let’s do a test.

Download fusee.bin from the atmosphere GitHub page (same release as what you’re using) and place it in /bootloader/payloads/

Change your hekate_ipl.ini from this:

[CFW (EMUMMC)]
emummcforce=1
fss0=atmosphere/package3
atmosphere=1
icon=bootloader/res/icon_payload.bmp
{}

to this:

[CFW (EMUMMC)]
emummcforce=1
payload=/bootloader/payloads/fusee.bin
atmosphere=1
icon=bootloader/res/icon_payload.bmp
{}

reboot and try to start CFW {EMUMMC)

 

[alba93]

Feels like something wrong w/ package3? Hmmm. Dunno.

Let’s do a test.

Download fusee.bin from the atmosphere GitHub page (same release as what you’re using) and place it in /bootloader/payloads/

Change your hekate_ipl.ini from this:



to this:



reboot and try to start CFW {EMUMMC)

thanks a lot for your feedback
by changing the hekate_ipl.ini it boots correctly

what could be the problem with package3?
Before changing the SD card all was running well with it

 

[raging_chaos]

thanks a lot for your feedback
by changing the hekate_ipl.ini it boots correctly

what could be the problem with package3?
Before changing the SD card all was running well with it

I stick with fusee because it's less of a hassle overall, but when I have tried to use package3 the only way I got it to boot was with this:

fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

 

[alba93]

How do i manage emunand with fusee
by replacing fss0=atmosphere/package3 by payload=/bootloader/payloads/fusee.bin in CFW sysnand, emunand and stock when i apply a theme for example for the emunand the theme is also modified in CFW sysnand
It seems it boots always on the same system
before with hekate all was running well

 

[binkinator]

How do i manage emunand with fusee
by replacing fss0=atmosphere/package3 by payload=/bootloader/payloads/fusee.bin in CFW sysnand, emunand and stock when i apply a theme for example for the emunand the theme is also modified in CFW sysnand
It seems it boots always on the same system
before with hekate all was running well

emummc_force_disable=1
and
emummcforce=1

those are the options that determine whether or not your emunand is enabled.

Themes are stored on the SDCard under /atmosphere/contents/01000000001000 and are therefore nand independent.

 

[alba93]

emummc_force_disable=1
and
emummcforce=1

those are the options that determine whether or not your emunand is enabled.

Themes are stored on the SDCard under /atmosphere/contents/01000000001000 and are therefore nand independent.

in my first post you've my hekate ipl.ini in which i replaced fss0.... by payload=....
but as I explained when i modify the theme it is also applied for all the other systems
in the switch settings when i select the theme black screen it is applied everywhere before my sd failure it was not

 

[binkinator]

in my first post you've my hekate ipl.ini in which i replaced fss0.... by payload=....
but as I explained when i modify the theme it is also applied for all the other systems

It will apply to anything running CFW that can read the /atmosphere/contents/01000000001000 directory. If you’re running Atmosphere…it doesn’t matter which *nand you are on…it will read that directory and layer on the theme if present.

 

[alba93]

in the switch settings when i select the theme black screen theme it is applied everywhere before my sd failure it was not

 

[binkinator]

in the switch settings when i select the theme black screen theme it is applied everywhere before my sd failure it was not

Oh, you mean the built in black/white themes. I’m not sure where those are set but it seems to me that should in fact be dependent upon the nand vs custom themes which are not. Booting into Hekate vs fusee in and of itself doesn’t cause this issue btw. I run exactly what I said above on my personal switch w/o any problems. Might double check System Settings to make sure you’re running on the *nand you are expecting in each case.

Perhaps someone else has more insight into this?

 

[alba93]

yes indeed
I mean the built in Nintendo's themes
As it was working before I think that these settings are recorded into the specific Nand
Is there another way to check on which Nand I'm?

 

[binkinator]

yes indeed
I mean the built in Nintendo's themes
As it was working before I think that these settings are recorded into the specific Nand
Is there another way to check on which Nand I'm?

Check your Firmware version under System Settings. It will tell you Firmware|CF|Nand, where Nand will be E for Emunand or S for Sysnand (or nothing for CFW and Nand if it‘s Stock.)

 

[alba93]

I'm currently reinstalling my emunand
I will check as soon as the installation is completed
But when I changed the theme i noticed that a E was always prompted in the system settings but I'm not sure, I will check

What can I do If I always boot on the emunand?

 

[alba93]

in any case thanks a lot for your support

 

[binkinator]

I'm currently reinstalling my emunand
I will check as soon as the installation is completed
But when I changed the theme i noticed that a E was always prompted in the system settings but I'm not sure, I will check

What can I do If I always boot on the emunand?

Having an E in all cases would absolutely explain it.

You will need to check the setting in your Hekate_ipl.ini file to see why it’s not using Sysnand when you expect it to do so. We are still using Hekate to launch…it‘s just we’re using Fusee.bin as the payload.

Perhaps something changed in your .ini file?

 

[alba93]

I confirm

6.2.0 | AMS 1.3.2|E under emunand
6.2.0 | AMS 1.3.2|E under CFW
6.2.0 | AMS 1.3.2|E under stock
6.2.0 without injecting payload

I inject hekate 5.7.2.bin

for stock my hekate ipl.ini parameters are the following

{--- Stock ---}
[Stock (SYSNAND)]
stock=1
emummc_force_disable=1
payload=/bootloader/payloads/fusee.bin
icon=bootloader/res/icon_switch.bmp
{}

by injecting directly fusee.bin it is the same
6.2.0 | AMS 1.3.2|E

 

[binkinator]

I confirm

6.2.0 | AMS 1.3.2|E under emunand
6.2.0 | AMS 1.3.2|E under CFW
6.2.0 | AMS 1.3.2|E under stock
6.2.0 without injecting payload

I inject hekate 5.7.2.bin

for stock my hekate ipl.ini parameters are the following

{--- Stock ---}
[Stock (SYSNAND)]
stock=1
emummc_force_disable=1
payload=/bootloader/payloads/fusee.bin
icon=bootloader/res/icon_switch.bmp
{}

We might want to move everything out of the way (temporarily) and just deploy a clean Atmosphere, Hekate and fusee.bin.

1. move/rename /atmosphere to /atmosphere.bk and then move/rename /bootloader to /bootloader.bk
2. unzip atmosphere.x.zip and hekate.x.zip at the top level of your SDCard
3. copy your /bootloader.bk/hekate_ipl.ini to the new /bootloader/ directory.
4. copy your /bootloader.bk/payloads/fusee.bin to /bootloader/payloads/
5. reboot and see if this fixes everything…

 

[alba93]

binkinator
in fact before reinstalling my emunand, i formated my SD card and extracted hekate and atmosphere at its root
It is already a clean installation

 

[alba93]

in hekate i disabled the emunand
i got :
6.2.0 | AMS 1.3.2|S under CFW
6.2.0 | AMS 1.3.2|S under stock

by selecting the emunand it boots on the nand

 

[binkinator]

in hekate i disabled the emunand
i got :
6.2.0 | AMS 1.3.2|S under CFW
6.2.0 | AMS 1.3.2|S under stock

by selecting the emunand it boots on the nand

So crazy. I’ve never seen anything like this.

I thought you copied data over. Must be mixing up people I’ve talked to…