Can't unlock bootloader. Access denied.

upsidaisy

I've been bashing my head against getting GrapheneOS installed and getting pretty frustrated. I've progressed to the point that I am supposed to unlock the bootloader through the installation instructions of the website, but while it does see the device it is unable to compelte the connection process. Instead, it says that it failed to open the device, access denied.

I'm on the most recent version of Fedora. OEM is unlocked. USB debugging is enabled. Device is loaded into fastboot mode. Adb and fastboot are installed.

Only thing that stands out is that the device isn't listed through the adb devices command, no matter what I do. It is listed under lsusb, however.

Any advice on how to solve this?

Hulk

upsidaisy it seems like you were following an unofficial installation guide.

Please do not follow any unofficial installation guides.

There is only one official guide to install GrapheneOS and it is here: https://grapheneos.org/install/

Please read it carefully in its entirety before doing anything.

We highly recommend using the web installer method instead of the command-line method.

gosuser

If you just installed android packages, reconnect the device (device may have been connected before udev rules were applied), or reboot the computer and try again.

upsidaisy

gosuser

I've just tried both of these, but nothing appears to have changed. Problem with unlocking the bootloader persists. No changes with adb, either.

lberrymage

upsidaisy Fedora isn't one of the officially supported installing OSs because its Android tools package doesn't ship with the necessary udev rules. You need to install the udev rules manually.

jmc

lberrymage I'm experiencing the same on Ubuntu 20.04.5 LTS

MetropleX

jmc

Have you made sure to read:

Chromium (outside Ubuntu, since they ship a broken Snap package without working WebUSB)

As Hulk said above, the only way to install GrapheneOS is to use the guide as linked. We can't support issues outside of that scope.

[deleted]

I've always had success using the web based installer on a chrome based browser (required). Would give that a shot and let us know how it goes.

jmc

yep I am following the guidance - I was using Brave browser. Downloading and using Chrome instead solved that issue but now flashing the release returns: Error: Failed to execute 'claimInterface' on 'USBDevice': Unable to claim interface. Will try with new cables.

MetropleX

jmc claim interface isn't a cable issue something is holding onto the USB port, restart, close EVERYTHING non essesntial on your system, and all other browsers. Do not use incognito and only have 1 tab open with the web installer.

We will get you there yet friend.

jmc

yea still the same unfortunately - freshly installed Chrome, no other programs running, no other tabs open, freshly rebooted system. Any ideas?

MetropleX

jmc still on Ubuntu?

https://askubuntu.com/questions/1242129/unbinding-usb-interface-to-use-chrome-web-usb-api
https://stackoverflow.com/questions/47695160/failed-to-claim-interface-0-device-or-resource-busy

jmc

unbinding the usb port solved the problem partially in that it enabled the flashing to progress as far as rebooting into the userspace fastboot, but then at this stage it fails with the same error message again - cannot claim interface, as if somehow the port is rebound during the flashing.

This is a completely fresh ubuntu 20.04 installation with a freshly installed chrome, no other programs running, and a brand new Anker cable. Confused as to what about my setup is complicating things.

MetropleX

jmc Chrome on Ubuntu is not supported as it breaks WebUSB actually says so in the web installer guide.

jmc

MetropleX the warning is for chromium/ubuntu - i didn't realize it also applied to chrome. Both ubuntu 20.04 and google chrome are listed as officially supported.

MetropleX

jmc true but I know people have had issues with both have you done the following which may help:

Linux
If Chromium has been installed from the snap store (the default in the Ubuntu Software Store) it will not be able to access WebUSB devices.

On some Linux distributions eg. Ubuntu, you may need to declare a udev rule. To do this:
Close Chrome
On Fedora, ensure that the plugdev group exists
getent group plugdev >/dev/null || sudo groupadd -r plugdev
Create a file at
/etc/udev/rules.d/50-microbit.rules
with the following content:
SUBSYSTEM=="usb", ATTR{idVendor}=="0d28", MODE="0664", GROUP="plugdev"
Add your user to the plugdev group (replace with your username):
sudo usermod -a -G plugdev <your-username>
Restart the udev rules
sudo udevadm control --reload-rules
Log out and log back in
Open Chrome and try to pair again

Beyond that all I recommend is how I flash my devices and use another Android phone lol

jmc

success!

the udev rules didn't fix it - the problem was that when the device was restarted the usb device was being auto-bound. To solve this, I ran echo '0' > /sys/bus/usb/drivers_autoprobe as root to stop it automatically binding the newly detected device.

Thanks a lot for all your patient help!

MetropleX

jmc don't need to thank me, I just held your hand while you did all the work. Just happy you got it sorted and in doing so provided a solution others can benefit from by being pointed here.

Syncrossus

jmc Had the same problem on my pixel 5, this worked! Thank you so much!

StealthKookaburra

jmc Flashing a new Pixel 6a today, I found that I also had to do this command on my Fedora laptop. I would like to recommend a slight different command to do the same thing:
echo '0' | sudo tee -a /sys/bus/usb/drivers_autoprobe

On the subject of USB vendor ID, it looks like this new Pixel 6a has the same vendor ID has my Pixel 7: 18d1.

StealthKookaburra

I am going through the Web installer on Fedora 36 for my Pixel 7.
First, the package to install on Fedora is "android-tools", to install it:
sudo dnf install android-tools

Second, the Pixel 7 has a different USB vendor ID than the Pixel 6. Therefore the udev rule from MetropleX needs to be adapted. Edit the file /etc/udev/rules.d/50-microbit.rules like so:
SUBSYSTEM=="usb", ATTR{idVendor}=="18d1", MODE="0664", GROUP="plugdev"

MetropleX

StealthKookaburra The udev rule offered by me is not official, the documentation on the site is. Any non supported OS you try to use is at an individuals discretion. I just believe in helping everyone and thank you for providing an update as you have to help others in the community.