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

[bombayjack]

Sorry to bother you about this, but I just wanted to confirm something before I attempt this. Does setting up an additional emunand require deleting any data on the SD? My 500GB Switch SD has about 40GB left and ideally I would like to use that space for a second emunand just for MP4, but I don't want to affect anything on the existing emunand because I have everything set up perfectly and dont want to have to set any of that stuff up again. I'm seeing from the screenshots in the nxNandManager that the tools seem to indicate that "all data on target disk will be erased," and if thats the case i would probably not want to go through with it. Thanks in advance for your advice with this.

My emunands are just under 3GB in space. What to do is dump your nand with hekate, then copy it to your PC. Open the latest NxNandManager and use your dumped prod keys with it. Open the dumped image 00 file.
Next click on tools, then resize nand (set size to 64mb), Next open the dumped RAWNAND.resized, right click on user, dump advanced, select passthrough zero /decrypt/and format user partiton. Save the user.bin to the pc, Now right click on user again, restore from file and select the user.bin file you just saved. Rename RAWNAND.resized to 00, now just keep the new 00 file and replace it with the orignal you dumped. You can remove all other files stating with 01-02 etc. Then you put them in your switch emunand folder, it should look like this:

emummc/XXXX/eMMC/00
emummc/XXXX/eMMC/BOOT0
emummc/XXXX/eMMC/BOOT1

You can replace XXXX with any 4 digit number or name. In hakete you can switch emunands by clicking on the emunand icon then just select the XXXX one. That way your new emunand will only take up just under 3GB of your sd card.

 

[xXSoulGeoXx]

they are now on the OP

Post automatically merged: Dec 6, 2025

*** Updated 2025 - 26 - 12 ***

Sigpatches updated for 21.0.1,

And Upgraded to Atmosphère 1.10.0

THEY ARE ON THE POST 5494

It is a good idea to keep sigpatches updated? or I'm fine with the ones uploaded in november?
Also, I been getting confused with the settings on hekate_ipl.ini

since I mostly just use the one that comes already prepared from the NH Switch Guide from this part of the process
https://switch.hacks.guide/user_guide/all/sd_preparation.html

Got sigpatches and Sys-Patch 1.5.8 v5 from the github on my SD Card, and my games run without problems
but just to be sure
Is there anything I should change here from my hekate_ipl.ini?
Should I add the "kip1patch=nosigchk" line, or everything's fine with Sys-patch also on my SD Setup?

 

[Earthshine]

always you man

Always you man. Sorry you don't like misinformation being corrected and thought out explanations of why the misinformation is wrong. Too much for ya to handle? Cope, seethe, cope, little fella. And why are you on my dick anyway? Always sticking your nose in with completely useless comments that have nothing to do with the conversation or topic. Getting to the point of weird stalker shit. Get away from me. You're gross and you creep me out.

 

[Insektaure]

It is a good idea to keep sigpatches updated? or I'm fine with the ones uploaded in november?
Also, I been getting confused with the settings on hekate_ipl.ini

since I mostly just use the one that comes already prepared from the NH Switch Guide from this part of the process
https://switch.hacks.guide/user_guide/all/sd_preparation.html

Got sigpatches and Sys-Patch 1.5.8 v5 from the github on my SD Card, and my games run without problems
but just to be sure
Is there anything I should change here from my hekate_ipl.ini?
Should I add the "kip1patch=nosigchk" line, or everything's fine with Sys-patch also on my SD Setup?

Adding kip1patch=nosigchk in your hekate_ipl file will trigger the use of sigpatches files in fss0/pkg3 mode (the one required to use them at atmosphere boot).

Without this line they will not be used, and only syspatch will.

If you don't have sigpatches files, and use this line in your hekate_ipl file, you can have an error when starting atmosphere (it tries to load patches but no files are present).

If syspatch is working as intended in you system, you can just use this, as the goal of the 2 are the same.

In the past having them both could help in case of one or the other was not properly updated, but I can't tell if this is still the case nowadays, as I switch to purely syspatch before upgrading to FW 21.

As per my testing, in FW 20.5.0 & FW 21.0.0 / 21.0.1, having only syspatch does the job and all games are able to launch (airplane mode or with the 3 lines for OLSC in atmosphere system_settings.ini if you want to launch with wifi on).

 

[xXSoulGeoXx]

Adding kip1patch=nosigchk in your hekate_ipl file will trigger the use of sigpatches files in fss0/pkg3 mode (the one required to use them at atmosphere boot).

Without this line they will not be used, and only syspatch will.

If you don't have sigpatches files, and use this line in your hekate_ipl file, you can have an error when starting atmosphere (it tries to load patches but no files are present).

If syspatch is working as intended in you system, you can just use this, as the goal of the 2 are the same.

In the past having them both could help in case of one or the other was not properly updated, but I can't tell if this is still the case nowadays, as I switch to purely syspatch before upgrading to FW 21.

As per my testing, in FW 20.5.0 & FW 21.0.0 / 21.0.1, having only syspatch does the job and all games are able to launch (airplane mode or with the 3 lines for OLSC in atmosphere system_settings.ini if you want to launch with wifi on).

So there's no need to change or add lines on my hekate_ipl.ini file, right?
thouhg, If I were to add that line
where should I put it in the first place?
and it would affect the use of Sys-Patch?
thanks for answering btw
Most people say to add the line, but I noticed it worked just fine with the hekate_ipl.ini file given on the NH Switch Hack Guide, and putting the contents of sigpatches and Sys-patch to the root of my SD Card

Edit: would like to add, Metroid Prime 4 Beyond installed fine on 20.5.0 on Atmosphere 1.9.5
same with Pokemon Legends A-Z

 

[Insektaure]

So there's no need to change or add lines on my hekate_ipl.ini file, right?
thouhg, If I were to add that line
where should I put it in the first place?
and it would affect the use of Sys-Patch?
thanks for answering btw
Most people say to add the line, but I noticed it worked just fine with the hekate_ipl.ini file given on the NH Switch Hack Guide, and putting the contents of sigpatches and Sys-patch to the root of my SD Card

Edit: would like to add, Metroid Prime 4 Beyond installed fine on 20.5.0 on Atmosphere 1.9.5
same with Pokemon Legends A-Z

No need to change the file if you are only using syspatch.

Having both is redundant at this point.

Syspatch is a sysmodule that will trigger on boot, and will stop itself when patching is done.

If you want to add the line to keep both, here is an example of my previous hekate_ipl where you can see the line.
If only syspatch, remove it.

[config]
updater2p=1

[Atmosphere FSS0 emuMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
emummcforce=1
atmosphere=1
icon=bootloader/res/emu_boot.bmp

[Atmosphere FSS0 sysMMC]
fss0=atmosphere/package3
kip1patch=nosigchk
atmosphere=1
emummc_force_disable=1
icon=bootloader/res/sys_cfw_boot.bmp

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

 

[Shubkin]

After installing 21.0.0 fw some games wouldn't start anymore. They show error:
"could not start the software.
Please try again from the HOME Menu."
/
Looks like all these games have fake signature, maybe that's the reason?
Tried to install sigpatches and sys-patch 1.5.8 v5, nothing changes. Tried to reinstall games after sigpatches and sys-patch and it also doesn't help. I just don't know what else to do.

 

[impeeza]

After installing 21.0.0 fw some games wouldn't start. They show error:
"could not start the software.
Please try again from the HOME Menu."
/
Tried to install sigpatches and sys-patch 1.5.8 v5, nothing changes. Tried to reinstall games after sigpatches and sys-patch and it also doesn't help. I just don't know what else to do.

READ THE OP!!!

INSTALL UPDATED SIGPATCHES, SYS-PATCH SYSMODULE.

AND REINSTALL YOUR GAMES USING AWOOINSTALLER.

 

[Flame]

@Earthshine clam down. Come back in the new year. Happy man.

 

[garbagehuman123]

are we actually winning?

 

[bombayjack]

READ THE OP!!!

INSTALL UPDATED SIGPATCHES, SYS-PATCH SYSMODULE.

AND REINSTALL YOUR GAMES USING AWOOINSTALLER.

You don't need to reinstall the games, Here's a tip for you.

1: Update sys-patch - test a homebrew forwarder/create one to make sure it works (then you know the patches are correct)

2: In the broken game, use dbi installer open "installed games" - select the broken game, Select Application and press the + button, select "generating dlc unlocker" then "generate and install", press B to go back then select the fake dlc you just installed, press + and then delete.

3: Broken game should now be working again as you just fixed the application flag.

4: Test Broken game, and it will now not be broken anymore.


Maybe someone can make a homebrew specifically to do this, as all you need to do is list the games, make a fake install , then remove it again. It doesn't seem like a hard homebrew to make.

 

[haipm92]

All of my game stuck here after I copied the sigpatches -_- how to fix it without restoring my SD Card pls?

 

[branchus]

All of my game stuck here after I copied the sigpatches -_- how to fix it without restoring my SD Card pls?
View attachment 544120

I upgraded the fw to 21.1.0 and Atmosphère to 1.10.1, I don't have sigpathes installed but have sys-patch 1.58 v5 installed, had the same issue. any solutions?

 

[bth]

@haipm92 @branchus
both of you booted (at least once) without patches loaded, ES didnt change in 21.1.0, so it's unlikely 21.1.0 is what did it, it's you booting "stock" or similar.

neither .ips sigpatches or sys-patch changed for FS or ES in 21.1.0

the fix:
re-install all affected titles.

 

[branchus]

@haipm92 @branchus
both of you booted (at least once) without patches loaded, ES didnt change in 21.1.0, so it's unlikely 21.1.0 is what did it, it's you booting "stock" or similar.

neither .ips sigpatches or sys-patch changed for FS or ES in 21.1.0

the fix:
re-install all affected titles.

deleted the title and reinstalled the title.

restarted the console

first title start is fine, exit to home screen, close the title. then cannot restart the title, same issue.

restart console, first time is fine, then fail on the second....

Actually, I don't need to reinstall the titles. After console reboot, I can start any title, but only for that first time. all the subsequent title start will fail.

 

[AllOver]

deleted the title and reinstalled the title.

restarted the console

first title start is fine, exit to home screen, close the title. then cannot restart the title, same issue.

restart console, first time is fine, then fail on the second....

Actually, I don't need to reinstall the titles. After console reboot, I can start any title, but only for that first time. all the subsequent title start will fail.

What other sysmods do you have installed? Do you have saltynx?

 

[branchus]

What other sysmods do you have installed? Do you have saltynx?

sys-patch 1.58v5 is the only sysmods I installed, I haven't installed any overlay.

discovered more details, as long as I disable WIfi, all title can start without any issue, but once wifi is connected. I will have the above issue.

 

[bth]

sys-patch 1.58v5 is the only sysmods I installed, I haven't installed any overlay.

discovered more details, as long as I disable WIfi, all title can start without any issue, but once wifi is connected. I will have the above issue.

then it's fake account linked issue

edit/add to: /atmosphere/config/system_settings.ini

[olsc]
default_auto_upload_global_setting = u8!0x0

 

[branchus]

then it's fake account linked issue

edit/add to: /atmosphere/config/system_settings.ini

[olsc]
default_auto_upload_global_setting = u8!0x0

added this setting and restarted my console, and seems all good now, Thank you very much

out of curiosity, what is this setting do? and why I don't have this issue when at fw 20.0.5

 

[bth]

added this setting and restarted my console, and seems all good now, Thank you very much

out of curiosity, what is this setting do? and why I don't have this issue when at fw 20.0.5

https://www.nintendo.com/en-gb/Supp...-Save-Data-Backups-and-Downloads-1434310.html

since you have a fake account linked with improper account data (linkalho is wrong), it's attempting to upload your save games.

this setting is enabled by default for NSO members, but since you have an improper fake account linked, it doesn't know you don't have NSO / doesn't have this setting enabled

1. From the HOME Menu, select "System Settings" > "Data Management" > "Save Data Cloud".
2. Select the desired user, then select "Settings".
3. Select "Automatically Back Up Save Data" to enable this feature. Tap this option again to turn the feature off.