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

[aIecxs]

after reading your previous posts i suggest to install twrp and zips into both slots

 

[PoochyX]

after reading your previous posts i suggest to install twrp and zips into both slots

I used the copy a/b partions zip for that function and still doesn't work....

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

---------- Post added at 06:50 PM ---------- Previous post was at 06:46 PM ----------

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.

Will this be ready to test today

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

 

[Spaceminer]

I used the copy a/b partions zip for that function and still doesn't work....

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

---------- Post added at 06:50 PM ---------- Previous post was at 06:46 PM ----------

Will this be ready to test today

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

Can you send me your boot.img, vbmeta.img, and the output of ls /dev/block/bootdevice/by-name?

 

[PoochyX]

Can you send me your boot.img, vbmeta.img, and the output of ls /dev/block/bootdevice/by-name?

Boot untouched newest firmware and Vbmeta_a and Vvmeta_bView attachment Files.zip

Sent from my moto g(7) play using Tapatalk

 

[Spaceminer]

Boot untouched newest firmware and Vbmeta_a and Vvmeta_bView attachment 4942235

Sent from my moto g(7) play using Tapatalk

It looks like there's a problem with Magisk and the Universal Disabler. See if this can disable encryption for you. Format /data using the "yes" method, reboot from twrp right back into twrp, mount /vendor /data /system, and flash it. Don't flash magisk. Just boot the OS, and reboot back into twrp to check if you're encrypted.

When you check the boxes to mount /data, /system & /vendor, look at the bottom and make sure that "mount system partition read only" is not checked. That's happened to people way more than you'd think.

 

[PoochyX]

Just tested device is still encrypted checked all boxes properly and system wasn't read only

 

[Spaceminer]

Just tested device is still encrypted checked all boxes properly and system wasn't read only

Just to double check... You formatted using the "yes" option, rebooted from twrp directly back into twrp, then mounted stuff and flashed it? I have to ask because it's important for troubleshooting. I'm not trying to be redundant.

 

[PoochyX]

Just to double check... You formatted using the "yes" option, rebooted from twrp directly back into twrp, then mounted stuff and flashed it? I have to ask because it's important for troubleshooting. I'm not trying to be redundant.

Yeah I did I formated data ran the twwrp installer rebooted back into recovery checked that data system and vendor were check unclicked them and clicked them back (just to make sure) flashed zip and rebooted without magisk after rom booted rebooted to recovery twrrp not opening and data still encrypted, did you change that flag in the boot img to false and update the csv number that was mismatched in twrp

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

 

[Spaceminer]

Yeah I did I formated data ran the twwrp installer rebooted back into recovery checked that data system and vendor were check unclicked them and clicked them back (just to make sure) flashed zip and rebooted without magisk after rom booted rebooted to recovery twrrp not opening and data still encrypted, did you change that flag in the boot img to false and update the number that was mismatched in twrp

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

I haven't changed those numbers or the flags yet. I'm going to though. I'm in the process of rebuilding twrp, mostly from scratch with the newest Pie boot.img as a base. I'm going to flash your vendor and oem images to my G6 Play, then pull their libs and bin files. I think that twrp's are outdated or at least a mismatch for your device. I'm essentially trying to alter it, so that twrp brings up the partitions the exact same way as the stock recovery would. I think this will solve most, if not all the problems. Might still need a modified disabler though, or an older version of magisk. We'll get there. Absolute worst case, I can buy the phone in about a week.

It's also possible that dm-verity is blocking /data access. I did some searching and found it living inside the dtbo.img, so I'm going to disable it. Thanks for the info, it's a huge help.

 

[PoochyX]

I haven't changed those numbers or the flags yet. I'm going to though. I'm in the process of rebuilding twrp, mostly from scratch with the newest Pie boot.img as a base. I'm going to flash your vendor and oem images to my G6 Play, then pull their libs and bin files. I think that twrp's are outdated or at least a mismatch for your device. I'm essentially trying to alter it, so that twrp brings up the partitions the exact same way as the stock recovery would. I think this will solve most, if not all the problems. Might still need a modified disabler though, or an older version of magisk. We'll get there. Absolute worst case, I can buy the phone in about a week.



It's also possible that dm-verity is blocking /data access. I did some searching and found it living inside the dtbo.img, so I'm going to disable it. Thanks for the info, it's a huge help.

Bro if you buy the phone we be offical in no time like you got the G6 it isn't a bad phone Tho and it's really cheap I got mines for twenty dollars plus first month of activation and they threw in the case came out like 70 dollars

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

 

[aIecxs]

try no-verity-opt-encrypt-6.1.zip it works for samsung

 

[Spaceminer]

@PoochyX

Testing

1. Flash this modified dtbo.img from fastboot and reboot. fastboot flash dtbo patched_dtbo.img If you don't bootloop, go to the next step. If you do bootloop, then flash the one from stock and continue anyways. (If it works it'll disable dm-verity.) patched_dtbo.img

2. fastboot boot test.img If it works, then format /data using the "yes" method, then flash the installer. Reboot from twrp directly back into twrp by using the menus. (If at any point you see "swipe to allow modifications" do so.)

test.img

test-twrp-installer-channel.zip

3. Format /data using the "yes" option again. And reboot from twrp directly back into twrp using the menus once more.

4. When twrp boots up again, mount everything that you can, /data, /vendor, /system, /cache etc. and flash either my modified disabler, or the 5.21.2019 release. Don't try any other versions. Reboot and see if you're encrypted.

5. If encryption is disabled, reboot into recovery, try making a fresh backup of /data, then try restoring it.

 

[PoochyX]

@PoochyX



Testing



1. Flash this modified dtbo.img from fastboot and reboot. fastboot flash dtbo patched_dtbo.img If you don't bootloop, go to the next step. If you do bootloop, then flash the one from stock and continue anyways. (If it works it'll disable dm-verity.) patched_dtbo.img



2. fastboot boot test.img If it works, then format /data using the "yes" method, then flash the installer. Reboot from twrp directly back into twrp by using the menus. (If at any point you see "swipe to allow modifications" do so.)



test.img



test-twrp-installer-channel.zip



3. Format /data using the "yes" option again. And reboot from twrp directly back into twrp using the menus once more.



4. When twrp boots up again, mount everything that you can, /data, /vendor, /system, /cache etc. and flash either my modified disabler, or the 5.21.2019 release. Don't try any other versions. Reboot and see if you're encrypted.



5. If encryption is disabled, reboot into recovery, try making a fresh backup of /data, then try restoring it.

I'm going to test it out when I get back home and let you know how it went I remember last time you modified dtbo with a hex editor device didn't boot up hopefully it be different this time around

Sent from my moto g(7) play using Tapatalk

 

[Spaceminer]

I'm going to test it out when I get back home and let you know how it went I remember last time you modified dtbo with a hex editor device didn't boot up hopefully it be different this time around

Sent from my moto g(7) play using Tapatalk

I'm pretty sure what happened the last time that I tried, is that I changed the file size, which also restructures the internal layout of the dtbo. This time I used some trickery to avoid it. I found the lines for verity. wait,verify,slotselect Since "verify" is in the middle, and "slotselect" is in the way... I filled tselect with zero bytes to erase it without changing the file size. Leaving wait,verify,slo in every spot. As is this would break everything because that makes no sense to Android. But... Since verify,slo is only 10 characters long, and so is slotselect, I was free to rewrite this again without changing the file size. This got me the result I needed. wait,slotselect without changing the size or internal layout.

Edit: I forgot to mention. The twrp I just put up, has some extra flags added for the data partition. And another flag that I edited, because according to Android Source, it forces encryption... I also fixed up the default.prop in the ramdisk.

 

[aIecxs]

i think you need to replace spaces with 0x20 or if spaces are no option you could just add a harmless flag like nofail nouser noauto or repeat already existing flag

 

[PoochyX]

I'm pretty sure what happened the last time that I tried, is that I changed the file size, which also restructures the internal layout of the dtbo. This time I used some trickery to avoid it. I found the lines for verity. wait,verify,slotselect Since "verify" is in the middle, and "slotselect" is in the way... I filled tselect with zero bytes to erase it without changing the file size. Leaving wait,verify,slo in every spot. As is this would break everything because that makes no sense to Android. But... Since verify,slo is only 10 characters long, and so is slotselect, I was free to rewrite this again without changing the file size. This got me the result I needed. wait,slotselect without changing the size or internal layout.

Edit: I forgot to mention. The twrp I just put up, has some extra flags added for the data partition. And another flag that I edited, because according to Android Source, it forces encryption... I also fixed up the default.prop in the ramdisk.

You have any idea why the backups don't restore successfully and why it gives error about loading persist saying not enough space on the device...

Sent from my moto g(7) play using Tapatalk

 

[Spaceminer]

You have any idea why the backups don't restore successfully and why it gives error about loading persist saying not enough space on the device...

Sent from my moto g(7) play using Tapatalk

There was no flag definining persist2, and there were missing flags for the data partition in twrp.fstab which are very important. Both recovery.fstab & twrp.fstab also had an additional flag on data that I believe was forcing encryption. flags=fileencryption=ice:aes-256-cts This has been fixed. The combo of those things were probably the cause of the problem.

 

[PoochyX]

There was no flag definining persist2, and there were missing flags for the data partition in twrp.fstab which are very important. Both recovery.fstab & twrp.fstab also had an additional flag on data that I believe was forcing encryption. flags=fileencryption=ice:aes-256-cts This has been fixed. The combo of those things were probably the cause of the problem.

If this device had an official twrp there wouldn't be no need for the mod boot IMG you made cause TWRP would of handled it cause it was specifically designed for that device

Sent from my moto g(7) play using Tapatalk

 

[Spaceminer]

If this device had an official twrp there wouldn't be no need for the mod boot IMG you made cause TWRP would of handled it cause it was specifically designed for that device

Sent from my moto g(7) play using Tapatalk

That's what the installer is for. The heart of twrp lives in the ramdisk, and since your device has recovery and the boot.img combined into one file, by necessity it has to inject itself there. The modified image is just so that twrp can actually inject itself into the boot/recovery image. The process would be the same even with an official twrp. In addition to this, most official twrp builds can't decrypt an encrypted data partition, so disabling encryption would probably still be necessary anyways. Deestroy has more info about it on twrp.me.

 

[PoochyX]

That's what the installer is for. The heart of twrp lives in the ramdisk, and since your device has recovery and the boot.img combined into one file, by necessity it has to inject itself there. The modified image is just so that twrp can actually inject itself into the boot/recovery image. The process would be the same even with an official twrp. In addition to this, most official twrp builds can't decrypt an encrypted data partition, so disabling encryption would probably still be necessary anyways. Deestroy has more info about it on twrp.me.

So the backups not restoring and boot looping device is not exactly TWRP s fault

Sent from my moto g(7) play using Tapatalk