Hovatek Forum DEVELOPMENT Android TECLAST P80X G5K8
Try our Online TWRP Builder..its free!
Can't login? Please, reset your password.


TECLAST P80X G5K8

TECLAST P80X G5K8

mocarela
mocarela
mocarela
Enthusiastic Member
7
20-11-2021, 10:12 AM
#1



I have TECLAST P80X G5K8 tablet (Android 9). I found the stock firmware and I'm able to flash it if it gets bricked.

I also successfully unlocked bootloader using this guide: https://www.hovatek.com/forum/thread-32287.html

The problem now is that I'm not able to root it.
Without creating and flashing custom signed vbmeta any other partition gets stuck on write when trying to flash it.
Using custom signed vbmeta (following https://www.hovatek.com/forum/thread-32678.html) I can perform flash of a recovery.image (signed with rsa4096_vbmeta.pem), but can't enter recovery afterwards. The tablet still boots if playing with recovery partition (and doesn't at all if playing with boot partition), but as I said can't enter recovery (and fasboot) anymore. I used several types of recovery... patched with Magisk, created with TWRP Porter, found on internet (probably for models G5K4 and G5K1) to no avail.

What am I doing wrong?
Do I have to use fastboot from the package for unlocking the bootloader also to flash the signed images?
My vbmeta has identical content as in https://www.hovatek.com/forum/thread-32666.html, so I just took the prepared bundle of private keys (+ one generated from rsa4096_vbmeta.pem).
Could I be using a wrong Magisk Manager? If I'm not mistaken it updates itself to the latest version before I'm able to patch anything, whatever version I install.
This post was last modified: 20-11-2021, 01:22 PM by mocarela.
hovatek
hovatek
hovatek
Administrator
49,597
21-11-2021, 07:50 AM
#2
(20-11-2021, 10:12 AM)mocarela ...
What am I doing wrong?
Do I have to use fastboot from the package for unlocking the bootloader also to flash the signed images?
My vbmeta has identical content as in https://www.hovatek.com/forum/thread-32666.html, so I just took the prepared bundle of private keys (+ one generated from rsa4096_vbmeta.pem).
Could I be using a wrong Magisk Manager? If I'm not mistaken it updates itself to the latest version before I'm able to patch anything, whatever version I install.

Patch boot using magisk canary instead.
Hope you know you need to create a custom vbmeta for flashing a modified boot.img
This post was last modified: 21-11-2021, 07:51 AM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
mocarela
mocarela
mocarela
Enthusiastic Member
7
22-11-2021, 12:57 PM
#3
(21-11-2021, 07:50 AM)hovatek Patch boot using magisk canary instead.
Hope you know you need to create a custom vbmeta for flashing a modified boot.img

Should I then flash it to recovery or boot?
Additional question... would be a test regarding custom vbmeta valid, if I perform an entire procedure with stock without patching it with Magisk? This way if it doesn't work, then the problem is in my procedure and if it works, then the problem would be in Magisk, right?
Thanks
mocarela
mocarela
mocarela
Enthusiastic Member
7
22-11-2021, 05:10 PM
#4
(22-11-2021, 12:57 PM)mocarela
(21-11-2021, 07:50 AM)hovatek Patch boot using magisk canary instead.
Hope you know you need to create a custom vbmeta for flashing a modified boot.img

Should I then flash it to recovery or boot?
Additional question... would be a test regarding custom vbmeta valid, if I perform an entire procedure with stock without patching it with Magisk? This way if it doesn't work, then the problem is in my procedure and if it works, then the problem would be in Magisk, right?
Thanks

So I did the above described test (everything except Magisk patch) and it works. So, my problem is in the step where I patch the stock boot image with Magisk.
Which version should I use? With bf80b08b it hangs on logo, with 7e9d4512(23014) it bootloops. With two other versions it's the same. Does anybody know which version is right?

This is the output of Magisk 20.4 run on a Linux box (x86):

Parsing boot image: [./boot.img]
HEADER_VER [1]
KERNEL_SZ [17014040]
RAMDISK_SZ [0]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
OS_VERSION [9.0.0]
OS_PATCH_LEVEL [2019-05]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyS1,115200n8 buildvariant=user]
CHECKSUM [5405cb0e89cdfc0dc51e866b75080e14a325cd6b000000000000000000000000]
KERNEL_FMT [raw]
RAMDISK_FMT [raw]
Add entry [init] (0750)
Patch with flag KEEPVERITY=[false] KEEPFORCEENCRYPT=[false]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
Patch @ 00C63A26 [736B69705F696E697472616D667300]->[77616E745F696E697472616D667300]
Parsing boot image: [./boot.img]
HEADER_VER [1]
KERNEL_SZ [17014040]
RAMDISK_SZ [0]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
OS_VERSION [9.0.0]
OS_PATCH_LEVEL [2019-05]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyS1,115200n8 buildvariant=user]
CHECKSUM [5405cb0e89cdfc0dc51e866b75080e14a325cd6b000000000000000000000000]
KERNEL_FMT [raw]
RAMDISK_FMT [raw]
Repack to boot image: [new-boot.img]
HEADER_VER [1]
KERNEL_SZ [17014040]
RAMDISK_SZ [593716]
SECOND_SZ [0]
RECOV_DTBO_SZ [0]
OS_VERSION [9.0.0]
OS_PATCH_LEVEL [2019-05]
PAGESIZE [2048]
NAME []
CMDLINE [console=ttyS1,115200n8 buildvariant=user]
CHECKSUM [7e4cf69c844d4a20bfe78492a8c120b73689cf78000000000000000000000000]

Looks OK to me. But again hanging on boot logo.
This post was last modified: 22-11-2021, 09:02 PM by mocarela.
hovatek
hovatek
hovatek
Administrator
49,597
23-11-2021, 09:20 AM
#5



(22-11-2021, 05:10 PM)mocarela ..
Looks OK to me. But again hanging on boot logo.

First, you create a custom vbmeta where you swap the keys for boot partition to your custom key
then you patch your boot partition using magisk canary version, sign it then flash
This was how we rooted our copy of the teclast p80x using magisk canary version and boot.img flashed to boot partition

This post was last modified: 23-11-2021, 09:23 AM by hovatek.

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
mocarela
mocarela
mocarela
Enthusiastic Member
7
23-11-2021, 06:16 PM
#6
(23-11-2021, 09:20 AM)hovatek First, you create a custom vbmeta where you swap the keys for boot partition to your custom key
then you patch your boot partition using magisk canary version, sign it then flash
This was how we rooted our copy of the teclast p80x using magisk canary version and boot.img flashed to boot partition

Done exactly like that. As mentioned, omitting just the Magisk step works as expected.
I don't doubt you successfully root the teclast p80x, but was it model G5K8?
Please, would you be so kind to patch boot.img from either of stock roms (P80X(G5K8)_Android9.0_EEA_V1.01_SZ or P80X(G5K8)_Android9.0_EEA_V1.02_SZ_NV) I can provide?
hovatek
hovatek
hovatek
Administrator
49,597
24-11-2021, 07:58 AM
#7
(23-11-2021, 06:16 PM)mocarela Done exactly like that. As mentioned, omitting just the Magisk step works as expected.
I don't doubt you successfully root the teclast p80x, but was it model G5K8?
Please, would you be so kind to patch boot.img from either of stock roms (P80X(G5K8)_Android9.0_EEA_V1.01_SZ or P80X(G5K8)_Android9.0_EEA_V1.02_SZ_NV) I can provide?

Our copy is the G5K1 but it shouldn't be so different from yours.
We're very occupied at the moment and are unable to patch / sign for you .
Let's focus on recovery first before we move to boot.
If you're rooting with the recovery partition, you must avoid booting to home screen before then trying to enter recovery mode because recovery-from-boot.p would've swapped the recovery image you flashed with stock recovery whose signature won't match what you have in vbmeta, hence it getting stuck at logo / failing.

Once you flash the signed magisk-patched recovery in fastboot, power off using the guide @ https://www.hovatek.com/forum/thread-32663.html
From off state, you then attempt to boot into recovery mode. The device will boot up normally. check if you have root

Note!
We have a reply schedule for Free Support. Please upgrade to Private Support if you can't wait.
mocarela
mocarela
mocarela
Enthusiastic Member
7
25-11-2021, 07:04 PM
#8
(24-11-2021, 07:58 AM)hovatek Let's focus on recovery first before we move to boot.

This was the key to the solution. Everything is fine now after going the recovery way.
Thanks a lot!!!!!!!!!
Users browsing this thread:
 1 Guest(s)
Users browsing this thread:
 1 Guest(s)
YtWhTl
live chat
whatsapp telegram instagram