Table of Contents

• Troubleshooting & FAQ
• How to enter the homebrew launcher
• Disabling mods and cheats when launching a title
• Partition-based vs file-based emuMMC
• Partition-based emuMMC
• File-based emuMMC
• Battery died and the Switch won't power on
• Archive bit fix (Mac & Linux users)
• Avoiding firmware update nags
• How to enter Maintenance mode
• What is maintenance mode used for?
• Random crash with Program 0100000000000025
• Crash while using Tesla, Program: 420000000007E51A - Tesla overlay
• Using a Switch kiosk model as a normal model
• Reset parental controls
• Hekate has corrupted graphics or no touch function
• Connecting to Nintendo gives an error or causes a freeze
• Issues starting a game
• Installed games show with no icon and a spinning circle
• Black screen or crash
• Linked Nintendo account required
• Connect to Nintendo to update account information
• Crash or freeze when starting Atmosphère
• Old CFW version
• Old or incompatible sysmodule
• Crash with Program 0100000000001000 - Theme
• Freeze on Hekate's Hekate - IPL boot screen
• Black screen right after Hekate's Hekate - IPL boot screen
• Crash with Program 010000000000BD00 - Old Mission Control
• Crash with Program 010000000000000F Error 2168-0002 - sys-patch
• Bluescreen after updating Atmosphère
• Crash with Program 010000000000001F Error 2002-2634 - Game card crash
• Crash with Program 0100000000000014 - Bad audio sys-module
• Crash with Program 420000000007E51A - Tesla overlay
• Crash with Program 010000000000002B - Bad system save
• Crash with Program 4200000000000010 - ldn_mitm
• Crash with Program 0100000000000025 Error 2002-3005 - Downgraded FW
• Incorrect fusee version!
• [ERROR] Fatal error: [NXBOOT] Couldn't parse boot0: !

Troubleshooting & FAQ

Here you will find some troubleshooting solutions and frequently asked questions and answers.

How to enter the homebrew launcher

There are two ways to launch homebrew:

• By clicking on the Album icon

  • This will launch you into applet mode. Some homebrew may not work. To use the album like normal, hold R when selecting the album

    ---

• By holding R while starting a working title in your home menu. (Title override)

Disabling mods and cheats when launching a title

If you want to disable mods or cheats when launching a title, hold L while launching your desired title.

Partition-based vs file-based emuMMC

• Partition-based emuMMC

  • Pros:
    • Has the least chance of corruption.
    • It is reliable.
    • Faster than file-based.
    • Moving an installed title between system and SD is possible.
  • Cons:
    • Creating a new emuMMC requires you to partition your SD card; thus, existing files on the SD will get deleted.
    • Migrating to a new SD card or making a backup of your emuMMC is more complex. But it's not done often.

      ---

• File-based emuMMC

  • Pros:
    • Easy to transfer or make a backup of.
    • Creating a new emuMMC is easier and won't require you to partition your SD card.
  • Cons:
    • Corruption! Your emuMMC setup has a higher chance of getting corrupted. (This applies to both FAT32 and exFAT users.)
    • Slower write speed. Which will affect dumping games and more.
    • Transferring games between your SD card and your emuMMC via system settings is not possible. (This is due to an unfixed bug.)
    • Added chance of user error. (Like not formatting the card properly like how Hekate does, or not making it FAT32 at all.)

Battery died and the Switch won't power on

Unpatched Erista devices:
You most likely have auto RCM enabled.
Connect your Switch to the original charger (not dock) and let it charge for an hour.
Afterwards you should be able to push a payload like usual.

Modchipped:
Try charging directly with the original charger instead of using the dock.

Archive bit fix (Mac & Linux users)

If you're using a Mac PC and you have inserted your SD card into your Mac PC, you might experience issues such as the Homebrew menu not detecting your Homebrew applications or some other issues. To fix this, do the following:

Boot first into Hekate, then press
Tools ➔ Arch bit • RCM • Touch • Pkg1/2 ➔ 🗀 Fix Archive Bit

• Do this twice to be sure when you're having an issue.

Avoiding firmware update nags

If you want to avoid getting the firmware update nag, you block Nintendo connections to block system firmware updates from being downloaded; see this guide page.
And boot to maintenance mode once so the downloaded update is deleted.

• Updating is usually the better alternative; see updating guides here.

How to enter Maintenance mode

You can boot into maintenance mode by following these steps:

1. Boot into Hekate.
2. From before selecting your launch option in Hekate, hold both volume buttons (- & +)
3. Select your emuMMC or sysMMC launch option and hold the volume buttons until you're in the white menu.

If you don't use Hekate:

1. Power off your console completely.
2. Hold both volume buttons (- & +) while booting into Atmosphère.

• What is maintenance mode used for?

  • Clear the cache for your Switch. This happens automatically when getting into the maintenance menu. Do not use any of the options there if all you want to do is clear the cache.
    • This can be used to remove a downloaded firmware update, and so get rid of the message asking to update.
    • And in some cases fix a game that's not launching.
  • The menu options in Maintenance mode are Update System, Initialize Console Without Deleting Save Data and Initialize Console
    • Initialize = Factory reset

Random crash with Program 0100000000000025

Blanking serial information without blocking Nintendo can cause Atmosphère to crash. Set up DNS.mitm to block Nintendo like shown on this page.

Crash while using Tesla, Program: 420000000007E51A - Tesla overlay

• The Tesla overlay module you were trying to use is likely outdated. Get a new compatible version or delete the module. Tesla modules are saved in /switch/.overlays
  See the Tesla guide and modules page here.
  If it is crashing on boot, then update. See the crash on boot entry.

Using a Switch kiosk model as a normal model

These Nintendo Switch models can be used as regular Switch models by using a patch for Atmosphère or a custom Atmosphère version.
Booting Atmosphère on these models without a patch will make the Switch boot to a simple message box showing Could not start the software. and rebooting to Hekate after pressing OK.

1. Download ams_mitm.kip from the latest kip release on this GitHub.
2. Copy ams_mitm.kip to /atmosphere/kips/ on your micro SD card.
3. Edit your hekate_ipl.ini and add a line to your launch option so the kip is loaded. e.g., kip1=atmosphere/kips/* or kip1=atmosphere/kips/ams_mitm.kip
4. Use your launch option from Hekate's launch menu and use the console as normal.

Reset parental controls

This can easily be done with the homebrew "Reset-Parental-Controls-NX" which you can find on this GitHub.

Download and copy the reset_parental_controls.nro to the /switch/ folder on your micro SD card. And use from the homebrew menu.

Hekate has corrupted graphics or no touch function

If Hekate starts but there are minor graphical issues or the touchscreen is not working, try the following:

• On the micro SD card, open the bootloader folder and edit the file nyx.ini, add the line bpmpclock=2 at the bottom and save it. This setting can be set up to 5. Try a 3-5 if the issue persists. A higher number is a lower memory clock speed. See Hekate's documentation for more info.

Connecting to Nintendo gives an error or causes a freeze

Certain games require being played in airplane mode or extra patches to play normally when the console has Nintendo blocked but is online. E.g., DOOM not starting at all.
There are a couple of ways of bypassing this issue:

• Airplane mode. Enable airplane mode and play the game. A minor annoyance, and some games will complain about it being enabled.
• SaltyNX nx-nonet patches. These patches (that you can get here) were made for SaltyNX and can be used globally or for specific games.
  • Copy these patches either to SaltySD/patches to make it work for every game or to SaltySD/patches/*titleid* to make it work for a specific game.

Issues starting a game

• Installed games show with no icon and a spinning circle

  • Signature patches were not loaded when the game was installed.
    Solution steps:
    1. Fix your CFW setup to have and load patches.
    2. Delete the "bad" install, using the data management menu, from the home menu or with a title manager.
    3. Install the title(s) again now that you've got a good setup.

    ---

• Black screen or crash

  • Make sure the game works without mods and cheats by starting the game while holding L.

  • All games require a certain FW requirement, and updating a game can increase that requirement to a higher FW version.

    ---

• Linked Nintendo account required

  • If you have Nintendo blocked but need a Nintendo account linked for a game to work, you can use Linkalho to link a fake account offline.
  • Solution steps:
    1. You can get Linkalho from this GitHub.
    2. Extract linkalho-v*.*.*.zip to the root of your micro SD card.
    3. Start Linkalho from hbmenu.
    4. Use Link selected accounts
    5. If a game did not previously work because of this issue, delete and then install that game again.

    ---

• Connect to Nintendo to update account information

  • If you have Nintendo blocked but get this message, use Linkalho to unlink accounts and then link accounts. A reboot is required for each.
  • Solution steps:
    1. You can get Linkalho from this GitHub.
    2. Extract linkalho-v*.*.*.zip to the root of your micro SD card.
    3. Start Linkalho from hbmenu.
    4. Use Unlink selected accounts
    5. After restarting, start Linkalho again.
    6. Use Link selected accounts.

    ---

• Cloud saves issue Please wait... or 2155-8007

  • If starting a game causes a repeatedly opening and closing Please wait... box or the error code 2155-8007 when the Switch is online but Nintendo is blocked.
  • You have 3 options for bypassing this problem:
    • Airplane mode. Enable airplane mode and play the game.

    • Link a new account. When a new NNID is linked, cloud saves will be disabled. Follow the same steps as the above issue, using Linkalho to unlink and linking a fake NNID account.

    • Atmosphère system config. In /atmosphere/config/ find system_settings.ini and add these lines at the bottom and save the file:

      [olsc]
      default_auto_upload_global_setting = u8!0x0
      

      • If you do not have the system_settings.ini file, copy it from /atmosphere/config_templates/
      • Using this setting will always block automatic save uploads while using CFW.

    ---

Crash or freeze when starting Atmosphère

If your device is not booting into Horizon OS properly, you might find the solution here in this list of known issues and fixes:

• Old CFW version

  • If you updated FW without updating CFW, this is likely your issue. You may follow this update guide page to update your CFW.

    ---

• Old or incompatible sysmodule

  • If you have had any sysmodules, then either update the ones you use or delete the ones you have.
  • Alternatively, you can delete them all by deleting the folder /atmosphere/contents/. This folder is also used for mods and cheats.

    ---

• Crash with Program 0100000000001000 - Theme

  • If your console doesn't boot anymore due to updating or a bad theme (mostly with SZS themes), delete the 0100000000001000 folder from the /atmosphere/contents/ folder from your micro SD card. When you can boot normally, launch the theme installer and select uninstall theme to finish the cleanup process.

    ---

• Freeze on Hekate's Hekate - IPL boot screen

  • The console freezes on Hekate's Hekate - IPL boot screen:
    On the micro SD card, open the bootloader folder and edit the file nyx.ini, add the line bpmpclock=2 at the bottom and save it. This setting can be set up to 5. Try a 3-5 if the issue persists. A higher number is a lower memory clock speed. See Hekate's documentation for more info.

    ---

• Black screen right after Hekate's Hekate - IPL boot screen

  • The console freezes on a black screen with no information after Hekate's Hekate - IPL boot screen. This is commonly caused by a bad/old kip patch, or Atmosphère needing to be updated. Some options for fixing this issue:
    • Use a compatible kip
    • Remove the old one from the micro SD card (e.g. /atmosphere/kips/loader.kip)
    • Remove the "kip1=" line to load it in your hekate_ipl.ini (e.g. kip1=atmosphere/kips/loader.kip)

      ---

• Crash with Program 010000000000BD00 - Old Mission Control

  • The system module Mission Control usually needs to be updated for every new Atmosphère version.
    You can fix this crash by deleting the folder 010000000000bd00 from /atmosphere/contents/. Or by getting a new updated version if that's available.

    ---

• Crash with Program 010000000000000F Error 2168-0002 - sys-patch

  • You can fix this by either deleting the folder 420000000000000B from /atmosphere/contents/.
    Or by getting a new updated version if that's available. Check the CFW update page.

    ---

• Bluescreen after updating Atmosphère

  • If you updated Atmosphère recently, but you are getting a blue screen on boot up, please ensure that you download the latest fusee.bin payload and place it in your /bootloader/payloads/ folder on your SD card or update your payload injector with the latest fusee.bin payload.
    (See also the updating CFW page here.)

    ---

• Crash with Program 010000000000001F Error 2002-2634 - Game card crash

  • Remove your game card if you updated firmware and you are getting Error Code: 2002-2634 for Program: 010000000000001F.
    You can enable nogc to avoid this crash, but that will prevent you from playing gamecards until you update your emuMMC after updating your Switch sysMMC to a newer supported firmware.

    ---

• Crash with Program 0100000000000014 - Bad audio sys-module

  • An incompatible audio sys-module, usually TriPlayer. Delete the TriPlayer sys-module by deleting 4200000000000FFF from /atmosphere/contents/.

    ---

• Crash with Program 420000000007E51A - Tesla overlay

  • The Tesla overlay could be outdated, or the module you were using. Get the latest of the 2 main Tesla modules, and the overlay module you were using. See the Tesla guide and modules page here.
    Or delete the Tesla sys-module by deleting the folder named 420000000007E51A from /atmosphere/contents/.

    ---

• Crash with Program 010000000000002B - Bad system save

  • Deleting system save 80000000000000d1 is often enough to fix that issue.
    If it's still crashing on boot after that, replace the system saves 8000000000000050 and 8000000000000052 from a working system or backup.

    ---

• Crash with Program 4200000000000010 - ldn_mitm

  • Caused by an incompatible version of ldn_mitm. Update to a working version. Or delete the ldn_mitm sys-module by deleting 4200000000000010 from /atmosphere/contents/.

    ---

• Crash with Program 0100000000000025 Error 2002-3005 - Downgraded FW

  • If you downgrade firmware and are now getting this error and code on boot: Error Code: 2002-3005 for Program: 0100000000000025 you can do one of the following:
    Factory reset or updating firmware from the maintenance mode menu.
  • Factory reset: Boot the downgraded system while holding both volume buttons until in the white maintenance mode menu. Then choose the second option Initialize console without deleting save data
    • Users and game saves will be saved, but all games and settings will be deleted. So games will have to be installed again.
  • Update FW: Boot the downgraded system while holding both volume buttons until in the white maintenance mode menu. Then choose the first option, Update System.

    ---

• Incorrect fusee version!

  • It's exactly what it says it is.
    Use the fusee.bin file that comes with the Atmosphère version you're using. Where it's being used from could likely be in /bootloader/payloads/ or where you select payloads in your payload injector.
    See also the updating CFW page and update correctly.

    ---

• [ERROR] Fatal error: [NXBOOT] Couldn't parse boot0: !

  • If you updated via ChoidujourNX on SX OS, then you will have a corrupt BOOT0. Ensure that your sysMMC is on the same version as your emuMMC, and do the following to resolve the issue:
    1. Boot into Hekate.
    2. Select Tools.
    3. Select Backup eMMC.
    4. Select eMMC BOOT0 & BOOT1.
    5. Once done, power off your device and connect your SD card to your PC. In your /backup/xxxxxxxx/ folder, move your BOOT0 and BOOT1 files into the /backup/xxxxxxxx/restore/emummc folder.
    6. Boot into Hekate and select Tools.
    7. Select Restore eMMC.
    8. Select SD emuMMC Raw Partition and make sure it's ON.
    9. Select SD emuMMC BOOT0 & BOOT1.
    10. Once the process is done, you may boot into Hekate and launch into Atmosphère.

    ---

• Warmboot errors

  • Failed To Determine WarmBoot Firmware

    • Your modchip needs the warmboot firmware dumped to the micro SD card. This is easily achieved since Atmosphère does it automatically when needed.
      (Using reboot to OFW does not use any part of Atmosphère to boot sysMMC and therefore does not dump warmboot.)

  • Failed to match warmboot with fuses!

    • A newer warmboot needs to be dumped because of an eFuse count. Start the updated sysMMC with a Hekate launch option.

  • Solution for both warmboot issues

    • Warmboot needs to be dumped to the micro SD card and using reboot to OFW does not do this.
      This is automatically done by launching sysMMC stock (or with CFW) from Hekate:
      • 1. Boot into hekate, select Launch and use your Stock, Warmboot Error Fix or sysMMC CFW launch option.
        2. Once you have booted sysMMC, you can reboot back to Hekate and launch your emuMMC as normal.
    • If you do not have Stock, Warmboot Error Fix or a sysMMC CFW Launch entry in your Launch menu, then go to your /bootloader/ folder and add this entry to your hekate_ipl.ini file:
      

      [Stock]
      pkg3=atmosphere/package3
      stock=1
      emummc_force_disable=1
      icon=bootloader/res/icon_switch.bmp
      

---

↵ Home 🦝