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

[urherenow]

Not sure what package3 and FSS0 are (still got some stuff to learn regarding the terminology), but my Switch first starts Hekate and then loads Atmosphere, so I'm pretty sure that's what I'm using. I got my sigpatches from this thread (latest greatest at the time of writing).
https://gbatemp.net/threads/sigpatc...-fusee-package3.571543/page-205#post-10517797

But good to know things are different depending on whether Hekate is used or not.

Please at least read the first page of the hekate repo. On Atmosphere, you actually need to look in the docs folder on github, to learn how all of the things are configured. You not knowing any of this, is why I despise AIO packs. They simply leave you ignorant.

Even loading hekate, you still have a choice to use fss0 or payload=fusee.bin. Using fusee as your payload, either directly or through hekate, will not work with sigpatches, if you got it from the repo. This is a function of /bootloader/hekate_ipl.ini.

 

[Nynrah]

Please at least read the first page of the hekate repo. On Atmosphere, you actually need to look in the docs folder on github, to learn how all of the things are configured. You not knowing any of this, is why I despise AIO packs. They simply leave you ignorant.

Even loading hekate, you still have a choice to use fss0 or payload=fusee.bin. Using fusee as your payload, either directly or through hekate, will not work with sigpatches, if you got it from the repo. This is a function of /bootloader/hekate_ipl.ini.

I had the disadvantage of someone else initially having set up my CFW, so the stuff I picked up is basically just enough to do what I need to do. Basically followed the (manual) steps outlined by a guide such as the one in this topic (after the one over at rentry.org got taken down) and that fortunately worked well enough to this day. As long as it worked, you don't tend to ask too many questions.

 

[Blythe93]

but my Switch first starts Hekate and then loads Atmosphere, so I'm pretty sure that's what I'm using.

Yep, that's the "loading Atmosphere's package3 via Hekate's FSS0" method where sigpatches still work properly.

I had the disadvantage of someone else initially having set up my CFW, so the stuff I picked up is basically just enough to do what I need to do. Basically followed the (manual) steps outlined by a guide such as the one in this topic (after the one over at rentry.org got taken down) and that fortunately worked well enough to this day. As long as it worked, you don't tend to ask too many questions.

The only thing you need to know is how to update your Switch and keep your CFW environment as clean as possible, unless you're the adventurous type that likes to have pretty much everything homebrew community has to offer for your Switch. I don't mess around with cheats, themes, overclocking, running emulators, installing forwarders, etc. I usually stay away from AIO installers and do most of the things manually. For what I've gathered, your less likely to run into an issue that you can't fix yourself. I'm pretty much only running the games the way they are supposed to be run, unless the game is so broken that requires unofficial patches/cheats to run properly.

If you run into an issue, most of us that stick around the forums might be able to help you out. ^^

 

[Nytrite]

Is there a problem if I use fusee.bin (renamed as payload.bin) as the one to boot into Atmosphere using an RCM Payloader? Or will there be problems? Since if I use the hekate.bin file as payload.bin, I can't use my game cartridges as it says it's corrupted. Right now I also can't properly download (via DBI MTP installer) Super Mario Party Jamboree and Nintendo Switch Sports as it keeps saying it's corrupted and that my microSD is corrupted (despite all my other games working, even other newly installed ones).

 

[duckbill007]

Just stop using DBI

 

[Nytrite]

Just stop using DBI

What would be a good alternative if I don't connect my Switch to the internet? I think tinfoil doesn't work anymore on my end too.

 

[RedColoredStars]

Just stop using DBI

Grow up and get some new material while you're at it. The entire "Just stop using DBI" shit you keep posting over and over and over and over and over is tired af. Zzzzzzzzzzzzzzzzzzzzz.

What would be a good alternative if I don't connect my Switch to the internet? I think tinfoil doesn't work anymore on my end too.

Don't listen to duckbill. He's just being his regular douche self. Either your card is actually corrupt or something is messed up with the files on your SD card. My suggestion is to format the card and start over. DBI not working, corruption messages, game cards not working, Tinfoil not working. You screwed something up bad along the way. Just start from scratch.

 

[Nytrite]

Grow up and get some new material while you're at it. The entire "Just stop using DBI" shit you keep posting over and over and over and over and over is tired af. Zzzzzzzzzzzzzzzzzzzzz.



Don't listen to duckbill. He's just being his regular douche self. Either your card is actually corrupt or something is messed up with the files on your SD card. My suggestion is to format the card and start over. DBI not working, corruption messages, game cards not working, Tinfoil not working. You screwed something up bad along the way. Just start from scratch.

Thank you! Must be during one weird update. Was able to fix the game cart not working but the two games I mentioned and some homebrew apps are not working. I'll try backing up my saves first. Is there anything else I should back up too?

 

[RedColoredStars]

Thank you! Must be during one weird update. Was able to fix the game cart not working but the two games I mentioned and some homebrew apps are not working. I'll try backing up my saves first. Is there anything else I should back up too?

Not that I can think of.

 

[Sergius22]

Hi, like many others, I had an error when updating my switch to version 19.01. At first it was an internet connection error and I fixed it. Then it wouldn't let me access the games. I placed the sightpatches correctly and now the games finally appear on the switch, but in the console's memory they appear at 0, as if they weren't taking up space, but on the SD card they are taking up space and I can't play them.
Does anyone know a solution?

 

[Yoshi_yogurt]

I have the latest sys- and sigpatches, but when checking Ultrahand Overlay, I can see that
"noncasigchk_new" and "nocntchk" are unpatched. What are these, and are they unpatched due to firmware or other reasons?

Firmware 18.1.0 and latest Atmosphere (1.8.0) and Hekate (v6.2.2).

 

[Blythe93]

Hi, like many others, I had an error when updating my switch to version 19.01. At first it was an internet connection error and I fixed it. Then it wouldn't let me access the games. I placed the sightpatches correctly and now the games finally appear on the switch, but in the console's memory they appear at 0, as if they weren't taking up space, but on the SD card they are taking up space and I can't play them.
Does anyone know a solution?

That's a bit weird situation you got yourself into. Not sure what you previously did in your CFW setup but, if you're using emuNAND, I'd check whether the Nintendo path in the emummc.ini is correct. Additionally, I'd switch to using sys-patch instead of sigpatches.

I have the latest sys- and sigpatches, but when checking Ultrahand Overlay, I can see that
"noncasigchk_new" and "nocntchk" are unpatched. What are these, and are they unpatched due to firmware or other reasons?

You don't need to have both, sys-patch should be enough.
Unpatched = the pattern wasn't found by sys-patch on the current system so there's no need to patch them (only present if you turn off the Version skip in the Options).
If unsure whether everything's working as it should, I'd suggest removing the sys-patch config and rebooting your Switch so that it can recreate a new default one which you can edit afterwards.

 

[Yoshi_yogurt]

Thanks for the info!

But it seems to work now when I removed 'kip1patch=nosigchk' from the hekate_ipl.ini file. Now, these are patched when launching 'cfw - emummc.'
Before, these were only patched when I booted via 'payload -> fusee.bin', and not via 'launch -> emummc'.

Post automatically merged: Jan 16, 2025

You don't need to have both, sys-patch should be enough.
Unpatched = the pattern wasn't found by sys-patch on the current system so there's no need to patch them (only present if you turn off the Version skip in the Options).
If unsure whether everything's working as it should, I'd suggest removing the sys-patch config and rebooting your Switch so that it can recreate a new default one which you can edit afterwards.

If I remove the sig-patches, will 'fss0=atmosphere/package3' still be launched, or will it be 'fusee.bin'?

 

[Sergius22]

That's a bit weird situation you got yourself into. Not sure what you previously did in your CFW setup but, if you're using emuNAND, I'd check whether the Nintendo path in the emummc.ini is correct. Additionally, I'd switch to using sys-patch instead of sigpatches.


You don't need to have both, sys-patch should be enough.
Unpatched = the pattern wasn't found by sys-patch on the current system so there's no need to patch them (only present if you turn off the Version skip in the Options).
If unsure whether everything's working as it should, I'd suggest removing the sys-patch config and rebooting your Switch so that it can recreate a new default one which you can edit afterwards.

How do I check this? The Nintendo folder weighs 170 GB out of 256 and it is super strange that it does not detect it. I have the Nintendo folder in the root of the SD.

 

[Blythe93]

How do I check this? The Nintendo folder weighs 170 GB out of 256 and it is super strange that it does not detect it. I have the Nintendo folder in the root of the SD.

Are you using emuNAND at all? I have two Nintendo folders. The one on the root of the SD card is used by the stock sysNAND, and the one located in the emuMMC folder is being used by emuNAND CFW. I'm not sure if there's sysmmc.ini or similar config file for sysMMC CFW setup, but in my emummc.ini file for my emuNAND CFW setup I have the following lines:

[emummc]
enabled=1
sector=0x2
path=emuMMC/ER00
id=0x0000
nintendo_path=emuMMC/ER00/Nintendo

nintendo_path is what you have to adjust/fix accordingly so that your games in the Nintendo folder appear in your emuNAND. Again, that's the case if you're using emuNAND at all.

 

[Kluezee]

Hello, i have a strange problem. I am using the modified fusee.bin i found in this thread, installed the newest sigpatches and am on the newest atmosphere (my switch is at 19.0.1) - i also modified the hekate_ipl.ini and removed 'kip1patch=nosigchk' from the file. everything works fine, except one thing. i tryed two sources but i always get the "the software was closed because an error occured black screen after selecting it from the start menu. Any idea what i can try?

 

[Rizsparky]

Its been a long time since I posted here last! Long story short, I have a Switch on 16.0.3 both (emuNAND and Stock) do I need to upgrade my firmware and install sigpatches for newer games to boot? I'm only having issues with one particular game at the moment.

 

[KiiWii]

Thank you to this thread and the contributors.

After reading I finally updated from 18.0.1 to 19.0.1 (and AMS 1.8.0) and it’s all working perfectly so far with syspatch 1.5.5, latest patches, and fusee.bin.

 

[Blythe93]

Hello, i have a strange problem. I am using the modified fusee.bin i found in this thread, installed the newest sigpatches and am on the newest atmosphere (my switch is at 19.0.1) - i also modified the hekate_ipl.ini and removed 'kip1patch=nosigchk' from the file. everything works fine, except one thing. i tryed two sources but i always get the "the software was closed because an error occured black screen after selecting it from the start menu. Any idea what i can try?

I'd suggest getting the latest sys-patch v1.5.6 (v1.5.5 provided by impeeza is fine as well, just make sure to remove any previous config file for the sys-patch as it may have redundant entries). If you're using sigpatches only, I believe that you do need the kip1patch=nosigchk line in your hekate_ipl.ini. Regardless, I've been using sys-patch v1.5.6 without any issues so far.

Its been a long time since I posted here last! Long story short, I have a Switch on 16.0.3 both (emuNAND and Stock) do I need to upgrade my firmware and install sigpatches for newer games to boot? I'm only having issues with one particular game at the moment.

You can follow this guide to update your setup. I'd suggest getting the latest sys-patch instead of sigpatches from now on, mainly because I've seen people having less issues with the sys-patch, sys-patch having less files to maintain than sigpatches and some extra features.

After reading I finally updated from 18.0.1 to 19.0.1 (and AMS 1.8.0) and it’s all working perfectly so far with syspatch 1.5.5, latest patches, and fusee.bin.

sys-patch v1.5.6 is currently the latest one, but it should be the same as the 1.5.5 with one exception which is the config clean-up on the first run, I believe. You don't need the sigpatches at all, you can safely remove them (just make sure to remove kip1patch=nosigchk line in your hekate_ipl.ini and you'll be good.

 

[FanNintendo]

Thank you to this thread and the contributors.

After reading I finally updated from 18.0.1 to 19.0.1 (and AMS 1.8.0) and it’s all working perfectly so far with syspatch 1.5.5, latest patches, and fusee.bin.

How do you update to 19.0.1?

Post automatically merged: Jan 19, 2025

I'd suggest getting the latest sys-patch v1.5.6 (v1.5.5 provided by impeeza is fine as well, just make sure to remove any previous config file for the sys-patch as it may have redundant entries). If you're using sigpatches only, I believe that you do need the kip1patch=nosigchk line in your hekate_ipl.ini. Regardless, I've been using sys-patch v1.5.6 without any issues so far.


You can follow this guide to update your setup. I'd suggest getting the latest sys-patch instead of sigpatches from now on, mainly because I've seen people having less issues with the sys-patch, sys-patch having less files to maintain than sigpatches and some extra features.


sys-patch v1.5.6 is currently the latest one, but it should be the same as the 1.5.5 with one exception which is the config clean-up on the first run, I believe. You don't need the sigpatches at all, you can safely remove them (just make sure to remove kip1patch=nosigchk line in your hekate_ipl.ini and you'll be good.

is Lockpick still working with latest 19.0.1? and How do I update to 19.0.1?