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.
Related
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
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
ItsJono said:
I'm trying to flash TWRP, i've got ADB and i've got the Universal ADB Drivers. The device is properly detected when in EUI and my Device ID is displayed correctly when I type 'adb devices', however when I reboot into fastboot and type 'fastboot devices', nothing is listed and cannot continue.
Which drivers do I use? What is it that I need to continue?
Thanks!
Edit: Nevermind, connected it into my linux machine and got it to work easier (lol winBLOWS amirite) and finally got it to recognize the device in fastboot mode. I kept rebooting and failing to get into TWRP. I found somewhere else that before doing 'fastboot reboot' that you should hold VOL UP so you can immediately boot into twrp and make it permanent, which ended up working for me. Freedom!
Click to expand...
Click to collapse
I believe you need to configure in the developers options that you don't want to have the recovery overwritten on reboot. What also seems to work is to boot into the TWRP from the command line via 'fastboot boot <recovery-file-name>'
I have the exact same problem. I have installed all drivers and adb, but as soon as i am into fastboot and my device doesnt show up in the command line. If i want to install the recovery the command line just says <waiting for device> and nothing happend.
I already enabled the "Enable AT Port" Settings (http://forum.le.com/in/index.php?threads/le-max-2-x820-qpst-not-working.14820/) but i think this is not permanent turned on on my phone, because i have to repeat this step after every reboot.
Anybody got some tips?
Edit: Also booting directly into TWRP doesnt work, 'fastboot boot <recovery-file-name>' just ends up in <waiting for device>..
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
RovnyiK said:
If you're using Win 8 or Win 10 you should turn off the driver singing verification before installing usb drivers for device.
In your case one of the drivers was blocked from installing and the systom does not see the device after it switches in fastboot/recovery mode.
I am not allowed to post urls, so google this: How to Disable Driver Signature Verification on 64-Bit Windows 8.1 or 10 (So That You Can Install Unsigned Drivers)
Click to expand...
Click to collapse
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Kampfgans said:
Thanks for this Hint! Didnt know this
Nevertheless, no improvement so far. I Unistalled every driver and installed them again, but the PC doesnt recognize the phone when its in fastboot mode
Click to expand...
Click to collapse
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
RovnyiK said:
There is a chance, that your computer has installed the WRONG driver for the fastboot mode, so find any related to the phone entries in Device Manager when the phone is connected in fastboot mode, and if it is not "Android Phone/Android ADB Interface" -> remove them with remove driver checkbox checked. Optionally, if nothing changes -> try to manually pick the device driver to Android ADB Interface
Click to expand...
Click to collapse
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Kampfgans said:
I tried it now with the fifth computer and after a few strange error messages, it "succesfully" installed TWRP.
BUT: There is no TWRP installed on my phone. I followed every tip which i found how to exit the fastboot mode (pressing Vol+ & Power / Removing USB Cable / Tried TeamSpains Automatic Installer).
What is wrong with this phone ? - I think i will oben a new thread, thanks for your help!
Click to expand...
Click to collapse
Kampfgans: Klingt irgendwo zwischen lustig und richtig bedrohlich...
Lots of ROMs (including most CM variants) like to "automatically 'recover'" recoveries, that is they overwrite the recovery partition with a copy of the "original" every time you reboot.
I seem to remember that my first attempt to overwrite the stock recovery using "fastboot flash recovery <twrp-image-name>" also didn't succeed in making TWRP "stick".
Within the CM13 which I installed next (over the stock v15) there is a developer option to control that, but in this case I simply used a trick, which seems to bypass the recovery overwrite: I told the phone to boot the TWRP recovery over USB after flashing.
It went like this:
fastboot flash recovery <name-and-path-of-TWRP-recovery> //puts the TWRP image on the recovery partition
fastboot boot <name-and-path-of-TWRP-recovery> //bypasses the recovery overwrite logic of either the bootloader or whereever it hides
That booted TWRP over USB and allowed me to install CM13.
There I disabled recovery overwrite in the deveoper's options and I've never had issues with TWRP disappearing since.
Actually you should in theory be able to leave the stock recovery in place and still use TWRP by booting it over USB on the fastboot command line.
I install drivers and USB but when trying to go to fast boot I receive "waiting for device"
I have a Zeki TBQC1063B Tablet with Android 4.1.1 on it. I am trying to see if I can unlock the bootloader so that I can try to put Ubuntu for mobile on it. This thing has been nothing but the bane of my existence all night tonight. I have made sure that while the device is on, the USB Debugger IS on, and I am using the correct USB drivers. In my SDK tools, I run the command adb devices and I get the following result:
List of devices attached
??????????????? device
For curiosity, I ran the command fastboot devices and nothing comes up. When I try to boot into "fastboot mode" it just comes up with a recovery screen with no mention of Fastboot. I am lost, confused, and very frustrated. Any thoughts?
So my device is recognized when it's turned on but then I go to command prompt and click ADB reboot bootloader (enter). It just says waiting for device. If it's on and I click ADB devices in the command prompt it tells me the serial number and then says device. On the computer management it is recognized as a device it says the name Xperia XA Ultra. I tried to update the Google driver into ADB but that was a failed attempt. I couldn't quite understand what I was supposed to do there or really even follow the instructions because it kept telling me that I was unable to update drivers after I followed the instructions they gave me. I just kept getting an error message. So I'm wondering how do I solve this problem? I really would like to unlock my bootloader and I'm not even sure if it's going into fastboot. I got the notification after turning off the phone hold Volume Plus and plug it in it said of my computer that it was installing the fastboot drivers. I'm assuming it was in fastboot at that time even though I didn't get a blue light it just turned blue for a minute and then it was Green. It said it was installing fastboot drivers so I'm assuming it was in fastboot mode. This is a really tricky process I guess.
What windows do you have?
Also I would recommend you to Google how install fastboot on your Windows type.
Sent from my F3213 using xda premium
I have windows 10
Windows 10. Why would I need to install fastboot on Windows? Fastboot is on my Android device. I use ADB. Android debugging bridge is the bridge that goes between your operating system and fastboot the bootloader and Android and all of that in order to be able to communicate with the phone. Why would I need to install Fastboot on my windows? You sound like a customer service representative. I can't even talk to them anymore because they tried to get me to act like Chris Farley.
If you don't install fastboot on your computer you can't unlock bootloader you can't install custom recovery or root the phone!
Sent from my F3213 using xda premium
Hello,
Here is the link to the ADB Installer that contains all the files you need (ADB, Fastboot and Drivers). Download and following the screen information to install the program.
https://forum.xda-developers.com/showthread.php?t=2588979/
Thanks,
Danjuma
Hi there
please note that Windows 10 x64 blocks the installation of unsigned drivers. To be able to install them anyway you have to enter the Windows Test Mode. To do this you just have to run "bcdedit /set testsigning on" in an administrative command line and restart your computer afterwards. You'll see "Test Mode" at the bottom right corner of your desktop. To leave the testmode use "bcdedit /set testsigning off" and restart again.
Done all of this and it doesn't work...
You have to use drivers from Sony for Flashmode and use drivers included in Flashtool (C:\flashtool\drivers) for fastboot and ADB. No problem for me with Windows 10 64bits and don't need to use Test mode.
I'm running into issues with my Compact X. Current situation:
- Omni 8.1 rom installed, but doesn't boot. Stuck on Sony logo.
- TRWP 3.3
- Rooted
- When in fastboot mode (vol up + connect usb cable) the device manager shows: Android Device > Sony Fastboot Interface.
- Windows 10 running in "Test mode"
- adb & fastboot v1.4.3
ADB does not recognize my device when the device is in fastboot mode. When it's in recovery mode the command 'adb devices' shows me the device listed. I can then reboot in fastboot mode, but then the device isn't listed anymore. I'm not sure what happened because a couple of hours ago I installed TWRP using fastboot.
I'm trying to get this thing up and running again, but not being able to flash anything via fastboot complicates things. Any idea's what could be the culprit?
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Some random said:
Download official Android drivers by Google and force Install them (search: Force Install Windows drivers" anywhere preferably YouTube
Click to expand...
Click to collapse
Thank you for your reply. As far as I know the official drivers were already installed. Because at first my device did show up listed when using the command 'adb devices' and I successfully flashed TWRP recovery. But to be sure I repeated the process:
- Connected my phone in fastboot mode (vol up + connect usb cable). The blue led lights up.
- Go to the device manager, right click on 'Android ADB interface' device and manually install the driver via 'Have disk'.
- The driver installs with no errors.
But still my phone is not listed and I cannot flash anything.
When the phone is in recovery mode it is listed using the 'adb devices' command. But when I'm trying to flash something I get the message <waiting for device> .
Ok, I restored my computer to a point before I started messing with my phone. After installing the official drivers my phone is still not listed (adb devices), but this time flashing did work. I managed to flash the AOSP 8.1 image. My phone is up and running again!