Just bought a new Fairphone 5 and I want to install e/os on it. I followed every step on the easy installer. I’m using Ubuntu. But then, when I connect my phone I get this error message :
Error on step: device-detection
Cannot execute command connect adb
The device is not connected Failed to connect: Cannot connect ADB Failed to open USB device: Failed to execute ‘open’ on ‘USBDevice’: Access denied.
Proposal: Check connection and that no other program is using the phone and retry.
Went to the “how to” section, downloaded the platform tools and tried to follow the instructions (not sure I’ve managed to do it correctly), still get the error
Can anyone help me on the installation path please ?
If you check a few posts with the hashtag eosinstaller you will notice that we frequently suggest simply to use the manual install method Install /e/OS on a Fairphone FP5 - “FP5”, particularly with fp5 as the install is done by a script so is not so hard.
Each user that wants to use ADB needs to be in the plugdev group. If you see an error message that says you’re not in the plugdev group, add yourself to it using the following command:
sudo usermod -aG plugdev $LOGNAME
Groups only update on login, so you must log out for this change to take effect. When you log back in, you can use id to check that you’re in the plugdev group.
The system needs to have udev rules installed that cover the device. The android-sdk-platform-tools-common package contains a community-maintained default set of udev rules for Android devices. To install it, use the following command:
apt-get install android-sdk-platform-tools-common
/quote
You realise that the error is one of the most common seen, the installer does not see the phone in Fastboot mode. You need to ask yourself, is the phone in Fastboot mode. An easy test (if you correctly installed platform tools) is
I am affraid those instructions are for using Android-Studio, and are not necessaries for using Platform-Tools.
(I can’t be 100% sure as i am plugdev-group member, and i have manually added udev rule to be able to use Odin4)
I can’t see such instructions in lineage Wiki or XDA.
Are these instructions “web-installer” specific ?
like “these dependencies were forgoten by /e/ web-installer devellopers” ?
It is a moot point whether this would be a solution and the url is a redirect from certain platform tools bookmarks to “Android Studio”.
Plugdev group has to be a good thing. The advantage of android-sdk-platform-tools-common is that bright users have the chance to improve udev rules if required.
Not in our documentation but this recommendation does appear in the help page for a similar installer.
I thank you for your answers, I’ll try your links tonight.
I did run the command adb devices and my fp5 was detected. But when I ran fastboot devices, the console didn’t show me anything. The script just ended and I could start another command.
About my chromium, it was a brand new one, as I use FF as my only browser. I just downloaded the basic latest chromium, without any tweak. I can try to start it as sudo to see if things changes like that.
Hi, ofc I don’t know your experience level. adb and fastboot speak a different language. Before getting into running scripts it is good to know that you have full control of the bootloader and can reliably boot to
Normal and Recovery where adb devices must get a reponse … and
Fastboot mode where fastboot devices results in the phone self-identifing with serial no and state as
123abc456 fastboot
Boot Modes
Recovery
With the device powered off - hold Volume Down + Power, then select “Recovery mode” using Volume keys.
Download
With the device powered off - hold Volume Down + Power
Edit @Januel first time users sometimes don’t recognise Fastboot in the Bootloader, maybe this is why the install page recommends
into fastboot by running the command in the PC console adb reboot bootloader
First, understanding that using the “fastboot” command was in fastboot mode. (And thus, understanding what was fastboot mode).
Then, in the howto, we are asked to use twice the command “./fastboot flashing get_unlock_ability” and the text is the same, so I though the rest was just some kind of typo. So I didn’t use the command “./fastboot flashing unlock_critical”. So obviously, when I tried to flash the e/os, the script didn’t work properly.
After some fidling on the fastboot mode and the command, I read again all the procedure to see my mistake. After that, it was smooth sailing.
What led me astray a bit was that when using the command “chmod +x flash_FP6_factory.sh && ./flash_FP6_factory.sh”, as it didn’t work properly, the error message asked me to remove the battery of my phone and try to start the phone (while plugged), tried quite a few times and … Well the phone wouldn’t start. So I stumbled a bit on this part.
For someone not experimented in this kind of things (but not totally a newbie either), I found the howto really helpfull and well made. Just needs a bit polishing and maybe one screenshot or two more. The main problem was between the chair and the screen, as usual.
