-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working #2
Comments
disable all other modules and try again. |
Unfortunately I have the same problem. No Magisk logs either. Edit: I should clarify, this is Android 14. |
Try this steps: Disable all modules except this one. Reboot open terminal or use adb shell and run these code:
output should be:
if its not, something might be resetting these props to safe values, and most probably its baked into your custom rom. |
I forgot to follow-up with the cause last night. The problem isn't your module, it's that adbd wasn't compiled with ALLOW_ADBD_ROOT. Modern Android ROMs (more and more) are removing that which causes adbd to literally be compiled neutered without the ability to use root. I simply ended up modifying my adb pull commands into an adb shell su copy to an accessible directory and then adb pull, rm. Thank you, though. Edit: You can see it |
@OdinVex : Have you managed to remount any partitions with |
@xaionaro, I never wanted to remount, merely access. I'm currently bringing support for PostmarketOS to my phones and I'm dumping Android entirely. |
I was hoping this would work because of all the extra secpolicy stuff you're fixing. Does it need to be flashed through TWRP specifically? I saw an error and flashed in KSU instead and it doesn't change any props or anything...
The text was updated successfully, but these errors were encountered: