Okay guys this one has been screwing with me for a while now and is getting progressively worse.
I have a launch day EVO 0002 hardware and I believe an Epson panel but don't remember that one 100%
My evo was running great up until the 31st/1st. I put on a CM6 rom and a snap kernel. Phone was running fine then started lagging horrible so I did a reboot.. Phone went into bootloop. So I went into recovery wiped data/ cache/dalvik 2 times (clockwork recovery).
Restored the phone to Freak E Froyo which I had been running for 2 weeks. Next day I tried the senseless Freak E Froyo and wasn't as much of a fan of it so I installed AVA v6(then flashed king kernel 8 over the top) then the touchscreen issues arose. My screen would think it is being touched when it is not pages would flip, apps would open and no buttons would work. When i hit the home button it opens whatever is on the left of the screen and when I push the back button it opens whatever is in the middle of the screen.
So I nandroid'ed to My Freak E froyo after wiping all again. Still did it. Flashed CM6 6.0.0 after wiping all. Still same problem but worse and even more noticeable on CM6 .
I then switched to AMON RA recovery, tried the same thing: wiping all 4 times, reinstalled CM6, same problem.
Tried reinstalling stock 2.2 odexed and rooted was fine until about 5 hours after running then almost every time I could only use the phone for about 6 seconds and the touchscreen would become unresponsive...
I am thinking it is a piece of a kernal not flashing correctly so It is causing problems maybe?
If not that do you think it could be a CPU problem itself? Maybe going out and unable to hold up anymore and causing freezing?
Any suggestions will be tried. If not work then...I will most likely try a 2.2 RUU and format my sd card and see if that does anything.. and lose root/nand unlock
Yes my v002 EVO had the same issue and all 002 are novatek but I dont think its a screen problem.
I gave up trying to figure it out but I know with mine if I ran ANY rom that came out before the 1.47 OTA then it would NEVER have this issue..
If I ran ANY rom after the 1.47 OTA then it would always do it..Sometimes it might take hours for it to happen but it will..I'll bet yours is probably the same way.
The offical HTC 2.2..yup same thing
The offical HTC 1.47 OTA..yup same thing and this is when it started.
I wiped/flashed/wiped whatever you can think of and the problem NEVER went away on any newer ROM's but as soonas I load a older ROM it never happened.
Look for the EVOlution v9 ROM..Its the ROM I ran until I exchanged the phone..I'll bet if you load that ROM you won't see a single touch screen issue.
Just my 2 cents but save yourself the headache and exchange that damn phone..
That is what I will most likely do tomorrow. Will take it back to stock to do it tonight but it is just weird because I never once had a problem until the bootloop. My buddy who has an evo we got em at the same time store ..etc.. His alot of times will do this and he is not rooted or anything...Just hoping they dont give me any problems tomorrow at sprint...
Related
I just got a new Evo yesterday from having my old one replaced due to screen seperation.
So my Evo Android 2.2 and all the newest OTA on it..
Before my Evo was rooted running CM6 and life was great. Now I can't get the thing unrooted with Unrevoked 2.3.1 and can't find a new method with the Evo I have now with all the newest OTA..
Any suggestions on what to do so I can get this awful HTC Sense off my phone A.S.A.P..
Thanks so much to every one in advance.
Your sure that it didn't work because its not like the old days were it flashed and engineered version. When the phone reboots it will have the same ROM as it did when you started the process. Only the stock ROM will be rooted. I'm sure you checked to see if it has ClockworkMod recovery on it now. I just rooted a EVO I received two days ago it worked fine.
on unrevoked it says that it failed and say it happens some times and to try again.
I tried about 5 times this morning and it failed every time.
power down pull the battery spin in a circle three times while chanting unrevoked will revoke the carriers attempt to prevent me from rooting. Then try again!
ok so really the battery part is the only part that you HAVE to do but the rest is still kinda fun. My friend had this problem and whether it was coincidence or not pulling the battery and then putting it back seemed to do the trick first time through it worked after.
Thanks.
I will give it a try when i get home from work.. Now I just have to wait 5 more hours till I get off work, durrrrrrrrrrrrrrrrrrr.
A battery pull did the trick..
Thanks for the help..
Basically when I install the warm 2.2 rom it will hang on the htc evo screen. I had flashed this rom earlier this morning and it flashed fine. Ever since I've flashed CR 6.1.1 this afternoon i've been having problems. Even my baked snack 1.9 rom is very slow but comes up after either sitting at the Green HTC text after it has booted. I had to power down the phone a few times to even get that to come up. Is there something I'm doing wrong here all the sudden? I am clearing davlik and partition cache, even tried to wide data/restore to no avail. I'm at a loss here. Anyone have any input here? As I type this, I just did a complete wipe and tried to install Warm 2.2 and it is just sittin at the white screen that says HTC EVO 4G. Powered down a few times and removed battery for a minute to no avail, still just sits at that white screen.
I am able to restore from nandroid. I am also able to isntall a few roms.
Thanks
Dave
Uh, what kernel/radios are you using? I had similar problems when I flashed the all in one radio combo in calk's thread.
That is exactly what I did too, flashed the radios. How did you resolve that issue? I dind't even think that would cause these types of problems.
I just put on Fresh 3.5 and it installed fine. I am using kernel 2.6.32.17-gee557fd (under it says [email protected] #15 (Which kernel would that be?) PRI is 1.90_003
Well I downgraded the radio to2.15.00.09.01 and I got past the white screen and into warm. THanks much!! I had no idea that a radio would just cause it to hang like that. So the only way to revert back to an old radio file is to install it? A nanrestore doesn't do that it appears??
Thanks very much
Dave
Im not a noob but this is a problem that i cant solve. I had to jus recently re root my phone. Flashed my 1st rom and phone would show same time for up and awake time sometimes awake time would be a fraction of a second more than up. ****in weird. Pulled battery... problem still persisted. flashed a few other roms also restored a nandroid(jus a week old) to see if it would stop. no go. Maybe I need to re root again?
stock htc kernel 15
rom- currently mikfroyo 4.30. tried calk's evio 1.7.7. and my nandroid back up was calk's evio 1.7.5
vlug said:
Im not a noob but this is a problem that i cant solve. I had to jus recently re root my phone. Flashed my 1st rom and phone would show same time for up and awake time sometimes awake time would be a fraction of a second more than up. ****in weird. Pulled battery... problem still persisted. flashed a few other roms also restored a nandroid(jus a week old) to see if it would stop. no go. Maybe I need to re root again?
stock htc kernel 15
rom- currently mikfroyo 4.30. tried calk's evio 1.7.7. and my nandroid back up was calk's evio 1.7.5
Click to expand...
Click to collapse
Do you have the latest raidios updated? Alot of people have been having issues with the NV and PRI being 1.90. Try downgrading that and see if it helps
my pri is only 1.34 so maybe i should try the latest radios
vlug said:
Im not a noob but this is a problem that i cant solve. I had to jus recently re root my phone. Flashed my 1st rom and phone would show same time for up and awake time sometimes awake time would be a fraction of a second more than up. ****in weird. Pulled battery... problem still persisted. flashed a few other roms also restored a nandroid(jus a week old) to see if it would stop. no go. Maybe I need to re root again?
stock htc kernel 15
rom- currently mikfroyo 4.30. tried calk's evio 1.7.7. and my nandroid back up was calk's evio 1.7.5
Click to expand...
Click to collapse
Also, do you use 4g? There is a known bug, that when you turn 4g on, and then toggle it off, that the radio remains scanning, and holds a wake lock. So you have to turn 4g off and reboot. Just throwing some things out there.
I am having this same problem, I thought it might have been some thing in Juice Defender... but my screen setting is set right and everything... I have to manually shut the screen off by pressing the top button... if I dont - it just dims to very low brightness and stays on...
I am having the same problem as well. Never had but had to switch evo's due to my old one dying. My new one always stays awake. I have tried four different rom's, same thing. I killed my old one updating radios so I am hesitant to do that again. Any other ideas? My am out and this phone is almost useless in this state. The battery life is down right atrocious. I hate to get rid of it but if this can't be corrected I won't have a choice.
Ladies and gents.
First, I realize Saturday is probably not the best day to have an issue, so I appreciate any input I can get.
First, I'm running a rooted (toast method) evo, currently on CM7.
For the longest time, I didn't change roms, and then updated to CM7 a couple of months ago (iirc).
Shortly thereafter, I began experiencing random reboots, my phone getting extremely hot, and sitting through bootloops upon startup.
After upgrading my radio, nothing was solved. I downloaded another CM7 clean and flashed it. Same issues.
I download a Fresh Rom, and was unable to even flash it after wiping continuously.
I nanroided back to my CM7, of course with the same instability issues.
Then I nandroided back to the ROM (damage control, iirc) I had (that was perfectly stable at the time for nearly 1 year) before CM7, and I barely got it booted all the way through before it reset and started looping.
I don't know if it's a hardware issue or a software issue, but I can't flash another ROM to find out.
I was going to unroot today and take it down to Sprint. Of course, I can't get the dadgum thing to restart in a stable manner, so I was going to move the PC36IMG file to my SD card via ClockwordMod recovery.
I get in to the bootloader and choose recovery. My phone resets like normal before entering recovery, except now it enters a bootloop.
Pulled the battery, tried again. Same result.
So if you have any thoughts on any of the issues above (in particular the CM7 stability issues or the recovery issue) I'd love to hear them.
healthpellets said:
Ladies and gents.
First, I realize Saturday is probably not the best day to have an issue, so I appreciate any input I can get.
First, I'm running a rooted (toast method) evo, currently on CM7.
For the longest time, I didn't change roms, and then updated to CM7 a couple of months ago (iirc).
Shortly thereafter, I began experiencing random reboots, my phone getting extremely hot, and sitting through bootloops upon startup.
After upgrading my radio, nothing was solved. I downloaded another CM7 clean and flashed it. Same issues.
I download a Fresh Rom, and was unable to even flash it after wiping continuously.
I nanroided back to my CM7, of course with the same instability issues.
Then I nandroided back to the ROM (damage control, iirc) I had (that was perfectly stable at the time for nearly 1 year) before CM7, and I barely got it booted all the way through before it reset and started looping.
I don't know if it's a hardware issue or a software issue, but I can't flash another ROM to find out.
I was going to unroot today and take it down to Sprint. Of course, I can't get the dadgum thing to restart in a stable manner, so I was going to move the PC36IMG file to my SD card via ClockwordMod recovery.
I get in to the bootloader and choose recovery. My phone resets like normal before entering recovery, except now it enters a bootloop.
Pulled the battery, tried again. Same result.
So if you have any thoughts on any of the issues above (in particular the CM7 stability issues or the recovery issue) I'd love to hear them.
Click to expand...
Click to collapse
Try running a RUU from here.
http://forum.xda-developers.com/showthread.php?t=884060
[Hint, don't run 4.24.651.1 or you'll lose root ]
Since you rooted using Toast's method, I doubt you ever ran unrevoked forever. So run the 3.70 RUU or lower. If you can get into recovery, I'd flash unrevoked forever just to be safe.
Unfortunately your issue sounds like a mixture of problems I've seen others have. If this is the case, worst case scenario is that you'll never be able to boot your phone again if the issues continue... you'll constantly loop regardless of running RUUs, etc. Best case scenario is that you'll always have the bootlooping/overheating issue and eventually have to get a replacement.
Again, these best/worse case scenarios are based on what I've seen others experience. Hopefully the RUU will fix your problems.
Good luck!
Sent from my PC36100 using Tapatalk
Hi,
So yesterday i was walking the dog listening to some music when my phone just died. I booted it back up again, listened some more and it died again. When this happened i was running version 1.2.0 of said mod, so i decided to try the latest.
Seems like i have this issue there aswell Everytime my phone goes into lock it shuts down. Anyone have an idea what can cause this? my phone is almost a year and a half.
Update: Removed my memorycard and no problems so far, will try to format it and let you know.
Update 2: Formatted SD-card, seems to be working again now.
Update 3: Nope, its back again. Any ideas?
Thanks to everyone for any help on this
Juji
Try installing the test version of 1.4 and do a full wipe before that.
You should also try and flash any other ROM (maybe even stock) to make sure it's a ROM issue and not some HW fault on your phone.
Do we have any chance to have a 2wcr kernel for this great ROM?
I have the same 1-2 times per day after calling with
Virtuous Quattro RC3
so maybe a bug in ICS ?
Have been running without any force shutdowns for over 24hours now, so it might have been temporary for me atleast.
I got no problems so far with ICS on DHD, flashing from 1.2.0 to 1.4.0 without full wipe. I think different phones get different issus with same ROM. Maybe the installed apps are a reason for that.
I had that bug, but I was running Gingerbread at the time. The problem worked itself out, around the same time I upgraded the SD card. That might be a cause, maybe re-seat the sd card? Might be loose or something along those lines.
I'm running 1.5.0 and mine keeps saying no network and keeps rebooting itself????