Database Info

Moto G Won't boot anymore.

Hello Guys,
after a week using Paranoid Android my moto g xt1032 acted weird, so I reinstalled stock using fastboot.
I am pretty familiar with the use of fastboot and flashing and so on (Guess I've flashed, and fixed over 20 different phones)
But now I've come to the point I can't even fix my own phone.
What does it do?
Well, when I start my phone, it will only show the "warning bootloader unlocked" message, and just restarts and does the same.
Sometimes it even gives a blue screen > restarts.
I can boot into fastboot mode, I tried to flash a RETAIL UK 4.4.2 And RETAIL UK 4.3 stock firmware, even though I am from The Netherlands,
but UK or German roms are the closed to mine, and as far as my knowledge goes, EU firmware are usually the same.
I managed to go into stock recovery, but when I flash philz or twrp, it just stays at the "warning bootloader unlocked" screen.

Going to try XT1032_RETAIL-EU_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF.xml.zip right now.

same result.

bump

bump

Try this - http://forum.xda-developers.com/moto-g/help/guide-recover-xt1032-gpe-4-4-4-t2824377
While my situation below may not be yours, at least this may get you back to a stable and functional device. I hope it helps. And as you are aware this will COMPLETELY wipe your phone. If you can, backup any pictures or files you want to keep before doing this.
My situation was like many others that had flashed a 4.4.4 GPE or custom ROM and ended up with a mini wifi tablet as the radio was off (as stated by dialing 8#8#4626#*#*). I have gone two days with no cell signal due to this. Trying to flash a stock image (http://sbf.droid-developers.org/phone.php?device=14) resulted in boot loops. I believe that is what everyone else is calling it. I never saw the loop as it stayed on the initial logo screen before the animation begins. Maybe it is looping fast and just showing the same screen again instead of it simply not changing. Oh well. I'm fixed now but on EU ROM. Now I'm attempting to install Blur_Version.174.44.1.falcon_umts.Retail.en.US. The EU ROM currently installed is 176.44.1, and while it works I simply want to be stock US version for now. I mention this because there is also a 174.44.4 US ROM on SBF-DROID-DEV. I tried that one (among many others) when trying to revive my phone. None of the stock images worked and I'm currently not happy with any of the custom ROMs. Stock or rooted stock will be good for me. On a tangent but I have a XT1032 purchased from AIO Wireless (now Criket but still part of ATT). Well AIO tweaked Motorola's ROM to disable tethering. I actually use Red Pocket for service (another ATT MVNO) and only bought from AIO becausse they had a sweet deal. Wasn't so sweet after I found I could not tether and after 6 months found a way to unlock bootloader, which cost another $25. In short it spent just as much money and had much frustration that could have been avoided if I had purchased directly from Motorola and got a FULLY stock and unlockable device.
---------- Post added at 11:51 PM ---------- Previous post was at 11:42 PM ----------
Pass this along also to anyone looking: theroot.ninja worked for me to unlock the bootloader (I've not posted enough to XDA so posting true URL is disabled. Google "sunshine bootloader unlock"). I found a vague reference on XDA somewhere but don't recall thread. Basically, certain carriers (like ATT and its MVNOs) have agreement with Motorola to restrict bootloader unlocking on devices they resell. Like I said, cost me $25, but it worked and I've wasted more $$ on less.

My bootloader is unlocked, I can't get into recovery, only fastboot.
and it stays at the "warning bootloader unlocked screen" aka logo screen, and it restarts so now and then.
When I start it up for the first time, the screen turns blue right away, and restarts, after a couple of restarts, it stays stuck on the logo screen :S
I tried lots of stock firmware, but none of them worked, I wonder if it's a hardware fault, but I reassembled everything, without success.

http://sbf.droid-developers.org no longer has the latest firmware images. You need to read through this thread instead:
http://forum.xda-developers.com/showthread.php?t=2546251​
4.4.4 Recovery flashable Stock Motorola zips available here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688​
Regarding fastboot and the 4.4.4 firmware image - you are obviously not doing all the necessary commands. Please state the commands you have used. Since you have updated your bootloader, ensure you are actually attempting to flash a 4.4.4 image, as a 4.4.2 image will result in an error.

lost101 said:
http://sbf.droid-developers.org no longer has the latest firmware images. You need to read through this thread instead:
http://forum.xda-developers.com/showthread.php?t=2546251​
4.4.4 Recovery flashable Stock Motorola zips available here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688​
Regarding fastboot and the 4.4.4 firmware image - you are obviously not doing all the necessary commands. Please state the commands you have used. Since you have updated your bootloader, ensure you are actually attempting to flash a 4.4.4 image, as a 4.4.2 image will result in an error.
Click to expand...
Click to collapse
I am pretty sure I am using 4.4.4
I used these commands:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk1
mfastboot flash system system.img_sparsechunk2
mfastboot flash system system.img_sparsechunk3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache

I suggest you add the follow command which will entirely wipe any remaining files your phone.
mfastboot erase userdata​

lost101 said:
I suggest you add the follow command which will entirely wipe any remaining files your phone.
mfastboot erase userdata​
Click to expand...
Click to collapse
Tried it, no change.

Jur13n said:
Tried it, no change.
Click to expand...
Click to collapse
The system flashing commands are wrong. They should be:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
See if that fixes it for you.

meekrawb said:
The system flashing commands are wrong. They should be:
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
See if that fixes it for you.
Click to expand...
Click to collapse
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
To be exactly, I know what I am doing

Jur13n said:
system.img_sparsechunk.0
system.img_sparsechunk.1
system.img_sparsechunk.2
To be exactly, I know what I am doing
Click to expand...
Click to collapse
Okay. Good luck!

Jur13n - did you try http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.

e.martin.howell said:
Jur13n - did you try http://forum.xda-developers.com/mot...-gpe-4-4-4-t2824377/post55768571#post55768571. Once back to 'base' you can update to 4.4.4 OTA or flash another ROM. And if you get stuck again, re-run this process. Three downloads, a few scripts to run; double-click easy.
Good luck.
Click to expand...
Click to collapse
http://sbf.droid-developers.org/phone.php?device=14 is offline atm, I'll try it.
What do you mean with three downloads o.o?
I only see him saying Blur_Version.174.44.1.falcon_umts.Retail.en.US

Your issue could be due to older images. Here is the EU Retail 4.4.4 image. It doesn't matter where you are in the world, it will work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348​

lost101 said:
Your issue could be due to older images. Here is the EU Retail 4.4.4 image. It doesn't matter where you are in the world, it will work fine.
http://forum.xda-developers.com/showpost.php?p=54757500&postcount=348​
Click to expand...
Click to collapse
Tried it, didn't work.
Going to try the Blur_Version.174.44.1.falcon_umts.Retail.en.US one right now.

-- edit --
no result, also tried to convert it to gpe, no result either.
I guess it's a hardware problem somehow (maybe reading the harddisk fails?)

If you still have the box that the phone came in look at it and it will tell you which Moto G you have.

[Q] Moto G [XT1033] KitKat 4.4.4 to Lolipop 5.0.2

Hi,
Current Configuration
1. Recovery : CWM Recovery
2. Device: XT1033 Indian Variant
3. Android Version: 4.4.4
4. ROM: Stock
5. Root Status: Rooted
I'm trying to install OTA vai cwm recovery but it's giving me following error.
Code:
Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:4.4.4/KXB21.14-L1.40/34:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.0.2/LXB22.46-28/30:user/release-keys; this device has motorola/falcon_retbr_ds/falcon_umtsds:4.4
E:Error in /cache/Blur_Version.210.12.40.falcon_umtsds.AsiaRetail.en.03.zip
(Status 7)
Installation aborted.
I'm stuck here since last 3-4 hours
Today Issue got resolved.
Steps I Followed.
Flashed Stock Firmware and all
Use this
If you want to preserve your Media and settings
Don't execute this
mfastboot.exe erase userdata
Click to expand...
Click to collapse
Then simply put your OTA in SD Card and install it from stock recovery.

ant24x7 said:
Hi,
Current Configuration
1. Recovery : CWM Recovery
2. Device: XT1033 Indian Variant
3. Android Version: 4.4.4
4. ROM: Stock
5. Root Status: Rooted
I'm trying to install OTA vai cwm recovery but it's giving me following error.
Code:
Package expects build fingerprint of motorola/falcon_asia_ds/falcon_umtsds:4.4.4/KXB21.14-L1.40/34:user/release-keys or motorola/falcon_asia_ds/falcon_umtsds:5.0.2/LXB22.46-28/30:user/release-keys; this device has motorola/falcon_retbr_ds/falcon_umtsds:4.4
E:Error in /cache/Blur_Version.210.12.40.falcon_umtsds.AsiaRetail.en.03.zip
(Status 7)
Installation aborted.
I'm stuck here since last 3-4 hours
Click to expand...
Click to collapse
you must using stock recovery

indrasatrya said:
you must using stock recovery
Click to expand...
Click to collapse
So is there any other way that i can install this OTA. Without messing above configuration ?

Flash the stock recovery . Unroot your phone (there is an option in SuperSU). Flash OTA update through stock recovery. To root again, flash philz recovery, reboot from recovery. You will get an option to disable recovery flash and install SU binaries. Choose yes for both and install SuperSU from the playstore. You will be on rooted 5.0.2 now.

today i downloaded the ota and while it was being insatalled about 25 % the screen displayed "error" and the device booted up and it said update unsuccessful....
what to do.......... unlocked bootloader + UNrooted moto g xt1033....

anooj21m said:
today i downloaded the ota and while it was being insatalled about 25 % the screen displayed "error" and the device booted up and it said update unsuccessful....
what to do.......... unlocked bootloader + UNrooted moto g xt1033....
Click to expand...
Click to collapse
Reflash the ASian XT1033 4.4.4 firmware and try again. There are numerous guides regarding this OTA flashing business in the general section. You might want to check them out.

pfufle said:
Flash the stock recovery . Unroot your phone (there is an option in SuperSU). Flash OTA update through stock recovery. To root again, flash philz recovery, reboot from recovery. You will get an option to disable recovery flash and install SU binaries. Choose yes for both and install SuperSU from the playstore. You will be on rooted 5.0.2 now.
Click to expand...
Click to collapse
Thanks for reply! I'll try this today.
Meanwhile I tried following and installed cm12 it worked.
1. format all partitions except /sd/media
2. Flashed cm11 with gapps
3. Faced Boot animation loop (Please some explain why ? )
4.Flashed CM12 (It Worked using it now)

pfufle said:
Flash the stock recovery . Unroot your phone (there is an option in SuperSU). Flash OTA update through stock recovery. To root again, flash philz recovery, reboot from recovery. You will get an option to disable recovery flash and install SU binaries. Choose yes for both and install SuperSU from the playstore. You will be on rooted 5.0.2 now.
Click to expand...
Click to collapse
Okay I tried these steps.
First Flashed Stock Recovery
Unroot from Supersu
Tried flashing OTA update through recovery but same error.
Any suggestion!

ant24x7 said:
Okay I tried these steps.
First Flashed Stock Recovery
Unroot from Supersu
Tried flashing OTA update through recovery but same error.
Any suggestion!
Click to expand...
Click to collapse
flash the stock firmware with stock recovery, stock 4.4.4 dual sim asia retail

pfufle said:
Flash the stock recovery . Unroot your phone (there is an option in SuperSU). Flash OTA update through stock recovery. To root again, flash philz recovery, reboot from recovery. You will get an option to disable recovery flash and install SU binaries. Choose yes for both and install SuperSU from the playstore. You will be on rooted 5.0.2 now.
Click to expand...
Click to collapse
woozie.2007 said:
flash the stock firmware with stock recovery
Click to expand...
Click to collapse
After flashing Firmware is there any chances of data loss ?

ant24x7 said:
After flashing Firmware is there any chances of data loss ?
Click to expand...
Click to collapse
yes, the phone will be like new

woozie.2007 said:
yes, the phone will be like new
Click to expand...
Click to collapse
Wait I know i'm asking questions like a noob. But data loss means
/data/media This partition will also get affected

ant24x7 said:
Wait I know i'm asking questions like a noob. But data loss means
/data/media This partition will also get affected
Click to expand...
Click to collapse
why you dont save all on your pc? after that flash a clean stock 4.4.4

woozie.2007 said:
why you dont save all on your pc? after that flash a clean stock 4.4.4
Click to expand...
Click to collapse
But Already I'm on Stock ROM with Stock Recovery and Device is unrooted.
Do I still need to flash KitKat Firmware ?

ant24x7 said:
But Already I'm on Stock ROM with Stock Recovery and Device is unrooted.
Do I still need to flash KitKat Firmware ?
Click to expand...
Click to collapse
is recomended to do a factory reset before a clean install, if you dont want to do this, you can try to flash without factory reset, but if the flash fail, you must do a factory reset....when you root the phone some libs files is modified

woozie.2007 said:
is recomended to do a factory reset before a clean install, if you dont want to do this, you can try to flash without factory reset, but if the flash fail, you must do a factory reset....when you root the phone some libs files is modified
Click to expand...
Click to collapse
Found these steps on other thread to Flash Stock 4.4.4
My Doubt is second last step where it says erase userdata. Does it wipe out my media partition too ?
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot

ant24x7 said:
Found these steps on other thread to Flash Stock 4.4.4
My Doubt is second last step where it says erase userdata. Does it wipe out my media partition too ?
Code:
mfastboot.exe flash partition gpt.bin
mfastboot.exe flash motoboot motoboot.img
mfastboot.exe flash logo logo.bin
mfastboot.exe flash boot boot.img
mfastboot.exe flash recovery recovery.img
mfastboot.exe flash system system.img_sparsechunk.0
mfastboot.exe flash system system.img_sparsechunk.1
mfastboot.exe flash system system.img_sparsechunk.2
mfastboot.exe flash modem NON-HLOS.bin
mfastboot.exe erase modemst1
mfastboot.exe erase modemst2
mfastboot.exe flash fsg fsg.mbn
mfastboot.exe erase cache
mfastboot.exe erase userdata
mfastboot.exe reboot
Click to expand...
Click to collapse
yes, will erase all

woozie.2007 said:
yes, will erase all
Click to expand...
Click to collapse
Thanks! Backing up Entire phone. Will update here after flashing.

ant24x7 said:
Thanks! Backing up Entire phone. Will update here after flashing.
Click to expand...
Click to collapse
Skip the second last step if you don't want to bother backing your phone up.

pfufle said:
Skip the second last step if you don't want to bother backing your phone up.
Click to expand...
Click to collapse
You saved my lots of time!
I flashed stock firmware without erasing userdata. And it worked. Now successfully updated to 5.0.2. With my all Media and settings preserved.:laugh::laugh:
Thanks a ton!

How to fix XT1032 Boot loop after factory reset

Hi,
after an apparently failed attempt to install the 5.0 OTA update my XT1032 now will boot to a droid lying on its back.
I went to the recovery from there (by pressing VolUp+Power) and did the "factory reset/wipe data" and rebooted.
Same result.
I did "wipe chache". Same result: Droid lying on its back, saying "Kein Befehl" (I guess that means "no command")
I can get into recovery mode (CWM was installed before all this*) so I could try to flash stuff from outside.
But what should I try to flash? I tried flashing a (supposedly) stock system but as soon as I start with "fastboot flash boot boot.img" the phone starts booting again. So I am not really sure what to do now.
Something is seriously wrong with this phone and I would like to restore it to stock settings. I bought it on amazon.DE - so if any one of you guys knows where I could find a truly original stock image for this phone and what to do with it, please let me know.
PS: Right now I can't even get into recovery anymore. The thing just keeps booting and booting. Can't even turn it off.
* meaning: before I flashed the supposed stock recovery that apparently, in combination with the OTA update, got me into this mess

I now followed this guide:
http://forum.xda-developers.com/showthread.php?p=47820707#post47820707
I used option 3b with a 4.4.4 rom ( RETAIL-DE_4.4.4_KXB21.14-L1.40_36_cid7_CFC_1FF )
I excuted all these commands. However, upon flashing the boot.img the phone immediately boots (and gets stuck).
So I re-entered fastboot again to finish the job. Everything else went fine.
But the problem persists: When booting, the phone now displays the "Warning: Bootloader unlocked" message for a long time, with a kind of water ripple effect from bottom to top, repeating.
When I switch it off, it switches back on automatically, trying to boot and getting stuck at this screen. Sometimes I get to the droid lying on its back with a red !-Triangle on top. Poor little bugger. Soft bricked.
What can I do to fix this?
I can still enter fastboot.
I assume that yet again I grabbed the wrong ROM.
Is this supposed to be dead? http://sbf.droid-developers.org/phone.php?device=14

I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.

legolas06 said:
I think you might be on lollipop bootloader as you are having a screen flickering issue & downgrading the boatloader might be dangerous.
I'm don't know whether it will solve your problem but try flashing a lollipop firmware.
I'm not allowed to post links. Google for XT 1032 lollipop firmware. I saw one in groupandroid website.
Download the firmware from the site & execute the given commands.
Click to expand...
Click to collapse
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.

ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.

fertchen said:
Thank you. I got that file.
"adb devices" won't find my phone, though.
"Fastboot devices" does. So I can't use "adb push ..." to move the ROM to the phone.
Also, whatever option I chose from the Fastboot Flash Mode, the phone starts to boot. So I can not "enter" Recovery.
Should I just use "fastboot update rom.zip"? I don't wan't to miss my last chance to revive this phone.
Click to expand...
Click to collapse
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.

audit13 said:
ADB commands will not work in with the phone fastboot mode.
Since fastboot commands do work, you can manually flash each partition from the stock ROM. Entering recovery isn't required to do this.
Click to expand...
Click to collapse
The problem here is that the phone will boot as soon as I flash the boot.img and the whole thing fails.
Do you see a way out of this situation?
Any way to do this with a .zip ROM?

Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.

@Fretchen
That might be because you are on lollipop bootloader & you are trying to flash kitkat bootloader?But I may be wrong. Previously you told that you tried restoring to kitkat & that boot.img is kitkat bootloader. Try with this lollipop firmware.

audit13 said:
Have you tried flashing different firmware such as the GPE for your phone?
Does boot.img flash properly? If it does, you could try installing TWRP, boot into TWRP, mount the data partition, and use your computer to copy a custom ROM to the phone fpr flashing.
Click to expand...
Click to collapse
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?

fertchen said:
I now did exactly what legolas06 wrote, using "MoeMoe_BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml"
There were "hab check fails" for recovery and boot but at least the device did not reboot upon flashing the boot.img.
I rebooted it and it is going further than ever before, all the Motorola animations were played but in the end the phone got stuck at the circular blue pool (water) with the bit Motorola 'M' plus the concentric water ripple effect.
I switched it off and on again and then it played through the animations, then updated the apps (total number: 9) and then started the system. Apparently it is working.
Thank you very much, I really appreciate your support.
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
Happy that I could help.
You flashed the stock firmware so everything should work again. OTA updates if available would work.

fertchen said:
Allow me thse final questions:
Can I from now on just apply OTA updates?
If not, what can I change to make this possible?
Is it advisable to install a EU Rom soon for whatever reason?
Click to expand...
Click to collapse
I don't know if you can apply OTA updates. Before the OTA update will work, you may need to update all Motorol apps via Play store.
You could wait until a fulkl stock lollipop pop is released for your phone and flash it using fastboot.
You can try different ROMs but stick to the ROMs made for your model. I have an xt1032 and I have installed US Retail, stock Telus, and GPE.

worked for me too, thank you soo much. give this solution a try
legolas06 said:
I had similar problems & this method worked for me everytime. Sorry I'm a new user & I cannot post the links.
You can search the forum & find the links.
I found a thread in "xda -> moto g general->[FIRMWARE][XT1032-XT1033] Firmware Lollipop Retail Brasil & Asia 5.0.2" by cristiand391. Download the firmware for your device. It will be in BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml.zip. Extract the contents to the fastboot.exe folder where you use regularly. Run the commands in fastbootmode. Please be careful with the commands.
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
Reboot.
Click to expand...
Click to collapse
these steps look soo similar that the ones you can find in other blogs/discussions, but for me, in my case the main difference was the firmware, I tried with a loot of them, but the one that is mentioned in this post, installed smoothly, and with no issues, thank you so much, to post your experience and this solution.
My Best Regards,
Esteban

AUSTRALIAN XT1572 guide to restore stock to get offical OTA 6.0 update

DISCLAIMER - if you have never rooted or flashed a phone in the past, please stop reading now. Don't even try this, you will probably brick your phone. This process complete replaces all OS components on your phone which can be hard to reverse if you don't know what you are doing. Proceed at your own risk! Backup and have a few roms handy to flash in case you mess up if the guide does not work for you. Make sure you have plenty of battery life before beginning.
This is a guide to restore to stock a Retail Asia (Australian Vodafone) Moto X Style XT1572 single sim phone.
I rooted and then flashed the EU single sim version rom of 6.0 a while ago, but now I wanted to go back to stock. Here is guide how. You will need your bootloader unlocked and developer mode on for USB debugging.
I believe the original Stock OS for the Retail Asia single sim Moto X style was 'X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1'. That is version 23.116-18.1. Retail Asia, NOT dual sim. The only reason to do this is you have an Australia/ Retail Asia handset and you flashed another rom on to it and want to go back to the Retail Asia single sim OTA update (Australian vodafone). If you have not messed with your phone you should not need to do this. But you could download the OS image as a future backup in case you ever want to back original stock rom the phone shipped with.
Google drive link - 'X_Style_XT1572_CLARK_RETASIA_5.1.1_LPH23.116-18.1 (1.4gb)
Once you have downloaded the zip, decompress it to a folder. Then using Command prompt or Terminal navigate to the folder. Make sure you have fastboot or mfastboot running properly (not sure why you need to use mfastboot but some do), boot in to the bootloader and beginning flashing the individual components of the zip file.
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
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 system system.img_sparsechunk.8
fastboot flash system system.img_sparsechunk.9
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot flash bluetooth BTFM.bin
fastboot erase cache
fastboot erase userdata
fastboot reboot
Once you reboot the phone you should be running the completely stock rom the phone come with. It will remove root and any custom recovery you might have installed. It will not relock the bootloader.
To get the OTA you need to be on the stock rom and NOT rooted. Once you reboot within seconds you should get an update notification to download the new 24.11.20 Android M 6.0 update. It is about 640mb.
I hope this helps.

Thanks
Was wondering when they would release the official update for retasia
Have reverted back to stock to download the OTA and also captured the OTA for single sim retasia. The version number on this is slightly newer than the Europe and US versions I have been using
edit: Link to retasia MM
https://drive.google.com/file/d/0B4G7mEPBaNoHckxCWWxnY0dzaVU/view?usp=sharing

Awesome! Thank you @Sensation_NZ. I tried to capture the OTA but for some reason my adb would flash but not rewrite anything from the device back. I have grabbed a copy for future use.

wondering if all Australian X Style handsets are Asian? or EU?

Thanks for the post... Just wondering if you could help me, where could I find the modem for the Australian version? Thank you

swifteagle said:
Thanks for the post... Just wondering if you could help me, where could I find the modem for the Australian version? Thank you
Click to expand...
Click to collapse
Never mind, it is included. "fastboot flash modem NON-HLOS.bin" . Thank you very much for this post, life saver!

How did you capture the OTA?

Will this work for dual sim??

Great .. My 1st BootLoop ..
I followed this to the T .. And now it doesn't boot ...
Anyone know how to fix this so it works again, like back to Stock that works.?

I think you flashed Lolipop.
The same way as here:
https://forum.xda-developers.com/moto-x-style/general/guide-flashing-stock-firmware-t3637235
Don't copy&paste; read, think & retype, download newest 6.x.x for your model, check how many sparsechunks it has(9,10,12?). @Lethal_1

How to take OTA after Rooting Nougat.. (NPJ 25.93-14 to NPJS 25.93-14-4)

TRY THIS AT YOUR OWN RISK! MAKE A NANDROID BACKUP BEFORE MAKING ANY CHANGES!
So, you have rooted The phone flashed EX kernel and then Rooted via SuperSU/Phh's Superuser/Magisk v 12.0
Find the stock Kernel of the version you are on, since this OTA needs you to be on 25.93-14, therefore, you can find the boot.img of the stock kernel. here and stock recovery here
Next would be to un-root the phone,
ANY FLASHING HERE NEEDS TO BE DONE IN CUSTOM RECOVERY. ( I know you know it, but Just a reminder)
1. SuperSU - use the un-root option,
2. Phh's Superuser - just uninstall the apk and then flash the stock boot.img
3. MagiskSU - Use the magisk uninstaller here
3 simple Steps to follow: (Please follow the order, as flashing the stock boot.img on the rooted phone can bootloop it! And nothing will help then except flashing the stock ROM.)
1. Make sure you redo any changes done to the System. (cannot guarantee if the OTA will succeed after this). The changes done by Magisk will be reverted as soon as you flash the uninstaller, so nothing to worry about that.
2. Un-root the phone by the steps above! Needs to be done in custom recovery. (Real Important) IGNORE IF ROOTED BY SUPERSU. USE APP UNROOT OR RESTORE THE NANDROID MADE BEFORE ROOTING
3. Connect the phone Via PC and then in bootloader mode flash the stock boot.img and recovery.img
Take the OTA of approx 40MB and then u can root the phone again!
Done!

I have also replaced the boot warning picture with a custom one. Wonder if I need to reverse this... I don't have the stock warning pic.
Maybe I should flash the system and logo completely, keeping the user data.

SoNic67 said:
I have also replaced the boot warning picture with a custom one. Wonder if I need to reverse this... I don't have the stock warning pic.
Maybe I should flash the system and logo completely, keeping the user data.
Click to expand...
Click to collapse
Yess, that needs to be brought back to stock... flashing the logo file in the stock firmware should do the trick... I have never tried it though!

I have re-flashed the 93-14.4 with the file that I have received. Well... it seems that the retention is gone. Again.

I uninstalled the root, flashed the stock recovery and removed any root apps on the phone. Still the update wouldn't work and I won't go as far as re-locking my bootloader in order to install a update that only patches some vulnerabilities that this device has been vulnerable to for at least 6 months. When I tried to install the update it would fail every time.

I did use the fastboot to re-flash the system and logo, keeping my data untouched. The "noerase.bat" file contains:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.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 erase cache
fastboot reboot

j0nas_ said:
I uninstalled the root, flashed the stock recovery and removed any root apps on the phone. Still the update wouldn't work and I won't go as far as re-locking my bootloader in order to install a update that only patches some vulnerabilities that this device has been vulnerable to for at least 6 months. When I tried to install the update it would fail every time.
Click to expand...
Click to collapse
How did u root the phone?? SuperSU? U don't really need to uninstall the the root apps as after unroot they do not function!!
Did u alter the system? Like made any user app as system app??

SoNic67 said:
I did use the fastboot to re-flash the system and logo, keeping my data untouched. The "noerase.bat" file contains:
Code:
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.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 erase cache
fastboot reboot
Click to expand...
Click to collapse
What's the error that u are getting after this??
Ideally, u should flash only system file!! Recovery and System 1-7!

abhi212b said:
How did u root the phone?? SuperSU? U don't really need to uninstall the the root apps as after unroot they do not function!!
Did u alter the system? Like made any user app as system app??
Click to expand...
Click to collapse
I rooted with superuser.zip with phh's superuser app. Got it somewhere here on xda and it has worked fine. Some root apps caused a bootloop, either gnuroot or root essentials or both. I just remove most root apps that may interfere with the bootup when I unroot even if they can't do anything after the unroot.

j0nas_ said:
I rooted with superuser.zip with phh's superuser app. Got it somewhere here on xda and it has worked fine. Some root apps caused a bootloop, either gnuroot or root essentials or both. I just remove most root apps that may interfere with the bootup when I unroot even if they can't do anything after the unroot.
Click to expand...
Click to collapse
Ohkay! did u flash EX kernel? Did u bring back that to stock??

abhi212b said:
Ohkay! did u flash EX kernel? Did u bring back that to stock??
Click to expand...
Click to collapse
Yes, I backed up the stock one before I flashed it for the first time.

j0nas_ said:
Yes, I backed up the stock one before I flashed it for the first time.
Click to expand...
Click to collapse
If everything's stock, there should not be any problems in taking an OTA!
You can go here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
And download the stock rom and flash only system files, just in case any messing up to the system was done.
Make a nandroid 1st.
Just flash systemsparse 0-7..
If that doesn't help...Flash all of these!
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 customize
fastboot erase clogo
This should do the trick.

abhi212b said:
If everything's stock, there should not be any problems in taking an OTA!
You can go here https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
And download the stock rom and flash only system files, just in case any messing up to the system was done.
Make a nandroid 1st.
Just flash systemsparse 1-7..
If that doesn't help...Flash all of these!
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.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 customize
fastboot erase clogo
This should do the trick.
Click to expand...
Click to collapse
Do I need to re-lock the bootloader? Because that was the only thing missing from complete unroot. When I tried to install the update it got to like 40% before crashing or something, don't know what causes that.

j0nas_ said:
Do I need to re-lock the bootloader? Because that was the only thing missing from complete unroot. When I tried to install the update it got to like 40% before crashing or something, don't know what causes that.
Click to expand...
Click to collapse
Nope, relocking is not mandatory to take the OTA! It fails because the device doesn't look like stock! if u uninstalled any system app, or removed the bootloader unlocked warning message or used any custom logo, or even added any folder to the system folder, it fails!

abhi212b said:
Nope, relocking is not mandatory to take the OTA! It fails because the device doesn't look like stock! if u uninstalled any system app, or removed the bootloader unlocked warning message or used any custom logo, or even added any folder to the system folder, it fails!
Click to expand...
Click to collapse
It still fails and it's as a clean install as it can be apart frombeing connected to my wifi and my google account, nothing else is installed. When I try to install the update this time it got to ~30% and then displayed a dead android and "Error!" below it.

j0nas_ said:
It still fails and it's as a clean install as it can be apart frombeing connected to my wifi and my google account, nothing else is installed. When I try to install the update this time it got to ~30% and then displayed a dead android and "Error!" below it.
Click to expand...
Click to collapse
I have no idea if everything is stock why is it failing OTA! Then you will have to install stock rom again.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Go here and follow the instructions! If u are rooted then make a titanium backup of all the apps and user data and then do this function! That way after taking the OTA u can root again and use the titanium backup app to get all the data back!

Newbie here. I hope to receive my Moto G4 Plus (xt1644) tomorrow! I don't understand this step:
2. Un-root the phone by the steps above! Needs to be done in custom recovery. (Real Important)
When rooting my G4 Plus, I will be using SuperSU. It seems that to unroot this app it's not done within custom recovery, which step 2 seems to require? Am I misunderstanding something?
Also, you speak of a 40MB OTA update. Does this change the Android version or is it just some type of security patch? Thanks

flroots said:
Newbie here. I hope to receive my Moto G4 Plus (xt1644) tomorrow! I don't understand this step:
2. Un-root the phone by the steps above! Needs to be done in custom recovery. (Real Important)
When rooting my G4 Plus, I will be using SuperSU. It seems that to unroot this app it's not done within custom recovery, which step 2 seems to require? Am I misunderstanding something?
Also, you speak of a 40MB OTA update. Does this change the Android version or is it just some type of security patch? Thanks
Click to expand...
Click to collapse
You use custom recovery to recover your bootloader and system before making any changes.
---------- Post added at 11:23 AM ---------- Previous post was at 11:18 AM ----------
abhi212b said:
I have no idea if everything is stock why is it failing OTA! Then you will have to install stock rom again.
https://forum.xda-developers.com/moto-g4-plus/how-to/moto-g4-plus-xt1640-43-athene-npj25-93-t3549369
Go here and follow the instructions! If u are rooted then make a titanium backup of all the apps and user data and then do this function! That way after taking the OTA u can root again and use the titanium backup app to get all the data back!
Click to expand...
Click to collapse
I used titanium backup to restore my apps after installing linage os. I felt the trouble of installing linage is less than acquiring that security update. So far so good Except all sms are lost and a few games lost their saves.

abhi212b said:
What's the error that u are getting after this??
Ideally, u should flash only system file!! Recovery and System 1-7!
Click to expand...
Click to collapse
I guess the bootloader didn't want to be re-written, but the logo also needed to be reverted (I had a custom one).
However, the above procedure worked fine for me, the installed applications where maintained.

j0nas_ said:
You use custom recovery to recover your bootloader and system before making any changes..
Click to expand...
Click to collapse
Sorry, I don't know what that has to do with step 2 which refers to unrooting SuperSU. As near as I can tell, one does the uninstall of SuperSU within the SuperSU app on Android, not custom recovery. Hope you can elaborate. Thanks