/e/OS/ clean install on OnePlus 8 Pro issue

Hello, I’m trying to install e/OS on OnePlus 8 pro. I did follow the instuctions on the Murena site completely, but I still get an error message while connecting to the phone:

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.

Has anyone had this problem already and knows how to solve it? Thanks for your help!

Hello @Akvezej, Welcome to the /e/ users forum.

Install /e/OS on a OnePlus 8 Pro - “instantnoodlep”

Were you able to follow the onscreen advice?

If not please describe exactly where this failed for you.

Hi, thanks for you reply. I did manage to come all the way to connection part. The phone is shown for the connection as OnePlus 8 Pro, but when I choose the phone and click Connect, the error massage appears :frowning:

If on Windows maybe you have insufficient drivers, if so this is the fix [Solved] Windows does not see my phone in Fastboot mode.

I’m running Ubuntu 24.4. LTS with latest updates installed.

I should change to manual install that way you can send the actual terminal trace in the event of trouble.

You might have a permissions issues … eosinstaller is using platform-tools “in the background” … you could try the advice under Ubuntu Linux here:

That is two things

  • plugdev group
  • android-sdk-platform-tools-common (or similar name) to get udev rules started.

However, only “common” … system installed platform-tools might interfere.

The Requirements section of the manual install page shows the way to proceed for that method. I would avoid flip-flop between the two methods.

I menaged to connect the phone to my laptop through Android studio. I’m not shure how to install e/OS form there manualy though. Like you wrote it is obviously some problem with the permissions I don’t know how to solve. I’m not very famialiar with Ubuntu also so I think this procedure may be exceeding my capabilities. I am after all 65 y old :slight_smile:

Thanks for your efforts anyway!

The idea was that, following those two actions, eosinstaller might now work.

Alternatively this Install /e/OS on a OnePlus 8 Pro - “instantnoodlep” is the command line install page. From Post #2 there is also [HOWTO] an Unified Install Guide Project for /e/

I obviously don’t have enough knowledge to do this :frowning: Thank you very much for dedicate some of your precious time to my problem!

1 Like

Hello, I’m back for some help. I’ve made some progress. It was the most stupid thing I did wrong in the step of connecting the phone. While typing on my laptop the phone’s screen has locked and that was obviously blocking the conection. I gues this should be added to the instructions.

With the screen beeing unlocked software downloaded but after the restart of the phone in bootloader mode after trying to connect the phone to a computer a new connection error has appeared. Is this problem maybe familiar to you:

Error on step: connect-bootloader

Cannot execute command connect bootloader
The device is not connected Failed to connect: Cannot connect to bootloader after 3 attempts. The device may not be in bootloader mode yet. Please ensure the device is in bootloader/fastboot mode and try again. Error: Failed to request USB device: Failed to execute ‘requestDevice’ on ‘USB’: Must be handling a user gesture to show a permission request.
Proposal: Check connection and that no other program is using the phone and retry.

The problem might be on the phone. Are you sure you have control of the finger presses in order to boot reliably into Fastboot mode?

With the device powered off - hold Volume Up + Volume Down + Power

If still using Ubuntu the recommendation in Post #7 is only two commands to copy and paste to your terminal.

sudo usermod -aG plugdev $LOGNAME

then

sudo apt-get install android-sdk-platform-tools-common

Right after the ROM was copied to the phone, it rebooted in a bootloader mode by itself. Am I supposed to hold Volume Up + Volume Down + Power after the phone automatically shuts down and restarts?

I’m not sure what am I supposed to do with this instructions:

f still using Ubuntu the recommendation in Post #7 is only two commands to copy and paste to your terminal.

sudo usermod -aG plugdev $LOGNAME

then

sudo apt-get install android-sdk-platform-tools-common

What do these two command do?



At the top of the phone screen I have Options:

START Recovery mode Power off Restart boot loader and Show barcode

And then:

Fast boot Mode

PRODUCT NAME - kona

VARIANT - SM8 UFS

BOOTLOADER VERSION -

BASEBAND VERSION -

SERIAL NUMMBER -

SECURE BOOT - YES

DEVICE STATE - locked

This is the screen where phone reboots and wont connect:

solution to not lost your time was already given in post 2

OK my comment to use button press is unnecessary as you are confident that the phone is already in

In the intro did the instructions inform you how unlocking was to be handled? Edit reported unlocked as I wrote.

You are wise to resist commands just pasted by a stranger, originally I linked the Android page explaining why this might be necessary. Edit, It may help to avoid permissions errors.

However eosinstaller should be complete. If it is incompetent, I think best to use manual install.

I understand what you mean but I don’t feel knowlegeable enough to install e/OS manually. That’s why I’m sticking to a e/OS installer Web procedure :frowning:

Thanks for your advice. I did menage to unlock the phone (DEVICE STATE - unlocked) but still get the error while connecting:

Error on step: connect-bootloader

Cannot execute command connect bootloader
The device is not connected Failed to connect: Cannot connect to bootloader after 3 attempts. The device may not be in bootloader mode yet. Please ensure the device is in bootloader/fastboot mode and try again. Error: Failed to request USB device: Failed to execute ‘requestDevice’ on ‘USB’: Must be handling a user gesture to show a permission request.
Proposal: Check connection and that no other program is using the phone and retry.

What did I miss?

Perhaps you should describe how you unlocked the bootloader.

Your reports indicate that you did “connect-bootloader” in order to unlock.

Currently looks like eosinstaller has a permissions issue with Ubuntu.

I did the steps from e/OS documentation under the chapter Unlockin the bootloader:

adb reboot bootloader
sudo fastboot oem unlock

Good you made the first steps from manual install. You were able to access Fastboot mode by issuing that fastboot command successfully in a way that eosinstaller cannot do (it would seem from your report).

As you read more on the install page it will begin to make more sense. It is ok if this learning process takes some time. :slightly_smiling_face:

1 Like