Hello,
I´m from Chile, and I´m really struggling with a serious problem. I got the XT1225, rooted and with SU, and I was with the stock firmware, but, with no reason, the screen stopped working. I was able to load and power the cell, but then, sometimes when the screen was locked, it won´t turn on. If I press the volumes buttons, it make a sound, but the screen doesn´t work. After a reboot, it works fine for a few minutes, but then, the same problem.
I thought that I messed some files, so I did a full wipe/factory reset, wipe system, and then installed the last Resurrection Remix ROM, but the problem persist. I can´t use it, I heard the sound from email or messages, but the screen just won´t turn on.
Please help!
Because this happened to me in differents roms, I don´t think this could be a software issue.
PS: Sorry for my English, I´m an spanish speaker.
Any help?
Based on what you've said, I'd agree that it doesn't seem like software, as long as you aren't flashing something similar with each ROM, like your favorite custom kernel or a specific mod. If you are consistently flashing something like that, stop and just flash the ROM. I doubt different gapps would do anything, since you had this issue on the stock build. You can try to revert back to complete stock, but I don't know if that will help. Still, its probably worth doing. Most likely, you have bad hardware, and that phone has to go out for repair (Unless you wanna try it yourself).
The Horak said:
Based on what you've said, I'd agree that it doesn't seem like software, as long as you aren't flashing something similar with each ROM, like your favorite custom kernel or a specific mod. If you are consistently flashing something like that, stop and just flash the ROM. I doubt different gapps would do anything, since you had this issue on the stock build. You can try to revert back to complete stock, but I don't know if that will help. Still, its probably worth doing. Most likely, you have bad hardware, and that phone has to go out for repair (Unless you wanna try it yourself).
Click to expand...
Click to collapse
Ok, thanks for the reply. Thats what I thought, a problem in the hardware. Now I need to look up for a good tech service, because here in my city, it´s difficult to find one.
I am having the same problem the with mine at the moment. Did you ever get yours fixed or find out what happened to it? I'm using a droid turbo from the US. But same exact problem i can flash another rom and it will work but i cannot let the screen go to sleep or else it happens
Related
The symptoms: SOMETIMES during incoming phonecalls Raphael rings (plays sound) but when I pick up the call, suddenly the phone sort of "mutes itself". I can't hear the person talking, nor can they hear me, even if I hang up and try later. The only thing that helps is a soft reset.
It's difficult to count the occurence, but I'd say like once a day at least.
I have already tried Hard reset, the phone is acting funny with only Advanced Config 3.1 and PHM RegEdit installed and a few tweaks applied (just Boost TFL3D performance tweaks and SMS conversation disabled)
I'm running stock 1.90.401.1 WWE FW, I have flashed a new radio version (1.02.25.31 Cingular) though.
Any advice/suggestion is appreciated.
Unless the new radio is giving you 3G, I'd go back to the stock ROM/radio combination and see if that works. I'm currently using the Cingular ROM/radio as well and I've never run into these problems, but that may be due to different hardware.
Thank you very much for a quick reply.
I'll try flashing the stock radio and will report back...
So, I flashed the original radio and it seemed for a while that the problem was gone.
Sadly, I must report that the problem is persistant as I had to restart my phone right now. When the "sound mute" thing happens I don't hear anything while answering phone calls (even though the phone rings normally!) and also when I try calling any number from my contacts including the operator hotline.
I really don't want to return the phone because I like it very much but having a phone which has problems with phone calls is kind of silly.
I'm at my wit's end.
Will anyone help me please?
I have a small update - today I was so desperate, that I tried flashing a custom ROM (namely DCS-TouchPro-v1.0 Hybrid) and the phone went bonkers right at the first incoming call. However, something IS different - now the phone is not silent but starts "buzzing" - making a long uninterruptible sound that lasts until reset.
Do you think I could have a HW problem?
I HAVE EXACTLY THE SAME PROBLEM!!!
I already posted a message in the "Issues" post of the Raphael Forum, but apparently no one had the same issue so far.
I did many hard resets (and installing gradually less things), it still bugs.
Currently the only tweak installed is the scorpion one to have 4 rows of icons in a menu.
My Raphael is behaving like this since 1 week. The bug occurs once or twice a day as well.
Anybody with some good IT experience has got an idea of what could be wrong with it?
Do you think it is more software related or hardware related?
Today it also crashed badly (grey doted screen and noway to make it work again by turning off. Had to soft reset).
PLEASE DO HELP US, because I'm using the phone for professional reasons and I'll really have to send it back if it keeps on bugging this badely!!!
I just sent a message to HTC Support.
Let's see what they say.
I'll post their response so those who have the same problem will know what to do.
Oh boy, I must say I'm glad not to be the only one with this problem, even though I never wish bad things to anyone.
While googling the problem, I found a few Diamond users with exactly the same symptoms, however most of them solved this by exchanging the device for a new one, so this won't help us much...
Me too, I was wondering if it was because I did something wrong with the phone...
But if I'm not the only it means that there is a problem with the phone itself.
Anyway I'll wait for the official answer from HTC...
I'll post their answer as soon as I receive it.
I'm actually quite curious what their answer will be.
But I wouldn't hold my breath for any miracle, so I'm preparing to send my phone to the service center to have them look at it...
Well.. that makes 3 of us then
at first i thought my symptoms are different, but Flippy confirmed they're identical.
http://forum.xda-developers.com/showthread.php?p=2611523#post2611523
I have to correct myself - I wrote that when the thing happens, the phone still rings, which is not true. It rings just the first time before the problem occurs, but then it's dead silent.
So it seems our symptoms really are exactly the same.
Told ya AntiProxy!
So we are indeed only 3. It is still ok, it means that there is only a very small proportion of of Touch Pro that have this problem.
Now let's only wait HTC's answer...
spoke to HTC support today.
not that i expected them to figure it out or have a solution at hand, but i figured what the heck.. give it a shot.
their solution?
hard reset.. the guy would swear by his daughter that a hard reset will solve it.
i just thanked him and hung up.. *sigh*
don't you just hate it when techsupport's solution to everything is a reboot or reformat.. when you know that's not the solution anyway!
Well, I tried already doing the "Clear Storage" through the settings -> system panel, but it still has got the same problem.
I'll give them a call aswell to see if by any chance I can get on the phone 1 person who will be able to provide us a better technical advice
Hard reset won't help, I've already done it like dozen times and it makes no difference...
I tried flashing the phone to the stock 1.90.405.1 ROM and so far (a day and half) I have NOT encountered the problem. It is too early to start hoping, but I wanted to let you know - if you don't mind flashing your phone, give it a try.
Zillator, can you keep us posted for like 1 week?
If in 1 week the phone doesn't present again that problem I'll flash it as well (I didn't want to flash it because I wasn't sure if it could void the warranty). If during 1 week you don't have the problem again it'll mean that out initial ROM was defective...
Thank you Zillator and please let us know. (by the way when I'll call them tomorrow I'll ask them if flashing the ROM to a newer stock version voids the warranty).
Zillator said:
I tried flashing the phone to the stock 1.90.405.1 ROM and so far (a day and half) I have NOT encountered the problem.
Click to expand...
Click to collapse
only thing is.. my phone is still running the stock ROM as it is!
AntiProxy said:
only thing is.. my phone is still running the stock ROM as it is!
Click to expand...
Click to collapse
AntiProxy, it might be a bug in the ROM we have in our machines. That's why maybe flash it could be the solution. Nevertheless I'll ask about the warranty tomorrow when I call them and let's see how it goes to Zillator.
If his phone doesn't bug for 1 week, there might be a big probability that the problem came indeed from our ROMs.
Guys, don't worry, I WILL keep you updated. I know how much the problem bothers me, so if there's anything I can do to help you, I will definitely do it.
In the end, that's why we are here - to help each other...
AntiProxy: is your stock ROM 1.90.405.1 WWE? Because mine was different (1.90.401.1 WWE) and I had the problem. Maybe Flippy_TK is right and the problem only exists in the 401 ROM.
I'll continue testing and we'll see...
Hey guys,
I tried looking for this issue but I can't seem to find it, I doubt I'm not the only one (I hope I'm not the only one...)
I've been flashing roms for a while now, fiddling with different settings/kernels/etc. and then all of a sudden I'm having issues with my Softkeys. I'll be using the phone and then they just go blank. What also happens is that the Search key gets held down (by a ghost, it seems) and it opens up the voice search option. I've also seen my Back button flicker as if it's being pressed repeatedly.
Right now I'm on CodeName Android 1.4 but I've tried 1.6, CM9 and it seems to be the same issue. I'm assuming that since this is consistant accross all ROMs that it's a hardware issue (I could be wrong) but I'm wondering if this has happened before and if there's a way to fix it.
Thanks gents
Hi friend,
The same happened to me once. It was very weird. I panicked, and locked the phone. Then when I unlocked it everything was as before. It must be some kind of a glitch, coming from CM9 built roms (almost all roms that are around). Try doing a totally clean install with a popular rom and see how it goes.
Now I remember that the same happened once again, when I got a drop of water on my screen, as the touchscreen seems to detect water as a form of touching and then all sort of weird things happened. Hope its a rom issue, not a Touchscreen failure.
Thanks man,
I'm really hoping it's not a hardware issue either as I'm not sure what the process is in terms of sending my phone in for repairs.
I'll try a clean wipe and install tonight and see how it goes.
Thanks again
Update: Alright so I ended up calling Samsung because I had come to the conclusion that it was a hardware issue because every ROM I flashed I had the same damn issue.
I got the ok to send in my phone and all that, I went to return my phone to Stock and when I installed the OEM operating system everything was okay... I seriously doubt that every ROM I downloaded was bugged.
I'm thinking it's just a general glitch or is it possible that 1 ROM I downloaded was bugged and everyone after that inherited the same problem? I don't know...
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
newr said:
I have s-off, rooted, was using insertcoin...Just thought I'd install the Revolution ROM. Did the wipe and then installed ROM. EVerything seem to be fine and it rebooted. Then I reinstalled apps through titanium backup.
When I was using the phone to call...after a minute or so...it started to make this long tone sound and everything freezes. It seem to reboot...and back to working again. I thought it was due to some apps still being reinstalled?
In any case, when I made call again...again after a minute or so..it started making that same tone....and it turned off.
Now, it won't respond at all. I tried pulling out battery...no matter what I do...the phone will not turn on.
please help! Is this bricked? I pretty much followed all the steps. I selected stock kernel instead of custom when prompted.
Click to expand...
Click to collapse
Try to boot with adb.
Sent from my HTC Sensation Z710e using xda premium
Hi...I am trying to install the new SDK package...but I do have the older ADB and when I tried it..it first says ADB sever out of date...then started daemon...and attached list showed nothing?
When I plug the phone in...there's no response from the PC..it won't beep or show anything connected on USB!
I just tried to run adb after installing the latest sdk package. Running adb from the platform-tool directory...the device listed is empty....doesn't seem to be recognizing the phone!
Any other ideas? Is this completely bricked?
I wouldn't call it a brick per se, but this has happened to more Sensations than you may realize. Most people who've reported said they went to bed (phone on or off the charger) and when they wake up, it just won't turn on.
Honestly, I believe it's a random catastrophic hardware issue. I think some Sensations are faulty and have a lower temperature threshold or something, not sure, but what you described seems hardware related.
Edit: Just reread about that tone. A long tone? Although you were on a phone call so it's no guarantee, something like a long speaker tone or a screen spazzing out (I work in electronics) tend to mean something hardware related. Again, not 100% solid, but that's how it usually turns out.
Also, don't believe this happened because you flashed a different rom or something, there is just no way flashing a rom would kill a phone. If that were true, normal software updates or factory resetting could cause the same thing, and they simply don't.
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
newr said:
Yes..it could be hardware related? The thing is, if it's bricked...I would think this wouldn't boot into the new ROM at all.. mine booted to the new ROM and I was able to restore all the apps...but all of a sudden while on the phone...I heard this long tone from the phone....then it just turned off.
The problem is, since this is rooted...doesn't it void waranty? Also, I am in Canada using a t-mobile phone I bought from the States...so I can't really bring it back to fix?
Wonder if I could get HTC to fix it?
It basically just died...battery was 100% when I was updating.
Any suggestion of what I should do?
Click to expand...
Click to collapse
take off the battery, SD card, SIM card and then put them back again.....try to press power+volume down (even power+volume up & down, all buttons) to see if you can log into the recovery...I don't know if this works but since your phone is almost dead, you won't lose anything to try any method...Do you think so?
If anything you have tried does not enable the phone to work normally again, please try to turn to some body who can check and repair the hardware of your phone for help...It could take a long time to send it back to HTC.....
Hope everything is going well with you.
Nothing works..I've tried taking out Battery..talked with HTC and they tried that with me too...but basically the phone is completely unresponsive. I am just wondering if it's a problem with the ROM or if it's a hardware thing. It seems strange it booted up ok and then had this long beep/tone thing.
There seem to be one other person posted in Q&A experiencing exactly the same thing...he was using revolution 6.6.3 and also had that sound and now it won't turn on!
I have talked to HTC and got a repair ticket...not sure if anyone locally can fix it...just wonder if HTC will have problems with it being rooted and all.
He was running ARHD 6.6.3?! I just downloaded it, now I'm weary to flash O.O
@newr
can you try one thing?
Remove battery ,sdcard, then connect the phone to power outlet using usb then try to power on the phone.?
If it doesn't turn on then remove the back shell too and try to power it on again?
sent from my blazing fast pyramid through sonic waves
Thanks for the suggestion. But again nothing happened. I've tried taking out SD, SIM, battery...with or without cover. Nothing turns the phone on...also no light when charging. It's like the phone is just dead?
There's one other post by someone on the forum that says his phone doesn't turn on..and it seem to happen the exact same way. He said he was running 6.6.3 and then all of a sudden a long beep/tone...then stuck..so turned it off and won't turn on again. Haven't seen any update / resolution there neither!
I am still not sure if it's a ROM problem or if it's a hardware problem. The thing is, the ROM did get installed and was rebooted...in fact, I used Titanium to reinstalled all the apps...unless restoring some data for things like bluetooth settings, desktop etc..causes it...which was fine when I restored it for InsertCoin...I don't understand how a ROM could cause a phone not to turn on at all?
I guess unless there are other ways to fix this..looks like it's sending back to HTC...hopefully they can't fix it neither and just send a different phone since if they turn it on and notice I have it rooted and S-On..they might just blame it on that!
Hi, been a member for a while, haven't posted before though, (yeah I know, I'm an ass who just downloads and flashes roms), but I have a MAJOR issue now. I tried the MoDaCo.one rom from http://forum.xda-developers.com/showthread.php?t=1711783 and decided that it wasn't for me, so I restored my old backup of CleanRom 4.2 Standard. However, upon restoring this image, my phone keeps looking for a LTE connection, even though there is none available, and as such, will not connect to any mobile network. I have tried doing a total reinstall of CleanRom, i have tried resetting everything, i have tried changing the APN settings, everything I can think of. I even called AT&T to see if something was up with the data in my area, and it is all fine, in fact, while I was on the phone, the LTE turned off, (as LTE cannot run while the voice is connected for some reason or another) and I actually got a connection, so it is something with the phone trying to get LTE all the time. Is there some way I can fix thigs?
Also, after trying the MoDaCo rom, my phone only does a hot reboot/fastboot, unless I use the power button hard reset. Any help anyone might be able to give would be greatly appreciated, I can't really afford another $650 phone lol
P.S. If someone, ANYONE, can give any kind of help, I promise I will be coming in and trying to help anyone I can from now on. I'm a Linux Dev (Mint and SolusOS) so I'm not a complete and utter moreoff in terms of how the OS works.
mclovin926 said:
Hi, been a member for a while, haven't posted before though, (yeah I know, I'm an ass who just downloads and flashes roms), but I have a MAJOR issue now. I tried the MoDaCo.one rom from http://forum.xda-developers.com/showthread.php?t=1711783 and decided that it wasn't for me, so I restored my old backup of CleanRom 4.2 Standard. However, upon restoring this image, my phone keeps looking for a LTE connection, even though there is none available, and as such, will not connect to any mobile network. I have tried doing a total reinstall of CleanRom, i have tried resetting everything, i have tried changing the APN settings, everything I can think of. I even called AT&T to see if something was up with the data in my area, and it is all fine, in fact, while I was on the phone, the LTE turned off, (as LTE cannot run while the voice is connected for some reason or another) and I actually got a connection, so it is something with the phone trying to get LTE all the time. Is there some way I can fix thigs?
Also, after trying the MoDaCo rom, my phone only does a hot reboot/fastboot, unless I use the power button hard reset. Any help anyone might be able to give would be greatly appreciated, I can't really afford another $650 phone lol
P.S. If someone, ANYONE, can give any kind of help, I promise I will be coming in and trying to help anyone I can from now on. I'm a Linux Dev (Mint and SolusOS) so I'm not a complete and utter moreoff in terms of how the OS works.
Click to expand...
Click to collapse
Does Wifi stay on and not search for connection? Meaning does Wifi always stay connected?
Sent from my box of McNuggets.
thanx for the fast reply, wifi work exactly as it should, no issues there, but mobile data is all kinds of messed up. However, just for s#*T's and giggles I decided to try and see if maybe I could get miui v4 2.7.20 to work, and for some reason or another, mobile data works in this one. I'm not exactly sure what's going on, and to be honest, I think I'm gonna try a few roms and see if maybe its only default ice type rooms that work, which would prob mean that something in sense is messed up after the MoDaCo rom trial. If Anyone might have an idea of what's going on, I'm all ears.
Well if all else fails run a ruu and start with a clean slate.
Sent from my Nocturnalized Beast
E.Cadro said:
Well if all else fails run a ruu and start with a clean slate.
Sent from my Nocturnalized Beast
Click to expand...
Click to collapse
Yeah, I think i may do that, maybe even relock the bootloader, unroot, and start over from a factory default and see if maybe I can get things repaired, or least working right lol.
Hi guys
Last night I installed the fallout rom on my desire s and it's all done.
I'm facing a problem, that is even when I disable auto-rotate from display settings, it still keeps rotating the phone. (In settings menu, and everywhere else unless I disable auto rotate in some app but most don't even have the auto rotate setting and follow the default settings, which is set to disable but is still on for some reason)
Basically I want to disable auto rotate permanently. I do not ever need it.
Any idea how to do this? There must be a way. This is really a deal breaker for me for this rom and it's the first custom rom i've installed on my phone.
This bug is known about Fallout. There is no fix.
You can try a newer Sense 4 ROM (like Nik Project X)
Googley35 said:
This bug is known about Fallout. There is no fix.
You can try a newer Sense 4 ROM (like Nik Project X)
Click to expand...
Click to collapse
I dont think there will be a fix because it it works!!!!!!!!!
flykthewiz said:
I dont think there will be a fix because it it works!!!!!!!!!
Click to expand...
Click to collapse
Not making a lot of sense there.
I understand ROM loyalty and am convinced that fallout is a great ROM and one which I want to stick with. However, your experience of never having had a certain problem does not mean that you can say it doesn't exist.
g-banjo said:
Not making a lot of sense there.
I understand ROM loyalty and am convinced that fallout is a great ROM and one which I want to stick with. However, your experience of never having had a certain problem does not mean that you can say it doesn't exist.
Click to expand...
Click to collapse
2 ppl are flashing the same rom, but only 1 is experiencing the problem, where do u think the problem lies.
Rom dev are not able to fix the problem if they are not experiencing it.
rain987 said:
2 ppl are flashing the same rom, but only 1 is experiencing the problem, where do u think the problem lies.
Rom dev are not able to fix the problem if they are not experiencing it.
Click to expand...
Click to collapse
You may have a point but it isn't valid in this case as the problem started two months after the installation.
Actually I lean to the feeling that this is not a problem with the ROM but I'm finding it interesting that I have now found several people mentioning this problem associated with this ROM - so I'm now seeking clarification, which is not really helped by apparently automatic denial that a problem exists by people who have no knowledge of it.
g-banjo said:
You may have a point but it isn't valid in this case as the problem started two months after the installation.
Actually I lean to the feeling that this is not a problem with the ROM but I'm finding it interesting that I have now found several people mentioning this problem associated with this ROM - so I'm now seeking clarification, which is not really helped by apparently automatic denial that a problem exists by people who have no knowledge of it.
Click to expand...
Click to collapse
My desire s with stock rom is experiencing some issue, i called htc up, tech told me to do a factory reset, hey that solve the problem, but wait, i dont think that should be the solution, ROLL OUT ANOTHER OTA!!!
Same case here, just do a fresh clean install, with backup apps and data. If after 2 months it happen again, then come back and report. Or you expecting fallout v6, which in my case i dont mind :victory: in xda new roms are always welcome.
The dev or someone with expertise needs to experience the issue for you to have clarification, if non are having u only get assumptions from people who are not knowledgeable enuf.
rain987 said:
My desire s with stock rom is experiencing some issue, i called htc up, tech told me to do a factory reset, hey that solve the problem, but wait, i dont think that should be the solution, ROLL OUT ANOTHER OTA!!!
Same case here, just do a fresh clean install, with backup apps and data. If after 2 months it happen again, then come back and report. Or you expecting fallout v6, which in my case i dont mind :victory: in xda new roms are always welcome.
The dev or someone with expertise needs to experience the issue for you to have clarification, if non are having u only get assumptions from people who are not knowledgeable enuf.
Click to expand...
Click to collapse
So following your advice I did a totally clean install and the problem was still with me - so I figured it was a problem with the phone. Just to be sure I installed a different ROM and the problem was gone. That suggests to me, regretably, that it is problem with this ROM. Why it should happen to some people and not others is a bit of a mystery.
I felt it was both arrogant and ignorant of me to give feedback with a diiferent Rom on my phone, so I decided to flash fallout before making a reply since I had the zip on my pc. Never like going back to older roms, always going for the newer ones.
And result is, rotation works. No issue here. On and it rotates, with the phone still tilted I off and it went back to vertical without me tilting it back.
Sad that this Rom is having issue with your phone.
SentDeDesiredS
rain987 said:
I felt it was both arrogant and ignorant of me to give feedback with a diiferent Rom on my phone, so I decided to flash fallout before making a reply since I had the zip on my pc. Never like going back to older roms, always going for the newer ones.
And result is, rotation works. No issue here. On and it rotates, with the phone still tilted I off and it went back to vertical without me tilting it back.
Sad that this Rom is having issue with your phone.
SentDeDesiredS
Click to expand...
Click to collapse
You're right, it is sad. I was perfectly happy with it otherwise.