[Recovery][UNOFFICIAL] TWRP Dirty Port For G7 Play

[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)

 

[BobbyBlunt]

I have not tested @Spaceminer'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.

 

[JohnSmith8786]

This method working for XT1952-6 handsets?

 

[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.

 

[DB126]

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.

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.

 

[Morricorne]

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.

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

 

[DB126]

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

You spammed the same basic question in multiple threads. Get over it; no 64bit.

 

[Viva La Android]

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.

 

[Gypsy]

Hi folks, first, thank you to @Spaceminer for all his didication to helping us with TWRP4.img and all the people who teamwork that make the thread so interresting, @Viva La Android, @ninjakira, @jasonmerc, @jwreidmoto 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.

 

[Viva La Android]

Hi folks, first, thank you to Spaceminer for all his didication to helping us with TWRP4.img and all the people who teamwork that make the thread so interresting, Viva La Android, ninjakira, jasonmerc, jwreidmoto 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.

Hello @ghislain_racine 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, @topjohnwu, gives a detailed explanation of installing Magisk to recovery in his gitbub.io support page. https://topjohnwu.github.io/Magisk/install.html

 

[Gypsy]

Hello @ghislain_racine 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, @topjohnwu, gives a detailed explanation of installing Magisk to recovery in his gitbub.io support page. https://topjohnwu.github.io/Magisk/install.html

Thanks @Viva La Android for answers and more, I will try soon !

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

Hello @ghislain_racine 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, @topjohnwu, gives a detailed explanation of installing Magisk to recovery in his gitbub.io support page. https://topjohnwu.github.io/Magisk/install.html

Thanks @Viva La Android for answers and more, I will try soon !

 

[Viva La Android]

Thanks @Viva La Android for answers and more, I will try soon !

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



Thanks @Viva La Android for answers and more, I will try soon !

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.

 

[Gypsy]

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.

@Viva La Android, 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

 

[Viva La Android]

@Viva La Android, 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

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. @Spaceminer, 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.

 

[Gypsy]

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. @Spaceminer, 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.

@Viva La Android It's rooted with Magisk, thanks so much !

 

[Viva La Android]

@Viva La Android It's rooted with Magisk, thanks so much !

I'm pleased to hear it. Glad it worked for you.

 

[fossyfosser]

Almost there!

This method working for XT1952-6 handsets?

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://forum.xda-developers.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.

 

[mtmtumbo]

Hello @ghislain_racine 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, @topjohnwu, gives a detailed explanation of installing Magisk to recovery in his gitbub.io support page. https://topjohnwu.github.io/Magisk/install.html

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

 

[JohnSmith8786]

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://forum.xda-developers.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?

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

 

[Viva La Android]

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

Devs are working on an official TWRP build over at TeamWin, although @Spaceminer'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.