You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the issues and haven't found anything relevant
If patch failed, root failed, or device unable to boot after flashing the new boot.img. Please goto KernelPatch
I will upload bugreport file in APatch Manager - Settings - Report log
My problem is fully stated in English, no reference to outside forums
I know how to reproduce the issue which may not be specific to my device
Describe the bug
The latest version of the Play Integrity Fork module by osm0sis fails to work as resetprop is missing the -Z argument.
To Reproduce
1: Open a terminal as root
2: Attempt to use resetprop with -Z argument, (example: resetprop -Z ro.boot.flash.locked 1)
3: Will display help information instead of running the proper command
Expected behavior
Command should run as expected
Screenshots
No response
Logs
No response
Device info
Device: Motorola One 5g Ace
OS Version: 13
APatch Version: 10450
Kernel Version: 4.19.157
Additional context
No response
The text was updated successfully, but these errors were encountered:
resetprop -Z was added to Magisk about 8 months ago (before v26.2), and the latest Magisk stable was 2 months ago (v26.4) in late November: topjohnwu/Magisk@f36b21b
KernelSU updated to latest resetprop from Magisk Canary 26404 about 2 weeks ago: tiann/KernelSU@153ce9a
So yeah, please do update so all the prominent root solutions are in sync! You can probably just grab the standalone build from that KSU commit even. 🙂
Please check before submitting an issue
Describe the bug
The latest version of the Play Integrity Fork module by osm0sis fails to work as resetprop is missing the -Z argument.
To Reproduce
1: Open a terminal as root
2: Attempt to use resetprop with -Z argument, (example: resetprop -Z ro.boot.flash.locked 1)
3: Will display help information instead of running the proper command
Expected behavior
Command should run as expected
Screenshots
No response
Logs
No response
Device info
Additional context
No response
The text was updated successfully, but these errors were encountered: