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!
Related
Now, I have figured out that I have to actually be in the android-sdk-windows\tools folder for ADB to work, but when I type adb devices it just says List of devices attached but doesn't list my Evo.
I have USB debugging on.
An Android ADB/rooting noob guide would be very helpful right now.
criccio said:
Now, I have figured out that I have to actually be in the android-sdk-windows\tools folder for ADB to work, but when I type adb devices it just says List of devices attached but doesn't list my Evo.
I have USB debugging on.
An Android ADB/rooting noob guide would be very helpful right now.
Click to expand...
Click to collapse
Does it have anything there when you type adb devices? Should come up with a HT and some numbers after it....being your device, EVO.
Actually, there is a step by step Guide for EVO root, and a ADB Guide for Beginners
Your device isn't being recoginized check the driver if u r in windows.
Ok, I managed to figure out the cryptic SDK installer and download the USB driver package to android-sdk-windows\usb_driver. I used Device Manager to install the driver and I pointed it to that folder and I get the "Windows was unable to install your ADB".
Are you already Rooted? as for the Drivers, when I plugged in my EVO via USB, it installed drivers...I also copied the HTC Sync that came on the SDCard w/phone, onto my pc. But I did not have to do anything further.
Can I ask what you are trying to do in adb? and is this for the EVO?
use the cd command to make sure you are in the android sdk tools folder
if you want adb to work
what i do
1. use the cd command to go to the directory where my sdk is located which for example is c:\androidsdk\tools
2. there you go
3. if you want shell make sure your device is connected
"adb shell"
and have htc sync from evo's sd card installed
http://myevo4g.net/main/?p=83
Sent from my HTC EVO
download htc sync and install that. i was having the same problems and apparently the usb drivers that get installed with that app are the ones that worked like a charm for me.
Try
Code:
./adb devices
Instead.
--> try" adb start-server "
If your HTC dont show up, it's usually because the ADB server isnt running. Hope this helps =]
I've rooted a hero before and felt pretty confident with android sdk, usb drivers, etc. After spending an hour trying to get it to work on my win 7 64 bit system, I thought it might save someone some time if I posted what finally allowed me to get adb to work.
My problem was the computer wouldn't recognize the EVO as a device. Even after I installed the usb drivers through android sdk. I tried to manually update them through device manager (pointing it to the usb drivers directory) and still no luck.
As the video linked above showed, the missing piece for me was installing htc sync. use the version that comes on the phone. So connect the phone to the computer, mount it as a drive from the phone menu, then copy over the htc sync directory to your computer, then run it. The version on my phone was 2.031. THEN the computer will recognize it with usb debugging turned on and I'm able to adb to the phone through the command prompt.
Hope that helps someone. Sean
Originally Posted by nicbennett
*Daemon not running, starting it now on port 5037*(this does successfully start the adb.exe process)
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon*
Click to expand...
Click to collapse
Originally Posted by snovvman
W7/64.
ADB worked for me for months. I used it regularly. The last thing I did was *trying* to use Wireless ADB Widget and issueing ADB TCPIP command. I have made no changes to the system.
The error occurs when no device device connected. Same error when device IS connected.
-Downloaded ADB/SDK again to a different directory, same error
-Updated USB driver and SDK components, same error
-Disabled all firewall/anti-malware/anti-virus, same error
-Rebooted multiple times, same error off boot
-Port 5037 is not bound by any app or process
-ADB, upon failed load, is not listed in Taskmgr, nothing to kill
-Deleted temp files
-Issued at prompt: ADB Disconnect, ADB USB, ADB devices: All return same error as above
-Issued at prompt: ADB kill-server, only prompt returns
Read lots of posts on the web, nothing helps.
I am really interested in a solution and would like to understand what is causing the problem. If in fact it is a configuration issue, where is the ADB config file?
Thanks.
Edit: I am running the command prompt as an administrator.
Click to expand...
Click to collapse
I originally added my post to this thread in the Nook forum. I don't think there is enough expertise in that forum to help with this problem.
The bottom line is that ADB no longer works and I can't figure out why (see quoted text above). I would imagine that someone here would have an answer for this. Please help!
Thanks.
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
DGreen1 said:
Only thing I would try it open Task Manager and go to processes and close anything that is adb or adb.exe.
Click to expand...
Click to collapse
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
snovvman said:
In this case, ADB never starts. It does not work even after a fresh reboot. It is not found in Taskmgr nor Process Explorer.
Click to expand...
Click to collapse
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
My problem was Windows
snovvman said:
The error occurs when no device device connected. Same error when device IS connected.
. . .
I am really interested in a solution and would like to understand what is causing the problem.
Click to expand...
Click to collapse
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Yellowcard8992 said:
Is what he meant was to kill any process that is using adb. This is not only a process that is Android related etc. My buddy had your exact same problem because he had his external hd connected to his computer before trying to run adb. Restarting and killing processes that were using adb on his computer did the trick. Hope this helps!
Click to expand...
Click to collapse
Interesting, but I haven't been able to find any other service that is bound to adb and I have no other USB devices connected. Thanks for chiming in though.
tgi007 said:
In my case, the problem was Windows Vista. From day one, Windows refused to successfully install the USB drivers for the EVO (with the very helpful diagnostic message: "Windows encountered an error installing..."). I have never been able to use adb, and this meant that all the rooting (and update/upgrade) guides that required adb had to be adapted to getting the file(s) onto the SD card, and then using Terminal Emulator (or similar app) to get the job done.
I've just completed a disk-wipe-and-reinstall of Windows on my laptop, and hope to find the time next week to install all the SDK goodies and make sure that the USB subsystem recognizes my EVO. I'm fed up with not being able to use adb, and that, along with Windows Update failing to install over a dozen security patches, finally pushed me over the edge into a re-install. Auuugh! The pain!
Click to expand...
Click to collapse
For me, I have been able to get two Vista and one Windows 7 computer to work with ADB and HTC drivers the first time. I also have an Epic, and the Samsung drivers installed fine as well (even though they are known to have issues).
Unfortunately, ADB just "broke" one day.
I keep thinking that the Evo community has enough brains and knowledge to sort this out quickly...
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
lovethyEVO said:
Have you updated the sdk recently?
The updated sdk moves the adb files from the tools folder to another folder called platform-tools.
I have adb working properly on both my vista machine and my ubuntu machine hosted on my vista machine.
If you have installed htc sync before uninstall it and the htc driver installer.
Redownload htc sync and the adb files (adb.exe and adbwinapi.dll is all you need). Since adb was working correctly before I'm assuming your java is installed correctly as well.
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
When you've rebooted again enable usb debugging on your device and connect it to your pc choosing charge only.
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
If the drivers install correctly you should be able to run adb from the directory your two files are in (desktop for example).
If you want, send me a pm with your gtalk username and I can help you troubleshoot it.
Click to expand...
Click to collapse
Thanks for replying. I had already updated ADB (in platform-tools) before started having this problem. I had also uninstalled HTC sync (reboot, launch ADB w/o HTC sync, same problem) and reinstalled HTC sync, same problem. I updated Java JVM, no change. I then re-downloaded the SDK to a different directory, no dice.
I usually open a command prompt "as Administrator" and run ADB from the directory. Even with a device disconnected, I get the same error. I test this way because if I issued "ADB devices" and it returns nothing, I know it's working. It appears that ADB doesn't even start to the point to poll for devices.
I have, just for laughs, connected my device (USB debugging/charge only), but no joy.
I won't have much time to poke around more until the weekend. If I don't come up with anything, I will take you up on the gtalk. Thanks again.
Windows Vista just makes it all that much harder to fix things...
lovethyEVO said:
If you have installed htc sync before uninstall it and the htc driver installer.
. . .
Reinstall htc sync. When that finishes I suggest a reboot. When you've rebooted uninstall htc sync but leave the htc driver installer. Reboot again.
. . .
This should hopefully reinstall the usb drivers correctly. On vista it installs as adb device or something along those lines.
Click to expand...
Click to collapse
In my case, I tried all these things and many more (lived with this problem since first getting my EVO on release date in June). No dice, as Windows Vista, once it installs a device driver, doesn't give the user the option to uninstall it (by Microsoft's expressly-stated intent -- a design decision I vehemently disagree with). At least the user could repair such problems in prior versions of Windows by simply uninstalling a device, choosing "yes" to the "remove driver files from the disk" question, and (after the obligatory and ubiquitous Windows reboot) re-connect the USB device. That would start fresh with that device's driver.
I never invested the time to learn how the USB subsystem registers devices and their drivers (in Windows Vista) in order to determine how to manually remove a driver from the Windows Registry adequately that it would treat the device as "new hardware detected" upon the next connection.
Once Windows Vista has scrambled some internals in the database/registry controlling the USB subsystem's driver knowledge, you're toast. Nothing I could find in Microsoft's Knowledge Base nor MSDN shed any light on how to tackle the removal-and-recreation-from-scratch of the USB system configuration.
Microsoft's stock answer was invariably "re-install Windows". Yeah, thanks for that. Windows, even more than 26 years later, is still not a real operating system, and still has bugs dating back to Windows 3.1.
Sigh.
Check Windows Firewall service.
In my case I just turned off the Windows Firewall and it started working.
regards
Gaurav
i had this problem.
disable any program like Proxifier and firewall
I accidently figured it out
so i was trying to find my cid number because i was flashing ICS firmware and stuff, and the adb deal in the prompt kept giving me the exact same error, and thus would'nt work. after trying everything (such as: installing drivers, killing the process, restarting my comp, reinstalling adb, etc.) for about an hour and a half, i just stumbled upon a page that was linked to in the ICS flash guide, that had a different adb folder download. this download has an entirely different effect on the command prompt and worked so i could get my cid number and rewrite superCid. here it is:
http://forum.xda-developers.com/attachment.php?attachmentid=872134&d=1327512033
Download it, click "start here", then treat it like normal
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
orangeipod1gb said:
ADB server din't ACK
Please help....I was trying installing Hellkat 4.4.2 on my kindle fire by following http://forum.xda-developers.com/showthread.php?t=2570078
Downloaded all the files and flashed through TWRP and was successful. But after flashing, when it is rebooting it is getting stuck on the hellkat logo and not booting.
If I try to install TWRP again, i am getting error ADB server din't ACK *failed to start daemon*. and ADB status online and boot status unknown.
Please help......
Click to expand...
Click to collapse
your solution is
netsh advfirewall set currentprofile firewallpolicy allowinbound,allowoutbound
Hi guys
I did own a Sapphire/Magic back in the days and came back to Android after some skipping done during the last year. Back then installing usb drivers and adb was easy: plug in the Sapphire, point Windows to the drivers folder, done.
With the Vision/Desire Z it was much more complicated. I did use the old drivers from back then and ran into problems. Device manager had an ADB device listed, ADB couldn't find it though. Once I got it working in Android, it wouldn't interface with the recovery adb though. Once I got that working, it wouldn't show/mount the SD card anymore. Short: a huge mess.
Right now I have everything more or less working (still using the old drivers I used with the Sapphire) but it's not really right, I tried an RUU the other day and it would fail because my ADB/RUU ADB/Driver combination wouldn't match.
Long story short: where did you guys get your drivers from to interface the Vision with ADB/Fastboot?
Update the SDK ...this time its in platform tools. run the sdk update and download the usb drivers. Refresh your SDK.
If you don't want to do that...then install pdanet just to grab the drivers
Or go to cyanogenmod the drivers may be avail in a post from ciwrl in vision.dz download section.
All right, I'm d/ling the Java JDK as prompted by the latest SDK installer
Thanks!
I did this too (SDK + Platform tools) to get ADB/shell. However, I never got fastboot to work (even tried fastboot-mac). Not sure what I was missing, but flashing via SD (including radio) has been working thus far for me. Any recommendations on where to get more info on "fastboot" process, specifically on a Mac?
Hmm... you did notice that the fastboot binary is - at least on Windows - in a different folder than ADB, right?
On Windows its two different paths pointing to either ADB or Fastboot.
[posted on the go]
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
Hi Dave, thanks for the reply.
I definitely have USB Debugging enabled - I also am 100% sure that I have installed the hboot driver before (I did it when rooting for the first time ages ago), and can confirm this by booting into Bootloader and having "Android Bootloader Interface" appear as a known device.
Also, with the HBOOT-Driver, it lists the phone as "Android 1.0" when Unknown, whereas my situation lists "Android Phone" as the unknown device.
davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Click to expand...
Click to collapse
Same here.
Have you added the environment variable for the sdk directory? It won't work if you don't.
Also.. install .. HTC Sync.. .and try.. and again uninstall only HTC sync.. and leave the HTC driver and try
I've had issues getting it working too and haven't quite figured out the sequence to get it to work. All I remember is the Android SDK drivers don't work, you need to use the HTC ones. You don't need to uninstall HTC Sync (try re-installing it though). You might then need to run update drivers on the unknown device for it to find them.
I can confirm that it does work with HTC Sync still installed. I sometimes find ADB devices takes a few attempts or restarting ADB to actually work.
vnvman said:
Have you added the environment variable for the sdk directory? It won't work if you don't.
Click to expand...
Click to collapse
Hi vnvman.
Thanks for the reply - I have indeed, my "PATH" value is as below:
C:\Program Files\Common Files\Microsoft Shared\Windows Live;C:\Program Files (x86)\Common Files\Microsoft Shared\Windows Live;%SystemRoot%\system32;%SystemRoot%;%SystemRoot%\System32\Wbem;%SYSTEMROOT%\System32\WindowsPowerShell\v1.0\;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Files\XviD MPEG-4 Video Codec 1.2.2 64-BIT;C:\Program Files (x86)\Common Files\Teleca Shared;C:\Program Files (x86)\Windows Live\Shared;C:\Program Files (x86)\QuickTime\QTSystem\;C:\android-sdk-windows\platform-tools;C:\android-sdk-windows\tools
Click to expand...
Click to collapse
However, even if I cd in CMD to the platform-tools folder and run adb from there, no luck. ADB itself works perfectly, but it just doesn't recognize my phone.
bobsie41 said:
I'm afraid windows 7-64 bit appears to be the problem. I have the same problem but, as yet, not the solution. If you have access to a computer running a different version of windows you should be able to get it to work on there!
Sorry i can't be any more help.
Click to expand...
Click to collapse
Like some others users posted here, win 7 x64 is working for me without any problems.
expza said:
Hi All.
I'm hoping you can help - I've searched far and wide (including the awesome little "Here are the similar threads we found" box that appears when you create a thread) with no luck.
Basically, my phone is as in my signature, but I can't get ADB to work. I go "adb devices" and it doesn't list anything. adb.exe is working, and I can access it and everything via command prompt, but no dice on actually using it.
Not sure if this is helpful or related, but fastboot works 100% perfectly which is what confuses the heck out of me.
I'm running Win7-64Bit. The only abnormality is that Device Manager lists "Android Phone" as an unknown device, yet I can mount USB storage (both in Recovery and when booted into Android) and access the SD-Card.
Trying to locate drivers for "Android Phone" via Windows Update, as well as looking in "C:\android-sdk-windows\extras\google\usb_driver" doesn't assist (drivers are in the directory). Not sure if that is related, but it might be.
Thanks for any and all replies
Click to expand...
Click to collapse
Try to reinstall android sdk completely following this guide:
http://wiki.cyanogenmod.com/wiki/Howto:_Install_the_Android_SDK
Hi MatDrOiD.
Thanks for the reply, I'll give that a shot as well as try jhonybravo4u and Antcodd's ideas.
Appreciate all input. If I get it working, I'll be sure to update this post so that anyone else who might have this problem has a solution
davebugyi said:
Windows 7 64-bit IS working - I am using it and it works without problems.
Do you have USB Debugging enabled in Settings > Application > Development?
Also: try this driver & instructions: http://unrevoked.com/rootwiki/doku.php/public/windows_hboot_driver_install
Click to expand...
Click to collapse
What i meant is that windows 7 seems 64bit seems to cause more problems than any other windows os. I had a windows 7 64bit computer and after days of pratting about i managed to get it working now, further down the road, and a bit more knowledgable(i think!) i have a new more powerful windows 7 64bit machine and i can't for the life of me get it working.
I know run adb from my wifes vista laptop and had no trouble whatsoever in setting this up.
If u tried "everything", u better don't ask for more ;-p
Sent from my HTC Desire using XDA Premium App
It worked for me last time, but then I formatted my drive, and now can't get it to work for the love of god. Actually I can, but I have to change the driver every time Android phone pops up in the device manager using have disk.
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