Basically my phone stops being recognized by the computer once I reboot into the bootloader. To be clear, the phone is recognized just fine and shows up when I type 'adb devices' when the phone is operating in the android os. Seeing that all is well there, I proceed to 'adb reboot bootloader' and it appropriately reboots to the white screen with the android on it. But there the problems begin: It reads on the screen:
FASTBOOT&RESCUE MODE
Please Connect Usb Cable to
Your Computer and Open Hisuite
More information:
the huawei website
Then it displays the droid
Then it says:
Phone Locked
FRP Unlock
I tried going ahead and running 'fastboot oem unlock ###...' but it just sits there waiting for a device to be connected. I have tried multiple USB drivers on my 2 windows 10 computers. I have removed all drivers using USBdeview and tried different drivers. Windows will not allow me to point to manualy choose my driver, instead saying, 'The folder you specified doesn't contain a compatible software driver for your device. If the folder contains a driver, make sure it is designed to work with windows for x64-based systems.' So I tried it on an old 32-bit windows 7 system. No joy. I've tried multiple USB cords and ports. In windows device manager it has the device labeled as 'Kedacom USB Device' -> 'Android Bootloader Interface'. I can't figure out what's going wrong other than to say it seems that Windows is not using the correct driver once it enters the bootloader. PLEASE HELP!!!
Surely you have a drivers problem.
Are you using Huawei or Google adb drivers?
I couldn't find any Huawei drivers. So I used the drivers from Android developer site and several others I found here on XDA. If you have a link for specific Huawei drivers that would be AWESOME!
Try HiSuite.
Sent from my Galaxy Tab 3 using XDA Labs
ajalogan said:
I couldn't find any Huawei drivers. So I used the drivers from Android developer site and several others I found here on XDA. If you have a link for specific Huawei drivers that would be AWESOME!
Click to expand...
Click to collapse
Have you tried this?
http://semantic.gs/huawei_handset_adb_interface_driver_download
Google ADB should be fine.
i just unlocked bootloader few hours ago... i using adb driver from this thread , and it worked for me http://forum.xda-developers.com/showthread.php?t=2588979
and i also installed HIsuite before that...
seii3 said:
i just unlocked bootloader few hours ago... i using adb driver from this thread , and it worked for me http://forum.xda-developers.com/showthread.php?t=2588979
and i also installed HIsuite before that...
Click to expand...
Click to collapse
Did you used Huawei oficial site to get unlock code or did you used a 3rd party method?
zinko_pt said:
Did you used Huawei oficial site to get unlock code or did you used a 3rd party method?
Click to expand...
Click to collapse
Huawei official website
same issue, different flavor....
I'm having this issue as well, on a debian system. I have good ADB connectivity, all ADB commands seem to work fine. With fastboot, I get a device listed form them fastboot devices command. After that all fastboot commands are "waiting for device". If this is a driver issue, any hints on how to install those drivers in Linux/Debian? I tried a number of google searches, and have found all sorts of information, but nothing telling me where to put which files where to get the working drivers. Any hints?
Are you on Windows? Check if the device manager shows the device as Android with an exclamation mark inside a yellow triangle.
The problem could be with Windows 8.1/10.
Try with Windows 7
Here are the official drivers for Windows x64, ripped from Hisuite:
Mediafire | MEGA
Windows 10 is fine, it's what I use and have zero problems. Most of the time is other software that conflicts.
I'm facing the exact same issue (using Windows 10). I did the oem unlock using the code from Huawei. However after connecting the phone via cable to the PC, it does not allow me to browse the storage (internal or SD card) of the phone. All I see is a device named KIW-L24 which appears as an empty folder, and a virtual CD drive HiSuite. I installed HiSuite and the software shows me the photos/apps/etc. however there is no way to move files from the PC to the phone storage. Any pointers to the process to install the right drivers?
can you give me the link for huawei official win X32 drivers pls?!
Install hisuite , it will install all huawei drivers that u needed
Related
Hi there,
I got a really nasty problem here: when I connect my Sony Xperia T to my home computer, the ADB driver will be installed properly. When I connect the same phone to my work computer, Windows just doesn't want to accept the drivers. The following things are equal:
- USB debugging is always on on the phone
- Both computer are running Windows 7 64bit
- On both computers I am pointing the Windows driver installation at the same folder with drivers downloaded from Sony.
The thing that is different is the device ID that Windows reports in the Details dialogue from Device manager:
On the home PC it is:
USB\VID_0FCE&PID_5182&REV_0228&MI_01
USB\VID_0FCE&PID_5182&MI_01
On the other PC where things go wrong it is:
USB\VID_0FCE&PID_5182&REV_0228
USB\VID_0FCE&PID_5182
So it seems Windows is not recognizing the phone as a composite device (MI is it multiplexing identifier?). I double checked that USB debugging is always on and also rebooted Windows.
What could could be causing this strange problem?
Android version is 4.1.2 (original Sony firmware).
Thanks
Tom
You could search for the adb drivers for your phone on Sony's website, maybe they are available there
Sent from my Nexus 4 running Android 4.2.2
mihahn said:
You could search for the adb drivers for your phone on Sony's website, maybe they are available there
Sent from my Nexus 4 running Android 4.2.2
Click to expand...
Click to collapse
This is exactly what I did! Downloaded the adb driver from Sony's website. Installed them on one computer - works. Transferred exactly this driver package to the second computer with a USB Stick.
On the second computer, Windows does not find a matching driver for the same phone in the same driver package.
The reason apparently is that the phone reports a slightly different USB id when connected to the second computer (missing the MI at the end of the ID, see my original post).
Hello,
I've recently decided to unlock and root my G5, however I'm having an issue with the unlocking process when using adb and fastboot.
Once I reboot the device into bootloader mode via adb reboot bootloader I cannot get it to recognize the phone. fastboot devices shows nothing and fastboot oem device-id just hangs on <waiting for device>.
I've tried downloading and playing around with all the different drivers, I've updated the official LG drivers, installed the USB drivers from Android SDK and downloaded the universal ADB drivers.
When in bootloader mode the device manager only shows these 3 drivers as available:
#recovery
Android Bootloader Interface
Kedacom KDB Interface
None of them work with fastboot.
Are you using the lg cable?
Yes, I am.
Try with different PC? I had similar issue with old phone in the past. Windows 8 blows + 10. When I used my gf laptop with windows 7, worked like a charm.
I have a H830, same problem. Nope, I don't have a windows 7 anything I can use, only Widows 10. My device manager shows the same titles as the OP. I have tried different drivers, different fastboot setups, nothing works so far. There are people who have gotten it to work on windows 10, but they don't bother to detail how.
I'm having the same issue when I tried to update my rooted H850 to 10i...
The funny thing is that I've used this laptop b4 with no problems; once on Windows 7 and once on Windows 10 but it's suddenly not working. Also tried on a friend's computer with Windows 7 and that didn't work either...
I remember a few months back there were widespread reports of people having the same issue, which I can only imagine got solved...
Tonight I'm going to try a USB 3.0 port on a different computer and try this Universal fastboot and adb tool:
http://forum.xda-developers.com/lg-...stboot-adb-tool-t3475840?nocache=1&styleid=21
Maybe yall should try with Linux OS? I wonder if yall could use a Ubuntu live disk to do it? So you don't gotta install Linux. Anyone familiar with that?
EmoObama said:
Hello,
I've recently decided to unlock and root my G5, however I'm having an issue with the unlocking process when using adb and fastboot.
Once I reboot the device into bootloader mode via adb reboot bootloader I cannot get it to recognize the phone. fastboot devices shows nothing and fastboot oem device-id just hangs on <waiting for device>.
I've tried downloading and playing around with all the different drivers, I've updated the official LG drivers, installed the USB drivers from Android SDK and downloaded the universal ADB drivers.
When in bootloader mode the device manager only shows these 3 drivers as available:
#recovery
Android Bootloader Interface
Kedacom KDB Interface
None of them work with fastboot.
Click to expand...
Click to collapse
I had exactly the same problem, but I solved it. Check my post #306 and previous here:<br />
<br />
http://forum.xda-developers.com/showthread.php?t=3363040<br />
<br />
My story starts with #289. Good luck.
Wysłane z LG G5 H850
The problem comes out because of the drivers not installed when the phone is in the fastboot mode.
You can solve the problem going to MyComputer/rightclick/manage/devices while the smartphone is in fastboot mode and then installing in the automatic way the proper drivers.
I have found the solution to get the fastboot work! It works great even in Virtual machine with USB 3.0 and Windows 10.
1. install LGBridge (you also can get it from codefire site) or LGMobileDriver (you can get it from codefire site)
2. connect the phone to PC, reboot phone into fastboot mode
3. open Device manager -> other devices -> Android -> update driver -> browse my computer for driver software -> let me pick from a list of device drivers on my computer -> show all devices -> next -> have a disk -> browse -> C:\Program Files (x86)\LG Electronics\LG Mobile Driver\ -> select "lgandbus.inf" -> OK -> LGE Mobile ADB Interface -> next -> yes -> close
4. reconnect the phone to PC
5. run any desired fastboot command
Here is the video tutorial.
please help me! i've FONEPAD ME175CG, blocked. i cant entry in recovery mode.... my pc dosnt see .... i've install the driver intel, but fastboot command doesnt work... PLEASE HELP!!!
donaldduck75 said:
please help me! i've FONEPAD ME175CG, blocked. i cant entry in recovery mode.... my pc dosnt see .... i've install the driver intel, but fastboot command doesnt work... PLEASE HELP!!!
Click to expand...
Click to collapse
Hi
Looks like your computer isn't recognizing the attached FonePad.
Assuming you've checked the USB cable and the connecting ports are working fine, if you are using a Windows pc, it is likely the bootloader interface drivers havent been installed properly specially if you are on Windows 10 anniversary update or beyond. This is because latest Windows builds won't allow unsigned drivers. So you can either try to download the device drivers from Asus official site and install them afresh, maybe the last time they didn't get installed properly. If you still can't, you can try using a pc with an older Windows version. You can Google for "Windows enable unsigned drivers" without quotes.
I have a FonePad ME372CG model and I've faced this issue once, rectified with ensuring that the bootloader interface driver shows up in device manager > android device name > ADB Bootloader Interface
Once you've ensured the drivers are installed okay, you can check for device connectivity by the flashboot devices command, should bring back a string of numbers.
If above fails and you're sure you've installed everything fine, you may want to check out about flashing raw firmware. I've never tried it but have seen users on asus forums mention it as a means to revive bricked devices. Here's a link to the raw firmwares
http://asusraw.blogfa.com
Please be absolutely sure of what you do and take responsibility for it
Sent from my Moto G4 Plus using XDA Labs
my mi a3 is not recognized when in fastboot mode by the computer
I had this problem just some couple of hours ago and what you have to do (or at least it solved this in my end) is go to Manage Devices, scroll to TP-Link Android Phone, expand it and right click Android Bootloader Interface and uninstall without deleting the driver, then refresh for hardware changes and it will install the driver again and fastboot will work this time.
Jhon_Locke said:
I had this problem just some couple of hours ago and what you have to do (or at least it solved this in my end) is go to Manage Devices, scroll to TP-Link Android Phone, expand it and right click Android Bootloader Interface and uninstall without deleting the driver, then refresh for hardware changes and it will install the driver again and fastboot will work this time.
Click to expand...
Click to collapse
I'm facing this same issue. Please can you tell me where I can see Manage Devices on my computer? I'm using Windows 10.
I had the same issue. I tried all the methods that i researched. Even tried virtual machines running Windows 7 and Linux but same thing happens. I thought it was a Windows 10 issue. Til 1 day i tried to use a different cable, and DAMN! that fixed it.
same here, recognized as adb device but not recognized by fastboot.
I'm using Linux and fastboot work well.
The problem is that with lsusb no device is displayed, so I think it's a bootloader issue, is the bootloader environment corrupted? is there other setting to enable other then enable usb debug and enable OEM unlock?
Go to device manager right klik on android device and update the driver automatic.thats all.
U had the same problem and i solved with this.
Probably you don't have installed correctly fastboot drivers
Barbiox Dogg said:
I'm facing this same issue. Please can you tell me where I can see Manage Devices on my computer? I'm using Windows 10
Click to expand...
Click to collapse
im late but if u still need to know then hold down windows and x, a list should come up and then click device manager from there
deniloo said:
my mi a3 is not recognized when in fastboot mode by the computer
Click to expand...
Click to collapse
Just Update the device driver probably be showing under others in Device manager.
Visit this site to get the driver for your device. https://www.getdroidtips.com/download-latest-xiaomi-usb-drivers/
Dears,
How has this issue just "disable driver signature enforcement"
Search youtube on this and follow instruction
Say thanks if it help please,
So, I have searched Reddit and other sites for clues and help and I have had no luck. I have even contacted an android developer and had him try on his computer and had no luck.
I am trying to install Lineage OS for 17.1 and am currently trying to root my device. I have downloaded Google USB Drivers directly and tried from Android Studio. It detects my device fine. I go into command and run adb device, it detects my device. I reboot the device into fastboot, windows detects the driver but has no driver to install. I manually install the driver and it says it "Windows could not find the drivers for your device" despite me pointing it to "...AppData\Local\Android\Sdk\extras\google\usb_driver" which is where the driver is located. I click let me pick, install it under Andoid Devic -> Android Bootloader Interface. It says "Successfully Updated Driver" but put the device in "Other Devices" with a "?" on the icon and "Unknown Device". Even tried to see if it still worked but no device was detected (fastboot device). The Google Pixel C is "Waiting for fastboot command . . . . " but that's it.
Tried both drivers downloaded. Windows updated and no driver download. Restart windows countless times. New usb cable. Different usb port including usb 2 and 3. Nothing.
Developer reported same. Any ideas appreciated!
Thanks!
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
jwoegerbauer said:
@slitterell
Never had troubles with ADB and/or Fastboot drivers.: I'm on Windows 10, too.
Use the ones as attached
Click to expand...
Click to collapse
Sorry for the slow response.
Same issue. I wouldn't expect otherwise though because the ones straight from Android Studio and Googles website doesn't work. Still shows "Unknown Device" and won't let me install the driver after showing "Waiting for fastboot command. . . ."
Drivers work fine until in fastboot mode.
Waiting for fastboot command. . . .
@slitterell
I'm pretty sure the USB driver ( does NOT mean ADB and/or Fastboot drivers ) you've installed is the culprit: Uninstall it and install the one suitable at 100% to your phone, will say the Google USB driver.
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
@slitterell
The mentioned Google USB Driver is required for Windows if you want to perform adb debugging with Google devices.
So it should be the correct USB-driver in your case.
The latest is attached.
slitterell said:
I don't disagree with you except I literally downloaded the the drivers and they won't install on either computer saying they are incompatible and they are the ones literally off the google website.
Click to expand...
Click to collapse
Google's driver package doesn't have Product ID of the Pixel C mentioned in its inf file, so it doesn't work for you. Interesting that you got adb connection anyway. So, maybe Windows has installed automatically some driver but it didn't had entry for the bootloader/fastboot.
Here is how people have added those adb entries. Bootloader entry can be found from device manager and added the same way...
https://stackoverflow.com/questions/34775508/where-is-the-windows-adb-driver-for-the-pixel-c
Or you could just use my Yet Another Universal ADB Driver Package
https://forum.xda-developers.com/an...staller-universal-adb-driver-package-t3595277
http://yet-another-universal-adbdriver.blogspot.com/
and hope for the best...