I was following the install guide for the FP5 and everything went normal until I executed the install script which just came as far as Sending 'bluetooth_a' (3356 KB) and is just stuck there (waited for up to 30 min, it should take less than a second). I did both unlock steps and fastboot oem device-info returns:
I can cancel the script in the terminal. When I do, lsusb is not listing the phone anymore. But after disconnect USB > Restart PC > Restart Bootloader on the Phone > reconnect it does see it again and, e.g. fastboot devices also lists it again.
The fact that the script gets as far as Sending 'bluetooth_a' also means that it was able to see the phone initially. I already repeated the procedure several times and also tried it with the community instead of the official build but there it is exactly the same.
I am afraid to do anything else than “restart bootloader” on the phone b/c of the possibility that it might brick the phone in this undefined state.
Do you have any idea what I could try to overcome this situation? Or can you think of a reason why it is getting stuck there reproducibly?
Is the previous version of /e/ for FP5 still available for download anywhere (officially)?
What would happen if I were to reboot the phone normally now? (And would I at least be able to get back into the bootloader?)
is there a danger of the phone running out of battery and not charging anymore? (happened to me with a tablet once which needed at least one .img (the recovery?) to be flashed correctly in order to charge)
Thanks a lot for any help
Edit: This is the Terminal output:
[jme@jme FP5]$ ./flash_FP5_factory.sh
*** Fairphone 5 flashing script ***
INFO: The procedure will start soon. Please wait...
Note that this will detect and flash only on Fairphone 5 device.
INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)...
INFO: One Fairphone 5 in fastboot mode found (serial number: XXXXXXXX).
Info: Your phone is in regular bootloader mode.
Sending 'bluetooth_a' (3356 KB)
Is the “Info: Your phone is in regular bootloader mode.” an issue?
hey thanks a lot again! still reading through the links you posted.
TWRP: I thought that is not supported since FP 3 or 4? – are you sure it would work?
Also, do you know if there are older images of previous /e/ versions available for FP5? e.g. 2.3.x? (I should maybe avoid 2.4.0 b/c of the issue they had with the update process?)
Yes, but I also have this, just one line above:
INFO: One Fairphone 5 in fastboot mode found (serial number: XXXXXXXX).
Looking at the script it would ouput either “Info: Your phone is in fastbootD mode.” or “Info: Your phone is in regular bootloader mode.” so maybe this is just in the newest version of the script?
The function in question
# Check if the device is properly unlocked
check_unlock_status() {
PHONE_IS_READY=true
if (fastboot getvar is-userspace 2>&1 | grep -q yes); then
echo "Info: Your phone is in fastbootD mode."
if (fastboot getvar unlocked 2>&1 | grep -q no); then
echo "Error: Your phone is still locked."
echo "Did you execute 'fastboot flashing unlock'?"
PHONE_IS_READY=false
fi
else
echo "Info: Your phone is in regular bootloader mode."
if (fastboot getvar unlocked 2>&1 | grep -q no); then
echo "Error: Your phone is still locked."
echo "Did you execute 'fastboot flashing unlock'?"
PHONE_IS_READY=false
fi
if (fastboot oem device-info 2>&1 | grep -q "critical unlocked: false"); then
echo "Error: Critical partitions are still locked."
echo "Did you execute 'fastboot flashing unlock_critical'?"
PHONE_IS_READY=false
fi
fi
if [ "$PHONE_IS_READY" = "false" ]; then
echo "Error: Your phone is not ready for flashing yet (see above), aborting..."
exit 1
fi
}
i managed to solve it now. I needed to be in the fastbootD mode (haha, actually see the code I posted before) and then some further detours… well described in the thread i linked here…
