- The Android 15 update for Pixel devices is causing unexpected bricking of Pixel 6 devices.
- Users report their Pixel 6 becoming completely unresponsive, with troubleshooting methods yielding no results.
- The issue might be related to the Private Space on Android 15, but further investigation is needed.
I thought this sounded familiar and sure enough, second paragraph:
The Pixel 6 series has a history of running into issues after Android updates. Last year, the Android 14 update locked some users out of their storage, and earlier this year, factory resets left many Pixel 6 devices unresponsive.
Disappointing, you’d think this wouldn’t happen with Google controlling both hardware and software
you’d think this wouldn’t happen with Google controlling both hardware and software
i only expect more problems with more google control instead of less.
Disappointing, you’d think this wouldn’t happen with Google controlling both hardware and software
Perhaps, the testing folks thought the same thing as you, and skipped testing a thing or four. 🤣/s
Anyway, the 1st gen pixel users suffered the most. The latest gen pixel 8 series (and perhaps pixel 9) are not critically hit and have less heating problems. It sucks being early adopter for beta hardware and software. Google should compensate the affected users with upgrade to pixel 7/8 or even 9 series if possible.
I’m curious, what’s the recourse here when this happens? Does Google make it right somehow when their own software bricks their own devices?
Or is just “Oops, our bad. Just buy a new one, best of luck!!”?
Does reflashing a ROM fix it? (aside from some data loss, of course)
Don’t know about the rest, but…
Does reflashing a ROM fix it?
The phones appear to be simply dead with no response to anything. No way to connect ADB, no way to connect fastboot, nothing.
Also the bootloader allows flashing over the cable only when it’s unlocked (at least on Pixels; I couldn’t find anything relevant in the Android documentation). The vast majority of Pixels should have their bootloaders locked, and it is only possible to unlock it through the system settings, so it’s pretty safe to say that most Pixels cannot be recovered if Android fails to boot because you cannot unlock the bootloader if you can’t get into settings.
Just updated this morning, shit. Working okay so far, though.
Absolutely no issues with the GrapheneOS Android 15 releases
How does this even happen?
Lack of QA.
“Customers do the QA for us now.”
That’s been Microsoft’s slogan for decades
Note Google fired more than 12,000 people in the last two years.
Is that why we haven’t gotten any new messaging apps lately?
We have Meet, Voice, and Messages.
Welcome to Google Messages Meet Voice. All the messaging apps combined in to one!
So, basically what hangouts was before it became allo and duo then messages?
They want you to buy a new phone. My 5a screen died just after 2 years. They had extended the warranty by a year because of screens going bad. If I would have known that I would have tried to get it replaced before the two years was up.
Too late for me. It’s been fine so far, but I’m also not really using anything new.
That’s why I thought ahead and stayed with the Pixel 5A, so that I would not get Android 15.
/s
Doh!
My Pixel 6 survived the update! \o/
Removed by mod
Upgraded to Android 15 with no issues on my 6a, but stuff like this is concerning.
I wonder if the is just happening on the 6 or the 6xl is also affected. Either way I’ll not be exploring the private spaces for a while.
Hope my pixel 7 doesn’t get effed.
I’m running Android 14 on a Pixel 5, no updates available for it but seems to be running fine.
Removed by mod
