Phone unresponsive after battery dying and plugging phone in to charge.

evesie

I mistakenly let my phone die last night, but didn't think anything of it and plugged it into the charger. Came back to the phone later and the screen was still off. Held power for about 3 seconds and the bootloader screen flashed a few times, and now the phone is doing nothing at all despite being connected to power all night .

Its not showing a bootloader screen, not a battery symbol, nothing.

I have tried holding the power button down, power and volume down, tapping power repeatedly, nothing seems to have any effect and the phone is completely unresponsive with a blank screen.

Any suggestions on what I can do to resolve?

Lilac6044

evesie There are a number of these posts on this forum. The github issue below may help also. It is catered to a specific usb setting but the workaround may help.

https://github.com/GrapheneOS/os-issue-tracker/issues/3590#issuecomment-3087453110

Neo14

Hello,

Same problem with my Pixel 8..
Black screen

Lilac6044

Lilac6044 Just saw you said you can no longer get to the bootloader screen. Try holding the power button for a long time (c. 60seconds). See if anything happens.

Neo14

Lilac6044

Thanks
After 30 seconds, the phone reboot with Google Logo, GrapheneOS Logo, and the password request.
When I start to type the password, the screen goes black and I can't do anything. Even the charging logo doesn't appear.

Lilac6044

Neo14 can you see the battery percentage?

evesie

Lilac6044 i

Neo14

I was able to get to the boot loader but i am having the same problem where I can see the home screen and battery percentage (100%) for a few seconds and then the screen fades to black and becomes unresponsive again. I have rebooted it probably 5+ times. Unsure where to go from here

Neo14

Lilac6044

When the screen goes black, nothing appears...
After 3 attempts, I succeeded! It's time to make backups!

I might activate USB debugging and unlock the bootloader, just in case?

Lilac6044

Neo14 My advice would be to make backups and try not to let the phone die again. You can unlock the bootloader but it will wipe the phone regardless so I would leave it as it is.

Neo14

Lilac6044

Thanks,
I meant to enable "OEM unlocking" in the developer options

Neo14

evesie

I had also connected the phone to the PC; I don't know if that helped...

evesie

I eventually got it to load properly by retrying the boot process (holding power + vol down for 20+ seconds) around 10 times or so.

strife-john-frozen

evesie wouldn't pressing the power button on the boot warning also work to let the phone charge for a while before it boots?

Neo14

1/ USB-C charge only is enabled
2/ ADB debug with USB is disabled
3/ OEM Unlocking is disabled

Let's imagine that GrapheneOS no longer starts, for example, due to a boot loop. With the options 1, 2 & 3, I wouldn't be able to unlock the bootloader and reinstall a new GrapheneOS?

theOtherAragorn

This is also happening to me. I don't think it's a simple 'out of power' issue. My phone seemed unable to charge, steadily lost power, and died. It was entirely unresponsive so I left it plugged in to charge and managed to hold down the volume+power and that got me into the boot screen. It had fastboot turned on, which seemed unusual as I hadn't noticed it previously. If allowed to resume booting, I get the G logo, the GrapheneOS logo, I will very briefly see my lock screen and then the phone 'dies' again. The power bar in that brief moment shows at 100%. I've gone through this several times and it's the same every time. I'm going to try to find instructions for a recovery install, but will be without a device until then. Has there been an update pushed recently that might have caused this?

To note: I've not installed, (chosen) to update, or customized my device in anyway beyond installing the standard Graphene OS image. The device is a Pixel 9a.

theOtherAragorn

Well, after 24 hours of doing absolutely nothing, the device is suddenly powering on and working. That even further suggests it was an update pushed by the Graphene team which isn't super encouraging. I think I read there's no way to opt out of those pushes, but I can't really risk the security and useability of my phone b/c someone with no accountability hit the wrong button. Super discouraging stuff.

Whispering_R

theOtherAragorn I can personally say this is NOT a recent issue nor that a fix was pushed in the last 48h. I've had this issue twice now. One being right now, the other being nearly a month ago (9th of August), which also "fixed itself" after a day or so of the phone not working. Same deal, phone died, would be stuck turning on and instantly off, until it went unresponsive after a couple of tries.
The phone died a few times since, so it doesn't happen every time the battery runs out. However, an issue like this is simply unacceptable, and having to gamble if my phone will be a paperweight every time it turns off is not one I want to take for the next 5 or 7 years. Also with a Pixel 9a, which I bought specifically for GrapheneOS. Thinking of returning it now, honestly :/

Whispering_R

Did some digging and it seems this issue has been reported as early as May (https://discuss.grapheneos.org/d/22206-help-my-pixel-8-pro-just-dead-this-morning/20). Seems whatever's causing it has not been fixed since.