Lost power during update

goblinoidtoad

I lost power during an update. Got to the fastboot screen, unlocked the bootloader with the installer. Then I was dumb and hit restart bootloader instead of flashing the update.

Now I am stuck with a charging screen. The black background, battery with a lightning bolt screen. It won't turn off with any combination of power or volume keys, even if I unplug it from the charger.

If I let the battery drain I get the "your device is corrupt" screen.

Thoughts?

intelligence

goblinoidtoad I lost power during an update. Got to the fastboot screen, unlocked the bootloader with the installer.

Sounds to me like it wasn't an "update", rather you were performing an installation.

Reboot to bootloader by powering on with the volume DOWN button held, then begin installation.

meiklmue

I assume OEM unlocking is disabled and you can't just reflash GrapheneOS with the webinstaller? Had a similar problem but unlocking was still enabled in my case.

For that and many other reasons I had to disable automatic updates as there is no "only apply updates when charging" option.

dirksche

meiklmue For that and many other reasons I had to disable automatic updates as there is no "only apply updates when charging" option.

How did you do this? Did I miss a setting?

f13a-6c3a

How did this happen? Dont Pixels, and GrapheneOS, utilize A/B targets which should prevent exactly this from happening?

Blastoidea

I was very curious about how this happened, but I just figured I must have missed something.

I’m still a bit mystified.

goblinoidtoad

It was an update. What happened was it was auto updating while charging from my laptop and then the power supply was disrupted (not sure if I jostled the cable or the laptop hibernated or something).

Letting the battery drain then recharging it got me back to fastboot and then I could reflash using the webinstaller, as OEM unlocking wasn't disabled because I forgot to do that step.

Thanks!

intelligence

goblinoidtoad It was an update.

If it was an update, then why were you in fastboot and why were you unlocking the bootloader? That does not make any sense!