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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,191,498
  • Replies Replies 7,280
  • Likes Likes 266
I've ended up making some adjustments to my scripts, and now have added the means to generate regular "sigpatches".




usage instructions:

git clone https://github.com/borntohonk/Switch-Ghidra-Guides.git sgg
cd sgg

requirements: python3 with the following pip modules lz4, pycryptodome)
( python -m pip install lz4 pycryptodome )

(optional unless making NEW patches - put new firmware .ncas in folder "firmware" (ex: firmware/*.nca and firmware /*.cnmt.nca))
python scripts/process_firmware.py

(optional unless making NEW patches, should be run - as it fetches the latest version of atmosphere and makes the loader and erpt patch)
(it also checks if patches are valid for new firmware files if processed with previous command)
python scripts/find_patterns.py --ams

(makes hekate patches.ini, and exefs_patches, then makes a .zip archive such as "Hekate+AMS-package3-sigpatches-1.10.1-cfw-21.1.0.zip")
python scripts/make_patches.py

exefs_patches included:
nfim_ctest (force network enable)
nim_ctest (includes both crashfix from 17+ for blanking prodinfo, and blocking automated firmware updates)
olsc_patches (spinning icon fix)
es_patches (es-certificate patch, the one letting you install things)
erpt_patches (for atmosphere's ERPT module, makes logging not happen - currently only latest atmosphere included)

kip_patches included:
fs down to 1.0.0 to latest (21.1.0)
loader only latest atmosphere (1.10.1)

hekate patches.ini included:
.nosigchk and loader (only atmosphere versions down to 1.9.3 - not worth time investment adding the rest)
(fs down to 1.0.0, up to latest of 21.1.0)


it automatically bundles these as:

"Hekate+AMS-package3-sigpatches-1.10.1-cfw-21.1.0.zip"
or
"Hekate+AMS-package3-sigpatches-1.10.1p-cfw-21.1.0.zip"
with the "p" signaling atmosphere pre-release, and atmosphere versions it supports, and the final value is the highest firmware version of patches included




edit: i have updated it to also generate kip_patches, after being asked to:
.zip uploaded has been updated to include them, and the scripts will generate them from now on.

edit2:
the .zip was reuploaded yet another time, because the hashes for old patches in patches.ini were wrong. (my source was the release from this https://gbatemp.net/threads/sigpatc...-fusee-package3.571543/page-275#post-10692213 which has the wrong hashes for all exfat before 10.0.0, potentially after as well. I only generate brand new from 10.0.0+ myself, so i haven't checked if the exfat hashes for 10.0.0 to 21.1.0 are incorrect in that release.
(i now generate from 1.0.0 to 21.1.0 for FS, even for noacidsigchk which in 10.0.0 moved to loader)

(my .zip archive does not have the incorrect hashes for FS.)
 

Attachments

Last edited by bth,
*** Updated 2025 - 08 - 12 ***

Sigpatches updated for 21.1.0,

And Upgraded to Atmosphère 1.10.1

SYS-Patch should work fine with this FW too.
Does this also work with 21.0.0? i downloaded the files you shared but now some games don't launch and some do, like it gives a message saying "Could not start the software. Please try again from the HOME menu."​
 
Does this also work with 21.0.0? i downloaded the files you shared but now some games don't launch and some do, like it gives a message saying "Could not start the software. Please try again from the HOME menu."​
what i posted works to 21.1.0 as indicated by the filename "Hekate+AMS-package3-sigpatches-1.10.1-cfw-21.1.0.zip"
 
  • Haha
Reactions: evil24
has homebrew been updated to for the latest version? been wanting to update switch so could play some games online but been worried it would break things set up on cfw
 
  • Haha
Reactions: Earthshine
Actually, files keep disappearing from the EmuMMC Nintendo folder after copying, so I'm thinking the culprit is a bad MicroSD card...
Just replaced the MicroSD card, and now I have a new problem: While my game updates now show up properly, I have lost the ability to launch games from the game card slot. Games purchased from the E-Shop boot, but physical games fail to boot with error 2002-1002.
 
Just replaced the MicroSD card, and now I have a new problem: While my game updates now show up properly, I have lost the ability to launch games from the game card slot. Games purchased from the E-Shop boot, but physical games fail to boot with error 2002-1002.
review if your SDMC:/bootloader/hekate_ipl.ini file have the line

autonogc=1

OR the file

SDMC:/atmosphere/config/stratosphere.ini

have the line:

nogc = 1


and then remove them. those lines disable the Cartridge.
 
review if your SDMC:/bootloader/hekate_ipl.ini file have the line

autonogc=1

OR the file

SDMC:/atmosphere/config/stratosphere.ini

have the line:

nogc = 1


and then remove them. those lines disable the Cartridge.
Didn't work; error 2002-1002 persists even after removing the relevant lines from both files.
 
Didn't work; error 2002-1002 persists even after removing the relevant lines from both files.
what (1) firmware version, (2) atmosphere version and (3) homebrew are you using to install things with?
what (4) set of patches are you using, if any, (5) version of sys-patch, if any?
what (6) games are failing with that error, specifically


if you have downgraded firmware, or your emummc is lower firmware than the highest firmware revision your sysnand has had, then your cartridge slot wont work until you upgrade your emummc/sysnand again

that's an anti-downgrade mechanism of lotus: https://switchbrew.org/wiki/Lotus3
 
Last edited by bth,
what (1) firmware version, (2) atmosphere version and (3) homebrew are you using to install things with?
what (4) set of patches are you using, if any, (5) version of sys-patch, if any?
what (6) games are failing with that error, specifically


if you have downgraded firmware, or your emummc is lower firmware than the highest firmware revision your sysnand has had, then your cartridge slot wont work until you upgrade your emummc/sysnand again

that's an anti-downgrade mechanism of lotus: https://switchbrew.org/wiki/Lotus3

1) 21.1.0 on both SysMMC and EmuMMC
2) 1.10.0
3) Nothing on my Switch is installed; all games are either carts or E-Shop purchases.
4) Combination of the sigpatches from this post and sys-patch
5) 1.5.9
6) All cartridge games; E-Shop games boot without errors.

I have never downgraded my firmware.
 
  • Like
Reactions: impeeza
review if your SDMC:/bootloader/hekate_ipl.ini file have the line

autonogc=1

OR the file

SDMC:/atmosphere/config/stratosphere.ini

have the line:

nogc = 1


and then remove them. those lines disable the Cartridge.
Didn't work; error 2002-1002 persists even after removing the relevant lines from both files.
As far as I can tell, removing those lines would do nothing in this case, because Hekate and Atmosphere will then use the default values for those, and they are the same. Instead, try keeping the lines in the files, in the same place as they were originally, uncommented (no leading ;s), but change their value to 0.
 
  • Like
Reactions: impeeza
As far as I can tell, removing those lines would do nothing in this case, because Hekate and Atmosphere will then use the default values for those, and they are the same. Instead, try keeping the lines in the files, in the same place as they were originally, uncommented (no leading ;s), but change their value to 0.
Added nogc = 0 to stratosphere.ini, already had autonogc=0 in hekate_ipl.ini; game cards still refuse to boot.
 
Added nogc = 0 to stratosphere.ini, already had autonogc=0 in hekate_ipl.ini; game cards still refuse to boot.
OK. Just in case, you restarted the console after editing the files, right?

If these are legit eShop downloads and game cards, maybe patches aren't the issue?

Searching for error 2002-1002, many results refer to checking the SD card, or data corruption. Do the game cards fail to boot in OFW too? With the SD card removed?

If the SD card itself is fine and legit, I'm not sure what else to try, other than backing up saves, creating a new emuNAND, and setting up Atmosphère from scratch.
 
OK. Just in case, you restarted the console after editing the files, right?

If these are legit eShop downloads and game cards, maybe patches aren't the issue?

Searching for error 2002-1002, many results refer to checking the SD card, or data corruption. Do the game cards fail to boot in OFW too? With the SD card removed?

If the SD card itself is fine and legit, I'm not sure what else to try, other than backing up saves, creating a new emuNAND, and setting up Atmosphère from scratch.
I have rebooted the console, and game cards boot fine in Stock SysMMC. Plus the SD card is brand new and was purchased at a Best Buy store, not online.
 
Hello everyone,

I have been searching for my own answer; however, I have not been able to find a clear approach.

Current set up: I am currently running Atmosphere 1.5.5. with Switch Firmware 16.1.

I have been having issues installing some games via Awoo Installer because of out-dated sigpatches. Can I update the current sigpatches using the most current versions while not touching Atmosphere or the Switch Firmware? Should I just update everything? Is there a localized place I can go with clear instructions on how to do any of this? I'm not having any other issues other than not being able to install some games.

Thank you all for the help. Much appreciated.
 
Hello everyone,

I have been searching for my own answer; however, I have not been able to find a clear approach.

Current set up: I am currently running Atmosphere 1.5.5. with Switch Firmware 16.1.

I have been having issues installing some games via Awoo Installer because of out-dated sigpatches. Can I update the current sigpatches using the most current versions while not touching Atmosphere or the Switch Firmware? Should I just update everything? Is there a localized place I can go with clear instructions on how to do any of this? I'm not having any other issues other than not being able to install some games.

Thank you all for the help. Much appreciated.
If you don't use tinfoil, and don't have any homebrew applications (no, not homebrew accessible from hbmenu, by homebrew applications i mean exactly homebrew applications)

then you can update to atmosphere 1.10.0, and firmware version of 21.1.0, with sys-patch 1.5.9

if you do care about homebrew applications. such as tinfoil.

atmosphere 1.9.5, max firmware version 20.5.0 and sys-patch 1.5.6


either way even if you do stay on 16.1, update to atmosphere 1.9.5 and sys-patch 1.5.6
theres no reason for you not to update to atmosphere 1.9.5

also, its not your patches that are out of date, if ES was out of date, none of your other installed games (that you hadn't paid for), wouldn't be working.

it's purely a master key problem, so you have to update your firmware.


(the "sigpatches" (not to be confused with sys-patch) in this thread are retroactive down to 1.0.0 anyway, up to 21.1.0, so those ones doesn't matter, as long as you boot correctly, if you only use awoo and zero homebrew applications and everything signature intact, then the ES patch loaded (the only ony you need to install things) is present anyway, no matter your firmware version, up to 21.1.0, and the ES patch will load no matter how you boot into atmosphere, hekate or fusee, doesnt matter.)
 
Last edited by bth,
I have rebooted the console, and game cards boot fine in Stock SysMMC. Plus the SD card is brand new and was purchased at a Best Buy store, not online.
Final update; I reformatted the microSD card, reinstalled atmosphere and sigpatches, and everything (including game cards) works again. It must have been something weird with my old atmosphere configs...
 
I'm on FW 19.0.1 | AMS 1.8.0 and I can't install Metroid Prime 4 Beyond no matter what I try. The minimum requirement for the game is 19.0 but every installer I use (AWOO, DBI (458 or the latest) Goldleaf, Tinleaf, Tinfoil, NS USBloader, etc) aborts due to "Old Firmware". I need a workaround. I refuse to upgrade my firmware to 20.0 or above because those lose about 25MB of Applet RAM needed to run many of my mods. MP4 is the last game I plan on installing on my Switch. I'm about to give up hope. :unsure:
 
I'm on FW 19.0.1 | AMS 1.8.0 and I can't install Metroid Prime 4 Beyond no matter what I try. The minimum requirement for the game is 19.0 but every installer I use (AWOO, DBI (458 or the latest) Goldleaf, Tinleaf, Tinfoil, NS USBloader, etc) aborts due to "Old Firmware". I need a workaround. I refuse to upgrade my firmware to 20.0 or above because those lose about 25MB of Applet RAM needed to run many of my mods. MP4 is the last game I plan on installing on my Switch. I'm about to give up hope. :unsure:
It works on FW 19, if you patch the game & update first using SAK (Swiss Army Knife) "Patch to lower firmware"
https://github.com/dezem/SAK/releases
Make sure you place FW 21 keys in SAK folder first. (Google to find them)
I used Awoo after patching to install, btw.
 
Last edited by BigOnYa,

Site & Scene News

Popular threads in this forum