Ok after a failed web installer try I am going for manual according to Install /e/OS on a Fairphone FP4 - “FP4”.
I followed all instructions (so I am in the developper mode) yet OEM unlocking is grayed out.
I did first booted in bootloader mode and then restarted and proceeded. Would that cause the issue. If they don’t me to boot in bootloader mode at that point: then say that clearly (don’t be vague with “This section will be relevant later throughout the guide, when you need to reboot into bootloader mode.” Does that mean already do it or not??
I really get annoyed by this unnecessary friction. I mean I understand it’s free and people are working hard but why the extra friction. I can’t even raise the issue directly with them (again friction… ).
Just to rule this out … is there any chance that there was a Google account, passwords or PINs left on the phone before the run with eosinstaller ?
Warning: Before proceeding with the installation, log out of any accounts you may have set on the stock ROM. Also, remove any screen locks that have been set on the device.
This is after allow USB debugging (again)?
I suggest also to boot into Fastboot mode, then run each command in a terminal and show the output
I never logged in to my Google account, entered a password or PIN (well apart to unlock the phone screen).
USB debugging: this is not in the manual installation. I did it now. Still OEM gray.
fastboot devices → (my serial no) fastboot
fastboot oem device-info →
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.009s]
Finished. Total time: 0.010s
fastboot flashing get_unlock_ability →
(bootloader) get_unlock_ability: 0
OKAY [ 0.002s]
Finished. Total time: 0.004s
Maybe OEM is grayed out because I am already in unlock mode because of the failed webinstaller? If so I tried the next step in the manual (while in FP A15) " Reboot on fastboot by running the command in the PC console adb reboot bootloader" It said something like no device found (I don’t remember the exact wording as I am now in fastboot mode).
PS: so I just now had to learn that ‘fastboot mode’ = ‘bootloader mode’. Please stick to e/OS terminology.
i started stock A15 again and for some reason now the command adb reboot bootloader works. fastboot flashing unlock I got something to the extent of already unlocked fastboot flashing unlock_criticalI got something to the extent of already unlocked
