Develop Bugs

[Q] Command line troubles

I'm trying to manually install the 4.2 update. My GNex is stock 4.1.2 and my computer is running Windows 8 Pro. The problem is that when the phone is on, I can type in "adb devices" and it see my device, but when I get into recovery and to the point where it tells me to sideload, I type in "adb devices" and my device is no longer detected. Any ideas for a solution? Thanks!

aaronmcd1214 said:
I'm trying to manually install the 4.2 update. My GNex is stock 4.1.2 and my computer is running Windows 8 Pro. The problem is that when the phone is on, I can type in "adb devices" and it see my device, but when I get into recovery and to the point where it tells me to sideload, I type in "adb devices" and my device is no longer detected. Any ideas for a solution? Thanks!
Click to expand...
Click to collapse
You need other drivers for fastboot I believe, check for info in one of the stickies in this section.
Swype'ed on my CM10 Galaxy Nexus

I uninstalled all the drivers and stuff that I had and reinstalled all the ones I could find and I'm still having issues. I've been able to root and unlock and all that before but for some reason it doesn't want to see it with stock recovery. I'm too impatient to wait for the OTA! lol

you need to re-install (manually, through device manager or whatever) the same drivers again, when device is in recovery

OK so I reboot into recovery and then just install drivers like I did the first time or are they different drivers?
Sent from my Galaxy Nexus using xda premium

Ok so I got the drivers reinstalled and the device is recognized but now when I enter "adb sideload e587de13bf8a.signed-takju-JOP40C-from-JZO54K.e587de13" it just gives me the help menu....

NVM guys, tried the "clear data and force stop" trick and got it the first time

First make sure you extract adb from the latest SDK distribution because older adb versions did not support the sideload command. (I also had to do this to run sideload.)
Second, if you use stock recovery, make sure you select "update from adb" from the menu before issuing the adb sideload command on your computer.
Sent from my Galaxy Nexus using Tapatalk 2

I might have had an older version of adb. I didn't think of that. Oh well, I was able to force the OTA by clearing and stopping the framework app so all is well. Thanks for the help!
Sent from my Galaxy Nexus using xda premium

[Q] Fastboot cannot find device (Ubuntu/Win7)

Ok, I *have* searched the forums and googled this, but none of the standard solutions seem to work.
I have the Verizon HTC One and successfully ran the rumrunner S-OFF (root, unlocked, etc). Now I want to flash a recovery using fastboot, but no matter what I do, I cannot get "fastboot devices" to show anything (or I get <waiting for device> if I try anything else with fastboot). ADB works fine.
On Ubuntu 11.10:
I downloaded the back-ported android-tools (apt-get install android-tools-fastboot/adb from the ppa:nilarimogard/webupd8 repository).
I tried fastboot as root, and I also tried with a udev rule (SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", MODE="0666").
adb works fine (I used it to reboot in fastboot-usb mode)
I tried different USB ports.
On Windows 7:
I tried both fastboot from the Android SDK and from the "Minimal Tools".
ADB works fine.
I un-installed and re-installed drivers as I plugged in and unplugged my phone into the USB ports.
Note that Windows 7 does complain about the drivers and says that the device is unplugged when it isn't. It seems to timeout when trying to install drivers from the internet
I tried installing and uninstalling HTC Sync, PDANet.
I would prefer if there is a way to make it work in Ubuntu so that I can eliminate the Windows drivers from the equation. Anything obvious that I missed? Does the version of fastboot matter?
Thanks in advance for any suggestions.

neutrino37 said:
Ok, I *have* searched the forums and googled this, but none of the standard solutions seem to work.
I have the Verizon HTC One and successfully ran the rumrunner S-OFF (root, unlocked, etc). Now I want to flash a recovery using fastboot, but no matter what I do, I cannot get "fastboot devices" to show anything (or I get <waiting for device> if I try anything else with fastboot). ADB works fine.
On Ubuntu 11.10:
I downloaded the back-ported android-tools (apt-get install android-tools-fastboot/adb from the ppa:nilarimogard/webupd8 repository).
I tried fastboot as root, and I also tried with a udev rule (SUBSYSTEMS=="usb", ATTRS{idVendor}=="0bb4", MODE="0666").
adb works fine (I used it to reboot in fastboot-usb mode)
I tried different USB ports.
On Windows 7:
I tried both fastboot from the Android SDK and from the "Minimal Tools".
ADB works fine.
I un-installed and re-installed drivers as I plugged in and unplugged my phone into the USB ports.
Note that Windows 7 does complain about the drivers and says that the device is unplugged when it isn't. It seems to timeout when trying to install drivers from the internet
I tried installing and uninstalling HTC Sync, PDANet.
I would prefer if there is a way to make it work in Ubuntu so that I can eliminate the Windows drivers from the equation. Anything obvious that I missed? Does the version of fastboot matter?
Thanks in advance for any suggestions.
Click to expand...
Click to collapse
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.

Do you have Fastboot turned off in system settings?
Unless I'm mistaken, you need to be sure that's switched off to utilize fastboot mode.
If it's already switched off and you are still having the issue, then ignore this post.

santod040 said:
Do you have Fastboot turned off in system settings?
Unless I'm mistaken, you need to be sure that's switched off to utilize fastboot mode.
If it's already switched off and you are still having the issue, then ignore this post.
Click to expand...
Click to collapse
I have fastboot checked in settings and fastboot commands work... When I'm in fastboot mode.
OP, I have made the simple mistake of not putting it in fastboot mode before. Were you booted into fastboot mode? I.E. reboot into bootloader, with fastboot selected hit the power button and ensure that it says deadbolt at the top? Something really simple that had tripped me up before!
Sent from my HTC6500LVW using XDA Premium 4 mobile app

This is worth a shot, as I've read in previous post. Only plug your HTC One into a usb 2.0 instead of 3.0. What does this mean? If you look inside the usb on your computer and the color you see is blue? Don't use that one. For whatever reason, when using the commands, usb 3.0 doesn't work with the HTC One. If you only have the 3.0 ports... I have nothing.

BygSii said:
This is worth a shot, as I've read in previous post. Only plug your HTC One into a usb 2.0 instead of 3.0. What does this mean? If you look inside the usb on your computer and the color you see is blue? Don't use that one. For whatever reason, when using the commands, usb 3.0 doesn't work with the HTC One. If you only have the 3.0 ports... I have nothing.
Click to expand...
Click to collapse
ADB works fine over USB 3.0 for any Android device if you have the proper drivers installed. If you have a mixture of 2.0 and 3.0 ports, as I do, use the 2.0, as it is more reliable, though slower. I'm using ADB on my device via USB 3.0 as I type this, using Windows 7 x64.
If your motherboard has an Intel chipset, you can try this method to get Fastboot working over USB 3.0, just disregard the download links about making it work on Windows 8, as the drivers were designed for Windows 7. My motherboard has an Asmedia USB 3.0 controller, and I am unable to use the Intel drivers, and thus unable to use Fastboot over USB 3.0, which isn't really a problem for me, as I also have the USB 2.0 ports.

brymaster5000 said:
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.
Click to expand...
Click to collapse
Oh, you mean directly on the phone? Presumably one could do it from "adb shell" as well? I would be interested to know what the commands are, since typing fastboot in the terminal emulator is not recognized.
[edit]
I found this in the forums:
Code:
su
flash_image recovery path_to_recovery_image.img
I assume that is what you meant.

kdj67f said:
I have fastboot checked in settings and fastboot commands work... When I'm in fastboot mode.
OP, I have made the simple mistake of not putting it in fastboot mode before. Were you booted into fastboot mode? I.E. reboot into bootloader, with fastboot selected hit the power button and ensure that it says deadbolt at the top? Something really simple that had tripped me up before!
Sent from my HTC6500LVW using XDA Premium 4 mobile app
Click to expand...
Click to collapse
So just to be patently clear. To boot into fastboot, I reboot into the bootloader with USB attached, select "fastboot", then it says "fastboot USB" and I select "Reboot", correct? I have never noticed the word "deadbolt". Is there a way to check on the phone that I've booted into fastboot?
I have been using USB 2 ports (tried different ones).
I have fast boot unchecked in my settings.

neutrino37 said:
So just to be patently clear. To boot into fastboot, I reboot into the bootloader with USB attached, select "fastboot", then it says "fastboot USB" and I select "Reboot", correct? I have never noticed the word "deadbolt". Is there a way to check on the phone that I've booted into fastboot?
I have been using USB 2 ports (tried different ones).
I have fast boot unchecked in my settings.
Click to expand...
Click to collapse
Don't click reboot once your phone says "Fastboot USB". That's where you're going wrong.
You say that ADB works on occasion. Trying downloading the newest drivers from this thread. Plug your phone in and type "adb devices". If it displays your phone's serial number and says "device" next to it, you're doing fine. Then type "adb reboot bootloader". It will bring you to where you are able to type fastboot commands. Type "fastboot devices". If it shows your device's serial number and says "fastboot" next to it, then your Fastboot commands will work properly.

neutrino37 said:
Oh, you mean directly on the phone? Presumably one could do it from "adb shell" as well? I would be interested to know what the commands are, since typing fastboot in the terminal emulator is not recognized.
[edit]
I found this in the forums:
Code:
su
flash_image recovery path_to_recovery_image.img
I assume that is what you meant.
Click to expand...
Click to collapse
Open a terminal emulator on your phone then get root access:
su
After that, cd to the location of the .img file: (i.e. if it was on the root of the sd card then...)
cd /sdcard/
Finally, flash the image to the recovery partition:
dd if=recovery.img of=/dev/block/mmcblk0p21 (not sure if this location will be different on this phone..someone else may want to chime in)
Then exit the terminal emulator and reboot.

IceDragon59 said:
Don't click reboot once your phone says "Fastboot USB". That's where you're going wrong.
You say that ADB works on occasion. Trying downloading the newest drivers from this thread. Plug your phone in and type "adb devices". If it displays your phone's serial number and says "device" next to it, you're doing fine. Then type "adb reboot bootloader". It will bring you to where you are able to type fastboot commands. Type "fastboot devices". If it shows your device's serial number and says "fastboot" next to it, then your Fastboot commands will work properly.
Click to expand...
Click to collapse
Thanks, not clicking the reboot made it work with fastboot (even in Win7!). I was confused by the statements about rebooting "into fastboot" and assuming that once it displayed "fastboot USB" I should reboot. Took me 2 seconds to install TWRP once this PEBKAC was resolved .
I would've tried the dd option from the terminal, but I'm glad I didn't have to (have used that wrong once on a Linux system and it was not pleasant!).

Glad you figured it out, even with my typo!
Sent from my HTC6500LVW using XDA Premium 4 mobile app

Commands
brymaster5000 said:
You can run a fastboot command from terminal emulator. If you can't find the commands, I will send them when I get to a computer tomorrow.
Sent from my One.
Click to expand...
Click to collapse
Hi, I have been trying to debrick my tp and I've posted in forums asking basically this question.. seems it goes fine till failed to install/find Fastboot.. would you send me the command? thanks..

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.

Stuck at google splash screen, ADB doesn't list devices with "ADB Devices" command

Stuck at google splash screen, ADB doesn't list devices with "ADB Devices" command
I was using Masgisk. I followed the steps from masgisk to restore before i took the OTA. The ota moved to step 2 but then restarted. Now i am stuck at the splash screen. I can get reboot to the bootloader but after I lauch my CMD from the platform tools window and use the command "ADB Devices" nothing is listed. I don't remember enabling usb debugging prior to this. Is there anything i can do to flash something that will not erase my data. If not is there any way i can flash the factory image?

angelino0919 said:
I was using Masgisk. I followed the steps from masgisk to restore before i took the OTA. The ota moved to step 2 but then restarted. Now i am stuck at the splash screen. I can get reboot to the bootloader but after I lauch my CMD from the platform tools window and use the command "ADB Devices" nothing is listed. I don't remember enabling usb debugging prior to this. Is there anything i can do to flash something that will not erase my data. If not is there any way i can flash the factory image?
Click to expand...
Click to collapse
Is your bootloader "fully" unlocked?? Have you tried side loading the OTA? It will not wipe data. From bootloader mode, type in fastboot devices to see if you get your phone ID displayed. The USB debugging part is what's worrying me though! Is OEM unlocking checked off in developer options at least??

Badger50 said:
Is your bootloader "fully" unlocked?? Have you tried side loading the OTA? It will not wipe data. From bootloader mode, type in fastboot devices to see if you get your phone ID displayed. The USB debugging part is what's worrying me though! Is OEM unlocking checked off in developer options at least??
Click to expand...
Click to collapse
Thank you for your reply, yes device state is unlocked and when I use fastboot devices I see something but not when I use adb devices
Edit: I was able to restore the factory image thank you though

Fastboot interface is missing. Help!

On Device Manager (Window 10). Were updating the driver, I can only see ADB interface but no Fastboot interface. I'm on the latest version SDK from Google and have OnePlus driver installed. I can command ADB but not fastboot. What am I missing? My device is OnePlus 7T TMobile is sim unlocked and I can toggle OEM unlocking and is on.

Not sure what mean, but fastboot only works when you're booted in bootloader. (Adb reboot bootloader)
Sent from my OnePlus7TPro using XDA Labs

That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.

PesTicide. said:
That's correct but when I fastboot cmd it get stuck on "waiting for device". So I read around on XDA on how to fix it and I tried to follow the instruction on PC - device manager, still no go.
Click to expand...
Click to collapse
I myself have never had this problem, I can only suggestion reinstalling OnePlus drivers.
Hopefully you figure this out
Sent from my OnePlus7TPro using XDA Labs

I reinstalled couple of times. Still no go! This is the first time that this happening. Never had problem since day one on Nexus devices. I'm going to try again and search more around.

You can also use the universal drivers by clockworkmod https://adb.clockworkmod.com/
Here's what I did.
1) Extract the android sdk platform tools and put on your c:// drive
2) Install the universal usb drivers
3) Enable usb debugging on your one plus and connect to computer. Switch to usb debugging mode and accept the popup on your one plus to allow the connection.
4) Open cmd and run "cd C:\platform-tools", then run "adb devices" to ensure that your devices is connected properly
5) Run "reboot bootloader" and device will restart into bootloader mode and fastboot will now work
*This is all assuming that you've already oem unlocked your devices as well already*

It work till fastboot. Still stuck at "waiting for device".

PesTicide. said:
It work till fastboot. Still stuck at "waiting for device".
Click to expand...
Click to collapse
Are you trying to open? Command shell? In windows 10 right? So for your information in windows 10 it's not supported , you have to open that platform tool folder which you installed already named as adb, platform tools , sdk may go into that folder and you will see a folders directory above there .. just click on that and type cmd and hit enter and cmd will pop up now you can use all your commands it's not your fault it's windows 10 fault ..maybe hope it may work for you

That how I done it. Fastboot Command appear on my Google Pixel 2 and 3 but I can't do it on my 7T. I don't get it
Thanks for the help! I tried working on Device Manager on PC yet doesn't work. Adb shell command work but no Fastboot command.

I found the solution! This is what I did and it worked for me! Here's the link for anyone who has the same issue I went through. Here you go and follow the instruction. http://www.wtfandroid.com/fix-fastboot-device-not-recognised-problem/
Mod you can close this thread. Thanks again for everyone who tried to help me. :highfive: