For me it was so unclear that I had to install in two steps:
First the img file on the right side: /e/ image ROM download via ADB command, use the same commands as in the guide above.
Then press Vol + button and keep holdin it before you press enter for this command: fastload reboot.
You should see there’s an update via Sideload available on the phone. Now use the zip file on the left from the /e/os sources.
on your PC run: adb sideload e-1.1-q-20220629200240-dev-FP2.zip
Then it should be installed.
If you want to fine tune - maybe get rid of microG, see here (for experience users only and in German, commands were clear to me though)
https:// forum.kuketz-blog. de/viewtopic.php?t=1655&hilit=eos&start=75
You might want to change the captive portal in order to cut connections to Google for real:
https:// www. kuketz-blog. de/android-captive-portal-check-204-http-antwort-von-captiveportal-kuketz-de/
Installation worked fine but took me hours because in the installation documentation there is a link to R community with download links to partition image files (IMG*.zip), but in the description adb sideload is used which requires OTA files (e*.zip). So I spent a lot of time to find out why I always get the error “invalid zip file format”… In the end I found the solution here.
Moreover I was confused by step 6 “Now reboot into recovery to verify the installation” of section “Installing a custom recovery” because there is no description how to do this.
I assume you installed /e/OS 1.21-r (r = Android 11). You are aware that /e/OS 1.21-r is most probably the last /e/OS version with security patches for the Fairphone 2 according to this statement? …
Thanks for your reply. No, I was not aware of this, bad news! But what else can I do with my FP2?
I just visited the /e/OS website and followed the information and links about the FP2. So I ended up in the FP2 installation documentation which links to downloads that cannot be used as described. I think this should be corrected so that other users do not get into the same trouble.
Of course some information in the FP2 info page about folded up security updates would be useful, too.
Hello everyone,
I’m wondering if there is any issue to change my eOS software from e-1.8.1-q (Android Q) to the latest version IMG-e-2.2-r in section Android R (here : https://images.ecloud.global/dev/FP2/ ).
Indeed, last year I downloaded and installed e-1.8.1-q version as my FP2 was initially under Google Android 10 (Android Q), I was not sure to be able to switch to Android R. And now, I see that there is not any update of section Android Q and worry about possible security issues not solved so.
I assume it is possible seeing this previous post :
Thanks fab for your answer.
I prefer asking advice as I saw the instructions about installing eOS on FP2 have changed since august 2023 when I installed e-1.8.1-q (Android Q), for which I had to install fist TWRP as the documentation specified earlier (this version https://web.archive.org/web/20230430210448/https://doc.e.foundation/devices/FP2/install ). Now I see the documentation does not refer any more to TWRP, so : what about it ?
While the latest version certainly would be better in this regard by definition, please note that Android 11 (R) didn’t get any security updates anymore since after the February security patches. It’s end-of-life, a dead end.
You can first watch what will come of this …
… and if this doesn’t result in continued security update support (not getting my hopes up), then you should seriously consider migrating to this here if you want to continue to use your Fairphone 2.
The current instructions are matching the contents of the current install files. No TWRP needed.
Thanks @AnotherElk for your answer.
Nevertheless, what’s the consistence of regular updates in section Android R (about one every month until july 2024 on current days) ?