Database Users

[XT1033][Mixed-Firmware]Convert Moto G into Google Play Edition(GPe)[NoobFriendly]

DISCLAIMER:
What you do with Your Device is Your Responsibility!
I am not responsible for anything that happens to your device.
I'll try to help you solve the problem, if I can!
I wanted to change my XT1033 into GPe, and well procedure isn't that hard, but it required installing two firmwares one over the other that is
GB first and then selective flashing of GPe. And as i frequently change between GPE, GB, AsiaRetail. I made custom scripts for each one of them. I also Mixed the firmware of GPe and GB to make one single firmware which can be directly flashed over XT1033 using one single bat to convert GPe.
I am lending the major part of work from @ffosilva who in turn gives credit to @oldblue910 on thread
[FASTBOOT] Google Play Edition images (semi-official)
I know similar threads already exist, I am starting a new one with the aim of keeping the thread Noob-Friendly, And provide a single download to convert into GPe. I am also adding the package to change the Unlocked bootloader logo to GPe version. and providing a bat script to make it easier for newbies!​Downloads
You can download the Mixed-Firmware From:
1.Here (GDrive)
2.Here (progammingnerds.com) by @tanmay190
Mirrors Needed!
Pre-Requisite: Installed Motorola Drivers.
Instructions:
Download the Package and Extract it to a folder
Reboot the phone into Bootloader (Power+VolumeDown).
Double Click XT1033_to_GPe.bat to begin
OR
Run Following commands from the Command Prompt after cd-ing to the folder, one by one
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot reboot-bootloader
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img
mfastboot flash fsg fsg_intl.img
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot erase cache
mfastboot erase userdata
Reboot into system to be booted into GPe version.
And there you have it the XT1033 converted to Moto G GPe.
Quick Useful Links/Tips:
CWM for GPe
Philz Recovery for GPe
Command to flash a recovery "fastboot flash recovery filename.img" (without quotes) where filename.img is the filename (It has to be in the same folder) of the recovery image that you are flashing. To go back to stock recovery you can find the recovery.img from the download package above and flash using the same command!
If you use CWM/Philz, when you exit the recovery while phone is unrooted, It will ask you that your phone is not rooted, Install su? You c5. an select yes to root your phone. and later install SuperSU from Play Store.
SuperSU flashable zip if you Think flashing SuperSU directly is better! I find the above method a lot faster!
If anything goes wrong, Use This Guide to Get Back to Stock
[Stock][Firmware Package][XT1033] Asia Retail - Alt. Link [4.4.2][Lock Bootloader]
Any Mirrors to Download Links are welcome.
Hit Thanks if it helps!​

Thanks. What is the purpose of fsg partition?
Sent from my XT1033 using Tapatalk

Dual SIM?
Sent from my Moto G using XDA Free mobile app

I dont know, do you know if it is related to dualsim? Lets say we converted a xt1033 into gpe with this and get one sim working. Can we flash stock based xt1032 custom roms on this gpe rom ? Gpe roms use ext4 filesystem whereas motorola roms use f2fs.
Lets say I want to keep f2fs file system and get one sim working with stock based xt1032 custom roms. What should i do ?
Sent from my XT1033 using Tapatalk

Convert it to GB
Semseddin said:
I dont know, do you know if it is related to dualsim? Lets say we converted a xt1033 into gpe with this and get one sim working. Can we flash stock based xt1032 custom roms on this gpe rom ? Gpe roms use ext4 filesystem whereas motorola roms use f2fs.
Lets say I want to keep f2fs file system and get one sim working with stock based xt1032 custom roms. What should i do ?
Sent from my XT1033 using Tapatalk
Click to expand...
Click to collapse
Flash a full GB firmware, you will get a single sim working! and you will also have a f2fs!

I could install this rom but recovery does not recognize the sd card.
I can't install any thing.
How can I fix this problem?

i don't know if it's just my mobile , but when i use single sim rom ( i mean xt1032/gpe rom ) audio in real racing 3 and nfs most wanted gets laggy , and sometimes audio repeat itself for every 3-4 seconds . gameloft games are fine tho . i tried replacing xt1032's "audio.primary.msm8226.so"
file with xt1032's "audio.primary.msm8226.so" but i lost sound completely .

Well
mobilephone01 said:
I could install this rom but recovery does not recognize the sd card.
I can't install any thing.
How can I fix this problem?
Click to expand...
Click to collapse
flash latest philz recovery or flash gpe specific recovery,anyway you'll get encryption error on custom roms
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon_gpe

rr46000 said:
flash latest philz recovery or flash gpe specific recovery,anyway you'll get encryption error on custom roms
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/falcon_gpe
Click to expand...
Click to collapse
I'm using latest philz recover.
If the same thing happen when I install the custom rom. I'll wait till you fix this problem.
Thank you.

Changed the method, Foolproof this time!
mobilephone01 said:
I'm using latest philz recover.
If the same thing happen when I install the custom rom. I'll wait till you fix this problem.
Thank you.
Click to expand...
Click to collapse
Changed the method, Foolproof this time!
Sorry had to change the files in downloads as well!
I found another thread with a similar concept but a better implementation, I am borrowing the files from them and just adding a couple things!
But it should work now!

And again, I already did this here.

thelegendofzeth said:
And again, I already did this here.
Click to expand...
Click to collapse
And again two people said they didnt understand!
I wrote in description the aim is to make it noob friendly!
And its not like your original work! I'd probably take that comment from @ffosilva

mfastboot.exe crash and can't install. Please fix it.

mobilephone01 said:
mfastboot.exe crash and can't install. Please fix it.
Click to expand...
Click to collapse
Right on it!
EDIT: Crash fixed, it was a command issued when bootloader was offline, ideally it should've waited, but i dont know whats wrong. I paused the script for a while It is working fine now!
Download the mfastboot+logo_bin.zip again!

mfastboot does not crash but still does not work.
Maybe not install all GPe file? Finishes very quick and still remain previous rom.
Do I have to download GPe file?

mobilephone01 said:
mfastboot does not crash but still does not work.
Maybe not install all GPe file? Finishes very quick and still remain previous rom.
Do I have to download GPe file?
Click to expand...
Click to collapse
You have to download two files! 1. Mixed-Firmware 2.mfastboot+logo_bin.zip

deej_roamer said:
You have to download two files! 1. Mixed-Firmware 2.mfastboot+logo_bin.zip
Click to expand...
Click to collapse
You changed the both files?

mobilephone01 said:
You changed the both files?
Click to expand...
Click to collapse
The first file was fine! There was no fault with the firmware. It was a scripting problem on my side, I've changed only the script

deej_roamer said:
Right on it!
EDIT: Crash fixed, it was a command issued when bootloader was offline, ideally it should've waited, but i dont know whats wrong. I paused the script for a while It is working fine now!
Download the mfastboot+logo_bin.zip again!
Click to expand...
Click to collapse
On some systems mfastboot crashes after the reboot command The best work around is to add "mfastboot continue" after the reboot command in the bat script

deej_roamer said:
The first file was fine! There was no fault with the firmware. It was a scripting problem on my side, I've changed only the script
Click to expand...
Click to collapse
I could not install. It was finished 1 second for install after click XT1033_to_GPe.bat. Is it normal?
Booting previous rom. Nothing changed.

[OTA ZIP] Moto X (2014) XT1092 5.0

Hi all,
Just got the notification to update my french Moto X (2014) XT1092.
Here is the link
LINK
Just flash it via stock recovery.
WARNING : The update will only succeed if you have a RETEUALL or RETIN XT1092 (it won't work for RETGB and RETDE) AND an untouched sytem (no root, xposed, or removed system apps...)
If you have a RETGB or RETDE, no worries you'll just need to convert your phone into a RETEUALL.
Here is how to do this :
1) You'll need an unlocked bootloader, as well as fastboot and adb drivers installed on your computer.
2) First you'll need to download the RETEUALL factory image : here and extract it.
3) Then you'll need to execute each command in a terminal window
Code:
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
4) After that you'll be able to take the OTA

benfiller said:
Hi all,
Just got the notification to update my french Moto X (2014) XT1092.
Here is the link
LINK
Will post screenshots as soon as the OTA finishes
Edit : OTA finished
Click to expand...
Click to collapse
I am getting below mentioned error
<Error>
<Code>ExpiredToken</Code>
<Message>The provided token has expired.</Message>
<Details>Request has expired: 1418383039</Details>
</Error>

Is it the same as the UK version?
Mine says retgb instead of reteu.
Sent from my XT1092 using Tapatalk

Cheers for this, but it looks like the link is down?

I got the file,
but once I try to sideload, it complaints that the fingerprint is not the same.

Yeah, the link is expired. I will mirror it as soon as I can !
You must have a completely untouched (no root, no xposed, no removed system apps etc...) system to pass the OTA.

mcnovy said:
I got the file,
but once I try to sideload, it complaints that the fingerprint is not the same.
Click to expand...
Click to collapse
what's your version retin reteu ????

nandroidz said:
what's your version retin reteu ????
Click to expand...
Click to collapse
21.21.45.victara_retde.retdeall.en.DE.retde
bought in Germany

i think its bcos urs is retde.retdeall

benfiller said:
Yeah, the link is expired. I will mirror it as soon as I can !
You must have a completely untouched (no root, no xposed, no removed system apps etc...) system to pass the OTA.
Click to expand...
Click to collapse
Are these steps the enough to revert the change or do I have to factory reset (I am asking because as far as I know Motorola haven't released factory images for variants other than XT1095)?
1) uninstall xposed through the app then remove the app itself with other modules.
2) completely remove root through SuperSu (Full unroot option).
3) restore stock recovery (link please if possible?)
4) I didn't add or remove system apps other than SuperSu
Thanks,

hasm_747 said:
Are these steps the enough to revert the change or do I have to factory reset (I am asking because as far as I know Motorola haven't released factory images for variants other than XT1095)?
1) uninstall xposed through the app then remove the app itself with other modules.
2) completely remove root through SuperSu (Full unroot option).
3) restore stock recovery (link please if possible?)
4) I didn't add or remove system apps other than SuperSu
Thanks,
Click to expand...
Click to collapse
I'll upload a twrp backup of my stock untouched 4.4.4 system+boot

hey thanks a lot for the link. Its working on my Moto X XT1092 indian version.

benfiller said:
I'll upload a twrp backup of my stock untouched 4.4.4 system+boot
Click to expand...
Click to collapse
Thanks mate,
So after flashing this backup. Do I have to restore the stock recovery or is that not required for the update?

hasm_747 said:
Thanks mate,
So after flashing this backup. Do I have to restore the stock recovery or is that not required for the update?
Click to expand...
Click to collapse
Yes, you'll need stock recovery to do the update.
I'll post it to with the twrp backup

New link is up, check the OP

benfiller said:
New link is up, check the OP
Click to expand...
Click to collapse
Doesn't work for me
Sent from my XT1092 using XDA Free mobile app

undeadadd said:
Doesn't work for me
Sent from my XT1092 using XDA Free mobile app
Click to expand...
Click to collapse
OTA or link ? The link works fine for me, either on phone or computer

benfiller said:
OTA or link ? The link works fine for me, either on phone or computer
Click to expand...
Click to collapse
The links not working on my phone lol
Sent from my XT1092 using XDA Free mobile app

undeadadd said:
The links not working on my phone lol
Sent from my XT1092 using XDA Free mobile app
Click to expand...
Click to collapse
Weird, what does it say ?

benfiller said:
Weird, what does it say ?
Click to expand...
Click to collapse
<Error>
<Code>ExpiredToken</Code>
<Message>The provided token has expired.</Message>
<Details>Request has expired: 1418383039</Details>
</Error>
Sent from my XT1092 using XDA Free mobile app

[Guide] [XT1095] [5.1] Upgrade from 23.11.14 to 23.16.3

DO NOT RESTORE BACK TO 4.4. THIS WILL BRICK YOUR PHONE.
--UPDATE--
JUST FLASH THIS! (In stock recovery) https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view
--
(if the above doesn't work, or if you are not on totally stock, use the following method)
Here is how to upgrade from 23.11.14 to 23.16.3
What you need: https://yadi.sk/d/cBaKACE7hQH9Y (upgrade from stock 5.0 to 23.16.3)
http://www.graffixnyc.com/motox.php (stock 5.0 image. You need to use this one. The one found in Motorola's site WILL NOT WORK WITH THIS METHOD)
Unzip the stock 5.0 image
Boot into fastboot
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
Boot into recovery
adb sideload Blur_Version.22.21.11.victara_tmo.tmo.en.US.zip
reboot!

can i only update via adb sideload ? from 23.11.14 to 23.16.3 ?? without back to stock 5.0 ?

Grzesiek1010 said:
can i only update via adb sideload ? from 23.11.14 to 23.16.3 ?? without back to stock 5.0 ?
Click to expand...
Click to collapse
if you're on 23.11.14 you have to go back to 5.0 in order to update to the newest 5.1 (23.16.3).
You can also copy the zip over and flash within recovery, if you prefer. I always think sideload is easier (though actually, now that I think about it, I copied it over and flashed from within recovery myself...)

bongostl said:
if you're on 23.11.14 you have to go back to 5.0 in order to update to the newest 5.1 (23.16.3).
You can also copy the zip over and flash within recovery, if you prefer. I always think sideload is easier (though actually, now that I think about it, I copied it over and flashed from within recovery myself...)
Click to expand...
Click to collapse
ok but what with all apps data setting ?

Grzesiek1010 said:
ok but what with all apps data setting ?
Click to expand...
Click to collapse
you have to do a full wipe.
if you're rooted, you could do a titanium backup, etc...

bongostl said:
you have to do a full wipe.
if you're rooted, you could do a titanium backup, etc...
Click to expand...
Click to collapse
better wait for official update too much risk lost data ...

I successfully downgraded to 5.0, and I've attempted the sideload method twice and failed. Each time it says there is an error in the package, status 7. I get the same result when I apply update from sd card. Any ideas?
---------- Post added at 12:25 PM ---------- Previous post was at 11:43 AM ----------
Be advised: some of us are discovering you can't do the OTA to 23.16.3 if you are on 5.0 46_11.11. Apparently you need to be on 5.0 46_11.10.

Use the files I posted.... That's what I used

It's necessary to downgrade to 5.0, even if I'm getting an OTA system update popup from 23.11.14?

leffer said:
It's necessary to downgrade to 5.0, even if I'm getting an OTA system update popup from 23.11.14?
Click to expand...
Click to collapse
If you're on 23.11.14 and you're getting the OTA alert for 23.16.3, then no you don't have to downgrade. Just take the OTA. You should try to capture the OTA if you're rooted

sivarticus85 said:
If you're on 23.11.14 and you're getting the OTA alert for 23.16.3, then no you don't have to downgrade. Just take the OTA. You should try to capture the OTA if you're rooted
Click to expand...
Click to collapse
I am rooted... How do I capture the OTA?
Sent from my XT1095 using XDA Forums

leffer said:
I am rooted... How do I capture the OTA?
Sent from my XT1095 using XDA Forums
Click to expand...
Click to collapse
The OTA is downloaded to the /cache folder. Copy it from your phone to a computer. Can you take a screenshot of the OTA alert?

Success!
Stanleywinthrop said:
Be advised: some of us are discovering you can't do the OTA to 23.16.3 if you are on 5.0 46_11.11. Apparently you need to be on 5.0 46_11.10.
Click to expand...
Click to collapse
I had this problem initially as well because I downgraded to 5.0 using the official Motorola 5.0 firmware downloaded from the Motorola website, which is apparently 46-11.11.
I had to use this one-day-older version instead, which is apparently 46-11.10: TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip. I found it and downloaded it from here: http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
So... I downloaded the firmware from that link, followed the OP instructions almost exactly*, and I was able to upgrade from 23.11.14 to 23.16.3 successfully.
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.

thenestor said:
I had this problem initially as well because I downgraded to 5.0 using the official Motorola 5.0 firmware downloaded from the Motorola website, which is apparently 46-11.11.
I had to use this one-day-older version instead, which is apparently 46-11.10: TMO_XT1095_5.0_LXE22.46-11_cid9_CFC.xml.zip. I found it and downloaded it from here: http://motofirmware.center/files/file/76-tmo_xt1095_50_lxe2246-11_cid9_cfcxmlzip/
So... I downloaded the firmware from that link, followed the OP instructions almost exactly*, and I was able to upgrade from 23.11.14 to 23.16.3 successfully.
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
Click to expand...
Click to collapse
thanks for your help. I tried to download from your link and for some reason the file will not extract. However, I noticed that your image file is named exactly as the image file linked in the OP to this thread. Are they one in the same?

sivarticus85 said:
The OTA is downloaded to the /cache folder. Copy it from your phone to a computer. Can you take a screenshot of the OTA alert?
Click to expand...
Click to collapse
Here is my current version... http://imgur.com/ae2O6PW
Here is my OTA notification... http://imgur.com/hZZB0DZ
The file name is Blur_Version.23.11.14.victara_tmo.tmo.en.US.zip - is that weird?
Here is a link to the file: https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view?usp=sharing
File Size: 163.7MB
MD5: d8c44d25d0479ef40ad5f092ff7ffd39
I'm sure this upload is gonna get flagged in no time on Google Drive... So somebody else should upload it if possible.

And...success finally. FYI you cannot use the method found in the OP to update the stock 5.0 image from motorola's website. You MUST use the stock image found in the OP.

thenestor said:
* One change I had to make from OP instructions: The pieces of system image had an extra period before the piece number, so I needed to retype those commands like this: fastboot flash system system.img_sparsechunk.0 ...etc.
Click to expand...
Click to collapse
Good catch! I have fixed the original post

Stanleywinthrop said:
And...success finally. FYI you cannot use the method found in the OP to update the stock 5.0 image from motorola's website. You MUST use the stock image found in the OP.
Click to expand...
Click to collapse
I've updated the original post to make this clearer.

anyone able to root this new OTA?
CF auto root was working on every previous OTA from 4.4 to 5.0 and 5.1 but now causes boot loops. I am able to TWRP back to the unrooted build to get me out of the bootloops.

leffer said:
Here is my current version... http://imgur.com/ae2O6PW
Here is my OTA notification... http://imgur.com/hZZB0DZ
The file name is Blur_Version.23.11.14.victara_tmo.tmo.en.US.zip - is that weird?
Here is a link to the file: https://drive.google.com/file/d/0B1xF6uYPZz7AMW1DUTU1X1poV2s/view?usp=sharing
File Size: 163.7MB
MD5: d8c44d25d0479ef40ad5f092ff7ffd39
I'm sure this upload is gonna get flagged in no time on Google Drive... So somebody else should upload it if possible.
Click to expand...
Click to collapse
Thanks! And no, the name is normal. The OTA filename always states the version you need to be on to install it, not the version that it contains.

Updated Moto X Pure 2015 to marshmallow 6.0 and now can't downgrade via twrp

I just recieved my Moto X pure/style today in the mail and opened the box and let the update install. After the installation I then unlocked the bootloader, flashed the correct logo.bin so I wouldn't have the unlocked bootloader crap, flashed twrp 2.8.7.0. Once I installed twrp I used the option to stay read only so I could get a backup with an unmodified system partion. I did the backup and then rebooted and downloaded the correct supersu by chainfire thanks by the way chain-fire! Then went on to root my device so I did that and then rebooted again. I downloaded a aosp 5.1.1 custom rom keep in mind I changed twrp from read only so I could modify the system. Rebooted and flashed the rom and everything seemed fine but when I rebooted it kept rebooting the the Motorola emblem. I thought maybe it was the rom but I downloaded one more and the same thing. So can you not install a 5.1.1 rom after you do the official 6.0 update? I guess the system partitions are not the same? It would be nice if someone can help me succeed doing this if there is a way. Thanks!

I miss the part where you whipe? And.....Shouldn't this be in Q&A?

ibila said:
I miss the part where you whipe? And.....Shouldn't this be in Q&A?
Click to expand...
Click to collapse
Of course I did the wipe. I did the advanced wipe and wiped the cache, dalvic cache, system, and data and it has been moved. Sorry about that. So do you know what the problem could be

jlbuck6212 said:
Of course I did the wipe. I did the advanced wipe and wiped the cache, dalvic cache, system, and data and it has been moved. Sorry about that. So do you know what the problem could be
Click to expand...
Click to collapse
You have to flash the Lollipop modem (NON-HLOS.bin) from the Lollipop SBF. Make sure you have the lollipop modem and kernel. If in doubt, use the return to stock tool and manually flash the LP modem. This should do the trick.
The lollipop modem isn't compatible with MM, and the MM modem isn't compatible with LP.

jlbuck6212 said:
Then went on to root my device so I did that and then rebooted again. I downloaded a aosp 5.1.1 custom rom keep in mind I changed twrp from read only so I could modify the system.
Click to expand...
Click to collapse
How did you go about making TWRP read write again? I chose to make it read only so I could go the systemless root method and TWRP does not give me the window to allow /system modifications, no matter whether I reflash or just boot it up.
Also, won't mounting TWRP the way you did create a bootloop because the stock recovery fights with TWRP when flashing?

EVR_PR said:
How did you go about making TWRP read write again? I chose to make it read only so I could go the systemless root method and TWRP does not give me the window to allow /system modifications, no matter whether I reflash or just boot it up.
Also, won't mounting TWRP the way you did create a bootloop because the stock recovery fights with TWRP when flashing?
Click to expand...
Click to collapse
Go into the mount tab and at the bottom uncheck where it says read only

samwathegreat said:
You have to flash the Lollipop modem (NON-HLOS.bin) from the Lollipop SBF. Make sure you have the lollipop modem and kernel. If in doubt, use the return to stock tool and manually flash the LP modem. This should do the trick.
The lollipop modem isn't compatible with MM, and the MM modem isn't compatible with LP.
Click to expand...
Click to collapse
Awesome I appreciate that. I figured it had something to do with that but what do you mean by flash it through lollipop sbf? Also you say make sure i have the stock kernel for lollipop. Why when I'm flashing a custom rom?

jlbuck6212 said:
Awesome I appreciate that. I figured it had something to do with that but what do you mean by flash it through lollipop sbf? Also you say make sure i have the stock kernel for lollipop. Why when I'm flashing a custom rom?
Click to expand...
Click to collapse
Perhaps I should have been more clear. You can find the lollipop SBF (full return to stock file) here: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view?usp=sharing
You can use RSD Lite, Return to Stock tool, or manual method to flash back to stock 5.1.1
Once flashed back to full stock, flash TWRP and install your custom ROM. It should work properly after this.
Since your custom ROM already includes /system, probably the easiest/fastest way assuming you have the SDK platform-tools installed is:
fastboot flash logo logo.bin
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash recovery TWRPfilename.bin
fastboot reboot-bootloader
boot into TWRP recovery. Flash your custom ROM. Reboot. Enjoy.

samwathegreat said:
Perhaps I should have been more clear. You can find the lollipop SBF (full return to stock file) here: https://drive.google.com/file/d/0B3gPYUZ4nRLwTl9Wd1JQX0hFejg/view?usp=sharing
You can use RSD Lite, Return to Stock tool, or manual method to flash back to stock 5.1.1
Once flashed back to full stock, flash TWRP and install your custom ROM. It should work properly after this.
Since your custom ROM already includes /system, probably the easiest/fastest way assuming you have the SDK platform-tools installed is:
fastboot flash logo logo.bin
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash bluetooth BTFM.bin
fastboot flash recovery TWRPfilename.bin
fastboot reboot-bootloader
boot into TWRP recovery. Flash your custom ROM. Reboot. Enjoy.
Click to expand...
Click to collapse
I really appreciate that! Thank you! It's been driving me crazy lol. I'll make it happen

Wifi not working after root

I rooted my Moto X Pure and the wifi stopped working. This is a problem I have run into before and I just have to flash a modem file in adb and that fixes the problem but not this time. I tried this one http://forum.xda-developers.com/moto-x-style/development/marshmallow-6-0-ota-modem-band-12-t3267680 but that didn't work. Any suggestions?

Did you try a search?

Did you flash it like this?
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2

gokart2 said:
Did you flash it like this?
Code:
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
Click to expand...
Click to collapse
Unfortunately that did not fix the problem. This is what I am using for root by the way. hXXp://androiding.how/systemless-root-moto-x-style-marshmallow-mph24-49-18/

Digital-Sapien said:
Unfortunately that did not fix the problem. This is what I am using for root by the way. hXXp://androiding.how/systemless-root-moto-x-style-marshmallow-mph24-49-18/
Click to expand...
Click to collapse
Do you have a Twrp backup of stock boot.img? If so flash that. Or flash the stock boot.img from somewhere. Then reboot to system. Then back to recovery. Then flash THIS. What it does is systemless root your stock boot.img. This is what I use, and many others do too.

gokart2 said:
Do you have a Twrp backup of stock boot.img? If so flash that. Or flash the stock boot.img from somewhere. Then reboot to system. Then back to recovery. Then flash . What it does is systemless root your stock boot.img. This is what I use, and many others do too.
Click to expand...
Click to collapse
That worked like a charm. thank you.

1 Unroot your smartphone
2. Flash the STOCK Rom
3 Retry any other CUSTOM Rom.

Digital-Sapien said:
That worked like a charm. thank you.
Click to expand...
Click to collapse
Can you give me the command to flash the super SU file? Am I flashing the entire thing or extracting the APK? Thanks!

Happened to me, I flashed my backup back to my unrooted stock rom then in twrp flashed SuperSU 2.62-3, for some reason this is the only version that works without killing wifi, once you have restarted update it in play store and all is good
https://www.dropbox.com/s/vqc91gzx825dlmn/BETA-SuperSU-v2.62-3-20151211162651.zip?dl=0