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

[Spaceminer]

Yeah I removed hab.sh on a fresh install while trying to assemble twrp and it still didnt stick with stock and if u meant did I send u hab.sh it's posted in post #356 was looking at the update binary is this the key to getting twrp to function and also we might as well transcend to orange fox and just skip twrp ?

Sent from my moto g(7) play using Tapatalk

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

So basically orange fox is a very plausible scenario for the G6 play and when the twrp is sorted out for the G7 play that same plausibility will be there for G7 play also

Sent from my moto g(7) play using Tapatalk

I'll find the post. I didn't realize that you had already dropped it in the threads, but yeah, that's what I was after. I want to get twrp working first, mostly because it's much simpler inside and the themes/UI are already sized properly, so it's one less thing to do. Once twrp is out of the way, porting Orange would be like a 1 day job.

 

[PoochyX]

I'll find the post. I didn't realize that you had already dropped it in the threads, but yeah, that's what I was after. I want to get twrp working first, mostly because it's much simpler inside and the themes/UI are already sized properly, so it's one less thing to do. Once twrp is out of the way, porting Orange would be like a 1 day job.

Its like once you get the phone all the mystery's will be solved

Sent from my moto g(7) play using Tapatalk

 

[Spaceminer]

Its like once you get the phone all the mystery's will be solved

Sent from my moto g(7) play using Tapatalk

From /vendor/bin/init.mmi.hab.sh

# High assurance boot image verification service
# Checks system image, oem image, or both depending on "which_image"
...
...
verified_boot_state=`/vendor/bin/getprop ro.boot.verifiedbootstate`

Yeah... that's about to be a Zero assurance boot image verification service. This script is my new best friend!

Do me a huge favor if you don't mind... Pull /vendor/build.prop, /oem/oem.prop, and /system/build.prop and send them to me.

 

[PoochyX]

From /vendor/bin/init.mmi.hab.sh

# High assurance boot image verification service

# Checks system image, oem image, or both depending on "which_image"

...

...

verified_boot_state=`/vendor/bin/getprop ro.boot.verifiedbootstate`

Yeah... that's about to be a Zero assurance boot image verification service. This script is my new best friend!



Do me a huge favor if you don't mind... Pull /vendor/build.prop, /oem/oem.prop, and /system/build.prop and send them to me.

Will Do

Sent from my moto g(7) play using Tapatalk

 

[PoochyX]

Props View attachment Props.zip

Sent from my moto g(7) play using Tapatalk

 

[Viva La Android]

You're either blocked from sending messages, or you need to change your account settings. I tried sending you a pm but it just gives me this instead.

Yeah it's most likely a restriction I've mistakenly clicked on in account settings. Wish that stuff could be managed in-app on XDA Labs. I'll sign in on my browser and work it out. Thanks for the heads up.

 

[Spaceminer]

@PoochyX

Can you give me the output of these commands? I'm editing init.mmi.hab.sh to disable verification checks.

getprop ro.boot.verifiedbootstate

getprop ro.boot.secure_hardware

 

[PoochyX]

@PoochyX



Can you give me the output of these commands? I'm editing init.mmi.hab.sh to disable verification checks.

getprop ro.boot.verifiedbootstate

getprop ro.boot.secure_hardware

Output

Sent from my moto g(7) play using Tapatalk

 

[Spaceminer]

OutputView attachment 4954165

Sent from my moto g(7) play using Tapatalk

Awesome. Are you on stock or running a GSI?

 

[PoochyX]

Awesome. Are you on stock or running a GSI?

Currently stock this microphone bug on calls is killing my Android 10 GSI ambition's at the moment

Sent from my moto g(7) play using Tapatalk

 

[Spaceminer]

Currently stock this microphone bug on calls is killing my Android 10 GSI ambition's at the moment

Sent from my moto g(7) play using Tapatalk

If you want to try this, I think it'll allow Magisk to work on GSIs. It should pass the verification checks if I did everything right. Copy to /vendor/bin and run chmod 0755 on it. Be sure to remove .txt, I did that so xda would let me directly post it. If you dont feel like testing it, no worries. I will have a G7 Play in my hands by Friday evening.

 

[PoochyX]

If you want to try this, I think it'll allow Magisk to work on GSIs. It should pass the verification checks if I did everything right. Copy to /vendor/bin and run chmod 0755 on it. Be sure to remove .txt, I did that so xda would let me directly post it. If you dont feel like testing it, no worries. I will have a G7 Play in my hands by Friday evening.

Just tried it on a fresh firmware GSI installation replaced bin file with modified one gave proper permissions intilized first Boot on lineage 17.1 GSI with decrypt zip and magisk zip and magisk didn't work...also tried it on Android 9 dot another fresh firmware GSI installation bartered me the same results at least u getting the phone Friday so you can get hands on and deliver us to the promise Land [emoji16][emoji1787][emoji23][emoji1787][emoji4]

Sent from my moto g(7) play using Tapatalk

 

[Spaceminer]

Just tried it on a fresh firmware GSI installation replaced bin file with modified one gave proper permissions intilized first Boot on lineage 17.1 GSI with decrypt zip and magisk zip and magisk didn't work...also tried it on Android 9 dot another fresh firmware GSI installation bartered me the same results at least u getting the phone Friday so you can get hands on and deliver us to the promise Land [emoji16][emoji1787][emoji23][emoji1787][emoji4]

Sent from my moto g(7) play using Tapatalk

That's actually not a bad thing. It means that I know exactly what needs to be changed. I appreciate you trying it out. It'll only save me time in the long run.

There's a section near the top of the script that checks the boot state, but I thought it was only to let the bootloader know if you're updating via OTA, so I didn't want to mess with it. But it looks like any update that changes the boot.img triggers this process. (magisk patching the boot.img, installing twrp...) So I need to make this section not care, not check, or pass the check anyways. I think I could just give it arbitrary definitions, or possibly remove it entirely. I'll figure it out soon.

 

[PoochyX]

That's actually not a bad thing. It means that I know exactly what needs to be changed. I appreciate you trying it out. It'll only save me time in the long run.



There's a section near the top of the script that checks the boot state, but I thought it was only to let the bootloader know if you're updating via OTA, so I didn't want to mess with it. But it looks like any update that changes the boot.img triggers this process. (magisk patching the boot.img, installing twrp...) So I need to make this section not care, not check, or pass the check anyways. I think I could just give it arbitrary definitions, or possibly remove it entirely. I'll figure it out soon.

Anything to help just looking forward to the day magisk and TWRP can co exist with a functional nanodroid

Sent from my moto g(7) play using Tapatalk

 

[PoochyX]

Anything to help just looking forward to the day magisk and TWRP can co exist with a functional nanodroid

Sent from my moto g(7) play using Tapatalk

Im stoned I think I sent you a message twice ...

Sent from my moto g(7) play using Tapatalk

 

[aIecxs]

Im stoned I think I sent you a message twice ...

lol ... :highfive: i'm smoking weed just now.. don't smoke and type!

 

[PoochyX]

Soon the G7 play will see better days

Sent from my moto g(7) play using Tapatalk

 

[Spaceminer]

For anyone curious, I do have a G7 Play. I just got it yesterday and I am working on TWRP. I can get it to boot up, but that's it. The touchscreen is not working for my model (xt1952-4 RETUS), and the usual things that I would do to fix it are also not working. I suspect the issue is using a mismatched dtbo.img. The one that works with twrp, also prevents the touchscreen from working. I've tried hard to build a dtbo or patch one, and all my efforts have failed. If you know anyone who can help me with this, please contact me or put them in touch with me. I really need some help with this. In the meantime I'm going to keep trying, but I can't fix anything if I can't get the touch screen working.

 

[aIecxs]

mouse with usb-otg or scrcpy

 

[Spaceminer]

mouse with usb-otg or scrcpy

I just found the USB trick, but I don't have an OTG adapter. How do I use the scrcpy method?

Edit: I found it already. I'll update this if I have any more problems.