02-20-2018, 11:33 AM
(02-19-2018, 09:13 AM)davek17 Wrote: 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?
Am sure philz will work out nice and easy as I had success using the philz tool. The twrp tool got a bug as of now, you can read my comments at the end of its thread.
To answer your questions. First dm-verity only works for system partition. Secondly I cant say much about adb root as I always prefer bare metal su because am always deleting and adding files to system partition so it would be a pain to rely on adb for that. Lastly if you are on MT6737* I have a working twrp for it you can tell me if you wanna try it.