Error on Installing /e on my LeEco Le 2

/e/OS Devices LeEco
1

Hi folks of the comunity,

First of all, I am an absolut beginner in this field of installing/flashing a mobile phone with a Custom ROM…

I’d like to install the /e ROM on the LeEco Le 2 X527 using Arch Linux (Reborn OS), but when I follow the instructions shown in the documentation for the device I’m already stuck at the point where I try to unlock the bootloader. When I want to check if my laptop finds the device (typing “fastboot devices” in the terminal) I get the answer

“no permissions”

What do I do now? The search on the internet only leads me to answers for people using Windows…

Any hint would be very helpful! :grin:

As I am a native German answers in my mother language would be highly appreciated… :stuck_out_tongue_winking_eye:

bixxby :wave:

2

OK, also. Die Fehlermeldung kann 3 Ursachen haben.

  1. Dein Handy ist nicht im Fastboot mode (Download mode).

  2. Die UDEV rules auf deinem Laptop sind nicht richtig. http://www.janosgyerik.com/adding-udev-rules-for-usb-debugging-android-devices/

  3. Du hast nicht die aktuellen adb / fastboot versionen. https://developer.android.com/studio/

Und falls du weiter in Deutsch schreiben möchtest. dann bau bitte im German-Bereich einen Post auf :wink:

------------------ english version ----------------
Okay, now. The error message can have 3 causes.

  1. your phone is not in Fastboot mode (Download mode).

  2. the UDEV rules on your laptop are not correct. http://www.janosgyerik.com/adding-udev-rules-for-usb-debugging-android-devices/

  3. you do not have the latest adb / fastboot versions. https://developer.android.com/studio/

And if you would like to continue writing in German. then please set up a post in the German section :wink:

3

If you receive an “insufficient permissions for device” message during the install process, try: adb kill-server

After that run: sudo adb start-server

And use sudo if commands do not work otherwise.

And for later: To mount android internal storage “yay -S jmtpfs” and “yay -S gvfs-tmp” are required.

4

This could be because four out of five computer users are using confoundedly Windows, while Linux is used by less than 2% of users.

A non-functioning ADB and Fastboot is a constant stumbling block when installing custom ROMs. You have already learned about three possible causes of errors. Maybe a look at the posting → here will help you.

By the way: Joining the /e/ forum in German requires a one-time activation.

5

In addition, i always download here: adb and fastboot

6

Hi folks,
I’m back again, sorry for that BIIIG delay, had some health issues :disappointed:…

@harvey: I followed yor advice and created with Janos Gyerik’s help a new file with udev ruless
Janos mentions something called “Android7”. Where does it come from or what does it mean?

[scheff@scheff-pc ~]$ lsusb | grep oogle
Bus 001 Device 008: ID 18d1:d00d Google Inc.

[scheff@scheff-pc ~]$ ls -l /dev/bus/usb/001/008
crw-rw-r-- 1 root root 189, 7 13. Feb 13:50 /dev/bus/usb/001/008

[scheff@scheff-pc ~]$ ls -l /dev/android7
ls: Zugriff auf ‘/dev/android7’ nicht möglich: Datei oder Verzeichnis nicht gefunden
[scheff@scheff-pc ~]$

Hallo wehrte Gemeinde,

nach einer laaangen Pause (war 'n bisschen krank :disappointed:)

@harvey: ich bin deinem Rat gefolgt und habe nach Janos Gyerik’s Anleitung eine Textfile mit udev-Regeln erstellt. Allerdings ist das Ergebnis wenig zufriedenstellend bzw. verstehe ich es nicht. Wo kommt diese “Android7”-Datei her? Was bedeutet sie?

Guckst Du hier:

[scheff@scheff-pc ~]$ lsusb | grep oogle
Bus 001 Device 008: ID 18d1:d00d Google Inc.

[scheff@scheff-pc ~]$ ls -l /dev/bus/usb/001/008
crw-rw-r-- 1 root root 189, 7 13. Feb 13:50 /dev/bus/usb/001/008

[scheff@scheff-pc ~]$ ls -l /dev/android7
ls: Zugriff auf ‘/dev/android7’ nicht möglich: Datei oder Verzeichnis nicht gefunden

Danke!

1 Like
7

. . . . . . . . . . . . . . . . . . . . . . .