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

[ManoloGeimer777]

Read the OP

Post automatically merged: May 12, 2025

NO. Never update your console unless you know what are you doing or the scene is in a very safe state for that firmware

i update my console without unistalling the theme i install before i update and when i boot without hack after the 2 logos of nintendo it appears "the software could not open" i dont know what to do pls help me

Post automatically merged: May 12, 2025

i update my console without unistalling the theme i install before i update and when i boot without hack after the 2 logos of nintendo it appears "the software could not open" i dont know what to do pls help me

i can only access on hekate

 

[Blythe93]

does anyone have the updated sigpaches?

Here they are. Remember to read the first post in this thread before asking whether they are available or not from now on.

Hi is it safe to update Emunand to 20.0.0?

Sysnand is updated to 20.0.0, atmosphere+Hekate is up to date, I have sys-patch 1.5.6 installed but idk if it's safe to update Emunand to 20.0.0 and my Emunand is still on 19.0.1. thanks

My emuNAND works perfectly fine on 20.0.1. However, it's not necessary to update to the latest firmware, especially if you're using mods (a lot of them) for some games like The Legend of Zelda Tears of the Kingdom as Atmosphere may crash due to the less memory available for sys-modules that Nintenodo introduced with all those new fancy features. Check the release notes here for more info.

Will these sigpatches work on Emunand 20.0.0?

If they are updated to work on firmware 20.0.0 (and by extension 20.0.1), I don't see why the wouldn't work on 20.0.0? With that said, Since you have sys-patch already, you don't need sigpatches (i.e. two things doing the same thing). That's just unnecessary clutter on your SD card.

i can only access on hekate

Check this reply and see if that works. Don't post all over the place the very same question.

 

[aaaaaaaaaaaaaaaaaaaa]

Read the OP

Post automatically merged: May 12, 2025

NO. Never update your console unless you know what are you doing or the scene is in a very safe state for that firmware

I won't update then thanks.

 

[martinlvm]

Same again...

Thank you so much ! I just created the account to thank you hahaha.

Can I ask you what modifications you made to make it work ? I would like to know to make them myself for future updates.

Thanks !

 

[Emrah1925]

Hello. How long does it take on average for Atmosphere to be released as a stable version?

 

[impeeza]

Hello. How long does it take on average for Atmosphere to be released as a stable version?

HASN'T BEEN A NON PRE-RELEASE VERSION FOR YEARS, BUT IF YOU WHERE ABLE TO READ THE RELEASE NOTES OF THE ATMOSPHÈRE GITHUB YOU WILL FIND OUT IS A VERY TESTED VERSION AND IF YOU FIND ANY ISSUE YOU CAN OPEN A BUG REPORT ON THE SAME GITHUB.

 

[user_root]

Hello, i'm having an hard time using sigpatches. Which is weird because i've done that a ton of times.
I downloaded the latest sigpatches from the original post, at the top, and drag and dropped the content onto my SD card, as usual.

Here's also my current hekate_ipl.ini file:

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

[CFW]
pkg3=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/cfw.bmp


[OFW]
pkg3=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/ofw.bmp

I'm kinda confused, any ideas please? Thank you!

Atmosphere version: Atmosphère 1.9.0 (pre-release)
Hekate version: hekate v6.3.0 & Nyx v1.7.0
Switch version: 20.0.1

 

[impeeza]

Hello, i'm having an hard time using sigpatches. Which is weird because i've done that a ton of times.
I downloaded the latest sigpatches from the original post, at the top, and drag and dropped the content onto my SD card, as usual.

Here's also my current hekate_ipl.ini file:

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

[CFW]
pkg3=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/cfw.bmp


[OFW]
pkg3=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/ofw.bmp

I'm kinda confused, any ideas please? Thank you!

Atmosphere version: Atmosphère 1.9.0 (pre-release)
Hekate version: hekate v6.3.0 & Nyx v1.7.0
Switch version: 20.0.1

install sys-patch sysmodule and report your findings

 

[user_root]

install sys-patch sysmodule and report your findings

This is the first time i use sys-patch (i kinda like the old-school way) and it seems to work properly, very weird, i don't understand what i'm doing wrong especially since i've had a ton of switch consoles in my hands and always did the same thing to install sigpatches.

I guess it's time to move on...

 

[alcab]

Does anyone have a modded fusee.bin for using sigpatches?

Thanks!

 

[impeeza]

Does anyone have a modded fusee.bin for using sigpatches?

Thanks!

yes on previous pages,

 

[alcab]

Sorry, I completely missed this message.
Thanks a lot!!

AMS for firmware 20.0.1 here.
Hekate for firmware 20.0.1 here.
Modded AMS for firmware 20.0.1 that allows the use of sigpatches here.
Sigpatches for firmware 20.0.1 here.
Sys-patch for firmware 20.0.1 here.
Lockpick RCM for firmware 20.0.1 here.
Mission Control for firmware 20.0.1 here.

Instructions on how to migrate from sigpatches to sys-patch here (read three messages).
Instructions on how to modify hekate_ipl.ini for the new version of Hekate here.
Ultimate guide by impeeza on how to update your firmware/Atmosphère here.


thank you @impeeza and @Blythe93!

 

[Ibim]

I can’t launch any games on sysmmc. It always says checking software information and then game coulnd‘t be launched. OFW works fine. Do I need to install these so that sysmmc works properly again?

 

[QTrue]

thank you @alcab This summary was very helpful!

 

[impeeza]

Hello, i'm having an hard time using sigpatches. Which is weird because i've done that a ton of times.
I downloaded the latest sigpatches from the original post, at the top, and drag and dropped the content onto my SD card, as usual.

Here's also my current hekate_ipl.ini file:

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

[CFW]
pkg3=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/cfw.bmp


[OFW]
pkg3=atmosphere/package3
emummc_force_disable=1
stock=1
icon=bootloader/res/ofw.bmp

I'm kinda confused, any ideas please? Thank you!

Atmosphere version: Atmosphère 1.9.0 (pre-release)
Hekate version: hekate v6.3.0 & Nyx v1.7.0
Switch version: 20.0.1

Well, I think this is not directly related to sigpatches but, Hekate 6.3.1 introduces some changes on the names of some keys/values pairs of Hekate_ipl.ini file. The most important changes are:

The Key fss0 was used to indicate in a boot entry to load a Atmopshère's package3 (or a FSO file), extract the needed parts and boot from them. Today the Key name has been renamed to pkg3. So you must change any config like fss0=atmosphere/package3 by pkg3=atmosphere/package3

Also was widely used the config atmosphere=1 which has not been needed for a while because if you set the setting fss0 that setting have NO relevance because the patching is done for the extracted parts of Package3; so you can remove it now on most boot entries.
That key has been renamed to kernelprocid, when you enable that setting the kernel process id send/recv patching is enables for stock HOS. Any needed reference to atmosphere key should be renamed to kernelprocid and used only on stock boot entries.

By example, the example Hekate_ipl.ini included on early versions of the sigpatches file have to be changed, the strikeout text should be removed and new text is marked with bold:

---

[config]
autoboot=2
autoboot_list=0
bootwait=1
noticker=0
autohosoff=1
autonogc=1
bootprotect=0
updater2p=1
backlight=91


{--- Custom Firmware ---}
{--- SYSNAND START---}
[CFW (SYSNAND)]
id=SYSNAND
emummc_force_disable=1
fss0pkg3=atmosphere/package3
atmosphere=1
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/atmosphere_hue_nobox.bmp
kip1patch=nosigchk
{--- SYSNAND END ---}

{--- EMUNAND START---}
[CFW (EMUMMC)]
id=EMUNAND
emummcforce=1
fss0pkg3=atmosphere/package3
atmosphere=1
logopath=bootloader/EnergyStarBL.bmp
icon=bootloader/res/payload_hue_nobox.bmp
kip1patch=nosigchk
usb3force=1
{--- EMUNAND END ---}
{--- Custom Firmware END ---}


{--- STOCK Firmware ---}
{--- Semi Stock start pkg3---}
[Semi Stock (SYSNAND)]
id=SMSTOCK
emummc_force_disable=1
fss0pkg3=atmosphere/package3
atmospherekernelprocid=1
icon=bootloader/res/switch_hue_nobox.bmp
{--- Stock END ---}

{--- Semi Stock start fusee.bin---}
[Semi Stock (SYSNAND)]
id=SMSTOCK
emummc_force_disable=1
payload=atmosphere/reboot_payload.bin
atmospherekernelprocid=1
icon=bootloader/res/switch_hue_nobox.bmp
{--- Stock END ---}

{---Stock START---}
[ Stock (SYSNAND)]
id=FSTOCK
emummc_force_disable=1
fss0pkg3=atmosphere/package3
stock=1
icon=bootloader/res/switch_hue_nobox.bmp
{--- Stock END ---}
{--- STOCK Firmware end---}

{--- PAYLOADS ---}
{--- LockPick payload ---}
[LockPick_RCM]
id=LockPick
payload=bootloader/payloads/LockPick_RCM.bin
logopath=bootloader/res/LPBootLogo.bmp
icon=bootloader/res/LockPick_hue_nobox.bmp
{--- LockPick payload end ---}


{--- TegraExplorer payload ---}
[TegraExplorer]
id=TegraExplorer
payload=bootloader/payloads/TegraExplorer.bin
logopath=bootloader/res/TegraExplorerBootLogo.bmp
icon=bootloader/res/TegraExplorer_hue_nobox.bmp
{--- TegraExplorer payload end---}
{--- PAYLOADS END ---}

 

[Blythe93]

I can’t launch any games on sysmmc. It always says checking software information and then game coulnd‘t be launched. OFW works fine. Do I need to install these so that sysmmc works properly again?

Do your sigpatches work properly? Atmosphere 1.7.0 and newer no longer supports ips kip patches (check the release notes here) which are usually used for piracy reasons. Therefore sigpatches won't work unless you:

1. Load Atmosphere's package3 via Hekate's FSS0 - You'll need to reboot to Hekate, go to Launch and select emuNAND CFW or sysNAND CFW (depending on which one you use). If you've downloaded the sigpatches from here. your bootloader/hekate_ipl.bin will already have everything you need to have configured.
2. Use modified Atmosphere's fusee.bin payload with ips kip patches support.
3. Use sys-patch instead of sigpatches.

For the sake of simplicity, I generally suggest and personally use sys-patch nowadays. Make sure to reboot your Switch for sys-patch to start working properly and see if games work after that.

 

[user_root]

Quick question, switching from sigpatches to sys-patch, what my IPL file should looks like? I simply remove "kip1patch=nosigchk" ?

Thats what i did and it works of course, i'm just asking to make sure it's all you have to do

 

[impeeza]

Quick question, switching from sigpatches to sys-patch, what my IPL file should looks like? I simply remove "kip1patch=nosigchk" ?

Thats what i did and it works of course, i'm just asking to make sure it's all you have to do

yes that is what you need to do if you remove the file «patches.ini» in order to avoid Hekate warnings on boot.

 

[xXSoulGeoXx]

Sorry, I completely missed this message.
Thanks a lot!!

AMS for firmware 20.0.1 here.
Hekate for firmware 20.0.1 here.
Modded AMS for firmware 20.0.1 that allows the use of sigpatches here.
Sigpatches for firmware 20.0.1 here.
Sys-patch for firmware 20.0.1 here.
Lockpick RCM for firmware 20.0.1 here.
Mission Control for firmware 20.0.1 here.

Instructions on how to migrate from sigpatches to sys-patch here (read three messages).


thank you @impeeza and @Blythe93!

I have a question
I have done a clean install of Atmosphere and all sys modules last month

Will I need to do a clean install for this new updates? or simply drag-n-drop will be find for me?

already checked, all the sysmodules I use all been updated for 20.0.1
Is there something we need to change manually for AMS for 20.0.1? its the thing I am confused about
if that's the case, what do I need to add?

 

[impeeza]

I have a question
I have done a clean install of Atmosphere and all sys modules last month

Will I need to do a clean install for this new updates? or simply drag-n-drop will be find for me?

already checked, all the sysmodules I use all been updated for 20.0.1
Is there something we need to change manually for AMS for 20.0.1? its the thing I am confused about
if that's the case, what do I need to add?

https://gbatemp.net/threads/ultimate-guide-to-upgrade-your-firmware-atmosphere.661148/