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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,180,106
  • Replies Replies 7,279
  • Likes Likes 266
may be your card is fake, on Hekate Issues you can read @CTCaer states long cards are supported now.

if you can test your card and you are completely sure you card is not fake (I am almost sure it is) you can contact to @CTCaer on github issues or discord and ask for help.


Backup all files on your SD card on your pc, format it to fat 32 using fat32 format (https://gbatemp.net/download/gui-format.33869/) then test your sd card using H2Testw (https://www.heise.de/download/product/h2testw-50539) or from Downloads section https://gbatemp.net/download/h2testw.39119/ (THAT WILL TAKE A LONG TIME)
@impeeza you are awesome it turned out i used the wrong cluster size i chose 64kb instead of 32kb i reformatted and put just the bootloader stuff for hekate and it booted and detected the full size of the card so now i just need to copy back all the other files which sucks because i had mini partition wizard spend a whole 24 hours on it all that time wasted because of incorrect cluster size oh well lesson learned and thank you again i cant count how many times you have helped me and i am very grateful have a good one
 
  • Like
Reactions: Skv0ra and impeeza
@impeeza you are awesome it turned out i used the wrong cluster size i chose 64kb instead of 32kb i reformatted and put just the bootloader stuff for hekate and it booted and detected the full size of the card so now i just need to copy back all the other files which sucks because i had mini partition wizard spend a whole 24 hours on it all that time wasted because of incorrect cluster size oh well lesson learned and thank you again i cant count how many times you have helped me and i am very grateful have a good one
Also you can format the card on Hekate, Hekate is full SD compliant, and put the correct spaces, partitions and spare space for correct working of the card.
 
  • Like
Reactions: Skv0ra and Blythe93
Hi, I'm really confused, I don't know which of the following is correct:

I download and use the shared sigpatches, and then I don't need to create them myself. Or the opposite, I create them myself and then I don't need to download the shared ones.

I need to download and use the shared ones and also create some myself.

Either of those two scenarios with or without sys-patch.

Either of those two scenarios with or without editing the hekate ini file.

In summary, I don't understand if what's in the OP are different alternatives for the same thing, or if they are steps of the same thing.

Any guidance will be appreciated.
 
I download and use the shared sigpatches, and then I don't need to create them myself.
That is correct.

I need to download and use the shared ones and also create some myself.
NO

Either of those two scenarios with or without sys-patch.
If you do not have the reading skills or you are so nooby ONLY USE SYS-PATCH and remove all sigpatches.

Either of those two scenarios with or without editing the hekate ini file.
Hekate ini file is for check how the console autostarts and if you like to apply patches of No Game Cartdrige, for that you need patches.ini file.

In summary, I don't understand if what's in the OP are different alternatives for the same thing, or if they are steps of the same thing.

Any guidance will be appreciated.
Just install SYS-Patch sysmodule, by extracting the zip file to the root of your SD Card. https://gbatemp.net/download/sys-patch-sysmodule.39124/
 
  • Like
Reactions: Blythe93
Remove pretty much everything that's usually included in sigpatches archive file i.e.:
  • folders es_patches, nfim_ctest and nim-prodinfo-blank-fix from the atmosphere/exefs_patches folder.
  • folders fs_patches and loader_patches from the atmosphere/kip_patches folder.
  • patches.ini file from the bootloader folder.
That should be it. Don't forget to reboot afterwards after you install the latest sys-patch (simply drag and drop).

In any case, I've just updated my CFW (firmware, Atmosphere, Hekate, sys-patch, MissionControl and a couple of other apps) and from what I can tell everything still works just fine. The only issue I run into was that my Switch rebooted on first boot right after the Switch logo. The second time it booted properly.
my computer gets an "unidentified error" preventing me from deleting these folders, the sd card is in my machine and i run windows 10
 
Can you help a novice a bit with sigpatches.
I have v1 with fw 20.1 and have installed latest sigpatches (from the 1st post) but still most of the nro's says patches missing. Should i downgrade firmware with daybreak (to which?) and syspatch?
What is currently best option to have sigpatches?
 
Can you help a novice a bit with sigpatches.
I have v1 with fw 20.1 and have installed latest sigpatches (from the 1st post) but still most of the nro's says patches missing. Should i downgrade firmware with daybreak (to which?) and syspatch?
What is currently best option to have sigpatches?
Install SYS-Patch Sysmodule and remove sigpatches.
 
*** 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.
 

Attachments

Last edited by impeeza,
@impeeza say, installed Patapon the other night, and it pointed to needing the eshop DL which I've never seen before. Think it's because of FW restrictions, or something else funky going on? Latest atmo, your sys-patch thing, and fw 20.1.0 since that's the newest atmo supports.
It is working for me

Tested with and without update

IMG_20250715_012549.jpgIMG_20250715_012514.jpg
 
Sigpatches updated for 20.2.0 only NIM patch is added, the rest are the same for 20.x.x

SYS-Patch should work fine with this FW.
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.
IMG_20250715_110935.jpg

Post automatically merged:

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.
IMG_20250715_110935.jpg
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
 
Last edited by Mars04,

Site & Scene News

Popular threads in this forum