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

suloku · Thursday at 12:11 PM

RoninSeito said:
Super simplified guide to setup Sys-Patch:
Download latest vers from github release pages: (currently)
1. "nx-ovlloader 21.0.0 support"
Extract zip to sd root (merge atmosphere folders).
2. "Tesla Menu 21.0.0 support"
Copy ovlmenu.ovl to /switch/.overlays/ovlmenu.ovl (create ". overlays" folder if needed)
3. "Sys-patch version v1.6.2.0"
Copy sys-patch-overlay.ovl to switch/.overlays/sys-patch-overlay.ovl
4. Reboot. Press L + Down + R stick button to open overlay and goto options to verify patches are on.

Note just tested on 22.1.0 and it works

This should be added to the first post. Thanks.

@ShadowOne333 if you are still active this may help people still going back to this thread like me.

Valkyrie743 · Monday at 4:36 AM

hey i've been away for a while and currently updating my switch.

being that no sigpatches updated for 22.1.0 or up anymore and just sys patch. how can i go about deleteing the past sig patches??? or should i just leave them installed?

bth · Monday at 9:52 AM

Valkyrie743 said:
hey i've been away for a while and currently updating my switch.

being that no sigpatches updated for 22.1.0 or up anymore and just sys patch. how can i go about deleteing the past sig patches??? or should i just leave them installed?

not sure what you're talking about.

i am the one who maintains sys-patch, naturally, i am able to also make .ips and hekate patches.

there's also my atmosphere fork at https://tinfoil.io/ams which has all the patches needed built into the source code of atmosphere.

https://github.com/borntohonk/Atmos...ude/mesosphere/kern_k_embedded_fs_patches.hpp
https://github.com/borntohonk/Atmos...sphere/loader/source/ldr_embedded_patches.hpp

the atmosphere fork supports both pkg3/fss0 hekate method of booting, and fusee.

creapas8 · 2026-06-09T22:52:43+0100

Hi all,

This is my first message, I am new to this community. I bought the switch for my girls 3 years ago, and I am updating time to time the console (when they want a recent game).

This week end, I updated from FW 18.1 to FW 20.5.0E using daybreak

Here are the elements I've downloaded and updated :
- atmosphere-1.11.1-master-d04c20a04+hbl-2.4.5+hbmenu-3.6.1
- hekate_ctcaer_6.5.2_Nyx_1.9.2
- sys-patch-v1.6.1
- NX-20.5.0
- DBI 845-en
- Linkalho 2.0.2

But when trying to launch a game, I have the following error :
"could not start the software.
Please try again from the HOME Menu."

Looking to this forum, I've applied the following change in my atmosphere/config/system_settings.ini
[olsc]
enable_olsc_communication_block = u8!0x1
default_auto_download_global_setting = u8!0x0
default_auto_upload_global_setting = u8!0x0

and restarted the console, but I still have the same error when trying to start a game (I tried several games and always same error).

When I delete and re-install a game with DBI, I have this error message
Missing ES sigpatches!
There were errors during ticket installation. Check for ES sigpatches
ERRORS FOUND DURING FILE TRANSFER. INSTALLATION ABORTED

Until now I was using sigpatches. As it is the first time I am using syspatch so I remove in bootloader\hekate_ipl.ini the following line kip1patch=nosigchk
Here is the full content of my hekate_ipl.ini
[config]
autoboot=0
autoboot_list=0
bootwait=2
backlight=100
autohosoff=1
autonogc=0
updater2p=1
bootprotect=0

[Atmosphere PURO]
payload=bootloader/payloads/fusee.bin
atmosphere=1
icon=bootloader/res/atmosphere.bmp
id=atmos

[Atmosphere PACKAGE3]
fss0=atmosphere/package3
icon=bootloader/res/icon_atmosphere.bmp
customlogo=1
logopath=bootloader/res/boot.bmp
id=pkg3

[sysMMC AMS]
fss0=atmosphere/package3
icon=bootloader/res/icon_sys.bmp
emummc_force_disable=1
customlogo=1
logopath=bootloader/res/sysboot.bmp
id=sysnand

[emuMMC AMS]
fss0=atmosphere/package3
icon=bootloader/res/icon_emu.bmp
emummcforce=1
customlogo=1
logopath=bootloader/res/emuboot.bmp
id=emunand

[Stock]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/switch.bmp
id=stock

[Extraer prod.keys]
payload=bootloader/payloads/Lockpick_RCM.bin
icon=bootloader/res/lockpick.bmp

[TegraExplorer]
payload=bootloader/payloads/TegraExplorer.bin
icon=icon_payload.bmp

[Android 10]
payload=switchroot/android/coreboot.rom
icon=bootloader/res/Switchroot.bmp
customlogo=1
logopath=bootloader/res/android.bmp
id=SWANDR

I don't know what else to do to be able to play again ....

bth · 2026-06-10T11:31:19+0100

creapas8 said:
Hi all,

This is my first message, I am new to this community. I bought the switch for my girls 3 years ago, and I am updating time to time the console (when they want a recent game).

This week end, I updated from FW 18.1 to FW 20.5.0E using daybreak

Here are the elements I've downloaded and updated :
- atmosphere-1.11.1-master-d04c20a04+hbl-2.4.5+hbmenu-3.6.1
- hekate_ctcaer_6.5.2_Nyx_1.9.2
- sys-patch-v1.6.1
- NX-20.5.0
- DBI 845-en
- Linkalho 2.0.2

But when trying to launch a game, I have the following error :
"could not start the software.
Please try again from the HOME Menu."

Looking to this forum, I've applied the following change in my atmosphere/config/system_settings.ini
[olsc]
enable_olsc_communication_block = u8!0x1
default_auto_download_global_setting = u8!0x0
default_auto_upload_global_setting = u8!0x0

and restarted the console, but I still have the same error when trying to start a game (I tried several games and always same error).

When I delete and re-install a game with DBI, I have this error message
Missing ES sigpatches!
There were errors during ticket installation. Check for ES sigpatches
ERRORS FOUND DURING FILE TRANSFER. INSTALLATION ABORTED

Until now I was using sigpatches. As it is the first time I am using syspatch so I remove in bootloader\hekate_ipl.ini the following line kip1patch=nosigchk
Here is the full content of my hekate_ipl.ini
[config]
autoboot=0
autoboot_list=0
bootwait=2
backlight=100
autohosoff=1
autonogc=0
updater2p=1
bootprotect=0

[Atmosphere PURO]
payload=bootloader/payloads/fusee.bin
atmosphere=1
icon=bootloader/res/atmosphere.bmp
id=atmos

[Atmosphere PACKAGE3]
fss0=atmosphere/package3
icon=bootloader/res/icon_atmosphere.bmp
customlogo=1
logopath=bootloader/res/boot.bmp
id=pkg3

[sysMMC AMS]
fss0=atmosphere/package3
icon=bootloader/res/icon_sys.bmp
emummc_force_disable=1
customlogo=1
logopath=bootloader/res/sysboot.bmp
id=sysnand

[emuMMC AMS]
fss0=atmosphere/package3
icon=bootloader/res/icon_emu.bmp
emummcforce=1
customlogo=1
logopath=bootloader/res/emuboot.bmp
id=emunand

[Stock]
fss0=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/switch.bmp
id=stock

[Extraer prod.keys]
payload=bootloader/payloads/Lockpick_RCM.bin
icon=bootloader/res/lockpick.bmp

[TegraExplorer]
payload=bootloader/payloads/TegraExplorer.bin
icon=icon_payload.bmp

[Android 10]
payload=switchroot/android/coreboot.rom
icon=bootloader/res/Switchroot.bmp
customlogo=1
logopath=bootloader/res/android.bmp
id=SWANDR

I don't know what else to do to be able to play again ....

that doesn't sound right, sys-patch 1.6.1 has no issues with firmware 20.5.0, dbi is reporting the wrong information, that or you are misreporting about having sys-patch (not having correctly put it on sd card / not having rebooted after putting it on sd card)

duckbill007 · 2026-06-10T11:45:42+0100

bth said:
dbi is reporting the wrong information

DBI reports about ES sigpatches only on 0x291 error on ImportTicket call. It can be caused either by not turned off signature validation or damaged ticket data. I assume first case because I never encountered damaged tickets in nsp files.

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

Well-Known Member

Member

Well-Known Member

Attachments

New Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum