One more Pixel 3 (my girlfriends) doing the same, suddenly, out for a walk, and stopped working, and not coming back to life...
Ridiculous, and a clear message from Google for NOT buying other of their phones again. I mean, 4 years I know that is good time for a phone, but sudden death, and checking and seeing that is more common than what I expected, is ridiculous.
Will wait to see if we can recover all what is inside (which is the biggest problem overall), but definitely, all doubts of whether buy a Pixel7 or not, are clear now.
Ridiculous, and a clear message from Google for NOT buying other of their phones again. I mean, 4 years I know that is good time for a phone, but sudden death, and checking and seeing that is more common than what I expected, is ridiculous.
Will wait to see if we can recover all what is inside (which is the biggest problem overall), but definitely, all doubts of whether buy a Pixel7 or not, are clear now.
while I'm still not sure what the problem is on mine (no power but nothing on Device manager either no matter what I do)...
in terms of Data Recovery... F U C K
(in my case... is there still some hope that the flash memory could be recovered by peeps like DriveSavers or other much-more-local data-recovery services?)
Yes, other Pixel models have had the same issue, models both older and newer than the Pixel 3.
Last edited:
Yes, I believe I saw reports of the same problem with a Pixel 2. You can search the Pixel 2 forums to be sure.
So, no fix? I had the same issue happen to me. I'm on Pixel 7 Pro now, but I still have this old phone and has the same issue as everyone here. Computer recognizes it, has the same name in Computer Manager.
No one came up with a way to force this thing to take a stock rom or anything?
No one came up with a way to force this thing to take a stock rom or anything?
It seems safe to assume this will never go anywhere, especially with Google (and a few auxiliary sources) suggesting it's not a fixable issue - but for anyone else watching this thread...
I just experienced this with a Pixel 5a that is barely over a year old.
The device was actively being used (browsing Amazon) when the screen froze for several seconds, then went black. The usual button-holding procedures did nothing, so I left it for the night, and the next morning randomly got the regular recovery mode to appear, and rebooted normally from there. Roughly 24 hours later it did the exact same thing again, and I have yet to wake it up a second time. I see the same QUSB_BULK_CID device when connected to a windows PC as others have reported.
For what it's worth, the storage on this particular device has taken a real beating, being completely filled up and emptied numerous times in the (short) time it was in operation. That would track with the suggestion that this could be traced back to physical degradation of the storage hardware.
Perhaps we're seeing a subset of Pixel devices with subpar storage chips, much like the knockoff flash drives that tend to fail much quicker than reputable brands?
I just experienced this with a Pixel 5a that is barely over a year old.
The device was actively being used (browsing Amazon) when the screen froze for several seconds, then went black. The usual button-holding procedures did nothing, so I left it for the night, and the next morning randomly got the regular recovery mode to appear, and rebooted normally from there. Roughly 24 hours later it did the exact same thing again, and I have yet to wake it up a second time. I see the same QUSB_BULK_CID device when connected to a windows PC as others have reported.
For what it's worth, the storage on this particular device has taken a real beating, being completely filled up and emptied numerous times in the (short) time it was in operation. That would track with the suggestion that this could be traced back to physical degradation of the storage hardware.
Perhaps we're seeing a subset of Pixel devices with subpar storage chips, much like the knockoff flash drives that tend to fail much quicker than reputable brands?
Regiestered just to drop a line and let y'all know that the same thing happened to my pixel 3xl today (3/20/23). Overnight, it bricked and nothing I've tried brought it back.
Damn, I replaced the battery a few weeks back with an ifixit kit too. I was hoping to get a few more years out of it...
Damn, I replaced the battery a few weeks back with an ifixit kit too. I was hoping to get a few more years out of it...
My Pixel 3 has also met this fate. Went to bed on 3/20 and everything was fine. Woke up 3/21 realizing my alarm never went off. Picked up the phone and it's completely unresponsive and dead. I get the same QUSB_BULK_CID device as others when plugging it in to a PC. I had notifications on my watch up through 4:15am, so something happened to it between 4:15am and 6:15am when my alarm was supposed to go off.
Since you have the ifixit kit, can you see if removing the battery and reinstalling the battery helps???? Some people here hinted that might be due to the phone entering in a continuous loop and that is fixed in some cases after months of not using it once the battery goes to 0. So it would be great to know whether if you unplug and replug the battery, helps to at least start it once to get the photos that the phone contains...
Thanks!!!
Tried removing the battery but it didn't work sadly. just got a Pixel 7 to replace the poor pixel 3.
I had the exact same experience on my Pixel 5a yesterday. I was browsing the web at 80% batt when it just froze and eventually shutdown. Tried every button holding trick, plugged it into AC charger, nothing. Then I plugged it into my laptop USB port, and the laptop made the "you plugged in a USB device noise". I waited a couple of hours, and I was able to boot up the phone just fine.
Except 24 hrs later, it went dead again. And when plugged into the laptop, it shows up as QUSB_BULK_CID.
Argh.
OG Pixel XL, had it from new for 3 years, just died like that, while browsing facebook. It was lagging and working slow seconds before it died. No updates. At least I had a backup of my photos, but it's outrageous for smartphone to die like that. I wanted to update to Pixel 7, but now, I'm not so sure to trust a Pixel. Don't know if it was a software issue, or flash degradation.
I use a Pixel 4XL and I also encountered this problem today. It happened suddenly and now I have lost trust in Google. They don't provide any 9008 data packages so I can't recover my phone and I've lost all my data.
maybe you can try just take it apart with tutorial in ifixit and disconnect the battery and replug it again?
My two teenagers both had Pixel 3s and both phones died of this fate this month!!! My wife and I use Pixel 3 XLs, so I guess we're sitting on time bombs.
This sucks. Never buying a Pixel phone again
This sucks. Never buying a Pixel phone again
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
5This issue happened to me a couple days ago, and I came across this thread. I happen to work at Google, so I spoke to some Pixel engineers.
They ran some debugging tool and one of them has actually seen this exact issue before. It's a failure in the flash memory chip. They sent a device just like mine to Micron, a couple months ago, and the result was that the UFS is failing to initialise, likely due to having exhausted its natural lifetime of write cycles. The phone gets stuck in QDL mode because it's waiting for a broken chip to give a "wake" signal that will never come. So they can't even firehose it out if they wanted because the device simply cannot read anymore.
Only Micron would have the tools to pull the data, but even if they did, it's encrypted with the PIN number PLUS the secret key in the Titan security chip, the latter of which can't be extracted. So RIP in peace.
Phone flash memory chips are cheap because manufacturers expect you to replace device every 2-3 years and only lightly use storage. A high quality microSD card has much better write endurance. Alternatively, the less storage you use, the more free space is available to take hits and avoid total catastrophic failure. All drives actually hide some space from you in anticipation of blocks wearing out (kind of like EV batteries) - but setting a limit for yourself will give you a bigger runway, and also force you to improve backup discipline.3
My phone bricked almost exactly 1 year ago. Plugged it in New Years Eve night, woke up the next morning to a dead phone. My search for a fix brought me here, I bookmarked and checked back in every few months to see if there was any progress.
This post sparked my interest so I went ahead and plugged in my Pixel 3 this morning, not really expecting anything. Lo and behold I got the charging pic along with a 0% I let it sit for awhile until it got to about 75%. I held in the power button and the Google spun up and a minute later my phone was back. Like above a ran to my computer and copied everything over. I got it all and an hour later the phone is still up and running.
So there is hope!! I suggest everyone give it one last try. It's been about 6 months since the last time I tried. I don't know what was different today, but it worked.2Today, after a few days worried about this ****, my pixel 3 has dead in the same circunstances. During the morning at around 1 pm, screen goes black, and only can connect pc and read "QUSB..."
Tried to contact Google support, tried scalated to tier 2 support, and only get "Send to repair to Google" (431€ in my case), and nothing more, out of warranty and goodbye.
Was thinking about get a pixel 6 (i keep a nexus 5 working till the days), and was planing to keep this pixel 3, but now i don't know what phone buy, but this makes me think: NOT A GOOGLE PHONE.22
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
