yashsingh1/xdaforums huggingface dataset:
[Moto G6 Play Guides, News, & Discussion] blowingoff:
oh hell, i've followed every step exactly and got a bootloop. 1922-5 brazilian model. is it because of the last update?

---------- Post added at 07:20 PM ---------- Previous post was at 07:18 PM ----------

and why does my phone show as a moto e4 now????

---------- Post added at 07:26 PM ---------- Previous post was at 07:20 PM ----------

just a thing: i obviously got some backups and i could revert the bootloop by just flashing the stock boot back into the phone.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
if you took the update you have to reflash the updated stock firmware after the update. if need be ill walk you through it ive already done it with one person over facebook messenger and after that they were successful. unfortunately they havent commented on saying so lol or thanked the post. sorry for the late reply also i just got off work lol also if links are dead i got dev access on afh now so ill be putting the new links on here ina bit . also tbh i have no clue why it says moto e4 when we put the twrp recovery on but it doesnt affect anything. it would be nice if we had an official twrp
[Moto G6 Play Guides, News, & Discussion] bote2345:
Moto G6 Play XT1922-3

It still doesn`t work,i flashed the stock JETER_RETAIL_8.0.0_OPPS27.91-35-3_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml,code by code with fastboot and gpt.bin,bootloader.img and oem.img fail flashing.

What should i do?

Every time i boot the phone normally or into bootloader it says bad key,and i also dont see my baseband anymore.

Help me!
[Moto G6 Play Guides, News, & Discussion] blowingoff:
I could imagine it was because we have no official twrp. what do you mean by updated stock image? I'm oj build opp27.91-87.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
You sir need to also use this https://mirrors.lolinet.com/firmware/moto/aljeter/official/RETAIL/. Go to step 19 and follow the reflashing stock firmware instructions. Use the most recent firmware. You can tell which one is new by dates
[Moto G6 Play Guides, News, & Discussion] blowingoff:
mine is the brazilian one, xt1922-5. the downloads are for the 1922-2. can i use it?

---------- Post added at 05:49 PM ---------- Previous post was at 05:45 PM ----------

oh, I think you didn't understand me. I've already reverted the bootloop, my phone is working. but if I flash magisk, it goes to bootloop
[Moto G6 Play Guides, News, & Discussion] ninjakira:
I just got off the phone with Moto they confirm your device is also the aljeter so those firmwares should work for you.
[Moto G6 Play Guides, News, & Discussion] blowingoff:
great. so i'll flash the firmware and try to root from it

---------- Post added at 06:40 PM ---------- Previous post was at 06:25 PM ----------

well. i got an update. I just flash magisk with no modified boot image, no fstab.qcom and such. just flash twrp and then magisk.

phone rooted, safetynet passed. wow!!!!!!!!!!
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Awesome you just helped confirm a couple things on my end to lol like the fstabs.qcom. I'm glad I could be of assistance to you and I'm glad the guide worked. I'll be removing the fstabs.qcom link since they are no longer needed now
[Moto G6 Play Guides, News, & Discussion] Dadud:
I'm pretty sure there's already a Jeter root guide. What's the point in creating a new one?
[Moto G6 Play Guides, News, & Discussion] ninjakira:
The other one was confusing people, and starting to cause more harm than anything. I've already helped a couple people in bootloop that tried to use the old guide and couldn't.
[Moto G6 Play Guides, News, & Discussion] Dadud:
Seems like those people weren't following the the guide TO A T (very important) /skimming thinking it works the old way. I've seen those types of people all over these forums. You're adding more unnecessary clutter to these already cluttered and poorly moderated forums. I'm also pretty sure you don't have permission from kwiksilver to use his files
[Moto G6 Play Guides, News, & Discussion] ninjakira:
I've already talked to a mod about this there looking Into it and trust me man I literally have gone on rants to the people about not skimming before I helped fox there devices. I'm just trying to help everyone the best way I can think of all at once. People before the OTA and after no longer need a patched boot.img because the latest magisk does it. Furthermore we don't need the patched fstabs.qcom as I've recently learned. The device can be unencrypted without all that now thanks to magisk. I've already also told quiksi1ver I'm willing to have mine taking down if he cleans his up and updates it.also a couple devices like the xt1922-3 and 5 are aljeter not Jeter but it seems the xt1922-5 still apply to this guide.
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Also in my post I put the link for the stock firmware along with the proper adb commands to flash said stock firmware from bootloader which ALOT of people also need
[Moto G6 Play Guides, News, & Discussion] blowingoff:
lol this thread is much clearer than the earliest. and also: i've followed the steps from the original thread but i got no response from anyone there. hehhe
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Thank you for that lol I just wanna actually try to help out our fellow g6 play users lol
[Moto G6 Play Guides, News, & Discussion] AcTSkull:
Thanks for creating this new thread, it really is cleaner than before.

Got it working on XT1922-5, brazilian model. Managed to get root and everything is working fine.

But just for curiosity, is there a way to revert it to stock with locked bootloader at all? Already flashed stock rom, my only problem is not being able to relock it.

Hope to see some new roms coming for our device soon!
[Moto G6 Play Guides, News, & Discussion] ninjakira:
Removed commands for bootloader relock because they don't work ignore this post
[Moto G6 Play Guides, News, & Discussion] AcTSkull:
Of course not! We are all here to learn, share and have fun with it.

Anyway, it didn't work. Still boots up with the Bad Key at the top and grayed out "unlocked oem" at developer options.

Let's wait and see if (when available around here, not OTA) flashing a new firmware will fix it, perhaps, as it updates the version to 27.91-147 (will confirm it later).
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Awesome stuff. Does everything appear to be working? If so, then you are safe to flash it. I think that'll work on all the 32gb G6 Play variants. Huge thanks for testing! I really couldn't do this by myself. The only feature you guys are lacking is partitioning the external sdcard. You can wipe it, or change file system on it though. I'll have to sort that out in the future. All other features should be working, even vendor mounting.
[Moto G6 Play Guides, News, & Discussion] Jboii36:
This does not work on the cricket variant

---------- Post added at 01:19 AM ---------- Previous post was at 01:14 AM ----------

I have the cricket version xt1922-9 really wish there was a way around this twrp n root would make this phone great
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Give me your stock recovery image, and I'll see what I can do.
[Moto G6 Play Guides, News, & Discussion] Jboii36:
The bootloader cant be unlocked no way to flash twrp with a locked bootloader right
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
They locked the OEM toggle on a Motorola? I definitely believe you. That does sound crazy though. Is it even present in the dev options? As in visible but greyed out?
[Moto G6 Play Guides, News, & Discussion] Jboii36:
Yes it's present and I have it turned on when I go to the Motorola bootloader unlock page it says my device is not supported
[Moto G6 Play Guides, News, & Discussion] jglm4u:
Does this mean soon will have official twrp for play variants?
[Moto G6 Play Guides, News, & Discussion] Jboii36:
It's present and turned on when I go to bootloader unlock page it tells me my device is not supported
[Moto G6 Play Guides, News, & Discussion] madbat99:
Cricket is AT&T. All locked bootloaders. No unlock code given from Motorola. Cricket users come in here every now and then hoping they've heard wrong. But, sad to say, no root without an unlocked bootloader.

Most of them are hoping for an exploit or 1 click like in the old days. But it just doesn't work that way anymore.

---------- Post added at 02:37 AM ---------- Previous post was at 02:34 AM ----------

We got it the first time. Sorry bro, no root on at&t, or cricket.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Official? No, I can't build from source yet.

Not supported? I'd like you to run this command in fastboot, then send me a private message with the output. I don't want to clutter the thread with another topic, so please don't post it here. I will look into this problem. No promises though.

fastboot oem get_unlock_data
[Moto G6 Play Guides, News, & Discussion] Brunolav:
Hi friend

You remind of the guy who could not use touch

TWRP is working fine

But it does not recognize the internal storage (I have to install through the sd card)

But it's not the question

I wanted to know if you can do these things at TWRP that you did "for me"
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Internal storage shows 0mb because your phone is encrypted.

To fix it...

1. Mount the /vendor and /system partitions

2. Flash the dm-verity disabler found in this thread.

3. Format data using the "yes" option in twrp.

4. Reboot.

Twrp will now be able to see the /data partition.

Once encryption is disabled you won't need to do this again, unless you restore your /vendor partition.

Someone else has touch issues with TWRP on another device? Tell them to send me a message and I'll try to help them out.
[Moto G6 Play Guides, News, & Discussion] Donavonn:
V4A already works doesn't it? I've been using it. However, I had to use a couple of the magisk modules to get it to work with YouTube.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Viper works. Magisk doesn't work properly though. It causes my boot animation to play 2x every time I reboot. I got tired of it, so I found a way to use SuperSU. I never released it because scripts have trouble executing through terminal. They do work, but sometimes it's a pain. Everything else works perfectly.

If you want SuperSU...

1. Grab /vendor/etc/selinux/precompiled_sepolicy and rename it to sepolicy.

2. Manually patch sepolicy with the SuperSU binary for sdk26, and make a copy.

3. Rename one sepolicy file to precompiled_sepolicy and push it back to /vendor/etc/selinux. Set permissions 0644.

4. Unpack the boot.img and add the other patched sepolicy file to the ramdisk. Make sure it's named sepolicy. Repack the image.

5. Remove dm-verity from the new boot.img. Then flash it.

6. Flash SuperSU.

I have not yet made this work on GSI's. I still have to use Magisk running those. It only works on stock.

For anyone on the xt1922-7 variant who wants an easy SuperSU, check the attachments.

1. Mount /vendor and copy the precompiled_sepolicy to /vendor/etc/selinux and set permissions to 0644.

2. Flash my G6SuperSU boot.img.

3. Flash SuperSU-v2.82-SR5

Optional: Flash Viper4Android 1.8.2 after the first boot.

Note: My G6SuperSU boot.img has dm-verity already disabled. It can also be used with Magisk instead of SuperSU if you're on a GSI. Just flash Magisk after flashing the boot.img.
[Moto G6 Play Guides, News, & Discussion] whodisname:
I have this phone, unlocked bootloader, broken lap top and a Chromebook. I have twrp installed and can boot to it. Can anyone please help me out with this? Indeed a flashable zip, or a twrp backup. Can I get one??

I buggered it up, no OS installed, etc. Can't use Odin or RSD lite. Am very familiar with allk this, tho. Flashaholic, etc.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
If you have an xt1922-7 I'll do it for you. If you have another model then list it, and I'll see if I can make a system.img for you to install. I have the tools for it.
[Moto G6 Play Guides, News, & Discussion] Donavonn:
Thanks buddy! 2 questions:

1. The mount command isn't working for me (mount -o rw,remount /vendor). I still get the message saying it's read-only. Is there a specific command I need to use?

2. What do you mean when you say, "flash after the first boot"?
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
If you're using my TWRP just mount /vendor in the options menu, and use the built in file explorer. Otherwise... I'll edit this shortly. I need to find that command, it's long and painful.

For #2. I mean after rooting, let the phone boot once with SuperSU installed. Then install Viper. Otherwise viper will not see SuperSU and place the correct files.
[Moto G6 Play Guides, News, & Discussion] whodisname:
That's the one that I have. I'd really appreciate it. I'm on the most busted device there is.
[Moto G6 Play Guides, News, & Discussion] Donavonn:
I did some research on it a while back and installed BusyBox through Magisk, then used, "busybox mount -o rw,remount /" which worked for letting me uninstall system apps with the app, "system app remover", but I still got the, "this is read-only" error on some things. I don't want to have to resort to installing BusyBox if there's an easier, official more reliable way.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
No worries, I made a system.img a few hours ago. I'll upload it shortly and drop you a link. Do you need the boot.img too? And if so, do you want dm-verity disabled?

---------- Post added at 08:16 PM ---------- Previous post was at 08:10 PM ----------

If you're using Magisk, cannot delete or read only errors come from module mode. Go into magisk's settings and enable the core only function and reboot. Do your app removal, change it back and reboot once more. This error usually happens when deleting things in /system/priv-app. SuperSU doesn't have this issue. Another reason I made it work.
[Moto G6 Play Guides, News, & Discussion] whodisname:
I had unlocked the bootloader, so I don't think I need a boot.IMG, but I am not sure. So if that's not an issue, I'll take it with dm-verity disabled. Thanks, man, you are awesome for that!

So would I just install this in TWRP like any custom ROM?
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Yes, just install it as you would any other ROM. Wipe, /cache, /dalvik, /data, /system. Not working, link removed. And here's the no verity boot.img.

The ROM itself contains the stock boot.img with verity still intact. You need to flash the no verity boot.img after installing the ROM. That first start takes a while, so give it time. (The update check I mean.) If for some reason it does not work, I'll upload a backup of my system, which is debloated, but it has the play store & chrome, and it will get you going again.
[Moto G6 Play Guides, News, & Discussion] whodisname:
Its been checking for updates for about 30 min. I wiped 3 times cuz I'm old, and installed the ROM, then the no-verity boot.img with twrp. Its so close, maybe I need to continue to wait?

Edit: over an hour.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Alright, I'll call that one a huge fail. (Probably a symlink issue.) Hold tight, I'll upload my system backup. Heads up, viper is in the system, and its going to error when you open it. Flash Viper 1.8.2 or later to remove it. Then you're free to reinstall it if you want. I suggest using the no verity boot.img from my last post with this.

---------- Post added at 05:05 AM ---------- Previous post was at 04:21 AM ----------

@whodisname

Just unzip this file, and copy the whole "TWRP" folder to your phone and your recovery should see it. I preserved the folder structure. xt1922-7 system backup.
[Moto G6 Play Guides, News, & Discussion] madbat99:
[MENTION=7718083]Spaceminer[/MENTION]

I also opened an issue on GitHub to get the latest source

Moto g6 play xt1922-7 Jeter

OCPS27.91-150-2

Should be up by Friday.

https://github.com/MotorolaMobilityLLC/kernel-msm/issues/197#issuecomment-456255701
[Moto G6 Play Guides, News, & Discussion] whodisname:
That fixed her all the way up, that's a nice slim version of it you have there! 100% working. I'm on it right now.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Yeah, I pulled some Lineage apps to replace the ones that don't work without Google services. I'm glad you're running again. It could've easily been me in that situation.

---------- Post added at 07:36 AM ---------- Previous post was at 07:34 AM ----------

Awesome! I'll be watching for it.
[Moto G6 Play Guides, News, & Discussion] Donavonn:
[MENTION=7718083]Spaceminer[/MENTION]

I see what you mean about the black things that appear at the bottom. Have you found a way to fix that yet or are you still facing the issue?
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
No fix yet. I've sent logs to both Motorola and Virgin Mobile at this point. Their response was to scratch their heads. I believe it's a problem in the kernel source. The 4 core variant is actually an msm8920, the 8 core is an msm8937. They share pin compatibility, but they aren't the same. (This is the reason why I had to fix TWRP's touch problem.) Motorola, instead of writing source code for our device, used shims to make the msm8937 code work on the msm8920. So, our 4 core thinks it's an 8 core that has no power or response from cores 4-7...
[Moto G6 Play Guides, News, & Discussion] Donavonn:
I couldn't find "Viper4Android 1.8.2" so I just installed the latest version I found on Google, however, it gets stuck on "Installing Driver". Do you have a link to the 1.8.2 version by any chance?
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Did you flash it? You need to flash it from twrp. Also make sure to mount /vendor. I do have a copy, I just want to make sure it's no longer being hosted before I share it, since it's not my work. zackptg5 is the one who created it.
[Moto G6 Play Guides, News, & Discussion] Donavonn:
[MENTION=7718083]Spaceminer[/MENTION]

I'm not sure if you read my previous message before I edited it but I was having issues with flashing the V4A, something about it not being able to mount storage, so I read around this thread and seen that I needed to disable force encrypt so that the TWRP could read my internal storage. So I went to the link you posted a couple pages back, downloaded the "Disable_Dm-Verity_ForceEncrypt_12.16.2018.zip", flashed it, however my phone still encrypts on boot, which leads it to TWRP not reading my internal storage again. What should I do to fix this? (Maybe it has something to do with me using your boot.img that you posted?)

Also, do you only us V4AFX, or do you use the audio modification library and compatibility patch for it as well?
[Moto G6 Play Guides, News, & Discussion] madbat99:
Did you format data and type "yes" in TWRP? I believe his boot.img already had forced encryption disabled. But you still have to format to remove encryption. Backup your files, formatting data will wipe your internal storage.
[Moto G6 Play Guides, News, & Discussion] Donavonn:
Yeah I did all of that, but every time I reboot it still encrypts.
[Moto G6 Play Guides, News, & Discussion] madbat99:
Oh, got it. I usually use this force encrypt disabler for my devices. It works for me so far. And magisk of course does it if you select the option. But that zip inserts the file so magisk will do it automatically if flashed.
[Moto G6 Play Guides, News, & Discussion] Donavonn:
Does this still work even if I'm not using magisk? I'm using SuperSU with what [MENTION=7718083]Spaceminer[/MENTION] provided.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Yes, it does. My boot.img has verity disabled, but you do need to disable encryption still. Just make sure /vendor is mounted and that's guaranteed to work. The author did a great job. You don't even need to be rooted to use that.
[Moto G6 Play Guides, News, & Discussion] Donavonn:
That's the one I'm using. Didn't notice the first time you sent; I assumed it was different than the one [MENTION=7718083]Spaceminer[/MENTION] posted.

I done everything that was in the instructions and in different ways as well but it still encrypts. I'm flashing it through adb sideload, could that be why? Adb pushing it to /tmp gives me validation error
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
That probably is the problem. I've always flashed it from my external sdcard in twrp.
[Moto G6 Play Guides, News, & Discussion] Donavonn:
Yeah man, I'm getting the same problem. I even completely formatted everything, installed stock firmware, booted it once, booted in twrp, formatted data, flashed the forceencrypt, formatted data, booted and it encrypts still. I'm not sure what I'm doing wrong. I just tried by using "adb push zip /tmp" and flashed but still nothing. It still encrypts.
[Moto G6 Play Guides, News, & Discussion] madbat99:
I don't think you need to format again after flashing it. Just before. And definitely make sure vendor is mounted before you flash it.

Did you download the latest version? Can't think of any other reason it would still encrypt.

Are you flashing TWRP, or just booting it? You should have TWRP installed as recovery. Start in TWRP, format data, reboot TWRP, then flash force encryption disabler.

From the op of that zip

If you're currently encrypted: BACKUP YOUR INTERNAL STORAGE TO YOUR PC. Then format data. Reboot back into recovery

After doing that or if you're not encrypted: Flash your rom, custom kernel (if applicable), then this zip, the magisk/supersu/other root, then anything else like gapps

This zip should be flashed after anything that modifies your boot img (like a custom kernel) but before magisk/supersu since this zip creates the files that tells magisk/supersu to not encrypt
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Did you mount /vendor in twrp before flashing it? Also, do you have an external sdcard to flash it from?
[Moto G6 Play Guides, News, & Discussion] Donavonn:
I don't have an external sdcard. I'm just pushing it on to /data

This is exactly what I'm doing:

(completely starting from scratch)

Boot to TWRP, format data, then advanced options and checking everything and formatting. After that I boot to bootloader and run these:

fastboot oem fb_mode_set

fastboot flash partition gpt.bin

fastboot flash bootloader bootloader.img

fastboot flash modem NON-HLOS.bin

fastboot flash fsg fsg.mbn

fastboot erase modemst1

fastboot erase modemst2

fastboot flash dsp adspso.bin

fastboot flash logo logo.bin

fastboot flash boot G6Supersu.img

fastboot flash recovery twrp.img

fastboot flash system system.img_sparsechunk.0

fastboot flash system system.img_sparsechunk.1

fastboot flash system system.img_sparsechunk.2

fastboot flash system system.img_sparsechunk.3

fastboot flash system system.img_sparsechunk.4

fastboot flash vendor vendor.img

fastboot flash oem oem.img

fastboot erase carrier

fastboot erase cache

fastboot erase userdata

fastboot erase DDR

fastboot oem fb_mode_clear

fastboot reboot (to boot once so I'm able to flash the zip without errors)

Boot into recovery, I then format data, mount /vendor and /system, 'adb push zip /data', flash the zip (Disable_Dm-ForceEncrypt_12.16.2018.zip), reboot and it encrypts again.
[Moto G6 Play Guides, News, & Discussion] madbat99:
You missed the one important step from the author of that zip. Boot to recovery, format data (not just wipe of course) REBOOT RECOVERY, then flash the zip for disabling encryption. Then you can boot system.

The rebooting of recovery in between the format and flashing of the zip is important, according to the author.
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
[MENTION=9642598]Donavonn[/MENTION]

If you didn't get it working already, rename the file in the attachments to fstab.qcom and use twrp's file manager to move it to /vendor/etc, and set permissions to 0644. If you're already encrypted, just format /data after moving the file. There is no way this won't work.
[Moto G6 Play Guides, News, & Discussion] Donavonn:
This is how to set the permissions, right?

chmod 644 /vendor/etc/file
[Moto G6 Play Guides, News, & Discussion] Spaceminer:
Yes. Don't forget the "0" in, chmod 0644 /vendor/etc/fstab.qcom