Pixel 9a stuck on 2025060300

blackrose

I also struggle to install any app from the GOS app store.

I have the following error message :

Unable to install Messaging.
Details:
INSTALL_FAILED_INTERNAL_ERROR: fs-verity not set up for system package update com.android.server.pm.PackageManagerException: APK doesn't have fs-verity: /data/app/vmdl1932868590.tmp/base.apk

Divby0

It appears you are not the only one...

https://github.com/GrapheneOS/os-issue-tracker/issues/5560

GrapheneOS

Divby0 That was an issue with updating Vanadium specific to certain early Pixel 9a releases. It didn't cause any issues for OS updates which are tested for each release prior to Alpha. It was an issue for system app updates and was quickly fixed.

Ammako

Are you able to try to manually sideload the newest release via usb and see if that resolves your problem?

https://grapheneos.org/usage#updates-sideloading

Do you need help with doing that or do you think you're able to figure it out on your own?

https://grapheneos.org/install/cli#cli-install

This is for setting up the command line tools, you don't need to follow all those steps and unlock your bootloader again (doing so would wipe all your data!) You just need to get the command line tools working, and once you are able to use adb with your phone connected to your PC, you can use adb sideload to install the update zip while in recovery.

blackrose

Ammako

Many thanks Ammako.
Side loading the update with adb did work !

GOS21606

Ammako

This works only when you can access your phone and you activate USB debugging.

How can you do side loading with USB debugging off and for example when you are in a boot loop?

My phone has by default: USB debugging off and USB-C port to Charging-only

GrapheneOS

blackrose Make sure you haven't disabled notifications for System Updater. That appears to be what you did because it provides all feedback about what it's doing and errors via notifications. We plan to prevent fully disabling notifications for it.

Divby0

Thanks for clarification.

de0u

GOS21606 This works only when you can access your phone and you activate USB debugging.

How can you do side loading with USB debugging off and for example when you are in a boot loop?

Sideloading does not require USB debugging, as explicitly documented: https://grapheneos.org/usage#updates-sideloading

userofgos

GOS21606 and USB-C port to Charging-only

This is most likely your problem. Change your USB-C port settings to "Charging-only when locked, except before first unlock" and then you should have no issue with sideloading without USB debugging (as de0u said is NOT required and also NOT recommended)

userofgos

n3t_admin Sorry, but what has any of that to do with sideloading? GrapheneOS doesn't influence how fastboot works. The USB-limitations are OS-level, not firmware-level.

I was replying to GOS21606 in reference to the following comment.

GOS21606 My phone has by default: USB debugging off and USB-C port to Charging-only

As de0u mentioned I didn't clue into the bootloop comment. I guess I also assumed that the USB-C port setting in the exploit protections would affect that. My mistake, I see the documentation is clear on the website which I quoted below with added emphasis.

Our USB-C port and pogo pins setting protects against attacks through USB-C or pogo pins while the OS is booted. For the majority of devices without pogo pins, the setting is labelled USB-C port.

GOS21606

de0u When I tried side loading on my old 4a I can not send any command like: ADB reboot recovery or ADB devices to the phone when USB debugging is switched off?

When I switched to USB debugging on I can finish the whole procedure including uploading the zip file.
I know I can reboot the phone in recovery mode without this command using the boot loader interface but the procedure says you can use this command (ADB reboot recovery) or selecting this option in the boot loader interface?

Maybe it is different on this obsolete phone I have not tried it on my newer ones.

BTW: I use a Linux machine and the Terminal window.

de0u

GOS21606 When I tried side loading on my old 4a I can not send any command like: ADB reboot recovery or ADB devices to the phone when USB debugging is switched off?

That is not surprising.

GOS21606 I know I can reboot the phone in recovery mode without this command using the boot loader interface but the procedure says you can use this command (ADB reboot recovery) or selecting this option in the boot loader interface?

If USB debugging is off, I would recommend booting into Recovery manually (using the buttons).

Sideloading is designed to work without USB debugging being enabled, and it does.

n3t_admin

GOS21606 I can not send any command like: ADB reboot recovery

and you don't need to. This part is only for the users who have USB debugging enabled. For everyone else, you can get there as per the guide:

by selecting the "Recovery" option in the bootloader interface

after that you follow the instructions:

You should see the green Android lying on its back being repaired, with the text "No command" meaning that no command has been passed to recovery.

Next, access the recovery menu by holding down the power button and pressing the volume up button a single time. This key combination toggles between the GUI and text-based mode with the menu and log output.

Finally, select the "Apply update from ADB" option in the recovery menu and sideload the update with adb. For example:

`adb sideload raven-ota_update-2021122018.zip``

and that's it. That's the official, recommended way. This works without developer options enabled at all.

userofgos Change your USB-C port settings to "Charging-only when locked, except before first unlock"

Sorry, but what has any of that to do with sideloading? GrapheneOS doesn't influence how fastboot works. The USB-limitations are OS-level, not firmware-level.
Edit: it was literally the next sentence in the guide lol

Our USB-C port and pogo pins setting protects against attacks through USB-C or pogo pins while the OS is booted.

de0u

userofgos Though if the device is in a boot loop then changing the USB port setting isn't going to work.

Booting into Recovery with the buttons should work.

de0u

In general there is a difference between:

I have followed the directions on the GrapheneOS web site and I am still stuck (this can happen!), versus
I have tried things based on what I used to do when I was running LineageOS back in 2008, or based on something I saw on TikTok.

If the GrapheneOS web site needs to be improved, it can be improved. It is not clear it is possible to improve TikTok.