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.....
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
My phone won't boot more than 3 seconds into the animation. I use CM6.0 stable. I had flashed the PS3Freedom zip in order to Jailbreak my PS3, restored to CM6 with no problem, and then when I did it again I couldn't boot into my RESTORED CM6 ROM. I restored few old nandroids that I didn't like till I got to my rooted Sense 2.2 one, then I deleted a few nandroids from when I was flashing nightlies to make room to download BakedSnacks 1.7 through ROM Manager. Everything was working fine, but then I tried to get CM6 running again and I am still not able to boot into it. What's going on here?
To the best of my knowledge I've been wiping the Data/Cache as often as necessary, even the Dalvik Cache a few separate times trying to get this to work.
blakerboy777 said:
My phone won't boot more than 3 seconds into the animation. I use CM6.0 stable. I had flashed the PS3Freedom zip in order to Jailbreak my PS3, restored to CM6 with no problem, and then when I did it again I couldn't boot into my RESTORED CM6 ROM. I restored few old nandroids that I didn't like till I got to my rooted Sense 2.2 one, then I deleted a few nandroids from when I was flashing nightlies to make room to download BakedSnacks 1.7 through ROM Manager. Everything was working fine, but then I tried to get CM6 running again and I am still not able to boot into it. What's going on here?
To the best of my knowledge I've been wiping the Data/Cache as often as necessary, even the Dalvik Cache a few separate times trying to get this to work.
Click to expand...
Click to collapse
what recovery are you using?
in clock work, try wiping to factory, wipe cache partition, wipe datavik then flash from zip to whatever rom.
in RA do the same but make sure your rom is on the root of your sd.
i had the same issue and did that and it worked fine.
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!
I recently decided to update the look on my Evo and went with the MikFroyo v4.5 Rom. I was running Netarchy's Burnt Rom, and had the toastmod kernel. After updating the radios, as they suggested, I proceeded with flashing with the MikFroyo rom. The MikFroyo Rom comes with stock HTC #15 Kernel, which I just left alone until my wifi stopped working.
I read on a few threads that some people were flashing a different kernel and were able to fix wifi, so I tried a couple of different ones. I've listed the kernels I used below. Additionally, I updated profile in system updates, and it still didn't fix anything.
[KERNEL]
Stock HTC #15 Kernel (came with MikFroyo v4.5)
4.3.1 netarchy-toastmod-cfs-nohavs-nosbc-universal
4.3.4-cfs-havs-less-nosbc (Less Aggressive HAVS) - This kernel is currently on my phone.
I'm just grasping at straws at this point, and I have no idea what else to do. I love the Rom, but I need the wifi to work.
Does anyone know a kernel that is supposed to resolve the wifi issue?
Are there perhaps some file location changes that were made when the new Rom was installed?
You stated that you kept the HTC 15 until wifi stopped working. This infers that wifi was working with MikFroyo and then something happened. What mods did you make to your phone just before wifi stopped working?
Hi, thanks for the reply. I meant to say I didn't start trying new kernels until I noticed the wifi wasnt working. The MikFroyo rom suggested updating the radios before flashing it, so I did.
The wifi problem surfaced after updating the radios to the current ones. I reverted the ROM back to Netarchy Burnt Droid 1.4.2 to see if it was the ROM that was causing the issue, but the wifi still can't scan for networks. I also always wipe the dalvik and cache before flashing.
Which radio did you flash.
I would suggest doing a full wipe, and then re-flashing the rom.
Khilbron said:
Which radio did you flash.
Click to expand...
Click to collapse
I did the combo and the boot update found here. I don't know which piece effects the wifi though.
teh roxxorz said:
I would suggest doing a full wipe, and then re-flashing the rom.
Click to expand...
Click to collapse
I also always wipe the dalvik and cache before flashing anything. Are you saying I need to wipe something else?
aerobic1 said:
I also always wipe the dalvik and cache before flashing anything. Are you saying I need to wipe something else?
Click to expand...
Click to collapse
I'm saying backup your rom and apps. Then do a full wipe, factory/data, cache, and your dalvik, then re-flash your rom. That should clear up your issues.
teh roxxorz said:
I'm saying backup your rom and apps. Then do a full wipe, factory/data, cache, and your dalvik, then re-flash your rom. That should clear up your issues.
Click to expand...
Click to collapse
Wooohooooo!!!! I wiped everything, and it's working PERRRRRRRFECTLY!!
Thanks a bunch teh roxxorz
Anytime man.
hello this is my first post,
i'm new here
i just flashed the Uber gingersense rcmix b1 by Joelz, then when i reboot system it freeze on htc incredible bootscreen,
i did a full wipe (data,cahce, cache partition, dalvik cache) before flashing..
how to solve this? did i miss something on installation? should i do battery pull now?
i use cmw 3 hboot .92
before i used this i use stock sense 2.0 ROM by incubus (froyo)
ok, solved
i did a battery pull, do a complete wipe, flash cmw 2.5, then re-flash the ROM
kazheeizm said:
ok, solved
i did a battery pull, do a complete wipe, flash cmw 2.5, then re-flash the ROM
Click to expand...
Click to collapse
sorry i never got back to you i feel asleep
i have the same problem and i keep doing batter pulls i even did a full wipe before flashing and it still happens
andimanium said:
i have the same problem and i keep doing batter pulls i even did a full wipe before flashing and it still happens
Click to expand...
Click to collapse
if you are using cwm 3, you should flash cmw 2.5 before flashing ROM (after do a full wipe of course)
i think when flashing sense 2.0/2.1 based ROM you should use cmw 2.5 (my experience said that)
but, CMIIW