>_ Atmosphère versions, downloads, and installation

Recent Atmosphère versions

Direct links to the files published on the official Atmosphere-NX repository. The .zip file contains atmosphere/ and hbmenu.nro; fusee.bin is the payload to send (or to be loaded by hekate).

Full list of versions on GitHub. Checked on September 6, 2026: the latest version is 1.11.2.

The necessary tools

• hekate + Nyx (v6.5.3) — the bootloader sent to the console in RCM: it launches Atmosphère, creates the emuMMC, partitions the card, and backs up the internal memory. Download hekate_ctcaer_6.5.3_Nyx_1.9.3.zip; the hekate_ctcaer_6.5.3.bin payload is inside.
• OmniRCM — the recommended injector for Windows, Linux, and macOS: it installs the driver and downloads payloads automatically.
• TegraRcmGUI — alternative Windows injector. Do not use the hekate payload bundled with the tool: it is outdated.
• Zadig — only if the driver installation fails on Windows: select "APX" then the libusbK driver.
• NXLoader — to inject from an Android phone via USB-C, without a computer.
• A jig — the small piece that shorts the right Joy-Con rail to enter RCM mode. A bent paperclip works, but a printed jig is safer.

Tools and procedure based on switch.hacks.guide — Sending a Payload, accessed on September 6, 2026.

Installing Atmosphère on the microSD

1. Check if your console is compatible. Without an RCM exploit, none of this applies: use the serial number checker.
2. Format the card as FAT32, with a single partition. Details, pitfalls, and required space calculation can be found on the microSD page.
3. Unzip the Atmosphère archive to the root of the card. You should have /atmosphere/ and hbmenu.nro directly at the root—not in a subfolder created by the unzipping tool.
4. Unzip hekate + Nyx to the root. This adds the /bootloader/ folder. Also place fusee.bin in /bootloader/payloads/: hekate will then be able to launch Atmosphère from its "Payloads" menu.
5. Check for version compatibility. The Atmosphère version must support the firmware installed on the console (see the "Max supported firmware" column above). When in doubt, update Atmosphère before touching the system.
6. Safely eject the card and insert it into the powered-off console. Never hot-swap: this can corrupt the filesystem.
7. Enter RCM mode. With the console completely powered off, insert the jig into the right rail, then hold Volume + and press Power. The screen will remain black: this is normal.
8. Send the hekate payload using OmniRCM, TegraRcmGUI, or NXLoader. If the hekate menu appears, your console is not patched.
9. Create the emuMMC (hekate → emuMMC → Create emuMMC). The original internal memory remains untouched: this is the safest setup to avoid a ban.
10. Back up the internal memory (Tools → Backup eMMC: BOOT0/BOOT1 and the keys), and store this backup somewhere other than the card.
11. Launch Atmosphère from hekate (Launch → CFW emuMMC). On the first boot, the console will rebuild its caches: this will take longer than usual.

Updating Atmosphère

• Delete the old /atmosphere/ folder before copying the new one—do not merge them, as outdated files can cause crashes.
• Also replace fusee.bin in /bootloader/payloads/ with each new version.
• Keep your personal folders: /switch/, /emuMMC/, /bootloader/ini/, and your themes are not affected by the update.
• Correct order: Atmosphère and hekate first, then the console firmware.

Information provided for educational purposes, for hardware that you own. Modifying a console voids the warranty and can lead to a permanent ban from online services—see the Basics page.

Sources consulted on September 6, 2026: switch.hacks.guide · Atmosphere-NX (versions) · hekate (CTCaer)