Kinda as the title says I cannot get adb to detect my phone adb driver is installed I've checked that in device manager I'm running wi does 10 USB debug is enabale OEM unlocking is enabled but just cannot get my phone to spear in adb any help will greatly be appriciated
Sent from my Nexus 6P using Tapatalk
nubston said:
Kinda as the title says I cannot get adb to detect my phone adb driver is installed I've checked that in device manager I'm running wi does 10 USB debug is enabale OEM unlocking is enabled but just cannot get my phone to spear in adb any help will greatly be appriciated
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
What does the CMD/Command Prompt return when you enter the command - 'adb devices' ?
Related
i want to unlock my bootloader but when i connect my nexus 7 to pc and use the command abd devices nexus 7 does not show up i tried installing this http://forum.xda-developers.com/showthread.php?t=1766220 but the install failed. Plz help as i can not unlock my bootloader
stranger97 said:
i want to unlock my bootloader but when i connect my nexus 7 to pc and use the command abd devices nexus 7 does not show up i tried installing this http://forum.xda-developers.com/showthread.php?t=1766220 but the install failed. Plz help as i can not unlock my bootloader
Click to expand...
Click to collapse
You need to enable USB debugging ...
Go to settings
Then go to about tablet
Then tap on build number aprox5 of 6 times ... You will see a toast notification the will say "you are now a developer"
Now try to what you tried to do before
Sent from my Nexus 7 using xda premium
You also will be unlocking the bootloader with fastboot commands, not adb.
ok i fixed it the usb degugging was already enabled. Just downloaded the drivers from asus website and now it is showing up in adb
Mods close the thread
Hi, I'm currently trying to revert my Nexus back to stock using the Nexus 4 Toolkit, and I don't know if I installed the drivers properly, in Windows Device Manager it says "Android Composite ADB Interface", and in the toolkit I'm not sure which one is the serial number, so I'm sending a print screen zippyshare.com/v/48728267/file.html
Am I doing everything ok?
Are you using wugfresh toolkit, or mskips toolkit? On mskips, if your drivers are set up it will display the serial # from your N4 at the top of the screen. I had an issue with wufresh toolkit recognizing my phone in adb, but worked fine in fastboot. Both toolkits will help you get back to stock.
dellortoPL said:
Hi, I'm currently trying to revert my Nexus back to stock using the Nexus 4 Toolkit, and I don't know if I installed the drivers properly, in Windows Device Manager it says "Android Composite ADB Interface", and in the toolkit I'm not sure which one is the serial number, so I'm sending a print screen zippyshare.com/v/48728267/file.html
Am I doing everything ok?
Click to expand...
Click to collapse
http://hippowise.com/revert-stock/
open adb and type fastboot devices while in fastboot. it should spit out something like a 12 or 16 digit number. if it spits that out, its connected and communicating how it should.
Check by using adb devices command,it'll show you your device as connected...
You can also confirm it by adb reboot bootloader command.It'll reboot the phone in bootloader..After that type fastboot devices while in fastboot.It will show your device there..Just check the adb devices & fastboot devices & you are good to go
Thanks for reply, I solved the problem, this thread can be closed.
I am trying to set up my adb and am having some problems. I am able to see my phone when I type adb devices, but it shows" offline". I am rooted and have twrp as my recovery but still my adb is offline.
I just updated my sdk but no lick. Anybody have any ideas?
Sent from my VS980 4G using Tapatalk 2
Connect your phone, go into device manager....do you have a G2 listed there with an exclamation next to it. If so, delete it and reconnect your phone and reinstall the drivers again
Remember that usb debug must be enabled as well.
mzimand said:
I am trying to set up my adb and am having some problems. I am able to see my phone when I type adb devices, but it shows" offline". I am rooted and have twrp as my recovery but still my adb is offline.
I just updated my sdk but no lick. Anybody have any ideas?
Sent from my VS980 4G using Tapatalk 2
Click to expand...
Click to collapse
Same issue here. I have a freshly updated version of ADB SDK installed and no yellow Exclamation mark in Device Manager. Still the command "adb devices" returns my serial number but says "offline". I'm using a Windows XP machine for this, as it seems it'd be much more difficult on my Windows 8 machine. Opinions?
I assume I won't be able to root until it reports as 'online" as well.
Ideas?
mzimand said:
I am trying to set up my adb and am having some problems. I am able to see my phone when I type adb devices, but it shows" offline". I am rooted and have twrp as my recovery but still my adb is offline.
I just updated my sdk but no lick. Anybody have any ideas?
Sent from my VS980 4G using Tapatalk 2
Click to expand...
Click to collapse
gbeardmore said:
Same issue here. I have a freshly updated version of ADB SDK installed and no yellow Exclamation mark in Device Manager. Still the command "adb devices" returns my serial number but says "offline". I'm using a Windows XP machine for this, as it seems it'd be much more difficult on my Windows 8 machine. Opinions?
I assume I won't be able to root until it reports as 'online" as well.
Ideas?
Click to expand...
Click to collapse
I don't have a G2 so my apologies for not knowing much about it but if you are on android version 4.2 or higher you need to authenticate the pc to allow USB debugging on the phone to get it to show as online.
Try disconnecting phone from PC, turn off usb debugging. Turn usb debug back on then connect to pc and send "adb devices" command, you should get this pop up screen on your phone (make sure you have screen unlocked)
If you still have issues I think it helps to be on newest version on ADB, try sending command "adb version" it should return 1.0.31
Hope this helps!
Which version of ADB are you using? I think that version 1.0.31 needs to be used for full connectivity with Android 4.2.2
Sent from my VS980 4G using Tapatalk 2
Klown80 said:
I don't have a G2 so my apologies for not knowing much about it but if you are on android version 4.2 or higher you need to authenticate the pc to allow USB debugging on the phone to get it to show as online.
Try disconnecting phone from PC, turn off usb debugging. Turn usb debug back on then connect to pc and send "adb devices" command, you should get this pop up screen on your phone (make sure you have screen unlocked)
If you still have issues I think it helps to be on newest version on ADB, try sending command "adb version" it should return 1.0.31
Hope this helps!
Click to expand...
Click to collapse
I gave up trying to update the SDK on my Win XP machine and installed it on my Windows 8 PC. Your suggestion worked after a couple of attempts. I think I've got it now, except that after my serial number it says "device" and not "online". Am I good to go? See the screenshot below...
Thanks!
gbeardmore said:
I gave up trying to update the SDK on my Win XP machine and installed it on my Windows 8 PC. Your suggestion worked after a couple of attempts. I think I've got it now, except that after my serial number it says "device" and not "online". Am I good to go? See the screenshot below...
Thanks!
Click to expand...
Click to collapse
Yes it should show "device" not "online" after the device ID number. Your adb is good to go with this device now.
Klown80 said:
Yes it should show "device" not "online" after the device ID number. Your adb is good to go with this device now.
Click to expand...
Click to collapse
Whew! I updated my SDK on my Win XP machine, must have taken 90 minutes. After running EVERY update available it still reported an older version. I'm guessing you can't run the newest version of ADB on XP. Anyway, thank you (all) for your help!
tgabaree said:
Which version of ADB are you using? I think that version 1.0.31 needs to be used for full connectivity with Android 4.2.2
Sent from my VS980 4G using Tapatalk 2
Click to expand...
Click to collapse
This was my problem. I was on version 1.0.29
I downloaded the latest ADT bundle and it updated the version to 1.0.31 and I was prompted to give the phone permission when I sent "adb devices". Now I am good to go.
Thanks
Hi all
I tried Wug's Nexus Root Toolkit and i keep on getting the trouble shooting message when ever i try to either unlock the bootloader or make a back up,
I have tried the other way using the sdk tool kit and using cmd prompts but it wont list my device when i enter adb devices.
I have enabled usb debugging and im using MDB08L
ant78 said:
Hi all
I tried Wug's Nexus Root Toolkit and i keep on getting the trouble shooting message when ever i try to either unlock the bootloader or make a back up,
I have tried the other way using the sdk tool kit and using cmd prompts but it wont list my device when i enter adb devices.
I have enabled usb debugging and im using MDB08L
Click to expand...
Click to collapse
Assuming you are on Windows, Try this tool. https://www.androidfilehost.com/?fid=24052804347803384
Also, make sure you have the option to unlock OEM bootloader under developer options turned on.
chichu_9 said:
Assuming you are on Windows, Try this tool. https://www.androidfilehost.com/?fid=24052804347803384
Also, make sure you have the option to unlock OEM bootloader under developer options turned on.
Click to expand...
Click to collapse
I'm using windows 10 and I already have oem unlock ticked .
Thanks
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
PaisanNYC said:
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
Click to expand...
Click to collapse
Most likely this problem. If you don't see the option to touch OK, restart the phone and/or replug the USB cable.
PaisanNYC said:
Could be a driver issue. Check in Device Manager and make sure the device is recognized as an ADB Composite Device. Also, when you connect your phone, and do "ADB devices", make sure to touck OK on the phone screen also
Click to expand...
Click to collapse
My ADB device in Device manager has a warning sign next to it, i click and ask windows to fix this but it says "Windows was unable to install your ADB device"
I have this on my new laptop and new desktop PC, all have usb 3 connections
Just followed this guide and fingers crossed it seems ok, http://visualgdb.com/KB/usbdebug-manual/
ADB detects my 6P but cannot detect any devices after restarting into the bootloader menu. When this kind of thing used to happen before I just removed and replaced the USB connection to fix. No more.
Mac is seeing "Nexus 6P" in System Report under USB when 6P is booted and "Android" when 6P is in bootloader menu. I am using Google Platform-Tools. I also tried with another super-clean Mac (both are running Sierra) and got same result.
Trying to flash to Oreo OPR 17 from stock 7.1.2. Device is unlocked. USB debugging is enabled. Just says "Connect USB Data Cable" in bootloader screen. I have never had trouble doing this before. Please help. It's driving me nuts.
Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.
wizardwiz said:
Two options
1. use a USB port directly on your motherboard and not one on the front of your PC.
2. Drivers issue. Remove and re-install ADB drivers.
Click to expand...
Click to collapse
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.
Calico007 said:
Thanks, but I'm using OSX on 2 laptops and it doesn't need drivers for the Nexus.
Click to expand...
Click to collapse
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Could you enter "Fastboot devices" and see what it says? Judging from your post, you are entering the wrong commands. Fastboot commands are issued when the phone is in the bootloader. ADB commands only work in recovery or when fully booted into Android.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Thank you! I knew I was doing something stupid. Much appreciated.