FP6 install e/os/ via e/os/ Installer Stuck Bootloader

Using /e/OS Setup
,
1

Hello,
Bought a FP6 today

Setup the minimum
I followed the instructions of the e/os/ installer (activated dev options, usb debug, auto file, oem unlock with a code).

Couldn’t detect the phone in bootloader mode via fastboot.

Found I had to update the phone, so I updated Android. There I activated OEM Unlock and no code was necessary.

There I got the Windows Update Drivers displayed, so I installed them.

Then i detected the phone in fastboot, and e/os/ installer, after redoing the first steps, detected it too while in bootloader.

I unlocked the bootloader when the installer made the phone ask me to unlock it.

The installer gone through the next steps (asked me to redo the android setup, dev options, debug, auto file).

The installer then did it again once, and then had a long step of installation (recovery.img and others).

Then it finished, the installer tells “you will see the following logo, …”. Indeed it displays it, then the boot animation, and reboots, displays “bootloader unlocked, security risk” then the E logo, and loops this way 3 or 4 times.

And now, the phone restarts automatically in bootloader mode, if I click on power when on the entry start”, it goes back to the bootloader mode.

I used the command : .\fastboot flashing get_unlock_ability, got this :

(bootloader) get_unlock_ability: 1
OKAY [ 0.001s]
Finished. Total time: 0.005s

So I locked it back, thinking I had to lock it (weird but ok), but it still goes to bootloader.

If I try to go to recovery, it goes to bootloader. I unlocked the bootloader.

Did I just broke the phone while following the e/os/ installer instructions ?

1 Like
2

No almost certainly you will recover it quite easily.

This happens when eosinstaller fails (for whatever reason) the phone is not broken if you have a working Fastboot mode. The flashing of both recovery and system failed. You can check any of the other threads with hashtag eosinstaller to read previous advice.

Beware, did you fully take in the anti-rollback hazard? See below.

Regular manual command line install page Install /e/OS on a Fairphone The Fairphone (Gen. 6) - “FP6”

PS

You must not be alarmed at this. The phone will be unlocked for the duration of the install process.

1 Like
3

I’m nearly in tears, and the Howto is way too long for me to handle calmly at any time (I can’t handle long process, that’s why the e/os/ installer was great for me and why I didn’t spend another 110€ to have a FP6 with e/os/ pre-installed).

Abouth the “anti-rollback” I don’t understand. I read this :

Your phone has a security feature called anti-rollback protection. This prevents installing older software versions once a newer one is installed. If you try to install an older software version while your bootloader is locked, you may trigger an anti-rollback error and brick your device.

So, there’s a security feature that will kill the phone if you make a mistake ?

So… Should I retry with the auto installer, or try to cope and read the kilometer long Howto ?

And when I read just the beginning of the guide I see this :

our Stock OS Android version, must be the latest available relative to the /e/OS build you want to install → not higher ! (this don’t apply to Fairphone devices)

But I don’t even know the stock android version because I just updated and used the e/os/ installer.
So I can’t even know if the auto installer used a correct version, or used an inferior one…

new version on witch you want to relock the bootloader, must included a NEWER (or the same) “android Security Update" aka "Security Patch Level” date (SPL),

otherwise you risk to change your device into Brick.

So I won’t be able to lock it again once it will be installed correctly, because MAYBE it’s not the right version to do it, and then maybe definitely lose 500€ ?

SO now, what do I do ? I don’t have the SPL noted down, because the auto installer seemed safe, but I can’t access anything now…

(the timeout between two messages will prevent me having a functionnal phone, increases my stress because I don’t know what to do, and will prevent me to ask for specific help during/before the process…)

4

Hello @Georges6, Welcome to the /e/ users forum.

it is a 3 steps process.

so can skip the last step for now,
you will have to wait for the next /e/ update release to relock the bootloader
(if you see advantage to relock it)

5

Fully understood. A period of adjustment must happen.

The Howto is necessarily long to try to cope with all the different situations users might find themselves.

Please read it alongside the manual install page. The actual flashing work is done by a script.

1 Like
6

Let’s deal with this early.

Did you keep a note of the command(s) used?

What is the result of these now?

.\fastboot oem device-info

.\fastboot flashing get_unlock_ability
1 Like
7

Don’t worry. You can do it again.

You can get code to unlock device from Unlock your Fairphone’s bootloader and you can return to process using manual docs.

I got similar with loop, did it 6 days ago. After unlock device, I finished it doing manual process which is very simple.

1 Like
8

I meant that the post was really long. Too many data, it stresses me out.

Okay, so I should be able to install, and for now not relock the bootloader.

Please read it alongside the manual install page. The actual flashing work is done by a script.

okay, the 2nd step, with

(replace “FP6” by your device codename)

chmod +x flash_FP6_factory.sh

then

./flash_FP6_factory.sh

You meant ? Okay.

Hum, just a question, for the time there’ll be a new eos version/update and SPL increase, when I’ll lock again (I need some banking apps). And I guess the update of e/os/ will be with the classic settings menu ?

It’s written

BUT NEVER DISABLE “allow OEM unlocking”, in “Developer Options”

Why ? When we relock the bootloader, we shouldn’t deactivate this ? But, dev options would be deactivated with my bank application, ‘cause of the card payment option.

Or just, maybe, I’ll use my previous phone for this specific use case only…

Did you keep a note of the command(s) used?

I used adb devices, adb reboot, adb reboot bootloader, fastboot devices, fastboot flashing get_unlock_ability, fastboot flashing unlock.

.\fastboot oem device-info

(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: true
OKAY [ 0.003s]
Finished. Total time: 0.004s

.\fastboot flashing get_unlock_ability

(bootloader) get_unlock_ability: 1
OKAY [ 0.001s]
Finished. Total time: 0.001s

Thanks for your help. I’ll try it and I’ll tell you when it’s done/error.

Edit : THANKS aibd ! It worked ! Now I’ll wait for the next update of e/os/ to be able to relock the bootloader, that’s it ? Is it sure the next update will update the SPL, or do I have to wait more to be 100% Sure ?

After your answer (or anybody else with safe knowledge, I’ll tag your first answer as the solver !

1 Like
9

if you do that, you will get_unlock_ability: 0

in case of problem where android system don’t boot, you will be stuck with impossibility to unlock the bootloader, and reinstall any OS.

2 Likes
10

Good to hear that you flashed your FP6 so fast.

So you can find the Android SPL of the current latest release from

https://support.fairphone.com/hc/en-us/articles/18896094650513-How-to-manually-install-Android-on-your-Fairphone

But it seems that it matters quite significantly whether your FP6 was running a15 or a16.

No crystal balls. You must get satisfactory evidence before you lock.

2 Likes
11

Thanks for all the additionnal information y’all gave.

I’ll do that when I’m sure.

Thanks for helping me, and now I’ll transfer my esim, then customize the FP6 (don’t really like Bliss Launcher, or any launcher without an app tray).