Hi everyone, I have a CWM problem. I SBF'd my phone today (.602), went fine. I rooted, downloaded rom manager, and flashed clockworkmod, all said it went fine. but when I hit reboot into recovery, the phone just reboots normally, not into recovery. I tried wiping data/cache and reflashing CWM, but still no luck. any ideas? I'd rather not have to re SBF/root if it can be avoided, but I can't think of anything else to do.
You have to install Clockworkmod Recovery by using Droid 2 Bootstrapper, then you can update it with ROM Manager.
Sent from my Transformer TF101 using Tapatalk 2
derp! thanks!
Related
Ok so I boughtmy phone today and I rooted. I ran rommanager and flashed clockwork recovery and downloaded a froyo rom and went into rommanager and clicked install rom in rmmanger. I chose the .zip and clicked wipe data and cache. It reboots and goes to stock recovery. It won't boot into Clockwork I tried many different root methods but nothing works. Any help would be apreciated.
Help please
Sent from my SPH-D700 using XDA App
darchevo said:
Help please
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
rom manager is not supported by the stock kernel- to use clockwork you need to use the one click on the dev forum
Can you use the Z4 method?
darchevo said:
Ok so I boughtmy phone today and I rooted. I ran rommanager and flashed clockwork recovery and downloaded a froyo rom and went into rommanager and clicked install rom in rmmanger. I chose the .zip and clicked wipe data and cache. It reboots and goes to stock recovery. It won't boot into Clockwork I tried many different root methods but nothing works. Any help would be apreciated.
Click to expand...
Click to collapse
Happened to me too. Once you install Clockwork Recovery with Rom manager, turn off phone, then turn it on but hold the vol down and camera buttons until the samsung.com screen. Then viola Clockwork recovery.
Basically I got both recoveries on here after using the one click method. All apps that reboot into recovery goto stock which I do need a fix for.
Sent from my "Wheres my 2.2 Epic 4G" using the XDA App
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
hockeyfamily737 said:
There are a few users having problems flashing the recent CM7 nightlies. Here is my scenario.
I'm running CM7.0.2 from EMMC. Last night I tried to flash N63. Downloaded the zip from here...http://mirror.teamdouche.net/?device=encore (where I always get them from). Rebooted to recovery, wiped cache and dalvik and installed the zip. Clicked reboot & got stuck at "ANDROID_". I did a hard reboot (holding down power). Booted back to recovery and did a full wipe (system, data, cache, and dalvik)...Installed the zip again, rebooted and same results. I tried re-downloading the mirror and I've tried installing it with my recovery sd. Everything yields the same results......"ANDROID_".
I can reboot to recovery, and load my nandroids (7.0.0, 7.0.2, Nookiecomb, and Phiremod), however I cannot get one of the new nightlies to flash. I have seen other people are having similar issues so I've started this thread in the hopes of resolving this. I have been working on this problem and searching XDA / Google and still no luck.
Click to expand...
Click to collapse
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
No OC kernel....Just trying to get the nightly to run before worrying about that. I can nanadroid back to any of my former roms with no problem. I'm going to try just doing a ONLY a cache wipe and load it again......just as soon as I run out of patience with my black "ANDROID_" screen of frustration, I'm currently looking at for the last 7 minutes.
Ronin3178 said:
Ok, not a very experienced dev or anything that here. And I have not experienced this problem myself, but a few ideas to throw out:
- Are you trying to install an OC kernel after nightly, or not b4 getting stuck?
- Maybe restore 7.0.x reboot, make sure it comes back. Back into recovery, flash nightly with just a cache wipe, see if it comes up.
Click to expand...
Click to collapse
Yeah........It's a no go. Nand back to 7.0.2, reboot to recovery, wipe cache only, instal zip for Nightly 63......."ANDROID_".....DAMMIT!!!!
I'm back to 7.0.2 again until someone has something else I can try.
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Interesting... I'm using 3.0.1. I'll try updating it tonight.
sent from my Ginger-Hero CDMA
ansleyj44 said:
Are you using cwm recovery 3.0.2.8?
Could be an issue if not.
Sent from my NookColor using Tapatalk
Click to expand...
Click to collapse
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Just another quick note.....To anyone having problems overclocking the new nightly builds. You need to use the ext. 4 overclock kernel, which can be downloaded here......http://forum.xda-developers.com/showthread.php?t=925451&page=239
hockeyfamily737 said:
Good call!!! I flashed Clockwork 3.0.2.8 and all is good. Flashed nightly 63 with no problems. Thanks!
sent from my Ginger-Hero CDMA
Click to expand...
Click to collapse
Nevermind.
janko10 said:
Is there a way to update CWM without burning a new image to SD card? I currently have 3.0.1.0 as well and I don't want to wipe my rom or SD card just to update to 3.0.2.8 but I can't seem to find any other way to do that.
Sorry but this is my first Andriod device so bit of a noob here.
Click to expand...
Click to collapse
I was going to say ROM Manager, but forgot it doesn't have 3.0.2.8 for Nook.
Here is the recovery zip file, flash from CWR. http://db.tt/gDlb5mw
- download to your SD card for Nook, boot into CWR, choose install zip from SD/choose zip, flash, reboot recovery
I had CM7 installed on my phone, and then i proceeded to update to the beta 2. I downloaded the file, then unpacked it on my phone sdcard then proceeded to reboot in recovery mode and cleared cache , dalvik, factory settings and then updated the zip file. then clear everything again and reboot. Get stuck on dual core logo.
I can still access recovery and mount usb to add files. can anyone tell me how to fix this?
did you make a backup before installing the beta?
It seems like you've never installed a ROM before, so I would advise you to read before you try again.
Try and restore it from the 1.8.3 SBF or restore from the CM7 pre-beta2.zip.
Don't unpack the zip file.
Oh and I feel obligated to ask, but did you install romracer's recovery?
I have Tenfar's recovery. Does it matter?
When you say restore, do you mean going in recovery mode and then apply the beta-update2.zip?
I also beleive my recovery got updated to Clockwork's when I had CM7 beta installed?
I have read another post on here that suggest I should RSD flash the 1.8.3 SDF and just start anew.
Should I do that? I was on 1.8.3 prior to installing CM7 beta
I understand I probably come across as a complete noob, but I did read before I did anything.
And now this happened and I just need help fixing it, you can just say. Yes flash back to 1.8.3 with RSD, I don't need a dot point instruction on how to do that.
Now my recovery is "ClockworkMod Recovery v4.0.1.4" even tough i originally flashed Tenfar's
and my phone is unlocked.
I have tried many times to clear all caches and update the beta zip again and it does not work, I just get stuck on dual core logo again.
Thanks in advance for any help.
Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.
quicklyspent said:
Redownload beta 2 again (I've had problems related to bum d/l's). Install romracers recovery. Wipe. Reinstall.
If that fails use fastboot -w to wipe and reinstall.
Click to expand...
Click to collapse
Legend, thanks a lot now I can go back to sleep.
I installed romancer's recovery (unlike tenfar's it took like 5 times longer to clear cache and install the rom) but it did work.
thanks for taking the time man.
I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk
Rayan said:
I think that you forgot to wipe cache and Dalvik cache from within CWM.
For me that did the trick ...
Sent from my Atrix using Tapatalk
Click to expand...
Click to collapse
No I had wiped dalvik and cache prior and after update.
Either beta 2 doesn't like tenfars recovery or it was an issue with the download . Since I installed romancers recovery before I tried the new download we will never know
Sent from my MB860 using XDA Premium App
Why use tenfar's recovery when you can use CWM real recovery now.
That might help a lot...
im having the same problem but i used romracers recovery in the first place. ive tried everything and i tried to restore my alien backup but the recovery cant find it... did prebeta1 change the directory? im lost.
Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk
Magnetox said:
Fastboot -w.
Sent from my Motorola Atrix 4G MB860 using Tapatalk
Click to expand...
Click to collapse
i tried that before and it didnt work.
edit- i found how to mount phone as usb in recovery. going to try the whole process again. i think my file was corrupt.
edit-- still cant get it to work even after redownloading teh file...
So ive been having this issue and it started all after i tried to flash the ubuntu zips that were supposed to work with a custom recovery. I flashed correctly as everyone said to do so, and my recovery would restart during flashing of the armhf.zip(the larger zip). The armhf.zip would get around 2/3 done and then just restart the recovery but now i am having the problem that i cannot recover from any of my recoveries without my recovery restarting. TWRP will recover the system and then while it is recovering the /data partition it restarts back into the recovery, but does not finish the restore. I am running the latest twrp 2.4.1.0. Please let me know if anyone knows how to fix this issue, or if you have experienced this.
Thanks in advance,
I am wondering if i am going to have to flash factory firmware and rom from google and unroot, and then reroot and what not. Just let me know if any of this would help.
Ran into the same exact thing. Had limited success wiping, restoring nandroid backups, or installing CM10 nightlies. I was finally able to get back up and running this morning using http://forum.xda-developers.com/showthread.php?t=2121673 to do a full wipe then install a clean Android ROM.
Sent from my Nexus 10 using Tapatalk HD
melvis02 said:
Ran into the same exact thing. Had limited success wiping, restoring nandroid backups, or installing CM10 nightlies. I was finally able to get back up and running this morning using http://forum.xda-developers.com/showthread.php?t=2121673 to do a full wipe then install a clean Android ROM.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
I am able to flash ROMs fine, its just restoring from nandroid that messes it up, did you do the kernel cleaner and superwipe or just the super wipe zip?
Edit: nevermind I just flashed super wipe, and everything is all good now, I can fully restore. Thanks for the help, I appreciate it.
Sent from my Nexus 10 using xda app-developers app
I have an international LG G2. I'm trying to update it to CM 11, but my CWM recovery is version 6.0.4.0 and I need 6.0.4.4. I tried updating through ROM Manager, but every time I boot into CWM, it's still version 6.0.4.0. I tried to use ROM Installer, but came across an error. I tried using Flashify to update CWM by manually downloading the CWM recovery image online, but also came across an error. Would really like to fix this problem.
I'm also having this issue on the ATT model, with the "6.0.4.5 CWM-based recovery" that came with Freegee. Trying to get the legit CWM 6.0.4.4 to flash and I can't do it.
Grab the zip file. Boot into recovery and install the zip. Never user rom manager ut doesn't work well with this phone
Sent from my LG-D800 using Tapatalk
tdevaughn said:
Grab the zip file. Boot into recovery and install the zip. Never user rom manager out doesn't with with this phone
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
Zip file? I can only find the img files on CWM's official website. I tried to use Flashify to install that, but when trying to boot into recovery, the phone got stuck at bootup and I had to hard reset it and it went back to normal with the recovery still at 6.0.4.0 unfortunately.
Been using Phil's recovery lately it is built off of cwm . http://goo.im/devs/philz_touch/CWM_Advanced_Edition/d800
Sent from my LG-D800 using Tapatalk