I installed Murena /e/os on my FP5 some months ago and was pleased with it and keen to minimise my dependence on Google. Following an upgrade to /e/os the banking apps I use stopped working (I live in Norway) so I decided to go back to FPOS. I followed the instructions but unfortunately the process stalled at a certain point where a file could not be uploaded/updated. The phone was stuck in a bootloader loop. I contacted Fairphone support and got a support number just over 4 weeks ago and haven’t heard anything more since. I have an old phone which I could use though it doesn’t work well. I became impatient and found a suggestion on the net which I (foolishly) followed and now the phone is completely dead with a black screen and no response to button presses. I assume that I have ‘bricked’ the phone. Can anyone tell me if there is any point waiting for support to get back to me? Is the phone fixable or should I be looking to get a new phone?
I would be grateful for any advice.
Hi Chris. Can you describe the steps you followed, that résulted in a non responsive phone?
From a poweroff state, press Volume - and plug to power source (computer or wall socket). Can you get to fastboot?
If the worst comes to the worst I would think you could have it re-installed from scratch at the Cordon repair centre.. I don’t know the cost, but the official repairs price list (outside of warranty) cites 34.10 € for assessment.
But before that, as koumilak says, let’s have some details. Also check whether you have a local FP angel who might be able to help.
Thanks koumilak and OldRoutard for your responses. It’s all a bit confused now exactly what I did but I attempted to use fastboot to install the FPOS using FP5-UT2P-factory image on linux using the command ./flash_fp5_factory.sh. The installation froze at a certain point I can’t remember which but think it might have been abl.elf repeatedly. I tried different cables etc as recommended by others. At this point I was stuck in a bootloader/recovery loop. After waiting some days for a response from support I became impatient and tried fastboot flash:raw abl_a abl.elf. (I was going on a cycling holiday and needed the phone for GPS guidance.) From then on the phone would not boot or respond. I’ve tried all combinations of Vol up, Vol down and plugging into a power source and removing and returning the battery but the screen remains stubbornly black. ‘adb devices’ doesn’t find anything. I’m not sure if this helps other than to reveal my level of stupidity but thanks to both of you for your interest. I would be nice to think that there is a chance the phone could be used again, I’d hoped to have it for a long time!
On linux? Could you tell us the distro and the version of fastboot?
It appears that the abl partition is exactly where the secondary-stage bootloader and thus fastboot is located.
If the flashing of the partition failed and it was corrupted, it may have broken fastboot.
Just to test, maybe let your phone charging a bit, it may just be a dead battery, and then see if lsusb on your computer recognizes the phone in any way.
It does recognise it!
Bus 003 Device 009: ID 05c6:900e Qualcomm, Inc. QUSB_BULK_SN:50CEC1E6
I’m using Ubuntu 24.04.2 LTS
fastboot --version
fastboot version 35.0.0-11411520
Installed as /usr/lib/android-sdk/platform-tools/fastboot
that’s some sort of error mode… so fastboot devices returns nothing, then?
That’s right. I’ve just tried it again.
a cursory search suggests that QUSB_BULK is linked to EDL mode, i think you should try to get out of it and boot it in another mode.
Either press power for 10s and try to get into fastboot, or remove battery then try Volume - and plugging.
I know you’ve already tried loads of permutations, but it’s really the last thing to consider before returning it to the shop
I tried the suggestions you gave but lsusb still reports QUSB_BULK. So as you say, I may have to return it to the shop but how can I do that without a response from Fairphone support?
I’m sorry ; it appears you don’t have much choice but to wait.
Thanks for your time and patience. At least I feel there may be some hope if FP support finally get back to me at least.
Chris
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.