Develop Bugs

FAILED (remote: flash_cmds error!)

ZE551ML - 4gb ram
I encountered this error when flashing thru fastboot.
My phone came from no fastboot/recovery then flash firmware with xFSTK, was able to get fastboot.
Tried commands like;
fastboot flash fastboot droidboot.img
fastboot flash recovery recovery.img
fastboot flash boot boot.img
fastboot flash system system.img
none of this works, getting " FAILED (remote: flash_cmds error!) " error.
Images are from WW_ZE551ML_2.15.40.13_20150506 official rom.
tried the clear cache command it just escape out of fastboot mode.
Also tried Asus Flash tool but getting failed error.
I hope someone could help.

Try flash the raw for .13 in flashtools ...5 minutes after you get "xfstki"- 'success!' but leave your cable in fone. Hopefully you see it flash to fone in that time. When you do see it flash leave it a while
Then start the flashtools ..if you see small green then red text in fastboot...restart flashtools when until it goes 'sky blue and bigger bold text' you will then get success there
P's, can you put all the links for fwr dnx and ifwi and raw etc here for me for .13 should I need these again ..my pc crashed ugh!

Thanks for your reply,
I'm at work right now.
But I'll try this later.

[SOLVED] FAILED (remote: flash_cmds error!)
This guide help me out..
http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256
Thanks XDA.

Thanks for that,glad you`re sorted out... pc restored now saved all the stuff for zenny , pheeeew !

@asus_abz May i know how did you get rid of "FAILED (remote: flash_cmds error!) " error."
I am trying to fix my hard bricked Zenfone 2 and the only thing that seems working is fastboot but i keep getting the above error message.
Thank you!

ulbx said:
@asus_abz May i know how did you get rid of "FAILED (remote: flash_cmds error!) " error."
I am trying to fix my hard bricked Zenfone 2 and the only thing that seems working is fastboot but i keep getting the above error message.
Thank you!
Click to expand...
Click to collapse
Same problem here. Anyone got any experience on this? Tried the guide above. Getting this error message in CMD:
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (12395 KB)...
OKAY [ 2.009s]
writing 'boot'...
FAILED (remote: flash_cmds error!
)
finished. total time: 4.831s
C:\adb>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (13967 KB)...
OKAY [ 2.082s]
writing 'recovery'...
FAILED (remote: flash_cmds error!
)
finished. total time: 4.917s
C:\adb>fastboot flash system system.img
error: cannot open 'system.img'
Asus Zenfone 2 (ZE551ML) /MM Z00A_WW_4.21.40.134

Workaround Solution to the dreaded remote: flash_cmds error!
Osaci said:
Same problem here. Anyone got any experience on this? Tried the guide above. Getting this error message in CMD:
C:\adb>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (12395 KB)...
OKAY [ 2.009s]
writing 'boot'...
FAILED (remote: flash_cmds error!
)
finished. total time: 4.831s
...
Click to expand...
Click to collapse
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
Updated 07-30-17: Some of the source file links were reported as broken and an alternative source was found by and provided courtesy of @beachbouy Thanks beachbouy!
||What the brick? How it all began (Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
In accordance with the guide, I was able to successfully use xfstk-downloader to get to the first checkpoint of success and arrived at the "not ..familiar ASUS screen but instead 4 color, just like some TV stations stop broadcasting on TV" Which means the device is working off of changes made with droidboot_dnx.img.POS_sign.bin, ifwi.bin, and dnx_fwr.bin
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
Any attempts to use an elevated CMD prompt using the
Code:
fastboot flash boot boot.img
^^^^^^^^^would resultin the remote:flash_cmds error!
|| `';~-=Resolving The Issue: Say Goodbye to flash_cmds error!=-~;'` ||​
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)​
Open (EXTRACT) the .RAW image file with Winrar, 7zip or equivalent and extract the contants of the .RAW image file to your ADB directory
Start device in bootloader and connected with fastboot and run the following commands
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Optionally (if you want to restore the full .RAW version)
Code:
fastboot flash ifwi ifwi.bin
Then seal the deal with
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
Code:
fastboot flash recovery twrp.img
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!

nucleare GOD BLESS YOU !!! you saved my fuc***d Zenfone 2 now i can send it back to ASUS becouse the camera keep on closing. Thank you

Marvelous stuff , this should be in a thread of its own for those with gpt trouble

nucleare said:
I was getting the exact same error after using ... to unbrick my Asus Zenfone 2 ZE551ML. ... Hit the Thanks if it does!
Click to expand...
Click to collapse
Thanks, you save me!

great guide OP
Sometimes you will need the following commands too
Make sure you type the correct name
Code:
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot flash token bom-token.bin

Hnk1 said:
Sometimes you will need the following commands too
Make sure you type the correct name
Code:
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot flash token bom-token.bin
Click to expand...
Click to collapse
Thanks @Hnk1 for pointing that out! To be sure, (and feel free to correct me if I'm wrong) if I'm not mistaken, the commands are going to depend if they're unbricking from a failed Lollipop to Marshmallow brick, or a Lollipop to Lollipop update brick, or essentially the last stable android file system build prior to the brick. And just to note in case someone finds this thread far in the future, the commands referenced the filenames that originated from the extracted downloads which had been linked to tutorials and were not changed. Therefore, if restoring using alternative RAW files, one would need to adjust the img/bin files accordingly.
~-`-`-`-`-~​
@Raul74 and @CrazyPhantomBR Thank you for the appreciation posts! It totally makes the time spent writing that all up worthwhile. And, I know that feeling of relief to see your device finally working again , so I am glad to have played a part in providing that experience for you guys

nucleare said:
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
||What the brick? How it all began(Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)
Start device in bootloader and connected with fastboot and run the following commands
Optionally (if you want to restore the full .RAW version)
Then seal the deal with
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!
Click to expand...
Click to collapse
You rocked buddy :good:
---------- Post added at 06:46 PM ---------- Previous post was at 06:45 PM ----------
Hnk1 said:
great guide OP
Sometimes you will need the following commands too
Make sure you type the correct name
Click to expand...
Click to collapse
U 2 buddy...great work

nucleare said:
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Click to expand...
Click to collapse
Where other post-xFSTK instructions left me hanging, this helped immensely. Thanks so much!

nucleare said:
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
||What the brick? How it all began (Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
In accordance with the guide, I was able to successfully use xfstk-downloader to get to the first checkpoint of success and arrived at the "not ..familiar ASUS screen but instead 4 color, just like some TV stations stop broadcasting on TV" Which means the device is working off of changes made with droidboot_dnx.img.POS_sign.bin, ifwi.bin, and dnx_fwr.bin
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
Any attempts to use an elevated CMD prompt using the
Code:
fastboot flash boot boot.img
^^^^^^^^^would resultin the remote:flash_cmds error!
|| `';~-=Resolving The Issue: Say Goodbye to flash_cmds error!=-~;'` ||​
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)​
Open (EXTACT) the .RAW image file with Winrar or equivalent and extract the contants of the .RAW image file to your ADB directory
Start device in bootloader and connected with fastboot and run the following commands
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Optionally (if you want to restore the full .RAW version)
Code:
fastboot flash ifwi ifwi.bin
Then seal the deal with
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
Code:
fastboot flash recovery twrp.img
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!
Click to expand...
Click to collapse
GOD bless you and your family for this tutorial )

nucleare said:
I was getting the exact same error after using xfstk-downloader_v1.7.0.exe to unbrick my Asus Zenfone 2 ZE551ML. Not seeing a reply to your post and after searching only to find unrelated posts. I took a whack at it and after a few hours, finally got my device to boot up again *insert Dr. Frankenstein's "It's Alive!" impersonation here*. My hypothesis was that it had to do with the partitioning being read incorrectly since it was the device reporting back issues with execution of the commands. In any case, here is how I got past it.
=--=-=-=-=-=-=-=-=--=--= If you want to go YOLO and skip to the answer, look for the HOT PINK
Legal Disclaimer: This is not a guide or tutorial. The following narrative may contain words or phrases commonly found in guides and tutorials found on forums.xda-developers.com such as "first," "then," and "make sure" which are used to portray the voice inside my head telling myself what to do, how to do it and what to expect and any references to taking steps as found in a guide or tutorial is purely coincidence. There are a number of important factors that could cause actual events or actual results of the typed narrative or therein to differ materially from those indicated by such set instructions.
Okay okay All kidding aside, you know the drill, im not responsible, dont hold me liable, try at your own risk and it may or may not work for you.
||What the brick? How it all began (Skippable) ||
The following events occurred on my Zenfone 2 : ZE551ML, originally with firmware LRX21V.WW-ASUS_Z00A-2.20.40.198_20160930_8756 which I foolishly and carelessly used the built-in system update to install the recently transferred firmware update file. after unlocking the bootloader and installing custom recovery, OEM software detected and offered to update for me so i then assumed, it probably detected that it would be compatible right? so i thought, WTH why not?....lol um yea, no. failed but I was having a YOLO moment and just had to do it anyways.
Lesson learned and happy to be alive to tell someone my story ;P.
|| Road to Recover and Encountering the "FAILED (remote: flash_cmds error!" (Skippable) ||
How I ultimately arrived at receiving this error (and for you to decide whether or not it may work for you):
My device was limp bricked where the screen didn't turn on and would only vibrate after holding the power button as an indication of life when beginning with the unbrick guide as previously posted by asus_abz within this thread (or otherwise found here http://forum.xda-developers.com/zenfone2/general/guide-brick-soft-hard-bricked-zenfone-2-t3284256)
In accordance with the guide, I was able to successfully use xfstk-downloader to get to the first checkpoint of success and arrived at the "not ..familiar ASUS screen but instead 4 color, just like some TV stations stop broadcasting on TV" Which means the device is working off of changes made with droidboot_dnx.img.POS_sign.bin, ifwi.bin, and dnx_fwr.bin
When attempting to use Asus FlashTool 1.0.0.14 to flash the .RAW image file, it would fail for reasons I fail to recall but otherwise...
Any attempts to use an elevated CMD prompt using the
Code:
fastboot flash boot boot.img
^^^^^^^^^would resultin the remote:flash_cmds error!
|| `';~-=Resolving The Issue: Say Goodbye to flash_cmds error!=-~;'` ||​
If you don't already have it, downlaod the .RAW format firmware for your device from the aforementioned guide at the Asus Flasher section
Otherwise ZE551ML2.20.40.194 or ZE550ML 2.20.40.155 (direct link from guide but the one for 550 is broken)​
Open (EXTACT) the .RAW image file with Winrar or equivalent and extract the contants of the .RAW image file to your ADB directory
Start device in bootloader and connected with fastboot and run the following commands
Code:
fastboot oem erase_osip_header
fastboot oem start_partitioning
fastboot flash /tmp/partition.tbl partition.tbl
fastboot oem partition /tmp/partition.tbl
fastboot erase system
fastboot erase APD
fastboot erase ADF
fastboot erase cache
fastboot oem stop_partitioning
fastboot flash fastboot droidboot_sign.bin
Optionally (if you want to restore the full .RAW version)
Code:
fastboot flash ifwi ifwi.bin
Then seal the deal with
Code:
fastboot flash recovery recovery_sign.bin
fastboot format system
fastboot flash splashscreen splash_sign.bin
fastboot flash system system.img
fastboot flash boot boot_sign.bin
fastboot reboot
Alternatively, you can flash your own recovery and whatnot because by now you should be able to successfully run the flash command for those partitions, but I would suggest flashing back to full stock first and then flash to custom. Personally, I flashed everything from the .RAW firmware except for recovery
Code:
fastboot flash recovery twrp.img
After the device restarts it might go through the updating android apps screen so expect a longer than usual boot up.
Optionally, you can include "fastboot erase data" if you needed to have a clean reinstall (such as coming from a different version of android) but I didn't bother because I didn't ever successsfully load another ROM and for me, by not wiping data, I was able to have it restored back to how I had it before I made any experimenting with restoring my backup from before the shaninagans.
I hope this helps anyone who may have had the same issue. Hit the Thanks if it does!
Click to expand...
Click to collapse
This Must ba a Sticky Solved Topic Not Tried yet but All Text Blog Telling my Situation
Edit:14.02.2017 GOD bless you Man Working Like a Magic Pls Mods Stick This Solution...

thank you to all for the kind words and more glad to hear it helped you. Perhaps I should rewrite the "tutorial" in a more 'toned down' and chronologically-and-well-laid out manner to be considered for sticky
EDIT: **that is of course, if the MODs see it as a worthwhile effort/meaningful contribution since this can be seen /regarded as a more lengthy answer to a troubleshooting question.

To clarify additional commands:
Hnk1 said:
Sometimes you will need the following commands too
Make sure you type the correct name
Code:
fastboot flash dnx dnx_fwr_ann_a0-mofd_v1-ze551ml.bin
fastboot flash ifwi ifwi_ann_a0-mofd_v1-ze551ml.bin
fastboot flash fastboot droidboot.img
fastboot flash splashscreen splashscreen_ze551ml.img
fastboot flash token bom-token.bin
Click to expand...
Click to collapse
For the future reference of any who stumble upon this page in the future, the aforementioned commands from @Hnk1 will apply to you if you did not use, or did not successfully flash already with, xfstk-downloader_v1.x.x to previously restore from no loading screen type brick to USB icon screen boot-loop type brick and more specifically stands in as an alternative method for flashing ifwi/dnx_fwr/droidboot/OSP as outlined in the program's (xFSTK's) Standard Operating Procedure Documentation PDF excerpt, which is commonly found with the filename "ZE550ML_ZE551ML_xFSTK_SOP.pdf" and included in many, if not all, current unbrick Zenfone methodologies.

Man, you are awesome!, i lost two fk.. days trying to do this with the asus flashtool, but no sucess, with your tip worked perfecly!.
I'm saving it offline in case somethink like it happens again, (probably will, since i love testing roms).

Rooting Motorola G6 Play gone wrong

Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.img picture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke

Hi Sven,
This isn't going to be the most advanced reply, as I'm not very experienced with this stuff either, but it seems you have accidentally flashed your twrp image to 'boot', wherever that is, which is why the phone isn't able to boot to system.
Can you still boot into bootloader and recovery (twrp)?
If so, then I'd suggest using fastboot to flash a sock or custom ROM. I'm not sure exactly which one though, you have basically the same model as me and that seems to use the JETER ROMS a list of which are over here (can't post links yet, so you will just have to search on mirrors . lolnet . com /firmware/moto/jeter/official/ or remove the spaces
I seem to have somehow lost the partitions on mine, but will start a new thread question about that.

Sven Onderbeke said:
Hi everyone,
I bought a Motorola G6 play model XT1922-3 type 374B and wanted root acces on this device.
So I started by succesfully unlocking my bootloader using the following tutorial.
After this a started tried to root the device using this tutorial.
This tutorial doesn't link to boot images anymore so I was able to find the moto-g6-play-jeter-patched-twrp.img somewhere else.
I did the following things:
- reboot to bootloader [Succesfull]
- fastboot boot moto-g6-play-jeter-patched-twrp.img [Unsuccesfull]
The device did boot the twrp image but I was unable to interact with it in any way. I couldn't swipe or press buttons.
I made a short video to show this.
I wanted to retry the whole thing so I did reboot to bootloader but then I accidently entered the following command:
fastboot flash boot moto-g6-play-jeter-patched-twrp.imgpicture of command prompt
After this I wasn't able to normally boot my device. When I try to do so the screen goes black and says n/a in the left corner.
Please does anyone know how I could either be able to boot my normal stock rom again or to have a rooted rom?
Kind regards Sven Onderbeke
Click to expand...
Click to collapse
Just flash a stock boot.img to boot. Then just flash TWRP to recovery. In TWRP, format data. Type yes. Then reboot recovery. Then Use TWRP to flash magisk. Done.

Hi again Sven,
I just wanted to let you know that I just downloaded the following RETAIL ROM
ALJETER_RETAIL_9.0_PPPS29.55-35-1_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
and used the following fastboot commands, one at a time.
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash modem NON-HLOS.bin
fastboot flash fsg fsg.mbn
fastboot flash dsp adspso.bin
fastboot flash boot boot.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash oem oem.img
fastboot flash vendor vendor.img
fastboot erase carrier
fastboot erase userdata
fastboot erase DDR
fastboot flash logo logo.bin
fastboot reboot
Which rebooted into bootloader so pressed "start" and all booted fine now. It looks like we have the same device, so hopefully that will work for you too.

How to revert Moto G5 XT1670 to stock rom

Hello, how are you? My Name Is Cristian and I'm from Argentina.
I've had a Moto G5 for a while and a lot of custom roms were installed on it. However, there were many problems in the process. The roms had bugs, performance issues, and some didn't even boot.
So i made the decision to go back to the factory rom and close the bootloader forever. But it couldn't. Something prevented it. Something was causing the phone to not start properly.
Therefore, after doing so many laps, i was able to do the whole process.
And today i publish this topic so that you can do it too. I hope you can come out triumphant in the process just like me. Have lucky!
1) The first thing you should do is download Rescue & Smart assistant. Install on your pc and create account (if you not) or login in.
Code:
https://support.lenovo.com/es/es/downloads/DS101291
2) You will need to find the official firmware of your device. Search for the exact device SKU (model of your phone) and exact region. For example the SKU of my device is XT1670 the region is RETAR (from Argentina). If you are from United States (and try to install RETAR) Rescue & Smart assistant will not recognize the SKU of your device, and will not be able to continue.
Find the exact firmware corresponding to your mobile phone.
Code:
https://mirrors.lolinet.com/firmware/moto/cedric/official/
Unzip the rom in the place that you prefer.
3) Now put your device in bootloader mode and execute the following commands (ignoring any errors in the process)
Code:
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash dsp adspso.bin
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash system system.img_sparsechunk.5
fastboot flash system system.img_sparsechunk.6
fastboot flash system system.img_sparsechunk.7
fastboot flash system system.img_sparsechunk.8
fastboot erase cache
fastboot erase userdata
fastboot reboot
4) Once the above process is finished, start your phone normally. Go to the developer options and activate usb debugging. Plug the phone into PC.
Open "Rescue & Smart assistant" and accept usb debugging on your phone. The app installs some control app, dont worry.
Go to Rescue & Smart assistant and select "Rescue". The program will recognize your phone's SKU if you downloaded the correct firmware. Otherwise, if a wrong sign appears, you will have to repeat step 2 and 3 with the correct firmware.
Click on "Rescue now" and the program will download the firmware corresponding to your phone. After this, the firmware installation will begin.
Why do all this process?
The Rescue & Smart app is official from Motorola. When the official firmware is installed, the signed firmware files are also installed with it. The firmware is official because is delivered directly by Motorola, specifically for your mobile phone, and not by unofficial sites.
5) Hey, wait! the bootloader needs to be blocked. True.
Go to C:\ProgramData\LMSA\Download\RomFiles and you will find there the official rom downloaded by "Rescue & Smart". This rom is unique, signed and official. Only for your phone, only for its hardware. Do not lose it. It will save your ass from many inconveniences, if one day you want to continue experimenting with your phone.
Copy the whole directory in other site and open cmd in it. Now shutdown your phone and start it in bootloader mode.
Now put these commands (ignoring bla bla bla errors):
Code:
fastboot oem lock
fastboot oem lock
fastboot flash oem oem.img
fastboot flash system system.img_sparsechunk.0
fastboot flash system system.img_sparsechunk.1
fastboot flash system system.img_sparsechunk.2
fastboot flash system system.img_sparsechunk.3
fastboot flash system system.img_sparsechunk.4
fastboot flash boot boot.img
fastboot oem lock
And that's it. Your mobile phone is now official and with its bootloader locked. almost factory-made.
So thank you for reading all this and I hope the information has served you a lot. Any questions about it (about this) do not hesitate to consult.

Great post and thanks for taking the time to post it :good:
For people who might struggle with this I've used Moto Auto Flash Tool v8.2 By Jamesjerss.rar with great success,
https://www.ytechb.com/moto-auto-flash-tool/
Takes a lot of the hard work out of it :good:

R1ffR4ff said:
Great post and thanks for taking the time to post it :good:
For people who might struggle with this I've used Moto Auto Flash Tool v8.2 By Jamesjerss.rar with great success,
https://www.ytechb.com/moto-auto-flash-tool/
Takes a lot of the hard work out of it :good:
Click to expand...
Click to collapse
The reason i made this post was mainly because a lot of people have problems with unsigned firmware and cannot follow normal recovery processes. However, I will consider this application for future experiments. It seems to be an application that already has the commands prepared, so there are no errors. The problem is that it does not offer the official firmware (from Motorola) directly for the specific device. Anyway it is good not to make mistakes in the commands.
Ty.

He.Art said:
The reason i made this post was mainly because a lot of people have problems with unsigned firmware and cannot follow normal recovery processes. However, I will consider this application for future experiments. It seems to be an application that already has the commands prepared, so there are no errors. The problem is that it does not offer the official firmware (from Motorola) directly for the specific device. Anyway it is good not to make mistakes in the commands.
Ty.
Click to expand...
Click to collapse
It's a great little program that I had to use Yesterday on a Moto G3 as the normal ADB way as per your post wouldn't work for whatever reason and I've used ADB loads
I was my own fault on that phone as I,"Soft Bricked" it using the latest version Magisk uninstall option so NEVER use this option in Magisk. I returned the phone to Stock and then upgraded it to my favourite Custom roms

Question How to re flash stock from brick, MSM not recognizing 9 pro

So I am trying to reflash oxygen os because through a series of wacky circumstance I bricked the 9 pro. It seems like the b slot got messed up and there is nothing I can do. I am trying to reflash using MSM however, I now get stuck on "Waiting for Device". I don't think I am properly in edl mode. I tried installing the qualcom driver however it seems like it stil doesn't work. What can I do to unbrick this? Sorry if this is a newbie question, I am newer to Oneplus.

Alright second update: Got fastboot to work with windows, it was an error with my windows in particular. The issue now is I can't get the phone in edl mode. It just goes to fastboot when I try to boot into it.
Update 3: So I think what happened is one of the slots got locked. This is from flashing with fastboot. I'm guessing this is causing it to not boot into edl as well.

I had the same problem.
In fastboot "fastboot -w" this deleted everything. Then via fastboot:
After that, begin typing in the following commands in the CMD window, one at a time:
fastboot flash boot boot.img
fastboot flash cpucp cpucp.img
fastboot flash dtbo dtbo.img
fastboot flash modem modem.img
fastboot flash oplusstanvbk oplusstanvbk.img
fastboot flash oplus_sec oplus_sec.img
fastboot flash qweslicstore qweslicstore.img
fastboot flash shrm shrm.img
fastboot flash splash splash.img
fastboot flash vbmeta vbmeta.img
fastboot flash vbmeta_vendor vbmeta_vendor.img
fastboot flash vbmeta_system vbmeta_system.img
fastboot flash vendor_boot vendor_boot.img
fastboot flash vm-bootsys vm-bootsys.img
That was the first part.
Then "fastboot reboot bootloader".
Here, switch off the device without USB cable. Wait one minute, then hold Volume - & Volume + for approx. 40 seconds and then plug in the USB cable with the keys pressed. The MSM Tools should have started.
This is how it worked for me.

my phone had a black screen and it wouldnt turn on nor do anything other than turn on and off every 10 seconds when plugged in (pc would make the hardware connected and disconnected sounds and qualcom device would show on DM) . THIS IS THE ONLY thing that worked
Follow the first post and it should be good 2 go.

Reverting to Stock

I've been disappointed with some of the firmware here, like Lineage and Arrow. Havoc has been my favorite, but when we transitioned from Havoc Android 10 (3.*) to Android 11 (4.*) I have lost LTE every morning, which means no texts, no data, no phone calls. I have to power down and up and who knows when I'd lose LTE again.
Also with TWRP I could not slide the unock, and trying to select files the screen mapping is all wrong, meaning I'd touch a file at the bottom and a file toward the top would be selected. I don't know why the problems were because no one has ever been able to communicate the structure and framework of Android coherently. It seems that most just know parts of it intuitively, not the whole intellectually.
So I have to resort to Stock. I thought maybe installing Stock then Havoc 4.8 would solve the LTE problem, but when doing that Havoc's boot just circles around forever.
So without further adieu here is how to install Stock on your Moto G Power. Mine is US T-Mobile on an XT2041-4.
Get the firmware here: https://mirrors.lolinet.com/firmware/moto/sofia/official/
I hit RETUS and RETUS_10 for Retail US Android 10. If you have a different carrier or nation try and decipher which is right for you. Use 10 as Beetle says below. (as of Jan, 2022, Havoc 4.12)
Unzip this file into its own directory and you will get a series of images and .xml files. Boot your phone into fastboot mode by turning it off, then hold {VolDown}{Power} at the same time to go into fastboot mode. In this case you do -not- then reboot into fastbootd mode! Just leave it like this and connect to your computer.
Code:
# fastboot devices
... should give you something like
Code:
ZY227VX6NG fastboot
Good, your computer sees the phone.
Go into the firmware directory. A key file here is flashfile.xml. This tells you exactly how these image files must be applied to the phone and in what order. I'll show below the files and procedure for my phone, but yours may be different so refer to that flashfile for your firmware.
The first file to flash is important. It sets up the partitions on the phone properly:
Code:
# fastboot flash partition gpt.bin
Now just work your way down flashfile. Here's mine:
Code:
# fastboot flash bootloader bootloader.img
# fastboot flash vbmeta vbmeta.img
# fastboot flash radio radio.img
# fastboot flash bluetooth BTFM.bin
# fastboot flash dsp dspso.bin
# fastboot flash logo logo.bin
# fastboot flash boot boot.img
# fastboot flash dtbo dtbo.img
# fastboot flash recovery recovery.img
# fastboot flash super super.img_sparsechunk.0
# fastboot flash super super.img_sparsechunk.1
# fastboot flash super super.img_sparsechunk.2
# fastboot flash super super.img_sparsechunk.3
# fastboot flash super super.img_sparsechunk.4
# fastboot flash super super.img_sparsechunk.5
# fastboot flash super super.img_sparsechunk.6
# fastboot flash super super.img_sparsechunk.7
# fastboot flash super super.img_sparsechunk.8
# fastboot flash super super.img_sparsechunk.9
# fastboot flash super super.img_sparsechunk.10
# fastboot flash super super.img_sparsechunk.11
# fastboot flash super super.img_sparsechunk.12
# fastboot flash super super.img_sparsechunk.13
# fastboot flash super super.img_sparsechunk.14
# fastboot flash super super.img_sparsechunk.15
# fastboot erase carrier
# fastboot erase userdata
# fastboot erase metadata
# fastboot erase ddr
# fastboot oem fb_mode_clear
And that's it. Reboot. It will take a while the first time so don't interrupt it. You're back to stock.

If you were trying to flash havoc over android 11 firmware, it wont work. These roms need android 10 as a base.

Ah, that explains it. I think Havoc is the best, but 4.6 and 4.8 reliably drop LTE for me mornings. It's caused business problems.
I now find that it's impossible to tear G**gle out of Stock, so that's out for me. Maybe Arrow or something.

What carrier do you have? I'm getting ready to put maybe Havoc or Linage on this phone, but need to know what to watch out for.
It seems to be like Android 11 is a common denominator in a lot of the issues I've seen people having. That's why I have no intention of even moving to a custom rom based on 11 for a good while. I'll be staying at Lineage 17 or Havoc 3 until I have no other choice. There's nothing in 11 I need or want, and that will probably be true for 12 and 13 and so on. As for de-googling Android, that's likely going to just get harder and harder with each version.

I seem to be the only one having problems with Android 11 afaict. Haven't seen anyone else posting issues. Decided it's something about my phone, but laying down 11 stock reset everything. I just can't run Havoc anymore.
I highly recommend Havoc 3.*.
I wonder whether laying down Android 10 would fix my issues with Havoc 4.*?

I went back to stock for the same reason as OP. As far as de-googling, it's a chore to get it to a point where I feel a bit comfortable turning wi-fi on, but I'm not very comfortable. Basically I disable all google stuff, including the play store, prevent the google apps installed post-setup, remove permissions from play services, turn off networking for it and everything else, go through settings to disable 'functions' , I use the keepass2android app's keyboard, install a different sms app, keep contacts to device, and firewall everything - I don't allow much networking functionality at all. Of course, I'm rooted., I also use app manager to disable trackers and disable "0" which is 'rough' location for all apps, system included - I eneble it for weather. I use aurora and f-droid for apps, but, mostly just reinstall from dumps. Also, I don't use a lot of apps and for my feng shui, the device (and my edge) works well. I'm likely leaving out a bunch of little tweaks that I do, apologies.
I use nextcloud, adaway, sms backup and restore, acalendar+, fx, firefox focus or bromite, pi-hole is on my LAN. ON my edge, with lineage (17) and tweaked 'my way', I feel reasonably safe. On my g power with stock, tweaked, I feel a little naked. Whereas I'm not shy, I am private. My g power mostly stays turned off kept in a drawer in my office.

I've been running CrDroid (google-free) v7.7 (android 11) with good results. I have data turned off on this screenshot, but have used it in limited amounts (my current plan allows only 1G per month). BTW, I'm on Red Pocket GSMA (ATT).

So I've cleared the decks by laying down Stock Android 10, then installing Havoc 4.8.
If I lose data tomorrow morning I will have to use another firmware, although I'm confident.
+1 on aCalendar+ and its beautiful widget, and add CalendarNotifications for nice popup.
I use SuperBackups to back up apps and call logs to SD card, and also AppBackupRestore just to be sure. Everything on the SD card was preserved during all these latest calisthenics, thankfully, including after the fastboot erases.
I've set up a Davical server at home for calendar and contacts sync, and on the phone DAVx5 to communicate with it. It's a faff to set up, but such a joy to know my calendars and contacts are always synced with home, once set up. (Thunderbird+Lightning for now, maybe soon Kontact)
The phone does all internet access through a WireGuard tunnel to home WG server virtual machine (interface: inWG), and then out the outWG interface to come out appearing that I'm in Switzerland or Spain, using AzireVPN service.
For Android firewall I use the fine AFWall+ and its little on/off widget, and for apps I always try F-Droid first then APKPure. Browser is Vivaldi. To transfer files with LAN I connect with wifi then use SSHDroid as SSH server on the phone and sshfs on the server to mount the phone. (SSHDroid is worrisomely getting old)
Also I use Nova as desktop renderer. I have 5 phone desktops and it takes me a day to rebuild everything with the standard Havoc desktop (Shady Launcher), no offense SkullShady. Nova lets you back up and restore all settings, including complete desktops setup, which is such a pleasure.
G**gle-less. G**gle-free. Sans G**gle. In my Postfix server I kick back all gmail messages with, "THANK YOU FOR SENDING THIS, BUT GMAIL IS CONSIDERED A SECURITY PROBLEM. PLEASE RE-SEND FROM ANOTHER ACCOUNT."

Good sign - I have data this morning.

Deleted. Thank you.

Worked like a charm. Followed this guide, then ran fastboot oem lock, to prepare a phone to give away. Thank you.
I extracted the files straight to my platform-tools folder to simplify.

Quantumstate said:
Good sign - I have data this morning.
Click to expand...
Click to collapse
Remember me? I still have my Sofia, but it's running stock A11 and Nova Launcher 6.2.9 rather that 7x which screws with my Android widgets. So, I've set the Play Store not to auto update apps to keep 6.2.9. This setup is OK, but I'd rather root it, install TWRP, and an updateable/upgradeable custom ROM. Can you offer some step-by-step guidance?
Thanks

jhford said:
Remember me? I still have my Sofia, but it's running stock A11 and Nova Launcher 6.2.9 rather that 7x which screws with my Android widgets. So, I've set the Play Store not to auto update apps to keep 6.2.9. This setup is OK, but I'd rather root it, install TWRP, and an updateable/upgradeable custom ROM. Can you offer some step-by-step guidance?
Thanks
Click to expand...
Click to collapse
Sure I remember you. I just did an install of beetle84's last version of Havoc as above, and as per the directions in his thread, it's worked ever since. Only glitch is I lose mobile data every morning, but just power down and reboot.
I'm afraid of this version as I tried and tried but could not make it work. Phone was down for days.

Beetle84 said:
If you were trying to flash havoc over android 11 firmware, it wont work. These roms need android 10 as a base.
Click to expand...
Click to collapse
I'm researching if I can flash XT2041-4_SOFIA_RETUS_10_QPMS30.80-109-5_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.zip onto my unrooted Android 11 phone, an XT2041-4 that was Android 10 but now Android 11.
I'm not familiar with havoc so I'm curious what you mean. Is that image flashable to my phone or am I wanting to flash havoc over android 11 firmware?

I followed the steps in the oP and bricked my device. I didn't unlock the bootloader so if you follow the tutorial above be sure to unlock the bootloader before wiping the partition.
If anyone knows how to recover from that point I'd appreciate any help. I have the unlock code but I didn't enable unlocking the bootloader before wiping the partition as I didn't know I needed to do that so I hosed myself.

powershift said:
I followed the steps in the oP and bricked my device. I didn't unlock the bootloader so if you follow the tutorial above be sure to unlock the bootloader before wiping the partition.
If anyone knows how to recover from that point I'd appreciate any help. I have the unlock code but I didn't enable unlocking the bootloader before wiping the partition as I didn't know I needed to do that so I hosed myself.
Click to expand...
Click to collapse
Are you still able to boot to the bootloader menu using hardware keys? You should be able to continue unlocking it regardless of what you wiped. Either way that shouldn't stop you from being able to flash the stock rom.
What exactly are you stuck on now?

TaZeR369 said:
Are you still able to boot to the bootloader menu using hardware keys? You should be able to continue unlocking it regardless of what you wiped. Either way that shouldn't stop you from being able to flash the stock rom.
What exactly are you stuck on now?
Click to expand...
Click to collapse
It wouldn't unlock in fastboot. What I did was I downloaded Android 11 and flashed it, then did the boot loader unlock.
But when applying stock Android 10 w/out errors during the flash, on boot the blue Motorola splash screen shows, it acts like it is booting then it reboots and the blue screen goes away and comes back. It will do that boot loop all day. I had to revert back to Android 11, but at least the phone boots now although I'd still like to get Android 10 on there as I'm not at all a fan of V11.

powershift said:
It wouldn't unlock in fastboot. What I did was I downloaded Android 11 and flashed it, then did the boot loader unlock.
But when applying stock Android 10 w/out errors during the flash, on boot the blue Motorola splash screen shows, it acts like it is booting then it reboots and the blue screen goes away and comes back. It will do that boot loop all day. I had to revert back to Android 11, but at least the phone boots now although I'd still like to get Android 10 on there as I'm not at all a fan of V11.
Click to expand...
Click to collapse
I think maybe you should try to flash stock android 10 image again. It's the kind of error that happened to me when I missed a step or forgot a command and looking over your post I think there is something missing or added that shouldn't be there. Also don't flash anything like magisk or twrp along with it, wait until the first boot for anything more.
Heres whats always worked for me (same model phone):
fastboot getvar max-sparse-size
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash bluetooth BTFM.bin
fastboot flash dsp dspso.bin
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase carrier
fastboot erase userdata
fastboot erase metadata
fastboot erase ddr
fastboot oem fb_mode_clear
fastboot reboot

TaZeR369 said:
I think maybe you should try to flash stock android 10 image again. It's the kind of error that happened to me when I missed a step or forgot a command and looking over your post I think there is something missing or added that shouldn't be there. Also don't flash anything like magisk or twrp along with it, wait until the first boot for anything more.
Heres whats always worked for me (same model phone):
fastboot oem fb_mode_set
fastboot flash partition gpt.bin
fastboot flash bootloader bootloader.img
fastboot flash vbmeta vbmeta.img
fastboot flash radio radio.img
fastboot flash logo logo.bin
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash recovery recovery.img
fastboot flash super super.img_sparsechunk.0
fastboot flash super super.img_sparsechunk.1
fastboot flash super super.img_sparsechunk.2
fastboot flash super super.img_sparsechunk.3
fastboot flash super super.img_sparsechunk.4
fastboot flash super super.img_sparsechunk.5
fastboot flash super super.img_sparsechunk.6
fastboot flash super super.img_sparsechunk.7
fastboot flash super super.img_sparsechunk.8
fastboot flash super super.img_sparsechunk.9
fastboot flash super super.img_sparsechunk.10
fastboot flash super super.img_sparsechunk.11
fastboot flash super super.img_sparsechunk.12
fastboot flash super super.img_sparsechunk.13
fastboot flash super super.img_sparsechunk.14
fastboot flash super super.img_sparsechunk.15
fastboot erase userdata
fastboot erase ddr
fastboot flash dsp dspso.bin
fastboot oem fb_mode_clear
fastboot reboot
Click to expand...
Click to collapse
That is what my script looks like with one exception, I can't run the flash bootloader bootloader.img successfully because it fails validation. All other steps succeed. Did you have Android 11 bootloader on there and put the Android 10 bootloader back?
In addition to those steps, I tried fastboot getvar max-sparse-size before all others and still no joy. I think the Android 11 bootloader doesn't boot Android 10 and I don't know how to reflash it back to the old bootloader even while unlocked.
Code:
[email protected]:~/android$ sudo /home/anon/android/platform-tools/fastboot oem unlock 2T4ETJZNOSHSA324GL6G
(bootloader) Bootloader is unlocked!
OKAY [ 15.676s]
Finished. Total time: 15.676s
[email protected]:~/android$
[email protected]:~/android/moto_stock_android10$ sudo /home/anon/android/platform-tools/fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.557s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/moto_stock_android10$

powershift said:
That is what my script looks like with one exception, I can't run the flash bootloader bootloader.img successfully because it fails validation. All other steps succeed. Did you have Android 11 bootloader on there and put the Android 10 bootloader back?
In addition to those steps, I tried fastboot getvar max-sparse-size before all others and still no joy. I think the Android 11 bootloader doesn't boot Android 10 and I don't know how to reflash it back to the old bootloader even while unlocked.
Code:
[email protected]:~/android$ sudo /home/anon/android/platform-tools/fastboot oem unlock 2T4ETJZNOSHSA324GL6G
(bootloader) Bootloader is unlocked!
OKAY [ 15.676s]
Finished. Total time: 15.676s
[email protected]:~/android$
[email protected]:~/android/moto_stock_android10$ sudo /home/anon/android/platform-tools/fastboot flash bootloader bootloader.img
Sending 'bootloader' (14204 KB) OKAY [ 0.557s]
Writing 'bootloader' (bootloader) Validating 'bootloader.default.xml'
(bootloader) Preflash validation failed
(bootloader) Preflash validation failed
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote: '')
fastboot: error: Command failed
[email protected]:~/android/moto_stock_android10$
Click to expand...
Click to collapse
It does flash back, I've done it a few times, I didn't have any difficulty. You said you unlocked the bootloader before, but you seem to be entering the code to unlock it again each time you try to flash or? Because once its unlocked you shouldn't be needing to do oem unlock anymore, unless you've locked it again. Also what distro are you using and adb package?
There may be some verification problem here if something is not fully unlocked for some reason, so just to clarify the first time you flashed android 10 over 11 you also had the bootloader failed error, or is this now on the second try?
Perhaps if all else fails can try to change to the next active slot like b, and try to flash there in case something maybe the partition table got screwed up somehow (at the start) "fastboot set_active b", cold booting with a twrp image may be able to fix it in that case.
I mean unless there is some kind of new protection in the lastest versions of 11 that i dont know about...? Maybe as a last resort reflash android 11 but the first version after 10, and then try to downgrade from that? I dunno man sorry... some stuff to think about...