Updating to 21.2.0

[HelloShitty]

Hello...


Just for context:
I am usign a Nintendo Switch Oled, hwfly RP2040.
I have been using a Sandisk 512Gb sd card and everything has been going good.


These last days I updated the OFW to 21.2.0 and then, I tried to update the CFW to the latest versions by using a prepack of a well known user here of this forum but I didn't know his prepack wasn't yet ready for 21.2.0, so I am getting some errors like "Coul not apply nosigchk" and the console wouldn't boot. This error only show up when booting to CFW. It boots normally to OFW.


Then, I tried the old manual way, with a few twists
Downloaded Atmosphere 1.10.2
Dowloaded Hekate v6.5.0 and Nyx 1.9.0
Downloaded sys-patch-sysmodule from here (sys-patch-1.5.9.zip)

Then unziped all of them, as usual, to the SD card root
Replaced /bootloader/payload/fusee.bin with the corresponding one for Atmosphere 1.10.2
Renamed /hekate_ctcaer_6.5.0.bin to /payload.bin
And then, I went to my friend's Prepack and copied over the following files and folders, to the corresponding locations in my SD card:

/boot.bat
/exosphere.ini
config/
themes/
forwarder/
/bootloader/hekate_ipl.ini
/bootloader/hekate_ipl.ini.template
/bootloader/hekate_ipl - 3 options.ini
/bootloader/hekate_ipl - Advance.ini
/bootloader/patches.ini

I performed these seps in a normal 512Gb Sandisk sd card that was already being used with the previous firmware versions, but I get that "Can't apply nosigchk" error and then, right after the Atmosphere and Nintendo logos show up in the screen that says:
A fatal error occured when running Atmosphere
Program ID: 010000000000bd00
Error Desc: Data Abort (0x101)
Report saved to /atmosphere/fatal_errors/report_0000000029b86ada.bin
Press POWER to reboot

If I boot to OFW, all seems to be good!
Where am I going wrong?

In one other SD card (Sandisk Extreme 64Gb), I tried the same steps, but also create the 12Gb partition and the emuMMC, but in this case, I always get the error:
Failed to apply 'nosigchk!
Press POWER to continue

I press POWER and it continues and loads the CFW, as far as I understand because I see 21.2.0|AMS 1.10.2|E
Where am I going wrong? What can I do to fix the fatal error on the 512Gb and the "nosigchk" error on the 64Gb Sandisk Extreme?

 

[HelloShitty]

Sorry for this reply. I wasn't being able to put all text in a single reply.

 

[urherenow]

/bootloader/hekate_ipl.ini

Remove ALL (there may be 1 or multiple) lines that say:

kip1patch=nosigchk

seriously, I'm pretty sure that searching for "nosigchk" in these forums would have brought up too many results to read, without having to take a restroom break...

 

[HelloShitty]

/bootloader/hekate_ipl.ini

Remove ALL (there may be 1 or multiple) lines that say:

kip1patch=nosigchk

seriously, I'm pretty sure that searching for "nosigchk" in these forums would have brought up too many results to read, without having to take a restroom break...

I know about that. What they say is to apply to sys-module, if I'm not mistaken. I did that! Or also to remove that line from hekate_ipl.ini. But I also copied over patches.ini, if that's what you mean! That if I don't use that functionality, then I don't need the flag nor the patches.ini file!

 

[urherenow]

I know about that. What they say is to apply to sys-module, if I'm not mistaken. I did that! Or also to remove that line from hekate_ipl.ini. But I also copied over patches.ini, if that's what you mean! That if I don't use that functionality, then I don't need the flag nor the patches.ini file!

Correct. If you use sys-patch (which is the easiest), you don't need that line, or patches.ini. Or the .ips files in /atmosphere/exefs_patches/es_patches or nfim_ctest, or atmosphere/kip_patches.

NONE of those things will work when launching fusee (such as when troubleshooting hekate problems) unless you have a custom fusee.bin, and even then, you would need patches specifically for your build of fusee.bin. Too much of a headache. sys-patch is where it's at.

But... what flag are you speaking of? You DO need the boot2 flag for sys-patch.

 

[HelloShitty]

Correct. If you use sys-patch (which is the easiest), you don't need that line, or patches.ini. Or the .ips files in /atmosphere/exefs_patches/es_patches or nfim_ctest, or atmosphere/kip_patches.

NONE of those things will work when launching fusee (such as when troubleshooting hekate problems) unless you have a custom fusee.bin, and even then, you would need patches specifically for your build of fusee.bin. Too much of a headache. sys-patch is where it's at.

But... what flag are you speaking of? You DO need the boot2 flag for sys-patch.

Ok, about nosigchk will remove that line from hekate-ipl.ini and the other files you mentioned.
However, about the other SD card, the 512Gb, that I've been using for some time now, I repeated the steps but I get that fatal error.

What can I do to try to fix that one?

Edited;
About the flag, I was talking about the line inside hekate-ipl.ini!

Can I then remove those folders relate to patches? /atmosphere/exefs_patches or only /atmosphere/exefs_patches/es_patches?

 

[Andre63]

@HelloShitty

Delete theses files :

/bootloader/hekate_ipl.ini.template
/bootloader/hekate_ipl - 3 options.ini
/bootloader/hekate_ipl - Advance.ini
/bootloader/patches.ini

And according to what /bootloader/hekate_ipl.ini contains, rename hekate_ctcaer_6.5.0.bin to hekate.bin, at the root of the SD card.

 

[HelloShitty]

@HelloShitty

Delete theses files :

/bootloader/hekate_ipl.ini.template
/bootloader/hekate_ipl - 3 options.ini
/bootloader/hekate_ipl - Advance.ini
/bootloader/patches.ini

And according to what /bootloader/hekate_ipl.ini contains, rename hekate_ctcaer_6.5.0.bin to hekate.bin, at the root of the SD card.

Files deleted.

The contents of hekate-ipl.ini are:

[config]
autoboot=0
autoboot_list=0
bootwait=0
verification=1
backlight=100
autohosoff=2
autonogc=1
updater2p=1

[Atmosphere (EmuMMC)]
pkg3=atmosphere/package3
emummcforce=1
icon=bootloader/res/emummc.bmp
{}

[Stock (SysMMC)]
pkg3=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/emu_boot.bmp
{}

At the root of my SD card I renamed hekate_ctcaer_6.5.0.bin to payload.bin. Is it correct?

 

[Andre63]

Files deleted.

The contents of hekate-ipl.ini are:



At the root of my SD card I renamed hekate_ctcaer_6.5.0.bin to payload.bin. Is it correct?

Not payload.bin but hekate.bin and it should be ok.

 

[HelloShitty]

Not payload.bin but hekate.bin and it should be ok.

Ok, wait...
Regarding the fatal error of my 512Gb SD card, it's nothing related to hekate.bin nor payload.bin.
The issue is that the version of the console is yet at 18.0.0|AMS 1.10.2|E so the issue is inside /atmosphere/contents/.

I renamed these modules:
$ ls -lah /media/sdcard/atmosphere/contents/
total 768K
drwxrwxrwx 12 root root 64K Jan 15 14:48 .
drwxrwxrwx 16 root root 64K Jan 15 14:09 ..
drwxrwxrwx 3 root root 64K Jun 12 2024 00FF0000636C6BFF_
drwxrwxrwx 3 root root 64K Jun 12 2024 010000000000000D_
drwxrwxrwx 2 root root 64K Jun 12 2024 0100000000001013_
drwxrwxrwx 3 root root 64K Jun 12 2024 010000000000bd00_
drwxrwxrwx 2 root root 64K Jun 12 2024 054e4f4558454000_
drwxrwxrwx 3 root root 64K Jan 15 14:09 420000000000000B
drwxrwxrwx 2 root root 64K Sep 23 16:19 420000000000000D
drwxrwxrwx 2 root root 64K Sep 23 16:19 420000000000000F
drwxrwxrwx 2 root root 64K Sep 23 16:19 420000000000012B
drwxrwxrwx 3 root root 64K Jun 12 2024 420000000007E51A_
$

and now the fatal error is gone.
I think the next tep is really to dump my own firmware with either TegraExplorer, I guess, and update it with Daybreak, correct?

Post automatically merged: Jan 15, 2026

Ok, I have dumped my firmware and I'm now on 21.2.0|AMS 1.10.2|E

However, I am haveing more issues, this time with JKSV. It threw this error while trying to backup all the titles:

 

[Andre63]

Ok, I have dumped my firmware and I'm now on 21.2.0|AMS 1.10.2|E

However, I am haveing more issues, this time with JKSV. It threw this error while trying to backup all the titles:

Are the homebrew up to date?
Yon can take a look here.

Thread 'Preliminary list of updated homebrew apps and tools for FW 21.0.0 | AMS 1.10.0 | Please add your findings!!!'

Nov 17, 2025

UPDATING TO NEW FIRMWARE 21.0.0 IS NOT RECOMMENDED. THERE ARE COMPATIBILITY ISSUES WITH A LOT OF HOMEBREW APPS.

UPDATED APPS for new firmware 21.0.0 (download the MODDED files if there is no official release for FW 21.0.0). USE the modded files with CAUTION. Not all modded apps have been tested.

YOU CAN USE THIS TOOL TO AUTOMATICALLY PATCH your NRO and OVL files to support FW 21.0.0

MAIN TOOLS:
Hekate: Here.
Atmosphère: Here.
sys-patch module: Here.

OTHER TOOLS:
Ultrahand Overlay: Here.
nx-ovlloader for...

• alcab
• Replies: 743
• Forum: Nintendo Switch

• 
• 

 

[HelloShitty]

Are the homebrew up to date?
Yon can take a look here.

Thread 'Preliminary list of updated homebrew apps and tools for FW 21.0.0 | AMS 1.10.0 | Please add your findings!!!'

Nov 17, 2025

UPDATING TO NEW FIRMWARE 21.0.0 IS NOT RECOMMENDED. THERE ARE COMPATIBILITY ISSUES WITH A LOT OF HOMEBREW APPS.

UPDATED APPS for new firmware 21.0.0 (download the MODDED files if there is no official release for FW 21.0.0). USE the modded files with CAUTION. Not all modded apps have been tested.

YOU CAN USE THIS TOOL TO AUTOMATICALLY PATCH your NRO and OVL files to support FW 21.0.0

MAIN TOOLS:
Hekate: Here.
Atmosphère: Here.
sys-patch module: Here.

OTHER TOOLS:
Ultrahand Overlay: Here.
nx-ovlloader for...

• alcab
• Replies: 743
• Forum: Nintendo Switch

• 
• 

I have jut updated JKSV and it worked.
I was now trying to download the modules present before inside /atmosphere/contents and trying to download the latest versions of each one to see if they woul work on the new firmware, but the first one I tried, sent me back to the fatal error. lol.
Now, I have to try to undo it!

Post automatically merged: Jan 16, 2026

Mission Control moule was just upated too, a couple of hours ago! Going to try it!

 

[ELY_M]

you need to get all updated apps and sys-modules. I had to recompile everything I have after I updated to 21

 

[HelloShitty]

you need to get all updated apps and sys-modules. I had to recompile everything I have after I updated to 21

You mean you recompiled all apps in Album menu, the modules you had inside /atmosphere/contents, /switch, /bootloader, /bootloader/payloads, etc?
Yes, I will wait a few days to get them compiled and only download them and put them in their places!

 

[TomSwitch]

Sorry for this reply. I wasn't being able to put all text in a single reply.

You need to clean the setup before copying files. Starting with no sdmc:\atmosphere directory copy over the content of AMS's zip should allow you to boot using fusee. sys-patch is required if you're running unofficial content, and you may also want to set up a method to block Nintendo’s servers.

 

[HelloShitty]

You need to clean the setup before copying files. Starting with no sdmc:\atmosphere directory copy over the content of AMS's zip should allow you to boot using fusee. sys-patch is required if you're running unofficial content, and you may also want to set up a method to block Nintendo’s servers.

Yeah, I got all that! I think problem was with hekate_pil.ini file!

 

[TomSwitch]

Yeah, I got all that! I think problem was with hekate_pil.ini file!

Do you mean ipl?
Try
[fusee]
payload=bootloader/payloads/fusee.bin

Make sure you have the correct fusee.bin

I think any hekate version should work just fine with that.