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
Related
My phone is permanently rooted using visionary, and I have flashed clock work recovery from rom manager, but when I try to boot into recovery it just shows the phone with the red triangle? Can any one help me.
Thanks
Sent from my T-Mobile G2 using XDA App
From what I have read elsewhere, re-flash Clockwork Recovery.
Doesn't work.
Sent from my T-Mobile G2 using XDA App
You're supposed to only download and flash recoveries from Rom Manager if you're on wi-fi since T-mobile caches web pages but I was able to get around this by flashing an older version (in Rom Manager) and immediately reflashing the correct recovery (without rebooting or even leaving RomManager).
Of course you can always download the recovery.img file and fastboot flash it.
me too
Same issue. Trying to boot into recovery gives pic of phone with red triangle.
- I reflashed clockwork recovery (not sure is this helped)
- manually went into recovery manager from rom manager menu which loaded w/o problems
- selected backup and restore
- perform backup
seems like it is working...
Volume-up + power. If you already did that then i dunno
Sent from my HTC Vision using XDA App
fix permissions in rom manager and reflash clockwork
recovery mode
newbie here, or course. back after 2 years away with BBerry, g2 cant get past recovery. i am looking for a way to get my device to turn back on... basically when i try to fastboot, it say i have the wrong image, or no image, fails to load E: sd card failed. i have acces to another G2 so i can get a copy of the stock rom image but has not worked::: i need assistance in this process. what do i need to load from the sd card to make my G2 turn back on or is this what bricking your device is? i have access to the recovery screen and can still load info from the sd card.
thanks for any info.
Are you saying your rom doesn't boot? Are you s-off? And if so can you get into recovery?
FYI - people generally don't fastboot from the SD, are you sure you were in fastboot mode and not hboot?
My Desire won't start up anymore, it reboots after about 15 seconds. This happended after installing the latest stock ROM from HTC. I am able to reach both the bootloader (HBOOT-0.93) and the recovery (Android system recovery 3e)
When trying to install a update.zip from here, I always get a "verification failed"-message. Any tips would be highly appriciated
What update.zip are you trying to flash?
I've tried a couple of the newest ROM's from the Desire section here at XDA. Downloaded, renamed update.zip, moved to SD, went into recovery and "apply update.zip". Verification failed comes immidiately
Sounds like you're trying to flash a custom ROM using the stock recovery. You do know you have to be rooted to flash a custom ROM?
Okey, so what should I do? Flash a stock ROM? Use a costum recovery? All I want is to get the phone up and running again
Well, you said you flashed a stock ROM already. Which one did you flash?
You could try a factory reset: Turn phone on whilst holding the back button and select 'Clear Data' and then reboot the phone
I've always had stock ROM, rooted with Unrevoked. I got an OTA update earlier this week, I don't have a build number on this but It seemed to install just fine. It seems this update replaced the custom recovery with the stock recovery (?) and as mentioned, the phone doesn't boot.
Factory reset doesn't help either.
I have the same problem on mz Desire. Rooted, but when applied the latest update from HTC phone just keep on rebooting every 10 secs. any sugestion?
TNX
You shouldnt be applying any updates to a rooted phone.....
What rom were you on? 2.29.405.2 or something similar?.....
Sent from my HTC Desire using XDA App
I was on 2.10 (i think) and stock rom (no custom)
Try flashing this...
http://shipped-roms.com/download.ph...9.00.32U_5.11.05.27_release_151783_signed.exe
You will need to boot your phone into fastboot (power & back button) then connect it to your PC. You should see 'fastboot usb' on the screen. Run the RUU you downloaded.
This will wipe your phone and unroot it.
Sent from my HTC Desire using XDA App
tnx
going to try it out!!
will post results
when i first rooted with unrevoked, then installed opendesire, i was stuck in a similar boot loop.
the solution was to boot into the boot loader and select "clear storage".
it then booted into opendesire straight off. a bit nerve racking when you think you've just made an expensive mistake.
i hope this solves the problem for you!
@slippy
didn't work, but thanks
@mike
erased it all, but phone is alive again. thanks
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Why do you think using ClockworkMod was a mistake? It's one of the better AOSP ROMs out there.
It sounds to me like you're probably going to have to download one of the stock RUUs to completely revert your phone to stock. You might have a corrupted recovery. You can't flash ClockworkMod or an alternative recovery via RomManager?
oh don't get me wrong, my huge problem here is that I can't get into recovery, and I didn't load clockworkmod initally, but it is (as rom manager says) my recovery image and it's just not working at all.
I tried going with a RUU and it wouldn't get into bootloader properly (just shows HTC on the screen till the the ruu times out) I'll try on a 32 bit machine when I get home. I was originally able to flash on that and unrevoked was giving me issues till I did a 32 bit xp attempt. Thanks for the response!
whoops, forgot to address your last point. Tried another version of clockwork and the RA_GNM 1.8.1 and neither stopped it from bootlooping rather than recovery screen.
HTCP2newb said:
I'm having issues with a bootloop on the incredible after rooting using unrevoked 3 and making the mistake of choosing cyanogenmod as the recovery because I'm incredibly new at this. Now granted this isn't an issue, I have root access now and I'm able to assign superuser and the phone boots to what looks like the stock rom. However, I wanted to flash cyanogen 7 rc2 and it's giving me a lot of issues when I try to access the clockworkmod recovery screen. I downloaded the rommanager from the market and flashed the recovery to clockworkmod 3.0.0.8 as per a wiki online and tried to boot to recovery. from there it hits the HTC incredible screen, then flashes every 3 seconds rather than showing the green text it's supposed to show.
I still have S-on and unrevoked won't run properly again. Tried running the factory reset and it's another bootloop. I tried going through the steps for a "manual recovery file flash via cyanogen's wiki, but I'm running into errors.
Summary:
unrevoked 3.32 completed successfully even using the cyanogenmod rom as the recovery file.
Have root access, S-on, radio version ~.7.28
Can't flash back to stock due to bootloop
Can't factory reset due to bootloop
Can't get to clockworkmod recovery screen due to bootloop
phone able to boot to main screen with original
Ideal solution: get to clockworkmod recovery screen and install C7RC2
Any help appreciated!
Click to expand...
Click to collapse
Did you try getting to recovery manually power off the phone while its off press power and volume down at the same time you should be in hboot use the volume button to scroll down boot into recovery.....
Sent from my Incredible using XDA App
I don't think unrevoked finish all The way because you should be s-off did you wait until it said "done"..... or did you stop when it said "this is a triumph"
Sent from my Incredible using XDA App
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
HTCP2newb said:
Okay, from a 32 bit system has resolved the flashing back to a stock rom, I will update as to whether I can get into recovery and will wait until I am told "triumphant" this time around.
Will post an update in a bit if this was all that was necessary to fix the issue. Thank you all to have posted so far, please post if you think I'm missing something else.
Click to expand...
Click to collapse
No you need to wait till it says done sorry you misunderstood me......let it go till it says done and it stops completely..... because the last thing it does is flash the recovery
Sent from my Incredible using XDA App
Did you try flashing a recovery through hboot?
Sent from my ADR6300 using XDA App
Okay, problem totally resolved. basically what happened was that there was an incomplete unrevoked process for whatever reason or another. I repaired by downloading the RUU off the HTC website and flashing back to stock. That generated an error of "your firmware is too new" which is available elsewhere in XDA, basically solved by going into hboot and factory resetting.
Once I had the factory reset completed, I used a 32 bit system to unrevoke the phone (after setting debugging to on in applications > developer settings >debugging on) then I was able to properly boot into recovery. I recommend Clockworkmod update to 3.0.0.8 in Rom manager, but I used 2.5 and didn't have much of an issue. I backed up and the wiped the memory and cache and installed 7r2 without an issue.
The phone is WAY more stable now (thanks to all the hard work at Cyanogen! Thank you also to everyone who posted here!) Pandora doesn't randomly cut songs in half and battery life seems to have improved. Whether that was verizon's crap or I went market-crazy and had waaaay too many apps syncing... I can't say.
Thank you everyone again!
Ok so i got my nexus today and it is fantastic. I unlocked the bootloader and rooted the phone no problem. installed clockwork with rom manager though, I turned the phone off and then while pressing vol up and down went into recovery again. Rebooted into clockwork and bam we're good. I rebooted to move some files over and when i tried to get into recovery again i get the android dude with the yield sign over and over again. Im not sure why this is happening, any suggestions?
I was having the same problem at first. Problem was fixed by "flash clockwork mod" and then reboot into recovery. After that I had no problems. :beer:
Sent from my Galaxy Nexus using Tapatalk
I also initially tried to install CWM thru rom mananger but after a reboot or 2, booting into recovery always led do a android with red triangle and I'd have to re-install (this was happened many times)
To finally fix it I downloaded the CWM .img and flashed it using fastboot on my laptop while the phone was in the bootloader. Recovery image hasn't died since.
Means image isn't applied.
Get Rom manager from the market and it will flash image.
Done.
Android with yield sign is stock Android recovery.
Sent from my Galaxy Nexus using XDA App
Hi guys, I managed to do something I've never heard of. To be fair, I try to follow directions pretty well, so I don't screw things up too often, and I'm not sure what to do now. Any help or guidance would be appreciated.
The symptom is that the phone will boot witht eh Samsung boot animation, I will see the Clockworkmod icon at the bottom, some Clockworkmod version information, then the phone will reboot. This will happen presumably indefinitely. I have watched it do it 3 times in a row and then pulled the battery. Post Philz, I get Android tablet icons instead of Clockworkmod icon and version info.
I loaded Whompasaurus http://forum.xda-developers.com/showthread.php?t=2039564 to my phone yesterday and I was about to load Venom http://forum.xda-developers.com/showthread.php?t=2121063 to my phone this morning (I had just copied it to the SD card). I told the phone to reboot into recovery by pressing the power button and selecting the option "reboot, recovery". The phone is now stuck rebooting attempting to enter recover and failing, or so it appears. I upgraded the Clockworkmod version to 6.0.4.3 yesterday, and that did act a little weird in my opinion, but since I had never done that before, I wasn't sure what to expect.
When I told it to upgrade in the Clockworkmod app, the phone powered off and I had to remove the battery to turn it back on. I booted to recovery and it said it was now at 6.0.4.3, so I booted normally. Back in the app it said it was 5.something. I kept poking around and it eventually asked for root access, which it hadn't before, and when I told it to upgrade the recovery this time, it actually rebotted the phone rather than turn it off.
I reflashed the CWM 6.0.4.3 recovery with Heimdall per these instructions (why aren't there proper instructions for Odin?!?!?! ermahgerd!!) via this link http://wiki.cyanogenmod.org/w/Install_CM_for_l900
That was successful but did not affect the symptoms.
I upgraded to Philz recovery thinking maybe I had to use a different recovery to reset the "boot to recovery" flag. I used this file and Odin, after resetting the Samsung driver: http://goo.im/devs/philz_touch/CWM_Advanced_Edition/l900/philz_touch_6.26.6-l900.tar.md5
The process was successful, but did not change the symptoms. Instead of seeing a Clockworkmod icon and version info at the bottom, I see what looks like android icons at the bottom, and then the phone reboots.
What can I do to fix my phone? I can boot to downloader mode fine. I would prefer to use Odin, but it seems I have Heimdall set up and working too.
Try using Odin to glad twrp 2.6.x then if it works try flashing your desired recovery from recovery
Sent from my SPH-L900 using XDA Premium 4 mobile app
Team Win FTW!!! That fixed it!
jlmancuso said:
Try using Odin to glad twrp 2.6.x then if it works try flashing your desired recovery from recovery
Sent from my SPH-L900 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Is there something special about 2.6.x? I saw that there's a 2.7.x available now. 2.6.x doesn't seem to like my 64GB SD card, or maybe something else is going on. I factory reset a few times and will upgrade to the latest TWRP and try to flash that latest Venom ROM now and see what happens.
*Edit* No, there's SDCARD, SDCARD1, and EXTERNAL_SDCARD and I didn't check all of them, that's all. Oy, oy, oy.... But I'm up to 2.7 and installing Venom now....
Are asking for ROM recommendations still a no-no?
Yeah still pretty much a no no. I have used all the roms here and they are all pretty good.
Now I do suggest that you flash philz 6.07.9 for your recovery. First is that it properly flashes 4.4 and TW 4.3 roms. Second it makes proper backups. Twrp still has issues with aosp 4.4 and TW 4.3.
Sent from my SPH-L900 using XDA Premium 4 mobile app