RELEASE Sigpatches for Atmosphere (Hekate/fss0/fusee-secondary only!)

I forgot to mention the issue where one set of patches are updated earlier than another. That doesn't seem to be the case nowadays as they seem to be updating simultaneously but in the past, this was a big sticking point as fusee patches tended to be updated earlier than Hekate patches. There are also situations where Hekate or fusee/Atmosphere get updated before the other one leading some people to think there is an issue with the patches rather than the bootloader.

What I'm trying to say is that it is impossible to make something idiot-proof but what you can do is educate as many people as possible so that in turn they can educate and help others when problems arise. In the entire history of patches, there has never been a thread or package with both sets included. Personally I would like to keep it that way to prevent as much confusion as possible. I also would personally like everyone to move away from the term "sigpatches" but unfortunately we don't always get what we want.

 

I agree. Everything is working with AMS (chainload or through direct payload). The issue is only when booting via fss0= and more than one people are double-checking and reinstalling the new patches to no avail. The culprit most probably is the updated patches.ini (or even something with the v. 5.3.3 of hekate).

What I am curious, however, is about the games that some people are having problem with. Me and some friends cant play, for instance, SM3D NOR paper mario, but you - and some other people - are saying paper mario is working. Strange.

 

All of the new patches are working fss0 and fusee-primary installed om 3 different Switch units all is working no issues the patches are not the problem nor the bootloader hekate

 

I was having issues with launching any installed NSPs after applying the latest patch for AMS 0.14.4 on HOS 10.2.0 (from the OP). I added "kip1patch=nosigchk" to /bootloader/hekate_ipl.ini and everything worked again (I'm wondering why this line is removed from recent releases?). It looked like this, starting at line 17:

{--- Custom Firmware ---}
[CFW (SYSNAND)]
emummc_force_disable=1
fss0=atmosphere/fusee-secondary.bin
atmosphere=1
kip1patch=nosigchk
logopath=bootloader/bootlogo.bmp
icon=bootloader/res/icon_payload.bmp
{}

Before I added that line, only games I purchased and installed worked, new install did not work.

 

Now I see why only some users have issues and others do not. OP doesn't include a pre-configured hekate_ipl.ini file with the line "kip1patch=nosigchk" which is required to launch .XCI converts/homebrew .NSP files along with the patches.ini file (don't ask me, I just follow the rules). You might think the solution is to just give everyone the same pre-populated hekate_ipl.ini file with that line under the CFW configuration but everyone's hekate_ipl.ini file differs a little. Not all people have a CFW (SysNAND) option to avoid accidentally booting into SysNAND with CFW or some people may be using autoboot. This is certainly one doozy of a pickle...

 

Seems like latest FW & patches have corrupted some of my games & homebrew nsps. Also getting same error earlier with goldleaf.Also dumped latests keys with lockpick & same issue happens.

 

Now I see why so many folks had issues. I never "update" my hekate_ipl.ini file due to custom settings, so all I got was the latest patches.ini file, and everything worked flawlessly. Props to both you & Shadow for doing what you do guys.

 

Just wanna confirm the fix mentioned above worked. Goldleaf and custom nsps are now working for me.

 

Yeah I seem to have the same issue. After updating to Atmosphere 0.14.4 (FW 10.2.0) with the latest sigpatches, some games refuse to boot/install while some other boot fine.

 

Thanks to info from NoxiosNinja I finally found out how to make sigpatches.... :-)

Here's an alternative sigpatch for Atmosphere 14.4 (which does the same thing as the current patch - just patched differently)

Code:

#Loader Atmosphere-0.14.4
[Loader:20EFF0183DA09563]
.nosigchk=0:0x1BC4:0x4:00A05839,20008052
.nosigchk=0:0x6868:0x4:1000016b,1000006b

@Raikkonen96 - go to your Atmosphere content folder and remove stuff that shouldn't be there, some added things such as emuiibo etc will cause certain games to not load.

 

Just tested it and can confirm that every issue that I was having are now 100% solved - everything works like a charm either via fusee primary or hekate chainload.

Seems like you found the culprit.

Thank you!

 

Thanks for this info. Needed it. My system crashed while enabled lol

 

Does anyone know the fork of the custom hekate that this git mentions?

 

Ok I spoke too soon. What I’m looking at on my sdcard is 2 bootloader folders one with an _ and inside that one is a Hekate.ini which has all the writing and the other folder has the ini with very minimal writing. And I’m also unable to rename or delete the _bootloader folder on the pc
and now my forwarders don't work and can't install any, also tinfoil won't load.

 

This dam switch hacking is the worst. I’ve hacked every system there is and this is the only one that gives me a headache. If I fix one thing it just breaks something else. Unbelievable. Now I can’t get reboot to payload too work

 

Update: by adding "kip1patch=nosigchk" to bct.ini I was able to get everything working again, thanks for the fix (as Draxzelex said, almost everyone has a different bct.ini file so I placed it on a different line). Only works when launching directly with Fusee-Primary, though. When I boot the Switch using Hekate, it doesn't work.

 

yep took me hours to find this out too lol

 

you have to add that line to the hekate_ipl.ini inside bootloader folder. Can you show me your bct.ini file cuz mine looks nothing like my hekate_ipl.ini file.