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

gamemasteru03

Nintendo nerd
Member
Joined
Sep 18, 2016
Messages
1,219
Trophies
0
XP
2,378
Country
United States
what's the difference between "without mesosphere" and with?
With mesosphere means that it has a custom kernal made by Sciresm while without mesosphere means that it uses the defualt Nintendo kernal. For the end user, both versions feel pretty much the same. Eventually the non-mesosphere version will be removed.
 
  • Like
Reactions: BigOnYa

ShadowTS

Member
Newcomer
Joined
Aug 24, 2020
Messages
22
Trophies
0
Age
36
XP
96
Country
Italy
Hi all,

I have a major issue with these sigpatches, it is the first time I have any issue in the Switch custom firmware world, and I've started 2 years ago in March 2019!

My working status was with FW 10.x with AMS 0.14.x or 0.15 and their Hekate Sigpatches.

I prepared the SD card with package taken from SDSetup (AMS 18.1 + hekate 5.5.4v2). I prepared the firmware folder with 11.0.1. I downloaded these sigpatches and replaced the files on the SD card as usual. Note: i basically delete everything but the Nintendo and the switch folders, put the newest SDSetup files, replace the Sigpatches files, make the flags folder/file for firmware update, check/replace the homebrews one by one in the switch folder.
First weird thing: as soon as I pushed the Hekated 5.5.4 included in the SDSetup download I immediately had a message about "old nyx gui. there will be dragons", which is the first time ever I saw this message.
I booted CFW (sysnand) as usual, everything worked, also games played, so I upgraded the firmware using Choi.
Once the process completed, it asked to reboot and I'm back to Hekate (still with the dragons message). I launched again CFW (sysnand) but this time nothing starts, just black screen.

After some failed attempts, I restored the SDSetup AMS, thus basically reverting all the sigpatches files (atmosphere+bootloader). No more "dragons" message as soon as I pushed Hekate. And now the CFW boots, but of course I don't have sigpatches!

EDIT:
I've tried the Sigpatches for 0.18.1, hekate version, from here:
https://github.com/ITotalJustice/patches/releases
No "dragons" error and the CFW boots correctly, but the only game I attempted to start did not launch and is now corrupted :(
EDIT 2:
I noticed ITotalJustice patches do not inlcude a customized hekate_ipl.ini. By adding the two properties kip1patch=nosigchk and atmosphere=1 to the default hekate config now the games boots correctly!

So summarizing:
With sigpatches on this thread:
- Hekate 5.5.4v2 shows dragons error
- 0.14.x+10.x boots from Sysnand and nsp installed games plays correctly
- 0.18.1+11.0.1 won't boot
With ITotalJustice hekate sigpatches:
- 0.18.1+11.0.1 boots and, applying the correct hekate_ipl.ini config the nsp installed games boot correctly.
 
Last edited by ShadowTS,

ShadowOne333

QVID PRO QVO
OP
Editorial Team
Joined
Jan 17, 2013
Messages
12,184
Trophies
2
XP
33,715
Country
Mexico
Hi all,

I have a major issue with these sigpatches, it is the first time I have any issue in the Switch custom firmware world, and I've started 2 years ago in March 2019!

My working status was with FW 10.x with AMS 0.14.x or 0.15 and their Hekate Sigpatches.

I prepared the SD card with package taken from SDSetup (AMS 18.1 + hekate 5.5.4v2). I prepared the firmware folder with 11.0.1. I downloaded these sigpatches and replaced the files on the SD card as usual. Note: i basically delete everything but the Nintendo and the switch folders, put the newest SDSetup files, replace the Sigpatches files, make the flags folder/file for firmware update, check/replace the homebrews one by one in the switch folder.
First weird thing: as soon as I pushed the Hekated 5.5.4 included in the SDSetup download I immediately had a message about "old nyx gui. there will be dragons", which is the first time ever I saw this message.
I booted CFW (sysnand) as usual, everything worked, also games played, so I upgraded the firmware using Choi.
Once the process completed, it asked to reboot and I'm back to Hekate (still with the dragons message). I launched again CFW (sysnand) but this time nothing starts, just black screen.

After some failed attempts, I restored the SDSetup AMS, thus basically reverting all the sigpatches files (atmosphere+bootloader). No more "dragons" message as soon as I pushed Hekate. And now the CFW boots, but of course I don't have sigpatches!

EDIT:
I've tried the Sigpatches for 0.18.1, hekate version, from here:
https://github.com/ITotalJustice/patches/releases
No "dragons" error and the CFW boots correctly, but the only game I attempted to start did not launch and is now corrupted :(
EDIT 2:
I noticed ITotalJustice patches do not inlcude a customized hekate_ipl.ini. By adding the two properties kip1patch=nosigchk and atmosphere=1 to the default hekate config now the games boots correctly!

So summarizing:
With sigpatches on this thread:
- Hekate 5.5.4v2 shows dragons error
- 0.14.x+10.x boots from Sysnand and nsp installed games plays correctly
- 0.18.1+11.0.1 won't boot
With ITotalJustice hekate sigpatches:
- 0.18.1+11.0.1 boots and, applying the correct hekate_ipl.ini config the nsp installed games boot correctly.
How are you booting exactly?
Through fusee-primary or fusee-secondary?
This is important.

The issue that I think could be the culprit, will most likely be the IPS patches directly, and not the patches.ini from Hekate itself.
Also, I don't think the hekate_ipl.ini file that is provided in the pack has anything wrong with it, since it's just settings.
 
  • Like
Reactions: BigOnYa

ShadowTS

Member
Newcomer
Joined
Aug 24, 2020
Messages
22
Trophies
0
Age
36
XP
96
Country
Italy
How are you booting exactly?
Through fusee-primary or fusee-secondary?
This is important.

The issue that I think could be the culprit, will most likely be the IPS patches directly, and not the patches.ini from Hekate itself.
Also, I don't think the hekate_ipl.ini file that is provided in the pack has anything wrong with it, since it's just settings.

In both cases I'm using fusee secondary.
With ITotalJustice it was just a metter of fixing the default hekate_ipl.ini config, adding the parameters for sigpatches, but CFW (sysNAND) boots and installed NSP works.
With the sigpatches on this thread instead, as soon as I push Hekate "5.5.4v2" (name found on SDSetup) I have the "dragons" warning and, with the config already included in this sigpatches package here, the CFW (sysNAND) do not boot, just black screen.
 

ShadowOne333

QVID PRO QVO
OP
Editorial Team
Joined
Jan 17, 2013
Messages
12,184
Trophies
2
XP
33,715
Country
Mexico
In both cases I'm using fusee secondary.
With ITotalJustice it was just a metter of fixing the default hekate_ipl.ini config, adding the parameters for sigpatches, but CFW (sysNAND) boots and installed NSP works.
With the sigpatches on this thread instead, as soon as I push Hekate "5.5.4v2" (name found on SDSetup) I have the "dragons" warning and, with the config already included in this sigpatches package here, the CFW (sysNAND) do not boot, just black screen.
What differences are there between the hekate_ipl.ini that worked and the one that didn't?
 

ShadowTS

Member
Newcomer
Joined
Aug 24, 2020
Messages
22
Trophies
0
Age
36
XP
96
Country
Italy
What differences are there between the hekate_ipl.ini that worked and the one that didn't?

Nothing in the CFW(sysNAND) boot part as I copied the config from the package here to the default hekate one, as ITotalJustice package do not include hekate_ipl.ini.
The differences are in the initial part:
autohosoff=1
bootwait=3
updater2p=0

But as I said, with the sigpatches here I immediately have the "dragons" warning before Hekate starts.
Could be related to the hekate payload used? SDSetup calls it "5.5.4v2", I image is "hekate v5.5.4 & Nyx v1.0.1" as there was a previous "hekate v5.5.4 & Nyx v1.0.0".
 

ShadowOne333

QVID PRO QVO
OP
Editorial Team
Joined
Jan 17, 2013
Messages
12,184
Trophies
2
XP
33,715
Country
Mexico
Nothing in the CFW(sysNAND) boot part as I copied the config from the package here to the default hekate one, as ITotalJustice package do not include hekate_ipl.ini.
The differences are in the initial part:
autohosoff=1
bootwait=3
updater2p=0

But as I said, with the sigpatches here I immediately have the "dragons" warning before Hekate starts.
Could be related to the hekate payload used? SDSetup calls it "5.5.4v2", I image is "hekate v5.5.4 & Nyx v1.0.1" as there was a previous "hekate v5.5.4 & Nyx v1.0.0".
It could be related to a mismatch of Nyx, but I am not sure.
Do you have an image of the error?
 

ShadowOne333

QVID PRO QVO
OP
Editorial Team
Joined
Jan 17, 2013
Messages
12,184
Trophies
2
XP
33,715
Country
Mexico
The message showing up is the one in the original post on this thead:
https://gbatemp.net/threads/bootloader-dragons-error.561914/

Later, starting CFW(sysNAND), just a black screen.
Ah yes, it's an error with Nyx not being the correct version.
Though sysNAND starting to a black screen shouldn't be happening, or really have anything to do with sigpatches afaik.
If the sigpatches are wrong, only booting up a game will result in an error, nothing else from the system should be touched.
 
  • Like
Reactions: BigOnYa

Gep_Etto

Being late since '88
Member
Joined
Mar 1, 2021
Messages
375
Trophies
0
XP
1,154
Country
Brazil
I get my sigpatches from AIO Updater. Is there any advantage in getting them from these threads other than getting them sooner?
 

LyuboA

Unknown Entity
Member
Joined
Jun 1, 2018
Messages
530
Trophies
0
XP
919
Country
Bulgaria
I get my sigpatches from AIO Updater. Is there any advantage in getting them from these threads other than getting them sooner?

AIO Updater get the patches from ITotalJustice repo and that repo is always first with the updates actually before the tools to make patches ourselves the OP was getting the patches for this thread from that same repo so better stick with the AIO Updater
 
  • Like
Reactions: BigOnYa

Gep_Etto

Being late since '88
Member
Joined
Mar 1, 2021
Messages
375
Trophies
0
XP
1,154
Country
Brazil
AIO Updater get the patches from ITotalJustice repo and that repo is always first with the updates actually before the tools to make patches ourselves the OP was getting the patches for this thread from that same repo so better stick with the AIO Updater
Gotcha! Thanks a lot. I'm still learning and you were very helpful.
 
  • Like
Reactions: BigOnYa

loopout

Member
Newcomer
Joined
May 26, 2017
Messages
14
Trophies
0
Age
37
XP
94
Country
Having a problem :S

Just updated to latest Deepsea release with Atmos 18.1, updated to latest fw 11.0.1, updated fss0 sigpatches from this thread and updated goldleaf to v9.

Then, I can launch already installed backups perfectly with no problems but any game (even older ones like Link's A.) that I try to install with goldleaf and quark says NCA invalid, sigpatches missing or too old version.

Any ideas? very strange that I can boot games with no problem but not install new ones.
 

Gep_Etto

Being late since '88
Member
Joined
Mar 1, 2021
Messages
375
Trophies
0
XP
1,154
Country
Brazil
Then, I can launch already installed backups perfectly with no problems but any game (even older ones like Link's A.) that I try to install with goldleaf and quark says NCA invalid, sigpatches missing or too old version.

That smells like a problem with your sigpatches. There's the hekate sigpatches (for when you first boot into hekate's payload before chainloading atmosphère with fusée-secondary) and the atmosphère sigpatches (for when you inject the fusée-primary payload directly). Are you sure you got the correct ones for your chosen method of booting into the CFW?

If that's not it, have you tried using an installer other than Goldleaf? I recommend you try Awoo Installer or TinWoo. They'll both warn you about invalid NCA signatures, but they'll allow you to proceed with the installation anyway. Only do that if you trust the source from where you got the games you're trying to install, as invalid signatures can mean that the files were maliciously altered (they can also mean nothing at all - e.g. if you split a >4GB NSP to fit in your FAT32 SD card, that will invalidate the NCA signature as well - but better safe than sorry).
 
  • Like
Reactions: BigOnYa

Site & Scene News

Popular threads in this forum

General chit-chat
Help Users
    Maximumbeans @ Maximumbeans: butte