How to Update a Modded Switch Safely: CFW & Firmware

Updating a modded Nintendo Switch requires more care than updating a stock console. If your Switch uses Atmosphère, Hekate, emuMMC, sysCFW, custom sysmodules, or homebrew apps, you should update the custom firmware components before installing a newer Nintendo system firmware.

Quick Answer: To update a modded Switch safely, first confirm that the target Nintendo firmware is supported by both Atmosphère and Hekate. Back up your microSD card, update Atmosphère, update Hekate and Fusee, test that CFW boots correctly, then update the Switch firmware. If you use emuMMC, update its firmware separately after updating sysMMC.
Display Your Ad Here
Whatsapp+971 55 912 8238Click to contact on Whatsapp Emailcloudcorex4@gmail.comClick to contact on email

Atmosphère 1.11.2 and Hekate 6.5.3 support Nintendo Switch firmware up to 22.5.0. Firmware 23.0.0 is not yet supported, so users who rely on custom firmware should not update to 23.0.0 yet.

Table of Contents

What Should You Update on a Modded Nintendo Switch?

A modded Switch normally contains several independent components. Updating only the Nintendo system firmware can leave the rest of the setup incompatible.

The main components are:

Nintendo Switch system firmware
Atmosphère CFW
Hekate/Nyx bootloader
Fusee payload
Homebrew Menu
emuMMC
Homebrew applications
Sysmodules
Tesla overlays
Custom themes

Atmosphère itself is the custom firmware layer, while Hekate manages boot configurations, emuMMC, SD card tools, payloads, and other system functions.

Check Firmware Compatibility Before Updating

This is the most important step when learning how to update a modded Switch.

Do not install a Nintendo firmware update until both Atmosphère and Hekate support it.

At the time of writing:

Component	Current Version	Firmware Support
Atmosphère	1.11.2	Up to 22.5.0
Hekate	6.5.3	Up to 22.5.0
Nintendo Firmware 23.0.0	—	Not currently supported by this CFW combination

Atmosphère 1.11.2 officially added basic support for firmware 22.5.0. It also requires users to update Fusee when upgrading.

The NH Switch Guide currently warns CFW users not to install firmware 23.0.0 until both Atmosphère and Hekate support it.

Back Up Your Modded Switch Before Updating

Create a backup before replacing any CFW files.

At minimum, copy your microSD card data to your computer.

Important directories include:

/atmosphere/
/bootloader/
/switch/
/emuMMC/

Also keep copies of important files such as:

hbmenu.nro
hekate_ipl.ini
exosphere.ini

A backup makes it easier to recover from:

Incompatible sysmodules
Broken boot configurations
Corrupted files
Failed Atmosphère updates
Hekate configuration problems
Theme-related boot crashes

If you already have a NAND backup, keep it stored somewhere separate from the Switch SD card.

How to Update a Modded Switch Step by Step

The safest order is:

Check firmware compatibility.
Back up the SD card.
Update Atmosphère.
Update Fusee.
Update Hekate.
Check sysmodules and themes.
Boot and test CFW.
Update sysMMC firmware.
Update emuMMC firmware if used.
Test homebrew apps again.

This avoids installing a Nintendo firmware version before your CFW environment is ready.

Step 1: Update Atmosphere

Download the latest compatible Atmosphère switch release from the official Atmosphere-NX repository.

For Atmosphère 1.11.2, the release archive contains the updated CFW files plus compatible Homebrew Menu components. Atmosphère 1.11.2 includes basic support for firmware 22.5.0.

Extract the ZIP file.

Copy its contents to the root of your Switch microSD card.

A typical SD structure looks like:

SD:/
├── atmosphere/
├── bootloader/
├── switch/
└── hbmenu.nro

When your operating system asks whether existing files should be replaced, select merge/replace.

The NH Switch Guide recommends copying the new Atmosphère release directly to the SD root and overwriting the existing files.

Step 2: Update Fusee

If you boot Atmosphère using Fusee, update the payload whenever the Atmosphère release requires it.

For Atmosphère 1.11.2, the official release notes specifically state that users should update Fusee.

Replace the old:

fusee.bin

with the Fusee version released alongside your Atmosphère version.

Using an outdated Fusee payload can cause:

Black screen
Atmosphère boot failure
Payload errors
Version mismatch errors

Keep Atmosphère and Fusee from the same release whenever possible.

Step 3: Update Hekate and Nyx

Download the latest compatible Hekate release.

For the current stable version, the archive contains:

bootloader/
hekate_ctcaer_6.5.3.bin

Copy the new:

bootloader

folder to the root of your microSD card.

Choose merge/replace when prompted.

Do not delete the existing bootloader folder before copying the new one. Hekate’s official update instructions specifically recommend merging the folder so your configurations and payloads are preserved.

Hekate also includes:

bootloader/update.bin

If this file is newer than your initially injected Hekate payload, Hekate can automatically load the newer version.

Step 4: Update the Hekate Payload if Needed

If you use an RCM Loader, PC, Android device, or modchip to launch Hekate, you may also need to update the initial Hekate payload.

The file will look similar to:

hekate_ctcaer_6.5.3.bin

For many modchip setups, Hekate is stored on the SD card as:

payload.bin

Hekate’s official documentation notes that updating the external injected payload is optional in many setups because the newer bootloader/update.bin can be loaded automatically.

Still, keeping the initial payload current helps avoid older bootloader compatibility issues.

Step 5: Disable or Update Incompatible Sysmodules

Before updating the Nintendo firmware, inspect third-party modifications stored in:

/atmosphere/contents/

Sysmodules and overlays sometimes require updates after major Nintendo firmware releases.

Examples include:

Tesla overlays
Overclocking modules
Controller sysmodules
Network modifications
Audio modifications
Custom services
Theme components

If you are unsure whether a sysmodule supports the target firmware, temporarily remove or disable it before the first boot.

Old sysmodules are one of the most common causes of Atmosphère crashes after an update.

Step 6: Remove Custom Themes Before Major Firmware Updates

Custom themes can depend on firmware-specific system files.

A theme that works on one Switch firmware version may cause Atmosphère to crash after a major update.

Before installing a significant firmware update:

Uninstall active themes.
Back up theme files.
Update your theme installer.
Reinstall compatible themes after confirming CFW works.

This makes troubleshooting easier because you can verify that Atmosphère itself boots correctly before restoring cosmetic modifications.

Step 7: Boot and Test Atmosphere Before Updating Firmware

After updating Atmosphère and Hekate, boot your existing firmware before installing a newer Nintendo update.

Check:

Hekate loads
Atmosphère boots
Homebrew Menu opens
emuMMC launches
Main homebrew apps work
No fatal Atmosphère errors appear

Open:

System Settings → System

The system version should show the Atmosphère version alongside the Nintendo firmware version.

Testing CFW first confirms that your core update files were copied correctly.

How to Update sysMMC on a Modded Switch

The correct sysMMC update method depends on whether the console is modchipped or uses an unpatched V1 setup.

Modchipped Switch

For modchipped consoles, the NH Switch Guide recommends updating major firmware versions through OFW/Stock.

From Hekate:

Home → Reboot → OFW

Then open:

System Settings → System → System Update

If OFW does not boot normally, use a Stock sysMMC launch configuration instead.

Updating through stock firmware helps keep the official system environment consistent, including expected fuse behavior.

Unpatched V1 Switch

For an unpatched console, the NH Switch Guide recommends booting the appropriate sysCFW environment and updating through:

System Settings → System → System Update.

If AutoRCM is enabled, be aware that updating through stock firmware can disable AutoRCM.

How to Update emuMMC on a Modded Switch

If you use emuMMC, updating sysMMC does not automatically update the emulated firmware environment.

Your emuMMC may therefore remain on an older firmware version.

A common workflow is:

Update sysMMC.
Obtain the firmware files from your own updated system.
Boot Atmosphère emuMMC.
Open Homebrew Menu.
Launch Daybreak.
Install the compatible firmware package.
Reboot emuMMC.

The NH Switch Guide documents updating emuMMC separately after updating the system firmware.

Do not install firmware files from unknown sources. Use firmware obtained from your own console and follow the compatibility requirements for Atmosphère and Hekate.

How to Update a Modded Switch With Hekate USB Tools

You do not necessarily need to remove the microSD card.

Hekate includes USB storage access.

From Hekate:

Tools → USB Tools → SD Card

Then connect the Switch to your computer with USB.

The SD card should appear as storage on the computer.

You can then copy:

Atmosphère files
Hekate files
Homebrew apps
Configuration updates

The NH Switch Guide uses this method for both Atmosphère and Hekate updates.

After copying files, safely eject the storage device before leaving USB mode.

How to Update Homebrew Apps After Updating the Switch

Homebrew apps are separate from Atmosphère.

Most .nro applications are stored under:

/switch/

After a major firmware or Atmosphère update, check whether your important homebrew apps have newer versions.

Prioritize apps that interact directly with:

Filesystem
System services
Controllers
Networking
Save data
Overlays
Firmware internals

Atmosphère 1.11 introduced changes related to application and applet lifecycle behavior after Nintendo firmware 22.0.0 changed how these processes work. Atmosphère added compatibility patches to restore expected homebrew behavior.

Common Problems After Updating a Modded Switch

Atmosphere Shows a Yellow or Blue Screen

The NH Switch Guide notes that a fully yellow or blue screen often indicates mismatched Atmosphère files, such as an incomplete update.

Reinstall the complete latest compatible Atmosphère package.

Unknown pkg1 Version Error

You may see:

Unknown pkg1 version.
HOS version not supported!

This commonly indicates that Hekate does not support the installed Nintendo firmware.

Update Hekate to a version compatible with the target firmware.

Atmosphere Crashes During Boot

Common causes include:

Outdated sysmodules
Old custom themes
Incorrect Atmosphère version
Old Fusee payload
Damaged SD card files
Unsupported Nintendo firmware

Temporarily remove third-party modifications and test a clean Atmosphère setup.

Hekate Boots but Atmosphere Does Not

Check:

/atmosphere/package3
/bootloader/hekate_ipl.ini

Also verify:

Correct Atmosphère files
Correct emuMMC configuration
Correct launch entry
Compatible Nintendo firmware
Current Hekate version

emuMMC Does Not Boot After Firmware Update

If sysMMC was updated but emuMMC was not, this alone is not necessarily a problem because they use separate firmware installations.

If emuMMC stops working after you intentionally update it, verify:

Atmosphère compatibility
Hekate compatibility
Sysmodules
Themes
Firmware installation
emuMMC configuration

Can You Update a Modded Switch Normally Through Nintendo?

Yes, but only after confirming CFW compatibility.

The danger is not the official Nintendo update process itself. The main problem is installing a Nintendo firmware version that your Atmosphère or Hekate version does not yet support.

For example, firmware 23.0.0 currently exceeds the supported firmware level of Atmosphère 1.11.2 and Hekate 6.5.3, so CFW users should not install it yet.

Should You Update Atmosphere Before Nintendo Firmware?

Yes.

For a modded Nintendo Switch, the recommended order is:

Atmosphère → Fusee → Hekate → CFW test → Nintendo firmware

This ensures your custom firmware environment already supports the system version you are about to install.

Installing Nintendo firmware first can leave the console unable to boot Atmosphère until compatible CFW releases become available.

Do You Need to Update Hekate Every Time?

Not for every small Atmosphère update, but Hekate should be updated whenever:

New Nintendo firmware requires it
emuMMC support changes
Atmosphère launch behavior changes
Hekate release notes recommend updating
You encounter a pkg1 compatibility error

Keeping Atmosphère and Hekate reasonably current reduces compatibility problems.

Frequently Asked Questions

How Do I Update a Modded Nintendo Switch?

Back up your SD card, verify firmware compatibility, update Atmosphère, Fusee, and Hekate, test CFW, then update the Nintendo firmware.

What Should I Update First on a Modded Switch?

Update the CFW components first:

Atmosphère
Fusee
Hekate
Important sysmodules
Nintendo firmware

Can I Update My Modded Switch Through System Settings?

Yes, once you have confirmed that Atmosphère and Hekate support the target firmware. The correct boot environment may differ between modchipped and unpatched consoles.

Will Updating My Switch Remove Atmosphere?

A normal Nintendo firmware update does not simply delete Atmosphère from the SD card. However, an unsupported firmware can prevent your installed Atmosphère version from booting.

Do I Need to Update emuMMC Separately?

Yes. sysMMC and emuMMC are separate firmware environments. Updating one does not automatically update the other.

Should I Remove Themes Before Updating?

Yes, especially before major firmware updates. Outdated themes can cause boot crashes.

Should I Update Sysmodules Before Updating Firmware?

Yes. Check important sysmodules and overlays for compatibility. If compatibility is unknown, disable them before the first boot.

What Is the Latest Atmosphere Version?

As of September 2026, the latest official release is Atmosphère 1.11.2, which adds basic support for Nintendo Switch firmware 22.5.0.

What Is the Latest Hekate Version?

The latest official release is Hekate 6.5.3 with Nyx 1.9.3.

Can I Update to Nintendo Switch Firmware 23.0.0?

Not if you currently depend on Atmosphère CFW. As of September 2026, the NH Switch Guide states that firmware 23.0.0 is not yet supported by Atmosphère 1.11.2 and Hekate 6.5.3.

Conclusion: How to Update a Modded Switch Safely

Knowing how to update a modded Switch is mainly about using the correct update order.

Start by checking whether your target Nintendo firmware is supported. Back up your SD card, update Atmosphère, Fusee, and Hekate, disable potentially incompatible themes or sysmodules, and confirm that CFW boots successfully before installing the Nintendo system update.

If your setup uses both sysMMC and emuMMC, remember that they are separate environments and may need to be updated individually.

Most update problems come from unsupported firmware, mismatched Atmosphère files, an outdated Hekate version, old Fusee payloads, or incompatible sysmodules. Keeping these components synchronized makes Nintendo Switch homebrew updates considerably more reliable.