Switch rebooting always to Hekate instead of Atmosphere

[switcherjoe]

Hi,
I have the second Switch console for my little son, it was configured to boot automatically fusee.bin (Atmosphere) and worked perfectly.
Now and I don't know how this is happened, if I reboot the console it always boots into Hekate instead of Atmosphere as it was previously.
I tried to delete the /bootloader folder with Hekate - it didn't help, it still boots into non-GUI Hekate version. Checked fusee.bin in /payloads and reboot_payload.bin in /atmosphere - everything looks well there, I also overwritten the files there just in case. Still if I reboot the console by any means - either by holding the "On/Off" button and selecting "Reboot" or by going in the Homebrew menu and choosing there "reboot to payload" - I always end up in Hekate instead of Atmosphere and have to boot into Atmosphere from there.
What can it be and how can I solve it?
Many thanks!!

 

[switcherjoe]

I found the solution - for some weird reason the file patches.ini disappeared from /bootloader . Really weird, my son couldn't have done it for sure...

 

[Jasonclarke1986]

exfat sd card by any chance? before i formatted to fat32 my card kept deleting the bootloader files and some from the atmosphere folder like the kip patchers folder and contents.

 

[kidkat210]

I found the solution - for some weird reason the file patches.ini disappeared from /bootloader . Really weird, my son couldn't have done it for sure...

It sounds like the reboot_payload.bin is a hekate.bin.

If you want a different way to fix it (or just for informational purposes)
Download a fresh atmosphere zip. Extract it. Navigate to atmosphere/content/. Copy the reboot_payload.bin from that to your sd in atmosphere/content/ overwriting the one on your sd.

I can only guess (from the sounds of it) the method you found to fix it is for hekate to autoboot into fusee.bin (atmosphere). So you reboot, it boots hekate (then immediately launching fusee.bin, this is called chainloading) then your in cfw

 

[Draxzelex]

Hi,
I have the second Switch console for my little son, it was configured to boot automatically fusee.bin (Atmosphere) and worked perfectly.
Now and I don't know how this is happened, if I reboot the console it always boots into Hekate instead of Atmosphere as it was previously.
I tried to delete the /bootloader folder with Hekate - it didn't help, it still boots into non-GUI Hekate version. Checked fusee.bin in /payloads and reboot_payload.bin in /atmosphere - everything looks well there, I also overwritten the files there just in case. Still if I reboot the console by any means - either by holding the "On/Off" button and selecting "Reboot" or by going in the Homebrew menu and choosing there "reboot to payload" - I always end up in Hekate instead of Atmosphere and have to boot into Atmosphere from there.
What can it be and how can I solve it?
Many thanks!!

What's wrong with using Hekate? Its much more useful than fusee.

 

[BeckysFootSlave]

What's wrong with using Hekate? Its much more useful than fusee.

Because he (like myself) have children and don't want them to load into hekate!
Same with hb app forwarders (I have none) and also the album works like it should and doesn't start hbmenu Applet mode!

Hbmenu (and hbmenu over album) just work with override in my case!
Tin... is installed as applet and not the self installer!

 

[Draxzelex]

Because he (like myself) have children and don't want them to load into hekate!
Same with hb app forwarders (I have none) and also the album works like it should and doesn't start hbmenu Applet mode!

Hbmenu (and hbmenu over album) just work with override in my case!
Tin... is installed as applet and not the self installer!

You could just setup autoboot if you don't want them to load Hekate.