For some reason i am unable to push the commands to my phone. Following this guide:
http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide
When I type adb fastboot devices it just displays syntax's that I can add to the command rather than doing what its suppose to.
Anyone?
Btw does radio become a concern with Nexus one? It was with the G1/Dream.
Follow the guide correctly. There is no "adb fastboot devices", you're not reading right. It's either "adb devices" in ADB mode, or "fastboot devices" in fastboot mode.
I tried to root my kindle through, http://forum.xda-developers.com/showthread.php?p=24128777 , but I got half way and got stuck at the fastboot mode. I don't have recovery or anything because it was a stock 6.3 kindle fire. Does anybody know how to get out of this? The adb isn't recognizing my device right now and I've tried hard resetting.
Any help would be appreciated!
Edit: Is the only way out of this is through a factory cable?
what means got half way ?
you switch to fastboot at a point - then adb commands are not recognized
only fastboot commands are recognized in fastboot mode
would try to issue:
fastboot -i 0x1949 getvar product - it should return "kindle"
if not check your drivers
if you got the drivers working resume with the above manual
about drivers:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6
Oh. Is that it? . So is it normal for the cmd command "adb devices" to not show the kindle device?
If so, that's a pretty big relief! And all I need to do is type that cmd?
you have a great manual here explaining how the kf works:
http://forum.xda-developers.com/showthread.php?t=1552547
furthermore this one could help you to understand how drivers/bootmode/commands correlate:
http://forum.xda-developers.com/attachment.php?attachmentid=943772&d=1331571368
I'm having a similar problem. I can boot into fastmode but when I try to reboot, it just seems to hang with a <waiting for device> message. I get the same <waiting for device> message if I do the fastboot -i 0x1949 getvar product command.
I am stuck in TWRP and if I hit reboot, the command prompt does return the info.
OK, it appears that the KF didn't update. It was just stuck in some weird boot loop or something. Maybe it was trying to update and couldn't for some reason? I am keeping all this info bookmarked in case something does happen though.
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
It sounds like you may not have the latest drivers for the Android SDK or ADB toolkit.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
When you are in bootloader, you can use fastboot commands.
RonaldusMagnus said:
I restarted my phone this evening, and when it booted up I got a "decryption unsuccessful" message. When that happens it appears my only option is to flash a factory image. So I download the most recent image, and when I get into the bootloader I see no option for fastboot.
When I'm in TWRP (3.0.2-0) I can see my phone listed in recovery or sideload when I run "adb devices" from my computer, but no devices are listed when the command is run while on the main bootloader screen.
Not sure if it matters at this point, but I had the 20160821 Pure Nexus build installed when this happened.
How do I get my phone into fastboot mode so I can flash the factory image?
Thanks so much for your help.
Click to expand...
Click to collapse
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
JustPlayingHard said:
When you are in bootloader, you can use fastboot commands.
Click to expand...
Click to collapse
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
RonaldusMagnus said:
So, if I'm at the bootloader's main screen, I should be able to see my device when I run the command "adb fastboot devices", right? Cuz that's not happening. Also, when I use the volume rocker to see the available options fastboot isn't listed.
When I go into recovery from the bootloader and run the command "adb devices" I see my device listed with "recovery" next to it. When I launch ADB sideload from TWRP, I also see my device listed with "sideload" next to it.
So, I can run fastboot commands when I'm in the bootloader even if "adb fastboot devices" returns nothing?
Click to expand...
Click to collapse
It's not adb fastboot.. It's just fastboot.
teh roxxorz said:
Not sure what you're talking about. Turn the phone off. Hold vol down + power, to boot into the bootloader / fastboot.
Run the fastboot devices command, and you should see your device. That's where you can flash your system images.
Click to expand...
Click to collapse
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
RonaldusMagnus said:
The problem I have is that when I'm in the bootloader (at the screen with the android robot on its back) and use the volume rocker to see the available options, fastboot isn't listed as an option to select.
Sent from my FIND7 using XDA-Developers mobile app
Click to expand...
Click to collapse
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
JustPlayingHard said:
It's literally, stay in bootloader
type: "fastboot devices" and you should see your device.
Click to expand...
Click to collapse
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
No worries, it's probably me that's being dense.
That should work fine
RonaldusMagnus said:
Thanks. I'll do as you said and report back. Maybe what I'm doing wrong is recalling the bootloader unlock procedures where "adb" precedes some of the commands when executing them from the Windows command prompt.
Just to be ridiculously clear it's:
1. While unplugged, Power + Volume Down to enter the bootloader.
2. Once in the bootloader connect USB cable.
3. Navigate to the SDK platform-tools folder, and from the Windows command prompt execute "fastboot devices". Then I should see my device listed.
Sorry if I'm being dense.
Click to expand...
Click to collapse
or plug your phone in (while its booted normally, into its OS)
type: adb reboot bootloader
once phone reboots to bootloader, type: fastboot devices
He must have came from a HTC bc he's looking for the option Fastboot in Bootloader.
Sent from my Nexus 6P using Tapatalk
Thanks for your help everyone. I'm back up and running now. My problems stemmed from a misunderstanding that once in the bootloader I'm already able to execute fastboot commands and didn't need to select a fastboot option from the bootloader. And I had a misunderstood how to execute the fastboot commands from the command prompt.
Many thanks to everyone setting me straight!
Hi,
I'm using moto g4 plus xt1643 with RR Custom ROM.
When i restart/Power ON/OFF my device it automatically goes into fast boot mode every time. at that time i have to press start for booting my device. Every time doing this task is getting irritation. Kindly anyone help me to fix this
Except this issue my device is working smoothly.
Thanks in advance.
Kind Regards
Kranthi Kanapala.
What happens if you connect your phone to your PC whilst in fastboot mode, open ADB (and use the command 'fastboot devices' to check if your device is detected), and in ADB run the command 'fastboot oem fb_mode_clear' (without quotation marks)? This command, as I understand it, should clear fastboot mode and permit you to boot properly.
echo92 said:
What happens if you connect your phone to your PC whilst in fastboot mode, open ADB (and use the command 'fastboot devices' to check if your device is detected), and in ADB run the command 'fastboot oem fb_mode_clear' (without quotation marks)? This command, as I understand it, should clear fastboot mode and permit you to boot properly.
Click to expand...
Click to collapse
Thanks you friend.... Its working
hi,
after apply update (5.2) on my shield tv 16Gb i've got some problems:
the option " enable usb" under storage is quickly hide when open menu and when i want open some menu or apps the shield tv turn-off and reboot...
So i'm tryingto do recovery with a official IMG. the command ADB DEVICES working good.When send "adb reboot bootloader" the shield restart on the bootloader .But it seem loosing the connection with PC.
the command "fastboot devices" and the CMD is waiting for a device... no more devices attached.
Someone can help me?
thanks:good: