No bootloader interface is found !
Hi experts.
ADB interface driver can be easily installed when "USB debugging" is enabled in phone because this way it allows Windows to detect a device with name string "ADB interface driver" and its specific vendor id along with product id. In my case, VID is VID_0bb4 and PID is PID_0004&MI_02 ( this PID is for ADB interface only). There is no problem in installation and detection of "ADB interface". adb reboot-bootloader is working from both Windows 7 64 bit command prompt and Ubuntu 15.04 terminal. Till now it is okay.
Now, this is what I am stuck at.
if anyone understood me with previous part please help me unlocking bootloader because unlocking bootloader requires switching into "fastboot" mode. With ADB command I am able to switch my phone into "fastboot" mode successfully. Now I disconnect USB cable from phone. Phone is still in "fastboot" mode ("=>> fastboot ..." written in lowest left corner on the screen). I connect USB cable again. No other new device is found this time. Fastboot commands that is detecting my phone successfully is with that adb interface port. Why is that ? At least I have learned from Internet that "bootloader interface" is required for Windows to unlock bootloader. Now after searching through many android_winusb.inf file from USB driver folder, I found out that the device id (VID) is same for both "adb interface" and "bootloader interface" BUT product id (PID) is different for both interfaces. Now it is VID_0bb4&PID_0FFF.
According to inf, Windows/Linux will only detect "bootloader interface" when the device which here in this case is a phone provides the VID_0bb4&PID_0FFF through the USB cable. The real problem here is my phone which is Micromax Bolt A065 (Kitkat 4.4.2, Kernal 3.4.67) is providing only one VID/PID in both ADB and fastboot mode and that is of "ADB Interface" only.
How can I get my phone to send that "bootloader interface" vid/pid to Windows/Linux in fastboot mode ?
Latest Android SDK is installed.
Tested with many adb/fastboot USB Drivers from Internet.
Related
I boot my Acer Iconia Tab A200 into fastboot mode (robot lying down and RED exclamation mark over it). I plug it into my Windows 7 (64bit) desktop computer with SDK installed, and from the directory with fastboot.exe I type FASTBOOT DEVICES but the device is not being seen, it just goes back to the prompt, like the command executed but didn't do anything. I assume this is because the drivers aren't installed. But I don't know how to install the "adb drivers". How is this done?
Go to Acer support page, you'll get the drivers there.
This device will not fully boot. It gets stuck at an "encryption unsuccessful" message. I'm trying to flash a rom image from my desktop computer using fastboot, but when my tablet is in fastboot mode, my desktop computer won't recognize it. ie adb devices command doesn't show that there is any device connected, and I think it's because the drivers aren't installed. I think those Acer drivers only work if the tablet can be fully booted.
Installed the Google USB Drivers from the SDK Manager already. Don't know what's wrong.
Alright I figured out how to get fastboot to interface with my Android tablet. The problem was that I wasn't getting the tablet into fastboot mode to recieve commands.
But now it's working. However, I'm trying to unlock the bootloader and it gives me an errors that says:
SetUnlockedMode: Error occured while unlock the device ...
Fastboot: Failed to set unlock mode
I have to unlock the bootloader before I flash an image to the tablet, right ?
Yep, surely.
Hello,
I'm (finally) trying to root my Rezound, but I'm unable to get the identifier token to get the bootloader unlock code from HTC. fastboot oem get_identifier_token gets stuck at < waiting for device >. I've ensured that:
USB Debugging is on.
USB connection type is "Charge Only".
The Fastboot option is Disabled in the phone's Settings.
HTC Sync is disabled.
There's only one copy of abd.exe and fastboot.exe (in C:\Android).
I'm running Windows 8.1, but I managed to find drivers that (apparently) worked online. When I connect the phone when it's NOT in Fastboot mode, it appears as "My HTC" under Android USB Devices. When connecting in Fastboot mode, it's in the same place, but there's a yellow exclamation with an error:
"This device cannot start. (Code 10)
A request for the USB BOS descriptor failed."
Additionally, a notification appears in the System Tray when connecting in Fastboot mode regarding the USB device malfunctioning.
It seems like I'm all set when outside Fastboot mode; the device has no errors in Device Manager and is visible when I run abd devices. It does not appear when I run fastboot devices in Fastboot Mode.
Any tips?
There are no working Windows 8 drivers for the Rezound in Fastboot... Sorry, you need Linux or Windows XP/Vista/7, wish I had a better answer for you.
Sent from my Nexus 4 using Tapatalk
Ah, I was afraid of that! Well, thanks for the quick response. I'll go dig up that Linux machine I have somewhere around here
Hello Guys,
i have a problem and hope you can help. i wanted to open my bootloader.
If i connect my G5 international with PC in fastboot the PC doesn't recognized the device.
In the device manager i can see "Android" as unrecogniced "device".
i tried several ways to update this driver but nothing helped.
So i can boot the fastboot from pc with "adb reboot fastboot".
The command "adb show devices" no problem too
But if i write "fastboot show oem-devices" i'll get the message
<waiting for device> and nothing happens.
have you enabled "usb debugging" in developer options?
Yes i enabled udb debugging and unlock via oem also.
Windows 7 will recognize an fastboot device but doesn't update/configure/install fastboot driver
fixed:
update driver -> search on computer -> Take from List -> CWM driver -> LGE ADB
pc got it
On the watch, I have enabled developers mode and then enabled ADB Debugging.
I then reboot the watch into CSC Fastboot Mode.
I installed the Universal ADB driver setup MSI.
I connected the watch to the PC
Device Manager shows ASUS Android Bootloader Device and says the Device is working properly
The USB icon in the taskbar show Android Device
I opened a command prompt in Administrator mode but when I run ADB it says device not found and Fastboot devices returns a blank.
What am I missing?
It's recognized when booting into the system but not in Fastboot mode. I am wondering if there is a specific driver for this device or not?
"Had the same issue, downloaded the Google USB driver, manually set the device driver to "Android Bootloader Interface" and it worked! Device shows up when running "fastboot devices" now."
I used the above method from another user on here. To give credit his name is CheshireShorty, link down below.
Fastboot Drivers