Edit: Many thanks to @[email protected] for suggesting that I hold all three buttons down. That appears to have worked! 🙏
Pixel 6 Pro. Yes, I did a factory reset after patching. No, I wasn’t aware there was an issue. Yes, I understand there’s no fix for this.
My question is, how do I turn off the phone once it is in this state? I’ve tried holding power alone, power + volume up, and power + volume down for varying periods of time up to 30 seconds each. I’ve tried in the recovery menu and at the error screen. I’ve tried catching it during the restart. Can someone help me please?
You must log in or register to comment.
Have you also tried holding down all three buttons at the same time?
My man! That hadn’t occurred to me. Phone appears to be off. Thank you!
Once you get into recovery manually, is there no “Power off”? It seems there should be:
Can you get there?I only have the two options, Try Again and Factory Data Reset. The first just reboots the device and I return to the same two options. The second asks for a confirmation, then it shows an error (/system/bin/tune2fs is missing) and takes me to the “dead droid” screen briefly, after which it reboots and we’re back to the same two options.
I’m familiar with the news about the brick - in the past I’ve had this problem (I think it was a bricked… pixel 2?) and faced similar power off issues. Keep trying what you’re trying but in various ways - I vaguely recall that I had to press volume up first and then hold power or something like that (meaning pressing them both at once or power first didn’t work). One of the various combos you’re trying is supposed to be the one that forces it off after ~30secs of holding but a fuzzy memory reminds me it was real finicky to actually get working. Worst case scenario, just let the battery die. :(
If you hold down the power button for 10-20 seconds it should turn off. At least that’s how it works inside the Android system
All I’ve gotten so far are sore fingers. 😆
Damn… 😅 Then I am out of ideas unfortunately
Yes, I did a factory reset after patching. No, I wasn’t aware there was an issue.
I also have a Pixel 6 Pro and am not aware of this issue. Should I be worried?
There was a lot of coverage of it back at the beginning of July. Wish I’d paid more attention then haha.
https://duckduckgo.com/?q=pixel+6+factory+reset+brick&t=fpas&ia=web
Google’s official position is “contact us” which I did today, but they wouldn’t tell me whether it would cost me or not without sending them a video of the problem, which rubbed me the wrong way. I know my phone is out of warranty now but the manufacturer broke this with their own update. Probably no more Google hardware for me. 😐
Edit: This link includes steps to avoid the problem. https://support.google.com/pixelphone/thread/283220215#redirected=true
Thanks for sharing that! Hopefully I don’t have any catastrophic failures any time soon.
Can you connect it via usb to your PC? From here you may try a fastboot command to boot from an image or power it down?
Wouldn’t USB debugging have to be enabled on the device for that to work?
No, I’m pretty sure that’s an OS-level setting for adb. The fastboot system should be separate.
I’m pretty sure, anyway. I don’t think I’ve actually tested it.
USB debugging is when you have full android loaded and all. Try to plug your phone on a PC and see if something appears
As far as I know you can power down a Pixel at any stage by holding the power button for over a minute. Had to do this a couple of times when I flashed a bad ROM and got stuck in a bootloop.
