Teclast T40 Pro (T1A3) - Unisoc T618 unable to unlock bootloader
Teclast T40 Pro (T1A3) - Unisoc T618 unable to unlock bootloader
02-03-2025, 11:41 AM
Hello,
Hoping someone can help me with this.
Some background:
- I have previously owned a T40 Pro (T1B1) - Unisoc T618 and successfully unlocked the bootloader and rooted it thanks to this forum and XDA. (hovatek thread, xda thread posts 67-70)
- A couple of years ago I purchased the 2023 model of the T40 Pro (Z3D1) and was unable to unlock the bootloader. I was made aware that Teclast started using their own RSA key so this was a dead end. I returned the tablet. (hovatek hread)
- I also have the Teclast T40 Plus, which I have successfully bootloader unlocked and rooted.
Current issue:
I've recently acquired a 2nd hand T40 Pro (T1A3), which is from the same generation as the T1B1 (before Teclast started using their own RSA keys). I have seen posts on XDA in which the T1A3 model has been successfully rooted.
The problem is, I can't seem to unlock the bootloader. I've reflashed the stock 2022 firmware from Teclast via SPD, I can enable OEM unlocking in Android settings, but I just can't appear to unlock the bootloader using standard methods or with the identifier token.
Code:
>fastboot flashing unlock_bootloader signature.bin
Downloading 'unlock_message'
OKAY [ 0.005s]
unlocking bootloader
FAILED (remote: Unlock bootloader fail.)
Finished. Total time: 0.118sI'm wondering if the previous owner may have done something which is preventing me from unlocking, although I can't see what that may be considering I've reflashed the stock Teclast firmware and can enable OEM unlocking. I don't think there was any updated firmware for this device that would have used the new Teclast RSA key.
Looking for some troubleshooting device. During my research, I've come across this repo as a possible solution https://github.com/TomKing062/CVE-2022-3...ootloader/ but I'm not sure which file I'd use.
Thanks!
This post was last modified: 02-03-2025, 11:49 AM by jazzk.
02-03-2025, 05:26 PM
https://github.com/TomKing062/CVE-2022-3...230801.zip
02-03-2025, 06:44 PM
(02-03-2025, 05:26 PM)Amar13 hello, test this for unlock your bootloader :
https://github.com/TomKing062/CVE-2022-3...230801.zip
Thanks, I'll try it. Do I just need to run unlock_autopatch_512.bat?
02-03-2025, 08:23 PM
(02-03-2025, 06:58 PM)Amar13 Hello, Yes
I'm stuck on "Waiting for connection (300s)". Is the device supposed to be in fastboot or fastbootd when running it? Does the device have to be connected to the computer at this stage or can the script be run with the device connected?
Having trouble understanding the Wiki. Appreciate any tips.
30-04-2025, 04:38 PM
Toggle OEM unlock in developer settings
Power off device
Open device manager in Windows
Unplug USB
Run the unlock batch file - it will say "waiting for connection"
Hold volume-down and plug in USB.
* If an unknown device should show up. Open the properties for it and then you'll need to update the driver for it. This is the driver: https://androiddatahost.com/dsa6h
If you had to install the driver then unplug the USB and do volume-down and plug it in again.
The script will continue if you did everything correctly. Afterwards it will wipe your device.
Users browsing this thread:
2 Guest(s)
2 Guest(s)
Users browsing this thread:
2 Guest(s)
2 Guest(s)
