HTC Evo Hardware 003
Sprint Labeled Extended Battery
Rooted using Unrevoked
Used Myn RLS 4 & 5 flawlessly.
Switch to MIUI about a month ago.
No overclocking was used for MIUI or RLS 5. RLS 4 I purchased it for support only and removed it after a few days.
Had to flash Sav v1.6 to keep the reboots to a minimum of 1.5-3 days. Once it started the first reboot I would have to pull the battery wait a few minutes.
Saved a Nandroid (since has been removed from sdcard) after the reboots started and went back to the Myn RLS 5, bootloops persisted there also.
Back to MIUI after a few over there thought it was kernel issues (which seemed to alleviate some of the bootloop)
Today after my 4th battery pull from bootloop issues I flashed Myn Z. Bootloops persisted.
At one point I pulled the sdcard, formatted it and myn booted up just fine. Stayed up until I rebooted to put the sdcard back in with the ROM, recovery, and PC36IMG's back in the sdcard.
With sdcard out of not I get bootloops now.
Bootloops again.
Installing clarification:
Used Caulkins Format All
Have RA v2.3
Wiped factory reset twice, wiped cache and davlik twice
With MIUI the wifi was set to never.
I am seriously at a loss here. Has anyone else found a solution to this issue? If I unroot, will that bring me back to stock everything so I can try this process over from the beginning? Will it carry over whatever might be an issue with me and just have a stock ROM that bootloops? If you need more information I can attempt to recall it, or pull it from the phone. Keep in mind I cant keep a ROM running for more than 5-15 seconds before bootloops so if it is something from there we might be out of luck.
Thank you kindly in advance.
I would suggest backing the rom up, then go a clean install, wipe everything, that tends to clear bootlooping. Also [I don't use] but on MIUI, you have to set your wifi sleep policy to never, or you will get bootloops.
teh roxxorz said:
I would suggest backing the rom up, then go a clean install, wipe everything, that tends to clear bootlooping. Also [I don't use] but on MIUI, you have to set your wifi sleep policy to never, or you will get bootloops.
Click to expand...
Click to collapse
Installing clarification:
Used Caulkins Format All
Have RA v2.3
Wiped factory reset twice, wiped cache and davlik twice
With MIUI the wifi was set to never.
Alrighty, seems good. By any chance are you over/underclocking?
teh roxxorz said:
Alrighty, seems good. By any chance are you over/underclocking?
Click to expand...
Click to collapse
Used it on RLS 4 for a few days but didnt find it necessary.
Have you tried flashing a newer kernel? All kernels don't play nice for every evo.
teh roxxorz said:
Have you tried flashing a newer kernel? All kernels don't play nice for every evo.
Click to expand...
Click to collapse
Now that would be something I havent tried since coming back from MIUI. I will try Netarchy's real fast and see if that had a good result.
BTW I am refreshing this thread about every minute. I have no phone and trying just about anything someone suggests.
Let me know what happens, and sounds good. Gona do my best to get ya up and running, but I feel the kernel is causing your problems.
teh roxxorz said:
Let me know what happens, and sounds good. Gona do my best to get ya up and running, but I feel the kernel is causing your problems.
Click to expand...
Click to collapse
To let you know installation order:
Caulkins Format All
Factory Reset wipe x2
cache x2
davlik x2
reboot into recovery
flash Warm Z
flash kernel
Will see how this goes after reboot
Sounds good again, but I thought warm Z was a stand alone?
Bootloops before it gets to Warm Z boot animation. 6 times.
used SBC-net-4.2.2-more-havs-v7
Out of curiousity, why are you flashing a previous rom before warm z? And you would have to flash the kernel after the rom because the rom will over write the kernel.
teh roxxorz said:
Out of curiousity, why are you flashing a previous rom before warm z? And you would have to flash the kernel after the rom because the rom will over write the kernel.
Click to expand...
Click to collapse
edited the post roxx.. it was a mistype.
Ah gotcha, try running one of these kernels. You're doing the process right. This time, try to boot into the before flashing the kernel.
teh roxxorz said:
Ah gotcha, try running one of these kernels. You're doing the process right. This time, try to boot into the before flashing the kernel.
Click to expand...
Click to collapse
Caulkins Format All
Factory Reset wipe x2
cache x2
davlik x2
flash Warm Z
rebooted
Ummm... it just rebooted, vibrated 5 times very fast and now has a green blinking light like i have a message.
Not responding to power button at all.
Try a battery pull, let it sit for about 30 seconds, then try to start the phone normally.
teh roxxorz said:
Try a battery pull, let it sit for about 30 seconds, then try to start the phone normally.
Click to expand...
Click to collapse
Nope... no response. Same blinking light.
Wait... got it going.
How long have you been letting it sit? Myn's roms have tended to take a few minutes to boot up...8 minutes for me the one time I had to install to update my PRL, and I thought I was bootlooping.
Bootloop.
Rebooting into recovery and flashing kernel.
teh roxxorz said:
How long have you been letting it sit? Myn's roms have tended to take a few minutes to boot up...8 minutes for me the one time I had to install to update my PRL, and I thought I was bootlooping.
Click to expand...
Click to collapse
Not the case but good question. It doesnt "sit". It actually goes back to the white HTC EVO 4G boot screen. Vibrates each time it does that...
Related
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
DL the new stock kernel to pc mount card to pc put the new kernel somewhere you'll remember then reinstall sdcard and try flashing the kernel that way if you haven't already
Sent from my ADR6300 using XDA App
Hypcrsy said:
Hey everyone,
Hopefully someone can help me with this situation. I haven't been able to find relevant information yet.
I'm currently running a Rooted Incredible with the latest Virtuous ROM. I'm trying to flash back to the stock .17 kernel from HTC, but ANY kernel I flash onto it causes the screen to load up as far as the red eye, stall and then reboot causing a constant loop. The only way I can get beyond this so far is just flashing my recovery image. I've installed from ROM manager and checked to wipe data/cache (backed up before of course!) and have even booted into recovery manually and flashed from the download folder and the actual zip file. Before that I've wiped data and dalvik cache. I can't figure out what I'm missing here. Any suggestions??? I hope I haven't crippled my Droid by doin this.
Click to expand...
Click to collapse
You should not be wiping data when flashing a new kernel.
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Hypcrsy said:
How does that differ from flashing it from recovery if I may ask? I figured I had done everything properly and even after just going to recovery, wiping dalvik, wiping data then flashing I keep getting the issue.
I'm actually at work at the moment and don't have access to my PC to download it. But I'll give it a shot when I get home. Luckily flashing my recovery image works just fine, I'm just stumped why now it wants to cause me grief.
Click to expand...
Click to collapse
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
najaboy said:
You should not be wiping data when flashing a new kernel.
Click to expand...
Click to collapse
Sorry I just saw this post immediately after I replied. I thought wiping data applied for both flashing ROMS and kernels.
najaboy said:
At the most, you should be wiping dalvik. You should not be wiping data when flashing a kernel. Doing so will result in the self-inflicted grief you're experiencing.
Click to expand...
Click to collapse
^This. Only wipe dalvik, not data.
Ok I'll give it a shot while I'm here. I was flashing over to the new edition of Kings and it just became incredibly unstable when interacting with SetCPU, so I was just going to go back to the stock HTC one, that's when I got the first constant bootloop. I'll give it a shot and let you guys know what happens. Thanks for the feedback.
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Hypcrsy said:
Yeah the reload worked this time, I don't know why it was giving me such an issue when I could have sworn it was working ok every other time I've done it before. Any reasons why I'd be getting such a hard time from Kings Kernel 6? I've seen so many rave reviews with it but everytime I have it on my phone it lasts me about ten minutes and then goes back to that same constant boot cycle.
Click to expand...
Click to collapse
thats weird anyone else having that problem? haven't tried 6 yet
Sent from my ADR6300 using XDA App
You only need to wipe dalvik if going to and from one with HAVS, but it doesn't hurt to be safe.
Sent from my ADR6300 using XDA App
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Hypcrsy said:
Thanks for the assistance everyone. I finally got the darn thing stable. But I'm still curious about the kings kernel 6. I was stoked to try it because I was hoping it would be stable. I was having that instability issue with 5. Anyone else know what I'm talking about???
Sent from my rooted Droid Incredible!!
Click to expand...
Click to collapse
Not exactly. I was running 5 on SkyRaider 3.3.2 for a while, then all of a sudden I started having horrible lag while unlocking the phone and for about 7-10 seconds afterwards. Is this what you're referencing? When I switched to BFS6, I didn't have the problem. But the problem did kick in a while after install of 5 (few weeks), I didn't have 6 that long. 6 seemed pretty solid. Give 6 a shot, if you don't like it, just flash something else. Nandroid just to be safe, too.
Sent from my Droid Incredible running Myn's Warm Two Point Two RLS4.
Yeah I always nandroid just in case when I do any serious modification, but I was experiencing the same issue with 6 as I was with 5. Just checking the different limits with SetCPU, anytime I went over 1.1 for overclocking the phone would stay on for about 15-20 seconds and then reboot, get as far as the red eye and then reboot again. That was as far as I ever got with his kernels which is unfortunate.
When testing SetCPU and overclocking, make sure you don't have set on boot enabled.
Sent from my ADR6300 using XDA App
Thanks I'll give it a shot later on.
Is anyone else having this problem? Every time I wake my phone up, it freezes then about 30 seconds later, Sense force closes on me. I thought it was the phone so I took it back. But even my new phone is having the same problem. Could it be an issue with the kernal?
saw somewhere to clear the cache. did that. worked for about an hour. then went back to freezing. i know a lot of you use warm. i need some help. because it is my absolute favorite ROM, but this problem is quite irritating
Try a different kernel.
what would be a recommended kernal for this ROM?
happened to me and i did calkulins format all
The recommended kernels are right on Myn's thread. I use the Net SBC kernel and its awesome! Fast, consistent and great battery!
If just changing the kernel doesn't do it, as one of the other guys said, flash calks format all, then reflash the rom and start fresh. That should handle it for you.
sent from my supersonic
damn. I was hoping you wouldnt say I had to reflash. but ill give it a shot. thanks guys.
kennethbring said:
damn. I was hoping you wouldnt say I had to reflash. but ill give it a shot. thanks guys.
Click to expand...
Click to collapse
Did changing the kernel not work? If not, you could try just wiping cache and davlik, then reflash rls5 without wiping data or flashing calks format all. See if that fixes it. If Not, then do the full wipe, flash calks formatall.zip, then reflash rom. Good luck.
sent from my supersonic
I haven't tried just switching kernels. I'll do that now. And if that doesn't work, time to pull out the ole dusty titanium backup.
okay. so i flashed a new kernal. the net sbc one. and cleared the cache and dalvik. and when i rebooted it, the screen was a greenish tint for about 5 minutes. its gone away since then. but is this normal?
kennethbring said:
okay. so i flashed a new kernal. the net sbc one. and cleared the cache and dalvik. and when i rebooted it, the screen was a greenish tint for about 5 minutes. its gone away since then. but is this normal?
Click to expand...
Click to collapse
I have never noticed anything of the such. Did it happen just that once, or does it persist after a reboot? If it's okay, I would say it was a fluke thing. I didn't have good luck with the SBC kernels, and the controversey on them was enough for me to stop using it. I like the kernel in my sig.
kennethbring said:
okay. so i flashed a new kernal. the net sbc one. and cleared the cache and dalvik. and when i rebooted it, the screen was a greenish tint for about 5 minutes. its gone away since then. but is this normal?
Click to expand...
Click to collapse
Flash myn and don't change the kernel. the default kernel works great. make sure you have updated your radio/pri/wimax before u flash the rom.
Also, are you undervolting? I had a problem where i undervoltd too much and it would freeze for a bit after i unlocked. as soon as i got rid of undervolt, everything was fine.
the stock rom (minus any apps you dont want) is very solid....i use the **** out of my phone and myn's RLS5 is one of the most fast and stable sense roms i've used.
I don't thinck so.
Sent from my evil evo!!
tried a couple different kernals (including the stock that is included with warm) and im still having the freezing problem.
as far as undervolting goes, i dont mess with the cpu. i dont see a need to. so i know thats not the problem.
so is my only choice now to format all and reflash the ROM?
and also, since i flashed a new kernal, my adobe flash hasnt been working. every time i go to a website that uses flash, the internet app just force closes. is this an issue with the kernal? or something else?
Undervolting is built into many custom kernels.
I personally use netarchy-toastmod cfs havs more aggressive no sbc on Myns RLS 5. I don't seem to have the freeze on unlock but my phone had the Adobe flash problem until I updated it through the market.
At first I thought it was the kernel, but I've used the stock HTC, ziggys, and netarchy and still it would close the browser with no indication, when there was flash content. Maybe its a memory issue? It still closes every once in a while, but not as much as it did before the update.
I also downloaded adfree from the market as Myns RLS 5 has an outdated hosts file slowing down the internet in general until updated. Just download, hit revert, then update.
I occasionally get a freeze in sense tho, maybe once or twice a day, lasts about 3 seconds. Doesn't bother me, this kernels gets me 14+ hours as a medium user and is quite snappy otherwise.
Im using the same kernal as you. And I uses Calkulins format all. And I'm still getting the freeze at unlock. It only seems to happen when my phone sleeps for a long period of time (45 min+). But it is really annoying. I dont know if this could affect it at all, but I'm using the old version of Clockwork to flash everything. I'm not familiar with edify and all that. Its really irritating because Myns rom is the only one I like enough to consider rooting my phone worth it. Is there anything else I can try?
ive been looking over the forums and havent found anything pertaining to this. does anyone know anything else to try?
kennethbring said:
Im using the same kernal as you. And I uses Calkulins format all. And I'm still getting the freeze at unlock. It only seems to happen when my phone sleeps for a long period of time (45 min+). But it is really annoying. I dont know if this could affect it at all, but I'm using the old version of Clockwork to flash everything. I'm not familiar with edify and all that. Its really irritating because Myns rom is the only one I like enough to consider rooting my phone worth it. Is there anything else I can try?
Click to expand...
Click to collapse
Stop using Clockwork. That's the first suggestion. Then use the format all and flash the rom again. don't change anything on the rom. use that for a day or 2. if you still have problems, go back to the stock sprint rom. if you STILL have an issue, unroot and take your device back.
Ive already taken it back once. So, I know its not the phone. But I tried switching ROM's and they all freeze. So its not just a problem with Warm. I clear the cache, dalvik, full wipe and format all before every flash. But, as I said, every ROM I flash still freezes. I tried Fresh, MIUI, Warm, Sprint Lovers, and Elite. I switched to Amon Ra as well to see if maybe the problem was the recovery I was using, but still, the same problem. I dont download many apps. So, I'm pretty sure its not something I'm downloading from the market or anything. I've tried everything. So, at this point, I'm considering unrooting and going back to stock. Any last chance efforts I should try?
Need the expertise of the XDA mindset here to help a guy out, please.
I was running Myn's RL5, and loving it. Well I wanted to delete it and install it fresh again, and with some different Kernel. So I did the standard full wipe, of data, dalvik, and cache, and ran that three different times, and then installed the Calkulin's format_all. So I did all that, and then go to install Myn's RLS-5, first before anything else, I then reboot, but it just hangs on the htc EVO 4g start screen, forever
I pull the battery, and go into recovery screen, wipe data again, clear everything, then go to Nan backup, and it reinstall's my previous saved backup from last week, but then again it just hangs at the load screen where it shows the htc EVO 4G logo forever until I pull the battery again.
ive learned to reflash the kernel specified to whatever rom that nandroid backup uses. when i cant boot... get it?
How long do you let it sit at the white screen?i have had mine hang for several minutes before it gets passed it.
Zorachus said:
Need the expertise of the XDA mindset here to help a guy out, please.
I was running Myn's RL5, and loving it. Well I wanted to delete it and install it fresh again, and with some different Kernel. So I did the standard full wipe, of data, dalvik, and cache, and ran that three different times, and then installed the Calkulin's format_all. So I did all that, and then go to install Myn's RLS-5, first before anything else, I then reboot, but it just hangs on the htc EVO 4g start screen, forever
I pull the battery, and go into recovery screen, wipe data again, clear everything, then go to Nan backup, and it reinstall's my previous saved backup from last week, but then again it just hangs at the load screen where it shows the htc EVO 4G logo forever until I pull the battery again.
Click to expand...
Click to collapse
How long has it been sitting there? Mine has been up to 5 minutes on 1 occasion.
elegantai said:
How long do you let it sit at the white screen?i have had mine hang for several minutes before it gets passed it.
Click to expand...
Click to collapse
I let it sit there for 10min, and nothing, it is still sitting on the startup screen now after 15min
Zorachus said:
I let it sit there for 10min, and nothing, it is still sitting on the startup screen now after 15min
Click to expand...
Click to collapse
Have you tried installing an older save then the one you are restoring?
teh roxxorz said:
Have you tried installing an older save then the one you are restoring?
Click to expand...
Click to collapse
No I just have the one saved.
I am following some sound advice from another member; will see how this goes ?
Try to flash like I edited above:
-Clear Memory
-_Format_All.zip
-Flash Rom
-Flash Radio
-Flash Kernel
Zorachus said:
No I just have the one saved.
I am following some sound advice from another member; will see how this goes ?
Try to flash like I edited above:
-Clear Memory
-_Format_All.zip
-Flash Rom
-Flash Radio
-Flash Kernel
Click to expand...
Click to collapse
That sounds logical. Just make sure you flash a sense kernel.
teh roxxorz said:
That sounds logical. Just make sure you flash a sense kernel.
Click to expand...
Click to collapse
Yes good call;
Ok...crosses finger lets see how this goes ? At the system updating screen, the little folder with arrow pointing down to green Droid. Did not get that far the last time.
I will give it 15min...and report back.
also skip the radio update if u can, if it doesnt work
do cal format all, wiope dalvik cache, then flash ROM, then kernel, let phone boot up, after that put phone into recovery and flash radio
Zorachus said:
Yes good call;
Ok...crosses finger lets see how this goes ? At the system updating screen, the little folder with arrow pointing down to green Droid. Did not get that far the last time.
I will give it 15min...and report back.
Click to expand...
Click to collapse
Well sounds like it booted up alright, just enter your info and good to go.
It worked Followed the instructions and back on
Followed the advice to the "t' and back on like a charm. Went pretty fast and smooth after doing all those steps one after the other, then rebooted, and bam, back in action.
Only thing I noticed is that my PRI version is 1.90_003 isn't that bad ? Should I flash the "EVO_PRI_1.77_003" ?
Installed, went to reboot system, all it does it go to the htc incredible screen, reboot, htc incredible screen, then goes to recovery. wtf over?
so i formated the cache, dalvik, and fixed permissions and still no luck.
what do i do next?
I second this...
In fact, today was the very first day it wouldn't do that when I flashed a Sense 3.0 ROM... now it's back to not flashing them anymore.
They weren't kidding in the instructions where it says to wipe cache/data three times. I started from scratch, wiped everything a bunch of times, reinstalled and it worked. My phone is very picky, because when I flash any ROM, it will never load the first time unless I go back and re-wipe everything. It's a pain, but it's a nice rom. Only thing i found that doesn't work is the flash on my camera, and the flashlight.??
RMinor205 said:
They weren't kidding in the instructions where it says to wipe cache/data three times. I started from scratch, wiped everything a bunch of times, reinstalled and it worked. My phone is very picky, because when I flash any ROM, it will never load the first time unless I go back and re-wipe everything. It's a pain, but it's a nice rom. Only thing i found that doesn't work is the flash on my camera, and the flashlight.??
Click to expand...
Click to collapse
What version of Clockworkmod are you using?
I had made sure I had done it several times.... and it's very arbitrary to be honest it seems whether a ROM will flash or not. RLS7 seems to flash just fine... but I can't get .5 on there again... I'll see what I can do..
Yeah... so apparently my phone is an exception of sorts... it seems like I've been having trouble flashing any sort of Gingersense ROM... but I am able to get RLS7 onto my phone. It's booting now. But I can't for the life of me seem to be able to get .5 on there. What's the difference anyways? Anyone.\lol
**By the way, I am 100% sure I wiped everything 3 times... and it would still get stuck on splash screen.
BrettApple said:
What version of Clockworkmod are you using?
Click to expand...
Click to collapse
3.0.0.8
i'm going to update to RLS 0.5... maybe. Just to see if that fixes the bug.
It says "flash disabled due to cold weather, low battery, or use of an app that uses a lot of battery power".
I live in Florida, have a full battery, and haven't re installed any apps.
Installing 0.5 - hopefully it worked.
Wiping several times DOES NOTHING. No matter if you say it did or not. The way to fix that, as I have had it happen is simply flash the rom again without wiping. So, say you wipe and flash, reboot, it goes back to recovery, just install zip again.
I also have the "flash disabled due to cold weather, low battery, or use of an app that uses a lot of battery power". Full battery, no high power apps running.
Been using SOS for a while now on my Evo 4G - loving it, except that once a day (haven't checked to see if it's at the same time each day) my Evo goes into a boot loop. Thought it might be an app of some setting I had on my Evo, until I installed this ROM on my wife's Evo 4G, and her's is doing it too (with minimal apps installed).
Can anyone offer either some debugging tool I can install to see what might be causing it, or otherwise offer some advise?
Many thanks,
Eric "GuitarEC"
P.S. - Did see something in the forums about Evos not playing nice with CPU clock settings lower than 128MHz, so I already uninstalled any CPU throttling. Still have the issue. Also, I wiped my wife's phone 3 times (cache included) 3 times in Recovery before flashing the ROM...
You for one can't clock any lower than 128 Mhz. What recovery are you using, because it may not be wiping correctly.
teh roxxorz said:
You for one can't clock any lower than 128 Mhz. What recovery are you using, because it may not be wiping correctly.
Click to expand...
Click to collapse
Using clockWorkMod v.5.0.2.2
guitarec said:
Using clockWorkMod v.5.0.2.2
Click to expand...
Click to collapse
Try switching to amon ra or twrp; clockwork doesn't wipe correctly for some users. You'll be good to go after that.
Flashed RA Recovery v 2.3. Wiped my phone (several times) and installed fresh version of SOS (v1.9.0.7). Recovered apps and data from Titanium Backup.
...now e wait and see...
Thank you for your help.
Eric "GuitarEC"
guitarec said:
Flashed RA Recovery v 2.3. Wiped my phone (several times) and installed fresh version of SOS (v1.9.0.7). Recovered apps and data from Titanium Backup.
...now e wait and see...
Thank you for your help.
Eric "GuitarEC"
Click to expand...
Click to collapse
Should be all good to go, and no prob man.
Okay, after all that, my phone just went into another boot loop. Was listening to Google Music at the time, this isn't the only app I'm running when it has done this in the past, but i figure I'd rather give more info than needed to help me diagnose this.
Also, can anyone recommend either a debugging tool, or a system logger/dump per that could shed some light on what's going on?
Thanks,
Eric "GuitarEC"
What are you clocked at?
TrevE Supporter!
infamousteeboy said:
What are you clocked at?
TrevE Supporter!
Click to expand...
Click to collapse
Using Rom Toolbox: Max - 998Mhz. Min - 245Mhz. Governor - Smart ass. Apply on boot checked.
guitarec said:
Using Rom Toolbox: Max - 998Mhz. Min - 245Mhz. Governor - Smart ass. Apply on boot checked.
Click to expand...
Click to collapse
Bootloop meaning that your phone turns off and goes back to the white "HTC EVO 4G" screen and starting over right? Jus to make sure you know what your talkin about cuz I remember I thought a bootloop was a Force Close when I first started flashing lol no joke being serious lol
TrevE Supporter!
infamousteeboy said:
Bootloop meaning that your phone turns off and goes back to the white "HTC EVO 4G" screen and starting over right? Jus to make sure you know what your talkin about cuz I remember I thought a bootloop was a Force Close when I first started flashing lol no joke being serious lol
TrevE Supporter!
Click to expand...
Click to collapse
What I observe: Phone freezes for a few seconds then goes straight to boot animation (Skips White "HTC Evo 4G"). After a short period (usually less than 45 seconds) boot animation freezes and restarts boot animation. Only way to snap some sense (no pun intended) back into it is to pull the battery. Then it boots up normally.
guitarec said:
What I observe: Phone freezes for a few seconds then goes straight to boot animation (Skips White "HTC Evo 4G"). After a short period (usually less than 45 seconds) boot animation freezes and restarts boot animation. Only way to snap some sense (no pun intended) back into it is to pull the battery. Then it boots up normally.
Click to expand...
Click to collapse
Hmmm....you got AmonRa so that's good...you may wanna
go into recovery
wipe cache
wipe dalvik cache
fix permissions (uid mismatch)
reboot
let it chill for a minute
ALONE
And see how that does sometimes ROMs will need to take a couple minutes to do its thing when 1st installed see if it helps
TrevE Supporter!
K. Brb... I'll give this a try.
Okay. Followed steps as prescribed - let my phone sit for about 30 minutes afterwards. We'll see if this helps or not after about a day or two. I'm hoping so, but another minor problem I've noticed is still present (keyboard preferences are cleared after reboot).
Now the waiting begins...
Lemme know if anything (no offense) I'll walk you through my installation process no offense intended its jus sometimes things happen that are user error and it sucks cuz I've actually done some pretty bad moves here there
TrevE Supporter!
None taken at all. I have some prior Linux experience, but I've only been doing the root thing for about a month.
In fact, if you could spell out your install process, I'll compare it with mine and see if there was anything i flubbed.
Sure.
Download Rom
Download Gapps (If Needed)
Download Kernel (In Case I dislike Stock Later)
Boot To Recovery
Wipe Cache
Wipe Dalvik
Fix uid mismatch
Create Backup
Go back
Flash zip from SD
Flash Kings Format All (x2)
Go Back
Wipe
WIPE EVERYTHING MYSELF (x2)
Except SD Card
Except Battery Stats
Except Rotate
Go Back
Flash zip from SD
Flash ROM
Flash Gapps (If Needed)
Go Back
Wipe
Wipe Cache
Wipe Dalvik
Fix uid mismatch
Reboot
Let it do its thing for about 5 or 10 mins
Unlock
Finish setup process
TrevE Supporter!
Looks like that did the trick. Wiped the Cache and Dalvik a couple of times each, fixed permissions and let the phone cook for about 15 after reboot. No boot loops over the weekend, and I applied the fix to my wife's Evo as well.
Thank you so much for the quick responses, and the patience for this relative noob. :^)
Eric "GuutarEC"
Glad you got it up and running brutha!
TrevE Supporter!