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.
Related
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
I currently have:
Fresh Evo 3.4.0.1
netarchy-toastmod-4.1.9.1 kernel
I would like to go to:
Fresh Evo 3.5.0.1
netarchy-toastmod-4.3.1 (unsure on bfs/cfs and havs/nohavs)
Looking to:
Save battery (Am using superpower and underclocking while unplugged)
OC/UC
Wifi Tether
The only reason i am paranoid is that I am still slightly new to flashing and like asking questions. (it took me a long time to work up the courage and flash what i have.) Also when i updated clockwork (to 2.5.1.2) i saw people having problems flashing new roms etc. so i didnt update anymore.
Backing up is not a problem (plan on using astro and sms backup)
Also should i use clockwork (version?) for fresh evo and RA for toast?
Again just looking for a smooth install. My phone is my baby and only source for internet..
Thank you for taking the time to read, even more if you reply and help.
Surrattster said:
I currently have:
Fresh Evo 3.4.0.1
netarchy-toastmod-4.1.9.1 kernel
I would like to go to:
Fresh Evo 3.5.0.1
netarchy-toastmod-4.3.1 (unsure on bfs/cfs and havs/nohavs)
Looking to:
Save battery (Am using superpower and underclocking while unplugged)
OC/UC
Wifi Tether
The only reason i am paranoid is that I am still slightly new to flashing and like asking questions. (it took me a long time to work up the courage and flash what i have.) Also when i updated clockwork (to 2.5.1.2) i saw people having problems flashing new roms etc. so i didnt update anymore.
Backing up is not a problem (plan on using astro and sms backup)
Also should i use clockwork (version?) for fresh evo and RA for toast?
Again just looking for a smooth install. My phone is my baby and only source for internet..
Thank you for taking the time to read, even more if you reply and help.
Click to expand...
Click to collapse
I never have problems with clockwork but, I always flash from recovery and wipe catche partition and dalvik cache. You also need to upgrade to the current version of clockwork. You current version does not save you wimax keys.
Sent from my PC36100 using XDA App
So youre saying if i update to 2.6.0.1 and ill be fine. Just wipe the cache and all that?
Any suggestion on which kernel version?
Nandroid what you have first. I also have never had problems with clockwork, RA on the other hand on 2 separate occasion caused issue I could not fix!
I forgot to mention nandroid.
I am updateing clockwork now.
I am going to try tonight and hopefully post back if all goes well. Im going with 4.3.1 bfs havs.
***EDIT***
All is well.
I guess i just wanted to hear good feedback.
And i tried clearing the cache, i waited 30-40 minutes. Still was at the White Boot screen.
Restored from nandroid and installed 3.5.0.1 w/o wiping cache. worked within 5 minutes.
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.
Ok so most likely I did something wrong, and not Clockwork but I really have no clue how this happened.
Started the day out on my daily driver, CM7 (#39 atm) but got the urge to flash so I figured I'd check out Evervolv. Pretty neat btw, nice work. Anyway, made a nandroid then flashed Evervolv and did some apps, setup etc, flashed an Ubuntu font pack I found in a WarmZ thread which worked fined then decided to go back to CM7 for the time being.
Restored my nandroid and I'm back in CM7, decide I miss the Ubuntu font so I flash that and get bootloops. No problem, restore my nandroid and all is well. Knowing just enough to get myself in trouble I decide to extract the fonts from the Ubuntu font pack, delete CM7 fonts located in /system/fonts, then copy the extracted Ubuntu ones to that location. Had to reboot for some reason and I'm getting bootloops again.
Here's the fun part...restored the same nandroid of #39 as before but now I'm getting bootloops on that. Tried yesterdays #39 nandroid, bootloops. Tried the Evervolv nandroid, bootloops. Every backup I had bootlooped. Btw before these restores I was formatting cache, dalvik, wipe data/factory reset, then went into mounts and wiped boot, system, data, cache. I'm paranoid I guess.
Thinking maybe the sd card was bad I ran a clean install of #39 from another sdcard without issue. Then I got the idea to put my normal sdcard back in and restore my once-was-but-now isn't working nandroid of #39 then flash #39 zip on top of it, and it worked. No more bootloop. Not only that, but now all my other backups are fine again.
So anyone have a clue what happened and how I can avoid it? My guess is I borked something messing with the system/fonts and for some reason the wipes weren't clearing it but like I said I know just enough to be dangerous. Is my wiping ritual wrong? Did I miss something? Any thoughts or ideas?
What version of clockwork were you using out of curiosity?
Sent from my ADR6300 using XDA App
3.0.0.8
HTC Incredible - CM7 - Incredikernel 2.6.37.4 (testA)
I know one of the 3.0 recoveries is known for not wiping completely. That's the only thing I can think of?
Sent from my ADR6300 using XDA App
3.0.0.8 is good far as I know. I suppose it couldn't hurt to downgrade and reflash to be sure (erase recovery checked of course)
HTC Incredible AMOLED - CM7 #39 - Incredikernel 2.6.37.6 (testA)
I think 3.0.0.7 was the one with the problem, I can't remember though. I personally use 2.5.1.2. Not really sure what else would cause that problem though, that's weird.
I was having troubles with 3.0.0.8 and was advised to switch to 3.0.0.7 and have had no problems wiping. I would try that if you think wiping might be the problem.
By no means am I new to this so I'm at a loss. Any help would be greatly appreciated. I've flashed pretty much everything on my hero and now on the evo but I always go back to CM. About a week ago I wanted to flash the latest CM nightly so I booted into recovery to make a nandroid. It was taking way too long (almost 20 minutes) so I pulled the battery, rebooted to recovery, plugged in the usb cable, and mounted the phone to find out I had a 3.8gb backup. I deleted it, unmounted, screamed, wiped everything, and tried to flash the nightly. Nothing but splash screen. Booted into recovery, wiped all, flashed MikG. Good to go. Recovery, wipe, nightly. Nothing. Recovery, wipe, Evo Classic. Good to go. Anything CM. Nothing. I tried every combination of wiping, powering down, rebooting to recovery, flashing different recoveries (started with RA style, went to CWM, RA 2.3), tried flashing with the Mason kernel. I had to nandroid back to an older unofficial CM7 nightly backup. This has never happened to me before. I can flash Sense but I can't flash CM to save my life. I'm a little worried with Deck Reloaded coming out that it'll be a no go for me. Haven't tried Deck 1.3d yet so not sure if it's CM specific or AOSP ROMs. Anyone have any suggestions? Thanks.
Sent from my PC36100 using xda premium
I reached out to ropodope and he hit it on the head. He told me that I had corrupted one of my main partitions. His solution was to RUU back to unrooted stock to repartition and format every one of the partitions like when I first got the phone. It did the trick. It wasn't bad because I was S-OFF. I flashed an old RUU PC36IMG from HBOOT, booted and updated everything while stock, flashed Smelkus 4.2 PC36IMG from HBOOT, nandroided, wiped, flashed CM, and I was good to go again. No need to re-root thanks to S-OFF. I wanted to share this in case anyone else runs into this problem.
Sent from my PC36100 using xda premium