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?
Related
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.
...
Hello all
I just updated to 3.0.0.5 and now when I reboot into revocery via Rom Manager I get to the HBOOT screen with the only options for:
BOOTLOADER
REBOOT
REBOOT BOOTLOADER
POWER DOWN
I don't get the usual black background with green letters? From what I've read it should go to the black background but now with Orange letters?
Please advise at what I'm doing wrong. Which option should I use to get to clockworkmod 3.0.0.5
Thanks in advance
-g
A lot of the current ROMS are not compatible with the new CWM and many people experienced the same as you. In RM, scroll all the way down and go back to the previous version.
patsfan1130 said:
A lot of the current ROMS are not compatible with the new CWM and many people experienced the same as you. In RM, scroll all the way down and go back to the previous version.
Click to expand...
Click to collapse
The oldest version available is the current one I am on 3.0.0.5. There are newer version .6 .7 and .8? Do you know if those versions will produce the same issue?
After much reading this cwm3 is causing lots of problems. I've searched the forums for a write up on how to flash back to 2x but haven't found one. Does anyone have a quick write up to get this done either through fastboot or adb?
Thanks
-g
I have a thread in the dev forum updated today that explains exactly what you want.
I had issues when I previously upgraded from 2.5.1.2 to 3.0.0.5 when I tried to restore a backup made with 2.5.1.2. It restored and got to the point of loading the kernel where the boot animation was animating. It just sat there for about 20 minutes so I pulled the battery and went back to 2.5.1.2 and restored the same backup and it worked. I wanted to see if 3.0.0.8 had fixed restores and I found it hasn't in my case although I do see how others don't have this problem. Just some info before I do a restore I always do a full wipe including boot and system. Oh and I flashed 3.0.0.8 in Rom Manager and the text in recovery is orange. Does anyone know why I can't restore a backup made from 2.x with 3.x recovery loaded?
tdiman said:
I have a thread in the dev forum updated today that explains exactly what you want.
Click to expand...
Click to collapse
Awesome tdiman! Thanks for the write up, it worked. I just needed to enable wipe!
sitrucz said:
I had issues when I previously upgraded from 2.5.1.2 to 3.0.0.5 when I tried to restore a backup made with 2.5.1.2. It restored and got to the point of loading the kernel where the boot animation was animating. It just sat there for about 20 minutes so I pulled the battery and went back to 2.5.1.2 and restored the same backup and it worked. I wanted to see if 3.0.0.8 had fixed restores and I found it hasn't in my case although I do see how others don't have this problem. Just some info before I do a restore I always do a full wipe including boot and system. Oh and I flashed 3.0.0.8 in Rom Manager and the text in recovery is orange. Does anyone know why I can't restore a backup made from 2.x with 3.x recovery loaded?
Click to expand...
Click to collapse
The only thing I've heard is that it works. When I've had a boot animation that loops like that, the following things have worked for me:
boot back into recovery, wipe the cache, then go to advanced and wipe the dalvik cache. Reboot. Give the boot animation a good 5 minutes before giving up. This is especially needed when going between different ROM versions (e.g. skyraider to CM7, non-sense to sense, etc.) .
Also, did you try booting it up twice after the boot animation loops before reflashing CWM? Sometimes all it takes is a battery pull and reboot. It does happen randomly.
I'm not convinced its related to the CWM version directly because I see that happen all the time randomly. Of course, I'm not convinced its not related either
tdiman said:
The only thing I've heard is that it works. When I've had a boot animation that loops like that, the following things have worked for me:
boot back into recovery, wipe the cache, then go to advanced and wipe the dalvik cache. Reboot. Give the boot animation a good 5 minutes before giving up. This is especially needed when going between different ROM versions (e.g. skyraider to CM7, non-sense to sense, etc.) .
Also, did you try booting it up twice after the boot animation loops before reflashing CWM? Sometimes all it takes is a battery pull and reboot. It does happen randomly.
I'm not convinced its related to the CWM version directly because I see that happen all the time randomly. Of course, I'm not convinced its not related either
Click to expand...
Click to collapse
First, thank you for your response. I'm not going to spend too much time on this since 3.x is the new standard. I use Cyanogenmod 7 dailys as my daily driver and rEVOlution 2.2 as my sense rom backup. So, if after a restore and rebooting and then wiping cache and davlik and possibly reflashing a froyo kernel, incredikernel 12/20, doesn't solve it I'll just restore from 2.x recovery, upgrade recovery, and then get a new backup. I'll do the same for Cyanogen and call it a day and start using cwm 3.x.
After testing I was unable to restore my rEVOlution rom using 3.0.0.8 from 2.5.1.2. I wiped cache and davlik and flashed a froyo kernel and still no dice. It was strange even though I could only see the boot logo the rom was fully booted as I had voicemails and I heard the voicemail notifications but the home screen never came up. I rebooted and still the same thing. So I reflashed 2.5.1.2 restored rEVOlution upgraded recovery then got a backup. I did the same for my Cyanogen nightly and I'm on 3.0.0.8 now for good. I wanted to pass this on to others. If I want to restore an older backup I'll just restore recovery to 2.5.1.2 and do a restore.
Hi, so I'm super green but itching to load custom kernel and rom... So my Evo is rooted and have seen some pretty sweet roms, lol, kinda scared to flash and not sure what roms go with what kernals, do I even need a new kernal? What I really want is a kernal I can overclock to 1198mhz, and a rom build based on honeycomb and or gingerbread that is 100% stable or as close as I can get... Help? Lol...
Sent from my PC36100 using XDA Premium App
hahah exited aren't you... welcome to the root world!
you asked for hc/gb. google hasnt released hc source code yet, probably not until ice cream, so there is none of that. you can however download cyanogen(mod) 7, which is almost totally stable.
http://mirror.teamdouche.net/?device=supersonic
there's the mirror link. download either rls4 or nightly 33. nightly 33 is a bit funky bcuz cyanogen is pulling an april fools prank saying he sold cm to teh duck revolution, and the rom is now called 'teh duck uber distro'. so maybe rls4 or just wait for the next nightly.
everything works. 4g (with one bug that there is an annoying fix for), hdmi (download hdmwin from the market) gps (with a fix) and everything else is perfect. it is still in beta/nightly stages, but should be done soon. it is my daily driver, as well as many other peoples. this rom is crazzzy popular. try it for sure.
start with stock kernel, but i'd try both savaged-zen and tiamat kernels on it. they will both give you much better battery. tiamat tends to give slightly better performance/quickness but savaged-zen (on custom SAVAGEZEN governer) gives fantastic battery. try them both!!!
again, welcome to the community. hope this helps.
Where do I get the kernals? And what process do I use? I have clockwork premium... I just don't wanna miss a step a jack myself
Also, is it gonna wipe my phone, do I need to wipe it? No issues with that though as I do it all the time... And thank you so much for the feedback BTW, still a little confused...
Sent from my PC36100 using XDA Premium App
ok, first of all, clockworkmod isn't the recovery you want to be using. download amon-ra's recovery here http://forum.xda-developers.com/showthread.php?t=705026 make sure you get the pc36img.zip. put the pc36img.zip on the root of your sdcard (that means not in any folders) MAKING SURE IT IS NAMED EXACTLY PC36IMG.ZIP. aka just dont rename it. then power off your phone, and once it is off, hold power and volume down. you will see a white screen with scateboarding droids at the bottom. this is your BOOTLOADER SCREEN also known as hboot, and you see it quite often. so hboot will scan your sdcard, and find the pc36img.zip. hit volume up to accept the 'update'. then once it is done, volume up again to reboot.
you can download kernels from the evo android development subforum right here at the xda.
so first flash your rom. you can either boot up into it, or just flash the kernel right away. flash the kernel just like you would a rom, but without wiping.
enjoy.
any other questions, ask away.
dkdude36 said:
ok, first of all, clockworkmod isn't the recovery you want to be using. download amon-ra's recovery here http://forum.xda-developers.com/showthread.php?t=705026
Click to expand...
Click to collapse
100% agree. Amon Ra imo is the much more stable & user friendly recovery
Alright, so, can I do all this just from my phone? Is a pc recommended? Will my stock kernal overclock? Never flashed a rom before, I'm an electronic/computer tech so I pick up shniz pretty quick but still don't wanna b---- this sucker...
Sent from my PC36100 using XDA Premium App
you can do it all from your phone if you want. i perfer downloading on my pc and transferring from there in case i want to modify anything, but you can always just dload on phone. make sure the pc36img.zip isnt in download folder or anything if you do. it needs to be on the root. your stock kernel can't overclock sadly. if you have never flashed a rom before, then cm7 will be crazy different than stock rom. most custom rom's are based off the stock htc software, just modded. cm7 is aosp, which means it is stock GOOGLE software. htc spends quite a few months modifying htc sense into google software, so the speed and memory increase is very noticable. just wipe data, cache, and dalvik cache when switching roms. you might want to backup your apps and their data using titanium backup. just dont backup system data, that can cause problems. then flash the rom after wiping, flash any kernel or addons you want (dont forget to flash gapps if it is an aosp rom, bcuz if you dont u wont have the market or anything) and reboot. for any other mods you install after that on the same rom, just wipe cache and dalvik cache and then flash away. wiping data between roms is always reccomended. if you want to stick with the cm7 nightlys, then all you need to wipe is cache and dalvik. there is never much of a problem with just flashing one over the other without a data wipe.
and forgot to mention, you cant control amon-ra recovery with rom manager. but then again, rom manager is just a touch screen version of recovery. you get used to the volume/power keys pretty quickly.
ok, im freaking out now, my phone is locked in the cm little surfer droid with the arrow circling around been constantly running for about 45 mins, im fuct, really fuct without my phone!!! its my only internet too!!! PLEASE HELP!!!
Did you do a factory wipe, Clear the cache & wipe Dalvik?
Sounds like it just wasn't a good install. Do the above in recovery & reinstall your ROM
ya did you wipe? doesnt sound like it. make sure data, cache, and dalvik cache are all wiped successfully. also make sure you are using amon-ra recovery. cwm can sometimes give you problems.
Hey all-
So I've flashed to CM7 3 times now and each time I get everything setup correctly, my apps restored etc. But as soon as I go to reboot I get stuck on the CM7 loading screen forever. The image is animated, but it will not finish.. it will go all night if I let it.
I have a feeling the issue is in the method im using to install. I'm coming from Fresh 3.5 using Amon Ra recovery. I cleared all user data, dalvik cache and then flashed the rom. I then flashed gapps and it boots into CM7 fine. The reboot is the problem. Am I missing a step? Should I be clearing/formating/deleting more before flashing the new ROM?
Thanks guys. This forum has been a huge resource for me in the last couple weeks. <3
Coreyfuncrusher said:
Hey all-
So I've flashed to CM7 3 times now and each time I get everything setup correctly, my apps restored etc. But as soon as I go to reboot I get stuck on the CM7 loading screen forever. The image is animated, but it will not finish.. it will go all night if I let it.
I have a feeling the issue is in the method im using to install. I'm coming from Fresh 3.5 using Amon Ra recovery. I cleared all user data, dalvik cache and then flashed the rom. I then flashed gapps and it boots into CM7 fine. The reboot is the problem. Am I missing a step? Should I be clearing/formating/deleting more before flashing the new ROM?
Thanks guys. This forum has been a huge resource for me in the last couple weeks. <3
Click to expand...
Click to collapse
I think i know what ur doing wrong first flash the rom then reboot then go back to amon ra wipe cache and then flash gapps and if it still doesnt work then do the exact same things but with clockwordmod (which u can both flash from rom manager).
Sent from my PC36100 using XDA Premium App
Followup Question:
Can I restore a Clockwork Backup using Amon RA? Amon wants to check the nandroid folder for backups..and I don't have any nandroid backups (not sure how I didnt do one). can I move a existing clockwork backup from the clockwork folder to the nandroid folder on my SD's root and use that?
Or does anyone have any suggestions on how to flash to clockwork? Now when flashing to CM7 or Fresh I'm getting stuck on the loading screen.. Thanks
So, it looks like the issue is with gapps. When I flash CM7 it works great..once I reboot into recovery, flash gapps, I get the freezing error. I am using version:
gapps-hdpi-20101113-signed.zip
Is this what I should be using?
No there's a newer version you can use let me see if I can find it and get you a link...
Edit: I found the one on my SD card its not the newest but it should work
http://db.tt/YuaCnd9
Sent from my nightly EVO
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