Vendor Name: Fairphone
Device name: Fairphone 4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: 2.9 T official
Not rooted
Murena Voice to text crash !
Vendor Name: Fairphone
Device name: Fairphone 4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: 2.9 A14 official
Not rooted
Update went well.
Screencast WIDI doesnt work since A14 upgrade, wfd system app seems to crash on trying to connect.
No other problems detected so far.
Thanks E Team
Thank you so much @AnotherElk to explain how itās works. I understand.
On the current active slot (Slot B) itās the old OS so 2.9.
I didnāt reboot my phone yet since this night , cause Iām scare to have a new boot error.
Is it possible to keep slot B with datas, and install New OS on slot A ? maybe with a sideload ?
Hi,
You have 2 solutions :
1> in fastboot mode
# Pour connaitre le slot actif
sudo fastboot getvar current-slot
# Pour activer le slot A
sudo fastboot set_active a
# Pour activer le slot B
sudo fastboot set_active b
2> with TWRP Recovery
in recovery go in reboot menu and press the slot Button that you want.
good luck
May depends on device ā¦
because i donāt have this option in the recovery of my FP3 !
Vendor Name: Fairphone
Device name: Fairphone 4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: v2.9-a14 (official)
Is the device Rooted / Not rooted: Not rooted
Hi there, the new update broke my phone 
ultimately im now stuck in fastboot with a corrupted device.
All the info I can find online points to this happening after manual e/os installs or custom ROMS but I simply pressed update in the official updater on the FP4 itsself. I was using v2.9 before and updated to 3.0 last night.
My issue is similar to that of Anonymous, just that it has progressed to get me stuck in fastboot now.
Initially, I was also stuck in recovery but could sometimes get back into the phone for about 5-6 minutes before it rebooted itsself into recovery. So I activated adb etc. and backed up light files I could copy quickly (however, in the stress I forgot my contacts of course and my 2FA app backup did not sync in time either >.<). I use Signal so I really needed that backup to copy but because it was 30gb in size, the time I had before the phone rebooted into recovery, was not enough. So I tried to push the file to my pc (linux) directly via adb, hoping the transfer speed would be better. It was but at around 30% the phone rebooted again, but not as before into recovery. This time it first showed me āYour device is corrupt. It canāt be trusted and will not bootā and then booted into fastboot. Now im stuck there.
I cant access adb from here of course and the options allowing me to boot into recovery etc. dont work either. I tried fixes from older threads on here and other FP forums but no commands are allowed as its in lock state. This also applies to changing the active slot. Most fixes are from 2022 so im hoping maybe someone has come up with a fix by now.
Does anyone have any ideas left? I dont mind things getting complicated! I just need to somehow decrypt and access those files 
Vendor Name: Fairphone
Device name: Fairphone 4
Device CodeName: FP4
Version of /e/OS or Stock which existed previously: 2.9 Stable A14 official
Not rooted
Update was smooth and clear.
Everything (that I use) seems all fine.
Just tested āFind my deviceā. All is perfect, exact position was received by SMS on the recipient device.
So all great! Big thanks to the whole team! 
āWil not bootā, isnāt there a [Try again] button?
HELP!! Sad to report, my Pixel 6 Pro may have expiredā¦
- Vendor Name: Google
- Device name: Pixel 6 Pro
- Device Code: Raven
- Version of /e/OS or Stock which existed previously: Lineage/MicroG 22.2
Step 7(below), rebooting to bootloader is where the device never turned back on.
This is the same method I have used for some years with no problem until now. Ive tried various methods to start device with no sign of life.
Any suggestions appreciatedā¦
1 - adb reboot bootloader
2 - fastboot flash boot boot.img
3 - fastboot flash dtbo dtbo.img
4 - fastboot flash vendor_boot vendor_boot.img
5 - fastboot reboot recovery
in recovery wipe data(factory reset)
then select apply update from adb
6 - adb sideload rom.zip (e-3.0-a14-20250530496774-community-raven)
7 - You should also flash the second slot once your setup is complete
Repeat the steps from above
No need to wipe data again
Yea there was but sadly after pressing that it booted into fastboot for the first time and got stuck there since 
Hello,
your are not alone. Iām in the same case. For now, my FP4 starts and I can access to interface. After a moment, my FP4 shutdown. My FP4 is not completely blocked because I have access to recovery mode and I can choose the āTry againā option to start the smartphone but it is not very practical . I donāt know if the 3.0 version is installed by default on slot A but Iām on Slot B, and Iāve got the error message. I made a backup of all my files and contacts. It sucks. I made all the official updates before I had not any problems.
Hope that the E/OS team can help us.
Thanks.
3 Likes
since I downloaded e/os3, my fairphone 5, bought on the purena site, doesnāt work any moreā¦It doesnāt recognize android, it sends me to the recovery page, and I tried it, and still the sameā¦the help center told me it would take 3 to 5 days to help meā¦I need my phone to workā¦can you help me here?
Regain your privacy! Adopt /e/OS the deGoogled mobile OS and online services
1 Like
exactly like me! on my fairphone 5 from Murena shop
1 Like
Honestly, I would wait until they resolve the issue.
ā¦without a phoneā¦difficult!
@Manoj Could you guys please get involved in this? Its effecting more and more people. Im dependant on this phone for work, as are many of the others.
3 Likes
Hi! After the update to /e/OS 3.0 yesterday the issue with the volume in ānormalā calls being low and distorted persists like before. Calls sounded better before with stock Android on my FP4. Any tips or fixes?
Vendor Name: Google
Device name: Pixel 5
Device CodeName: Redfin
Previous Version of /e/OS: 2.9-t-20250321478215-official-redfin
Version of /e/OS: 3.0-t-20250528496286-official-redfin
Device: Not rooted
Update smooth & successful.
Longer process than previous updates : ~45mn (especially the āFinalising package installationā step).
Some remarks :
- Camera app is still useless, Iāll keep using a GCam port
- Still Android 13, even if this was expected.
Anyway, I feel lucky compared to some othersā¦
Hey urs_lesse!
Thanks for the information. I upgraded to 3.0 on my FP5. The A13 remains from previous. I followed the link to e/OS official FP5 download but the process stopped just after the download. I think it might be a browser issue. Are you aware of plans to push an automatic update for A14/A15 in near future? I donāt want to kill my FP5 due to lack of patience!!
Does this run to charge response including connect and disconnect power?