Hey guys
I attempted to use ADB on my Nexus today to now avail. I have updated my drivers and still cannot find a device when opening an ADB Shell on my Windows 7 64 bit laptop.
The weird issue is I can do ADB functions through Wug's Nexus Root Tool Kit. It even shows my device and passes the driver test with flying colors.
What am I missing?
Thanks in advance!
Run terminal as administrator?
Sent from my i9250
Have you checked
Code:
adb devices
?
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thanks
FNM
Related
I'm having a problem that is affecting two different computers, both of them gives me a 'adb device not found' message and it won't list my G2 when I typed in 'adb devices', the only difference between them is that in my laptop it gives me a message that it couldn't successfully install 'ADB'(Windows 7 Home 64 Bit) while my older Windows XP SP3 desktop gives me no such message.
Before replying, please note that I have Checked USB debugging and have done everything in the ADB for dummies thread, which includes the adding the tools part to Path and I have reinstalled my drivers more than five times (with and without USBDeview), each time with a different method. I am not mounting my SD card. I have also tried the PDAnet method. I have modified the android_winusb.inf file and reinstalled it. Tried uninstalling my USB Root Hub's as suggested by another. I have updated my USB Driver in SDK to rev 4. There aren't any yellow checkmarks in my Device Manager, however I have noticed that I only have 'Android Phone' and the subcategory 'Android Composite ADB Interface', I've heard that I should see another category like 'ADB Device Driver'. I have tried to fix this problem for five hours to root my G2, any help would be appreciated very much.
Where did you get your drivers from ? In the guide at http://forum.xda-developers.com/showthread.php?t=865685 I suggest getting them from the HTC Sync software, not the SDK.
I walked a guy with Win 7 through this the other day, and it worked fine for him.
I know it sounds like a stupid question but is the adb.exe file in your tools folder? If not, try running an advance search and only in the titles search for "drivers". You should only get about 10 returns. The top one should have some files attached named tools. Download them and extract the files to your tools folder. Then try running the adb devices again, yesterday I had to do that cuz for some reason adb.exe wasn't there.
I second getting the drivers from HTC Sync and remember the desire z is the same a G2 so run the seach for desire z for htc sync.
Sent from my HTC Vision using XDA App
ddgarcia05 said:
Then try running the adb devices again, yesterday I had to do that cuz for some reason adb.exe wasn't there.
Click to expand...
Click to collapse
adb has been taken out of the latest version of the SDK "Starter" package (the 2.3 one). It used to be there in the 2.2 version. So now you have to run SDK Manager to install the platform-tools add-on, then you get adb. This is all in my updated adb guide
ddgarcia05 - I didn't have adb in my tools folder, however I don't believe that you need adb.exe in that folder, just in the 'platform-tools' folder or in the system-32 fodler. Thanks for trying.
steviewevie - Thank you so much! I found your adb for noobs thread and it seems that installing HTC Sync after uninstalling my previous drivers via USBDeview worked like a charm. I also didn't see that you had to add 'platform-tools' in the Path in the various other threads, so I did that too. +1 Thanks to your helpful thread!
what does our phone have to be in to use adb? ive never used it before but want to to obtain root without unlocking the bootloader and losing my info. is it rebooted in adx mode? just turned on normally? off?
thanks!
You cannot root without unlocking the bootloader! To access adb you need to be in OS and have debugging enabled under Developer options in the settings.
RTContent said:
You cannot root without unlocking the bootloader! To access adb you need to be in OS and have debugging enabled under Developer options in the settings.
Click to expand...
Click to collapse
i was directed here
http://forum.xda-developers.com/showpost.php?p=23290676&postcount=1
for a workaround to rooting without unlocking the bootloader
Wow, I must have missed that news. Apologies! Have you tried replying in that thread then?
RTContent said:
Wow, I must have missed that news. Apologies! Have you tried replying in that thread then?
Click to expand...
Click to collapse
you already answered my question to be in the OS with debugging enabled! thanks!
You could re-lock the bootloader though if you ever wish to unroot your phone...
my computer wont allow me to recognize my gnexus using adb. im following these steps - http://droidmodderx.com/galaxynexus/how-to-set-up-the-sdk-for-galaxy-nexus
and i know i have already installed the dirvers previously, but when i use the cmd prompt, my computer does not find my device whatsovever. tried uninstalling it from device manager, but it just reinstalled it when i plugged it in with the MTP drivers already on my computer.
does anyone have any suggestions? i did remember to leave usb debugging on.
thanks!
after rebooting, i tried this in cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Josh Bucher>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
************** offline
C:\Users\Josh Bucher>adb devices
List of devices attached
C:\Users\Josh Bucher>
so it looks like it detected it as offline, then it doesnt. any thoughts? i **ed my phones serial #
ive managed to get the toolkit to install fastboot drivers, but ADB drivers still are not installed and adb does not recognize my phone. fastboot does see it but adb doesnt. ive uninstalled all the drivers and tried the nexus toolkit, pdanet and manual installation but for some reason, i cannot get it to install adb drivers or even recognize that it is an option. does anyone have any suggestions?
joshtb86 said:
ive managed to get the toolkit to install fastboot drivers, but ADB drivers still are not installed and adb does not recognize my phone. fastboot does see it but adb doesnt. ive uninstalled all the drivers and tried the nexus toolkit, pdanet and manual installation but for some reason, i cannot get it to install adb drivers or even recognize that it is an option. does anyone have any suggestions?
Click to expand...
Click to collapse
So there's nothing listed if you input :
adb devices
You are connected via usb with debugging enabled?
Edit: could you also open up device manager in windows and have a look if the device is listed
Sent from my Galaxy Nexus using Tapatalk
RTContent said:
So there's nothing listed if you input :
adb devices
You are connected via usb with debugging enabled?
Edit: could you also open up device manager in windows and have a look if the device is listed
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
usb is enabled.
nothing is listed under ADB, but there is my serial number listed under fastboot. I uninstalled all drivers the toolkit and the SDK. I am going to try the toolkit again now that everything is been uninstalled. The device will be listed in Windows but usually without the ADB driver listed, however the fastboot driver is listed.
now that I tried using the toolkit,
I still had the same problem with no ADB but fastboot was the listed. Then I went to uninstall the drivers through the toolkit and I got an error message saying that they remove failed three times and that no device was removed. However the device still exists under portable devices in the device manager. I am going to uninstall the toolkit after removing the drivers and remove all the drivers from the device manager and then try using just the SDK to route the phone.
after using the toolkit, I am now getting Samsung ADB interface driver installed on my computer. However the toolkit cannot access or realize that ADB is connecting to my phone. I do have USB debuggingenabled. I might try using the SDK to manuallyto connect to it.
fixed the problem. i plugged my phone in directly to the computer instead of through a usb splitter. got it rooted via this post
http://androidforums.com/verizon-ga...oot-un-root-without-unlocking-bootloader.html
thanks for everyoines help! everyone is tahnked!
joshtb86 said:
fixed the problem. i plugged my phone in directly to the computer instead of through a usb splitter. got it rooted via this post
http://androidforums.com/verizon-ga...oot-un-root-without-unlocking-bootloader.html
Glad you got it fixed. If I knew I could have told you the usb hub would have been the problem (they always are)
thanks for everyoines help! everyone is tahnked!
Click to expand...
Click to collapse
Sent from my Galaxy Nexus using Tapatalk
I have got the drivers installed it shows properly. Gotten to the point of opening adb shell and pulling my device I'd and no device is found. My ini file shows the right I'd. I habe spent 3 hours going through google and pulling info and trying this and that and still no device is found. When I try to pull the device list it states list showing with no device under it in adb shell. Any ideas would be helpful running wimdows 8 64 bit. Adb is listed under device manager all seems well
Sent from my SAMSUNG-SGH-I717 using xda premium
You probably will be ask to move this thread to Q&A,Help &Troubleshooting section. The thread http://forum.xda-developers.com/showthread.php?t=2244094 should have your answer. I think you don't have the driver setup properly. Did you enabled usb debugging on your kindle? If so it should work, I don't remember the stock process but when you connect to the pc, my CM10.1 kindle will ask to allow usb debugging and when I press ok, adb will recognize the device on the pc.
Korvan30 said:
I have got the drivers installed it shows properly. Gotten to the point of opening adb shell and pulling my device I'd and no device is found. My ini file shows the right I'd. I habe spent 3 hours going through google and pulling info and trying this and that and still no device is found. When I try to pull the device list it states list showing with no device under it in adb shell. Any ideas would be helpful running wimdows 8 64 bit. Adb is listed under device manager all seems well
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
Do you have the Android SDK installed?
If yes, is it the latest version?
If yes, open the CMD prompt in C:\Android\system\bin or replace "C:" with whatever drive you installed it on & run it from there, where adb resides. It is probably a PATH issue.
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Appsdroid said:
Hi Guys
Do a require a specific driver for the new 4.2.2 system. I have updated my phone to run Cyanogenmod 10.1 and had some issues originally getting adb etc to identify the phone. I have since got past this and now get an unauthorised error in adb. This is normal the issue im having is that my phone does not prompt me when I connect it to my PC. I should be getting a whitelist prompt to confirm I authorise the Pc to run ADB commands.
Has anyone else had this rather than the expected whitelist prompt im getting the little android bloke asking do I want to copy files via usb. Im just trying to work out what I need to do to get my phone to prompt me when I connect via ADB. I have already enabled ROOT access to Apps and ADB, Enabled USB debugging etc
Any help would be appreciated I have tried a number of drivers but only ever get asked to copy file via usb.
Click to expand...
Click to collapse
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Wilks3y said:
Do you have HTC Sync Manager?
Also, in Device manager does your Drivers have Errors (Yellow Triangle)?
Click to expand...
Click to collapse
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Appsdroid said:
Hi Mate
I have tried with HTC Sync on and again after uninstalling it both result in the same issue usb prompt rather than ADB fingerprint prompt. No in Device Manager both of the connections for the device identify and install correctly. One with the phone and another stating something like Android Interface device not on my PC at the mo to confirm the exact name but its something like
My HTC
Android Interface Device or possibly android ADB interface
Click to expand...
Click to collapse
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Wilks3y said:
Hmm Very strange.
Try:
http://forum.xda-developers.com/showthread.php?t=2217396
Or if not try hasoons Root Toolkit, im sure that installs some drivers too. Hasoons got my ADB working.
Finally, to find ADB device, are you opening command prompt in Platform-tools folder?
Click to expand...
Click to collapse
Nice one cheers mate will try these drivers when I get home later. I was originally using Hasoons toolkit which is what flashed the recovery and new rom but once I updated to 4.2.2 the toolkit stopped. It was coming up as device offline. I have managed to get it working by overwritting the old ADB and fastboot files with the new ones for 4.2.2. The ones the toolkit comes with is 4.1 so was erroring as it didnt know to carry out the fingerprint check.
Yes mate I have tried various methods I have accessed the android\android-sdk\platform-tools folder and run ADB from there this identifies the phone but states its not authorised. I tried using the toolkit with the new ADB and fastboot but get the same.
Im just missing the ADB prompt on my phone for usb debugging just cant for the life of me identify why im getting the copy files from usb prompt rather than the adb fingerprint prompt. Im sure its drivers so am hopeful the ones on the link will fix it. Fingers crossed
I was having issues with adb not finding my device. These drivers worked for me...
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
Nice one mate will try these ones when I get in to on way home now hopeful one of the driver links sorts out the prompt for me will update later thanks guys
Sent from my HTC One X using xda app-developers app
Cheers All removed all drivers for htc one x then downloaded the 4.2 versions from the link
http://forum.xda-developers.com/show....php?t=2217396
once reinstalled adb gave unauthorised error again but then put the prompt up on the phone. So possible the 4.2 contains the info for requesting permission as i havent changed anything other than the drivers adb and fastboot have been the same since i started. Anyway cheers all
confusion about installing driver
crshd said:
I was having issues with adb not finding my device. These drivers worked for me...
Click to expand...
Click to collapse
bro i download your driver but how to install it. my htc one x just start in fastboot mode. i want to unlock bootloader but without adb i am helpless
If you have Windows 7,8,8.1 just enable automatic update and let windows install correct drivers
Sent from my HTC One X using Tapatalk 2
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Mambobuzzz said:
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Click to expand...
Click to collapse
This is a problem related to Windows 10 that uses the wrong driver.
Somewhere I have found a guide to manually choose the correct one, but at the moment I don't remember where... googling you will find instructions
Mambobuzzz said:
Hi there,
I'm trying to install TWRP. But I can't do any fastboot command. ADB works. Device isn't recognized in system and with "fastboot devices" nothing shows up. :/
I've tryed many drivers but nothing works.
I'm using Win 10 x64. Does anyone have a suitable way to get it working?
Thanks!
Mambobuzzz
Click to expand...
Click to collapse
This is not the Q&A section. Please post your questions there, according to the forum rules. Can a moderator please move this? Thanks.
Monfro said:
This is a problem related to Windows 10 that uses the wrong driver.
Somewhere I have found a guide to manually choose the correct one, but at the moment I don't remember where... googling you will find instructions
Click to expand...
Click to collapse
I've googled it. Tried many. Event tried to boot Windows without driver signature. Didn't work. :/
michie said:
This is not the Q&A section. Please post your questions there, according to the forum rules. Can a moderator please move this? Thanks.
Click to expand...
Click to collapse
Oh sorry.
Does someone have an idea?
This might come a year too late, but in case someone else runs into the same problem (like myself), you can solve it by installing the latest (signed) ADB drivers with this Tool, then rebooting the tablet to fastboot mode and run the tool again. This still doesn't install the correct fastboot drivers, but it should now be listed as "ADB Interface" -> "Unknown Device" in the device manager, and if you right click and choose "Update driver" -> "Browse my computer for driver software", you should see a driver called "Fastboot interface (Google USB ID)", that installs and works correctly for the Pixel C.
@Mambobuzzz
One option you have and it's been updated this month too, is you could try installing and using tiny adb & fastboot from here: https://forum.xda-developers.com/t/tool-windows-tiny-adb-fastboot-august-2021.3944288/
I can't stand Windows for a few reasons! Make a live USB and try a Linux distro! You will never have this problem again and I guarantee you won't miss Windows.
Edit added:
Reasons why this is happening:
Bad connection somewhere.. The USB connection you are plugging in to on your PC could be messed up, the USB cord could be messed up, or where your type c plugs in to your device is messed up.... Oooorrrrr it's driver issue. And knowing Windows I betcha it's a driver issue. When you plug your tablet in are you enabling USB debugging and developer options and changing the "default USB configuration" from "Charging" to "File tansfer ?" And when you do those things are you watching the table REALLY CLOSELY for the little box that pops up for 5 seconds that you MUST put a checkmark in otherwise adb and fastboot will not work? Reboot a few times on your PC and update the drivers in Windows Device manager.. I remember once I had to reboot 3-4 times to finally get mine working. When you type adb --version then push enter in terminal and fastboot --version push enter what does it say?