Hacking Weird issue with booting CFWs

[ZakMcKrackin]

So I'll try to keep this short and concise. I was on system firmware 10 and was using the last version of Atlas/Kosmos, which worked fine.

I updated to the latest Kosmos them rebooted into stock and updated the switch to 10.0.3 and then rebooted. For some reason, whenever I try to boot to a cfw (Hekate), I get the Kosmos logo and then a black screen, where it stays.

I've literally gone as far as formatting the SD card as fresh in the stock fw, completely rebuilding the SD card from scratch, which works, but after a reboot (no modifications, just the initial boot, then a reboot) I just keep getting the blank screen. I've also tried booting into sxos, but I get a black screen when clicking on cfw.

The only way I can consistently boot to cfw is by using fusee_primary but would prefer to use Hekate.

Anyone come across this problem before or able to offer any insight as to what might be happening?

 

[Hayato213]

Try this

https://gbatemp.net/threads/how-to-hekate-chainload-vanilla-atmos.563255/

Kosmos is dead by dead, the github for it has been archived.

 

[ZakMcKrackin]

not sure if you skimmed my post but its not just kosmos that does it. I've done a fresh install with atmosphere/hekate and also tried the SXOS boot, no luck.

 

[Hayato213]

not sure if you skimmed my post but its not just kosmos that does it. I've done a fresh install with atmosphere/hekate and also tried the SXOS boot, no luck.

Did you load with fusee-primary.bin instead?

 

[ZakMcKrackin]

yeah, that works but every other option I've tried gives me a blank screen.

 

[Hayato213]

yeah, that works but every other option I've tried gives me a blank screen.

Fusee-Primary is atmosphere official bootloader it wants that.

 

[ZakMcKrackin]

ok. so forgive my ignorance here, but why can't I use hekate?

--------------------- MERGED ---------------------------

also, because i like to use my sxos usbc dongle to launch payloads, i figured i'd copy fusee-primary to the SD card. just booted up, selected payloads and chose fusee-primary and get a blank screen.. its as if it doesnt like booting from SD?

 

[Hayato213]

ok. so forgive my ignorance here, but why can't I use hekate?

You could just that Kosmos' hekate_ipl.ini doesn't have it pointed to fusee-primary.bin, you need to load fusee-primary to load up fusee-secondary payload stated in Hekate_ipl.

--------------------- MERGED ---------------------------

SX OS dongle doesn't work this way, it use payload in .dat format not .bin format.

 

[ZakMcKrackin]

ok, just as an update, i found a slightly different hekate_ipl.ini online which looks like this:

{------ Atmosphere ------}
{Pick this option to launch CFW.}
[Atmosphere]
payload=atmosphere/fusee-primary.bin
{ }
{------ Stock ------}
{NOTE: This option does not launch CFW.}
[Stock]
fss0=atmosphere/fusee-secondary.bin
stock=1
{ }


The version I had before looked like this:

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

[CFW - sysMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
fss0=atmosphere/fusee-secondary.bin
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/icon_payload.bmp

[Stock - sysMMC]
fss0=atmosphere/fusee-secondary.bin
emummc_force_disable=1
stock=1
icon=bootloader/res/icon_switch.bmp


I before swapping the ini file out entirely, I tried editing the file first, replacing the word 'secondary' with 'primary' but still got the blank screen - not sure if thats related to the kip1patch lines though since I know fusee-primary uses different patches.