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

[EngineFixer44]

Yeah, getting TWRP to stick was pretty easy, thanks to clear instructions and a stable twrp4.img from @Spaceminer

1. fastboot flash dtbo dtbo.img from https://drive.google.com/file/d/1pV6-LbNoMG0J8vcyAWN0QWYGx67vxBgT/view?usp=sharing
2. fastboot boot twrp4.img from https://drive.google.com/file/d/13MROGlEA_TdgHFTaiqOswo4w0NgXhGbx/view?usp=sharing
3. adb push disable_dm-verity_forceencrypt.zip from https://forum.xda-developers.com/attachment.php?attachmentid=4838211&d=1570520141
4. Wipe, Format
5. Flash disable_dm-verity_forceencrypt.zip
6. Advanced, Install Recovery to Ramdisk
7. Reboot to recovery
8. Reboot to bootloader
9. Repeat steps 2-7 for slot b (or a if you did b first), fastboot --set-active=b

Before flashing any custom ROM, be sure you are using the arm32_binder64 arch GSI (no custom ROMs available yet specifically for this model that I can find) and wipe the system partition before flashing system image. Otherwise system loading will bootloop.

After doing this the touchscreen is not responsive in twrp.

 

[kpc]

After doing this the touchscreen is not responsive in twrp.

That might be a model/firmware thing (mine is RETUS, and it works), or you might need to start from the latest stock.

I can only speak to my own experience/device, and these steps give me a bootable TWRP in both slots, with functional touchscreen.

 

[BobbyBlunt]

So dumb question.... How are we rooting and keeping twrp? Do we patch twrp with magisk since we are using magisk as part of the recovery?

Wouldn't flashing a patched boot IMG back just overwrite the recovery?

Again this a/b stuff is still very new to me

 

[ninjakira]

Holy hell this is great to see ?

 

[Viva La Android]

Holy hell this is great to see ?

I know right?

---------- Post added at 01:39 AM ---------- Previous post was at 01:35 AM ----------
@EngineFixer44, working smooth on my xt1952-4 Sprint variant. Hats off to @Spaceminer for his dedicated work on the stable twrp4.img.

 

[SmallGiant]

Yeah, getting TWRP to stick was pretty easy, thanks to clear instructions and a stable twrp4.img from @Spaceminer

1. fastboot flash dtbo dtbo.img from https://drive.google.com/file/d/1pV6-LbNoMG0J8vcyAWN0QWYGx67vxBgT/view?usp=sharing
2. fastboot boot twrp4.img from https://drive.google.com/file/d/13MROGlEA_TdgHFTaiqOswo4w0NgXhGbx/view?usp=sharing
3. adb push disable_dm-verity_forceencrypt.zip from https://forum.xda-developers.com/attachment.php?attachmentid=4838211&d=1570520141
4. Wipe, Format
5. Flash disable_dm-verity_forceencrypt.zip
6. Advanced, Install Recovery to Ramdisk
7. Reboot to recovery
8. Reboot to bootloader
9. Repeat steps 2-7 for slot b (or a if you did b first), fastboot --set-active=b

Before flashing any custom ROM, be sure you are using the arm32_binder64 arch GSI (no custom ROMs available yet specifically for this model that I can find) and wipe the system partition before flashing system image. Otherwise system loading will bootloop.

Thank you for the instructions. Would anybody be able to help me with an error, however? I tried the first command "fastboot flash dtbo dtbo.img", and get the following error.
"fastboot: core/libsparse/sparse.cpp:131: int write_all_blocks(struct sparse_file *, struct output_file *): Assertion `pad >= 0' failed.
Aborted (core dumped)" Using an older version of android-tools fixed this, in case anyone else has this problem.

However, I'm having the same issue as @EngineFixer44 mentioned earlier. It seems the touch-screen isn't working for me either. I'm on XT1952-2.

 

[jwreidmoto]

Instructions for Slot B

Can you show me what to add to the commands in order to do the above instructions to the b slot? Also are you able to root once the above commands are done to both slots?

 

[jwreidmoto]

Instructions for Slot B

Yeah, getting TWRP to stick was pretty easy, thanks to clear instructions and a stable twrp4.img from @Spaceminer

1. fastboot flash dtbo dtbo.img from https://drive.google.com/file/d/1pV6-LbNoMG0J8vcyAWN0QWYGx67vxBgT/view?usp=sharing
2. fastboot boot twrp4.img from https://drive.google.com/file/d/13MROGlEA_TdgHFTaiqOswo4w0NgXhGbx/view?usp=sharing
3. adb push disable_dm-verity_forceencrypt.zip from https://forum.xda-developers.com/attachment.php?attachmentid=4838211&d=1570520141
4. Wipe, Format
5. Flash disable_dm-verity_forceencrypt.zip
6. Advanced, Install Recovery to Ramdisk
7. Reboot to recovery
8. Reboot to bootloader
9. Repeat steps 2-7 for slot b (or a if you did b first), fastboot --set-active=b

Before flashing any custom ROM, be sure you are using the arm32_binder64 arch GSI (no custom ROMs available yet specifically for this model that I can find) and wipe the system partition before flashing system image. Otherwise system loading will bootloop.

Could you post instructions on how to do the above instructions to the b slot?
Thanks

 

[moochermick]

fastboot flash system_b "file to flash"
I believe it's as above without the quotes

 

[jwreidmoto]

Thanks

 

[BobbyBlunt]

New ota seems to be rolling out on the Sprint variation. Looks like it contains October's security fixes

 

[Luqueuris150]

So dumb question.... How are we rooting and keeping twrp? Do we patch twrp with magisk since we are using magisk as part of the recovery?

Wouldn't flashing a patched boot IMG back just overwrite the recovery?

Again this a/b stuff is still very new to me

I want to know that too, does anybody knows how to install magisk and twrp here? What to patch first, what to patch, and everything else?

 

[aIecxs]

in Magisk Manager is option somewhere to patch recovery instead of boot. Patch the twrp.img
https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

 

[Wiliz Yei Yei]

I know right?

---------- Post added at 01:39 AM ---------- Previous post was at 01:35 AM ----------
@EngineFixer44, working smooth on my xt1952-4 Sprint variant. Hats off to @Spaceminer for his dedicated work on the stable twrp4.img.

Yes, it worked 10/10, install android 10 GSI and without success: '(

 

[Spaceminer]

Yes, it worked 10/10, install android 10 GSI and without success: '(

I think that's a vndk issue. Android 10 only boots with Oreo firmware for us G6 Play users, and I think you folks shipped with Pie, so you don't even have Oreo firmware. I've always had to flash Oreo vendor, oem, and boot images, then flash phh's special magisk build under the v200 tab.

 

[Wiliz Yei Yei]

I think that's a vndk issue. Android 10 only boots with Oreo firmware for us G6 Play users, and I think you folks shipped with Pie, so you don't even have Oreo firmware. I've always had to flash Oreo vendor, oem, and boot images, then flash phh's special magisk build under the v200 tab.

We will stay a little longer without Q. Is there any method to root by having the TWRP?

 

[Spaceminer]

We will stay a little longer without Q. Is there any method to root by having the TWRP?

Post #233 just a few replies above this. I believe that's how you do it. Magisk should be more compatible then ever at this point. I think they've moved to Android 10 support.

 

[Viva La Android]

Post #233 just a few replies above this. I believe that's how you do it. Magisk should be more compatible then ever at this point. I think they've moved to Android 10 support.

Yeah, the Magisk v20.0 change log includes myriad inclusions surrounding Android 10 support. I haven't taken the time to read the entire change log, but it's packed with changes following the previous Magisk release, including the notorious system-as-root implementation (something I'm still studying to grasp).

 

[SmallGiant]

Does anyone know if TWRP will be getting an official port on this device? I tried earlier and wasn't able to use the dirty port, as the touch-screen wouldn't work for me (even after flashing the dtbo first). Also, is there a way to backup the system and install a new ROM without TWRP, am I stuck for now until I can get it to work? Thanks.

 

[daftshanks]

I want to know that too, does anybody knows how to install magisk and twrp here? What to patch first, what to patch, and everything else?

Yeah this is where I'm wondering too. Do I flash twrp from stock and then magisk recovery by patching the twrp? Just need to know if possible to have both Magisk and TWRP on this phone due to the recovery method for our phones