My phone is connected but it say "no compatible devices found"

ShadowKitty

Hello.. I am using a Pixel 6A, Windows 10 , usb-c to usb-c cable, on the Chrome browser.

When the phone is plugged in, the Devices list shows Pixel 6a - "Device can perform faster when connected to USB 3.0". Then when I attempt to unlock the bootloader, the Device list message changes to Pixel 6a - "Driver is unavailable." But Graphene says "no compatible devices found."

So it seems my computer is seeing the phone..... but there is some gap preventing Graphene from seeing it.
Any suggestions much appreciated!

de0u

ShadowKitty So it seems my computer is seeing the phone..... but there is some gap preventing Graphene from seeing it.

Is Windows 100% up to date? See: https://grapheneos.org/install/web#connecting-device
Is Chrome 100% up to date, and configured correctly? See: https://grapheneos.org/install/web#prerequisites

fid02

ShadowKitty When the phone is plugged in, the Devices list shows Pixel 6a - "Device can perform faster when connected to USB 3.0". Then when I attempt to unlock the bootloader, the Device list message changes to Pixel 6a - "Driver is unavailable." But Graphene says "no compatible devices found."

Sounds like the device is not connected while in the bootloader interface. Please do this: https://grapheneos.org/install/web#booting-into-the-bootloader-interface

ShadowKitty

de0u Is Windows 100% up to date? See: https://grapheneos.org/install/web#connecting-device
Is Chrome 100% up to date, and configured correctly? See: https://grapheneos.org/install/web#prerequisites

Thanks - Yes, I checked Windows updates and it says it is up to date (Win 10), and I downloaded Chrome yesterday and used that. I also tried the Brave browser with shields down.

I wish I could identify what is wrong when the computer can "see" the Pixel 6a but Graphene cannot. Its frustrating!

ShadowKitty

fid02 Sounds like the device is not connected while in the bootloader interface. Please do this: https://grapheneos.org/install/web#booting-into-the-bootloader-interface

Thank you. I feel like I am following the instructions... I boot the phone into the bootloader interface, then I plug it into the computer. Then Graphene says "no compatible devices found." I've read that it could be a cable problem, but I just bought this brand new Anker cable (this one), and I'm plugging that directly into the Usb-c port, not through a dongle or anything.

That link also says that "Current Windows 10 and Windows 11 include a generic driver usable for fastboot and no longer require installing a driver for installation on the Pixel 4a (5G) or late" -- so I assume I don't need to go through adding a new usb driver? I wish I could figure out where the problem is happening. Its annoying.

de0u

ShadowKitty Given what you're experiencing, I do think installing Google's driver is a good next step.

fid02

ShadowKitty I've read that it could be a cable problem, but I just bought this brand new Anker cable (this one), and I'm plugging that directly into the Usb-c port, not through a dongle or anything.

Do you have access to the USB-C cable that came with the device? If so could you try with that?

ShadowKitty

I don't know if this means anything, but in Chrome, when I go into Privacy and Protection, Site Settings, under USB Devices, with my phone plugged in, it says "No USB devices found."

ShadowKitty

de0u Given what you're experiencing, I do think installing Google's driver is a good next step.

Ok, I will try this next and report back, thank you!

ShadowKitty

fid02 Do you have access to the USB-C cable that came with the device? If so could you try with that?

I bought the Pixel used from Swappa - and it only came with a very cheap cable - I assumed that would not be good enough to put Graphene on it, so I bought the Anker cable listed a few posts back ...

Just to be sure, I just tried using that cable now and it has the same issue, the computer can see it but Graphene cannot.

N1b

What hasn't been asked yet:

Did you install the adb drivers in Windows 10 (should pop up in Windows update as an optional install once the phone is connected in fastboot)?
Did you try transferring data over your cable first (some cables only do charging)? Best would be between your Pixel 6a (on Pixel OS) and the very Windows 10 computer you are using to install GOS.
Did you try using a USB 3 port (in case you have one)? Not that it should magically work because of the port, but it will install much quicker for sure.

Hope you'll be successful on your next try. And welcome to the GOS community!

ShadowKitty

N1b Did you try using a USB 3 port (in case you have one)? Not that it should magically work because of the port, but it will install much quicker for sure.

I haven't - does this cable look like a good choice for that?

ShadowKitty

N1b Did you install the adb drivers in Windows 10 (should pop up in Windows update as an optional install once the phone is connected in fastboot)?

This has never popped up in Windows Update in all the times I have connected this phone to the laptop.

de0u

ShadowKitty Personally I would not buy an Anker cable (or any premium-ish cable) from eBay. I'm sure many sellers there are honest, but it would be a lot of hassle and delay if you happened to run into bad luck.

I think before I would buy an Anker cable from eBay I would buy an appropriately spec'd Best Buy cable from Best Buy, e.g.: https://www.bestbuy.com/site/insignia-3-3-usb-to-usb-c-3-2-gen-2-superspeed-10gbps-cable-black/6419159.p?skuId=6419159. But the cable I did buy from them four years ago isn't showing on the site now, so I am not in a position to recommend the exact thing that worked for me.

In general a USB-C-to-USB-C cable would be better. But I can't help noticing that the Anker cable you provided an Amazon link to appears to be for a charging cable (the Amazon listing doesn't seem to show a data rate). For installing GrapheneOS the key thing is the quality of data transmission. A cable with a good data rating and a good power rating is probably higher-quality than one with just a good data-transfer spec, but power is in some sense icing on the cake.

Also, in general, for installation purposes a short cable is probably better than a long cable. I would recommend against anything longer than 6 feet / 2 meters, and something like 3 feet / 1 meter is less likely to make trouble.

de0u

ShadowKitty This has never popped up in Windows Update in all the times I have connected this phone to the laptop.

Maybe try this? https://developer.android.com/studio/run/win-usb

de0u

ShadowKitty It is fine to turn the phone off (try pressing and holding the power button for a long time). When you turn it on later, I suggest holding the volume-down button, then also holding down the power button, to get back to Fastboot mode.

~~Meanwhile, I think I am going to re-suggest that, if you haven't, you try installing Google's adb driver (de0u).~~ Can you confirm that when you wrote "I then also finally got the USB driver installed" you were referring to the Google USB driver?

ShadowKitty

de0u But I can't help noticing that the Anker cable you provided an Amazon link to appears to be for a charging cable (the Amazon listing doesn't seem to show a data rate). For installing GrapheneOS the key thing is the quality of data transmission.

I think you might be onto something here - thank you! I am going to try that cable you suggested.

ShadowKitty

Ok, I am back. I made some progress, but now a new weird issue is happening.
I used the new cable that @de0u suggested. I then also finally got the USB driver installed.

Graphene could see my phone and I was able to get through the step of "Download release."

At the next step, "Flash Release" this is where it got weird. After I clicked on that, it said it was restarting the phone a couple of times (and made that sound Windows makes when you connect a new device) but it just stayed on that black screen that has a red triangle and says "Fastboot Mode" (the one that shows when you first unlock the bootloader). So its like nothing happened.

This video shows at the 12:07 mark how the screen changes during the Flash Release - https://www.youtube.com/watch?v=qruzL9IdUr8 - but mine never did any of that.

Graphene said it had flashed the install to the device, but then under the Lock Bootloader section it says "Error: Failed to execute 'requestDevice' on 'USB': No device selected"

So somehow it got stuck at the Flash Release stage... I don't know what to do next. I don't want to mess up this phone. If I just turn it off can I try all this again from a different computer? Should I lock the bootloader first? I am lost.

If anyone has suggestions, like how to start over from scratch, it would help. Thank you!

I would like to take this over and try it on a friend's computer instead, but not sure how to get out of the spot I'm in with the phone... so that would be the main piece of advice (I'm stuck on the Fastboot Mode screen where it says its unlocked).

de0u

ShadowKitty Also, one thing to watch out for during flashing is that it can be disruptive if the device, the cable, or the computer are moved. You would also want to make sure that the computer doesn't decide it's idle and go to sleep (maybe tap a Shift key every now and then).

ShadowKitty

de0u . Can you confirm that when you wrote "I then also finally got the USB driver installed" you were referring to the Google USB driver?

Yes, I did .. in my Device Manager list it shows under Android Device - Android Bootloader Interface,

ShadowKitty

de0u

Thank you for your on-going help!! I really appreciate it!

Since it seems I was able to download the release.... but got stuck at the Flash release.... when I try this again, should I just jump to Flash release again from the Graphene Web Installer page? Most likely I will do this from a different computer just to see if that works better.