How to Boot Into Hekate on Nintendo Switch: Complete Guide

If you are trying to figure out how to boot into Hekate on Switch, the correct method depends on your Nintendo Switch setup. An unpatched V1 Switch normally enters RCM mode and receives the Hekate payload from a PC or RCM Loader, while a modchipped Switch can usually load Hekate automatically from the microSD card.

If you are already running Atmosphère CFW, you can also reboot directly back into Hekate without manually entering RCM again.

Quick Answer: To boot into Hekate on an unpatched Nintendo Switch, fully power off the console, insert an RCM jig into the right Joy-Con rail, hold Volume Up, tap Power, and inject the latest hekate_ctcaer_x.x.x.bin payload using an RCM Loader or compatible payload injector. If Atmosphère is already running, restarting the console can also return you to Hekate when reboot_payload.bin is configured correctly.

The latest official release is Hekate 6.5.3 with Nyx 1.9.3, supporting Horizon OS through version 22.5.0.

Table of Contents

What Is Hekate on Nintendo Switch?

Hekate is a custom Nintendo Switch bootloader commonly used with Atmosphère CFW. It provides a graphical interface called Nyx and lets users manage several parts of a homebrew-enabled Switch.

Hekate can be used to:

Launch Atmosphère CFW
Boot emuMMC or sysMMC configurations
Manage the microSD card
Create and restore NAND backups
Access USB storage
Launch additional payloads
Manage boot configurations
Boot supported Linux or Android installations

The current Hekate project supports CFW, payload tools, Android, Linux, and multiple Switch hardware configurations.

What You Need Before Booting Into Hekate

Your required files and hardware depend on the type of Nintendo Switch you have.

For an Unpatched V1 Switch

You typically need:

Compatible unpatched Nintendo Switch
microSD card
Hekate files
RCM jig
USB-C cable or RCM Loader
PC, Android device, or another payload injector

For a Modchipped Switch

You usually need:

Modchip already installed and configured
microSD card
Hekate bootloader folder
Hekate payload renamed according to your modchip setup

Many modchip configurations use:

payload.bin

on the root of the SD card.

The NH Switch Guide instructs modchip users to place both the Hekate bootloader folder and payload on the SD root, then rename the Hekate payload to payload.bin.

How to Boot Into Hekate on an Unpatched Switch

The standard method for an unpatched V1 Nintendo Switch is to enter RCM mode and inject the Hekate payload.

Step 1: Download the Latest Hekate Files

Download Hekate from the official CTCaer GitHub repository.

The archive contains files similar to:

bootloader/
hekate_ctcaer_6.5.3.bin

Copy the:

bootloader

folder to the root of your Nintendo Switch microSD card.

Your SD card may look like:

SD:/
├── atmosphere/
├── bootloader/
├── switch/
└── hbmenu.nro

Hekate’s official update instructions recommend merging the new bootloader folder with the existing one rather than deleting it first.

Step 2: Fully Power Off the Nintendo Switch

Hold the Power button and select:

Power Options → Turn Off

Do not simply put the Switch into sleep mode.

The console needs to enter RCM from a powered-off state.

Step 3: Insert the RCM Jig

Remove the right Joy-Con.

Insert the RCM jig into the right Joy-Con rail.

The jig is used to help compatible unpatched Switch hardware enter Recovery Mode.

An RCM jig does not contain Hekate itself. The actual Hekate .bin file must still be injected from another device.

Step 4: Enter RCM Mode

With the jig inserted:

Hold Volume Up.
Briefly press the Power button.
Release the buttons.

If RCM starts correctly, the Switch screen should remain completely black.

Do not assume a black screen means the console failed to start. RCM itself does not display a menu.

Step 5: Inject the Hekate Payload

Use your chosen payload injector to send:

hekate_ctcaer_6.5.3.bin

to the Switch.

You can inject Hekate using:

RCM Loader
Windows PC
Compatible Android payload injector
Other supported USB payload injection tools

After successful injection, the Hekate/Nyx interface should appear.

How to Boot Into Hekate With an RCM Loader

An RCM Loader stores the Hekate payload and injects it without requiring a PC every time.

Place the Hekate payload inside the correct loader profile.

Many RCM Loaders expect the filename:

payload.bin

For example:

RCMLOADER/
└── USER1/
    └── payload.bin

or:

RCMLOADER/
└── ATMOSPHERE_HEKATE/
    └── payload.bin

Then:

Power off the Switch.
Insert the RCM jig.
Hold Volume Up.
Tap Power.
Confirm the screen remains black.
Connect the RCM Loader.
Hekate should launch automatically.

If nothing happens, verify that the RCM Loader is using the profile where the Hekate payload is stored.

How to Boot Into Hekate From Atmosphere

If Atmosphère Switch is already running, you usually do not need to repeat the complete RCM process.

The NH Switch Guide confirms that users running CFW can return to Hekate either through a reboot-to-payload homebrew app or, on compatible setups, by simply selecting Restart from the Switch power menu.

Using Restart

Hold the Power button and select:

Power Options → Restart

On a correctly configured unpatched V1 Atmosphère setup, Atmosphère uses:

/atmosphere/reboot_payload.bin

as the reboot payload.

If that file contains Hekate, restarting sends you directly back to Hekate.

Using Reboot to Payload

You can also launch a Reboot to Payload homebrew application from the Homebrew Menu.

The process is:

Open the Homebrew Menu.
Launch Reboot to Payload.
The console restarts.
Hekate loads from the configured reboot payload.

The NH Switch Guide notes that this app-based method does not work the same way on modchipped Switch consoles because modchips already handle payload booting during restart.

How to Set Hekate as the Atmosphere Reboot Payload

If restarting Atmosphère launches another payload instead of Hekate, check:

SD:/atmosphere/reboot_payload.bin

For a setup intended to restart directly into Hekate, that file should contain the appropriate Hekate payload.

A common structure is:

SD:/
├── atmosphere/
│   └── reboot_payload.bin
│
├── bootloader/
└── switch/

The configured payload determines what Atmosphère launches when using reboot-to-payload behavior.

How to Boot Into Hekate on a Modchipped Switch

Modchipped Switch consoles work differently from unpatched V1 units.

You generally do not need an RCM jig or external payload injector every time.

A typical modchip Hekate setup places:

hekate_ctcaer_x.x.x.bin

on the SD card and renames it to:

payload.bin

The NH Switch Guide’s modchip setup instructions use this structure:

SD:/
├── bootloader/
└── payload.bin

After inserting the microSD card and powering on the console, the modchip loads the payload and Hekate should appear.

If the modchip reports No Payload or Hekate does not appear, verify that payload.bin exists on the SD card root.

How to Boot Atmosphere From Hekate

Once Hekate is open, you can boot your configured Atmosphère environment.

From the Hekate main menu:

Select Launch.
Choose your configured CFW entry.
Select the appropriate emuMMC or sysMMC option.
Wait for Atmosphère to start.

Common entries may include names such as:

Atmosphere CFW
Atmosphere EmuMMC
Atmosphere SysMMC

The exact labels depend on your:

/bootloader/hekate_ipl.ini

configuration.

Hekate’s official configuration template confirms that boot entries are controlled through the hekate_ipl.ini configuration system.

Why Hekate Is Not Booting

If you enter RCM but Hekate never appears, check the setup systematically.

Switch Is Not Entering RCM

If the Nintendo logo appears, the Switch has booted normally instead of entering RCM.

Try again:

Fully power off the console.
Reinsert the jig correctly.
Hold Volume Up.
Tap Power.

A successful RCM entry normally leaves the screen black until a payload is injected.

Wrong Hekate Payload

Make sure you are injecting:

hekate_ctcaer_x.x.x.bin

rather than an unrelated or outdated payload.

Using the current Hekate version also reduces compatibility issues with newer Switch firmware.

Missing Bootloader Folder

Injecting Hekate without the proper SD files can prevent the full Nyx interface from loading correctly.

Verify:

SD:/bootloader/

exists.

The official Hekate package provides both the payload and required bootloader files.

Outdated Hekate Version

Older Hekate releases may not support newer Nintendo firmware.

The current Hekate 6.5.3 / Nyx 1.9.3 release supports Horizon OS through 22.5.0.

RCM Loader Has the Wrong Payload

If you use an RCM Loader, confirm that:

Hekate is stored in the selected profile.
The filename is correct.
The loader is charged.
The correct LED/profile is active.

For loaders requiring a fixed filename, the payload may need to be:

payload.bin

Modchip Shows No Payload

For a modchipped Switch, verify:

SD:/payload.bin

exists and contains Hekate.

The NH Switch Guide specifically identifies missing payload.bin or a missing SD card as common causes of No Payload behavior.

Hekate Boots but Atmosphere Does Not

If Hekate itself loads normally but Atmosphère fails, the problem is usually no longer the Hekate payload.

Check:

Atmosphère version
Nintendo firmware compatibility
hekate_ipl.ini
package3
emuMMC configuration
Old sysmodules
Custom themes
SD card files

A Hekate boot entry depends on the files and values specified in:

/bootloader/hekate_ipl.ini

Incorrect paths or missing files can cause Hekate launch errors.

Can You Boot Hekate Without an RCM Jig?

Yes, depending on your setup.

You may not need an RCM jig when:

Your Switch has a compatible modchip.
You are already inside Atmosphère and reboot to Hekate.
Your console is already in RCM.
Your setup uses another compatible method to trigger RCM.

For a standard unpatched V1 Switch that is completely powered off, however, an RCM jig is one of the common methods used to enter RCM before injecting Hekate.

Can You Boot Directly Into Hekate After Restarting?

Yes.

If Atmosphère is configured with Hekate as:

/atmosphere/reboot_payload.bin

selecting Restart can return you directly to Hekate on compatible V1 setups.

For modchipped systems, restarting generally causes the modchip to load its configured payload again, which can also be Hekate.

This is more convenient than entering RCM manually every time.

Frequently Asked Questions

How Do I Boot My Switch Into Hekate?

On an unpatched V1 Switch, power off the console, insert an RCM jig, hold Volume Up while tapping Power, and inject the Hekate .bin payload using an RCM Loader, PC, or compatible injector.

Why Does My Switch Stay on a Black Screen in RCM?

A black screen is normal while the Switch is waiting for an RCM payload. Inject Hekate using your configured payload injector.

Can I Boot Hekate Without a PC?

Yes. An RCM Loader can inject Hekate without a PC. Modchipped Switch consoles can also boot Hekate directly from a payload stored on the SD card.

How Do I Reboot From Atmosphere to Hekate?

Use Power Options → Restart when Hekate is configured as Atmosphère’s reboot payload, or use a Reboot to Payload homebrew app on compatible setups.

Where Does the Hekate Payload Go?

For manual RCM injection, you select:

hekate_ctcaer_x.x.x.bin

from your payload injector.

For many modchip setups, the file goes on the SD root as:

SD:/payload.bin

What Is the Latest Hekate Version?

As of September 2026, the latest official release is Hekate 6.5.3 with Nyx 1.9.3, released June 16, 2026. It supports Horizon OS through 22.5.0.

Does Hekate Boot Atmosphere?

Yes. Hekate can launch Atmosphère using entries configured in hekate_ipl.ini. It can boot configurations such as Atmosphère on emuMMC or sysMMC when the required files are installed correctly.

Conclusion: How to Boot Into Hekate on Switch

Learning how to boot into Hekate on Nintendo Switch mainly depends on whether you have an unpatched V1 console, a modchipped Switch, or an Atmosphère setup that is already running.

For an unpatched Switch, the normal process is enter RCM mode → inject the Hekate payload → open the Hekate/Nyx interface. If you already use Atmosphère, restarting to a configured reboot_payload.bin provides a much faster way to return to Hekate.

For modchipped consoles, Hekate can usually boot directly from payload.bin on the microSD card. Keep the Hekate payload and bootloader folder updated together so your CFW boot environment remains compatible with your Nintendo Switch firmware.

Latest post: