I have a Fairphone 2 here, it works fine but I cannot get it in fastboot modus. “adb reboot bootloader” reboots the device, but then it gets stuck. When I use the buttons it does not work too. And I also cannot come in the recovery modus with the buttons…
So I guess there is something really wrong with the recovery, is there a way to reinstall it, or something like that?
Background: I want to install LineageOS on the device.
I found out more. When I do “adb reboot bootloader” it looks-like it’s stuck, but “fastboot devices” does work! So I could flash the recovery.
But after that, I had problems to go to the recovery with “Power + holding Volume UP”, but I also found a way. I did not turn-off the device but I rebooted it from fastboot modus with “Power + holding Volume UP”, and came into recovery. So I guess I can install LineageOS now.
I don’t know what the phone was running exactly, and if it was updated to the latest version. The phone is from a customer who needed help to install LineageOS. I did that before, but I am not an expert.
If LineageOS is working now, and fastboot mode is still without indication, then the modem files on this particular Fairphone 2 are outdated, and LineageOS will not update them.
I mean, even the latest available modem files are old now, but at least there are more current ones then pre-19.02.1, here’s the link again … and the 19.02.1 files for instance fixed a noticeable bug, apart from introducing fastboot mode indication.
Either that, or you can install the ZIP file in recovery mode, if the recovery offers that (TWRP does).
Can’t say I’ve seen this, but then I always used TWRP to install such ZIPs back in the day (and TWRP had a setting for signature verification which had to be kept turned off).
If you want to try and TWRP is not installed, you can just boot TWRP without installing it, see #twrpwoflashing .
I would try to boot into TWRP to see if it works then. With Stock FP recovery e.g. you cannot flash LOS so maybe there is some “incompatibility” when you use the LOS recovery. With TWRP it always worked well