• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[FIX] Pixel 3 QUSB_BULK_CID:xxxx_SN:xxxxxxxx

Search This thread

nullx

Member
Sep 7, 2010
20
4
I just took the official android 12 update yesterday... phone was working fine.. went to sleep, woke up, and now am getting the same issue as everyone else..
 

AsItLies

Senior Member
Nov 4, 2009
1,352
525
tucson
Google Pixel 3
I just took the official android 12 update yesterday... phone was working fine.. went to sleep, woke up, and now am getting the same issue as everyone else..

that's very unfortunate. Just to clarify, you say you 'just took' the official update? That means u got the OTA correct?

It seems, not exactly certain by any means, that it's the OTA process that is somehow causing this issue. And it doesn't seem to happen immediately, like a day or so later.

Not that that info helps you now. Personally, I'd look into making complaints with Google. It's totally not fair that some of these devices are becoming completely worthless much earlier than they should be.

cheers
 

nullx

Member
Sep 7, 2010
20
4
that's very unfortunate. Just to clarify, you say you 'just took' the official update? That means u got the OTA correct?

It seems, not exactly certain by any means, that it's the OTA process that is somehow causing this issue. And it doesn't seem to happen immediately, like a day or so later.

Not that that info helps you now. Personally, I'd look into making complaints with Google. It's totally not fair that some of these devices are becoming completely worthless much earlier than they should be.

cheers
Yes the official OTA update to android 12. Really unfortunate and quite strange timing considering I pre-ordered the 6 pro just the other day... too bad this couldnt have happened AFTER I received the 6 pro...

But yea, I posted over in the main thread: https://support.google.com/pixelpho...lk-cid-likely-caused-by-security-update?hl=en

verrry annoying the phone was working perfectly and now it's just a brick..
 

ShadowVlican

Senior Member
Feb 27, 2007
573
94
Toronto
I also got the official OTA update to Android 12, and now a couple days later my Pixel 3XL has bricked itself. I'm sure this is not caused by Android 12 but just down to random dumb luck and coincidence. The phone died while I wasn't using it; I came back to it and found it dead.

The phone is dead. It's completely unresponsive, doesn't respond to the power button or volume button combinations to get into recovery mode, fastboot mode, etc NOTHING. I'm seeing the same QUSB_BULK_CID:0402_SN:XXXXXXXX in my device manager when I'm connected to my windows PC.

I finally got through to Google Support and they eventually said there's nothing that could be done. The phone is long out of warranty and not worth fixing. I've already pre-ordered the Pixel 6 Pro, hoping to use my Pixel 3XL for trade-in credit, but I guess I won't qualify for any credit anymore.
 

xtafan1

Member
Oct 27, 2021
5
1
If your phone is still working, is there anything you can do to retain access in case it enters EDL mode later? While not exact, I am thinking something analogous to the SHSH blobs of iphones.

If not for the pixel 3, has something been done on a similar phones that could be ported over with some effort such as light reverse engineering or a known security flaw?
 

AsItLies

Senior Member
Nov 4, 2009
1,352
525
tucson
Google Pixel 3
If your phone is still working, is there anything you can do to retain access in case it enters EDL mode later? While not exact, I am thinking something analogous to the SHSH blobs of iphones.

If not for the pixel 3, has something been done on a similar phones that could be ported over with some effort such as light reverse engineering or a known security flaw?
No, don't believe there is. EDL mode needs the 'firehose' file to access the device, but google won't release it.

It is actually fairly easy to access the device, with the firehose. I've used both qualcomms qfil app and the bkerler edl python utilities to access LG phones, but the firehose file is available for them, not the pixel 3.
 

FuPete

Senior Member
Sep 21, 2012
73
21
Ulm
Just replaced the mainboard of my girlfriends Pixel 3 because of the QUSB Brick. Her phone just turned off while listening to music. She was on Android 11, so in this case the Android 12 Update had nothing to do with this brick. Happened 3 days ago. Phone was bought on release.
I started with the Nexus 4, but this was our last Google Phone.
 

AsItLies

Senior Member
Nov 4, 2009
1,352
525
tucson
Google Pixel 3
Just replaced the mainboard of my girlfriends Pixel 3 because of the QUSB Brick. Her phone just turned off while listening to music. She was on Android 11, so in this case the Android 12 Update had nothing to do with this brick. Happened 3 days ago. Phone was bought on release.
I started with the Nexus 4, but this was our last Google Phone.

sorry to hear, and I don't blame you re 'last google phone'. Just to clarify; did replacing the mainboard fix the issue?

Also, to clarify, the suspicion we have, of why this is happening, isn't because of updating to android 12, it's because of doing an OTA (to 12, 11, security patch, etc).

And again, it's only a suspicion, derived at because so many have reported they experienced this 'edl brick' soon after having done an OTA update (not a specific one, just OTA update).

What we know for sure is that the abl partition can't be read, it's corrupted, the hardware has gone bad, etc etc (we don't know). When something like that happens, the device will go into edl mode automatically.

Also, if one looks in the 4a forums, they too have been experiencing the same thing. It's crazy really, to think google hasn't addressed this. What a thing to have to live with, that your phone may one day simply be unusable, not because the battery wore down, not because of some change you made, etc etc, But because the device just simply bricked itself.

cheers
 

FuPete

Senior Member
Sep 21, 2012
73
21
Ulm
sorry to hear, and I don't blame you re 'last google phone'.

Well, maybe it's just my current anger, never had a electronic device fail so fast without a reason. My approximately 15 year old PSP is still running, my Nexus 4 was running for 5+ years, my Nexus 6 was running for 5+ years, her 6P was running for 5+ Years and the Pixel 3... Well.

Just to clarify; did replacing the mainboard fix the issue?

Yes, the bricked Pixel 3 is now running fine with the replaced mainboard. I bought a Pixel 3 with cracked screen and backcover for 30€ and disassembled the mainboard. Additionally I have now a original spare battery, if the battery degrades in the future.

Also, to clarify, the suspicion we have, of why this is happening, isn't because of updating to android 12, it's because of doing an OTA (to 12, 11, security patch, etc).

Hmmmm. Can't say if she did a OTA recently.
 
  • Like
Reactions: AsItLies

timg11

Senior Member
Jul 20, 2010
188
20
Google Pixel 3 XL
I have a Pixel 3XL. It is still working fortunately, and I guess I'll have to deny further OTAs from what I read. I'm thinking about what my next phone will be. I've owned and liked Pixel phones, and the Pixel 6 looks appealing. I would buy it in the next few months under normal circumstances. But until Google comes clean on this EDL bricking issue (explains the root cause, confirms it has been fixed, and provides a fair remedy for customers affected) I'm done. The fact that this issue has been ignored for 6 months leaves me feeling very negative towards Google and their phones -- they will have to do something significantly positive to win back their customer trust.
 
  • Like
Reactions: AsItLies

SSamDav

New member
Nov 1, 2021
1
0
Hi all,

I have a Pixel 3XL and until today morning it was working fine with the android 12, however, when I wake up it is bricked 😥 I tried all the possible combination of power + volume buttons but the phone doesn't respond, however, when I do that with the phone connected to my laptop, windows recognizes that I'm plugging and unplugging a new device (I say this because it does the sound of connecting a new device). Moreover, when I go to device manager I think my phone appears with the name QUSB_BULK_CID. I just read this thread and it seems that the solution wasn't found I will try to drain the battery on my and charge it to see if I can restart again.
 

AsItLies

Senior Member
Nov 4, 2009
1,352
525
tucson
Google Pixel 3
Hi all,

I have a Pixel 3XL and until today morning it was working fine with the android 12, however, when I wake up it is bricked 😥 I tried all the possible combination of power + volume buttons but the phone doesn't respond, however, when I do that with the phone connected to my laptop, windows recognizes that I'm plugging and unplugging a new device (I say this because it does the sound of connecting a new device). Moreover, when I go to device manager I think my phone appears with the name QUSB_BULK_CID. I just read this thread and it seems that the solution wasn't found I will try to drain the battery on my and charge it to see if I can restart again.

Very unfortunate. Be sure to let google know that this happened. We don't know that they'll ever do anything about it, but it's clearly not something that should be considered 'reasonable', these devices are not that old.

cheers
 

mcwups1

Senior Member
May 4, 2011
2,461
479
Google Pixel 6 Pro
I also got the official OTA update to Android 12, and now a couple days later my Pixel 3XL has bricked itself. I'm sure this is not caused by Android 12 but just down to random dumb luck and coincidence. The phone died while I wasn't using it; I came back to it and found it dead.

The phone is dead. It's completely unresponsive, doesn't respond to the power button or volume button combinations to get into recovery mode, fastboot mode, etc NOTHING. I'm seeing the same QUSB_BULK_CID:0402_SN:XXXXXXXX in my device manager when I'm connected to my windows PC.

I finally got through to Google Support and they eventually said there's nothing that could be done. The phone is long out of warranty and not worth fixing. I've already pre-ordered the Pixel 6 Pro, hoping to use my Pixel 3XL for trade-in credit, but I guess I won't qualify for any credit anymore.
Mine just died tonight.

I've been shrugging off the update, swiping it away. I was literally on my phone when the screen went dark, and now is dead, bricked.

I can plug it in to a PC, it identifies something there, but no Fastboot commands, or Device attached. I get this in my Device Manager "
QUSB_BULK_CID:0402_SN:xxxxxxxx".

Is there a file you can get from QCOM to get this fixed?
 

ShadowVlican

Senior Member
Feb 27, 2007
573
94
Toronto
Mine just died tonight.

I've been shrugging off the update, swiping it away. I was literally on my phone when the screen went dark, and now is dead, bricked.

I can plug it in to a PC, it identifies something there, but no Fastboot commands, or Device attached. I get this in my Device Manager "
QUSB_BULK_CID:0402_SN:xxxxxxxx".

Is there a file you can get from QCOM to get this fixed?
afaik, there hasn't been any fixes for this... contact google and hope they replace it, otherwise we're all SOL
 
  • Like
Reactions: mcwups1

mcwups1

Senior Member
May 4, 2011
2,461
479
Google Pixel 6 Pro
afaik, there hasn't been any fixes for this... contact google and hope they replace it, otherwise we're all SOL
Spent from 10pm to 12:50 am waiting in chat for Google assistance. They are no help, of course. My phone is immaculate. Charging port is great, screen protector and case have it looking like I just pulled it out of the box from years ago.

I can't believe the thing just died in front of my face. Completely dead, and the USB on my PC doesn't recognize it. I can hear it turning off and on though, if I hold the power button. It just doesn't boot up, or show anything in my ADB Devices search. It's just crazy.

I was going to have to get a new phone anyway, because I was on Sprint service, and with TMobile taking it over, this phone couldn't be used on their towers, or so they told me.

I have to upgrade to another phone with 5G. Me and my oldest daughter. Fun.
 

ShadowVlican

Senior Member
Feb 27, 2007
573
94
Toronto
Spent from 10pm to 12:50 am waiting in chat for Google assistance. They are no help, of course. My phone is immaculate. Charging port is great, screen protector and case have it looking like I just pulled it out of the box from years ago.

I can't believe the thing just died in front of my face. Completely dead, and the USB on my PC doesn't recognize it. I can hear it turning off and on though, if I hold the power button. It just doesn't boot up, or show anything in my ADB Devices search. It's just crazy.

I was going to have to get a new phone anyway, because I was on Sprint service, and with TMobile taking it over, this phone couldn't be used on their towers, or so they told me.

I have to upgrade to another phone with 5G. Me and my oldest daughter. Fun.
I feel your pain... I also had to wait quite a long time until I got through to Google Support and in the end they were not helpful. My Pixel 3XL was bought almost 3 years ago at launch, so it was a long shot getting Google to cover this defect under warranty. The media ought to put more pressure on this planned obsolescence and unnecessary e-waste.

Even though I've got the Pixel 6 Pro on order, I could've given this phone to my parents or kept it as backup. Now it's just a useless paper weight not worth repairing.
 
  • Like
Reactions: mcwups1

AsItLies

Senior Member
Nov 4, 2009
1,352
525
tucson
Google Pixel 3
Spent from 10pm to 12:50 am waiting in chat for Google assistance. They are no help, of course. My phone is immaculate. Charging port is great, screen protector and case have it looking like I just pulled it out of the box from years ago.

I can't believe the thing just died in front of my face. Completely dead, and the USB on my PC doesn't recognize it. I can hear it turning off and on though, if I hold the power button. It just doesn't boot up, or show anything in my ADB Devices search. It's just crazy.

I was going to have to get a new phone anyway, because I was on Sprint service, and with TMobile taking it over, this phone couldn't be used on their towers, or so they told me.

I have to upgrade to another phone with 5G. Me and my oldest daughter. Fun.

Sorry to hear. Just as an fyi though, pretty sure it could have easily been used on t-mo towers by just flashing the generic firmware rom google makes readily available.

It's the rom that controls which towers the phone will have availability for, and the generic / open rom has all the major bands (including 71) that t-mo uses.

cheers, be sure to let google know this happened, it really should not be happening for sure.
 
  • Like
Reactions: mcwups1

mcwups1

Senior Member
May 4, 2011
2,461
479
Google Pixel 6 Pro
I feel your pain... I also had to wait quite a long time until I got through to Google Support and in the end they were not helpful. My Pixel 3XL was bought almost 3 years ago at launch, so it was a long shot getting Google to cover this defect under warranty. The media ought to put more pressure on this planned obsolescence and unnecessary e-waste.

Even though I've got the Pixel 6 Pro on order, I could've given this phone to my parents or kept it as backup. Now it's just a useless paper weight not worth repairing.
They really should! This should be an "Apple slows down phone near new phone launch" type of headline. Should be made more public and there should be something done about it. My phone is immaculate, but all the sudden, when I get a notification to update, it craps out?

Really needs more attention.
 

mcwups1

Senior Member
May 4, 2011
2,461
479
Google Pixel 6 Pro
Sorry to hear. Just as an fyi though, pretty sure it could have easily been used on t-mo towers by just flashing the generic firmware rom google makes readily available.

It's the rom that controls which towers the phone will have availability for, and the generic / open rom has all the major bands (including 71) that t-mo uses.

cheers, be sure to let google know this happened, it really should not be happening for sure.
That's interesting. I remember flashing radio's a long time ago with HTC phones, and didn't really think about it. I surely would have got a new phone without remembering this.
 
  • Like
Reactions: AsItLies

sj3vans

New member
Nov 9, 2021
2
0
Happen to me tonight. 3XL. Same as everyone. I've loved this phone! Told many people about how well it has worked for me. :( Boooooo!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Mine just died tonight.

    I've been shrugging off the update, swiping it away. I was literally on my phone when the screen went dark, and now is dead, bricked.

    I can plug it in to a PC, it identifies something there, but no Fastboot commands, or Device attached. I get this in my Device Manager "
    QUSB_BULK_CID:0402_SN:xxxxxxxx".

    Is there a file you can get from QCOM to get this fixed?
    afaik, there hasn't been any fixes for this... contact google and hope they replace it, otherwise we're all SOL
    1
    Spent from 10pm to 12:50 am waiting in chat for Google assistance. They are no help, of course. My phone is immaculate. Charging port is great, screen protector and case have it looking like I just pulled it out of the box from years ago.

    I can't believe the thing just died in front of my face. Completely dead, and the USB on my PC doesn't recognize it. I can hear it turning off and on though, if I hold the power button. It just doesn't boot up, or show anything in my ADB Devices search. It's just crazy.

    I was going to have to get a new phone anyway, because I was on Sprint service, and with TMobile taking it over, this phone couldn't be used on their towers, or so they told me.

    I have to upgrade to another phone with 5G. Me and my oldest daughter. Fun.
    I feel your pain... I also had to wait quite a long time until I got through to Google Support and in the end they were not helpful. My Pixel 3XL was bought almost 3 years ago at launch, so it was a long shot getting Google to cover this defect under warranty. The media ought to put more pressure on this planned obsolescence and unnecessary e-waste.

    Even though I've got the Pixel 6 Pro on order, I could've given this phone to my parents or kept it as backup. Now it's just a useless paper weight not worth repairing.
    1
    Spent from 10pm to 12:50 am waiting in chat for Google assistance. They are no help, of course. My phone is immaculate. Charging port is great, screen protector and case have it looking like I just pulled it out of the box from years ago.

    I can't believe the thing just died in front of my face. Completely dead, and the USB on my PC doesn't recognize it. I can hear it turning off and on though, if I hold the power button. It just doesn't boot up, or show anything in my ADB Devices search. It's just crazy.

    I was going to have to get a new phone anyway, because I was on Sprint service, and with TMobile taking it over, this phone couldn't be used on their towers, or so they told me.

    I have to upgrade to another phone with 5G. Me and my oldest daughter. Fun.

    Sorry to hear. Just as an fyi though, pretty sure it could have easily been used on t-mo towers by just flashing the generic firmware rom google makes readily available.

    It's the rom that controls which towers the phone will have availability for, and the generic / open rom has all the major bands (including 71) that t-mo uses.

    cheers, be sure to let google know this happened, it really should not be happening for sure.
    1
    Sorry to hear. Just as an fyi though, pretty sure it could have easily been used on t-mo towers by just flashing the generic firmware rom google makes readily available.

    It's the rom that controls which towers the phone will have availability for, and the generic / open rom has all the major bands (including 71) that t-mo uses.

    cheers, be sure to let google know this happened, it really should not be happening for sure.
    That's interesting. I remember flashing radio's a long time ago with HTC phones, and didn't really think about it. I surely would have got a new phone without remembering this.
    1
    Just out of curiosity, is it possible for developers to dig thru the Pixel source code to see if Google is planting some sort of malicious code to brick Pixel phones? This is happening to far too many owners and Google isn't even addressing this issue.

    Maybe I'm just being paranoid but I feel safer using custom ROM's knowing I'm not using Google's bugged firmware.

    I doubt google would put anything in the source, even if they wanted to do as u imagine. If it were true (which I don't believe), they'd use the OTA to do something it shouldn't, rather than have it be found in source.

    I'd bet it's something in the ota process, that is inadvertently doing something like overwriting the gpt table, or corrupting some other part of the boot process.

    Just as an fyi, I don't do ota's. I download the zip and flash it with the flashall.sh script. I won't do an ota. Maybe it's crazy, but it's out of an abundance of caution.

    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
    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...
    1
    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
    1
    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 ¯\_(ツ)_/¯
    1
    OK, this is really getting weird. My wife's phone just did the exact same thing. I've never seen anything like this so I thought it was an oddball thing, but this thread tells me otherwise. I wonder if the Pixel 3 is just a ticking time bomb or if we all did something to brick them. I know in my case, I just recently (2 weeks ago) replaced her charger with an Anker charger from Amazon. Figured maybe that could be part of the reason. Anyone else have any suspicions as to what might have caused the issue? I'm going to work on trying to bring it back to life or at the very least recover as much information from the device as possible, so if anyone's already working on that, please share with the group!