(02-16-2018, 05:38 PM)Qym Wrote:
(02-16-2018, 05:12 PM)davek17 Wrote: I have been unable to get any custom recovery working, or to get SU, busybox or anything installed
So what you really want is su and also debloat your stock rom. Right? Then you just need a custom recovery first. Use philz hovatek auto porter to get a custom recovery
No, I don't need SU, I just want to be able to get ADB root. In fact SU is bad for a number of reasons as I can't run certain apps like Google Pay etc if the devices is rooted. Normally I can do what I need to do from ADB.
Normally to get ADB root you change the boot.img as above, however it is simply not working. I can see using adb shell getprop
that the properties have changed in the default.prop file, adb root
seems to do something, however when I adb remount rw
, I get an error that I need to use adb root first!
I have tried to port a custom recovery, as this device does not seem to have one installed. However I have tried to install TWRP or even the MTK recovery tool that many other MTK based devices have on them with the same CPU and Android OS. I flash these using SP Phone tools but the device just reboots when I try to enter recovery mode. I think I tried every single latest version of TWRP and this is the result so far.
Is there something I have missed here? It seems to me that these newer MTK devices are just locked and no-one knows how to get them working any more?
I will try philz hovatek auto porter and see if that brings any joy! but the purpose of this thread is to see why these devices are behaving like they are. So the outstanding questions are:
1. Is it do with verity? I am not getting any verity errors.
2. Why isn't the normal way of getting ADB Root working like above (boot.img editing default.prop)? Does verity block this?