Related
A couple days ago, I was browsing the internet, then my Nexus 7 2013 suddenly froze. I did a reboot, but it got stuck on the boot animation. So, since it wasn't booting back up, I tried to load from one of my old backups. I managed to get the back up to work, however I needed to download the 4.4.2 update OTA through TWRP. It never officially said it finished, but I restarted the tablet and it's been stuck on the Google screen. I've went to fastboot, but it wont let me into TWRP recovery since it only loads the Google screen. I've also tried this ( http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/#.U0o0z3nn_0x ) and it didn't work.
When I try to reset through WugFresh, I've flashed KRT16S 4.4 and KOT49H 4.4.2, and and I get
Code:
sending 'bootloader' (3911 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
I've also tried a few other ways of restoring to factory settings but nothing has worked :crying:
Any help is much appreciated!
I deleted my OS on my nexus... Oops? what I did is I did a ADB Sideload custom rom but if you can't get into twrp you are screwed. Maybe send it to Asus or return it if it is under warranty and get a new one. Just remember don't listen to me, in just a child on a tablet at night trying to unpack full posting privileges.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Any other suggestions..?
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
codemonkey98 said:
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
PieceofSlice said:
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
Click to expand...
Click to collapse
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
Yes you will need to replace by the "bootloader-grouper-3.34.img" by the name of the img in your device archive.
For my Razorg / deb (The LTE version) it will be :
Code:
fastboot flash bootloader bootloader-deb-04.02.img
and
Code:
fastboot -w update image-razorg-kot49h.zip
And for the Razor / flo (Wifi version) it will be :
Code:
fastboot flash bootloader bootloader-flo-flo-04.02.img
and
Code:
fastboot -w update image-razor-kot49h.zip
For reminder, factory images can be found there : https://developers.google.com/android/nexus/images?hl=FR#razor
Debugging mode / ADB is not nessesary until you write the bootloader in fastboot mode
But don't forget to install drivers, except if you already do this step
I hope i helped you.
PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
You mustn't flash grouper bootloader on flo/deb!
Only the bootloader that belongs to your firmware.
Yet I'm not sure if your USB driver is installed properly.
Are you 100% sure it is?
that link is great!...
Don't worry you are not screwed...just follow the link the person above posted about how to hard reset your nexus device. Since you have a 2013 nexus just make sure that you download the correct nexus image and make sure you flash the correct files and you will be fine. I have used that same tutorial on my nexus 7 2013 flo and deb to fix issues.
Trust me it will work...
-droidshadow
codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
PieceofSlice said:
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
Click to expand...
Click to collapse
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Well, just my 2 cents... I read somewhere else on this forum from someone having the same issue that replacing the cable he used actually did the trick for him. You might try that. Won't hurt..
tetakpatak said:
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
PieceofSlice said:
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
Click to expand...
Click to collapse
Yes just move your firmware files (bootloader and image.zip) out of the folder.
Updating is easy, double-click SDK manager application (you will see it as soon as you open SDK folder) and there you can choose what to update. You just need an internet connection.
tetakpatalked from Nexus 7
i am intrigued to see if this person was able to fix his tablet...
I think that all the suggestions above are very good ones. Making sure he has the most updated software...
Make sure he tries another usb cable or make sure you are using the stock usb cable.
And trying another usb port...
However from this fastboot devices output it did show that his device was connected which i don't think would happen with a default usb cable.
Okay so here is what i think may be causing the problem.
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
I hope this has been helpful.
Don't give up...
-droidshadow
LOL, good point @droidshadow!
Hey, @PieceofSlice, is your bootloader possibly still locked? Please make photo of the text in bootloader mode on bottom left and post screenshot of it.
tetakpatalked from Nexus 7
droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
-droidshadow
Click to expand...
Click to collapse
I'm pretty sure my bootloader is unlocked, my tablet has the unlocked padlock at the Google screen. I'll take your advice and try a new cord too
droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
-droidshadow
Click to expand...
Click to collapse
So I actually tried to do this because, even though I updated the Android SDK, when I typed in "fastboot erase boot", it basically froze on "erasing bootloader." When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
There are two generally different modes by using Android Debugging Bridge:
1. ADB (device booted in OS or recovery)
2. FASTBOOT (device in bootloader mode)
When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
Click to expand...
Click to collapse
So, if you have tried this command above when your device was in bootloader mode, it was wrong command, as the command should have started with "fastboot...." instead of "adb..."
If the device was booted in OS, this command would have been correct and such response could have two reasons:
* USB debugging was not enabled
* drivers are not installed properly
After updating SDK manager, it is always highly recommended to check if the driver still works.
PieceofSlice said:
when I typed in "fastboot erase boot", it basically froze on "erasing bootloader."
Click to expand...
Click to collapse
Careful, mate, I hope you didn't try to erase your bootloader? That would have fatal results. Actually "boot" means kernel! As long as your bootloader is there = your tab will be fine.
By flashing a factory image the order of doing things is
* erase all (kernel, system, userdata etc)
* flash new bootloader
* reboot bootloader
* flashing whole factory image zip file
tetakpatalked from Nexus 7
Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
should be in Q&A mate
I have requiested the mods to move this
So first things first. You are not bricked, you are just stuck. Bricked means your device cannot boot, cannot turn on, cannot access any bootloaders or recovery.
You messed something up and it is failing to boot, it isnt bricked.
Second, running disk encryption on rooted devices is especially dangerous for these scenarios. Disk encryption attempts to prevent many of the things running roms, custom recoveries and such put on the device.
Now, I cannot recall if a full GPE version can do this or not, but from Fastboot you should be able to flash just the system partition. But being you are encrypted it may fail to access your old data. The command for that would be:
Fastboot flash system system.img (if you were able to obtain a system.img)
Again that works on Nexus devices, I cant recall if the GPE fastboot accepts it as well.
Wish you well, but honestly I would expect to lose your data. The reason the update failed the second time was because you are Rooted. 5.0+ has a new OTA system where any changes to the system partition can/will fail the OTA.
tschakk said:
Hello everyone
So I have a m8 and converted it to the GPE edition. I changed my CID & MID and installed 4.4.4. My phone was rooted and I installed custom recoveries and went back to the stock recovery.. Here is what went wrong.
Today the update 5.0.1 came, when I tried to install it the update was failing and said my Version is not the right one. So I found out, that I flashed an old recovery and because of that it could not install it. Ok, downloaded the original OTA of 4.4.4 extracted the recovery.img and flashed that one. Now the verification check went trough..
It startet installing and after 5 minutes the update failed! Saying something like, it could not create symlinks on the system... I tried again, and now it stops with this error:
fileexist(): check the existence of /system/lib/libgoogle_recognizer_jni_1.so failed, error no such file or directory() installation aborted...
My system partition is broken now and i cannot start any system anymore...
I would like to save my data or install anything that my phone is working again, but I want to keep my data.. My phone is encrypted! :/ I tried with custom recoveries, but they apparently don't support disk encryption on the m8...
I think I cannot flash 4.4.4 with RUU as this would also delete the data... adb backup only works if the system is up, because the shell command tells me that a system dialog will appear and ask me for my password....
Anybody has any suggestion how to save my data?
Thanks!
Click to expand...
Click to collapse
First, your phone isnt bricked, its not bricked as long as you can access HBOOT, second, why would you encrypt your phone? uhg... I dont know what to tell you, try RUUing to stock, but dont expect to keep your data...
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
tschakk said:
I also had the idea with just flashing the system.img from fastboot. but that doesn't work..
target reported max download size of 1830617088 bytes
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
i now try to flash it with dd directly to the block..
Click to expand...
Click to collapse
You can only flash boot and recovery individually, you would have to put system.img and android-info.txt in a zip and flash in ruu mode
UNBELIEVABLE!
I could restore the system with dd... Just copied the system.img from Android 4.4.4 to the block device.. now the phone is booting up and i can see my data... uffff.. :victory:
so now i will do a backup and then go on...
Solution
If someone should encounter the same issue, this is what I have done to fix it:
I didn't want to lose my data, so I did not reinstall the RUU.. I couldn't get my data with ADB backup, because you need a system display to do it. And I also couldn't find any recovery which supported device encryption for the m8.. So I thought to backup my data partition with 'dd' to an external SD card and then if necessary I would reinstall the full system with RUU..
Code:
$ cat /fstab.qcom #to find the needed partitions
$ dd if=</dev/block/DATA-DEVICE> of=/external-sd/backup.bin
Now I knew I had a backup and was on the safe side. So I wanted to try to rewrite the system partition with the system.img from 4.4.4 GPE RUU. But fastboot flash didn't work. I always got this error message:
Code:
$ fastboot flash system system.img
...
erasing 'system'...
FAILED (remote: not allowed)
finished. total time: 0.010s
So what the hell, I used 'dd' also for this... :
Code:
$ cat /fstab.qcom #again to find the needed partitions
$ dd if=/external-sd/system.img of=</dev/block/SYSTEM-DEVICE>
And this actually worked, my m8 booted up with Android 4.4.4. First thing I did when Android booted was a full Android backup with adb.. To be safe to have my data back, because I didn't really know how to extract my encrypted data from the bin file I've created before... Then I just installed the update to 5.0.1 and this time it worked...
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).
The device appears to be soft-bricked. Boot hangs at the logo screen. I can access the Fastboot Menu and the Recovery menu. I have the ROM backup created with Lenovo Smart Assistant.
What I've already tried:
1. Using Lenovo Smart Assistant. That only gets so far and then it expects the tablet to be able to boot enough to get to the USB options, which it can't.
2 Since the device will talk to a computer while at the fastboot menu, I did fastboot flash boot boot.img and the outcome was the same.
3. I would have tried to restore just the system.img, but the ROM has 30 system img files, system_1.img, system_2.img, system_3.img, et cetera. I tried to combine them using:
- 3a. simg2img system* newsystem.out but got the error "build_directory_structure: can't set android permissions - built without android support"
- 3b. packsparseimg which gave me a "raw" system file. I could not find a way to convert this to a single system.img file.
4. fastboot flashall, but I don't know what to set $ANDROID_PRODUCT_OUT to just to make that work. I'm also not sure if this requires the ROM directory to be zipped?
What is there to try next?
jeb.jr said:
The device appears to be soft-bricked. Boot hangs at the logo screen..........
Click to expand...
Click to collapse
I don't have this device myself but, I had performed a quick search and found the following thread where the most recent post may be helpful for what you are looking for that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=3508508
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
Thanks, but Lenovo Smart Assistant only gets to the screen where it prompts me for USB debugging, but my tablet won't boot that far. The Device Manager in Windows doesn't come up with a triangle for anything.
However, I tried something else and got myself stuck at the fastboot menu:
There is no flash_all script in the ROM directory, but one was created by typing python createFlashTool.py. Then flash_all.sh, flash_factory.sh, and flash_all_except_storage.sh. I ran flash_all.sh and it said "Missmatching image and device". Oddly enough, flash_all is looking for MSM8953 and I have MSM8909. This must be the correct ROM because it was the one that downloaded from Lenovo Smart Assistant with my tablet number and hardware versions. So, I modified the first line of flash_all, replacing MSM8953 with MSM8909. When I entered ./flash_all.sh this time, it flashed all the img files, giving me OKAY messages over the next several minutes. Update: I suspect there's a bug in here, because it looks like system is just being overwritten 30 times instead of actually being built up.
Now, booting from power up kicks into the fastboot menu. I can reach the recovery menu, but that's it. Fortunately I can power the device down (press and hold power for exactly 3 sec) but if I try to charge it, I just get the fastboot menu again.
Update: popped the cover and removed and reinstalled the battery. still stuck in fastboot! aaauugghh...
Latest Update: I used packsparseimg again to combine all the system img files, and then fastboot flash system system.combined. Now it just reboots in a continuous loop until I power it off. Something different, but no fixy. Here's my thought: I have the uncompressed system files, now if there's a way to make an img file out of them, that would be great!
jeb.jr said:
Thanks, but Lenovo Smart Assistant only gets to the screen where it prompts me for USB.........
Click to expand...
Click to collapse
I wish that I could be more helpful to you as I only have a limited working knowledge of only a handful of the Lenovo devices.
Maybe someone like @Droidriven or @SubwayChamp could provide some guidance or someone who can help you out a bit further.
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Apple Macintosh.
jeb.jr said:
Thanks, but Lenovo Smart Assistant only gets to the screen where it prompts me for USB debugging, but my tablet won't boot that far. The Device Manager in Windows doesn't come up with a triangle for anything.
However, I tried something else and got myself stuck at the fastboot menu:
There is no flash_all script in the ROM directory, but one was created by typing python createFlashTool.py. Then flash_all.sh, flash_factory.sh, and flash_all_except_storage.sh. I ran flash_all.sh and it said "Missmatching image and device". Oddly enough, flash_all is looking for MSM8953 and I have MSM8909. This must be the correct ROM because it was the one that downloaded from Lenovo Smart Assistant with my tablet number and hardware versions. So, I modified the first line of flash_all, replacing MSM8953 with MSM8909. When I entered ./flash_all.sh this time, it flashed all the img files, giving me OKAY messages over the next several minutes. Update: I suspect there's a bug in here, because it looks like system is just being overwritten 30 times instead of actually being built up.
Now, booting from power up kicks into the fastboot menu. I can reach the recovery menu, but that's it. Fortunately I can power the device down (press and hold power for exactly 3 sec) but if I try to charge it, I just get the fastboot menu again.
Update: popped the cover and removed and reinstalled the battery. still stuck in fastboot! aaauugghh...
Latest Update: I used packsparseimg again to combine all the system img files, and then fastboot flash system system.combined. Now it just reboots in a continuous loop until I power it off. Something different, but no fixy. Here's my thought: I have the uncompressed system files, now if there's a way to make an img file out of them, that would be great!
Click to expand...
Click to collapse
Have you tried fastboot flashing the individual img files(i.e. fastboot flash system, fastboot flash boot, etc..)? It might be easier to flash each img by itself instead of all together.
Sent from my SM-S767VL using Tapatalk
Droidriven said:
Have you tried fastboot flashing the individual img files(i.e. fastboot flash system, fastboot flash boot, etc..)? It might be easier to flash each img by itself instead of all together.
Click to expand...
Click to collapse
Yes, I have. Looking at the flash_all.sh script (that was generated earlier with python createFlashTool.py) it's a list of fastboot commands. I ran the script, but I also tried running each command individually. The cyclical reboot stopped, but I'm back to booting only to fastboot mode.
I might also mention this, although it still doesn't work, it might be a lead if someone else wants to investigate:
As mentioned before, the system images are split into 30 image files. Using packsparseimg.exe and its companion imgextract.exe (or something similar) to get the uncompressed system files in their proper directory structure. Those are Windows command-line executables, but then I booted my PC back into Linux, and entered the following (this is partially from memory so it might not be 100%):
dd if=/dev/zero of=~/sys.img bs=1M count=1850 (the 1850 was found by trial and error)
mkfs.ext4 -O '^64bit' -b 4096 sys.img (that means 'not' 64bit, the target device is only 32-bit)
sudo mkdir /mnt/x
sudo mount -t ext4 -o loop sys.img /mnt/x
sudo chmod 777 /mnt/x
cp -r ~/system_folder /mnt/x (where the system folder contains the files to go into the virtual drive)
sudo umount /mnt/x
img2simg sys.img system.img
fastboot flash system system.img
UPDATE: strike this stuff because it didn't work and something else did (see below).
jeb.jr said:
Yes, I have. Looking at the flash_all.sh script (that was generated earlier with python createFlashTool.py) it's a list of fastboot commands. I ran the script, but I also tried running each command individually. The cyclical reboot stopped, but I'm back to booting only to fastboot mode.
I might also mention this, although it still doesn't work, it might be a lead if someone else wants to investigate:
As mentioned before, the system images are split into 30 image files. Using packsparseimg.exe and its companion imgextract.exe (or something similar) to get the uncompressed system files in their proper directory structure. Those are Windows command-line executables, but then I booted my PC back into Linux, and entered the following (this is partially from memory so it might not be 100%):
dd if=/dev/zero of=~/sys.img bs=1M count=1850 (the 1850 was found by trial and error)
mkfs.ext4 -O '^64bit' -b 4096 sys.img (that means 'not' 64bit, the target device is only 32-bit)
sudo mkdir /mnt/x
sudo mount -t ext4 -o loop sys.img /mnt/x
sudo chmod 777 /mnt/x
cp -r ~/system_folder /mnt/x (where the system folder contains the files to go into the virtual drive)
sudo umount /mnt/x
img2simg sys.img system.img
fastboot flash system system.img
Click to expand...
Click to collapse
Usually for large sized images fastboot splits them and send the image by parts to our device, I don´t think that you need to do other additional procedure for this if the image is for your device. Can you upload some screenshot of your folder to see which files it contains and the sizes, also a link to the firmware that you are using.
Try erasing by fastboot cache, userdata, data; try them one by one in this order and try to boot.
Code:
boot.img system_18.img userdata_2.img
cache_1.img system_19.img userdata_3.img
cmnlib.mbn system_1.img userdata_4.img
createFlashTool.py system_20.img userdata_5.img
emmc_appsboot.mbn system_21.img userdata_6.img
gpt_backup0.bin system_22.img userdata_7.img
gpt_both0.bin system_23.img userdata_8.img
gpt_main0.bin system_24.img userdata_9.img
keymaster64.mbn system_25.img vendor_10.img
MD5_DATA.xml system_26.img vendor_11.img
mdtp.img system_27.img vendor_12.img
NON-HLOS.bin system_28.img vendor_13.img
partition_vb.xml system_29.img vendor_14.img
partition.xml system_2.img vendor_15.img
patch0.xml system_30.img vendor_16.img
persist_1.img system_3.img vendor_17.img
prog_emmc_firehose_8909_ddr.mbn system_4.img vendor_18.img
ramdisk.img system_5.img vendor_19.img
ramdisk-recovery.img system_6.img vendor_1.img
rawprogram0.xml.bak system_7.img vendor_20.img
rawprogram_unsparse_upgrade.xml system_8.img vendor_21.img
recovery.img system_9.img vendor_2.img
rpm.mbn tzbsp_no_xpu.mbn vendor_3.img
sampleapp.mbn tz.mbn vendor_4.img
sbl1.mbn userdata_10.img vendor_5.img
sec.dat userdata_11.img vendor_6.img
splash.img userdata_12.img vendor_7.img
system_10.img userdata_13.img vendor_8.img
system_11.img userdata_14.img vendor_9.img
system_12.img userdata_15.img vendor.img
system_13.img userdata_16.img widevine.mbn
system_14.img userdata_17.img zeros_1sector.bin
system_15.img userdata_18.img zeros_33sectors.bin
system_16.img userdata_19.img
system_17.img userdata_1.img
Try erasing by fastboot cache, userdata, data; try them one by one in this order and try to boot.
Click to expand...
Click to collapse
Code:
$ fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.023s]
finished. total time: 0.023s
$ fastboot erase userdata
******** Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY [ 0.192s]
finished. total time: 0.192s
$ fastboot erase data
erasing 'data'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.004s
Still boots to fastboot.
Update: I just did something else and I might just have it working. More details to follow....
Before, I had used Packsparseimg from this page:
https://forum.xda-developers.com/android/software-hacking/easy-unpack-systemxx-img-firmware-t3583543
to pack all the system*.img files into one system.raw. The part that I overlooked was this:
img2simg system.raw system.img
file system.img (read the output make sure it's an android image)
fastboot flash system system.img
fastboot reboot
I saw the Lenovo logo, then a big circle with the word "erasing", then the Lenovo logo again, then the logo becomes animated and then back to static. After several minutes of nervous waiting...
Prompts for license agreement! Hooray!
Then something odd: It updated its ROM to the lastest version automatically, and then tried to update to the same version again. When it rebooted, I got the Error with the downed robot. I thought, darn...but it proceeded to boot normally. I'll have to run it through its paces before I declare it working, but I'm glad to be back on track.
Hi, guys...This tablet is making me crazy. It came bootlooping. After i tried wrong firmware and i softbricked it. I flash the right firmware but now i can just go to fastboot mode, recovery mode and edl mode.
I flashed it with different dongles and QFIL. Device state is locked. If I flash the firmware its bootlooping. After flash if ill go to recovery mode and wipe data its going to animated logo the a white bar is going for a while then freezes and the tablet reboots.After this reboot is bootlooping again until ill wipe data. HELP!
Edit: I can't flash through fastboot as tablet is in locked state.
FAILED (remote: Partition flashing is not allowed)
i second that (me too!)
i had re-locked mine and now after doing all these things, still nothing.
quite sad, if anyone would know how to help that would be so nice and i hope nobody else has this problem
:crying:
jeb.jr said:
Before, I had used Packsparseimg from this page:
https://forum.xda-developers.com/android/software-hacking/easy-unpack-systemxx-img-firmware-t3583543
to pack all the system*.img files into one system.raw. The part that I overlooked was this:
img2simg system.raw system.img
file system.img (read the output make sure it's an android image)
fastboot flash system system.img
fastboot reboot
I saw the Lenovo logo, then a big circle with the word "erasing", then the Lenovo logo again, then the logo becomes animated and then back to static. After several minutes of nervous waiting...
Prompts for license agreement! Hooray!
Then something odd: It updated its ROM to the lastest version automatically, and then tried to update to the same version again. When it rebooted, I got the Error with the downed robot. I thought, darn...but it proceeded to boot normally. I'll have to run it through its paces before I declare it working, but I'm glad to be back on track.
Click to expand...
Click to collapse
Could you share those 2 files you got from that link? It doens't seem to available anymore (asks for some password to download I don't have).
I'm in the same shoes as you, would love to get back on track with this tablet!
Thanks in advance!
Edit: Never mind, found it elsewhere!
jeb.jr said:
Before, I had used Packsparseimg from this page:
https://forum.xda-developers.com/android/software-hacking/easy-unpack-systemxx-img-firmware-t3583543
to pack all the system*.img files into one system.raw. The part that I overlooked was this:
img2simg system.raw system.img
file system.img (read the output make sure it's an android image)
fastboot flash system system.img
fastboot reboot
I saw the Lenovo logo, then a big circle with the word "erasing", then the Lenovo logo again, then the logo becomes animated and then back to static. After several minutes of nervous waiting...
Prompts for license agreement! Hooray!
Then something odd: It updated its ROM to the lastest version automatically, and then tried to update to the same version again. When it rebooted, I got the Error with the downed robot. I thought, darn...but it proceeded to boot normally. I'll have to run it through its paces before I declare it working, but I'm glad to be back on track.
Click to expand...
Click to collapse
Hi, I am in the same situation as you. I can only start bootloader and recovery. I can't flash system.img from twrp and when I try to flash it from fastboot it returns the error:
fastboot: error: cannot load 'system.img': Permission denied
Anybody has a hint on how can I solve this?
I am in over my head once more and could use help from someone more experienced.
The problem?
I bought an Alldocube M5X Pro tablet for my kids. First thing I did was root it using Magisk. I found the stock ROM, extracted the boot.img file, patched it with magisk manager, unlocked the bootloader and then used the fastboot command to flash the modified boot.img. Smooth sailing, worked flawlessly, kids were happy. 2 kids, 1 tablet, the happiness didn't last too long. They both wanted to use the tablet all the time. So when I found a sales promotion for the same model tablet, I decided to buy one more. Tablet #2 arrives, also an Alldocube M5X Pro, model T1006, Kernel version 3.18.60, Android version 8.0.0, same as tablet #1. I go through the same steps, but when I try to flash the modified boot.img file on the new tablet, it tells me Remote: Flash WRITE failure.
Here's what I did, step by step:
1. I verified that the 2nd tablet had the same build number as the 1st tablet. It did: T1006_V1.01_20200504
2. I enabled USB debugging in developer options and set the OEM Unlock option to ON
3. I trusted the connected computer in order to use the adb commands
4. I rebooted to the bootloader and executed the command Fastboot OEM unlock
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 7.825s]
finished. total time: 7.826s
Click to expand...
Click to collapse
5. I executed the command Fastboot Flash boot magisk_patched.img with the img file in the path from where I'm running the command
C:\adb>fastboot flash boot magisk_patched.img
target reported max download size of 134217728 bytes
sending 'boot' (10253 KB)...
OKAY [ 0.468s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
6. I've tried erasing the cache and user data partitions from the stock recovery and repeating step 5, but received the same error.
And that's where I'm stuck. The tablet can reboot from there, will detect tampering and proceed to run an erase command and starts with the Android Setup tutorial.
Just for the hell of it I tried flashing the stock ROM using the SP Flash tool for Mediatek devices, which works just fine. I then tried tried flashing an older build (0304) but still received the same error when trying to flash the boot.img
I also tried flashing a custom recovery as well as booting a recovery.img but in both cases the tablet ends up booting normally, I assume because the custom recovery isn't compatible with this device.
Everything I find online about flash write failure errors seems to indicate a defective emmc however most of those are specific to the Nexus 5 phone. The difference here seems to be that I can unlock the bootloader just fine, it stays unlocked as far as I can tell and I can overwrite with a new ROM, so I'm thinking the emmc is fine.
I'm just trying to puzzle this together from what I can find online, but I could really use the help of someone with more insight into the inner workings of Android.
Any help would be greatly appreciated.
After flashing 4 different ROMs, formatting the emmc completely and doing lord knows what else, it finally dawned on me that I could simply flash the patched boot image using the SP Flash tool instead of via Fastboot. It does wipe the data, and starts the Android setup wizard, but once that is completed, I was able to install Magisk Manager and download the missing files. The device rebooted after that and came back with systemless root.
Problem solved.