My humble apologies if this has been answered elsewhere, but I've searched extensively and found nothing.
I have CWM installed, and am able to boot into recovery just fine from within the Atrix UI (the system recovery app). But when I try to boot into recovery using the volume down key, it gives me the infamous white triangle and orange exclamation point, but that's confusing to me because clearly i DO have a recovery installed.
I've tried reinstalling it a number of times, and it always says it's successful, but still can only enter recovery from within the UI. Any ideas?
with phone off -> remove battery -> plug in charger (WALL OUTLET, NOT USB) -> replace battery
the phone should now automatically boot into recovery
you have to boot either from the bootstrap app or from the method above (plug in wall charger and poweron), you dont do it via hardware buttons anymore.
Related
Months ago I flashed a Modaco custom ROM to my friend's San Francisco. There haven't been any problems of late, however today I attempted to flash a Froyo build so he can try out C2DM apps like Beejive and Facebook and I was unable to load up a recovery screen. When holding Vol DOWN and booting I just got a white rectangle with FTM inside it - indicating that there was no recovery image installed.
I tried flashing Clockwork Recovery with the ZTE Blade Recovery Manager 2.9 but it kept saying 'Unrecognised' after selecting the .img file, no matter which one I used or whether I changed the name or screamed 'hail Mary'. I attempted multiple reinstalls to no avail.
The device is rooted so I tried using Terminal from the Android Market and flashing the recovery image but although it didn't come up with any errors I was still unable to boot into the recovery image. All it does now is show a green android the same as it would if pressing VOL UP when booting.
I've even tried installing with fastboot for mac, but despite being able to input the necessary commands, fastboot doesn't flash the device and just sticks at 'waiting for device' when the recovery flash command is executed. I've tried connecting the device a number of times, rebooting etc. I have no other USB ports available and no access to a Windows pc at present.
Can anyone assist here? The phone still works fine with the Modaco ROM but it's a bit annoying if that's all he will ever be able to use now!
Thanks in advance.
Japanese_Jellyfish_RLS9_image.zip should be easy, and it installs recovery as well. Please read how to install it.
I'm on 4.1.2 stock and wanted to update to 4.2, however I can't get to the recovery. First attempts: Turn n7 off, vol down + power, etc.., boot recovery: It then switches to the google logo (and this device is unlocked), screen flashes to black, google logo again, and it starts to boot normally. I've googled the problem found some things about needing a usb connected to a computer tried it didn't work, tried using a app to boot to recovery, didn't work. I used a toolkit to flash twrp recovery (and tired cwm later on), tried to boot into recovery again both manually and with a app, same thing happened.
Anyone have any idea what is going on?
The booting into recovery bug should be fixed in 4.1.2. Have you tried booting into the bootloader by holding both volume up and down and the power button at the same time when the phone is off? From there you can use the volume button to scroll to recovery and select it with the power button. If that doesn't work then you may have other issues. The custom recoveries may not have flashed with the toolkit or may have been over written on a reboot with stock recovery. You might try flashing twrp using fastboot and rename the recovery-from-boot file. http://www.teamw.in/project/twrp2/103
I am having the same issue.
First noticed something was wrong when Android asked me to update to 4.2 (OTA). I allowed the update and the device rebooted, only to come back in 4.1.2 without any sign of the update. Then I tried to do the update manually, but I can't seem to enter recovery mode in any way.
Things I tried:
* Boot while holding volume up + volume down -> Select Recovery Mode
* Boot while holding volume up + volume down and connected to a PC -> Select Recovery Mode
* Use Quick Boot to enter Recovery Mode
* Use Rom Manager to enter Recovery Mode
* Flash ClockworkMod Recovery through Rom Manager
* Flash ClockworkMod Touch through Rom Manager
* Flash TWRP Touch Recovery through Google Nexus 7 Toolkit
Each time I try to enter the Recovey Mode it will: Show the Google logo and the open padlock symbol for a few seconds -> Screen turns off -> Google logo and the open padlock symbol again -> Nexus logo -> Booted in normal mode. Seems like something errors when attempting to enter Recovery Mode and then it just boots normally.
I attempted the method on http://www.teamw.in/project/twrp2/103. Booting while holding down volume down will boot to FASTBOOT MODE, but the secreen does not say FASTBOOT USB when connecting it to a PC. I have the USB drivers from Google Nexus 7 Toolkit installed, do I need other drivers?
EDIT: So I finally got a custom recovery installed by doing a "fastboot flash recovery" of the latest TWRP (2.3.1.1) from here: http://teamw.in/project/twrp2/103
Neither of the current CWM recoveries (6.0.1.0) would work for me.
You are not alone. Same thing has happened to me. I manually flashed the 4.2 OTA zip yesterday from CWM and while that went fine, I have been unable to re-install a custom recovery ever since. I tried flashing CWM and TWRP from toolkit multiple times. I also did a manual fastboot flash of a newly download CWM but I am getting the same results as you. Nexus 7 will not boot into a custom recovery no matter what.
On the plus side, 4.2 is working well..... Would really like to get root back though.
Menthix said:
I am having the same issue.
First noticed something was wrong when Android asked me to update to 4.2 (OTA). I allowed the update and the device rebooted, only to come back in 4.1.2 without any sign of the update. Then I tried to do the update manually, but I can't seem to enter recovery mode in any way.
Things I tried:
* Boot while holding volume up + volume down -> Select Recovery Mode
* Boot while holding volume up + volume down and connected to a PC -> Select Recovery Mode
* Use Quick Boot to enter Recovery Mode
* Use Rom Manager to enter Recovery Mode
* Flash ClockworkMod Recovery through Rom Manager
* Flash ClockworkMod Touch through Rom Manager
* Flash TWRP Touch Recovery through Google Nexus 7 Toolkit
Each time I try to enter the Recovey Mode it will: Show the Google logo and the open padlock symbol for a few seconds -> Screen turns off -> Google logo and the open padlock symbol again -> Nexus logo -> Booted in normal mode. Seems like something errors when attempting to enter Recovery Mode and then it just boots normally.
I attempted the method on http://www.teamw.in/project/twrp2/103. Booting while holding down volume down will boot to FASTBOOT MODE, but the secreen does not say FASTBOOT USB when connecting it to a PC. I have the USB drivers from Google Nexus 7 Toolkit installed, do I need other drivers?
Click to expand...
Click to collapse
Sim2 said:
EDIT: So I finally got a custom recovery installed by doing a "fastboot flash recovery" of the latest TWRP (2.3.1.1) from here: http://teamw.in/project/twrp2/103
Neither of the current CWM recoveries (6.0.1.0) would work for me.
Click to expand...
Click to collapse
That actually does work, but I just didn't have any idea what I was doing first. Got it to work now.
If you are like me:...
* Before you go into fastboot/bootloader, get CWM-SuperSU-v0.98.zip and place it on your sdcard.
* Go to http://teamw.in/project/twrp2/103
* Download openrecovery-twrp-2.3.1.1-grouper.img
* Put it in the 'put_img_files_to_flash_here' folder of Google Nexus 7 Toolkit
* Boot while holding volume up + volume down and connected to a PC
* Start Google Nexus 7 Toolkit
* Select option 11
* Type the openrecovery-twrp-2.3.1.1-grouper.img filename
* Once it is done pushing the file to the phone, boot from it
* You can now install CWM-SuperSU-v0.98.zip to get root on 4.2
Menthix said:
I am having the same issue.
First noticed something was wrong when Android asked me to update to 4.2 (OTA). I allowed the update and the device rebooted, only to come back in 4.1.2 without any sign of the update. Then I tried to do the update manually, but I can't seem to enter recovery mode in any way.
Things I tried:
* Boot while holding volume up + volume down -> Select Recovery Mode
* Boot while holding volume up + volume down and connected to a PC -> Select Recovery Mode
* Use Quick Boot to enter Recovery Mode
* Use Rom Manager to enter Recovery Mode
* Flash ClockworkMod Recovery through Rom Manager
* Flash ClockworkMod Touch through Rom Manager
* Flash TWRP Touch Recovery through Google Nexus 7 Toolkit
Each time I try to enter the Recovey Mode it will: Show the Google logo and the open padlock symbol for a few seconds -> Screen turns off -> Google logo and the open padlock symbol again -> Nexus logo -> Booted in normal mode. Seems like something errors when attempting to enter Recovery Mode and then it just boots normally.
I attempted the method on http://www.teamw.in/project/twrp2/103. Booting while holding down volume down will boot to FASTBOOT MODE, but the secreen does not say FASTBOOT USB when connecting it to a PC. I have the USB drivers from Google Nexus 7 Toolkit installed, do I need other drivers?
Click to expand...
Click to collapse
It will be of no use to you, but may encourage others I suppose. One of your options above helped me. I managed to get the CWM recovery working by reinstalling it via Rom Manager, then dropping into Recovery via Quickboot (I know it's worked before so didn't try the Rom Manager route). Then I flashed 4.2 via the CWM recovery.
?
[did u solve ur problem?>??
Hi!
I bought me a Nexus 4 on Friday. Today I unlocked the bootloader and then immediately (without booting in maintime) flashed TWRP Recovery 2.3.2.3.
I did everything with the All in One Toolkit 1.3.0.
Now I am stuck in a bootloop.
If I press volume down I can start into fastboot. BUT: before the bootloop my device was detected, now nothing. If I choose "Restart Bootloader" I get again in Fastboot. "Recovery mode" -> Bootloop. Same with Start. Power off does what it's supposed.
If I power off and plug in the charger -> bootloop
if I press volume up and power long time it goes off. Turn on -> bootloop.
My PC runs Win8, I could also start Win7 or Ubuntu if necessary.
Can anyone help me with this? Thanks!
KobiP
Lol, I tried everything. Restarting, Linux, .... Now I tried a different USB Port and voila Fastboot booted and PC detected the Device. Flashed different Recovery and Cleared Cache, Returned to Stock and now it is booting...
phew... :laugh:
Why does this always happen immediately after I write something like this, not before?
Glad to see you got it working. Now you're stronger because of that. Flash on
Sent from my Nexus 4 using Tapatalk 2
Out of the box, remote paired, went straight to update to version 5.1.1, but the cable on my power strip must have come loose during the update and now im stuck at the Google screen.
Ive pressed and held down the bluetooth button on the bottom of the player and got into recovery mode. When it gets to the "No command" portion, I press and hold again to get the options to factory reset the device, but this does not fix the problem and the Nexus Player boots right back to the Google screen. So I wipe the cache, then factory reset, but that fails to work too.
I have OTG USB adapters, is there a way I can copy a stock image to a flash drive and restore the system?
Is there an app that I can install to help restore via USB cable?
Ive read alot of threads, but almost all of them have to do with rooting or flashing to Lollirock, so I dont have any dev tools installed and have only had limited success in using ADB in the past. What am I missing?
SOLUTION!
Got a factory image and unziped it into a folder with fastboot and adb.
https://developers.google.com/android/nexus/images
Followed the steps, but it kept failing. What was I doing wrong?
Well I was using a OTG USB adapter, when I should have been using a normal MicroUSB to USB cable.
Also, I was in the wrong boot mode.
There appears to be two types of recovery mode in which my Nexus Player is detected in Windows/DeviceManager. One is where you press and hold the lone button under the player and apply power, letting go a few seconds into the Google logo. In this initial recovery menu, I have the options to boot normally, boot into recovery, or restart the recovery menu, well I should have stayed there and ran the flash-all script, because when I did do this, it failed initially. Trying a 2nd time worked in restoring my Nexus Player.
The second recovery mode is, from the initial recovery menu, you option to boot into recovery, get the no command error, then pressing and holding the lone button to boot into a menu where you had the option of factory resetting, wipe cache, reboot and apply update from adb. Applying the update from adb allowed my device to get detected in Windows/DeviceManager, but the flash-all script failed. Then tried the sideload command to send a recovery image zip file to the player, but the file transfer would fail about half way through each time. Nexus player would report install aborted.
Hey guys I was trying to flash MIUI 8 on my a6000 lenovo. Bear with me because I'm new to this so I might have screwed up.
Rooted and installed TWRP perfectly. Phone was running kitkat.
I then, through TWRP tried to flash MIUI 8 from http://forum.xda-developers.com/lenovo-a6000/development/rom-miui-7-lenovo-a6000-a6000-t3355692
After first swiping right to install the zip, i got an "error executing binary in zip" error. Wiped dalvik,etc. again and tried again and then I got a MD5 file not found "warning". It was not in red letters and after that message there was no progress bar or anything and the phone just stopped responding. I assumed it wasn't working and few minutes later took the battery out. After trying to boot again it would give me the "mi.com" boot screen (not the default lenovo I used to get) and won't boot into neither recovery nor normal mode. (for recovery boot I'm trying holding both volume buttons and the power button at the same time. perhaps that is different now?)
I'm guessing the flashing was going on and i interrupted it. How can I fix this?
Update: It boots into MIUI now however pretty much nothing works as expected. It wont even go into settings. Recovery still seems botched and i cant boot into it.
TLDR: Recovery broken cant boot into it. Can boot into MIUI with very limited capabilities. Cannot select USB debugging and "adb devices" won't find the phone. What can I do?
Alright nevermind guys I managed to fix it. for anyone wondering or having the same issue, i tried many things but what I think worked is this:
Turnt on my phone in fastboot mode (hold volume - and power button) , connected it to the computer and used command "fastboot flash recovery recovery.img" to flash the old TWRP i had on my computer. After that I managed to boot my phone in recovery mode and reflash the rom properly. The weird thing is, my phone could not be recognized by the computer and "adb devices" gave me nothing back so I thought using any fastboot command wouldn't work. Oddly, it did and it flashed TWRP back into my phone.