my power button is broken and my phone powered off. i managed to get it into download mode by holding vol - and plugging into pc. i have adb set up, i just need some help with the commands.
i figured it out. let the phone die, charge a little, hold vol + and plug into a pc. it boots into a mode that you can use adb reboot with and voila.
From download you can do "fastboot reboot" in case you ever need again.
i tried fastboot reboot and it hung on "waiting for devise"
iateshaggy said:
i tried fastboot reboot and it hung on "waiting for devise"
Click to expand...
Click to collapse
You need to install HTC Drivers.
iateshaggy said:
i tried fastboot reboot and it hung on "waiting for devise"
Click to expand...
Click to collapse
Get the adb files too
random power downs has made for almost daily use of this foretold method and its getting a little old, would any of yall care to help me script a batch file that can run my commands.
cd C:\abd
adb reboot
Use htc_fastboot.exe. It is modified to work with later htc's.
my fastboot works, i just want to make a batch file so all i have to do is plug in my phone and double click the batch file to make my phone reboot.
Related
Does anybody know how to re-lock Galaxy Nexus without using fastboot ?
My computer recoqnize it as ADB however no matter how many times I install the driver it wont recoqnize it as fastboot.
The phone power button stop working and Google offer it to replace it.
However I need to re-lock the phone to send it back to them.
thanks
You need Fastboot. Are you putting the phone into Fastboot mode before you try?
If the phone is recognized by the PC and ADB works, then Fastboot should work just fine.
martonikaj said:
You need Fastboot. Are you putting the phone into Fastboot mode before you try?
If the phone is recognized by the PC and ADB works, then Fastboot should work just fine.
Click to expand...
Click to collapse
Yes the phone its in fastboot
since power button is not working, I press vol+ and - at the same time i put the battery on.
But the computer is not recoqnizing it.
I reinstall drivers and etc.
I have 2 galaxy nexus, the other one the computer recoqnize it.
ANy other idea how to put re-lock the bootloader without fastboot ?
hoodred said:
ANy other idea how to put re-lock the bootloader without fastboot ?
Click to expand...
Click to collapse
Has to use Fastboot.
Have you tried simply booting up normally and typing "adb reboot bootloader" and letting it enter Fastboot that way?
martonikaj said:
Has to use Fastboot.
Have you tried simply booting up normally and typing "adb reboot bootloader" and letting it enter Fastboot that way?
Click to expand...
Click to collapse
Yes,
It went to fast boot mode, the same like volume up+down and power. But the computer is not recoqnizing it. It recoqnize adb just not fast boot.
when i decide to change rom, after flashing kernel by fastboot and power on phone, I can't going to recovery by pressing volum down.
is there a command for fastboot to boot phone to recovery without pressing volum down?
Use adb i.e. adb reboot recovery
Many ways to do this...Easy wasy out,try an app like rom manager which gives u a direct recovery boot option,or u can use comand line prompts from ur PC ..or use terminal emulator..type in /system/bin/reboot recovery..
sinkster said:
Use adb i.e. adb reboot recovery
Click to expand...
Click to collapse
i connect phone in fastboot mode and use adb reboot recovery but not working! "error device not found"
Forgot, you can only be connected to adb if the phone's active or in recovery. When it's rebooting are you repeatedly pressing the buttons or holding them?
Hi, I am having a simlar issue. I flashed the Lupus kernel and after i turned of my phone, I pressed the volume down button while i turned the phone on and once it loads it just goes into safe mode. Am i doing something wrong?
EDIT: I was holding the button down. Not pressing repeatedly. All good now. Thanks.
amir143 said:
i connect phone in fastboot mode and use adb reboot recovery but not working! "error device not found"
Click to expand...
Click to collapse
flash again driver package in driver folder flashtools and select your device options
rod555 said:
flash again driver package in driver folder flashtools and select your device options
Click to expand...
Click to collapse
I do it but adb not working in fastboot mode
amir143 said:
I do it but adb not working in fastboot mode
Click to expand...
Click to collapse
try flashing CWM again ?
amir143 said:
I do it but adb not working in fastboot mode
Click to expand...
Click to collapse
your OS? Win7 x64?
Hi amir143!
You could try installing x-Parts (a free application from the market).
Good luck.
I thinks it's kernel dependent..
try pressing Vol-down OR backward button several times when the LED lights OR the phone vibrate OR the logo glow from normal after powered-on.
I recently tried to flash back from Lego Rom to stock ZVC and have hit some trouble. I used CWM to clear the caches/data, as per usual, but after installing the ZVC rom the phone just boot loops at the Lego Rom boot screen.
Normally, I would jump into recovery, but my volume buttons no longer work (they failed after a screen replacement, I suspect the ribbon cable is damaged). What are my options? Can ADB force it into recovery for me?
I've installed the latest USB drivers, but ADB is not recognizing any devices (at the ROM booting screen or at the charging/battery graphic). Do I have any options beyond buying a new volume button ribbon cable?
I have the same issue in windows and ubuntu. Will LGNPST be able to communicate with the device?
LordKyleOfEarth said:
I've installed the latest USB drivers, but ADB is not recognizing any devices (at the ROM booting screen or at the charging/battery graphic). Do I have any options beyond buying a new volume button ribbon cable?
I have the same issue in windows and ubuntu. Will LGNPST be able to communicate with the device?
Click to expand...
Click to collapse
well first of all yes you can reboot recovery using adb.
But if you installed the zvc rooted ROM then why is it booting Lego?
You can install philz or twrp for a full touch recovery and not need volume buttons. You'll still need to use cmd to do "adb reboot recovery" or adb reboot fastboot". You can also flash recovery from adb. Just get a recovery.IMG I think it's adb fastboot flash recovery.IMG or whatever the name of the recovery is.
But if ADB doesn't return any devices when I execute "ADB devices" how can I get it to send a reboot signal to the phone? When I tried "ADB reboot recovery" I was given an error about no device connected.
LordKyleOfEarth said:
But if ADB doesn't return any devices when I execute "ADB devices" how can I get it to send a reboot signal to the phone? When I tried "ADB reboot recovery" I was given an error about no device connected.
Click to expand...
Click to collapse
I must have not been thinking the whole picture. What can the phone do? What happens when you turn it on, do the volume buttons work at all? Because if you can get into recovery or fastboot at all then something can be done try multiple combinations as much as possible. I'm thinking hold the power button down and plug in USB. Wait for something to happen then let go of power. Does your computer ever recognize something is plugged in? Maybe during boot?
hey guys,
i was bored and flashed a .zip on my phone and now I'm no longer bored. Long story, short... I'm booted into the os (almost) with constant errors popping up. I can't get the power button down for 10 seconds to reboot phone and i want to get back to recovery to flash by back up. How can I use terminal (mac) to force back into recovery if phone is not in mode for adb to recognize phone?
Thanks in advance.
Try hold power button + volume up to force reboot. Once the screen goes black release those buttons and hold volume down button to go to hboot
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.
andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Otherwise, I guess I wait until power drain.
Click to expand...
Click to collapse
Power + Volume Up should work. But as you asked for adb/fastboot
1) "adb devices" to check if device is recognized
2) "abd reboot bootloader" so the phone reboots into bootloader
3) go to recovery and try a reflash
andason said:
Thanks for your reply. Seems the power + volume is not be recognized. Is there a way with fastboot or adb?
Click to expand...
Click to collapse
This should always work as long as the screen is on. It might take 10 seconds or more, so you may not be holding the buttons long enough.
Alternately, you can use:
adb reboot bootloader
or
adb reboot recovery
There is no required more for adb commands, as long as the screen is on. Fastboot on the other hand, requires the phone to be in fastboot mode.
What did you flash? Was it a ROM, and if so did you do a full wipe (data, cache and Dalvik) before flashing?
Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?
andason said:
Thanks for all the replies. It finally died and I was able to jump back into recovery. I was trying to flash a .zip (one+ one theme) to my rom and some things about it (audiofx) was not liked. I guess adb could not recognize the phone since it was basically booted into the os. I just thought there was a way to still use adb or fast boot to push it into recovery. I did not get to try adb reboot boot loader, but would adb recognize phone even with this command?
Click to expand...
Click to collapse
Glad it worked and that we could help a
adb reboot bootloader should be recognized nearly any time.
Sent from my HTC One_M8 using XDA Free mobile app
Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
elektrosoundwave said:
Hi people,
I unlocked, rooted, and flashed Liquid on my XL tonight. Everything seemed to be going fine when I rebooted again and got a bootloop. TWRP is not loading, what I am getting is the Android on it's back menu and here's where I'm lost. I'm getting the error in the screenshots when I try to sideload the factory image from ADB. My cords are good, drivers are updated, and I have ADB and Fastboot set to Large Address Aware. I don't want to admit that I have a paperweight now. Any ideas? Thanks in Advance
Click to expand...
Click to collapse
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
koivth said:
Can you reboot to download mode (fastboot)? Hold the power button and vol down buttons together.
If you can get into the bootloader, use fastboot to flash the factory image instead of using adb. Or try issuing 'adb reboot-bootloader' command to reboot to bootloader
Click to expand...
Click to collapse
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
elektrosoundwave said:
Both volume buttons? I've only done the power and down volume. I will try both of these when I get home tonight, or when I wake up. I stayed up until 6am working on this and did not get much sleep. I'm also going to uninstall and reinstall the Pixel driver. I don't remember off the top of my head if I installed it before or after I upgraded my laptop to Windows 10.
Click to expand...
Click to collapse
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
koivth said:
Sorry for being unclear. To get into the bootloader (where you can use the fastboot command to re-flash the factory image), you hold the Power Button and Volume Down buttons together (not volume up button). This is what your screen should look like if you successfully get to the bootloader: https://www.xda-developers.com/files/2016/10/CvqcEDHUsAA_EY4.jpg
If you see that screen, you're sitting good. Download the latest factory image (https://developers.google.com/android/images#marlin) and run the flash-all.bat (for windows) script to reflash your phone. You will have to have fastboot drivers installed on your computer for that to work.
If your device is recognized by adb (if you type 'adb devices' and it shows your device as the output) but you are having trouble getting to the bootloader, you can type in 'adb reboot-bootloader' to reboot your device into fastboot mode where you can flash the factory image. Hopefully that helps push you in the right direction. Your phone isn't bricked/lost forever if adb or fastboot recognizes your device and you can save it!
Click to expand...
Click to collapse
That's where that first screenshot came from. I will try the reboot bootloader tonight. They sort of recognize my phone, but I can't get them to flash anything. This isn't my first rodeo with borked phones, but I don't think I've had this much trouble since I placed the wrong boot animation on my Droid 4 many years ago.
:victory: :highfive: It's flashing right now. You don't know how much I appreciate it.
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Is your bootloader unlocked?
obsidianlycanthrope said:
Hi, thought I would jump in on this thread. I have the same issue, and I can get to the fastboot screen and device is recognised by adb with "fastboot devices". When I try to flash-all I get the message that the device must be unlocked. Any idea why mine in different? I just have stock recovery, maybe that is it. The device also will not boot into recovery, it just bootloops
Click to expand...
Click to collapse
Before you can flash the factory image, you have to unlock the bootloader by issuing this command first: 'fastboot flashing unlock'