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...
sweet, i got a few a501dls to test it out once youre ready
not going good, I'm getting secureboot failure and nothing boots but twrp. mtkclient doesn't write vendor or system. Nor dumps system. Confused, bootloader says unlocked, unsure how to proceed

Update: Somehow booting again and got rid of encryption in the process
 
Last edited:

luridphantom

Senior Member
Apr 4, 2021
200
40
GT-i9250
AT&T Samsung Galaxy S III
not going good, I'm getting secureboot failure and nothing boots but twrp. mtkclient doesn't write vendor or system. Nor dumps system. Confused, bootloader says unlocked, unsure how to proceed

Update: Somehow booting again and got rid of encryption in the process
nice, looks like youre making good progress, was gonna ask if you had flashed an empty vbmeta
 
nice, looks like youre making good progress, was gonna ask if you had flashed an empty vbmeta
there is no vbmeta on this device. if you would like to continue helping me test stuff, please contact me on Telegram since it's live and much quicker to post test stuff and talk easier.
 
Last edited by a moderator:

Oswald Boelcke

Senior Moderator / Moderator & RC-RT Committees
Staff member
there is no vbmeta on this device. if you would like to continue helping me test stuff, please contact me on Telegram since it's live and much quicker to post test stuff and talk easier.
@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
 
  • Like
Reactions: Badger50
@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?
 
Last edited:

Figlet

Member
Aug 7, 2016
48
5
36
Little Rock
I have one that's almost functional, it boots if I 'reboot to bootloader', but I locked up the normal boot process by trying factory reset from settings instead of twrp, so now force boots to recovery.

Does anyone know which file to delete in order to stop the factory reset when invoked from settings menu? I've googled it and can't find anything, but I know there's a file that either needs to be modified or deleted and it will no longer try to boot to recovery/factory-reset

Thanks!
 

luridphantom

Senior Member
Apr 4, 2021
200
40
GT-i9250
AT&T Samsung Galaxy S III
I have one that's almost functional, it boots if I 'reboot to bootloader', but I locked up the normal boot process by trying factory reset from settings instead of twrp, so now force boots to recovery.

Does anyone know which file to delete in order to stop the factory reset when invoked from settings menu? I've googled it and can't find anything, but I know there's a file that either needs to be modified or deleted and it will no longer try to boot to recovery/factory-reset

Thanks!
$ adb shell :/ $ su :/ # mount -o rw,remount / :/ # cd system/ :/system # mv recovery-from-boot.p recovery-from-boot.p.bak :/system # mount -o ro,remount /
 

Figlet

Member
Aug 7, 2016
48
5
36
Little Rock
$ adb shell :/ $ su :/ # mount -o rw,remount / :/ # cd system/ :/system # mv recovery-from-boot.p recovery-from-boot.p.bak :/system # mount -o ro,remount /
Yes, I had already tried that, to no avail. Also, I flashed the lk image found in the a501dl.zip package, and now I might be bricked pretty hard, but I'll use mtk-tools and see if I can restore the factory lk.img, if anyone has it, or if lk2.img is the same kind of like the old bootloader backup partitions
 

luridphantom

Senior Member
Apr 4, 2021
200
40
GT-i9250
AT&T Samsung Galaxy S III
Yes, I had already tried that, to no avail. Also, I flashed the lk image found in the a501dl.zip package, and now I might be bricked pretty hard, but I'll use mtk-tools and see if I can restore the factory lk.img, if anyone has it, or if lk2.img is the same kind of like the old bootloader backup partitions
there is an lk2 you can backup and restore to your lk partition
 
  • Like
Reactions: Figlet
Like most TracFone branded mobile devices, this TCL A3 variant is not supported for bootloader unlocking. To date, no exploit has been discovered to circumvent the perma-locked bootloader. Therefore, root is not possible, since Magisk systemless root would require flashing the /boot partition with a Magisk patched boot image. With the bootloader locked, the /boot partition is fully.write protected.
 
Like most TracFone branded mobile devices, this TCL A3 variant is not supported for bootloader unlocking. To date, no exploit has been discovered to circumvent the perma-locked bootloader. Therefore, root is not possible, since Magisk systemless root would require flashing the /boot partition with a Magisk patched boot image. With the bootloader locked, the /boot partition is fully.write protected.
You have no clue what you are talking about good sir, I suggest some research
 
You have no clue what you are talking about good sir, I sugges)
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
 
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
 
  • Like
Reactions: Viva La Android
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
@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.
 
@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
 
  • Like
Reactions: Viva La Android
@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.
 
  • Like
Reactions: PizzaG

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