Hey all,
I'm having a slight issue with Clockwork Recovery as in it won't boot unless I just reflashed it.
I rooted and started flashing ROMs on day 1, but a friend of mine noticed on his phone that he cannot get into Clockwork Recovery unless he opens ROM Manager, flashes CWR, shut down manually, and reboots into Recovery manually. Any other time he is greeted with Andy on his back with the Orange /!\ on his chest. So I checked it on my phone, and sure enough, same thing.
Is this a consistent problem for everyone and if not, is there a fix?
Thanks in advance!
CWM hasn't been permanently flashed, hence the stock recovery going back unless you go through (the crap) ROM Manager. Manually flash it using fastboot and you're sorted
It automatically restores the stock recovery on boot. Look at one of the rooting guides in the dev section for info on which file you need to rename to stop this behavior.
Sent from my Galaxy Nexus using xda premium
I recently got a GSM gNex and last night I decided to upgrade to JB using the OTA links posted here in the forum. I unlocked the boot loader, flashed twrp's recovery, installed SuperSU and then the JB 4.1.1 OTA file and everything went smoothly. Since after the upgrade, on my PC when I connect my gNex, I'm getting a "Fast boot read error" and my PC stopped recognizing the device. I switched to my Mac and got everything I needed done. Why am I here? Obviously I've been able to go into twrp recovery to do a lot of this stuff. But now, anytime I try to go into recovery mode, I get the screen with android lying on back with the exclamation point. I have to flash recovery (I've tried CWM, CWM touch, optimus prime touch) using fast boot every time I have to go into recovery. I tried going to recovery using ROM manager and that gets me to same situation. (Android on back).
Any thoughts?
Sent from my Galaxy Nexus using xda app-developers app
verruckterGeck said:
I recently got a GSM gNex and last night I decided to upgrade to JB using the OTA links posted here in the forum. I unlocked the boot loader, flashed twrp's recovery, installed SuperSU and then the JB 4.1.1 OTA file and everything went smoothly. Since after the upgrade, on my PC when I connect my gNex, I'm getting a "Fast boot read error" and my PC stopped recognizing the device. I switched to my Mac and got everything I needed done. Why am I here? Obviously I've been able to go into twrp recovery to do a lot of this stuff. But now, anytime I try to go into recovery mode, I get the screen with android lying on back with the exclamation point. I have to flash recovery (I've tried CWM, CWM touch, optimus prime touch) using fast boot every time I have to go into recovery. I tried going to recovery using ROM manager and that gets me to same situation. (Android on back).
Any thoughts?
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If 4.1.1 is anything like 4.0.x, you'll have to rename/remove this file: /system/etc/install-recovery.sh
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
If you a can boot into recovery than you aren't bricked.
You can do a factory reset that might clear it up.
Worst case go into download mode and use Odin to reinstall the stock ROM.
Sent from my SGH-I747 using xda app-developers app
northstar7 said:
I have a rooted Galaxy S3 that is running the ATT Jelly Bean update.
Last night, while looking at ROM manager I got a popup saying there is a newer version of CWM and did I want to install it.
After installing it, the phone will only boot into recovery. I cannot get it to start. And when I tried to restore from a backup that I have used successfully before, I got an error while restoring data.
At this point, I am thinking that I might have bricked this phone. Searching on the ATT Galaxy S3 forum hasn't turned up anything relevant.
Does anyone have an idea what I can try next?
Thanks
Click to expand...
Click to collapse
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Different CWM
xBeerdroiDx said:
Im assuming you powered down, did a battery pull and powered back up? Factory reset?
What error message is displayed when trying to restore a backup?
The latest cwm release is 6.0.2.8. If you came from 6.0.2.3, I would download a cwm flashable zip of that recovery and flash that. Perhaps try a reboot then. If it's still a no-go, try restoring a backup with the cwm you had just downloaded and flashed to see if it will restore without an error message
Click to expand...
Click to collapse
Thanks very much for the advice.
For the record, my phone is displaying "ClockworkMod Recovery v6.0.2.9"
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
I as well. Tried everything and no go. Will try ODIN and see if it works.
Domoo said:
I just has this happen to me as well. I just put the s3 in download mode and used Odin to re flash cwm. I'm using the same version cwm.
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
stranglely pressing the recovery button combo fixed it and im back in CM10.1 #lolwut?
In the end I got the phone working again
For whatever reason, after getting that update to ClockworkMod, the phone would not boot.
I followed the Beginners' Guide to Rooting the Galaxy S3 forum. When I was finished I immediately got an OTA update from ATT.
So now the phone is running again, but I've lost most of my customization and personal data.
What is with this CWM "upgrade?" Or is the problem with ROM Manager?
More likely is that I did something wrong.
At least I can make calls now.
Same here, stay away from that update! Bad things!
This also happened to me. Cwm is showing up as .9 instead of .8. I flashed a previous version of twrp and it still proceeded to go into recovery mode after selecting reboot. I did a factory reset and re flashed aokp and also cm10.1 (along with gapps of course) and it still did it. So I pulled the battery and put it into download mode and reset it from there. That's the only way to get the phone to boot up. From what I see here, is the basic fix for this problem flashing an older cwm in Odin?
Having the same issue, version .9 No amount of clearing data/wipe/reflash/restore will do anything for me either. So much for a lunchtime AOKP update...
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
I flashed with the same version of cwm I had previously before this issue (6.0.28). It seems to be an issue with 6.0.29 if so many people have this same issue.
Sent from my SAMSUNG-SGH-I747 using xda premium
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I flashed the CMW-recovery_ATT-6.0.2.3_zip directly from the external sd card to the phone and the phone is now working. but I did have to reboot phone twice. the first time it stayed in recovery.
THANK YOU!!
xBeerdroiDx said:
I've looked in several different forums on xda and the general fix seems to be flashing a previous version of cwm. No need to reset your phone and flash roms all day long.
Download prior cwm release (.tar)
pull battery and replace
boot to download mode
connect to pc and flash cwm
Disconnect, pull battery, reboot
Here's the 6.0.2.3 release. You can grab the .8 in the Android dev section if you wish
https://www.dropbox.com/s/sfkjtndn7k0urmh/recovery-clockwork-6.0.2.3-d2att.tar
Let me know if this does not work. If your device is not recognized by your pc, you can try flashing this cwm zip in recovery itself (if you have a micro sd card):
http://d-h.st/8qP
Click to expand...
Click to collapse
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
J M L said:
I believe this can even be simplified a bit more. At least for me, some people may find Odin to be the simple way to do things. So you're stuck at recovery:
Hold the power button for 10 seconds to power off.
Boot to download mode by holding volume down and home. The phone will probably start to boot right away after releasing the power button. If it doesn't go to download, then your timing is off, try again.
Hold the power button for 10 seconds to power off and reboot.
It should boot regularly now.
Flash a new recovery. You can download CWM 6.0.2.8 or use this as an opportunity to move to TWRP. Once you have the img file on your phone, go to a terminal and (after su, if needed) run dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p18 (replace "/sdcard/recovery.img" with the path and name of the img file you downloaded. You can also flash the recovery using whatever other on-phone method you prefer.
The CWM download page is now showing that 6.0.2.8 is the newest version for many of the S3 variants, so they've certainly noticed the bug.
Click to expand...
Click to collapse
How is this simpler? There are left out bits and errors all through your instructions. My steps were for odin so I'm not sure why you thought they were not.
So, I was trying to put 4.4 kitkat onto my galaxy nexus verizon phone and I had CM10.3 working on it (which was roughly 4.3.x) and clockword recov mod. and then I got a new clockwork rom (as attached) and I ran: fastboot flash recovery newrecovery.img
Then it successfully ran via adb, but then when I rebooted it, i told it to go to recovery mode, but it brings up a default "Google" page with a unlocked symbol on the bottom. Its been running for about 10 minutes now and it will not get off this page.
What can I do? Is this thing done for? I cannot seem to get it to work.
Thank you.
Flash the newest cwm via fastboot and reboot to recobery.
Sent from my Galaxy Nexus using XDA Premium HD app
So, I need to send my Nexus 7 back in for factory inspection/repairs, since it decides to reboot multiple times a day on its own. I had my N7 running CM w/ TWRP. I've flashed my device back to stock and everything, however it fails to boot up to the stock recovery. In it's stead I just get an Android man lying on his side open with a red exclamation in a triangle. I can't link the image directly, but http //i stack imgur com/kcSE4 jpg. Periods where there are spaces, except for right after the http, there is the usual colon.
I've tried running Restore Stock Recovery thru the Nexus Root Toolkit. I've tried manually flashing the recovery.img with fastboot flash recovery recovery.img while in the bootloader. I'm not sure what else to try. Is there anyone that could help me?
I get the recovery thing too and I've never installed a custom ROM or recovery (although I did flash twrp once but I did not install it) its not really a big deal for me be cause if I ever need a recovery I can flash one from my computer But I would like to know why this happens anyway.
Sent from my Nexus 7 using XDA Premium 4 mobile app
mugzylol said:
I get the recovery thing too and I've never installed a custom ROM or recovery (although I did flash twrp once but I did not install it) its not really a big deal for me be cause if I ever need a recovery I can flash one from my computer But I would like to know why this happens anyway.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I'm just primarily afraid that my warranty would be voided if they discovered that the recovery was missing. I can flash
TWRP back just fine, but not stock.
EDIT: Never mind. I apologize for my ignorance. I found out that you go to the recovery menu from that screen by holding the Power button and then pressing the Vol Up button. No more assistance shall be needed.
Yoou are saying that after flashing stock recovery you see a android with open stomach and exclamination mark
But android with open stomach and exclamination mark showing in recovery means it is stock recovery of nexus 7
I have a nexus 7
When it was not rooted i tried to boot to recovery i got the same
After rooting i get twrp in recovery
Sent from my Nexus 7