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??
Hi guys i've got some issues i'm hoping someone might be able to advise me with.
I'm running a Windows7 in a VirtualBox installed on OSX and i'm unable to get it to recognize the phone.
I'm currently stuck at fastboot so when the phone is connected i see a new device called Fastboot with the flag that "needs troubleshooting".
After trying to troubleshoot and reinstall the drivers, it sais that the driver installation failed.
Does anyone know a way around this?
Thanks in advance,
-Miro
SOLVED:
As it turns out VirtualBox needs an expantion pack found here to recognize usb ports as USB 2.0
Hopefully this can help someone else using a mac and troubleshooting there phones on a Windows VM
Hey guys, I have been trying to get Windows 7 Drivers to work properly with adb on my A100. I have a Virtual Machine of Windows 7 and I have manually added the USB device ID's to the VBox settings for the VM client, Windows 7 sees the device ok and will mount the device fine via MTP. I can even get the drivers to say that they are working properly for the device, but when it all comes down to it they aren't.
I have tried using the ADB driver from the Android SDK which of course won't work out of the box since the device ID's aren't made for the Iconia A100, however I modified them to match the vendor/device IDs, but still - no go. I can do ' adb devices' and it will either show the device as offline or will just say the name and serial#, but when I try to connect it either says 'device offline' or it will give me a adb protocol error.
I don't know what else to really try, and at this point I am really thinking Virtualbox isn't passing the USB properly to the Guest OS, but what is odd, is my HTC WildFire S will work fine with adb (same binary).
I have also tried the Acer drivers that are available on the Acer Website, as well as a few other device drivers that I can't recall off the top of my head.
I guess some people are wondering if this is working in Linux why am I so concerned about getting it to work in a Virtual Machine running Windows. In short the answer is: I am developing kernels and recovery for the A100 as many may already know, and I am working on some automated installers that are cross platform compatible and I need to test the Windows side of things before I make releases, yet it's a bit hard to do when Windows is such a PITA when it comes to anything Android.. Yea, I'm a Linux person I know it's obvious - but I need this working somehow in a Virtual Machine because I'm not willing to do a native install of Windows on any of my machines, simple as that lol..
Anyone who may have a Virtualbox install of Windows 7 (or vista) that has adb working with their A100, please let me know the adb drivers you used and if at all possible attach them here, or give me a direct link. I greatly appreciate the help guys!
Here is a snippet of the troubles:
Code:
List of devices attached
037c624643a033d7 device
C:\Users\Lance\Downloads\godmachine81-Acer-A100-TWRP-Installer\godmachine81-Acer
-A100-TWRP-Installer-c8ccd42>adb shell
error: protocol fault (status 72 6f 6f 74?!)
**Edit: I kinda found a solution to my own problem, but not a great one. The problem was with EHCI 2.0 in VirtualBox, when this setting is disabled it will allow adb to work correctly, however on Windows 7 it will break the USB host so there is no possible way to use the tablet period, with Windows XP however it works fine. Windows XP has the exact same issue, but the USB Hub will actually work without EHCI 2.0, not really sure if there is a workaround to the Windows 7 problem, but I didn't really mess with it long - I'd say one might be able to uninstall the USB adapter and reinstall it after disabling EHCI and then also reinstall the Acer drivers. I got tired of fooling with windows 7 and just installed a copy of XP, wrote the batch script for windows, and will soon be uninstalling most likely haha.. Hope this might be some good info for others who run into a similar issue
Pretty straightforward question. I'm looking at going from a Windows laptop to a macbook and want to make sure some of the programs I use frequently work. Will Odin work via Windows on a Mac? Thanks.
Anyone? Really want to pull the trigger on this MBP, but want to ensure I can still tinker with my android devices...
i just used Odin and it would not work on my MBP with Parallels Win 7. I had to drag out my PC and then Odin worked fine
red321red321 said:
i just used Odin and it would not work on my MBP with Parallels Win 7. I had to drag out my PC and then Odin worked fine
Click to expand...
Click to collapse
How about boot camp? Do you think the issue has to do with drivers? Not familiar with Mac OS yet... My current laptop is the only windows machine I own and don't want to get rid of it in lieu of the MBP in case some of my programs don't work...
Haven't tried boot camp
Sent from my SM-P600 using XDA Premium HD app
Sent via PM, but finally realized why it wasn't posting in the forum (links)
...So posting here since someone else may need/want this at some point:
1) You'll want vmware fusion; there's a trial. You can easily install and uninstall it on a mac if you don't want to pay. Vbox and parallels won't work.
2) You'll need the Samsung USB drivers for phones exe from Samsung's website. You'll probably also want to separately get the Kies binaries (both windows bins).
3) MS offers pre-made VMs in virtualbox format (ova's); these aren't activated and expire in 30 days, but will still sorta work after that (they'll shut down after about 30-60mins after that point). Easy enough to just reimport; not sure how often you plan on using Odin. Kies itself is generally ok on a mac, but nothing else is (aside from like graphics-tab apps, and generic usb file stuff). You'll want to get Win7 vm images. These should work but if not you can google; MS doesn't make a secret of their VMs, they're made for developers to check compatibility between different versions of IE. Get all of these and then decompress, and you'll get an .ova file (links to Win7-IE10 VM archive files removed as I don't have 10 posts yet).
4) In VMware Fusion, you'll want to import the .ova file (.ova's are technically virtualbox images, but vmware will easily convert them to its own format). Once you've imported it go into the VM's settings and allocate 2gb of ram or so to the VM (I wouldn't go much below that; if you have a later mac that shouldn't be a problem; you might be able to get by on 1.5gb though I haven't tried). You'll also want to go into the vmware usb settings and make sure to be prompted when you add a device instead of just attaching it to one or the other or you'll wind up with issues, possibly, later on.
5) Boot the Win7 vm, install VMware tools, reboot, install samsung drivers, and then install Kies if you want Kies as well (Kies may also bridge some driver gaps, I can't remember; I do remember I had a bit of trouble with correct device recognition; I'll keep an eye on this thread and if you have a problem post publicly and I can message you with the proper driver set otherwise this should work afair); the problem, if I recall, was in detecting the specific USB devices/hub, if anything. DO NOT plug in your tablet until all of these drivers have been installed and you have rebooted the VM. You've been warned.
6) Boot the VM, plug the cable into the tablet, and then the other end into the Mac. If you've set up the USB prompting properly (btw make sure you set it to 2.0 not 3.0), you should get a prompt asking if you want to attach it to the Mac or Windows; choose Windows. The drivers should do there thing in a few minutes and eventually recognize the tablet. You may or may not want to reboot the VM one last time at this point before opening Odin, but at this point it should all work.
* A note: you'll probably want to enable a shared folder via VMware with the contents of anything you want to flash and the exes to flash them with; this is pretty straightforward in the VM settings. You'll want to copy/paste from that shared folder to the VM, not run from it; Odin and other stuff tends to hang if you try to run it directly from the share. I just keep everything I need or might want to use in the future on the VM and suspend it til I need it again, but you can just as easily shut it down and it'll retain all of the data, etc; just be mindful of the 30 day limit if you're using one of the precompiled VMs (as I said, they'll still work, but it can get naggy and shut itself down if not in use (or maybe if it is, but I haven't had it bomb out on me mid-flash (yet, knock wood)).
Good luck and enjoy.
not a single problem with parallels windows 8 or xp. while i flash 4.4.2 via odin i surf the web on mac safari.
supremekizzle said:
Pretty straightforward question. I'm looking at going from a Windows laptop to a macbook and want to make sure some of the programs I use frequently work. Will Odin work via Windows on a Mac? Thanks.
Click to expand...
Click to collapse
VMware should do.
It works very well on Linux.
That's interesting...
jpl69 said:
not a single problem with parallels windows 8 or xp. while i flash 4.4.2 via odin i surf the web on mac safari.
Click to expand...
Click to collapse
Mind if I ask what release of OSX and hardware you're on? I know I was having some USB recognition problems with the other two, but that was 2 point releases ago on Mavericks (on 10.9.3 now, haven't tried again). It could be a MBP thing also. I wouldn't mind using Parallels (I have a licensed copy) if it worked for this; as it stands I use parallels for OSX, vbox for *nix and android, and vmware for windows OSes for various reasons.
Macbook Pro 13.3 2012. Mavericks updated, parallels updated with latest version. Windows 8.1 work fine with odin, but i use mainly windows xp. both configure with usb 3.0 driver.
12GB ram, 512GB SSD samsung evo (this is just for show off not relevant to update our tablet) .
i used vmware sideways with parallels but find that parallels it's more faster, reliable and more crash proof.
after you connect the tablet to mac you get the option to connect to mac or virtual machine. afterwards you allways have the option to connect/disconect the usb periferic.
rsd2000 said:
VMware should do. It works very well on Linux.
Click to expand...
Click to collapse
That's what I use; until Ben Dobell can fix Heimdall for Linux for the P60X series I've just been booting into Win7 via VMWare from my Linux machine.
jpl69 said:
Macbook Pro 13.3 2012. Mavericks updated, parallels updated with latest version. Windows 8.1 work fine with odin, but i use mainly windows xp. both configure with usb 3.0 driver.
12GB ram, 512GB SSD samsung evo (this is just for show off not relevant to update our tablet) .
i used vmware sideways with parallels but find that parallels it's more faster, reliable and more crash proof.
after you connect the tablet to mac you get the option to connect to mac or virtual machine. afterwards you allways have the option to connect/disconect the usb periferic.
Click to expand...
Click to collapse
I'm on a late 2013 13.3 MBP. I think back when I was trying to debug the problem I'd read that USB 3.0 and how it's handled on the latest MB might have something to do with it, but I can't recall correctly. I should probably retry just for sh*ts and giggles; was always on the most recent Parallels, VMware, and VirtualBox. That said, I've found VMware in general to be more stable on my particular machine, and quicker to boot/suspend/unsuspend. It could very well just be my imagination or preference though, nosing its way in.
And talking about hardware is never showing off, as long as you're making good use of it. OS wars, however, is another story.
Let me start off with the basics...
Nexus 7 (2013) - Stock Rooted 5.0.2
Variant: flo 16G
HW Version: rev_e
Bootloader Version: FLO-04.04
Tried MTP on/off - Doesn't work
Tried USB Dev on/off - Doesn't work
Tried on Windows 7/8.1 - Doesn't work
Tried on Ubuntu 14.04/14.10/Linux Mint 17/17.1 - Doesn't work
EVERYTHING WORKS on Mac OSX Maveric and Yosemite!!!
MTP and ADB and Fastboot do not work at all. In linux, lsusb shows nothing. In Windows, Device manager shows no changes (also, never plugged it in before this and followed Wug's toolkit howto exactly).
When I plug the device into my girlfriend's MacBook Pro (10.10 Yosemite as well as when she was on Maverics) everything works. On her Mac, ADB works, Fastboot works, and MTP (using the android transfer tool) works flawlessly. This is using the same exact USB cable that I used on all other systems. I tried this on my Linux laptop and a Windows desktop. Triend all USB ports. It seems my tablet will only work with a Mac.
Any ideas??
Does the laptop or desktop recognize the tablet? Is the Android SDK up to date?
I don't use the full SDK. I use android-tools-adb and android-tools-fastboot which is a cross platform toolset. This works for 2 of my phones, my ouya, and her phone so I know its just the tablet. The 3 phones and the ouya work on the windows desktop and laptop but not my tablet. As soon as I plug the tablet into her Mac, it is detected right away. I really wish I can solve this... I hate taking her MacBook from her every time I want to tinker with things.