I have an FP3 running e/OS 1.17-s-20231111351092-dev-FP3.
The updater keeps saying there is no update available.
I tried to wipe updater’s data and to spam the refresh button but the issue persists.
I am surprised since e.g.v1.18 for Android 12 has been available since December 2023.
I am aware that OTA upgrade for Android 13 is not ready yet, still there have been numerous updates for Android 12 since then.
I extensively browsed related topics but have not found a solution.
Can you point me in the right direction ?
the phone screen will be mostly blank with just the output at the bottom showing progress.
(Do not take attention to the wipe related things on the photo ! it is a “second-hand” photo…)
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)
A quick note to say that updates through ADB are to be found there : https://ota.ecloud.global/api/v1/<model>/<version>, e.g.https://ota.ecloud.global/api/v1/FP3/dev.
Hi piero
This sound like the solution I am looking for, thank you very much for your detailed description.
Just for clarification: You mentioned “ignore the Wipe part” twice. Does this mean, your update/upgrade solution works without any app data and personal data loss?
But yes, there is no data loss expected when performing “dirty update or upgrade” untill you don’t wipe or format the /data partition or unlock or relock the bootloader that is a “clean install or upgrade”…
I have the same problem with a FP3 (stuck on 1.17 forever). However, when I sideload the update via ADB, the recovery mode tells me that the sideloaded ZIP does not contain the update binary. I tried with both official 2.4.1 and 2.7 builds.
I saw that when looking at the OTA build endpoint (Builds – Django REST framework) all recent builds have set "is_upgrade_supported": false. Is having a build that is_upgrade_supported == True important for a successful sideloading process? How do I get an official ADB-Upgradeable image?
What also didn’t work: I tried “sidejumping” this issue by first building some 1.x version myself and then providing the official OTA URL, but this did not work as 1. i wasn’t able to build any version larger than 1.21 using the recommended docker setup and 2. i wasn’t able to provide an OTA URL that the repository would take as working.
I now noticed that I was trying to use the IMG prefixed one, and not as mentioned above the one without.
Now using that non-prefixed file worked perfectly for sideloading.
Do you know whether it would be possible to somehow mention this difference on the Build download page (/e/OS official FP3 download), and maybe also directly link OTA / update builds there? I think this would have saved me quite a bit of time.
Using ADB sideload to install or update is not officially documented or endorsed on FP3 (even if it might work, but there’s no guarantee), so I doubt it will get mentioned in official documentation.
Unless the official way to install gets changed, the probability for which is not zero.
it is the traditional way to install and update replican, cianogenmod, lineageos !
built-in system updater do that way…
although if you decompress the OTA file you optain the same /partitions.img than in the IMG container, except the userdata one…
.
to go in your way @AnotherElk , i need to verify for recent devices (i just replace my FP3 motherboard, so it is an opportunity), but in the FP2 install-script the code ask if you want to wipe userdata or not, so the IMG container may be used to update too, i can’t remember it is documented…
as i understand official indication the way to upgrade is to lose data, even if we see for years that the official documentation was always unclear or inacurate.
edit : this is part of the FP3 script :
# Warn about data wipe, and ask for confirmation
data_wipe_check() {
if [ "${CLEAN_FLASH}" = "true" ]
then
echo ""
echo "WARNING: Flashing this image wipes all user data and settings on the phone."
echo " Are you sure you want to wipe data and continue?"
echo ""
# Read user's input
read -rp " Type \"Yes\" (case sensitive) and press enter to wipe data and continue. Else, just press enter: " a
echo ""
if [ "_${a:-"No"}" != '_Yes' ]
# NOTE: $a is being set by the read command above,
# so the check for a to be set is mostly redundant
then
echo "WARNING: You DID NOT type \"Yes\", proceeding without data wipe."
echo ""
CLEAN_FLASH="false"
else
echo "WARNING: You typed \"Yes\", proceeding with data wipe."
CLEAN_FLASH="true"
fi
fi
}
I just said why in my opinion ADB sideloading will not be mentioned on the official install pages for FP3, unless /e/OS developers themselves decide to switch to this install method on FP3 .
I don’t have anything against ADB sideloading on FP3, I’ve done it myself, but I’m aware it is not the official and documented way on FP3.
There shouldn’t be much harm done with regular updates within the same Android version, as you correctly pointed out the updater itself uses OTA install files in a comparable way.
I don’t have much against “dirty” upgrading the underlying Android version this way either, I’ve done it myself, but I’m aware I could be in for a new install or a factory reset anyway, if the upgrade doesn’t work out as intended, which can happen. The key is to be aware and prepared.
Yes. There’s no fault in that, it’s the clean way, causing the least trouble overall.
I’m aware it’s inconvenient, I worked around it myself from time to time, too. But it’s still the clean way, causing the least trouble overall.
If official documentation is unclear or inaccurate, it can be fixed in the place it is … Documentation Suggestions - /e/OS community
Forum posts can be unclear or inaccurate, too, or get outdated over time. Have fun fixing those.
i first used the official way to install 2.5-t over stock Fairphone OS
Résumé
the script let me choose to format /userdata or not but decline leads in a non booting system because of stock /userdata, device self-booting in recovery-e, so i did the factory-reset and my phone boot normally. after the fist settings menu, i made my additionnals minimum settings (what i musn’t have to do on a real user-respective OS) and just toke a random photo to be sure there a thing from me in internal storage.
then i used the official way to install 2.6.3-t over 2.5-t, the script let me choose to format /userdata or not and its true : i can update and find my photo
2.6.3-u and 2.7-u have the flash-script but abort because missing files
both are unusable following official instruction
Even usable using fastboot flash each partition
Curious … downloaded December 31, script is there …
It was even acknowledged that the images in the archive didn’t match the script in the archive, the script got corrected by commenting out all flash commands that couldn’t succeed (Perhaps they removed the script now to let people do the correct flashing if they know how, or let them search for the solution here?) … Week 3, 2025: Development and Testing Updates - #2 by Manoj
Seeing as the same set of images is provided as before … Is the corrected script in the archive, or is it the faulty old one, trying to flash partitions which are not provided?
.
