Problems trying to install e/os on FP4

[rsk]

I’ve read a few threads by people having similar difficulties but still can’t find a solution so I would really appreciate help..

I’m running Linux mint

I’ve tried the e/os web installer multiple times, as well as manual installation. After downloading, I get the following:

[ An error occurred while trying to unlock or check the bootloader. Make sure oem unlocking is enabled in developer options, then try again.

Device does not report as unlocked (expected “Device critical unlocked: true”) ]

I think this might have something to do with the fact that oem unlocking is toggled off and greyed out (so no option to toggle on) with status: Bootloader already unlocked

[fastboot oem device-info] yields waiting for any device

[fastboot oem_unlock] yields (bootloader) verity mode:true, (bootloader) Device unlocked: true, (bootloader) Device ciritical unlocked: false, (bootloader) charger screen enabled:false

[fastboot get_unlock_data] yields fastboot: usage: unknown command get_unlock_data

[fastboot flashing unlock] yields FAILED (remote: ‘Device already unlocked!’)

[fastboot flashing unlock_critical] yields FAILED (remote: flashing unlock is not allowed)

These are commands i’ve gleaned from various how to fix it threads but i don’t actually know what i’m doing with this stuff. Can anyone help??

[Lidwien]

I wonder if you have enough rights on the computer and is your phone found by your computer?

I have writing this in Dutch, but the commands are the same in English.
$ lsusb
geeft: Bus 002 Device 008: ID 18d1:4ee7 Google Inc. Nexus/Pixel Device (charging + debug)

Dus bij mij is vendorid ‘18d1’ en ‘4ee7’ geeft ‘goto ADB’.
Ik gebruik het programma ‘gedit’ om bestanden te bewerken.
Van het internet heb ik android-udev-rules/51-android.rules at main · M0Rf30/android-udev-rules · GitHub
gedownload en met gedit heb ik deze regel toegevoegd aan de gedownloade file:
SUBSYSTEM==“usb”, ATTR{idVendor}==“18d1”, ATTR{idProduct}==“4ee7”, MODE=“0660”, GROUP=“plugdev”

Daarna de gedownloade file verplaatsen:
[root]$ mv 51-android.rules /etc/udev/rules.d/
Nu de juiste rechten geven:
[root]$ chmod a+r /etc/udev/rules.d/51-android.rules

Daarna moet de service ‘udev’ opnieuw worden gestart om de rechten te activeren:
‘service udev restart’ of ‘systemctl restart udev’ of ‘systemctl restart systemd-udevd’
(afhankelijk van de Linuxversie die je draait)

Let op: je moet de group plugdev aanmaken en zorgen dat jij daar rechten hebt:
[root]$ groupadd plugdev
Check hoe je bent ingelogd:
$ echo $USER
Dit moet jouw inlognaam weergeven. Daarna kan je je inlognaam toevoegen aan de groep ‘plugdev’:
$ sudo usermod -aG plugdev “$USER”

Maak een directory ‘platform-tools’.
Download het programma https://dl.google.com/android/repository/platform-tools-latest-linux.zip in die directory ‘platform-tools’ en pak daar de zipfile uit (met unzip).

Installeer het pakket ‘android-tools’, dit levert o.a. de programma’s adb en fastboot.

Let op: haal op je Fairphone de screen lock weg en verwijder al je accounts die op de telefoon staan.
Doe je dit niet dan kun je straks onder /e/OS geen screen lock instellen.

Installeren /e/OS

Wat je ook doet, de bootloader niet locken. Want Murena loopt achter met de security updates.

[rsk]

Thanks for replying, but even put through an english translater this does not mean much to me.

It’s worth mentioning I took my phone to a computer specialist (although not an expert with phones) and he had the same problem, so I’d be surprised if it was to do with computer rights

[Lidwien]

Connect your phone to the computer and type

lsusb

What is the outcome?

Do you have a file

/etc/udev/rules.d/51-android.rules

[yvmuell]

@rsk

oem unlocking is toggled off and greyed out (so no option to toggle on)

So critical is locked and you cant unlock correct?

You might have a chance by using root to reset unlock ability

Trapped in fastboot mode with locked bootloader and corrupted custom ROM

Sure Keep in mind that I haven’t tested this, because I didn’t lock my bootloader afterwards and I can’t guarantee that there’s no possibility left to brick your phone! With that out of the way, download the boot.img and the Magisk.apk (for others trying this on a different ROM, please use the corresponding boot.img for that ROM!) from those two links to your PC… …and enable ADB debugging on your FP4 if you haven’t already. Install the Magisk app by either running a…

[urs_lesse]

Just for cross-reference:

Trying to install eos on Fairphone 4

[rsk]

this thread refers to someone installing calyx os . Could anyone convert it to a set of instructions for my specific situation? Bearing in mind I don’t know what any of it means, but I can follow clear instructions

[yvmuell]

How to root is described here you need for sure use the e/OS boot img

FP4 Root Access is possible, maybe a bit risky

Disclaimer: You do this at your own risk! I’ve been running my phone this way only for about an hour, this might still eat your data, make backups! I managed to get Magisk working, here’s what you need: Unlocked bootloader adb & fastboot Magisk app installed Either the stock boot.img provided by Fairphone (check Settings → About phone → Build number for the version you need, just use the newest one if you are on a version not yet available) Or, if running an OS other than stock, …

[rsk]

these instructions are a bit beyond me, which probably means that rooting is beyond me. If there was a set of clear step by step instructions, i could probably follow them

eg. what does it mean to patch the downloaded stock boot.img

[yvmuell]

Else at the beginning I think IodeOS didnt require to unlock cirtical when I remember correctly may see if you can install this somehow. Else maybe only FP can help you

[gabs]

May be the best way to find help is to search for a local community and someone there with an installed /e/OS .

[rsk]

how would that help??

[Meaghan]

You could find a local Angel to sit with you and help with the process.

[rsk]

Ok, someone who knows about rooting. I’ll look into it

[rsk]

Apparently there are only 2 angels in England. That’s a dead end then!

[FPbonn]

The iode shell script does not make any checks, but it tries to erase and flash the avb partition, which is a critical partition.

[yvmuell]

I have no idea what you want to say?

[FPbonn]

You suggest to try iode, but this also won’t work with the critical partitions locked.

[Volker]

You might use fastboot flashing lock to lock your device. This would enable the “oem unlock” slider in your device and you could start from scratch.
BUT locking the device migh brick your device, depending on what exactly you’ve done before (if there was a downgrade of the security patch level (SPL) involved). I wouldn’t expect it based on what you’ve written. But the risk remains! In case of bricking it you’d have to send it in to FP for a repair.
So this solution is rather is a kind of “last resort” because of the potential risks involved.

[rsk]

is this the same as locking the bootloader?