well im 99% sure this is why my phone is having issues.
when i updated my rom manager, it told me to update CWM, so i did.
well that was like a week ago, and i wanted to flash a new kernel, did that, CWM was slower then usual, seemed buggy. well i flashed the kernel, nothing but bootloops.
fine, whatever.
so i reflashed my rom, phone was working again, i go back into the buggy recovery, flash a kernel. bootloops.
never before have i had this issue.
i really want to go back to 2.5.0.1.
the current version on my phone and rom manager says is current is 2.6.0.1
anyway know how i can do that?
i found a .zip from the net that says its that version, but it wont install.
perhaps because im using a newer version?
so since my phone is in BOOTLOOPS once again on its own for no reason (no kernel flash either) i think im going to have to flash to amon ra, then flash the 2.5.0.1 zip.
sound like what i should do?
Alright,
so what i did worked.
i used rom manager to flash Amon, then when inside Amon, i flashed the 2.5.0.1 zip, and all is well!
feels good to be back in the "safe zone"
lol
Many people have been having issues with Rom Manager.
Sent from my PC36100 using XDA App
Related
Okay so i had CM6.1.1 flashed onto my evo and everything was working fine. i installed the new version of clockwork mod on my phone and i found something else i wanted to flash. i tried to reboot my phone and now everything force closes. and i mean EVERYTHING! i tried to restore all of my backups and none are working. can anyone help?
dude what i just did was go to rom manager and scroll all the way down flash alternate recovery and after its installed go and tap om clockworkmod recoveries and install the 2.5.0.1 and your good to go !!
JJS714 said:
Okay so i had CM6.1.1 flashed onto my evo and everything was working fine. i installed the new version of clockwork mod on my phone and i found something else i wanted to flash. i tried to reboot my phone and now everything force closes. and i mean EVERYTHING! i tried to restore all of my backups and none are working. can anyone help?
Click to expand...
Click to collapse
I doubt *flashing* clockwork would cause force closes. But you can always revert back to 2.5.0.1 or AmonRa and restore a backup. Check the "Legacy" area of ROM Manager.
I also had this problem as ROM manager kept informing me that a new version of clockwork mod was available. after "updgrading" I couldn't flash any new ROMs and got a truncated message that during the process that 3.0 series clockwork mod needed to have some files deleted due to changes with Gingerbread and something about google.... (sorry about the lack of good definition on this, but the text was truncated and I was freaking out at the time since I started getting stuck at the white HTC boot screen.) Eventually I was able to perform a recovery and finally flash back to clockwork 2.5 and everything is OK now.
Strangely, after doing this ROM Manager indicated that 2.5 CW was the current version... However, after a few hours I started getting the message to "upgrade" to 3.0 again. I'll just ignore that for now.
Does anyone know why 3.0 is not working for everyone?
I got this also, but i wasnt using CM...i was on a sense mod and was able to restore a different rom and went to the new amon-RA instead.
Maybe its something with CM specifically
It has to do with the scripts used in the update.zips. Most people are still using the olds version used in 1.5... Net said that he had to change it to the new scripts used in gingerbread which makes it not work with any updates or backups made prior. There is a topic on it in here where he explains it. He says to flash the 2.5 if it's not letting you update something.
snappydave said:
I also had this problem as ROM manager kept informing me that a new version of clockwork mod was available. after "updgrading" I couldn't flash any new ROMs and got a truncated message that during the process that 3.0 series clockwork mod needed to have some files deleted due to changes with Gingerbread and something about google.... (sorry about the lack of good definition on this, but the text was truncated and I was freaking out at the time since I started getting stuck at the white HTC boot screen.) Eventually I was able to perform a recovery and finally flash back to clockwork 2.5 and everything is OK now.
Strangely, after doing this ROM Manager indicated that 2.5 CW was the current version... However, after a few hours I started getting the message to "upgrade" to 3.0 again. I'll just ignore that for now.
Does anyone know why 3.0 is not working for everyone?
Click to expand...
Click to collapse
Sent from my PC36100 using Tapatalk
They put up a new version of Clockworkmod recovery 2.6.0.1. This will work for all that had problems with the 3.0.XXX versions of the recovery. All the goodies of the 3.0XXX but with amend support so it will work with all roms.
All I can say is that Amon has never let me down. May want to check it out if you haven't already. Even their recent update was smooth as silk. No problems for me.
I had this happen to me too with a flash resulting in the white evo screen loop. I was able to flash to the amon ra 1.8 but I couldn't flash anything. So I upgarded to the new version of RA but am still not able to flash anything. I go into the white evo screen loop and then I have to pull the battery and nand a restore. Not sure what I need to do now. Any help would be greatly appreciated.
Ok so rom manager was telling me that there was a update for clockworkmod, i was on 2.5.0.1, i was very happy with it and never had any issues. I wanted to go to amon so I could back up my wimax just in case. So I did that.
When I went back to clock work it installed some newer buggy version and i was unable to get back to 2.5.0.1. Only other versions.
I wanted to flash a new kernel, i have not been able to, nothing but bootloops.
I'm currently on amon, but still get bootloops, i found 2.5.0.1 as a zip file but when I flash it I just go to it like normal but it doesn't stick, when I go back to recovery i still get amon, until I flash that zip, then I'm back to. 2.5.0.1.
But flashing a kernel through either recoveries I still get bootloops.
How can I get back to 2.5.0.1 for good so its the main recovery?
Any thoughts or opinions?
Yes im wiping dal and cache.
I think something is messed in recovery.
The only way I get the phone to boot normal is if I reflash the rom im using.
Sent from my PC36100 using Tapatalk
Sent from my PC36100 using Tapatalk
If possible, flash the Rom you are currently using. Once that is done, load up clockwork manager and switch back to clockwork's recovery. Once you do that, then flash the zip you had to get back to your older version of clockwork.
I had a similar problem (without constant bootloops though).
Sent from my PC36100 using XDA App
I need help fast...
I got my Htc Incredible replace today and as soon I got it I rooted the phone and I use a custom recovery image to root.. everything went well but when I got the Rom manager from the market and now its asking me to flash a recovery but I dont want to flash to the v3.. I wanna stay with the 2.5 version is there any way I can flash a image with rom manager instead of flashing the new version..
thanks .
EDIT: re-read post.
If you rooted with the latest unrevoked, you should be on 2.5 anyway. The latest ROM Manager only works with the 3.x recoveries. So, either don't use rom manager, (Flash stuff manually) or upgrade.
-----------------------------------------------------------------------------------------------------------------
All the CWM recoverie are here. http://mirrorbrain.cyanogenmod.com/cm/recoveries/
2.5.1.2 here, RM should be able to flash it.
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-2.5.1.2-inc.zip
And there's always 2.5.0.5 PB31IMG.zip, via unrevoked forever.
http://downloads.unrevoked.com/forever/recovery/clockworkmod/PB31IMG.ZIP
If you want the older version of CWM to persist, don't update it in rommanager. Note that when flashing stuff, you do it through recovery, not rommanager.
I have the older CWM, rommanager v 3.0.7, works to create backups. Use recovery to flash and restore.
Sent from my ADR6300 using XDA Premium App
Welp
Personally, I stay away from RomManager. Have never seen something work in RomManager that didn't also work (better) straight out of CWM Recovery.
I am still on 2.5.x.x as well; 3.0.0.5 and 3.0.0.8 seem to cause WAY too much trouble, and there is no clarification from Koush that he is resolving those bugs.
I would love to see an answer on this. I can go back to 2.5 but...
Some of the newer roms require you to use 3.xx.xx Most say to use 3.0.0.7. I would love to but when I set to this version my phone shows no recovery. Just a black screen. I can still push the buttons and get the actions to work, from memory, but this is not a solution. Is anyone else have the "black screen" issue?
Great Offender said:
I would love to see an answer on this. I can go back to 2.5 but...
Some of the newer roms require you to use 3.xx.xx Most say to use 3.0.0.7. I would love to but when I set to this version my phone shows no recovery. Just a black screen. I can still push the buttons and get the actions to work, from memory, but this is not a solution. Is anyone else have the "black screen" issue?
Click to expand...
Click to collapse
I think 3.0.0.7 had an SLCD issue. You must have an SLCD Incredible. You might try 3.0.0.8, I believe it works fine with the newer Incredibles.
I had a nightly running perfectly so decided to back it up in Rom Manager. After backing up it got stuck in booting loop. Couldn't get anything to work in recovery so ended up flashing a stock ROM in hboot (still with root). Now trying to install RC3 but get an error in recovery.
CM report log's last entry says:
line1: unexpected character at 'u'
Syntax error in update script
Any ideas? I'd like to be able to restore one of my older backups (a sense rom) if possible.
mtown_cyclone said:
I had a nightly running perfectly so decided to back it up in Rom Manager. After backing up it got stuck in booting loop. Couldn't get anything to work in recovery so ended up flashing a stock ROM in hboot (still with root). Now trying to install RC3 but get an error in recovery.
CM report log's last entry says:
line1: unexpected character at 'u'
Syntax error in update script
Any ideas? I'd like to be able to restore one of my older backups (a sense rom) if possible.
Click to expand...
Click to collapse
Try flashing CW manually and restoring your previous nandroid manually as well
Hope this helps
I always flash using Clockwork. I use Rom Manager to get the ROM but I perform the actual flash in Clockwork. You'll have fewer issues if you do.
Thanks for the replies. I rolled-back to an earlier version of ClockworkMod, then reflashed CyanogenMod. That worked. Not sure what happened to start this because I was just trying to do a backup. I did have SetCPU installed and overclocked so maybe that had something to do with it.
mtown_cyclone said:
Thanks for the replies. I rolled-back to an earlier version of ClockworkMod, then reflashed CyanogenMod. That worked. Not sure what happened to start this because I was just trying to do a backup. I did have SetCPU installed and overclocked so maybe that had something to do with it.
Click to expand...
Click to collapse
Which version of CWM are you using now, I'm thinking about going to 3.0.0.7 from 3.0.0.8
KB3MMX said:
Which version of CWM are you using now, I'm thinking about going to 3.0.0.7 from 3.0.0.8
Click to expand...
Click to collapse
I went to 3.0.0.7 but I'm back to 3.0.0.8 now. And just flashed RC4. Working great so far. Very fast.
As long as you fixed your problem, we're good, right? Also, try RA if you're having too many problems with CWM
Sent from my Magnolia Incredible
drk.hd said:
As long as you fixed your problem, we're good, right? Also, try RA if you're having too many problems with CWM
Sent from my Magnolia Incredible
Click to expand...
Click to collapse
Yep, all good.
I'm having an issue with ROM Manager. I've contacted Koush and RA and we're are in the midst of working it out. I am curious if any one else has had the same, or similar issues.
I run CM7031 on my Evo. I recently flashed SavagedZen202 kernel from ROM Manager. I used it for about a week and I wanted to check out a taimat kernel. I backedup with CWM and tried to flash to RA to make a nandroid. ROM Manager said the RA was flashed, but when I booted into recovery I was still in CWM. I ttried everything, clearing cash, erasing recovery, un/re installing RM, flashing earlier versions of CWM. Nothing worked. So, without making a nandroid I flashed tiamat405. I figured that would clear up the issue, but I was wrong. Same issue. Finally I flashed a previous backup to CM with its original kernel and everything was fine. I could flash back and forth between CWM and RA. Thinking everything was alright and that I had done something wrong in my other backups, I flashed tiamat again. Same issue, I can not flash between recoveries.
If any one has similar issues or possible causes I'd appreciate the input.
Thanks
Kinda confused...so what actually is the problem?
Had the exact problem. Stuck on clockworkmod no matter what I do. To top it off clockworkmod didn't even work correctly, couldn't flash correctly. I tried to restore a Rom but it ended up being the same Rom, so it didn't actually restore. I ended up unrooting the phone and flash the Sprint 3.7 ruu to go back stock. Then I rooted again and RA/clockworkmod switching started working again.
I guess the problem is one of functionality, I can't flash back and forth between CWM and RA. Its not a big deal because I'm currently on RA and I like RA. But, I have to wonder if RM isn't working correctly are my nandroids backing up correctly? I could go back to CM7 kernel, but I wanted to push my OC a bit more and I wanted to use _viperboy_ scrip for uv and its built for Evo on tiamat. At least that is my understanding. So, what's the problem? A malfunctioning app, I guess! Or maybe an incompatibility between an app and a kernel?!?! And maybe something to do with the ROM? I don't know! That's why I asked.
I had a problem early on when I uped from CM6 to CM7 with Titanium backup, but I worked that out. I've been running CM7 for a while now without issue, until this.
you should just reboot in to recovery and flash your kernels from there instead of using RM its a much better way...
Yeah, I flashed SZ from RM just to kind of see how it worked. But I flashed the tiamat zip from recovery.