I have had the Mi 11 since today, I wanted to unlock the boot loader, but my PC doesn't recognize it.
looked for adb drivers and downloaded them, did not work.
I turned on USB debugging.
can someone give me a tip or with which driver it would work?
Zimty86 said:
I have had the Mi 11 since today, I wanted to unlock the boot loader, but my PC doesn't recognize it.
looked for adb drivers and downloaded them, did not work.
I turned on USB debugging.
can someone give me a tip or with which driver it would work?
Click to expand...
Click to collapse
I had the same problem after sending a new device in exchange for my defective one. It was not recognized at all on the USB port. In Fastboot mode only in sideload mode. I just did a factory reset. The device was then displayed as unauthorized in ADB mode, but Fastboot mode is sufficient to unlock the bootloader It was then displayed correctly there. However, the waiting time has increased to over 500 hours. The first device lasted 260 hours. No matter. Now it's in the drawer until August.
Related
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
cjsill9473 said:
I found out this morning that my phone had cut off during the night. When I tried to turn the phone back up it just stayed at the loading screen and does not go any further than that. I can get into Fastboot/recovery but not sure what is going on. Phone is locked as well.
I am running on Developer preview 5 and I assuming it has something to do with this. I have read up on others having issues and talk about sideloading the OTA that has resolved the issue but my computer does not even detect the device, so adb does not see the device. Feel like if I can just get my computer to detect my phone I'll be in business.
Really need some help on this one as it is starting to look like I am going to have a nice paper weight the rate its going. Thank you in advance.
Click to expand...
Click to collapse
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
ktmom said:
If I understand correctly, you can get to fastboot mode. If you then plug in the usb cable, and type fastboot devices, does the computer recognize it?
Have you ever connected to the phone using your computer and either adb or fastboot? In other words, is there a high level of confidence that the drivers are setup on your computer?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
I've had experience with using adb/fastboot on my moto x 2014 but this is the first time doing this on my nexus and I am pretty sure I had never hooked up my nexus to this computer before this issue happened. So I wouldn't be surprised if it is a driver issue but I have downloaded Android sdk and gone into sdk manager to have it install google drivers. I just now now played around with Nexus Root toolkit to assist in installing drivers with the same results. I had used the tool to uninstall any drivers that could have impacted this and reinstalled with no luck.
Click to expand...
Click to collapse
Do you have an otg cable? Does that work?
I do but I don't have one on me currently. I am currently at work but will be home in about 2 hours.
ktmom said:
Do you have an otg cable? Does that work?
Click to expand...
Click to collapse
cjsill9473 said:
That is correct, I am able to get into fastboot mode, the phone will detect a USB cable "will say transfer mode: USB connected" but when I am in command prompt on my computer and type in "adb devices" it finds nothing.
Click to expand...
Click to collapse
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
You are correct, device does show up when type in fastboot devices. Guess that is what I get when trying to do this while I am at work and haven't messed with this type of stuff in months. I really appreciate the fast response on this and my derp moment. Now to try and side load the OTA to see if I can bring my phone back to life. Looks like I just need to go into custom recovery and select "Apply Update from ADB" and hopefully I'll be in business.
jj14 said:
When you are in fastboot mode, and connect to your computer, you should run "fastboot devices", instead of "adb devices".
Click to expand...
Click to collapse
Well at this point I was able to side load the OTA DP5 build and its doing the same thing. Trying a factory reset now to see if that will make a difference but if not looks like I am going to have to go out and get me a new phone till I can get this one fixed or RMA'ed. Just stuck at the loading animation.
Edit: Factory restore finally brought it back to life. Thank you again for the quick help and assistance on this!
Hello!
I am trying to root my phone, which requires and unlocked bootloader.
Here are the steps i have completed:
1. Got the unlock code.
2. Installed adb and fastboot drivers.
3. Installed HiSuite
4. Connected the phone to my desktop (windows 10).
Here i have to mention that the pc recognises my phone, and it is listed under devices. USB debugging and OEM unlock are enabled.
5. I opened cmd in the folder where abd is installed. Checked that abd devices finds my phone (which it does).
Here is where the problem comes in. After booting phone into fastboot (using adb reboot bootloader), i tried to find my phone using the command fastboot devices.
This doesn't find the phone. If i try to unlock anyways, it gets stuck on waiting for devices. I tried the same steps on a laptop (also running windows 10) and the problem stays the same.
Help is appreciated.
EDIT: solved the problem by using a windows 8 installed laptop.
Uninstall HiSuite, it may interfere with the phone's connection. It is not used when unlocking/root.
monoxian said:
Uninstall HiSuite, it may interfere with the phone's connection. It is not used when unlocking/root.
Click to expand...
Click to collapse
Thank you for your reply, but this didn't work.
To add a detail, the reason i installed HiSuite was, because in fastboot mode it says:
"Please install HiSuite and connect your phone to your computer with an USB cable.
Nastmi said:
Thank you for your reply, but this didn't work.
To add a detail, the reason i installed HiSuite was, because in fastboot mode it says:
"Please install HiSuite and connect your phone to your computer with an USB cable.
Click to expand...
Click to collapse
You can try using this tool to unlock bootloader:
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
I personally used this and worked flawlessly, make sure to get the latest version of it if you do.
If you are in fastboot&rescure mode, try the command "fastboot devices" and see if the device is detected, if not try unplugging and replugging phone
monoxian said:
You can try using this tool to unlock bootloader:
http://forum.xda-developers.com/p9/development/tool-srk-tool-huawei-bootloader-root-t3374068
I personally used this and worked flawlessly, make sure to get the latest version of it if you do.
If you are in fastboot&rescure mode, try the command "fastboot devices" and see if the device is detected, if not try unplugging and replugging phone
Click to expand...
Click to collapse
Will try the tool when i get home from school, but fastboot devices doesn't detect my device.
EDIT: The tool didn't work. It is stuck on waiting for device.
Fixed the problem by unlocking on another laptop (has windows 8).
Nastmi said:
Fixed the problem by unlocking on another laptop (has windows 8).
Click to expand...
Click to collapse
Glad to hear that you got it working, I had windows 10 and that worked on mine =\
Sent from my iPhone using Tapatalk
Hello all, I have a strange problem on my xiaomi 8 phone.
Every thing works fine, the phone is BL unlocked, with global rom installed and can be OTA-updated.
Now I want to re-lock the Bl (because of google pay), so I booted to fastboot and the strange thing happens. When I connect to the usb port of my win10 pc, nothing happens, the device manager also show no new device or unknown device. And I als connected to my ubuntu server, dmesg show nothing, and lsusb also show nothing new.
So the issue is, in fastboot mode, my phone seems not be responsed the usb connection. This is boring, because I also accidently replaced the twrp with stock recovery, now I can do nothing on my phone without the fastboot connection.
Any one has an idea or simillar issue and have a solution for it? Thanks in advance.
Zhifu_Yu said:
Hello all, I have a strange problem on my xiaomi 8 phone.
Every thing works fine, the phone is BL unlocked, with global rom installed and can be OTA-updated.
Now I want to re-lock the Bl (because of google pay), so I booted to fastboot and the strange thing happens. When I connect to the usb port of my win10 pc, nothing happens, the device manager also show no new device or unknown device. And I als connected to my ubuntu server, dmesg show nothing, and lsusb also show nothing new.
So the issue is, in fastboot mode, my phone seems not be responsed the usb connection. This is boring, because I also accidently replaced the twrp with stock recovery, now I can do nothing on my phone without the fastboot connection.
Any one has an idea or simillar issue and have a solution for it? Thanks in advance.
Click to expand...
Click to collapse
It sounds like you accidentally relocked the bootloader.
If so you will need to repair the phone in EDL mode by using QPST. There are plenty of how to guides available. You can buy a EDL cable from Amazon
https://www.amazon.com/Baosity-Flas...ds=edl+cable&qid=1552775105&s=gateway&sr=8-11
Since I flashed my Mi 11 ultra from CN to EEA version Rom, it is not recognised by Windows 10 laptop when in fastboot mode.
Its the same Win 10 laptop which I used to flash the phone, so all the drivers are still installed.
You have to turn USB Debugging on again in developer settings
Done that. I've done everything. It just doesn't get recognised. No little chime when I plug it in, nothing. It works in normal mode, but not fastboot.
message me privately and i can help you through zoom/teamviewer
saisannihith said:
message me privately and i can help you through zoom/teamviewer
Click to expand...
Click to collapse
there is a hardware fault on my phone. usb debugging is enabled. when in plug in phone in fastboot mode, it doesn't even show in device manager. nothing. this screenshot is taken with the phone plugged in in fastboot mode. As you can see, it doesn't show at all.
spikemann007 said:
there is a hardware fault on my phone. usb debugging is enabled. when in plug in phone in fastboot mode, it doesn't even show in device manager. nothing. this screenshot is taken with the phone plugged in in fastboot mode. As you can see, it doesn't show at all.
Click to expand...
Click to collapse
I cant tell you anything until i see it.
Weird, I attached a screenshot before. Here I try again.
put cellphone in fastboot download and install file here's download link https://ufile.io/1xc7dudc
thephonetechdoc said:
put cellphone in fastboot download and install file here's download link https://ufile.io/1xc7dudc
Click to expand...
Click to collapse
I already installed that same file before. No difference. doesn't even show in devive manager. I give up.
Bro not like this. Iam asking if i can connect remotely to your PC to diagnose the drivers.
Unusual xiaomi drivers and adb devices and reinstall
Have a look and try out the method mentioned in the video. Did the trick for me
I did all of it. I don't even get that little chime that lets you know when you plug the phone in. Silence.
It works fine in normal mode.
Hi @spikemann007 !
I had the same issue.
Root cause was (for me) the USB cable. Have you already tried a alternative?
best regards!
I have a very odd issue with fastboot. The computer (windows 10) detects the device the first time I use fastboot and then will not show up in device manager on other attempts.
I have the EU variant running Oxygen OS 11.0.11.11.EB12BA with Magisk installed.
I have installed the Oneplus ADB drivers and this works flawlessly. Booting the first time into fastboot mode the device showed in the device manager, I was able to install the fastboot driver and fastboot devices showed my phone.
Trying a second or third time nothing shows in the device manager. The device is completely absent from USBDeview.exe. It behaves as if it's not even plugged in.
I was able to reproduce this on another computer I have.
Is anyone else facing this issue and/or knows what might be going wrong?
EDIT: If it helps anyone else having this issue I'm able to get the "OnePlus Android Bootloader Interface" to show up if I plug the phone into a USB HUB, then plug the HUB into the computer. Rebooting the phone again into fastboot will not show up but if I unplug and replug the hub in the driver will activate again.
VoltaGe86 said:
I have a very odd issue with fastboot. The computer (windows 10) detects the device the first time I use fastboot and then will not show up in device manager on other attempts.
I have the EU variant running Oxygen OS 11.0.11.11.EB12BA with Magisk installed.
I have installed the Oneplus ADB drivers and this works flawlessly. Booting the first time into fastboot mode the device showed in the device manager, I was able to install the fastboot driver and fastboot devices showed my phone.
Trying a second or third time nothing shows in the device manager. The device is completely absent from USBDeview.exe. It behaves as if it's not even plugged in.
I was able to reproduce this on another computer I have.
Is anyone else facing this issue and/or knows what might be going wrong?
EDIT: If it helps anyone else having this issue I'm able to get the "OnePlus Android Bootloader Interface" to show up if I plug the phone into a USB HUB, then plug the HUB into the computer. Rebooting the phone again into fastboot will not show up but if I unplug and replug the hub in the driver will activate again.
Click to expand...
Click to collapse
You don't need to install any fastboot drivers, if you're on windows; just install one plus driver (without driver signature/in test mode) and stay on them.
Sony make.belive said:
You don't need to install any fastboot drivers, if you're on windows; just install one plus driver (without driver signature/in test mode) and stay on them.
Click to expand...
Click to collapse
Sorry I think I've explained incorrectly. Those are the drivers I've installed, the problem is it only works once.
The second time I reboot the phone into Fastboot mode it doesn't display in device manager. Looking at USBDeview absolutely nothing shows up. Changing USB ports and the cable have no effect, however if I plug the phone into an old USB 2 hub I have then plug that into the computer it will display again in the device manager.