Week 44, 2025: Development and Testing Updates

/e/OS Smartphone Operating System Development Updates
43

As the Pixel 8 installs /e/OS using fastboot if done manually, the manual install file from the download page is not suited to be used by the updater or the recovery, they need a different install file in the OTA format.
You can get it from the OTA update server … https://ota.ecloud.global/api/v1/shiba/official/ … (download links are in the “url:” lines, note that the filename there is missing the “IMG-” prefix as a distinction compared to the manual install download page).

Be safe with a backup of everything important from the phone to somewhere safe, as usual when updating or upgrading any OS.

2 Likes
44

Did you smash the refresh button more than 5 times?

45

Smashed it a million times :smiley: No result on two different Pixel 8 devices.
I’m downloading the OTA file now and will give you feedback.
Thanks for your fast answers. :clinking_beer_mugs:

46

This morning I did the installation manually without issue on my pixel 8. I downloaded the zip with the IMG as a prefix.

47

@mngt Do you use an official build or community? For me the IMG-file didn’t work with official.

@AnotherElk Installed the OTA file without a problem! Thank you!

48

Yes official. Before installing, I flashed my pixel to the latest Android 15 from google.

49

Thank you for the hint to the OTA-file. In my case (Pixel 7, panther, official) the updater didn’t find the OTA-update either. Even after waiting and a dozens times close and refresh. I was von 3.1.1-t (last official).

Downloading the OTA-ZIP and install as “lokal update” went smoothly. Now, I’m on 3.2-a15-official.

1 Like
50

I dont know if related, but my Pixel 8 does not detect the OTA update, and I see on the ota link that the « incremental » format changed for this one (and for Pixel 7 too), but not for others like FP5
It was previously like « eng.root.20250915.225544 » (prefixed date) and it’s now « 1761127123 » (timestamp).
It’s not higher in alphabetical order so maybe it’s why the OTA client thinks that the release is not newer than the current ?
I’m trying to download the zip file and install it through the local update in the updater.

edit: no problems to update using the OTA updater and the « local update » feature, using the file on the ota cloud server

2 Likes
51

The OnePlus 9 is almost the only OnePlus device still not getting A15, but it also is not in the list of failed builds. @Manoj: can you tell when it’s coming?

Furthermore: when can we expect V3.2 on A13 for OnePlus 7 pro?

52

The v3.2 release date are till Nov 3. As mentioned in the initial post, the devices are released on a random basis. Which makes it difficult to predict when a particular device build is going to be released.

5 Likes
53

Hi Mihi - thanks for your input. I have a response from Manoj who confirms that A15 for the Murena CMF phone-1 is not ready for release yet.

Andrew H

54

I’m really looking forward to when Android Auto works again, because I need it and unfortunately it doesn’t make sense for me to switch to /e/OS before then.

1 Like
55

Hello @Manoj I tested flashing the recovery for Android 15 (3.2 Community) from Android 14 (3.2 Community) for the OnePlus 7T Pro and it seems corrupted.

“The current image (boot/recovery)/has been destroyed and can not boot.

Please flash the correct image…”

56

A post was merged into an existing topic: Week 45, 2025: Development and Testing Updates

57

My bad, I have not carefully read the installation process, so I forgot to unzip the recovery file and flashed the dtbo and vbdata files before

So I will wait for the battery to run out and flash these 2 files followed by the new recovery.

I will keep you posted.

Thanks and keep up the good work!!

58

Will check with the developers on the nature of the fix and update. Ideally it should be across all devices.