yashsingh1/xdaforums huggingface dataset:
[Moto G6 Play Guides, News, & Discussion] Ancient_Radio_Station:
Issues with XT1922-9

Hello all.

Just trying to root this XT1922-9 so I can use my titanium backups and the like. However, nothing seems to be working. I've done everything step by step and this is not my first time unlocking phones and flashing roms. I ended up going through the revert to stock instructions with the ATT stock ROM given in the op (XT1922-9_JETER_ATT_9.0_PCP29.118-63_cid1_subsidy-ATT_regulatory-DEFAULT_CFC.xml.zip).

I'm not sure which ROM I had when I got the device. I purchased it from newegg and don't remember anything from the original install except that the software channel was and still is "Wind". When I received it I went through all the updates to get to current version of pie, then started the process in the op. I've done root procedures similar to this on two nexus phones, and three one plus phones, so it's not that new to me, albeit I'm still not well versed in what's going on during the flashing. I don't think I'm making any glaring errors here. Probably just missing the right files.

Regardless, here's what I've done.

1. I get to stock via running a bash script with all the commands to do the flashing.

All the commands run successfully as far as I can tell. I do get "(bootloader) is-logical:X: not found" where 'X' is replaced by partition, bootloader, modem, fsg, dsp, boot, system, oem, vendor, and logo for their respective flash commands.

I also get "Image signed with bad key" when flashing boot.img.

These don't seem to matter since on reboot I get a fresh setup screen.

2. Wait till setup screen, click through, then reboot to bootloader

3. flash recovery for pie

4. format data and ensure it's fsf2

5. reboot to recovery

6.. push dmverity and magisk to sdcard/twrp

7. flash dmvertiy 1st, magisk 2nd

8. reboot to system

What happens:

1. screen turns on, displaying N/A

2. screen goes black after about 1-2 seconds

3. reboots to screen with N/A

This cycle repeats ad infinitum with no change. I've left it for half an hour and nothing changes.

I've tried the older version of dmverity as well as magisk 19.1, 19.3, and 20 as many others have suggested.

I've also tried flashing magisk then dmverity as I've done on my one plus phones.

Nothing gets me back to setup once those are flashed.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
hooooolllddddd on, are you saying that you have a AT&T branded Moto g6 play that is bootloader unlocked? Or do you have unlocked sim model? Because the at&t and Verizon models can't be bootloader unlocked
[Moto G6 Play Guides, News, & Discussion] Ancient_Radio_Station:
I'm guessing I don't then. It obviously works on at&t as I'm use the device right now. But I really don't know what device I've got cause it came from a third party seller.

Link to hardware info screenshots:

https://drive.google.com/folderview?id=1-5W_OjTy1fewiu9OA8MYbeusjI5CzjQO
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Did you do the bootloader unlock request? If not try doing that for me, turn developer options on and touch the button that says OEM unlocking first then Do the bootloader unlock request from moto
[Moto G6 Play Guides, News, & Discussion] Ancient_Radio_Station:
I'm way past that point my dude. That's the first thing u have to do.
[Moto G6 Play Guides, News, & Discussion] Hannibal Smith:
moto g6 play single sim xt1922-2 32gb ROM

software variant ora

software channel oraeu

android version 8.0.0

patch 1 june 2018

baseband

m8937_19.22.05.62R JETER_EMEA_CUST

kernel

2.18.71-perf-gdd9581c-00001-g0146109

build

OPP27.91-87

I think it's orange branded.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Try flashing the stock firmware from retus
[Moto G6 Play Guides, News, & Discussion] madbat99:
What commands? What script? Did you make the script?

Each script is made for specific firmware.

Have you unzipped the firmware and extracted the flashfile.xml to see the actual commands?

Sounds like you skipped a bunch of stuff and treated this phone like a Nexus.

Don't change the data format. When you format data, you choose the option at the bottom that requires you to type y e s. Not the repair data option.
[Moto G6 Play Guides, News, & Discussion] Ancient_Radio_Station:
Did that after att didn't work. Get the same behavior. Also tried flashing 8.0 versions of both. No change. I could try again but I need to be able to use the phone so I want to make sure I'm bringing something new to the table.

---------- Post added at 11:42 PM ---------- Previous post was at 11:16 PM ----------

1. The commands are the basic fastboot commands included at the bottom of the op for flashing back to stock firmware.

2/3. Instead of constantly typing each one over and over for every reflash, I just copied them into a bash script and run that. So yes I made the script.

4. Of course I unzipped the firmware, its unflashable thru twrp for some reason. There is a flashfile.xml with all of the same commands in my bash script, just a couple are out of order. Erase modems and flash logo are earlier than my script has them. Also flash vendor and oem are swapped in order relative to the op's commands. There is nothing else in the flash file aside from some stuff in the header. (How is this flashfile.xml supposed to be used correctly? If it's here why did the op tell us to run all those commands manually?)

5. If I skipped a bunch of stuff, the op skipped a bunch of stuff. I followed those directions to the t.

6. I only mentioned the fsf2 thing because another user had issues and someone suggested it as a fix. Formatting the data partition thru "format data" and typing "yes" automatically went to fsf2, so I didn't actually need to change the filesystem for data. This is correct as I'm currently using the phone right now to respond.

It's not that I'm unable to flash back to a stock rom. Thats always been successful. It's that the dmverty and magisk don't work once I do. That might be related to a poor flash procedure, but this happened on the first iteration while I was still on the os that came with the phone as well.
[Moto G6 Play Guides, News, & Discussion] Ancient_Radio_Station:
Are there any logs or files I can get you that would help?
[Moto G6 Play Guides, News, & Discussion] madbat99:
I only asked about the script because I've seen people try to use old scripts.

The order on those few probably isn't a problem.

4.

The flashfile.xml can be used with RSDlite. It reads it and executes the commands.

Or you can use an XML to .bat converter to create a .bat file from it.
[Moto G6 Play Guides, News, & Discussion] Ancient_Radio_Station:
Good to know. Appreciate the information.
[Moto G6 Play Guides, News, & Discussion] willemmerson:
'bad key' boot loop after flashing stockboot.img

I successfully rooted using these instructions a while ago. There is an OTA update so I tried to follow the magisk instructions for installing them (https://github.com/topjohnwu/Magisk/blob/master/docs/tutorials.md#ota-installation). I flashed stockrecovery.img (fastboot flash recovery stockrecovery.img) and tried to install OTA update but it failed without giving me a reason. I then realised maybe I need stock boot so I flashed that (fastboot flash boot stockboot.img) but now it is stuck in a bootloop which just says 'bad key'.

Someone in this thread had a similar problem but it wasn't obvious what they did, someone said 'Android isn't going to boot until you remove dmverity' but I don't how to do this.

Any ideas? Thanks.
[Moto G6 Play Guides, News, & Discussion] resinis:
I figured it out. motorola is still pushing OTA updates to this phone!! pretty awesome honestly, its over 2 years old now... but in my case, annoying because it reboots to TWRP and of course gets stuck there.

Theres no way to turn off periodic OTA install attempts, so i bought titanium backup app and froze the motorola update app. seems to work, no reboots for a week now.
[Moto G6 Play Guides, News, & Discussion] mactherapy:
I can confirm I got the same behaviour. I have a UK XT1922-2 32GB P4 and following the guide resulted in a boot loop.

I tried a few times starting with clean stock 8 and 9 and always the same after flashing Magisk.

I tried again using the older packages and it booted just fine.

Thanks, I was about to start trying random older versions when I found your post.
[Moto G6 Play Guides, News, & Discussion] Veggo:
Hello I have some issues with the steps in OP:

I recently updated from Oreo to Pie with the OTA updates. The last one was Oct 2019. I then unlocked bootloader and since then I get the message "bad Key" in the above left corner for 15s then the phone boots normally. (is this normal behaviour?) Next i tried to boot the pie TWRP as mentioned in OP but touchscreen isn't working. As someone mentioned in this thread that flashing stock firmware helped with this issue, I flashed the stock firmware and tried again the pie TRWP but still no touchscreen. Next I tried the 32GB Oreo TWRP and touchscreen is working. I then backed up boot and recovery (I had to correct the path to the files, the 7824900.sdhci folder wasn't there)

Next step would be to format data as mentioned in op but i get errors like "unable to mount storage" and "mkfs.f2fs -t 0 /dev/block...... process ended with ERROR: 1" and "unable to wipe data" and "unable to format to remove encryption"

As I dont want to mess anything up any further I hope someone can help me.

Model: xt1922-3

reteu

Build: PPPS29.55-35-12-5
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
You disable dm-verity by flashing the universal disabler made by zackptg5 in twrp. First install twrp, then format data using the "yes" option. Reboot into recovery from twrp's menus, then mount /vendor, /system, /data and flash the disabler. Then remount all those partitions again and flash magisk 19.3 after that.

---------- Post added at 04:46 PM ---------- Previous post was at 04:43 PM ----------

You can disable automatic updates in the developer options.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Send me your stock recovery and I'll check this out. Your model may have gotten an update that made it incompatible with twrp. I've seen the touch thing happen too many times. It's pretty easy to fix. In the mean time try this one and see if it works.
[Moto G6 Play Guides, News, & Discussion] NENAD_GT:
can someone upload their build.prop file as fast as possible? i corrupted mine (somehow) while enabling camera2api so i run into bootloop and i need the phone for tommorow lol
[Moto G6 Play Guides, News, & Discussion] dotzip.:
heres mine from XT1922-7

https://drive.google.com/file/d/1f97dNE83S1oh11JhxNx1hhDHd_3IF6__/view?usp=drivesdk
[Moto G6 Play Guides, News, & Discussion] Gleniu:
Hi, as I'm in exactly the same situation as Veggo, (the same issues, the same model number and the same firmware version), I'm attaching you a stock recovery.img from said firmware. Unfortunately, the TWRP you attached isn't working as well - the screen doesn't respond to touches.

The touches work fine on Oreo 32GB TWRP, but I can't format data in this TWRP version.

I hope you can help me :) Thank you.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
It looks like your recovery no longer uses a dt.img, which is what holds the touchscreen drivers. I think they're using dtbo, or maybe it's loading the dt.img from boot. Try this and see if it works. It might hang on the twrp splash screen for a few seconds before the menus show up.
[Moto G6 Play Guides, News, & Discussion] Gleniu:
Thank you very much! Works like a charm. Now I'm trying to root my phone, however I get into bootloop after flashing Magisk. Tried Magisk versions 20.0 and 20.1. After unlocking bootloader, there is a "bad key" info on the top of the screen upon every boot. After flashing DM-verity disabler and Magisk, the "bad key" text switches to some kind of key (the format is XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX) and I get into bootloop - I don't even see Moto logo, just the key on top for about 5 seconds and then reboot.

Any help on that? :)

EDIT: Nevermind, I solved it by using a fantastic tutorial by tamaringon in post 391 :)
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Magisk 19.4+ will cause a bootloop for us because it signs the boot.img with legitimate keys, which our bootloader refuses. Reflash your stock boot.img, wipe /data, /cache, /davlik. Flash disabler first, then flash magisk 19.3.

---------- Post added at 02:14 PM ---------- Previous post was at 02:09 PM ----------

@Veggo

See post #423 for the fixed twrp.

---------- Post added at 02:15 PM ---------- Previous post was at 02:14 PM ----------

@Veggo

See post #423 for the fixed twrp.
[Moto G6 Play Guides, News, & Discussion] carzevedo:
Thank you so much! This sequence and apps works perfectly :D:good::good::good::good::good:
[Moto G6 Play Guides, News, & Discussion] Gleniu:
Thank you for the explanation. I successfully rooted with Magisk 19.1 using tutorial in post 391. However, I went for it and tried to update Magisk to latest version (20.1) using Magisk Manager with Direct Flash method. "Bad key" message turned to "XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX-XXXXXXXX", but this time system booted just fine :) So, it seems that we can use the latest Magisk, but the first flash in TWRP must be done using Magisk version <19.4, and then updated using Magisk Manager.
[Moto G6 Play Guides, News, & Discussion] Veggo:
Thank you very much. Like Gleniu mentioned TWRP is working fine but I also stuck in bootloop after flashing DM-verity disabler and Magisk

First I tried with Magisk 19.3 but stuck in bootloop so I reflashed stock boot.img, wipe /data, /cache, /davlik. Then repeated the steps from the beginning but with Magisk 19.1. But also stuck in bootloop.

I couldn't find Disable_Dm-Verity_ForceEncrypt_05.21.2019 so I used the latest as in OP (10.20.2019.).

[MENTION=1153765]Gleniu[/MENTION]: which version of Dm-Verity did you use?
[Moto G6 Play Guides, News, & Discussion] Gleniu:
I used the attached one. I also couldn't find it on the project website, so I just googled it :) Worked perfectly, so I think it is safe to assume that the disabler is the issue, not the Magisk itself. Hope you'll root your phone as well :)
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
I can give you the one I use. I believe it's the 5/21/19 release.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Hello everyone, thank you to the people that's been helping on the guide lately, I'm sorry I haven't been posting alot some recent family tragedy has come about so I've had to refocus my attention the last week, our twrp maintainer [MENTION=7718083]Spaceminer[/MENTION] is working on updating on TWRP which will fix the issues everyone is having lately, once he is done with TWRP it will uploaded and added to the guide, thank you for your patience and as a reminder, please drive safe
[Moto G6 Play Guides, News, & Discussion] harryspar:
Just for the record

I have an unlocked RETUS 1922-9 on the Pie update.

Everything failed for me except using the 5/21 version of the verity script, and Magisk 19.2, which then worked.
[Moto G6 Play Guides, News, & Discussion] painball:
Honestly you are more stubborn than I am. Can you post this Verity script? Nothing makes my 1922-3 working. When I try to verity and magisk immidiately goes into bootloop with numbers on the top.

[MENTION=309187]edit[/MENTION]: Seems to be working indeed. No numbers on top. Now stuck ant Motorola logo. Well. I will let it think this out for 10 minutes. I flashed plenty of devices. Never had such fight and so many variables between models. Budget phone in 9 versions - what a drama.
[Moto G6 Play Guides, News, & Discussion] brunohrbarros:
Hello Spaceminer! Thank you very much for helping us!

I can confirme the same problem with that "string of numbers"

Coming from android 9 ppps29.55-35-12-5 xt1922-5 retbr

Should I try Magisk 19.3?

I'm new to this, I appreciate if you can explain some things to me, if it won't bother you.

I`ve read all pages, each comment, to understand better what I`m trying to do, but it`s not familiar to me.

What do Disable and Magisk do? (I understood Disable solves the problem with data encrypt and Magisk do the root process)

And when I flash a GSI, do I have root, or I will need to do these steps too?

Another very stupid quest, when I use this command "adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img", what is the .img file location?

Thank you for your patience!

---------- Post added at 10:18 PM ---------- Previous post was at 09:55 PM ----------

ninjakira you are great! Thanks for all this work! My prayers to you and to your family!
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
-The disabler prevents encryption, and also removes dm-verity which is a security feature that can prevent you from booting GSIs, or sometimes even the stock OS if it's been modified.

-Yes, Magisk handles all the root stuff.

If you flash a GSI you may or may not have root, it depends. Some GSIs have it included as part of the system and some don't.

If you keep the rooted boot.img from stock and flash a GSI, Magisk will usually show up in your app drawer shortly after booting up. If you open it, it'll prompt you to download some files and finish re-rooting the new system.

If it doesn't show up, you'll have to reflash Magisk in twrp. (use v19.3 by the way)

If you successfully disabled encryption before flashing a GSI, it'll stay disabled on the GSI as well, so no need to reflash the disabler.

-The image file location should be in the same folder you're running adb from.
[Moto G6 Play Guides, News, & Discussion] painball:
And that's in teory. In practice the devices got different bootloaders. Even if I try to "root" stock 9.0 the device won't boot. With xt1922-3(lucky me) none of mentioned in topic methods pass the bootloop on stock 9.0 or GSI ROMS. Maybe with 8.0? Don't have time for now. Wasted like 3hours yday. For reflashing/booting/searching for archive versions of magisk, disablers etc.
[Moto G6 Play Guides, News, & Discussion] brunohrbarros:
Just one more question, in case I mess everything, I downloaded the stock rom from lolinet servers (XT1922-5_ALJETER_RETBR_9.0_PPPS29.55-35-12-5_cid50_subsidy-DEFAULT_regulatory-XT1922-5-BRAZIL-MANAUS_CFC.xml).

It shows on info file Modem Version: M8937_31.39.05.93R, but my actual modem version is m8937_31.39.05.93Z. Should I concern about flashing this stock rom from lolinet?

I got a bit confused with these termnologies that Motorola adopted with Moto G6 Play.

When I`m on fastboot mode, it shows on screen:

BL: MBM-2.1-aljeter_retail-b1f322d-190926

Product/Variant: jeter XT1922-5 32 GB p4

There is no jeter rom for XT1922-5 on lolinet
[Moto G6 Play Guides, News, & Discussion] Hannibal Smith:
anyone have this stock rom ? I'd like to have it in case i messe up something..
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
If you're in Brazil then that should be the correct firmware. I wouldn't worry about the modem, that just looks like a small update. If you're not in Brazil, you'll probably want this firmware. It's retail aljeter: Link

---------- Post added at 06:31 PM ---------- Previous post was at 06:07 PM ----------

Orange? You'll want this one. ORAEU Pie
[Moto G6 Play Guides, News, & Discussion] amedeh123:
whats the difference between retail and retbr firmwares?

is it safe to go back and forth between them?
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Not much of anything. One is RETAIL the other is just specific to Brazil. If you use the wrong one then OTAs won't work. That's about it. I'm on the xt1922-7 with Virgin Mobile and I can flash RETUS or RETAIL, and they work fine even though it should be Sprint.
[Moto G6 Play Guides, News, & Discussion] MEDDLER2020:
Thanks a lot, I had the same problems. followed the tutorial several times precisely. After I read your post, I tried again with the older versions of the files. and now.... it finally worked :) thank you very much. I also have the XT1922-2 model.

---------- Post added at 09:17 AM ---------- Previous post was at 09:00 AM ----------

It worked on "jeter XT1922-2 32GB P4" with older versions of the files --> I used

Magisk-v19.1

and

Disable_Dm-Verity_ForceEncrypt_05.21.2019

and it booted. I could not install TWRP. Maybe someone can help to solve this last prob..... thanks "mactherapy" for his post!!!
[Moto G6 Play Guides, News, & Discussion] dotKin:
I would recommend to boot twrp.img from fastboot and then flash the img from TWRP as a Recomery image
[Moto G6 Play Guides, News, & Discussion] amedeh123:
Just confirming for reference: Sucessfully rooted my XT1022-5 on RETBR's october update by flashing Magisk 19.3 and 05/21 verity script.

Updating Magisk to 20.1 from the manager app after the fact seem to have worked too, so no worries there about using outdated software.
[Moto G6 Play Guides, News, & Discussion] Veggo:
Big thank you

Hi, I wanted to say thank you for helping me here. With these exact releases it worked prefectly fine.

Sorry for replying so late.

Kind regards
[Moto G6 Play Guides, News, & Discussion] lordsibemol1ro:
I want to share with you my results:

I spent a whole day trying to get root on my G6 Play XT1022-4 with Android 9, I followed the steps in this post and as a result I got a black screen, with a code in white letters, in an eternal bootloop. Then I began to read carefully the comments where my model and its version of android were talked about. And what helped me was to follow these steps:

1.- Make sure your model is TX1022-4 and has Android 9.

2.- enter Bootloader mode.

3.- Execute the fastboot boot twrp.img command, to start from the TWRP without installing it.

4.- A screen will appear asking for password or pattern, ignore it, as she (or he (or both)) ignored you, give it to cancel.

5.- If you enter Install and put "Select Storage", you will see that the internal memory says 0MB. You come back and do Wipe.

6.- Restart from the TWRP in Reboot> Bootloader.

7.- You rewrite fastboot boot twrp.img.

8.- Now the screen will not appear asking for a password or pattern. Delizas calmly and flash from the SD:

- Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip

- Magisk-v19.1 (19100) .zip

In that order.

9.- Reboot System

10.- Ready!

That is the way I could get root on my G6 Play XT1022-4 with Android 9 Pie. ;):cowboy::good::cyclops:

I hope it serves someone. :laugh::cool:
[Moto G6 Play Guides, News, & Discussion] Vazzim:
?

Hello, I'm having trouble with the twrp it doesn't seem to register my touch.

When I reboot the phone to exit twrp the phone boots up normaly and the touch works properly, I'm certain that I downloaded the right file, I have the xt1922-3 variant and I've downloaded the Pie link for twrp.
[Moto G6 Play Guides, News, & Discussion] LordUnderling:
Count me among those who had a bootloop problem, endlessly repeating display of the alpha-numeric string "80012A99-867FDA48-4E357816-0E549F1B-B067FBD5", because of installing Disable_Dm-Verity_ForceEncrypt_10.20.2019.zip and Magisk-v20.1.zip within an otherwise successful TWRP recovery installation on a Retail US XT1922-9 Jeter G6 Play phone with October 1, 2019 build # PPP29.118-68.

Restoring stock firmware and then installing TWRP with Disable_Dm-Verity_ForceEncrypt_05.21.2019.zip and Magisk-v19.3.zip is also what worked for me.

It was only because I was still able to get back into recovery that I could fix this. I ended up wasting some of my own time by starting over with the TWRP installation without first reinstalling the stock firmware. I feared that reinstalling stock would turn out to be more painful than it actually was. Simple copy and pasting into a terminal window within my Linux setup is what worked for me.

Thanks to everybody who put the work into creating all this.

Now it's on to trying out the GSI ROMs.