fastboot not detecting phone - Huawei Watch

hello all,
I am trying to install android 2.0 preview. I installed android studio and I am able to get device listed using "adb devices" command.
I am able to enter boot loader using "adb reboot-bootloader" as well.
but in boot loader when I try to run fastboot oem then it says "waiting for an device".
also "fastboot devices" does not return anything.
E:\Android\sdk\platform-tools>fastboot oem unlock
< waiting for any device >
I can see "Kedacom USB device" is installed while in bootloader mode. can anyone help me? thanks
I am using windows 10

Same here, not detected by '
Code:
adb devices
' or '
Code:
fastboot devices
'. Windroid toolkit stuck at "rebooting device" while it is in Fastboot mode, and if you reboot it manually, it gets stuck at "unlocking device". Drivers are installed, maybe not properly?not properly?

adb devices works for my case after downloading latest sdk. but fastboot is no go.

windows xp ???

Sorry forgot to add that details - windows 10

Have you found a way to resolve this?

Related

Returning to Stock, fastboot doesn't seem to exist.

I am trying to return to stock on my T-Mobile HTC One M8 using the nandroid backups thread that @ckpv5 put up here. I need to get all the information using "fastboot getvar all", but fastboot devices doesn't list anything. My device is listed when I type in "adb devices". USB debugging is enabled. When I type in "adb reboot fastboot", my device just restarts. When I type "adb reboot bootloader", it brings me to the bootloader. I choose reboot fastboot, but fastboot devices still doesn't list anything.
My adb and fastboot drivers are from the "Minimal ADB and Fastboot" thread here.
What is the issue?
Update 1: I re-installed the HTC drivers that come with HTC Sync Manager and it has worked so far.
I GOT IT TO WORK. THANKS ANYWAYS!

Fastboot doesn't see my Zenfone 2

Hi, I searched for an answer but I didn't find it, so I created this thread.
My Z00A is running on the latest official OTA version perfectly fine. It is unlocked but bricked once and I successfully unbricked it.
I installed Intel Android driver and adb on windows 10.
Booted in Android, adb sees my device when I enter "adb devices".
In the bootloader, when I enter "fastboot devices", fastboot leaves a bank space and open a new command line and if I enter any other command it says < waiting for device >.
It looks like Windows 10 didn't let the driver work properly. I downloaded the drivers from ASUS and manually installed the bootloader interface driver via legacy wizard. Then, I uninstalled the old one and now fastboot is functional.

fastboot never start after update to android 6

Hy
I had an unlocked bootloader phone. Yesterday I flashed the new Android 6, Europe version from the Huawei blog forum, no beta, on my Huawei GX8. I used the method, dload on SD card, Phone off an the press Volume down+volume up+Power button.The flashing was normaly.
Now the phone starts normaly but I can´t start fastboot. When the phone is off and i press Vol down + Power the phone start the android system and the Huawei logo is coming not the fastboot Modus. I can see my phone and the order under Windows but i can not control my phone with the fastboot command. (example: fastboot device. the answere ist searching devices, but it comes no resolution) I loaded the last version of Fastboot, but the problem is the same.
Please can you help me. What can i do? Many thanks for your help!
Should be connect the charger cable to the phone.
charger or computer
excuse me for bad english
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
bertl237 said:
No i use a data cable, debugging is on. I can copy data from my phone to PC or from PC to phone, but fastboot does not found my device.
Click to expand...
Click to collapse
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
krispin said:
And when you use adb to reboot to bootloader, what happen? Do you have "Minimal adb and fastboot tool" installed?
Click to expand...
Click to collapse
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
bertl237 said:
Sorry for my question, what´s the differents about adb and fastboot tool? I have install the last version of minimal adb and the fastboot tool, also the Windows driver for the phone. Debugging is on. I try to connect my phone about the fastboot terminal. When i try to set the phone into the bootloader mod with the fastboot terminal and the equivalent command, fastboot say´s "searching phone". My phone does not react.
Click to expand...
Click to collapse
So, you connect your phone, open minimal adb and fastboot too, run "adb devices", you see device id? If yes, run "adb reboot bootloader" . Phone shoult reboot to fastboot mode. Then run "fastboot devices" to see if it is connected properely.
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
bertl237 said:
i did it, like you described, but i see not my device id. Only the note "seach device"
Is it possible that TWRP is defect on my device? Is TWRP necessary for fastboot or only for root?
Click to expand...
Click to collapse
No, you should be able to use adb and fastboot with stock recovery.
After first adb command you shoult approve authorization on your phone.
Here is screenshot from minimal adb...
Phone must be in MTP mode.
And here is phone in fastboot
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
bertl237 said:
Many thanks for your help, now I m in my bootloader.
2 problems i had.
1. My daemon was not started correctly, i have not seen my device.
2. I used the wrong command. I started with fastboot, not with the command adb device. I tap „fastboot reboot-bootloader“,but the correct command is “adb reboot-bootlader“
Now i have seen my phone is unlocked, i hope i can root my android 6.
Click to expand...
Click to collapse
Just reboot to fastboot and flash surdu-petru version of TWRP recovery 3.0.2 with command "fastboot flash recovery xxxxx.img". And than reboot to recovery and flash supersu zip.

Fastboot driver problem on Windows XP

Windows XP SP3
Wileyfox Swift, Android 5.1.1, Cyanogen OS 12.1.1-YOG7DAS2FI
I need Fastboot to flash radio.img, because TWRP gives me black screen without it and I need TWRP to flash custom ROM (currently stuck with cyanogenmod recovery). I installed ADB, Fastboot and Drivers v1.3 (1.4.2 didn't work) from this thread. ADB can see my phone in USB debugging mode with adb devices command. Device manager shows my phone as "Wileyfox Composite ADB Interface" and unknown "MTP" in Other devices. I updated "MTP" device with "Wileyfox ADB Interface" driver as the only option it allowed me to choose. Fastboot can't see my phone in USB debugging mode as intended I suppose.
When I go to bootloader mode neither ADB or Fastboot can't see my phone with adb devices, fastboot devices or fastboot -i 0x2790 devices commands. Any other fastboot commands come back with <waiting for device>. Device manager shows my phone as unknown "Android" in Other devices and it's not letting me install drivers manually simply not giving it as an option (it says drivers are impossible to find), even tho I know it's there because I was able to force update another "unknown device" with it (it gave me the option of 3 Google Inc drivers: composite adb, adb and bootloader).
So how do I fix it? Or are there any ways to flash radio without fastboot? Any TWRP black screen fixes are also appretiated.

In fastboot mode, message "OTG NOT MOUNTED, File NOT FOUND"

I have used the SDK tools trying to root my M9.
Activated developper mode, OEM unlocking end usb debugging.
In bootloader mode I can use the command line "adb devices" and it list in terminal a number for the device.
If I do the same in fastboot mode ("adb devices" at command line) then it doesn't show any device number and keeps searching.
When in fastboot mode I got the following message:
SD MOUNTED
OTG NOT MOUNTED
File NOT FOUND
Can somebody help me to solve this issue pls!!
mgbeek68 said:
I have used the SDK tools trying to root my M9.
Activated developper mode, OEM unlocking end usb debugging.
In bootloader mode I can use the command line "adb devices" and it list in terminal a number for the device.
If I do the same in fastboot mode ("adb devices" at command line) then it doesn't show any device number and keeps searching.
When in fastboot mode I got the following message:
SD MOUNTED
OTG NOT MOUNTED
File NOT FOUND
Can somebody help me to solve this issue pls!!
Click to expand...
Click to collapse
Why don't you just install twrp using fastboot then flash magisk?

Categories

Resources