So I have the OTA ICS update now. I want root again (didn't have it previously on this phone), so I decided I would try one of the "1-click" scripts. My problem now lies in my PC (win 7 64bit) and drivers I think. Downloaded the motorola utility to get all my correct drivers. When I plug up my phone, my pc downloads all the drivers, but it never downloads the Mot ADB interface one. I'm stumped. I've tried it on all 3 machines. I can transfer files and the phone mounts ok OTHER THAN the adb interface.
When I run adb shell it says "error: device not found"
Here's what I have done.
1. Uninstalled all my drivers
2. Re-installed all the drivers
3. Tried every USB port on the computer
4. Made sure USB Debugging was checked
5. Made sure my phone was in Media mode
6. Wiped cache and data
7. Tried it on other machines
8. Re-installed windows on 1 machine.
When I put the phone in AP Fastboot, then and ONLY then will the PC see the phone as an adb interface.
Any thoughts?
I think you need to switch it to a pc mode other people have said.
Sent from my GT-I9300 using xda premium
You use USB 2.0 ports?
Zanith said:
I think you need to switch it to a pc mode other people have said.
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
on the new ICS update there isn't a PC mode.
HSD-Pilot said:
You use USB 2.0 ports?
Click to expand...
Click to collapse
yes.
Here's what my device manager looks like. As you can see, it has NO option of ADB anywhere! Thinking it might be this phone.
{
"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"
}
jdenman03 said:
Here's what my device manager looks like. As you can see, it has NO option of ADB anywhere! Thinking it might be this phone.
Click to expand...
Click to collapse
This is what you should see:
pedrotorresfilho said:
This is what you should see:
Click to expand...
Click to collapse
You are correct. But its not prompting me even to install the adb interface. Thus the reason why I feel as though it is the phone and not the PC's. I run adb on my other phones just well.
Try typing
start adbd
In terminal emulator in your phone?
Sent from my GT-I9300 using xda premium
I'm going to assume you tried this link to get the drivers:
http://forum.xda-developers.com/showthread.php?t=1539192
If not, uninstall all the drivers you have currently and reboot and then go to the link above and get the Moto drivers and RSD Lite.
Another link is here which really gets in-depth on getting ADB to function:
http://www.droidrzr.com/index.php/t...find-out-how-to-manipulate-your-system-files/
Zanith said:
Try typing
start adbd
In terminal emulator in your phone?
Sent from my GT-I9300 using xda premium
Click to expand...
Click to collapse
this doesn't do anything.
iBolski said:
I'm going to assume you tried this link to get the drivers:
http://forum.xda-developers.com/showthread.php?t=1539192
If not, uninstall all the drivers you have currently and reboot and then go to the link above and get the Moto drivers and RSD Lite.
Another link is here which really gets in-depth on getting ADB to function:
http://www.droidrzr.com/index.php/t...find-out-how-to-manipulate-your-system-files/
Click to expand...
Click to collapse
tried this and still failed. I've done it now on 5 machines. All have the same issue. None of them ever prompt me to install drivers for adb interface. terminal emulater doesn't do anything on my phone either. Bout to take my phone to verizon.
OK I am running emulator on my phone, and when I enter command "adb shell" adb starts and still says "error: device not found"
gonna throw this phone to the wall. Thanks for all the suggestions and help thus far. If I can't get it fixed by tonight, i'll take it to verizon tomorrow and have them send me a replacement.
EDIT: Plugged in my wife's razr with usb debugging and everything worked correctly. DEFINITELY the phone! Can't believe I have wasted this past 2 days on this!
I am having the SAME EXACT problem running the same version of Windows. I'm guessing you haven't found a work around as of yet, eh? I still have been unable to get Windows to recognize the ADB interface. Whenever I connect my Bionic, it finds/installs it just fine, but not so much with the Razr Maxx.
Have you attempted a factory reset at all? The issue began with me because I rooted the device, used OTA rootkeeper, installed the OTA, but then Rootkeeper was unable to restore root, so I also tried to use the 1-click scripts.
jdenman03 said:
OK I am running emulator on my phone, and when I enter command "adb shell" adb starts and still says "error: device not found"
gonna throw this phone to the wall. Thanks for all the suggestions and help thus far. If I can't get it fixed by tonight, i'll take it to verizon tomorrow and have them send me a replacement.
EDIT: Plugged in my wife's razr with usb debugging and everything worked correctly. DEFINITELY the phone! Can't believe I have wasted this past 2 days on this!
Click to expand...
Click to collapse
I had the same issue.. You need to download Matts utility 1.7 and then extract the zip into an (empty) folder. Then click the first file in your folder and click on the 64 bit. Let it install then run the utility.. Make sure your device is in USB debugging mode and that you have your storage device set to mtb.. Then click the root android 4.0.4 option and let the program to the rest! I hope this helps it sure helped me.
Sent from my DROID RAZR using xda app-developers app
I had a very similar issue that was stopping me from re-rooting after I pulled the official OTA. At the end of it, my problem seemed to also center on not having the Mot Composite ADB Interface driver install when I connected the device by USB. I was running Moto Drivers ver. 5.7.0 (current) and successfully connected on other RAZRs, just not my current one. Same 'device not found' errors.
Connecting my device as a camera (PTP) fixed the problem (settings -> storage -> press the menu key and choose Camera (PTP). After doing that, windows installed the additional devices: USB Composite Device, DROID RAZR, and Mot Composite ADB Interface and I was back on track. Regardless of what I tried otherwise (including a wipe data) the ADB interface just wouldn't install until I connected as a camera.
My post is here:
http://forum.xda-developers.com/showthread.php?t=1743367&highlight=root+ota&page=2
EDIT: Just re-read the OP. Not just close. Sounds like you're having the SAME problem. Hope this helps.
At first I could not get this script to work. Apparently I had no ADB interface installed. What did the trick for me, was switching off the USB debugging, plugging in my Droid 4 a few times in camera, MTP and mass storage mode. That made my computer install all the necessary drivers.
Having done this, it all worked perfectly. Thank you very much! I am completely new to Android and XDA, and this almost foolproof script is excellent. :good:
So simple..
Had same problems with my new phone as everyone else, PC not recognizing ADB .... tried downloading a couple of different things from other advice as I don't know much about computers this just got confusing. All I had to do was turn off the USB debugging, plug in under the different USB computer connections and ta da!
No Storage Drives Show
Hi everyone.
First time I post on the forum, although I've been using it for quite some time.
This time I'm experiencing an annoying situation with which I spent many hours of my last two days.
Turns out my Windows (7 64-bit) won't display the mass storage drives from my Droid Razr (XT910 Model, Brazilian Carrier OTA).
The funny thing is that all Motorola Drivers are shown on Device Manager and when in AP Fastboot Mode, RSD will recognize the phone as connected and flash normally.
I am really out of ideas here. Did religiously everything written on this forum and many others:
Tried different cables and pcs
ReInstalled ICS OTA
Wiped cache/data
Factory Reset from Android
Tried to connect as Camera, Media and Mass Storage
Tried with USB Debugging both on and off
One thing that may have caused the problem, from what I recall, is I am running without the cid file, as I deleted it to install JellyBean through the steps suggested by "TheRazRGuy" here on xda.
Thing is, as I don't have the cid, I must boot through BPTools on bootmanager everytime the system is turned on. After I downgraded the JellyBean to ICS OTA again, I went on to root the device but forgot about the boot requirement I described.
After the easyroot first reboot, the screen went black as always when normal reboot without cid. Even though easyroot still rebooted 2 more times and displayed the "your phone is rooted" message, I thing something may have gone wrong on this process.
It is worth saying that with JB the mass storage was being shown and before the easyroot process too..
I am really out of clues here, hope someone can help!
Found a solution on another thread:
http://forum.xda-developers.com/showthread.php?p=36543010#post36543010
Just had to modify an option on BootMenu Manager
Related
Question for the community:
I have recently joined the Droid Razr community as a previous Droid Charge owner. I've been having a horrible time getting my device to root. (I've never had issues with any other device).
I installed the motorola drivers for Windows 7.
I am using a Verizon XT912 running android 4.0.4 ICS.
When using any of the auto-root scripts here I get "device not found".
Upon researching further into the situation, I have attempted downloading the android SDK and using the adb that comes with it. I've uninstalled all other phone drivers from Windows 7. I restarted/uninstalled motorola drivers/restarted and adb still finds no devices.
EDIT: I've also tried all the different USB ports on my computer.
I can verify adb doesn't find the droid razr by typing "adb devices" at the command prompt. Windows 7 Device Manager shows Droid Razr installed with a working driver.
Any help would be appreciated.
SOLUTION: I read the thread here http://forum.xda-developers.com/showthread.php?t=1743367&highlight=root+ota&page=2 after doing three million different things to my phone. Finally, I did a factory reset. When my phone reset, I did NOT set up my google account. I then made sure the USB mode was in PTP camera mode and USB debugging was on. I installed the motorola drivers from this thread http://forum.xda-developers.com/showthread.php?t=1539192 !!! DO NOT INSTALL THE ONES FROM MOTOROLA's website, they are pure garbage !!!. adb now recognizes my device.
A big shout out to clifference for posting what worked for him. And a big thumbs down to motorola for posting horrible drivers on their website.
This was such a large problem that I have documented it on my blog. Fix adb Droid Razr Problems
THANK YOU
Have been beating my head against this issue for weeks (ever since the ICS OTA update). I was on the verge of reinstalling Windows, but this fixed the issue completely. THANK YOU!!!!!
arsenik13 said:
Question for the community:
I have recently joined the Droid Razr community as a previous Droid Charge owner. I've been having a horrible time getting my device to root. (I've never had issues with any other device).
I installed the motorola drivers for Windows 7.
I am using a Verizon XT912 running android 4.0.4 ICS.
When using any of the auto-root scripts here I get "device not found".
Upon researching further into the situation, I have attempted downloading the android SDK and using the adb that comes with it. I've uninstalled all other phone drivers from Windows 7. I restarted/uninstalled motorola drivers/restarted and adb still finds no devices.
EDIT: I've also tried all the different USB ports on my computer.
I can verify adb doesn't find the droid razr by typing "adb devices" at the command prompt. Windows 7 Device Manager shows Droid Razr installed with a working driver.
Any help would be appreciated.
SOLUTION: I read the thread here http://forum.xda-developers.com/showthread.php?t=1743367&highlight=root+ota&page=2 after doing three million different things to my phone. Finally, I did a factory reset. When my phone reset, I did NOT set up my google account. I then made sure the USB mode was in PTP camera mode and USB debugging was on. I installed the motorola drivers from this thread http://forum.xda-developers.com/showthread.php?t=1539192 !!! DO NOT INSTALL THE ONES FROM MOTOROLA's website, they are pure garbage !!!. adb now recognizes my device.
A big shout out to clifference for posting what worked for him. And a big thumbs down to motorola for posting horrible drivers on their website.
This was such a large problem that I have documented it on my blog. Fix adb Droid Razr Problems
Click to expand...
Click to collapse
Keeps disappearing
Resetting worked for me... for minutes. Then the phone didn't show again.
I'm on a Mac, there are no drivers. Simply keeps disappearing after the first time it works, and then I have to reset again.
There also is an official thread on Motodev community.
arsenik13 said:
Question for the community:
I have recently joined the Droid Razr community as a previous Droid Charge owner. I've been having a horrible time getting my device to root. (I've never had issues with any other device).
I installed the motorola drivers for Windows 7.
I am using a Verizon XT912 running android 4.0.4 ICS.
When using any of the auto-root scripts here I get "device not found".
Upon researching further into the situation, I have attempted downloading the android SDK and using the adb that comes with it. I've uninstalled all other phone drivers from Windows 7. I restarted/uninstalled motorola drivers/restarted and adb still finds no devices.
EDIT: I've also tried all the different USB ports on my computer.
I can verify adb doesn't find the droid razr by typing "adb devices" at the command prompt. Windows 7 Device Manager shows Droid Razr installed with a working driver.
Any help would be appreciated.
SOLUTION: I read the thread here http://forum.xda-developers.com/showthread.php?t=1743367&highlight=root+ota&page=2 after doing three million different things to my phone. Finally, I did a factory reset. When my phone reset, I did NOT set up my google account. I then made sure the USB mode was in PTP camera mode and USB debugging was on. I installed the motorola drivers from this thread http://forum.xda-developers.com/showthread.php?t=1539192 !!! DO NOT INSTALL THE ONES FROM MOTOROLA's website, they are pure garbage !!!. adb now recognizes my device.
A big shout out to clifference for posting what worked for him. And a big thumbs down to motorola for posting horrible drivers on their website.
This was such a large problem that I have documented it on my blog. Fix adb Droid Razr Problems
Click to expand...
Click to collapse
Big thanks from me! I worked on this all weekend and could NOT figure out why I could never see device as ADB. Factory Reset and immediately connecting worked long enough to get me rooted
arsenik13 said:
Question for the community:
I have recently joined the Droid Razr community as a previous Droid Charge owner. I've been having a horrible time getting my device to root. (I've never had issues with any other device).
I installed the motorola drivers for Windows 7.
I am using a Verizon XT912 running android 4.0.4 ICS.
When using any of the auto-root scripts here I get "device not found".
Upon researching further into the situation, I have attempted downloading the android SDK and using the adb that comes with it. I've uninstalled all other phone drivers from Windows 7. I restarted/uninstalled motorola drivers/restarted and adb still finds no devices.
EDIT: I've also tried all the different USB ports on my computer.
I can verify adb doesn't find the droid razr by typing "adb devices" at the command prompt. Windows 7 Device Manager shows Droid Razr installed with a working driver.
Any help would be appreciated.
SOLUTION: I read the thread here http://forum.xda-developers.com/showthread.php?t=1743367&highlight=root+ota&page=2 after doing three million different things to my phone. Finally, I did a factory reset. When my phone reset, I did NOT set up my google account. I then made sure the USB mode was in PTP camera mode and USB debugging was on. I installed the motorola drivers from this thread http://forum.xda-developers.com/showthread.php?t=1539192 !!! DO NOT INSTALL THE ONES FROM MOTOROLA's website, they are pure garbage !!!. adb now recognizes my device.
A big shout out to clifference for posting what worked for him. And a big thumbs down to motorola for posting horrible drivers on their website.
This was such a large problem that I have documented it on my blog. Fix adb Droid Razr Problems
Click to expand...
Click to collapse
Good to know the solution works. I had to use it. I was never aware that you had to have your device in camera mode when connected to your PC. That's what was screwing me..
Losing hope...
vazersecurity said:
Good to know the solution works. I had to use it. I was never aware that you had to have your device in camera mode when connected to your PC. That's what was screwing me..
Click to expand...
Click to collapse
I have the similar issue... just my problem is much more complex since I cant enter the Android or do anything with the phone. My phone keep on restarting every 1 min while showing dead android picture in a meantime.
I cant use RSD Lite and fastboot new android on my phone, since phone isnt connected with computer and computer always keep on showing me message:
The last USB device conected to this computer is malfunctioned windows can not recognize it.
Recommendation:
Try reconnecting device. If Windows stil does not recognize it, your device may not work properly.
I tried installilng new drivers million times. I tried using motohelper drivers but still the same. Also I changed PC but again the same!!!!
I cant use ADB since my phone isnt connected with computer, same issue.
While watching dead android picture I can just enter recovery mode where I have these options:
-reboot system now
-apply update from external storage
-apply update from ADB
-wipe data/factory reset
-wipe cache partition
I tried wipe options but nothing. While I cant update from ADB.
I really dont know what to do...
JoLoLo said:
I have the similar issue... just my problem is much more complex since I cant enter the Android or do anything with the phone. My phone keep on restarting every 1 min while showing dead android picture in a meantime.
I cant use RSD Lite and fastboot new android on my phone, since phone isnt connected with computer and computer always keep on showing me message:
The last USB device conected to this computer is malfunctioned windows can not recognize it.
Recommendation:
Try reconnecting device. If Windows stil does not recognize it, your device may not work properly.
I tried installilng new drivers million times. I tried using motohelper drivers but still the same. Also I changed PC but again the same!!!!
I cant use ADB since my phone isnt connected with computer, same issue.
While watching dead android picture I can just enter recovery mode where I have these options:
-reboot system now
-apply update from external storage
-apply update from ADB
-wipe data/factory reset
-wipe cache partition
I tried wipe options but nothing. While I cant update from ADB.
I really dont know what to do...
Click to expand...
Click to collapse
So you can't get the computer to connect to the phone while it's in fastboot mode?
vazersecurity said:
So you can't get the computer to connect to the phone while it's in fastboot mode?
Click to expand...
Click to collapse
First the problem was somehow with drivers, but I got advice to uninstall all drivers (Motorola, Nokia, Samsung) which I had on my PC, and to reinstall just motorola drivers, and that fixed problem.
After that I got new problem with empty battery, so my phone was completely briced, but creating a factory cable solve everything
JoLoLo said:
First the problem was somehow with drivers, but I got advice to uninstall all drivers (Motorola, Nokia, Samsung) which I had on my PC, and to reinstall just motorola drivers, and that fixed problem.
After that I got new problem with empty battery, so my phone was completely briced, but creating a factory cable solve everything
Click to expand...
Click to collapse
Okay, good to know you got the problem solved.
tks
this helped a lot!! tkss
Slightly Alternative Solution
arsenik13 said:
Question for the community:
SOLUTION: I read the thread here http://forum.xda-developers.com/showthread.php?t=1743367&highlight=root+ota&page=2 after doing three million different things to my phone. Finally, I did a factory reset. When my phone reset, I did NOT set up my google account. I then made sure the USB mode was in PTP camera mode and USB debugging was on. I installed the motorola drivers from this thread http://forum.xda-developers.com/showthread.php?t=1539192 !!! DO NOT INSTALL THE ONES FROM MOTOROLA's website, they are pure garbage !!!. adb now recognizes my device.
Click to expand...
Click to collapse
I had this problem with the Motorolla Turbo. To fix it I did two of the things you suggested and one third not listed here.
1.) Download the drivers from http://forum.xda-developers.com/showthread.php?t=1539192
2.)Made sure the USB mode was in PTP camera mode.
3.) I manually installed the adb drivers on the phone by following the steps in this tutorial.
http://visualgdb.com/tutorials/android/usbdebug/manualinstall.php
Hopefully this information will help someone who needs it.
So I tried searching google and the forums and found nothing.
So on multiple PC's it will charge my DNA but it will not detect it in device manager, like it's not plugged in at all. Almost like it's not seeing any RX/TX Just VCC and Ground. I've tried 3 different Pc's and probably 10 different USB cables. Multiple roms and it will not even see it in bootloader. Not sure if anyone else has experienced this issue, it's been going on for months, I can do pretty much everything without USB access to my phone but if I want to RUU I'm going to be SOL.
Any thoughts?
yutsoku said:
So I tried searching google and the forums and found nothing.
So on multiple PC's it will charge my DNA but it will not detect it in device manager, like it's not plugged in at all. Almost like it's not seeing any RX/TX Just VCC and Ground. I've tried 3 different Pc's and probably 10 different USB cables. Multiple roms and it will not even see it in bootloader. Not sure if anyone else has experienced this issue, it's been going on for months, I can do pretty much everything without USB access to my phone but if I want to RUU I'm going to be SOL.
Any thoughts?
Click to expand...
Click to collapse
What operating system are u using? I started a thread about windows 8 not seeing the dna in bootloader. it happens because htc has not updated the drivers for windows 8
heres the link http://forum.xda-developers.com/showthread.php?t=2521504
Win7 and linux... Think its a phone issue. Well I'm 99% sure
Sent from my HTC6435LVW using Tapatalk
Do you have drivers installed and can you boot into recovery and mount ur device? You may need adb installed. Do you have SDK drivers installed.
Another good way to get ur computer to see ur phone is to download pdanet and it will install the needed drivers to see ur phone.
thayl0 said:
Do you have drivers installed and can you boot into recovery and mount ur device? You may need adb installed. Do you have SDK drivers installed.
Another good way to get ur computer to see ur phone is to download pdanet and it will install the needed drivers to see ur phone.
Click to expand...
Click to collapse
i have done all that. i can adb into bootloader but once in bootloader the computer does not recognize the phone anymore.
thayl0 said:
Do you have drivers installed and can you boot into recovery and mount ur device? You may need adb installed. Do you have SDK drivers installed.
Another good way to get ur computer to see ur phone is to download pdanet and it will install the needed drivers to see ur phone.
Click to expand...
Click to collapse
Not quite understanding, it's not a driver issue... The PC it's self will not see the device. Not even in device manager as an unknown device, the phone it's self will not say, "Hello PC I am here, do you have my drivers?" I plug it in, get nothing as if I am using a charging cable with only VCC and ground, without RX/TX. I'm pretty positive that it's a phone issue, not a PC/Driver issue. Even if it was a driver issue I'd be getting the MTP device showing up.
yutsoku said:
Not quite understanding, it's not a driver issue... The PC it's self will not see the device. Not even in device manager as an unknown device, the phone it's self will not say, "Hello PC I am here, do you have my drivers?" I plug it in, get nothing as if I am using a charging cable with only VCC and ground, without RX/TX. I'm pretty positive that it's a phone issue, not a PC/Driver issue. Even if it was a driver issue I'd be getting the MTP device showing up.
Click to expand...
Click to collapse
Actually it could be a driver issue. There has to be a driver installed for something to notice something.
Go to device manager and look at the very top when you connect your phone does it show this?
{
"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"
}
Or the driver could be corrupted and you tried to uninstall and reinstall
thayl0 said:
Actually it could be a driver issue. There has to be a driver installed for something to notice something.
Go to device manager and look at the very top when you connect your phone does it show this?
View attachment 2408658
Or the driver could be corrupted and you tried to uninstall and reinstall
Click to expand...
Click to collapse
Driver isn't installed on my work PC still nothing. Tried driver on work PC...still nothing :/
Sent from my HTC6435LVW using Tapatalk
yutsoku said:
Driver isn't installed on my work PC still nothing. Tried driver on work PC...still nothing :/
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
Heres what I just had to do because my phone wasn't being seen by my pc.
http://www.youtube.com/watch?v=oaNM-lt_aHw
Do that and after boot into recovery and mout the system is should reinstall the correct driver.
Confirmed it's not drivers my phone can't see USB otg either. Probably my phone is defective
Sent from my HTC6435LVW using Tapatalk
yutsoku said:
Confirmed it's not drivers my phone can't see USB otg either. Probably my phone is defective
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
I find that to be very rare but okay best the luck to you.
Hey!
This is my first time posting, but I have read tons of threads on here over the last year or so with my Droid DNA.
A while ago, I rooted my DNA, and unlocked the Bootloader, and used moonshine for S-OFF. I now want to undo all that I have done. Wiping data is no issue, I backed up all my info. I plan to get a new phone soon. Basically, I can't get adb drivers to work. So I deleted my drivers, and installed the ones mentioned in the thread linked below, and I can't find how to get these drivers to work.
My plan is to follow this thread, using step 3 (for moonshine). I have TWRP installed, and flashed the lock_bootlader.zip file provided there. I cannot get adb to work, however, for the next step. For example, "adb devices" returns no devices. And thus i cannot use adb commands. When I run "adb devices", it shows this. What do I do??
Thanks
Some more clarification:
I might also add that Device manager shows my phone as "HTC6435LVW", under "Portable Devices". It seems to recognize it as an MTP Device when I try to update the drivers, and won't let me update the drivers, because "The best driver software for your device is already installed".
In addition, HTC Sync Manager does not recognize my phone either. I should mention that I already chose "Reset Phone" from the Settings menu, and then also did a Factory Reset from TWRP.
I'm so confused by all this - Why can't I get ADB to recognize it?? I have been and will continue to be searching for solutions to this problem here on XDA and also on Google. And do I even need to do all this to give my phone back to Verizon?
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
RLGL said:
Try getting the drivers from PDAnet. If you are using Windoze 8 or 8.1 , good luck.
Click to expand...
Click to collapse
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
av ed said:
I am very interested in this as I am having a similar problem. This is the guide I attempted numerous times with no success http://forum.xda-developers.com/showthread.php?t=2293919.
Click to expand...
Click to collapse
Ok thanks I will try this when I get home. Glad to see I'm not the only one with the problem!
EDIT: Thats the thread I am following, as I stated in the OP.
[/URL]
antrom1818 said:
I tried that, it gets stuck at the USB Driver Installation page, when it asks to connect your phone. I have USB debugging enabled, and I even installed PdaNet on my phone to try to use their "USB Mode". The DNA has not USB options for Mass Storage, etc like the pdanet driver help page ( pdanet . co / driver ) (It wont let me post a link because I'm a new user, sorry) tells me to look for.
Windows device manager does not recognize it as an Android phone, but instead as a portable device, could this be a problem?
Thanks for your reply
Click to expand...
Click to collapse
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
RLGL said:
[/URL]
My device manager shows 2 entries:
Portable device
HTC6435LVW
and
Android USB Device
My HTC
You did not state the OS your computer has.........
See post from Santod040
Click to expand...
Click to collapse
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
antrom1818 said:
Windows 7, and my Device Manager does NOT show the Android USB Device>My HTC. Thats the problem that I am asking for help with, the USB drivers.
Click to expand...
Click to collapse
Try a different cable.
RLGL said:
Try a different cable.
Click to expand...
Click to collapse
Thanks for the suggestion, I will try it when I get home and report back with an edit to this post!
EDIT: Nope, didn't work. Momentarily, I got it to install drivers. During that time, adb worked but not fastboot. So then I deleted the drivers to try to reinstall for fastboot, and now neither of them works.
Hello, I'm having a few different issues when I go to install the latest 4.4.3 (or any for that matter) RUU. I've connected my phone to my laptop and downloaded HTC sync and have automatically updated the drivers. However when I go to actually install the ruu, the usb disconnects and I'm forced to hard reset the phone to get it unstuck. I've tried this with two different USB cords and two separate computers. Any advice? Stuck without service and I'd really like to see UPSM and boomsound improvements. This is completely stock. Thank you
What OS. USB 3.0 ports or 2.0…?
Win 8.1 with USB 3.0 ports can be finicky to get it to work just right.
- Sent from a payphone ...
tommy_riley said:
What OS. USB 3.0 ports or 2.0…?
Win 8.1 with USB 3.0 ports can be finicky to get it to work just right.
- Sent from a payphone ...
Click to expand...
Click to collapse
Both are running Windows 7. I'm not sure on the USB ports, I believe they're 2.0
What hboot numbers is the phone currently on?
It is the AT&T branded version M8, correct? I only ask, because folks sometimes come on here trying to flash an AT&T RUU on another version device.
Any error messages when the RUU fails?
redpoint73 said:
What hboot numbers is the phone currently on?
It is the AT&T branded version M8, correct? I only ask, because folks sometimes come on here trying to flash an AT&T RUU on another version device.
Any error messages when the RUU fails?
Click to expand...
Click to collapse
The # is 3.16.0.000. The errors I receive are 170 & 171, something about the usb disconnectingand to check it and try again.
Sounds like a driver issue. Uninstall HTC related drivers and install the drivers from adb or the google drivers.
- Sent from a payphone ...
tommy_riley said:
Sounds like a driver issue. Uninstall HTC related drivers and install the drivers from adb or the google drivers.
- Sent from a payphone ...
Click to expand...
Click to collapse
Just tried this as suggested abd still getting the same error. I get far enough that I can accept the version update on the ruu, the phone displays "HTC" against a black screen, and the usb disconnects. I uninstalled all the drivers and after I plugged in the cord, the sync manager said it was updating the drivers. Should o uninstall sync manager and try again?
Yeah get rid of sync manager. After its gone try the alternative drivers and make sure the phone comes up correctly in device manager then try RUU again. It might be a matter of trying a few different driver vs RUU combinations.
If the system only has USB 3.0 ports and its an Intel chip set then you might also try and go install the latest Intel USB port drivers directly from their website. If the USB port drivers are outdated or if Microsoft has their drivers in for USB instead of Intel's (on 3.0 ports only most of the time) what will happen is everything will look fine with connection to phone via USB from computer but once you are in recovery or fastboot mode the connection will be lost.
I can give more specifics if you want to go down this route much later in the evening with screen shots and driver locations if needed, I'm just on my phone ATM on my way to work. So it would be much later tonight. Let me know...
- Sent from a payphone ...
tommy_riley said:
Yeah get rid of sync manager. After its gone try the alternative drivers and make sure the phone comes up correctly in device manager then try RUU again. It might be a matter of trying a few different driver vs RUU combinations.
If the system only has USB 3.0 ports and its an Intel chip set then you might also try and go install the latest Intel USB port drivers directly from their website. If the USB port drivers are outdated or if Microsoft has their drivers in for USB instead of Intel's (on 3.0 ports only most of the time) what will happen is everything will look fine with connection to phone via USB from computer but once you are in recovery or fastboot mode the connection will be lost.
I can give more specifics if you want to go down this route much later in the evening with screen shots and driver locations if needed, I'm just on my phone ATM on my way to work. So it would be much later tonight. Let me know...
- Sent from a payphone ...
Click to expand...
Click to collapse
I uninstalled sync manager and the phone proceeded to Download the drivers again (in addition to an older sync manager driver for some reason) but still no avail. The laptop is definitely an Intel powered one, I'd greatly appreciate if you could post those screenshots when you get the chance
is fastboot enabled? If stock it is not enabled by default...enable it and try again. If you do not know how to enable it follow this:
Settings>About>Software information>More
Tap on build number 7 times repeatedly developer options will be enabled
Go back to settings open Developer options, make sure USB Debugging is enabled
WNC - Good point.
- Sent from a payphone ...
tommy_riley said:
WNC - Good point.
- Sent from a payphone ...
Click to expand...
Click to collapse
I tried installing it in fastboot usb but It didn't even detect the phone. Is there another type of fastboot or is that the only way?
Only one fastboot. Sounds more and more like a driver issue,be it a usb system driver update or htc driver update...something is amiss on that end.
Apologies for not getting back to this thread. Started a new work assignment this week causing my commute to significantly increase (along with a nasty storm yesterday resulting in power outage). I'll get back here this weekend when I have some time to login from home computer...
- Sent from a payphone ...
So, there are a few ways to check if you have USB3.0 drivers
One, is to look at the USB ports on your laptop/computer - unless it's a custom gaming rig, the USB2.0 ports plastic tabs will be black, while the USB3.0 ports will be blue - if all of your little plastic tabs inside the actual USB ports are blue, then sounds like you have USB3.0 ports only.
The other way is to go into your device manager and look at see what it lists under USB - refer to the below image. Should look like something similar to as follows:
{
"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"
}
Now, provided that you have an INTEL chipset AND these 3.0 extensible drivers are currently using Microsoft drivers, then what you may want to do is replace the Microsoft Intel USB 3.0 drivers with the INTEL drivers themselves.
What you would look for is your chipset version of the intel chipset (e.g. C220, C217, C270 etc) you should see other areas in your device manager that will refer to your Intel chipset type) then do a search on Intel's website for "USB 3.0 driver C216" (or C220, C270 etc) and download the drivers for your version of Windows (Windows 7 64bit? probably)
The download center for Intel is here: https://downloadcenter.intel.com/
The original article where I ran into this same situation was located here - for some reason I still have it book marked. I was trying to update/root an HTC EVO LTE about two years ago and ran into this issue on Windows 8 - I imagine a similar issue exists on Windows 7 USB3.0 only systems. This allowed me to keep my connection to my EVO while in fastboot mode (no USB disconnected) on Windows 8 and do what I needed to do to root my phone. It was my first root and folks were saying it was impossible to use Win8 with USB3.0 only ports to accomplish this task, but using the method at the link I was able to : http://plugable.com/2012/12/01/windows-8-and-intel-usb-3-0-host-controllers
Here's to hoping you are running into something similar. If not, the next area I would try is just going to Intel's website and download there own driver check utility which should search your computer for all of their own drivers and download install the updated ones. You can try that out too.
Let me know how it goes.
ISSUE RESOLVED. See post #17 for solution.
Hi, I have a Redmi Note 4 Qualcomm variant with MIUI Global 8.5 | Stable 8.5.4.0 (NCFMIED) ROM. I want to unlock the bootloader but MI Unlock Tool (v2.3.803.10) cannot recognize the phone in fastboot mode. I've gotten the permission to unlock.
I've tried v2.2 of the tool and encountered same problem. Tried multiple drivers, plugging phone in/out. Running "fastboot devices" command shows the device is connected. Tried installing Mi Driver that came with the tool but its setup says it's installed while the unlock tool says it isn't.
Suggestions appreciated. Thanks.
Note: I'm running Win 10 x64 Creator's Update (15063).
Hexerus said:
Hi guys, I have Redmi Note 4 Qualcomm Global variant with MIUI Global 8.5 | Stable 8.5.4.0 (NCFMIED). I want to unlock the bootloader but MI Unlock Tool (v2.3.803.10) cannot recognize the phone (connected in fastboot mode). I have gotten the permission to unlock. I'm running Win 10 x64 Creator's Update build 15063.
I've tried v2.2 of the tool and encountered same problem. Tried multiple drivers, plugging phone in/out. Running "fastboot devices" command shows the device is connected. Tried installing Mi Driver that come with the tool, its setup says it's installed but the unlock tool says it isn't. Really confused right now.
Any suggestion appreciated.
Click to expand...
Click to collapse
Did you enable usb debugging in developer options?
No you didn't
Stevica Smederevac said:
Did you enable usb debugging in developer options?
No you didn't
Click to expand...
Click to collapse
Yes I did Enabled both OEM unlocking and USB debugging. For a person to unlock phone / flash ROM, expect him to at least know this.
Hexerus said:
Yes I did Enabled both OEM unlocking and USB debugging. For a person to unlock phone / flash ROM, expect him to at least know this.
Click to expand...
Click to collapse
I don't expect anything, sometimes you have to start from the beginning. . With that attitude,i have nothing more to say.
Stevica Smederevac said:
I don't expect anything, sometimes you have to start from the beginning. . With that attitude,i have nothing more to say.
Click to expand...
Click to collapse
I'm really sorry if it offended you. Didn't mean to be rude. It's late night and I'm really tired trying again and again with different changes. Googling didn't end up with satisfactory solutions so posted in a few forums. Apparently everyone is past this stage and into 50% and account binding errors. I don't know why I'm stuck here. Even MiFlash detects the phone but not Mi Unlock.
Again I'm sorry for that comment. I should have written it in OP.
Disable driver enforcement in windows 10 and then try again from start.
Hexerus said:
I'm really sorry if it offended you. Didn't mean to be rude. It's late night and I'm really tired trying again and again with different changes. Googling didn't end up with satisfactory solutions so posted in a few forums. Apparently everyone is past this stage and into 50% and account binding errors. I don't know why I'm stuck here. Even MiFlash detects the phone but not Mi Unlock.
Again I'm sorry for that comment. I should have written it in OP.
Click to expand...
Click to collapse
So many things are now installed that it would be a good idea to uninstall as much as possible including drivers.
After that install one version of unlock tool and try again.
Pretty confusing that only unlock tool can't recognize the device.
I think you already tried but I'll suggest anyway, try with different USB ports. Maybe you are plugged in usb hub or 3.0 and for some reason unlock tool is not working.
Reboot into bootloader and then type "fastboot devices" in the adb cmd. If it doesn't recognize any fastboot devices then you need fastboot driver. Use universal adb driver for that. Hope it helps.
EDIT: Sorry didn't notice that OP already tried this. I think maybe at this point you should try using a different computer, or log in from a different account on your pc.
small2cats482 said:
Reboot into bootloader and then type "fastboot devices" in the adb cmd. If it doesn't recognize any fastboot devices then you need fastboot driver. Use universal adb driver for that. Hope it helps.
Click to expand...
Click to collapse
But he said it does in fastboot but only not in unlock tool.
Try installing Mi pc suite..! If you have already. Then try reinstalling it.. Then check if your phone gets detected there.
himesh_d said:
Disable driver enforcement in windows 10 and then try again from start.
Click to expand...
Click to collapse
Did that. No luck. Although, I'm wondering why I didn't get this red "Can't verify the publisher" message:
{
"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"
}
.
It's assumed to be the reason for disabling driver signature enforcement according to many tutorials around the web. It is supposed to come when MiFlash is being installed but I didn't get it while installing MiFlashSetup_eng.msi (latest MiFlash tool).
Stevica Smederevac said:
So many things are now installed that it would be a good idea to uninstall as much as possible including drivers.
After that install one version of unlock tool and try again.
Pretty confusing that only unlock tool can't recognize the device.
I think you already tried but I'll suggest anyway, try with different USB ports. Maybe you are plugged in usb hub or 3.0 and for some reason unlock tool is not working.
Click to expand...
Click to collapse
Yes, exactly. I first installed Universal ADB drivers that gets installed in Program Files/Clockwork something folder. Then I downloaded ADB driver installer from here: http://adbdriver.com/. They have a GUI tool that apparently show whether drivers are correctly installed or not when you plug in your phone, and prompts to install if not. It showed a green dot, so I didn't install it. Then, since it wasn't working (the tool), I tried ADB 1.4.3 from here (XDA). Same result. I also tried Xiaomi's own driver that come with Unlock tool with its own setup. That is also not working, unfortunately. Every time, adb.exe and fastboot.exe recognizes phone in their respective modes, but not the tool.
I've tried uninstalling and reinstalling drivers through Device Manager, as there seems to be no folder in C: and no entry in Programs and Features for any driver. I think I have to try another PC. Not sure if a virtual machine would do (I can setup a Win7 VM just for the sake). Finding another PC would require waiting
And yes, tried different ports.
zerohunk said:
Try installing Mi pc suite..! If you have already. Then try reinstalling it.. Then check if your phone gets detected there.
Click to expand...
Click to collapse
Regarding MI PC suite, I installed it a few weeks ago and it wasn't detecting the phone, even with the ADB drivers installed and USB debugging and everything turned on. I googled it and found out that Xiaomi hasn't updated it to support devices running Marshmallow or later. It only works with Lollipop and prior devices. So yeah I will try but I think the result will be same i.e. phone won't get detected.
Hexerus said:
Yes, exactly. I first installed Universal ADB drivers that gets installed in Program Files/Clockwork something folder. Then I downloaded ADB driver installer from here: http://adbdriver.com/. They have a GUI tool that apparently show whether drivers are correctly installed or not when you plug in your phone, and prompts to install if not. It showed a green dot, so I didn't install it. Then, since it wasn't working (the tool), I tried ADB 1.4.3 from here (XDA). Same result. I also tried Xiaomi's own driver that come with Unlock tool with its own setup. That is also not working, unfortunately. Every time, adb.exe and fastboot.exe recognizes phone in their respective modes, but not the tool.
I've tried uninstalling and reinstalling drivers through Device Manager, as there seems to be no folder in C: and no entry in Programs and Features for any driver. I think I have to try another PC. Not sure if a virtual machine would do (I can setup a Win7 VM just for the sake). Finding another PC would require waiting
And yes, tried different ports.
Click to expand...
Click to collapse
I also ha windows 10 and minimal adb and fastboot tool. I didn't require any other drivers. My phone is recognized in every situation
Hexerus said:
Regarding MI PC suite, I installed it a few weeks ago and it wasn't detecting the phone, even with the ADB drivers installed and USB debugging and everything turned on. I googled it and found out that Xiaomi hasn't updated it to support devices running Marshmallow or later. It only works with Lollipop and prior devices. So yeah I will try but I think the result will be same i.e. phone won't get detected.
Click to expand...
Click to collapse
My Rn4 was on android nougat stable ROM when i installed mi pc suite and it did get detected.. I do remember while installing it asked me if i wanted to install drivers.. Click on yes! I think that will do it for you!
zerohunk said:
My Rn4 was on android nougat stable ROM when i installed mi pc suite and it did get detected.. I do remember while installing it asked me if i wanted to install drivers.. Click on yes! I think that will do it for you!
Click to expand...
Click to collapse
Mine says "Connect your device via USB" as soon as a plug phone. I too have nougat stable version. Which PC suite version do you have? I have 3.2.1.3111. It didn't prompt for any driver installation. Do you enable USB debugging while connecting to PC suite? Tried MTP and PTP modes, still the same.
Edit 1: Sometimes getting the "You need to update your device to use Mi PC suite..." a few moments after the previous error.
I finally went past this step. Here's my short guide to resolve the issue:
Note: I'm using Mi Unlock tool version 2.3.803.10 on Windows 10 x64 build 15063. This is the tool's latest version as of 28 August, 2017.
1. Extract the zipped archive of MI Unlock tool to a new folder in the root of your system drive, like C:\any_folder. I extracted it to C:\unlock, making the path of the tool's executable: "C:\unlock\miflash_unlock.exe".
2. Run MiUsbDriver.exe from the folder as administrator and, even if it already says "Driver installed", click "Install" to make sure. Click "Retesting" to see if it says the same. Close the program.
3. Put your device into fastboot mode (make sure to turn on USB debugging and OEM unlocking in the developer options), and connect it through USB 2.0 port. (I don't know if 2.0/3.0 makes a difference but if you have 2.0 available, use it).
4. Go to device manager. Expand "Android Phone", right click "Android Bootloader Interface" and click properties. Click on "Driver" tab. See if the driver provider is "Xiaomi Technology, Inc.", driver date is "11/3/2016", and driver version is "16.0.0.0".
If it's not then:
(a) Close the properties window.
(b) Right click android bootloader interface and click "Update driver".
(c) Click "Browse my computer for driver..." -> "Let me pick from a list ...".
(d) Uncheck "Show compatible hardware".
(e) Select "Xiaomi Technology, Inc." from the left side and "Android Bootloader Interface" from the right and click next.
After it's installed, check the properties -> driver tab of "Android Bootloader Interface" to make sure driver provider, date and version is what I mentioned above.
5. Go to unlock tool folder. Go to driver\win10 folder, right click android_winusb.inf and click install. You'll get operation completed successfully message.
6. Go back to unlock folder and run the tool as administrator. Now before clicking agree, click on the settings gear on the top right corner. Here, MI Usb Driver should say "Already installed". If it doesn't, it won't work. In that case, you can check/re-do steps 1-5 to see if it helps. No idea beyond that.
7. Now you're good to go. Click agree, sign in and voila, your phone shall be connected, ready to unlock.
Thanks.
Hexerus said:
Oh THANK GOD, I finally went past this step. Thank heavens jeez. So here's my short guide that tells what I did to resolve this problem.
Note: I have Mi Unlock tool version 2.3.803.10 (latest as of now). I'm on Windows 10 x64 build 15063.
1. Extract the zipped archive of MI Unlock tool to the root of your system drive, like C:\any_folder. I extracted it to C:\unlock, so the path of the tool's executable became "C:\unlock\miflash_unlock.exe"
2. Run MiUsbDriver.exe from the folder with as administrator and click "Install". Make sure it says "Driver installed" after that. If it already says that, hit install again just to make sure. Click "Retesting" to see if it remains the same. Close the program after.
3. Put your device into fastboot mode (make sure to turn on USB debugging and OEM unlocking in the developer options), and connect it through USB 2.0 port. (I don't know if 2.0/3.0 makes a difference but if you have 2.0 available, use it).
4. Go to device manager. Expand "Android Phone", right click "Android Bootloader Interface" and click properties. Click on "Driver" tab. See if the driver provider is "Xiaomi Technology, Inc.", driver date is "11/3/2016", and driver version is "16.0.0.0".
IF it's not, then close the properties window, right click android bootloader interface and click "Update driver". Click "Browse my computer for driver..." then "Let me pick from a list ...". Uncheck "Show compatible hardware", click "Xiaomi Technology, Inc." from the left side, then "Android Bootloader Interface" from the right and click next. After it's installed, check the properties to make sure it says what I mentioned above.
5. Go to unlock tool folder. Go to driver\win10 folder, right click android_winusb.inf and click install. You'll get operation completed successfully message.
6. Go back to unlock folder and run the tool as administrator. Now before clicking agree, click on the settings gear on the top right corner. Make sure MI Usb Driver says "Already installed". This is really important. Otherwise IT WON'T WORK. If it doesn't say that check previous steps and make sure your didn't miss any. Beyond that I have no idea.
7. Now you're good to go. Click agree, sign in and voila, your phone shall be connected, ready to unlock.
Thanks.
Click to expand...
Click to collapse
You are a LIFESAVER... Having spent more than 12 hours searching the internet..... Thanks again.
Hexerus said:
Oh THANK GOD, I finally went past this step. Thank heavens jeez. So here's my short guide that tells what I did to resolve this problem.
Note: I have Mi Unlock tool version 2.3.803.10 (latest as of now). I'm on Windows 10 x64 build 15063.
1. Extract the zipped archive of MI Unlock tool to the root of your system drive, like C:\any_folder. I extracted it to
7. Now you're good to go. Click agree, sign in and voila, your phone shall be connected, ready to unlock.
Thanks.
Click to expand...
Click to collapse
Hey Bro!!!!! I had made an account on XDA just & just to write this THANKFUL comment. Hell Lot of THANKS Buddy!!
Hexerus said:
Oh THANK GOD, I finally went past this step. Thank heavens jeez. So here's my short guide that tells what I did to resolve this problem.
Note: I have Mi Unlock tool version 2.3.803.10 (latest as of now). I'm on Windows 10 x64 build 15063.
1. Extract the zipped archive of MI Unlock tool to the root of your system drive, like C:\any_folder. I extracted it to C:\unlock, so the path of the tool's executable became "C:\unlock\miflash_unlock.exe"
2. Run MiUsbDriver.exe from the folder with as administrator and click "Install". Make sure it says "Driver installed" after that. If it already says that, hit install again just to make sure. Click "Retesting" to see if it remains the same. Close the program after.
3. Put your device into fastboot mode (make sure to turn on USB debugging and OEM unlocking in the developer options), and connect it through USB 2.0 port. (I don't know if 2.0/3.0 makes a difference but if you have 2.0 available, use it).
4. Go to device manager. Expand "Android Phone", right click "Android Bootloader Interface" and click properties. Click on "Driver" tab. See if the driver provider is "Xiaomi Technology, Inc.", driver date is "11/3/2016", and driver version is "16.0.0.0".
IF it's not, then close the properties window, right click android bootloader interface and click "Update driver". Click "Browse my computer for driver..." then "Let me pick from a list ...". Uncheck "Show compatible hardware", click "Xiaomi Technology, Inc." from the left side, then "Android Bootloader Interface" from the right and click next. After it's installed, check the properties to make sure it says what I mentioned above.
5. Go to unlock tool folder. Go to driver\win10 folder, right click android_winusb.inf and click install. You'll get operation completed successfully message.
6. Go back to unlock folder and run the tool as administrator. Now before clicking agree, click on the settings gear on the top right corner. Make sure MI Usb Driver says "Already installed". This is really important. Otherwise IT WON'T WORK. If it doesn't say that check previous steps and make sure your didn't miss any. Beyond that I have no idea.
7. Now you're good to go. Click agree, sign in and voila, your phone shall be connected, ready to unlock.
Thanks.
Click to expand...
Click to collapse
Thank you, you solve my problem I try almost everything and the problem continues, your guide solve my issue with the USB drivers, good work