Need help! Error: Failed to execute 'requestDevice' on 'USB': No device selected

alwayslearning

other8026 Thanks for those steps. I will try each one and let you know how I go.

alwayslearning

other8026 Okay. I have:

Confirmed using USB-C ports (only ones on the macair laptop)
Tried both (USB-C) ports
Restarted the computer and tried again
Not sure what Fastboot mode is. But I didn't see 'Fastbootd' at all
Tried another quality cable.
And nothing changes. For some reason, the phone is not being recognised.

All I get is: the triangle alert symbol above "The bootloader is unlocked and software integrity cannot be guaranteed. Any data stored...etc....." [Then, below that] "Visit this link on another device: g.co/ABH ..."
The phone then cycles through to a white screen with 'google' in the middle of it. Then, to a black screen. And it keeps cycling, 15 seconds or so each, until the battery goes flat. In the first bootloader page, I have pressed the "Press power to pause" and it stays on this page until it goes flat. Leaving the phone on the charger leaves it to get quite warm as it constantly stays on.

de0u

alwayslearning n the first bootloader page, I have pressed the "Press power to pause" and it stays on this page until it goes flat. Leaving the phone on the charger leaves it to get quite warm as it constantly stays on.

How about:

Pause the bootloader
Unplug the phone
Quit the browser (maybe reboot)
Restart the browser and the installer
Plug the phone in

If none of that works, does Google's online flasher for their Pixel OS work?

spring-onion

A mac shouldn't give you any trouble so this is very strange indeed.

alwayslearning Not sure what Fastboot mode is. But I didn't see 'Fastbootd' at all

May this be the problem all along? Fastboot is the bootloader interface you reach by holding volume down while the device boots, you can only flash from that mode so it's imperative you have it open.

de0u

alwayslearning Which version of macOS, which version of which browser?

alwayslearning

de0u Mac Sonoma v14.5. And Chrome version 126.0.6478.127 (arm64).

RandomlyGeneratedName1

Did you try to do it from different browsers? For me installation worked only from Google Chrome.

alwayslearning

RandomlyGeneratedName1 Yes, I followed the Graphene OS instructions. So have only used Chrome. And I made sure to update the OS on the new phone, and the laptop. And also updated Chrome.

alwayslearning

de0u Great suggestions. Thank you. I will give them a go - and if needed - Google's online flasher. Thank you!

alwayslearning

Sigh...

Paused the bootloader - check
Unplugged the phone - check
Quit Chrome browser and rebooted - check
Restarted browser and installer - check
Plugged the phone in - check
Opened google's flasher for Pixel OS - check.
Again, this flasher does not recognise there is a device attached.
Removed one end of the cable and restarted Chrome & google flasher. Repeated at the other end. And then a different USB-C port on the laptop (there's only 2). Switched with another good cable (New Pixel cable and another good quality cable.
Nothing seems to make any difference to the phones behaviour and it continues to not be recognised.
I see that the google flasher site has some code instructions (nothing that I saw for apple osx though). I do have an old android phone and also a pc that runs linux, if that helps. Not the most confident with coding but have done a little bit once or twice. A new and very expensive phone that refuses to work is a bit nerve wracking. So I am keen for any further help (Thanks for being so kind as to help in working out this puzzling situation).

de0u

alwayslearning I do have an old android phone and also a pc that runs linux, if that helps.

What kind of Linux?

Trying one or the other of those seems timely.

alwayslearning

de0u It's a Ubuntu variation called Tuxedo. They include it with their own laptops and also offer it as another distro.

Ducter

Not familiar with Mac but double check on the phone developer option is enabled, USB debugging is enabled, select the option for no timeout on debugging notification in case you missed it on the phone also OEM unlocked enabled, watch for the onscreen notification allowing USB debugging. On your computer, if you're running anything like uBlock or or any other extensions like these make sure they allow from graphene website or turn them off temporarily.

de0u

Ducter As far as I understand the installer, USB debugging is completely not a requirement for installing, and is a good thing to have turned off the rest of the time, unless one is actually connecting the device up to a debugger. USB debugging is recommended in various YouTube videos but not, as far as I'm aware, in any official GrapheneOS documentation.

alwayslearning

Ducter Thanks for your experience and insights on this. Clearly it's at the trickier end of things - at least for a newbie like me.

Ducter

de0u the purpose of USB debugging was to hopefully trigger the computer that another/ new device is connected. It's listed in the steps for flashing Google factory images which he mentioned he was trying to see if Google's web flashing recognized his phone.

de0u

Ducter It's listed in the steps for flashing Google factory images which he mentioned he was trying to see if Google's web flashing recognized his phone.

Understood.

fid02

Ducter It's listed in the steps for flashing Google factory images which he mentioned he was trying to see if Google's web flashing recognized his phone.

That's odd. I've flashed back to PixelOS several times, and never needed to enable USB debugging, nor was it ever mentioned on flash.android.com. But maybe Google's tool does suggest that, but only for users of macOS? If so, it's always good to follow the official instructions.

In any case, USB debugging is not needed to flash GrapheneOS. The install issue isn't there...

de0u

alwayslearning It's a Ubuntu variation called Tuxedo.

I don't know if anybody has tried an install from a Tuxedo machine. It might or might not work, but it might be worth a try!

alwayslearning

de0u Then I'll give it a whirl! Seems the key issue is the website being unable to see the device. So, that got me wondering if trying different OSs would be worth doing (I've already tried another mac with no device recognition on that either)