ok i am running simpleroot evo 2.1 and i was trying to flash the stock froyo rom but everytime i go into recovery to flash it, it gives me a error when attempting to write the boot. error on line 5 to be exact. then on restart the phone goes into an endless white screen reboot. before the flash i did a phone wipe and cache wipe. neither work. has anyone else had this problem and is it fixable? i flashed the radio and wimax fine. and i had this problem attempting to flash the Ava froyo mod also. they all end in a nand restore....
thanks in advance
Damn bro, I'm sorry you are having such difficulties flashing Roms. What recovery are you using to flash? RA or clockwork? Whichever one you are using, try using the other one and see if you get the same error.
Sent from my EVO 4G(Extraterrestial Velocity Object from a 4th Galaxy) - **** is fasttt
tried clockwork and ra neither work, and its with all roms, its line 5 with the froyo roms, line 383 i think with other roms, and another line 400 something error, but there all with the boot. everything else seems go fine
Any ideas? I also used the htc stock 1.47 ruu to restore the phone and re root. Still getting the boot error
ok, well i didnt get any answers to WHY the error was being caused but i did manage to get the stock OTA rooted via unrevoked forever. restored the stock recovery on the evo then did the OTA update, flashed clockwork recovery afterwords then installed superuser from recovery. so basically stock froyo rooted, which was all i wanted. so for anyone else having problems you can still maintain root after the OTA if you install unrevoked-forever.
Please help I am stuck at the HTC screen after trying to flash to a custom rom. I can still access clockwork mod recovery. I tried the factory reset, I tried wainting but nothing...
i had the same problem today flashing leedroid 2.1, 3rd time got lucky and worked did nothing different at all
tried about 5 times already
Thank goodness I finally got the phone to work flashing with the AuraxTSense v7.6.1 ROM but this is not something I want. I want something closer to stock just with apps2sd and maybe wireless-n, ext4 abd updated apps like flash and googlemaps (no OCUV, since I don't believe in that, no theme mod etc)
i had that after trying to install leedroids 2.1 over the 2.0b so i had to do a full wipe and reinstall and it started to work
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.
I'm very confused as to what happened, and feel like I'm only making things worse so decided to come here. I've been rooted for about 2 months now after using Unrevoked Forever, and until last week everything was fine.
Using Rom Manager I attempted to flash Salvage Mod coming from Cyanogen 6.1.2. After wiping Data/Cache, when going to open the Zip Clockwork told me that the Rom did not exist in my SD card?
I redownloaded and tried again several times with no luck. I tried downloading other ROMS through my computer and putting them directly on my card and now I'm getting an error saying the Zip files are "(bad)"
Flashed RA Recovery through Rom Manager, the same errors, and now flashing back to Clockwork won't work. Any ideas what the problem maybe? Any solutions would be greatly appreciated
Have you tried booting to recovery directly and flashing a rom? I personally use CWM 2.6 and prefer to do all the work myself through recovery instead of hoping RomManager gets it right.
Yes I've tried booting into Recovery myself, keep getting the error that the zip. is bad
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.