My Redmi Note 8 gets detected just fine in ADB but when it goes to fastboot, it just shows that "There is no driver installed" for the Android device. I already installed the ADB and fastboot drivers from google and they show up in my device manager when I show the hidden devices. When I click on the drivers (Android Composite ADB Interface), they say that the hardware isn't currently connected to the computer, when my pc detects that it's indeed connected, but somehow the driver isn't detecting it. When I try to update the android driver to the fastboot drivers that I've found, it says that it installs it successfully but then when clicking on the device in device manager, it still shows that no driver is installed. How do I fix this?
Try downloading this your driver from here.
Thank you for the reply, I have installed both drivers but when plugging in my phone when it is in fastboot mode, it still says "No drivers are installed for this device" it's like my pc detects the phone and yet my drivers don't.
Oblivionchain said:
Thank you for the reply, I have installed both drivers but when plugging in my phone when it is in fastboot mode, it still says "No drivers are installed for this device" it's like my pc detects the phone and yet my drivers don't.
Click to expand...
Click to collapse
Then maybe it's the cable, try changing the cable.
Is your device in download mode or fastboot mode?
Oblivionchain said:
Thank you for the reply, I have installed both drivers but when plugging in my phone when it is in fastboot mode, it still says "No drivers are installed for this device" it's like my pc detects the phone and yet my drivers don't.
Click to expand...
Click to collapse
Windows PC? First reboot your PC.
Download Xiaomi Unlock tool:
Direct download link (English Version 5.5.224.55)
Use the direct download link.
Extract all files into short-named folder. Go into folder and double click on MiUsbDriver.exe when your phone is under fastboot mode and connected to PC.
{
"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"
}
If you are using desktop, use the USB port on the motherboard directly.
If after this your device is detected, then reboot PC again.
Related
Hello buddies,
I am having a sort of problem with my M8.
Just to make it clear from the beginning I'm pretty much a noob in this.
So after I got my phone debranded byba rooting method and had twrp installed I wanted to flash the stock recovery in my device so I can get OTA updates.
The momental state of the device: stock firmware 1.54.401.10, S-On, tempered, unlocked bootloader.
At first everything was going fine, but when I typed the command to erase cache before flashing the recovery.img, cmd in my pc crashed.
Now when I connect my device, in cmd I can see it only when I check usb debugging, when it's unchecked there isn't any device on the list unauthorised like it should be.
When I enter the command to reboot into fastboot, my device just reboots and when I get into fastboot manually cmd doesnt recognize it.
Just to make clear I don't think it's the drivers fault, I installed/uninstalled them several times and tried it in another pc and the same thing happens.
I messed up again something with the drivers, now I get two devices with the same name in fastboot
{
"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"
}
When i try to reboot now into fastboot it says: error: more than one device andemulator
Sent from my HTC One_M8
I got it working
Sent from my HTC One_M8
leart369 said:
I got it working
Click to expand...
Click to collapse
How?
redpoint73 said:
How?
Click to expand...
Click to collapse
Firstly I installed a tiny program for drivers, where i uninstalled all the drivers which had been in relation with the phone(i can't remember the program name, i will post it later when i'm at home) then i revoked the usb debugging and connected my phone with usb debug off and let the pc install the drivers by itself. After that i checked debugging and fastboot recognized it with adb devices, i rebooted into bootloader and typed fastboot devices(it showed my device).
Flashed the recovery and done
Sent from my HTC One_M8
leart369 said:
Firstly I installed a tiny program for drivers, where i uninstalled all the drivers which had been in relation with the phone
Click to expand...
Click to collapse
Like some kind of PC clean-up program?
I knew it had to be a driver issue, but the fastboot response you were getting was odd or at least new to me. So glad you sorted it out. Nice work!
redpoint73 said:
Like some kind of PC clean-up program?
I knew it had to be a driver issue, but the fastboot response you were getting was odd or at least new to me. So glad you sorted it out. Nice work!
Click to expand...
Click to collapse
More like a driver manager, i'll post the name when i get on my laptop
The programm is called usbdeview, sorted my drivers by date and uninstalled all drivers that have been installed these days. And then connected the phone again wihout installing anything just let windows do his job
Sent from my HTC One_M8
Hello
i have a problem. When i connect my phone to my computer with Fastboot. My phone says "FASTBOOT USB" and 15 sec later I get this error and my phone says "FASTBOOT"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
My phone is on Fastboot mode. Adb and Fastboot driver are installed. Please HELP me!
evildog1 said:
Hello
i have a problem. When i connect my phone to my computer with Fastboot. My phone says "FASTBOOT USB" and 15 sec later I get this error and my phone says "FASTBOOT"
My phone is on Fastboot mode. Adb and Fastboot driver are installed. Please HELP me!
Click to expand...
Click to collapse
Windows 8/8.1 has had issues with using devices in Fastboot mode. Luckily, a fix is already available. Follow the instructions in the thread linked below and make sure you have the drivers installed and HTC sync removed
http://forum.xda-developers.com/htc-wildfire-s/general/driver-finally-how-to-fastboot-to-t2857536
Click to expand...
Click to collapse
This method does not work
evildog1 said:
Hello
i have a problem. When i connect my phone to my computer with Fastboot. My phone says "FASTBOOT USB" and 15 sec later I get this error and my phone says "FASTBOOT"
My phone is on Fastboot mode. Adb and Fastboot driver are installed. Please HELP me!
Click to expand...
Click to collapse
Here is your solution: http://blogs.msdn.com/b/usbcoreblog...8-0-but-fail-on-windows-8-1-with-code-43.aspx
evildog1 said:
This method does not work
Click to expand...
Click to collapse
Have you installed the drivers for the phone? Because the only reason for it to not work is the unavailability of the drivers
csoulr666 said:
Have you installed the drivers for the phone? Because the only reason for it to not work is the unavailability of the drivers
Click to expand...
Click to collapse
I have installed the HTC drivers and enter FASTBOOT again but the word "FASTBOOT USB" disappear without any errors on Windows 8.
evildog1 said:
I have installed the HTC drivers and enter FASTBOOT again but the word "FASTBOOT USB" disappear without any errors on Windows 8.
Click to expand...
Click to collapse
And what about HTC sync, is it installed as well? Also try to use a newer version of fastboot just in case(if you haven't updated it in some time)
csoulr666 said:
And what about HTC sync, is it installed as well? Also try to use a newer version of fastboot just in case(if you haven't updated it in some time)
Click to expand...
Click to collapse
@evildog1: If you have usb connection in recovery mode your drivers are ok. Please read my previous link on this page for solving the problem in windows 8.1.
Marcel1962 said:
@evildog1: If you have usb connection in recovery mode your drivers are ok. Please read my previous link on this page for solving the problem in windows 8.1.
Click to expand...
Click to collapse
i successfully flashed custom recovery with my old computer running Windows 7.
when i connect my device to my computer running Windows 7 without any HTC drivers, the word "USB" did not disappear from Fastboot and it always says "FASTBOOT USB". i installed HTC Drivers and run Fastboot flash and it worked perfectly.
On Windows 8. without any HTC Drivers, it tells me that there was something wrong with the USB. After i installed HTC Drivers and run Fastboot again, the word "USB" disappear from Fastboot screen without any errors.
EDIT: Solved
Before you ask, yes, I do have USB debugging on, and I do have ADB and fastboot drivers installed. I'm running Windows 10.
The ADB shell is working well while the watch is in "normal" system mode, but after I boot it into fastboot with the "adb reboot bootloader" command, it's no longer recognized by my PC. "adb devices" brings up an empty list, and entering any command at all gets ADB stuck at < waiting for any device >.
What do?
Instead of adb use
Code:
fastboot devices -l
ranf said:
Instead of adb use
Code:
fastboot devices -l
Click to expand...
Click to collapse
I mean I did that, sorry for being unclear.
Anyway, it was a Windows 10 driver issue. Apparently you have to manually specify via Device Manager that the watch uses Android ADB while it's in fastboot mode.
[NUMINIT] said:
I mean I did that, sorry for being unclear.
Anyway, it was a Windows 10 driver issue. Apparently you have to manually specify via Device Manager that the watch uses Android ADB while it's in fastboot mode.
Click to expand...
Click to collapse
Hi,
I have the same problem, how did you solve it in WIN 10 ?
Ferdinand
fmcheetah said:
Hi,
I have the same problem, how did you solve it in WIN 10 ?
Ferdinand
Click to expand...
Click to collapse
If I recall correctly, the watch showed up as an unknown device while plugged in in fastboot mode. It's just a matter of identifying it (unplug & plug in and see which one reacts) and manually pick "ADB device" or some such from the manual update settings.
I am having a problem with this also. After having many android devices and other OS's......this is the first time I have been unable to get the correct drivers to be able to see my watch file system on my Win7 PC....and Win10 laptop.
Here is what I get when trying to update the driver with ADB debugging enabled in on watch as well..
{
"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"
}
Here are my choices available:
I get stuck selecting the right choices and all lead to the same "code 10" cant find/install driver.
RR215 said:
I am having a problem with this also. After having many android devices and other OS's......this is the first time I have been unable to get the correct drivers to be able to see my watch file system on my Win7 PC....and Win10 laptop.
Here is what I get when trying to update the driver with ADB debugging enabled in on watch as well..
Here are my choices available:
I get stuck selecting the right choices and all lead to the same "code 10" cant find/install driver.
Click to expand...
Click to collapse
This is probably a dumb question, but it never hurts to make sure: you do have the drivers installed, right?
That is my problem....I dont see it in the available list. I have several other android devices in use with no problems, also have the Sony PC Companion 2.1 on my PC and use that.
I am actually not in OP's situation actually now that I re-read the thread over. This is in normal boot mode. How do i get the correct driver for the watch from here.
Thanks for your help.
pls delete this thread, wiping my pc again and make an format.
Install windows fresh and hoping the best.
KornY10 said:
pls delete this thread, wiping my pc again and make an format.
Install windows fresh and hoping the best.
Click to expand...
Click to collapse
Did it work?
Didnt done it. Maybe today or tomorrow, dont know -.- How can i complete deinstall USB Drivers?
Installed now:
Android SDK
ADB install 1.4.3
Oneplus3 Drivers
Device is detected as: Kedracom?! And then - Kedracom Device, after clicking on "driver update" i can change it to "Android ADB Device" then ADB Sideload works.
When i boot then to Fastboot the Device is detected as "Android Bootloader Device" or so...then i cant install nothing, and i cant connect to the Phone.
Im Using the USB ports from behind, dont use the front one.
Any tip? What can i do? screws me up -.-
{
"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"
}
KornY10 said:
Didnt done it. Maybe today or tomorrow, dont know -.- How can i complete deinstall USB Drivers?
Installed now:
Android SDK
ADB install 1.4.3
Oneplus3 Drivers
Device is detected as: Kedracom?! And then - Kedracom Device, after clicking on "driver update" i can change it to "Android ADB Device" then ADB Sideload works.
When i boot then to Fastboot the Device is detected as "Android Bootloader Device" or so...then i cant install nothing, and i cant connect to the Phone.
Im Using the USB ports from behind, dont use the front one.
Any tip? What can i do? screws me up -.-
Click to expand...
Click to collapse
I'm sitting in the same boat xD
ADB is working fine phone Will be recognized. But in Fastboot Mode nothing.....
On my PC is Windows 10 installed and on my phone OOS 3.2.7
Same here, really strange, or a rly ****ing Noob fail and I don't get it. If someone else could read and help ...would be good
So, dont know...read so many things, all is fine and adb connected but wtf is fastboot not work -.-
are u trying some thing?
me too no Fastboot at all
OP3 : 3.2.7
It maybe bcz the last update, or that old OP3 tool
Hello again
Everything is working good
it seems to be a problem with adb Windows 10 IDK
, it is better to do it on Windows 7
Follow this :
http://forum.xda-developers.com/oneplus-3/how-to/oneplus-3-how-to-unlock-bootloader-t3398733
Ok, so i could install win7 as second OS? Have enough Harddisks, so its np.
Think i try this, PC is fresh installed, so if its not good or buggy i kill it again :/
Ok, Installed Windows 7 and all works fine... damn. thx for the tip
I had this exact issue and fixed it. Fastboot would never see my device, and the device manager shows "Kedracom" no matter how I tried to install or force the correct drivers. Turns out Windows 10 (and Windows 8) has a feature that completely prevents installation of unsigned drivers. If you're seeing "Kedracom" in the device manager, then your driver is NOT actually installed. This is true even if Windows doesn't throw you an error message during install, or if you appear to force the installation. Even though it looks like you're doing the install correctly, Windows just ignores your unsigned drivers.
You need to temporarily disable the security feature to permit installation of unsigned drivers. This involves invoking a special restart function. http://www.howtogeek.com/167723/how...8.1-so-that-you-can-install-unsigned-drivers/
One you've done this you, you can do a forced install of the drivers you downloaded for the OP3.
It’s been a while since my last root project I was able to download and install one plus drivers. Got adb downloaded, my phone is recognized initially when when I try the command adb devices. Enter the command adb reboot bootloader which works flawlessly. However once in bootloader mode none of the Fastboot commands work. I keep on getting the waiting for device prompt.
I check device manager in windows 10 and the device is showing. Am I missing something? I tried 3 different cables, USB ports I can’t figure it out. Is there a special adb package I need to get or driver or something?
Quick specs
X570 chipset
AMD Ryzen 9 5900x
Gigabyte arous Master v2
I am using a usb 3.0 hub however I tried different ports on my pc and same issue
Oem unlock is enabled
Windows 10 Pro
Official one plus drivers
No other usb are connected besides the one hub.
Any help would be much appreciated.
Thanks
Make sure that you use the latest Platform tools from the Android website when using ADB or Fastboot. Also, can you show a screenshot of the device manager here when you're connected with your device in Fastboot mode?
here is a screenshot of my device manager when im in windows and my phone is at the home screen
{
"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"
}
Here what it shows in fastboot bootloader mode
nofroyo said:
here is a screenshot of my device manager when im in windows and my phone is at the home screen
View attachment 5665575
Here what it shows in fastboot bootloader mode
View attachment 5665577
Click to expand...
Click to collapse
You're missing the Fastboot drivers as you can see on the SS, Android connected, but it's missing the driver. Remember, OnePlus Drivers don't install the fastboot drivers, just standard ADB. Also, Fastboot uses different set of drivers, they're not the same as ADB.
I uploaded the ADB-Setup, install it, and it will install the Fastboot drivers too from Google. Make sure that your phone is connected to the PC and in fastboot (bootloader) mode when installing these.
After, restart the PC once, and you're good to go.
ekin_strops said:
You're missing the Fastboot drivers as you can see on the SS, Android connected, but it's missing the driver. Remember, OnePlus Drivers don't install the fastboot drivers, just standard ADB. Also, Fastboot uses different set of drivers, they're not the same as ADB.
I uploaded the ADB-Setup, install it, and it will install the Fastboot drivers too from Google. Make sure that your phone is connected to the PC and in fastboot (bootloader) mode when installing these.
After, restart the PC once, and you're good to go.
Click to expand...
Click to collapse
Thank you for the help I got it working, now I just need to figure out which root package I use for my phone. seem like a few different versions from what i can see. AA device is unlocked north american variant