[Please help] Unpack and repack of system.img are different file sizes.
[Please help] Unpack and repack of system.img are different file sizes.
(16-02-2018, 01:39 PM)Qym Man there is what we call dm-verity it wont let you boot to a modified system image. You need to patch your boot image.
(16-02-2018, 02:26 PM)Qym I also own MT6737m with Android 6 and getting Android 7 or 8 to work has been a tough experience. And of course yea, you need to unlock your bootloader. Then get a tool to unpack your stock boot image head on to fstab.6735 then delete verify on the /system mount flags. Repack your image. Then delete the verity_key from your /system partition and you should be good to go. Right now am on my free time I can patch up the boot image for you ONLY if you can trust a stranger! Haha...
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system /system ext4 ro wait, verify
/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system /system ext4 ro wait
(16-02-2018, 04:21 PM)davek17 Questions:
1. So where is the verity_key in the system partition? Mine is in the boot.img ramdisk
2. Will this resolve being able to run ADB in root mode so I can adb remount rw and tinker with the system on the device?
(16-02-2018, 04:58 PM)Qym But most of the time you won't need the debug props unless you want to do adb root you can just do adb shell su.
(16-02-2018, 05:12 PM)davek17 I have been unable to get any custom recovery working, or to get SU, busybox or anything installed
(16-02-2018, 05:38 PM)QymNo, 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.(16-02-2018, 05:12 PM)davek17 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