Alcatel TCL A502DL/A501DL root/custom recovery/custom roms?

Search This thread

lmgnsa

New member
Mar 20, 2021
3
1
Is there any way to get root/custom recovery/custom roms on the A502DL or A501DL? If so, how?
 
Solution
Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.
adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
Code:
fastboot oem unlock-go
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 erase recovery
fastboot flash recovery recovery.img
fastboot oem reboot-recovery
Then it should...

lehmancurtis

Senior Member
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
 
  • Like
Reactions: Hitti2

Hitti2

Senior Member
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?
 

lehmancurtis

Senior Member
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
 

0000.0000.00

Senior Member
Feb 13, 2017
179
45
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.
 

lehmancurtis

Senior Member
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.
 

0000.0000.00

Senior Member
Feb 13, 2017
179
45
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?
 

lehmancurtis

Senior Member
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.
 

lehmancurtis

Senior Member
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.
 

0000.0000.00

Senior Member
Feb 13, 2017
179
45

lehmancurtis

Senior Member
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.
 
  • Like
Reactions: 0000.0000.00

0000.0000.00

Senior Member
Feb 13, 2017
179
45
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Perhaps, good sir, I am incorrect on this point. If that is the case, I have no problem admitting I'm wrong and apologizing for the misinformation. So, for what i have been able to gather, device owners are using an MTK-based utility to dump the partition images. In turn, the boot image can be patched for Magisk systemless root and flashed back to the /boot partition using the same MTK tool. I'm also hearing about a Hydra tool that can unlock the bootloader. @PizzaG does this sound accurate? After all, good sir, since you called me out for being wrong, please clarify these points. Thanks
    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/mtkclient
    1
    @PizzaG thank you much for the information and the link. This is splendid news that a TracFone branded TCL device can at last be exploited..I look forward to unlocking mine.
    Again, I stand corrected for my misstatement and truly appreciate your guidance.
    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 journey
    1
    @PizzaG
    As an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads. These conditions obviously don't apply to your post, you or this thread. For this reason the reference to Telegram has been removed. Please refrain from sharing of social media links or attempts to drag members to them in future. Thanks for your cooperation!

    Regards
    Oswald Boelcke
    Senior Moderator
    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.
    1
    Here is the A502DL stock recovery and boot img/bin files and magisk patched boot bin/img and TWRP recovery also

  • 4
    @PizzaG
    As an exemption from the last bullet of rule no. 5 of the XDA Forum Rules, we grant only developers the privilege to share references to their social media in their own development threads. These conditions obviously don't apply to your post, you or this thread. For this reason the reference to Telegram has been removed. Please refrain from sharing of social media links or attempts to drag members to them in future. Thanks for your cooperation!

    Regards
    Oswald Boelcke
    Senior Mod

    :poop:(y):poop:

    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
    Bump. I found some information, but unfortunately the instructions are not very clear. I assume lehmancurtis means to go to fastboot with the boot mode tool, and then flash the TWRP.img with adb. However, I am not sure if this is the right way to do things and I do not have adb drivers for the A501DL or A502DL.
    adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
    Code:
    fastboot oem unlock-go
    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 erase recovery
    fastboot flash recovery recovery.img
    fastboot oem reboot-recovery
    Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
    And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
    1
    adb and fastboot include a generic Google driver and the VCOM driver installer for mtk includes what you'll need. Once in fastboot...
    Code:
    fastboot oem unlock-go
    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 erase recovery
    fastboot flash recovery recovery.img
    fastboot own reboot-recovery
    Then it should boot to TWRP. Be sure to format data f2fs to remove encryption so you can mount data.
    And you will need to install Magisk from recovery to have root and keep. OEM recovery from replacing TWRP.
    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 🥺
    1
    Make 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 tool
    1
    Here is the A502DL stock recovery and boot img/bin files and magisk patched boot bin/img and TWRP recovery also