I've tried the TWRP *.img given in the link above and I can confirm it can be launched on Teclast P80X (G5K4 variant - the one with USB Type-C connector).
However, it has some troubles to be used.
I'm not an expert about TWRP debugging, but I can confirm at least 2 things:
- The SD Card storage cannot be mounted, so it's not possible to navigate through it.
- When I try to retrieve the internal storage data of the tablet memory, I can't found any folder giving acess to it.
By the way, browsing the shown folders seems to give scrambled folder and file names.
The good news is that TWRP system is launched without issue, but the bad one is that it can't be used as is right now.
Can I know if this TWRP *.img was built from a specific P80X firmware?
Maybe the issues I've raised are due to the fact that I'm using a G5K4 variant and not a G5K1 variant?
I know that it exists 3 variant of this tablet:
- G5K1 -> First release with a Micro USB connector and spread with 2 type of firmware, a Chinese one (CN - without Gapps) and a Worldwide one (WW - with Gapps).
- G5K2 -> Korean market specific. A release using almost the same HW as the G5K1 but using a different Modem and Wifi module with a. Worldwide Firmware.
- G5K4 -> The last known release from my own research. The difference with the G5K1 is the USB connector that is USB 3.0 Type-C and not Micro-USB anymore and it it has probably another modification on the PMIC power management chip but I don't know if it's SW or HW related. Spread with 2 type of firmware, a CN and a WW one, but only the CN one is available for download at Teclast support site.
I know all of this because I've made a mistake applying the G5K4 CN firmware and I discovered after action that there was 2 firmware variant...
Now I can't go back to the original firmware present at delivery and I have to deal with the CN firmware until Teclast release the WW one, but thanks to Hovatek efforts, I was able to root my device and add the needed Google services manually.
f TWRP is working, I'll try to install the openGapps package with it.
I stay at your disposition if you want me to do other tests.
(23-03-2020, 03:00 AM)djelloul Wrote: I've tried the TWRP *.img given in the link above and I can confirm it can be launched on Teclast P80X (G5K4 variant - the one with USB Type-C connector).
However, it has some troubles to be used.
I'm not an expert about TWRP debugging, but I can confirm at least 2 things:
- The SD Card storage cannot be mounted, so it's not possible to navigate through it.
- When I try to retrieve the internal storage data of the tablet memory, I can't found any folder giving acess to it.
By the way, browsing the shown folders seems to give scrambled folder and file names.
The good news is that TWRP system is launched without issue, but the bad one is that it can't be used as is right now.
Can I know if this TWRP *.img was built from a specific P80X firmware?
Maybe the issues I've raised are due to the fact that I'm using a G5K4 variant and not a G5K1 variant?
I know that it exists 3 variant of this tablet:
- G5K1 -> First release with a Micro USB connector and spread with 2 type of firmware, a Chinese one (CN - without Gapps) and a Worldwide one (WW - with Gapps).
- G5K2 -> Korean market specific. A release using almost the same HW as the G5K1 but using a different Modem and Wifi module with a. Worldwide Firmware.
- G5K4 -> The last known release from my own research. The difference with the G5K1 is the USB connector that is USB 3.0 Type-C and not Micro-USB anymore and it it has probably another modification on the PMIC power management chip but I don't know if it's SW or HW related. Spread with 2 type of firmware, a CN and a WW one, but only the CN one is available for download at Teclast support site.
I know all of this because I've made a mistake applying the G5K4 CN firmware and I discovered after action that there was 2 firmware variant...
Now I can't go back to the original firmware present at delivery and I have to deal with the CN firmware until Teclast release the WW one, but thanks to Hovatek efforts, I was able to root my device and add the needed Google services manually.
f TWRP is working, I'll try to install the openGapps package with it.
I stay at your disposition if you want me to do other tests.
We've launched TWRP Porter v1.4. Try it out and give feedback
Tried both your new TWRP v3.3.1 release and TWRP v1.4 porter generated recovery.
They needed to be signed for vbmeta signature checking but both variant where able to launch on the device.
This time, the SD Card can be mounted and every files and folders are accessible.
The internal storage access (/sdcard) gives same scrambled result as before.
I also tried to check the content of data partition (/data) and I can see the name of the file and folders that are just under it, but when I browse each of these folders, the same scrambled folder and filename appear, as in previous Internal Storage browsing.
Other partitions seems OK, because I'm able to mount the system (/system), product (/product) and vendor (/vendor) partition and explore them without problem.
I'm sure of that because I've made manual modification in the /system/app and system/priv-app folders that I'm able to see from TWRP file manager.
However when mounted, the access path is /system/system and not /system as I'm used to see in other devices, but it's maybe due to the system_as_root partition layout you described in the P80X Root procedure topic.
What do you think?
Do you have an idea why the internal storage and data partition doesn't looks as it should under TWRP interface?
For information my device is not encrypted.
Do you have an idea why the internal storage and data partition doesn't looks as it should under TWRP interface?
For information my device is not encrypted.
Thank you very much for your kind help.
Can you send a screenshot of what you see so I compare to mine
(02-07-2020, 11:07 AM)rocapri Wrote: Why i can't flash TWRP?
create a new thread for your device issue by clicking "Ask Question" at the top
in the new thread, state your device model and properties and error message you encountered
Website
Find
Reply