• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Teclast T30 T1P2 Root

Search This thread

RomerGG

Member
Mar 13, 2012
11
1
Gijón
A three versions of the hybrid ROM 1.04 / 1.05:
- last edited on 19 December 2020

Download:
Version 1.0 - Initial, first version (60Hz screen refresh rate), better touch response
Version 1.1 - version 1.0 plus pre-installed Magisk (Root)
Version 1.2a - version 1.0 plus pre-installed TWRP 3.3.1

Installation 1.0:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT6771_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Firmware upgrade"
- Turn off your tablet.
- Press “Download” button to start
- Connect your tablet into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- Reboot System

Installation 1.1:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT6771_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Firmware upgrade"
- Turn off your tablet.
- Press “Download” button to start
- Connect your tablet into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish !
- Reboot System
- Install Magisk Manager v7.5.1 or Magisk Manager v8.0.3

Installation 1.2a:
- Unpack FlashTools, and Click on Flash_tool.exe
- Select "scatter-Loading" and search MT6771_Android_scatter.txt in ROM
- Wait file to be added into Flash Tool
- Select "Download only"
- Turn off your tablet.
- Press “Download” button to start
- Connect your tablet into the computer via USB data cable.
- The process will start and a red progress bar will appear after color purple, yellow.
- And green circles display
- Finish
- Do not start tablet by normal way!!!
- To go to TWRP start the tablet by pressing and holding the Power and Vol+ buttons simultaneously, until text menu on tablet will appears
- On the tablet screen, use Vol+ to select "Recovery Mode", confirm the selection with the Vol-
- To control the TWRP connect the mouse to the tablet, because touch do not work in TWRP
- Click Cancel when prompted for a password
- Click on Wipe / Format Data / Swipe to confirm
- On question enter "yes"
- Click Back (3 times) and click to Reboot / Recovery!!!
- Install "DisableForceEncryption_Treble.zip"
- Install Magisk 21.1
- Click Reboot System
- Install Magisk Manager v8.0.3
- To easy access to TWRP instal Recovery reboot application

Note. Unfortunately, the touch does not work in TWRP, so a mouse and USB adapter must be used

Hello rbt07, first of all, thank you very much for your work, the rom is going fantastic.
I've been using the ROM for two months, since I use the tablet every day, but I have a problem that makes me have to uninstall it and I would not like to.

Since I installed it, I have continuous problems of disconnection from the wifi network, I get the error that the password is incorrect, but it makes no sense, because when I turn off and turn on the wifi again it reconnects correctly.

I have completely formatted the tablet, and reinstalled the rom about 3 times, but the wifi problem is still present.

If I am on a work call, it is very problematic to have to reconnect several times because of wifi downtime.

Can you take a look at the problem?
Do you need a log?

Thank you very much.
 

Werct

New member
Jul 29, 2021
3
1
Setting up a non-GSI Android 10 for T30 (Version from September 2020, VNDK 29)
You are doing everything described here at your own risk. Please read the manual and perform the steps carefully.
The TWRP recovery attached here is only usable with this vendor and partition table. Don't try to use it on Android 9 firmware or vendor.

Recovery:
  • No encryption (needed for proper recovery functioning, nothing can be done at this point (no known Mobicore TEE encryption implementation found))
  • Touchscreen doesn't work (use OTG mouse)
Firmware:
  • Screen brightness can be too dark in automatic mode (fix available, see "Bug fixing")
  • No Android 10 gesture toggle in settings (fix available, see "Bug fixing")
  • No Play Store, but Google Services are present (flash custom gapps to get Store, Opengapps Pico\Nano tested)
  • Android Webview from Google Play can't be used (fix available, see "Bug fixing")
  • Per-app battery statistics are not available (fix available, see "Bug fixing")
GSI:
  • Interface can be slow (fix available, see "Bug fixing")
  • 3.5mm jack doesn't function properly (fix available, see "Bug fixing")
    No need to fix manually for AOSP11 v311+ and GSIs based on it.
  • Screen brightness (fix available, see "Bug fixing")
    No need to fix manually for AOSP11 v311+ and GSIs based on it.
  1. Backup everything on the device, any data left will be wiped in the process.
  2. Write down the device's IMEI and MACs that belong to Bluetooth and Wi-Fi somewhere. They can be lost if this step is ignored.
  3. Unpack the firmware's archive (Link) and run Flashtool (Upgrade Tools\Upgrade Tools.exe). Select a firmware's scatter file in "Scatter-loading file" field (MT8788_O109_Q5L3X1\MT6771_Android_scatter.txt). Choose a "Format all + Download" method in a list below, then click a "Download" button. Then attach the turned off device to PC. Then a flashing process should start.
  4. Turn on the device. Go to the settings and enable developer settings. Enable "OEM unlocking" switch in the developer settings. Then reboot into fastboot and attach the device to PC. Execute "fastboot flashing unlock" and accept bootloader unlocking on the device.
  5. To restore IMEI and MACs please refer to the PDF document in the archive (教程.pdf) on how to use SN_writer (SN_Writer_Tool_exe_v1.1924.0.0\SN_Writer_Tool_exe_v1.1924.0.0\SN_Writer.exe). Basically, set the parameters as on the screenshots in the PDF and attach the turned off device to the PC.
  6. Boot to fastboot and attach the device to the PC. Then flash the recovery (Link) (fastboot flash recovery path-to-the-image); flash empty vbmeta (Link) to all three vbmeta partitions (fastboot flash vbmeta path; fastboot flash vbmeta_system path; fastboot flash vbmeta_vendor path). Flash modified super image (Link) (fastboot flash super path). The latter is needed to make system and vendor partitions writable to disable encryption and install gapps. Then format userdata partition (fastboot erase userdata). Do not reboot to system from here. If you do this, you need to format userdata from fastboot again.
  7. Reboot directly to the recovery (hold power button and Vol+, then select recovery). Format the data partition from there (Wipe->Format data->Yes). Reboot to recovery again (Reboot->Recovery).
  8. Copy encryption disabler zip (Link) to the device and flash it.
  9. Then you can boot to the system (Reboot->System).
Encryption disabler zip should be flashed every time a clean super image is flashed.
To set up a GSI on the new vendor, flash this super image either through fastboot (fastboot flash super path) or through image flashing option in the recovery (select "super" destination on the bottom of the list). Don't forget to apply encryption disabler before first boot into system. After flashing the super image, you can flash any GSI you want through recovery into "System Image" destination.
This super image contains an empty "product" partition, so there is more space in "system" partition to install a GSI (~3180Mb). It also contains AOSP10 as system image just for example.
Firmware:
  • Autobrightness is setting itself too dim occasionally:
    Replace an overlay package (Link) in "/vendor/overlay/FrameworkResOverlay/" and set 644 permissions.
  • Per-app battery statistics are not available:
    Apply the overlay from the item above (autobrightness fix). If you've already done this, there is no need to do anything.
  • No setting for Android 10 gestures:
    Enable ADB in developer settings and execute "adb shell cmd overlay enable com.android.internal.systemui.navbar.gestural" on PC.
  • Android System Webview from Google Play is not available to use:
    Copy an overlay package (Link) to "/vendor/overlay/", set 644 permissions, install Android System Webview from Google Play, reboot and check if it's available to use in developer options.
    Alternatively, you can use the Webview Manager magisk module.
GSI:
  • Interface is slow:
    Enable "Disable HW overlays" setting in Treble App.
  • 3.5mm jack is not working properly (Sound is coming from both heaphones and the device itself):
    If you use AOSP11 v311+ or GSIs that are based on it, there is no need to apply this fix.
    Try to enable "Force headset switch" setting in Treble App (it worked for me). But the proper way of fixing it is to copy a treble overlay (Link) to "/system/overlay/" ("/system_root/system/overlay/" from recovery) on Android 10 GSIs or to "/system/product/overlay/" ("/system_root/system/product/overlay/" from recovery) on Android 11 GSIs. Then set 644 permissions and reboot, the 3.5mm jack behavior should be fixed.
    If you use an old Android 11 GSI (older than AOSP11 v311 or some third-party GSI that doesn't contain new overlays) you need to use r\w compatible images (like vndk-lite variants of phhusson GSIs).
  • Screeen brightness is too dim (like on stock):
    If you use AOSP11 v311+ or GSIs that are based on it, there is no need to apply this fix.
    Apply the treble overlay from the item above (3.5mm jack fix).
The recovery here is based on this tree.
Webview overlay is compiled from source in this repository.
Firmware credits belong to Teclast, I guess.
 
Last edited:
  • Like
Reactions: rbt07

aryanhington

Senior Member
Aug 21, 2020
79
5
Setting up a non-gsi Android 10 for T30 (Version from September 2020, VNDK 29)
You are doing everything described here at your own risk. Please read the manual and perform the steps carefully.
The TWRP recovery attached here is only usable with this vendor and partition table. Don't try to use it on Android 9 firmware or vendor.

  • Screen brightness can be too dark in automatic mode (fixable through overlay modification)
  • No Android 10 gesture toggle in settings (you can use an ADB command to enable it)
  • No encryption (needed for proper recovery functioning, nothing can be done at this point (no known Mobicore TEE encryption implementation found))
  • No Play Store, but Google Services are present (fixable through custom gapps flashing, Opengapps tested (Nano))
  1. Backup everything on the device, any data left will be wiped in the process.
  2. Write down the device's IMEI and MACs that belong to Bluetooth and Wi-Fi somewhere. They can be lost if this step is ignored.
  3. Unpack the firmware's archive (Link) and run Flashtool (Upgrade Tools\Upgrade Tools.exe). Select a firmware's scatter file in "Scatter-loading file" field (MT8788_O109_Q5L3X1\MT6771_Android_scatter.txt). Choose a "Format all + Download" method in a list below, then click a "Download" button. Then attach the turned off device to PC. Then a flashing process should start.
  4. Turn on the device. Go to the settings and enable developer settings. Enable "OEM unlocking" switch in the developer settings. Then reboot into fastboot and attach the device to PC. Execute "fastboot flashing unlock" and accept bootloader unlocking on the device.
  5. To restore IMEI and MACs please refer to the PDF document in the archive (教程.pdf) on how to use SN_writer (SN_Writer_Tool_exe_v1.1924.0.0\SN_Writer_Tool_exe_v1.1924.0.0\SN_Writer.exe). Basically, set the parameters as on the screenshots in the PDF and attach the turned off device to the PC.
  6. Boot to fastboot and attach the device to the PC. Then flash the recovery (Link) (fastboot flash recovery path-to-the-image); flash empty vbmeta (Link) to all three vbmeta partitions (fastboot flash vbmeta path; fastboot flash vbmeta_system path; fastboot flash vbmeta_vendor path). Flash modified super image (Link) (fastboot flash super path). The latter is needed to make system and vendor partitions writable to disable encryption and install gapps. Then format userdata partition (fastboot erase userdata). Do not reboot to system from here. If you do this, you need to format userdata from fastboot again.
  7. Reboot directly to the recovery (hold power button and Vol+, then select recovery). Format the data partition from there (Wipe->Format data->Yes). Reboot to recovery again (Reboot->Recovery).
  8. Copy encryption disabler zip (Link) to the device and flash it.
  9. Then you can boot to the system (Reboot->System).
  • Autobrightness is setting itself too dim occasionally:
    Replace an overlay package (Link) in "/vendor/overlay/FrameworkResOverlay/"
  • No setting for Android 10 gestures:
    Enable ADB in developer settings and execute "adb shell cmd overlay enable com.android.internal.systemui.navbar.gestural" on PC
The recovery here is based on This tree.
Firmware credits belong to Teclast, I guess.
why not use a gsi instead?
 

Werct

New member
Jul 29, 2021
3
1
why not use a gsi instead?
UI there is faster for me, and it has more modern libraries and videodrivers, so it doesn't have some minor bugs that GSIs have (like chrome crash on video playback and MTP connection shutdown after some idle). Also Chrome-like 64-bit browsers had Vulkan rendering enabled by default, but is seems that's not the case anymore since version 92.
Also the new kernel (4.14) has lmkd instead of legacy low memory killer, and uses schedutil instead of schedplus scheduler (whatever it is, perhaps an mediatek proprietary technology).
 

aryanhington

Senior Member
Aug 21, 2020
79
5
UI there is faster for me, and it has more modern libraries and videodrivers, so it doesn't have some minor bugs that GSIs have (like chrome crash on video playback and MTP connection shutdown after some idle). Also Chrome-like 64-bit browsers had Vulkan rendering enabled by default, but is seems that's not the case anymore since version 92.
Also the new kernel (4.14) has lmkd instead of legacy low memory killer, and uses schedutil instead of schedplus scheduler (whatever it is, perhaps an mediatek proprietary technology).
I'm getting an issue where the screen truncates for a split second when the screen goes to sleep and turns off as shown https://streamable.com/7tilcn why is that?
 

muil

Member
Feb 12, 2021
16
3
Setting up a non-GSI Android 10 for T30 (Version from September 2020, VNDK 29)
You are doing everything described here at your own risk. Please read the manual and perform the steps carefully.
The TWRP recovery attached here is only usable with this vendor and partition table. Don't try to use it on Android 9 firmware or vendor.

Recovery:
  • No encryption (needed for proper recovery functioning, nothing can be done at this point (no known Mobicore TEE encryption implementation found))
  • Touchscreen doesn't work (use OTG mouse)
Firmware:
  • Screen brightness can be too dark in automatic mode (fix available, see "Bug fixing")
  • No Android 10 gesture toggle in settings (fix available, see "Bug fixing")
  • No Play Store, but Google Services are present (flash custom gapps to get Store, Opengapps Pico\Nano tested)
  • Android Webview from Google Play can't be used (fix available, see "Bug fixing")
  • Per-app battery statistics are not available (fix available, see "Bug fixing")
GSI:
  • Interface can be slow (fix available, see "Bug fixing")
  • 3.5mm jack doesn't function properly (fix available, see "Bug fixing")
    No need to fix manually for AOSP11 v311+ and GSIs based on it.
  • Screen brightness (fix available, see "Bug fixing")
    No need to fix manually for AOSP11 v311+ and GSIs based on it.
  1. Backup everything on the device, any data left will be wiped in the process.
  2. Write down the device's IMEI and MACs that belong to Bluetooth and Wi-Fi somewhere. They can be lost if this step is ignored.
  3. Unpack the firmware's archive (Link) and run Flashtool (Upgrade Tools\Upgrade Tools.exe). Select a firmware's scatter file in "Scatter-loading file" field (MT8788_O109_Q5L3X1\MT6771_Android_scatter.txt). Choose a "Format all + Download" method in a list below, then click a "Download" button. Then attach the turned off device to PC. Then a flashing process should start.
  4. Turn on the device. Go to the settings and enable developer settings. Enable "OEM unlocking" switch in the developer settings. Then reboot into fastboot and attach the device to PC. Execute "fastboot flashing unlock" and accept bootloader unlocking on the device.
  5. To restore IMEI and MACs please refer to the PDF document in the archive (教程.pdf) on how to use SN_writer (SN_Writer_Tool_exe_v1.1924.0.0\SN_Writer_Tool_exe_v1.1924.0.0\SN_Writer.exe). Basically, set the parameters as on the screenshots in the PDF and attach the turned off device to the PC.
  6. Boot to fastboot and attach the device to the PC. Then flash the recovery (Link) (fastboot flash recovery path-to-the-image); flash empty vbmeta (Link) to all three vbmeta partitions (fastboot flash vbmeta path; fastboot flash vbmeta_system path; fastboot flash vbmeta_vendor path). Flash modified super image (Link) (fastboot flash super path). The latter is needed to make system and vendor partitions writable to disable encryption and install gapps. Then format userdata partition (fastboot erase userdata). Do not reboot to system from here. If you do this, you need to format userdata from fastboot again.
  7. Reboot directly to the recovery (hold power button and Vol+, then select recovery). Format the data partition from there (Wipe->Format data->Yes). Reboot to recovery again (Reboot->Recovery).
  8. Copy encryption disabler zip (Link) to the device and flash it.
  9. Then you can boot to the system (Reboot->System).
Encryption disabler zip should be flashed every time a clean super image is flashed.
To set up a GSI on the new vendor, flash this super image either through fastboot (fastboot flash super path) or through image flashing option in the recovery (select "super" destination on the bottom of the list). Don't forget to apply encryption disabler before first boot into system. After flashing the super image, you can flash any GSI you want through recovery into "System Image" destination.
This super image contains an empty "product" partition, so there is more space in "system" partition to install a GSI (~3180Mb). It also contains AOSP10 as system image just for example.
Firmware:
  • Autobrightness is setting itself too dim occasionally:
    Replace an overlay package (Link) in "/vendor/overlay/FrameworkResOverlay/" and set 644 permissions.
  • Per-app battery statistics are not available:
    Apply the overlay from the item above (autobrightness fix). If you've already done this, there is no need to do anything.
  • No setting for Android 10 gestures:
    Enable ADB in developer settings and execute "adb shell cmd overlay enable com.android.internal.systemui.navbar.gestural" on PC.
  • Android System Webview from Google Play is not available to use:
    Copy an overlay package (Link) to "/vendor/overlay/", set 644 permissions, install Android System Webview from Google Play, reboot and check if it's available to use in developer options.
    Alternatively, you can use the Webview Manager magisk module.
GSI:
  • Interface is slow:
    Enable "Disable HW overlays" setting in Treble App.
  • 3.5mm jack is not working properly (Sound is coming from both heaphones and the device itself):
    If you use AOSP11 v311+ or GSIs that are based on it, there is no need to apply this fix.
    Try to enable "Force headset switch" setting in Treble App (it worked for me). But the proper way of fixing it is to copy a treble overlay (Link) to "/system/overlay/" ("/system_root/system/overlay/" from recovery) on Android 10 GSIs or to "/system/product/overlay/" ("/system_root/system/product/overlay/" from recovery) on Android 11 GSIs. Then set 644 permissions and reboot, the 3.5mm jack behavior should be fixed.
    If you use an old Android 11 GSI (older than AOSP11 v311 or some third-party GSI that doesn't contain new overlays) you need to use r\w compatible images (like vndk-lite variants of phhusson GSIs).
  • Screeen brightness is too dim (like on stock):
    If you use AOSP11 v311+ or GSIs that are based on it, there is no need to apply this fix.
    Apply the treble overlay from the item above (3.5mm jack fix).
The recovery here is based on this tree.
Webview overlay is compiled from source in this repository.
Firmware credits belong to Teclast, I guess.
I could install everything but the gsi because there is no system partition on twrp. I tried flashing system.img to Super and made a mess. Then tried on fasboot but there is not system partition. Any advise?
Update: I managed to install A12 gsi via fastbootd as fastboot and twrp are useless for the job. The prob now is twrp not completes booting so I can not flash magisk :(. I don't recommend anybody upgrading to A12 yet, the instalation is tricky and flipping windows is laggy.
(The flashing problem is now solved by the new twrp fixed by Werct).
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Is there no way to root without unlocking the bootloader first?

    Unlocking bootloader is useless for 90% of users
    Why ?:
    - Only for fastboot commands
    - Unlocking bootloader avoid warranty

    You can do lot of things without unlock:
    - Install TWRP (with Upgradetool)
    - Install custom system, logo, boot, etc ... with upgradetool

    and
    You can root without unlock:

    - Download firmware (T1P2) from teclast website and unpack in PC folder, ex: "T30_firm".
    - Download and install "MTK_USB_All_v1.0.8" for MTK drivers (search on google)
    - Connect your T30 to PC with usb
    - In "T30_firm/firmware" folder, copy "boot-verified.img" to you T30
    - Install magisk manager on your T30 an launch it
    - Choose install magisk by "patch a file", choose your "boot-verified.img" and wait
    - Now, you have a "magisk-patched.img" file in download folder
    - Copy "magisk-patched.img" on your "T30_firm" folder PC
    - Launch "Upgrade tools.exe" in "T30_firm/upgrade tool" folder
    - Unselect all "img" files
    - Select only "boot" line and choose your "magisk-patched.img" (click on same line, "location" column)
    - Shutdown your T30 (allways connected to pc)
    - Clic on "download" in upgrade tool and wait for big popup with green "V"

    You can disconnect you T30 and boot.
    Open magisk manager, "tada !" magisk is ready :)
    2
    Hello

    T1P4 firmware is available on Teclast china : http://www.teclast.com/tools/pad/putcode.html
    enter T1P4 and you will have baidu link for it (extract code: 2tbe)

    Carefull on this firmware:
    modem and efs partitions may be different to your tab (europe/us versions)

    but you can take recovery and boot verified img from this firmware.
    :)
    2
    Recovery

    Ok. Here is T1P4 recovery partition copied with dd.
    2
    When I got my T1P4 it rebooted a few seconds after turning off the screen. Eventually got $25 rebate for it.
    Then I flashed a magisk patched T1P2 boot.img and installed busybox, and now it works 100% without rebooting.