Lately I've been having a problem with my Evo. After flashing the latest stable roms 6.1 and 6.1.1, I found my phone freezes, force closes, and reboots, then wont get past the white evo screen. Ive wiped everything using amon ra and clockwork but i keep coming back to the same issues. I even try not using Setcpu on a clean install and still have issues. I also noticed that everytime I wipe then flash, the google apps show up after my first boot, even though i never flashed the google zip file. Is my phone wiping correctly? What could be the problem?
aheavyguy said:
Lately I've been having a problem with my Evo. After flashing the latest stable roms 6.1 and 6.1.1, I found my phone freezes, force closes, and reboots, then wont get past the white evo screen. Ive wiped everything using amon ra and clockwork but i keep coming back to the same issues. I even try not using Setcpu on a clean install and still have issues. I also noticed that everytime I wipe then flash, the google apps show up after my first boot, even though i never flashed the google zip file. Is my phone wiping correctly? What could be the problem?
Click to expand...
Click to collapse
If this ONLY happens to you when using cyanogenmod roms, then you are not alone. The exact same issue happens to me also ONLY when using CM 6.1 and CM 6.1.1. I have never had this issue with any other rom, both aosp or sense-based, except with CM 6.x roms.
Sent from my HTC EVO running Myn's Warm TwoPointTwo RLS 4 loaded with all the goodies
Yea for some reason these last 2 releases just wont work right on my phone. Which def sucks because I love Cyanogenmod roms. Anyone have any suggestions as to why this might be happening?
Try the following:
Wipe data+cache twice
Flash sense ROM
boot
wipe data+cache twice
verify MD5's
flash CM
flash gapps
U recommend clockwork or ra
What? This title for a thread and no poop jokes? The Internet makes me sad.
Seriously, though...
I'm partial to Clockwork now because I use ROM Manager Pro. AmonRa was the one I always used on my Hero. Both are good. It's yet another "personal preference" thing.
CM6 Issues
I too have had trouble with CM 6.0 and 6.1. I flashed CM6.0 Stable, and could not get apps to install or uninstall after flashing. I tried restoring an earlier Nandroid backup of my previously working HTC Sense ROM, and still could not install/uninstall any apps. I tried clearing Market cache, fixing permissions, wiping cache, Dalvik cache, numerous reboots, and flashing earlier ND backups with no luck. I finally bit the bullet, flashed Stock RUU, and had to reroot to get phone working properly again.
Think I would have learned from above, but being flashaholic that I am, I flashed CM 6.1 when it came out. Exact same probs, and again had to reflash stock RUU and reroot.
No more Cyanogen mod for me. Nothing against CM, and it may work great on some people's EVOs, but its only caused me headaches.
Good news is I'm getting pretty damn proficient rooting phone using old-school manual adb shell/rageagainstthecage/chmod exploit method, having done it three times now (although I hope I don't find myself in this situation again).
YMMV
Me too. Tried with both clockwork and ra...no dice. Problem is, when I went back to warm, it left pieces and now even warm doesn't run correct. I tried wiping twice and clearing the dalvik too. I know it wasn't erasing everything because there would be apps that were already installed. Like it was installing to a partition, though I have never set that up.
...
Related
So i just recently finished rooting with Unrevoked 3 and i want to try out Roms now, I tried to flash Damagecontrol v3.5 but it got me stuck on the loading screen and wouldn't get past it so i just did a restore with ROM manager (thank god) and was able to get my phone back it got me really scared so can anyone suggest any good stable roms? Also did i need to have unrevoked forever install? and my last question would be if i install a ROM can i install themes on it? how does it work?
I've been using Fresh 3.4. Very stable, with riptides theme... u must wipe everything before flashing a rom....
Sent from my PC36100 using XDA App
Don't let that experience scare you away. We're lucky to have a large number of quality roms, themes,etc. For our evos. Make sure you always make a nandroid/backup before flashing new stuff and you're golden. It's difficult to actually 'brick' your evo. Read, experiment, find what you like, and become a flashoholic like most others on these boards.
-sent via xda app on my supersonic evo
Myns warm two point two rls3 is by far my favorite Rom. It's smooth and very stable. Check it out. I always do a full wipe... wipe system, wipe cache, wipe dalvik, and if battery is at 100% wipe battery statts.
Sent from my PC36100 using XDA App
Klk450 said:
So i just recently finished rooting with Unrevoked 3 and i want to try out Roms now, I tried to flash Damagecontrol v3.5 but it got me stuck on the loading screen and wouldn't get past it so i just did a restore with ROM manager (thank god) and was able to get my phone back it got me really scared so can anyone suggest any good stable roms? Also did i need to have unrevoked forever install? and my last question would be if i install a ROM can i install themes on it? how does it work?
Click to expand...
Click to collapse
Yes install Unrevoked Forever. Wipe and factory reset twice, wipe cache twice and also wipe dalvik cache twice then retry rom.
Thanks for all the replies guys, i just finished Flashing CM6.1 and i installed a theme called MattedBlue, although i can't get it to look how it is in the picture lol but im getting the hang of this, and must say im becoming a flashaholic
so you got it without my help? glad to hear it.....
I haven't found any solution with this. About 3 or 4 weeks ago my Evo went crazy so I rebooted and was missing many apps. I did a nand to another sense rom and every time I tried to install an app (either download or from sd card) it would reboot. The odd thing is, it only does it with sense roms. I can use CM 6 or 7 fine and install whatever I want. I was originally one Myn's rls5, I also tried the Fresh roms. I have non clue what's causing this, tried googling and all said clear the market cache or try an older market, which I've done both. Any help would be greatly appreciated.
tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?
Don't use a backup. Flash a sense ROM and install everything manually.
Sent from my PC36100 using XDA App
shogun26 said:
tricky one. have you tried flashing a stock sense rom, and seeing how things work for you there?
Click to expand...
Click to collapse
I haven't tried a stock rom yet, once I get things back up I'll find one and try it.
gqstatus0685 said:
Don't use a backup. Flash a sense ROM and install everything manually.
Click to expand...
Click to collapse
I can't install anything. period. as soon as I try to install any apk from my sd card or anything from the market that doesn't come installed in the rom, as soon as it "finishes" the installation part it will reboot, but not a full reboot, it will go out to the boot screen (but not all the way to the htc screen).
Since going from AOSP to Sense what was your procedure for flashing? Just want to make sure your starting with a clean slate.
- What steps to you take?
- Full wipe? Data, cache, sd-ext?
- SD format?
The more info you can give the better and maybe we can help you track it down.
Ive done the standard full wipe, data, cache, dalvik. I do that everytime between roms. Not sure what the ext does and in haven't formatted my sd card since then
Sent from my PC36100 using XDA App
Update - I flashed the stock rooted 3.70 and was able to install. This was after formatting my sd card. Then tried to flash Myn's rls5 again and had the same problems as before. Only difference is with the 3.70 I forgot the flash the radios, but still had a fine signal. I flashed the radio updates with Myn's. Any help/advice is greatly appreciated.
At this point all I can think of doing is unrooting your device and getting it completely back to stock, then try re-rooting and make a nandroid of your rooted, stock sense rom.
Maybe you can root through a different methods than what you did originally.
After that, try another sense rom, make sure the md5 checks out too.
Sent from my PC36100 using XDA App
What recovery are you using and what version? I thought there were known issues with ClockWork 3.x.x.x version of recovery not wiping cache correctly? If you are using ClockWork you might want to try switching to Amon_RA 2.2.1. to see what happens. There is also a zip floating around (which I have attached) that can be used to wipe everything, you may want to give that a shot then reinstall the ROM. I have not used this zip, so use it at your own risk as I cannot guarantee the results. I have read about others using this and it working just fine.
ok i've been flashing roms for over six months and have been able to fix every issues i've ever had until now..
was running cm nightly 21, tried to update to 23 a couple weeks ago and all i got was a boot loop on the white htc evo screen. ok so i re-download the nightly, clear cache dalvik data and reflash. same boot loop occur. so i waited a few days and new nightlys appeared. so i download and tried to flash. same results with the boot loop.
i reverted back to cm nightly 21. tried to flash savage zen 2.1 kernel. reboot. same white htc evo screen boot loop. flash savage zen 2.0 with cm nightly 21 and it works flawlessly. flashed cm rc2 with savage zen 2.0 and ran flawlessly but boot loops with sz 2.1-1.0.
problem: cm nightly 23 and up (23-30), cm rc3, savage zen 0.2.1 and up, and tiamat's latest kernel (3.32?) all would install properly but when phone boots it is stuck on boot loop at the white htc evo screen.
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
here's my system: latest radio, wimax, prl, pri, hboot.. latest everything update. hardware revision 003. baseband 2.15.00.07.28. S-off. what else..
my thoughts: cm 23 and up, savage 2.1 and up, and tiamat's latest all incorporated hdmi into their builds. i've never used nor have the ability to activate hdmi on my phone. so i'm thinking it's something to do with hdmi? every other rom from cm 21- and rc2- and sense roms seem to work perfectly fine.
i am currently running cm rc2 with savage zen 2.0.. are my days of flashing the lastest and badarse combos of cm and savage zen over? please help if anyone have any ideas and thanks in advance..
losphn said:
ok i've been flashing roms for over six months and have been able to fix every issues i've ever had until now..
was running cm nightly 21, tried to update to 23 a couple weeks ago and all i got was a boot loop on the white htc evo screen. ok so i re-download the nightly, clear cache dalvik data and reflash. same boot loop occur. so i waited a few days and new nightlys appeared. so i download and tried to flash. same results with the boot loop.
i reverted back to cm nightly 21. tried to flash savage zen 2.1 kernel. reboot. same white htc evo screen boot loop. flash savage zen 2.0 with cm nightly 21 and it works flawlessly. flashed cm rc2 with savage zen 2.0 and ran flawlessly but boot loops with sz 2.1-1.0.
problem: cm nightly 23 and up (23-30), cm rc3, savage zen 0.2.1 and up, and tiamat's latest kernel (3.32?) all would install properly but when phone boots it is stuck on boot loop at the white htc evo screen.
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
here's my system: latest radio, wimax, prl, pri, hboot.. latest everything update. hardware revision 003. baseband 2.15.00.07.28. S-off. what else..
my thoughts: cm 23 and up, savage 2.1 and up, and tiamat's latest all incorporated hdmi into their builds. i've never used nor have the ability to activate hdmi on my phone. so i'm thinking it's something to do with hdmi? every other rom from cm 21- and rc2- and sense roms seem to work perfectly fine.
i am currently running cm rc2 with savage zen 2.0.. are my days of flashing the lastest and badarse combos of cm and savage zen over? please help if anyone have any ideas and thanks in advance..
Click to expand...
Click to collapse
Strange indeed my friend. There have been many reports of bootlooping with cm7, and many can't recover. See the thread titled bootloops and no recovery. Its odd that older cm builds and sense work fine for you, and newer ones don't. Its interesting, your observation about the HDMI kernels. I wish I had some suggestions for you, but it appears as though you've exhausted all the things I would've suggested to you already. You've even ran ruu and rerooted. If that didn't work, I'm not sure what will...
Sent from my PC36100 using XDA App
going into recovery is fine. i've tried reflashing with ra mon 1.8, 2.2, and 2.3 recovery but still end up with the white screen boot loop. than i would switch to clockworkmod 2.5 and 3.0 and reflash the roms. they would all install fine with the recoveries saying "install from sd card complete". but when i reboot, it gets stuck on the htc screen! strange indeed..
losphn said:
going into recovery is fine. i've tried reflashing with ra mon 1.8, 2.2, and 2.3 recovery but still end up with the white screen boot loop. than i would switch to clockworkmod 2.5 and 3.0 and reflash the roms. they would all install fine with the recoveries saying "install from sd card complete". but when i reboot, it gets stuck on the htc screen! strange indeed..
Click to expand...
Click to collapse
Sounds like you tried everything before you even posted! At least you can run sense roms and older cm in the meantime, while you try to figure it out. Do other newer gingerbread builds flash and run for you? Or is it just cm7? I wish I had more to suggest, but like I said, it seems like you've covered your bases..
Sent from my PC36100 using XDA App
i've ran miks, myns, and fresh before from the sense side and all worked fine. from the gb side i've ran evolve, kings? (can't remeber right now), and cm starting from cm gingerbread 4 through 6.1.2 to cm7 nightly 21 where i got stuck. i have not try the newest gb roms outside cm. am downloading the latest from evolve now so will give it a shot.
f.y.i. to those afraid of cm roms, my current fig is rc2, sz 2.0 cfs wimax gb, with dark horse v1.0 cm7 rc2 theme and everything (minus hdmi) works flawlessly. i mean gps tracks and follows without drops, wifi works great, absolutely no issues with bluetooth, no random reboots, wimax connects quickly and doesn't drop, 3g hotspot works great, even 4g wireless hotspot works!! i swear it. tested it out the other night and it connected right away and started working. we used it on 4g for about 20 mins without drop.
if everything is working so great, why would i want to update roms? because the cm dev and team are badarse and i love their work (many thanks to you guys). plus titanium backup doesn't work...only app i use that gets fc. biggest irk though is that it just doesn't feel right not being able to flash the lastest builds..
losphn said:
i've ran miks, myns, and fresh before from the sense side and all worked fine. from the gb side i've ran evolve, kings? (can't remeber right now), and cm starting from cm gingerbread 4 through 6.1.2 to cm7 nightly 21 where i got stuck. i have not try the newest gb roms outside cm. am downloading the latest from evolve now so will give it a shot.
f.y.i. to those afraid of cm roms, my current fig is rc2, sz 2.0 cfs wimax gb, with dark horse v1.0 cm7 rc2 theme and everything (minus hdmi) works flawlessly. i mean gps tracks and follows without drops, wifi works great, absolutely no issues with bluetooth, no random reboots, wimax connects quickly and doesn't drop, 3g hotspot works great, even 4g wireless hotspot works!! i swear it. tested it out the other night and it connected right away and started working. we used it on 4g for about 20 mins without drop.
if everything is working so great, why would i want to update roms? because the cm dev and team are badarse and i love their work (many thanks to you guys). plus titanium backup doesn't work...only app i use that gets fc. biggest irk though is that it just doesn't feel right not being able to flash the lastest builds..
Click to expand...
Click to collapse
I will also say that I had good experiences with cm. It always ran smooth for me, and as you stated, everything worked. Same with all the other recent gingerbread roms have been flawless for me too. All the boot loop and no recovery issues, take it for what its worth. To each his own. I like all roms, but ill be on sense for a little while.
Sent from my PC36100 using XDA App
Have you tried flashing the FORMAT_ALL.zip from calkulin?
housry23 said:
Have you tried flashing the FORMAT_ALL.zip from calkulin?
Click to expand...
Click to collapse
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
From the OP ^^^^ He's wiped with calk's format all, used different recoveries, he's gone as far as unrooting and then re rooting. wiping again. He's tried everything I could think of. Reflashing recoveries(different versions), ran RUU's, re rooting....what's left?
thanks buckley
Sent from my PC36100 using XDA App
Guys, this is all over the forums now. Something in CM is causing these major problems that people are not able to recover from. One theory is that it's causing a bad block in the internal memory, which apparently, the Evo can't recover from.
I think I got lucky when it happened to me last month, where I suddenly white screened for no reason, while running a CM ROM, and I RUU'd my way out of it, but the problem has gotten much worse, obviously.
I loved CM, but at this point, I'm not stupid enough to try and run it anymore.
I hate to sound rash, but I'd lose any CM Rom's you guys are running until the Dev's can figure this one out.
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.
So I have my EVO rooted w/ unrevoked since last years launch. I have run Fresh ROM's up until about 6mon ago when I installed CM7 RC1, then 7.0, then 7.0.2. Last night I decided I wanted to try Synergy or Fresh again, so I updated Clockwork backed up the phone, then installed Synergy.
Everything went fine, wiped Cache/User/Dalvik, installed then rebooted. I was stuck at the Unrevoked splash screen, and about every 20seconds It would reboot and continue the cycle. I battery pulled went to Clockwork and Tried my Fresh ROM, did the same thing. Ok, So i said screw it, im gonna restore it. So I navigate Clockwork to the location i backed up to, then restore.
After a reboot, the unrevoked screen would just stay frozen forever, no ROM booting. So I still had my CM7.0.2 on the card that i flashed 5 months ago, and all be damned it worked back up and running in minutes, whew.
So this morning I am back at it, trying to install fresh again, and im going back throught the same unrevoked spalsh screen boot loop. Any help on figuring out what is wrong?
mrsmegz said:
So I have my EVO rooted w/ unrevoked since last years launch. I have run Fresh ROM's up until about 6mon ago when I installed CM7 RC1, then 7.0, then 7.0.2. Last night I decided I wanted to try Synergy or Fresh again, so I updated Clockwork backed up the phone, then installed Synergy.
Everything went fine, wiped Cache/User/Dalvik, installed then rebooted. I was stuck at the Unrevoked splash screen, and about every 20seconds It would reboot and continue the cycle. I battery pulled went to Clockwork and Tried my Fresh ROM, did the same thing. Ok, So i said screw it, im gonna restore it. So I navigate Clockwork to the location i backed up to, then restore.
After a reboot, the unrevoked screen would just stay frozen forever, no ROM booting. So I still had my CM7.0.2 on the card that i flashed 5 months ago, and all be damned it worked back up and running in minutes, whew.
So this morning I am back at it, trying to install fresh again, and im going back throught the same unrevoked spalsh screen boot loop. Any help on figuring out what is wrong?
Click to expand...
Click to collapse
You cannot install synergy with clockworkmod. It must be installed with amon ra. This is stated in the original post of the synergy thread.
Sent from my PC36100 using Tapatalk
Ok I guess I didnt see that part about Synergy. Howerver I just tried to install the latest Fresh rom, and it was doing the same thing (rebooting at the Unrevoked Screen).
However I was able to flash to the latest Cyanogen 7.0.3 Stable for EVO, so until I find a solution, I guess I am stuck w/ that in the meantime.
mrsmegz said:
Ok I guess I didnt see that part about Synergy. Howerver I just tried to install the latest Fresh rom, and it was doing the same thing (rebooting at the Unrevoked Screen).
However I was able to flash to the latest Cyanogen 7.0.3 Stable for EVO, so until I find a solution, I guess I am stuck w/ that in the meantime.
Click to expand...
Click to collapse
I would still try flashing Ra Recovery and seeing if you can flash Fresh ROM.
Also it could be ur SD card. Alot of times its not partitioned right or what not. I know cm7 leaves SD card alone for most part.
free the dirk
The solution is to get Amon Ra, so you can wipe properly and partition your SD card properly
might wanna wipe boot as well...usually fixes issues in such cases.
theidlemonk said:
might wanna wipe boot as well...usually fixes issues in such cases.
Click to expand...
Click to collapse
Last I used CWM you could not wipe boot without a custom script (ie. Calkulins format all, or VR_Superwipe)
Khilbron said:
Last I used CWM you could not wipe boot without a custom script (ie. Calkulins format all, or VR_Superwipe)
Click to expand...
Click to collapse
Amon RA recovery has that option under the wipe menu.
But then Calkulins format all or VR_Superwipe are good too. Gets the job done.
This is all very helpfull, I am going to try some of that in the next few days. I really didn't have any idea that SD partitions can effect the boot of a phone, Ill read about that as well.
Today I managed to get the Latest Stable CM 7.0.3 on my phone, but the experimental 7.1 wouldn't load, so I am going to stick with that. One of those things when you feel like you have read everything before you start upgrading, then you miss something and all goes to hell. Thanks for the help everybody.
theidlemonk said:
Amon RA recovery has that option under the wipe menu.
But then Calkulins format all or VR_Superwipe are good too. Gets the job done.
Click to expand...
Click to collapse
Yes I know this. I use ra recovery. However the OP uses CWM which is why I assumed you were instructing her to do this with clockwork.
Sent from my PC36100 using Tapatalk