Hi,
I have CyanogenMod "11.0 Installer XNPQ02R" from January 10th running almost stable.
When I now try to update to the CM11 M3 or to one of the nightlies after the reboot I get in an error loop. A popup comes on that "KeyguardTestActivity has been stopped". After I choosed OK it comes back again. It's not possible to use the phone any more.
What could be the reason and how could I fix that.
Cheers Wolle
Related
Hi there!
After almost 2 days from my holydays trying to install cianogen beta3 in my defy I lost almost all my hopes. Than I made my last call, I tried a version older, and GOTCHA! I have cyanogen working.
So the problem is, if i try installing beta3, all that I get is a black ugly screen after moto logo.
And with a test version before beta3 cyanogem works like a charm.
I already tried with the nordic, korean and uk roms, and tried too patching pays rom 3 and 5.
Also i got some weird error with SuperOneClick2.1 than i used SuperOneClick 1.65
Also, again, i tried to update beta3 from the test with and without wipe, and no luck.
Any sugestions to me to get the beta3 working?
I'm guessing you have, because you got an earlier release working, but are you doing the 2nd INIT boot with the boot menu thingo? cuz thats why i copped a black screen when trying to get it to work
I suppose he already has 2ndinit working considering he has it working before though?
Thanks for the answers. Yeah i needed the second init thing to make the test build work. The only strange thing that i see is a error message that sometimes i got whenever i install beta 3 saying that xbin/su dont exist. when i got this message i try install it again and says that it was completed. But when i install the test build i never get this message.
Search did not give any results i guess. Finally got the nexus up and running again / was on CM10 and had neglected to wipe data when flashing the 4.2.2 factory image. It was pretty weird, I think. The phone had sat on the 'X' screen time after time, minutes not counted.. I had at first vol up/ vol down / power and had gotten a red exclamation for some reason. Eventually got into fastboot, I had used the toolkit by mskip / reflashed the 4.2.2 image , made sure to clear data and all works fine. When flashing a custom rom it sticks on the google unlocked screen. Why? What is the problem? How does this fix itself or going about it to get it fixed? ....... Again, if this is a stupid question and you have easily found the answer by all means pass along the right keyword. If this is not a stupid question, you don't think, and are cool about helping me out, by all means, please do so.
Edit . I had flashed stock then custom rom on another device with only the usual, i guess, load time. The best advice search forums gave me was , just wait'.
http://forum.xda-developers.com/showthread.php?p=38127432
Flashed cm-10.1-20130217-NIGHTLY and got stuck on the "Google" logo on reboot. Booted to recovery and installed the Feb 16 build and all is good. Hopefully the next nightly works well.
From the CM thread.
Hello.
Try to flash the 2013.02.17 nightly AND some 4.2.2 kernel.
I tried with LeanKernel 6.0exp1 and it works
There are reports with working flashed 2013.02.17 with Franco's Kernel latest too.
vfmmeo said:
hello.
Try to flash the 2013.02.17 nightly and some 4.2.2 kernel.
I tried with leankernel 6.0exp1 and it works
there are reports with working flashed 2013.02.17 with franco's kernel latest too.
Click to expand...
Click to collapse
perfect work.
Since the nightly 20131103 everytime I install a new version an error appears before rebooting, about a kernel and NFC crash.
anyone have the same problem? I tried with a clean instalation and nothing.
LG- e975
Cheers!
Hi,
I was previously running Quantum Rom until one of the recent builds (I believe 3.2) was having some issues so I switched to a Cyanogenmod Snapshot. When a newer version of Quantum was released, I went to flash it but I ran into some issues. When the setup wizard appeared, I kept getting spam "Unfortunately phone has stopped" messages that I could not go away. Thinking it was a problem with the rom, I went back to flash the previous version of Cyanogemod that was working fine before. But this time when CM brought up the startup wizard, I was getting the same spam message. All I can do right now is restore previous nandroid backups, but for some reason, every time I try to flash a new rom I get this message. Any ideas?
Thanks!
Did you clear cache, data, and Dalvik before and after installing the ROM? Did you try formatting the system before installing?
Hi! I am running the newest nightly of the LineageOS (14.1-20170220-nightly-bullhead) on my Nexus 5X with the newest twrp 3.0.2-2 and I always get the error "can't connect to camera" when I try to start the camera. It started with the update from the first nightly to the second nightly. After today's installation and no fix I made a clean install, same issue. I tried deleting cash same result. What can that be?