TECLAST P80X G5K8
TECLAST P80X G5K8
(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.
(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
(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
(22-11-2021, 05:10 PM)mocarela ..
Looks OK to me. But again hanging on boot logo.
(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
(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?