yashsingh1/xdaforums huggingface dataset:
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
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 ?

---------- 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
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
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.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Its like once you get the phone all the mystery's will be solved
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
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.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Will Do
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Props View attachment Props.zip
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
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.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
[MENTION=7815789]PoochyX[/MENTION]

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
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Output
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
Awesome. Are you on stock or running a GSI?
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Currently stock this microphone bug on calls is killing my Android 10 GSI ambition's at the moment
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
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.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
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]
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
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.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Anything to help just looking forward to the day magisk and TWRP can co exist with a functional nanodroid
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Im stoned I think I sent you a message twice ...
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] alecxs:
lol ... :highfive: i'm smoking weed just now.. :D don't smoke and type!
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Soon the G7 play will see better days
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] 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.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] alecxs:
mouse with usb-otg or scrcpy
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
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.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
Thanks for your interest. Your assistance on a solid TWRP would be appreciated by many. Yes, the model number base is xt1952 and the code name is CHANNEL. I just downloaded the latest firmware package for my variant, the xt1952-4 (Sprint, Boost Mobile, Virgin Mobile). The most recent build is PCY29.105-134 with a June 1, 2019 security patch level. I will upload the boot image from that firmware package and post the link shortly. Again, thank you for your help.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
No problem. Thank you for helping me out! It goes both ways. I can start working on it in about an hour or two. With any luck I'll have some tests up this evening. (Eastern standard time.)
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
Sounds good friend. I'm uploading the stock boot image now, but I'm at work and service in here is crap, so it's uploading slowly but surely. I will post a link momentarily.

Update: I won't be able to complete the upload until I get off work at 5:00 p.m. EST. Very poor internet service here. The WiFi is doen and I have only 1 bar of service.

Also, on the architecture of the chipset, the Moto G7 Play is running on the Snapdragon 632, and is listed as an arm64 arch, but I'm not certain as to whether the actual firmware config is running on arm32 or arm64. I will research this a little further.

---------- Post added at 07:48 PM ---------- Previous post was at 07:04 PM ----------

It appears that the architecture is armv7l (32-bit).
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
[MENTION=7718083]Spaceminer[/MENTION], this is an unmodified stock boot image for the xt1952-4, from firmware build PCY29.105-134.

https://drive.google.com/file/d/1-hKUJ8Fy7Gr9my_iqXM2mvyJVmHIXCGD/view?usp=drivesdk
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
Thanks for that. If I'm understanding the problem correctly... TWRP does work, but it's not permanent and because of this, magisk can't be installed correctly. That's all pretty normal sounding. We have A only, but get the same behavior in that scenario. (Booting vs flashing)

It sounds like the real solution is booting twrp temporarily, and installing it to both slots so it'll be permanent and work correctly. That function is actually getting implemented in the next release. It might have already been released, I'll look. The G7 Plus folks had it unofficially. If there's more to it, like the touch screen not working or if something I said is incorrect, please let me know.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] ninjakira:
Guys this is the current maintainer of the Moto g6 play twrp and I'm the one in charge of the root guide for the g6 play so I would def help out [MENTION=7718083]Spaceminer[/MENTION] as much as possible ? fully vouch for him as he's taught me alot which is why I suggested trying to use our root guide with your twrp. If he is able to get you guys a twrp that works could someone please try out what I suggested to gain root as long as you have a stock firmware on mirrors it shouldn't be a problem to experiment as that's the only way we'll know how to help since we don't have the device. Although I am due for a upgrade from boot so maybe will have the device soon.(I hate calling it lolinet because well dark web ??)
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
Root Test

This is only for model xt1952-4 (sprint/virgin/boost) and you must be running firmware version PCY29.105-134. Keep a copy of your stock boot.img on hand in case it doesn't work. You'll have to unzip that first. I don't know who's bright idea it was to have an 8mb limit on image files, so don't ask.

Using fastboot:

fastboot flash boot boot.img

fastboot reboot

You should see it bootloop at least one time. That's normal when installing Magisk. It should not bootloop more than 3x. If it does...

Go into fastboot and enter the following commands.

fastboot erase userdata

fastboot erase DDR

fastboot reboot

If it still fails to boot after that, then reflash your stock boot.img and I'll get back to the drawing board.

If it does boot up...

Give it 1-2min to settle down, then open up Magisk from the app drawer. It should offer to install Magisk Manager, and ask to download additional files to finish setting up. Do both. It'll reboot on it's own when it's finished and you should be rooted. (You might need to manually allow access to storage in "settings > apps" for Magisk.)

* If Magisk is not in your app drawer, install the one in the attachments and open it up.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] ninjakira:
If it does boot up and if you get twrp going. After flashing twrp. Press cancel, swipe right to allow system modifications, hit wipe, hit format data next to advanced wipe button, type yes, reboot recovery, and you should hopefully be decrypted temporary, flash encryption disabler from zackptg5 here https://zackptg5.com/android.php#disverfe then flash the latest magisk beta which is here https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 (you can use stable but I personally use beta so that's why I say use magisk beta), reboot system and hopefully congrats. You have successfully decrypted and root your Moto g7 play. And remember We are not responsible for bricked devices, thermonuclear war, ligma, or anything else so please keep that in mind before wanting to blame us lol the risks are laid out. And please if able send recovery logs and logcats as well as information on what went wrong so we can try to help ? Moto g family gotta stick together so we can help each other. MAKE BACKUPS OF STOCK BOOT AND STOCK RECOVERY because it's always good to be in that habit lol
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
Nice. I will try this out first thing tomorrow morning and will report back on my experience. Thanks again [MENTION=7718083]Spaceminer[/MENTION], and [MENTION=7843264]ninjakira[/MENTION].
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Fdraco10:
Oohh!! This is good news!!

Thanks man
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] ninjakira:
Just wanna help you guys out since it was a ***** for us when the g6 play first came out ? we figured it out from trial and error so here's to hoping the same logic can be applied lol

---------- Post added at 03:06 PM ---------- Previous post was at 03:02 PM ----------

And if it does manage to work I'll make you guys a proper guide that will clearly explain it all with all the needed links. Just post recovery logs on here and logcats on here because we both are busy people irl like I'ma manager for example lol but posting them in the forum instead of pm will allow other people with the knowledge to help in case we can't get to it which is how our g6 play is where it is now. Share everything ? just don't steal cause we have absolutely no shame in calling it out lmao. Since logcats can be long try to save it in .txt format at least to make the comment section less cluttered
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] jwreidmoto:
No Boot

I tried it with no luck. Just shows bad key screen without changing would that be considered a multi bootloop?. Anyways, I reflashed my phone back to normal.

Thanks.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
I tried and no root. However, my device did boot into the OS normal. Magisk Manager was not installed upon reboot. I installed the apk manually and it indicated that Magisk was not installed. Thank you [MENTION=7843264]ninjakira[/MENTION] and [MENTION=7718083]Spaceminer[/MENTION] for helping on this. I feel as though root and TWRP are just around the corner.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] ninjakira:
Can you grab a recovery log or logcats and send them over to spaceminer?
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
I'm not sure if it counts. Your device might be using different display drivers. You should've at least seen the boot animation try to run. If you've ever gotten a black or unresponsive touch screen in twrp, that would be why. (I read someone on here had that problem.) We have Moto G6 Play variants like this. It caused me all sorts of hell getting twrp to work for those ones. That's a long story for another day though.

I have some ideas what the problem is. I'll have to do some research. I might just buy one this weekend so I can work with it directly. I'm seriously considering it. Ninja may do the same as well. I can grab the Virgin model for like $120 right now so it's very tempting. In any event, I'll try to help you folks out. We'll probably open up a new thread specifically for this root business. It seems like the appropriate thing to do rather than clutter up this one. I was hoping the boot.img would be a one shot deal and we could make a guide from there, but this will need more work unfortunately.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Viva La Android R.I.P.:
Yeah, I agree. A dedicated rooting thread may be the most appropriate venue for this. By the way, I found my Boost Moto G7 Play for an amazing deal on eBay for $89, new and sealed, with a full month of unlimited service included. https://rover.ebay.com/rover/0/0/0?mpre=https://www.ebay.com/ulk/itm/113694163907

I'm very thankful that you and Ninja have stepped up offering your skills and experience on this device.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] jwreidmoto:
So anything from here on in this thread will not work with my variant?
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
Not if I can help it! What model number do you have xt1952-(?), and what firmware build are you on? Also, are you able to elaborate on what twrp can, or can't do in it's current state? Like...

Can it boot?

Does the touch screen work?

Can you mount partitions?

Can you format data with it?

Has anyone tried flashing it? (Just an FYI: You must flash the stock rom to slot A & B first or you'll brick. Slot B can't be empty when installing twrp.)

I've done this before and I'm sure I can do it again. I just need some solid info on what, if anything, is wrong with twrp.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] jwreidmoto:
My Phone Info

I am from Canada and I use Virgin Mobile. XT1952-4_CHANNEL_RETCA_9.0_PPY29.105-134

Yes, it boots. I can format data thru fastboot commands if that's what you mean. I have flashed my original boot file to get my phone back to normal after I tried the above instructions. I am a bit of a newbie but I have rooted 2 other previous phone for which there was a recovery for. This new A/B partition stuff is new to me. I am patient and willing to learn more about fastboot to get this phone rooted though. Any help would be immensely appreciated.

Thanks:)
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
The questions I had are in regards to twrp. Can you boot twrp, can twrp format data on your phone, etc? Sorry for the confusion. I'm moving root related testing elsewhere since this is the twrp thread. I'm willing to work on twrp if you guys need it, but I also need to know what (if anything) is wrong with it.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Damn its sounding bad already
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
It's not looking good at the moment. The scrcpy method won't work with twrp booted up. The OS has to be booted, so it doesn't do me any good. I found an OTG cable and that method doesn't work either. So I'm stuck with the dtbo problem again.

I find it extremely hard to believe that not one person on xda can explain how to build that. (Especially when there's several people building them right now.) There's like one guide for xiaomi devices and it's really not even a guide. The android developer website, just tells you the tool that's used to make it. But... Not how to build the tool, how to use the tool, or where I can download it. They technically tell you how to build it, but it fails to compile due to some python error that no one has a solution to. All I need is information! It shouldn't be this hard... It really shouldn't be this hard.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Damn another set back what was the Discovery you found to making everything work?
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
I figured out how to write the fstabs correctly. But if I can't use twrp at all, I can't really do anything with that knowledge. This is a huge problem, and I really can't find a solution. I've tried to build a dtbo for over 6 months, and haven't succeeded yet. There just isn't enough information. Google did not, and probably never will, provide enough information for people to get into android development. This is a huge reason why good devs are almost non existent.

The people who know how to do it, need to start talking, because without that info I'm stuck indefinitely. There is literally not enough documentation about this. And the little that does exist, is lacking so much, that I might as well sh*t in my hand if I hope to get anything out of it. You guys have no idea how frustrated I am with this BS. I've reached out to many people who I know can do this, and none have responded.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] alecxs:
isn't this documented by motorola - you have the sources there should be instructions how to build? why can't you use TWRP it has a command line usage from adb?
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
This is alot to fathom like woah
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
I'm going to get my head right... and revisit this tomorrow. I really hate it when crap is this difficult, but if there's a way to make this work I'm going to find it.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
As corny as this sounds l believe in you ..
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
Here's Motorola's joke that they call instructions. There are no steps. It's essentially...

Install the tools

(They tell you to check all the readmes to find the tools you'll need. There's thousands of readmes in the documents folder. There's no list of tools either.)

Install the kernel sources, and apply all Linux patches...

(Which patches and where are they? Also, if you do download and extract the kernel sources, you're still missing critical parts they don't tell you about. You'll figure it out when you get errors.)

They tell you that you must have gcc 3.2+ available.

(Not a problem, but go ahead and try gcc 7, 8, 9, or even clang which Android Pie is supposed to compile with by default. You'll get error after error. Look for a solution for days. Finally fix it. Then find a new error 5sec after restarting. Repeat until you're burnt out.)

List a bunch of options and variables that don't apply to your specific device.

Include configs for 90 other devices, in your device specific kernel sources... for no reason.

(Your device's config is also in another folder, and you need to manually move it to the right one for "make" to work. It's not in arch/arm(or arm64)/configs. They don't tell you this anywhere.)

You now have a new kernel.

(No you don't.)

If you have problems email us @ ...

(You will have problems. They won't respond.)

I could write a novel on this stuff.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] alecxs:
hm.. other thread from [MENTION=3445372]scritch007[/MENTION] isn't helpful? seems he did it
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] scritch007:
Yeah building the kernel has been working since the beginning.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
I don't know how hell I missed that... Thank you! This is exactly what I needed to see. Round 2 begins now...
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
Success!

[MENTION=3445372]scritch007[/MENTION]

I really can't thank you enough for the info that you left us here. I would've been at this for ages. This was the missing piece of the puzzle that I needed.

[MENTION=7815789]PoochyX[/MENTION]

It's all over! I got the touchscreen to work. I can fix everything now. I'm going to burn the midnight oil and try to get working builds up by tomorrow.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Riiiiiii
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
Unofficial TWRP

*Fixed touchscreen drivers for xt1952-4 RETUS

For those of you who know what you're doing, you shouldn't have a problem using this. For anyone else, I will post very detailed instructions when this is more stable.

xt1952-x: twrp.img

DTBO: dtbo.img

For developers:

#!/sbin/sh

load_panel_modules()
{
path=$1
panel_supplier=""
panel_supplier=$(cat /sys/devices/virtual/graphics/fb0/panel_supplier 2> /dev/null)

case $panel_supplier in
[COLOR="green"]+ dsbj)
+ insmod $path/ilitek_mmi.ko
+ insmod $path/drv2624_mmi.ko
+	insmod $path/nova_36525_mmi.ko
+ ;;[/COLOR]
djn)
insmod $path/nova_36525_mmi.ko
;;
tianman)
insmod $path/nova_mmi.ko
;;

ilitek_mmi.ko -- touchscreen digitizer

drv2624_mmi.ko -- vibration
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Twrp in this post doesn't even format data with the yes option gives crypto header error
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] Spaceminer:
I'm aware. It's missing f2fs files. The original twrp doesn't format /data for me either for the same reason. I'm working on it.
[Moto G7 Play ROMs, Kernels, Recoveries, & Other De] PoochyX:
Also restoring a backup Still doesn't work