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

[bth]

They have the option to skip fw version, hence why the old fs patches say unpached.

I said as much?

 

[Deleted member 413168]

I said as much?

No you didn't

 

[bth]

No you didn't

This is a public forum, why you attempting to gaslight lmao, just go back a page and re-read it.

 

[Deleted member 413168]

This is a public forum, why you attempting to gaslight lmao, just go back a page and re-read it.

What?

 

[Razor-69]

Sorry for stupid question, but just like to understand: i have both sigpatches and sys-patches installed. In the sys-patch overlay logs only fs noncasigchk_new stated as unpatched, everything else is patched (either yellow or green). Is this normal, or i made some mistake in installation process and patches not working as intended?
Also, can someone explain what are all those patches, what they are for and whats the differences between them?

 

[Blythe93]

In the sys-patch overlay logs only fs noncasigchk_new stated as unpatched, everything else is patched (either yellow or green). Is this normal, or i made some mistake in installation process and patches not working as intended?

Unpatched means 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). I'd suggest that you update to the lastest version, remove config/sys-patch folder, reboot and recheck.

Also, can someone explain what are all those patches, what they are for and whats the differences between them?

@impeeza made a really good thread about how to make your own sigpatches where he also explained what each type of patches does.

 

[impeeza]

Unpatched means 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). I'd suggest that you update to the lastest version, remove config/sys-patch folder, reboot and recheck.


@impeeza made a really good thread about how to make your own sigpatches where he also explained what each type of patches does.

Humm I didn't remember about that thread I have to update it with Info abour NIF and incognito crash...

 

[Razor-69]

Unpatched means 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). I'd suggest that you update to the lastest version, remove config/sys-patch folder, reboot and recheck.

As for now i'm on 20.1.0 FW, AMS 1.9.1 and Hekate 6.3.1, i'm already at the latest sys-patch (1.5.6), after deleting config folder and rebooting everything still the same - only noncasigchk_new is unpatched

 

[impeeza]

Humm I didn't remember about that thread I have to update it with Info abour NIF and incognito crash...

ha ha ha I had updated that post already and I didn't remember!! I think the old age is hitting me now!

 

[razovya]

While both can coexist without conflict, you can reduce the clutter on your SD card as yo)u don't really need two things doing the same thing at the same time.
To remove sigpatches, remove pretty much everything that's usually included in sigpatches archive file i.e.:

• folders es_patches and nfim_ctest from the atmosphere/exefs_patche folder.
• folders fs_patches and loader_patches from the atmosphere/kip_patches folder.
• patches.ini file from the bootloader folder.

Also, remove kip1patch=nosigchk line from the hekate_ipl.ini file.
That should be it. Don't forget to reboot afterwards.

what about replacing fss by pk3 in hekate ini file? i did not do it and it seems to be working

also i have sysmodule in overlays 1.2.2 and when i go in in it says sys-patch is off with a house sign next to it.

when i go in sys-patch overlay i see all on except for disable ca verifications ( 3 times) should they be on?



in sys patch log i have

log- fs
noncasigchk_new patched green
nocntchk2 patched green


log : idr
noacidsigchk patched green

log: es
es3 patched green

log nifm
ctest2 patched green

log:nim
nim: patched YELLOW

LOG: SSL

ALL 3 DISABLED

 

[impeeza]

what about replacing fss by pk3 in hekate ini file? i did not do it and it seems to be working

I thing you are talking about FSS0 and that WILL BE deprecated on next releases, today both are supported.

 

[razovya]

I thing you are talking about FSS0 and that WILL BE deprecated on next releases, today both are supported.

somebody was suggesting to replace fss note in hekate.ini by pk3 .

I still launch from fss50 whats pk3?

a centralized guide would be nice. Info is scattered all around within posts.

 

[impeeza]

somebody was suggesting to replace fss note in hekate.ini by pk3 .

I still launch from fss50 whats pk3?

a centralized guide would be nice. Info is scattered all around within posts.

Release note for Hekate 6.3.0:

https://github.com/CTCaer/hekate/releases/tag/v6.3.0

• HOS 20.0.0 support
• Config: Added pkg3 key support that replaces fss0 with the same exact functionality
  fss0 will still work for compatibility reasons but it's now deprecated.
  At some point fss0 will become obsolete, so make sure you update your configs to use pkg3 instead.
  The templates were updated to use that.
• Config: Added pkg3kip1skip key support. Only for advanced users, read README.
• Config: atmosphere key is now renamed to kernelprocid to match what it does
  Only advanced users that do not use fss0/pkg3 are affected by this
• Config: fss0experimental key was renamed to pkg3ex

This is why, one should manually download the homebrew, READ THE RELEASE NOTES and install manually all on your console. using prepackaged packages make you confused about this changes.

For summary, Hekate can continue the boot process form different sources:

• A payload binary file, is indicated with the payload=path/from/SDROOT/payloadname.bin, Hekate will chainload the boot to that binary file. this can be used to load linux by example.
  • If you boot to Atmosphère's fusee.bin payload you could use the atmosphere key to indicate to Hekate to NOT LOAD PATCHES nor make changes on the memory so a PLAIN VANILLA Atmosphère will be loaded. TODAY that key was renamed to kernelprocid for a short time booth names will be suppported.
• Atmosphère's Third Package loading, this is indicated with the line pkg3=atmosphere/package3 where Hekate will read the file indicated, unpack it, extract the needed modules and continue with the third stage of boot of the console, this key was called FSS0 before, TODAY booth names will be supported and treated as synonyms, but on a near future the FSS0 key will not be supported.

so if your SDMC:/bootloader/hekate_ipl.ini file have some of those keys, you should rename them soon.

 

[razovya]

Release note for Hekate 6.3.0:

https://github.com/CTCaer/hekate/releases/tag/v6.3.0

• HOS 20.0.0 support
• Config: Added pkg3 key support that replaces fss0 with the same exact functionality
  fss0 will still work for compatibility reasons but it's now deprecated.
  At some point fss0 will become obsolete, so make sure you update your configs to use pkg3 instead.
  The templates were updated to use that.
• Config: Added pkg3kip1skip key support. Only for advanced users, read README.
• Config: atmosphere key is now renamed to kernelprocid to match what it does
  Only advanced users that do not use fss0/pkg3 are affected by this
• Config: fss0experimental key was renamed to pkg3ex

This is why, one should manually download the homebrew, READ THE RELEASE NOTES and install manually all on your console. using prepackaged packages make you confused about this changes.

For summary, Hekate can continue the boot process form different sources:

• A payload binary file, is indicated with the payload=path/from/SDROOT/payloadname.bin, Hekate will chainload the boot to that binary file. this can be used to load linux by example.
  • If you boot to Atmosphère's fusee.bin payload you could use the atmosphere key to indicate to Hekate to NOT LOAD PATCHES nor make changes on the memory so a PLAIN VANILLA Atmosphère will be loaded. TODAY that key was renamed to kernelprocid for a short time booth names will be suppported.
• Atmosphère's Third Package loading, this is indicated with the line pkg3=atmosphere/package3 where Hekate will read the file indicated, unpack it, extract the needed modules and continue with the third stage of boot of the console, this key was called FSS0 before, TODAY booth names will be supported and treated as synonyms, but on a near future the FSS0 key will not be supported.

so if your SDMC:/bootloader/hekate_ipl.ini file have some of those keys, you should rename them soon.

yeah i think back then i used captainprepack ,in launch there is and fss50 option. BtwI replaced the fsss in hekate .

but my nim file only shows patched yellow , yesterday it was green. What's that for and why it is not green anymore.


edit: how to fix this
NIM
The NIM patches are needed to avoid Atmosphère crashes when you boot Firmware 17.0.0 or newer with blanked Prodinfo.

 

[Blythe93]

edit: how to fix this
NIM
The NIM patches are needed to avoid Atmosphère crashes when you boot Firmware 17.0.0 or newer with blanked Prodinfo.

Both sys-patch and sigpatches come with the nim fix. In the past we used to use this until it was integrated into sigpatches and sys-patch.

 

[razovya]

Both sys-patch and sigpatches come with the nim fix. In the past we used to use this until it was integrated into sigpatches and sys-patch.

mine is orange though yesterday it was green pathced. how do i fix this

 

[Deleted member 413168]

mine is orange though yesterday it was green pathced. how do i fix this

You don't. Orange means its patched.

 

[aarstar]

Could someone please explain what the following sig patches do? nocntchk and noncasigchk_2
I'm on the latest atmosphere, sig patches, and sys-patch. OS version is 18.x. These are the only 2 that are not patched, everything else is green or orange.

 

[Deleted member 413168]

Could someone please explain what the following sig patches do? nocntchk and noncasigchk_2
I'm on the latest atmosphere, sig patches, and sys-patch. OS version is 18.x. These are the only 2 that are not patched, everything else is green or orange.

- nocntchk (no content distribution check) isn't needed.
- noncasigchk (no nca sig check) patches the check for the nca header, only needed if the nca is modified.
- noacidsigchk (no acid sig check) is for the program nca, it patches acid check, only needed if the program nca is modified (like above). this used to be part of fs, now its in ldr. as loader is reimplemented by atmosphere, its actually ams loader.kip that gets patched.
- es patches the check for verifying the es/cert signature, only needed if the ticket is modified (usually faked).

 

[razovya]

- nocntchk isn't needed.

hey do you recommend tesla menu or the ultrahand menu
UltraHand Overlay Menu