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.
Related
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.
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
I am having trouble flashing a new kernel and it is driving me crazy. I am running CM7 with the Tiamat 3.3.7 kernel and wanted to update to a new Tiamat version. I downloaded the zip and placed it on the SD card.
I booted into Recovery using RA and performed a Nandroid backup. Then wiped the cache and davlik. Then flashed the kernel. Screen said it was installed correctly.
What is the next step? I get back to the main screen on RA and I choose "reboot system now", correct? When I do this, it either 1) loops the htc evo screen or 2) takes me back to the bootloader menu.
I have tried the battery pull trick and re-flashed the kernel a few times now and nothing seems to fix the problem. Is there a simply step I am missing here?
nvmd, it finally kicked over and rebooted cleanly. thread can be deleted if need be. thanks.
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
First off i want to make known that I have been on may different custom roms & just comming from RCmix 234 2.7.
The other day I tried using cwm to restore a previously saved rom that I had backed up & switched to many times before but I would not work. Then today I tried to go back to a previous version through recovery, which I have done in the past. (I Believe I was having superuser issues)
I have tried multiple different roms & the device keeps getting stuck on the white HTC screen before going to the bootloader screen for the particular rom I am trying to install.
I have even started over again by going back to basics.... PD98img, root, s-off, eng-off, install root checker, & rom manager...... up to this point everything is working but If I try to install either via cwm, or through recovery I keep getting nothing but the White HTC Screen
Any ideas before I attempt to put all back to stock again.... & send in for repair?
Many thanks in advance.
Ok Now.... i have been able to restore the old backup I have using recovery, I attempted through rom manager but it would only just opened recovery so I attempted to flash any zip from a new rom...... but why wont it work as it would before? It only freezes on the white htc screen
HTC White Screen
Anyone know why when trying to flash a new rom that it hangs @ the HTC White Screen?
System Partitions?
Since I all of a sudden cannot reboot after flashing a rom.... does my system partition free space of only 14.8MiB be the cause of why it wont boot fully when asked to re-boot from recovery?
Am I forever stuck with the backup I created weeks ago, its the only rom that goes to the boot img of the rom which is just past the white htc screen.
Thanks for helping.
Well I hope I solved it.... somehow Recovery seems changed to mabey a new version, & it seems that the roms I was using were ext3 roms & I was led to believe I needed the ext4 full wipes which modded my configuration to ext4.
Switched configuration back to ext3 & now roms boot up past the white screen.
i have the same problem with this rom RCMmid3d Bliss i stuck in splash screen..i tried the recoveries 4ext and clockworkmod but at all i stuck there..
shadowman110 said:
i have the same problem with this rom RCMmid3d Bliss i stuck in splash screen..i tried the recoveries 4ext and clockworkmod but at all i stuck there..
Click to expand...
Click to collapse
I found a fix.... restore your saved rom, assuming you have one.
1) Update cwm to the newest version
2) reboot into recovery & find the format ext3 option & format to ext3
3) Choose whichever rom you like (I went back to RCMIX 3D 234 V2.7) Install
4) Reboot & be rid of that pesky issue
Please hit the thanks if this helped!
gixer131 said:
I found a fix.... restore your saved rom, assuming you have one.
1) Update cwm to the newest version
2) reboot into recovery & find the format ext3 option & format to ext3
3) Choose whichever rom you like (I went back to RCMIX 3D 234 V2.7) Install
4) Reboot & be rid of that pesky issue
Please hit the thanks if this helped!
Click to expand...
Click to collapse
Nice find!
the 3.5 sense roms are temperamental at best to some users right now, though capy of rcmix with his new update seems to be working well just keep in mind its truly a beta still. as for issues with flashing and getting the roms to fully boot is mostly a recovery issue and that only. as long as u r not only wiping all before the flash, but also formatting everything there should be very little to nothing left that could cause any issues at all. i recommend first using ext4 for recovery especially if that is the type of roms u r using. if the rom doesn't format the system to ext4 and u have wiped with cwm recovery u could of reverted back to ext 3 and now your rom is going to loop or lock up for sure. u can always flash new version of ext4 if ur back ups don't restore also, this happenes if a rom manager update is an issue with ext4 and on a few of the old non-final versions. good luck, though u seem to be back up and running already