1. briischamp's Avatar
    Before I went to bed Sunday, my Pixel 3 XL was functioning perfectly fine. Rested it on my Pixel Stand for the night and woke up the next morning to a bricked phone.

    I did see it mentioned on some other sites, but not in these forums, that Pixel 3's have been bricked and the culprit was possibly wireless chargers. Some blamed it on trying to use third party chargers (Samsung and others), but others like me had used the Pixel Stand.

    Trouble shot it with Google, cleared the charging port, tried a wired charger, tried hard reset, etc., no luck. Verizon sent replacement via overnight due to manufacturer defect. Wondering if anybody has confirmed the Pixel Stand was to blame? I'm nervous about using it with my replacement device now.
    02-28-2019 12:29 PM
  2. HyperM3's Avatar
    Ive been using the pixel stand since day one, every night, and I have no issues to report.
    Coop61 and briischamp like this.
    02-28-2019 01:04 PM
  3. GSDer's Avatar
    I'm nervous about using it with my replacement device now.
    As long as they're going to replace it with a new device under warranty you may as well keep at it - someone has to test these things!

    On a serious note, I haven't seen that mentioned in the forums here or in places like XDA, but I'll see if Reddit has anything, or perhaps the Google user forums.
    briischamp likes this.
    02-28-2019 01:51 PM
  4. Rukbat's Avatar
    Funny thing I learned when my Pixel 2 "bricked". If you look at Deuces Bootloop-Recovery & Flashing Script you might get an idea of how to "unbrick" a Pixel (if the Verizon bootloader can be unlocked on the 3 - you should always keep it unlocked, just for situations like this).
    mustang7757 and briischamp like this.
    02-28-2019 04:45 PM
  5. mustang7757's Avatar
    Funny thing I learned when my Pixel 2 "bricked". If you look at Deuces Bootloop-Recovery & Flashing Script you might get an idea of how to "unbrick" a Pixel (if the Verizon bootloader can be unlocked on the 3 - you should always keep it unlocked, just for situations like this).
    True ..
    briischamp likes this.
    02-28-2019 05:11 PM
  6. Mike Dee's Avatar
    Before I went to bed Sunday, my Pixel 3 XL was functioning perfectly fine. Rested it on my Pixel Stand for the night and woke up the next morning to a bricked phone.

    I did see it mentioned on some other sites, but not in these forums, that Pixel 3's have been bricked and the culprit was possibly wireless chargers. Some blamed it on trying to use third party chargers (Samsung and others), but others like me had used the Pixel Stand.

    Trouble shot it with Google, cleared the charging port, tried a wired charger, tried hard reset, etc., no luck. Verizon sent replacement via overnight due to manufacturer defect. Wondering if anybody has confirmed the Pixel Stand was to blame? I'm nervous about using it with my replacement device now.
    It really could anything. This is the first brick I've heard of actually. I can't think of anything that technical that would cause a stand to brick a phone even though there is other connectivity going on with Pixel. Of course anything is possible.
    briischamp likes this.
    02-28-2019 08:55 PM
  7. briischamp's Avatar
    Thanks for feedback all. Since it doesn't seem to be very widespread, I'm going to chalk it up to random device defect. I'll throw it on the same Stand tonight and that's our constant. If this replacement turns to a paperweight we'll know why. : )

    EDIT: here's where I saw others possibly having the same issue, just haven't run across anything definitive: https://www.google.com/amp/s/amp.red...l_3xl_bricked/
    02-28-2019 09:19 PM
  8. Mike Dee's Avatar
    Thanks for feedback all. Since it doesn't seem to be very widespread, I'm going to chalk it up to random device defect. I'll throw it on the same Stand tonight and that's our constant. If this replacement turns to a paperweight we'll know why. : )

    EDIT: here's where I saw others possibly having the same issue, just haven't run across anything definitive: https://www.google.com/amp/s/amp.red...l_3xl_bricked/
    Based on those posts the common denominator seems to be wireless charging not specific to Google. Could still be a coincidence because a lot of Pixel users use wireless charging. If we could find Pixels that are bricking while not using wireless charging then we could almost rule it out the wireless connection. Myself and lots of others who pre-ordered are not experiencing this issue...I hope it isn't widespread. How long have you owned it?
    02-28-2019 10:23 PM
  9. mustang7757's Avatar
    another thing to know if it was soft bricked all you need to do is boot up in recovery clear cache and reboot, now if it was hard bricked you need to sideload the OS again to put back partitions files . just heads up
    02-28-2019 10:48 PM
  10. briischamp's Avatar
    Based on those posts the common denominator seems to be wireless charging not specific to Google. Could still be a coincidence because a lot of Pixel users use wireless charging. If we could find Pixels that are bricking while not using wireless charging then we could almost rule it out the wireless connection. Myself and lots of others who pre-ordered are not experiencing this issue...I hope it isn't widespread. How long have you owned it?
    I did not pre-order, but purchased maybe 3 weeks - 1 month after release.
    03-01-2019 03:09 PM
  11. GSDer's Avatar
    another thing to know if it was soft bricked all you need to do is boot up in recovery clear cache and reboot
    Please stop perpetuating this myth - there is no cache to clear on devices with the A/B partition scheme!
    03-01-2019 07:36 PM
  12. mustang7757's Avatar
    Please stop perpetuating this myth - there is no cache to clear on devices with the A/B partition scheme!
    Yeah forgot about pie you cant do this anymore, it's not a MYTH I've done it before on soft brick phone before they stopped the clearing cache.
    Thanks for reminding
    03-01-2019 07:47 PM
  13. GSDer's Avatar
    Yeah forgot about pie you cant do this anymore
    This actually goes all the way back to Android 7 (Nougat); Google devices like the original Pixel which shipped with Nougat supported seamless updates; it was optional so other manufacturers often didn't bother.
    And Google devices that upgraded from an earlier OS, like the Nexus 6P, were out of luck - they use the older partition scheme which still has a system cache partition.
    03-02-2019 02:22 AM
  14. mustang7757's Avatar
    This actually goes all the way back to Android 7 (Nougat); Google devices like the original Pixel which shipped with Nougat supported seamless updates; it was optional so other manufacturers often didn't bother.
    And Google devices that upgraded from an earlier OS, like the Nexus 6P, were out of luck - they use the older partition scheme which still has a system cache partition.
    I think we getting off the topic here a little.
    I'm talking about clearing cache in recovery and your talking about seamless updates which is for software updates and cant help anyone when phone gets bricked.
    Since we can't clear cache in recovery anymore only option would be factory reset to see if you can fix the soft brick otherwise would have to reload OS if it's hard bricked.
    03-02-2019 08:15 AM
  15. Lilybell2's Avatar
    Just to clarify, it's not that "we can't clear cache in recovery anymore," it's that Pixel phones do not have and have never had a cache partition, ergo, you cannot clear/wipe something that does not exist. The same would be true of any Android phone using the A/B system.
    03-02-2019 05:42 PM
  16. mustang7757's Avatar
    03-02-2019 05:57 PM
  17. Lilybell2's Avatar
    https://source.android.com/devices/t...ent#partitions

    A/B devices do not need a recovery partition or cache partition because Android no longer uses these partitions. The data partition is now used for the downloaded OTA package, and the recovery image code is on the boot partition. All partitions that are A/B-ed should be named as follows (slots are always named a, b, etc.): boot_a, boot_b, system_a, system_b, vendor_a, vendor_b.
    03-02-2019 07:19 PM
  18. mustang7757's Avatar
    Just to clarify, it's not that "we can't clear cache in recovery anymore," it's that Pixel phones do not have and have never had a cache partition, ergo, you cannot clear/wipe something that does not exist. The same would be true of any Android phone using the A/B system.
    I stand corrected if this is true , might be thinking about my other andriod phones
    Javier P likes this.
    03-02-2019 07:24 PM
  19. Golfdriver97's Avatar
    I'm tempted to say they didn't. I don't recall seeing it in the Pixel 1 when I first got it.
    Saying that pixel phones never had clear cache systems in recovery is false .
    03-02-2019 07:45 PM
  20. mustang7757's Avatar
    I'm tempted to say they didn't. I don't recall seeing it in the Pixel 1 when I first got it.
    You dont recall?
    If I'm wrong I stand corrected as i could be mixing this up with my other andriod devices
    03-02-2019 08:37 PM
  21. Golfdriver97's Avatar
    You dont recall?
    If I'm wrong I stand corrected as i could be mixing this up with my other andriod devices
    If I had to give an answer, I'd say they didn't. I remember looking for the cache partition after I got the pixel, but it was a few months after I got it.

    I can go as far as flashing the first ROM when I get some time, to check.
    03-02-2019 08:41 PM
  22. mustang7757's Avatar
    If I had to give an answer, I'd say they didn't. I remember looking for the cache partition after I got the pixel, but it was a few months after I got it.

    I can go as far as flashing the first ROM when I get some time, to check.
    Ok cool .. be interesting if you can
    03-02-2019 08:44 PM
  23. Mike Dee's Avatar
    If I had to give an answer, I'd say they didn't. I remember looking for the cache partition after I got the pixel, but it was a few months after I got it.

    I can go as far as flashing the first ROM when I get some time, to check.
    I believe the system change happened with 7.1
    03-03-2019 07:58 AM

Similar Threads

  1. How To Configure Mobile Hotspot Settings?
    By zanshin777 in forum Android 6.0 Marshmallow
    Replies: 6
    Last Post: 04-10-2019, 11:34 PM
  2. I continue to receive Google account alerts on removed devices. How do I stop it?
    By sdfg54wregasdf4u in forum General Help and How To
    Replies: 2
    Last Post: 03-06-2019, 09:36 AM
  3. Will Pixel Filters increase display lifetime?
    By Android Central Question in forum Ask a Question
    Replies: 1
    Last Post: 02-28-2019, 05:02 PM
  4. Enable apps to disable notifications
    By MarineDawg in forum Samsung Galaxy S8 & S8+
    Replies: 1
    Last Post: 02-28-2019, 11:43 AM
  5. Samsung Galaxy Tab S4 won't respond to OK Google
    By Crossesfour in forum Ask a Question
    Replies: 1
    Last Post: 02-28-2019, 10:57 AM
LINK TO POST COPIED TO CLIPBOARD