Google Pixel 6 Pro hard bricked after Android 17 and June Google Play Services update
Hey everyone, I’m posting this on behalf of my friend who just lost his Pixel 6 Pro to the recent brick wave (and obviously has no phone to access his accounts right now). We’re trying to figure out if this is a widespread software issue or a sudden hardware death. Here is exactly what happened to his device: His phone successfully updated to Android 17 recently, and everything was working completely fine for a while. Then, he installed the June 2026 Google Play Services/system update. Shortly after that, the phone just died completely. Now it's a total "black brick." Current state: Absolutely zero signs of life. What we've tried: We cannot boot it into Fastboot mode at all. Holding down the Power + Volume Down combinations does absolutely nothing. PC connection: When plugged into a computer, it’s not recognized at all — no sound, no device detected in Device Manager, nothing. Charging: He left it on a verified working charger for hours, but it remains completely dead and cold. Honestly, what is even going on with these Google Play system updates lately? Why do you guys keep pushing these mandatory updates if you clearly don't test them properly on older devices? The Pixel 6 series is already considered old, and if your dev team can't ensure stability for older hardware, maybe you should just stop releasing updates for them entirely instead of sending out patches that literally fry the bootloader and kill the phone. Could an official Google update really trigger a sudden motherboard/CPU failure (like a hard brick due to a corrupted bootloader), or did his motherboard just coincidentally die right after the update? Has anyone else experienced this specific behavior after the June updates on Android 17? Any advice on what to do next when the physical buttons and PC connection are totally unresponsive? Thanks for any help!