Thanks for your help.
I found out about this in Step 3 of Installing /e/OS.
However I cannot install e/OS:
./flash_FP6_factory.sh
INFO: You are using a Linux distribution.
INFO: Looking for connected device(s)...
Could not start dynamically linked executable: /home/klt/Downloads/FP6/bin-linux-x86/fastboot
NixOS cannot run dynamically linked executables intended for generic
linux environments out of the box. For more information, see:
https://nix.dev/permalink/stub-ld
Most of the programmes in bin-linux-x86 are installed, e.g. /etc/profiles/per-user/klt/bin/fastboot but the versions might not be the same.
Just ordered my FP6 (and another one for somebody in the family) and will flash e/OS when they arrive.
The instructions seem a bit more complicated than what it used to be, when I flashed my last phone with LineageOS. But that should not be an issue, if all steps are followed.
Does anybody know if the FP6 is included in the âsome devicesâ category for VoLTE and the IMS? Or does it work without first using telephony (because I donât want to get a new eSIM 3 times)?
Additionally, some devices require that VoLTE/VoWiFi be utilized once on stock to provision IMS.
Hey, did you have the very same dates for the security patches on both your Android version and /e/OS build as in example 2 of the install doc? Just asking because on my wifeâs FP6 itâs May the 5th, while on the current /e/OS build itâs June the 5th.
Google Android anti-roll back feature is supposedly a way to ensure you are running the latest software version, including the latest security patches.
ERROR: Could not erase the misc partition on device ae0c35fb.
ERROR: Please unplug the phone, take the battery out, boot the device into
ERROR: fastboot mode, and start this script again.
ERROR: (To get to fastboot mode, press Volume-Down and plug in the USB-C)
ERROR: (cable until the fastboot menu appears.)
ERROR: Aborting now (press Enter to terminate).
I did remove the battery and did run the script again but the error persists
I already flashed several fairphone 3s 4s and 5s and never seen this error before
UPDATE: I got it to work now. (But i donât know what made the difference)
After the 4th flashing it worked like a charm =)
In case you installed /e/OS on your FP6:
Donât try to revert to Fairphoneâs Android OS for the moment, as you currently risk bricking your device when doing this, and as of now it isnât clear why this happens!
What is clear is that you shouldnât revert from the upcoming /e/OS 3.0.3 with the June security patch level to any Fairphone Android OS with May security patch level (see Fairphoneâs release notes for this), because this would trigger Android rollback protection.
But /e/OS 3.0.2 was confirmed to have May security patch level, so this shouldnât be the cause for the current brickings.
If you want to help to get to the bottom of this:
When in fastboot mode, run the command fastboot flashing get_unlock_ability before attempting to relock the bootloader.
Donât relock the bootloader if the result of the command is 0!
First try to get the OEM unlock setting enabled again in the Android Developer options and only try to relock the bootloader if back in fastboot mode the result of fastboot flashing get_unlock_ability is 1!
Please report successful relocking here or in the Fairphone forum (if you still dared relocking, brave soul)!
Please follow proceedings here (might be difficult to keep 2 forums up to date all the time) âŚ
I got a brick when I went back to stock from EOs. I tried to boot after installing stock, and now Iâm bricked.
Iâve contacted Fairphone, and theyâre blaming me for everything and for not reading the instructions. Thatâs not true, but oh wellâŚ
Anyway, Iâm trying to return my phone to Fairphone since itâs only 5 days old.
If anyone has a solution, Iâd try it⌠Thanks everyone.
That was before Murena cleared up here that you didnât perform a rollback, as it initially would have looked like judging by the FP6 install instructions (which wrongly list June 6 as the security patch level, which will only become true with /e/OS 3.0.3).
Please insist on Fairphone to take into account the following information:
ok thanksâŚ
I donât know if Iâll get a response from Fairphone. Iâve sent several emails. In the end, I think Iâll decide to return the phone. Iâm still within the 14-day trial period.
Hi all - I got a Fairphone 6 today intending to install /e/OS using a fresh installation of Linux Mint, but Iâve encountered numerous issues along the way. I managed to get to step 5 here, but Iâm having the same issue as described here:
Running the command fastboot flashing unlock results in the perpetual waiting described in that message. Iâm led to believe the phone just isnât transmitting data through the cable while in the bootloader and thus the terminal isnât picking it up, but I havenât found a way to fix that, no matter how many USB ports I try. Trying sudo fastboot flashing unlock as suggested later did not have any effect, either.
Any logical next steps? Something I might have missed? Many thanks, I really do not want to use the default OS more than I have to.
Have you checked this is the case for you @kijelilon?
After Factory reset (with unlock) the phone is expected to return to Factory settings so the OEM unlock must be done again.
As all of this Enable USB Debugging and OEM Unlock would have been done in a safe way if the instructions were followed exactly before you got to No 5 you quote.
