well i am a little lost... i tried to update the kernel to the newest version of savaged zen. But got stuck on the white screen, so i went back and wiped both catches again, then i got to the boot animation and now thats looping.. okay so i made a backup before starting but now after wiping everything and restoring the backup is boot looping too. Any suggestions?
Try another kernel. I am using the BCblend kernel from november, it's awesome and very stable. Once you get it booted, go into your advanced wifi settings and set your sleep policy to never.
well... my backup boot loops too... wouldnt the backup have the old kernel?
It's possible your phone doesn't like that kernel either, mine didn't. How long were you running it before flashing the new kernel? I would try at least a couple more kernels and if you still can't get it booted then wipe and start over. What version of MIUI are you running?
In my opinion...if you have a good working kernel do not change it. From what ive seen every custom rom is based off a stock rom that comes with a kernel. Usually only custom kernels that match the rom version work well. So it could be the rom and the kernel dont work well together. One thing is nobody seems to list which kernel version is from which rom. So its hard to tell. Also I think your pri version will mess with compatability also. Basically newest rom versions should work with newest kernels. But if your on an older rom...the older kernels will probably work better. And usually kernels come out (it seems) before rom versions. Like new miui kernel supports 4g, but the rom does not support it yet. Also nandroid? backups should have the kernel also. Not sure bout miui backup. But wiping and installing it fresh usually works well. If not you know the deal..wipe everything..then flash the rom..and start over So.....find a good one...keep it=no issues
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
Related
So here's the deal, it feels like I can not get netarchy or kings to install on my phone no matter what. Unless the kernal is built into the ROM there is absolutely no way it is going on my phone. I always boot into the ROM, let it load up, reboot into recovery, wipe cache, and flash the kernal. Every time I do this with either of those kernals my phone will work fine for 5 minutes then start going into random reboots. Is there something special that I am not doing? I'm not a noob, have been a flashaholic since July. I just need to know if its my phone because I am seriously getting tired of it. Kernals I can use with no problem are any cm6 or ziggy kernal. I find this whole thing really bizarre.
firsttimer44 said:
So here's the deal, it feels like I can not get netarchy or kings to install on my phone no matter what. Unless the kernal is built into the ROM there is absolutely no way it is going on my phone. I always boot into the ROM, let it load up, reboot into recovery, wipe cache, and flash the kernal. Every time I do this with either of those kernals my phone will work fine for 5 minutes then start going into random reboots. Is there something special that I am not doing? I'm not a noob, have been a flashaholic since July. I just need to know if its my phone because I am seriously getting tired of it. Kernals I can use with no problem are any cm6 or ziggy kernal. I find this whole thing really bizarre.
Click to expand...
Click to collapse
are you running cm6? Or any AOSP rom? if you are you need to make sure that the kernel you are flashing is an AOSP kernel. The Kings and Netarchy's kernels you are trying to flash might be sense kernels and well that might explain the boot loop.
No I am not trying to run sense kernals on aosp roms or vice versa. I don't have problems with AOSP roms or kernals, basically just netarchy and kings on sense.
caguirr4 said:
are you running cm6? Or any AOSP rom? if you are you need to make sure that the kernel you are flashing is an AOSP kernel. The Kings and Netarchy's kernels you are trying to flash might be sense kernels and well that might explain the boot loop.
Click to expand...
Click to collapse
For instance I am running MYN RLS4 currently and every netarchy or kings kernal will send it into random reboots after proper installation.
that is pretty weird. the only thing that i can suggest is to flash the rom of choice and make sure to wipe dalvik and other caches. then try to flash the other kernel. i would even go as far as re-downloading the rom and kernel of choice to make sure that the one you have isnt corrupt or something. sorry if this doesnt help. the one time that i ran into this problem, fresh rom and kings kernel, once i wiped all caches problem went away.
firsttimer44 said:
So here's the deal, it feels like I can not get netarchy or kings to install on my phone no matter what. Unless the kernal is built into the ROM there is absolutely no way it is going on my phone. I always boot into the ROM, let it load up, reboot into recovery, wipe cache, and flash the kernal. Every time I do this with either of those kernals my phone will work fine for 5 minutes then start going into random reboots. Is there something special that I am not doing? I'm not a noob, have been a flashaholic since July. I just need to know if its my phone because I am seriously getting tired of it. Kernals I can use with no problem are any cm6 or ziggy kernal. I find this whole thing really bizarre.
Click to expand...
Click to collapse
Not sure if this will help but random reboots have been reported due to the underclocking on those kernels, I think there is a little blurb on it in the netarchy thread for the kernels, it is in one of the text boxes with the q and a's. Are you running setcpu? if so set the min to 245760 and see what happens. Just an idea.
Installed MIUI ROM yesterday and just flashed Kings 11 CFS kernel but after it rebooted my touchscreen doesn't work! The phone is working but I can't unlock the phone. Tried rebooting and taking out the battery but it didn't help
What do I do?!
Kings 11 CFS is a Sense kernel. MIUI is an AOSP ROM. You need to flash a kernel that is meant for AOSP ROMs. This is flashing 101. Methinks you need to do a bit more research before you flash anything else, before you do some damage to your phone.
Okay thank you for that...but how do I un-freeze my phone? I tried going into recovery to restore one of my backups but it says there are no files found. Is there anyway I can remove the Kings kernel and go back to the original from the recovery mode? Like I said I can't access ROM manager or anything bc my screen is frozen
NM I figured it out...
Hi
Hoping someone can help. I recently rooted my Desire. I then installed LeeDroid and everything looked great. Then my phone rebooted itself and started rebooting approx every 10 minutes even when not in use.
I had wiped all data and caches before installing and made sure I had the correct radio version installed.
So I decided to wipe again and install the CM ROM instead. Exactly the same thing happened - it booted up into CM fine and then after 10 mins or so decided to start rebooting.
So I then restored back to my stock ROM and the phone was fine - no reboots since.
Has anybody else had this issue? Is it a problem with the phone or the ROMs or something else? I find it hard to believe it's the phone as it's fine when the stock ROM is running.
HELP!!!
Never had reboots like that, not on a single ROM. I followed everything as they suggested (ROM) thread. Check your radio version, if it is compatible with the ROM. Try a different kernel.
Sent from my customized HTC Desire using TTP
Sorry if i'm thick....how do i try a different kernel?
The radio version is compatible.
nobody else?
Serach for kernels here. Just flash them via recovery as the ROM. No wipe needed.
How do I know which one to try? Also, will this affect getting my restore back if it goes wrong or does my backup include the kernel?
Sense kernel for Sense ROMs, AOSP for non Sense ROMs.
Nandroid backs up the kernel as well. Which to try? I suggest the latest Neophyte 1000mv, because:
For people who have lags and/or reboots:
Click to expand...
Click to collapse
1000mV -NeoPhyTe-2.6.32.28-Halcyon_HAVS.1000_CFS_SLQB_VR_v38
This is for SENSE Based ROMs.
Kernels for CM (gingerbread): here and here.
Also you might check for this thread for further information
Anyone having problems flashing the most recent MIUI, or is it just me?
I'm on MYN Warm with stock kernel. I'm using Amon, factory reset and cleared the Dalvik.
It says that MIUI is installed, but when I reboot, it just goes to the default white EVO screen and stays there.
I've downloaded and tried it several times, but same result.
Is it because it is a Sense kernel? And do I flash the AOSP kernel or MIUI ROM first?
Sorry for my scrub questions - just rooted.
Sent from my Evo - WarmTwoPointTwo
Wipe data again then flash
sent from my HTC evolution running a freshly baked gingerbread with the 4gs in it
Do a full wipe, then flash the rom first; always the rom first. And if you flashed the kernel first, fine, but when you install the rom, that kernel will override the kernel you flashed, and then have to flash it again.
Also to make sure.. if your flashing the 1.3.5.. you need to install the 1.3.4 first.. then the 1.3.5.
1.3.4 - http://bit.ly/ePj9IF
1.3.5 - http://bit.ly/eY4Oal
(english)
Also, it has been noted several times.. and I've had much better luck with this rom since doing it this way.. But do a complete wipe.. then wipe cache.. then wipe dalvak.. And for good measure.. do it all at least 1 more time completely. I thought it was bs but I used to get force closes and reboots Constantly whenever i flashed this rom but ever since I wiped everything a couple times it works every time just fine. Hope this helps you out.
So I have to flash 1.3.4 first... okay, gotcha, thanks much. Just wondering, what AOSP kernel do you use/recommend? I know most people say that you need to experiment, but just wondering.
Sent from my Evo - Myn
After wiping your phone to your heart's content, flash 1.3.4, stay in recovery, flash 1.3.5 hotfix, stay in recovery, flash whatever else you need to (kernel, other mods, etc.)
I'm using the Tiamat 2.1.5 kernel, but I think I like the performance of Savage (NOT SavagedZen) 1.6 better/
Aight, thanks guys. Made a Nandroid backup, flashed everythink like you said and Savage 1.6 kernel, and everything is running smooth as butter. Thanks for the help
ok i've been flashing roms for over six months and have been able to fix every issues i've ever had until now..
was running cm nightly 21, tried to update to 23 a couple weeks ago and all i got was a boot loop on the white htc evo screen. ok so i re-download the nightly, clear cache dalvik data and reflash. same boot loop occur. so i waited a few days and new nightlys appeared. so i download and tried to flash. same results with the boot loop.
i reverted back to cm nightly 21. tried to flash savage zen 2.1 kernel. reboot. same white htc evo screen boot loop. flash savage zen 2.0 with cm nightly 21 and it works flawlessly. flashed cm rc2 with savage zen 2.0 and ran flawlessly but boot loops with sz 2.1-1.0.
problem: cm nightly 23 and up (23-30), cm rc3, savage zen 0.2.1 and up, and tiamat's latest kernel (3.32?) all would install properly but when phone boots it is stuck on boot loop at the white htc evo screen.
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
here's my system: latest radio, wimax, prl, pri, hboot.. latest everything update. hardware revision 003. baseband 2.15.00.07.28. S-off. what else..
my thoughts: cm 23 and up, savage 2.1 and up, and tiamat's latest all incorporated hdmi into their builds. i've never used nor have the ability to activate hdmi on my phone. so i'm thinking it's something to do with hdmi? every other rom from cm 21- and rc2- and sense roms seem to work perfectly fine.
i am currently running cm rc2 with savage zen 2.0.. are my days of flashing the lastest and badarse combos of cm and savage zen over? please help if anyone have any ideas and thanks in advance..
losphn said:
ok i've been flashing roms for over six months and have been able to fix every issues i've ever had until now..
was running cm nightly 21, tried to update to 23 a couple weeks ago and all i got was a boot loop on the white htc evo screen. ok so i re-download the nightly, clear cache dalvik data and reflash. same boot loop occur. so i waited a few days and new nightlys appeared. so i download and tried to flash. same results with the boot loop.
i reverted back to cm nightly 21. tried to flash savage zen 2.1 kernel. reboot. same white htc evo screen boot loop. flash savage zen 2.0 with cm nightly 21 and it works flawlessly. flashed cm rc2 with savage zen 2.0 and ran flawlessly but boot loops with sz 2.1-1.0.
problem: cm nightly 23 and up (23-30), cm rc3, savage zen 0.2.1 and up, and tiamat's latest kernel (3.32?) all would install properly but when phone boots it is stuck on boot loop at the white htc evo screen.
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
here's my system: latest radio, wimax, prl, pri, hboot.. latest everything update. hardware revision 003. baseband 2.15.00.07.28. S-off. what else..
my thoughts: cm 23 and up, savage 2.1 and up, and tiamat's latest all incorporated hdmi into their builds. i've never used nor have the ability to activate hdmi on my phone. so i'm thinking it's something to do with hdmi? every other rom from cm 21- and rc2- and sense roms seem to work perfectly fine.
i am currently running cm rc2 with savage zen 2.0.. are my days of flashing the lastest and badarse combos of cm and savage zen over? please help if anyone have any ideas and thanks in advance..
Click to expand...
Click to collapse
Strange indeed my friend. There have been many reports of bootlooping with cm7, and many can't recover. See the thread titled bootloops and no recovery. Its odd that older cm builds and sense work fine for you, and newer ones don't. Its interesting, your observation about the HDMI kernels. I wish I had some suggestions for you, but it appears as though you've exhausted all the things I would've suggested to you already. You've even ran ruu and rerooted. If that didn't work, I'm not sure what will...
Sent from my PC36100 using XDA App
going into recovery is fine. i've tried reflashing with ra mon 1.8, 2.2, and 2.3 recovery but still end up with the white screen boot loop. than i would switch to clockworkmod 2.5 and 3.0 and reflash the roms. they would all install fine with the recoveries saying "install from sd card complete". but when i reboot, it gets stuck on the htc screen! strange indeed..
losphn said:
going into recovery is fine. i've tried reflashing with ra mon 1.8, 2.2, and 2.3 recovery but still end up with the white screen boot loop. than i would switch to clockworkmod 2.5 and 3.0 and reflash the roms. they would all install fine with the recoveries saying "install from sd card complete". but when i reboot, it gets stuck on the htc screen! strange indeed..
Click to expand...
Click to collapse
Sounds like you tried everything before you even posted! At least you can run sense roms and older cm in the meantime, while you try to figure it out. Do other newer gingerbread builds flash and run for you? Or is it just cm7? I wish I had more to suggest, but like I said, it seems like you've covered your bases..
Sent from my PC36100 using XDA App
i've ran miks, myns, and fresh before from the sense side and all worked fine. from the gb side i've ran evolve, kings? (can't remeber right now), and cm starting from cm gingerbread 4 through 6.1.2 to cm7 nightly 21 where i got stuck. i have not try the newest gb roms outside cm. am downloading the latest from evolve now so will give it a shot.
f.y.i. to those afraid of cm roms, my current fig is rc2, sz 2.0 cfs wimax gb, with dark horse v1.0 cm7 rc2 theme and everything (minus hdmi) works flawlessly. i mean gps tracks and follows without drops, wifi works great, absolutely no issues with bluetooth, no random reboots, wimax connects quickly and doesn't drop, 3g hotspot works great, even 4g wireless hotspot works!! i swear it. tested it out the other night and it connected right away and started working. we used it on 4g for about 20 mins without drop.
if everything is working so great, why would i want to update roms? because the cm dev and team are badarse and i love their work (many thanks to you guys). plus titanium backup doesn't work...only app i use that gets fc. biggest irk though is that it just doesn't feel right not being able to flash the lastest builds..
losphn said:
i've ran miks, myns, and fresh before from the sense side and all worked fine. from the gb side i've ran evolve, kings? (can't remeber right now), and cm starting from cm gingerbread 4 through 6.1.2 to cm7 nightly 21 where i got stuck. i have not try the newest gb roms outside cm. am downloading the latest from evolve now so will give it a shot.
f.y.i. to those afraid of cm roms, my current fig is rc2, sz 2.0 cfs wimax gb, with dark horse v1.0 cm7 rc2 theme and everything (minus hdmi) works flawlessly. i mean gps tracks and follows without drops, wifi works great, absolutely no issues with bluetooth, no random reboots, wimax connects quickly and doesn't drop, 3g hotspot works great, even 4g wireless hotspot works!! i swear it. tested it out the other night and it connected right away and started working. we used it on 4g for about 20 mins without drop.
if everything is working so great, why would i want to update roms? because the cm dev and team are badarse and i love their work (many thanks to you guys). plus titanium backup doesn't work...only app i use that gets fc. biggest irk though is that it just doesn't feel right not being able to flash the lastest builds..
Click to expand...
Click to collapse
I will also say that I had good experiences with cm. It always ran smooth for me, and as you stated, everything worked. Same with all the other recent gingerbread roms have been flawless for me too. All the boot loop and no recovery issues, take it for what its worth. To each his own. I like all roms, but ill be on sense for a little while.
Sent from my PC36100 using XDA App
Have you tried flashing the FORMAT_ALL.zip from calkulin?
housry23 said:
Have you tried flashing the FORMAT_ALL.zip from calkulin?
Click to expand...
Click to collapse
my remedies: wipe cache davik data 1x,2x,3x to no success. used caulkins all format zip plus the wiping of cache, etc to no success. i've tried wiping and flashing with ra mon 2.2-2.3 recovery and clockworkmod 2.5-3.0.5 and still no success. i've unrooted my phone, reroot, wipe and flash and no success. i've even tried to not wipe cache/dalvik and just flashing nightlies 23+ and rc3 and still same boot loop at the htc evo screen.. worth a try since i've done everything else i could think of..
From the OP ^^^^ He's wiped with calk's format all, used different recoveries, he's gone as far as unrooting and then re rooting. wiping again. He's tried everything I could think of. Reflashing recoveries(different versions), ran RUU's, re rooting....what's left?
thanks buckley
Sent from my PC36100 using XDA App
Guys, this is all over the forums now. Something in CM is causing these major problems that people are not able to recover from. One theory is that it's causing a bad block in the internal memory, which apparently, the Evo can't recover from.
I think I got lucky when it happened to me last month, where I suddenly white screened for no reason, while running a CM ROM, and I RUU'd my way out of it, but the problem has gotten much worse, obviously.
I loved CM, but at this point, I'm not stupid enough to try and run it anymore.
I hate to sound rash, but I'd lose any CM Rom's you guys are running until the Dev's can figure this one out.