I can not be held responsible for any type of problem with your device. This information is for the sole purpose of reporting and is delivered "as is". Only the tests will confirm if everything works well or does not work at all, proceed with caution.
- Make sure to back up all information, device data, and (optional) persistence partitions of the device.
- Always use common sense, and confirm that you do not have an error message in the console. Verify that things are done correctly.
- Make sure that the drivers and everything related to connectivity is working properly. The official Motorola drivers work fine, and the google fastboot drivers too. Look for tutorials on installing the fastboot driver if your computer is not detecting it properly, the tutorials of other moto models (eg moto g5 plus) on the drivers and others work just as well.
- All this process spends time and of course the battery of your device, make sure you have a good battery (50+) and stay connected as much as possible.
- Make sure you install the right firmware, in other devices from Oreo things are not so tight, in my case, my XT1926-7 device works perfect with a retailUS firmware, but it depends on each one...
- All the commands and others are done from the fastboot utility, you can find it in https://developer.android.com/studio...platform-tools.
- Download the correct firmware for your device.
Right now there are not many firmware available, as time passes the list will grow.
One of several sites is LOLINET.
- (If not already installed, make sure of ..) Install the drivers and download the fastboot utility. And of course, verify that the driver works properly. It will be done later.
- Extract the fastboot utility, and the firmware within the same directory.
To verify the connection, enter the bootloader of your device, connect it with the PC. On the PC; run the console, go to the folder where you extracted the fastboot utility, and type fastboot.exe devices, you should see the listed device in the console.
If the connection works correctly and you notice nothing strange, you can start the process.
- Open the console in the directory where the fastboot utility is on the firmware files, there should be no more folders inside. (In this case you should adjust the path of the files in the commands). And write the following commands, verify that you do not have errors.:
The commands listed below as "optional" do not necessarily have to be executed, but to be completely safe, execute them all, as long as you have the right firmware.
fastboot getvar max-sparse-size fastboot oem fb_mode_set fastboot flash partition gpt.bin fastboot flash bootloader bootloader.img (optional) fastboot flash modem_a NON-HLOS.bin fastboot flash fsg_a fsg.mbn fastboot erase modemst1 (Optional) fastboot erase modemst2 (Optional) fastboot flash bluetooth_a BTFM.bin fastboot flash dsp_a dspso.bin fastboot flash logo_a logo.bin fastboot flash boot_a boot.img fastboot flash system_a system.img_sparsechunk.0 fastboot flash system_a system.img_sparsechunk.1 fastboot flash system_a system.img_sparsechunk.2 fastboot flash system_a system.img_sparsechunk.3 fastboot flash system_a system.img_sparsechunk.4 fastboot flash system_b system_b.img_sparsechunk.0 fastboot flash system_b system_b.img_sparsechunk.1 fastboot flash oem_a oem.img fastboot flash oem_b oem_other.img fastboot flash vendor_a vendor.img_sparsechunk.0 fastboot flash vendor_a vendor.img_sparsechunk.1 fastboot erase carrier (Optional) fastboot erase userdata fastboot erase ddr fastboot oem fb_mode_clear
- Press the Power button, and wait a bit.. It will take a few minutes to start.
If you hear "Hello moto", congratulations you are in Stock (and everything "should work fine").
- If your firmware has more or less sparsechunk files (eg, sparsechunk.3 or img_sparsechunk.7), run them all.
- The bootloader will remain unlocked.
With love by iGor.