Originally Posted by insanespain
Because as of now, the way i understand it is that we can't use a version of CWM built for the standard moto g on our GPE devices. Everything in that thread you linked to, pertains to a STANDARD moto g. And even though they are the same hardware, there are some small differences that are causing issues with recoveries. Hence the entire point of this thread.
Any CWM releases that fail to boot on the GPE are broken and will also fail on any non-GPE G with 4.4.2 bootloaders.
Common problems, whether non-GPE with 4.4.2 bootloaders or GPE are:
1) Most 4.4 source-built recoveries fail to boot with "fastboot boot", but will work fine if flashed to the recovery partition
2) Repacks that are compatible with "fastboot boot" are too big to flash into the recovery partition - an example being the repack I posted in a1pha's thread. That particular repack is, for the most part, pretty terribad, but it's enough to allow you to flash SuperSU to root your device.
3) People new to Moto (including myself) forget that volup selects an entry in thebootloader menu and power just forces a normal boot no matter what is selected, leading to them thinking that their recovery is busted (this happened to both myself and Dees_Troy)
I have confirmed that Dees_Troy was able to "fastboot boot" the TWRP image I posted in a1pha's thread, and was also able to flash and run a source-built TWRP that I sent to him (built from integrating dhacker's device trees and kernel into an omni configuration). e.g. his GPE is not behaving any differently, at all, from my non-GPE with 4.4.2 bootloaders.
Main delay has been that until someone was able to gain root, they couldn't gain a backup of the stock recovery for the GPe, and those people were nervous about flashing an unknown recovery to their recovery partition without a backup. The issues with "fastboot boot" resulted in a big delay.