Did you check the OTA Uodate?
I was offered an OTA Update for my phone (Fairphone 5). The only point was, that the offered OTA update was still Android 13 which didn’t bother me to much.
I also understood, that one if the next OTA updates will be Android 14. I just wait and have not to bother with the manual procedure.
Oliver
Sorry not to be a real geek but it is possible to return to the previous version?
I’ve no phone since 10 days and I really need it. As I upgraded v2.6.3 I cannot use my esim.
I not sure to want and to be able to put an other OS on my FP4.
I’ll really appreciate a solution before the next version.
PS. What is OTA?
Hi,
OTA means over the air. But as you have already upgraded, there is no way back without manual flashing.
If you are not confident enough to do this by yourself it is better to wait for the fix for your esim problem. You can brick your phone when going back to the older version if the bootloader is locked.
Best regards
Oliver
Thanks.
I think I’ll wait because the previous version didn’t allow me to use the 2 sims (physical sim and esim) at the same time…
I hope this will be fixed
Device:
I’ve installed the update on 23.12.2024 before it was pulled.
With Spotify installed in the Work Profile managed by Shelter I ran into the issue of the app crashing the whole device when playing anything.
The workaround provided by @rikshaw solved this for the time being.
I also had some trouble with KISS-Launcher frequently not working properly: The searchbar wouldn’t respond and the app needed to be restarted to work again. This seems to be caused by some new restrictions enforced by Android 14.
To fix this I enabled KISS Launcher in “Settings → Accessibility → Downloaded apps”. Apparently another workaround is to install the app via F-Droid which uses another install-method where the restrictions in question aren’t enforced.
I found those workarounds here: Kiss launcher freezes on my Pixel 8 · Issue #2308 · Neamar/KISS · GitHub
Thanks for the continuous updates and a happy new year (albeit a bit late)!
That only applies if you have official build…
Hi @olli0371
yes, I have checked, and there was not. As I could read from some replies I have received above, OTA should not happen on “community versions” of /e/OS for upgrades from an Android version n to n+1 on devices not sold by Murena (which is my case, from A13=T to A14=U for a Samsung Tab S5e).
I do have another device (Sony XA2) where the OTA upgrade to A14=U is available, and there, I will try to do that as soon as I have understood how to upgrade the Samsung Tab S5e, so that, if something goes wrong, I can fix the Sony XA2. This is important to me, since the Sony XA2 is actively used as phone, whereas I can bear some disruption on the Samsung tablet without too many issues.
Thank you for your reply and understanding
I am still waiting for this update. Any reason why I do not see it on my (AFAIK still supported) Oneplus 7t pro @Manoj ?
Version upgrades (in your case T-> U) for community builds are not offered OTA.
New builds for your device : /e/OS community hotdog download
Ah, missed this was a version upgrade. Need to dive into upgrading then…
(Mean while searching for the links…)
Motorola
Edge 20
Berlin
Upgraded from previous version ( e-2.5-t) via adb sideload in recovery
Not rooted
No issues whatsoever upgrading manually this model. Working fine!
Motorola
Moto G 5G Plus
Nairo
Upgraded from previous version ( e-2.5-t) via adb sideload in recovery
Not rooted
Been using this phone on /e/OS for over a year and a half. It has been a top notch experience and I highly recommend this phone for /e/OS it is very stable and everything works excellently, wifi calling even works too! This was the first time I ran into an issue doing the manual upgrade on this model. When you upgrade version e-2.6.3-u via adb sideload then do the first reboot the phone will get into /e/OS for a a few seconds then freeze and then just get stuck in a boot loop. The only way to get out of it is to go back into recovery and to restore to factory settings. In other words you will lose all of your data if you do the upgrade. So save all of your data before you do it. I had this confirmed by a friend who has the exact same model phone (Motorola, Moto G 5G Plus Nairo). I guided him through the upgrade, and exactly the same thing happened to his phone as what happened to mine, it gets stuck in a bootloop after the upgrade and you have to restore it back to factory settings in recovery. Unlike me my friend backed up all his stuff as I advised him to do so.
Having said the above, the phone is working fine and is stable with no issues once you do the fresh install of version e-2.6.3-u
Updated to : 2.6.3-t-20241217455358-official-panther (e_panther-user 13 TQ3A.230901.001 eng.root.20241217.053446) using OTA
Straightforward process : notification then click on update then wait for about 10 minutes to download/upgrade/reboot.
First tests are all OK :
Congrats and thanks !
Vendor Name: OnePlus
Device name: 8T - variant KB2003
Device CodeName: kebab
Used the latest OOS 14 sideloadable firmware flasher zip from Wishmasterflo (https://github.com/Wishmasterflo/Firmware_flasher ) to get the firmware right and performed a “dirty” system upgrade (via a bootloader/fastbootd procedure):
Everything stayed in place and works as before!
So this was really a straight and easy upgrade …
Many thanks to the team!
Update went smoothly and everything seems to be working without issue.
I must have looked at the release notes too quickly, because I expected this to update to Android 13, but I’m still on A12. From hte Teracube forum I know it can be updated to 13 now. Part of the reason I purchased from Murena was so it would be kept up to date and I wouldn’t need to mess around with it myself. Is there a plan or timeline for the Teracube phones Murena sold to get updated to 13 sometime in the future?
Does @Manoj or anyone else know about that?
Thanks!
I store pictures on the SD card at the moment. That information was missing in my post.
I’m not an expert. I guess so.
I would suggest to copy like documents, music and picture to an sd card, this wasn’t wiped or copied by usb cable to a pc/usb storage. SMS and WLAN was backedup by Seedvault.
Some banking apps need to be reinitialised or transfered to a 2nd Smartphone and the retransferred after Upgrade.
Apps like Signal with their own back up should be backed up on their own.
Vendor Name: Fairphone
Device name: FP4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: v2.5-t-...
The device is Not rooted.
The update was smooth. All Apps seem to work despite the message of some apps that they are not designed for Android 14.
Now I faced a problem with miracast / screen cast. When I try to activate it, it dos not work and often a message appears: “Wfd Service keeps stopping”, the TV shows a symbol that the device is connecting, and the screen cast icon appears on the Android device, but the connection does not happen. Some time later the symbol on TV disappears and the screen cast icon disappears at another time.
In summer and autumn the miracast worked perfectly.
Vendor Name: Xiaomi
Device name: Poco X3 Nfc
Device CodeName: Surya
Version of /e/OS which existed previously: 2.5.3 T
Is the device rooted: not rooted
“Dirty” upgrade via recovery and adb sideload. Updated to 2.6.3 U.
Everything working good.Thank’s .
See here, does not exactly refer to 13 but to murena devices (~ phone models sold in the shop) in general (13 may even be skipped if technically possible):