Web installer fails at the bootloader step with error - FP4

Community Web Installer
,
1

I have tried installing Murena /e/OS on my Fairphone 4, but I get an error message:

Error on step: connect-bootloader
Cannot execute command connect bootloader
The device is not connected Failed to connect: Cannot connect Bootloader
Proposal: Check connection and that no other program is using the phone and retry.

Am I to understand that this is probably due to my using a USB-C to USB-A USB 2.0 cable? There appear to be various USB-C to USB-A USB cables for purchase. USB-C to USB-A 3.2 Gen.1, USB-C to USB-A 3.2 Gen.2, USB-C 3.1 to USB-A 2.0, etc. A bit of a mess… What do I need?

2

you can test your cable with : fastboot devices

you can have a try with : Install /e/OS on a Fairphone FP4 - “FP4”

1 Like
3

Did you activate the developer options and did you set all necessary settings?

If you are on Windows a driver is needed when the device switches into all the modes (fasboot for bootloader, etc.).

4

Yes, I activated all of the necessary settings. I am using Linux. Wondering if this could be done with FreeBSD as well :thinking:

5

I did an installation on Mint with Ungoogled Chromium yesterday and I had no issues. Try to follow every step correctly.

2 Likes
6

I just tried using the web installer, using a different computer, running LMDE and using the Chromium browser. Same error.

The bootloader is reading “start” in green. Is that as it should be? The installer detects “Android” instead of Fairphone 4 at the bootloader.

7

Pictures of Computer and Smartphone would be gold.

The whole installer is not only on the Computer you also have to do things on the Smartphone.

8

This page Web installer | Install | GrapheneOS includes the need for udev rules being present / set up for the target phone. Also a few words on establishing that you are in fastboot mode.

9

OK, thanks. After having read through the documentation, I installed android-sdk-platform-tools-common. This seems to have been the issue. After that, the installation completed without any errors.

Unfortunately, my phone will not boot into the system. I just keep getting the bootloader :scream: What is going on and how do I solve it?

10

So you got e-Recovery ok?

Does Recovery offer to Format factory data or Factory reset might be worth a try.

Does the Bootloader confirm that the phone is unlocked?

11

There is a recovery mode, but I am unsure what it will try to recover to, and whether it will be successful.

Device state, as it is called, is unlocked.

—-

There is e-recovery.

——

I tried the boot system option and it went back to the bootloader. Now I no longer get e-recovery.

12

It will be much easier to manual install as Install /e/OS on a Fairphone FP4 - “FP4” than to debug web-installer.

fp4 is installed by a script, so it is not so hard.

Does web-installer indicate that it has kept any kind of log? Without that, advice from here would be based on guesswork.

Web-installer will have started to install the Official build, so I suggest you use that rather than the Community build.

1 Like
13

I think the priority here is how do I recover the phone from this, not installing another system on top of something that doesn’t work, but that there is no information about…

14

Indeed, and I am not one to say that an automated install is a good thing.

The guesswork is that maybe the script did not complete – this is quite commonly seen in manual install where one partition fails to flash, with the result that the script aborts intentionally – this is deemed the safest wording for the script. Seeing this, one can confidently just re-run the script until it succeeds.

The phone is ok, all the time you have a functioning fastboot. There is the expectation that system and recovery are clearly overwritten and replaced by any install instructions.

The most severe hazard is if there is any risk that you trip anti rollback. This hazard is fully explained in the install page I linked.

… but the web-installer is only automating the manual method and my comment about official was to ensure that you did not attempt to install something different.

1 Like
15

Wow. That actually worked. Thanks. I have read posts about people bricking their phones, so I have always viewed either the snap package or the web install as being the safest way of doing things

1 Like
16

The web-installer doesn’t really show any way to see a log. There are ‘Popup’ messages that something is wrong. But for people who aren’t aware of manual install and all the steps, it is pretty difficult to get a read.

I will check @globetrotterdk try with the plattform tools if that is needed. I do not think so, but I’ll give it a try to debunk it.

@globetrotterdk Is your installation now succefully done?

17

Thanks for your follow up @mihi . Different distros handle udev rules (mentioned in the GrapheneOS web-installer) in different ways …

android-sdk-platform-tools-common

… seems the way to provide udev etc for this distro.

Debian (and I think Ubuntu) provides a solution by the same name android-sdk-platform-tools-common. In Debian and I expect the other distros the common package is marked as a dependency when one system installs platform-tools. Seems it is recognised not provided by Graphene web-installer.