[Guide][Channel][Stock]Moto g7 play Factory Firmware Images

[lexiyuri]

Moto g7 play Android 9 and 10 Factory Firmware Stock Images​

Info Updated on 23-11-2020

Hi there. I have found the moto g7 play stock images mirrored in lolinet servers for Android 9, and from motorola servers for Android 10. Go and download the image you need

Android 9 Stock direct download links

Here is the repository of stock ROMs for g7 play codename chanel from Lollinet

Android 10 Stock direct download link

Finally, Android 10 has arrived!! Here is the link to the Android 10 stock rom for moto g7 play, from Motorola Cloud servers.

The download stops sometimes but can be ressumed. I suggest use Free Download Manager, Internet Download Manager (IDM) or Flashget for download without interrrumptions.

https://bit.ly/381Y2rE


---------------------------------------------------------------------------------------------------------------

How to flash your Stock Android 9 or Android 10 ROM:

If you can't get your Android 10 update via OTA, follow these instructions:

Step 0: Install Motorola Drivers through Motorola Device Manager, you can download official companion here

Step 1: Extracting Fastboot and Firmware Images:
Extract zip for chosen Firmware Image to a folder with a simple directory structure. For example: C:\motog7play-firmware\

Download the adb fastboot from Google official links according to your operating system:

https://dl.google.com/android/repository/platform-tools-latest-windows.zip
https://dl.google.com/android/repository/platform-tools-latest-linux.zip
And unzip into the firmware folder

Step 2. Reboot the phone into 'Bootloader mode' and preparing PC for flashing

In Windows there's two ways:

2.1 Entering Fastboot mode:
------------------------------------
i) The 'hardware' way.

a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.

ii) The 'software' way.

a) Enable developer mode on the Moto g7 play (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB, you should see a new ADB device detected and drivers installed.
d) Open Command Prompt, navigate to the Firmware / ADB folder (i.e CD C:\motog7_firmware ) and type:

Code:
adb reboot-bootloader

In Linux:

2.2 Linux:
Entering Fastboot mode:
------------------------------------
i) The 'hardware' way.

a) Unplug the USB cable and power off the phone.
b) Press and hold 'Volume down' then power on the phone.
c) Connect USB cable to your computer.

ii) The 'software' way. (Requires ADB to be already installed - see below)

a) Enable developer mode on the Moto G (Settings-> 'About Phone'. Tap 7 times on 'Build Number')
b) Enable USB debugging. (Settings -> 'Developer options' -> 'USB Debugging' -> check)
c) Connect phone to computer via USB
d) Navigate to the Firmware folder, right-click and open terminal and type:

Code:
adb reboot-bootloader

Installing ADB / Fastboot:
-------------------------------------
Flashing via Linux LiveCD: (Put factory firmware files on an external usb drive / pen)
--------------------------------
a) Download some Ubuntu LiveCD latest distro
b) Burn to DVD or write to USB pen
c) Restart PC, Boot from DVD into Ubuntu
d) Open Terminal and type the following:
sudo add-apt-repository ppa:nilarimogard/webupd8
sudo apt-get update
sudo apt-get install android-tools-adb android-tools-fastboot
e) Test fastboot by typing: sudo fastboot devices
You should see:
<serial number> fastboot
f) You are now ready to flash the fastboot files

Step 3: Write Fastboot Commands for Android 9

Do commands manually, one at a time - checking that each one returns an [OKAY] in the cmd (windows) or konsole (linux)
NOTE: Do not simply copy and paste these commands! - system.img_sparsechunks may differ in number and name.
Always check contents of folder you're working with. You must flash all of the sparsechunk files you have.

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_b system_b.img_sparsechunk.0
fastboot flash system_b system_b.img_sparsechunk.1
fastboot flash vendor vendor.img
fastboot flash oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase userdata
fastboot erase DDR
fastboot reboot


Step 3 alternative: Write Fastboot Commands for Android 10

Do commands manually, one at a time - checking that each one returns an [OKAY] in the cmd (windows) or konsole (linux)
NOTE: Do not simply copy and paste these commands! - system.img_sparsechunks may differ in number and name.
Always check contents of folder you're working with. You must flash all of the sparsechunk files you have.


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 boot boot.img
fastboot flash logo logo.bin
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_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 oem oem.img
fastboot flash oem_b oem_other.img
fastboot erase DDR
fastboot erase cache
fastboot erase carrier
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

Regional Variants and their Android 9 download Links

The moto g7 play has seven known variants: XT1952-1 (Europe), XT1952-2 (Latin america), XT1952-3 (United States), XT1952-4 (United states, Sprint carrier), XT1952-6 (United states, Metro PCS carrier), XT1952DL (United States, Tracfone carrier) and XT1952-T (United States, T-Mobile carrier). It is also known in some US Carriers as moto g7 optimo

FCC technical data can be found here

Official Android 9 ROMS suggested for XT1952-2 (Latin America Dual Sim)
Latest build: April 2020 security patch

Retail Generic ROM - RETAIL Channel (1.7 Gb) (April 2020 security patch): CHANNEL_RETAIL_9.0_PPYS29.105-134-12_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC

This ROM works and fit mostly on all latin american countries, and also may work in another g7 play variants

View old ROM links for other countries here

Argentina (2 Gb) (October 2019 security patch): XT1952-2_CHANNEL_RETAR_9.0_PPYS29.105-134-2_cid50_subsidy-DEFAULT_regulatory-XT1952-2-ARGENTINA_CFC


Brasil (2 Gb) (October 2019 security patch): XT1952-2_CHANNEL_RETBR_9.0_PPYS29.105-134-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC


Costa Rica (2 Gb) (October 2019 security patch): XT1952-2_CHANNEL_RETLA_9.0_PPYS29.105-134-4_cid50_subsidy-DEFAULT_regulatory-XT1952-2-COSTARICA-DS_CFC


México (2 Gb) (October 2019 security patch: XT1952-2_CHANNEL_OPENMX_9.0_PPYS29.105-134-2_cid50_subsidy-DEFAULT_regulatory-XT1952-2-MEXICO_CFC

Regional Variants and their Android 10 download Links

Apparently, the OTA released rom works like a charm (at least in my Moto g7 play XT1952-2 model) because is a non attached to carrier ROM, being very closer to the Retail ROM

Official Android 10 ROM for XT1952-2 (Latin America Dual Sim)
Latest build: October 2020 security patch


Retail Generic Android 10 ROM - RETAIL Channel (1.8 Gb) (October 2020) from Lolinet Mirrors (Download Latest): https://mirrors.lolinet.com/firmware/moto/channel/official/RETAIL/

This ROM worked without problems with Colombian mobile operators (I tested each different simcard carriers from my relatives). So, there's no excuse to work in other latin american countries, and also may work in another g7 play variants

 

[fossyfosser]

Success verbatim for the stock image on XT1952-6 (United states, Metro PCS carrier) purchased at a store a week ago.
CHANNEL_RETAIL_9.0_PPYS29.105-134-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

Only hiccup was

fastboot flash boot boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.887s]
Writing 'boot_a' (bootloader) Image signed with key bad key

But that's expected as motorola doesn't sign any official images :/

This did not unlock my SIM, but it does give me the boot.img I'll need to patch with magisk in order to have a recovery based root... not ideal, but it'll do.

Update:
The G7 Play has no "Recovery" partition. Recovery mode is just an argument to the boot.img and some signature checks disabled. So flash your patched image to the boot partition.

Update 2:
Don't flash retail images, specially the modem, to the Metro Phone!!! you may experience temporary LTE bans

 

[xtermmin]

I have a XT1952-T, got it both bootloader and SIM unlocked, and flashed the RETUS XT1952-4 firmware on it about a month ago. No more carrier bloatware.

 

[JohnSmith8786]

I have a XT1952-T, got it both bootloader and SIM unlocked, and flashed the XT1952-3 firmware on it about a month ago. No more carrier bloatware.[/QUOTE

Have you noticed weak signal since doing this? I've also flashed a T variant but with the XT1952-4 firmware and the strongest I get is -109 dbm.

 

[xtermmin]

I have a XT1952-T, got it both bootloader and SIM unlocked, and flashed the XT1952-3 firmware on it about a month ago. No more carrier bloatware.[/QUOTE

Have you noticed weak signal since doing this? I've also flashed a T variant but with the XT1952-4 firmware and the strongest I get is -109 dbm.

XT1952-4 is meant for Sprint, so that could be the issue. Flash XT1952-3 instead.

EDIT: Sorry, I meant the RETUS version of XT1952-4, not the Sprint version.

 

[JohnSmith8786]

XT1952-4 is meant for Sprint, so that could be the issue. Flash XT1952-3 instead.[/QUOTE]

Can you post a link to that file? The only XT1952-3 I seem to find are for vzw

 

[xtermmin]

XT1952-4 is meant for Sprint, so that could be the issue. Flash XT1952-3 instead.

Can you post a link to that file? The only XT1952-3 I seem to find are for vzw [/QUOTE]

Go to the firmware link in the OP: https://mirrors.lolinet.com/firmware/moto/channel/official/

Scroll down and click on RETUS (Retail US)

EDIT: Whoooops, I said XT1952-3 earlier, I meant the RETUS version of XT1952-4! Moto makes this so confusing... What I linked to above is the unlocked model's firmware.

 

[JohnSmith8786]

[/QUOTE] EDIT: Whoooops, I said XT1952-3 earlier, I meant the RETUS version of XT1952-4! Moto makes this so confusing... What I linked to above is the unlocked model's firmware.[/QUOTE]

I flashed it anyway against my better judgement lol (over the lastest unlocked RETUS version) lost my (the wife's) IMEI when I flashed back to the RETUS not entirely sure why. Had a heck of a time trying to register the Sim card, flashing back to stock TMO firmware didn't work either. I even fastboot flashed by cmd line with no luck. Flashed the VZW firmware and I had signal.... So I flashed the lastest RETUS and the modem files from the VZW firmware and I'm fine (This is strange to me because it's a TMO revvlry not a VZW branded phone) The question I'm indirectly asking is why did I lose my IMEI? I stayed on PIE... Also curious to know if anyone has had this happen before and how they fixed if they did.

 

[muhahsan2004]

Moto G7 play Stock image required

I have a XT1952-2, purchased from local supplier. I need to know which stock image is form my G7 play.

Build number: channel-userdebug 9 PPY29.68-23 2de9intcfg.test-keys

 

[JohnSmith8786]

Success verbatim for the stock image on XT1952-6 (United states, Metro PCS carrier) purchased at a store a week ago.
CHANNEL_RETAIL_9.0_PPYS29.105-134-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

Only hiccup was

fastboot flash boot boot.img
Sending 'boot_a' (32768 KB) OKAY [ 0.887s]
Writing 'boot_a' (bootloader) Image signed with key bad key

But that's expected as motorola doesn't sign any official images :/

This did not unlock my SIM, but it does give me the boot.img I'll need to patch with magisk in order to have a recovery based root... not ideal, but it'll do.

Update:
The G7 Play has no "Recovery" partition. Recovery mode is just an argument to the boot.img and some signature checks disabled. So flash your patched image to the boot partition.

Update 2:
Don't flash retail images, specially the modem, to the Metro Phone!!! you may experience temporary LTE bans

Can you elaborate on "temporary LTE bans"

 

[thetojo]

Can you elaborate on "temporary LTE bans"

Did you find out what he meant by the LTE bans?

 

[JohnSmith8786]

Did you find out what he meant by the LTE bans?

No, never did...

 

[thetojo]

Well twas worth a shot thanks

 

[Spaceminer]

Can you elaborate on "temporary LTE bans"

What he really meant to say is loss of LTE. Different carriers use different radio bands for service, so if you flash the wrong modem you'll have signal problems.

 

[ggg777]

Hello everyone,

I tried flashing stock, but get some problems.
Device:
XT1952-1
RETEU

I have downloaded this stock:
XT1952-1_CHANNEL_RETEU_9.0_PPYS29.105-134-7_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Spaceminer told me, that before TWRP etc. I have to look that A and B are not empty so I tried flashing stock to get it safe (am I right that flashing stock would both partitions flash?)

PC-System:
Linux debian

Problem:
$ fastboot flash modem NON-HLOS.bin
target reported max download size of 536870912 bytes
sending 'modema' (65280 KB)...
OKAY [ 2.669s]
writing 'modema'...
(bootloader) Invalid partition name modema
FAILED (remote failure)
finished. total time: 2.670s
--------
$ fastboot flash fsg fsg.mbn
target reported max download size of 536870912 bytes
sending 'fsga' (11120 KB)...
OKAY [ 0.456s]
writing 'fsga'...
(bootloader) Invalid partition name fsga
FAILED (remote failure)
finished. total time: 0.457s
--------

There is always a "a" at the filenames.
modem -> modema
fsg -> fsga

How should I handle this?


Thanks for your help

 

[Spaceminer]

@ggg777

Use the latest fastboot from the Android sdk or use the latest fastboot portable from xda. If you already are, then try specifying the slot with boot_a or boot_b.

 

[ggg777]

@ggg777

Use the latest fastboot from the Android sdk or use the latest fastboot portable from xda. If you already are, then try specifying the slot with boot_a or boot_b.

Thanks, I will try that

 

[hassanmuj]

Hi. I tried flashing a couple of different versions of XT 1952-2 (such as RETAIL, RETBR) on my phone but everytime i try to run my phone the accelerator sensor seems to be inverted.
I've searched all over and most of the forums say that it happens probably because the proper version of the stock rom wasn't flashed.

The first time I got this phone it had loads of probably developer-esque apps such as battery tracer, bugs2go (if that's what it's called), etc.

Another interesting thing is that my bootloader is in engineering mode and i suspect that might be the reason my accelerator seems to be inverted.

I also tried to root my phone hoping i could modify some related files but everytime i flashed magisk, it doesn't root the phone.

Here's the bootloader if that explains something....
AP Fastboot Flash Mode (Not Secure)
BL:MBM-2.1-channel_retail-6bae60c-190618
Baseband: M632_17.61.01.99p CHANNEL_LATAMDSDS_CUST
Product/Variant: channel XT1952-2 32GB DVT1A

I've been super frustrated with this and any response would be more than appreciated. Thanks.

 

[CFKod]

Hi. I tried flashing a couple of different versions of XT 1952-2 (such as RETAIL, RETBR) on my phone but everytime i try to run my phone the accelerator sensor seems to be inverted.
I've searched all over and most of the forums say that it happens probably because the proper version of the stock rom wasn't flashed.

The first time I got this phone it had loads of probably developer-esque apps such as battery tracer, bugs2go (if that's what it's called), etc.

Another interesting thing is that my bootloader is in engineering mode and i suspect that might be the reason my accelerator seems to be inverted.

I also tried to root my phone hoping i could modify some related files but everytime i flashed magisk, it doesn't root the phone.

Here's the bootloader if that explains something....
AP Fastboot Flash Mode (Not Secure)
BL:MBM-2.1-channel_retail-6bae60c-190618
Baseband: M632_17.61.01.99p CHANNEL_LATAMDSDS_CUST
Product/Variant: channel XT1952-2 32GB DVT1A

I've been super frustrated with this and any response would be more than appreciated. Thanks.

When you say you magisk...have you tried to reboot to recovery mode from bootloader screen?..

My device...

Baseband Version: M632_26.100.01.120.01R CHANNEL_SUPER_CUST
Kernel Version: 4.9.112-perf+ [email protected] #1 32-bit
Java Virtual Machine: ART 2.1.0
Android Version: 9
Build Number: PPYS29.105-134-9 (cd8e0)
Build Fingerprint: motorola/channel_reteu/channel:9/PPYS29.105-134-9/cd8e0:user/release-keys
Build Description: channel_reteu-user 9 PPYS29.105-134-9 cd8e0 release-keys
Build Date: Mon Feb 10 12:39:21 CST 2020

Just patched mine

A useful trick when updating magisk version.... Patch the stock boot img in magisk manager, use the Flasher within ex kernel manager app to flash new boot img.... Reboot recovery... Saves all the fastboot stuff you do first time round

 

[Spaceminer]

If anyone gets ahold of the Android 10 soak test let me know because I want it. I got approved for it, but I'm unable to download it. The last ota "160-4" will break your ability to grab it. Stay on 160. The official build releases in 30 days if everything goes well.