You can try to use nano instead of gedit since I don’t know if using graphical applications as root is a good idea…
About using sudo from a terminal vs creating a udev rule I guess it’s mostly a matter of convenience in the latter case. I might add the udev rule myself and see how it works.
The answer is actually quite simple: fastboot needs the permission to access the fairphone device.
Using sudo will work in most cases because root has all permissions by default. But you can also use your normal user account, if it has permissions to access the device.
On many (but not all) Linux distributions this is done via udev using the “plugdev” user group.
To see whether your normal user is in the “plugdev” group, type:
groups
and check if the output list contains “plugdev”. If not, you need to add user user to the groups as described above (“adduser plugdev”).
To see whether your normal user can access the fairphone device, you should first identify which USB device is used by the phone:
lsusb
That gives a list of all attached USB devices. Example:
~$ lsusb
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 006: ID 2ae5:f003
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
[…]
With the extra knowledge that Fairphone has the USB vendor ID “2ae5”, I found my Fairphone as device 006 on USB bus 002.
Now simply check the permissions of the device in the fliesystem with:
ls -l
In my case:
~$ ls -l /dev/bus/usb/002/006
crw-rw----+ 1 root plugdev 189, 133 Sep 30 18:13 /dev/bus/usb/002/006
The output tells me that the device is owned by user “root” with "r"ead and "w"rite permissions and by group “plugdev” also with “r"ead and “w"rite permissions. Other users have no access (”-”). So root and all users in the “plugdev” groups should be able to access the device.
That did not work out of the box on my system, but I had to add a udev rule as already described above.
As root user, I created the file
/etc/udev/rules.d/adb.rules
with the following content:
ACTION==“add”, SUBSYSTEM==“usb”, ATTRS{idVendor}==“2ae5”, MODE:=“0660”, GROUP:=“plugdev”
Because the file needs to be created and edited as root user, a text mode editor like nano or vim may be simpler to use with sudo.
Hi there,
thanks for the tutorial. I tried it and it seemed to work and I’m now stuck on a blue screen with “emergency calls” and “next” at the bottom and notification from services stopped.
Here are some details:
3.2 "Check connectivity to your phone by issuing adb devices from a terminal or the Command Prompt. This should display your device’s serial number together with the word device. Reboot the phone to Fastboot mode by issuing adb reboot bootloader and Change into the directory where the package is downloaded as it seemed unnecessary and i didnt know how to perform that.It seems that it wasnt a clean install (as i can see notifications from older services). Can anyone help? Is this issue known? Thanks for your support!!
Nicolas.
Hi,
I have performed again these steps and i have the same result (except i dont see any optimization after reboot)…
how could i make sure to have a clean install?
Should i install other softwares?
Should i use a completely another method?
Thanks for your input…I am stressed to have a brick…
Thanks @AnotherElk for your quick reply. I can reboot in TWRP mode but cant run any app, therefore cant download the OTA package. I’ll try a detour: download it on my computer, transfer it to the microSD and run TWRP, wipe all (excep microsd) and install. That should do the trick?
Thanks again, I’ll keep you posted!
@AnotherElk, should i install the “OTA” OR “manual installation” package with TWRP? And should i unzip the downloaded file or not?
The OTA if you install via TWRP.
Do not unzip it.
I followed the simple steps, the install displayed “done” and when i pressed “reboot”, it said No OS installed! Are you sure you wish to power off?
That’s scary! Should i reboot?..
I went through the TWRP procedure again and had the same message…I spiwed to reboot and it seemed to work! Thanks guys!!!
I can’t install Fairphone Open with these steps. The script output is the following:
** Fairphone Open 18.03.1 Manual Flashing Script **
WARNING: Flashing this image wipes all user data and settings on the phone.
Validating files...
Validation complete.
ERROR: Unable to create a plug-in (e00002be)
WARNING: No Fairphone 2 found in fastboot mode.
WARNING: Make sure that a Fairphone 2 is connected.
WARNING: To check for devices, type './bin-darwin/fastboot devices'.
Do you want to look for a Fairphone 2 again? [(Y)es/(n)o]:
I have prepared the script with the following steps:
I’m using macOS High Sierra with the newest Android Studio and included Android SDK.
Looks like this (see below) bug in the macOS version of the SDK, which some users are reporting still doesn’t work with fastboot version 0.0.1-4500957 (27.0.1, and definitely 26.0.1). A manual build is provided in comment 8 that appears to work for people who have commented on the bug:
https://issuetracker.google.com/issues/64292422
Thanks for your response. I’m not sure, whether the bug still exists. I can successfully access the Fairphone using adb devices or fastboot devices, but I can’t execute the script. I also can flash successfully further developer devices from LG and Wileyfox but not the Fairphone 2.
I’m currently using fastboot version 0.0.1-4500957 on macOS 10.13.3 on a MacBook Pro with Touchbar. Another potential problem could be the USB-C port respectively driver for this device.
Anyway I switched to my Linux developer VM and managed to install Fairphone Open with KDE Neon.
Unfortunately Fairphone Open is only available for people educated in computer science. I think, Fairphone should offer Fairphone Open preinstalled, because the Google layer violates privacy and security. Today European consumers have no alternative to iOS or Google Android. There are only after marked alternatives available.
I don’t think that education in Computer Sciences is needed… Just following a tutorial. You have made it this far and the only thing stopping you is a bug. Unfortunately.
Fairphone can’t preinstall AOSP because people expect Google Services - despute all their privacy issues. Strange world, indeed.
Hello FP Forum,
I really do want Fairphone Open but can not accomplish the manual.
I think my phone gets in fastboot, shown by the known splash screen, which stays on display instead of leading to android start up. I connect the phone via USB but flash-for-mac.command leads to the error, stated in the title of this topic. This is the complete code, triggered by the installation file:
** Fairphone Open 18.03.1 Manual Flashing Script **
WARNING: Flashing this image wipes all user data and settings on the phone.
Validating files…
Validation complete.
ERROR: Unable to create a plug-in (e00002be)WARNING: No Fairphone 2 found in fastboot mode.
WARNING: Make sure that a Fairphone 2 is connected.
WARNING: To check for devices, type ‘/Users/sebastianschumann/Downloads/fp2-sibon-> 18.03.1-manual-switcher/bin-darwin/fastboot devices’.Do you want to look for a Fairphone 2 again? [(Y)es/(n)o]:
I did a tutorial for installing adb and fastboot. I am in developer mode, with usb debugging enabled and media transfer mode. My cable is a transfer cable from an sony camera. I use OSX 10.13.04.
I would appreciate any ideas to try out.
Despite the fact, that I might not be able to implement a manual build in my system, the link is broken. I will try the flashing manual with a windows machine as soon as I am able to.
Thank you so far.
Had no problems setting up Fastboot & ADB upon Mac OSX 10.13.4 using this resource, which couldn’t have been easier:
http://www.stechguide.com/setup-adb-and-fastboot-on-mac-easy-step-by-step-guide/