Hovatek Forum DEVELOPMENT Android Teclast T40 Pro T1B1 Root - Help
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


Teclast T40 Pro T1B1 Root - Help

Teclast T40 Pro T1B1 Root - Help

Pages (2): 1 2 Next
thkgop001
thkgop001
thkgop001
Enthusiastic Member
12
28-08-2022, 07:16 PM
#1



Hi HovaTek team,



Requesting your help on my attempt to root Teclast T40 Pro T1B1.

At the moment, I get stuck a boot loop after flashing the Magisk-patched boot.img
Here are my steps as of now:





2.

Enter fastbootd

Flash the attached vbmeta using














fastboot flash vbmeta vbmeta-sign-custom.img

When rebooting, it still gets stuck in a boot loop - though the end of the loop is the Teclast splash screen with the moving circuitry












I managed to get around this boot loop by repeating Step 1 and then flashing the attached vbmeta using











fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta-sign-custom.img



At this point, I can boot into Android consistently.











3.








Enter fastbootd

Flash attached patched boot using






fastboot flash boot magisk.img

When rebooting, it gets stuck in a boot loop - this time the boot loop is much shorter.




I see this text on the device screen - right at the top



INFO: LOCK FLAG IS : UNLOCK!!!


Then it reboots over and over.




4.

At this point, I found your posts here





https://www.hovatek.com/forum/thread-32678.html




https://www.hovatek.com/forum/thread-32664.html



https://www.hovatek.com/forum/thread-32666.html





But I'm getting stuck right here with this error:


avbtool add_hash_footer: error: argument --image: invalid FileType('rab+') value: 'boot2.img'




This error is the same on both (1) my Windows 11 (with python 2 installed) as well as (2) my WSL-Ubuntu under my Windows.




I've attached my imgs, avbtool, rsa4096_vbmeta, etc here
https://www.filemail.com/d/uuukszxuglgqksi


Please could you help me?
Attached Files
.jpg
avbtool2.jpg
Size: 100.14 KB / Downloads: 3
.jpg
avbtool1.jpg
Size: 84.84 KB / Downloads: 1
hovatek
hovatek
hovatek
Administrator
49,617
29-08-2022, 09:40 AM
#2
(28-08-2022, 07:16 PM)thkgop001 Hi HovaTek team,

...

Please could you help me?

Try using WSL2 (Ubuntu sub system)

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
Gargoyle
Gargoyle
Gargoyle
Contributor
505
29-08-2022, 02:07 PM
#3
Try another version of Magisk, Magisk-v23.0 or Magisk-v24.3.

Magisk-v25.0 and higher didn't work for me on Unisoc SC9863A and T610, bootloop.

Or try this one, it's your stock_boot.img you uploaded, I used Magisk v23.0 and signed the rsa4096_vbmeta.pem key.
https://mega.nz/file/OUtwCYbB#GHwF-VM3nV...sIErVE6UxA
Gargoyle
Gargoyle
Gargoyle
Contributor
505
29-08-2022, 02:33 PM
#4
Did you extract the keys from vbmeta-sign.img?

I compared your custom with the factory, downloaded from the manufacturer's website, the l_agdsp key does not agree

factory key
Chain Partition descriptor:
Partition Name: l_agdsp
Rollback Index Location: 11
Public key (sha1): e93e7d91ba1a46b81a5f15129b4dc5769bf41f26

Your custom
Chain Partition descriptor:
Partition Name: l_agdsp
Rollback Index Location: 11
Public key (sha1): 2597c218aae470a130f61162feaae70afd97f011

this is the same as rsa4096_vbmeta.pem which is used for boot.img
Chain Partition descriptor:
Partition Name: boot
Rollback Index Location: 1
Public key (sha1): 2597c218aae470a130f61162feaae70afd97f011
thkgop001
thkgop001
thkgop001
Enthusiastic Member
12
30-08-2022, 05:38 AM
#5



Thank you, I'll try your patched boot file when time allows.

It didn't occur to me to use an older certain of Magisk. I did, however try the latest canary version of Magisk to patch the stock boot image file though I flashed it without signing it and ended up in a boot loop.

Regarding vbmeta, no I did not sign the keys myself. A fellow XDA member uploaded it for me so I'm not sure how it was signed. It successfully gets flashed without bootloop though I have to use the no verity flag.

Can I still use it with your patched boot image?
Gargoyle
Gargoyle
Gargoyle
Contributor
505
31-08-2022, 01:50 PM
#6
Yes you can use vbmeta with this boot.img, you still need to disable vbmeta verification,
or use a fixed vbmeta
https://mega.nz/file/OYMSnApS#PxZr13yVID...ciUTyWmEuY

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.
This post was last modified: 31-08-2022, 02:50 PM by Gargoyle.
thkgop001
thkgop001
thkgop001
Enthusiastic Member
12
31-08-2022, 07:42 PM
#7
(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
https://mega.nz/file/OYMSnApS#PxZr13yVID...ciUTyWmEuY

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
thkgop001
thkgop001
thkgop001
Enthusiastic Member
12
01-09-2022, 06:49 PM
#8
(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
https://mega.nz/file/OYMSnApS#PxZr13yVID...ciUTyWmEuY

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

Hi Gargoyle

Tried these combinations but always end up in the same boot loop

1. Your fixed vb_meta and then your boot.img

2. My vb_meta (from my first post) and then your boot.img

So I guess this means that I must get my Linux running in order to sign my patched boot.img? So far, I've put this off because I'm only running Windows...and the Ubuntu sub-system gets me stuck with that error: invalid FileType('rab+')

Do you think if I sign my patched boot.img in Linux, I'll achieve root?

And just to make sure I'm on the right track, the patched boot.img I need to sign, should be one that Magisk 23.0 patches, correct?

Thank you for your help
Gargoyle
Gargoyle
Gargoyle
Contributor
505
02-09-2022, 01:32 PM
#9
" 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:
https://mega.nz/file/CYUW2LRZ#XlZP6Pg8yz...o-hC6iLFYI
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.
This post was last modified: 02-09-2022, 02:01 PM by Gargoyle.
thkgop001
thkgop001
thkgop001
Enthusiastic Member
12
03-09-2022, 04:58 AM
#10
(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:
https://mega.nz/file/CYUW2LRZ#XlZP6Pg8yz...o-hC6iLFYI
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.

Hi Gargoyle

"Edit:
https://mega.nz/file/CYUW2LRZ#XlZP6Pg8yz...o-hC6iLFYI
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."

Appreciate all your help...thanks.

So I tried the 2 files you uploaded...
vb_meta works fine (though I have to use this command, otherwise boot loop right here itself) - note the vb_meta_b

fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta-sign.img

Android boots up fine and and then I tried flashing boot.img using

fastboot --disable-verity --disable-verification flash boot boot.img

Flashes successfully but still in a boot loop

So I'm guessing the manufacturer used his own custom key for signing? And that means I'm all out of luck on achieving root here?

No point doing all this again in Linux, or should I still give that a try?

The weird thing is that other users with a similar tablet seem to be achieving root without issues - https://forum.xda-developers.com/t/tecla...ot.4338751

N.B: BTW, the only reason I want root on this is to restore apk and data from another rooted device (using Alpha Backup or Titanium Backup)...any other way I can get this done without Magisk?

I've already tried a GSI ROM that had superuser baked in, and while it restores apks fine, it does not restore data...hence game progress can't be restored from my daughter's old tablet. I'm guessing this is because the old tablet was rooted with Magisk and this tablet (on the GSI) was rooted with superuser?

P.S: I made a backup of the Android folder from the old tablet; anything I can do with this to restore data to the apks with/without root?
Pages (2): 1 2 Next
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl