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?
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.
Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
(irc help would be awesome still since I now have some help with main issue- I enter all the correct info into the app but it shows nothin. I've tried several to no avail. I appreciate the help) second I've ran into more pretentious ppl in these forums for Android then others no offense to the good guys but just my exp. It was brash to say that in this post tho. Thank you guys again for the ones willing.
That's because even the biggest idiot can work an iphone.
Jataadroid said:
Ok no help? Not even some direction for irc where I can get some real help? Well just flashed a diff kernel thanks for the help guys. The Droid community has been a very unhelpful one compared to iPhone....
Click to expand...
Click to collapse
Jataadroid said:
Ok since this the third time typing this here is the condensed version. Running myns rls5 ontop of toastmod kernel listed on same page. Initial flash went ok minus the Flickr screen, distortion lines laterally, horrendous battery life, weird boot process...osmonitor I had to install due to interference with the OS. Myns crashed a lot with in first flash. Also some one dumb down how to use an irc app cuz I'm also lost....also what IM service can I get hold of u guys on cuz I hate forums.... too impatient
Click to expand...
Click to collapse
Patience dude. I didn't catch it, but what exact kernel are you using, net has a lot of em, the one in the OP of myn's thread you mean? What recovery(and version of that recovery, some versions of clockwork floating around that have some bugs i think) did you use to flash the rom? what radio version and pri version do you currently have installed? Which ROM were you coming from, and did you do a full wipe(data, cache, davlik cache) before flashing it? I have never experienced anything like you are describing whilst using Myn's, his ROMs have been solid. Give a little more info and surely we can help you get running smoothly again.
thanks for the reply heres the details...myn's rls5, net toast havs more, ra_superson
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Looks like we're running nearly the same setup, minus my ra_supersonic 2.2.1 recovery. I have attempted the stock kernel furnished in the Rom zip but since it didn't offer overclock I switched to net havs more smartass. I do the dalvik and cache wipe each time.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
Not trying to be a smart ass but do you realize that by insulting us will not get you any help? Rhetorical question
From reading what you jus stated the obvious problem is you did not do a FULL WIPE as you should do when flashing between roms.
Also next time please be patient as those like myself who browse through this section to help impatient ppl like your self, do actually have a life outside of xda. Its been a big snow storm in the southeast so most like myself included are outside enjoying the snow!
DO A FULL WIPE THEN REPORT BACK!
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
gotta do a full wipe if you are switching between roms
Sent from my PC36100 using XDA App
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Ok. Well crap.... thanks guys since that is apparently my only option.
OneStepAhead said:
also make sure whatever kernel your using works with the 3.70 based roms, as many dont.
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
The kernel was included in the op and I've seen tags with same setup as mine.
Jataadroid said:
Gonna ignore the soap box chatter...
Obviously know I didn't do full wipe.....just gonna wait for other poster
Click to expand...
Click to collapse
Sorry you feel that way but since i have had the hero, on every thread about a rom says wipe all! This must be a joke for someone as rude as yourself to come on here and disrespect those who are trying to help.
Next time you decide to flash a rom remember to do a full wipe because inside the data partition is files for the particular rom, if you dont wipe, the new files will just over lay but not delete the old one. This will cause conflicting issues within the files as the phone tries to do both at the same time.
Screen tearing and the "jigglies" as I like to call it have always come from kernels - in my experience. And just because someone might have the same set up as you, the way it affects your phone ccan be quite different as you are running different apps, different settings, etc.
First thing I would do if I were you is to freeze any kernel govenor you are using - no setcpu, no secreen off profile, no set on boot, no os monitor govenor, no nothing like that. You don't want want any of that going on when you flash a new rom or kernel.
I know you don't want to do a full data wipe so let's see if we cna get you going without that. I used to HATE doing data wipes, I don't mind so much now because I've learned that trobule shooting can frequently take longer than just doing a data wipe.
I would say #1 make sure you are using AMON RA. Power button-reboot-recovery. Wipe cache at least twice, wipe dalvik at least twice. Now JUST flash the rom (you've already said your radios are updated so you wont have a problem with this). Let the phone boot up and give it time to settle in. You wont have any screan tearing. Now you're running a completely stock Myn's rls5 rom. Check some stuff out, make sure your basic settings are good, make sure your 4g is not scanning, etc.
Make a nandroid of this and keep it.
Now start making changes if you'd like. Flash a different font, flash a different kernel, etc. But leave all the governors OFF until you have a kernel that you KNOW will run ok on your phone. For example - I can run 2 of ziggy's kernels but the others don't work for me. I can run a few of net's kernels, but many don't work for me.
So my basic suggestion is to make sure you get a stable, stock Myn's rls5 on your phone before you mod it. If you can't get that, then yes - you might want to wipe data. Doing a batch backup in Titanium is really easy and it makes restoring very easy as well. It's our own customizing that is time consuming because we are all probably very picky (and proud!) of our beautiful phones.
Thanks for the helpful info from ALL that posted. I understand the risk of the non entire wipe, nandroid is safe of original stock Rom but not of new one. After tinkering with setcpu I've gotten more consistent stability. I know I will reflash with an entire data wipe here soon to see results. Running ra_supersonic 2.2.1 recovery.
I've made list of check point when I test some new Roms and kernels. I have some more question on backing up user info from backed up apps but Im sure ill find it on here.
Now that my system is stable for the time being, some one mind help me setup irc? And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it. Ra_supersonic 2.2.1 recovery i like also.
Jataadroid said:
Sincerely thanks for your reply. Typing this on my evo as my screen tears on and off. Running ra_supersonic(newest ver.) With Myns rls5 on net havs more smartass as listed on page. Updated to current radio and pri as listed on his post. Only dalvik and cache wiped not data. Flashed
Hulu and data governor hacks...CPU is only overlooked to 1190 in smartass and can't go any higher. This was my first root and flash so came from stock 2.2 on 3.30 ver. Have noticed avg using temp is around 103 off charger, cameras broke, my CPU in system panel says I'm running 100% continuously. Did a fast reboot , norm reboot, and still doin it. I had diminished battery life from the get go, I understand battery life per clockspeed relation but have underclocked profile to try to assist, which only cause frustration when coming back from lock screen and its still tryin to switch profile. Lagged the phone nearly locked out several times cuz it couldn't keep up with my fingers.0003 hw....I think that's it. Thank you again
Click to expand...
Click to collapse
You're welcome. I am late at getting back to this post, but yea. Definitely. As everyone else has suggested, you have to do a full wipe when changing ROMS. Only time you could get away with just wiping davlik cache and cache is when upgrading the same rom ( like from rls 3 to rls 4, and rls to rls 5), but even then, it doesn't always work. Full wipe is always recommended. I would also recommend downloading your apps one at a time from the market, and adding your mods one at a time, make sure everything is stable after each flash. Good luck.
QUOTE And also has anyone issues with camera breaking with this Rom or kernel? I should wait to wipe entirely to see if it fixes, but I'd rather not waste my time with this Rom or kernel if the camera won't work. Love everything else about this Rom, need to learn more about the kernel to praise it QUOTE
If your phone is the newer hardware (late 003 or 004), you can only use the stock kernel, or a kernel based off stock for the camera to work. That would be htc #15. I believe Net's 4.3 kernels are based off of that. I am also pretty sure that Net explains that in his kernel thread in the development section.
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
r.storm85 said:
Theres been lots of issues with 3.70 based roms. I always stick to lower versions..usually 3.30 and have no problems.. i also hace seen alot of people having battery problems on 3.70 after updating to 1.90 pri. They usually downgrade to pri 1.77 and there good.....
Evo - Myn 2.2 RLS 3 - Clockwork - HBoot .76
Click to expand...
Click to collapse
This isn't true, the problem is ALWAYS the kernel. I'm running myn rls5 and mikfroyo 4.3 with an SBC #15 v7 kernel (i'll edit post and add the link) and I have had zero issues except I can't download MMS messages on 4g on mikfroyo.
Jataadroid said:
Thanks guys did the full wipe and reflashed, working ok except SD file permissions are screwed up now. I go to test camera and it says insufficient file permissions when I take a pic. I go to check in astro, I see all the file that are supposed to be there but no editing; it still shows rw. Did not have card in when full wipe was completed would that effect it? Any help? Haven't attempted another SD card. I hope this isn't the second SD card to be trashed during my rooting process. Atleast I can still see that there r files on there. Thanks for the help.
Also any help gettin set with irc? Still having a horrible time trying to work with it....it seems so simple.... so 0003hw are stuck with stock roms or ones based off them...I believe nets kernel on that page was. I will test it out and let you know. I just need to know about the SD card problem. Thanks again guys.
Click to expand...
Click to collapse
Okay, this process will 100% work. It's the one I've been using since my lowly mytouch slide oh so many months ago.
*before you do this, make sure you have backups of your nandroid and your rsa keys. I'll edit post and give you links on how to back up your rsa keys*
RSA Key back-up: http://forum.xda-developers.com/showthread.php?t=887900 ...since you're rooted you can go straight to the part where it says "if you're rooted do this.."
1. First you need to fix the sd card. Create a folder on your computer desktop and call it "my sd card". Plug your phone into the computer and select "disk drive". Next you're going to copy EVERYTHING from the sd card and place it in the folder on the desktop (and dude I mean everything! AS IS, DON'T CHANGE ANY NAMES). Then, you're going to unhook your phone, go to settings>sd and phone storage. Then you're going to format your sd card. Yes, do it, but make sure you have EVERYTHING backed up first. After that's done, plug your phone back in, select disk drive and copy everything from your "my sd card" folder on your computer and put it back onto your sd card.
*phew*
Okay now that the sd problem is fixed, here's how you fix the rest. You see, when you upgrade your PRI to 1.90 and your radio, etc etc you gotta update the kernel to a version that's 1.90 supported. I'll edit post and post a link to where you can find one OR you can just use the kernel that's included with myn's rom because it WILL WORK. *edit* the kernel I'm using has been taken down because of the witch hunt against SBC kernels. So for now, just stick with stock. It works just fine.
Anyway.
Steps to getting myn working perfectly.
*before starting, re-download myn rls5 in case the screen flickering was caused by a corrupted download*
1. Download Titanium Back-up from the market. Back up all the apps you want to keep (basically, anything you downloaded from the market as you'll get facebook, sense widgets, etc back). You can do this while you re-download the rom.
2. Make a nandroid back-up in case something goes seriously wrong. A rom that flickers your screen is better than a brick.
3. Once that back-up is done, reboot into recovery. Once there, you're going to WIPE EVERYTHING. Full data, cache and dalvik wipe. Yes, do it. There is no other option.
3. Flash myn's rom. Let it go all the way through. Do NOT flash a new kernel until you've found one that's 3.70 compatible and works with PRI 1.90. Myn rls5 is designed to work with the newest updates (which means a #15 kernel, like the one that came stock).
4. Reboot. If the screen is still flickering, then at this point it's a hardware problem. Flash back to stock, unroot and go get a new one. If it works fine, re-download titanium back-up from the market and restore all your apps. From there it's just putting your widgets back on your home screen.
From here, you can search the forums for a kernel that works with the newest updates. If you read them, they'll tell you what they're compatible with. Remember do NOT use an AOSP kernel with a SENSE rom, that's just spells IDIOCY. Until you find a kernel that works, stick with the one that came with the rom because everyone knows that one works.
I hope this helps. As for the IRC chat, not all the experts are on all the time. If no one is online that can help when you get one, try getting a few hours earlier or a few hours later.
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...
Hello everyone. I have not been too particularly active here mainly because I have had no real reason to post. I give thanks when needed, but don't really post. Well, now I am having an issue that I genuinely cannot figure out. I recently dropped my phone and the digitizer cracked big-time. When I went to replace it, the connector for the ribbon cable broke. So instead of buying a new logic board, I just decided to buy a new Evo. However, I couldn't afford the approx. $600 for the "without a contract" price. So I went to a local Sprint dealer in my town and bought a factory refurbished Evo. Here is where the problems start.
I have been having reboots constant with this phone. I knew that there were some issues with the Evo randomly rebooting, but I have never seen something like this. It happens about every minute or so. Sometimes sooner. Sometimes I luck out and it doesn't reboot for a few hours. I notice that it does not reboot at all while it is in recovery, which is a great thing. I have tried multiple different ROMs and each one does it. I am completely out of ideas. I don't necessarily want to take it back, mainly because returning it to stock would be a pain. However, it is looking like I have to. Does anyone have any idea? It is obvious that it is not a bootloop, because I am able to actually get into the launcher. However, within a minute, it reboots. Can old radios cause it to reboot like this? It did this even with stock unrooted.
If any information is needed, please let me know. I really want to get this working without returning.
Thanks
StompySan
EDIT: It would seem that flashing my Nandroid backup of stock rooted seems to stop the rebooting issues. Could the ROMs I am installing be conflicting with the radios, causing it to reboot?
If I were you, without unrooting, I would flash the RUU for your phone. Then flash the pc36img for Amon Ra.
Before all that, I'd also back up your SD Card, then reformat it, so you are basically starting from scratch. A good idea, before you restore everything to your SD Card, but after you flash Amon Ra, is to partition it for EXT3. ( http://themikmik.com/showthread.php?5669-GUIDE-TUTORIAL-Apps2SD-Guide&highlight=partition+sdcard )
A lot of the ROMS now will take advantage of that. Once that's done, you can restore your SD Card backup to your phone.
Then I'd make a nandroid of that stock/rooted ROM, so you can always go back to it if you need to. When I nandroid, I backup everything except cache.
Figure out which ROM you want, put it on your card along with DT A2SD and the kernel you want to use. Make sure it's a kernel for the type of ROM you want, either AOSP or Sense. Personally, I keep the best rated kernel for each on mine.
Go to Wipe in Recovery and wipe everything, EVERYTHING, except the SD Card, then flash your ROM, and in the same recovery session, flash DT A2SD.
Let it boot up and let it settle in before you do anything. For me, that means once the screen shuts itself off.
Back to recovery, wipe Cache and Dalvik-Cache, then flash your kernel, reboot and let it settle in again.
THEN setup your Google accounts and preferences.
For me, I'd go back to recovery and nandroid that setup, before you've restored your apps, and make another nandroid, so you have one of your ROM's Base.
Then, reboot and see if the problem is fixed. If it is, restore your apps and see how it goes. If it starts rebooting, you know it's in your apps, so you can go back to the nandroid you made and start form there, installing a few apps at a time
Thanks for your reply HipKat.
I followed your tutorial step-by-step. However, after flashing A2SD and rebooting, it bootlooped (not like what I was getting, but an actual no boot logo bootloop). I am assuming that the ROM that I flashed didn't like the A2SD. So I restarted the tutorial, skipping the part where you flash the A2SD script. It seems like it is doing great now! I have no clue what I was doing wrong. I was using CWM. Maybe that was the problem. Could it have not been wiping it properly?
Thanks again for the quick response!
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
2. Before flashing new roms, wipe everything is absolutely required, otherwise strange problems will keep coming out.
What I comprehend is that flash roms on phone is like upgrading OS on your computer, you can't run windows7 with XP's configuration, right?
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
plainjane said:
Hey HipKat, I've noticed that you advise people to wipe everything but the SD card in Amon Ra. You may want to note that wiping battery stats is only good if you have a full battery and plan on calibrating properly. If you wipe battery stats at 70%, your phone won't charge past 70% (thinking that it's full) unless you use an sbc kernel. Just something to keep in mind.
I'm not knocking your directions, you help a lot of people out. It's just something to think about.
Sent from my PC36100 using Tapatalk
Click to expand...
Click to collapse
You're right! I keep overlooking that because I never flash unless I'm fully charged.
My mistake on those posts. Thanks!
I was still getting reboots after doing all of that. I thought it went away, but it didnt.
79x1 said:
1.There are some roms that provides a CPU speed of 1.2G. With those roms and setcpu installed manually by myself, my evo rebooted just like yours. I don't know why, too.
But after I wipe everything(as HipKat said) and flash other rom, my evo 4g works just fine.
Click to expand...
Click to collapse
This has to be it. I changed the speed to 1.15GHz in SetCPU and it has not done it since. Thanks!
EDIT: Well, it was OK, but it has started again. I have no clue why it is doing it again...
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours.
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
79x1 said:
And the CPU speed should be below 998MHz on my device (HW version:004)! Set your cpu frequency lower first, then try some other roms.
Click to expand...
Click to collapse
It doesn't matter what speed I set it to. I had it at 998 before and it still rebooted.
79x1 said:
Maybe you should try some classic roms that don't require app2sd, like kings' kinged kingdom.
Before I partition my sd card, with shooter E3D and synerge, my evo also sometimes reboot, but not so frequently as yours
Click to expand...
Click to collapse
I am going to flash Synergy real quick. I have already tried the following:
EVOlvedROM r3chargeD
Cyanogenmod
Are there any other ROMs I should try?
EDIT: I recorded a video of exactly what it is doing. I am currently encoding it. I will throw a YouTube link up soon.
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/showthread.php?t=1180048
Here is the video of the rebooting problem. Sorry it is so long. It seems like the one time I want it to reboot it took forever for it to. lol.
79x1 said:
Kings' Alliance is the steadiest rom i've ever used, without sense 3.0 though. If you don't mind you could try this:
http://forum.xda-developers.com/show....php?t=1180048
Click to expand...
Click to collapse
I will try this ROM later tonight. I probably won't be able to reply tomorrow, because I have to work from 10AM to 10PM (I hate long days, lol), but will reply as soon as possible.
MIUI, for the win, man!
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
stompysan said:
OK, I can pretty much confirm that it is a hardware problem. I have tried every ROM I can think of. It always seem to restart when it tries to turn on the Mobile access. If it is connected to WiFi, it will not reboot. The moment it is disconnected, it starts. However, I know it is not because of a bad radio flash. I have tried re-flashing the radios and it still doesn't work. I have restored it completely back to stock (while keeping S-Off, naturally) and it still does it. So, I am going to be returning it tomorrow. However, I have one real quick question. I know how to unroot, but I am not sure on how to achieve S-On with the Revolutionary root. Can you just flash the Unrevoked S-On zip with this root, or is there a different method? I wasn't able to find anything out on this.
Thanks again for all of your help. I really can't believe how quick people on here replied.
Click to expand...
Click to collapse
You can flash S-On.zip directly from the recovery, I suggest you try out the method I mentioned in the previous post, before you go doing something drastic.
prometh1us said:
It isn't your hardware, I had a similar issue on my phone, it wouldn't go past the evo screen (for hours), I updated my firmware and it worked.
Clear caches, flash this rom (supersonic_4.24.651.1_odexed-signed2 google it), it will update your firmware, then flash the rom you want on top of it
Click to expand...
Click to collapse
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
stompysan said:
Nonono, it goes past the Evo screen. It goes past the standard boot logo. However, once you are in the lockscreen, and it tries to connect to 3G, it reboots. It is not a standard no boot logo bootloop.
Click to expand...
Click to collapse
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
HipKat said:
If you're gonna trade it in, you don't need to unroot. Chances are no one will ever know, as long as you have a stock ROM on there.
Click to expand...
Click to collapse
Yeah. That's what I was reading. Plus, I rooted with Revolutionary, which doesn't have a method to enable S-On.
Last night I flashed the latest stock ROM. As soon as it booted up and got to the lockscreen, it restarted. I can't see it not being a hardware problem. I am going to return it today. Hopefully they don't notice that it is S-Off. Any suggestions on what to say if they do?
same issue
i have an old evo that is doing the same thing, i flashed the original ruu and it still does it. i just reported it lost.
I was wondering if anyone could help me out please. I've tried searching the forums, but I haven't been able to find my exact issue. Basically, I feel as if my phone seems to have increasing issues with flashing through Clockwork Recovery; here's the details:
I originally rooted my phone using the Odin flash method. I flashed the Juggernaut available at the time, wiping data/factory, cache, dalvik, and battery stats through clockwork first, and letting it chill for 15 minutes with the first boot. I follow the same steps each time I flash another rom ( I've read that I should also wipe /system, but Juggernaut seems to do that itself, so I haven't ). A month and a half ago, I wanted to add a few things, so I wiped, then flashed the latest Juggernaut, rebooted, let it settle,and then flashed the ICS Ultimate Theme, no wipe, then after another settle, flashed the Pdroid zip ( no wipe ) I made with the v1.27 auto-patcher. Everything seemed to work flawlessly for a month or so, then I started having issues that just kept getting worse: phone freezing while installing market apps then unfreezing, camera lagging, random freeze & reboots, etc. I tried fix permissions, and no luck. I wiped and tried reflashing everything the way I had, and the phone kept freezing after the faux kernel loading screen. Installing Juggernaut or another rom by itself, or a nandroid restore, is the only thing that got it past boot. Not even themes flashed over roms that they're made for get past boot. I restored my phone to stock using this method, wiped both SD cards, and re-rooted then flashed Juggernaut again, but this time I used clockwork's wipes and darkside's super wipe before flashing, but I still can't flash anything but the rom itself without a boot loop, even with fix permissions. I had a similar issue on my old mytouch Espresso; consecutive flashes seemed to almost eat away at my phone and make things worse, but that phone also had hardware issues. I'm using a new MicroSD since then. Also, if it means anything, I tried flashing the new clockwork touch from the zip on these forums after these issues started, and it never took, however, flashing through Rom Manager's after I purchased it worked fine.
Sorry about the long post, but I wanted to detail everything I've tried that I could think of before bothering anyone here. Does anyone know what could be the issue? I would really appreciate some help, because this issue is really frustrating, and I have no idea what's causing it.
Could someone help me with this please? I can try and get a log cat if needed. I'm just really hoping to get to the bottom of these issues.
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
techfanatic9 said:
I will be glad to help you out!
One big problem I see is that your not using Darkside Superwipe before flashing new roms.
So I would highly recommend you flash Darkside Superwipe first (clears all cache, partitions, ect very very thorughly) Better option than manually clearing cache and all that in clockwork mod.
Try Darkside Superwipe install the rom and see if you get any problems.
Here's how to use it if you dont know how to:
Click to expand...
Click to collapse
I'd like to point out that he does in fact use tdjs super wipe.
OP: have you tried other ROMs or kernels. In my past experiences, faux kernel did not meet my expectations so I moved along to another one. Give my configuration a go (refer to my signature) and let me know of the problem persists
Sent from my Galaxy Nexus using Tapatalk 2
Thanks for the replies!
techfanatic9 - I originally just wiped through clockwork ( before darkside superwipe was standard ), but now I use that too, and I'm still having those issues. I watched through the entire video just in case, and I'm doing it just like they say to.
iLeopard - I have tried Digital Warfare, but I still have the same issue when flashing things over it ( ICS Theme and/or PDroid ), even if it's supposed to be compatible, though I haven't tried kernels yet. I'll give your sig's setup a try and report back.
Meanwhile, could anything else be the issue? As you can probably tell, I've tried almost every mistake I could think of, and since my last phone had the same issue, a similar hardware issue seems unlikely.
All right, I've been running that ROM and kernel combo for a few days now. I don't seem to have any issues when I just flash the ROM and kernel, but I get stuck at the boot screen if I try to flash something else on top of it. Also, when I try to restore my text message backups through Gosms ( around 9800 texts that I want to keep ), the phone freezes halfway through the restore, and from that point on, the phone will freeze 5-10 minutes after rebooting, unless I reflash. I make sure I don't have the phone running and I leave it alone while restoring, and it doesn't help. I've only had this gosms issue since my flashing issue, and sometimes it restores fine.
Does anyone know what could be causing that?