[Development] Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
[Development] Mediatek (MTK) Auto TWRP recovery porter by Team Hovatek
(23-08-2019, 03:31 PM)Stephelyn Doesn't work for me, after porting and flashing, it doesn't boot twrp. Philz Touch Recovery Porter tool works fine and booted on my device except TWRP. I have tried TWRP from other website porting it, same result. Idk why TWRP won't boot, i have unlocked bootloader. My device is Cherry Mobile Flare Y7 LTE powered by MT6739W 64bit Oreo-Go edition.
(23-08-2019, 07:04 PM)X3nonYes... I have tested them all, it doesn't boot in any 8.x versions. Is this cause from encrypted data? I have encrypted data, other words encrypted phone.(23-08-2019, 03:31 PM)Stephelyn Doesn't work for me, after porting and flashing, it doesn't boot twrp. Philz Touch Recovery Porter tool works fine and booted on my device except TWRP. I have tried TWRP from other website porting it, same result. Idk why TWRP won't boot, i have unlocked bootloader. My device is Cherry Mobile Flare Y7 LTE powered by MT6739W 64bit Oreo-Go edition.
check page 1, did you try the 3rd suggestion under "Note"? ie trying twrp from other oreo versions
(23-08-2019, 10:51 PM)Stephelyn Yes... I have tested them all, it doesn't boot in any 8.x versions. Is this cause from encrypted data? I have encrypted data, other words encrypted phone.
(24-08-2019, 12:28 PM)Stephelyn When i ported TWRP to my device, a message comes up that dm_verify not found, no need to patch boot.img. I didn't have any boot problems on Philz Touch, only this, tried different TWRP images from same chipset, same result, not booting to TWRP, just simply restart itself to normal. I don't know about this Encrypted Phone, is this dm_verify cause? I have encrypted phone, when i look into my fstab stock recovery, i saw this partition data with forceencryption.
Never Mine, i have ported 3.2 Twrp with same chipset with mine, it boots now and the only thing that bothers me is the Encrypted Storage Data, can't mount data, need to decrypt, any guides?
(26-08-2019, 10:17 AM)X3nonI have found the problem, the twrp that i ported to my device doesn't have f2fs format function, because my kernel only supports data with f2fs files system, formatting it to ext4 would cause a bootloop and data storage can't create necessary files like dalvik folder and other related data files, only media where internal storage is found. So here's the solution, i ported again a twrp with same device but now i pull the mkse.f2fs from other twrp, and put them to sbin folder of my ported twrp and set permission in cpio.list, so if Qurepack repack my recovery it will be included upon compiling, so luckily, when i booted up and format again my data storage, my data is now f2fs, but i modified the fstab of my twrp, instead of ext4 i change i to f2fs, so that twrp will automatically format my data into f2fs. And about forceencrypt, i found a mt6739.fstab from my vendor/etc/ partition, i remove forceencrypt flag, so that it will not encrypt my data automatically upon reboot system... Problem Solve, i have now magisk installed and rooted my device.(24-08-2019, 12:28 PM)Stephelyn When i ported TWRP to my device, a message comes up that dm_verify not found, no need to patch boot.img. I didn't have any boot problems on Philz Touch, only this, tried different TWRP images from same chipset, same result, not booting to TWRP, just simply restart itself to normal. I don't know about this Encrypted Phone, is this dm_verify cause? I have encrypted phone, when i look into my fstab stock recovery, i saw this partition data with forceencryption.
Never Mine, i have ported 3.2 Twrp with same chipset with mine, it boots now and the only thing that bothers me is the Encrypted Storage Data, can't mount data, need to decrypt, any guides?
either try flashing no-ver-opt.zip OR try the decryption method as explained @ https://www.hovatek.com/forum/thread-29013.html
if you still have any problems then create a new thread for your device issuer by clicking "Ask question" at the top