Pixel 7 - boot loop - lock screen shows briefly

nelzzz89

its gotten further than it did before, currently verifying update package and is at 33%, its never gone this far! fingers crossed

Developer-Dude

nelzzz89 thats a good sign!

nelzzz89

It completed the install and I had high hopes but it was the same as before, showed the lock screen for a moment then restarted again, and comes up with this again :(

https://ibb.co/mVtJnmCK

nelzzz89

There is a difference to the fastboot screen to before, where now i has boot slot a instead of before it was b. could this be something i should look into?

https://ibb.co/kVrs16wm

nelzzz89

also snapshot-update-status: merging has changed to snapshot-update-status: snapshotted in cmd

nelzzz89

new overview of the situation now
Pixel 7 / panther, GrapheneOS 2026062800. Battery died during reboot after OTA update. Device shows my normal lock screen briefly, I can swipe up and almost reach password entry, then it reboots before keyboard appears. Recovery says “Cannot load Android system. Your data may be corrupt.” Bootloader locked. Both slots successful. Correct signed OTA package was sideloaded successfully via recovery. Active slot changed from B to A. snapshot-update-status changed from merging to snapshotted, but the same reboot issue remains. Data is important; looking for any non-wipe recovery options if possible.

Developer-Dude

nelzzz89 yes. Reboot again to see what it ends up in. Your phone has 2 boot slots. If one fails, it rolls back to the other one. Try sideloading again to see if it sideloads to the other slot

Developer-Dude

nelzzz89 try sideloading again to see if it goes to the other slot. I'm hoping this isn't a hardware failure, but you never know

Developer-Dude

Also, when you boot up the phone, use the power button to pause it at the "your device is loading a different operating system" warning screen. Check the boot key hash and make sure it matches EXACTLY as below

3efe5392be3ac38afb894d13de639e521675e62571a8a9b3ef9fc8c44fd17fa1

nelzzz89

Developer-Dude Yep its exactly the same and i tried sideloading again and its on boot slot B but sadly still situation where it restarts after showing the lock screen for a split second. Is my only option to wait for a new update and hope that once it comes out i can try again?

de0u

nelzzz89 Further sideloading is unlikely to help at this point.

What if the device is booted into safe mode while it has no access to wireless networks? Remove the SIM card and go into the wilderness?

de0u

Developer-Dude Your phone has 2 boot slots. If one fails, it rolls back to the other one.

If the active slot is booted when it is not yet marked as successful, and that boot doesn't get to the point that it is marked successful, and that happens enough times, it will flip back. But it doesn't flip back and forth any time there is any sort of crash.

nelzzz89

de0u good suggestion but still same thing with no sim card in unfortunately. its seeming more and more likely there is corrupted data of some sort cos it reaches the lock screen for a split second, sometimes long enough for the keyboard to appear but it never gets far enough to enter my password, and other times it only shows upto half the screen load up before it restarts

Johnnyloans

Developer-Dude

[How to get a security preview file from GOS]

Go to the releases pages, copy any link (in this case the OTA update file for sideloading), change the URL link you copied so the version number ending in 00 is changed to end with 01

Now paste the new url into the web browser to get the 01 security preview file.

The error would have to be mention: "The version you are sideloading is 1 second older than what is currently on the phone" for the suggestion to get the 01 version to matter.

Earlier, maybe the OP downloaded the flash install .zip file instead of the OTA update file.

Sideloading should overwrite both boot slots. On the computer, if it says xfer: 2.0x then it wrote to both boot slots.

Sounds like the OS is most likely fine and there's corruption in the user data.

and/or there could be a hardware failure. Sorry mate. If you haven't gone into safe mode after sideloading, you could try that.

nelzzz89

Johnnyloans will try this now, thank you for the suggestion

nelzzz89

Johnnyloans unfortunately the same thing, lock screen shows for a second with the clock then shuts off, even managed to press the side button to get the 'calls and messages are silenced' popup when it did load but havent been able to have it on long enough to enter my password

nelzzz89

i think my only hope now is to just wait each time a new update comes, and try install it and hope somehow it fixes it, im in no rush to use the phone as i have my old one i can use in the meantime, i really do hope it'll be fixed eventually.

GrapheneOS-Jub

nelzzz89 i hope you will find a way to go to Safe Mode and possibly be able to save your important files. But since you cannot go to Safe Mode from a logged screen, perhaps going to Safe Mode after reboot?
I think Safe Mode will not help revive your loop problem as the problem is not an installed app or user service but possibly a data corrruption issue.
Waiting for next OTA update (sideloading) perhaps doubtful as your current update was anyway confirmed successful.
Would it do any harm if you repeat sideloading again the current update, let it run and just wait for several hours without any user intervention? In the hope that perhaps the unit is just "crawling & tired of moving" and later wakeup.

Developer-Dude

nelzzz89 yes have you tried Safe Mode yet?

de0u

nelzzz89 good suggestion but still same thing with no sim card in unfortunately.

Has the device been booted without a SIM card in a place where no known Wi-Fi networks are available?

« Previous Page Next Page »