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

[josete2k]

Just downgraded and it works for me

Post automatically merged: Oct 16, 2024

Hmmm I see if versión skip is active there's no "nocntchk" patch.


All I have works but you can edit this line

{ "nocntchk", "0x081C00121F050071..0054", -4, 0, bl_cond, ret0_patch, ret0_applied, true, MAKEHOSVERSION(10,0,0), MAKEHOSVERSION(15,0,0) },

Change MAKEHOSVERSION(15,0,0) to MAKEHOSVERSION(18,0,0)

Post automatically merged: Oct 16, 2024

What does the nocntchk patch do?

 

[masagrator]

did you compile it and put it at \devkitPro\tools\bin\npdmtool.exe? you need the new one here for the flag to be right

switch-tools was updated in devkitpro, there is no need to do it manually

 

[impeeza]

did you compile it and put it at \devkitPro\tools\bin\npdmtool.exe? you need the new one here for the flag to be right

I didn't know how to make the latest version of switch-tools, but learned 1 hour ago, will test new build of sys-patch code and let you to know.

 

[josete2k]

automake
autoconf
. /configure
make

 

[impeeza]

automake
autoconf
. /configure
make

I used this commands to build the tools:

cd ~
rm -rf switch-tools
git clone --recursive https://github.com/switchbrew/switch-tools
cd ~/switch-tools
./autogen.sh
autoreconf --install
mkdir build
cd build
../configure
make
cp *.exe /opt/devkitpro/tools/bin/

 

[jaysea]

I ran the 1.5.3-dirty and the es7_fw18-19 is showing as unpatched in the log while I am on fw 18.1.0.
Edit: Everything seems to run fine except for tinfoil since I used the self installer. Fixed that by changing to forwarder.
So basicaly it shows unpatched for es7_fw18-19. Haven't tried with removing the ES patch file though.

 

[alfonsovin]

Nope. Tesla menu is the initial overlay menu to be loaded by nx-ovlloader and nx-ovlloader is the post process for loading Switch overlay OVLs (NROs). As @duckbill007 mentioned, Tesla menu allows you to see your installed sys-modules, including sys-patch. Other than checking its logs, you can turn on or off some of sys-patch options as well.

Installation is simple: grab Tesla + nx-ovlloader and latest sys-patch, just make sure that you extract them to the right directories (to the root of your SD card). Once installed, reboot the system and after that if you you press L + D-pad Down + R (Stick) combo, Tesla menu should appear. There you can select sys-patch, followed by Log. If it says:

1. Patched = the pattern it's searching for is already patched by sigpatches, so there's no need to patch it again;
2. Patched = the pattern is patched by sys-patch (i.e. sigpatches are not present or haven't been applied on boot);
3. Unpatched = the pattern wasn't found by sys-patch on the current system so there's no need to patch them (only present if you turn off the Version skip in the Options).

For now Im not going to update emuMMC to 19.0, still in 18.1 but just to clarify: I have yellow patched in log of sys-patch

So my question is:
is it better to be green? (patched by sys-patch)
to get it green, may I have to delete the sigpatches folders in content folder?
Better stay as it works: "while it works better you don't touch"

 

[impeeza]

For now Im not going to update emuMMC to 19.0, still in 18.1 but just to clarify: I have yellow patched in log of sys-patch

So my question is:
is it better to be green? (patched by sys-patch)
to get it green, may I have to delete the sigpatches folders in content folder?
Better stay as it works: "while it works better you don't touch"

Do not upgrade your FW unless is needed. lots of software will be need to rebuilt to work on the new FW.

 

[shadow256]

Do not upgrade your FW unless is needed. lots of software will be need to rebuilt to work on the new FW.

New FW and new Atmosphere also, the forwarders and at least some modules doesn't work if just updating Atmosphere without update firmware to 19.0.0.

 

[alfonsovin]

Do not upgrade your FW unless is needed. lots of software will be need to rebuilt to work on the new FW.

my question is about FW update, I have clear idea to stay in actual FW in CFW while it is stable and works. The question is in general, is it better be "yellow" or "green"? To be "green" may I have to delete the content folders of sigpatches?

 

[Blythe93]

is it better to be green? (patched by sys-patch)

Short answer: Yes.
Long answer: Check my previous post to see what each color means. Green and orange are both fine, red one's fine if intentional and If everything works,

to get it green, may I have to delete the sigpatches folders in content folder?

Yep. Once you remove sigpatches, sys-patch log should say Patched.

Better stay as it works: "while it works better you don't touch"

Indeed. As long as there's no game or its update/DLC that requires higher firmware version, you don't really need to update. Who knows what may get broken in the process.

 

[impeeza]

my question is about FW update, I have clear idea to stay in actual FW in CFW while it is stable and works. The question is in general, is it better be "yellow" or "green"? To be "green" may I have to delete the content folders of sigpatches?

Read the post about the colors

There is no better, if is patched is patched, the colors only indicate in which step was patched.

 

[TomSwitch]

switch-tools was updated in devkitpro, there is no need to do it manually

how to get 1.13?

 

[impeeza]

View attachment 465292
how to get 1.13?

I don´t know mine is 1.13.0-1

The problem is your repo is telling 1.12.0-1 is latest version, which devkitpro are you using?

Try running

pacman -Syuu

Post automatically merged: Oct 17, 2024

did you compile it and put it at \devkitPro\tools\bin\npdmtool.exe? you need the new one here for the flag to be right

Switchbrew team got mad about me giving the instructions for build manually the repo. but well today you can install switch-tools 1.13.0-1 package which have the latest code.

 

[TomSwitch]

Try running

pacman -Syuu

Yes, that works.

Post automatically merged: Oct 17, 2024

Today the problem with this debug flag thing means my way or the high way to those who are not updating to atm1.8 cause if you build with the flag that works for atm1.8 it will either not work or crash on atm1.7 just like the older build will either crash or not work on atm1.8

Post automatically merged: Oct 17, 2024

@impeeza you may want to make a note telling people to use the old version for atm1.7 at your release page for sys-patch

There may be few but there will be some who come late and want to use sys-patch on atm1.7

 

[impeeza]

For now Im not going to update emuMMC to 19.0, still in 18.1 but just to clarify: I have yellow patched in log of sys-patch

So my question is:
is it better to be green? (patched by sys-patch)
to get it green, may I have to delete the sigpatches folders in content folder?
Better stay as it works: "while it works better you don't touch"

YOUR ANSWER IS ON THE VERY PREVIOUS PAGE!!!!

Nope. Tesla menu is the initial overlay menu to be loaded by nx-ovlloader and nx-ovlloader is the post process for loading Switch overlay OVLs (NROs). As @duckbill007 mentioned, Tesla menu allows you to see your installed sys-modules, including sys-patch. Other than checking its logs, you can turn on or off some of sys-patch options as well.

Installation is simple: grab Tesla + nx-ovlloader and latest sys-patch, just make sure that you extract them to the right directories (to the root of your SD card). Once installed, reboot the system and after that if you you press L + D-pad Down + R (Stick) combo, Tesla menu should appear. There you can select sys-patch, followed by Log. If it says:

1. Patched = the pattern it's searching for is already patched by sigpatches, so there's no need to patch it again;
2. Patched = the pattern is patched by sys-patch (i.e. sigpatches are not present or haven't been applied on boot);
3. Unpatched = the pattern wasn't found by sys-patch on the current system so there's no need to patch them (only present if you turn off the Version skip in the Options).

 

[froggy55]

YOUR ANSWER IS ON THE VERY PREVIOUS PAGE!!!!

so ive been reading through tis thread at least the last 10 post or so and i saw some stuff about the switch tools 1.13 is that for updating sys-patch and is this still in progress im in no rush just curious thanks

Post automatically merged: Oct 18, 2024

so ive been reading through tis thread at least the last 10 post or so and i saw some stuff about the switch tools 1.13 is that for updating sys-patch and is this still in progress im in no rush just curious thanks

i was asking a question but thank you

Post automatically merged: Oct 18, 2024

so ive been reading through tis thread at least the last 10 post or so and i saw some stuff about the switch tools 1.13 is that for updating sys-patch and is this still in progress im in no rush just curious thanks

Post automatically merged: Oct 18, 2024

i was asking a question but thank you

ok so i went back and re read everything am i correct in understanding that you are still working on this i saw a post about an updated version by snip but no confirmation as wether or not it works or if thats what you are using to make the new update any ways thank you so much for your hard work and contributions

 

[RedColoredStars]

Is there any difference between sys-patch 153 here and what's on three cats? File hashes are different for a couple of the files but could be from being built differently. Any actual differences, or the same?

 

[linuxares]

Is there any difference between sys-patch 153 here and what's on three cats? File hashes are different for a couple of the files but could be from being built differently. Any actual differences, or the same?

The hashes will always change depending on whom compiles it. But in theory they should be the same. If you want the closest to vanilla go with the cat site.

 

[impeeza]

Is there any difference between sys-patch 153 here and what's on three cats? File hashes are different for a couple of the files but could be from being built differently. Any actual differences, or the same?

Yes they're difference but sadly due to all bitching and cat fight of the latest time the code was released the gurus are trying ykeep the code away of public. Once is stable I will share diffs for the one interested