Alcatel TCL A502DL/A501DL root/custom recovery/custom roms?
- Thread starter lmgnsa
- Start date
Solution
Fastboot is hidden from conventional methods, but since it is a mtk device you should be able to use the mtk-boot-mode tool to reboot to fastboot. That is how I was able to access fastboot. The tool is a bit hit and miss and sometime you have to run it a few times to get it to work. I've built a few custom recoveries for the 502 and was able to use them before my display broke the rest of the way lol. The 501 is a very similar device. Mtk-su should give you a temp root (unless you have received the patch). If you are able to get anywhere with it, post the boot and recovery images and I'll build a custom recovery for it. Also, I can pack the other changes you will need to keep the stock ROM from replacing the recovery
I thought there is a twrp for this device, i downloaded it and was planing to flash.
Where can i download this mtk boot mode tool?
I put a link to the tool in my Alcatel idol 5 thread. The recovery is for the 502 which is very similar but the kernels are slightly different. But it wouldn't take me very long at all to compile one specifically for the 501 once I have the boot.img
I spent about 3 hours trying to enter Bootloader mode, i was unable to enter using mtk boot selector, or adb to bootloader
I may have a solution if you know how to use adb. Are you using Windows or Linux? Have you checked to see if mtk-su gives you root?
I don't know why I asked about which OS. The tool only works on Windows. Also when you tried the tool did your phone reboot? If so were you holding vol(-)?
Follow the readme file and you should be able to access fastboot mode as long as mtk-su works on your device. Same goes for the 502.
I have the tcl a1 (a501dl) and I tried using mtk-su but I get this error
Failed critical init step 4
UID: 2000 cap: 0000000000 selinux: enforcing
Not sure why I'm getting that error
I tried using the mtk-bootmode took but it didn't seem to work not sure what I did wrong there I tried rebooting and pressing volume down when rebooting or turning phone off and holding volume down and then plugging phone in but all of that didn't seem to work since the tool got stuck on "Waiting port" when trying to enter fastboot
I wasn't sure how to install the vcom drivers so I installed them from here and used the automatic installation.
The phone has a security patch level of February 5, 2020 so not sure why mtk-su doesn't work.
I did look at device manager and noticed a mediatek preloader thing appearing for a few seconds during boot.
You have the patched version on your device. I'm not sure if we have a work around for this device yet or not. You would need to be able to flash the older stock ROM. Well, the lk binary is usually the only thing that needs to be downgraded.
I looked but wasn't able to find any stock firmware for this phone. Has the mtk bootmode tool been patched or was I using it wrong?
The tool hasn't been patched but I didn't create it so I am not sure what it uses in order to write to the misc partition in order to call for the device to boot into fastboot mode. My guess is that it used mtk-su or something very similar in order to gain the required permissions. Alcatel patched the lk binary disabling the exploit. That being said, it is possible that the patch also killed the tool. I don't know this for sure but the timing fits. I'll dig a bit deeper to see if I can verify this though.
Install Sugar_MTK. I just checked and a501 is supported. Follow the instructions in the Alcatel Tetra guide for using sugar to replace your lk binary. Use the lk from the zip I posted earlier in this thread.
How do you login to sugar mtk I tried the login info I found online but it didn't work I tried Username: SUBRECella and Password: Rampasbt12!
There are a handful of different packages of Sugar floating around. Some of them are duds lol. I will try to share the exact one I have once I'm able to access my machine.
This is a screenshot of the error I'm getting https://gyazo.com/77940c6dc66ba36d24bf9a289babd225
If I paste in a username and password that's different from those credentials which you said were correct, I get this error instead https://gyazo.com/b9f5f3dc407b360fcdfb52e24a4a838d
I got sugar from here and downloaded the newest version
I've never seen either of those errors. But, I have a message when I start mine that says forbidden version lol. I'll get it linked asap.
I did also try a few different versions and even tried following some youtube tutorials but none of them seem to have worked to let me login to sugar. I tried sugar in a virtual machine as well but that didn't let me get past login either.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
1
You are correct good sir on MTK Client. Hydra is a Paid solution people usually use to network unlock their devices and I know little to nothing about that aspect. I know for a fact that MTK Client will Bootloader Unlock Both the A501DL(device I own) as well as the A502DL(a user in my telegram group had one).
The process looks like this for MTK Client.
-Make a dump of the whole device
-Magisk Patch the boot.img(boot.bin)
-Use MTK Clienbt to Flash patched boot.img
-Enjoy!!
I have twrp and custom stock for A501DL. Since I don't have the A502DL, I personally have done nothing with it.
here is the github link for MTK Client
https://github.com/bkerler/mtkclient1
no worries bud, happy to help whenever I can. I can also dump and build twrp. If you need a hand, join my Telegram and I'll see what I can do. Best of luck on your journey1
Thank god you saved the day from us joining a telegram group that we wanted to join to discuss this topic further in depth... Smh.1Here is the A502DL stock recovery and boot img/bin files and magisk patched boot bin/img and TWRP recovery also
TCL_LX_A502DL_Files.zip | by Privyetcyka for Generic Device/Other
Download GApps, Roms, Kernels, Themes...www.androidfilehost.com
-
4
as a side note, to my recollection, there is no dev in this thread doing anything with this device except me, so I fail to see how your quote to rule 5 pertains to this thread. Seems to me this is just a random thread about a random device. What you are essentially doing is cutting off everyone from test releases and general info about this device in favor of forcing people to stay on your site. I get it but I feel that goes against the whole dev community. But that's fine anyways, it is not worth my time to try and fight XDA mods over outdated rules and regulations and sharing my time and energy, I'm scrapping this project... My personal dev routine is to hop on XDA and see what's available for a device, I contact all threads related and drop some info and a link to my TG group. Once I get a tester I usually put out several test releases/bug fixes and then at that point, I will go ahead and make my own xda post for said device with mostly tested releases. I honestly can't be bothered with the slow trickle of info and chat that you find with a forum as my personal time is important to me and I don't have alot of it to sit around waiting for responses and feedback and such. Again, I understand you XDA Mods are trying to keep people on your site but I seriously can't relate and at what point does this not become Bullying?1
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Follow the instructions on your device to unlock the bootloader. Then boot to system and reboot to fastboot with bootmode tool. Once in fastboot...Code:fastboot oem unlock-go
Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.Code:fastboot erase recovery fastboot flash recovery recovery.img fastboot oem reboot-recovery
And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.1
Just to confirm:
To prevent the OEM recovery from replacing TWRP, I have to flash Magisk.
If I flashed a gsi, would this problem still be present?
edit: if I wanted to flash a gsi, would I be able to flash "A" only roms, "AB" only roms, or A/AB roms?
edit2: @lehmancurtis plz help me
1Make sure to install the MTK VCOM drivers first, the android drivers from google or samsung will not work!
I was able to bootloader unlock my Alcatel 3T 8, even being on tmobile using the boot selector toolMediatek USB VCOM Drivers (all MTK devices).zip | by www.foldertips.com for Utilities
Download GApps, Roms, Kernels, Themes...androidfilehost.com
1Here is the A502DL stock recovery and boot img/bin files and magisk patched boot bin/img and TWRP recovery also
TCL_LX_A502DL_Files.zip | by Privyetcyka for Generic Device/Other
Download GApps, Roms, Kernels, Themes...
