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.
Related
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
Hello,
I have flashed twrp-2.8.6.0-xt1032.img from trwp site as recovery and have flickering line going from top to bottom on the screen. Somebody knows how to fix this? my Bootloader is version 41.18 and Im currently on stock Lollipop 5.02 . I wanted to backup my phone first, before starting with custom roms. But now I dont know ,if this affects backing up my system , and then when I need to recover some day.
Thx
Skastream
I'm pretty sure this is a known issue with the Lollipop 5.1 bootloader we have...
I have the same issue, but don't see any effect on my system.
Ok I solved the problem myself by doing this:
Downloading old twrp-2.8.6.0.-falcon_STOCK_NOTHEME.img - 9.2 Mo from here:
http://forum.xda-developers.com/moto-g/development/recovery-twrp-2-8-2-0-touch-recovery-t2980621
and flashing it again with fastboot in windows cmd!
the flickering is gone
Hello there,
Is there anyone who can help me getting back to KitKat 4.4?
I have bought a Note Pro and the previous owner cleaned it and updated it to Lollipop.
The troubles I experience are:
flickering screen,
unwanted reboots and
the message: cpu overheated.
[solved this a bit by limiting background services and it is al lot less but I do not like it].
So I would like to go back to KitKat as I understood on this forum this OS is rockstable.
I flashed original firmware P900XXUANK2 [PHN version] with Odin to my Pro, well it starts up but freezes with
"Samsung" in the screen, and that is it. [Did this several times]
When I flash it back to Lollipop it works, but still having prementioned problems.
Is there anyone who would like to help me, I am a newby and searched on XDA but am stuck.
Would appreciate any help.
Greetings
Aedriaen
The Netherlands
I have a note pro p905
I flashed between lollipop and KitKat and never had similar problem
maybe it is your bootloader that is locked to lollipop and it prevents you from flashing KitKat
maybe you need to flash the KitKat factory firmware which is 4 files with pit file
if someone can confirm this I will put the link to a factory firmware
This sounds like the battery connector issue to me, it may not be software.
http://forum.xda-developers.com/showthread.php?t=2835337
Sent from my SM-P900 using Tapatalk
Aedriaen said:
Hello there,
I have bought a Note Pro and the previous owner cleaned it and updated it to Lollipop.
The troubles I experience are:
flickering screen,
unwanted reboots and
the message: cpu overheated.
[solved this a bit by limiting background services and it is al lot less but I do not like it].
So I would like to go back to KitKat as I understood on this forum this OS is rockstable.
I flashed original firmware P900XXUANK2 [PHN version] with Odin to my Pro, well it starts up but freezes with
"Samsung" in the screen, and that is it. [Did this several times]
Click to expand...
Click to collapse
You should read the threat " Flickering Screen "
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Lollipop or Kitkat, either cannot solve hardware problem: cracked battery connector. This connector should be re soldered, software cannot fix it.
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
Again, either system can not fix this problem of cracked battery connector.
muzzy996 said:
This sounds like the battery connector issue to me, it may not be software.
http://forum.xda-developers.com/showthread.php?t=2835337
Sent from my SM-P900 using Tapatalk
Click to expand...
Click to collapse
Hello Muzzy996,
thanks for the reply, battery connector seems to be OK since I am able to transfer data between de pro and my pc.
Also Odin gives me a green light when I connect the pro to the pc. Loading the battery is not a problem either. So it seems to me the connector don't seems to be the problem.
Anyway, thanks for your help.
Appreciate it!
Beut said:
You should read the threat " Flickering Screen "
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Lollipop or Kitkat, either cannot solve hardware problem: cracked battery connector. This connector should be re soldered, software cannot fix it.
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
Again, either system can not fix this problem of cracked battery connector.
Click to expand...
Click to collapse
Hello Beut, thanks for the reply.
Connectors seems to be ok, loading the battery works fine, transfering data to my pc and vice versa works fine.
Odin gives a "green" light when flashing so I don't think this is the problem.
Tried it again with the latest Odin and flashing works fine, but the problem remains.
Flickering occurs only when the connector is not conneted to the device.
Appreciate your help.
Teflanzy said:
I have a note pro p905
I flashed between lollipop and KitKat and never had similar problem
maybe it is your bootloader that is locked to lollipop and it prevents you from flashing KitKat
maybe you need to flash the KitKat factory firmware which is 4 files with pit file
if someone can confirm this I will put the link to a factory firmware
Click to expand...
Click to collapse
Hello Teflanzy,
Thanks for the reply. I searched the internet for hours but am only able to find 1 file containing the Samsung
Galaxy Pro 12.2 Kitkat 4.4 firmware.
If someone has another or a site where to fetch it, I would appreciate it.
Appreciate your help.
Aedriaen said:
Hello Beut, thanks for the reply.
Connectors seems to be ok, loading the battery works fine, transfering data to my pc and vice versa works fine.
Odin gives a "green" light when flashing so I don't think this is the problem.
Tried it again with the latest Odin and flashing works fine, but the problem remains.
Flickering occurs only when the connector is not conneted to the device.
Appreciate your help.
Click to expand...
Click to collapse
I think you confuse between battery connector and USB connector. When using Odin, you are only working with USB connector.
Flickering when not connected to a charger, the problem is from your cracked battery connector which can only see under microscope.
Trust me, the only fix is resoldering your battery connector. Kitkat or Lollipop has nothing to do with flickering screen.
Beut said:
You should read the threat " Flickering Screen "
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Lollipop or Kitkat, either cannot solve hardware problem: cracked battery connector. This connector should be re soldered, software cannot fix it.
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
Again, either system can not fix this problem of cracked battery connector.
Click to expand...
Click to collapse
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
I think this is the problem, any idea where I can get the Kitkat bootloader for the Pro. Searched but didnot find it.
When I have this file [excuse me for being a newby] can I flash this with Odin using the BT option?
Greetings
Aedriaen
Aedriaen said:
From Lollipop to Kitkat, you need a bootloader for Kitkat as it's not the same as bootloader of Lollipop, that's reason it hang up at boot.
I think this is the problem, any idea where I can get the Kitkat bootloader for the Pro. Searched but didnot find it.
When I have this file [excuse me for being a newby] can I flash this with Odin using the BT option?
Greetings
Aedriaen
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/
I don't know which model you have SM-P900 or SM-P905/907. Search for firmware from that site, Cellular South is for US region.
Depending which one you want, Kitkat and Lollipop have different bootloader.
what is your model ? What firmware are you going to flash ?
This is Bootloader for Kitkat Note Pro
http://www.mediafire.com/download/6862sfh6d8bjas7/BL_Kitkat_Note_Pro.rar
In Odin, you should load BL ( bootloader ) and AP ( rom file ), after it's done, you should boot normally to the start screen.
Beut said:
I think you confuse between battery connector and USB connector. When using Odin, you are only working with USB connector.
Flickering when not connected to a charger, the problem is from your cracked battery connector which can only see under microscope.
Trust me, the only fix is resoldering your battery connector. Kitkat or Lollipop has nothing to do with flickering screen.
Click to expand...
Click to collapse
Hello Beut,
I found out that when the battery is above 40% the problem does not occur. Only beneath 40% the flickering
starts???
Greetz
Aedriaen
Aedriaen said:
Hello Beut,
I found out that when the battery is above 40% the problem does not occur. Only beneath 40% the flickering
starts???
Greetz
Aedriaen
Click to expand...
Click to collapse
Must either be the internal battery connection or the battery itself. Again going to point you back to the flickering thread, specifically post 131 in it. Look at the photos in that post.
http://forum.xda-developers.com/showpost.php?p=63133996&postcount=131
Sent from my SM-P900 using Tapatalk
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.
Hi guys I'm crazy. I replaced the LCD to xt1541 and always go to bootloop. I tried updating the firmware 6.0.1 stock but the touch does not work and if it reboots back into bootloop. I can not even unlock the bootloader because the touch does not work. Please help me
Non-OEM screens are known to cause bootloop in Marshmallow (and maybe later) versions. You'll need an official screen or the older one for the touch to work again.
Lollipop ? is reported to work fine with 3rd party screens. You may consider downgrading, just leave gpt and bootloader commands when flashing the firmware.
Broadcasted from Zeta Reticuli
@Gravemind2015 is correct, the most likely issue is a "cheap" or old display panel... We have seen many times where a non-OEM display panel causes bootloop on Marshmallow, but works fine on Lollipop.
This is why it is often recommended that either you get the device repaired by Moto, repaired by a qualified shop (who guarantees there work), or you use an OEM screen... at the very least don't use one without contacting the seller to verify they guarantee it to work with Marshmallow.
As was mentioned, the only alternative at this point is to downgrade to Lollipop to get the device working, or replace the screen with one that is compatible with Marshmallow.
I know it doesn't make much sense that hardware would cause this specific behavior, but it has been tested and proven multiple times.
Update!!!
I put old broken screen. It is turned on !!!. I have enabled oem. Unlock bootloader. Root permissions. Flash lineage 14.1 and gapps. Put lcd hack again. And voilà. All perfect!!!
jackk11111 said:
Update!!!
I put old broken screen. It is turned on !!!. I have enabled oem. Unlock bootloader. Root permissions. Flash lineage 14.1 and gapps. Put lcd hack again. And voilà. All perfect!!!
Click to expand...
Click to collapse
Nice! It seems our builds of LOS has a patch that uses the Lollipop touchscreen firmware, which also fixes the ghost touch issue, as do many other custom ROMs. If you ever go back to stock you will likely have issues though.
jackk11111 said:
Update!!!
I put old broken screen. It is turned on !!!. I have enabled oem. Unlock bootloader. Root permissions. Flash lineage 14.1 and gapps. Put lcd hack again. And voilà. All perfect!!!
Click to expand...
Click to collapse
Thanks for confirming!
Broadcasted from Zeta Reticuli
I'm posting just to further confirm NON-OEM Screen replacement caused boot loop on XT1543. This replacement screen looks so bad too, its like they are lower resolution but screenshots still come as 1280x720, odd. Anyway, went back to Stock Lollipop. Cheers.