What you're changing and why it matters
The RCM jig is a physical tool that puts your Switch into Recovery Mode, and Hekate is the bootloader software that loads when the console starts. Changing your jig means replacing the physical device itself, while changing your Hekate setup means updating the bootloader files on your microSD card or adjusting which version runs at startup. Most people change one or the other when they want to use a different jig design, update to a newer Hekate version, or switch between different boot configurations.
You do not need to change both at the same time. A jig change is purely physical — you swap out the old tool for a new one. A Hekate change involves replacing or modifying files on your microSD card. Understanding which one you actually need to change will save you time and prevent mistakes.
Key Takeaways
- Changing your RCM jig means physically replacing the old jig with a new one; the bootloader software does not need to change.
- Changing Hekate means downloading a new version from the official repository, extracting it to your microSD card, and replacing the old bootloader files.
- Before you change either one, back up your current microSD card contents to your computer in case something goes wrong.
- Most jig changes require no software changes at all — the new jig works with your existing Hekate setup immediately.
- Hekate updates are optional but recommended when new versions fix bugs or add features you want to use.
Replacing your RCM jig with a different physical tool
If you are switching to a new jig design — perhaps from a 3D-printed jig to a manufactured one, or from one shape to another — you simply remove the old jig and insert the new one. The jig itself does not contain any software; it is only a physical connector that bridges two pins on the Switch's dock connector to trigger Recovery Mode.
Insert the new jig into the right Joy-Con rail the same way you inserted the old one. Push it in gently until you feel it seat. Your existing Hekate bootloader will work with the new jig without any changes. Test it by holding Volume Up and plugging in a USB-C cable while the console is powered off — if Recovery Mode appears on your screen, the new jig is working correctly.
If the new jig does not trigger Recovery Mode, check that it is fully inserted and that the pins are making contact. Some jigs require a small amount of pressure to maintain connection. If you are still having trouble, verify that your Switch model supports the jig design you purchased — some third-party jigs are designed for specific Switch revisions.
Downloading and installing a new version of Hekate
Hekate updates are released on GitHub in the official Hekate repository. Visit the releases page and download the latest version — it will be a ZIP file named something like hekate_ctcairo_[version].zip. Download it to your computer, not directly to your Switch.
Extract the ZIP file to a folder on your computer. Inside you will find a bootloader folder and other directories. The bootloader folder contains the files you need to copy to your microSD card. Before you proceed, connect your microSD card to your computer using a card reader and back up the entire contents to a separate folder — this way you can restore your old setup if the new version causes problems.
Open your microSD card in a file browser. You should already have a bootloader folder at the root level. Delete the old bootloader folder entirely, then copy the new bootloader folder from the extracted ZIP file to the root of your microSD card. Make sure the folder structure matches: the root should contain a folder named bootloader, and inside that folder should be subfolders like hekate_ctcairo.bin, nyx, and others.
Updating Hekate configuration files without replacing the bootloader
If you only want to change how Hekate behaves — such as which operating system loads by default, or which custom firmware appears in the boot menu — you do not need to replace the entire bootloader. Instead, you edit the configuration files that Hekate reads at startup.
The main configuration file is located at bootloader/hekate_ipl.ini on your microSD card. Connect your card to your computer and open this file in a text editor like Notepad. Inside you will see sections for different boot options, each starting with a label in square brackets like [CFW] or [Stock]. Each section contains settings that control what loads and how.
Common changes include setting autoboot=1 to make a specific option load automatically, or changing the icon path to display a different image in the boot menu. Save the file after making changes, eject your microSD card safely, reinsert it into your Switch, and restart the console to test your new configuration. If something goes wrong, you can always restore your backup and try again.
Switching between different Hekate versions on the same card
Some users keep multiple versions of Hekate on the same microSD card and choose which one to boot at startup. This is useful if you want to test a new version without fully committing to it, or if you need to use an older version for compatibility reasons.
To do this, rename your current bootloader folder to something like bootloader_old. Then extract the new Hekate version and copy its bootloader folder to the root of your microSD card. When you insert the card and power on your Switch, it will boot the new version. If you want to go back, you can rename bootloader_old back to bootloader and restart.
This method works because Hekate looks for a folder specifically named bootloader at the root level. By renaming the old folder, you are telling Hekate to use the new one instead. Keep in mind that having multiple versions on one card does use extra storage space, so this approach works best on larger microSD cards.
Troubleshooting when Hekate does not boot after a change
If you updated Hekate and now the console will not boot, the most common cause is an incomplete file copy or a corrupted bootloader folder. Connect your microSD card to your computer and verify that the bootloader folder exists at the root level and contains the expected files like hekate_ctcairo.bin and the nyx subfolder.
If the folder structure looks wrong, restore your backup and try the download and extraction process again. Make sure you extracted the ZIP file completely before copying — some extraction tools leave files nested in an extra folder level. If you are still stuck, you can always restore your old bootloader folder from your backup and return to your previous setup.
Another common issue is a microSD card that is not being read correctly. Try removing the card, waiting a few seconds, and reinserting it firmly. If the console still will not boot, try the card in a computer to make sure it is not physically damaged. A failing microSD card can cause Hekate to fail to load even if the files are correct.
When to change your jig versus when to change Hekate
Change your jig when you want to use a different physical tool to enter Recovery Mode. This might be because your current jig is broken, uncomfortable to use, or you prefer a different design. Changing the jig does not affect your software at all.
Change Hekate when you want to update the bootloader software itself, fix bugs, add new features, or adjust how your console boots. You might also change Hekate if you are switching to a completely different custom firmware or if the version you are using is no longer maintained. Most of the time, you will change Hekate much less often than you change your jig — a working bootloader can stay the same for months or years.
If you are new to this process, start by testing your current setup with your existing jig and Hekate before making any changes. Once you are comfortable with how everything works, making changes becomes straightforward.
Frequently Asked Questions
Do I need to change Hekate when I get a new jig?
No. The jig is only a physical tool that triggers Recovery Mode. Your Hekate bootloader will work with any jig that successfully enters Recovery Mode. Simply insert the new jig and test it — no software changes needed.
What happens if I copy Hekate files to the wrong folder on my microSD card?
Hekate will not find the files and your console will not boot. The bootloader folder must be at the root level of the microSD card, not inside another folder. If this happens, connect your card to a computer, check the folder structure, and move the bootloader folder to the correct location.
Can I keep my old Hekate configuration when I update to a new version?
Usually yes. The hekate_ipl.ini configuration file is separate from the bootloader binary itself. When you extract a new version, it includes a default configuration file, but you can replace it with your old one after copying the new bootloader folder. Test carefully to make sure your settings still work with the new version.
How do I know if a new Hekate version is worth updating to?
Check the release notes on the GitHub repository for the version you are considering. If it fixes a bug that affects you, adds a feature you want, or improves stability, it is worth updating. If your current version works fine and the changes do not matter to you, there is no need to update.
What should I do if my microSD card stops working after I change Hekate?
First, restore your backup of the old bootloader folder and test whether the console boots. If it does, the problem is with the new Hekate files — try downloading and extracting them again. If the console still will not boot even with your backup restored, the microSD card itself may be failing and you may need to replace it.