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

[BobbyBlunt]

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.

Will give this a try as soon as I get home. Wasn't expecting such a quick reply. Thank you and thank you for helping us get this far

 

[PoochyX]

Will give this a try as soon as I get home. Wasn't expecting such a quick reply. Thank you and thank you for helping us get this far

Spaceminer I followed the instructions that you wrote Bobby blunt about getting TWRP to work with stock and it didn't work used the zip from the G6 forum and that didn't work the issue with TWRP after stock rom had data persisted of it not opening like Bobby blunt explained so I then went into the fstab file with a text editor and it already said encryptable (posting screenshot) this issue doesn't occurr on the GSIs TWRP does stick there after GSI has data but doesn't happen with stock what are we doing wrong that it's not working if you can definitely say u got TWRP to stick on the G7 play stock rom ?

Sent from my moto g(7) play using Tapatalk

 

[Spaceminer]

Spaceminer I followed the instructions that you wrote Bobby blunt about getting TWRP to work with stock and it didn't work used the zip from the G6 forum and that didn't work the issue with TWRP after stock rom had data persisted of it not opening like Bobby blunt explained so I then went into the fstab file with a text editor and it already said encryptable (posting screenshot) this issue doesn't occurr on the GSIs TWRP does stick there after GSI has data but doesn't happen with stock what are we doing wrong that it's not working if you can definitely say u got TWRP to stick on the G7 play stock rom ?View attachment 4939049

Sent from my moto g(7) play using Tapatalk

Can you pull /vendor/etc/fstab.qcom and send it to me? The readout from running

cat /proc/cpuinfo

would also be helpful. And one more thing; what's your firmware channel? (RETUS, RETEU?) I'm going to see if I can fix this up tonight.

 

[PoochyX]

Can you pull /vendor/etc/fstab.qcom and send it to me? The readout from running

cat /proc/cpuinfo

would also be helpful. And one more thing; what's your firmware channel? (RETUS, RETEU?) I'm going to see if I can fix this up tonight.

I'm a boost user however I'm on retail firmware (still using sprint firmware modem so I won't get sim lock while I'm on retail firmware cause my device is not network unlocked)

Sent from my moto g(7) play using Tapatalk

 

[PoochyX]

Fstab (untouched) and CPU info readoutView attachment G7.zip

Sent from my moto g(7) play using Tapatalk
View attachment 4941451

 

[Spaceminer]

Fstab (untouched) and CPU info readoutView attachment 4941443

Sent from my moto g(7) play using Tapatalk
View attachment 4941451

Are you using the most recent build, RETAIL_9.0_PPYS29.105-134-7?

 

[PoochyX]

Are you using the most recent build, RETAIL_9.0_PPYS29.105-134-7?

Yeah bro I flashed back from lineage17 to help you get this twrp4 hopefully evolved to twrp 5 and you fixing that phh zip for us G7 play users

Sent from my moto g(7) play using Tapatalk
View attachment 4941461

 

[Spaceminer]

Yeah bro I flashed back from lineage17 to help you get this twrp4 hopefully evolved to twrp 5 and you fixing that phh zip for us G7 play users

Sent from my moto g(7) play using Tapatalk
View attachment 4941461

Make sure you have the stock OS installed to both slots. Also make sure encryption is disabled. Try using fastboot boot twrp.img then try flashing the installer. After flashing the zip, use the menus in twrp to reboot directly back into recovery.

After rebooting into twrp wipe > format > type "yes" to continue. Reboot directly into twrp from the menus once more. See if you can mount /data. If that works, flash any recent version of magisk that you know works on stock. If you run into any errors let me know.

If everything goes well... Let the OS boot up once, and see if Magisk is installed. If it's good to go, reboot into recovery and verify that twrp is working. If you have both, try making and restoring a fresh backup.

Just a note, if you run LOS 17 and need root, flash the stock unmodified boot.img before flashing phh superuser.

Download: twrp.img

 

[PoochyX]

Make sure you have the stock OS installed to both slots. Also make sure encryption is disabled. Try using fastboot boot twrp.img then try flashing the installer. After flashing the zip, use the menus in twrp to reboot directly back into recovery.



After rebooting into twrp wipe > format > type "yes" to continue. Reboot directly into twrp from the menus once more. See if you can mount /data. If that works, flash any recent version of magisk that you know works on stock. If you run into any errors let me know.



If everything goes well... Let the OS boot up once, and see if Magisk is installed. If it's good to go, reboot into recovery and verify that twrp is working. If you have both, try making and restoring a fresh backup.



Just a note, if you run LOS 17 and need root, flash the stock unmodified boot.img before flashing phh superuser.



Download: twrp.img

Alright im going to test this out and report to you... hopefully this will be TWRP 5 ( that megaupload is that twrp 4 or a new revised twrp)

Sent from my moto g(7) play using Tapatalk

 

[PoochyX]

Alright so the twrp installer zip patched twrp to the ramdisk without me having to manually patch to the ramdisk inside of twrp however after flashing decryption zip after stock boots up the rom is still encrypted (so twrp didn't stick still) so the flashing of the magisk zip didn't work also this twrp you posted on mega is the twrp 4 which is the one I was using when I encountered the issue of flashing the phh zip in Los so that still didn't work and I wasn't able to aquire root in Los

Sent from my moto g(7) play using Tapatalk

 

[Spaceminer]

Alright so the twrp installer zip patched twrp to the ramdisk without me having to manually patch to the ramdisk inside of twrp however after flashing decryption zip after stock boots up the rom is still encrypted (so twrp didn't stick still) so the flashing of the magisk zip didn't work also this twrp you posted on mega is the twrp 4 which is the one I was using when I encountered the issue of flashing the phh zip in Los so that still didn't work and I wasn't able to aquire root in Los View attachment 4941499

Sent from my moto g(7) play using Tapatalk

What I just uploaded is definitely not twrp4. Did you flash the disabler immediately after flashing the twrp installer?

Edit: When you boot into recovery does it take you to the stock recovery, or twrp?

 

[PoochyX]

What I just uploaded is definitely not twrp4. Did you flash the disabler immediately after flashing the twrp installer?



Edit: When you boot into recovery does it take you to the stock recovery, or twrp?

I assume they were cause the mega upload is the same exact size as twrp 4, I reflashed stock firmware fast booted into twrp flashed the installer then I rebooted formated data then did magisk then installed decryption zip and rebooted magisk not installed and device still encrypted

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

---------- Post added at 04:39 AM ---------- Previous post was at 04:35 AM ----------

Also tried flashing the los root zip before on clean boot img and still gave me that error

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

---------- Post added at 04:42 AM ---------- Previous post was at 04:39 AM ----------

What I just uploaded is definitely not twrp4. Did you flash the disabler immediately after flashing the twrp installer?



Edit: When you boot into recovery does it take you to the stock recovery, or twrp?

It's takes me to twwrp but it doesn't open cause the device is still encrypted

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

 

[Spaceminer]

I assume they were cause the mega upload is the same exact size as twrp 4, I reflashed stock firmware fast booted into twrp flashed the installer then I rebooted formated data then did magisk then installed decryption zip and rebooted magisk not installed and device still encrypted

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

---------- Post added at 04:39 AM ---------- Previous post was at 04:35 AM ----------

Also tried flashing the los root zip before on clean boot img and still gave me that error

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

---------- Post added at 04:42 AM ---------- Previous post was at 04:39 AM ----------

It's takes me to twwrp but it doesn't open cause the device is still encrypted

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

You need to format data using the yes option, then reboot directly back into twrp by using the menus. Mount /data, /vendor, & /system, then flash the disabler, remount /data, /vendor, & /system again and flash Magisk last.

If you follow those steps exactly, it "should" work.

 

[PoochyX]

You need to format data using the yes option, then reboot directly back into twrp by using the menus. Mount /data, /vendor, & /system, then flash the disabler, remount /data, /vendor, & /system again and flash Magisk last.



If you follow those steps exactly, it "should" work.

Alright I will try it that way hopefully it will make a difference

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

---------- Post added at 05:10 AM ---------- Previous post was at 04:51 AM ----------

I did it the exact way you said and Device is still encrypted which means twrp doesn't stick and magisk is still not installed, and los zip still didn't work its something with this recovery and on a GSi I tried a back up from internal storage and device boot looped

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

 

[Spaceminer]

Alright I will try it that way hopefully it will make a difference

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

---------- Post added at 05:10 AM ---------- Previous post was at 04:51 AM ----------

I did it the exact way you said and Device is still encrypted which means twrp doesn't stick and magisk is still not installed, and los zip still didn't work its something with this recovery and on a GSi I tried a back up from internal storage and device boot looped

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

I might've just found the problem. There was an interesting line in the prop.default of the stock boot.img, persist.vold.ecryptfs_supported=true. And the boot csv number was wrong in twrp. I'm going to change it to false, make a modified boot.img, and make another recovery.

 

[PoochyX]

I might've just found the problem. There was an interesting line in the prop.default of the stock boot.img, persist.vold.ecryptfs_supported=true. And the boot csv number was wrong in twrp. I'm going to change it to false, make a modified boot.img, and make another recovery.

Alright Bro I'm here to do all the testing you need however why on the GSI rom it still decrypts with decryption zip when using stock img on GSI Rom

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

 

[aIecxs]

did you see post #297 from Spaceminer, disable_dm-verity and magisk both rely on anykernel, so they currently share the same bug

 

[PoochyX]

did you see post #297 from Spaceminer, disable_dm-verity and magisk both rely on anykernel, so they currently share the same bug

So you know why this twrp is not being able to decrypt stock rom with decrypt zip why magisk is not flashing root on stock and why when backups in twrp are restored in gsi with rom decrypted they boot loop the device the only answer I can speculate is that twrp doesn't stick on the stock rom is cause it's not being decrypted

Sent from my moto g(7) play using Tapatalk

 

[aIecxs]

if twrp is not able to decrypt then the twrp build does not support decryption, your firmware or vendor is broken, or you messed up with encryption credentials. in any case it's simply impossible to decrypt then, there exist no such thing like decrypt zip

so your only choice left is to format data. if you want to stay unencrypted you need to disable forceencryption. you can patch your fstab manually as suggested, or flash the older versions of magisk and dm-verity-forceencrypt-disabler (as suggested)

i don't know if this fixes your issues with boot or rooting but i can for sure say once you used current zip release there is no way back than reversing to stock images

 

[PoochyX]

if twrp is not able to decrypt then the twrp build does not support decryption, your firmware or vendor is broken, or you messed up with encryption credentials. in any case it's simply impossible to decrypt then, there exist no such thing like decrypt zip

so your only choice left is to format data. if you want to stay unencrypted you need to disable forceencryption. you can patch your fstab manually as suggested, or flash the older versions of magisk and dm-verity-forceencrypt-disabler (as suggested)

i don't know if this fixes your issues with boot or rooting but i can for sure say once you used current zip release there is no way back than reversing to stock images

It's the twrp obviously little by little spaceminer getting it better and better he making it work without even having the phone if he had the phone we would of had a fully functional twrp already with magisk and twrp at the same time I'm really looking forward to the day that happens [emoji817]

Sent from my moto g(7) play using Tapatalk