Hi. I was having the title problem; which also prevented me from restoring to stock. I ended up fixing it by switching the cable from my USB 2.0 port to my USB 3.0 port. Afterwards the fastboot commands worked as intended! Just wanted to share what worked for me.
Thanks! Worked for me!
I was having issues installing TWRP until trying USB 3.0 port. I then entered, in Linux terminal: fastboot boot twrp.img
I was then able to install TWRP from OTG and continue.
Related
Hey guys! I've been having this issue with my Verizon Galaxy Nexus where when I'm on the Bootloader and plug my USB cable into the phone, it says: Fastboot Command Read Error -2147483647
Some strange things accompany this error as well. When I boot into recovery, Wugfresh, Quick ADB, etc. all recognize the device! Yet, any function I use does not work. For instance, flashing a .zip through Wugfresh never goes through the flash process. I'm stuck at this point. I've re-installed the drivers, tried different computers and USB cables, and scoured XDA! Any help is much appreciated
I'm trying to update from 8.0 to 8.1 using the ota file posted on the Google images site using stock recovery and adb sideload and I can't get it to work. The phone is totally stock, locked, no root etc. I'm using an Ubuntu based distro on my laptop. I have the adb and fastboot working showing the serial numbers when testing adb devices / fastboot devices. I added the path to platform tools and tools in my bashrc. I have 51 android rules. My phone is being recognised by all accounts. How ever when ever I adb sideload update.zip nothing actually happens at all on my pc. The phone screen sits there saying verifying update package or something but nothing actually flashes or happens. I have tried usb 2.0 & usb 3.0 ports, different usb a - c cables. I even got fresh downloads of the ota package. I went a step further and reinstalled the android SDK. By all means it should work as the phone is recognised in all modes including sideload but nothing happens when the phone should be side loading the ota file. Please help! Thanks in advance
Are you in recovery mode and USB Debugging is turned on?
Usb debugging is turned on in the main phone settings. The phone was in recovery and apply update from adb mode
I'm not enrolled into beta etc. Phone is 100% stock
To update I bought yet another usb cable and this one worked and I was able to complete the update. It was a usb 3.0 A - C 1 meter cable and I used a usb 3.0 port on my laptop.
Hey gals and guys,
my girlfriend dropped her Xiaomi A2 lite and no the touchscreen doesn't respond. The phone has the stock Android One and I can only access fastboot.
Code:
fastboot devices
recognizes the phone.
The recovery is the stock recovery.
Code:
adb devices
won't recognize the phone and gives me an empty line as output
I also can't access the phone via usb with my filebrowser. If I try, the phone makes a "bing"-sound and the filebrowser gives me:
Code:
unable to open MTP device
I am using archlinux and I also have a windows device available.
Is there any chance on getting pictures etc from the phone?
Any suggestions besides getting a replacement for the touchscreen?
Thank you so much.
Connecting via USB probably needs you to click something.
I'm guessing developer mode is not enabled...
If you've got a micro USB OTG cable, you could plug a mouse in.
If you boot TWRP (fastboot boot twrp-3.3.1-dees-troy.img) you should be able to get adb and usb transfers working. Don't need to install it, just boot it. Not sure if that works without unlocked bootloader.
If you've got a micro USB OTG cable, you could plug a mouse in.
Click to expand...
Click to collapse
This did the trick.
Thank you
Fastboot does not recognize when unlocking bootloader.Fastboot does not recognize when unlocking bootloader.
Check to make sure you have the latest drivers installed.
I could not for the life of me get it to work on my windows laptop. Tried installing the OnePlus USB Drivers, tried isntalling generic USB drivers, rebooted multiple times, tried differetn cables, tried different versions of ADB, through chocolatey and the minimal ADB installer here on XDA.
On my other laptop running Arch Linux i installed the android-tools package and it worked perfectly though. adb reboot, and then fastboot devices, and fastboot oem unlock on first try.
I have one device (I do not remember what one) that always needed to be unplugged on the computer side after a reboot to bootloader for fastboot to find it.
A bit annoying but, I got use to it. I use USB-A 2.0 Port to USB-Micro/USB-C cables.
Unplugging the cable on the device side did not make a difference, it had to be the computer side.
Also try a different cable and USB port on computer.
Not sure if it helps or makes a difference in your circumstance. ¯\_(ツ)_/¯
I just remember it driving me crazy until I accidentally unplugged it and it was found as soon as I plugged it back in.
Cheers.
PS.
Found a post I recently made about cables I use for adb/fastboot.
USNF - [ xdaThread ] - Post # 2,638
Hey all,
I am attempting to root my 2XL, and have so far unlocked the bootloader using ADB, however when attempting to use
fastboot boot <twrp.img>
I get stuck on < waiting for any device >
Using Deuce's flashing script, I get the following:
Checking if Fastboot exe is accessible..
Checking if Fastboot works correctly
Error! Fastboot not accessible!
Press Enter to continue...:
When attempting to update the device driver using the official Google USB Device driver inf, I get the error message
The folder you specified doesn't contain a compativle software driver for your device.
If the folder contains a driver, make sure it is designed to work with Windows for x64-based systems.
Earlier today I was able to update the device driver, and that fixed an issue I had with ADB not working, but I've hit a wall with this and there doesn't seem to be any solutions online.
Any help is greatly appreciated.
Cheers,
Boots.
How did you unlock the bootloader if fastboot isn't working?
Does the phone show up in device manager when connected and at the bootloader screen? If yes, what is the driver info?
To check if fastboot is working, run fastboot devices in the command line.
Note that USB-C ports tend to be unstable with this phone. Connect it to a USB-A port.