I ended up factory resetting everything is working normally now. But yeah I was unable to side load anything
Unable to boot into graphene after phone running out of battery
The problem in this instance had NOTHING to do with the system image being "corrupt". It had to do with how the phone shut down. It clearly powered off without a clean shutdown and unmounting the filesystem safely. While this is very rare, it clearly corrupted the USERDATA filesystem during the unclean shutdown.
intelligence That sounds plausible... but is it expected that sideloading an OS image would fail as a result?
intelligence With my very limited knowledge I would tend to agree that it was the user data filesystem that was corrupted. That being said, after the phone died it did boot back into user system before dying again without having unlocked the phone. Something happened when the phone died during the standard boot process, after that point it seems to have locked out everything, when trying to flash the OS image (not the update OTA file) it was unable to verify the signature (as stated previously with my limited knowledge this could be by design which would make sense). The phone would also flash into a "ghost" charging icon even when the phone was not plugged in. It happened on the first few reboots and then went into the google logo boot loop. During this "ghost" icon thing I was unable to boot into graphene recovery.
Tic If you have already done a factory reset, so there is nothing on the phone you care about, you have room to experiment. Maybe sideloading will work now that there shouldn't be potential interference from the plausibly-bad/now-gone user data partition.
I have a faint memory that you can see the "corrupt" message on startup for a while even if everything is fine, because the procedure that clears the "corrupt" flag runs only in limited circumstances. If sideloading the current OTA image doesn't clear the "corrupt" flag, then I think your options might be (a) flashing back to Google's stack and then reinstalling GrapheneOS from scratch (kind of a pain), or (b) waiting until a new GrapheneOS release is issued, which I suspect will cause the "corrupt" flag to be cleared.
But I am not an expert, so I might not have this all correct.
Tic Something happened when the phone died during the standard boot process, after that point it seems to have locked out everything,
Yes, it detected a corrupted filesystem (userdata), marked it corrupt, and rebooted.
Tic Sideloading is for OTA packages, not factory images. You tried to sideload the factory images which isn't how it works and is why it was rejected since it's not the signed OTA package. If you want to try sideload, follow our instructions.
Unfortunately I have with my Pixel 6a the same problem: After my battery turned off at 0 percent and I tried to switch it on at the beginning of charging, it is in a boot loop.
I have tried an update via ADB. Unfortunately without success.
So how you found solution for this. Or if not... before I do a factory reset, I would like to know if there is a way to get the data.
Thanks
I also observe this strange behavior... as soon as you plug in the charging cable, the pixel tries to boot up, usually shortly after the PIN entry for the SIM card appears, the pixel goes off and boots up again a short time later with the message that the data is corrupted and requests a factory reset or reboot.
Solution:
Wait a few minutes so that the Pixel has enough power to complete the boot process to the extent that you can enter your PIN and reboot.
Desired solution:
Why doesn't anyone come up with the idea of deactivating this "I boot immediately when the cable is plugged in" function?
Can't anyone tell me that this behavior makes sense and contributes to the security of the device if the device is sent into the boot process immediately when it is supplied with power after a battery discharge, even though it is clear that this boot process is unsuccessful?
So forget this factory reset nonsense and just wait a few minutes and boot up.
WhoTheFuckisAlice Why doesn't anyone come up with the idea of deactivating this "I boot immediately when the cable is plugged in" function?
I agree. I have a MacBook that boots if I just open the lid -- as if I would never want to open it and clean the keyboard/screen.
I think this behavior is due to the firmware. If so, the only party who could change it would be Google.
- Edited
de0u As is so often the case when it comes to the functionality of a normal device. But why don't these errors occur with stock OS?
Edit: But next tip, if the phone reboots push power button in the OS checking screen, then the booting stops and we have a beautiful loading screen while phone is off