Develop Bugs

fastboot usb mode (device not found)

Ok I can use commands VIA fastboot when the phone is on. The problem is using commands when the phone is in bootloader. It says "fastboot usb" But when i am trying to use commands like :adb reboot" i get a " device not found " error
The device is Eng s off and ship s off
Tryed this with 3 computers with no luck
I have all the needed drivers.
And using commands in bootloader worked before.

you cannot use adb commads while in fastboot, not will your device show up with the "adb devices" command, you can only issue fastboot commands. so to reboot you must use the command "fastboot reboot" and to show your device you can use the command "fastboot devices"

AndroHero said:
you cannot use adb commads while in fastboot, not will your device show up with the "adb devices" command, you can only issue fastboot commands. so to reboot you must use the command "fastboot reboot" and to show your device you can use the command "fastboot devices"
Click to expand...
Click to collapse
K thnx .
One more thing
I have SU on (#) and i cant even use commands in terminal .. tried reboot command : not permited

primpower said:
K thnx .
One more thing
I have SU on (#) and i cant even use commands in terminal .. tried reboot command : not permited
Click to expand...
Click to collapse
are you using leedroid's rom? i had the same problem, when i used his rom, some of the permissions in /system/bin/ are wrong on his rom, they are rwsr-xr-x and they should be set to rwxr-xr-x, try using adb

AndroHero said:
are you using leedroid's rom? i had the same problem, when i used his rom, some of the permissions in /system/bin/ are wrong on his rom, they are rwsr-xr-x and they should be set to rwxr-xr-x, try using adb
Click to expand...
Click to collapse
I was using Leedroid, i f**** up and installed multiple .zip at once.... first "leedroidRom.zip" and then "theme" without rebooting between.
After that it stopped working ( I think )
I then wiped everything and installed Android Revolution 2.0.12..
"Terminal"
# Reboot
not permited!
About the question i asked earlier. So its not possible to use adb commands trough fastboot. only fastboot commands.
so i have to use : "fastboot flash" and "fastboot push" to execute commands ?

you cannot use the push command while in fastboot for the same reason you cannot use ADB commands, because at that moment android is not booted, you can use adb commands from recovery though
here are the fastboot commands i know of:
fastboot devices - fastboot devices will give you a list of devices connected to the computer. This is also a good way to make sure that your phone is actually connected to the computer.
fastboot reboot - this will reboot your phone normally
fastboot oem unlock - Dont think this works with the DHD
fastboot erase XXX - Will erase the partition XXX (such as userdata, cache) - mainly used for resetting phone and clearing userdata / factory settings.
fastboot flash XXX YYY - This will flash XXX partitionn with YYY image

Desire stuck on fastboot mode, cannot flash recovery

My desire is stuck on fastboot mode,
it is S-OFF
bravo pvt1 ship s-off
riff: 0.93.0001
microp-051d
radio-4.06.00.02_2
Made goldcard, but all the PB99IMG.zip I put on the sdcard are reported as INVALID.
try via fastboot, but I allways get the same error as it wasnt connected.
when I type: fastboot devices I get the device sn but not the $ to keep sending commands so every command I send reports the same error.
try the android flasher, nothing.
used the search button, read a lot but still cannot get the fastboot flash recovery recovery.img to work
run out of ideas, need some help please.

Please specify exactly which error is given when you execute "fastboot flash recovery recovery.img"(recovery.img being your recovery image).
Because if you've got fastboot commands working you should be able to flash.
Do your hboot say alpharev anywhere?

C:\Documents and Settings\Usuario>fastboot devices
HT05PPL02709 fastboot
C:\Documents and Settings\Usuario>cd\sdk
C:\sdk>cd android-sdk-windows
C:\sdk\android-sdk-windows>cd tools
C:\sdk\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4216 KB)...
FAILED (status malformed (1 bytes))
finished. total time: 0.000s
I read this means no proper comunication in fastboot.
it is the clockworkmod recovery and the RA recovery...
both give me the same error... I cannot use any fastboot commmands.
they all end as previously shown.
tryed android flasher 1.8.0, selected recovery.img.... got "could not find part of the path data\recovery.img"
everytime, with every recovery.img I use.
this is all the lines on the hboot screen:
BRAVO PVT1 SHIP S-OFF
RIFF: 0.93.0001
MICROP-051d
TOUCH PANEL-SYNT0101
RADIO-4.06.00.02_2
Aug 10 2010,17:52;10

You can flash a recovery with the following command over adb or terminal emulator if your s-off. I know cm7, amonra recovery and rmd recovery support this, others...probably.
su
flash_image recovery /sdcard/recovery.img
I use it all the time.
Sent from my HTC Desire using XDA App

it doesnt work because I am stuck on fastboot.
adb shell do not work for me.
is there anything I should do after "fastboot devices" command?
I am using a xtc clip created goldcard.
should I flash a new hboot or a new radio?

hugmax said:
it doesnt work because I am stuck on fastboot.
adb shell do not work for me.
is there anything I should do after "fastboot devices" command?
I am using a xtc clip created goldcard.
should I flash a new hboot or a new radio?
Click to expand...
Click to collapse
[enter]
fastboot flash radio radio.img [enter] {wait the ok message}
fastboot reboot-bootloader [enter] {wait the reboot}
fastboot flash recovery recovery.img [enter] {wait the ok message}
fastboot reboot-bootloader [enter] {unplug the cable and wait the reboot}
from the bootloader menu go into recovery and flash the rom u want
ensure the img file are in the same directory of fastboot.exe
how u got s-off? with alpharev or an xtc clip? the xtc clip doesn't give u fastboot flash commands i think, then u should try run revolutionary.io i think, after u can flash recovery etc

s-off via xtc-clip.
will try the commands... should I pick any radio.img?

hugmax said:
s-off via xtc-clip.
will try the commands... should I pick any radio.img?
Click to expand...
Click to collapse
first run revolutionary, it will give u a patched s-offed hboot..this hboot will allow commands like "fastboot flash..."
about the radio, u can use the latest in this thread (extract the img from the zip) be careful flashing it..wait it to finish..don't remove battery or something like that

if I run revolutionary all I get is "waiting for device"
D:\Docs\Celulares\htc\desire\revolutionary-0.4pre4>revolutionary
=============================================
| Revolutionary S-OFF & Recovery Tool 0.4pre4 |
=============================================
Brought to you by AlphaRev & unrEVOked.
Waiting for device...
Click to expand...
Click to collapse
if I am stuck on fastboot and xtc clip doesnt allow any fastboot command... and unrevoke/revolutionary dont recognize my fastboot device...
what am I suppose to do now?
I get FAILED(status malformed.... ) with every single fastboot command.

hugmax said:
if I run revolutionary all I get is "waiting for device"
Click to expand...
Click to collapse
uninstall htc synch at all, and other programs that can interferr
install this fastboot drivers
run revolutionary, plug the phone in fastboot mode

Have you try to unroot with a PB99IMG?
Sent from my rooted and s-offed HTC Desire.

andQlimax said:
uninstall htc synch at all, and other programs that can interferr
install this fastboot drivers
run revolutionary, plug the phone in fastboot mode
Click to expand...
Click to collapse
I installed the drivers, it says
Android Composite ADB Device
version 2.0.10.12
date: 11/08/2009
Shouldnt it says 3.0?
anyway... it didnt work... I will try to delete/uninstall everysingle htc driver in my pc or try on another fresh laptop with no htc drivers.

Again here,
new pc, Windows XP SP3 with no HTC/Android software.
Intalled the HTC 3.0 and the phone was not recognized
should I try on win7?
that is going to be my next test

follow up: tryed on win7, htc 3.0.0 drivers didnt work. phone is not recognized.
I know it was working fine... tryed to flash it and it died... resurrected with RIFF Box but cannot flashed with any firmware.

i tried to flash a new hboot with android flasher, but it just reboot and nothing happened.

did you check md5 sum btw? just with the error saying invalid and 1 byte...
So you can still access fastboot but cant flash? hmmm...
I would personally delete all your android sdk and redownload it all and set up adb fastboot again, it does sound like a driver problem

timothio said:
i tried to flash a new hboot with android flasher, but it just reboot and nothing happened.
Click to expand...
Click to collapse
What did you expect? Its requires few seconds to flash it..If u saw the success message and u see the new hboot on the bootloader screen, thats all

ok,
now I went to find a PB99IMG.zip with the same radio.
copied it to the sd
power on the phone
and I got this:
Uploaded with ImageShack.us
but it is just sitting there, waiting for something to happen?
I tryed to select something but it doesnt respond to anything... can it be that the touch screen is faulty? because it was working at the beginning.
I did redownload everything again.
java sdk and everything
it doesnt work with the htc 3.0 driver, only with 2.0

can't unroot/relock GNex - please help

I walked through the following steps to put the stock OS back on my device...
adb reboot bootloader
fastboot flash bootloader bootloader-toro-primekk15.img
fastboot reboot-bootloader
fastboot flash radio radio-toro-i515.ek02.img
fastboot reboot-bootloader
fastboot flash radio-cdma radio-cdma-toro-i515.ek05.img (Note: This one takes a couple minutes. Be patient)
fastboot reboot-bootloader
fastboot -w update image-mysid-icl53f.zip
I now have the stock OS loaded and can boot alright, unlocked. When I get back into the OS I turn debugging on and then head back to adb. I can browse to my device through the USB but get the following error when attaching to my device.
c:\android\android-sdk\platform-tools\adb shell
[email protected]:/ $ adb reboot bootloader
adb reboot bootloader
error: device not found
1|[email protected]:/ $
Further, if I run "fastboot devices" from my command prompt I get no devices returned.
What am I missing?? I need to get this device relocked to send back in for warranty quickly. I'm trying to get the device locked back up. Any help you can provide is appreciated!
Edit: Resolved now

nevermind... whew... figured it out.

Mark threads as solved and update first post with whats happening, so one doesnt waste time like i did.
No need to double post for that.

[Q] How to flash an hboot with fastboot/adb

Clockworkmod recovery doesn't work(only get a blank screen after I make my selection), and my phone wont boot. I'm trying to flash a rom via fastboot or adb.
I installed fastboot and adb using this guide:
fastboot adb guide
I downloaded htc sync to install the drivers.
I'm trying to follow this guide for flashing a new rom
xda flashing guide
when i try "fastboot -w" the command prompt returns "erasing 'userdata'... FAILED <remote: not allowed>"
it seems the sollution for this is posted here. but i don't know how to flash an hboot. Can anyone point me in the right direction? I've been searching and all i could find was fastboot commander, but when I try to flash a new Hboot or my recovery image it returns "flash FAILURE"

sombomb said:
Clockworkmod recovery doesn't work(only get a blank screen after I make my selection), and my phone wont boot. I'm trying to flash a rom via fastboot or adb.
I installed fastboot and adb using this guide:
fastboot adb guide
I downloaded htc sync to install the drivers.
I'm trying to follow this guide for flashing a new rom
xda flashing guide
when i try "fastboot -w" the command prompt returns "erasing 'userdata'... FAILED <remote: not allowed>"
it seems the sollution for this is posted here. but i don't know how to flash an hboot. Can anyone point me in the right direction? I've been searching and all i could find was fastboot commander, but when I try to flash a new Hboot or my recovery image it returns "flash FAILURE"
Click to expand...
Click to collapse
In clockwork use the trackball to select items, not the power button.
To use most fastboot commands you need an unlocked bootloader, or the engineering bootloader. To chanhe your bootloader you need to be s-off, or do an entire ruu.

cmlusco said:
In clockwork use the trackball to select items, not the power button.
To use most fastboot commands you need an unlocked bootloader, or the engineering bootloader. To chanhe your bootloader you need to be s-off, or do an entire ruu.
Click to expand...
Click to collapse
Wasn't using the trackball. This is embarrassing. Thanks for all the helpful info, you're awesome.

=X
wow this is funny, but sadly it helped me also

In case you'd still like to know how to do it via fastboot, here are some steps:
Place the .zip in the same directory as the adb and fastboot executables
Double check the md5 of the .zip before proceeding to prevent bricking the device
Run the following commands in command prompt:
fastboot devices //Verify that the device is detected
fastboot erase cache //Not sure if this is completely necessary, but the guide I followed included it as a step
fastboot oem rebootRUU //Boot into RUU, which lets you flash HBOOT, radio, etc.
fastboot flash zip [zipname.zip] //Replace zipname.zip with the actual name of the file you are flashing
fastboot reboot-bootloader //The guide I pulled this info from didn't specifically say that you should reboot to bootloader rather than to Android, but I have seen others mention that you should always reboot to the bootloader first after flashing an HBOOT or radio. I would do this just in case

thehiggins you saved the day

Thanks You
Didn't know I had to be in RUU. When do I need to be in RUU, when flashing the boot or any boot related img/zip ?

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"

Flashing to stock Android NPD90G from TWRP error: "remote: unsupported command"
Fixed flashing error "remote: unsupported command" when flashing a Pixel C back to stock
I used TWRP and SuperSU to root and modify the buildprops to enable and get an early look at the windowing in Android N beta on my Pixel C release 5 ahead of time.
When Release 5 NPD90G was available I decided to flash back to stock from Developer Preview 4 NPD56N rooted with SuperSU and flashed with TWRP. I like root - I run Ubuntu and Win 7. I don't mind running a rooted device if it doesn't have all my work and financial data. When the final N release is out, the Pixel C will become my work machine. It's almost there.
I'm naturally paranoid. I change my long passwords frequently and use 2 factor authentication for everything. So if I can, I'll take a stock release. See my instructions for wiping Android devices: How to wipe an Android Phone: the paranoid editon
I could not flash the NPD90G stock bootloader because of an error "remote: unsupported command"
Here's how I fixed it.
Updated the SDK manager including SDK Tools and USB drivers.
With the Pixel C in recovery mode, {hold the power key and volume down}
In TWRP mount System and reboot to recovery
>ADB Shell.
From ADB Shell I ran
>fwtool vbnv write dev_boot_fastboot_full_cap 1 to reenable Fast boot.
Then I changed from TWRP to Fastboot mode {power button plus hold the volume up button}
>fastboot erase userdata
>fastboot erase boot
>fastboot erase cache
>fastboot erase recovery
>fastboot erase system
See Note 1. Below
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
Note 1.
The first time through I flashed the following line items which resulted in the resting robot Andi. I don't think I needed to do this, but if the above instructions don't work, run the following before continuing for {flash bootloader bootloader-dragon-google_smaug.7900.27.0.img}
>flash bootloader bootloader-dragon-google_smaug.7900.27.0.img
>fastboot reboot-bootloader
>fastboot reboot-bootloader
>fastboot flash system system.img
>fastboot flash boot boot.img
>fastboot flash recovery recovery.img
>fastboot flash cache cache.img

Twrp can't flash
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command

Tugio said:
The problem is that I can't boot into the twrp because when i try to flash it the answer is failed unsupported remote command
Click to expand...
Click to collapse
When in fastboot mode, use:
Code:
fastboot boot twrp-local-file-on-computer.img

DanBUK said:
When in fastboot mode, use:
Click to expand...
Click to collapse
It's nice of you to help a fellow XDA user. But I suspect he's already solved his problem of three months ago.....

Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards

lllopa said:
Hi guys
I have the same problem:
- the bootloader is unlocked (Coreboot menu says so)
- fastboot says "secure: yes" but "unlocked: yes" too
- "fastboot flashing get_unlock_ability" returns "1"
- "fastboot flashing unlock" says that the bootloader is already unlocked
But I have no recovery and if I try to fastboot boot recovery.img it fails with signature verification error
Can I do something to unbrick the device?
Regards
Click to expand...
Click to collapse
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C

Make sure you have the latest version of fastboot and adb. I get these errors almost every month if I don't update.
https://developer.android.com/studio/releases/platform-tools.html

@stevep2007, thank you so much! I've been dealing with this "remote: unsupported command" nonsense for days now after trying to revert back to an older Oreo version of Lineage. This did the trick!

How can I solve the problem when my Pixel C is not unlocked? My Pixel made an update and after installing the Update I got the green little man. Now I have no Chance to activate USB debugging etc. Its also not possible to install twrp.img
How can I go to ADB shell with locked bootloader? Or isn't it possible?
Fastboot devices shows me my tablet. ADB devices also show my tablet with "sideload".
But every try to flash my Pixel fails. I alway get the message .... remote: unknown command.......fastboot error: command failed
flash-all.bat showes that all "*.img are missing" error: command failed... unknown command etc.......
So any idea to get my Pixel working again? ADB shell would make it I think. But how with locked bootloader.

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
This did it for me!! Thanks much. I also updated platform-tools at the same time, who knows which did it

_Arne_ said:
My solution is very simple:
fastboot flashing lock
fastboot flashing unlock
fastboot reboot
And now let it boot.... and wait.
After the (failed) reboot check again: Now you can write all partitions... worked with my Pixel C
Click to expand...
Click to collapse
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions

bernardomarx said:
In the scenario described by @llopa this solution does not work.
In that scenario there are no solutions
Click to expand...
Click to collapse
Sorry replied incorrectly