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).

Pixel C - fastboot unsupported command

Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !

Did you unlock your device first with "fastboot oem unlock"?

redukt said:
Did you unlock your device first with "fastboot oem unlock"?
Click to expand...
Click to collapse
Yes i did this before, i was running on Remix OS

I don't know if this is of relevance but there were new fastboot commands introduced from Android M (?) and I have recollection about "partial unlock" - two flags required to be set and if only one was set it could be reported that the bootloader was unlocked but fastboot saw it as locked. Above may be totally wrong.
Here's the difference between old and current fastboot commands. Note the new lock/unlock commands
Code:
************************ OLD **************************************
commands:
update <filename> reflash device from update.zip
flashall flash boot, system, vendor and if found,
recovery
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format[:[<fs type>][:[<size>]] <partition> format a flash partition.
Can override the fs type and/or
size the bootloader reports.
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> [ <second> ] ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ] create bootimage and
flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
************************ NEW **************************************
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot
usage: fastboot [ <option> ] <command>
commands:
update <filename> Reflash device from update.zip.
Sets the flashed slot as active.
flashall Flash boot, system, vendor, and --
if found -- recovery. If the device
supports slots, the slot that has
been flashed to is set as active.
Secondary images may be flashed to
an inactive slot.
flash <partition> [ <filename> ] Write a file to a flash partition.
flashing lock Locks the device. Prevents flashing.
flashing unlock Unlocks the device. Allows flashing
any partition except
bootloader-related partitions.
flashing lock_critical Prevents flashing bootloader-related
partitions.
flashing unlock_critical Enables flashing bootloader-related
partitions.
flashing get_unlock_ability Queries bootloader to see if the
device is unlocked.
flashing get_unlock_bootloader_nonce Queries the bootloader to get the
unlock nonce.
flashing unlock_bootloader <request> Issue unlock bootloader using request.
flashing lock_bootloader Locks the bootloader to prevent
bootloader version rollback.
erase <partition> Erase a flash partition.
format[:[<fs type>][:[<size>]] <partition>
Format a flash partition. Can
override the fs type and/or size
the bootloader reports.
getvar <variable> Display a bootloader variable.
set_active <slot> Sets the active slot. If slots are
not supported, this does nothing.
boot <kernel> [ <ramdisk> [ <second> ] ] Download and boot kernel.
flash:raw boot <kernel> [ <ramdisk> [ <second> ] ]
Create bootimage and flash it.
devices [-l] List all connected devices [with
device paths].
continue Continue with autoboot.
reboot [bootloader] Reboot device [into bootloader].
reboot-bootloader Reboot device into bootloader.
help Show this help message.

-Yazh- said:
Hi everyone ! (I apologyze for my english)
I cant flash anything on my Pixel C because of this:
C:\Users\ykant\Desktop\Minimal ADB and Fastboot>fastboot flash recovery TWRP_dragon_3.0.2-23.img
target reported max download size of 268435456 bytes
erasing 'recovery'...
FAILED (remote: unsupported command)
finished. total time: -0.000s
Click to expand...
Click to collapse
No system to boot on and my TWRP is wiped !!
--> Cant do this:
fwtool vbnv write dev_boot_fastboot_full_cap 1
Click to expand...
Click to collapse
Is my pixel C bricked now ?
regards !
Click to expand...
Click to collapse
Hi, I'm just wondering if you were able to fix your tablet. I ran into the same problem as you here and am not able to find a solution to it.

Hi !!
Sorry for bad news, but i didn't found any solution since my Pixel C was bricked. Maybe there is a solution, but I dropped it before finding it.
I hope you find something to fix it !

@viii_xvi Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html

peterk-1 said:
Are you using "Minimal ADB and Fastboot" as shown in the post you quoted by -Yazh- ? The current (?) version that I can find is 1.4.3 and that looks to be "2015".
Click to expand...
Click to collapse
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
peterk-1 said:
For the current versions of adb and fastboot and the revision history, 12 since October 2016, see https://developer.android.com/studio/releases/platform-tools.html
Click to expand...
Click to collapse
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?

viii_xvi said:
No. I used the 15 second ADB and Fastboot installer. I'm pretty sure it works fine as I can use fastboot commands.
I don't really know what to do with the files found in the zip. If I'm doing it wrong, can you tell me what I should be doing?
Click to expand...
Click to collapse
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.

peterk-1 said:
There are Youtube videos on installing Android Platform Tools and a web search for installing Android Platform Tools with your o/s will find many hits. You need to know you are installing just the platform tools - some of the guides assume you are installing or have installed the full Android Software Development Kit (SDK).
Assuming you are using Windows then the simplest method is to copy the contents of the zip file into the current location of your "15 second" files. This ensures that you can run the new version of fastboot with the folder path you have used previously. In file manager "find" fastboot.exe and that will give you the folder to unzip ALL of the platform tools files. You will know if you have done it correctly if you get requests to overwrite existing files when you unzip the files.
Click to expand...
Click to collapse
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
fastboot: usage: no command
Click to expand...
Click to collapse

viii_xvi said:
I've followed the instructions so I'm confident I did it correctly. Despite this, nothing has improved. I still can't flash the stock ROM or a custom recovery in fastboot.
What I've noticed from updating the fastboot version are some new commands I found when I entered "fastboot -h"
Code:
fastboot -h
commands:
reboot [bootloader|emergency]
stage <infile>
get_staged <outfile>
options:
--skip-secondary
--skip-reboot
--disable-verity
--disable-verification
--unbuffered
--version
From what I've tried, all the commands in options returns
Click to expand...
Click to collapse
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.

rhmanoa said:
Hi, Did you tried to flash with the oldest stock rom of the pixel C ? Because it uses older version of fastboot so maybe it will work. I has also the same problem as you but hopefully twrp still worked so i could flash another system image.
Click to expand...
Click to collapse
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.

viii_xvi said:
I have now tried to flash the earliest factory image and am disappointed to say the bootloader did not flash and so I wasn't able to complete the flashing.
I don't think the problem is the fastboot version. It may be the bootloader itself. I've read someone describe this problem as "Broken fastboot (bootloader) security." I think the problem is that, when unlocked, the bootloader would return the same messages as if it was locked. The security of the bootloader still thinks it's locked and not allow flashing of any images. Also that locking and reunlocking does not improve the situation. This would explain why, when bootloader is unlocked, I get "remote: unsupported command" and "remote: image verification failed", the same as when I try the same commands when the bootloader is locked.
Click to expand...
Click to collapse
Just bought today, same issue, have you solved it?

mansonstein said:
Just bought today, same issue, have you solved it?
Click to expand...
Click to collapse
No, I didn't manage to fix it.

did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command

richardwia said:
did you found a solution yet？
I got a same problem,cant flash anything but ordinary using.
I got the problem caused by flashed twrp3.2.3,cant get into system,just always get into twrp.
cant flash any official firmware with "flash-all.bat",no matter which platform tool or firmware.but the twrp were installed before can flash anything.
finally,I flashed newest OTA firmware,then device can be booted. but got the unsupported command
Click to expand...
Click to collapse
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.

viii_xvi said:
I'm assuming you have the latest version of TWRP installed. IIRC, there should be "Fix Fastboot" in advanced options. If indeed you have the same problem I had, pressing this should fix the problem. I don't know anything beyond this as I never got to find out what happens afterwards.
Click to expand...
Click to collapse
really？where I can find the“fix fastboot in advanced options”？

richardwia said:
really？where I can find the“fix fastboot in advanced options”？
Click to expand...
Click to collapse
I believe I'm not qualified to help you as I disposed of my tablet months ago. All the advice I've given is off of memory and may not be accurate. That being said, I won't help you anymore in fear of giving inaccurate information that may lead to bricking of your tablet.

I have a pixel C, flashed with latest 3-rd pixel experience before, someday i tried to flash back to factory image, hit the same trouble like this topic, i came here several times before, no solution, today, i found another article about this , it's solved my trouble.
sorry i am new here, i couldn't share the outside article link.
would like to share what i did on my pixel c.
1. root your pixel c
2. adb shell //this command could be executed under recovery mode too.
3. su
4. fwtool vbnv write dev_boot_fastboot_full_cap 1
5. adb reboot fastboot
then you could flash anything you want.

I had this just now - I finally got fed up of my Pixel C being so laggy and also chrome opening up as blank pages (I switched to brace to fix this, but it's abit crashy).
Anyhow I found that after
adb reboot bootloader
that
fastboot flash recovery twrp.img
was failing for me in the "Writing" stage
I discovered that the fix was to use
adb flashing unlock
then it will ask you a question (power button to confirm and one of teh volume keys to cancel).
after this it spins with erasing for a while and then comes back to fastboot after which
fastboot flash recovery twrp.img
Worked, after this you get an annoying 30s delay for each restart, I think that can be fixed by
adb flashing lock
I'll verify this when I've finished flashing a usable ROM to my Pixel C...

Install TWRP and then to root.

Hello please can anyone advise me and forgive any wrong terms..
I am trying to push twrp to my lg g4 H815 20g using adb and fastboot but everytime it comes back with
error: cannot load 'twrp.img': No such file or directory
PS C:\Users\Anthony\Desktop\ADB>
i have tried renaming twrp file to various things and changing the command fastboot flash twrp.img or fastboot flash recovery.img
but i keep getting errors of one discription or the other..
I have followed guild after guild but still not made the magic happen..
Bootloader is officially unlocked via LG and twrp for lg g4 downloaded from twrp site.
Been trying for two days to install a recovery so i can also root but having no luck.
please any help or advise would be appreciated..

you must put the "twrp.img" into to your "ADB" folder and then exec this:
Code:
fastboot flash recovery twrp.img

Hi thanks for your help
yes I have the img file in adb/fastboot folder and been doing this and still comes back in cmd as no such file etc..
Tried renaming twrp img file and changing fastboot flash line to match but still no joy..
Tried earlier g4 twrps same outcome it’s as if downloaded recovery’s are corrupt or something as they don’t appear to be being seen..
What is best name for the twrp image or do you leave it as it came downloaded and run the
fastboot flash recovery twrp.img Regardless of what twrp called when downloaded..
Thanks

Have you changed directory to the sdk folder? Or shift + right clicked in folder "open cmd here"?
The command is "fastboot flash *whatever recovery is called in adb folder*"
I ended up changing the name to "twrp3.1.1" or whatever cause it had a hell of a name when downloaded. Just name whatever you want as long as you call it same thing when flashing.
Make sure you also have a copy of it on your SD too because it wont stick and when you reboot to the recovery you then need to reflash the image from in there.

Hi I think it was successful i changed name of twrp on second attempt and it seemed to work..
only problem was when i tried to manually boot into recovery via volume down and power i did something wrong and accidentally reset the dam thing instead of booting into twrp......will have to do it all over again but hopefully i have it sorted..
PS C:\ADB> adb reboot-bootloader
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
PS C:\ADB> fastboot flash recovery twrp.img
error: cannot load 'twrp.img': No such file or directory
PS C:\ADB> fastboot flash recovery twrp-3.1.1-1-g4.img
target reported max download size of 536870912 bytes
sending 'recovery' (33952 KB)...
OKAY [ 0.781s]
writing 'recovery'...
OKAY [ 0.422s]
finished. total time: 1.219s
PS C:\ADB> fastboot reboot
rebooting...
finished. total time: 0.031s
PS C:\ADB>

Hello! I reopen this tread.. I have an issue with flashing twrp, via adb I start into bootloader, but when i put the command to flash it.. <waiting for device>. Why?

Question Anyone had problems rooting OOS13 final

I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play

djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
I also had issues booting the boot.img. I took the risk of flashing it and it worked.

Airwolf79 said:
I also had issues booting the boot.img. I took the risk of flashing it and it worked.
Click to expand...
Click to collapse
Using what command? Just fastboot flash boot rootedimage.img?
Kind of reticent to do that cos there's no linux MSM tool

djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
Also having that issue on the NA varient. So f-ing annoying.

djsubterrain said:
I'm on the EU final, bootloader was already unlocked.
Usually I'm on my Windows 11 PC but I'm stuck on my linux laptop for now (ZorinOS).
Downloaded the platform tools but the fastboot command isn't recognised, even with ./ :
:~/ADB$ ./fastboot
fastboot: usage: no command
./adb works ok
Both ADB and Fastboot show executable permissions
So I downloaded and installed ADB and Fastboot with APT
Also, finally, got the payload_dumper to install correctly and extract the payload.bin
Magisk 25.2 is installed, copied the extracted boot.img over and rooted it, copied it to my computer
Used ADB REBOOT BOOTLOADER, that worked fine
Used fastboot with the rooted image, which seemed to work fine:
~/ADB$ fastboot boot magisk_patched-25200_2FxQP.img
downloading 'boot.img'...
OKAY [ 6.735s]
booting...
OKAY [ 0.448s]
finished. total time: 7.183s
Then I just get stuck on the fastboot logo, I know sometimes it's slow to boot but I left it for ages and no boot, nothing's destroyed though, the phone will boot back normally, albeit with that new ugly orange mode message.
Tried it a second time too, same result.
Any ideas? I was wondering if the fastboot installed via APT might be out of date but the one in the google platform tools doesn't seem to want to play
Click to expand...
Click to collapse
Go into recovery and factory reset. That happen to me once when flashing in fastboot from bootloader.

djsubterrain said:
Using what command? Just fastboot flash boot rootedimage.img?
Kind of reticent to do that cos there's no linux MSM tool
Click to expand...
Click to collapse
Yeah, I know. I'm on a Mac, so, same boat. Yes, I flashed with "fastboot flash boot boot.img", specifically renaming the patched img to boot.img. This used to be the standard way of doing it, although I realize it's safer to boot the img.

My mistake, you are trying to get root, correct?

TheGhost1951 said:
My mistake, you are trying to get root, correct?
Click to expand...
Click to collapse
Try fastboot enhanced maybe? Nope, sorry, that is for windows only I believe.

TheGhost1951 said:
Try fastboot enhanced maybe? Nope, sorry, that is for windows only I believe.
Click to expand...
Click to collapse
Being on a MAC, I really don't have a clue bud..

Actually found the linux version of MSM tool (It's really just a Qualcomm tool) so I might try flashing directly, will need to grab the appropriate MSM image just in case.
Made a guide here for anyone else in Linux but I haven't tested yet

djsubterrain said:
Actually found the linux version of MSM tool (It's really just a Qualcomm tool) so I might try flashing directly, will need to grab the appropriate MSM image just in case.
Made a guide here for anyone else in Linux but I haven't tested yet
Click to expand...
Click to collapse
Did root work?

If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.

mustangtim49 said:
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
Click to expand...
Click to collapse
You did actually read my post, right?

mustangtim49 said:
If you're trying to root, just run the command "fastboot boot magisk_patched boot.img" Don't use the command "fastboot flash boot magisk_patched boot.img" You only want to boot the patched img, once it boots, then use the magisk apk to direct install.
Click to expand...
Click to collapse
I'm still getting a bootloop

LuckyTheCoder said:
I'm still getting a bootloop
Click to expand...
Click to collapse
Of course, once it goes wrong, it stays wrong. Did you use the fastboot flash boot command? Either way, msn tool and start from scratch.

mustangtim49 said:
Of course, once it goes wrong, it stays wrong. Did you use the fastboot flash boot command? Either way, msn tool and start from scratch.
Click to expand...
Click to collapse
I did, yes. MSN tool? Like fully reset?

LuckyTheCoder said:
I did, yes. MSN tool? Like fully reset?
Click to expand...
Click to collapse
It will!

TheGhost1951 said:
It will!
Click to expand...
Click to collapse
:/

LuckyTheCoder said:
:/
Click to expand...
Click to collapse
I can't count the number of times I have started from scratch just from trying different things and crashing!

TheGhost1951 said:
I can't count the number of times I have started from scratch just from trying different things and crashing!
Click to expand...
Click to collapse
How in the world am I supposed to back it up?

Can't install TWRP

I flashed my redmi note 8 pro indian version with miflash, and downgraded to android 9 from 11 to install Ubuntu touch.
Ubports installer still didnt recognize my phone I am guessing cause it was Begoniain(india) as opposed to Begonia(Global) that is supported.
But my problem is I want to go back to Android, and I dont know how to go back, I didn't have any recovery tool installed before installing Ubuntu Touch, now Ubuntu is very buggy, and I can't seem to install TWRP. I have no other recovery tools installed, just fastboot. I guess I should hvae installed twrp before installing Ubuntu Touch. I want to know how I can go back to android or to any other supported custom rom.
Thank you.

whats wrong with fastboot?

Hey, thanks for replying. I followed the steps in this video
which is a very accurate video i found after searching for many videos.
basically he asked to download the right TRWP, then ADB platform tools, then the ADB driver found here
[OFFICIAL][TOOL][WINDOWS] ADB, Fastboot and Drivers - 15 seconds ADB Installer v1.4.3
15 seconds ADB Installer v1.4.3 ADB, Fastboot and Drivers What is this? This is All-in-One installer for 3 most needed PC tools for Android. No need to download big SDK for 3 small things. I originaly made it for my Kurdish friend AnGrY DuDe in...
forum.xda-developers.com
then using "fastboot flash recovery twrp.img" cmd command
this seemed to work for many people and everything went well. but I just can't boot to twrp it just takes me to the ubuntu touch screen and i log back in to UT

xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery

aIecxs said:
xiaomi:
Code:
fastboot flash recovery twrp.img
fastboot oem reboot-recovery
Click to expand...
Click to collapse
I get this message
FAILED (remote: 'unknown command')
fastboot: error: Command failed

more commands I tried
'fastboot flash boot' gives me this error
fastboot error android_product_out not set
and 'fastboot boot recovery' command gives me this error
fastboot error cannot load 'recovery' no such file or directory
another command 'adb reboot bootloader' gave me this
error no devices/emulators found

I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.

now the phone is stuck at restarting
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
i just want a way to reset the phone back to android or other custom rom

Partition table doesn't exist?? you must have done something stupid...

aIecxs said:
I recommend to read 'fastboot help'
'fastboot flash' cmd requires two arguments: target (partition name) and source (path to file on pc)
'fastboot boot' cmd requires one argument only: source (path to file on pc)
'no such file or directory' means there exist no such file or directory with name 'recovery'
(Note this command requires bootable flag on current slot or will silently fail)
'fastboot oem' commands are device specific hidden commands. 'fastboot oem reboot-recovery' does not work on my device, but you will find lot suggestions for this here in forum (I just copy-pasted of xiaomi forum)
'adb' commands generally can't work in fastboot mode (and 'adb reboot bootloader' is fastboot mode btw)
if 'fastboot oem reboot-recovery' is unknown command, you can use 'fastboot reboot' instead. press and keep holding volume up while the phone reboots, it will enter recovery mode.
Click to expand...
Click to collapse
thank you i will try it

aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
yes i think so, i think i should've installed twrp before that was the mistake, but i'll have to format this somehow

Did you try flash by mi flash the rom that you used to downgrade?

yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.

i want to install a custom rom that goes best with my phone, i dont really want andriod to be honest, but need to have something installed to boot atleast, and I dont really mind if the phone goes dead, so i am not worried about experimenting on it

pp1pkew said:
yes this is the first thing i tried, the same procedure i used to downgrade to 9 with mi flash, but when i do that it flashses in just 1 second, and gives success message, i was like it can't be that fast, but that happens everytime, so i figured somethings wrong. I turn on my phone and it's not flashed, it boots to ubuntu touch, but now even that's not happening, now it just keeps restarting after xiomi unlcoked screen.
Click to expand...
Click to collapse
Try flash by sp flash tool. Maybe your partitions got fked by flash Ubuntu.

pp1pkew said:
i tried this 'fastboot erase data"
FAILED (remote: Partition table doesn't exist)
Click to expand...
Click to collapse
aIecxs said:
Partition table doesn't exist?? you must have done something stupid...
Click to expand...
Click to collapse
I believe that error message is misleading. It should mean
FAILED (remote: 'No such partition.')
you probably meant 'userdata' partition. however, I do not recommend fastboot erase cmd.
you should be able to enter fastboot mode with Volume Down button. instead of flashing TWRP into recovery partition (where it belongs) you could cheat bootloader and flash TWRP into boot partition instead. this will boot into TWRP recovery without Volume Up Button.
Code:
fastboot flash boot twrp.img
once in TWRP you can format Data, flash boot partition and install TWRP recovery.
probably easiest way is, create backup of boot + recovery from TWRP backup menu. that will create two files, boot.emmc.win + recovery.emmc.win in TWRP/Backups/<serialno>/<date> directory. just create another directory TWRP/Backups/<serialno>/my_files and place your files in there (rename boot.img = boot.emmc.win and twrp.img = recovery.emmc.win) then restore 'my_files' backup from menu.
then you can install any ROM from TWRP via System Image. Note that's android device, you can only install android. even ubports Ubuntu touch is not linux, it is just some gui build on top of android kernel to give you linux-like feelings.