Hello all,
I have installed android sdk, google usb drivers etc. I am using windows Xp. My phone is upto date as per the Sony PC companion installed in windows. When I try to connect my phone in usb debugging mode to adb, its not showing up. when I give adb devices it doesn't list any devices.
when I give adb shell, it says device not found. I tried all methods like kill-server, start-server and killing adb.exe etc. after I went thru the existing threads in this forum. Nothing works !!
And the interesting thing that I could not figure out is about the device manager. After I try all methods it says drivers not installed. I try to install google usb drivers as well by browsing the folder in my android sdk . It was displaying like 'nothing found to install'
Any ideas please ??
One update.
Google usb drivers were not being installed correctly. When I update driver and browse to the Android SDK folder where the Google USB drivers present (My case .... Android SDK-> Extras-> Google -> usb_driver) it says 'nothing to update'
Then I edited android_winusb.inf file there and included my device ID (as showing up in Device manager). And it installed the drivers.
Then I opened adb again. And gave 'adb devices' and finally I could see my device listed !!!!
But still one major problem exists. That the device is getting disconnected continuously from adb and each time I would have to restart the adb and this makes it useless....
Not able to figure out why ...
Try using this: adbdriver . c o m
If it does not work try flashtool's drivers
Related
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
I believe you need the android usb drivers supplied by google to get it to connect. They can be downloaded using the sdk package manager. Also I'm not sure it will work having the Samsung drivers installed and you may have to uninstall them first.
they are installed already since i installed the whole sdk manager pack
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
ringnutz said:
install kies from Samsungs website
Sent from my myTouch 4g via Tapatalk
Click to expand...
Click to collapse
thx for answer but I already done that..any other suggestions?
tzacapaca said:
they are installed already since i installed the whole sdk manager pack
Click to expand...
Click to collapse
What drivers are showing up when you plug in the device? If it says Samsung then you don't have the android drivers installed. And I believe you can't have both installed only one or the other as only one will load when you plug in the device not both.
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
tzacapaca said:
I have the Samsung Android ADB Interface driver(although is not showing when i plug in the device) and the drivers which came with sdk manager
Click to expand...
Click to collapse
When you plug the device in, under Device Manager in Windows, there should be listed Android Composite ADB Interface under the device. If not the Google USB drivers were not installed properly.
yeah I dont think my theme is the culprit, there are many reasons why ADB wouldnt show devices. Also Heimdall>Zadig is good for drivers.
run sdk manager and install latest google drivers as well.
are you on Windows OS?
nope,not your theme its the culprit..cuz i didnt install it and i cant install it cuz of no adb connection which is required by a tool named AutoDEOTool1.0.3
I installed latest google driver via sdk manager too..
yes,on Win 7 64 bits
*pulling hair*
I didn't have my usb cable yesterday to check it out but adb actually works with the Samsung drivers. Device Manager>Android Phone>SAMSUNG Android ADB Interface. And when I type the command "adb devices" it shows up. This works both if you plug the tablet in wihtout powering it up and when its turned on so I'm not sure what your problem is. I do have Kies installed on the laptop too so yours should be working if you installed the sdk and drivers correctly.
Which Tab do you have? I have the 6210 unlocked wifi only, it could be other models work differently. Not sure if you have a locked bootloader that you can access the tab through adb.
GT P6200 European
and here is what i get on cmd
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Users\Tavi>adb devices
* daemon not running. starting it now *
* daemon started successfully *
List of devices attached
C:\Users\Tavi>adb devices
List of devices attached
C:\Users\Tavi>
EDIT:SOLVED!
Thank you all for answers
How did you solve this?
I input in cmd adb fastboot reboot and suddenly the device got the command and then recognized my tab..(pretty strange i know)
make it done
tzacapaca said:
I get this error when i try to connect my tab to adb ..do you guys have any ideas what i can do to make it to work?
I mention that i have the drivers(from Kies),usb debugging is enabled and adb works on my phone.
Click to expand...
Click to collapse
do this steps:
1) remove battery
2)insert battery
3) connect the phone via usb will turned off and leave it till usb android phone installed
4) turn ur android phone on
5) wait for full boot
6) install Motorola usb driver .zip attached down there
7)select charge only mode
8) then write the commands of tacoroot.bin
9) when all is done hit the thanx button
ADB wireless
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Unitedforlife said:
I was having the same problem, I tried to install driver, KIES, everything, tried to uninstall then reinstall in control panel, etc... to no avail.
Then I tried adb wireless... and it works. give it a try.
Click to expand...
Click to collapse
What do u mean adb wireless?
I have read many guides about setting up and using ADB, I am using an older computer with windows xp sp3. I just got my first nexus device which is a nexus 5, in device manager the phone shows up as " samsung android phone" and then "google nexus adb interface". I have tried uninstalling and then reinstalling the drivers using many different ones found on xda. I have the android sdk installed and adb seems to be working, at least when I type in "adb version" the version number comes up, but when I type "adb devices" nothing comes up as attached devices. This is really frustrating me, as I have have been trying to get this working for days now.i have already uninstalled every other android related driver using USBDeview. If anyone could please help me with this I would greatly appreciate it. I'm almost to the point go giving up! Could the problem be because I rooted the phone before getting all this setup? I ask this because when I try to update the driver in device manager it always shows driver type as clockwork mod no matter what driver I try to use
Did you enable ADB via Dev Options on the phone?
theesotericone said:
Did you enable ADB via Dev Options on the phone?
Click to expand...
Click to collapse
Do you mean USB debugging, yes I have that enabled
Go to device manager select your phone (samsung device or whatever it's showing!!) and right click and select "Update Driver Software".
On the next screen, select "Browse my computer for driver software" and set the path to : C:\Program Files (x86)\Android\android-sdk\extras\google\usb_driver"
I have used C:\Program Files (x86) because that's the place in which I have installed the SDK. Put a tick mark on "Include subfolders" and then hit Next...
Your device drivers will be installed again and adb will be working!
PS: Please make sure you have the latest android sdk and usb_driver downloaded from SDK manager!!
I am actually following the steps from the pwnieexpress guide to build my own pwn phone, in an attempt to build my own pwn phone. With no malicious intent, I'm trying to build up my pentest skills on the go.
I'm currently on Windows 7 using the android sdk. Fastboot devices manage to return my device but on step 13, my adb devices shows blank in the list of devices.
When I plugged in my wiped out nexus 5, device manager shows the Google nexus adb driver, but I cannot seem to get the adb devices to show my device.
I tried restarting the adb server and reconnecting my device to multiple USB ports but doesn't seem to work.
Any ideas? I've yet to try on a different machine, but could it be a problem with the ports?
Looking forward for any help available.
Don't slam me for asking the obvious, but do you have USB debugging ticked on in the os settings? You may have to go through an update of the android composite adb interface drivers via device manager. Just choose to browse computer, pick from a list, then run the update on each item listed. This doesn't install anything new but does seem to reset drivers. Beyond that, can't help.
Sent from my Nexus 9 using Tapatalk
Fixed. Seem to be a problem with the usb drives on my home PC, it failed to detect the device during adb devices. Weird, as fastboot seemed to work out well.
I basically installed the drivers in another machine and adb devices and adb push .. /sdcard/ worked just fine.
Thanks!
As the title says.
I'm trying to unlock the bootloader on my XZs so I can root it.
My device is listed normally when turned on w/ the command window, but in fastboot mode it disappears and when I try a command, an error comes up saying ""error: no device/emulator found". (see attached image)
As far as I'm concerned, I have all the necessary drivers, I've tried on another PC, the result is always the same.
And when I try to change the drivers (Via Device Manager>Update Driver>Browse My Computer...>Let me pick...>Have Disk...)
I get yet another error saying "The folder you specified doesn't contain a compatible software driver for your device..."
Can someone please give me a solution. This has been asked before on XDA by someone else (that thread has no replies). It seems it's always us little guys with actual problems which need solving who get little to no help at all here.
Reinstall driver again.
It doesn't work. The problem is I want to install the Google USB drivers for my Xperia phone but Windows 10 will not let me and driver signing seems to be impossible to disable (currently typing this on my laptop while it's in test mode).
1. Turn off your phone. Boot in to fastboot mode and plug the cable. After your heard the sound from the computer for new device found. Go to device manager look to usb S1 device. Reinstall driver by manual choose (do not search) from the menu with the name is Android Google. When prompt for install. Choose install anyway. After successful install driver, please check status from flashtool to make sure your device show connected in fastboot.
2. Change the usb port. Sometimes you get problem with usb port 2.0 and 3.0
Hope you can fix it asap.
Nothing by the name of 'Android Google' appears in the menu when selecting new drivers.
I clicked on 'S1boot Fastboot' under 'other devices' in Device Manager and clicked on update driver
>Browse Computer
>Let me pick
- and then there's something similar called 'Android Device' but no 'Android Google' so I click on that
- then I get three options:
Android ADB Interface Version 11.0.0.0
Android Bootloader Interface Version 11.0.0.0
Android Composite ADB Interface Version 11.0.0.0
None of them worked when I tried.
I think the solution is to have the phone on, with USB debugging enabled, connect via USB to PC, test your adb devices again, if all good, go ahead and
Rich (BB code):
adb reboot fastboot
This is because some phones use Fastbootd (notice the d..).
Hey there people,
I can't find a solution for this one, so here I am!
I want to transfer files from my computer on Windows 11 to my original Pixel, but I can't find a way to install drivers for it:
Automatic driver install does not work
Google USB drivers aren't compatible with it according to the device manager
Google drivers from the full list of Windows drivers don't work either
The phone is detected as 4 Pixels in the device manager, as well as a disk which isn't readable and returns nothing in the disk management service of Windows.
Any tip will be really greatly appreciated!
Thanks in advance to you all
BTW I tried the usual fixes: original cable, other USB port, reboot, changing the USB management setting to PTP/MTP… nothing works.
follow these instructions brother. The fix for me was to put the phone in fastboot mode before trying to install the Google drivers. You do that by issueing the command "adb.exe reboot bootloader",