I am seriously thinking about going to x64 and I need to know if the drivers exist for QPST and the HTC modem driver to have ESPT (on the phone) and QPST (on the computer) talk to each other.
If someone would be as nice to give me some URL's for that driver, it would be nice.
And if the standard QPST won't function on a 64bit OS, is there a version that will?
Also, will BuildOS function on x64?
I have been using computers since I was 8 years old and now I am 32, I feel like an ass for not knowing this, so please be kind in your flamings...
Yes, both work on Vista x64. Make sure to run the applications as Administrator.
Use this file for the HTC Modem drivers required by QPST:
http://www.vzam.net/uploadedfiles/WModemDriverInstaller.exe
It will install the x64 drivers automatically. Then put your phone into diagnostic mode, connect via USB, and shazam!
Related
Hi,
I know there have been threads on this before but largely they just mention installing the Vista 64 bit drivers (done that). I'm running Windows 7 64 bit with the Vista 64 bit drivers and MCR 2.8 (although I was on stock and 2.2 with the same problem). HTC Sync on the phone just will not find it on the PC. I can mount the SD card with no trouble, just problems with Sync.
Any suggestions as to what I can do? Please feel free to direct me to another thread that I've missed so long as it's not just about the drivers.
Ta
M
martint235 said:
Hi,
I know there have been threads on this before but largely they just mention installing the Vista 64 bit drivers (done that). I'm running Windows 7 64 bit with the Vista 64 bit drivers and MCR 2.8 (although I was on stock and 2.2 with the same problem). HTC Sync on the phone just will not find it on the PC. I can mount the SD card with no trouble, just problems with Sync.
Any suggestions as to what I can do? Please feel free to direct me to another thread that I've missed so long as it's not just about the drivers.
Ta
M
Click to expand...
Click to collapse
In addition to HTC sync and the drivers, have you tried getting the android sdk? I know that I had issues with HTC sync finding my phone as well when syncing it to Win7 x64, so try following this guide here, it might allow HTC sync to view the phone properly. The guide teaches you how to setup adb-usb drivers which might trigger the application to know that your phone is there.
I had the same problem, turns out one of the task killer apps that I had been using had killed the sync process. Might be a plan to check if the same has happend to you.
Florida.
Hi Princedwi and Florida,
Thanks for the replies. I'm confident that my sync process is still running as I've tried numerous reboots of phone and PC so the task killer wouldn't have had chance to stop the process. However I will give it a go just to make sure.
Regarding the SDK, I'll try that when I get home. I used to have the SDK installed but then I did a re-install of windows and haven't bothered installing the sdk yet. May well work, I'll let you know.
Ta
M
Hi,
Ok tried it at home. The SDK isn't installing in the same way as I remember it doing last time. A DOS box flashes up and then disappears when I run SDK setup.exe.
Any other ideas?
Ta
M
2.0.18 is out now... should be W7 compatible -
http://www.htc.com/europe/SupportViewNews.aspx?dl_id=847&news_id=471
I had to install the Vista 64 bits drivers twice to get them working properly. The first time my hero appeared as "HTC Hero ADB". Rebooted, connected to USB, opened notifier, selected PC-Sync and reinstalled drivers (always choosing the folder where HTC should be leaving their drivers). This second time it appeared as "MY HTC" and it worked fine then. So just try again until you see the magic word "My HTC".
yrreP said:
2.0.18 is out now... should be W7 compatible -
http://www.htc.com/europe/SupportViewNews.aspx?dl_id=847&news_id=471
Click to expand...
Click to collapse
I've installed it today on my 7 64bit ultimate installation, and still no avail, i installed the vista x64 drivers and it worked.
Gr. B
martint235 said:
The SDK isn't installing in the same way as I remember it doing last time.
Click to expand...
Click to collapse
Because from android 1.6 setup process has changed in SDK. Normally it opens a windows from where you can add the version of android SDK you want and install the driver.
martint235 said:
A DOS box flashes up and then disappears when I run SDK setup.exe.
Click to expand...
Click to collapse
Same problem here with windows 7 64bit. Not sure if it's related to java environnement installed (For example when i installed JRE on my win7 64 the JAVA_HOME env variable was not set, i had to do it manually).
martint235 said:
Any other ideas?
Click to expand...
Click to collapse
Nope for now but if I found the problem be sure i'll post it here.
Ok I found the solution. My problem is that I've installed only the JRE but according to the requirements (developer.android.com/intl/fr/sdk/requirements.html) we need the JDK also.
So i've uninstalled the JRE 1.6 (64bit) I had, and installed the JDK 1.6 (32bit as i saw many ppl having problem with 64bit and android SDK). And it worked, I run againg the "SDK Setup.exe" and it opened the windows as intended.
I had the same problem, even with 2.0.18. what I did was install HTC Sync 2.0.18 (with the drivers copied in Program Files\HTC\HTC Driver\Vista_x64). then go to device manager, ADB interface, update driver, browse for a list of compatible software and choose My HTC.
after rooting it (although I'm not sure this is the cause) it happened now and then to fail to get recognized by the computer so I followed the same steps to update the drivers to My HTC.
I can't install HTC Sync 2.0.18, it gives an error about some resource file not found and closes. I tried on two different computers with the same result. Anyway 2.0.8 works fine here after I reinstalled the 64 bits driver until it was detected as "My HTC".
the same for me.
after update to version 2.0.18 my win7 64bit didnt find my phone anymore...
My computer keeps popping up finding new hardware when I ##3424# to go into DM mode.
I have activesync and htcsync, as well as the drivers that work up to the touch pro as well.
Give me a few minutes, I'll look into it. You might have just hit something big (from what i've seen of this so far)
You may have just found a gaping hole that could be some fun. Can't say much more, but i'll post back with some updates if this means anything.
They are attached. I modded some other drivers I found earlier. Simply, download and install :
http://www.vzam.net/uploadedfiles/WModemDriverInstaller.exe
Run specified 32bit/64bit installer, grab files out of %TEMP%, change value "0b03" to "0c08". Update driver for phone from task manager with that drivers folder. 32-bit modded drivers attached. I don't know how to talk to HTC DIag though.
Could someone try this on unix/linux? I don't have a working box (just sold my eee) Hopefully the drivers install and you get something. Looks like possibly a modem though.
http://www.mediafire.com/?ondwg2xiwyy
PS - if this file is agains the rules, can a mod remove it? Thanks!
32 bit drivers work
Drivers work with 32 bit windows 7 if you edit the USB device ID in the files, I haven't been able to do anything of interest with it yet aside from read from the phone using QPST and QXDM, it needs to be CID'd to do anything of use, I have no idea how to go about doing it with an andriod based device.... any suggestions?
The Hero drivers work great.
Just download the Hero drivers. Then use the latest version of QPST, with ##DIAG#.
Works great. You probably don't need to go through all of that other pain to accomplish the same goal. Good find though.
So is this a dead end?
Hey, I was wondering if anyone had a link to download the HTC Bootloader drivers. It fails when I try and load "something" in Windows.
Thanks.
p.s: This will lead to good things...
The only drivers that I am aware of are the ones that are in the Android SDK Toolbox and in the HTC Sync program. Correct me if I am wrong, but as far as I know, they aren't specific drivers ie "bootloader" drivers. They are just drivers to get your comp to recognize the phone when its attached.
I'm assuming this is something you're expirementing with to get root via the adb in recovery, if so, good luck.
-------------------------------------
Sent via the XDA Tapatalk App
Hi crax0r,
The folks at Android (aka Google) provide these instructions for installing the drivers. It involves installing their SDK first, and installing Java for that, and an IDE called eclipse.... UGH.
The HTC "Sync" Application that hoovnick is referring to can be found here.
It has been so long ago that I installed drivers (on a WinXp x32 laptop) that I can't remember what order I did things in, whether or not the driver used by HTC sync is sufficient for fastboot but not adb (or vice versa), whether I did the SDK install first, etc etc etc. As a matter of fact, it's been so long ago that the computer that I did it on is now dead, and here I am using a Linux machine.
For all I know, the order you do things in affects the outcome - it sure seems like a lot of folks with Windows 7 complained about driver troubles.
One thing is for sure, though - setting up the entire Android SDK (+ Java + Eclipse + ...) in order to install a device driver has to be the worlds most roundabout way of doing a driver install.
If you are considering using the "fastboot" method to install Amon_RA's recovery boot, you might try just installing HTC Sync first, and see if that is sufficient for getting fastboot talking to the phone. That install is way, way easier than setting up the SDK to get a driver installed.
The other thing which is an option, if you are a little bit Linux-savvy, is to boot one of those "Live CDs" (Ubuntu, SuSe, etc) on your PC - there are no drivers to install in the case of Linux, you just need to be running as "root" on the Live (linux) CD to get fastboot to talk to the phone. The downloads (fastboot for Linux and the Amon_RA recovery image) are small, and they will both easily fit in the /tmp folder of the Linux (Live CD) boot on the PC.
Once you have Amon_RA on the phone, you won't need the SDK any longer, unless you want to start doing dev-like things; that's why a one-time boot into Linux would also work.
bftb0
I <3 Ubuntu. It's amazing!
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
crax0r said:
It's OK. I'm running Ubuntu now.
Click to expand...
Click to collapse
Excellent. Just remember to always run fastboot as root, and if using adb, then the first time after you boot (the PC), run adb as root.
The reason is that by default, Ubuntu won't let an unprivileged user access the USB.
Since I have adb and fastboot in my Ubuntu (regular user) PATH, I usually just do a
$ sudo `which adb` blah-blah-blah
or
$ sudo `which fastboot` blah-blah-blah
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
I don't know - I've already forgotten everything I did with the driver install in Windows, and I don't currently have a working Windows machine. Sorry I can't be of more help. As I said, the troubles people have been having seem to depend on which version of Windows (Xp/Vista/7), whether its x32 or x64, phase of the moon, etc. Seems like people run into snags on Win7 or x64 versions of Windows more than Xp-32, but I don't know why that is.
Keep plugging away at it. If you are looking for resources to help resolve the problem, I would go look at docs relating to Windows driver install troubleshooting - the driver install problem seems to be a Windows issue, not really anything to do with the SDK.
bftb0
hoovnick said:
bftb0, I am trying to install only the driver from the SDK tools, but when I follow the instructions for a fresh install, and point windows to the folder with the driver in it, windows says it can't find a driver there. What am I doing wrong here?
Click to expand...
Click to collapse
Sounds like what happened to me. i had to hit the icon at the top of my phone that showed the usb cable.. i had to switch charge only to disk drive "mount as disk drive"... folder popped right up on my windows machine asking how i wanted to open the file
I have the SDK running and my phone being recognized on my computer with Vista but I have another one running XP 32 bit and windows will NOT recognize the .inf? Any ideas? I deleted all previous HTC drivers and tried that approach but nothing seems to be working.
I have CELB 2.7 installed with Cyanogen 5.0.8-DS, I have tried on both an xp machine as well as a windows 7 32 bit machine, neither works, I have installed the NDIS driver on windows xp, I turn on USB debugging, I turn on USb tethering inside the wireless/networks settings, I plug the phone in, it installed some drivers for windows 7, and windows xp. I manually installed NDIS into xp, but I dont see anything.
Im not even sure what is supposed to happen, am I supposed to see another network connection or something?
Also, do i need ADB installed for this to work?
is there any other way to fix this? my comp is 32bit
trying to root using this method: http://zepinventory.wordpress.com/2014/03/31/how-to-root-azpen-a727-tablet/
I couldn't make it work from XP, and had to do it from Win7
I couldn't make it work from XP either. XP said it couldn't find the Android drivers, even though they were where I pointed to.
I had to DL the 64bit version of tha Andriod SDK, and to the driver install on my SO's 64 bit Win7 laptop, From there, Kingo Root could root it, and I could remove the SDK and Kingo Root from the SO's machine.
I got it to work once using the SDK on Windows 7 Professional, but subsequent tries did not. And for the life of me I can't figure out how I did it.
I'm assuming I need to install the Android ADB Interface as opposed to Android Composite ADB Interface, correct?
gotroot801 said:
I got it to work once using the SDK on Windows 7 Professional, but subsequent tries did not. And for the life of me I can't figure out how I did it.
I'm assuming I need to install the Android ADB Interface as opposed to Android Composite ADB Interface, correct?
Click to expand...
Click to collapse
AFAIK, yes. I believe that's what I installed. It's a "do once" operation, as once the driver is in place, you can root the device.