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.
Too Hot to Handle: Fixing the "Hekate Boot Entries Overheat" Issue If you are deep into the Nintendo Switch custom firmware scene, you have almost certainly met Hekate —the powerful bootloader that lets you launch Atmosphere, Linux, or Android. But have you ever launched Hekate, navigated to the boot entries screen, and felt your console suddenly turn into a hand warmer ? You aren't alone. A common but frustrating phenomenon is the Switch heating up significantly (sometimes dangerously) while sitting on the "Launch" menu or the hekate_ipl.ini selection screen. Let’s break down why this happens and, more importantly, how to fix it. The Core Problem: Auto Boot & Idle Loops The primary culprit is rarely a hardware failure. It is usually a misconfiguration in your bootloader/hekate_ipl.ini file. Here is what is happening under the hood:
The "Auto Boot" timer: You have autoboot=1 (or higher) set in your config. The Countdown: Hekate begins counting down to launch your default entry (e.g., "CFW - SysMMC"). The Stall: You press a button to stop the autoboot, or the timer gets stuck in a logic loop. The Heat: Because the bootloader is running in a "waiting for input" loop without proper power management flags, the CPU stays pegged at max frequency. On an unpatched Erista (V1) Switch, this generates significant heat within 60 seconds.
Is it Actually Dangerous? Short answer: Yes, if ignored. bootloader hekateiplini has boot entries hot
Erista units (V1): These run hotter by default. Sitting at 55°C+ on the boot screen can degrade the battery and thermal paste over time. Mariko units (V2/Lite/OLED): Better efficiency, but still, unnecessary heat is the enemy of lithium-ion batteries.
If your Switch is too hot to touch after 30 seconds on the Hekate menu, power it off immediately (hold Power for 15 seconds). How to Fix the "Hot Boot Entries" Problem Grab your SD card and edit bootloader/hekate_ipl.ini with a text editor (like Notepad++ or Visual Studio Code). Fix #1: Disable Autoboot (The most effective fix) If you don't need the Switch to boot automatically into a specific OS, just turn it off. Find this line: autoboot=1
Change it to: autoboot=0
Result: Hekate will sit idle on the main menu without spinning up a boot timer, keeping the CPU cool. Fix #2: Lower the CPU Speed During Boot If you need autoboot, tell Hekate to throttle down. Add this line to the [config] section of your hekate_ipl.ini : [config] autoboot=3 bootwait=3 autohosoff=2 {--- Add this line below ---} cpubench=0
cpubench=0 prevents Hekate from running a CPU stress test (which some old builds enabled by accident).
Fix #3: Update Hekate (Critical!) If you are using a version older than 5.5.0 , you are missing power management patches. The error message "No main boot entries found
Old bug: Hekate kept the high-performance cores (A57s) unlocked on the menu. New fix: Current versions (6.x) drop the CPU to the lowest P-state when idle.
Action: Download the latest hekate_ctcaer_x.x.x.bin from GitHub and replace the file on your SD card. Fix #4: Check your payload (Modchip users) If you have a HWFLY or Instinct-NX chip: