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

[Mars04]

Why are you mixing sys-patch and sigpatches?

Sys-patch is enough.

I just had them always both, with the idea of having a backup if one of both fails. But will remove sigpatches now and only go forward with sys-patch from now on.

Since I don't have to use sigpatches anymore, what is actually the best or fastest way to boot up atmosphere? Should I go back to fusee or staying with Hekate FSS0 to boot up system?

 

[Blythe93]

what is actually the best or fastest way to boot up atmosphere? Should I go back to fusee or staying with Hekate FSS0 to boot up system?

Pushing the fusee.bin payload is probably the fastest. I do use Hekate's FSS0 to boot up my system, though, mainly because I set Hekate's payload as my reboot-to-payload payload. No issues whatsoever while using sys-patch only.

 

[josete2k]

In the past fss0 was faster than fusee.

Now they are the same.

 

[ConraDargo]

install SYS-PATCH https://gbatemp.net/download/sys-patch-sysmodule.38936/ and restarT your console

Ah, that did the trick! I was so sure that I'd have to use an older sys-patch since I'm still on 18.1.0.

Everything's working as it should now, thanks!

Edit: Should my \atmosphere\contents folder contain anything other than the 420000000000000B folder? I'm thinking I've got stuff that shouldn't be here (two extra folders to be precise), although I did uninstall sigpatches by using TinWoo.

 

[shadow256]

Ah, that did the trick! I was so sure that I'd have to use an older sys-patch since I'm still on 18.1.0.

Everything's working as it should now, thanks!

Edit: Should my \atmosphere\contents folder contain anything other than the 420000000000000B folder? I'm thinking I've got stuff that shouldn't be here (two extra folders to be precise), although I did uninstall sigpatches by using TinWoo.

The "atmosphere/contents" folder contains modules for the CFW or mods or cheats for games. What are the folders' name in it, with this we should try to identify the contents?

 

[ConraDargo]

The "atmosphere/contents" folder contains modules for the CFW or mods or cheats for games. What are the folders' name in it, with this we should try to identify the contents?

I've got 00FF0000636C6BFF and 420000000007E51A!

 

[shadow256]

I've got 00FF0000636C6BFF and 420000000007E51A!

"0FF0000636C6BFF" is the module Sys--clk and "420000000007E51A" is the module for launching overlays (Tesla or Ultrahand).

 

[ConraDargo]

Oooh gotcha, thank you!

 

[The_Chaotician]

Sounds like a lot of people are having issues with 19.0.0 / 19.0.1...

My setup is:
- Erista chipset, model HAC-001
- SysNAND OFW 19.0.1
- EmuNAND OFW 19.0.1
- Atmosphere 1.8.0
- Hekate 6.2.2

- kip1patch=nosigchk is enabled in my hekate_ipl.ini for EmuNAND ONLY​

- Latest Sigpatches from this thread (V6), including the prodinfo fix
- SysPatch 1.5.5
- Switchcraft EOS 1.5.0

- Includes Ultrahand and sys-clk​

- Exosphere is enabled to blank my PRODINFO for both SysNAND and EmuNAND CFW
- dns_mitm is installed
- 90DNS is set up correctly
- I do not (and will not) use Tinfoil. The latest English release of DBI works fine for me.

I always boot into CFW through Hekate using an official xkit USB dongle (not one of the many Chinese copies) - e.g. not directly with fusee through Tegrasmash.

When i boot into my EmuNAND, my Sys-Patch logs match the picture in this post.

As far as i can see, everything is working as expected, i updated my forwarders before i updated my Switch, as i was aware of the issues with them in advance. So my questions are as follows:

1) Should i care?
2) I recall a post by @impeeza suggesting it doesn't hurt to have both sigpatches and sys-patch installed - has this changed, and what is the recommended set up if so?

 

[bth]

I personally cannot reproduce any problems;
fw 19.0.1, emunand
sys-patch 1.5.5
atmosphere 1.8.0
hekate set to boot with payload=atmosphere/reboot_payload.bin
exosphere prodinfo blanker and dnsmitm (just *nintendo* 127.0.0.1) configured
every single item is patched.

zero kip_patches (fusee-mod), zero patches.ini (hekate), zero exefs_patches. All done by sys-patch.

installed homebrew works, installed games work, tinfoil v19 works as expected.

2) I recall a post by @impeeza suggesting it doesn't hurt to have both sigpatches and sys-patch installed - has this changed, and what is the recommended set up if so?

I cannot speak for what is being distributed, but it sounds like that both incorrect patches are circulating (FS), in addition to compatibility issues with the ES .ips exefs_patch when also running sys-patch, which seem unique to 19.0.0+

 

[The_Chaotician]

I personally cannot reproduce any problems;
fw 19.0.1, emunand
sys-patch 1.5.5
atmosphere 1.8.0
hekate set to boot with payload=atmosphere/reboot_payload.bin
exosphere prodinfo blanker and dnsmitm (just *nintendo* 127.0.0.1) configured
every single item is patched.

zero kip_patches (fusee-mod), zero patches.ini (hekate), zero exefs_patches. All done by sys-patch.

installed homebrew works, installed games work, tinfoil v19 works as expected.



I cannot speak for what is being distributed, but it sounds like that both incorrect patches are circulating (FS), in addition to compatibility issues with the ES .ips exefs_patch when also running sys-patch, which seem unique to 19.0.0+

Thanks for the reply - as i say, i dont see any problems!

You mention a fusee-mod, do you happen to have a link for it? I'm interested to try it!

 

[bth]

Thanks for the reply - as i say, i dont see any problems!

You mention a fusee-mod, do you happen to have a link for it? I'm interested to try it!

all it does is revert this commit https://github.com/Atmosphere-NX/Atmosphere/commit/46a43578829163cd08b9ddcaaacc6febd1e71e0e
it's unnecessary and stupid, use sys-patch.

 

[The_Chaotician]

all it does is revert this commit https://github.com/Atmosphere-NX/Atmosphere/commit/46a43578829163cd08b9ddcaaacc6febd1e71e0e
it's unnecessary and stupid, use sys-patch.

Lets hope the mighty @impeeza remains interested in keeping it up to date in the future

 

[bth]

Anyways i checked the patches.ini this thread links to

what I generate myself is this:

#FS 19.0.0-fat32
[FS:D94C6815F8F50A20]
.nosigchk=0:0x021478:0x4:60090036,1F2003D5
.nosigchk=0:0x0745A0:0x4:89740394,E0031F2A

#FS 19.0.0-exfat
[FS:EDA87868A4490750]
.nosigchk=0:0x021478:0x4:60090036,1F2003D5
.nosigchk=0:0x0745A0:0x4:95A20394,E0031F2A

while the ones in the patches.ini from this thread is:

#FS 19.0.0-FAT - SDKVersion:19.3.0.0
[FS:D94C6815F8F50A20]
.nosigchk=0:0x745A0:0x4:89740394,E0031F2A
.nosigchk=0:0x21478:0x4:60090036,1F2003D5
.nosigchk=0:0x74524:0x4:C0030054,10000014

#FS 19.0.0-ExFAT - SDKVersion:19.3.0.0
[FS:EDA87868A4490750]
.nosigchk=0:0x745A0:0x4:95A20394,E0031F2A
.nosigchk=0:0x21478:0x4:60090036,1F2003D5
.nosigchk=0:0x74524:0x4:C0030054,10000014

 

[impeeza]

Lets hope the mighty @impeeza remains interested in keeping it up to date in the future

Hello there, I am not the programmer, I am only a collector (hoarder if you like) and a proxy for the real heroes whom making the patches or change the code to include the new set of patterns.

Some of them want to remain anonymous the others are referenced on the pages

 

[The_Chaotician]

Hello there, I am not the programmer, I am only a collector (hoarder if you like) and a proxy for the real heroes whom making the patches or change the code to include the new set of patterns.

Some of them want to remain anonymous the others are referenced on the pages

Either way, your work is very much appreciated. Safe to say a lot of us would still be having problems if not for your effort

 

[gerardPolloRebozado]

I have updated to atmosphere 19 and installed the sys-patch and instaled new sigpatches from it but when booting atmosphere I get nosigchk error and can't open any app. I also changed the hetake_ipl:
[config] autoboot=0 autoboot_list=0 bootwait=0 autohosoff=0 autonogc=1 updater2p=1 backlight=100 [CFW - sysMMC] fss0=atmosphere/package3 kip1patch=nosigchk atmosphere=1 emummc_force_disable=1 icon=bootloader/res/icon_payload.bmp [CFW - emuMMC] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 atmosphere=1 icon=bootloader/res/icon_payload.bmp [Stock - sysMMC] fss0=atmosphere/package3 emummc_force_disable=1 stock=1 icon=bootloader/res/icon_switch.bmp
I alsoe downloaded the custom fusee.bin

 

[shadow256]

I have updated to atmosphere 19 and installed the sys-patch and instaled new sigpatches from it but when booting atmosphere I get nosigchk error and can't open any app. I also changed the hetake_ipl:
[config] autoboot=0 autoboot_list=0 bootwait=0 autohosoff=0 autonogc=1 updater2p=1 backlight=100 [CFW - sysMMC] fss0=atmosphere/package3 kip1patch=nosigchk atmosphere=1 emummc_force_disable=1 icon=bootloader/res/icon_payload.bmp [CFW - emuMMC] fss0=atmosphere/package3 kip1patch=nosigchk emummcforce=1 atmosphere=1 icon=bootloader/res/icon_payload.bmp [Stock - sysMMC] fss0=atmosphere/package3 emummc_force_disable=1 stock=1 icon=bootloader/res/icon_switch.bmp
I alsoe downloaded the custom fusee.bin

Don't use sig_patches anymore, I gave some instructions to delete it a few post ago.

In your Hekate's config delete the lines "kip1patch=nosigchk" witch are now unusful when not using sig_patches. And also don't use custom fusee.bin, like sig_patches it's unusful except for some people who want to make some advanced tests.

 

[Emrah1925]

working on them

Post automatically merged: Oct 16, 2024

Happy June 15th for everyone!!

with this great day also comes the new set of patches.

I can't download it?

 

[impeeza]

I can't download it?

yes read the OP