Convert Figma logo to code with AI

CTCaer logohekate

hekate - A GUI based Nintendo Switch Bootloader

7,467
606
7,467
31

Top Related Projects

Atmosphère is a work-in-progress customized firmware for the Nintendo Switch.

1,347

Library for Switch Homebrew

The Nintendo Switch Homebrew Menu

Quick Overview

Hekate is a custom bootloader for the Nintendo Switch. It provides a user-friendly interface for booting custom firmware, managing partitions, and performing various system-level operations on the Switch console. Hekate is an essential tool for Switch modding and homebrew development.

Pros

  • User-friendly interface with touchscreen support
  • Comprehensive feature set including custom firmware launching, partition management, and backup/restore functionality
  • Regular updates and active development
  • Supports various payloads and custom firmware options

Cons

  • Requires a vulnerable Nintendo Switch console (not all models are compatible)
  • Can potentially void warranty or lead to console bans if misused
  • Complexity may be overwhelming for novice users
  • Requires additional hardware (like a RCM jig) for initial setup

Getting Started

  1. Check if your Nintendo Switch is vulnerable to the exploit (typically units sold before July 2018).
  2. Obtain an RCM jig and a USB-C cable.
  3. Download the latest Hekate release from the GitHub repository.
  4. Extract the contents of the zip file to the root of your Switch's SD card.
  5. Create a hekate_ipl.ini file in the root of your SD card with your desired configuration.
  6. Put your Switch into RCM mode using the jig.
  7. Use a payload injector (e.g., TegraRcmGUI for Windows) to send the Hekate payload to your Switch.
  8. Once Hekate boots, you can use its interface to launch custom firmware or perform other operations.

Note: This is a simplified overview. Always refer to up-to-date guides and the official documentation for complete instructions and safety precautions.

Competitor Comparisons

Atmosphère is a work-in-progress customized firmware for the Nintendo Switch.

Pros of Atmosphere

  • More comprehensive custom firmware solution with advanced features
  • Better support for homebrew applications and emulators
  • Regular updates and active development community

Cons of Atmosphere

  • Slightly more complex setup process for beginners
  • May require additional patches for certain games or applications

Code Comparison

Atmosphere (main.c):

void __init_heap(void) {
    extern char *fake_heap_start;
    extern char *fake_heap_end;

    fake_heap_start = (char *)0xF0000000;
    fake_heap_end   = (char *)((u32)fake_heap_start + 0x10000000);
}

Hekate (main.c):

void *sd_file_read(const char *path, u32 *fsize)
{
    FIL fp;
    if (f_open(&fp, path, FA_READ) != FR_OK)
        return NULL;

    *fsize = f_size(&fp);
    void *buf = malloc(*fsize);

Summary

Atmosphere and Hekate are both popular custom firmware solutions for the Nintendo Switch. Atmosphere offers a more comprehensive package with advanced features and better homebrew support, while Hekate provides a simpler bootloader with a focus on ease of use. The code comparison shows different approaches to memory management and file handling in their respective implementations.

1,347

Library for Switch Homebrew

Pros of libnx

  • Comprehensive library for Nintendo Switch homebrew development
  • Extensive documentation and community support
  • Regular updates and maintenance

Cons of libnx

  • Steeper learning curve for beginners
  • Requires more in-depth knowledge of Switch hardware

Code Comparison

hekate (bootloader configuration):

{
    "autoboot": 0,
    "autoboot_list": 0,
    "bootwait": 3,
    "backlight": 100,
    "autohosoff": 0,
    "autonogc": 1
}

libnx (basic application initialization):

#include <switch.h>

int main(int argc, char **argv)
{
    consoleInit(NULL);
    // Your code here
    consoleExit(NULL);
    return 0;
}

Key Differences

  • hekate focuses on bootloader functionality, while libnx provides a comprehensive development framework
  • hekate is more user-friendly for end-users, whereas libnx targets developers
  • libnx offers more flexibility for creating complex homebrew applications
  • hekate provides a graphical interface, while libnx is primarily used through code

Both projects serve different purposes in the Nintendo Switch homebrew ecosystem, with hekate handling the initial boot process and libnx facilitating application development.

The Nintendo Switch Homebrew Menu

Pros of nx-hbmenu

  • Focused specifically on homebrew menu functionality
  • Lightweight and optimized for quick loading of homebrew applications
  • Actively maintained by the Switch homebrew community

Cons of nx-hbmenu

  • Limited functionality compared to hekate's broader feature set
  • Less customization options for users
  • Requires additional tools for tasks like backup and restoration

Code Comparison

nx-hbmenu:

void menuUpdate(void) {
    menuEntry_s* me = NULL;
    menu_s* menu = menuGetCurrent();
    if (menu->nEntries > 0) {
        me = menu->firstEntry;
        int i;
        for (i = 0; i < menu->curEntry; i++) {
            me = me->next;
        }
    }
    // ... (additional code)
}

hekate:

void gui_init_argon(void)
{
    sd_mount();
    bpmp_mmu_enable();
    minerva_init();
    gfx_init_ctxt((u32 *)IPL_FB_ADDRESS, 720, 1280, 720);
    gfx_con_init();
    display_backlight_brightness(100, 1000);
}

The code snippets show different focuses: nx-hbmenu on menu handling, while hekate initializes various system components.

Convert Figma logo designs to code with AI

Visual Copilot

Introducing Visual Copilot: A new AI model to turn Figma designs to high quality code using your components.

Try Visual Copilot

README

hekate - Nyx

Image of Hekate

Custom Graphical Nintendo Switch bootloader, firmware patcher, tools, and many more.

Features

  • Fully Configurable and Graphical with Touchscreen and Joycon input support
  • Launcher Style, Background and Color Themes
  • HOS (Switch OS) Bootloader -- For CFW Sys/Emu, OFW Sys and Stock Sys
  • Android & Linux Bootloader
  • Payload Launcher
  • eMMC/emuMMC Backup/Restore Tools
  • SD Card Partition Manager -- Prepares and formats SD Card for any combo of HOS (Sys/emuMMC), Android and Linux
  • emuMMC Creation & Manager -- Can also migrate and fix existing emuMMC
  • Switch Android & Linux flasher
  • USB Mass Storage (UMS) for SD/eMMC/emuMMC -- Converts Switch into a SD Card Reader
  • USB Gamepad -- Converts Switch with Joycon into a USB HID Gamepad
  • Hardware and Peripherals info (SoC, Fuses, RAM, Display, Touch, eMMC, SD, Battery, PSU, Charger)
  • Many other tools like Archive Bit Fixer, Touch Calibration, SD/eMMC Benchmark, AutoRCM enabler and more

Bootloader folders and files

Folder/FileDescription
bootloaderMain folder.
|__ bootlogo.bmpIt is used if no logopath key is found. User provided. Can be skipped.
|__ hekate_ipl.iniMain bootloader configuration and boot entries in Launch menu.
|__ nyx.iniNyx GUI configuration
|__ patches.iniAdd external patches. Can be skipped. A template can be found here
|__ update.binIf newer, it is loaded at boot. Normally for modchips. Auto updated and created at first boot.
bootloader/ini/For individual inis. More configs menu. Autoboot is supported.
bootloader/res/Nyx user resources. Icons and more.
|__ background.bmpNyx - Custom background. User provided.
|__ icon_switch.bmpNyx - Default icon for CFWs.
|__ icon_payload.bmpNyx - Default icon for Payloads.
bootloader/sys/hekate and Nyx system modules folder. !Important!
|__ emummc.kipmemuMMC KIP1 module.
|__ libsys_lp0.bsoLP0 (sleep mode) module.
|__ libsys_minerva.bsoMinerva Training Cell. Used for DRAM Frequency training.
|__ nyx.binNyx - hekate's GUI.
|__ res.pakNyx resources package.
|__ thk.binAtmosphère Tsec Hovi Keygen.
|__ /l4t/Folder with firmware relevant to L4T (Linux/Android).
bootloader/screenshots/Folder where Nyx screenshots are saved
bootloader/payloads/For the Payloads menu. All CFW bootloaders, tools, Linux payloads are supported. Autoboot only supported by including them into an ini.
bootloader/libtools/Reserved

Bootloader configuration

The bootloader can be configured via 'bootloader/hekate_ipl.ini' (if it is present on the SD card). Each ini section represents a boot entry, except for the special section 'config' that controls the global configuration.

There are four possible type of entries. "[ ]": Boot entry, "{ }": Caption, "#": Comment, "newline": .ini cosmetic newline.

You can find a template Here

hekate Global Configuration keys/values (when entry is [config]):

Config optionDescription
autoboot=00: Disable, #: Boot entry number to auto boot.
autoboot_list=00: Read autoboot boot entry from hekate_ipl.ini, 1: Read from ini folder (ini files are ASCII ordered).
bootwait=30: Disable (It also disables bootlogo. Having VOL- pressed since injection goes to menu.), #: Time to wait for VOL- to enter menu. Max: 20s.
noticker=00: Animated line is drawn during custom bootlogo, signifying time left to skip to menu. 1: Disable.
autohosoff=10: Disable, 1: If woke up from HOS via an RTC alarm, shows logo, then powers off completely, 2: No logo, immediately powers off.
autonogc=10: Disable, 1: Automatically applies nogc patch if unburnt fuses found and a >= 4.0.0 HOS is booted.
bootprotect=00: Disable, 1: Protect bootloader folder from being corrupted by disallowing reading or editing in HOS.
updater2p=00: Disable, 1: Force updates (if needed) the reboot2payload binary to be hekate.
backlight=100Screen backlight level. 0-255.

Boot entry key/value combinations:

Config optionDescription
warmboot={FILE path}Replaces the warmboot binary
secmon={FILE path}Replaces the security monitor binary
kernel={FILE path}Replaces the kernel binary
kip1={FILE path}Replaces/Adds kernel initial process. Multiple can be set.
kip1={FOLDER path}/*Loads every .kip/.kip1 inside a folder. Compatible with single kip1 keys.
pkg3={FILE path}Takes an Atmosphere package3 binary and extracts all needed parts from it. kips, exosphere, warmboot and mesophere.
fss0={FILE path}Same as above. !Deprecated!
pkg3ex=1Enables loading of experimental content from a PKG3/FSS0 storage
pkg3kip1skip={KIP name}Skips loading a kip from pkg3/fss0. Allows multiple and , as separator. The name must exactly match the name in PKG3.
exofatal={FILE path}Replaces the exosphere fatal binary for Mariko
--------------------------------------------------------------------------------
kip1patch=patchnameEnables a kip1 patch. Allows multiple and , as separator. If actual patch is not found, a warning will show up.
emupath={FOLDER path}Forces emuMMC to use the selected one. (=emuMMC/RAW1, =emuMMC/SD00, etc). emuMMC must be created by hekate because it uses the raw_based/file_based files.
emummcforce=1Forces the use of emuMMC. If emummc.ini is disabled or not found, then it causes an error.
emummc_force_disable=1Disables emuMMC, if it's enabled.
stock=1OFW via hekate bootloader. Disables unneeded kernel patching and CFW kips when running stock. If emuMMC is enabled, emummc_force_disable=1 is required. emuMMC is not supported on stock. If additional KIPs are needed other than OFW's, you can define them with kip1 key. No kip should be used that relies on Atmosphère patching, because it will hang. If NOGC is needed, use kip1patch=nogc.
fullsvcperm=1Disables SVC verification (full services permission). Doesn't work with Mesosphere as kernel.
debugmode=1Enables Debug mode. Obsolete when used with exosphere as secmon.
kernelprocid=1Enables stock kernel process id send/recv patching. Not needed when pkg3/fss0 is used.
--------------------------------------------------------------------------------
payload={FILE path}Payload launching. Tools, Android/Linux, CFW bootloaders, etc. Any key above when used with that, doesn't get into account.
--------------------------------------------------------------------------------
l4t=1L4T Linux/Android native launching.
boot_prefixes={FOLDER path}L4T bootstack directory.
ram_oc=0L4T RAM Overclocking. Check README_CONFIG.txt for more info.
ram_oc_vdd2=1100L4T RAM VDD2 Voltage. Set VDD2 (T210B01) or VDD2/VDDQ (T210) voltage. 1050-1175.
ram_oc_vddq=600L4T RAM VDDQ Voltage. Set VDDQ (T210B01). 550-650.
uart_port=0Enables logging on serial port for L4T uboot/kernel.
sld_type=0x31444C53Controls the type of seamless display support. 0x0: Disable, 0x31444C53: L4T seamless display.
Additional keysEach distro supports more keys. Check README_CONFIG.txt for more info.
--------------------------------------------------------------------------------
bootwait=3Overrides global bootwait from [config].
id=IDNAMEIdentifies boot entry for forced boot via id. Max 7 chars.
logopath={FILE path}If it exists, it will load the specified bitmap. Otherwise bootloader/bootlogo.bmp will be used if exists
icon={FILE path}Force Nyx to use the icon defined here. If this is not found, it will check for a bmp named as the boot entry ([Test 2] -> bootloader/res/Test 2.bmp). Otherwise defaults will be used.

Note1: When using the wildcard (/*) with kip1 you can still use the normal kip1 after that to load extra single kips.

Note2: When using PKG3/FSS0 it parses exosphere, warmboot and all core kips. You can override the first 2 by using secmon/warmboot after defining pkg3/fss0. You can define kip1 to load an extra kip or many via the wildcard (/*) usage.

Warning: Careful when you override pkg3/fss core kips with kip1. That's in case the kips are incompatible between them. If compatible, you can override pkg3/fss0 kips with no issues (useful for testing with intermediate kip changes). In such cases, the kip1 line must be after pkg3/fss0 line.

Boot entry key/value combinations for Exosphère:

Config optionDescription
nouserexceptions=1Disables usermode exception handlers when paired with Exosphère.
userpmu=1Enables user access to PMU when paired with Exosphère.
cal0blank=1Overrides Exosphère config blank_prodinfo_{sys/emu}mmc. If that key doesn't exist, exosphere.ini will be used.
cal0writesys=1Overrides Exosphère config allow_writing_to_cal_sysmmc. If that key doesn't exist, exosphere.ini will be used.
usb3force=1Overrides system settings mitm config usb30_force_enabled. If that key doesn't exist, system_settings.ini will be used.

Note: cal0blank, cal0writesys, usb3force, as stated override the exosphere.ini or system_settings.ini. 0: Disable, 1: Enable, Key Missing: Use original value.

Note2: blank_prodinfo_{sys/emu}mmc, allow_writing_to_cal_sysmmc and usb30_force_enabled in exosphere.ini and system_settings.ini respectively, are the only atmosphere config keys that can affect hekate booting configuration externally, if the equivalent keys in hekate config are missing.

Payload storage:

hekate has a boot storage in the binary that helps it configure it outside of BPMP environment:

Offset / NameDescription
'0x94' boot_cfgbit0: Force AutoBoot, bit1: Show launch log, bit2: Boot from ID, bit3: Boot to emuMMC.
'0x95' autobootIf Force AutoBoot, 0: Force go to menu, else boot that entry.
'0x96' autoboot_listIf Force AutoBoot and autoboot then it boots from ini folder.
'0x97' extra_cfgWhen menu is forced: bit5: Run UMS.
'0x98' xt_str[128]Depends on the set cfg bits.
'0x98' ums[1]When Run UMS is set, it will launch the selected UMS. 0: SD, 1: eMMC BOOT0, 2: eMMC BOOT1, 3: eMMC GPP, 4: emuMMC BOOT0, 5: emuMMC BOOT1, 6: emuMMC GPP,
'0x98' id[8]When Boot from ID is set, it will search all inis automatically and find the boot entry with that id and boot it. Must be NULL terminated.
'0xA0' emummc_path[120]When Boot to emuMMC is set, it will override the current emuMMC (boot entry or emummc.ini). Must be NULL terminated.

Nyx Configuration keys/values (nyx.ini):

Config optionDescription
themebg=2d2d2dSets Nyx background color in HEX. EXPERIMENTAL.
themecolor=167Sets Nyx color of text highlights.
entries5col=01: Sets Launch entry columns from 4 to 5 per line. For a total of 10 entries.
timeoff=100Sets time offset in HEX. Must be in HOS epoch format
homescreen=0Sets home screen. 0: Home menu, 1: All configs (merges Launch and More configs), 2: Launch, 3: More Configs.
verification=10: Disable Backup/Restore verification, 1: Sparse (block based, fast and mostly reliable), 2: Full (sha256 based, slow and 100% reliable).
------------------------- The following options can only be edited in nyx.ini -------
umsemmcrw=01: eMMC/emuMMC UMS will be mounted as writable by default.
jcdisable=01: Disables Joycon driver completely.
jcforceright=01: Forces right joycon to be used as main mouse control.
bpmpclock=10: Auto, 1: Fastest, 2: Faster, 3: Fast. Use 2 or 3 if Nyx hangs or some functions like UMS/Backup Verification fail.
hekate  (c) 2018,      naehrwert, st4rk.
        (c) 2018-2025, CTCaer.

Nyx GUI (c) 2019-2025, CTCaer.

Thanks to: derrek, nedwill, plutoo, shuffle2, smea, thexyz, yellows8.
Greetings to: fincs, hexkyz, SciresM, Shiny Quagsire, WinterMute.

Open source and free packages used:
 - Littlev Graphics Library,
   Copyright (c) 2016-2018 Gabor Kiss-Vamosi
 - FatFs R0.13c,
   Copyright (c) 2006-2018, ChaN
   Copyright (c) 2018-2022, CTCaer
 - bcl-1.2.0,
   Copyright (c) 2003-2006, Marcus Geelnard
 - blz,
   Copyright (c) 2018, SciresM
 - elfload,
   Copyright (c) 2014 Owen Shepherd,
   Copyright (c) 2018 M4xw

                         ___
                      .-'   `'.
                     /         \
                     |         ;
                     |         |           ___.--,
            _.._     |0) = (0) |    _.---'`__.-( (_.
     __.--'`_.. '.__.\    '--. \_.-' ,.--'`     `""`
    ( ,.--'`   ',__ /./;   ;, '.__.'`    __
    _`) )  .---.__.' / |   |\   \__..--""  """--.,_
   `---' .'.''-._.-'`_./  /\ '.  \ _.--''````'''--._`-.__.'
         | |  .' _.-' |  |  \  \  '.               `----`
          \ \/ .'     \  \   '. '-._)
           \/ /        \  \    `=.__`'-.
           / /\         `) )    / / `"".`\
     , _.-'.'\ \        / /    ( (     / /
      `--'`   ) )    .-'.'      '.'.  | (
             (/`    ( (`          ) )  '-;   [switchbrew]