Develop Bugs

[Q] Can't get ADB to work, have tried everything

Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies

expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.

Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
Hi Dave, thanks for the reply.
I definitely have USB Debugging enabled - I also am 100% sure that I have installed the hboot driver before (I did it when rooting for the first time ages ago), and can confirm this by booting into Bootloader and having "Android Bootloader Interface" appear as a known device.
Also, with the HBOOT-Driver, it lists the phone as "Android 1.0" when Unknown, whereas my situation lists "Android Phone" as the unknown device.

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Click to expand...
Click to collapse
Same here.

Have you added the environment variable for the sdk directory? It won't work if you don't.

Also.. install .. HTC Sync.. .and try.. and again uninstall only HTC sync.. and leave the HTC driver and try

I've had issues getting it working too and haven't quite figured out the sequence to get it to work. All I remember is the Android SDK drivers don't work, you need to use the HTC ones. You don't need to uninstall HTC Sync (try re-installing it though). You might then need to run update drivers on the unknown device for it to find them.
I can confirm that it does work with HTC Sync still installed. I sometimes find ADB devices takes a few attempts or restarting ADB to actually work.

vnvman said:
Have you added the environment variable for the sdk directory? It won't work if you don't.
Click to expand...
Click to collapse
Hi vnvman.
Thanks for the reply - I have indeed, my "PATH" value is as below:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\XviD MPEG-4 Video Codec 1.2.2 64-BIT;C:\Program Files (x86)\Common Files\Teleca Shared;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\QuickTime\QTSystem\;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools
Click to expand...
Click to collapse
However, even if I cd in CMD to the platform-tools folder and run adb from there, no luck. ADB itself works perfectly, but it just doesn't recognize my phone.

bobsie41 said:
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.
Click to expand...
Click to collapse
Like some others users posted here, win 7 x64 is working for me without any problems.
expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
Try to reinstall android sdk completely following this guide:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK

Hi MatDrOiD.
Thanks for the reply, I'll give that a shot as well as try jhonybravo4u and Antcodd's ideas.
Appreciate all input. If I get it working, I'll be sure to update this post so that anyone else who might have this problem has a solution

davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
What i meant is that windows 7 seems 64bit seems to cause more problems than any other windows os. I had a windows 7 64bit computer and after days of pratting about i managed to get it working now, further down the road, and a bit more knowledgable(i think!) i have a new more powerful windows 7 64bit machine and i can't for the life of me get it working.
I know run adb from my wifes vista laptop and had no trouble whatsoever in setting this up.

If u tried "everything", u better don't ask for more ;-p
Sent from my HTC Desire using XDA Premium App

It worked for me last time, but then I formatted my drive, and now can't get it to work for the love of god. Actually I can, but I have to change the driver every time Android phone pops up in the device manager using have disk.

[Q] ADB works, but no MTP/PTP functionality

So I got my Nexus 7 2013 to work perfectly on my laptop, which runs Windows 7 x64. However, on my desktop, which also runs Win7 x64, I only have the ADB working correctly for the N7. As I recall, sometimes there is a device under Device Manager called "D:/", which is non-descriptive, but seems like the closest thing to the N7. I have tried to update this mysterious device's drivers by pointing to Google's USB drivers and the OEM drivers, but neither was accepted. There are also no devices with missing drivers listed in Device Manager.
At this point, I am not sure how to proceed. Is there a precise way identify under what device name/category the N7 shows up in Device Manager? Please advise. :fingers-crossed:

See if this helps:
http://forum.xda-developers.com/showthread.php?t=2391236

Cool, I'll give this a try in a bit.

zeppelin101 said:
Cool, I'll give this a try in a bit.
Click to expand...
Click to collapse
I cant get Nexus 7 to show has folder when check in MTP mode. it will show as camera folder PTP. Any solutions to this problem? very frustrating!

mickrg123 said:
I cant get Nexus 7 to show has folder when check in MTP mode. it will show as camera folder PTP. Any solutions to this problem? very frustrating!
Click to expand...
Click to collapse
Make sure USB Debugging is disabled, device is plugged in, and go to device manager in windows. Then right click on nexus 7 or android adb device, or any similar name. Then after uninstalling everything, unplug device and replug it in. Let windows get the drivers, and MTP should work!

fevanson said:
Make sure USB Debugging is disabled, device is plugged in, and go to device manager in windows. Then right click on nexus 7 or android adb device, or any similar name. Then after uninstalling everything, unplug device and replug it in. Let windows get the drivers, and MTP should work!
Click to expand...
Click to collapse
Thats my problem it doesn't when trying this.

mickrg123 said:
Thats my problem it doesn't when trying this.
Click to expand...
Click to collapse
get this and delete anything related to google and adb.
http://www.nirsoft.net/utils/usb_devices_view.html

fevanson said:
get this and delete anything related to google and adb.
http://www.nirsoft.net/utils/usb_devices_view.html
Click to expand...
Click to collapse
Deleted everything related to google and nexus. Still installs as adb device but doesnt show as nexus 7 device! Wug fresh has this program in its tool kit

It might sound dumb, but I was literally just having this issue. But apparently certan roms or kernel disable MTP mode when they are installed. i reinstall every driver just now. My fix was as easy as going to Settings > Storage > Menu Button Top right > Enable MTP box.

tonu42 said:
It might sound dumb, but I was literally just having this issue. But apparently certan roms or kernel disable MTP mode when they are installed. i reinstall every driver just now. My fix was as easy as going to Settings > Storage > Menu Button Top right > Enable MTP box.
Click to expand...
Click to collapse
What kernal or rom are you running?
---------- Post added at 10:10 PM ---------- Previous post was at 10:02 PM ----------
mickrg123 said:
What kernal or rom are you running?
Click to expand...
Click to collapse
Going to try a custom rom see if that works!

I have tried a number of the suggestions in this thread, including the deletion of all my google/adb/nexus (and samsung) drivers. None of these steps resolved my problem. However, at the end of the day, I can still use both ADB and MTP, just not at the same time. So it's not a big deal. I think I will mess around with Tasker and/or get a widget for turning ADB on/off.

Are you ale to get a nexus 7 device to show so you can access internal storage? I can only access camera storage.

mickrg123 said:
Are you ale to get a nexus 7 device to show so you can access internal storage?
Click to expand...
Click to collapse
Yea, that's what MTP is.

zeppelin101 said:
Yea, that's what MTP is.
Click to expand...
Click to collapse
That's my problem I can't access mtp.

mickrg123 said:
Are you ale to get a nexus 7 device to show so you can access internal storage? I can only access camera storage.
Click to expand...
Click to collapse
Are you running stock?
If so, do you have USB debugging turned on?
If you have USB debugging turned on, the USB IDs change and it might not (depending on what you have previously installed) recognize the MTP device anymore.
If you turn off USB debugging, it should recognize MTP.
Now if you are on a custom ROM, there might be some issues on the ROM side causing the MTP problem. Try going back to stock and see if it works.
If you are on stock and have the case where MTP only works with USB debugging disabled, then you can try this driver inf I put together to address that.
It is available in this thread:
http://forum.xda-developers.com/showthread.php?t=2391236

Device Shown as Offline after GPe rom flash

Hi all,
I rooted my M8 recently with the Windroid toolkit. Everything worked great, and I flashed the digitalhigh GPE rom and love it.
Now when I try to connect my phone to my computer, I do not receive the prompt for RSA key trust. My phone shows offline on my 8.1 VM and it is just not found on my Windows 7 machine. It also shows offline on a Macbook Air. I have tried everything I can find to get USB debugging to start working again but I just can't seem to find out what needs to be done. I have the latest version of the HTC drivers I believe and I should have the latest add drivers. On Sense, I had to turn on USB debugging and select the phone to be mounted as a disk drive for WinDroid to be able to root my phone.
So, how can I get this fixed? Is it an issue with the ROM? Is there some way that I can turn on a disk drive mode on the rom.
Any help is appreciated!
Thank you.

Check the device manager in Windows. Does it state a 'unknown device' (or similar)
Sent from my HTC One_M8

Joery360 said:
Check the device manager in Windows. Does it state a 'unknown device' (or similar)
Sent from my HTC One_M8
Click to expand...
Click to collapse
Looking at device manager, it shows my phone in two different places. It shows once in 'other devices' as just android phone and then under 'portable devices' as the name of the phone.
When I go into detail under 'other devices', device manager show that drivers are not installed but says everything is installed correctly under 'portable devices'.
I have the latest version of Sync Manager, so by that reasoning I should have the latest version of the HTC drivers. What else would I need to get my phone to not show as offline?
Thank you

RaspberryRye said:
Looking at device manager, it shows my phone in two different places. It shows once in 'other devices' as just android phone and then under 'portable devices' as the name of the phone.
When I go into detail under 'other devices', device manager show that drivers are not installed but says everything is installed correctly under 'portable devices'.
I have the latest version of Sync Manager, so by that reasoning I should have the latest version of the HTC drivers. What else would I need to get my phone to not show as offline?
Thank you
Click to expand...
Click to collapse
Uninstall Sync Manager. It doesn't play nice with ADB. The only thing it is good for if you are rooted is installing the drivers. After that, get rid of it.

xunholyx said:
Uninstall Sync Manager. It doesn't play nice with ADB. The only thing it is good for if you are rooted is installing the drivers. After that, get rid of it.
Click to expand...
Click to collapse
Hm, alright. I will try that.
Thank you.

Still having issues
Hello all,
I am still having issues with getting my computer to recognize that USB debugging is on and getting it connected to my computer with adb. I have uninstalled sync manager, and yet my phone is still not recognized.
Under debugging in developer options, the only thing I have checked is USB debugging.
Is there something else that needs to be checked in the developer options? Why do I still have this issue?
P.S. I would post pictures, but I can't unfortunately :\

RaspberryRye said:
Hello all,
I am still having issues with getting my computer to recognize that USB debugging is on and getting it connected to my computer with adb. I have uninstalled sync manager, and yet my phone is still not recognized.
Under debugging in developer options, the only thing I have checked is USB debugging.
Is there something else that needs to be checked in the developer options? Why do I still have this issue?
P.S. I would post pictures, but I can't unfortunately :\
Click to expand...
Click to collapse
Hey man, you constantly have to go to here... And change the option from charge only to whatever you want

bford152 said:
Hey man, you constantly have to go to here... And change the option from charge only to whatever you want
Click to expand...
Click to collapse
Thanks for the reply bford152. Oddly, I do not have this option available to me.
I would like to post pictures of the options I have under USB debug. But even posting a link and not having it parse still tries to read it and says I cannot post outside links. Next question, how do I attach photos without adding it as a link to the post. Maybe I'm blind, because I cannot see an option to do this.
Thanks everyone!

What's your adb version ?
It needs 1.0.31 for Android 5.1 and 1.0.32 for Android 6.0 (minimum requirement)
Have you tried with a secured kernel/boot.img ? If you don't have "Revoke USB debugging authorizations" in Developer options - means that you have insecure kernel installed.

ckpv5 said:
What's your adb version ?
It needs 1.0.31 for Android 5.1 and 1.0.32 for Android 6.0 (minimum requirement)
Have you tried with a secured kernel/boot.img ? If you don't have "Revoke USB debugging authorizations" in Developer options - means that you have insecure kernel installed.
Click to expand...
Click to collapse
I have adb version 1.0.32, so all good there.
I don't seem to have "Revoke USB debugging authorizations". So, I have Elite kernel right now and I guess that's the issue. I will get a different kernel and see if that helps.
Thanks!

RaspberryRye said:
I have adb version 1.0.32, so all good there.
I don't seem to have "Revoke USB debugging authorizations". So, I have Elite kernel right now and I guess that's the issue. I will get a different kernel and see if that helps.
Thanks!
Click to expand...
Click to collapse
I got everything to work now. Switched to Cyanogenmod 12.1 and it gives me all the options I need. Thanks for all your help.

adb will not work

I have got my device to be recognized by my PC but adb will not work ... Can anyone provide help on how to make it work?

When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.

dratsablive said:
When you plug the phone into the PC, pull down the notification area and change the USB options from Charging to Transfer Files.
Click to expand...
Click to collapse
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work

canemaxx said:
I've done that...the phone is recognized by my PC just not when I run adb devices...nothing shows up ...adb reboot doesn't work
Click to expand...
Click to collapse
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?

Lawlrus said:
Did your phone prompt you to allow the computers fingerprint ? If not toggle debugging a few times till it does.
You have updated sdk and driver's ?
Click to expand...
Click to collapse
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC

canemaxx said:
I don't have fingerprint set up but I have toggled back and forth and do not get the prompt to allow connection to my PC
Click to expand...
Click to collapse
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computers fingerprint, meaning make alterations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use

Lawlrus said:
I'm not talking about fingerprint protection, when you switch to other modes aside form Charing when you have USB debugging turned on, if will prompt you to accept the computer fingerprint, meaning make altercations to your device.
You need to allow that, and if you're not getting that prompt, update your sdk tool, drivers, u install the drivers, reinstall them, try a different cable/USB port/ computer. Pretty much do all the basic trouble shooting.
My device was very picky about what port I could use
Click to expand...
Click to collapse
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?

canemaxx said:
That's what I'm not getting is that prompt ...it will connect for mtp and PTP file transfer but will not recognize adb. Which ask version are you using and do you have a link?
Click to expand...
Click to collapse
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Try running adb devices and see if it will make the prompt show up

Lawlrus said:
Can't check because I'm not home, all I know is I used minmal fastboot and adb tools because my windows uses powershell not cmd.
Doesn't Google link the newest on the page for their official images ?
Click to expand...
Click to collapse
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl

canemaxx said:
Yeah and that's what I downloaded was their latest version of platform tools. I just don't get this. I'm so close to returning this phone and just keeping my og xl
Click to expand...
Click to collapse
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.

Lawlrus said:
Whatever works for you lol. Can promise you that this is not the ONLY device that can give issues on the first time getting adb to work. I've had it happen on two other devices that were Nexus units.
Click to expand...
Click to collapse
I don't get what else I could do to make this work tho that's the problem....what am I missing

USB debugging enabled?

Heisenberg420 said:
USB debugging enabled?
Click to expand...
Click to collapse
Ues

canemaxx said:
Ues
Click to expand...
Click to collapse
Try running adb kill-server and then adb devices

Heisenberg420 said:
Try running adb kill-server and then adb devices
Click to expand...
Click to collapse
Bro thank you!!!! That worked

canemaxx said:
Bro thank you!!!! That worked
Click to expand...
Click to collapse
Yep

canemaxx said:
I don't get what else I could do to make this work tho that's the problem....what am I missing
Click to expand...
Click to collapse
Adb kill-server worked

I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.

Yooperjusty said:
I hope someone still sees this post. I have a friends Google Pixel XL that I was able to revive from a bootloop by sideloading the latest OTA. Upon starting up, my friend forgot his screenlock passcode. I've been trying everything to get the device recognized in bootloader mode on my pc. It keeps showing up blank. I am trying to use ADB to bypass the unlock code. If anyone has an idea how I can get into this phone BEFORE I reset it, that would be very appreciated! It is not rooted and no unlocked bootloader.
Click to expand...
Click to collapse
You have to enable USB Debugging in settings in order to delete the unlock code. Unfortunately, you can't because he forgot it. You can try booting TWRP on the device using fastboot and see if you can delete the unlock code's key file using TWRP's file manager, but the reality here is that you likely will have to reset. Hope your friend didn't use a throwaway email address when setting up the device.

adb fastboot not seeing device

Sorry for noob question. Searched Searched xda and can't find anything. Pixel3 xl. Stock Android 10. Rooted. Windows 10 with correct drivers so it sees device. Can transfer files easily. USB debugging enabled. ADB and Fastboot do not see device. Used to work but not now. Tried kill-server and start-server in ADB. Tried different cables, restarting phone and computer. No luck. In fastboot mode (on phone) fastboot devices returns nothing. Totally stumped. Can anyone help. Again apologize for noob question but this has always worked before and I've flashed roms as well as stock numerous times with no issues till now. Help!

Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?

sliding_billy said:
Do you have the current platform tools https://developer.android.com/studio/releases/platform-tools.html, and are you in the platform tools directory in command prompt or have your path set correctly?
Click to expand...
Click to collapse
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.

Daisymae said:
I have the latest tools. Path set correctly as far as I can tell. I'm running the commands from the directory. Nothing. What kills me is that I never had this problem before untill I reinstalled Windows with a fresh copy.
Click to expand...
Click to collapse
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/

jd1639 said:
You might need to allow unsigned drivers. Here's one how to, https://www.howtogeek.com/167723/ho...8.1-so-that-you-can-install-unsigned-drivers/
Click to expand...
Click to collapse
Thanks. Did that. Same thing. Blank list.

Daisymae said:
Thanks. Did that. Same thing. Blank list.
Click to expand...
Click to collapse
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.

Have you recently updated and not re-authorized your phone?

sliding_billy said:
I think the easy step to determine if it is a phone or computer issue is to at least try from another computer. The one thing that did just occur to me would be to make sure you are using an A>C USB cable and A port and not a C>C with a C port. The Pixel series has tons of problems with C>C.
Click to expand...
Click to collapse
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.

spotmark said:
Have you recently updated and not re-authorized your phone?
Click to expand...
Click to collapse
Turned usb debugging off then back on again. When I plug in a cable I reauthorize usb debugging but get the same results.

Daisymae said:
Thanks. Don't have another windows computer to try on. Do have an old Mac and it works on that, just not my windows laptop which is what I use. I have no idea what's making this happen. Computer sees the phone just fine.
Click to expand...
Click to collapse
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.

sliding_billy said:
To my previous comment, are you using an A>C cable or the C>C that comes with the phone/charger? Besides that, it still sounds like it could be a driver issue where it is recognizing the phone as a generic USB storage device.
Click to expand...
Click to collapse
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.

Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
If you boot to the bootloader and plug the phone in, does Windows recognize it then?

Daisymae said:
I'm using an A-C cable. Same that I used before when it worked. I thought it might be a device driver too but when I plug the phone in the computer immediately sees it and if I open device manager the phone is seen as an android device.
Click to expand...
Click to collapse
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.

ktmom said:
If you boot to the bootloader and plug the phone in, does Windows recognize it then?
Click to expand...
Click to collapse
No. Tried that first thing. Fastboot devices turns up nothing.

sliding_billy said:
OK, thanks. One thing I can think to do is delete the driver, reboot the phone and computer and then plug in and start over. Make sure to use the Google device driver from the developer page.
Click to expand...
Click to collapse
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.

Daisymae said:
Believe it or not I already did that. I've tried everything with no luck. As I mentioned I was always able to use it before with no problems then this started when I reinstalled a fresh copy of windows.
Click to expand...
Click to collapse
just for the heck of it, do you have other cables. Stranger things have happened that made a difference, and the next suggestion involves reinstalling computer and/or phone. Maybe a live USB Ubuntu disk to see what is working and what is not.

Daisymae said:
No. Tried that first thing. Fastboot devices turns up nothing.
Click to expand...
Click to collapse
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.

ktmom said:
I understood fastboot devices doesn't see it, but does Windows show a driver installed for it? I strongly suspect you don't have (the right) drivers properly installed.
Click to expand...
Click to collapse
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.

Daisymae said:
Yes. Windows shows a driver installed and when plugging it in identifies it as a Pixel 3 XL.
Click to expand...
Click to collapse
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?

Homeboy76 said:
Do a search for fastboot, if you find more than one delete the one that is not in your Platform-tools folder.
Did you give fastboot execute permission?
Click to expand...
Click to collapse
Only one instance of fastboot. Not sure what you mean execute
permissions. You mean on Windows or on the device? Windows has execute permissions. I don't have adb or fastboot on the device.