[GUIDE][ROOT][Moto G6][ALI] TWRP, Root, and Magisk installation guide.

[Android-Jack]

---------- Post added at 09:10 PM ---------- Previous post was at 08:49 PM ----------

Quote:
Originally Posted by Xero1017
Successfully rooted my g6 1925-6 with the 19-4 build. Only issue now is that I cannot setup fingerprint security at all. I went through device setup and did fingerprint + pattern, entered pattern but it kept looping back when I needed to setup fingerprint. I skipped it thinking it was a temp glitch but now when I go to settings it keeps crashing when I click on fingerprint setup.

Anyone else with this issue?

Update, wiped my cache, re installed magisk zip, footed and got fingerprint capabilities back but now the play store won't run... going to try again when I'm back home. Curious if anyone else noticed play store, fingerprint reader, or any other 'core' function not working after rooting?

Thanks

Did you resolve the issue?

===========================================================

Want to buy a Moto G6 XT1925-6, USA, and read through this thread. Want to confirm that the post #1 instructions are good for this variant before purchase? Their are not many root G6 threads or root confirmations and success posts .

Thanks!

 

[stifmaster81]

on the web lolifirmware do not take more images of the motorcycle g6, the monthly performances are only by ota?

Enviado desde mi moto g(6) mediante Tapatalk

 

[Alexibarra98]

on the web lolifirmware do not take more images of the motorcycle g6, the monthly performances are only by ota?

Enviado desde mi moto g(6) mediante Tapatalk

I do not know but you dont miss much the July patch does not change anything important

 

[stifmaster81]

I do not know but you dont miss much the July patch does not change anything important

As you can tell from a Nexus to this phone ... my god what a phone potato

Enviado desde mi moto g(6) mediante Tapatalk

---------- Post added at 07:02 PM ---------- Previous post was at 06:56 PM ----------

What is the last motorcycle patch g 6 Ali? the one from maio? or is there another more updated? If so, can you pass the link? Thank you

Enviado desde mi moto g(6) mediante Tapatalk

---------- Post added at 10:47 PM ---------- Previous post was at 10:41 PM ----------

how much to the last thing, I just have to put the official rom of my mobile XT1925 / 4, but if I put for example XT1925 / 10 what would happen? and the last question, when updating would be worth the boot. img

Enviado desde mi moto g(6) mediante Tapatalk

Someone can clarify the doubt ... Thank you forum. . .

Enviado desde mi moto g(6) mediante Tapatalk

 

[Alexibarra98]

As you can tell from a Nexus to this phone ... my god what a phone potato

Enviado desde mi moto g(6) mediante Tapatalk

---------- Post added at 07:02 PM ---------- Previous post was at 06:56 PM ----------

Someone can clarify the doubt ... Thank you forum. . .

Enviado desde mi moto g(6) mediante Tapatalk

you can do it, if the firmware corresponds to your model then when flashing it will start, it will work but it can give you some problems like 4g or wifi, do it at your own risk, I recommend you make a backup in twrp before

---------- Post added at 06:41 PM ---------- Previous post was at 06:35 PM ----------

I can make a backup with my security patch for July (OPS27.82-87) and upload it but as I said it can give you problems if you install it, better wait for your cell phone to update

 

[stifmaster81]

Extras:

THIS AREA STILL CONTAINS LEGACY DOWNLOADS AS WELL AND ARE THUS NOT ENSURED TO WORK


The following is provided for backup purposes only in case you forgot to back up. When pulled from the phone, the images are the full partition size, not actual size.

XT1925-6 (OPS27.104-15-10) Factory pulled files
These files will get you back to stock as far as this guide is concerned. Remember though, 'bad key' will be displayed as they were pulled from a device instead of being provided by Motorola
Factory boot image - XT1925-6_factory-boot.img
Factory recovery image - XT1925-6_factory-recovery.img
Factory fstab.qcom file - factory-fstab.qcom - You can push this file to /vendor/etc/ to go back to stock vendor parition if you need. Factory boot images will probably have an issue booting without vendor being completely stock.


The following images have been provided by other XDA members:
XT1925-2
Factory boot image - XT1925-2_factory-boot.img
XT1925-4
Factory boot image - XT1925-4_factory-boot.img
XT1925-5
Factory boot image - XT1925-5_factory-boot.img

for the new version 82-87 the boot.img of the 82-72 version does not work in bootloop, will you release new versions of the boot?

 

[dejello]

for the new version 82-87 the boot.img of the 82-72 version does not work in bootloop, will you release new versions of the boot?

Upload and provide a link and I'll get on it :good:

[EDIT] Found the zip link on lolinet... You can try this: OPS27.82-87_no-verity_boot.img Let me know if it's working and I'll add to to the first post.

 

[Alexibarra98]

yes it worked, thanks dude

 

[stifmaster81]

Upload and provide a link and I'll get on it :good:

[EDIT] Found the zip link on lolinet... You can try this: OPS27.82-87_no-verity_boot.img Let me know if it's working and I'll add to to the first post.

goes perfect on Xt1925-4
Thank you for your time and dedication

 

[ChefGeoff]

Sorry wrong terminology, I can boot into TWRP but when I go to install the magisk zip (what I was calling flashing) I cannot get the data partition to mount no matter what I do. I've gone step by step in this guide multiple times and can't get data to mount.

Any ideas? Thanks

You have to flash twrp after you boot into twrp, and then reboot into recovery and then you have to wipe data and then you can see contents of SD card to flash magisk.

 

[stifmaster81]

https://forum.xda-developers.com/pr...e-development/converting-device-to-b-t3834499


it would be a breakthrough if you can do this

Enviado desde mi moto g(6) mediante Tapatalk

 

[tomjohnson9009]

If you have device not found then you need to ensure the usb device is installed correctly. Once correct drivers are installed it should work as expected

The drivers were fine. The fact I was flashing anything was proof. My problem ended up being I was flashing the incorrect file. 19-4 no verity worked perfectly and I am now rooted. Dragging files into the command prompt window for pushing files on to my phone was easier than figuring out where the adb folder is on my computer. For example "adb push (file in your download folder on your computer)".

 

[dejello]

Added OPS27.82-57_no-verity_boot.img. Please let me know how it works out so I can update the first post (Model number and such).

 

[Jleeblanch]

EDIT...

Moved post to Stock Firmware thread OTA Update - XT1925-6 OPSS27.104-15-10-4

 

[Android-Jack]

EDIT...

Moved post to Stock Firmware thread OTA Update - XT1925-6 OPSS27.104-15-10-4

Have new unrooted phone with opss27.104-15-10. how can it be root with the update? Or is root limited to the no_verity builds per post #1 links?

Thanks!

 

[Jleeblanch]

Have new unrooted phone with opss27.104-15-10. how can it be root with the update? Or is root limited to the no_verity builds per post #1 links?

Thanks!

I've been busy most of the day, but am working on that as we speak.

Make sure to backup your updated stock boot.img (using the steps provided in the OP) before you attempt any messing around. I've personally tried a few things and each time I've ended up in a boot loop and even a couple times (mostly due to the forced encryption) I've had to re-flash the stock rom and start from scratch. I have not yet manually patched the boot.img myself to remove the "verify" flag from /system & /vendor as I wanted to experiment a little being that I was running a clean unmodified setup.

One good thing that's came out of this tho was I created a nice little script for Linux users to re-flash the stock rom for our device. I'll probably share that in the [STOCK][ALI] Firmware Moto G6 thread at some point.

 

[Android-Jack]

I've been busy most of the day, but am working on that as we speak.

Make sure to backup your updated stock boot.img (using the steps provided in the OP) before you attempt any messing around. I've personally tried a few things and each time I've ended up in a boot loop and even a couple times (mostly due to the forced encryption) I've had to re-flash the stock rom and start from scratch. I have not yet manually patched the boot.img myself to remove the "verify" flag from /system & /vendor as I wanted to experiment a little being that I was running a clean unmodified setup.

One good thing that's came out of this tho was I created a nice little script for Linux users to re-flash the stock rom for our device. I'll probably share that in the [STOCK][ALI] Firmware Moto G6 thread at some point.

So i should:

OTA update patch?
Backup updated build?
Install no_verity per OP or wait for a no_verity with update/patch from you?

Appologies for the basic noob questions. I have successfully rooted two different phones in the past few years and both times went pefect on first attempt. This phone has me a bit more concerned/intimidated.

On win 10, not linux.

 

[Jleeblanch]

So i should:

OTA update patch?
Backup updated build?
Install no_verity per OP or wait for a no_verity with update/patch from you?

Appologies for the basic noob questions. I have successfully rooted two different phones in the past few years and both times went pefect on first attempt. This phone has me a bit more concerned/intimidated.

On win 10, not linux.

Wait for updated patched boot.img from myself or the OP.

I would also hold off on permanently flashing TWRP as it probably won't stick anyway. But you can fastboot boot twrp.img to back up stock images (at minimum boot and recovery). Just follow that section in the OP to backup as much as you can. I personally backed up system, vendor, boot, recovery, persist, logo and oem (I think more partitions too) as well as fstab.qcom. That last one is the same as the previous version so if you already did that, don't stress it.

 

[Jleeblanch]

OPSS27.104-15-10-4 OTA Update

I finally had a chance to mess with the boot.img from the latest OTA update for OPSS27.104-15-10-4 (retus).

I was able to successfully remove verity and gain root with Magisk! I'll upload the new boot.img here shortly for the users who accepted the OTA update and want to root.

I'm also happy to note that my custom kernel also works on the latest update, so I'll be opening a new thread in the Moto G6 development section later on today as well

Another thing, I'm also trying to work on another option for ALL Moto G6 users to be able to remove verity (and root if you want) without the need to maintain new boot.img's every time there is an OTA update. No promises just yet, but I got some ideas. It would make things a hell of a lot easier for everyone if I can pull it off.

 

[Android-Jack]

I finally had a chance to mess with the boot.img from the latest OTA update for OPSS27.104-15-10-4 (retus).

I was able to successfully remove verity and gain root with Magisk! I'll upload the new boot.img here shortly for the users who accepted the OTA update and want to root.

I'm also happy to note that my custom kernel also works on the latest update, so I'll be opening a new thread in the Moto G6 development section later on today as well

Another thing, I'm also trying to work on another option for ALL Moto G6 users to be able to remove verity (and root if you want) without the need to maintain new boot.img's every time there is an OTA update. No promises just yet, but I got some ideas. It would make things a hell of a lot easier for everyone if I can pull it off.

Great!!

You mentioned in an earlier post not to "permanently flash twrp". Doesnt the op unstructions flash twrp permanently?