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

bth · Feb 15, 2026

Xmortal said:
It's your file because after copying my backup it started working again. I'm not doing anything different.

It doesn't work that way.

Hayato213 · Feb 15, 2026

Xmortal said:
Your file has a problem; I just copied, pasted, and replaced it. When loading the emuMMC, after the Atmosphere logo, the screen stays black, and then Hekate doesn't start.

They are just text files so it is impossible to brick, it has to do with the soldering for the modchip.

browntigerz · Feb 16, 2026

Xmortal said:
Your file has a problem; I just copied, pasted, and replaced it. When loading the emuMMC, after the Atmosphere logo, the screen stays black, and then Hekate doesn't start.

in /atmosphere/kip_patches/ delete loader_patches and fs_patches

in exefs_patches folder delete es_patches, nfim_ctest and nim_ctest

After you delete them try booting into emummc again

bth · Feb 16, 2026

browntigerz said:
in /atmosphere/kip_patches/ delete loader_patches and fs_patches

in exefs_patches folder delete es_patches, nfim_ctest and nim_ctest

After you delete them try booting into emummc again

/bootloader/patches.ini and /atmosphere/kip_patches/ doesn't collide, like, ever.

infact, unless the user deliberatly uses a modified fusee.bin (not hekate, not atmosphere's official fusee.bin), /atmosphere/kip_patches/ are never loaded.

the functionality to load kip_patches was removed from atmosphere long ago. Only people who compile atmosphere with the change reverted can use them.

Thelastunicorn · Feb 16, 2026

froggy55 said:
so i just downloaded diablo 2 from the web and installed with awoo via usb and it still wont boot the game i still get the error the software was closed because an error occurred

You need Sys-patch 1.5.8 for Atmosphere 1.10.2

froggy55 · Feb 16, 2026

Thelastunicorn said:
You need Sys-patch 1.5.8 for Atmosphere 1.10.2

thanks for the reply man but i solved this a long time ago by doing just what you said cheers

WolfHOwl · Feb 17, 2026

Hello. I have version 21.2.0 with AMS 1.10.2. Some games install fine and then some, like Little nightmares 2, I can only install using DBI (awoo says invalid nca detected and when I click continue it says failed to install...). When the base game finishes installing through dbi it is just a black square with a loading circle/ If I install the update it gives me the logo but says there is trouble loading the game everytme. I thought it was the game but it installs just fine on my other switch and I have redownloaded from several sites just to make sure. I thought it was the sigpatches but downloaded the ones on this thread and same thing happens. Any ideas?

bth · Feb 17, 2026

WolfHOwl said:
Hello. I have version 21.2.0 with AMS 1.10.2. Some games install fine and then some, like Little nightmares 2, I can only install using DBI (awoo says invalid nca detected and when I click continue it says failed to install...). When the base game finishes installing through dbi it is just a black square with a loading circle/ If I install the update it gives me the logo but says there is trouble loading the game everytme. I thought it was the game but it installs just fine on my other switch and I have redownloaded from several sites just to make sure. I thought it was the sigpatches but downloaded the ones on this thread and same thing happens. Any ideas?

it's unlikely the second console can have it installed, while the first cannot. Unless the other console has sys-patch instead of sigpatches?

either way, if you are missing FS patches (patches.ini) for 21.2.0, then that could happen, if the nca is signature broken, like it might be since awoo says the nca is invalid, which implies someone tampered with the game files.

WolfHOwl · Feb 17, 2026

bth said:
it's unlikely the second console can have it installed, while the first cannot. Unless the other console has sys-patch instead of sigpatches?

either way, if you are missing FS patches (patches.ini) for 21.2.0, then that could happen, if the nca is signature broken, like it might be since awoo says the nca is invalid, which implies someone tampered with the game files.

I believe the sys-patch is the issue. Just got finished reading a bit more on that and didn't realize it wasn't going to be as easy as pasting the new sigpatches as before. Now I'm working on learning this syspatch deal.

*Update It was syspatch and it was a much easier fix than I though that would be. Thanks.

Grandepuffoo · Feb 17, 2026

Hi!
I hacked my switch time ago and I am finding myself a bit confused coming back to the scene after a while.

I am currently on the firmware 19 (can't remember the specific one) and wanted to upgrade to play Mario Galaxy, but apparently things changed with that firmware update.

I am a bit confused with the new sigpatches system, what should I do to update in the most hassle-free way possible?

bth · Feb 17, 2026

Grandepuffoo said:
Hi!
I hacked my switch time ago and I am finding myself a bit confused coming back to the scene after a while.

I am currently on the firmware 19 (can't remember the specific one) and wanted to upgrade to play Mario Galaxy, but apparently things changed with that firmware update.

I am a bit confused with the new sigpatches system, what should I do to update in the most hassle-free way possible?

for end-user related user-experience, sys-patch is always the superior system.

"sigpatches" (the ones from example, this thread) will stop working inbetween firmware versions, even if the offset and patch being applied are exact same between the firmware versions, if nintendo recompiled it and made the moduleID or buildhash (for FS) be different, and a new one for EVERY version of atmosphere.
not all firmware versions have such changes, sometimes the same patch "sigpatch" will work between many firmware versions, as that is just nintendo not updating it.

sys-patch does not have to do that as it patches it on the fly through code using regex patterns, rather than static files needing the filename to be the modulename any of the exefs_patches or sha256 of FS ("kip_patches") to be present with the correct offset+patch

petspeed · Feb 18, 2026

Grandepuffoo said:
Hi!
I hacked my switch time ago and I am finding myself a bit confused coming back to the scene after a while.

I am currently on the firmware 19 (can't remember the specific one) and wanted to upgrade to play Mario Galaxy, but apparently things changed with that firmware update.

I am a bit confused with the new sigpatches system, what should I do to update in the most hassle-free way possible?

I am on 19.0.1 and Super Mario Galaxy 1 & 2 works fine. No need to update

Grandepuffoo · Feb 18, 2026

bth said:
for end-user related user-experience, sys-patch is always the superior system.

"sigpatches" (the ones from example, this thread) will stop working inbetween firmware versions, even if the offset and patch being applied are exact same between the firmware versions, if nintendo recompiled it and made the moduleID or buildhash (for FS) be different, and a new one for EVERY version of atmosphere.
not all firmware versions have such changes, sometimes the same patch "sigpatch" will work between many firmware versions, as that is just nintendo not updating it.

sys-patch does not have to do that as it patches it on the fly through code using regex patterns, rather than static files needing the filename to be the modulename any of the exefs_patches or sha256 of FS ("kip_patches") to be present with the correct offset+patch

petspeed said:
I am on 19.0.1 and Super Mario Galaxy 1 & 2 works fine. No need to update

Ok, thank you so much. I should have managed to set everything up.

Maybe I was on 18 then. I can't remember exactly, I just remember that when Galaxy came on switch it came with a new update which made it incompatible and I didn't do it then

sahey · Feb 19, 2026

Mars04 said:
Hi, I just updated my firmware on emunand(via daybreak) and OFW(normal update via eshop), as I saw Hekate supported the new firmware. Normally Atmosphere also always do with a minor updates. But for some reason I can't get Atmosphere booted anymore after I updated to FW 20.2.0. I first thought it maybe was cause of Syspatch, so I deleted syspatch and ovlmenu from my device, and the content map(420000000000000B) as well. But still I don't get Atmosphere booted up.

Anyone have same issue? Now at the moment I don't mind so much as my son plays OFW most of the time anyway and that one works. But I just would like to get an idea in which direction I have to look for this issue. I always get the error seen in the attachment. Thanks in advance.
View attachment 516669

Post automatically merged: Jul 15, 2025

Sorted the issue out. Couldn't find earlier that there do are issues with Atmosphere if you update. But I used the AMS which you posted in another thread that does work with new FW. Thanks alot

can you share more details how to fix the error and link to another thread?

bth · Feb 19, 2026

sahey said:
can you share more details how to fix the error and link to another thread?

You just update atmosphere and hekate... There's no extra steps to it.

dzik · Feb 22, 2026

Thelastunicorn said:
You need Sys-patch 1.5.8 for Atmosphere 1.10.2

Do I need to update fw to 21.1.0 ? currently I have 19

Hayato213 · Feb 22, 2026

dzik said:
Do I need to update fw to 21.1.0 ? currently I have 19

That is up to you as the firmware goes up there is less amount of memory for homebrew and sys modules so it come down to what you need, eventually there will be games that can't be patched to firmware 18.1.0 and 19.0.0

dzik · Feb 22, 2026

Hayato213 said:
That is up to you as the firmware goes up there is less amount of memory for homebrew and sys modules so it come down to what you need, eventually there will be games that can't be patched to firmware 18.1.0 and 19.0.0

thanks for reply. I asked because I experienced this problem with D2 ROW and I don't know that is there any way to play it with v19 or I must update

Hayato213 · Feb 22, 2026

dzik said:
thanks for reply. I asked because I experienced this problem with D2 ROW and I don't know that is there any way to play it with v19 or I must update

You can try patching it but if it doesn't run on 19.0.0 then you probably have to update, there is more stuffs to keep in mind about 20.x.x and above, there is the slow down in the home menu and battery drain issue that can be fixed with few lines for the atmosphere config.

MiloDragon1999 · Feb 22, 2026

impeeza said:
*** Updated 2026 - 01 - 12 ***

Sigpatches updated for 21.2.0,

And Upgraded to Atmosphère 1.10.1 (no version for FW 21.2.0 yet)

SYS-Patch should work fine with this FW too.

Hi all, can I use this update for my AMS1.9.5? I have an issue with MH Rise, I think update sigpatches will help me.

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

Well-Known Member

Newcomer

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

New Member

Well-Known Member

New Member

Member

Well-Known Member

Well-Known Member

Member

New Member

Well-Known Member

Member

Newcomer

Member

Newcomer

New Member

Attachments

Similar threads

Popular threads in this forum