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

[26.12.2015] Samsung USB Drivers for Mobile Phones 1.5.55.0 [Win 10/8.1/7/XP]

{
"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"
}
INFO:
This driver allows you to connect your Samsung device to your computer without installing KIES and allows you to use Odin and ADB with your phone.
This driver is the latest as of 26.12.2015 and works with ALL Samsung Android phones and tablets. This driver works on Win 10 & 8.1 & 7 & Vista & XP, 32 and 64 bit.
You can also download latest ADB & Fastboot Tools below. ADB and Fastboot binaries are latest as of 26.12.2015
WHAT'S THE HASSLE:
Samsung Drivers package's installation mechanism doesn't work on Windows 8 for many people (driver installation doesn't even start), so the point is that the drivers have to be installed manually. In order to do this I unpacked Samsung Drivers package .exe file using UniExtract 1.6.1 (link) so that the drivers can be installed via "have disk" method. I used these drivers succesfully in Windows 8 Enterprise x64 to connect my SGS i9000 to ODIN3 1.3. Odin sees the phone and can flash firmware, reformat partitions etc.
Download the INSTALLER. If it won't work for you, try RAR ARCHIVE then and read its Installation Guide 2 & 3 below.
The drivers are also available at: www.odindrivers.net
SAMSUNG USB DRIVERS 1.5.55.0 INSTALLER: DOWNLOAD HERE
SAMSUNG USB DRIVERS 1.5.55.0 RAR ARCHIVE: DOWNLOAD HERE
ADB & FASTBOOT TOOLS (.exe files): DOWNLOAD HERE
Click to expand...
Click to collapse
INSTALLATION 1:
1. Download the driver INSTALLER.
2. Uninstall previous Samsung USB drivers from "Programs And Features" and "Device Manager".
3. Run the installer "USB_Drivers_1.5.27.0.exe" and proceed with the installation steps, finish the installation and restart your computer.
4. Connect it to your computer via USB cable.
5. If your phone is still not correctly recognized by Odin and the driver installer finished installation successfully - skip the 2nd method and use the 3rd. If drivers didn't install correctly (e.g. the installer failed to launch or failed to finish installation) - try the 2nd method first.
INSTALLATION 2:
1. Download the driver RAR ARCHIVE.
2. Uninstall previous Samsung USB drivers from "Programs And Features" and "Device Manager".
3. Unpack USB_Drivers.rar to some location, eg. C:\.
4. Run the installer from "C:\USB_Drivers\SAMSUNG_USB_Driver_for_Mobile_Phones\setup.exe" and proceed with the installation steps, finish the installation and restart your computer.
5. Switch your Samsung phone into download mode (i9000: power it on with Power + Vol UP + Home pressed simultanously).
6. Connect it to your computer via USB cable.
7. If your phone is still not correctly recognized by Odin - try the 3rd method.
INSTALLATION 3:
0. This is the "have disk" method. You have to follow every step in this guide
1. Download the driver RAR ARCHIVE.
2. Uninstall previous Samsung USB drivers from "Programs And Features" and "Device Manager".
3. Unpack "USB_Drivers.rar to some location, eg. C:\.
4. Switch your Samsung phone into download mode (i9000: power it on with Power + Vol UP + Home pressed simultanously).
5. Connect it to your computer via USB cable.
6. Your phone should become discovered by Windows as some device. In my case, Windows has found my SGS i9000 as a "Gadget Serial" device.
7. Go to Windows Device Manager. Right click on the device your phone has been discovered as (eg. "Gadget Serial" in my case) and choose "Update driver" option from the context menu.
8. Choose "Search my Computer...", check "Include subfolders" option and point the updater to the folder where you've had unpacked the drivers .rar archive to, eg. C:\USB_Drivers.
9. The driver should install automatically.
10. It may happen that after the installation some new "unknown device" ("Samsung Modem" in my case) would appear in the Device Manager. Complete 7 & 8 step for that device and any other new device that may appear afterwards.
11. Restart your computer.
12. Done!

Be careful - the Samsung USB Driver Installer will try to also install multiple malware programs. You'll need to slow down, watch for each screen that defaults to "Accept" and manually click on "Decline". Eventually, you'll reach the actual Samsung driver install.

Thanks

How to issue fastboot command in Galaxy S2
Hi, I've installed the drivers and my device is being recognized by ODIN 0:[COM5] in Odin mode
Now I wanted to issue fastboot command "fastboot oem off-mode-charge 0". However my devices is not being listed in fastboot devices in odin mode.
Also tried the same status in bootloader mode. Can some one throw some lite please.. Am stuck with this for 5 days now.. I've CM13 flashed now in SG S3. I've earlier tried with syiah and the same problem was there. Tried multiple USB ports, different PC with windows 7 and windows 10.
Or is there any other way to issue this fastboot command "fastboot oem off-mode-charge 0" other than fastboot options.. I just want to enable boot on USB connect option in my device.
Thanks in advance for help.

Thanks!

Testing...
---------- Post added at 10:20 AM ---------- Previous post was at 10:05 AM ----------
Very good for Galaxy S2

Baboon_Red said:
Be careful - the Samsung USB Driver Installer will try to also install multiple malware programs. You'll need to slow down, watch for each screen that defaults to "Accept" and manually click on "Decline". Eventually, you'll reach the actual Samsung driver install.
Click to expand...
Click to collapse
The download or the actual file? Trying to download but all I get is an 80kb file. That's probably the malware right? How do i get the rar archive file?

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.

Bricked OnePlus 3T

Hello,
i have a locked Bootloder with twrp and can't boot the Phone.
The device wan't to reset the storage but TWRP is not booting.

http://forum.xda-developers.com/oneplus-3t/help/oneplus-3t-factory-restore-utility-t3511287

Hey, I uploaded the Unbrick Tool for the Oneplus 3T with the drivers! Hope I can help you out.
I cant send Links in here, becouse im a newbie.... so, contact me Privat.
Step 1 :- Extract Drivers and Recovery Tool files on Desktop.
Step 2 : If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 5 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices
Step 6 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 7 :- Click start at top left corner and wait for it to finish (green text will come).
Step 8 :- Disconnect phone from PC and boot into system.
Works great with my OP3T
Best wishes,
Lloyd Smallwood

Everything works great, Thanks
Is me first Phone with the new security features, on me old Note 2 everything was easier.

can i have the link? Please i need it
hachamacha said:
http://forum.xda-developers.com/oneplus-3t/help/oneplus-3t-factory-restore-utility-t3511287
Click to expand...
Click to collapse
i have the same problem

swowdi said:
i have the same problem
Click to expand...
Click to collapse
I'm lost. What are you asking for that isn't in that quote or this thread? The link to .. . ?

martinklaus said:
Hello,
i have a locked Bootloder with twrp and can't boot the Phone.
The device wan't to reset the storage but TWRP is not booting.
Click to expand...
Click to collapse
Driver: https://mega.nz/#!AgohmbqC!h16GeeOnlvubYDyfID3feY-qVJuBZiWVvYsXSAeKIA8
Unbricktool: https://mega.nz/#!Q1YnTTAT!gnLf6NEkSRy7W-WY8J0H2SmJJLzO91-vReKx7B1VVpI[/QUOTE]

I tried to use the tool, but when I click start says it downloads Fire Hose binary and then says that Sahara Communication failed, I can't unbrick my device

UckTay said:
I tried to use the tool, but when I click start says it downloads Fire Hose binary and then says that Sahara Communication failed, I can't unbrick my device
Click to expand...
Click to collapse
If the steps not working you can ask the OnePlus Support and one guy make it in a remote session for you.

martinklaus said:
If the steps not working you can ask the OnePlus Support and one guy make it in a remote session for you.
Click to expand...
Click to collapse
You can use my tool:
Hey, I uploaded the Unbrick Tool for the Oneplus 3T with the drivers! Hope I can help you out.
Driver: https://mega.nz/#!AgohmbqC!h16GeeOnl...iWVvYsXSAeKIA8
Unbrick Tool: https://mega.nz/#!Q1YnTTAT!gnLf6NEkS...1-vReKx7B1VVpI
Step 1 :- Extract Drivers and Recovery Tool files on Desktop.
Step 2 : If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
http://www.howtogeek.com/167723/how....igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 5 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices
Step 6 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 7 :- Click start at top left corner and wait for it to finish (green text will come).
Step 8 :- Disconnect phone from PC and boot into system.
Works great with my OP3T
Don't forget to Thank!
PayPal: www.paypal.me/harisscoot
Best wishes,
Lloyd Smallwood

LloydSmallwood said:
You can use my tool:
Hey, I uploaded the Unbrick Tool for the Oneplus 3T with the drivers! Hope I can help you out.
Driver: https://mega.nz/#!AgohmbqC!h16GeeOnl...iWVvYsXSAeKIA8
Unbrick Tool: https://mega.nz/#!Q1YnTTAT!gnLf6NEkS...1-vReKx7B1VVpI
Step 1 :- Extract Drivers and Recovery Tool files on Desktop.
Step 2 : If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
http://www.howtogeek.com/167723/how....igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 5 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices
Step 6 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 7 :- Click start at top left corner and wait for it to finish (green text will come).
Step 8 :- Disconnect phone from PC and boot into system.
Works great with my OP3T
Don't forget to Thank!
PayPal: www.paypal.me/harisscoot
Best wishes,
Lloyd Smallwood
Click to expand...
Click to collapse
what is decrypton key

Gautamgzb2 said:
what is decrypton key
Click to expand...
Click to collapse
Go on my thread, there are the currect links.
https://forum.xda-developers.com/on...oneplus-3t-t3515306/post70653711#post70653711

UckTay said:
I tried to use the tool, but when I click start says it downloads Fire Hose binary and then says that Sahara Communication failed, I can't unbrick my device
Click to expand...
Click to collapse
I am having the same prob bro,,,How did you solved the prob?

Hi Guys,
I think I have no lucky these days...
I was testing a new ROM and when a returned the backup with TWRP android asked me a patteren for unlock.
The patter I usauly use didnt work.
I found a help that say to erase some files in /data/system but it didnt work...
I had a idea to block the cell with my google account and set a new PIN for unlock... It didnt work too...
Now I have the cell blocked by google and its impossible to access the internal memory with TWRP...
I need help... I dont know what to do...
Please !!!!

LloydSmallwood said:
You can use my tool:
Hey, I uploaded the Unbrick Tool for the Oneplus 3T with the drivers! Hope I can help you out.
Driver: https://mega.nz/#!AgohmbqC!h16GeeOnl...iWVvYsXSAeKIA8
Unbrick Tool: https://mega.nz/#!Q1YnTTAT!gnLf6NEkS...1-vReKx7B1VVpI
Step 1 :- Extract Drivers and Recovery Tool files on Desktop.
Step 2 : If you are using Windows other than Windows XP,turn off Driver Signature Enforcement.To do so,follow this guide :
http://www.howtogeek.com/167723/how....igned-drivers/
Step 3 :- Press the power button for 40 seconds to turn off the phone.
Step 4 :- Press only volume up button for 10 seconds and while keeping it pressed,connect your phone to PC.Keep volume up pressed till your device shows in device manager as [Unknown Device,QHUSB_BULK (under Unknown Devices) or Qualcomm HS USB ...... (under COMs and Ports)].
Step 5 :- Right Click on your device in the device manager and select Update Device Software. Choose the .inf file manually from x86 or x64 folder as the case implies and select Qualcomm 9008 from the listed devices
Step 6 :- When the device shows as Qualcomm 9008 ,go to the extracted Recovery Package and run the MSM Download Tool as administrator.
Step 7 :- Click start at top left corner and wait for it to finish (green text will come).
Step 8 :- Disconnect phone from PC and boot into system.
Works great with my OP3T
Don't forget to Thank!
PayPal: www.paypal.me/harisscoot
Best wishes,
Lloyd Smallwood
Click to expand...
Click to collapse
Hi, I followed all the steps and how you can see I have the Qualcomm 9008 in the list
{
"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 when I run the recovery package nothing happens and the device is not displayed in the list, why?
EDIT: I did wrong the step 4 "Press the volume up button for 10 seconds", I pressed the volume up and the power button together this is why it didn't work

brekane said:
EDIT: I did wrong the step 4 "Press the volume up button for 10 seconds", I pressed the volume up and the power button together this is why it didn't work
Click to expand...
Click to collapse
Your not the first to do this, coming from owning a Mediatek device/phone, it makes sense as that's exactly the same way the recovery works on those phones. ?

i did everything but...
I installed the MSMdownload to my 3t, removed it from my pc and booted it but for some reason it wont boot or connect to my PC anymore. can you please help. thanks

Question My computer doesn't recognize the phone in fastboot even with drivers installed

Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.

Check in another USB Port, use original xiaomi's wire...and install latest USB drivers

I have the same problem, i'm using the original xiaomi wire and already installed lastest usb drivers.. the fact is that when I plug in the cell phone in fastboot mode the computer keeps sounds as connecting and disconnecting the device (I used two wires and two different computers)

Yup exact same thing, I hope somebody knows how to fix it and help us out.

Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem

Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
I'll try that, thanks for the help.

I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.

seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
Can you please tell me how do I do that?

Ricardo 182 said:
Try with mi flash tool software for the computar... And let the program install the original firmware again... I think you can get rid of the problem
Click to expand...
Click to collapse
Tried that but still don't recognize the phone

seyren00 said:
I had the same problem, and I fixed it changing the cellphone drivers in device manager, from: "Android" to ---------> "Xiaomi Composite MDB Interface".
Hope it helps someone.
Click to expand...
Click to collapse
worked perfect for me! thank you!

liam_lost said:
Can you please tell me how do I do that?
Click to expand...
Click to collapse
{
"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"
}

seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
Thanks I tried but not sure why it shows this android one

liam_lost said:
Thanks I tried but not sure why it shows this android oneView attachment 5366067
Click to expand...
Click to collapse
Thats it bro, change that to Xiaomi Composite MDB interface, the first time my cellphone showed the same.

Ricardo 182 said:
Check in another USB Port, use original xiaomi's wire...and install latest USB drivers
Click to expand...
Click to collapse
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.

Pino76 said:
Hi, where do I get the USB drivers? Even the official website says to make sure that "your PC has necessary drivers", but they don't provide any link where you can get them.
The Unlock Tool only has a "Check" button next to the version number, which says "5.5.224.24(Already latest)" and again, no drivers check. There are tons of fishy websites that claim to have the drivers and I have already tried several of them, but no success. Your help would be much appreciated.
Click to expand...
Click to collapse
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.

seyren00 said:
https://c.mi.com/thread-3221402-1-0.html try using this guide bro.
Click to expand...
Click to collapse
Thank you, unfortunately, it didn't work for me. My device is still not showing up.

liam_lost said:
Hi all,
I really need your help, my computer doesn't recognize the phone in fastboot, I've installed different drivers and none of them work, in device manager it appears as Android with the yellow exclamation mark. I've already enabled USB Debugging mode, not sure what am I missing, please help.
Click to expand...
Click to collapse
Hi, after almost 2 days of constant researching and trying and failing and testing, I have finally figured it out! You need two things: MediaTek Driver and disabling Driver Signature Enforcement in Windows 10. It's because normally, the (64-bit) Windows 10 system won't allow you to install an unsigned driver and the Mediatek Driver is unsigned.
Here are the steps:
1. Press the Windows key on your keyboard, open PC settings
2. Go to Update & Security
3. Go to Recovery tab
4. Press & hold Shift key on your keyboard and click the Restart now button (in the Advanced startup section)
5. Select Troubleshoot ->Advanced setup -> Startup Settings and press Restart
6. Press 7 number key corresponding to "Disable driver signature enforcement" entry.
The system will now boot with the Driver Signature Enforcement disabled (it's going to be automatically enabled with the next restart). Download the Mediatek Driver (official source), unzip the file. Here's how I installed the driver:
1. Press the Windows key, type Device Manager and open the utility program
2. Click the top item in the list (your PC's name) and click Action in the menu and select Add Legacy Hardware.
3. Click Next in the Wizard, select Install hardware manually, and again Next and Next again.
4. Click Have Disk, Browse, navigate to the unzipped folder: SmartPhoneDriver > x64 > Unsigned infs and select the file android_winusb.inf. Click OK and select Media Tek Inc. in the left pane and then Next and Finish.
Your phone will now finally appear in the Unlock Tool.
This should work for all Note 10s users who also happen to have a 64-bit Windows 10 machine. Let me know how it went for you.

hey Guys, i´m new in the forum. But i had the same problem and i´m bringing the solution.
This error happens because Windows doesn´t recognize the bootloader, then you must install manually the bootloader´s driver and connect again your phone, so simple. I´m attaching the driver in this post.
Cheers.

download google usb driver: https://developer.android.com/studio/run/win-usb
connect phone to pc in fastboot mode. then go to device manager and update related driver named: android.
choose have disk and select Android_USB.inf file. then highlight Android bootloader interface and install driver. in win 10 must disable driver signature verification

seyren00 said:
View attachment 5365973
Click to expand...
Click to collapse
After searching for a long time, I found that this is the solution that works 100%. At last I was able to register the unlock of the bootloader today after a week of searching how to do it, since the driver did not work, thank you.