Hacking Sigpatches for Atmosphere (Hekate, fss0, fusee & package3)
- Thread starter ShadowOne333
- Start date
- Views 2,150,045
- Replies 3,335
- Likes 245
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
not sure what cat sit refer to, but eh, i thought the project was dead due to the recent dmca
and here on the sys-patch thread there is a link to: https://gitflic.ru/project/impeeza/sys-patch/release
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.
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?
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.
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
Last edited by urherenow,
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.
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
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...Still freezes at the logo
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.
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...
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...
Last edited by guily6669,
Similar threads
it! 
..............................