Closed 4aiman closed 3 months ago
hi I have a teclast t50 pro (mediatek G99). I also had a doogee t30 pro and a Headwolf HPad6. All are G99. All SLAs etc. are false. All of these have the same problem with MTK_DA_V6.bin as you do. However, if I use DA_BR.bin from the firmware of the tablet I own, all of my tablets are recognized by mtkclient. Try getting DA_BR.bin from the firmware you have. Or, as I did, you may be able to use DA_BR.bin from a model you don't have.
I'm not a developer, so I just renamed DA_BR.bin to MTK_DA_V6.bin and used it.
hi I have a teclast t50 pro (mediatek G99). I also had a doogee t30 pro and a Headwolf HPad6. All are G99. All SLAs etc. are false. All of these have the same problem with MTK_DA_V6.bin as you do. However, if I use DA_BR.bin from the firmware of the tablet I own, all of my tablets are recognized by mtkclient. Try getting DA_BR.bin from the firmware you have. Or, as I did, you may be able to use DA_BR.bin from a model you don't have.
I'm not a developer, so I just renamed DA_BR.bin to MTK_DA_V6.bin and used it.
I have a Headwolf HPad5. I've tried a bunch of DA_BR.bin files found via Google but none has worked. How did you get one from the firmware of your HPad6? Can you share one that works with your HPad? It might work with mine too.
hi I have a teclast t50 pro (mediatek G99). I also had a doogee t30 pro and a Headwolf HPad6. All are G99. All SLAs etc. are false. All of these have the same problem with MTK_DA_V6.bin as you do. However, if I use DA_BR.bin from the firmware of the tablet I own, all of my tablets are recognized by mtkclient. Try getting DA_BR.bin from the firmware you have. Or, as I did, you may be able to use DA_BR.bin from a model you don't have. I'm not a developer, so I just renamed DA_BR.bin to MTK_DA_V6.bin and used it.
I have a Headwolf HPad5. I've tried a bunch of DA_BR.bin files found via Google but none has worked. How did you get one from the firmware of your HPad6? Can you share one that works with your HPad? It might work with mine too.
I used DA_BR.bin from teclast t50 pro (a6d4). This firmware is officially released by teclast. DA_BR.bin from doogee t30 pro also worked with hpad6.
Firmware for alldocube G99 series has also been officially released. I haven't tried it, but it might work.
Thanks for the help, @rusantiman!
Unfortunately, as I've stated in the opening post, there's no firmware for my device (KENSHI E12) in the wild.
I've tried DA_BR.bin from Teclast t50 and it did help getting into the device after 2 reboots 🥳
(Removed MTK_DA_V6.bin
, copied DA_BR.bin
and renamed DA_BR.bin
-> MTK_DA_V6.bin
)
[11:05:18]: Device detected :)
[11:05:37]: [Errno 5] Input/Output Error
[11:05:38]: Device detected :)
[11:05:38]: Device is unprotected.
[11:05:38]: Device is in BROM-Mode. Bypassing security.
[11:05:38]: Failed to dump preloader from ram, provide a valid one via --preloader option
[11:05:38]: Uploading xflash stage 1 from MTK_DA_V6.bin
[11:05:38]: Successfully uploaded stage 1, jumping ..
[11:05:44]: Stage 1 successfully loaded.
[11:05:44]: Uploading stage 2...
[11:05:44]: Successfully uploaded stage 2.
[11:05:44]: Successfully uploaded stage 2
[11:05:44]: SLA is disabled
Question is, does a preloader from a different device break anything? Like, can I safely backup the device and be sure that the backup doesn't have anything to do with the teclast t50?
Edit: While we're at it: do I need to generate keys? MTK Client freezes if I try.
If you can get it to work, it's probably ok for reading and even writing. Try reading and writing a non-essential partition first, like something on a _b slot.
I think this can be marked as solved, since I did get a backup of all partitions and was able to flash those back (some of them anyway). Didn't manage to root the device, but oh, boy, is it nice to have a backup ;)
Similar to #361, my device (equipped with MT6789) is stuck right after
Jumping to 0x200000
.Key notes:
Status: Waiting for PreLoader VCOM, please reconnect mobile to brom mode
Jumping to 0x200000
Jumping to 0x200000
for a couple of minutes or so) it spits outDeviceClass - USBError(5, 'Input/Output Error')
but not always.debug log
section does it show the following: