Teclast M40 bricked after magisk boot.img
Teclast M40 bricked after magisk boot.img
(21-12-2020, 02:58 PM)snow43 Apparently magisk canary was needed, i cannot enter to fastboot or recovery now. Stuck at bootlogo with INFO LOCK FLAG IS UNLOCK!!!
No TWRP, not visible in device manager
what to do?
Update: managed to start flashing with "UpgradeDownload.exe"
Update 2: Managed to unbrick, now the question is how to properly root the device? Do i need to do this? https://www.hovatek.com/forum/thread-32664.html
python2 avbtool make_vbmeta_image --key snow.pem --algorithm SHA256_RSA4096 --flag 2 --chain_partition boot:1:keys/boot_key.bin --chain_partition vbmeta_system:3:keys/vbmeta_system_key.bin --chain_partition vbmeta_vendor:4:keys/vbmeta_vendor_key.bin --chain_partition dtbo:5:keys/dtbo_key.bin --chain_partition socko:6:keys/socko_key.bin --chain_partition odmko:7:keys/odmko_key.bin --chain_partition recovery:2:keys/snow.bin --chain_partition l_modem:8:keys/l_modem_key.bin --chain_partition l_ldsp:9:keys/l_ldsp_key.bin --chain_partition l_gdsp:10:keys/l_gdsp_key.bin --chain_partition pm_sys:11:keys/pmsys_key.bin --chain_partition l_agdsp:12:keys/l_agdsp_key.bin --chain_partition l_cdsp:13:keys/l_cdsp_key.bin --padding_size 20480 --output vbmeta_custom.img
(22-12-2020, 02:07 PM)snow43 Bootloader is unlocked.
I'm currently at this stage https://www.hovatek.com/forum/thread-32664.html
DHTB Padding was 00 50 00 00 which is 20480
comparing with avbtool info_image the public keys match with exception to boot/recovery (tried boot partition with boot_key.bin and my own, the command below is with boot_key.bin)
Code:python2 avbtool make_vbmeta_image --key snow.pem --algorithm SHA256_RSA4096 --flag 2 --chain_partition boot:1:keys/boot_key.bin --chain_partition vbmeta_system:3:keys/vbmeta_system_key.bin --chain_partition vbmeta_vendor:4:keys/vbmeta_vendor_key.bin --chain_partition dtbo:5:keys/dtbo_key.bin --chain_partition socko:6:keys/socko_key.bin --chain_partition odmko:7:keys/odmko_key.bin --chain_partition recovery:2:keys/snow.bin --chain_partition l_modem:8:keys/l_modem_key.bin --chain_partition l_ldsp:9:keys/l_ldsp_key.bin --chain_partition l_gdsp:10:keys/l_gdsp_key.bin --chain_partition pm_sys:11:keys/pmsys_key.bin --chain_partition l_agdsp:12:keys/l_agdsp_key.bin --chain_partition l_cdsp:13:keys/l_cdsp_key.bin --padding_size 20480 --output vbmeta_custom.img
When flashing with fastboot flash vbmeta vbmeta_custom.img it gets stuck at writing 'vbmeta', tried also with fastboot --disable-verity and --disable-verification and both at once
I've attached all files that i'm using to make the image
(23-12-2020, 12:55 PM)snow43 Here's the unpadded vbmeta_custom.
Also https://onedrive.live.com/?authkey=%21AH...ion=locate this is the pac file incase you want to look.
(25-12-2020, 11:43 AM)snow43 No difference, stuck at Writing 'vbmeta'
(26-12-2020, 01:21 PM)snow43 Flashing is successful with vbmeta1.img but device gets into bootloop flashing the logo for 1s, i've managed to reflash the device, and try it again with signed boot img but same thing happens.