[Atmosphere CFW] payload=bootloader/payloads/fusee.bin icon=bootloader/res/icon_payload.bmp Use code with caution. Copied to clipboard
If you see this message, it is usually a sign that everything is working correctly. The boots are "hot" because the system is ready to go.
Boot entries are defined in the bootloader/hekate_ipl.ini file on your SD card. This text file dictates what options appear on the screen. A typical entry looks like this: bootloader hekateiplini has boot entries hot
As noted in the official Hekate documentation , the bootloader/hekate_ipl.ini is crucial. It holds two types of entries:
When modding a Nintendo Switch, few errors are as frustrating as seeing the message: This usually happens right when you're ready to launch your custom firmware (CFW). [Atmosphere CFW] payload=bootloader/payloads/fusee
Let’s dissect the anatomy of Hekate, the role of hekate_ipl.ini , and why "hot boot entries" are a feature, not a bug—and how to manage them before they burn through your system stability.
[config] autoboot=0 autoboot_list=0 bootwait=3 backlight=100 autohosoff=0 autonogc=1 updater2p=1 [Atmosphere CFW] payload=bootloader/payloads/fusee.bin icon=bootloader/res/icon_payload.bmp [Stock SysNand] fss0=atmosphere/package3 stock=1 emummc_force_disable=1 icon=bootloader/res/icon_switch.bmp Use code with caution. Boot entries are defined in the bootloader/hekate_ipl
Safely eject the SD card, put it back into your Switch, and inject Hekate.
If the console goes completely black after selecting an entry, a system module or patch is conflicting.