Database Develop

[Q] Possible Brick - Need Help

Hi people.
One week ago I bought my phone. Unlocked bootloader and rooted my device. I was running stock 4.4.4, from Personal - Argentina.
Today I was messing with Titanium BackUp and used the feature "integrate updates" wich made apps like google play, hangouts and Motorola Modality Services to crash repeatedly. I read that I needed to restore to the stock rom...
I couldnt find any file from the 4.4.4 so I decided to get back to 4.4.2, found on sbf.droid-developers
I followed this tutorial mark.cdmaforumscom/MotoX-ReturnToStock html step by step and now my phone is almost dead.
When I turn my phone, it shows the boot screen (the unlocked bootloader message), then the motorola animation and then goes black.
I can reboot into fastboot but cant enter into the recovery mode (when I enter into recovery appears the stock recovery image but no text or option)
Can you guys help me with this problem? Is there a way to save my phone?
Thanks in advance. If you need more info just ask

luizdf said:
Hi people.
One week ago I bought my phone. Unlocked bootloader and rooted my device. I was running stock 4.4.4, from Personal - Argentina.
Today I was messing with Titanium BackUp and used the feature "integrate updates" wich made apps like google play, hangouts and Motorola Modality Services to crash repeatedly. I read that I needed to restore to the stock rom...
I couldnt find any file from the 4.4.4 so I decided to get back to 4.4.2, found on sbf.droid-developers
I followed this tutorial mark.cdmaforumscom/MotoX-ReturnToStock html step by step and now my phone is almost dead.
When I turn my phone, it shows the boot screen (the unlocked bootloader message), then the motorola animation and then goes black.
I can reboot into fastboot but cant enter into the recovery mode (when I enter into recovery appears the stock recovery image but no text or option)
Can you guys help me with this problem? Is there a way to save my phone?
Thanks in advance. If you need more info just ask
Click to expand...
Click to collapse
Dude...this is sad.
You say that you followed @KidJoe 's excellent tutorial, but you missed the BIG ORANGE warning???
"NOTE: If you have Android 4.4.2 or later on your Moto X, do NOT attempt to downgrade the ROM version on your phone! Updated parts included with the 4.4.2 and above prevent successful downgrading to a lower version, causing you to either brick your phone, or set you up to brick later!"
You have very few options at this point. Any attempt to recover is going to leave you with mismatched partitions because you can NOT downgrade motoboot (bootloader) or gpt.bin (partition table).
Why oh why didn't you heed the warning?
Now your only option is to try using the manual method (OPTION 5) to flash everything from the 4.4.2 SBF except gpt.bin (which will leave you in a mismatched, but MAYBE working state) and hope that the 4.4.4 full SBF is released soon. Until then you will have mismatched partitions. And if you successfully flash the 4.4.2 ROM with the mismatched gpt.bin, you have a very good chance of bricking AGAIN if you take the OTA to 4.4.4. Don't do it! Assuming you are even able to get back to 4.4.2 and it works, don't take the OTA. Stay on 4.4.2 until the full 4.4.4 SBF is released....

It was a silly mistake. I didnt paid attention to that line... :/
Fortunately I had the problem solved by following the Moto X > Moto X General > [GUIDE][VIDEO] Moto X - Return to 100% stock (which have different lines for manual flashing)
I guess this is the line responsible for solving the problem:
fastboot oem fb_mode_clear
The system seem to run normally and I already updated again to 4.4.4 (I didnt seen your warning before...). Is there a way to check if everything is ok?
Thank you so much for your answer.

luizdf said:
It was a silly mistake. I didnt paid attention to that line... :/
Fortunately I had the problem solved by following the Moto X > Moto X General > [GUIDE][VIDEO] Moto X - Return to 100% stock (which have different lines for manual flashing)
I guess this is the line responsible for solving the problem:
fastboot oem fb_mode_clear
The system seem to run normally and I already updated again to 4.4.4 (I didnt seen your warning before...). Is there a way to check if everything is ok?
Thank you so much for your answer.
Click to expand...
Click to collapse
You are welcome. It looks like you got lucky. Just beware that the next OTA you accept could leave your device in a semi-bricked state. Keep your fingers crossed that all is well. There is no way to tell until you attempt to take the next OTA that is released (whenever that happens).

[Q] Rooting disables NFC?

I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.

goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
Rooted, and unlocked via NTK here. NFC works fine.

goodfellaslxa said:
I have rooted my N6 via adb, the supersu .bat file, TWRP, and the Nexus Toolkit. No matter what I do, after restoring my N6 and rebooting, I lose the NFC options under settings. If I do a factory reset I regain the options, but when I re-flash root I lose them again. NFC writing programs can't detect NFC ability on my phone, and ztest says I don't have it.
I am running the stock factory image.
NFC works fine before I root. I have rooted every Android device I've had, and never experienced this. Is this an N6 issue, a lollipop issue, or some special circumstance of my own creating?
Has anyone else experienced this?
TIA.
Click to expand...
Click to collapse
what are you using to gain root? the latest supersu should not mess things up. the latest supersu is version 2.37 http://download.chainfire.eu/636/SuperSU/UPDATE-SuperSU-v2.37.zip

I've had no problems at all. I used the wugfresh toolkit over in the development section. Worked flawlessly and was pretty much the easiest root I've ever used. You just click buttons. Lol. Go back to full stock and use that.

I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.

goodfellaslxa said:
I have used Wug's toolkit, and agree it's very easy. I have also tried every other method. I have only flashed the stock rom. Maybe it's something that's loading afterwards? Are any apps known to kill NFC? I literally lose the option to enable NFC (and also Android beam). It's just not there.
My process has been 1. Flash stock rom. 2. Restore from Google. 3. Flash root. Sometime after flashing root (and making sure I still have NFC) it disappears.
Again, I have rooted many phones over the years, and never had this problem. I am going to have to try to diagnose what step exactly causes me to lose NFC. I reflashed yesterday and had NFC, but today it's gone again.
I don't think I'm doing anything out of the ordinary, so I will post IF I find the culprit. I doubt I will be the only one to experience this.
Click to expand...
Click to collapse
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.

simms22 said:
again, ill repeat myself, what file are you using to gain root? if you are using older files, they break things.
Click to expand...
Click to collapse
I used 2.36. I'll try 2.37 to see if it makes a difference.

goodfellaslxa said:
I used 2.36. I'll try 2.37 to see if it makes a difference.
Click to expand...
Click to collapse
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.

simms22 said:
it doesnt matter, 2.36 is still good. the only thing i can tell you is root your phone the right way. you want to fastboot oem unlock the bootloader first, then fastboot flash a custom recovery, then flash the the supersu file via that recovery, then just reboot.
Click to expand...
Click to collapse
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).

jj14 said:
Is there an issue with the following method?
fastboot oem unlock
chainfire's autoroot in stock recovery
Just trying to understand if there is a reason why I should do it a different way. At this time, I don't need custom recovery (all I want root for at the moment is adaway - and that is working fine). I suspect i will end up flashing TWRP in the near future (when I need it).
Click to expand...
Click to collapse
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.

simms22 said:
yes, there very well could be. doing it right is just as easy as using any root toolkit, its a nexus and has the options to do it manually, no hacking. if you have the drivers to your computer installed, it takes about 3-4 minutes.
Click to expand...
Click to collapse
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?

jj14 said:
Till Lollipop, I've always done it the manual way. With lollipop on my N5 and then, on my N6, the sticky's here didn't seem to provide any different method - it was autoroot.
Reading other threads showed that it was either custom kernel with relaxed permissions and supersu, or autoroot, or the toolkit.
I know that chainfire was testing a version of supersu that wouldn't need the modified kernel, but it was still in beta.
So, what method would you have recommended? (which did you use?) SuperSU by itself isn't sufficient (unless you went with the beta). Or is there a different guide/sticky thread that I missed?
Click to expand...
Click to collapse
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.

simms22 said:
i recommend the way i did it, the right way. fastboot oem unlock, fastboot flash a recovery, and flash the latest supersu. what you are reading is now considered old. flashing the new supersu(beta) is all thats needed.
Click to expand...
Click to collapse
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.

jj14 said:
I guess I'll try it when the next update comes along. Get system partition back to stock by flashing appropriate system images, and then using the new supersu.
Click to expand...
Click to collapse
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.

simms22 said:
oh, i almost forgot. the n6 has a new option, before unlocking the bootloader, you have to go to developer settings and enable oem unlock.
Click to expand...
Click to collapse
Thanks
Yeah, I knew that (I already unlocked bootloader and rooted)

Well, after reflashing and not rooting I still lost NFC (though it took several hours and a few reboots before it stopped), so I decided to try not using google restore, and setup as a new device.
After manually reinstalling 300+ apps, reconfiguring everything, and rooting (using 2.37), NFC appears to be working fine. I *think* that some setting that was being restored from previous google backups eventually killed NFC.

I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.

lkevinl said:
I'm not rooted... stock T-Mobile Nexus 6 running a nano SIM from my Droid Maxx on VZW. There are no NFC settings in the Wireless settings section.
I'm not unlocked or rooted... just took the over the air update that came right after the phone first powered up.
Is the nano SIM a factor? What exactly is the difference between the NFC nano SIM and the non-NFC nano SIM? The Droid Maxx has NFC, so I assume that its nano SIM supports NFC. Not sure what's going on here.
Click to expand...
Click to collapse
I think its not a root issue. Did you restore a previous backup, or use the tap-to-import option? I think there is a setting that is being imported that causes this. Try resetting to stock, and when you go through the initial setup don't import a backup. That fixed it for me.

I used the original auto-root, and I still have NFC options available also. (and I never had to enable developer options. I unlocked the bootloader right out of the box).

Hmmm... was hoping to avoid doing the factory reset. I did try to the Tap to Go option but wasn't sure if it did anything. I'm mostly interested in getting my WiFi settings restored. I suspect your right about a restored setting mucking this up. I may have to do the reset anyway because of the other problem I'm having with Facebook that I posted about in an earlier thread.

[Q] [XT1064] Is it possible to convert XT1064 to GPE (Google Play Edition)?

Hello, can someone help me convert my Moto G 2014 XT1064 (US) to the Google Play Edition?
I bought the Moto G on sale at Amazon a few days ago, then remembered why I had put off purchasing it previously, all of the Motorola bloatware!! No Motorola, I don't need an additional backup service, and I don't want your services constantly running and pinging home, and I'd like to get updates in a reasonable amount of time. My device said it was up to date but was still on KitKat, which was very disappointing.
So far I've unlocked my bootloader (via the official Motorola method) and I did successfully upgrade to Lollipop but it was the Motorola version.
These are the packages that I have downloaded:
Blur_Version.21.11.17.titan_retuaws.retuaws.en.US.zip (the motorola 5.0 update?)
Blur_Version.22.11.6.titan_retuaws.retuaws.en.US.zip (small update for motorola android 5)
GPE_XT1032_KOT49H.M004_CFC.xml.zip (stuck at Google screen with unlock icon, waited 30 minutes)
One issue is that it seems like both of the main sites that host the stock images have been down for a few days:
- http://sbf.droid-developers.org/phone.php?device=36 (DOWN as of 12/12)
- http://motofirmware.com/files/category/38-titan/ (DOWN as of 12/12)
I also used the MotoToolAioV3.1 with the GPE_XT1032_KOT49H ROM which resulted in a bootloop, I'm guessing this is for the 1st gen Moto G?
Right now I'm back on Motorola KitKat version 21.11.17.titan_retuaws.retuaws.en.US.
Is there a way to make my Moto G XT1064 stock GPE or should I look for a custom ROM that or should I try CyanogenMod 11?
One thing to note is that I was running on less that 50% battery when trying to flash GPE_XT1032_KOT49H with MotoToolAIO, could this have been an issue or is this only to prevent the battery from dying?
Thanks for the help guys!
P.S. It was not worth it saving $70 to get the on-sale version at Amazon rather than the Google Play Edition. I've not even been able to find out for sure if you can get the 2014 version with GPE, which makes this even more frustrating.
Also, which versions are compatible with each other or are none of them compatible unless stated? Will the 1st gen ROMs work on the 2nd gen phone?

there is no GPE edition for Moto G 2ND GEN.......... and 1st gen ROMS wont work in our phones.. flashing dem results results in a BOOTLOOP

ak88900 said:
there is no GPE edition for Moto G 2ND GEN.......... and 1st gen ROMS wont work in our phones.. flashing dem results results in a BOOTLOOP
Click to expand...
Click to collapse
Thanks, it's really disappointing that I can't have stock Android on a Moto G 2014 and have it somewhat easy to update. When is that going to change Google, come on, it's been the same ROM -> Bootloop -> flash -> brick -> hours of ADB and mfastboot for 5 or 6 years. Having 20 Motorola services phoning home and alerting me to signin to Motorola constantly is inexcusable, and makes this otherwise great phone a LEMON.
Is there a tool or method to strip out all of the Motorola junkware?

eeeee
derekm_ said:
Thanks, it's really disappointing that I can't have stock Android on a Moto G 2014 and have it somewhat easy to update. When is that going to change Google, come on, it's been the same ROM -> Bootloop -> flash -> brick -> hours of ADB and mfastboot for 5 or 6 years. Having 20 Motorola services phoning home and alerting me to signin to Motorola constantly is inexcusable, and makes this otherwise great phone a LEMON.
Is there a tool or method to strip out all of the Motorola junkware?
Edit: I don't understand, we have root, we have an unlocked bootloader, why can't this phone be 100% converted to a GPE phone? What's the technical limitation that's preventing this?
Click to expand...
Click to collapse
yeah all u gotta do is Root->install Titanium Backup->uninstall all unwanted bloatware
GPE---- well the gpe edition dosnt exist--

ak88900 said:
yeah all u gotta do is Root->install Titanium Backup->uninstall all unwanted bloatware
GPE---- well the gpe edition dosnt exist--
Click to expand...
Click to collapse
Oh, sweet, thank you so much!
It probably seems like a "duh" but this tip should be a sticky!
I never once have read somewhere that the Moto G 2014 doesn't have a Google Play Edition. Eventually I suspected that it didn't but only after an hour of flashing and bootloops.
So this is not the 2014 version? https://play.google.com/store/devices/details/Moto_G_Google_Play_edition_8GB?id=moto_g_8gb&hl=en Is the model number of the GPE phone I just linked to XT1032?

.
derekm_ said:
Oh, sweet, thank you so much!
It probably seems like a "duh" but this tip should be a sticky!
I never once have read somewhere that the Moto G 2014 doesn't have a Google Play Edition. Eventually I suspected that it didn't but only after an hour of flashing and bootloops.
So this is not the 2014 version? https://play.google.com/store/devices/details/Moto_G_Google_Play_edition_8GB?id=moto_g_8gb&hl=en What's the model number of the GPE phone I just linked to?
Click to expand...
Click to collapse
A varient of XT1032

Man you must be dumb if you think you can flash the moto g 2013 gpe rom to the 2nd generation moto g. It's like me trying to flash a GS5 or Note 4 ROM on my GS4. It will never work and results in a softbrick or worse. Also quit being so dramatic. This motorola rom is as close to stock android as you are gonna get from an OEM. If you want to get rid of the unintrusive motorola services just root and remove the unwanted apps with titanium backup.

ImperiousRex89 said:
Man you must be dumb if you think you can flash the moto g 2013 gpe rom to the 2nd generation moto g. It's like me trying to flash a GS5 or Note 4 ROM on my GS4. It will never work and results in a softbrick or worse. Also quit being so dramatic. This motorola rom is as close to stock android as you are gonna get from an OEM. If you want to get rid of the unintrusive motorola services just root and remove the unwanted apps with titanium backup.
Click to expand...
Click to collapse
It's certainly not obvious at first glance that there is not a GPE version of the 2014 version of the Moto G.
What's the technical reason that I can't flash the rom on a different device? Hardware driver support? Config files?
Is it really that difficult for Android to support having multiple drivers available for different hardware? Windows does it just fine. Linux does it.
I can't seem to root the XT1064, most people seem to end up in bootloops when trying to and so did I, so no Titanium Backup at the moment.
This is as close to stock as many manufacturers offer?? That's very disappointing.

derekm_ said:
It's certainly not obvious at first glance that there is not a GPE version of the 2014 version of the Moto G.
What's the technical reason that I can't flash the rom on a different device? Hardware driver support? Config files?
Is it really that difficult for Android to support having multiple drivers available for different hardware? Windows does it just fine. Linux does it.
I can't seem to root the XT1064, most people seem to end up in bootloops when trying to and so did I, so no Titanium Backup at the moment.
This is as close to stock as many manufacturers offer?? That's very disappointing.
Click to expand...
Click to collapse
dude try the root kernel(thanks to @savoca) and BETA-SUPERSU-v2.38.zip(http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t2964330) worked for me/
it takes about 10 minutes to boot...........

ak88900 said:
dude try the root kernel(thanks to @savoca) and BETA-SUPERSU-v2.38.zip(http://forum.xda-developers.com/moto-g-2014/general/twrp-twrp-backup-t2964330) worked for me/
it takes about 10 minutes to boot...........
Click to expand...
Click to collapse
Thanks, I'll try that today.
I tried the xt1064_lollipop_boot.img version yesterday with the 2.16, 2.35, 2.38, 2.39 but I might not have waited long enough on some of them (did wait 15+ minutes with 2.16 with no luck).
What screen was it on while booting? Was it ever a completely black screen (with backlight on) for an extended period of time?
What ROM / OS version were you on when you rooted it?

derekm_ said:
Thanks, I'll try that today.
I tried the xt1064_lollipop_boot.img version yesterday with the 2.16, 2.35, 2.38, 2.39 but I might not have waited long enough on some of them (did wait 15+ minutes with 2.16 with no luck).
What screen was it on while booting? Was it ever a completely black screen (with backlight on) for an extended period of time?
What ROM / OS version were you on when you rooted it?
Click to expand...
Click to collapse
i got the bootlogo for over 15mins.. and finally booted up...
i am using XT1068 Dual sim stock lollipop 22.11.16(XT1064 firmware):silly:

ak88900 said:
i got the bootlogo for over 15mins.. and finally booted up...
i am using XT1068 Dual sim stock lollipop 22.11.16(XT1064 firmware):silly:
Click to expand...
Click to collapse
Are you using the stock Lollipop recovery or TWRP?
How do you get into recovery from Lollipop? I've tried all different combinations of power/volume buttons but cannot get past the Broken Android screen.
By "flash SuperSU" does everyone mean using "adb sideload superSU.zip" from recovery?

derekm_ said:
Are you using the stock Lollipop recovery or TWRP?
How do you get into recovery from Lollipop? I've tried all different combinations of power/volume buttons but cannot get past the Broken Android screen.
By "flash SuperSU" does everyone mean using "adb sideload superSU.zip" from recovery?
Click to expand...
Click to collapse
The rom seems to replace the flashed Recovery with the stock..... I flash the recovery every time I want..... :-/
Place the SuperSU.zip(v2.38 beta worked for me). In your INTERNAL memory and boot into recovery(TWRP) flash it..

ak88900 said:
The rom seems to replace the flashed Recovery with the stock one...... I flash the recovery every time I want..... :-/
Place the SuperSU.zip(v2.38 beta worked for me). In your INTERNAL memory and boot into recovery(TWRP) flash it..
Click to expand...
Click to collapse
I pushed SuperSU 2.38 to /data/local/tmp/ because that's the only place that I could write to as far as I know.
I booted into recovery and installed SuperSU then rebooted (I didn't clear any cache manually).
The phone is on the Warning Bootloader Ulocked screen and rebooting. I'll let it sit for about 20 minutes and see if anything good happens. Thanks for the assistance.
Edit: is mine on the wrong screen? You said yours stayed on the "bootlogo", is that the Motorola splash screen or the "Warning Bootloader Unlocked" screen?
Edit: IT WORKED! Thank you!!
Edit: Looks like it's bootlooping after reboot.

derekm_ said:
I pushed SuperSU 2.38 to /data/local/tmp/ because that's the only place that I could write to as far as I know.
I booted into recovery and installed SuperSU then rebooted (I didn't clear any cache manually).
The phone is on the Warning Bootloader Ulocked screen and rebooting. I'll let it sit for about 20 minutes and see if anything good happens. Thanks for the assistance.
Edit: is mine on the wrong screen? You said yours stayed on the "bootlogo", is that the Motorola splash screen or the "Warning Bootloader Unlocked" screen?
Edit: IT WORKED! Thank you!!
Edit: Looks like it's bootlooping after reboot.
Click to expand...
Click to collapse
Yeah it bootloops at every reboot..... But eventually it'll boot up..... Hope someone comesup with a more stable rooting method

[Q] Wifi not turning on after flashing Lollipop Root

So just to summarize what I've done so far, I have a Moto G (2014) which has been updated to Lollipop through normal means. I started off following this guide: http://forum.xda-developers.com/moto-g-2014/general/xt1063-t3018818/page12
The guide then lead me to this one, as my model is XT1064, a Moto G from Windmobile. I had no issues unlocking my bootloader. http://forum.xda-developers.com/moto-g-2014/development/xt1064-lollipop-root-t2938051
With the guide above, after I flashed that file, my wifi would not turn on. Every time I pressed the toggle, it would immediately switch back to off. I then flashed the TWRP Recovery, and used that to finally root my device with SuperSU.
I checked my root, and my device is confirmed to be rooted, but the wifi is still not working. I looked around a little, and found this: http://forum.xda-developers.com/moto-g-2014/general/guide-lollipop-xt1064-north-edition-t2955076
The problem with the guide above is that its for a phone that was kitkat, while my phone is already lollipop. The guide does mention the wireless issue though, so I was thinking of trying out the steps outlined in that guide, also using that file (though that file is for 4.4).
Would this work? Or is the safer bet finding an 5.0.1 stock rom, and flashing back to that?
Edit: I found a link to a 5.0.2 stock rom (which is the version my phone currently is) I think downloading that and using that to fix the modem files is the better thing to do. (link: http://www.filefactory.com/file/53c1pepzp9cp/RETCA_XT1064_5.0.2_LXB22.99-24.2_cid14_CFC.xml.zip)
Thanks for all and any help.

I recommend flashing the stock images, that will almost certainly fix your issue with Wifi.

Moto X always boots into recovery unless I manually choose normal startup each time

I rooted my XT1052 straight after updating to 5.1, a few years back. As a result I have never been able to install the OTA update (the one which fixed Stagefright, so far as I'm aware it's the only OTA Moto did after the 5.1 update.)
I've been unable to install a few apps recently due to SafetyCheck failing on the rooted phone, so yesterday I decided I would unroot and return to stock, which would also enable me to install the bugfix OTA. (And with Magisk, nowadays we can keep root access without a modified system partition.)
I didn't have a stock image (or I had an image of some sort on a hard drive but couldn't remember its provenance). Moto's download page has images for the XT1053 but not the XT1052… Eventually I found firmware.center, where (I thought) I found the right image.
However, when flashed it (following the step-by-step guides which are the same on various pages, including Moto's own instructions), it failed to flash the `system` image. I got messages about invalid block sizes (IIRC) and then an error saying the image was corrupt (it wasn't; I checked the MD5).
This left me unable to boot. So I downloaded LineageOS (I'd been considering switching to LineageOS anyway to get Android 6), and was able to flash it from TWRP without any issues (other than the fact that a newer version of TWRP is required than the one published on their website…)
All well and good – except that now, when I turn my phone on it goes straight into Recovery (TWRP). Initially I could only get System to boot by starting the bootloader (Pwr+VolDn) and selecting 'BP Tools', which would cause it to boot normally. (I found this by trial and error.) Now, after re-flashing the boot image, It also works if I select Standard Boot from the bootloader. But I still have to select it manually. If I just turn the phone on normally, with the power button, it always boots into Recovery. Also, all the 'reboot' options from fastboot/adb or TWRP all boot to Recovery.
Now, I think I know what I did wrong. The stock image I downloaded was 'XT1052_GHOST_RETGB_5.1_LPAS23.12-15.5-1_cid7_CFC.xml.zip', but my system version before was 5.1_LPA23.12-15.5. I just assumed that the 5.1_LPAS23.12-15.5-1 version was a minor update – likely with the Stagefright OTA installed – so I went for that. But probably I should have gone for the exact version I already had installed.
Searching these forums and the wider web, I haven't found anyone with the exact same issue. But from similar issues, I decided I needed to re-flash the partition table (gpt.bin). I took the gpt.bin image from an older 5.1 ghost ROM I had saved, but I'm not able to flash it – the bootloader shows security warnings when I try.
So I'm stuck now – I have tried pretty much everything I can think of.
If anyone has any ideas I'd be very grateful!

I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?

Alexjrbr said:
I have the same problem, my moto x only boot in recovery mode.
Did you get any solutions?
Click to expand...
Click to collapse
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.

cmjs said:
No :'(
I think our phone is old enough now that not enough people use it any more to find solutions to problems like these.
It's sad, I don't want to upgrade, I've never seen a phone I like as much as my Moto X.
Click to expand...
Click to collapse
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done

Alexjrbr said:
I found a solution!
I did mine and now it's all right! I'll post here explaining how it should be done
Click to expand...
Click to collapse
Woohoo! Well done!
Look forward to seeing your solution

cmjs said:
Woohoo! Well done!
Look forward to seeing your solution
Click to expand...
Click to collapse
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644

Moto X 2014 XT1092
Alexjrbr said:
https://forum.xda-developers.com/moto-x/general/guide-fix-moto-x-boots-recovery-t3699644
Click to expand...
Click to collapse
Can this solution be used in my case. I have the same problem of the phone booting to recovery on start up...