MIDDLE part of one plus has become unresponsive after update lollipop ROM . tried many different solutions . none of them worked . please help how to get the touchscreen back again
The lower part of my screen (last inch or so) is often unresponsive so if I type, I'll miss a bunch of spaces.....
theMoiz94 said:
MIDDLE part of one plus has become unresponsive after update lollipop ROM . tried many different solutions . none of them worked . please help how to get the touchscreen back again
Click to expand...
Click to collapse
Test your touchscreen using this app https://play.google.com/store/apps/details?id=com.rn.yamtt
If there are issues with multi touch, only thing I can suggest is to switch to other ROM if you are rooted and bootloader unlocked
I had read that CM has fixed touchscreen issue in their latest CM12.1 nightlies
If you are not rooted, a factory reset may work (hopefully) else call the customer service for RMA if they do it for you so easily
I was facing such issue on CMOS12 and also on all lollipop ROMs so I downgraded to XNPH05Q
Related
I want to use guaranty for my tablet so What should I do to turn my rooted device to official state.
Full story:
Touch screen stopped working and I can work only with pen. I searched web and tried some solutions such as factory reset, but didn't help.
So i think it's a hardware issue and I want to turn it in for repair. But the problem is I've rooted my device with odin(probably with custom Rom) and my binary counters shows 2.
Please guide me how to roll back to official state
P.S. If anyone can help to solve the touch screen issue, I prefer to have my device rooted.
Download and run Triangle |Away from the Play store .
Run TA
Boot to download mode flash stock rom for your phone reboot factory reset.
ardalan_o said:
I want to use guaranty for my tablet so What should I do to turn my rooted device to official state.
Full story:
Touch screen stopped working and I can work only with pen. I searched web and tried some solutions such as factory reset, but didn't help.
So i think it's a hardware issue and I want to turn it in for repair. But the problem is I've rooted my device with odin(probably with custom Rom) and my binary counters shows 2.
Please guide me how to roll back to official state
P.S. If anyone can help to solve the touch screen issue, I prefer to have my device rooted.
Click to expand...
Click to collapse
Post # 2 covers the restore but I have seen many posters with pen issue just like yours and it appears that you could have caused the problem somewhere in your Rooting and or the installation of the custom ROM.
Do a search there are lots of people with the same condition and I believe it is rooting and or user MOD's related.
Good luck.
.
Tanx JJegan, It worked smoothly:victory:.
But still I have the touch screen issue kkretch .
Now I am realy convinced that it is hardware. but thank you for the tip man.
I want to ask if there is any problem (flicker screen, red notification on booting up...) when I install CM11 from stock 5.0.2 on Falcon Moto G XT1032? (follow this official guide on CyanogenMod: http://wiki.cyanogenmod.org/w/Install_CM_for_falcon)
Thank you.
I've done this recently and the only issue I've noticed is the screen flickering problem. The solution is to simply press the power button to lock the screen then unlock it and it should be fixed. You only have to do this once but if you reboot your phone you will have to lock/unlock again on first boot.
Thank you for your answer. Just to be sure, did you follow CM guide? Is there anything important which I should be careful about? (I did the same thing with several phones but still noob)
I just booted into custom recovery (I use Philz) and wiped the different partitions along with /cache and /dalvik. You can follow the guide and use the push method or you can use sideload which I did.
I did that and now i have problems with the mac address (i was using 5.1.1) my shows me a different mac and i don't know how fix it, but if i back to LP the problem is solved.
It's a bootloader issue for sure and general happen because you're bootloader is updated to Lolipop 5.0.2 and now you install kitkat as cm 11 over Lolipop.
In simple words your bootloader is new while the software is old
screen flickering issue can be resolved by downgrade bootloader but "BE EXTREMELY CAUTIOUS" failed to upgrade bootloader make your device permanently dead and downgrading is not recommended....
I will recommend try cm12.1 it's rock solid stable as cm11
I finished installed CM 11, firstly the prob is screen flickering. Then after installing all my apps, the android.com.systemui was crashed over and over and cannot use anymore. I reflashed CM and gapps and reinstalled apps but it happened again. Finally, I had to returned to Lollipop.
Anyway, thank you all for your help
Same thing happened to me unfortunately but I've found this one here and it is working beautifully. Try it and see if it works for you without the constant systemui errors.
Thank you. At the moment i am quite happy with GPE version. It seems that this version GPE 5.1.1 is better than Moto stock one.
Calling owners of A6000+. Need some advice and help.
Recently, I was given a6000+ and I have rooted it and even have CM11 working on it and probably will have only KK on it. Its a nice phone and all except of 2 issues which I am sure that a6000+ users have come across. Since I tried googling these issues and have read on such issues:
1) The lower area of the screen especially the 'period' and 'backspace' keys can freeze momentarily. I have downloaded the Lenovo Mobile Troubleshooting app and the touchscreen diagnostics seems to indicate that its ok. Thought that changing the ROM may help...but it didnt. I have not embarked on flashing LP or MM ROMs. If anyone has flashed LP or MM ROMs and it worked, pls let me know. If ROM change is not a solution, any idea how I can resolve this without sending it back to Lenovo since I have voided the warranty?
2) When using the phone while charging, issue 1 becomes more pronounced.
3) On stock ROM, when plug into the PC, the charging mode doesnt work. Any workaround for stock ROM? On CM11, it works fine.
Would love to hear any tips or solutions.
Thanks!
The capacitive touch button bug is a software issue and was fixed in lp. And I never had USB charging issue on stock kk so I can't say anything about that
Hi everyone.
I recently replaced my shatter LCD and was subsequently trapped in a bootloop. I began to wonder if the LCD I ordered was defective, so I removed the new screen and attached the old one. The device booted up fine (as fine as a devastated LCD screen would permit anyway). I detached the broken screen and reattached the new one and the device seems to be working fine.
I am now worried that shutting down the device will cause it to enter a boot loop again. Would reflashing the stock rom solve this issue? Has Motorola installed a failsafe that would prevent devices from booting up if there is a replacement screen attached to the logic board??
I am having the same issue, did you find a solution?
mike29892 said:
I am having the same issue, did you find a solution?
Click to expand...
Click to collapse
Unfortunately, no. After replacing the screen I've opted to keep the device on. Have you turned your phone off after getting it to work with the new screen?
ElonNoir said:
Unfortunately, no. After replacing the screen I've opted to keep the device on. Have you turned your phone off after getting it to work with the new screen?
Click to expand...
Click to collapse
I restored the phone to 5.1 and it booted up fine. Unfortunately my new screen seems defect, it has phantom touches and is not accurate. Perhaps with 6.0 a screen hardware test was added on bootup and both of our devices are failing it?
mike29892 said:
I restored the phone to 5.1 and it booted up fine. Unfortunately my new screen seems defect, it has phantom touches and is not accurate. Perhaps with 6.0 a screen hardware test was added on bootup and both of our devices are failing it?
Click to expand...
Click to collapse
Were the phantom touches present before restoring to 5.1? I'm running Marshmallow right now and I don't have a phantom touch issue. I've thought about reflashing stock rom and updating back to 6.0 but if a hardware test was indeed added, perhaps Flashing CM will allow the phone to operate free of bugs. Maybe that's just wishful thinking.
ElonNoir said:
Were the phantom touches present before restoring to 5.1? I'm running Marshmallow right now and I don't have a phantom touch issue. I've thought about reflashing stock rom and updating back to 6.0 but if a hardware test was indeed added, perhaps Flashing CM will allow the phone to operate free of bugs. Maybe that's just wishful thinking.
Click to expand...
Click to collapse
I couldn't even get the device to boot before restoring to 5.1. I was on 6.0 broke my screen and then replaced the screen. After turning the phone back on it entered a boot loop. I restored to 5.1 and it was able to boot, but the touch screen was all wonky, and getting phantom touches. I tried to flash 6.0 again and it just put me in the boot loop again.
Same issue here on XT1540. Ordered from the most popular seller on Ebay. I'm wondering running CM might fix it.
Update - unlocked bootloader and flashed CM12 - no issues any more with new LCD. Maybe some sort of hardware check with the stock ROM? Tested the digitizer with the "pointer location" dev tool and it was accurate.
Update 2 - can't seem to boot into TWRP with the new screen and CM12 flashed. Rom boots with no issues and runs with no issues though. Old broken screen boots TWRP no problem. Not sure why this is. Can boot cyanogen recovery but that doesn't seem to flash correctly.
fresh cut vegetables said:
Same issue here on XT1540. Ordered from the most popular seller on Ebay. I'm wondering running CM might fix it.
Update - unlocked bootloader and flashed CM12 - no issues any more with new LCD. Maybe some sort of hardware check with the stock ROM? Tested the digitizer with the "pointer location" dev tool and it was accurate.
Update 2 - can't seem to boot into TWRP with the new screen and CM12 flashed. Rom boots with no issues and runs with no issues though. Old broken screen boots TWRP no problem. Not sure why this is. Can boot cyanogen recovery but that doesn't seem to flash correctly.
Click to expand...
Click to collapse
Sorry for the delayed response. How did you manage to flash a ROM if the device goes into bootloop when turned off or rebooted? This is what is keeping me from doing it flashing CM. I fear the device will reboot during the flashing process and it will be borked and stuck in a bootloop.
ElonNoir said:
Sorry for the delayed response. How did you manage to flash a ROM if the device goes into bootloop when turned off or rebooted? This is what is keeping me from doing it flashing CM. I fear the device will reboot during the flashing process and it will be borked and stuck in a bootloop.
Click to expand...
Click to collapse
It won't reboot until the OS starts loading, as long as you can access TWRP you should be safe to flash a custom ROM... it seems to be a known issue that a non-Moto replacement screen will bootloop the OS with Marshmallow but not Lollipop, unknown if CM13 and ROMs based it (which is all custom MM ROMs) will bootloop or not.
Best solution is replace it with an OEM Moto screen, it won't bootloop, only 3rd party ones do.
Please have a look at my issue now ,From morning my display is flickering ( every 4-5 seconds ) and there are weird lines all over the screen ,I have checked by reverting back to stock ROM but it didn't fix it ,THE ONLY THING IS THAT THE TWRP RECOVERY DOES not have this problem ,instead it works well like it was earlier ,No flickering and no vertical lines ,pls Tell me what's the problem? Is it related to bootloader or kernels or is screen issue , I got my display replaced 1 month ago when the old one got broken . Thanks . I am On AOSP 3.2 ROM right now ,Moto g Xt1557.
[email protected] said:
Please have a look at my issue now ,From morning my display is flickering ( every 4-5 seconds ) and there are weird lines all over the screen ,I have checked by reverting back to stock ROM but it didn't fix it ,THE ONLY THING IS THAT THE TWRP RECOVERY DOES not have this problem ,instead it works well like it was earlier ,No flickering and no vertical lines ,pls Tell me what's the problem? Is it related to bootloader or kernels or is screen issue , I got my display replaced 1 month ago when the old one got broken . Thanks . I am On AOSP 3.2 ROM right now ,Moto g Xt1557.
Click to expand...
Click to collapse
Did you replace your display with a Motorola/Lenovo OEM replacement? It is a common issue -- although not really known why -- that many non-OEM replacement displays for the Moto G 2015 will only function with Android 5.1.1 based Lollipop ROMs. Try reverting to Stock Android 5.1.1 and see if that solves the issue.
MotoJunkie01 said:
Did you replace your display with a Motorola/Lenovo OEM replacement? It is a common issue -- although not really known why -- that many non-OEM replacement displays for the Moto G 2015 will only function with Android 5.1.1 based Lollipop ROMs. Try reverting to Stock Android 5.1.1 and see if that solves the issue.
Click to expand...
Click to collapse
Note: Downgrading firmware is a bad idea.
sud[email protected] said:
Please have a look at my issue now ,From morning my display is flickering ( every 4-5 seconds ) and there are weird lines all over the screen ,I have checked by reverting back to stock ROM but it didn't fix it ,THE ONLY THING IS THAT THE TWRP RECOVERY DOES not have this problem ,instead it works well like it was earlier ,No flickering and no vertical lines ,pls Tell me what's the problem? Is it related to bootloader or kernels or is screen issue , I got my display replaced 1 month ago when the old one got broken . Thanks . I am On AOSP 3.2 ROM right now ,Moto g Xt1557.
Click to expand...
Click to collapse
I think this is a screen related issue . did you replaced it with a genuine one or a high copy ?
HelpMeruth said:
Note: Downgrading firmware is a bad idea.
Click to expand...
Click to collapse
Downgrading firmware is never an issue as long as the bootloader.img and gpt.bin are not downgraded.