Error while loading fss0 - pls help (2024)

Error while loading fss0:
atmosphere/package3
Wrong ini cfg or missing/corrupt files!
Failed to launch HOS!

After creating an emummc, I get this error when trying to launch it, I'm f*cking clueless what to do, please help

Hayato213 said:

Check your hekate_ipl if you have a fusee-secondary.bin your line that why it won't boot. Read the change log for Atmosphere 1.0.0

Click to expand...

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

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

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

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

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

No fusee-secondary.bin in sight. That's not the issue here

ShowtimevonParty said:

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

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

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

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

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

No fusee-secondary.bin in sight. That's not the issue here

Click to expand...

Replace your CFW files from where you previously get your fss0 build. Also update your hekate if it outdated.

Hayato213 said:

Replace your CFW files from where you previously get your fss0 build. Also update your hekate if it outdated.

Click to expand...

How do I do that?

ShowtimevonParty said:

How do I do that?

Click to expand...

Look at the folder that you get your CFW files from and replace them.

omg, I think I know what happened, when creating a partition for the emummc it deleted all the other folders, including atmosphere.

I only have bootloader and emuMMC in the root of my sd card, do I re add atmosphere at the root or inside one of these two folders?

ShowtimevonParty said:

omg, I think I know what happened, when creating a partition for the emummc it deleted all the other folders, including atmosphere.

I only have bootloader and emuMMC in the root of my sd card, do I re add atmosphere at the root or inside one of these two folders?

Click to expand...

re add to root. aswell as sigpatches if u need and your exosphere if you used to block nintendo.

Hayato213 said:

Look at the folder that you get your CFW files from and replace them.

Click to expand...

Reading the release and main page of the Atmosphère and Hekate repos on GitHub. Or reading the so many posts and guides existing here on GBATEMP.

impeeza said:

Reading the release and main page of the Atmosphère and Hekate repos on GitHub. Or reading the so many posts and guides existing here on GBATEMP.

Click to expand...

My post earlier said Atmosphere 1.0.0 changelog

ShowtimevonParty said:

omg, I think I know what happened, when creating a partition for the emummc it deleted all the other folders, including atmosphere.

I only have bootloader and emuMMC in the root of my sd card, do I re add atmosphere at the root or inside one of these two folders?

Click to expand...

Download the /atmosphere folder, put it on the root of your SD card, and make sure the SD card is formatted to FAT32.

Hayato213 said:

Check your hekate_ipl if you have a fusee-secondary.bin your line that why it won't boot. Read the change log for Atmosphere 1.0.0

Click to expand...

i do have it what would i do then?

Felix12332 said:

i do have it what would i do then?

Click to expand...

You replace the specified fusee-primary.bin with fusee.bin and fusee-secondary.bin with package3, and also update your CFW files.

Hayato213 said:

You replace the specified fusee-primary.bin with fusee.bin and fusee-secondary.bin with package3, and also update your CFW files.

Click to expand...

not entirely sure what those are but i can give you a layout of what i'm using right now and send a link to my current thread so we don't accidentally revive this one https://gbatemp.net/threads/corrupted-files.603421/

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

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

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

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

If you use fusee.bin as bootloader , then it would be

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

Hayato213 said:

You replace the specified fusee-primary.bin with fusee.bin and fusee-secondary.bin with package3, and also update your CFW files

Click to expand...

we can continue here if you'd prefer

it's now showing

failed to apply 'nosigchk'
press POWER to continue
press VOL to go to the menu

pressed VOL and got

failed to launch HOS
press any key