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
Related
Anyone else having this issue? It started within the last day or two on GT-N8013 with stock rooted UEALI3. Even did a factory data reset and same issue. About to try CM10.
mi7chy said:
Anyone else having this issue? It started within the last day or two on GT-N8013 with stock rooted UEALI3. Even did a factory data reset and same issue. About to try CM10.
Click to expand...
Click to collapse
Same problem on my 8010 (unrooted) too.
works fine for me I am not rooted though using orignal rom
Apparently, they have some new code/script on their web site that force closes Android 4.0.4, CM9.1, Gingerbread 2.3.4, etc. stock browser when viewing the full site (not mobile). The only device that doesn't appear to be affected is Nexus 7 JB 4.1.2.
Help report the issue via http://www.theverge.com/contact-the-verge if you're experiencing this issue.
You wonder ?
They are Crapple-agents, not worth reading them, just Crapple-sh..
Still works fine on my tablet even with desktop view please see the attached screenshot
{
"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"
}
Seems to be resolved today. I can consistently bring up the full site without issue.
mi7chy said:
Seems to be resolved today. I can consistently bring up the full site without issue.
Click to expand...
Click to collapse
That's too bad...
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.
Ok so I'm getting this spam of errors for the sensors. While the spam active my sensors do not work, first thing to notice is the auto rotate. Then I used GPS Status and Androsensor apps and they both do not get a reading from the sensors. Now I've searched almost all of the interwebz but I can't find anything related or somebody who has found or understood this Logcat. This happens with stock kernels and custom kernels, stock ROM and custom ROMs. On some customs kernels, once I flash them it never even starts working.
If somebody has the knowledge here to interpret the Logcat and help me pinpoint the issue that would be much appreciated.
Logcat: http://pastebin.com/kGpJj155
{
"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"
}
Any ideas?
neriamarillo said:
Any ideas?
Click to expand...
Click to collapse
How to reproduce?
Aerowinder said:
How to reproduce?
Click to expand...
Click to collapse
I honestly have no idea. I toggle the autorotation on and off but it does nothing. If I entered in the terminal emulator:
su
stop sensors (it stops spamming)
start sensors (it starts back up)
OK so I have an update to this. Flashed back to stock 4.4 and everything works fine even with custom kernels that never worked before. However if I update to 4.4.2 (stock or any custom ROM except CM or CM based ones) it breaks and stops working. On CM and CM based ones it works but without the custom kernels since I use Franco kernel and it is not compatible.
Anyone have an idea as to what could be the cause for this to happen? What is in 4.4.2 that is breaking the auto rotate and the rest of the sensors.
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
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.