Hello,
Fairphone 5 running /e/OS Android 14.
The device already showed higher-than-expected battery drain from the beginning.
Update sequence:
-
/e/OS 3.1.1 → 3.1.4 (successful, system working normally)
-
Update to 3.2 → the phone stopped booting completely.
Current state:
-
No power on, no vibration, no logo
-
No access to recovery or fastboot
-
Not detected as an Android device by the PC
-
On GNU/Linux Debian it appears as Qualcomm 9008 (QDL / EDL mode) when connected via USB, identified as
Bus 001 Device 012: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode)usinglsusb
It is not clear whether the system can still be recovered by flashing firmware again or whether the bootloader / low-level partition has been affected.
Has anyone managed to recover a Fairphone 5 in this state after a /e/OS 3.2 update?