Fairphone 3+
FP3
Updated from v1.19.1-s-stable to v1.20-s-stable
Not rooted
Update straightforward and completed in 35 minutes.
All appears to be working OK on initial testing of basic functions & apps: wi-fi, mobile data, bluetooth, GPS, phone, message, mail, browser, camera, app lounge and various other apps.
The long-standing reported issue I have with no automatic VPN connection is still present.
Thanks again for all the good work.
Hello /e/ OS Community,
I’ve purchased the Fairphone 5 together with a mobile data plan in 02/2024, in Germany.
The provider delivered the device with stock Android.
I flashed immediately /e/ OS on it, following this guide:
https://doc.e.foundation/devices/FP5/install
Everything went well, including unlocking the bootloader, flashing the ROM and locking the bootloader again afterwards.
I went on happily with my life.
But then, yesterday (02.03.2024) in the evening, I received on my phone a notification about an update of the OS to version 1.20.
With a charging phone with more than 30% battery I tapped “Download” and installed afterwards the update but I didn’t reboot yet the phone and went to sleep.
Today (03.03.2024) in the morning, I picked up the fully charged phone and tapped “Reboot”.
When the devices turned off, nothing. BRICK!
I tried every key-combo:
Nothing. The screen does not react, no vibration, nothing, no feedback from the phone.
The only “feedback” I get is, when I connect the phone to the PC, I hear the sound the PC makes when something gets connected.
The device manager then only shows under “Other devices” : QUSB_BULK_CID:XXX_SN:XXX
I replaced the serial numbers with XXX.
Also while holding Power or Power + volume down for 10 seconds while connected to the PC, I get the sound of disconnection and connection from the PC. That’s all.
Also, installation of fastboot and/or ADB drivers did not help.
Has anyone an idea what happend? Any advice what to do?
If there is nothing I can do, do I have a change for a fix by sending it to the Netherlands for a fix?
If yes, does anyone know who to contact for sending in the phone?
Thanks a lot in advance for your help guys!
Regain your privacy! Adopt /e/OS the unGoogled mobile OS and online services
Xiaomi Redmi Note 9s
miatoll
Updated from version: e-1.19.1-s-20240112372761-dev-miatoll.zip
Not rooted.
Loaded the new recovery;
did NOT factory reset, did NOT format;
Sideloaded the new OS Firmware.
The progress counter stayed at 47% for a good while. On returning to the machine, it had completed.
All functioning as before.
Thanks.
Xiaomi Redmi Note 9s
miatoll
Updated from version: e-1.19.1-s-20240112372761-dev-miatoll.zip to 1.20 T version
Not rooted.
Loaded the new recovery;
did NOT factory reset, did NOT format;
Sideloaded the new OS Firmware.
Seems fine except SaftyNet status fails. CTS profile mismatch so it seems it recognize unlocked bootloader again? SaftyNet was passing in several last /e/ os (S) updates on miatoll. Unfortunatelly fails again on Android T so one application I need which requires SaftyNet do not work anymore. Please fix this again. Thx
EDIT:
adb shell getprop ro.boot.verifiedbootstate
green
As verfied boot state is green CTS does not fail because of bootloader state as before?! This is new problem.
EDIT2: after several restart, failing app which requires saftynet is working again. SaftyNet is still failing. My guess is that particular app was updated (APP Lounge reported update but you don’t see which one)
SaftyNet is becoming obsolete so maybe it is not required anymore while app is not updated to use play integrity yet.
Vendor Name: Fairphone
Device name: Fairphone 3
Device CodeName: FP3
Version of /e/OS or Stock which existed previously: /e/OS 1.19.1-t-20240113373116-dev-FP3
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on 1.20-t-20240222382228-dev-FP3.
The following things work for me:
Vendor Name: Fairphone
Device name: Fairphone 2
Device CodeName: FP2
Version of /e/OS or Stock which existed previously: /e/OS 1.19.1-r-20240110372392-dev-FP2
Is the device Rooted / Not rooted: Not rooted
No issue with updating, now on 1.20-r-20240221382014-dev-FP2.
The following things work for me:
What a lovely spring clean!
It’s a great start to the new year.
My update went smoothly and quickly. I made sure that the screen didn’t go dark during the installation (standby?). I had the impression that this made it run faster than when the screen was dark.
Thanks for the great work. redfin
Indeed I still wonder why this isn’t automatic be done before an OTA update starts. Nobody needs an update time of more than a whole hour.
I would wonder how much more battery the quick way (keeping the screen on) would really use, if any, before making this the default way.
But then again I wouldn’t want to invest the odd hour and change to find out 
.
The only thing needed would be a checkbox on the update page, “let the screen on”. Then the user could test this and decide himself. A rather simple thing.
Thank you for taking up my suggestion. It is indeed surprising from the user’s point of view. An options popup should appear before the installation, with the recommendation to temporarily suspend standby during the update. This should certainly be a useful enhancement suggestion for the wish list here in the forum. Thanks.
Dear all,
I can confirm the exact same behaviour for my Fairphone 5. It looks like bricked 
(I did not test to connect it to a computer as @kipo did though).
Please provide help !
I liked /e/OS until yesterday evening after I hit “Reboot” and then could only see a black screen and think that I might have been too much confident in Murena and /e/OS developers.
Found out and updated manually Mi 11 Lite 5 NE (lisa) from 1.19.1-s to 1.20-t.
All working well. Thanks team! Nice thing I found out in /e/OS 1.20-t is capability to charge my phone to desired percentage - nice
please does a power-user interested in Fairphone can investigate on How to unbrick the FP5 and share his found on this forum.
thanks in advance…
Would be great if they implement that also for the FP5, still missing there 
So, my Fairphone 4 sucks the battery within 4-8 hours…
/e/OS supports 5 different Fairphones right now … 2/3/3+/4/5.
And /e/OS is available as dev as well as stable for most of them.
Since v1.20 it’s no longer possible to download Apps from AppLounge, when using a USB-C- Lan-Connector. It now says: No connection
At home my Family and I don’t use wifi. I only use my Fairphone with a LAN-Adaptor and so fare it worked well. Would be great, if the AppLounge worked again in 1.21.
Thanks, for all your hard work.
Cheers Marc
Vendor Name: Google
Device name: Pixel 7a
Device CodeName: lynx
Previous Version : stock ROM
Rooted: False
Hi everyone,
So with v1.20 the Pixel 7a (lynx) is now supported, thanks a lot to the team !
However, I had some difficulties to achieve the installation, since the e-recovery image provided doesn’t work (and Lineage recovery does but won’t install /e/OS), and the additionnal partition files are missing…
I would have suggested improvements in documentation but the topic doesn’t exists yet in the wiki section (@Manoj ?)
So if someone wants to install 1.20 on a Pixel 7a (lynx) device, I managed to do it by downloading the /e/OS 1.20 zip file provided in the installation instructions, then use the payload-dumper-go tool (see here) to extract from the the zip file all the .img files needed to flash the various partitions AND the recovery.
Using those files in the same way as described in the install proc finally worked !
Now, the phones seems to work great, even tho I haven’t used it for long at the moment.
Thanks again !
And one final question, I see that it is possible to relock the bootloader for Pixel 7 and Pixel 7 Pro, but I can’t manage to find a solution to do it on the Pixel 7a. Does someone know if it could be possible ?
Thank you,
Vendor Name: Fairphone
Device name: Fairphone 5
Device CodeName: FP5
Previous Version of /e/OS: 1.19.1-s
Rooted: False
Working fine apart from now having a persistent ‘cloud storage full’ notification meaning i cant sync things despite only using 656.8 MB of 1GB storage.