Hey,
so as the title says, the touch screen of my KFHD7 doens´t work anymore. Further, the buttons on the side refuse to work either. When plugged in via usb, my pc recognizes the kindle and i am able to view the files on it. The screen also gets bright and i see the function to unlock the kindle, which is infact impossible without touch
But lets start from the beginning:
I installed an app called "droidmote" (a remote between two androids). This app wanted me to install "busybox" as well to function correctly. after installing busybox, the app worked some time and then i rebooted my KFHD. After this reboot, i had some kind of mouse cursor on the screen. the standard touch functions refused to work. instead, i had to move this cursor (a little cirlce, not an arrow) and press the screen. When i used more fingers "multitouch" it also showed several of this cirlcles...it was really weird. After some reboots, things became even worse: If i moved my finger to the left, the circle moved to the top... if i moved my finger to the right, the circle went down...it was really annoying. After giving up, i tried a factory reset.
After booting up again, the KFHD asked me which launcher it should use? How could that be? i thought a factory reset would wipe all the data and of course my root and 3rd party launchers? how ever, i was not able to chose any launcher because the touch screen refuses totally...To make things even worse...during the pain of navigating with this circles an changed directions i think i deactivated the adb feature
So...has anybody an idea of what i could do? Thank you!
SmokeyMcPart said:
Hey,
so as the title says, the touch screen of my KFHD7 doens´t work anymore. Further, the buttons on the side refuse to work either. When plugged in via usb, my pc recognizes the kindle and i am able to view the files on it. The screen also gets bright and i see the function to unlock the kindle, which is infact impossible without touch
But lets start from the beginning:
I installed an app called "droidmote" (a remote between two androids). This app wanted me to install "busybox" as well to function correctly. after installing busybox, the app worked some time and then i rebooted my KFHD. After this reboot, i had some kind of mouse cursor on the screen. the standard touch functions refused to work. instead, i had to move this cursor (a little cirlce, not an arrow) and press the screen. When i used more fingers "multitouch" it also showed several of this cirlcles...it was really weird. After some reboots, things became even worse: If i moved my finger to the left, the circle moved to the top... if i moved my finger to the right, the circle went down...it was really annoying. After giving up, i tried a factory reset.
After booting up again, the KFHD asked me which launcher it should use? How could that be? i thought a factory reset would wipe all the data and of course my root and 3rd party launchers? how ever, i was not able to chose any launcher because the touch screen refuses totally...To make things even worse...during the pain of navigating with this circles an changed directions i think i deactivated the adb feature
So...has anybody an idea of what i could do? Thank you!
Click to expand...
Click to collapse
If the launcher was written into system data, then it would remain. After all, factory reset only reverts back to system data, and if the launcher is there, it will stay there.
I had a problem like that once, and I reset it also. Turned out I was plugged into a charger. Some chargers, due to voltage, will cause the touch screen to behave weirdly. Just unplug, and it will work fine again.
If this is your case, unplug the charger. Otherwise, I've got no clue. You're rooted right? Use the KFHD Sysem Restore tool. http://forum.xda-developers.com/showthread.php?t=1951254
Related
Hello everybody,
I was doing a lot of research on this issue and was using the search function of course, however I was not able to find a fix to the problem I am experiencing.
I have a Samsung at&t captivate with cyanogenmod 10.0 installed.
The problem:
Lately I experienced strange touchscreen problems, where it seemed that my phone did what it wants to do. Opening google maps zooming in and out, opening other apps and it even called a friend one time. All that did not seem to follow any pattern, it was more like someone randomly touched on my screen.
What I tried:
After doing some research, I booted to recovery and deleted the cache and dalvik cache. After I rebootet the phone everything seemed alright, except for when writing a message, some keys "p" and "?" where not working.
So I rebootet to recovery again and did a factory reset, and installed cyanogenmod 10.0 again. Everything seemed alright at the beginning, but when I clicked my way through the welcome process, I noticed that the "p" key does not work again, all the other keys though, especially the ones in the bottom right corner, work just fine.
And here comes the problem: On the next screen "Google & location", I can not press the ">" button to proceed in the bottom right corner!
Do you think it is a hardware problem? What is against this is, that the same spot where the ">" button appears, works fine on the other screen, when I enter my Email adress.
Every kind of help is very much appreciated!! Thank you all in advance!
Best,
Moritz
moritz1 said:
Hello everybody,
I was doing a lot of research on this issue and was using the search function of course, however I was not able to find a fix to the problem I am experiencing.
I have a Samsung at&t captivate with cyanogenmod 10.0 installed.
The problem:
Lately I experienced strange touchscreen problems, where it seemed that my phone did what it wants to do. Opening google maps zooming in and out, opening other apps and it even called a friend one time. All that did not seem to follow any pattern, it was more like someone randomly touched on my screen.
What I tried:
After doing some research, I booted to recovery and deleted the cache and dalvik cache. After I rebootet the phone everything seemed alright, except for when writing a message, some keys "p" and "?" where not working.
So I rebootet to recovery again and did a factory reset, and installed cyanogenmod 10.0 again. Everything seemed alright at the beginning, but when I clicked my way through the welcome process, I noticed that the "p" key does not work again, all the other keys though, especially the ones in the bottom right corner, work just fine.
And here comes the problem: On the next screen "Google & location", I can not press the ">" button to proceed in the bottom right corner!
Do you think it is a hardware problem? What is against this is, that the same spot where the ">" button appears, works fine on the other screen, when I enter my Email adress.
Every kind of help is very much appreciated!! Thank you all in advance!
Best,
Moritz
Click to expand...
Click to collapse
I'm thinking you might have to go back to Stock KK4 and start fresh. If that doesn't work, it's most likely a hardware issue (humidity perhaps). If it comes down to that, take apart the phone and put it in a bag of rice for a couple days. Now if that doesn't fix it, you might have to get a new screen
I'd add bad screen protector to the humidity/hardware list. the key is that it keeps recurring in the same place on the screen. if you rotate the keyboard 90 degrees, does the p key work?
Sent from my SGH-I897
Hello, I have my moto G 2014 for about 2 weeks now (full stock, never even connected it to the PC). A few days ago sometimes when I lock my phone by pressing the power button the touchscreen becomes unresponsive. The side buttons both work but nothing happens as I tap the screen, I can't unlock it or shut down. Then, out of nowhere it starts to work briefly, and I can shutdown only, not unlock.
But this time it rebooted and remained unresponsive, I can input 2 of the pin numbers and then it goes unresponsive... RMA?
Thank you
This dont look like a problem before..... You seem to be the first one with this problem. Have you ever dropped your phone? Or installed something wierd? Can you also tell what you did before when this problem came?
The phone is imaculated, never droped it. The first signs were after I installed Swiftkey, the key to change between numbers and symbols was not responding. Now sometimes the screen is all unresponsive, other times the top bar can be accessed, other times the menu keys don't work. I did a factory reset, after much struggle to get to the Config. menu, rebooted to the same issue.
Mebseven said:
I did a factory reset, after much struggle to get to the Config. menu, rebooted to the same issue.
Click to expand...
Click to collapse
I wouldn't loose to much time, trying to hunt down the problem. Sounds like the digitizer is broken. Unless you use your phone only while connected to the charger. Most chargers will emit a low electrical field that makes it almost impossible to operate the touchscreen. If this is not the case, replace the device.
It's not connected to anything right now, the top bar and 3 menu buttons are working but the rest is dead, can't swipe the screen or select any app, not even the app drawer. I guess it's RMA time.
Yea seems like a good idea, its a great device. I hope your warranty is still working
Hi all, forgive me if this has already been asked in some form.
My girlfriends Verizon Moto X lost battery one day while she was playing a game. After she charged and tried booting again, it just booted to a black screen. It still runs through the full boot animation. Weirdly enough, active display will still show her information (and can be interacted with until unlocked), and holding power will bring up a power menu for shutdown. The camera gesture also works to launch it, but you can't interact with anything at all. Safe mode provides the exact same issues.
She is running the latest 5.1 update and is fully stock. She also does not wish to root or flash a custom recovery.
I have tried to pull the data, which windows recognizes as a media device, but shows empty when clicked on. OSx immediately says that the storage can not be accessed over android file transfer. I plugged it in for ADB but ADB won't seem to find it when its turned on. It is recognized in fastboot though. I also wiped the cache via the stock recovery, but that didn't help.
I believe a factory reset will be the solution to the black screen, but she has a bunch of photos she would really like to save. Is there anyway for me to actually get them off of the phone? If she can get those, I can get it factory reset for her no problem.
Thanks for any advice!
The exact same thing has happened to my girlfriend's phone as well and I'm also looking for a solution to recover the data. Moto X (2014) Pure, 5.1
The device boots. The Motorola boot animation plays all the way through, the screen brightness dims slightly as normal, and then the Amber Alert from the previous night vibrates the phone several times and displays over a fully black background. There are no soft buttons and no status bar. The home screen appears not to have loaded (yet?)
Attempts to click "OK" to close the alert fail.
The phone is hot. It is working hard. Something stuck in a loop?
The power button will bring up the "Power Off" prompt with no issues. The animation plays smoothly and the phone can be powered off as normal. The phone is able to recognize touch input here.
Calling the phone while it's on will play a ringtone. It is receiving calls.
Plugging the phone into a computer will show up as an MTP device. However, there are no contents listed.
Sometimes, the phone will prompt that the "System" process is not responding and will ask to close it. This has no effect.
Booting into Safe Mode has no effect.
Clearing the application cache from recovery mode has no effect.
I have a CSE degree but absolutely no Android experience. Forensics on a NAND dump or something like that isn't out of the question, unless it's not possible. Hope you're able to get some help.
Edit: Some other threads with the same issue:
http://forum.xda-developers.com/mot...-screen-to-recover-data-t3168103#post62117413
http://forum.xda-developers.com/moto-x-2014/help/black-screen-boot-t3161110
https://www.reddit.com/r/MotoX/comments/3cf4gr/51_black_screen_after_turning_on/
https://www.reddit.com/r/MotoX/comments/3aqr95/moto_x_2nd_gen_black_screen_after_update/
https://www.reddit.com/r/MotoX/comments/383ej6/black_screen_on_startup/
I am having the exact same issue. Has anybody had a luck resolving it short of a factory reset?
My phone battery died last night. I plugged my phone in, let it get about 15% charge, then tried to turn it back on. The phone boots like normal, but after the boot animation goes away, the screen is black. Active notifications still seem to work, and I can hold the power button to get the Power Down option. I can boot into the bootloader & access recovery just fine. However, my phone is fully stock (no root, no bootloader unlock, no anything). I can't seem to access ADB when the phone is powered normally (ie, when I'm at this mysterious black screen), but it's possible that USB debugging isn't even enabled.
So far, I've found a bunch people who've said a full factory reset will fix the problem, but I'm looking for another solution, or at least a way to grab my data before I reset. Since my bootloader's still locked, I can't seem to use fastboot boot to boot into TWRP, and I can't find any other way to access my data to copy it off the phone. I've tried wiping the cache using the stock recovery to no avail. Any suggestions?
Update?
Hello,
I am having this issue as well.
Unfortunately I am unable to perform any form of factory reset, the bootloader also just brings me to the black screen and I am unable to use soft keys. The kicker for me is that I cannot connect to my PC with a working USB. I used to have that available and now no device is recognized.
Hi all
My screen light, when my qwerty is slide in, stop working. Idk why, but the touchscreen is not affected. When keyboard is out, it works fine...
is there any solution? is there any way to "force" the light on, even slide in/out my keyboard?
any ideas?
thanks a lot
Dalamar666 said:
Hi all
My screen light, when my qwerty is slide in, stop working. Idk why, but the touchscreen is not affected. When keyboard is out, it works fine...
is there any solution? is there any way to "force" the light on, even slide in/out my keyboard?
any ideas?
thanks a lot
Click to expand...
Click to collapse
Factory reset and/or reflash firmware with rsd lite
If device is not rooted factory reset should work.
Or
There are some apps like lightflow that may help
Sent from my XT907 using Tapatalk
Thanks a lot
Lightflow is for notifications?
I was referring to the backlight.
I think that it's a HW problem, poor connection between the screen and qwerty or something similar. I put a little carton between the keyboard and the screen and the lights on...
Hi again
My screen doesn't work anymore.
I dont know what happened with my phone, i think that in a reboot it entered to safestrap or other option and doesn't boot.
When I press vol keys, my D4 vibrates.
My pc shows 2 disk but I can't see the data (maybe it's unmount?).
I can't see the device via ADB.
PD: Fortunately, previously I made a backup of memory (8 GB) ... but I wanted made a full backup with safestrap D:
Dalamar666 said:
Hi again
My screen doesn't work anymore.
I dont know what happened with my phone, i think that in a reboot it entered to safestrap or other option and doesn't boot.
When I press vol keys, my D4 vibrates.
My pc shows 2 disk but I can't see the data (maybe it's unmount?).
I can't see the device via ADB.
PD: Fortunately, previously I made a backup of memory (8 GB) ... but I wanted made a full backup with safestrap D:
Click to expand...
Click to collapse
Your LCD or flex cable likely failed, fairly common with slide out droids
both can be replaced
you need to unlock you screen to see data on drives
Likely the Digitizer is still working, just need to guess where the unlock is
sd_shadow said:
Your LCD or flex cable likely failed, fairly common with slide out droids
both can be replaced
you need to unlock you screen to see data on drives
Likely the Digitizer is still working, just need to guess where the unlock is
Click to expand...
Click to collapse
Thanks again! superfast answer
Now, my pc shows "mot single adb interface" in device manager. But when i'm listing ADB devices, doesn't show my D4
Without doing anything myself, my Moto X 2014 has almost reset itself whilst I was asleep.
The first warning was no notifications, there's always an email or two, but then it wouldn't let me pull the quick settings down either. The phone wasnt using Smart Lock, in fact most system settings were reset. I figured something might be wrong with xposed (however, it's been running for months with no change, no updates to Android, xposed framework, or modules) so I updated all the modules and rebooted, still nothing. For some reason I went and switched to guest account, then switched back to my account and I'm now able to see notifications I missed and use phone almost normally. But my settings had reset and after setting swiftkey back up I see "Predictions not available. Check SD card." so typing is a pain.
My home button isn't working either, it flashes but doesn't do anything. The back and multitasking buttons work. Holding home button brings up Google Now on Tap, but it doesn't take me to home screen.
What could have happened? Is my storage knackered? Its not near full. Just to be clear, all my apps remained installed and logged in as far as I can tell. Only SwiftKey and the Home buttons remain as a problem.
Edit: Bluetooth devices also reset, wasn't connected to car stereo.
Edit 2: reinstalled swiftkey and predictions came back. Rebooted and they went again! Home button still not working.
Edit 3: Installed CatLog and when I press home it says: Not starting activity because user setup is in progress. So it thinks I'm trying to do first time setup? My accounts are already there (one of the settings that did remain).
Edit4: Ran
Code:
am start -n com.google.android.setupwizard/.SetupWizardTestActivity
as root (use su command) in terminal emulator and managed to complete setup... Home button works now and SwiftKey predictions seem to be working after a few reboots.
I hope that never happens again.