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.because it doesn't take any memory to be active
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.because it doesn't take any memory to be active
I was wondering de same and also thinking aboutActually 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.
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.it apply patches with patern witch is more efficient than fixed patches
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.
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.
For last 2 or 3 ofw you have to update syspatch and create new patterns. So the same as for classic sigpatches.don't have to regenerate the patches
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.
Actually sys-patch has a memory footprint, very small but still
sigpatches haven't got any
Minimal sigpatches only take 3-4 files depending if you're using both FAT32 and exFAT
About 4Ko on SD card
sigpatches are the lightest solution
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)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.
Nop. You need to read the previous post where the different patches status are explainedHi,
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?
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!
They don't even work since Atmosphere 1.7.0 prerelease deleted support for kip patches.kip_patches
They don't even work since Atmosphere 1.7.0 prerelease deleted support for kip patches.
Yes IPS sigpatches and SYS-module are redundantsCan 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?
It's available on archive.org.Does someone has the source of the Sigpatcher-updater?
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.It's available on archive.org.
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)?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.