Ensure you haven't accidentally created a folder named hekate_ipl.ini containing a text document; it must be a standalone file.
Check if a file named hekate_ipl.ini exists. If it does not exist, right-click in the folder, create a new text document, and name it exactly hekate_ipl.ini (ensure you delete the .txt extension).
This file contains the configuration text that populates the menu in Hekate. If this file is missing, empty, misconfigured, or corrupted, Hekate will boot into its main menu but display a red error banner or pop-up warning you that it has "no boot entries." Without these entries, you cannot launch Atmosphere, Android, Linux, or your stock system from the Hekate interface. Common Causes
Using Hekate's boot entries is relatively straightforward. Here's a step-by-step guide:
The Nintendo Switch homebrew ecosystem relies heavily on Hekate, a powerful custom graphical bootloader. At the heart of Hekate's configuration is the hekate_ipl.ini file, located in the /bootloader/ directory of your SD card. This file dictates exactly how your console boots, what payloads it loads, and how it manages system configurations. bootloader hekateiplini has boot entries hot
The file must be placed exactly at the root of your SD card in the /bootloader/ folder (e.g., SD:/bootloader/hekate_ipl.ini ).
If you need to create a new hekate_ipl.ini file from scratch, copy and paste the following basic "Atmosphere" setup into a text file and save it as hekate_ipl.ini inside the /bootloader/ folder:
If you used a Mac to move files, "Archive Bit" issues or hidden metadata files can sometimes prevent Hekate from reading the .ini correctly.
Navigate to the bootloader folder located at the root of your SD card. Look for a file named hekate_ipl.ini . Ensure you haven't accidentally created a folder named
Ensure your file explorer has "File name extensions" checked. If your file is named hekate_ipl.ini.txt , Hekate will not read it. Rename it to remove the .txt .
Leaving your console unattended in RCM or Hekate can drain the battery and generate persistent heat. Ensure autohosoff=1 is set in your configuration. This parameter automatically powers down the console if it accidentally boots into Hekate or RCM via an unofficial charger or payload injection error, preventing it from overheating in a carrying case. Verify Thermal Paste and Hardware Health
The file became corrupted due to an unorderly shutdown, a faulty SD card reader, or a fake SD card.
If manual configuration feels overwhelming, you can use a pre-configured homebrew package like Hekate's official releases or popular community packs (such as Hats or DeepSea). These packages include pre-configured hekate_ipl.ini files. This file contains the configuration text that populates
A “hot path” in code is a loop that runs constantly. If Hekate loads IPlini, but IPlini’s target (e.g., payload.bin ) fails, the system recycles back to Hekate. This creates an endless boot cycle that generates heat.
How to Fix Hekate "bootloader/hekate_ipl.ini has no boot entries" Error
Before diving into the fixes, it helps to know what triggered the issue. The most frequent culprits include:
For the fastest possible startup, you can configure Hekate to automatically launch a default boot entry without showing the menu. This is ideal for users who always want to boot into Atmosphere CFW.