this post was submitted on 06 Aug 2024
53 points (96.5% liked)

Android

27509 readers
253 users here now

DROID DOES

Welcome to the droidymcdroidface-iest, Lemmyest (Lemmiest), test, bestest, phoniest, pluckiest, snarkiest, and spiciest Android community on Lemmy (Do not respond)! Here you can participate in amazing discussions and events relating to all things Android.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Rules


1. All posts must be relevant to Android devices/operating system.


2. Posts cannot be illegal or NSFW material.


3. No spam, self promotion, or upvote farming. Sources engaging in these behavior will be added to the Blacklist.


4. Non-whitelisted bots will be banned.


5. Engage respectfully: Harassment, flamebaiting, bad faith engagement, or agenda posting will result in your posts being removed. Excessive violations will result in temporary or permanent ban, depending on severity.


6. Memes are not allowed to be posts, but are allowed in the comments.


7. Posts from clickbait sources are heavily discouraged. Please de-clickbait titles if it needs to be submitted.


8. Submission statements of any length composed of your own thoughts inside the post text field are mandatory for any microblog posts, and are optional but recommended for article/image/video posts.


Community Resources:


We are Android girls*,

In our Lemmy.world.

The back is plastic,

It's fantastic.

*Well, not just girls: people of all gender identities are welcomed here.


Our Partner Communities:

!android@lemmy.ml


founded 1 year ago
MODERATORS
 

Edit: Many thanks to @MrGerrit@feddit.nl 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?

top 16 comments
sorted by: hot top controversial new old
[โ€“] MrGerrit@feddit.nl 25 points 1 month ago (1 children)

Have you also tried holding down all three buttons at the same time?

[โ€“] sgibson5150@slrpnk.net 18 points 1 month ago

My man! That hadn't occurred to me. Phone appears to be off. Thank you!

[โ€“] user224@lemmy.sdf.org 10 points 1 month ago (1 children)

Once you get into recovery manually, is there no "Power off"? It seems there should be:

Can you get there?

[โ€“] sgibson5150@slrpnk.net 10 points 1 month ago (2 children)

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.

[โ€“] scsi@lemm.ee 5 points 1 month ago

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. :(

[โ€“] DaTingGoBrrr@lemmy.ml 1 points 1 month ago (1 children)

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

[โ€“] sgibson5150@slrpnk.net 4 points 1 month ago (1 children)

All I've gotten so far are sore fingers. ๐Ÿ˜†

[โ€“] DaTingGoBrrr@lemmy.ml 2 points 1 month ago

Damn... ๐Ÿ˜… Then I am out of ideas unfortunately

[โ€“] Chozo@fedia.io 8 points 1 month ago (1 children)

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?

[โ€“] sgibson5150@slrpnk.net 12 points 1 month ago* (last edited 1 month ago) (1 children)

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

[โ€“] Chozo@fedia.io 2 points 1 month ago

Thanks for sharing that! Hopefully I don't have any catastrophic failures any time soon.

[โ€“] Magister@lemmy.world 4 points 1 month ago (1 children)

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?

[โ€“] sgibson5150@slrpnk.net 2 points 1 month ago (2 children)

Wouldn't USB debugging have to be enabled on the device for that to work?

[โ€“] catloaf@lemm.ee 4 points 1 month ago

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.

[โ€“] Magister@lemmy.world 1 points 1 month ago

USB debugging is when you have full android loaded and all. Try to plug your phone on a PC and see if something appears

[โ€“] Andromxda@lemmy.dbzer0.com 1 points 3 weeks ago

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.