• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[GUIDE][CHANNEL] Stock Android 10 for Boost Mobile Moto G7 Play

Search This thread
Motorola Moto G7 Play
Codename: CHANNEL
Boost Mobile Variant
Model No. XT1952-4

IMPORTANT NOTE:
At the time this thread was created, Motorola Mobility had not yet released the official stock Android 10 update for this variant of the CHANNEL. Because this variant has long since received the official Android 10 update, this thread is beneficial only for experimental or educational purposes. While you may certainly install RETAIL Android 10 firmware on the Sprint compatible xt1952-4, it is recommended always to install the latest official Android 10 firmware package released exclusively for this variant. Official Motorola stock firmware packages are available for the Boost Mobile/Sprint variant here https://mirrors.lolinet.com/firmware/motorola/channel/official/Sprint/

COMPATIBILITY:
Although this guide specifies the Boost Mobile (xt1952-4) variant of the CHANNEL, device owners have tested and confirmed that this Android 10 firmware is compatible with other variants/models. Namely, the MetroPCS xt1952-6 and the T-Mobile xt1952-T are confirmed. It is safe to assume that, because this is a RETAIL based official firmware build, compatibility should be universal for all region based retail models.

DISCLAIMER:
By proceeding further, you are assuming full responsibility for the operability and integrity of your device. Although this is an official firmware package, installation of firmware has an inherent risk of damaging your device or otherwise rendering it inoperable if the instructions are not followed carefully. Follow this detailed guide carefully and concisely and the installation should go smoothly. However, I am absolved of any liability in the event you break something. If you do mess something up, either myself or one of the many knowledgeable members herein will try to assist you.


OFFICIAL ANDROID 10:
For owners of the Moto G7 Play, it's no secret that the official Android 10 OTA update has already began rolling out to device owners in Brazil. As such, it probably will not be long before device owners in the US begin seeing a notification for the Android 10 update. In the meantime, for owners of the Boost Mobile variant (xt1952-4) who want to manually update to Android 10 by flashing the official Android 10 retail firmware package, I have put this simple guide together to assist you. In essence, to update manually, you will need to install the Android 10 firmware package via fastboot or RSD-Lite. This guide is premised upon the fastboot mode method. This Android 10 firmware is stable and may be used for your daily driver ROM. Look to the end of this guide for reported bugs.

BUILD INFO:
Android Version: Android 10
Build Region: RETAIL
Build No. QPY30.52-22
Kernel Version: 4.9.206-perf+
Radio Version: M632_41.178.01.156R
FSG Version: FSG-8953-25.163
Bootloader Version:2.1-channel_retail-315bc626c6-200423
System Version: 30.1.24.channel.retail.en.US
Build Date: April 13, 2020
Security Patch Level: April 1, 2020

ANDROID 10 UPDATE FEATURES:
• Optimized Fast Charging
• Bug Fixes for Battery Drain Issues
• Power Optimizations
• System-Wide Dark Theme
• Gesture-Based Navigation
• Privacy & Location Controls
• Sound Effects -- Stock Equalizer & Amplifier
• Smart Reply w/Messaging Apps
• Incognito Mode w/Google Maps
• Focus Mode
• Live Caption
• New Parental Controls
• New Moto Actions

INSTALLATION:
For those members who are not familiar with installing official firmware via fastboot mode, I will outline the exact steps below, including links to the files you'll need for the job. This guide requires a Windows PC or laptop, running Windows 7, 8.1 or 10 (32 or 64-bit). While fastboot can be used with other operating systems, this guide is outlined for Windows based systems only:

1. First, on your Windows PC or laptop, you will need to download and install the latest version of Motorola Device Manager, to ensure installation of up-to-date USB device drivers. Motorola Device Manager can be downloaded here: https://support.motorola.com/us/en/solution/MS88481

2. Next, download and install the latest fastboot and ADB utilities for flashing the firmware to your device. We will be using the Minimal ADB & Fastboot tools, version 1.4.3. On your PC or laptop, visit this link https://mega.nz/file/dVR3xCJL#GjcIXtNcCoB7R9DJtyqJ3dfOmeuGuPUvx6FKgp23yrc

3. Now download the official Android 10 retail firmware package from the Downloads section below;

4. Extract the contents of the firmware package zip you just downloaded to your Minimal ADB & Fastboot directory;

5. Boot your Moto G7 Play into AP Fastboot mode. With the device powered off, hold the power button along with the volume down button for around 8 seconds or until AP Fastboot mode appears on your device display;

6. Connect your device to your PC or laptop using the OEM supplied -- or quality equivalent -- USB to USB type C charging/syncing cable;

7. Open a command prompt in the path of your Minimal ADB & Fastboot directory. Execute the following command: fastboot devices
If your PC/laptop & device are properly synced, the command window will return an alphanumeric string synonymous with your device serial number. If you are not properly synced, try another USB syncing cable, change USB ports on your computer, or try reinstalling the USB device drivers.

**NOTES: by following these installation instructions, you will wipe your device of all userdata. Before proceeding further, make a backup of any important files and media.
Once you have confirmed proper syncing between your device and PC/laptop, execute the following fastboot commands, preferably in this order:

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
fb oem config fsg-id boost
fb oem config carrier boost
fastboot erase DDR
fastboot erase cache
fastboot erase userdata
fastboot oem fb_mode_clear
fastboot reboot

Upon reboot, your Boost Mobile Moto G7 Play will be running stock Android 10. During setup, select the "Use Mobile Data" option instead of using WiFi. This will allow your device to establish its initial 4G/LTE data connection on the Boost Mobile network. Once setup is complete, your cellular data, voice and messaging services should be functioning normally. Make a test phone call and send a test text message to confirm.

DOWNLOADS:
Android 10 Retail Firmware:
•Build No. QPY30.52-22 (April 1 SPL): https://mega.nz/file/YIZnwAAZ#17HH-vbEsbxQVPNLjvgNqdTHFI4Ow2ah6SNC4Nnw9ec
•Build No. QPYS30.52-22-2 (June 1 SPL): https://mega.nz/file/lB5gkaqK#BD-r7dSTw8dgZAfI90pJq7LB_XJvqcvSVshXbLo-yic

Android 9 Pie Stock Firmware:
• Official Firmware Builds: https://mirrors.lolinet.com/firmware/moto/channel/official/Sprint/

BUGS:
• PRL/Domestic Roaming:
When roaming outside of the home network, the device may give a mobile IP registration response error (MIP Error 67-- Mobile Node Failed Authentication), and the cellular signal may become unstable. This is most likely due to the lack of an integrated PRL (Preferred Roaming List) provisioning service within the retail firmware. I am looking for a workaround: possibly implementing the Boost Mobile radio firmware from Android 9, or including the SprintDM mobile provisioning service as an add-on;
• Gesture/Navigation Features:
As XDA Member @JohnSmith8786 has pointed out, some of the native Gesture Navigation features in the RETAIL Android 10 firmware are somewhat unstable and buggy at times. This bug has been reported to Motorola Mobility via official bug report. Since this issue does not appear to be specific to a particular variant/model, and has been reported on various different models, this issue is likely unique to the RETAIL Android 10 firmware builds, and will likely be resolved by stability improvements/bug fixes in a future OTA(s).

Please report any bugs or instabilities in comments below. Also, please provide confirmation regarding compatibility of this Android 10 firmware on specific Moto G7 Play models. In theory, this firmware should work on any model with an unlocked bootloader. As all Android enthusiasts, modders and devs know, confirmation is always better than theory.
 
Last edited:
Can confirm working on XT1952-6 & XT1952-T
Thank you very much. I will add that to my OP heading. Yeah I've noticed some slight buggy behavior on the RETAIL Android 10 gesture navigation features too. Motorola Mobility has been notified of this issue, so perhaps a future OTA will fix this.
 
Last edited:
  • Like
Reactions: JohnSmith8786
So this shouldn’t affect my modem or data connection on the Sprint Nationwide Network for Boost?
Correct. Flashing this firmware to a device active on the Boost Mobile network will continue to function normally. I have noticed some buggy behavior when roaming outside of the home network. Other than that, your device should function just as if you were using the Sprint firmware build.
 

COOLinMc

Member
Sep 16, 2016
16
2
Does anyone know if in this Android version call recording goes back to our Motorola? On Android 9 I had to root phone for enable call recording. How is it now?
 
For those with the Sprint/Boost Mobile variant of the xt1952-4, the latest OTA is live, bringing the Build No. to QPYS30.85-18-6 and the security patch level to October 1. For anybody needing it, I will try to post a link for the entire firmware package this weekend. Here is a link to the latest full firmware package for the Sprint/Boost Mobile xt1952-4 https://mega.nz/file/SmAEwRZL#M4KP8hHHEtBw5fOtHGRuGfDV8F0SUkFENVGctzJagFw
 
Last edited:
For those with the Sprint/Boost Mobile variant of the xt1952-4, the latest OTA is live, bringing the Build No. to QPYS30.85-18-6 and the security patch level to October 1.
Were you able to get Magisk running and the device rooted?

I had the Lenovo rescue tool unbrick my phone and it 30.85-18-11 and I can't get Magisk to stay on, let alone get it rooted.
 
You can I stall it via TWRP or fastboot
Let me make sure I am not misunderstanding. You want to run official stock Android 10 and root with Magisk, correct? If so, you can certainly do that, but since the Moto G7 Play does not have a boot-ramdisk, you ate forced to jump through some hoops to get Magisk installed. You are much better off flashing.offiicial Lineage OS 18.1 (Android 11) and installing Magisk using the typical boot image patching method -- the normal method. LineageOS 18.1 has a boot-ramdisk. If you do not like LineageOS, there are many official Android 11 based custom ROMs available for the CHANNEL. And a few Android 12 custom ROMs. They all include boot-ramdisk.
 
Last edited:
Let me make sure I am not misunderstanding. You want to run official stock Android 10 and root with Magisk, correct? If so, you can certainly do that, but since the Moto G7 Play does not have a boot-ramdisk, you ate forced to jump through some hoops to get Magisk installed. You are much better off flashing.offiicial Lineage OS 18.1 (Android 11) and installing Magisk using the typical boot image patching method -- the normal method. LineageOS 18.1 has a boot-ramdisk. If you do not like LineageOS, there are many official Android 11 based custom ROMs available for the CHANNEL. And a few Android 12 custom ROMs. They all include boot-ramdisk
I've never bothered with custom ROMs. My interests with rooted phones are for practicing forensics and pentesting.

I'm downloading the latest Lineage and will try it that way. I'll report back when completed or I run into issues.
 
I've never bothered with custom ROMs. My interests with rooted phones are for practicing forensics and pentesting.

I'm downloading the latest Lineage and will try it that way. I'll report back when completed or I run into issues.
Cool. Yeah let me know. Follow the install instructions for LOS 18.1 directly from the Lineage WiKi. The install is not standard TWRP like most Lineage builds. This has to be done using.adb sideload in TWRP mode with a PC.
 
That should have posted 2 hours ago.

This is what I f'ing loathe about this process because it happens virtually EVERY time regardless of the device or OS or mod that I'm doing.

The first thing I did was make sure sdk tools were updated. There were updates for Android 6 and 10, as well as two new modules to install. It took about a half hour to go through them all, but everything is updated.

Downloaded LoS, latest version, and the recovery image.

Go to the first step on the LoS install, which is to sideload a specific zip file. kay...
-reboot into bootloader, then from there to recovery
-adb sideload <the file>
-on computer: error:closed
-on phone: Error 21, footer is wrong

This nearly ALWAYS happens, and I have yet to find a fix. I google for an answer, keeping results to just within the last year, and someone on Reddit had suggested a fix that worked for the poster. His problem was that he was in stock recovery. He needed to be in LoS recovery.

I think "well, they give you a recovery image separate with the OS download, maybe it's to boot with, like TWRP." So I boot into the bootloader and try to fastboot boot <lineage recovery.img>..........and it just starts up normal. I go to settings and check the build, and it's still the Android 10 version I started with. Tried it again, same results.

So then I get the bright idea to stay where I'm at in stock OS and adb reboot <lineage recovery.img>

Now, on my phone it's in a weird Android Recovery screen. "Can't load Android system. Your data may be corrupted. If you continue to get this message...." Then it gives me two options: Try again or factory reset.

Well, my mama didn't raise no quitter, so I hit Try Again. It goes to the black screen with "N/A" on it (which is what it would do back when I had this thing rooted and everything was peachy until I forgot the lock screen pattern), but then I get that error message again.

I'm going to factory reset and see what happens. Anyone with a solution, feel free to chime in anytime.
 

Top Liked Posts