[RC-FAQ]>> CM12 Frequently Asked Questions for Motorola Moto G [Updated: 2015/09/08]

[djpailo]

My Story:

I have a Moto G 2013 3G and was on UK stock 5.0.2 and I did the following steps:

-unlocked the bootloader successfully
-rooted the phone successfully
-Installed TWRP successfully
-Mounted latest CyanogenMod onto SD Card successfully
-But upon flashing the zipped ROM, it always failed.

After researching, I thought updating the bootloader might help. I followed the links provided in the thread, used the tool for windows and updated the bootloader to version 41.19 and then tried again, but this didn't work for flashing the new ROM. I then read the error message and it said:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
Although I had already done this prior to updating the bootloader, I simply tried again and this time it worked!

So now I have the latest bootloader and CM12. I am very grateful for all the instructions.

I'd like to ask some questions for understanding purposes:

1) adb only worked when my phone was booted up in normal mode. It would never list any devices when the phone was in fastboot. Is this normal?
2) I am on TWRP and it had this flashing/ flickering thing on screen. Even upon updating the bootloader, the flashing thing was still there. What should I do now? I am on TWRP 2.8.6.0
3) I notice there is a Cyanogen Recovery img from the downloads page. Is this another recovery system instead of TWRP and if so, why, on the guide, are we told to install TWRP and not the cyanogen one?
4) Can I flash a different recovery, like ClockwordMod, without having to re-flash a system ROM?
5) I still see the motorola bootloader message telling me the phone's bootloader is unlocked (I've been lazy and not searched this up, will do in morning), is this normal?
6) After flashing the ROM, can I remove the zip file from the /sdcard/ location?

PS: Thanks for adding a blocked caller feature. I was amazed Motorola didn't add this!

 

[ice-it]

Issues with accelerometer and orientation sensor

Hello, I've flashed cm12.1 20151010 nightly on my xt1032 retail UK, (bootloader 41.1A and TWRP 2.8.7.0) after a complete wipe of the system. I've noticed a strange behavior of Google when I use the blur mode : even if the phone is still the camera feel the movement too fast. I've used cpu-z to look into this issue and seems that the accelerometer and the orientation sensor values change continuously even with the phone laying on the table, it feel strange for me. Anyone have the same problem here?

 

[insanezz]

My Story:

I have a Moto G 2013 3G and was on UK stock 5.0.2 and I did the following steps:

-unlocked the bootloader successfully
-rooted the phone successfully
-Installed TWRP successfully
-Mounted latest CyanogenMod onto SD Card successfully
-But upon flashing the zipped ROM, it always failed.

After researching, I thought updating the bootloader might help. I followed the links provided in the thread, used the tool for windows and updated the bootloader to version 41.19 and then tried again, but this didn't work for flashing the new ROM. I then read the error message and it said:
"Can't install this package on top of incompatible data. Please try another package or run a factory reset"
Although I had already done this prior to updating the bootloader, I simply tried again and this time it worked!

So now I have the latest bootloader and CM12. I am very grateful for all the instructions.

I'd like to ask some questions for understanding purposes:

1) adb only worked when my phone was booted up in normal mode. It would never list any devices when the phone was in fastboot. Is this normal?
2) I am on TWRP and it had this flashing/ flickering thing on screen. Even upon updating the bootloader, the flashing thing was still there. What should I do now? I am on TWRP 2.8.6.0
3) I notice there is a Cyanogen Recovery img from the downloads page. Is this another recovery system instead of TWRP and if so, why, on the guide, are we told to install TWRP and not the cyanogen one?
4) Can I flash a different recovery, like ClockwordMod, without having to re-flash a system ROM?
5) I still see the motorola bootloader message telling me the phone's bootloader is unlocked (I've been lazy and not searched this up, will do in morning), is this normal?
6) After flashing the ROM, can I remove the zip file from the /sdcard/ location?

PS: Thanks for adding a blocked caller feature. I was amazed Motorola didn't add this!

1. Yes, adb only works when your phone is on. It won't list any devices because you're in fastboot and that's a different mode. If you type the command ''fastboot devices'' it should list it when you're in fastboot.
2. I have the same flickering when I'm in TWRP. I'm not sure why tough.
3. I'm not sure how long cyanogen has been offering their own recovery. The guide on XDA hasn't been updated i think. But TWRP is mostly fine so i don't see a reason to download the cyanogen one.
4. Flashing a different recovery shouldn't be a problem. You shouldn't have to reflash the entire rom. (but i'm not a 100% sure on this).
5. Yes i have the same message everytime i boot my phone. You can get rid of it but i'm too lazy. If you want to know how just search XDA there's a thread for it somewhere.
6. If you have flashed the rom you can delete the zip from your SD card indeed.

 

[tlwhitec]

Hello, I've flashed cm12.1 20151010 nightly on my xt1032 retail UK, (bootloader 41.1A and TWRP 2.8.7.0) after a complete wipe of the system. I've noticed a strange behavior of Google when I use the blur mode : even if the phone is still the camera feel the movement too fast. I've used cpu-z to look into this issue and seems that the accelerometer and the orientation sensor values change continuously even with the phone laying on the table, it feel strange for me. Anyone have the same problem here?

Hi, AFAIK xt1032s don't have a gyroscope (which is (I think) a requirement for such features as photosphere or lens blur). So I'm afraid you'll have to wave bye bye to these features. I'm quite surprised that the Google cam lets you enable the lens blur mode.

 

[ice-it]

Hi, AFAIK xt1032s don't have a gyroscope (which is (I think) a requirement for such features as photosphere or lens blur). So I'm afraid you'll have to wave bye bye to these features. I'm quite surprised that the Google cam lets you enable the lens blur mode.

Thanks for reply, but I think only photosphere need the gyroscope, cause I've used the lens blur many time on stock fw without issue, it only need a little move up, so I think this is a accelerometer related thing.

 

[tlwhitec]

...cause I've used the lens blur many time on stock fw without issue...

If that's really so, then it really has to be some problem with (reading) the sensors. Too bad I can't help you here confirm the issue. I bought an xt1032 for my GF, but now she won't let me play with it

 

[captain_nemo]

If Snapshot build may come on near future for 12.1?

 

[roshan2989]

hello guys,i just got my brother phone(xt1033) from the shop,just came back from warranty..and my brother say he want single sim.
so the phone was in moto 4.4.4 (1033xt) stock..so i converted to gpe succesfully..so the problem is i cant install cyanogenmod 12.1 on the phone..sometime its stuck on "patching system unconditionally " so i had to revert back to kit kat gpe for a while..help would be appreciated guys..

sorry to mention one thing i just updated the bootloader to 4.1.18..

 

[nikilpereira]

Sms/MMs Issue

Hi Guys,

Device model - xt 1033
Android Version - 5.1.1
CM 12.1-20151017-Nightly-falcon

Flashed the rom as per instructions. Everything works except the SMS/MMS part. I can't see/send/receive any SMS.

Log cat says "PackageManager: Failure retrieving resources for com.android.mms: Resource ID #0x0"

Now this sort of error comes for any 3rd party texting app also including google's messenger. I've tried updating with the latest CM12.1 or downgrading to a bit older version also but no avail. Also i did a complete wipe off from my fone before installing the OS.

Any help or suggestions would be appreciated.

 

[doryx]

Encryption Working

Found plenty of people asking if encryption is working on CM12.1 nightlies with the Moto G (falcon) but no straight answers. Is encryption working for anyone? If so what build date? I can test it this weekend but can't deal with a boot looping phone during the week.

Thanks

 

[Pupet_Master]

I don't know if its on the right topic but..
On the Peregrine Moto G LTE/4G (2013)... what are the advantages of CM12.1 vs the stock ROMs with Xposed?
In term of performance (as i use crDroid with Xposed on it.. but i'm considering in give stock a try as i never instaled stock Lollipop.)

 

[gm2racer]

I have an Boost XT1031 running on ringplus. Does anybody know how I can get 3G data to work? Calls and SMS work.

Thanks

 

[marioherobr]

I have an XT1032 but i'm getting Emergency calls only error, i try flashing radio but didn´t work, any help?

 

[alfick3]

I just updated to the 1107 nightly and noticed the section that was supposed to indicate the latest security patch, but it looks like a US phone number. Is that just a mess up with text or is it something else? Please seed attached screen shot.


Sent from my Moto G XT1034 using Tapatalk

 

[gabriel96torres]

I have an XT1032 but i'm getting Emergency calls only error, i try flashing radio but didn´t work, any help?

You have installed a rom?

 

[samewaterbottle]

You have installed a rom?

No Snapshot out yet?

 

[GuestD0709]

No mobile data connection

Hello!

I just followed the CM 12.1 install steps (using with TWRP) on my XT1032 with stock rom.
I had no problems with the installation process, but I noticed that mobile data connection is not working. It keeps showing and exclamation mark on the signal icon and the browser shows a dns resolve error.
I tried with the last snapshot and the last nightly build, on both is not working.

Anyone knows how to resolve this?

Thanks

---------- Post added at 12:24 PM ---------- Previous post was at 11:46 AM ----------

Hello!

I just followed the CM 12.1 install steps (using with TWRP) on my XT1032 with stock rom.
I had no problems with the installation process, but I noticed that mobile data connection is not working. It keeps showing and exclamation mark on the signal icon and the browser shows a dns resolve error.
I tried with the last snapshot and the last nightly build, on both is not working.

Anyone knows how to resolve this?

Thanks

Nevermid, I re-created the APN settings and now is working! :victory:

 

[G0rr]

[SIZE=+1]Q9: Why do i get screen flickering (until i turn off/ON screen) and how to get rid of it?

Two cases:

• You are using the new lollipop bootloader (41.18) and an 'old' CM12 nigthly ==> simply update to a 20150315+ one.
• You are still on one of the old JB/KK bootloader (41.05~41.15) and installed nightly 20150315 or newer (until 20150324+)==> you'll need to upgrade your bootloader. (cf question 10)

[/SIZE]
[SIZE=+1]Q10: Why does the installation abort? (nightly 20150324+)

If you are facing this error:

this package support bootloader(s): 0x4118: this device has bootloader 0x4113.
E: Error in /data/media/0/cmupdater/cm-20140324-NIGHTLY-falcon.zip
(Status 7)
Installation aborted

Then you need to update your bootloader:[/SIZE]
Upgrading the Bootloader:
Available bootloaders : 41.18, 41.19, 41.1A for the following devices:

• XT1032 - Global GSM MotoG Single SIM: 41.18, 41.19, 41.1A
• XT1033 - GLobal GSM MotoG Dual SIM: 41.18, 41.19, 41.1A
• XT1034 - US GSM: 41.18, 41.19, 41.1A
• XT1039 - 4G/LTE MotoG (Europe): 41.1A
• XT1040 - 4G/LTE MotoG (Brazil/Canada): 41.1A
• XT1045 - 4G/LTE MotoG: 41.1A
• XT1002: 41.18
• XT1003: 41.18
• XT1008: 41.18

All available bootloaders can be found here
NOTE: Flashing bootloader (and failing, for any reason) is one of the few way to HARDBRICK your Device.

If for some reason you can't (or don't want to) update your bootloader, then read this post by @wskelly

Windows
Use the bootloader upgrader tool provided by @Xyzko

Linux:
Before messing with the bootloader:

1. Download manually the desired bootloader here IF YOUR DEVICE WAS LISTED ABOVE.
2. Check the file integrity by checking the md5sum.
3. You are ready

Open terminal in the BL folder (or cd to it), plug device to PC.

adb reboot bootloader

Check your current bootloader :

fastboot getvar version-bootloader

Output example: (bootloader) version-bootloader: 4105
==> my bootloader was 41.05

Then flash the new one:

fastboot flash motoboot motoboot.img

Wait until done:

target reported max download size of 536870912 bytes
sending 'motoboot' (1953 KB)...
OKAY [  0.114s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [  1.567s]
finished. total time: 1.682s

(A new blank command line waiting for instruction will appear in terminal)

Reboot the bootloader:

fastboot reboot-bootloader

Re-check its version:

fastboot getvar version-bootloader

Expected output: (bootloader) version-bootloader: 4118
==> my (and your) bootloader is now 41.18

Reboot your device, now the screen flickering should be gone in CM12 (but might appeared in your recovery, depending on the build time...)​

Hi.

I don't know whether someone already asked this, but I'm having a bit of trouble updating the bootloader.

I have a xt1032 and downloaded the 41.19 version.
I followed your steps in a Linux and found out the bootloader version is 41.13, but as soon as I type the command 'fastboot flash motoboot motoboot.img' a message appears saying
error: cannot load 'motoboot.img': No such file or directory".

I don't know whether it helps or not, but in my mobile screen it appears
cmd: getvar: partition-type:motoboot
cmd: getvar:max-download-size

I was wondering if you could me some hints on what to do.
Cheers

 

[_that]

I have a xt1032 and downloaded the 41.19 version.
I followed your steps in a Linux and found out the bootloader version is 41.13, but as soon as I type the command 'fastboot flash motoboot motoboot.img' a message appears saying
error: cannot load 'motoboot.img': No such file or directory".

Make sure motoboot.img is in your current directory before running that command.

 

[matmutant]

Hi.

I don't know whether someone already asked this, but I'm having a bit of trouble updating the bootloader.

I have a xt1032 and downloaded the 41.19 version.
I followed your steps in a Linux and found out the bootloader version is 41.13, but as soon as I type the command 'fastboot flash motoboot motoboot.img' a message appears saying
error: cannot load 'motoboot.img': No such file or directory".

I don't know whether it helps or not, but in my mobile screen it appears
cmd: getvar: partition-type:motoboot
cmd: getvar:max-download-size

I was wondering if you could me some hints on what to do.
Cheers

is you bootloader file really named motoboot.img ? or motoboot_4119.img?