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

[Chains]

Can confirm all the games are working with the latest hekate 0.14.2 patches.

for me some games not working with latest patch like pokemon sword

That specific game did not work for me either, when I did a clean atmo + hekate 0.14.2 patch install.
I got it working by copying exefs_patches/es_patches into the atmosphere folder.

 

[ShadowOne333]

Can confirm all the games are working with the latest hekate 0.14.2 patches.



That specific game did not work for me either, when I did a clean atmo + hekate 0.14.2 patch install.
I got it working by copying exefs_patches/es_patches into the atmosphere folder.

Interesting.
So actually copying the IPS patches into those folders does make a difference?
I assume you had the patches.ini file only?

 

[fmjax]

That specific game did not work for me either, when I did a clean atmo + hekate 0.14.2 patch install.
I got it working by copying exefs_patches/es_patches into the atmosphere folder.

fusee_primary.bin needs exefs_patches and kip_patches.
fusee_secondary.bin needs exefs_patches and patches.ini.

I already did some comparisons alongside what the user at the other thread said, and so far it has been narrowed to 29CA1C792CF3AB63 and 987521753F9B8CE9.
The first one is not in IPS format in this pack, while the other seems to have 4 more bytes patched in from the fusee-primary pack.
So we might need to implement the recent/updated changes from those two into the fss0 pack ith patches.ini

Is someone creating patches.ini from scratch? It should be easy to convert working kip_patches to the patches.ini format.

 

[fmjax]

These fs_patches IPS files have changed between between the fusee_primary patches for 0.14.1 and 0.14.2, but patches.ini for 0.14.2 in this thread does not reflect this. Only a new loader patch has been added.

#FS 10.0.0
[FS:3EEBD9B7BCD1B5E0]
#FS 10.0.0-ExFAT
[FS:817EA2B0B702C1F3]

Edit:
The IPS patches seem to be overwriting a longer pattern. I think they're functionally the same.

 

[shivoooooo]

Did you try the last option of Initializing the console?
I had that issue before with one specific game that, no matter what I did, it didn't work, while it worked before I updated.
Only after doingthe initialization step it ended up working for.
It's the most extreme of cases, but the only one if you already tried everything else.



I already did some comparisons alongside what the user at the other thread said, and so far it has been narrowed to 29CA1C792CF3AB63 and 987521753F9B8CE9.
The first one is not in IPS format in this pack, while the other seems to have 4 more bytes patched in from the fusee-primary pack.
So we might need to implement the recent/updated changes from those two into the fss0 pack ith patches.ini

Did you try the last option of Initializing the console?

Really, this was the only thing he hadn't done.

I did it. It worked.
Initialize the console and format the microSD.

But install vanilla Atmosphere and Sigpatches for Atmosphere (fusee-primary)

 

[swtch_jts]

I moved from deepsea to clean atmosphere and now everything is working

 

[Ange1333]

Guys I am lost, and very confused.

I followed this guide perfectly, and everything that guide goes through works perfect.
switch. homebrew. guide/

But Gamecard Installer and Goldleaf, the two only reasons I wanted to do this, do not work.

Gamecard installer will install the game but never be able to open and always gets corrupted.
Goldleaf does not even install anything and just fails right away (trying to install a .nsp)

All my googling has led me here, to whatever the hell sigpatches are. I copied the data from the download onto my SD and there is no difference, and now I'm stumped.

The payload I'm using is hekate_ctcaer_5.3.2.bin as per the noob guide, could that be the problem?

Any guidance is appreciated, sorry I'm a noob with no knowledge of programming trying to wrap my head around all of this.

 

[Ibcap]

The payload I'm using is hekate_ctcaer_5.3.2.bin as per the noob guide, could that be the problem?

Any guidance is appreciated, sorry I'm a noob with no knowledge of programming trying to wrap my head around all of this.

Yes. That is the problem. Youre using an unofficial boot method that doesnt work with normal sigpatches. Youll need to either get the atmosphere payload from atmospheres github to boot, or get the fss0 specific sigpatches from the other sigpatch thread,

edit: just realized this is already the fss0 thread. so probably didnt update to the new patches

 

[Hayato213]

Guys I am lost, and very confused.

I followed this guide perfectly, and everything that guide goes through works perfect.
switch. homebrew. guide/

But Gamecard Installer and Goldleaf, the two only reasons I wanted to do this, do not work.

Gamecard installer will install the game but never be able to open and always gets corrupted.
Goldleaf does not even install anything and just fails right away (trying to install a .nsp)

All my googling has led me here, to whatever the hell sigpatches are. I copied the data from the download onto my SD and there is no difference, and now I'm stumped.

The payload I'm using is hekate_ctcaer_5.3.2.bin as per the noob guide, could that be the problem?

Any guidance is appreciated, sorry I'm a noob with no knowledge of programming trying to wrap my head around all of this.

If you are using Hekate to load Fusee-Secondary then use the FSS0/Hekate patches, if you are booting from Fusee-Primary then use the Fusee Signature patches.

FSS0 patches can be found in the opening post.

https://gbatemp.net/threads/guide-to-choose-which-atmosphere-patches-to-use-on-switch-fw-10.563886/

Explanation of booting with Fusee-Primary and using Hekate to boot Fusee-Secondary and explained in the thread above.

 

[capsleepyy]

Yes. That is the problem. Youre using an unofficial boot method that doesnt work with normal sigpatches. Youll need to either get the atmosphere payload from atmospheres github to boot, or get the fss0 specific sigpatches from the other sigpatch thread,

fss0 isn't unofficial, if it was then SciresM would've never written the option in the first place. It's just not default, don't be disingenuous.

 

[Ibcap]

fss0 isn't unofficial, if it was then SciresM would've never written the option in the first place. It's just not default, don't be disingenuous.

What? SciresM didnt make it and it isnt part of atmosphere. Its part of HEKATE which Scires never made and has no involvement with. anyway i just realized this is already the fss0 thread so probably the issue is they didnt get the new patches i uploaded the other day.

 

[capsleepyy]

What? SciresM didnt make it and it isnt part of atmosphere. Its part of HEKATE which Scires never made and has no involvement with. anyway i just realized this is already the fss0 thread so probably the issue is they didnt get the new patches i uploaded the other day.

https://github.com/Atmosphere-NX/Atmosphere/releases/tag/0.8.5

 

[ZachyCatGames]

What? SciresM didnt make it and it isnt part of atmosphere. Its part of HEKATE which Scires never made and has no involvement with. anyway i just realized this is already the fss0 thread so probably the issue is they didnt get the new patches i uploaded the other day.

Scires had direct involvement in its creation, support for it had to specifically be added to Atmosphere and it's an official feature.

 

[Ibcap]

Scires had direct involvement in its creation, support for it had to specifically be added to Atmosphere and it's an official feature.

Really? Well til then i trust you on that. But base atmosphere cant use it right? You would require outside programs like hekate

Edit: from reading the github it looks like scires specifically allowed people to make alternate boot methods, but he himself was not part of developing fss0 which would be the specific hekate function. Maybe theres more to this that im unaware of, but i wouldnt say that microsoft made a program or that the program is officially part of windows just because windows supports the functions the program uses.

 

[ZachyCatGames]

Really? Well til then i trust you on that. But base atmosphere cant use it right? You would require outside programs like hekate

Edit: from reading the github it looks like scires specifically allowed people to make alternate boot methods, but he himself was not part of developing fss0 which would be the specific hekate function.

So, how it works is that fusee-secondary has a header that contains information on where the various kips, exosphere, sc7fw/lp0fw, etc are stored in the binary.
This header is specifically intended to allow other bootloaders (ex. Hekate) to pull the kips and all that stuff out of the fusee-secondary binary and boot with them (previously you'd have to manually extract them or compile Atmosphere yourself, throw them on your SD card, and create a config pointing to the individual kips, secmon, etc).
The header had specifically been added by Scires for that purpose.

 

[Ibcap]

So, how it works is that fusee-secondary has a header that contains information on where the various kips, exosphere, sc7fw/lp0fw, etc are stored in the binary.
This header is specifically intended to allow other bootloaders (ex. Hekate) to pull the kips and all that stuff out of the fusee-secondary binary and boot with them (previously you'd have to manually extract them or compile Atmosphere yourself, throw them on your SD card, and create a config pointing to the individual kips, secmon, etc).
The header had specifically been added by Scires for that purpose.

Yes i understand that, scires added support for atmosphere to be booted via other methods. However supporting the ability for devs to develop fss0 is not the same as scires himself making fss0 and its definitely not the same as fss0 being part of atmosphere. I even double checked with pika on this because i was second guessing myself.

 

[ZachyCatGames]

Yes i understand that, scires added support for atmosphere to be booted via other methods. However supporting the ability for devs to develop fss0 is not the same as scires himself making fss0 and its definitely not the same as fss0 being part of atmosphere. I even double checked with pika on this because i was second guessing myself.

fss0 is part a of Atmosphere, and can be used by other developers to more easily boot Atmosphere with other bootloaders. Open fusee secondary in a hex editor and you'll see it right there at the start of the file.

 

[Ibcap]

fss0 is part a of Atmosphere, and can be used by other developers to more easily boot Atmosphere with other bootloaders. Open fusee secondary in a hex editor and you'll see it right there at the start of the file.
View attachment 224379

Huh well then, i didnt know that. I stand corrected then. Anyway going back to the initial issue, they probably werent using the new patches for 0.14.2.

 

[ShadowOne333]

So how are the latest patches by lbcap working for everyone?
Has anyone had issues so far?

I haven't been able to test, much less update anything yet.
I might try to see if I can port the latest modified patches from their IPS form into Hekate's patches.ini form, but I'm not sure what file in particular those IPS patches touch to compare them and get the original values.

Anyone has a clue as to how to do that?

 

[Ange1333]

If you are using Hekate to load Fusee-Secondary then use the FSS0/Hekate patches, if you are booting from Fusee-Primary then use the Fusee Signature patches.

FSS0 patches can be found in the opening post.



Explanation of booting with Fusee-Primary and using Hekate to boot Fusee-Secondary and explained in the thread above.

Thank you so much! This was exactly my problem. I just restarted from scratch using fuse-primary and the Sig patches seem to be working for gamecard installer, been too busy to try goldleaf yet but I'm assuming that was the problem for that as well.

Also sorry tad unrelated, after I install with gamecard installer it tells me to update. So I booted the switch without cfw, updated, then launched games in airplane mode (in cfw). Is this right?