Hi,
I'm getting crazy.. maybe someone can help me:
I've got that tiny great cool new mini projector from Doogee running android, it's really great but some software needs to get disabled. Getting into recovery is a bit hidden, but quite easy once found:
Call "adb reboot recovery", pluign an USB keyboard and you end up in an nice old recovery session. "adb sideload" works, but when installing SuperSU it breaks with "BAD RECOVERY DETECTED, NO UNZIP". Fair enough, this message is already from custom code running as root.
But now I've spend hours without any success getting just the unmodified update.zip extracted and repackaged so that the recovery accepts the signature. Can anybody give me a hint how the SuperSU.zip is created? There must be something special. Next step would just be to add a cp into the script and install the unzip somewhere from /data
Thanks
I'm getting crazy.. maybe someone can help me:
I've got that tiny great cool new mini projector from Doogee running android, it's really great but some software needs to get disabled. Getting into recovery is a bit hidden, but quite easy once found:
Call "adb reboot recovery", pluign an USB keyboard and you end up in an nice old recovery session. "adb sideload" works, but when installing SuperSU it breaks with "BAD RECOVERY DETECTED, NO UNZIP". Fair enough, this message is already from custom code running as root.
But now I've spend hours without any success getting just the unmodified update.zip extracted and repackaged so that the recovery accepts the signature. Can anybody give me a hint how the SuperSU.zip is created? There must be something special. Next step would just be to add a cp into the script and install the unzip somewhere from /data
Thanks
from xda-developers http://ift.tt/1WvRaHO
via IFTTT
No comments:
Post a Comment