Fairphone 6 (non-Murena-edition) web-installer, stuck in bootloop

Using /e/OS Setup
, ,
22

fastboot devices returned: (device serial.no) fastboot - I did however notice this returns like this even if the device was unplugged. I figured there had to be something wrong with the PC, so I rebooted it. After rebooting it seems all the commands work as they should!
fastboot flashing get_unlock_ability returns 1
fastboot flashing unlock worked after PC reboot, and fastboot flashing unlock_critical said it was already unlocked, so I could finally proceed to the installation of eOS itself.

I ran the install-script, like the page said chmod +x flash_FP6_factory.sh && ./flash_FP6_factory.sh

But it seems the script is stuck at sending 'uefisecapp_a' (192 KB)

23

The script works as “flash or abort” so any fail to flash any one partition will fail like this.

Probably good to double check the whole USB chain … so best data cable, perhaps even a high capacity cable is needed ?? (certainly not a skinny one) avoid any hub and aim to connect to a USB port soldered to the motherboard.

Then try again.

You say “stuck at” … if the terminal prompt did not return (as should be the case for abort) I would be also think it a bit like your

24

Here is the entire log for when I did chmod +x flash_FP6_factory.sh && ./flash_FP6_factory.sh:

INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)...
INFO: One Fairphone 6 in fastboot mode found (serial number: c1ececb8).
Info: Your phone is in regular bootloader mode.
Sending 'bluetooth_a' (812 KB)                     OKAY [  0.021s]
Writing 'bluetooth_a'                              OKAY [  0.002s]
Finished. Total time: 0.041s
Sending 'bluetooth_b' (812 KB)                     OKAY [  0.021s]
Writing 'bluetooth_b'                              OKAY [  0.002s]
Finished. Total time: 0.036s
Sending 'devcfg_a' (47 KB)                         OKAY [  0.002s]
Writing 'devcfg_a'                                 OKAY [  0.001s]
Finished. Total time: 0.016s
Sending 'devcfg_b' (47 KB)                         OKAY [  0.002s]
Writing 'devcfg_b'                                 OKAY [  0.001s]
Finished. Total time: 0.015s
Sending 'dsp_a' (65536 KB)                         OKAY [  1.602s]
Writing 'dsp_a'                                    OKAY [  0.036s]
Finished. Total time: 1.651s
Sending 'dsp_b' (65536 KB)                         OKAY [  1.545s]
Writing 'dsp_b'                                    OKAY [  0.038s]
Finished. Total time: 1.598s
Sending 'modem_a' (180876 KB)                      OKAY [  4.434s]
Writing 'modem_a'                                  OKAY [  0.095s]
Finished. Total time: 4.542s
Sending 'modem_b' (180876 KB)                      OKAY [  4.294s]
Writing 'modem_b'                                  OKAY [  0.086s]
Finished. Total time: 4.392s
Sending 'xbl_a' (1138 KB)                          OKAY [  0.029s]
Writing 'xbl_a'                                    OKAY [  0.009s]
Finished. Total time: 0.051s
Sending 'xbl_b' (1138 KB)                          OKAY [  0.029s]
Writing 'xbl_b'                                    OKAY [  0.007s]
Finished. Total time: 0.049s
Sending 'tz_a' (3932 KB)                           OKAY [  0.098s]
Writing 'tz_a'                                     OKAY [  0.003s]
Finished. Total time: 0.117s
Sending 'tz_b' (3932 KB)                           OKAY [  0.095s]
Writing 'tz_b'                                     OKAY [  0.003s]
Finished. Total time: 0.111s
Sending 'hyp_a' (1642 KB)                          OKAY [  0.041s]
Writing 'hyp_a'                                    OKAY [  0.002s]
Finished. Total time: 0.059s
Sending 'hyp_b' (1642 KB)                          OKAY [  0.040s]
Writing 'hyp_b'                                    OKAY [  0.002s]
Finished. Total time: 0.054s
Sending 'keymaster_a' (430 KB)                     OKAY [  0.012s]
Writing 'keymaster_a'                              OKAY [  0.001s]
Finished. Total time: 0.026s
Sending 'keymaster_b' (430 KB)                     OKAY [  0.012s]
Writing 'keymaster_b'                              OKAY [  0.002s]
Finished. Total time: 0.026s
Sending 'abl_a' (239 KB)                           OKAY [  0.007s]
Writing 'abl_a'                                    OKAY [  0.001s]
Finished. Total time: 0.024s
Sending 'abl_b' (239 KB)                           OKAY [  0.007s]
Writing 'abl_b'                                    OKAY [  0.001s]
Finished. Total time: 0.020s
Sending 'aop_a' (311 KB)                           OKAY [  0.009s]
Writing 'aop_a'                                    OKAY [  0.001s]
Finished. Total time: 0.023s
Sending 'aop_b' (311 KB)                           OKAY [  0.009s]
Writing 'aop_b'                                    OKAY [  0.001s]
Finished. Total time: 0.022s
Sending 'featenabler_a' (102 KB)                   OKAY [  0.003s]
Writing 'featenabler_a'                            OKAY [  0.001s]
Finished. Total time: 0.018s
Sending 'featenabler_b' (102 KB)                   OKAY [  0.003s]
Writing 'featenabler_b'                            OKAY [  0.002s]
Finished. Total time: 0.018s
Sending 'imagefv_a' (51 KB)                        OKAY [  0.002s]
Writing 'imagefv_a'                                OKAY [  0.006s]
Finished. Total time: 0.021s
Sending 'imagefv_b' (51 KB)                        OKAY [  0.002s]
Writing 'imagefv_b'                                OKAY [  0.005s]
Finished. Total time: 0.020s
Sending 'multiimgoem_a' (11 KB)                    OKAY [  0.001s]
Writing 'multiimgoem_a'                            OKAY [  0.005s]
Finished. Total time: 0.019s
Sending 'multiimgoem_b' (11 KB)                    OKAY [  0.001s]
Writing 'multiimgoem_b'                            OKAY [  0.008s]
Finished. Total time: 0.022s
Sending 'qupfw_a' (59 KB)                          OKAY [  0.002s]
Writing 'qupfw_a'                                  OKAY [  0.006s]
Finished. Total time: 0.021s
Sending 'qupfw_b' (59 KB)                          OKAY [  0.002s]
Writing 'qupfw_b'                                  OKAY [  0.001s]
Finished. Total time: 0.020s
Sending 'uefisecapp_a' (192 KB)

It does not say anything failed, it just is stuck at that last step without proceeding. Is it safe to abort the program and retry with a different cable/USB-port?

25

Yes, will be fine to Ctrl + C.

26

OH MY GOD IT’S WORKING! :star_struck: Thank you so incredibly much for sticking with me through this process! I am almost over the finish-line, almost gotten the privacy-focused OS that I always wanted :smile:

However, the script also rebooted my device, but the install-instructions told me to do fastboot flashing lock_critical and fastboot flashing lock BEFORE i rebooted the device… Does that mean I have to do this whole process over again to lock it?

27

Great. Good to hear you got this far.

It is good practice to lock before reboot.

BUT can you tell for certain that you are safe to lock the bootloader as mentioned

Most important did you keep a record of the Android SPL showing on FairphoneOS before you unlocked it?

28

No, not that I am aware of. I got the phone and did all the regular updates one would do to their phone before I discovered eOS… :upside_down_face: Fairphone’s own website provides these files for Android 15, and the newest one is on security update 05 June 2025, the same as the current eOS image it seems. The version on Fairphone’s website was released 14. july.

So do I boot into eOS and set up everything, and update everything to be as new as they can be and then attempt to lock it? Or should I wait for some sort of future security update? If so, how should I proceed?

29

One avenue is to keep the phone on /e/OS and update until you feel certain that /e/OS is in advance of what your previous FairphoneOS could possibly have been. However when you lock you will Format data, so you start again.

30

I think I will do that then. For now, I will avoid having anything of importance on the device. Thanks again for all the help!

Is it obvious when a new security-version gets installed? Or do I just have to check it manually every now and then? Are those kinds of updates released weekly, monthly, etc?

1 Like
31

You should be notified monthly on the phone,
2 or 4 days after the new version release (that is announced on the forum 2 or 4 days before the date).

32

You know you find your /e/OS version and Android SPL from

Settings > About phone > tap on Android version.

You might subscribe to the weekly update found in Development Updates to understand in advance updates to expect.

(I was surprised following your Fairphone link to see that a 14th July FaiphoneOS release does not include Android Security Bulletin—July 2025 but this is just about my expectation after your OP locking failure.)

33

I reached out to their support, and they told me the latest security-patch is on 5th of June, the same as what is listed for eOS, great stuff!

However, when I go into the actual settings in eOS and look at Securety update for Android it says 1st of June, not 5th of June :thinking: Did they list the wrong security update on the webpage?

34

For clarity … Fairphone said this … confirming what we already discussed ??

… but, that is the problem, /e/OS seems to declare only June 2025

Reference

… we then find the build contains only SPL for 1st June 2025.

35

I quote their support staff:

The latest security patch that we do have on the phone (Google OS) is from the 5th of June from what we have on our side.

image
image895×392 41.6 KB

image is from the the FP6 install page, where it says the security patch is 2025-06-05. That is the 5th of June, right?

36

I guess my suggestions were to support you not to lock your bootloader if unsafe.

You could get text output of this alongside your build_version_string (or else a screenshot) then you could Report an issue in the documentation or at least alert a moderator here.