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

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.
 
D

Deleted member 11575455

Guest
I've got a A501DL, I enabled usb debugging and oem unlock, seems like the A501DL in fastboot does not talk with the pc, i've installed so many driver things its crazy butat fastboot when typing fastboot reboot bootloader, it reboots the phone but it skips fastboot and turns on to my home screen, I used volume up and power, I get in fast boot butthe device isnt being detected by windows 10 64 bit. Also in fast boot there is only
reboot system now
wipe data/factory reset
wipe cache partition
power off

im going nut that fastboot isnt working with this device.
BootLoader UNLOCKED folks, You can use mtkclient. I will release custom recovery and custom stock if anyone wants it

twrp device tree made, twrp built and it works
 
Last edited by a moderator:
D

Deleted member 11575455

Guest
i can flash it but adb sideloading, sdcard and usb otg mounting dont work. it also can't mount data due to the encryption
ya, it has a few fstab issues I need to fix for mounting external sd and usb-otg. I'm working on Custom Stock now that kills encryption and other security to get ready for GSI Roms

Testing Custom Stock Rom now
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    D
    Deleted member 11575455
    @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?
    2
    BTW, I've finally gotten twrp to compile for me, so now that I've got the build system worked out and the proper device setup, i'll have the kinks worked out of our twrp in the next few days! Once I get a normal twp compiled, then I'll compile us an orangefox or something too....
    2
    Here is the A502DL stock recovery and boot img/bin files and magisk patched boot bin/img and TWRP recovery also

    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