Database Info

[GUIDE] Rooting Mi A1 without TWRP

Device will be wiped if your bootloader isn't already unlocked.
Obviously, before doing this, you should enable OEM unlocking and ADB debugging in Developer Options. Also you should have ADB and Fastboot on your system (meaning they work on any directory). I use this version, just accept the installation of both the ADB/Fastboot drivers and the Google Device Drivers and you should be good to go.
Below you can find the untouched boot.img for the version you are on (or you can extract them yourselves, guide at the bottom of the thread):
2018:
March (V9.5.9.0.ODHMIFA) (OTA)
April (V9.5.10.0.ODHMIFA) (OTA)
May (V9.5.11.0.ODHMIFA) (OTA)
June (V9.6.2.0.ODHMIFE) (OTA)
June (V9.6.3.0.ODHMIFE) (OTA)
July (V9.6.4.0.ODHMIFE) (OTA)
August (V9.6.5.0.ODHMIFE) (OTA)
September (V9.6.6.0.ODHMIFE) (OTA)
October (V9.6.7.0.ODHMIFE) (OTA)
November (V9.6.8.0.ODHMIFE) (OTA)
December (V10.0.3.0.ODHMIFE) (OTA)
2019:
January (V10.0.4.0.ODHMIFE) (OTA)
January (V10.0.4.0.PDHMIXM) (OTA)
February (V10.0.5.0.PDHMIXM) (OTA)
March (V10.0.7.0.PDHMIXM) (OTA)
April (V10.0.8.0.PDHMIXM) (OTA)
May (V10.0.9.0.PDHMIXM) (OTA)
June (V10.0.10.0.PDHMIXM) (OTA)
July (V10.0.11.0.PDHMIXM) (OTA)
August (V10.0.12.0.PDHMIXM) (OTA)
September (V10.0.13.0.PDHMIXM) (OTA)
October (V10.0.14.0.PDHMIXM) (OTA)
November (V10.0.15.0.PDHMIXM) (OTA)
December (V10.0.16.0.PDHMIXM) (OTA)
Here we go:
GENERATING THE PATCHED BOOT.IMG
0. Download a suitable UNTOUCHED boot.img from above or extract one yourself by using the OTA links and dumping the image using the guide on the bottom of this thread.
To check which one is suitable for you go to Settings -> System -> About phone and check your build number. (e.g September 2019 one should be PKQ1.180917.001.V10.0.13.0.PDHMIXM)
1. Install Magisk Manager
2. Open the app and press Install on the prompt (It should prompt you to install the latest version).
3. Tap on Install on the prompt and then "Patch Boot Image File".
4. Select the untouched boot.img through your File Explorer. Wait for it to do its thing.
The patched_boot.img was created and it should be located at /storage/emulated/0/Download/patched_boot.img.
UNLOCKING THE BOOTLOADER
1. Move the patched_boot.img to your PC
2. Connect the device to your computer and open a Command Prompt
3. Check that ADB works with:
Code:
adb devices
Should say:
Code:
XXXXXXXXXXXX device
where the X's are a unique ID.
4. Boot into fastboot mode with:
Code:
adb reboot bootloader
(Yes you can obviously boot into bootloader by using Volume Down+Power Button etc)
5. You should be in fastboot mode. Check that it works properly:
Code:
fastboot devices
Should say:
Code:
XXXXXXXXXXXX fastboot
The device will be wiped after the next step.
6. Now we are going to unlock the device's bootloader with:
Code:
fastboot oem unlock
7. At this point the device is unlocked. Now do:
Code:
fastboot reboot
And let the phone boot
8. After booting, go into fastboot mode again with:
Code:
adb reboot bootloader
BOOTING INTO THE PATCHED IMAGE AND INSTALLATION
You should now be in fastboot mode from the last section.
1. Boot into the patched_boot.img that you generated earlier with:
Code:
fastboot boot patched_boot.img
The phone should boot normally and shouldn't take too long. For me it was the same boot time as always.
2. Now open Magisk Manager and press Install
3. When prompted tap onto Install and then choose "Direct Install (Recommended)"
Let it do its thing and then choose Reboot.
You should now have a rooted phone with Magisk without using TWRP.
Do not relock your bootloader or your device probably won't boot because you are rooted.
PAYLOAD DUMPING
Requirements: python3, protobuf (do python -m pip install protobuf after having installed python3)
1. Download the desired OTA (full OTA needed, not incremental ones, should probably be 1GB+)
2. Download the zip of the python script on github
3. Extract the script (both .py's) and inside the folder extract the payload.bin from the OTA archive
4. Now run:
Code:
python payload_dumper.py payload.bin
Wait for it to be done and you should have all the images in the same directory. With those, you can either just use the boot.img or even create a fastboot flashable OTA with a script.
Cheers!

Thank you very much, I just got my hands on the phone and wanted to root without wiping. Unfortunately when I try to patch the boot.img the resulting image is a zip file that cannot be used.

The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).

Update: I have done it, I could not generate my own patched image, so I had to use the one in the provided post. I still opted to install magisk beta instead of the normal one and there was no problem, now I'm rooted. Thanks again.
---------- Post added at 05:22 AM ---------- Previous post was at 05:21 AM ----------
sipollo said:
The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).
Click to expand...
Click to collapse
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.
---------- Post added at 05:23 AM ---------- Previous post was at 05:22 AM ----------
sipollo said:
The only downside is that the first time the phone will go to recovery mode (stock or custom recovery) will be formatted and encrypted (data AND internal storage).
Click to expand...
Click to collapse
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.

clau1996 said:
There shouldn't be a problem, by pressing down the Volume Down key you can bypass the wipes. I did it minutes ago, successfully.
Click to expand...
Click to collapse
With vol- trick wipes are only postponed. Don't boot in recovery mode and you'll be fine. If you boot pressing power and vol+ phone will be wiped.
If you boot temporary twrp phone will be wiped.

sipollo said:
With vol- trick wipes are only postponed. Don't boot in recovery mode and you'll be fine. If you boot pressing power and vol+ phone will be wiped.
If you boot temporary twrp phone will be wiped.
Click to expand...
Click to collapse
this is correct, I learned the hard way
I honestly don't understand all this patched boot img nonsense
ffs if you want root just BOOT into custom recovery via fastboot and then flash/install the beta magisk zip 16.7 in said custom recovery, that's it
Sent from my Nexus 6 using Tapatalk

I guess I should have included that if you boot into any recovery after doing the "bypass" procedure, the device will get wiped, as mentioned by the rest of you guys.
This "guide" is only if you don't intend to ever use TWRP or something similar. Anyway, will add it to the OP, sorry if anyone got screwed up because I didn't mention it.
sgloki77 said:
this is correct, I learned the hard way
I honestly don't understand all this patched boot img nonsense
ffs if you want root just BOOT into custom recovery via fastboot and then flash/install the beta magisk zip 16.7 in said custom recovery, that's it
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
I guess if someone wants to start off with a new install it's better and faster to just boot into TWRP and flash Magisk as you just said.
Guide is mainly targetted to people who don't want to wipe for whatever reason (whether that is data or anything).

clau1996 said:
Thank you very much, I just got my hands on the phone and wanted to root without wiping. Unfortunately when I try to patch the boot.img the resulting image is a zip file that cannot be used.
Click to expand...
Click to collapse
The resulting image should actually be a .img (or a .img.tar if you choose so in the settings) ?
Maybe you didn't look in the correct directory for the image (?)
Double check, because I did this procedure twice on my device and it worked that way.
Thanks for using the guide btw!
EDIT: whoops, should have merged with the other reply..

Thanks for the guide. Is it possible to update via OTA once we have the new update monthly and repeat the same process for rooting?

fernoct said:
Thanks for the guide. Is it possible to update via OTA once we have the new update monthly and repeat the same process for rooting?
Click to expand...
Click to collapse
I suppose it should be possible but I guess I will have to test it on the next OTA we get just to be sure.

hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks

lord bim said:
hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks
Click to expand...
Click to collapse
I don't think there's a way to bypass the wipe from Mi Flash tool, at least not that I know about.

michkost858 said:
I don't think there's a way to bypass the wipe from Mi Flash tool, at least not that I know about.
Click to expand...
Click to collapse
I mean if the full ROM of July has the same problem as in May when I unlock the bootloader

lord bim said:
I mean if the full ROM of July has the same problem as in May when I unlock the bootloader
Click to expand...
Click to collapse
Oh, yes it does. By the way, just to clarify; it's not a problem, it's a safety measure which Xiaomi implemented on the May Update and on. Otherwise your data would be at risk and easy to steal.

Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368

lord bim said:
Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368
Click to expand...
Click to collapse
Yes, nothing special about it

lord bim said:
hi, I have V.9.5.10.0 and I want to flash V9.6.4.0 with Mi Flash Tool. Do I have to follow this guide to avoid losing data after unlocking the bootloader?
thanks
Click to expand...
Click to collapse
After unlocking bootloader with vol- trick, if you want i uploaded last Fastboot Rom with a modified script.
You won't lose data and your bootloader will remain unlocked.
A Backup is strongly recommended (just in case).
Use Miflash.
https://1drv.ms/u/s!AnNVEh3KeCSVj94TW6xkP6Xj-CDeRg

lord bim said:
Thanks for your help.
this patch boot it is ok?
https://forum.xda-developers.com/showpost.php?p=77137193&postcount=1368
Click to expand...
Click to collapse
ProchyGaming said:
Yes, nothing special about it
Click to expand...
Click to collapse
I would recommend generating your own if possible.
Not sure if there's a difference tbh, however I think that, that one was patched for 16.0 and not 16.7 which makes it freeze up sometimes during boot.

thanks to all the valuable inputs the op and other have given here, so conclusion in you can install magisk without wiping data by this method, but your data will be erased the next time you boot into recovery. Also, one cannot be sure about otas as ota might trigger recovery for some stuff and then the data will be wiped. The only viable option is to just backup your data, either by titanium backup after installing magisk like mentioned in the op or just manually save necessary stuff somewhere, permanently unlock, flash twrp and then flash magisk.

One question though, why do we need to update Magisk into the beta version? Now that we have 17.0 is it necessary?

[GUIDE] [ELI5] [Root] [TWRP] [Moto E5] Root and TWRP for Moto E5 Play Explained

Explain It like I'm 5 - TWRP and Root for Moto E5 Play (and other E5 variants)
Step-by-Step explanation of the Root procedure found in @CodyF86 TWRP and Root thread for the Moto E5 Play
Because there are some entry-level users out there, I wanted to break down the steps for those of us who might not have as much experience in working with phones.
12/02/18 - THREAD UPDATE!
PLEASE READ BEFORE CONTINUING
Procedure should be safe for all E5 devices.
DO NOT FLASH ANY NO-VERITY KERNELS LISTED IN XDA
Expand for details...
This guide was originally written for James specific devices.
HOWEVER.. many have asked if this will work on their specific devices, and after answering questions and doing some brief research, I am convinced that this procedure SHOULD BE safe for ALL Moto E5 devices.
BEWARE.. The TWRP port provided for this procedure is not fully ported for the E5. I have confirmed flashing zip or image files, and making/restoring backups of boot, system and data are successful with James. These basic features of TWRP will work on all E5 phones, BUT this TWRP build will cause your phone to be identified as a PERRY device when checked by ROMs or flashable zips that do assert checks on the device name or id.
Prerequisites
ADB and Fastboot installed on PC
Motorola USB Drivers installed for your device
TWRP and fstab files from E5 Play Root / Recovery thread.
Latest Magisk
DISCLAIMER
Unlocking your bootloader is not for the faint of heart. Unlocking your device and installing your own software might cause the device to stop working, disable important features and functionality, and even make the device unsafe to the point of causing you harm. Neither Motorola, nor your wireless carrier or retailer from whom you purchased the device, will be responsible for such damage, so please do not unlock or load any software unless you know what you are doing.
You have only yourself to blame. Unless you have a Developer Edition device, once you get the unlock code, your device is no longer covered by the Motorola warranty; in other words, please don't blame us if things go wrong, even if they appear unrelated to unlocking the bootloader.
The law still applies. You still need to operate your device in compliance with all applicable laws, rules and regulations prescribed by the FCC, and any other governmental agency for that matter. Your wireless carrier may prohibit unlocked devices from operating on their network.
Steps from Stock Device
1 - Unlock Bootloader
Procedure
Enable Developer Options on your Device (Settings -> About Device -> Software -> Tap Build No. until Dev. Options are enabled.
Enable USB Debugging under Developer Options.
Enable OEM Unlock under Dev Options
Follow the Motorola Bootloader Unlock Prodecure on Motorola's Customer Support Portal
2 - Flash TWRP
DISCLAIMER
This process will overwrite your recovery partition. It is wise to make a complete nandroid backup of your device prior to performing any of the steps below.
Procedure
Download Magisk zip package, TWRP 3.2.1 E5 Play and fstab.qcom files from the E5 Play Root Recovery thread.
Put these 3 files in your adb/fastboot directory on your pc
With your phone on and booted to android, connect to your PC using your USB cable.
Open Command Prompt and cd to your ADB/Fastboot directory
run "adb devices" to make sure your device is connected to adb (you will need to approve the initial connection on your device)
manually copy twrp_james.img to your phone's external sd card or
Code:
adb push twrp_james.img /sdcard/
run "adb reboot bootloader" to reboot to fastboot mode
boot directly to TWRP with
Code:
fastboot boot twrp_james.img
make a full backup and store the backup on your phone's external sd card or transfer to your PC.
in TWRP, Reboot->Reboot Bootloader
When back in fastboot mode, flash TWRP to your recovery partition.
Code:
fastboot flash recovery twrp_james.img
fastboot reboot recovery
your phone should reboot to TWRP now on your recovery partition.
3 - Disable Force-Encryption and Root device with Magisk
Procedure
while in TWRP, run the following in your ADB terminal
Code:
adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
adb push fstab.qcom /vendor/etc/fstab.qcom
from TWRP menu: Wipe-> Format Data
copy magisk zip to newly formatted data partition
Code:
adb push Magisk-v17.2.zip /sdcard/
From TWRP, Install Magisk zip
You now are rooted and have TWRP on your Recovery partition. After rebooting to Android, make sure you install the latest Magisk Manager first thing.

Great tutorial. Worked like a charm on my James.

Thanks for posting this. Ive been rooting and messing with phones for years but never really got comfortable with adb and fastboot commands and the other post makes no mention of unlocking the bootloader even though it was obvious i needed to. I considered doing it this way same way i unlocked my e4 Qualcomm but wasn't 100% sure that was what was needed until i read this. Very easy to follow guide that ensures i didn't miss anything.

AesopRock127 said:
Thanks for posting this. Ive been rooting and messing with phones for years but never really got comfortable with adb and fastboot commands and the other post makes no mention of unlocking the bootloader even though it was obvious i needed to. I considered doing it this way same way i unlocked my e4 Qualcomm but wasn't 100% sure that was what was needed until i read this. Very easy to follow guide that ensures i didn't miss anything.
Click to expand...
Click to collapse
My pleasure. Thank you very much. I'm happy to help.

Working like a charm on my Moto E5 PLAY XT1920-16
HI,
After a few attempts i've managed to root my Moto E5 PLAY XT1920-16. I did not flashed twrp_james.img (boot error) just boot directly to TWRP (fastboot boot twrp_james.img) and followed the instructions from step 3. Flashed boot logo from here to "hide" N/A, Bad Key message.

Thanks for this, as it's easy to understand and follow - especially the ADB in TWRP for FSTAB which I previously messed up and got into all sorts of horrible boot loops / errors and had to run away and hide for 36 hours as my wife threatened to chop off something if she heard me scream "B*******" one more time.
No drama this time, it just worked :laugh:

Will this work on a regular E5?

diaconu.silviu said:
HI,
After a few attempts i've managed to root my Moto E5 PLAY XT1920-16. I did not flashed twrp_james.img (boot error) just boot directly to TWRP (fastboot boot twrp_james.img) and followed the instructions from step 3. Flashed boot logo from here to "hide" N/A, Bad Key message.
Click to expand...
Click to collapse
Thanks for this! I've been trying to figure out how to hide the N/A forever on this phone

bubba1601 said:
Thanks for this, as it's easy to understand and follow - especially the ADB in TWRP for FSTAB which I previously messed up and got into all sorts of horrible boot loops / errors and had to run away and hide for 36 hours as my wife threatened to chop off something if she heard me scream "B*******" one more time.
No drama this time, it just worked :laugh:
Click to expand...
Click to collapse
Awesome lol. Thanks for your comment

Slavois said:
Will this work on a regular E5?
Click to expand...
Click to collapse
TWRP version excluded, yes, it should. First make sure you get a TWRP image that is compatible with E5 model you are working with. I wouldn't use the twrp_james.img file linked in this thread if you dont have a james device. I dont know if the regular E5 is james, nora or rhannah. You should have information related to this on your fastboot screen.
If I recall correctly, the fstab.qcom file linked in this thread, which is needed to disable encryption, should work on your phone. There was another member who used it on their E5 Plus without issue.

weakNPCdotCom said:
TWRP version excluded, yes, it should. First make sure you get a TWRP image that is compatible with E5 model you are working with. I wouldn't use the twrp_james.img file linked in this thread if you dont have a james device. I dont know if the regular E5 is james, nora or rhannah. You should have information related to this on your fastboot screen.
If I recall correctly, the fstab.qcom file linked in this thread, which is needed to disable encryption, should work on your phone. There was another member who used it on their E5 Plus without issue.
Click to expand...
Click to collapse
Also a warning about twrp.....
I'm using the XT1920-15 E5 play (PETTYL) and the alleged twrp version for that device (not available here on XDA) doesn't work on that device.
The James version works on PETTYL.
There's two or three E5 play and plus twrp versions floating around here, just a heads up for users to be cautious.....

bubba1601 said:
There's two or three E5 play and plus twrp versions floating around here, just a heads up for users to be cautious.....
Click to expand...
Click to collapse
I would love a TWRP build for this phone that supports backups for all the major partitions and not just basic system/data/cache
Would also be nice if it could wipe lock screen security.
If I knew how to port twrp I would build some

Error msg.
When I run this command I get the following message below. I used both command prompt and powershell. Powershell gives me that error message while command prompt just goes through, but it doesnt give me any confirmation. What must I do?
PS C:\Users\Lit\Desktop\Moto E5 play root> adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
Error msg:
At line:1 char:19
+ adb shell mount -o,rw /dev/block/bootdevice/by-name/vendor /vendor
+ ~
Missing argument in parameter list.
+ CategoryInfo : ParserError: ) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : MissingArgument

Im using moto e5 play for TMobile xt1921-3 and was wondering if someone can point me in the right direction for twrp installation? And the proper img file? The one I flashed, twrp_james.img, stuck for like a day but now its gone?? Wat am i doin wrong?

Swagnutz34 said:
Im using moto e5 play for TMobile xt1921-3 and was wondering if someone can point me in the right direction for twrp installation? And the proper img file? The one I flashed, twrp_james.img, stuck for like a day but now its gone?? Wat am i doin wrong?
Click to expand...
Click to collapse
If you follow these directions in the op exactly you will be fine and twrp will stick after you boot. The twrp linked here in the op is the one. I used it and I have same exact device as you, same model and all. From my experience tinkering with it you gotta decrypt for twrp to stay. Otherwise if you wanna stay encryted you just use fastboot and fastboot boot twrp.img from your computer every time you use recovery. Hope that helps.
Sent from my XT1921-3

SM210 said:
If you follow these directions in the op exactly you will be fine and twrp will stick after you boot. The twrp linked here in the op is the one. I used it and I have same exact device as you, same model and all. From my experience tinkering with it you gotta decrypt for twrp to stay. Otherwise if you wanna stay encryted you just use fastboot and fastboot boot twrp.img from your computer every time you use recovery. Hope that helps.
Click to expand...
Click to collapse
I got twrp to stick but cant back up data? N magisk flashed no problem....here are some screenshots. Im tryin to flash lineage rom n im gettin no where lol. Sorry im a noob!

Swagnutz34 said:
I got twrp to stick but cant back up data? N magisk flashed no problem....here are some screenshots. Im tryin to flash lineage rom n im gettin no where lol. Sorry im a noob!
Click to expand...
Click to collapse
As 1st post states: see my screenshot attached from the original post... Follow that exactly
then flash magisk 17.2 zip in twrp recovery and reboot and you then can see your data partition in recovery and twrp will hold perminately.
Hope that helps. Always read up alot , I always try to. As specially these days. TONS of new things to learn. Hope that helps. Cheers.
Sent from my james using XDA Labs

for some reason i can flash the hannah twrp 3.2.3 for my moto e5 plus and i can boot intp twp recovery. i made a back up and now its just stuck on the start up loop. and when i get to the adb part of this tutorial i cant push none of the files using the sideload option in twrp so i can decrypt twrp.

Failed at 'fastboot reboot recovery' with the following:
rebooting into recovery FAILED (remote: 'Unknown command')
Continued from step 3 after bring it back to TWRP as [email protected] suggested. However, did not get root. Any suggestions what to try next? The device is XT1921-2.
Thanks!

Hi! I have the xt1920-18 version and TWRP doesn't recognize touch. In case anyone else has this problem, I used the mouse with OTG and it works perfect.Hi! I have the xt1920-18 version and TWRP doesn't recognize touch. In case anyone else has this problem, I used the mouse with OTG and it works perfectly.

Moto G7 root and TWRP

This thread contains known working root and custom recovery, along with any other verified working mods for this device
Thanks to anyone who is willing to help out in advance. You are awesome
Code:
* Your warranty is now void.
*
* I am not responsible for bricked devices, dead SD cards, fires, rigged elections,
* thermonuclear war, or you getting fired because the alarms failed and you
* could not call in.
*
* Please ensure you have an advanced understanding of this device before
* flashing it! YOU are choosing to make these modifications of your own free will
THIS REQUIRES AN UNLOCKED BOOTLOADER!!! DO NOT ATTEMPT ON A LOCKED BOOTLOADER. YOU ALSO NEED APPROPRIATE DRIVERS AND ADB TOOLS. THIS GUIDE IS ONLY FOR THE MOTO G7 SERIES, DO NOT ATTEMPT ON ANY OTHER DEVICE
Also check under developer options USB debugging and OEM unlock is checked. Tap build number 7x under settings -> about phone to enable developer options. Please note that some carrier locked variants do not permit OEM unlocking and as such currently have no method to unlock the bootloader
Follow the instructions here to unlock your bootloader
Confirmed Magisk working with boot image, patched through Magisk app.
TWRP needs some work but basic functionality is up
Magisk
Download the appropriate firmware from here, making sure to match build number and variant, found under Settings -> System -> About Phone. Even if you use boot images given to you, I recommend you do this just in case something messed up
Extract the boot.img file
Copy it to the internal storage of your device
Install magisk manager app, found here and open it.
Make sure under advance setting both keep dm-verity and keep force encryption are checked, otherwise you may get stuck in a bootloop
Tap install beside "Magisk is not installed" on the first card
Tap patch boot image
Select your boot image
Once magisk creates the image, copy it to the folder that contains the adb tools
The output can be flashed via fastboot on an unlocked bootloader via
Code:
adb reboot bootloader
fastboot flash boot boot.img
After initial setup/first boot, reboot your device again. Magisk Manager stub should now show up under apps. If you have previously installed it, you'll still need to reboot after the initial boot with magisk for the app to recognize you have it
The stub will download the actual app (if necessary). Once that's installed, open it and tap yes when it asks you to set up environment. If that failed, just close the app and reopen, tapping yes on the prompt. Do that until it says setup done
We now have twrp so theoretically the magisk zip can be flashed. I personally have experienced a lot of problems with this method so I'd recommend against it, but if you want to here's how:
See below instructions to flash twrp if you haven't already
Download the latest magisk zip here and save it to your SD card if you have one
Reboot to TWRP via volume down + power, which will get you to bootloader. In bootloader, use the volume keys to scroll to recovery mode, then press power to select. I personally prefer adb via
Code:
adb reboot recovery
Type in you screen lock if prompted, then hit the check mark on keyboard when done
Tap install
Navigate to where you saved the zip and select it
Swipe to install
Follow the last two steps of the other method
TWRP
A beta version of TWRP is now available here. Credit to @Alberto97
Download the file and copy to your adb tools folder
Reboot to bootloader
Code:
adb reboot bootloader
Boot it with
Code:
fastboot boot twrp-version-build-river.img
Put the TWRP image in your external SD Card or, in case you don't have one, push it to /data with adb this way:
Code:
adb push twrp-version-build-river.img
Tap Advanced -> Install Recovery Ramdisk -> Navigate to /data or /external_sd and select TWRP -> Swipe to Install
Select Fix Recovery Bootloop from Advanced tab, and swipe to fix
In case of emergency (eg, soft brick), follow these instructions to get back to stock before reattempting. They may say for updating, but they work to get back to stock

I Have two G7 rooted with Magisk indeed

if you look at the full firmware there seems to be no stock recovery included in it. we definitely need twrp to even flash a custom gsi rom. id help but i have no time or idea how to build twrp.

mingkee said:
I Have two G7 rooted with Magisk indeed
Click to expand...
Click to collapse
Can you please provide evidence? A screenshot of the main page of Magisk app and a screenshot of root checker will do

fix-this! said:
if you look at the full firmware there seems to be no stock recovery included in it. we definitely need twrp to even flash a custom gsi rom. id help but i have no time or idea how to build twrp.
Click to expand...
Click to collapse
I know how, but I'd need the stock recovery

clcombs262 said:
Can you please provide evidence? A screenshot of the main page of Magisk app and a screenshot of root checker will do
Click to expand...
Click to collapse
OK
You asked for it

clcombs262 said:
I know how, but I'd need the stock recovery
Click to expand...
Click to collapse
There's a possibility recovery is merged into boot.img
I found patched boot is significantly smaller than original
I will look more into original boot.img to find required parameters for boardconfig.mk, but probably you can only boot with TWRP not flashing it.

mingkee said:
OK
You asked for it
Click to expand...
Click to collapse
Can you share step by step how you did it?
Like patch boot img with magisk, flash magisk zip, use TWRP, etc?

mingkee said:
There's a possibility recovery is merged into boot.img
I found patched boot is significantly smaller than original
I will look more into original boot.img to find required parameters for boardconfig.mk, but probably you can only boot with TWRP not flashing it.
Click to expand...
Click to collapse
Thanks for the effort!

clcombs262 said:
Can you share step by step how you did it?
Like patch boot img with magisk, flash magisk zip, use TWRP, etc?
Click to expand...
Click to collapse
He described it in
https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084/page4
I'm trying to gather enough courage to root my G7. Scary. But I need it for things like titanium backup, AfWall, etc.
Besides I believe twrp is not yet available. Need it for the nandroid backup to restore if things go bad.

maybeme2 said:
He described it in
https://forum.xda-developers.com/moto-g7/how-to/root-g7-magisk-t3907084/page4
I'm trying to gather enough courage to root my G7. Scary. But I need it for things like titanium backup, AfWall, etc.
Besides I believe twrp is not yet available. Need it for the nandroid backup to restore if things go bad.
Click to expand...
Click to collapse
That's a generic set of instructions, with no links or evidence provided that it works
I could literally use those instructions to root any device with magisk. (Excluding device that can't unlock bootloader and such)
I'm looking for confirmation, instructions tailored to our device, links to appropriate files, what's working on what model/firmware/variant, etc
Also we should figure out TWRP. Very handy in rooting and unrooting

clcombs262 said:
That's a generic set of instructions, with no links or evidence provided that it works
I could literally use those instructions to root any device with magisk. (Excluding device that can't unlock bootloader and such)
I'm looking for confirmation, instructions tailored to our device, links to appropriate files, what's working on what model/firmware/variant, etc
Also we should figure out TWRP. Very handy in rooting and unrooting
Click to expand...
Click to collapse
I have my Moto G7 xt1962-1 US Retail rooted with magisk. It works. You can use my patched boot image if your're running the same on ppo29.114-16-5 and don't want to do it yourself. Flash with:
Code:
fastboot flash boot patched_boot.img

mingkee said:
There's a possibility recovery is merged into boot.img
I found patched boot is significantly smaller than original
I will look more into original boot.img to find required parameters for boardconfig.mk, but probably you can only boot with TWRP not flashing it.
Click to expand...
Click to collapse
Of course its merged. I did not realize this, but it is a arm64 A/B partition device. that means that recovery is merged into boot

clcombs262 said:
That's a generic set of instructions, with no links or evidence provided that it works
I could literally use those instructions to root any device with magisk. (Excluding device that can't unlock bootloader and such)
I'm looking for confirmation, instructions tailored to our device, links to appropriate files, what's working on what model/firmware/variant, etc
Also we should figure out TWRP. Very handy in rooting and unrooting
Click to expand...
Click to collapse
I can work on providing the steps I take with river_amz later today and document each step. Will edit this reply when I do so.

Ni
clcombs262 said:
That's a generic set of instructions, with no links or evidence provided that it works
I could literally use those instructions to root any device with magisk. (Excluding device that can't unlock bootloader and such)
I'm looking for confirmation, instructions tailored to our device, links to appropriate files, what's working on what model/firmware/variant, etc
Also we should figure out TWRP. Very handy in rooting and unrooting
Click to expand...
Click to collapse
cclombs, you are correct. ANY device that can be bootloader unlocked can be rooted with Magisk in this way. Magisk works by inserting itself into the boot image so you just need access to the boot image. However, this method requires you to have access to the Stock ROM. Luckily, Moto seems to be very good about supplying this.
EDIT: Section removed. Access to read boot.img requires root. I was wrong!
And yes, I have successfully achieved root using the above methods. I used it on my Moto G7 Power, and on my Nexus E4 plus before TWRP was available.

zerogun said:
cclombs, you are correct. ANY device that can be bootloader unlocked can be rooted with Magisk in this way. Magisk works by inserting itself into the bootloader so you just need access to the bootloader image. However, this method requires you to have access to the Stock ROM. Luckily, Moto seems to be very good about supplying this.
Theoretically, even if you did not have access to the stock ROM, you can enable ADB debug in Developer Options, go into an ADB shell, and then do this:
dd if=/dev/block/[boot location] of=/data/downloads/boot.img
This would do a full image backup of your boot.img and put into your downloads folder. And yes, I have successfully achieved root using the above methods. I used it on my Moto G7 Power, and on my Nexus E4 plus before TWRP was available.
Click to expand...
Click to collapse
I thought dd required root?
And I think you mean boot image, not bootloader. Bootloader is very different, and should NEVER be modified

You are correct. I meant to say boot image. I'll edit to not confuse people.
I'll have to check later on if dd requires root. I thought it only needed adb debig access.

Thank you zerogun. I'm trying to learn.
zerogun said:
However, this method requires you to have access to the Stock ROM. Luckily, Moto seems to be very good about supplying this.
Click to expand...
Click to collapse
Where do they supply these stock ROMs?
zerogun said:
Theoretically, even if you did not have access to the stock ROM, you can enable ADB debug in Developer Options, go into an ADB shell, and then do this:
dd if=/dev/block/[boot location] of=/data/downloads/boot.img
This would do a full image backup of your boot.img and put into your downloads folder. And yes, I have successfully achieved root using the above methods. I used it on my Moto G7 Power, and on my Nexus E4 plus before TWRP was available.
Click to expand...
Click to collapse
When you 'go into an adb shell' do you mean use adb from a connected PC or is there an adb shell app on the phone itself?

Anybody interested in partially working TWRP? My plan was to release it once fully working but I'm stuck on decryption since days (I can't understand what keymaster 4 is still missing since it wants to upgrade the key) and I might change idea.
With broken decryption you can't use your internal storage but you will be still able to flash things from sdcard or usb otg.

Alberto97 said:
Anybody interested in partially working TWRP? My plan was to release it once fully working but I'm stuck on decryption since days (I can't understand what keymaster 4 is still missing since it wants to upgrade the key) and I might change idea.
With broken decryption you can't use your internal storage but you will be still able to flash things from sdcard or usb otg.
Click to expand...
Click to collapse
You can wipe with TWRP to remove encryption once, but you have to reboot in TWRP

How To Guide Root Edge 2021 with Magisk

I finally did it last weekend. It's pretty straightforward and it's no difference from other Moto phones I rooted.
Definitely, bootloader MUST be unlocked. A new purchased phone must wait 96 hours to have OEM unlock toggled.
You should have Lenovo RSA installed which also has needed driver installed. Get the latest ROM from RSA and let it run rescue (phone will be wiped, but bootloader unlock wiped the phone anyway). Doing this in order to grab boot.img from C:\Program Data\RSA\Download\Romfiles\.
You will lose Widevine L1 after bootloader unlocked. Stop if it matters to you.
Are you ready? Let's do it
1. Unlock the bootloader if you didn't do it. The way to get "oem get_unlock_data" is to use mark on command window and copy 5 lines of code and paste on notepad, and make it into one line. Submit to https://motorola-global-portal.custhelp.com/app/standalone/bootloader/unlock-your-device-a
You should get the code in few minutes over email. Then use this below:
Code:
fastboot oem unlock (code received from email)
(your phone will be wiped]
To enter bootloader. Turn the phone off (make sure you make a backup and copied files to host computer) then press and hold volume down and power buttons.
2. Patch boot.img. After bootloader unlocked, you can stay on bootloader screen and run RSA rescue. Doing this to make your phone up to date as well as getting boot.img. Your phone will be wiped again during the process.
Now you have to do initial setup and install Magisk. Copy the boot.img to the phone and patch it, and copy the patched_boot.img back to host computer.
You can get USNF, fox Magisk Module Manager, Adaway, and other modules if you want.
3. Post root process. You should re-enable USB debug and allow the host computer.
Enter fastbootd
Code:
adb reboot fastboot
or
Code:
fastboot reboot fastboot
Flash patched_boot
Code:
fastboot flash boot
Press space once to make a space, drag and drop patched_boot into command window, and press enter.
Since 24.1, Magisk has different approach to hide/deny.
Enable Zygisk, enforce deny list, install USNF as module (don't worry about GMS because USNF takes care of it).
Put any app can detect root on deny list and reboot everytime you updated the list
Happy rooting

This is my first time rooting an android phone, so thank you. Perhaps I might suggest you add some more details to the "patch boot.img" section, as it took me some extra looking about before I figured out what I was doing.
Thankfully it's pretty simple, I just had to download the Magisk apk from its official github repo onto the phone (post step 1), transfer over the downloaded "boot.img" that the lenovo RSA app downloads during its rescue process (it tells you were it downloads it in the app), over to the phone (usb file transfer), patch "boot.img" on the phone using the Magisk app (install > pick file > done!), transfer back over the newly patched image (stored in downloads) to pc, and then use the above instructions to `fastboot flash boot /path/to/your_patched_boot.img` when the phone is once again put into fastboot mode.
Okay maybe that isn't super simply explained, but I wanted to write it down so others might benefit.
Thank you again, I now have my phone rooted, and will be looking into various things I can do with it, such as degoogling, TWRP (if it's even available for this phone), etc.
---
As far as I know, there is no TWRP yet pre-made for this phone. Unless I'm mistaken, I'd have to manually compile TWRP for my phone? (Not exactly sure how to go about that.)
Also, any tips for a newbie like me?

Can anyone confirm if using the magisk patched boot.img method works tho? Because unless you plan on actually using a custom rom or GSI you don't need twrp anymore for magisk, at least that's my experience with the moto Edge(2020) racer retus. Edit: I'ma dummy, literally the post above this answered my question lmao, I'm currently using a work phone from Samsung because I got my 2020 moto edge hardbricked in edl mode and typical Samsung didn't load everything lmao

ninjakira said:
Can anyone confirm if using the magisk patched boot.img method works tho? Because unless you plan on actually using a custom rom or GSI you don't need twrp anymore for magisk, at least that's my experience with the moto Edge(2020) racer retus. Edit: I'ma dummy, literally the post above this answered my question lmao, I'm currently using a work phone from Samsung because I got my 2020 moto edge hardbricked in edl mode and typical Samsung didn't load everything lmao
Click to expand...
Click to collapse
Yes, this is how I did mine

Fastboot issues when rooting Moto G Pure

Device is a Moto G Pure (codename Ellis), I've found little to no support for this device on the Internet, and a friendly redditor informed me due to the nature of the processor's manufacturers (MediaTek), there never will be much support for this model of device. I have managed to unlock the bootloader, and I'm all ready to go with drivers and fastboot and ADB, and I also have a twrp recovery image. My issue is I'm unsure if this is the correct TWRP img as I downloaded one for a similar Moto model (Moto G Stylus 2020, TWRP 3.5.0-0) and fastboot keeps throwing errors when I try to flash or boot this image. First error was 'command is not support' as I was using flashboot boot boot.img, did some research and instead tried flashboot flash boot boot.img which wasn't liked either, threw the error 'image size exceeds file limit'. I changed active partition from a to b and tried both commands, both of which presented the same issue. I even tried compressing the file down to 35mb and it still threw a fit. The TWRP file is only 48mb, what do I do? Further researching the issue is not bringing me much luck

there is no TWRP for Moto G Pure (yet) don't do stupid things

aIecxs said:
there is no TWRP for Moto G Pure (yet) don't do stupid things
Click to expand...
Click to collapse
So what should I do to start the rooting process? Do I use a different root program or… wait for support?? I was going to flash LOS as my custom rom too, I guess they don’t support moto g pure either then considering I downloaded a generic moto rom

MisterMilo said:
So what should I do to start the rooting process? Do I use a different root program or… wait for support?? I was going to flash LOS as my custom rom too, I guess they don’t support moto g pure either then considering I downloaded a generic moto rom
Click to expand...
Click to collapse
The stock rim is available at lollinet. I actually have a copy of it and have a magisk patched boot img. I think where your reaching the error is ( and I'm very new so feel free to correct me) the fastboot command. I think it's an a b partition. So it would be fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
MisterMilo said:
So what should I do to start the rooting process? Do I use a different root program or… wait for support?? I was going to flash LOS as my custom rom too, I guess they don’t support moto g pure either then considering I downloaded a generic moto rom
Click to expand...
Click to collapse

I rooted mine through magisk by just boot image didn't disable dm verity or vb meta I do have root but you can't flash twrp from any other moto g because the moto g pure has a mediatek Helios g25 chip (I think,definitely mediatek tho)and all the others have quallcom snapdragon chips that's why you can't flash twrp in fastboot mode it's crazy no one's compiled twrp yet for this device seeing how easy it is to root. If you need help rooting yours lmk.

bayjones742 said:
I rooted mine through magisk by just boot image didn't disable dm verity or vb meta I do have root but you can't flash twrp from any other moto g because the moto g pure has a mediatek Helios g25 chip (I think,definitely mediatek tho)and all the others have quallcom snapdragon chips that's why you can't flash twrp in fastboot mode it's crazy no one's compiled twrp yet for this device seeing how easy it is to root. If you need help rooting yours lmk.
Click to expand...
Click to collapse
I Wanna Root Mine, Can You Teach Me How???

ROBOOTO said:
I Wanna Root Mine, Can You Teach Me How???
Click to expand...
Click to collapse
Easy all you gotta do is download your rom/firmware you can easily do this through the Lenovo rescue tool once you download your rom/firmware just extract into a folder somewhere you can easily access oh that rescue tool will download the firmware into crogramData\RSA\Download\RomFiles I think even though it says it's in downloads folder at first I couldn't find it for like an hour but anyways once you find the rom just extract it into a folder somewhere you can easily access & take the boot.img and send it or a copy of it into your phone's internal storage after you do that just download magisk 25.2 you know the latest one from johnwu's GitHub page and install that on your phone and you know how the rest goes just go to install magisk select img to patch choose the boot.img you transferred onto your phone let magisk do it's thing once it's done you have to transfer it back into the rom files you extracted remember to rename it back to boot.img because magisk names it something else but once you put it back in it's folder with the rest of the roms files I can't remember if I zipped em back up or not but anyways take that whole file back to the folder where the rescue tool downloaded it CrogramData\RSA\Download\RomFile and just go and adb reboot your phone into bootloader mode and let the rescue tool flash your moto g pure but with the patched boot image and hahahahaha you done oh but you have to have an unlocked bootloader otherwise you can't flash ... boi! Oh btw you'll have root but I can't uninstall system apps can't mount mount system to rw and as far as I know there's no TWRP but use fox's magisk module manager and flash bootloop protector it save my butt couple times already don't flash Sony Bravia engine will cause bootloop idk if I could compile TWRP I would almost 10 years I been doing this ... and still haven't learned to do that...lol
{Mod edit: Inappropriate language iaw. rule no. 2 removed. Oswald Boelcke}

Hi I'm feeling your pain from not having rw with your root. Have you checked out lebigmac's make sysRW script? I had to do it to get RW on my Moto G Stylus 5G cuz Android 11. Looks like I'll have to do it again for this model. Any luck on getting TWRP?