boot loop - Update issue to 2024102100

de0u

m0ng00se Have you tried booting in safe mode?

Does removing the SIM card help? (The need to unlock the SIM adds complexity to the situation.)

Is it possible that storage is full on the device?

m0ng00se

Tried safe mode. Vibration kicks, "safe mode" appears in the lower left corner. Passphrase screen (with my personal wallpaper) appears for a sec. Then reboot/boot loop.

Removed the SIM card already. I also had the thought, that the OS "can't decide which screen to boot first", because of the switches.

Storage can't be full. I have the 256 GB hardware, and I am very conservative on this. Few pics, no video or music content.

Is there any possibility to get hands on a signed OTA update before 2024102100? I saw that I can still download 2024101200. Anything in between?

de0u

m0ng00se Is there any possibility to get hands on a signed OTA update before 2024102100?

It looks as if the update images for the cancelled stable candidates have been removed. Since some of them were troublesome for some users, I guess that's not surprising.

DeletedUser87

this sounds very familiar. I had a lot of customers with broken UFS/NAND that exhibited the same symptoms. I don't know if downgrading will be possible even, afaik that was disabled some time ago between major Android versions. Your best bet would be to wait for a new release I guess.
In your case, I feel like the chance of data loss is very high. But, to be fair, if it's only been a few days since the pictures were taken - while still unfortunate - your kid is not quite newborn anymore, but still very fresh and worthy of memorable pictures ;) I hope all turns out well!

m0ng00se

From what I see on the recovery screen, it seems that I am still stuck on the 2024101200 (second line).
So any OTA update from there on - but not the 2024102100 - could be a possible alternative or be at least a try.

Although a HW defect is always possible, there was no harming incident or whatsoever.
To be honest, it would be my first defective HW, till back to the days of Nexus 4 and Nexus 7.

Sideloading with 1.2 GB is also not a problem.

I already set eyes on the next release. Backup HW is up and running.
So it's all about the rescue mission now ;-)

de0u

m0ng00se Although a HW defect is always possible, there was no harming incident or whatsoever.

If the flash storage had been about to fail, downloading the A15 release all in one go might have been enough concentrated load to push it over the edge. I think I remember seeing that for this release even the delta update is large (not surprising since it's a new OS). Anyway, I believe the delta update saves only download size: to do the upgrade it is necessary to combine the delta with the running system image to write an entire new system image.

And then after rebooting GrapheneOS will pre-compile all of the installed apps, which is another burst of load on the storage.

Overall, it is possible that the upgrade itself pushed the device over the edge. Hopefully not, in which case the next release might get you back in business. But it's a possibility.

m0ng00se

Maybe I can get your opinions on the following:

My bootloader is locked. So there is no option to change the boot slot from (currently) b to a, without user data loss?! Because the bootloader has to be unlocked first, right?
Would it be a possible try to sideload the ota-2024102100-beta? I am running the stable train. Maybe something small differs and the update follows trough? Or is crossing path with beta not advised on the ota level?
Do you have any idea, where to get the ota updates between ota-2024101200 and ota-2024102100, e.g. 2024101600? Via contact to the project's email adress? I don't want to bother the staff, but they would probably be the best source for that...

de0u

m0ng00se Would it be a possible try to sideload the ota-2024102100-beta? I am running the stable train. Maybe something small differs and the update follows trough?

That's not how GrapheneOS releases work. There is only one 2024102100 image. That one image was made available first to alpha-channel devices, then beta-channel devices, finally stable-channel devices.

m0ng00se Do you have any idea, where to get the ota updates between ota-2024101200 and ota-2024102100, e.g. 2024101600? Via contact to the project's email adress?

Maybe. But the device will reject all releases older than whatever it is running. This is to prevent an attacker from forcing the device to run an old release that contains a known exploitable bug.

other8026

m0ng00se My bootloader is locked. So there is no option to change the boot slot from (currently) b to a, without user data loss?! Because the bootloader has to be unlocked first, right?

I don't remember the exact thing that happens, so I'll just use vague words here, but all user data is lost when the bootloader is unlocked.

m0ng00se Would it be a possible try to sideload the ota-2024102100-beta? I am running the stable train. Maybe something small differs and the update follows trough? Or is crossing path with beta not advised on the ota level?

de0u already responded to this part, so I'll just add one more thing: I saw a developer say in the testing room that a new release will be available shortly (based on their ETA the releases should be finished building around now, and may be released within a few hours). You can try sideloading the new release when it's available. Keep an eye onAnnouncements if you want to try.

m0ng00se

Thanks for the clarification on beta images. I got the impression from the table of the Pixel 7 release pages.

Concerning the older ota update images: As stated before, when I am in recovery, it still shows the following

google/panther/panther
14/AP2A.240905.003/2024101200

So I would think, that the update to 2024102100 didn't go through, and I am still on 2024101200...

m0ng00se

other8026 Thank you very for the hint on the possible release. I will keep an eye out!!

m0ng00se

fyi
I tried the new release... didn't work. I did a factory reset. Device is working well now. Hardware doesn't seem to be the issue.

not-so-fun-fact: after my first factory reset, I ran into the "keyboard-boot-issue" described in this post. I used the Fossify Keyboard (had OpenBoard before, which seems discontinued, therefore it isn't available in F-Droid anymore). But as others found out too, the Fossify Keyboard doesn't come up at boot. Original AOSP Keyboard was second place, not deactivated. But it didn't come up. So I had to do a second factory reset.

Now I am using Helio Board. Tested it after fresh install. Works so far.
Cheers

de0u

m0ng00se Thanks for reporting back! I'm sorry it didn't work out without a reset.