So this seems to be the second time this has happened with my One X. I believe it was on two separate ones too (I had a warranty exchange). What happens is the phone will freeze while I'm using it. Then it'll reboot itself. But from then on, it won't get past the red text htc screen. I have to the RUU back to stock and redo everything. Has this happened to anyone else?
mikel.canovas said:
So this seems to be the second time this has happened with my One X. I believe it was on two separate ones too (I had a warranty exchange). What happens is the phone will freeze while I'm using it. Then it'll reboot itself. But from then on, it won't get past the red text htc screen. I have to the RUU back to stock and redo everything. Has this happened to anyone else?
Click to expand...
Click to collapse
edit :: Scratch that. Turns out my power button is on the fritz. Kept thinking i was holding it down.
mikel.canovas said:
So this seems to be the second time this has happened with my One X. I believe it was on two separate ones too (I had a warranty exchange). What happens is the phone will freeze while I'm using it. Then it'll reboot itself. But from then on, it won't get past the red text htc screen. I have to the RUU back to stock and redo everything. Has this happened to anyone else?
Click to expand...
Click to collapse
I think this should be in Q&A section.
Sent from my Evita
mikel.canovas said:
So this seems to be the second time this has happened with my One X. I believe it was on two separate ones too (I had a warranty exchange). What happens is the phone will freeze while I'm using it. Then it'll reboot itself. But from then on, it won't get past the red text htc screen. I have to the RUU back to stock and redo everything. Has this happened to anyone else?
Click to expand...
Click to collapse
never seen this issue before. sorry
Related
Not sure what has changed but recently my camera/camcorder doesn't work. The screen is just black. Doesn't do anything. If I press home the phone goes back to home screen. Any ideas? What should I do.
I had this issue happen to me about 2 weeks after having purchased my inspire. Luckily I was within the 30 day warranty and got a new phone that same day.
When it happened, I didn't even bother to reset the phone or troubleshoot the issue. You might want to try that. But, if you're within the 30 days, head to an ATT store and show them the problem.
Sent from my Desire HD
billymild said:
Not sure what has changed but recently my camera/camcorder doesn't work. The screen is just black. Doesn't do anything. If I press home the phone goes back to home screen. Any ideas? What should I do.
Click to expand...
Click to collapse
Well, if it worked before, and all of the sudden it doesn't, you should probably make sure there's no chance it was something you did, before going through the hassle of a return.
First thing to do is start checking apps installed, and services running.
Roms flashed? One or two had known issues with camera preview not showing.
Does the camera actually still take the picture, even though preview is non-visible?
Inspired Ace 1.0.1¦ XDA Premium
I'm rooted running Leedroid and a very odd occurrence happened tonight. The volume level started decreasing by itself until it hit vibrate and then the phone just became unresponsive. I pulled the battery and now no matter what I do the phone won't power back on again. if I press power or hold volume down and power, it vibrates 5 times and shows a solid green light, still doesn't turn on. Even if I hook up the USB cable same thing, only exception is that it immediately starts vibrating 5 times without pressing any buttons. I also left it on the charger for a while and swapped out batteries and nothing changes. Has anyone experienced this same issue?. I'm thinking maybe it's a hardware error and possibly bricked.
UPDATE ... I took the SD card out and let it sit for about 30 mins and then it powered up fine. This is very odd indeed. I don't know what could have been the problem.
My wife had this happen to hers after she shut down the phone and it would not boot back up properly. Trying to boot would either give five vibrates and green led or three vibrates and a red led iirc depending on if I tried a normal boot or hboot. Was on irc with attn1 trying a number of different things, as I was able to get adb to recognize the phone when booting into recovery even through the screen was blank, with no success, and finally just had at&t send a replacement.
I did try swapping another sd card but didn't try booting with no card installed so I don't know if that would have helped in my case though I am certainly curious now after reading your post. Wish I could get the phone back to test now. lol
Any solution to this? My phone is stuck like this now.
jznomoney said:
Any solution to this? My phone is stuck like this now.
Click to expand...
Click to collapse
I had one go this route too. I think its a corrupt boot partition (or some other critical partition in the built-in flash ROM). I could not get it to boot to anything usable at all. I ended up filing a warranty claim and got a new one. Hopefully your's is still covered, or you have insurance, otherwise, your best bet is send it back to HTC for repair. They are actually pretty reasonable from what I hear, but you'll be without a phone for awhile.
I did a rma straight from HTC since I didn't have the insurance from at&t on it. They said it was the motherboard that died and replaced it.
shawn1224 said:
I'm rooted running Leedroid and a very odd occurrence happened tonight. The volume level started decreasing by itself until it hit vibrate and then the phone just became unresponsive. I pulled the battery and now no matter what I do the phone won't power back on again. if I press power or hold volume down and power, it vibrates 5 times and shows a solid green light, still doesn't turn on. Even if I hook up the USB cable same thing, only exception is that it immediately starts vibrating 5 times without pressing any buttons. I also left it on the charger for a while and swapped out batteries and nothing changes. Has anyone experienced this same issue?. I'm thinking maybe it's a hardware error and possibly bricked.
UPDATE ... I took the SD card out and let it sit for about 30 mins and then it powered up fine. This is very odd indeed. I don't know what could have been the problem.
Click to expand...
Click to collapse
it sounds like something is going on with you data partition and sd card format. i recomend booting in to clockwork mod recovery and wiping all data and cache partitions as well as dalvik and then re-installing the ROM of your choice. id also recomend backing up your SD card and reformatting that as well, and if none of that works. i think its time to try a new rom
I have this issue!!!! The EXACT same thing happened to me! I can't resolve it .. if i turn it on like normal, it flashes orange and vibrates 3 times. If i hold vol + down and turn it on, solid green and vibrates 5 times/ black screen. Help!
Chronei said:
I have this issue!!!! The EXACT same thing happened to me! I can't resolve it .. if i turn it on like normal, it flashes orange and vibrates 3 times. If i hold vol + down and turn it on, solid green and vibrates 5 times/ black screen. Help!
Click to expand...
Click to collapse
Try and take out the SD card for 30 min
Sent from my HTC Desire HD using XDA Premium App
I tried that and it did not work. I tried both the sim and sd card. I still need help. This is the only post on the internet I found that reproduced the issue -- and if this EXACT issue I have is happening to someone else, there has to be a way to fix it.
If my volume+up button worked, I could boot it to recovery. I need a way to do this without the use of the volume+up.
jznomoney said:
I did a rma straight from HTC since I didn't have the insurance from at&t on it. They said it was the motherboard that died and replaced it.
Click to expand...
Click to collapse
How much did they charge you?
And if anyone fixes my issue, I will donate $50 if you find me a resolution that works for me.
Chronei said:
How much did they charge you?
And if anyone fixes my issue, I will donate $50 if you find me a resolution that works for me.
Click to expand...
Click to collapse
Try to run the ruu .exe file from your computer
Sent from my HTC Desire HD using XDA Premium App
Chronei said:
How much did they charge you?
And if anyone fixes my issue, I will donate $50 if you find me a resolution that works for me.
Click to expand...
Click to collapse
HTC didn't charge me anything since it was a hardware failure. Your inspire will still be under warrenty since it hasn't been a year yet. Just call htc support and they will create the rma. You will just have to pay shipping to them. It took about 10 days round trip.
an update .. i can run droid explorer with it turned off, but plugged in usb and it detects it. I tried rebooting/rebooting to recovery via droid mgr but same thing happens. But it's a good sign pc detects it .. anything I can do?
I really need this fixed. If you can find a resolution, I'll donate $50
Chronei said:
an update .. i can run droid explorer with it turned off, but plugged in usb and it detects it. I tried rebooting/rebooting to recovery via droid mgr but same thing happens. But it's a good sign pc detects it .. anything I can do?
I really need this fixed. If you can find a resolution, I'll donate $50
Click to expand...
Click to collapse
Ok thats good news that it can read it. Connect it to the computer and run that file.
http://www.filefactory.com/file/b50...60.19_26.06.04.06_M_release_166557_signed.exe
XAviierG said:
Ok thats good news that it can read it. Connect it to the computer and run that file.
http://www.filefactory.com/file/b50...60.19_26.06.04.06_M_release_166557_signed.exe
Click to expand...
Click to collapse
Hmm, I don't think i can execute files with droidexplorer, can you ? Or run it with windows?
Chronei said:
Hmm, I don't think i can execute files with droidexplorer, can you ? Or run it with windows?
Click to expand...
Click to collapse
Run it with windows
Sent from my HTC Desire HD using XDA Premium App
Error 170 - usb not connected. But it shows up in droid explorer and "adb devices" check! Perhaps to use RUU you have to be at least in recovery menu or something .. I feel like this should work, though. Any thoughts?
Chronei said:
Error 170 - usb not connected. But it shows up in droid explorer and "adb devices" check! Perhaps to use RUU you have to be at least in recovery menu or something .. I feel like this should work, though. Any thoughts?
Click to expand...
Click to collapse
Hmm its working with adb?
Sent from my HTC Desire HD using XDA Premium App
XAviierG said:
Hmm its working with adb?
Sent from my HTC Desire HD using XDA Premium App
Click to expand...
Click to collapse
Yes -- works with adb
Chronei said:
Yes -- works with adb
Click to expand...
Click to collapse
Did you try and reboot into recovery or bootloader with it?
Sent from my HTC Desire HD using XDA Premium App
I haven't rooted this phone or ANYTHING. There was an annoying blinking microphone/headset on the phone so HTC said to reset the phone. I did that, and it was stuck in boot loop. It would get to the point where the dots would come down (and finish the screen where it says something about possibilities) and only two dots would come down, it would flash back to the HTC screen, and go back to the dots and so on and so forth. I pulled the batter, and we are back in bootloop.
WTH do I do?????
If you can get into HBOOT again, try a factory reset again. Or try running the ruu.
Sent from my Inspire 4G using Tapatalk
itsnowornever said:
I haven't rooted this phone or ANYTHING. There was an annoying blinking microphone/headset on the phone so HTC said to reset the phone. I did that, and it was stuck in boot loop. It would get to the point where the dots would come down (and finish the screen where it says something about possibilities) and only two dots would come down, it would flash back to the HTC screen, and go back to the dots and so on and so forth. I pulled the batter, and we are back in bootloop.
WTH do I do?????
Click to expand...
Click to collapse
If all else fails, you should have a 1-year warranty on the phone through HTC. I'd get them back on the phone and get a warranty replacement, especially since you're stock. If you opted for the insurance through AT&T, it should be covered through them, but you may have to pay a deductible for the replacement. Like gmurphy said, I'd give the factory reset option a go and see if that works.
Thanks guys. I went to att, and thank goodness i am close enough to a warranty replacement location, and i got a new one! Thank you all so much. It was beyond help!
Sent from my Desire HD using Tapatalk
At least the blinking icon is gone now too LOL
Sent from my Desire HD using Tapatalk
Hi there,
I have a Rogers Galaxy SGH-i727R. About three weeks ago, the phone started re-starting on it's own. I though maybe it was a sticky power key and had that replaced. The problem persisted. I then noticed that it was primarily upon receiving text messages that the phone would reboot. So it seemed it was a software issue. I am running the stable build of CM9.
Yesterday the phone rebooted and never got off the angry alien screen. I pulled the battery, charged it etc and still could not get it to fully boot up. I left it for over an hour. I finally decided to call it quits and re-flash the phone. Problem is, it will not boot into recovery at all. When I hold down Vol + - and Power, it jsut goes into a loop of vibrating every three seconds until I let go and then it tries a normal boot again. Once, I briefly got a screen saying I was trying to install custom software and to press volume up to do so, but before I could hit volume up, the phone cycled off.
I should also mention that the four buttons on the bottom of the screen do not work. I accidentally sliced the wires on the side of the phone when opening it up. I use a software button saver widget to access their functions. I wonder if that issue is related....
Thanks for any advice. I would like to get into recovery so I can load a new ROM or a stock ROM.
You're going to get blasted for posting this here....
That being said, your power button is borked, common on these phones. Happened to mine, but I was still under warranty so it was replaced.
eagercrow said:
You're going to get blasted for posting this here....
That being said, your power button is borked, common on these phones. Happened to mine, but I was still under warranty so it was replaced.
Click to expand...
Click to collapse
He said his was replaced and the issue continued..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Blast away
Sorry. Where should I be posting this? I am happily corrected. I find the titles of the forums confusing, sorry.
btm fdr said:
He said his was replaced and the issue continued..
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
Your point? I can't tell you how many times I've been sent "new" or "tested good" parts and they are DOA when installed. Or people who claim to have replaced or fixed a part but really didn't.
tonyrage.stc said:
Sorry. Where should I be posting this? I am happily corrected. I find the titles of the forums confusing, sorry.
Click to expand...
Click to collapse
In the Q/A section is the proper place. I had the exact same issues you are having, fortunately I had the option to trade it in for a new one. Good luck!
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?