The Moto X was a big deal when it was launched.
Like me if you had bought it back then, you would have been severely disappointed that Google stopped thinking about the device as soon as they launched the 2nd Gen.
Forgotten and forlorn, the Moto X gradually devolved into a bloated and clingy device, that started crashing midway through PhoneCalls and got stuck up on a lot of apps.
I decided it was time to change and take back the phone.
I outline my noble quest to root and install CyanogenMod 12 Nightlies on the device.
CM12 – http://download.cyanogenmod.org/?device=ghost
latest CM11 M12 release – https://download.cyanogenmod.org/get…-M12-ghost.zip
TWRP – http://teamw.in/project/twrp2
Mandatory XDA thread – http://forum.xda-developers.com/moto-x/development/rom-cyanogenmod-12-moto-x-t2995381
Before we proceed:
*** DISCLAIMER ***
I AM NOT RESPONSIBLE IF YOU MESS UP YOUR PHONE! OR IF YOU LOSE ANY DATA, ITS CALLED BACK IT UP BEFORE HAND! READ GOOGLE READ IF YOU DON’T UNDERSTAND.
First step is to unlock the bootloader.Download Links
HighonAndroid has an excellent tutorial to do this.
Once the phone is unlocked, the next step is to unlock it.
How to install TWRP/CWM Recovery and SuperSU
Now that you have your bootloader unlocked its time to install are custom recovery and SuperSU so we have Root
Before we worry about that phone please make sure you have installed the SDK and then copied the fastboot files over to the directory your ADB is in. Also before we put the phone into bootloader mode we need to copy the SuperSU.zip over to are phone
Now that we have all that moved over everything that we need. it is time to get are phone into the bootloader you can do that by turning off your phone, Then turning it back on while holding volume down + the power button.
Once into the bootloader plug your USB cable in and set your phone down. Now we need to open a CMD window and CD to the directory ware we placed the MFastBoot files. This is my location but i use the Moto X toolkit yours is going to be ware ever you install the SDK
So in the CMD window navigate to the folder of the fastboot. Now that we are in the right location it is time to install TWRP/CWM we are going to do that by typeing the commands below
fastboot flash recovery twrp-126.96.36.199-ghost-4.4.img
or what ever the name of your recovery img is as soon as you type the above command to flash TWRP/CWM we need to boot the phone into recovery before we let it boot to android we can do that via the buttons below.
click the Volume – button until it highlights Recovery then press the Volume + button to select it and it should boot into recovery.
If you do not immediately boot your phone into recovery after you flash it, recovery wont work.
IMPORTANT: The Device GPS apparently has an independent memory that is not affectd by the ROM. So, it is critical you get a lock on the GPS before flashing the ROM. If you fail to do so, the GPS does not work.
Also, now might be a good time to backup.
Creating And Restoring Nandroid Backups via Recovery
There are a few ways which you can make a Nandroid backup. The recommended way is to use a custom recovery to create one, and it’s the only way to restore from one. Once you’ve flashed TWRP onto your device, you can boot into it and choose to create (or later on, restore from) a Nandroid backup. It’ll go through the process and create a backup file on your storage. This is the recommended method because it can create and restore backups without having Android running at the same time. Doing it this way can avoid any issues that might arise from files that could change during the process of backing up or restoring.
At this point I realized that I had been an idiot in not transferring all the files / downloading the files to the mobile.
So, I rebooted into the system and did a file transfer of the entire thing again.
Then reboot into the TWRP and wipe and then install CM11.
Now, CM 11 throws an error. It fails with error message as
"This package is for device: xt1052,ghost,xt1053,ghost_retail,xt1055,ghost_usc, xt1056,ghost_sprint,xt1058,ghost_att,ghost_rcica,x t1060,ghost_verizon; this device is " + getprop("ro.product.device") + ".")".
To sort this, we just have to remove the first part in the updater script of the CM12 builds.
1. Using 7z app, open flashable ROM zip file
2. go to META-INF\com\google\android\
3. Right Click on the update-script file and select Edit
4. Open this script file with Notepad++
5. Delete the lines starting from “assert (getprop………… upto abort(“this package…..” (see screenshot attached)
6. Save the script in Notepad++
7. Now 7Zip should pop a dialog asking you whether it can save the archive
8. Close zip file
9. Copy to your phone sdcard memory
Now since, you’ve modified the zip file, the Zip file signature Validation will fail. So, be sure to uncheck the box. Once, CM11 is successfully flashed and the cool droid with circles spinning around come alive.
Boot into CM11 and enjoy your hard earned effort for sometime.
So far so good, now all that remains is flashing CM12.
Or so I thought.
The same aprop error exists for CM12 also. Again remove the assert line of code in the ZIP file. CM12 is successfully now running.
The final step is to install GApps. I strongly recommend using Paranoid Android’s GApps.
I used the Pico Version, as this gave me the flexibility to only install the Apps I really needed and avoid all of the other Playstore nonsense.
Link : http://forum.xda-developers.com/showthread.php?t=2397942
Ta da, Ready da
Now boot into your brand new phone and enjoy.
Among interesting features were the ability to set priority interruptions. CM12 also has a theme engine. This is the stock theme. I preferred the Dark Material CM12 theme.
Now that you have the system configured as per your, here are some interesting things that can be accomplished with your new OS.
To change the lockscreen