mod please remove

[ninjakira]

mod please remove this thread

 

[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.

 

[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

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.

 

[bote2345]

Moto G6 Play XT1922-3

/*
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections, ligma,
* thermonuclear war, or your mom getting upset with you for being on the computer all day

Please
* Ensure you have an advanced understanding of this device before flashing it! YOU are choosing to make these modifications or your own free will.
*/

I've decided to make a new guide for our jeter devices because the other guide is a little sloppy now lol. I have no problem with having this taking down if the op for the original guide decides to clean theirs up. this one should help clear up stuff now at least lol

This has been confirmed to work on:
XT1922-3 Model
XT1922-4 Model
XT1922-5 Brazilian Model
XT1922-7 Boost Mobile
XT1922-9 Model

Please make backups using TWRP IN CASE OF FAILURE.

Original stock firmware can be found here. https://mirrors.lolinet.com/firmware/moto/jeter/official/

The steps listed in this process WILL wipe your userdata. If you have anything you need to save back it up first.


Prerequisites:
Unlocked bootloader.
ADB/Fastboot installed on your machine ( https://developer.android.com/studio...platform-tools ) If you have issues with commands make sure you have a current build of ADB and fastboot.

Minimal adb/fastboot v1.4.3 installer can be found here. https://androidfilehost.com/?fid=746010030569952951

Step 1.) Download twrp image to the ADB/Fastboot folder on your computer. https://www.androidfilehost.com/?fid=1322778262904017969

Step 2.) Reboot to your bootloader. You can do this by turning on your device and holding power and both volume buttons at the same time.

Step 3.) Once the device reboots to the bootloader type the following from your computer with your phone connected via USB.

Code:
fastboot boot moto-g6-play-jeter-patched-twrp.img

Step 4.) Once TWRP boots from your computer type (it may take a bit to boot because it is trying to decrypt your userdata, but it will fail and prompt for a password. Just click cancel):
Code:
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
This will backup your stock boot and recovery images if you to revert to stock later.

Step 5.) Code:
adb reboot bootloader

Step 6.) Run the following command from your computer to install the TWRP image to your device.
Code:
fastboot flash recovery moto-g6-play-jeter-patched-twrp.img

Step 7.) Use the volume keys on the device to select boot to recovery and TWRP will boot up again. When it prompts for a decryption password select cancel again.

Step 8.) From your computer type the following into your command prompt/terminal from your adb/fastboot folder:
Code:
adb shell mount -o,rw /dev/block/platform/soc/7824900.sdhci/by-name/vendor /vendor

Step 9.) Download and extract https://www.androidfilehost.com/?fid=1322778262904017972 this patched fstab.qcom boot image into the ADB/Fastboot folder on your PC.

Step 10.) Run the following command from command prompt/terminal on your computer:
Code:
adb push fstab.qcom /vendor/etc/fstab.qcom

Step 11.) Next click the "Wipe" button in TWRP and slide "Swipe to Factory Reset" THIS WILL WIPE YOUR DATA ON YOUR PHONE. Ensure you have backup.

Step 12.) Download the Magisk Beta 17.2 zip file from https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445 to your ADB/Fastboot folder.

Step 13.) Run the following command to push the boot image to your device
Code:
adb push Magisk-v17.2.zip /tmp
This will push the Magisk-v17.2.zip to your /tmp folder

Step 14.) Flash Magisk-v17.2.zip from TWRP using the install option and navigate to the /tmp folder to select it and install it.

Step 15.) Reboot your device

Step 16.) It will say N/A in the top corner of your device for a few seconds. Then it will boot the the Motorola boot screen and you can setup your device as a new phone.

Step 17.) Verify Magisk Manager is installed and the root functionality works. if force encrytion is checked just uncheck it, click install then whatever option magisk recommends then reboot.

step 18.) have fun.

Step 19.)DOWNLOAD STOCK FIRMWARE HERE https://mirrors.lolinet.com/firmware/moto/jeter/official/ UNZIP STOCK FIRMWARE TO YOUR ADB/FASTBOOT FOLDER TO FLASH IT. TO REVERT BACK TO STOCK YOU HAVE TO REFLASH STOCK FIRMWARE FROM THE BOOTLOADER if your device is bootlooped or bricked or not working right you have to reflash the stock firmware your device came with. PLEASE INPUT THESE COMMANDS ONE AT A TIME DO NOT DO THEM ALL AT ONCE. I KNOW ITS A HASSLE BUT IT GUARANTEES A SUCCESSFUL REFLASH. I CANNOT EMPHASIZE THIS ENOUGH

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 flash dsp adspso.bin
fastboot flash boot boot.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 oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot oem fb_mode_clear
fastboot reboot

if you guys think anything should be edited from this let me know and ill fix it. like im not 100% sure if we still have to use the modified fstabs.qcom i just used it still after i took the update and re-rooted. so if someone can tell me they didnt use the fstabs.qcom and still got the same results please let me know

Credits: @kwiksi1ver for making the original guide. and @topjohnwu for magisk. and @shimp208 for minimal adb/fastboot.

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!

 

[blowingoff]

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

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.

 

[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

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.

 

[blowingoff]

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

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

 

[ninjakira]

I just got off the phone with Moto they confirm your device is also the aljeter so those firmwares should work for you.

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

 

[blowingoff]

I just got off the phone with Moto they confirm your device is also the aljeter so those firmwares should work for you.

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!!!!!!!!!!

 

[ninjakira]

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!!!!!!!!!!

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

 

[Dadud]

I'm pretty sure there's already a Jeter root guide. What's the point in creating a new one?

 

[ninjakira]

I'm pretty sure there's already a Jeter root guide. What's the point in creating a new one?

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.

 

[Dadud]

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.

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

 

[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.

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.

 

[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

 

[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

 

[ninjakira]

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

Thank you for that lol I just wanna actually try to help out our fellow g6 play users lol

 

[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!

 

[ninjakira]

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!

Removed commands for bootloader relock because they don't work ignore this post

 

[AcTSkull]

I personally have not used this yet to relock my bootloader so I cannot say 100% this will work. So please don't get mad at me if not. If it works for you please let me know and I'll add it to the post

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).