The following lines were added (+) and removed (-):
The Moto G Power XT 2041-4 is retail US retail device but can be also sold from carriers such as US cellular and Google Fi. The XT 2041-6 is a model only sold by consumer cellular. All phones variants can support both CDMA and GSM service providers. You can buy the US version (XT2041-4) on the Motorola web or from 3rd party sources, it is the carrier unlocked Moto G Power for North America and uses a radio configured for North America optimized bands. '''WARNING! - Root by patching boot.img from XT2041-4_SOFIA_RETUS_10_QPMS30.80-63-6-8-3_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip obtained off of lolinet FAILED! We do not have a verified working root solution at this time. The guide below is academic if not practical.'''=== Part 1: Set up communication between device and PC, query device, and request Unlock Key from Motorola for G8 ====== Part 1: Set up communication between device and PC, query device, and request Unlock Key from Motorola for G Power ===#[https://github.com/topjohnwu/Magisk Download Magisk Manager] as ''''MagiskManager-v8.0.5.apk'''' that you can copy from the PC to the phone in a later step, or otherwise install directly to the phone. MagiskManager-v8.0.5.apk is the install file for Magisk Manager at the time of this writing, newer version may now be available.#On computer copy ''''boot.img'''' and ''''stub-release.apk'''' to your phone storage, path similar to ''''mtp://[usb:002,012]/Internal shared storage/Download''''#On computer copy ''''boot.img'''' and ''''MagiskManager-v8.0.5.apk'''' to your phone storage, path similar to ''''mtp://[usb:002,012]/Internal shared storage/Download''''#Now install Magisk Manager apk on your Moto G8 Power and open it '''stub-release.apk'''' (stub-release did not work in our test, used the full debug version)#Now install Magisk Manager apk on your Moto G Power and open it '''MagiskManager-v8.0.5.apk'''' See section: '''Magisk is Confusing'''#Use Magisk Manager to patch the image file '''boot.img''' from the firmware you downloaded and copied to the phone.#Use Magisk Manager to patch the image file '''boot.img''' from the firmware you downloaded and copied to the phone. See section: '''Magisk is Confusing'''#Magisk will produce a boot-patched.img file, it can be difficult to find, if it doesnt appear try to copy it to the DCIM. Ensure it is visible and exists.#Magisk will produce a boot-patched.img file, it can be difficult to find, if it doesnt appear then disconnect the USB cable from the phone, wait a few seconds and reconnect it, now look again. This seems to cause the file to become visible.#Turn off your phone and then boot your Moto G Power into Fastboot mode.#Now move the boot-patched file back to your PC. It is recommended that you rename the unpatched boot.img file to boot.img.org or something and then rename the patched file boot.img. #Turn off your phone and then boot your Moto G Power into Fastboot mode. (hold volume down and power) Once in fastboot mode you may have to press arrow keys until you see "BOOTLOADER LOGS"The adb devices command will show that the phone device is unauthorized if you have not yet responded to the prompt on the Moto G8 Power phone itself that comes up when the phone is properly connected, USB debugging is active. The adb devices command will show that the phone device is unauthorized if you have not yet responded to the prompt on the Moto G Power phone itself that comes up when the phone is properly connected, USB debugging is active. * Update: added new source for firmware. see: * Update: added new source for firmware. see: https://mirrors.lolinet.com/firmware/moto/sofia/official/RETUS/ RETUS = Retail, United States. sofia (not sofiar) is for the Moto G Power (not the G8 Power). Motorola versions with these models is problematic, as there are variants. Here is a command to help you identify what your phone model and version currently is: fastboot getvar all Study the output to help you determine what firmware file you need to download and use. === Magisk is Confusing ===We have tested using installer stub-release.apk and MagiskManager-v8.0.5.apk. Note that 8.0.5 is the version current as of this writing and by the time you read this a newer one may be available. stub-release seems to be an online installer file whereas MagiskManager-v8.0.5.apk seems to be the full app. Using MagiskManager-v8.0.5.apk is preferred. Once you copy Magisk Manager installer to the phone and click on the apk file (Magisk Manager) you will be advised that the Google will block the install as it is from an unrecognized source. You can go tosettings from this warning dialog and allow the installation. *If using stub_release.apk Now the installer will launch and ask if you wish to install the full version of Magisk Manager. This you want to do. *If using MagiskManager-v8.x.x.apk then you have the full version. Check on the interface under Manager to determine if Magisk is current. The Magisk Manager interface is confusing if you've not used it before. You are presented with two main options under Home# Magisk - Install# Manager - Install Tap the Install option next to 1. Magisk, then on the next screen under -Method choose "Select and Patch a File" then browse to the download directory and select the boot.img. You will see a message indicating that it is flashing with a bunch of different ascii characters being interchanged for the text reading "flashing" which is an indication the process is proceeding. You will get a success message witha directory path and file name of the output patched boot file. When you navigate to the path using either Android files app or within the computer you may not see the output patched file. This is not uncommon. Disconnect the USB cable from the phone, wait a few seconds, then reconnect it. The computer will redetect the phone and if asked choose file transfer mode. Now the file should be visible in both the phone files app and via the computer in the Downloads directory path. You will see the magisk patched file, it will look something like this: magisk_patched_xxxxx.img What we have done is to take the boot.img file from the archive we downloaded, which is on the computer, and copied it to the Android where we use the app Magisk to patch the boot image file. Once patched, we then move it back tothe computer and put it in with the firmware files that we extracted from that firmware archive. However, it will need to be renamed boot.img and replace the unpatched boot.img file. Keep a backup of the unpatched boot.img simplyby renaming it something like boot.img.bak or boot.img.org or boot.img.unpatched. The patched version will be renamed boot.img and will be standing by in the folder and ready for the flash process. It seems like extra work to have to copy the boot.img file to the phone just to patch it and move it back to the computer again, however, in this method we use Magisk which is an Android app to do the work, and that is performed on the phone as the app runs on the phone. However, the flash process reads from the firmware files on the PC when it writes to the phone. The working directory on the computer for the firmware files that were extracted from the archive might be a path something like this example:* ~/Downloads/Moto G Sofia 10-30-80-63-6-8===bootloader mode===The phone needs to be booted into “Bootloader mode” to use the Fastboot commands. It enables access on all your device partitions. When you’re working on the bootloader mode, ADB commands will no longer work, as the device is not booted into Android OS. To use developer tools like fastboot and adb you have to enable developer mode on the android phone and Enable USB Debugging, to do so, You’ll need to enable Android developer options: #Settings -> About -> Build Number and Tap for 7 times.#Observer "You’re a developer now.”#Settings -> Developer Options -> USB debugging and enable it.A word on fastboot oem unlock: Running the unlock command in the command prompt will wipe your entire data on the phone.The boot image contains the kernel of your device. You can use the Fastboot Flash boot command to replace the stock kernel with a custom kernel. fastboot flash boot bootimage.imgFOR TESTING A KERNEL IMAGE without overwriting anything on the phone... ie playing it safe... boot with a host-side kernel image. This command allows you to download a kernel image (and optional root filesystem image) and boot the phone with those, instead of using the kernel and rootfs in the boot flash partition. It is very useful while developing a kernel or modifying the rootfs. fastboot boot < kernel > [ < ramdisk > ]The difference is that you exclude the word "flash" therefore not actually writing over the boot.img on the phone while still booting from an alternative boot.img.===TWRP Custom Recovery Advantages===You can install TWRP. When you install a custom recovery such as TWRP on the Android phone you replace the stock recovery with the custom recovery. fastboot flash recovery twrp.imgSwitching from a carrier rom to an unlocked version won't SIM unlock a phoneSwitching from a carrier rom to an unlocked version won't SIM unlock a phone. All Motorola firmware comes with two xml files, flashfile.xml and servicefile.xml ( simply flash and service ) with the difference being that the the flash file will wipe the device and the service file does not while both install the firmware. Flash full ROM using LMSA rescue is the simplest method.Flash full ROM using LMSA rescue is the <s>simplest method</s>. However LMSA rescue is Lenovo's poor excuse for software that under the most ideal computer configuration still is buggy or refuses to run.or whatever your boot.bin is called and this will test your patched file. or whatever your boot.bin is called and this will test your patched file. The phone needs to be booted into “Bootloader mode” to use the Fastboot commands. It enables access on all your device partitions. ===touchscreen does not work after flash===If the touchscreen didn't work then that usually means you flashed a different version of the kernel / signed differently. If you can get the stock boot.img and flash it...it should recover itself also.===Rescue and Smart Assistant (LMSA)===Tested with zero success / '''unsuccessful''' and not recommended - buggy program requires additional registrations interface does not load on Windows 7 64-bit unable to proceed.Requires Micro$oft Windows. Lenovo chooses to ignore Mac and Linux users.Requires lots of registration. Apparently your Lenovo account and your Motorola account is not enough, this fucking app requires you to register yet another asshole Lenovo ID just to use it. The software calls on chromium engine to load the registration page which seems to fail, so you will be lucky if you can even get past this step in this asshole piece of shit Lenovo pile of steaming turd mess.If your device does not power on, has serious software issues, or you forgot your PIN, reinstalling the device firmware with the Lenovo Rescue and Smart Assistant (LMSA) tool could resolve the issue and avoid having to repair or replace your device. Online the tool is often referred to as LMSA for short. Compatible Windows 7 or 10 having to be 64 bit. Rescue and Smart Assistant (LMSA) is an official tool installs on PC. Can help to manage smart device (include all Lenovo android phone, MOTO phone, Lenovo tablet ) data, flash smart device software, and more Lenovo support functions. LMSA does not work though a virtualbox or other virtualization environment. It is not recommended via Wine. Sadly, it requires a PC with a direct installation of Windowze.* [https://support.motorola.com/uk/en/products/cell-phones/moto-g-family/moto-g8-power/documents/MS140571 Lenovo Rescue and Smart Assistant (LMSA)] and [https://support.lenovo.com/in/en/downloads/ds101291 files]. You will also need crappy .Net Framework 4.5. (because Lenovo can't hire real coders). Also, the basic framework Micro$oft provides for running binaries is insufficient, as it seems necessary to install the full developer version if you get an error from the Lenovo installer stating it cannot detect the presence of dot-net framework.you must install the [https://support.motorola.com/us/en/drivers Motorola Device Manager/USB drivers] in addition to LMSA, otherwise LMSA will incorrectly insist your phone is not in fastboot flash mode if you have to resort to rescuing from fastboot mode.===RootJunkys RSD Lite===Using RSD-Lite-Mac-Linux.zip from rootjunkys - tested and '''highly successful''' results with correct firmware.How to use RSD-FLASH.SH file on your Mac or Linux machines.#Download the RSD-Lite-Mac-Linux.zip here and extract the zip to location where u end up with a folders called RSD-Lite-Mac-Linux#Paste extracted firmware files into the same folder (RSD-Lite-Mac-Linux) as the rsd-flash.sh resides#In console from within the RSD-Lite-Mac-Linux folder execute the rsd-flash.sh command followed by your choice flashfile.xml or servicefile.xml#watch for any errors. If no errors at the end of the script then press enter to reboot the device.If there are errors then you are hosed. Good luck!*https://www.youtube.com/watch?v=HDmABQazDIc&feature=youtu.be*http://rootjunkysdl.com/files/?dir=Android Programs