Database Develop

X98 Plus II - TWRP + ROOT v1.2

Hi, with the help of kalijo, I have made an archive to install TWRP and root your X98 Plus II model C2D4.
Reported to also works on C2D6 and C2E3.
Use at your own risk.
You will need an USB mouse to navigate in TWRP.
Instructions are in the archive.
With v1.2, I've added instructions to save the original boot and recovery images, but this will only works with new install, not upgrade.
Download link
MD5: 8634eb14ed5add0c573649aba383daa7.
Version 1.2:
- Added commands to backup boot and recovery images
- Updated SuperSU to v2.79
Version 1.1:
- Updated SuperSU to v2.78
- Added some infos in this file
Version 1.0:
- Initial release

Version 1.1:
Updated SuperSU to v2.78

Thanks! I haven't had a chance to use it yet, but I'm the most recent download.

Here is the new flashable SuperSU:
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.78-201609011115.zip
You may have to install SuperSU on GooglePlay after.

Is this for the c2e3?
Sent from my SM-G935F using XDA-Developers mobile app

CountZer0 said:
Is this for the c2e3?
Sent from my SM-G935F using XDA-Developers mobile app
Click to expand...
Click to collapse
It might or might not work.
I have a C2D4, what is the specs of C2E3?

It's android only. 2gb Ram.
Skickat från min SM-G935F via Tapatalk

problem with superSU binaries
I have install this SuperSU following instructions. All was OK severals days and singe few days super SU ask for new binaries and no way to install thèse binaires.
What is the solution please ?
I precise that my C2D4 is rooted with your method.
Thanks a lot
Sée you

Good afternoon .. please can someone help me. today trying to get into the Android tablet hangs on teclast screen, I can not even get into recovery. I state that the tablet is original, someone can help me figure out how to fix it? thank you

miloucrabe said:
I have install this SuperSU following instructions. All was OK severals days and singe few days super SU ask for new binaries and no way to install thèse binaires.
What is the solution please ?
I precise that my C2D4 is rooted with your method.
Thanks a lot
Sée you
Click to expand...
Click to collapse
See post #4
carlo201983 said:
Good afternoon .. please can someone help me. today trying to get into the Android tablet hangs on teclast screen, I can not even get into recovery. I state that the tablet is original, someone can help me figure out how to fix it? thank you
Click to expand...
Click to collapse
What have you done before ? more infos needed.

Version 1.1:
Updated SuperSU to v2.78

Did anyone have any success so for on C2E3 (2GB Android only model)?
Or, maybe to the DEVS - as this is for the dual boot version, is there any reason it would definitely not work on the Android only model? Willing to take some amount of risk, but dont want to brick my device...

It should work. Worst case, you have to reinstall Android, so make sure you have the files before trying.
To obtain the files, type your model number here (you can use Chrome for auto translation):
http://www.teclast.com/tools/pad/pad.php?t=p
That will lead you here:
http://pan.baidu.com/s/1nvpQOGx
(Use Jdownloader to download the file).
The dl speed is rather slow, I'm trying to download right now, will update the post with a mirror soon.
Update: here is a mega mirror:
https://mega.nz/#!sFBCDJiJ!7fLWNkmdg0yUH1IgPlerDo_Og0Vw5Ypgnh4rf0ItnVI
Please report your findings, so I can update the first post.

Well bad news, I tried to flash according to the instructions but the whole thing stopped working/responding during the "fastboot boot loader.efi" stage. I tried restarting the process using dnx mode, however in the end I received "corrupt bzimage kernel" error and device would not boot. I then installed phone flash tool and tried restoring the default images, the process completed OK however when booting teclast logo stays on screen for around 10 minutes, then I get this error: "Bootloader error code 06. Multiple crash events have been reported."
I tried flashing both the "blank" and "recovery" profiles, flash completes OK but tablet is unsable
Any ideas how to solve this, or did I just brick it?
Edit: Screenshot
http://i.imgur.com/OmqhH1E.jpg

In my attempts to install xposed module, I destroyed my both boot and system.
Since you have the problems with bootloader, get android files for your tablet (C2D3) unpack and find the boot.img and system.img
First step flahs origin boot.img
fastboot flash boot boot.img
Then try fastboot boot loader.efi
If your tablet is stuck in a bootloop, then also flash the original system
fastboot flash system system.img
Hope it helps
BTW, did somebody succeeded in installing xposed on our tablet?(C2D4)

I got a working factory image up and running, turns out the issue was some kind of driver/USB problem, I reinstalled everything from scratch on a fresh PC and the recovery flash worked flawlessly the first time I ran it. I will try root procedure again on the other machine later today or tomorrow.

Hooray, I got it working on my c2e3 model using the files and instructions in the original post.
However I have to say this was one of the scarier rooting procedures I went through, even using the cleanly installed PC to flash I had to do it multiple times and kept getting various flashing errors, bootloops, TWRP exiting immediately upon launch etc.. But of course this could just be some kind of HW issue with my tablet, would not suprise me at this price.
Thank you all for your support! Now if we could only get Nougat on this baby...

@maxmax0 thanks for the feedback. @veaceslav No wonder you had issues, Xposed for X86-64 don't exist ! which one have you tried ?

@mooms I tried the normal version, which gave me a bootloop and then I tried the magisk version. Actually the magisk version is flashed, but it doesn't show..

You don't get the point, normal or Magisk version, they are not designed for x86-64, only ARM, ARM64, and X86.

I got TWRP and root on magisk here's how.

I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.

hey man, i'm wodering which version of magisk did you choose for oneplus 5?

ihead said:
hey man, i'm wodering which version of magisk did you choose for oneplus 5?
Click to expand...
Click to collapse
I recommend using the latest beta (v13)
---------- Post added at 07:22 AM ---------- Previous post was at 07:21 AM ----------
OcazPrime said:
I have ABSOLUTELY no clue why this works, BUT. Giving credit where credit is due and also a discovery of my own.
@3DSammy listed 3 different ways to get TWRP on the 5. One of them was VERY VERY CLOSE. They suggested a seperate usb port which was close. What I did was i tried to install TWRP on my surface pro 3 where i originally unlocked my bootloader, but for some reason it refused to let me add TWRP on top. So I grabbed a secondary PC and tried every single USB port on it since the Surface pro 3 only has 1 usb. None of them worked. Tried restarting the pc. Nothing. Tried updating fastboot drivers and uninstalling and reinstalling fastboot drivers. STILL NOTHING
At this point I just got really pissed and force shut my laptop down by holding the power button. Tried it again on my surface to no avail. But once i went back to my other computer i forced down it worked for some reason.... O,o really spooky. So i guess if you want twrp then force shut down a windows PC and try again after it boots. Its just how i got it to work i REALLY hope this works for others because i was steamin. I got my 3t rooted in 2 seconds but this thing. MAAAAN a whole afternoon wasted on such an odd solution. I think it has something to do with the usb ports losing all power then resetting once they receive power again.
Take all this with a grain of salt, i dont know if this will work for you but lots of folks seem to be having issues with getting TWRP running.
Also yes, magisk does work normally and passes safetynet.
Click to expand...
Click to collapse
Did you decrypt before installing Magisk?

Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%

OcazPrime said:
Im using beta 13 and i dont know anything about the decryption so im guessing no im not. But i think i know wjat you mean. When i went into twrp the first time it asked for my pattern. So i drew that and it worked perfectly. I think maybe that decrypted it. Twrp and magisk work 100%
Click to expand...
Click to collapse
I just asked because it seems that Magisk can't work if your device is decrypted

Didn't know that. But, no it's working perfectly fine. I used the test twrp build on the stable twrp 3.1.1 thread. Everything went great, no reason to flash anything else. Stock is king.

i have tried to used magisk v12 and it didn't work perfectly, specificialy 3C System Tuner doesn't get the root permission correctly then i have to use supersu 2.8.2
so if you want to root you OP5 , magisk v13 or supersu is recommended

If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?

geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
You won't be able to update OTA because your stock recovery is gone. You'll need to download the full ROM and flash it in TWRP every time an update comes. You can uninstall SuperSU and put Magisk v13. I currently have it, works perfect and safety net passes.

geoff5093 said:
If I'm already rooted with SuperSU, would it be pretty easy to unroot and then root using the latest beta of Magisk?
It looks like this modified the boot image, would this cause problem when taking updates or would we simply just need to reflash Magisk after?
Click to expand...
Click to collapse
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.

ArkAngel06 said:
If you do the OTA through the official update method in the settings, it will say that you have a rooted device and the entire package will need to be flashed. Then TWRP will flash it and the phone will update correctly. However, you lose root, as well as TWRP. So then you have to fastboot flash recovery and then flash Magisk to get back to where you were.
I did it last night.
Click to expand...
Click to collapse
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.

Eric214 said:
Once you flash the full zip, flash magisk BEFORE you got into the phone, you will keep root and that also keeps the stock recovery from overwriting TWRP. So you keep root and TWRP. After flashing full zip.
This is for future reference so you do go through that again.
Click to expand...
Click to collapse
Hmm, I can't remember if it auto rebooted or not now, but thanks for the tip.

Accidentally put my US model Huawei Mate 10 Pro into a bootloop - Could use some help

Hello,
If anyone could help me out it would be greatly appreciated. I have a US model BLA-A09 Mate 10 Pro.
I am definitely somewhat new to this. My Mate 10 is now in a boot loop. It gets to the EMUI recovery, but when attempting to download the recovery package from my wifi it fails and goes no further stating something like "cannot get package info".
I successfully unlocked my phone's bootloader, and succesfully rooted it, and I even got the latest TWRP installed on the phone. What I was trying to do however, was follow this thread https://forum.xda-developers.com/ho...agisk-root-honor-view-10-mate-10-pro-t3749280.
I was trying to use that thread to get magisk installed but in doing so I went into TWRP and flashed a file called "BKL-L09_ramdisk.img" when my phone is actually BLK-A09.
Now, I have no access to TWRP as far as I can tell, and the EMUI recovery fails as mentioned before. I can only get into fastboot now and I dont know what to do to get the phone working again. Do I need to flash the stock image of my phone or is it possible I messed it up more than that?
Edit: also here is everything I could get from fastboot about the device.
https://ibb.co/dtQ8Rc
Thank you for the help

Ltsmba said:
Hello,
If anyone could help me out it would be greatly appreciated. I have a US model BLA-A09 Mate 10 Pro.
I am definitely somewhat new to this. My Mate 10 is now in a boot loop. It gets to the EMUI recovery, but when attempting to download the recovery package from my wifi it fails and goes no further stating something like "cannot get package info".
I successfully unlocked my phone's bootloader, and succesfully rooted it, and I even got the latest TWRP installed on the phone. What I was trying to do however, was follow this thread https://forum.xda-developers.com/ho...gisk-root-honor-view-10-mate-10-pro-t3749280.
I was trying to use that thread to get magisk installed but in doing so I went into TWRP and flashed a file called "BKL-L09_ramdisk.img" when my phone is actually BLK-A09.
Now, I have no access to TWRP as far as I can tell, and the EMUI recovery fails as mentioned before. I can only get into fastboot now and I dont know what to do to get the phone working again. Do I need to flash the stock image of my phone or is it possible I messed it up more than that?
Edit: also here is everything I could get from fastboot about the device.
https://ibb.co/dtQ8Rc
Thank you for the help
Click to expand...
Click to collapse
Power down your device. Vol+ and Power should bring you to twrp

Ltsmba said:
Hello,
If anyone could help me out it would be greatly appreciated. I have a US model BLA-A09 Mate 10 Pro.
I am definitely somewhat new to this. My Mate 10 is now in a boot loop. It gets to the EMUI recovery, but when attempting to download the recovery package from my wifi it fails and goes no further stating something like "cannot get package info".
I successfully unlocked my phone's bootloader, and succesfully rooted it, and I even got the latest TWRP installed on the phone. What I was trying to do however, was follow this thread https://forum.xda-developers.com/ho...gisk-root-honor-view-10-mate-10-pro-t3749280.
I was trying to use that thread to get magisk installed but in doing so I went into TWRP and flashed a file called "BKL-L09_ramdisk.img" when my phone is actually BLK-A09.
Now, I have no access to TWRP as far as I can tell, and the EMUI recovery fails as mentioned before. I can only get into fastboot now and I dont know what to do to get the phone working again. Do I need to flash the stock image of my phone or is it possible I messed it up more than that?
Edit: also here is everything I could get from fastboot about the device.
https://ibb.co/dtQ8Rc
Thank you for the help
Click to expand...
Click to collapse
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-bla-a09-c567-usa-t3775258
-Download UPDATE.zip at the bottom of OP
-Unzip
-Flash in fastboot

253simon said:
https://forum.xda-developers.com/mate-10/development/huawei-mate-10-pro-bla-a09-c567-usa-t3775258
-Download UPDATE.zip at the bottom of OP
-Unzip
-Flash in fastboot
Click to expand...
Click to collapse
I agree, this saved my device yesterday. I would download the already extracted zip at the bottom of that post (in OP). Flash the SYSTEM.img using fastboot. Then try rebooting. If it still boot loops I suggest you also flash the KERNEL and the RECOVERY_RAMDISK

When I tried to flash the system.img in fastboot it wouldn't work I can flash other things but it says unknown partition

solved! Bricked/ wiped my P9

Hi.
A while ago I installed lineage 14 on my p9 because my son who uses the phone did want to have an experience a little closer to aosp.
Today he wanted to go back to stock emui. I thought I use the dload method. But I couldn't enter the recovery. Every time I ended up back at twrp.
Then I installed magic rainbow 4. The installation went OK but not all apps where available. Camera etc not installed.
Again I tried to use de dload method but still the same issue.
The I tried to reinstall lineage 14. Because in magic rainbow I couldn't enter the the developers option to activate oem unlock or USB debugging.
I thought that the problem for dload was an frp lock. In bootloader there is everything unlocked. But I wanted to check it.
After reinstall of lineage I wanted to reboot but I always ended up in TWRP....
I seems that there wasn't a system installed?
Then I found a tutorial that said to wipe all partitions and manually flash boot.img and system.img
But the flashing failed of both img.
So now I have a phone with all wiped....
Anyone an idea about this?

curtricias said:
Hi.
A while ago I installed lineage 14 on my p9 because my son who uses the phone did want to have an experience a little closer to aosp.
Today he wanted to go back to stock emui. I thought I use the dload method. But I couldn't enter the recovery. Every time I ended up back at twrp.
Then I installed magic rainbow 4. The installation went OK but not all apps where available. Camera etc not installed.
Again I tried to use de dload method but still the same issue.
The I tried to reinstall lineage 14. Because in magic rainbow I couldn't enter the the developers option to activate oem unlock or USB debugging.
I thought that the problem for dload was an frp lock. In bootloader there is everything unlocked. But I wanted to check it.
After reinstall of lineage I wanted to reboot but I always ended up in TWRP....
I seems that there wasn't a system installed?
Then I found a tutorial that said to wipe all partitions and manually flash boot.img and system.img
But the flashing failed of both img.
So now I have a phone with all wiped....
Anyone an idea about this?
Click to expand...
Click to collapse
If you were installing MR v4, didn't you read also the OP post #3 about HWOTA method for going back to stock from custom Nougat ROMs
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3

zgfg said:
If you were installing MR v4, didn't you read also the OP post #3 with HWOTA method for going back to stock from custom Nougat ROMs
https://forum.xda-developers.com/showpost.php?p=75787156&postcount=3
Click to expand...
Click to collapse
Forgot to mention. Yes. I tried that but software install failed.

curtricias said:
Forgot to mention. Yes. I tried that but software install failed.
Click to expand...
Click to collapse
You had to use the proper TWRP (from MR v4 thread) and flash by HWOTA the same stock you were before going to custom.
You can try HWOTA7
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
or even HuRUpdater
https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/

zgfg said:
You had to use the proper TWRP (from MR v4 thread) and flash by HWOTA the same stock you were before going to custom.
You can try HWOTA7
https://forum.xda-developers.com/p9/development/rebrand-update-tool-hwota7-p9-eva-t3820849
Already tried this to. Script ended with more than one device emulator.
or even HuRUpdater
https://forum.xda-developers.com/ho...lash-official-firmware-recovery-t3769279/amp/
Click to expand...
Click to collapse
And tried this also. Software installation failed.

I tried to install magic rainbow 4 again and it worked!
First I flashed TWRP from the MR4 topic.
But...
still various apps are missing. When I want to enter developer settings I automatically go back to home screen.
What can I do from there.
@Tecalote I'm gonna quote you here. Maybe you have an idea?

FYI
I managed to solve the problem!
Started over again.
In TWRP full wiped.
Tried HuRUpdater again. Flashed successfully the latest stock EMUi (C432-B505).
Factory reset in stock recovery.
Complete setup.
Rooted with latest Magisk (patched boot.img)

Trouble rooting my g6

I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.

jmalmberg said:
I'm coming to the g6 from an older Samsung. I figured that rooting this one would be just as simple, but was I ever wrong. I've gone through the guides available here, as well as guides on other sites, but no joy. I've probably restored my phone to the original system now 5 or 6 times. I'm hoping that someone can point me in the correct direction here.
The last couple of times I tried, here's what I did and what went wrong. I found a guide over at https://www.androidinfotech.com/root-moto-g6-and-g6-plus-pie/ that was fairly straight forward.
The first time I followed the instructions, booting to twrp failed but I figured that was because it never included flashing twrp to the phone. So I flashed it and used fastboot to boot the phone to the image. I then wiped the phone, flashed magisk and then did the same thing with no-verity-opt and rebooted.
On the reboot, the phone cycled through a couple of attempts and then was successful on the third try. But some things were broken. The battery indicator said I had 0% charge, and the phone refused to connect to wi fi. It also didn't recognize my network. And best of all, I've never achieved root. When I boot back into the bootloader, it comes up with the standard motorola file; not twrp.
Just FYI, I'm running pie.
Can anyone point me in the correct direction here? any help will be very much appreciated.
Click to expand...
Click to collapse
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?

kc6wke said:
Need a bit more info
What model G6 ? Software channel?
What build number of Pie are you trying to root?
You say "restored my phone to the original system now 5 or 6 times" what version and build number is that and how are you restoring it?
Click to expand...
Click to collapse
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.

jmalmberg said:
Model is xt1925-6
Android version is ALI_RETAIL_9.0_PPS29.118-11-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip.
I'm restoring it using Minimal ADB and Fastboot, and flashing the files over.
A couple of other things I should probably say too.
1. The phone was originally running Oreo. About two weeks ago, Motorola pushed out PIE to me and I installed it. That caused a tone of problems... the biggest one was that you couldn't hear the phone anymore. Couldn't hear callers, ringing, notifications, etc... It might has well have been a doorstop. I tried to roll the phone back to Oreo doing a factory reset, but that didn't work either. Wiped out my IMEI and carrier. So I did a little research and found out that some other people had the same issue. They couldn't roll back so I figured I was stuck with Pie.
2. At that point, I unlocked the bootloader and downloaded the version above from a link in one of the forums and flashed it to the phone. For whatever reason, that cured the IMEI, carrier and sound issues. Since I've come this far and the phone doesn't have anything on it, I'd like to root what I have and get some of the capability that I had on the Samsung.
Thanks for your assistance on this.
Click to expand...
Click to collapse
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting

kc6wke said:
PPS29.118-11-1 has a lot of issues. downgrading doesn't seem possible. I thought we had it solved today but ran into the same issue with calls
Follow This thread for rooting
Click to expand...
Click to collapse
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.

jmalmberg said:
Oh, interesting, That's the thread I started with but couldn't get to work for me. That's when I went out and found the guide that I linked to in my original posting. Let me walk through the steps I used here to see if you can tell me where I went wrong.
1. Unlocked my bootloader.
2. Installed Minimal ADB & Fastboot.
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
4. Flashed TWRP to the phone and used Fastboot to load it.
5. Wiped the phone. Used advanced wipe and deleted the cache and data then rebooted to TWRP and did it again. At this point, I installed the SD card.
6. Rebooted the phone into TWRP and then selected install for DM Verity and again for Magisk.
7. Reboot and check for root using Rootcheck. I'm being told that I don't have root access.
What am I missing here?
Again, thank you for the assistance.
Click to expand...
Click to collapse
You need to format data (type yes) In twrp

kc6wke said:
You need to format data (type yes) In twrp
Click to expand...
Click to collapse
That worked! Thank you very much!!! I really appreciate it!!!!

jmalmberg said:
3. Placed TWRP, in the Minimal ADB director on my PC and loaded Magisk, DM Verity, Magisk Manager apk to the SD card on my phone. (NOTE: the SD card isn't installed in the phone yet. I'll do that after doing the wipe. Just putting the software on it.)
.
Click to expand...
Click to collapse
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,

Tigger31337 said:
What ver TWRP did you use?
Apparently there is an official version and a modified version to mount vendor-specific mount points?
Thanks,
Click to expand...
Click to collapse
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps

jmalmberg said:
I renamed the TWRP file I flashed "recovery.img" and I don't remember the original file name. When I boot to recovery mode it says 3.3.0-0. Hope that helps
Click to expand...
Click to collapse
Yup, I solved it. Thanks. I ended up using 3.2.3.official.

Rooting; ending in bootloop help
Sorry if I am hijacking this thread; thought to discuss here as the title "Trouble rooting my g6" still applies.
I have:
XT1925-13 (Moto G6 ALI) running stock Android Pie with build ppss29.55-34.
I have issues when I tried to root. I followed these steps:
I downloaded the factory image “ALI_RETAIL_9.0_PPS29.55-34_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip” and flashed it first. The mobile restarted and went to the first screen to select a language.
I rebooted it into bootloader, ran the TWRP as a temp by command “fastboot boot twrp-3.3.0-0-Ali.img,” which asked for the password.
I pressed cancel, and then I wiped cache and data.
Via ADB I transferred “adb push Magisk-v20.0.zip /sdcard” and “adb push no-verity-opt-encrypt-6.1.zip /sdcard”.
Then from TWRP, I installed Magisk. Then when installing no-verity, it gave an error “updater process ended with an error: 1 error installing zip file ‘no-verity-opt-encrypt-6.1.zip’.
Rebooted the device with hope and ended in a boot loop.
I also tried to use Magisk-v19.4.zip in the above steps and also tried to skip no-verity-opt-encrypt-6.1.zip. All ended in boot loop.
Any idea why? Are there any guides for the combination XT1925-13 (Moto G6 ALI) running ppss29.55-34?
Many thanks for your time.

Here is a solution
Flash original boot in fastboot followed by TWRP and reboot in recovery.
Install Magisk 19.4 in TWRP (3.3.x Android 9 OK) and reboot
You can update to 20 in Magisk Manager later