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

[impeeza]

no, you either gotta boot atmosphere with hekate using fsso, use a modified version of atmosphere that enables kips, or you gotta use sys-patch

Or all of them

 

[Asia81]

You can NO LONGER use OFFICIAL Atmosphere with signature patches. They're no longer supported.
You HAVE TO USE Hekate or Sys-Patch

Guide for how to setup Sys-Patch (interface requires Tesla on your Switch)
https://www.gamebrew.org/wiki/Sys-patch_Switch

Borrowing from @impeeza hekate_ipl.ini file
Your hekate_ipl.ini need this to launch with Patches via Hekate

[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

sys-patch was't working anymore for me on 18.0 and latest ams (games was unable to start), so i just manually downloaded the kip sigpatch and now everything work

 

[linuxares]

sys-patch was't working anymore for me on 18.0 and latest ams (games was unable to start), so i just manually downloaded the kip sigpatch and now everything work

Yeah sys-patch have been updated to work with the latest version. It's on the Cat site

 

[Asia81]

Yeah sys-patch have been updated to work with the latest version. It's on the Cat site

not sure what cat sit refer to, but eh, i thought the project was dead due to the recent dmca

 

[impeeza]

Yeah sys-patch have been updated to work with the latest version. It's on the Cat site

and here on the sys-patch thread there is a link to: https://gitflic.ru/project/impeeza/sys-patch/release

 

[RedColoredStars]

I tried and can connect the switch to wifi with internet connection not turned on, this is the point of the patch.

Can you please tell me the steps you took to achieve/test this? I was previously wrong and I must be doing something incorrect in the process because I can't connect to wifi with the internet connection off regardless of sigpatches or sys-patch.

 

[Kiran36]

I can't get past the switch logo when booting atmosphere, I've updated the sigpatches, atmosphere and hekate and I also have 18.0 on the switch (don't know if that matters), I'm pretty sure I'm booting trough fs0 but i tried the modified fusee.bin and ended up the same. Is it bc the sigpatches are not for atmosphere latest version? Can anyone help me pls?

 

[impeeza]

I can't get past the switch logo when booting atmosphere, I've updated the sigpatches, atmosphere and hekate and I also have 18.0 on the switch (don't know if that matters), I'm pretty sure I'm booting trough fs0 but i tried the modified fusee.bin and ended up the same. Is it bc the sigpatches are not for atmosphere latest version? Can anyone help me pls?

Bootlogo lockup normally have nothing to do with sigpatches, maybe a currupted SDCard or emunand, can you boot in to OFW?

 

[urherenow]

I don't believe that and I've already explained why several times over. For the last time.... If using both sigpatches and sys-patch, the sys-patch overlay should show ctest in orange.

The color will not change once it works and stays working. The logs don't get completely rewritten every time you boot. Delete your logs and see what color it is. Your "belief" doesn't negate reality.

 

[RedColoredStars]

The color will not change once it works and stays working. The logs don't get completely rewritten every time you boot. Delete your logs and see what color it is. Your "belief" doesn't negate reality.

You're late to the party. This has already been discussed and cleared up. Also, the log does in fact change at boot. If you turn patches off in the setting and reboot, the log will reflect that. Soooooooo.... yeah.

 

[urherenow]

You're late to the party. This has already been discussed and cleared up. Also, the log does in fact change at boot. If you turn patches off in the setting and reboot, the log will reflect that. Soooooooo.... yeah.

because you turned the setting off. Now, didn't I start off with "As long as they are working and STAY WORKING"? Before the repo went down, there was an issue about this very thing. Deleting the logs was the solution.

EDIT: Or maybe I'm not getting enough sleep. I seem to have completely missed the replies from duckbill007 and iTotalJustice

 

[RedColoredStars]

EDIT: Or maybe I'm not getting enough sleep. I seem to have completely missed the replies from duckbill007 and iTotalJustice

Yeah. lol. It's been cleared up. Cheers.

 

[Kiran36]

Bootlogo lockup normally have nothing to do with sigpatches, maybe a currupted SDCard or emunand, can you boot in to OFW?

Yeah, OFW works fine, but i can't get to CFW, I think i've had this problem before but i don't remember how I solved it

 

[impeeza]

Yeah, OFW works fine, but i can't get to CFW, I think i've had this problem before but i don't remember how I solved it

Try to backup and remove the /atmosphere/config folder and try to boot CFW

 

[Kiran36]

Try to backup and remove the /atmosphere/config folder and try to boot CFW

Still freezes at the logo

 

[impeeza]

Still freezes at the logo

test your card may be is corrupted.

 

[urherenow]

Still freezes at the logo

Sorry for jumping in without going back to find out... but are you launching with a game cart inserted? Does removing it make a difference? I mean... since you've booted OFW, it shouldn't really matter, unless your emummc is a really old version (using sxos would be the only reason I can think of to do that). And another thing, that I don't think I've heard of locking at the boot logo, but rather triggering a crash early after startup, would be having your serial number blanked in CFW, while not having the proper servers blocked in the hosts file...

Also, if it's been a while since you've updated Atmosphere, it can take a while (SEVERAL minutes) for it to delete old logs and crash reports. Try deleting everything in atmosphere/fatal_errors, fatal_reports, and logs. See if something manages to appear in there if you try again and it still locks up.

 

[Hassal]

Still freezes at the logo

Your problem is in your emuNAND its corrupted, you can either opt to fix it or generate a new one.

 

[Kiran36]

Yeah, there was something corrupted idk if was the sd card or the emuNAND but I formated it and everything works just fine, thanks everyone

 

[guily6669]

Can anyone please share a link for a trusted compiled Fusee.bin with sigpatches support??

I want to continue to use Hekate Fusee payload method and don't want to use sys-patch either...

I'm currently using Atmos 1.7.0 for beta testing EOS 1.2 with Erista CPU UV support with FSS0 but when FW 18 games start coming out I plan to stay on FW 17.0.1 if they can still play them fine while using fusee payload which doesn't work with hekate FSS0...

ps: However I see a tut on to move to atmos 1.7.0 and they just use Hekate Fusee payload and their sigpatches still are the same usual atmos sigpatches like from many time ago but just updated with FW18 and atmos 1.7.0 values, I'm not even understanding cause the fusee link they provide is for the original download from atmosphere github, not modded...