This topic was automatically closed after 68 days. New replies are no longer allowed.
Hi all, another update/info: it did work for the Samsung Galaxy Tab S6 lite (SM-P610 / gta4xlwifi). I upgraded from /e/ 1.19.1 (Android 12 / S) to /e/ 2.4.1 (Android 13 / T; e-2.4.1-t-20241009439852-community-gta4xlwifi).
@piero thanks for the thread – I had the same question and did not find it because of the title – maybe make it a bit clearer so that people can find it? (e.g. something along the lines of: upgrade android version directly from recovery (without flashing firmware, “dirty upgrade”)’ … i don’t know 
– the problem is that most won’t know that this process is called “dirty upgrade”). cheers!
HowTo perform a dirty upgrade to “/e/OS-T” from a previous /e/ version ?
→ it is as simple as a dirty update…
there are multiple ways :
- download the file, go to " → settings → system updater" and use the called “locale update” feature if you have it in the “3 dot menu”.
OR
- download the file, boot the phone to the recovery mode and use “apply update” then “from internal storage” if your “recovery mode” have the feature.
OR
- download the file on a SDcard, boot the phone to the recovery mode and use “apply update” then “from External SDcard” if your “recovery mode” have the feature.
OR
- download the file on a computer, boot the phone to the recovery mode and use “apply update” then “from ADB” :
Install platform-tools on a computer
Installing adb and fastboot on a Linux PC
Installing adb and fastboot on Windows PC
On the computer,
download the latest /e/OS-T build for your device
(put it into the platform-tools folder)
.
Boot the phone into recovery mode.
.
Select Apply Update, then Apply from ADB
The screen should now change and the output at the bottom ask you to send the package from your computer.
On the computer,
Open a terminal from the /platform-tools folder, and
issue command to sideload the latest /e/OS-T installation zip.
adb sideload e-2.4.1-t-20241009439852-community-gta4xlwifi.zip
the phone screen will be mostly blank with just the output at the bottom showing progress.
(Do not pay attention to the wipe related things on this photo that came from the full install from stock instructions !)
On the computer the sideloading shows progress as a percentage figure that will stop at 47%. The phone will still be installing though (even though it might feel like nothing is happening sometimes!) and you can expect to see the following screens (excepting the wipe related things)
Then press the arrow at the top of the screen to return to Home Screen
Tap Reboot system now to boot into eOS.
4 Likes
I just installed /e/OS 2.5-t- (Android 13) on a virgin Oneplus 7 pro with Oxygen OS. The GM1911 phone was on Android 11. Steps were:
- reset the phone to factory settings
- OEM unlock and unlock bootloader
- Upgrade to latest OxygenOS (Android 12)
- Followed the Install /e/OS on a OnePlus 7 Pro - “guacamole” guide for /e/os T (Android 13)
- done
All went smooth and fine. OP 7 pro is now running the latest /e/os.
Does anyone know if this tutorial applied to A14 too ? If i have a A12 phone and i want to upgrade it to A14, what can i do?
Did you consider the S → T upgrade by this method ? One version at a time is probably safer.
I would suggest that the majority of ROMs will contain the vendor parts found in T builds, but one would be best to check by the methods mentioned at the top of the thread. [1]
With a serious backup strategy I had no hesitation in upgrading to U (testing – I cannot say more) without format data or wipe, if advising someone though I would suggest check for the presence of vendor parts first.
[1]
1 Like
It depends on the phone. Some phones can be updated with a 'dirty flash`, others need a factory reset / data wipe before upgrading. The need for factory reset seems to be more common when upgrading to Android 14 , than with upgrades to earlier devices.
Look at the LineageOS Wiki page for your device: there will be a section on upgrading
https://wiki.lineageos.org/devices/
EDIT:
Also worth noting that dirty upgrade may be possible in /e/OS, even if it is not possible in LineageOS. Ask in this forum stating which device you are using
Hi,
Thanks for this helpful guide.
Unfortunately, it doesn’t work with my FP3+… Or i missed something.
The context: i realized some weeks ago that my FP3+ (bought in 2021 on /e/ os website, installation with the easy installer) didn’t propose me updates since the 1.19.1-s-20240109372023-stable-FP3 release (yes, it took me a long time to realize it 
). Even if i force the manual checking more than 20 times, even with advanced privacy on or off. And the App lounge can’t be able anymore to show, install or update apps, but it’s another problem (seen in some dedicated topics).
I followed advices on some topics on this forum, for example this current one, or Update from 1.19.1-s to 1.20-t on beyond2lte, or [HOWTO] an Unified Install Guide Project for /e/ steps 8 and 9 (english and french versions).
I tried to apply the dirty upgrade process by myself.
At first without computer, by recovery reboot.
there are multiple ways:
- download the file, go to " → settings → system updater" and use the called “locale update” feature if you have it in the “3 dot menu”.
I don’t have this menu…
OR
- download the file, boot the phone to the recovery mode and use “apply update” then “from internal storage” if your “recovery mode” have the feature.
OR
- download the file on a SDcard, boot the phone to the recovery mode and use “apply update” then “from External SDcard” if your “recovery mode” have the feature.
When I reboot in recovery mode, then select Apply Update, it doesn’t propose me neither “from internal storage” or “from External SDcard”. I have only “Apply from ADB”. I don’t understand why. Any idea?
OR
- download the file on a computer, boot the phone to the recovery mode and use “apply update” then “from ADB”
So, then I tried with ADB, installed on my linux mint 21.3 machine (fastboot too). The installation went well. I put the Debogage USB “on”, in dev options menu of my phone (i don’t know if it’s necessary, but in doubt…).
The command on the terminal adb devices returns one device (my FP3+ i guess), so it sounds good. I downloaded on my computer the last <file2.5>.zip for FP3.
When i launched the recovery reboot, then selected Apply update / Apply with ADB, the connection between my phone and my computer breaked down (a popup appears "Impossible de monter FP3 - Impossible d’ouvrir le périphérique MTP “003.021” " and on the terminal the command adb devices returns that my connected device is “unauthorized”.
And on my phone there is this error:
What did i missed?
I haven’t installed the Platform Tools. Maybe should i try to do with it? how can this change something?
I think i don’t have TWRP and it seems to me really harder to use… But could it be a solution?
If i understand well, there’s no need to do factory reset, and the loss of data would not occur by thy way, right? I’d rather not to have to do this.
Another question that i wonder: is that safe to update my FP3+ from 1.19 to 2.5? It’s a huge step!
I hope my message is clear. I’m not a developer, it’s a little difficult to me to do this by my own. Thanks in advance for help!
As there are a number of people with this problem with Fairphone official=stable builds where the OTA Android version upgrade failed to happen. I assume (but you don’t mention) that you likely have a locked bootloader.
I think that you should prepare yourself for a Format data and reinstall, that is ensure you have a good backup strategy.
Maybe we can help find a solution but we know that the System updater does some special magic for the Android version upgrade. Maybe the magic is in the before and after builds. These “historic” builds are not available due to the the outage from which we are not fully recovered.
1 Like
You may need this file : e-2.5-t-20241111446629-official-FP3.zip, not the IMG-e-2.5-t-20241111446629-official-FP3.zip one…
2 Likes
Thanks piero for the file. Where can I get it and the next updates?
Thanks aibd for the feedback, it’s a bit discouraging for me. I didn’t specify for the bootloader because I don’t know how to know if it’s locked or unlocked (we’re reaching the limit of my technical knowledge 
). What I can say is that I don’t have access to the hidden system files on my file manager, I’m not root. What would be the procedure for unlocking the bootloader? That’s probably a good idea.
My (regular) backup strategy is limited to saving the data I have access to in my file manager (internal storage) including Android’s “data”, “media” and “obb” folders. I imagine that won’t be enough. And I guess I’ll have to root my FP3+ to be able to make system backups?
Thanks in advance for help!
There’s no /e/os T rom currently existing for the S7… That’s why i wanted to know about directly switching from S to U. We still don’t know which murena devices will get it, so i prepared in case of.
Besides, the last vendor patch for S7 was created in 2021… So i don’t think the vendor will cause any trouble when i’ll upgrade.
I don’t think so as S7 is no longer maintained…
Yes, you can dirty-flash as well, latest /e/ “S”, “T”, or “U” version over your existing “S” based system.
1 Like
This can be determined easily from the bootloader screen, the screen with big green “START” at the top. The bootloader is reached from
Shut off your phone and press Volume Down + Power Button
If the phone is locked and you unlock it, the phone will have all data wiped.
This HowTo [HOW-TO] Flash /e/-OS on Fairphone 3 using Debian based GNU/Linux explains with images.
@piero linked the OTA update file which is quite different from the install ROM which you had linked.
The OTA ROM might work in one of the methods here …
but the install ROM is not made for this … the main a plausible reason for your fail.
Platform-tools would allow you to try Method 4.
On Fairphone 3 use of TWRP is an expert solution and sure to give problems while the bootloader is locked.
That would be correct if you could apply the OTA upgrade ROM successfully without any need to format or wipe data (as this thread proposes). Edit Beware that one could be put in a position where you format data (while hoping to avoid). So have a backup of essentials.
This is significant … and a good reason for caution.
1 Like
So if my phone gets the update, the only thing i need to do is just flashing the ROM without any kinds of wipe ? No data loss? Sounds great!
1 Like
Yes according to last upgrade experiences (since android Q 10)
BUT you may have to format /data partition IF there are major changes in the device-tree used to build android in the future.
There is [UNOFFICIAL BUILD] Samsung Galaxy S7 / S7 Edge / Note 7 for /e/OS-T - #5 by ronnz98
1 Like
And is it the case ? Is there a known change in the device tree ?
I don’t know the future…
1 Like
I just successfully upgraded my Fairphone 3 from e/OS 1.17 to 2.5 and this was the missing piece. Thank you! Where did you find the link to that file? I was only finding the IMG-* files on the official download pages, and those were not working with the adb sideload.