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
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.
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.
Sorry, just noticed I posted in wrong place. Can admin move this to the correct one?
i want to upgrade my TF201 to unofficial rom from official rom.
I follow the instruction flash TWRP in fastboot mode.
This is the wired thing, in device manager, 'ASUS fastboot interface' was shown. In device & printer, it shown as 'fastboot' under unspecified category.
In CMD windows, it can return the serial number within the first 10 seconds (roughly) after Computer turned on(Yes, the PC, not tablet).
after a very short time, fastboot devices returns nothing, flash command returns 'waiting for any devices'.
I'm using 64bits windows 10. I tried both usb 3.0 and 2.0, same issue.
BTW, for people who encountered 'device not recognize' issue, pleas disconnect the keyboard.
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
I'm at a total loss here...
phone has unlocking and USB debugging toggled on.
phone is not a US phone and unlocking is allowed.
phone goes into fastboot mode (by turning on while holding volume)
"fastboot devices" command returns my phone is in fastboot and connected
"fastboot oem unlock 0xPASSWORD" returns FAILED (remote: 'Command not supported in default implementation')
and fastboot: error: Command failed
I have no idea what to do or try from here.
If I try to flash an image i get:
FAILED (remote: 'Download is not allowed on locked devices')
so, defiantly still locked out of the bootloader
Try below steps
1. Ensure you have platform tools 33.x , 34 has issues.
2. Try to reboot to bootloader from pc.
adb reboot bootloader
3. Try running
fastboot flashing unlock unlockcode
Try it :
fastboot oem unlock
or
fastboot flashing unlock
SOLVED I am so happy. I'm on day 3 of trying to get the phone to bootload.
there is definitely a difference between going into fastboot through the phone itself and through adb commands on PC.
fastboot through the phone shows the drop down menu and no blue light illuminated on phone.
fastboot through adb phone is black screen with a blue light on right corner on the phone.
the windows drivers behave differently between the two. I am running windows 10. phone model XQ-CT72
steps that solved the issue. For anyone in the future.
I downloaded and used platform tools version 33.0.3 NOT version 34.
"adb reboot bootloader" used from windows PC
opened windows device manager found my "discovered device" and forced it to use the SONY driver downloaded from sonys website. It would not detect it on its own, or even use the SONY driver without me telling it to specifically. device manager> "andorid" > properties > update driver > browse computer for driver > installed sony driver
everything worked following these instructions here https://www.droidwin.com/unlock-bootloader-and-root-sony-xperia-1-iv/
alexriethmeier said:
There is definitely a difference between going into ...
Click to expand...
Click to collapse
fastboot, part of the android bootloader, abl
fastbootd, part of recovery
I had same issue and same solution fixed it what you showed and did. I was terrified, after investing so much money on this phone and not getting it unlocked.
You won't need to go through such hassle if you just use Linux VM (a Ubuntu distro will do). The driver works out of the box.