Hekate & Nyx for Nintendo Switch

Use the complete ZIP for Nyx and bootloader resources. The standard BIN is for your supported payload boot method; the BIN alone does not supply the SD-side Nyx files.

1. Start with the correct hardware guideHekate is a bootloader, not a universal stock-console exploit. Use your model’s supported setup route and keep a backup of your working microSD configuration.
2. Copy the full bootloader folderExtract the ZIP to the microSD root. Merge the supplied bootloader/ folder while preserving your existing configuration and payloads. Do not remove the entire folder first.
3. Keep your boot entriesbootloader/hekate_ipl.ini defines Launch entries. Separate configurations can live under bootloader/ini/. Retain the entries appropriate to your actual sysMMC/emuMMC setup rather than substituting an unrelated configuration.
4. Use the standard payloadFor a supported injection/boot method, select hekate_ctcaer_6.5.4.bin. On applicable existing setups Hekate also checks bootloader/update.bin for a newer version. A desktop injector is separate from this console build.
5. Open Nyx and confirm the setupBoot with the supplied SD resources and verify the version. Select your established Launch entry. Tools includes backup and USB functions; follow the documentation for the exact operation before changing partitions or restoring storage.

microSD root/
└── bootloader/
    ├── hekate_ipl.ini [your existing configuration]
    ├── update.bin
    ├── sys/ [Nyx and runtime resources]
    ├── ini/ [optional separate entries]
    └── payloads/ [your configured payloads]

Confirm the complete bootloader folder is on the card and that your Launch entry points to files actually present. A missing Nyx resource or an incorrect boot entry needs a configuration/file check. Restore your backed-up configuration if an update breaks a previously working setup, then follow the linked project documentation.

• Official 6.5.4 / Nyx 1.9.4 notes
• Bootloader files & configuration reference
• Nintendo Homebrew · supported boot methods

Console files are preserved locally with source URLs, versions, sizes and SHA-256 checksums. ZIP layouts and RetroArch’s 7z integrity and Switch NRO header were inspected. No console payload or application was executed, and physical-console installation has not been tested. The bootloader workflow artwork is an original illustration based on the documented file layout, not a console screenshot.