Database Info

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

[HOW-TO] Flash Marshmallow on Moto X Style (XT1752 only!!!)

Hey guys,
since there isn't a standalone tutorial on how to flash Android 6.0 either on the Moto X Style XT1572, I will provide one.
WARNING! I am not responsible for any harm on your phone. When you're not sure if you can do it, leave it! Use the Brazilian version ONLY on phones which use US-modems! If there is anything wrong or not working, contact me!
Prerequesites:
Make sure you have backuped your internal storage and your apps, because they will delete during the fastboot flash process
Decide which version you need: Indian or Brazilian? You only should download and use the stock rom of one of them!
Install ADB and Fastboot on your PC using Minimal ADB or Android SDK
Install all ADB and Fastboot drivers, for example with Universal ADB driver
Download the files provided in the link section
Steps:
At first, extract the ADB and Fastboot files in a new folder of your choice. After that, extract the 5.1.1 stock rom and copy the boot_root.img and the TWRP image in the same directory and make sure, that there are NO subfolders
Open a command line in the new directory
Now reboot your phone into Bootloader Mode. You can do that by typing "adb reboot bootloader" in an adb command line or by turning it of and then holding the Volume down + power button
Now the funny part begins. Open a command window in the directory where you extracted ADB/Fastboot and the 5.1.1 stock rom to. Now use this commands in this order:
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 system system.img_sparsechunk.10
fastboot erase modemst1
fastboot erase modemst2
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
Setup your device. After that make sure you can open the internal storage on your PC. Copy the Marshmallow patch and the SuperSU file on the internal storage of your Moto
Boot into recovery by rebooting into bootloader mode and then selecting the "Restart Recovery" option with the volume rockers followed by pressing the powerbutton
When the text "No command" is shown, press at first the power button and then volume up. Now apply the patch by selecting it after ticking the option "Install update from SDCard" in the recovery and wait till it finished. Reboot your device afterwards
Reboot again into bootloader mode. Now install the bootloader from 5.1.1 by typing "fastboot flash bootloader bootloader.img". We need this to make TWRP work again.
Type "fastboot flash recovery name_of_the_TWRP_image.img" to flash TWRP
Still in the bootloader mode, type "fastboot flash boot boot_root.img", in order to get root working
Boot into recovery mode and flash the SuperSU file. Afterwards reboot into system
That's it! You now have MM on your Style.
Thanks to:
patt2k for the mirrors for the Indian stock rom
gmillz for having the idea with stock 5.1.1
sathishtony for the fastboots commands to flash the stock rom
freakzapster for the MM patch
Sabissimo for root
Links:
SuperSU https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip
Indian Stock 5.1.1 http://forum.xda-developers.com/showpost.php?p=63770825&postcount=208
Brazil Stock 5.1.1 https://mega.nz/#!bYU0FI7a!W1QjmjUaeG-M4XYrhC9RZwrcMqzSXCA66DebFOplmZc
Indian MM Patch http://forum.xda-developers.com/moto-x-style/general/marshmallow-ota-zip-t3250253
Brazil MM Patch https://mega.nz/#F!rElFjZqJ!Vcx1gA-48Pqx0EMOwZ6A1Q
TWRP https://dl.twrp.me/clark/
Root http://forum.xda-developers.com//mo...ow-ota-zip-t3250253/post63922440#post63922440

Do you need a unlocked bootloader for this?

Kedas said:
Do you need a unlocked bootloader for this?
Click to expand...
Click to collapse
of course.

alex1301 said:
Hey guys,
[*]Boot into recovery by rebooting into bootloader mode and then selecting the "Restart Recovery" option with the volume rockers followed by pressing the powerbutton
Click to expand...
Click to collapse
Followed all steps till now, works fine, i am on indian 5.1.1 now- BUT i can't get to recovery *-*
When i choose to get to the recovery I only get the green Android-mascot and "No command."
What now?
Thanks!
/okay, embarassing. You could add that to your how-to for idiots like me.
When seeing "no command" hold down the power button and press volume up once --> Voila, the recovery options show up.

schlitzohr1812 said:
Followed all steps till now, works fine, i am on indian 5.1.1 now- BUT i can't get to recovery *-*
When i choose to get to the recovery I only get the green Android-mascot and "No command."
What now?
Thanks!
/okay, embarassing. You could add that to your how-to for idiots like me.
When seeing "no command" hold down the power button and press volume up once --> Voila, the recovery options show up.
Click to expand...
Click to collapse
Thanks, added it.

Does this work for Verizon has anyone tried?
Sent from my XT1575 using Tapatalk

No need to thank the people in the original thread who figured it all out, eh? No problem putting a donate mention in though.

MattBooth said:
No need to thank the people in the original thread who figured it all out, eh? No problem putting a donate mention in though.
Click to expand...
Click to collapse
Normally I should only thank gmillz because after he said he flashed 5.1.1 stock Rom I was the first one who tried it and got it working. Am I right?

alex1301 said:
Normally I should only thank gmillz because after he said he flashed 5.1.1 stock Rom I was the first one who tried it and got it working. Am I right?
Click to expand...
Click to collapse
I was unaware you had done anything to be honest I just hit the Indian firmware and flashed the OTA as soon as I got in from work My point was there are several people responsible for this success and you only named a few

MattBooth said:
I was unaware you had done anything to be honest [emoji14] I just hit the Indian firmware and flashed the OTA as soon as I got in from work My point was there are several people responsible for this success and you only named a few
Click to expand...
Click to collapse
Yeah I know what you mean, but the other members contributed to make it working on the XT1575 Pure Edition, so it was unnecessary for my tutorial.

@alex1301 Could you do the same for Brazilian Moto X Style (XT1572 dual sim)? I got my OTA file here: https://mega.nz/#F!rElFjZqJ!Vcx1gA-48Pqx0EMOwZ6A1Q
If you need, I also have the stock firmware.

Tcix said:
@alex1301 Could you do the same for Brazilian Moto X Style (XT1572 dual sim)? I got my OTA file here: https://mega.nz/#F!rElFjZqJ!Vcx1gA-48Pqx0EMOwZ6A1Q
If you need, I also have the stock firmware.
Click to expand...
Click to collapse
Yeah send me also the link for the stock firmware and I will modify the thread. Normally, you have to do the same steps for the Brazilian version like for the European one.

alex1301 said:
Yeah send me also the link for the stock firmware and I will modify the thread. Normally, you have to do the same steps for the Brazilian version like for the European one.
Click to expand...
Click to collapse
Great! Just give me some time (about 50 minutes) I'm uploading the firmware to Mega.
---------- Post added at 11:04 AM ---------- Previous post was at 10:57 AM ----------
A question, can I use my stock 5.1.1 instead the Indian version? Because the Indian modems do not work here in Brazil, only the US modems do.

Tcix said:
Great! Just give me some time (about 50 minutes) I'm uploading the firmware to Mega.
---------- Post added at 11:04 AM ---------- Previous post was at 10:57 AM ----------
A question, can I use my stock 5.1.1 instead the Indian version? Because the Indian modems do not work here in Brazil, only the US modems do.
Click to expand...
Click to collapse
Yep

@alex1301 Here is the Brazilian stock firmware: https://mega.nz/#!bYU0FI7a!W1QjmjUaeG-M4XYrhC9RZwrcMqzSXCA66DebFOplmZc

can anybody tell me that has taken the ota or flashed this. is there a toggle to enable the dark ui or rro "layers" support out of the box like the nexus devices have?

Which one between Indian or Brasilian MM patch must be used for an european mono sim XT1572 Moto X Style? I've already european 5.1.1 stock rom files.

bbb77 said:
Which one between Indian or Brasilian MM patch must be used for an european mono sim XT1572 Moto X Style? I've already european 5.1.1 stock rom files.
Click to expand...
Click to collapse
You need the indian one but you must also install Indian 5.1.1 stock rom

I'm getting this when I try to flash MM OTA:
"/modem/image/adsp.b01" has unexpected contents.
E:Error in /sideload/package.zip
(Status 7)"
Any clues?

ThiEarsiling said:
I'm getting this when I try to flash MM OTA:
"/modem/image/adsp.b01" has unexpected contents.
E:Error in /sideload/package.zip
(Status 7)"
Any clues?
Click to expand...
Click to collapse
Which version of the style do you habe and which stock rom have you flashed?

Stock XT1562 RETEU Single-SIM 5.1.1 to Stock XT1562 RETASIA Dual-SIM 6.0 (No Wipe)

Hello everyone, I just upgraded my phone to Dual SIM Marshmallow yesterday while leaving the bootloader intact and without losing any data (as far as I can tell). Yes, this is a dirty flash operation, so proceed with caution.
First a little bit of gibberish: Because I got tired of waiting around for the European 6.0 update, and also having interest in the Dual SIM function anyway, I inspected the gpt.bin of both XT1562 RETEU and XT1562 RETASIA with gpt_parser.py
Turns out: the userdata partition wouldn't suffer from misalignments by flashing a different partition table:
India gpt.bin gpt_parser.py output:
Code:
[-] Partition 42
[-] Partition type GUID: 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
=> Partition type: unknown partition, UNKNOWN
[-] Unique partition GUID: 86E734CA-D096-B657-DA2D-095F241A084A
[-] First LBA: 7634944
=> Disk Offset: 0xE9000000
[-] Last LBA: 7634943
=> Disk Offset: 0xE8FFFE00
[-] Attribute flags: 1152921504606847000, UNKNOWN
[-] Partition Name: userdata
Europe gpt.bin gpt_parser.py output:
Code:
[-] Partition 42
[-] Partition type GUID: 1B81E7E6-F50D-419B-A739-2AEEF8DA3335
=> Partition type: unknown partition, UNKNOWN
[-] Unique partition GUID: 0C44D2CF-AFB9-7EEE-2FAE-03E3E1D02EB8
[-] First LBA: 7634944
=> Disk Offset: 0xE9000000
[-] Last LBA: 7634943
=> Disk Offset: 0xE8FFFE00
[-] Attribute flags: 1152921504606847000, UNKNOWN
[-] Partition Name: userdata
If you're not scared by the above feel free to proceed. The following worked for me, keep in mind that I can't know for sure if this will work out with your setup, so if you follow these instruction, you do so at your own risk:
1. I started out with LPD23.118-10 XT1562 RETEU with locked bootloader - userdata was encrypted.
2. I flashed LPD23.118-10 XT1562 RETASIA (a.k.a. Indian, and the version number is important because the OTA upgrade will only work with that - there was a faster google drive link somewhere I can't find it, sorry, will update the post if someone sends me a link) firmware like described here, but note the crucial difference:
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot reboot
fastboot erase userdata is missing before the reboot because we want to keep our current settings and apps data that can't be backed up (looking at you org.thoughtcrime.securesms)
3. Boot normally, etc. it will optimise some apps because cache was erased etc. Dual SIM should be enabled now!
4. If you want to pop into the Marshmallow world without waiting till you get OTA notifications, grab the update, place it in the root directory of your SD card, and check for system updates.
5. Wait a long time while it upgrades, boots and optimises.
6. Happily check out your Android version: 6.0 and System version: 25.11.18.lux_retasia_ds.retasiaall.en.03 reteu (yes, apparently it recognises that it's a reteu phone - a little scary but everything is fine for now)
7. ???
8. PROFIT
I already switched my data/voice plan around making use of the Dual SIM ability. It works great and now I pay a couple euros less while keeping my old number! Keep in mind though, you should use two different network providers, if the same provider sees an IMSI try to log in twice poop might get shagged up. (Also, if you use an MVNO, make sure the infrastructure providers they use are also different)
Play safe and happy (dirty) flashing
Edit: fixed link

mxnd said:
...
1. I started out with LPD23.118-10 XT1562 RETEU with locked bootloader - userdata was encrypted.
2. I flashed LPD23.118-10 XT1562 RETASIA (a...
Click to expand...
Click to collapse
From where did you download that LPD23.118-10 XT1562 RETASIA ROM.
I can't find it on filefactory site.

00sand00 said:
From where did you download that LPD23.118-10 XT1562 RETASIA ROM.
I can't find it on filefactory site.
Click to expand...
Click to collapse
Here moto.shreps.fr/?dir=Moto%20X%20Play%20%28lux%29/rom/stock

What should I do if I want to make the same, but with Single-SIM and clean install?

@mxnd
Dude, you rock.
Converted uk x play single to dual sim and everything works. Data intact
Now going for marshmallow
Updated marshmallow India.
So far so good, everything seems ok.

PanOptikum said:
What should I do if I want to make the same, but with Single-SIM and clean install?
Click to expand...
Click to collapse
As far as I can tell, only dual sim phones have gotten a 6.0 update so far. No idea what takes them so long

mxnd said:
Hello everyone, I just upgraded my phone to Dual SIM Marshmallow yesterday while leaving the bootloader intact and without losing any data (as far as I can tell). Yes, this is a dirty flash operation, so proceed with caution.
Click to expand...
Click to collapse
Awesome Job Mate!!!

At the link there is a retasia marshmallow firmware too. Is it not easier to upgrade directly to marshmallow instead of the asian version of lollipop and then to marshmallow with the ota update

Jeso said:
At the link there is a retasia marshmallow firmware too. Is it not easier to upgrade directly to marshmallow instead of the asian version of lollipop and then to marshmallow with the ota update
Click to expand...
Click to collapse
Yeah, I haven't downloaded and/or inspected the gpt partitioning of that. I would assume everything would stay in the same place there too, but verifying with the python script above is probably a good idea. I thought this was the safest route and it worked If anybody experiments, I'll happily update the post.

bablu048 said:
Here moto.shreps.fr/?dir=Moto%20X%20Play%20%28lux%29/rom/stock
Click to expand...
Click to collapse
Is taht the dual sim version? in the code name does not apears "DS"

kamarilla said:
Is taht the dual sim version? in the code name does not apears "DS"
Click to expand...
Click to collapse
yes all indian versions are dual sim.
you can get it from here also https://github.com/motoxplay/stock

Superb popped my tray out and there was a blank got it out
And there's a nice picture sim 2 underneath :good:

Where can I get firmware for asiaretail_pacific?

Excellent guide
I'm following XDA since several years but I never posted.
I followed your guide and with a bit of attention I was able to reflash my Moto X Play from single sim eu to dual sim asia/eu.
I moved from XT1562_LUX_RETEU_6.0.1_MPD24.107-52 (single sim) to XT1562_LUX_RETASIA_DS_6.0.1_MPD24.107-52 (dual sim dual standby).
A check with gpt_parser.py gives same result than on original post, so I decided to try this.
This is the exact command sequence I gave (only differs in the /sparsechunk/ section because it has 9 chunks instead of 7 of the original guide. Note that EU firmware has 8 chuncks and asia has 9 chunks, so be careful and inspect zip package before flashing).
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 erase cache
fastboot reboot
Now phone is working, SIM1 is correctly registered and now I have a dual sim phone. I don't have a second sim yet so I can't test, but in the settings there is the additional SIM menu.
Some questions:
* IMEI of SIM2 is zero. Is this a problem with carriers? Is there a way to have an IMEI for SIM2 too?
* Should the phone see the update to MPD24.107-70 or not? Now it is not seeing it (software up to date)
Thank you all for the guide and for the answers.
EDIT: After some hours, the phone stopped detecting SIM1. So I had no SIM working. After some readings I flashed the single sim european software back. I still need to read something to properly achieve this conversion. Every suggestion is appreciated

acehigh1971 said:
I'm following XDA since several years but I never posted.
I followed your guide and with a bit of attention I was able to reflash my Moto X Play from single sim eu to dual sim asia/eu.
I moved from XT1562_LUX_RETEU_6.0.1_MPD24.107-52 (single sim) to XT1562_LUX_RETASIA_DS_6.0.1_MPD24.107-52 (dual sim dual standby).
A check with gpt_parser.py gives same result than on original post, so I decided to try this.
This is the exact command sequence I gave (only differs in the /sparsechunk/ section because it has 9 chunks instead of 7 of the original guide. Note that EU firmware has 8 chuncks and asia has 9 chunks, so be careful and inspect zip package before flashing).
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 erase cache
fastboot reboot
Now phone is working, SIM1 is correctly registered and now I have a dual sim phone. I don't have a second sim yet so I can't test, but in the settings there is the additional SIM menu.
Some questions:
* IMEI of SIM2 is zero. Is this a problem with carriers? Is there a way to have an IMEI for SIM2 too?
* Should the phone see the update to MPD24.107-70 or not? Now it is not seeing it (software up to date)
Thank you all for the guide and for the answers.
EDIT: After some hours, the phone stopped detecting SIM1. So I had no SIM working. After some readings I flashed the single sim european software back. I still need to read something to properly achieve this conversion. Every suggestion is appreciated
Click to expand...
Click to collapse
I did exactly the same a few days ago. I flashed the Asia firmware and then I flashed RR (a custom rom) and forced second SIM with the fastboot command and now it looks like this:
(I cropped the IMEI SIM1 out.)
And it's working like this. Currently I'm using only 1 SIM but I tested it with a second SIM and both works.
I got the 1562 (EU/Germany) version.
I hope that helped you!
Sent from my XT1562 using XDA-Developers mobile app

So you didn't have problems of SIM1 not detected?
Is the sim1 working ok?
My question is: probably asia firmware contains a different modem partition and it does not enable all the frequencies of my european phone.

acehigh1971 said:
So you didn't have problems of SIM1 not detected?
Is the sim1 working ok?
My question is: probably asia firmware contains a different modem partition and it does not enable all the frequencies of my european phone.
Click to expand...
Click to collapse
No, SIM1 is working with both SIM cards (congstar and O2).
Hmm, I don't think so, because it worked well for me too, but I can't confirm this 100%.
Sent from my XT1562 using XDA-Developers mobile app

Ok,
I did the procedure again from the beginning. After reboot and android optimization, I removed SIM card from slot 1 and booted again without sim.
Then shutdown, inserted SIM and then powered on. I got a notification that a new sim is present and I can configure it. From then it worked fine with one sim (I only have one at the moment).
Somewhere I read there is a bug with some custom firmware not reading both SIMs, and probably I met this bug also with an original firmware.
BUT ANYHOW, there are some serious drawbacks to this stock firmware replacements:
1) IMEI of SIM2 is 0. I don't know which operators block IMEI 0 and which don't care. Googling for info does not provide meaningful results for my country (IT). But in general this could be a problem, especially if you go abroad and you don't know the details for each operator.
2) OTA do not come if, like in my case, I have a RETASIA reteu mixed device.
There are some clever posts in this thread: http://forum.xda-developers.com/moto-x-play/help/enabling-dual-sim-single-sim-devices-t3225546 where these notes are pointed out, with practical tests.
Based on this, for the moment I decided to go back to RETEU reteu single sim sw... sigh.

He cant go back, the Asia DS one is newer as the RETEU. Only with open Bootloader he can install a older one. (there is a thread in General also.)
Got no Problems with 2 Sims (O2 and german Telekom) with the DS FW on 2 RETEU Play Devices (only with Custom FW )but there is a command to fix it.
On one Device (open Bootloader and out of Warrenty i´m back on older EU FW).
He have to wait on a newer EU FW or open the bootloader (with risks) if he would back to.
(btw.: i read on some Countrys is not legal to use a Sim with no Imei + the second Sim is not detected.)
edit: maybe it would be a good idea to wipe the whole device, and start fresh?

Already reverted to reteu
Assuming you are referring to me (... He can't go back ...), I already switched back to reteu firmware.
I did all these experiments with same build level for both versions (reteu and retasia): MPD24.107-52.
This confirms me 2 things:
* Frankenstein phones like this do not get ota updates (during the time I stayed with retasia I didn't receive upgrade notification (even checking manually). And I should, because there is a new sw for retasia already available (MPD24.107-70).
* If I stay with the same build level, the partition scheme is the same so I can go back and forth between versions, with locked bootloader and without erasing userdata. The benefit in doing this is zero for me at the moment, but this is another story. It was an interesting experiment. I learned a lot.

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

[ROM][8.0.0][STOCK] Stock Android 8.0.0 ROM for Moto E5 Play (James) XT1921-3

I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Code:
fastboot devices
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
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 erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:

Thanks for posting this. I was actually going to upload it myself. You save me from having to do the work

weakNPCdotCom said:
Thanks for posting this. I was actually going to upload it myself. You save me from having to do the work
Click to expand...
Click to collapse
Not a problem.... I actually found most of the firmwares that MotoJunkie01 had posted, I might repost his firmware post (copy and paste) and replace the links after i upload them to my own Gdrive, when I have time....

AesopRock127 said:
Not a problem.... I actually found most of the firmwares that MotoJunkie01 had posted, I might repost his firmware post (copy and paste) and replace the links after i upload them to my own Gdrive, when I have time....
Click to expand...
Click to collapse
sweet. sounds great man. thank you

NM connection working now

https://mirrors.lolinet.com/firmware/moto/ look here for firmware and make sure its correct one and up to date before flashing it.

AesopRock127 said:
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Click to expand...
Click to collapse
How did you get your phone to work meaning when I call some one they can't hear me but I can hear them .I re-flashed so many ROMs already that I'm staying on GSI Rom 8.1.0 Hanna metro PC's also I did flash stock Rom and still the see problem maybe it's time for replacement. It's been 3 days searching and asking for help. Maybe device to new idk ..

skullkid383 said:
https://mirrors.lolinet.com/firmware/moto/ look here for firmware and make sure its correct one and up to date before flashing it.
Click to expand...
Click to collapse
dude this link is worth money. amazing. thank you so much.

weakNPCdotCom said:
dude this link is worth money. amazing. thank you so much.
Click to expand...
Click to collapse
Yeah I used it on my Perry before I got hannah so it was first place looked when I needed Hannah fw

Googleme35 said:
How did you get your phone to work meaning when I call some one they can't hear me but I can hear them .I re-flashed so many ROMs already that I'm staying on GSI Rom 8.1.0 Hanna metro PC's also I did flash stock Rom and still the see problem maybe it's time for replacement. It's been 3 days searching and asking for help. Maybe device to new idk ..
Click to expand...
Click to collapse
I got mine to work because I have a James device.... You mention Hannah device so guessing you flashed the wrong firmware and that's the issue. I have the James xt1921-3

AesopRock127 said:
I got mine to work because I have a James device.... You mention Hannah device so guessing you flashed the wrong firmware and that's the issue. I have the James xt1921-3
Click to expand...
Click to collapse
Ok Thanks

I'm glad i could be of assistance,i was actually hunting down root methods for my GFs samsung and saw a video that linked to the user who uploaded it to AFH, rootjunkie was the channel if i recall,so i can't take all of that sweet credit. Yall have fun,but not too much fun

AesopRock127 said:
I know I'm not the only one who has been having trouble finding the stock firmware for the Moto e5 play xt1921-3 MetroPCS/TMobile variant, code named James, that wasn't posted by @MotoJunkie01 and therefore blocked and undownloadable.
So thanks to @HPLazerJetPrinter1012 who was kind enough to find it on XDA in another section and thanks to @timjames474 for posting it in that thread....
VERY IMPORTANT IMHO THAT YOU BACKUP YOUR IMEI INFORMATION AS SOON AS YOU ROOT YOUR DEVICE, PREFERABLY BEFORE FLASHING A CUSTOM ROM. GOING FROM CUSTOM OREO BACK TO STOCK CAN EASILY ERASE ALL YOUR PHONES IMEI INFO MAKING VOLTE AND 4G AND PHONE INOPERABLE. HAPPENED TO ME AND IT WAS A HUGE P.I.T.A. TO FIX.
Download Links
JAMES_T_OCP27.91-51-4_cid21_subsidy-TMO_RSU_regulatory-DEFAULT_CFC.xml.zip / MIRROR
This is the newest (at least at the time of post) update, dated Oct 1, 2018
Instructions to revert back to stock firmware and make it so that you can get OTA updates again:
To install, extract the zip file in your adb/fastboot directory and then make sure you are properly connected to your computer by running the command
Code:
fastboot devices
Then, once you confirm you are properly connected, just run the following fastboot commands one line at a time, making sure spelling is correct (or copying and pasting to ensure proper spelling):
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash dsp adspso.bin
fastboot flash bootloader bootloader.img
fastboot flash recovery recovery.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
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 erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
After this is complete, simply reboot your device, and as long as you did everything right, you should be back on stock firmware with the ability to receive OTA updates.
Flashing a stock recovery,unencrypting your phone, or rooting will make OTA fail, so i recommend waiting to do those things until you are fully updated (unless you don't care about the latest build).
Just to cover my ass, i had nothing to do with the making of these files and I am simply posting well known information for newer users to help them get back to stock.
Therefore, i claim no responsibility for any damage or bricking of your device.
Have a good day friends and if I helped you out, a 'thanks' would be appreciated :good:
Click to expand...
Click to collapse
PLEASE tell me how you fixed the IMEI/SIM not recognized issue. I can't figure this out at all. Thanks!

OMG!!!! This was a god send. Thank you guys for putting this together for us. I thought all hope was lost. My phone is back and running. YaY!!!!!!

weakNPCdotCom said:
dude this link is worth money. amazing. thank you so much.
Click to expand...
Click to collapse
I keep getting unsecured network... Is this an issue from my end?

How do you backup IMEI in TWRP?
EFS?
Mine won't mount data for backup and cache in red
Or should I do it another way?

I have XT1924-2 AND I TOO HAVE IMEI=0 ANY FIXES?

Thank you!
This was very helpful, thanks!

TheLastAlphaUK said:
I have XT1924-2 AND I TOO HAVE IMEI=0 ANY FIXES?
Click to expand...
Click to collapse
Flash most up-to-date software

skullkid383 said:
Flash most up-to-date software
Click to expand...
Click to collapse
That's a weird Necro-Response. Also updating doesn't fix IMEI, (even though this was over a year ago, they would need an IMEI flasher and the box/numbers found somewhere else)