Infeasible

Bug

Status Update

No update yet.

Description

za...@gmail.com

created issue #1

Jun 25, 2021 06:04PM

Pixel 3 died around 7am Pacific time, with my waking up to a black screen.

It is able to charge both wired and wirelessly. I see "Qualcomm, Inc. Gobi Wireless Modem (QDL mode)" when I plug it into my computer and run `lsusb`, but it is not detected by `adb devices` or `fastboot devices`. I see it rebooting by watching `lsusb` while I hold down the power button.

This seems to be more than an isolated incident, as this reddit thread shows multiple users in the same situation.

https://www.reddit.com/r/android_beta/comments/o7h1li/pixel_3_not_turning_on_black_screen/

* What device are you using? (for example, Pixel 4 XL)
Pixel 3

* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
Phone was on a wired charger overnight while sleeping.

* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Hardware
_____________________________________________________
Google Response:
“This issue occurred due to the natural lifecycle of a memory component. Memory components have a predefined lifecycle based on consumer use cases over time. The recommended solution is an out of warranty repair or replacement - see

https://support.google.com/pixelphone/answer/10227672 to contact our authorized repair vendor”.
_____________________________________________________

Comments

ad...@google.com <ad...@google.com> Jun 28, 2021 01:18PM

Assigned to ad...@google.com.

ad...@google.com <ad...@google.com> #2Jun 28, 2021 06:58PM

Information redacted by Android Beta Feedback.

ja...@gmail.com <ja...@gmail.com> #3Jun 28, 2021 07:13PM

Thank you for reporting this issue. For us to further investigate this issue, please provide the following additional information:

Could you please provide any necessary screenshots of the issue for clarity?

ad...@google.com <ad...@google.com> #4Jul 1, 2021 01:41PM

Please provide the requested information to proceed further. Unfortunately the issue will be closed within 7 days if there is no further update.

za...@gmail.com <za...@gmail.com> #5Jul 1, 2021 02:58PM

- Build Number: google/lynx_beta/lynx:14/AP11.231117.006/11174680:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Screenshot added

Debugging information
Google Play-Dienste
com.google.android.gms
Version 234914038 (23.49.14 (190400-590296185))
System App (Updated)

Android System WebView
com.google.android.webview
Version 609914433 (120.0.6099.144)
System App (Updated)

Network operator:

vodafone.de
SIM operator: Vodafone

Filed by Android Beta Feedback. Version (Updated): 2.39-betterbug.external_20231115_RC02 (DOGFOOD)
To learn more about our feedback process, please visit

https://developer.android.com/preview/feedback#feedback-app.

ad...@google.com <ad...@google.com> #6Jul 2, 2021 09:17AM

Information redacted by Android Beta Feedback.

ja...@gmail.com <ja...@gmail.com> #7Jul 2, 2021 07:41PM

The above screenshots are not relevant to the issue. Could you please share another screenshots?

ad...@google.com <ad...@google.com> #8Jul 7, 2021 11:21AM

Why are the Screenshots Not relevant? They Show the settings where the battery information should be. But my system language ist German, maybe therefore you wrote it's not relevant.

mo...@gmail.com <mo...@gmail.com> #9Jul 7, 2021 12:38PM

We have passed this to the development team and will update this issue with more information as it becomes available.

ja...@gmail.com <ja...@gmail.com> #10Jul 7, 2021 08:15PM

redacted

ch...@gmail.com <ch...@gmail.com> #11Jul 7, 2021 11:41PM

We only enable this page on Pixel 8a and beyond, so this is WAI(Working as Intended)

be...@gmail.com <be...@gmail.com> #12Jul 9, 2021 02:07AM

Why was it removed in the first place and why it worked until now? It's such a useful feature...

ky...@gmail.com <ky...@gmail.com> #13Jul 11, 2021 06:03AM

Could you confirm what the reasoning is behind removing this feature from all existing devices, when it seemed to work ok prior to QPR2?

ec...@gmail.com <ec...@gmail.com> #14Jul 12, 2021 10:21AM

Please re-evaluate the removal of this feature.

It's a very useful feature, and it's an AWFUL practice to say the least to add a feature with the QPR1 update, announce the feature as one of the highlights of the OS release, and then remove it in QPR2.

No reason why it should only be available on Pixel 8a and newer devices.

ch...@gmail.com <ch...@gmail.com> #15Jul 12, 2021 06:24PM

We only enable this page on Pixel 8a and beyond

So, just to be clear, this page -- which is working perfectly fine as is and actually brings considerable value to those who ideally want to keep their phones for more than 1 year -- is being removed for no apparent reason other than "because we feel your old device doesn't deserve this feature?"

I didn't know the Pixel 8A and other phones had some special hardware capability that allows it to get this feature -- a feature that has been working perfectly fine for the past 3 months on older devices with Android 14.

Perhaps, it would benefits everyone here if the developers were a bit more transparent on this.

ja...@gmail.com <ja...@gmail.com> #16Jul 13, 2021 07:48AM

Google be transparent lol lol lol

ad...@google.com <ad...@google.com> #17Jul 14, 2021 05:21PM

Beyond frustrated. The excuse of "Working as Intended" is not only infuriating but also reeks of a lack of accountability.

It's mind-boggling that a feature, which worked perfectly fine for months, is suddenly considered a luxury exclusive to newer devices. Is this some kind of twisted tech elitism? Older phones don't deserve basic functionality?

The comments from other users echo my sentiments – this move is a slap in the face to those who have been loyal to your brand. Announcing a feature as a QPR1 update highlight and then stripping it away in QPR2 for no apparent reason is nothing short of incompetence. Your lack of transparency on why this decision was made is unacceptable. Users deserve more than a dismissive "WAI" response. Provide a valid explanation for this blatant disregard for user experience on older models.

be...@gmail.com <be...@gmail.com> #18Jul 14, 2021 05:23PM

The level of the incompetence in your company is fucking insane. Your bullshit software team and you should go work in a fast food chain or something, and EVEN THEN I am not sure the company wouldn't go bankrupt.

ch...@gmail.com <ch...@gmail.com> #19Jul 14, 2021 05:35PM

I do agree with others. This is not some AI stuff that needs to be locked to new devices to sell them in false pretence of hardware incompatibility. This is a basic feature and users should have complete and full knowledge about battery health. In this form or another. What makes it worse is that feature was taken away and the reason why it was removed is disrespecting to Pixel owners.
Can this be re-evaluated and if escalated please? You know...just "Don't be evil"

jg...@gmail.com <jg...@gmail.com> #20Jul 16, 2021 05:24PM

Have you decided yet when you will be removing this useful feature from "Pixel 8a and beyond" phones?

am...@gmail.com <am...@gmail.com> #21Jul 16, 2021 05:30PM

Plus 1

is...@gmail.com <is...@gmail.com> #22Jul 18, 2021 02:32AM

Google Pixel 8 pro, obsolete already...

ni...@gmail.com <ni...@gmail.com> #23Jul 19, 2021 05:28AM

ka...@gmail.com <ka...@gmail.com> #24Jul 19, 2021 04:17PM

ro...@gmail.com <ro...@gmail.com> #25Jul 19, 2021 06:41PM

+1

I am glad it got "Assigned" and marked as "Bug"!

ro...@gmail.com <ro...@gmail.com> #26Jul 19, 2021 06:44PM

+1

You are kidding me that this was intentionally removed and will now be only available for the Pixel 8a and beyond?
Pixel 8 Pro user here who loved this feature...
Please revert your change!

ni...@gmail.com <ni...@gmail.com> #27Jul 19, 2021 11:38PM

br...@gmail.com <br...@gmail.com> #28Jul 20, 2021 12:49AM

This is not a selling feature, so please bring it back. This would greatly help for those buying Pixels second hand

go...@gmail.com <go...@gmail.com> #29Jul 20, 2021 02:57AM

+1

Imagine buying Google's most expensive phone and then seeing software features locked to the budget model of the exact same series of phone. Definitely going to heavily reconsider Google products in the future if this is the way Google is going to approach basic software features.

si...@gmail.com <si...@gmail.com> #30Jul 20, 2021 05:48AM

ad...@google.com <ad...@google.com> #31Jul 20, 2021 12:50PM

deleted

be...@gmail.com <be...@gmail.com> #32Jul 20, 2021 12:58PM

Definitely going to heavily reconsider Google products in the future if this is the way Google is going to approach basic software features.

You really should reconsider how you treat your customers using your phones or your services in general. The only reason I am not using iPhone yet is that I hate their walled garden policy even more, but each and every case of your corporate incompetence really starts to make me think that walled garden might not be as bad as this. My Pixel 6a is great, but it has its issues (dual SIM calls dropping – luckily solved by RMA, inability to tap to wake from time to time, an Android bug known since 2018, I cannot remove obsolete devices from Google Play, reported for many years too, inability to use certain features like Family Link or Google Play rating as a Workspace user etc.).

I love receiving new Android a few hours after it's announced, but maybe it's just not worth it.

Pls do the right thing and bring this one feature back!

ma...@gmail.com <ma...@gmail.com> #33Jul 20, 2021 01:00PM

Yep really, you need to add this feature back to phones which had it already. This is very anti-customer behavior, if you want to keep your loyal Pixel fans happy and keep them in the Pixel ecosystem then dont remove useful basic features they already had.

ka...@gmail.com <ka...@gmail.com> #34Jul 20, 2021 01:02PM

+1
If it wasn't bad enough how buggy this phone is, now you remove features that were a selling point in the first place?

za...@gmail.com <za...@gmail.com> #35Jul 20, 2021 01:10PM

+1

Imagine promising 7 years of OS updates and only 2 year old devices getting pretty much nothing new in QPR's and also getting treated like this. Great job Google.

mo...@gmail.com <mo...@gmail.com> #36Jul 20, 2021 02:26PM

My Pixel 6a used to show this setting but after an update it disappeared. LAME. (screenshot attached)

co...@gmail.com <co...@gmail.com> #37Jul 20, 2021 07:20PM

Recently purchased Pixel 8 pro. That was three months ago. With the promise of updates and support for 7 years. After three months, they report that it is already out of date🤣

be...@gmail.com <be...@gmail.com> #38Jul 20, 2021 07:55PM

To respond to a commenter:

now you remove features that were a selling point in the first place?

Just to be clear, a feature like this shouldn't even be called a "selling point." This is a feature that is widely available on other Android and Apple devices, and there are many use cases.

Some examples:

if you buy a refurbished smartphone, being able to see the battery health information is important since it tells you if your battery is too old or needs to be replaced (in which case you can ask for a warranty exchange). If I buy a refurbished phone, I expect the battery to be at least somewhat usable. If the battery only has 60% estimated capacity, I would get that returned ASAP.
although not as significant of a reason, if you want to keep my phone for more than 1 year, being able to see your phone's battery health is important because you can decide when the phone's battery should be replaced.

There's no reason why this feature should be limited to the "Pixel 8a and beyond." If you create a full bug report (which can be done through Developer Options), or you use an app that can get ADB access (e.g., aBattery and Shizuku), or you use ADB directly, you can easily get these numbers (battery cycle, estimated capacity remaining, etc.). I'm able to do this on a Pixel 8 Pro (a device that's only 6 months old) and a Pixel 4A (which is stuck on Android 13 because Google no longer supports it). So, in other words, the numbers are clearly there, and they're clearly available.

I could talk more about how this behavior just shows that Google is becoming more anti-consumerism, but I digress.

I do hope that Google changes course and makes battery health information available to all devices with Android 14. Seeing that this bug report has been reassigned, reopened, and labeled as a bug does give me some hope. We'll see what happens in the next feature drop.

ka...@gmail.com <ka...@gmail.com> #39Jul 20, 2021 08:10PM

This feature needs to come back. It's kind of crazy that it was NOT in Android until now--as this is basic info you can call up (in some form or another) on almost any other type of device that has a battery in it. There was no excuse for removing it again. If this is WAI then what you have is a design defect instead of a code defect, but it's still a defect.

ro...@gmail.com <ro...@gmail.com> #40Jul 20, 2021 11:42PM

I am kind of disappointed too. It was a nice statistical feature for me. What's most annoying is that it got added and then removed again. Why add it in the first place then?
Dear Google Devs, please bring this feature back.

cl...@gmail.com <cl...@gmail.com> #41Jul 21, 2021 10:01AM

Bring it back!

no...@gmail.com <no...@gmail.com> #42Jul 21, 2021 09:11PM

ro...@gmail.com <ro...@gmail.com> #43Jul 22, 2021 08:42PM

Been a loyal Pixel user since the Nexus day till today still using Pixel phone. And how on earth that Google ridiculously removed feature that is useful?
And Pixel 8 Pro has been promised 7 years of OS update and now they are starting to remove features bits by bits...
Is this another way to stop user of being aware of their battery is degraded and force user to replace phone yearly or every 2 years?
So much of "eco-friendly".

Dear Rick Osterloh, are you aware of this? lol...

ra...@gmail.com <ra...@gmail.com> #44Jul 23, 2021 02:24AM

The feedback has been passed on to the product team for consideration.

ma...@gmail.com <ma...@gmail.com> #45Jul 23, 2021 07:40AM

Very poor decision. Google should consider changing marketing to "Your Pixel is getting massively worse with time - Pixel Drops". In either case I think investing any money in hardware made by Google should be reconsidered by users.

pe...@gmail.com <pe...@gmail.com> #46Jul 24, 2021 05:49PM

Wow, you closed this issue again? I had the battery info on my Pixel 6a, you removed it and stated that it will be available on Pixel 8a and beyond. I now have the Pixel 8A and there is still no battery info. Please re-open this issue and fix it.

ph...@gmail.com <ph...@gmail.com> #47Jul 25, 2021 11:28AM

Oh, sorry, I have the info on my Pixel 8a, was checking the wrong Settings page. :-) Still sad you removed from older Pixels which already had this, there is no reason why you should do so.

za...@gmail.com <za...@gmail.com> #48Jul 25, 2021 02:41PM

Just wanted to add mine here. Tried to check messages at 1AM, phone was dead. Plugged it in, still dead. Tried the hold power down and vol down (and up), dead.

ri...@gmail.com <ri...@gmail.com> #49Jul 25, 2021 02:53PM

Same issue with my Pixel 3XL, went to bed with a working device, woke to one that is completely unresponsive. Black screen, tried several attempts of vol down and power, no boot.
I was waiting to upgrade to a Pixel 6 in October, since no Google devices seem to be available for sale in the US now, looks like I am headed back to Motorola.

lo...@gmail.com <lo...@gmail.com> #50Jul 27, 2021 12:29AM

Same thing happened with my pixel 3. I plugged it in before bed and it was working perfectly fine. Woke up and it was completely unresponsive. I had thought maybe it came unplugged at the wall so I tried another charger and still no response. Dead. Plugged it into the pc and it showed up as "bulk" device.

di...@gmail.com <di...@gmail.com> #51Jul 27, 2021 09:39AM

Happened to me yesterday on my pixel 3. Was working fine and now get the bulk message when plugged into the PC. Never buying a pixel phone again and will probably move away from google entirely. Completely unacceptable .

gl...@gmail.com <gl...@gmail.com> #52Jul 28, 2021 05:15AM

Happened to my wife's Pixel 3a this morning, completely bricked overnight. Just got done with the two year of payments... Was going to coast for a bit before upgrading. Sucks that Google might be forcing my hand here. Don't really feel comfortable buying another pixel if they don't address this issue.

be...@gmail.com <be...@gmail.com> #53Jul 29, 2021 08:46AM

Unbelievable! Woke up this morning and my Pixel 3xl was dead! Same Issue. I can't believe that there is no solution yet as this Problem is known for quite some time! My Phone was fine and there wasn´t an OTA update yesterday, which might have caused it. I have never ever experienced this with any phone in the past (samsung). I´m very dissapointed as I was waiting for the pixel 6 to arrive. But now, due to the fact that Google is not able/willing to fix this, we have to accept the fact that this might happen again! And I won´t pay over 1.000€ again for a phone, knowing that it can break without my own fault at any giving time!

For the very first time I´m really considering buying an Iphone as I just want a great phone which lasts longer than 3 damn years.

This s**t is just unbelievable!

Greetz from Germany

ka...@gmail.com <ka...@gmail.com> #54Jul 29, 2021 01:12PM

Okay, it's been more than 30 days since this issue was created and three dozen reports of Google bricking their phones on this site alone.

It seems to me that this should be elevated to a higher priority. This isn't just a glitch, it's destroying customer's phones.

ro...@gmail.com <ro...@gmail.com> #55Jul 29, 2021 01:47PM

The incredibly frustrating part is that other manufacturers release the files that allow users to reflash their devices. Google do something. I want my stock pixel 3xl back

th...@gmail.com <th...@gmail.com> #56Jul 29, 2021 02:02PM

Commenter #53, don't cross over to the iPhone dark side! I didn't have time to wait for Google to get its act together on this issue. The temporary phone I was using is one of the old Samsungs with the nifty exploding battery feature, and it was staying hot. I ended up buying 2 Motorola G Stylus 5G phones to replace my Pixel 3XL & my son's Pixel 3. Both phones with Moto Care for both were less than $1000 USD total ordered unlocked directly from Motorola's website. We have been using them for a few days, and we both love them just as much, if not more, than our Pixel 3 & 3XL. The battery life has been amazing, even in the poor service area where we live. It's also very fast!

pb...@gmail.com <pb...@gmail.com> #57Jul 29, 2021 02:07PM

I also experienced my 3XL bricking overnight earlier this week. Very disappointing for a phone that wasn't even 3 years old.

be...@gmail.com <be...@gmail.com> #58Jul 29, 2021 02:09PM

This sucks. And the problem is all other phone similar or smaller than the Pixel 3 are the 3a/4a, probably the 5a, and the iPhone 12 mini.

I don't want a bigger phone. I miss my iPhone 3gs size, but not Apple.

co...@gmail.com <co...@gmail.com> #59Jul 30, 2021 06:02PM

Just want to add another phone to list list. My Pixel 3XL bricked last night, same as everyone else, and the remediation steps did not help.

st...@gmail.com <st...@gmail.com> #60Jul 31, 2021 03:31AM

Also happened to my 3XL back in May. Phone stuck in EDL mode...At this point I'd really just like some way to recover files off the phone. Seeing this same thing from too many people for google to not being doing anything.

da...@hotmail.com <da...@hotmail.com> #61Jul 31, 2021 04:47AM

hey Google, thanks for bricking my Dad's phone /s

to...@gmail.com <to...@gmail.com> #62Jul 31, 2021 07:27AM

Same thing happened to my pixel 3 xl yesterday. I went to bed while phone on the charger, used it last time at 3 am and woke up at 8 am with a dead phone. Phone is phsyically in absoluty fine condition, never dropped, spilled water or any cracks / big scratches. Connected to a pc it shows QUSB_BULK_CID:... and it's disappearing and reappering when long pressing power button - so it's still physically alive and probably stuck in EDL. I'm also out of warranty.. this really sucks and will prevent me from buying any other google phone.

:-(

ja...@gmail.com <ja...@gmail.com> #63Jul 31, 2021 12:43PM

After contacting the support helpdesk multiple times (10+ mails), pointing out to this issue tracker, Reddit threads and Google support forum threads with the same issue, I finally got my RMA accepted. My phone was 2.5 years old and I'm happy to say that I'm typing this of my new refurbished pixel 3 phone.

Hopefully this one won't brick, no more beta for me.

ph...@gmail.com <ph...@gmail.com> #64Jul 31, 2021 03:03PM

Everyone - if this happened to you/your phone/significant others you are reporting on behalf of, make sure you "star" the top at the top next to the issue number. That tracks how many are affected, from what I understand.

be...@gmail.com <be...@gmail.com> #65Jul 31, 2021 09:40PM

For those in Quebec, use the full extent of your rights.

http://www.google.com/url?sa=D&q=https%3A%2F%2Fwww.opc.gouv.qc.ca%2Fen%2Fconsumer%2Ftopic%2Fwarranties%2Fapplying-warranty%2Fapplication-legal-warranties

Currently in chat with Google about this. They are basically telling me that they can brick our phones with to repercussion.

94...@gmail.com <94...@gmail.com> #66Aug 1, 2021 07:59AM

I just got hit by this. Phone was face down on my desk and after an hour or so it was completely unresponsive and unable to charge. Pc shows QUSB_BULK_CID and I found a very recent thread filled with people saying the same thing happened to them.

https://forum.xda-developers.com/t/fix-pixel-3-qusb_bulk_cid-xxxx_sn-xxxxxxxx.4205331/

sh...@gmail.com <sh...@gmail.com> #67Aug 1, 2021 01:31PM

Same issue here, working fine last night at 12:30am, nothing this morning.

Infuriating to say the least

er...@gmail.com <er...@gmail.com> #68Aug 2, 2021 11:27PM

My phone is bricked today too. Screen completely black. Holding Power Button and Vol buttons does not boot into recovery. Windows recognizes the devices as QUSB_BULK_CID:0402_SN:<redacted>.

Came here from this thread:

https://forum.xda-developers.com/t/fix-pixel-3-qusb_bulk_cid-xxxx_sn-xxxxxxxx.4205331

ti...@gmail.com <ti...@gmail.com> #69Aug 4, 2021 05:13PM

My phone bricked today. Same thing on my Google Pixel 3XL. Phone did a back up at 2:50am and then crashed sometime before I woke up.

an...@jorgensenfamily.us <an...@jorgensenfamily.us> #70Aug 4, 2021 10:37PM

Mine was bricked this way ages ago during an Android beta. If I plug it in, it comes up in this QUSB_BULK_CID:0402 only. IIRC mine was still in warranty... except that I was using the beta, so no warranty. I'd love to be able to recover it, and it seems like the path to do so is pretty clear, just need Google to provide the tool and files we need.

Worth mentioning that uBreakiFix does not have the tools to recover these, because Google hasn't provided them anything either.

Are there enough of us for a class action lawsuit maybe? I know mine was bricked by an OTA, and it looked like a lot of people are seeing exactly the same thing.

ks...@gmail.com <ks...@gmail.com> #71Aug 6, 2021 07:35PM

Add another one to the list. My wife's 3XL just did this. There is an obvious issue with, likely, a recent update since this is suddenly happening to a lot of people.
Google, I know you're a faceless corporate machine, but please respond in some manner.

na...@gmail.com <na...@gmail.com> #72Aug 7, 2021 12:58PM

Another one here, woke up today thinking the phone was just out of charge. Nope it is bricked. It will charge but I get no response from the phone.

oz...@gmail.com <oz...@gmail.com> #73Aug 7, 2021 12:59PM

Add another here. Pixel 3 bricked overnight, totally black screen. Plug into PC and get QUSB_BULK_CID device id in Windows Device Manager. Can see it turning off and on again as I hold power, or power+down.

Left it drain, then tried the power+down as recommended. Same outcome. Phone appears to have corrupted bootloads as suggested by others in thread.

Will contact Google support for options.

ke...@gmail.com <ke...@gmail.com> #74Aug 7, 2021 03:04PM

Same issue for my google pixel 3xl, when i woke up the phone refused to power on. I think that's why they move to tensor because some qualcomm processor on other phones were bricked in the same way.

oz...@gmail.com <oz...@gmail.com> #75Aug 8, 2021 04:40AM

Support just advised to send to authorised repair centre. That's pretty annoying, but going to follow it through. Hopefully it's a quick restore of firmware. What I don't understand is how it happened in the first place, and why it's happening to so many people.

I can only guess there's orders of magnitude more people with the issue that don't come to the issue tracker and just think their phone is plain dead.

pe...@gmail.com <pe...@gmail.com> #76Aug 8, 2021 12:05PM

+1 Google Pixel 3

Woke up to black screen. Plug into PC and get QUSB_BULK_CID device id in Windows Device Manager,

oz...@gmail.com <oz...@gmail.com> #77Aug 8, 2021 12:10PM

Note to everyone: Make sure you 'star' the issue (up top beside the bug number dropdown) so Google can see how many people this is affecting.

ja...@gmail.com <ja...@gmail.com> #78Aug 8, 2021 05:54PM

Same experience as others - Pixel 3XL Android 12 Beta 1. Overnight became completely unresponsive.

jd...@gmail.com <jd...@gmail.com> #79Aug 8, 2021 07:44PM

Am having the same issue - no access to bootloader and device appears to be bricked with the exception of QUSB BULK when plugged in.

ci...@gmail.com <ci...@gmail.com> #80Aug 9, 2021 03:04AM

Happened to me in December 2020. Was using it and placed it into my pocket only to find a dead screen few mins later. When connected to computer I get the same message that a device is detected starting with QUSB. Still waiting for a solution.

me...@gmail.com <me...@gmail.com> #81Aug 9, 2021 06:13AM

Same Problem with Pixel 3 and QUSB_BULK_CID device id in Windows Device Manager....

co...@gmail.com <co...@gmail.com> #82Aug 9, 2021 06:15AM

Just to let everyone know, I reached out to Engadget to inform them of this issue. Perhaps if there is a higher-profile piece done on it there could be some restitution. Don't forget to star!

ke...@gmail.com <ke...@gmail.com> #83Aug 9, 2021 07:52AM

Same issue happened to me a few days ago on my Pixel 3. Working fine when I checked my phone at 5am but by 7am it was completely unresponsive.

jh...@gmail.com <jh...@gmail.com> #84Aug 9, 2021 07:43PM

Got up this morning with bricked Pixel 3! .... it shows QUSB_BULK_CID in Windows Device Manager...

er...@gmail.com <er...@gmail.com> #85Aug 9, 2021 09:20PM

I should note that my issue is occured on the latest Android 11, and suspect this is the case for many others posting here. I believe this issue tracker is intended for the Android 12 beta development. But I'm not certain what resources if any are available for reporting issues with the production build.

I have contacted Google Support and have basically run into a dead end with them claiming it to be a hardware issue that would need to be repaired at my own cost.

Based on this link it appears Google introduced a fix for an issue causing this problem. It would seem that fix was either reverted or a new issue with similar results has been introduced.

https://source.android.com/security/bulletin/pixel/2019-07-01

Thanks for the advice to star the topic I have done so.

ja...@gmail.com <ja...@gmail.com> #86Aug 9, 2021 09:25PM

I was neither sure if it had to do with the android 12 version; but after reading those posts I don't think it is related to that.

I also want to mention that, after a lot of emails and refering to this bug, Google support did offer me a free RMA even while my warranty was expired.

I just hope my refurbished pixel 3 will last long enough and not have this same issue.

ks...@gmail.com <ks...@gmail.com> #87Aug 9, 2021 09:32PM

Yes, I did want to reply to confirm that my wife's affected 3XL was on Android 11, not the 12 beta. I was linked this issue listing not realizing it was only for the 12 beta.
There are currently mixed reports as to whether this issue would be fixed for free or not. I suspect it is a roulette as to what support rep you talk to. Also not clear if the RMA would result in data loss or not.

ja...@gmail.com <ja...@gmail.com> #88Aug 9, 2021 09:35PM

I got a refurbished phone back and I think even with a repair it would result in data loss. Mainly losing all your keys in the authenticator app is frustrating...

oz...@gmail.com <oz...@gmail.com> #89Aug 9, 2021 10:07PM

From

comment #85

, the bug track references for the Pixel 3 getting stuck in EDL mode are A-122000615, A-133150859. I don't have access to those in the tracking system, but hopefully will be a good starting point for the dev investigating.

For the Google staff looking - is it worth creating a second tracking issue for Android 11, which seems to be where most people on this thread are finding the issue, or are you happy to just use this ticket for both the 12 beta and 11 problem?

ya...@gmail.com <ya...@gmail.com> #90Aug 10, 2021 01:13PM

Adding myself to the list, left out the room and came back to a bricked Pixel 3 XL

da...@gmail.com <da...@gmail.com> #91Aug 11, 2021 01:56AM

Ran into the same issue today, had my phone charging and now it is bricked. Experiencing the same bootloader issue as the phone is recognised as a USB device when plugged into a PC but everything else won't work. Unable to flash to stock.

su...@gmail.com <su...@gmail.com> #92Aug 11, 2021 04:17AM

Bricked my 3xl mid July with andorid 11. There was a message about device being corrupt to restart and it never powered on after that.

ma...@gmail.com <ma...@gmail.com> #93Aug 11, 2021 04:34AM

Commenting to stay in the loop and add another experience of my Pixel 3 (Android 11, Aug 2021 update) while charging overnight this weekend. Find My Device last locates the phone at 7:30 AM Sunday Pacific and PC connection also shows QUSB_BULK_CID

ky...@gmail.com <ky...@gmail.com> #94Aug 11, 2021 01:13PM

Woke up (very late for work) this morning due to my Pixel 3 bricked after performing an automatic OTA security update last night.

ky...@gmail.com <ky...@gmail.com> #95Aug 11, 2021 01:31PM

Google had the nerve ask me to send phone in for repair due to their negligence. THIS IS AN ISSUE, GOOGLE YOU ARE F***KING US!

da...@gmail.com <da...@gmail.com> #96Aug 11, 2021 03:33PM

Same problem had 2 units, one Pixel3 and one XL died overnight July 11ish

la...@gmail.com <la...@gmail.com> #97Aug 11, 2021 11:38PM

Another affected user. Pixel 3XL. Android 11, latest stable. Happened around Aug 5th (don't remember the exact date, just stumbled on this as I checked bugs for Android 12, beta 4).

Same thing as others... woke up in the morning to the same corruption error. I was able to do a factory reset and bring it back to life. But it sucked since I was on vacation away from wifi. I had to drive to town to get good internet to update my phone apps, etc.

ki...@gmail.com <ki...@gmail.com> #98Aug 12, 2021 05:54AM

Another affected user here:
Pixel USB_BULK_CID402_S:D1F6DE38

happened about a month ago and moved to another phone, just to find out that it's caused by an google issue not the phone issue.
How do i get a replacement phone !!!

ec...@gmail.com <ec...@gmail.com> #99Aug 12, 2021 07:41AM

In response to

comment #97

"...woke up in the morning to the same corruption error. I was able to do a factory reset and bring it back to life..."

Then you didn't have the same issue. Factory reset is not possible with the issue described by everyone here.

to...@gmail.com <to...@gmail.com> #100Aug 12, 2021 10:56AM

It happened to me two days ago, i plugged the charger at 40% and after an hour the phone was unresponsive. It's a 3XL, never had an issue, i installed the latest update a couple of weeks ago prior to this.
I had this phone since launch and wasn't planning on upgrading it, still a solid phone for my use.

un...@gmail.com <un...@gmail.com> #101Aug 12, 2021 05:35PM

Same thing happened to me. Find my pixel has the last connection with my phone at 7 am two days ago. I just need to get my data/pics, dont care about the phone all that much to be honest. Hopefully we can extract the data somehow with it connected to a laptop

jb...@gmail.com <jb...@gmail.com> #102Aug 12, 2021 07:24PM

Pixel 3xl with the same issue, never unlocked/rooted. Support wanted me to send it in for a $400+ repair because I am out of warranty.

ch...@gmail.com <ch...@gmail.com> #103Aug 13, 2021 04:35AM

Having the same issue on the Pixel 3, but I am not on Beta. Started about a week ago. Going back and forth with support but they are insisting I send the phone in for repair at my expense. This will be my last Google device ever.

bi...@gmail.com <bi...@gmail.com> #104Aug 14, 2021 04:41AM

My Google Pixel 3 also had gone black last night while it was charging. It was in perfect condition before this. I see the same QUSB_BULK device appear when I plug it into my PC and hold down power.

GOOGLE - where are you? You destroyed over 100 phones with your update, only counting those reporting in this thread. We know this is much larger.

CLASS ACTION LAWSUIT

ti...@gmail.com <ti...@gmail.com> #105Aug 14, 2021 04:45AM

Welcome to the club!

I've tried getting mine to boot a week later with no success.

th...@gmail.com <th...@gmail.com> #106Aug 14, 2021 10:07AM

Adding my hat into the mix, phone is completely stock and on android 11. Got an OTA update and phone started acting weird. Rebooted and now phone is bricked. Support won't RMA it as it is 1 month out of warranty (how convenient) and expect me to buy a new phone.

rt...@gmail.com <rt...@gmail.com> #107Aug 14, 2021 05:18PM

About a week ago, my Pixel 4 updated, restarted, then went into boot loop. If I forced it to shut off for a few hours, it would turn back on, work normally for a few hours or days, then crash and boot loop again. It has now reached the “your device is corrupt” page and won’t turn on at all.

ze...@gmail.com <ze...@gmail.com> #108Aug 15, 2021 12:18AM

Pixel 3 XL simply died (around April this year) on my hands when I was checking the time.
Have the same behaviour as pretty much everyone here... the device shows the QUSB_BULK thing when it's connected to the PC...

It's INSANE to me how Google simply decided to not to give a f**k at all about this after all this months and all these bricked devices...

oz...@gmail.com <oz...@gmail.com> #109Aug 15, 2021 10:31PM

@#107 - That sounds like a different situation. Ours are not showing any "your device is corrupt" page - just a blank screen and aren't even accessible in adb or fastboot. If you're getting a page up when you turn it on, you should be able to rewrite your stock firmware. Check out threads on XDA on how to achieve that.

ma...@googlemail.com <ma...@googlemail.com> #110Aug 16, 2021 09:55AM

Pixel 3 died overnight around April 2021 and Device Manager only shows the phone as QUSB_BULK device.
I was on beta and I think the device at least tried to reboot, as it woke me with a bright screen. After that...nothing.

to...@gmail.com <to...@gmail.com> #111Aug 17, 2021 04:57AM

Adding another to this list. 2 weeks ago I just had my pixel 3 XL on a table doing nothing and it bricked itself. Completely stock. Would love a fix seeing as the phone is in near perfect condition.

mu...@gmail.com <mu...@gmail.com> #112Aug 17, 2021 03:53PM

Just happened to me last night. Stock Android 11, went to bed and plugged the phone in at 1am, and woke up to a brick. Black screen, no button combination yields any result, and plugged into the iMac and System Report reads it as QUSB_BULK.

What the hell Google.

or...@gmail.com <or...@gmail.com> #113Aug 18, 2021 07:28PM

I’ve starred this thread, and am here to report that my Pixel 3XL bricked itself into EDL mode back in February, right after the extended warranty I paid for expired.
Like many others have said, unless Google comes up with some sort of fix (folks in the XDA forum are talking about a ‘firehose’ please don’t ask me to explain, lol) it will be my last Google phone and probably my last Android phone.
(Comment successfully typed on my old iPhone 8!)

ka...@gmail.com <ka...@gmail.com> #114Aug 20, 2021 03:44PM

+1 to the list.

Pixel 3, Verizon, locked bootloader, stock Android 11. Always up to date. Went to bed with a pending OTA update. Woke up with my Pixel 3 in EDL mode. PC shows "QUSB_BULK_CID" in device manager.

jl...@gmail.com <jl...@gmail.com> #115Aug 21, 2021 08:56PM

I JUST had this happen today, Pixel 3, totally vanilla/stock, android 11. Went to bed with a working phone and woke up with a "dead" one, but I do get "QUSB_BULK_CID" when I plug it in to my computer.

What total BS Google.

de...@gmail.com <de...@gmail.com> #116Aug 22, 2021 04:46PM

Same happened to me overnight. Stock Pixel 3. Stuck in EDL mode.
So that's how we keep people buying new phones....
This IS A SCAM!

pe...@gmail.com <pe...@gmail.com> #117Aug 24, 2021 12:40AM

Reminder make sure you "star" the top at the top next to the issue number to indicate you are impacted by this. A comment isn't enough.

pe...@gmail.com <pe...@gmail.com> #118Aug 24, 2021 12:57PM

Same problem with my Pixel 4, no warranty, nothing! Totally dead.

ci...@gmail.com <ci...@gmail.com> #119Aug 24, 2021 01:06PM

I see 72 stars and probably many more are affected who most likely don't know about this forum. Is anyone from Google even working on this?

th...@gmail.com <th...@gmail.com> #120Aug 24, 2021 07:49PM

Comment has been deleted.

Message last modified on Aug 24, 2021 07:50PM

se...@gmail.com <se...@gmail.com> #121Aug 24, 2021 07:52PM

Woke up Monday morning to a bricked pixel 3 xl, from the Aug 21 security update. Spoke with google support and they want me to pay to have them fix it because it isn't under warranty. I get that, but your software update is bricking a bunch of phones. When we spend as much money as we do on a "flagship" phone it goes without saying that we expect the vendor to not break the device and if they are responsible for breaking the device they should pay for repairs.

eh...@gmail.com <eh...@gmail.com> #122Aug 25, 2021 01:22PM

add my phone to the list also... i just spoke with Google support and they assured me it could be fixed if i opt out of android 12 and it would send an OTA update

be...@gmail.com <be...@gmail.com> #123Aug 25, 2021 01:29PM

Reply to 122

Thats pure bs.

I never even opted in for Android 12. How can they fix over OTA when the phone doesn't connect to wifi/mobile network and is not recognized properly by a computer? Magic?

Cna someone from Google tell us if they are at least investigating this fkr a fix or confirm that they are telling us to fuck off? These are the only two outcome. And one of them for sure means I'm never touch9a Google phone again, and may look into de-googling my life.

se...@gmail.com <se...@gmail.com> #124Aug 25, 2021 01:34PM

MAKE SURE THE STAR IS FILLED IN WITH COLOR SO GOOGLE KNOWS YOU STILL HAVE THIS ISSUE.

Has anyone on this thread been supplied a fix or replacement for the damage google did with the updates? Just curious because I see there is a back log of issues from others that appears to have not been addressed for months.

ci...@gmail.com <ci...@gmail.com> #125Aug 25, 2021 01:40PM

I don't think Google is even checking this. Is there any other way to get their attention? Maybe a newspaper report or so?

co...@gmail.com <co...@gmail.com> #126Aug 25, 2021 01:43PM

I submitted a tip to Engadget and was also going to send an email to Paul Thurrott, who tends to be interested in these types of things. Anyone else who wants to try to get publicity somewhere is more than welcome. A tip to Engadget from another source might also call more attention to it.

da...@gmail.com <da...@gmail.com> #127Aug 25, 2021 01:49PM

Add me to the list. My Pixel 3 XL bricked sometime on the afternoon of 8/18. Totally unresponsive, but the find my device service pulled a location later that night around 7:30PM when I was messing around with long presses. Was working great before this.
I impulsively ordered a 5a before discovering that this is a widespread issue. I'm starting to regret that decision...

ri...@davey.com <ri...@davey.com> #128Aug 25, 2021 01:52PM

If anyone works with Google at the Enterprise level (Google Workspace), reach out to your Google rep. Getting any Google eyes on this will help. Blast Google on Twitter.

re...@gmail.com <re...@gmail.com> #129Aug 25, 2021 09:23PM

Add me to the list as well, my Pixel 3XL bricked yesterday in my hand. No warning, screen just turned off and it wouldn't start again.

oz...@gmail.com <oz...@gmail.com> #130Aug 25, 2021 10:25PM

For what it's worth, I'm pursuing mine according to Australian Consumer Law which provides guarantees on expected product lifetime, as well as service quality (automated updates are a service). Right now it's with the store that sold it to me, who are getting an assessment of the fault from Google's repairer at no cost to me (mad props to JB HiFi for doing that, will definitely go back there). Depending on how it comes back, I'll see what my options are.

ci...@gmail.com <ci...@gmail.com> #131Aug 26, 2021 01:34AM

Reply to #130

Please keep us posted on the result.

mi...@toogood.net <mi...@toogood.net> #132Aug 26, 2021 02:23AM

Pixel 3 XL same issue. Bricked 2 days ago. One minute working and the next it's dead. Shows up as QUSB_BULK_CID so it would appear to be the same issue as everyone else is experiencing. Will be contacting google support.

Message last modified on Aug 26, 2021 02:24AM

wi...@gmail.com <wi...@gmail.com> #133Aug 26, 2021 08:59AM

I turned off my Pixel 3 XL then put it on charge overnight, but it was non-responsive in the morning and wouldn't turn on.
There are no issues with the cable or any debris in the charging port, no luck with wireless charging either (stand shows battery is charged but phone doesn't respond).
My computer lists the phone as 'QUSB_CID...etc' when plugged in via USB but there doesn't seem to be any way to interact with it.
Holding down the power and volume down button triggers the sound when a device in connected/disconnected but no life on the phone.

Small hope that I'll get anywhere with my telco since the phone is few months out of warranty.

na...@gmail.com <na...@gmail.com> #134Aug 26, 2021 01:33PM

Hey all

Been emailing back & forth with google support, their support has been less than fine. The only solution I was given was this link

https://flash.android.com/welcome . Important to note I wasn't given any instructions with the link, the email was just the link.

I'll allow the users here to realise why this wont work.

Has anyone here had any luck with communicating with the google support team?

ja...@gmail.com <ja...@gmail.com> #135Aug 26, 2021 02:23PM

Yes. After emailing and complaining a lot. My phone was 5 months out of warranty (2 year and 5 months old) and they finally made an exception for me. I had to RMA my phone and got a refurbished one in return.

th...@gmail.com <th...@gmail.com> #136Aug 28, 2021 12:46PM

Adding that my wife's phone has also just suffered from this. Pixel 3XL from Oct 2018, plugged in last night, last status was 100% battery at around 4am. Unresponsive at 6am. Plugged into PC and showing QUSB_BULK_CID:0402...

be...@gmail.com <be...@gmail.com> #137Aug 28, 2021 01:00PM

Escalation thru my provider who sold me the phone (up to the Office Of The President) didnt work, Google Support escalation to management/legal isnt answering back. So I filed a "Formal Noticed" with tracked mail (sorry dont know the english terms) for breach of the "Legal Warranty" protection we have in Quebec. Once received, my provider has 10 days to reply to my satisfaction, if not I can then sue in small claim court.

Good luck everyone.

he...@utexas.edu <he...@utexas.edu> #138Aug 28, 2021 04:52PM

Adding another version of the same story here: Went to bed with a phone, woke up with a brick. No previous issues or damage on my end. The only sign of life is my phone shows up as QUSB_BULK_CID: (not Pixel 3 like it used to) when I plug it into my computer. Google help chat completely unhelpful, uBreakiFix says only options are to try screen repair ($275ish and seems unlikely to fix it to me) or motherboard, in which case the phone's totaled.

sp...@gmail.com <sp...@gmail.com> #139Aug 30, 2021 12:37AM

Same problem here. Exactly as described in every post before. Went to bed - woke up to a brick. Unbelievable that Google does not offer any kind of help. Will switch to Samsung. Super disappointed. Maybe you guys should stick to software.

ze...@gmail.com <ze...@gmail.com> #140Aug 30, 2021 02:24AM

Add mine to the list as well. Pixel 3, bought unlocked straight from the Google store, no modifications done to bootloader, not rooted, etc.

Mine died randomly in the afternoon while in my pocket. I pulled it out to look something up and it never came up or turned on again. I tried to charge it through various chargers with no change. When I attempted to charge from my computer, it showed up as the aforementioned QUSB_BULK_CID. Research has shown this to mean it's locked in EDL mode, and that we need a "firehose" file to fix it. UbreakIfix wants to replace the screen, even knowing this is not the issue, so no help there.

Not sure what to do next, but I guess I'll try Google support, though my phone is considerably past warranty. I'm hoping I get someone smarter that can see this is Google's doing and help me out. I won't hold my breath though, given the other reports.

pe...@gmail.com <pe...@gmail.com> #141Aug 30, 2021 12:18PM

By the way, I also had this problem with my Pixel 4. Totally out of options, Google says I'm out of warranty so there is NOTHING they can do.
Phone was running latest Android 12 Beta and was charging.

he...@gmail.com <he...@gmail.com> #142Aug 31, 2021 02:28AM

Mine just died overnight. Was charged. The screen doesn't turn on and the only indication it works is when it connects to the computer and shows up as QUSB_BULK_CID.
In the process of getting Google to do something about it via Australian Consumer Law like #130 but bought it direct from the Google Store, so no support from JB HiFi...

mi...@gmail.com <mi...@gmail.com> #143Aug 31, 2021 11:54PM

Same thing happened toast Monday, my pixel 3xl has had battery fast draining and issues with USB. So I thought it had other issues but then saw this issue being reported and realized it is the same thing. My phone is just shy of 3 years and battery issue started outside warranty period.

ch...@gmail.com <ch...@gmail.com> #144Aug 31, 2021 11:57PM

This happened to my Wife's pixel 3. On the charger overnight, and in the morning it was stone dead. Shows up in device manager with the EDL bulk device name.

pr...@gmail.com <pr...@gmail.com> #145Sep 1, 2021 02:01AM

Throwing in another 'this happened to me'. About 3-4 weeks ago, went to bed and everything was fine; woke up and the screen has been black ever since. Absolutely ridiculous that this is such a widespread issue, and Google isn't owning it.

pw...@gmail.com <pw...@gmail.com> #146Sep 1, 2021 02:31AM

Same thing here. I bought a new phone because of this. So sad Google isn't addressing this. I wasn't holding out for the pixel 6 and bought a one plus 9 pro, and I hate it.

pi...@gmail.com <pi...@gmail.com> #147Sep 1, 2021 04:27AM

My Pixel 3 was bricked. Bought another Pixel 3 before I saw this. Not bricked yet but I don't dare update it.

tf...@gmail.com <tf...@gmail.com> #148Sep 1, 2021 05:01AM

Same for me and unfortunately had to buy a new phone...

em...@gmail.com <em...@gmail.com> #149Sep 1, 2021 05:13AM

This issue happened to me too. I heard a text notification and when I went to look at the phone it was bricked. Tried everything above and nothing. Ordered a oneplus 9 but very disappointed with the camera compared to the 3xl.

jo...@gmail.com <jo...@gmail.com> #150Sep 1, 2021 05:27AM

Adding my Pixel 3 to the list, exact same thing as everyone else. Happened overnight, wasn't even charging. Now just blank screens and EDL nonsense. Good to know that my Pixel 1 XL still works like a champ since Google is killing all the Pixel 3's.

ci...@gmail.com <ci...@gmail.com> #151Sep 1, 2021 05:35AM

Don't forget to click the star on top...7 more to reach a 100. That's 100 Google pixel users with expensive paper weights that Google is ignoring. I guess if they do admit that there is an issue and start fixing the phones free of charge, 100s more people are going to come forward. The majority probably don't even know about this forum. They probably just bought another phone and dumped the bricked phone somewhere.

ja...@gmail.com <ja...@gmail.com> #152Sep 1, 2021 05:37AM

Do we need to move this bug to the non beta related issue tracker?

ci...@gmail.com <ci...@gmail.com> #153Sep 1, 2021 05:40AM

The issue is also happening to people who were on stock non rooted as well. So yes it is better to move it to non beta related issue as I don't think it is related to any beta software.

ja...@gmail.com <ja...@gmail.com> #154Sep 1, 2021 05:47AM

https://www.androidpolice.com/2021/08/31/pixel-3-and-3-xl-phones-are-getting-stuck-in-edl-mode-and-seemingly-bricked/?amp

pa...@gmail.com <pa...@gmail.com> #155Sep 1, 2021 06:40AM

Comment has been deleted.

Message last modified on Sep 19, 2021 03:22PM

tr...@gmail.com <tr...@gmail.com> #156Sep 1, 2021 08:02AM

Pixel 3xl also fully bricked. Stuck in EDL with blank screen. Shows as QUSB_BULK_CID when plugged into PC.

ma...@gmail.com <ma...@gmail.com> #157Sep 1, 2021 08:40AM

Same issue here, went to bed on Mon 23 Aug and my Pixel 3xl was working fine. Woke up on Tues 24 August and my phone was dead, assumed the battery had run out overnight and so tried charging. Tried various chargers, leads etc and no sign from the phone that it was charging at all. Went through google pixel support and tried all the options they suggested ie trying to load in recovery mode etc. I was told that the phone would need to be repaired or replaced at my expense.
No mention in this support call about whether the phone was recognised when plugged into a PC/Laptop. However I later noticed that when plugged into my laptop I get the "QUSB_BULK_CID" message. I later stummbled across the articles mentioned above about this issue. My phone has never been rooted, has always been kept in a case and has no damage or been dropped etc. Very frustrating that I have looked after the phone and it decides to die less than a year outside of warranty. I have a lot of data on that phone that I would like to recover.

nu...@gmail.com <nu...@gmail.com> #158Sep 1, 2021 08:49AM

Pixel 3XL. Exact same issue. Never rooted. Phone 6 months out of warranty. Google support couldn't assist and directed me to a repairer. Mentioned this issue thread but was advised as there is no resolution on the issue they can't do anything. Not happy.

ma...@gmail.com <ma...@gmail.com> #159Sep 1, 2021 11:27AM

Good morning, I got this issue a few weeks ago (went ahead and bought a new Pixel 3). Thought my phone was dead, saw an article Android Police yesterday and checked this morning. Behold, phone is not dead I am getting the same QUSB_BULK_CID message when I plug the old Pixel 3 into my laptop. It does not respond to buttons and the screen stays black. Google, please help or provide a fix.

ch...@gmail.com <ch...@gmail.com> #160Sep 1, 2021 12:58PM

Glad i found this comment and can confirm this happened to me on April 2nd, 2021. I posted in the pixel community and on reddit, but back then there was not much info circulating. Happy to see im not the only one and hopefully google will stand by there product and provide a fix.
They also told me I was out of luck, just out of warranty period.....

https://support.google.com/pixelphone/thread/104787061/pixel-3-unresponsive-overnight?hl=en

sr...@gmail.com <sr...@gmail.com> #161Sep 1, 2021 01:09PM

Here to add my Pixel 3XL. Mine bricked itself a few weeks ago, it was working perfectly then out of nowhere could I turn it on or get any response from the screen. Talking with Google Support, none of the recovery steps have worked.

sl...@gmail.com <sl...@gmail.com> #162Sep 1, 2021 01:30PM

Same thing here. My wifes died while sitting on the counter. Was not charging at the time. Google support directed me to ubreakifix. Hopefully they have the firehose file and can reflash it.

de...@gmail.com <de...@gmail.com> #163Sep 1, 2021 01:33PM

My spouse had this exact issue as well in mid-August. Same QUSB_BULK_CID as described when plugged into a computer. This is unacceptable that Google would effectively brick people's phones, then offer nothing for the phones that are out of warranty.

em...@gmail.com <em...@gmail.com> #164Sep 1, 2021 01:38PM

Happened to me too in aug 2021.. pixel 3xl
Q

be...@gmail.com <be...@gmail.com> #165Sep 1, 2021 01:46PM

Just in case, I opened

https://issuetracker.google.com/issues/198313905 in the non-Beta issue tracker with a link to here.

ro...@gmail.com <ro...@gmail.com> #166Sep 1, 2021 02:01PM

Adding another case to this issue, Pixel 3XL, purchased April 2019, bootlooped and then bricked July 2019. Have not yet reached an EDL mode screen. Out of Warranty, and uBreakIFix was only able to offer an expensive motherboard replacement as an option

ro...@gmail.com <ro...@gmail.com> #167Sep 1, 2021 02:03PM

Sorry, in regards to #166 I meant July 2021

fo...@gmail.com <fo...@gmail.com> #168Sep 1, 2021 02:12PM

Happened to me on 8/20. Woke up at 4am to pee, didn't understand why my phone wouldn't turn on (alarm for work in 2 hours) and thought the charging cable wasn't plugged in all the way. Nope. Turned out it was the QUSB-BULK everyone is is experiencing. That was after I placed an order on iFixit for a battery repair kit. Luckily I didn't start ripping my phone apart before testing the USB device name. Now I'm going to lose money on the return of the battery kit since iFixit has terrible return policies even though the shipping box wasn't even opened.

And google is denying the issue exists. Making us pay for fixes. I just bought another Pixel 3 XL on

woot.com during the recent sale and I'm pretty paranoid this phone will also have the issue...

aa...@gmail.com <aa...@gmail.com> #169Sep 1, 2021 02:17PM

Happened to me as well back in July. Forced upgrade to Pixel 5 😕

kh...@gmail.com <kh...@gmail.com> #170Sep 1, 2021 02:37PM

Same problem.

9a...@gmail.com <9a...@gmail.com> #171Sep 1, 2021 02:48PM

Add another to the list. Phone stuck in EDL mode due to bad OTA update.

na...@gmail.com <na...@gmail.com> #172Sep 1, 2021 02:48PM

My Pixel 3 XL isn't affected yet, watching this now. I disabled auto software updates a while back, so that could be related to what this issue is.

My info: Stock Android 11, unlocked bootloader, June 5th 2021 Android security update, August 1, 2021 Google Play system update.

Kernel: 4.9.248-ga11f008926d6-ab7264851 #0 Wed Apr 7 09:32:21 UTC 2021

Build: RQ3A.210605.005

Hopefully this info helps isolate the issue/patch that is causing this.

9a...@gmail.com <9a...@gmail.com> #173Sep 1, 2021 02:49PM

Pixel 3XL as well.

jg...@gmail.com <jg...@gmail.com> #174Sep 1, 2021 03:17PM

Same problem a few weeks ago. I was forced to buy a new phone with no solution available.

ja...@gmail.com <ja...@gmail.com> #175Sep 1, 2021 03:18PM

Pixel 3 XL hard bricked overnight on August 27th. No results from troubleshooting.

th...@gmail.com <th...@gmail.com> #176Sep 1, 2021 03:27PM

Pixel3 XL only boots to EDL mode after sitting overnight on my charger. Please release the firmware so we can fix our still usable hardware.

ze...@gmail.com <ze...@gmail.com> #177Sep 1, 2021 03:27PM

Pixel 3 XL hard bricked overnight on August 27th also - fully stock and without warning.

na...@gmail.com <na...@gmail.com> #178Sep 1, 2021 03:30PM

As much as Google have made it clear they don't want to, they should release the firehose & any other relevant resources for users to repair this themselves. It is the easiest solution but I don't hold out much hope for us getting a win.

ch...@gmail.com <ch...@gmail.com> #179Sep 1, 2021 03:32PM

time to take this out of this bug tracker thread that google clearly isn't watching. if you use twitter, please tweet @madebygoogle to bring some attention to this situation.

ci...@gmail.com <ci...@gmail.com> #180Sep 1, 2021 03:34PM

Not a very technical person but since this QUSB thingy is connected to Qualcomm as is mentioned by people here, has anyone contacted the company Qualcomm for a fix? Sorry if that was a dumb suggestion. Just trying my luck since my phone has been dead since December 2020 in this EDL mode and I'm out of ideas.

sy...@gmail.com <sy...@gmail.com> #181Sep 1, 2021 03:43PM

Pixel 3XL bricked 4 months ago with the same symptoms as other users reported - didn't know this issue tracker existed until now.

aa...@gmail.com <aa...@gmail.com> #182Sep 1, 2021 03:45PM

I experienced this back in December, but was told by Google support it was likely the screen. No screen, but the same thing mentioned by others in ADB when connected. About a year before that I had the same issue on my 1XL. Would really love to resolve this and at least have devices usable again.

sa...@gmail.com <sa...@gmail.com> #183Sep 1, 2021 04:04PM

My beloved 3XL has had the same problem as well it appeared that it was applying some type of update right around the beginning of July 1st week or something like that and then I noticed that it kept rebooting. I've never had any issues with this phone and have baby did and always put it in a case and I prided myself on telling everyone I hadn't upgraded in the past few years because I love my phone. but BS like this is really frustrating when there's nothing but crickets from Google ongoing issues with my first pixel device, and then my pixel tablet died on me. people wonder why others switch to Apple and repeated engineering and support issues like this are probably the reason why. I was getting ready to put money down for a new pixel 6 even if it was overpriced, but I have serious reservations if I want to stay a super fan of pixel and just move over to Apple at this point. I can understand if this is the first time it's ever happened but being an informed owner I know all too well the other hardware and software issues Google has Pat with other pixel devices in the past. Google the plate and give us a resolution so we can have our beloved phones back

sl...@gmail.com <sl...@gmail.com> #184Sep 1, 2021 04:07PM

Ubreakifix (The Authorized Google Service Center) informed me today that they do not have access to the firehose files to flash through EDL. Their only option was a motherboard replacement that will cost more than the phone. Come on google release the files so we can fix this ourselves!

kf...@gmail.com <kf...@gmail.com> #185Sep 1, 2021 04:08PM

Pixel 3 - My husband woke up to a dead phone on August 22. Took it to ubreakifix and they found a swollen battery. They tried a new battery but still nothing, so their only suggestion was a screen replacement, thinking the swollen battery had caused damage. I wasn't going to pay that much, so brought home the phone minus a battery. At that point we realized my Pixel 3 (they were purchased at the same time) also has a swollen battery but is still operational. Google agreed to replace my phone, but will do nothing about my husband's. After reading about this bricking issue, I'm certain that's his problem. The swollen batteries were just dangerous, unrelated problems.

ro...@gmail.com <ro...@gmail.com> #186Sep 1, 2021 04:56PM

My pixel 3XL had the same issue a month or so ago, it's sitting on my desk and I am now using my 5 year old Samsung backup. It definitely vibrates when plugged in, with no display or any other function.

cs...@gmail.com <cs...@gmail.com> #187Sep 1, 2021 07:16PM

Pixel 3 just had the same issue this afternoon. Worked fine this morning, didn't work after I took it back out of my pocket. Shows up in Device Manager as QUSB_BULK_CID, as with the rest of them.

va...@gmail.com <va...@gmail.com> #188Sep 1, 2021 07:46PM

Happened to me as well a few months ago. Phone was on the counter playing Bluetooth music when all the sudden the music stopped and screen was black. Never turned on again. I took great are of the phone and to have it just brick like that sucks. My ex had the exact same problem with her XL as well just 2 weeks ago where she left it charging before going to bed and woke up with the same issue. This is definitely an issue that needs to be addressed

j....@gmail.com <j....@gmail.com> #189Sep 1, 2021 08:57PM

Same here , bricked over night during charging. Can not restart the device. When connected to PC using USB it is detected as a strange device. all the attempts for factory reset has not recovered the phone from this mode.

to...@gmail.com <to...@gmail.com> #190Sep 1, 2021 09:22PM

It has to be the latest update (at least in my case), theres no other explanation.. I bought a second hand 3XL for cheap to replace the board on my phone and definitely would turn off autoupdates.

A few more week for the launch of the new iPhone i would consider buying over a pixel phone.

be...@gmail.com <be...@gmail.com> #191Sep 1, 2021 09:26PM

3XL. Same as other reports, couple of months ago after being charged
overnight I woke up to find it completely dead.
It would have had plenty of battery to still be functional in the morning
even if it didn't charge properly.

On Wed, 1 Sep 2021, 21:57 , <buganizer-system@google.com> wrote:

- Show quoted text -

ga...@gmail.com <ga...@gmail.com> #192Sep 1, 2021 11:18PM

I woke up to find my Pixel 3 seemingly dead a few weeks ago, but it would vibrate when placed on a wireless charger, so I guess it was just stuck with the screen off. After trying various combinations of holding the power button, power + volume for 10+ seconds, it eventually rebooted. It hasn't done it since.

ka...@gmail.com <ka...@gmail.com> #193Sep 2, 2021 12:18AM

- Show quoted text -

Same, except it was a sudden death in this February.
Confirmed the phone was in the EDL mode by checking it with lsusb. Cannot get it out of EDL.

an...@gmail.com <an...@gmail.com> #194Sep 2, 2021 02:22AM

One of my two Pixel 3XLs died like this a couple months ago. It's stuck in EDL mode. Please Google, help us get these phones out of EDL mode.

re...@gmail.com <re...@gmail.com> #195Sep 2, 2021 02:52AM

Google is aware of the issue, doesn't appear they want to fix the issue.

Pixel 3XL support..jpg

206 KB

View

Download

af...@gmail.com <af...@gmail.com> #196Sep 2, 2021 03:28AM

I just found about this. I thought my pixel 3 died when I received a phone call in the last week of April and the screen went blank. After sitting in my drawer since then, it still is not responsive but windows detects as others have pointed it out.

vi...@gmail.com <vi...@gmail.com> #197Sep 2, 2021 04:01AM

For me it was the morning of August 19th on my stock Pixel3, phone in EDL mode confirmed by USB on the computer

so...@gmail.com <so...@gmail.com> #198Sep 2, 2021 04:01AM

This issue has affected me as well. Supply the tools and I will do it myself, otherwise fix it on your dime. I will not pay for this company's fuck up

jw...@gmail.com <jw...@gmail.com> #199Sep 2, 2021 05:20AM

Just found out about this EDL issue. My 3XL died during the night about 3 weeks ago.
Thought it was battery issue, but the repair place said it was a motherboard issue and couldn't repair it.
Was going to wait for the 6Pro. But now I am thinking of moving brands after being with Google since the Nexus 1.

dp...@gmail.com <dp...@gmail.com> #200Sep 2, 2021 05:26AM

Pixel 3XL died this morning while playing music at rest. Verified QUSB_BULK_CID in device manager. The lack of response on this issue kills any interest I have in the Pixel 6.

fr...@gmail.com <fr...@gmail.com> #201Sep 2, 2021 12:37PM

Woke up to a bricked phone this morning. Tried the hold power button + volume down down for over 30 seconds, and still nothing. I ALSO get the QUSB_BULK_CID when plugging in my phone

ke...@gmail.com <ke...@gmail.com> #202Sep 2, 2021 01:00PM

Pixel 3 XL. Failed to come out of overnight charge. No response to power button, nor attempt to invoke boot menu.

ra...@gmail.com <ra...@gmail.com> #203Sep 2, 2021 01:08PM

Pixel 3 XL, about 2 months ago woke up to a black screen. Tried hard resetting, charging via cable and wirelessly. This entire time I had thought I had dropped it, ending its life until I found this. I too get the QUSB_BULK_CID when plugging in to computer. Been a Nexus/Pixel user since Blackberry, but the lack of response on this is a major turn off. In search of a fix...

pw...@gmail.com <pw...@gmail.com> #204Sep 2, 2021 01:25PM

I talked to support and they are giving the same BS about warranty and want me to take it to a random cell phone store to have it repaired. They're refusing to send me a replacement because it's out of warranty.

ga...@gmail.com <ga...@gmail.com> #205Sep 2, 2021 02:22PM

The same thing happened to my Pixel 3xl as described by other people above - used my phone all the way to past midnight on 8/9/2021, plugged it in to charge, and woke up at 6 am to a completely dead phone. Tried everything possible, but nothing worked. The worse part is my Gmail account access has the 2 way verification to my phone, and my Gmail account is my subscription to Google Fi. Couldnt use my phone to access my Gmail account; therefore, could use my Gmail account to set up my phone number to a different device. Lost every freaking thing saved on the Gmail account! And no service to help me recover the Gmail account when it's Google's phone that caused me the problem! What a nightmare Google put me through for a lousy phone!

ki...@gmail.com <ki...@gmail.com> #206Sep 2, 2021 02:52PM

Same exact issue for me overnight 2 nights ago. Yesterday I woke up to a dead phone even though it was on the charger all night. Windows detects it same as everyone else. This was crippling for me at work as I use my phone for 24 hour emergency work calls for one of my jobs.

sh...@gmail.com <sh...@gmail.com> #207Sep 2, 2021 03:50PM

My Pixel 3 died a few days after it got a little bit wet in some rain in July. It's been in worse rain. It had been working for 2-3 days after so I was puzzled why it quit then. I put it aside for a few weeks and used an old phone. Still nothing. Pulled the back off to see if there was water damage. There was none. Bought a refurb Pixel 3 to replace it.

Then an article on AndroidPolice alerted me to this issue and sure enough, my old Pixel 3 shows up as QUSB_BULK_CID on my Mac. Really disappointing that an update did this. Most things on the old phone were backed up so no real issue there other than Authenticator keys (one site is having to snailmail out a recovery key to me).

Next phone isn't going to be from Google if they can't fix this.

da...@gmail.com <da...@gmail.com> #208Sep 2, 2021 04:24PM

Pixel 3 XL died 2 days ago August 31, same QUSB_BULK_CID device in device manager. Blank screen and unresponsive.

mc...@gmail.com <mc...@gmail.com> #209Sep 2, 2021 04:31PM

This has been happening to my 3XL for 3 months now. Glad to be able to finally identify what the problem is now that I found this thread. Is there a fix?

te...@gmail.com <te...@gmail.com> #210Sep 2, 2021 04:39PM

My Pixel 3 was working fine last night when I went to bed. I put it on the charger and when I woke up the screen was off. I have tried all the troubleshooting steps listed on the Google Support site for when a device won't turn on. Nothing helped. I also contacted Pixel support and they said that I had tried everything already. They recommend me taking the device to ubreakifix. This phone had nothing wrong with it when I went to bed. Google really needs to do something about this issue. Now I need a new phone.

bl...@gmail.com <bl...@gmail.com> #211Sep 2, 2021 05:36PM

Pixel 3 XL. Started shutting off randomly. Would turn on and stay on for about 20 seconds. Then shut down. Finally it stopped turning on. Tried Recovery mode and it would just say "No Command".

Google bricked my pixel. Was probably going to be getting a Pixel 6 Pro....but now I'm thinking I'll just go to Apple.

ch...@gmail.com <ch...@gmail.com> #212Sep 2, 2021 05:55PM

again, i urge folks to pester google via twitter about this issue. this issue gets no attention from google and we're just an echo chamber of commiserating. i spent another hour on the phone with them this morning to no avail. google basically stole our phones from us and their only response is "buy a new one."

ar...@gmail.com <ar...@gmail.com> #213Sep 2, 2021 07:49PM

I've got the same issue. This is absurd that Google can remotely kill our phones at any time and force us to go buy a new one. We can't let them get away with this!

ar...@gmail.com <ar...@gmail.com> #214Sep 2, 2021 07:49PM

Has anyone started down the track of litigation?

an...@gmail.com <an...@gmail.com> #215Sep 2, 2021 08:23PM

I had the same exact issue. Phone randomly went to a black screen, won't respond to any button presses. I tried every suggestion that support gave me, and no response. My computer recognizes when I plug the phone in but I can't do anything with the phone. This is ridiculous.

nd...@gmail.com <nd...@gmail.com> #216Sep 2, 2021 09:10PM

I had this happen 4 months ago. Phone was left overnight with 80% battery and when I woke up it wouldn't do anything. Had the same info as posted above when I plugged it in. No help from Google at the time other than directing me to take it to a service center that was no where geographically close. Verizon replaced my device under their policy but now that this issue is becoming more known I'm worried about my replacement

da...@gmail.com <da...@gmail.com> #217Sep 2, 2021 09:50PM

Just adding my name to the bricked Pixel 3 list. It was fully charged. It was working perfectly well 30min before. Went to make another call and it was dead.

da...@gmail.com <da...@gmail.com> #218Sep 2, 2021 10:13PM

Just adding my own device to the list. On April, 6th 2021, I put my Pixel 3XL on my Pixel Stand to charge overnight. Woke up the next day wondering why my phone alarm hadn't gone off and discovered my Pixel was bricked. No screen response or on/off/volume button response. Just dead. Had been functioning fine prior, all current Android updates, etc. Nothing special running or sideloaded or anything like that. Pretty disappointing. It's just sitting in my 'dead gadget' drawer collecting dust now.

br...@gmail.com <br...@gmail.com> #219Sep 2, 2021 10:19PM

Adding on to this as well, happened to my wife Pixel 3 last night/morning or 9/2, need fix ASAP.

jo...@gmail.com <jo...@gmail.com> #220Sep 2, 2021 11:45PM

Same issue! Pixel 3 just bricked for no apparent reason. See qualcomm chip when plugging in to PC. Contacted Google support who told me nothing they can do, past warranty. Called their suggested approved repair shop who told me they were seeing a lot of this and Google knows about it. Very disappointed. My Pixel 1 suffered a similar fate....seems to be a pattern. I Bought a Samsung now but sure hope Google will do the right thing here and recompense us!

oz...@gmail.com <oz...@gmail.com> #221Sep 3, 2021 12:25AM

Thinking out loud, I wonder if it's a wear levelling issue with the flash, similar to the one Tesla had that led to massive recalls.

lc...@gmail.com <lc...@gmail.com> #222Sep 3, 2021 12:47AM

Pixel 3 XL completely bricked. Buttons unresponsive and screen blacked out. Can't get into bootloader with power and volume down. This occurred in the middle of the night 2 days after taking the latest security update OTA. Phone stuck in EDL mode. Have to use an old Samsung Note 5, unacceptable for a company to kill a product with an OTA and not replace or fix, warranty or not.

mi...@gmail.com <mi...@gmail.com> #223Sep 3, 2021 02:50AM

We had a pixel 3 fail this way (worked at night, was charging, morning it was dead, but PC can detect it). Happened in May 2021. Worried for my other pixel 3 and pixel 3XL. and really sad for my daughter who saved for a year to buy the phone that failed and wasn't replaced because it was just a few months out of warranty. Google, please do the right thing...

er...@gmail.com <er...@gmail.com> #224Sep 3, 2021 02:54AM

I've got the same issue. I've got a nonworking Pixel 3 XL phone now and because I'm out of warranty there is no way to fix it.

mo...@gmail.com <mo...@gmail.com> #225Sep 3, 2021 03:10AM

My wife phone had the same thing happen mid-Aug where she had it charged to nearly 100% got up was using it a little bit then put it down and when she picked it up 5 minutes later it was blank screen can't turn on QUSB_Bulkie_CID:xxxxxx_SNxxxxxx when we plug it into a computer. 1 min. plus of trying to load into boot loader is a no go. let it drain over 5 days then try to recharger was a no go.

of...@gmail.com <of...@gmail.com> #226Sep 3, 2021 04:07AM

Adding my name to the list. Happened to me in June, I thought I was the only one. Same story as most people here - plugged in my phone to charge before bed and woke up to a brick. We should build a bricked Pixel 3 shed. I'm sure that'd get attention.

gl...@gmail.com <gl...@gmail.com> #227Sep 3, 2021 04:42AM

Add mi píxel3 to de list is brick and y have the same problem

ma...@gmail.com <ma...@gmail.com> #228Sep 3, 2021 06:24AM

My Pixel 3 XL has died two days ago too. After reading around I connected it to my PC and it does come up in device manager as qusb_bulk_cidxxx. So this appears to be part of the corrupted upgrade?

I sure hope Google are willing to fix this, it's not great looking after an expensive device for two years only to have Google break it remotely for you.

be...@gmail.com <be...@gmail.com> #229Sep 3, 2021 11:19AM

Exact same issue with my 3XL a couple weeks ago.

pr...@gmail.com <pr...@gmail.com> #230Sep 3, 2021 01:28PM

I rarely use Twitter, but just fired up my account to tweet @Google and @MadeByGoogle with a hashtag of #Brixel3. I encourage everyone else to do the same - maybe get some attention to this issue.

jk...@gmail.com <jk...@gmail.com> #231Sep 3, 2021 01:52PM

On a duplicate bug of this (

https://issuetracker.google.com/issues/198313905#comment3), they recommend posting on the Pixel Community instead of here. Maybe we should all post there about the issue. Not sure if a massive thread is better, or a bunch of individual comments, but maybe a mix of both?

pi...@gmail.com <pi...@gmail.com> #232Sep 3, 2021 02:31PM

It seems that Google is doing everything they can to avoid addressing this issue. There is already this post on the Pixel Community where they are telling people to take the phone to an "authorized repair center" - which will tell you sorry, we have to replace the motherboard for $400.

https://support.google.com/pixelphone/thread/113517096/pixel-3-xl-bricked-overnight-computer-recognizes-as-qusb-bulk-cid-likely-caused-by-security-update?hl=en

ma...@gmail.com <ma...@gmail.com> #233Sep 3, 2021 03:00PM

Same thing happened to me. Put it down while I ate lunch, picked it up and it wouldn't come on. Very frustrating

na...@gmail.com <na...@gmail.com> #234Sep 3, 2021 03:04PM

I think we have a pretty good idea of what will prevent this issue now (blocking the update(s) in question?), but not yet how to reverse it without a firehose file being provided by Google. Just so we can get a better idea of what update is causing this, if you have a Pixel 3/3 XL that's unaffected, share the system information here.

ci...@gmail.com <ci...@gmail.com> #235Sep 3, 2021 03:23PM

Mine got bricked on December 14, 2020 and I believe I did the December security update around a week prior to that. To be honest I don't know if the issue is related to a security update. I think it's more of a hardware issue.

dj...@gmail.com <dj...@gmail.com> #236Sep 3, 2021 03:47PM

This just happened to me as well. Stuck in EDL mode

jc...@gmail.com <jc...@gmail.com> #237Sep 3, 2021 04:27PM

This happened to me also, P3XL with Beta 12 about 3 weeks ago. Plugged in the charger, went to bed and the next morning it was bricked. Sucks, no symptoms of any issue to that point.

em...@gmail.com <em...@gmail.com> #238Sep 3, 2021 05:31PM

How is this priority 3 and severity 3? Please bump this up..you have a whole bunch of phones that are dead

rm...@gmail.com <rm...@gmail.com> #239Sep 3, 2021 06:00PM

I had this issue happen to my Pixel 3XL charing overnight on 8/2, I figured the battery died but the description of this issue sounds exactly what happened to my phone. After being an advocate for Pixel devices for years, I'm about done with Google devices after this and after my Nexus 6p met a very similar fate 4 years ago.

he...@gmail.com <he...@gmail.com> #240Sep 3, 2021 06:04PM

Just happened to my pixel 3 as well, middle of the day, just sitting on the counter. Picked it up and everything is black, plugged it in to PC and got QUSB_BULK_CID:..... Never rooted or anything, on Google Fi.

ri...@gmail.com <ri...@gmail.com> #241Sep 3, 2021 06:10PM

Same here, Pixel 3XL working fine when I put it on the charger - dead when I tried to use it next morning.

ro...@gmail.com <ro...@gmail.com> #242Sep 3, 2021 06:11PM

same with my two year old pixel3 which died a few month ago in the same manner: bricked after overnight OTA update. Went to uBreakifix and they asked for $400 for motherboard replacement :-(

I had to purchase a new pixel 5. Now I'm concerned if pixel 5 will die in time too :-(

I may have to switch over to iphone when pixel 5 dies.

ka...@gmail.com <ka...@gmail.com> #243Sep 3, 2021 06:20PM

Okay, it looks like Nobody from Google has even come on here since July 20th. I guess that they have no idea how to fix their own technology. Or they despise their own customers.

en...@gmail.com <en...@gmail.com> #244Sep 3, 2021 06:25PM

Same issue here. My died around the middle of May. Tried all suggestions to get it working again, but no luck.

ba...@gmail.com <ba...@gmail.com> #245Sep 3, 2021 06:27PM

Same thing happened to my Pixel 3XL about a month ago... I plugged it in overnight (like I always did), woke up in the morning to a completely dead phone. I ended up getting a Pixel 5, but am now worried that it might suffer the same fate eventually. If that happens, I'm moving on... too bad, though, I really like the Pixel line.

pr...@gmail.com <pr...@gmail.com> #246Sep 3, 2021 06:47PM

Same, Pixel 3 bricked. Sent it for RMA - they can't repair it

ra...@gmail.com <ra...@gmail.com> #247Sep 3, 2021 07:48PM

My Pixel 3 bricked 2 weeks ago out of nothing! Was running Android 12 Beta. The screen does not turn on anymore.

Happened after putting the phone on a wireless charger with still half of the battery charged. Half an hour later, when I checked it out, I saw it was dead.

I'm from Brazil and out of warranty.

Google´s technical support couldn't do anything.

So sad, really liked the phone!

ca...@gmail.com <ca...@gmail.com> #248Sep 3, 2021 08:54PM

Same thing happened to my Pixel 3 XL on stock android 11 that I bought in late 2018.

ne...@gmail.com <ne...@gmail.com> #249Sep 3, 2021 09:52PM

Last month my pixel 3 died while i was swiping my login, it never came back on, unrooted, always updated phone, when i plug in the charger, i can feel heat generated from charging and setting it on a wireless charger turns on the led, i get the usb qid, but cant get any farther.

This seems like more than a little problem at this point

ch...@gmail.com <ch...@gmail.com> #250Sep 3, 2021 10:30PM

For those who are impacted by this, be aware that your locale may offer consumer protection laws that Google's warranty can't override. For instance, I think you'd be very likely to win a case against Google in New Zealand using the Consumer Guarantees Act, though I am not a lawyer.

ma...@gmail.com <ma...@gmail.com> #251Sep 3, 2021 10:31PM

Pixel 3 XL died around the end of April beginning of March 2021. Woke up after leaving it plugged in all night and it would only show a black screen. I can see it in Device Manager as QUSB_BULK_CID:[serial number]. Replaced it with a Pixel 5 because it was out of warranty and I figured it was dead.

* What device are you using? (for example, Pixel 4 XL)
Pixel 3 XL

* What are the steps to reproduce the problem? (Please provide the minimal reproducible test case.)
Phone was on a wired charger overnight while sleeping.

* Issue Category e.g. Framework (platform), NDK (platform), Hardware (CPU, GPU, Sensor, Camera), ART (platform), Runtime Permissions etc
Hardware

bi...@gmail.com <bi...@gmail.com> #252Sep 3, 2021 10:39PM

Adding my name to the list, but I was likely one of the first, as my Pixel
3 XL, died all the way back in September 2020.

I charged my stock unrooted P3XL on my Pixel Stand to 100%, then installed
the official Android 11 OTA update. After the update, I updated my apps,
read some news and went to bed with my phone on my bedside table with ~85%
battery remaining. Woke up the next day with a dead phone and couldn't turn
on, couldn't get to bootloader, etc. But it would still charge on my Pixel
Stand, and I could still plug it into my computers USB.

I tried Google customer support which made me drive >60 miles to the
closest uBreakIfix, which even though I had an appointment they couldn't
work on the same day. Next day they called back and said the battery was
fine, but it needed a new motherboard for $400. I declined the service and
had them ship it back to me, as I wasn't about to drive another 60+ miles.
I had to pay return shipping of $15.

I tried complaining on Twitter, but @Google and @MadeByGoogle couldn't care
less. So I made an appointment at the Apple Store to switch to iPhone after
using Android since the launch of the G1 and every generation of Nexus and
Pixel since. I just couldn't stand iOS though so I returned it and I
switched back to OG Pixel (I was using my Pixel 2 XL as a work phone),
while waiting for Pixel 5 pre-orders.

I've been through the same thing with Nexus Player, where a software update
hard bricked every single Nexus Player ever sold, and they did nothing.
Google just doesn't care about their customers or stand by their hardware.

I've starred the issue and added my story, but no amount of complaining
#metoo or #brixel3 will get Google to take any action. Even if there was a
class action lawsuit, like for the Nexus 6P, you will have to wait years to
get paid pennies for your nearly $1000 paperweight that Google bricked
overnight with a software update, not through any action of your own.

On Fri, Sep 3, 2021, 2:53 PM <buganizer-system@google.com> wrote:

- Show quoted text -

je...@gmail.com <je...@gmail.com> #253Sep 3, 2021 10:48PM

Same issue has happened to last Sunday, left phone charging overnight and woke up to a brick. I see it in device manager as QUSB, sucks as my only photo of my daughter is on the phone

lc...@gmail.com <lc...@gmail.com> #254Sep 3, 2021 11:03PM

I have been fighting with Google support for 6 hours today so far. They are really basically telling their customers to go screw themselves. The moral of the story is don't buy Google devices.

lc...@gmail.com <lc...@gmail.com> #255Sep 3, 2021 11:04PM

The device was fine until your OTA ruined like the hundreds of other Pixel 3's.

See your own threads:

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

https://support.google.com/pixelphone/thread/113517096/pixel-3-xl-bricked-overnight-computer-recognizes-as-qusb-bulk-cid-likely-caused-by-security-update?hl=en

Hundreds of your customers are being screwed by this. I will continue to spread the word so people don't buy your Pixel devices.

Others out of warranty have been given refurbished phones as this is the right thing to do since you're responsible for breaking these devices with no due fault of the end users.

Here is so more reference to what is happening to me and hundreds of others.

https://9to5google.com/2021/09/01/some-pixel-3-devices-are-getting-bricked-by-an-edl-mode-issue/

https://www.androidpolice.com/phones-devices/google-phones-devices/pixel-3/

https://www.phonearena.com/news/pixel-3-and-pixel-3-xl-models-are-bricked-when-stuck-in-edl-mode_id134710

https://www.extremetech.com/mobile/326636-something-is-bricking-pixel-3-pixel-3-xl-phones

There is more I could send you, all published within the past few days. You are leaving us all little choice but to bring legal action against Google.

oz...@gmail.com <oz...@gmail.com> #256Sep 3, 2021 11:09PM

I may have shared this with the nice reporter folks at Slashdot and Ars Technica.

https://slashdot.org/story/21/09/03/019201/pixel-3-and-3-xl-phones-are-getting-stuck-in-edl-mode-and-seemingly-bricked

https://arstechnica.com/gadgets/2021/09/reports-of-pixel-3s-bricking-with-edl-message-are-growing/

Now the story is being carried by some major tech news outlets, feel free to talk to your local news stations, newspapers, bloggers, etc. to give them "story hints", which will carry the news even further. While I'm positive there's no planned obsolescence going on, it's actually news that flagship phones are dying after just two years - especially when the Pixel 6 is about to come out.

bi...@gmail.com <bi...@gmail.com> #257Sep 3, 2021 11:12PM

Actually not a bad idea to get it on local tv news on Google's home turf
here in silicon valley. I'll share all of these links with the NBC news
consumer investigator in San Jose.

On Fri, Sep 3, 2021, 4:09 PM <buganizer-system@google.com> wrote:

- Show quoted text -

pb...@gmail.com <pb...@gmail.com> #258Sep 4, 2021 12:08AM

Maybe it is just a coincidence (doubtful) but the same thing just happened to me on a Pixel and a Pixel XL first generation: one about a month ago and the other a few weeks ago.

Interesting that this is happening weeks before the release of their new model...

ri...@gmail.com <ri...@gmail.com> #259Sep 4, 2021 01:34AM

Had the exact same issue on a Pixel 3 while driving, my phone was plugged in and fully charged while running Google Maps and Pandora. It died and won't restart, even after an extended power/volume button hold. If I plug it into a PC, I get the "QUSB_BULK_CID:" message.

ca...@gmail.com <ca...@gmail.com> #260Sep 4, 2021 02:11AM

Wow, also happened to me back in July while streaming to a hotel Chromecast. Finished the stream while the screen was black and it never came on again. The local repairer Google referred me to for out of warranty repair (ubreakifixit) only offered to replace the screen for $300 which doesn’t sound like it would’ve helped anyway. On iPhone again after about 9 years of Android doing stuff like this, though never this bad before.

bi...@gmail.com <bi...@gmail.com> #261Sep 4, 2021 02:11AM

@#258 It doesn't seem like issues affects Android 11 only. People are experiencing it with Android 12 beta as well. Also, while the majority of complaints here are from P3/XL, there are reports of other Pixels being affected as well. P1 and P4 at least. And the issue has been going on for a long time.

I am the first one affected I know of so far, which happened to me all the way back in Sept. 2020, the night that I installed the Android 11 OTA update from Android 10. I take it out of my closet every few months to see if I can revive it, but not luck. Called Google, took it to uBreakIfix, and tried getting a reaction from @MadeByGoogle. Phone was delivered Oct. 28 2018, died on Sept. 8 2020. Only a 1 year warranty, they don't give a damn, so now I have a $980 brick in my hand. No point in buying a $400+tax motherboard replacement when there are other new phones with better warranties to be had for the same or less.

From lsusb:
Bus 001 Device 011: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)
Device Descriptor:
bLength 18
bDescriptorType 1
bcdUSB 2.10
bDeviceClass 0
bDeviceSubClass 0
bDeviceProtocol 0
bMaxPacketSize0 64
idVendor 0x05c6 Qualcomm, Inc.
idProduct 0x9008 Gobi Wireless Modem (QDL mode)
bcdDevice 0.00
iManufacturer 1 Qualcomm CDMA Technologies MSM
iProduct 2 QUSB_BULK_CID:0402_SN:Fxxxxxxx
iSerial 0
bNumConfigurations 1

lc...@gmail.com <lc...@gmail.com> #262Sep 4, 2021 02:22AM

Here's the response to all you posting here and after showing them all the widespread reports of this occurring via all the reporting happening within the past two days by lots of tech sites. They don't give a damn if they ruined your device. They are telling their customers to go away.

Hi Leo,

Thanks for contacting Google Support Team.

I apologize for the inconvenience. I can't comment on six months ago issue tracker links and third party sites. I have provided you with the best available options to repair the device. Since Google is the manufacturer on record for Pixel phones, when a Pixel phone is out of warranty:

We cannot support any warranty claims that require device replacements. Hardware Warranty Center
Appreciate your time and patience.

pr...@gmail.com <pr...@gmail.com> #263Sep 4, 2021 02:40AM

Received the same response, almost verbatim.

I understand your concern. I cannot comment on third party sites and the issue tracker which you shared is from June 25, 2021. Google is committed to continually making improvements to our devices in future software updates.

I wish your device was in warranty to help you with replacement options. Hardware Warranty Center

However, we have provided you with the best available options for repairing the device. You can check with your point of purchase if they can help you with better options.

lc...@gmail.com <lc...@gmail.com> #264Sep 4, 2021 02:43AM

Just keep at them. Don't relent and make noise on their social media accounts.

na...@gmail.com <na...@gmail.com> #265Sep 4, 2021 03:15AM

I also woke up to an unresponsive Google Pixel 3 phone. Doesn't turn on or vibrate to indicate any activity. This happened late August 2021. Please help Google!
Been running perfectly before that. When are they going to admit the have a software bug which is bricking these phones!!!

no...@gmail.com <no...@gmail.com> #266Sep 4, 2021 03:55AM

Pixel 3 Owner here.

My issue is different with a result of a, bricked phone.

My phone is stuck in Fast boot mode. It will not boot even after replacing the battery at the Google recommend repair store. The store attempted to factory reset my phone with no success.

I contacted Google support and after a long chat Google wants me to return to the store.

I was told it may be a hardware issue. I replied that somtimes software can cause a hardware issue

bl...@gmail.com <bl...@gmail.com> #267Sep 4, 2021 04:29AM

Outside of legal action which will take forever, I think the only thing that's possible to be heard is to get as many people as possible to troll their twitter and other social media accounts. Maybe a huge counter campaign on the announcement of the Pixel 6. I was holding out updating my 3 XL to get the 6 as it looks like it will be a great phone.

But this is just bad....My Nexus 6p had issues, but at least it turned on.

Maybe we all create Twitter accounts "Googlebrickedmypixel" and just constantly troll them with links to all of the articles out there about this issue.

ke...@gmail.com <ke...@gmail.com> #268Sep 4, 2021 05:52AM

I had almost the exact same problem with my original Pixel about 2 years ago, there was a huge thread about it on Google forum and yet nothing ever came out of it. Woke up in the morning to a dead/bricked phone. Seems like history just repeat itself. I'm scared for my Pixel 3 now...

ke...@gmail.com <ke...@gmail.com> #269Sep 4, 2021 05:57AM

https://support.google.com/pixelphone/thread/14977268/pixel-xl-gen-1-dead-after-android-10-update-not-powering-no-indication?hl=en

Link to the original Pixel 1 thread about waking up to a bricked phone.

ok...@gmail.com <ok...@gmail.com> #270Sep 4, 2021 06:42AM

Same issue here. I connected the phone to PC to confirm.

ad...@gmail.com <ad...@gmail.com> #271Sep 4, 2021 11:00AM

Hey ,I'm on pixel 3 , beta 12.3 , phone keeps freezing and screen unresponsive, while i reset it 3 times already in risking the same , I'll upload the logs , phone is unresponsive when heavy app switch , looks like overload on resources is the one to blame , but then playing something heavy on graphics sometimes work sometimes blanks the phone , will follow up

bt...@gmail.com <bt...@gmail.com> #272Sep 4, 2021 12:20PM

Same thing happened to me 2 months ago after a software update and support said there wasn't anything they could do except send it in for repair. When I was filling out the info for repair it said it would be $450!!!!!! What a joke for something they did after a software update........ They just brushed it off and wouldn't accept responsibility very frustrating.

mu...@gmail.com <mu...@gmail.com> #273Sep 4, 2021 12:42PM

Comment has been deleted.

Message last modified on Sep 4, 2021 12:43PM

am...@gmail.com <am...@gmail.com> #274Sep 4, 2021 01:00PM

Same issue here Android 11 Pixel 3 Verizon version. Bricked into EDL and only shows QUSB_BULK_CID when connected to Windows computer.

ja...@gmail.com <ja...@gmail.com> #275Sep 4, 2021 02:33PM

Same issue seemingly useless....what is the consensus as of late? We purchased a phone to use....as a phone, not a paperweight. Please advise.

gi...@gmail.com <gi...@gmail.com> #276Sep 4, 2021 02:47PM

Same issue here. Overnight my fiancé had her Pixel 3 XL charging, it shows up as the QUSB_BULK_CID but is otherwise completely bricked. It was running stock software and I don't seem to be able to get to any boot loader or light up the screen in any capacity.

ze...@gmail.com <ze...@gmail.com> #277Sep 4, 2021 03:08PM

To add to the long list above, my Pixel 3 is now also bricked as of this morning, Sep 4 2021. Definitely seems software related judging from the thread above. For a $900+ phone investment to die in 2+ yrs, is unacceptable. With two-factor auth everywhere for everything, logins for work and all else is dependent on our phones. This is too big a risk to get another Google phone. I'm a die hard Google-r, but I have no choice but to switch to possibly Samsung. Even if I fight for a replacement, we'll need to live in stress that this can happen at any time, maybe in a life or death emergency.

Terrible way to end the trust and support we had in Google.

sa...@gmail.com <sa...@gmail.com> #278Sep 4, 2021 03:19PM

Dying during charging seems like a common thread.. Did anyone's phone NOT die whilst charging?

It feels more like the flash has gone bad rather than as a result of an update, since not everyone mentions the problem occurring after an update.
If it's bad flash it usually bricks immediately after flashing new code.. as it becomes corrupt when written.. so id be interested if an update can be identified after which it never managed to boot even once.

If most (judging by the comments) died while charging at night I guess its NOT immediately after an update.. and therefore much more likely to be a hardware problem.

fr...@gmail.com <fr...@gmail.com> #279Sep 4, 2021 03:23PM

Pixel 3xl just die!! for no reason. put it on my desk come back 5 minutes later and it was dead... HELP!!

I love this phone!!

de...@gmail.com <de...@gmail.com> #280Sep 4, 2021 03:42PM

Sept 1 2012, my Pixel 3 was low in battery (about 20%) but seemed not to charge. So I restarted. The phone never came back on. Took it to local mobile expert, he diagnosis it to be the motherboard, in otherwords a complete hardware fail.

co...@gmail.com <co...@gmail.com> #281Sep 4, 2021 03:57PM

I'd like to pile on this as well. My wife's Pixel 3aXL went black after an update several weeks ago. Tried all the standard fixes, but is recognized by plugging in to a computer. Bricked and in EDL mode hell.

ta...@gmail.com <ta...@gmail.com> #282Sep 4, 2021 04:22PM

Starred and also awaiting resolution. I have a 3XL, situation is similar to what others have mentioned, so nothing to add on that front. With the age of the phone, I consider this something that needs to be formally addressed either through update or RMA. It's not acceptable and severely damages the reputation of the Pixel lineup. Not everyone subscribes to the "upgrade every year" model.

sm...@gmail.com <sm...@gmail.com> #283Sep 4, 2021 05:24PM

How is it possible that this problem is not being responded to by Google ?

Get ready for a big lawsuit !

You - Google - are %100 responsible party. It's your product, and your policy to force updates on the phone.

Your silence on this is deafening.

ni...@gmail.com <ni...@gmail.com> #284Sep 4, 2021 05:50PM

Hey Google, how about releasing firehorse files so this issue can be investigated by the community?

da...@gmail.com <da...@gmail.com> #285Sep 4, 2021 05:54PM

Same thing happened to my Pixel 3XL. Went to bed plugged in. Woke up, phone was dead. Screen and buttons were unresponsive. Tried holding various combinations to reboot, draining and charging, plugging into computer, but nothing worked. Went and bought a new phone, but would be nice to get it working again.

mg...@gmail.com <mg...@gmail.com> #286Sep 4, 2021 05:57PM

Estoy en la misma situación, mi mujer puso a cargar el teléfono durante la noche y por la mañana no encendía. Si lo conectas al ordenador lo detecta te dice el número de serie, pero no lo detecta por adb.

pa...@gmail.com <pa...@gmail.com> #287Sep 4, 2021 10:35PM

Keep me informed

From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Saturday, September 4, 2021 10:55 AM
To: b-system+-1846687054@google.com
Cc: patnchar@gmail.com
Subject: Re:

Issue 192008282

: Pixel 3 bricked while charging overnight around 7am Pacific

Replying to this email means your email address will be shared with the team that works on this product.

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

Changed

<mailto:da...@gmail.com> da...@gmail.com added

comment #285

https://issuetracker.google.com/issues/192008282#comment285> :
Same thing happened to my Pixel 3XL. Went to bed plugged in. Woke up, phone was dead. Screen and buttons were unresponsive. Tried holding various combinations to reboot, draining and charging, plugging into computer, but nothing worked. Went and bought a new phone, but would be nice to get it working again.

_______________________________

Reference Info: 192008282 Pixel 3 bricked while charging overnight around 7am Pacific

component: Android Public Tracker <

https://issuetracker.google.com/components/190602> > Android Developer Preview / Beta
status: Assigned
reporter: za...@gmail.com <mailto:za...@gmail.com>
assignee: ad...@google.com <mailto:ad...@google.com>
cc: ad...@google.com <mailto:ad...@google.com> , za...@gmail.com <mailto:za...@gmail.com>
type: Bug
priority: P3
severity: S3
blocked by: 192267656 <

https://issuetracker.google.com/issues/192267656>
found in: SPB2.210513.011
hotlist: Platform <

https://issuetracker.google.com/hotlists/461195>
retention: Component default
ReportedBy: User

Generated by Google IssueTracker notification system

You're receiving this email because you are subscribed to updates on Google IssueTracker

issue 192008282

https://issuetracker.google.com/issues/192008282> where you have the role: starred.
Unsubscribe from this issue. <

https://issuetracker.google.com/issues/192008282?unsubscribe=true>

pa...@gmail.com <pa...@gmail.com> #288Sep 4, 2021 10:36PM

Keep me informed

From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Saturday, September 4, 2021 10:25 AM
To: b-system+-1846687054@google.com
Cc: patnchar@gmail.com
Subject: Re:

Issue 192008282

: Pixel 3 bricked while charging overnight around 7am Pacific

Replying to this email means your email address will be shared with the team that works on this product.

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

Changed

<mailto:sm...@gmail.com> sm...@gmail.com added

comment #283

https://issuetracker.google.com/issues/192008282#comment283> :
How is it possible that this problem is not being responded to by Google ?

Get ready for a big lawsuit !

You - Google - are %100 responsible party. It's your product, and your policy to force updates on the phone.

Your silence on this is deafening.

_______________________________

Reference Info: 192008282 Pixel 3 bricked while charging overnight around 7am Pacific

component: Android Public Tracker <

https://issuetracker.google.com/issues/192267656>
found in: SPB2.210513.011
hotlist: Platform <

issue 192008282

https://issuetracker.google.com/issues/192008282> where you have the role: starred.
Unsubscribe from this issue. <

https://issuetracker.google.com/issues/192008282?unsubscribe=true>

pa...@gmail.com <pa...@gmail.com> #289Sep 4, 2021 10:36PM

Keep me informed.

From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Saturday, September 4, 2021 9:23 AM
To: b-system+-1846687054@google.com
Cc: patnchar@gmail.com
Subject: Re:

Issue 192008282

: Pixel 3 bricked while charging overnight around 7am Pacific

Replying to this email means your email address will be shared with the team that works on this product.

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

Changed

<mailto:ta...@gmail.com> ta...@gmail.com added

comment #282

https://issuetracker.google.com/issues/192008282#comment282> :
Starred and also awaiting resolution. I have a 3XL, situation is similar to what others have mentioned, so nothing to add on that front. With the age of the phone, I consider this something that needs to be formally addressed either through update or RMA. It's not acceptable and severely damages the reputation of the Pixel lineup. Not everyone subscribes to the "upgrade every year" model.

_______________________________

Reference Info: 192008282 Pixel 3 bricked while charging overnight around 7am Pacific

component: Android Public Tracker <

https://issuetracker.google.com/issues/192267656>
found in: SPB2.210513.011
hotlist: Platform <

issue 192008282

https://issuetracker.google.com/issues/192008282> where you have the role: starred.
Unsubscribe from this issue. <

https://issuetracker.google.com/issues/192008282?unsubscribe=true>

00...@gmail.com <00...@gmail.com> #290Sep 5, 2021 12:26AM

Same thing happened to me last night with Pixel 4XL

es...@gmail.com <es...@gmail.com> #291Sep 5, 2021 03:57AM

Same for me. On top of that had my vacation pictures that were not backed up (this happened the day we came back so no cloud backup possible).
Does anyone know if I can at least get the pictures out?

jo...@gmail.com <jo...@gmail.com> #292Sep 5, 2021 05:29AM

Pixel 3 bricked overnight while charging last night. Google support gave me a list of local repair shops and said they couldn't help.

bo...@gmail.com <bo...@gmail.com> #293Sep 5, 2021 08:15AM

Pixel 3xl bricked with this bug. No help from support yet.

ni...@gmail.com <ni...@gmail.com> #294Sep 5, 2021 10:09AM

Just some random idea... I am not affected yet, so I can't test this and don't want to test this on my productive device. There is no firehorse binary for the Pixel 3. These flasher binaries are signed for secure boot. IF there is just one signing key and the bootloader is signed with the same key, it might be possible to run the bootloader instead of firehorse through EDL. That might help to boot the phone a last time to backup your data.

So, if someone wants to try this:

Get the bootloader.img from the factory image
Use the firehorse tools from alephsecurity or the edl tool from bkerler to upload and execute the bootloader.img - you probably need to slightly modify the tools

Using the full image might not work. However, it's possible to extract xbl, abl etc. from the image using imgtool. Maybe abl can be uploaded and execute directly.

# ../../imgtool/imgtool bootloader.img 
QCom SD845 ("FBPK") image detected
Partition Table with 19 entries:
0x23b0: msadp 
0x63f0: xbl 
0x385430: xbl_config 
0x39d470: aop 
0x3cb4b0: tz 
0x5c14f0: hyp 
0x621530: abl 
...

Another possibility could be unsoldering (BGA!) the UFS flash, flashing the (probably broken) bootloader directly using UFSProg-CS and resolder it.

Note: (de)soldering BGA is highly advanced... Only do that if you know what you are doing and can risk final loss of your data!

ma...@gmail.com <ma...@gmail.com> #295Sep 5, 2021 11:02AM

The same thing happened with my phone. Pixel 3

br...@gmail.com <br...@gmail.com> #296Sep 5, 2021 09:11PM

My Pixel 3 XL bricked while in use on Tuesday. It is stuck in EDL mode. Google support said there is nothing they can do since these are all out of warranty. The local Google authorized repair shop is willing to try to fix it and only charge me if the fix works. I'll probably try it and report back.

pa...@gmail.com <pa...@gmail.com> #297Sep 5, 2021 09:36PM

Where is your repair shop?

Get Outlook for Android<

https://aka.ms/AAb9ysg>
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Sunday, September 5, 2021 2:11:17 PM
To: b-system+-1846687054@google.com <b-system+-1846687054@google.com>
Cc: patnchar@gmail.com <patnchar@gmail.com>
Subject: Re:

Issue 192008282

: Pixel 3 bricked while charging overnight around 7am Pacific

Replying to this email means your email address will be shared with the team that works on this product.

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

Changed

br...@gmail.com added

comment #296

https://issuetracker.google.com/issues/192008282#comment296>:
My Pixel 3 XL bricked while in use on Tuesday. It is stuck in EDL mode. Google support said there is nothing they can do since these are all out of warranty. The local Google authorized repair shop is willing to try to fix it and only charge me if the fix works. I'll probably try it and report back.

_______________________________

Reference Info: 192008282 Pixel 3 bricked while charging overnight around 7am Pacific
component: Android Public Tracker > Android Developer Preview / Beta<

https://issuetracker.google.com/components/190602>
status: Assigned
reporter: za...@gmail.com
assignee: ad...@google.com
cc: ad...@google.com, za...@gmail.com
type: Bug
priority: P3
severity: S3
blocked by: 192267656<

https://issuetracker.google.com/issues/192267656>
found in: SPB2.210513.011
hotlist: Platform<

issue 192008282

https://issuetracker.google.com/issues/192008282> where you have the role: starred.
Unsubscribe from this issue.<

https://issuetracker.google.com/issues/192008282?unsubscribe=true>

ma...@gmail.com <ma...@gmail.com> #298Sep 5, 2021 10:24PM

I have a Pixel 3, I hope this gets fixed fast. I have enabled my USB debugging and bug reports just in case

ma...@gmail.com <ma...@gmail.com> #299Sep 5, 2021 10:56PM

You also destroyed my phone.

YOU DID THIS.

pe...@gmail.com <pe...@gmail.com> #300Sep 5, 2021 11:05PM

My Pixel 3 also suffered this same fate a while ago.

I thought it was dead until recently when I found out about this issue. I plugged it into my computer and found that it showed up in device manager on my Windows PC as QUSB_BULK_CID.

I hope that this issue can be fixed by you as you have broken it. I don't understand how such a big company can so blatantly ignore such a mountain of evidence that shows it was something you did to break all these phones.

da...@gmail.com <da...@gmail.com> #301Sep 5, 2021 11:38PM

My Pixel 3 died on me last week. I couldn't wait to get it fixed so just went out and bought a new one. I found out a few days later it's not actually dead but just in some sort of bricked coma. It appears dead but plugging in to my PC does bring up the QUSB_BULK_CID in device manager.
Now really worried that my new Pixel 3 could randomly crap out too. Called Google support but they claimed they're not aware of an issue. It's out of warranty so looks like I'll have to pay to get it fixed for a problem that was not caused by me.

na...@gmail.com <na...@gmail.com> #302Sep 5, 2021 11:40PM

The same here. Originally purchased from Google Fi and I was thinking of getting the new Pixel foldable next year. Now I am switching to Motorola G as they are affordable in a limited time like this. Goodbye Google

da...@gmail.com <da...@gmail.com> #303Sep 6, 2021 12:11AM

This exact same thing happened to me yesterday morning. Woke up and my 2018 Pixel 3 was stuck on black screen, but still draws power and displays QUSB_BULK_CID in the device manager when plugged into a computer. Google Support wouldn't help since the phone was out of warranty, and local repair shop said they couldn't fix it. Before all of this the Pixel 3 was the most reliable phone I have ever owned; I'm disappointed in Google's response to this so far. Doesn't give a lot of confidence for buying future models from them. Hopefully they can do something to help all of us users stuck in the same boat.

mo...@gmail.com <mo...@gmail.com> #304Sep 6, 2021 01:43AM

Pixel 2 XL bricked while charging. Plugged into computer it shows QUSB_BULK. Will have to buy a new phone, and the lack of response on this topic guarantees that new phone won't be made by Google.

st...@gmail.com <st...@gmail.com> #305Sep 6, 2021 02:35AM

I have pixel 3 xl that bricked from overnight charging on pixel stand. That was about 30 days ago now, tried everything I could find online to try and get it to boot, no luck. Black screen, no charge indicator....nothing. Hopefully google comes out with fix. I still have another working pixel 3xl that I would like to keep running for a while. Would be great to get replacement repair under extended warranty as this now seems like.

th...@gmail.com <th...@gmail.com> #306Sep 6, 2021 02:59AM

I currently behave a Pixel 3 xl and mine is constantly shutting down like most people are complaining about here. Hard to get back on and shuts down in multiple's. What is Google doing to fix this ongoing issue. I understand I'm out of warranty but don't change my phone's that often due to getting updates as needed. Please advise. Be nice if we can get a credit of some sort towards a new phone if they can't fix the issue. It's annoying as we all depend on our Phones.

sh...@gmail.com <sh...@gmail.com> #307Sep 6, 2021 03:12AM

pixel 3a bricked today, support is no help. out of warranty but only 19 months old. too bad so sad. not buying another pixel phone that's for sure.

ku...@gmail.com <ku...@gmail.com> #308Sep 6, 2021 06:22AM

same thing happened to me as well. device completely bricked. I went to authorized repair center and they mentioned that i would need to get my mother board replaced (costing 500 USD) - which is insane as there is not even a scratch on the device, no water damage, nothing. It just stopped working overnight exactly like everyone else reported here. Now am stuck and will have to buy another phone in urgency.

no...@gmail.com <no...@gmail.com> #309Sep 6, 2021 06:30AM

Same thing happened to my Pixel 3 just out warranty and only 17 months old.

bk...@gmail.com <bk...@gmail.com> #310Sep 6, 2021 09:29AM

Same here. I had to buy a terrible Motorola because the Verizon store didn't have any other phones.

al...@gmail.com <al...@gmail.com> #311Sep 6, 2021 12:50PM

Same here, mine bricked a couple of months ago...

ad...@lumsdenlive.com <ad...@lumsdenlive.com> #312Sep 6, 2021 01:05PM

Adding myself to the list. Late July work up to a dead 3XL with all the same symptoms. Heres the fun part, went back to my old Pixel 1 as a backed up, it started to boot and ended up in the same state!

Thanks Google! Loyal buyer since the Galaxy Nexus, looking forward the the 6. Now just trying to decide if I'm going Samsung or full Apple.

ho...@gmail.com <ho...@gmail.com> #313Sep 6, 2021 01:11PM

Same here, Pixel 3XL bricked overnight.

br...@gmail.com <br...@gmail.com> #314Sep 6, 2021 01:41PM

Exact same issue as others, couldn't believe it. Have the old phone still, and the receipt to show when I had to buy a replacement in July.

st...@gmail.com <st...@gmail.com> #315Sep 6, 2021 01:59PM

Same issue as others, bricked black screen after night of charging. I plugged my bricked phone into pc. Under connected devices is says "Qualcomm HS-USB QDLoader 9008 (COM6)". I can't otherwise access the device in any way through the USB connection aside from seeing that description.

Totally stock unlocked pixel 3 xl purchased from Google Fi in 2018. A little worried as this was just one of the pixel 3 devices in my household. Have two other examples still working ......for now. Please fix Google. If it can't be fixed, please help those affected with a new/refurbished device.

jo...@gmail.com <jo...@gmail.com> #316Sep 6, 2021 02:36PM

I have a 3xl but not bricked, and the last update I did was for Android 10. Never updated to 11 because I read about many initial problems for upgraded 3xl's. I'm curious what's everyone's Android version and security patch when it bricked.

st...@gmail.com <st...@gmail.com> #317Sep 6, 2021 03:07PM

This happens to my pixel 3xl as well while charging over night. I woke up at 5am and my phone was black. Spent the next week trying to find the issue with Google support. They said it's no longer under warranty so they won't help me.

mg...@gmail.com <mg...@gmail.com> #318Sep 6, 2021 03:12PM

My Pixel 3XL had the save issue. Awoke one morning to a bricked phone. Took it to Google approved repair vendor, they said nothing can be done, it is dead. Clearly there's an issue with this model and Google needs to do something for those of us that experienced it.

ja...@gmail.com <ja...@gmail.com> #319Sep 6, 2021 03:32PM

Still no (helpful) response from Google to this bug report. Remember to star the issue, don't just comment.

I would also recommend google 'Android News' and emailing/messaging your favourite websites and publications, hopefully, if the media pick up this story Google will do something about all these bricked phones!

pa...@gmail.com <pa...@gmail.com> #320Sep 6, 2021 03:51PM

Apple is looking better and better, especially since no new pixel XL. Bye bye Google.

From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Monday, September 6, 2021 6:06 AM
To: b-system+-1846687054@google.com
Cc: patnchar@gmail.com
Subject: Re:

Issue 192008282

: Pixel 3 bricked while charging overnight around 7am Pacific

Replying to this email means your email address will be shared with the team that works on this product.

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

Changed

<mailto:ad...@lumsdenlive.com> ad...@lumsdenlive.com added

comment #312

https://issuetracker.google.com/issues/192008282#comment312> :
Adding myself to the list. Late July work up to a dead 3XL with all the same symptoms. Heres the fun part, went back to my old Pixel 1 as a backed up, it started to boot and ended up in the same state!

Thanks Google! Loyal buyer since the Galaxy Nexus, looking forward the the 6. Now just trying to decide if I'm going Samsung or full Apple.

_______________________________

Reference Info: 192008282 Pixel 3 bricked while charging overnight around 7am Pacific

component: Android Public Tracker <

https://issuetracker.google.com/issues/192267656>
found in: SPB2.210513.011
hotlist: Platform <

issue 192008282

https://issuetracker.google.com/issues/192008282> where you have the role: starred.
Unsubscribe from this issue. <

https://issuetracker.google.com/issues/192008282?unsubscribe=true>

pe...@indez.com <pe...@indez.com> #321Sep 6, 2021 04:09PM

I have had my Pixel 3 since April 2019. Always worked perfectly. Screen OK. Battery OK. All OK. Then it just stopped working. It will not start or charge or anything. I wasn't doing anything ... it just stopped. I started looking and found https://www.techradar.com/uk/news/google-pixel-3-and-3-xls-randomly-bricking-as-hundreds-report-dead-phones.

I am 6 months past the end of Warrantee. I checked the cost of a repair and Google quoted me £324+tax. I plan to upgrade to a Pixel 6. What should I do?

wi...@gmail.com <wi...@gmail.com> #322Sep 6, 2021 04:28PM

My Pixel 3 was bricked on Aug. 24th.

sa...@gmail.com <sa...@gmail.com> #323Sep 6, 2021 05:19PM

In reply to

comment #321

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

"What should I do"

Definitely not buy a Pixel 6.. Google cant put together a working and long lasting phone.. my Nexus 4, 5X and Pixel 3 have all died of hardware faults. I've got 15 year old phones from other manufacturers that work just fine.

ma...@gmail.com <ma...@gmail.com> #324Sep 6, 2021 05:39PM

No issue here with my Pixel 3a 🙂

sa...@gmail.com <sa...@gmail.com> #325Sep 6, 2021 06:02PM

We should definitly celebrate that google made a phone that latesd nearly 3 years!

ha...@gmail.com <ha...@gmail.com> #326Sep 6, 2021 06:50PM

And here I was thinking to get Pixel but with this NAH I'll just stick with Huawei instead

al...@gmail.com <al...@gmail.com> #327Sep 6, 2021 06:51PM

My Pixel 3 bricked on August 31st after charging all night. I had 0 issues with the phone before then. Now it will only accept a charge but I cannot do anything else with it.

to...@gmail.com <to...@gmail.com> #328Sep 6, 2021 07:20PM

Just a reminder to make sure to check the "star" the top, at the top next to the issue number. That tracks how many are affected.

an...@gmail.com <an...@gmail.com> #329Sep 6, 2021 08:49PM

Same problem with mine. Charged overnight and woke up to a bricked phone.

mc...@gmail.com <mc...@gmail.com> #330Sep 6, 2021 08:50PM

Happened on my Pixel 3 the morning of June 27, 2021
Model G013A on Verizon
I get the QUSB_BULK_CID:0402_SNxxxx in device manager and nothing else.

st...@gmail.com <st...@gmail.com> #331Sep 6, 2021 09:09PM

Just to follow up on my earlier post, my Pixel 3 xl bricked overnight August 18. No idea what OTA updates may have gone out in that time frame. Hooking dead phone to PC shows only "Qualcomm HS-USB QDLoader 9008 (COM6)".

Just trying to be detailed in the hope that someone may actually be working on this. Hopefully if people include useful info (instead of or in addition to their threats to move to another brand or OS) we could actually get a fix.

jo...@gmail.com <jo...@gmail.com> #332Sep 6, 2021 10:06PM

Exactly the same problem as everyone else - happened overnight in March 2021. Qualcomm USB error just like everyone else.

sl...@gmail.com <sl...@gmail.com> #333Sep 6, 2021 10:34PM

Still didn't happen to me, but I'm really amazed how google can just ignore such thing, I would go completely crazy if this happens, I'm pretty much too broke to have to buy a new phone

al...@gmail.com <al...@gmail.com> #334Sep 6, 2021 10:35PM

Kinda wonder if this problem is connected to leaving the phone on a charger overnight. My Pixel 3XL still works, but recently it overcharged the battery while on the Pixel Stand, and made the battery swell up, popping the back cover open slightly; I think this is also a known issue. I don't normally leave the phone on the charger overnight. *crosses fingers*

el...@gmail.com <el...@gmail.com> #335Sep 6, 2021 11:35PM

My 3XL was bricked almost exactly a year ago. Initially, was able to get the computer to recognize it, but nothing more, despite trying to access the bootloader using methods mentioned in this thread. Took it to the authorized ubreakifix store, who took it apart and said it was "probably" a motherboard issue, and they don't carry the parts. Since then, the computer doesn't even recognize it.

cs...@gmail.com <cs...@gmail.com> #336Sep 7, 2021 12:00AM

Same problem for me last week. Pixel 3. Charged overnight on wireless pixel stand. In the morning would not turn on. Black screen. Tried everything nothing works to get the screen on. Not safe mode, nothing. Completely dead. Using old lg g5 now.

na...@gmail.com <na...@gmail.com> #337Sep 7, 2021 01:19AM

It is in my phone as well

pw...@gmail.com <pw...@gmail.com> #338Sep 7, 2021 01:24AM

Update: I was able to get them to agree to an RMA. I had to threaten litigation and be a bit of a Karen to get them to escalate it. I'll remain skeptical because my phone isn't in the best of shape and I fear they'll say no once they 'inspect' it.

la...@gmail.com <la...@gmail.com> #339Sep 7, 2021 03:35AM

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!

pe...@gmail.com <pe...@gmail.com> #340Sep 7, 2021 04:07AM

Same issue here, woke up to a bricked Pixel 3 on July, 25th. Bought a Samsung galaxy S21 that day. Google may make some money selling Pixel 4 and 5's to the replace the phones they destroyed, but the reputational damage and lost customers will outweigh the short-term profits.

jo...@gmail.com <jo...@gmail.com> #341Sep 7, 2021 04:27AM

Super shitty of Google to turn their backs on their customers

[Deleted User] <[Deleted User]> #342Sep 7, 2021 07:00AM

Hey Google - can you spell CLASS ACTION LAWSUIT?

le...@gmail.com <le...@gmail.com> #343Sep 7, 2021 08:02AM

same here. pixel 3xl, bricked 2 months ago

ja...@gmail.com <ja...@gmail.com> #344Sep 7, 2021 09:00AM

Same here ... Bricked on June 25th. I placed the phone on the table with no charger connected and about 30% battery remaining. When I came back to it 10 minutes later, it was bricked. Android 11 stock.

Was really looking forward to Pixel 6, but not after realizing that this problem was so widely-spread and that Google doesn't seem to care. If Google doesn't resolve this, Pixel 3 was my last Google product.

Don't forget to star the issue!

ka...@gmail.com <ka...@gmail.com> #345Sep 7, 2021 09:51AM

Mine got bricked on june, EDL issue too. very disappointed with google... no Pixel 6 until resolve this.

ni...@gmail.com <ni...@gmail.com> #346Sep 7, 2021 10:16AM

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

Anyone interested to test this?

se...@gmail.com <se...@gmail.com> #347Sep 7, 2021 10:22AM

Hi, I have exactly same issue - my Nexus 6p phone. It worked like a charm for the last 6 years and now... I had YouTube opened and it suddenly just turned off without any message and never turned back on again. When I connect my phone to charging, there's no battery sign on screen.
Tried everything which is possible including turn on into bootloader but nothing...

pa...@rgbassurance.com.au <pa...@rgbassurance.com.au> #348Sep 7, 2021 11:00AM

Adding to the long list. Pixel 3, running Android 11 bricked today. located in Australia on Vodafone network.

ke...@gmail.com <ke...@gmail.com> #349Sep 7, 2021 11:27AM

Just found out I'm not the only one! Google should send us a new phone right?

Also, went to a repair shop and they told me the motherboard is toasted so unfixable. This was definitely and update to happened overnight.

to...@gmail.com <to...@gmail.com> #350Sep 7, 2021 12:34PM

Happen to my 3XL last summer (2020). Had it charging overnight and woke up to it being bricked. Have a second 3XL that I recently purchased new from Woot, we'll see how long that lasts.

er...@gmail.com <er...@gmail.com> #351Sep 7, 2021 03:20PM

My Pixel 3XL also died while charging.

rh...@gmail.com <rh...@gmail.com> #352Sep 7, 2021 03:45PM

Same Issue on Pixel 3XL. This is nice well maintained phone. This happened while charging, it went into bootloop and after sometime never turned on again. Took it UbreakIfix (Google's authorized service), they said motherboard has gone bad!

zz...@gmail.com <zz...@gmail.com> #353Sep 7, 2021 04:23PM

Same issue here. Phone bricked overnight with no reasons. Fortunately it was my day off otherwise I might lose my job. I'm not going to buy any Google products in the future and I will tell anyone I know to avoid them as well.

ni...@gmail.com <ni...@gmail.com> #354Sep 7, 2021 04:26PM

The same thing happened to my 3XL a couple of weeks ago. Thank God I had a backup phone I could switch over to. Driving and the phone just went black. Charges wirelessly, but will not turn on. Just black screen.

zh...@gmail.com <zh...@gmail.com> #355Sep 7, 2021 04:38PM

Also happened to my Pixel 3XL a few weeks back. Bricked overnight. Consulted with support and no resolution. Now I see the issue is so wide-spreading.

lc...@gmail.com <lc...@gmail.com> #356Sep 7, 2021 06:02PM

Day 5 of non stop emailing to Google. They are still stonewalling, but media is now reporting they confirmed the problem exists but will make no further comment. Light them up on all platforms, keep sending them emails. What they are doing is wrong.

https://www.iphoneincanada.ca/news/google-pixel-3-brick/

bl...@gmail.com <bl...@gmail.com> #357Sep 7, 2021 06:40PM

https://chimicles.com/google-pixel-3-class-action-investigation/

Law firm that won the Nexus 6p suit wants information on Pixel 3 issues.

bi...@gmail.com <bi...@gmail.com> #358Sep 7, 2021 08:15PM

I filled out their form:

On September 8 2020, I updated my Google Pixel 3 XL to Android 11 using the
official OTA update from Google. I set my phone on my bedside table with
>80% battery remaining and went to sleep. The next morning my phone was off
and could not be rebooted. I can charge the phone using wireless charging
or the supplied USB-C cable, but there is absolutely nothing that can be
done to get the screen to turn on, or to get to the phones boot loader to
factory reset the device or flash a new version of the OS. Plugging the
phone into my computer I can see that the phone is stuck in QDL/EDL mode
and is not recoverable.

Prior to this incident, the phone was in perfect working condition. It had
never been dropped, it had never been exposed to water, the screen was in
excellent condition with no chips or cracks. I called Google Customer
Support and they informed me that there was nothing they could do as the
phone was out of warranty and recommended that I take the phone to a 3rd
party repair shop >30 miles from my home. The repair shop said that both
the battery and screen were fine, but that the phone would need a new
motherboard which would cost $400 + tax. I declined repair and had them
ship the phone back to me, which cost $15 for return shipping.

The phone cost $979.91 from the Google Store and was less than 2 years old
when it randomly died by no act of my own. My Pixel 3 XL was completely
damaged, either by a hardware failure, or a software update provided by
Google. The warranty is only 1 year, so Google is completely unwilling to
help resolve the matter. As the phone cannot be powered on, it could not be
used as a trade-in to subsidize the cost of a new phone.

Although, the majority of complaints are from Google Pixel 3 and Google
Pixel 3 XL users on Android 11. As I understand, this issue began in July
2020 and has been occurring more recently on all Google Pixel mobile phones
from 2017 onward, when running Android version 11 or 12. Even with
thousands of reported cases, Google has not released a statement and so far
has been unwilling to provide support to affected users.

On Tue, Sep 7, 2021 at 11:40 AM <buganizer-system@google.com> wrote:

- Show quoted text -

zn...@gmail.com <zn...@gmail.com> #359Sep 7, 2021 08:16PM

Bricked pixel 3 out of nowhere. Not detected in Windows or Mac, holding any button combination doesn't help. So probably there is nothing I can do about that.

bi...@gmail.com <bi...@gmail.com> #360Sep 7, 2021 08:19PM

Although a class action suit is the last thing I want. It will take years
and affected users will get next to nothing out of it. I would much rather
see Google take ownership, step up and provide either 1) replacements, 2)
full trade-in value for affected units to upgrade to Pixel 5a, Pixel 6 or
Pixel 6 Pro, or 3) a refund equal to the current full trade-in value.

On Tue, Sep 7, 2021 at 1:14 PM Stewart Gateley <birbeck@gmail.com> wrote:

- Show quoted text -

mm...@gmail.com <mm...@gmail.com> #361Sep 7, 2021 08:33PM

My Pixel 3XL turned itself off out of nowhere and would not come back on. This was on August 29th, 2021 in the late afternoon to early evening. Since the warranty was no longer good through Verizon, I was forced to get a new phone when I wasn't ready to upgrade yet. I think that regardless of the warranty, Google should stand by its product and provide those customers affected with a new Pixel 6 when it comes out.

mi...@gmail.com <mi...@gmail.com> #362Sep 7, 2021 08:50PM

Add Me to the list my Pixel 3 just died blackscreen I cannot revive it no matter what I try I called Google and they told me that it is out of warranty and they can't do nothing. I have three other pixel 3 is in my family I hope they don't die as well

ch...@gmail.com <ch...@gmail.com> #363Sep 7, 2021 08:58PM

My Pixel 3XL died last Thursday similar to everyone else. Put it on to charge overnight, woke up in the morning (late to work because no alarm) and was unable to get it to turn on or respond to anything. Completely bricked 4 months short of 3 years of having it and no history of issues.

ri...@gmail.com <ri...@gmail.com> #364Sep 7, 2021 09:14PM

My pixel 3 bricked a week and a half ago. Woke up to a black screen and the phone is detected as qusb_bulk_cid:*****

jo...@gmail.com <jo...@gmail.com> #365Sep 7, 2021 09:36PM

I had 4 Pixels purchased at release for the family, one had this brick.

qu...@gmail.com <qu...@gmail.com> #366Sep 7, 2021 09:48PM

Mine isn't bricked quite yet but 2 weeks ago phone keeps doing with 80% battery life. The battery istelf seems to be expanding as the phone is getting swollen and screen is starting to pop off phone.

Bought the 5a 5g from Google but got lost in transportation for bad address apparently. Googled support is ridiculous as it has now been 6 days of hearing "we escalated your issue you will hear from us in 24 hrs" after 24 hours it was again "you will hear from us in 24 hours" now they are telling me I will "hear from us in 72 hours."

What a joke. They offer no resolutions for this issues.

ag...@gmail.com <ag...@gmail.com> #367Sep 7, 2021 09:56PM

Mine 2 months ago

jo...@gmail.com <jo...@gmail.com> #368Sep 7, 2021 10:10PM

My mother's died overnight last week. I can see it from my laptops USB. Is there no fix yet?

sd...@gmail.com <sd...@gmail.com> #369Sep 7, 2021 10:11PM

+1 more Pixel 3XL bricked. Though it happened a few months back and I didn't realize this was an ongoing issue that appears to be the fault of some update sent by Google. Or is that still just speculation? Hard to say since they don't seem to care.

Here's hoping that Google does the right thing and makes good on this problem. Eventually. Maybe. I guess.

ta...@gmail.com <ta...@gmail.com> #370Sep 7, 2021 10:12PM

Same issue as everyone on here with a Pixel 3. Woke up to a dead phone, can't get it to turn back on in any form. Tried all troubleshooting steps. Not a satisfied customer.

br...@gmail.com <br...@gmail.com> #371Sep 7, 2021 10:20PM

As of 09/07/2021 my Pixel 3XL is running flawlessly on Android 12 beta. I consider myself on borrowed time. This is a bummer because I never intended to get this phone. It was for my wife but no headphone jack was a deal breaker for her. This has been the best phone I've ever had and I've had no interest in getting another. Now I'm being forced to consider other phones in case mine bricks. I'll admit the Pixel 6 looks interesting but I don't want to get the first run. Google's track record with initial production is not great.

ri...@gmail.com <ri...@gmail.com> #372Sep 8, 2021 12:06AM

Pixel 3xl bricked - totally black screen. Ended up moving on to a 5a, but wasn't planning on the upgrade anytime soon.

st...@gmail.com <st...@gmail.com> #373Sep 8, 2021 12:18AM

I just got off the phone with Google Fi to which Google store directed me because only Fi can deal with the issue when you purchase there. I tried to explain the Qualcomm EDL issue but as expected was told that the phone is out of warranty and I'm out of luck. A bit angry since it seems pretty apparent that this is a Google F*#@ up, not a "me" problem. I'd be lying if I said I was switching. Don't like Apple and stock Android is a great experience. I have purchased 4 nexus phones and now on my 9th pixel phones in my household, a half dozen Chromebooks, including pixelbooks, a house full of nest products, etc. If you added it all up I'm sure it's more than $10k over the last decade. Just wondering when I can become an important customer? A bit disappointed Google.

sa...@gmail.com <sa...@gmail.com> #374Sep 8, 2021 01:03AM

Same sad story as everyone else... my Pixel 3 died last night and is now completely unresponsive.

ab...@gmail.com <ab...@gmail.com> #375Sep 8, 2021 01:05AM

My pixel 4xl was working flawlessly without any issues. On Aug 2 night I put my mobile for charged and went to bed. When I woke up and checked my phone all I saw was a black screen.

I tried restarting the device, charging it multiple times and even gave my phone to a Google authorized service center but there was no help from anyone.

wa...@gmail.com <wa...@gmail.com> #376Sep 8, 2021 02:17AM

the same problems pixel 3xl just died at night

e....@gmail.com <e....@gmail.com> #377Sep 8, 2021 02:27AM

Same problem here, my pixel 3xl died a couple of weeks ago. I turned it off for a flight and it never turned back on again. It's completely bricked.

ta...@gmail.com <ta...@gmail.com> #378Sep 8, 2021 03:24AM

Same issue.
Pixel 3, Android 10(?), left (not charging) on bedside table overnight and found it to be completely unresponsive the next day. No lights, no buzzing, no charging, no life.
Plugging into computer shows device as "qusb_bulk" followed by numbers.

ak...@gmail.com <ak...@gmail.com> #379Sep 8, 2021 05:13AM

My Pixel 3 bricked about 2 months ago

to...@gmail.com <to...@gmail.com> #380Sep 8, 2021 10:26AM

I also have this issue. I posted about it on an XDA Developers thread where I first learned that it was more a of a widespread issue:

https://forum.xda-developers.com/t/fix-pixel-3-qusb_bulk_cid-xxxx_sn-xxxxxxxx.4205331/post-85171159

ed...@gmail.com <ed...@gmail.com> #381Sep 8, 2021 12:15PM

I have the same issue running the latest Android 12 beta on a Pixel 3.

ga...@gmail.com <ga...@gmail.com> #382Sep 8, 2021 12:40PM

Same here :(

mr...@gmail.com <mr...@gmail.com> #383Sep 8, 2021 03:32PM

My pixel 3XL bricked without warning on the 21/8/2021. One min working next blank screen won't respond to anything

ja...@gmail.com <ja...@gmail.com> #384Sep 8, 2021 03:42PM

My Pixel 3 XL bricked in mid April 2021. Google were useless the whole time. Switched to Xiaomi.

jo...@gmail.com <jo...@gmail.com> #385Sep 8, 2021 04:09PM

My Pixel 3XL bricked on July 1,2021. It was the same as stated above, I plugged my phone in before bed and woke up to a brick.

My computer would recognize a device but not as my phone. Not trouble shooting steps worked to recover my phone. I took it to a repair shop and they tried reseating the battery. When that didn't work, they tried hooking up a new screen. Unfortunately that didn't work either. They didn't charge me anything for their services, just apologized that they couldn't fix it and said the phone wasn't worth repairing at this point anyway.

Luckily I had insurance on my device but they were only able to replace it with a Pixel 4XL. I do not like my 4XL at all. I'm not ready to jump to Apple but I'm not feeling much love from Google.

de...@gmail.com <de...@gmail.com> #386Sep 8, 2021 04:12PM

Same problem here my pixel 3 just bricked last night. Official reply from the support : "we are not aware of this problem," but with a 2 clicks research, ive found tons of messages of this problem

jc...@gmail.com <jc...@gmail.com> #387Sep 8, 2021 04:19PM

Add another one to the pile. Pixel 3 was left unattended and not on charge overnight. Had been working fine, pristine condition apart from the known camera focus glitch. In the morning discovered blank screen - tried to charge, long press power, power & volume up/down - nada. Connected to PC via USB, and it too is seen under Other Devices as "QUSB_BULK_CID" etc.

jk...@gmail.com <jk...@gmail.com> #388Sep 8, 2021 04:22PM

Experienced this issue myself a couple weeks ago. Pixel 3. It's been sitting dead ever since, I had to grab my Pixel 1 XL as an "emergency" backup.
Put it on charge and went to sleep. Woke up and the battery was at ~25%. Put it on charge with another charger after I noticed. Phone said it was charging so I went and did a few things for work. Came back and phone was at 23%. So I played around with a few things, closing apps, unplugging/reseating the charger cable. Nothing was moving the bar. I decided to reboot the phone (at around 16% charge) The phone shut down and then never came back up. It does not respond to any attempt to bring life back in to it.

bo...@gmail.com <bo...@gmail.com> #389Sep 8, 2021 04:34PM

Not yet! but I'm thinking of punching the verizon store salesperson in the nose for strongly suggesting it for me.

kb...@gmail.com <kb...@gmail.com> #390Sep 8, 2021 05:01PM

My pixel 3xl keeps factory resetting itself, loses wifi and Bluetooth constantly, settings keeps crashing, system UI keeps crashing, I fear the worst that soon mine with kick the Bucket too. WHYYYYYYYYYYY!!!!!!???!?!!!!!

ji...@gmail.com <ji...@gmail.com> #391Sep 8, 2021 06:41PM

Bricked; QUSB_BULK_CID issue.
Pixel 3 XL was plugged into charger overnight.
Confirmed phone stopped responding around 9/8/2021 3:30AM ET based on Android Find My Phone status.

Stock OS, NOT rooted, with all automated updates.
Screen unresponsive.
Hard reboot impossible.
Power + volume down or holding power will cause USB connection to PC to detect/disconnect.

When connected to PC via USB:
Device recognized as: Qualcomm HS-USB QDLoader 9008
Bus reported device description: QUSB_BULK_CID {sn redacted}
Current Power State: D0 (fully on state)

If NO Android 9 or 10 Pixel 3 phones are affected by the QUSB_BULK CID issue, then owners are owed some form of compensation for bricking CAUSED by Android 11 or associated version update / security update.

re...@gmail.com <re...@gmail.com> #392Sep 8, 2021 06:58PM

Why is this a P3, this is a P1 global issue. Google is losing good will with pixel fans and now the lawfirm that won the Nexus 6p suit is starting to butt in. All I want is something, credit or tools to reflash my phone myself. Not a "f you, buy a new phone" from the support chat.

lo...@gmail.com <lo...@gmail.com> #393Sep 8, 2021 07:42PM

1. Enable developer options by tapping on build number a bunch of times (in "about phone")
2. Go to developer options and find "automatic system updates" (or search for it)
3. Turn it off

Maybe this can prevent the issue to happen to those with a working P3? Not sure tho!

mf...@gmail.com <mf...@gmail.com> #394Sep 8, 2021 08:22PM

Had this phone for 2 1/2 years. The battery life was poor from the outset and became worse over time. Constantly needed charging which I learned to live with. Last month I turned the phone off and charged at night. The next morning the screen was black and phone has been totally dead ever since. Read other reviews and it appears that this is a common issue and Google has ignored the problem. If you get/have this phone make sure you have real time backup. I learned that the hard way. However, the camera was great but does not balance out with the flaws

bl...@gmail.com <bl...@gmail.com> #395Sep 8, 2021 08:23PM

I've gotten nowhere with Google CS. At one point I asked of they were recording the conversation and they advised they were. I advised them that I would be recording our conversation as well and they advised they were hanging up now because I was recording and that was against their policy that I record the conversation.

am...@gmail.com <am...@gmail.com> #396Sep 8, 2021 08:35PM

The exact same thing happened to me. Had to get a new phone because mine is completely inoperable. No one could/would help me when I tried to get in touch. This is terrible customer service.

ja...@gmail.com <ja...@gmail.com> #397Sep 8, 2021 08:57PM

Same thing happened to me a couple of months ago. Charged overnight, woke in morning and put straight in bag. Looked at it at lunch as dead. Took it to several store's with no joy - said charge was fine so fault with hardware. Bought in London, UK

be...@gmail.com <be...@gmail.com> #398Sep 8, 2021 08:58PM

Idem pixel 3 mort 😡écran noir plus aucune réactions branché ou non. C'est arrivé lors d'une recharge sur pixel stand ಠ︵ಠ

wh...@gmail.com <wh...@gmail.com> #399Sep 8, 2021 10:23PM

Same; Pixel 3 dead...warms up, appears to charge, but no screen/no LEDs...

so...@gmail.com <so...@gmail.com> #400Sep 8, 2021 10:59PM

Mine died this Monday. Woke up and phone was just dead and won't turn on. Sigh. Not buying Google Phone anymore as much as I loved this one.

Message last modified on Sep 9, 2021 09:32PM

jb...@gmail.com <jb...@gmail.com> #401Sep 8, 2021 11:10PM

Having the same issue everyone is reporting on a Pixel 3 XL. Phone restarted and never worked again.

af...@gmail.com <af...@gmail.com> #402Sep 8, 2021 11:11PM

Same here. Wife's 3XL was working normally at bedtime, plugged it in, woke up to a black screen. Bricked. ThebLife360 app last pinged at like 1:47am local time so that appears to be it's official Time Of Death.

My Pixel 5 actually black screen bricked 5 weeks later. It was under warranty though, so Google fixed it. They said it had a "bad screen and charging port". Not sure I buy that though.

ji...@gmail.com <ji...@gmail.com> #403Sep 9, 2021 12:04AM

The QUSB_BULK_CID / Qualcomm EDL mode issue is a result of a bad OTA flash.

This is a "hard brick" because the EDL mode is put in place by Qualcomm specifically to recover from such instances (bad flash to the Secondary Bootloader), and the key to recovery is not made available, see below.

The solution is to use Qualcomm's proprietary management tools QPST / QFIL to flash the phone.

With the correct driver (QDLoader), the phone appears as a Qualcomm HS-UDB QDLoader 9008 device.

QPSTConfig.exe correctly detects the device and COM port number. This confirms the phone is ready for an EDL flash of a factory image.

However, in order to successfully flash a factory image with QFIL, an OEM-digitally-signed programmer is required by the Qualcomm Sahara protocol. Simplified, a proprietary binary "key" needs to be provided by Google to proceed with the EDL recovery flash.

While it is understandable that perhaps releasing the programmer may lead to exploits, surely a tool can be wrapped around QFIL and the programmer to securely perform the flash and released to ubreakifix to do a 20~30 minute factory flash reset.

The first step is acknowledging the severity of this issue - the bugtracker tracking this issue is currently only P3 - to be addressed when able. This should be a P1 - to be addressed quickly, if not P0.

P3 is an insult to everyone using stock, unrooted Android Pixel 3 phones getting bricked by an automated update.

jg...@gmail.com <jg...@gmail.com> #404Sep 9, 2021 12:32AM

Add another one here. Pixel 3xl. Middle of streaming DisneY+ just blam, dead. Plugging into pc says driver unavailable.

bn...@gmail.com <bn...@gmail.com> #405Sep 9, 2021 01:17AM

Adding myself to the list. My Pixel three was on when I woke up and took it off the charger and it died. I did everything and it wouldn't turn back on. The repair place tried several things and nothing. Got it replaced by Verizon because of an extended warranty I didn't know I had.

ab...@gmail.com <ab...@gmail.com> #406Sep 9, 2021 01:20AM

Add another one to the list. Girlfriend's pixel 3, same experience.

Was excited for the pixel 6 to come out. Now I'm switching my entire family to iPhone. Never purchasing or recommending to a Google phone again. And this is coming from someone who was a HUGE Google fanboy previously.

we...@gmail.com <we...@gmail.com> #407Sep 9, 2021 02:11AM

My wife's Pixel 3 died overnight on the charger. Was fine when she went to bed. Woke up and it's a paperweight.

cn...@gmail.com <cn...@gmail.com> #408Sep 9, 2021 10:18AM

My phone got the same issue on 9/8/2021. Phone was charged and not plugged in. Confirmed that the device shows QUSB on windows device manager. Cannot boot device, buttons are unresponsive, etc just like others in the thread.

Completely unacceptable.

va...@gmail.com <va...@gmail.com> #409Sep 9, 2021 11:16AM

Pixel 3XL EDL write like the rest way to do the ball before your new product launch. Can't wait for the pixel 6 launch when my phone is dead, can't take the risk of buying some other pixel phone to get no help when it bricks with the rest of the planet.

ci...@gmail.com <ci...@gmail.com> #410Sep 9, 2021 11:21AM

300 stars and Google still isn't aware of this issue....

fa...@gmail.com <fa...@gmail.com> #411Sep 9, 2021 12:54PM

Pixel 3 died while charging last night. Black screen. will not boot while holding power or volume buttons for reset.

ri...@gmail.com <ri...@gmail.com> #412Sep 9, 2021 01:44PM

Pixel 3 XL with same issue, charging overnight and woke up to unresponsive phone with <QUSB...> activity shown when connected with Windows PC. VERY FRUSTRATING!!!

ja...@gmail.com <ja...@gmail.com> #413Sep 9, 2021 02:06PM

The same thing happened to my beloved Pixel 3XL months ago. I still have it around.

al...@gmail.com <al...@gmail.com> #414Sep 9, 2021 02:26PM

Same thing happened to my pixel in July. Still have the dead phone lying around in a desk draw.

ju...@gmail.com <ju...@gmail.com> #415Sep 9, 2021 04:14PM

Same thing here .. for me, it's just a " planned obsolescence" !! Mine , Pixel 3, dead in February, just 2 years and 1 day after first Power ON !! Yes 1 day . Google does not care about that situation, Pixel 3 just power Off and now starting G in loop, and nothing... Still have try EVERYTHING .. but no way ..

me...@gmail.com <me...@gmail.com> #416Sep 9, 2021 04:38PM

I see this being picked up on the news more. I have a Pixel 3Xl and a 4XL, both are unlocked and bought directly from Google and have the 3XL on VZ and 4XL on AT&T. Other than a bloated battery issue last year on the 3XL which I got repaired, both have not had issues.

I would second the suggestion earlier, to go into developer mode and disable automatic system updates as well as disable auto updates from the Google store until this gets resolved. Sucks because I generally keep my apps up to date, but don' want to take the chance of hosing either phone.

mj...@gmail.com <mj...@gmail.com> #417Sep 9, 2021 04:50PM

Same issue here with my Pixel 3xl. Happened a few weeks ago and had to buy a new phone as an emergency. Thanks for nothing google.

lu...@gmail.com <lu...@gmail.com> #418Sep 9, 2021 05:52PM

Hey, Google. I have a Pixel 3XL that actually still works by some miracle. However, I am starting to feel like I am on borrowed time.

Do the right thing and help these people ^ out. Step up, do the right thing, and replace their devices. Maybe then I won't second-guess getting another Pixel someday.

hg...@gmail.com <hg...@gmail.com> #419Sep 9, 2021 06:41PM

My Pixel 3 xl also bricked while charging overnight. No button commands bring it back or initiate a reset cycle.

mi...@gmail.com <mi...@gmail.com> #420Sep 9, 2021 09:45PM

My Pixel 3 bricked sometime between 3:30am and 6am this morning. Stuck in EDL. get the same QUSB.... as everyone else when I plug it into my computer. Can't upgrade to a new pixel because they're sold out everywhere.

br...@gmail.com <br...@gmail.com> #421Sep 10, 2021 01:10AM

Happened to me on 8/14... Android 11, plugged in overnight and woke up noticing battery was at 4%, charging icon showed but wouldn't actually charge. I went to restart it and completely dead. Repair stores said motherboard issue, google told me to buy a new phone. After the nexus bootloop and now this never again. Make sure to contact

https://chimicles.com/google-pixel-3-class-action-investigation/

ru...@gmail.com <ru...@gmail.com> #422Sep 10, 2021 01:18AM

I have no idea if it makes any difference, but the September monthly security update (below) has 18 lines with Qualcomm
I updated my two Pixel 3 XL (bought 2018 from Google, on Rogers, Canada, stock, not rooted, Android 11) and both work fine (so far)

https://source.android.com/security/bulletin/2021-09-01

Message last modified on Sep 10, 2021 01:20AM

ke...@gmail.com <ke...@gmail.com> #423Sep 10, 2021 05:31AM

August 20th, put Pixel 3 XL on charge overnight.

Woke up to bricked device; black screen, Non-responsive to power+voldown.

Taken in to Ubreakifix, verdict: "Motherboard failure of some kind".

When plugged into PC shows up as "QUSB_BULK_CID:0402_SN: ..." just as with the other reports of this type.

de...@gmail.com <de...@gmail.com> #424Sep 10, 2021 09:09AM

Same issue here, happened Sept. 9th. Just hoping now that I can recover some of my data.

th...@gmail.com <th...@gmail.com> #425Sep 10, 2021 11:51AM

Just joining in. I woke up to a dead phone on September 1. Took it to Ibreakufix for free diagnostics per google support recommendation, they had it several days before calling back to say they couldn’t get it to do anything. Yeah, no kidding. And of course it died right after the 2 year/last payment mark. Had been considering the 5a, but nope. Not very happy at the moment

ks...@gmail.com <ks...@gmail.com> #426Sep 10, 2021 12:13PM

- Build Number: google/redfin/redfin:12/SPB5.210812.002/7671067:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

I have had the same problem - woke up Saturday morning (4th) to a completely dead Pixel 3. It was running the latest beta of Android 12 at the time.

Debugging information
Google Play services
com.google.android.gms
Version 213016053 (21.30.16 (190400-391784508))
System App (Updated)

Android System WebView
com.google.android.webview
Version 457706234 (93.0.4577.62)
System App (Updated)

Network operator: giffgaff
SIM operator: giffgaff

Filed by Android Beta Feedback. Version (Updated): 2.20-betterbug.external_20210805_RC02
To learn more about our feedback process, please visit

https://developer.android.com/preview/feedback#feedback-app.

ci...@gmail.com <ci...@gmail.com> #427Sep 10, 2021 12:29PM

Google pixel 3 bought on 1 December 2018, bricked in EDL mode on 14 December 2020. 2 years and 2 weeks. It may be interesting to post exactly how many days your phone lasted to see if there's a trend.

pl...@gmail.com <pl...@gmail.com> #428Sep 10, 2021 12:38PM

Just reporting that I woke up on September 5th with the exact same issue. Dead phone, in EDL mode. Nothing I can do. Great timing google as I was going to wait for the Pixel 6. I'm done with google phones now as nothing is in stock and I need a replacement.

ly...@zoominternet.net <ly...@zoominternet.net> #429Sep 10, 2021 01:16PM

My Google Pixel 3 worked at 8:30 am on September 6th. Tried to turn it on at 11:30 am and it wouldn't. Verizon was useless, as usual, so I took it to UBREAKIFIX and he said the battery actually fried the inside and that I was very lucky it didn't explode in my hand. My pictures were all backed up but due to the severity, were irretrievable. I had the extended warranty but there was a pin sized crack in the screen and wouldn't honor it

lo...@gmail.com <lo...@gmail.com> #430Sep 10, 2021 02:46PM

Pixel 3xl Blank home screen every day, need to reboot to make it come back. Not sure how long it will last and I hope it wont get bricked soon but this is my last google phone I will ever buy. Going back to apple, where the phones actually work and has monetary value long after purchase date.

ji...@gmail.com <ji...@gmail.com> #431Sep 10, 2021 03:05PM

Until the OTA bricked my 3 XL, I have to admit it was the best phone I've ever owned.

To everyone that's considering getting another new Pixel despite this horrible experience, please remember to opt-out of arbitration.
When you buy a new Pixel, Google slips in a non-arbitration agreement as PART of the act of purchasing.

Search for "Pixel arbitration opt-out" or go here within 30 days of activation:

https://partnerdash.google.com/apps/devicearbitrationoptout/optoutform
Make screenshots, and note the day and time of when you opted out.

la...@gmail.com <la...@gmail.com> #432Sep 10, 2021 07:49PM

Adding my name to the list, plugged my phone in one night in June and the next morning just a black screen. Phone had no problems before then.

ri...@gmail.com <ri...@gmail.com> #433Sep 10, 2021 09:00PM

My 3XL has been going black screen unresponsive for a couple of weeks but a forced power down and power up seems to resolve currently. Charging port quit working a couple of months ago and lately pressure in the screen causes it to become unresponsive. Like if I tap too hard it takes a force restart to function again. I've been generally happy with my Pixel until the last couple of months, but this is really shoddy build / software quality. I will not be purchasing another pixel unless this issue is resolved and guarantees are in place in case of a similar problem down the line.i really feel like the class action route is going to be the only avenue for reloef.

Do the right thing Google. Your motto used to be "Don't Be Evil". We just want our phones to work

ra...@gmail.com <ra...@gmail.com> #434Sep 11, 2021 12:53AM

Last year I started getting the infamous "Bluetooth has stopped working" popup and my Bluetooth & wifi would constantly disconnect, requiring dozens of restarts daily and tapping the device against hard surfaces to jostle the poorly soldered part of the board that causes this problem to get it to work again. I ended up smashing the screen out of frustration one day. (It worked pretty good for a little while after that).

And now, I'm bricked... Phone won't boot, stuck on this screen.

IMG-20210910-WA0000.jpeg

1.1 MB

View

Download

be...@gmail.com <be...@gmail.com> #435Sep 11, 2021 07:22AM

Add mine to the list of dead phones. Fine one day, dead the next. They're bricking phones intentionally. Never going with Google again.

zn...@gmail.com <zn...@gmail.com> #436Sep 11, 2021 08:59AM

the same for me - dead out of nowhere. charging, holding buttons for a long time does not help.

bo...@gmail.com <bo...@gmail.com> #437Sep 11, 2021 12:18PM

My wife's Pixel 3 bricked overnight. She used it before bed, woke up just a little while ago and completely bricked. It was on the charger. Tried power+vol down, nothing. So very disappointed.

ja...@gmail.com <ja...@gmail.com> #438Sep 11, 2021 12:23PM

Pixel 3xl user here that has the brick issue. Shame we are holding out for
the pixel 6 and this will force us to change brands so my wife has a
phone. May want to take care of the people that are waiting for the pixel
6 that are ready to upgrade from the 3. You will lose sales over this.

On Sat, Sep 11, 2021, 8:19 AM <buganizer-system@google.com> wrote:

- Show quoted text -

je...@gmail.com <je...@gmail.com> #439Sep 11, 2021 12:23PM

My pixel 3xl bricked on 9/9/21 around 9am. It got caught in a constant state of restarting. I tried everything to get it started in a different mode with not luck. I let it completely drain the battery and charge it all the way up with no luck either.

vi...@gmail.com <vi...@gmail.com> #440Sep 11, 2021 01:11PM

My phone restarted by itself overnight and in the morning was stuck on a google backup screen. Tried to force restart using the power button and hasn't come up since. Completely blank screen with no charging sign etc.

aa...@gmail.com <aa...@gmail.com> #441Sep 11, 2021 02:15PM

https://twitter.com/aashishmallik/status/1436581113909088257

I am also facing same issue with my google pixel 3 device . Please retweet my link and make it a campign against Google for pixel 3

ps...@gmail.com <ps...@gmail.com> #442Sep 11, 2021 03:55PM

My pixel3 XL did this about a week ago, called google support, they said
out of warranty, take it to UBREAKIFIX. They had no solution.

On Sat, Sep 11, 2021, 08:15 <buganizer-system@google.com> wrote:

- Show quoted text -

sh...@gmail.com <sh...@gmail.com> #443Sep 11, 2021 04:31PM

My Pixel 3xl become brick 2 night ago.
Since its from 2019 it out of warranty ...
Chat with google support and saying its all over the web ended with
8:17:15 Ryan: There are people who are working on that issue tracker. If you need to any update on the issue, you can view the link.
8:17:40 Ryan: However in this case, we wont be able to provide any warranty options for the device.

hi...@yahoo.com <hi...@yahoo.com> #444Sep 11, 2021 09:23PM

Add my wife's phone to this list. Praying mine doesn't die now.

Message last modified on Sep 11, 2021 09:24PM

ja...@gmail.com <ja...@gmail.com> #445Sep 11, 2021 09:39PM

How many pixel 3 owners are on this list that were waiting for the pixel 6 to come out to upgrade?? How many of you are now reconsidering this purchase after being told they weren't going to do anything to help you?

ho...@gmail.com <ho...@gmail.com> #446Sep 11, 2021 10:23PM

Me. And I just purchased a Galaxy 21. I loved that damn Pixel 3xl too.
________________________________
From: buganizer-system@google.com <buganizer-system@google.com>
Sent: Saturday, September 11, 2021 5:39:33 PM
To: b-system+-312113003@google.com <b-system+-312113003@google.com>
Cc: howiehaslb@gmail.com <howiehaslb@gmail.com>
Subject: Re:

Issue 192008282

: Pixel 3 bricked while charging overnight around 7am Pacific

Replying to this email means your email address will be shared with the team that works on this product.

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

Changed

ja...@gmail.com added

comment #445

https://issuetracker.google.com/issues/192008282#comment445>:
How many pixel 3 owners are on this list that were waiting for the pixel 6 to come out to upgrade?? How many of you are now reconsidering this purchase after being told they weren't going to do anything to help you?

_______________________________

Reference Info: 192008282 Pixel 3 bricked while charging overnight around 7am Pacific
component: Android Public Tracker > Android Developer Preview / Beta<

https://issuetracker.google.com/components/190602>
status: Assigned
reporter: za...@gmail.com
assignee: ad...@google.com
cc: ad...@google.com, fr...@google.com, za...@gmail.com, and 1 more
type: Bug
priority: P3
severity: S3
blocked by: 192267656<

https://issuetracker.google.com/issues/192267656>
duplicate issue: 199294995<

https://issuetracker.google.com/issues/199294995>
found in: SPB2.210513.011
hotlist: Platform<

issue 192008282

https://issuetracker.google.com/issues/192008282> where you have the role: starred.
Unsubscribe from this issue.<

https://issuetracker.google.com/issues/192008282?unsubscribe=true>

xb...@gmail.com <xb...@gmail.com> #447Sep 12, 2021 07:49AM

So i have this same issue, and i;ve simply been told to "pair for out of warranty" repairs.
Wonderfull...

rw...@gmail.com <rw...@gmail.com> #448Sep 12, 2021 02:46PM

I got a pixel xl 3 and it went to the black screen and I can't get it to respond to anything

dr...@gmail.com <dr...@gmail.com> #449Sep 12, 2021 03:07PM

Same problem with same symptoms. Pixel 3 stuck in QUSB_BULK_CID mode.

dd...@gmail.com <dd...@gmail.com> #450Sep 12, 2021 03:15PM

- Build Number: google/crosshatch/crosshatch:12/SPB5.210812.002/7671067:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

The Pixel 3 XL turned off while charging and didn't turn on for 2 days. Now, for some reason, it has come to life.

Debugging information
Сервисы Google Play
com.google.android.gms
Version 213017053 (21.30.17 (190400-395706864))
System App (Updated)

Android System WebView
com.google.android.webview
Version 457706233 (93.0.4577.62)
System App (Updated)

Network operator: MegaFon
SIM operator: MegaFon

Filed by Android Beta Feedback. Version (Updated): 2.20-betterbug.external_20210805_RC02
To learn more about our feedback process, please visit

https://developer.android.com/preview/feedback#feedback-app.

rs...@gmail.com <rs...@gmail.com> #451Sep 12, 2021 03:50PM

Yup... One of the two Pixel 3 phones in the family just bricked a couple months ago... No screen message, just a completely black brick... Originally purchased thru Google Fi, but no support other than purchasing a new 4a... Trade in for credit not allowed on the bricked unit cuz it won't power on.

sb...@gmail.com <sb...@gmail.com> #452Sep 12, 2021 05:55PM

Phone bricked sitting idly on my desk today. Phone won't react to any kind of I/O

jm...@gmail.com <jm...@gmail.com> #453Sep 12, 2021 07:22PM

On the night of August 29th my phone was charging in my bed as per usual, when I plugged it in the battery was around 70%. I checked it for messages later on and found it had turned itself off. I thought that was kind of strange, but didn't think too much of it and turned it back on. The battery was then at 90%. When I checked it again later, it again had turned itself off, only this time it would not turn back on. Every time I would try to launch it, it was show the Google logo at boot, and then immediately shut down. It was acting like it didn't have enough battery life to even boot.

I tried for the whole next day to charge the phone in multiple different ways (from the computer, wirelessly, with the original charger and cable, and any other appropriate cable) and to launch it in every possible way from the Fastboot menu to recover the phone, but every time it would launch it would do the same thing of showing the Google logo, then shutting off-- even while plugged in for hours. Initially, when plugged in and off, it would at least display the charging battery symbol on the screen and get warm to the touch. Eventually with all my attempts to boot it, it got in a loop of flashing the Google logo over and over as it tried to boot repeatedly. Now it won't even do that much, it's gone completely dead, unresponsive, and won't charge. I've had this phone for about 2 years and a month. The warranty only lasts for a year. I'm pretty annoyed for my phone to have this catastrophic failure after just 2 years. I will still replace it with another Google phone, because up until this moment I was totally satisfied with it, but what a horrible way to go out from something that was by no means cheap. Very disappointing.

sh...@gmail.com <sh...@gmail.com> #454Sep 12, 2021 08:15PM

Left my house yesterday AM with a working phone. Got out of the car and P3XL was off. Bricked. Will not turn on. Absolutely dissapointed.

et...@gmail.com <et...@gmail.com> #455Sep 13, 2021 09:18AM

SImilar with me, but it wasn't charging, it wasn't doing anything. I was scheduled to perform surgery (I'm a neurosurgeon resident). While I was waiting for the preoperative DSA to complete, I picked up my phone from the table and it simply won't turn on. I was still using it to record 4 videos of the DSA less than 15 minutes prior.

I remember still having around 40%ish before putting it down on the table. I tried charging it with various chargers, pressing the power button for >30s, pressing both power and volume rocker (attempted up, down, and both), and it still doesn't show anything on the screen. I tried connecting it to my laptop, and there it goes... QUSB_BULK_CID. Yep, it's bricked.

It was vanilla, no history of rooting or any other tampering, I only enabled the developer mode (Forgot what for).

I've read about the issue in the beginning of the month on arstechnica, but I was mulling on the replacement, and these 2 weeks has been hectic at work, so I haven't decided on the replacement. Now it's ruining my day, I can't contact the patients I scheduled for this week and the next, and I can't communicate with most people because most people use whatsapp around here. total pain in the arse. I know I'm going to replace it, but not like this.

am...@gmail.com <am...@gmail.com> #456Sep 13, 2021 11:48AM

I got the same issue and guess I will have to throw it away now.

em...@gmail.com <em...@gmail.com> #457Sep 13, 2021 03:41PM

happened to me too - woke up august 30 to a screen saying my phone was corrupted and could not be trusted, and when I hit the button to continue it locked itself in EDL mode and I haven't been able to get it out. thankfully I had an old phone to fall back on, but I lost a lot of data and my old nexus 6p has very little battery life.

da...@gmail.com <da...@gmail.com> #458Sep 13, 2021 04:25PM

Same issue here happened to me back in April - Google support only suggestion was to send in for expensive repair. Same "Could not be trusted" error and then going in to EDL mode and unable to power-on. Appears to charge via wireless but doesn't power on.

ia...@cazabat.com <ia...@cazabat.com> #459Sep 13, 2021 06:56PM

Adding my Pixel 3XL to the list of now dead Pixels. Battery was running down quickly last night (7% => 1% in less than a minute) so I put it on the charger & went to sleep. Woke up late for work today & realized phone was dead.

I am/was anticipating the launch of the unannounced Pixel 6, but this will give me a bit of pause if the Pixel 6 does come out with a "flagship" price tag. I bought my 3XL used, so was a great deal.

I loved my 3XL up until it died. I'm hoping Google does the right thing and gives us a chance to get these phones working again. Most of my stuff was backed up the night before, but pictures/etc that I took yesterday are currently "lost".

ia...@cazabat.com <ia...@cazabat.com> #460Sep 13, 2021 07:20PM

Please release the necessary "firehose" file for the Pixel 3/pixel 3XL. That way we can resurrect our phones! If you need a "broken" phone for testing, I'd gladly send mine in!

More info on firehose:

https://forum.xda-developers.com/t/fix-pixel-3-qusb_bulk_cid-xxxx_sn-xxxxxxxx.4205331/page-2
Qualcomm HS-USB QDLoader 9008

m....@gmail.com <m....@gmail.com> #461Sep 13, 2021 07:39PM

Same exact EDL issue. My phone died Late July/Early August. Brought it into uBreakiFix and it was returned to me as "unfixable". This issue has kicked off a series of events with my current carrier, Verizon, and I am now leaving them. I am buying new Samsung phones with my new carrier as I will no longer purchase any Google product. So good job, Google, you lost this customer AND cost Verizon a customer of 15 years.

jk...@gmail.com <jk...@gmail.com> #462Sep 13, 2021 08:49PM

I have the same issue - woke up to a dead Pixel 3, when plugged in it shows QUSB_BULK_CID. Phone in perfect condition, stock, unlocked, one year old

or...@gmail.com <or...@gmail.com> #463Sep 13, 2021 08:53PM

Same here! Can't believe they keep treating me like I did something wrong and should take it to an authorized dealer - when an authorized dealer can't fix it.

ja...@gmail.com <ja...@gmail.com> #464Sep 14, 2021 05:11AM

I've had this same issue with my Pixel 3. It's a fancy paper weight. And Google Support....my god what a joke! Customer service certainly is lost with these mega corporations! They'd rather ignore the problem in hopes of saving a few bucks. Has anyone had luck getting their data back?

pa...@gmail.com <pa...@gmail.com> #465Sep 14, 2021 07:47AM

Here's your conspiracy thought of the day: This was hard coded into the firmware to happen. Semi-randomized end-dates. Was supposed to have happened six to eight months _after_ the Pixel 6 was out, to "encourage" people to take the easy path and upgrade. But the pandemic threw a monkey wrench into it, and for whatever reason, they are unable to stop it.

Mind you, I believe the Zombie Apocalypse is imminent, so, yeah.

ma...@gmail.com <ma...@gmail.com> #466Sep 14, 2021 09:35AM

If it is a consiparcy it has backfired for google, I had a Pixel 1xl that the battery gave up 2 years in and so upgarded to Pixel 3xl (Ok maybe that consiparcy worked lol). Saw the Pixel 6 teasers and was preparing to upgarde to that when it was released but when my Pixel 3 bricked itself prematurely, it was too early to look at the 6 and I didn't want to risk having another phone that bricks for no reason. I am now the proud owner of a Redmi Note 10 pro. Quarter of the price of a new pixel and so far just as happy with it.....possibly more happy as I have money left in the bank :) . I cannot justify paying flagship prices for phones that die before you are ready to move on.

ex...@gmail.com <ex...@gmail.com> #467Sep 14, 2021 12:06PM

I just had the same experience as many above. Phone was unexpectedly off this morning. Nothing shows on the screen, no charging icons, long hold on power button does nothing (that I can tell), long hold on power and down volume does nothing (that I can tell).

nv...@gmail.com <nv...@gmail.com> #468Sep 14, 2021 03:35PM

Adding to the list of bricked Pixel 3XLs

re...@gmail.com <re...@gmail.com> #469Sep 14, 2021 03:42PM

Buy a Pixel 3/3XL with a smashed screen on ebay for 50 bucks. Swap the
motherboard into your Brixel 3/3XL and downgrade to android 10 and or
disable automatic OTA updates and updates through the Google store until
Google figures out what the hell they've screwed up and announces a fix or
apologizes. Don't buy a new phone, this one is perfectly fine and it's the
cheapest still relevant flagship out there.

On Tue, Sep 14, 2021, 11:36 AM <buganizer-system@google.com> wrote:

- Show quoted text -

bi...@gmail.com <bi...@gmail.com> #470Sep 14, 2021 05:07PM

Any lawyers here for a class law action suit or is there one already going on?

je...@gmail.com <je...@gmail.com> #471Sep 14, 2021 05:59PM

This.

ja...@gmail.com <ja...@gmail.com> #472Sep 14, 2021 06:06PM

My wife's 3xl did this over the weekend. I installed the Android 12 beta
in hopes that mine won't do this. All we wanted was to use the 3 until the
6 comes out. This crap makes us not want to buy the 6 and jump brands. If
there is a class action suit, we are ready to hand over a sample of a
bricked phone!

On Tue, Sep 14, 2021, 2:00 PM <buganizer-system@google.com> wrote:

- Show quoted text -

m....@gmail.com <m....@gmail.com> #473Sep 14, 2021 06:19PM

Apply for the official Pixel Superfans club and let them know how you feel until they address this issue:

https://docs.google.com/forms/d/1dmYGc-6-eY2TwwfqxINP1QEzEv2ep69AZH6947LH8oo/viewform?edit_requested=true

https://www.androidauthority.com/pixel-superfans-3022875/

ja...@gmail.com <ja...@gmail.com> #474Sep 14, 2021 06:23PM

Am I the only one who actually got an RMA on this issue even when my warranty has expired?

ni...@gmail.com <ni...@gmail.com> #475Sep 14, 2021 09:06PM

https://chimicles.com/google-pixel-3-class-action-investigation/

je...@gmail.com <je...@gmail.com> #476Sep 14, 2021 09:33PM

Mine got bricked as well. Woke up to a dead phone. Also getting the "QUSB_BULK_CID" when I hook up to a computer.
Charging to google wifi charger doesn't help either even if the white light indicator on the charger is blinking.
Did try that hold power and volume down button for 32 seconds for more than 10 times now. Still no luck!

wi...@richey.id.au <wi...@richey.id.au> #477Sep 14, 2021 09:40PM

Same issue. Phone unexpectedly off this morning. Nothing shows on the screen, and pressing the power button or power button + volume does nothing. Connecting to PC shows it's stuck in Qualcomm EDL mode

jo...@gmail.com <jo...@gmail.com> #478Sep 14, 2021 09:49PM

I have a working pixel 3 XL. Does somone have any advice to have it not brick itself in the near future?

am...@gmail.com <am...@gmail.com> #479Sep 14, 2021 11:01PM

Interesting, not sure if anyone else has had success (lots of posts here I haven't had a chance to read them all) but Google device support reached out to me today by email requesting I send my Pixel 3 VZW version into them for evaluation. Email body copied below for reference.

-----------------------------------------------------------------
Hi,

My name is Sean, and your case was escalated to the Advanced Hardware Support Team for additional review. I understand you are experiencing an issue with your Pixel 3 stuck in EDL mode. I’m happy to look into this for you!

Our analysis team is interested in looking at some of these devices, so I'd like to offer you a replacement device. This process requires you to ship your original device first. After we receive the device, we will ship out the warranty device. Expect a turnaround time of 5-10 business days. If you're open to that, please respond with the following information:

Your full name:
IMEI of the Pixel:
Full shipping address:
Phone number:
I look forward to hearing back from you. Feel free to include any questions in your response.

Thanks!

Sean
The Google Support Team

ze...@gmail.com <ze...@gmail.com> #480Sep 14, 2021 11:07PM

No success as of yet. Was your device still under some kind of warranty?

To those who haven't already, be sure to click that little star in the top right corner to mark yourself as effected. Thanks! :D

am...@gmail.com <am...@gmail.com> #481Sep 14, 2021 11:32PM

No it was definitely not under any extended warranty. It was purchased in Dec of '18 direct from Verizon (shameful yes I know) so it wasn't even still under the 24 month warranty extension they supposedly applied due to the 3XL screen PR nightmare from launch.

Hopefully they make it right. I used to upgrade my phone at least once a year for as long as I could remember. I ordered the Pixel 3 right after launch and have had it since. Truly the best phone I've ever owned and still was fast enough & approaching 3 years old. The perfect combination of size and features.

ja...@gmail.com <ja...@gmail.com> #482Sep 15, 2021 01:02AM

My wife just got done with a chat with support. They acted like they had
no idea what she was talking about. She gave them this issue id number 3
times to look up. It was a waste of her time and patience.

On Tue, Sep 14, 2021, 7:32 PM <buganizer-system@google.com> wrote:

- Show quoted text -

sa...@gmail.com <sa...@gmail.com> #483Sep 15, 2021 01:02AM

Ya my Pixel 3 XL bricked itself overnight as well, woke up, no response at all, repair place said they could not figure it out, figure it got a patch overnight and bricked itself.

mc...@gmail.com <mc...@gmail.com> #484Sep 15, 2021 02:50AM

Same issue here on Pixel 3 bricked out of the blue on Aug 10.

Google CS recommended I get it checked out at a local ubreakifix. They didn’t have a solution except replace the motherboard for $500.

Google CS then suggested I mail the phone in to get diagnosed. They now claim the phone has water damage and quoted $450+ for a refurbished phone (while they have them on the google the store for $250). They even changed the ticket to show that I reported a water damage even though I originally reported a blank screen issue.

I’m normally not a paranoid person, but Ubreakifix did not find water damage and actually noted the phone was in very good condition in their ticket.

I’ve been with google phones since Nexus and was planning on getting a Pixel 6. However I’m tired of dealing with quality issues on every google phone I’ve had and their terrible CS. Will be moving on to something else.

to...@gmail.com <to...@gmail.com> #485Sep 15, 2021 01:46PM

Just a reminder to make sure to check the "star" the top, at the top next to the issue number. That tracks how many are affected.

bl...@gmail.com <bl...@gmail.com> #486Sep 15, 2021 02:41PM

To anyone reading this I would suggest hounding Google customer support. I requested a call from them and refused to accept no for an answer. I stated that the evidence is clear that this is absolutely something Google did to mess up the Pixel 3. I sent them about 10 articles from news publications as well as a link to this issue tracker. I had a request sent to replace my Pixel 3 XL that bricked about 2 weeks ago. They denied it. I emailed back and asked for a call to explain why it was denied.

The representative was somewhat helpful....I also got pretty upset and demanding without ever getting rude. He stated they could do a $35 store credit but he knew it I would not be happy with that offer. Afterwards he stated he was going to send another request for RMA to a different higher dept. The following day he emailed me stating they were making a one time exception. I have my dead Pixel 3 XL boxed up and was going to send it off yesterday, but the shipping store was closed due to a hurricane.

It wasn't pleasant and it wasn't easy, but eventually they agreed to replace.

So call, raise hell, and don't take no for an answer. Be polite with a little belligerence and hopefully they'll do the same for you.

ji...@gmail.com <ji...@gmail.com> #487Sep 15, 2021 03:41PM

Contact device support. They will deny knowledge of QUSB_BULK_CID issue, "we do not find that keyword in our support knowledge base".
Call them out immediately for lying. Refer to this bugtracker, and people that have already raised this issue to support numerous times.
Feel free to refer to my Case ID below.

Please post your CASE IDs here. It's very hard for support to deny knowledge when we list our Case IDs referring to the same problem.

I was promised my case would be escalated to engineering, only to be railroaded like copied below.

=====================================================
2021 SEP 9

Your Google Support Inquiry: Case ID [0-3328000031401]

Hi Jim,

Thanks for contacting Google Support!

After escalating the case to the escalations team they have given their decision. Unfortunately they pushed back the request for a replacement device for this issue. I am sorry Jim, but we cannot process anything for this. We appreciate you letting us know about this issue.

Have a great day and stay safe!

Thanks!
Jhon
The Google Support Team

to: device-support

This is unacceptable without an explanation.

I was told the engineering team would be involved, but the decision is not based on any empirical evidence, just a denial of request by an escalations team without reason.

This is not a user caused failure, nor has any investigation of this documented problem attributed to hardware failure.

If no due process is being made to determine the cause of failure, then the only explanation is that a software update CAUSED this wide-spread failure.

In the bug tracker, there is not a single case of the QUSB_BULK_CID issue with Android 10 or Android 9.

Initial escalation team even denied knowledge of this problem, while the bug tracker and news outlets have documented this for months.

Please provide an explanation of the denial of warranty exception.
Please provide evidence this problem is NOT caused by a software update, which can be construed as willful intent to disable my Pixel 3XL.

be...@gmail.com <be...@gmail.com> #488Sep 15, 2021 03:48PM

For those that managed to get a RMA, can you post your google case id so we can reference it to help our case?
Thx

me...@gmail.com <me...@gmail.com> #489Sep 15, 2021 03:52PM

So do we know if it is updates via the Google Play store or if it is the automatic system updates or a combo of both?

am...@gmail.com <am...@gmail.com> #490Sep 15, 2021 03:54PM

Hopefully this helps!

Your Google Support Inquiry: Case ID [5-1064000031500]

ji...@gmail.com <ji...@gmail.com> #491Sep 15, 2021 03:57PM

@am...@gmail.com #490

did you happen to get an RMA for Case ID [5-1064000031500]? Thanks for posting!

ce...@gmail.com <ce...@gmail.com> #492Sep 15, 2021 05:07PM

Adding my phone to list. Randomly bricked overnight, currently identified as QUSB_BULK

vi...@gmail.com <vi...@gmail.com> #493Sep 15, 2021 08:05PM

Every time I do a chat with them and reference case [5-1064000031500], they say we will follow up on that case and forcefully close the chat. I told them numerous times that it is not my case and I am just referencing it to show the similarity in the issues. Sigh.. Amazing support. Wow, the level of competence of the support folks is amazing.

an...@gmail.com <an...@gmail.com> #494Sep 16, 2021 01:03AM

Mine just randomly bricked overnight as well. Wtf google. This isn't the first time hardware they've released has had major bricking issues.

lu...@gmail.com <lu...@gmail.com> #495Sep 16, 2021 01:06AM

I have had this issue with multiple Pixel and Nexus phones, including my current Pixel 3XL, usually around the 2 or 3 year mark, when the battery is starting to lose its ability to charge (the symptom of the battery starting to fail is that the charge will drop from something like 15% to 0% in a matter of seconds). Usually the bricking has happened when I have been running some high-power-drain application when the battery drained to zero. From that point, it seems that the battery reached such a low voltage that even with the USB cord plugged in, something in the charging circuitry or firmware refuses to switch the power system into charging mode, and won't even draw enough power from the USB cable to boot. The last time this happened it took me several days of trying all sorts of combinations of plugging, unplugging, holding down button combinations for different periods of time, etc., sometimes with a brief flash of something on the screen, sometimes not, before the phone suddenly powered on again and it was back to working. I replaced the battery through uBreakiFix, and haven't had any problems since. No phone should ever enter a state where the power circuitry refuses to accept power from at least the USB cable, or refuses to switch on the battery charging circuitry! This is ridiculous. Again, I have had this problem on multiple Pixel and Nexus devices.

ji...@gmail.com <ji...@gmail.com> #496Sep 16, 2021 01:18AM

Case ID [9-2313000031523]
Me: I am also recording this conversation
Support: We do not allow you to record
Me: So you can record, but I can't?
Support: That is correct.

... railroading continues, goes nowhere ...

Support: would you like to provide feedback after this call?
Me: sure
Support: please hold *click*

Call disconnected.

ti...@gmail.com <ti...@gmail.com> #497Sep 16, 2021 01:58AM

Your Google Support Inquiry: Case ID [0-7369000031531]

Hi $NAME

Thank you for contacting Google Support Team.

This email is in reference to our conversation about device won't turn on.

As discussed, your device is out of warranty, and we'd recommend you to get in touch with the CTDI Google's official repair partner they'll help you get your device fixed.

Please find below the details of CTDI :-

CTDI
All Pixel phones
Type of service: Not available services
Repairs for Pixel phones affected by physical or liquid damage
Phone: +61 2 9150 4243

http://www.ctdi.com.au/page/contact
Hours
Mon-Fri: 8:30 AM–4:30 PM local time

ca...@gmail.com <ca...@gmail.com> #498Sep 16, 2021 02:18AM

Same issue here. No power at all.

ph...@gmail.com <ph...@gmail.com> #499Sep 16, 2021 02:49AM

Seems like a lot of people are having a more than an unsatisfactory experience with Google tech support, same when I had to contact them for defective Pixel Buds. A lot of articles out about this Pixel situation with very few updates. Perhaps Engadget, Android Authority, 9to5 Google, etc. can start doing some articles on Google's very poor customer support and push to fix things for the better.
My Pixel 3 is still surviving but I had to dig a lousy old Samsung phone and get it ready to go just in case. Phone contact is critical for my job and Google is letting me down.

cu...@gmail.com <cu...@gmail.com> #500Sep 16, 2021 04:13AM

Same here. My phone has stopped working. And my device is out of warranty probably. And google doesn't even seem to have the support that I have to roam around its issue tracker. How about you don't send some shitty updates and make the device work autonomously? I talked to google using the phone and they were clueless lol. Even after poininting this link they were like we can't open issuetracker.

Thanks google for bricking my device. I lost all my photos/files probably.

ze...@gmail.com <ze...@gmail.com> #501Sep 16, 2021 04:17AM

If you were running with default settings, you could try logging into google photos online. Photos should be backed up there, though probably not files.

Hope this helps!

(Don't forget to click the star at the top :D )

am...@gmail.com <am...@gmail.com> #502Sep 16, 2021 10:26AM

No RMA yet for my case ID. I gave them a day to process my info so I'll email today to see what is what & update here.

oz...@gmail.com <oz...@gmail.com> #503Sep 16, 2021 12:17PM

I was ready to buy the Pixel 6, however this experience has soured me on Google hardware forever. I've switched to an iPhone (Apple have fantastic after-market service these days, even well beyond warranty) and have been very active in my not-inconsiderable social network in advocating strongly against Google branded phones. At least 10 of my friends now will not be purchasing the 6 and are looking elsewhere.

While it's unlikely Google will ever care (P3/S3 on this ticket literally means "never look at this"), at the least we can cost them tens to hundreds of thousands of dollars in sales.

aq...@gmail.com <aq...@gmail.com> #504Sep 16, 2021 01:12PM

My Pixel 3 XL also bricked out of nowhere. I can't remember the exact day anymore but I think it's nearly a month now since it happened. The last date on Google Photos backup shows August 18 so it'll be somewhere around that time. I woke up one day to find the phone unresponsive. I thought it ran out of battery overnight since I didn't charge it. Didn't feel like I needed to because I knew it had over 75% battery before I went to bed. One my way to work I tried charging it on my car's wireless charger and the charger indicator LED lights up to show that it's charging, but even after about 15 minutes of charge, it won't boot up at all. I then kept it charged with a proper charger but it never came back on. Tried everything and anything but it won't turn on.

I then plugged it into my PC just to see what will happen and sure enough, the PC detects it but shows the "QUSB_BULK_CID......" name as the device, just like everyone else here.

Before it bricked, I was already running Android 12 beta since it was announced and never had any issues. Everything was running smoothly, even after various beta updates along the way. I don't remember which update I last received before it died though so unfortunately I cannot provide any info on that.

My IMEI number 99001201*******, I can provide the complete number to a Google technician/Engineer separately if necessary. I am also willing to part ways with it if will be substituted for either the same phone or newer. I just need to figure out a way to back up some things in it such as my messages, etc because I was not ready for it to just die out of nowhere. I was hoping that it will at least last until the Pixel 6 come out, but it's really disappointing that it just randomly died. I understand the inherent risk of running beta software, but I also don't expect it to just implode for no reason. I've been beta testing with every single Android release since Ice Cream Sandwich on all my Android phones, and never experienced this before. I hope Google will do the right thing and compensate everyone who's Pixel phone bricked, especially if this has something to do with either an update or patch they pushed.

ro...@gmail.com <ro...@gmail.com> #505Sep 16, 2021 01:32PM

I had the same issue with my phone dying. I had to order a new pixel 4. Because the pixel 3 wouldn't turn on, I couldn't trade in either! Extremely disappointed!

fo...@gmail.com <fo...@gmail.com> #506Sep 16, 2021 02:01PM

Same issue, pixel 3 got stuck in EDL mode overnight and became unusable. Was holding out to the pixel 6, but seems plans have changed.

ro...@gmail.com <ro...@gmail.com> #507Sep 16, 2021 03:20PM

I have a similar issue; my charging port won't work anymore

ro...@gmail.com <ro...@gmail.com> #508Sep 16, 2021 03:22PM

Now I have to use wireless every single time and this is getting to be really frustrating. I hope this didn't/doesn't happen with any other pixel :/

ia...@cazabat.com <ia...@cazabat.com> #509Sep 16, 2021 04:15PM

Comment has been deleted.

Message last modified on Sep 16, 2021 04:17PM

ia...@cazabat.com <ia...@cazabat.com> #510Sep 16, 2021 04:17PM

If charging wirelessly works & the phone boots up, then it's not related to this issue. These phones will no longer turn on & are currently unusable.

aq...@gmail.com <aq...@gmail.com> #511Sep 16, 2021 04:20PM

Has anyone given this guide a try by any chance? It's not for the Pixel per se, but maybe we might get lucky

https://www.droidwin.com/unbrick-oneplus-7t/

st...@gmail.com <st...@gmail.com> #512Sep 16, 2021 09:25PM

Same problem here... We should not allow Google to walk away from this without reimbursing us. This is not a warranty issue, this is an issue they created by sending out faulty updates which damaged our devices. They are 100% at fault.

aa...@gmail.com <aa...@gmail.com> #513Sep 17, 2021 01:52AM

another person with a Pixel 3 being stuck in EDL mode since last night.
You will be all glad to hear that the support person was happy to "apologize for any inconvenience" they tried to do the right thing but then the terms on my return want me to pre-approve $1,199 AUD to be deducted if its decided its not within warranty for the replacement Pixel 3 they would send me out.

Given the frequency of these claims and the age of the phone its a bit rough for them to expect me to trust their process when they don't publicly acknowledge the issue.

oz...@gmail.com <oz...@gmail.com> #514Sep 17, 2021 02:20AM

@#511, that guide explains how to restore a phone that you can get to the bootloader from. For this particular issue, the bootloader is broken so it is stuck in EDL mode.

ms...@gmail.com <ms...@gmail.com> #515Sep 17, 2021 08:52AM

Same case here, my Pixel 3 died (July) on my own hands after restarting it. It got stuck on loading a Google Chrome website and died. Google gently offered a refurbished unit for 400 euros ;)

mi...@gmail.com <mi...@gmail.com> #516Sep 17, 2021 10:45AM

Same issue for me. I have owned a Pixel 3 since shortly after launch. In mid August, the phone bricked itself overnight. I could plug it into my computer and my computer would recognize it but every feature of the phone was not functional.

At the time, I was not aware of the EDL issue going on, so I brought it to a uBreakIFixIt store. They did some diagnostics (battery replacement, etc) and could not determine what the issue was with the phone. I now know it is the EDL issue.

da...@gmail.com <da...@gmail.com> #517Sep 17, 2021 11:25AM

Same problem with my Pixel 4, which is out of warranty. Just woke up one morning and it was bricked. None of the suggested attempts to fix it work.

ca...@gmail.com <ca...@gmail.com> #518Sep 17, 2021 02:40PM

9/17/2021 Went to bed and my phone was working fine. Woke up and it was black screen. Dialed it my wife's Pixel 3 still working and it went straight to voicemail. It wasn't that low on battery so it should have been on still even if it wasn't charging as I go to battery save at 50% and never see my phone get to 0 before putting it on a charger.

I recently got a security update I installed 3-4 days ago. I have tried to use the hard reset buttons but nothing comes on the screen ever. I popped out the Sim and tried to turn it on, same thing. Tried different chargers that are all working with my wifes phone and nothing. Seems dead.

Odd thing. Pulled out my wife's old pixel 1 and plugged it in and saw the charging meter come on. Let it charge for a half hour and popped in my sim and turned it on. Now its bricked. Now I am getting conspiratorial. haha

re...@gmail.com <re...@gmail.com> #519Sep 17, 2021 04:43PM

Adding my Pixel 3 XL to this list. Updated to the latest security update. Went to bed with the phone on the pixel stand and woke up in the middle of the night to an error and now will not start up. When plugged into the computer the computer makes the windows sound for a device connecting, but the device doesn't show up in windows explorer. Talked with the local repair shop and she said that she is seeing this on many Pixel 3 and Pixel 3 XL phones. Google support doesn't recognize an EDL issue and just says you have so send it in and pay the $500+ fee to fix it.

hr...@gmail.com <hr...@gmail.com> #520Sep 17, 2021 04:47PM

Adding Pixel 3XL to list as well.

Same result, Went to sleep with Pixel charging, woke up to phone on 1% and recognized charger, but refused to charge. Continuedly cycles in a boot loop before dying from low battery.

Tried multiple chargers, connected to computer, nothing. Tried to opt out of Android 12 but I can't get in my phone to remove it.

ji...@gmail.com <ji...@gmail.com> #521Sep 17, 2021 05:14PM

allegedly level 2 support reached out to engineering and the only resolution offered, like everyone here, is to take it to ubreakifix.
i will be repeatedly asking Google support to get an official position from the engineering team.

I will not take it in to ubreakifix at this time, reasons detailed in my most recent email to them below

====================
Hi [device-support],

I appreciate the follow up, and I understand you currently can only offer solutions your team is allowed to give.

Unfortunately, all instances of users sending phones to ubreakifix on the bug tracker report the same thing: ubreakifix cannot determine the cause of the failure.
Most cases, due to the inability to diagnose why the EDL issue occurs, the recommended resolution is motherboard replacement, which in all practicality is a phone replacement, but at the consumers cost without ever knowing if the fault is hardware or caused by a patch.
Links attached below to the bug tracker with these instances.

Since the engineering team is refusing to make an official statement as to the cause of the EDL issue, I would like to reserve the right to keep this trouble ticket open until an official position or statement is made.
The logic to me is simple, if it is truly a known hardware defect, it would have already been announced, since all of us affected by this issue would be voided of any recourse under expired warranties.

Citing the ubreakifix examples below, I will not send to a repair center for these reasons:
a) the cause is unknown to ubreakifix, and engineering team will not take a position
b) if the solution is to replace the motherboard, any evidence or proof of the EDL status is lost. In the event that Google will voluntarily or is mandated to compensate, I will need the phone to show EDL status to be compensated.
c) like the examples below, I will be asked to pay for repairs or pay for return shipping, without any concise diagnosis

I look forward to staying in touch to learn of the engineering team's response or the media's response.

Regards,
Jim

[links removed, they all reference messages in this tracker above]

bl...@gmail.com <bl...@gmail.com> #522Sep 17, 2021 05:27PM

Hi BXXXXX,

Thank you for your patience.

First, they have advised that our Google Engineers will look at the link you gave and provide a concrete solution on the matter. Second, they have decided to process a one time exception as long as there is no physical damage. Please provide your choice based on the options below. Also, we need your shipping details and consent for us to proceed processing your replacement. Please say YES, if you agree.

We really appreciate your continued patience and cooperation as we work to resolve this situation.

1. Advance Exchange: With Advanced Exchange we’ll provide you with a link to order your replacement device and it will ship to you within 2-7 business days before you need to send your defective device back. This way, you’re not without a phone and you can easily transfer your data from the old device to the new device.
Please note, this option will require an authorization hold (14 business days)on a credit or debit card for the full cost of the device, but once your defective device is returned- the authorization hold is removed from your card.

2. Standard Exchange: You may also opt for Standard return. In Standard exchange, you need to send in the defective device first and once received and inspected, we'll dispatch the replacement order. The complete process may take 5-10 business days.

Complete Name:
Shipping Address:

Phone#:
_____________________________
I chose standard exchange. My phone arrived to Dallas yesterday via prepaid FedEx shipping.
Upon receipt of the replacement Pixel 3 XL I will share my RMA #. I'm not totally convinced Google isn't monitoring this and will hold it against me somehow for sharing my RMA or case ID #.

Stay on them. I got this response only after being told "no" 4 times.

pw...@gmail.com <pw...@gmail.com> #523Sep 17, 2021 11:46PM

I successfully got mine replaced by Google.

sh...@gmail.com <sh...@gmail.com> #524Sep 18, 2021 03:04AM

My phone is soft bricked. I have this going on. It allows me maybe to go to recover and reset. The most important thing is my files. I have heard two ideas to try and get something back. Find the restart button in the upper right by trial and error after you turn back on. Let the battery drain, and then plug it in and hit start within a few minutes.

Has anybody tried these with luck?

thanks for any help. Is my soft brick different than what most are experiencing?

Who needs to arrange the class action suit here. Do it quickly before the Google 6. Google has a huge investment in keeping this quiet.

All the best,

ca...@gmail.com <ca...@gmail.com> #525Sep 18, 2021 03:14AM

Comment has been deleted.

Message last modified on Sep 21, 2021 02:39PM

sh...@gmail.com <sh...@gmail.com> #526Sep 18, 2021 03:30AM

Here is the image:

20210917_182957 (1).jpg

1.9 MB

View

Download

pf...@gmail.com <pf...@gmail.com> Sep 18, 2021 07:23AM

support interaction.txt

4.3 KB

View

Download

sh...@gmail.com <sh...@gmail.com> #527Sep 18, 2021 02:03PM

Peter, thank you for that.

Assuming the worst, here. But I seem to be in a different circumstance than most.

My phone is not completely unresponsive...though it is.

I seem to have the possibility at least of going into rescue, recovery, restart bootloader mode.

Look above at the image. The bar code does get me the bar code, so I assume the other three would move me someplace.

But I don't feel I have the knowledge to move around in there.

Is this what is called a "soft brick?" That there is a possibility of doing something?

Some have said to let the battery drain and then restart and the phone managed to. If I drain fully would there be a new start for fastboot mode, or it would start another way and the boot images would load properly.

Or should I just assume as I have that this is done.

My need is what is on the phone: documents, downloads, texts etc. My wife thinks some of those are at google and when I buy another phone I will get something back. On the other apps, Whatsapp, etc. is it the phone or the cloud where there is storage.

My apologies for the long note, but if somebody can clarify this, I guess I can move on.

Thank you, kindly.

bi...@gmail.com <bi...@gmail.com> #528Sep 18, 2021 03:42PM

Hi Guys,

For those who got the phone replace out of warranty; was it a free replacement?

bl...@gmail.com <bl...@gmail.com> #529Sep 18, 2021 04:10PM

Mine was replaced out of warranty at no cost. It should be here Monday.

bi...@gmail.com <bi...@gmail.com> #530Sep 18, 2021 04:19PM

How'd you go about getting a replacement?

sh...@gmail.com <sh...@gmail.com> #531Sep 18, 2021 08:05PM

Had conversation with Google Fi. They, as yet, have no consideration for us. Have no knowledge of folks who got some accommodation.

bi...@gmail.com <bi...@gmail.com> #532Sep 18, 2021 08:38PM

I got an email stating that since its out of warranty I would have to eat the cost; any suggestions on getting them to replace it?

ka...@gmail.com <ka...@gmail.com> #533Sep 18, 2021 09:34PM

My phone has bit the dust too. This is outrageous.

jo...@gmail.com <jo...@gmail.com> #534Sep 19, 2021 01:54AM

Just happened to my phone also. It shows the Google symbol then fades out almost as if the screen was disconnected. Doesnt work when plugged in either.

jo...@gmail.com <jo...@gmail.com> #535Sep 19, 2021 01:55AM

It might be useful to not update if anyone still hasn't. Copy all the data you need off the phone while you still can. I wasn't able to :/

sh...@gmail.com <sh...@gmail.com> #536Sep 19, 2021 02:21AM

For those who have successfully got a phone out of warranty, which phone is being offered/issued?

When I talked to a tech today, a little light. He showed me that our phones have an auto-back-up. I believe it does not however include all. I was told for instance that texts are saved on the phone. So gone. Not sure what is and isn't. But we should have something.

pw...@gmail.com <pw...@gmail.com> #537Sep 19, 2021 11:20AM

Comment has been deleted.

Message last modified on Sep 21, 2021 05:19PM

pa...@gmail.com <pa...@gmail.com> #538Sep 19, 2021 03:24PM

same here!
Sent it in and they told me it is an issue with power supply and replacement would be >200€. Seems like the service center is not up to date.... PLS FIX!

bi...@gmail.com <bi...@gmail.com> #539Sep 19, 2021 03:45PM

If everyone would please open a case with them so you have document of the case number; hopefully the more people open a case they would take a serious look into this.

bi...@gmail.com <bi...@gmail.com> #540Sep 19, 2021 03:46PM

And for those who got there phone replace out of warranty; if you guys can provide any suggestion or tips on what you did?

bl...@gmail.com <bl...@gmail.com> #541Sep 19, 2021 08:54PM

Your replacement device has shipped, RMA# RMA86582552

Mine was replaced out of warranty as previously stated. Don't give up. Keep calling and don't take no for an answer. Blame them over and over again. Let them know it's 100% their fault and they owe you a replacement phone. That's what I did.

sh...@gmail.com <sh...@gmail.com> #542Sep 19, 2021 10:39PM

And the replacement phone was what? A Pixel 3 with some sort of warranty? Or another phone?

Thank you.

bl...@gmail.com <bl...@gmail.com> #543Sep 19, 2021 10:50PM

Replacement was what I had. Pixel 3 XL 128gb black. Don't think it has a warranty. I'll sell it as soon as I get it most likely.

de...@gmail.com <de...@gmail.com> #544Sep 20, 2021 12:31AM

Add my phone to this long list. Bricked for no reason four days ago. You would think Google would at least acknowledge there is a problem.

ja...@gmail.com <ja...@gmail.com> #545Sep 20, 2021 04:36AM

Just adding mine to the list. I went to sleep last night with a perfectly working Pixel 3xl on the charger. I woke up to a brick! I was confused and frustrated! Now that I found this thread in my search hoping to find a fix, I’m irritated!! This is absolutely crap and it seriously needs some legal ramifications!!

kj...@gmail.com <kj...@gmail.com> #546Sep 20, 2021 06:29AM

Same thing happened to mine! I have a 3 XL which was in mint condition. Charging and all of a sudden screen goes dark. Won't reboot can't get it too do anything...brick! What the hell? I've seen several articles about this happening all over! Can you say class action suit?

sc...@gmail.com <sc...@gmail.com> #547Sep 20, 2021 09:30AM

Hello, I'm just adding my name to this for the class action lawsuit. I work up this morning with a bricked phone. wont start, and reads as QUSB_BULK_CIDXXXXXXXXXX. such a shame google haven't provided more assistance to users who have had this issue.

gp...@gmail.com <gp...@gmail.com> #548Sep 20, 2021 02:07PM

Was listening to music on my Pixel 3XL on September 18 @ 5:35PM EDT and the phone just stopped playing. Looked at the phone and everything was blank and no ability to turn back on.

Plugged into PC and received the same result as all the rest, Unknown device list as QUSB_BULK_CID:0402XXXXXXXXXXXX.

This is the Second Google Pixel I have owned that has just randomly stopped and failed. This is severely disappointing and makes me to never consider a GOOGLE product again. If this CANNOT be resolved, I will ACTIVELY campaign against anyone buying GOOGLE products in the future.

aq...@gmail.com <aq...@gmail.com> #549Sep 20, 2021 02:26PM

Hell all again,

while we all wait for Google to take some kind of general action to resolve this issue, I would like to try and figure out what might have caused our phones to "brick" and end up in EDL mode. At first I thought that it might be a firmware update pushed by Google that caused this. However, as far as I'm aware, a user needs to approve of any firmware update before it can be installed. From what I'm seeing here, there are many users experiencing the phone "bricking" while it's in use, and some waking up to the phone being dead.

I'm starting to lean towards the idea that it might have been some kind of system or core updates (I may be using the wrong terms here) that gets automatically pushed and updated via Google Play. This is the only way I can see that the phone can "brick" while it's the middle of being used, as the phone might receive a pushed update, installs the update, and that resulted in some kind of instruction to reboot and now the phone is stuck in EDL mode.

This is just a thought but might help if we can at least narrow down the cause. I still very much prefer if Google will take the right actions and try to figure out what's going by taking in these bricked phone at their own cost, and either fix them or replace them. If they can fix it and figure out a way to have users fix the issue on their own, I think that will quickly put out the flames.

ja...@gmail.com <ja...@gmail.com> #550Sep 20, 2021 02:30PM

Or the flash storage wears out due intensive writes at a certain location.

fr...@gmail.com <fr...@gmail.com> #551Sep 20, 2021 03:41PM

My Pixel 3 patched to Aug 2021 suddenly went black yesterday while on a call... It was struggling all day with with charging and overheating as I was using it to navigate in it's wireless charger on the dash f my car. I seemed to be unable to charge all day slowly loosing charge ~ 1% . Every 5 minutes. After the screen went black I immediately restarted, and it took ~ 5 minutes longer than normal for my phone's screen to come back to life.

maybe this was a "near-miss" and the circumstances can help google isolate the problem.

jj...@gmail.com <jj...@gmail.com> #552Sep 20, 2021 06:18PM

Replying to

comment #549

My Pixel 3 XL has turned off out of the blue and bricked while I was using it in the car with Google Maps and Spotify running. I had all Google Play automatic updates turned off - it needed my manual action to update an app. So with that - my phone couldn't be bricked with Google Play automatic update. We probably need to look somewhere else :(

jc...@gmail.com <jc...@gmail.com> #553Sep 20, 2021 08:18PM

https://www.iphoneincanada.ca/news/google-pixel-3-brick/
Per the above linked article "Google confirms crashing issue" but then also "said it has 'nothing else to share' for now." :(

ja...@gmail.com <ja...@gmail.com> #554Sep 20, 2021 08:49PM

I experienced the same issue as everyone else here. Bottom line, do not give up. Keep pressing Google for solutions. Sounds like this is headed for a class action. Right now they are offering replacement phones, yet who wants the same crappy Pixel 3 that's just going to end up bricking again?? Google needs to make this right with the mass amount of users negatively effected by this.

th...@gmail.com <th...@gmail.com> #555Sep 20, 2021 09:26PM

Mine bricked as well last night. Pixel 3.

c....@gmail.com <c....@gmail.com> #556Sep 20, 2021 11:20PM

3xl here, bricked just a couple of hours ago. After the whole Nexus thing some years ago I wont buy anything Google ever again. Just in time for the i13 too.

t....@gmail.com <t....@gmail.com> #557Sep 21, 2021 02:33AM

yep same here, 3xl bricked over night

se...@gmail.com <se...@gmail.com> #558Sep 21, 2021 09:59AM

I have a Pixel 3XL and I just woke up to a black screen and phone not responsive. Battery was below 30% last night when I went to bed. Trying some troubleshooting steps but so far, no luck.

jr...@gmail.com <jr...@gmail.com> #559Sep 21, 2021 02:52PM

My wife's 3XL is currently experiencing the same issues here and gives the EDL popup if you plug it into a computer. This is BS and something needs to be done about it by Google.

pw...@gmail.com <pw...@gmail.com> #560Sep 21, 2021 05:25PM

I experienced the same QUSB_BULK_CID bricking over the weekend. I have reported the problem with the Case ID 7-7225000032008

Please help report this issue by clicking on “Contact Us” in the bottom of this page:

https://goo.gle/2Eqys1z and share your Case ID here.

ca...@gmail.com <ca...@gmail.com> #561Sep 21, 2021 05:52PM

Comment has been deleted.

Message last modified on Sep 21, 2021 05:53PM

ca...@gmail.com <ca...@gmail.com> #562Sep 21, 2021 05:53PM

CaseID 4-6371000031454 created.

ra...@gmail.com <ra...@gmail.com> #563Sep 21, 2021 06:03PM

ID 3-3762000031403 just created mine

bi...@gmail.com <bi...@gmail.com> #564Sep 21, 2021 06:26PM

ID 3-7420000031989

na...@gmail.com <na...@gmail.com> #565Sep 21, 2021 07:37PM

Case ID [8-5721000031932]

I have a suspicion that those that are getting RMAs are from places with stronger consumer laws. Where support knows, those with weak consumer laws have no leverage and can be brushed off. My suggestion is just constantly harassing support but who knows what good that is.

As for the actual support experience. Good god it is awful. The amount of emails where I've asked direct questions that were subsequently ignored is astounding. Seems the plan of action within the support team is stone wall users. Has anyone here had any luck getting through to support.

For those who managed to get a phone call from support, how did you go about this and where are located?

bl...@gmail.com <bl...@gmail.com> #566Sep 21, 2021 07:42PM

I'm in Louisiana, US. We don't have particularly tough consumer laws. Weak if anything.

I did threaten to sue, but it didn't seem to affect them. They basically said "yea you can do that if you want".

I got a call by sending them an email and basically stating, I demand that you call me regarding this issue.

es...@gmail.com <es...@gmail.com> #567Sep 21, 2021 08:09PM

Tried again to no luck, support obviously answering from a script, some parts were word for word the same as my last conversation with them. Really sucks, because now I don't want to get another Pixel Phone and I really loved them.

I hope iPhones are better than I remember

bi...@gmail.com <bi...@gmail.com> #568Sep 21, 2021 08:20PM

To reach Google Pixel Customer Support
- From your Pixel phone: Go to Settings -> Tips & Support -> Contact Us,
you can ask for a call back
- From the web:

https://support.google.com/pixelphone/gethelp. They will
usually call you within a few minutes
- You can also call them directly at 855-836-1987
- If you are a Google One subscriber, request help from the Google One app
for priority support

I tried again yesterday and got the same out of warranty BS as usual, and
was told that legal action is an option if I choose. I did get an
escalation but they were busy and never did call me back. Several hours
later I got an email:

Your Google Support Inquiry: Case ID [4-7420000031742]

Thanks for contacting Google Support!

This is Adam, Pixel Support Supervisor.

I hope you are doing great. This is regarding your case about your device
not turning on. I understand that all troubleshooting were performed
already. Please be advised that the device warranty is already expired. Our
best option here is repair. Now, I understand that you don´t want to pay
for the repair fee. Unfortunately, we can no longer cover the repair fee
since warranty is up. I hope you understand that we did handle this case in
accordance to our policy.

Thanks!
Adam
The Google Support Team

I am trying to get this covered by the local news station here in the bay
area, in Google's back yard. Class actions never really benefit the consumer

On Tue, Sep 21, 2021 at 12:42 PM <buganizer-system@google.com> wrote:

- Show quoted text -

ca...@gmail.com <ca...@gmail.com> #569Sep 21, 2021 09:11PM

Your right that Class actions don't benefit consumers, attorneys are the only ones with a sizable chunk of the settlement.

I got a bit further by getting escalation support. I googled "pixel 3 emd" and copy and pasted every android/pixel web site on the first page covering this expanding issue. I let them know this is a growing issue that is going to swallow them if they don't pay attention. I reminded them of the Iphone battery issue where they pushed software that "broke" iphones and how that tarnished Apple's image for quite some time.

The escalation support said he is escalating it further. They gave me their contact in email and said they will keep me up to date.

I did see in this blog of the many I posted to them, Google has responded to them saying they are looking into it.

https://www.iphoneincanada.ca/news/google-pixel-3-brick/

They may just blow me off tomorrow, who knows.

ba...@gmail.com <ba...@gmail.com> #570Sep 21, 2021 09:12PM

I have the same problem, My ChatID is 6-1993000031909, although I did not get a caseID.

sh...@gmail.com <sh...@gmail.com> #571Sep 21, 2021 09:45PM

Just had a thought here and checked it.

Minimum update & support periods
Phone No guaranteed Android version updates after No guaranteed security updates after
Pixel 3 October 2021
October 2021
Is this part of the mix - for Google - at how they are reacting?

It still boggles the mind. I was planning to buy the Pixel 6 Pro, and I bet a considerable number here were thinking the same. I don't understand with the launch of 6, why Google is infuriating the 3s by their lack of response and action?
.

aa...@gmail.com <aa...@gmail.com> #572Sep 21, 2021 10:05PM

This happened to my Pixel 1XL as well.

My 3XL bricked, so turned to the 1XL to use as a backup, only to have the same issue happen a couple days later.

I've spent hours chatting with Google and they only option they've given me after escalation is to send the phone in with a quote of $400 to repair. They make you put in a card to charge that amount should the repairs be needed.

se...@gmail.com <se...@gmail.com> #573Sep 21, 2021 10:29PM

My google chat ID from earlier today is ID 7-0861000031721. They told me I can send it in or take it to the authorized repair center, but there would be a fee associated with it. So disappointing as there is a bigger issue happening here that isn't a hardware issue. I was ready to buy the Pixel 6 Pro next month but rethinking this since Google won't confirm there is an issue here that is growing in size due to either a software/update bug or a defective hardware that may be wearing out since there has been no physical issue/damage/drop I can even associate with this issue since I just plugged my phone into my Google charger as I do every other night and it was in good working order. Considering going with a Samsung or the new Surface Duo 2 depending on Microsoft's announcement on Wednesday. Just disappointing since Google has done the right thing on previous Pixel models as I have been a customer on when an issue like this comes up. Hopefully they will do the same as the Pixel 6 is released and will allow us to trade in our problemed Pixel devices with a discount.

ga...@ghart.com <ga...@ghart.com> #574Sep 21, 2021 10:33PM

Yup, another case here. Completely blank screen but shows up in Device Manager as QUSB_BULK_CID:0402_SN:xxxxxxxx

I chatted with a Google rep; I was polite but very insistent. They just kept coming back with "We do value your loyalty. As the device is out of warranty and the device is not enrolled into device protection, there are no options available to replace or repair." They also refused to escalate the case (8-9575000031738).

ci...@gmail.com <ci...@gmail.com> #575Sep 21, 2021 10:34PM

This is my case id way back from December 2020 [8-6394000031057]. They were asking to send it in for repairs and that they will inform the charges to me. I didn't because I knew they will charge me some insane amount which I will anyways refuse.

za...@gmail.com <za...@gmail.com> #576Sep 21, 2021 11:21PM

So I'm actually the person who first filed this bug report, but I figured I would detail my experience a bit in case anyone is feeling hopeful that persistence will pay off.

The first time I reached out, they told me that my device was out of warranty, but "You can get the device repaired at our Google repair partner" which is UbreakiFix. I ended up taking it to UbreakiFix, and they told me they had no way of talking to a phone that doesn't turn on. They could try replacing the screen to see if it was a hardware issue, but they doubted it would work. After doing a good bit of research, starting this thread, and eventually coming to the conclusion that I'm out of luck until they release the firehose files, I reached out again, mainly to see if I would get lucky and they would forward it along to the correct engineering team. I was told they were aware of the issue, but there was nothing else they could say about it at this time.

Then I shared one of the articles on reddit, and I commented about how it happened to me, and I got this DM from one of the google support staff:

I work for the Pixel Community team and saw your post about your Pixel 3 not turning on. We’d like to investigate this further. If you’ve already contacted customer support, can you please share your case ID (will look like this x-xxxxxxxxxxxxx) so I can escalate this issue to the appropriate team?

So I reached back out, assuming this means they are interested in investigating further and hopefully finding the root cause of the issue. This made it even more frustrating when I got the same canned response:

I've checked the details of the IMEI number and noticed that the device is out of warranty. However, not to worry, you can create a repair order either online or in person at a repair location. We've 2 types of repair options

I exchange ~10 emails with the person until they stopped responding to me, detailing how the warranty status is irrelevant when the issue is one caused by an OTA update, not one that would lead to a warranty repair; and the repair is a minimum of $411 even though a refurbished phone is available directly from Google for $250. They insisted that the issue could not be escalated any higher, and "The best possible option in this case is to get the device repaired."

So I'm not sure why they reached back out to me, but I do know that there is no way I'm buying another pixel device until they show that they are willing to stand behind their hardware and provide the support required. It's definitely frustrating, but I do still wish everyone the best of luck in getting a customer service representative who is actually trying to solve problems instead of copy and paste links to their repair page.

jo...@gmail.com <jo...@gmail.com> #577Sep 22, 2021 12:12AM

Add mine to the list. Pixel 3xl. Bricked in the middle of work at 80% battery. All of my work email apps and MFA apps were rendered useless. Customer service gave me the same canned response of "Send it in to get fixed because it's out of warranty". I mentioned several tech sites (Techradar, etc.) that had stories on this issue. The rep then said that she would speak with the engineering team and would get back to me in 5 minutes... 3 minutes later, the chat was closed. My case ID is ID-2-5272000031881. I'll echo #596 "there is no way I'm buying another pixel device until they show that they are willing to stand behind their hardware and provide the support required". Make it right!

je...@gmail.com <je...@gmail.com> #578Sep 22, 2021 12:46AM

Happened to my Pixel 3 last night, too. Worked yesterday, plugged it in to charge overnight, and per the Find My Phone, it shut down at 3am. Couldn't get it back up and took it to a repair shop where it was deemed unrepairable. Support chat at Google told me the same things it's telling everyone else - out of warranty, have it repaired at UBreakIfix (which after a call with them and describing the QUSB_BULK thing to them, they deemed it unrepairable), nothing they can do, etc.

ta...@gmail.com <ta...@gmail.com> #579Sep 22, 2021 02:24AM

I find it ironic that we're now using our Nexus 6 (a 7 year old device!) because our Pixel 3XL (a 3 year old device) failed with this QUSB_BULK_CID error by no fault of our own.

This is not an issue that should be handled under warranty, but instead handled under the common sense principle that many people (myself included) will never invest in a phone from a company that won't fix an issue that is clearly related to either elapsed time or a flawed update. The fact that so many people are experiencing this issue in such a small window of time is significant.

I want a replacement, or the value of a replacement device applied to a new model.

na...@gmail.com <na...@gmail.com> #580Sep 22, 2021 05:19AM

Adding myself to the list as well with a 3XL. About 2 months ago, the phone randomly went into a reboot loop for half a day, managed to somehow get it out of it and it worked perfectly for a few days. Then, similar to just about everyone here, I plugged my phone in as I went to bed and while putting my son back to bed at 3:04 AM (I checked my phone and saw what time it was), I then checked again in the morning (around 6am) and the phone wouldn't turn on. Everything I've tried (volume buttons + power button, etc) doesn't work and plugging it into my computer I receive a similar message: QUSB_BULK_CID:XXXX_SN:XXXXXXXX.
So incredibly frustrating.

in...@gmail.com <in...@gmail.com> #581Sep 22, 2021 07:15AM

Add My device to the list, What are you doing Google? Is this was the company that we are trusting? I don't think we need to leave this simply. We have the right to use our Hardware and Software after the purchase of the smartphone. We can use it for Decades there shouldn't be any problem. How can they do this? This was Just Google's Fault. They might have pushed an update and it might be an irreversible one so From September 5th to 23rd many devices getting Bricked . If anyone is ready let's protest this issue on Twitter With "#pixel3brickedbygoogle" "#suchashamebygoogle" . Let's Do this guys

an...@gmail.com <an...@gmail.com> #582Sep 22, 2021 08:20AM

I also have a hard brick problem. During the installation of the Android 12 beta the phone froze. Google did not suggest doing OEM unlock and unlocking the bootloader. Result? It's been four months since I opened buganizer reports and I only receive random responses (update the system, access fastboot etc.).

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

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

pw...@gmail.com <pw...@gmail.com> #583Sep 22, 2021 08:28AM

If you want to push the #BrickedbyGoogle on social media. I have made an image here. Let's get the company attention so the issue won't be ignored any longer.

https://pbs.twimg.com/media/E_4CTeoVQAEeeb3?format=jpg&name=4096x4096

tr...@gmail.com <tr...@gmail.com> #584Sep 22, 2021 01:45PM

Add my device to this list please. I woke up this morning to an update notification, something about 'what google apps can do for you.' I swiped and cleared the notification and got ready for work. An hour later I picked my phone up and the screen was black and unresponsive. I tried to ring the phone through my google account, nothing.
What if I had an emergency????
I was raised to take care of my things, this phone has not been dropped or been exposed to water. This is not my fault, and I need this corrected.

bi...@gmail.com <bi...@gmail.com> #585Sep 22, 2021 02:21PM

Status Update: I got an email from google support after many tries on getting replace and they are going to replace it for free.

So my suggestion to everyone is: Open a case with them and keep telling them this is a KNOWN ISSUE; they will push back and tell you that your phone is out of warranty; but keep telling them to escalate the ticket.

Hope this helps ya'll. I'm not sure if I can trust google anymore; but there camera is awesome.

Maybe I'll give oneplus a try; since they don't bloat ware there phones and reasonably price.

xe...@gmail.com <xe...@gmail.com> #586Sep 22, 2021 03:48PM

Same here. Lost all data when phone bricked. Ubreakifix could do nothing.
Sad, was waiting for the Pixel 6 but now will look into other phones

pc...@gmail.com <pc...@gmail.com> #587Sep 22, 2021 03:48PM

My Pixel 3 XL also has been bricked by the update.
I have been going to and fro google support for 2 months now on and off and they are still refusing to sort this out as it's "out of warranty".
I miss my 3 XL :(

re...@gmail.com <re...@gmail.com> #588Sep 22, 2021 03:52PM

Le mer. 22 sept. 2021, 16:48, <buganizer-system+190602+192008282@google.com>
a écrit :

- Show quoted text -

fi...@gmail.com <fi...@gmail.com> #589Sep 22, 2021 04:10PM

My Pixel 3 bricked today, if I remember correctly, there was a recent update a few days ago.
Died out of nowhere, never dropped the phone and it was working just fine before it just turned off and is apparently in EDL mode showing up as QUSB_BULK_CID on my PC.

Phone is about 3 years old, and I'm in Europe so apparently I can't talk to Google support - they won't call me and I can find zero options of contacting them from here.

k....@gmail.com <k....@gmail.com> #590Sep 22, 2021 04:12PM

+1. when is the class action?

da...@gmail.com <da...@gmail.com> #591Sep 22, 2021 05:10PM

happened to me 3 days ago, nothing helps!
loved my pixel 3. Its so annoying!!!

aq...@gmail.com <aq...@gmail.com> #592Sep 22, 2021 08:19PM

I'm still going back and forth with Google's level 2 tech support, who's insisting that I ship the system to UBIF to get it "fixed", despite me explaining that we all know they cannot fix the issue at hand. I also am not willing to pay around $400 for the repair process, which you're required to pay when submitting the repair request, especially for something that I didn't do.

As someone above mentioned, everyone here with the same issues we're all having, please make sure to take some time to open a ticket with them, so they will have more records of the issue. I don't necessarily think they're keeping track of the number of cases based on people's posts here, so if you want the situation eventually resolved, do your part and open your ticket.

To open a ticket, go to

https://support.google.com/pixelphone/gethelp and follow the steps there. Make sure you chat or speak with a representative. Also make sure you don't accept a "Oh it's out of warranty, you're out of luck" and "please send the phone to UBreakIFix and since it's out of warranty, you need to pay for repairs" statement. Keep pressuring them for a fair and just resolution by Google, and keep escalating the ticket up the chain. Level 1 and 2 might not be able to give you the answer you want, but eventually someone will.

bl...@gmail.com <bl...@gmail.com> #593Sep 22, 2021 08:56PM

Find a UBIF that is a corporate owned store. Call them and explain the situation. Let them know that their policy states "free diagnostics" for any phone whether in or out of warranty. They will look at it for free. You don't have to pay shipping or even return shipping.

I ended up not having to send mine off because Google RMAd mine. But I had the shipping label printed and had already spoke with UBIF. The main thing is to find a corporate location and not an independently owned UBIF.

bi...@gmail.com <bi...@gmail.com> #594Sep 22, 2021 09:49PM

#593 UBIF still charged me $15 for return shipping after they did their
free inspection. I had denied the $400+tax motherboard replacement, so I
guess the free shipping is only if you pay them to service your phone.

On Wed, Sep 22, 2021 at 1:56 PM <buganizer-system@google.com> wrote:

- Show quoted text -

pe...@gmail.com <pe...@gmail.com> #595Sep 22, 2021 10:53PM

I raised my case (ID [0-3507000032150]) with Google support (I'm in Australia) and they were pretty dismissive as I am out of warranty by a few months. An interesting comment he dropped in the conversation was something along the lines of "Google has the best support so I will try to help you". He said there were no known outstanding issues with the Pixel 3 so I referred him to this issue tracker and this is the response I got back: (which basically says they have their heads in the sand on this issue)

Thank you for contacting Google Support.
I have discussed this case with my concerned team and would like to let you know that we only consider the emerging issue which are listed under our internal trix and this is not an ongoing issue with Pixel 3.
I would request you to get in touch with the CTDI which is our official repair partner.
If you have additional questions, feel free to reply to this email or initiate a chat/phone with our support team.

oz...@gmail.com <oz...@gmail.com> #596Sep 22, 2021 11:38PM

Update on mine (in Australia) - the store I bought it from (JB Hi-Fi) were very helpful and sent the phone off to the official repairer on their own dime (huge props to them, this is not their issue and they are still helping). Came back with a diagnosis of "not a screen fault, so probably main board". The repairer offered me an option of a refurbished phone for $360 (which is more expensive than a new one off eBay), which I politely declined.

So now I have the phone back. The options I really have are (1) taking them to court - would cost me about $150 and a ton of time to go through small claims with a fairly slim chance of anything happening given any definitive analysis can only be done by Google themselves (we need right to repair laws); and (2) write a complaint to the ACCC, which may get legs if enough other Aussies do the same thing.

As I've said before, I'm done with Google hardware. I'm done with recommending it, and I'm now fairly vocal in my opinions against it.

mu...@gmail.com <mu...@gmail.com> #597Sep 23, 2021 12:12AM

also effecting me in NZ, pretty sure I'm stuffed as I bought this overseas. Really disappointing from a company like google to not acknowledge this.

lc...@gmail.com <lc...@gmail.com> #598Sep 23, 2021 12:48AM

I was able to get an out of warranty replacement.
Here's what it took, it took 30+ emails and I was relentless on social media (Facebook and Twitter, posted about it on every post they made, every ad). I would not take no for answer . Each time they said no, I told them to escalate me to the next person.

tv...@gmail.com <tv...@gmail.com> #599Sep 23, 2021 03:19AM

Bricked Pixel 3XL here. Happened around May 15,2021. Perfectly good and working stock phone. Was listening to music on the morning on a full charge, suddenly music stores and phone is off and wont turn back on. Beyond frustrating.

sh...@gmail.com <sh...@gmail.com> #600Sep 23, 2021 03:39AM

lc...@gmail.com

Curious what sort of guarantee they gave you onthe replacement phone? Since they aren't acknowledging the cause, how are they guaranteeing that it will not happen again? Or if they can guarantee it, then they know exactly the cause and repaired it on the replacement phones. Curious and curiouser.

ni...@gmail.com <ni...@gmail.com> #601Sep 23, 2021 03:43AM

This happened to me as well with my Pixel 3 XL. It occured overnight June 26 2021. Thought the battery was dead but it wouldn't charge. Same messaging as others when plugged into a computer. :(

bi...@gmail.com <bi...@gmail.com> #602Sep 23, 2021 09:00AM

My response to Google support:

---

Thank you for your response, however unsatisfactory it may be.

I understand that the device is no longer under warranty, however this is
not a one off case, or any doing of my own cause. The device has never been
dropped, has never been exposed to water, has no screen damage, or any
other physical damage, and has a perfectly working battery. It has never
been rooted, or had the device bootloader unlocked for any reason.

A manufacturing defect has caused the device too reboot into EDL mode. It
is effectively hard bricked and unrecoverable without the appropriate
firehose files, which are not made available to the public, or even to
Google authorized repair centers.

This defect has already affected thousands of Pixel devices worldwide, with
more falling victim every day. Predominately the Pixel 3 and Pixel 3 XL,
but all current Pixel devices are at risk. The issue is known by, and has
been acknowledged by Google, without a viable fix available. The issue is
reported on the Google Issue Tracker and has been covered by most major
tech sites around the world. There are class action suits being formed
against Google as a result.

The only "fix" is to replace the motherboard at the owners expense, which
is $400+tax, more than a refurbished Pixel 3, or other competing devices,
even from Google themselves. Replacing the motherboard is only a temporary
fix, as the new motherboard could be bricked shortly later as well.

I have already taken my device to uBreakIfix, and was given the assessment
that the motherboard needs replaced. I have also verified that the device
is stuck in EDL mode as lsusb reports QUSB_BULK_CID.

I am aware that many Pixel owners affected by this issue have been issued
at an out of warranty replacement. I am giving you, and Google, this one
exclusive opportunity to make the situation correct by offering an out of
warranty exchange, or full trade-in value on a new Pixel device, before
having to be forced into litigation.

---

I'm sure it will get be nowhere, but I'll let you know if and how's they
respond. Feel free to use it as a template for your own communications.

On Wed, Sep 22, 2021, 8:43 PM <buganizer-system@google.com> wrote:

- Show quoted text -

ja...@gmail.com <ja...@gmail.com> #603Sep 23, 2021 11:56AM

Add my Case ID: 7-0225000032189
Going to UBreakIFix later for supposedly free diagnostics. That way they can tell me the same thing they are telling everyone else, there’s nothing we can do!

lk...@gmail.com <lk...@gmail.com> #604Sep 23, 2021 12:46PM

Case ID [6-2971000031139]

With the number of users experiencing the same issue, it is unethical for Google to completely ignore the issue and to keep giving people the same lame responses. I am sure the customer support staff members are embarrassed about having to send those lame responses, but they have their instructions from their management. It is time to switch back to iPhone. BTW there are great deals on iPhone 13!

mj...@gmail.com <mj...@gmail.com> #605Sep 23, 2021 02:22PM

Just adding my incident to this thread. On 9/17/2021 was listening to a podcast while running with around 70% battery, and the phone turned off. No warning or anything. The phone hasn't been dropped or exposed to water. It won't turn on or respond to anything. Plugging the device into my computer and viewing the device manager shows the device is in EDL mode because QUSB_BULK_CID is present. Contacted Google support, informed them the phone was bricked and that there are many reported cases of the problem, but I was told to take it to UBreakIt or spend roughly $350 to send it to Google for repair.

The phone was purchased from the Google store and out of warranty.

yu...@invitae.com <yu...@invitae.com> #606Sep 23, 2021 03:16PM

Just happened to me too. Woke up this morning (9/23/21) to a dead and completely unresponsive phone.

Message last modified on Sep 23, 2021 03:46PM

bv...@gmail.com <bv...@gmail.com> #607Sep 23, 2021 03:21PM

Me too

br...@gmail.com <br...@gmail.com> #608Sep 23, 2021 03:59PM

same issue for me and my 3xl. completely bricked, same error

by...@gmail.com <by...@gmail.com> #609Sep 23, 2021 04:57PM

Also went to bed with about 30% battery and charging. Phone was working fine. Woke up at 6 on 9/23, phone was still plugged in and bricked. Tried multiple chargers and cables with no luck. Tried combinations of buttons for over 30 seconds each, also nothing. Shows up in device manager as QUSB_BULK_CID...

ma...@gmail.com <ma...@gmail.com> #610Sep 23, 2021 05:40PM

This exact thing happened to me with my Pixel 3XL back in late July. Never had an issue before this with the phone since owning it in Jan of 2019. Did a security update on Android 12 beta, then a few weeks later it bricked. I took it in to UbreakIFix to see what was wrong, but they had no idea what happened. Found this thread and saw that everyone had just about the same issues I had, down to the phone being recognized as QUSB_BULK_CID issue. I'd love to see if this could get resolved because I loved that phone.

jj...@gmail.com <jj...@gmail.com> #611Sep 23, 2021 06:01PM

This just happened to me this week. Morning alarm went off, I turned it off and then 15 mins later picked up the phone to browse, but just a black screen. Nothing happens when power button is held. Searched and came across this issue and confirmed it shows up in device manager as QUSB_BULK... etc. Very disappointed this failure mode exists and Google has no method of repair.

sh...@gmail.com <sh...@gmail.com> #612Sep 23, 2021 06:43PM

Pixel 3xl that is about 2 1/2 years turned into "brick" few days ago at the middle of the night ; connecting it to a computer shows “QUSB_BULK_CID:xxxx_SN:xxxxxxxx”.
So its looks like an EDL mode
Google support and chat just tell you to go to a repair shop...and the repair shop say its dead.

an...@gmail.com <an...@gmail.com> #613Sep 23, 2021 07:37PM

I've contacted support and been told they are unaware of an issue. This is ridiculous. I've started tweeting at them and Consumer Reports, maybe if we keep adding public pressure they won't be able to sweep this under the rug and we can get a solution.

mi...@gmail.com <mi...@gmail.com> #614Sep 23, 2021 07:41PM

This is so back and forth, they say it's a known issue and I've even seen a
site that indicates they are doing some replacements. But they apply site
Reddit and probably this thread...

On Thu., Sep. 23, 2021, 1:37 p.m. , <buganizer-system@google.com> wrote:

- Show quoted text -

ja...@gmail.com <ja...@gmail.com> #615Sep 23, 2021 09:38PM

Just went through this issue with my Pixel 3XL. Did all the troubleshooting, took it to the ubreakifix people and they were unable to fix it. “QUSB_BULK_CID:xxxx_SN:xxxxxxxx” when plugged into the computer. I can hear the sound notification from the PC when I press power and volume down on the phone indicating the phone disconnected and reconnected to the PC.

le...@gmail.com <le...@gmail.com> #616Sep 23, 2021 10:37PM

Tried to avoid installing this borked update by disabling automatic updates in the developer options, but it's now nagging to reboot, suggesting that it's already downloaded the bad OTA anyway. How can I fully block this OTA from installing if I, for whatever reason, have to restart the phone?

oz...@gmail.com <oz...@gmail.com> #617Sep 23, 2021 10:46PM

@#616: There's no evidence any specific OTA is bad, or even if it's caused by OTA at all. To me, it looks much more like the flash memory not being properly wear levelled and dying prematurely (or given the timing as just out of warranty, maybe not prematurely at all).

wa...@gmail.com <wa...@gmail.com> #618Sep 24, 2021 06:43AM

Pixel 3 xl
Phone was on a wired charger overnight while sleeping.
Android 12 beta

he...@gmail.com <he...@gmail.com> #619Sep 24, 2021 09:20AM

Replying to my

comment #142

on Aug 31 - So many comments and bricked phones just in the last 4 weeks!!!

So... I got a replacement Pixel 3 XL through the RMA process. I'm from Australia so I used the Australian Consumer Law as part of my argument (sorry everyone else...). If you're from Australia (i.e. #595 & #596), you can try to escalate and send them the following written email listing out:

1. Purchase history (where, when and how much)
2. Description of the issue, steps taken to troubleshoot and repair and/or examples of the issue occurring elsewhere
3. What your expected outcome should be
4. Set a reasonable timeframe to resolve or reply

The Vic Consumer website has a good overview of the process and template letters to send:

https://www.consumer.vic.gov.au/contact-us/resolve-your-problem-or-complaint/write-to-the-people-involved

The following is what I sent to them:

--------------------------------------------------------

This is a technical software issue which should be covered under the Australian Consumer Law.
The product was purchased on X from the online Australian Google Store at a cost of $X.
See attached the receipt.

The phone was working on the night of X but was not working on the morning of X.
I have tried all the troubleshooting steps as mentioned in the chat support (X -> add chat ref no., dates etc.) , which included the following:
Holding the power button for 30 seconds
Charging the phone (both wired and wirelessly, and using the original charger)
These steps did not resolve the issue.
When I was looking into the problem, I connected the phone into my laptop. The device was showing up as a 'QUSB-BULK-CID' device (see attached).
Through searching online, it seems that this problem I'm encountering is occurring on phones across the world as seen in users evidence posted on multiple websites:

https://support.google.com/pixelphone/thread/113517096/pixel-3-xl-bricked-overnight-computer-recognizes-as-qusb-bulk-cid-likely-caused-by-security-update?hl=en

https://support.google.com/pixelphone/thread/120215795/google-pixel-3xl-black-screen?hl=en

https://issuetracker.google.com/issues/192008282?pli=1

https://forum.xda-developers.com/t/fix-pixel-3-qusb_bulk_cid-xxxx_sn-xxxxxxxx.4205331/

https://www.reddit.com/r/GooglePixel/comments/mmbcx9/pretty_sure_overnight_update_bricked_my_pixel_3xl/

https://www.reddit.com/r/GooglePixel/comments/mmcn93/my_pixel_3_xl_bricked_overnight/

https://www.reddit.com/r/GooglePixel/comments/n06miw/got_the_pixel_3_qusb_bulk_cid_brick_issue_today_i/

https://www.androidpolice.com/2021/08/31/pixel-3-and-3-xl-phones-are-getting-stuck-in-edl-mode-and-seemingly-bricked/

While the phone has minor physical damage from wear and tear, such as small scratches and minor screen cracks (see attached photo), these did not cause the issue where the phone has completely stopped working due to total software failure.
It is unreasonable that the phone will stop working due to a software issue only after 2 years, whereas phone plans are available for up to 3 years.

I am within my rights to request a replacement or repair of the faulty product either by Google, or full compensation if I have to pay for the repairs myself. I would appreciate this matter being resolved within the next 10 business days.

If I do not hear from you within 10 business days, I will forward my complaint to Consumer Affairs Victoria for further advice.

--------------------------------------------------------
They sent the following reply, which I think is absolutely disgraceful:
--------------------------------------------------------

Appreciate your patience while we were working on this. I have got an update from our internal team and happy to inform you that exception to replace the device has been approved.

--------------------------------------------------------
I really hope this helps someone... I've pretty peeved off (even if I did get a replacement) with Google on how they treat us and handle this situation. The fact they had to make an 'exception' really makes it seem like Google hopes this is swept under the rug and will not admit fault at all.

oz...@gmail.com <oz...@gmail.com> #620Sep 24, 2021 09:50AM

@#619 - Yep this is exactly the tack I'm progressing with, except I'm going to JB Hi-Fi as the original seller, as required. Sucks for them because it's really Google's fault. :/

ra...@gmail.com <ra...@gmail.com> #621Sep 24, 2021 10:37AM

Same issue for me.

fi...@gmail.com <fi...@gmail.com> #622Sep 24, 2021 11:22AM

Same happened with me on my pixel 2xl. Only black screen. That won't turn on, won't charge, won't get into recovery mode, and gets recognized as QUSB_BULK when connected to a pc.

ni...@gmail.com <ni...@gmail.com> #623Sep 24, 2021 12:22PM

Let's add me to the list. Phone worked fine last night, woke up and it was bricked 100%. Can't do factory reset, can't do anything.

go...@gmail.com <go...@gmail.com> #624Sep 24, 2021 12:23PM

same here. where is the response?!

ga...@ghart.com <ga...@ghart.com> #625Sep 24, 2021 12:31PM

When you guys add your "me too", don't forget to click the star at the top

[Deleted User] <[Deleted User]> #626Sep 24, 2021 05:41PM

Comment has been deleted.

Message last modified on Sep 24, 2021 05:42PM

pv...@gmail.com <pv...@gmail.com> #627Sep 24, 2021 05:43PM

Same issue here. Guessing there was an update last night.

dk...@gmail.com <dk...@gmail.com> #628Sep 24, 2021 08:07PM

Same issue here, happened last night after midnight.

sh...@gmail.com <sh...@gmail.com> #629Sep 25, 2021 12:26AM

I can't count the number of times and cases that I have established on this to get Google Fi, Google's own service, to pay attention to this and get me and all of us the replacements we are entitled to. Google is fully responsible for the destruction of our phones. It is frankly embarrrassing how Google, the company, disrespects their front line people having them parrot empty notions that we are not under warranty, and that we should waste our time going to ubreakitIfix and even some attempt to say they never heard of this issue.
I have been waiting for a promised supervisor to call me back for days now. No responsibilty. No respect. In the end no professionalism.
I needed a phone so even though I am expecting consideration from Google, I bought an interim phone and paid for expedited shipping. The phone didn't arrive in the expected period which Google deemed. We had to phone FEDEX. Although we paid for expedited, Google delivered it as standard. I will repeat that. Although we were charged for expedited shipping, Google Fi delivered it as standard. Then I wasted more time with a Google Fi rep who told me: "Want to be honest with you, to not to set proper expetations beyond the power of control."
Or in his case, no control and an hour wasted. The phone is actually in my city and there are hours left for delivery from FedEx today. But they will not even take off the expedited fee, and I will have to after the late
delivery recontact them.

In every way Google, acts with a complete disregard for the customer. We have all had the same disregard heaved on us when we have to continually call and waste our time. Why isn't Google racing to right this. I still can't understand with the roll out of Google 6 which I among many Google 3 owners were anticipating what is in it for Google to infuriate their loyal customers like this.

dk...@gmail.com <dk...@gmail.com> #630Sep 25, 2021 12:39AM

Just to add to everyone in this thread, Google is not going to replace or repair any of these phones. I have spent a few hours on the phone with their 'support' and it was very clearly stated to me that it's out of warranty and any repair is my responsibility.

So, if you come here looking for some hope on getting a replacement, don't. I've been using Fi since it was called Project Fi and I've only bought nexus and pixel phones. I was shown no loyalty, no compassion, just a faceless voice telling me that it's my fault that I bought the Pixel 3.

fe...@gmail.com <fe...@gmail.com> #631Sep 25, 2021 12:46AM

Same issue here. I'll never buy another phone from Google, this whole experience has been a nightmare.

me...@gmail.com <me...@gmail.com> #632Sep 25, 2021 01:25AM

Some good news it seems

https://www.gizmochina.com/2021/09/23/google-now-reportedly-replacing-pixel-3-3-xl-units-bricked-with-edl-mode/

dk...@gmail.com <dk...@gmail.com> #633Sep 25, 2021 01:29AM

Sorry bud, but those replacements aren't happening according to Google Support. When I specifically mentioned the article, they stated that the articles are false. Honestly, if they were real, the support would say something to that effect, instead they made sure I'll never buy another Google branded phone.

ma...@gmail.com <ma...@gmail.com> #634Sep 25, 2021 05:31AM

Similar to what Australian users have been suggesting, have any UK buyers had luck with the Consumer Rights Act 2015? Obviously this would be to the retailer and not necessarily Google. Mine was purchased from a large department store so I will be trying them later today.

ma...@gmail.com <ma...@gmail.com> #635Sep 25, 2021 03:49PM

I had been dreading this. Woke up at 4 am to a bricked pixel 3 xl. What am I supposed to do?

kl...@gmail.com <kl...@gmail.com> #636Sep 25, 2021 04:23PM

Similar issue the evening of the 24th, pixel 3 xl is bricked, unresponsive, same experience as #615 above.

sp...@gmail.com <sp...@gmail.com> #637Sep 25, 2021 07:25PM

it happens to poco m3 too

jt...@gmail.com <jt...@gmail.com> #638Sep 26, 2021 01:44AM

My phone worked on the morning of Sep 13, 2021, for about 15 min. I set it down to cook some breakfast, only to pick it up and found the black screen. Nothing I tried could start it back up. Phone was about 90% charged when it happened. I can plug into my desktop and it recognizes a USB device being plugged in, but no way to talk to it. Seems like a software issue. Talked with customer support on Fri, Sep 24, and they were no help. Out of warranty so no offer of a replacement. Told me to take it to UBreakiFix as an alternative to being out of warranty. Even told me that I could trade it in for a new phone. I asked, even if the phone is dead? No response.

How do they expect us to be excited about any new Google products if they can't even own up to these type of problems that are not caused by the user?

pv...@gmail.com <pv...@gmail.com> #639Sep 26, 2021 01:49AM

google support gave me the same answer, and of course ubreakifix gave me a blank stare when i told them what was going on. looks like this was my last google device; i'm giving up and moving over to apple products. (was hit with a similar issue with my pixel 2 where a software update bricked it and google told me to kindly shell out for a new device.)

mi...@gmail.com <mi...@gmail.com> #640Sep 26, 2021 01:51AM

My P3XL is now in EDL mode and useless! 😡

bl...@gmail.com <bl...@gmail.com> #641Sep 26, 2021 03:11AM

I wish I could make this up. My 3XL was replaced out of warranty by Google on RMA. I just opened up the new phone and turned it on....there's a small circle of dead pixels on the screen.
On the phone again with Google at this moment to see what they will do.

w1...@gmail.com <w1...@gmail.com> #642Sep 26, 2021 06:24AM

My pixel3 crashed yesterday too. I can't even boot in safe mode. No solution to the problem can be found at all.

ru...@gmail.com <ru...@gmail.com> #643Sep 26, 2021 06:36PM

Adding another Pixel 3 to the EDL pile. I set my phone down for 30 mins and went to use it again and it was blank.

to...@gmail.com <to...@gmail.com> #644Sep 26, 2021 07:22PM

Same issue here - EDL mode when i plug it into a PC. Unable to do anything /w it at this point

re...@gmail.com <re...@gmail.com> #645Sep 26, 2021 07:30PM

My 3XL died in the middle of the night July 11th. Considering every other
time I've had contact with the Pixel and Nexus teams after warranty, I
didn't bother contacting them. Now I want a replacement too! Even a Google
store credit would be a nice gesture.

On Sun, Sep 26, 2021, 12:22 <buganizer-system@google.com> wrote:

- Show quoted text -

ma...@gmail.com <ma...@gmail.com> #646Sep 26, 2021 09:33PM

YOU DESTROYED OUR PHONES.

Now, do the responsible thing and fix us.

If I destroyed hundreds of dollars of Google property, I'd be in jail.

You destroyed HUNDREDS OF THOUSANDS OF DOLLARS of our property.

da...@gmail.com <da...@gmail.com> #647Sep 27, 2021 12:39AM

- Build Number: google/crosshatch/crosshatch:12/SPB5.210812.002/7671067:user/release-keys
(Note: It is the build when sending this report. For exact build reference, please see the attached bugreport.)

Debugging information
Layanan Google Play
com.google.android.gms
Version 213614053 (21.36.14 (190400-395708125))
System App (Updated)

Android System WebView
com.google.android.webview
Version 457708233 (93.0.4577.82)
System App (Updated)

Network operator: TSEL-PAKAIMASKER
SIM operator: Telkomsel

Filed by Android Beta Feedback. Version (Updated): 2.20-betterbug.external_20210805_RC02
To learn more about our feedback process, please visit

https://developer.android.com/preview/feedback#feedback-app.

deleted

Restricted+

0 B

da...@gmail.com <da...@gmail.com> #648Sep 27, 2021 12:39AM

Information redacted by Android Beta Feedback.

deleted

Restricted

0 B

ca...@gmail.com <ca...@gmail.com> #649Sep 27, 2021 02:14AM

I'm also adding my phone to the bricked pile. Same bug as above :(

pw...@gmail.com <pw...@gmail.com> #650Sep 27, 2021 07:06AM

The support team has denied it's a known issue.

"Thank you for contacting Google Support.

I'm sorry to know that the troubleshooting didn't work. Thanks for highlighting this issue to us. I want to inform you that we haven't received any official information from our internal team if it's an known issue. I would suggest you to try resetting your device bootloader menu."

Case ID [7-7225000032008]

wi...@gmail.com <wi...@gmail.com> #651Sep 27, 2021 10:40AM

My Pixel 3 xl bricked overnight the guest week of August while on vacation. Woke up with an error message. Pressed power button to continue, and that's all she wrote. Dead.

aq...@gmail.com <aq...@gmail.com> #652Sep 27, 2021 12:55PM

Looks like there might be some light at the end of the tunnel here folks! This is why it's very important for you to submit a ticket in and keep pushing them to do the right thing. Eventually someone over at Google will do the right thing, especially with how widespread this issue is.

https://www.reddit.com/r/GooglePixel/comments/psqe7e/google_is_replacing_my_bricked_3xl/?utm_source=share&utm_medium=web2x&context=3

re...@gmail.com <re...@gmail.com> #653Sep 27, 2021 04:58PM

Light at the end of the tunnel, right. It's only been how many months since this started happening and how many months till they started working the problem. I sent my phone in, they wouldn't properly diagnose it and said F you. If that one person who sent in their phone isn't some PR person from google bullshitting us then I'd be surprised.

message-123993698-10388378487505066076.jpg

206 KB

View

Download

ga...@gmail.com <ga...@gmail.com> #654Sep 27, 2021 05:50PM

This just happened today at around 8:30AM PST to my Pixel 4.

bg...@gmail.com <bg...@gmail.com> #655Sep 27, 2021 06:04PM

My Pixel 3XL did this about a month ago. Was at or near 80% battery, no pending updates that I know of. Sat the phone on my nightstand and took a little 20 minute afternoon nap and woke up to a completely dead device. Plugging it into my computer shows QUSB_BULK in device manager. This is awful especially considering that I cannot access my Google Authenticator app and I've got 7 or 8 accounts there... This just sucks.

cm...@gmail.com <cm...@gmail.com> #656Sep 27, 2021 06:59PM

Just adding another voice to the chorus that my phone was absolutely fine and charged this morning and was dead at lunch time. It had been sitting on a desk undisturbed. Same issue as everyone else--no booting, but is recognized when plugged into my desktop via USB.

ia...@cazabat.com <ia...@cazabat.com> #657Sep 27, 2021 08:01PM

Just parroting what has been said before. If you comment, be sure to click the "Star" at the top of the page. At this point, that's a simple thing for Google to see how big a problem this is.

ja...@gmail.com <ja...@gmail.com> #658Sep 27, 2021 08:53PM

I anyone aware of this same issue happening across other Pixel devices?

After a lot of haggling and back and forth, I've gotten Google to agree to replacement my bricked Pixel 3 with a new Pixel 4 device. At first they offered only a Pixel 3 (which obviously I said no way), then only a refurbished Pixel 4 (which I also said no way). They have agreed to a new Pixel 4 device and I'm waiting to hear back to confirm they aren't having the same bricking issue and that it will also carry a new device warranty.

Bottom line Google has had an awful response to this issue suddenly destroying the Pixel 3 phones and the only way to get a response from them is persistence and stubbornness.

oz...@gmail.com <oz...@gmail.com> #659Sep 28, 2021 06:03AM

@658 There's been two or three Pixel 4s on this thread. Nothing to say it's common though (yet), though given we don't even know the cause it could just be a matter of time.

ra...@gmail.com <ra...@gmail.com> #660Sep 28, 2021 12:24PM

Is there a way to sort open issues by the star count? Just to know how important this issue with 427 stars is.
And what does S3 severity mean?
PS: I already commented in this thread that my P3 is bricked.

cd...@gmail.com <cd...@gmail.com> #661Sep 28, 2021 12:35PM

Another one bites the dust..
Went to set up my pixel 3a for my daughter about a week ago Did the factory reset, UPDATED (I didn't know😭. At the time, I couldn't fathom this happening.) Walked away, when I came back it wasn't charging anymore, and it's been dead ever since. WTF Google

co...@bodcare.com <co...@bodcare.com> #662Sep 28, 2021 02:31PM

I'm a shareholder in #Alphabet/ #Google and I'm genuinely concerned that they would not send out a patch to prevent the widespread bricking issues they caused via OTA from arising to remaining 3 users including myself. I am moved by the sheer numbers if you can go to your local media and go public, it would be a good story. CBC Canada is one. News stations in Australia and UK, a variety in USA.
This is one time that the company must in good faith and public relations to act positively

ta...@gmail.com <ta...@gmail.com> #663Sep 28, 2021 02:42PM

With the Pixel 6 release date right around the corner, the best option for Google was probably to resolve this quickly, though delaying past release may be a viable option for them as well. I had a reply of mine deleted (it was truthful and polite, mind you) on a popular tech news site after bringing up the issues my family ran into with the Pixel 3XL, and noticed later on that it was deleted. It's certainly possible there was no relation whatsoever, but the tinfoil hat in me wonders if Google has their friendly media partners running point on this ahead of the Pixel 6 release. Trying to suppress negative views on the Pixel brand and whatnot. It wouldn't surprise me; I saw a few articles about these Pixel issues but they didn't seem to attract the attention I expected ahead of what is supposed to be a pretty major release for Google.

ro...@gmail.com <ro...@gmail.com> #664Sep 28, 2021 03:14PM

My wife and I have the same issues with our 2 3xl phones. We love our pixel devices and chose them over Samsung. Based on Googles lack luster response on this "unknown issue" we may switch to another phone provider. Granted we had our phones for 3 years now, we didn't see any reason to upgrade. I still have my nexus 5 and 6P phones....

ta...@gmail.com <ta...@gmail.com> #665Sep 28, 2021 03:23PM

^ we broke out our old Nexus 6 to replace our bricked Pixel 3. Sort of ironic..

ga...@gmail.com <ga...@gmail.com> #666Sep 28, 2021 04:23PM

lol I broke out my pixel 3 to replace my broken pixel 4

ja...@gmail.com <ja...@gmail.com> #667Sep 28, 2021 08:09PM

This issue is happening across Pixel 4 units as well? FML. After pulling teeth, I finally got Google to send me a replacement for my Pixel 3 out of warranty, a new Pixel 4XL 128GB. I should have it tomorrow but if this is an issue with the 4's as well, I'm afraid to even plug it in.

an...@gmail.com <an...@gmail.com> #668Sep 28, 2021 11:03PM

Happened to my wife's pixel 3 today. Very upsetting, it's her lifeline to everything and how she keeps connect with kids in school. Unacceptable.

ga...@ghart.com <ga...@ghart.com> #669Sep 29, 2021 12:05AM

Don't forget to hit that star at the top! And if you have connections at tech sites, feel free to nudge them to publicize this as well.

da...@gmail.com <da...@gmail.com> #670Sep 29, 2021 02:14AM

Ugh... same issue here. I was kind of hoping that Google would have a solution for this by now. :-/

ru...@gmail.com <ru...@gmail.com> #671Sep 29, 2021 03:11AM

A DIFFERENT perspective to be considered: Google SOLD several MILLIONS of Pixel 3, and now “only” HUNDREDS of them are bricked.
Therefore “only” about ONE in TEN THOUSAND is “defective”.
From Google point of view this is “probably” “acceptable”.
The “odds” of being bricked is “very low” (1 in 10,000)
Of course, this is no consolation to those whose phones are bricked.
It would probably take a MUCH HIGHER number of bricked phones to move Google.
As #617 speculated, maybe it is caused by flash memory not being properly wear levelled

my...@gmail.com <my...@gmail.com> #672Sep 29, 2021 03:29AM

THIS ISSUE HAPPENED TO ME TONIGHT, ONE SECOND IM STREAMING MUSIC NEXT THE PHONE IS OFF. I THOUGHT IT DIED BUT NOPE, WONT CHARGE, WONT TURN ON. PLUG INTO PC AND GET THE QUSB_BULK PROMPT.

Google -- HOW IS THIS OKAY? You cant just wreck peoples phones and do nothing!

ta...@gmail.com <ta...@gmail.com> #673Sep 29, 2021 03:34AM

#671, keep in mind this is a technical forum and not a formal report tool for devices. I think it's safe to say those reporting here are the "techies" and are the minority subset of a larger population facing this issue. Probably not a good idea to draw conclusions from the numbers here. If anything, I'm surprised by how many people have reported the issue here. It's typically quiet around here. The activity here has me thinking it's actually quite a widespread issue.

Would the average person plug the device into a computer, get the error code, Google that, and find this post? I don't think so. I think many would either contact their provider directly for a replacement or put it in a drawer and buy a new phone because they rely on it and can't go without it.

co...@gmail.com <co...@gmail.com> #674Sep 29, 2021 03:55AM

Same issues as #22.

sa...@gmail.com <sa...@gmail.com> #675Sep 29, 2021 03:59AM

I agree with you, #673. If 600+ people are finding this obscure thread and reporting the problem, I believe that a much larger percentage may have the same issue and have not reported it.

Regardless of the number of customers affected, I think it's a shame how Google is handling this situation... diehard fans are becoming haters. I wish Google would do the right thing and help us.

mi...@waychison.com <mi...@waychison.com> #676Sep 29, 2021 04:15AM

I've been following this thread for a while now, as a long time 3 XL user,
and as somebody who has used google's Android phones since the beginning.
I believe I have witnessed the issues reported here on our devices at
various times, but am not sure. I hope my words below may help some of
those following this thread.

The symptoms are as follows: the device "turns off", with the screen going
blank, seemingly off / black, but still powered (hard to tell due to OLED).
This seems like a hard crash of some sort, where the device is locked and
wont easily reset. We've also witnessed it do this and then come up with a
small text warning about "corruption" and being unable to boot.

When this has happened in the past, we have been able to recover the phone
through some combination of holding the both the Power key and either the
Volume Down or Volume Up key, for more than 40 seconds. I think it is
volume down, but frankly it seems to change between phones so if one
doesn't work try the other. Usually this will eventually trigger the phone
to reboot and often get into either recovery mode or fastboot mode, both of
which you should be able to navigate and reboot the device correctly. If it
doesn't work, I usually just try switching to the other combination a few
times and it usually works.

If you leave the phone in this broken state for long enough, it seems to
slowly drain your battery in a bad way. When trying to recover from this,
I've found it useful in the past to do as others have mentioned and use a
"dumb" USB power source. Something not a computer that will negotiate or
sense and possibly power down the port, as it is possible that the phone
may not be able to negotiate power well when the battery is completely
flat. This is what others mean when suggesting using an "AC adapter" up
thread. 12V-USB car adapters seem to work as well. This seems to be less an
issue with the electronics in the 3 XL, however it might help.

oz...@gmail.com <oz...@gmail.com> #677Sep 29, 2021 04:56AM

@676 Power + Vol Up/Down has been tried many times, as has forced power drain to drive a reset. The problem is the phone doesn't ever get to recovery or fastboot mode and instead remains in the Qualcomm Emergency Download (EDL) mode. This indicates either dead flash or bootloader corruption - both of which are unrecoverable without the Qualcomm signed flash image and Qualcomm image loader. Google could trivially provide a Qualcomm signed image for us to try to rule out bootloader corruption. They have not done this.

pa...@gmail.com <pa...@gmail.com> #678Sep 29, 2021 05:25AM

Google is squandering customer goodwill here. Sure - we Pixel 3XL owners are but flyspecks to a multibillion dollar corporation. But treating existing customers poorly - either ignoring them, or pretending that an obviously catastrophic problem in an existing product in customer hands doesn't exist, can lead people to decide that loyalty to an objectively otherwise very good brand of phones is not worth the risk of future mistreatment if we stick with them.

So far, I'm lucky. My 3XL is still alive, auto-updates turned off. But I live with constant worry that I'll wake up with a doorstop next to my bed, not my smartphone. I monitor a currently vacant home remotely via the phone, so if it dies, I lose critical alerts. Likewise I run some cloud servers - hosted within google and others - that I'll lose alerts for if it dies.

I don't need the stress. And I'll happily spend my thousand bucks elsewhere if another brand shows willingness to treat customers as valuable assets *after* they've gotten their thousand bucks from me. S21 Ultra? Maybe. OnePlus 9 Pro? Maybe. There are other phones besides the yet-to-be-released Pixel 6 Pro out there. The 'pure android' experience has been a pleasure. I'm sure I can adapt to a different 'distro' if need be.

pa...@gmail.com <pa...@gmail.com> #679Sep 29, 2021 05:33AM

Re #671 - even if the rate were as high as one in 1,000 rather than one in 10,000, Google can certainly afford to *treat those customers who have experienced this catastrophic failure of their device with more respect*. Repeatedly telling people to take it to a repair shop, of offering a replacement at or near full retail price because it's 'out of warranty' - ridiculous. We all know the margins on smartphones. Their bottom-line would not even register the cost of treating these customers respectfully. Why would I drop a grand on a Pixel 6 Pro with this example of customer care, and no objective way to convince myself 'well, it won't happen on this phone after the warranty has run out'.

le...@googlemail.com <le...@googlemail.com> #680Sep 29, 2021 03:43PM

I had this same problem with my Pixel 3, but it happened to me the evening of the 4th of May. As it happened so long ago, I thought it had just died, this was before I started seeing all these reports.

I actually bought a broken screen phone second hand in June after putting up with my Essential Phone for a while and then I repaired it myself by transferring the insides of the phone from ebay to the case of my phone. It's got a working screen etc now where the phone from ebay had a broken screen.

Be interested in knowing if a fix ends up being found for this, I must have had one of the first phones to die because of this issue. Again, it was stock, no root etc. Most it had was possible developer options enabled.

gu...@gmail.com <gu...@gmail.com> #681Sep 29, 2021 08:18PM

Same thing happened a couple nights ago, I think it was September 26, 2021 to my Pixel 3 XL. Phone was on a wired charger overnight while sleeping.
It was fine the night before, plugged it in, went to sleep, and it was dead in the morning. Completely stock, unlocked from my phone provider.
I have also tried letting it die out completely (I assume, no way to check) and charging afterwards for fun. It lights up on my wireless charger and shows up as "QUSB_BULK_CID:XXXX_SN:XXXXXXXX" when plugged into my pc.
Holding power button will have it disappear from my device manager and show up a few seconds later.

Very cool Google, thankyou.

re...@gmail.com <re...@gmail.com> #682Sep 29, 2021 09:24PM

#479 who got the reply from Sean with a return.
Which address was it coming from? I've made zero progress with folks at the device-support@google.com people.
This is beyond frustrating.

pa...@gmail.com <pa...@gmail.com> #683Sep 29, 2021 10:28PM

Wow - just wow. No, my Pixel 3XL hasn't bricked, yet. But the back glass is separating along the power-button side. We know what that means - bloating battery. So, unsafe to continue using it, replacing the battery with impending bricking always looming is simply not a sane option, Pixel 6 Pro not out likely for several weeks to a month. Guess it's 'bye bye Google phones' forever. Now to spend five hours deciding between the Samsung Galaxy S21 Ultra or the OnePlus 9 Pro. Both seem to be about the pinnacle at the moment, both have shortcomings, but very different ones from one another. Gosh this is fun. Thanks google!

ma...@gmail.com <ma...@gmail.com> #684Sep 30, 2021 04:43AM

Add me to the list. Pixel 3 bricked Aug 7. Woke-up that morning and unplugged the phone, downloaded an update. Was driving with maps and I noticed it was acting oddly, also wouldn't charge. When the battery wound down I got the boot screen, none of the recovery options worked. All it will do now is flash the lightening bolt when plugged in. Customer service experience mirrors what others here have said, send it in for repair at my cost.

ga...@ghart.com <ga...@ghart.com> #685Sep 30, 2021 02:27PM

#683 - try contacting Google about your bloating battery. They very quickly replaced mine with a bloating battery even though it was out of warranty because that was considered a "safety risk".

https://support.google.com/pixelphone/gethelp

pa...@gmail.com <pa...@gmail.com> #686Sep 30, 2021 02:54PM

Just to add my issue to the list. I have a Pixel 4 XL and it appears to have the same symptoms. Plugged it into a functional charger overnight, woke up to a blank screen with no way to get it to boot back up. I have tried a few of the troubleshooting steps that I have seen in this chat.

sa...@gmail.com <sa...@gmail.com> #687Sep 30, 2021 03:01PM

Same issue here with Pixel 3. It is stuck in EDL mode supposedly. Is there a way to at least grab files off of the onboard storage when it is in this mode?

pa...@gmail.com <pa...@gmail.com> #688Sep 30, 2021 05:50PM

re #685, about contacting google about the bloated battery - appreciate the advice, but - nah. I'm done with google, at least when it comes to anything other than "hey google, what's the best alternative to the upcoming Pixel 6 Pro". I ordered a Oneplus 9 pro last night. I'll buy a battery replacement kit on ebay and replace the battery myself, when i feel like it. And hopefully, someday, google will actually admit there is a bricking problem with the Pixel 3XL, and figure out a fix. As before, I'm not going to hold my breath.

Disassociating oneself entirely from google is damn nigh impossible, so i'm not going to even try, but dropping many hundreds of bucks/a grand in google's pocket is definitely not going to happen. You want my business - beyond sniffing my email for ad opportunities and such? You'll have to earn my trust back. We'll see how the Pixel 7 Pro turns out in a couple of years, and how the 6 pro has fared in that interval. Now to figure out which carrier to switch to from Google Fi...

ra...@gmail.com <ra...@gmail.com> #689Sep 30, 2021 06:10PM

I have had this issue but I've managed to get a replacement device sent out by Google support, even though I'm out of warranty. I sent them a bunch of links to this issue (incl this) and the rep was quite supportive and understanding.

re...@gmail.com <re...@gmail.com> #690Sep 30, 2021 06:26PM

#689 I've gotten dozens of replies saying no. Luck of the draw?

On Thu, Sep 30, 2021, 11:10 <buganizer-system@google.com> wrote:

- Show quoted text -

dk...@gmail.com <dk...@gmail.com> #691Sep 30, 2021 07:59PM

That's a Google PR intern at work.

ra...@gmail.com <ra...@gmail.com> #692Sep 30, 2021 08:04PM

Luck of the draw I guess. I'm from the UK if that makes a difference. Also if I was a google PR, why would I be encouraging people to speak to google support if their mandate is to say no? Think more before commenting.

dk...@gmail.com <dk...@gmail.com> #693Sep 30, 2021 08:52PM

UK makes a big difference. You have different laws on consumer electronics (Like Australia where they are replacing them).

You're right about the PR thing, Google has only read from a script which says take it to UBreakIFix along with stuff like 'No Warranty' and 'I dont know what you are talking about <click>'.

wd...@gmail.com <wd...@gmail.com> #694Sep 30, 2021 09:16PM

Add me to the list of Pixel 4 XL owners who are beyond frustrated. My phone was charging on my desk and when I went to pickup my phone to check a voicemail, the screen was black and I couldnt do anything. Getting the "QUSB_BULK_CID" in device manager so I can only assume its stuck in EDL. Google support was beyond rude to me about this issue and implied that somehow this was related to me installing Android 12 beta on my device. I'm sending my phone back for "repair" based on the extra 1 year of warranty they added to Pixel 4, but I'm just waiting for them to try to weasel out of it and somehow blame me for what is obviously a hardware/software issue they need to deal with. They still have a chance to salvage my business, otherwise I will never spend another penny on their hardware. Based on my experience with customer service chat today, I won't be holding my breath for a free repair.

oz...@gmail.com <oz...@gmail.com> #695Sep 30, 2021 10:01PM

@#694 Very interesting that Google are noting that Pixel 4's doing the same thing is a duplicate of this issue. I wonder if we'll seem Pixel 5s with the same issue in 12 months or so?

db...@gmail.com <db...@gmail.com> #696Sep 30, 2021 10:03PM

Pixel3 XL died overnight on the stand 9/29/2021. Took a pic of my 2factor codes a month or two prior, when all the reports of the 3 started coming out on the phone self bricking. Glad I did. Ordered from

store.google.com on Oct 9, 2018.

ca...@gmail.com <ca...@gmail.com> #697Sep 30, 2021 11:37PM

Same here. Pixel 3 died overnight on the 7th August. Shows up as "QUSB_BULK_CID:XXXX_SN:XXXXXXXX" when plugged into my pc.

ri...@gmail.com <ri...@gmail.com> #698Oct 1, 2021 04:13AM

Same here with the "QUSB_BULK_CID:XXXX_SN:XXXXXXXX" error while plugged into PC. Phone is completely unresponsive and two chats with support have so far told me to spend $400 to repair the thing. Very dissapointed with google support for their own hardware. I will be looking elsewhere if google does not provide a reasonable response to this issue. A flagship phone should not fail after such a short amount of time.

ca...@gmail.com <ca...@gmail.com> #699Oct 1, 2021 04:43PM

My original post was #518.
Google has shipped my replacement Pixel 3 and it should be here Monday. I will let you know if it craps out after setting it up. I did ask and there is like a 90 day warranty on the refurb if you get one.

ok...@gmail.com <ok...@gmail.com> #700Oct 1, 2021 04:56PM

How did you manage to get a replacement? Was it under warranty?

an...@gmail.com <an...@gmail.com> #701Oct 1, 2021 06:04PM

Droidwin.com is suggesting the following fix. Wondering if anyone has tried it and had any success?

What you need to do is let your device’s battery completely drain out so that it turns off. When that happens, plug-in your device into the charger and keep it in that state for a few minutes. Then unplug your device and power it on, it should now directly boot to the OS, bypassing the EDL Mode.

https://www.droidwin.com/fix-pixel-3-automatically-booting-to-edl-mode/

ta...@gmail.com <ta...@gmail.com> #702Oct 1, 2021 06:23PM

#701 - we've tried that multiple times over the past couple weeks with no luck. I think the author was just taking a shot in the dark, or maybe echoing solutions that fix other phones that are in EDL mode for other reasons.

ca...@gmail.com <ca...@gmail.com> #703Oct 1, 2021 06:45PM

#700 - My device was no longer under warranty as most Pixel 3/XL's. I got the same crap everyone got when calling. I pointed to this thread and multiple issues documented on all the android/pixel fan sites. I did a quick google and started pasting each URL starting with this one in over and over. Search google Pixel 3 EDL issue and you will have plenty. Then I asked for an escalation. When I went to second level support I pointed out again this is a known issue, was due to some update pushed to all our phones and pointed out it is impossible by chance this all started happening due to something all of us did. The person said they were escalating my issue to a higher team and gave me their contact via email. Within one day the second level support said they were going to do an exception replacement with a refurb.

My guess is they want to get their hands on several to get a better handle on this issue and are doing so on a certain number for persistent customers. I have no idea.

I will let you know if my replacement bricks. My wife also has one that hasn't bricked yet.

re...@gmail.com <re...@gmail.com> #704Oct 1, 2021 08:55PM

I'd love a copy of those emails as I'm getting zero traction with what
sounds like the same message.

On Fri, Oct 1, 2021 at 11:46 AM <buganizer-system@google.com> wrote:

- Show quoted text -

--
This message and any attachments are for the designated recipient only and
are confidential and may contain privileged, proprietary or otherwise
private information. If you are not a named recipient, please notify the
sender immediately and delete the original. Any other use of this email by
you is prohibited. Use beyond your sole knowledge must be requested by the
sender.

na...@gmail.com <na...@gmail.com> #705Oct 2, 2021 09:41AM

@#617: I find it hard to believe it's a coincidence that everyone I know with Pixel 3's who have auto-updates turned off are unaffected by this issue (including me).

ki...@gmail.com <ki...@gmail.com> #706Oct 2, 2021 01:13PM

Had the same thing happen to a Pixel 3XL around the end of August. Went to sleep with phone not on charger, woke up to black screen. Bought at release from the Google store in October 2018. Not concerned with the unit itself just would like a way to retrieve data.

jb...@gmail.com <jb...@gmail.com> #707Oct 3, 2021 01:54AM

This is absurd. 100s of people reporting the same issue and the best Google can do is advise to take it to ubreakifix (which won't fix this specific issue) or give us the generous offer of having us spend $400 for Google to fix an issue they caused. I've been using strictly Google phones since the Nexus but this is the final draw. Google needs to do the right thing and fix our phones.

am...@gmail.com <am...@gmail.com> #708Oct 3, 2021 05:18AM

@682

The email I got with the offer to replace my device and the RMA number/shipping label was the device-support@google.com email address.

Full disclosure I was out of town for a couple weeks so I haven't sent my phone in for replacement yet but I did receive an RMA number and return label from that email address.

jo...@gmail.com <jo...@gmail.com> #709Oct 3, 2021 05:27AM

Here's the final gem of a response I got from 12 messages back and forth with Device Support:

I'd like to let you know that you've reached the highest level of support and we have provided the relevant options available to you from our end which is getting the device repaired through our repair partners or ship the device to Google for repair. I've also reviewed the links you've shared with us and currently there aren't any replacements being processed for the devices being out of warranty and would also suggest you to refrain from referring to any third party sites as it might not have the complete and official information.

I'm sorry if this disappoints you but we have tried our best to help you with the alternate solution. If you've any other questions, please don't hesitate to contact us. We'll be happy to help!

sf...@gmail.com <sf...@gmail.com> #710Oct 3, 2021 04:47PM

Oh, that's rich. "I [...] would also suggest you to refrain from referring to any third party sites as it might not have the complete and official information." (from #709)

How about we get an official response from Google about why Pixel 3s are failing at an alarming rate, then, instead of leaving us to rampant speculation? Let those of us with a broken phone make informed decisions about repair vs replace. For those whose phones are still working, help them take measures to protect themselves.

ca...@rego.io <ca...@rego.io> #711Oct 3, 2021 06:23PM

Comment has been deleted.

Message last modified on Oct 3, 2021 06:24PM

ca...@gmail.com <ca...@gmail.com> #712Oct 3, 2021 06:24PM

Happened to my Pixel 3 last night. Stuck in EDL as described by everyone.
If no solution is presented asap I see no other alternative than buying a new phone (different brand of course).

wa...@gmail.com <wa...@gmail.com> #713Oct 4, 2021 02:18AM

Comment has been deleted.

Message last modified on Oct 4, 2021 02:19AM

wa...@gmail.com <wa...@gmail.com> #714Oct 4, 2021 02:20AM

thanks google, I hate your company and your smartphones, my first 3xl pixel died in August, I replaced the motherboard with another broken pixel, and it died just a week after use, the worst attitude towards users, thanks for the great user experience

we...@gmail.com <we...@gmail.com> #715Oct 4, 2021 04:13AM

Adding to the many reports here.
I went to bed, leaving my Pixel 3 XL unplugged, woke up the next morning with it completely bricked. The screen is completely black and when I plug it into my computer I see the device as QUSB_BULK_CID:0402_SN:<redacted>.

ke...@gmail.com <ke...@gmail.com> #716Oct 4, 2021 10:04AM

On Pixel 6 Launch Day, let this be a reminder on why no one should ever buy a Google device again :)

ev...@gmail.com <ev...@gmail.com> #717Oct 4, 2021 10:53AM

Comment has been deleted.

Message last modified on Oct 4, 2021 10:54AM

ev...@gmail.com <ev...@gmail.com> #718Oct 4, 2021 10:57AM

Same issue over here. Woke up next to a dead Google Pixel 3XL. Nothing is working anymore. And like everyone I also see the device as QUSB_BULK_CID etc. I always have been very careful with my pixel and then we got this. Just weeks before the pixel 6 release.

I loved my pixel but this not amusing. And what bothers me is that this issue is reported for so long. You should expect a phone in this segment would last longer than the warranty period. And it's not even the customers fault.

Google please help is out here.

le...@gmail.com <le...@gmail.com> #719Oct 4, 2021 12:00PM

Same issue here. No help from google... Only repair possible... For the
same price I bought a pixel4a...

Le lun. 4 oct. 2021, 12:58, <buganizer-system@google.com> a écrit :

- Show quoted text -

bi...@gmail.com <bi...@gmail.com> #720Oct 4, 2021 02:48PM

Same issue here. My Pixel 3XL died just some minutes ago during the day, not charging. Same with QUSB_BULK_CID etc.

jo...@gmail.com <jo...@gmail.com> #721Oct 4, 2021 03:32PM

same happened with my Pixel 3XL, shows in device manager but cant get anywhere on device even to bootloader.

je...@gmail.com <je...@gmail.com> #722Oct 4, 2021 08:08PM

Got the reply from Google after shipping my phone to them so they can inspect my device.

You’ve qualified for a replacement Based on the inspection, we’ve found that repairing your device costs more than replacing it. Therefore, you’ve qualified for a fully refurbished replacement. It'll be the same model as your device but may be a different color. With your approval, we’ll charge you and prepare to ship you the replacement. Cost is $481.00 plus tax.

iv...@gmail.com <iv...@gmail.com> #723Oct 4, 2021 09:13PM

Also having this issue with my 3XL. I noticed the battery was draining way faster than usual over the past week or so, I figured it must have been an update or something. Went to bed last night, put it on the charger, woke up at 7am and it was dead. Reboot won't work, fast recovery doesn't work. Nothing works. My PC recognized it when I tried to plug it in as "QUSB_BULK_CID" but can't do anything with it. It must be registering it somehow, because when I tried holding down the volume + power for 30 seconds while it was plugged in, the phone disconnected from the PC and reconnected, but nothing actually happens on the phone itself.

la...@gmail.com <la...@gmail.com> #724Oct 5, 2021 02:37PM

Woke up to a bricked Pixel 3 at about 7:15am CST. Recognized on my PC as "QUSB_BULK_CID", can't reboot, can't utilize fast recovery - this thing is a paperweight now.

The fact that Google has been aware of the problem and has "nothing to add" is ridiculous. I'd intended to upgrade, but at this point, I don't know if I'd be willing to risk another Google phone that might shut down the next time they have a big launch planned.

m....@gmail.com <m....@gmail.com> #725Oct 5, 2021 06:36PM

Hello,

I am #725. My 3XL phone is bricked from updating last night, i'm assuming. It had the 'Google' Screen on for like 5 hours until I unplugged. No rebooting trick worked. Saw the QUSB_BULK_CID briefly when plugging into computer this morning. Have not been able to replicate. I want to stay with Google and get that P6, considering this is my first time posting to something like this. Waiting in line to talk with support (3 hours now). I hope this gets seen and recognized. Kinda silly on Google to brick old phones before a new release rather than after.

ch...@googlemail.com <ch...@googlemail.com> #726Oct 6, 2021 12:57PM

Same issue 3PXL is totally bricked over night. Totally dead. No combination of power and volume keys does anything, completely unresponsive. No way to get a bug report. When plugged in to a Windows PC it does come up as "QUSB_BULK_CID" holding down the power button causes the devices to disconnect / connect from Windows PC.

Google clearly released and update that has broken a large number of premium phones - surely something has to be done???

an...@gmail.com <an...@gmail.com> #727Oct 6, 2021 04:32PM

Google has really dropped the ball on this one. I tweeted about it, they told me to dm them, I did, they told me to email them, I did, they stopped responding to my emails. I contacted support again, they told me they would have to escalate the situation and that it would have to be through email. I'm waiting to see if they actually take ownership of this and make it right. I think everyone with this issue needs to just keep contacting Google through Twitter, email, and support channels. Maybe that will get them to do something to take care of their customers.

ia...@cazabat.com <ia...@cazabat.com> #728Oct 6, 2021 08:18PM

I was originally #459, but I figured I'd update here, since I've got an RMA for a free replacement. I'll post all the details here, but here's the rough overview of what I did:

Start off with a chat to support, explaining the issue with the bricked phone & you know it's out of warranty, mention this bug tracker & QUSB_BULK_CID in device manager. Be prepared to do the basic troubleshooting (it's in their script, they have to do it) and for them to eventually send you to ubreakifix for service.
Call/go in to ubreakifix (or take in for estimate) they'll tell you they either can't fix it, or it'll be a motherboard for $600. Decline service.
Get back on chat with Google, tell them you previously chatted about your out of warranty Pixel 3 & tell them ubreakifix can't fix this cost effectively. Ask for them to escalate your ticket to the next level of support.
Repeat previous info to tier-2 support. Remind them that you didn't do anything to cause the failure. Odds are, they'll look into the issue and email you back later.
When they email you back, they'll likely offer mail-in repair for ~$400. Reply that it isn't cost effective & reference this bugtracker. Ask them to escalate your ticket.

The key is to be extremely nice the entire time. You can show a little frustration, but remember no foul language or yelling (if you're on the phone). It is up to their discretion if they help you, so be nice & they might be more likely to help you out.

pi...@gmail.com <pi...@gmail.com> #729Oct 6, 2021 09:28PM

- Jump up and down three times
- Rub your belly
- Do a backflip
- Do another backflip, but forward
- Eat a shoe
- Go wait in line at the DMV
- Call your aunt Martha, who likes to talk for HOURS
- Now MAYBE we'll replace the phone that WE broke (but only if you talk
nice to us)

On Wed, Oct 6, 2021 at 4:18 PM <buganizer-system@google.com> wrote:

- Show quoted text -

br...@brionyryles.co.uk <br...@brionyryles.co.uk> #730Oct 8, 2021 02:18PM

My Pixel 3 died about an hour ago, with the exact symptoms mentioned, and I've just been chatting with Google Support about it. They state that they are unaware of any known issues with the Pixel 3 (although I sent them a link to this page, and other links, as someone suggested). I've been directed to contact the support outlets, although unfortunately they all seem to be in London, and I am not. I'm cynically wondering whether bricking Pixel 3s right before the Pixel 6 is released is a way to encourage us to spend money.

jd...@gmail.com <jd...@gmail.com> #731Oct 8, 2021 06:41PM

My Pixel 4 just encountered this issue. Device isn't two years old yet. Went to bed and everything was fine. Woke up, and EDL. Can't decide if I really want a Pixel 6 now (especially since I need a phone yesterday), or if it might be time to jump ship, since Support has been... unsupportive.

es...@gmail.com <es...@gmail.com> #732Oct 8, 2021 06:45PM

I've tried talking to Support on different occasions, I tried using the Quebec consumer warranty that forces companies to support their products even after warranty (apple does 3 years)

https://www.apple.com/legal/warranty/docs/Quebec_Consumer_Warranty_Notice_text.pdf
And at the end, nothing. I will keep trying.

On the other hand I went and got me a iPhone 13 pro, and I am super happy. This after being super loyal to Android and being annoyed at how apple gates you in their ecosystem. But I just want things that work, with a company that will go and fix their issues when they have them. So I guess it's done for Android for this family of 4

ba...@gmail.com <ba...@gmail.com> #733Oct 8, 2021 07:14PM

I wonder if anyone running a custom ROM is experiencing the same issue.
After a few years when my phones start to get older, I like to breathe new
life into them with a custom ROM... I didn't do it this time (was running
the developer's version of 12), but I'll be that I could have "saved" my
phone that way.

On Fri, Oct 8, 2021 at 2:46 PM <buganizer-system@google.com> wrote:

- Show quoted text -

co...@gmail.com <co...@gmail.com> #734Oct 8, 2021 08:37PM

My Pixel 3 XL was working fine last night but I woke up this morning and it's having the same issue described in this thread. I've tried holding the power button as well as holding the power button and the volume down button at the same time. When plugging it in to my Windows laptop it shows up as QUSB_BULK_CID:<redacted>SN:<redacted> in Device Manager. It also makes the Windows noise when plugging it in/unplugging it, or when I restart/reset the phone while it's plugged in.

ri...@gmail.com <ri...@gmail.com> #735Oct 9, 2021 12:00AM

My Pixel 4 is one more to the list of the EDL of death!! Damn! Looks like Google just don't care.. I tried everything...

lj...@gmail.com <lj...@gmail.com> #736Oct 9, 2021 01:26AM

Chiming in here, add me to the list of affected users, and at the worst possible time too. I had just landed in a different city after a long flight, when my Pixel 3 XL died overnight. Same symptoms, power/volume buttons did nothing when trying to reset, and plugging into a computer shows QUSB_BULK_CID in the Device Manager. The uBreakiFix that I brought the phone to was also unable to do anything. That left me scrambling to find a store to purchase a new phone on-the-fly so that the rest of my travel itinerary wouldn't be too badly disrupted from effectively losing my phone on the very first day. Ironically, none of the stores I checked had any Pixel phones in stock, so I went with a Samsung Galaxy phone. I was originally holding out for the Pixel 6, but now I'm having second thoughts.

jl...@gmail.com <jl...@gmail.com> #737Oct 9, 2021 02:52AM

Welp my add my Pixel 3 to the list of dead phones. Was working fine one minute, the screen shut off and now it won't turn on and I get the QUSB_BULK when I plug it into my computer. The best part is I reached out to Google Support and they suggested plugging it into the original charger for five minutes and trying to power it on. At 4 minutes and 30 seconds they disconnected from the chat, so I couldn't even continue troubleshooting with them! My wife and I just had our second child, so I'm really not looking forward to having to buy a new phone! I know this phone is technically out of warranty, but I feel like this ends up happening with every Google phone I buy. At this point if Google can't put out a solid phone that can last more than a year or two and isn't going to stand behind their products I think I'm just going to pick up an iPhone. I love Android, but I need a phone that's not going to unexpectedly just die on me, leaving me stranded and unexpectedly having to shell out hundreds of dollars for a new one.

sh...@gmail.com <sh...@gmail.com> #738Oct 9, 2021 05:37AM

Dear google supporters,

We know you are busily analyzing why this case reproduced.
But before that, would you please share the recovery TOOL/METABUILD for us to recovery the phone? So far as I know, we need the meta build to reflash the bootloader via the EDL diag port.

Regards,
Shaoxu

an...@gmail.com <an...@gmail.com> #739Oct 9, 2021 02:39PM

Dear Google supporters

We know you are busily analyzing why this case reproduced.
But before that, would you please share the recovery TOOL/METABUILD for us to recovery the phone? So far as I know, we need the meta build to reflash the bootloader via the EDL diag port.

Regards,
Antonio (pixel 3xl bricked while upgrade beta android 12)

al...@gmail.com <al...@gmail.com> #740Oct 9, 2021 02:41PM

A supervisor responded back to my bricked phone issue:

"
Thanks for reaching out to Google support. Hope you're doing good.This is
Emma, one of the supervisors at Google support. Hope you're doing good.

I understand that your device shows black screen despite performing all the
possible steps and I also see that you have been offered repair options to
get the issue fixed.

Since the device is far outside the warranty period, we are helping you
with the repair options as an alternative. Had there been an option to
replace, I'd have definitely helped you. Hope you understand the
limitations towards warranty policy.

Please go ahead with either Ubreakifix or Google Mail-in repair. Rest
assured, our partners are very competent and the will definitely fix the
issue once and for all."

The next message is all the same. Word for word. Copy pasted. Google
ultimately said, Out of warranty, not our responsibility.

...
Yes, you can use their repair options, but as has been pointed out, the
repair cost is going to amount to $400+. I was going to upgrade to pixel 6
and use my now-bricked pixel 3xl as a backup camera. I purchased this phone
for about $800 USD directly from Google Store but it only lasted for about
2.5 years. For the price I paid, I expected a lot better customer service,
especially from Google, but my latest customer support experiences were
terrible and Google simply doesn't want to admit fault in this rampant
issues found in Pixel 3

Hopefully Google invests their time to release a fix instead of turning
their back on the loyal customers.

On Mon, Oct 4, 2021, 8:33 AM <buganizer-system@google.com> wrote:

- Show quoted text -

jd...@gmail.com <jd...@gmail.com> #741Oct 9, 2021 04:04PM

Google Support is being of no use. At this point, they're just sending back the same generic responses. I ran the entire gauntlet with them yesterday. I've been an Android fanboy since before the first Android phone was released. I've even been on Google Fi since it was in Beta. With this, I'll be moving back to Verizon, especially since they'll allow me to trade my bricked phone for a brand new iPhone.

I can't imagine why a company would make such a stupid support decision. Serious fail on Googles part. At this point, I don't think I'll ever trust another of their products. Too many good products have been shuttered (Inbox, Play Music, etc), and they simply don't invest the resources to get what remains to be excellent.

Should have taken note from Asus and others who replaced graphics cards that got fried unexpectedly (talking $1500+ RTX 3090's). There's an example of taking care of customers.

am...@gmail.com <am...@gmail.com> #742Oct 10, 2021 02:14PM

Adding an update on my bricked Pixel 3 and interactions with Google device support. I fully understand I'm a bigtime outlier so far.

Google agreed to replace my phone. They actually reached out to me as a result of my posting on this thread out of the blue (I previously posted the email I received from device support). I had not yet reached out to customer service directly at the time as I had just started looking into the issue to see if it was something I could fix myself (out of warranty). They requested I send my device in for evaluation with a replacement to be sent to me.

Additionally, I voiced concern by email that I have several Pixel 3 devices on my account and I am worried of losing others at the drop of a hat. They went and sent me an "exception" upgrade to a Pixel 5 no additional questions asked under a different RMA and it arrived yesterday before I even sent my P3 in for eval. Refurb, but still.

I sent in my P3 brick under the original RMA yesterday. No idea why I got the royal treatment. And no, I am not a Google employee.

am...@gmail.com <am...@gmail.com> #743Oct 10, 2021 02:20PM

Replacement device info if it helps

Case ID [7-5771000031494]
RMA73462936

na...@gmail.com <na...@gmail.com> #744Oct 10, 2021 04:44PM

Hi!
Here from Spain!
Just the same problem with my Pixel 3XL last September 4. My phone was charging and I woke up next to a dead Google Pixel 3XL. Nothing is working anymore. I also see the device as QUSB_BULK_CID etc, like everyone here.
I just contacted to Google by telephone, my device is out of warranty. I don't know what to do.

ro...@gmail.com <ro...@gmail.com> #745Oct 10, 2021 05:36PM

is there a way to remove the component to recover data? I would want to recover my text messages on the dead pixel3. Thanks

ti...@gmail.com <ti...@gmail.com> #746Oct 11, 2021 06:19PM

Adding my name to the list. Same thing just happened to me. Woke up to a dead Pixel 3XL. Went through the useless troubleshooting methods. Talked to support, was told to send it in or drive to UBreakIFix (I hate that name. I didn't break it!). QUSB_BULK_CID etc.

I bought the Pixel 3XL brand new from the Google Store in 2018. It was a pricey investment, but I wanted a great camera. Now the bricked phone has lost my access to hundreds of pictures I've taken. I've read that this could be an easy fix if Google would release the program files. I also read the Google is offering replacement phones to some customers, but I'm not sure what the criteria is.

da...@gmail.com <da...@gmail.com> #747Oct 11, 2021 07:14PM

My Pixel 3XL bricked on Saturday night with this problem. Contacted google support was told to have it repaired at UBreakIFix. Just like everyone here tried everything to get it to response and nothing. I was looking to upgrade to Pixel 6, but now It looks like I won't be.

dg...@gmail.com <dg...@gmail.com> #748Oct 11, 2021 07:19PM

I guess I'm one of the new lucky ones.

I see a QUSB_BULK_CID:0402_SN:A0B97E3C when connected under my devices

ji...@gmail.com <ji...@gmail.com> #749Oct 11, 2021 08:01PM

First, thanks to everyone posting all their experiences and details in this
thread. It was very valuable knowledge.

I have been sent an "exception replacement" - my recommendations below.

* have demonstrable evidence that you indeed get the QUSB_BULK_CID in
device manager
** snapshot/video of device detection, for example
* find and document, in device properties, that the device power state is =
D0
** D0 means that the device is in a FULLY ON state
* be able to explain the implications of what EDL mode is and why QUSB_BULK
appears
** the EDL mode is a primary bootloader by Qualcomm that allows reflashing
of the secondary bootloader (Google's OS)
* cut and paste reports from here that going to ubreakifix resolves nothing

Deny that this is a request for warranty service. Request an exception
replacement due to software update.
Stress that the phone is bricked either wilfully via OS update or by a bad
software patch by Google.
When asked to send to their repair center UBREAKIFIX, reject, and tell them
you already know what people in your situation experience
(attempts at battery replacement, or cause unknown, motherboard replacement
- which is literally a phone replacement).
State it is reported here and in tech sites that exceptions are being made
*for this exact* situation.

Tell them you are willing to accept being "out-of-warranty" if they will
publicly declare this is caused by a hardware fault.
Short of that, they can't PROVE it was NOT caused by software. And if an
update is caused by software update, it is negligent and does not pertain
to warranty.
Tell them you know they have received EDL/QUSB phones for the engineering
team to review (search this thread), if there is no public position as to
why it occurs, then,
there is no evidence of hardware failure, therefore your only conclusion is
this bricking is caused by an OTA update by the manufacturer, therefore you
will only
accept a replacement or a public statement that it is a hardware failure.

During the initial support, when asked if the phone will power on, if you
have D0 power state, *emphatically* state the phone is indeed on, despite
nothing on screen.
Don't let them rephrase that the phone won't power on, this is inaccurate.
By maintaining the phone is fully on, it narrows the problem down to the
EDL mode, not, "just a phone that won't turn on".
Explain that since the secondary bootloader is not working, of course
nothing can talk to the screen.

If you have time to research and understand that EDL mode requires a
digital signature from Google to reflash the phone and perhaps how/why the
firehose protocol is needed.
Explain that if a primary bootloader (Qualcomm EDL) can load, ready for
flashing, then there is no hardware failure unless a repair partner can
prove after flashing in EDL results in failure.

Request escalation after passing all the Level 1 support questions and when
they say they've never heard of EDL/QUSB.
Level 2 will be dodgy, too, but keep pressing, in all the support formats
made available - voice, chat, email.

Be prepared to spend hours in chat & voice. My motivation was to have an
equitable resolution, to fight for the principle of the issue.
For me, I estimate the used market value of my P3XL to be ~$150.
Ask yourself how many hours of tying up their support is equitable. 4
hours? 6? 8?

I spent roughly 5 to 6 hours. At 8 I would have quit and chalked it up to
making Google pay their call centers instead.

Eventually, they made the exception replacement.

Other notes: be firm, don't get mad. show empathy by saying things like, i
know you can't do more in your position, but I _really_ need to speak to
someone who can.
Level 2 will have the authority to "speak to the engineering team", which
is the same as the car salesman talking to their boss, it's just a
reassessment of whether it's more cost
effective to railroad you or give you a replacement. Keep all these in
mind.

IF somehow they say their position is final, fine, call back and don't give
your ticket # and let them open a new ticket, and start over again.
IF the final decision is to send your phone to authorized repair center,
say no thanks, I'll keep my phone as-is in order to retain proof in the
event it is needed for a class action suit.

Good luck all. If you are like me and into the principle of things, I have
no doubt you'll help make Google see it's clearly cheaper to send us
refurbs,
especially when we stand firm tying up support lines and refusing to send
to UBREAKIFIX, which is a way for them to say, oh well, if repair center
can't fix, it's hardware, you're SOL!

PS - if at some point you would like to signal you will be a little
adversarial, or need to occupy more time, right after the call connects to
a human, ask them if the call is recorded.
They will confirm. Then tell them you are recording too -- they will say
you are not allowed to per policy. Say, fine, you will stop recording, but
launch a philosophical discussion of
how it is equitable or fair for one party to record but not the other.
Easily a 15 minute discussion.

-JH

On Mon, Oct 11, 2021 at 2:19 PM <buganizer-system@google.com> wrote:

- Show quoted text -

ri...@gmail.com <ri...@gmail.com> #750Oct 11, 2021 08:21PM

My phone has been experiencing this issue for 3 weeks now. Same sudden death same BULK device showing up in device manager. I've contacted support three times and each time they deny knowledge of this issue and try to get me to take the ubreakifix $400 repair option. This last time I told them this was not an acceptable resolution and asked them to leave my ticket open as unresolved. They offered to send me alternative repair options via email which sounded promising. Turns out they were literally emailing me the exact same options in an attempt to get me to go off chat. Very disappointed in Google support so far. I am a long time fi customer who purchased their phone directly from Google and this has me reconsidering my relationship with both fi and their hardware.

ti...@gmail.com <ti...@gmail.com> #751Oct 11, 2021 08:45PM

UPDATE - because I purchased Device Protection they have offered me a replacement. However they are only acknowledging that the phone won't turn on (hardware issue), and have denied knowledge of EDL mode bricking.

ma...@gmail.com <ma...@gmail.com> #752Oct 11, 2021 09:38PM

So after weeks of back and forth I got the final FU from Google really-

"I truly understand the entirety of your point. Regardless of what is the issue of your device, we rely on the warranty policy. As I mentioned from my previous email, we cannot process a replacement as the warranty of your device has already expired."

I bought a 4a cheap to get me working again, and now people are having issues with 4's too. Great.

on...@gmail.com <on...@gmail.com> #753Oct 11, 2021 10:06PM

My Pixel 3 just did this overnight Saturday to Sunday. There seems to be no way to recover. Using the normal google support options (hold power + volume, slow charge with laptop, charge with official charger overnight) doesn't have any effect.

When I plug it into a PC, the computer makes the chime sound that something has been connected but nothing is visible. If I hold the power button while connected to a PC it will make another chime and something called "QUSB_BULK_CID:XXXX_SN:XXXXXXXX" will show as a connected device but nothing can be done with it.

Looking into this online appears to be a HUGE issue with Pixel 3's since December 2020, but accelerating since September this year.

What is Google doing about it? Is there a solution, or a class action in place yet?

g....@gmail.com <g....@gmail.com> #754Oct 12, 2021 02:48PM

Adding my name to this list - my pixel 3 bricked on 10/6. QUSB_BULK_CID:0402_SN:5E909FED when connected to my computer. @google would really appreciate a fix for this.

br...@sevensoupcans.com <br...@sevensoupcans.com> #755Oct 12, 2021 06:36PM

I have also had this issue happen to my Pixel 3 after leaving it charging overnight. I get the QUSB_BULK_CID:* when connecting over a USB cable to my computer.

I'd love to get this resolved as this device was still working properly!

wy...@gmail.com <wy...@gmail.com> #756Oct 12, 2021 07:02PM

My wife's Pixel 3 can be added to this list.

-Phone plugged in over night and woke up to blank screen? Check.

-No combination of button presses/holds can reset/recover/turn on the device? Check.

-Connecting it to my PC and it comes up in device manager as QUSB_BULK_CID:XXXX_SN:XXXXXXXX? Check.

-Wondering what Google will do to rectify this issue, but expecting it will be nothing? Check.

na...@gmail.com <na...@gmail.com> #757Oct 12, 2021 09:06PM

Support worker was so so close to taking responsibility, but training kicked in just at the last minute.

"
------------------------------------------------
Hi Me,

I am sorry if you felt ignored. We have checked with the internal team already on this issue and we request you to try the suggested below steps.

We release system updates to improve system performance and stability and to fix minor bugs. System updates are intended to keep devices secure.

We are not sure what changes might have made though developers settings or devices could have been modified/ rooted in any way where it could break the OS. Developer mode is specially intended for developers to use restricted features and provide feedback to the Android team.

If there's a system update available and the device has never been rooted, I recommend you to please update the device.

Good day!

Thanks!
Sasha
The Google Support Team
------------------------------------------------

------------------------------------------------
<me@gmail.com>
10 Oct 2021, 17:21 (2 days ago)
to device-support

Hi

Thanks for the reply, so are you saying that if I update my phone and it bricks in the same manner as all the other devices reported, you would be willing to replace it?

Thanks
------------------------------------------------

------------------------------------------------
device-support@google.com
10 Oct 2021, 20:15 (2 days ago)
to me

Hi Nathan,

We cannot promise anything. We release system updates to improve system performance and stability and to fix minor bugs. System updates are intended to keep devices secure.

If you wish, you can try to update the device and that will help you. We can check other options, once you follow the steps recommended to you earlier.

Thank you for your time.

Thanks!
Sasha
The Google Support Team
------------------------------------------------

------------------------------------------------
<me@gmail.com>
10 Oct 2021, 20:48 (2 days ago)
to device-support

Hi

But as you said "If there's a system update available and the device has never been rooted, I recommend you to please update the device." and my device isn't rooted, then if this update bricks my phone you would take responsibility for this?

Thanks
------------------------------------------------

------------------------------------------------
device-support@google.com
10 Oct 2021, 21:03 (2 days ago)
to me

Hi me,

As informed you earlier, I wouldn't be able to comment anything for now. If you experience any issues with the device post update. I will have to collect the details from you and check with my internal team seeking their suggestions.

Thanks!
Sasha
The Google Support Team
------------------------------------------------

They really are tip toeing around this.

jo...@jedi.net <jo...@jedi.net> #758Oct 12, 2021 09:52PM

I had a scare today. I applied the October 2021 security update which was prompting me in a notification on my Pixel 3XL. I gave it permission to proceed and my screen went black shortly there after and never did anything more. Pressing buttons didn't seem to help. However a "adb devices -l" did seem to indicate my phone was connected still; though "unauthorized" for usb debugging from my computer. I started googling around and found this thread which frightened me even more. I looked in the USB device list on my MAC and saw that Vendor ID and Manufacturer was Google Inc still, and not the QUSB stuff.

So, I worked up enough courage to hold down the power button and it eventually reset and showed the Google boot screen and came up just fine. I checked the settings and it shows that Oct 2021 security update was applied.

I'm waiting for the Pixel 6 Pro launch next week. Now I'm wondering if I should choose to trade this thing in (the selfie camera lens is FULL of dust) or just keep it and wait for the Class Action suit to maybe get some more value out of it? Any suggestions on that decision?

ji...@gmail.com <ji...@gmail.com> #759Oct 12, 2021 10:04PM

imo trade it in esp if you can get more than market value, if you were
going to upgrade anyway.

Even though Nexus class action suit netted between $5 to $400 for the
bootloop defect,
there are mitigating possibilities, a) if the suit successfully goes to
trial, b) the case wins, and
c) if Google's Arbitration Agreement is opted out, or enforceable.

If you purchase a new Pixel today, notice you are forced into agreeing to
arbitration agreement *upon purchase*.
You then have 30 days to opt-out, make sure you opt-out to fully retain
your power to join a class action case if necessary.

Nexus case source:

https://topclassactions.com/lawsuit-settlements/consumer-products/electronics/nexus-class-action-settlement-gets-final-approval/

On Tue, Oct 12, 2021 at 5:52 PM <buganizer-system@google.com> wrote:

- Show quoted text -

jo...@gmail.com <jo...@gmail.com> #760Oct 13, 2021 08:28AM

Same here. My phone is bricked out last night and Google don't do anything. Your warranty is expired :-(

gl...@gmail.com <gl...@gmail.com> #761Oct 13, 2021 10:30AM

another brick in the wall. Contacted Google support and was told the Pixel 3 XL is Out of Warranty and I can contact their local support service center for an out of pocket repair cost. This is completely unacceptable. **1.Phone was working. 2. Connected to charger overnight. 3. Woke up to a phone that displays nothing on the screen. 4. Shown as QUSB_BULK_CID device within Windows.** I've had every almost every Google phone from the Nexus and Pixel line and this kind of of customer experience is falling well below my expectations.

dr...@gmail.com <dr...@gmail.com> #762Oct 13, 2021 04:41PM

Bricked pixel 3 last night... so sad... like everyone else was holding out for the pixel 6

ki...@gmail.com <ki...@gmail.com> #763Oct 13, 2021 09:49PM

Same problem here. We have 2 x Pixel 3 that are dead. We have 1 more that is still working, and auto updates have been turned off, just in case.

If this was Apple, it would be headline news on all the tech and news sites, and the company would definitely offer some sort of compensation.

A perfectly working phone one day, and a brick the next day, due to some sort of pushed automatic update, is unacceptable. In or out of warranty.

an...@gmail.com <an...@gmail.com> #764Oct 14, 2021 12:52AM

Pixel 3XL was on, battery at about 50%, and then turned off. Showed the white screen with Google logo at the centre, then shut off. Won't charge, won't turn back on. Laptop makes a noise when I connect to laptop but that's it.

wr...@gmail.com <wr...@gmail.com> #765Oct 14, 2021 03:23PM

Pixel 3 was fully working and charged at 0600. When I woke up at 0900 it was to a bricked phone, showing as QUSB_BULK_CID device in Windows. I was holding out for the 6 but now? We'll see.

bs...@gmail.com <bs...@gmail.com> #766Oct 14, 2021 04:41PM

Woke up this morning to the same issue. AOD was on but showed 3:50 AM and fully charged. I held down the power button to wake it up and it went dark and has remained dark every since. Connecting to PC does nothing but shows QUSB_BULK_CID like everyone else here.

Not under warranty anymore, of course, but perfectly functioning phones are just bricking overnight??? This does not sound like a hardware issue.

pe...@gmail.com <pe...@gmail.com> #767Oct 14, 2021 05:58PM

This happened to me last week with a regular Pixel 3. I got the same rigmarole from customer support with no satisfaction. What a disgrace. It really seems to be picking up bricks as we near the P6 release.

wd...@gmail.com <wd...@gmail.com> #768Oct 14, 2021 06:19PM

#694 back again for an update. I had a Pixel 4 XL that was still under warranty. Sent it back 15 days ago (calendar days) and it was just repaired and is being shipped back to me at some point in the coming days. I'm one of the "lucky" ones who was able to get a repair, but it took almost 3 weeks and too many hoops to jump through. After this experience, I've decided that I am *DONE* with android. It's a shame because I was a die-hard google/android "fanboy" for the past 10+ years, starting with the o.g. nexus. I decided to take the offer to trade in my phone (working or broken) for a new iPhone. For all the people who have P3's that are dead and out of warranty, I'm sorry that happened to you. The way Google treated you is unfair and has made me turn to the dark side and jump to iOS. I'll never buy another google product again. All they had to do was own it and they couldn't do that, so bye-bye Android. Wish me luck while I learn how to use this stupid iPhone.

ah...@gmail.com <ah...@gmail.com> #769Oct 14, 2021 07:53PM

My Pixel 3 just turned into a brick today. Working perfectly until update.

ri...@googlemail.com <ri...@googlemail.com> #770Oct 14, 2021 10:11PM

Hi,

I am not affected. I just am interested about this issue.

May be this article is helpful?

https://www.getdroidtips.com/fix-slot-unbootable-load-error-on-pixel-devices/

Message last modified on Oct 14, 2021 10:13PM

oz...@gmail.com <oz...@gmail.com> #771Oct 14, 2021 10:20PM

@#770 Nope - the issue here is that you can't even get to the bootloader screens. It's stuck in Qualcomm Emergency Download (EDL) mode, which renders it as a basic USB device only - no screen, no way of inputting anything, no way of going to TWRP or anything else. The only software solution would be for Google to release a Qualcomm signed firmware in the appropriate EDL format that they must use internally to flash the phones in the first place.

an...@gmail.com <an...@gmail.com> #772Oct 14, 2021 11:41PM

After we'll over a month of persistent contact on my end, Google finally agreed to replace my bricked 3XL. I kept contacting them via Twitter, DMs, email, and chat support and finally spoke with a supervisor who escalated it and agreed to replace the phone outside of warranty. It should not have taken that much effort but I'm glad at least they're taking some ownership, so don't let them tell you they don't know it's an issue and that they aren't replacing phones!

bo...@gmail.com <bo...@gmail.com> #773Oct 15, 2021 11:56AM

Woke up to a bricked pixel 4, showing as QUSB_BULK_CID on 10/12. After talking with tech support and going though all the usual troubleshooting steps to try and get it to restart and go into the bootloader, they insisted that the screen needed replacing. Support would not acknowledge that it wouldn't appear as a QUSB_BULK_CID if it was just a screen issue and that it was something that they caused via an overnight update.

li...@gmail.com <li...@gmail.com> #774Oct 15, 2021 01:19PM

Same problem over here with Pixel 3 XL, 13/oct bricked overnight. Unresponsive, no combination of buttons works, and in my pc shows as QUSB_BULK_CID:XXXX_SN:XXXXXXXX also. :(

tm...@gmail.com <tm...@gmail.com> #775Oct 15, 2021 01:32PM

My Pixel 3XL bricked yesterday. Attempted reboots, attempted to charge and reboot, nothing. When plugged into a comp I get the same QUSB_BULK_CID showing.

re...@gmail.com <re...@gmail.com> #776Oct 15, 2021 06:50PM

My Pixel 3XL bricked itself this morning at around 11:50AM. The phone was working fine all morning. I started to the the LastPass application. The phone completely froze and immediately went to a black screen. The phone tried to immediately restart itself and got to the bootloader screen and proceeded past that. Once it went passed the bootloader screen, the screen went black again and the phone turned off. The phone is completely unresponsive to holding down the Power button or Power + Volume down for short durations (<5 seconds) or long durations (longer than 32 seconds). The screen does not illuminate and the phone is cold to the touch. I do not think the phone is handshaking with the google power adapter and not charging.

When plugging the phone into Windows 10, the phone shows up as QUSB_BULK_CID:<redacted>. Device manager says: The drivers for this device are not installed. (Code 28) There are no compatible drivers for this device. To find a driver for this device, click Update Driver.

ga...@gmail.com <ga...@gmail.com> #777Oct 16, 2021 01:42PM

All,
I have a glimmer of hope from Google. I've been going back and forth with their tech support for 3 weeks now. Just in the last day or two, the tech rep has said that she is checking with her resources to continue looking into my case. She said she'd get back with me in the next 24-48 hours. I have linked her this tread and a few other news articles on the issue during our conversations. She said that she isn't allowed to comment on 3rd party news articles but it seems like Google is aware that it's being reported on.

an...@gmail.com <an...@gmail.com> #778Oct 16, 2021 03:16PM

I've been asking for support since May. this is my report

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

ko...@gmail.com <ko...@gmail.com> #779Oct 16, 2021 07:05PM

Guess I'm joining the ranks here. Happened overnight, thought I was out of batteries, but not the case. Unresponsive phone, get the QUSB_Bulk reading when connected to PC. Hope a solution is found for this as soon as possible.

fi...@gmail.com <fi...@gmail.com> #780Oct 16, 2021 07:43PM

Hey, my wife's Pixel 3 was bricked today. It worked without any problems, everything on the phone is stock, it wasn't rooted or anything like that. Suddenly it stopped working, the screen is black, the buttons and their combinations do nothing. When connected to PC it shows up in device manager as QUSB_BULK_CID:XXXX_SN:XXXXXXXX. I have a Pixel 5 and I'm looking forward to the Pixel 6, but I guess I'll have to really think twice about staying with a Pixel device (I was a big fan, but from what I see here, I can't recommend a Pixel phone to anyone anymore).

sc...@gmail.com <sc...@gmail.com> #781Oct 16, 2021 10:31PM

Pixel 3XL bricked instelf this morning. Was driving with my phone connected via Bluetooth to my car with Spotify playing music. Phone randomly froze, then went to a black screen. It's been on a charger all day. Tried rebooting with just the power button as well as every other physical button combination. No luck. I'm also seeing the device as QUSB_BULK_CID:XXXX_SN:XXXXXXXX in my device manager. Was really considering a Pixel 6 Pro, but if my device is going to brick itself in just under three years, I may be considering phones from the competition.

ru...@gmail.com <ru...@gmail.com> #782Oct 17, 2021 12:40AM

Just noticed: #9 + # 552 + #781 bricked while connected to Spotify

ru...@gmail.com <ru...@gmail.com> #783Oct 17, 2021 01:54AM

: #9 + # 552 + #781 bricked while connected to Spotify
Also #188 + #200 +#548+ #599 +#672 bricked while playing MUSIC

on...@gmail.com <on...@gmail.com> #784Oct 17, 2021 02:38AM

Mine bricked after snoozing an alarm. Maybe it has something to do more with playing sound after a specific update?

al...@gmail.com <al...@gmail.com> #785Oct 17, 2021 07:19AM

My pixel 3 also bricked overnight just a day ago. I was waiting for the Pixel6 launch to see if it's a good option to upgrade, but now I'm not so sure.

va...@gmail.com <va...@gmail.com> #786Oct 17, 2021 03:41PM

My stock Pixel 3XL bricked overnight Oct 11, 2021. Woke up to a dead phone, thought it was a battery problem. I took it to UBreakiFix and they suspect it is a motherboard issue, confirmed it was not the battery. When I plugged it into my PC, it pops up as QUSB_BULK in the Windows Device Manager.
While I've experienced issues since the beginning (bought it Nov 2018 with speaker sound distortion, camera lagged or froze intermittently), I did not expect a flagship phone to suddenly brick itself. Can't even recover some of the data that I didn't get a chance to back-up. Previously a Pixel fan (mainly got it for taking photos), but never again!! Won't be recommending Pixels to anyone in the future. Such unreliable devices.

ph...@gmail.com <ph...@gmail.com> #787Oct 17, 2021 07:23PM

My Pixel3XL bricked overnight. Plugged it in at 30% power and it was charging when I went to bed. Woke up to a black screen. Tried 3 different wired chargers and a wireless charger and nothing

to...@gmail.com <to...@gmail.com> #788Oct 17, 2021 07:30PM

My Pixel3XL bricked today, october 17th
When I plugged it into my PC, it pops up as QUSB_BULK in the Windows Device Manager.

pe...@gmail.com <pe...@gmail.com> #789Oct 18, 2021 01:18AM

My Pixel 3xl quit while charging. Phone had not been tampered with in anyway and was factory stock. Just went to use it and it was dead...no screen, no sound, nothing. I can hear my computer recognize it, but that's it. Its a brick, what a shame as I really enjoyed it. I guess its in the EDL mode. If google would just send out a way to fix these phones.

pa...@gmail.com <pa...@gmail.com> #790Oct 18, 2021 02:43AM

https://issuetracker.google.com/issues/192008282#comment733,
"I wonder if anyone running a custom ROM is experiencing the same issue.
After a few years when my phones start to get older, I like to breathe new
life into them with a custom ROM... I didn't do it this time (was running
the developer's version of 12), but I'll be that I could have "saved" my
phone that way."

Since my Pixel 3XL has yet to brick, and since I purchased a OnePlus 9 Pro, because sorry google, not giving you any money for the Pixel 6 pro I had planned on buying, not with this sort of treatment for existing customers (also canceled google fi and moved to Mint Mobile) - anyway, I figured I'd test it out. Since a single pixel 3XL that hasn't bricked yet isn't really a representative sample, there's quite possibly nothing to learn from this. But since I do require a backup phone, I figured I'd give it a shot. Installed LineageOS 18.1 just now. Running fine.

Only time will tell. And really, until google actually figures out and explains exactly why this failure is happening, time may not tell.

But one this is for sure, I'm never dropping a dime on google phones or service, ever again.

mi...@gmail.com <mi...@gmail.com> #791Oct 18, 2021 02:10PM

My Pixel 3 bricked last night with same exact symptoms as all above. No modifications, no problems otherwise. I've been quite set in my ways with my Google phone and other integrated devices in my home. What a shame.

jb...@gmail.com <jb...@gmail.com> #792Oct 18, 2021 02:54PM

I am now victim to this bricked issue as of yesterday, 17 OCT 2021. Google team, please help us. The previous noted attempts at resolution were unsuccessful.

ti...@gmail.com <ti...@gmail.com> #793Oct 18, 2021 03:23PM

This is the issue Pixel 3 and 3XL owners are currently suffering from:

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

We need an official statement from Google on what the fix will be.

On Mon, Oct 18, 2021, 10:55 AM <buganizer-system@google.com> wrote:

- Show quoted text -

ch...@gmail.com <ch...@gmail.com> #794Oct 18, 2021 04:34PM

My Pixel 3 XL died on 13th October.
I contacted Google support, but they told my that my device is 2,5 years old and now out of warranty.
So they did not offer anything. This is a very unlucky customer experience.

sm...@gmail.com <sm...@gmail.com> #795Oct 18, 2021 04:48PM

My wife's Pixel 3 XL bricked on the morning of October 6th at 4:41am, per the last known time Google saw the phone and location. I tried all the normal button combinations but just like everyone else, only Windows chimes in to tell me that it is a QUSB_BULK device now.

li...@gmail.com <li...@gmail.com> #796Oct 18, 2021 05:35PM

My Pixel 3XL dies on 15th October. Last backup was just past 5:00am and I can't get it to start. As above, same QUSB_BULK ID and nothing more than that. Particularly frustrating when relying upon it on holiday for Android Auto routes and other things! Tried Google support but nothing offered as just over two years old. Was looking forward to seeing the Pixel 6 but am more likely to take my business to another manufacturer now.

on...@gmail.com <on...@gmail.com> #797Oct 18, 2021 08:15PM

Just wanted to update those on the thread with my issue. After going back and forth with Google support since Thursday, I've been offered a free replacement device despite it being out of warranty. No idea what device yet, but a replacement none-the-less. I do need to send the device back to them as part of the replacement, but since the device is bricked anyway I don't mind. Honestly, they probably want their hands on as many of these as possible to figure out what happened.

My suggestion is to not quit at your first NO from the first line of support. They ultimately don't have any power and are following a script, one that says the device is out of warranty. Ask to speak to the next level of management in your case. Make sure to outline exactly what happened when your device crashed, and mention the EDL issue. Google is unlikely to take action on this proactively, so we need to be loud enough to be heard. Otherwise, they are likely to face another class-action like the Pixel 1, and the right people need to hear this, not just the frontline customer service reps.

Also, I was told during my call (second call actually, after 2 chats), that Pixel device support is not handled by the customer service phone or chat. It is only managed via email. I don't know if you can email them directly without a rep referring you to them, but here is the email all my support issues went through: device-support@google.com

Good luck everyone! I'll let you know if things don't work out as promised.

ga...@gmail.com <ga...@gmail.com> #798Oct 18, 2021 08:50PM

All,
I was also just contacted by Google support and offered a device replacement. I have been going back and forth with them for a couple of weeks and was always respectful. It seems Google may finally recognizing the issue.

ma...@mattlovett.com <ma...@mattlovett.com> #799Oct 18, 2021 09:55PM

My phone is also stuck in EDL mode it happened about a week ago. I have been unable to get any tech support from google other than pay Ubreak for a new mobo.

bi...@surgeons.org <bi...@surgeons.org> #800Oct 18, 2021 10:24PM

Comment has been deleted.

Message last modified on Oct 18, 2021 10:24PM

zo...@gmail.com <zo...@gmail.com> #801Oct 18, 2021 10:26PM

This happened to my phone overnight - was fine when I plugged it in to charge, dead screen of misery this morning. Am so unimpressed. Tried the various troubleshooting options without success. Get a sound notification when connected to laptop, but cannot find the device, even under the code/descriptor others have suggested. I've loved my Pixel 3XL, but seriously considering returning to Samsung now. Updated software last week (I think). This is seriously appalling behaviour - stop forcing us to be such a ridiculously tech-consuming society and make things that last for years and/or can be easily repaired by the owner. Seriously.

mi...@gmail.com <mi...@gmail.com> #802Oct 19, 2021 05:41AM

10/18/2021 phone died all of the sudden while playing music over bluetooth speaker. Pixel 3 xl . has been a great phone. was in beta program, no issues. Tried the 3 button reset while plugged in, with simcard, without sim card, while plugged in and not. Nothing bringing it back to life. will let it sit and see for the battery to drain as it was at 70% power and see if plugging it back in after its dead would bring to life.

en...@gmail.com <en...@gmail.com> #803Oct 19, 2021 05:44AM

Another dead pixel 3xl. while on vacation :( all pictures lost.

phone was not damaged or dropped. died while listening to music.
tried 3 button reset, not powering up any more.

This is not acceptable that software update can brick a device, and that there is no repercussions or resolution or honoring or replacing of the device by the cause.

bi...@gmail.com <bi...@gmail.com> #804Oct 19, 2021 09:46PM

Add another one to the list. Dead pixel 3. Plugged in for the night and went back to check it a little later and it would not respond at all. Same QUSB_BULK_CID... message when plugged in to the computer.

in...@gmail.com <in...@gmail.com> #805Oct 20, 2021 12:42AM

Same issue. In my pocket, half battery charged, just took it out and it was completely dead and unresponsive regardless of how I try to reboot or power it on. When I plug it into my laptop I see it as the QUSB device in the device manager.

ga...@gmail.com <ga...@gmail.com> #806Oct 20, 2021 01:03AM

Just a follow up to my post #798 on the replacement device. I received my RMA info today and mailed the phone in. The Google rep said I would receive a refurbished pixel 3 XL. I did pre-order the Pixel 6 today and will likely just sell the refurbished phone.

To all those still chatting with Google support, keep trying! Link this thread to them, be respectful, be honest, and keep asking what they can do to remedy the issue. I did take mine to a ubreakifix store but they tried to swap the battery and said it couldn't be fixed after that. I was honest with ubreakifix as well on what the issue was with details from this thread.

ph...@gmail.com <ph...@gmail.com> #807Oct 20, 2021 09:24AM

My Pixel 2 bricked on Saturday mid day while I was using it. It locked up, became unresponsive and none of the button combos for a restart did anything. It was 2/3 full battery when it happened and I have since been able to at least get a portable battery to illuminate while it charged but not any more. Have plugged into my Mac but I can't find the QUSB_BULK_CID

Following day, my partner's P3 froze up. She chucked it on charge for a while and thankfully it came back to life. Auto updates are off now and fingers crossed this one doesn't go down too.

se...@gmail.com <se...@gmail.com> #808Oct 20, 2021 12:48PM

Same issue. Happened last week. Time for a new phone and expense that was otherwise unnecessary at this time.

sp...@gmail.com <sp...@gmail.com> #809Oct 20, 2021 05:55PM

I know this doesn't help the situation at all, but I just saw that you can buy refurbished Pixel 3 from the google store for $249/$279. The fact that taking it to ubreakifix, and getting charged $400 for a motherboard replacement tells me it's not worth it at all.

Definitely don't take it to ubreakifix, it's not worth it. Google needs to replace everyone's defective phones for free.

jo...@gmail.com <jo...@gmail.com> #810Oct 20, 2021 08:51PM

my phone was sitting on a table today, went to pick it up, and it was bricked like all the other devices in this thread. I have a pixel 3 that is just over two years old. when plugged in I get the QUSB in my device manager

ro...@gmail.com <ro...@gmail.com> #811Oct 20, 2021 09:43PM

My spouse's phone bricked last night. It is stuck in EDL/QUSB Mode. What is Google going to do about this? A perfectly good phone shouldn't fail on an overnight update.

du...@thedatabender.com <du...@thedatabender.com> #812Oct 20, 2021 09:49PM

My 3XL bricked while camping back in April. Just spent an hour chatting with support and they refuse to replace outside of warranty only directed me to ubreakifix. :(

al...@gmail.com <al...@gmail.com> #813Oct 20, 2021 09:50PM

Ok yeah phone sucks pixel 2 frozen useless no remedy

On Tue, 19 Oct 2021 at 2:44 AM <buganizer-system@google.com> wrote:

- Show quoted text -

--
*🌟 Blessings to you and yours 🌟*
* Patrick N. Hall LMSW CPC*
* (505) 457-7040*
* (505) 397-2525*
* pathall123@hotmail.com <pathall123@hotmail.com>*

ga...@gmail.com <ga...@gmail.com> #814Oct 20, 2021 09:52PM

You need to take your phone to ubreakifix and tell them what's going on. Let them know that you just need a report saying it's not the display or battery and that they are unable to fix it. Take that info back to Google.

ai...@gmail.com <ai...@gmail.com> #815Oct 21, 2021 02:00AM

Same happened to me back in april. Pixel 3, gets the QUSB_BULK_CID plugged into windows.

ia...@cazabat.com <ia...@cazabat.com> #816Oct 21, 2021 03:22AM

Got my out-of-warranty replacement Pixel 3XL yesterday. My original post was #459, followed up by #728. As I said in my last post, be courteous, but firm. State that this is their fault, not your own.

RMA number: RMA51612316 Case ID: 1-9241000031851

I hope this information helps someone. Keep pressing them, be truthful, be nice.

cr...@gmail.com <cr...@gmail.com> #817Oct 21, 2021 11:34PM

Another Pixel 4 suffering from EDL. The phone was working great the evening of October 19, then the morning of October 20, the phone was unresponsive. Confirmed it is stuck in the EDL.

An...@Joncas.net <An...@Joncas.net> #818Oct 22, 2021 01:40AM

Pixel 3a stuck in EDL. Confirmed with Windows device manager. Opening case.

cg...@gmail.com <cg...@gmail.com> #819Oct 22, 2021 03:43AM

In Canada, the representative from an escalated support.

Thanks for contacting Google Support.

I have checked all the further options and in this case, as the device warranty has expired, the only option we have is to get the device repaired at the authorized repair partner, here are the details:

Website:

https://www.ubreakifix.com

Phone: 1-877-320-2237

Hours
Mon-Sat: 10 AM to 10 PM PT
Sun: 12 PM to 8 PM PT

Thanks!

I have stated this is a glitch from your software update and nothing I have done. Maybe now that the pixel 6 launch has happened, google stops caring...

ni...@gmail.com <ni...@gmail.com> #820Oct 22, 2021 09:30AM

Same problem.

Was charging phone last night as always. Woke this morning to a brick. No lights, no charge indication (charges wirelessly based on lights on stand)

Plugged into computer, and QUSB_BULK_CID:XXXX_SN:XXXXXXXX shows up.

Device is stuck in EDL mode.

What's the next step?

me...@gmail.com <me...@gmail.com> #821Oct 22, 2021 01:36PM

So I actually ended up getting both the Pixel 6 and Pixel 6 Pro the other day for both my phones, a Pixel 3XL (VZ) and 4XL (AT&T). Got the Pixel 6 Pro from Google directly (with preferred care 36months) and they are giving me $125.00 for trading in my Pixel 3XL directly with Google vs VZ only offering me like $80.00.

That Pixel 6 Pro will be on my AT&T line and the regular Pixel 6 I ordered directly from VZ w/o trade in. Both of these I am able to expense out for my job. But the AT&T is primary and the VZ one is secondary/backup.

I will keep the 4XL as a backup for both, just in case history repeats itself like the current issues with the 3 XL that are ongoing.

***side note, I just checked Google Store and looks like they are only giving $80.00 now for Pixel 3XL with 128GB that powers on and no cracked screen. So my guess is that they had an influx of orders with people trading in their Pixel 3XL, for whatever reasons, and they will be sending those out to people who are experiencing the current issues with their Pixel 3XL who b*itch loud about the brick issue and then selling them as well, as mentioned above, to people who will buy "refurbished" just to get a working phone back. I have a new battery in the 3XL that is only 12 months old, so whoever gets it, at least the battery is newish.

ph...@gmail.com <ph...@gmail.com> #822Oct 22, 2021 01:44PM

Curious if this has happened to anyone since doing the Android 12 final OTA update that dropped a few days ago?

ky...@gmail.com <ky...@gmail.com> #823Oct 22, 2021 07:04PM

i also have a pixel 3 xl that has done this

js...@gmail.com <js...@gmail.com> #824Oct 22, 2021 10:10PM

This has happened to me last night, two days after upgrading to Android 12. Pixel 3 XL. It seems suspicious that Pixel 6 releasing has magically bricked my phone.

as...@googlemail.com <as...@googlemail.com> #825Oct 22, 2021 10:38PM

Another to add to the 500+ long list…

Upgraded to Android 12 earlier this week and overnight, whilst on charge, it’s gone dark in EDL mode.

du...@thedatabender.com <du...@thedatabender.com> #826Oct 22, 2021 10:45PM

All that my local UbreakIfix could suggest is trying to replace the battery and while in there see if it's the screen. Of course neither of those worked.

al...@gmail.com <al...@gmail.com> #827Oct 23, 2021 12:40AM

Can't do a bug report if you can't turn on the phone. The phone is Bricked, Dead, Non responsive. Like hundreds of others, I would like to know what google is going to do about this problem?

al...@gmail.com <al...@gmail.com> #828Oct 23, 2021 12:48AM

Why would owners of bricked Pixel 3 want to buy another Pixel? This was my last one, can't trust them.

ga...@gmail.com <ga...@gmail.com> #829Oct 23, 2021 12:56AM

#826
If ubreakifix tells you that they can't fix it, give that info to Google Support. They'll likely ask for the location, receipt, and repair number.

sh...@gmail.com <sh...@gmail.com> #830Oct 23, 2021 02:30AM

This happened to me today!!! While I was using my phone 😡 I've tried all the tricks I found, nothing works. Not at all happy about it. No way I'll buy another pixel. Done. I'm switching platforms.

sh...@gmail.com <sh...@gmail.com> #831Oct 23, 2021 02:39AM

This happened to me today!!! While I was using my phone 😡 I've tried all the tricks I found, nothing works. Not at all happy about it. No way I'll buy another pixel. Done. I'm switching platforms.*edit* Pixel 3xl. Surely expected it to last more than two years.

bg...@gmail.com <bg...@gmail.com> #832Oct 23, 2021 12:35PM

Happened to me about two hours ago. Woke up, my phone was bricked(EDL). According to Find My Device, it was last seen at 5:44am. Didn't have the phone charged but still saw that my phone was corrupted. Unacceptable.

sp...@gmail.com <sp...@gmail.com> #833Oct 23, 2021 12:55PM

My unit died last night, too. Same issue.

bu...@googlemail.com <bu...@googlemail.com> #834Oct 23, 2021 01:36PM

My pixel 3 died last night, exactly the same issue, waiting on a response from Google.

Message last modified on Oct 23, 2021 01:37PM

sc...@googlemail.com <sc...@googlemail.com> #835Oct 23, 2021 04:12PM

Aaaand same here. Just turned off while listening to music, now in EDL mode.

lo...@gmail.com <lo...@gmail.com> #836Oct 23, 2021 05:11PM

Pixel 3 bricked this morning. Same issue

ph...@gmail.com <ph...@gmail.com> #837Oct 23, 2021 05:58PM

Comment has been deleted.

Message last modified on Oct 26, 2021 12:43AM

br...@gmail.com <br...@gmail.com> #838Oct 23, 2021 05:58PM

Pixel 3 XL bricked yesterday, 10/22. Working fine one minute with > 80% battery charge, put phone down on table, picked it up 5 minutes later and no screen, no response to button clicks, nothing. Plugged into computer when got home and get the notification that the following is plugged in - QUSB_BULK_CID: . Phone was purchased in March of 2019 new.

ma...@gmail.com <ma...@gmail.com> #839Oct 23, 2021 07:59PM

I had this happen to my Pixel 3 back in September. I've contacted support multiple times since then without getting any help. The last communication I got said that my case had been escalated to "the specialist team". I'm not sure what that means, but I'm hoping they can provide a replacement.

li...@gmail.com <li...@gmail.com> #840Oct 24, 2021 02:26AM

Pixel 4XL happened overnight. Phone was off charge. Unresponsive - qusb_bulk_CID: when plugged into pc

fi...@gmail.com <fi...@gmail.com> #841Oct 24, 2021 11:58AM

It also happened on my Pixel 3 today.
It does not accept all operations, including charging, and the screen remains off.
I bought a Pixel 6 but it will arrive next week.

Google's hardware support isn't as good as Apple's.
I want improvement it.

sk...@skaccess.com <sk...@skaccess.com> #842Oct 24, 2021 02:50PM

My Pixel 3 XL is stuck in EDL Mode.

connected my phone to the OEM charger on the 22/10/2021 night, went to sleep,
woke up on 23/10/2021 morning and my phone was off. tried to turn it on, nothing.
when connecting it to a computer, it is showing as QUSB_BULK_CID:0402_SN:XXXXXXXX
contacted google support, and they redirected me to a repair company and would not do an RMA.

i ask them to escalate the issue, will see how that goes.

wo...@gmail.com <wo...@gmail.com> #843Oct 24, 2021 05:29PM

Just spent an hour chatting with support, Pixel 3 updated to Android 12 yesterday and was working fine. This morning I was listening to music and the phone just died even though it was 95% charged. It was dropped and had a corner crack last year, but all functions worked fine on the home screen. It was out of warranty in August 2020 the agent told me and suggested I take it to ubreakifix, which is an hour away from me. Went there last year to see if there was anything they could do with the corner crack and they told me they could fix it for $700, can't imagine how much they'd charge for a bricked phone! From all the people who also have had this happen, I'm beginning to think that this is just a marketing ploy to get people to buy a Pixel 6, but it is pretty stupid if it is. There is very little choice for me as I am with Spectrum mobile now (bought the phone from Verizon originally) and they told me that the Pixel 6 would not work on their network (which is Verizon, who is also selling the 6!). Spectrum also told me my Nexus 5X (which was a great phone) would not work on their network, even though it worked fine on Verizon for years. This really seems like a ploy to me, but can't figure out for sure what the end game is, except to sell more phones. I live rurally and there is no 5G for 60 miles, so that is of little interest. Can't believe after all these years of having a cell phone I am now without it...feels strange.

pi...@gmail.com <pi...@gmail.com> #844Oct 24, 2021 05:40PM

Pixel 3 XL stuck in EDL Mode...
Took the official android 12 update yesterday.. phone was working fine.
I went to sleep, and when I woke up the phone is completely dead. When connecting to PC I get: QUSB_BULK_CID:0402_SN:XXXXXXXX in device manager
Ain't that some BULLLLLLLLSHEEEET

fi...@gmail.com <fi...@gmail.com> #845Oct 24, 2021 05:52PM

As of this morning, my Pixel 3 is also stuck in EDL mode - after connecting to PC, device manager shows "QUSB_BULK_CID:0402_SN:XXXXXXXX."
Phone was working fine last night, woke up to it bricked this morning after leaving it charging overnight.

This is a stock Pixel 3 purchased from the Google store in 2018.

da...@gmail.com <da...@gmail.com> #846Oct 24, 2021 07:38PM

Same thing for me today, woke up and stuck in edl mode. Paid to have insurance replace it but this is seriously messed. up.

jr...@gmail.com <jr...@gmail.com> #847Oct 24, 2021 09:47PM

Happened to me today. Left my phone for 1+ hours while I watched football. Checked it and screen was black, wouldn't power on, wouldn't charge.
Tried all the combinations of power+down volume for 1 minute, etc...

Plugged it into the computer and shows up as: "Qualcomm HS-USB QDLoader 9008 (COM4)"

ne...@gmail.com <ne...@gmail.com> #848Oct 25, 2021 01:13AM

The same thing happened to me today, went to bed around 11pm woke up at 2 and phone was on charge and the screen was black, my smartwatch linked to the phone got a last notification at 140am but that was it. I plugged it into the computer and shows up as: "Qualcomm HS-USB QDLoader 9008 (COM4)"

sp...@gmail.com <sp...@gmail.com> #849Oct 25, 2021 01:21AM

My 3XL died last Sunday Oct 17 and my sons pixel 3 just died today Sunday Oct 24. Just wanted to add ourselves to the growing list of people this is happening to.

st...@gmail.com <st...@gmail.com> #850Oct 25, 2021 02:04PM

I have had a similar experience. I upgraded my Pixel 3XL to Android 12 in the middle of last week. The upgrade went smoothly, other than some periodic lag unlocking the device. When I woke up on Sat 10/23, the device was unresponsive. Went through the various debugging steps and saw the `QUSB_BULK_CID` in Device Manager. I spoke with Pixel Support, but their only suggestion was to take it to a an authorized repair facility 90 miles away, or mail in the device for repair, with all charges at my expense because it is out of warranty. Regardless of the fact that it appears that an official and supported software update seems to have caused the issue.

pe...@gmail.com <pe...@gmail.com> #851Oct 25, 2021 02:08PM

There has to be something that can be done about google bricking phones.

pi...@gmail.com <pi...@gmail.com> #852Oct 25, 2021 04:37PM

My Original pixel 1 just did this last night.

on...@gmail.com <on...@gmail.com> #853Oct 25, 2021 05:22PM

For those of you having the EDL issue in this thread. I wanted to tell you to not give up with Google's first "NO" on replacing your device. It took me almost a week of back and forth with their support group, but I have a replacement device arriving this week for free. Unfortunately it is a refurbished 3...which scares me it will just happen again...but it is better than nothing.

Just don't give up. If you get told no, ask to be escalated to the next level or management/support. If they say no, keep asking for the next level. Be sure to explain EXACTLY what happened when it died. Make sure to explain the steps you've taken, including if UbreakiFix looked at it. Make sure they know it has the QUSB_BULK_CID label when plugged into a computer and that it is the EDL issue. Give them links to reputable articles referencing this issue, including this thread. Basically do all the heavy lifting for them if you want this resolved. They will not do it on their own out of kindness. We need loud voices keeping the issue from being swept under the rug.

It is clear this issue is accellerating in recent months. I fully expect a class-action suit or other action by Google before long. This is a huge issue, Google knows it, but they aren't going to admit it until they are forced to.

I guess I just want you to not give up. Keep pushing for a resolution. And remember, the first-line phone and chat support has no real power to help you. They have a strict script to follow. You need to go up a level or two for help. The Pixel team is where you eventually want to end up (and they only work via email). Also, reach out through multiple channels. I did phone, chat, and even direct messaged the Made by Google Twitter account (which seemed to be the best path for getting things rolling). Good luck and don't give up!

fk...@gmail.com <fk...@gmail.com> #854Oct 25, 2021 06:57PM

Just adding my name to the list - Stock Pixel 3xl, purchased from the Google store. Bricked on 10/24, was not on the charger, at about 50% battery when it died. I am seeing the QUSB Bulk message when connected to my laptop, and haven't been able to get it to a boot screen at all.

al...@gmail.com <al...@gmail.com> #855Oct 25, 2021 07:29PM

Purchased my Pixel 3XL on October 20th, 2018. Bricked over night on the charger while I was sleeping on October 20th, 2021. 3 years to the day. The last time I interacted with my phone was at 1am to check the time. uBreakiFix deemed it unrepairable. Fighting with Google now for a repair/refurb. Trying to avoid this $481 repair fee for something I didn't do is ridiculous.

I'm losing unrecoverable data, access to my multifactor authenticator, and so much more. Any reference to the nation wide bricking is ignored by Google. Simply unprofessional and ridiculous.

oz...@gmail.com <oz...@gmail.com> #856Oct 25, 2021 10:09PM

@#855 - It is extremely unlikely that you will get back anything from your phone (authenticator, data, anything) whether Google acknowledges this or not. Any fix is very likely to involve a complete factory reset of the phone.

dk...@gmail.com <dk...@gmail.com> #857Oct 25, 2021 11:47PM

Adding to list... Pixel 3, upgraded to Android 12 then bricked. Contacted Google support, took to uBreak and all confirmed: brick. Feels like at least a credit to upgrade to new phone would be warranted since their upgrade bricked the phone.

sh...@gmail.com <sh...@gmail.com> #858Oct 26, 2021 01:43AM

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.

ro...@gmail.com <ro...@gmail.com> #859Oct 26, 2021 12:17PM

exactly the same circumstance here, attached is the BS conversation with google support

Google Support.html

74 KB

View

Download

cb...@gmail.com <cb...@gmail.com> #860Oct 26, 2021 02:50PM

My phone turned into a brick on my drive to work this AM. It was fully charged and not to hot or too cold, I got to work and NOTHING! This is ridiculous, I could understand a hardware issue due to age but there is absolutely NO WAY a software issue literally shutting down our phones and making us lose everything on them should be happening in this day and age. This is not a virus or malware, this is something inherently wrong with the Android Software and the Pixel 3.

je...@gmail.com <je...@gmail.com> #861Oct 26, 2021 04:27PM

My phone also became a paper weight overnight while I was sleeping. I got to tier 2 support and they also told me that I'll have to pay someone to fix my phone because Google's update broke it. It probably won't help, but I'll be filing a complaint with my state's AG because what they're doing is essentially theft. They stole a perfectly fine device from me and are saying "Sure, you can have it back if you pay us what you paid for it when you first bought it."

th...@googlemail.com <th...@googlemail.com> #862Oct 26, 2021 04:52PM

Here's another bricked phone. Same issue as everyone else. It has been updating just fine prior to this, and I do not believe it was updating overnight. Checked the charger, cable and all options there, no response. I have followed all of the steps listed above with no response from the phone.

gn...@gmail.com <gn...@gmail.com> #863Oct 26, 2021 08:32PM

I have the same issue.

mc...@gmail.com <mc...@gmail.com> #864Oct 26, 2021 08:57PM

Just as a data point towards the hypothesis that this bricking is being
caused by a software issue (or perhaps I have just been lucky so far): I
turned off automatic app software updates weeks ago. 65+ app updates are
waiting now. I have not installed the last security update. I have not
updated to A12. My Pixel 3 is still running ok at this time. Sure wondering
how long I can keep this up.

On Tue, Oct 26, 2021 at 1:32 PM <buganizer-system@google.com> wrote:

- Show quoted text -

ni...@gmail.com <ni...@gmail.com> #865Oct 26, 2021 10:09PM

[SOLUTION] - Possibly

Google has offered me an 'Exception Replacement'. It was rather easy to get to, but again your mileage may vary (I'm in canada, so I guess it's Kilometrage)

1. Engage google support chat (usually a bot + human for level 1 stuff) let them and the bot run through the script and answer as required. Eventually they will run out of script. Save the chat ID.
2. They will hopefully (especially if you're courteous and a normal human being) escalate you to tier 2. I asked to be escalated as "I had lots of previous google devices, and was literally communicating on my nexus 5 which still worked". I asked for customer retention.
3. Eventually they will recommend that you either send it in, or take it to "youbreakifix" or a similar authorized repair location. Take it to one of those, and get an estimate for repairs. If you don't think it's worthwhile, don't get it repaired, and re-initiate the conversation referencing the chat ID.
4. Once you let them know that it isn't economically viable to repair the phone, hopefully they will initiate an exception and send a replacement. You could indicate that's what you want. They should send you an email.
5. Work with them, and hopefully you'll luck out.

Best of luck

js...@gmail.com <js...@gmail.com> #866Oct 27, 2021 12:52AM

Google Support refused to escalate me to the next tier. Only after 20 minutes of back and forth and me asking almost a dozen times, did they escalate me.

My previous support ticket apparently they stopped replying to.

Google support is such a joke.

ir...@gmail.com <ir...@gmail.com> #867Oct 27, 2021 03:00AM

In the same boat. Happened overnight October 17-18. Plugged in to go to bed, woke up to black screen unresponsive. Pixel 3XL out of warranty in otherwise mint condition. Showing up as same thing in device manager as others. +1 to Google Support not being much help other than recommending ubreakifix.

st...@gmail.com <st...@gmail.com> #868Oct 27, 2021 03:34AM

I too have a Pixel3 that I found dead when I woke up.

go...@gmail.com <go...@gmail.com> #869Oct 27, 2021 07:11AM

I would LOVE if people would say if their dead phone was on stock or custom ROM: that would give us statistical power to maybe avoid bricks in a lot of phones in the future!

PLEASE DO INCLUDE INFO IF YOUR NEXUS WAS ON STOCK ROM OR CUSTOM ONE

re...@gmail.com <re...@gmail.com> #870Oct 27, 2021 08:48AM

This happened to me also this week but I have an OnePlus 8T (stock rom). After I got an OTA my phone appeared really slow (but I got the notification it was successfully updated), so I decided to reboot once more. After the reboot the screen stayed black and appears dead. But connected to Windows it was recognized as QUSB_BULK_CID:XXXXSN:XXXXXX I also found out that when pressing vol + AND vol - AND power for more than 10 seconds I could enter fastboot mode. But from there I only could 'power off' and 'reboot into fastboot' mode. 'Start' and 'Reboot to recovery' resulted in the black screen again.

But in the end I could resolve this issue and now I have a working phone again. What I did: installed the correct Qualcomm drivers, after doing so my phone was recognized in Windows Device Manager as 'Qualcomm HS-USB QDLoader 9008 (COM4)'. And then I used the 'MSM Download Tool', this can be a specific OnePlus tool (I don't know for sure) but maybe there is also such a tool for Pixel phones....?

oz...@gmail.com <oz...@gmail.com> #871Oct 27, 2021 09:19AM

@#870 Yes, that's the tool we would like Google to release for the Pixel 3. It would solve the problem.

ow...@neko-logic.com <ow...@neko-logic.com> #872Oct 27, 2021 09:58AM

Having a tool to hose the OS would only be a temporary fix, since whatever is in the code that is causing this problem will reoccur, and we don't know for sure which update (if it is an update) causes it to brick. Resetting to a lower version of the OS will expose your device to security issues so just not updating from whatever factory version you flash to is not an ideal solution.

Google has to find out what is causing this, create a fix for it, then deploy it to protect any further updates. Since they seem to be asking some users to send in their bricked devices, it would seem that's what they're working on (although how many engineers they've assigned to this is anyone's guess). Debugging something that is intermittent and not easily repeatable is a difficult task, so this may take some time. I very much doubt this is deliberate and although it seems to mostly affect Pixel 3s, it seems from this thread that a few 4s and 5s are also affected, the 6 doesn't use a Qualcomm processor so hopefully it won't be affected by this, but I wouldn't rule anything out at this point.

My Pixel 3XL bricked itself overnight at the start of September, stock Android 11, locked bootloader. I'm an Android developer, and using vanilla OS is kind of important to me (I've had various Google phones since the Nexus One, and I've always liked them), so I hope that Google resolves this soon. I'm waiting to upgrade to the 6, but I won't do so until they have some kind of fix.

ni...@gmail.com <ni...@gmail.com> #873Oct 27, 2021 02:35PM

@#870 @#871 not the tool itself is the problem (https://github.com/bkerler/edl would work, too) but the signed EDL / firehorse image that Google won't release.

mi...@gmail.com <mi...@gmail.com> #874Oct 27, 2021 02:35PM

In case this reminder helps anyone else: I gave up on google helping with our 1.5yr old stock pixel 3 that died with this issue "out of warranty" back in May. I remembered I had purchased it on the Costco Citibank card that extends the warranty. Citi came thru after providing all their requested documentation (receipts, photos of perfect phone that wouldn't turn on, and the UBreakIFix written description of being non-repairable). I'm still mad at google on this, but I'm very happy with Citi right now! Hope this helps as a reminder for someone else because it took me a while to remember I had that coverage.

de...@gmail.com <de...@gmail.com> #875Oct 27, 2021 06:22PM

Exact same issue is affecting Pixel 4/4XL - mine bricked last night, same exact issues. Same "QUSB_BULK_CID" message when plugged in via USB to a PC.

FIX THIS, GOOGLE!!

me...@gmail.com <me...@gmail.com> #876Oct 27, 2021 08:48PM

Got my new Pixel 6 for replacement of my VZ Pixel 3XL, which is still running after turning off updates in developer mode and google play store. Hoping it will live until the weekend when I have time to swap out and migrate over to the new phone. Google giving me $125 for trade in, so at least I get what is cost me for a new battery last year to replace the bloated one. UBreakIFix charged me $60 I think and like 90mins, so get paid for my time as well.

la...@gmail.com <la...@gmail.com> #877Oct 27, 2021 10:57PM

Just like #875, my Pixel 4 bricked this morning around 3AM EST.

er...@gmail.com <er...@gmail.com> #878Oct 27, 2021 11:46PM

I purchased my wife's Pixel 3 from Verizon on November 22, 2018.

It died unexpectedly while wirelessly charging October 27, 2021. Yes, this is starting to sound like a epitaph or obituary.

It was at about 80% when she looked at it last, and then it was just dead and would not turn on. We've tried Power + Volume Down both plugged in to AC power and not plugged in.

It's never been rooted (probably not even possible on the Verizon model) nor have we installed any of the beta versions of Android. She took the official Android 12 OTA within the past week.

Nothing we've done so far has worked to coax any sign of life out of the phone.

la...@gmail.com <la...@gmail.com> #879Oct 28, 2021 12:54AM

I think it's interesting many of us are reporting this issue happening last night...I don't feel like that's a coincidence...

js...@gmail.com <js...@gmail.com> #880Oct 28, 2021 01:15AM

I've created two tickets, and two have been escalated. The "supervisors" stop responding after one initial email. I don't know how that's OK, to just stop replying after one message.

I've sent them responses with this link, they don't even acknowledge it. I called UBreakIFix and they said "don't bring it in" because they can't actually fix it, and that they are getting flooded with this problem all week.

I told Google this, their response? "Contact UBreakIFix and they can fix it, they're the manufacturer". No, they're not the manufacturer. and they're not even reading the words I'm writing. I'm sure you guys are having the same experience. Terrible.

ge...@gmail.com <ge...@gmail.com> #881Oct 28, 2021 01:55AM

I've managed to keep my 3xl running with a different launcher app after
having some issues before but just the other day my phone started having
Bluetooth and wifi issues again after working flawless for at least a few
weeks. Really weird

On Wed, Oct 27, 2021, 8:16 PM <buganizer-system@google.com> wrote:

- Show quoted text -

jo...@gmail.com <jo...@gmail.com> #882Oct 28, 2021 12:42PM

My Pixel 3 died this morning at about 5am CDT. It was plugged into it's charger with a full battery. At about 4am I watched a few videos, put my phone down, and then a little after 5am I found it in what appears to be an off state. None of the restart methods work and there's no indication from the phone when connected to chargers. When it's plugged into my computer a device appears in Device Manager with the description "QUSB_BULK_CID: ..." (screenshot attached).

I have about 16 bug reports saved over the phone's life, with the latest in the end of May (bugreport-blueline-RQ2A.210505.002-2021-05-29-14-33-05).

Pixel3 Device Manager 2021-10-28 072504.jpg

92 KB

View

Download

al...@gmail.com <al...@gmail.com> #883Oct 28, 2021 01:04PM

Add another one to the list, when it first happened I thought "Oh well, it's has a decent run" but now that I see it's likely a software issue and one that's not been handled well I'm mad about it.

I don't think I'll be going for another pixel, although I've been very happy with my 3 until this.

mc...@gmail.com <mc...@gmail.com> #884Oct 29, 2021 12:17AM

Just as a data point towards the hypothesis that this bricking is being caused by a software issue (or perhaps I have just been lucky so far): I turned off automatic app software updates weeks ago. 65+ app updates are waiting now. I have not installed the last security update. I have not updated to A12. My Pixel 3 is still running ok at this time. Sure wondering how long I can keep this up.

tc...@gmail.com <tc...@gmail.com> #885Oct 29, 2021 03:43PM

Pixel 3 bricked overnight 10/28 on charger. All the data and authenticator inaccessible because it's stuck in EDL mode. Displaying QUSB_BULK_CID:xxxx_SN:xxxxxxxx when plugged into computer.

Release the firehose so we may potentially fix this.

me...@gmail.com <me...@gmail.com> #886Oct 29, 2021 04:31PM

Pixel 3xl bricked overnight on 10/28 while sitting on the dining table. Android 12 update was installed 3 days prior. This phone has been well taken care of and was fully charged before it decided to brick over night.

an...@gmail.com <an...@gmail.com> #887Oct 29, 2021 05:38PM

when will you deign to give an answer? my case is 193624145

de...@gmail.com <de...@gmail.com> #888Oct 29, 2021 05:44PM

I think it's safe to say that Google has swept this under the rug, and will not be replying to any owners here.

I have begun contacting media outlets and linking to this page in hopes of someone picking up the story.

Thousands of bricked devices over a short period of time known to be caused by and ignored the manufacturer is patently unethical and anti-consumer.

pa...@gmail.com <pa...@gmail.com> #889Oct 29, 2021 05:47PM

Nope, they seem to hope that all will just be forgotten and nobody will ever force them to give a shit. It's incredibly shitty to hide behind "out of warranty and not enrolled in device protection" rather than even admitting the issue is real. Some real garbage behavior, and the really shitty part is they'll likely get away with it with no real repercussions.

je...@gmail.com <je...@gmail.com> #890Oct 29, 2021 05:50PM

Google just returned my bricked pixel 3xl. They offer not to repair it as
it will cost me almost $500.
No replacement offer even though I bought it directly from their store due
to being out of warranty.
Not even a gift card to compensate me for ruining a perfectly running phone
prior to the software update, and
Not even an apology or acknowledgment of their mistake.
I don't think calling and bugging customer support is worth my while. They
are probably suffering from irate customers and anyway underpaid to handle
this fiasco.
What is the next step for all of us? Should we file a claim to a claim's
court so we can all be compensated?

On Fri, Oct 29, 2021 at 10:38 AM <buganizer-system@google.com> wrote:

- Show quoted text -

on...@gmail.com <on...@gmail.com> #891Oct 29, 2021 06:15PM

I finally got my replacement in the mail yesterday. It took me probably 10+ hours of back and forth over a week, constantly asking for escalations before I was offered a replacement. TONS of heavy lifting on my part. (see previous posts in this thread). The shipping took almost two weeks from when they shipped it (likely due to a combination of shipping issues globally, and the launch for Pixel 6). Try reaching out to Made By Google on Twitter through a private message, that seems to be what finally got the ball rolling for me (include your case number from customer service calls, chats, or email as well).

Of course they sent me another Pixel 3...so we will see if this one craps out too, but it is better than nothing. My dead one is on it's way back to them for analysis.

Frankly everyone here is right. This is a huge problem. We shouldn't have to go through the lengths I did...and clearly Google is aware of this problem. It has been reported in several outlets already, and Google has acknowledged it to people via documented emails. BUT, it is being ignored and that is a big problem. I think a class action is in order, and I fully expect one soon. If there are nearly a 1000 people here with this problem, think of all the people who don't know to look at Google Issue tracker...my bet is this is in the tens of thousands of devices, and it is rapidly increasing month to month. I also think people concerned here should reach out not just to attourneys specialising in this, but to their congressional repesrentatives as well. Once legal action is taken Google will go into damage control.

ni...@gmail.com <ni...@gmail.com> #892Oct 29, 2021 06:47PM

Just joined the ranks of dead Pixel 3s 2 days ago. Ran android 12 and didn't unlock or mess with the bootloader in any way. Should Google release the firehose file and let us restore our devices would we still retain our data? Reading the XDA developer forum, XDA forum it seems that with the firehose file we could boot to a factory image, does this mean that it would boot into a factory reset state with all the data wiped? I have lots of data that I would like to save in the case that I could get my phone to turn back on. Looking forward to any class action suits or any legal action to force Google to help us with our bricked devices.

th...@googlemail.com <th...@googlemail.com> #893Oct 29, 2021 08:32PM

time to google "how to file a class action lawsuit" repeatedly to bother the algorithm

mi...@gmail.com <mi...@gmail.com> #894Oct 30, 2021 06:36PM

My pixel 3 just died over night with this issue. Absolutely absurd

mi...@gmail.com <mi...@gmail.com> #895Oct 30, 2021 06:39PM

Truely annoyed that now I won't get the estimated trade-in value for my phone because it's bricked, and to no fault of my own. This was a perfectly working device until last night. And now to want to shell out money for a phone while I wait for my pixel 6 preorder that won't arrive until next year. what a money grab.

kr...@gmail.com <kr...@gmail.com> #896Oct 30, 2021 08:32PM

I have the same problem with my PIXEL 3XL back in the summer , while charging it just went black. I have tried all button combinations I have tried tools for qualcomm chipset and it will see my phone on a com port but will not flash it or recognize it as a phone. If I could at least get it to be recognized on my computer so I could transfer anything that was on it over for storage that would be appreciated. I have been reading about this since my phone "Died" so I have gotten myself the new PIXEL 6 pro but would still like to get a bit of life back into my PIXEL 3 XL to retrieve my personal things.

di...@gmail.com <di...@gmail.com> #897Oct 31, 2021 01:37AM

Just dusted off my OG Pixel and joined the club. I plugged it in for the first time in a while. Saw the red LED and the battery icon. Turned it on after a few minutes, it booted to the G logo and loaded for a while. Checked in on it a few minutes later, it was completely black with no LED or anything. Completely unresponsive to all button-pushing combinations. The only sign of life is "QUSB_BULK" in my device manager when I connect it via USB. This is pretty unacceptable.

da...@gmail.com <da...@gmail.com> #898Oct 31, 2021 03:22AM

I work in a repair shop and we are seeing this several times on the daily. for the last week or so.

de...@gmail.com <de...@gmail.com> #899Oct 31, 2021 02:02PM

Hello , my P3 XL died yesterday with 90 % of battery during my work. Now its a black brick... chatting with Big G back and forth.

le...@gmail.com <le...@gmail.com> #900Oct 31, 2021 04:21PM

My great Halloween mood was completely ruined after receiving email like this from google support, google refuse to help me and ask me to find other repair store to fix the issue myself.

Hi,

Thank you for writing back to Google support.

I've read your email. Unfortunately, we do not have an alternative for you. I'd kindly request you to check with any other local repair stories and see if they can fix this for you. (I live overseas)

Have a great day!

Thanks!
The Google Support Team

mf...@gmail.com <mf...@gmail.com> #901Oct 31, 2021 06:09PM

This was my email response from Google Support this week. During my phone calls with them, they refuse to acknowledge that some users were offered replacements even though the phones were beyond warranty.
My original post on this thread was #394, in Sept, but I did not go to direct personal calls until Oct, when I saw that some had received replacements. My bad. Also, months ago I replaced my bricked Pixel 3 with a Pixel 5, which has a much better battery than I ever saw with the P3. However, I was unhappy to learn that the P5 also has the same Qualcomm chip that has bricked in the 3 and recently in the 4 Series. (Pixel 6 apparently does not. Maybe Google's reaction to issue) Happy to learn however, that Verizon offering an open extended warranty period until 12/2021 even for phones purchased months ago. EW for $4.15/mth sounds attractive if available without extra add ons. Will explore and update a report in near future
Any lawyers on this thread should consider 'Class action' which I would be willing to join.

" Thank you for contacting Google Support.
Please be informed we've already escalated the matter to the higher up team and we've got the same answer. Your device is no longer eligible for a replacement as it is already out of warranty. We can definitely see where your frustration is coming from and we wish this was a policy we could bend. But please understand that our hands are tied."

de...@gmail.com <de...@gmail.com> #902Oct 31, 2021 07:18PM

https://twitter.com/DV1510/status/1454889328274984962?t=mqcA7xViNlNsZrFpn-6wmw&s=19

ga...@gmail.com <ga...@gmail.com> #903Oct 31, 2021 07:38PM

Plus 1... Another pixel 3 xl stuck in EDL loop with likely Android 12 update overnight.

sm...@gmail.com <sm...@gmail.com> #904Oct 31, 2021 08:05PM

I'm really curious what is going on here.
Since I heard about this issue, and subscribed to this issue, I have updated my phone 3 times. Each time I was dreading the result. Each time I encountered zero issues.

I'd really like to know what is different between my pixel 3a and the rest of the affected devices.

pg...@gmail.com <pg...@gmail.com> #905Nov 1, 2021 12:03AM

Same issue has happened to me overnight - left phone charging and woke up to a brick. Repair shop said they can't help and have been seeing TONS of Pixel 3s with no hope of fixing.

ad...@lidskialf.net <ad...@lidskialf.net> #906Nov 1, 2021 12:48AM

My Pixel 3 has just suddenly died. It was on stock Android 12 from normal software update. It was working fine, then tried it 10 mins later => black screen.

Plugging it into a PC shows it is now stuck in QDL mode.

ss...@gmail.com <ss...@gmail.com> #907Nov 1, 2021 12:13PM

My Pixel 3XL also just suddendly died, It was on stock Andord 12 for a couple of days and it worked fine, however, this morning when I wake up just got a black screen. When I plug it into the PC the name that appears in the device manager is QUSB_BULK_CID...

ja...@gmail.com <ja...@gmail.com> #908Nov 1, 2021 12:22PM

So is this being considered a non-issue for Google?
Or is there work being done and communicated to the public and I am just not aware?

pa...@gmail.com <pa...@gmail.com> #909Nov 1, 2021 12:26PM

Sure seems they're trying to sweep us under the rug!

2j...@gmail.com <2j...@gmail.com> #910Nov 1, 2021 01:10PM

Same issue with my pixel 3, bricked after android 12 update. stuck in EDL mode, will not power on.

ta...@gmail.com <ta...@gmail.com> #911Nov 1, 2021 01:20PM

#904: It's not 100% of phones, so it's not surprising some people are not affected. We're a multi-Pixel family and have had this issue happen on one of our two Pixel 3 devices. The issue is playing out like issues on other phones where flash memory was failing or failed entirely. In this case, it seems to affect the bootloader. The downside of this case is that we can't repair it ourselves because the device is locked down and the manufacturer does not make the necessary recovery files available like other manufacturers do. Even if we were able to repair it, the root cause is very likely that failing or failed memory, so a fix wouldn't necessarily be a lasting fix.

kj...@gmail.com <kj...@gmail.com> #912Nov 2, 2021 12:55AM

Wow! Let's just say GOOGLE has absolutely the worst customer service! Bar None! It's goes back to the old training methods of teach them only what we want them to say. All they do is practically read off there own FYI website! LOL! They have no idea what they are talking about and that's exactly how GOOGLE likes it!

My Pixel 3XL bricked just like all of you 09/01/2021 and called and emailed with no results. I THINK IT'S TIME FOR CLASS ACTION SUIT!!!! Also, with enough media and social media post to make sure they don't just think they are getting away with it!

an...@gmail.com <an...@gmail.com> #913Nov 2, 2021 04:28AM

Just to add my P3 to the list.. died about the 20th oct, overnight.

sk...@skaccess.com <sk...@skaccess.com> #914Nov 2, 2021 05:00AM

My Pixel 3 XL is stuck in EDL Mode. (Update from post #842 : i am one of the lucky ones that got an RMA from Google)

connected my phone to the OEM charger on the 22/10/2021 night, went to sleep, (Android 11)
woke up on 23/10/2021 morning and my phone was off. tried to turn it on, nothing.
when connecting it to a computer, it is showing as QUSB_BULK_CID:0402_SN:XXXXXXXX
23/10/2021 contacted google support via Chat, and they redirected me to a repair company and would not do an RMA.
i ask them to escalate the issue,

25/10/2021 got a reply via email that they are willing to do a Standard Exchange (RMA)
Filled up all shipping form etc, and requested a pickup (Toll/DPEX/Expansys) from Perth, to Hong Kong
27/10/2021 faulty phone picked up by Toll
28/10/2021 Replacement phone Shipped via StarTrack from Sydney (Ingram Micro)
01/11/2021 Faulty Phone Delivered in Hong Kong.
Replacement Phone Delivered in Perth.
Arrived with Android 10 , 0% battery (9 days since contacting Google Support)
updated to latest Android 12
Now, hopefully the replacement does not brick itself!!!

oz...@gmail.com <oz...@gmail.com> #915Nov 2, 2021 05:46AM

@#914 Did you purchase your phone directly from Google, or via a 3rd party?

st...@gmail.com <st...@gmail.com> #916Nov 2, 2021 08:50AM

Pixel 3 bricked 11/1/2021 around 10:00PM EST. Phone was in pocket and suddenly stuck on Google boot screen. Stayed that way for at least 2 hours. Now won't charge or power on.

pa...@gmail.com <pa...@gmail.com> #917Nov 2, 2021 12:36PM

@914 were you enrolled in Device Protection? They kept leaning on that for me - like I should have to pay a ransom for the phone to not suddenly crap out for no reason.

ti...@gmail.com <ti...@gmail.com> #918Nov 2, 2021 01:57PM

I have already added my name to this list, but to recap:

- Bought the phone stock from the Google store in 10/2018 and enrolled in Google Fi.
- Loved the phone for 3 years
- Bricked in mid October, same EDL issues everyone is having
- Did all of the useless troubleshooting
- Had a back-and-forth with Google Support, who finally offered me a replacement because of Device Protection
- The caveat is that they aren't acknowledging the EDL issue, they are insisting the device itself is faulty

I have been holding out for a few weeks in hopes that a fix is released so that I can get my data back, but I may just bite that bullet because it's better to get something out of this. I really enjoyed the Pixel 3XL and was planning on upgrading to the Pixel 6, but now I will never buy another Google phone and I am leaving Google Fi.

me...@gmail.com <me...@gmail.com> #919Nov 2, 2021 02:20PM

I bought the phone from Verizon in Nov 2018 and really liked it. I was planning on upgrading to a pixel 6 when they came out. It bricked overnight in July while charging with the same EDL issue and at the time there was not much info available and I needed a new phone right away so I left it and kept researching hoping I could get my data back at least. I tried all the troubleshooting and also contacted Google support in September who had me do all the same troubleshooting. They told me I could send my phone in for repair but if it wasn't a manufacturer defect it wouldn't be covered and I was worried I wouldn't get the phone back so I kept it. Still hoping they might come out with a fix that would at least allow for data transfer. The 3xl was my first and will be my last Google phone, not so much for the phone itself but the lack of support when it is very obviously not a consumer caused (or controllable) issue.

oa...@gmail.com <oa...@gmail.com> #920Nov 2, 2021 06:06PM

Comment has been deleted.

Message last modified on Nov 2, 2021 06:07PM

2x...@gmail.com <2x...@gmail.com> #921Nov 2, 2021 06:09PM

Pixel 3a, downloaded Android 12 update, asked for restart, upon restarting would not load Android OS. Got a message "Cannot find Android system". ... straight to the end of the story, it appears that one of the apps I had on the phone was causing the problems....... I can reset to factory original, restore from back up no problem, as soon as the screens time outs phone crashes. Back to Cannot find Android system. After numerous resets, restores from back up and Safe Starts, I decided not to restore from back up and continued. Signed to my google account, but did not restore from the back up. Did not reinstall any of my 3rd party apps and looks like I am back on.

be...@gmail.com <be...@gmail.com> #922Nov 2, 2021 06:31PM

My Pixel 3 also is a bootloop since october 16th, I have the google animation repeating, I tried to go to the recovery mode but whatever I choose the devices reboots and get stuck in the bootloop again.

sy...@gmail.com <sy...@gmail.com> #923Nov 2, 2021 08:48PM

My wife's phone is also stuck in this EDL.

Google, we thought you were better than this. Don't you make these phones? Don't you make this software? Don't you care about your customers?

cd...@gmail.com <cd...@gmail.com> #924Nov 2, 2021 09:05PM

Pixel 3XL also stuck in bootloop after applying Android 12 update.

I can either "retry" or "factory wipe." Retrying results in a flickering screen, then returning to the same retry / factory wipe screen. Factory wiping restores responsiveness, and allows me to setup phone... but then phone becomes unresponsive. It flashes my home screen as soon as it goes to the lock screen. Restarting results in the same retry / factory wipe screen.

I did a factory reset, with no backup. I was able to use the phone as normal it seemed. Tried to factory reset after the successful install and restore all apps - crashed again as stated above.

It seems that at least for my instance, restoring my Pixel is causing the issue. But I still need my passwords, photos, etc. I shouldn't be penalized for upgrading.

ec...@gmail.com <ec...@gmail.com> #925Nov 2, 2021 09:15PM

#924 why are you telling us about this completely unrelated issue? We all wish our phones were in your situation. You wiped all your data that most likely where completely recoverable wheres we have lost everything.

mi...@gmail.com <mi...@gmail.com> #926Nov 3, 2021 12:03AM

Happened to me also. Pixel 3XL completely bricked overnight while charging. Not getting more security updates is one thing but my phone becoming completely unusable is completely unacceptable especially since I have kept my phone in near-perfect condition for the past three years.

bm...@gmail.com <bm...@gmail.com> #927Nov 3, 2021 05:12AM

Pixel 3XL also bricked overnight, and showing the same QUSB_BULK_CID ice ice I’d when plugged into a computer.

ja...@gmail.com <ja...@gmail.com> #928Nov 3, 2021 06:48AM

Contacted Google Support multiple times. Both times I waited ~2 hours to finally talk to someone. Both times the agent assured me my case was escalated to Pixel support, and that I'd be receiving a follow up email to further triage/resolve the issue. Both times I received zero follow-up. Seems like they're aware of the issue and are doing all they can to brush everyone off or buy time until Google makes some sort of formal statement or decision.

sk...@skaccess.com <sk...@skaccess.com> #929Nov 3, 2021 09:18AM

@915 phone was acquired via 3rd party (Telstra, a phone company in Australia)
@917 i do not have any device protection plan (I don't think that this is even an option in Australia)

ja...@gmail.com <ja...@gmail.com> #930Nov 3, 2021 05:34PM

This happened to me too (Pixel 3). Woke up and phone screen was frozen showing full battery and 4:06AM. I tried to restart it and it would not turn back on. Talked to Google customer support and was directed to Verizon. Verizon sent me to a local UbreakIFix. Just heard back from UBreakIFix and they said they could not get the phone to turn on. Reached back out to Google today and they suggested I send the phone in to Google. Looked at that option: Estimated Cost of repair $400!!!!!!

This is insane. It is a known issue. The phone is not in warranty but it is still fully supported by Google. Google's update broker my phone through no fault (or action) of my own.

Here are the reasonable solutions:
1. Fix my phone for free
2. Send me a new or refurbished Pixel 3
3. Give me a credit to buy a new phone

Anything short of the above is unsatisfactory and unfair. I would like a new Pixel 6 Pro, but with this "customer service" experience, I am thinking it might be time to switch back to iPhone. Apple stands by their product.

w3...@gmail.com <w3...@gmail.com> #931Nov 3, 2021 06:59PM

Reply

On Wed, Nov 3, 2021, 12:34 PM <buganizer-system@google.com wrote:

- Show quoted text -

an...@gmail.com <an...@gmail.com> #932Nov 4, 2021 10:39AM

My Pixel 3 worked perfectly fine ( I have kept this phone in MINT condition since new) and when I woke up on Saturday 30 October 2021, it was fully charged and operational. I messaged a friend and put my phone down. I came back to my phone , an hour later and it was totally black and has not started since. I have tried all the remedies but nothing. Not one sign of power. I am very frustated that I spent $1200 Australian dollars on this product and it is out of warranty and now useless. Google Australia says there is nothing they can do. Totally unacceptable.

je...@gmail.com <je...@gmail.com> #933Nov 4, 2021 11:48PM

Hello, I have a Google Pixel 3 XL in excellent condition (until couple of hours ago). I got the Android 12 update couple of days ago. Now my phone is dead. It had more than 60% charge. I was typing some message & then it just died. Pressing the Power button, or pressing & holding Power + Volume Up buttons do nothing. After a lot of Googling & reading, I found that it could be the famous EDL stuck issue (As I see that my device shows up under the Device Manager in my laptop with the name "QUSB_BULK_CID:xxxx..." & I hear the sounds when I connect my device to my laptop through the USB cable. What can I do now? I'm in US & can send the device to get fixed. What is the best way to contact Google on this? Is there an email? Is there a way to chat with them?

Thanks much for your help on this!

at...@gmail.com <at...@gmail.com> #934Nov 4, 2021 11:56PM

I've had this issue
On Tue, Nov 2, 2021, 2:48 PM <buganizer-system@google.com> wrote:

- Show quoted text -

ca...@gmail.com <ca...@gmail.com> #935Nov 5, 2021 02:17AM

Just adding my bricked Pixel 3 phone to the sad bricked phone pile. Set my alarm last night and went to bed. Woke up at 7am to a black screen.

je...@gmail.com <je...@gmail.com> #936Nov 5, 2021 03:34AM

ad...@google.com, Please provide an update. From the last comment from you, you need further information. Unfortunately the information you require cannot be obtained from a bricked phone. All the people on this thread are awaiting google's official reply. I have created my own issue so it will be easier for me to keep track of the response from google. Again, unfortunately that issue had been linked to this bug and was marked Duplicate. It has been more than a month since my phone got bricked. My phone has already been returned a month from this day, unrepaired and no other options as you consistently insist that it is out of warranty. I have requested for an RCA why the device just suddenly died on its own without any interference. Still no response after a month. What other options can we take? We have been very patient about this issue.

For such an expensive phone from a "reputable" company, I would expect more. I cannot accept the standard reply that it is out of warranty. To me that is just you saying that your company is in the business of only producing low quality phone at a high quality price.

The acceptable action expected from you are either:

repair the phone at no cost from me
replace it with a new or refurbished phone
give me a credit that will allow me to buy a new phone

I hope to receive a reply from this the soonest as this is more than a month old issue.

jm...@gmail.com <jm...@gmail.com> #937Nov 5, 2021 01:31PM

Same issue here with my Pixel 3 XL. No video on screen. Detected by Windows 10 PCs as "QUSB_BULK_CID:0402_SN:........" Stuck in EDL mode.

I am not sure how you think this is supposed to inspire me to stick with Pixel phones. It is angering to see how many people before me you have left hanging before me, for months!

pr...@gmail.com <pr...@gmail.com> #938Nov 5, 2021 03:11PM

This absolute BS lack of any sort of acknowledgement is the only reason I didn't pre-order the Pixel 6. I'm sure I'm not the only one. Google is screwing themselves out of a lot of phone sales with their deafening silence on this issue.

de...@gmail.com <de...@gmail.com> #939Nov 5, 2021 03:46PM

Great news on my Pixel 4 XL - instead of filing a claim through Assurant and paying a $149 deductible, I've now been offered the option to send the phone directly to Google for repair for just $500!!

ja...@gmail.com <ja...@gmail.com> #940Nov 6, 2021 01:13PM

Another one bites the dust I guess. My pixel 3 bricked a few days ago thought it would be a charging port issue but learned about this WIDESPREAD issue all pixel 3 users are getting. Same circumstances that the phone was on charge over night and woke in the morning to find the phone wouldn't turn on.

er...@gmail.com <er...@gmail.com> #941Nov 6, 2021 01:57PM

Comment has been deleted.

Message last modified on Nov 6, 2021 01:58PM

er...@gmail.com <er...@gmail.com> #942Nov 6, 2021 01:58PM

My Pixel 3 XL bricked last night for no reason. Stuck in EDL mode like others. Hope Google does something about this. I feel so stupid because I was hyping up the Pixel 6 to everyone just this week. Now I will be making the move back to Samsung permanently if this isn't resolved. Can't trust Google to not have this happen again in the next few years with any future phone. Such a shame. Also Android 12 SUCKS!

xp...@gmail.com <xp...@gmail.com> #943Nov 6, 2021 06:07PM

Mine died this morning. I updated it 2 days ago, worked fine. Used my phone as normal. Made a phone call today and put it back in my pocket when done. 15 minutes later I went to check the time and my phone was dead and will not turn on.

sy...@gmail.com <sy...@gmail.com> #944Nov 6, 2021 07:55PM

So, let's all start giving more information.

Our phone was purchased through Verizon. Let's look for a pattern.

What did each of you get your phone?

On Sat, Nov 6, 2021, 11:07 AM <buganizer-system@google.com> wrote:

- Show quoted text -

na...@gmail.com <na...@gmail.com> #945Nov 7, 2021 05:13AM

My wife's Google Store purchased unlocked Pixel 3XL bricked last night. Getting the same QUSB_BULK_CID when plugged in as mentioned above. No amount of key press/duration/combination is making a difference.

ro...@gmail.com <ro...@gmail.com> #946Nov 7, 2021 12:37PM

pixel 3 EDL mode, help fix please

dk...@gmail.com <dk...@gmail.com> #947Nov 7, 2021 06:06PM

Can someone tell me who I need to contact about this and what is the best method? I keep running up against a call center in India that frankly is very rude and unhelpful. I chatted with support on Friday and they referred me to an email that was sent to me a month ago that I needed to reply to about this issue. This email was support I started with Google Fi since it was purchased through them. They just responded saying the issue is too old and to start a chat, which is what I did Friday. When I ask to speak to the next level up the chain they tell me there is no one else. It seems like Google is using this call center to completely cut off support to their customers. I am getting sick of this tactic, imagine if the company you work at shuffled it customers off to speak to someone in India that keeps telling you to go pound sand. Someone please help me since support doesn't care and they've told me they don't. (Google, if you don't believe me, look at my call/chat/email logs. If it was you getting this service from another company, you'd never do business with them again).

ja...@gmail.com <ja...@gmail.com> #948Nov 7, 2021 06:09PM

Support told me they would follow up via email and also assured me they
would send me a transcript of chat as I requested. Completely ghosted me.
At this point I think the best option is to collect screenshots of chat and
report them over to the better business bureau for straight lying to us.

https://www.bbb.org/file-a-complaint

On Sun, Nov 7, 2021 at 10:06 AM <buganizer-system@google.com> wrote:

- Show quoted text -

de...@gmail.com <de...@gmail.com> #949Nov 7, 2021 07:50PM

Comment has been deleted.

Message last modified on Nov 24, 2021 05:29AM

ka...@gmail.com <ka...@gmail.com> #950Nov 8, 2021 01:11PM

Hi, I'm having the same issue. I charged my phone before going to bed and the next morning I woke up to a dead, unresponsive phone. It was working fine until the day before.
Seems like many have had the same issue.

dk...@gmail.com <dk...@gmail.com> #951Nov 8, 2021 02:49PM

After the 3rd time contacting customer support, i just realized that my phone is not broken, it doesn't matter if it's under warranty or not. What IS broken is the android software that caused my phone to go into EDL mode. If we start looking at it from that position, then the responsibility to fix these problems lies solely on Google, not an expired warranty or UBreakIFix.

na...@gmail.com <na...@gmail.com> #952Nov 8, 2021 10:52PM

Both my pixel 3 and my wife's have suddenly bricked without warning. Hers bricked last week. So I thought I'd give her my old Pixel3 that I hadn't used in a few months since upgrading to a Pixel 5G. That's when I discovered that my old Pixel3 was totally unresponsive. It sounds similar to what others have described here. Google needs to fix this. Now I'm wondering if I'll run into the same problem eventually with my newer Pixel phone.

kh...@gmail.com <kh...@gmail.com> #953Nov 8, 2021 11:09PM

Same issue here with Pixel 3: black screen, not responding

ce...@gmail.com <ce...@gmail.com> #954Nov 9, 2021 01:43AM

Same issue here with Pixel 3: black screen, not responding
Before unresponding there are a tip shows some files are corrupt.

ab...@gmail.com <ab...@gmail.com> #955Nov 9, 2021 03:50AM

Same issue here. Bought my phone through Rogers (AT&T in Canada) and it is completely bricked.

qu...@gmail.com <qu...@gmail.com> #956Nov 9, 2021 09:22AM

Same issue, woke up seeing message like " your device is corrupted and can not be trusted, press power to continue", I thought it would be a reboot, but after pressing power button, it never turns on again, customer support said my phone is out of warranty, pushed me to ubreakifix, who claimed they've seen tons of customers had this issue before, not worth fixing it because they will charge more than the remaining value of the pixel 3 has. Google should take the full responsibility fixing this issue, the phone was in good shape, running fine until an overnight security patch that bricked it, there should be better answer than " sorry, I wish there's something we can do but your phone is out of warranty", it's the software that disabled the phone that's still on the supported list, not a hardware issue, has nothing to do with warranty, otherwise, google can just retire all 3 year old phones by pushing out a "patch", pixel 3 is not deprecated yet to my understanding, even it is, google has no right to brick the phone on users. If this issue can not be addressed gracefully, there needs to be a class action.

to...@gmail.com <to...@gmail.com> #957Nov 9, 2021 02:16PM

My Pixel 4XL did this overnight. Went to bed with it fine, woke up this morning to a brick. I have the same `QUSB_BULK_CID:...` identifier on my PC. Vanilla phone, updated to Android 12 about a week ago. Out of warranty, although that seems trivial as this wasn't caused by an action on my part.

gr...@gmail.com <gr...@gmail.com> #958Nov 9, 2021 04:48PM

Same issue. Last night I put my Pixel 3 XL on my Pixel Stand, as I have done for years. I woke up this morning to a bricked phone. Google Fi says there's nothing they can do. I'm very disappointed, to say the least.

j....@gmail.com <j....@gmail.com> #959Nov 10, 2021 08:15PM

Pixel 3XL did this on 11/10/21 between 6:30AM EST and 10:00AM EST. Tried power button for 30 seconds, power + volume down, plugging into PC (got QUSB_BULK_CID... device). Updated to Android 12 a week or two ago.

wi...@gmail.com <wi...@gmail.com> #960Nov 10, 2021 11:19PM

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 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 v1, v3 and 3XL, 4 XL 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.

ah...@gmail.com <ah...@gmail.com> #961Nov 11, 2021 12:28AM

Happened to me last night as well, will be chatting to Google today.

fp...@gmail.com <fp...@gmail.com> #962Nov 11, 2021 02:32AM

Phone pixel 3 Xl.
Stuck in EDL Mode.
Completely dead. Nothing is bringing it back to life.
How can it be a possible that an update bricks a phone.
This is not good. So much for investing in a tough phone case with a pretty phone for it only not to work now.
Google do something about it please.
Your customers are not happy.

co...@gmail.com <co...@gmail.com> #963Nov 12, 2021 02:39PM

As of this morning, add my Pixel3XL to the list.

Rebooted yesterday around 2PM Eastern.
Phone worked fine for rest of day.
Put on charger at ~1030PM Eastern and was fine.
woke this morning to black screen
Tried Power/Volume Down buttons - nothing
Get QUSB_BULK... message when connected to PC, so assume I'm stuck in EDL mode like others.
Went round and round with support this morning, but their bottom line is "your device is out of warranty, so it's your issue to fix". Zero responsibility for the software update that caused this.

This is HORRIBLE customer service. I escalated to what I was told was highest I could go and referred them to this tracker. Their response "well, that's a public bug tracker, so not relevant" despite the fact that this thread and dozens of similar discussions exist around the internet.

I was pretty happy with my phone and had planned to upgrade to Pixel 6 soon, but just can't do it if this is how they treat folks.

Can't afford to wait around until they maybe fix the issue, so off I go.

Since Google controls Android, do I have to have a lobotomy and go to Apple to be safe? I can't even believe I said that, but this is just too sucky for words.

dk...@gmail.com <dk...@gmail.com> #964Nov 12, 2021 04:05PM

Just FYI to everyone coming here, Google is hiding behind a pretty useless call center in another country. This call center only helps people who are still in warranty. If you are not in warranty, tough luck, even for someone like me who's owned 3 Nexus phones and 2 Pixels. It's a way for one of the richest corporations to cut off all communication with their customers that have already handed over their money. The highest level of support you can get from this call center is 'Floor Supervisor'. Not a specialist, or even someone in the US (hell, i'd even take someone from Ireland). You get a Floor Supervisor that gives you a canned response. Trust me, after 4 times using different methods (call, chat, email), that response is exactly the same. Oh, and don't say that you're not satisfied with the help, they will hang up on you. At least they gave me a laugh, the last time I asked for a status, they sent me a link to buy a new phone. Funny guys at that call center.

wo...@gmail.com <wo...@gmail.com> #965Nov 12, 2021 04:06PM

Update to my earlier thread on my Pixel 3. They want me to send a bricked phone to Google to be "repaired" for the low price of $433! I paid $800 for this phone 3 freakin' years ago and it was working fine until 10/24 when their garbage Android 12 update destroyed it. I am using my old Nexus 5X by LG, which was and is actually a pretty good phone and won't update above Android 8.1 so I'm betting they can't spy on me as much as they were on Android !! Hope it holds up for me til I can hold my nose and get an Apple phone which I swore I never would do. At least Apple has a phone number for tech support.
I told Google I would pay them $433 on the hope that they could repair my phone...NEVER!! They owe me and the rest of us replacement phones at the very least.
Lots of web sites for their buggy OS:

https://www.technotification.com/2021/10/google-android-12-bugs-issues.html,

https://www.androidcentral.com/google-pixel-november-security-update-bug-fixes (note the 3s aren't listed) , etc. etc.
This is a scam to FORCE users to buy their new 6 which runs 12 and is chock full of spyware and buggy as hell, they even make the chip! I have filed a complaint with the FCC and the Better Business Bureau of Santa Clara County. Believe it or not Google does not participate with the BBB, no surprises.

el...@gmail.com <el...@gmail.com> #966Nov 12, 2021 05:57PM

Hi everyone and today I unfortunately join this discussion.

I was a Google Phones fan until this morning. My Google Pixel 3 XL worked great but it broke down AT NIGHT while charging, although I don't have automatic updates. So I took it out from charging, and it was just dead. I tried to check the USB port, to check the charging condition, to turn on/off button and turn sounds +- buttons and all that things... It doesn't 't work at all !
My computer did not see my phone at all, then it began to identify it as a driver called Qualcomm HS-USB QDLoader 9008.

Then I turned to the Google support center, where I was asked to do the same procedures with charging and on/off buttons (they take us for fools!)
and tell them my IMEI number to let me know that my warranty is over (as if they just couldn't just ask if I have a valid warranty, of course I dont, the phone was released in 2018).
At the end, the consultant suggested that I send the phone to the service center and choose that this is a problem with the motherboard (lol, I didn't have any problems until Google forced update)
Anyway I will do it soon and will inform you if you are interested to find out if it is possible to solve this issue.

jp...@gmail.com <jp...@gmail.com> #967Nov 12, 2021 08:09PM

Same problem for me.

I woke up this morning, the phone no longer works.

After multiple searches and a lost day of work.

My Google pixel 4 XL has switched to EDL Mode.

I contacted google who want me to PAY the repairs.

If anyone has any files that I could use in qpst or qfil I am the taker.

thanks in advance

jn...@gmail.com <jn...@gmail.com> #968Nov 13, 2021 11:29AM

Add my Pixel 3XL to the list. Bricked overnight. Stuck in EDL. Had been working fine before this.

ni...@gmail.com <ni...@gmail.com> #969Nov 14, 2021 03:39AM

Another one for the list. 3XL worked perfectly fine before bed last night, completely bricked this morning.

ee...@gmail.com <ee...@gmail.com> #970Nov 14, 2021 06:54PM

My Google Pixel 3XL just bricked yesterday (11/13).

tr...@gmail.com <tr...@gmail.com> #971Nov 14, 2021 07:13PM

My Pixel 3 also bricked today without any warning. I can't do anything it seems .. tried all the above but its just not working ..

ai...@gmail.com <ai...@gmail.com> #972Nov 14, 2021 07:32PM

Add me to this. My pixel 3xl bricked itself around 6 am this morning. I am livid.

am...@gmail.com <am...@gmail.com> #973Nov 14, 2021 07:48PM

I added my device to the list in post 274 and last update was post 742/743.

Another update on my RMA. After some prodding, Google sent me a Pixel 4 to replace my bricked Pixel 3 which I sent back to them under RMA for evaluation of the issue a few weeks ago.

As I mentioned in my previous post(s) they also sent me a Pixel 5 because I voiced concern about the 4 other Pixel 3s on my account dropping dead.

As others have said, be persistent but respectful. I have had the most luck with chats and very little luck with email. Obviously YMMV.

dm...@gmail.com <dm...@gmail.com> #974Nov 14, 2021 08:29PM

Hi everyone! Unfortunately, I'm in this boat as well. Would love an update/fix as soon as it's possible.

ai...@gmail.com <ai...@gmail.com> #975Nov 15, 2021 01:46AM

Google wanted to send me to the ubreakifix shop, obviously, they cannot fix what is wrong with this phone without replacing the motherboard. That is essentially a new phone. I explained my phone was stuck in EDL mode and they didn't seem to care or understand. Maybe I gave up too easily..especially seeing as how some of you have gotten replacements. One replacement of the issue should warrant that for others with the same problem. Ugh, it shouldn't be this hard to have them fix something they broke. My phone was in amazing condition.

qu...@gmail.com <qu...@gmail.com> #976Nov 15, 2021 02:07AM

An update from me, I had a chat with customer support couple of days ago, at first I was again told that my device is out of warranty, there's nothing they can do with it, after couple rounds of going back and forth, the representative was persuaded to talk to the hardware team to see what they can do, I was hoping to get a replacement, but today, I got a response from the support team that they do not have an option to help me with the device replacement, as the device is not covered under device protection and warranty. Such a BS, seems like they don't even care about customers but keep telling them that's users' issue not having extended warranty on the device. I'm switching back to iphone regardless of this resolution.

ba...@gmail.com <ba...@gmail.com> #977Nov 16, 2021 02:58PM

Same with me. Woke up to a wonderful shiny black brick. Chatted with Google support with the same reply. Too bad so sad attitude. No sympathy. No help. Have been a Google customer for many years and now am seriously considering another phone manufacturer. Feel very disappointed with Google. They can't seem to fix this issue they caused. I am seriously thinking they are creating a timed obsolesce to build up their sales. This would be extremely sad if this is the case. If anyone hears of a class action suit, please let me know. Good luck other brick owners.

le...@gmail.com <le...@gmail.com> #978Nov 16, 2021 03:24PM

I can add my Pixel 3 to the pile of bricks as well. Died while just sitting on the Desk, doing nothing. Google offered a >400€ repair... No thanks.
I know, this is an issue tracker for Android, but maybe someday Google might be arsed to make the EDL files available so we can at least attempt recovery.

th...@gmail.com <th...@gmail.com> #979Nov 17, 2021 10:10AM

Same issue here with Pixel 3. Bought it on Google Store, never rooted.
Contacted the support (France) and ask me to pay more than 400€.

aw...@gmail.com <aw...@gmail.com> #980Nov 17, 2021 03:41PM

Also a bricked phone. same issue. Phone was vanilla, charged on Pixel stand it's entire life.
currently open ticket with support.... not optimistic

mi...@gmail.com <mi...@gmail.com> #981Nov 17, 2021 05:40PM

Pixel 3 stuck in EDL mode. Verified by plugging it into computer where it detects hardware ID but doesn't boot up. Was charging it overnight and it never fully powered on after that.

cb...@gmail.com <cb...@gmail.com> #982Nov 17, 2021 08:09PM

Same here. Pixel 3 on charge over night blank screen in morning. Device recognized by PC per EDL comments above.

jz...@gmail.com <jz...@gmail.com> #983Nov 18, 2021 12:42AM

Same as everyone else here. Got the new Android 12 update on my phone (Pixel 3) a few days ago, put my phone on the charger last night (1am), and woke up (9am) with it not turning on at all. Went to a Verizon store and the assistant told me she's seen multiple other Pixels come in with the same issue recently, and that there's nothing to be done. Had to just buy a new phone, no time to try and go through any sort of support, which I see would've been a waste of time anyway! Extremely annoyed and upset with this. I would've liked to use this phone for much longer, and I did end up buying a Pixel 6 as I do like google phones and didn't have time to do any sort of research on other phones.

th...@gmail.com <th...@gmail.com> #984Nov 18, 2021 02:44AM

I luckily haven't had this problem on my Pixel 3XL but have been holding off on updates for a couple of months out of fear, hoping a solution comes along soon. Question: has anyone tried the steps detailed in this article?:

https://www.getdroidtips.com/unbrick-dead-pixel-phone-android-12-update/

It mentions the EDL stuck issue specifically.

ja...@gmail.com <ja...@gmail.com> #985Nov 18, 2021 02:49AM

My pixel 3 XL bricked just sitting in my pocket. Easily my favorite phone ever... crazy that google is pushing this back on their customers

na...@gmail.com <na...@gmail.com> #986Nov 18, 2021 03:09AM

I have now updated two pixel 3 phones without issue to Android 12. I did
noticed that the updates were not going once by month as of late and we're
directly going from my current settings to android 12 in one update. I
suspect they had a bug and fixed it in a later update. I was able to get
one phone replaced after it bricked with the August security update and the
replacement pixel 3 was successfully updated to Android 12 by myself. My
other pixel 3 was sitting at Android 10 and I was able to upgrade to
Android 12 in one update...no issues. That phone never bricked. For the
one I did get replaced, I used to Google chat to get to the 'Pixel team' to
get the replacement. My advice be courteous but persistent.

On Wed, Nov 17, 2021, 8:44 PM <buganizer-system@google.com> wrote:

- Show quoted text -

ta...@gmail.com <ta...@gmail.com> #987Nov 18, 2021 05:06AM

#984: someone mentioned a similar (or the same?) article previously.. those guys are just putting buzzwords for SEO. The bricked phones can not access the bootloader so the guide is useless.

ro...@gmail.com <ro...@gmail.com> #988Nov 18, 2021 03:07PM

add me to this list. my pixel 3xl bricked randomly and I'm still waiting on my replacement from verizon.

ma...@googlemail.com <ma...@googlemail.com> #989Nov 19, 2021 07:55AM

Another one to add to the list. If I had known about the possibility of this issue beforehand I would have taken more app specific backups as I've lost a lot of setup/configuration etc now

ch...@gmail.com <ch...@gmail.com> #990Nov 19, 2021 09:08PM

Adding to the list. A mostly charged Pixel 3 running android 12 bricked between 630am and 730 am ET this morning. Come to find out it wasn't backing up files automatically since 8/2020 like it should have been so I have lost a lot of messages. I am not happy. This phone worked fine yesterday and for my alarms this morning and then it didn't. I just want it to reboot enough to back it up and then I'm done with it.

ji...@gmail.com <ji...@gmail.com> #991Nov 19, 2021 09:24PM

My pixel 4xl encounter the same problem yesterday... Hoping to have solution to it.

al...@gmail.com <al...@gmail.com> #992Nov 20, 2021 12:00AM

Same thing happened to mine. I loved that phone.

er...@gmail.com <er...@gmail.com> #993Nov 20, 2021 02:11PM

Happened to me 2 days ago. P3 from Fi, bought from the Fi store 3 years ago. The phone served me well and I feel it provided a good life for what I spent on it. Now using the P6P. No need for any legal action as this was clearly out of warranty and served me well. I just want my data from the phone. Has anyone been able to recover data after a brick?

op...@gmail.com <op...@gmail.com> #994Nov 20, 2021 03:47PM

This just happened to me this morning. I was using a pixel 3 xl running android 12 and when I woke up this morning I have a black screen and unable to restart and am seeing the QUSB_BULK_CID:XXXX when plugging it into a PC.

wi...@gmail.com <wi...@gmail.com> #995Nov 20, 2021 06:08PM

Just spent 50 minutes in a chat session on the Pixel Phone Help site. The flow of the conversation went as expected, with the support specialist ultimately referring me to a repair center in the US for further diagnosis.

My response was, "Based upon my research, the only available repair options is replacement of the motherboard with one that has a healthy bootloader partition. Here's the issue with that - there is no guarantee that the next OTA will not kill my replacement motherboard's bootloader, so that option seems unwise. wasteful."

Following that I said, "Please send the Pixel team a request to supply a software-solution which employs Qualcomm's EDL mode to reinstall the Android bootloader. That's the only way to guarantee this problem can be overcome going forward."

And of course the on-line support person's response was, "I will take this feedback and forward to the specialist team."

--sigh.

tr...@gmail.com <tr...@gmail.com> #996Nov 21, 2021 12:05PM

Another one that just experienced the issue, just like the rest i was told its not under warranty etc and i can have it repaired blah blah blah..
Don't see how its on us to pay when it looks like the phone's issue is caused either by an update or something else especially since it runs fine and then decides to just enter the EDL Mode.

I have a 6 Pro on the way but the way its being handled sort of makes me rethink do i want to spend and potentially have this issue affect or another one where im forced to pay for something that was not caused by my misuse..

ch...@gmail.com <ch...@gmail.com> #997Nov 21, 2021 07:32PM

Happened to me yesterday with Pixel 3XL, have spent many hours on chat with Google Support and Fi Support. They pretend not to know what the issue is, try to ping-pong me back and forth in order to preserve the support person's metrics. Try to send me to a local uBreakIFix, who they know do not have the capability to fix this issue. It's extremely frustrating as a decade-plus user of Google hardware and services of all kinds.

Well, that's certainly coming to a stop here and now. I gave them another shot after the GNex burn-in, and the Nexus 4 turned out fine. Nexus 6P wasn't so fine, and ate its own face just like this one. I gave them another another shot with the 3XL, which has had every problem in the book from panel issues to imbalanced speakers and wireless problems, and finally ate its own face as well. Fool me four times, shame on me.

de...@gmail.com <de...@gmail.com> #998Nov 21, 2021 09:52PM

My Pixel 3 is also bricked out of the blue. Working perfectly, great condition, no mods. Last night it went into EDL out of nowhere and now it is completely unresponsive.

Spoke with customer support, as expected they told me my warranty is up and that I should take my phone to uBreakIFix. It's terrible customer support from Google's side. They certainly know of this problem and are still sending their customers to a third party repair shop that they know will not be able to actually fix the problem. I spoke with uBreakIFix on the phone and they told me Google doesn't give them the files that would be nessesary to get the phone out of EDL mode anyways so there's no point.

It seems comical that some of the posts I've read online say that the recommended repair by the shops was a screen replacement. It shouldn't be 'uBreakIFix', it should be 'Google ships faulty hardware, Google Fix'.

Google knows about the problem and they would rather send their customers on a wild goose chase and spend money to get their perfectly good phone out of a state that was no fault of their own, rather Google's.

I'll try to see if I can talk to someone at Google who can actually solve this issue without deflecting it to someone else.

Until then...

Google if you are reading this, PLEASE own up to your mistake.

fr...@gmail.com <fr...@gmail.com> #999Nov 22, 2021 02:34PM

Happened to my mothers pixel 3xl as well, she was using it, went to bed and woke up with a dead phone. I checked it and its the exact same issue as what everyone is reporting. @GOOGLE SUPPORT, what is the plan? You need to fix this issue. Mistakes happen, its how you handle them that defines you! Create a form for us to complete, send us a shipping label, fix it, and return it, or offer a like value of the phone in credit so we can replace it since this is on YOU!

ra...@gmail.com <ra...@gmail.com> #1000Nov 23, 2021 06:20AM

Same happened to me yesterday, exact same EDL issue. Google Support tried to forward me to ubreakifix

Google own up to your mistake!!!!

cc...@google.com <cc...@google.com> Jan 31, 2022 07:43PM

Status: Won't Fix (Infeasible)

Issue 192008282

Description

Issue summary

Comments

ad...@google.com <ad...@google.com> Jun 28, 2021 01:18PM

ad...@google.com <ad...@google.com> #2Jun 28, 2021 06:58PM

ja...@gmail.com <ja...@gmail.com> #3Jun 28, 2021 07:13PM

ad...@google.com <ad...@google.com> #4Jul 1, 2021 01:41PM

za...@gmail.com <za...@gmail.com> #5Jul 1, 2021 02:58PM

ad...@google.com <ad...@google.com> #6Jul 2, 2021 09:17AM

ja...@gmail.com <ja...@gmail.com> #7Jul 2, 2021 07:41PM

ad...@google.com <ad...@google.com> #8Jul 7, 2021 11:21AM

mo...@gmail.com <mo...@gmail.com> #9Jul 7, 2021 12:38PM

ja...@gmail.com <ja...@gmail.com> #10Jul 7, 2021 08:15PM

ch...@gmail.com <ch...@gmail.com> #11Jul 7, 2021 11:41PM

be...@gmail.com <be...@gmail.com> #12Jul 9, 2021 02:07AM

ky...@gmail.com <ky...@gmail.com> #13Jul 11, 2021 06:03AM

ec...@gmail.com <ec...@gmail.com> #14Jul 12, 2021 10:21AM

ch...@gmail.com <ch...@gmail.com> #15Jul 12, 2021 06:24PM

ja...@gmail.com <ja...@gmail.com> #16Jul 13, 2021 07:48AM

ad...@google.com <ad...@google.com> #17Jul 14, 2021 05:21PM

be...@gmail.com <be...@gmail.com> #18Jul 14, 2021 05:23PM

ch...@gmail.com <ch...@gmail.com> #19Jul 14, 2021 05:35PM

jg...@gmail.com <jg...@gmail.com> #20Jul 16, 2021 05:24PM

am...@gmail.com <am...@gmail.com> #21Jul 16, 2021 05:30PM

is...@gmail.com <is...@gmail.com> #22Jul 18, 2021 02:32AM

ni...@gmail.com <ni...@gmail.com> #23Jul 19, 2021 05:28AM

ka...@gmail.com <ka...@gmail.com> #24Jul 19, 2021 04:17PM

ro...@gmail.com <ro...@gmail.com> #25Jul 19, 2021 06:41PM

ro...@gmail.com <ro...@gmail.com> #26Jul 19, 2021 06:44PM

ni...@gmail.com <ni...@gmail.com> #27Jul 19, 2021 11:38PM

br...@gmail.com <br...@gmail.com> #28Jul 20, 2021 12:49AM

go...@gmail.com <go...@gmail.com> #29Jul 20, 2021 02:57AM

si...@gmail.com <si...@gmail.com> #30Jul 20, 2021 05:48AM

ad...@google.com <ad...@google.com> #31Jul 20, 2021 12:50PM

be...@gmail.com <be...@gmail.com> #32Jul 20, 2021 12:58PM

ma...@gmail.com <ma...@gmail.com> #33Jul 20, 2021 01:00PM

ka...@gmail.com <ka...@gmail.com> #34Jul 20, 2021 01:02PM

za...@gmail.com <za...@gmail.com> #35Jul 20, 2021 01:10PM

mo...@gmail.com <mo...@gmail.com> #36Jul 20, 2021 02:26PM

co...@gmail.com <co...@gmail.com> #37Jul 20, 2021 07:20PM

be...@gmail.com <be...@gmail.com> #38Jul 20, 2021 07:55PM

ka...@gmail.com <ka...@gmail.com> #39Jul 20, 2021 08:10PM

ro...@gmail.com <ro...@gmail.com> #40Jul 20, 2021 11:42PM

cl...@gmail.com <cl...@gmail.com> #41Jul 21, 2021 10:01AM

no...@gmail.com <no...@gmail.com> #42Jul 21, 2021 09:11PM

ro...@gmail.com <ro...@gmail.com> #43Jul 22, 2021 08:42PM

ra...@gmail.com <ra...@gmail.com> #44Jul 23, 2021 02:24AM

ma...@gmail.com <ma...@gmail.com> #45Jul 23, 2021 07:40AM

pe...@gmail.com <pe...@gmail.com> #46Jul 24, 2021 05:49PM

ph...@gmail.com <ph...@gmail.com> #47Jul 25, 2021 11:28AM

za...@gmail.com <za...@gmail.com> #48Jul 25, 2021 02:41PM

ri...@gmail.com <ri...@gmail.com> #49Jul 25, 2021 02:53PM

lo...@gmail.com <lo...@gmail.com> #50Jul 27, 2021 12:29AM

di...@gmail.com <di...@gmail.com> #51Jul 27, 2021 09:39AM

gl...@gmail.com <gl...@gmail.com> #52Jul 28, 2021 05:15AM

be...@gmail.com <be...@gmail.com> #53Jul 29, 2021 08:46AM

ka...@gmail.com <ka...@gmail.com> #54Jul 29, 2021 01:12PM

ro...@gmail.com <ro...@gmail.com> #55Jul 29, 2021 01:47PM

th...@gmail.com <th...@gmail.com> #56Jul 29, 2021 02:02PM

pb...@gmail.com <pb...@gmail.com> #57Jul 29, 2021 02:07PM

be...@gmail.com <be...@gmail.com> #58Jul 29, 2021 02:09PM

co...@gmail.com <co...@gmail.com> #59Jul 30, 2021 06:02PM

st...@gmail.com <st...@gmail.com> #60Jul 31, 2021 03:31AM

da...@hotmail.com <da...@hotmail.com> #61Jul 31, 2021 04:47AM

to...@gmail.com <to...@gmail.com> #62Jul 31, 2021 07:27AM

ja...@gmail.com <ja...@gmail.com> #63Jul 31, 2021 12:43PM

ph...@gmail.com <ph...@gmail.com> #64Jul 31, 2021 03:03PM

be...@gmail.com <be...@gmail.com> #65Jul 31, 2021 09:40PM

94...@gmail.com <94...@gmail.com> #66Aug 1, 2021 07:59AM

sh...@gmail.com <sh...@gmail.com> #67Aug 1, 2021 01:31PM

er...@gmail.com <er...@gmail.com> #68Aug 2, 2021 11:27PM

ti...@gmail.com <ti...@gmail.com> #69Aug 4, 2021 05:13PM

an...@jorgensenfamily.us <an...@jorgensenfamily.us> #70Aug 4, 2021 10:37PM

ks...@gmail.com <ks...@gmail.com> #71Aug 6, 2021 07:35PM

na...@gmail.com <na...@gmail.com> #72Aug 7, 2021 12:58PM

oz...@gmail.com <oz...@gmail.com> #73Aug 7, 2021 12:59PM

ke...@gmail.com <ke...@gmail.com> #74Aug 7, 2021 03:04PM

oz...@gmail.com <oz...@gmail.com> #75Aug 8, 2021 04:40AM

pe...@gmail.com <pe...@gmail.com> #76Aug 8, 2021 12:05PM