Related
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
buster3845 said:
Guys, I need a little help here. I've rooted my share of phones, and even some tablets, but the Evo i bought a few days ago has been a nightmare.
For some reason, and I can't tell why, this thing will not be recognized by Windows.
It always shows up as "Unknown Device" under the USB catagory on Device Manager.
I've tried different OS versions (Windows 7 64Bit, Vista 64bit, Even Mac). I've also pulled down every form of driver I can think of (SDK Orginal version, HTC Sync, Hboot Versions, etc.)
I just cannot get this thing to be recognized. And if I manually try to update the driver and point it to one that I've downloaded, Windows tells me that the most current driver is already installed.
The bottom line is that I need to be able to connect to the phone from the comp in order to push stuff via ADB and throw commands at it. The same unknown device situation happens when the phone is in bootloader or actually booted into Stock Froyo (2.2)
Has anyone ever seen anything like this? I know i haven't, and it's buggin me out.
Click to expand...
Click to collapse
I've never seen that before. Wish I had something for ya. Is the Evo brand new or used? Are you sure the usb cable is good? I've seen a bad cable cause some headaches before. Wish I had more for ya, sorry man.
Sent from my PC36100 using XDA App
EVO is not new. I bough it from cragslist a few days ago. It seems to work fine otherwise. Not rooted for sure, and running Sprint original 2.2.
I did try a couple of different USB cables just to be sure, and had the same results.
The funny thing is that even though I was never able to get it "recognized" on any of my machines, I was able to get ADB so "see" it for a while. I started the rooting process by pushing files to it via ADB and even sent a reboot command to it.
Once it rebooted, that's when it all went bad. It was still showing as unrecognized (just like before), but now ADB can't see it at all. Keeps telling me no devices are connected.
Even my friend's Mac Air (which supposedly doesn't need any kind of drivers to see the phone) can't see it either.
It's just weird...
perform a hard reset, maybe a rogue app or setting got messed up,
fastboot screen>clear storage>yes
Tried that as well. Sorry i didn't mention it in the original post.
I think I've pretty much tried everything that's somewhat logical at this point.
Now I'm looking for the "illogical" ideas.
Make sure usb debugging option is turned on in settings>applications>development and the phone is in charge only mode. Then it should be recognized and you should be able to use adb.
Debugging was turned on already. I made sure of that.
As for the mode of connection I've tried them all with mixed results.
Here's what I've seen so far...
Charge only - unrecognized device in Device manager, and ADB can't see it.
HTC sync - unrecognized device in Device manager, and ADB can't see it.
Disk Drive - unrecognized device in Device manager, and ADB can't see it.
Internet Sharing - never tried it.
Here's the weird part. If i uncheck Debugging and set the phone to HTC Sync, I am sometimes able to get ADB to see it.
This is just confusing...
What happens if you uninstall HTC Sync and just leave the drivers installed? Could work I suppose. I know unrevoked says to make sure you uninstall HTC Sync and install the ADB drivers.
try this. connect your evo to a machine running xp. i had the same problems rooting one evo using windows 7. connected to a machine running xp ,zipped right through without a hitch.
HOPE THIS HELPS YOU IN YOUR QUEST
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
I'm not sure which USB drivers you are using, but these work for me. Uninstall the drivers first, then install this. I hope it is legal to put these here and if not I am extremely sorry.
PS you could try a Linux Live CD and it will see it without drivers or go with Wubi which installs Ubuntu on your Windows hard drive and can be uninstalled just like any other program. It gives you the option to boot into Ubuntu or Windows on bootup. Neat little program and it is faster than using the live CD. Go to this link Wubi and click the Start Download button to download Wubi.
Those seem to be the same drivers I've tried (well those and a ton of others as well).
I'm gonna give that LiveCD idea a shot. Burning it now.
If not, I'm gonna try to find an XP machine somewhere.
I've got a couple of VM's on my machine running XP, but since the main Win7 Machine doesn't see it, it can't seem to pass the USB connection over to the XP VM.
Man, I have to say, this is just the most complicated rooting process I've ever seen. If this was my first root attempt, I'm pretty sure I'd leave Android forever
It usually is a painless operation to root the Evo. For some reason you are having a difficult time with driver installation. It seriously has to be something simple that has been missed, because I have rooted mine and several friends Evo's and it was very easy. I had a MyTouch 3g 3.5mm before this Evo and talk about a pain. Before the Universal Auto root app you had to make a gold card first and that in itself took over an hour. It was my first root and it was very difficult and time consuming, so to see how easy the Evo was no matter which way I do it made me very happy.
buster3845 said:
Thats what I tried on the Vista box.removed HTC sync, and left the HTC drivers.when that failed I removed the drivers too and replaced them with several different ones I found online.none seemed to work.
The strangest part is that all guides seem to say that MAC OS should just see it without any drivers.
I borrowed friends MAC air and it didn't see it either.
Click to expand...
Click to collapse
yes the mac doesn't require additonal drivers to run adb however u need to make sure the directory is properly set in terminal so adb knows where to pull commands from... on windows did u try uninstalling everything phone related? SDK, HTC Sync, the whole nine yards then try reinstalling only the sdk and the usb drivers? I know with the lastest SDK the usb driver is not included for some reason or at least it wasn't with mine... then one day my adb just randomly stopped working and a uninstall/reinstall cleared up everything... try this usb driver and see where it gets u. Don't know if it's any different that wat the guy above posted but worth a shot. Reinstall the appropriate SDK first then i would recommend plugging the evo into the pc with no usb drivers installed then when it cant automatically find the drivers direct it to the file u downloaded and it should pull the necessary drivers from there and see if that does the trick...
View attachment android-usb-driver.zip
No dice so far guys...but i have made progress in identifying the issue (sort of).
So here's the deal - the ONLY way the phone is recognized is if i toggle the "debugging" setting.
If i plug the phone in with the switch set on (meaning USB Debugging enabled) the phone is not recognized. Pointing the unknown device to the drivers (any drivers) does nothing.
However, if i plug the phone in with the switch set off, it finds a usb mass storage device. Then i turn the debugging switch on, and it finds the ADB Android phone with no issues. Then i can push commands via ADB without any problems.
The problem i have is that I cannot toggle that switch if i boot into HBOOT menu. So the comp never see's the phone.
I've tried this experiment on Win7-64bit, Vista-64bit, XP 32bit, and even MAC.
The same situation seems to apply everywhere, and with all of the drivers I've tried. None of them seem to allow the phone to be plugged in and automatically be found. The only way for the comp to see the phone is if i toggle the debugging switch off, then on.
At this point, I'm ready to put out a bounty on this. $20 via PayPal to anyone who can walk me through it. Bottom line is that I need to be able to see the phone without having to toggle the debugging switch. That will allow me to boot into HBOOT and still send commands to the phone via ADB.
Thanks for all the help guys. Hopefully, we can get this resolved.
**BUMP**
Anyone care to take a shot??
Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!
mojo1633 said:
Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!
Click to expand...
Click to collapse
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA
The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.
eksasol said:
The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.
Click to expand...
Click to collapse
Thanks both of you for your help so far. I tried installing these naked drivers but no still luck. I don't have any preexisting Android drivers on the computer, but how would I uninstall drivers on the Nexus? The message I get when I try to update the drivers to these is that Windows could not find a better match for the hardware than you currently have installed. I checked the Driver Details and the driver it has listed is C:\WINDOWS\system32\DRIVERS\klfltdev.sys. I've tried numerous times "uninstalling" the driver, rebooting the computer, and starting the process over again but still no luck. I'm unable to actually remove this system file from my computer. I've been trying to do this on a work computer running XP, but I tried the naked drivers on a Vista machine as well, and I still get a similar message about the software already being the best match when I try to point Windows to these drivers (again, no other drivers installed on that machine). I'm so frustrated...
PoorCollegeGuy said:
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA
Click to expand...
Click to collapse
I have done all of this, including following the complete instructions and trying all options at http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Still nothing seems to work. I am at a complete and total loss, and am entirely discouraged. For the life of me, I can't believe it's so utterly difficult just to properly install device drivers on a developer phone.
Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.
ifly4vamerica said:
Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.
Click to expand...
Click to collapse
Yes, I turned debugging on. Never hurts to check, though. I'd love for the solution to be something so simple that I just overlooked.
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
First of all, DO NOT USE TOOLKITS!
I know it is easier for you, since you are new to this rooting stuff, but trust me on this, 2/3 people who said their phone's bricked used toolkit instead of adb and fastboot method
Now with that out of the way, you can check if you got any other drivers installed by going to Control Panel->Hardware and Sound->Device Manager
From there, connect your phone via USB and see driver pop up. If it's something like "Android 1.0", uninstall that, and then install naked driver. If you don't see any driver pop up after connecting, just install naked driver (for me, when I checked USB debugging, Windows automatically installed Samsung ADB driver that works well for me.). If you see something like "Samsung ADB Interface Driver", you should be able to use adb commands and such.
If you don't have fastboot and adb files, make sure you do this step!: After that, you should download adb files, fastboot files (adb and fastboot files can be found from Efrant's attachment from this thread: http://forum.xda-developers.com/showthread.php?t=1626895), and Android SDK (If you already have SDK for some reason, just download adb file and fastboot file ). After downloading Android SDK, put the folder in somewhere easy to find. (C:\ directory should do it). Now, put adb and fastboot files inside the platforms file (that can be found from SDK folder)
Now you got files set, go to the directory where you put adb and fastboot files, shift+right click and then click Open Command Prompt Here
Type "adb devices" and if you see one device from the cmd, you are good to go
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
lol nice.
mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
That's great! Make sure you give the guy who helped you Thanks
I have previously have installed drivers for 3 android devices and never had a problem except now. Neither my pc or my laptop (both win7 64bit) can recognize it. I've tried changing ports (could not change cables because I do not have an extra micro usb cable), I have installed and uninstalled several times on both computers. I've even tried to see if it ewas a compatibility issue with the 64 bit sytem but when I went into setup.exe properties there was not a compatibility tab. I bought this refurbished from Walmart so Acer no longer covers it under warranty. I did buy a 2 year extended warranty that I can use as a last resort.
Is the micro usb cable suppose to seat flat against the body of the Acer a100 or can you see a portion of the metal part of the plug? Also, should I be able to wiggle the usb plug back and forth. Any assistance with this would certainly make my day. I have been working with this for 2 days now.
I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium
[email protected] said:
I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Yes, I did download from Acer. I finally went back and reviewed the paper work that came with Tab and found that the company that refurbished for Walmart has a 90 day warranty. I have emailed there warranty support service, hopefully I will hear something from them tomorrow. The only thing I have not tried is a different usb cable which I will pick up tomorrow at good old Radio Shack. If that does not fix the problem then the problem must be in the Tab. I have installed drivers for 3 other android device on the same pc's and never had a problem. Tomorrow is going to be a busy day for me. Dealing with this issue, going to the dentist and I am suppose to get the new Vizio Co-Star so I will be setting that up and then learning how to operate it and seeing what its potential is.
[email protected] said:
I'm assuming you installed the driver downloaded from Acer? My laptop is also 64-bit and it recognizes just fine after installing the driver. Yes, you can still see some metal part of the usb plug and it does wiggle, at least it does on mine.
Sent from my Nexus S using xda premium
Click to expand...
Click to collapse
Would it be possible to install clockworkmod and root and install the rom over wifi? I not sure how to do it but, I am sure there is someone that has done this before.
lartomar2002 said:
Would it be possible to install clockworkmod and root and install the rom over wifi? I not sure how to do it but, I am sure there is someone that has done this before.
Click to expand...
Click to collapse
Only if you have adb over network, which stock doesn't have, so no you can't do that, has to be USB.
Tapatalked from my Galaxy S II.
pio_masaki said:
Only if you have adb over network, which stock doesn't have, so no you can't do that, has to be USB.
Tapatalked from my Galaxy S II.
Click to expand...
Click to collapse
Da*n, Oh well, back to the drawing board.
lartomar2002 said:
I have previously have installed drivers for 3 android devices and never had a problem except now. Neither my pc or my laptop (both win7 64bit) can recognize it. I've tried changing ports (could not change cables because I do not have an extra micro usb cable), I have installed and uninstalled several times on both computers. I've even tried to see if it ewas a compatibility issue with the 64 bit sytem but when I went into setup.exe properties there was not a compatibility tab. I bought this refurbished from Walmart so Acer no longer covers it under warranty. I did buy a 2 year extended warranty that I can use as a last resort.
Is the micro usb cable suppose to seat flat against the body of the Acer a100 or can you see a portion of the metal part of the plug? Also, should I be able to wiggle the usb plug back and forth. Any assistance with this would certainly make my day. I have been working with this for 2 days now.
Click to expand...
Click to collapse
I also have this problem with two Computers,Windows 7 64 Bit and Windows 8 Consumers Preview 64 Bit. Many Hours Lost trying but still unable to find a fix. It has to be a Security Issue possibly with an Exploit in the USB Driver Software. My Resolution was to Break Out the Old Trusty Dell XP Laptop. Copy and Pasted the Same Downloaded Files to a USB Drive and used them on the XP Laptop and in Less then 5 Minutes Successful Root !
Izzyb914 said:
I also have this problem with two Computers,Windows 7 64 Bit and Windows 8 Consumers Preview 64 Bit. Many Hours Lost trying but still unable to find a fix. It has to be a Security Issue possibly with an Exploit in the USB Driver Software. My Resolution was to Break Out the Old Trusty Dell XP Laptop. Copy and Pasted the Same Downloaded Files to a USB Drive and used them on the XP Laptop and in Less then 5 Minutes Successful Root !
Click to expand...
Click to collapse
I was at Radio Shack and bought a cable for $20.00, what a rip-off I could have gotten the same cable for $4.95 from Monoprice. Anyways that was the problem and now the pc sees the device.
You can download an Ubuntu Live CD for free, and boot from it without needing to reformat / repartition your hard disk. In other words you don't need to install it, just reboot run the commands you need, take the disc out, boot back to windows and done.
I put together this package that simply includes adb and fastboot, it will install them automatically and allow you to run them with ease.
Download here:
android-cmdline-tools.zip
Instructions:
Boot into your Live Ubuntu CD (or other distro)
Download the above package
Open your terminal emulator (i.e. Gnome Terminal, Konsole, Terminator, etc) do the following:
Code:
cd /tmp && unzip ~/Downloads/android_cmdline_tools.zip
*If you downloaded to a different location you need to correct the path, I used ~/Downloads as it is the typical download location on linux for Chrome and Firefox.
After the file is unzipped you should have the android-cmdline-tools directory in /tmp/android-cmdline-tools
Now lets install adb and fastboot:
Code:
cd android-cmdline-tools && sudo bash ./install-linux.sh
(may request your password if you are on a live cd then it shouldn't, however if it does leave it blank, otherwise you should type your users password)
This will prompt you to make sure you wish to install. Enter Y to install, any other key to abort
If this succeeds, you will now have adb and fastboot ready to run on your device
On linux you shouldn't need any special drivers for these tools to work with the A100 so this package is a small convenient download that is quick to install and use the tools, and should come in handy for usage via Live CD/DVD to access your A100 or most other android devices through adb/fastboot
Good luck and hope this helps!
linuxsociety said:
One quick solution would be to grab an Ubuntu Live CD download and reboot your computer into the Live installation, download the adb and fastboot files for linux. You usually can get them in packages aimed at flashing recovery so you don't have to download the entire Android SDK. Ubuntu shouldn't have a problem seeing your A100 without the need for any drivers or modifying any .ini files. This is an alternative, so that you don't have to wipe your Win7 install. just keep a Live CD for linux laying around, they usually come in handy!!
Actually now that I am thinking of it I'll just make a package named A100-cmdline-tools.zip that contains both adb and fastboot for both windows and linux. Maybe it will come in handy for some of you guys
Click to expand...
Click to collapse
Bought another micro usb cable and that fixed the problem. But I am going to use your suggestion and burn a Live CD to have around. Thanks
lartomar2002 said:
Bought another micro usb cable and that fixed the problem. But I am going to use your suggestion and burn a Live CD to have around. Thanks
Click to expand...
Click to collapse
edited that post, made a Linux android-cmdline-tools.zip package that includes both adb and fastboot and will install them for you. May be a handy .zip file to keep laying around for your PC, small size and easy for a quick download too if your on Live CD. I also have the Windows adb.exe and fastboot.exe files as well as the required .dll's in the zip, I just haven't made an installer for windows (yet - will be install-windows.sh) .
linuxsociety said:
edited that post, made a Linux android-cmdline-tools.zip package that includes both adb and fastboot and will install them for you. May be a handy .zip file to keep laying around for your PC, small size and easy for a quick download too if your on Live CD. I also have the Windows adb.exe and fastboot.exe files as well as the required .dll's in the zip, I just haven't made an installer for windows (yet - will be install-windows.sh) .
Click to expand...
Click to collapse
Where do I d/l from?
lartomar2002 said:
Where do I d/l from?
Click to expand...
Click to collapse
where it says download here, and then provides the link or I'll just provide it in this msg too: http://beta.androidfilehost.com/?fid=9390062577138008179
linuxsociety said:
where it says download here, and then provides the link or I'll just provide it in this msg too: http://beta.androidfilehost.com/?fid=9390062577138008179
Click to expand...
Click to collapse
Duh! Sometimes I can be so dense.
A few weeks after rooting and installing CM10 on my GS3, it stopped recognizing any form of USB data connection. It still charges from both computer and wall adapter, but I cannot initiate a data transfer or recognize my device using ADB.
I have tried:
three different OEM Samsung cables (from SG3/SG4 phones)
all the ports on two different Win 7 laptops
all the ports on an Ubuntu desktop
enabling or disabling USB debugging
with different combinations each time. No "USB connection" dialog has shown up on the phone, and no "new device" dialog has shown up on any of the computers. I know that I can get ADB working with a different Android phone (HTC Inspire 4G) so I know that my main laptop has USB ports that work and the cables I've tried work as well, so I'm left to assume that the issue is with the GS3. External visual inspection does not suggest the USB port on the phone is damaged, and the phone is only a year old, so I don't believe that is the cause.
Is there a system setting that I may have modified on the GS3 that would disable all forms of USB communication?
(The end goal is to get at least ADB working so I can try and recover some deleted files from the internal memory; I haven't found a reliable method that does not require ADB so I'm trying to get that to work. I know that transferring files on or off can be accomplished with the external SD card or over Wifi but that is not what I'm looking for)
Any suggestions from anyone?
I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7
stelv said:
I am not sure. Could be a software issue. I would try backing up your current cm ROM and try installing a fresh touchwiz ROM to see of that works, to rule out software issues. This could also be a android 4.3 issue. Could try stickmount or a similar otg app from the market.
Sent from my Nexus 7
Click to expand...
Click to collapse
I don't think any OTG app like stickmount will help; I'm not trying to connect devices to my phone. I'm trying to get my computer to recognize my phone (and vice versa) in order to get ADB working.
If I can avoid flashing a RAM I'd like to, because I'm still interested in recovering those deleted files. If that is the only thing that would help, though, then I'll do it. Any other suggestions?
Install Kies and that should get the drivers for the pc in place. Odin should recognize the device when it is in the download mode. If that works, then the pc to phone connection is OK and I'd look to software instead of hardware.
Or, if you boot into your custom recovery, either CWM or TWRP, you should be able to get ADB to recognize the device and issue commands including pulling the files on Internal storage. TWRP also has a file browser built in that might be useful.
I have tried uninstalling any Samsung drivers then using the SGS3 toolkit to install the official drivers, but that didn't change anything on the PC end.
Additionally, I tried finding my device while it was in recovery using ADB and there was no connection indication either.
I currently have CWM installed, but I didn't see a mounting option like I've seen for TWRP. Can I flash TWRP without a computer?
Or try this out: Download mode>Connect via USB>Let Windows download and update all drivers until the notification in the bottom right says it's ready to use>Unplug>Battery Pull>Boot normally>connect again. Voila! It works every time when it's being wonky and its a simple way that doesn't require a bunch of downloads!
installing insecure adb might help
Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?
thanks
thanks
what next?
aEx155 said:
Rebooting into download mode does nothing.
I believe rooting and installing CM10 means I already have insecure adb?
Click to expand...
Click to collapse
I have this same issue, in download mode, the device is still not connecting.
what is the next step? I have followed this thread and have the still have the same issues.
So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?
Subscribed
I'm having the same issue. Stock non rooted and it will not connect. I have tried it on other computers cables ports everything.
Art2Fly said:
So my phone was mounting fine on my pc, and then all of a sudden it wasn't. My Nexus 7 still mounts properly and accepts developer commands, but the m8 won't (yes developer settings is on).
I tried wiping and flashing a rom clean and it still doesn't work, charges fine though. Any advice?
Click to expand...
Click to collapse
You might try a different cord.
Open Device Manager in Windows and then plug the phone in. Do you see it in the list with a little yellow triangle? Do you see Android USB Devices listed?
OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck
beamer1341 said:
OP after literally messing with various driver files, 8 usb ports and 2 laptops, I dug out my old box of cables and found a taped up, on its last limb OEM HTC EVO 4g (not lte the original) cable. This thing has been through the ringer. But its exactly what It needed. I figured with the 3 cable I had already tried this wasn't the issue, but have you tried using an OEM cable? I guess that is all that works. Good Luck
Click to expand...
Click to collapse
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader
Art2Fly said:
Still trying to get it to work, have tried 4 cables myself. I might just end up having to return the phone.... Fastboot works in bootloader
Click to expand...
Click to collapse
Uninstall all HTC drivers and HTC Sync. Then connect the phone. DO NOT choose the option to automatically install any drivers.
Open Device Manager, find the phone. Select the option to manually pick the driver, and select the generic MTP device driver.
This is what worked for me, after countless attempts at re-installing various HTC drivers, different cables and ports, etc.
Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.
Art2Fly said:
Bump. Still looking for answer to this. I have RUU'ed both to Sense and Google Phone editions and the problem still persists, the phone does not detect its connected to a computer and change to mtp accordingly. Only way I was able to get the RUU in there was through fastboot, which is again the only time I can access the phone through usb. Adb is no luck in either android or recovery.
Click to expand...
Click to collapse
Have you tried revoking the USB debugging authorization and then accepting the RSA fingerprint key again when connecting to PC?
Obviously it can't be an USB cable problem if you can connect to it in bootloader mode and use fastboot commands.
To clarify, the phone just charges when connected, it does not detect that it is connected to PC so debugging doesn't even trigger, neither does mtp. I don't even get the slow charging notification
Does it do the same when you plug it in and reboot the computer to "pick up" during boot up process? Or if you run a live CD? I never had an issue like that with my phone but I did have a similar problem with the USB external blu ray drive I bought some time ago. The pc just didn't detect it at all not on any of the ports until I rebooted my PC with the drive already plugged it and for some reason it picked it up. <Not a solution as I don't know what caused it to not be detected in the first place but still...
Not sure if it's an issue with the device(Phone for you, blu ray drive for me) or if it's a problem with the PC even though other things might still work for you as it definitely did for me(phone, headset, mouse, keyboard, usb extender + all the external hard-drives connected to it)...
Problem exists in all computers, Mac, pc, linux
Did you try what I suggest in Post #6 above?
This worked for me when I had the same issue. adb and fastboot would work, but it would not mount MTP.
And just in the last day or 2 I helped someone else with the same issue and fix.
The phone doesn't show up in device manager.
Have you modify the Kernel? (Applying some settings for example)
I browsed over the web for this issue and found some people with the same problems. They solved by removing the settings applied on the kernel or flashing a new one.
I've flashed various kernels and ruu, still same result
Still looking for help