Hello, first i would like to say i have spent over 10 hours trying to flash a custom ROM on my incredible all of which include searching through endless forums for people with similar issues. current specs are:
hboot: .92
radio: 2.15.00.07.28
clockworkmod: 2.5.1.2
I used unrEVOked 3 to root.
I have tried to flash redemption 2.3, cyanogenmod 6, skyraider 3.5, and the stock incredible 2.2 image which i saw in another thread here. What happens is the roms install fine and boot up. At some point, usually within the first couple minutes they are booted up, the phone restarts and will not boot back into rom. Any help would be appreciated.
Are you doing a complete wipe before installing the rom?
If so try installing the rom from recovery (don't install from Rom Manager), and flash a different kernel. Then reboot and see if the problem still persists.
Are you restoring apps and data? Restoring system data is always a quick way to get weird issues...also, as mentioned above, wipe cache, dalvik, and do factory wipe. As a practice, I've done all three 3 times each, and never run into any such issues. Think of the bathroom...wiping too much might take longer, but not wiping enough will definitely cause issues later
HTCInc-redibly re-ENGINEERED
baboonsRus said:
Are you restoring apps and data? Restoring system data is always a quick way to get weird issues...also, as mentioned above, wipe cache, dalvik, and do factory wipe. As a practice, I've done all three 3 times each, and never run into any such issues. Think of the bathroom...wiping too much might take longer, but not wiping enough will definitely cause issues later
HTCInc-redibly re-ENGINEERED
Click to expand...
Click to collapse
Not sure that 3 times is necessary, but I like the analogy.
baboonsRus said:
Are you restoring apps and data? Restoring system data is always a quick way to get weird issues...also, as mentioned above, wipe cache, dalvik, and do factory wipe. As a practice, I've done all three 3 times each, and never run into any such issues. Think of the bathroom...wiping too much might take longer, but not wiping enough will definitely cause issues later
HTCInc-redibly re-ENGINEERED
Click to expand...
Click to collapse
LOL love that last bit.
Sent from my Droid Incredible running Myn's Warm TwoPointTwo RLS5.3.
Thanks guys, i already did wipe dalvik cache, wipe cache, and do a factory wipe each time before installing the various ROMS. none of this fixed the issue. i found a back to stock image, and i took it into verizon and they are sending me a refurb. than its back to root again!
Related
It keeps happening on my evo and im using the newest fresh rom and the current radio http://tweetphoto.com/33676911
jxb25 said:
It keeps happening on my evo and im using the newest fresh rom and the current radio http://tweetphoto.com/33676911
Click to expand...
Click to collapse
that's called a Force Close (FC). It usually happens with an unstable ROM/unstable app but more often it happens when you don't wipe (Cache/Dalvik) before installing a custom ROM.
Backup any important data that's not already on your sdcard, go back into recovery, wiple your cache and dalvik, and flash the ROM again. see if that helps you
initial said:
that's called a Force Close (FC). It usually happens with an unstable ROM/unstable app but more often it happens when you don't wipe (Cache/Dalvik) before installing a custom ROM.
Backup any important data that's not already on your sdcard, go back into recovery, wiple your cache and dalvik, and flash the ROM again. see if that helps you
Click to expand...
Click to collapse
even if im coming from the old fresh to the new fresh i still have to wipe
I'm not familiar with Fresh's ROMs, if you read his threads carefully I'm sure he'll tell you which version upgrades require a wipe and which don't. Usually a drastic upgrade will require a wipe. In your case a wipe will most likely fix these FCs
With the learning curve for the EVO still growing, its usually a good idea to wipe data/cache/dalvik when flashing new roms. Even updates. I haven't seen too many "No Wipe Necessary" around this forum. As long as you've got Titanium or MyBackup, wiping isnt as big of a headache as it used to be. Hope you get things figured out. Screwing with these phones can get frustrating. Dont know how many times I wished I hadnt messed with anything.
well i just wiped and reloaded fresh so hopefully this will fix everything
Can anyone help me?
I am running SkyRaider 3.1 with the Hydra SSUV kernel.
I ran ClockworkMod through Rom Manager, selected wipe cache, then wiped dalvik cache and the phone is now stuck in the boot sequence at the Droid eye screen. It's now been about 20 minutes, so I assume it has had enough time to rebuild itself.
Any ideas? I have a nandroid backup from a few days ago, but I would like to avoid doing that.
joehero said:
Can anyone help me?
I am running SkyRaider 3.1 with the Hydra SSUV kernel.
I ran ClockworkMod through Rom Manager, selected wipe cache, then wiped dalvik cache and the phone is now stuck in the boot sequence at the Droid eye screen. It's now been about 20 minutes, so I assume it has had enough time to rebuild itself.
Any ideas? I have a nandroid backup from a few days ago, but I would like to avoid doing that.
Click to expand...
Click to collapse
It should have completed by now, I hate to say pull the battery.... but if you are really stuck.
go back to recovery wipe Dalvik and Cache Partition, try booting again, it will take quite a bit of time to reboot this time.
If that does not work use your nandroid backup.
BTW always nandroid before making any changes to your phone that way you lose nothing, even if you think they are quick, easy or minor. Hardware has a way of keeping us humble.
Thanks for the recommendation. I had pulled the battery and figured I would try booting to recovery and wiping the cache again to see what happened. Did that and booted in a minute.
Currently doing a new Nandroid backup...
I am running Myn warm 2.2 rls 3. I will be going to rls 4 shortly. I have yet to establish a procedure for updating/switching ROMs that works. I have gone from one release of a rom to another and only wiped cache and dalvik. Sometimes this works and other times not. I have had best results wiping data, cache, and dalvik, but then I have to get my phone back up-to-date. I use Titanium Backup (paid) and it restores pretty well. Again best procedure that works consistently for me is to restore only user apps and data, but then I have to resetup homescreen settings, ringtones, speed dial, bluetooth pairings, wifi keys, etc. I have run into problems when restoring system data with TB. Any ideas for a procedure that works consistently?
To go from RLS3 to RLS4 you should only have to wipe dalvik and cache.
To go from one version of CyanogenMod to a newer one, you only need to flash the update.
To go from two completely different ROMs, you have to wipe data and cache. You can restore WiFi, Bluetooth, and Phone settings via TitaniumBackup, in addition to all your apps.
Doing a search on here for five seconds would have gotten you all of these answers.
drmacinyasha said:
To go from RLS3 to RLS4 you should only have to wipe dalvik and cache.
To go from one version of CyanogenMod to a newer one, you only need to flash the update.
To go from two completely different ROMs, you have to wipe data and cache. You can restore WiFi, Bluetooth, and Phone settings via TitaniumBackup, in addition to all your apps.
Doing a search on here for five seconds would have gotten you all of these answers.
Click to expand...
Click to collapse
I have not gone to a newer release of Myn yet. The recommendation is to do a full wipe. I will try cache and dalvik, but in the past with other roms this has caused problems.
Not interested in CM, but thanks for the info.
I have not yet been able to determine what to restore for bluetooth or phone settings that was why I was asking.
BTW, I did search (took me much more than 5 mins) and found nothing helpful to my situation.
When i went from rls3 to rls4 i only wiped the cache and dalvik and i got force closes. I then wiped everything and reflashed and i havent gotten any problems. So the best thing is to wipe all at least for me. I dont really know about the other stuff, i only back up apps
Sent from my PC36100 using Tapatalk
I'm really enjoying CM6.1.1, however I'd like to update my PRL and the only way to do that is to NANDroid backup CM and flash a Sense based ROM.
I did the backup, downloaded Fresh ROM, did a full wipe and even did a separate Cache wipe and then Dalvik Cache wipe. Then I flashed Fresh. The installation goes fine and I reboot.
I hit the white HTC Evo 4g splash and that's it... it just hangs for more than 5 minutes I've waited. I did a battery pull and booted again and it would just hang. Then I did a full wipe, cache wipe and dalvik wipe and rebooted, still just hanging.
I thought I might have gotten a bad download so I tried MYNs warm 2.2 just in case and the same deal.
Is there something that's done to the phone after CM6.1.1 is installed that prevents a Sense ROM from booting up?
thanks for any help!
danootz said:
I'm really enjoying CM6.1.1, however I'd like to update my PRL and the only way to do that is to NANDroid backup CM and flash a Sense based ROM.
I did the backup, downloaded Fresh ROM, did a full wipe and even did a separate Cache wipe and then Dalvik Cache wipe. Then I flashed Fresh. The installation goes fine and I reboot.
I hit the white HTC Evo 4g splash and that's it... it just hangs for more than 5 minutes I've waited. I did a battery pull and booted again and it would just hang. Then I did a full wipe, cache wipe and dalvik wipe and rebooted, still just hanging.
I thought I might have gotten a bad download so I tried MYNs warm 2.2 just in case and the same deal.
Is there something that's done to the phone after CM6.1.1 is installed that prevents a Sense ROM from booting up?
thanks for any help!
Click to expand...
Click to collapse
No sometimes recovery doesn't wipe everything correctly... downlload caulks format all and then flash sense rom. Should fix your problem!!
Sent from my PC36100 using XDA App
!!
I think i figured out what the problem is.
I flashed the latest radios, that is, i flashed the leaked ones (ending in .19 i think)
So I don't any of the roms i was trying to flash were compatible with the new radio.
At least that's what I read in some forum.
After nandroid backing and restoring and wiping things multiple times, i'm too lazy to try flashing an older radio so i might just wait till a new ROM based on 3.70 comes out.
danootz said:
!!
I think i figured out what the problem is.
I flashed the latest radios, that is, i flashed the leaked ones (ending in .19 i think)
So I don't any of the roms i was trying to flash were compatible with the new radio.
At least that's what I read in some forum.
After nandroid backing and restoring and wiping things multiple times, i'm too lazy to try flashing an older radio so i might just wait till a new ROM based on 3.70 comes out.
Click to expand...
Click to collapse
radios have nothing to do with it. they base roms off new ota so that you can get the benefits of the changes not the radios. You can flash the original radio that came with the evo and it would not affect the rom. The radio controls your signal strength and wimax strength. which is why there is a thread with all the different radios because each phone reacts different to each radio.....
Edit: Still not fixed. Any help would be appreciated.
Hi all. I'm currently using MIUI and want to swith to CM7 for 2.3 and 4G. I've been on the Cyanogen forums but to no avail. I have so far tried the following...
1. Flash from MIUI to CM7 #8 through rommanager with wipe.
2. Flash from MIUI to CM7 nightly 8, 12, 17 through Clockwork with full data and cache wipe.
3. Flash from MIUI to CM6 to CM7 through clockwork w/ full wipe.
4. Flash Amons recovery in rommanager and flash from MIUI to CM7 nightly 17 w/ full wipe.
I am currently at a loss. Please throw any suggestions my way.
- Nick
What exactly are you wiping when you say full wipe?
Try flashing calkulin's format_all.zip, then cyanogenmod, then gapps, all within one recovery session (no rebooting/restarting between flashing each one)
Sent from my hand with XDA Premium installed
Try a full wipe, cache, dalvik, and data. Then reflash the rom.
By full wipe I mean data/factory reset, then wipe cache, then dalvik.
Trying Calkulin now. On Cyanogen forum someone suggested a different kernel. I've never flashed only just a kernel. Would I use the same method as flashing other zips?
That's correct, just wipe dalvik and cache before doing so.
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
I use amon RA recovery and when I was stuck in a boot loop I would wipe data/factory reset, cache, dalvik cache, as well as wipe the system. That did the trick for me. Best of luck!
PS. Not sure of you can wipe system via clockwork mod, I used it briefly before I got aggravated and flashed a better recovery img IMO.
hTC Evo CM7-n17
You can do a full wipe in clockwork:
factory/data reset, and wipe cache from the main screen, then navigate to advanced and then wipe dalvik cache.
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
deaconzero said:
The reason I've been using clockwork is because I like using Rom Manager, but I'm not against Amon if it's the answer. Though, I've now tried it, and it doesn't seem to be.
I've been doing the wipes you're suggesting since the beginning. Those aren't doing it. I have a few ideas that I didn't try last night. Gave up after about hour 7 of trying different things.
My next experiment is to switch kernels. But I'm also thinking there could be a problem w/ my Titanium backup. I don't remember specifically, because I didn't notice it at first, but it does seem to only have a problem after I do a restore. Any thoughts on that one??
Click to expand...
Click to collapse
Well amon_ra isn't the answer. I've used clockwork and had ZERO problems, and still use it. But if you think titanium is your issue, go into it, and click problems, and it'll download the busybox and correct itself. And if you think the kernel may be the problem, it could be, so go for it. Just make sure to use an aosp kernel on an aosp rom, and the same for sense; don't mix them.
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
deaconzero said:
Thanks for the advice. Any suggestions on which kernel I could try? On MIUI my kernel is brandon-ThinkPad-T510 #5.
Click to expand...
Click to collapse
Well I would try the a froyo savaged zen kernel. They all play nice from what I hear.
No fix yet even after switching kernels. I found this link when I was looking up more info http://www.shahz.net/android/what-is-dalvik-cache.html and this section interested me.
"This dalvik cache can grow immensely huge as more applications are installed on your phone. It is safe to wipe dalvik-cache. It will be rebuilt again when the phone boots. This also explains why your phone takes ages to start up for the first time. As for my Nexus One, having about 145 applications installed, it takes about 13 minutes to build the cache"
Could this be what's going on? Is the dalvik cache being rebuilt and I'm not actually getting a bootloop? Do I need to let the blue arrow circle around the skating android for 15 minutes?
Still not working. Tried the kernel switch and the above idea of letting the boot screen run for over 20 minutes. Nothing.
Anyone w/ any thoughts?? Thanks.
Are you flashing the new kernel the same time you flash the rom. What you should do is wipe everything, factory/data, cahe, dalvik cache, then flash the rom. Give it a couple of minutes to boot up. After it eventually boots up, back it up, then flash the new kernel, just wipe the cache and dalvik before you do so.
deaconzero said:
So, I did the calculkin format all however I also did something different this time. I started to notice that it would only boot loop after I did a Titanium batch restore. I would normally restore all apps and system data. This time I only restored apps instead of system data and I can reboot just fine... for now.
Would this cause a problem? Restoring system data from a backup inside MIUI and restoring it in CM?
Edit: Now it's stuck at the white screen. Doing a nandroid backup and going to try some other fun stuff. Yay...
Click to expand...
Click to collapse
Restoring system data through Titanium Backup is almost a certain recipe for disaster - especially when switching between different ROMs. Use TB only to restore user apps, and the data associated with only those apps.
The other thing you may want to try is to repartition/format your SD card. Make sure you back it up to your computer first, then use whatever recovery (I know Amon Ra will do it, think CWM will too) to partition and format the SD card. This helped me out when I was getting bootloops...
Good luck!
BigJohn