Conversation
|
also remove lines: edit lines, save or just new commit message and push |
|
also comment: on 18.1.0 https://github.com/impeeza/sys-patch/blob/master/sysmod/src/main.cpp#L256 this hits function 0x74310 instead of 0x743BC and must be changed to: |
|
I mirrored this logic here: |
|
also i notice @impeeza is uploading .7z release, why? do "make dist" and it will create sys-patch.zip https://github.com/impeeza/sys-patch/blob/master/Makefile#L51-L56 |
{ "10-18", "0x40f9...9408.0012.050071", 2, 0, bl_cond, ret0_patch, ret0_applied, true, MAKEHOSVERSION(10,2,0), MAKEHOSVERSION(18,1,0) },//fw10.2.0-fw18.1.0 |
|
{ "1-9A", "0x........0036..00b4..40b9", 2, 0, bl_cond, ret0_patch, ret0_applied, true, MAKEHOSVERSION(1,0,0), MAKEHOSVERSION(9,2,0) }, }; |
|
This doesn't apply to EXFAT, exfat I couldn't find the wildcard, so this item applies to 17+ |
Sorry about that was so slept, editing now. |
|
Hello there, Thanks a lot for all the work you are investing on. This is a great optimization. It's ready to be mereged? it looks so nice! |
|
This is the unfixed area: #FS 7.0.0-ExFAT #FS 8.0.0-ExFAT #FS 8.1.0-ExFAT #FS 14.0.0-ExFAT #FS 15.0.0-ExFAT #FS 16.0.0-ExFAT #FS 16.0.3-ExFAT |
So I have a very hot opinion here. Maintaining compatibility down to 10.0.0 is good enough. 10.0.0 released april 14 2020. 4 years ago. most important is current firmware, and maybe down to 17.0.0 (all are supported currently, no reason to do much more work) |
|
|
@borntohonk correctme if I am wrong. using as starting point IPS patch (or boot.ini enties) is no easy to create SYS-Patch patterns, they are two different approachs. |
ips patches contain offsets and what patch it writes to the offset, you could just as easily open the binary in ghidra, go to the offset, see whats there and create a pattern (diffing several firmwares give better patterns,) (same applies to patches.ini with hekate, nothing there cannot be looked up) alternatively you can just do with one and instead pattern arm instructions, and then some static bytes |
|
@borntohonk Is This PR ready to be merged? |
🤷 it's not my PR, but it's about as ready as it can be i guess |
|
Okay, I'm sure it's fine. |
|
will review this the next week I come back to home and let you to know. |
|
i personally prefer having the functions labelled over "9a 9b 9c 9d", but the existing labels weren't consistent either. |
|
Merged on PR9 |
|
This changes was merged on the PR9, Thanks a lot for all the work. |


No description provided.