Back to Stock & ReLock Boot Loader (Google Fi) - Moto G7 Guides, News, & Discussion

I wound up getting the $150 deal from google for the G7, had massive issues with the phone, so back to google with it.
If you are curious the issues I had included:
Speaker would randomly stop working, seriously I'd reboot, it would work, the phone would lock then within 1-5 minutes it would just not work anymore. No ringer, no alarm, nothing.
Calls would not answer in wifi network, then lockup the phone. Oddly no problem in LTE.
System UI would crash randomly.
Phone would randomly lock up.
The slightly older PPOS29.114-16-5-2 firmware didn't have such severe issues, but also would not detect my SIM card, so I could never fully activate the phone.
Here's the steps I did to reflash stock and relock the device, this works under Linux, it can be modified slightly to work under windows or OSX, I put comments to show what I'm doing.
The firmware listed is for Google Fi river phones, may work similarly for other types listed, I of course have not tested it for anything but Fi. Other firmware is here: https://mirrors.lolinet.com/firmware/moto/river/official/
Code:
#
# Flash XT1962-1_RIVER_FI_9.0_PPOS29.114-16-5-2_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
# Lock Bootloader
#
# Make a directory and go to it
mkdir "PPO29.114-134"
cd "PPO29.114-134"
# Get Latest Firmware
wget https://mirrors.lolinet.com/firmware/moto/river/official/FI/XT1962-1_RIVER_FI_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
# Unzip It
unzip XT1962-1_RIVER_FI_9.0_PPO29.114-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
# Reboot to Bootloader
adb reboot bootloader
# Flash Latest Firmware
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
fastboot flash dsp adspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash system_b system_b.img_sparsechunk.2
fastboot flash vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot flash vendor vendor.img_sparsechunk.2
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase DDR
fastboot oem fb_mode_clear
# Lock the Bootloader
# Yes, you need to do oem lock 3 times
# Then flash the boot.img again or it'll throw:
# boot.img is not signed
fastboot oem lock
fastboot oem lock
fastboot oem lock
fastboot flash boot boot.img
fastboot oem lock

Moto G7 US unlocked reflash success
Thank you, vbrtrmn! This reflashing guide worked for me (RETUS / XT1962-1, US, carrier unlocked).
I picked up the G7 a few days ago, flashed LineageOS on it but had some problems: if the screen was left on, the phone was fine, but occasionally when attempting to wake the display, the phone would simply shut off! I thought it was the battery at first. I let it drain playing youtube at max brightness until it died, put it back on the charger overnight, and the problem persisted.

Worked perfectly for me. My second G7 from the same vendor on eBay. The microphone wouldn't work on the first one. The second one stopped recognizing my SIM card, then when I removed the tray to troubleshoot, the SD card had vanished (whereabouts still unknown).
Back to stock and back to the vendor. No idea how you came by such intricate information but my hat's off to you for it.

You sir are a scholar and a gentleman. Worked great with my amz variant using the proper firmware. Thanks again!

Going back to pie from android 10 stock.
Hello
I have google Fi unlocked G7 which I purchased the last November.
Yesterday, I got OTA android 10 updates, since then I can't use LTE. I am using Tello (Sprint MVNO).
Due to LTE, custom gesture conflicts with NOVA launcher and some other little issues, I want to go back to pie.
I saw your detailed posting about how to. However, to do that, should I unlock the bootloader first?
Mine is completely stock, not rooted, no twrp what so ever.
I am just worrying that I will brick my phone. Thank you very much for your help in advance!
kostop1

kostopman1 said:
Hello
I have google Fi unlocked G7 which I purchased the last November.
Yesterday, I got OTA android 10 updates, since then I can't use LTE. I am using Tello (Sprint MVNO).
Due to LTE, custom gesture conflicts with NOVA launcher and some other little issues, I want to go back to pie.
I saw your detailed posting about how to. However, to do that, should I unlock the bootloader first?
Mine is completely stock, not rooted, no twrp what so ever.
I am just worrying that I will brick my phone. Thank you very much for your help in advance!
kostop1
Click to expand...
Click to collapse
You need to very careful with flashing firmware, if the bootloader is locked.
Don't downgrade or flash a different software channel.
Safest option for flashing with a locked bootloader is LMSA'S flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

Thank you very much for the reply. I've just read the link you gave. Is it possible to downgrade through LMSA? It looks like that LMSA always download the latest firmware.
sd_shadow said:
You need to very careful with flashing firmware, if the bootloader is locked.
Don't downgrade or flash a different software channel.
Safest option for flashing with a locked bootloader is LMSA'S flash rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse

kostopman1 said:
Thank you very much for the reply. I've just read the link you gave. Is it possible to downgrade through LMSA? It looks like that LMSA always download the latest firmware.
Click to expand...
Click to collapse
Downgrading a moto with a locked bootloader will cause it no longer function correctly.
Sent from my Moto E (4) using Tapatalk

but, if I unlock the bootloader, i can downgrade firmware, right?

airplaneliker said:
but, if I unlock the bootloader, i can downgrade firmware, right?
Click to expand...
Click to collapse
There's still some risk, but yes.
Sent from my Moto E (4) using Tapatalk

Thank you for your answer. I found out that MOTO G7 Android updates messed up LTE on several people (I found out that at reddit. Verizon user, Sprint user whoever uses CDMA got impacted). Hopefully motorola give us a fix qiuickly. I don't think that I will downgrade now, since I still have warranty until the end of november, but if they don't fix it by then, I will try to downgrade. I research a lot how to do it here at XDA, and when I had a samsung galaxy 4, I remember that I used odin to upgrade and downgrade firmware. so I bet it is kind of similar steps.
By the way, could you please let me know what can be the some risk you mentioned? even if I follow the step correctly..

Where do we download the google Fi version firmware?
Lolinet removed the link for google Fi version.
There is a Fi folder on lolinet but it has the RETUS firmwares inside, instead of the Fi versions.

googlephoneFKLenAsh said:
Where do we download the google Fi version firmware?
Lolinet removed the link for google Fi version.
There is a Fi folder on lolinet but it has the RETUS firmwares inside, instead of the Fi versions.
Click to expand...
Click to collapse
I'm pretty sure that Fi and RetUS are same channel.
You could try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk

sd_shadow said:
I'm pretty sure that Fi and RetUS are same channel.
You could try LMSA's Flash Rescue option
https://forum.xda-developers.com/general/general/update-moto-lenovo-moto-smart-assistant-t3951714
Sent from my Moto E (4) using Tapatalk
Click to expand...
Click to collapse
No, they are different channels. Several months ago, I downloaded the Fi firmwares from the lolinet Fi folder, which were different from RETUS firmwares.
If anyone needs to relock bootloader on Fi version moto g7, he needs to use Fi version firmware, not RETUS or RETAIL versions.
I flashed to RETAIL firmware several months ago. Will LMSA still be able to recognize my phone as Fi version and download the Fi firmwares?
Does any one still have the last Pie firmware for google Fi moto g7 and provide a download mirror? It should be PPOS29.114-134-14.

Related

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.

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 ?

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

[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

Just installed June security patch (ALI)

Hey, I just installed June security patch on my Moto G6 and I gotta say this build is super smooth.
I’m getting more than 5-6hrs of SOT and yes DIGITAL WELLBEING IS A SYSTEM APP NOW.
I downloaded the latest firmware from here : https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
And flashed it via RSD Lite.
Don’t forget to hit thanks
aaryan1596 said:
Hey, I just installed June security patch on my Moto G6 and I gotta say this build is super smooth.
I’m getting more than 5-6hrs of SOT and yes DIGITAL WELLBEING IS A SYSTEM APP NOW.
I downloaded the latest firmware from here : https://mirrors.lolinet.com/firmware/moto/ali/official/RETAIL/
And flashed it via RSD Lite.
Don’t forget to hit thanks
Click to expand...
Click to collapse
Can I install this patch with Android 9 OTA with Root?
bradz28 said:
Can I install this patch with Android 9 OTA with Root?
Click to expand...
Click to collapse
No, unfortunately not. This is a full wipe/fresh install only. The same rooting method works, but it will have to be a fresh install.
xfrobex said:
No, unfortunately not. This is a full wipe/fresh install only. The same rooting method works, but it will have to be a fresh install.
Click to expand...
Click to collapse
Ok, thanks
Hello, I upgraded my phone through CMD commands in fastboot folder, but now I can't hear nor be heard in calls. I tried already intalling the NON-HLOS.bin from Stock ROM RETAIL OPSS27.104-92-4 and tried with the NON-HLOS.bin from the Sotck ROM from my region OPENMX OPSS27.82-87-8 too, but it didn't work.
Tried turning the phone on Secure Mode to see if it was a problem related with an app but it wasn't the case, also tried couple of times doing factory reset, but it gave the same result.
I was on the RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8 and the calls were fine. Could someone help me, please?
I did all of above with locked bootloader.
Edit:
Now I unlocked bootloader to downgrading to RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8, and it didn't work so I relock bootloader.
mariconojoda said:
Hello, I upgraded my phone through CMD commands in a fastboot folder, but now I can't hear and can't be heard in calls. I tried already intalling the NON-HLOS.bin from Stock ROM RETAIL OPSS27.104-92-4 and tried with the NON-HLOS.bin from the Sotck ROM from my region OPENMX OPSS27.82-87-8, but it didn't work.
Also tried turning the phone on Secure Mode to see if it was a problem related with an app but it wasn't the case, also tried couple of times doing factory reset, but it gave the same result.
I was on the RETAIL PPSS29.55-34-1 and the calls were fine. Could someone help me, please?
All of above with locked bootloader.
Edit:
Now I unlocked bootloader to downgrading, I donwgrade to RETAIL PPSS29.55-34-1 with NON-HLOS.bin from OPENMX OPSS27.82-87-8, it didn't work so I relock bootloader.
Click to expand...
Click to collapse
As you unlocked the bootloader your warranty is gone, plus I didn’t try with CMD commands, I used RSD Lite, so maybe try a fresh install again if problem persists.
aaryan1596 said:
As you unlocked the bootloader your warranty is gone, plus I didn’t try with CMD commands, I used RSD Lite, so maybe try a fresh install again if problem persists.
Click to expand...
Click to collapse
It don't recognize the device
Nevermind I just needed to connect the device in another port, also now the calls work thank you @aaryan1596
How do I install this without RSDLite? The program doesn't work for me at all (v5.7 on Win10), and I do not fully understand how to use fastboot/batch files to install the unpacked .zip file. Thank you for your help.
Edit: I was able to easily install this using Minimal ADB and Fastboot. Simply extract the contents of your .xml.zip file to your Minimal ADB and Fastboot installation folder. Boot your phone into fastboot mode (volume+power down) and copy and paste these commands (you can copy and paste the entire block and they will run sequentially):
Code:
fastboot erase userdata
fastboot erase cache
fastboot erase modemst1
fastboot erase modemst2
fastboot erase carrier
fastboot erase DDR
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash oem oem.img
fastboot flash logo logo.bin
fastboot flash dsp adspso.bin
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot erase modemst1
fastboot erase modemst2
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 vendor vendor.img_sparsechunk.0
fastboot flash vendor vendor.img_sparsechunk.1
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot erase cache
fastboot reboot
Using this method I was able to easily install to latest version onto my XT1925-6, which shipped with Oreo.
Is there any different between ROM with february security patch and this one (june security patch)?
Has anyone in the UK been able to download this update via system updates yet?
um.z said:
Has anyone in the UK been able to download this update via system updates yet?
Click to expand...
Click to collapse
Just downloading via system updates, channel: retgb.
Well, I received the June 1, PPS29.55-37-4 OTA (retgb channel) at around 9:40pm (Mon 5th Aug, UK time). It took 12 minutes to download the 818.6Mb package over a 4G connection, and a further 26 minutes to install it.
Everything went without a hitch, and all seemed perfectly fine afterwards...
...however, having previously read about the problems reported here on XDA and on the Lenovo/Motorola community support forum regarding recent Pie updates, I decided to perform a factory wipe/reset immediately after the update. A tiresome chore to be sure, having to set everything up again aftwards, but it just seemed the prudent thing to do.
So now, some 19 hours later, my G6 is still working perfectly, with no obvious problems, and it does certainly feel smoother and more responsive than it's predecessor, PPS29.55-24, which I received at the end of March. And, yep, this new 'build' includes Google's Digital Wellbeing app integrated at the system level, so I guess that's something new to tinker around with.
Anyhow, just some thoughts regarding my experience of updating to this latest version of Pie.
Rgrds,
Ged.
test

Categories

Resources