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??
I've searched and search and found nothing, so I need a little help with this one.
On my computer I run portable apps from a flash drive. I also like to connect my Android phone. The problem I have is that while either one works swell by itself, the computer fails to recognize one or the other when both are plugged in at the same time. Preference is always given to the device that is plugged in first.
As I'm always using my flash drive, it's a hassle to disconnect it just to plug in my phone. And it's even more irritating to know that I can't access my portable apps as long as my phone is connected. The best I can do so far is to plug the phone in and choose charge only which allows XP to see it as an Android ADB device. This assigns drive letters to the multiple drives android uses, but all drives are listed as being empty. I should also note that I do have a printer connected via USB but I never have any problems with it.
What I've tried to fix the problem:
-Utilize the USB ports in the rear of the computer - No Luck
-Manually assigning drive letters - No Luck
-Search for alternative driver for Flash Drive - No Luck
-Downloaded HTC SYNC for an alternative driver to my phone - No Luck
-Downloaded and "Unsuccessfully" attempted to install Android SDK USB driver. - I don't know if this would have solved the problem or not but the installation of SDK never seems to give me the driver the phone is looking for.
So I'm at a loss as to whether or not there is a fix to my problem. Any help would be appreciated!
Computer - XP SP3 / Pent 4
FlashDrive - 8Gig Corsair Voyager
Phone: Rooted HTC Incredible running Synergy RC1 ( I throw this in there just for an FYI but the problem was present on other ROMS I've tried so I'm not led to believe it's a Rom issue)
I'm not sure if this is a Phone issue, or a computer issue so I've cross posted this with the folks over at Tech Guy Support
MOD - Problem Solved please feel free to delete if you don't think it's useful to keep this around.
Problem was solved (Credit to Rockn over at Tech Guy Support). My PC is underpowered to run my USB devices. I plugged the phone into a Powered USB Hub and it works perfectly now.
I've read some people are having trouble with GN2 when connecting it to a PC via a USB cable. I've been having that problem as well.
I've found some suggested solutions, but none worked for me:
Code 10 error device manager
Missing Hardward ID fix
I found a partial solution. It's limited in what is solves. This is good for a user who is looking just to be able the phone USB storage so you can transfer files and what not. This does not give access for ADB. This will get rid of the need to plug and unplug the usb cord, or enable or disable USB debugging or whatever else people need to a bunch of times for the phone to finally be recognized by their machines. This works in Windows 7 64bit; I assume 32 bit. Don't know about Windows 8 (if there is the problem)
Basically, uninstall the Samsung USB drivers. Then just reconnect the GN2 to your PC. Let Windows install it's drivers. You'll see failures for Ssmsung and ADB, but still have access. You'll get the same access with and with USB debugging. Below are pics showing the results of driver installation by Windows, and hardware device properties. If you click the picture, you get see a large image of the screen shot.
Without USB debugging
WIth USB debuggind turned on:
Maybe someone with more knowledge can figure out the rest to complete fix the issue. But I assume for most, this should be sufficient.
lovekeiiy said:
I've read some people are having trouble with GN2 when connecting it to a PC via a USB cable. I've been having that problem as well.
I've found some suggested solutions, but none worked for me:
Code 10 error device manager
Missing Hardward ID fix
I found a partial solution. It's limited in what is solves. This is good for a user who is looking just to be able the phone USB storage so you can transfer files and what not. This does not give access for ADB. This will get rid of the need to plug and unplug the usb cord, or enable or disable USB debugging or whatever else people need to a bunch of times for the phone to finally be recognized by their machines. This works in Windows 7 64bit; I assume 32 bit. Don't know about Windows 8 (if there is the problem)
Basically, uninstall the Samsung USB drivers. Then just reconnect the GN2 to your PC. Let Windows install it's drivers. You'll see failures for Ssmsung and ADB, but still have access. You'll get the same access with and with USB debugging. Below are pics showing the results of driver installation by Windows, and hardware device properties. If you click the picture, you get see a large image of the screen shot.
Without USB debugging
WIth USB debuggind turned on:
Maybe someone with more knowledge can figure out the rest to complete fix the issue. But I assume for most, this should be sufficient.
Click to expand...
Click to collapse
Hey....Thanks so much!! It's a good start.
With all of the brilliant developer on these boards, I'm surprised no one has come up with a fix yet. In good time!!!!
I figured most users on here aren't needing to use ADB after rooting, but want to access storage. I tried accessing using ADB, which I have installed on my PC but never use, and it wasn't connecting. I had to look up how to use it. When I asked for listed devices, nothing came up.
If you look at the threads listed, it appears it's a driver issue with Samsungs USB drivers. I figure at some point either Samsung or Microsoft will fix it, more than the developers here. Although, I think they'll probably find a solution faster.
HA! I'm glad I'm not the only one. I've been rebooting my PC to solve the issue. It only happens once in a while. I'll be watching this thread. Thanks
I know this isn't exactly on topic but I've seen this discussed here and other forums as far as "properly" ejecting the Note 2/GS3 from your PC. Some say you just pull the USB, it will not corrupt etc. I just wanted to share that you can eject(windows). Just go to Devices and Printers, you will see SPH-L900 in your list. Right-click and eject. Probably means nothing but figured I'd share for those that feel iffy about just pulling the plug
I just pull my USB. I don't do the whole eject thing. The "having" to do the eject thing basically went out when Windows 7 arrived. I've been doing this method for couple years with Windows 7 for various devices. Never an issue.
And even faster than when you mention, if on WIndows 7, you go to the task bar to the right, there is a triangle that shows all your running background apps. Click that, right click the USB icon. It should be listed. If not, there is a "open devices and printers" which takes to the same place.
Hi Guys,
A weird one here for you, I'm already contemplating throwing my phone at a wall that's how long I've been trying to fix it.
I have a LG G3 D855 Gold 32gb model purchased via Kogan in Australia.
The unit is now on Android 5.0 (no updates available for 5.1+) - Software Version V20i-SEA-XX with Build number LRX21R.A1440645925.
This phone is non-rooted with stock ROM etc.
So the issue at hand, I upgraded my Win7 PC via the upgrade option to Win10 to retain my games/files etc.
Now when connecting the phone to the PC it only goes to charging mode and I am unable to click on it within the drop-down to change it to anything else.
I have tried LG G3 drivers, Googles generic drivers, ADB suite drivers. I am unable to adb find the phone, I do not have an Acer Composite device in Device Manager.
Win 10 keeps saying the device is not recognised/malfunctioned.
Tried different cords, double checked the connector on the phone for any dust specs etc.
My PC refuses to work with any driver I have thrown at it, however in each scenario with various drivers, warnings still persist in Device Manager.
Some of the drivers force the phone to connect/reconnect and cause the "ping" sound each time it disconnects and reconnects (with malfunction warning prompts).
This is on Win10 with 64bit Home edition.
I am at my wits end and can't think of anything I haven't tried beyond a factory reset of my phone (hoping not to at this stage as I'm thinking it's driver-related).
It won't let me tether or anything via USB also, same goes with USB debugging, no change.
Lastly which may also help narrow it down, with the phone plugged in BEFORE it gets to the OS, I can change between PTP/MTP and USB charge, however once the Win10 OS loads up, it disconnects/malfunctions and lists Charge Only.
And yes, this phone can connect on my Win7 small PC which I use for testing crap out on.
Any ideas guys?
Let me know if any log files or anything is required.
At this stage I am unable to do a root to the phone (due to adb issues etc) nor can I connect to the internal phone system unless I use in the in-built file explorer.
Edit: *SOLVED*
Ok so turns out the issue is, and this is just my case, my motherboard has various utilities, one of which is a USB 3.0 boost option.
When I did an upgrade to Windows 10, it somehow screwed up various programs on my PC including registry etc.
I reinstalled the particular utility (I was actually trying to fix my graphics clock etc so happy coincidence) which also re-installs the USB 3.0 Boost software which in turn has fixed my USB Ports.
So if you have a custom built PC (my Motherboard being a Rampage 4 Formula). Check the Mobo Utilities/Drivers for any conflicts.
I have the exact same problem, and I can't seem to find a solution for months now. It's really annoying and depressing
nicholsonr said:
Hi Guys,
A weird one here for you, I'm already contemplating throwing my phone at a wall that's how long I've been trying to fix it.
I have a LG G3 D855 Gold 32gb model purchased via Kogan in Australia.
The unit is now on Android 5.0 (no updates available for 5.1+) - Software Version V20i-SEA-XX with Build number LRX21R.A1440645925.
This phone is non-rooted with stock ROM etc.
So the issue at hand, I upgraded my Win7 PC via the upgrade option to Win10 to retain my games/files etc.
Now when connecting the phone to the PC it only goes to charging mode and I am unable to click on it within the drop-down to change it to anything else.
I have tried LG G3 drivers, Googles generic drivers, ADB suite drivers. I am unable to adb find the phone, I do not have an Acer Composite device in Device Manager.
Win 10 keeps saying the device is not recognised/malfunctioned.
Tried different cords, double checked the connector on the phone for any dust specs etc.
My PC refuses to work with any driver I have thrown at it, however in each scenario with various drivers, warnings still persist in Device Manager.
Some of the drivers force the phone to connect/reconnect and cause the "ping" sound each time it disconnects and reconnects (with malfunction warning prompts).
This is on Win10 with 64bit Home edition.
I am at my wits end and can't think of anything I haven't tried beyond a factory reset of my phone (hoping not to at this stage as I'm thinking it's driver-related).
It won't let me tether or anything via USB also, same goes with USB debugging, no change.
Lastly which may also help narrow it down, with the phone plugged in BEFORE it gets to the OS, I can change between PTP/MTP and USB charge, however once the Win10 OS loads up, it disconnects/malfunctions and lists Charge Only.
And yes, this phone can connect on my Win7 small PC which I use for testing crap out on.
Any ideas guys?
Let me know if any log files or anything is required.
At this stage I am unable to do a root to the phone (due to adb issues etc) nor can I connect to the internal phone system unless I use in the in-built file explorer.
Click to expand...
Click to collapse
Try the drivers from this site
http://forum.xda-developers.com/showthread.php?t=2785089
ludoke said:
Try the drivers from this site
http://forum.xda-developers.com/showthread.php?t=2785089
Click to expand...
Click to collapse
Using the drivers on that page you have advised gives the following.
Device Manager shows a Warning on it in USB controllers as "LGE Mobile USB Composite Device". It automatically "malfunctions" according to Windows 10 and I can't change the connection interface on the phone.
Going into the properties on that device in Device Manager lists the following;
This device cannot start. (Code 10)
A device which does not exist was specified.
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
This also works for win 10
If u find this helpful rember the thanks button
TheMadScientist420 said:
http://forum.xda-developers.com/lg-g3/help/answer-windows-8-8-1-detecting-lollipop-t2967574
This also works for win 10
If u find this helpful rember the thanks button
Click to expand...
Click to collapse
This didn't work. Already tried
Fixed my problem
I've had the same issue with my LG G3 in being unable to connect the device to my laptop. I'm not sure if the cause was a phone software update or the upgrade from Windows 8.1 to Windows 10. Either way, I searched and fixed it tonight by installing updated drivers. Hope this helps others as well.
Hmmm, I cannot post the link! technobuzz dot net lg g3 drivers
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
So I found a few mentions of this throughout the forums, but nothing that came really remotely close to solving the problem.
I'm having trouble getting my machines (a laptop and a desktop) running Ubuntu to recognize my device (LG G4) - but not always. So naturally, I tried to set it to PTP mode, but I actually couldn't find this setting anywhere on the device. I plugged it in on my Windows machine and made sure it was in PTP mode while plugged in, and still no luck. This is pretty problematic seeing as I'm a developer and I'm going to be starting work on an Android app for work soon. I'm not 100% sure if this is a problem centralized to the G4, but I didn't really get any reception on the Ubuntu forums, so I thought I would check here. Has anyone else had this problem?
No problems here, though I am using 15.10.
It does take a few moments, though. Once the phone is plugged in, I get the 'USB Connected' notification. which is where you can tap to change from mtp to ptp. After a few moments, it will automatically go to mtp/ptp mode - whichever was the last mode you set. Then a few moments later the debugging notification comes up, and I am then able to see the phone in adb.
misterbreadcrum said:
So I found a few mentions of this throughout the forums, but nothing that came really remotely close to solving the problem.
I'm having trouble getting my machines (a laptop and a desktop) running Ubuntu to recognize my device (LG G4) - but not always. So naturally, I tried to set it to PTP mode, but I actually couldn't find this setting anywhere on the device. I plugged it in on my Windows machine and made sure it was in PTP mode while plugged in, and still no luck. This is pretty problematic seeing as I'm a developer and I'm going to be starting work on an Android app for work soon. I'm not 100% sure if this is a problem centralized to the G4, but I didn't really get any reception on the Ubuntu forums, so I thought I would check here. Has anyone else had this problem?
Click to expand...
Click to collapse
Have you tried this?
Find the vendorid and productid with lsub:
$> lsusb
Bus 001 Device 013: ID 0bb4:0c02 HTC (High Tech Computer Corp.) Dream / ADP1 / G1 / Magic / Tattoo (Debug)
...
the "0bb4" is the vendor-id, the "0c02"is the productid
open the file "/lib/udev/rules.d/69-libmtp.rules" for edit:
$> gksudo gedit /lib/udev/rules.d/69-libmtp.rules
Insert the new device, by duplicating a previous one and correcting the id's and save the file:
# Wiko DARKMOON
ATTR{idVendor}=="0bb4", ATTR{idProduct}=="0c02", SYMLINK+="libmtp-%k", MODE="660", GROUP="audio", ENV{ID_MTP_DEVICE}="1", ENV{ID_MEDIA_PLAYER}="1"
Unplug your smartphone and replug it. Your Linux should mount your device like it would do for other one.
Click to expand...
Click to collapse
I got these directions from http://stackoverflow.com/questions/15055304/unable-to-mount-samsung-android-in-ubuntu and it helped me get my phone properly recognized in Mint.
dcorrea said:
Have you tried this?
I got these directions from http://stackoverflow.com/questions/15055304/unable-to-mount-samsung-android-in-ubuntu and it helped me get my phone properly recognized in Mint.
Click to expand...
Click to collapse
I'll give this a shot.
And thanks, but no amount of waiting brings it to debug mode if that's not in the cards. I just plugged it in, and on the first try it went into debug mode, but on subsequent plug-ins, it failed to recognize. Really odd behavior. I was beginning to think it a factory defect, but my buddy's phone also doesn't work, so it definitely seems to be Ubuntu.
Unfortunately, no luck on this. Adding device rules to either this file or 51-android don't work. I also find it incredibly strange that it is recognizing it ~1% of the time.
Just as clarification, I've made positive my maufacturer and device ids are correct. I managed to lsusb on one of the successful plugins and used those details to fill in entries in the rules files.
When I get home I'll fire up an Ubuntu distro and see if I have the same problem. When you plug the phone in and type "ls usb" does it show at all there?
dcorrea said:
When I get home I'll fire up an Ubuntu distro and see if I have the same problem. When you plug the phone in and type "ls usb" does it show at all there?
Click to expand...
Click to collapse
Thanks!
Only when I get the verifications that come with a successful attempt. A beep-boop, an android bug icon and usb icon at the top of the device, and a popup about my file-system. I ought to have copied the lsusb output here, because of course I can't get it to recognize now.
misterbreadcrum said:
Thanks!
Only when I get the verifications that come with a successful attempt. A beep-boop, an android bug icon and usb icon at the top of the device, and a popup about my file-system. I ought to have copied the lsusb output here, because of course I can't get it to recognize now.
Click to expand...
Click to collapse
I have Ubuntu 15.10 but it works fine with that. As soon as I plug my phone in, I get instant notification that its recognized on the phone, and then a few seconds later it mounts in Ubuntu. At this point it sounds like either a hardware problem like a bad USB cord, or some sort of corruption in your Distro. Have you considered running another Ubuntu distro off a LIveUSB to rule out the hardware?
Since you need to be in ptp mode, editing a udev rule for mtp recognition is not likely going to help, I think.
I would definitely check your cable, and even usb ports used. I just booted my 14.04 laptop, and it works exactly the same as in my 15.10 laptop and PC
claydoh said:
Since you need to be in ptp mode, editing a udev rule for mtp recognition is not likely going to help, I think.
I would definitely check your cable, and even usb ports used. I just booted my 14.04 laptop, and it works exactly the same as in my 15.10 laptop and PC
Click to expand...
Click to collapse
Yeah, I think I'm at the point where I've tried a different phone, different cable, different port, different computer, and the only thing that worked - different OS. My home desktop deploys test apps just fine, but I used the same Ubuntu Gnome 14.04 image for my other two computers.
I should try re-installing the drivers I guess.