Magisk on G7 Play XT1952-4 Installed Succesfully

[pbarrette]

Do you guys know if this solution will work for CHANNEL_T_QPY30.85_18_9_cid21_subsidy_MPCS_RSU_QCOM_regulatory_XT1952_6_CFC.xml?
When I use MagiskManager 8.0.7 I get a patched image around 17.6mb. I can successfully flash it. When I reboot and get to the lock screen I am unable to swipe to unlock the screen. The touchscreen and fingerprint sensor are completely dead. The power and volume buttons work, but I'm essentially locked out of the phone without any touch sensors working. When I reflash the original boot.img I still have the same problem. I have to resort to a full firmware reflash to fix the problem.

Hi @coderasm

I don't know.

Which boot image were you patching? The one from your firmware version or the one that M47Z uploaded? If it's M47Z's boot image, then I'm not entirely surprised there are issues since you usually can't mix and match partition images across different firmware versions.

In either case, why don't we try to find out? If you're willing to give it a shot, this boot image is pre-patched with Magisk 21.4 and is based on the MetroPCS QPY30.85_18_9 image for XT1952-6 that you mention above.

For everyone else out there, my AndroidFileHost Folder currently has Magisk infused boot images for:
magisk_patched_METROPCS_10_QPY30.85-18-9.img (Untested)
magisk_patched_RETAIL_10_QPYS30.52-22-12.img (Tested, working)
magisk_patched_RETUS_10_QPYS30.85-23-3.img (Tested, working)

Also, as a side-note, my device is the XT1952-T, T-Mobile US, Revvlry variant. I got it SIM unlocked from T-Mo, then bootloader unlocked via Motorola's website. I have installed both the RETAIL and RETUS firmware and both seem to work without issue.

The device isn't my primary device and it has a data-only SIM in it, so I can't speak to VoLTE or VoWiFi functionality.

 

[coderasm]

Hi @coderasm

I don't know.

Which boot image were you patching? The one from your firmware version or the one that M47Z uploaded? If it's M47Z's boot image, then I'm not entirely surprised there are issues since you usually can't mix and match partition images across different firmware versions.

In either case, why don't we try to find out? If you're willing to give it a shot, this boot image is pre-patched with Magisk 21.4 and is based on the MetroPCS QPY30.85_18_9 image for XT1952-6 that you mention above.

For everyone else out there, my AndroidFileHost Folder currently has Magisk infused boot images for:
magisk_patched_METROPCS_10_QPY30.85-18-9.img (Untested)
magisk_patched_RETAIL_10_QPYS30.52-22-12.img (Tested, working)
magisk_patched_RETUS_10_QPYS30.85-23-3.img (Tested, working)

Also, as a side-note, my device is the XT1952-T, T-Mobile US, Revvlry variant. I got it SIM unlocked from T-Mo, then bootloader unlocked via Motorola's website. I have installed both the RETAIL and RETUS firmware and both seem to work without issue.

The device isn't my primary device and it has a data-only SIM in it, so I can't speak to VoLTE or VoWiFi functionality.

I was patching the one from my firmware version. I made some dumb mistakes which I know better not to do now. I ended up erasing the phone's IMEI somehow and could not bring it back after flashing stock firmware. I took it to the metropcs store and played dumb like the phone stopped working for some reason and they said they would send it back to be fixed free of charge. I had flashed it back to the stock firmware and locked the bootloader again. When I get the g7 play back I will try your patched boot image. So in the meantime while I wait for the phone to come back I had to get a another phone. I ended up getting the same phone you have, the XT1952-T, T-Mobile US, Revvlry variant. How did you get the bootloader unlocked? I tried submitting the unlocker codes for my phone to the motorolla site, but it said the phone was not eligible for unlocking. Do I have to get the sim unlocked from tmobile first before getting the bootloader unlocked? Thanks for your help.

 

[pbarrette]

Hi @coderasm,

You know that Moto keeps track of bootloader unlocks and may refuse to fix your -6, right?

I purchased my XT1952-T from a brick and mortar T-Mobile store and paid in full. I asked T-Mobile support to SIM unlock it immediately and they agreed since I was a post-paid customer with no financed devices and years of account history. Otherwise, you need to have the phone active for 30 or 45 days before they allow you to SIM unlock.

I didn't request my bootloader unlock from Motorola until months after the SIM unlock, so I don't know if there is a delay between purchasing and the IMEI becoming eligible on the Moto bootloader code site. I also don't know if you have to be SIM unlocked first, but my phone was.

 

[coderasm]

Hi @coderasm,

You know that Moto keeps track of bootloader unlocks and may refuse to fix your -6, right?

I purchased my XT1952-T from a brick and mortar T-Mobile store and paid in full. I asked T-Mobile support to SIM unlock it immediately and they agreed since I was a post-paid customer with no financed devices and years of account history. Otherwise, you need to have the phone active for 30 or 45 days before they allow you to SIM unlock.

I didn't request my bootloader unlock from Motorola until months after the SIM unlock, so I don't know if there is a delay between purchasing and the IMEI becoming eligible on the Moto bootloader code site. I also don't know if you have to be SIM unlocked first, but my phone was.

Thanks for the clarification. I didn't think about motorola keeping a log of me requesting a bootloader unlock code. Oh well, the phone was dirt cheap. I bought my revvlry from a brick and mortar store and have a years old account with metro/tmobile as well. I'll try contacting tmobile directly if the gplay doesn't pan out.

 

[LuisFernando97]

@daftshanks Good evening friend, I hope you are having an excellent weekend. I strongly ask you on behalf of all the users who have this particular device and model to update or make a new post about Android 10 with Magisk very kindly and thank you very much in advance.

 

[hellomrwhite]

RETRACTED

 

[motog7playtest]

Lurking but never posted.

I have two identical Moto G7 Play XT1952-6 (Apparently MetroPCS)
Magisk working on one, and not the other.

Device #1:
BL: MBM-2.1-channel_t-272b230-190614
Magisk adb sideload via twrp worked.
Sequence approx.: TWRP > LOS > TWRP > Magisk adb sideload

Device #2:
BL: MBM-2.1-channel_t-9edb71e-190923
Magisk did NOT work using adb sideload via twrp

I also tried many other variations, wipe everything, Magisk first, last, using LineageOS recovery, TWRP, etc on the second Moto G7 Play, but I have not be able to get Magisk to work. The first one worked relatively easily (but I have done so many tests, that I don't specifically remember the sequence that worked)

Posting this in case it might be of use to someone. I will try updating the bootloader once I am certain that I won't mess anything up since, I don't really need to root, just doing it more for the learning/research/experimentation.

Magisk 22.1
LineageOS 18.1 up to date
LineageOS recovery subsequently replaced by TWRP
adb and fastboot from linux

Specific actions/commands in sequence (approx??):
UI: Android debug activate
adb reboot bootloader
fastboot oem get_unlock_data
fastboot oem unlock XXX......
fastboot reboot
UI: Android OEM unlock
adb reboot bootloader
fastboot boot twrp-3.5.2_10-0-channel.img
adb sideload lineage-18.1-20210411-nightly-channel-signed.zip
adb reboot system
UI: Android debug activate
adb reboot recovery
adb sideload twrp-installer-3.5.2_10-0-channel.zip
adb reboot recovery
adb sideload Magisk-v22.1.zip
adb reboot system

Android rooted, confirmed by Magisk app in LOS