[Q] Red flashing frame on screen - Moto G Q&A, Help & Troubleshooting

Hi,
yesterday I unlocked the bootloader on my Moto G (1st Gen.) and installed CM12 - which worked fine.
Today I've installed Xposed Framework along with several modules, and after a while I've started noticing a red frame randomly (?) flashing on the screen.
I've looked around for a solution, but in my case it is not related to the Strict Mode in Dev Options - they weren't even enabled. I also tried to edit build.prop adding a couple of lines but that didn't help either. (Yes, I rebooted)
Does anybody have the same issue? Could it be due to Xposed? Any ideas?
Thanks.

It must be off.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

thuybang said:
It must be off.
Click to expand...
Click to collapse
It is, all of my Dev Options are off...

Update : I bricked my phone and I had to reinstall CM12.1 and everything else but the problem still occurs. I've got the nightly version, anybody has been experiencing the same issue?

Hypocryptic said:
Update : I bricked my phone and I had to reinstall CM12.1 and everything else but the problem still occurs. I've got the nightly version, anybody has been experiencing the same issue?
Click to expand...
Click to collapse
Why dont you flash stock ROM by cmd over mfastboot ,if it work,then flash CM12.1 later ?

thuybang said:
Why dont you flash stock ROM by cmd over mfastboot ,if it work,then flash CM12.1 later ?
Click to expand...
Click to collapse
I had to do that the other day, nothing changed.

Related

[Q] Scrambled Display

I had My HTC One S working fine with an unlocked bootloader, CWM Recovery, and CyanogenMod 10.2. One day, I get a notice that there's a system update, so I thought, hey that's cool, over the air updates for CyanogenMod. So I do it and now when it boots it looks like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
With some difficulty, I was able to get into the bootloader then into CWM. I cleared everything and re-flashed the original CyanogenMod ROM, but it still does this when it boots. It also does not appear to turn on properly. Does anybody know what's going on here?
polybius said:
I had My HTC One S working fine with an unlocked bootloader, CWM Recovery, and CyanogenMod 10.2. One day, I get a notice that there's a system update, so I thought, hey that's cool, over the air updates for CyanogenMod. So I do it and now when it boots it looks like this:
With some difficulty, I was able to get into the bootloader then into CWM. I cleared everything and re-flashed the original CyanogenMod ROM, but it still does this when it boots. It also does not appear to turn on properly. Does anybody know what's going on here?
Click to expand...
Click to collapse
Your link doesn't work.
I also cannot see any picture of your screen, but I think you mean freaky colours on your screen.
This is due to updated display drivers some time ago on CMs side.
Which means if you use a newer ROM, you also have to use a newer kernel to get the correct colours back.
If you are S-On your kernel won`t be updated by just flashing the firmware, you have to fastboot the kernel afterwards.

[Q] [HELP] Error when checking for OTA update!

Whenever I go to Settings > About Phone > Sytem Updates , instead of checking for OTAs, it just throws up this error message.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Now, I know its not because of a custom kernel, because some guy just received the 4.4.3 OTA on the same kernel.
I have tried rebooting, only to realize that nothing happened
Anyone else facing this issue or knowing how to fix it?
I sometimes receive the same error on a locked bootloader. I think its just server overload issue or something like that from Moto's side.
KDB223 said:
Whenever I go to Settings > About Phone > Sytem Updates , instead of checking for OTAs, it just throws up this error message.
Now, I know its not because of a custom kernel, because some guy just received the 4.4.3 OTA on the same kernel.
I have tried rebooting, only to realize that nothing happened
Anyone else facing this issue or knowing how to fix it?
Click to expand...
Click to collapse
This might help you
https://www.youtube.com/watch?v=gF1KasRo2iY
3RAN7ON said:
This might help you
https://www.youtube.com/watch?v=gF1KasRo2iY
Click to expand...
Click to collapse
Nope. Didn't work.
I also tried the same thing for the "MotorolaOTA" app; no bueno :thumbdown:
-sent from my little moto beast
Alright, its working fine now.
I believe it was something to do with my Motorola ID not being recognized.
I simply set it up again
-sent from my little moto beast

(Solved) Disappeared Wifi 4.4

Hello, I have a problem, I have and always open bootloader and installed without problems cyanogenmod, carbon AOSP, etc ... Yesterday install AOKP and I have no wifi signal, no mac address appears to me, went back to the 4.2 meter by flastool. 2 version .17 and I started the process again, doing the dalvik cache and format system / format.
Probe with thunder and phantom and kernels either.
I never had this before last as long probe many roms.
Someone tell me would know that there is solution for this? Thanks
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
lokura72 said:
Hello, I have a problem, I have and always open bootloader and installed without problems cyanogenmod, carbon AOSP, etc ... Yesterday install AOKP and I have no wifi signal, no mac address appears to me, went back to the 4.2 meter by flastool. 2 version .17 and I started the process again, doing the dalvik cache and format system / format.
Probe with thunder and phantom and kernels either.
I never had this before last as long probe many roms.
Someone tell me would know that there is solution for this? Thanks
View attachment 2824850
Click to expand...
Click to collapse
By saying 17fw,are you sure you're flashing latest one...or maybe you're flashing the older one that is 4.1.2?
faizalotai said:
By saying 17fw,are you sure you're flashing latest one...or maybe you're flashing the older one that is 4.1.2?
Click to expand...
Click to collapse
No,got the .17 4.2.2, and the truth I'm going crazy trying everything
Ok, solved, you were right but was getting the .17 4.1.2

[HELP] E3 D2122 stuck on bootloop

first like to apologize for my English, so .... a while ago I installed the Nitrogen One rom @vinay, worked for a while and started giving problems in applications, appeared "common camera stopped working" all the time. after that the phone simply shut down and "bootloop". my phone is like a while since, I installed practically a rom stock every day, because now every day of the same problem! Can someone help me? is there any solution just to solve the "common camera stopped" problem?
Just flash the stock ftf file everything will be alright mate no worries
vincy009 said:
Just flash the stock ftf file everything will be alright mate no worries
Click to expand...
Click to collapse
but i keep having the problem with the camera common, it dont stop, no matter what i do
marcosviniccius said:
but i keep having the problem with the camera common, it dont stop, no matter what i do
Click to expand...
Click to collapse
Whats the problem the bootloop or camera?
Clear Cache
vincy009 said:
Whats the problem the bootloop or camera?
Click to expand...
Click to collapse
i will try to explain it to you, my phone shows a windows with "camera common has stopped", just like that (
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
) if i press ok nothing happens, after a time my phones turns off and start bootlooping, no matter what i do it keeps happening. i already installed a custom rom but it keeps happening.

Oneplus One random reboot

I have this issue where my OPO randomly reboots.
Sometimes it freezes for 4 seconds then reboots, sometime it just reboots even when screen is off, sometimes it reboots many times in a row (5-6+), sometimes just once a day, sometimes it doesn't reboot for 1 week then the problem comes back.
All I know is that when it happens once, it is likely to happen again immediately/within 1 minute.
I thought it was a battery problem, but replacing the battery did not fix it.
I did a full wipe, reflash LOS15.1, did not help. Full wipe + LOS15.1+franco kernel did not help.
I also had this problem on 7.0,7.1,8.0.
It started like 5 months ago, my phone was fine before then.
I haven't tried new ROM yet but that's not the problem, nobody else on LOS has this problem.
Any thoughts?
I have this problem too. It's happened to me on CyanogenMod, LOS 14.1 and 15.1. While it's not the end of the world, a fix would be appreciated!
Likely has something to do with the internals of the phone.
Also, which modem firmware are you using?
You can see that in Settings -> About phone, just like the Android / LOS version.
headsh0t95 said:
Likely has something to do with the internals of the phone.
Also, which modem firmware are you using?
You can see that in Settings -> About phone, just like the Android / LOS version.
Click to expand...
Click to collapse
Do you mean the build number?
headsh0t95 said:
Likely has something to do with the internals of the phone.
Also, which modem firmware are you using?
You can see that in Settings -> About phone, just like the Android / LOS version.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What's the latest firmware/baseband that will work with LOS 15.1? One of the few things I haven't tried yet.
bump

Categories

Resources