Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)

[Vin_Thod]

if you don't provide what version of atmosphere you are running and what firmware version you're running, then can't really help you.

if ams 1.9.5 and 20.5.0 and below, use sys-patch 1.5.6
if 1.10 and above, use any version of sys-patch of 1.5.7 or above

hello,
AMS 1.10.1.0E
HOS 21.0.1
used latest sys-patch before but returned nosigchk error then reverted. sigpatches removed the error now but presented with software failure. reinstalling games does nothing. atleast zelda botw & totk works

 

[bth]

hello,
AMS 1.10.1.0E
HOS 21.0.1
used latest sys-patch before but returned nosigchk error then reverted. sigpatches removed the error now but presented with software failure. reinstalling games does nothing. atleast zelda botw & totk works

"nosigchk error" is a hekate concept.

delete the lines saying nosigchk in hekate_ipl.ini or add the hekate patches.ini (required for "that kind of sigpatches")

 

[Vin_Thod]

if you don't provide what version of atmosphere you are running and what firmware version you're running, then can't really help you.

if ams 1.9.5 and 20.5.0 and below, use sys-patch 1.5.6
if 1.10 and above, use any version of sys-patch of 1.5.7 or above

hello,
ams 1.10.1e
hos 21.0.1
sys-patch 1.5.9 (doesnt work)
sigpatches 2025/8/12 (partially work)

reinstalling game doesnt fix either haha

 

[bth]

hello,
ams 1.10.1e
hos 21.0.1
sys-patch 1.5.9 (doesnt work)
sigpatches 2025/8/12 (partially work)

reinstalling game doesnt fix either haha

so you posting this again a second time, out of confusion, does not change my previous answer.

sys-patch 1.5.9 works just fine, it's your hekate configuration that's messed up.

 

[Vin_Thod]

"nosigchk error" is a hekate concept.

delete the lines saying nosigchk in hekate_ipl.ini or add the hekate patches.ini (required for "that kind of sigpatches")

let me try

Post automatically merged: Dec 29, 2025

so you posting this again a second time, out of confusion, does not change my previous answer.

sys-patch 1.5.9 works just fine, it's your hekate configuration that's messed up.

yeah bad internet lol

Post automatically merged: Dec 29, 2025

"nosigchk error" is a hekate concept.

delete the lines saying nosigchk in hekate_ipl.ini or add the hekate patches.ini (required for "that kind of sigpatches")

yes this works.
latest sys-patch 1.5.9

 

[Mossymus]

Hi everyone, I need help to find the sigpatch for my switch (19.0.1 | AMS 1.8.0 | S). Does this still work? Do I need to update my FW or use a Hakate?

 

[bth]

Hi everyone, I need help to find the sigpatch for my switch (19.0.1 | AMS 1.8.0 | S). Does this still work? Do I need to update my FW or use a Hakate?

update to version atmosphere 1.9.5 and firmware version 20.5.0, and yes update hekate to max.
pair with sigpatches from this thread or sys-patch 1.5.6

if you go beyond atmosphere 1.9.5/firmware version 21.0.0+ then sys-patch 1.5.9

 

[Mossymus]

update to version atmosphere 1.9.5 and firmware version 20.5.0, and yes update hekate to max.
pair with sigpatches from this thread or sys-patch 1.5.6

if you go beyond atmosphere 1.9.5/firmware version 21.0.0+ then sys-patch 1.5

update to version atmosphere 1.9.5 and firmware version 20.5.0, and yes update hekate to max.
pair with sigpatches from this thread or sys-patch 1.5.6

if you go beyond atmosphere 1.9.5/firmware version 21.0.0+ then sys-patch 1.5.9

Is it possible that I don’t update the FW? Cuz the problem I ran into currently is that when I download a game from tinfoil, it shows no software. And I found it may be caused by a missing sigpatch.

 

[glitcher]

if you don't provide what version of atmosphere you are running and what firmware version you're running, then can't really help you.

if ams 1.9.5 and 20.5.0 and below, use sys-patch 1.5.6
if 1.10 and above, use any version of sys-patch of 1.5.7 or above

Thanks alot! sys-patch 1.5.6 in combination with the latest sigpatches worked!
I also used the following bootloader/hekate_ipl.ini content (I have no idea if all settings are right, but that worked):

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

[CFW - sysMMC]
pkg3=atmosphere/package3
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
pkg3=atmosphere/package3
emummcforce=1
icon=bootloader/res/icon_payload.bmp

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

I also used the Tinfoil NSP and installed it using Goldleaf, this also worked! (but starting while pressing R button seems to be essential too)

 

[FanNintendo]

https://rentry.org/ExosphereDNSMITM

so that mean i can go online with retroarch update my assets and download new cores or thumbnails with no worries?

 

[Hayato213]

so that mean i can go online with retroarch update my assets and download new cores or thumbnails with no worries?

That only block Nintendo server communication doesn't mean no wifi.

 

[glitcher]

Thanks alot! sys-patch 1.5.6 in combination with the latest sigpatches worked!
I also used the following bootloader/hekate_ipl.ini content (I have no idea if all settings are right, but that worked):

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

[CFW - sysMMC]
pkg3=atmosphere/package3
emummc_force_disable=1
icon=bootloader/res/icon_payload.bmp

[CFW - emuMMC]
pkg3=atmosphere/package3
emummcforce=1
icon=bootloader/res/icon_payload.bmp

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

I also used the Tinfoil NSP and installed it using Goldleaf, this also worked! (but starting while pressing R button seems to be essential too)

I was wrong it still does not start! I accidentially started CFW sysMMC and it worked there...

I compleytely formatted my SD card, re-installed Atmosphere andre-created emuMMC. Then I just used the mentioned sys-patches. Still the software is ended with the error message, no matter if I start a game or Tinfoil.
I am on FW 21.1.0 and Atmosphere 1.10.1.

Does anyone know how to fix this?

 

[Deleted member 782613]

It works for me

 

[bth]

Fixed a bug with Tinfoil, which now works with 21.1.0 and Atmosphere. Recompiled the package3 file, just overwrite the one in the Atmosphere directory.

forcing mesosphere to ignore 0x108 TLS restriction and recompiling atmosphere with pre 0x180 TLS libnx isn't "fixing bug with tinfoil".

you'd have to do both. 21.0.0+ writes to 0x108 to 0x110 TLS though, so it's not good behaviour to try force it. just wait for tinfoil to be recompiled.

also GPLV2
https://github.com/Atmosphere-NX/Atmosphere?tab=GPL-2.0-1-ov-file#readme

provide the source code for your binaries now.

Post automatically merged: Dec 29, 2025

I was wrong it still does not start! I accidentially started CFW sysMMC and it worked there...

I compleytely formatted my SD card, re-installed Atmosphere andre-created emuMMC. Then I just used the mentioned sys-patches. Still the software is ended with the error message, no matter if I start a game or Tinfoil.
I am on FW 21.1.0 and Atmosphere 1.10.1.

Does anyone know how to fix this?

atmosphere 1.10+ (not firmware version 21.0.0) doesn't support tinfoil as it uses TLS of 0x108.

atmosphere 1.10, as opposed to atmosphere 1.9.5, enforces TLS of 0x180, or very least, 0x110, as 0x108 is restricted due to the bytes being written to in 21.0.0+

downgrade to 20.5.0 and downgrade atmosphere to 1.9.5 until tinfoil is recompiled.

other games not starting is you missing patches/having booted once without patches (requires re-install)

 

[ussdssss]

Please help me. I have firmware 20.5 and Atmosphere 1.10.1, but when I launch the console, it crashes with error 2162-0002. I understand that the problem is with sigpatches, which I haven't installed. Can anyone share all the necessary patches for my case? please

 

[FanNintendo]

That only block Nintendo server communication doesn't mean no wifi.

Still Oops ?

 

[grassblade]

Hi team, I have just migrated from sxos to atmosphere and my current firmware is 10.2.0 | AMS 1.10.1 | E. I tried with latest sigpatches but it didn't work. Which sigpatches should I use or which workflow should I follow?

I appreciate your help and responses.

 

[Hayato213]

Hi team, I have just migrated from sxos to atmosphere and my current firmware is 10.2.0 | AMS 1.10.1 | E. I tried with latest sigpatches but it didn't work. Which sigpatches should I use or which workflow should I follow?

I appreciate your help and responses.

Are the patches in the correct directory though?

 

[grassblade]

Are the patches in the correct directory though?

Yes, atmosphere and bootloader directories at ssd root.

Post automatically merged: Dec 30, 2025

Yes, atmosphere and bootloader directories at ssd root.

Looks like this:
/atmosphere
├─ exefs_patches
├─ kip_patches
└─ ...
/bootloader
├─ patches
└─ ...

 

[Hayato213]

Yes, atmosphere and bootloader directories at ssd root.

Post automatically merged: Dec 30, 2025

Looks like this:
/atmosphere
├─ exefs_patches
├─ kip_patches
└─ ...
/bootloader
├─ patches
└─ ...

Keep in mind you have to use hekate to load atmosphere not fusee.