Database Info

CWM and TWRP on Google Play Edition Moto G

Hi everyone,
So it would appear that the current builds of CWM and TWRP for the retail XT1032 Moto G won't boot on the Google Play Edition, at least not while booting from memory.
I've tried using fastboot boot recovery.img and it simply reboots and boots into the stock ROM normally.
Since factory images aren't available, I won't attempt to do a perm flash (fastboot flash recovery recovery.img) because I don't want to overwrite stock recovery without dumping it first (for archival purposes).
So, I guess my question here is twofold.
1. Has anyone else with a Moto G GPE had luck booting CWM or TWRP?
2. If not, is someone willing to try to get a version of one or both that WILL boot?
Any insight and help would be appreciated!
Sent from my Moto G Google Play Edition using Tapatalk

Have you tried the Supervboot method? That may allow you to root without modifying the recovery.

Maybe it sounds dumb, but did you unlocked the bootloader first? maybe you just can flash the recovery safely since the GPE its Android 4.4.2, you can flash the same stock recovery from the US Retail 4.4.2... I don't see why the recovery must be updated on the GPE since it has the same Android version as the other 4.4.2 firmwares...

Beegee7730 said:
Have you tried the Supervboot method? That may allow you to root without modifying the recovery.
Click to expand...
Click to collapse
I'll check into that.
EDIT: Not going to work. It would involve changes to the boot image, which I also don't want to do. I want raw, untouched dumps of system, boot, and recovery. I get the feeling that the only way to get that right now is going to be booting CWM or TWRP from memory using "fastboot boot," but that method doesn't currently work with the currently available Moto G builds of TWRP or CWM.
joel_sinbad said:
Maybe it sounds dumb, but did you unlocked the bootloader first? maybe you just can flash the recovery safely since the GPE its Android 4.4.2, you can flash the same stock recovery from the US Retail 4.4.2... I don't see why the recovery must be updated on the GPE since it has the same Android version as the other 4.4.2 firmwares...
Click to expand...
Click to collapse
The recovery is different between each and every Android ROM. The stock recovery from the retail ROM would probably boot but you wouldn't be able to flash GPE OTAs with it. And yeah, I unlocked the bootloader before I booted it for the first time.
Sent from my Galaxy Note 3 using Tapatalk

I saw this from a post from XDA but maybe you can try it:
conect via adb shell or in terminal emulator type: cat/proc/mtd and press enter
you will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
after that you will have recovery.img on your sd card

OK so I downloaded the stock XT1032 US falcon_umts images for Android 4.4.2. I did fastboot boot recovery.img on the stock recovery from those images. It worked, so the bootloader is definitely capable of booting a recovery from memory. I think this is more an issue with the actual custom recoveries available. With that said, anyone up for trying to get this working? I'll happily be the guinea pig for any test builds.

joel_sinbad said:
I saw this from a post from XDA but maybe you can try it:
conect via adb shell or in terminal emulator type: cat/proc/mtd and press enter
you will see which is recovery partition and then type: dd if=/dev/mtd/mtd1 of=/sdcard/recovery.img (note that mtd1 you must replace with number which is recovery partition)
after that you will have recovery.img on your sd card
Click to expand...
Click to collapse
Unfortunately, that only works if you're rooted. That's why I'm looking to boot a custom recovery from memory. I'll have root access via adb shell and be able to dump to my heart's content without overwriting the stock recovery or the stock boot image. Thanks for the suggestion, though.

Beegee7730 said:
Have you tried the Supervboot method? That may allow you to root without modifying the recovery.
Click to expand...
Click to collapse
@oldblue910 I don't think this method changes boot.img. it just boots a custom boot.img from your PC and roots phone. On next boot it boots boot.img from the phone as normal.
BTW I'm on non-GPE 4.3 stock recovery and can issue
fastboot boot recovery.img
to boot into a custom recovery.
However I believe on nexus devices the option to boot a recovery from PC was removed but you can still do it using some weird parameters on the command - maybe the same type of thing on moto g GPE when booting just a custom recovery??
See following link for the parameters on nexus 7 (which is most likely just for nexus 7 but you get the idea)
http://forum.xda-developers.com/showthread.php?t=2380675

scott_doyland said:
@oldblue910 I don't think this method changes boot.img. it just boots a custom boot.img from your PC and roots phone. On next boot it boots boot.img from the phone as normal.
BTW I'm on non-GPE 4.3 stock recovery and can issue
fastboot boot recovery.img
to boot into a custom recovery.
However I believe on nexus devices the option to boot a recovery from PC was removed but you can still do it using some weird parameters on the command - maybe the same type of thing on moto g GPE when booting just a custom recovery??
See following link for the parameters on nexus 7 (which is most likely just for nexus 7 but you get the idea)
http://forum.xda-developers.com/showthread.php?t=2380675
Click to expand...
Click to collapse
Thanks for clarifying about the boot.img. I'll look into it some more.
As for "fastboot boot", every Nexus and GPE can do it as long as the bootloader is unlocked. I've never had any issue booting recoveries from memory except on the GS4 GPE. Not to get off topic, but touch recoveries are useless if booted from memory on the GS4 GPE. That's not so much of a problem for CWM since you can navigate with the volume and power keys, but TWRP, forget it. If you perm flash, everything is fine.
EDIT: That's interesting about the Nexus 4. Apparently that was a bootloader change beginning with Android 4.3. I can confirm that more modern Nexus devices do not have this issue. Weird.
Anyway, I'm going to look into that root method some more. I'll report with success or failure.

OK, just an update. Superboot doesn't work with the Play Edition ROM. If you fastboot boot it (I tried using normal Android fastboot and the Moto fastboot that comes in the zip file), it just boots to a blank screen and hangs. No boot animation, no nothing.
Obviously there's something different somewhere between the GPE and the retail US XT1032. Not sure what it is...but yeah, right now none of the custom recovery kangs work and superboot doesn't work. The only thing I've managed to boot successfully using fastboot boot was the 4.4.2 stock recovery for the retail US XT1032.

At this point I'm going to loop @a1Pha into this thread and ask if he has any thoughts, since he created the working kangs of CWM and TWRP that people seem to be using.

oldblue910 said:
OK, just an update. Superboot doesn't work with the Play Edition ROM. If you fastboot boot it (I tried using normal Android fastboot and the Moto fastboot that comes in the zip file), it just boots to a blank screen and hangs. No boot animation, no nothing.
Obviously there's something different somewhere between the GPE and the retail US XT1032. Not sure what it is...but yeah, right now none of the custom recovery kangs work and superboot doesn't work. The only thing I've managed to boot successfully using fastboot boot was the 4.4.2 stock recovery for the retail US XT1032.
Click to expand...
Click to collapse
I just rooted my XT1032 US Retail 4.4.2 with Superboot, it booted a weird purple screen and then went black screen, but after Hard Rebooting, the phone was rooted, did you checked that?

joel_sinbad said:
I just rooted my XT1032 US Retail 4.4.2 with Superboot, it booted a weird purple screen and then went black screen, but after Hard Rebooting, the phone was rooted, did you checked that?
Click to expand...
Click to collapse
Just checked. There is no su binary in /system/xbin or /system/bin/.ext and there is no Superuser.apk file either.
Sent from my Moto G Google Play Edition using Tapatalk

oldblue910 said:
At this point I'm going to loop @a1Pha into this thread and ask if he has any thoughts, since he created the working kangs of CWM and TWRP that people seem to be using.
Click to expand...
Click to collapse
Interesting. So did I understand this correctly, that flashing a stock recovery from non-GPE Moto G does work?
Which version does your bootloader show? Which kernel version shows up in phone settings?

a1Pha said:
Interesting. So did I understand this correctly, that flashing a stock recovery from non-GPE Moto G does work?
Which version does your bootloader show? Which kernel version shows up in phone settings?
Click to expand...
Click to collapse
You understand correctly, yes. The bootloader version is 41.05 and the kernel version in settings is 3.4.0.
Sent from my Galaxy S4 Google Play Edition using Tapatalk

oldblue910 said:
You understand correctly, yes. The bootloader version is 41.05 and the kernel version in settings is 3.4.0.
Sent from my Galaxy S4 Google Play Edition using Tapatalk
Click to expand...
Click to collapse
Looks like we have to wait for GPE sources to be released to adapt the kernel to the new bootloader. They should release the sources quite soon, so said a source of @dhacker29

a1Pha said:
Looks like we have to wait for GPE sources to be released to adapt the kernel to the new bootloader. They should release the sources quite soon, so said a source of @dhacker29
Click to expand...
Click to collapse
Sounds good. Thank you very much for your help! Let's keep this thread open for continuing discussion once the sources are released. Once we have kernel source, I'll be happy to test any recovery builds on my GPE device if you need testers.
Sent from my Galaxy S4 Google Play Edition using Tapatalk

oldblue910 said:
Sounds good. Thank you very much for your help! Let's keep this thread open for continuing discussion once the sources are released. Once we have kernel source, I'll be happy to test any recovery builds on my GPE device if you need testers.
Sent from my Galaxy S4 Google Play Edition using Tapatalk
Click to expand...
Click to collapse
The GPE Moto G uses ext4 data partition vs f2fs data partition for the Retail version so it's just a matter of having the right fstab in the recovery.

Try with this build
https://mega.co.nz/#!P8BQGYKK!StnnD0z91KLFxAgxQvSMUVWGC-A-4tcqiv9sgh1yXcw
alternate link
https://drive.google.com/file/d/0BxD_8WtIEc3SZnY2al9ZM0VTOFE/edit?usp=sharing
install with flashify app from phone booted in normal mode and then go to recovery

oldblue910 said:
Hi everyone,
So it would appear that the current builds of CWM and TWRP for the retail XT1032 Moto G won't boot on the Google Play Edition, at least not while booting from memory.
I've tried using fastboot boot recovery.img and it simply reboots and boots into the stock ROM normally.
Since factory images aren't available, I won't attempt to do a perm flash (fastboot flash recovery recovery.img) because I don't want to overwrite stock recovery without dumping it first (for archival purposes).
So, I guess my question here is twofold.
1. Has anyone else with a Moto G GPE had luck booting CWM or TWRP?
2. If not, is someone willing to try to get a version of one or both that WILL boot?
Any insight and help would be appreciated!
Sent from my Moto G Google Play Edition using Tapatalk
Click to expand...
Click to collapse
If you go through a1pha's thread, you'll find a TWRP repack from me that was based on a stock 4.4 kernel. Can you try that with "fastboot boot"? (In fact, that particular release from me is ONLY compatible with fastboot boot as it's too big to fit into the recovery partition...) That particular build has a lot of flaws, but should at least let you flash SuperSU on your device so you can back up the stock recovery and kernel partitions.
My observations on Monday are that a lot of recoveries that work properly when flashed to the device fail when attempting to boot them using "fastboot boot" - even on the non-GPe variants! None of the recoveries in dhacker's CM11 thread work with "fastboot boot" and neither does any one I build from Omni sources.
Many non-Nexus devices often have weird issues where "fastboot boot" doesn't work properly. I know Omni lost at least two weeks on the Oppo N1 due to the fact that "fastboot boot" is broken on that device.

[Q] HELP moto g xt1032 stuck at fastboot

So i tried flashing the lollipop software to my moto g xt1032 (i am a noob at this) and i think i messed up my phone. It now wont go past the bootloader/fastboot screen. Before updating i was running android 4.4.2. When i initially boot up my phone it says version downgraded for boot, failed to validate boot image, fastboot reason: fall through from normal boot cycle i have tried to follow the many guides their are out there that work/i am too dumb to understand them. If anyone can please help me. If i did not give enough info please ask and i will try my best to give it to you.

austin66887 said:
So i tried flashing the lollipop software to my moto g xt1032 (i am a noob at this) and i think i messed up my phone. It now wont go past the bootloader/fastboot screen. Before updating i was running android 4.4.2. When i initially boot up my phone it says version downgraded for boot, failed to validate boot image, fastboot reason: fall through from normal boot cycle i have tried to follow the many guides their are out there that work/i am too dumb to understand them. If anyone can please help me. If i did not give enough info please ask and i will try my best to give it to you.
Click to expand...
Click to collapse
You need to flash android 5.0 factory image for boot, and system. Follow the regular fastboot procedures to flash the 5.0 firmware. Makr sure you don't downgrade back to kitkat once you flash lolipop or else YOU WILL END UP IN A HARDBRICK!!!!!

skyguy126 said:
You need to flash android 5.0 factory image for boot, and system. Follow the regular fastboot procedures to flash the 5.0 firmware. Makr sure you don't downgrade back to kitkat once you flash lolipop or else YOU WILL END UP IN A HARDBRICK!!!!!
Click to expand...
Click to collapse
as i said i am a noob i am not really sure how to do that

skyguy126 said:
You need to flash android 5.0 factory image for boot, and system. Follow the regular fastboot procedures to flash the 5.0 firmware. Makr sure you don't downgrade back to kitkat once you flash lolipop or else YOU WILL END UP IN A HARDBRICK!!!!!
Click to expand...
Click to collapse
i have been trying to flash 5 and when i go in to recovery and load the file through adb it goes for like 5 minutes then says installation aborted

austin66887 said:
i have been trying to flash 5 and when i go in to recovery and load the file through adb it goes for like 5 minutes then says installation aborted
Click to expand...
Click to collapse
You need to flash using fastboot not adb. Look around the forum there are some great tutorials for a beginner.

skyguy126 said:
You need to flash using fastboot not adb. Look around the forum there are some great tutorials for a beginner.
Click to expand...
Click to collapse
So I tried to flashing using fastboot and my device still wont load up

Were you trying to install GPE 5.0.1? Or the soak test for X1033?

austin66887 said:
So I tried to flashing using fastboot and my device still wont load up
Click to expand...
Click to collapse
You need to flash all the partitions.

motorola actually agreed send me a new one despite what i did so all is good

[HELP]Can't Factory Reset. Moto G converted to GPe with Lollipop.

Guys, recently I converted my XT1032 to GPe version to get Lollipop update. I installed everthing and now I've got it.
The problem is, whenether I try to factory reset, it gets Error on Green Robot image.
Is there any solution for this? It freaks me out.

I have the same issue with my converted Moto G. I haven't had time to investigate yet, but there's a (relatively) easy way to do this:
Code:
fastboot erase userdata
Keep in mind that this will erase everything.
If you aren't already familiar with fastboot and the Moto G, there's a wealth of information on this forum. Just search Google and/or XDA for "fastboot Moto G".

Same error here. Got the same error if trying to reach stock recovery. Did you try to flash custom recovery to solve this?

Solved
Antique_Angel said:
Guys, recently I converted my XT1032 to GPe version to get Lollipop update. I installed everthing and now I've got it.
The problem is, whenether I try to factory reset, it gets Error on Green Robot image.
Is there any solution for this? It freaks me out.
Click to expand...
Click to collapse
Bro I did was flash the stock recovery for the GPE with mototool and then I did it manually entering fastboot , recovery and making wipe data . Solved for me

fastboot method is the only current method right now, once the 5.0.2 or 5.0.3 firmware comes out, flash the partition and the stock recovery and try again through recovery.

michael android said:
Bro I did was flash the stock recovery for the GPE with mototool and then I did it manually entering fastboot , recovery and making wipe data . Solved for me
Click to expand...
Click to collapse
Great! Is this a permanent solution, or you have to do this every time you want to reset the device?
Also, if I later want to go back to Motorola Stock will I have issues with this GPE stock recovery?
I hope my questions make sense, as you can see i'm one of those "first time commenting" newbies on XDA

[Q] Moving Line on Screen w/ flickering?

Me being an impatient person, I updated my moto g XT1032, to 5.0.1 GPE firmware, before it came out for official Motorola rom. Since the UI was a bit too laggy, I switched to Cyanogenmod 12 (Yes, it was much smoother). But I started noticing a moving line with a flickering screen (I noticed this on TWRP recovery while I was on GPE firmware, but it didn't bother me). The flickering line is on the boot animation of CM, and it stays there when it turns on, unless I turn off the screen, then turn it on again. This goes for recovery mode as well. This starting to really bother me, so I hope there is a fix for this. One thing I noticed on Fastboot Flash Mode is the following: AP Fastboot Flash Mode (S)
41.18 (sha-99084d5, 2014-10-29 23:54:18)
Noticed the version? It was 2014-10-29, that's a very recent version. I think the bootloader got updated, I didn't think that was possible. Maybe this is causing the flickering's and the line? I saw other articles about this problem, but all of them only talked about recovery mode, and didn't give much detail. I hope someone finds a fix for this. Thanks for reading!

Same problem!
I am facing the same problem too. any solution?
MetalPhoenix45 said:
Me being an impatient person, I updated my moto g XT1032, to 5.0.1 GPE firmware, before it came out for official Motorola rom. Since the UI was a bit too laggy, I switched to Cyanogenmod 12 (Yes, it was much smoother). But I started noticing a moving line with a flickering screen (I noticed this on TWRP recovery while I was on GPE firmware, but it didn't bother me). The flickering line is on the boot animation of CM, and it stays there when it turns on, unless I turn off the screen, then turn it on again. This goes for recovery mode as well. This starting to really bother me, so I hope there is a fix for this. One thing I noticed on Fastboot Flash Mode is the following: AP Fastboot Flash Mode (S)
41.18 (sha-99084d5, 2014-10-29 23:54:18)
Noticed the version? It was 2014-10-29, that's a very recent version. I think the bootloader got updated, I didn't think that was possible. Maybe this is causing the flickering's and the line? I saw other articles about this problem, but all of them only talked about recovery mode, and didn't give much detail. I hope someone finds a fix for this. Thanks for reading!
Click to expand...
Click to collapse

dhyaneswaran.s said:
I am facing the same problem too. any solution?
Click to expand...
Click to collapse
No still didn't find a fix. ?
Sent from my Moto G using XDA Free mobile app

I have the same problem
MetalPhoenix45 said:
Me being an impatient person, I updated my moto g XT1032, to 5.0.1 GPE firmware, before it came out for official Motorola rom. Since the UI was a bit too laggy, I switched to Cyanogenmod 12 (Yes, it was much smoother). But I started noticing a moving line with a flickering screen (I noticed this on TWRP recovery while I was on GPE firmware, but it didn't bother me). The flickering line is on the boot animation of CM, and it stays there when it turns on, unless I turn off the screen, then turn it on again. This goes for recovery mode as well. This starting to really bother me, so I hope there is a fix for this. One thing I noticed on Fastboot Flash Mode is the following: AP Fastboot Flash Mode (S)
41.18 (sha-99084d5, 2014-10-29 23:54:18)
Noticed the version? It was 2014-10-29, that's a very recent version. I think the bootloader got updated, I didn't think that was possible. Maybe this is causing the flickering's and the line? I saw other articles about this problem, but all of them only talked about recovery mode, and didn't give much detail. I hope someone finds a fix for this. Thanks for reading!
Click to expand...
Click to collapse
I downgrade to cm11 snapshot 6 stable, it worked one time always with this line which disappears after unlocking and then I had a sim card issue and force close com.android.systemui. Phone unusable, solution please

moumss52 said:
I downgrade to cm11 snapshot 6 stable, it worked one time always with this line which disappears after unlocking and then I had a sim card issue and force close com.android.systemui. Phone unusable, solution please
Click to expand...
Click to collapse
Factory reset, or update to a later version. If you restored a backup from a stock ROM, its probably why. I suggest you backup from adb then restore it to cyanogen mod.
Sent from my Moto G using XDA Free mobile app

MetalPhoenix45 said:
Factory reset, or update to a later version. If you restored a backup from a stock ROM, its probably why. I suggest you backup from adb then restore it to cyanogen mod.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
I handed the rom stock kitkat, it works but I still have this line in the recovery, in the boot and in the rom which disappears after lock screen. For now no other bug, I stay in rom stock some time to see if bugs appear.
I'm french, sorry if my english sucks!

The line is caused by the Kernel you are using not being compatible with the current Bootloader on your phone.
The problem will hopefully be solved by custom Kernels in the [near] future. If you absolutely can not wait, flash Lollipop Bootloader and Stock Lollipop, Motorola or GPE.

lost101 said:
The line is caused by the Kernel you are using not being compatible with the current Bootloader on your phone.
The problem will hopefully be solved by custom Kernels in the [near] future. If you absolutely can not wait, flash Lollipop Bootloader and Stock Lollipop, Motorola or GPE.
Click to expand...
Click to collapse
I am using CyanogenMod's stock kernel, I hope cyanogen looks into this in the future. But your answer doesn't make sense for recovery mode, unless recovery mode uses a kernel. Why does the line disappear after turning off and on then?
Sent from my Moto G using XDA Free mobile app

MetalPhoenix45 said:
I am using CyanogenMod's stock kernel, I hope cyanogen looks into this in the future. But your answer doesn't make sense for recovery mode, unless recovery mode uses a kernel. Why does the line disappear after turning off and on then?
Click to expand...
Click to collapse
Recoveries are also affected, because they are not fully compatible with the new Bootloader.

No Custom Roms in GPE 5.0.1
How did you install Cyanogenmod and other Custom Roms ? Because when I try to install them I get an error. I tried it with Philz Touch and TWRP. Of course I have made a full wipe. I'm running 5.0.1 GPE on my XT1032 Moto G. I used this thread to install GPE : http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847 . And here is a photo of the error in Philz Touch.
Sorry for my bad english.

Philz Recovery is no longer in development.
TWRP support for Lollipop is being worked on. More here.

Cameo164 said:
How did you install Cyanogenmod and other Custom Roms ? Because when I try to install them I get an error. I tried it with Philz Touch and TWRP. Of course I have made a full wipe. I'm running 5.0.1 GPE on my XT1032 Moto G. I used this thread to install GPE : http://forum.xda-developers.com/moto-g/general/gpe-ota-lrx21z-5-0-1-xt1033-xt1032-t2969847 . And here is a photo of the error in Philz Touch.
Sorry for my bad english.
Click to expand...
Click to collapse
I never saw this error before, I will search Google for it. But can you give me a screenshot of what it says on TWRP, because I'm more used to that. Thanks.
Sent from my Moto G using XDA Free mobile app

Of course here it is. I did a full wipe.
Sent from my XT1032 using XDA Free mobile app

This has been a known issue since the first unofficial CM12 builds; current kernel is not compatible with new bootloader (41.18), the issue won't be fixed until Motorola releases the kernel source code, so people can see where the problem is and fix it in custom roms or custom kernels.
To fix it you can:
a) follow a guide here in the forum to downgrade from 5.0.1 GPE to 4.4.4 GPE, then to 4.4.4 Motorola and then updating to 5.0.2 OTA (some people had the flickering fixed this way)
b) Wait for the full Motorola 5.0.2 firmware, wipe everithing and flash it
c) wait for the kernel source release, so someone can debug and fix that and then go to a custom ROM like CM12

Ok thank you for your helping. And when I downgrade to 4.4.4 Stock Motorola can I install custom roms ? Or does lollipop changed everything and I really have to wait till Motorola releases the codes. And I read many threads from people who hard bricked there moto g when they tried to downgrade. Is there a " safe " instruction.

Cameo164 said:
Ok thank you for your helping. And when I downgrade to 4.4.4 Stock Motorola can I install custom roms ? Or does lollipop changed everything and I really have to wait till Motorola releases the codes. And I read many threads from people who hard bricked there moto g when they tried to downgrade. Is there a " safe " instruction.
Click to expand...
Click to collapse
I have bootloader 41.18, if you read my post you would know that. It actually has nothing to do with bootloader. TWRP couldn't mount system. You could fix by changing file system to EXT4.
Sent from my Moto G using XDA Free mobile app

moralesnery said:
This has been a known issue since the first unofficial CM12 builds; current kernel is not compatible with new bootloader (41.18), the issue won't be fixed until Motorola releases the kernel source code, so people can see where the problem is and fix it in custom roms or custom kernels.
To fix it you can:
a) follow a guide here in the forum to downgrade from 5.0.1 GPE to 4.4.4 GPE, then to 4.4.4 Motorola and then updating to 5.0.2 OTA (some people had the flickering fixed this way)
b) Wait for the full Motorola 5.0.2 firmware, wipe everithing and flash it
c) wait for the kernel source release, so someone can debug and fix that and then go to a custom ROM like CM12
Click to expand...
Click to collapse
This could possibly fix the screen issue?
Sent from my Moto G using XDA Free mobile app

MetalPhoenix45 said:
I have bootloader 41.18, if you read my post you would know that. It actually has nothing to do with bootloader. TWRP couldn't mount system. You could fix by changing file system to EXT4.
Sent from my Moto G using XDA Free mobile app
Click to expand...
Click to collapse
My file system is already ext4 so I don't understand the problem why TWRP can't mount the system partition.

Cameo164 said:
My file system is already ext4 so I don't understand the problem why TWRP can't mount the system partition.
Click to expand...
Click to collapse
Install the TWRP app from playstore and then go to install recovery and install the latest version available.
Sent from my Moto G using XDA Free mobile app

Cameo164 said:
My file system is already ext4 so I don't understand the problem why TWRP can't mount the system partition.
Click to expand...
Click to collapse
Maybe try and do a factory reset through fastboot?
Sent from my Moto G using XDA Free mobile app

No cellular service because radio is off?

I'm not sure what exactly caused it but about a week ago I lost cell service on my xt1032. When I dial *#*#4636#*#* it says the radio is off and the turn radio on button doesn't do anything. Wifi and GPS are working fine. Around that time I had updated the bootloader to 41.18 so that I could flash cm12.1 nightlies, erased modemst1 and modemst2 in fastboot, and flashed cm12.1. I had com.android.phone crashes like a few others did which they resolved by flashing backups.
I have tried to fix it by clean flashing cm12.1, flashing the latest XT1032_GPE_3112.97.00R radio, and clean flashing an old cm12 nightly but the radio remains off.
Any ideas?

I'm having the same issue. Dit you find a solution?

Have either of you tried flashing stock firmware?
Sent from my XT1031

ATTACK said:
Have either of you tried flashing stock firmware?
Sent from my XT1031
Click to expand...
Click to collapse
Yes. But I will do it again, just to see if I get any further.
Do you think I need to flash stock recovery also?

BiggyB99 said:
Yes. But I will do it again, just to see if I get any further.
Do you think I need to flash stock recovery also?
Click to expand...
Click to collapse
I wouldn't think so, but I suggest flashing the entire firmware.
Sent from my XT1031

ATTACK said:
I wouldn't think so, but I suggest flashing the entire firmware.
Sent from my XT1031
Click to expand...
Click to collapse
Thank you for your reply's. I'm now flashing stock rom from here (http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-lollipop-rom-t3017510). Let you know in a sec
edit: still nothing Flashed the stock rom, wiped dalvik cache after. Rebooted a couple of times, but nothing seems to work.
Any other ideas?
edit2: Tried the optimized 'stock' rom, no success either. Also, I ruled out a SIM failure before, just did it agian because this is making me crazy!

Don't flash a ROM, flash the stock firmware.
http://motofirmware.center/files/category/9-moto-g-1st-generation/
Sent from my XT1031

ATTACK said:
Don't flash a ROM, flash the stock firmware.
http://motofirmware.center/files/category/9-moto-g-1st-generation/
Sent from my XT1031
Click to expand...
Click to collapse
Searching for the smiley that hits a hammer into his head. Sorry for my noobness! Flashing the firmware now.
edit: hanging on (bootloader) Preflash validation failed . Search xda learns me that that means the bootloader is locked, but the message says it is unlocked. I'll just go ahead and search some more
edit2: trying the bootloader unlocking procedure learns me that the bootloader is already unlocked: (bootloader) Device already unlocked!
What can I do next. (btw, the error comes on step 2 of the guide, where I put in: mfastboot flash motoboot motoboot.img. Everything else comes woth an OKAY. (http://forum.xda-developers.com/showthread.php?t=2542219)

You don't need a unlocked bootloader to flash stock firmware.
Use fastboot to flash the firmware. Extract the contents to your fastboot folder and double click on the flash-all.bat (or whatever its named).
Sent from my XT1031

ATTACK said:
You don't need a unlocked bootloader to flash stock firmware.
Use fastboot to flash the firmware. Extract the contents to your fastboot folder and double click on the flash-all.bat (or whatever its named).
Sent from my XT1031
Click to expand...
Click to collapse
I do not have a flash-all.bat (or something in that way) in my folder. Downloaded the firmware from the site you gave, the mfastboot from the Guide (http://forum.xda-developers.com/showthread.php?t=2542219) and I runned the commando's named there (for a xml.zip file).
edit: could it be that my bootloader is newer than the stock firmware is expecting? Running 41.18 now...
edit2: WORKED! I just kept trying to flash the stock firmware, error kept the same. Tried another recovery, did the flashing again but skipped the recovery step (error with bootloader still came up). After that I booted, and it worked! Sticking with stock 4.4.4 for now
Thanks for the help!
edit3: Working on 5.0.1 (stock) Did the OTA, failed because of my custom recovery. Flashed stock recovery, did OTA again --> works like a charm

Awesome!
Sent from my XT1031