Bootloader Hekateiplini Has Boot Entries Hot Guide

The error message "No main boot entries found... check that bootloader/hekate_ipl.ini has boot entries" is a common issue with the Hekate bootloader on the Nintendo Switch. It typically means the configuration file that tells Hekate how to launch your Custom Firmware (CFW) is missing, empty, or incorrectly formatted. Common Fixes

If you are seeing this error, check the following common causes and solutions based on community consensus:

File Extension Issue (Most Common): Ensure the file is named exactly hekate_ipl.ini and is not actually hekate_ipl.ini.txt. In Windows, you must enable "File name extensions" in the View tab of File Explorer to see and remove the hidden .txt extension.

Missing Entries: Hekate does not come with boot options by default; you must add them yourself or use a premade template. A standard entry for Atmosphere often looks like this:

[Atmosphere CFW] payload=bootloader/payloads/fusee.bin icon=bootloader/res/icon_payload.bmp Use code with caution. Copied to clipboard

Wrong Directory: The file must be located at the root of your SD card in the /bootloader/ folder. It cannot be inside a subfolder or renamed.

Outdated Configuration: If you recently updated, older lines like fss0=atmosphere/fusee-secondary.bin may no longer work and should be updated to fss0=atmosphere/package3.

Archive Bit (Mac Users): If you use a Mac to transfer files, the "archive bit" can cause read errors. In Hekate, go to Tools -> Arch bit • RCM • Touch • Partitions -> Fix Archive Bit to resolve this. Where to Find Valid Configs

For a ready-to-use configuration, you can refer to authoritative community resources:

Hekate Official Templates: Official examples from the developer.

NH Switch Guide: Provides a standard hekate_ipl.ini file for most setups. bootloader hekateiplini has boot entries hot

The error "No main boot entries found" in Hekate typically means the hekate_ipl.ini

file is missing, incorrectly named, or empty. By default, Hekate does not include any boot options; you must create them manually or download a template. 1. Correct File Placement and Naming : The file must be located exactly at /bootloader/hekate_ipl.ini on the root of your SD card. Common Mistake : Ensure the file is not accidentally named hekate_ipl.ini.txt

. In Windows, enable "File name extensions" in File Explorer to verify the extension is strictly Folder Error hekate_ipl.ini is a file, not a folder containing a text document. 2. Recommended Configuration Template

You can copy and paste the following standard configuration into your hekate_ipl.ini

file. This setup includes entries for Atmosphere CFW on both emuMMC and sysMMC, as well as a clean Stock boot option.

[Corruption] How to fix the bootloader folder without formatting #614

When modding a Nintendo Switch, few errors are as frustrating as seeing the message: "No main boot entries found... Check that bootloader/hekate_ipl.ini has boot entries." This usually happens right when you're ready to launch your custom firmware (CFW).

The issue stems from a missing or improperly configured hekate_ipl.ini file, which acts as the roadmap for the Hekate bootloader. Without it, Hekate has no instructions on how to load Atmosphere or your system's NAND. Why You’re Seeing This Error

Hekate does not come with boot entries by default. You must manually create or download a configuration file that tells the bootloader where to find the necessary files (like package3 or fusee.bin) to start your console. Common causes include:

Missing File: The hekate_ipl.ini file is entirely absent from the /bootloader/ folder. The error message "No main boot entries found

Incorrect Naming: The file is named hekate_ipl.ini.txt because Windows is hiding file extensions.

Folder Misplacement: The file was accidentally placed inside a folder also named hekate_ipl.ini. How to Fix Your Boot Entries

To resolve this, you need to create or edit the hekate_ipl.ini file located at sdcard:/bootloader/hekate_ipl.ini. 1. Enable File Extensions

Before editing, ensure you can see file extensions on your computer. In Windows, go to the View tab in File Explorer and check File name extensions. This prevents you from accidentally creating a .txt file that Hekate can't read. 2. Create the Configuration File

Open a text editor (like Notepad) and paste the following standard configuration used by many modern guides:

[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.

(Note: Ensure you have fusee.bin in your /bootloader/payloads/ folder if using the "Atmosphere CFW" entry above.) 3. Save and Verify

Save this file as hekate_ipl.ini and place it directly into the /bootloader/ folder on your SD card root. Once you re-inject the Hekate payload, the "Launch" menu should now show your new boot options. Advanced: Using "More Configs"

If you prefer to keep your main menu clean, you can place individual .ini files in the bootloader/ini/ folder. These will appear under the More Configs button in the Hekate GUI rather than the main Launch screen.

Part 7: When “Hot” Is Actually a Hardware Fault

Sometimes, the bootloader is not the cause. If you have verified your hekate_ipl.ini and IPlini chain is flawless, but the system still reports hot entries, inspect: Part 7: When “Hot” Is Actually a Hardware

Part 6: Preventing Future “Hot” Boot Entries

To avoid heating up your bootloader again, adhere to these rules:

  1. Never chain IPlini from IPlini. That creates an infinite recursion that overheats the CPU within seconds.
  2. Keep your Hekate and IPlini versions in sync. A mismatch (e.g., Hekate 6.0.2 with IPlini 5.5.0) causes silent boot entry corruption.
  3. Use fss0 over payload whenever possible. fss0 boots Atmosphere directly without invoking IPlini, reducing thermal load.
  4. Monitor temperatures in Hekate. Press (Vol +) + (Vol -) on the main screen to display the PMIC temperature. Anything above 55°C at idle indicates a boot entry is still “hot.”

How to Use Hot Boot

  1. Edit /bootloader/hekate_ipl.ini on your Switch’s SD card.
  2. Add the [config] section with autoboot set to the desired entry index (e.g., 0 for the first boot entry).
  3. Adjust bootwait and timeout as needed.
  4. Save the file and reboot Hekate — the hot boot entry will launch automatically.

Step 4: Voltage & Clock Stabilization (Advanced)

For modchip users (HWFLY, SX Core):

1. Thermal Overload (Literal Heat)

The most literal interpretation. If your SD card or eMMC chip gets physically warm during boot entry selection, it indicates:

Symptom: The back of the Switch (near the SD card slot) feels warm to the touch within 10 seconds of booting Hekate.

Part 1: The Trinity of Switch Hacking (Hekate + IPL + INI)

To understand the keyword, we must break it down into three distinct parts.

The Most Common Reason for the Message

The phrase is commonly seen in debug logs or verbose output when Hekate is scanning the ini for payloads. Specifically, if you have a "More Configs" folder or if you are using payload forwarding, Hekate flags those entries as "hot" to ensure they can switch contexts quickly.

In short: 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.

The "Dirty" Workaround (No SD Card Editing)

If you can't edit the config right now:

  1. Launch Hekate.
  2. Do not go to the "Launch" screen.
  3. Stay on the Nyx Options tab (the one with the wrench). For some reason, Nyx (Hekate's GUI) runs cooler than the boot entry selector.

Or simply: