[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
To Browse quickly the FAQ and find what you need, Ctrl+F is the key feature
From CM11 or CM12: simply download ROM zip and gapps, then Flash From other ROM:
download ROM and gapps
Reboot to recovery
Format /system, /data (data content will be lost, but should not impact /data/media), /cache and wipe dalvik-cache.
==> this is for CWM, on TWRP, better use the factory-reset option.
Sideload from Computer or install from storage depending on where the download was completed)
wait
Reboot
wait (may take more than 3 minutes)
enjoy!
Rq:
For Falcon, Nightly releases on official CM12 are reported working on XT1032, XT1033 and XT1034 and GPE XT1032. The XT1028/XT1031 (non-LTE 3G CDMA) are not able to get data, calls and SMS
For Peregrine: ?
[SIZE=+1]Q2: How to get root?[/SIZE]
Enable Dev settings (multiple tap on "Build Number" in /settings/about phone/)
Go to Dev settings
Root access : Change to Apps and ADB
[SIZE=+1]Q3: Where is the Terminal?[/SIZE]
It is now disabled by default, simple enable it in Dev Settings by toggling "Local Terminal"
[SIZE=+1]Q4: What's that # at the to right corner of my screen sometimes?[/SIZE]
This icon warns you that an app or service is currently using its granted root access, maybe your file manager or some automated actions like Greenify auto hibernate is running (in the background?)
[SIZE=+1]Q5: How to set SELinux state to Permissive?[/SIZE]
Paste it to /etc/init.d, set permissions to -rwxr-xr-x and edit extension to .sh to file manager can execute
Execute the script manually at each boot if your SELinux state is anything above Permissive (init.d scripts are not granted SU rights when in Enforcing mode).
[SIZE=+1]Q9: Why do i get screen flickering (until i turn off/ON screen) and how to get rid of it? (nightlies 20150315-->20150324)[/SIZE]
The answer involves upgrading your bootloader, be extremely careful.
Follow this short step-by-step guide
[SIZE=+1]Q10: Why does the installation abort? (nightly 20150324+)[/SIZE]
If the error message you are facing is the following,
Code:
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 The answer involves upgrading your bootloader, be extremely careful.
Follow this short step-by-step guide If for some reason you can't (or don't want to) update your bootloader, then read this post by @wskelly
[SIZE=+1]Q11: How do i report an issue to get some help?[/SIZE]
It says the device model, the Bootloader version, the ROM (the one coming from and the one where the problem occures), and some more informations about the process.
[SIZE=+1]Q12: Why Ambient display and gestures are gone and how to get it back?[/SIZE]
Ambient display and gestures were handled by motodoze which conflicted with Android's way of turning screen On and Off, this application from motorola has its sources closed and thus cannot be modified by CM team to handle the conflict. Motodoze has been nuked (20150903)
But we have a new king to rule the kingdom: AcDisplay !
[SIZE=+1]Q13: Having issues with your partition table?[/SIZE]
When installing CM you may experience being stuck at "Patching system image unconditionally..." mainly if you device was converted to GPe.
This happens because the recovery tries to write a block that exceeds the partition size (/system of the GPe partition table seems to be smaller than the CM one) ==> this also happens when you want to upgrade a MotoE (Condor) from stock 4.4.4 to CM12.1
I'm having issues with the camera. Both the cyanogenmod camera and the good camera aren't taking any pictures. Both apps open and otherwise function properly, but whenever I try to take a picture it just doesn't work: the animation of a taken picture occurs, but then nothing happens. What can I do? This had been a persistent problem for the last couple of nightlies.
I'm having issues with the camera. Both the cyanogenmod camera and the good camera aren't taking any pictures. Both apps open and otherwise function properly, but whenever I try to take a picture it just doesn't work: the animation of a taken picture occurs, but then nothing happens. What can I do? This had been a persistent problem for the last couple of nightlies.
Ok I just came back to my Moto g. And now that I would like to flash a cm12 rom I don't know which one because theirs more than 5 cm12 roms out there!!!.. Can anyone point me to the one that is best to flash plz.
Ok I just came back to my Moto g. And now that I would like to flash a cm12 rom I don't know which one because theirs more than 5 cm12 roms out there!!!.. Can anyone point me to the one that is best to flash plz.
if you are talking about keyboard, then, that's a known issue (try to use google keayboard instead, available on playstore), i will try to make a "know issue chart" ASAP but i don't have enough time right now
Initially the camera seems to work. I can reboot and the camera works for a few hours. After a few hours it stops working. It takes a pic and then doesn't save it...This has been the case since the first official nightly.
I'm sure it will get ironed out! So far, working mostly great otherwise!
Initially the camera seems to work. I can reboot and the camera works for a few hours. After a few hours it stops working. It takes a pic and then doesn't save it...This has been the case since the first official nightly.
I'm sure it will get ironed out! So far, working mostly great otherwise!
I just flashed it, and I will try not to reboot for a day or so, 'cause the problem seems to arise after some time, as you said in your post. Right now camera is working well.
I just flashed it, and I will try not to reboot for a day or so, 'cause the problem seems to arise after some time, as you said in your post. Right now camera is working well.
Please, i'm having issues with the camera since i was trying to use early versions of CM12 ...
Camera loads up, but when i click to shoot a photo, the picture freezes, and nothing happens. Tried with Google Camera ( and updated version) , with Motorola Camera ( and updated version) and several apps, like Whatsapp,Snapchat,etc...
Anyone knows how to fix that, or a previous version where the camera works?
Please, i'm having issues with the camera since i was trying to use early versions of CM12 ...
Camera loads up, but when i click to shoot a photo, the picture freezes, and nothing happens. Tried with Google Camera ( and updated version) , with Motorola Camera ( and updated version) and several apps, like Whatsapp,Snapchat,etc...
Anyone knows how to fix that, or a previous version where the camera works?
Sad I've been using version 01.14 of the nightly, and it seems no problem (of that kind at least) on my XT1032.
Devs suggest to use TWRP latest (2.8.some.thing) as custom recovery.
Upgrading bootloader be able to install CM12 20150324+ nightlies
[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:
Code:
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
From CM11 or CM12: simply download ROM zip and gapps, then Flash From other ROM:
download ROM and gapps
Reboot to recovery
Format /system, /data (data content will be lost, but should not impact /data/media), /cache and wipe dalvik-cache.
==> this is for CWM, on TWRP, better use the factory-reset option.
Sideload from Computer or install from storage depending on where the download was completed)
wait
Reboot
wait (may take more than 3 minutes)
enjoy!
Rq:
For Falcon, Nightly releases on official CM12 are reported working on XT1032, XT1033 and XT1034 and GPE XT1032. The XT1028/XT1031 (non-LTE 3G CDMA) are not able to get data, calls and SMS
For Peregrine: ?
[SIZE=+1]Q2: How to get root?[/SIZE]
Enable Dev settings (multiple tap on "Build Number" in /settings/about phone/)
Go to Dev settings
Root access : Change to Apps and ADB
[SIZE=+1]Q3: Where is the Terminal?[/SIZE]
It is now disabled by default, simple enable it in Dev Settings by toggling "Local Terminal"
[SIZE=+1]Q4: What's that # at the to right corner of my screen sometimes?[/SIZE]
This icon warns you that an app or service is currently using its granted root access, maybe your file manager or some automated actions like Greenify auto hibernate is running (in the background?)
[SIZE=+1]Q5: How to set SELinux state to Permissive?[/SIZE]
Paste it to /etc/init.d, set permissions to -rwxr-xr-x and edit extension to .sh to file manager can execute
Execute the script manually at each boot if your SELinux state is anything above Permissive (init.d scripts are not granted SU rights when in Enforcing mode).
[SIZE=+1]Q9: Why do i get screen flickering (until i turn off/ON screen) and how to get rid of it? (nightlies 20150315-->20150324)[/SIZE]
The answer involves upgrading your bootloader, be extremely careful.
Follow this short step-by-step guide
[SIZE=+1]Q10: Why does the installation abort? (nightly 20150324+)[/SIZE]
If the error message you are facing is the following,
Code:
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 The answer involves upgrading your bootloader, be extremely careful.
Follow this short step-by-step guide If for some reason you can't (or don't want to) update your bootloader, then read this post by @wskelly
[SIZE=+1]Q11: How do i report an issue to get some help?[/SIZE]
It says the device model, the Bootloader version, the ROM (the one coming from and the one where the problem occures), and some more informations about the process.
[SIZE=+1]Q12: Why Ambient display and gestures are gone and how to get it back?[/SIZE]
Ambient display and gestures were handled by motodoze which conflicted with Android's way of turning screen On and Off, this application from motorola has its sources closed and thus cannot be modified by CM team to handle the conflict. Motodoze has been nuked (20150903)
But we have a new king to rule the kingdom: AcDisplay !
[SIZE=+1]Q13: Having issues with your partition table?[/SIZE]
When installing CM you may experience being stuck at "Patching system image unconditionally..." mainly if you device was converted to GPe.
This happens because the recovery tries to write a block that exceeds the partition size (/system of the GPe partition table seems to be smaller than the CM one) ==> this also happens when you want to upgrade a MotoE (Condor) from stock 4.4.4 to CM12.1
[SIZE=+1]This a short list of frequently asked questions in this device forum and the answers often given as a response. It should serve as a starting point for gathering knowledge and finding solutions to many common problems. Please only post in this thread with feedback on how to improve this document. Do not post "Thank you" type responses. If you have additional questions or require more help, try to find an existing thread or create your own. Do not use this as a general help thread.[/SIZE]
To Browse quickly the FAQ and find what you need, Ctrl+F is the key feature
Yeah, it should be the same, though better compare a 4.4.4 bootloader for XT1032 and XT1034 (to see if they are same), and then, if they are, you can try the XT1032/XT1033 41.18 bootloader. i really hope all Falcon devices have the same bootloader, but as for now (26/03/2015) nobody officially asserted that...
It seems to be working fine. I just flashed the XT1032 brazil bootloader via fastboot on my XT1034 and then updated to the latest TWRP. I'm see flickering in TWRP, but I was able to flash the latest CM12 nightly just fine, and there is no flickering in CM12.
hi
i have a xt1033 runnig on stock 5.0.2 asia retail.
can i update directly from current rom to cm 12.1 ?
-------
i have another question.
if i update to cm 12.1 can i return to stock 5.0.2 easily?and how can i?
Yes you can directly clean install 12.1 over stock 5.0.2 but there are some prerequisite
1) You should have to unlock ? the bootloader by going to Motorola website.
2) Install custom recovery like cmw or twrp.
3) make a backup of current rom using recovery.
4) flash cm 12.1 zip after cleaning wiping data/cache & system partitions, no need to wipe internal storage.... Now you're rom is good to go.....
Answer regarding next question is that first you will not want to go back to stock rom because cyanogenmod is addictive, second if in some cases you have to go back.... Then flash the backup rom as created by you in aforementioned step 3 or just flash optimized stock rom zip.... Easy as pie....