Related
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
http://www.mylgphones.com/tag/usb-drivers try these drivers
That's the ones that didn't work.
Same problem here... Any luck?
Change the USB mode to PTP and you should get the RSA prompt.
anod said:
Same problem here... Any luck?
Click to expand...
Click to collapse
Yes I have install Google universal usb drivers worked for me search on Google for them
PTP worked for me, no LG driver installed.
Just got my G3 on Verizon, cannot see the device over ADB either on Mac OSX
I tried MTP, PTP, and Charge only both with and without LG drivers installed. Since it's OSX, there are no Google Universal USB drivers.
Android File Transfer opens up fine, but ADB doesn't show the device. Quite fishy indeed.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
May I ask how you managed to connect your phone to your mac via MTP? I am unable to get any kind of connection to my mac.
On windows it works finde, I can open the internal and external sd card and copy files from and to the device, I would be more than happy to achive the same on my mac.
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
Hi there, you will first need to enable USB Debugging. Head over to Settings > General > About Phone > Software Information. Tap Build Number 5 times, and you'll unlock the Developer options.
Go to Settings > Developer options, and check USB Debugging. From there, ADB should work. Good luck!
OK, so I installed the new drivers, rebooted, and got ADB to recognize my LG, and was able to debug successfully. Now Android File Transfer doesn't see it, nor does Finder show the device. What am I missing?
It's broken, I saw a tweet from jcase regarding the issue. I have the same problem. I just adb push/pull when necessary for now.
Sent from my LGLS990 using XDA Free mobile app
EDIT - It wasn't jcase, it was @utoprime
Mine works fine on my Mac
faded03cobra said:
Mine works fine on my Mac
Click to expand...
Click to collapse
You have adb and MTP works? What OSX version?
Sent from my LGLS990 using XDA Free mobile app
Solution
rickythefox said:
Anyone got adb on latest Mac OSX working? I can connect in MTP mode but adb devices never shows my phone. Tried the Unified Driver v4.5 and v4.7 to no avail.
Click to expand...
Click to collapse
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
KAR0SH1 said:
I know this is a seriously old thread, but for future reference - if your device is NEVER recognised by adb from the start, no matter how much you add the vendor etc, open up Terminal.app and type this in:
cd ~/.android/
rm adbkey adbkey.pub
This will navigate to android's folder and remove the RSA keys your computer uses to identify with the phone. If the address of the folder is wrong you can alter the first line to whatever is appropriate.
Click to expand...
Click to collapse
Seriously old, and seriously unresolved (for me and a few people on reddit, at least). Still have not succeeded at getting ADB to detect G3 on USB, tried running the -usb flag on the cli and everything. Is there a working process yet? Verizon seems to be the outlier here as well...
Just worked for me on OSX Yosemite with a D855 on V10l:
- Update ADB (android platform tools)
- Install LG Driver (link is in this thread)
- Reboot
- run "rm ~/.android/adbkey" and "rm ~/.android/adbkey.pub"
- run "adb devices" (you should now see your G3)
- run "adb kill-server" (just to make sure there is no interference)
- quit all applications on your phone and go to home screen
- run "purpledrake_osx.command" which should now work
Inbetween (guess it was directly after running "purpledrake_osx.command") you should get a permission request on your phone which you should allow
Thanks
_ranch said:
Change the USB mode to PTP and you should get the RSA prompt.
Click to expand...
Click to collapse
Thanks, this works for me on El Captain
Also on El Capitan:
After enabling developer settings + USB debugging on phone (see earlier in thread),
Removing the adbkey + pub from the users .android folder (see earlier in thread),
and connecting with PTP,
It finally works
I'm having some trouble and I think it might be related to drivers. I'm on Mac OSX 10.8.5 so I downloaded the LGUnitedMobile_Mac_Driver_Ver_4.22 from here:
http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
I installed, restarted computer. When I plug in the G4 via USB I don't get the popup requesting ADB access. (I've got USB debugging on in Developer Options and it shows as on in Developer Options as well as a notification in the pulldown menu). If I tap on the notification from the pulldown for MTP options I'm asked if I want to install the drivers. So, I do that too and wait for it to complete. Still no ADB popup. If I open the Debloater tool, no welcome popup and the "device connected" light is red.
I tried toggling between MTP and PTP and still nothing. Tried unauthorizing my computer in Developer Options, unplugging, and waiting. Tried restarting phone.
Further, if I open Android File Transfer I get a message "No Android device found" whereas before trying to install the driver it found the G4 just fine. Ran the uninstall script from the LG driver software and Android File Transfer then CAN see the phone.
Any ideas? Any help would be appreciated - I'm trying to run the Debloater tool (which can't see the G4 either no matter what I try).
creaky said:
I'm having some trouble and I think it might be related to drivers. I'm on Mac OSX 10.8.5 so I downloaded the LGUnitedMobile_Mac_Driver_Ver_4.22 from here:
http://www.andromods.com/download-files/latest-lg-g4-drivers-usb-adb-win-mac.html
I installed, restarted computer. When I plug in the G4 via USB I don't get the popup requesting ADB access. (I've got USB debugging on in Developer Options and it shows as on in Developer Options as well as a notification in the pulldown menu). If I tap on the notification from the pulldown for MTP options I'm asked if I want to install the drivers. So, I do that too and wait for it to complete. Still no ADB popup. If I open the Debloater tool, no welcome popup and the "device connected" light is red.
I tried toggling between MTP and PTP and still nothing. Tried unauthorizing my computer in Developer Options, unplugging, and waiting. Tried restarting phone.
Further, if I open Android File Transfer I get a message "No Android device found" whereas before trying to install the driver it found the G4 just fine. Ran the uninstall script from the LG driver software and Android File Transfer then CAN see the phone.
Any ideas? Any help would be appreciated - I'm trying to run the Debloater tool (which can't see the G4 either no matter what I try).
Click to expand...
Click to collapse
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.
uly609 said:
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.
Click to expand...
Click to collapse
Thanks for the response. Tried that (typed adb devices in Terminal) and got this: -bash: adb: command not found
Not sure what I'm doing wrong here.
Do you have installed the android sdk?
creaky said:
Thanks for the response. Tried that (typed adb devices in Terminal) and got this: -bash: adb: command not found
Not sure what I'm doing wrong here.
Click to expand...
Click to collapse
If I remember correctly you need to download the android sdk and install the sdk and platform tools. When you do this make sure you make a folder on your desktop and name it whatever you want, and when you install the sdk make sure the install path goes to the folder you made. Then open a terminal window and navigate to the folder you installed the sdk to.
Then run the adb command, but it will be slightly different:
./adb devices
uly609 said:
You won't get the adb popup until you run an adb command in terminal. for example adb devices command is what triggered my popup.
Click to expand...
Click to collapse
wadamean said:
Do you have installed the android sdk?
Click to expand...
Click to collapse
I had to reinstall - that was the problem. Thanks!
uly609 said:
If I remember correctly you need to download the android sdk and install the sdk and platform tools. When you do this make sure you make a folder on your desktop and name it whatever you want, and when you install the sdk make sure the install path goes to the folder you made. Then open a terminal window and navigate to the folder you installed the sdk to.
Then run the adb command, but it will be slightly different:
./adb devices
Click to expand...
Click to collapse
Thanks again for the help. Problem solved.
Hey so then you were able to root using your mac? what variant g4 do you have? Could you please message me what steps you did to get successful root? i would really really appreciate it. its very rare to find mac users.
wadamean said:
Hey so then you were able to root using your mac? what variant g4 do you have? Could you please message me what steps you did to get successful root? i would really really appreciate it. its very rare to find mac users.
Click to expand...
Click to collapse
Not root, used Debloater tool to block updates. Would love to see a Mac root method released.
oh i see then. i will keep patiently waiting for a simpler root method. this one is already but for sure there has always been even more simpler methods surfaced.
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.
After upgrading to Android Q suddenly my pc can't recognize my pixel as a android device also i can't connect any wired things such as dongle jack or USB Transfer (USB charging options disappeared).
Planning to downgrade to Pie but the problem is my device can't be detected on my pc. Any solutions? Thanks
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!
simplepinoi177 said:
If you're using a Microsoft Windows machine, I would suggest uninstalling any "Android" drivers from the Device Manager. Then restart the PC, then turn off "USB debugging" and back on for the Pixel, and even "Revoke authorizations" in hopes that it will re-alert & request another authorization and, therefore, verify it being connected and detected on the PC....
After all that -- or if you can only enter in Bootloader Mode -- type the command "fastboot devices" and say here what it outputs. If anything, while in Bootloader Mode, do what I previously said, but look for anything "Android" and "Bootloader" and uninstall those device drivers...
Good luck and hope this helps!
Click to expand...
Click to collapse
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
blancheSX said:
Thanks for replying, i already tried to uninstall android driver, but when i try to reconnect, my pc recognize my device as "unknown device"
Click to expand...
Click to collapse
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU
I have this issue before, and after all i got my phone detected. But when i flash it, it say unbootable slot in fastboot screen. After couple onf time, it cant be flashed again and die.... My phone cant turn on in fastboot mode again, it bricked
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
If anyone is still having the issue of PC not recognizing device in fastboot, please be sure you have UNinstalled the older version(s) of SDK Tools from yhour PC and make sure to INSTALL the latest versions.
You can find the latest version linked in the 9x guide in my signature.
Also, make sure you have both older and newer USB cables handy. The Pixel has a nasty reputation for being finicky with USB cables, try diff cables and different USB ports on your PC.
There is also a basic troubleshooting guide in the same link in my sig.
Best regards!
simplepinoi177 said:
what about the other things I suggested?
Or, so it can be clearer, are you in the System/OS when plugging/reconnecting or in Bootloader Mode?
Click to expand...
Click to collapse
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
dallas90733 said:
I ran across the same issue..I followed this video to get rid of the old USB drivers and updated to the new Android driver.. Now my window 10 recognize my pixel 2xl storage completely.
https://youtu.be/Zc_dhxc8iJU
Click to expand...
Click to collapse
i tried those tuturial and ended in error code : 10, device cannot started.
SageWilliams said:
I had to use the USB dongle to connect a flashdrive to my phone, wait for it to recognize the drive, then unplug the drive and dongle... Then connect phone to PC... Profit!
Click to expand...
Click to collapse
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
blancheSX said:
i did in 2 conditions, first one is my device turned On (adb is not detected) also 2nd one is my device in bootloader mode (fastboot devices is not detected too)
been trying to update my driver but i always got (error code : 10, device cannot started) i dunno what to do right now
Click to expand...
Click to collapse
blancheSX said:
whenever i try to connect a flashdrive with my dongle, there is no option or something, it's just usb charging option appeared.
Click to expand...
Click to collapse
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Only THEN, once these two things are extracted and installed (as is the case in the first step) and you revoked the authorizations, can you plug in your device and USB cord. Watch your phone/device, as it will ask for authorization to connect to your computer, and you’ll have to make sure the box is checked that says “don’t ask this every time” or “remember this device” – I can’t recall off-hand – and then make sure to “Allow” it. By doing this, you can be sure that your computer and device are talking correctly.
*One suggestion that isn’t mandatory is that you select where it says “USB charging” and change it to “MTP” or “file-sharing” (sorry, again, I can’t recall specifically off the top of my head…)
If all things are working well, if you can open up a command prompt (a.k.a. “cmd”, and also make sure you are running it “As an administrator”) and direct it to the platform-tools directory (hopefully you followed my suggestion and kept it simple so it will either be at the root “C:\” or on your Desktop “C:\Users\[username]\Desktop” so it won't be too difficult directing it there...), and run the commands
Code:
adb devices
and
Code:
fastboot --version
.
Hopefully, if you do all of these things, it might get things reset and working from a stable established set up.
If it somewhat works, but the device in your "Device Manager" is showing up something "funky", then it'll take a rather nuanced Windows troubleshooting technique to resolve where I would have you correct the wrong entry/driver in the "Device Manager" and have it specifically point to one of the contents of the .zip files; shown prior.... We'll tackle that if need be and if all this initial beginning troubleshooting doesn't pan out...
Let me/us know how it works out, good luck, and hope this all ends up being helpful…
simplepinoi177 said:
So…without you being too definitive…it seems that you’re able to get into your OS…
What I’d like you to do is uninstall and remove Google usb drivers on your computer. Then, download it again HERE: https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip . And, in case things don’t work out this time around, if you can please save the (.zip) file on your Desktop or root folder (usually the C: drive). I might have you direct the device detected to the files in this .zip directly.
Then, after installing the USB drivers, I’d like you to uninstall and remove any/all things that are named “platform-tools” (so there will only be ONE "platform-tools" after you re-download it in this step) on the whole device. After, I’d like you to download the latest Windows version HERE: https://developer.android.com/studio/releases/platform-tools . Again, to simplify things, if you can extract it either in your Desktop or root folder (C: drive).
Again, like I mentioned before, I would like for your device to request authorization for your computer again, so if you can please go to the Developers option, and select “Revoke USB debugging authorizations” as well as double-checking you have "USB debugging" enabled…
Click to expand...
Click to collapse
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
blancheSX said:
thanks for ur explanation, and i'm sure i already did this 100% as you mentioned before. looking for solution and i found this at pixel community thread : https://support.google.com/pixelphone/thread/14477635?hl=en
and btw when i try to disable and back to enable (again) USB debugging, there's no pop up or something like that, just nothing appear. so i just realized why i got error code : 10 is just because my phone still not detected by PC also i tried in other computer (with windows 8.1 installed) my device is got detected but as "device descriptor request failed" not as an android device. Hopefully next update google will fix this "bug". Once again thank you very much
Click to expand...
Click to collapse
Yeah...I figured as much...I was just making sure to lay down the "ground work" before proceeding...
If you're still willing....what I had planned next was to walk you through manually updating/"editing" the driver (on the PC) to directly look at the Google usb drivers specifically to try and get around the whole "device descriptor" and other (detection) error codes.......
Might want to try uninstall the SDK toolkit, reboot PC, then install the latest SDK toolskit.
Also having both USB 2.0 and 3.0 cables saved me more than once, and is a known thing on the 2XL.
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.