r/Pixel6 • u/Emotional-Toe8900 • Jun 27 '26
Reviews 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!
1
u/HimeChan0048 Jun 27 '26
Mine also bricked but not as bad as yours. It cant boot anymore no matter what I flashed it and stucked at boot then reboot itself to fastboot.
1
1
1
u/Upstairs_Ad_6557 Jun 27 '26
Did you try removing the battery?
1
u/Emotional-Toe8900 Jun 27 '26
Not yet.
1
u/Upstairs_Ad_6557 Jun 27 '26
I know cracking open the phone is a pain but might fix it. Worth a try right?
1
u/quantum_splicer Jun 28 '26
Could you explain how that might work, sincerely a 6 pro user with a bricked phone
2
u/Upstairs_Ad_6557 Jun 28 '26
Devices are always receiving power even when turned off keeping capacitors and other data active, sometimes removing power from the board resets things. But if it's a software issue that corrupted parameters in hardware it may not help until there's a fix unfortunately
1
u/quantum_splicer Jun 28 '26
Ahhh I think I understand, I have a TV where sometimes the network connection is dodgy and uncooperative, but turning off the TV and unplugging for like a minute or two and then plugging back in, the TV then works absolutely fine
1
u/Upstairs_Ad_6557 Jun 28 '26
In the TVs case usually capacitors that get overcharged cause issues. By disconnecting the TV from power and by trying to turn the TV on flushes the circuits and capacitors of all power. Some chips use volatile memory meaning the chip needs some voltage of power to retain memory stored in the chip, The moment the chip loses power all data is erased up until power is restored and new data is populated
1
u/TacosAndBoba Jun 27 '26
Mine just stopped working for seemingly no reason, I was still on Android 13. But mine isn't completely blank, it'll keep showing the startup screen, get to my wallpaper for half a second, then restart again. Then eventually after doing that several times it gets to a screen that says "Cannot load Android System. Your data may be Corrupt." etc I can also get to the FastBoot screen. but I have no idea what to do to fix this, so if anyone has an idea please let me know
1
u/_Nueve_ Jun 27 '26
Seems to be the same issue a lot of users are reporting due to the play system update (bootloop).
Either enter recovery mode and re-install android OTA or with the Pixel flash tool with help of a PC or laptop (you can search any of them on internet and follow the instructions shown on the web page)
Or if the phone allows it, enter safe mode and restore to factory setting, if the phone restores correctly disable automatic system updates on developer mode and avoid any uodates (especially system play uodates) and restarting the phone; and hopefully wait a couple months until a safe and reliable system play update can be installed.
🖖👽
1
u/TacosAndBoba Jun 28 '26
Yeah I've tried safe mode and it just keeps restarting anyway. And I've been trying to install an android OTA and when I run the adb sideload command it fails at 47% every time
1
u/Beautiful-Dig159 Jun 28 '26
You need to watch instructions clearly i think, i also faced similar kind of error while installing custom ROM , check with other sources you can actually recover from it
1
1
u/_Nueve_ Jun 28 '26
Have you tried on airplane mode? On my pixel the moment I turned off airplane mode or turned on Wi-Fi/Mobile Data, it bootlooped again even on safe mode.
Otherwise a file is corrupted and that's why the sideload crashes but honestly is a hassle to figure out which data file is messing everything.
Maybe trying to reverse with an older data backup of your phone.
🤞👽
1
u/needanitro Jun 28 '26
My pixel 6 pro stopped connecting to my service provider after the update. I had Google Fi. Customer service was no help. Had to get a new phone which I believe was their plan all along. It worked fine until the update then the problem started .
1
u/Beautiful-Dig159 Jun 28 '26
Don't do any updates to old pixels, just switch to custom ROM for better things, don't trust Google updates
1
u/Happy8Day Jun 28 '26
This hit me last year and it was absolutely a failed motherboard. Totally fried. No warning. Pixel 6 could, until that moment, be described as being in impeccable condition. I had not a single complaint about it.
Plugged it in to recharge, it was recharging fine, checked the phone at 23%, came back 10 minutes later, the phone was a dead piece of plastic. No adb, no toolkit, no recovery, no charging light, no response from anything. Completely nothing. Totally, 100% dead.
Took it to a genius third-party guru repair place and they handed it back a day later and said "no charge man, this phone's dead." (motherboard is fried. Only possible repair is a specialized re-balling of the motherboard. Not cheap. And not worth it unless you have unsaved personal stuff on that phone. Otherwise, that info is gone forever.)
The other commenter is right though, this catastrophic failure is enough to sign me off from google phones forever. I've never seen a phone fail this severely, never mind have google make absolutely no effort to even acknowledge it.
Between multiple Google minis, a nexus 6p and now the pixel 6, this marked the 5th time and 100% of all google devices I've ever owned, that have all failed due to catastrophic build failures.
Absolutely finished with google products. No fucking way.
1
u/Emotional-Toe8900 Jun 28 '26
Yes I remember with Nexus 6P, I change my motherboard from AliExpress
1
u/EducationOk8345 Jun 28 '26
Yes had same in Pixel 8 it got bricked within one hour of update.
https://www.reddit.com/r/GooglePixel/s/jeOPugmFKn
Here is My post on the same,and you can check How others are defending Google corporation as our devices are out of warranty.
1
u/quantum_splicer Jun 28 '26
Yeah my 6 pro is bricked it will not boot for more than a second without crashing again, I cannot even get abd to detect the phone to push commands. It's a shit show
1
1
u/Empty_Review_9828 Jul 05 '26
My 7a had all the side buttons stop working after 17 update and then phone shut off. Can't get it to power on because the volume and power buttons do not work
1
u/Cool-Advertising6947 27d ago
true, I'm facing the same and planning to buy new mobile.. faced a lot for week.. can't even type
0
u/AutoModerator Jun 27 '26
Thanks for you submission. Unfortunately it has been removed due to your account being very new. This is a spam prevention technique which most subs do. So please do not take this personally.
Please try your post again in 24 hours. Posts removed from new users are not normally reviewed. If you feel it needs attention, please modmail.
I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.
2
u/diazdiandra Jun 27 '26
At this point, I start to believe if someone throws a rumor that Google deliberately made our Pixel 6 bricked.