Unable to update from 2024032100

chip

I am unable to update from 2024032100 to a newer version.
The update downloads fine, and goes through verification, but the install just silently fails silently. There is no notification saying I should reboot to install the update, but I have rebooted anyway and no update is applied.

I have also tried side loading the update and it also fails with the following:

Recovery signature Verification Failed Error 21 install adb state 2
I am unsure if there is a way to fix this problem?

de0u

chip Is it possible that notifications from System Updater have been disabled?

de0u

chip I have also tried side loading the update and it also fails with the following:

Recovery signature Verification Failed
Error 21

That message might mean that the OTA image is for the wrong phone, or that the file is not an OTA image, or perhaps that some "helpful" thing on your system unzipped the file as part of downloading.

Can you indicate the name of the file and the SHA256 hash?

Is the GrapheneOS release you are currently running an official release rather than a custom build?

Blastoidea

Which phone?

chip

Sorry, it is a pixel 6a.

chip

de0u All of the notifications settings for System Updater are checked on. I get notifications from it that the update is downloading, and that it is verifying. The install notification appears, but then shortly vanishes without the bar filling up.

I have around 80gb of free space, so it isn't that either.

chip

de0u

072c638d5058988d7f8508b6b137379e25dc267644bbab702450259047f00d9b bluejay-ota_update-2024060500.zip

The GrapheneOS I am running is an official release.

de0u

chip 072c638d5058988d7f8508b6b137379e25dc267644bbab702450259047f00d9b bluejay-ota_update-2024060500.zip

I think at least one of us is doing something wrong. Here is what I see:

% shasum -a 256 bluejay-ota_update-2024060500.zip
bc13e0ce7b5a4209a65f455727200e2d3617b8d9f45e17fa813e7c8f09fbcb53  bluejay-ota_update-2024060500.zip
% shasum -a 1 bluejay-ota_update-2024060500.zip
a7d42851918e29ddca16590096f73d03c10f3ebc  bluejay-ota_update-2024060500.zip

chip

de0u I re-downloaded the zip, checked again, and got the same results as you this time. No idea what went wrong there.

I tried again to install the update via adb, and again it failed. This time however I got error 61 which is something about a corrupted device. I did take notes, but they have been scribbled over by a toddler now and I can not read them.

Anyhow, with a corrupted device I assume either something went wrong with the last update which is why this one won't install, or I have a hardware error in the storage. Either way I assume the only way to get back up to date is to fully reinstall Graphene OS again.

de0u

chip I re-downloaded the zip, checked again, and got the same results as you this time. No idea what went wrong there.

Whatever it was, the signature check stopped the device from being bricked. Good!

chip I tried again to install the update via adb, and again it failed. This time however I got error 61 which is something about a corrupted device. I did take notes, but they have been scribbled over by a toddler now and I can not read them.

If you do the sideload again I expect it will reproduce the message (which would be useful).

chip Anyhow, with a corrupted device I assume either something went wrong with the last update which is why this one won't install, or I have a hardware error in the storage. Either way I assume the only way to get back up to date is to fully reinstall Graphene OS again.

Likely, but not yet for sure. Is it possible to get the error message?

Ammako

I would strongly recommend rebooting and comparing the verified boot key hash with this before you attempt anything else.

https://grapheneos.org/install/web#verified-boot-key-hash

For the 6a, you should see 08c860350a9600692d10c8512f7b8e80707757468e8fbfeea2a870c0a83d6031 on boot.

If there is a mismatch... yes, do a fresh reinstall, but also change your credentials on any online accounts you may have used on this device.

de0u

Ammako I would strongly recommend rebooting and comparing the verified boot key hash with this before you attempt anything else.

I see no harm in that, but am curious as to why it is believed that this is a high-priority matter.

geueu

Hello i have a google pixel 8 and i am facing the same issuse and i think the only fix is erasing everything and re-installing graphene.

de0u

geueu It seems the original poster was experiencing at least two issues, one of which was a corrupted download, and overall it's not clear what was wrong since the original poster has not followed up for five months.

I think it would be best for you to start a new thread. Please describe what you have tried and what the results were, including the exact text of any error messages received. Thanks!