Related
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).
Hi, i installed the latest LG G5 Update (lineage-14.1-20170822-nightly-h850-signed), the first regular reboot was fine.
The second reboot has "bricked" my phone.
Please check the attached Picture from the phone.
Anyon a idea how to get back the phone to "life"??? :crying:
Thank you in advance for any assistance
MoPhat
This advise comes "as is" and with no warranty and I will not be responsible for any damages of any kind.
That's a soft brick (I wouldn't even call it a brick) and should be easy to resolve.
Did you erase data and system before flashing the ZIP file? You should always do this before flashing a new OS or did you just flash over your original LG5's OS without erasing those partitions?
Try re-downloading lineage-14.1-20170822-nightly-h850-signed and run a crc32 check on both zip files (the one you downloaded originally and the one you downloaded the second time) to see if the crc32 values match. If they don't, that would explain why you ended up in this situation (assuming you flashed the file the correct way). If you are on Windows, you can download a utility called "hashmyfiles" by NirSoft to get the crc32 along with other checksum values. If you are on linux, you can use the "crc32 lineage-14.1-20170822-nightly-h850-signed.zip" command to see the crc32 value and if values do not match, try downloading it again and do the check one more time until the values match. You can also click on the "sha256" and "sha1" links below the link you downloaded the file from and then using "hashmyfiles" you can compare the values whether they match.
Anyway, the way I personally would go with this one is try to enter Recovery mode, erase system, data (and probably boot but not necessary as the OS zip file will over write it anyway) and try again. If your recovery asks you to install root / SuperUser, you should select "No" and use LOS's official SuperUser add-ons if that's what you are after.
Thank you marco-v
I can't check the crc from the file because i have updated the latest Version with the build in update function...
I have tryed to boot in the recovery menu by pressing the power und volume down button, realising when i see the lg logo an pressing again both to (normaly) enter the recovery mode. it appears the same message
http://androidflagship.com/20275-boot-lg-g5-recovery-mode
the only menu that Comes are the "factory data reset" menu, but this makes no difference...
any further ideas?
marco-v said:
This advise comes "as is" and with no warranty and I will not be responsible for any damages of any kind.
That's a soft brick (I wouldn't even call it a brick) and should be easy to resolve.
Did you erase data and system before flashing the ZIP file? You should always do this before flashing a new OS or did you just flash over your original LG5's OS without erasing those partitions?
Try re-downloading lineage-14.1-20170822-nightly-h850-signed and run a crc32 check on both zip files (the one you downloaded originally and the one you downloaded the second time) to see if the crc32 values match. If they don't, that would explain why you ended up in this situation (assuming you flashed the file the correct way). If you are on Windows, you can download a utility called "hashmyfiles" by NirSoft to get the crc32 along with other checksum values. If you are on linux, you can use the "crc32 lineage-14.1-20170822-nightly-h850-signed.zip" command to see the crc32 value and if values do not match, try downloading it again and do the check one more time until the values match. You can also click on the "sha256" and "sha1" links below the link you downloaded the file from and then using "hashmyfiles" you can compare the values whether they match.
Anyway, the way I personally would go with this one is try to enter Recovery mode, erase system, data (and probably boot but not necessary as the OS zip file will over write it anyway) and try again. If your recovery asks you to install root / SuperUser, you should select "No" and use LOS's official SuperUser add-ons if that's what you are after.
Click to expand...
Click to collapse
So it looks like your Recovery mode is messed up too? Not sure how that might have happened unless you instructed LOS to "Update Recovery" .
Have you tried to see if you are able to enter fastboot mode and reflash your custom recovery image again and try to enter Recovery mode again? The one I use on my device (Oppo Find 7) is a TWRP image and I find it very reliable.
You can see if you can boot to Recovery by running the following command from fastboot mode (assuming you have a TWRP image)
fastboot boot twrp-x.x.x-x-h850.img
Replace x.x.x.x with the version of the file.
Tryed, result is:
Code:
C:\Temp\root_H850>fastboot boot twrp-3.1.1-0-h850.img
downloading 'boot.img'...
OKAY [ 0.430s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.451s
With "adb.exe devices" are the phone not listed
Ok, my device is locked!?!?
Code:
C:\Temp\root_H850>fastboot flash recovery twrp-3.1.1-0-h850.img
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.428s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.456s
So i have tryed to unlock the device again with the unlock key i get:
Code:
C:\Temp\root_H850>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.037s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.059s
How can i disable the " Enable OEM unlock" in the developer Settings without a gui???
Ok, fastboot works, that's good but it looks like your bootloader is locked again.
FAILED (remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Try following these instructions: https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047 and see if you can get TWRP running and if you do, you can try flashing LOS again but format data + system (you will lose all data) and if you are not careful, you might lose data on internal storage + external storage so read carefully what's displayed on the screen before going ahead.
Also: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS and this will show you how to unlock your bootloader.
---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------
I just read your post, you can try:
fastboot oem unlock
and see if it works. May be it will because it was unlocked already once but can't tell for sure.
Sorry, nothing has worked.
I will try set "upgrade error" back in the lg update tool to flash the original firmware, but i need a SERIAL or the IMEI number, how can i find this out?
Normally, IMEI numbers are located right under the battery on phones that come with removable back covers and batteries. Yours however slides out, it might be somewhere there or perhaps you can check the box / packaging. So the following command didn't work?
fastboot oem unlock
What's the error you got? The official bootloader instructions on LG's website should have worked as it supports your model. To me the only issue you seem to be having is a restricted booloader and once you unlock it, everything should be fine. This is why you can't boot into TWRP using the boot command.
Not worked, the result is:
Code:
C:\Temp\root_H850>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
I see, thx, if the LG official unlock instructions did not or no longer work followed by the instructions here https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047, I am out of ideas. Perhaps someone else can help and provide further hints.
I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.
sammd301 said:
I have struggled to fix my bootlooping problem , After install LOS rom/ other rom and flashing the Magisk. Everything installed fine, but for some reason, after restarting the system it will get to LOS loading screen and bootloop. I attempted to install a stock rom on it, but that load fine but it WIFI and Cellular Network doesn't work. The boot loader has been unlocked Any detail instruction will be highly appreciated. Thanks
Background info, I have spent more than 1 years using this awesome phone with Lineage OS 15.1 , I wake up one morning with the constantly boot looping. I have the T-Mobile version with the bootloader unlocked. I have also spent weeks going through and following other threads but haven't been able to resolved my issue.
Click to expand...
Click to collapse
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.
41rw4lk said:
Whenever you move from custom to stock and vice versa you should format user data. Easiest way is in bootloader mode, issue the command 'fastboot -w' w/o quotes.
Click to expand...
Click to collapse
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------
sammd301 said:
I applied the "fastboot -w" below is the output I got; Still no WIFI and Cellular network not working
-------------------------------------------------------------
PS C:\adb> fastboot -w
Erase successful, but not automatically formatting.
File system type raw not supported.
Erase successful, but not automatically formatting.
File system type not supported.
erasing 'userdata'...
(bootloader) Permission denied
FAILED (remote failure)
finished. total time: 0.005s
-------------------------------------------------
Click to expand...
Click to collapse
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?
41rw4lk said:
Do you have an imei number still? Is the bootloader still unlocked? Have you tried following the return to stock thread and doing a clean install of the latest TMO firmware?
Click to expand...
Click to collapse
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance
You need to blankflash, then flash the latest TMO firmware for your phone. Usually you lose baseband when you flash the wrong firmware, does it say XT1789-04 by the usb port?
sammd301 said:
The IMEI number is “Unknown” , Yes the bootloader is Unlocked because, I am able to flash TWRP image on the phone. Yes I spent close to a week following the return to stock thread, the first time I did it, the Cellular network come on about 30 minutes after the phone completed loading to the home screen. Thanks for the guidance
Click to expand...
Click to collapse
I would go through the unlock process again. Your bootloader shows flashing_locked
Uzephi said:
I would go through the unlock process again. Your bootloader shows flashing_locked
Click to expand...
Click to collapse
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>
sammd301 said:
I follow the procedure to unlocked the bootloader again, it now shows "flashing_unlocked" as show in the photo below; I flashed another oem rom but still no wifi and network and Still Baseband /Baseline is < not found>
Click to expand...
Click to collapse
Can you link the flash all you used and how you flashed it?
Uzephi said:
Can you link the flash all you used and how you flashed it?
Click to expand...
Click to collapse
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
sammd301 said:
I have been following this tread on xda [ https://forum.xda-developers.com/z2-force/how-to/how-to-return-to-stock-sprint-t3694783 ]
Below is the steps
How to fix your phone:
Download the Utilities zip Link to the flash all https://www.androidfilehost.com/?fid=5862345805528053597
Extract the zip to it's own folder
Download the flash all for your device from the options below.
Extract the flash all zip into the same folder as the Utilities.
Run the Flashall.bat file
Watch windows command prompt put your phone back to stock!
Click to expand...
Click to collapse
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?
I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit
sammd301 said:
I used the T-Mobile Flash All zip the link was to google drive https://drive.google.com/file/d/1Bo_ry_38J6BHy4-A4fuhAnv94C5yV1TW/edit
Click to expand...
Click to collapse
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash
Uzephi said:
What zip did you use?
Edit: that thread uses AFH which has an older version bootloader than in your picture so something isn't going right. How long does it take to flash?
Edit 2: does your phone reboot after running the .bat file?[/QUOTE
Yes the phone does reboot by itself after running the .bat file, But it reboot back to bootloader screen.
Click to expand...
Click to collapse
Uzephi said:
Yeah, that one is old. Try https://androidfilehost.com/?fid=11410963190603877456 just like the guide states, it should open command prompt and you should see it flashing. The process can take s minute or two. If it immediately closes within 30 seconds or hangs, it didn't flash
Click to expand...
Click to collapse
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s
sammd301 said:
I download the suggested rom [ https://androidfilehost.com/?fid=11410963190603877456 ] and flashed it to my phone running flashall.bat via Windows PowerShell,
It took approximately 6 minutes for the flashing to be complete, but with some minor error, Afterword the phone reboot back to the bootloader screen. After starting it still doesn't show the IMEI number and No cellular network or WIFI available.
The output of the flashing process is below along with the attach screenshot of the error;
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ 0.803s]
finished. total time: 0.807s
Click to expand...
Click to collapse
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.
Uzephi said:
Flash again, after it is done, type fastboot --set-active=other and then run it one last time. Then boot your phone.
Click to expand...
Click to collapse
After flashing the rom again, and getting the error " Erase successful, but not automatically formatting..." I input the fastboot command "fastboot --set-active=other" and I got back "unknown option -- set-active=other" as show in the image below. Was the syntax right?
I have been googling the errors I have received like "Erase successful, but not automatically formatting.
File system type raw not supported" to see if I can land on page that can help resolve the issue with the phone.
I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.
sammd301 said:
I have downloaded the latest adb and fastboot platform tools versions, after running the flashall.bat file, I still got the same error at the end. I follow up with the "fastboot --set-active=other" command and this time I got [ Setting current slot to '`' FAILED (remote: '') ] as show in the image below.
Click to expand...
Click to collapse
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B
Uzephi said:
Seems it isn't recognizing other then, which it should. Do =_b then to see if you can swap to slot B
Click to expand...
Click to collapse
After inputting the command [ fastboot --set-active=_b ] the output I got back was [ Slot _b does not exist. supported slots are:
a
b ]
I proceed to input [ fastboot --set-active=b ] the output was [ Setting current slot to 'b' ]
So I the flashing again and input the [ fastboot --set-active=b ] again and got back [ Setting current slot to 'b' ]
I pressed the power button to start the phone from bootloader menu , the phone boot-loop with the Motorola logo as show, after 6 to 8 cycling of the boot looping with the Motorola logo the phone bootup again with T-Mobile logo. When it got home screen, I saw again that Network and cellular still not working and No IMEI number too.
Hope you guys can give me a hand and get me out of this situation...
What I am using
Xiaomi Redmi Note 5 Pro with:
- Pixel Experience Rom
- TWRP 3.5.2_9
Windows 10 21H1 x64
What happend
- Updating Pixel Experience Rom failed
Downloaded update
Booted into Recovery (battery 85%)
Recovery stuck on Logo
After 30m I tried to reboot to system (thinking update failed or never started)
Reboot in to Recovery
Stuck on Logo
What I tried
- I tried XiaomiFastBootADBTools (latest version)
Device is recognized in Recovery mode
In recovery I can't do anything
Rebooting to System from here results in reboot into Recovery
Booting to fastboot works, but device is not recognized
Re-installed drivers, but no luck
Still recognized in Recovery mode
Still NOT recognized in Fastboot mode
Windows Device Manager > The drivers for this device are not installed. (Code 28)
And turning of phone is not possible, just goes back to Recovery
Don't know what else to do. I have installed all the drivers I could find. Even used Snappy Driver, but nothing seems to do the trick when the phone goes into Fastboot mode. PC just doesn't recognize it.
So can't do anything in Recovery mode; just watching the TWRP logo.
And device is not recognized in fastboot mode; forgot usb debugging?
And can't boot into system to change that, because of bootloop to Recovery.
So, am I **** out of luck and bricked my phone?
While in Recovery mode (when the phone is still recognized) type in adb window the command - adb reboot bootloader. Phone should boot to Fastboot mode and see if it's still recognized.
zaqm said:
While in Recovery mode (when the phone is still recognized) type in adb window the command - adb reboot bootloader. Phone should boot to Fastboot mode and see if it's still recognized.
Click to expand...
Click to collapse
Yeah, that works. Same as with XiaomiADBFastbootTools. But after that the problem starts (remains).
When I get into Fastboot the Device Manager shows the phone as Other Devices > Android with an exclamation mark and the message that the drivers are not installed. I'm missing a driver, but I don't know which one. Guessing Xiaomi USB driver? Finally fixed that issue with another round of googling. I read that you just need net "Mi unlock Tool". So tyring to find that one:
- https://en.miui.com/unlock/download_en.html
results in a download that doesn't contain the files needed.... No driver_install and no miflash_unlock.exe etc.
pretty weird, found another page https://c.mi.com/thread-2262302-1-0.html with previous versions
- 4.5.813.51 won't download... really xiaomi, your site sucks.
- 4.5.707.49 finally downloads and seems to work.
So updated the driver by pointing to that folder. Worked like a charm.
Opening Minimal ADB and Fastboot (XiaomiADBFastboottools didn't recognize phone once in fastboot).
- adb reboot bootloader > success
- fastboot flash recovery 'recovery_file_location' > error
target reported max download size of 536870912 bytes
sending 'recovery' (47140 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried both latest TWRP and Orangefox. Same message each time.
Tried an older/smaller TWRP 3.3.1 and got a different but still similar message
target didn't report max-download-size
sending 'recovery' (38924 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried it with Platform-Tools
- adb reboot bootloader
- fastboot boot 'recovery_file_location'
Which results in
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
OR
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
AND eventually
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
2 hours in, calling it a day for now.
FlashyDuck said:
Yeah, that works. Same as with XiaomiADBFastbootTools. But after that the problem starts (remains).
When I get into Fastboot the Device Manager shows the phone as Other Devices > Android with an exclamation mark and the message that the drivers are not installed. I'm missing a driver, but I don't know which one. Guessing Xiaomi USB driver? Finally fixed that issue with another round of googling. I read that you just need net "Mi unlock Tool". So tyring to find that one:
- https://en.miui.com/unlock/download_en.html
results in a download that doesn't contain the files needed.... No driver_install and no miflash_unlock.exe etc.
pretty weird, found another page https://c.mi.com/thread-2262302-1-0.html with previous versions
- 4.5.813.51 won't download... really xiaomi, your site sucks.
- 4.5.707.49 finally downloads and seems to work.
So updated the driver by pointing to that folder. Worked like a charm.
Opening Minimal ADB and Fastboot (XiaomiADBFastboottools didn't recognize phone once in fastboot).
- adb reboot bootloader > success
- fastboot flash recovery 'recovery_file_location' > error
target reported max download size of 536870912 bytes
sending 'recovery' (47140 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried both latest TWRP and Orangefox. Same message each time.
Tried an older/smaller TWRP 3.3.1 and got a different but still similar message
target didn't report max-download-size
sending 'recovery' (38924 KB)...
FAILED (remote: Requested download size is more than max allowed
)
finished. total time: 0.004s
Tried it with Platform-Tools
- adb reboot bootloader
- fastboot boot 'recovery_file_location'
Which results in
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Invalid argument))
fastboot: error: Command failed
OR
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (Too many links))
fastboot: error: Command failed
AND eventually
Sending 'boot.img' (43884 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed
2 hours in, calling it a day for now.
Click to expand...
Click to collapse
What about trying to flash latest fastboot rom with MiFlash since fastboot now works?
Absolutely awesome! We did it!
I'm no expert in all this, so I had to use a guide to flash a fastboot rom with the Mi Flash Tool. I used this guide: https://www.thecustomdroid.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
That was all straight forward untill I came to step 6; flashing the actual rom with the Mi Flash Tool.
The tool just wouldn't recognize my phone when in Fastboot mode. Even after the driver install popup.
- after pressing refresh phone disconnected.
- tried 3 different usb ports (read online that this could be the issue)
- tried 3 different cables...
The third cable (Ugreen cable) worked! Although it only worked on a usb 3.0 port strangely enough.
I used the "clean all" option and flashed the latest MIUI global fastboot rom for the RMN5.
Flashing process was a bit strange, because the tool didn't provide me with the same information shown in the guide, but it flashed a couple of things to 100% completeness and after that it kept counting up and showing $pause. Not much later the phone started to boot into MIUI and everything was normal.
Enabled dev options and usb debugging.
Re-flashed latest twrp recovery just to be sure.
And it's all working fine again.
Really, thank you for your help! It's much appreciated!
FlashyDuck said:
Absolutely awesome! We did it!
I'm no expert in all this, so I had to use a guide to flash a fastboot rom with the Mi Flash Tool. I used this guide: https://www.thecustomdroid.com/install-miui-fastboot-rom-using-miflash-tool-xiaomi/
That was all straight forward untill I came to step 6; flashing the actual rom with the Mi Flash Tool.
The tool just wouldn't recognize my phone when in Fastboot mode. Even after the driver install popup.
- after pressing refresh phone disconnected.
- tried 3 different usb ports (read online that this could be the issue)
- tried 3 different cables...
The third cable (Ugreen cable) worked! Although it only worked on a usb 3.0 port strangely enough.
I used the "clean all" option and flashed the latest MIUI global fastboot rom for the RMN5.
Flashing process was a bit strange, because the tool didn't provide me with the same information shown in the guide, but it flashed a couple of things to 100% completeness and after that it kept counting up and showing $pause. Not much later the phone started to boot into MIUI and everything was normal.
Enabled dev options and usb debugging.
Re-flashed latest twrp recovery just to be sure.
And it's all working fine again.
Really, thank you for your help! It's much appreciated!
Click to expand...
Click to collapse
Glad that it worked out. Sometimes even the most untraditional methods work like usb 3.0 and the third cable.
Still all went good and that's the good news. Enjoy
--double, woops--
zaqm said:
Glad that it worked out. Sometimes even the most untraditional methods work like usb 3.0 and the third cable.
Still all went good and that's the good news. Enjoy
Click to expand...
Click to collapse
Unfortunately, the problem has returned.
The first time flashing Orange Fox Recovery was no problem. I could boot to Recovery. I installed Pixel Experience Plus again. That all worked fine.
Today I wanted to try out ArrowOS. And this is what I did:
- loaded the .zip file on the phone
- turned off the phone
- booted into recovery
- stuck on recovery logo screen...
- after this the phone bootloops to recovery again as before...
In Recovery and Fastboot the phone is still recognized by the PC. But in Recovery I can't do anything.
So in Fastboot mode I tried re-flashing Orange Fox , but same result. Flashing seems successful but can't get past the Recovery logo. I even tried flashing TWRP, but also same result.
I can probably redo all the steps in my previous post, but once I boot to recovery the phone is done for it seems.
Any ideas?
FlashyDuck said:
Unfortunately, the problem has returned.
The first time flashing Orange Fox Recovery was no problem. I could boot to Recovery. I installed Pixel Experience Plus again. That all worked fine.
Today I wanted to try out ArrowOS. And this is what I did:
- loaded the .zip file on the phone
- turned off the phone
- booted into recovery
- stuck on recovery logo screen...
- after this the phone bootloops to recovery again as before...
In Recovery and Fastboot the phone is still recognized by the PC. But in Recovery I can't do anything.
So in Fastboot mode I tried re-flashing Orange Fox , but same result. Flashing seems successful but can't get past the Recovery logo. I even tried flashing TWRP, but also same result.
I can probably redo all the steps in my previous post, but once I boot to recovery the phone is done for it seems.
Any ideas?
Click to expand...
Click to collapse
Hmm, I don't know why is that happening. It's usually the custom recovery's fault in such case except if Pixel rom comes with its own prebuilt recovery that overwrites the one you installed.
I suggest you first to try to boot into system to see if it will work - in fastboot mode type the command fastboot reboot.
If this doesn't work then flash again fastboot rom to get the phone in working condition and after installing twrp FORMAT DATA in twrp Wipe section. Then install rom again.
Good luck, zaqm!
zaqm said:
Hmm, I don't know why is that happening. It's usually the custom recovery's fault in such case except if Pixel rom comes with its own prebuilt recovery that overwrites the one you installed.
I suggest you first to try to boot into system to see if it will work - in fastboot mode type the command fastboot reboot.
If this doesn't work then flash again fastboot rom to get the phone in working condition and after installing twrp FORMAT DATA in twrp Wipe section. Then install rom again.
Good luck, zaqm!
Click to expand...
Click to collapse
It worked!
Don't know why, but it's working. Here's what I did:
- In Fastboot Mode > fastboot reboot > booted to recovery, so no luck there
- Used MiFlash to flash the fastboot rom again (clean all)
- Setup the phone etc. and activated usb debugging
- Flashed TWRP
- Booted to TWRP
- Format Data
- Rebooted to TWRP
- Mounted Storage, uploaded ArrowOS.zip and installed it
- Wiped Dalvik/Cache
- Booted ArrowOS, and success!
Have done several reboots to (and from) system/recovery and it just works again, as it should.
I think the Format Data in TWRP did the trick. I remember in Orange Fox this all was a bit unclear; I'm just not used to Orange Fox, always used TWRP. So my bad for not correctly flashing the rom probably.
Again, thank you very much for your help! Have a great day! And let's hope this is the end of this issue haha.
FlashyDuck said:
It worked!
Don't know why, but it's working. Here's what I did:
- In Fastboot Mode > fastboot reboot > booted to recovery, so no luck there
- Used MiFlash to flash the fastboot rom again (clean all)
- Setup the phone etc. and activated usb debugging
- Flashed TWRP
- Booted to TWRP
- Format Data
- Rebooted to TWRP
- Mounted Storage, uploaded ArrowOS.zip and installed it
- Wiped Dalvik/Cache
- Booted ArrowOS, and success!
Have done several reboots to (and from) system/recovery and it just works again, as it should.
I think the Format Data in TWRP did the trick. I remember in Orange Fox this all was a bit unclear; I'm just not used to Orange Fox, always used TWRP. So my bad for not correctly flashing the rom probably.
Again, thank you very much for your help! Have a great day! And let's hope this is the end of this issue haha.
Click to expand...
Click to collapse
Maybe some glitch of OrangeFox recovery and yeah, let's hope that this issue won't appear anymore.
All the best, zaqm!
Official TWRP is now available: https://twrp.me/asus/rogphone6.html
IMPORTANT NOTES:
This device has a recovery partition (2, in fact), and fastboot boot is disabled in the bootloader. Flashing TWRP to the recovery partition is the only way to use it.
If you attempt to fastboot boot the TWRP image, your device may end up unbootable. YOU'VE BEEN WARNED.
Any questions, comments, feedback, or concerns should always be accompanied by logs (recovery log, logcat, dmesg)
TWRP Trees
Common: https://github.com/TeamWin/android_device_asus_sm84xx-common
Device: https://github.com/TeamWin/android_device_asus_AI2201
It doesn't work! Either flashing or just booting via fastboot gives an error message. Tried to install twrp app...it crashes all the time, couldn't even flash the zip...
I also had to reflash the raw because the phone was stuck in bootloader mode.
I can't flash the img either. I'm on tencent version, is it the difference?
Code:
fastboot flash recovery_a twrp.img
Sending 'recovery_a' (102400 KB) OKAY [ 2.319s]
Writing 'recovery_a' FAILED (remote: 'Flashing non-hlos image is not allowed in lock state')
fastboot: error: Command failed
minazukix said:
I can't flash the img either. I'm on tencent version, is it the difference?
Code:
fastboot flash recovery_a twrp.img
Sending 'recovery_a' (102400 KB) OKAY [ 2.319s]
Writing 'recovery_a' FAILED (remote: 'Flashing non-hlos image is not allowed in lock state')
fastboot: error: Command failed
Click to expand...
Click to collapse
The message seems to indicate that your device bootloader isn't unlocked...
Captain_Throwback said:
The message seems to indicate that your device bootloader isn't unlocked...
Click to expand...
Click to collapse
I have unlocked the bootloader already.
I can flash to WW by flashall_AFT.cmd, like here https://androplus.org/en/entry/rog-phone-6-china-to-global-conversion/
minazukix said:
I have unlocked the bootloader already.
I can flash to WW by flashall_AFT.cmd, like here https://androplus.org/en/entry/rog-phone-6-china-to-global-conversion/
Click to expand...
Click to collapse
Flashing RAW doesn't require an unlocked bootloader.
I'm just telling you what the message from the bootloader is saying. I don't control that, sorry.
Captain_Throwback said:
Flashing RAW doesn't require an unlocked bootloader.
I'm just telling you what the message from the bootloader is saying. I don't control that, sorry.
Click to expand...
Click to collapse
I've already unlocked my phone with the official unlock device app.
I have the boot loader is unlocked warning screen when my phone power on.
Also, I can flash the patched boot.img to get root.
Code:
fastboot flash boot magisk_patched-25200-boot.img
Sending 'boot_a' (98304 KB) OKAY [ 0.301s]
Writing 'boot_a' OKAY [ 0.240s]
I think my bootloader should be unlocked.
minazukix said:
I've already unlocked my phone with the official unlock device app.
I have the boot loader is unlocked warning screen when my phone power on.
Also, I can flash the patched boot.img to get root.
Code:
fastboot flash boot magisk_patched-25200-boot.img
Sending 'boot_a' (98304 KB) OKAY [ 0.301s]
Writing 'boot_a' OKAY [ 0.240s]
I think my bootloader should be unlocked.
Click to expand...
Click to collapse
Then try just
Code:
fastboot flash recovery twrp.img
without the slot suffix and see if that works. That'll just flash TWRP to the active slot.
Just read carefully on the page that you've downloaded the twrp.img. I saw a short brief guide on how to flash TWRP recovery as below: (using termux or any terminal on your phone)
1. Copy downloaded file and Place it in the root of your /sdcard folder and rename it to twrp.img.
2. Type following command on termux or any terminal (on your phone).
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_a
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_b
Ps_1: it works for me, after failed to flash via fastboot due to locked state. (my phone is rooted with Magisk)
All credit to: Captain_Throwback.
I take no credit at all.
Ps_2: your phone must rooted.
tuannghia1985 said:
Just read carefully on the page that you've downloaded the twrp.img. I saw a short brief guide on how to flash TWRP recovery as below: (using termux or any terminal on your phone)
1. Copy downloaded file and Place it in the root of your /sdcard folder and rename it to twrp.img.
2. Type following command on termux or any terminal (on your phone).
su
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_a
dd if=/sdcard/twrp.img of=/dev/block/by-name/recovery_b
Ps_1: it works for me, after failed to flash via fastboot due to locked state. (my phone is rooted with Magisk)
All credit to: Captain_Throwback.
I take no credit at all.
Ps_2: your phone must rooted.
Click to expand...
Click to collapse
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.
fux1976 said:
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.
Click to expand...
Click to collapse
Yes, it works for me too.
You can use adb push/pull to transfer files in TWRP.
fux1976 said:
Hi! It worked, thanks a lot! The only problem is no otg support...which makes flashing a bit a pain in the... Now I'm experimenting. I've had issues with voice typing and Android Auto, so through TWRP I'm trying to fix them.
Click to expand...
Click to collapse
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.
minazukix said:
Yes, it works for me too.
You can use adb push/pull to transfer files in TWRP.
Click to expand...
Click to collapse
Thanks, that's the best option to push file directly via abd push.
tuannghia1985 said:
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.
Click to expand...
Click to collapse
I just flashed the latest raw zip(WW-AI2201-32.2810.2210.220-REL-2210-M2.13.33.24-ASUS_1.1.1-Phone-user-20221109.raw), then everything is working well (e.g. /vendor/factory/COUNTRY is already WW).
I don't use voice typing, Android auto, google pay and fingerprint either, but I just tested the fingerprint features, there is no problems. I pass safetynet and hide root by this Method 2: https://www.droidwin.com/how-to-pass-safetynet-on-rooted-android-12/
tuannghia1985 said:
I'm not get any trouble with voice typing by google keyboard, not try Android auto yet? If you got trouble about Device is certified then try MagiskHide props config (magisk module) and using a verified fingerprint (mine is using fingerprint from rog phone 5). Everything is fine even google wallet.
Click to expand...
Click to collapse
Everything is working fine, except these 2 features. Voice typing at first is working but after downloading my configuration (google backup) and my apps, it stops. I can live without it. I've tried several ways: no way of making it work. So I gave up..Maybe with Android 13... as everything was fine on Android 11 on my deceased Rog2. I have Magisk props (safetynet: passed, banking apps ok). But Android auto keeps crashing..Never mind. I have a spare phone to use when I'm driving.
So if you try to fastboot Boot the twrp Image you end up with a destroyed device with no return? Or do i misunderstand that?
Einheit-101 said:
So if you try to fastboot Boot the twrp Image you end up with a destroyed device with no return? Or do i misunderstand that?
Click to expand...
Click to collapse
It says unbootable, not destroyed. RAW should fix it without a problem. It's just a long road to take, including having to wipe the device, for not following a simple instruction.
Hi guys, I want to flash this but I have 2 quick questions:
1. Can I FOTA after install TWRP ?
2. Do I need to reflash it every FOTA ?
fux1976 said:
It doesn't work! Either flashing or just booting via fastboot gives an error message. Tried to install twrp app...it crashes all the time, couldn't even flash the zip...
I also had to reflash the raw because the phone was stuck in bootloader mode.
Click to expand...
Click to collapse
hi how to reflash raw rom , i cant run flashh aft my phone stuck stock recovery help
Captain_Throwback said:
It says unbootable, not destroyed. RAW should fix it without a problem. It's just a long road to take, including having to wipe the device, for not following a simple instruction.
Click to expand...
Click to collapse
how to flash raw ? my laptop cant run flash all AFT pls help