In a few hold on
i have to go to mincha in 20 so maybe after then
Alright I know I said this before but I think I found the issue
I knew it already before man I’m feeling slow today
If build not debug nothing works. Will patch, or you can change debug to user with resetprop to test
Try it should work
1 Like
To test theory
adb shell su -c resetprop ro.debuggable 1
adb shell su -c resetprop ro.secure 0
adb shell su -c resetprop ro.adb.secure 0
Still needed patches to services, but won’t apply without this, rebuilding services now to work on user build too.
PS C:\Users\Daniel Frydman\Downloads> adb shell su -c resetprop ro.debuggable 1
PS C:\Users\Daniel Frydman\Downloads> adb shell su -c resetprop ro.secure 0
PS C:\Users\Daniel Frydman\Downloads> adb shell su -c resetprop ro.adb.secure 0
PS C:\Users\Daniel Frydman\Downloads> adb shell su -c “cmd package install /data/local/tmp/1.apk”
Failure
Need reboot, and eitherway…
Put new services.jar and reboot
Alright, now I am VERY invested 
Guess I gotta wait for you to come back from mincha
This is the latest patch:
# This:
sget-boolean v0, Landroid/os/Build;->IS_DEBUGGABLE:Z
const/4 v1, 0x1
if-nez v0, :cond_1 # If debuggable, continue # Otherwise:
const-string v2, "Failure"
return v1
# To this:
sget-boolean v0,
const/4 v1, 0x1
const/4 v0, 0x1
if-nez v0, :cond_1
Notice the plain string v2, "Failure"
1 Like
leaving in a few -
i replaced the services.jar
1 Like
so i have to make it user debug again
If you put in latest, that I labeled user build, no need to change props
it worked
4 Likes
gotta go but im so happy
1 Like
wow @ars18 for the win (again )
4 Likes
WOOHOO!
Just a suggestion, if you want to contribute back to the community, release the ROM as your own 1.1.1 for new qin phones. No pressure
2 Likes
for you ill do it - just dont know when it will be ready
3 Likes
I feel great too!
is the backgroung kill app included in this services.jar
are the other patches also nessary