/e/OS Installer, OnePlus 7: fail to execute ADB commands

Out of curiousity I’ve been giving the webinstaller a new chance.
Using it on a FP6 I did manage to get /e/OS installed although it did not relock the bootloader.

So, I figured that it would make more sense to use the webinstaller for community devices.
I tried an OnePlus 7 but it is consistently failing dispite I was using the same laptop and USB-cable. I even installed Google Chrome to see if it would work but even that didn’t solve the problem.

It keeps giving an error message on step 7 when I have tot connect de device: ‘Cannot connect ADB Failed to open USB device: Failed to execute ‘open’ on ‘USBDevice’: Access denied.’ However, the device responds to adb commands using the terminal.

Does anyone knows a work around? Or can I raise a ticket somewhere? I am willing to do some more to help improve the web-app.

Maybe … as “open” is not a regular adb command, it would be worth trying this diagnostic tool to see of it gives any clue (??). One could read the error as permission denied to open the WebUSB session.

You can report bugs in the /e/OS Installer

https://gitlab.e.foundation/e/devices/eos-installer/-/issues

Thanks for this advice. The USB Ports Tester has the same kind of output as the webinstaller.

Connection Test: FAILED

  • Could not claim the interface — it’s most likely already claimed by your operating system’s built-in driver (very common for HID, mass-storage, or composite devices). (NetworkError)*

So, it’s most likely an internal problem on the phone instead of the webinstaller.
I gave it a factory reset and did everything over again but got the same result.

I am inclined to think that the reported error is a Network error “out of” or “from” Chrome and your PC.

I wonder, does your Fairphone pass the Tester app? Are you using Linux? If yes the tips section at the foot of this page suggests Chrome may require udev.rules for the device.

I’ve been testing on Windows and Ubuntu Linux.
I was wondering if it might be better to retest on a clean device. So I took another laptop and it worked like a charm. So it wasn’t the smartphone after all.
Now I wonder if it only works for the first smartphone you try and something is left behind that hinders the next attempt. I will get back on that if it is.

1 Like

This topic was automatically closed after 3 days. New replies are no longer allowed.