Pixel 6 completely dead after September 2026 OTA update black screen, won't turn on
Has anyone else had their Pixel 6 basically brick itself after the recent September 2026 update?
Mine was working normally, but now it seems completely dead. The screen stays totally black and I can't get it to boot at all.
So far I've tried:
- Holding the power button for 30–60+ seconds
- Power + Volume Down to try to enter Fastboot
- Power + Volume Up
- Connecting it to a charger
- Connecting it to my Mac via USB
- Trying different boot/restart combinations
Nothing shows on the screen, no Google logo, battery icon, vibration, Fastboot screen, or recovery menu.
My Mac also doesn't seem to react when I plug the phone in. I'm going to check adb devices, fastboot devices, and the USB devices through Terminal as well, but so far there's no obvious sign that the computer can see it.
The strange part is that the phone gets noticeably warm/hot when I hold the power button and try to turn it on. So it seems like something inside is still drawing power, even though absolutely nothing appears on the screen.
This happened around the time of the September update, which is why I'm wondering whether the update could have caused some kind of firmware/boot issue rather than the phone randomly dying at exactly the same time.
I've also found Google's Pixel Update and Software Repair tool, but from what I understand it requires the phone to actually enter Fastboot first — which mine currently won't do.
I'm trying to avoid a factory reset or anything that would wipe the phone because I still have data on it that I'd really like to recover.
Has anyone with a Pixel 6 experienced something similar after a recent update?
Especially interested if your phone had:
- Completely black screen
- No Fastboot/recovery
- No USB detection
- Phone still heating up when attempting to boot
And if you managed to recover it, what actually worked? At this point I'm trying to figure out whether there's still some software/bootloader recovery method I haven't tried, or whether this is likely a motherboard/power issue and I need to send it to Google for repair.