Database Develop

[TUT] Dummies guide: updating HTC USB Sync Drivers

First of all you will need to download the drivers attached in this post and extract them. Remember where you extract them to!
The main reason for updating these drivers is so that you can use USPL or MTTY. USPL is an alternative to HSPL and is used for flashing roms. MTTY is used for retrieving information from the HTC bootloader as well as setting certain things. One of the more popular uses for MTTY is to clear the rom update error code in the bootloader after a failed flash.
The drivers that come with Windows for the HTC Bootloader are incompatible with USPL and MTTY. Once you update the driver with this guide you will be able to use USPL and MTTY.
Now that you have the drivers downloaded and extracted you need to know which version of Windows you have.
If you have Windows XP go to post 2
If you have Windows Vista or Windows 7 go to post 3
MOD EDIT
If you have previously updated drivers and successfully flashed a rom before you do not need to update drivers again. If 'usb' is not displayed at bottom of bootloader when connected to pc, simply reboot, press F8-key & select option to ignore the signature. Phone should now state 'usb' in bootloader to enable you to flash rom

Windows XP
Use this method only if you have Windows XP!
Before you start this, put your phone into its bootloader and plug it into your computer via the USB cable. Your phone should show USB at the bottom of the bootloader screen. It is very important not to skip this!
If you have ActiveSync installed, start at step WXP1. Otherwise skip to step WXP4.
WXP1 - Downloads
(WXP1a) Drivers.zip
(WXP1b) Extract each item to its own folder
WXP2 - Open ActiveSync and click File, Connection Settings.
{
"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"
}
WXP3 - Uncheck Allow USB connections and click OK and then close ActiveSync.
WXP4 - Press Start menu, Run, type in devmgmt.msc, and press OK. Or you can press and hold the Windows and R keys. This also brings up the Run dialog.
WXP5 - In the Device Manager locate Windows CE USB Devices and expand it. Double-click on HTC USB Sync.
WXP6 - In the HTC USB Sync Properties click the Driver tab and then Update Driver.
WXP7 - In the Hardware Update Wizard, click the No, not this time radio button and then click Next.
WXP8 - Continuing in the Hardware Update Wizard, click the Install from a list or specific location radio button and then click Next.
WXP9 - Continuing in the Hardware Update Wizard, click the Don't search. I will choose the driver to install radio button and then click Next.
WXP10 - Continuing in the Hardware Update Wizard, click the Have Disk button.
WXP11 - In the Install From Disk dialog, click the Browse button.
WXP12 - In the Locate File dialog, browse to where you downloaded the driver. Select the 32-bit folder if you use the 32-bit edition of Windows, or select the 64-bit folder if you use the 64-bit edition. Select wceusbsh.inf and click the Open button.
WXP13 - Back in the Hardware Update Wizard, select the HTC USB Sync and click Next.
WXP14 - Continuing in the Hardware Update Wizard, you will see an error: This device cannot start. (Code 10)
This is totally normal, do not worry. Click Finish.
WXP15 - The Device Manager will show an exclamation point next to the HTC USB Sync. Unplug the USB cable from your phone. You will notice the bootloader on your phone change from USB to Serial.
WXP16 - The Device Manager will no longer show the HTC USB Sync. Plug the USB cable back in to your phone. You will notice the bootloader on your phone change from Serial to USB. The Device Manager will now show the HTC USB Sync as fully functional. You are done!

Windows Vista / Windows 7
Use this method only if you have Windows Vista or Windows 7!
Before you start this, put your phone into its bootloader and plug it into your computer via the USB cable. Your phone should show USB at the bottom of the bootloader screen. It is very important not to skip this!
If you have the 64-bit edition of Windows you must disable digital driver signing before you continue on! To do this, restart your computer. After the initial BIOS screen but before the Windows bootup splash screen, spam press F8 until you see a Windows menu. If you do not get a menu and end up in Windows you pressed F8 at the wrong time. Try it again until you get the menu. In the menu select Disable Driver Signature Enforcement or Disable Digital Driver Signing (depending on your version of Windows). Windows will finish booting up and you can continue on.
If you have Windows Mobile Device Center installed, start at step WV1. Otherwise skip to step WV4.
WV1 - Downloads
(WV1a) Drivers.zip
(WV1b) Extract each item to its own folder
WV2 - Open Windows Mobile Device Center, hover over Mobile Device Settings and click Connection Settings.
WV3 - Uncheck Allow USB connections and click OK and then close Windows Mobile Device Center.
WV4 - Press Start menu, Run, type in services.msc, and press OK. Or you can press and hold the Windows and R keys. This also brings up the Run dialog.
WV5 - Make sure both the Windows Mobile 2003-based device connectivity and Windows Mobile-based device connectivity services show Started. If they are not, start them.
WV6 - Press Start menu, Run, type in devmgmt.msc, and press OK. Or you can press and hold the Windows and R keys. This also brings up the Run dialog.
WV7 - In the Device Manager locate Mobile Devices and expand it. Double-click on HTC USB Sync.
WV8 - In the HTC USB Sync Properties click the Driver tab and then Update Driver.
WV9 - In the Update Driver Software Wizard, click the Browse my computer for driver software button.
WV10 - Continuing in the Update Driver Software Wizard, click the Let me pick from a list of device drivers on my computer button.
WV11 - Continuing in the Update Driver Software Wizard, click the Have Disk button.
WV12 - In the Locate File dialog, browse to where you downloaded the driver. Select the 32-bit folder if you use the 32-bit edition of Windows, or select the 64-bit folder if you use the 64-bit edition. Select wceusbsh.inf and click the Open button.
WV12 - Back in the Update Driver Software Wizard, select the HTC USB Sync and click Next.
WV14 - Continuing in the Update Driver Software Wizard, you will see a message: The hardware you installed will not work until you restart your computer.
This is not true at all, do not restart. Click Finish.
WV15 - The Device Manager will show an exclamation point next to the HTC USB Sync. Unplug the USB cable from your phone. You will notice the bootloader on your phone change from USB to Serial.
WV16 - The Device Manager will no longer show the HTC USB Sync. Plug the USB cable back in to your phone. You will notice the bootloader on your phone change from Serial to USB. The Device Manager will now show the HTC USB Sync as fully functional. You are done!

A big noobish question: what are these drivers meant for?? what are the benefits of installing them??

Kristaps-K9-Lv said:
A big noobish question: what are these drivers meant for?? what are the benefits of installing them??
Click to expand...
Click to collapse
Also interested in this one. Haven't heard of them so far ?

Kristaps-K9-Lv said:
A big noobish question: what are these drivers meant for?? what are the benefits of installing them??
Click to expand...
Click to collapse
johnpatcher said:
Also interested in this one. Haven't heard of them so far ?
Click to expand...
Click to collapse
If you want to use USPL or MTTY.

excellent tutorial cRaCKwHoRe. that would save lots of time to answer same questions over and over again.

cRaCKwHoRe, you are such a wonderful person...
Your guide is even better & more comprehensible than the one over at Modaco!
Thank you!

Wonderful piece of work bro... another amazingly easy tutorial...

Thanks, CrAcKwHoRe
this thread need a glue

Thanks for your work
GREAT WORK HERE. WISH THIS WAS AROUND WHEN I FIRST HAD TO DO IT. THANKS FOR YOUR DEDICATION OF HELPING OTHERS AS ALWAYS.

I haven't in device manager windows CE USB devices
I tried reinstall ActivSync 4.5 without any results.
How can I fix this problem?
Thanks for the help

zoltrix3 said:
I haven't in device manager windows CE USB devices
I tried reinstall ActivSync 4.5 without any results.
How can I fix this problem?
Thanks for the help
Click to expand...
Click to collapse
Are you putting your phone in the bootloader before you connect it to your PC via USB?

cRaCKwHoRe said:
Are you putting your phone in the bootloader before you connect it to your PC via USB?
Click to expand...
Click to collapse
No
That was the reason
Thanks

I'm about to attempt this driver update, but I have a conflict with your instructions.
Your instructions hint that there should be a 32-bit folder and a 64-bit folder inside the drivers.zip file. I just see 6 individual files. Is it okay to proceed with extracting all six files to a single folder and updating the driver with the wceusbsh.inf file?

ModernMuseum said:
I'm about to attempt this driver update, but I have a conflict with your instructions.
Your instructions hint that there should be a 32-bit folder and a 64-bit folder inside the drivers.zip file. I just see 6 individual files. Is it okay to proceed with extracting all six files to a single folder and updating the driver with the wceusbsh.inf file?
Click to expand...
Click to collapse
I just downloaded the attachment from the first post. When I open the archive in Winrar on Winzip I see two folders, 32-bit and 64-bit. I get the same directory structure when I unzip them...

cRaCKwHoRe said:
I just downloaded the attachment from the first post. When I open the archive in Winrar on Winzip I see two folders, 32-bit and 64-bit. I get the same directory structure when I unzip them...
Click to expand...
Click to collapse
I've tried it on two PC's and got the same result: 7 files in one directory - the first five appear to be 32-bit and I extracted those five to a directory on my PC:
WceRndis.cat
WceRndis.inf
wceusbsh.cat
wceusbsh.inf
wceusbsh.sys
(64-bit files wceusbsh.sys and wceusbshx64.inf appear to be the only 64-bit files and I did not extract them)
I believe I updated the drivers successfully, but when using USPL to update the phone to 1.54 SPL (step USPL3), it gets stuck at 0% and then sends me into a Recovery sequence.
Anyone got any ideas? I need to get this done ASAP before I leave the country.

ModernMuseum said:
I've tried it on two PC's and got the same result: 7 files in one directory - the first five appear to be 32-bit and I extracted those five to a directory on my PC:
WceRndis.cat
WceRndis.inf
wceusbsh.cat
wceusbsh.inf
wceusbsh.sys
(64-bit files wceusbsh.sys and wceusbshx64.inf appear to be the only 64-bit files and I did not extract them)
I believe I updated the drivers successfully, but when using USPL to update the phone to 1.54 SPL (step USPL3), it gets stuck at 0% and then sends me into a Recovery sequence.
Anyone got any ideas? I need to get this done ASAP before I leave the country.
Click to expand...
Click to collapse
When you use USPL does it "reboot" your phone and show SPL 1.15.USPL?

cRaCKwHoRe said:
Are you putting your phone in the bootloader before you connect it to your PC via USB?
Click to expand...
Click to collapse
Guys i'm italian and i don't understand this piece and i don't able to install that drivers ._.
Anyone can help me?

Lilith_v2 said:
Guys i'm italian and i don't understand this piece and i don't able to install that drivers ._.
Anyone can help me?
Click to expand...
Click to collapse
Bootloader screen = Tri-colour screen
1. Turn off device
2. Hold down Volume down
3. Turn on device & continue to hold down volume down
You will enter a tri-colour screen. This is bootloader.
You need to be in bootloader before connecting your computer to phone.
Sorry this is not in Itailian. Hopefully you understand

ADB Driver - Access is Denied

So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
HTC ADB Composite Device Driver (not sure exactly of this...)
Access is Denied
Click to expand...
Click to collapse
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.

Stigy said:
So I just installed Windows 7 on my machine and was trying to ADB with my Android since I used it ALL the time on Windows XP.
I put the phone in Debug mode and plugged into my computer and told it the location of the driver. It seems to work well for a second and then it tells me that there was a problem installing the driver. It then says:
Anyone else seeing anything similar on Vista or Windows 7? BTW I already tried this in Safe Mode as well.
Click to expand...
Click to collapse
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess

xidominicanoix said:
I have mines working perfectly on Win7. Maybe you don't have admin rights on your computer? Just a guess
Click to expand...
Click to collapse
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.

Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around

http://forum.xda-developers.com/showthread.php?t=532719
The link in this thread usbdeview seems to fix alot of driver issues

Stigy said:
Nope I have administrative rights and even tried it in safe mode.
Would you be able to zip up the drivers you used or link to where you downloaded them from?
So strange.
Click to expand...
Click to collapse
i got mines from the 1.6 sdk .. x64

Simple Solution
Here is a simple solution without having to read that long thread:
For future reference, here is how to install the drivers or fix the drivers should they not be working.
Everything you need is contained within this:
http://www.divshare.com/download/8845496-f72
This is the howto documentation
This is how to get your android phone to connect to you PC
to use functions like adb and other developer tools.
If you have installed the phone before but adb function dont work
then:
1) Run USBDeview
2) Select the list item(s) that have the word "android" within the description
3) Right Click > Uninstall
If you have done the above, or are plugging your phone in for the first time:
1) Plug in phone
2 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
2 b) If no message appears or you get a message saying drivers failed
to install. Goto device manager
2 b i) start > All Programs > accessories > run
type devmgmt.msc and press ok.
3 b) find the android device in device manager, it will have a warning icon
next to it and be in a section like unknown.
4 b) Right click and install driver
5 a) When prompted to install drivers select the "android driver" folder
contained within this tutorial
Click to expand...
Click to collapse

USBDeview is awesome but....
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.

digimancer said:
Even after removing all of the drivers associated with my device, as soon as I try to install the fresh new drivers, I still get "Access Denied" at the end of the install.
Click to expand...
Click to collapse
I have this same issue on an Ideos U8150 and on XP... At one point in the past it was working (before I flashed Cyanogen 7). Since then I have tried numerous driver packages, both specific to my phone and generic, and have had no luck getting past the access denied error.. I have even gone as far as changing the registry permission as well as checking all of my folder permissions... I am stumped.

Adb root - run that from command prompt.

B-man007 said:
Even if you have admin rights, UAC can f it up.
Make sure you right click on command prompt and click "Run as Administrator"
Also, do you have x64? That requires a signed drivers. I don't remember if the ADB drivers were signed by microsoft, but if they aren't, it won't work unless you apply the work around
Click to expand...
Click to collapse
I know it a while ago since you posted this but still, it helped me fix the "Access denied" thing which i didn't know how to fix. I installed ADB drivers 3 times... anyways, tnx :good:

So If you are like me you had this same issue in 2022. Idk if it will be a fix for you but it was for me.
follow this youtube video for the exact setup so you can get hopfully the same out com to the T.
{
"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"
}
1. make sure you're in administrator mode for command prompt.
2. The file name has changed from what it was so instead of doing
cd adb\platform-tools_r30.0.4-windows\platform-tools
It's now this
cd adb\platform-tools\
This will get you to the correct path if you followed the file placement in the video.
next all you have to do is type
adb devices on the command prompt. to test if it worked
other things that you might have to try is seeing if the driver it self is being blocked. you might also have to turn off and back on developer mode. View other posts in this thread if it's still stuck for you. Hopefully I helped one person at least.

Can't seem to get past the stuck at 50% Bootloader unlock issue.

In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.

vgdoc said:
In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.
Click to expand...
Click to collapse
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.

Hi, I run into the same issue on win 10 and also installed the android sdk. however, I only can see driver version 11 or an unsigned version 7, both are not working for me.
I can find the device with fastboot, however "fastboot getvars" fail all the times with the same error:
Code:
fastboot getvar all
getvar:all FAILED (command write failed (Unknown error))

stefipant said:
Hi, I run into the same issue on win 10 and also installed the android sdk. however, I only can see driver version 11 or an unsigned version 7, both are not working for me.
I can find the device with fastboot, however "fastboot getvars" fail all the times with the same error:
Click to expand...
Click to collapse
You still have problem, unlocking your device?
Sent from my Xiaomi Mi 5 using XDA Labs

vgdoc said:
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.
Click to expand...
Click to collapse
May I ask where you downloaded sdk tools and which file you used to manually update the driver? I have the same problem you had earlier. I'm using Windows 10 if that makes a difference.

abelmaster said:
May I ask where you downloaded sdk tools and which file you used to manually update the driver? I have the same problem you had earlier. I'm using Windows 10 if that makes a difference.
Click to expand...
Click to collapse
Common error.. Use sdk from ADT.. Or just use minimal adb and fastboot
Sent from my Xiaomi Mi 5 using XDA Labs

harish15 said:
Common error.. Use sdk from ADT.. Or just use minimal adb and fastboot
Click to expand...
Click to collapse
For me fastboot doesn't work, it doesn't show any device connected when I use minimal adb and fastboot, that is why I am searching for another solution.
So how do you suggest to get the right drivers with sdk from ADT? Where should I download it and how can I manually update the driver to the drivers included in this sdk?

abelmaster said:
For me fastboot doesn't work, it doesn't show any device connected when I use minimal adb and fastboot, that is why I am searching for another solution.
So how do you suggest to get the right drivers with sdk from ADT? Where should I download it and how can I manually update the driver to the drivers included in this sdk?
Click to expand...
Click to collapse
https://dl.google.com/android/installer_r24.4.1-windows.exe
Download and install this. Choose google usb driver and install package.
Then connect in fastboot mode and in the device manager update driver manually(let me choose update) and install version 9 driver.
Reboot your system and try unlocking again.

vgdoc said:
https://dl.google.com/android/installer_r24.4.1-windows.exe
Download and install this. Choose google usb driver and install package.
Then connect in fastboot mode and in the device manager update driver manually(let me choose update) and install version 9 driver.
Reboot your system and try unlocking again.
Click to expand...
Click to collapse
Thanks for posting your link, this helps me find it quick. Now one last question (I hope . Where can I find/download the version 9 driver?

"Google USB driver" in the SDK tools application. That is the version 9 driver.

vgdoc said:
"Google USB driver" in the SDK tools application. That is the version 9 driver.
Click to expand...
Click to collapse
When I type SDK tools application into windows menu bar nothing pops up, so i guess you mean the android sdk manager?
{
"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"
}
But where in the SDK manager can I "google" (or do you mean "search") for something?

In SDK manager did you install tools > Android sdk tools and tools > Android sdk platform-tools ?
If not try to install them, then check you can detect your device with adb tools :
connect your phone with usb
windows key + r
in prompt enter cmd
go to your adroid sdk platform-tools directory with "cd" command
then type "adb devices"
Your device should be find
Here an example :
Code:
cd /D F:\android\sdk\platform-tools
F:\android\sdk\platform-tools>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
74a9b5b5 device <<<<<<<<<<<<<<<<<<<
If you do not see your device there is something wrong, try to install this pack from xda :
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
It worked for me.
If it still not work after installation usb driver from xda have a look in the miFlashunlock log directory, open the MiFlashUnlock.log file and check the error.

What helped me was to
- get to the 50% error
- uninstall the kedacom USB device (remove drivers)
- restart miunlocker
- miumlocker would reinstall the driver
- the connection would work, but only once. If there is another error after 50%, you will have to remove/reinstall driver again.
Wasted a lot of time on that, they really should work on the quality of their software. I get the security concerns, but fastboot oem unlock is so much better.

I'm convinced it's impossible.
I've done a clean install of all the drivers (either via SDK or the minimal adb packs), tried doing what crim did... Still stuck on 50% error. Mind boggling stuff.

vgdoc said:
In spite of my best efforts, I can't seem to unlock my bootloader on my mi5.
The error I get is "Can't verify device-not connected to mi phone"
Here is a list of all things I've done after reading through countless threads on xda and miui forums:
Applied for permission and got the permission in three days
Downloaded and extracted the miflashunlock tool
Changed my Phone rom form global stable to global dev
Made sure that only one device was linked to my account.
Logged into unlock tool using my phone number.
Installed Koush's adb drivers and when connected to my PC in fastboot mode, it shows up as "android bootloader interface" under "Kedacom USB device" in device manager.
Any help on the topic would be appreciated.
Click to expand...
Click to collapse
same problem guys plz help me
---------- Post added at 02:43 AM ---------- Previous post was at 02:04 AM ----------
dkmsn8 said:
same problem guys plz help me
Click to expand...
Click to collapse
ok i did it guys thanks

Crim Soukyuu said:
What helped me was to
- get to the 50% error
- uninstall the kedacom USB device (remove drivers)
- restart miunlocker
- miumlocker would reinstall the driver
- the connection would work, but only once. If there is another error after 50%, you will have to remove/reinstall driver again.
Wasted a lot of time on that, they really should work on the quality of their software. I get the security concerns, but fastboot oem unlock is so much better.
Click to expand...
Click to collapse
I dont know why this worked, but it did. Finally! I tried this method a couple of times and the fourth time it works. Have to say that mi unlock did not install the driver for me, I searched for it online with the built in windows driver update. It gave me the kedacom one again, but it worked!

vgdoc said:
I've finally managed to unlocked my device. I used sdk tools to install google usb driver and then manually updated(technically downgraded from v11 to v9) driver from device manager. Restarted my PC and tried again and it successfully unlocked. Hope this helps for others facing the same issue.
Click to expand...
Click to collapse
hello, i am a chinese mi5 user and i get the same problem with you when i unlock my mi5 at first. and this problem almost spends me 2 whole days to solve it.i searched many webs and i found many other mi5 users had this problem. i do all the procedures that the official posts and others suggested again and again and it helps nothing. in the end, i solved it. i believe you did not bind your account with your phone after your login your account.i cant say where to type that option(i mean bind your accout with your phone) because i am using aosp now.your should try to find that option in miui and type that option,then you will solve this problem.sorry for my bad english and i hope you can understand what i wanna express. good luck.
---------- Post added at 01:16 PM ---------- Previous post was at 01:13 PM ----------
eros1on said:
hello, i am a chinese mi5 user and i get the same problem with you when i unlock my mi5 at first. and this problem almost spends me 2 whole days to solve it.i searched many webs and i found many other mi5 users had this problem. i do all the procedures that the official posts and others suggested again and again and it helps nothing. in the end, i solved it. i believe you did not bind your account with your phone after your login your account.i cant say where to type that option(i mean bind your accout with your phone) because i am using aosp now.your should try to find that option in miui and type that option,then you will solve this problem.sorry for my bad english and i hope you can understand what i wanna express. good luck.
Click to expand...
Click to collapse
and i believe other guys with this problem can also solve it via this method.

i solved it by;
1.disable internet coonection cause of auto update driver
2.uninstall kedacom driver, select delete files.
3.update driver manually and select let me pick driver.
4. choose usb composite device than try "fastboot oem-devices" command .
if it shows your device. unlock wont be stuck at %50.

Which Qualcomm interface driver for download mode?

Hi all!
I am trying to flash QFIL file to my Nokia 7 plus (TA-1046), but with no success because the Qualcomm driver is not installed automatically.
I have the 1.0 Qualcomm driver collection installed, but when I plugin my phone in download mode, I see it appear in device manager under "other devices" as "Android". I can update the driver to any other Qualcomm driver, but I don't know which one to choose. I tried the "QDLoader 9008" and it installs fine, but in QFIL.exe I can't flash my phone. I still get sahara errors.
What driver (type number) do I need to install to connect my phone's interface (download mode)?
EDIT:
Forgot to mention the obvious, it's Windows 7...

sbsoft said:
Hi all!
I am trying to flash QFIL file to my Nokia 7 plus (TA-1046), but with no success because the Qualcomm driver is not installed automatically.
I have the 1.0 Qualcomm driver collection installed, but when I plugin my phone in download mode, I see it appear in device manager under "other devices" as "Android". I can update the driver to any other Qualcomm driver, but I don't know which one to choose. I tried the "QDLoader 9008" and it installs fine, but in QFIL.exe I can't flash my phone. I still get sahara errors.
What driver (type number) do I need to install to connect my phone's interface (download mode)?
EDIT:
Forgot to mention the obvious, it's Windows 7...
Click to expand...
Click to collapse
When you install QPST Too,l all qualcomm drivers are installed to your pc. if your device is not detected by your pc try restarting your pc. if restart not working the. open device manager and search for unknown device then install driver manually.

sarath medithi said:
When you install QPST Too,l all qualcomm drivers are installed to your pc. if your device is not detected by your pc try restarting your pc. if restart not working the. open device manager and search for unknown device then install driver manually.
Click to expand...
Click to collapse
Thanks for your reply!
I did all you said (incl installing QPST tool), but still see "Android" under "Unknown devices". It is not recognized at all by Windows.
I want to install manually, but don't know which driver to choose from. I see a list of about 50 Qualcomm port drivers (MSM xxxx, QDLoader xxxx, Diagnostics xxxx), so which one is the correct one? What do you see under your "Ports (COM and LPT)" in device manager when you connect your phone in download mode?

QFIL Flashing Procedure
sbsoft said:
Thanks for your reply!
I did all you said (incl installing QPST tool), but still see "Android" under "Unknown devices". It is not recognized at all by Windows.
I want to install manually, but don't know which driver to choose from. I see a list of about 50 Qualcomm port drivers (MSM xxxx, QDLoader xxxx, Diagnostics xxxx), so which one is the correct one? What do you see under your "Ports (COM and LPT)" in device manager when you connect your phone in download mode?
Click to expand...
Click to collapse
Please confirm your qfil version.
Tool frome here:
https://aiomobilestuff.com/download-...st-flash-tool/
Drivers from here:
http://www.mediafire.com/file/j3g88d...r+V1.1.0.0.rar
Steps to flash the phone
Step1: To use QPST, some drivers need to be installed on your Computer.
Note: While installing driver avoid using cable for successful installation.
When Drivers installed, Attach Phone to PC via USB cable.
While connecting to PC, phone should be switched off and press volume up & down as boot key.
If it Create Qualcomm HS-USB QDLoader 9008 port in device manager , then driver has been successfully installed.
Once driver installation is complete, follow the instructions below to flash the MBN firmware file to your Qualcomm device.
Step 2. Make sure your device is charged to at least 30%.
Step 3. Run QFIL tool.
Step 4. Now Browse under the Programmer path to Chose the B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf File.
Step 5. As soon as the elf file is selected, Select Build will automatically select the Update or Stock ROM.
Step 6. Next Go To Load XML, selectB2N-0-132E-rawprogram0.xml and Select B2N-0-132E-patch0.xml
Step 7. Turn off the Phone and Attach it to PC by pressing Vol up & down button.
Step 8. Click on Select Port and choose the port.
Step 9. Click on Download to start flashing.
Step 10. Disconnect device from USB cable once Finish Download appears.
That’s all!
Hit thanks button if you find this helpful
Happy flashing
Note: If you get the Sahara Errors Place Firmware folder in QFIL\Bin folder. Check whether programmer file is available in your firmware folder. It is an elf file (B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf). Use recent version of QPST. earler versions cant flash .elf programmers.

sarath medithi said:
Please confirm your qfil version.
Tool frome here:
https://aiomobilestuff.com/download-...st-flash-tool/
Drivers from here:
http://www.mediafire.com/file/j3g88d...r+V1.1.0.0.rar
Steps to flash the phone
Step1: To use QPST, some drivers need to be installed on your Computer.
Note: While installing driver avoid using cable for successful installation.
When Drivers installed, Attach Phone to PC via USB cable.
While connecting to PC, phone should be switched off and press volume up & down as boot key.
If it Create Qualcomm HS-USB QDLoader 9008 port in device manager , then driver has been successfully installed.
Once driver installation is complete, follow the instructions below to flash the MBN firmware file to your Qualcomm device.
Step 2. Make sure your device is charged to at least 30%.
Step 3. Run QFIL tool.
Step 4. Now Browse under the Programmer path to Chose the B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf File.
Step 5. As soon as the elf file is selected, Select Build will automatically select the Update or Stock ROM.
Step 6. Next Go To Load XML, selectB2N-0-132E-rawprogram0.xml and Select B2N-0-132E-patch0.xml
Step 7. Turn off the Phone and Attach it to PC by pressing Vol up & down button.
Step 8. Click on Select Port and choose the port.
Step 9. Click on Download to start flashing.
Step 10. Disconnect device from USB cable once Finish Download appears.
That’s all!
Hit thanks button if you find this helpful
Happy flashing
Note: If you get the Sahara Errors Place Firmware folder in QFIL\Bin folder. Check whether programmer file is available in your firmware folder. It is an elf file (B2N-0-132E-prog_emmc_ufs_firehose_Sdm660_ddr.elf). Use recent version of QPST. earler versions cant flash .elf programmers.
Click to expand...
Click to collapse
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???

sbsoft said:
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
Click to expand...
Click to collapse
QFIL don't need unlocked bootloader as it uses EDL Mode for flashing. I suggest you to change the usb port and try with another data cable.
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
sbsoft said:
Thanks for your replay!
I did all you said and I think the driver is now installed correctly. Only problem that remains is the locked bootloader, which is preventing flashing.
I have tried to disable it by "fastboot oem unlock", but no success, because access is denied. (I have enabled OEM unlock in dev options).
QFIL keeps reporting me "100 Unable to connect to port". Sahara is not an issue anymore (I guess).
Do I really need to unlock bootloader to flash the elf?
EDIT: I've read another article on XDA that states that Nokia devices cannot be flashed???
Click to expand...
Click to collapse
can you share the qfil log or screenshot

sarath medithi said:
QFIL don't need unlocked bootloader as it uses EDL Mode for flashing. I suggest you to change the usb port and try with another data cable.
---------- Post added at 12:13 PM ---------- Previous post was at 12:12 PM ----------
can you share the qfil log or screenshot
Click to expand...
Click to collapse
Here we go:
(I have Dutch language version of Windows 7, so no English in some pictures)
1. The driver is installed correctly and working fine. (I need to boot Windows in testsigning mode with no driver signature checking, because the driver is not signed correctly?)
{
"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"
}
Phone is in Download mode.
When I click Download in QFIL, this is the output and nothing happens.
The configuration of QFIL looks like this:
Is this enough for you? If not, please let me know. I am starting to get headaches of this problem...
Thanks!

sbsoft said:
Here we go:
(I have Dutch language version of Windows 7, so no English in some pictures)
1. The driver is installed correctly and working fine. (I need to boot Windows in testsigning mode with no driver signature checking, because the driver is not signed correctly?)
Phone is in Download mode.
When I click Download in QFIL, this is the output and nothing happens.
The configuration of QFIL looks like this:
Is this enough for you? If not, please let me know. I am starting to get headaches of this problem...
Thanks!
Click to expand...
Click to collapse
Try to update your QFIL.i think there is a new version available. update it and try again. may be it is giving an error due to the programmer file which is an elf file. earlier it is .mbn or .bin file. hope you understand.

Did you succede in using QFIL ? @sbsoft

How to install the correct drivers for fastboot to a Windows 10 laptop?

Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
{
"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"
}
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!

Omninano said:
Hi there, I'm a software developer but not an Android developer at all (I have no experience), so answers that are understandable to newbies would be very appreciated
My Moto X4 power button stopped working a few days ago (the phone doesn't register when it is pressed). Based on my Google searching this seems to be a common problem among many users of the phone. Luckily, it wasn't a big issue for me because I could still use the fingerprint scanner to lock/unlock the phone. The problem arose last night when I accidentally let my phone run completely out of battery. With no working power button, I could no longer turn on the phone!
This is especially an issue because I am in a foreign country right now so I can't send my phone in anywhere to get fixed. Yet I really need it for WhatsApp to contact some people today.
I have been following this guide (reddit - How to turn on your phone if/when your power button breaks) to install fastboot and use the reboot command to turn the phone on. Almost every step works fine for me (I successfully installed the Android SDK "platform tools", I can get my phone to go to the fastboot screen by holding the volume down button when plugging in the USB), the only problem is when I plug my phone (in fastboot mode) into my Windows 10 laptop, it does not seem to have the correct drivers installed to communicate with the device. So when I try to run the fastboot reboot command, it just gets stuck at <waiting for any devices> .
I have tried downloading the Motorola Device Manager executable (from here: https://support.motorola.com/us/en/drivers) to install the correct drivers, but even after doing that, when I plug my phone in, the Windows Device Manager still shows my phone as having the incorrect drivers.
I think that it is a compatibility issue. The first time after installing the Motorola software, Windows created a pop-up about the program potentially installing incorrectly and provided the option to re-install using compatibility settings, but since I hadn't tried the drivers at all yet at that point, I ignored it. I have not been able to reproduce the pop-up since.
How do I install the correct drivers so that I can run the fastboot reboot command?
I'm running 64-bit Windows 10 on an HP Envy laptop.
Any help is extremely appreciated, thank you so much!
Click to expand...
Click to collapse
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish

Datclefxuj said:
Hi, you can try uninstall from device manager, and run cmd cleanmgr-> clean system files, find device driver and click Ok, this erase all obsolete drivers, and install again Moto Device Manager
Or in the device manager, "update driver"->find driver on my pc->chose driver list, and find adb driver.
Good luck
pd. Sorry for my english, isnt y native languaje and my SO is in Spanish
Click to expand...
Click to collapse
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!

Omninano said:
Hi Datclefxuj! No problem about the English, I understand what it is like to not be using your first language
I tried what you suggested, but there are a few small issues I ran into.
First, I uninstalled my phone from the device manager.
Then I ran 'cleanmgr' and clicked my C: drive.
But when you say "find device driver and click Ok", I don't know where the device drivers are located on my computer. Where would I typically find those? This is what my cleanmgr looks like:
Also, when you say "in the device manager, 'update driver'->find driver on my pc->chose driver list, and find adb driver", I do not have an adb driver to choose. Where would I download that from? Do I need an adb driver, anyway? I just want to be able to access fastboot on my phone.
I hope that makes sense. Thank you very much!
Click to expand...
Click to collapse
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:

Datclefxuj said:
it's here
or after to install motorola drivers
this is my drivers
https://drive.google.com/file/d/1chPe7UJpDC-rkSBoOGcmC0rJDYKmf966/view?usp=sharing
:good:
Click to expand...
Click to collapse
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!

Omninano said:
MUCHAS GRACIAS!!!!
After following your steps, it worked! I am able to use my phone again!
En serio, thank you so much! I cannot thank you enough!
Click to expand...
Click to collapse
Great! You're welcome!