can only boot CFW through Hekate, fusee.bin results in Blackscreen

[naddel81]

hi at all,


as title says: I updated kosmos/deep sea and can only boot through hekate (Launch-CFW). When I select payload (fusee.bin) it results in blackscreen.

can someone help me?

best wishes.

 

[Hayato213]

Make sure fusee.bin is the most updated one.

 

[naddel81]

Make sure fusee.bin is the most updated one.

it is.

 

[impeeza]

Which method do you use to start your console and inject payload?

 

[naddel81]

Which method do you use to start your console and inject payload?

tegraRCMgui (win 10)
or nxloader (android)

 

[impeeza]

Ok, remember to update the payload.bin to the latest fusee.bin, download it again even if you thing you have the newest.

 

[Hayato213]

it is.

If you update Atmosphere and you want to use fusee.bin as bootloader you have to update fusee.bin, it specified on Atmosphere github.

 

[naddel81]

I updated fusee.bin on both SD card and on my boot devices (windows or android) and pushing it to the switch makes it blackscreen. hekate works fine though.

 

[Hayato213]

I updated fusee.bin on both SD card and on my boot devices (windows or android) and pushing it to the switch makes it blackscreen. hekate works fine though.

SD card format?

 

[impeeza]

some extra information:

if you inject fusee.bin as payload, you get black screen

If you inject Hekate as paylad all load fine?

please give us a copy of your hekate_ipl.ini file.

 

[naddel81]

SD card format?

FAT32

Post automatically merged: Nov 14, 2023

some extra information:

if you inject fusee.bin as payload, you get black screen

If you inject Hekate as paylad all load fine?

please give us a copy of your hekate_ipl.ini file.

hekate boots fine and then ONLY "LAUNCH CFW" works.
when I try to load fusee.bin through "Payloads" it results in the same black screen as pushing fusee.bin through tegra or nxloader:

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

{hekate with sigpatches}
{}
{Provided by: WiiDatabase.de}
{}

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

[CFW (EMUMMC)]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummcforce=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
{}

 

[Hayato213]

FAT32

Post automatically merged: Nov 14, 2023

hekate boots fine and then ONLY "LAUNCH CFW" works.
when I try to load fusee.bin through "Payloads" it results in the same black screen as pushing fusee.bin through tegra or nxloader:

It is weird that hekate can boot package3 and Fusee.bin can't

Perhap trying loading fusee through Hekate

with

{--- Fusee ---}
[Fusee]
payload=bootloader/payloads/fusee.bin

 

[impeeza]

It is weird that hekate can boot package3 and Fusee.bin can't

Perhap trying loading fusee through Hekate

with

{--- Fusee ---}
[Fusee]
payload=bootloader/payloads/fusee.bin

Hekate, really do not load package3, Hekate decompress package3 file, extract some code and create a hybrid custom load package, so only part of the code of package3 is used.

yeah, that entry on Hekate_ipl.ini file will chainload the file fusee.bin.

 

[The Real Jdbye]

FAT32

Post automatically merged: Nov 14, 2023

hekate boots fine and then ONLY "LAUNCH CFW" works.
when I try to load fusee.bin through "Payloads" it results in the same black screen as pushing fusee.bin through tegra or nxloader:

Do you launch sysnand or emunand? With fusee.bin, it will always launch emunand (since it always uses what is in emummc.ini) if there is one. In other words if your emunand was bricked and you are launching the sysnand option in hekate then fusee would not work at all.

Also delete the contents of your exefs_patches and kip_patches and put the latest sigpatches on again. Hekate doesn't use these folders, but Fusee does, so if there are old files left behind they could prevent Fusee from working.

 

[josete2k]

Rename your emummc folder and try again...

 

[naddel81]

Do you launch sysnand or emunand? With fusee.bin, it will always launch emunand (since it always uses what is in emummc.ini) if there is one. In other words if your emunand was bricked and you are launching the sysnand option in hekate then fusee would not work at all.

Also delete the contents of your exefs_patches and kip_patches and put the latest sigpatches on again. Hekate doesn't use these folders, but Fusee does, so if there are old files left behind they could prevent Fusee from working.

I never used emunand, but I will try your hint with deleting patches and adding them again.

Post automatically merged: Nov 15, 2023

Rename your emummc folder and try again...

never used it, but just to make sure. where is that folder located?

 

[BigOnYa]

https://rentry.org/UpdateCFWAndFW

 

[naddel81]

https://rentry.org/UpdateCFWAndFW

is the result the same whether I load hekate to boot CFW or fusee.bin?

 

[BigOnYa]

is the result the same whether I load hekate to boot CFW or fusee.bin?

I personally boot to hekate then press "payloads" then select "fusee.bin" but not sure if any differences.

 

[naddel81]

I personally boot to hekate then press "payloads" then select "fusee.bin" but not sure if any differences.

I think Hekate (package3) loader does not need sigpatches. But how does it load games then if sigpatches are not required?