Bootloader unlocked
s-off
supercid
hboot: 2.18
Have recently been running CM12.1 nightly from April 26th.
Phone has been working fine until today the touchscreen became completely unresponsive while I was using the phone, would not register touch anywhere on the screen. However when in recovery (TWRP-evita-F2FS-2.8.5.0-unofficial) the touchscreen was entirely functional. I did a full wipe and flashed the newest CM12.1 to see if it would fix the issue. Again when in the ROM touch was not working at all, but in recovery it was completely fine. I decided to run the 5.18 RUU.(Filename: HTC_One_X_RUU_5.18.502.1.exe) to see if it would fix the issue. After successfully running the RUU touch no longer works in the ROM or in TWRP recovery.
Seems very odd to me. Is there anything else I can do to try fixing this?
Update: just flashed CWM recovery so i could flash a rom using the hardware buttons, had candykat 4.4.4 on my computer. Rom booted up and the capacitive buttons started flickering all crazy when i pressed one then stopped after a second and touch is now fully working again....odd. Perhaps hardware failure is imminent lol, but for the time being things are working.
edit: spoke too soon, appears touch is still a bit wonky. I can get it to work but it stutters a bit and usually the capacitive button lights will be flickering when touch starts performing poorly. Could this be a loose connection? dying digitizer? Any help is appreciated.
Related
I was flashing a rom the other day (that i had flashed in the past and worked fine) and then i noticed that the touchscreen did not work. (everything else worked)
i flashed back to the cyanogen rom and my touchscreen still did not work.
(when i say my touchscreen doesnt work i mean that i cant touch anything, not even the android to set up my phone)
the trackball works but i am FORCED to touch the android and i cant
ive been flashing and still no luck, any ideas on what happened to my touchscreen or any ideas on how to fix it?
please help!
Greetings all, recently I have rooted and flashed Cyanogenmod 10.1 nightly to my GT-i9300 but a couple of days ago I started to get random reboot loops, the screen waking and sleeping on its own, etc. I tried flashing several other AOSP based roms such as AOKP and Carbon with no success. Today while I was in the car I noticed that if I just extremely lightly touch the power button it will function as it should, however if I press it normally it starts messing up again. I'm not sure if this is a problem with the 3.0 kernel of the roms I've flashed or if it's simply a faulty power button but I would like some enlightenment so I can make my phone usable again, cheers
Hey there.
whats the android version of your rom? 4.2 or 4.1?
i had almost the same problem with my S3 when i flashed a rom with android 4.2
it seems like on the 9300 the hardware isnt able to work properly with 4.2 8if i imagine this info correctly)
after wipe and installing 4.1 everything was fine again.
i hope this may help you
I updated yesterday, everything went smooth even the flashing of the recovery which I see some people are having trouble with.
Only problem: The touch screen doesn't work while I'm in TWRP.
Only way i got it to work:
Enter TWRP
Wait till screen locks
Open screen - Then the touch works (If I manually lock it then wake it up the touch screen still doesn't work).
I've looked around and I don't think its Lollipop related as people encountered this problem before.
Any suggestions?
Thanks in advance to everyone who helps~
Situation is kinda strange.
Yesterday i was bored and i started to flash some roms on my OPO. I started with the latest ColorOS that i found here on XDA, but i didn't like it. So i flashed PA 4.6 beta 6. I noticed that the red boot logo of colorOS remained despite the full wipe of the internal storage. And the fastboot mode started to show some chinese characters instead of the regular ones.
But that's not the problem. Problem is that this morning i wasn't able to turn off a call because the screen turns off every time a call is made and there's no chance to turn it again on. The only thing i could do is to long press the power button and reset the phone. The call starts, the speaker works, the screen turns on and you can't do nothing than this.
I said "ok, it could be the PA rom, it's in beta, y'know"...So i flashed the PA stable and...same problem.
Then i tried the first rom i saw (vanir lollipop, last build) and...same problem? WTF?
Now i'm flashing the original 44s by fastboot and see what happens. In case nothing happens with the fastboot way, i will try to flash it by recovery. But i have a bad feeling about this.
Any similar experiences? I will keep the thread updated for people with the same problem.
EDIT 1: ok, after the fastboot flash of the cm11 44s i'm able to make calls without those problems. It will be amazing if the problem were still there.
EDIT 2: i have to say that the chinese fastboot and the red logo are gone now.
The reason your proximity sensor stopped working was because of the modem you flashed while you flashed ColorOS.
I flashed ColorOS aswell and has the same proximity sensor issue after flashing back a CM11 rom.
mumaster20 said:
The reason your proximity sensor stopped working was because of the modem you flashed while you flashed ColorOS.
I flashed ColorOS aswell and has the same proximity sensor issue after flashing back a CM11 rom.
Click to expand...
Click to collapse
Damn! I knew it!
That terrible ROM messed up all my phone -_-
I really don´t undestand whats happening. While I turn on the phone with charger plugged, it works well. However if a turn on unplugged, touch screen doesnt work.
ROM Installed with CWM 6.0.4.8.
It had the 2.18 Hboot from stock, however I flashed firmware of Cyanogemod site for test.
Thanks.