ive been trying to get fastboot drivers onto my z5c for 2 hours now, device manager with some xiaomi drivers, disable driver updates when restarting my pc, the whole shpeal, but nothing has worked as the damned message "the best drivers are already installed, windows has determined" yada yada yada, i was wondering if anyone could help? anything will be appreciated, any info will be provided if need be.
Try linux
Berni-0815 said:
Try linux
Click to expand...
Click to collapse
Darn
I'm sorry for my short, but honest, comment.
But Windows is notorious for its quirks of allegedly mismatched drivers.
This rarely happens with Linux.
MrTheyes said:
ive been trying to get fastboot drivers onto my z5c for 2 hours now, device manager with some xiaomi drivers, disable driver updates when restarting my pc, the whole shpeal, but nothing has worked as the damned message "the best drivers are already installed, windows has determined" yada yada yada, i was wondering if anyone could help? anything will be appreciated, any info will be provided if need be.
Click to expand...
Click to collapse
Do you still need help installing drivers?
MrTheyes said:
ive been trying to get fastboot drivers onto my z5c for 2 hours now, device manager with some xiaomi drivers, disable driver updates when restarting my pc, the whole shpeal, but nothing has worked as the damned message "the best drivers are already installed, windows has determined" yada yada yada, i was wondering if anyone could help? anything will be appreciated, any info will be provided if need be.
Click to expand...
Click to collapse
My SXZ5C (and SXZ1C) were not listed with 'fastboot devices'. So I installed this https://adb.clockworkmod.com/ and then (more or less) followed a guide :
1) Device manager
2) Right click on device (the android device with the yellow warning signal).
3) 'Update driver'
4) 'Browse my computer for drivers'
5) 'Let me pick from a list [...]'
6) Clicked the only one that appeared (don't remember it's name, because now my SXZ5C is installed as 'Android Composite ADB Interface' and not as whatever it was before I succeeded). Also possible it has nothing to do with the Universal ADB Drivers linked at the beginning, because I already installed a bunch of different stuff I don't remember.)
7) Then I could proceed as planed as my devices were now listed.
That is the guide I used : https://stackoverflow.com/a/35076765
Adb works here under windows 11 with the drivers bundled by microsoft like a charm.
mvikrant97 said:
Do you still need help installing drivers?
Click to expand...
Click to collapse
since i usually use windows 10 for pretty much everything, i do need a sorta walkthrough on how to install the drivers on ubuntu, cause im not really up to date with this terminal stuff
Code:
sudo apt-get install adb fastboot
The package that comes with Ubuntu Mate is broken, adb-pair does not work, how you will get on I don't know, it may be better to use the official adb.
There are instructions for installing adb on Linux here
Using ADB and fastboot | LineageOS Wiki
wiki.lineageos.org
Just extract adb somewhere and add it to your $path
I'm using the adb version that came with Xubuntu since many years now without any problems.
Is this problem solved? A feedback would be nice...
Berni-0815 said:
Is this problem solved? A feedback would be nice...
Click to expand...
Click to collapse
I gave the phone to my friend and he just hasn't been out with it for a bit, but what I do remember is not knowing how to install adb, how to run anything since I was using Ubuntu from Rufus on a usb (not installed) and yeah, a walkthrough or something would hundred percent be appreciated
In the post #10 is a kind of walkthrough...
Berni-0815 said:
In the post #10 is a kind of walkthrough...
Click to expand...
Click to collapse
Ah **** yeah sorry, been a bit since I saw that
(PEBKAC, deleted - sorry)
Related
Sorry for asking this stoopid,noob question,but I never used PC Suite.
So,I just re-installed Windows XP and all is quite smooth. So,since I have a stable Windows OS now,I'm willing to flash the new baseband (finally,huh? ).
Do I only need to install LG PC Suite and all drivers will be installed(For using KDZ/LGMDP),or I need external tools/downloads/etc.? If so anyone kindly post a link here.
Only the drivers should be adequate.
But sorry I forgot the url where I got them.
I didnt use LG PC Suite, coz then I dont need it
PS. I admire your great work Ciaox
FrenchOnly said:
Only the drivers should be adequate.
But sorry I forgot the url where I got them.
I didnt use LG PC Suite, coz then I dont need it
PS. I admire your great work Ciaox
Click to expand...
Click to collapse
Thanks!
I have 2 drivers in my PC right now, I'm using win7 dont know if it works for XP.
But if you want to try I'd glad to share them with you through dropbox.
If it's OK then I'll PM the details
FrenchOnly said:
I have 2 drivers in my PC right now, I'm using win7 dont know if it works for XP.
But if you want to try I'd glad to share them with you through dropbox.
If it's OK then I'll PM the details
Click to expand...
Click to collapse
Hmm... AFAIK win7 drivers are different
Found this http://www.lg.com/uk/support/mc-support/mobile-phone-support.jsp. Can anyone confirm this is working?
Well then...
Here you go..might found what you're looking for here
edit...
Yes I got mine from there
Don't install other devices' drivers and be careful with that goddamn LGMDP... I bricked my phone with that
onlymeipse said:
Don't install other devices' drivers and be careful with that goddamn LGMDP... I bricked my phone with that
Click to expand...
Click to collapse
I'm not installing other devices' drivers
BTW I just noticed that LGMobile update program isn't so stable. Firstly it changes automatically to Korean,then has some issues with Visual C++...
FrenchOnly said:
Well then...
Here you go..might found what you're looking for here
edit...
Yes I got mine from there
Click to expand...
Click to collapse
there (my link)?
Make sure you disable LGE Modem on windows Device Manager, right click on it should do the work.
Don't know about that but seems being plugged in while the LGE Modem is still active could interrupt the debugging process.
CMIIW
edit.
Yes both yours and my link.
Try my link, they are easily listed.
Phone is recognize from LGMobile update tool. Had some (resolved) issues with drivers,but now that tool recognizes the phone,so it's all ok? i wanna be sure
Usually I ran adb command just to make sure
Driver Issues
I am having trouble installing drivers for my P500 on Windows XP using the B2CApp.
It installs 3 of them:
LGUnitedMobileDriver_S4981MAN32AP22_ML_WHQL_Ver_3.2.1.exe
LGSmartPhone_ModemlinkDUNDrive_WHQL_ML_Ver_1.0.exe
LGWindowsMobile_USBDriver_WHQL_ML_Ver_1.0.exe
But even then, my phones not detected on the PC.
Btw, I must mention that I am stuck on the fastboot screen, while trying to do a NANDroid backup, after ROM Manager screwed up with my Custom Recovery installation.
Any idea if the above 3 are enough for me to proceed with the below link, or is there another LG fastboot driver that I might be missing? :
http://forum.xda-developers.com/showthread.php?t=1088046
When I connect my phone and hit the first command on cmd prompt:
Code:
fastboot erase recovery
I get the following:
Code:
< waiting for device >
UPDATE:
I have fixed the issue. Got the drivers mentioned in this thread:
Anyone else stuck with Windows XP not recognizing the device even after the B2CApp installation, try these drivers:
http://android.modaco.com/topic/324744-waiting-for-devicefastboot/#
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
The last USB device you connected to this computer malfunctioned, and Windows does not recognize it.
Click to expand...
Click to collapse
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
This device cannot start. (Code 10)
A request for the USB BOS descriptor failed.
Click to expand...
Click to collapse
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
[TSON] said:
I've looked all around for this - I got ADB drivers to install just fine so that's no issue. It's just... for some strange reason my phone works completely fine while plugged in, but the minute you go into fastboot my computer rejects it. I get a pop up saying:
So, of course, I do a little digging and find where my DNA in Fastboot should show up in device manager.. and it says:
Should I reinstall HTC Sync or something (I uninstalled it)? I'm lost. Can't think of anything to do. Shuffling around the drivers that come with the SDK doesn't help any - and my Windows 7 machine didn't have any of these issues. Too bad it's dead now
Click to expand...
Click to collapse
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
inexplicability said:
Alright, so you're going to want to have HTCSync installed, then after thats done, go to your device manager and select your device (not sure what it will be under, but it will have a (!) sign next to it). Download these drivers and use the "have disk" thing when looking for drivers in device manager. Make sure your DNA isn't plugged into a USB3 port, and then fastboot should work for you.
Click to expand...
Click to collapse
Ran into this yesterday. My computer ONLY has USB3 so I was unable to get it to work. Tried on a Win7x64 machine and did it first time no problem. Sigh...
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I don't have any tips for you, other than to say that I've had fastboot work with my DNA on 2 different win 8 64 machines.
I *think* I got my drivers from HTCSync, and then uninstalled HTCSync, but not the drivers afterwards.
I did have problems with fastboot and adb when I was playing around with the CM10 build that is available here. Maybe try switching your rom and kernel?
[TSON] said:
Whoops, thought I posted this already... But yeah, that didn't fix the problem. Same two errors no matter what drivers I use.
Click to expand...
Click to collapse
I ran into the same exact issue on my win8 64-bit machine. luckily i have a couple usb2 ports and they work just fine. i wonder if using a usb hub that is compatible with usb2 or lower would work.
Did you try disabling driver signing in Windows 8 pretty sure thats the problem.
Here
Yeah you have to do that in order to install the universal driver or any other unsigned drivers - but once the drivers are installed you're good to go. No matter which drivers I pick I have this problem, I've tried probably 7 different ones.
Works fine on my Vista laptop but that things about to creak... Just used it to S-OFF and it took over an hour to turn on :crying:
EDIT: And for what it's worth, doesn't matter if it's a USB 3.0 or 2.0 - same error. Doesn't work on stock or on Cubed/Viper (though this is fastboot so kernel/ROM shouldn't have anything to do with 'em).
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
_kevn_ said:
I was able to get mine working with the combo of
1. uninstalling any HTC sync or sync manager and the HTC BMP USB Driver. Basically anything HTC.
2. Install HTC sync. Not sync manager. Go to the HTC support page and you'll see both listed. If you go to the specific phone support page it might not be there. (One S doesn't have the sync program, just sync manager iirc.)
3. Download PDAnet. When installing, It'll give a warning that you already have drivers installed and ask if you want to fix them or leave as is. I chose it to fix and it went though its process and I had working drivers after that.
I think this was already suggested before. I going back and giving thanks wherever due after this post. (On the mobile app right now)
Other easy way if you're using a One S is to download Hasoon2000's All-On-One Toolkit. He's updated the drivers for windows 8. I haven't tried it yet as mine are working so haven't had the need. I would assume his tool for any of the other phones he supports would have the updated drivers too.
Click to expand...
Click to collapse
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
_kevn_ said:
Hey there! Sorry my fix didn't work for you.
My question is, are you running windows 8 or 8.1? The reason I ask is because the 8.1 update has broken fastboot apparently. I don't remember the last time I tried on my computer to see if fastboot still works or not since I updated to 8.1.
If you are running 8.1 windows then the guide at droid-now.com seems to have worked for many people. Go to that site and search fastboot fix windows 8.1 or you could just Google that too I guess. I would paste the link right now but my phone is being stupid and not letting me paste it ATM. :-|
If that doesn't work then you may be able get what you need done by dual booting into Ubuntu if you feel comfortable doing so. You could easily make a bootable flash drive that you could boot into just for an emergency. I just used one for about 4 days while fixing my computer after I accidentally erased the partition tables of my hard drive, trying to make a permanent installation of Ubuntu. Got it fixed BTW! ats self on back:
Keep us posted if you get it fixed or have any more questions! I hope I've been at least a little helpful. I'll try to help any more I can if possible!
Good luck!
Kevin
transmitted via skynet
Click to expand...
Click to collapse
I am running Windows 8.1, however it looks like the fix only applies to Intel motherboards connecting through USB 3.0 ports. I do have USB 3.0 ports, but my motherboard is AMD and my USB3 controller reads "VIA USB 3.0 eXtensible Host Controller - 0100 (Microsoft)." I'm not sure that the fix applies to me, unfortunately. Also, I am not connecting my phone to my PC using the USB3.0 ports.
I tried downloading the USB 3.0 Drivers for Windows 8 64-bit on the manufacturer's website for my motherboard (http://www.gigabyte.us/products/product-page.aspx?pid=4305), but when I try to update my drivers to the ones I got from the website it says that the Microsoft provided ones are the most recent/ up to date drivers.
Daniuhl said:
Specs: Windows 8 64-bit. Clean and restored HTC EVO 3D. HBOOT 1.58.0000.
I have tried almost everything, but I can't get my phone recognized in fastboot mode.
I tried what was listed here: http://forum.xda-developers.com/showthread.php?p=39218156#post39218156
And the phone is recognized fine when in regular mode. Though, whenever I reboot the phone into the Bootloader using adb, it restarts into the fastboot, but it doesn't change to "Fastboot USB" and shortly after I get a "USB Device Not Recognized" on my PC and it saying something about it malfunctioning. So I get stuck on "Waiting for device" when trying out this command "fastboot oem get_identifier_token."
Any ideas? I'm trying to unlock the bootloader and root so that I can install custom ROMs and kernels.
Click to expand...
Click to collapse
Be Advised, there is perhaps a way , you wil find in the link below, but be sure to use the right intel driver And only if you hae an intel chipset for usb3 , please read the comments and my bad experience :
Under win8.1/X64 that if you have(like me) an Intel 8 /c220 (or with a 4th generation like intel I7 4770k) you may encounter a big mess , and perhaps you''l have to do a clean install of win 8.1 : all the usb2 DEVICES were disconnected after the first iusb3xhc.inf driver install !! So no more usb/Bluetooth keyboard+mouse , fortunately i had an old ps2 keyboard and i was able to delete only with "tab/alt Tab/ctrl tab" keys the
"intel usb3 extensible " line in device manager, and as soon as i done a refresh (ALT+A) in device manager the previous driver(Microsoft) was reinstalled by win 8.1 andall the usb2 devices connected (mouse/keyb/hub etc)
http://plugable.com/2012/12/01/windo...#comment-19066
see there there's in the last comments at the bottom , Andrew(tks to him!)a link + modified drivers for intel8/c220)
and for me it worked mouse/keyB were functional during all the process
next step check the fastboot adb is working now
Here you go... http://forum.xda-developers.com/showthread.php?t=2061435
A later post I made (I havent updated the OP, shame on me...) is a link to some universal drivers from CWM that works fantastic! - http://forum.xda-developers.com/showthread.php?p=40108463#post40108463
Before trying this I would goto your device manager and right click on the currently installed drivers and uninstall them before installing the drivers again.
Hope that helps. I am using the link found in that second link and fastboot and adb works perfect. Also, while you can boot into fastboot, stock 1.58 will not let you run a lot of fastboot commands and will need to flash a different hboot.
Hi. First of all I want to excuse me that I' m asking a common thing several times threated in other posts.
I'm working now 2 days on getting another rom on my lemax 2.
I have installed the driver for the phone on my windows 7. system manager shows a propper installation. ADB driver's have been installed. The phone is in developper mode and oem and usb debugging is turned on. I switched to MTP and to PTP to make my device visible for ADB. But when I'm trying to see if my computer shows the mobile phone in CMD with the following command "adb devices" there will never be something listed! I tried already a lot... Uninstalling drvers for ADB, tried different drivers... And so on... Does anybody have an idea to help me??
Same problem here. Phone doesn't show, ADB can't connect. I am starting to get frustrated.
Most likely a problem with the usb driver, did you try another phone? I had the same problems and ended up doining it under linux afther a couple of hours messing in win10.
http://askubuntu.com/questions/659880/ubuntu-15-04-adb-fastboot-impossible-to-install
DeScheep
MOB* said:
Most likely a problem with the usb driver, did you try another phone? I had the same problems and ended up doining it under linux afther a couple of hours messing in win10.
http://askubuntu.com/questions/659880/ubuntu-15-04-adb-fastboot-impossible-to-install
DeScheep
Click to expand...
Click to collapse
Linux definitely is the better choice.
The fastboot drivers are different from the ADB drivers, and in Windows 10 you might have to switch the driver after fastbooting the phone.
It's really really silly and took me hours to find out.
You can change them in device manager, find the USB device there and update its driver. You don't need one from the web, just take the fastboot one from the list that Windows offers.
Sörnäinen said:
Linux definitely is the better choice.
The fastboot drivers are different from the ADB drivers, and in Windows 10 you might have to switch the driver after fastbooting the phone.
It's really really silly and took me hours to find out.
You can change them in device manager, find the USB device there and update its driver. You don't need one from the web, just take the fastboot one from the list that Windows offers.
Click to expand...
Click to collapse
I have no second android phone to test. But I tried already on OS Win 7 & 10 with different drivers on Win 7 as well. On win 10 the driver was already given by Windows, no need to install. I think that the problem has something to do with the phone, but I can't find the problem. It must be something with authorisation, that Win Os will recognize the Leeco correctly to have access.
I finally found a good working driver for WIN 10. I found it from a Chinese chatting group, so use it at your own risk.
Below is the share link.
https://drive.google.com/file/d/0BxNNPNS50QQiUk50YTliT2p5Mmc/view?usp=sharing
You will need to boot your phone into bootloader, connect to computer, manually switch the diver via 'Browse my computer for driver software" -> 'Let me pick fromm a list of device drivers on my computer"-> "Have Disk".
Hi all,
After reinstalling Windows7 32-bit on my laptop, I ran into the same issue as you guys here. What I did was to install pdanet and the adb interface worked. However, I could not get into the QDLoader 9008 and also Diagnostic Driver was not working, simply the drivers could not get installed no matter what I tried. I searched quite a lot of time how to get make it work and looks like there was a zip "QDLoader HS-USB Driver". You can google it and it has 32-bit and 64-bit installations. I am not very sure if I had to install pdanet but that was the first step to make it work, at least to have adb.
I'm sure that you guys found the answer already, but I wanted to help others as well if they run into the same issue.
valy_cta said:
Hi all,
After reinstalling Windows7 32-bit on my laptop, I ran into the same issue as you guys here. What I did was to install pdanet and the adb interface worked. However, I could not get into the QDLoader 9008 and also Diagnostic Driver was not working, simply the drivers could not get installed no matter what I tried. I searched quite a lot of time how to get make it work and looks like there was a zip "QDLoader HS-USB Driver". You can google it and it has 32-bit and 64-bit installations. I am not very sure if I had to install pdanet but that was the first step to make it work, at least to have adb.
I'm sure that you guys found the answer already, but I wanted to help others as well if they run into the same issue.
Click to expand...
Click to collapse
Thanks a lot for sharing it !!! This helped me A LOT !! :fingers-crossed: :fingers-crossed: :fingers-crossed:
I have the same problem. Tried different drivers, two computers, win10 and win7. Nothing helps...
midirt said:
I have the same problem. Tried different drivers, two computers, win10 and win7. Nothing helps...
Click to expand...
Click to collapse
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
is there any solution for this problem........my device le eco letv 2s is not listed in the adb devices.....can anyone help me....
Dhatchina said:
is there any solution for this problem........my device le eco letv 2s is not listed in the adb devices.....can anyone help me....
Click to expand...
Click to collapse
if you're sure it's not a driver issue you can try the following (solved the problem for me):
on your windows machine navigate to "c:\users\<insert your user name here>\.android" and delete the file "adbkey".
either jump directly to the folder or turn on hidden/os files in explorer and navigate there.
now plug in your phone, the rsa-key dialog should pop up.
if not, that wasn't your problem.
btw. i'm using "universal adb installer".
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
It helpded me a lot. Thanx.
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
Great, man.!. It works for me
THIS Method Works For LeEco Le Max2
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
This Method Works Perfectly.... After Enabling the AT port.. the drivers begin installing immediately. Have Patience. They will all install.
LeEco le2 is not showing up under adb devices list... tried damn lot of drivers ...What do I do??
You should post a Screenshot of your devicemanager becsuse that information is not enough.
Gesendet von meinem Le X820 mit Tapatalk
Install ADB Driver installer 2.0
dhankhar13 said:
LeEco le2 is not showing up under adb devices list... tried damn lot of drivers ...What do I do??
Click to expand...
Click to collapse
adbdriver.com/downloads/
Use this above link
1 ) Download adb driver installer software zip file
2 ) Extract the zip file
3 ) Install & Run a adb driver installer.exe file
my le2 doesn't show up in fastboot mode, but shows up once booted into system. Any idea?
Thanks!
GC-82 said:
Have you tried dialing *#*#76937#*#* and enable AT port, this worked for me
Click to expand...
Click to collapse
This worked for me too!!!:good::good::good:
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