Related
I have a non-rooted Sensation Z710e running Android 4.0.3 and v3.6 Sense.
Since upgrading to ICS it's been unstable. Getting worse I think, with more frequent restarts. Never did that on GB.
Yes I can do a factory reset but since apparently I'm not the only one with this problem, I thought this would be a good place to ask if that actually solved the problem for those who did that.
Separate (NOOB-level) but related question: Is there a problem that with every one of these restarts, the Android 36-step install happens?
This seems stoopid and takes forever to get he phone operational each time. It's not like it's actually pulling down new updates.
Note I did check for other threads for this and none specifically met my issue's criteria.
NorrRadd said:
I have a non-rooted Sensation Z710e running Android 4.0.3 and v3.6 Sense.
Since upgrading to ICS it's been unstable. Getting worse I think, with more frequent restarts. Never did that on GB.
Yes I can do a factory reset but since apparently I'm not the only one with this problem, I thought this would be a good place to ask if that actually solved the problem for those who did that.
Separate (NOOB-level) but related question: Is there a problem that with every one of these restarts, the Android 36-step install happens?
This seems stoopid and takes forever to get he phone operational each time. It's not like it's actually pulling down new updates.
Note I did check for other threads for this and none specifically met my issue's criteria.
Click to expand...
Click to collapse
Well actually there is a thread about random restarts with ics and someone say that is battery related and someone say that is sw related...
Sent from my Sensation using Tapatalk 2
@ NorrRadd My advice to you is to go and download RUU either from football links or from HERE Flash your phone with the software, your problems sounds like bad Upgrade. Anyway it is original software so you want make mistake. You know how to use RUU ? (If you dont...
1.download the file
2.Run the .exe in windows
3.Connect your phone (USB)
4.Follow the instructions on screen )
A lot of people have been having the problem. I called HTC and my warranty isn't up so I can send in my phone and get a new mother board. The rep confirmed that they have been getting lots of complaints about this problem.
I tried this fix http://forum.xda-developers.com/showthread.php?t=1622683 and have been going 3 days without a shutdown. I have never been able to go that long before. I just used a piece of notecard and wedged it in there. Worth a try and of that doesn't work call HTC if you have had your phone for less than a year.
Thanks all. I will look in ruu and having HTC look at it as it's still under warranty. Will let you know how I make out.
Thanks again.
Quick background: I purchased a One X from AT&T a few weeks ago. It came with the 2.20 firmware, so I used the X-Factor Exploit and unlocked the bootloader via HTCDev. From there I flashed TWRP Recovery and then AOKP.
Pretty much everything was fine at that point, except for the fact that once or twice a day I would pull my phone out of my pocket and it would be completely unresponsive. None of the buttons would wake the phone up, plugging it in didn't do anything, and it wouldn't receive calls. I would then have to do a hard reboot (Power + Volume Down) to get anywhere.
I thought maybe it was an AOSP problem, so I flashed a Sense-based ROM (CleanROM 5). I experienced the same issue.
From there, I re-locked the bootloader and ran the latest RUU. That was 4 days ago and I have yet to experience the problem again.
Has anybody else experienced this, and is there any way to prevent it?
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
redpoint73 said:
power + Vol down puts you into the bootloader. What do you do from there to get the phone booted? Have you tried just holding the power button for 5 seconds or so, until the capacitive buttons flash (same as a battery pull)?
GPS on, by any chance?
Click to expand...
Click to collapse
I would just select reboot and it would boot normally. Power alone would also work, I believe. I usually just did power and vol down out of habit I guess.
GPS and WiFi were always on.
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
c5satellite2 said:
What radio/RIL were you running?
What hboot version?
You are on 2.20, did you flash the correct KERNEL manually and clear dalvik and cache?
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
HBoot 1.14. Didn't mess with the radio, so the stock AT&T 2.20 one (0.19as.32.09.11_2_10.105.32.25L).
Yes, I flashed the correct kernel. It did it with both the plain AOKP kernel and rohan's kernel.
Cleared caches several times.
GPS on when this happens, by any chance?
redpoint73 said:
GPS on when this happens, by any chance?
Click to expand...
Click to collapse
I hardly ever disable it, so it was likely on. No idea if it was actually in use any of the times.
I can say one time it happened immediately after a call, one time it was immediately after a SMS notification, and the rest just seemed to be randomly in the middle of the day.
Try going straight to CR5 directly from the stock ruu rom and see if it persists. Maybe the aokp Rom borked something along the way and the ruu has restored it now. I have seen issues similar to this that only the ruu will fix.
Sent from my HTC One X using xda app-developers app
Have the same issue.Try going to ViperXl and see what happens.My phone constantly reboots and enters sleep of death.I always have the gps disabled.have 1.09 hboot.And currently I am on 1.85 stock at&t.This issue is kikling me
I only mention GPS, since my old phone (Desire Z) had an issue where leaving the GPS on, would make the phone shutdown, and only a battery pull would start it (never tried going into hboot). Which sounds similar to what you were seeing. In my case, no ROM, kernel, or radio flashing ever remedied it. And I could isolate the issue to the GPS being on. If the GPS was used, the phone was going to black screen within a couple hours, without fail. But rebooting the phone after using the GPS (and shutting off GPS) prevented it every time. A few other owners of the DZ had the same problem. One guy sent his into HTC, and they told him it was a defect of the GPRS module, and replaced the motherboard, which fixed the problem.
Hopefully, its not a similar hardware issue in your case. But the fact that you have the GPS on all the time, and the black screen hasn't cropped up like clockwork (like it did in my case) seems to point to the fact that it might not be the exact same issue.
These types of issues tend to be really hard to troubleshoot (and pinpoint the cause). In my case, it took me a couple months to realize it was the GPS, since I usually have it off, and don't use it all that often (usually just when travelling). And I also suffered a lot of "placebo effect" type incidents while flashing various ROMs and kernels trying to fix the issue. If the issue doesn't crop up again after running the RUU, I'd consider myself lucky, and leave it well enough alone.
No it is not the same problem redpoint73.This only happens on Custom ROMS.I have tried every combo on the 3 ROMS i flashed.Could it be an int.d problem???My only is this.
nighthawk696969 said:
No it is not the same problem redpoint73.This only happens on Custom ROMS.
Click to expand...
Click to collapse
Yeah, I already said its probably not the same problem. But it doesn't hurt to check everything. As I mentioned, its easy to get sucked into thinking you have the cause isolated, when you really do not.
I understand what you're saying but i have checked it,i'm sure..
nighthawk696969 said:
I understand what you're saying but i have checked it,i'm sure..
Click to expand...
Click to collapse
It also doesn't sound like your problem is exactly the same as the OPs. You mention reboots, while OP does not (just BSOD, or shutdown requiring rebooting in hboot).
No my main problem are the Sleeps of Death.There are no BSODs in android
nighthawk696969 said:
No my main problem are the Sleeps of Death.There are no BSODs in android
Click to expand...
Click to collapse
Some people have been calling this condition BSOD = Black screen of death. Yes, its a little too derivative of things like Windows blue screen, XBox RROD etc. But you get the idea.
Update: I re-unlocked the bootloader and flashed CM 10.0.0 upon its release. I've yet to encounter this issue, so I'm thinking my stint on CleanROM might have buggered something. I probably forgot to wipe something somewhere along the line. D'oh.
I am, however, having a pretty severe albeit unrelated problem with an app called Voxer. Every time I listen to a message it kills the microphone until I Force Stop the app. I guess I'll pop over to one of the other AOSP ROMs and see if it persists.
I was having a similar problem on king kang and pacman. I could turn the phone on and off with the power button, but the touch screen was completely unresponsive. Happened randomly, I would have to hold the power button down and watch the lights flash until the phone shut down, and would be fine after a reboot. When I tried installing viperxl, I had the same issue during the aroma installer, I had to try flashing it 7-8 times, because it kept freezing during the install. No issues running it after a successful install. I was using king kang and rohans b5 kernel when it was happening most often
Ever since I bought my phone, before being rooted and even on stock ROM, I'll get delayed text messages and they wont recieve until I reboot my phone or switch airplane mode on and off. Then they hit me ALL at once. This happens atleast once a day and people will end up thinking I'm ignoring them because of this problem. Is it a problem with the HTC One X in general? or Android? It still happens on every single ROM I tried too and I have tried various radios and none fix it. I am on AT&T, and currently on MagioRom. It still does it regardless of what ROM though. This is the one single thing that I have just sort of learned to put up with, as much as I hate it. I came from an iPhone and they never had that problem so I really miss that. I reboot my phone about 5 times a day to remedy it. Besides that this phone is amazing of course.
Oh and was the bug with iPhone screenshots being sent through text to the One X and coming out really really tiny ever fixed? Im still getting that problem too.
It's not a problem with the phone or Android as such. Do you ever suffer signal drops which may cause this to happen? Or do you live in an area with low signal? It sounds more like a carrier bug to me.
Sent from my Evita
timmaaa said:
It's not a problem with the phone or Android as such. Do you ever suffer signal drops which may cause this to happen? Or do you live in an area with low signal? It sounds more like a carrier bug to me.
Sent from my Evita
Click to expand...
Click to collapse
I always have great signal, no signal drops ever, so I never thought it would be my carrier, thats strange... Now I don't know if its AT&T or a defect with my phone...
It could be an issue with your phone? Have you tried running an RUU? I'd do that and leave it stock fire a few days to see if it continues. You'll want to make sure you're safe to RUU first though, what are your hboot details?
Sent from my Evita
Hboot 1.14
I can't RUU yet though cause I'm still S-On, which I haven't tried to do yet because I didnt wanna risk messing my phone up... Would that actually help?
And could it be an Hboot version problem or firmware problem? Cause I bought my phone about 1 year ago and it came with Icecream Sandwich. And I've had to deal with this problem the entire year.
It could be anything. Do you have SuperCID? You definitely must get s-off before running an RUU.
Sent from my Evita
Yep, it says 111111111111
I'll try getting S-Off and running RUU then, I just really wanted to avoid doing that but I guess I have no choice.
Sometimes it's the only way to find out what you're dealing with. The process is simple, it took me five minutes.
Sent from my Evita
Just picked up an HTC ONE XL
Seems to have some issues I did some research and found out there was an issue with updates.
Issues
1.IF I do a factory reset as phone is loading speaker phone speaker works. Then stops after home screen loads
2.Home back apps buttons are use less (very common)
My Phone
evita s on
hboot 2.14
3.18
I used a ruu nothing changed. Is there any way for me to root or downgrade this phone.
It seems the only option I could find are with linux(which I never used) .
Why are you wanting to root/downgrade? If you've run an RUU and those problems are still present you're dealing with hardware faults. Only a repair will fix those.
Sent from my Evita
timmaaa said:
Why are you wanting to root/downgrade? If you've run an RUU and those problems are still present you're dealing with hardware faults. Only a repair will fix those.
Sent from my Evita
Click to expand...
Click to collapse
Not at all. For some reason select htc one XL were not compatible with the 3.14 update.
People with these phones lost there front touch panel and some people lost the speaker.
my speaker randomly turns on and off since update, my front touch panel lights up but has no use.
If you're confident the problems were caused by the update itself then that sounds like it should be covered by warranty.
Sent from my Evita
I began posting this problem in a previous thread but am starting a new one to avoid clogging said thread.
Here are my phone details at the moment:
S-Off
SuperCID
HBoot 2.14
Radio 0-24p.32.09.06
Open-DSP-v34.1.0.45.1219
I bought the phone used off kijiji. It was stock when I got it. Rogers, Android 4.1, 3.17 firmware. I unlocked the bootloader, got SuperCID and S-Off, flashed TWRP and flashed a custom ROM - CleanROM. Things were okay for a bit.
Then I started getting random restarts and losing signal. I realized I was on 2.14 hboot so I updated to 2.15. I thought it fixed the problem but no- before long, more random reboots--though I did fix the signal issue.
So I flashed Beastmode kernal. Now, I did this without doing a full wipe - just threw it on top of CleanRom. Possibly a bad idea because everything kinda got all screwy at this point. The phone started acting really oddly--freezing a lot, restarting even more often, and sometimes the touchscreen would act up.
Next step: I tried to do a full wipe and flash a different ROM: KickDroid. Only thing was, it wouldn't flash. The installer would crash, most of the time at 30%. The phone would then restart, though it wouldn't boot (obviously), so I'd have to hold down the volume to put it into the bootloader.
Tried flashing CleanROM then - no go. It wouldn't flash either - phone would just power down.
This became a theme. The phone would just start turning itself off all the time. Even sometimes when I was doing a wipe in TWRP, the thing would just crash partway through and turn off. Somehow, this morning, I DID manage to get CleanROM to flash, but then it wouldn't boot- froze at the Google splash screen and turned off...
On timmaaa's suggestion at this point I went to an RUU and tried to get the phone back to stock. Went with the 3.18 Cingular RUU. For whatever reason, it didn't work the first time (might have been my fault - I forgot to uninstall HTC Sync Manager) but when I tried it again, it did. I was excited - phone was, hopefully, back to its old self, after all!
Booting to splash screen: freezes on the HTC logo. Turns off, randomly. AAGGHH!!!
So I try again, knowing, at this point, it's futile. The phone BEGINS to boot up. Gets to the Cingular screen and then just enters into Android - says it's going to start refreshing apps or whatever... and then it turns off.
Note that I have it sitting in the bootloader right now and it is not turning off. The bootloader itself seems to work well enough.
Even now, I tried to boot the thing up just one more time, and it again just nearly got into Android but turned off before fully loading.
I'm at a loss. It's not like I've been just randomly flashing things on here - I only used ROMs that worked for the phone. Maybe my dirty flash (is that the right terminology) of Beastmode was the problem, but I feel like it shouldn't continue to persist this long, after using an RUU. I'm wondering if perhaps it's a hardware issue at this point.
Any thoughts, ideas, suggestions, etc. are amazing... thank you.
At this point I believe you've tried pretty much everything you could try. It's possible you have a faulty motherboard.
Sent from my Evita
timmaaa said:
At this point I believe you've tried pretty much everything you could try. It's possible you have a faulty motherboard.
Sent from my Evita
Click to expand...
Click to collapse
Darn. Anything that can be done about that? Is it feasible or even worth it to try to replace it?
Get this - it just booted to Android, and seems to be staying there. For the time being, anyway.
Edit: never mind. lol. Turned right off again after connecting to wifi.
It all depends on whether you think it's worth the money to repair it, or just to buy a new device.
Alright. Thanks a lot for your help. I'll try to consider my options.
Try running a different RUU. Not sure of it will help just a suggestion
Sent from my HTC One XL using xda app-developers app
johnnyp12321 said:
Try running a different RUU. Not sure of it will help just a suggestion
Sent from my HTC One XL using xda app-developers app
Click to expand...
Click to collapse
Yeah, I'll give that a shot, too. Thanks. Though I'm not that optimistic at this point, lol.
On a related note: I have the opportunity to buy an HTC One XL with a broken screen for cheap. What do you guys think the options are for me (a) taking the mobo out of the broken one and using it in mine or (b) replacing the screen on the broken one with the working one from mine? Do you know how difficult/manageable either process is?
The phone seems to be more or less completely dead now. It will occasionally power up but can't do much beyond the bootloader. Anyone have any experience replacing motherboards on the HTC One XL? Is it possible to swap one out from a working phone? Or is it possible to use my screen to replace one on a phone with a broken screen?