[FIX] Pixel 3 QUSB_BULK_CID:xxxx_SN:xxxxxxxx

[Dheerajvirgo]

Oh wow this literally just happened to me today. I picked my phone up from my desk and checked my notifications, put it down and then picked it up 10 minutes later and it was completely bricked. This is what Device Manager shows:

View attachment 5292881

My phone was at 50-60%. I've tried everything. I guess next would be to let it die and see if it boots back up. I have some important data on this phone that wasn't backed up. I hope there's a fix .

did you got your phone fixed? what was the issue? my redmi note 10 is going through same

 

[josevu]

f google, same thing happened to my wife pixel 3 xl, my pixel 4 xl cannot recognize the battery level, will never buy google things again

 

[bdubbin16]

Pixel 4XL here... was hoping there was some sort of solution. I had plugged my phone in before it crashed. It was at about 60%... checked a few hours later and it was bricked with it showing up in Device Manager as stated in the thread subject.

If nothing happened when I plugged it into a PC I'd say, okay - it's dead... but because the PC recognizes it's not totally totaled I figure we collectively should be able to get these things out of dead mode (recognizing they're not just plain dead!) and be useful phones again.

 

[AustraliaX]

Does anyone know f I'd able to keep all my files and data after I replaced the the motherboard? I plugged in my Pixel 4 XL to a PC but I could not see anything pop up in the device manager. Though the PC did play the usual chime when a USB device is plugged in. I am planning to replace the motherboard as replacing the battery did not help.

Thank you in advance.

 

[cyang812]

I met this issue two years ago, my pixel 3 phone suddenly can't boot up. And I got it fixed in Shenzhen Huaqianbei where you can find anything related to electrical devices. I didn't lost any data after it got repaired. Four month later, the repaired phone suddenly bricked again during the night, and I got fixed one more time at the same store I went to with the same price. However, it dead again in 6 month and I left Shenzhen and can't fix it now. I deeply believe there is a way to fix it and without any data lost as what I did before.

 

[oburt]

This just happened to me as well. Pixel 3, originally bought in 2018 so we had a decent run but still very frustrating for it to brick without warning. No relation to any update or any action, it was just sitting on the table when I went to use it and it was black and completely unresponsive. Checked the device status by connecting to my PC by USB and saw the same Other Device > QUSB.... designation, so assume it is the same issue as everyone else here. The only upside is thanks to this thread I didn't have to hesitate wondering if I should spend much time or effort trying to resurrect it and immediately went ahead shopping for a new phone.

 

[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.

 

[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.

 

[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.

 

[InvertedB]

Pixel 3XL died this morning, another one on the pile

 

[emkorial]

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".

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.

 

[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.

 

[emkorial]

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.

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.

 

[HHigh]

can you guys also post your storage version ? maybe it can due to the 64GB version having a worse quality UFS chip ?

 

[CTere]

My smartphone poco x3 pro happen the same, died overnigth

 

[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