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

  • Thread starter Thread starter ShadowOne333
  • Start date Start date
  • Views Views 5,306,580
  • Replies Replies 7,368
  • Likes Likes 266
whats the best firmware to update to at this point in time with regards to homebrew being updated for overclocking? I'm still on 18.x.x . Not been on my switch for a while. There's some new titles i'd like to try out but they need 20.x.x firmwares. Thanks
 
Last edited by KungFuzion,
whats the best firmware to update to at this point in time with regards to homebrew being updated for overclocking? I'm still on 18.x.x . Not been on my switch for a while. There's some new titles i'd like to try out but they need 20.x.x firmwares. Thanks
Unless a software, app or game needs you to upgrade there is no need to upgrade your firmware, if you are going to upgrade you need to consider if you need big mods because on FW 19 and 20 the available memory for homebrew was reduced.

most of overclock systemmodules has been upgraded to FW 20 so you can upgrade up to 20.4.0.
 
  • Like
Reactions: Blythe93
why do you need the console not going to sleep if you leave on the dock unused?
I switched off the Switch first, then put it in the dock for charging.
I prefer it to be kept on switched off instead of in sleep mode because there may be a hot charging problem in sleep mode.
Is the any way to do so?

On the other hand, I just find that there is a translated latest DBI released for everyone in need. :lol:
 
Last edited by johnliu,
Since sometimes it will have hot charging problem in sleep mode, that's why I prefer it to be switched off when charging.
Neither using the chipNX R0.31/0.32 firmware nor spacecraft v0.2.0 will help, a switched off Switch will still goes to sleep mode when charging in dock.
I don't want to reinstall everything from the beginning to solve the hot charging problem again. It is very time consuming and the hot charging problem will eventually comes back sometimes after Switch firmware updates.
If the Switch is kept on switched off during charging, there will be no hot charging problem.

May be using back the temporary methods to keep it switched off when charing.:
1. halfly put it in dock, switch it off and put it in the dock immediately.
OR
2. switch it off during charging.
 
Last edited by johnliu,
Since sometimes it will have hot charging problem in sleep mode, that's why I prefer it to be switched off when charging.
Neither using the chipNX R0.31/0.32 firmware nor spacecraft v0.2.0 will help, a switched off Switch will still goes to sleep mode when charging in dock.
I don't want to reinstall everything from the beginning to solve the hot charging problem again. It is very time consuming and the hot charging problem will eventually comes back sometimes after Switch firmware updates.
If the Switch is kept on switched off during charging, there will be no hot charging problem.

May be using back the temporary methods to keep it switched off when charing.:
1. halfly put it in dock, switch it off and put it in the dock immediately.
OR
2. switch it off during charging.
Solution to that in


 
Unless a software, app or game needs you to upgrade there is no need to upgrade your firmware, if you are going to upgrade you need to consider if you need big mods because on FW 19 and 20 the available memory for homebrew was reduced.

most of overclock systemmodules has been upgraded to FW 20 so you can upgrade up to 20.4.0.
Thanks for your reply. It's mainly for new games and with overclock systemmodules being upgraded I may as well. I read through the release note that memory had been reduced for homebrew etc.
Post automatically merged:

I switched off the Switch first, then put it in the dock for charging.
I prefer it to be kept on switched off instead of in sleep mode because there may be a hot charging problem in sleep mode.
Is the any way to do so?

On the other hand, I just find that there is a translated latest DBI released for everyone in need. :lol:
I heard a while ago he added bricking code if anyone decided to tamper with the code? If this is true or not remains to be seen?
 
Last edited by KungFuzion,
  • Love
Reactions: impeeza
Remove pretty much everything that's usually included in sigpatches archive file i.e.:
  • folders es_patches, nfim_ctest and nim-prodinfo-blank-fix from the atmosphere/exefs_patches folder.
  • folders fs_patches and loader_patches from the atmosphere/kip_patches folder.
  • patches.ini file from the bootloader folder.
That should be it. Don't forget to reboot afterwards after you install the latest sys-patch (simply drag and drop).

In any case, I've just updated my CFW (firmware, Atmosphere, Hekate, sys-patch, MissionControl and a couple of other apps) and from what I can tell everything still works just fine. The only issue I run into was that my Switch rebooted on first boot right after the Switch logo. The second time it booted properly.
After doing this, should I turn the sys-patch = On at sysmodules?
I already had sys-patch in my switch SD, but it was sys-patch = off at sysmodules.
Ah, remove the kip1patch=nosigchk line from your hekate_ipl.ini file and reboot.
I was getting the "failed to apply nosigchk" error and just removed it from the hekate_ipl.ini file like you said here but didnt removed some folders you said above.


I actually don't quite understand what sigpatches or sys-patches are for at this point. Shouldn't they be used for unsigned apps or games?

The sys-patch config.ini is on default, I didn't change anything in it.

This is my sys-patch log file:
[options]
patch_sysmmc=1
patch_emummc=1
enable_logging=1
version_skip=1
[fs]
noacidsigchk1=1
noacidsigchk2=1
noncasigchk_old=1
noncasigchk_new=1
noncasigchk_new2=1
nocntchk_old=1
nocntchk_new=1
nocntchk=1
nocntchk2=1
[ldr]
noacidsigchk=1
[es]
es1=1
es2=1
es3=1
es4=1
es5=1
es6=1
[nifm]
ctest=1
ctest2=1
[nim]
nim=1
[ssl]
disablecaverification1=0
disablecaverification2=0
disablecaverification3=0

 
Last edited by gutoblauth,
  • Love
Reactions: impeeza
After doing this, should I turn the sys-patch = On at sysmodules?
sys-patch does its thing on boot and then turns off. There's no need to turn it on afterwards. Just make sure that whenever you update it to reboot afterwards.

I was getting the "failed to apply nosigchk" error and just removed it from the hekate_ipl.ini file like you said here but didnt removed some folders you said above.
That's fine but I personally prefer to keep my SD card setup as tidy as possible.

I actually don't quite understand what sigpatches or sys-patches are for at this point. Shouldn't they be used for unsigned apps or games?
Among other things, yeah.

The sys-patch config.ini is on default, I didn't change anything in it.
It should work just fine. Since I'm using emuMMC only, I've disabled the patch on sysMMC and enabled whichever patch wasn't turned on by default. I'm yet to run into an issue on my Switch so far.
 
sys-patch does its thing on boot and then turns off. There's no need to turn it on afterwards. Just make sure that whenever you update it to reboot afterwards.


That's fine but I personally prefer to keep my SD card setup as tidy as possible.


Among other things, yeah.


It should work just fine. Since I'm using emuMMC only, I've disabled the patch on sysMMC and enabled whichever patch wasn't turned on by default. I'm yet to run into an issue on my Switch so far.
Thank you. When you say to reboot, you mean the HOS, the emuMMC/sysMMC, right? I actually go to Hekate very often, so basically I can restart to it and then boot whatever emuMMC or sysMMC, both cfw.

Does the sys-patch prevent burning fuses when updating sysMMC thought cfw? Or do you know what actually does that? Everytime i did update my Switch, I downloaded the update just by hitting update over official switch prompts or menu update, over SysCFW, and ever since my Switch won't burn fuses anymore. I just want to prevent my EmuMMC to break when I eventually update my SysMMC.

I actually never use stock, even when going online. I just dont do shady stuff when on SysCFW. I use jailbreak features of the SysCFW just for updating without burning fuses and to reboot to Hekate easly, since I use a V1 unpatched erista

PLEASE READ THE OP OF THIS THREAD, EVERYTHING YOU AR ASKING IS ANSWERED THERE!! EVERYTHING!
To much cluttered information + people over old posts saying to move to sys-patches + sigpatches being updated ramdomly afterwards + my switch working fine even without sig-patches working or even in the hekate ini file... all of this got me confused by alot
 
  • Like
Reactions: Blythe93
Does the sys-patch prevent burning fuses when updating sysMMC thought cfw?
NO THAT IS JOB OF ATMOSPHÈRE.
Post automatically merged:

Thank you. When you say to reboot, you mean the HOS, the emuMMC/sysMMC, right? I actually go to Hekate very often, so basically I can restart to it and then boot whatever emuMMC or sysMMC, both cfw.

Does the sys-patch prevent burning fuses when updating sysMMC thought cfw? Or do you know what actually does that? Everytime i did update my Switch, I downloaded the update just by hitting update over official switch prompts or menu update, over SysCFW, and ever since my Switch won't burn fuses anymore. I just want to prevent my EmuMMC to break when I eventually update my SysMMC.

I actually never use stock, even when going online. I just dont do shady stuff when on SysCFW. I use jailbreak features of the SysCFW just for updating without burning fuses and to reboot to Hekate easly, since I use a V1 unpatched erista


To much cluttered information + people over old posts saying to move to sys-patches + sigpatches being updated ramdomly afterwards + my switch working fine even without sig-patches working or even in the hekate ini file... all of this got me confused by alot
You should move your questions to https://gbatemp.net/threads/switch-noob-paradise-ask-questions-here.488277/page-2345#post-10725138 that thread is the discord on the forum for the ones not willing to read.
 
You should move your questions to https://gbatemp.net/threads/switch-noob-paradise-ask-questions-here.488277/page-2345#post-10725138 that thread is the discord on the forum for the ones not willing to read.
I've been in this thread before and was trash. People who was supposedly helping did a really bad job, someone who's name starts with Draco or Drago-something as I remember. Also I did read, not my fault if infos for this are all cluttered and misleading, if it wasnt, not many people would be struggling with it.
 
When you say to reboot, you mean the HOS, the emuMMC/sysMMC, right? I actually go to Hekate very often, so basically I can restart to it and then boot whatever emuMMC or sysMMC, both cfw.
Yep, that's correct. That's how I do it as well, reboot to Hekate and back to CFW.
 
  • Like
Reactions: Blythe93
I'm still using FW18. What games require higher FW besides DKC Returns HD? That's the only thing I'm interested in, but I don't think there's any point in updating just one game if everything else works.
 

Site & Scene News

Popular threads in this forum