yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 Questions & Answers] jancoow:
Same happened to me this morning. Woke up, saw a message "your device is corrupted". Saw the google boot logo for a second and after that it won't turn on. Only black screen. Computer recognise it as qusb_bulk_cid. Any way of recovering? Can I reflash the image ?
[Google Pixel 3 Questions & Answers] BDroidz:
Update:

Per guidance from https://store.google.com/us/repair I took my phone into uBreakiFix to have it repaired. They agreed the phone was stuck in EDL mode but thought the screen was dead.

They attempted a screen replacement at no charge. It did

not

fix the problem. Their next thought was the motherboard needed replacement but said at that point... you might as well buy a new phone.

It seems the problem is likely beyond the skill level of your standard phone repair shop. Anyone else will probably want to send their device directly to Google for repair or just buy a new one.
[Google Pixel 3 Questions & Answers] AsItLies:
It's unfortunate for sure, the problem is pretty obvious, as is the solution. We need the specific firehose for the pixel 3, and we need backups of the mmcblk0 un-corrupted image (that almost certainly is the reason it's stuck in edl, this image is corrupted).

I don't think any of the mom and pop 'repair' shops would be able to fix this issue. Honestly, I'm shocked google isn't releasing the firehose. It wouldn't stop it from getting corrupted, but it could be easily fixed if / when it did happen.

Good luck to you. Do be sure to let google know you won't be buying another of their phones! It's crazy they're doing this to their customers.
[Google Pixel 3 Questions & Answers] utahphunk:
I don't think "send your device directly to Google for repair" is a viable option if your phone is out of warranty.

If I'm remembering correctly, Google wanted something close to $450 to "repair" it. (This was according to an area of their site, perhaps within the Google Fi help area because that's our service provider.)

I spoke with our local (Utah) Ubreakifix location and was very specific in asking them if they could flash the firehose needed to resolve this, and they said no.
[Google Pixel 3 Questions & Answers] utahphunk:
Between randomly losing text messages regardless of app being used (on both my wife's Pixel and and mine) on Google Fi and Google bricking my wife's phone, we're absolutely never buying another Google phone or piece of hardware again.
[Google Pixel 3 Questions & Answers] jancoow:
I tried contacting google support. They are not aware of the issue. And because I'm out of warranty I'm not able to repair it..

Ubreakifix is not available in my country.

Is there any other thing I can do?
[Google Pixel 3 Questions & Answers] AsItLies:
It seems, at this point, just wait and hope that the firehose becomes available / or one is discovered to work with the pixel 3.

I've read, think it was on reddit, about someone that kept trying to get to fastboot, initially they only saw the screen for a second, but kept trying and eventually it got info fastboot. **if** one was able to do that, they could then flash a factory image.

But, as others have already mentioned, no combination of keys worked for them, so it doesn't sound promising at all really.

cheers
[Google Pixel 3 Questions & Answers] thevanesth:
Dear God. I'm kinda scared for my Pixel 3.

But Id like to understand if there's a pattern. Do you guys have your bootloader unlocked?
[Google Pixel 3 Questions & Answers] utahphunk:
Neither my wife's phone nor mine is unlocked or messed with in any way. Her phone bricked. Mine did not. 🤷
[Google Pixel 3 Questions & Answers] AsItLies:
Yes it is frightening... always good to have a beater back-up phone around, if possible.

It **seems** that the only possibly consistent pattern is having done an OTA update. But, even if that is it, it doesn't happen right away, and takes a day or two later. None of it really makes sense. I'm not doing any OTA updates personally... and hoping.

cheers
[Google Pixel 3 Questions & Answers] jancoow:
My bootloader was not unlocked. I was running the android 12 beta tho.

I see it is also happening to the pixel 4, but unsure this is related?

I can't believe google won't help their customers. I tried contacting the support but I'm only getting those default answers. Nothing really useful. A software repair at a "qualified google repair" in Germany costs me 400 euro......
[Google Pixel 3 Questions & Answers] marcuselia:
Here for the ratio as it were. Pixel 3XL, spontaneously bricked a couple of months ago. ubreakifix said CAD$500 to replace the screen, which I did not go for because my gut feeling was that this would be a very expensive first troubleshooting attempt. Went back to using my almost-4-yrs-old iPhone 8 until some clever fix comes around for the big phone. Bring on the firehose (whatever that is)!
[Google Pixel 3 Questions & Answers] AsItLies:
Smart move, pretty sure someone else did that, had the screen replaced, made absolutely zero difference, but cost a lot!

a 'firehose' is a small but officially 'signed' file that works in conjunction with Qualcomm's qfil utility. This utility program allows you to replace and backup the partitions on a device. But it only works through the EDL (Emergency DownLoad) interface...

But, that's exactly what these phones are stuck in, EDL mode. So **if** there is a way to fix them, that would be it.
[Google Pixel 3 Questions & Answers] elbello:
Wow, I also got hit with this... my daughters phone just went dead and I hear it connect to the PC and get that same QUSB_BULK-CID device... Guess no one found a solution but to replace the phone?
[Google Pixel 3 Questions & Answers] TheKial:
Looks like this is becoming quite common. Pixel 3, Android 12 Beta, stuck in EDL mode with a blank screen. Connects to PC as QUSB_BULK_CID. Contacted google and they responded with "your device needs to be repaired."

They have little interest in resolving this issue. Bricked phone is bricked, they won't give up the "key" to this lock.
[Google Pixel 3 Questions & Answers] jancoow:
Maybe raise more attention on the issue tracker.

Google Issue Tracker

issuetracker.google.com
[Google Pixel 3 Questions & Answers] shabazz18:
Mine Just did it on vacation. 100% stock
[Google Pixel 3 Questions & Answers] AsItLies:
Out of curiosity, was it the VZW variant? Wondering if the way vzw 'locks down' the bootloader has anything to do with it...
[Google Pixel 3 Questions & Answers] shabazz18:
Unlocked from Google
[Google Pixel 3 Questions & Answers] the1dynasty:
This happened to my gf's 100% stock, Google Store bought, bootloader locked, Pixel 3XL in January. Unfortunately I searched and searched and found nothing else for the Pixels. Plenty of info on LG phones and I think even OnePlus but nothing to help my case specifically. I tried many random attempts at ADB and Fastboot commands... Nothing seemed to work and I set the phone down for a couple months...

Then one random day in March I decided to plug the phone in to charge, by this time she was using my Pixel 3 because I bought the Pixel 5... The phone decided to turn on and show the Google logo and it actually booted up!!! So after thinking the display was busted somehow, it turned on long enough for me to factory reset the phone... As the phone was booting back up, the loading bar under the Google logo was moving for a couple of mins, then the screen went blank and I haven't been able to get it to turn on since March...

I thought that if I left it alone and drained the battery all the way down like I did the first time, that it would turn on again once I plugged it in... Still no luck and I'm not giving up on this phone...

So if someone finds out how to get this thing working, I can get it booted back up and maybe sell it or trade it in for the Pixel 6 in a couple of months... Thanks for the thread! Gives me hope that someone will eventually find a fix for this...

In case anyone missed it because I read this entire thread, the display is certainly not busted, don't waste your time with Google telling you to replace the display...
[Google Pixel 3 Questions & Answers] AsItLies:
So maybe this is a little info to help understand the situation better.

When a phone is in EDL (Emergency Download Mode), the screen is always completely blank. And the only way you know it's in edl mode is (as has been mentioned) when it's usb connected and in device manager you'll see the (as title mentions) QUSB_BULK etc.

So, what this means is 1) the phone isn't completely dead 2) but the only way you can access the phone is with qualcomm qfil type software, which talks to a qualcomm device that's in edl mode.

Normally, edl mode happens on purpose, meaning you intentionally press the appropriate keys to put the device in that mode. But in this case, it's happening because there's (more than likely) something wrong with the bootloader, and it's going into edl mode by itself (it can't do anything else). But, it is telling that the1dynasty actually had his bootup once, surprisingly, that seems to suggest it's hw related (where heat etc can sometimes affect it's working or not).

Just to clarify, I've no idea if there is a solution, but IT IS NOT a problem with the screen, a blank screen in edl mode is EXACTLY the way it's suppose to behave (in that mode). And replacing the screen will be very expensive and will do absolutely nothing to fix the problem (as has been pointed out by at least one person already).

I've had an LGV40 and for it, we have a file called a 'firehose'. That's a very specific file that allows you, while in edl mode, to modify the device (and that's why I know about edl mode). You basically have complete control of the device, i.e. you can change any partition. Unfortunately, the needed firehose file is 'device specific', and there isn't one for the pixel 3 (or any pixel afaik).

So, just to reiterate what the1dynasty is saying, it's NOT the screen! Don't let anyone tell you it is. I wish I knew what would fix it, at this point it's sounding hw related, but we may never know for sure.

cheers
[Google Pixel 3 Questions & Answers] peikojose:
Happened here too, P4.

There is nothing to do yet!
[Google Pixel 3 Questions & Answers] ZetaPirate:
Just registered to mention it's happened to me as well. I didn't even know this was a thing.

Pixel 3 bought unlocked from Google, stock everything... I'm seriously disappointed that there is nothing I can do. I'll wait a few days, I guess, and hope a dead battery makes a difference? I didn't notice anything up with it and I wasn't downloading anything as far as I am aware.
[Google Pixel 3 Questions & Answers] AsItLies:
sorry to hear that.

I'd encourage everyone that there is something you can do, complain to google. Yes, it's not likely to have an immediate effect, but they might feel more pressure to release the needed 'firehose' file, which could possibly fix the issue.

Just as an fyi, the pixel 4a threads indicate people having the exact same problem. All I can say is, be sure to back up all files that are critical, pics etc. And if u can, have a spare device (I have an old lg v30) around, just in case.

cheers
[Google Pixel 3 Questions & Answers] ZetaPirate:
Thanks. What is the best way to do so, and what is the "firehose" file actually called? I assume that's a "local" name for it and that whoever I talk to won't know what that is.

I have an old Galaxy S4 that I can use, but there was a reason I left it in the first place. With an activation fee of $35 each time I swap a phone, that's $70 if I buy a new one and swap them again. So now I have to decide if I want to spend another $800+, if I want another Pixel (I'm torn on this) and how long I want to be without a phone in between.

I love the Pixel because it isn't owned by the carrier and manufacturer. In my opinion, (and while I dislike IPhone) this is something Apple got right.

(Also, I can't imagine other brands are going to be any better at this point. Everyone is out to screw everyone, these days.)
[Google Pixel 3 Questions & Answers] AsItLies:
I think they'll understand 'firehose' file, but believe it's also referred to as 'programmer' file. The file is what's needed in 'Qualcomm HS-USB QDLoader 9008' mode. Without that file the software utility has no access to the device.

Some mfgs make that file available, if google did, there's a chance these devices could easily be fixed.

I'd encourage everyone to let google know you'd like to have that file, to fix your device.

cheers
[Google Pixel 3 Questions & Answers] ZetaPirate:
Can I assume these are not the files we are looking for? I know everyone has probably searched for this forever, but thought I should ask.

Driver Binaries for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 3 Questions & Answers] ZetaPirate:
Random thought I had... Has anyone tried to tear the device apart and disconnecting the battery? I'm not sure what good it would do with a modern device, but with my older phones, I could pull the battery for a bit and it would come back after a while.
[Google Pixel 3 Questions & Answers] AsItLies:
No, those don't include the needed file. Follow this link and you'll find numerous devices that have their needed firehose. sadly, pixel 3 (or others) not included.
[Google Pixel 3 Questions & Answers] AsItLies:
not likely, but, 1 person has already indicated that they did leave the device to sit for some time and it did actually reboot once. That (to me) would imply that it's a hardware error. So if you want to try something, I'd consider putting the device in the freezer for a period, to change the temp of the hardware, that may get it to boot once.

But here's the thing, even if by some odd chance it did boot once, it probably wouldn't continue to on subsequent tries. It's a long shot but for those that are desperate, doubt that it would hurt anything to try.

cheers
[Google Pixel 3 Questions & Answers] Mamai lc:
Like
[Google Pixel 3 Questions & Answers] ZetaPirate:
Yeah, it was worth a shot, I guess. I had seen that site with the firehoses and had already gotten my hopes up there. Right now, the phone is sitting on my desk in the hopes that a drained battery would miraculously help. I hadn't considered that it booting back to normal would not actually fix it though.

Do Pixel 5 phones have this issue? As scared as I am to get another pixel, I have my doubts that other brands are any better, really.
[Google Pixel 3 Questions & Answers] AsItLies:
not sure about the 5, but the 4a does, was just looking at the thread yesterday. Same exact problem. I was seriously considering a 4a too, my 3 is okay at the moment, staying there for now.

should add, I just returned a 5, yesterday. Wasn't sure if I could live with the 'speaker under the display' thing, nope, cannot. You have to turn up the vol to get the same level of sound, and then the sound starts to distort. Also, the 'screen lift' thing, had it. It wasn't bad on 3 sides, couldn't notice. But on the bottom, one side was as it should be, the other was 'lifted'. While yes, you could squeeze the glass and frame and it would go to as it should, but I highly doubt it would stay that way.

maybe it's just me, but don't google phones always seem to have hardware issues? Alas
[Google Pixel 3 Questions & Answers] NotAPirate:
Google Pixel 3.

Woke up Friday the 27th of August with a dead phone. It was set on Extreme Battery Saver before going to bed.

Original USB Charger won't help.

Anker won't charge either, the screen is not turning on.

Wireless charging stand seems to detect something but phone is not lighting up.

Regular power button doesn't help, Power+VolDown neither.

PC detects a QUSB_BULK_CID... sometimes.

Google Support said to bring the device to UBreakIFix. They diagnosed a broken screen and wanted to charge 300$ to fix it. I paid 150$ for the phone on ebay...

I'm about to try the M360soft Diagnostic software.

M360 / Mobile Diagnostics & Utility

The only phone diagnostic & utility app you will ever need. If you are in the mobile buy-sell-repair business M360 is your true, all-in-one tool.

m360soft.com

Crosspost with Reddit so we have more chances of finding a solution...

https://www.reddit.com/r/Pixel3/comments/mm7yp2
[Google Pixel 3 Questions & Answers] ZetaPirate:
Just out of curiosity, did M360 give you anything?
[Google Pixel 3 Questions & Answers] ZetaPirate:
I added a report to the issue tracker mentioned before. Now I'm looking at new phones, and can't decide if I want the Oneplus 9, or Samsung S21... I did read about some crappy ad tactics on the S21 though... :/
[Google Pixel 3 Questions & Answers] dcarvil:
Samsung is now disabling the camera when you unlock the bootloader. I don't know what models they are doing this on, though. See this post: https://xdaforums.com/t/magisk-general-support-discussion.3432382/post-85534107
[Google Pixel 3 Questions & Answers] NotAPirate:
I just picked up my phone from UBreakIFit after they said the screen was broken and needed to be replaced. I didn't buy that at all. M360 won't work for the QUSB_BULK issue. I will let my Pixel's battery empty for a few weeks, then recharge it and try to reboot again. Can't do much more than that...

I plan to buy another Google Pixel 3, because it is around 100$ and does everything I need for the moment. Eventually, when I get back to working at the office, I'll get a Pixel 6 (if it is a good phone after its initial hype has died off)

Here is the e-mail answer from Filip @ M360.

I tried rebooting with the power button and with power+vol down, nothing happened. I tried charging it with 3 different chargers and with my wireless stand, the screen never turned on.

My PC detects the phone as a QUSB_BULK_CID:xxxx device so I think something is happening with it but I don't know more. Would M360 be able to diagnose a burned screen? Let's assume the screen is broken and the phone stays at the unlock code but I can't enter it because the screen doesnt work, would M360 be able to diagnose it?

Unfortunately no. To use M360, you need a device that turns on and you can install the M360 app on it. If the screen is dead you won’t be able to do it.

Basically M360 is great to diagnose devices that you can turn on and they seem to be functioning well. You can check for not so obvious errors, for example, check if all microphones working, check the battery’s condition, check the mainboard by checking the gyroscope, accelerometer, bluetooth, wifi, etc.
[Google Pixel 3 Questions & Answers] ZetaPirate:
Oh, I see. Well thank you for trying. I wasn't familiar with that particular software. I ended up picking the Pixel 5. I considered another 3, or any refurbished, but the P3 I had almost made it three years. If I shell out the money, I usually hope a phone lasts five. We'll see how well this one works out, and maybe Google will finally address the issue with the 3 and 4 so it doesn't happen again in the latest versions.
[Google Pixel 3 Questions & Answers] NotAPirate:
Article about the issue, maybe Google will pay attention and offer help.

Pixel 3 and 3 XL phones are getting stuck in EDL Mode and seemingly bricked

There doesn't appear to be any clear solution to the issue

www.androidpolice.com
[Google Pixel 3 Questions & Answers] ZetaPirate:
Is Android Police one of those that like to pester companies for comments? I'm hoping this gets us moving in the right direction.

I read it, it reads good, but let's see if Google will do anything about it.
[Google Pixel 3 Questions & Answers] AsItLies:
That's encouraging to see, AndroidPolice is a well known and long time website and it's articles like that which can have an effect.

I'd point out, this exact same problem is being reported in the pix 4A forums. That *might* cause google to release the 'fire hose' for these devices and we may then have the ability to fix them.

cheers
[Google Pixel 3 Questions & Answers] rmnelson97403:
Total Noob question. Is an aftermarket ROM a way to avoid this issue? I've been thinking of installing Lineage OS on my Pixel 3 since updates stop soon and wonder if my better choice is to stop updating entirely or install Lineage OS. I'd like to get another 6 months to a year out of the 3 if I can avoid this problem. I'm not happy about no security updates if I stay stock, but advice is welcome. Thanks!
[Google Pixel 3 Questions & Answers] AsItLies:
I think that's an 'Unknown' if aftermarket rom will make a diff. All we know for sure is that the bootloader is either getting corrupted OR it's a hardware problem.

*If* it's hardware, a Rom won't help. I have Lineage on mine now, and just hoping I don't find it in edl mode some day. Have also done 1 ota update with Lineage, all went fine. Knock wood.

Afraid we just don't have enough info about this problem.

cheers
[Google Pixel 3 Questions & Answers] rmnelson97403:
Thanks for the info. A good phone while it works!
[Google Pixel 3 Questions & Answers] istrebitjel:
I guess disabling updates would "help", though.... right?
[Google Pixel 3 Questions & Answers] AsItLies:
Afraid we don't know enough, for sure, to say that. Some have mentioned their device quit responding not long after an update, but not everyone.

Some may not have 'made that connection', or they simply didn't do an update prior? Don't know.

The way I'd put it is; 'it probably wouldn't hurt' to not do an update. And, if I had to have a feature from (one of the few left) updates, I'd do it with the files and not OTA.

cheers
[Google Pixel 3 Questions & Answers] hiddeneclipse:
Made an account to reply here since the thread isn't 395834 years old and dead.

Had something very similar happen to me just now (5th of sep), as in woke up to find my phone (~1 year old Nokia 8.3) dead and unresponsive. first reaction was to put my phone charging since i hadn't charged it overnight, but there was no reaction to me plugging in the charger (which in hindsight might not have been a reason to be alarmed but I Had just woken up), but my charger had been acting weird recently, so I got up and tried another charger.

When that didn't give me any reaction either I started to panic for good, and went to look for help on phone not turning on, before I realised I could try to connect my phone to my computer to see if it's really doing something when plugged to a charger (at this point I was in too much of a rush to try and leave my phone charging for a longer time to see if the battery was just dead). Computer gave me the qusb_bulk_cid and I found myself here, but reading the first page I saw someone mention the volume+power button (which was what I was looking for when trying to find fixes on phone not turning on, since I feel like I've had to use that trick in the past), and got my phone to turn on just fine, with barely 2% battery.

Swapped my phone back to a charger that's not connected to my computer, and left it charging, while I went to get breakfast etc, and came back to read the rest of the thread in case I could be enlightened somehow, and my phone is now at 36% charge. Haven't tried to take it off the charger yet to see if battery drains super fast or if something else bad happens.

So tl;dr: phone died during the night, I panicked when it didn't appear to be charging, connected to computer only to get qusb_bulk_cid'd, but managed to turn phone on with volume+power button so don't know if my phone actually just had a very dead battery. So far no further complications, as everything so far has happened within the last hour.