Didn't boot after update, now does

Googlesucks69

BobHanson in fairness I can say I have ran alpha since Pixel 6 and had zero issues until this. If anyone else sees this, save yourself don't factory reset. You need to sideload the latest update be CAREFUL with the partions brush up your adb knowledge and its cinch, promise everything will transfer and the issue will be fixed courtesy of user wayfare.

Googlesucks69

other8026

BobHanson You see it seems many 7pro users it resets and fixed no issues again, pixel 7 users.. It keeps happening over and over until you sideload update again. This has been the experience of quite a few pixel 7 users who have had this issue anyway.

other8026

Googlesucks69 You see it seems many 7pro users it resets and fixed no issues again, pixel 7 users.. It keeps happening over and over until you sideload update again. This has been the experience of quite a few pixel 7 users who have had this issue anyway.

Right. Some people were having issues upgrading and the update failed, but there is another issue that seems to be caused by the firmware, which Google has to fix. A couple people have said that sideloading fixed the issue for them, one other that I know of said their phone started working again after multiple reboots.

macrosploit

other8026 Another data point: My phone still doesn't boot after hours but after sideloading the update in rescue mode every once in a while it can enter the charging/battery percentage screen when plugged in. Rebooting gets it back into the "No valid operating system" boot loop. For now I'll just wait and let it reboot for a few days.

other8026

macrosploit So, let me get this straight. What you're saying is that the phone is rebooting even after you attempt to sideload? It never fully boots up? If that's the case, have you tried sideloading again?

If it isn't working even after sideloading, then I'm afraid there might be something else wrong with it. Others with the same problem have reported that their phones booted up normally after sideloading or rebooting many times.

macrosploit

other8026 Yes exactly. However, after about 3-4 hours and about 1500 reboots it finally booted up, so it really is a matter of trying again and again and I was just unlucky with how much I had to do that.
I do find that weird though, does an A/B system work in a way so that it randomly chooses the partition to boot? Confusing and time-consuming overall.

Aaron

Ran into same issue on P7. Per recommendations I kept rebooting and after 5-6'ish tries it rebooted correctly. Now it updates and reboots without issue.

other8026

macrosploit does an A/B system work in a way so that it randomly chooses the partition to boot?

I don't believe it's random. You can refer to the official docs: https://source.android.com/docs/core/ota/ab#slots

From what I understand, an update is installed to the unused slot, then that slot is marked as bootable. The phone tries to boot to that new bootable slot. If it's successful, it's marked as successful. If not, it's supposed to go back to the old slot (effectively "rolling back" the update). Though, since many people have had this same issue, I'd guess that the firmware is messing one of these steps up.

f13a-6c3a

Well, sad to report that my P7P was another victim of "no os" failed boot last night.

The phone updated to 2023111500, prompted to reboot and cycled up ok, recompiled apps and prompted to reboot again at which point failed with "no os" error. After 4-5 off/on cycles it started up.
The interesting part for me is that when the phone started up, it was into the latest update 2023111500 with all apps already recompiled, which means it did not fall back to the previous instance in A/B install mechanism but somehow plowed through the "no os" issue - am I correct? If yes, then why did it fail and also why and how it eventual "forced through" and started up?

other8026

f13a-6c3a The phone updated to 2023111500, prompted to reboot and cycled up ok

After this step, the new slot would have been marked with a flag to indicate that it had booted up successfully.

f13a-6c3a The interesting part for me is that when the phone started up, it was into the latest update 2023111500 with all apps already recompiled, which means it did not fall back to the previous instance in A/B install mechanism but somehow plowed through the "no os" issue - am I correct? If yes, then why did it fail and also why and how it eventual "forced through" and started up?

I'm not sure I follow this question. But maybe this will help clarify...

There's little that is known about this issue or what causes it. As far as I know, based on what I've read here and other places, the no-OS-found issue is a firmware issue, not a GrapheneOS issue. That means that Google has to fix it. Maybe we will learn more about what caused the problem later on down the road, but maybe they will just fix it and not share any details.

f13a-6c3a

other8026 Tank you for clarification. Your first response actually answers my question which was how did the phone, eventually, loaded the updated partition if it just failed. Now I see that I overlooked the first reboot which marked the updated partition as bootable.

Yeah, I hope more information comes to light to determine what causing the "no os" boot failure as it was pretty unnerving

joaqgl

My device (6a) also failed to boot after the update, but with a different error screen, the RED eio screen. I have been not been able to sideload due to a problem I explain in my own post here. If folks here have any suggestions I would really appreciate it