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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,247,798
  • Replies Replies 7,350
  • Likes Likes 266
what says the OP?
By the way, thank you for always keeping OP updated with the latest patches and info.

I don't follow the scene as much like before but i appreciate being able to the get the latest reliable info about patches every time there is a new update.
 
I got confused. Who published a custom package3 patches?
This thread moved quite quickly. I just wanted to point that out after seeing a couple of people go back and forth about patches being different. I automatically assume that one of them built a custom fusee, then used their own package3 with IPS_Patch_Creator. Just a guess.
 
This thread moved quite quickly. I just wanted to point that out after seeing a couple of people go back and forth about patches being different. I automatically assume that one of them built a custom fusee, then used their own package3 with IPS_Patch_Creator. Just a guess.
Yeah everything is a light speed. That's why I got confused
 
  • Like
Reactions: Blythe93
Hello, at work, WiFi requires authorization by phone number with an activation code, otherwise you will not be able to open the pages in the browser. Writes an error with certificates. Firmware 19.0.1
 
is ther a way to completely uninstall the patches? it's getting kinda annoying to have to press power every time i reboot from payload
 
Delete the folders that will remove them. How patches are interfering with reboot?
"failed to apply 'nosigchk'!" every time i reboot from payload
i should say that i have NOT updated to the current beta patches, i would rather wait for the full release
 
"failed to apply 'nosigchk'!" every time i reboot from payload
i should say that i have NOT updated to the current beta patches, i would rather wait for the full release
That is a Hekate error saying you have NOGC set on Hekate_ipl.ini but no patches.ini content for the current firmware, or remove NOGC or upgrade patches.ini.
 
  • Like
Reactions: Blythe93
Anyone have any battery drain issues on sleep mode? My switch oled with hwfly suddenly experience this. I'm not sure if it's the update or if it's because I left my switch powered off for a while before playing it again
 
Anyone have any battery drain issues on sleep mode? My switch oled with hwfly suddenly experience this. I'm not sure if it's the update or if it's because I left my switch powered off for a while before playing it again
Known issue. Apparently it stared sometime when 18.x.x was introduced and now it's even more present on 20.x.x. From what I've gathered, it's caused by console trying to fetch new EULA for your account to accept while constantly being blocked by 90DNS or similar. There are a couple of workarounds for this like staying offline or in airplane mode, removing all real NNIDs from your profiles (not sure if this actually fixes the issue), creating a new emuNAND from an updated sysNAND where EULA has been agreed to, etc.

I personally have no real NNIDs linked to any of my profiles (except from the fake ones linked by linkalho) and I'm yet to run into that issue on my emuNAND.
 
Known issue. Apparently it stared sometime when 18.x.x was introduced and now it's even more present on 20.x.x. From what I've gathered, it's caused by console trying to fetch new EULA for your account to accept while constantly being blocked by 90DNS or similar. There are a couple of workarounds for this like staying offline or in airplane mode, removing all real NNIDs from your profiles (not sure if this actually fixes the issue), creating a new emuNAND from an updated sysNAND where EULA has been agreed to, etc.

I personally have no real NNIDs linked to any of my profiles (except from the fake ones linked by linkalho) and I'm yet to run into that issue on my emuNAND.
Thanks, let me disable WiFi and will test

Edit: yes that's fixed it. Thanks so much for info
 
Last edited by Jajabinx,
  • Like
Reactions: Blythe93
Will (SYS-TWEAK) Get any update for FW20??
Post automatically merged:

Will (SYS-TWEAK) Get any update for FW20??
 
Will (SYS-TWEAK) Get any update for FW20??
Post automatically merged:

Will (SYS-TWEAK) Get any update for FW20??
To be perfectly real with you, read the atmosphere changelog.
Code:
Please note: As a result of changes made to nintendo's software in 20.0.0, there is roughly 10MB less memory available for custom system modules.

    We can only steal a maximum of 14MB from the applet pool, down from 40MB.


You shouldn't be using sysmodules anymore. (*) If you want to keep using them, downgrade to 18.1.0, as 19.0.x+ also has reduced memory available, though not as severe as 20.0.x+ has.

not even the overlayloader, all bloat consuming memory you do not have available, of the 14MB pool emummc as example, eats 8MB of that, so you have 6MB pool in 20.0.0+

*: can use sys-patch, or homebrew that in general exit memory after boot. afaik no other sysmodules that don't operate after boot do this properly, other than sys-patch.
 
hi has anyone encountered issue after the recent update of zelda botw 1.8.0 and totk 1.4.0? Both game stucks with the loading switch logo while wisdom of echoes simply says error and would not load at all. I've tried the base game/dlc/previous updates and they all work fine. Could it be the sigpatch issue? But I am already using the latest sigpatch 1.5.6 and system on 19.0.1/ ams 1.8.0. Anybody pls kindly advise. thanks..
 
Known issue. Apparently it stared sometime when 18.x.x was introduced and now it's even more present on 20.x.x. From what I've gathered, it's caused by console trying to fetch new EULA for your account to accept while constantly being blocked by 90DNS or similar. There are a couple of workarounds for this like staying offline or in airplane mode, removing all real NNIDs from your profiles (not sure if this actually fixes the issue), creating a new emuNAND from an updated sysNAND where EULA has been agreed to, etc.

I personally have no real NNIDs linked to any of my profiles (except from the fake ones linked by linkalho) and I'm yet to run into that issue on my emuNAND.
Update, the problem has been solved:
I'll leave the post up for someone that might need it:
The issue was solved by renaming the "atmosphere/contents" folder to "oldcontents", then, by excluding things, I found out that the issue was the "0000000000534C56" folder which was SaltyNX.

Hi, sorry for bothering, any idea why softwares doesn't start up anymore?

I regularly updated:
- Atmosphere to 1.9.1 + fusee.bin
- Hekate to the v6.3.1
- Changed hekate_ipl.ini (changed fss0 to pkg3 + removed kip1patch=nosigchk, .ini in the bottom)
- Replaced sigpatches (deleted patches.ini, kip and exfs folders) with sys-patch 1.5.6

I've tested new sigpatches aswell with the modified fusee.bin, no effect whatsoever, same issue...

Sys-patch shows 'noncasigchk_new, nocntchk2, noacidsigchk, es3, ctest2, nim and disablecaverification1/2/3' all Patched in green, but, only a couple games actually works without giving the error: "The software was closed because an error occurred".
 
Last edited by UsualVII,
hi all, havent posted here in years, back in the wii days afaik.
Struggling with an AIO solution, as the ALL say tinfoil (e.g.) has corrupted data
is anyone allowed to post to a link to a premade AIO?
I have tried deepsea (github), and a french one (Switch_AIO_LS_pack_5.18.0_-_firmware_20.1.0_-_Atmosphere_1.9.1_-_Hekate_6.3.1)

in the old days is was the sdsetup site and SO easy ! then jits worked great !

i have 2 of the OG swtict using jigs ans 256gb sandisks, and neither seem happ runnig games any more!
tried the modded fusee.bin too, from 30th May above
tried going to hekate, then payload orginal fusee (from latest atmosphere) and that modded one
---
btw - i thought corruption was me in hekate creating an emunand (file based, FAT32, no exfat !) and it complaing about the original os of 15.0ish
then i've updated the emunand to 19.xx (and on another attempt 20.xx)
and still the corruption :(
 
Last edited by xakamd,

Site & Scene News

Popular threads in this forum