Strange installation and upgrade behaviour Pixel 7

**Regain your**Two days ago, I installed e/os on a Pixel 7. Not with the installer, but manually. And it only worked with recovery version 3.1.4 and, accordingly, with community version 3.1.4—no idea why, but whatever. After that, I was offered two upgrades in a row, first to 3.2 and then to 3.3, both of which installed very quickly.

After that, I set up the device, installed my banking app, Signal, etc., and everything worked smoothly.

Yesterday, I finished the setup and was then offered another upgrade, to 3.4, dated January 16. This upgrade takes forever to download and could not be verified afterwards. When I try again, the download speed is extremely slow again. Any advice?

privacy! Adopt /e/OS the deGoogled mobile OS and online services

Wait for a week, it is now Rush hour because of the new release

Thanks! Is it usual that the release is later distributed than published? Because the date of the upgrade says 16th of january, but I was informed on the 23rd. -?

Yes, 16 is the build date,
when release started the 19 for the first set of models
and continue until the 23 for the last set of models,
also, notifications comes later (often 1 or 2 days) than the upload to servers..

Ah, ok, thank you very much!

Hi, Did you install the community or official build? If you installed the community build perhaps it better to switch to the official build. See this post

Is there a howto for switching?

I’m not sure if there’s an easy switch. I think it involves manually installing the official build and you need to backup everything. I’m sure piero knows this much better than I do. I just wanted to mention it since you just installed the os it would be a shame if you need to do it again after you setup the phone completely.

If switching from Community to Official, only relocking the bootloader (optional step) imply a factory-reset / format /data partition…

1 Like

Sorry for not beeing precise enough and thanks for your hints.

So device is pixel 7

Android version is 15

and e/os version is 3.3-a15-20251212556760-community-panther.

So is this: https://images.ecloud.global/official/panther/IMG-e-3.4-a15-20260114569178-official-panther.zip the version I could switch to?

these “IMG-” files (aka fastboot install script files) you can use for complete reinstall from scratch that is another possible option.
In this case follow :

Oops. I`d prefer to keep all my data and setup and do the above mentioned way of switching:

Do I have to take a build with the same numbers, like this one? : https://images.ecloud.global/official/panther/IMG-e-3.3-a15-20251210556408-official-panther.zip

No, you need a “non IMG” file (aka OTA file, to use from recovery mode) like :

https://images.ecloud.global/official/panther/e-3.3-a15-20251210556408-official-panther.zip
or
https://images.ecloud.global/official/panther/e-3.4-a15-20260114569178-official-panther.zip

Ah, thank you so much, I will try this and report.

Am I understanding this correctly: The local upgrade via system updater method does not work.

The recovery upgrade method fails because the e-recovery cannot upgrade from internal storage.

So the last option is via adb sideload: Is it possible to keep your data this way, or does it start from scratch?

i am surprised, it is expected to work

EDIT : because switching from Community to Official you may face a build signature missmatch.

yes, it could be not supported on Pixel

of course, just DO NOT apply Factory-reset / format /data partition.

said in both versions: error importing file (translated by myself, cause it was in german)

using a “non IMG” file ?

yes, the two you sent me the link

1 Like

you may have to confirm : “install anyway” because switching from Community to Official you may face a build signature missmatch.