Related
I Tried guides that try to solve this from everywhere, Including here,
I used latest version of the android usb-drivers that comes with the latest Android SDK (downloaded directly from google with the SDK download GUI thinggy).
Tried to uninstall all usb roots,
Tried force removal of driver using external app and re-installations
Tried different drivers from multiple locations,
And still, whatever I try - there is notihng on the "adb devices" list
"List of devices attached"
<CR>
<CR>
C:\.......>
Everything shows up okay, on first run of the adb the 'whatever' service starts and everything is fine
Device DOES appear properly on device manager "Android Composite ADB Interface".
Windows DOES the pnp beep whenever I check or uncheck the "Debugging mode"
This hapnned both on STOCK ROM (first or second software version of the phone released) and on latest Cyanogen 5.0.6
One thing I did noticed, "Android ADB Device" Either appear under "Android" type (usb debugging on) or under USB Controllers (When usb debugging is off).
Ho, I did not mentioned the phone, I'm talking about Nexus One.
Thanks for any help.
Amm, any ideas?
Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.
I take it your on Windows, so I might not be much help as I use Linux strictly but try to run the command prompt as Administrator (right click > run as I think) and then
adb kill-server
adb start-server
Not sure if that will help but I know in Linux you must start the ADB server as root in order to see the attached devices, so I assume in Windows you must start it as Administrator.
I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps
Beackman said:
Try using a program named USBDEVIEW, remove the android driver and plug the phone to your PC again and wait to reinstal the drivers.
Click to expand...
Click to collapse
I Ment just that when I said "Tried force removal of driver using external app and re-installations"
drew630 said:
adb kill-server
adb start-server
Click to expand...
Click to collapse
Tried that just now, on windows I'm in the Administrators group, that should work... It doesn't :/
bmxrideher said:
I ran into a similar issue with my sapphire. Turns out it was as simple as me having my tethering app on. Once I turned it off (pda net), it worked like a charm. Hope this helps
Click to expand...
Click to collapse
Good idea, but still no salvation :/
Try uninstalling the mass storage driver for the phone, this worked for me
Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed
Synestr said:
Oh Ehm Gee!!!!
That was perfect! I did that and I got what I needed. Now I'm off to root that som'bish.
+1 to you sir, +1 indeed
Click to expand...
Click to collapse
No problem, lol, almost a month later. Glad I could help.
Naemion said:
No problem, lol, almost a month later. Glad I could help.
Click to expand...
Click to collapse
Hells to the yea, I now has root and rom and I am a happy boy!
Thanks again
hmm >.< nothing is working for me this laptop is not detecting my (Nexus S) device in ADB
windows sees it fine, drivers are installed (for normal mode and ADB mode), mass storage works,
but ADB Devices list shows up empty
2 other phone works just fine (SGS & XT720)
Update: went to another computer and it shows up properly.... (you just gotta "luv" windows )
Try installing htc sense from htc website even if running vanilla. It will install the driver properly. Then un-install sense and keep drivers. It's the only thing that worked for me.
Sent from my HTC Vision using XDA App
Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk
Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000
METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.
I'm going to test in my desktop this weekend to check if it works with it.
I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.
I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
I got my i9000 recognized using the latest drives from the Google sdk
That‘s great
http://ics.samsung-updates.com/addons/usb_driver.zip
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA
oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)
USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK
IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me
The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !
these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.
I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
plug the phone, open a terminal as administrator/root and type
adb stop-server
adb start-server
adb devices
the last command must return your device name-id
If not there is smth wrong with your installation
The device didn't show up do you know what I could have done wrong? Do I have to turn on mass storage? Could it have something to do with my drivers, can't remember installing any... And in the device manager I see four android with a orange triangle with am exclamation mark inside.
Sent from my U8800 using Tapatalk 2
theminikiller said:
The device didn't show up do you know what I could have done wrong? Do I have to turn on mass storage? Could it have something to do with my drivers, can't remember installing any... And in the device manager I see four android with a orange triangle with am exclamation mark inside.
Sent from my U8800 using Tapatalk 2
Click to expand...
Click to collapse
No you don't need to enable mass storage, but you need to enable USB debugging from dev settings from the device. Use these drivers
https://www.dropbox.com/s/ryn7l7z0nfc842g/u8800_pc_drivers.zip
emmm... feeling kinda stupid right now... but how do i install the drivers? xD
theminikiller said:
emmm... feeling kinda stupid right now... but how do i install the drivers? xD
Click to expand...
Click to collapse
You have to install them manually from device manager.
Sent from my U8800
After i choose the folder with the drivers i only get a message saying it didnt find any drivers. Do you know why i cant install them?
Is it the same drivers when I'm using aurora ics as gingerbread roms?
Sent from my U8800 using Tapatalk 2
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
kross666 said:
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
Click to expand...
Click to collapse
Thanks alot! That worked perfectly, now i can start using adb on my phone xD
btw i have a question for adb... what does reboot to download mode mean? is that pink screen?
theminikiller said:
Thanks alot! That worked perfectly, now i can start using adb on my phone xD
btw i have a question for adb... what does reboot to download mode mean? is that pink screen?
Click to expand...
Click to collapse
I think its safe mode
Sent from my Impulse 4g running vPure Professional CM7.
kross666 said:
I had the same issue. This tutorial worked for me: http://goo.gl/OS3Vi
Hope it helps
Click to expand...
Click to collapse
Thank you the instructions in the link provided worked for me. I am able to see my listed by adb device command...
help
i have been trying to root my acer iconia tablet A100 for a week now, i ve tried and followed a dozen of ways. this is were it has brought me,
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
please help me, what did i do wrong
thanks in advanced
jakk181571 said:
i have been trying to root my acer iconia tablet A100 for a week now, i ve tried and followed a dozen of ways. this is were it has brought me,
Device connected. Preparation for executing of the main script.
mkdir failed for /data/local/tools, Permission denied
push: tools/su -> /data/local/tools/su
failed to copy 'tools/su' to '/data/local/tools/su': No such file or directory
Unable to chmod /data/local/tools/*: No such file or directory
remote object '/data/local/tools/mempodroid' does not exist
The file "mempodroid" isn't created!
-
Not getting root!
-
Error!
-
Press any key.
please help me, what did i do wrong
thanks in advanced
Click to expand...
Click to collapse
this is not the forum for ur device..
then please tell then where is the correct forum.
i only when to this one because google brought me here, and it was on adb, which is what i am have trouble with.
Re: Adb - device not found (I had same problem) Fixed
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
I had the same issue updating my Nexus 7 in adb download mode device not found. You will also notice in system setting device driver is showing an error. You can download Adb driver installer which should detect any missing driver and fix the issue.
It worked for me straight away otherwise I had no way round getting to solve the problem. Fheww!! hope it works for you
Many Thanks.
adbdriver.com/downloads
---------- Post added at 05:55 PM ---------- Previous post was at 05:43 PM ----------
You may be missing the device driver when switching to USB Debugging mode using ADB Command prompt device not found.
Please download and intsall adb driver installer. It found my device and installed missing driver straight away problem fixed now I dont seem to have any issue.
adbdriver.com/downloads/
Glory be to Almighty God. Thank you!!
theminikiller said:
Hi, im trying to set up adb on my windows 7 computer and i have installed the update packages but when i try a command to my phone i get an error saying "error: device not found" even tho i have it connected via usb and i have debugging on. How can i fix it?
Click to expand...
Click to collapse
same problem...
For some reason when i connect the phone the the computer, it wont show up MTP.. but for PTP it works.. When its connected the small window pops up alerting me the "nexus 4" was connected but thats it, the drive wont show up.
I think getting rid of the adb drivers I used so it doesnt show up as "android adb inferface" will solve the issue... but whenever I uninstall the drivers from device manager and delete
the usb drivers folder.. it still installs them right back when I connect the usb!
*edit* it detects on my dads computer just fine and MTP works.. i think it has to do with the adb drivers i installed.. wish i knew how to uninstall them for good so windows wouldnt automatically install them again even with deleting the drivers folder off my harddisk
Bump. Tried everything to no luck
Sent from my Nexus 4 using xda premium
Did you find a solution to this? I am having the same problem. The original drivers that installed worked just fine over MTP but not adb. Now, abd works but my Nexus wont show up as an MTP device.
jonesy420 said:
Did you find a solution to this? I am having the same problem. The original drivers that installed worked just fine over MTP but not adb. Now, abd works but my Nexus wont show up as an MTP device.
Click to expand...
Click to collapse
Try these drivers, http://forum.xda-developers.com/showthread.php?t=1514942 i have no problems with them.
It works!! Thanks a lot! I was going crazy trying to figure out what was wrong.
Hi guys,
I'm currently experiencing a probem with my Nexus 4. No matter what OS I use (Linux or Windows) or what driver I use adb keep saying that my device is offline. As I saw elsewhere I tried an other usb cable or port but nothing seemed to work. Does anyone got an idea for this ? This thing is gonna drive me crazy !
Thanks
Task Manager, then kill the ADB one. Then open ADB, adb devices again.
Otherwise, did you check the debugging =.= Or reinstall the driver manually (not by WIndows).
I have had a problem with this and it has been unsolved as of yet, but I may be able to help you. In the SDK Manager, there is an extras area, if you don't have the drivers from there I have found you may have trouble. It could be something else, but this should be a sufficient launchpad.
Sent from my ADR6425LVW on GrayTheWolf's CM10 build.
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
saintjimmy said:
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
Click to expand...
Click to collapse
Are you on 4.2.2 they changed somethings with the update. Have you updated your SDK?
Try installing PDAnet drivers. They will make it work.
xdaOSdev.team said:
Try installing PDAnet drivers. They will make it work.
Click to expand...
Click to collapse
I can verify this, it solved the problem I have been having for a few months in Linux OSes.
Sent from my ADR6425LVW on GrayTheWolf's CM10 build.
saintjimmy said:
Thanks to you both, but I mainly use Ubuntu and not Windows. I've tried killing and restarting adb a lot of times.
Click to expand...
Click to collapse
Guys, he said he's using ubuntu lol there are no usb drivers to install
try this...it sounds like your adb may be out of date. This will also reinstall fastboot, unless you leave 'android-tools-fastboot' off the last command
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
btw, if you haven't already done so, you should get the full sdk installed. It's better to have it and not need it than to not have it and realize after three hours of pulling your hair out you should have had it all along lol (I've done it, so I speak from experience)
Thanks @hp420 but sadly the device is still offline. I'm just realizing it now but I didn't have the warning message about the association with the computer that I usually have when activating USB debugging with 4.2.2
Load latest SDK version. Load driver inf fix. Search forum. Known problem. Easy fix.
sent from my nexus 4; cat on lap, beer in hand
This is due to the new whitelist for adb in 4.2.2.
Some of these steps may be unnecessary, but I know this works (I've had to do it a few times to all my devices that have been upgraded to 4.2.2).
You need the adb from the latest SDK.
Untick USB Debugging.
Reboot the phone.
Tick USB Debugging.
Reboot the phone.
On your PC, make sure you add the new SDK/tools to the PATH then do adb kill-server; adb start-server
Unlock your phone.
Plug it in to your PC.
A message on your phone will appear asking to add the PC to the whitelist.
Accept this and your phone should appear when you do an adb devices
No need for driver i'm running linux...
Sent from my Nexus 4 using xda app-developers app
Nark.GA60 said:
This is due to the new whitelist for adb in 4.2.2.
Some of these steps may be unnecessary, but I know this works (I've had to do it a few times to all my devices that have been upgraded to 4.2.2).
You need the adb from the latest SDK.
Untick USB Debugging.
Reboot the phone.
Tick USB Debugging.
Reboot the phone.
On your PC, make sure you add the new SDK/tools to the PATH then do adb kill-server; adb start-server
Unlock your phone.
Plug it in to your PC.
A message on your phone will appear asking to add the PC to the whitelist.
Accept this and your phone should appear when you do an adb devices
Click to expand...
Click to collapse
Tanks fort that answer I'll try it as soon as possible !
Sent from my Nexus 4 using xda app-developers app
Try typing
adb kill server
adb start-server
Sent from my Nexus 4 using Tapatalk 2
scream4cheese said:
Try typing
adb kill server
adb start-server
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
saintjimmy said:
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
try a live cd of ubuntu and see what happens. that will at least narrow it down to whether it's your ubuntu installation or your phone. if it still won't mount in the live cd we can assume it's an issue with your phone. from there you can run a nandroid backup and reflash the factory images to see if that fixes the issue. if it does, you can try a fresh install of the rom you're using. if it still works, then restore all your apps/app data
if it's your ubuntu installation there are other avenues you can try.
saintjimmy said:
Already did that countless times...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
You can try uninstalling SDK and perform a fresh install. Move your platform tools to a more convenient locations and change the path under windows properties.
I don't know if you tried this already but..
Have you tried uninstalling and reinstalling the drivers for phone?
switch to another USB port? A different usb cable?
scream4cheese said:
You can try uninstalling SDK and perform a fresh install. Move your platform tools to a more convenient locations and change the path under windows properties.
I don't know if you tried this already but..
Have you tried uninstalling and reinstalling the drivers for phone?
switch to another USB port? A different usb cable?
Click to expand...
Click to collapse
UBUNTU!!!!!
lol
hp420 said:
UBUNTU!!!!!
lol
Click to expand...
Click to collapse
Or try using Ubuntu. LOL.
But dual-booting to another OS is a hassle.(?) If ubuntu is not your daily driver, you're gonna have to keep rebooting in between OSs.
scream4cheese said:
Or try using Ubuntu. LOL.
But dual-booting to another OS is a hassle.(?) If ubuntu is not your daily driver, you're gonna have to keep rebooting in between OSs.
Click to expand...
Click to collapse
Thann you all for your answers! I use linux mint which is my main OS. I manage to resolve my problem in a weird way: first I push a CWM recovery with fastboot and then I flash the ZIP from SuperSu ! From now USB debugging is working properly and I get the usual warning !
What I would like to know now is why ? Does the SuperSU ZIP reset something ?
Sent from my Nexus 4 using xda app-developers app