Database Info

[DRIVERS] Latest HTC Drivers [4.2.0.001]

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)
Click to expand...
Click to collapse
Links
ALL DRIVER FILES: www.mediafire.com/?o10b16j5b3r3o
OEM SETUP FILES: www.mediafire.com/?1rwmleoe17akd
Updated on 6.6.13
HTCDriver_4.2.0.001.exe
SyncManager_2.0.61.0.exe
Updated on 4.23.13
HTCDriver_4.1.0.001.msi
HTCDriver_4.1.0.001.exe
HTCPluginChecker.exe
HTCSync_3.3.21.exe
SyncManager_2.0.53.0.exe
SyncManager_2.0.53.0_STRIPPED.exe
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
HTCDriver_4.0.1.002.exe
HTCDriver_4.0.1.002.msi
IPTInstaller_4.0.8.msi
Updated on 3.6.13
HTC_BMP_USB_Driver_x86_1.0.5375.msi
HTC_BMP_USB_Driver_x64_1.0.5375.msi
HTCDriver_4.0.1.001.exe
HTCDriver_4.0.1.001.msi
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
Click to expand...
Click to collapse
------------
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]
Click to expand...
Click to collapse
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"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
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.
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.

Extracted x32 BMP Driver and added to OP
HTC_BMP_USB_Driver_x32_1.0.5375.msi​

Do I need to uninstall any old version first (from older Sync)?

Interesting, I found a HTC Driver Installer 4.0.1.002 in my machine.

Re: [DRIVERS] Latest HTC Drivers [v4.0.1.001]
RayYung said:
Interesting, I found a HTC Driver Installer 4.0.1.002 in my machine.
Click to expand...
Click to collapse
Are you sure? If you have the (htc sync) exe can you upload it somewhere and give me the link?
I heard that the drivers were updated as well, and I've literally redownloaded HTC Sync about 50 times to try and update this, with no luck.

CNexus said:
Are you sure? If you have the (htc sync) exe can you upload it somewhere and give me the link?
I heard that the drivers were updated as well, and I've literally redownloaded HTC Sync about 50 times to try and update this, with no luck.
Click to expand...
Click to collapse
This is what I have(see attached), I am still trying to figure out where it come from...
(I uninstalled and re-install three different versions of HTC Sync multiple time coz my HOX is "unknown" in device manager...)
I extract every exe I have but no luck, will let you know once I find it...

RayYung said:
This is what I have(see attached), I am still trying to figure out where it come from...
(I uninstalled and re-install three different versions of HTC Sync multiple time coz my HOX is "unknown" in device manager...)
I extract every exe I have but no luck, will let you know once I find it...
Click to expand...
Click to collapse
OK, I uninstall all version and install them one by one, HTC Driver Installer 4.0.1.002 come with HTC Sync Manager 2.0.41.0. But can't find it in the exe, will play with it more tomorrow...

Updated OP with IPTInstaller and Drivers version 4.0.1.002
Updated on 3.31.13
HTCDriver_4.0.1.002.exe
HTCDriver_4.0.1.002.msi
IPTInstaller_4.0.8.msi
Click to expand...
Click to collapse

Updated OP with another link; some cleaning up in OP as well.
Updated on 4.02.13
RemoveOldHTCDriver3.exe (packaged in HTC Sync Manager v2.0.41.0)
Removed duplicate x32 BMP Driver
Updated instructions with link to determine if on 32-bit or 64-bit
Click to expand...
Click to collapse

Updated OP with md5sum how-to and checksums.

Have updated all drivers per above but I get a constant error "There is a problem with MTP driver"
Device manager says "The installation failed because a function driver was not specified for this device instance"
Driver update always says it cannot find a driver automatically, when I try to install drivers manually it says the driver is already up to date and does not need to be changed
Any ideas?
WP7 64-bit OS

Go to Devices and Printers > Your phone > Right click the icon > Properties > Edit details / Change settings (or something similar) > uninstall driver (THEN UNPLUG PHONE)
Then go to Control Panel > All Programs > Uninstall everything that has HTC and try again.
These drivers have worked for me upon several reinstalls of Win7 x64 on my laptop, so there's just something interfering with it on your end. I've also gotten several reports of it working for other people on their Win7 x64

CNexus said:
Go to Devices and Printers > Your phone > Right click the icon > Properties > Edit details / Change settings (or something similar) > uninstall driver (THEN UNPLUG PHONE)
Then go to Control Panel > All Programs > Uninstall everything that has HTC and try again.
These drivers have worked for me upon several reinstalls of Win7 x64 on my laptop, so there's just something interfering with it on your end. I've also gotten several reports of it working for other people on their Win7 x64
Click to expand...
Click to collapse
i am on Windows 8 and no way i can make the computer recognize the phone, keep telling me USB device not recognized and on properties i have HTC with the question mark on it?

CNexus said:
Go to Devices and Printers > Your phone > Right click the icon > Properties > Edit details / Change settings (or something similar) > uninstall driver (THEN UNPLUG PHONE)
Then go to Control Panel > All Programs > Uninstall everything that has HTC and try again.
These drivers have worked for me upon several reinstalls of Win7 x64 on my laptop, so there's just something interfering with it on your end. I've also gotten several reports of it working for other people on their Win7 x64
Click to expand...
Click to collapse
Afraid I still definitely have a problem with the MTP driver on one PC (not all my PCs).
HTC support logged in remotely to my PC but were unable to fix it: they have escalated the problem to their technical team - I hope to have a response next week and will post when (if) resolved.

Anyone able to get the drivers working in fastboot mode on Windows 8 ?

appelflap said:
Anyone able to get the drivers working in fastboot mode on Windows 8 ?
Click to expand...
Click to collapse
i managed to do all the process using another laptop where there were no driver installed, is a window 8 and worked fine, no i try to personalize the phone and will let you know

melando said:
Afraid I still definitely have a problem with the MTP driver on one PC (not all my PCs).
HTC support logged in remotely to my PC but were unable to fix it: they have escalated the problem to their technical team - I hope to have a response next week and will post when (if) resolved.
Click to expand...
Click to collapse
Cool. Let me know, maybe some other drivers are interfering woth the HTC drivers

For those having issues with Windows 8 drivers, look here

KidCarter93 said:
For those having issues with Windows 8 drivers, look here
Click to expand...
Click to collapse
Thanks a million. Going tot try these drivers out.

Bump

[Tutorial] How to install Android SDK/ADB tool & HTC's drivers [BEGINNER FRIENDLY]

[Tutorial] How to install Android SDK/ADB tool & HTC's drivers [BEGINNER FRIENDLY]
[SIZE="+1"]-- Android SDK/ADB tool Tutorial --[/SIZE]​
I decided to create this Beginner Friendly tutorial on how to install SDK tool mainly because recent phones such as the i.e. HTC One X / One X+ are requiring many basic usage of adb command line, and lots of members are having difficulities to have basics adb command to work because their SDK tool is not correctly installed. I won't show you how to make usage of it, there is plenty of How-to's for that purpose all around xda and on the Web.
This is all safe to install on your Windows based computer, and if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device. From now on, I or anyone else on the Internet can not be held responsible if something really bad is happening to you because you didn't read and followed any given instructions letters by letters and you ended with a screwed, pricey and valuable paperweight device. That being said, let's get started.​
Let's GO!
____________________________________________
[SIZE="+1"]-- Enabling USB debugging mode --[/SIZE]
On your phone simply follow this path : Settings -> Developer options -> Turn the option ON -> under Debugging -> tick USB debugging option Debug mode when USB is connected
That's it, done!
____________________________________________
[SIZE="+1"]-- Java Installation --[/SIZE]
This is a prerequisite to have a flawlessly working SDK tool installation.
Click on the following link to download it on Java's website : Free Java Download
On the next page, do not click on Agree and Start Download, instead click on See all Java downloads.
Which should you choose? If you have a 64-bit Windows OS you MUST install the two versions (both 32-bit and 64-bit), otherwise the 32-bit is sufficient for a 32-bit Windows OS.
Before installing the latest version of Java, it is recommended to uninstall all previous Java's installation. (How to -> Remove Older Versions)
Complete the required installation depending of the type of Windows installation.
You are all done for Java.
-- Screenshots for the visual ones --
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
____________________________________________
[SIZE="+1"]-- SDK Tools Installation --[/SIZE]
First step is to download the SDK Manager, to do so click on this link -> Download the SDK
Next locate on the bottom of your screen the USE AN EXISTING IDE, click on it.
On the Get the Android SDK page, tick the I have read and agree with the above terms and conditions box and click on the Download the SDK Tools for Windows button.
Navigate to your Download folder, and locate a file named like this: installer_r21.1-windows.exe (N.B. The r21.1 version was available when I did this how to, your version could be different.)
Double click on the installer_r21.1-windows.exe file to start the installation. Take good note where the file will be installed, generally the default SDK path is : C:\Users\your_session's_name\AppData\Local\Android\android-sdk.
Now, navigate to the path of the SDK installation folder.
Select all (CTRL + A) in this folder and Copy (CTRL +C) them for the next step.
Now you need to create a new folder at the root of your C:\ drive named : AndroidSDK
Open up the newly created folder and Paste (CTRL + V) the previously copied files.
Stay in this folder and double click on the SDK Manager icon.
The SDK Manager will open a new window, click on Deselect All, then tick the following line in Tools : AndroidSDK Platform-tools
Click on Install 1 Package..., accept the license agreement and click on Install let the manager do it's thing.
Click on Done and close the manager's window.
Congrats! You have created successfully your SDK tool!
Wait! Let's clean your computer a bit....
Go back to the previous folder, the one located in this path : C:\Users\your_session's_name\AppData\Local\Android\android-sdk
Click on the Uninstaller, we don't need this one anymore. Don't worry the other AndroidSDK folder won't be deleted.
Voilà! You are done with this part.
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Creating of script file for a fast access --[/SIZE]
Locate the Platform-tools sub-folder in the AndroidSDK folder.
Right click in a empty space of the folder and select in the contextual menu New -> Text Document
Open this new Text Document and Copy/Paste this : c:\windows\system32\cmd.exe
Save this file as : Start SDK.bat
Acknowledge the : If you change file extension... warning.
Right click your new created Start SDK and send a shortcut on your Desktop.
Done! If you try to double click on your Start SDK shortcut, a command window should open with something like these lines :
Code:
C:\AndroidSDK\platform-tools>c:\windows\system32\cmd.exe
Microsoft Windows [version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\AndroidSDK\platform-tools>
Success!
____________________________________________
[SIZE="+1"]-- Installing HTC's Drivers --[/SIZE]
This one is very easy, simply download and run the installer and let Windows do the rest. Drivers compatbile 32-bit or 64-bit
Download the Self-install HTCDriver_4.0.1.001.exe/
Make sure your phone is not plugged on your computer via the USB cable.
Simply run the installer of the driver you've just downloaded.
Once the installation is completed, simply plug your phone via your USB cable and Windows "wizard manager" will now detect your phone.
If it doesn't work, unplug your phone and reboot your computer. Then plug back your phone once rebooted.
Done!
-- Screenshots for the visual ones --
____________________________________________
[SIZE="+1"]-- Let's try all this! --[/SIZE]
With your phone plugged on your USB cable...
From your Desktop, double click on your Start SDK shortcut.
In the command window, at the command line : C:\AndroidSDK\platform-tools> type this -> adb devices (Enter)
The serial number of your phone should appear in the command window. If it is the case, then try this again : C:\AndroidSDK\platform-tools> type this -> adb reboot (Enter)
Your phone will now Reboot
If all this worked, you have a successful SDK Tools installation!
-- Screenshots for the visual ones --
This is it, I hope this tutorial was helpful, if you have some sort of problems let me know, I will try to help you at the best of my knowledge. Have fun hacking your Android!!

Lucky Thirteen said:
...if you can not achieve success with this installation, well obviously, you shouldn't play the hacking game with your device.
Click to expand...
Click to collapse
Excellent tutorial... but I disagree with this line. No process is bulletproof and there is no way a tutorial can account for all the variables with Windows.
Which explains why I am now asking for help!
This is my third Android phone and fifth Android device. I've rooted all five and installed multiple ROMs and for the most part have not had too many problems.
I'm currently running Elegancia 5.3.0 on my AT&T One X+ and have a few issues that I'm tired of dealing with. I decided to flash the RUU to go back to stock and also to update to hboot 1.4 which is required for the Blackout ROM I was thinking about trying. The RUU cannot find my phone unless I connect while in the bootloader. Even then though, the RUU flash still fails. Since it cannot see my phone while it's running, I decided to check if ADB can see it. Nope. No luck at all. I have connected with ADB to my device many, many times... but it has been close to a year since the last time I did. I removed all HTC drivers and Sync from Add/Remove Programs, deleted my old version of the SDK and Java and followed your tutorial step-by-step.
My phone still shows up in Device Manager under PORTABLE DEVICES and I can't seem to make it connect any other way.
Please tell me you have a suggestion to help me fix this. I've tried using every combination of search terms I can think of and have had no luck for the past 36 hours.

Finally fixed my ADB problem using these steps in case anyone else runs into it.

This worked great for me after two days of trying to get my phone to connect. I had to uninstall everything related to java, android, and htc, and the link for the htc drivers was dead so I just reinstalled sync manager, but it all works now, much thanks. All this effort was just so I could put my music on the phone, and so that I could do a full backup to my pc without rooting.

[OFFLINE UPDATE] WP8.1 To W10 Mobile [ATT] [Verizon] [T-Mobile] (Build 10586.107)

Prerequisites:
Your PC must be at least Windows 7 Service Pack 1, although you must install every Visual C++ Redistributable Runtime and the Windows Device Recovery Tool.
Your Phone OS version must be at least 8.10.14219.341 or newer. If not, please update it using the windows insider app.
Have registered your device as a developer with the WP SDK.
Remove pin lock and turn off reset protection before the update procedure.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
:fingers-crossedlease follow this guide at your own risk as I am not responsible for bricked devices, dead SD cards or thermonuclear war:crying:.
Instructions:
1. Backup Your device.
2. Download Iutool (WP_CPTT_NT-x86-fre.msi) from the attachments section and install it. The default install directory will be
Code:
C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
3. Download the M8.Rar that reflects your Carrier and extract the contents to C:\ on your PC.
M8ATT
M8Verizon
M8TMobile
Code:
C:\M8ATT
Code:
C:\M8Verizon
Code:
C:\M8TMobile
4. Open Command Prompt as administratior and change directory to where Iutool is installed.
Code:
cd C:\Program Files (x86)\Windows Kits\10\Tools\bin\i386
5. Plug your M8 into your PC and check to see if Iutool discovers your device by typing
Code:
iutool -l
If your device appears then you are ready to continue
If you met error 80070490 when executing iutool -l then disconnect your device and remove it from the Devices & Printers section of Control Panel
6. Assuming you extracted the correct zip into C:\ you are either going to type
Code:
iutool -V -p C:\M8ATT
Code:
iutool -V -p C:\M8Verizon
Code:
iutool -V -p C:\M8TMobile
That command will push the update to your device and it will prepare for the installation! Once the update is ready, take it! You'll want to find something to occupy your time as the process will take 40 minutes.
8. Once booted into W10 open Settings and navigate to the "For Developers" menu and enable Developer Mode.
9. Download and install Interop-Tools from it's respected thread and follow the For All other OEM Devices section to Interop/Cap Unlock your M8 if you had planned on doing so.
Interop-Tools https://forum.xda-developers.com/wi...app-interop-tools-versatile-registry-t3445271
10. Use any method that you know to modify your model(DeviceTargetingInfo) to a supported W10 Mobile Device
11. Now enable Windows insider preview builds and set to either slow or release ring.
12. Go into phone update and search for update. You should be brought to build 14393 or later. Updating to this build will fix critical issues/bugs you met earlier.
13. I also recommend a factory reset after all updates as that will reset Registry values to defaults and fix other things as well.
A HUGE thanks to @hikari_calyx for the Offline Update package V4.1 that he had put together over on the Windows 10 Mobile forums!
Another HUGE thanks to @gus33000 for Interop-Tools!​

RECOMMENDED TO ADD:
1. If you met 80070490 error when executing iutool -l, disconnect your phone, and delete your phone in Device & Printers (Run "control printers") and delete your phone listed on it, then reconnect your phone again.
2. You can also install Mobile Enterprise provisioned package in order to get 10586.753. This provisioned package will be available with my Offline Update Package V4.
3. I also recommended to modify PhoneHardwareVariant to RM-1045 if you are going to modify to L930. You should also modify PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB.
4. Turn off reset protection before update procedure.

hikari_calyx said:
RECOMMENDED TO ADD:
1. If you met 80070490 error when executing iutool -l, disconnect your phone, and delete your phone in Device & Printers (Run "control printers") and delete your phone listed on it, then reconnect your phone again.
2. You can also install Mobile Enterprise provisioned package in order to get 10586.753. This provisioned package will be available with my Offline Update Package V4.
3. I also recommended to modify PhoneHardwareVariant to RM-1045 if you are going to modify to L930. You should also modify PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB.
4. Turn off reset protection before update procedure.
Click to expand...
Click to collapse
PhoneHardwareVariant to RM-1045 if you are going to modify to L930? does this affect anything?
PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB? will this help service? i had not changed these values before updating myself.

AnierinB said:
PhoneHardwareVariant to RM-1045 if you are going to modify to L930? does this affect anything?
PhoneMobileOperatorName to a unbranded variant, such as 000-44, 000-88, 000-HK, 000-GB? will this help service? i had not changed these values before updating myself.
Click to expand...
Click to collapse
In some case, without modifying them, you can't search any update.

I successfully installed WP 10.0.14393.953 in my HTC M8 and everything seems ok but the in-call volume that is very very low, quite inaudible. Any ideas? Thanks, ALe

I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
---------- Post added at 06:50 AM ---------- Previous post was at 06:30 AM ----------
Cashdog53 said:
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
Click to expand...
Click to collapse
Never mind. Fixed the problem by removing my SD card, and restarting the phone I think...

zagreo said:
I successfully installed WP 10.0.14393.953 in my HTC M8 and everything seems ok but the in-call volume that is very very low, quite inaudible. Any ideas? Thanks, ALe
Click to expand...
Click to collapse
ThIs is normal as I've encountered the same issue.
Bugs I know of:
Front facing camera sometimes causes reboot (switching from back in most cases)
Sound will sometimes only go through one speaker (works itself out but happens every now and then)
Flashlight toggle in quick settings has a long delay and sometimes doesn't work at all
Dot view doesn't work (but I personally delete the "extras" apps as the update process somehow made that possible for me)
Other than all that I'm pretty amazed at the way this devices handles the OS... every time I've gone back to 8.1 I'd instantly regret it after the setup

Hi so I tried installing Interops on my WP 10 HTC but for whatever reason it doenst let me install stating i dont have 10.0.14393.953 or higher but if i recall i have 10.0.15xxx.xxx Im not home so i cannot check the actual numbers.

Cokefrevr said:
Hi so I tried installing Interops on my WP 10 HTC but for whatever reason it doenst let me install stating i dont have 10.0.14393.953 or higher but if i recall i have 10.0.15xxx.xxx Im not home so i cannot check the actual numbers.
Click to expand...
Click to collapse
Are you trying to install interop tools via the store? From what I can recall installing the pre release via device hub worked on all builds for me

Cashdog53 said:
I got the following error after pushing the contents of the M8ATT folder onto my device:
[1] Transferring files complete: 37 files
[1] Installation failed (HRESULT = 0x80004005)
[1] Failed (0x80004005)
ERROR: 0x80004005
Command failed. (HRESULT = 0x80004005)
Is this bad?
---------- Post added at 06:50 AM ---------- Previous post was at 06:30 AM ----------
Never mind. Fixed the problem by removing my SD card, and restarting the phone I think...
Click to expand...
Click to collapse
Everything work out?

AnierinB said:
Are you trying to install interop tools via the store? From what I can recall installing the pre release via device hub worked on all builds for me
Click to expand...
Click to collapse
Yea trying to install from the store, sorry for being stupid really tired but device hub?

Cokefrevr said:
Yea trying to install from the store, sorry for being stupid really tired but device hub?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=71000190&postcount=607
Download arm dependencies and arm interop tools. Extract and install dependencies one by one via file manager before installing interop tools appx.
Oh and it's called the device portal... here's a link to info on that https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile

AnierinB said:
https://forum.xda-developers.com/showpost.php?p=71000190&postcount=607
Download arm dependencies and arm interop tools. Extract and install dependencies one by one via file manager before installing interop tools appx.
Oh and it's called the device portal... here's a link to info on that https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile
Click to expand...
Click to collapse
Thanks, although it seems to be auto closing, then if i open it again it stays loading and auto closes again.

I've got the same problem installing interop tools i've install the dependencies and the appxbundle but when i try to open the program on the phone it only show a logo for a few seconds and go back to the main screen. Is interop tools the only way to modify the devicetargetinfo ? Please advice.

Cokefrevr said:
Thanks, although it seems to be auto closing, then if i open it again it stays loading and auto closes again.
Click to expand...
Click to collapse
rayxanber said:
I've got the same problem installing interop tools i've install the dependencies and the appxbundle but when i try to open the program on the phone it only show a logo for a few seconds and go back to the main screen. Is interop tools the only way to modify the devicetargetinfo ? Please advice.
Click to expand...
Click to collapse
https://forum.xda-developers.com/wi...app-interop-tools-versatile-registry-t3445271
Follow the for all other OEM Device section. Interop tools has changed a bit since I last used the device.
And yes that reminds me.. In worst case you can't get interop tools to work I'm afraid you'll have to change it before you do the offline update via The modified preview for developer's.. But no worries as the WDRT tool can bring you back to 8.1 NP.
Besides that.. How's the experience with w10 on the m8 for you guys?

AnierinB said:
[*]Your PC must be at least Windows 7 Service Pack 1, but you must install every Visual C++ Redistributable Runtime and Windows Device Recovery Tool. Windows 8/8.1/10 are also acceptable.
Click to expand...
Click to collapse
I found that only 2013 was necessary, and specifically the x86 (not x64, even if you have a 64bit computer and 64bit OS) as iutool is a 32bit binary. This link should also be handy for anyone wanting to install all the Visual C redistributables.
AnierinB said:
(If you met error 80070490 when executing iutool -l, disconnect your phone, and delete your phone from Device & Printers section of control panel. Then reconnect your phone again)
Click to expand...
Click to collapse
This didn't work for me on my main computer. Even after I removed ALL windows devices. I got out a burner laptop, installed Win10 fresh and set up the necessary tools and only then did iutool work for me.
AnierinB said:
Besides that.. How's the experience with w10 on the m8 for you guys?
Click to expand...
Click to collapse
Once I can figure how to get Win10 to update, I'll let you know.
[EDIT] WOW, I just found https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile, that I can upload the app using nothing but a browser. All this time I was thinking I'd have to use the USB cable and find yet another deployment tool.. but I still get the same problem as Cokefrevr and rayxanber in that it always auto-closes or crashes.
[EDIT2] Ok, finally found out that anything beyond the 1.9 beta crashes in this old windows build. At least the 1.9 beta runs... now I need to figure out what this cryptic statement means in terms of steps:
AnierinB said:
11. Use any method that you know to modify your model(DeviceTargetingInfo) to a supported W10 Mobile Device
Click to expand...
Click to collapse
[EDIT3] I found https://windowsinsiderbits.blogspot.com/2017/03/upgrading-unsupported-windows-phone-81.html which led me to the steps:
1. Edit registry HKLM/SYSTEM/Platform/DeviceTargetingInfo changing PhoneManufacturerModelName to RM-1105 and PhoneModelName to "Lumia 950" (taken from http://www.lumiafirmware.com/ )
2. Run the Windows Insider app, select the Insider Slow release (it should automatically reboot)
3. Check for updates in the Settings > Update & security > Phone update
Now I'm finally updated to Version 1607 OS Build 10.0.14393.448
[EDIT4] And now that it's on the current windows version, the Interop Tools from the store can run... but it needs some kind of extensions which I think are what is referenced in the 'Other Device' section, but needs Interop Tools to run before extensions can be side-loaded? That doesn't make much sense. I guess I'm fine with my device saying HTC Lumia 950 until Interop works or I find a better simple registry editor without so many complicated dependencies.
[EDIT5] Looks like the RC beta from the originally linked thread works on this version. I have to say, the self-web-host to install applications is by far the easiest way to side-load apps. I think the only thing I miss by going up to Win10 is the dotview. :crying: I hope some awesome developer makes a dot-view addition to Win10. Oh... looks like it's downloading the 1703 version now...

reukiodo said:
I found that only 2013 was necessary, and specifically the x86 (not x64, even if you have a 64bit computer and 64bit OS) as iutool is a 32bit binary. This link should also be handy for anyone wanting to install all the Visual C redistributables.
This didn't work for me on my main computer. Even after I removed ALL windows devices. I got out a burner laptop, installed Win10 fresh and set up the necessary tools and only then did iutool work for me.
Once I can figure how to get Win10 to update, I'll let you know.
[EDIT] WOW, I just found https://docs.microsoft.com/en-us/windows/uwp/debug-test-perf/device-portal-mobile, that I can upload the app using nothing but a browser. All this time I was thinking I'd have to use the USB cable and find yet another deployment tool.. but I still get the same problem as Cokefrevr and rayxanber in that it always auto-closes or crashes.
[EDIT2] Ok, finally found out that anything beyond the 1.9 beta crashes in this old windows build. At least the 1.9 beta runs... now I need to figure out what this cryptic statement means in terms of steps:
[EDIT3] I found https://windowsinsiderbits.blogspot.com/2017/03/upgrading-unsupported-windows-phone-81.html which led me to the steps:
1. Edit registry HKLM/SYSTEM/Platform/DeviceTargetingInfo changing PhoneManufacturerModelName to RM-1105 and PhoneModelName to "Lumia 950" (taken from http://www.lumiafirmware.com/ )
2. Run the Windows Insider app, select the Insider Slow release (it should automatically reboot)
3. Check for updates in the Settings > Update & security > Phone update
Now I'm finally updated to Version 1607 OS Build 10.0.14393.448
[EDIT4] And now that it's on the current windows version, the Interop Tools from the store can run... but it needs some kind of extensions which I think are what is referenced in the 'Other Device' section, but needs Interop Tools to run before extensions can be side-loaded? That doesn't make much sense. I guess I'm fine with my device saying HTC Lumia 950 until Interop works or I find a better simple registry editor without so many complicated dependencies.
[EDIT5] Looks like the RC beta from the originally linked thread works on this version. I have to say, the self-web-host to install applications is by far the easiest way to side-load apps. I think the only thing I miss by going up to Win10 is the dotview. :crying: I hope some awesome developer makes a dot-view addition to Win10. Oh... looks like it's downloading the 1703 version now...
Click to expand...
Click to collapse
Glad you got it working.. Haven't logged in to xda in a while because i'm using micro g on my Android device so sorry about the absence of help. How you liking it so far? HTC should have supported this huh? p.s lumia 735 works best for device spoofing.. 950 is unnecessary

I'm curious, which phone should I change it to in the registry, to receive updates? To make sure it doesn't break?
Also I'm using Interop Tools 1.9 since apparently, everything after that crashes, and I can't unlock Interop/cap it keep turning off. Do you have any pointers to what I should do?

nar001 said:
I'm curious, which phone should I change it to in the registry, to receive updates? To make sure it doesn't break?
Also I'm using Interop Tools 1.9 since apparently, everything after that crashes, and I can't unlock Interop/cap it keep turning off. Do you have any pointers to what I should do?
Click to expand...
Click to collapse
What carrier do you have? I used an ATT varient and before using the offline update I used the custom preview for developers method to change my device to a lumia 735 on wp 8.1 then did the offline update because interop tools kept failing for me at the time as well. if I remember correctly, you can also use interop tools to change the device targeting info but nothing else if you can't cap unlock/ interop unlock your device.
And about cap unlocking your device:
Download the NDTK packages and the WPAK utilities
Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
Put the two NDTK cabs in one empty folder on your PC
Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored >" with your phone connected into the PC
if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click
on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.

AnierinB said:
What carrier do you have? I used an ATT varient and before using the offline update I used the custom preview for developers method to change my device to a lumia 735 on wp 8.1 then did the offline update because interop tools kept failing for me at the time as well. if I remember correctly, you can also use interop tools to change the device targeting info but nothing else if you can't cap unlock/ interop unlock your device.
And about cap unlocking your device:
Download the NDTK packages and the WPAK utilities
Go to the Interop Unlock section of Interop Tools, and tap the button that says "Enable installing NDTK on any device"
Put the two NDTK cabs in one empty folder on your PC
Open a command prompt as administrator and make sure you're in the directory where the iutool executable is located from the WP(AK) zip
run "iutool -V -p "<fulllocationwherethetwondtkpackagesarestored >" with your phone connected into the PC
if iutool throws an error, please unplug your device, go to the control panel, devices and printer, select your phone, should be ghosted, click
on uninstall device, and then replug the device and wait for it to reinstall. If you still have issues, run GETDULOGS from the same CMD prompt, and post the cab you get along with a message in this thread
When the installation is finished, open Interop Tools, go to the Interop Unlock section, and tap restore the original manufacturer info button.
Click to expand...
Click to collapse
Am I supposed to do all this on my computer, or the phone? And I don't have the "NDTK" button on Interop 1.9 on my M8 (It's the AT&T version, if that helps)

Yet Another Universal ADB Driver Package and adbupdater for Windows

I made this installer as a kind of "update" the old driver package I had made for Ainol and Actions before.
While at it I added those two tools usually used, that is adb and fastboot.
Based on batch scripts, so it's open source.
Self Signed, not need to do annoying reboots and other tricks.
Tested working using VirtualBox, from XP to Win10, both 32 and 64 bit. Edit: Tested working on Win11.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
(five seconds wasted)
Download: https://yadi.sk/d/Xwt9cfb73HFhgA
The Readme.txt included is below.
-------------------------------------------------------
Yet Another Universal ADB Driver Package (+adbupdate)
-------------------------------------------------------
By CXZ (Slatedroid,Freaktab) / CXZa (XDA,4pda)
http://cxzstuff.blogspot.com
DISCLAIMER: No guarantee of any kind. Use at your own risk!
-------------------------------------------------------
Yet Another Universal Android Debug Bridge USB Driver
-------------------------------------------------------
Uses universal adb trick used in some (unsigned) packages before.
It works but fails in inf2cat signability test. Maybe there are reasons for that?
Signability test failed. Errors:
All Universal Serial Bus (USB) devices must have VID and PID sections in the PnP Device ID string.
Third-party USB function drivers must not install through a compatible ID match.
The following formats are not acceptable:
USB\Class_ii, USB\Class_ii&SubClass_jj, USB\Class_ii&SubClass_jj&Prot_kk
Can be uninstalled through the Control Panel.
Other choices: https://www.google.com/search?q=adbdriver
-----------------------------------------------------------
Leave YAUADBdriver certificate to the cert stores
-----------------------------------------------------------
Instead of deleting the YAUADBdriver certificate after
installing the driver, it's left into the certificate stores.
This is maybe needed in the newer Win10 versions. --> http://
www.anandtech.com/show/10747/examining-win10au-driver-signing-policy
Should be safe as certificates cannot be used without the
private key and I deleted the self signed certificate used
immediately after signing the driver. Certificate will
be added to Root and TrustedPublisher stores having
"___YAUADB-driver" as its name so it's easy to find.
-----------------------------------------------------------
ADB-Prompt (bat), ADB (version 1.0.32) and Fastboot
-----------------------------------------------------------
Installer just extracts the files to the chosen folder
and creates shortcuts to the SendTo subfolder.
Read the Readme.txt in SendTo subfolder for more info.
To uninstall just delete the folder (and shortcuts created).
There are newer versions than 1.0.32, but it was selected
on purpose because it's the last version that remembers
the previous shell commands used.
If a newer is needed use my "Yet Another ADB + Fastboot Updater"
which is now included in the package. For more info --> https://
https://forum.xda-developers.com/an...er-package-t3595277/post74097138#post74097138
ADB-Prompt (bat) allows one to avoid typing that darn
"adb" before every single adb command...
-------------------------------------------------------
ADB Prompt - h=open adb help in notepad, q=quit, c=cmd /k
v=add vendor IDs to adb_usb.ini, r=root+remount
-------------------------------------------------------
Remove the old ADB OEM Driver installations
-------------------------------------------------------
Uninstalls all the oem*.inf ADB Driver installations
including the YAUADBdriver (if it's installed).
(use the Control Panel for uninstalling the YAUADBdriver)
-------------------------------------------------------
Remove the old ADB Driver registry entries
-------------------------------------------------------
Removes the old ADB Driver registry entries.
Reboot possibly needed before ADB can be used.
-------------------------------------------------------
Looking for adbupdater or adbupdate? See the eighth post.
https://forum.xda-developers.com/an...er-package-t3595277/post74097138#post74097138

Changed but not updated.
Just minor adjustment done so that the version number is the same everywhere.
So, no need to re-download.

Suddenly like a hundred downloads more at the Yandex.
Either this has been praised elsewhere by someone, or that
someone has problems downloading from the Yandex link.
That many download problems? Probably not - but
here is a local download link - just in case.
edit: This local package doesn't include Yet Another ADB + Fastboot Updater - yet.
You can download it from here: https://forum.xda-developers.com/an...er-package-t3595277/post74097203#post74097203
PS: Please, do NOT share this elsewhere (Yandex link or this ok).
I want to be able to update if necessary.
edit: attachment removed. Use Yandex link instead. A bit easier if less places.
Download: https://yadi.sk/d/Xwt9cfb73HFhgA

Over 300 downloads, but no comments (nor thanks) what so ever.
Did I manage to do it too good at the first time?
(AFAIK, this installer is the only one - at the moment - being truly universal and in the same time
correctly signed. Checked some like a year ago, but I don't think they have changed much.)
(snip)

Hi, just checked your tool... i m in bootloop of death, can your tools unlock my Bootloader in fastboot command ? i m not able to access Recovery (Stoct or TWRP) .. only fastboot i can access

vijaygogawale said:
Hi, just checked your tool... i m in bootloop of death, can your tools unlock my Bootloader in fastboot command ? i m not able to access Recovery (Stoct or TWRP) .. only fastboot i can access
Click to expand...
Click to collapse
I believe it depends on what kind of bootloader and tablet you have there.
I have fastboot in one MTK tablet only. I don't think its bootloader was locked.
And with it it's easier to use their flashing tool. So I haven't used fastboot much myself.
The adb (and also fastboot) in this installer is a bit older - on purpose.
I think that it might be better that you use the latest versions instead.
https://dl.google.com/android/repository/platform-tools-latest-windows.zip

CXZa said:
Over 300 downloads, but no comments (nor thanks) what so ever.
Did I manage to do it too good at the first time?
(AFAIK, this installer is the only one - at the moment - being truly universal and in the same time
correctly signed. Checked some like a year ago, but I don't think they have changed much.)
(snip)
Click to expand...
Click to collapse
Thank you for "YAUADP" it worked flawless on my Windows 8.1 x64.
Don't worry about having huge download counts but no thanks or replys.
This forum has grown so big. There are alot of passive users. Who download but don't comment or click thanks.
Simply count your downloads as "thanks"

Yet Another ADB + Fastboot Updater
I was about to add this ADB + Fastboot Updater tool into the YAUADBdriver package,
but decided to publish it is as separate download instead.
Just put it to the ADB-Prompt folder and run to update the programs if needed.
This stand alone program can also be used without the YAUADBdriver .
Just put it any folder (preferably to an empty one) and run...
Download the exe: https://yadi.sk/d/UWsvoEsV3ReyeJ
Download zipped: https://yadi.sk/d/nZTi7Eqx3NcBwW
Tested working using Win7, Win8 and Win10.
DISCLAIMER: No guarantee of any kind. Use at your own risk!
The Readme included is below. (It, ini and bat files will be extracted on the first run.)
----------------------------------------------------------------------------
Yet Another ADB + Fastboot Updater
(companion for Yet Another Universal ADB Driver Package)
----------------------------------------------------------------------------
by cxz (slatedroid,freaktab) / cxza (4pda.ru,xda) /
http://cxzstuff.blogspot.com/
-------------------------------
Key names used in adbupdate.ini (extracted on the first run)
-------------------------------
adburl - from where to download the zip archive (platform-tools-latest-windows.zip)
https://dl.google.com/android/repository/platform-tools-latest-windows.zip
http://dl-ssl.google.com/android/repository/platform-tools-latest-windows.zip
adbolddate - previous file time at the server.
adboldsize - previous file size at the server.
daysbetweenchecks - check updates every X days. if 0 (zero) startup check is not done.
to enable startup check, define the value and run the program once.
program's shortcut is then created to "Start Menu/Startup" folder.
to disable startup check, change value to 0 and run the program once.
lastcheck - when the latest check was done
adbupdateerror - if more than 0 and startup check is on, checking is done on the next startup.
startupdelayminutes - delay checking X minutes at the startup.
targetfolder - define where to extract ADB + Fastboot files. Run program as Admin and
use for example C:\windows as the target folder to run them system-wide.
addtothepath - if "a", add current exe dir or the target dir to the path and use adb system-wide.
removing: change to "r", and re-run to remove targetfolder/current dir from the path.
(do not change the targetfolder value if any, or removing it from the path will fail)
(value "ok" means that the folder is now in the path variable)
useragent - define the user-agent used. max 256 characters.
makebackups - backup the files to be replaced to the adbupdate.exe\~backup folder. 1=yes.
keepthezip - the platform-tools zip is saved to the adbupdate.exe\~platform-tools folder. 1=yes.
extractfile1 - files to be extracted. 1, 2, 3 and so on. Use full paths inside the zip.
the files are extracted to the targetfolder/adbupdate.exe folder
without using the paths inside the zip.
Both ADB and Fastboot are terminated if running before updating
(or installing if the ADB is not in the target folder).

Yet Another ADB + Fastboot Updater
Local copy. Removed. See the previous post.
Added it also to the Yet Another Universal ADB Driver Package zip but not into the installer yet.
PS: Please, do NOT share this elsewhere (Yandex link or this ok).
I want to be able to update if necessary.

Yet Another ADB + Fastboot Updater
Update. The download addresses are the same.
Now ADB + Fastboot are only terminated if they are updated/installed.
Also added a batch file for automatically checking updates and updating
ADB + Fastboot if they are installed system-wide (e.g. c:\windows folder,
keep adbupdate.exe in another folder so windows update doesn't remove it)
(if previously downloaded just the exe, delete the readme file to get its last version.)
edit:
adbupdate_scheduled-task batch file removed. It works, but I forgot that
(after xp?) windows does not allow user interface on system tasks. Sorry.

Yet Another ADB + Fastboot Updater
CXZa said:
adbupdate_scheduled-task batch file removed. It works, but...
Click to expand...
Click to collapse
A version in which above works, or a such that adds the target folder to the path
thus allowing system-wide usage might come some day in the near future.
In the meanwhile system-wide ADB can be updated "semi-automatically" like this .
Use two folders. One that checks updates, and another that has c:\windows as the target folder.
Then when a new update is found, let it update the first one and then run another as admin.

Disabled commenting at Yandex downloads.
Someone has been posting there a download link of a small
executable telling (in Russian) that it would be an updated version.
It is not. It could be a virus, so do NOT execute it!
Комментирование отключено в Яндекс.
Кто-то отправил ссылку, чтобы загрузить небольшую
исполняемый файл, говорящий, что это будет обновленная версия.
Не является. Это может быть вирус, поэтому НЕ запускайте его!

Hi, I wanted to try your installer but I got a little bit confused by all the packages and updates
Which one is the right one to install?

provolinoo said:
Hi, I wanted to try your installer but I got a little bit confused by all the packages and updates
Which one is the right one to install?
Click to expand...
Click to collapse
The one that is mentioned in the 1st post is always the latest.
This one: https://yadi.sk/d/Xwt9cfb73HFhgA
Now it has "Yet Another ADB + Fastboot Updater" included, but as separate installation - one doesn't have install it.
Latest "Yet Another ADB + Fastboot Updater" as separate installer program:
https://forum.xda-developers.com/an...er-package-t3595277/post74097138#post74097138
(the yadi.sk download addresses always stays the same )

provolinoo said:
Hi, I wanted to try your installer but I got a little bit confused by all the packages and updates
Which one is the right one to install?
Click to expand...
Click to collapse
So, what was the result? YAUADBdriver should work with any device.
Universal adb driver packages are a good option when one doesn't have
a driver package meant for your device. But obviously it's always best to
use a driver package by the manufacturer...

Yet Another ADB + Fastboot Updater
CXZa said:
A version in which above works, or a such that adds the target folder to the path
thus allowing system-wide usage might come some day in the near future.
Click to expand...
Click to collapse
Okay, I now updated the Yet Another ADB + Fastboot Updater.
It now has option to add target or the exe path to the path variable
thus enabling using adb system-wide without big windows updates
messing it by removing exe from the win subdirs.
(It wasn't really a big problem, easily fixed by re-running the program. Then again,
adding dir to the PATH has that advantage that admin rights aren't needed anymore
thus enabling that automatic adb update to work better when adb is used system-wide...)
Anyway, now are all the files at Yandex(yadi.sk) updated.
(The Yet Another Universal ADB Driver Package has still adbupdate as separate exe in its own folder.)
Here are the download links again for those lazy ones:
Yet Another Universal ADB Driver Package: https://yadi.sk/d/Xwt9cfb73HFhgA
Yet Another ADB + Fastboot Updater as exe: https://yadi.sk/d/UWsvoEsV3ReyeJ
Yet Another ADB + Fastboot Updater zip-file: https://yadi.sk/d/nZTi7Eqx3NcBwW
PS: If you have used an older adbupdate before, remove/rename the old ini and readme files in its folder
in order to get them updated as well.

Yet Another ADB + Fastboot Updater
Nice round number of downloads after this last update.
Altogether four and half thousand or more. That is if these two
program DLs are put together. Any feedback/suggestions of any kind?
There was some asking in "15 second installer" thread about device not showing.
The reason probably is that it, at least when I previously checked, uses Google's
vendor ID. If your device manufacturer use its own, you have to install driver
package provided by them, or use some universal one - like this YAUADBDriver...

CXZa said:
Nice round number of downloads after this last update.
Click to expand...
Click to collapse
Was 666. Not that round really. But now it is, the last update has exactly one
thousand downloads altogether...
To my knowledge these two packages of mine work as expected.
So they are not updated anymore - unless the users give some good reasons for it...

CXZa said:
To my knowledge these two packages of mine work as expected.
So they are not updated anymore - unless the users give some good reasons for it...
Click to expand...
Click to collapse
In another thread I came to think that some beautiful day the adbUpdater might not work anymore. But no worry, an update is coming soon before that. Then you can decide what files to extract, etc...
At the moment it doesn't extract for example the libwinpthread-1.dll as it was only used like one fastboot version. I don't know why it's still in the zip. Maybe it's used for something else?? Please tell if you know more, or if your device needs it, etc...
So, what to download from this a bit messy thread of mine? Here are the links again:
Yet Another Universal ADB Driver Package: https://yadi.sk/d/Xwt9cfb73HFhgA
Yet Another ADB + Fastboot Updater as exe: https://yadi.sk/d/UWsvoEsV3ReyeJ
Yet Another ADB + Fastboot Updater zip-file: https://yadi.sk/d/nZTi7Eqx3NcBwW

@kk131
There is one my friends again giving me thanks. Thanks buddy for your support!
(BTW, if you all would say something it would easier for me to thank you back... )

ADB no longer works with devices I have used for years

I originally posted in the "Ask ANY Question. Noob Friendly" thread but got no replies so am trying again in its own thread. I just find it hard to believe no one has seen a similar problem anywhere....
ILikeOldStuff said:
I've been using ADB for some years on several devices but recently ran into a snag. On the same machine (an older desktop running XP) where it has always worked before, I recently tried to use it but got an odd error message:
E:\platform-tools> adb version​Android Debug Bridge version 1.0.32​Revision 57224c5cff69-android​​E:\platform-tools> adb devices -l​List of devices attached​* daemon not running. starting it now on port 5037 *​ADB server didn't ACK​*failed to start daemon *​error: cannot connect to daemon: No error​error: cannot connect to daemon: No error​​I tried to google it but everything I found either assumed there was a problem with eclipse, with wifi, with not using correct cables, not installing drivers, etc. But NOTHING about a case where it used to work but for some reason no longer does.
I do not (and never did have) have eclipse, nor even the android SDK installed, just the much smaller platform-tools thing. The desktop box does not have any wifi radio hardware so I can rule those out. It also is not a usb port or cable issue as I can still transfer files through MTP.
It is not really a device issue as it suddenly started happening on ALL android devices including ones I used it on before. And it isn't a case where the device updated to change anything as these are older devices running FroYo, IceCreamSandwich, Jellybean, and Oreo, where updates stopped many years ago.
I don't think it is a device driver issue as all devices I tried do show up properly in device manager.
The last time it worked was 25Sep2022 when I adjusted some permissions on the BetterBatteryStats app. I did not need it again until recently when it started doing the above error message.
Has anyone seen anything similar or have an idea how to fix it?
Click to expand...
Click to collapse
I will add that I have tried disabling AV and adding extra permissions to the firewall (which were never needed before as the process was always local) to no avail. I have never had genymotion installed (another common culprit according to various google hits). There does not seem to be anything useful in system event logs either. And Task Manager does show the adb process is indeed running.
One question I have , is how to get more clues for solving this problem. I thought firewall logs might show if that was blocking anything, so set it to log all connection activity attempts but it is not showing up in firewall logs, which makes me think the problem is elsewhere.
I see that some apps can write things to system event logs, but ADB seemingly has not done this. Is there some setting to make it write event log entries, or any other way it can be made to write some debug logging details somewhere?
Any other thoughts of how to solve this?

To start, I suggest using the latest version of platform-tools-latest-windows.zip.
or use mAid:
[LIVE-ISO][mAid][v4.0] manage all your Android devices without driver hassle
is now: (read here why) About The existence of mAid (abbreviation for [m]anage your [A]ndro[id]) has a simple reason. I wanted to have something where I were able to point users to when they came with issues on Windows because the most...
forum.xda-developers.com

Update ADB: dowmload latest version from here
Releases · K3V1991/ADB-and-FastbootPlusPlus
A small Application for Windows that allows you to install the latest Version of ADB and Fastboot Files on the Computer without installing the entire Android SDK Package + Toolkit & Commands - ...
github.com
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

ze7zez said:
To start, I suggest using the latest version of platform-tools-latest-windows.zip.
or use mAid:
Click to expand...
Click to collapse
Sadly I can't do either of these. Platform tools R23 (that I have been using) is the last one that is compatible with Windows XP. And this desktop box is running on an old P4 processor, which is 32bit only, with no hardware support for virtualization either, so mAid does not look compatible.
xXx yYy said:
Update ADB: dowmload latest version from here
Click to expand...
Click to collapse
Again, that looks like too new of a version of platform_tools to be compatible with XP.
But thank you both for at least trying to help!
What bugs me, is that debugging mode USED to work, until recently when it didn't.

ILikeOldStuff said:
...
Again, that looks like too new of a version of platform_tools to be compatible with XP.
...
Click to expand...
Click to collapse
The ADB driver ( has nothing to do with platform tools package ) since ever is 32-bit, hence it will work with Windows XP, too.

xXx yYy said:
The ADB driver ( has nothing to do with platform tools package ) since ever is 32-bit, hence it will work with Windows XP, too
Click to expand...
Click to collapse
While it may be still 32 bit, it does not work anymore with Windows XP since it uses functions that are only available in Vista & up. It gives an error message:
The procedure entry point WSAPoll could not be located in the dynamic link library WS2_32.dll.​

Time to change OS version or update WS2_32.DLL ( read: WinSock 2 DLL - the system file that contains the Windows Sockets API, an important software that is used to run most network and internet applications ) .

Right, v23 is latest version working for Windows XP (and still works). delete the %userprofile%\.android folder and try again (do backup if necessary)

alecxs said:
delete the %userprofile%\.android folder and try again
Click to expand...
Click to collapse
This took a little longer before it eventually gave a similar error message :
E:\platform-tools> adb devices -l​List of devices attached​* daemon not running. starting it now on port 5037 *​* daemon started sucessfully *​** daemon still not running​*failed to start daemon *​error: cannot connect to daemon: No error​error: cannot connect to daemon: No error​​but Task Manager shows adb.exe is indeed running, and my firewall log reports that adb.exe is listening on port 5037, and is not blocked.

what firewall? is that the cause? disable completely?

Comodo 3.14.130099.587
I don't really think it is the cause, it has been running on the machine since even before the first use of ADB and never caused an issue before, allowing ADB to work in the past. Also ADB has never showed up in the logs as having been blocked.
I might try disabling it later tonight when I get home.

do a search on whole disk for other adb.exe make sure you haven't running multiple instances.

ILikeOldStuff said:
...
​but Task Manager shows adb.exe is indeed running, and my firewall log reports that adb.exe is listening on port 5037, and is not blocked.
Click to expand...
Click to collapse
In a previous post you stated ADB.EXE doesn't work due to missing or invalid shared system library file named WS2_32.DLL file.
Why not fix this issue as 1st thing of all things?
ws2_32.dll free download | DLL‑files.com
Download ws2_32.dll free! Fix DLL missing error. Solve it yourself or get help using DLL‑files.com Client to fix DLL error automatically.
www.dll-files.com

xXx yYy said:
In a previous post you stated ADB.EXE doesn't work due to missing or invalid shared system library file named WS2_32.DLL file.
Why not fix this issue as 1st thing of all things?
Click to expand...
Click to collapse
It is neither missing nor invalid. There is Ws2_32.dll version 5.1.2600.7074 present in \Windows\system32. This is the latest version for XP, from installing MS16-077 KB3161949 ; it just does not have (and was never intended to have) the WSAPoll function that was introduced in Vista.
This error message only happens if I try to run the latest version of ADB, which is no longer compatible with XP. I do not see this when I stay with the r23 version that is the last one compatible with XP.
xXx yYy said:
Time to change OS version or update WS2_32.DLL
Click to expand...
Click to collapse
Installing a newer Windows OS is not really an option for this older hardware; it just does not have the RAM nor CPU horsepower for anything beyond XP. There is also the lack of device drivers for older hardware, and I am not willing to do without such "frills" as a working video card, ethernet adapter, parallel printer port, and other items which I use on a daily basis but are not supported by W10.

alecxs said:
what firewall? is that the cause? disable completely?
Click to expand...
Click to collapse
ILikeOldStuff said:
Comodo 3.14.130099.587
I don't really think it is the cause . . .
I might try disabling it later tonight when I get home.
Click to expand...
Click to collapse
I finally got around to trying this, and it turns out you were right and I thought incorrectly. So thanks for the reminder to re-check the obvious.
alecxs said:
do a search on whole disk for other adb.exe make sure you haven't running multiple instances.
Click to expand...
Click to collapse
The only other copies of adb.exe that I have are inside the .zip files for other newer (no longer XP compatible) versions of platform-tools. I left them inside the .zip files and unzipped only the r23 version to prevent accidentally running the wrong ones.
Task Manager mostly only showed the one instance. The only time I could see multiple was when I disabled the firewall, started one, re-enabled the firewall, then did another "adb devices -l"; repeating this sequence several times would produce one additional instance for each repeat. Using task manager to kill the extras allowed the remaining one to work properly provided the firewall was disabled.
So I can still run the r23 version of ADB after all, although the workaround of disabling first the ethernet and then the firewall is inconvenient to say the least, and hardly ideal.
I am still confused why Comodo FW clearly is blocking this while not logging that action. And also why it is blocked at all when I am using only a USB cable and neither ethernet nor wifi networks. Even moreso why it USED to work with no need to disable the firewall but no longer does.
Looks like getting these other questions sorted will need some visits to the Comodo forums.

adb client communicates with adb server via TCP. here is list of ports you must whitelist in firewall.
https://developer.android.com/tools/adb