Touchscreen Response Mirrored - Re-flash Kernel?
I've tried posting on some other forums, and I'll include here what I've written there, but I think maybe I just need to re-flash the kernel? Is there anywhere I can download a flashable zip file of the HTC kernel?
Here's the issue:
Last week my phone ran out of battery and it shut down. When I turned it back on the touch response is mirrored on the X axis. So if I touch on the left, it registers touch on the right. Up and down is still the same. But it's not perfect and some areas of the screen don't respond. I was rooted and had a custom recovery, but I did a factory reset in recovery and it didn't help. So I downloaded the stock ROM from VMRoms and it flashed fine, but it didn't fix the issue. So I switched to an old phone (Optimus V for life!) and put the 816 on my desk.
A day later or so the touch screen worked fine. So I ran the system update to Android 5.
Another day passed with it was working perfectly, and then it switched back at a reboot to being mirrored. Then it started working again, but for the last 3 days it's been mirrored...
So what do I do?
Honestly it sounds like some weird hardware problem.
Related
so i'm trying to figure out a friend's evo.
it starts up super slow... takes 5+ minutes to boot and once booted, the touch screen doesn't work
TLDR:
i use voldn+power to power up (not sure what this screen is called. i don't own an HTC android phone) and among the messages there, it reads "Touch Panel-Fail" and when i choose recovery, the phone reboots and i get an exclamation mark in a triangle.
this phone has never been rooted
she said that she went to bed one night and woke up to the evo in this condition.
USB debugging isn't enabled and since i can't use the touch screen, i am unable to enable it to use ADB
any ideas on what i can do to get this thing functional (besides bring it back to sprint)?
thanks so much
i had this happen but i was rooted and wen i flashed a custom recovery it fixed it
Is it rooted? If so, flash one of calculins touch panel drivers.
Sent From My HTC Evo 4G Using Tapatalk On The Now Network From Sprint.
no, this phone has never been rooted. unfortunately, usb debugging is turned off and i can't turn it on to root the phone due to my inability to get past the lock screen
i've successfully gotten one shipped rom to flash via zip (PC36IMG_SuperSonic_S_Sprint_WWE_3.70.651.1_Radio_2 .15.00.11.19_NV_1.90_release_161482_signed.zip) but it didn't resolve the problem.
no other shipped rom zips will flash for some reason
I am running the RENOVATE 4.1.2 ROM (ICS) on my One X with CWMR 5.4.0.8. Had a weird problem today. I accidentally dropped my phone while rushing to pick up a call. When I picked it back up again, its screen was frozen at whatever it was displaying whatever was on it before I dropped it. When I tried to navigate, nothing worked and no buttons were responding.
It eventually self rebooted itself and got stuck at the HTC logo. I tried rebooting it via the bootloader three times and it never progressed beyond the HTC logo screen. Thankfully, the recovery was still accessible and I figured that maybe the boot was corrupted and not the ROM itself. I immediately reflashed the boot.img for the ROM and waited for it to reboot.
VOILA! It did. Rebooted normally and came to the home screen. NO changes. No damages. Its all working fine now.
The reason for creating this thread is to know if this is normal? I mean, dropping the phone SHOULD NOT corrupt the boot! I was on a custom ROM and I knew how to flash the boot.img again so I recovered from the issue quite easily but if its was a stock phone, then what? I dont think users will be able to figure it out.
SO, is this supposed to happen?
RipperNash said:
I am running the RENOVATE 4.1.2 ROM (ICS) on my One X with CWMR 5.4.0.8. Had a weird problem today. I accidentally dropped my phone while rushing to pick up a call. When I picked it back up again, its screen was frozen at whatever it was displaying whatever was on it before I dropped it. When I tried to navigate, nothing worked and no buttons were responding.
It eventually self rebooted itself and got stuck at the HTC logo. I tried rebooting it via the bootloader three times and it never progressed beyond the HTC logo screen. Thankfully, the recovery was still accessible and I figured that maybe the boot was corrupted and not the ROM itself. I immediately reflashed the boot.img for the ROM and waited for it to reboot.
VOILA! It did. Rebooted normally and came to the home screen. NO changes. No damages. Its all working fine now.
The reason for creating this thread is to know if this is normal? I mean, dropping the phone SHOULD NOT corrupt the boot! I was on a custom ROM and I knew how to flash the boot.img again so I recovered from the issue quite easily but if its was a stock phone, then what? I dont think users will be able to figure it out.
SO, is this supposed to happen?
Click to expand...
Click to collapse
don't think so mate. maybe the fall has shaken the electronics and did that...weird indeed.
i dropped my wallet on to my phone the other night it froze and turned off, slightly strange if you ask me.
Sent from my Transformer TF101 using xda app-developers app
No it is not supposed to happen. The only reason I can think of is the impact somehow causing an electrical spike due to some internal contacts short circuiting. Probably some files in the system partition got corrupted. But that is a very unlikely scenario.
[Samsung Galaxy Note II N7100]
((EDIT: Suddenly, after leaving it turned off for about 15 minutes, it works. It just powered up IN THE PACMAN ROM! Still no clue what happened though, Would like to find out for the future))
Hello there,
My device was working fine yesterday, however today I re-rooted after an update. This went well and all was working fine, until I decided to try my first ROM, the PACMan ROM. I flashed with CWM6 (Following a tutorial, using Odin) which seemed to work fine until I actually tried to use it. I went to reboot my phone, and when it started up, it was (graphically) glitching, with the Samsung Galaxy Note II logo twitching around the screen, and a strange set of brown, thick-ish bars moving around the bottom half. Following a few seconds of this, the device shut off.
Following this I discovered that I could get it to stay on and boot-up successfully if I held down the home button (Not sure if relevant), however I still wanted to get down to the bottom of the issue. Following some research, I decided to try and flash a different download of CWM 6 for my phone again. This time it worked, and I went straight to factory reset then install the 'Gapps' and ROM file. There were no unexpected errors in this installation, however when the phone restarted, the same glitch occurred, only without a way past it.
I have since tried patching with the other CWM file that didn't work to see if perhaps I could use my phone again, but this didn't work. Similarly, I've used the working CWM to do a factory reset without installing any ROMs, and the booting still didn't work.
Please help I don't wan't to risk doing further damage, and would be perfectly happy going back to regular jellybean.
Thanks in advance!
Regards,
Thomas
TL;DR My Galaxy Note I N7100's boot is after flashing
Hi,
As I'm tired of waiting for Orange UK to release the 4.2.2 / Sense 5 update for the HTC One X I recently flashed the Maximus HD ROM. Before I flashed this I flashed the latest Clockworkmod recovery (5.8.4.0) and everything seemed OK. However, when I switched my phone off that night and plugged it in to charge it powered itself on at some point in the night. I tried it again the next day, this time at work where I could watch it, and sure enough it powered itself on when charging (not immediately - it came on when it was at about 89%) then when I switched it back off and plugged it back in it powered itself on a few minutes later.
Is this a known bug with Clockworkmod? Does the same thing happen with TWRP? I always switch my phone off at night when I go to bed (please, no replies with "don't switch your phone off" etc.) and this behaviour drove me crazy, so I eventually went back to the stock Orange build - as soon as I removed Clockworkmod from my phone the rebooting issue disappeared.
Any advice / guidance other than "don't switch it off" etc. gratefully received!
Nasalhair said:
Hi,
As I'm tired of waiting for Orange UK to release the 4.2.2 / Sense 5 update for the HTC One X I recently flashed the Maximus HD ROM. Before I flashed this I flashed the latest Clockworkmod recovery (5.8.4.0) and everything seemed OK. However, when I switched my phone off that night and plugged it in to charge it powered itself on at some point in the night. I tried it again the next day, this time at work where I could watch it, and sure enough it powered itself on when charging (not immediately - it came on when it was at about 89%) then when I switched it back off and plugged it back in it powered itself on a few minutes later.
Is this a known bug with Clockworkmod? Does the same thing happen with TWRP? I always switch my phone off at night when I go to bed (please, no replies with "don't switch your phone off" etc.) and this behaviour drove me crazy, so I eventually went back to the stock Orange build - as soon as I removed Clockworkmod from my phone the rebooting issue disappeared.
Any advice / guidance other than "don't switch it off" etc. gratefully received!
Click to expand...
Click to collapse
yes that is a well know problem of the recovery, i think philz touch recovery and twrp solved that.
Mr Hofs said:
yes that is a well know problem of the recovery, i think philz touch recovery and twrp solved that.
Click to expand...
Click to collapse
Good to know. Thanks for taking the time to read and reply.
No problem
Sent from my HTC One X using XDA Premium 4 mobile app
So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
[SOLVED]
strangely enough, I found a solution in a most peculiar way.
I managed to finally get into the phone by charging to 100 percent. Then, I downloaded flashify, and attempted to flash tekxodus rom, as well as selecting dalvik and cache wipe.
The flash did not work. the phone just rebooted. Then, I downloaded rom manager premium, and then rom manager attempted its prerequisite attempt to detect my recovery. (up until that point, I had twrp installed).
The detection lingered, so I pressed the back key and selected reboot into recovery. Surprisingly enough, I was back in Stock recovery.
So apparently the solution to the anomaly I encountered in the OP, is to either follow the simple steps above, or, to flash stock recovery in Odin. If that is at all possible for the user. I can confirm the above worked for me as I tried everything for the last week and this was the only method that worked.
The shutdown/startup logos are back, with no screen flicker or hesitation on sleep/wake.
msmercy42 said:
So i was using Darthstalker v3 and arter97 kernel 9.3 with no issues.
Suddenly one day, i noticed screen flicker when waking the device, followed by hesitation. So my first step was to wipe the dalvik/cache. That apparently did not help.
I then lost my bootup logos, as well as shut down, along with the screen pretty much refusing to come on.
I used smart switch to emergency recover the stock firmware. Nothing. Then i Odined a stock untouched rom. No change. Once i actually got the phone to render the screen in recovery, so i wiped everything three times, and and flashed darthstalker v6. I also rooted the phone again just before that. I
So when the phone is powered off, the battery icon is present, and the screen wakes to that no problem. Since i set the device to never timeout while charging,
when i plug it in, the screen comes on, but as soon as i try to touch it, poof, the rendering of the screen goes. But, while this occurs, i can hear the icons being pressed,
etc. Completely stumped as to what to do. Can someone help?
Click to expand...
Click to collapse
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel
powerful111 said:
yeah i just suddenly started having this problem. my phone would reboot itself and then it would be updating apps as if i just flashed xposed or something, my phone would have issues with wifi, flickering lockscreen, and if you rub the screen while its off which wouldl show you information stream doesnt work either. Decided to dump the rom. Am going with the TEKXodus N5 with arter kernel
Click to expand...
Click to collapse
It's just like I told you. When I read that you had experienced the same precursors that I came across with the rom, I had a hunch you would be soon after posting the exact issues that I eventually ran into.
So when you download Tekxodus and flash, please keep me informed as to if it resolves the issue. As you are aware, stock firmware has not resolved the problem for me, but then again devices vary.
So enjoy the fix if you ever run into the above issue.
Im fine with stock, but I miss the fun of trying new roms.