No Valid OS Recurring Issue

After leaving it alone connected to my computer for a bit mocking me with the "no os " prompt, it was charging and displayed the charging bolt on the screen, disconnected it, pressed the power button, and was able to boot up properly again. I have no idea how that worked.

ispotato Providing power while it struggles is good. Typically if it struggles for a while it will succeed. Plus, running out of power during an update is risky.

Just wanted to chime in that I ran into this problem on my Pixel 7. Up until the update around a month ago everything went smoothly. Then I got the No valid OS found error when I did the update. Got it to reboot after a couple tries and it seemed to download and install the update properly. Since then I have continued to occasionally run into the booting issue.

The phone has so far always managed to eventually reboot. Attaching it to a power supply seems to help it happen faster. I'm not technically proficient but I've read up on the process of sideloading and feel I could try that in Rescue mode if it fails and normal rebooting doesn't seem to work. I'm not inclined to experiment with it though just to see what happens.

In the meantime I've backed up onto a flash drive and have taken to avoiding rebooting unless I'm in at home. I have considered if this is related to a hardware failure though the phone being less then a year old and the coincidence of it running perfectly up until that update has made me kind of wonder about that.

+1-ing this with a pixel 6.
My events were:
-1 day staying on completely dead battery
-after plugging it in i saw 2 restart until the "battery with bolt" appeared, then when wanted to load in (holding the power button) again 2 restarts until i saw the "sparking percents".
-Battery 100%, pulled down.
-Had to go online, update got pulled, while aurora got the app updates too. Updater promted me to reboot. when everithing finidhed, i rebooted.
-2 reboot failed, third loaded in.

A full reinstall would help or not really?

GiftedAccess A full reinstall would help or not really?

It seems as if that is not necessary or effective, so I don't think it is recommend at present.

de0u I thought only to the case when it is an escalating problem, where a value or something non function-critical changing with reboots or something and at the given boot it fails.
I heard, saw no defenite explanation of the cause... (ok firmware, but how, what.. [i will have tocheck]).
I hope only an interstellar particle hit in the right place, in the right time, and not something what degrades in my phone phisicly... or the firmware will be fixed soon.

This morning I experienced the no valid OS issue and could only get it working again by sideloading the update. Luckily it worked out.

Mahalo Glad it worked! Which phone model do you have?

Bit of a follow up. Have not 2023110700run into the issue since the last post. Albeit I have only rebooted on a few occasions.
I just installed the 2023110700 update and rebooted without issue. Hoping the issue is resolved.

ispotato
This is a known firmware issue. Typically rebooting (sometimes multiple times+ ) will resolve it. This is something that is outside the scope of the GrapheneOS project.