Homebrew Homebrew app sys-patch - sysmod that patches on boot

[paulinodp]

Hello when trying to start cfw emummc with the new files in 21.2.0 of Atmosphere gives me this failure, although then I give the power button and it continues everything perfectly, but I would like to know how to solve that problem so that this message does not come out anymore please. Thank you for the help beforehand.

 

[froggy55]

Can you read?

The official Atmosphère repository had been updated some hours ago

yes i found it right after posting. my bad

 

[BigOnYa]

Hello when trying to start cfw emummc with the new files in 21.2.0 of Atmosphere gives me this failure, although then I give the power button and it continues everything perfectly, but I would like to know how to solve that problem so that this message does not come out anymore please. Thank you for the help beforehand.

https://github.com/impeeza/sys-patch/releases/tag/v1.5.9 Unzip this .zip file, copy the files to root of your sd card, reboot Switch.

 

[bth]

https://github.com/impeeza/sys-patch/releases/tag/v1.5.9 Unzip this .zip file, copy the files to root of your sd card, reboot Switch.

if you look at his picture, his thing says he's booting with hekate pkg3/fss0 method, and have the .nosigchk line in his hekate_ipl.ini

adding sys-patch wont fix that, he has to edit his configuration, and remove the lines that say nosigchk

 

[paulinodp]

if you look at his picture, his thing says he's booting with hekate pkg3/fss0 method, and have the .nosigchk line in his hekate_ipl.ini

adding sys-patch wont fix that, he has to edit his configuration, and remove the lines that say nosigchk

if you look at his picture, his thing says he's booting with hekate pkg3/fss0 method, and have the .nosigchk line in his hekate_ipl.ini

adding sys-patch wont fix that, he has to edit his configuration, and remove the lines that say nosigchk

Hello, if it is correct I am not caring about that failure, I will see if I am able to correct those lines that you comment on me in the hekate_ipl.ini and see if it is solved. thanks

Post automatically merged: Jan 14, 2026

if you look at his picture, his thing says he's booting with hekate pkg3/fss0 method, and have the .nosigchk line in his hekate_ipl.ini

adding sys-patch wont fix that, he has to edit his configuration, and remove the lines that say nosigchk

Hello, I try to remove what you tell me about hekate_ipl.ini but it keeps failing me but now with another different message, I can contact you on telegram and pass you my pack and you make me a hand please?? thanks for everything you contribute

 

[bth]

Hello, I try to remove what you tell me about hekate_ipl.ini but it keeps failing me but now with another different message, I can contact you on telegram and pass you my pack and you make me a hand please?? thanks for everything you contribute

no thanks.

the only "pack" i support is combining these three:
https://github.com/Atmosphere-NX/Atmosphere/releases/latest
https://github.com/CTCaer/hekate/releases/latest
https://github.com/impeeza/sys-patch/releases/latest

i will not, ever, provide support for problems someone else create.


delete folder on sd card /atmosphere
replace with new of everything by combining the three above.
done.

 

[paulinodp]

no thanks.

the only "pack" i support is combining these three:
https://github.com/Atmosphere-NX/Atmosphere/releases/latest
https://github.com/CTCaer/hekate/releases/latest
https://github.com/impeeza/sys-patch/releases/latest

i will not, ever, provide support for problems someone else create.


delete folder on sd card /atmosphere
replace with new of everything by combining the three above.
done.

ok, thank you so much for everything, try to fix it as you can. a hug

 

[impeeza]

@impeeza

Recommend update to Sys-patch, add function to check the current firmware version:
Example working (tested) function:

int getFirmwareVersionInt() {
    SetSysFirmwareVersion firmware;
    Result rc = setsysGetFirmwareVersion(&firmware);
  
    if (R_FAILED(rc)) {
        return -1;
    }
  
    // Convert to integer format: major * 1000 + minor * 100 + micro
    // Example: 12.0.1 -> 12001, 16.1.0 -> 16100, 17.0.0 -> 17000
    return (firmware.major * 1000) + (firmware.minor * 100) + firmware.micro;
}

Example Use like this:

int fwVersion = getFirmwareVersionInt();
if (fwVersion == 21000){
---add code here to set patches
}

Next add menu item to set recommended patches based on detected firmware running. This should be very easy to implement and would help some newer users select the correct patches to use.

Hello there you are welcome to make a PR on the Repository

 

[bth]

Hello there you are welcome to make a PR on the Repository

he doesn't know how to use git, and the suggestion you responded to are from november, back when he was obviously ai generating all his code with zero knowledge of how things actually works.

 

[impeeza]

he doesn't know how to use git, and the suggestion you responded to are from november, back when he was obviously ai generating all his code with zero knowledge of how things actually works.

yeah, was part of the sarcasm.

 

[korn16ftl3]

ok so its been a while since I've done the switch CFW thing so I'm a bit out of the loop.

i have been able to update my v1 switch to atmosphere 1.10.2 and hekate 6.5.1 Nyx 1.9.1 along with a partition based emuMMC on FW 20.5.0

are these the correct syspatchs i want to apply to my SD card:
https://github.com/impeeza/sys-patch/releases/tag/v1.5.9

i also see these syspatches but I'm uncertain what files i need from here as there isn't a drag and drop zip file:
https://github.com/impeeza/sys-patch

is it still recommended as i have read to also run sigpatches as well as the syspatchs or does that not matter as much anymore?

sorry for being so out of touch with the scene and thank you all in advance for helping me put the last bit that I'm having a hard time understanding back together

 

[AllOver]

ok so its been a while since I've done the switch CFW thing so I'm a bit out of the loop.

i have been able to update my v1 switch to atmosphere 1.10.2 and hekate 6.5.1 Nyx 1.9.1 along with a partition based emuMMC on FW 20.5.0

are these the correct syspatchs i want to apply to my SD card:
https://github.com/impeeza/sys-patch/releases/tag/v1.5.9

i also see these syspatches but I'm uncertain what files i need from here as there isn't a drag and drop zip file:
https://github.com/impeeza/sys-patch

is it still recommended as i have read to also run sigpatches as well as the syspatchs or does that not matter as much anymore?

sorry for being so out of touch with the scene and thank you all in advance for helping me put the last bit that I'm having a hard time understanding back together

syspatch, not syspatches.

The first link you posted has a zip.

Sigpatches aren't needed anymore.

 

[impeeza]

ok so its been a while since I've done the switch CFW thing so I'm a bit out of the loop.

i have been able to update my v1 switch to atmosphere 1.10.2 and hekate 6.5.1 Nyx 1.9.1 along with a partition based emuMMC on FW 20.5.0

are these the correct syspatchs i want to apply to my SD card:
https://github.com/impeeza/sys-patch/releases/tag/v1.5.9

i also see these syspatches but I'm uncertain what files i need from here as there isn't a drag and drop zip file:
https://github.com/impeeza/sys-patch

is it still recommended as i have read to also run sigpatches as well as the syspatchs or does that not matter as much anymore?

sorry for being so out of touch with the scene and thank you all in advance for helping me put the last bit that I'm having a hard time understanding back together

syspatch, not syspatches.

The first link you posted has a zip.

Sigpatches aren't needed anymore.

Sigpatches are small IPS files for patching the memory at boot time.

Sys-Patch is a sysmodule which run at system start and patches the memory.

Booth make the same, can be complementary. or you can use one or another.

 

[bth]

(this is not a full release, it's a pre-release / testing version)


version 1.6.0 contains some refactoring and compatability with latest set of libnx commit relating to DebugEventInfo

https://github.com/impeeza/sys-patch/compare/master...borntohonk:sys-patch:master
https://github.com/borntohonk/sys-patch/releases/tag/v1.6.0

if it works as expected, i will mark it as not pre-release and PR it upstream in 2-3 weeks as there is no rush at current moment.


edit: on 3rd of march 2026 the final version of 1.6.0 was pushed.

the git actions is now able to compile it https://github.com/borntohonk/sys-patch/actions/runs/21862434045

this release will be marked as a full release, without any changes on the 24th of february, if no issues are reported, and then upstream push requested to https://github.com/impeeza/sys-patch

(so far one problem has been reported, and fixed, the nifm pattern not working - stable otherwise (?))

edit: this release was removed due to issue with overlay - fixed later

 

[Vin_Thod]

(this is not a full release, it's a pre-release / testing version)


version 1.6.0 contains some refactoring and compatability with latest set of libnx commits (not in latest libnx release yet)
(these two specifically)
https://github.com/switchbrew/libnx/pull/702
https://github.com/switchbrew/libnx/pull/707




https://github.com/impeeza/sys-patch/compare/master...borntohonk:sys-patch:master
https://github.com/borntohonk/sys-patch/releases/tag/v1.6.0

if it works as expected, i will mark it as not pre-release and PR it upstream in 2-3 weeks as there is no rush at current moment.

+1 follow

 

[bth]

I was given feedback first now (for 1.6.0), that the overlay seems to be incompatible with whatever "ultrahand 2.0.0" is, will have to verify if it was the refactor or not, if it wasn't, then yeah... that sounds like a libultrahand problem.

I'd rather deprecate the overlay (remove it), but the overlay it self has nothing to do with sys-patch, all it does is read and edit the config file and/or log file. (in other words, the overlay is optional and doesn't affect the functionality of sys-patch at all)

i will give some more thought about it, and consider if it's worth the time investment to support whaver mess libultrahand is


I have re-targeted with https://github.com/ppkantorski/libultrahand / https://github.com/ppkantorski/Ultrahand-Overlay

here's a 1.6.0 test version that intends to support that. seeing as that is what people use nowadays...?

(nothing sys-patch wise is changed, just the optional overlay)

Post automatically merged: Feb 28, 2026

I guess i would need to know what people actually use, i personally never bothered with overlays.


do people use:
https://github.com/DefenderOfHyrule/nx-ovlloader
https://github.com/DefenderOfHyrule/Tesla-Menu


or:
https://github.com/ppkantorski/nx-ovlloader
https://github.com/ppkantorski/Ultrahand-Overlay


because if i support the ultrahand-overlay enviroment, i would be removing support for the tesla-menu enviroment
i could revert to tesla-menu enviroment, which does seem to also work with ultrahand overlay, but i'm not sure if theres much point in supporting tesla-menu enviroment if people use ultrahand-overlay now

edit: this version is only experimental, and the changes have already been reverted (it does work with ultrahand-overlay, but not needed)

 

[AllOver]

Ultrahand should be compatible with all overlays. If any overlay crashes whilst using ultrahand, then it's likely a ultrahand issue. In the case of syspatch overlay, it's not doing anything crazy. Just displaying some boxes and text. If that's causing ultrahand to crash, then something is seriously wrong as that's what all overlays do.

In my experience most people still use Tesla, although the number of ultrahand users are ever increasing due to it being included in packs, installers bundling it in and the new APIs which work nicely with the OC stuff.

I would just target Tesla, and if it causes ultrahand to not work then oh well. Have them report the bug upstream to ultrahand.

 

[Blythe93]

I haven't had a chance to play with 1.6.0 yet since 1.5.9 works perfectly on my setup. As for Ultrahand vs Tesla, I've switched to Ultrahand not long ago as it's the one that's actively maintained at the moment.

 

[bth]

Ultrahand should be compatible with all overlays. If any overlay crashes whilst using ultrahand, then it's likely a ultrahand issue. In the case of syspatch overlay, it's not doing anything crazy. Just displaying some boxes and text. If that's causing ultrahand to crash, then something is seriously wrong as that's what all overlays do.

In my experience most people still use Tesla, although the number of ultrahand users are ever increasing due to it being included in packs, installers bundling it in and the new APIs which work nicely with the OC stuff.

I would just target Tesla, and if it causes ultrahand to not work then oh well. Have them report the bug upstream to ultrahand.

errr, i guess i'll keep it at the 3 year old libtesla, as the recent libtesla changes change bit too much


compromise:

I update to:
https://github.com/WerWolv/libtesla/tree/f766e9b607a05e9756843cbd62b3bfb98be1646c

which is the libtesla version checked out in:
https://github.com/DefenderOfHyrule/Tesla-Menu/tree/master/libs

I haven't had a chance to play with 1.6.0 yet since 1.5.9 works perfectly on my setup. As for Ultrahand vs Tesla, I've switched to Ultrahand not long ago as it's the one that's actively maintained at the moment.

technically 1.6.0 isn't formally released yet either, as it's not a product seeking to solve a problem, it's not urgent or anything.

edit: reuploaded on 3rd of march 2026; change to sys-patch itself patching mechanic

edit again: should work now. had to revert nibble wildcarding to support some weird memory problems on some consoles

 

[TAOKTC]

Thanks @bth for the new upload on March 3rd.
The previous build was crashing with Ultrahand.
I can confirm that this version works perfectly on my side with Ultrahand 2.2.9, ATM 1.10.2, and FW 21.2.0.