When the Hekate bootloader displays the message "No main boot entries found... check that bootloader/hekate_ipl.ini has boot entries," it means the bootloader cannot find or read the specific instructions needed to launch your Custom Firmware (CFW) or Stock OS. Why This Happens
Missing hekate_ipl.ini File: Hekate does not include boot options by default; you must manually add this file to the /bootloader/ folder on your SD card.
Incorrect File Extension: Often, the file is mistakenly named hekate_ipl.ini.txt because Windows hides known file extensions. It must end strictly in .ini.
Wrong Folder Location: The file must be placed in the /bootloader/ folder on the root of your SD card, not in a subfolder or the root itself.
Empty or Corrupted File: If the file exists but has no content or incorrect syntax (like missing section brackets []), Hekate will not see any valid "entries". How to Fix It
To resolve this, you need to create or edit the hekate_ipl.ini file in your /bootloader/ folder and add valid boot sections. 1. Basic Template
Below is a standard configuration for Atmosphere CFW and Stock booting. You can copy this into a text editor and save it as hekate_ipl.ini:
[config] autoboot=0 autoboot_list=0 bootwait=3 autohosoff=0 autonogc=1 updater2p=1 backlight=100 [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. Copied to clipboard 2. Key Terms in the Config CTCaer/hekate - A GUI based Nintendo Switch Bootloader
The error message "No main boot entries found... check that bootloader/hekate_ipl.ini has boot entries" indicates that your Nintendo Switch's bootloader cannot find or read the configuration file that tells it how to launch your Custom Firmware (CFW). This often happens because the file is missing, misnamed, or improperly formatted. Common Fixes bootloader hekateiplini has boot entries hot
Fix File Extension (Windows Users): Windows often hides file extensions. You might have accidentally named the file hekate_ipl.ini.txt. In File Explorer, go to the View tab. Check the box for File name extensions. Ensure the file is exactly hekate_ipl.ini and not a folder.
Correct File Location: The file must be placed exactly at the root of your SD card in the /bootloader/ folder (e.g., SD:/bootloader/hekate_ipl.ini).
Repair Corrupt Folders: If the file exists but won't load, the /bootloader folder may be corrupted. Delete the existing folder and replace it with a fresh copy from the official Hekate GitHub. Sample Configuration
If your file is empty or missing, create a new text file, rename it to hekate_ipl.ini, and paste the following standard entries used by many Switch modding guides:
[config] autoboot=0 autoboot_list=0 bootwait=3 autohosoff=0 autonogc=1 updater2p=1 backlight=100 [CFW - sysMMC] fss0=atmosphere/package3 kip1patch=nosigchk emummc_force_disable=1 icon=bootloader/res/icon_payload.bmp [CFW - emuMMC] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 icon=bootloader/res/icon_payload.bmp [Stock - sysMMC] fss0=atmosphere/package3 emummc_force_disable=1 stock=1 icon=bootloader/res/icon_switch.bmp Use code with caution. Copied to clipboard Advanced Troubleshooting
What is Hekate?
Hekate is a bootloader that enables users to boot their Nintendo Switch into various operating systems, including the official firmware, custom firmware, and homebrew applications. It's designed to be highly customizable and user-friendly.
Boot Entries in Hekate
In Hekate, boot entries are essentially configurations that define how the system should boot. These entries can be customized to point to different operating systems, kernel versions, or even specific homebrew applications.
Hot Swapping Boot Entries
One of the key features of Hekate is its ability to hot swap boot entries. This means that users can change the boot entry without having to restart the system or reconfigure the bootloader. Hot swapping allows for greater flexibility and convenience when switching between different operating systems or homebrew applications.
How Hekate Manages Boot Entries
Hekate stores boot entries in a configuration file, usually named hekate.ini. This file contains a list of entries, each with its own set of parameters, such as:
title: The name of the boot entry.path: The path to the kernel or operating system.args: Additional arguments to pass to the kernel or operating system.Users can edit the hekate.ini file to add, remove, or modify boot entries. Hekate also provides a built-in editor or can be configured to use an external editor.
Benefits of Hekate's Boot Entry Management
The ability to manage boot entries in Hekate offers several benefits, including: When the Hekate bootloader displays the message "No
Overall, Hekate's boot entry management features make it a powerful and user-friendly bootloader for the Nintendo Switch.
autoboot=1 – Enables auto-boot (hot boot). The number refers to the boot entry index (0 = first entry, 1 = second, etc.).autoboot_list=0 – Set to 1 if you want to auto-boot from a boot entry list file (advanced).bootwait=3 – Seconds to wait for volume button override before auto-booting.timeout=5 – Total seconds before the auto-boot entry launches.hekate_ipl.ini with a Hot Boot Entry[config] autoboot=1 autoboot_list=0 bootwait=3 timeout=5[Atmosphere CFW] emummc=1 payload=bootloader/payloads/fusee.bin icon=bootloader/res/icon_atmosphere.bmp
[Reboot to Payload] hotbl=False payload=reboot_payload.bin
In the context of Hekate, a hot boot entry refers to a configuration section that enables automatic booting without user interaction. These are often called “auto-boot” or “reboot-to-payload” entries. When enabled, Hekate will immediately launch a specified payload or firmware after a short timeout, skipping the main launch menu.
The Hekate IPL (Initial Program Loader) is the standard bootloader for the Nintendo Switch custom firmware scene. It acts as a multi-tool menu that allows you to launch CFW (Custom Firmware), Android, Linux, or stock firmware.
When users refer to boot entries being "hot," they usually mean one of two things:
boot.ini entries and the auto-boot configuration.The primary culprit is rarely a hardware failure. It is usually a misconfiguration in your bootloader/hekate_ipl.ini file. title : The name of the boot entry
Here is what is happening under the hood:
autoboot=1 (or higher) set in your config.