yashsingh1/xdaforums huggingface dataset:
[Google Pixel 3 Questions & Answers] gpixel3user123:
Adding myself to the list.

- Google Pixel 3 64GB

- Purchased Nov. 10, 2018 for $999.00 CAD ($1138.86 CAD w/tax)

- Received Nov. 16, 2018

- Stock operating system; no modifications

- Light use

- Phone started randomly rebooting the last few weeks but otherwise worked the same as normal

- Battery life was still good enough to last a whole day of use with battery saver on

- Lasted 4 years, 7 months, 3 days (1676 total days)

- Cost per day of use was $0.68 CAD

I am surprised there isn't a class action. It seems like an obvious design failure for a technology device to fail within 2 years for heavy users and within 5 years for light users.
[Google Pixel 3 Questions & Answers] emkorial:
Edit: DISCLAIMER: Just because this worked for me does not mean it will work for you. It is STUPID easy to blow off micro components, warp motherboards, or otherwise completely destroy electronics using a hot air station if you do not have experience with using them. Do not try this unless you are 100% comfortable turning your phones motherboard into a 100% irreparable piece of scrap.

------------------------------------------------------------------------

Has anyone tried reflowing the Micron chip? I've successfully repaired other devices (not phones) that failed due to cracked solder balls by reflowing them.

Edit : SUCCESS!! (as least as far as I was willing to take it)

I opened the phone, made up a little foil mask to protect the tiny components from getting blown off, set my hot air station to 350C, and removed the metal cover hiding the Micron chip (the CPU and some other chips are in there too)

I added liberal amounts of flux around the Micron chip and added heat until the solder balls remelted and it passed the nudge test. Yes I know this risks shorting out solder balls but I don't have a full BGA rework station and the phone was dead anyway so I couldn't break it more

Anyway got it to nudge and pull back in place, I let the board cool, reassembled it, plugged it in, and it booted right up. Couldn't believe it. No signs of anything every happening to the phone, worked just fine. I quickly copied off all my data

So if you have the tools/experience to try the reflow give it a shot, maybe it will work for you too. I would not trust the device to stay operational long term, if the BGA connections failed on one chip, they are likely failing on other chips, and oxidation can form in solder ball cracks and prevent a solid electrical connection even after a reflow so it wouldn't surprise me if the device randomly died again. I just wanted the data off I already moved on to another device, never buying a Pixel again. Screw multi billion dollar corporations using the cheapest parts and assemblers they can find to save a penny at the expense of users.
[Google Pixel 3 Questions & Answers] gpixel3user123:
Thank you emkorial for the detailed post!

I tried a number of troubleshooting steps but alas has zero luck. My phone displayed a black screen with the message "Your device is corrupt. It can’t be trusted and may not work properly." before going into EDL mode so my issue is likely to do with the flash prematurely failing rather than a connection or other issue that can be solved by a simple "reflow".

Here is a list of steps I tried:

Basic troubleshooting:

- Attempting to charge via Google Pixel Stand (1st gen) and Google-provided USB-C cable.

- Pressing and holding the power button and volume down button for an extended period of time.

- Pressing and holding the power button and volume up button for an extended period of time.

- Pressing and holding the power button for an extended period of time.

- Attempting to drain the battery and power on the device using combinations of the above steps.

Advanced troubleshooting:

- Opening the phone and disconnecting the battery flex cable and charging assembly flex cable, waiting a few hours for capacitors to be fully discharged, reassembling the phone, and attempting the basic troubleshooting steps.

- Opening the phone, removing the motherboard (and removing the antenna cables from the motherboard), "reflowing" the motherboard in a toaster oven at 375F for 10 minutes, reassembling the phone, and attempting the basic troubleshooting steps.

Taking apart the phone was easier than I expected. I didn't have a fancy ifixit kit and instead resorted to a hair dryer (in place of the iOpener), cardboard (in place of picks), and fingernails (in place of a spudger). I did look for signs of water damage, battery bulging, and obvious component damage but didn't see anything. It does seem really easy to break the antenna cables and the earpiece speaker's flex cable when disassembling/reassembling the phone. I did end up breaking the earpiece speaker's flex cable on the second reassembly. If my troubleshooting had worked, I would have had to buy new adhesive for the back cover and the phone likely wouldn't have been water resistant anymore.

After the final reassembly, the phone still shows up as "QUSB_BULK_CID:xxxx_SN:xxxxxxxx" on a Windows 10 device so I have confirmation that I didn't fix the phone but also break it disassembling and reassembling.

For anyone reading this, if you have a couple hours of free time I do recommend disassembling the device and attempting the same steps as I did. At least you'll have some piece of mind that you tried everything and got some experience taking apart a phone.
[Google Pixel 3 Questions & Answers] InvertedB:
Pixel 3XL died this morning, another one on the pile :(
[Google Pixel 3 Questions & Answers] emkorial:
The error seems to have to do with the phone not being able to access what it needs from the Micron chip. I'm not an Android dev, but from my reading, it seems the phone boots up, then tries to read something it needs from the flash memory chip, it can't, and as a result the phone dumps into EDL mode.

There are only really two scenarios why the device cannot access the contents of the flash memory chip, either the chip has failed (and if so there's nothing you can do about it) or the connection to the chip has failed (and that connection might be repairable). In my case it looked to be the latter since a reflow fixed it. But there is also no way of knowing if I just got lucky and my issue was connection related but everyone else is chip failure related.

I don't recommend "oven reflows", the only way to KNOW the solder balls have remelted is to nudge the chip and see it move then pull back into place via surface tension, and you obviously can't do that when the board is in an oven. Also without any air movement the transfer of heat is limited. You want to be blowing hot air on the chip, not sitting it in a hot environment. And even if the solder did melt, you would be reflowing every chip on the board at the same time with an incredibly high chance of causing a short among the BGA connections. My way of using a hot air station is already the wrong/dangerous way to do it, an oven is even moreso. With bigger chips that have larger BGA connections ovens can be OK (People do it a lot when reflowing chips in Flat Screen TV Control boards) but everything in a phone is miniaturized. That tiny little chip has 168 BGA connections on it.

None of your other steps really have anything to do with the Micron chip so I wouldn't expect them to make any difference.
[Google Pixel 3 Questions & Answers] m_wali:
I am very certain Google is behind all this, I updated Google Keyboard app very recently and the phone started acting weirdly since then (I even reported it to the developer, and it is so unfortunate that we can't roll it back to the previous version if such a buggy update is sent to our phones).

Weird been to such a level that the keyboard typing would froze so I changed the default keyboard to another one offered by Microsoft temporarily. Used it for a day then switched back to default one that I updated and moments after that my POCO X3 Pro died, wont turn on, and completely unresponsive. And when connecting to computer it is showing the same QUSB_BULK_CID with some numbers as others have mentioned.

This is a def scam update offered by Google that completely made our phones useless when it had no physical damage of any sort or any sign of misuse like fire, water, lightning or heat exposure.
[Google Pixel 3 Questions & Answers] emkorial:
Doubtful this is a software issue. Everything points to the issue being caused by the phones inability to read from the Micron chip/flash memory, which is a hardware failure (this is also Google "official" response). It dying after changing an app is probably coincidental, but then again who really knows. There may be multiple things behind the failures.
[Google Pixel 3 Questions & Answers] HHigh:
can you guys also post your storage version ? maybe it can due to the 64GB version having a worse quality UFS chip ?
[Google Pixel 3 Questions & Answers] CTere:
My smartphone poco x3 pro happen the same, died overnigth
[Google Pixel 3 Questions & Answers] phoenixpb:
Hi guys , i don't know if it's serious or not but firehose files would be located in /data/misc/firehose

Only one problem you need Root access to copy them.

I can't test my pixel 3 xl is bricked
[Google Pixel 3 Questions & Answers] ShadowVlican:
Not sure if I replied this thread in the past, but my P3XL encountered the same problem right before I was trading it in for a P6P... just my luck.

Prior to this, I have an OG pixel with a bulging battery and a dead Nexus 6P... that's THREE google devices that have died. I have no confidence in Google making a long lasting phone, so I don't care that they recently announced 7 years of OS updates for the Pixel 8. I'm done with Google.
[Google Pixel 3 Questions & Answers] kungpowchimken:
Shame to hear all this. I've had the pixel 3 for years now with no issue and genuinely like the phone. I was watching a stream last night and phone died at 4%. I let it charge for a bit, and it did reboot, but died again while plugged in. When I would unplug, it would die, so maybe that CAUSED the boot cycle problem. I let it charge overnight but woke up to that cursed black screen. I'm praying that draining will help it reboot, but it couldn't happen at a worse time. Have a flight tomorrow morning....
[Google Pixel 3 Questions & Answers] Fluxtopia:
My 2nd Pixel 3XL bricked last night ...I purchased it after my screen cracked on my first Pixel 3XL February 2022.

The phone may have been in developer mode before it failed because of issues I had installing a SIM card when switching mobile service providers in March.

My old 3XL with the cracked screen is now my working phone. I can plug both phones into the PC and COM3 Qualcomm HS-USB QDLoader 9008 shows up for the bricked phone. The USB driver won't install for the working phone, but I am able to access the device using ADB. I haven't had the same access with the broken phone.

I'm not a developer, but I did read that having a second Pixel 3XL might be useful to recover the data? Anyone who could provide resources that would help me understand how to get the data off the phone I would really appreciate it. I'd be happy if I could just get the pictures from the phone but I know as soon as I can access it I'll find more things I really need.
[Google Pixel 3 Questions & Answers] Nunya Biznass:
Adding to the list here.

My kiddo came home from school today and said his phone wouldn't turn on. Was fine this morning (he uses it as his wake-up alarm), but when he went to use it at lunchtime, it was just a black screen.

I can't get anything to display at all. Doesn't visually respond to power button being held, not alone or in combo with Vol+ or Vol- keys.

My Win10 laptop chimes when I plug it in, and the Device Manager shows it as

Other Devices/QUSB_BULK_CID:0402_SN:DB608DBE

When I hold the power button while plugged in, after about 15 seconds the laptop chimes and the device disappears, then chimes a few seconds later and it reappears. But the device itself shows no indication of any activity.
[Google Pixel 3 Questions & Answers] webwude:
Joining the list as well.

Used a Pixel 4 for my daughter's diabetes management. It is more or less one app which is controlling the sensor and the insulin pump. It was used via family link.

Charged the phone to 100% and we went all to bed. According to the readings the phone stopped working at 2pm in the morning and is dead ever since. My daughter almost went into hypoglycaemia as the phone was not longer present.

Tried all sorts of reviving techniques - no luck so far. Gladly we still had the predecessor (pixel 3) for my girl...
[Google Pixel 3 Questions & Answers] 90Ninety:
Just adding to the list

I got my my mum a used Pixel 3 , was in perfect condition . I flashed it with Lineage OS , was working a few months .. Then just died overnight with the QUSB_BULK being the only sign of life

Will be avoiding Google phones
[Google Pixel 3 Questions & Answers] Zilch163:
Anyone else interested in starting a class action lawsuit?
[Google Pixel 3 Questions & Answers] Cubzfan:
Time for the annual follow up.

After sitting for another year, I plugged it in this afternoon and the little battery icon came on the screen. Let it charge until it was full and it's now up and working yet again. We'll see how long it lasts this time, but there is again hope if you've got pics or something you want to snag. Let it sit for about a year and then try again.

Happy New Year All!
[Google Pixel 3 Questions & Answers] Adelgamal:
The solution is to setup tha cualcomm driver on ur computer
[Google Pixel 3 Questions & Answers] pixel_unbricker:
Could you please send the link to the driver package.

It just happened to me today, and I checked and indeed my pixel 3 XL still gets recognized by my pc.

View attachment 6054042
[Google Pixel 3 Questions & Answers] Chibsz:
Just wondering how long your Pixel 3 is working this time you managed to get it up and running ?

This just happened to me 5 days ago and it seems to have the same symptoms as everyone else that has posted.

Did you try doing a factory reset by any chance after you manged to get it working ?

I'm hoping that a complete battery drain would allow me to at least start my phone so I can get some data off it... and maybe a factory reset afterwards might allow me to keep the phone functional instead of being a paperweight for the majority of the year (backing up photos to Google One etc).

In the meantime I've pulled out my Nexus 5 just to tie me over. Disappointing that my Nexus S and 5 both still work but a completely stock Pixel 3 bricks itself.
[Google Pixel 3 Questions & Answers] Cubzfan:
It only lasted for about a day this time around. I wasn't really using it for anything as I had already pulled everything off last year. I messed around with it a bit that day and then plugged it in and left it to sit. When I came back, it was dead again.

I have not done a factory reset on it. Maybe I'll try that next year if I remember. You may not have to wait a full year to get a full battery drain, but that's what worked for me. Probably best to just throw it in a drawer and forget about it for a few months. Good Luck!
[Google Pixel 3 Questions & Answers] brainwash123:
Pixel 3 here, was just plugged in and reporting temperature for the past ~4 years. Died some weeks ago, with a bloated battery, second battery that is. Ordered a new (3rd) battery, installed it, saw the boot screen two times but the phone just went to black screen. Same QUSB device. I think all big tech channels should be alerted about this issue and mention it every time they review a pixel phone. This is unacceptable. All my older phones and tablets still work and have seen more flash abuse than this.
[Google Pixel 3 Questions & Answers] Mr Tots:
Adding to the long list as well here.

A couple of weeks ago I woke up to find my Pixel 3 dead, which was shocking since it was working completely fine the night before. Befor stumbling onto this page today, I had taken it to a phone repair shop which said that everything they tested seemed to be working ok (the battery, the screen, the charging port..). They suggested replacing the motherboard and I have since been browsing online for one.

I have already upgraded to the Pixel 6a but would love to get my pixel 3 back up and running.

Has the fix been found?
[Google Pixel 3 Questions & Answers] Mr Tots:
Just came across read the "unrecoverable hardware failure" post.
[Google Pixel 3 Questions & Answers] Chibsz:
Not that I've found unfortunately...

One or two people in this thread said that they tried testing their Pixel 3's after it sat there for 1 year and they managed to get it working before it bricks itself again.

Someone also said that they tried pulling the battery and it did nothing for them. Makes me wonder if they pulled the battery and let it sit there for a while without a battery, would it make that battery discharge solution any quicker ?

(Presuming that some capacitors or maybe a smaller battery inside the phone is holding charge despite the battery itself being disconnected / replaced - unlikely but it doesn't explain why replacing the battery doesn't fix it)

Since Jan I've been periodically checking my P3 every few weeks. A few weeks ago the whole "QUSB_BULK_CID:xxxxx etc" disappeared from my Device Manager and it got replaced with a "Qualcomm Device", but it's still not charging nor booting up.

I've just switched to a new phone and might just try the P3 in a year or so to see if I get lucky like the others.....
[Google Pixel 3 Questions & Answers] PetNoire:
This is wild. my pixel 3 just did this. It was fine, complaining at me all morning that the battery was low while i brushed it off. it finally died, i plugged it it and it was stone dead, same as everyone here.

my backplate was held on by cheap replacement tape so it was easy to reconnect the battery, didnt change anything, still borked. phone was flawless up until this, only thing was putting a new battery in a few months ago
[Google Pixel 3 Questions & Answers] stpenn123:
Same issue here on the 3 XL.

May have been a coincidence, but I did reboot because of the May OTA earlier in the day. Seemed fine for a few hours, then went to pick it up and completely dead. Shows up as

Qualcomm HS-USB QDLoader 9008 connected to PC. So I guess its just booting in EDL mode.

Anyone have the qualcomm firehose files or a solution to this??

At the very least I'd just like to be able to get to my data.
[Google Pixel 3 Questions & Answers] tarung81:
It also happened to my missus's pixel 3xl 5 days back. When I connected it to the computer can see QUSB-BULK. But cannot start the phone as well. What is going on here? Is Google purposely bricking all pixel 3 phones?
[Google Pixel 3 Questions & Answers] bobbintb:
Just had this happen today at work. It was on my desk fine. Picked it up a few minutes later, dead.
[Google Pixel 3 Questions & Answers] kaykhoso96:
Same happend to my Pixel 4 XL today.. Wokeup in the morning with dead phone.. Plugging in shows QUSB_BULK_CID:0404xxxxxx.

Has anyone able to figure out the fix?
[Google Pixel 3 Questions & Answers] moohan123:
The same thing happened to me two nights ago: Pixel 3XL Running Android 12 Beta 1, no issues, overnight it broke. Woke up to a screen saying 'phone corrupted' It was similar to this: xdaforums.com/t/your-device-is-corrupt-it-cannot-be-trusted-huh.3582779/, unfortunately, I didn't take a picture, etc.

Since then the phone is off and completely unresponsive to any button presses (no recovery mode boot etc). When plugging it into my Windows PC it is seen as -

QUSB_BULK_CID:0402_SN:FA3EECC5 . I've tried forcing Google drivers onto it, I also tried adb and fastboot but I don't really know what I'm doing with those! If anyone wants to suggest commands I'm happy to try them and post the results.
[Google Pixel 3 Questions & Answers] tommygnns:
Hi - The same issue happened to me yesterday morning where I woke up to a bricked Pixel 3. None of the troubleshooting methods worked (plugging in device & letting it charge, holding various button combos, etc.).

My PC is able to recognize the device via USB with similar device info listed in device manager that other people have posted earlier in this thread (QUSB_BULK_CID:xxxx_SN:xxxxxxx).

I had installed the June 2021 security update about 5 days ago. I don't know if there is any possible correlation.
[Google Pixel 3 Questions & Answers] LegalMario:
I bought another phone, I am ever decided to buy a pixel my phone was in excellent condition and I do not find a solution.
[Google Pixel 3 Questions & Answers] AsItLies:
Not sure if this will help you guys, but we put the LG v40 into edl mode regularly. To get the device out of edl mode hold volume down and power for about 5 seconds, or for as long as it takes for it to start to boot.

The really strange thing is that your devices are going into edl mode on their own. That makes it sound like there's some kind of a problem, and there may be no way to exit edl?
[Google Pixel 3 Questions & Answers] jasestu:
Thanks for the suggestion, but I think the reason these phones are falling into EDL mode is because the bootloader has been corrupted during an attempted update - it's in EDL mode because there's nothing else it can boot into. I'd speculate it some link with that "clever" new approach of being able to update the OS in the background and switch to it on the next boot.

I've tried various hardware button combinations and nothing seems to work. Have even let the battery drain stone cold and then tried to breathe life into it. Feels like the only approach is the QFIL/firebase approach mentioned earlier in the thread.
[Google Pixel 3 Questions & Answers] AsItLies:
Well, that 'clever' new approach you refer to is project treble, and by no means is the pixel 3 the only phone using that. Virtually every phone made today uses it, and they aren't experiencing the same issue.

The 'normal' way to exit EDL is the one I mentioned. Works every time I've ever done it. So it not working for this device tells us, something else if F'd up, for sure. I'll have to re-read for the qfil solution, as qfil is not that difficult to get up and working.

But from what others in this thread have experienced, this is a devastating thing to be going wrong. To have your device, completely out of the blue, become completely unusable, that's so wrong it's not even slightly funny.

Doing some additional research, looks like the mmcblk0 image is getting corrupted. I don't see, following the qfil threads / mentions, that there is a firehose specifically available for pixel 3. I have one for sdm845 chip but it's for lgv40 specifically, I believe.

So, it appears, correct me if I'm wrong, that even having the mmcblk0 image (not corrupted of course), there's no way to flash it to the device without the specific firehose?

And, this has happened with other devices, but doesn't look like that many, HTC and another I saw, but also other pixels, including the pixel 2. But I've never heard of it happening with LG v30, 35, 40 (which are my recent devices).

still searching for more info.
[Google Pixel 3 Questions & Answers] jasestu:
Thanks @AsItLies, no specific firehose is where I ran out of options when I deep dived the issue when it first happened to me. Unless someone smarter than me (not hard) finds a solution, I'm left waiting for Google to decide to release (or someone to leak?) a firehose. Not holding my breath there.
[Google Pixel 3 Questions & Answers] utahphunk:
Registered here just to post in this thread. My girlfriend's completely stock, vanilla, non-rooted Pixel 3 was bricked by this 2 days ago. Same exact situation everyone else has described here. After spending an entire day researching this, I had to give up and file a device protection (which we have through Google Fi) claim to get her a replacement phone for a $79 deductible.

Did we really just get F-ed by Google with no recourse? She'll end up being without a phone for about 5 days if the replacement arrives when they said it would. That's a pretty bad look when someone is looking for a job, too. We're absolutely furious here.