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
Related
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...
Can't find an answer to this on google or xda. Didn't know if I should post this in General or Q&A.
I have been using my Incredible since it came out. I quickly learned about rooting, roms, s-off... with no problems. I have been running Skyraider almost from the beginning.
Here is the problem: A few days ago, I noticed on the SR thread that there were updates for the radio and hboot. So, I went ahead and flashed them. Almost immediately I started noticing the screen becoming unresponsive. After a minute or two I did a battery pull, rebooted, and again after a little while, freeze and reboot. I also noticed that even when the phone is awake but screen off, it would wake itself up. The rebooting and freezing makes it impossible to use my phone.
I tried everything I could think of:
Nandroid restore (obviously didn't work since this doesn't effect hboot or radio).
Reinstalled fresh SR Rom wiping everything, including dalvik, and did factory reset.
Finally, I downgraded back to the hboot and radio versions I had before, still no effect. (Baseband version 2.15.00.07.28, hboot .79 ).
I tried installing another ROM (Uncommon sense) to make sure it wasn't a ROM issue, ..same problem.
Please, any help would be much appreciated. I don't know what my next step should be.
do you overclock at all?
g00s3y said:
do you overclock at all?
Click to expand...
Click to collapse
No overclocking, I don't use setcpu, and I have been running the stock kernel. But it does feel like overclocking.
I wonder if the timing of events is just coincidence and its a hardware issue. I've had my Inc since June... rooted s -off in july and had no problems until about a month ago. I don't oc I use the new stock kernel but my phone hates change. Even flashing a small mod will cause rebooting.... and navigation always causes it. Phone heats up fast with these particular activities too but sometimes it will reboot at only 35c after a flash. I'm thinking hardware
Sent from my ADR6300 using XDA App
Thanks,
You may be right.
For now things are working, let's hope they stay that way.
Hey, guys!
I am in a desperate need of help. Here's my situation:
I've got an HTC Desire (obviously), which reboots every time the ROM starts. It all began after I decided to move back to a Sense ROM after having been testing ICS for the past couple of weeks. So, I flashed RCmix S - a ROM I knew to be stable and working snappily on my phone. Everything went well, I restored my apps with Titanium and then decided to remove some of the junk stock apps. When this was done, I restarted the phone, only to be faced with a series of reboots every time I got glimpse of the Sense UI (i.e. seconds after unlocking the SIM card).
I thought this might be a ROM-related issue, so I tried another one - Supernova. Same thing. Tried flashing it several times after full wipe always. No luck.
During the whole process I switched HBOOTs a few times - from stock, to Fatsys (IN2SD), back to stock. Tried several recoveries (AmonRA, 4Ext touch).
Even flashed official RUUs at least 3 times in order to get the phone back to its factory state. Once the stock ROM worked fine. Then I went on to root it and tried flashing one of the customs ROMs again, which, predictably, began rebooting just after SIM unlock.
I thought this might be connected to problems with the SD card, so I reformatted it completely - 6,8 GB FAT32 + 1 GB Ext4, using GParted. All by the book.
No I've got a clean SD (removed all the previous folders), but it doesn't seem to solve the problems.
Can anyone, please, think of something that I could do in order to get my phone back?
P.S. I forgot to mention, that my phone is S-Off. It struck me as strange, though, that it stayed S-Off even after flashing the RUUs.
New development: this morning, after successfully creating a Gold Card, I went on to try and flash a 2.2 RUU again. This time, however, the installer announced it was unable to access certain files and thus the flash process had failed. Meanwhile, the phone itself displayed a triangle and an exclamation mark on the 4 corners of the screen. I no long can access Recovery or the Bootloader. Help me, please!
Never mind, I managed it myself.
Hello everyone, just got a quick question to ask.
I was running CM10 stable and had a problem with my SD card a while back (which I never figured out), so I decided to preform a clean wipe of CM10.0 and a stock rom as a troubleshooting method.
I finally stuck back with CM10.0 and I've been rocking that install for some time, but have a problem. Every fifteen minutes or so the phone's cell connection would drop completely then pick back up a min or so later. It's very temperamental and I have no idea what was causing it. It never inhibited the utility of the phone, so I just dealt with it.
Today I flashed a clean install of Paranoid Android, gs2usr's unofficial version, and it still has the same issue.
I've flash different modems and the issue still remains, but I have no idea where to troubleshoot beyond that.
Any ideas guys?
|EDIT| Solution was taking it back to stock by flashing with Odin then re-rooting and flashing CM10 stable. No issues so far!
Has anyone has a similar problem to this or any ideas how to troubleshoot?
I've had my lovely 1X since launch. Soon after I rooted her and then had her run CM nightlies until the past week when I decided I wanted to revert to stock for a while
This went swimmingly; I locked, installed the RUU then a slew of updates and last night the phone was happy, stable, making and receiving calls. I plugged her in as normal before I went to bed.
Got up today, unplugged her and almost immediately she crashes and reboots. Continually getting to the first screen, able to unlock sometimes and then goes black and reboots or just freezes and needs resetting.
So I figure, it's software, right?
I unlock her bootloader again, flash CWR 5.8.4.0 again, flash the boot.img from this JB rom and then the rom itself, then 4.2 gapps.
Everything fine. While plugged in.
Unplug; reboot cycle again
Not entirely sure what to do with her now other than try a bunch of other roms. A problem that's consistent across roms/recoveries/boot images, locked and unlocked though...
Anyone have any ideas, please?
I suppose you did a full wipe every time you changed the ROM? Don't be so sure it's only software... Could be a hardware, too.
[email protected]|-|oR said:
I suppose you did a full wipe every time you changed the ROM? Don't be so sure it's only software... Could be a hardware, too.
Click to expand...
Click to collapse
I did wipe of course.
And if it happens across roms, lock/unlock etc. I probably IS hardware. Just want to be as sure as possible.