yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 Questions & Answers] xdahoc:
I made an account just to add onto this saga....

I had my Pixel 3XL brick yesterday night, and upon reading everyone else's experiences, my diagnosis is this EDL mode problem. The best part, is that I pulled out my Pixel XL (first gen) from the drawer to use in the meantime, and IT BRICKED TOO! I put it on the charger and it showed a charging icon for a couple of seconds, and then went black and unresponsive, just like the Pixel 3XL. :(

I've tried pretty much everything I could think of;

I tried holding every combination of button for 2 minutes, nothing.

I tried using muscle memory to turn on USB File Transfer Mode (I thought the screen was broken), nothing.

I put them both in the freezer for an hour, nothing.

My Pixel 3XL's back cover was smashed to bits already so I pulled it all off and disconnected the battery, screen cable, every possible cable I could find and re-fastened them.. nothing!

So now I'm sitting here with two dead phones. Hopefully there's some news soon. I can't believe both of these phones died within a day to the same issue. At first I thought it was the charging cord and that it had somehow shorted both of the phones or something!
[Google Pixel 3 Questions & Answers] googletermsofservice:
Has this affected anyone running Pixel Dust or any other custom rom?
[Google Pixel 3 Questions & Answers] pixelburner:
Adding to the list here. My Pixel 3 was bricked on Aug 15th.

My phone was an unlocked and stock model, running Android 11. It was fully charged and NOT plugged in when it went into EDL mode (emphasizing that it wasn't plugged in, as there seems to be some correlation with that on other threads and the issue tracker).

I brought it to UBreakIFix, and they told me it was the motherboard and would cost $400 to fix. I declined and bought a brand new Pixel 3 on Ebay to hold me over until the Pixel 6 was released.

When I stumbled on this issue via the AndroidPolice article, I immediately turned off auto updates. Not sure if that's what caused the problem but it's still running (fingers crossed as I'll be traveling next week).

There is a law firm investigating this problem to determine if a class action is warranted/possible:

https://chimicles.com/google-pixel-3-class-action-investigation/
[Google Pixel 3 Questions & Answers] AsItLies:
Interesting, and a bit surprising it's taken this long for a suit to come up. The law firm lists 'multiple' problems, which, imho, isn't needed and only confuses the issue.

There's really only 1 issue, this one. And it's severe enough and it's case is strong enough, all by itself.

I have not yet had this issue (knock wood), but if so, I'd def join the suit. Most of the time these suits just enrich the lawyers, but sometimes the resolution will be google offering a replacement device or something like that.

It's good to see it in the 'light of day'. It most assuredly is about the most egregious thing possible to go wrong with a phone. I mean the only thing worse would be if it blew up?

cheers
[Google Pixel 3 Questions & Answers] ZetaPirate:
I looked over that class action investigation, and it lists problems that are not this one. So would signing up even help?

On another note, if you have not already done so, make sure to click the star at the top of the issue tracker to note that the issue effects you as all. I just got an update that the list has 453 comments, but only 336 phones effected... (Granted, this is much higher than it was.)

Something I had noticed that I thought was a bit fishy... The main issue tracker that has been used is for the beta version of Android 12 I believe. So someone started another tracker for the full version android os, and it was marked as a duplicate, but the reference tracker has been locked out so you can't view it.
[Google Pixel 3 Questions & Answers] ZetaPirate:
So this is interesting to note... Not sure, but maybe Google is "officially" looking into the trouble now? (Comment #479 on the issue tracker)

https://issuetracker.google.com/issues/192008282

View attachment 5409843
[Google Pixel 3 Questions & Answers] ember32:
update! after leaving my p3 off the charger in EDL mode for a week, now instead of QUSB_BULK_CID, it's showing up as Qualcomm HS-USB QDLoader 9008, which may or may not be the same thing... considering it's still stuck.
[Google Pixel 3 Questions & Answers] AlexKarimov:
Sorry if it's giving false hope but I googled Qualcomm HS-USB QDLoader 9008 and this is what came up.

Qualcomm HS-USB QDLoader 9008 Drivers: Download and Installation Guide

Download Qualcomm HS-USB QDLoader 9008 drivers for communicating with your Android device in Emergency Download (EDL) mode. Learn how to install these drivers on any Windows 11/10/8.1/8/7 computer.

www.thecustomdroid.com
[Google Pixel 3 Questions & Answers] ember32:
according to that guide, HS-USB QDLoader 9008 is the same thing, but with the appropriate qualcomm drivers for the device installed, apparently. so, not helpful, but I do appreciate the effort. we still don't have the firehose file etc to do this from qpst/qfil.
[Google Pixel 3 Questions & Answers] aquariuz23:
Edit: Yeah nevermind, this doesn't work for the Pixel :(

Hello all,

has anyone given this guide a try? https://www.droidwin.com/unbrick-oneplus-7t/

I'm currently at work so I don't have my dead Pixel 3 XL with me, but I might try this later, assuming nobody has and had no success with it.
[Google Pixel 3 Questions & Answers] JSilver2021:
Mine just hit the same issue last night. Was able to install Qualcomm drivers but cannot find anything to resolve past getting it recognized by USB. Just freaking great! This is my second Pixel that has died on me. I am not sure I will buy another Pixel at this point.
[Google Pixel 3 Questions & Answers] AsItLies:
Very unfortunate. I'd recommend to anyone experiencing this to let Google know. The more people that tell them their device is stuck in 'EDL' mode (and can't be gotten out of), the more likely they may respond with a possible fix.

It's really pretty ridiculous that this is happening, with a once flagship device.

cheers
[Google Pixel 3 Questions & Answers] ZetaPirate:
So I just learned something I was previously unaware of. Apparently, when you buy a device from Google, you are bound by an arbitration agreement. I had seen something mentioned earlier, either here or on that issue tracker, but hadn't confirmed it (as I threw those papers that came with the phone away). Basically, my understanding is that you can't sue Google, including class action suits, for most device (and related) issues, including inventory wide issues. You only have 30 days to opt out of said agreement after activating a device for the first time.
[Google Pixel 3 Questions & Answers] AsItLies:
If that were the case, then there would never be a lawsuit against any phone mfg. I'm sure your reading of the agreement is accurate, but I'd bet there are laws / exceptions that allow lawyers to bring civil suits regardless of the arbitration agreement. They do it all the time.

The issue here is catastrophic. The phone becomes completely and totally non functioning. If google doesn't respond in a reasonable time frame, there has to be recourse for those affected.
[Google Pixel 3 Questions & Answers] Amon Darthir:
Whelp, y'all know the story. Woke up this morning and my Pixel 4 is suddenly a very expensive paper weight. I see a variety of persons who were and weren't running the Android 12 Beta. I did have it running.

All the same symptoms. Phone is black as night. Plug in, and you get the Qualcomm goodness.
[Google Pixel 3 Questions & Answers] AsItLies:
Sorry to hear. a pixel 4 now? First I've heard of this with them. The 4a has the issue also, they have a specific thread for it. Haven't seen anyone with a 5 yet, but may just be a matter of time.

If you look at the Wiki page for the pixel 3, they mention this problem specifically at the bottom of the page.
[Google Pixel 3 Questions & Answers] Amon Darthir:
I wasn't far enough into digging to notice if the Pixel 4 had it's own thread or not. I have seen a few people mention it as a problem, but certainly not as prevalent yet as the Pixel 3. Also, once I understood the issue, a quick Google search showed that several outlets have been writing about it in the last couple months. Looks like the rate at which it's happening is increasing.
[Google Pixel 3 Questions & Answers] 350zfern:
Happened to my girls pixel 3 xl over the weekend. Literally woke up like this.
[Google Pixel 3 Questions & Answers] Nandosolera:
Hi everyone! I woke up last October 5 with the same problem. My Pixel 3XL bricked while charging during night.

I had the official android 11 rom, automatic updates activated. The October security update was release October 4, so I deduced that my phone was rebooted automaticaly due the update and never more wake up.

My windows PC recongise it as QUS_BULK_CID:... as all of your phones.

No guaranty, so spanish Google technical service don't take care of it.

Hope for a solution.
[Google Pixel 3 Questions & Answers] JSilver2021:
I was on the Android 12 Beta so I was able to open a support case for the issue on my phone, however, Android 12 has since been released and have yet to have any updates to the case or what will become of this issue.

I would hope to see a class action suit against Google/Qualcomm, but since the phone is "Out of Warranty" the likelihood looks bleak. :-(
[Google Pixel 3 Questions & Answers] nullx:
I just took the official android 12 update yesterday... phone was working fine.. went to sleep, woke up, and now am getting the same issue as everyone else..
[Google Pixel 3 Questions & Answers] AsItLies:
that's very unfortunate. Just to clarify, you say you 'just took' the official update? That means u got the OTA correct?

It seems, not exactly certain by any means, that it's the OTA process that is somehow causing this issue. And it doesn't seem to happen immediately, like a day or so later.

Not that that info helps you now. Personally, I'd look into making complaints with Google. It's totally not fair that some of these devices are becoming completely worthless much earlier than they should be.

cheers
[Google Pixel 3 Questions & Answers] nullx:
Yes the official OTA update to android 12. Really unfortunate and quite strange timing considering I pre-ordered the 6 pro just the other day... too bad this couldnt have happened AFTER I received the 6 pro...

But yea, I posted over in the main thread: https://support.google.com/pixelpho...lk-cid-likely-caused-by-security-update?hl=en

verrry annoying the phone was working perfectly and now it's just a brick..
[Google Pixel 3 Questions & Answers] ShadowVlican:
I also got the official OTA update to Android 12, and now a couple days later my Pixel 3XL has bricked itself. I'm sure this is not caused by Android 12 but just down to random dumb luck and coincidence. The phone died while I wasn't using it; I came back to it and found it dead.

The phone is dead. It's completely unresponsive, doesn't respond to the power button or volume button combinations to get into recovery mode, fastboot mode, etc NOTHING. I'm seeing the same QUSB_BULK_CID:0402_SN:XXXXXXXX in my device manager when I'm connected to my windows PC.

I finally got through to Google Support and they eventually said there's nothing that could be done. The phone is long out of warranty and not worth fixing. I've already pre-ordered the Pixel 6 Pro, hoping to use my Pixel 3XL for trade-in credit, but I guess I won't qualify for any credit anymore.
[Google Pixel 3 Questions & Answers] xtafan1:
If your phone is still working, is there anything you can do to retain access in case it enters EDL mode later? While not exact, I am thinking something analogous to the SHSH blobs of iphones.

If not for the pixel 3, has something been done on a similar phones that could be ported over with some effort such as light reverse engineering or a known security flaw?
[Google Pixel 3 Questions & Answers] AsItLies:
No, don't believe there is. EDL mode needs the 'firehose' file to access the device, but google won't release it.

It is actually fairly easy to access the device, with the firehose. I've used both qualcomms qfil app and the bkerler edl python utilities to access LG phones, but the firehose file is available for them, not the pixel 3.
[Google Pixel 3 Questions & Answers] FuPete:
Just replaced the mainboard of my girlfriends Pixel 3 because of the QUSB Brick. Her phone just turned off while listening to music. She was on Android 11, so in this case the Android 12 Update had nothing to do with this brick. Happened 3 days ago. Phone was bought on release.

I started with the Nexus 4, but this was our last Google Phone.
[Google Pixel 3 Questions & Answers] AsItLies:
sorry to hear, and I don't blame you re 'last google phone'. Just to clarify; did replacing the mainboard fix the issue?

Also, to clarify, the suspicion we have, of why this is happening, isn't because of updating to android 12, it's because of doing an OTA (to 12, 11, security patch, etc).

And again, it's only a suspicion, derived at because so many have reported they experienced this 'edl brick' soon after having done an OTA update (not a specific one, just OTA update).

What we know for sure is that the abl partition can't be read, it's corrupted, the hardware has gone bad, etc etc (we don't know). When something like that happens, the device will go into edl mode automatically.

Also, if one looks in the 4a forums, they too have been experiencing the same thing. It's crazy really, to think google hasn't addressed this. What a thing to have to live with, that your phone may one day simply be unusable, not because the battery wore down, not because of some change you made, etc etc, But because the device just simply bricked itself.

cheers
[Google Pixel 3 Questions & Answers] FuPete:
Well, maybe it's just my current anger, never had a electronic device fail so fast without a reason. My approximately 15 year old PSP is still running, my Nexus 4 was running for 5+ years, my Nexus 6 was running for 5+ years, her 6P was running for 5+ Years and the Pixel 3... Well.

Yes, the bricked Pixel 3 is now running fine with the replaced mainboard. I bought a Pixel 3 with cracked screen and backcover for 30€ and disassembled the mainboard. Additionally I have now a original spare battery, if the battery degrades in the future.

Hmmmm. Can't say if she did a OTA recently.
[Google Pixel 3 Questions & Answers] timg11:
I have a Pixel 3XL. It is still working fortunately, and I guess I'll have to deny further OTAs from what I read. I'm thinking about what my next phone will be. I've owned and liked Pixel phones, and the Pixel 6 looks appealing. I would buy it in the next few months under normal circumstances. But until Google comes clean on this EDL bricking issue (explains the root cause, confirms it has been fixed, and provides a fair remedy for customers affected) I'm done. The fact that this issue has been ignored for 6 months leaves me feeling very negative towards Google and their phones -- they will have to do something significantly positive to win back their customer trust.
[Google Pixel 3 Questions & Answers] SSamDav:
Hi all,

I have a Pixel 3XL and until today morning it was working fine with the android 12, however, when I wake up it is bricked 😥 I tried all the possible combination of power + volume buttons but the phone doesn't respond, however, when I do that with the phone connected to my laptop, windows recognizes that I'm plugging and unplugging a new device (I say this because it does the sound of connecting a new device). Moreover, when I go to device manager I think my phone appears with the name QUSB_BULK_CID. I just read this thread and it seems that the solution wasn't found I will try to drain the battery on my and charge it to see if I can restart again.
[Google Pixel 3 Questions & Answers] AsItLies:
Very unfortunate. Be sure to let google know that this happened. We don't know that they'll ever do anything about it, but it's clearly not something that should be considered 'reasonable', these devices are not that old.

cheers
[Google Pixel 3 Questions & Answers] mcwups1:
Mine just died tonight.

I've been shrugging off the update, swiping it away. I was literally on my phone when the screen went dark, and now is dead, bricked.

I can plug it in to a PC, it identifies something there, but no Fastboot commands, or Device attached. I get this in my Device Manager "

QUSB_BULK_CID:0402_SN:xxxxxxxx".

Is there a file you can get from QCOM to get this fixed?
[Google Pixel 3 Questions & Answers] ShadowVlican:
afaik, there hasn't been any fixes for this... contact google and hope they replace it, otherwise we're all SOL
[Google Pixel 3 Questions & Answers] mcwups1:
Spent from 10pm to 12:50 am waiting in chat for Google assistance. They are no help, of course. My phone is immaculate. Charging port is great, screen protector and case have it looking like I just pulled it out of the box from years ago.

I can't believe the thing just died in front of my face. Completely dead, and the USB on my PC doesn't recognize it. I can hear it turning off and on though, if I hold the power button. It just doesn't boot up, or show anything in my ADB Devices search. It's just crazy.

I was going to have to get a new phone anyway, because I was on Sprint service, and with TMobile taking it over, this phone couldn't be used on their towers, or so they told me.

I have to upgrade to another phone with 5G. Me and my oldest daughter. Fun.
[Google Pixel 3 Questions & Answers] ShadowVlican:
I feel your pain... I also had to wait quite a long time until I got through to Google Support and in the end they were not helpful. My Pixel 3XL was bought almost 3 years ago at launch, so it was a long shot getting Google to cover this defect under warranty. The media ought to put more pressure on this planned obsolescence and unnecessary e-waste.

Even though I've got the Pixel 6 Pro on order, I could've given this phone to my parents or kept it as backup. Now it's just a useless paper weight not worth repairing.
[Google Pixel 3 Questions & Answers] AsItLies:
Sorry to hear. Just as an fyi though, pretty sure it could have easily been used on t-mo towers by just flashing the generic firmware rom google makes readily available.

It's the rom that controls which towers the phone will have availability for, and the generic / open rom has all the major bands (including 71) that t-mo uses.

cheers, be sure to let google know this happened, it really should not be happening for sure.
[Google Pixel 3 Questions & Answers] mcwups1:
They really should! This should be an "Apple slows down phone near new phone launch" type of headline. Should be made more public and there should be something done about it. My phone is immaculate, but all the sudden, when I get a notification to update, it craps out?

Really needs more attention.
[Google Pixel 3 Questions & Answers] mcwups1:
That's interesting. I remember flashing radio's a long time ago with HTC phones, and didn't really think about it. I surely would have got a new phone without remembering this.
[Google Pixel 3 Questions & Answers] sj3vans:
Happen to me tonight. 3XL. Same as everyone. I've loved this phone! Told many people about how well it has worked for me. :( Boooooo!
[Google Pixel 3 Questions & Answers] AsItLies:
Another unfortunate experience, sorry to hear. Out of curiosity, did u recently do an OTA update? It **seems** that may be causing the problem, we're not sure.

thnx
[Google Pixel 3 Questions & Answers] sj3vans:
I have been on 12 via OTA for about a week and had been quite happy with it. There may have been OTA update but I am not aware of it if there was.

I have noticed that if I hold down the power for an excessive amount of time, then plug it in to a PC, I get nothing, same if I then press the button briefly to pressumably turn it on. It only get the PC to recognize it if I hold down volumn-down and the power button. Then after about 15 seconds the PC blips as if it connected a USB device. Not sure what that means but conitnuing to troubleshoot.
[Google Pixel 3 Questions & Answers] JSilver2021:
@AsItLies , I do not believe this revolves around an OTA update by Google. When mine bricked, I was running Android 12 Beta 3 or 4 (do not recall) and was well into 2-3 weeks of current update when phone in the middle of the day while listening to music just bricked. There were no pending updates and all was current at the time of my failure. I think the timing of most around OTA updates is a coincidence, but does not seem to be the actual cause.

I think I had read somewhere that Qualcomm had the ability to push updates on their own to the devices to update the chipset if needed, however I cannot find nor remember where think I read that. However I read so many different articles about so many subjects, I could be conflating stories.
[Google Pixel 3 Questions & Answers] AsItLies:
Really the only thing we have to go on is that many people reporting this issue indicate they 'did an OTA update' recently. Some indicated 2 or 3 days prior.

That's all we have, and absolutely, it could be inaccurate. It could be though that an OTA is corrupting some part of the boot chain that doesn't get recognized right away. Then, it eventually gets recognized (or maybe it trys to reboot for some reason), and it can't do anything but go to edl mode.

Have never heard of qualcomm pushing updates on their own. Don't think google would allow that.

cheers
[Google Pixel 3 Questions & Answers] mrbillishere:
I'm curious if anyone recalls seeing a 'device is corrupted...' message like I did. The end result is the same, a bricked Pixel 3 stuck in EDL mode but I wonder if the means by which my device got into this state is different.

Here's the long version:

My stock, carrier-unlocked Pixel 3 64GB is dead within 24 hours of the Android 12 OTA upgrade.

Was prompted earlier in the week that the Android 12 OTA was ready but I had to postpone it. So, this past Saturday morning I elected to have the phone upgrade itself to Android 12. Seemed to go just fine. Used the phone for the remainder of the day/night. Went to bed, woke up around 2AM and picked it up to check the time and instead, discovered this message being displayed:

"Your device is corrupt. It can't be trusted and may not work properly." The only action I could take was 'Press power button to continue' which, upon doing so, caused the phone to apparently power off and ever since, we got nothing.

Can't power it up at all. Can't boot into fastboot mode. It is literally unresponsive.

Like everyone else, when I plug it into my Windows PC, plug n play detects it as a "QUSB_BULK__CID:0402_SN:9CAF70CD"

This phone was never bootloader unlocked, nor did it ever run anything custom. Developer Options never enabled, thus USB debugging was never enabled. Pure OEM setup.

It's absolutely ridiculous that a routine OTA update (the timing is too coincidental to not be related to that) would make it impossible to recover the software/OS on the cellphone but clearly I am not alone. I've owned Nexus devices, the Pixel XL, the Pixel 3 and 3XL, the 4XL and I have a v6 Pro coming next week. Heck, I even got invited to join the Pixel SuperFans Facebook group. That said, I'm in the throws of an existential brand-loyalty crisis over this because of how much of a disruption this has caused and the seeds of doubt that researching this has sewn.
[Google Pixel 3 Questions & Answers] AsItLies:
Sad to hear. Totally understand the brand-loyalty issue... it's difficult to fathom google would let this go on without some response / explanation.

Numerous others have had the same suspicion re the timing of this and a recent OTA update. It *seems* that something is getting corrupted but it's not detected for a period of time...

I'd encourage you and anyone else to let google know about this, even if it's just an email to their support. It's not at all a 'reasonable expectation'.

cheers
[Google Pixel 3 Questions & Answers] ab123321:
Got my Pixel 3 bricked today AND it was running Android 11 (August patch) :P