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

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

Search This thread
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...

0000.0000.00

Senior Member
Feb 13, 2017
179
45
Ah ok let me fix that lol. Check it now. You should be able to get it now.
,
I looked but I can't seem to find the a501dl in sugar, not sure if I'm missing something. I tried flashing a different model to see if that would work, I tried the alcatel tetra thing but it wouldn't flash and said something about com port in use and I restarted and tried installing vcom drivers again but same issue.
 

lehmancurtis

Senior Member
I looked but I can't seem to find the a501dl in sugar, not sure if I'm missing something. I tried flashing a different model to see if that would work, I tried the alcatel tetra thing but it wouldn't flash and said something about com port in use and I restarted and tried installing vcom drivers again but same issue.
Good thing it didn't flash the wrong ROM lol. The kernel would more than likely fry the digitizer at the least. With sugar you sometimes have to clear old devices stored as COM ports in device manager. Also, since the battery is considered non-removable, you have to be sure the phone is powered down. Go through the process of starting the flash before you plug the device to the computer. I've not checked the drop down menu for the a501dl, but it did have other files used to pull in the ROM for flashing. Not sure why they did one and not the other, but I am going to take a closer look. More to follow after I check it out.
 

0000.0000.00

Senior Member
Feb 13, 2017
179
45
Good thing it didn't flash the wrong ROM lol. The kernel would more than likely fry the digitizer at the least. With sugar you sometimes have to clear old devices stored as COM ports in device manager. Also, since the battery is considered non-removable, you have to be sure the phone is powered down. Go through the process of starting the flash before you plug the device to the computer. I've not checked the drop down menu for the a501dl, but it did have other files used to pull in the ROM for flashing. Not sure why they did one and not the other, but I am going to take a closer look. More to follow after I check it out.
ok, a501dl has a removable battery btw so I think you are confusing it with another model. When I started the process in sugar the phone stayed with the screen black and there was the mediatek vcom port in device manager
 

0000.0000.00

Senior Member
Feb 13, 2017
179
45
I was thinking about the a502dl that the battery doesn't come out of. Sorry about that. Is the a501 in the list of options in the drop down menu?
I’m not 100% sure here but I think the a501 might be referring to the Alcatel a501 which exists and is completely different from the tcl a501dl. The image sugar shows for the a501 doesn’t match the tcl a501dl but matches the Alcatel a501.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 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
    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
    I cannot get to fastboot even if I follow these steps... @williamhancock328` @lehmancurtis

    It still says "waiting port" forever.
    It sometime takes a few tries to get the phone and tool to do what its supposed to, but if you get the waiting message start over until the program reboots the device. It will work, it's just not a perfect process.
    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 🥺
    You need to modify a few files. It's almost just like the 5059 devices and you can look up the 5041c thread to see what needs edited. Use the fstab.mt6739 from the 5041c.
    1
    Here's the tool. I think some of the links to it got messed up. Make sure you turn on developer options and check that oem unlock is ticked as well as adb usb options. Once in fastboot, issue the following
    Code:
    fastboot oem unlock-go
    Follow the instructions on the device. Then boot into system and complete setup so that you can turn on developer options again since your device was just reset. Boot to fastboot once again and issue these.
    Code:
    fastboot flash recovery ./recovery.img
    Code:
    fastboot oem reboot-recovery
    That should be the custom recovery you just installed. It will be replace on reboot if steps are not taken. I was in the process of working this issue when my beat up a501dl succumbed to its varied and multiple impact injuries. If I can find the time to repair it I will finish where I left off, but in the mean time I will help as much as I can.