Hi @lubosak, welcome to this forum.
There are no problem for traditionnal devices, because first installation, updates and upgrades follow the same process (via recovery) and use the same file…
Only few phones included Fairphone since the model 3 are using a fastboot install script and an IMG.zip folder for new installation,
i don’t understand why the recovery-compatible file needed for updating or upgrading is simply hiden, specially on the ota server
Because it’s not officially “needed” on the Fairphone 3/3+, the install instructions use the officially downloadable files (for fastboot, not for recovery use).
The update procedure via the recovery in case of the Fairphone 3/3+ is inofficial and undocumented (apart from the forum). It may work, it even should work technically, but there’s no guarantee.
Hi piero,
I’m taking advantage of the calm of the vacations to dive back into this problem. The fact that lubosak has succeeded with this new file gives me hope!
Could you please point me to the url where the aforementioned e-2.5-t-20241111446629-official-FP3.zip file is stored?
On each of the two links you mention (images.ecloud.global and ota.ecloud.global), the .zip file names don’t match (there’s always the IMG-* prefix), and their MD5 doesn’t match this file either.
Thanks in advance for your clarifications!
Happy New Year!
https://ota.ecloud.global/official/FP3/e-2.5-t-20241111446629-official-FP3.zip
https://ota.ecloud.global/official/FP3/e-2.6.3-t-20241217455358-official-FP3.zip
I confirm the “dirty upgrade” worked on my OnePLus 6T.
I went from /e/os 1.17 to 2.6.3-u-community
Recovery went perfectly well
Hi Edouard,
I’d like to do a dirty upgrade on my Oneplus 6T running /e/os 1.8 to go to 2.6.3-u
As it works for you, can you please share the procedure you followed? Which files did you used?
Thanks a lot
Hi @jamio, welcome to this forum.
https://images.ecloud.global/community/fajita/
Upgrade to T have worked without dataloss on OnePlus 7,8,9 devices
Hi Piero,
Thank you for your reply
So if I get it well I just need to download the zip file from the link you gave and then update from the recovery
The version of the recovery does not matter?
Thanks again
I think this is the reason that @piero asked you to tell us the full_version_string of the build you are currently running. "[HOWTO] Give complete /e/OS version … " is a link above.
Sorry I did not get it.
Here is the full version string
1.8.1-r-20230206257804-dev-fajita
Thank you very much for help guys
./payload-dumper-go -l e-2.6.3-u-20241218455570-community-fajita.zip
Please wait while extracting payload.bin from the archive.
payload.bin: /tmp/payload_344338513.bin
Payload Version: 2
Payload Manifest Length: 119371
Payload Manifest Signature Length: 267
Found partitions:
LOGO (8.0 MB), abl (2.2 MB), aop (184 kB), bluetooth (766 kB), boot (67 MB), cmnlib (381 kB), cmnlib64 (500 kB), devcfg (41 kB), dsp (34 MB), dtbo (8.4 MB), fw_4j1ed (352 kB), fw_4u1ea (352 kB), hyp (397 kB), keymaster (221 kB), modem (120 MB), qupfw (66 kB), storsec (25 kB), system (3.0 GB), tz (2.1 MB), vbmeta (4.1 kB), vendor (1.1 GB), xbl (3.3 MB), xbl_config (98 kB)
as the build seems to include firmware parts, upgrading Oneplus 6T (farita) should works without dataloss from R to U following one of the three methods described in post 24
using the build from /e/OS community fajita download
about Samsung Galaxy A52 4g (a52q)
it is the same for the U build, it don’t include firmware parts, so
Then you will be abble to upgrade to /e/OS-U without dataloss following one of the three methods described in post 24 using the build from /e/OS community a52q download
Hi,
I finally got time to test the update and it indeed works perfectly.
Thank you again for your help
Hi Everyone,
I am new here, and have the same issue as many it seems, an e/OS version stuck at 1.17, with the automatic updater not finding any newer version.
Here are my phone’s data :
Phone : FP4
Version d’ Android : 12
Version /e/OS : 1.17-s-20231109350748-stable-FP4
If I apply to my case what I read above, I should simply download on my phone the latest /e/OS version here : https://images.ecloud.global/dev/FP4/ and see if that appears directly in the system updater’s, or one of the 3 options @piero described earlier in the chat?
Does that seem correct ? Is there any specifities for fairphones?
Thank you for the help
recently (six months ago), “dev” became “community”, when “stable” became “official” !
as you already running on “stable” branch, (e-1.17-s-20231109350748-stable-FP4) now called “official” branch,
So, no, you don’t need the “IMG-e” file community release, that is designed to “first time install” :
https://image.ecloud.global/community/FP4/IMG-e-2.7-u-20250110460550-community-FP4.zip
you need the “OTA” file official release, that is designed for “update” or “upgrade” :
https://ota.ecloud.global/official/FP4/e-2.7-u-20250109460370-official-FP4.zip
Yes, Very Specific Case of the Fairphone and other devices with “IMG” containing install-script files :
Yes, @piero has explained it, but here in different words.
Normal download install files for fp4 are named with a leading IMG. You cannot use them for this method. You need the OTA_PACKAGE as has been listed, no IMG in the filename.
It is advised not to change build types. You are on stable=official so best avoid community=dev.
The hashtag fp4 will point to specific user experiences with this phone.
Thanks very much @piero ans @aibd, just did it and it worked perfectly.
I used the link provided, and the process 3 : stored the .zip file on my sd card, booted the phone on recovery mode and updated from the sd card.
No data loss, all apps and app lounge are up to date and working fine.
Thanks very much =)
