[SOLVED] Updating to /e/OS 3.2 broke my Pixel 6a

Hi y’all!

I just did the OTA update to /e/OS on my Pixel 6a. It has been working without any problems and this is also not the first update I did. But this one broke it. If I try to start the phone now, the screen tells me “Your device is loading a different operating system” Then it shows the google logo, then the little dead androidwith a red sign with an exclamation mark on the openedchest. I can still boot into fastboot mode. Is there any other option than doing a complete wipe and reinstalling? Also, does anyone know what caused this?

Thanks a million for any hint into a helpful direction!

You can try to change the OS slot to see whether there’s something bootable on the other slot, if the bootloader allows this.
(See https://source.android.com/docs/core/ota/ab for context.)

  • If not done already, download the current Android SDK platform tools to the computer and unzip the ZIP file to a folder you can navigate to easily.

  • Open a command line/ terminal and navigate to the folder to which you unzipped the tools. If you are unfamiliar with the command line/ terminal, here’s a really good and short 1 page introduction to everything you need for now … https://tutorial.djangogirls.org/en/intro_to_command_line/

  • Enter the fastboot devices command to display an ID of the phone to make sure that fastboot works with the connected phone.

  • Change the slot with the command fastboot --set-active=other

  • If the command does not complain that this is not allowed and ran successfully, try to reboot with fastboot reboot.

Ok, the wildest thing happened. I had to leave the house for a couple of hours. I left the phone plugged into the charger with the broken android symbol visible. When I cam back two hours later, it had just booted up. Thank you very much for your quick reply, @AnotherElk , sadly I couldn’t try changing the boot slots, because I definitely will not fidget around with a running system. I will mark that thread as solved, even though I don’t know if it’s a solution for anyone else…

1 Like

Ah, It also did not go through with the Update. I’m back on 3.1.4. I’ll try another Update tomorrow.

This topic was automatically closed after 180 days. New replies are no longer allowed.