GrapheneOS won't start after dead battery

DeletedUser370

xxboigraphene Luckily currently, I believe I currently have USB debugging enabled!

From experience, I have never needed USB debugging to be enabled in order to sideload a release with ADB.

Which OS are you using? If it's Windows, I might be able to write a short guide on how to use ADB to sideload (if time allows). It's not difficult but might be a bit confusing if you haven't used ADB before.

de0u

DeletedUser370 From experience, I have never needed USB debugging to be enabled in order to sideload a release with ADB.

Indeed. But many web pages suggest adb reboot recovery instead of using the device buttons to enter Recovery. I assume that's the source if the "need" for USB debugging.

xxboigraphene

de0u

Hello, sorry for such a delay. I had to mind my life for a bit but ive finally had a moment to sit back down and work on this again.

de0u That piece says: "You'll see a screen with a sad Android robot lying on his back with a red exclamation mark. To open the hidden recovery menu, press the Volume Up button while holding the Power button". Thus I recommend that on the "No command" screen you press and hold the power button while tapping and releasing the volume-up button. That works for me. Does it work for you?

It doesn't let me get into the hidden recovery menu. when I hold the volume up button and power button in the "no command" screen it makes it go black and then it boots back to the "Your device is loading a different operating system" screen and the whole process is back to square one. I have tried quite a few times is different ways and it won't let me get forward.

Do you have any suggestions?

de0u

xxboigraphene When I hold the volume up button and power button in the "no command" screen it makes it go black and then it boots back to the "Your device is loading a different operating system" screen and the whole process is back to square one.

It is necessary to hold the power button while pressing and releasing the volume-up button, and then release the power button. Any time the power button is held down for a long time the device will shut off.

Press the power button and hold it.
While the power button is still held, press the volume-up button.
Quickly release the volume-up button.
Release the power button.

cattaway07

I am having the same issue with my pixel. I dropped the phone and the screen cracked. It sat dead for about a month. I installed a new screen and now I am stuck in a boot loop. I installed an OTA update from grapheneOS. Windows PowerShell and the phone say that the install was successful but the phone just goes back into a boot loop. Please help

de0u

cattaway07 It is possible that the fall damaged more than just the screen. Has a repair shop looked for other issues?

Maciektruskawka

Hi. How do you fix that? Please help, my pixel 8a is dead. I need everything from that

de0u

Maciektruskawka Please help, my pixel 8a is dead.

If it is completely dead, it will likely be necessary to take it to a repair shop. If not, please describe the exact symptoms.

randomwords

Another thing you can try that worked today on my 6a after dying was wait until you get to the "Loading a different operating system" page, pause it, and then let it sit for 30 mins or so. This page seems to use a minimal amount of power since it isn't really booting anything yet if it's paused, as long as you're connected to a decent adapter it might slowly charge, at least enough to boot with 2-3% charge. That worked for me at least. My phone wasnt suffering from any kind of boot partition damage or physical issues.

desdichado

Hi guys, so apparently I ran to the similar issue with my Graphene OS Pixel 8a. It ran out of the battery during the night. Later that night I plugged it to the charger, not checking it and went back to sleep. In the morning I unplugged it showing 89% charge (on off screen) but I couldn't start it. Later at work, I got to the loop. I tried to turn it off and reboot it and I even got it booted, but when I entered the pin, it went off and to the loop again. I repeated the process several times with no luck. I tried to let it charge in paused "loading a different operating systemů screen and started in in approx 30 minutes. That helped and the Graphene loaded as its supposed to. Thanks a lot guys!

bonus_crab

I'm having this same issue right now I think , stuck in a sort of boot loop after dead battery during the night. Side loading the latest update fails. I took pictures of the errors in the log after the failed sideload. Here's some pictures of the logs after 2 failed attempts.
https://postimg.cc/MMd2vsmc
https://postimg.cc/9w03TGLL
https://postimg.cc/w7t8jQyv
https://postimg.cc/K48hd2mt
https://postimg.cc/XX16Wzvm
https://postimg.cc/bsKXDSkR
https://postimg.cc/186kpRK1

bonus_crab

I rebooted after and actually got into the OS, and it began 'validating system update'. I'm backing everything up as best I can now... seems solved atm I'll be back if not.

lor-mer

I just had a different problem on Pixel 9, my battery is stuck at 100% but the phone just died. There is no way it's 100% after 5h of Newpipe videos... After rebooting it still shows 100%...

SourLemonJuice

This basically happened to me after every time the battery drained. No data has been damaged but the phone can't charge any power into the battery.
Maybe there is a security protection feature that cuts off the USB connection before the system startup. However, android also doesn't allow the phone to bootup without power...

In my opinion, if it's not a trade-off, then it's a bug. If you encounter this, try to enter the fastboot screen or click the power button once on the "Loading a different operating system" screen to keep the phone powered on. It should charge successfully.

de0u

schweizer SourLemonJuice My vague sense is that the power controller believes it knows which state the phone "should" be in, on or off. I think if the OS is explicitly shut down then it tells the power controller that the target state is "off", so then plugging in a charger causes the device to present its happy charging display. But I think that if the device runs the battery flat the target power state remains "on", so that plugging it in causes it to try to boot.

I'm not saying this is a good idea! But it might be a useful model for people to keep in mind.

The good news is that tapping the power button to pause booting, and then charging for not very long, should make booting possible if the device stays plugged in. The surest thing is to let it charge for at least half an hour, but I don't think that's necessary in most cases.

It may be bad for the battery over time to repeatedly run it flat.

schweizer

I had a very similar problem recently with my Pixel 6. As soon as I plugged the charger the phone tried to start. But I did not want this, I wanted it to charge first. There must be a mechanism that prevents or interrupts (fast) charging during the boot phase so if there is not any charge left the phone will shut down. And the process restarts.

My solution was to press the power button to pause the startup in the bootloader screen. In that state it does charge. So I waited a bit and resumed the startup later.

The fact that the phone immediately tries to start when plugged to a charger after running out of battery is a bug to me considered the phone is not able to boot in battery bypass mode.

de0u

nosch I do not understand why the phone boots again after it turned itself off (because of a drained battery) when it is pluged to a charger. It should rather stay off and I could turn it on manually...

Scroll back a bit... de0u

Church

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

sman

Just happened to me on Pixel 8 Pro. Pressing the power button to pause the startup in the bootloader screen and charging the phone in this state solved my problem.

r134a

I do have a powerbank that displays when 'quick charge' is being used by displaying a green light, i believe the powerbank determines > 5W as 'quick charge'. I've noticed several times while rebooting, in boot fase the powerbank doesn't show the green light, indicating that while booting, charging is (below) 5W.

This alligns with this fenomen described here, that when the battery is completely depleted, and when plugging when the device automatically starts the boot process, it can't deliver enough power (below or equal to 5W) to boot, hence why the described method of pausing probably works.

Perhaps someone with more accurate gear than 'a powerbank with a green light' can replicate this and report back accurate numbers.

rufus

I mesured right now with a usb powermeter and have observed that while boot to OS is no charging at all.

When starting phone while booting the bootloader the phone is charging only in normal 5V mode.
While booting to OS there is no charge at all.
(When phone is off it starts with 5V charging and turns to 9V while in chargemode with the big battery symbol showing up.)

« Previous Page Next Page »