Database Info

Pixel bricked with locked bootloader

Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).

You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.

post-mortem said:
You could try the Deuces script. It was designed for the Pixel 2. If you're hesitant to run the script, you can look at it in a text editor, and run the commands yourself while following along.
Click to expand...
Click to collapse
That unfortunatly doesn't work. It's only for unlocked or at least unlockable deviced. I still tried it, but most fastboot commands require the bootloader to be unlocked. flashing unlock, flashing unlock_critical oem unlock, flash, format, boot, --set-active all don't work with a non-unlockable bootloader.
Although it shouldn't be needed, you could try fasboot flashing unlock_critical.
Click to expand...
Click to collapse
Also fails with 'oem unlock is not allowed'.
Another thing which may help is to use fastboot to simply boot: fastboot boot boot.img. If you are able to boot, you may be able to go back into the developer options to toggle allowing unlock.
Click to expand...
Click to collapse
Fails with 'Command is not supported. Please unlock device to enable this command.'

This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905

junglism93 said:
This may be worth a punt
https://forum.xda-developers.com/pixel/help/help-asap-pixel-bricked-t3518905
Click to expand...
Click to collapse
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.

Marvin0509 said:
No luck there. In my case I can't even boot to the system anymore (with fastboot continue), since anything else than bootloader just briefly flashes the boot animation, then my phone shuts off.
Click to expand...
Click to collapse
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Sent from my Pixel using XDA Labs

junglism93 said:
Damn, well it was worth a shot. Hopefully someone with a bit more knowledge might pipe up with a solution at some point.
Click to expand...
Click to collapse
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.

Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
Definitely seems a non recoverable scenario and happy days on getting it RMA'd for free :good:
Sent from my Pixel using XDA Labs

Marvin0509 said:
I found nothing that could help me, so I contacted Google, and they offered me a free RMA, which I gladly accepted.
Click to expand...
Click to collapse
It's over a year old right?? And they RMAed it for free?

aholeinthewor1d said:
It's over a year old right?? And they RMAed it for free?
Click to expand...
Click to collapse
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.

Marvin0509 said:
Over two years old, actually. I was really surprised as well, especially since it's my own fault that it doesn't work anymore. I don't know exactly why, but I certainly won't say no to this offer.
Click to expand...
Click to collapse
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?

post-mortem said:
Interesting. Did you tell them you were messing with the bootloader, or did you play stupid?
Click to expand...
Click to collapse
No, I told them the whole truth, that I rooted it, modified the system, and that it doesn't work at all anymore.

Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks

HeinrichSpy said:
Marvin,
What google support did you contact? Can you share the link or contact details perhaps? I have exactly the same problem and I have not been able unlock the bootloader and fear I have a hard bricked device, with Google being the only solution...
Thanks
Click to expand...
Click to collapse
I have a subscription for Google One, so I contacted support from one.google.com. They quickly talked to me, then added a Pixel support employee to the conversation. I think I could have also contacted Pixel support directly on this page: support.google.com/pixelphone/contactflow. However I'm not sure if this will work in your country, I'm from Germany and the page wants me to select my Pixel, then I could contact a support employee via chat or wait for a callback, but if I change the language to English, the page seems broken and is just blank.

Marvin0509 said:
Today I made a mistake and possibly broke my Pixel permanently.
The bootloader was unlocked, TWRP was installed and the system was rooted and modified.
I intended to reset the device completely to factory settings (with the factory image), but locked the bootloader without thinking BEFORE restoring the system. This caused the Pixel to go into a boot loop, neither system nor recovery were available, I could only get into the bootloader, so it was soft-bricked. That wouldn't be a problem, I should be able to unlock the bootloader and install the factory image. But this is not possible, because for some reason I can't unlock the bootloader anymore.
"fastboot oem unlock" or "fastboot flashing unlock" fails with "oem unlock is not allowed".
I don't know exactly why the bootloader is locked without system, but it definitely is. I can also not boot anything, not the system and not any recovery. If anything other than the bootloader is loaded, the Google logo flashes briefly, then the Pixel reboots. I can't use adb because there is no recovery or system available, and practically all fastboot commands are locked because the bootloader is locked.
I've been looking for solutions, but haven't found any. Is the Pixel definitely broken, or is there maybe some way to make it usable again? I don't care if I would lose data, but it would be a real bummer if the Pixel would be broken now.
Thanks in advance for any suggestions (even if it's just to throw the phone away and move on).
Click to expand...
Click to collapse
i tried flashing a stock ota image...it was successful, but on reboot, nothing has changed. still the same. u know of a solution? i cant find it anywhere. thanks

Oneplus6 Stuck on rolling dot

Hi all,
My stock ROM Oneplus 6 (3 weeks out of warranty :crying: ) became unresponsive today and crashed.
It failed to boot back in to the OS so I cleared cache - no better, then system settings - no better, then data - no better - but this time I got the Qualcomm crash dump mode.
I've used MSMDownloadtool to flash first - enchilada_22_O.09_180517, then after that did not boot i tried - enchilada_22_O.30_190403.
MSMDownloadtool 'worked' as far as I can tell, as all messages were positives (no errors) and the phone restarted
But unfortunately both have the same result, the phone is stuck on the android spinning dots - no Qualcomm crash dump anymore - small blessings.
I can get into both recovery and fastboot, but I'm at a loss as to what to try next.
I thought the MSMDownload tool was the nuclear option and would work - but no.
Would anyone have any suggestions ?
Thank you!
Dan

Try to flash a stock rom with fastboot, you can find a stock one in the forum and will find a batch file that will flash all the partitions for you, good luck

Chinaroad said:
Try to flash a stock rom with fastboot, you can find a stock one in the forum and will find a batch file that will flash all the partitions for you, good luck
Click to expand...
Click to collapse
Thank you Chinaroad,
I'm sorry for the stupid question, but I thought the MSMDownloader tool was a stock ROM installed through fastboot - this is all new to me - do I need to follow a different method ?
Thanks again
Dan

The msm is a tool that flashes the stock rom at another level than fastboot, and yes as you said it's the ultimate solution and it's strange that it doesnt work for you, so since you can access to fastboot, try to flash it that way without using msm

Chinaroad said:
The msm is a tool that flashes the stock rom at another level than fastboot, and yes as you said it's the ultimate solution and it's strange that it doesnt work for you, so since you can access to fastboot, try to flash it that way without using msm
Click to expand...
Click to collapse
I'm trying the flash-all.bat method, but the guide I'm using (and the program output) tells me the bootloader must be unlocked - of course it isn't.
I've tried Tool All in one to unlock the bootloader - but I get the error message Failed (remote: 'Flashing unlock is not allowed')
What step am I missing...
Sorry, and thanks again
Dan

it says flashing unlock is not allowed cuz i think it needs to be activated in dev menu of the phone, but since you can't power it up ..... . So lets comeback to MSM, are you sure all the files are there and you get no output error?

Chinaroad said:
it says flashing unlock is not allowed cuz i think it needs to be activated in dev menu of the phone, but since you can't power it up ..... . So lets comeback to MSM, are you sure all the files are there and you get no output error?
Click to expand...
Click to collapse
I've weakened and gone for an RMA - in some vain hope that they'll offer a warranty repair :fingers-crossed:
I've followed the guides for MSM to the letter, and it gave only positive feedbacks - but then just wouldn't complete the boot.
From reading these forums - anyone at the stage / with the symptoms I found myself with seems to have been resolved with an RMA
I guess if I'm an idiot and it was software, then the charge won't be huge, I'll suck it up - if I'm not and the issue was hardware then I'll make a descision when I know.
Thanks for your time, and I'll be sure to feedback !
Dan

Goodluck hope you fix it for free or at least not too much

Chinaroad said:
Goodluck hope you fix it for free or at least not too much
Click to expand...
Click to collapse
One plus honoured my (technically expired) warranty and replaced the main board.
Great news, if a little late, I did already buy a OnePlus 7 Pro...

Dan1Dan2 said:
One plus honoured my (technically expired) warranty and replaced the main board.
Great news, if a little late, I did already buy a OnePlus 7 Pro...
Click to expand...
Click to collapse
Nice from them and good for you xD

Dan1Dan2 said:
Hi all,
My stock ROM Oneplus 6 (3 weeks out of warranty :crying: ) became unresponsive today and crashed.
It failed to boot back in to the OS so I cleared cache - no better, then system settings - no better, then data - no better - but this time I got the Qualcomm crash dump mode.
I've used MSMDownloadtool to flash first - enchilada_22_O.09_180517, then after that did not boot i tried - enchilada_22_O.30_190403.
MSMDownloadtool 'worked' as far as I can tell, as all messages were positives (no errors) and the phone restarted
But unfortunately both have the same result, the phone is stuck on the android spinning dots - no Qualcomm crash dump anymore - small blessings.
I can get into both recovery and fastboot, but I'm at a loss as to what to try next.
I thought the MSMDownload tool was the nuclear option and would work - but no.
Would anyone have any suggestions ?
Thank you!
Dan
Click to expand...
Click to collapse
your problem is now fix or still faceing this problem????beoouse i have also same issue becouse i erase persist partiton..when my bootloader unlock after flashing official full firmware via msm download tools my phone stuck on bootloop..won't boot

btuhin17 said:
your problem is now fix or still faceing this problem????beoouse i have also same issue becouse i erase persist partiton..when my bootloader unlock after flashing official full firmware via msm download tools my phone stuck on bootloop..won't boot
Click to expand...
Click to collapse
The motherboard was replaced, this was the only fix for my problem.

Dan1Dan2 said:
The motherboard was replaced, this was the only fix for my problem.
Click to expand...
Click to collapse
only motherboard replace solved this problem??

NV Backup Warning - Dynamic partition invalid. Quite the riddle.

UPDATE: So hopefully this title and OP update take as I don't want to spam the forum with threads. Despite have dozens of Android phones since the original G1 I am stumped by this, but I imagine a guru could solve this puzzle. Here we go:
I messed up my phone partition table when I messed up the last step from the dual boot TWRP thread. I tried fixing my newly bricked phone using MSM tools but it's a converted GM1915 Tmobile OP7P running global firmware. The Tmobile stock MSM recovery pack MEGA link has gone dead, so I tried the Tmo to Int'l conversion files again. The phone booted, but I kept getting "NV Backup warning - dynamiic partition is invalid". I could make calls, but had no orientation sensor, no mobile data, baseband shows blank in fastboot mode, etc. I've tried flashing fastboot ROMs as well but no matter what, the dynamic partition invalid message pops up.
It seems ike this is an EFS issue, so late last night I tried a few more things. IIRC, I was able to flash that persist.img via "fastboot flash persist persist.img", and in any case most everything seems to work now, including the sensors. But, I'm still getting that dynamic partition invalid error and no baseband shows on my bootloader screen. I
'm guessing there's still some corruption in EFS? I'd understood from reading that even with persist.img one good thing was to erase the modem files and persist first, because then they will regenerate, according to this post.
So, I tried these commands with plans to then flash persist.img again....
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
It won't let me erase them though, as it says the critical partitions are locked. Do you think this path might fix whatever issue is triggering this message, and if so, does anyone know how to do it? I think I may have use dd, but I'm not sure which partitions I'll be looking to erase and how to do it that way, either.

Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424

¿GotJazz? said:
Maybe try this: https://forum.xda-developers.com/oneplus-7-pro/how-to/rom-stock-fastboot-roms-oneplus-7-pro-t3931424
Click to expand...
Click to collapse
Thanks, but that's what I've been trying. No joy so far. I need to check because actually it may have hung on params or some other issue that an L2 driver update could fix. Of course me figuring out how to fix that will be the next feat, LOL.

Updated thread title and OP with new info. Phone almost back to 100%, but still getting an error message.

So another update as I learn. Now that I've gotten TWRP and Magisk back on it, I realized there is another odd thing with the phone now. Just before the bootloader unlocked warning screen, for a fraction of a second there's a message that says SMT Download Failed. More reading seems to suggest that using an SMT recovery in conjunction with MSM tool can fix the SMT Download Failed message. Most of these say you need to have an EFS backup, which some suggest that you can wipe EFS (as indicated in OP) and it will regenerate.
I've taken a TWRP backup of EFS, but I'm not sure whether I should proceed with the wipe processes with so many saying you should have an EFS backup (lesson learned, yes you should - and don't delete/misplace it like I did). Anyway, I'm wondering if going through that process might resolve that, as it could be a flag that didn't get set right, or whether or not there's some issue with my EFS that means my backup from the current state is worthless.
Maybe my EFS isn't corrupt after all, maybe it was the persist.img that needed to fix the sensores and now I'm good except for some flag that's triggering the SMT Download Failed message and the subesquent dynamic partition invalid message?

Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work

yulian6766 said:
Maybe you could do that on twrp by terminal commands, some fastboot command dont work on Bootloader but in twrp work
Click to expand...
Click to collapse
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.

vettejock99 said:
That's actually an idea I was kicking around for my next move. I was hoping that before I do that, though, I could get a sense from one of the gurus as to whether I'll be able to recover my IMEI and such afterwards.
Click to expand...
Click to collapse
Your problem is recover your IMEI?

yulian6766 said:
Your problem is recover your IMEI?
Click to expand...
Click to collapse
The phone shows IMEI right now, and calls and mobile data work, so except for the weird " SMT download failed!!! please check your download flow is right" message at boot start and the NV Backup UI warning Dynamic partiton invalid messages the phone otherwise seems just fine. I'm pretty comfortable with system, boot, and data partition stuff from all my time at this, but I'm just being extra cautious that by erasing my modems via some sort of commands or SMT flash that I can at least get it back to where it is now even if I can't get back to an error-free state.

Have you tried flashing QCN file?

yulian6766 said:
Have you tried flashing QCN file?
Click to expand...
Click to collapse
I had heard about and used QPST before, but QCN is new to me. I did a quick search and it sounds like on some phones like ASUS ROG, you REALLY need to have one to recover from erasing your modems. Oneplus phones recreate those if they are erased, don't they?

Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.

Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.

Velrix said:
Hey man I know I posted the other one up with the issue too but thanks for this after seeing you flashing the persist fixed your sensors I tried and walla they are good now! I still have the same SMT failed and NV Backup warning but at least the phone can auto rotate.
Click to expand...
Click to collapse
Good stuff. I'll definitely post a resolution here if I get it all. Just glad to have the phone working again for sure!

yulian6766 said:
Create a QCN backup from QPST of your phone and flash it again, maybe that will fix your problem.
Click to expand...
Click to collapse
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.

I did go ahead and try a SMT flash. Unfortunately, while I've gotten it to start, it ultimately gets to "Param preload" then I see the Status of Connection change to N/A and then it just hangs....grrrr...

vettejock99 said:
I went and installed QPST again and I can get it to see the phone in EDL mode, but I don't believe I have the drivers to get it into diagostnic mode. If I try it shows GM1915 with unknown USB drivers, but I've downloaded some and they don't seem to be able to get the device recognized properly. Until I figure that out, I can't pull QCN, I don't think.
Click to expand...
Click to collapse
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me

yulian6766 said:
You have to install the right drivers
https://forum.xda-developers.com/rog-phone-2/how-to/guide-restoring-imei-efs-erasing-t4071159
This drivers should work for me
Click to expand...
Click to collapse
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?

vettejock99 said:
That's the one I was using. Just downloaded and compared the hashes. Now that I think about it, I chose WWAN-DHCP mode. Should I have chosen ETHERNET-DHCP?
Click to expand...
Click to collapse
I choose the same option

yulian6766 said:
I choose the same option
Click to expand...
Click to collapse
So if we're both choosing WWAN-DHCP for the driver mode, I'm not sure why it wouldn't work. Right now everything is working and I told the NV Backup UI notification to Never Show so it will probably be a few days before I get around to trying to get the whole thing to flash properly. My OCD is really the only thing that would drive me to do it

Question Is unbricking possible?

Good morning all, I tried relocking my bootloader using the command "fastboot oem asus-csc lk" and at first, it seemed to be a success. However I restarted my device and was met with this error message. "Your device is corrupt. It can't be trusted and will not boot." I've tried searching high and low and it seems that I'm royally screwed, just wanted to confirm that I was though. Thanks for reading my post and any input is appreciated.

If your boot.img is not stock before locking you will get this error. Try flashing stock boot.img. I had a similar experience with realme phone but not encountered this issue with ROG 5
Edit: Sorry since you locked the bootloader i think you cant flash it unless you unlock it again. Give a try with EDL firmware

This is becoming a pretty common issue. I think it's time we make a WARNING thread.
WARNING: Read BEFORE Locking Bootloader
DO NOT LOCK THE BOOTLOADER WHILE ROOTED! When locking the bootloader while rooted, the boot image will fail verification and the system will fail to boot. You cannot flash a stock boot image with a locked bootloader. Locking the bootloader will...
forum.xda-developers.com

jhosharath said:
If your boot.img is not stock before locking you will get this error. Try flashing stock boot.img. I had a similar experience with realme phone but not encountered this issue with ROG 5
Edit: Sorry since you locked the bootloader i think you cant flash it unless you unlock it again. Give a try with EDL firmware
Click to expand...
Click to collapse
How would I go about doing that? If you don't mind telling me of course. I've tried doing some research on it but it seems there isn't much on this phone at all

Jdotswift said:
How would I go about doing that? If you don't mind telling me of course. I've tried doing some research on it but it seems there isn't much on this phone at all
Click to expand...
Click to collapse
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com

twistedumbrella said:
ROG Phone 5(s) Help Index
"Quick Filters" let you see all posts of a certain type. This can make finding posts easier, but what if a guide began as a "Question"? This thread aims to bridge that gap. You will find nearly all of the common things new owners are trying to...
forum.xda-developers.com
Click to expand...
Click to collapse
Thanks for your help so far but I'm having issues putting the phone into edl mode. I'm trying to follow what was suggested in the tutorial but it isn't working. I also tried the fastboot command that was done in the video and to no avail. Google isn't giving much either. Am I missing something?
Edit: Made it into Edl mode but when trying to flash the ww image folder, I'm met with an error message saying "Object reference not set to an instance of an object". It seems like there is no fix for this at the moment

Jdotswift said:
Thanks for your help so far but I'm having issues putting the phone into edl mode. I'm trying to follow what was suggested in the tutorial but it isn't working. I also tried the fastboot command that was done in the video and to no avail. Google isn't giving much either. Am I missing something?
Edit: Made it into Edl mode but when trying to flash the ww image folder, I'm met with an error message saying "Object reference not set to an instance of an object". It seems like there is no fix for this at the moment
Click to expand...
Click to collapse
That's likely because the bootloader is locked. It was possible that EDL mode could still allow a full restore, but also quite possible it wasn't going to work because of that.

twistedumbrella said:
That's likely because the bootloader is locked. It was possible that EDL mode could still allow a full restore, but also quite possible it wasn't going to work because of that.
Click to expand...
Click to collapse
Well thanks for your help. I admit defeat but learned a very valuable lesson

Jdotswift said:
Well thanks for your help. I admit defeat but learned a very valuable lesson
Click to expand...
Click to collapse
You may still want to contact Asus and tell them you don't know what happened. They may be able to restore it. I wouldn't tell them you unlocked the bootloader, since it's locked if they ask.

As long as bootloader mode works, You can flash a RAW file to boot the phone back.
Ensure the phone has enough battery power left for a 20 min+ flash,
USB Cable to be connected on the side port, (not bottom charging port - fastboot doesn't work there)
and to use the exact raw firmware file which matches the device model and variant.
Latest WW Raw file is here

JazonX said:
As long as bootloader mode works, You can flash a RAW file to boot the phone back.
Ensure the phone has enough battery power left for a 20 min+ flash,
USB Cable to be connected on the side port, (not bottom charging port - fastboot doesn't work there)
and to use the exact raw firmware file which matches the device model and variant.
Latest WW Raw file is here
Click to expand...
Click to collapse
Hopefully this time is different, but every report so far has been that it fails. I believe we still need the firehose to use any programs that override the bootloader security on fastboot.

twistedumbrella said:
Hopefully this time is different, but every report so far has been that it fails. I believe we still need the firehose to use any programs that override the bootloader security on fastboot.
Click to expand...
Click to collapse
Can confirm it one hundred percent works. Mine was the American variant purchased directly from Asus' website. I don't think that had anything to do with it but my phone is up and running with a locked bootloader now. I really appreciate the help fellas

Jdotswift said:
Can confirm it one hundred percent works. Mine was the American variant purchased directly from Asus' website. I don't think that had anything to do with it but my phone is up and running with a locked bootloader now. I really appreciate the help fellas
Click to expand...
Click to collapse
Glad to hear it. Apparently, the issue was people not following instructions...

TCL A509DL NO FASTBOOT-ABILITY??

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.