Develop Bugs

[Q] ADB & USB Connection

Bloody Hell i still cant get work any usb connection from my Kaiser to my PC.. Im using W7 x64.. i think its biggest problem (x64)
and please, any manual how to get work ADB commands? step-by-step for newbies

I listed this problem to the issues list:
http://forum.xda-developers.com/showthread.php?t=748717
I have not been able to use ADB since Donut or so!

SuperJMN said:
I listed this problem to the issues list:
http://forum.xda-developers.com/showthread.php?t=748717
I have not been able to use ADB since Donut or so!
Click to expand...
Click to collapse
sry but you have ther only polaris.. add there kaiser please too

There are no windows drivers AFAIK, that's why it won't work...
I read somewhere about someone being able to do it on Ubuntu. I'm not sure about it though. I removed Ubuntu from my laptop couple of months ago and can't test ADB now.
I tried a lot with Win 7 32bit - for about a week, but no luck
If you want to copy files, just remove the SD card and use a card reader. Or you can enable recovery mode then the card will be readable in windows.

i have better think than remove SDCard.. i have FTP Server on my phone, and im connecting on it through Wi-Fi. Its pretty fast
And i have access on full /
on /system + sdcard
its faster than hacking through terminal

[Q] EVO Unrecognized - WTF??

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??

A possible alternative for MTP (on Windows): an adb-provider for Windows powershell

Posting this in the Galaxy Nexus forums, since this seems to be one of the few devices which right now has no mass-storage mode.
Everyone seems to hate on MTP, for both the right and the wrong reasons.
With MTP not really being very accessible from the command-line, I find myself using "adb shell ls", "adb push" and "adb pull" quite a lot. It works out OK, but it's not very fluent, especially for batch operations.
So I want something which does batch-operations fluently too. And since I know .NET, I figured a Powershell-provider should be doable.
I envision you should be able to do something like the following:
Code:
Windows PowerShell
Copyright (C) 2009 Microsoft Corporation. All rights reserved.
PS C:\Users\josteink> cd ADB:
PS ADB:> copy \sdcard\*.* C:\backup\
etc.
So before I start wasting my time on this, I figured I'd poll the mood. Is anyone else interested in this, or is the Windows-crowd already feeling comfy with the tools they have?

I'm comfortable with the regular tools i have, and MTP is working fine for me.

A few may want it because of the issues that they have with MTP. Personally I prefer MTP over mass storage.

I think it would be a very cool experiment. The idea of getting access to files on my device opens up some neat scripting possibilities! My stupid Xoom also uses MTP.
Sent from my Galaxy Nexus using xda premium

im having some trouble installing the MTP driver for my galaxy nexus on Win XP
I tried PDANet for the phone driver but I can't seem to get the MTP to work properly on XP, n i couldnt find any driver for MTP. On the other hand, the driver installed itself on my other platform thats running Win7...

I just use adb with the push and pull statements as I always have. I never really used MTP or USB or whatever back in the days with my OG. I'm fairly certain however that the average user would not use adb however! (nor would they be on xda however!)

MTP works well enough on Windows and even on osx. Whenever I do use command line its fairly simple and batching commands up as needed is also simple enough.
I'm not sure there's huge value in another way to transfer on windows, but if its something you need, then just do it.
I think a more useful project might be a file manager that uses adb instead of mtp. You could add shell extensions to it too. Something like that would have a lot more broad appeal.

It's already been done: Droid Explorer
http://de.codeplex.com/

pascanu said:
It's already been done: Droid Explorer
http://de.codeplex.com/
Click to expand...
Click to collapse
Nice, but windows only again :/
MTP works well enough on windows, and support will probably only get better. Its other platforms that are a pain.

If you want, you can use AirDroid to manipulate your files on a Wifi Network!

jairmoreno said:
If you want, you can use AirDroid to manipulate your files on a Wifi Network!
Click to expand...
Click to collapse
I use AirDroid for media files. those non-media files or large data files, I prefer WiFi File Explorer PRO, which is better than AirDroid.

mingtaoh said:
im having some trouble installing the MTP driver for my galaxy nexus on Win XP
I tried PDANet for the phone driver but I can't seem to get the MTP to work properly on XP, n i couldnt find any driver for MTP. On the other hand, the driver installed itself on my other platform thats running Win7...
Click to expand...
Click to collapse
Do you have WMP12 installed?
I had a hard time finding XP driver for GN, and I once read somewhere that WMP12 includes the driver needed
I installed it then plugged in my GN, and after loading for a while XP recognized it as a MTP device and I can move files to and from GN
Hope it works for you
Sent from my Galaxy Nexus using Tapatalk

Not done yet, not by any means, but I have started.
Following is a screenshot of actual running code
The syntax will become better after a while. Just for now I'm working on bolting the technical bits together and learning how Powershell components are built

momomok said:
Do you have WMP12 installed?
I had a hard time finding XP driver for GN, and I once read somewhere that WMP12 includes the driver needed
I installed it then plugged in my GN, and after loading for a while XP recognized it as a MTP device and I can move files to and from GN
Hope it works for you
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
I'm using winxp so I dont think I can install WMP12, but I have WMP 11 installed should I uninstall and reinstall it again?

Still quite a bit of way to go, but at least now "Get-item" parses stuff 100% correctly, and I have "ls" working too

After a bit more work (and learning some more powershell)
I now have rooted devices like (SDCARD) working correctly as well
Edit: It seems rooted devices act a bit wonky and should be looked into, but now I can add CD to the list of things working too.

So im guessing this is the reason i cant access my backed up apks on my sd card?

xzombiex66 said:
So im guessing this is the reason i cant access my backed up apks on my sd card?
Click to expand...
Click to collapse
Yeah. That doesn't work over MTP.

Post moved to new thread

Jumped in on this late-- looks like you decided to go forward -- I think there is a need for a powershell provider for MTP. ADB can get information to/from the device, but not in any way that powershell likes... It would be great to have the MTP system mountable as a psdrive. You can 'adb shell ls /sdcard/... ' but what you get back has to be captured and parsed. It's frustrating that MTP is a file system that can be browsed graphically but not as a true file system available to the entire OS (and the command line/powershell). Although I'm getting the impression from my reading elsewhere that the storage is entirely ext fs and Windows has never played nice with Linux-ish file systems.

Win7 64bit pc does not Recognize A100 tab

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.

[Q] Android Device not recognized / MTP ADB driver problem

I'm about at my wit's end with this. Just for information sake I'm running Cyanogenmod10 on an Incredible 2.
Recently, about a week ago, I "removed" Windows Media Player from my Windows 7 services menu (because it's a piece of **** and I use MPC-HC), and didn't notice anything wrong until I tried to sync my Incredible 2 with Mediamonkey again to update my music collection and found that it wouldn't recognized the Android device.
After ****ing around with my drivers in device manager for a bit and doing some Google searches to try and figure out what the problem was, I came across the idea that it might be something with WMP and how it has MTP drivers installed that Mediamonkey needs to see the Android device in its program. This was confirmed on the MM wiki. So I re-allowed WMP via Windows service features and it still wouldn't recognize the device.
I've tried everything short of a fresh install and nothing works. Tried updating the ADB drivers, that didn't work. Tried deleting them and installing them manually, that didn't work. Tried downloading and installing the next version of WMP to see if that would refresh whatever drivers I needed, and get told that the "update doesn't apply to my computer". Tried installing the Android SDK toolkit to see if I could manually install the drivers without using device manager and that didn't seem to work either. Even tried installing the ****ty proprietary HTC Sync bloatware from HTC's website to see if that would give me the drivers I needed.
Then I tried backing up my phone data, doing a clean wipe of my phone through recovery, and putting stock Android on my phone to see if I could install the necessary MTP notification drivers from my phone onto my computer that way after I idiotically deleted them from device manager. The installer tells me it fails every time I try to connect the Incredible to my computer via USB. Currently I restored my CM10 installation and can't figure out what to do.
Now I have a royal cluster**** of things that may or may not work and I still can't get MM or WMP to recognize the device.

Um...I just drag my music into the music folder in explorer and that works fine..try that?
sent from my paranoid android

JehC said:
Um...I just drag my music into the music folder in explorer and that works fine..try that?
sent from my paranoid android
Click to expand...
Click to collapse
Because I have a rather large music library and Mediamonkey makes it incredibly easy to manage it. If I just transferred files over manually then I wouldn't be able to manage my library effectively; using MM allows me to make changes in the program that effects my native music library and then quickly sync with my phone, and syncing takes less than a minute.
Basically I'm trying to get MTP functionality back, I'm sure it has something to do with disabling Windows Media Player but even after re-enabling it on my PC I still can't get MM or WMP to recognize my device.

Try a different computer

I'm on the same boat. I plugged in my phone to my computer for the first time in a while and my computer would give me "usb not responding" message and my phone doesn't display anything, it doesn't come up with adb devices either. Any ideas?
Sent from my Incredible 2 using Tapatalk 2 Beta-5

9zeronine said:
Try a different computer
Click to expand...
Click to collapse
Took this advice and it turns out when I connect my phone to another computer running MM it recognizes it.
Which means I can only assume it was a problem around disabling and reenabling WMP on my computer messing with the MTP functionality on my laptop.
So I guess my next question would be, how to do a full reinstall of WMP / Windows Media Features? There's really not a way to do it that I know of because you can't really uninstall WMP from Windows (thanks Microsoft), you can only disable it, and it's obvious that re-enabling it did nothing to fix or mitigate the problem.

alaminion said:
Took this advice and it turns out when I connect my phone to another computer running MM it recognizes it.
Which means I can only assume it was a problem around disabling and reenabling WMP on my computer messing with the MTP functionality on my laptop.
So I guess my next question would be, how to do a full reinstall of WMP / Windows Media Features? There's really not a way to do it that I know of because you can't really uninstall WMP from Windows (thanks Microsoft), you can only disable it, and it's obvious that re-enabling it did nothing to fix or mitigate the problem.
Click to expand...
Click to collapse
It sounds like the drivers for your phone have been damaged by the WMP disable. I'm not sure why that would be, but perhaps reinstalling them will fix it.

k1mu said:
It sounds like the drivers for your phone have been damaged by the WMP disable. I'm not sure why that would be, but perhaps reinstalling them will fix it.
Click to expand...
Click to collapse
The phone / Windows 7 keep failing to reinstall the drivers automatically and HTC doesn't give out the individual drivers for people to install manually.