My FP4, which has been running for 2 years without any problems (/e/OS & hidden Magisk with root for AdAway, NeoBackup, BusyBox, …), can now neither OTA nor manual update (“the update check failed…”), because in my guess the “current version” that is otherwise always necessary for update comparison is suddenly gone. The version would have to be updated from the last OTA
2.9-a14-20250321478214-official-FP4
build number e_FP4-user 14 AP2A.240905.003 eng.root.20250321.130437 corresponds to this.
Apart from the mystery of how it was deleted, I want to get OTA updates up and running again.
Since I can hopefully re-enter the string for version with BusyBox or adb shell (root) to fix it, I’m currently looking for where this config file is located in /e/OS.
Alternatively with new installation, I have no experience with sideload system updates, I want to avoid deleting all installations on the FP4 at all costs.
I’m grateful for any tip…
Just for information, this link Feedback for v3.0 - #203 by nicofonk describes a method suitable to adb sideload an updated image (hopefully without loss of data, but backup essentials before any intervention).
- on “a phone with a problem”
- a phone like an fp4 where only an Install ROM is published and documented, that is there is no “manual update” documentation.
Edit. adb sideload is the old school way to do an “everyday” manual update where userdata is not impacted.
Edit 2. The above method includes the way to strip IMG- within the Install-filename url. (Easy when it is explained well there). You can alternatively collect an OTA_PACKAGE from ota.ecloud.global/api/v1/FP4/official to find your downloadable image please search for "url".
Edit 3. I did suggest a non-sideload method but using the Updater (if it is competent for you) here Feedback for v3.0 - #521 by aibd
there was a patch a month ago to hide some system props to apps, accidentially affecting platform/system apps - but v2.9 is too old to have that patch? maybe seeing updater debug logs helps understand the issue