It has been published, it is a community build, it is Android 14 (U) so using it will entail a manual upgrade.
So there is no OTA right?
As there is not an official, but only a community build, there will be no OTA upgrade from /e/OS T to /e/OS U for miatoll, unfortunately.
2 Likes
After the manual update to the community version, will I be able to perform the updates OTA or will they all require manual labor from now on?
Community=dev, the naming convention changed, always get OTA updates of /e/OS version (say about monthly) but Android version Upgrade has to be done manually.
Only official=stable builds have ever received OTA Android version Upgrade.
5 Likes
One question: does this mean those will be the first to get eOS 2.7? I don’t see the Moto G7 Power (ocean) listed there. Is it because it won’t have a 2.7 build yet, or because it won’t get one at all?
The ocean is already on /e/OS U . You can download the build here
This list contains the names of devices for which we have been able to make U builds for. It does not mean that the devices which do not show up here will not get u builds in future. We will work to upgrade the builds for all devices where it is possible.
5 Likes
Hi, I have a Google Pixel 5 with official Redfin v. 2.7 T installed with AOSP 13 and I would like to upgrade to e/OS U with AOSP 14 maintaining all the app and files installed: is it possible? What’s the procedure?
Thanks
Paolo
I cannot say for sure for official T → community U on the same version …
Least for me (Pixel 4a community T version 2.6.4 → community U version 2.7) and others the adb-sideload approach worked well:
That approach seems to be somewhat “reliable” for many models (browse the forum for “dirty upgrade”) … but: No guarantees (!) and not sure if there´s anything special to be considered in your case beforehand - besides backups of important data and settings.
I am sure others will jump in with insights as well …
Of course You´d need to adopt the correct file: redfin/e-2.7-u-20250111460593-community-redfin.zip
Thank you very much.
I tried with adb-sideload, but I receive the message on the phone “Signature verification failed” and the upgrade doesn’t work
Could check MD5sum or SHA256sum after download be the problem? How can I sign the .zip file?
Could you please check your actual build? Is your bootloader locked?
Settings → ‘About the phone’ then there is the e/OS/ version
Looks something like this: 2.5-t-20241108446630-community-sunfish
The dirty upgrade method does not really support change of the Different Build Types from official to community. That would be quite likely to cause
2 Likes
Thanks for pointing that out!
I’m sorry it can’t be done. I hope the official build will be upgraded to AOSP 14. Thanks for your support
1 Like
The official advice is to treat such a move as a new install. Did you activate the Seedvault backup Settings > System > Backup ? I do not remember seeing a review of Seedvault backup in Android 13 (T) and I have not had call to use my Seedvault backup myself. Some have commented that it does not backup everything but it does declare exactly what you can expect omitted. One should always plan a backup strategy – anything might happen!
With a sound idea that you have a backup, and I suggest uninstalling all non “essential to keep” apps you may eliminate the error by following the install page Install /e/OS on a Google Pixel 5 - “redfin” installing by fastboot community_build_recovery etc, but with the intention of avoiding any wipe or format of data, before
adb sideload downloaded_file_name_community.zip
I cannot judge the exact chance of success as it is unknown to me the exact divergence of official and community with any specific build; it is possible that the device will ask or require you to format data.
But @obacht you have passed from T (official version) to U (community version) right?
Yes I did a backup of all before trying the upgrade. With ADB sideload the upgrade from v.2.7 redfin T to v.2.7 redfin U doesn’t work for signature verification failed. With fastboot the problem is the bootloader locked…
That is the problem then; unlock will Format data for sure, then you will be forced to a Clean install.
Before official builds can be published for any officially supported device, the community build will be effectively further tested by community users while devs work on the OTA Upgrade of Android version. This will be unlikely to be “quite soon”. However T remains stable.
See the relevant section (near the bottom of the post each week) Development Updates. There is no indication that “Testing” is under way for any official Android 14 (U) build.
OS OTA Related information
The subsection Testing is currently empty.
1 Like