[Moto G6 Plus Questions & Answers] lcmp:
This is how I managed to fix my Moto G6 plus

I was able to fix my phone so I will reply to my own post:

It took me almost 4 days to fix the phone. It took a lot of reading and MANY hours of trial and error, so I´m going to describe what I did in order to help anybody with the same problem to save themselves a LOT of time.

As it happens, I found out that a lot of people have run into the same problem of bootloops after uninstalling magisk and then even after flashing the stock rom, had no wifi and no carrier signal. Hence, a useless phone.

Prerequisites for this solution:

Be able to boot your phone into bootloader mode.

If you don´t know what bootloader mode is, do your research. It´s very simple to get to it. Just power off your phone and then press the power and volume down buttons simultaneously for a couple for a couple of seconds. How to use it is another matter entirely. Again... do your research.

1. Before disaster strikes... Do not use an installer script to force install TWRP on a phone which has A / B boot slots. If you plan to install Magisk later, do not force instal TWRP. Moto G6 Plus is such a phone. This is written very clearly in the Magisk troubleshoot wiki. I wish I had read this before.

If you want to use TWRP ( and you should ), load TWRP 3.3 or newer temporarily from fastboot with the boot command. It will be able to decrypt your phone´s data. TWRP 3.2 does not.

To decrypt you will need to have a pin or pattern unlock set previously on your phone.

I used a script to force install twrp 3.2 to my phone. It´s useless since it can´t decrypt the phone and it was surely the cause of all this mess.

I´m not blaming TWRP or Magisk. This mess was all my fault. I´ll tell you about it later.

2. I have a TWRP 3.3 full decrypted backup of ALL the partitions of the phone from last week. I always do regular backups. I´ve been using TWRP for years and it has always served me well. This time it didn´t. My bad, not TWRP´s. I flashed the backup to the phone and it kept bootlooping. I flashed the backup about 20 times!

3. If you´re in this mess already because you forced install TWRP and you uninstalled magisk and your phone is bootlooping, you will probably have to wipe your phone and flash the stock ROM appropriate to your model. Trust me, if you´re not an android / linux guru, your only way to get your phone back will be to wipe your phone completely. I realized this the hard way.

Don´t flash the original ROM for the G6 plus ( android 8 ). Use the latest build. It seems motorola took note of so many people having the "no carrier / no wifi signal" problem, so they have included a fix for this in the latest android 9 releases. This has worked for other people, It worked for me. I don´t know for sure if it will work for you.

4. Here´s one important piece of info. For motorola phones it is very important to have a backup of these two partitions:

EFS

PERSIST

I´m not 100% percent sure of all the info they have or the entire purpose that they serve, but I now know 1 thing. These two partitions have critical and unique information about your phone.

They provide the unique IMEI info. Wifi Mac address info. Baseband info, which is all the technical carrier signal communications stuff, etc..

How do you back up these partitions? Use a custom recovery like TWRP or similar. If you want to mod your phone, please do your research on the software you are going to install. I usually do it, this time around I just winged it, and look where it got me.

5. Here´s another important piece of information to take note of BEFORE disaster strikes. Write down on a piece of paper and store in a safe place ( a txt file on your pc will do ) the following:

Your phone´s exact model Nº. Mine is:

XT1926-7

Go to settings: tap System, tap about phone and write down which software channel you are on.

Mine is: RETLA

This is important because it determines which stock ROM you will need to download, as not all ROMS for this device are the same. The XT1926-7 is a dual SIM phone so NO. Not all versions of the stock rom will work.

6. In order to download the correct stock ROM for your phone, on your computer, go to:

mirrors .lolinet .com /firmware/moto/evert/official/

This website is one of several which offer stock roms for motorola phones. You can use this one or search around for another one.

The website will show you a directory structure of all the different software channels available for the motorola Moto G6 Plus. Choose the folder appropriate for your phone.

Remember mine was the RETLA channel?

These are the only channels which offer stock roms for the XT1926-7

RETLA

or

TEFCO

or

TEMX

or

TIGCO

If your phone is factory unlocked you will probably have to use the RETLA versions.

Within the correct folder, look for the latest ROM for your model. Pay close attention to the name of the rom. The first section will indicate what model it´s intended for. For example, in the RETLA folder there´s ROMS for 2 different models:

XT1926-6

XT1926-7

The correct file for my phone was:

XT1926-7_EVERT_RETLA_DS_9.0_PPWS29.116-11-6_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip

Please do your research and download the right file for your phone. If you´re not careful, it will lead to bigger problems.

Please also download the original factory version of android 8 ( oreo ) made for your phone. you´re gonna need 2 files from that ROM. In my case the file was:

XT1926-7_EVERT_RETLA_8.0.0_OPWS27.113-89-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml

The stock roms are about 2 gigs in size.

6. Next you´ll need to download the right tools to flash the stock rom to your phone.

I´m assuming you have downloaded and installed the latest motorola USB drivers for your computer and installed them. If you haven´t. The time is now.

The internet will tell you to download the Android SDK platform tools. This package will give you fastboot and ADB.

Don´t download it. The "vanilla / run of the mill" version of fastboot won´t help you.

Motorola created a modified version of fastboot for their phones, which flashes a motorola phone in specific ways. It´s called: mfastboot

I saw the procedure differences while running mfastboot in the DOS window. In the end I was able to fix my phone because of the differences which mfastboot offers. You´re gonna have to trust me on this one.

Since the motorola version of fastboot is small in size, i´m going to attach it to this comment. Look for the attached file named:

mfastboot_adb_tools.zip

7. Create a folder on your hard drive. It doesn´t matter how you call it. Just remember where it is. Unzip / decompress the entire contents of the file:

mfastboot_adb_tools.zip

you just downloaded to that folder. it should look like this:

Then unzip / decompress the entire contents of the:

XT1926-7_EVERT_*YOUR-CHANNEL*_DS_9.0_PPWS29.116-11-6

to the same folder. it should look like this:

Now we will need just 2 files from the:

XT1926-7_EVERT_*YOUR_CHANNEL*_8.0.0_OPWS27.113-89-5

Unzip these two files to the same folder where you have unzipped everything else:

8. It is now time to boot your G6 Plus into bootloader mode. With the phone turned off, press the power and volume down buttons simultaneously for about 5 seconds.

You´ll get a black screen with the android robot laying on its back. At the bottom of the screen you will see a piece of text which reads:

Connect USB Data cable.

Do it. Connect the usb cable to your computer and then connect it to the phone. the connect data cable message will change to a green sentence which reads:

Transfer mode: USB connected

9. On your computer, return to the folder where you placed all the files. Look for a blank space with no files within that folder and press the shift key + mouse right click. out of the context menu you get, select:

open command window here

You will get a black screen with a white prompt.

Now let´s make sure your phone is connected to your computer. In that black window type:

mfastboot devices

The result should be your phones serial number followed by the word fastboot.

If you got nothing or any sort of error it means you phone is not connected properly or some drivers are missing. troubleshoot that and come back when your phone is actually connected.

10. OK... let´s start flashing the files. The following series of commands I copied from another post in this website. I did not come up with this set of commands and I will repeat that i´m no expert. This worked for my particular situation and by no means i can guarantee that it will work with your phone. All I´m saying is that if you´re desperate and at the current moment you have a soft bricked phone, go ahead and try this.

In that black window, start copying these commands 1 by 1. Wait for them to execute and get an OK message from the phone. If you get an error try that command again. to paste the command in the black window ctrl + v does not work. you have to right click your mouse on top of that window and paste the command that way. When you´ve pasted the command, press enter to execute.

These are the commands:

mfastboot getvar max-sparse-size

mfastboot oem fb_mode_set

mfastboot flash partition gpt.bin

mfastboot flash bootloader bootloader.img

mfastboot flash modem_a NON-HLOS.bin

mfastboot flash fsg_a fsg.mbn

mfastboot erase modemst1

mfastboot erase modemst2

mfastboot flash bluetooth_a BTFM.bin

mfastboot flash dsp_a dspso.bin

mfastboot flash logo_a logo.bin

mfastboot flash boot_a boot.img

mfastboot flash system_a system.img_sparsechunk.0

mfastboot flash system_a system.img_sparsechunk.1

mfastboot flash system_a system.img_sparsechunk.2

mfastboot flash system_a system.img_sparsechunk.3

mfastboot flash system_a system.img_sparsechunk.4

mfastboot flash system_b system_b.img_sparsechunk.0

mfastboot flash system_b system_b.img_sparsechunk.1

mfastboot flash oem_a oem.img

mfastboot flash oem_b oem_other.img

mfastboot flash vendor_a vendor.img_sparsechunk.0

mfastboot flash vendor_a vendor.img_sparsechunk.1

mfastboot erase carrier

mfastboot erase userdata

mfastboot erase ddr

mfastboot oem fb_mode_clear

press power button on the phone and restart it.

It might take a while to boot, but if and when you see and hear the "hello moto" greeting, it means your phone has been fixed.

You might end up with a restored phone, but no wifi and no carrier signal. Then what you will need to do is to flash the backup of your EFS and Persist partitions using TWRP, and then retry the whole procedure again.

This is the way I fixed my Moto G6 plus.

It wasn´t a perfect fix for me. Since I had forced installed TWRP 3.2 with an installer script, that did something to the boot partition and now even after reflashing the entire phone I don´t have any type of recovery.

No stock recovery of any kind. It´s not a problem since we can boot TWRP temporarily from mfastboot and in bootloader mode just like the procedure we did with the stock rom. All the rest is back to perfect working condition.

I was also able to make a new full phone backup.

I will tell you this, now I know that all this mess is not TWRP´s or Magisk´s fault. They are fine programs. It was my fault due to a lack of research. I shouldn´t have mixed them both in the way I did.

I forced installed TWRP to my phone because it was what I was used to and I didn´t read any instructions for Magisk which I had never used. I come from the SU era.

I hope this wall of text will be of help to anyone going through the same situation with a Moto G6 plus.

Unfortunately nobody replied to my original post so I had to solve this on my own. The good thing is that I did manage to fix it.

I will repeat it one more time. I´m not an android expert. Not by far. I´m not saying this procedure will work for your particular problem. I´m only sharing what worked for me and I hope it will work for you. If it doesn´t. Keep looking and researching.

GOOD LUCK.