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
Related
Hi Guys,
I was facing some issues with Virtuous Infinity v1.33 so I decided to do a full wipe. Although after doing a full wipe, I accidently rebooted the device instead of flashing the ROM again. Now my volume down button is a little dodgy and doesn't come in handy if I have to boot into the Bootloader/Recovery.
Is there any alternative to this?
Any help is appreciated.
Edit: If I power the device on, I see the white screen with the HTC logo and then it goes to a blank screen with nothing but the backlight on. I can charge my device if it's off. Oh & i've done a format - system, boot, data, all partitions except SD card.
Thanks in advance!
Have you removed the battery for a sec and then tried going into hboot? Regardless of all your partitions hboot should always be accessible, unless it has been wiped or corrupted, sometimes only a battery pull will let you access hboot again. If you absolutely can't get into hboot because of a bad volume rocker then you could try adb shell, but getting the pc to read phone is going to be tricky. If you hold volume up and power I think it goes into fastboot with a black screen.
did you try to boot in recovery mode with adb?
http://www.crocko.com/18FF41A02AB045FB8E821F6A614DEF0A/fastboot.zip
extract zip, open command prompt, go to the extraction directory an type: "adb reboot recovery" while phone is connected to your PC.
Good luck!
Gizmoe said:
Have you removed the battery for a sec and then tried going into hboot? Regardless of all your partitions hboot should always be accessible, unless it has been wiped or corrupted, sometimes only a battery pull will let you access hboot again. If you absolutely can't get into hboot because of a bad volume rocker then you could try adb shell, but getting the pc to read phone is going to be tricky. If you hold volume up and power I think it goes into fastboot with a black screen.
Click to expand...
Click to collapse
kinggizmo said:
did you try to boot in recovery mode with adb?
http://www.crocko.com/18FF41A02AB045FB8E821F6A614DEF0A/fastboot.zip
extract zip, open command prompt, go to the extraction directory an type: "adb reboot recovery" while phone is connected to your PC.
Good luck!
Click to expand...
Click to collapse
Thanks guys! the battery trick did it. I will save that file for any future references though.
It was 2AM and I was bored out of my mind at work :silly: If i knew how to close this thread I would. This is solved.
Thanks again!! :good:
Thank God i found this thread,
With fastboot finally i can manage running my DHD again using Blackout ROM. Honestly this is my 1st time flashing DHD and quite long night i spent off, thankfully it's done very well at last
Thank you a lot for all thread's participants :good:
I rooted and installed an ICS ROM several months back on my Fire. One morning the wife brings it in and says my son got it stuck in some weird mode. Turns out it is stuck on the TWRP yellow triangle and does not seem to be able to get into recovery mode. I have done that several times before so I am pretty confident I am not messing that up. Just the power button never turns orange and eventually the device just turns off. My computer see the USB device but ADB does not. I did `android update adb` and then added '0x1949' to '~/.android/adb_usb.ini'. Do I have any options left or is it bricked?
Thank you to anyone who takes the time to read this. Especially to any who can reply with suggestions.
nnutter said:
I rooted and installed an ICS ROM several months back on my Fire. One morning the wife brings it in and says my son got it stuck in some weird mode. Turns out it is stuck on the TWRP yellow triangle and does not seem to be able to get into recovery mode. I have done that several times before so I am pretty confident I am not messing that up. Just the power button never turns orange and eventually the device just turns off. My computer see the USB device but ADB does not. I did `android update adb` and then added '0x1949' to '~/.android/adb_usb.ini'. Do I have any options left or is it bricked?
Thank you to anyone who takes the time to read this. Especially to any who can reply with suggestions.
Click to expand...
Click to collapse
Download TWRP and FFF1.4
TWRP
http://forum.xda-developers.com/showthread.php?t=1592681
FFF1.4
http://forum.xda-developers.com/showthread.php?t=1632375
ADB will not work because you're in fastboot mode. Use fastboot commands to install the new TWRP and change the bootmode.
Code:
fastboot flash recovery /path/to/recovery.img
fastboot oem idme bootmode 5001
Hold the power button to perform a hard shutdown and restart the device. You should then be able to launch recovery using the power button. If not, you'll have to flash the bootloader as well. If this is the case, be extremely careful you don't pull the USB cable during the flash or you will really brick your device.
Also, it is very important to know that the version of FFF you'll download comes in a .zip format to be flashed in recovery. Don not flash the .zip file directly to your bootloader partition. Instead, unzip it and find the "fff-u-boot_v1.4.bin" located in the cache folder and flash it.
Code:
fastboot flash bootloader /path/to/fff-u-boot_v1.4.bin
fastboot reboot
If you were able to access recovery just by reinstalling it with the first command, push the FFF1.4.zip file to your sdcard and flash it in recovery. Just remember not to wipe anything before installation. That will help you to fix your bootmode problems a lot easier in the future by holding the power button untill the boot options appear at the bottom.
soupmagnet said:
Download TWRP and FFF1.4
ADB will not work because you're in fastboot mode. Use fastboot commands to install the new TWRP and change the bootmode.
Code:
fastboot flash recovery /path/to/recovery.img
fastboot oem idme bootmode 5001
Hold the power button to perform a hard shutdown and restart the device. You should then be able to launch recovery using the power button.
Click to expand...
Click to collapse
Thank you! I am back in recovery!
I can't boot up my device it's have blink sleeping android error. (my device is ze551ml running WW_2.19.40.22 firmware and never ever ROOT!!! )
I tried hold power button and press volume up button but its doesn't work.
I also can't access to recovery mode too.
It's have the same blink error message and can't pass by hold power button and press volume up button.
Oh but i can access to fastboot page.
and my computer don't recognize my phone at all(i already install driver)
Before this problem happen I get in to recovery mode try to wipe cache but i miss press and i selected "apply update from adb"
and that time my phone doesn't connected with PC. I don't know what to do so I turn off my phone.
then I open recovery mode again and select wipe cache then I go out to take a bath.
I came back and see my phone is off so I boot it.
It's booting about 2-3 mins and nothing happen so i go to recovery mode again but this time they have problem like i explain before(blink error message that can't pass by hold power button and press volume up button)
So anyone have a solution for my problem. please I really need your help!
Sorry for my bad english
Hi,
I had this when I went to wipe my system cache and it failed. Your best bet, especially if you can't get into recovery is to fastboot flash the recovery again if you have an unlocked bootloader.
If you don't you'll want to unlcok the bootloader and follow the instructions for using ADB if you're new to it: http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596
How can I unlock my boot loader when i can't even open up my phone.
stultus136 said:
How can I unlock my boot loader when i can't even open up my phone.
Click to expand...
Click to collapse
If you hold volume down and power, it should go to bootloader first, then you have your choices for recovery....Get it to the bootloader screen, then run the commands to unlock it...
Could you please tell me everything step by step on how to cure my phone?
I'm very noob.
okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code
stultus136 said:
okay thank you.
I can start it now
THANKS!!!!!!!
p.s. i use fastboot erase cache code
Click to expand...
Click to collapse
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.
Same Problem
smokinjoe2122 said:
Glad you have it working...It seems that wiping the system cache can be problematic at times - Perhaps it's a bug.
Click to expand...
Click to collapse
Hey I'm having the same problem, how'd you get the computer to recognize that the phone was plugged in? My computer does not recognize that the phone is on when I have the flashing error screen, so ADB doesn't recognize that there is a device connected.
Hi,
I had the exact same problem, and I managed to boot up again thanks to you!
What I did :
Install ADB and Drivers
Boot my phone into Fastboot (Power+Volume Up at boot, keeping VolumeUp button pressed while booting). Don't go into any menu (do not select recovery or so). At this point your computer should recognize your Android phone when you plug it in through USB.
Open up a cmd with admin rights, navigate to adb install path by typing : cd C:\adb
Then type : fastboot erase cache
It should trigger an action on your device, and the prompt should display sth like "Cache successfully erased" (I don't remember exactly)
Finally type : fastboot reboot, press volume up while booting again, and access Recovery like usual!
Now you can try wiping your partition cache again.
Worked like a charm for me! Thanks a lot
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.
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'