Q&A for [ROM] Official Cyanogenmod 11 4.4.4 for the Moto G 4G (Peregrine)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer. Thanks for understanding and for helping to keep XDA neat and tidy! :smile:
Notification light not working with cyanogenmod
Hi,
I'm using cyanogenmod (m6 and afterwards the current daily builds) on my moto g and for quite some time I have the problem that my notification light is not working. I tried out installing the motorola led activator widget, but this doesn't help. Even when trying out an LED tester app nothing happens. The LED is not broken though as it lights up when trying to boot my moto g on low battery. Do you have any ideas how to solve this?
Thank you in advance!
Link down
Seems the latest build link is down
not I download the latest build. fallen servers
Does the ROM still have the low ram bug ?
Problem audio speakers CM11 / Stock ROM
How about, first of all, I'm new here and do not speak English, so I excuse my writing.
I have a problem with my Moto G LTE (XT1040) with Stock ROM 4.4.4 KK Brazil, although I am from LatinAmerica.
Well, I have not much to this terminal, but a few days ago I had some problems with the rom Stock, restarting not it caught more, so I decided to flash the latest rom Cyanogenmod (specifically 20,141,012) due to some stability issues decided you go back to the Stock, having the same error when freezing some applications Motorola as usual to, so back to CM and switch to the "20141016" to the few hours I started to fail the camera, remained frozen when taking a photo . After that, it went back to flashing CM rom and had the same errors, updating the "20141018" was the same, but a new bug, and could not hear the music or videos without headphones was added, calls were heard if it was not for speaker, so I decided to go back to the Stock, but apparently the problem was continuing, feel that the speakers are damaged, but the alarms or notification sounds if they worked properly. Now try wipes Cache / Dalvik from CWM but only achieved a temporary solution, put a good song and all, but to change it or put it back the audio is going.
Help me, do not know what else to do, I guess that having unlocked the bootloader and lost my warranty
Thanks in advance if this post is incorrect or I violate any rule, excuse me, I'll delete.
I'm also trying to get GPS to work on my Moto G LTE in cm11:
Based on what I read here, I reflashed stock, and tried it out, had no problems at all. Then restored the cm11 nandroid I had made, and it couldn't see any satellites still. Will restoring the nandroid backup also restore the not-working-gps then? What is being saved by unlocking the gps? Will I have different results from backing up everything with titanium backup, then going back to stock, using gps, reinstalling cm, and restoring the backed up apps? It's much more of a pain to do it that way, but if it works, I'll find the time...
This is a canadian xt1040, btw, in case it makes a difference.
UPDATE: I went ahead and reinstalled stock, played with gps for a while, and it worked without any trouble, then reinstalled CM11 (oct 21 nightly this time) restored my backed up apps with titanium backup (not any system apps). Unfortunately, still no gps at all. It never sees a single satellite. Is there anything else to try?
Hello,
First of all, thank you and all people to contributing and helping developing CM for this device!
I only have one question about GPS bug :
You indicate that it's necessary to have a GPS lock in the stock ROM first to enable GPS in CM.
Does a fix for this bug is intended/possible or the only one solution is to reinstall the stock rom, enable GPS and install CM?
Thanks in advance.
Audio solved
It updated my previous query, I could solve the problem of audio speaker, I began to disassemble the phone and as imagined, I found steel wool at the entrance and were making contact, so the cell believed to have headphones all the time .
Enable GPS in Moto G Nightly
This is in response to jac0708 in the thread this thread who asked:
Mind expanding on these two? What is the low ram bug? And how do you get a lock from stock for the gps fix?
Sorry for noobishness
Click to expand...
Click to collapse
The answer I found for the GPS not working was that when I installed CM11 within hours after taking delivery of my Moto G, the GPS would not get a fix. The solution is explained here by colinw:
Posted 11 October 2014 - 10:42 PM
Okay I just fixed my problem following some other post for a Moto phone.
1) Made a (nandroid) backup using clockwordmod of my current setup (cyanogen 11)
2) Restored old backup of a stock rom (I restored back to the one that came with my phone)
3) Then I had to USE the GPS - hadn't done that yet. Also made sure it was set to Device Only mode in settings->location because someone somewhere suggested it.
4) Restored to cyanogen rom.
5) Working!!
Click to expand...
Click to collapse
Just wanted to add that it doesn't always work. I tried at least three times, restoring stock, using gps, and then restoring my backup before I had gps working in CM. But it does work now! Be patient, and maybe just leave the phone with the stock, sitting on maps for a while. Perhaps I rushed it before?
Q&A for [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM][5.X][XT1028/XT1031] CyanogenMod 12.1 for Moto G [METICULUS]. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
no calls or data
I have an xt1031 flashed to page plus. I have bootloader 41.19 from a failed lollipop update attempt. I flashed the 4/8 build and I can't make calls and do not have 3g. The network shows as 31000. What should I do?
I have been trying each of his builds and anything newer than 4/8 data hasnt worked I'm on boost if that makes any difference
Verizon?
Good morning,
I'm on an XT1028 still with service through Verizon Prepaid; my bootloader is unlocked and I'm on an optimized KK stock ROM at the moment. I've been following the development of Meticulus' CM12.1 through the primary thread and there has been a lot of discussion as to problem solving and issues on the XT1031 and various carriers but little mention as to the status of the latest weekly builds on the XT1028 still on Verizon in terms of functionality or hiccups from users. Does anyone have the latest versions running on their 1028? Are any of the data or service issues present when running it on Verizon?
Thanks.
Followup: Installed the latest 4/25 weekly on my XT1028 on Verizon Prepaid. Installed fine, got phone and SMS, but the network is identified as Boost Mobile and I have no mobile data. Is there a fix? Is a build.prop edit necessary for Verizon? Thanks.
Reboot then bootloop
Hi, I've been trying to get my installation of this ROM working for two days now, but keep running into an issue that I cannot seem to solve
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
The issue has been occurring on build 4/8, 4/25, and 5/2.
The exact steps I have been taking to install this ROM (for all builds) and then what happens:
Bootloader is unlocked
Going into recovery and wiping dalvik cache then factory reset (wipe)
Installing CM11 (latest snapshot) [on my first attempts only, not afterwards since it made no difference anymore]
Factory reset again (just to be certain)
Installing the zip for a build specified above
Installation always succeeds with no errors
Installing gapps-L-3-28-15 with success
Reboot into android
First boot always succeeds (and takes appropriate length of time)
Set up the phone (connect to wifi, google account, restore my apps [18 of them, just common popular ones, mostly Google actually], and apply a theme
Use it for a couple minutes (enable root and usb debug in Developer Settings, set my apps up, etc)
Restart two or three times without any hiccups
Suddenly, after a random reboot, the boot animation happens twice (instead of only once how it supposed to be)
Phone boots and shows "Android is starting..." and optimizes the apps (104 of them) one by one
Goes to "Starting apps..." and succeeds
The phone shows the lockscreen, but only for approximately 1-2 seconds
Phone reboots
CM boot animation runs twice, once for a long time then again for a shorter period of time
Phone goes through process described above (Android is starting, optimizes, then flashes lockscreen)
This just happens again and again and again
Steps I've taken to try and remedy the issue:
Run: "adb reboot" from computer while phone is optimizing apps
Hard reset the phone by holding the power button for 15 seconds
Run: "adb reboot bootloader" from computer when possible, then go into recovery and wipe both dalvik and normal cache
Swipe on the lockscreen as soon as I see it to see if I can get in (lockscreen does not respond though)
Go into recovery and shut the phone off, then start again
Let it loop for about 2 hours
I had also tried leaving the phone overnight looping, and when I woke, it was still looping, but after a eight or so more hours, I came back and found that it had booted and stayed on (and was working completely normally).
The phone was running stock 4.4.2 completely fine before this (with no reboot issues). I attempted installing the latest version of BlissPop, which exhibits a similar but still different issue (it would always boot into android [and not loop], but after a couple restarts, it showed an error about the System UI crashing that would pop up every time I dismissed it, and continued doing so after each restart after that). CM11 seems to be running well on the phone (but only in my very limited test while transitioning between ROMs and such).
I unfortunately cannot provide a log due to not being able to run any logging app during bootup, but hopefully I have provided enough details above to allow understanding of the issue and maybe bring suggestions on how to fix it. I can provide any more information needed on request. I really would like to get this phone back up and running (and especially on this ROM as I do love the work the creator has put into it).
Sorry for the very large wall of text :| Thank you in advance for any suggestions on how to proceed from here
tartilc said:
My device is a 2013 Moto G XT1031 (Boost Mobile) with Bootloader version 41.05 and the latest CWM recovery.
Click to expand...
Click to collapse
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
a_gert said:
Having not experienced your issue I can't say for certain, but it may be possible you need to update the bootloader to at least 41.13, which is the 4.4.4 KitKat BL? I'd run it past @Meticulus and see if he might have some direction, there. Also, does the theme you apply have a different bootanimation, by any chance? There is a known issue/potential memory leak related to large boot animations on Lollipop that can cause failures at boot or bootloops.
Click to expand...
Click to collapse
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
I now have a logcat! I'm having trouble understanding what it is talking about, but I started logging as soon as the "Android is starting..." box changed status from "Optimizing apps x of x" to "Starting apps" and then stopped logging after a couple seconds of the boot animation. It is attached below (split into three parts).
EDIT: Attached what might be a better logcat reading (recording started right before lockscreen showed, I tried unlocking it, then stopped as soon as I saw the blue animation)
tartilc said:
Thank you for the advice I have downloaded a file with the name of falcon_boost_user_4.4.4_KXB21.14-L1.57_57_release-keys-cid9.xml.zip, unzipped it, then flashed according to the directions posted on how to restore the stock firmware. Everything during installation seemed to go smoothly, but at this point, I am stuck again. When I try to boot up, it just shows the splash screen ("Warning Bootloader Unlocked") and stays there indefinitely :| I have hard reset the phone and got into boootloader, which states that I am now on 41.13, but it just stays at that splash screen Should I boot into TWRP and try flashing an update.zip of the stock 4.4.4 Boost ROM? What else can I try?
EDIT: Flashing the stock update did not work, but I was able to install CM11 (so I'm am on bootloader 41.13 with CM11 currently)
EDIT TWO: Yes! I'm on bootloader 41.19 now and official CM12.1 nightly is booting!!
EDIT THREE: NOOOO It just started bootlooping again! CM animation twice, "Android is starting...", lockscreen, then cycle again. It happened after I changed my DPI from 320 to 280 (never restarted, just looped from then on).
Click to expand...
Click to collapse
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
XPOSED on Meticulous Rom?
Is there any way to get XPOSED working? I really want gravity box for LL.
Awesome. I was going to download this from your site today but it is showing an error with connecting to its database. None of the computers i have access to can get on your site.
no wifi no cellular network
and after i flashed cynogenmod 12.0 in my moto g 2014, there is no wifi nor network :'( what am i suppose to do now?
Ui crash
Is there anything special i need to do to flash this update? i'm running on the 408 build and every time i try ti go the next version there is an issue. Either data stops working or i get a system Ui crash like on the 530 build. I would love to get this issue fixed with the 606 build. Besides that, great job.
a_gert said:
Whoa, that's a lot of jumps! Be careful with the bootloader, as once you're on the Lollipop BL (and it appears you've already made that jump), you're kind of locked into LP ROMs from this point out. The point you were failing on the 4.4.4 stock would probably have been a good time to go in and manually restore things via fastboot just to make sure all your partitions were straight. What did you use to update your bootloader to 41.19? And have you tried a ROM specifically designated for the CDMA-only XT1031/Boost? I've only used the Meticulus and the unofficial Linaro CM12.1 buld by Cody on my XT1028 specifically because I know they're CDMA compatible, so I'm not sure where the official CM12.1 sits on that right now.
I know there exists an actual legitimate stock 5.0.2 Boost ROM and it's possible that may be able to be restored manually as a last resort, so don't move too hastily.
Click to expand...
Click to collapse
Yeah that is a lot of jumps I'd be hella nervous myself lol
K well guys today is your day , as a_gert stated there is a boost 5.02 , and it does work fine on any cdma xt1031 so first flash that
-depending on signal you may wish to update your modem also there is only 4.4 modem for boost public
Buuuutttt nvm all that for now
The problem the ONLY problem I have had when bootlooping was that it was not prepped correctly and my phone came with 41.19 and came unlocked-
1.) Make sure you are on c/O SuperR-Developer -- PhilZ-Touch-6.59.0_LPK .img OR twrp * twrp-2.8.6.0.1-falcon_STOCK.img
**Notice For Even PhilZ I only Named the -IMG- Version which means flash it with adb properly please
***if ever after you flash it via recovery it will show partition mismatch which apparently is no problem just that the custom recovery does not match the factory one is all.. ..
1.) Download PhilZ-Touch-6.59.0-LPK.img to PC
2.) Reboot to bootloader
3.) Plug phone into PC
4.) Open terminal in directory where the img is located
5.) Issue the following command:
Code:
fastboot flash recovery twrp-2.8.6.0.1-falcon_STOCK.img
2.) Do a format of System w/EXT4 AND REBOOT INTO RECOVERY
3.) Format dalvik/art + Cache + Data w/EXT4 & REBOOT INTO RECOVERY
4.) Format Data PLUS data/media with f2fs then Do the 'factory wipe' then manually format data/media with f2fs again please ..
- SIDELOAD THE ATTACHED STOCK LOLLIPOP NO GAPPS GIVE IT TEN MINUTES REBOOT FEW TIMES/ POWER DOWN ONCE & REBOOT AGAIN
5.) Reboot into recovery and flash the first zip I have attached (I_nomodem is just IF you find your 4.4 radio baseband worked better and want to format it for LP again in the future WITHOUT LP radio included)
****EDIT - SEE VERY BOTTOM OF POST CENTERED AREA LOL
6.) Power off & reboot into recovery manually
7.) Flash your Rom (OR STOCK LOLLIPOP DEBLOATED AGAIN) + Kernel(if any custom one) + Gapps -wait 5-15 minutes for initial boot
* I recommend AeroKernel for the included stock lollipop 5.0 debloated if not the stock kernel or after flashing and few reboots to settle ,just follow instructions from that thread if any are needed..
Please anyone with any moto g don't think updating your bootloader is needed or even really safe whatsoever it is THE main reason moto phones get bricked or messed up otherwise it is not necessary or any kind of improvement yes once you are on an LP one leave it be..
Other flashing yeah okay, bootloader no if so proceed with utmost caution.
After this your modem will be updated with the cdma LolliPop one, if you have any signal issues or what not go to the stock modems section for your specific phone and flash the one for your specific carrier and/or find the "update RIL" flash thingie on here in moto G section and follow instructions but the boost modems work on all cdma variants of Moto G..
For whatever reason I could not upload files to xda I tried five times it kept dying so here there are on googldrive :good:
**Do not Click individual Item Use the Download Arrow At the Very Top of Page to DL the zip properly plz
1.) Falcon LolliPop Part Updater + Modem
2.) Falcon LolliPops Part Updater (No Modem)
_____________________________________________________________________________________________________________________________
--EDIT #2-- LolliPop 5.0 Falcon XT1031 debloated
SIDENOTE: IF YOU FORMAT DATA/MEDIA & DO NOT KNOW HOW TO SIDELOAD THE ABOVE STOCK DEBLOATED ZIP I'M PRETTY SURE YOU'RE NOT GONNA LIVE TO TELL BOUT IT
BE PREPARED TO SIDELOAD - REBOOT IMMEDIATELY AFTER SIDELOAD THE ZIP ROM IS COMPLETE NOT INTO RECOVERY NOT ANYWHERE ELSE SYSTEM REBOOT
-And wait 5-10 Minutes For First Boot - You Only Need to Do this for the first LP rom loadin after that normal flashing do NOT format data/media anymore after this initial setup
--You can try to just use the script, but it did not work for me after many tries the above was the real solution and has been perfect since
2,3,4,5,6,7
·Install flashable (Boost Mobile/CDMA XT1031 only):
·Download falcon_PhilZ-Touch-6.59.0_LPK.zip to phone
·Reboot into current custom recovery
·Flash zip
·Enjoy!
Use the script again to prepare you partition properly anytime you are about to flash a new rom clean after factory wipe/ format is done..
As I said before data/media is never necessary again after this and MAY not be this time but it is the only thing that kept me out of bootloops ,and if you do it yeah it will force you to sideload your rom it erases all leftovers and your rom zips off the internal card and formats them for fresh start The script does not format /media guys k no worries
------TWRP 2.8.6..1 does not seem to restore properly- -system write only thing .. PhilZ-Touch is fine as is twrp-2.8.6..0 also
Nice, got 41.19 BL!
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
rammsteinaus said:
I tested this and works fine, now i have my shiny new moto g running AICP. Thanks @shoobiedoobiiwhompwop!
Click to expand...
Click to collapse
K welcome
Arrite guys for a little clearer step by step see here please apologies carrying on and on I have been gone quite some time here http://forum.xda-developers.com/mot...-moto-g-xt1031-lollipop-t3132974#post61346260
It actually Runs really nice, really REALLY nice once the system app package I am adding shortly was used and tweaked out ..
Is it safe to flash cyanogenmod onto the verizon moto G - 1028 4.3 plus
Hello community ,
I had serious problems flashing cyanogenmod onto a galaxy S3 that was running stock 4.3 , verizon bricked my S3 , and said that the software was not authorized by Verizon. Does this problem exist across the board for any verizon phone running 4.3 or higher ?? If so ... then anything to do with flashing cyanogenmod onto a verizon phone should have warnings in BIG RED LETTERS ... because you cannot even buy a new phone with 4.2 on it anymore.
Issues flashing cm12.1 on XT1031 Please Help
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Moto G CDMA issues
citizen3rased said:
Tried flashing the second to last release on 2 of my moto g xt1031's and I keep getting diff issues. This is what I did:
I had complete stock 4.4.4
unlocked bootloaders,
flashed latest TWRP,
Did a factory wipe
Flashed CM12.1
Flashed Gapps
Rebooted
Stuck in boot loop--> waited over 30mins and rebooted a few times. No luck.
I heard to try flashing CM11 first, then flashing 12.1 so I did this:
Back to TWRP -->factory wipe
Flash cm11
reboot to cm11
reboot to TWRP -->factory wipe
Flash CM12.1
Now I can get past the boot logo and begin setup, however, it will randomly reboot to the boot logo and then back to setup after a minute or so- erasing anything I've already input. Sometimes I could make it through the setup to the desktop, but then it would do the same thing. Had this same exact issue on both of my xt1031s with the same process used for both.
After this I tried doing a factory wipe and then also wiping /data and /system in the advanced wipe options and then flashing cm12.1 and still had the same issue of the rebooting. At some point I must have done somthing, but I started trying to just flash cm12.1 several times over to see if it would stick and I noticed when I did the factory wipe I was getting a parsing error so I tried doing a full data format, and fix data filesystem. I'm not sure what format it was supposed to be so I did a ex4. THat stopped the parsing error, but still having the same issues.. any help would be appreciated.
Click to expand...
Click to collapse
Hello Citizen 3 , You are farther along than me. I have only successfully flashed cyanogenmod once , and that was on an S3 so it was straightforward. I still have not unlocked my bootloader. I have not been able to copy and paste the long strings of characters from motorola , inside command prompt. It would be so nice if Meticulus or one of the other developers could get this to be an official release. The Moto G , and a few other inexpensive phones ( LG realm , Kyocera Hydro latest version ) would work like greased lightning , if they were running CM12. Any help that you could offer with pasting the strings of unlock code would be so appreciated.
I want to ask if there is any problem (flicker screen, red notification on booting up...) when I install CM11 from stock 5.0.2 on Falcon Moto G XT1032? (follow this official guide on CyanogenMod: http://wiki.cyanogenmod.org/w/Install_CM_for_falcon)
Thank you.
I've done this recently and the only issue I've noticed is the screen flickering problem. The solution is to simply press the power button to lock the screen then unlock it and it should be fixed. You only have to do this once but if you reboot your phone you will have to lock/unlock again on first boot.
Thank you for your answer. Just to be sure, did you follow CM guide? Is there anything important which I should be careful about? (I did the same thing with several phones but still noob)
I just booted into custom recovery (I use Philz) and wiped the different partitions along with /cache and /dalvik. You can follow the guide and use the push method or you can use sideload which I did.
I did that and now i have problems with the mac address (i was using 5.1.1) my shows me a different mac and i don't know how fix it, but if i back to LP the problem is solved.
It's a bootloader issue for sure and general happen because you're bootloader is updated to Lolipop 5.0.2 and now you install kitkat as cm 11 over Lolipop.
In simple words your bootloader is new while the software is old
screen flickering issue can be resolved by downgrade bootloader but "BE EXTREMELY CAUTIOUS" failed to upgrade bootloader make your device permanently dead and downgrading is not recommended....
I will recommend try cm12.1 it's rock solid stable as cm11
I finished installed CM 11, firstly the prob is screen flickering. Then after installing all my apps, the android.com.systemui was crashed over and over and cannot use anymore. I reflashed CM and gapps and reinstalled apps but it happened again. Finally, I had to returned to Lollipop.
Anyway, thank you all for your help
Same thing happened to me unfortunately but I've found this one here and it is working beautifully. Try it and see if it works for you without the constant systemui errors.
Thank you. At the moment i am quite happy with GPE version. It seems that this version GPE 5.1.1 is better than Moto stock one.
Hi guys
I have CM11 installed, the problem I have is when is power off the Moto G, it automatically restarts. I want to be able to keep it off to charge quicker.
Any ideas?
bigmaz said:
Hi guys
I have CM11 installed, the problem I have is when is power off the Moto G, it automatically restarts. I want to be able to keep it off to charge quicker.
Any ideas?
Click to expand...
Click to collapse
Which CM11 build are you using? i built one my self with latest sources and i got the same problem, it's probably due to a specific commit we've probably already identified, (i tried to fix it wit the help of Alberto97 and i failed, more or less, is that i tried to use Lollipop kernel on CM11 to avoid the screen flickering, i got a black screen instead of the automatically restart because of the updated kernel), anyway i just dropped it, the only reason i've tried to get a fully working CM11 was a bug with Motorola update 5.X (yes, stock ROM has that bug too and we get RIL binaries/libraries from it) and my provider only (H3G ITA), when making a call, it doesn't show the number that i called in the recent calls, but it shows "private number" instead.
I've recently received a good offer by a different provider, so i don't longer need to back to KitKat.
Here is the build info. Thanks