Fastboot: Stuck at "waiting for device" - YU Yureka Q&A, Help & Troubleshooting

have already used the PDA method still no luck

Related

[Q] Trying to unlock write failed error

Just got Nexus 4 and trying to unlock the bootloader.
Follow the instructions and Fastboot detetcts the Nexus ok using command "fastboot devices"
But when I then type "fastboot oem unlock" I get "command write failed unknown error"
Any ideas please?
robolots said:
Just got Nexus 4 and trying to unlock the bootloader.
Follow the instructions and Fastboot detetcts the Nexus ok using command "fastboot devices"
But when I then type "fastboot oem unlock" I get "command write failed unknown error"
Any ideas please?
Click to expand...
Click to collapse
Off the top of my head: try another port, another cable reinstall drivers.

Booting to recovery failed

I tried to boot my phone into TWRP recovery using the adb command to boot it remotely without having the recovery installed. It tries to do it but it comes up with an error message saying: "FAILED (remote: Command not allowed). How do I get this to work?

fastboot Failed (remote: command unknown)

Hi
I have Lenovo Tablet 2 Pro 1380L. I have simpley bricked it by flashing wrong firmware.
the problem is that when I boot it into FASTBOOT I cannot flash any IMG file and I get an error message that says "FAILED (remote command unknown)"
any idea why I'm getting such message ?

Flashing Help - Mismatching image and device

Hi All,
Trying to flash an A1 with the following rom images and both give the error of Mismatching image and device.
tissot_images_V9.5.9.0.ODHMIFA_20180316.0000.00_8.0_f8cd1b4e8e
tissot_images_V9.5.11.0.ODHMIFA_20180504.0000.00_8.0_1a04581058
The phone is currently a brick belonging to a friend of mine, and I would like to try and get it back up and running. Fastboot can see the device, as can MiFlash, but when running the command
Code:
Fastboot oem device-info
it throws an error stating
Code:
FAILED (Command write failed (Unknown Error))
Any ideas? The device will boot into fastboot but no further, and gives a warning about being unlocked when you try to boot. I'm not sure how to check if it is a re-branded Mi5x or not, as the box is a Global version A1 box with corresponding IMEI cods to a model MDG2. The phone does have the Android One laser etch on the back however.
By bricked I mean the phone will turn on, load the warning about an unlocked bootloader and then go to the Android One "bars" screen you see before the pretty android one loading screen. Here it just stops.
The drivers i'm using come from the MiFlash install, and I've tried doing a TWRP install with fastboot but still no joy. Fastboot can see the device, and talk with it, but nothing I seem to do has got the kit back working.
Anyone able to give some help or advice?
Further info on what ive tried here
http://en.miui.com/thread-3158263-1-1.html

Fastboot stuck at 'sending'

Running the command (on Linux)
Bash:
~/platform-tools/fastboot flash recovery recovery.img
I get:
Code:
Sending 'recovery' (21101 KB)
...and that's it. Fastboot hangs indefinitely, seemingly not sending anything, and can only be killed by unplugging the USB. The phone says "FASTBOOT MODE" in green. I've tried all 3 USB ports on my laptop, the paths and filenames are correct, i've tried a lot and using both twrp and LineageOS recovery images, but I never get beyond this, except for getting an error sometimes, "FAILED (Write to device failed (Protocol error))", "FAILED (remote: 'unknown command')", or "FAILED (Write to device failed in SendBuffer() (Protocol error))", which turns into this after rebooting fastboot mode or trying again. What am I missing? I've unlocked the bootloader with the app, I'm trying to install a recovery to install LineageOS.
Edit: Doesn't seem like there's a solution, but I tried another computer and it worked. Annoying how buggy it is, but there.

Categories

Resources