Web install process fail: "Unable to claim interface"

Chronos

Greetings,

I’m trying to install Graphene OS on a Pixel 4a.

The method I’m using is the web install, since it’s the only one available to me (lack of hardware and software compatibility), from my previous android phone.

The installing phone runs Android 8, the latest Chrome browser (play store certified up to date), has OEM unlock enabled and USB debugging enabled.

Pixel 4a runs Android 12.

Usb cable is the original from Pixel 4a.

I run everything ok up until the point where I et to the fastbootd screen with the options “Reboot system now”, “Enter recovery mode”, “Reboot to bootloader” and “Power Off”.

On the side of the installing phone, Chrome keeps asking for permission, as I keep accepting it, and the error message persists:

“Failed to execute “claim interface” on “USBdevice”: Unable to claim interface.”

If I rerun the process with another mode of USB connection (instead of giving energy to the Pixel, taking it from it) chrome happens to not find any device to connect, when “reconnect” is pushed. The message then shows as:

“”Failed to execute “request device” on “USB”: No device selected.

I’ve rerun the process with the USB debuggind disabled, I’ve tried to shoot down every process running in the background affecting the USB except the basic ones. I’ve erased cache.

I don’t have any technical expertise, and would rate myself barely above the average user.

I’ve consulted some threads here and elsewhere with similar problems, but I can’t see anything of help as per to my case.

I’ll appreciate any help, I’d really like to try out this system as I delve deeper into the Open Source, privacy focused technology.

Many thanks.

other8026

Chronos

It's my understanding that the browser will say that if the device is already claimed. You can try completely exiting the browser, maybe even restarting the phone and computer, then try again. Make sure you only attempt to flash with one tab open.

Not sure if that will work. Maybe another person who knows more about this than me will have other suggestions.

de0u

Chronos The installing phone runs Android 8, the latest Chrome browser (play store certified up to date), has OEM unlock enabled and USB debugging enabled.

I don't think the installing phone needs OEM flashing on or USB debugging on, and I can imagine that USB debugging could get in the way. What if you turn them off on the installing phone?

Chronos

other8026

Chronos If I rerun the process with another mode of USB connection (instead of giving energy to the Pixel, taking it from it) chrome happens to not find any device to connect, when “reconnect” is pushed. The message then shows as:

“”Failed to execute “request device” on “USB”: No device selected

I'm going into it Android to Android (no computer), and I've tried all of the above many times, including erasing all browser data an give full permision.

The only difference I manage to gather was as I mention, changing the settings of the USB connection from supplying energy to recieve it. Neither work.

Chronos

de0u

Chronos I’ve rerun the process with the USB debuggind disabled, I’ve tried to shoot down every process running in the background affecting the USB except the basic ones. I’ve erased cache.

So far, I think I've gotten all of what could possibly have gotten in the way out of it. Since it didn't work, something else must be.

I'll flash the latest OS available (Android 13) and maybe give it another shot down the line, since apparently there is no unified solution at this moment.