I recently unlocked the bootloader and rooted my xt 1033, but I'm facing a lot of issues after that.
As you can see in the attached screen shot my device is no more compatible with Motorola boot services.
Since Motorola started rolling android 5.1 update but I'm not getting any notification to update my device.
I used the twrp recovery but when I go to the recovery menu the screen starts bouncing with many lines on screen.
Please help me in fixing these issues
I think your issue is with custom recovery.
motorola official update only works on stock recovery.
can you guide me how to revert back to stock recovery please?
hi i have installed 5.0.1 few months ago on moto g 1st gen after rooting. i had unlocked the bootloader. i have been facing problems since then like "emergency calls only" after every 15 mins.i want to revert back to stock android.i am able to perform till rebooting the phone into bootloader and i m not able to perform any steps further. please help me .thanking u in advance.
Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7
electriceccentric said:
Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7
Click to expand...
Click to collapse
Hi.
In my xt1040, i can flash CM 12 lollipop or a stock rom based from kitkat 4.4.4 without problems (I have a updated bootloader), to get OTA updates again, its necessary flash the stock rom (KK or LP), without root, PURE stock (with all "bloatware").
Now im using a optimized rom from:
http://forum.xda-developers.com/moto-g/4g-development/rom-stock-motorola-4g-lollipop-rom-t3142816
No bugs, amazing battery life, and a pure stock, no "bloatware", great ram management.
Sorry for bad english.
electriceccentric said:
Okay, so I recently bought a used Moto G LTE, seller said it would be on Lollipop 5.1. When I received it, it had been rolled back to 4.4.4. Hence the screen ripple at every boot up (which persists until the phone is locked and then unlocked) that almost gave me a heart attack the first time. A little googling later I learn this happens because while you can downgrade android the upgraded version's bootloader remains. So last night I finally got around to rooting since I just can't go from a rooted phone to living with a non rooted one, feels like my phone has a noose around it. Anyway I wanted to know if it's safe to flash CM on my phone now or should I reupgrade to 5.1 first? And if I should is there a way to get it to update OTA again? If not any suggestions where to find the firmware? I just want to feel free to flash roms without bricking my phone. Here is a screenshot of my About Phone, in case someone needs it to help, imgur.com /v8iLOU7
Click to expand...
Click to collapse
You'll have to wipe the system anyway, updating it will be a waste of time...
I bought this phone a week ago. Received a system upgrade notification and I upgraded Nougat from BLN-L22C675B150CUSTC675D001 to BLN-L22C675B340CTSTC675D002. The upgrade process was successful :good:. But sensor is not working to unlock the when screen is off & touch response is also degraded after upgrade activity. Prior to upgrade both functions working without any issues. Can anyone please help me to resolve this issue. Thanks in advance
kvinodsagar said:
I bought this phone a week ago. Received a system upgrade notification and I upgraded Nougat from BLN-L22C675B150CUSTC675D001 to BLN-L22C675B340CTSTC675D002. The upgrade process was successful :good:. But sensor is not working to unlock the when screen is off & touch response is also degraded after upgrade activity. Prior to upgrade both functions working without any issues. Can anyone please help me to resolve this issue. Thanks in advance
Click to expand...
Click to collapse
Did you try factory reset??
But your sensor still work or not? I mean, if you touch it you feel vibrations when the fingerprint is wrong, or not at all?
Hello,
I am a experienced user. I have been lucky to get a J710fn donated to play around because it has a not working touch screen. The person who gave it to me told me that touch stopped working after update to nougat.
I did some research on the internet. There are a lot users of this phone saying they did have the same problem. Downgrading to marshmallow should fix it. Since I updated the phone to the latest firmware it has binary 6.
I don't know if it is a hard- or firmware problem. I tried several stock roms.
If someone can give me a hint if there is a way to find out if it is a hardware problem or other ideas how to solve the problem, I would be grateful.