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

[Juice4z0]

I updated my Atmosphere and hekate. I can boot to 20.0.1 with no issues. However I am having issues launching my Apps from the home screen. I know typically this had to do with sigpatches. I followed the instructions in this thread to install the sys-patch and I went through and removed the listed folders from my SD card. I also edited the hekate.ini to remove the sigcheck lines. After rebooting I still can't launch any apps from the home screen. I read some more troubleshooting steps and I went to check the sys-patch logs and .ini and they are not being generated. I did as suggested and manually created the sys-patch\config.ini and it is still not working. The only thing that devated during the folder removal process from the instructions was that I did not have a nim-prodinfo-blank-fix folder.

If anyone has any idea on my next steps of troubleshooting or possibly knows how to resolve my issue It would be much appreciated.

Thank you again in advance for the help

 

[Mars04]

Hi, do we have to replace "fss0" with "pkg3" in the hekate_ipl.ini file after Hekate's latest release?

Or am I misunderstanding the release notes?

Extract release notes:

"Config: Added pkg3 key support that replaces fss0 with the same exact functionality
fss0 will still work for compatibility reasons but it's now deprecated.
At some point fss0 will become obsolete, so make sure you update your configs to use pkg3 instead."


I did change it in my own config file and all seems to work, but just wondering since I don't see anyone else asking questions about this

 

[LuigiGad]

Ho aggiornato la mia atmosfera e l'ecate. Posso avviare la versione 20.0.1 senza problemi. Tuttavia, ho problemi ad avviare le mie app dalla schermata principale. So che in genere questo ha a che fare con le sigpatch. Ho seguito le istruzioni in questo thread per installare la sys-patch e ho esaminato e rimosso le cartelle elencate dalla mia scheda SD. Ho anche modificato il hekate.ini per rimuovere le righe di sigcheck. Dopo il riavvio, non riesco ancora ad avviare alcuna app dalla schermata principale. Ho letto alcuni passaggi per la risoluzione dei problemi e sono andato a controllare i registri delle patch di sistema e .ini e non vengono generati. Ho fatto come suggerito e ho creato manualmente la sys-patch\config.ini e ancora non funziona. L'unica cosa che ha dedotto durante il processo di rimozione della cartella dalle istruzioni è che non avevo una cartella nim-prodinfo-blank-fix.

Se qualcuno ha qualche idea sui miei prossimi passi per la risoluzione dei problemi o forse sa come risolvere il mio problema, sarebbe molto apprezzato.

Grazie ancora in anticipo per l'aiuto

use this homebrew (not in applet mode and with the prod.keys available in the switch folder) it creates them for you on the spot, really useful

 

[Juice4z0]

use this homebrew (not in applet mode and with the prod.keys available in the switch folder) it creates them for you on the spot, really useful

Thank you, I will try but Applet mode via the album button is the only way anything will launch. If i try launching an existing NSP forward like to FTPD classic or checkpoint I get the error "Unable to start software". I have also tried by holding down the right bumper.

I dumped my keys using lockpick again today to make sure they were in the correct place.

 

[josete2k]

Hi, do we have to replace "fss0" with "pkg3" in the hekate_ipl.ini file after Hekate's latest release?

Or am I misunderstanding the release notes?

Extract release notes:

"Config: Added pkg3 key support that replaces fss0 with the same exact functionality
fss0 will still work for compatibility reasons but it's now deprecated.
At some point fss0 will become obsolete, so make sure you update your configs to use pkg3 instead."


I did change it in my own config file and all seems to work, but just wondering since I don't see anyone else asking questions about this

Yes, fss0 will be replaced in a future release.

 

[LuigiGad]

Thank you, I will try but Applet mode via the album button is the only way anything will launch. If i try launching an existing NSP forward like to FTPD classic or checkpoint I get the error "Unable to start software". I have also tried by holding down the right bumper.

I dumped my keys using lockpick again today to make sure they were in the correct place.

that homebrew is designed for full RAM mode. start a game while holding R and install the first forwarder directly for hbmenu to solve the problem. if you don't have any game installed, use tinwoo in applet mode and install a backup game of yours (maybe a small one so you shorten the time)

 

[Juice4z0]

that homebrew is designed for full RAM mode. start a game while holding R and install the first forwarder directly for hbmenu to solve the problem. if you don't have any game installed, use tinwoo in applet mode and install a backup game of yours (maybe a small one so you shorten the time)

I was able to get into non applet mode by using a physical game cart. I tried it and had no luck. If i save it as an NSP gold leaf gives error "RomNcaHeaderSignature1VerificationFailed". Trying to install directly from the app. throws errors also. "fsOpenFileSystemWithID"

I feel like this has to do with trying to switch to sys-patches as it isn't generating a log and the behavor i see when trying to launch an app is like what happened the past few FW upgrades. The fix used to be getting sigpatches but from what I read it was better to move to sys-patch.

I'm kinda lost at this point. I didn't intend on upgrading my CFW to 20.0.1 but it auto updated.

Thanks again for the help.

 

[Mars04]

Yes, fss0 will be replaced in a future release.

Thanks, then I leave my hekate_ipl.ini file with the new pkg3 changes implemented, since it has to be like that then anyway soon.

 

[LuigiGad]

Sono stato in grado di entrare in modalità non applet utilizzando un carrello di gioco fisico. L'ho provato e non ho avuto fortuna. Se lo salvo come foglia d'oro NSP dà l'errore "RomNcaHeaderSignature1VerificationFailed". Anche il tentativo di installare direttamente dall'app genera errori. "fsOpenFileSystemWithID"

Sento che questo ha a che fare con il tentativo di passare alle patch di sistema in quanto non sta generando un registro e il comportamento che vedo quando provo ad avviare un'app è come quello che è successo negli ultimi aggiornamenti FW. La soluzione era ottenere sigpatch, ma da quello che ho letto era meglio passare a sys-patch.

A questo punto sono un po' perso. Non avevo intenzione di aggiornare il mio CFW alla versione 20.0.1, ma si è aggiornato automaticamente.

Grazie ancora per l'aiuto.

I was able to get into non applet mode by using a physical game cart. I tried it and had no luck. If i save it as an NSP gold leaf gives error "RomNcaHeaderSignature1VerificationFailed". Trying to install directly from the app. throws errors also. "fsOpenFileSystemWithID"

I feel like this has to do with trying to switch to sys-patches as it isn't generating a log and the behavor i see when trying to launch an app is like what happened the past few FW upgrades. The fix used to be getting sigpatches but from what I read it was better to move to sys-patch.

I'm kinda lost at this point. I didn't intend on upgrading my CFW to 20.0.1 but it auto updated.

Thanks again for the help.

You definitely have an incorrect setup, I have stock 20.0.1 from which I created emummc. I only have hekate 6.3, atmo 1.9, and sys-patch 1.5.6 and everything works.

 

[frimp]

I updated my Atmosphere and hekate. I can boot to 20.0.1 with no issues. However I am having issues launching my Apps from the home screen. I know typically this had to do with sigpatches. I followed the instructions in this thread to install the sys-patch and I went through and removed the listed folders from my SD card. I also edited the hekate.ini to remove the sigcheck lines. After rebooting I still can't launch any apps from the home screen. I read some more troubleshooting steps and I went to check the sys-patch logs and .ini and they are not being generated. I did as suggested and manually created the sys-patch\config.ini and it is still not working. The only thing that devated during the folder removal process from the instructions was that I did not have a nim-prodinfo-blank-fix folder.

If anyone has any idea on my next steps of troubleshooting or possibly knows how to resolve my issue It would be much appreciated.

Thank you again in advance for the help

I'm having a similar issue after following all the same steps. Sys-patch seems to be working when I check the tesla overlay. When launching any application though, besides Zelda BOTW, it says "Unable to start software."

 

[QuartZander]

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.

I tried all this but i now get a black screen when booting into atmosphere. is it caused by sys patch or something else?

 

[Ormis10]

Will sigpatches be released? Or is there an idiots guide on how to transition from using sigpatches to syspatch?

 

[Blythe93]

I tried all this but i now get a black screen when booting into atmosphere. is it caused by sys patch or something else?

It could be something else but I'm not sure what. The usual suspect are the outdated sys-modules.
When I updated my Switch to 20.0.1 the first time it just rebooted back to payload. but it worked the second time.

Or is there an idiots guide on how to transition from using sigpatches to syspatch?

Here it is.

 

[impeeza]

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.

Wow mate, very well done. Also you need to remove NOGC from Hekate_ipl.ini

 

[Konzolista]

New IPS_Patch_Creator_1.6.1
You can find the link in any older version in HELP- Online information
I had the latest v. 1.5.9...

MrDude, Thank you...!

 

[Yasuke7]

@impeeza
Thank you for your work on sys-patch module. I had a question, I just transferred over to using sys-patch module from sigpatches and have noticed by default there is a setting in the overlay options called "Patch sysMMC" turned on. I run all my backups under emuMMC, is there any reason that this setting should be kept on for me? I'm wondering if it is fine to turn it off and just keep "Patch emuMMC" on instead.

 

[impeeza]

New set of sigpatches created!!!!


full supporting Atmosphère 1.09.0 and Firwmare 20.0.0

FOR FW 21 AND ATM 1.9.1 SEE THE OP PLEASE

 

[VenCraft]

Hi! After updating all the packages and using sys-patch, Tinfoil gets stuck at loading sdmc:/switch/tinfoil/db/titles.US.en.json. Is anyone else experiencing this? Cheers!

Post automatically merged: May 10, 2025

New set of sigpatches created!!!!


full supporting Atmosphère 1.09.0 and Firwmare 20.0.0

I'm getting lost here—so what should we use, sigpatches or sys-patch? If we use sigpatches, I assume we shouldn't remove the NOGC option from Hekate_ipl.ini...

 

[sudeki300]

Hi! After updating all the packages and using sys-patch, Tinfoil gets stuck at loading sdmc:/switch/tinfoil/db/titles.US.en.json. Is anyone else experiencing this? Cheers!

Post automatically merged: May 10, 2025

I'm getting lost here—so what should we use, sigpatches or sys-patch? If we use sigpatches, I assume we shouldn't remove the NOGC option from Hekate_ipl.ini...

use which one you want, sigpatches or sys-patch.

 

[VenCraft]

I'm having issues with Tinfoil both with sys-patch and sigpatches, anyone else? Thanks.