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

lmgnsa

New member
Mar 20, 2021
3
1
Use the boot mode tool from here for the a501dl. It definitely is unlockable! You can grab the TWRP.img I compiled for the a501dl from this link.
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.
 

lehmancurtis

Senior Member
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.
 
Last edited:
  • Like
  • Angry
Reactions: sj78 and lmgnsa
Solution

lmgnsa

New member
Mar 20, 2021
3
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 🥺
 
Last edited:
  • Like
Reactions: augustgenz

fliproc

New member
Mar 26, 2021
3
0
Thanks for the reply! I tried this tool, along with adb commands, etc., and I just can't even get fastboot. This would be an AWESOME phone, if not for this dumb crap!! The phone I had before this one is a Z717VL, and it sucks as well. They are both Tracfone phones that were given to me by my wife. I think I'll just get a Galaxy S8 or so and just root it instead. All other phones that I had on Verizon in the past have been super easy... just a One-Click-Root. Thanks everyone for your time and help!
 

sj78

Member
Mar 30, 2021
19
0
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.

Use a tool that controls bootmode. Mtk-mode-selector
Are you sure the method you thought of works? The bootmode tool you linked cannot get the A501DL to fastboot mode, it just says "waiting port" forever.
 

mickeybeats

New member
Dec 15, 2015
4
3
St. Louis
LG G8
  • Like
Reactions: lehmancurtis

sj78

Member
Mar 30, 2021
19
0
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
I have already installed the MTK VCOM drivers multiple times, I don't know why it still doesn't work.
 

lehmancurtis

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

To keep recovery from being replace several files need to be disable (various approaches are effective i.e. removed, replace, or renamed). Magisk usually handles this task, but sometimes there are exceptions. But, you need to address that before flashing gsi's for multiple reason and none are fun to deal with. Yes, this is A only and does not use A/B update method (at least not entirely as a few partitions are making use of the A/B partition labels). I've not been doing much with this particular device since mine was cracked and the usb port messed up when I got it, so nature took its course before I was able to achieve a fully stable custom setup.
 
Last edited:

lehmancurtis

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

lehmancurtis

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

lehmancurtis

Senior Member
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.
 
Last edited:
  • Like
Reactions: sj78

Hitti2

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

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