Related
I have been doing Android development for a while on my work laptop that runs Windows Server 2003 64bit. Previously I've used a HTC Magic (AT&T) and a Moto Droid (Verizon) for development. Now I also have a EVO that I am trying to use. The problem is that I cannot get ADB to work with it.
System: Windows Server 2003 64 bit (work laptop, no I cannot put Windows <whatever else> on here).
Phone: EVO
Since I have been doing development for some time I already have the SDK, along with the USB drivers.
Here are things I have tried:
1. Plug in EVO. It wants to install ADB drivers. I choose the USB drivers location. Fails.
2. Delete USB Drivers. Redownload them from the SDK. Plug in, choose drivers, fail.
3. Plug in, allow drivers to fail, I have the ! in device manager for ADB. Unistall the ADB driver. Scan for hardware changes. Install ADB drivers. Fail.
4. Uninstall the Motorola USB Driver package. Try all above steps, fail.
5. Try to install HTC Sycn, Server 2003 not supported, fail.
What else can I try to get ADB working? Seems funny that it would work perfectly with a HTC Magic and a Droid but not this EVO.
Eureka! I found an obscure post on some crappy forum to a link for what someone called HTC Evo 64 bit drivers, so I thought what the hay, lets try them.
http://depositfiles.com/en/files/yd61xorii
The folder of drivers in there was really called Vista x86 but, still worth a shot.
It worked perfectly. The phone doesnt say ADB in device manager now but "My HTC". ADB is working fine.
Hopefully someone in the same boat as me will happen across this and it will save them time.
Thank you! Saved me a BUNCH of time! You're the man!
The file appears to be unavailable on that site now, could someone please re-host this ASAP? I can't get anything else to work and I'd really appreciate it if this turned out to be my fix. Thanks.
weidong said:
The file appears to be unavailable on that site now, could someone please re-host this ASAP? I can't get anything else to work and I'd really appreciate it if this turned out to be my fix. Thanks.
Click to expand...
Click to collapse
just grab HTC Sync from the HTC www site. It will install the drivers you need.
frankenstein\ said:
just grab HTC Sync from the HTC www site. It will install the drivers you need.
Click to expand...
Click to collapse
not always. I had to search for drivers for mine too. HTC Sync (latest rev on website) wouldn't work. Android SDK wouldn't work.
Still neeeeed help!
frankenstein\ said:
just grab HTC Sync from the HTC www site. It will install the drivers you need.
Click to expand...
Click to collapse
twin001 said:
not always. I had to search for drivers for mine too. HTC Sync (latest rev on website) wouldn't work. Android SDK wouldn't work.
Click to expand...
Click to collapse
downloadin HTC Sync made it worst. i had some htc evo drivers just not the ADB driver. After downloading now i don't have any drivers with my htc evo.
since i cant connect my evo to pc it will not automatically install the drivers!!!!!!
is there any way i can manually download the htc evo drivers to windows 7!
im back to normal i can read my sd card and i can connect to pc thank you all
bboy_201 said:
downloadin HTC Sync made it worst. i had some htc evo drivers just not the ADB driver. After downloading now i don't have any drivers with my htc evo.
im back to normal i can read my sd card and i can connect to pc thank you all
Click to expand...
Click to collapse
I can't connect on VMWare Fusion and Windows 7. How did you fix your problem? Did you find drivers? Thanks.
wow. never had a problem on windows 7 or ubuntu getting the evo to be recognized. but, head to work, plug it in, and no go. install the sdk and update it, no go. i was baffled, because i've never had a problem before. but, this file did the trick! thanks!
Unfortunately for those of us who are behind a proxy and can't get at the SDK file, going through the stupid SDK to get the driver is very annoying.
pcm2a said:
The folder of drivers in there was really called Vista x86 but, still worth a shot.
Click to expand...
Click to collapse
Didn't work for me. I'm running Deck's 4.0.3 ROM and can't get my device recognized on my computer. I tried to install the driver pack above through device manager and got an "unable to install" message. Any advice?
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??
Can anyone help me?
I'm running windows 8 64-bit, and I have an HTC One from VZW.
The phone is recognized via ADB, but whenever I get into the bootloader, it tells me the device isnt recognized and I can't do any fastboot commands with it. I was able to root and use fastboot on my N7 2013 from the same PC, so this is frustrating because I want to send my One in to sonic but if I can't DO anything when I s-off there's no point in sending it it.
If anyone can help I'd appreciate it.
Thanks
PS - I've only tried this PC, no others. It may work on my macbook but thats away for repair.
crazyg0od33 said:
Can anyone help me?
I'm running windows 8 64-bit, and I have an HTC One from VZW.
The phone is recognized via ADB, but whenever I get into the bootloader, it tells me the device isnt recognized and I can't do any fastboot commands with it. I was able to root and use fastboot on my N7 2013 from the same PC, so this is frustrating because I want to send my One in to sonic but if I can't DO anything when I s-off there's no point in sending it it.
If anyone can help I'd appreciate it.
Thanks
PS - I've only tried this PC, no others. It may work on my macbook but thats away for repair.
Click to expand...
Click to collapse
I would just install HTC Sync, sounds like it's a driver issue and HTC Sync will provide those needed new drivers for HTC.
andybones said:
I would just install HTC Sync, sounds like it's a driver issue and HTC Sync will provide those needed new drivers for HTC.
Click to expand...
Click to collapse
So just install and plug my phone in and the drivers will be installed?
Sent from my HTC6500LVW using Tapatalk 4
EDIT - that didnt do anything
Looks like I need to try something else...
crazyg0od33 said:
EDIT - that didnt do anything
Looks like I need to try something else...
Click to expand...
Click to collapse
sorry, thought I read it installed all the new drivers, you could try using Google to find the HTC current drivers, I can give you the numbers I have on mine my cpu is win 7 64bit not sure if it'll help but when in "uninstall or change a program" my HTC BMP USB Driver driver # is 1.0.5375
and my HTC Driver Installer driver # is 4.0.1.001
can't say it this helps at all but this is the CPU I used that I fixed the issue with
Best of luck!
andybones said:
sorry, thought I read it installed all the new drivers, you could try using Google to find the HTC current drivers, I can give you the numbers I have on mine my cpu is win 7 64bit not sure if it'll help but when in "uninstall or change a program" my HTC BMP USB Driver driver # is 1.0.5375
and my HTC Driver Installer driver # is 4.0.1.001
can't say it this helps at all but this is the CPU I used that I fixed the issue with
Best of luck!
Click to expand...
Click to collapse
My BMP is the same but my HTC Driver Installer is 4.0.3.001
Maybe I can find that other one and it will work for me
Here is a previous post I made to another guy having the same problem. Not sure if this will help but this is what I did.
I had this problem too running windows 8 x64. I think my problem was that I installed the sdk first with google's USB driver and not HTC's driver. What I did to make it work is switch computers over to my wifes which at the time I hadn't installed anything on yet. I went to htcdev.com and went to the part of the site where it is step-by-step on how to unlock the bootloader. I installed the Java Runtime Environment on the link provided on the upper right side of the site, then I installed the HTC sync manager on the link provided as well. I had my phone connected to my computer usb 2.0 (not usb 3.0) the whole time and with USB debugging enabled (not in fastboot mode, but with phone normally on). After that I took the three files from the sdk that htc wants you to place in a separate folder and put them in c:\Android. I did not install anything from sdk this go around.. i just took the three files out and put them in a separate folder as instructed by htc. After that I opened cmd and directed it to the folder I placed the files in (cd c:\Android) and ran command "adb reboot bootlader" Once I did that and hit fastboot the "My HTC" in device manager no longer had an exclamation point. So in summary, I couldn't reverse the drivers from my computer that I installed first so I resorted to using my wife's computer that didn't have anything installed yet. I installed JRE, then HTC sync software, and just used the 3 files HTC wants from sdk and placed them into a separate folder. I didn't install anything from sdk. It all worked after that. I don't have instructions on how to reverse the usb drivers you have already installed because I couldn't figure it out... in fact, I formatted windows on my pc and am reinstalling. Hope this helps.
-eL
eL_777 said:
Here is a previous post I made to another guy having the same problem. Not sure if this will help but this is what I did.
-snip-
-eL
Click to expand...
Click to collapse
Yeah I'm going to try it out on my roommates laptop that only has samsung drivers and the ADB installed and see what happens. Can't reformat the PC cause it's my School desktop and I've got work on there.
Once my macbook pro comes back from repairs I'll use that though, since I've never had issues running adb commands on my mac
Found a soultion
After I tried almost everything I tried to improvise and try something totally different and it worked!
First uninstall the driver in the Device Manger and then press to update it >> then press Browse my Computer for driver Software >> then press on Let me pick from list.... >> in the list choose the Portable Devices >> choose MPT USB Drive !
And It works...
:good:
gald said:
After I tried almost everything I tried to improvise and try something totally different and it worked!
First uninstall the driver in the Device Manger and then press to update it >> then press Browse my Computer for driver Software >> then press on Let me pick from list.... >> in the list choose the Portable Devices >> choose MPT USB Drive !
And It works...
:good:
Click to expand...
Click to collapse
MPT USB Drive isnt one of my options
However I've found that it's microsofts USB3 drivers, which override the Intel ones.
I just got my macbook back from repairs and it has USB3 ports as well so I was worried it wouldnt work, but its working fine from there
I'm having this same problem and nothing I do is working. I even tried from another computer but had no luck. adb finds the phone fine but fastboot just won't work. This is keeping me from getting S-Off. Someone please help.
Edit: Nevermind I think the issue is that I'm using Windows 8.1
I'm having the same problem I'm windows 8 64bit...
I have a nagging feeling that it's pda net.. I need to look into it today sometime
Sent from my HTC6500LVW using xda app-developers app
I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Silent Assasin said:
I followed the instruction for this link. (http://forum.xda-developers.com/showthread.php?t=1347321) Everything was going well. Now I can't get out of mini pooploader. I searched around and was suggested from other peoples issues that I need to install the drivers. I manually installed the drivers, supplied in the link and Windows 7 states that the drivers I have are up to date. DO I need to go to HTC and find there drivers (Which are windows based or find android drivers)
I recently upgraded my XOOM to KIT KAT and am happy with it. I had fast boot and ADB installed for that project. Is that what the problem is? I have co-mingled the downloads for the NAND install with the KIT KAT ADT Bundle?
I have no problem running ADB and seeing SDK recognize the commands. When I try Fastboot commands I get waiting for device messages. Can someone please point me in the right direction. I know this is an old thread and Im hoping someone will be having so much fun this holiday weekend that they'll hop online and help. I hope this use the phone in conjunction with the updated Xoom.
Oh yeah, Thanks to all the VETS out there
Click to expand...
Click to collapse
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
wizardknight said:
Try this guide. Lot newer.
http://forum.xda-developers.com/showthread.php?t=2049567
Click to expand...
Click to collapse
Thanks for replying. That's the guide I was using. I can't get into fastboot. ADB commands work. I tried to manually install the drivers (On the computer). Windows 7 says my drivers are up to date. I can't move forward out of mini pooploader (funny name by the way). Any ideas would be appreciated...
I meant to say that I found that thread after being stuck in mini poop mode.
9. Turn the phone back on. You should see a blue miniPooploader screen with a lot of white text scrolling for a moment. When it gets done, pull the battery to shut it off. Then replace the battery (it should still be off)
10. Connect the usb cable between the phone and the PC, and turn the phone on. The PC should see the device, and may or may not assign drivers to it.
Click to expand...
Click to collapse
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
plrusek said:
have you done this part? when you do the 10th one, your phone should get a black screen and a driver should be automatically installed by windows 7. for me - the driver was HTC Bootloader. after this, i installed the fastboot driver. more specific - the driver in the ADB_fastboot folder. after that - it went smooth.
Click to expand...
Click to collapse
I followed your advice. I let mini pooploader run the blue screen with white letters. Once finished, I removed the battery, placed the battery back in and then plugged usb into computer. I then powered the phone up with the same results. I performed this task 11 times with the same results. No black screen and no win 7 driver install. The computer says unknown device. I have tried to install drivers and computers states the drivers are up to date. I have tried different USB ports. I have attempted to install HTC drivers someone posed in this forum as well as the drivers that come with SDK with negative results. I have tried to uninstall the drivers in hopes that windows would install upon recognizing device with no luck.
Any ideas? I really need to get this working. i have not had a phone for a week now
After going through a replacement process (twice) after cracking the screen on my first device, I was relieved to find that the replacement I got sent wasn't updated to un-moddable status. However, after using rumrunner to s-off, flashing cwm 6.0.4.8 recovery, and using that to install cm11 m6 snapshot, I was disappointed to find that my phone will not connect to Windows in a manner where I can access USB storage. Enabling debugging in dev options does initiate the "device plugin sound" from Windows, but after looking in device manager, all that shows up there is "Android ADB Interface". When debugging is disabled, Windows makes no sounds, and there is nothing in the device manager. The only response i'm receiving is that the charge light on the device comes on. I would try to install drivers, but seeing as the computer doesn't even recognize that a device is plugged in, i'm pretty much halted on that front. Any comments or solutions would be greatly appreciated.
Cheers!
StaticSpark said:
After going through a replacement process (twice) after cracking the screen on my first device, I was relieved to find that the replacement I got sent wasn't updated to un-moddable status. However, after using rumrunner to s-off, flashing cwm 6.0.4.8 recovery, and using that to install cm11 m6 snapshot, I was disappointed to find that my phone will not connect to Windows in a manner where I can access USB storage. Enabling debugging in dev options does initiate the "device plugin sound" from Windows, but after looking in device manager, all that shows up there is "Android ADB Interface". When debugging is disabled, Windows makes no sounds, and there is nothing in the device manager. The only response i'm receiving is that the charge light on the device comes on. I would try to install drivers, but seeing as the computer doesn't even recognize that a device is plugged in, i'm pretty much halted on that front. Any comments or solutions would be greatly appreciated.
Cheers!
Click to expand...
Click to collapse
try a different USB port?
also, uninstall HTC drivers. reboot the pc then install the drivers again should fix this.
synisterwolf said:
try a different USB port?
also, uninstall HTC drivers. reboot the pc then install the drivers again should fix this.
Click to expand...
Click to collapse
Unfortunately, as the computer doesn't even react at all when I plug in the device, I can't manipulate drivers at all. That means no uninstalling or installing :/
StaticSpark said:
Unfortunately, as the computer doesn't even react at all when I plug in the device, I can't manipulate drivers at all. That means no uninstalling or installing :/
Click to expand...
Click to collapse
which windows are you on?
also HTC driver was an EXE file so you should be able to find in the uninstall program portion of windows.
synisterwolf said:
which windows are you on?
also HTC driver was an EXE file so you should be able to find in the uninstall program portion of windows.
Click to expand...
Click to collapse
Windows 7. But I never used HTC Sync or anything like that. I didn't install any exe's for drivers
StaticSpark said:
Windows 7. But I never used HTC Sync or anything like that. I didn't install any exe's for drivers
Click to expand...
Click to collapse
ah okay, install sync manager:
http://www.htc.com/us/software/htc-sync-manager/
once the windows sees the phone. feel free to remove the sync portion of the install and keep the driver installer on the pc.
this should fix it and wont mess with ADB or fastboot.
Hehe, thanks. I guess I'm just a little paranoid about having junky, manufacturer specific software on my pc. Will see if this works.
StaticSpark said:
Hehe, thanks. I guess I'm just a little paranoid about having junky, manufacturer specific software on my pc. Will see if this works.
Click to expand...
Click to collapse
me too. :/ but i found that this was the less headache way for me. sync and drivers will show up as 2 different installers. i deleted sync and kept the drivers. im sure one can uninstall the driver installer part of htc software and windows will keep the ini file intact but i never tried this.
synisterwolf said:
me too. :/ but i found that this was the less headache way for me. sync and drivers will show up as 2 different installers. i deleted sync and kept the drivers. im sure one can uninstall the driver installer part of htc software and windows will keep the ini file intact but i never tried this.
Click to expand...
Click to collapse
Thanks for your input! Turns out, i'm an idiot. I had to enable MTP in the usb connection settings >.<
StaticSpark said:
Hehe, thanks. I guess I'm just a little paranoid about having junky, manufacturer specific software on my pc. Will see if this works.
Click to expand...
Click to collapse
Your worried about junky software and you run windows
Glad to see you got everything worked out mate