yashsingh1/xdaforums huggingface dataset:
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] :
Wow, that was really quick. So I can flash the dtbo image, though it seems the new TWRP doesn't boot. I get the following from the terminal.

fastboot flash dtbo dtbo.img
(bootloader) is-logical:dtbo_a: not found
Sending 'dtbo_a' (1507 KB) OKAY [ 0.209s]
Writing 'dtbo_a' OKAY [ 0.068s]
Finished. Total time: 0.279s

fastboot boot twrp.img
Sending 'boot.img' (22806 KB) OKAY [ 0.610s]
Booting FAILED (remote: '')
fastboot: error: Command failed

"(bootloader) is-logical:dtbo_a: not found" also happens when flashing the old dtbo.img, so I'm not sure how relevant that message is. About the dtbo.img however, it seems I can't boot at all with the new dtbo. I get stuck on the "bad key" message when trying to boot up the phone. I could still flash the old dtbo though so the phone still works for me.

Thanks again for working on this device.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
Try flashing your stock dtbo then booting twrp. That might work.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] :
It seems that the new twrp image isn't working for me regardless of the dtbo. I used fastboot --set-active=b (as I hadn't yet flashed dtbo to the b slot), then booted twrp.img. However, I get a black screen for a bit, then the phone just boots the OS normally.

Additionally now, switching back to --set-active=a, I get a bootloop for a few times trying to start up the phone (shows the bad key screen, vibrates, black screen, repeat). Then I get a message that the system couldn't start, prompting me to either try booting again, or to perform a factory reset. Oddly enough, the flashing the old dtbo in a-slot again doesn't seem to fix it. Not sure what happened there, hopefully I don't screw anything up on the b slot, which still boots.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
Do you have an OS installed to both slots? If so, then it's a problem on my end and I think I know how to fix it. If not make sure your firmware is installed to A & B, then try again. You shouldn't need to set any slot as active, twrp should be handling that automagically when you try to boot it up.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] :
I'm not sure if I have an OS in both slots, though I do have a system_a and system_b partition. I haven't installed any ROMS, or flashed to the recovery partition. I believe the only things I've done are switching slots in fastboot, flashing the dtbo_a partition and attempting to boot twrp. So I think my phone should be pretty close to stock, except for the flashed dtbo_a.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
Hey [MENTION=7718083]Spaceminer[/MENTION], I've been off the map for a few days traveling and have not yet had an opportunity to try things out. I'll indulge in some catch-up reading on the thread and try to get up to speed.

Oh, I wanted to inform owners of the Boost Mobile xt1952-4 that our default MSL code appears to be 000000. For any members who want to access the programming menu, open your dialer and enter ##3282#. Select a field such as "APN Settings" and then choose "Edit." When prompted to enter your MSL code, enter 000000 and you should be in. It works on my Boost Moto G7 Play, and may possible even work on other variants. However, please employ ample caution with the programming menu. It will allow you to do things like change LTE band priority, disable and enable supported bands, change the default APN configuration, etc. Your cellular signal and service can be adversely affected or broken by altering the default fields in this menu. In the event you do have a mishap and lose service or data connectivity, dial ##72786# to prompt a full network configuration reset. Upon reboot you should be back to normal. You can likewise prompt a BRAND carrier reset by dialing ##27263# (which appears to do the same thing as ##72786#).

I apologize for the off-topic post. I recalled they there were a few Boost device owners on this thread and wanted to pass the info along.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] nabilps5:
I do not know how to thank you :good::good::good:

I have made my device root using your method :cowboy::cowboy:

Thank you Thank you Thank you Thank you Thank you Thank you

My phone

Moto G7 play XT1952-1 :cool:
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Guhl0rd64:
I think this TWRP a bit strange, because after I installed it, my Moto G7 Play, It is no longer vibrating for anything, either when I boot, nor when I get a call, or when I use the navigation bars, I need some help if I can !!

(Yes i know my english is horrible)
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] BobbyBlunt:
I have not tested [MENTION=7718083]Spaceminer[/MENTION]'s last twrp build yet. I plan on giving it a try this weekend.

Hopefully i am able to patch it with magisk to get both twrp and root.

I see a few people have already started flashing Android 10 GSI rims, but for now my goal is twrp and root.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] JohnSmith8786:
This method working for XT1952-6 handsets?
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Morricorne:
Now need to wait stable twrp build. Then working 64bit custom rom.

No other chooice. I buyed this moto a half month ago.

Im poor, i dont have money, to buy new moto g7 power. Where i have 64bit ARMv8-A CPU and os.

Keep it UP good work dev.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] DB126:
Unlikely on both fronts as there is little development interest in this device. 64-bit will buy exactly nothing given modest specs. That said, stock ROM is clean and performs well rooted or not. Magisk and a few modules will go a long way toward satisfying the tinker twitch.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Morricorne:
Your thoughts not interest me. And i know any custom rom is clean compare to any Stock rom.

I owned many android devices, where almost every time i flash Cyanogenmod or Lineageos. I started my Custom Rom Android Adventure with ZTE Blade in 2011 and now stuck on Moto Device.

I ask simple question. Its 64bit rom or no?

If you cant simply answer to my question. Then just wont say anything
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] DB126:
You spammed the same basic question in multiple threads. Get over it; no 64bit.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
For owners of the Sprint compatible xt1952-4, the latest OTA is live, Build No. PCYS29.105-134-6, with the December 1st security patch level. If the rumors are correct, official Android 10 for the G7 Play should be rolling out very soon.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Gypsy:
Hi folks, first, thank you to [MENTION=7718083]Spaceminer[/MENTION] for all his didication to helping us with TWRP4.img and all the people who teamwork that make the thread so interresting, [MENTION=10059830]Viva La Android[/MENTION], [MENTION=7843264]ninjakira[/MENTION], [MENTION=5006327]jasonmerc[/MENTION], [MENTION=9918609]jwreidmoto[/MENTION] for all his questions and all others.

In order to root this phone, I interrested to this post. I have a Motorolla G7 Play XT1952-4 PSB29-105-134-4 RETCA.

I read all the posts in that thread, I understand that there's is no ROOT solution with magiks so far, doesn't it ?

But it seems to have way to installed TEMPORARLY the TWRP by install it from the RAMDISK with TWRP4.img, doesn't it ?

Once TWRP4.img is installed in RAMDISK, it's seems possible to patched PERMANENTLY the BOOT image with TWRP4.img, doesn't it ?

I rooted few phones by fellowing step by steps a procédure. I'm not familiar with all the Fastboot commands that required a A/B boot system.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
Hello [MENTION=5768479]ghislain_racine[/MENTION] and welcome. Yes, this A/B partitioning scheme has certainly changed the conventional methods for rooting Android devices. On the Moto G7 Play, since the ramdisk no longer resides within the /boot partition, Magisk has no other choice than to be installed to the /recovery partition. Using the boot image patching method from Magisk Manager, it is necessary to select the "Recovery Mode" option in Advanced Settings before patching your boot image. And, of course, once the Magisk patched boot image has been installed to your device, both Magisk and recovery mode reside in the same place. Booting to recovery is then nececessary during every reboot on order for your Android OS to run Magisk systemless root.

To answer your question, yes the Moto G7 Play (including the xt1952-4) has a Magisk root solution. However, the A/B partition scheme and the system-as-root configuration of our device mandates booting to recovery in order to properly use Magisk.

I hope I've explained this correctly, and I would ask one of the more learned members to correct my dictum if I've made any mistakes. My device is also the xt1952-4 (Boost Mobile) and I'm running Magisk systemless root via the recovery mode method.

Magisk's creator and maintainer, [MENTION=4470081]topjohnwu[/MENTION], gives a detailed explanation of installing Magisk to recovery in his gitbub.io support page. https://topjohnwu.github.io/Magisk/install.html
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Gypsy:
Thanks [MENTION=10059830]Viva La Android[/MENTION] for answers and more, I will try soon !

---------- Post added at 08:30 PM ---------- Previous post was at 08:30 PM ----------

Thanks [MENTION=10059830]Viva La Android[/MENTION] for answers and more, I will try soon !
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
Anytime friend. First and foremost, grab yourself the stock boot image for your device, preferably by extracting it from a stock firmware package. The RETCA xt1952-4 stock Moto firmware can be downloaded from here. https://mirrors.lolinet.com/firmware/moto/channel/official/RETCA/

Once you have the stock boot image, you can proceed with the boot patching process. Good luck and let us know if you need any help.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Gypsy:
[MENTION=10059830]Viva La Android[/MENTION], after have patched my boot.img as recovery image by manually check “Recovery Mode” in Advanced Settings!... In order to flash the patched boot/recovery image I had boot into bootloader to issu the follwing command ... anf finaly have the message "(bootloader) Invalid partition name recovery FAILED (remote failure)"

Did I do something wrong or this message is normal ?

C:\adb\platform-tools>fastboot flash recovery magisk_patched.img

target reported max download size of 536870912 bytes

sending 'recovery' (17677 KB)...

OKAY [ 0.515s]

writing 'recovery'...

(bootloader) Invalid partition name recovery

FAILED (remote failure)

finished. total time: 0.515s

I also had the the BAD KEY message in reboot process. I guess I did something wrong ?

Sorry about poor quality of my english
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
Your English is okay. I understand you my friend. Okay. The command you are actually supposed to execute is:

fastboot flash boot magisk_patched.img

I know, it is a bit confusing, because Magisk isn't actually being installed to /boot per se, but instead it's going to /recovery. But, Magisk patched the boot image so that it will install correctly when you chose "Recovery Mode" during the patching process. Flash it to /boot instead of /recovery and you should be good.

The bad key notification is normal. It isn't an error. It just means your bootloader is unlocked.

Once you flash the patched boot image, you will need to boot your device as if you were booting into recovery mode. Again, I know this is very unorthodox compared to the traditional way of rooting, but booting your device into recovery each time you need to reboot will boot your Android OS with Magisk installed and active. [MENTION=7718083]Spaceminer[/MENTION], if I'm missing anything please correct me, or any other members with any input on this. I'm going strictly off memory on these steps. I know you must use fastboot flash boot magisk_patched.img, but I hope I'm not missing anything after that.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Gypsy:
[MENTION=10059830]Viva La Android[/MENTION] It's rooted with Magisk, thanks so much !
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
I'm pleased to hear it. Glad it worked for you.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] fossyfosser:
Almost there!

I don't see why not... they are practically giving them away... I unlocked the bootloader less than 30 minutes after getting one. Only string was a month of Metro service and a $15 activation. Carrier unlocking is 180 days acording to TOC or 90 days according to rep.

Step one to Root the Metro PCS XT1952-6:

1. Get a stock image... flash it.... don't update.

https://xdaforums.com/moto-g7/how-to/channel-moto-g7-factory-firmware-images-t3996303

2. Patch the recovery image using magisk manager...

That's where I'm stuck, which one is the recovery image?

adspso.bin CHANNEL_PPYS29.105-134-4_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt fsg.mbn NON-HLOS.bin regulatory_info_default.png system_b.img_sparsechunk.0 system.img_sparsechunk.1 system.img_sparsechunk.4 system.img_sparsechunk.7
boot.img dtbo.img gpt.bin oem.img servicefile.xml system_b.img_sparsechunk.1 system.img_sparsechunk.2 system.img_sparsechunk.5 vendor.img
bootloader.img flashfile.xml logo.bin oem_other.img slcf_rev_d_default_v1.0.nvm system.img_sparsechunk.0 system.img_sparsechunk.3 system.img_sparsechunk.6

Update:

I've got root!!!

Did https://topjohnwu.github.io/Magisk/install.html#boot-image-patching

just remember to select "recovery" under advanced options for magisk manager.

after flashing the stock image onto my MetroPCS phone. Now I have no Metro garbage and root.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] mtmtumbo:
I'm having problems rooting as well on my g7 play (RETCA)

I select recovery in magisk and patch the boot.img on my xt1952-4, but after it reboots, all i see are xxxxxx-xxxxx-xxxxxx-xxxxxx-xxxxx and the phone reboots in a loop

do you have to run the fastboot flash boot twrp.img command on both partitions?

and what is the correct firmware to use for RETCA? there are 4 versions on the link you provided earlier (I am using XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-134_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC) but perhaps the boot.img is the wrong one for my phone
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] JohnSmith8786:
Thanks for the response, yeah it's tricky, it's a nice little device aside from the 2gb of ram. I figured the devs would be all over this thing. I picked up a redmi 7 basically the same phone with more ram and a larger battery
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
Devs are working on an official TWRP build over at TeamWin, although [MENTION=7718083]Spaceminer[/MENTION]'s unofficial build is very stable. Far as custom ROM development goes, it's not a priority because the G7 Play is fully Project Treble supported. There are at least a half dozen Android 10 GSI builds that work great on this device, not to mention a few smooth Pie builds.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
When you say the twrp is very stable what do you mean exactly, does the twrp stick with the stock rom (other twrp4 bootloops once the stock rom has data) , are you able to flash magisk zip in this twrp(like you can with river and ocean) and obtain root (eliminating having to not have to use the magisk patched img) and are you able to make nanodroids on the other twrp4 if you restored a backup the device would never boot I restored and made backup to external storage tho. I'm also a boost G7 play user like yourself
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] jonthn41:
hey just a heads up, some of u that boot to a black screen with a bunch a numbers like 12423-121230-123123-123 or something like that but wont fully boot. i was have ing the same problem . but then i was pressing voL+ (or maybe vol-) while rebooting and a screen popped up asking me to retry or factory data reset. I factory data reset. then rebooted to recovery and... it booted, rooted with magisk and got it to boot the same way.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
The number things is the bootloader signing the magisk boot with the bootloader key

([emoji3590]09-09-18[emoji3590])

---------- Post added at 07:29 AM ---------- Previous post was at 06:32 AM ----------

Damn this post be dead

([emoji3590]09-09-18[emoji3590])
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] JohnSmith8786:
Right on, did you stay stock? If not what GSI did you try? I RSD Lite flashed a stock xt1952-4 firmware file (PPY29.105.116) took care of all the metro bloat for me
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] fossyfosser:
I got DOT 9 to work and found the nav button settings... but no mobile data. Stock Retail 9 is good. I ended up being fine with MetroPCS 9, and removed the bloat with debloater. Wish I could get 10 thought for the better VPN DNS handling. Having to manually select Recovery for root is tedious and inherently less reliable.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] thenatti:
For those who bootloader's display bad key and Rand numbers I made boot.logo images for our phone the ones with the white backgrounds hide the message it's in a thread on the main page for the G7 play forums
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Crazy I been asking you I get my mobile data to work on GSI with boost Mobile and you couldn't even DM me the solution bro like a 5 minute answer like it isn't that hard like please I need this

---------- Post added at 09:26 PM ---------- Previous post was at 09:23 PM ----------

There's a error with your boot logos ..there is like a black screen when putting it into the charger before the charging animation comes on showing it's charging (the flash logo before the charging number one)also when you fastboot into twrp shows same Black screen instead of bin and then booting into TWRP other than that there great currently using one
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
[MENTION=7815789]PoochyX[/MENTION], as I explained in the PM, I'll be posting a guide on GSI ROMs and enabling mobile data with Boost Mobile, Sprint, Virgin Mobile, etc.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Under stand bro but why not just DM me the solution I need real quick so I can get right

([emoji3590]09-09-18[emoji3590])
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
I don't do support by PM. That doesn't help other users on the forums. There are several Boost G7 Play users needing help with mobile data on GSI ROMs. It's not just a quick solution. While it's not overly complex, it does involve sequential steps and reboots.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
It's just frustrating other users with different variants don't be having the issue of there signal bar going in and out not being able to hold signal they just set there apn settings and were good to go it just makes me feel like my G7 play is defected some how

([emoji3590]09-09-18[emoji3590])
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
Yeah there are several. I've had numerous PMs on the issue. That's the very reason i opted to post a guide.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
It's very typical as well for CDMA Moto devices to experience RIL & cellular data issues when running ROMs other than stock, especially Sprint compatible devices. This is an issue dating all the way back to the 1st Gen Moto G and Moto E series. (It took months to establish cellular data on the Sprint Moto E4 [SPerry] on custom ROMs.) This is due to the unique carrier provisioning used by Sprint, its MVNO & subsidiary providers. Unlike GSM carriers (and even Verizon on the CDMA side), Sprint isn't as simple as merely putting an active UICC (SIM) in a device to establish telephony and a data connection. On Sprint and its respective providers, the UICC number (ICCID) must be uniquely paired with the device's MEID in order to activate service. Even then, the UICC cannot normally be transferred between devices. (It is possible, but requires nv data modding). I'm presently testing a data enabling mod that can simply be installed via TWRP that will dispense with all the steps involved on the xt1952-4 Sprint compatible Moto G7 Play on GSI ROMs. Also, to the OP of this thread, I do apologize for the off-topic colloquy. I will soon post a thread for this topic and move related discussions there accordingly.

Update: I've made a thread here: https://xdaforums.com/g7-play/how-to/guide-cellular-data-sprint-compatible-t4037297
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] alecxs:
this is not related to TWRP but the dtbo.img you flashed
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] BobbyBlunt:
So I have actually had a chance to tinker with this thing some more

I was able to get TWRP to stick, but as soon as you boot the stock rom once, the recovery will bootloop. From what I am seeing you guys that flashed a gsi do not have this issue (any of the gsi roms I have tried to flash so far have failed so I was unable to test that out for myself.)

Also patching TWRP directly did not work. I tried patching it with the latest canary build of magisk

It seems as though the encryption is the problem. Install twrp, boot stock rom, and the recovery bootloops. Do not boot the stock rom and recovery is fine. After running the stock rom and then going back and booting twrp using fastboot I notice everything is encrypted.

Also [MENTION=7718083]Spaceminer[/MENTION] I tried both your BST twrp test, and your dtbo with dm-verity disabled. Neither appears to have worked. I am on the boost version of the device.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
I'm on the boost G7 play also and the majority of GSIs do boot, this is not a offical Verison of twrp so encryption is not completed removed on the stock rom for some reason once first boot is completed the rom re encrypts itself and twrp is not usable it does stick on GSI (but then you wouldn't have root cause the only way to root as of now is with the patched magisk img flashing magisk in twrp doesn't work in this twrp like it does for river and ocean) unless you use lineage 9 by andy yan which has lineage root or a phusson rom with baked in su also if you make twrp stick on the GSI when you use the decrypt zip it breaks lockscreen so you can't use pin code password or swipe... Hopefully we get an offical twrp in the future so we can obtain magisk via flashing in twrp and still have twrp in the ramdisk

/09/[emoji645]/[emoji725]/
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
Once you have twrp installed to the ramdisk, format data using the type "yes" to continue method. Then use twrp's menus to reboot directly back into twrp, and manually mount /vendor, /data, and /system with the check boxes, then flash the universal disabler. I personally use the 5.21.2019 release because later versions don't disable encryption properly for some reason. You can find a copy of that in the attachments of my twrp thread for the G6 Play if you need it.

If that doesn't work, pull /vendor/etc/fstab.qcom open it with a text editor, find forceencrypt and change it to encryptable. Copy it back to /vendor/etc and set permissions to 0644. You can do this from twrp using the build in file manager. Just make sure to mount /vendor first or you won't see anything. Format using the "yes" option in twrp after replacing your fstab and reboot. Encryption should stay disabled unless you reflash your vendor.img.

If for some crazy reason none of that works, send me the fstab and your boot.img.

---------- Post added at 10:38 AM ---------- Previous post was at 10:34 AM ----------

If you need root on Lineage OS 17 see this post. Magisk is broken for me too on Android 10 builds.