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
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.
Hello, I could use some help with my Desire.
A few months ago I rooted my HTC Desire (Bravo, EU version) with Unrevoked3 and then tried a couple ROMS, like CM6 and MIUI. The installations all went fine without any problems and the ROMS worked as advertised.
I decided to go back to the stock 2.2 because of some app compatibility issues, using the backup I made from the recovery tool and have stayed with it since.
Now, whenever I try to install a newer ROM, like Aurora v04 or PyramidMod007, the installation never works, even though I always wipe/factory reset/wipe Dalvik cache before installing. The post-installation booting always freezes on the HTC logo screen for more than 20 minutes and I'm forced to remove the battery and restore my backup image.
The only ROM that I've tried and works is the latest MIUI.
Can anyone tell me what I'm doing wrong?
Are you wiping?
Are you downloading versions that fit in the stock hboot, NOT cm7 hboot?
Are you following ALL the instructions/requirements in the rom threads, including required partitions on SD card?
Hi,
I was playing around with the installing Ubuntu on my DHD, i relaised that I need a kernel that has loopback support (I dont remember flashing a kernel the only thing i have flashed is the Virtuous Quattro Rom rc3_spade)
I flashed the GLaDOS-cfs-V2.10 kernel onto my DHD and rebooted it.
It then got stuck on the white HTC logo screen.
I can get into clockworkmod recovery and i tired to restore a backup i had made prior to flashing the kernel but it says md5 sum mismatch.
I'm slightly stuck, i'm not an expert on these things but i do know a but but at the moment i am completely stumped.
Any suggestions?
Thanks
EDIT:
I found a way to get it back i put the quattro rom back onto my phone using the command prompt and adb but i reflashed the quattro rom its now all fine and its all wokring but im wondering,
when i tried to restore the rom (after i had reflashed it), why did it come up with md5 sum mismatch still?
:S This is confusing me .....
Currently i have been sat here for about half an hour waiting for RunnyMede AIO V6.0.4.3 too boot, and im just sat looking at the boot animation
Ive Checked MD5 Sums on the file and they are correct
I have been running Sandvold ICS and Cyanogenmod 7 for the last year and felt moving back too sense and so far i cant boot into any sense rom for some reason
I am on Stock Hboot
1gb EXT4 Partition
I have done a full whipe and i also use 4EXT Recovery Touch
Any Idea's?
Probably a very basic Answer to this but i cant find it >.<
Just pull the battery then boot into recovery, do full wipe, dalivik ect.. and try again.
Sent from my HTC Desire
Ive done that so many times >.<
Lol happened to me before when i tryed runny rom, took like 8 goes just to download it then bout 4 times to try and install it, it just kept on freezing when booting up. Why not try runnymede aio 6.1.1 s/e. Its very good.
Sent from my HTC Desire
Hi, I had similar problem with installing slim ICS for Desire [based Sandvold]. After couple of tries I notice, that problem seem be in boot.img, recovery didn't flash boot.img. Manual flash boot.img from your ROM zip archive over fastboot may resolve your problem too.
Thanks, may give it a go but just flashed cm7.2 and fallen back in love with it so ill take the knowledge on board again
..
stefi.com said:
Hi, I had similar problem with installing slim ICS for Desire [based Sandvold]. After couple of tries I notice, that problem seem be in boot.img, recovery didn't flash boot.img. Manual flash boot.img from your ROM zip archive over fastboot may resolve your problem too.
Click to expand...
Click to collapse
i want to try and see if this works but i dont understand what you mean. im having the same problem
Ryno101 said:
i want to try and see if this works but i dont understand what you mean. im having the same problem
Click to expand...
Click to collapse
He is saying you unzip the rom that you are trying to flash, then go into Fastboot and then use the command: fastboot flash boot.img
Personally never done it as i just gave up and moved onto cyanogenmod kangs, and there amazing currently
Not 100% sure about the command but someone will correct me if im wrong