Related
Hey all, this is my first post here and unfortunately its a question I have with CM7 Nightly #8..
I've been running CM7 RC1 since it's release and I've had no problems, no reboots, no lag- nothing. I've steered clear of nightlies because every time I flash one I get random reboots.
Today I picked up #8 did a factory reset/davlik/cache wipe and did a clean install and flashed over Chad's incredikernel for GB as thats the Kernel thats worked best for me on RC1. I restored my apps via Titanium Backup like usual and set up everything back to what I had.. ten minutes later my phone goes into a boot-loop.
Anyone else having these issues?
What verison of CWM recovery do you have?
I flashed 3.0.0.8 shortly after it was released. Prior to that I was on the 2 series and still had the issue. I just went and flashed back to RC1 which was more stable for me. Any thoughts?
Sent from my ADR6300 using XDA App
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.
When turning on my evo i get the White screen + vibrate, then it reboots to another white screen + vibrate, and then the ROM loads. Anyone know why this happens? I always perform full format prior to ROM installs.
omgzilla85 said:
When turning on my evo i get the White screen + vibrate, then it reboots to another white screen + vibrate, and then the ROM loads. Anyone know why this happens? I always perform full format prior to ROM installs.
Click to expand...
Click to collapse
What rom are you currently using and does it contain its own boot animation and splash screen? Have you experienced this with other roms or just the current one?
I am currently on Savaged Zen RC2. It happened while using Warm Z and CM7 also.
omgzilla85 said:
I am currently on Savaged Zen RC2. It happened while using Warm Z and CM7 also.
Click to expand...
Click to collapse
That is indeed odd. Download & flash a fresh copy of amon RA v2.3 and then, after you made a nandroid backup of your current setup. Wipe EVERYTHING except the SD card itself. Afterwards, reflash the rom of your choice and see if the double boot animation disappears. As a matter of fact, check your PM.
I'm having this problem too but I didn't notice it until I installed Savaged Zen RC2 the other day. When I install new roms I always at LEAST triple wipe data, cache and dalvik, and use Calk's format all.
It must be something to do with splash screen trying to install but not installing correctly or the fact that I've had my own custom splash installed.
Is this only after your first install of a ROM, or every time you reboot? I've been seeing this ever since I started using darktremor A2SD with an ext3 partition. It only does this on the first reboot after install, and then it's fine on subsequent reboots. I'm thinking it's normal. A2SD probably does some setup, then reboots.
If you're seeing it every time, or not using a2sd, then yes, it may be a problem.
The OP's problem was solved by re-flashing amon RA v2.3 then booting into recovery and wiping EVERYTHING except the SD Card itself. I've sent the both of you a link to download the version I use and sent to the OP.
posting & replying via the XDA Premium app
is this a problem? my phone does this too but it doesn't really bother me. I am running sz rc2.
Sent from my PC36100 using XDA Premium App
I am running into the same issue. It's only after a power down and not a regular reboot. I'm going to try the method suggested above to see if that solves the problem. I figure it's not a big deal, just not desirable.
Mine was doing it on Deck's rc6 then decided to stop. I got me a self-healer!!!
Ignorance = Bliss
Well the steps listed above just fixed the problem. I flashed to Amon RA v2.3, did a nand, wipe EVERYTHING but the sdcard and flashed CM7-nightly38, gapps and the savaged zen BFS 1.1.0 kernel.
Odd thing I found though is that when i tried to use Rom Manager to flash Amon RA v2.2.2 it would refuse to flash. Not sure that if there was something related to Clockwork Recovery that caused the double white screen or what.
Well I tried the newest recovery and did full wipe on everything, three times at that. No dice. Twice it rebooted without double splash screens but every time now it does it. Doesn't matter if it's normal reboot, reboot from recovery, or started from shut down. It's not a big deal to me, mostly a minor inconvenience. I mostly did the full wipe as an excuse to let me start clean on the CM7 final.
Hmm. Seems to be back on reboot for me. I might try a sense rom and see if does the same thing.
Sent from my CM7 Evo using XDA App
I'm having the same issue, I'm running a different splash screen currently, but same issue occurs. Splash, black screen, splash, boot animation, startup. It is really only a minor inconvienence, but it would be nice to fix it. I have this splashscreen, and this bootscreen. Running CyanogenMod-7 with SavagedZen1.1.0CFSHAVSWiMAXGB kernel. I can't pinpoint exactly when it started, but I want to say probably when I flashed SZ. The kernel runs great, so if thats causing it, I can just live with it for now.
I did see someone stated a reflash of the Amon RA recovery, and a full wipe and reinstall solves this. However, I also saw this thread that states its the way the newest SZ kernel is designed to boot that way? I'm willing to do a complete wipe, re install the recovery, kernel, and rom if necessary when I have some more time. Before I do can anyone confirm if this will for sure this corrects it?
Ok so here is my issue I hope some of you will have some incite.
I've been running CM7 7.0.3 for a while now but have been experiencing some issues so I wanted to go back to a sense ROM. I've flashed Skyraider 4.0 and Redemptive rEVOlution. Both give me the same problem after it flashes I reboot and get only to the 1st splash screen, HTC quietly brilliant. I've been using CWR 3.0.0.8 and RA_GNM 2.2.1, I get the same out come no matter what. If anyone has any suggestions I'm all ears.
Thanks
b1gd4ddyx said:
Ok so here is my issue I hope some of you will have some incite.
I've been running CM7 7.0.3 for a while now but have been experiencing some issues so I wanted to go back to a sense ROM. I've flashed Skyraider 4.0 and Redemptive rEVOlution. Both give me the same problem after it flashes I reboot and get only to the 1st splash screen, HTC quietly brilliant. I've been using CWR 3.0.0.8 and RA_GNM 2.2.1, I get the same out come no matter what. If anyone has any suggestions I'm all ears.
Thanks
Click to expand...
Click to collapse
3.0.0.8 has a known issue of not completely wiping. Do it 3 times or flash 3.0.0.7. You need to wipe data/factory reset, wipe cache partition, wipe dalvik cache, then flash.
Sent from my ADR6300 using XDA App
Thanks for the suggestion, I rolled back to 3.0.0.7 and still no luck. A little extra info just to avoid questions hboot .92 and 11.19 radio. This has got me stumped. I've tried roms both on rom manager and not on it. So I'm not sure what else unless the downloads were corrupted.
b1gd4ddyx said:
Thanks for the suggestion, I rolled back to 3.0.0.7 and still no luck. A little extra info just to avoid questions hboot .92 and 11.19 radio. This has got me stumped. I've tried roms both on rom manager and not on it. So I'm not sure what else unless the downloads were corrupted.
Click to expand...
Click to collapse
Use Clockwork 2.5.1.2 and report back and see what happens??
That did the trick man thanks to both of you
I'm trying to flash my ROM from virtuous unity over to virtuous quattro. I have installed the most recent version of clockwork mod and ROM manager. However when I attempted to flash I've gotten this common error. I searched it on Google and seems to be on other incredible s/2 devices. Is there a way to fix this issue? I downloaded the most recent version of the ROM as well. I mounted the SD after booting into recovery, security is off, wiped with system factory restore, and tried just about everything else. Can anyone help ?
Because Quattro is for IncS only...
I'm so fresh you can suck my nits...
I know virtuous has there infinity rom on the inc2 but last I remember you have to flash the rom then fast boot the boot.img from ukb for it to not boot loop, I don't know about quattro if this trick would also work
Sent from my Incredibly still working