• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[DRIVERS] Latest HTC Drivers [4.2.0.001]

Search This thread

CNexus

Senior Member
May 17, 2012
9,009
13,995
~/android
Latest HTC Drivers
Latest HTC Drivers extracted from HTC Sync v3.3.21 and HTC Sync Manager v2.0.61.0

Latest Driver Version (HTC Sync): 4.0.1.001
Latest Driver Version (HTC Sync Manager): 4.2.0.001

BMP Drivers are the same for both sets of drivers.


For those who don't want to have to download 120 some MB of bloatware called HTC Sync ;)

Instructions:
  • Determine if your system is 32-bit or 64-bit
  • Download the BMP Driver for your OS type (x86 version if on 32-bit, x64 if on 64-bit)
  • Download the newest HTCDrivers file (choose either the "EXE" or "MSI" driver file, but not both)
  • Disable any antivirus program(s) present
  • Run both files downloaded above (the BMP.msi and the HTCDriver file)
  • Re-enable your antivirus program(s)

Links

ALL DRIVER FILES: www.mediafire.com/?o10b16j5b3r3o
OEM SETUP FILES: www.mediafire.com/?1rwmleoe17akd

Updated on 6.6.13

Updated on 4.23.13

Updated on 4.02.13
  • RemoveOldHTCDriver3.exe (packaged in HTC Sync Manager v2.0.41.0)
  • Removed duplicate x86 BMP Driver
  • Updated instructions with link to determine if on 32-bit or 64-bit

Updated on 3.31.13

Updated on 3.6.13

Updated on 11.28.12
  • HTC BMP USB Driver_x86.msi DELETED: Turned out to be the same 1.0.5375 as above. Download from link above.
  • HTCDriver_3.0.0.023.msi





------------

MD5 CHECKSUMS
Sometimes downloading from the internet can yield a corrupt download. To prevent this, make sure you always check the md5 checksum (also known as "md5sum") of the file. This method verifies the digital integrity of the file by verifying its digital signature with the MD5 algorithm.

After you download each file, make sure to check that the md5sum matches what is given.

Code:
[LIST]
[*]25912deacc5d55528e223ec7b99705cc [B]*HTCDriver_3.0.0.023.msi[/B]
[*]220c41f3b03f42190899db8cb081b5c6 [B]*HTCDriver_4.0.1.001.exe[/B]
[*]a578d837343fe2542ecf405a630d46a0 [B]*HTCDriver_4.0.1.001.msi[/B]

[*]8223ec1c2aa71503b431a0daabb23154 [B]*HTCDriver_4.0.1.002.exe[/B]
[*]4dfbd4ae8662124d06e0a04db2065069 [B]*HTCDriver_4.0.1.002.msi[/B]

[*]bf24b0adc2f792ee4180ca545e4b60a0 [B]*HTC_BMP_USB_Driver_x32_1.0.5375.msi[/B]
[*]7b461095d56f9a6814d8f3e14cac0859 [B]*HTC_BMP_USB_Driver_x64_1.0.5375.msi[/B]

[*]96e6d181192a995214493a6828e4287d [B]*IPTInstaller_4.0.8.msi[/B]
[*]92bd34ec7787e631231c68aba392b6e7 [B]*RemoveOldHTCDriver3.exe[/B]

[*]f281d8994ab9f1315828ac2226a9bb75 [B]*HTCDriver_4.1.0.001.exe[/B]
[*]ed6d5fc5cc7dcca653f7a0beab01035d [B]*HTCDriver_4.1.0.001.msi[/B]
[*]96589c02be46fd7b85160d5b15f4c88a [B]*HTCPluginChecker.exe[/B]
[*]36ba2c8627ba18c6540bfa25be3b67fc [B]*HTCSync_3.3.21.exe[/B]
[*]a356e5c828c7cb3869dc67058e5bbc2c [B]*SyncManager_2.0.53.0.exe[/B]
[*]da1e40e478725d3e829243e84043d21f [B]*SyncManager_2.0.53.0_STRIPPED.exe[/B]
[/LIST]

How to check the md5sum of a file:

Windows:
For windows you need to download the md5sum binary. I recommend the one from my dev-host.

After that, copy the file you're trying to verify to the directory where where you downloaded the "md5sum.exe"

Once that is finished, do SHIFT+RIGHT CLICK (inside the folder window) and choose "Open command window here"

dKeAEvd.png


Then type the following ("fileNameHere" must include the extension):
Code:
md5sum fileNameHere
That will output a hash, which you can compare to the ones above.
xjcL0IG.png


Linux: No need to download anything, md5sum binaries are included in all distros, as far as I know.

Open a terminal and type the following ("fileNameHere" must include the extension):

Code:
$ cd path/to/download/folder
$ md5sum fileNameHere


Two important notes:
This method can be used with any files you download, as long as the download site (or the dev themself) provides the correct md5sum.
If any of the digits do not match exactly, you need to download the file again.
 
Last edited:

rum0s

Senior Member
Dec 22, 2007
524
73
Wow really cool, I have always hated installing htc sync :D Thank you a thousand times!!!
 

Sneakyghost

Senior Member
Jul 24, 2008
8,303
13,584
InMyHead
What about the Universal Naked Driver thread?
Are these drivers in any way more up-to-date or in other ways better than those? Or additional?

I currently use that driver package and am setup quite well with it. But i think i still had to set up HTCSync to get the MTP drivers. Not sure anymore lol.
 

ipit

Senior Member
Nov 29, 2010
549
142
MSI files don't seem to install. Getting error messages on ALL. Error 2732 Directory Manager not initialised.

edit: disregard, just temporarily disabled UAC settings and it worked.
 
Last edited:
  • Like
Reactions: daro201983

CNexus

Senior Member
May 17, 2012
9,009
13,995
~/android
What about the Universal Naked Driver thread?
Are these drivers in any way more up-to-date or in other ways better than those? Or additional?

I currently use that driver package and am setup quite well with it. But i think i still had to set up HTCSync to get the MTP drivers. Not sure anymore lol.
I believe that the universal naked drivers would work just as well, but for ADB only

For the purposes of transferring files using either MTP or UMS, you need the HTC drivers

EDIT: If you look at the thread, the drivers were last updated Nov. of 2012, so I would say that these are more up to speed than those
 

Sneakyghost

Senior Member
Jul 24, 2008
8,303
13,584
InMyHead
AW: [DRIVERS] Latest HTC Drivers [v4.0.1.002]

I believe that the universal naked drivers would work just as well, but for ADB only

For the purposes of transferring files using either MTP or UMS, you need the HTC drivers

EDIT: If you look at the thread, the drivers were last updated Nov. of 2012, so I would say that these are more up to speed than those

Ok cool thanks I had that feeling that the universal drivers are ADB only but want sure anymore. Then I thank you for this nice extraction. Very handy.

Sent from Viper 2.2
 
  • Like
Reactions: CNexus

Sneakyghost

Senior Member
Jul 24, 2008
8,303
13,584
InMyHead
Got an idea, the MD5 verification you posted sounds awefully complicated. Why don't you just recommend windows and/or mac users to install HashTab? Its a Windows Shell extension that produces a new tab on the properties dialogue for each file and lets you compare hashes by just c/p any hash you want from one file property into another.

It's free and totally cool. You find it here: http://www.implbits.com/hashtab.aspx

[EDIT]
I am having issues identifying which driver packages i have to install on my windows 7 x64. I just went through all of them (apart the obvious x86 bmp package). I noticed that i had to create a uniqueID folder in \TEMP with another uniqueID subfolder and place one of the MSI packages in there and rename it to what the MSI wanted to have, in order to make that package work.

I assume, the HTC Sync or the Sync Manager would usually unpack those files to that folder and name them accordingly (in fact, i think you extracted them from there the same way i would extract a RUU lol) and then you renamed those packages to include the version numbering? Unfortunately those drivers aren't easy that way for noobs. I wonder if they can be re-packaged with some easy install automator program so that in the end you could offer like a HTC Sync package without the HTC Sync crap in it?
 
Last edited:

CNexus

Senior Member
May 17, 2012
9,009
13,995
~/android
Got an idea, the MD5 verification you posted sounds awefully complicated. Why don't you just recommend windows and/or mac users to install HashTab? Its a Windows Shell extension that produces a new tab on the properties dialogue for each file and lets you compare hashes by just c/p any hash you want from one file property into another.

It's free and totally cool. You find it here: http://www.implbits.com/hashtab.aspx

[EDIT]
I am having issues identifying which driver packages i have to install on my windows 7 x64. I just went through all of them (apart the obvious x86 bmp package). I noticed that i had to create a uniqueID folder in \TEMP with another uniqueID subfolder and place one of the MSI packages in there and rename it to what the MSI wanted to have, in order to make that package work.

I assume, the HTC Sync or the Sync Manager would usually unpack those files to that folder and name them accordingly (in fact, i think you extracted them from there the same way i would extract a RUU lol) and then you renamed those packages to include the version numbering? Unfortunately those drivers aren't easy that way for noobs. I wonder if they can be re-packaged with some easy install automator program so that in the end you could offer like a HTC Sync package without the HTC Sync crap in it?

What windows suite do you have? Before I even started uploading extracted drivers, I tested all of the installations (run from my desktop) on my Windows 7 ultimate x64 laptop, precisely because I suspected it might somehow be blocked. And all (including the msi's) installed with no problem. I've even reinstalled the latest ones (downloading from my own mediafire) after I had to reinstall windows 7 on my laptop. Also, which msi did you have problems installing?
 
  • Like
Reactions: Sneakyghost

CNexus

Senior Member
May 17, 2012
9,009
13,995
~/android
Awesome, thanks for the feedback that it works on Win8, will add to OP. Couldn't test it myself because I have no machines running 8. But thanks :good:
 

Sneakyghost

Senior Member
Jul 24, 2008
8,303
13,584
InMyHead
What windows suite do you have? Before I even started uploading extracted drivers, I tested all of the installations (run from my desktop) on my Windows 7 ultimate x64 laptop, precisely because I suspected it might somehow be blocked. And all (including the msi's) installed with no problem. I've even reinstalled the latest ones (downloading from my own mediafire) after I had to reinstall windows 7 on my laptop. Also, which msi did you have problems installing?

Running Windows 7x64 Ultimate.
Dunno bro probably just some mess on my machine then.
Think if your machine took it alright with the same OS it'll probably be some screw-up on mine.

mobile post
 

Top Liked Posts

  • There are no posts matching your filters.
  • 80
    Latest HTC Drivers
    Latest HTC Drivers extracted from HTC Sync v3.3.21 and HTC Sync Manager v2.0.61.0

    Latest Driver Version (HTC Sync): 4.0.1.001
    Latest Driver Version (HTC Sync Manager): 4.2.0.001

    BMP Drivers are the same for both sets of drivers.


    For those who don't want to have to download 120 some MB of bloatware called HTC Sync ;)

    Instructions:
    • Determine if your system is 32-bit or 64-bit
    • Download the BMP Driver for your OS type (x86 version if on 32-bit, x64 if on 64-bit)
    • Download the newest HTCDrivers file (choose either the "EXE" or "MSI" driver file, but not both)
    • Disable any antivirus program(s) present
    • Run both files downloaded above (the BMP.msi and the HTCDriver file)
    • Re-enable your antivirus program(s)

    Links

    ALL DRIVER FILES: www.mediafire.com/?o10b16j5b3r3o
    OEM SETUP FILES: www.mediafire.com/?1rwmleoe17akd

    Updated on 6.6.13

    Updated on 4.23.13

    Updated on 4.02.13
    • RemoveOldHTCDriver3.exe (packaged in HTC Sync Manager v2.0.41.0)
    • Removed duplicate x86 BMP Driver
    • Updated instructions with link to determine if on 32-bit or 64-bit

    Updated on 3.31.13

    Updated on 3.6.13

    Updated on 11.28.12
    • HTC BMP USB Driver_x86.msi DELETED: Turned out to be the same 1.0.5375 as above. Download from link above.
    • HTCDriver_3.0.0.023.msi





    ------------

    MD5 CHECKSUMS
    Sometimes downloading from the internet can yield a corrupt download. To prevent this, make sure you always check the md5 checksum (also known as "md5sum") of the file. This method verifies the digital integrity of the file by verifying its digital signature with the MD5 algorithm.

    After you download each file, make sure to check that the md5sum matches what is given.

    Code:
    [LIST]
    [*]25912deacc5d55528e223ec7b99705cc [B]*HTCDriver_3.0.0.023.msi[/B]
    [*]220c41f3b03f42190899db8cb081b5c6 [B]*HTCDriver_4.0.1.001.exe[/B]
    [*]a578d837343fe2542ecf405a630d46a0 [B]*HTCDriver_4.0.1.001.msi[/B]
    
    [*]8223ec1c2aa71503b431a0daabb23154 [B]*HTCDriver_4.0.1.002.exe[/B]
    [*]4dfbd4ae8662124d06e0a04db2065069 [B]*HTCDriver_4.0.1.002.msi[/B]
    
    [*]bf24b0adc2f792ee4180ca545e4b60a0 [B]*HTC_BMP_USB_Driver_x32_1.0.5375.msi[/B]
    [*]7b461095d56f9a6814d8f3e14cac0859 [B]*HTC_BMP_USB_Driver_x64_1.0.5375.msi[/B]
    
    [*]96e6d181192a995214493a6828e4287d [B]*IPTInstaller_4.0.8.msi[/B]
    [*]92bd34ec7787e631231c68aba392b6e7 [B]*RemoveOldHTCDriver3.exe[/B]
    
    [*]f281d8994ab9f1315828ac2226a9bb75 [B]*HTCDriver_4.1.0.001.exe[/B]
    [*]ed6d5fc5cc7dcca653f7a0beab01035d [B]*HTCDriver_4.1.0.001.msi[/B]
    [*]96589c02be46fd7b85160d5b15f4c88a [B]*HTCPluginChecker.exe[/B]
    [*]36ba2c8627ba18c6540bfa25be3b67fc [B]*HTCSync_3.3.21.exe[/B]
    [*]a356e5c828c7cb3869dc67058e5bbc2c [B]*SyncManager_2.0.53.0.exe[/B]
    [*]da1e40e478725d3e829243e84043d21f [B]*SyncManager_2.0.53.0_STRIPPED.exe[/B]
    [/LIST]

    How to check the md5sum of a file:

    Windows:
    For windows you need to download the md5sum binary. I recommend the one from my dev-host.

    After that, copy the file you're trying to verify to the directory where where you downloaded the "md5sum.exe"

    Once that is finished, do SHIFT+RIGHT CLICK (inside the folder window) and choose "Open command window here"

    dKeAEvd.png


    Then type the following ("fileNameHere" must include the extension):
    Code:
    md5sum fileNameHere
    That will output a hash, which you can compare to the ones above.
    xjcL0IG.png


    Linux: No need to download anything, md5sum binaries are included in all distros, as far as I know.

    Open a terminal and type the following ("fileNameHere" must include the extension):

    Code:
    $ cd path/to/download/folder
    $ md5sum fileNameHere


    Two important notes:
    This method can be used with any files you download, as long as the download site (or the dev themself) provides the correct md5sum.
    If any of the digits do not match exactly, you need to download the file again.
    8
    I unpacked and uploaded newest drivers:

    HTC_ADB_USB_Driver v2.0.7.23 (from HTC_Sync_Manager v2.4.11.0) and compatible with the newer HTC phones like One S
    HTC_ADB_USB_Driver v2.0.7.20 (from HTC_Sync v3.3.63) and compatible with all HTC phones.

    To complete I also added:
    ADB_v1.0.31+Fastboot (from Android-SDK_2013-10-30)

    Because the fastboot/adb files deliverd with HTC drivers are a little old as usual.

    Only and only the needed files. Nothing less, nothing more. This is the real deal, with the real drivers version numbers.
    7
    Updated OP with md5sum how-to and checksums.
    2
    What about the Universal Naked Driver thread?
    Are these drivers in any way more up-to-date or in other ways better than those? Or additional?

    I currently use that driver package and am setup quite well with it. But i think i still had to set up HTCSync to get the MTP drivers. Not sure anymore lol.
    I believe that the universal naked drivers would work just as well, but for ADB only

    For the purposes of transferring files using either MTP or UMS, you need the HTC drivers

    EDIT: If you look at the thread, the drivers were last updated Nov. of 2012, so I would say that these are more up to speed than those