I am very new at this… I don’t understand what is meant in a lot of instances in the setup guide for /e/Os on FP5.
What is meant by"** Reboot on fastboot by running the command in the PC console adb reboot bootloader**"??? I haven’t got a clue… How do do I run a command? What is the PC console? Quite literally: Where do I type what?
What in meant by " Ask for unlock with fastboot flashing unlock"?? Who or what do I ask, and how?
“Unlock critical with fastboot flashing unlock_critical” What the actual… still haven’t dot a clue.
Considering FP5 that have simplified instructions, only steps (1), (2), (3) then (5) and (6) of the following guide are mandatory, the rest is done automatically by the flash script
Hi Piero.
Thank you for the info and your patience with schooling me…
However, I seem to not be able to execute the first step of installing the flashing tools.
does this mean that whatever needed to be done, was done?
considering steps 2 and 3 of the HOWTO, I should have taken care of that because I followed the easy install webpage untill it refused at step 9/31 because the PC didn’t recognised the a device.
however , at step 5 of the HOWTO, things become vague to me ( * I require baby steps…)
It says to use it as a adb sideload. I don’t understand what that means.
I have the file [IMG-e-2.8-t-20250219470165-official-FP5.zip] downloaded and extracted as follows.
The Howto is generic,
the procedure is simplified for Fairphone devices you don’t need to flash the recovery then install /e/ from it,
Step (4) is unneeded, and Tasks described in steps (7) and (8) or (9) are done automatically by running the chmod +x flash_FP5_factory.sh && ./flash_FP5_factory.sh command
I have now loaded the files from [IMG-e-2.8-t-20250219470165-official-FP5.zip] into the folder “platform-tools”. THen I entered the following in the command prompt:
Then th pc asks me to select a application to open the file.
What application do I use? Or am I in the wrong direction alltogether?
Download an /e/OS build I have this file downloaded and unzipped. Now pasted in the same folder as the adb file. I suspect that isn’t correct, judging by the reactions…
Unlock the Bootloader Here I cannot make out anything the Howto wants me to do. Could you help me out here in human language?
I kindly request a point-by-point reaction, because I couldn’t make out what some reactions to my questions were refering to exactly. Hope this is OK?
I didn’t see in your comments where you actually got adb connected to the phone. When you enter the command “adb devices” it should return the serial number of the phone. If it returns a blank line, adb does not see the phone. On the phone check USB debugging is enabled in Developer options and the mode is file transfer. Verify you’re using a data cable and not a charging cable.
In some cases the phone needs to be awake when you plug in the cable where you’ll get a notification to enable USB debugging and which mode to use. My phone sleeps through that and I don’t get an adb connection until I wake it up.
When you run “adb reboot bootloader” you should see on the phone it has rebooted into fastboot mode. Enter “fastboot devices” to see the PC is connected in that mode. It should return the device serial number. If it returns a blank line there’s a problem with the PC driver. Fastboot requires a driver that can be obtained from Windows Update automatically. The driver for adb is canned with Windows 10 and 11, Windows does not need to download it.
The file “flash_FP5_factory.sh” is a bash script which means it has to run in a bash shell. You’re trying to run it in a Windows command shell (cmd.exe). Bash is native for Linux, but on Windows you have to use Git Bash which has to be downloaded. Also, in bash you have to proceed a script with ./ to run it (or specify the whole path to run it). That’s not the case for the Windows command shell.
I have tried again with the phone “awake”,to run adb in the command promt and it says the following.
Now I tried ‘adb reboot bootloader’, and the following is shown:
I have allowed the pc to make changes on the device.
This time around the command gave no textual return, but the phone swithched to bootloader mode. (the command prompt gave the following:)
Now I run “flash_FP5_factory.sh” in gitbash and it gives the following reaction:
However, Windows isn’t finding the appropraite drivers. I found universal ADB drivers, which I downloaded and installed. Sadly the message stays the same as above.
Where and how would I find and install an additional device update?
Also: My device is brand new out of the box.
also also: I am worried that if I update to the latest version of android, that there is a chance that i brick the device when changing OS. Am I correct in suspecting that it might?
Windows update should find and install the fastboot driver unless you have disabled Windows driver updates. From the Run box or cmd Window, run SystemPropertiesAdvanced.exe. Under the hardware tab click on Device Installation Settings. Check Allow Windows Update to update drivers is selected.
Connect your phone to the PC and put it in fasboot mode (adb reboot bootloader). Run devmgmt.msc or call up Device Manager. Under the “others” category, right click on the unknown device, select Update Driver, and Search. On my machine the device properly installed appears under Kedacom USB Device → Android Bootloader Interface.
Note that Fastboot uses an Android specific driver that has to be downloaded. Windows Update should do that automatically, but you may have to initiate it manually.
ADB uses something called an MTP driver which is a generic file transfer driver. It’s included with the base Windows installation and there is no need to download or update it. However, be sure to set the mode to file transfer when the phone prompts for it upon connection.
Yes you can, but only under certain circumstances. Check the warning about Anti-Rollback and make sure you understand it. Also don’t re-lock the bootloader unless you’re running the official /e/os release and you’re sure there’s no anti-rollback issue.
Hi Craig, You’re an absolute hero! very understandable steps, these are.
My problem seems to be that, even though I downloaded and installed the (supposedly) correct driver ( from https://adb.clockworkmod.com/universal adb drivers), my device manager still shows the following:
I select “update driver” and the following is the message I keep recieving, and I’m pretty sure that I am referring to the right pathway after 9 times…
I feel this is getting rather out of hand, but please know your help is much appreciated!
