Phone stuck in fastboot mode, unable to install Fairphone OS

Hi, I recently got a Fairphone 5 and wanted to install e/os on it. I had thought I could do it through the easy installer but found out after buying that wasn’t an option yet. Anyway, I wasn’t too put off and read the instructions carefully and then tried to step through them.

Long story short, the installation didn’t work. It’s stuck in the bootloader menu (it gives me the four options start, restart bootloader, recovery mode, power off, but choosing any only loops it back to this screen). It will still recognise fastboot commands, so for now I’ve been trying to set it back to Fairphone OS. I’ve downloaded the latest image from here: https://support.fairphone.com/hc/en-us/articles/18896094650513-Install-Fairphone-OS-manually - Version: FP5.UT2E.B.078

I’m having no luck with this either though, it starts ok but always hangs at the same point (Sending ‘modem_a’ ) and wont go any further:

$ ./flash_fp5_factory.sh 

*** Fairphone 5 flashing script ***

INFO: The procedure will start soon. Please wait...
INFO: The package type is "user-factory"
INFO: You are using a Linux distribution.

INFO: Validating the integrity of the package.
      This might take a while. Please wait...
INFO: Validation complete.
WARNING: Flashing this image wipes all user data and settings on the phone.
         It will also remove the Google factory reset protection.
         Are you sure you want to continue?
         Type "Yes" (case sensitive) and press enter to continue: Yes
INFO: Looking for connected device(s)...
INFO: One Fairphone 5 in fastboot mode found (serial number: xxxxxx).
INFO: The device is fully unlocked.
INFO: Proceeding to flash the device.
INFO: flashing partitions...
Sending 'abl_a' (152 KB)                           OKAY [  0.007s]
Writing 'abl_a'                                    OKAY [  0.001s]
Finished. Total time: 0.018s
Sending 'abl_b' (152 KB)                           OKAY [  0.007s]
Writing 'abl_b'                                    OKAY [  0.003s]
Finished. Total time: 0.018s
Sending 'aop_a' (203 KB)                           OKAY [  0.008s]
Writing 'aop_a'                                    OKAY [  0.001s]
Finished. Total time: 0.017s
Sending 'aop_b' (203 KB)                           OKAY [  0.009s]
Writing 'aop_b'                                    OKAY [  0.002s]
Finished. Total time: 0.024s
Sending 'apdp' (13 KB)                             OKAY [  0.002s]
Writing 'apdp'                                     OKAY [  0.001s]
Finished. Total time: 0.012s
Sending 'bluetooth_a' (3388 KB)                    OKAY [  0.117s]
Writing 'bluetooth_a'                              OKAY [  0.009s]
Finished. Total time: 0.135s
Sending 'bluetooth_b' (3388 KB)                    OKAY [  0.107s]
Writing 'bluetooth_b'                              OKAY [  0.014s]
Finished. Total time: 0.130s
Sending 'cpucp_a' (182 KB)                         OKAY [  0.008s]
Writing 'cpucp_a'                                  OKAY [  0.001s]
Finished. Total time: 0.018s
Sending 'cpucp_b' (182 KB)                         OKAY [  0.008s]
Writing 'cpucp_b'                                  OKAY [  0.003s]
Finished. Total time: 0.018s
Sending 'ddr' (20 KB)                              OKAY [  0.002s]
Writing 'ddr'                                      OKAY [  0.001s]
Finished. Total time: 0.010s
Sending 'devcfg_a' (52 KB)                         OKAY [  0.003s]
Writing 'devcfg_a'                                 OKAY [  0.001s]
Finished. Total time: 0.014s
Sending 'devcfg_b' (52 KB)                         OKAY [  0.003s]
Writing 'devcfg_b'                                 OKAY [  0.006s]
Finished. Total time: 0.018s
Sending 'dsp_a' (65536 KB)                         OKAY [  2.193s]
Writing 'dsp_a'                                    OKAY [  0.168s]
Finished. Total time: 2.369s
Sending 'dsp_b' (65536 KB)                         OKAY [  2.166s]
Writing 'dsp_b'                                    OKAY [  0.145s]
Finished. Total time: 2.319s
Sending 'featenabler_a' (84 KB)                    OKAY [  0.004s]
Writing 'featenabler_a'                            OKAY [  0.001s]
Finished. Total time: 0.014s
Sending 'featenabler_b' (84 KB)                    OKAY [  0.004s]
Writing 'featenabler_b'                            OKAY [  0.003s]
Finished. Total time: 0.016s
Sending 'hyp_a' (3601 KB)                          OKAY [  0.123s]
Writing 'hyp_a'                                    OKAY [  0.011s]
Finished. Total time: 0.141s
Sending 'hyp_b' (3601 KB)                          OKAY [  0.127s]
Writing 'hyp_b'                                    OKAY [  0.017s]
Finished. Total time: 0.153s
Sending 'imagefv_a' (64 KB)                        OKAY [  0.004s]
Writing 'imagefv_a'                                OKAY [  0.003s]
Finished. Total time: 0.014s
Sending 'imagefv_b' (64 KB)                        OKAY [  0.003s]
Writing 'imagefv_b'                                OKAY [  0.003s]
Finished. Total time: 0.015s
Sending 'keymaster_a' (261 KB)                     OKAY [  0.010s]
Writing 'keymaster_a'                              OKAY [  0.007s]
Finished. Total time: 0.030s
Sending 'keymaster_b' (261 KB)                     OKAY [  0.011s]
Writing 'keymaster_b'                              OKAY [  0.003s]
Finished. Total time: 0.022s
Sending 'logfs' (16 KB)                            OKAY [  0.003s]
Writing 'logfs'                                    OKAY [  0.001s]
Finished. Total time: 0.012s
Sending 'modem_a' (184796 KB)

I have contacted Fairphone support but haven’t heard anything back yet. I wondered if anyone here had any good ideas to try in the meantime?

Thanks :slight_smile:

Hi,
Have you looked at two posts here yet? In your case only steps 1 - 8 in second post applicable:
https://forum.fairphone.com/t/fairphone-stuck-in-fastboot-mode-bootloader-unlocked/85968/6?u=aspergerguy

Did you unlock critical? Not sure thats required for e/OS or not, however its required for FPOS

Not sure this very old iode FP4 topic applies for the FP5, I would not suggest it

I did both unlock and unlock_critical. I even checked it again when I went to flash FPOS (it gave me the error that it was unlocked already).

Flashing some form of recovery image might be an idea, although I can’t follow those instructions exactly as it’s for a different OS and different phone. Also I’m sure the first thing FP support will ask me to do is try to install the standard Fairphone OS.

This may sound wierd and I couldn’t believe it at first until I experienced it myself but… use a different cable. At least this solved my problems when flashing kept finishing unsuccessfully.

3 Likes

I would have tried this earlier but I didn’t have a spare one handy - the only one I found on first look was charging only. But I had a rummage around a few drawers this evening and found one - and yes, it has worked!

It’s weird that with the other one it was always stopping at the exact same point, that was what really made me think it was something else.

No matter, it’s solved, I hope others will learn from me and try the simple solutions first :slight_smile:

2 Likes