Teclast T40 Pro T1B1 Root - Help
Teclast T40 Pro T1B1 Root - Help
(28-08-2022, 07:16 PM)thkgop001 Hi HovaTek team,
...
Please could you help me?
(31-08-2022, 01:50 PM)Gargoyle Yes you can use vbmeta with this boot.img, you still need to disable vbmeta verification,
or use a fixed vbmeta
[ Login to download]
Without the need to disable vbmeta verification, you can also try locking the bootloader, the device will be rooted even with a locked bootloader, it's up to you if you leave it unlocked, re-lock doesn't affect root, just install Magisk Manager v23.0.
Edit:
Magisk Patched boot.img must always be signed, without signing it will cause a bootloop.
(31-08-2022, 07:42 PM)thkgop001(31-08-2022, 01:50 PM)Gargoyle Yes you can use vbmeta with this boot.img, you still need to disable vbmeta verification,
or use a fixed vbmeta
[ Login to download]
Without the need to disable vbmeta verification, you can also try locking the bootloader, the device will be rooted even with a locked bootloader, it's up to you if you leave it unlocked, re-lock doesn't affect root, just install Magisk Manager v23.0.
Edit:
Magisk Patched boot.img must always be signed, without signing it will cause a bootloop.
Thank you for this. I'll try this and revert with feedback
(02-09-2022, 01:32 PM)Gargoyle " Do you think if I sign my patched boot.img in Linux, I'll achieve root?"
I don't think the result will be the same.
Try flashing vbmeta with disable-verification, then patched and signed boot.img,
I suspect the manufacturer didn't use the rsa4096_vbmeta.pem public key to sign vbmeta, that's probably why it doesn't work.
Edit:
[ Login to download]
Try these two files, it's stock boot without magisk and vbmeta without changes with original keys, only signed rsa4096_vbmeta,
if the device does not boot it is 100% sure that the manufacturer used a custom key for vbmeta to sign vbmeta, i doubt you will get his key to create your own vbmeta.