How to downgrade Android 11 to 10

Search This thread

jhford

Senior Member
Well, I rescued - again, with LRSA and I'm back to stock A11. 😢 I think I'll delete everything I installed on my Windows 10 laptop and reinstall everything, retry tomorrow, and report back.
Pardon the delayed reply, but I got busy with worldly matters, OMG. I can't believe it. I'm running A10 stock. Here's what I did.
  • Downloaded A10 firmware again, but deleted it because I downloaded the same file last week.
  • Deleted flashfile.bat from all directories.
  • Re-ran 2-rsd-flash-flashfile-windows.bat.
  • Copied flashfile.bat to the sofia factory restore directory.
  • Booted the phone to fastboot.
  • Booted recovery from fastboot.
  • Ran "Enter fastboot" which booted fastbootd.
  • Double clicked flashfile.bat in sofia factory restore.
Everything processed the same way it did last week, but this time A10.

Now for the $64 question. I'm very used to running various customs Roms. But they seem to come and go, which I understand; thankless job. But Moto has announced that it will no longer support Sofia XT-2401-4. So, I want to install one that will last and provide long term updates and upgrades. And, of course, I want to root it. BTW I've had nothing but trouble with Magisk 24.x, so I'm sticking with 23.x until the smoke clears. I am running Lineage OS 19.x on my Nexus 7 2013 deb tablets, and it's fine. I can't complain. I'm not a stickler for the very best. I primary want durability. What would you suggest? And are there any unusual Rom installations steps/tricks I should know?
And once again, thanks for all your help. Android Junky must be happy, also.
 

someguy1233

New member
Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.
The second option will reset the phone, right?
 

someguy1233

New member
Downgrading the android version with Moto firmware is always a risk.
If you downgrade you need to disable updates, OTA updates could brick the device.

First Unlock the bootloader

Once the bootloader is unlocked, find your
Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...

You can find your firmware here

download. and Unzip it

Check if your device uses fastbootd

Flash option 1
Find the flashfile.xml in the firmware folder
and use the online flashfile converter to get the flash commands
add the fastboot reboot fastboot commands if you have a fasbootd device.

Flash Option 2
Install LMSA
use the rescue option to download the current firmware for your device
move the LMSA firmware to a different folder
rename the Android 10 firmware folder to the same name as LMSA firmware.
Move that folder to the LMSA download folder
Use the rescue option to flash renamed firmware.

There is no guarantee that either method will work, but it should.


On the phone
Toggle off "install updates" option in Dev Options
Hey, do you know how to move apps to SD card? I have rooted my Moto G8 Power (Android 11) with Magisk, but I still can't move apps with any app like link2SD (it shows me failure [-6]), apps2SD (it shows me a lot of text) or AppMgr III.
I was about to return to Android 10 because I assumed it was caused by my Android version, but it really was because Motorola manufacturers blocked that option in this device (it can't be formatted as internal storage in the SD card settings). So do you know how to evade this blockage?
 
Last edited:

Alan172

New member
Oct 20, 2018
1
0
Hoily Heysoos Crisco!

I done almost bricked my G Power 2020 XT2041-4 RETUS.

After making the mistake of connecting to WiFi during setup of a unlocked (advertised as bootloader unlockable too) Moto G Power I bought on ebay that came w/ A-10, it OTA'd to A-11 in the background (while installing a lot of g0ggle-bloat) and after reboot I was Android 11 which meant no custom ROMs! So I proceeded down the rabbit hole of A11 to A10 downgrade and it was a scary ride!

Long story short, I lost fastbootd because I didn't understand fastbootd is a userspace layer that is integrated w/ recovery according to:
https://source.android.com/devices/bootloader/fastbootd
and should be distinctly differentiated from the bootloader now while only the newest fastboot command package works to get to fastbootd from the bootloader.

DISCLAIMER:
I am not a dev.
I am a linux user (which gave me a slight advantage during rescue).
While I can read/understand instructions well enough to have done custom ROMs many times before (Samsung S4/5, Ouya/Madcatz MOJO game boxes, Moto G4 and lastly my beloved Moto G6+ dual SIM which ATT nuked 3G service for Feb. 22-ish 2022), I relied on my previous tools(FWUL)/knowledge to flash once again w/ an Android version I had no experience with and it bit me in the tookus!
This will NOT help you if you have a 2021 G Power (borneo).

This will be long as I'm mashing what I found in many threads together into how I rescued my Moto G Power so click the spoiler to see how.

First thing I noticed was when getting ready to put on a custom ROM was using "adb reboot fastboot" (on my desktop machine) dumped me to fastbootd which I had never seen before.
The above command is the only way I was able to get to fastbootd at the time. So I used the volume/power to get to the bootloader (what I recognized as what happens when I did "adb reboot fastboot" before).

This confused me and I went to research fastbootd and after reading posts of bad experiences with fastbootd and flashing I decided I needed to do more research (this ultimately saved me and allowed downgrade):

So I tried what I'd read about verifying if you have fastbootd using "fastboot getvar is-userspace" which gave me:

flash@bench:~$ fastboot getvar is-userspace
is-userspace: no
Finished. Total time: 0.000s

So I thought I was safe because I didn't understand that the "yes" value only shows when asKed during fastbootd and is "no" when in the bootloader.
E.G.:

flash@bench:~$ fastboot getvar is-userspace
is-userspace: yes
Finished. Total time: 0.000s

I first tried downgrading via LMSA v5.9.2.4 (64-bit ONLY now) in a virtualbox Win7-64 virtual as it might have OEM specific tricks to deal with their hardware.
So after it downloaded the A-11 package, I moved the downloadeded folder out of C:\Program Data\RSA\downloads, replacing it w/ an extracted A-10 package folder renamed to the A11 package name, and let it rip.

It had tricks, but not good ones (when run virtual at least).
I've seen reports of it working, but only when run non-virtually I guess.

The Moto G Power USB device it showed up as disappeared when LMSA rebooted the phone using what seems like "fastboot reboot fastboot" (from it's behavior) and I needed a to make a custom filter for "Motorola Mobility LLC. Fastboot sofia S(0100)" by stopping the virtaul machine w/ the phone booted into the bootloader and then creating a persistant filter from what it showed up as now.

After that, I tried flashing.
It got to 32% (as another poster experienced) and stopped w/ the phone rebooting the bootloader screen over and over like it did each time I tried to connect the Fastboot USB device dynamically before.

The phone would only boot to the bootloader now. :-(
I have only myself to blame though as I'd seen another poster who claimed probelms when using LMSA vitually.

Then I tried flashing A-10 using FWUL which I hadn't been updated since I was ROM'ng the G6+ 4 YEARS ago:
I looked at the project page and found I still had the latest version and had no idea that adb and fastboot commands had changed so much and that was the reason "fastboot reboot fastboot" while in the bootloader gave the output
"fastboot: usage: unknown reboot target fastboot" as a response instead of booting to fastbootd.

I used it because my native linux fastboot package 4 years ago had problems when used on a system w/ an AMD processor and I could boot FWUL from USB on a Celeron laptop I had handy which became my flashing machine but have found it woefully out of date now in 2022.
(HINT: check your adb/fastboot version and make sure you're using the latest.)

So now I'm stuck in the bootloader and "fastboot reboot recovery" goes to this "no command" screen and think I have borked the G Power beyond all saving and it makes me think "Well, I can't break it much worse than this!" so I'm willing to try anything.

I have a folder dedicated to the G Power custom ROM project looking at the files in there and and amongst A-10/A-11 stock firmwares and HavocOS ROM, see boot.img . I forget where/why I downloaded it (probably in search of rooting the G Power) and decide as a last ditch effort to try "fastboot boot boot.img".

The phone reboots and Hot Diggity Dognuts!, there is the fastbootd screen!!!

After reading @auhsoj200 's post in this thread finding out that downgrading worked for him when flashed from fastbootd I immediately use the "flashall" shell command @Quantumstate posted in the HavocOS thread:
in the extracted A-10 official firmware folder, reboot, and now am at the "Get started" screen like the phone was when I got it!

THIS TIME I skip both SIM and WiFi screens and breeze through the new gestures tutorial to get to settings and check Android version in "About phone" which now says 10!!

As soon as this check is done I do the 7x's tap on Build number to turn on Developer options and then got to System/Developer options to turn OFF Automatic system updates to make sure I don't have to do this all over again!

So now I'm back from brickdom, have A-10, and am now ready to start trying out customizations (like TWRP, root, ROMs, etc.).

TWRP DOES NOT FLASH CORRECTLY IN FASTBOOTD and will give the dead droid "No command" screen for any attempt to boot to recovery after trying that way.

But running "fastboot flash recovery twrp-3.5.0-0-rav-sofia.img" in the bootloader will boot TWRP when recovery boot is chosen.

I did apply a custom fabbed logo I'd built for the G6+ (as the G Power has a silimarly sized screen) with "fastboot flash logo logo.bin" in the bootloader and it shows up for ~2 sec., then gives the unlocked bootloader warning in text only for another ~3 sec., and then goes back to the custom logo for another ~2 sec. before booting fastboot/recovery/system now.
Not perfect, but better!

Below are the commands/output I used in the order used to get here:

flash@bench:~$ fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.017s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
flash@bench:~$ fastboot devices
ZXXXXXXXXX fastboot
flash@bench:~$ fastboot reboot recovery
Rebooting into recovery OKAY [ 0.020s]
Finished. Total flashe: 0.070s
flash@bench:~$ cd Downloads/Moto_G8_Power/
flash@bench:~/Downloads/Moto_G8_Power$ ls
boot.img
Havoc-OS-v4.14-20220227-sofiar-Official.zip
Lenovo_Moto_Smart_Assistant_v4.5.0.14.zip
Magisk-v24.3.apk
rescue_and_smart_assistant_v5.9.2.4_prod_setup.exe
twrp-3.5.0-0-rav-sofia.img
XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
flash@bench:~/Downloads/Moto_G8_Power$ fastboot boot twrp-3.5.0-0-rav-sofia.img
Sending 'boot.img' (42408 KB) OKAY [ 1.093s]
Booting (bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote: '')
fastboot: error: Command failed to boot into userspace fastboot; one or more components might be unbootable.
flash@bench:~/Downloads/Moto_G8_Power$ fastboot boot boot.img
Sending 'boot.img' (65536 KB) OKAY [ 1.670s]
Booting (bootloader) Failed to load/authenticate boot image: Not Found
FAILED (remote: '')
fastboot: error: Command failed
flash@bench:~/Downloads/Moto_G8_Power$ cd A11
flash@bench:~/Downloads/Moto_G8_Power/A11$ ls
boot.img
bootloader.img
<snip>
super.img_sparsechunk.9
vbmeta.img
flash@bench:~/Downloads/Moto_G8_Power/A11$ l flashall
-rw-r--r-- 1 flash flash 1284 Mar 23 13:28 flashall
flash@bench:~/Downloads/Moto_G8_Power/A11$ chmod 0777 flashall
flash@bench:~/Downloads/Moto_G8_Power/A11$ l flashall
-rwxrwxrwx 1 flash flash 1284 Mar 23 13:28 flashall
flash@bench:~/Downloads/Moto_G8_Power/A11$ ./flashall
Flashing to Stock Android 10...

max-sparse-size: 268435456
Finished. Total flashe: 0.000s
OKAY [ 0.005s]
Finished. Total flashe: 0.005s
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' (bootloader) Validating 'gpt.default.xml'
(bootloader) Committing 'gpt.default.xml'
(bootloader) - flashing 'gpt_main0.bin' to 'partition:0'
OKAY [ 0.466s]
Finished. Total flashe: 0.469s
Sending 'bootloader' (14204 KB) OKAY [ 0.380s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Committing 'bootloader.default.xml'
(bootloader) - flashing 'cmnlib.mbn' to 'cmnlib'
(bootloader) - flashing 'cmnlib64.mbn' to 'cmnlib64'
(bootloader) - flashing 'keymaster.mbn' to 'keymaster'
(bootloader) - flashing 'hyp.mbn' to 'hyp'
(bootloader) - flashing 'tz.mbn' to 'tz'
(bootloader) - flashing 'devcfg.mbn' to 'devcfg'
(bootloader) - flashing 'uefi_sec.mbn' to 'uefisecapp'
(bootloader) - flashing 'prov64.mbn' to 'prov'
(bootloader) - flashing 'rpm.mbn' to 'rpm'
(bootloader) - flashing 'abl.elf' to 'abl'
(bootloader) - flashing 'qupfw.elf' to 'qupfw'
(bootloader) - flashing 'xbl_config.elf' to 'xbl_config'
(bootloader) - flashing 'xbl.elf' to 'xbl'
OKAY [ 0.313s]
Finished. Total flashe: 0.871s
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.006s]
Finished. Total flashe: 0.008s
Sending 'radio' (199933 KB) OKAY [ 5.079s]
Writing 'radio' (bootloader) Validating 'radio.default.xml'
(bootloader) Committing 'radio.default.xml'
(bootloader) - flashing 'NON-HLOS.bin' to 'modem'
(bootloader) - flashing 'fsg.mbn' to 'fsg'
(bootloader) - erasing 'modemst1'
(bootloader) - erasing 'modemst2'
OKAY [ 0.881s]
Finished. Total flashe: 8.158s
Sending 'bluetooth_a' (4608 KB) OKAY [ 0.119s]
Writing 'bluetooth_a' OKAY [ 0.063s]
Finished. Total flashe: 0.184s
Sending 'dsp_a' (32768 KB) OKAY [ 0.836s]
Writing 'dsp_a' OKAY [ 0.193s]
Finished. Total flashe: 1.036s
Sending 'logo_a' (5040 KB) OKAY [ 0.133s]
Writing 'logo_a' OKAY [ 0.079s]
Finished. Total flashe: 0.297s
Sending 'boot_a' (65536 KB) OKAY [ 1.670s]
Writing 'boot_a' OKAY [ 0.616s]
Finished. Total flashe: 2.532s
Sending 'dtbo_a' (24576 KB) OKAY [ 0.624s]
Writing 'dtbo_a' OKAY [ 0.203s]
Finished. Total flashe: 1.120s
Sending 'recovery_a' (65536 KB) OKAY [ 1.669s]
Writing 'recovery_a' OKAY [ 0.850s]
Finished. Total flashe: 2.877s
Sending 'super' (262140 KB) OKAY [ 6.983s]
Writing 'super' OKAY [ 0.059s]
Finished. Total flashe: 7.121s
Sending 'super' (262140 KB) OKAY [ 7.296s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 8.865s
Sending 'super' (262140 KB) OKAY [ 6.951s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 8.152s
Sending 'super' (262140 KB) OKAY [ 7.021s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 8.178s
Sending 'super' (245904 KB) OKAY [ 6.492s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 7.606s
Sending 'super' (231856 KB) OKAY [ 6.180s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 7.294s
Sending 'super' (262084 KB) OKAY [ 6.988s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 8.176s
Sending 'super' (262140 KB) OKAY [ 7.005s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 8.134s
Sending 'super' (262140 KB) OKAY [ 7.045s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 8.290s
Sending 'super' (233732 KB) OKAY [ 6.208s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 7.310s
Sending 'super' (236012 KB) OKAY [ 6.255s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 7.268s
Sending 'super' (262124 KB) OKAY [ 7.006s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 7.988s
Sending 'super' (262120 KB) OKAY [ 6.855s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 7.925s
Sending 'super' (262124 KB) OKAY [ 6.689s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 7.782s
Sending 'super' (262124 KB) OKAY [ 6.724s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 7.830s
Sending 'super' (262140 KB) OKAY [ 6.743s]
Writing 'super' OKAY [ 0.001s]
Finished. Total flashe: 7.846s
Erasing 'carrier' OKAY [ 0.066s]
Finished. Total flashe: 1.158s
Erasing 'userdata' OKAY [ 0.080s]
Finished. Total flashe: 0.080s
Erasing 'metadata' OKAY [ 0.048s]
Finished. Total flashe: 0.048s
Erasing 'ddr' OKAY [ 0.046s]
Finished. Total flashe: 0.047s
OKAY [ 0.003s]
Finished. Total flashe: 0.003s
flash@bench:~/Downloads/Moto_G8_Power/A11$ fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total flashe: 0.050s
flash@bench:~/Downloads/Moto_G8_Power/A11$ fastboot devices
ZXXXXXXXXX fastboot
flash@bench:~/Downloads/Moto_G8_Power/A11$ fastboot getvar is-userspace
is-userspace: no
Finished. Total flashe: 0.000s
flash@bench:~/Downloads/Moto_G8_Power/A11$ fastboot set_active a
Setting current slot to 'a' OKAY [ 0.265s]
Finished. Total flashe: 0.265s
flash@bench:~/Downloads/Moto_G8_Power/A11$ fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total flashe: 0.050s
flash@bench:~/Downloads/Moto_G8_Power/A11$ fastboot reboot fastboot
Rebooting into fastboot OKAY [ 0.019s]
< waiting for any device >
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
flash@bench:~/Downloads/Moto_G8_Power/A10$ cd ..
flash@bench:~/Downloads/Moto_G8_Power$ ls
A10
boot.img
flashall
Havoc-OS-v4.14-20220227-sofiar-Official.zip
Lenovo_Moto_Smart_Assistant_v4.5.0.14.zip
Magisk-v24.3.apk
rescue_and_smart_assistant_v5.9.2.4_prod_setup.exe
twrp-3.5.0-0-rav-sofia.img
XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
XT2041-4_SOFIA_RETUS_11_RPMS31.Q1-54-13-8_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip
flash@bench:~/Downloads/Moto_G8_Power$ fastboot set_active a
Setting current slot to 'a' OKAY [ 0.556s]
Finished. Total flashe: 0.578s
flash@bench:~/Downloads/Moto_G8_Power$ fastboot flash boot boot.img
Sending 'boot_a' (65536 KB) OKAY [ 1.715s]
Writing 'boot_a' OKAY [ 0.612s]
Finished. Total flashe: 3.230s
flash@bench:~/Downloads/Moto_G8_Power$ fastboot reboot
Rebooting OKAY [ 0.046s]
Finished. Total flashe: 0.096s
flash@bench:~/Downloads/Moto_G8_Power$ cd A10
flash@bench:~/Downloads/Moto_G8_Power/A10$ ls
boot.img
bootloader.img
<snip>
SOFIA_RETAIL_QPMS30.80-109-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.info.txt
<snip>
super.img_sparsechunk.15
vbmeta.img
flash@bench:~/Downloads/Moto_G8_Power/A10$ l flashall
-rw-r--r-- 1 flash flash 1330 Mar 23 16:41 flashall
flash@bench:~/Downloads/Moto_G8_Power/A10$ chmod 0777 flashall
flash@bench:~/Downloads/Moto_G8_Power/A10$ ./flashall
Flashing to Stock Android 10...

getvar:max-sparse-size FAILED (remote: 'Unknown variable')
Finished. Total flashe: 0.001s
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
Sending 'partition' (37 KB) OKAY [ 0.002s]
Writing 'partition' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'bootloader' (14204 KB) OKAY [ 0.401s]
Writing 'bootloader' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'vbmeta_a' (4 KB) OKAY [ 0.001s]
Writing 'vbmeta_a' OKAY [ 0.008s]
Finished. Total flashe: 0.027s
Sending 'radio' (199565 KB) OKAY [ 5.321s]
Writing 'radio' FAILED (remote: 'No such file or directory')
fastboot: error: Command failed
Sending 'bluetooth_a' (4608 KB) OKAY [ 0.120s]
Writing 'bluetooth_a' OKAY [ 0.112s]
Finished. Total flashe: 0.322s
Sending 'dsp_a' (32768 KB) OKAY [ 0.873s]
Writing 'dsp_a' OKAY [ 0.253s]
Finished. Total flashe: 1.551s
Sending 'logo_a' (5040 KB) OKAY [ 0.140s]
Writing 'logo_a' OKAY [ 0.089s]
Finished. Total flashe: 0.326s
Sending 'boot_a' (65536 KB) OKAY [ 1.751s]
Writing 'boot_a' OKAY [ 1.499s]
Finished. Total flashe: 4.060s
Sending 'dtbo_a' (24576 KB) OKAY [ 0.660s]
Writing 'dtbo_a' OKAY [ 0.201s]
Finished. Total flashe: 1.172s
Sending 'recovery_a' (65536 KB) OKAY [ 1.764s]
Writing 'recovery_a' OKAY [ 1.454s]
Finished. Total flashe: 4.028s
Sending 'super' (262140 KB) OKAY [ 7.620s]
Writing 'super' OKAY [ 1.434s]
Finished. Total flashe: 9.141s
Sending 'super' (262004 KB) OKAY [ 7.730s]
Writing 'super' OKAY [ 1.444s]
Finished. Total flashe: 9.219s
Sending 'super' (261856 KB) OKAY [ 7.941s]
Writing 'super' OKAY [ 1.397s]
Finished. Total flashe: 9.418s
Sending 'super' (262140 KB) OKAY [ 7.788s]
Writing 'super' OKAY [ 1.362s]
Finished. Total flashe: 9.181s
Sending 'super' (262140 KB) OKAY [ 6.977s]
Writing 'super' OKAY [ 1.450s]
Finished. Total flashe: 8.433s
Sending 'super' (262140 KB) OKAY [ 7.081s]
Writing 'super' OKAY [ 1.443s]
Finished. Total flashe: 8.533s
Sending 'super' (262140 KB) OKAY [ 7.027s]
Writing 'super' OKAY [ 1.443s]
Finished. Total flashe: 8.478s
Sending 'super' (262140 KB) OKAY [ 7.024s]
Writing 'super' OKAY [ 1.427s]
Finished. Total flashe: 8.458s
Sending 'super' (256100 KB) OKAY [ 6.865s]
Writing 'super' OKAY [ 1.427s]
Finished. Total flashe: 8.300s
Sending 'super' (262140 KB) OKAY [ 7.065s]
Writing 'super' OKAY [ 1.444s]
Finished. Total flashe: 8.513s
Sending 'super' (262140 KB) OKAY [ 7.027s]
Writing 'super' OKAY [ 1.426s]
Finished. Total flashe: 8.460s
Sending 'super' (262140 KB) OKAY [ 7.015s]
Writing 'super' OKAY [ 1.455s]
Finished. Total flashe: 8.478s
Sending 'super' (262140 KB) OKAY [ 7.047s]
Writing 'super' OKAY [ 1.483s]
Finished. Total flashe: 8.536s
Sending 'super' (262140 KB) OKAY [ 7.040s]
Writing 'super' OKAY [ 1.451s]
Finished. Total flashe: 8.499s
Sending 'super' (235444 KB) OKAY [ 6.294s]
Writing 'super' OKAY [ 1.353s]
Finished. Total flashe: 7.655s
Sending 'super' (36112 KB) OKAY [ 0.959s]
Writing 'super' OKAY [ 0.252s]
Finished. Total flashe: 1.216s
fastboot: error: cannot load 'super.img_sparsechunk.16': No such file or directory
Erasing 'carrier' FAILED (remote: 'Partition doesn't exist')
fastboot: error: Command failed
Erasing 'userdata' OKAY [ 0.615s]
Finished. Total flashe: 0.618s
Erasing 'metadata' OKAY [ 0.050s]
Finished. Total flashe: 0.052s
Erasing 'ddr' FAILED (remote: 'Partition doesn't exist')
fastboot: error: Command failed
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
flash@bench:~/Downloads/Moto_G8_Power/A10$ fastboot reboot
Rebooting OKAY [ 0.000s]
Finished. Total flashe: 0.050s
flash@bench:~$ adb reboot fastboot
flash@bench:~$ fastboot getvar is-userspace
is-userspace: yes
Finished. Total flashe: 0.000s
flash@bench:~$ adb reboot fastboot
flash@bench:~$ fastboot getvar is-userspace
is-userspace: no
Finished. Total flashe: 0.000s
flash@bench:~$ fastboot getvar all
(bootloader) kernel: uefi
(bootloader) version-bootloader: MBM-3.0-sofia_retail-2c4117ea2d-211130
(bootloader) product: sofia
(bootloader) board: sofia
(bootloader) secure: yes
(bootloader) hwrev: PVT
(bootloader) radio: NA
(bootloader) storage-type: eMMC
(bootloader) emmc: 64GB MICRON S0J9K8 RV=08 PV=10 FV=0000000000000004
(bootloader) ufs: N/A
(bootloader) ram: 4GB MICRON LP4 DIE=16Gb M5-M8=FF 04 10 10
(bootloader) cpu: SM_NICOBAR 1.0
(bootloader) serialno: ZXXXXXXXXX
(bootloader) cid: 0x0032
(bootloader) channelid: 0x97
(bootloader) uid: FA0ECD25
(bootloader) securestate: flashing_unlocked
(bootloader) factory-modes: disabled
(bootloader) verity-state: enforcing (0)
(bootloader) iswarrantyvoid: yes
(bootloader) max-download-size: 805259264
(bootloader) reason: Reboot mode set to fastboot
(bootloader) imei: 3XXXXXXXXXXXXX
(bootloader) imei2:
(bootloader) meid:
(bootloader) date: 09-25-2020
(bootloader) sku: XT2041-4
(bootloader) carrier_sku: XT2041-4
(bootloader) battid: SB18C57585
(bootloader) battery-voltage: 4370
(bootloader) iccid: 8901260971115579508
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) poweroffalarm: 0
(bootloader) ro.carrier: fi
(bootloader) ro.build.fingerprint[0]: motorola/sofia_retail/sofia:10/QPM
(bootloader) ro.build.fingerprint[1]: S30.80-109-5/2d6e7:user/release-ke
(bootloader) ro.build.fingerprint[2]: ys
(bootloader) ro.build.version.qcom: LA.UM.8.11.r1-01800-NICOBAR.0
(bootloader) version-baseband: M6125_43.45.03.49R SOFIA_NA_CUST
(bootloader) kernel.version[0]: Linux version 4.14.117-perf+ (nobody@and
(bootloader) kernel.version[1]: roid-build) (clang version 8.0.12 for An
(bootloader) kernel.version[2]: droid NDK) #1 SMP PREEMPT Tue Sep 1 03:2
(bootloader) kernel.version[3]: 3:51 CDT 2020
(bootloader) git:xbl: MBM-3.0-sofia_retail-1186df2c-211130
(bootloader) git:xbl_config: MBM-3.0-sofia_retail-1186df2c-211130
(bootloader) git:rpm: MBM-3.0-sofia_retail-2579863-211130
(bootloader) git:tz: MBM-3.0-sofia_retail-da525ab-211130
(bootloader) git:hyp: MBM-3.0-sofia_retail-da525ab-211130
(bootloader) git:devcfg: MBM-3.0-sofia_retail-da525ab-211130
(bootloader) git:cmnlib: MBM-3.0-sofia_retail-da525ab-211130
(bootloader) git:cmnlib64: MBM-3.0-sofia_retail-da525ab-211130
(bootloader) git:keymaster: MBM-3.0-sofia_retail-cf01af6-211130
(bootloader) git:prov: MBM-3.0-sofia_retail-da525ab-211130
(bootloader) git:abl: MBM-3.0-sofia_retail-2c4117ea2d-211130
(bootloader) git:qupfw: MBM-3.0-sofia_retail-319dab9-211130
(bootloader) git:uefisecapp: MBM-3.0-sofia_retail-da525ab-211130
(bootloader) frp-state: no protection (0)
(bootloader) current-slot: a
(bootloader) running-bl-slot: _a/_a
(bootloader) running-boot-lun: 0
(bootloader) slot-count: 2
(bootloader) slot-successful:_a: yes
(bootloader) slot-successful:_b: no
(bootloader) slot-unbootable:_a: no
(bootloader) slot-unbootable:_b: yes
(bootloader) slot-retry-count:_a: 6
(bootloader) slot-retry-count:_b: 0
(bootloader) logical-block-size: 0x200
(bootloader) erase-block-size: 0x200
(bootloader) is-userspace: no
(bootloader) pcb-part-no: SB28C55260
(bootloader) primary-display: tm_ft8756_fhd_vid
(bootloader) secondary-display:
all: listed above
Finished. Total flashe: 0.067s
flash@bench:~$

Hope that helps somebody like me!
Now on to flashing HavocOS and rooting it and I'll update with any other issues/fixes I run into as the A-10 flash did have some failures.!
Could you explain a little better how you did to install fastbootd? I can't start it at all
 

theshadower10

Senior Member
Apr 7, 2011
65
8
Texas
so my mother-in-law gave me her old phone to mess around with (happens to be xt2041-6) and ive noticed that while trying every single way listed here it keeps erroring out. when using LMSA it errors out at around 68%, the method 1 from shadow also errors when going through even though it completes it bootloops and lastly the moto batch installer gets ALOT of errors when trying to install the boot files (too many to list but like bluetooth and wifi and antenna?). so its now at 0/3. HOWEVER, i can recover a11 with LMSA and get to the android start here point atleast. so unless someone has any ideas im stumped lol. btw the file i got on loli was (XT2041-6_SOFIA_CCAWS_10_QPMS30.80-63-6-8-5_subsidy-CCAWS_regulatory-DEFAULT_CFC.xml.zip)
 
  • Like
Reactions: fakepepsilol

fakepepsilol

Senior Member
Apr 11, 2021
79
14
Moto G8
so my mother-in-law gave me her old phone to mess around with (happens to be xt2041-6) and ive noticed that while trying every single way listed here it keeps erroring out. when using LMSA it errors out at around 68%, the method 1 from shadow also errors when going through even though it completes it bootloops and lastly the moto batch installer gets ALOT of errors when trying to install the boot files (too many to list but like bluetooth and wifi and antenna?). so its now at 0/3. HOWEVER, i can recover a11 with LMSA and get to the android start here point atleast. so unless someone has any ideas im stumped lol. btw the file i got on loli was (XT2041-6_SOFIA_CCAWS_10_QPMS30.80-63-6-8-5_subsidy-CCAWS_regulatory-DEFAULT_CFC.xml.zip)
I have the same problem. (xt2045-2) LMSA doesn't work, if i do it manually it boot loops. I even tried an older bootloader but still no luck. Can't figure out what causes it either, maybe some of the partitions are different, no clue.
 

chadman3030

Member
Feb 19, 2008
14
6
Moto G Power
The whole key to flashing Moto G Power per above seems to be using fastbootd mode instead of flashboot mode.

How to get there?

Prerequisites of flashing custom ROMS: Allow OEM unlocking + Unlock Bootloader and Enable USB Debugging in Developer options

1. While phone booted into system and running - connect USB cable and do "adb reboot fastboot" per ezjamm's post above
2. You are now in FASTBOOTD mode as indicated by bright red letters at the top!

-or-

1. From FASTBOOT MODE (power+voldown) scroll down using volume down button to RECOVERY MODE and press power button to select
2. When RECOVERY MODE boots it will show NO COMMAND (seems like nothing can be done here, but)
3. Now hold power button and press volume up button
4. Another menu will appear
5 choose ENTER FASTBOOT
6. You are now in FASTBOOTD mode as indicated by bright red letters at the top!
Hope this helps!
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Downgrading the android version with Moto firmware is always a risk.
    If you downgrade you need to disable updates, OTA updates could brick the device.

    First Unlock the bootloader

    Once the bootloader is unlocked, find your
    Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...

    You can find your firmware here

    download. and Unzip it

    Check if your device uses fastbootd

    Flash option 1
    Find the flashfile.xml in the firmware folder
    and use the online flashfile converter to get the flash commands
    add the fastboot reboot fastboot commands if you have a fasbootd device.

    Flash Option 2
    Install LMSA
    use the rescue option to download the current firmware for your device
    move the LMSA firmware to a different folder
    rename the Android 10 firmware folder to the same name as LMSA firmware.
    Move that folder to the LMSA download folder
    Use the rescue option to flash renamed firmware.

    There is no guarantee that either method will work, but it should.


    On the phone
    Toggle off "install updates" option in Dev Options

    Thanks a lot sd_shadow

    I tried Flash Option 2 using LMSA. Replaced all the Android 11 ROM files in the default download directory folder with official Android 10 ROM files, and then used the rescue option to flash the Android 10 files to the Moto g Power. Everything worked perfectly. I now have Android 10 back on my phone. I keep getting the notification that there is an Android 11 update available but just have to ignore this. Thanks again for your help.

    Gord
    4
    I unfortunately decided to upgrade my Moto G Power 2020 to Android 11 when the update was available and have had many issues most of which is that it is now very slow and battery drain is much higher. Have tried the many suggestions online to help, but none have worked. I found that Android 10 was good and stable. My question is, how can I downgrade my Moto G Power back to Android 10 easily? Can it be done with Moto's Rescue and Smart Assistant? This rescue utility seems to only want to keep the device on Android 11. Please provide step by step instructions how to do this. Thanks.
    Downgrading the android version with Moto firmware is always a risk.
    If you downgrade you need to disable updates, OTA updates could brick the device.

    First Unlock the bootloader

    Once the bootloader is unlocked, find your
    Software Channel, it will be like, Retail, RetUS, Verizon, MetroPCS...

    You can find your firmware here

    download. and Unzip it

    Check if your device uses fastbootd

    Flash option 1
    Find the flashfile.xml in the firmware folder
    and use the online flashfile converter to get the flash commands
    add the fastboot reboot fastboot commands if you have a fasbootd device.

    Flash Option 2
    Install LMSA
    use the rescue option to download the current firmware for your device
    move the LMSA firmware to a different folder
    rename the Android 10 firmware folder to the same name as LMSA firmware.
    Move that folder to the LMSA download folder
    Use the rescue option to flash renamed firmware.

    There is no guarantee that either method will work, but it should.


    On the phone
    Toggle off "install updates" option in Dev Options
    4
    Curious.
    I managed to downgrade, but can't re-lock the bootloader on Android 10 or else it throws this error and will not boot:View attachment 5375851

    However, when I reflashed Android 11 and re-locked the bootloader, it boots just fine, without any warnings.
    Something, the bootloader itself maybe, must be stuck on 11 and won't let me relock the bootloader when 10 is flashed.

    Since I need the bootloader locked so I can pass Playstore security, I guess I'm stuck on Android 11 :\
    Magisk Hide should be able to hide the bootloader status
    2
    Nothing ventured, nothing gained I guess. I was afraid of doing this whole thing because I'm your typical Problem User who tends to make things worse. Might as well go for root now that I've voided my warranty (not that I cared anyway).

    Flashed Android 10 and Magisk got me past playstore security. Everything's working as intended now.
    I'm quite surprised at how easy it was, since I had read that Google patched MagiskHide at hardware level sometime ago.

    THANK YOU VERY MUCH, sd_shadow.
    2
    Curious.
    I managed to downgrade, but can't re-lock the bootloader on Android 10 or else it throws this error and will not boot:
    IMG_20210801_223203163.jpg


    However, when I reflashed Android 11 and re-locked the bootloader, it boots just fine, without any warnings.
    Something, the bootloader itself maybe, must be stuck on 11 and won't let me relock the bootloader when 10 is flashed.

    Since I need the bootloader locked so I can pass Playstore security, I guess I'm stuck on Android 11 :\