yashsingh1/xdaforums huggingface dataset:
[Moto G6 Play Guides, News, & Discussion] madbat99:
I had a feeling he was using the wrong version of magisk
[Moto G6 Play Guides, News, & Discussion] krltz2:
Thank for all i am very happy YA LO LOGRE

---------- Post added at 04:50 AM ---------- Previous post was at 04:49 AM ----------

Thank for all YA LO LOGRE
[Moto G6 Play Guides, News, & Discussion] Swift2603:
I was using ADB for sideloading ;)

EDIT: Flashed the stock ROM right now. Forced encryption takes ages... Let's see whether the update works. Then a factory reset, switching off encryption and installing Magisk again... fingers crossed.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Are you saying your good? Did you manage to finally get everything working?
[Moto G6 Play Guides, News, & Discussion] ninjakira:
I mean to simplify that that flash stock rom then twrp push magisk to tmp and install it through twrp. It will stay force encrypted during the boot. After boot up go into magisk and uncheck perserve force encryption then hit install and do that one that magisk recommends. And Bam. Force encryption is no longer an issue
[Moto G6 Play Guides, News, & Discussion] krltz2:
Yes its correctly thats very good all good
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Holy Christ finally ?????
[Moto G6 Play Guides, News, & Discussion] Maximus Supremum:
confirm working in XT1922-3 Model

rooted OK

thx
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Heck yeah. I seen your post in the old guide so I'm glad my guide was able to help you out good sir ?
[Moto G6 Play Guides, News, & Discussion] madbat99:
[MENTION=7843264]ninjakira[/MENTION] your root guide worked great for me. I didn't decrypt my phone though. I flash things from the SD card. I also didn't really see the need to flash TWR p i just booted it and installed magisk 17.3. modules work fine too so this device must not have the f2fs loopback bug.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Hell yeah I'm glad it worked and I suppose you don't have to decrypt it if you don't want to As long as magisk still works that's all that really matters lol I personally don't see a need for encryption in my life because well i was a bad seed growing up so the government and other people like Google have had my info since I was a teen so it doesn't really bug me I suppose ?
[Moto G6 Play Guides, News, & Discussion] madbat99:
By the way I have the Virgin Mobile Moto G6 play if you want to add that to your tested and working list. It's the same as the Boost one so not important just thought I'd let you know if it was useful to you.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
I've added it. Any info on any of the g6 play variants help. So thank you for telling me what carrier variant it was lol
[Moto G6 Play Guides, News, & Discussion] LordUnderling:
Not wanting to brick a Moto G6 Play that I just bought as an open-box special, I've been reading and rereading both this guide and the one started by kwiksi1ver to try to understand why the instructions within the two diverge.

Would I be correct in presuming that your guide depends on on installing and using Magisk-v17.3.zip while the other guide depends on Magisk-v16.4.zip? Might that be enough to explain the differences or is there something else going on?

kwiksi1ver's guide also requires downloading and installing an XXXXXX-X_no_dm-verity_boot.img boot image file. Your's does not. Was this an oversight on your part is this step now unnecessary?

Your Step 8 ("adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor") is identical to kwiksi1ver's Step 10 but your guide omits downloading and installing the file fstab.qcom at location "/vendor/etc/" as kwiksi1ver does for his Steps 11 and 12. Is this another oversight or have these steps also become unnecessary?

BTW, if you go to the github web page for Magisk (github.com/topjohnwu/Magisk/releases/), it does appear that Magisk-v17.3.zip is out of beta or, rather, that it is not currently beta. I've been feeling uneasy about using it but this is making me feel better about doing so.
[Moto G6 Play Guides, News, & Discussion] madbat99:
The new magisk version eliminated the need for fstab. Just need TWRP and magisk. That's it. I used 17.1 but 17.3 works fine as well. This is a more updated guide that's why it has an older magisk version. No dmverity boot.img needed either. Again, just TWRP and magisk.
[Moto G6 Play Guides, News, & Discussion] LordUnderling:
Excellent. You really should have stated this in your leading paragraph. Instead of saying that the other guide was "sloppy", you could have said that it was dated because of its reliance on an older version of Magisk and that v17 simplifies the rooting process.

I nitpick but trying to understand why the two guides disputed each other ate up quite a bit of my time.

Anyway, do I now need not worry about not downloading any Android updates before rooting? Or is it a matter of backing up the stock boot and stock recovery to match the stock firmware should I need to reinstall that?

In other words, might the thing to do now is, first, back up the stock boot and recovery as soon as possible (as, say in my case, "stock_8.0.0_OPPS27.91-35-3_cid50_boot.img" instead of "stockboot.img" and "stock_8.0.0_OPPS27.91-35-3_cid50_recovery.img"), THEN allow all Android updates to be installed and THEN install the new Jeter TWRP recovery and Magisk v17-x?

I mention "8.0.0_OPPS27.91-35-3_cid50" because I see that the current Build Number on my G6 Play is OPPS27.91-35-3 (Settings->System->About phone) and that appears to match one of the firmware files at mirrors.lolinet.com/firmware/moto/jeter/official/RETUS/. It so happens that I NOW see that there is an even newer one that matches the Build Number of the update that I'm now being asked to install on my G6 Play (OPP27.91-140). (This is new because I didn't see this file yesterday.)
[Moto G6 Play Guides, News, & Discussion] Starkiller2:
The updated boost firmware is available now on mirrors.lolinet. I missed it somehow.

https://mirrors.lolinet.com/firmwar...ubsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
[Moto G6 Play Guides, News, & Discussion] ninjakira:
I I noticed it also added the different variants of the xt1922-9 model. This is great because a few people need that so off to my Facebook messenger and pm I go lol o I help people both on messenger and through pm.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
I made this guide because the other guide is not properly maintained. Magisk 16.4 doesn't do dm-verity patch and we needed a patched boot.img. and patched fstab. magisk 16.7 and up does the patches for us now including the fstab file

As long as your using 16.7 and up you should be fine but why use older things when something new is out? Once i get the notification for a new magisk version is when I update it and I'm using the beta channel on magisk manager and it hasn't told me there's an update yet. I just chose beta because at the time it's what I was using when I made the guide. I do update my guide pretty often to include new info or exclude old info. I updated it to say magisk 17.3 when it came out but again it was still beta so I'll just add /stable. That's why the other guide has older stuff and that's why I made this guide. if you use his patched boot Img now you will be ina bootloop and his guide was starting to cause alot of issues with users that my guide has been able to fix. And I didn't realize the adb shell code was still there I thought I took it out. That was used for the patched fstab file it's no longer needed as magisk does it for us. I wouldn't say my guide relies on the latest magisk but it makes things alot easier if your using the latest one. But magisk 16.7 and up is what you need to use. Will be taking that out after I post this.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
What variant of the g6 play. is it xt1922-9 if so it looks like the newest firmware for it was upload sometime today. Your best bet is stay stock and take the ota then do root
[Moto G6 Play Guides, News, & Discussion] madbat99:
You quoted me, I didn't make the thread. But op said they made because the other was not maintained. Update all the way, then do backups and root.
[Moto G6 Play Guides, News, & Discussion] LordUnderling:
Sorry about that. I intended that for the OP. My apologies.
[Moto G6 Play Guides, News, & Discussion] Omar04:
Yes finally that was the build I was looking for before rooting. I knew the other two wasn't for my device, mine is OPP27.91-140
[Moto G6 Play Guides, News, & Discussion] gsmccormick:
Hello All!

I have no trouble with following this guide at all until i get to the point where it says that you should flash the DM Verity that coincidences with your model. OK, on my fastboot screen it says my model is a 1922-7. I downloaded it and tried to flash it, but i get the error that says

"ERROR: flash write fail! unsigned image" How do i get this to flash correctly?

My other problem with this guide is that after i do the fastboot boot moto-g6-play-jeter-patched-twrp.img file, it loads fine and brings up TWRP, but my problem is when i try to adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot stockboot.img

adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery stockrecovery.img, my computer says that im no longer connected to ADB and says "no emulators found". I have tried to go into the ADB sideload feature on TWRP, but it doesnt work either. Help please! I really love this phone and want to root it. Oh BTW, i have unlocked my bootloader, thats another question i have, when ever i have to reboot my phone, i get a blank dark screen with white letters that say "Bad Key" and it takes 2 times to actually boot back into android.

Thank you so much!
[Moto G6 Play Guides, News, & Discussion] madbat99:
All you have to do is boot TWRP and Flash magisk. Installing magisk will automatically backup your stock boot image. If you only boot TWRP and don't flash it, you can install the app Flashify and use that to back up your stock recovery. Save that back up off of your device along with the backup stock boot image. Then you can flash TWRP if you want. I couldn't get ADB to pull my stock boot image and stock recovery either. You don't need to flash any DM Verity, magisk handles that for you.
[Moto G6 Play Guides, News, & Discussion] gsmccormick:
Thanks Man, i am gonna try that tonight..... Keep ya updated!
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Nowhere in my guide does it say to flash the dm-verity not sure where your getting that from magisk handles the dm-verity patching for us. And don't worry about the bad key thing it changes to N/A once you flash twrp and even then it's nothing to worry about it's just because we're using unsigned stuff. And you have to let the drivers install once you boot up into twrp. It more than likely will say Moto E4 once it installs the drivers so don't worry about that either. Don't flash whatever dm- verity file your talking about. Just follow the guide and flash twrp then push magisk to it and install magisk through twrp
[Moto G6 Play Guides, News, & Discussion] sumner2q:
this might not be the place to post it but the motorola unlocksite is saying my cricket 6g forge cant me bootloader unlock with the code
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Make sure there is no spaces in the code. Use the scrubber tool they offer to help with that. If you entered it correctly and it still is saying that then that simply means your device is not eligible for bootloader unlock unfortunately
[Moto G6 Play Guides, News, & Discussion] madbat99:
Cricket is at&t so... Not likely unlockable.
[Moto G6 Play Guides, News, & Discussion] mafero17:
Enviado desde mi moto g(6) play mediante Tapatalk
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Please remove this is not needed. Thank you. You can find your stock image in the links provided in the guide. After magisk 16.7 we no longer need a patched boot.img
[Moto G6 Play Guides, News, & Discussion] the-her0:
ok, so where's the g6 play device tree? I want to be able to get a more up to date twrp built so that we can access the data partition on our devices, and it'd be way easier to do if I had the device tree to base it off of
[Moto G6 Play Guides, News, & Discussion] madbat99:
Well there isn't one. TWRP for the Moto G6 play is basically a patched version of the one for the E4. we would all like to be able to use encrypted data with TWRP. [MENTION=6485916]squid2[/MENTION] is working on some common trees, but it could be a while.

You could also try checking on the TWRP builders device git repo. They use a tree builder script to build their TWRP. There could be some kind of a tree there. But the only ROMs right now are GSI's. So I think some trees would need to be made to do anything else.
[Moto G6 Play Guides, News, & Discussion] lucasottani:
Help

I follows the steps from the not updated guide at

https://xdaforums.com/moto-g6/how-to/guide-twrp-root-magisk-installation-t3802715

now my phone got a bootloop. I follows it step by step with caution to not miss anything.

when I run:

fastboot flash boot XT1922-5_no_dm-verity_boot.img

it says <bootloader> Image not signed or corrupt. And the process stops in less than one second. I think it's not flashing properly. When I try to flash the recovery.img it says <bootloader> Image size exceeded partition limits.

Also, when I run

adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor

It says error: no devices/emulators found

My bootloader is unlocked and all the drivers are installed correctly. My devices shows up when I type the command fastboot devices.

my phone is the brazilian XT1922-5 version.

Also, at TWRP if I go to Restore, there is nothing there. Is this the correct way to restore the stock firmware?

please help.

--Edit

Trying to follow these new steps and the same "Image not signed or corrupt" shows up when trying to:

fastboot flash recovery moto-g6-play-jeter-patched-twrp.img

That didn't happen when I did this for the first time using the other guide. :(
[Moto G6 Play Guides, News, & Discussion] TNSTIC:
I have been a visitor of this site for many years. However I have not participated in the forums until now. I myself with years of knowledge and a 4 year degree in a related field of study, followed the previous op and got stuck in a soft brick on boot logo. That's not to say anything demeaning or criticize the efforts of the first posted op at all. What happened to the days when coming together and learning and developing improvements for our devices was the most important issue? I agree everyone should get recognition for the effort and time they donate. As for me personally I'll continue to try and be more helpful rather than so quick to criticize one persons effort over another. So in closing thank you sir for your effort and time as well as the all the people who dedicated their time to the first op and each and every person who has ever donated their efforts and more importantly their time to this site for the improvement of our devices.
[Moto G6 Play Guides, News, & Discussion] madbat99:
Well you don't need to flash a boot image anymore. That has changed since magisk 17.1. the warning message that you're getting about the image not being signed is normal, it will still Flash. Before attempting this guide make sure you flash your stock boot image back. the other guy is very outdated and there aren't even modified boot images for the most current firmware. And we don't need them anymore anyways. Just TWRP then use that to flash magisk and you're done.

I don't know what to say about the image size exceeding partition size. you should probably make sure you're downloading the right thing check your downloads check the size of the files before and after you download them.

And when you're trying to back up the vendor with ADB commands, you have to remember that ADB only works if the device is booted. You can't run ADB commands in fastboot mode. Also make sure your cord is good, maybe try a different USB port on your computer.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
I'm sorry for not being on alot and updating the magisk versions quicker here lately. It's the holidays and my work schedule changed from morning to night every other day do I'm basically just been on autopilot lately grinding for Christmas and sleeping lol. Thank you kindly [MENTION=5752019]madbat99[/MENTION] for helping everyone lol. Once the holidays are over I should able to be on regularly again lol
[Moto G6 Play Guides, News, & Discussion] madbat99:
Got the notification for November security patch today.XT1922-7 here. Going to install tonight when I get to my puter
[Moto G6 Play Guides, News, & Discussion] taichipo:
Corrupt disc image

when I tried to fastboot the twrp.mg file to my MOTO G6 Play it kept coming up with corrupt disc img.

please help:(
[Moto G6 Play Guides, News, & Discussion] madbat99:
It always says image not signed or corrupt. It will still proceed.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Unofficial TWRP xt1922 (4,5,7,9)

I've updated TWRP for our device. The ADB commands are no longer needed using the attached image. Just boot it, and make a backup. TWRP now has full vendor support!

Added: Vendor mount/backup/restore/erase.

Fixed: Device build properties now match the G6 Play. It should no longer say "Moto E4" in recovery.

Fixed: Added the proper libs from stock recovery to twrp.

Fixed: Removed the mouse cursor.
[Moto G6 Play Guides, News, & Discussion] madbat99:
Thank you. Very much needed.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
I do what I can. I'm about to drop SuperSU for Oreo. I already have it working on our device along with Viper4android. I've been testing it for days. It is rock solid! Stay tuned, I gotta write some scripts.
[Moto G6 Play Guides, News, & Discussion] Rexidexi:
So... I did try your guide on my XT1922-3 and so far everything works fine. Any suprises I should expect?
[Moto G6 Play Guides, News, & Discussion] madbat99:
Surprises? From rooting? Have you rooted before? Besides the obvious, not trying to take an OTA update? No
[Moto G6 Play Guides, News, & Discussion] Rexidexi:
I mean like SafetyNet suddenly failing or stuff like that. This was one of the first times I did any kind of rooting. Oh and btw... what does OTA stand for?
[Moto G6 Play Guides, News, & Discussion] madbat99:
OTA = Over The Air update. Meaning a system update, security patch, any kind of system update. If you get a system update notification, don't try to take it. It will fail.

Safetynet passes for me with magisk v18
[Moto G6 Play Guides, News, & Discussion] Rexidexi:
Got it. Turned off auto updates any way right from the beginning. Google Play Services shouldn't be a problem right?
[Moto G6 Play Guides, News, & Discussion] Brunolav:
on my device (G6 play/XT1922-5) the touch on recovery does not work
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
If TWRP on the first page of this thread works for you, then mine should as well. I need a little more information. Does it boot? If so, what does work? Can you select anything at all? Etc.

As a side note, that is not a flashable zip. I don't know if you were trying to flash it, but I feel that's worth mentioning just in case.
[Moto G6 Play Guides, News, & Discussion] Brunolav:
Sorry for the lack of information.

Both your and the first page works all the functions to install custom rom and more will except the touch

I can only use it if I connect a USB mouse

Sorry if there are any errors. I'm using the translator.
[Moto G6 Play Guides, News, & Discussion] madbat99:
Services should be fine. Any apps are fine. I mean a system update, from Motorola. Not something from the play store, you can update any of that. System update occur in stock recovery, so TWRP won't install them (unless they are modified) plus they will fail if anything is modified, like the boot.img (from rooting) or any number of changes in /system, sometimes just mounting /system as read/write can cause an update to fail.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Just to clarify; The touch screen is not working on either twrp for you?

If you have a copy of your stock recovery image, please attach it so I can take a look.

PSA

If anyone else using the xt1922-5 could report on twrp's functionality, I would greatly appreciate it. Please let me know if you used the one in OP, mine, or both and how it's working. Thanks in advanced.
[Moto G6 Play Guides, News, & Discussion] Rexidexi:
Alrighty... thank you very much for the detailed answers!
[Moto G6 Play Guides, News, & Discussion] Brunolav:
1 yes any twrp from xda or other sites

2 how can I be making a copy of stock recovery for you?
[Moto G6 Play Guides, News, & Discussion] madbat99:
Did you back it up? ADB pull before flashing TWRP. If not, extract it from the stock firmware for your device.
[Moto G6 Play Guides, News, & Discussion] blowingoff:
I'm usind the TWRP provided in this thread on my xt1922-5 and it works just fine. as phone is encrypted, I can only access /tmp folder through TWRP. as anybody else.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Thank you for the info. I didn't want to dig into a problem unless it could be confirmed.

You can disable encryption by flashing the universal disabler, or using the manual way. You must format data using the yes option in twrp after making the change. You'll be able to mount data afterwards.

Open /vendor/etc/fstab.qcom

Find the line that says,

/dev/block/bootdevice/by-name/userdata /data f2fs rw,discard,nosuid,nodev,noatime,nodiratime,nobarrier,inline_xattr,inline_data wait,check,formattable,forceencrypt=/dev/block/bootdevice/by-name/metadata

Change what I highlighted in red to encryptable.

Save, reboot recovery, format data, and you never have to do this again unless you flash the stock vendor.img.
[Moto G6 Play Guides, News, & Discussion] Brunolav:
my stock recovery https://drive.google.com/file/d/17wW5AFT7LQZ-bsKyKPCKbrhxiRDsQI1w/view?usp=drivesdk
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
I'll take a look.
[Moto G6 Play Guides, News, & Discussion] Brunolav:
thank you
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
You need to change access to the file in your Google drive settings, I am unable to download your recovery image.
[Moto G6 Play Guides, News, & Discussion] Brunolav1:
I can not log into my main account xda

look if it's going now
[Moto G6 Play Guides, News, & Discussion] Unguided79:
TWRP Unresponive

When I run either of the TWRP images on my G6 Play (XT1922-2) I get no response from the touch screen or able to use the volume buttons to move around, so I cannot get past the Decrypt data prompt or swipe to unlock.

I did try to link the stock Boot and Recovery images, but I can't post links currently (10 post requirement)
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
This should not work with the xt1922-2. Which is why I didn't list it. Are you on the Aljeter variant? I do want to get it working for you too, but for right now it only appears to work on the Jeter.
[Moto G6 Play Guides, News, & Discussion] Unguided79:
The baseband version is M8937_24.28.05.72R JETER_EMEA_CUST with a build number OPP27.91-143
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Does your bootloader screen say Jeter or Aljeter? Baseband is usually a good indicator, but not always. The bootloader should know though.
[Moto G6 Play Guides, News, & Discussion] Unguided79:
Product variant is: jeter XT1922-2 32GB P4
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Weird. My guess as to what's going on, is that there are different device tree blobs being used for 8 core and 4 core variants. I can use your stock recovery, and your boot image even though I'm on, OCPS27.91-150-2. The only thing that doesn't work is audio. I'm on the 16gb play. This will take some digging. I have some ideas though. Does the one in the OP work for you, or same problems?
[Moto G6 Play Guides, News, & Discussion] Unguided79:
No the OP twrp is unresponsive as well to both touchscreen and volume control
[Moto G6 Play Guides, News, & Discussion] Brunolav1:
my is xt1922-5

It was meant to work, was not it?

or is mine still incompatible