[FIX] Pixel 3 QUSB_BULK_CID:xxxx_SN:xxxxxxxx

Search This thread

theassailant

New member
May 29, 2022
1
0
Made an account to post here. Had the QUSB_BULK issue happen to my OG Pixel XL a while back. Guess we never got a fix for that.

Noticed a week ago my battery was bulging and lifting the back glass on my 3 XL. Ordered a replacement battery and successfully swapped it. Everything looked fine when powered back on, no issues, fingerprint reader worked. Not my first phone repair rodeo. Set it to charge in order to calibrate. Next thing I know the entire screen is a deep red and not responding. Power cycled and nothing. Set up some devices to drain the battery and recharge, nothing.

PC recognizes it as a Pixel 3 XL, and stupidly I pressed the power button multiple times seeing if maybe it was just stuck and had an awkward call with a 911 operator. So clearly the phone works, no idea why the screen would just randomly go though.

Not even sure if this is related to the thread issue at all but it seems the Pixel was downloading something of multiple gigabytes in the background while charging, Google Wifi tells me that much.

Shame because I was hoping to pass it onto my uncle who needs a new phone but doesnt want to spend money on one. Figured a $1000 phone from a couple years ago would work fine, guess not. Feeling even more justified in recently giving up on Google products.
 

ernoor

New member
May 29, 2022
1
0
This problem has happend to my pixel 3 this morning. I am disappointed that there is no solution for that. My phone was a good condition.

I am surprized with number of affected phones that I have read about in this thread alone.
 

justinCOYG

New member
May 29, 2022
1
0
Такая же проблема случилась вчера с моим пикселем 3xl. Ребят, неужели нет решения этой проблемы?
 

ajb_uk

Member
Dec 26, 2017
8
2
Sadly I need to add my voice to the list of affected phones. Perfect condition Pixel 3, owned from new. Only issue had ever been a glitchy power button at one point (fixed with compressed air).

Went to sleep with the phone on charge, checked the time overnight and it was fine, woke up to it being dead and in EDL mode.
 

PierreDunn

Member
May 17, 2022
6
0
Такая же проблема случилась вчера с моим пикселем 3xl. Ребят, неужели нет решения этой проблемы?
Чел, у меня на P4 такая же трабла. Как мне сказали, чтобы как-то оживить телефон нужно снимать память и перепрошивать. Проблема в том, что программатор для пикселей последний раз видели в 17м году и то на первые 2.
 

kaurimon

New member
Jun 7, 2022
1
0
Same story as previous users. Owned the phone for over 3 years without a single issue. Never dropped, always in a case. Set the alarm in the evening and put it to charge. In the morning (today) phone dead, does not respond to anything and shows the same name (QUSB_BULK_CID:xxxx_SN:xxxxxxxx) when connecting to a PC.
 

sseulgi

New member
Jul 1, 2022
1
0
Welp, my loved 3XL finally bit the dust. I tried it pretty much all now and I don't even get a QUSB_BULK anymore. Off to a OnePlus, I guess. I'm sorry for the imminent rant; it's the third time something like this happens to a Google Phone of mine, first my 5X, then my OG Pixel, and now the 3XL. Google really needs to release a tool to fix our phones or just make them reliable past two years. smh

Hope you guys find a solution.

Cheers.
 

dzuck89

New member
Aug 31, 2010
4
0
Is there any fix to this? Woke up with what I think is this issue today - thread says [FIX] but I can't find any info on what the fix is...
 

khorne01

New member
Jul 5, 2010
2
0
Another casualty here. This morning battery was around 16%. Trip to work (less 30 minuts) and the phone is dead. Plug into PC and get the QUSB_BULK... device.
I hope firehose is released at some point... but now looking into getting a Pixel 5 or maybe wait til 6a available....
 

ccomtruise

New member
Oct 5, 2012
4
1
My Pixel 3xl just fell victim. Took a nap, when I looked at the phone, bricked. Found this thread and checked in device manager and it is listing QUSB_BULK.

The response from Google is disgusting. If they really leave us all out to dry, I won't be buying another Google phone. The phone was great, and seemed so dependable. Such a waste to have it fail like this.
 

white stormy

Member
Feb 23, 2008
31
5
same boat with my dad's phone. he's more pissed about loosing all the pictures and videos he had on it. never had sync turned on.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    For how long were you using 3XL? Also, had you upgraded to 12? My 3XL is 2.5+ years old at this point and I am extremely worried :|
    Since December 2018, had been keeping it on Android 11 to keep my root active, until I did an upgrade to 12, then put LineageOS on it. Had been running that for a week or two before it died.

    I contacted Google and they just told me there was nothing they could do. This will be my last Google phone after dealing with this and the Nexus 6P. Bought a Motorola One 5G Ace since it has an unlockable bootloader, headphone port, and MicroSD card slot, and way more affordable than Pixels. Switching from Fi to AT&T too.
  • 2
    Sorry to necro this thread, but this literally just happened to me over night. Did anyone find any solutions or am I SOL?
    I was SOL. The 4a is nice ¯\_(ツ)_/¯
    2
    Happened to my unlocked, vanilla Pixel 3 (ordered 1/20/2019), in EDL mode and non responsive to any button combo, shows in device manager QUSB.

    I believe I was at the most recent version of 12, non-beta. Last night, I was in Play Store and updated Messages app to latest, along side a Carrier Update and some others (can not recall). I also uninstalled a selection of apps to free up space. This morning, I woke up to a bricked phone.

    I have been on Android 12 for a couple weeks, no issues until today. Curious about the Carrier Update (and/or possibly another one). As much as I am willing to believe this is some major neglect on Google's software... even possibly planned obsolescence, I have a feeling it (great source, I know!) that it may have to do with the flash storage reaching it's limits. Not trying to excuse, just searching for an explanation like us all.

    I have the device protection plan with Google Fi. Spoke with their support, the first go around we went through the obvious steps. I even sent a screenshot of the device showing up in device manager, including S/N. When that went no where, the support rep said we could skip the device repair and go straight to replacement. He mentioned that the replacement would be "with whatever they had in stock" and I had some hope of getting a new/refurb 4 or higher. Unfortunately, I got the replacement email and it was for the exact same model Pixel 3, storage and color, refurbished. I contacted support again, and asked to cancel my RMA as I did not want another Pixel 3. I also shared how this issue seems to be common, sent them the Google Issues link, and that Google needs to make the firehose file available to end users to allow them access to their phones stuck in EDL mode. The rep said there was nothing they could do. The RMA cancellation had to be raised to their next tier of support, and that I would be contacted via email by said support. Still awaiting that email as of this post. I will also broach the topic of making the firehose available to end users.

    I starred the issues tracker, since no more comments can be entered.

    I also filled out the class lawsuit form, any pressure is good so long as it ends in Google releasing these firehose files. Arbiration opt-out be damned, if it takes hold that will likely not have much weight in the matter (IANAL).
    Sorry to hear, don't blame u at all being rather pissed, I'm not happy either having a pix 3.

    One important thing though, the firehose would give us access in EDL mode, but **if** the problem is failed hardware, then there's nothing that could be done even with the firehose.

    That may be why google is approaching this as they are, they may prefer to leave this as a *mystery*, rather than have it be known as hardware failure. Additionally, I"ve read of this now starting to occur with the 4a and the 4.

    I'ts a pretty big mess really. I'm personally switching back to my LG preference for daily driver. Last thing I'd like to have happen is to need to make an emergency call or something, and find the device is dead.

    cheers
    2
    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...

    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
    2
    Today, 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.
    2
    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...