Hovatek Forum MOBILE Android Teclast M40 bricked after magisk boot.img
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


Teclast M40 bricked after magisk boot.img

Teclast M40 bricked after magisk boot.img

Pages (2): 1 2 Next
snow43
snow43
snow43
Enthusiastic Member
7
21-12-2020, 02:58 PM
#1



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
This post was last modified: 21-12-2020, 03:40 PM by snow43.
hovatek
hovatek
hovatek
Administrator
49,570
21-12-2020, 07:16 PM
#2
(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

Is bootloader still unlocked?

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
snow43
snow43
snow43
Enthusiastic Member
7
22-12-2020, 02:07 PM
#3
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
This post was last modified: 22-12-2020, 06:29 PM by snow43.
Attached Files
.zip
avbtool.zip
Size: 68.73 KB / Downloads: 18
hovatek
hovatek
hovatek
Administrator
49,570
23-12-2020, 06:25 AM
#4
(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

I still spot other differences. Zip and attach the unpadded custom vbmeta_custom.img
This post was last modified: 23-12-2020, 06:44 AM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
snow43
snow43
snow43
Enthusiastic Member
7
23-12-2020, 12:55 PM
#5



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.
Attached Files
.zip
vbmeta_custom.zip
Size: 8.16 KB / Downloads: 13
hovatek
hovatek
hovatek
Administrator
49,570
25-12-2020, 11:18 AM
#6
(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.

Try flash this vbmeta and give feedback 
https://mega.nz/file/hSQljIAb#RymCQo8L4c...5SQOSmRnfQ

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
snow43
snow43
snow43
Enthusiastic Member
7
25-12-2020, 11:43 AM
#7
No difference, stuck at Writing 'vbmeta'
hovatek
hovatek
hovatek
Administrator
49,570
26-12-2020, 11:17 AM
#8
(25-12-2020, 11:43 AM)snow43 No difference, stuck at Writing 'vbmeta'

Yes. You'll notice that python avbtool info_image --image says its not a vbmeta image.
There was an error during creation
Try these two vbmetas. If they fail then that narrows it down to padding and flags
https://mega.ndz/file/EHAiAZ7C#rqC-5Awjg...0J5bDlDzXw
This post was last modified: 26-12-2020, 11:18 AM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
snow43
snow43
snow43
Enthusiastic Member
7
26-12-2020, 01:21 PM
#9
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.
hovatek
hovatek
hovatek
Administrator
49,570
26-12-2020, 02:51 PM
#10



(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.

The padding script needed to be adjusted for your model type. 
For the bootloop, ensure to patch boot using magisk canary, not normal magisk.
If you choose to root via recovery then either magisk should be fine

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Pages (2): 1 2 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram