Check | That Bootloader/hekate_ipl.ini Has Boot Entries Extra Quality

[Atmosphere FSS0 EmuMMC] [Atmosphere FSS0 SysMMC] [Stock SysNAND] (zero entries):

No "Launch" menu. No "Atmosphere" icon. No "Stock" option. Just a blank payload menu or a direct reboot to Horizon. This is the silent failure of a missing configuration. This is what happens when you forget to check that bootloader/hekate_ipl.ini has boot entries. In the world of Switch custom firmware (CFW), hekate is the gatekeeper. It doesn’t boot your operating system directly; instead, it reads a simple text file called hekate_ipl.ini to know what to boot.

Think of it as a restaurant menu. Hekate is the waiter. Your SD card is the kitchen. Without the menu (the .ini file), the waiter has no idea what dishes (operating systems or payloads) to serve you. check that bootloader/hekate_ipl.ini has boot entries

The file lives at: /bootloader/hekate_ipl.ini A healthy hekate_ipl.ini contains at least one boot entry . Each entry is a block of text describing a bootable configuration. A minimal entry looks like this:

You breathe a sigh of relief. But then: Nothing. Just a blank payload menu or a direct reboot to Horizon

You’ve just soldered a modchip, pushed a payload, or watched the blue screen of your RCM jig flash. The Nintendo Switch vibrates, and the familiar hekate logo—the custom bootloader’s icy blue interface—splashes across the screen.

(three entries):

One line of text. Infinite boots.