Hi Ingo, while I myself am useless for contributing to this work here, let me just say that I very much like how you are helping with making it easier to install an alternative OS with less Google baggage. Just wanted to clarify you’re not posting into a nirvana here. 
6 Likes
BTW, I solved my problem by going for the second option.
And while testing the installer I found a few things here and there which are also fixed now.
In fact I was able to run the installer from my IDE and successfully flash the FP3.
On the first boot after relocking the bootloader I shortly saw the LOS recovery and another reboot.
So at the moment I’m not 100% sure the flashing was successful, because on the one hand /e/ boots, but then I already had it installed before and I haven’t checked if it not just booted the other slot already containing /e/ as well.
I should probably (learn to) reflash stock ROM and really try from scratch.
6 Likes
First working alpha (from sources, no binaries yet) available
In order to not write it all twice: details at https://community.e.foundation/t/e-os-easy-installer-development-thread-about-adding-new-devices/15461/44?u=ingo_fp_angel
5 Likes
I’m somewhat stuck because of the unlock code mentioned in https://support.fairphone.com/hc/en-us/articles/360041655711-Unlock-the-bootloader-of-your-Fairphone-3
I’m one of the people who didn’t need that code, so the current version of the /e/ installer is not able to install on FP3s where this unlock code is needed.
Is there anybody who had to enter the unlock code on their FP3? I’m trying to find a way to determine if an FP3 needs the code or not.
Maybe the output of the following command would be help, but I need someone to run it on “the other type of FP3”:
fastboot flashing get_unlock_ability
For me it’s just this in locked state:
$ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 0
As requested this is my result upon DEVICE STATE - locked:
iMac:~ adrian$ fastboot flashing get_unlock_ability
(bootloader) get_unlock_ability: 1
OKAY [ 0.014s]
Finished. Total time: 0.015s
Thanks. It looks like it just shows if unlock is enabled or not. No hint if a code is needed or not.
Just a small heads up: I hope the FP3 support will soon be added to the /e/ easy installer: https://gitlab.e.foundation/e/tools/easy-installer/-/merge_requests/59
And while the installer at the moment only is tested and packaged for linux, today I integrated the two work-in-progress (WIP) branches of my FP3 and the windows support done by /e/ to check that flashing the FP3 will also work with windows. And in fact I was able to flash my FP3 on windows, too, with the WIP version of the installer
8 Likes
How are you actually testing the installer? Do you have a 2nd FP3 for that?
Yes, exactly, I’m not doing these kinds of experiments with my daily driver.
And strictly speaking I’m not testing my changes as an end user would do. The official installer is provided as a snap package. But I don’t know how to create those. The build tools can automatically create a ZIP file that contains all binaries, so I’m using that.
Which could mean that there are still obstacles while creating/using the snap. But as I understood is something the /e/ team would handle if it came up.
Ok, got it. Just curious: Did they provide that 2nd phone?
No, I bought it myself. For the purpose of (beta) testing things (like getting new custom ROMs to support the FP3 even if I can’t do the porting myself or official Android 10 support later).
5 Likes
Small update: I’ve added FP2 support to the installer. Let’s see if my changes get accepted.
More info (plus binaries download link) at https://community.e.foundation/t/e-os-easy-installer-development-thread-about-adding-new-devices/15461/71?u=ingo_fp_angel
It would be nice if someone could test and report back. I’m especially interested if the detection of the phone works properly. The embedded adb seems to take some time for the adb devices -l step that doesn’t happen with the platform tools installed locally on my computer.
5 Likes
As the Easy Installer now seems to work with the FP3 as well, I wonder whether it also provides the unlocking of the bootloader or if that needs to be done on the FP3 before running the Easy Installer?
I was offline for a while but the /e/ devs continued working on the FP3 support.
I had a quick glance at the changes they did while I was away and it seems they’ve added a step that points to the official unlock instructions on the FP homepage.
But I’m not sure if they’re finished.
3 Likes
I actually tried the Easy Installer (via Windows 10) on the FP3 last night. Unfortunately, while it correctly identified the device as an FP3, it would regard it as “not supported” by /e/OS both when Fairphone OS Android 9 (A.0120) was installed on it as well as when Fairphone OS Android 10 (A.00045) was installed. I had previously succeeded to install /e/OS – using the step-by-step instructions – on the FP3 even when the latest Fairphone OS Android 10 was installed right before.
3 Likes
There seems to be a problem with the /e/ documentation (i.e. the device page): the work on the FP3 is not yet finished.
On the installer page https://doc.e.foundation/easy-installer you can actually not see the FP3 yet.
4 Likes
Thanks for the quick clarification 
BTW, the FP3/FP3+ support has now arrived at the /e/ easy-installer: https://community.e.foundation/t/the-e-os-easy-installer-now-supports-the-fp3-fp3-and-its-contributor-tells-us-all-about-it/23125?u=ingo_fp_angel
I wouldn’t close this topic (or mark this post as solution) as there’s still support for the FP2 to be added.
7 Likes
Not sure what it would take to get the FP2 officially supported in the easy-installer.
As long as that didn’t happen, I can provide new binaries from time to time.
Just follow this topic in the /e/ forum: /e/ OS “easy” installer: development thread about adding new devices - Easy Installer - /e/ community
3 Likes
This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.