Related
Today I started using CyanogenMod 7 nightly build #27 on my HTC Incredible. Everything was going great and I loved gingerebread. I used it for several hours and decided to make it permanent. I unmounted my sd and formatted it on my PC, after making a copy of all its contents of course. I re-mounted the card and started getting low space warnings, so I figured I should just restart. When I restarted, Cyanogen went into an infinite boot loop. No worries, I had a nandroid backup on my PC from a few hours before Cyanogen. I flashed back to rooted 2.2 Sense stock rom. New issue, I can't access anything on the sd. It appears empty, and none of my widgets can load. So I figured why not just start all over re-root and all of that. I followed a downgrade guide for an out of the box experience,(shouldnt have). The downgrade seemed to be successful but now my phone only boots to the white screen with the skateboarding androids. I have Bootloader, Reboot, Reboot Bootloader, & Power Down. I dont think I have root and I dont have clockwork anymore. Maybe if I could get clockwork back I could get back to 2.2 at least and use rom manager to get back to cyanogen 2.3.
What can I do???
SOLVED
Goto:
http://www.incredibleforum.com/foru...kwork-hangs-htc-incredible-splash-screen.html
Ok, the easiest way to fix this:
1. Format your sd card to FAT32 on your computer
2. DL this recovery zip: http://fourty.net/~berzerker/bamod/PB31IMG-red.zip
3. Place that zip on the root of your sdcard, rename to PB31IMG.zip
4. With the phone off, insert sdcard
5. Hold "Volume Down" and power button until a white screen pops up
6. It should scan for files, and find the zip on the sdcard
7. Press "Volume Up" to confirm update, you should see a progress bar top right.
8. When finished, select "No" when asked to reboot
9. Select "Recovery" with volume keys, confirm with power button.
You should now boot into ClockworkMod recovery. Wipe all data/factory reset, then format your sdcard (optional, just make sure PB31IMG.zip gets erased). You can then mount usb mass storage from "mounts" menu, and copy over CM7.
Stuck at HTC Incredible screen
Hey,
Thanks so much for your quick reply! I was able to flash the recovery you linked me too which has made my day a lot better already, but it seems its not quite over yet.
I wiped all the data, wiped the cache, fomatted the sd, mounted the sd to my pc and copied over CM7.
The first try I also copied over the signed google apps package I received from rom manager, which was in my backup.
Installed them both and the phone never made it past the white HTC Incredible Screen.
So I wiped again and only installed CM7. Same issue.
I have a nandroid backup of 2.2 rooted but otherwise stock HTC Sense rom, but I can't find the recovery on the sd. I copied over my entire old clockwork folder, but its nowhere to be found. I realize the recovery img you gave me looks a lot like clockwork but is titled BAMod Recovery. Could that prevent me from seeing the clockwork folder?
Thanks so much for your help with this!
I'm going to try flashing the radio back to 2.xx
and then try CM6 stable and see what I can get
FU3L said:
I'm going to try flashing the radio back to 2.xx
and then try CM6 stable and see what I can get
Click to expand...
Click to collapse
NO!!!
Flashing a radio is probably not the greatest idea.
Instead, do a search for clockworkmod recovery for the inc. The link I gave you was the one I had on hand, since I wrote all that at midnight lol.
Another thing I'd do is to re-download CM7 from the official teamdouche mirror site, along with g-apps, as I have a feeling your backups are somewhat corrupt.
Ok I won't reflash the radio. But right now the radio is 1.xx
Doesn't CM7 require a 2.xx radio? It rolled back during the stupid downgrade I did.
I've started downloading CM7 and g-apps again. And I will replace BAMod with clockwork. I can do that with the same steps as before right? It will just overwrite BAMod?
FU3L said:
1. Ok I won't reflash the radio. But right now the radio is 1.xx
Doesn't CM7 require a 2.xx radio? It rolled back during the stupid downgrade I did.
2. I've started downloading CM7 and g-apps again. And I will replace BAMod with clockwork. I can do that with the same steps as before right? It will just overwrite BAMod?
Click to expand...
Click to collapse
1. In that case, yes, flash a 2.XX radio.using a PB31IMG. Froyo and gingerbread both require it.
2. Yep, just follow the steps, it'll just overwrite it.
I flashed the radio successfully, something worked!
However I'm having a hard time getting clockwork. I donwloaded clockwork 2.5.0.7 img
I then put it in a zip called PB31IMG
The phone picks up on it and flashes through some things pretty quick the last being parsing PB31IMG.zip....
Then it just jumps back to HBOOT. It doesn't ask if I want to update like the radio did.
I even tried to push it over fastboot from my pc, but everytime it says Failed remote not allowed.
Since I have the correct radio I am trying to flash CM6.1 to see what happens. BAMod is installing it now. If I can get in and get rom manager it can flash clockwork.
Thats my thinking anyway
It says it installed CM6.1 successfully, but still hangs at white HTC Incredible screen on startup
Wiped and installed CM7 successfully but still hung on white HTC Incredible screen.
Should I try using fastboot on my PC to erase the recovery partition? clockwork just gets rejected everytime, the only thing thats seemingly different about the phone now is having BAMod recovery install things instead of clockwork, which worked...
I miss my incredible
Flashed Amon Recovery, installed CM7 build #27. Still hanging on boot screen.
VICTORY!
Here's how I got it working again:
Head over to h**p://dougpiston.com/?page_id=108 site (due to me being an absolute noob to this forum, I can't post links, so just replace h**p with http) , and pick up the PB31IMG version of the original stock HTC image. Flash it, and everything should start up as fresh as the day you bought it. It seems it loses root and custom recovery though, so just reapply and all should be well.
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.
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?
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