Related
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Meakii said:
Hi all
A bit new to posting in here but am really hoping to receive some help from you all. Last night I installed all the standard USB drivers i.e. Android SDK pack and followed them all as mentioned. Then using the root tool from ChainFire I got to the little android guy after going through the process of unlocking the bootloader and gaining root, but the phone never actually rebooted.
Now when I try to flash the original fastboot files using the WUG kit I get "FAILED: remote: flash write failure" The same is the case with writing the boot img and recovery img. See attached.
I can put the phone into Fastboot mode only and it says lock state is "unlocked" but it would seem that I can no longer write anything to the internal disk as nothing will work or boot. I also get a status on my PC saying that the driver QHSUSB_Bulk could not be found.
Has anybody had a similar problem to this? Is there any way to somehow get this working again? And if I RMA with Google will they say my warranty is voided now that it says the lock state in Fastboot is unlocked?
Many thanks in advance guys any help is appreciated.
Click to expand...
Click to collapse
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
abaaaabbbb63 said:
Try flashing the factory images manually.
http://forum.xda-developers.com/showthread.php?t=2513701
Method 2.
Does fastboot work properly? What output does 'Fastboot devices" have?
Click to expand...
Click to collapse
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Meakii said:
Thanks have tried flashing them manually but still the same error saying FAILED: remote: flash write failure
It as if nothing can be written to the phone at all.
Yea fastboot seems to work fine but sorry what do you mean by what ouput does fastboot devices have?
Thanks a lot
Click to expand...
Click to collapse
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
abaaaabbbb63 said:
write "Fastboot devices" in CMD while phone is in fastboot.
What happens when you boot in recovery? Try that, and do a factory data reset.
Click to expand...
Click to collapse
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Meakii said:
Ok see attached. Also it doesn't allow me to boot into recovery at all. I used the WUG kit to temporarily boot into TWRP and tried a factory reset there but it says there's no ROM installed. It's like everything has been wiped and it can't write anything to the internals to read from. Thanks for you help so far. Any other suggestions?
Click to expand...
Click to collapse
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
abaaaabbbb63 said:
Just... stop using toolkits for a second here! These automated processes got you here in the first place.
Try this command:
fastboot erase userdata
Does it succeed?
Click to expand...
Click to collapse
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Meakii said:
Ok ummm see attached. I'm so gutted any further thoughts or advice?
Click to expand...
Click to collapse
It seems like a brick. Something got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
abaaaabbbb63 said:
It seems like a brick. Your internal memory got corrupted. I searched far an wide on XDA and other forums, but no one with this problem has found the solution.
It seems that your last chance is RMA.
Click to expand...
Click to collapse
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
Who knows? Try it!
I don´t think the reason was CF-auto root. There must be something wrong with the device´s flash from the beginning. My thoughts are that you´r flash has a corrupted area which surprisingly wasn´t used for the stock factory flash and CF-autoroot triggered it while flashing a specific partition. Maybe i´m completely wrong.
I hope you´ll get it exchanged :good:.
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Meakii said:
Ok thanks for your help. How this happens simply rooting a device following step by step instructions having rooted many devices before I'll never know. There was no interrruptions or reasons for this to have happened. Do you think they will take one look at it and say warranty is voided?
Click to expand...
Click to collapse
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
abaaaabbbb63 said:
I don't really know what happened. I guess there are always risks when using tools like this. That's why I always recommend rooting using the manual method.
I have no idea how google will react. In theory, a simple unlocked bootloader won't affect warranty. In reality, anything can happen. Good luck, and sorry!
Click to expand...
Click to collapse
Absolutely gutted but thanks so much for your help. I'll report back with Googles response.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
It will respond, but the memory won't flash. Major no-fix problem.
pert_S said:
It's a mystery indeed, it might not be CF but best way is to stay away from toolkits and do it manually.
http://forum.xda-developers.com/showthread.php?t=2507905
Does it respond to anything?
Will it turn on but just get stuck?
If it won't respond to anything at all then I doubt Google would say the warranty is void. They probably wouldn't know since it's dead.
Click to expand...
Click to collapse
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Would opening the command prompt window with administrative rights make a difference? Worth a shot.
Meakii said:
Hi nah it only boots into Fastboot mode where it says down the bottom in red "LOCK STATE - unlocked" . Have tried every trick posted on here but it seems that during the rooting process somehow corrupted internal storage meaning it can't write anything to the phone (therefore not being able to reset to factory etc etc).
What a disaster.
Click to expand...
Click to collapse
Oh I see.
Well like abaaaabbbb63 said, in theory it shouldn't affect warranty.
They would have to show that unlocking the bootloader caused the fault I presume.
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
El Daddy said:
Make sure you tell Google that this happened when using a toolkit and a script when asking for a new phone free of charge.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
How would that help? I think pleading ignorance to how it happened would probably be best wouldn't it?
Thanks for all the replies.
It's sarcasm friend. ;3. Daddy isn't a fan of toolkits nor of people claiming new handsets after a problem occurs as a result of one.
o I rooted my nexus 5. No issues. Installed TWRP. Same. Downloaded CM and GA to the phone. Then, very foolishly, wiped everything to prep for the install - SD card included. Now, all I can load is TWRP. No ROM to be found - obviously. Computer won't recognize the phone to load a ROM that way. Would be VERY appreciative of any help. TY!S
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
meangreenie said:
you can use the 'adb push' command in recovery to transfer a rom zip to the phone via your computer
Click to expand...
Click to collapse
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
bradley.robt said:
I have TWRP v2.6.3.0 installed. The bootloader option takes me to TWRP. The Recovery option just hangs at the Google splash screen. Can you be more specific pls? Thanks for the help.
Click to expand...
Click to collapse
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
aldyu said:
Install adb drivers on your computer then go to TWRP recovery with your phone connected to your computer. Type 'adb devices', to check if your phone is detected, it should display your phone's serial number. Then you can 'adb push file' to transfer the cm/gapps zips from your computer to phone's internal sdcard.
Click to expand...
Click to collapse
Sorry, assume 'adb devices' is in the command prompt, but noob town - which folder in the ADT parent folder?
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
That's what I figured, but...challenge accepted. Thanks for the links.
RoyJ said:
So you have no idea how to use ADB? You're in for a real long night. -__-
Read this
http://forum.xda-developers.com/showthread.php?t=2513701
And this
http://forum.xda-developers.com/showthread.php?t=2507905
Click to expand...
Click to collapse
RoyJ,
Appreciate the help. TY, all's good.
Happened to me a few times tinkering with the gnex, n4...boneheadedly wiped the internal storage. Easiest fix in my opinion is to just flash factory stock and start back from stretch. If not like they said you're in for a long night trying to get your phone to sync up to push the files via adb if you aren't familiar with the stuff.
Do wish you the best. Been there.
I have not been in that situation but couldn't you use a OTG cable (a Y type one which accepts power as well) and a SD card or stick and then mount it within TWRP to access a ROM to flash...?
EDIT: Also consider the Nexus Toolkit - very useful.
I really think that the faster way is to flash stock firmware back (if you have no experience with ADB commands).
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
TheLastSidekick said:
Don't be so scared of adb. Its hard if you don't know Linux but adb is really really copy and paste for first time use. (That's how I learned anyways) You learn it once and it stays current and useful.
Sent from my Nexus 7 using XDA Free mobile app
Click to expand...
Click to collapse
It's really not that hard.. You plug it in, open a folder, open the prompt and type a few words.. My advice is to try and learn.
sent from my Nexus 5
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Seadra said:
Just install official images of nexus 5. No need to learn complex stuff where u have no idea even abt adb.
Click to expand...
Click to collapse
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Glad you got it sorted.
Letharqy said:
You need fastboot/adb to do it anyways. Unless you use toolkits, ew.
Click to expand...
Click to collapse
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
TheLastSidekick said:
A bit discouraging friend. I say learn on all about adb it's essential for Android. Knowledge is power.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
No, you didn;t get my point. I told him to straight away restore by images just because his phone wasn't working at all. He can learn all that stuff later, but atleast he should be with no phone at all.
Seadra said:
Yes, just the adb drivers needs to be installed. And I have never used toolkit ever.
Click to expand...
Click to collapse
How would you flash the .imgs without using adb/fastboot?
Letharqy said:
How would you flash the .imgs without using adb/fastboot?
Click to expand...
Click to collapse
by adb drivers, I mean adb/fastboot or SDK and drivers of the phone that's always included.
Tried converting to GPE edition by following htc-one.wonderhowto.com/how-to/convert-your-htc-one-m8-into-google-play-edition-0154471/ and using this file: RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5_rooted.zip. (I don't have 10 posts yet, so I can't post URLs.)
During the process, I edited android-info.txt to include my phone's mid and cid. Everything seemed to go fine, but now it only boots to the bootloader screen where I can choose fastboot or recovery or whatever, but recovery doesn't work. Also, my laptop is no longer detecting my phone on USB so I can't use ADB commands.
Please help... Don't know what to do from here.
darkhelmet46 said:
Tried converting to GPE edition by following htc-one.wonderhowto.com/how-to/convert-your-htc-one-m8-into-google-play-edition-0154471/ and using this file: RUU-HTC_One_M8_GPE_5.0.1-3.11.1700.5_rooted.zip. (I don't have 10 posts yet, so I can't post URLs.)
During the process, I edited android-info.txt to include my phone's mid and cid. Everything seemed to go fine, but now it only boots to the bootloader screen where I can choose fastboot or recovery or whatever, but recovery doesn't work. Also, my laptop is no longer detecting my phone on USB so I can't use ADB commands.
Please help... Don't know what to do from here.
Click to expand...
Click to collapse
If you are still in this situation install team viewer and pm me the Id and passcode so I can take a look.
dottat said:
If you are still in this situation install team viewer and pm me the Id and passcode so I can take a look.
Click to expand...
Click to collapse
Yep, still am. However, this morning I rebooted my laptop and now it is able to detect the phone on USB so hopefully it is now fixable. I'll PM you after I get TeamViewer installed, thanks very much!
darkhelmet46 said:
Yep, still am. However, this morning I rebooted my laptop and now it is able to detect the phone on USB so hopefully it is now fixable. I'll PM you after I get TeamViewer installed, thanks very much!
Click to expand...
Click to collapse
Actually, I take that back... It makes the "ding" noise like it's connected, but ADB complains "device not found" when I try to run commands...
Forgot to update this. dottat helped me out earlier this week and he is indeed the man! I'm good to go!
As the title says, i cant manage to unlock the bootloader. My device is GM1910, i am running 9.5.10 GM21AA. i went to OB2 but then rolled back and decided i wanted to unlock and root, but for some reason i cannot. followed all the proper guides, tried the adb method, but when i type fastboot oem unlock, it just says waiting for device. I also tried the all-in-one tool and same problem, the moment i check for bootloader status, the application hangs. has anyone faced this issue before? could use some help. Thanks
Using the OP cable and tried on both USB 3 and 2
linx1287 said:
As the title says, i cant manage to unlock the bootloader. My device is GM1910, i am running 9.5.10 GM21AA. i went to OB2 but then rolled back and decided i wanted to unlock and root, but for some reason i cannot. followed all the proper guides, tried the adb method, but when i type fastboot oem unlock, it just says waiting for device. I also tried the all-in-one tool and same problem, the moment i check for bootloader status, the application hangs. has anyone faced this issue before? could use some help. Thanks
Using the OP cable and tried on both USB 3 and 2
Click to expand...
Click to collapse
If your on sprint you cant unless you pay off the phone or have it active for 50days. Not sure about t-mobile. heres a helpful link tho.
https://forum.xda-developers.com/oneplus-7-pro/how-to/discussion-sprint-oneplus-7-pro-5g-t3963319
lonewolf2k2 said:
If your on sprint you cant unless you pay off the phone or have it active for 50days. Not sure about t-mobile. heres a helpful link tho.
https://forum.xda-developers.com/oneplus-7-pro/how-to/discussion-sprint-oneplus-7-pro-5g-t3963319
Click to expand...
Click to collapse
Sorry but mine isnt any carrier phone GM1910 is the chinese international running GM21AA
Sounds more like a USB connectivity issue, than a problem with the device. Try the command: fastboot devices
And if it just hangs, then you don't have USB fastboot connectivity.
To be clear, the phone is booted to bootloader-fastboot mode (which is required for fastboot commands)?
You need the latest windows 10 drivers, adb & fastboot. And off course Open Beta it's still young... meanning sh.. could happen.
redpoint73 said:
Sounds more like a USB connectivity issue, than a problem with the device. Try the command: fastboot devices
And if it just hangs, then you don't have USB fastboot connectivity.
To be clear, the phone is booted to bootloader-fastboot mode (which is required for fastboot commands)?
Click to expand...
Click to collapse
null0seven said:
You need the latest windows 10 drivers, adb & fastboot. And off course Open Beta it's still young... meanning sh.. could happen.
Click to expand...
Click to collapse
Yes adb devices does register and adb reboot bootloader command does take me to the bootloader, but when i tried the fastboot devices it didnt register, so i think you are on to something. I will check again once i get home today. Thanks
I was on open beta, i reverted to 9.5.10 Pie in order to unlock bootloader and root.
If its not too much trouble, could you link me to the drivers (i would ask adb too but seeing as it works when i do adb devices command, i think thats working fine)? Thanks
Platform tool 2.9.0.4 (adb-fastboot), latest
https://android.gadgethacks.com/how...stall-adb-fastboot-mac-linux-windows-0164225/
null0seven said:
Platform tool 2.9.0.4 (adb-fastboot), latest
https://android.gadgethacks.com/how...stall-adb-fastboot-mac-linux-windows-0164225/
Click to expand...
Click to collapse
Thanks. This was the version i was working with yesterday. Could you link me to the usb drivers i might need? Since response stops at fastboot i am assuming the drivers are to blame
One thing you can try, on Windows go to Device Manager, find the phone, and pick the option to update the drivers. Select the drivers manually (don't let Windows find the drivers automatically). Then the one called Generic Android Device (or something like that).
I sometimes have to do this, to get Windows to work with adb/fastboot.
This is all on my old Windows 7 machine. So if you have Win 10, it might be a bit different.
redpoint73 said:
One thing you can try, on Windows go to Device Manager, find the phone, and pick the option to update the drivers. Select the drivers manually (don't let Windows find the drivers automatically). Then the one called Generic Android Device (or something like that).
I sometimes have to do this, to get Windows to work with adb/fastboot.
This is all on my old Windows 7 machine. So if you have Win 10, it might be a bit different.
Click to expand...
Click to collapse
Thank you. You were right about the driver issue....going through the device manager yielded the driver situation. Had to enable debugging to finally let the driver install. I completely forgot about this. I had to do this same thing when i had to unlock bootloader and twrp for my HTC 10.
Now that i am done with this, a few final things i would like to clear out....doing the local update on root to restore stock system is still valid right? and if i want to go full stock from say custom roms like los and so on, a flash through MSM tool? Will doing that also relock the bootloader? Sorry for all the noob questions and thanks in advance.
Local upgrade works with/without root or twrp.
MSM tool revert youre phone like it's out of the factory. Bootloader locked, no root, no twrp.
If you come back to Oos from custom roms you need to Format Data (this will wipe ALL in youre phone. everything).
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into fastboot mode.
All the usual processes have been eliminated...enabled Developer options, enabled OEM Unlock for Bootloader, enabled Usb debugging, etc...all ready, set, don't go.
I powered off the phone, restarted while holding the power+vol dwn, pwr+vol up, pwr+vol up and down, pwr+assistant key, pwr+vol up+assistant key and every combo thereof including every combon with the battery removed and USB connected while keys pressed. I gotta get to this fastboot or I'll go nuts...PLEASE!! Somebody help!!
Check whether Fastboot is supported or not via ADB
Code:
adb devices
adb reboot fastboot
fastboot devices
If a connection with bootloader got successfully established don't forget to end it
Code:
fastboot reboot
TCL is never known to have offered BL unlock for any of its device. On top of that, US carriers tend to enforce non-unlockable BL, Straight Talk / Tracfone (implied by the DL suffix) the worst among them.
jwoegerbauer said:
Check whether Fastboot is supported or not via ADB
Code:
adb devices
adb reboot fastboot
fastboot devices
If a connection with bootloader got successfully established don't forget to end it
Code:
fastboot reboot
Click to expand...
Click to collapse
Hi I have tried all of the above commands and about a dozen more. I'm tempted to believe what
I was recently told, that US Phone maker enforce the no Unlock bootloader policy. There would still need to be some window or method available for flashing in the event of a software failure, right? In the Developers menu it says the bootloader is already unlocked and the toggle is grayed out. When I reboot from ADB using adb reboot fastboot my phone reboots back to startup with no fastboot connection??
I also happened on one of these TCL A3's (A509DL), and I confirm that there is no fastboot mode, and only 3 options in recovery, no adb or sdcard or log access, strictly factory wipe and cache wipe.
Hopefully mtkclient will crack this baby open a little bit, I left my laptop in a friend's truck, but when I get it back here in a few days ill hack the crap out of it!
NashvilleKarl said:
I also happened on one of these TCL A3's (A509DL), and I confirm that there is no fastboot mode, and only 3 options in recovery, no adb or sdcard or log access, strictly factory wipe and cache wipe.
Hopefully mtkclient will crack this baby open a little bit, I left my laptop in a friend's truck, but when I get it back here in a few days ill hack the crap out of it!
Click to expand...
Click to collapse
Hey bro. Thanks for responding. Let me know how it goes. I can't even find Stock Firmware for this little pain. Mine is branded TCL A509DL a friend has the exact device thru Cricket branded Alcatel with a different model number but same deal zero fastboot or bootloader for fastboot. Now I HAVE to crack this pain.
Try with python mtkclient , not responsible, you got to know what you're doing, very easy to brick
JansenLove said:
Hey there guys and girls. I just bought a cheap TCL A509DL to experiment with and immediately hit a roadblock of megalithic proportions...no fastboot mode available on this cracker-jack prize equivalent phone. Seriously...no way to boot into fastboot mode.
All the usual processes have been eliminated...enabled Developer options, enabled OEM Unlock for Bootloader, enabled Usb debugging, etc...all ready, set, don't go.
I powered off the phone, restarted while holding the power+vol dwn, pwr+vol up, pwr+vol up and down, pwr+assistant key, pwr+vol up+assistant key and every combo thereof including every combon with the battery removed and USB connected while keys pressed. I gotta get to this fastboot or I'll go nuts...PLEASE!! Somebody help!!
Click to expand...
Click to collapse
Hey just tried and succeeded, using python Git and mtkclient from https://forum.xda-developers.com/t/blu-b130dl-unlock-recovery-root-release.4350825/ basic same principle just swap around a few files and it worked, a509dl tcl a3 is rooted, not responsible for any damage to device, I hope y'all know what your doing
bbcdt22 said:
Hey just tried and succeeded, using python Git and mtkclient from https://forum.xda-developers.com/t/blu-b130dl-unlock-recovery-root-release.4350825/ basic same principle just swap around a few files and it worked, a509dl tcl a3 is rooted, not responsible for any damage to device, I hope y'all know what your doing
Click to expand...
Click to collapse
I just got a tcl a3 (a509dl), dumping the firmware right now with mtkclient. I had driver problems with Windows (ghostspectre 11).. used the 're_livedvdv3' bootable iso. So far so good
Woo thank you for the info ! Unlocked and magisk rooted. Do we have twrp for this device on xda?
JansenLove said:
Hey bro. Thanks for responding. Let me know how it goes. I can't even find Stock Firmware for this little pain. Mine is branded TCL A509DL a friend has the exact device thru Cricket branded Alcatel with a different model number but same deal zero fastboot or bootloader for fastboot. Now I HAVE to crack this pain.
Click to expand...
Click to collapse
I lost my dumps, long story.. I need the stock firmware for this phone also, I bricked mine messing around lol even just The boot.img and vbmeta might be all I need can anyone with this phone grab them w mtkclient and upload ??
iamx51 said:
I lost my dumps, long story.. I need the stock firmware for this phone also, I bricked mine messing around lol even just The boot.img and vbmeta might be all I need can anyone with this phone grab them w mtkclient and upload ??
Click to expand...
Click to collapse
I recently bootloader unlocked then bricked the tcl a509dl hahaha was wondering if anybody could make a dump for me? I would be so very appreciative!
r1pp3d2 said:
I recently bootloader unlocked then bricked the tcl a509dl hahaha was wondering if anybody could make a dump for me? I would be so very appreciative!
Click to expand...
Click to collapse
I'll even teamview with somebody and use unlocktool to make the backup.
r1pp3d2 said:
I'll even teamview with somebody and use unlocktool to make the backup.
Click to expand...
Click to collapse
Following . Still need the stock firmware or dumps
Bahh... lame, I'm still in need of firmware/dump. Bout to go buy another one just to get it. lol .. they did have this phone at dollar general, I think its like 39$ .and the chick that's usually working gave me a discount, so the last one for $20. I think I have myself sufficiently talked into it now. If i do buy another, I will upload it for you guys.
iamx51 said:
Bahh... lame, I'm still in need of firmware/dump. Bout to go buy another one just to get it. lol .. they did have this phone at dollar general, I think its like 39$ .and the chick that's usually working gave me a discount, so the last one for $20. I think I have myself sufficiently talked into it now. If i do buy another, I will upload it for you guys.
Click to expand...
Click to collapse
Man, if you get another one I would love a backup from it.
r1pp3d2 said:
Man, if you get another one I would love a backup from it.
Click to expand...
Click to collapse
I have succeeded in getting the one I have already to allow me to do another dump, but it only boots to the bootloader says the dm-verity corruption crap, then reboots itself.c
If I remember correctly, this began after flashing a Magisk patched boot.img .. it is possible I did something else, but pretty sure that's what happened. messing with it now, will start the dumps before I pass out
iamx51 said:
I have succeeded in getting the one I have already to allow me to do another dump, but it only boots to the bootloader says the dm-verity corruption crap, then reboots itself.c
If I remember correctly, this began after flashing a Magisk patched boot.img .. it is possible I did something else, but pretty sure that's what happened. messing with it now, will start the dumps before I pass out
Click to expand...
Click to collapse
I'm pretty sure that's what screwed mine up too. But mine won't even come on now but I'm still able to connect to the chip to flash.
iamx51 said:
I have succeeded in getting the one I have already to allow me to do another dump, but it only boots to the bootloader says the dm-verity corruption crap, then reboots itself.c
If I remember correctly, this began after flashing a Magisk patched boot.img .. it is possible I did something else, but pretty sure that's what happened. messing with it now, will start the dumps before I pass out
Click to expand...
Click to collapse
any chance i could try that dump that you have?
iamx51 said:
Woo thank you for the info ! Unlocked and magisk rooted. Do we have twrp for this device on xda?
Click to expand...
Click to collapse
For clarification, are you stating that you have unlocked the bootloader and rooted the TCL A3 (A509DL) branded by TracFone Wireless. If so, as far as I know, there is a $1,700 cash bounty up for the first person to OEM unlock and/or root the A509DL.