[Q] Random reboots? - Sprint HTC EVO 4G LTE

My Evo just found itself a new vice. Every now and then it reboots. Only happens when it's locked, never when I'm using it.
So far I've tried reflashing it to stock, and tried a few different ROMs, with no effect.
I've also tried shaving a bit of plastic off the door by the power button, thinking that if the phone bends in my pocket a bit, it could push the power button. That didn't help, and wasn't even a very sound theory, since the phone reboots rather than just powering off.
Anyone got any ideas?
Thank you!

I had that happen on stock ROM, custom ROMs. However, it's not happening on CM10 at all. I didn't find a reason for it, but maybe it's Sense related?

i had the same problem with my evo 3d.. i tried everthing.. last thing i did was unroot and ran RUU and it went away.. after running the ruu i was still s-oss so all i had to do was flash a custom recovery and then a custom rom and i was good to go.. the reboots stopped :good:

Related

Screen won't come back on

Recently my phone has been suspending the screen and not bringing it back when I press the power button. I was running 3.2.6 before, reverted to 3.2.3. Tried hard-resets, taken out the battery, tried running with just the rom and nothing else installed after flashing, still doesn't work.. I've also tried taking out my memory card and running without that.
The power button still works because it will still turn the phone on, and bring the phone out of sleep sometimes, but if it doesn't work on bringing it out of sleep it seems that I have to soft-reset or the phone just doesn't work...
Any suggestions? Also.. I this is a bell phone, they have stock roms available on their site, but am I able to get the stock bootloader back on in case I have to warranty this thing?
You've tried most things that people could suggest, however have you tried a different ROM?
I know this used to be a very common problem when the Tilt came out, but once everybody started changing ROMs, it slowly disappeared.
My suggestion in short: Try relocking the bootloader
My Two Cents:
This is actually the most evil bug ever for this phone. I got this bug on my Sprint Mogul and couldn't get rid of it. Some people say it's because Java is running and then causes the phone to hang, but I never found that to be the issue. I got a Verizon XV6800 and experienced this problem only when I was flashing from stock to dcd 3.2.6. It occurred after I unlocked the bootloader, but after I flashed to dcd it went away. It was between having the stock and dcd roms that I found that most people experienced this problem when the loaded they new bootloader.
If I had to guess, based on my knowledge of operating systems, that some process is taking up a lot of resources, mostly CPU time, and is not allowing the phone to come out of standby. I guess this because sometimes I have had this happen and the screen would come on after a LONG delay.

[Q] Touchscreen Issues??

Hello all,
I've had the same touchscreen? issues with 2 different Evo3D's. The first phone I had replaced even though when I took the phone to a Sprint repair center, the Slate machine said theres nothing wrong with the phone.
What happens is quite simply is the phone starts acting crazy. It acts like Im pressing on the screen, making tons of selections, calling people etc...I can click on the power button to make it stop. But then it will act up again in a few minutes. The first phone I had the store flash back to stock, turned s-off etc... It didn't make a difference. No matter what ROM is on the phone it continues to do it. So I had that phone replaced.
The second phone does the exact samething. If I didn't have the first phone in front of me when I received the second one, I would have thought they sent me the same phone back to me. I rooted this one right away as the other one so I dont know if the phone had the same problem before the root process. I've stuck on a ton of different ROMS to various degrees of success. I'm running Eternity right now because it allows me to at least use the phone semi functionally. The touchscreen problems are limited to the upper 20% of the screen where its unresonsive most of the time. But the craziness clicking is down to a minimum comapred to other roms.
I fixed the problem once when I was flipping ROMS and kernels. I put on ViperROM2.1 then flashed the Tiamat kernel. I was like yesssssss, I found the right combo. But alot of the phones functions didnt work like voice reconition, 4g, etc... So I cleared storage to start again and all the problems of the touchscreen as before came back. I've tried flashing kernels like Tiamat, stock, dual cores, single cores. Always have the same result. Last bit of info is I tried to superwipe and that failed. So maybe theres something in the internal memory thats causing all these problems? any help would be appreciated.
Thanks
kdub2000 said:
Hello all,
I've had the same touchscreen? issues with 2 different Evo3D's. The first phone I had replaced even though when I took the phone to a Sprint repair center, the Slate machine said theres nothing wrong with the phone.
What happens is quite simply is the phone starts acting crazy. It acts like Im pressing on the screen, making tons of selections, calling people etc...I can click on the power button to make it stop. But then it will act up again in a few minutes. The first phone I had the store flash back to stock, turned s-off etc... It didn't make a difference. No matter what ROM is on the phone it continues to do it. So I had that phone replaced.
The second phone does the exact samething. If I didn't have the first phone in front of me when I received the second one, I would have thought they sent me the same phone back to me. I rooted this one right away as the other one so I dont know if the phone had the same problem before the root process. I've stuck on a ton of different ROMS to various degrees of success. I'm running Eternity right now because it allows me to at least use the phone semi functionally. The touchscreen problems are limited to the upper 20% of the screen where its unresonsive most of the time. But the craziness clicking is down to a minimum comapred to other roms.
I fixed the problem once when I was flipping ROMS and kernels. I put on ViperROM2.1 then flashed the Tiamat kernel. I was like yesssssss, I found the right combo. But alot of the phones functions didnt work like voice reconition, 4g, etc... So I cleared storage to start again and all the problems of the touchscreen as before came back. I've tried flashing kernels like Tiamat, stock, dual cores, single cores. Always have the same result. Last bit of info is I tried to superwipe and that failed. So maybe theres something in the internal memory thats causing all these problems? any help would be appreciated.
Thanks
Click to expand...
Click to collapse
My guess is that something is screwing up kernal wise or your flashing. If your phone was fine stock then something got dicked during the flash.
Is there anything I can do to a clean wipe and start fresh again? Or should I try to figure out why the Superwipe isnt working? Or do I have to flash all the stock back on and turn the s-on and get a new phone? I think the digitizer is causing these issues.

[Q] random reboots

Ok I have been having an issue where my phone randomly reboots or completely powers off. This started after I started using newtsone ics ROM. It was suggested I try other ics roms which I did and then it was suggested I switch back to a gb ROM which I did. However it is still doing it. I thought maybe the battery was lose and it was losing power so I tried to wedge a small piece of paper in there to make a tight fit but that didn't work. It doesn't do this if connected to a power source and I don't have a battery to test my battery theory. Has anyone else had this issue or have any ideas on how to fix it? My newest issue now also is that texts don't come through. They only come through when I make a call then six or seven of them will finally come through. Any thoughts? I'm hboot 1.40 s-off and running the latest radio.
Are you overclocked?
Sent from this 3D thing
Try this
http://forum.xda-developers.com/showpost.php?p=10878511&postcount=8311
#Root-Hack_Mod*Always\
Ye I gR this.before too. r u using boost or virgin mobile. also reflash your radio. I was having reboot issues with the baseband 1216 but it was because I didn't use freezas all in one. my pro wasent right now I have 1.43_003 where I had 1.24_003
No I'm not overclocked and not on boost or virgin. I don't know if mentioned it before in my first post, but it only does this when the phone is sitting idle and the screen is off. If I unlock the phone and the screen is on, actively using it, or it's on the charger then it's fine. I'm going to try reflashing the radio or going back to my old one and see if I have any luck with that. Anything else you can think of in the mean time let me know.

[Q] phone app acting up?

So one day out of the blue, my phone starts acting weird. I think hey no big deal, and I just go on to restart the darn thing. When it boots up it acting normal again, but then I start to get a phone call. No big deal I answer it, but when I go to hang up it is still stuck at the point I answered it. With the answer or decline button. I think to myself to reinstall the rom again. Do that same problem still going on... I install another rom same problem two roms later same problem even after flashing a stock rooted rom.. Now here is my real question what do you think is my problem? I went from cm 10.1 working fine, to an older cm10.1 then fresh rom 3.5 then stock. With the stock rom it would boot all the way to the home screen then restart. But on my cm 10 it would boot up fine act normal then when screen timer turned the screen off it would be stuck off not like frozen the lights at the bottom would cut on but not the screen, and I'd also hear it click off.
Any ideas or is this just something for sprint tep to handle?
More information is needed to even begin to answer.
S-on or S-off, recovery version, clean or dirty flash? Take a look at the sticky for rooting and flashing roms to ensure you are doing the right processes etc.
Sent from my EVO using xda app-developers app

Stuck entering recovery

UPDATE: SOLVED
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
XDA mark said:
Here I am again,
Story
I've been using a HTC One since April , but I keep maintaining my GS3 (I9300) that my girlfriend uses now.
I keep maintaining it because it keeps needing maintenance. I always use stable ROM's and no custom kernels or other modifications, because she just wants a normal working phone. Sadly, it's been problems after problems. First of all, after using CM10 for months starting in April, the phone just stopped working. I still don't understand what happened. It started performing worse and worse, until it wouldn't even boot up anymore. Anyway, I managed to get a stock ROM on it after sadly deleting everything of her phone. The phone at least worked again.
Recently, I decided to flash something different for her because it was such a laggy old ROM. I flashed ARHD 40 (android 4.3) since I use ARHD on my HTC One as well and it's usually very stable. The performance was way better now, her phone was as fast as my HTC One. Though she became aware of one problem quite quickly: the phone takes anywhere from 5 seconds to 1 minute to wake up from sleep. I even called her and it wouldn't appear because the phone was not waking up.
Now here comes the problem
Running ARHD 40 (android 4.3), I decided to flash Boeffla-Kernel 5.1beta12 (newest I could find). As far as I read, this would fix the slow/not waking up from sleep.
Now here comes the real problem
I needed to boot into recovery to flash this kernel. Since this ROM didn't have a quick boot into recovery shortcut, I decided to download ROM Toolbox Lite. First of all to see what it's about, since I recalled hearing nice things about it. And it had a boot into recovery option, so that would be easy.
I pressed the button to go into recovery.
Since then, my phone is completely stuck, constantly trying to boot into recovery but failing. You see it's trying (the 4 buttons at the bottom appearing from the recovery) and sometimes even the wallpaper shows up. But it always stops, after which it reboots and I see the logo. And this keeps repeating over and over again.
I removed the battery a few times, I tried holding down the power button a long time, to force it to just boot itself up normally again. I can enter download mode, though I have nothing there to help me. Phone is basically completely useless.
My question
Does anybody know anything about this? Is it a known problem? Is my first experience with this ROM Toolbox Lite the most horrible one ever, or does it play no role in the problem?
It was to late to start searching for solutions yesterday evening, I had to work early again today and I was so pissed I would have broken the damn plastic thing in two. So I just decided to leave it and my girlfriend is passing this day without one. But I'm really sure I want to fix the damn thing when I get home in a few hours. If possible, to just make it stable, fast and NORMAL, with no more weird problems in the future...
Thanks in advance!
Kind regards
Click to expand...
Click to collapse
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
tallman43 said:
What do you mean "can enter download mode, though I have nothing there to help me" What happens exactly when you enter download mode....Can't you just flash back to stock with odin in download mode ?
Edit:..Have you tried ADB into recovery or tried this >>> http://forum.xda-developers.com/showthread.php?t=1703488 <<< toolkit
Click to expand...
Click to collapse
I can enter download mode normally, so I can use Odin to flash stuff.
I just flashed that kernel I wanted to flash before my phone went trippin, but after flash the same continues. Re-downloading ARHD 40 via my laptop now and going to reflash it via odin, hope that my phone can then let go of it's obsession of trying to get into recovery.
There must be a way to fix this, I didn't make a Titanium Backup for a while. Don't want to lose stuff just because I got some super rare weird problem... again. Why does tech hate me
EDIT:
Realized that I can't flash ARHD 40 because it only comes in zip not tar... anyway, tried flashing the newest version of philz touch recovery, still didn't change anything.
EDIT 2:
Flashed TWRP recovery via ODIN, now everything is fine again. It rebooted into TWRP normally, then choose to reboot the device. Everything is still there, like nothing ever happened.
THANK you lord!
Out of interest, how do you find the HTC 1 compared to the S3?
gsw5700 said:
Out of interest, how do you find the HTC 1 compared to the S3?
Click to expand...
Click to collapse
It's an entirely different phone, especially how it feels and looks. After using the One for such a long time, I find it super weird to hold a S3.. it feels so light and "cheap", though ergonomically the S3 is a tad easier to hold then the One. Overall I enjoy using the HTC One much more as it feels really solid.
Besides that it's fast and stable, what you would expect, but not much faster then a S3 with a good ROM. Screen is really excellent, this is also a big difference from the S3. It's a different type of screen and you can really notice. The speakers are the nicest you can get on a phone and compared to the S3 they are really a league above. The camera is average, sometimes it's great sometimes it isn't. Battery life is comparable to the S3.
Not that I didn't enjoy my S2 and S3 at the time, but I'm not really interested in the Galaxy line anymore at the moment. Samsung really has to do something amazing to get my attention again Will see what HTC brings with the successor of the HTC One, might upgrade to that one. I'm also curious about the iPhone 6 to be honest, the small screen is the main reason I haven't owned an iPhone in my life, if that changes I might want to try it. Or I might just use my current device for a second year for a change, since it's excellent
Many thanks for that, I now intend to take a look at the new HTC m8 - hoping the camera is better!
Me too. If they make a big leap with the camera and bring it on par with the iPhone 5S for example, it would be fantastic. Battery life should also be brought to the new higher standards of the LG G2.
If these 2 things happen they already got me, since it's a near perfect phone. Add some bonuses like making the bezels smaller/screen larger in the same body... don't think I could resist

Categories

Resources