Hi! I tried following the web installer for Fairphone 6. I followed all the steps, but for some reason the progress froze on step 22 at 92 percent. I waited for over an hour, and it did not budge.
But I managed to boot back into the stock system that came with the phone, and reinitiated the install process. This time it skipped a whole lot of steps, and got passed step 22. The webinstaller said the system was installed, and told me to lock the bootloader again and let it reboot.
This is where the true nightmare starts, because now I seem to be stuck in a bootloop. After hitting START on the bootloader, the Fairphone-logo shows for half a second, then the Murena-logo. After a little while the screen goes black, and I go back into the bootloader.
Going into the Recovery-mode gets me into /e/OS recovery. Factory reset does nothing.
Is my device completely bricked? Can this be salvaged?
What do you mean? I followed the steps of the web-installer for eOS. I got to the part where it said the system was installed, and I should lock the bootloader. There were more steps left after this, but I could not get further because /e/OS wonāt actually boot.
I am apparently time-limited with my replies here on the forums, sorry for such a slow answerā¦
In the bootloader I have these options to choose from:
START
Restart bootloader
Recovery mode
Power off
Boot to Alternate Slot
Ah, I see. Well, I had no intentions of being an early adopter of that I went to the main website (e.foundation) and clicked āDownload and TRY!ā, and then I clicked the āCheck Device Compatibilityā button. This took me to the installer, which verified that my device was eligible and took me through the steps.
I did not mean to communicate blame on you ā¦ but there is no method known to me to get a log of where eosinstaller failed. Perhaps check threads with that hashtag.
Going through the Command line / manual install method will still work.
This implies that e-Recovery installed ok but some other partition(s) of system failed to flash.
Oh no, I did not take it that way at all! Iām just saying the process guided me to this web-installer naturally. And since I discovered that Murena sells FF6-devices with their OS installed (after I bought mine ofcā¦) I assumed it was rather safe to go ahead when the installer confirmed that everything was working
Iāll just have to go ahead and try the Command line / manual install method thenā¦ I hope itās rather step-by-step, because Iām not that good at this stuff But from what Iām reading in the documentation, it tells me to go into my device and unlock the bootloaderā¦ I assume itās locked since that was the last thing the installer told me to do before rebooting into an endless loop. Is it possible to āunlockā it without a working OS? Or is it still unlocked since I get sent to boot in the first place?
It would be nice to have some sort of logs for that web-installer tho, Iām sure that wouldāve explained a lot of my issues
Yes, but the phone asked me if I wanted to lock my device during the last step I did before I got stuck in the boot-loop (the second time I tried, after I redid the install after getting stuck at step 22). The web-installer told me to do so, so ofc I did
In retrospect I find that odd, since as an end-user I had yet to confirm if the system actually worked before I did that. Perhaps this should be a step AFTER the end-user confirms that it works?
In the bootloader screen with the green START there is a value that says āDEVICE STATE - lockedā; could this be the bootloader that is locked?
with adb devices I cannot locate the phone on my PC. But with fastboot devices it shows up. Running the flash_FP6_factory.sh script has me stuck at āLooking for connected device(s)ā¦ā
Were you told by the web-installer to lock the bootloader as well before rebooting the system?
This is normal at this point. ADB is the Android Debug Bridge, it works only when any Android OS or a compatible recovery mode is booted. It doesnāt work in fastboot mode (aka bootloader).
This is the way.
In fastboot mode, what does the command fastboot flashing get_unlock_ability give you, 0 or 1?
If the web installer itself doesnāt complain anymore about not being compatible, we should assume it is compatible. /e/OS online documentation has a tendency to lag behind.
The bootloader is locked now.
We are trying to establish whether it can be unlocked again before proceeding with anything.
It is a new phone, and the new flagship of the /e/OS ā Fairphone partnership. The web installer wasnāt ready to handle the new phone at launch (sadly), but of course the incompatibility would not last forever.
The former Easy installer is no more, it was superseded by the web installer (ā/e/OS installerā).
I know, but again, the FP6 is not mentioned. Itās a good reminder for new buyers of the FP6 or other smartphones to be careful before installing /e/OS on their smartphone.
This command returns 1; does that mean there is still hope?
That might be, but let me take you throug exactly how I ended up here.
I went to the e.foundation website.
I clicked Download and TRY !
Here you could browse āShow supported devicesā, but since they sell this as a phone themselves I assumed that bit was in the box, there for I scrolled further down and found
Check device compatibility - I clicked this button, and it took me here.
I followed the instructions on-screen.
Now Iām not out here to blame people. I just want to make the process better and safer, because privacy is important. If the phone is listed to work with eOS in the first place, I think itās not ridiculous for the uninitiated to believe in the process they get taken through on the website. Failsafes should probably be in place, to make absolutely sure people do not mess up their stuff on a permanent basis wit the web-installer. In this case, having the web-installer itself informing the user that the web-installer is not yet confirmed supported on the current device would go a long way. Iām certainly no tech-guru (as you obviously can see ), but I do care about better basic privacy.
1 signifies that you are expected to have unlock ability. Great!
So Steps 1 ā 5 are to get you safely to Fastboot mode.
So you should now be ready for step 6. I guess you would particularly want to see your Bootloader screen transit from locked to unlocked before you run the script.
Ah, I see. Proceeding to Step 6 I type in fastboot flashing unlock in a linux-terminal. From what I can gather, I am supposed to get some sort of message or pop-up on the phone where I can confirm this action, but this does not happen it seems? Not in Bootloader, not in recovery, and not in the fastboot-section of recovery.
There is a tip/note about running all commands in an adb-console - does that just mean adb is present and working on the device? Or can I somehow run adb and then type these things in as commands?
I went to the main website (e.foundation) and clicked āDownload and TRY!ā, and then I clicked the āCheck Device Compatibilityā button. This took me to the installer, which verified that my device was eligible and took me through the steps.
