I installed /e/os on my FP6 using the web installer. All went well and it got met to the part where the web installer told me that the installation was successful, that I had to boot my phone and follow the instructions on screen.
However my phone won’t boot and I think I need some help to get it working properly.
When I turn on the phone the following happens:
1 The fairphone logo is briefly shown.
3 The fairphone logo is shown again. A bit longer this time.
4 The screen turns off and after a few seconds the whole process starts again from step 1.
If I hold the volume down button during step 4 I get into the bootloader menu.
The first few cycles the Murena logo was shown instead of the fairphone logo. The phone then gave the option to boot from another partition (or something like that,I don’t remember the exact wording) and since then I’m stuck in the bootloop described above.
I’m out of ideas here, so any help for getting out of this situation will be greatly appreciated.
The significant thing here is that this is the AOSP recovery and it shows the Android OS (formerly called “Fairphone OS”) version. /e/OS would come with an all different looking /e/ recovery (e icon, black font on white background).
Did you already try to “Reboot system now” from here?
This fits to what I wrote above – apparently something went wrong with the /e/ installation, so the phone switched back to one of its two partitions, i.e. the one that still has the Android OS version that you were on when you started the installation.
From what I know, the web installer would usually instruct to lock the bootloader. Your 2nd and 3rd photo both show it is not locked.
I cannot give a specific recommendation right now. But it might be good to know that /e/ is planning to release a new version 3.1.4 soon which will also include newer security patches:
your interpretation is apt, those are A/B slots. It’s a redundant partition scheme to switch if booting fails from the other slot. With fastboot you can query and switch the slot, either in menu or via the cli command.
“Different looking recovery mode” - that is fastboot vs fastbootd. The blue colored font is fastbootd. Green “START” headline is lower level regular fastboot.
In general the flash process seems incomplete. If the web installer fails you, going the cli route is more robust, see the link posted by piero.
Sure, web installer didn’t warn about security patch level. I did the same misake bricking my phone - I just forgot that it needs to be checked before installation. There are two solutions:
At the moment I’m mentally preparing to deal with the cli stuff.
So, I’m in the slot that holds the original OS. What I don’t understand is why this OS also fails to boot. And I don’t see an option to switch to the other slot.
However, I’m not sure if finding answers to those questions is relevant right now.
I have just one small issue. The manual says to lock your Bootloader before rebooting, but the phone rebooted automatically when the install script was done. Any advise on how to proceed?
you can relock at any time, but make sure to know the security patch level (a date) from stockrom, in doubt wait until after updating to 3.1.4 that will be ahead in SPL
I triple checked before starting the installation, but since I ultimately used an alternative instalation method I’m gonna take your advice and wait for the next release. Thank you very much.
