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.
Related
ADB isnt working..well it is but saying my phone is "unauthorized"...I have researched the mess out of this and nothing is working to get it working again.
I am on windows 10 and my windows key file is not in any of the locations to "delete"...the problem I see is almost always solved by getting on your computer and deleting the rsa key file, then you will just get prompted for another.
Well all the locations I have found to go in an delete it, its not in there.
fastboot works right, and adb tries to run, but just reads unauthorized.
any help is appreciated.
thanks
Disconnect your phone. Open developer options. Go down and select revoke usb debugging authorizations. Plug your phone in again and wait for the popup to authorize the phone. you might have to issue adb devices to get the pupup to show.
See if that works.
PiousInquisitor said:
Disconnect your phone. Open developer options. Go down and select revoke usb debugging authorizations. Plug your phone in again and wait for the popup to authorize the phone. you might have to issue adb devices to get the pupup to show.
See if that works.
Click to expand...
Click to collapse
Have tried this too...I haven't found a "usual" solution that works.
Sent from my Nexus 5X using XDA-Developers mobile app
Your computer's RSA key may be corrupted.
You can try nuking these and ADB should regenerate new ones.
I have no idea where they could be stored on a Mac or Windows box, but on a Linux box, these are ~/.android/adbkey and ~/.android/adbkey.pub.
Fif_ said:
Your computer's RSA key may be corrupted.
You can try nuking these and ADB should regenerate new ones.
I have no idea where they could be stored on a Mac or Windows box, but on a Linux box, these are ~/.android/adbkey and ~/.android/adbkey.pub.
Click to expand...
Click to collapse
Have tried this and there is no key file in the two places they are stores on Windows machines.
Sent from my Nexus 5X using XDA-Developers mobile app
joho5 said:
Have tried this and there is no key file in the two places they are stores on Windows machines.
Sent from my Nexus 5X using XDA-Developers mobile app
Click to expand...
Click to collapse
You should have these files.
Have your tried another computer or reinstalling the Android SDK (adb and friends)?
Fif_ said:
You should have these files.
Have your tried another computer or reinstalling the Android SDK (adb and friends)?
Click to expand...
Click to collapse
The phone works fine on my other computer using adb.
I dont use the whole sdk...I just use the adb and fastboot part of it, which I downloaded from an alternate location on xda. I have always done this with nexus 4, 5, 5x, oneplus 1, 2 and x.
I have tried revoking authorizations, tried finding file to delete on pc, tried toggly adb debugging on and off, different cable, different port, factory reset...I have tried everything
Out of ideas
joho5 said:
The phone works fine on my other computer using adb.
I dont use the whole sdk...I just use the adb and fastboot part of it, which I downloaded from an alternate location on xda. I have always done this with nexus 4, 5, 5x, oneplus 1, 2 and x.
I have tried revoking authorizations, tried finding file to delete on pc, tried toggly adb debugging on and off, different cable, different port, factory reset...I have tried everything
Click to expand...
Click to collapse
Did you by any chance find a solution? Ive tried everything aswell, reinstalled the whole android studio and formatted my phone. Nothing on the web works
Joshf17000548 said:
Did you by any chance find a solution? Ive tried everything aswell, reinstalled the whole android studio and formatted my phone. Nothing on the web works
Click to expand...
Click to collapse
I don't know if it is important for OP anymore, but on my PC the adb key is stored in %UserProfile%\.android (in case you wanted to dry deleting that directory and having it repopulated)
For example
C:\Documents and Settings\username\.android\adbkey
C:\Documents and Settings\username\.android\adbkey.pub
C:\Users\username\.android\adbkey
C:\Users\username\.android\adbkey.pub
its been around a year now, did u find a solution?
my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Evnul000 said:
my oneplus 3 does not connect to my pc. I have tried turning on and off developer options, turn off and on oem unlocking and usb debugging. I change the usb connection to mtp from charging but does not change. Also does not recognize it when i connect to pc. Also does not pop up on status bar and i checked portable devices. I also tried installing the oneplus drivers. i am on Android 7.0 freedomos-2.5. Any way to fix this issue? i might try to update freedomos because im on a old version of it.:crying:
Click to expand...
Click to collapse
Windows drivers 100%.
null0seven said:
Windows? If, yes windows drivers are the problem.
Try to other pc, to see if it works., first.
Click to expand...
Click to collapse
I have tried it on both my PC and laptop with both windows 10. Does not work. My PC also has windows 7 still seems to not work. Are there any other drivers i might be missing?
i have also done some research that you should update your drivers from device manager. I dont see anything related to my device. i went to portable devices nothing and i dont have a other devices section in device manager. Any help?
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
null0seven said:
What recovery?
Try to flash latest twrp. I use blu-spark by eng-stk. You can fla**** thru recovery or Flashify app.
Click to expand...
Click to collapse
i am on the latest twrp. will blu-spark help fix it?
ive also found out theres no kedcom driver when i go to fastboot. i even reinstalled adb drivers to insure its there but it does not pop up.
You'll need to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
I once have kind of youre problem connecting to my laptop (win.10). But, at work, on that laptop, connection was ok (win.7).
I reinstal windows 10 and connection works fine, since.
I allways use latest TWRP & version of rom. I can't tell for sure what it's goin on with youre phone.
If i was in youre situation i format my phone (this will erase ALL in youre phone). And if PC still does not see the phone reinstall windows.
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
dentman said:
You'll bed to remove drivers reboot, install correct drivers, reboot and then be nice to everyone you ever meet and it'll show up. It's a real pain but you can get there. XDA tutorial all the way there!
Click to expand...
Click to collapse
What are the driver links if you have? I already installed the OnePlus drivers.
ninjeratu said:
Also: Try a different cable.
A cheap cable could have a charging pin layout but lack data pins connections.
9 out of 10 issues with connecting to PC and getting odd behaviours is due to a bad/wrong cable.
Click to expand...
Click to collapse
I used the OnePlus cable and another cable.
Driver issues win 10
Find the excellent tutorial here on drivers.
For some reason my phone didn't show up but was able to receive commands. It was frustrating because I wanted to use the all in one XDA product but couldn't.
Even if you installed drivers they can be broken!
Do drivers from scratch per xda tutorial. Don't forget reboot!
Try different cables and usb ports! My front ones never seem to work!
Don't just try fastboot commands also try adb. Like I said mine wasn't seen properly yet it took the commands.
Unless your windows is a years old install it shouldn't require reinstall.
Factory phone reset might help.
Best of luck!
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.
I flashed a custom rom and now my PC does not recognize my phone. I can't transfer files or fastboot to the phone from the PC.
I wanted to go back to stock, but when I went to flash-all, it stalls at waiting for device.
Not sure what happened, any help solving this would be appreciated.
It's not the drivers in the PC, it's something that happened within the phone.
Gordietm said:
I flashed a custom rom and now my PC does not recognize my phone. I can't transfer files or fastboot to the phone from the PC.
I wanted to go back to stock, but when I went to flash-all, it stalls at waiting for device.
Not sure what happened, any help solving this would be appreciated.
It's not the drivers in the PC, it's something that happened within the phone.
Click to expand...
Click to collapse
Deleted
Gordietm said:
I flashed a custom rom and now my PC does not recognize my phone. I can't transfer files or fastboot to the phone from the PC.
I wanted to go back to stock, but when I went to flash-all, it stalls at waiting for device. Not sure what happened, any help solving this would be appreciated. It's not the drivers in the PC, it's something that happened within the phone.
Click to expand...
Click to collapse
You should also try a different A-C cable. Do you still have a custom recovery or stock? If so you can use adb to push/pull files to the phone and try "update via adb". Have you done a full factory reset?
It's not the cable, I've a few different ones. I can't use adb, because the PC doesn't recognize that Mr phone is connected.
Gordietm said:
It's not the cable, I've a few different ones. I can't use adb, because the PC doesn't recognize that Mr phone is connected.
Click to expand...
Click to collapse
Have you enabled usb debugging , reinstalled the Google usb drivers, is the adb folder all right (maybe re-downlaod an re-install).
gee2012 said:
Have you enabled usb debugging , reinstalled the Google usb drivers, is the adb folder all right (maybe re-downlaod an re-install).
Click to expand...
Click to collapse
I have enabled USB debugging, the adb floder is fine. I still have to try updating the drivers, haven't done that yet. Thanks
Gordietm said:
I have enabled USB debugging, the adb floder is fine. I still have to try updating the drivers, haven't done that yet. Thanks
Click to expand...
Click to collapse
Turns out that restating the PC did the trick.
Everything works now. Thanks for the help.
Firstly, this sounds like a very noob question and I am sorry, but I have unlocked phones in the past so I should know how to do this, yet I am running into an issue. I am trying to unlock bootloader on this phone, but my phone is not recognized at all by my pc. If I am in Android and I connect my phone I should get the dialog where it asks me if I want to transfer files or charge my phone etc., right? Yet this dialog doesn't appear. If I enable debugging and type 'adb devices' I get 0 devices. If I reboot to bootloader and try 'fastboot devices' I get nothing. Am I missing something obvious here? I tried both Windows and Linux and got the same results, my phone is just invisible. Do you have any advice? I bought the phone today and I am running the latest software V13.0.10.0.SKOEUXM.
Mthw said:
but my phone is not recognized at all by my pc. If I am in Android and I connect my phone I should get the dialog where it asks me if I want to transfer files or charge my phone etc., right? Yet this dialog doesn't appear.
Click to expand...
Click to collapse
Different usb port/cable. Open device manager and see if it reloads when you plug it in, if yes, than you need drivers.
abcxdaabc said:
... see if it reloads when you plug it in, ...
Click to expand...
Click to collapse
If it doesn't, do I have a bad device?
I tried a different computer and a different cable (the original one is a mess and so is my win11 pc), and it worked. Now I am waiting for 143 hours, wasn't it a week before?
Mthw said:
I tried a different computer and a different cable (the original one is a mess and so is my win11 pc), and it worked
Click to expand...
Click to collapse
Nice.
Mthw said:
I am waiting for 143 hours, wasn't it a week before?
Click to expand...
Click to collapse
I got 167, random asf.