Assistance with CFW Update + Patches etc

[Wayno1337]

Hello friendly and helpful CFW Community!

Long timer lurker here, decided this time to register and make a post asking for some assistance as I cant seem to figure out where I am going wrong.

I have recently updated to OFW 18.1.0 Atmosphere 1.9.1 Hekate 6.3.1 Nyx 1.7.0

However, it seems like the sigpatches/patching scenario has changed since I last updated and I am at a loss to what the correct approach is for my current setup:

OFW: 18.1.0
Atmosphere: 1.9.1
Hekate 6.3.1
Nyx 1.7.0
I am pretty sure I am using SysMMC. My current system version in settings reads as: Current system version: 18.1.0|AMS 1.9.1|S

First I attempted to update my old setup manually but due to too many outdated sysmodules etc, I was unable to boot and instead of spending a lot of time figuring out what the cause was, I ended up using the HATS pack and then modified it a bit to remove a few things I did not want.

However even though most things seem to be working all good and as intended, it seems my sigpatches + sys-patch setup is incorrect and I am at a loss to which sigpatches to use or if they can be completely removed and instead use sys-patch.

I have tried the most recent sigpatches I can find on the main thread here on GBAtemp, no luck.
I have tried sys-patch on its own, no luck.
both together, no luck.
I cant remember what happened in either scenario but either I could not boot at all or successfully booted with no change to my situation where some more recent games / updated titles wont load.


Sys-patch overlay shows the following: (some patched, some unpatched)

my hekate_ipl.ini reads as follows:
[config]
autoboot=2
autoboot_list=0
bootwait=2
verification=1
backlight=100
noticker=0
autohosoff=2
autonogc=1
updater2p=1
bootprotect=0

[Stock SysNAND]
pkg3=atmosphere/package3
stock=1
emummc_force_disable=1
icon=bootloader/res/stock.bmp
usb3force=1


[CFW (SYSMMC)]
pkg3=atmosphere/package3
kip1patch=nosigchk
emummc_force_disable=1
icon=bootloader/res/sysnand.bmp
usb3force=1

I kindly request the assistance of anyone knowledgeable within the CFW community that can potentially highlight where I have gone wrong.

- Am I chain loading / booting incorrectly for my setup?
- is my hekate_ipl.ini configured incorrectly?
- Am I required to use a specific version of Sys-Patch? Does it need to be manually configured or just drag and drop?
- Am I required to use a specific version of sigpatches to match my OFW + Atmosphere combo as well as the way I boot?
- Does Sys-patch require some kind of configuration that I have missed?

When I search and look into the above, I keep coming up with either conflicting or outdated information and I am now confused as to what the correct approach is. Some things suggest I can simply remove all the old sigpatches and use the latest Sys-patch however that did not work for me so I am wondering if my hekate config is incorrect or if it something else I am doing wrong.

- Also on a related note, did I make the right choice sticking with 18.1.0 for now or should I consider upgrading to 19.x?

- One final question, if I were to drag, drop and overwrite with the latest Atmosphere released a few days ago, would I need to reconfigure anything else?


Thanks in advance to anyone who takes the time to assist me <3

 

[thesjaakspoiler]

Sigpatch files do work on the latest FW but the sys-patch module makes life easier.
I'm not sure when the sys-patch module was introduced and if it has some minimum requirement.

If you used the sigpatch files, did you add the sigpatches for Hekate in the bootloader folder and the ones for Atmosphere in the atmosphere folder?
Both have their own sigpatch data.

If you are using a Mac, try the Hekate option to fix the archive bit.
Macs do have the habit to set that flag and this makes files invisible for the Switch.
Not sure if the same happens with a PC.

 

[Wayno1337]

I have added the sigpatches to the correct locations, however I am not sure if I am using the correct ones for my setup or if a specific set of sigpatches are required for my OFW + CFW versions.

I am using a windows PC. I tried the archive bit thing, no fix.

Thanks for chiming in, anyone else? <3

 

[UsernamesAreWeird]

Get rid of sigpatches and let Sys-Patch do its thing

 

[Wayno1337]

Get rid of sigpatches and let Sys-Patch do its thing

Unfortunately this not not working correctly for me. As I mentioned, only some patching is happening and others are not, as shown in the pictures.

The majority of titles will launch and run correctly but some will not.

I feel like I've got to configure something slightly differently? Like perhaps the way I am loading initially or a specific version of Sys-patch or some other kind of config I have missed?

Surely one of you hardcore modders may know exactly what my issue is

 

[UsernamesAreWeird]

Like I said, removing sigpatches should resolve the issue

 

[impeeza]

Sigpatch files do work on the latest FW

That is false, the firmware have nothing to do with non working patches, they do not work on plain official atmosphère because SciresM removed the KIP patches loading. BUT IF YOU USE HEKATE PKG3 (FS0) loading or a custom Atmosphère with patches loading reenabled, THEY WILL WORK.

but, yes for the noob user SYS-Patch sysmodule is the best.

Post automatically merged: Jul 20, 2025

Unfortunately this not not working correctly for me. As I mentioned, only some patching is happening and others are not, as shown in the pictures.

The majority of titles will launch and run correctly but some will not.

I feel like I've got to configure something slightly differently? Like perhaps the way I am loading initially or a specific version of Sys-patch or some other kind of config I have missed?

Surely one of you hardcore modders may know exactly what my issue is

all the patches you have enabled ARE WORKING, please READ THE DOCUMENTATION of the SYS-Patch green means patched by sys-Patch Sysmodule, Orange means ALREADY PATCHED, and disabled is YOUR DO NOT ENABLED THAT PATCHES, if you know what they are and like to enable, ENABLE THEM ON THE CONFIGURATION.

 

[Wayno1337]

Like I said, removing sigpatches should resolve the issue

Like I said in the original post "I have tried sys-patch on its own, no luck." then I told you again its not working correctly for me, elaborating on what is happening.

That is false, the firmware have nothing to do with non working patches, they do not work on plain official atmosphère because SciresM removed the KIP patches loading. BUT IF YOU USE HEKATE PKG3 (FS0) loading or a custom Atmosphère with patches loading reenabled, THEY WILL WORK.

but, yes for the noob user SYS-Patch sysmodule is the best.

Post automatically merged: Jul 20, 2025

all the patches you have enabled ARE WORKING, please READ THE DOCUMENTATION of the SYS-Patch green means patched by sys-Patch Sysmodule, Orange means ALREADY PATCHED, and disabled is YOUR DO NOT ENABLED THAT PATCHES, if you know what they are and like to enable, ENABLE THEM ON THE CONFIGURATION.

So what you are telling me is that:
noncasigchk_new UNPATCHED
nocntchk UNPACHED

Is correct and how it should look?

Straight from the Sys-Patch readme:

• Unpatched means the patch wasn't applied (likely not found).
• fs and es need new patches after every new firmware version.

So far I have only been told to do this or do that even though my original post stated that I have already attempted these things.

Perhaps someone that actually has an idea what might actually be happening here instead of just telling me to do what I have already done

Post automatically merged: Jul 20, 2025

Update:

I was reading these threads (new account on GBAtemp wont let me post links)
games-not-starting-up-with-20-1-0.672051/
updated-switch-from-16-to-20-however-i-get-an-error-when-booting-failed-to-apply-nosigchk.672056/

Then I noticed "kip1patch=nosigchk (REMOVE THIS LINE FOR SYS-PATCH)" and another comment on the second thread "Remove kip1patch=nosigchk from hekate.ipl.ini."

I had a feeling this might change things and surely enough now my Sys-Patch Overlay shows:

I attempted to remove the sigpatches completely by removing the following file and folders:

/bootloader/patches.ini
/atmosphere/kip_patches/
/atmosphere/exefs_patches/

I was then met with this on boot:

After a little digging I discovered that the following folders don't seem to be part of or included with the Sigpatches zips and it unlikely wasn't booting due to deleting these folders, especially the one related to my theme.

Sorted that out, now booting fine with sigpatches completely removed.
Sys-Patch looks healthy - All types of patching showing 'Patched' in Green.

HOWEVER:
If I do the updates to the titles listed here, they do not launch and give an error 'software unexpectedly closed'.

Also, if I try to download and run the latest version of LEGO Horizon Adventures, the game will run fine at first but after a reboot, it will no longer load and states 'Checking if the software can be played...'

I also tried to download a more recent game with the latest update & DLC - The Legend of Zelda: Echoes of Wisdom, but unfortunately it just does not load and gives the software unexpectedly closed error.

I am currently using Tinfoil.

Any advice would be greatly appreciated

 

[UsernamesAreWeird]

If I do the updates to the titles listed here, they do not launch and give an error 'software unexpectedly closed'.

Yes, this can happen when moving from sigpatches to sys-patch

Just reinstall the games that don't work

Also, if I try to download and run the latest version of LEGO Horizon Adventures, the game will run fine at first but after a reboot, it will no longer load and states 'Checking if the software can be played...'

This is a ticket issue, DBI installer can fix it, you'll keep having issues like these if you keep using tinfoil

And please don't mention the names of "shops"/warez sites, it is against the rules

I also tried to download a more recent game with the latest update & DLC - The Legend of Zelda: Echoes of Wisdom, but unfortunately it just does not load and gives the software unexpectedly closed error.

Again, could be an issue with tinfoil (wouldn't surprise me in the slightest) or it could be that the game requires a more up to date firmware (19.0.1)

 

[Wayno1337]

Yes, this can happen when moving from sigpatches to sys-patch

Just reinstall the games that don't work

This is a ticket issue, DBI installer can fix it, you'll keep having issues like these if you keep using tinfoil

And please don't mention the names of "shops"/warez sites, it is against the rules

Again, could be an issue with tinfoil (wouldn't surprise me in the slightest) or it could be that the game requires a more up to date firmware (19.0.1)

I have attempted to reinstall several of the games that don't launch after switching to Sys-patch and I still get the same error.

When you say DBI installer can fix it, how so? What function am I looking for within DBI?

My bad mentioning the name of an eShop, I figured mentioning it was relevant in case they were potentially known to have broken installs or something along those lines, not mentioning the direct links or info required to use it, I assumed that would be fine.

I appreciate you attempting to help but honestly your 'should' and 'could' responses don't really tell me anything definitive.

I was really hoping that someone with definitive knowledge or information would chime in, so far its been:
- try doing this (even though I already stated I had already attempted it)
- nah for real, like I said, do this thing you have already done, it 'should' fix the issue.
- again (even thought it was never actually mentioned a first time) it 'could' be this or 'could' be that.

Honestly, all you have said is:
- 'do what you have already done'
- 'like I said, do what you have already done it 'should' work'
- 'This is the issue. This can fix it. But I cbf elaborating what-so-ever as to how, figure it out on your own'
- 'like I said, do what I apparently have already told you to do but actually didn't, it 'should' fix it.'
- 'or it 'could' be this, like you were already wondering and asking, but I am just guessing at this point'

Are you just farming up your post count on this forum?

Please don't reply to this thread with any more 'it worked for me so it should work for everyone else' or 'I told you before but I actually didn't, it 'could' be this or 'could' be that, without any elaboration what-so-ever.

When people like yourself repeatedly reply, it causes others to not even read the forum post assuming with several replies the issue has already been resolved.

Please, someone that actually has a real idea what might be going on or some definitive information, id greatly appreciate some expert advice <3

 

[Nephiel]

You need to determine what is causing the issues you're having. Here's what I would do:

• Delete the log file /config/sys-patch/log.ini, then reboot the console, and then check the log using sys-patch overlay again. If it still shows Patched in green for all except disablecaverification... ones, then you can be sure sys-patch is working fine.

If the issue persists, Tinfoil itself may be the cause:

• Tinfoil shops can be unreliable, dump or source a backup of your game from somewhere else, to rule out a bad dump.
• Tinfoil as an installer is known to cause issues like these with temporary tickets. Reinstall your game using the latest version of DBI to rule that out.

 

[browntigerz]

Does everything have to say patched, im on an oled switch. All my games are working but the top one says unpatched and im using sys patch. Also I believe i didn’t remove the line from heteke.ini, should i do that if im using sys patch?

 

[Wayno1337]

You need to determine what is causing the issues you're having. Here's what I would do:

• Delete the log file /config/sys-patch/log.ini, then reboot the console, and then check the log using sys-patch overlay again. If it still shows Patched in green for all except disablecaverification... ones, then you can be sure sys-patch is working fine.

If the issue persists, Tinfoil itself may be the cause:

• Tinfoil shops can be unreliable, dump or source a backup of your game from somewhere else, to rule out a bad dump.
• Tinfoil as an installer is known to cause issues like these with temporary tickets. Reinstall your game using the latest version of DBI to rule that out.

Thank you so much for this informative post. I have did as you said and confirmed Sys-Patch is working fine.

I agree with your advice regarding Tinfoil or a bad dump potentially being the issue.
When I get a chance, I will do as you said using DBI or an alternative method.

Post automatically merged: Jul 22, 2025

Does everything have to say patched, im on an oled switch. All my games are working but the top one says unpatched and im using sys patch. Also I believe i didn’t remove the line from heteke.ini, should i do that if im using sys patch?

Remove the line from your hekate_ipl_ini file that calls the sigpatches and remove them completely. (Be careful not to remove patches related to Nxthemes installer if you use it and bluetooth etc) Download the sigpatches patch as a reference for what folders and files to delete if you need to. Backup whatever you plan to delete first, in case of an issues you can simply revert back.

Then reboot, you should be fully patched using Sys-Patch instead.

 

[nitrozz]

Install last sigpatch and syspatch
Don’t remove kip1patch=nosigchk
Reboot
If you get noncasigchk_new = unpatched is not realy important

 

[Deleted member 702243]

I also tried to download a more recent game with the latest update & DLC - The Legend of Zelda: Echoes of Wisdom, but unfortunately it just does not load and gives the software unexpectedly closed error.

echoes of wisdom 1.1.0 uses sdk 20 and probably requires firmware 20 or higher