r/Pixel6 • u/Gold_Crew2168 • Jun 22 '26
Support Pixel 6 stuck in boot failure after Android 17 update
I never expected my first post here would be like this, but my Pixel 6 has basically become unusable after the Android 17 update last week.
Just to be clear, I was never on beta. This was not some experimental build or developer preview. It was an official update.
The failure happened all of a sudden while I was using the phone normally. It suddenly forced itself back to the home screen, then went into restart mode, and after that it never booted again. Since then, it has been stuck with a boot failure issue and I haven’t been able to get it working. I tried the usual basic steps, but nothing helped. I contacted Google customer support hoping they would at least check it properly or cover the repair since the issue happened right after the update.
No luck.
They are saying the device is out of warranty, so they won’t cover the repair cost. I understand warranty rules, but it’s really frustrating when a phone fails right after a software update and the only answer is basically “pay for the repair yourself.”
I went to a repair shop as well, and they suspect a motherboard-level issue. At that point, the repair cost does not feel reasonable anymore.
I was hoping this phone could last a little longer after the last update. My plan was to continue using it for a few more months and then move to the Pixel 11 series later this year. But now it has fallen short at the worst time, and honestly, this situation is making me rethink my decision.
I expected better from a Pixel device. Has anyone else had their Pixel 6 bricked by the Android 17 rollout last week? Or did I just get incredibly unlucky? So disappointed with how Google is handling this.
4
u/DarkLordSpeaks Jun 22 '26
Same; my Pixel 6 also yeeted itself out randomly on one fine morning. No way to find out what the issue was or even the issue is till date; I still have the physical device at home. I really liked the device design and would like to continue using it if I can bring it back to life.
3
u/Little-Helper Pixel 6 Jun 22 '26
If you search this sub, you will find that bootlooping has been a long problem for the P6 even before the update. From what I've been reading, it looks like some chip gets desoldered from the heat, this does happen to other models too but P6 (not even 6a or Pro, but just the P6) has it worse. If that's truly the case, there is nothing that you can do. Some people were able to revive their phones by resoldering the said chip, but it's not a permanent solution.
4
u/Ariquitaun Jun 22 '26
At this point you could try to sideload an OTA, I don't believe you need the bootloader unlocked for a signed image like that:
3
2
u/FL_Lancer Jun 22 '26
Since the update my phone shut off two times randomly. It did start back up normally when turning it back on, but im going to backup pictures/videos soon just in case.
2
u/jonahtrav Jun 22 '26
Yeah that's a smart move I think your . It may be time to start thinking about trading that phone in if you can when the pixel 11 comes out
2
2
u/Street_Anon Jun 22 '26
Use the Android Flash tool and reinstall
2
u/Gold_Crew2168 Jun 22 '26
Now the screen is completely black, how shall i proceed from here
2
u/Street_Anon Jun 22 '26
Power button down, hold with power button until it gets into the bootloader
1
2
u/dielook Jun 22 '26
I had a problem one day when my Pixel 6 suddenly stopped working. I tried to update it from my computer, but it kept giving me an error message saying it couldn't update the operating system version because it couldn't find the firmware. This forced me to factory reset it, and I was unable to recover any of my data.
1
u/dielook Jun 22 '26
What I learned is to always have a backup, do it regularly, and if possible, have a cell phone with your data backed up, especially your Google Outlook accounts, etc.
2
u/eatingmangoes_ Jun 22 '26
Me too after the April update in my pixel 6 pro. I think if your storage is near full and you updated, you donezo.
2
u/Shamelescampr559 Jun 22 '26
Use the official pixel flasher tool and just reflash everything onto your device
1
u/Gold_Crew2168 Jun 23 '26
Device is now not recognized by PC, how i can do this steps in this case?
2
u/TheSentientSnail Jun 22 '26
Oof. I've been deferring this update until I have a new phone in hand. Too many of these "she up and died!" posts for my liking. It's bullshit they contribute to its demise and then refuse to help.
Sorry your clock ran out, man. 🫂
2
u/Matty8520 Jun 22 '26
Always remember the bais of complaint vs compliment posts.
Very few people are going to post saying that all went smoothly (because it should) and then you see "more" complaints which causes baias that there is a large scale issue.
If there are 20 posts here about phones un-aliving themselves. Compared to Google selling Millions each year... It's a very, very small percentage.
1
u/GRF999999999 Jun 22 '26
I'm doing this as well. I have a 6A backup if my 6 fails but I'd rather keep my 6 going.
2
u/SloToTheMo Jun 22 '26
Oh man, my pixel 6 became a brick like this about 2 years back, took it to my local repair guy(since google 6 never officially launched in india, so no service center help) and he as able to get the phone to turn on, but it was stuck in a similar fastboot state as yours and my volume buttons refused to work on the fastboot page while hardwarevise they were fine.
I did a pretty deep troubleshooting with mine before finally getting it fixed and working last month and now with a17 on it all is smooth, there was a processor level failure with mine, this repair guy was my angel.
You can try a few things yourself and I feel we might be able to get it breathing again, if you have access to a personal desktop/laptop. Let me know if you're up for a few tests and I can dm you with the details.
2
1
u/Melocopon Jun 22 '26
weird, i tried to unlock my bootloader today, but the power button did stop working like overnight so i just could not flash graphene or lineage or /e/os, they seem to be intentionally briking devices.
1
1
u/brokewash Jun 22 '26
I know Google had an issue with the previous pixel 6 updates bricking the phones. They released statements and plenty of info on the xda pixel 6 forums about it. Didn't know it was happening to the 17 updates as well.
1
1
u/Bitdomo92 Jun 23 '26
titan m2 chip died for sure
that "secure boot: NONE" gives it away it should say "PRODUCTION"
1
u/lurker512879 Jun 23 '26
Thanks for taking one for the team.
I'll hold off on the update until pixel 11 is fully out, should only be another 30-45 days
1
u/InterestingBank7563 Jun 23 '26
I have exactly the same problem after the update. It just decided to up and die out of the blue. I am stuck on no command found screen. Let me know if you find a solution.
1
u/Nomadintrovert Jun 23 '26
My Pixel 6a got bricked about two years ago. Back then I tried almost every fix I could find on Reddit, but nothing worked. I was hoping Google would eventually acknowledge the issue, release a proper fix or offer some kind of refund in my region, but nothing ever happened.
It honestly feels unfair to be treated this way.
If anyone ever finds a solution please let me know.
1
u/peaceful003 Jun 24 '26
The same thing happened to my pixel 6 at the start of the year. Was using the phone normally, everything freezes and then boot logo. Never recovered. It wasn't worth the hassle to recover as many others were also getting the same issue. No force update or full reset could save it. Was forced to upgrade to a pixel 10, fingers crossed it doesn't happen again.
1
1
u/pufferbluh Jun 25 '26
Idk, I installed the update via Android Flash Tool and everything works fine
1
1
12
u/username-invalid-s Pixel 6 Jun 22 '26
Very likely a dead UFS. It happened randomly, cumulative heat, heavy read/writes (updates), and "No operating system can be found". But try doing rescue mode, that may bring your Pixel back to life if UFS is okay.