[GUIDE][ROOT][Moto G6 Play][JETER] TWRP, Root, and Magisk installation OLD guide

[Beefvvl]

I'm having the same exact issue. I bought mine on amazon. It came with firmware OPP27.91-81. I did all the steps and would get bootloops. I tried installing OPP27.91.87 and then tried rooting and still would get the bootloops. I tried reverting to the OPP27.61-14-4 and would get this:

C:\Minimal ADB and Fastboot>fastboot flash partition gpt.bin
target reported max download size of 535822336 bytes
sending 'partition' (45 KB)...
OKAY [  0.004s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.116s

If you can help me figure out how to revert to OPP27.61-14-4 or get root for the latest OPP27.91.87 on the XT-1922-5 somehow.

Thanks for all you do.

I would like the ROM full Motorola Moto G6 Play ROM (XT-1922-5) version OPP27.91-87 (or a way to recover the device). After updating to this version, when doing root, the device has looped. I tried to go back to version OPP27.61-14-4, but RSD Lite fails to flash the gpt.bin file.

I was able to download and flash the complete ROM for the XT1922-5, version OPP27.91-87, but when doing the procedures in this topic (which worked well in the OPP27.61-14-4 version), the device now looped in the "Hello Moto" animation.
I tried to flash the previous ROM (OPP27.61-14-4), but a RSD Lite crash occurs in the gpt.bin file.
I am currently in OPP27.91-87, but no root.:crying:

---------- Post added at 10:07 PM ---------- Previous post was at 09:54 PM ----------



c:\adb>adb reboot bootloader

c:\adb>fastboot boot moto-g6-play-jeter-patched-twrp.img
downloading 'boot.img'...
OKAY [ 0.544s]
booting...
OKAY [ 0.076s]
finished. total time: 0.620s

(TWRP Decrypt Data = Cancel)

c:\adb>adb shell
[6ndd if=/dev/block/platform/soc/7824900.sdhci/by-name/boot of=/external_sd/boot.img
~dd if=/dev/block/platform/soc/7824900.sdhci/by-name/boot of=/external_sd/boo
# t.img[6ndd if=/dev/block/platform/soc/7824900.sdhci/by-name/boot of=/external_sd/
boot.img
/sbin/sh: [6ndd: not found
~ # dd if=/dev/block/platform/soc/7824900.sdhci/by-name/boot of=/external_sd/boo
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.297303 seconds, 53.8MB/s
~ # ^C
c:\adb>adb reboot bootloader

c:\adb> fastboot flash boot XT1922-5_no_dm-verity_boot.img
target reported max download size of 535822336 bytes
sending 'boot' (16384 KB)...
OKAY [ 0.568s]
writing 'boot'...
(bootloader) Image not signed or corrupt
OKAY [ 0.359s]
finished. total time: 0.927s

c:\adb>fastboot flash recovery moto-g6-play-jeter-patched-twrp.img
target reported max download size of 535822336 bytes
sending 'recovery' (16228 KB)...
OKAY [ 0.543s]
writing 'recovery'...
(bootloader) Image not signed or corrupt
OKAY [ 0.266s]
finished. total time: 0.809s

(TWRP does not start that way, so I use fastboot boot)

c:\adb>fastboot boot moto-g6-play-jeter-patched-twrp.img
downloading 'boot.img'...
OKAY [ 0.546s]
booting...
OKAY [ 0.076s]
finished. total time: 0.622s

(TWRP Decrypt Data = Cancel)

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

c:\adb>adb push fstab.qcom /vendor/etc/fstab.qcom
28 KB/s (1696 bytes in 0.058s)

(TWRP = "Wipe">"Swype to Factory Reset" = OK)

c:\adb>adb push Magisk-v16.4.zip /tmp
4111 KB/s (4500886 bytes in 1.068s)

(TWRP = "Install">"Magisk-v16.4.zip" = OK)

(Reboot System...)

(Screen "N/A"...)

(Animation "Hello Moto" in loop...)

 

[ksk35695]

https://forum.xda-developers.com/moto-g6/how-to/getting-lineageos-dev-rahulsnair-moto-t3828115

 

[Beefvvl]

will this work as long as we have the correct boot img for the same firmware we're currently on?

 

[jacob019]

Just spent two hours reverting to stock so I could take the damn update on my Boost Moto G6 Play (XT1922-7). I extracted the updated stock partitions to save some other people the trouble: http://jacobstoner.com/stock-OCP27.91-23-3.zip (give it an hour or two from the time of this post to finish uploading)
Here we have boot, system, modem, recovery, and vendor. It should be enough to update boot and system, do it in the bootloader with a current version of fastboot:
fastboot flash boot boot
fastboot flash system system
then boot into twrp and flash the latest Magisk beta (Magisk-v16.7.zip)
That's all you need to do to update to the latest stock rom. Maybe someone who is more generous with their time will pack it into a flashable zip, but I think this is easy enough.

 

[Beefvvl]

Just spent two hours reverting to stock so I could take the damn update on my Boost Moto G6 Play (XT1922-7). I extracted the updated stock partitions to save some other people the trouble: http://jacobstoner.com/stock-OCP27.91-23-3.zip (give it an hour or two from the time of this post to finish uploading)
Here we have boot, system, modem, recovery, and vendor. It should be enough to update boot and system, do it in the bootloader with a current version of fastboot:
fastboot flash boot boot
fastboot flash system system
then boot into twrp and flash the latest Magisk beta (Magisk-v16.7.zip)
That's all you need to do to update to the latest stock rom. Maybe someone who is more generous with their time will pack it into a flashable zip, but I think this is easy enough.

Can you point me out how to extract it for mine? I have the XT-1922-5

 

[ninjakira]

Just spent two hours reverting to stock so I could take the damn update on my Boost Moto G6 Play (XT1922-7). I extracted the updated stock partitions to save some other people the trouble: http://jacobstoner.com/stock-OCP27.91-23-3.zip (give it an hour or two from the time of this post to finish uploading)
Here we have boot, system, modem, recovery, and vendor. It should be enough to update boot and system, do it in the bootloader with a current version of fastboot:
fastboot flash boot boot
fastboot flash system system
then boot into twrp and flash the latest Magisk beta (Magisk-v16.7.zip)
That's all you need to do to update to the latest stock rom. Maybe someone who is more generous with their time will pack it into a flashable zip, but I think this is easy enough.

404 error

 

[Beefvvl]

404 error

He said give it a couple hours to have time to upload.

 

[ninjakira]

Yeah didnt see that at first

---------- Post added at 05:28 AM ---------- Previous post was at 05:24 AM ----------

was excited about updating lol Been reading on how to patch boot.img with no dm verity but no luck lol

---------- Post added at 04:54 AM ---------- Previous post was at 04:28 AM ----------

so i hopefully i did this correct. i got the updated stock boot.img for the xt1922-7 variant and went into magisk and used the option ''patch boot image file'' and it said it patched the dm-verity to be no dm-verity so here it is if anyone wants to test it. I used magisk beta 16.7 https://drive.google.com/open?id=156z2yYW2VJKoEXXbSEckm6lppKtnBR11

 

[Weeaboo15321]

Could someone make a TWRP image that allows for the mounting of vendor in the "mount" tab? The adb command doesn't seem to work for me. I believe that the Moto g6 TWRP image can do it.

 

[ninjakira]

well i tested out the updated patched boot.img i made and it worked i also i used this in twrp. https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 flash that first then magisk 16.7 and you should have root on the update for the boost mobile variant

 

[jacob019]

well i tested out the updated patched boot.img i made and it worked i also i used this in twrp. https://forum.xda-developers.com/android/software/universal-dm-verity-forceencrypt-t3817389 flash that first then magisk 16.7 and you should have root on the update for the boost mobile variant

You can do it that way, and that's fine. With that method you can avoid TWRP entirely, but you can also just flash stock system and boot and then flash the magisk zip file from within TWRP which I find to be a little easier. When you install the Magisk zip in TWRP it patches the boot image in place, very easy.

Can you point me out how to extract it for mine? I have the XT-1922-5

1. revert to stock
2. take the updates
3. fastboot boot twrp.img
4. adb pull partition images:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/system
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/modem
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/vendor
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery
Boot and system are required at a minimum, but more are be required if you want to use these to revert to stock later for future updates.

 

[Beefvvl]

1. revert to stock
2. take the updates
3. fastboot boot twrp.img
4. adb pull partition images:
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/system
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/modem
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/vendor
adb pull /dev/block/platform/soc/7824900.sdhci/by-name/recovery
Boot and system are required at a minimum, but more are be required if you want to use these to revert to stock later for future updates.

How do I get it to root after that? Sorry I feel like such a noob lol.

Hope this looks right!

C:\Minimal ADB and Fastboot>fastboot boot moto-g6-play-jeter-patched-twrp.img
downloading 'boot.img'...
OKAY [  0.549s]
booting...
OKAY [  0.077s]
finished. total time: 0.628s

C:\Minimal ADB and Fastboot>adb pull /dev/block/platform/soc/7824900.sdhci/by-name/boot
adb server version (32) doesn't match this client (36); killing...
* daemon started successfully *
[   ?] /dev/block/platform/soc/7824900.sdhci/by-name/boot: 16777216/?

C:\Minimal ADB and Fastboot>adb pull /dev/block/platform/soc/7824900.sdhci/by-name/system
[-901] /dev/block/platform/soc/7824900.sdhci/by-name/system: 2516582400/?

C:\Minimal ADB and Fastboot>adb pull /dev/block/platform/soc/7824900.sdhci/by-name/modem
[   ?] /dev/block/platform/soc/7824900.sdhci/by-name/modem: 104857600/?

C:\Minimal ADB and Fastboot>adb pull /dev/block/platform/soc/7824900.sdhci/by-name/vendor
[   ?] /dev/block/platform/soc/7824900.sdhci/by-name/vendor: 419430400/?

 

[jacob019]

Did you use the patched TWRP.img and just rename it or did you use a different one?
How do I get it to root after that? Sorry I feel like such a noob lol.

If you just want to update and root then you don't need to pull the partitions, unless you want a backup. Just revert to stock, apply the updates, boot into twrp with the patched TWRP.img and install Magisk-v16.7.zip.

The no-verity kernel is no longer necessary with the latest Magisk-v16.7, and it wouldn't work anyway as the update has a new kernel. If you want to disable encryption then update /vendor/etc/fstab.qcom and reformat data as well.

Basically, you can just follow the OP after updating, but skip the no-verity kernel and use Magisk 16.7.

Pro tip for free tether, append to /vendor/default.prop:
net.tethering.noprovisioning=true

 

[Beefvvl]

If you just want to update and root then you don't need to pull the partitions, unless you want a backup. Just revert to stock, apply the updates, boot into twrp with the patched TWRP.img and install Magisk-v16.7.zip.

The no-verity kernel is no longer necessary with the latest Magisk-v16.7, and it wouldn't work anyway as the update has a new kernel. If you want to disable encryption then update /vendor/etc/fstab.qcom and reformat data as well.

Basically, you can just follow the OP after updating, but skip the no-verity kernel and use Magisk 16.7.

Pro tip for free tether, append to /vendor/default.prop:
net.tethering.noprovisioning=true

Thanks again!

So do I need to run this step also?

adb push fstab.qcom /vendor/etc/fstab.qcom

 

[jacob019]

So do I need to run this step also?

adb push fstab.qcom /vendor/etc/fstab.qcom

It may be required if you want a decrypted data partition. I did, because otherwise you can't backup data with TWRP.
adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor
adb push fstab.qcom /vendor/etc/fstab.qcom
make sure you format the data partition
after that you can restore userdata or start fresh

 

[ninjakira]

Thanks again!

So do I need to run this step also?

Or use the 2nd link I provided. It does the fstab.qcom stuff. Flash it in twrp. Then flash magisk

 

[Weeaboo15321]

Or use the 2nd link I provided. It does the fstab.qcom stuff. Flash it in twrp. Then flash magisk

If I use this zip, do I still need to mount vendor?

 

[ninjakira]

Alright so after really checking stuff out since it's not 5 in the morning I can confidently say this. The zip file in the link I provided for the universal dm-verity and force encrypt disabler did not work. Once I set my fingerprint up and rebooted I had to enter my password to start android. using the patched fstab.qcom from quiksilver however does still work and the updated patched boot image I made works so just do everything in this guide and instead use the new patched boot image I made for the updated xt1922-7 instead of the onequiksilver provided. As of now this only works on the boost variant.

 

[Pandarenz]

Hi everyone, i´m trying to flash boot and i get this error using fastboot and mfastboot:
target max-sparse-size: 256MB
sending 'boot' (18992 KB)...
OKAY [ 0.505s]
writing 'boot'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.518s

Someone can help me? plz

 

[freddysam]

If I have followed the steps in the first post, what steps do I need to take to go back to stock in order to do a OTA update? Is uninstalling Magisk, flashing the stock boot and recovery enough? I have the XT-1922-5

The reason I ask is because I get an "error" when I tried this during the OTA update.