Database Develop

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.

[Q] Stuck in *Daemon Started Successfully* during ROOT

Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.

retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.

I'm having the exact same problem here.
RooQemu hangs at *Daemon started successully* and nothing happens
when I try to enter "adb shell" in a cmd i get the error "device not found"
Kindle is shown correct in device manager as "Android Composite ADB Interface" and I can transfer files via explorer without problems.
Windos 7 64 bit and Kindle from amazon Germany Version 7.2.1_user_2040020
Tried on my Laptop and my PC, both with the same result.
At least someone seems to have the same problem as I do. Hope someone comes up with a solution. I tried the steps mentioned above, same result...

spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse
Thanks man..
unfortunately, it didn't work for me..
i think it might be something with the drivers since it keeps telling me that the install didn't work correctly..and i need to "manually install it".
Any more ideas?
Thanks everyone! :good:

retroflashbacks said:
Thanks man..
unfortunately, it didn't work for me..
i think it might be something with the drivers since it keeps telling me that the install didn't work correctly..and i need to "manually install it".
Any more ideas?
Thanks everyone! :good:
Click to expand...
Click to collapse
Try this. Install the Android SDK in your computer reboot your kindle and the computer and try again. It worked for me

Darn..still not working...

This problem is due to the drivers!
You need to uninstall the drivers in the device manager, and manually install the drivers from the location you install the ADB drivers.
In my computer, the location is "C:\program files\amazon.com\kindle fire\drivers".
The wrong driver is like this: ”Android ADB Interface“
{
"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"
}
And the correct driver is like this:
retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse

Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..

retroflashbacks said:
Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..
Click to expand...
Click to collapse
Try to do what PMcHargue explained, it didn't work for me but who knows? Locate the adb_usb.ini file and insert the last line.
PMcHargue said:
"C:\Users\<your username>\.android\adb_usb.ini"
now hjas the line in it,
"# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x1949"
And that allowed ADB to see the KFHD7
Click to expand...
Click to collapse

retroflashbacks said:
Thanks everyone for the responses! I really appreciate it!
It's getting really weird..because even though the drivers said it was installed correctly..everything seemed to install fine.
My device manager do say "Android Composite ADB Interface"
can't do a screenshop because i'm not allowed to post links..
Click to expand...
Click to collapse
Hey! I'm the one that had the same problem as you.
I tried everything... Then I installed Android SDK and followed this guide:
groovypost . com / howto / kindle-fire-hd-connect-adb-debug
Then it worked.
Hope that helps!

spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse
I had the same problem but I did this bur turned my wifi off before step 2. The device appeared with a caution sign next to it in the device manager (no driver installed) but the adb commands started to work and I could root my kindle. Hope this works for you.
Sent from my KFTT using xda app-developers app

It didn't work for me with the drivers in this post, it worked using the Amazon drivers from Android SDK.

retroflashbacks said:
Sup everyone..
Purchased a KF HD (10.2.1) a week ago and is looking to put Google Play Store on it.
I've been using RootQEmu for the actual root..
I downloaded the ADB drivers for the kindle..and although it says "the drivers are not installed correctly"..the details show that everything is okay..
and my kindle also shows as "Android Composite ADB" on my computer's device manager.
I ran the rootqemu.bat file and is getting stuck in step one.
*Daemon started successully* shows up and gets stuck there.
I already tried reinstalling the drivers about 20x and made sure my kindle has ADB debugging on.
please help!!!
Thanks everyone in advance.
Click to expand...
Click to collapse
What worked for me was to download the android SDK into the root folder of the PC...OR C: If you like....I still found that after every step I had to unplug the device and re-plug it (Is that a word) to continue as the device wasnt found. Im now told ADB tools works better? Gotta have another go since Super user didnt get root access....Guess were on the same journey!

I have the "Android ADB Interface" and not the Composite one and its worked fine for me

thanks alot mate ...
i have windows 8 and faced same problem ...
i did what u said n the root method worked like charm..
thanks again
spliter200 said:
what worked for me in the past was to go to... assuming you have windows 7
1.control panel and uninstalling the driver. then re install the driver again. (thats the driver given to you by rootqemu)
2.Also if that does not work go to connect the kindle fire hd to computer start>computer>right click on computer>device manager>portable devices> expand the tree> right click and uninstall driver> reconnect kfhd to computer and allow for driver to install>then install rootqemu driver>
3.make sure you have ADB on?
4. rootqemu worked for me after i did these steps.
Click to expand...
Click to collapse

x64 problem?
I'm having the exact same issue, 'daemon started successfully' I think it has something to do with my OS being x64. I kpet the Task Manager open, and it seems like it opens up 2 adb.exe *32 at once. I tried closing one, and the program would continue. I'm using an Intel x64, and I noticed that the only drivers in the Amazon.com folder were *386, and AMD64. I'm not sure if AMD64. Not sure if this added info is relevant, since the original driver is prior to these directories. I hope an easier method evolves.

Update ... I tried downloading the android sdk, then copied the adb.exe over to the Root\stuff folder and it worked! once you copy the adb.exe, just follow the original OP's instructions.

Eu quero meu root

[Nook HD+] Nook HD+ will not get out of MTP Device mode

I've been working with leapinlar in this thread
http://forum.xda-developers.com/showthread.php?t=1994129
to get my HD+ ready for sideloading and root. One thing to know up front is that I'm running with HD+ OS 2.0.2. I got to where the Nook shows up as a MTP Device (BNTV600 under Portable Devices in Win7 x64 Device Manager), but when I unplug the Nook, enable ADB, and plug it back in it keeps getting redetected as the MTP Device. I tried disabling and re-enabling multiple times, rebooting my PC, power cycling the Nook, different USB ports. Nothing seems to work. I used USBDeview to make sure there is nothing else with the same Vendor and Product ID installed (there isn't).
I have other BN drivers installed for my other Nooks (a Touch and Tablet). These have the same Vendor ID (2080) but different Product IDs. I don't think I should have to uninstall them, doesn't seem like that should be necessary.
The odd thing is, the first time I plugged the HD+ in to my PC ADB was accidentally already enabled. It was detected immediately as an Other Device as it should before installing the Android Composite driver. Once I disabled ADB and got MTP to install (and it does work - the HD+ is visible in File Manager) it will now never show up as a new Other Device with ADB enabled.
My apologies in advance, but I was hoping posting this in its own thread would maybe provide better visibility.

Per the NEW announcement,
http://forum.xda-developers.com/showthread.php?p=34819554#post34819554
I redeclare this thread open...

tonyp22 said:
I got to where the Nook shows up as a MTP Device (BNTV600 under Portable Devices in Win7 x64 Device Manager), but when I unplug the Nook, enable ADB, and plug it back in it keeps getting redetected as the MTP Device. I tried disabling and re-enabling multiple times, rebooting my PC, power cycling the Nook, different USB ports. Nothing seems to work. I used USBDeview to make sure there is nothing else with the same Vendor and Product ID installed (there isn't).
The odd thing is, the first time I plugged the HD+ in to my PC ADB was accidentally already enabled. It was detected immediately as an Other Device as it should before installing the Android Composite driver. Once I disabled ADB and got MTP to install (and it does work - the HD+ is visible in File Manager) it will now never show up as a new Other Device with ADB enabled.
Click to expand...
Click to collapse
I'm having the same problem. Were you able to get it working?
I think it has something to do with the OS being 64 bit and not being able to install the driver but it recognized it as an Android Composite Something once before I tried installing the driver on it and restarting but now it won't recognize it if I enable the developer option. It just keeps repeating the device disconected sound over and over and over OMG THE SOUND!
please let me know if you were able to fix it and how.
BTW, has ANYONE been able to get adb to work on win7 x64?

I had the same problem. I was able to fix it by going to the device manager and uninstalling the device listed under portable devices. Then when I unplugged and re-plugged in the HD, it showed up under Other Devices.

lkmiller said:
I had the same problem. I was able to fix it by going to the device manager and uninstalling the device listed under portable devices. Then when I unplugged and re-plugged in the HD, it showed up under Other Devices.
Click to expand...
Click to collapse
Didn't work for me.

r1c47 said:
I'm having the same problem. Were you able to get it working?
BTW, has ANYONE been able to get adb to work on win7 x64?
Click to expand...
Click to collapse
I've got it working with win7 64-bit and so does my husband.

Ok, I got it to work, somehow.
I'm not sure but here's what I think might have done it.
-with adb disabled connected the nook to the pc
-uninstalled device under portable device, it gets reinstalled automatically as BNTV600 under portable devices, again.
-restarted the nook and it's still recognized as BNTV600, without disconnecting it from the pc, enabled adb(which causes the pc to go into the annoying reconnect sound loop(now I noticed a usb mass storage device with the yellow yield sign with the exclamation mark so I decided to:
-click on the new device with the yield sign and select update device to install the device drivers for the adb(same as you would have tried normally before, just that this time it will work)
-check "adb devices" in command promt to make sure that it's being recognized
and that's pretty much what I think did it.
I think I've rooted it and enabled sideloading and disabled ota, I've yet to install any apps yet though. But there's this graphical glitch in the unlock screen which I think is a side effect from rooting(hope it isn't a glitch though...)
But yeah, I'm going to try installing an app now and will report back with my findings.

Thanks all for these suggestions. I had tried using various combinations of disbling / uninstalling but it never worked. I went to my Win XP Pro laptop and got it all hooked up in seconds that way.

r1c47 said:
Ok, I got it to work, somehow.
I'm not sure but here's what I think might have done it.
-with adb disabled connected the nook to the pc
-uninstalled device under portable device, it gets reinstalled automatically as BNTV600 under portable devices, again.
-restarted the nook and it's still recognized as BNTV600, without disconnecting it from the pc, enabled adb(which causes the pc to go into the annoying reconnect sound loop(now I noticed a usb mass storage device with the yellow yield sign with the exclamation mark so I decided to:
-click on the new device with the yield sign and select update device to install the device drivers for the adb(same as you would have tried normally before, just that this time it will work)
-check "adb devices" in command promt to make sure that it's being recognized
and that's pretty much what I think did it.
I think I've rooted it and enabled sideloading and disabled ota, I've yet to install any apps yet though. But there's this graphical glitch in the unlock screen which I think is a side effect from rooting(hope it isn't a glitch though...)
But yeah, I'm going to try installing an app now and will report back with my findings.
Click to expand...
Click to collapse
This worked great for me as well, thanks so much! I'm struggling to figure out how to use ADB to install an APK that I extracted from my phone. Aptoide worked for every app I wanted that I hadn't paid for in google play. But I have three apps I'd like to install that Aptoide does not have because they are paid apps. I'm stuck where I am trying to use ADB. All of the APK installers did not recognize the files if I just moved them to my nook from the computer. These are the files on my SD card. View attachment 4649607
The highlighted ones installed but the red circled one was a paid app and it did not even get recognized by the installer. I've gotten as far as getting my nook to be recognized in command prompt. I'm attempting to use command prompt to install the .apk but I think it may be a problem with the .apk itself. Do you know how to go about that? This is where I get stuck.
{
"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"
}
My other struggle is that my nook also does not allow me to send anything to it. It connects. It's recognized but it will not allow files to go onto it.
I'm not sure what to do now. It doesn't let me type anything at this point and my nook doesn't even respond to the fact that I'm trying to send something to it. Please let me know if I'm doing it all wrong. I realize how green I am. I know this was forever ago for you so if you can't remember it's no biggie.

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.

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.