Hacking RELEASE Sigpatches for Atmosphere (fusee-primary only!)

Tokiwa · Jul 8, 2020

The sigpatches itself are fine, i've been using them since it was posted here

Make sure you guys are also updating the fusee-primary.bin file, it needs to match the same version of the atmosphere you're using.

Yondaime_Kazzy · Jul 8, 2020

Tokiwa said:
The sigpatches itself are fine, i've been using them since it was posted here

Make sure you guys are also updating the fusee-primary.bin file, it needs to match the same version of the atmosphere you're using.

I don't think the sigpatches are fine because my CFW just now booted up when I didn't have the sigpatches. I also have an updated fusee-primary.bin file so that's not the issue. But I am going to do more testing.

Tokiwa · Jul 8, 2020

Yondaime_Kazzy said:
I don't think the sigpatches are fine because my CFW just now booted up when I didn't have the sigpatches. I also have an updated fusee-primary.bin file so that's not the issue. But I am going to do more testing.

They are fine, yes. I tested them myself, i've done this on more than one Switches and they are all working fine. Your issue is definitely something else.

If it still fails, delete (not overwrite) your atmosphere and sept folders, redownload latest atmosphere from the official github, install the patches from this thread and nothing else (no custom system module for example) and try again with latest fusee-primary.bin.

Yondaime_Kazzy · Jul 8, 2020

Tokiwa said:
They are fine, yes. I tested them myself, i've done this on more than one Switches and they are all working fine. Your issue is definitely something else.

If it still fails, delete your atmosphere and sept folders, redownload latest atmosphere from the official github, install the patches from this thread and nothing else (no custom system module for example) and try again with latest fusee-primary.bin.

I said earlier that I already reinstalled atmosphere and I was already going to try to install the patches again. I'll let you guys know if it still works after the patches.

--------------------- MERGED ---------------------------

Tokiwa said:
They are fine, yes. I tested them myself, i've done this on more than one Switches and they are all working fine. Your issue is definitely something else.

If it still fails, delete (not overwrite) your atmosphere and sept folders, redownload latest atmosphere from the official github, install the patches from this thread and nothing else (no custom system module for example) and try again with latest fusee-primary.bin.

So, it works. I think I updated Atmosphere incorrectly by overwriting the folders instead of deleting them completely. Thank you for your patience.

CanadianHummus · Jul 9, 2020

Ibcap said:
I dont make the patches but I know who has been making them (these and the last patches for 10.0.0). I would recommend using fusee over fss0. You can configure hekate to load it with your normal launch options.

Any idea how these sigpatches are made?

DaFixer · Jul 10, 2020

Just updated my switch to OFW 10.4 and AMS 0.13.0 and I use the new sigpatched.
But when loading Kosmos I get a "failed to appy 'nosigchk' " error

Bullseye · Jul 10, 2020

DaFixer said:
Just updated my switch to OFW 10.4 and AMS 0.13.0 and I use the new sigpatched.
But when loading Kosmos I get a "failed to appy 'nosigchk' " error

I would have not expected that, coming from "DaFixer" lol.

You need sigpatches for hekate, these ones are for fusee-primary.

DaFixer · Jul 10, 2020

Bullseye said:
I would have not expected that, coming from "DaFixer" lol.

You need sigpatches for hekate, these ones are for fusee-primary.

I'm a more into hardware, but like to learn new stuff

But I find those sigpatches and copy it to SD card and it works.
Thank you for your help

Bullseye · Jul 10, 2020

DaFixer said:
I'm a more into hardware, but like to learn new stuff
But I find those sigpatches and copy it to SD card and it works.
Thank you for your help

Happy to help! Takes a bit to understand everything but once you do it's quite simple, thanks to the Devs, of course, that they make it dummy proof

William Bernhard · Jul 10, 2020

hey people I just updated my sigpatches but now I get a black screen with this error:
A fatal error occurred when runing Atmospere.
Title ID: 010041544d530000
Error Desc: std::abort() called (0xffe)
anyone know the problem? I already tried deleting my atmosphere and hekate folders and using fresh copies again along the new sigpatches.
any suggestions?

CanadianHummus · Jul 11, 2020

Hello, I am Junior Developer and I was wondering how the signature patches are created? Also was wondering why there are 2 different ones (Hekate & Fuse)? I was under the impression that the hekate payload invokes the fuse payload. Thanks in advance

LyuboA · Jul 11, 2020

CanadianHummus said:
Hello, I am Junior Developer and I was wondering how the signature patches are created? Also was wondering why there are 2 different ones (Hekate & Fuse)? I was under the impression that the hekate payload invokes the fuse payload. Thanks in advance

you can use hekate to chainload the fusee-primary payload but you can also use hekate as atmos bootloader and directly load fusee-secondary then you need patches for hekate since hekate reads the same patches differently then atmos bootloader
and as for how they are made devs dont say this way they feel better then everyone else

hippy dave · Jul 11, 2020

Someone will have disassembled the firmware code and tracked down the functions that perform the signature checks and give error messages if they fail, and will have modified that code to always give the correct result. These modifications are translated into patch files that are applied to change the relevant code when the system starts. Most of the time the patches can be ported to a new firmware version by looking for the matching code instructions and changing the patches to the new addresses - this is more straightforward than the original task of creating the patches, so there are probably more people who can do it. If there are significant changes in the relevant code between firmware versions - like the recent change that moved one sigcheck to a different system module - then more disassembly work may be needed.

CanadianHummus · Jul 11, 2020

hippy dave said:
Most of the time the patches can be ported to a new firmware version by looking for the matching code instructions and changing the patches to the new addresses - this is more straightforward than the original task of creating the patches, so there are probably more people who can do it.

^This is exactly what I am trying to do. I am using HxD (16 bit) to anaylize the patches but cant seem to figure what the encoding is which ends up leaving with a bunch of gibberish.

I.e
.
50 41 54 43 48 01 5F CC 00 04 E0 03 1F 2A 01 60 64 00 04 E0 03 1F 2A 03 FB F8 00 04 1F 20 03 D5 04 EC 24 00 04 1F 20 03 D5 04 EC 30 00 04 1F 20 03 D5 04 F4 30 00 08 1F 20 03 D5 1F 20 03 D5 04 F4 3C 00 04 1F 20 03 D5 04 F4 50 00 04 1F 20 03 D5 45 4F 46

Decoded text:
PATCH_Ì�à*`d�à*ûø� Õì$� Õì0� Õô0� Õ Õô<� ÕôP� ÕEOF

hippy dave · Jul 12, 2020

CanadianHummus said:
^This is exactly what I am trying to do. I am using HxD (16 bit) to anaylize the patches but cant seem to figure what the encoding is which ends up leaving with a bunch of gibberish.

I.e
.
50 41 54 43 48 01 5F CC 00 04 E0 03 1F 2A 01 60 64 00 04 E0 03 1F 2A 03 FB F8 00 04 1F 20 03 D5 04 EC 24 00 04 1F 20 03 D5 04 EC 30 00 04 1F 20 03 D5 04 F4 30 00 08 1F 20 03 D5 1F 20 03 D5 04 F4 3C 00 04 1F 20 03 D5 04 F4 50 00 04 1F 20 03 D5 45 4F 46

Decoded text:
PATCH_Ì�à*`d�à*ûø� Õì$� Õì0� Õô0� Õ Õô<� ÕôP� ÕEOF

The patches themselves are IPS format. You could look that up, or you could apply the patch file to the firmware file it's intended for, and then compare the patched file with the original.

pofehof · Jul 14, 2020

Looks like a new update just dropped (10.1.0). Doubt it'll work with Atmosphere atm since it seems to be a big update, so we'll need to wait a while for sigpatches.

Edit: Atmosphere 0.12.0 boots fine, will check if new sigpatches are needed.

KiiWii · Jul 14, 2020

https://twitter.com/sciresm/status/1282831275170992128?s=21

rodrigues14 · Jul 14, 2020

just wainting for new patches to update :rofl2:

pofehof · Jul 14, 2020

Can confirm that the current sigpatches for 0.13.0 (and even those for 0.12.0) work with 10.1.0. No need to wait for sigpatch update it seems.

MasterJ360 · Jul 14, 2020

Im sure a switch thread of a new system update 10.1.0 is being made but atleast nothing serious was changed for cfw. I just updated to 10.04 for smash and this comes out sigh....

Hacking RELEASE Sigpatches for Atmosphere (fusee-primary only!)

Well-Known Member

Well-Known Member

Well-Known Member

Well-Known Member

New Member

Dare to be stupid

Well-Known Member

Dare to be stupid

Well-Known Member

Well-Known Member

New Member

Unknown Entity

BBMB

New Member

BBMB

Well-Known Member

Editorial Team

Well-Known Member

Well-Known Member

Well-Known Member

Similar threads

Popular threads in this forum