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

[PoochyX]

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.

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

Sent from my moto g(7) play using Tapatalk

 

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

 

[PoochyX]

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.

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

 

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


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.

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

 

[fossyfosser]

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

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.

 

[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

 

[PoochyX]

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.

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

Sent from my moto g(7) play using Tapatalk

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

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

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

Sent from my moto g(7) play using Tapatalk

 

[Viva La Android]

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

 

[PoochyX]

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

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

 

[Viva La Android]

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

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.

 

[PoochyX]

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.

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

 

[Viva La Android]

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

Yeah there are several. I've had numerous PMs on the issue. That's the very reason i opted to post a guide.

 

[Viva La Android]

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://forum.xda-developers.com/g7-play/how-to/guide-cellular-data-sprint-compatible-t4037297

 

[aIecxs]

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

this is not related to TWRP but the dtbo.img you flashed

 

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

 

[PoochyX]

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

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]/

 

[Spaceminer]

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

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

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]/

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

 

[PoochyX]

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

Why isn't magisk flash able with this twrp like it is with river and ocean leaving us with the only option of flashing magisk patched img

/09/[emoji645]/[emoji725]/

---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------

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.

Are there any GSI or with stock flashing magisk in twrp will work

/09/[emoji645]/[emoji725]/

 

[Spaceminer]

Why isn't magisk flash able with this twrp like it is with river and ocean leaving us with the only option of flashing magisk patched img

/09/[emoji645]/[emoji725]/

---------- Post added at 05:43 PM ---------- Previous post was at 05:40 PM ----------

Are there any GSI or with stock flashing magisk in twrp will work

/09/[emoji645]/[emoji725]/

If encryption was enabled it will prevent Magisk from flashing. Other than that, you should be able to just install Magisk. If Magisk breaks twrp, then it's a Magisk issue. The process should be, install twrp to the ramdisk, then patch the same boot.img with Magisk. Have you tried Magisk 19.3?

 

[PoochyX]

If encryption was enabled it will prevent Magisk from flashing. Other than that, you should be able to just install Magisk. If Magisk breaks twrp, then it's a Magisk issue. The process should be, install twrp to the ramdisk, then patch the same boot.img with Magisk. Have you tried Magisk 19.3?

So you was able to have magisk and twrp to work on stock and have twrp and magisk to work on Android 9 GSI (and that magisk flashing in twrrp for Android 10 GSIs are broken only way to get magisk to work on android 10 GSI is with magisk patched img with recovery mode set which eliminates you using twrp threw recovery) in regards to restoring a twrrp backup does restoring work from external SD card or you can only restore from internal storage like river and ocean

/09/[emoji645]/[emoji725]/