Actually ips files don't take any memory too since they are loaded via modules that are always active and do also other jobs than patching.
Homebrew Homebrew app sys-patch - sysmod that patches on boot
- Thread starter TotalJustice
- Start date
- Views 114,656
- Replies 393
- Likes 109
I was wondering de same and also thinking about
That have no sense at all, it applies the same patches, only some of them are a little different but is only instead apply 2 patches on normally adjacent offset apply one bigger on only an offset but the difference is mute.
But with the module you don't have to regenerate the patches, for loader patch you can change or even rebuild Atmosphere without having to change anything else. It's not difficult to rebuild a new loader patch but with the module no need to do it anymore. Personaly I think that with Atmosphere stoping suport to fs_patches the module is the best choice, it offer only advantages against old solutions. But it's true that the patches are a little different but like you say nothing change realy (games work like before, installation and launching homebrew also) so what are the advantage of old sig_patches.
Totaly right, the module use a little memory during the boot process (maybe it could be concidered as a week point against old solutions but the module need realy a small amount of memory so is it realy a problem) but after it's the same as using IPS patches no?
For last 2 or 3 ofw you have to update syspatch and create new patterns. So the same as for classic sigpatches.
Also syspatch has a very serious bug in the algo: it does not check that found by pattern place is unique and just patch first found place. There's no guarantee that this is a correct place.
Easier to update a simple module than sig_patches witch have multiple files in multiple dirrectories. And you're right, the module could need some updates to match with new firmwares but for loader patches at least don't need them, also true for nfim_patches.
You seem to have more knowlages than me on the subject but for now is it already a problem? And maybe the algo could be rewrite to use the result number associed with a pattern (for example if a pattern match with 2 results we decide to apply it on the first or second result depending on the firmware or anything else), it's not a perfect solution but I don't know how to fix this, detecting patches like that should always have this problem because we can't be sure that the pattern founded it the good one.
My knowlages and comprehension of sig_patches are very limited so I could make some mistakes.
Yes for the first afirmation but only during boot process for a short time.
Also yes for the second one but module solution is easier to maintain and again work for all configuration, including launching Atmosphere with fusee.bin witch is not supported anymore by sig_patches except if you rebuild Atmosphere to re-include the support witch is not a good solution, I think we are all agree about that. I think for advanced users it's not a problem to continue to use sig_patches but for normal users the Sys-patch solution is now a better choice.
From my point of view correct algorithm should be following: for known FW there should be fixed patches at fixed known offsets, and only for unknown FW and maybe for atmosphere's loader (too many versions) there should be find by pattern (with log to file at what offset pattern is found, so dev can check it manually and add to static patch list)
Hi,
I'm running FW 18 and Atmosphere 17, the sys-patch overlay gives me everything patched in orange, exception made for es6 that is unpatched and ctest which is green.
Do i need es6 patched as well? is there any reason why I haven't got es7?
I'm running the latest hekate with the package 3 i found in this thread, i also updated the hekate_ipl.ini accordingly.
Thank you in advance for your support!
I'm running FW 18 and Atmosphere 17, the sys-patch overlay gives me everything patched in orange, exception made for es6 that is unpatched and ctest which is green.
Do i need es6 patched as well? is there any reason why I haven't got es7?
I'm running the latest hekate with the package 3 i found in this thread, i also updated the hekate_ipl.ini accordingly.
Thank you in advance for your support!
Last edited by Tsunamy,
Nop. You need to read the previous post where the different patches status are explained
- Patched = the pattern it's searching for is already patched by sigpatches, so there's no need to patch it again;
- Patched = the pattern is patched by sys-patch (i.e. sigpatches are not present or haven't been applied on boot);
- 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).
Can all sigpatches be deleted safely and just use sys-patch? Is it okay to just delete the kip_patches & exefs_patches folders along with the patches.ini file? Or are some files still necessary?
Edit: Seems to be working fine but can't delete patches.ini file without getting an error about kip1patch=nosigchk so I put that file back. On that note, is kip1patch=nosigchk necessary when using only sys-patch?
Edit: Seems to be working fine but can't delete patches.ini file without getting an error about kip1patch=nosigchk so I put that file back. On that note, is kip1patch=nosigchk necessary when using only sys-patch?
Last edited by RedColoredStars,
They don't even work since Atmosphere 1.7.0 prerelease deleted support for kip patches.
Yeah. I was aware of that since 1.7 was released but there's also the modified fusee. I guess I asked because I got the error about kip1patch=nosigchk when I deleted the two folders AND the patches.ini file. The error went away when I put the ini file back, hence my edit.
I assume the kip1patch=nosigchk line can also be deleted from hekate_ipl.ini and then the patches.ini file can also be deleted.
Didn't find it. The archived version is from 2020, directly downloaded from the Wayback Machine version of the Github repository, and checking directly on archive.org is just *.bundle files, my guess it's the data from the archived version of the repository.
Are you looking for sigpatches-updater or Sigpatch-Updater? I assumed the latter one, since you're asking in this thread (ITotalJustice worked on both sys-patch and Sigpatch-Updater)?
Similar threads
-
- Locked
- Portal
-
-
-
-
-
-
-
-
-
@
ZeroT21:
only ps5 updated to latest firmware can go on psn, jailbroken ones just don't use psn or they risk getting flagged or banned, altho spouting profanity in online play alredy does that -
-
-
Y @ YuseiFD:Then how come you do it and don't get banned ? or is it a question of getting caught doing it ?
-
-
@
BakerMan:
wtf is the point of banning swearing in games? that's utterly a dumb decision
the new generation playing MWII won't be as hardened as the previous one playing original MW2 -
@
Veho:
What's the point of video games? Kids playing video games won't be as hardened as the previous ones getting shoved down a hillside.+2 -
-
@
BakerMan:
kids, yall are fucking pussies, grow some asshair before you even dare touch My Friend Peppa Pig or Mario's Early Years+1
-
-
-
-
-
-
-
-
