Updating your modified Nintendo Switch can feel like walking through a minefield. One wrong move leaves you staring at a black screen or an error code.
If you're running custom firmware (CFW), you can't just tap the system update button in the standard Nintendo settings menu. Doing that will break your CFW setup, corrupt your SD card layout, or burn hardware fuses.
This guide walks you through updating your Nintendo Switch firmware safely while keeping your Atmosphere environment, sigpatches, and homebrew apps fully operational.
What You Need Before You Start
Preparation prevents bricked consoles. Gather these tools and files on your computer before touching your Switch:
- A computer with a reliable USB-C cable for data transfer.
- The latest stable release of Atmosphere from the official GitHub repository.
- The matching Hekate - CTCaer payload bin file.
- The latest Sigpatches pack to ensure backup games and custom forwarders launch properly.
- The correct official Nintendo Switch firmware zip file from a trusted archive source.
Don't skip backing up your SD card contents. Copy the entire contents of your Nintendo Switch SD card to a folder on your computer desktop before making any file replacements. If something goes wrong, you can restore your setup in minutes.
Step 1: Update Atmosphere and Hekate First
Before touching the system firmware version, update your bootloader and system modules. If you update the firmware first, older versions of Atmosphere won't boot the new Horizon OS version.
- Remove your SD card from your Switch and plug it into your computer.
- Download the latest Atmosphere zip archive and extract it directly to the root of your SD card. Overwrite existing files when prompted.
- Download the latest Hekate zip archive and place the
payload.binfile into your payload injector or RCM loader. Also placehekate_ctcaer_X.X.X.bininside your bootloader folder on the SD card. - Extract the latest sigpatches zip file to the root of your SD card, merging folders (
exefs_patchesandloader.ini).
Step 2: Download and Prepare Official Firmware
You need the official Nintendo firmware files to perform an offline update via Daybreak.
- Download the official firmware update zip package matching your target version from a trusted community repository like Darthsternie's Firmware Archive.
- Create a new folder on the root directory of your SD card named something recognizable, like
firmware. - Extract all files from the official firmware zip into that new folder on your SD card.
- Safely eject your SD card from your computer and insert it back into your Nintendo Switch.
Step 3: Run the Daybreak Firmware Installer
Daybreak is the official offline firmware installer built directly into Atmosphere. It replaces older, riskier tools like ChoiDujourNX and eliminates the danger of burning unwanted fuses.
- Boot your Switch into RCM (Recovery Mode) using your jig and payload injector, then launch Hekate.
- Tap Payloads, select your updated Hekate payload, and launch into the Atmosphere custom firmware environment via the Fusee or Hekate payload launcher.
- Once booted into Horizon OS, open your Album to launch the Homebrew Menu.
- Scroll down and open Daybreak.
- Select Install on the main menu.
- Navigate to the
firmwarefolder you created earlier on your SD card and select it. - Daybreak will validate the firmware files. Once validation finishes, tap Continue.
- Select ExFAT + FAT32 (recommended, as it supports modern game cards and large files) or FAT32 depending on your preference.
- Confirm the installation and wait for the process to complete. Never turn off your console or remove the SD card during this stage.
Step 4: Clean Up and Reboot
Once Daybreak finishes writing the update, it will prompt you to reboot.
- Tap Reboot on the screen.
- Inject your Hekate payload again if your console enters RCM.
- Verify the update worked by navigating to System Settings > System on your Switch. You should see your current system version paired with the Atmosphere tag (e.g., AMS X.X.X|E).
Common Mistakes to Avoid
Even experienced users run into trouble by skipping small details. Watch out for these pitfalls:
- Updating via Nintendo's online servers: Never use the official system update prompt in the standard settings menu if you want to keep Atmosphere running smoothly. Always update offline using Daybreak.
- Forgetting sigpatches: If your homebrew apps load fine, but your installed games crash immediately with an error saying "The software was closed because an error occurred," you forgot to update your sigpatches or placed them in the wrong directory.
- Using mismatched Atmosphere versions: Mixing old atmosphere modules with a newly updated Horizon OS version causes an immediate software crash loop (often showing a fatal error screen with error code
0x2000). Always update Atmosphere and Hekate before updating your firmware.
Frequently Asked Questions
Can I update my emuMMC and sysMMC at the same time?
Yes, but it's best practice to update your emuMMC first via Daybreak to test stability. Once confirmed working, you can boot into your sysMMC (running CFW) and repeat the Daybreak process if you also want your clean system environment updated.
What should I do if my Switch gets stuck on a black screen after updating?
This usually happens because an outdated Atmosphere module or theme is incompatible with the new firmware version. Remove your SD card, put it in your computer, navigate to atmosphere/contents/, and delete the folder matching the title ID of any custom themes or obsolete sysmodules causing the crash.
Do I need to redo my RCM exploit setup after updating firmware?
No. System firmware updates do not patch hardware vulnerabilities on unpatched V1 consoles. Your hardware exploit method remains identical.
Where can I check the latest stable Atmosphere releases?
Always check the official Atmosphere GitHub Releases page to verify compatibility notes before starting any update procedure.