Database Info

[Q] Restore GPE US to sock

Hey,
So I've been searching for a few days now in the moto g section. I can't find any guides to restore my moto g GPE US version to stock. I found somewhat of walkthrough using the moto tool but I dont' have a windows machine to run that program. Is there another way to do this? Please let me know, also if I missed a post that shows this info please reply with the link.
Thank you!

If you don't have a Windows machine, it'd be good if we knew what you do have in order to guide you properly.
Flashing back to stock on Linux is quite easy once you've got the tools set up. I would assume MacOS X is similar provided you can get a suitable fastboot or mfastboot binary. (I recommend having them in a directeory listed in your $PATH variable with proper permissions for USB so that you don't need to sudo to use them.)
If you've got no computer, but can boot in a modified recovery, it should be possible to flash the entire stock ROM with that. You wouldn't be able to relock the bootloader though, if that's something you were aiming for.

killjoydreams said:
Hey,
So I've been searching for a few days now in the moto g section. I can't find any guides to restore my moto g GPE US version to stock. I found somewhat of walkthrough using the moto tool but I dont' have a windows machine to run that program. Is there another way to do this? Please let me know, also if I missed a post that shows this info please reply with the link.
Thank you!
Click to expand...
Click to collapse
If you are on MAC or linux I suppose you have fastboot installed! If not get it installed from here
Now To restore your phone to stock download this firmware.
After Downloading! Extract the firmware. cd to the directory of extraction.
Use the script in the attachement to restore your phone.
OR
Enter these commands manually
Code:
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash motoboot motoboot.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img_sparsechunk1
fastboot flash system system.img_sparsechunk2
fastboot flash system system.img_sparsechunk3
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
You will need the path to fastboot to be added in path variable!

OMG!!!! thank you, thank you, thank you!!!!!
Worked like a charm, I was flipping out trying to figure this out b4 I had to work, your a life saver!!! Btw is there any downside to this process, like can I re-lock the boot loader and is it still possible to get OTA updates?

OTA updates work regardless of whether your bootloader is unlocked or not.
It's root and other changes to the /system partition that'd prevent such updates from working.

killjoydreams said:
Worked like a charm, I was flipping out trying to figure this out b4 I had to work, your a life saver!!! Btw is there any downside to this process, like can I re-lock the boot loader and is it still possible to get OTA updates?
Click to expand...
Click to collapse
No no downsides
You can re-lock the bootloader
And you will get OTA updates as well, even if your bootloader is unlocked!
Just have stock recovery

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.

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

A Noob's Guide to upgrade Moto X Play to Marshmallow ;)

Before i begin, i would like to state that none of the files belong to me, they have been uploaded or provided by someone or other over the internet and i have given credit wherever it is due. If i forget somewhere and please lemme know, I'll fix it.
Note: This is tested only on Moto X Play XT1562 Indian version only. Others use this guide at their own risk. Currently Calls/Data do not work in X1562 as you loose the modem files on upgrade and flashing them back has no effect
First, Lets download the stuff we need at hand:
1) Stock Brasilian Firmware drive.google.com/open?id=0Bx1aljTBgTbATE9ISmNYZ3h2UGs From Yuri Martins @ androidpit.com
2) The Marshmallow update. https://drive.google.com/open?id=0B-MLCAZmmekxb2hOa3ppWTBFRjQ from estanenmi @ XDA
Steps:
1)Now Reboot in fastboot mode by turning off phone and turning it on by holding volume down and power button. Connect to PC, open the command prompt in ADM folder by using shift+right click on ADB folder and selecting open command prompt option.
2)Copy past all the line below as it is in the command prompt. Sit back and relax. It will take around 5 minutes.
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 modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot erase cache
fastboot erase userdata
fastboot reboot
3) Restart the phone, it will have Brasilian firmware. Go through the initial set up and connect to PC to copy the marshmallow update file in phone directory.
4) Again restart the bootloader of phone by turning it off and turning on by holding the volume down and power button. Here select the recovery option. It will show a dead android pic, press power button and quickly tap volume up. You will be in the stock recovery. There select the install update from SD card option. Select the update file and install. Beware it will take a lot of time and it would appear stuck at patching or verifying files (can't remember which one ) but dont worry, its normal. Once it is done, restart the phone and enjoy the yummy marshmallow.
P.S: Sorry if i missed any instructions, i know the community here will help out others. I was in a bit of hurry, getting very late for bed, will add more instructions and pics tomorrow.
Adios

Mods, please edit the title to : A Noob's to upgrade Moto X Play to Marshmallow

antisocialbratt said:
Mods, please edit the title to : A Noob's to upgrade Moto X Play to Marshmallow
Click to expand...
Click to collapse
Plz upload TWRP backup if possible

Will do that once i have a stable build running. Having trouble with getting sim card detected. I think i need to get the correct modem files for Indian version. Trying to find out correct files for the Dual Sim.

antisocialbratt said:
Will do that once i have a stable build running. Having trouble with getting sim card detected. I think i need to get the correct modem files for Indian version. Trying to find out correct files for the Dual Sim.
Click to expand...
Click to collapse
Yes you have to flash indian modem files... Just flash modem files of retail india firmware

Dont have them and cant find them. Can anyone share the files or upload them to their google drive. They are hardly 40mb, dont wanna download whole indian firmware of 1.2 gb for that :/

antisocialbratt said:
Dont have them and cant find them. Can anyone share the files or upload them to their google drive. They are hardly 40mb, dont wanna download whole indian firmware of 1.2 gb for that :/
Click to expand...
Click to collapse
Here you go

droider007 said:
Plz upload TWRP backup if possible
Click to expand...
Click to collapse
pls upload twrp backup please

Please upload twrp backup by any indian for indian version ... Thnks in advance

Is it multilingual?
Envoyé de mon XT1562 en utilisant Tapatalk

Has anyone tested this procedure on a Canadian xt1563?

I managed to save the modems upto brasilian rom upgrade. Lets see if i can manage to get them all the way through the end till marshmallow.

Hii
---------- Post added at 12:53 PM ---------- Previous post was at 12:49 PM ----------
Hey I am using moto x play Indian Version. Can it upgraded to 6.0? What about warranty?

flash original brazilian firmware with rsd lite then update via stock recovery to marshmallow.
you doesnt need unlocked bootloader

Unable to get the sim to work in Marshmallow for Indian Moto X Play. Here are my findings. Could be useful for the tinkerers .
1) Install Indian ROM>Brasil ROM(no Sim)> Marshmallow (No Sim.)>Flash Indian modem = No Sim
2) Install Indian ROM> Brasil ROM without Brasil Modems (Sim works)> Marshmallow (No Sim)> Flash Indian modem = No Sim
3) Install Indian ROM>Brasil ROM> Flash Indian modem = No Sim

OK, so from everything I have read, this does NOT work correctly with the XT1562, in that modems do not work with this method, and thus no data or calls/sms. Should this not be given a big massive warning in the first post?
S

TheBishopOfSoho said:
OK, so from everything I have read, this does NOT work correctly with the XT1562, in that modems do not work with this method, and thus no data or calls/sms. Should this not be given a big massive warning in the first post?
S
Click to expand...
Click to collapse
Done that. Thanks for pointing it out. Actually when i created the thread, I did not put my sim card in the phone thus had no idea about it. Its a shame though that everything else works flawlessly.

antisocialbratt said:
Unable to get the sim to work in Marshmallow for Indian Moto X Play. Here are my findings. Could be useful for the tinkerers .
1) Install Indian ROM>Brasil ROM(no Sim)> Marshmallow (No Sim.)>Flash Indian modem = No Sim
2) Install Indian ROM> Brasil ROM without Brasil Modems (Sim works)> Marshmallow (No Sim)> Flash Indian modem = No Sim
3) Install Indian ROM>Brasil ROM> Flash Indian modem = No Sim
Click to expand...
Click to collapse
Did you used the method with four steps to change the modem?
Like:
Code:
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
Anyway think twice before upgrading with this method because usually on motorola phones you can't simply downgrade the firmware, many users in other forum sections faced some soft or even hard bricks trying to downgrade ( mainly bootloader and/or gpt )

Great, thanks. Ive been burned before a few times and left with expensive paperweights for phones from not reading all the comments and blindly updating. I make sure I know what Im heading into before flashing!

So... is anybody able to use his/her sim in europe (germany etc.) with this (brazilian) firmware with or without flashing the modem ?

[FIRMWARE][GUIDE] Restoring the Moto E5 Play to Stock Factory State

Stock Android 8.0.0 Factory Firmware
Moto E5 Play (James) xt1921-5
Sprint/Virgin Mobile/Boost Mobile
WARNING: This stock Android 8.0.0 firmware package should not be used in an attempt to downgrade your device to an earlier firmware build. (While downgrading is possible, only the more advanced users should attempt it ) Use this firmware & guide only if your device has never been upgraded beyond Build No. OCP27.91-23. Attempting to downgrade your partition index (gpt.bin) or your bootloader partitions (bootloader.img) can result in a hard-bricked device -- and typically bricked beyond repair. By proceeding further, you are assuming sole responsibility for the integrity and functionality of your device, thus absolving me from any civil liability in the event your device becomes bricked, damaged, or otherwise inoperable.
SPECIFICATIONS:
Android Version: 8.0.0 Oreo
Build No. OCP27.91-23
Kernel Version: 3.18.71
Radio Version: M8920.11.54.11.41R
Security Patch Level: March 1, 2018
APPLICABILITY:
There are any number of reasons to use this restoration guide. If you are running a rooted device with system-based or systemless modifications to your Android OS, and you merely want to return to an unmodified stock configuration, this guide will accomplish that. If your device is soft bricked, stuck in a boot loop or is otherwise malfunctioning from a software standpoint, this guide will repair your phone. Or, perhaps you simply want to return to unmodified stock in order to install an OTA update. Again, this guide is for you.
RESTORATION/FLASHING INSTRUCTIONS:
This guide is written with the assumption that you have at least a rudimentary knowledge of AP Fastboot Mode and basic flashing commands. While this firmware can certainly be installed using RSD-Lite, mFastboot, etc., this guide aims at a basic fastboot installation. This procedure will erase all userdata stored on your device, enables dm-verity (device mapping), and enables default force encryption of the /userdata partition. Please make a backup of any data, files, media, etc. that you want to keep prior to proceeding. This process removes root binaries, BusyBox, root-dependent mods, and restores all OEM and carrier-specific bloatware. This guide also assumes that you have a recent version of the Minimal ADB & Fastboot utilities installed on your PC or laptop, as well as the proper USB device drivers.
1. Download the firmware package from the below link and extract the contents of the archive to your adb/fastboot directory on your PC;
2. Boot your device into AP Fastboot Mode by first powering down your device and then simultaneously holding the Power + Volume Down keys for around 8 seconds, until you see AP Fastboot Mode on your device display;
3. Connect your device to your PC using the OEM supplied or quality-equivalent micro USB to USB syncing cable;
4. Open a command window in the path of your adb/fastboot directory;
5. Enter this command:
fastboot devices
Press Enter/Return
If your device and PC are properly connected, an alpha-numeric string will appear in the command window synonomous to your device serial number;
6. After ensuring a proper connection, execute the following commands:
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 erase DDR
fastboot erase cache
fastboot erase userdata
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot oem fb_mode_clear
7. Now reboot your device by entering:
fastboot reboot
Press Enter/Return
Upon reboot, your device should be fully restored to stock Android 8.0.0 firmware, Build No. OCP27.91-23, and your device will be fully capable of installing OTA update packages.
DOWNLOAD LINK:
https://drive.google.com/file/d/1v39JAH7gUjjN5-iR8qPln4WS9Hozq88s/view?usp=drivesdk

Over the next few days, I will be adding threads with firmware packages and restoration instructions for other variants of the Moto E5, including the Moto E5 Cruise & the Moto E5 Plus.

You're awesome, Because I somehow disappeared my radio again. lol. Between the rom and this you've singlehandedly rebuilt my phone

Starkiller2 said:
You're awesome, Because I somehow disappeared my radio again. lol. Between the rom and this you've singlehandedly rebuilt my phone
Click to expand...
Click to collapse
Glad it helped you. I'm in the process of updating this thread to reflect the most current firmware build of OCP27.91-23-3 with the June 1, 2018 security patch level.

MotoJunkie01 said:
Glad it helped you. I'm in the process of updating this thread to reflect the most current firmware build of OCP27.91-23-3 with the June 1, 2018 security patch level.
Click to expand...
Click to collapse
somehow I still messed up. now I'm stuck in airplane mode, with mobile radio stuck to off. I've tried everything, rerooting, different apps, programming menu. I give up. lol. even the stuff I did after I soft bricked it isn't working.

@Starkiller2, I will try to help. Who is your carrier? Your mobile service provider in other words.

MotoJunkie01 said:
@Starkiller2, I will try to help. Who is your carrier? Your mobile service provider in other words.
Click to expand...
Click to collapse
Boost mobile. Thanks for the help

Starkiller2 said:
Boost mobile. Thanks for the help
Click to expand...
Click to collapse
Ok. Try this. From the firmware package above, extract two files to your adb/fastboot directory -- NON-HLOS.bin and fsg.mbn. Boot your device into fastboot mode, connect to your PC, and open a command window in your adb/fastboot path. Execute these commands in order:
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem config fsg-id boost
fastboot oem config carrier boost
fastboot erase DDR
fastboot erase cache
fastboot oem fb_mode_clear
Reboot by entering:
fastboot reboot
This process configures your radio firmware partitions for Boost Mobile, reinstalls your radio firmware, and resets all network configurations to the factory default settings. This will typically fix problems with the cell radio, signal strength issues, domestic roaming, no cell signal, etc. Let me know. We can try some different things if need be. Whatever your issue is caused from, just remember it is fixable. Frustrating for sure, but fixable.

MotoJunkie01 said:
Ok. Try this. From the firmware package above, extract two files to your adb/fastboot directory -- NON-HLOS.bin and fsg.mbn. Boot your device into fastboot mode, connect to your PC, and open a command window in your adb/fastboot path. Execute these commands in order:
fastboot oem fb_mode_set
fastboot flash modem NON-HLOS.bin
fastboot erase modemst1
fastboot erase modemst2
fastboot flash fsg fsg.mbn
fastboot oem config fsg-id boost
fastboot oem config carrier boost
fastboot erase DDR
fastboot erase cache
fastboot oem fb_mode_clear
Reboot by entering:
fastboot reboot
This process configures your radio firmware partitions for Boost Mobile, reinstalls your radio firmware, and resets all network configurations to the factory default settings. This will typically fix problems with the cell radio, signal strength issues, domestic roaming, no cell signal, etc. Let me know. We can try some different things if need be. Whatever your issue is caused from, just remember it is fixable. Frustrating for sure, but fixable.
Click to expand...
Click to collapse
No go. Whatever it is its causing the mobile radio power switch in the programming menu to keep reverting to the off position. if I try turning it on and running a ping it switches right back off.

Starkiller2 said:
No go. Whatever it is its causing the mobile radio power switch in the programming menu to keep reverting to the off position. if I try turning it on and running a ping it switches right back off.
Click to expand...
Click to collapse
Let me research this a bit. Are you running the latest OTA update? Build OCP27.91-23-3?

yeah I flashed the stock firmware this morning and took it over wifi.

Starkiller2 said:
yeah I flashed the stock firmware this morning and took it over wifi.
Click to expand...
Click to collapse
Ok. I think I know the issue. Repeat the entire firmware restoration process again, just like you done previously, except this time skip gpt.mbn, adspso.bin and bootloader.img. Upon reboot your cell radio should work.

Still nothing. Except now it keeps trying to make me take the update again.
---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
Lol. I have a third party warranty thank God. It covers it still. Maybe it's a write off.
Still a negative. now whenever I take the update and try the firmware without the pieces you instructed, it just tries to make me update again. But recovery is working again

Starkiller2 said:
Still nothing. Except now it keeps trying to make me take the update again.
---------- Post added at 09:01 AM ---------- Previous post was at 08:59 AM ----------
Lol. I have a third party warranty thank God. It covers it still. Maybe it's a write off.
Still a negative. now whenever I take the update and try the firmware without the pieces you instructed, it just tries to make me update again. But recovery is working again
Click to expand...
Click to collapse
When it prompted you to accept the OTA, did you accept and install it? Try that and see what happens. Yours is beginning to sound like a hardware issue.

yeah I accepted it every time. lol. Im thinking I may need to just replace it. I had issues with data when I first rooted it but that was my fault and I had it working again. Thank you for all your help.

@MotoJunkie01 Do you happen to have your hands on the Retus or Unlocked firmware for this model? (Moto E5, Play)

maxmotos said:
@MotoJunkie01 Do you happen to have your hands on the Retus or Unlocked firmware for this model? (Moto E5, Play)
Click to expand...
Click to collapse
Give me the exact model number and I'll check.

The latest build is up on my Moto E5 Play Stock ROM thread -- OCPS27.91-23-3
https://forum.xda-developers.com/mo...tock-android-8-0-0-rom-moto-e5-t3806530/page2

Works with XT1944-3?
Was wondering if any of the above stock roms would work with xt1944-3 variant of Moto E5
Can you help me please? Thanks in advance

amn92 said:
Was wondering if any of the above stock roms would work with xt1944-3 variant of Moto E5
Can you help me please? Thanks in advance
Click to expand...
Click to collapse
Who is your mobile provider? I have some firmware for the xt1944-3 but I believe it's the retail. Just added xt1944-3 firmware in my thread. https://forum.xda-developers.com/moto-e5/how-to/firmware-moto-e5-xt1944-4-dual-sim-t3820901