How to Change Files with RCM Jig and Hekate on Nintendo Switch

If you've been exploring custom firmware on the Nintendo Switch, you've likely come across two names that keep appearing together: RCM jig and Hekate. Understanding how these tools interact — and how to manage files through them — makes the difference between a smooth setup and hours of frustrating trial and error.

What Is an RCM Jig and Why Does It Matter?

RCM stands for Recovery Mode, a low-level boot state built into the NVIDIA Tegra X1 chip that powers the original Nintendo Switch. When the Switch enters RCM, it's essentially waiting for instructions before the normal operating system takes over.

An RCM jig is a small physical tool — usually a bent wire or a 3D-printed connector — inserted into the right Joy-Con rail. Its job is to short specific pins (pins 1 and 10 on the Joy-Con rail) to signal the Tegra chip to enter RCM mode when you hold the Volume Up button and press Power.

Without entering RCM mode first, none of the payload injection or file management through Hekate is possible. The jig is your entry point.

What Is Hekate?

Hekate is a custom bootloader for the Nintendo Switch. Once your Switch is in RCM mode, you inject Hekate as a payload using a tool like TegraRcmGUI (on Windows) or Rekado (on Android). From that point, Hekate acts as a control center — letting you:

• Boot into custom firmware (like Atmosphere)
• Manage partitions
• Create and restore NAND backups
• Access the SD card file system directly from the Switch itself

That last capability is where the concept of changing files through Hekate becomes relevant.

How File Management Works Through Hekate 🗂️

Hekate includes a built-in file browser that lets you navigate your microSD card without removing it or connecting the Switch to a PC. This is particularly useful when:

• You need to update or replace configuration files (like hekate_ipl.ini)
• You want to swap boot entries or payload files
• You're troubleshooting a broken boot setup and can't get into the OS

The Key Files You'll Typically Work With

Changing these files — whether editing boot entries, swapping payload binaries, or updating configuration values — is the core of what people mean when they search for how to change files using an RCM jig and Hekate.

Step-by-Step: The General Process for Changing Files

1. Enter RCM Mode

Insert your RCM jig into the right Joy-Con rail. Hold Volume Up, then press Power. The screen will stay black — that's correct. The Switch is now in RCM.

2. Inject the Hekate Payload

Connect your Switch to a PC via USB-C. Open TegraRcmGUI (or your preferred injection tool), select your Hekate .bin payload file, and click inject. Hekate's interface will appear on the Switch screen.

3. Navigate to the File Browser

Inside Hekate, tap Tools → File Browser (in newer Hekate versions, this may appear as USB Tools or within the Payloads menu depending on version). From here, you can browse your SD card's directory structure.

4. Select and Modify Your Target File

Navigate to the file you want to change. Hekate's file browser supports:

• Viewing text-based config files
• Deleting files
• Copying files between locations

For more complex edits — like rewriting the contents of hekate_ipl.ini — most users find it easier to remove the SD card, edit files on a PC using a plain text editor (Notepad++, VS Code), then reinsert the card.

5. Reboot and Test

After making changes, use Hekate's Reboot menu to reboot into your chosen firmware, into RCM again, or to power off cleanly.

Variables That Affect Your Experience ⚙️

The process described above is straightforward on paper, but several factors shape how it actually goes:

Switch hardware revision matters significantly. The original "unpatched" Switch (HAC-001) is the only model compatible with RCM jig exploitation. The patched HAC-001-01, Switch Lite, and Switch OLED models cannot use this method at all.

Hekate version changes what menus and features are available. Older versions have different menu layouts. Always check documentation that matches your specific Hekate version.

SD card format plays a role too. Hekate works best with FAT32 formatted cards for most setups, though some configurations use exFAT. File visibility and browser functionality can vary.

Your existing file structure — whether you're starting from scratch or modifying an existing Atmosphere setup — determines which files need touching and which should be left alone. Editing the wrong value in hekate_ipl.ini can break your boot chain.

Technical comfort level is genuinely a variable here. Users comfortable editing .ini files and understanding boot chains can make targeted changes quickly. Those newer to the ecosystem may find that one file change cascades into understanding a half-dozen related components.

Different Setups Lead to Different Workflows

Someone running a single CFW setup with Atmosphere only needs to manage a handful of config files and occasionally update payloads. Their Hekate interaction is minimal.

A user running multiple boot configurations — perhaps EmuNAND and SysNAND, or different firmware versions for different games — will work with Hekate's file system regularly, maintaining separate boot entries and payload sets.

Someone recovering from a failed update may need to use Hekate's file browser as a lifeline — replacing broken files without a functioning OS to help.

Each scenario involves the same tools but a meaningfully different scope of file changes.

What files you need to change, how often, and through which method — directly on the Switch via Hekate's browser or on a PC with the card removed — depends entirely on what your setup looks like and what you're trying to accomplish with it. 🎮