OK, so I;m trying to install the new Android M developer preveiw on my Sony Xperia Z3 Compact. I followed all of Sony's instructions and even installed Ubuntu on my Surface Pro to do it. Created the build and now, Fastboot doesn't work. It just says < Waiting for Device >.
So before anyone asks, USB Debugging is enabled and the device is recognized under adb. I don't see the device under fastboot devices, although the device IS in Fastboot mode. Any ideas?
Try to run the fastboot command as root, also sudo ./fastboot
That worked for me
Sent from my GT-I9100 using XDA Free mobile app
Related
I am trying to unlock my device and keep having the problem of it not being recognized in fastboot.
I have the latest drivers from the android SDK (4.0), and have trying reinstalling them. It appears to mount fine, and all of the adb commands work. However, when I try fastboot devices, it returns nothing. fastboot oem unlock only gives a "waiting for device".
Any ideas?
Thanks
Device needs to be in the fastboot screen of the bootloader...
Sent from my Nexus One using XDA App
While I feel really stupid for somehow missing that fact in dozens of threads, it doesn't seem to fix the problem. I now have it in fastboot and at the top is says "FASTBOOT USB". Windows recognizes the device when its plugged in, but still no luck with devices.
Nevermind, I figured it out. It downloaded fastboot from another source. I am guessing that I was somehow missing a file. Thanks though.
Hi there,
I have a new KFHD 7" with bootloader version 7.4.9, which I tried to put a custom ROM with the How-To from the Cyanogen website (Install_CM_for_tate).
I have a fastboot cable and everything went fine, after flashing the files, the device started TWRP. I pushed the CyanogenMod and Gapps over, which completed successfully and then back-upped as recommended.
After that, I was asked if I wanted it to install SU which I accepted. In the next reboot, I got into a bootloop with the kindle logo not turning blue anymore.
I tried to reflash, but that resulted also in a bootloop without getting into TWRP.
Any ideas what I should try next? Thanks!
3rd gen.
2012
Tate-PVT-08
thatissounfair said:
Hi there,
I have a new KFHD 7" with bootloader version 7.4.9, which I tried to put a custom ROM with the How-To from the Cyanogen website (Install_CM_for_tate).
I have a fastboot cable and everything went fine, after flashing the files, the device started TWRP. I pushed the CyanogenMod and Gapps over, which completed successfully and then back-upped as recommended.
After that, I was asked if I wanted it to install SU which I accepted. In the next reboot, I got into a bootloop with the kindle logo not turning blue anymore.
I tried to reflash, but that resulted also in a bootloop without getting into TWRP.
Any ideas what I should try next? Thanks!
3rd gen.
2012
Tate-PVT-08
Click to expand...
Click to collapse
Use the KFHD system restore tool. Make sure it's for the 7" tablet. You'll need a fastboot cord to restore.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
Use the KFHD system restore tool. Make sure it's for the 7" tablet. You'll need a fastboot cord to restore.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Thanks for your reply!
I tried following the instructions from Thread 1951254.
Problem is, I plugged in the fastboot cable, the Kindle shows the fastboot logo, I enter
Code:
adb shell su -c "reboot bootloader"
and get
Code:
error: device not found
When entering
Code:
fastboot -i 0x1949 getvar product
the product type is printed.
I thought adb commands don't work in fastboot mode?
Is it maybe the Kindle boot version that I have? I think it was 7.4.9...
Adb takes adb commands.
Fastboot takes fastboot commands.
There is no need to issue a reboot command because you are already in bootloader mode (fastboot).
thatissounfair said:
Thanks for your reply!
I tried following the instructions from Thread 1951254.
Problem is, I plugged in the fastboot cable, the Kindle shows the fastboot logo, I enter
Code:
adb shell su -c "reboot bootloader"
and get
Code:
error: device not found
When entering
Code:
fastboot -i 0x1949 getvar product
the product type is printed.
I thought adb commands don't work in fastboot mode?
Is it maybe the Kindle boot version that I have? I think it was 7.4.9...
Click to expand...
Click to collapse
The ADB commands are there in case you still have access to your OS and root. That's when this can be done with a regular USB cord. You don't have that so use your fastboot cord to enter fastboot automatically (should.) Run the bat and choose option 3.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
LinearEquation said:
The ADB commands are there in case you still have access to your OS and root. That's when this can be done with a regular USB cord. You don't have that so use your fastboot cord to enter fastboot automatically (should.) Run the bat and choose option 3.
Sent from my Nexus 7 Flo running Paranoid Android 4.4.4 using XDA premium 4 mobile app
Click to expand...
Click to collapse
Awesome, it worked!! Thanks for the explanation too, very helpful!
I would like to retry the flashing. Any recommendations or tips I need to follow?
Got it, thanks everyone!!
thatissounfair said:
Awesome, it worked!! Thanks for the explanation too, very helpful!
I would like to retry the flashing. Any recommendations or tips I need to follow?
Click to expand...
Click to collapse
If you want the 2nd bootloader and TWRP,use FireFlash or Flasher or flash them manually
Sent from my device running CyanogenMod 11
Hello everyone. I want to install CyanogenMod to my Sony Xperia SP 12.1.A.1.205.
I already unlocked the bootloader, I already rooted it, and even my PC (using Linux) detects it, but I just can't get fastboot to recognize the device. If I type in the command line
Code:
adb devices
CB51240CAW device
But if I try to do fastboot flash boot boot.img to install CyanogenMod I always get "Waiting for device". If I type fastboot devices I get no response (of course I restart my phone holding volume up to fastboot).
Is it even possible that my PC recognize my device using adb but not using fastboot?
Thank you in advance.
Nevermind, I did it in Windows 8.1 following this:http://forum.xda-developers.com/showthread.php?t=2588979
bbabel said:
Nevermind, I did it in Windows 8.1 following this:http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
U can install the fastboot drivers on windows 8 or 8.1 by signing off of the drivers in advance reboot of the PC.:good:
Little help Please guys, i have been trying to unlock the bootloader and install TWRP on my G watch R all day now, the problem is adb recognises my watch is plugged in and i can execut "adb reboot bootloader" however once the watch is in fastboot mode it no longer shows up as a connected device in adb, as a result when i try to execute "fastboot oem unlock"
the command window just hangs on "waiting for device" and never does anything.
i have tried updating all of my drivers and restarting pc, watch etc but i am getting nowhere.
debugging is enabled and i am running stock android 5.1.1
any help is appreciated.
thanks
I think you need to install the drivers while the device is in the boot loader, but I'm not sure
There aren't separate drivers for boot loader mode are there ?
Sent from my HTC One_M8 using XDA Free mobile app
Sorted it, not sure why but the version of fastboot I was using didn't work with the watch, used the minimal adb and fastboot of here and jt worked straight away
Sent from my HTC One_M8 using XDA Free mobile app
Has anyone tried using adb fastboot on Samsung Galaxy Note 8 recently.
I have tried unsuccessfully to get the fastboot work using Windows and Macbook with the latest Samsung Samsung drivers for fastboot. Even installed the fastboot drivers from Android Development platform but still no luck beyond <waiting for device>.
I read on another forum that Samsung no longer allows fastboot to work with their devices. Is it correct?
Fastboot as I understand it is an extension of Android recovery.
If you have USB Debugging enabled on your device, you should be able to issue commands: adb reboot fastboot
Fastboot commands also work in bootloader.
@V0latyle
Thanks for your reply.
I have USB debugging enabled alongwith the unlocked bootloader, as my device is rooted.
Recently, I was trying to use adb fastboot to flash boot image file of my Samsung device. However, it kept displaying <waiting for device> .
I tried the same command from my MacBook using Android platform tools, but result was still the same.
All adb commands work very well on Windows and MacBook without any hiccups.
Prof_Shekhar said:
@V0latyle
Thanks for your reply.
I have USB debugging enabled alongwith the unlocked bootloader, as my device is rooted.
Recently, I was trying to use adb fastboot to flash boot image file of my Samsung device. However, it kept displaying <waiting for device> .
I tried the same command from my MacBook using Android platform tools, but result was still the same.
All adb commands work very well on Windows and MacBook without any hiccups.
Click to expand...
Click to collapse
The appropriate command to flash /boot would be:
Code:
fastboot flash boot <boot image>