d:\tmp>fastboot flash:raw boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 0.937s]
writing 'boot'...
FAILED (remote: (00000004))
finished. total time: 0.937s
I have a MZ604 xoom, and I got above error when using a MZ604 images download from http: //developer.motorola.com/products/software/.
when I use : fastboot flash boot boot.img to flash the boot partition, I also got image size too large for the boot partition error.
Anyone have any idea what's going on or how to fix it? Thanks.
I misedited my build.prop so I am trying to reflash a stock system.img to my Atrix 2 using Terminal on my mac.
When I attempt to flash it I get error messages.
localhost:android williamguy$ ./fastboot flash system /Users/williamguy/Desktop/5.5.1-EDEM-28-TNZ_cfc.xml/system.img
target reported max download size of 1056964608 bytes
sending 'system' (491264 KB)...
OKAY [ 23.605s]
writing 'system'...
(bootloader) Preflash validation failure
FAILED (remote: )
I only need to flash the system.img to fix my phone, other images from the rom flash successfully - only boot.img and system.img get this error message.
williamguy said:
I misedited my build.prop so I am trying to reflash a stock system.img to my Atrix 2 using Terminal on my mac.
When I attempt to flash it I get error messages.
localhost:android williamguy$ ./fastboot flash system /Users/williamguy/Desktop/5.5.1-EDEM-28-TNZ_cfc.xml/system.img
target reported max download size of 1056964608 bytes
sending 'system' (491264 KB)...
OKAY [ 23.605s]
writing 'system'...
(bootloader) Preflash validation failure
FAILED (remote: )
I only need to flash the system.img to fix my phone, other images from the rom flash successfully - only boot.img and system.img get this error message.
Click to expand...
Click to collapse
You need to get the moto-fastboot utility. Google search for it.
You use the moto-fastboot command and not the fast boot command to flash. I have used it on my macs many times without issue.... The fastboot command does not work on moto phones/images.
NOTE: Says when on rsd mode failed to boot 0x00001
on fastboot same + is says failed to format pds and does't connect to the pc after that
i have over 50 hours in 5 days looking for way to fix no luck .
i try my luck with Fastboot. I first tried flashing the recovery with no luck. I then tried flashing over the official moto files (boot/sytstem/....)
adb reboot bootloader
fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.694s]
writing 'boot'... FAILED (remote: (19000008))
....
If i follow that order boot/system and recovery fail then userdata says it works and it lets me flash the other options (but clearly just says they work it looks like it's lying)
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.694s]
writing 'boot'... FAILED (remote: (19000008))
.......
C:\SDK_tools>fastboot flash userdata userdata.img
sending 'userdata' (139233 KB)... OKAY [ 11.598s]
writing 'userdata'... OKAY [ 0.164s]
finished. total time: 11.764s
C:\SDK_tools>fastboot flash boot boot.img
sending 'boot' (8192 KB)... OKAY [ 0.688s]
writing 'boot'... OKAY [ 3.462s]
finished. total time: 4.151s
.....
If I try fastboot oem unlock I'm prompted with the unlock message and after hitting accept. I see the following error on the screen
ERROR: Failed to format UDA.
Error while unlocking device.
My next try was with RSD light. I tried flashing all of the images for my xoom off this site . all of them give me the following error:
Failed flashing process. Failed Flashing process. Interface AP-OS: Error flashing subscriber unit. Device API error: 0xE0020085 Address: 0x1F870 Command: ADDR (0xE0222085); phone connected
I ran out of ideas on what to do next. One post i saw said try using a nand backup but I can't find one that will work.
Any help would be great. I really love my XOOM and I'm sad i can't fix it.
Hey guys
having some problem flashing a stock system.img to my phone. I try to get back to Mashmellow to get my phone back to stock. Currently its rooted and unlocked.
I downloaded the following zip:
Honor 8_Firmware_FRD-L09_Android 6.0_EMUI 4.1_C432B131_Western Europe.zip
I unzipped it and extracted all Images from the UPDATE.APP file.
Flashing cust.img, recovery.img, and recovery2.img is no problem. Problem is when flashing system.img
It always says
Code:
[[email protected] honor8]# fastboot flash system SYSTEM.img
target reported max download size of 471859200 bytes
sending sparse 'system' 1/6 (435393 KB)...
OKAY [ 11.022s]
writing 'system' 1/6...
FAILED (remote: sparse flash write failure)
finished. total time: 11.056s
[[email protected] honor8]#
[[email protected] honor8]# fastboot --version
fastboot version 7.1.1_r13
Phone is unlocked
FRP is unlocked
Flashing recovery works:
Code:
[[email protected] Downloads]# fastboot flash recovery twrp-3.1.0-0-frd.img
target reported max download size of 471859200 bytes
sending 'recovery' (24884 KB)...
OKAY [ 0.630s]
writing 'recovery'...
OKAY [ 0.327s]
finished. total time: 0.957s
TWRP tells me, that it cannot mount system. When restoring a backup with TWRP it works: it writes the system to the flash.
After restore I can reboot into Android again. Unfortunately I tried to installe the latest OTA (B380) which bricked my camera for some reason and makes the system itself kinda buggy.
Does anyone have an idea, how I get out of this situation?
Current Version: FRD-L09C432B360
It won't work this way. I wasted so much time trying. You have to use the rollback procedure to get your phone working again. Search the forum for it, it's been documented pretty well. Good luck
Idk if I searched longg enough. But I didn't see it yet. Is there any way to go back to stock when stuck at fastboot mode. Is there a firmware flash all bat ... I cannot get to recovery, I cannot boot in OS. Doesn't matter what I do. But I do know I need to see how fastboot flash the stock firmware.
If anyone has a clue or some info it would be GREATLY APPRECIATED!
Look for ADB sideload...
In fastboot? I didn't think you could do anything with adb in fastboot mode?
So if you are in fastboot mode this means you should still be able to fast boot flash.
When in fastboot don't select anything (on the screen with the option to start your phone), plug your phone into your computer and move (cd) to your platform tools folder. Open a terminal or ADMINISTRATOR powershell at this location.
You will need to download the TWRP fastboot image from on of the ROM threads below, it doesn't matter which one you get they both work. It may be easier to download the IMG from the unofficial twrp thread because there is a download link on the front page.
Now you want to run sudo fastboot flash boot twrp.img if you are using terminal or .\fastboot flash boot twrp.img if you are using powershell.
After that completes you should now select recovery mode on your screen and you SHOULD boot into twrp. My advice (it worked best for me) is in twrp complete wipe your phone then get the new TWRP installer zip and flash that. Then reboot to recovery and flash the stock ROM you download from asus.
Everything should work fine, feel free to ask me if you need more clarification. (Obligatory not responsible for bricks)
@Grom8 thank you for your detailed response. But I have tried multiple time to boot twrp. But it won't allow me to just goes right back to fastboot.. I will try to flash the official twrp tomorrow. My theory is that the partitions are messed up and won't allow me to do anything until they are sorted out. But I really don't know lol.
I had the same problem, try flashing the stock boot and system.img, then boot into twrp again
0Null0 said:
I had the same problem, try flashing the stock boot and system.img, then boot into twrp again
Click to expand...
Click to collapse
I will try tonight after work. Thank you
Ugh nothing worked now stuck in edl mode. Can connect to qcomm. Anyone know how to recover it from there lol
This was my solution
Ran into an issue where i could not get to anything but fastboot on the phone and could not flash TWRP from fastboot
here was the solution i came to
go to the following URL: it wont let me post URL's yet... go get the stock image from ASUS's website. should be a ZIP for ZenFone 6 (ZS630KL)
download the stock image. it will be a zip file
extract the zip file. we will come back to it later
download the latest version of python from here: still wont let me post links yet. google latest version of python
install python and give it all permissions it needs
download the payload dumper from here: (replace carrots on meat with com) mediafire.CarrotsOnMeat/file/pslxh616isribx6/payload_dumper.zip/file
extract the payload dumper
go back to the image that you downloaded and extracted, open the folder
the folder should be named something like UL-ASUS_I01WD-ASUS-16.1220.1909.193-1.1.1-user
inside the folder, there should be a file called "payload.bin"
copy the file
paste the file in the payload dumper file you extracted
make sure you are in the payload dumper folder at this point
Hold the SHIFT key and RIGHT CLICK somewhere in the folder that is empty space
select the OPEN POWERSHELL WINDOW HERE option
enter the following command:
python -m pip install -r requirements.txt
you should see something like the following:
Collecting protobuf==3.6.0 (from -r requirements.txt (line 1))
Downloading WEBSITEpackages/85/f8/d09e4bf21c4de65405ce053e90542e728c5b7cf296b9df36b0bf0488f534/protobuf-3.6.0-py2.py3-none-any.whl (390kB)
100% |████████████████████████████████| 399kB 5.1MB/s
Collecting six==1.11.0 (from -r requirements.txt (line 2))
Downloading WEBSITEpackages/67/4b/141a581104b1f6397bfa78ac9d43d8ad29a7ca43ea90a2d863fe3056e86a/six-1.11.0-py2.py3-none-any.whl
Requirement already satisfied: setuptools in c:\users\dperez\appdata\local\programs\python\python37-32\lib\site-packages (from protobuf==3.6.0->-r requirements.txt (line 1)) (40.8.0)
Installing collected packages: six, protobuf
Successfully installed protobuf-3.6.0 six-1.11.0
You are using pip version 19.0.3, however version 19.2.3 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
after you have done this command, run the following command:
python payload_dumper.py payload.bin
this one will take some time to run and it will extract all the .IMG files from the payload.bin file
you should see an output like this:
xbl
xbl_config
aop
devcfg
tz
cmnlib
cmnlib64
dsp
hyp
keymaster
abl
bluetooth
modem
boot
dtbo
system
vendor
vbmeta
asusfw
qupfw
uefisecapp
xrom
when this is finished, hold control and select the boot.img file && and the system.img file
copy them
paste them where you have the fastboot tools
navigate to that folder in command prompt
paste the following:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
the following is output:
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot devices
ABCDEFG1234567 fastboot
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_a boot.img
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.536s]
writing 'boot_a'...
OKAY [ 1.889s]
finished. total time: 4.434s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_b boot.img
target reported max download size of 805306368 bytes
sending 'boot_b' (98304 KB)...
OKAY [ 2.309s]
writing 'boot_b'...
OKAY [ 1.850s]
finished. total time: 4.166s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_a system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_a'...
OKAY [ 19.418s]
sending sparse 'system_a' 1/5 (777195 KB)...
OKAY [ 19.089s]
writing 'system_a' 1/5...
OKAY [ 0.003s]
sending sparse 'system_a' 2/5 (712614 KB)...
OKAY [ 24.339s]
writing 'system_a' 2/5...
OKAY [ 0.003s]
sending sparse 'system_a' 3/5 (746935 KB)...
OKAY [ 22.488s]
writing 'system_a' 3/5...
OKAY [ 0.016s]
sending sparse 'system_a' 4/5 (778963 KB)...
OKAY [ 25.393s]
writing 'system_a' 4/5...
OKAY [ 0.007s]
sending sparse 'system_a' 5/5 (444941 KB)...
OKAY [ 26.145s]
writing 'system_a' 5/5...
OKAY [ 0.003s]
finished. total time: 136.949s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_b system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_b'...
OKAY [ 13.330s]
sending sparse 'system_b' 1/5 (777195 KB)...
OKAY [ 19.158s]
writing 'system_b' 1/5...
OKAY [ 0.006s]
sending sparse 'system_b' 2/5 (712614 KB)...
OKAY [ 24.303s]
writing 'system_b' 2/5...
OKAY [ 0.018s]
sending sparse 'system_b' 3/5 (746935 KB)...
OKAY [ 22.501s]
writing 'system_b' 3/5...
OKAY [ 0.017s]
sending sparse 'system_b' 4/5 (778963 KB)...
OKAY [ 25.291s]
writing 'system_b' 4/5...
OKAY [ 0.003s]
sending sparse 'system_b' 5/5 (444941 KB)...
OKAY [ 26.169s]
writing 'system_b' 5/5...
OKAY [ 0.005s]
finished. total time: 130.843s
you should now be able to get into the stock recovery, from there, you can either use ADB sideload to flash back to the stock firmware, or you can put it on an SD card and flash it from there, which is what i did. Hope this was helpful.
---------- Post added at 08:21 PM ---------- Previous post was at 08:01 PM ----------
st3wart said:
Ugh nothing worked now stuck in edl mode. Can connect to qcomm. Anyone know how to recover it from there lol
Click to expand...
Click to collapse
i posted how i fixed mine in detail
My problem now is I cannot even get to fastboot mode. It's stuck in edl mode. Will this fix work for that?
dperez2010 said:
Ran into an issue where i could not get to anything but fastboot on the phone and could not flash TWRP from fastboot
here was the solution i came to
Click to expand...
Click to collapse
Thank you so much! I thought I just bricked my new phone.
st3wart said:
My problem now is I cannot even get to fastboot mode. It's stuck in edl mode. Will this fix work for that?
Click to expand...
Click to collapse
My phone shows up as "Qualcomm HS-USB QDLoader 9008" in the device manager, which I think means it is stuck in edl mode similar to your situation?
Did you manage to find a fix for that?
Nope not yet. Still looking and waiting to see if anyone has a fix.
st3wart said:
Nope not yet. Still looking and waiting to see if anyone has a fix.
Click to expand...
Click to collapse
I've found this thread: /zenfone-6-2019/how-to/qdloader-brick-t3980165
But as I am a complete noob, I don't know whether I should just run a script, of which I have no understanding of what it does.
Don't even know for sure if it could fix the issue.
Thanks man I'll check it out when home from work. I'll shoot you an update if I can get it fixed!
Yes yes YES! It fixed the phone and brought it back to life!!!! Amazing ...thank you thank you thank you.
Follow the instructions as he put them. Works like a charm!
Hello,
I have a similar problem. My phone is turned off and on the fastboot mode screen. Normal keys with volume keys, recovery mode, open, restart, even if I try to reboot on this screen opens. I tried to connect and format the computer, but I do not install all the drivers and files, but computers do not see my phone. Can you find me a solution?
Hello dperez2010,
your method seems to work, but i get the following error
fastboot flash system_a system.img
Invalid sparse file format at header magic
Sending sparse 'system_a' 1/5 (773136 KB) OKAY [ 17.209s]
Writing 'system_a' FAILED (remote: 'Partition not found')
fastboot: error: Command failed
Do you or does anyone know whats going on here?
/zenfone-6-2019/how-to/guide-unbricking-zs630kl-t3998767
Here's a hint
file size too big, can't flash or boot Into TWRP
dperez2010 said:
Ran into an issue where i could not get to anything but fastboot on the phone and could not flash TWRP from fastboot
here was the solution i came to
go to the following URL: it wont let me post URL's yet... go get the stock image from ASUS's website. should be a ZIP for ZenFone 6 (ZS630KL)
download the stock image. it will be a zip file
extract the zip file. we will come back to it later
download the latest version of python from here: still wont let me post links yet. google latest version of python
install python and give it all permissions it needs
download the payload dumper from here: (replace carrots on meat with com) mediafire.CarrotsOnMeat/file/pslxh616isribx6/payload_dumper.zip/file
extract the payload dumper
go back to the image that you downloaded and extracted, open the folder
the folder should be named something like UL-ASUS_I01WD-ASUS-16.1220.1909.193-1.1.1-user
inside the folder, there should be a file called "payload.bin"
copy the file
paste the file in the payload dumper file you extracted
make sure you are in the payload dumper folder at this point
Hold the SHIFT key and RIGHT CLICK somewhere in the folder that is empty space
select the OPEN POWERSHELL WINDOW HERE option
enter the following command:
python -m pip install -r requirements.txt
you should see something like the following:
Collecting protobuf==3.6.0 (from -r requirements.txt (line 1))
Downloading WEBSITEpackages/85/f8/d09e4bf21c4de65405ce053e90542e728c5b7cf296b9df36b0bf0488f534/protobuf-3.6.0-py2.py3-none-any.whl (390kB)
100% |████████████████████████████████| 399kB 5.1MB/s
Collecting six==1.11.0 (from -r requirements.txt (line 2))
Downloading WEBSITEpackages/67/4b/141a581104b1f6397bfa78ac9d43d8ad29a7ca43ea90a2d863fe3056e86a/six-1.11.0-py2.py3-none-any.whl
Requirement already satisfied: setuptools in c:\users\dperez\appdata\local\programs\python\python37-32\lib\site-packages (from protobuf==3.6.0->-r requirements.txt (line 1)) (40.8.0)
Installing collected packages: six, protobuf
Successfully installed protobuf-3.6.0 six-1.11.0
You are using pip version 19.0.3, however version 19.2.3 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.
after you have done this command, run the following command:
python payload_dumper.py payload.bin
this one will take some time to run and it will extract all the .IMG files from the payload.bin file
you should see an output like this:
xbl
xbl_config
aop
devcfg
tz
cmnlib
cmnlib64
dsp
hyp
keymaster
abl
bluetooth
modem
boot
dtbo
system
vendor
vbmeta
asusfw
qupfw
uefisecapp
xrom
when this is finished, hold control and select the boot.img file && and the system.img file
copy them
paste them where you have the fastboot tools
navigate to that folder in command prompt
paste the following:
fastboot flash boot_a boot.img
fastboot flash boot_b boot.img
fastboot flash system_a system.img
fastboot flash system_b system.img
the following is output:
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot devices
ABCDEFG1234567 fastboot
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_a boot.img
target reported max download size of 805306368 bytes
sending 'boot_a' (98304 KB)...
OKAY [ 2.536s]
writing 'boot_a'...
OKAY [ 1.889s]
finished. total time: 4.434s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash boot_b boot.img
target reported max download size of 805306368 bytes
sending 'boot_b' (98304 KB)...
OKAY [ 2.309s]
writing 'boot_b'...
OKAY [ 1.850s]
finished. total time: 4.166s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_a system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_a'...
OKAY [ 19.418s]
sending sparse 'system_a' 1/5 (777195 KB)...
OKAY [ 19.089s]
writing 'system_a' 1/5...
OKAY [ 0.003s]
sending sparse 'system_a' 2/5 (712614 KB)...
OKAY [ 24.339s]
writing 'system_a' 2/5...
OKAY [ 0.003s]
sending sparse 'system_a' 3/5 (746935 KB)...
OKAY [ 22.488s]
writing 'system_a' 3/5...
OKAY [ 0.016s]
sending sparse 'system_a' 4/5 (778963 KB)...
OKAY [ 25.393s]
writing 'system_a' 4/5...
OKAY [ 0.007s]
sending sparse 'system_a' 5/5 (444941 KB)...
OKAY [ 26.145s]
writing 'system_a' 5/5...
OKAY [ 0.003s]
finished. total time: 136.949s
C:\Users\surface\Desktop\Asus\Fastboot\fastboot\tools>fastboot flash system_b system.img
target reported max download size of 805306368 bytes
Invalid sparse file format at header magic
erasing 'system_b'...
OKAY [ 13.330s]
sending sparse 'system_b' 1/5 (777195 KB)...
OKAY [ 19.158s]
writing 'system_b' 1/5...
OKAY [ 0.006s]
sending sparse 'system_b' 2/5 (712614 KB)...
OKAY [ 24.303s]
writing 'system_b' 2/5...
OKAY [ 0.018s]
sending sparse 'system_b' 3/5 (746935 KB)...
OKAY [ 22.501s]
writing 'system_b' 3/5...
OKAY [ 0.017s]
sending sparse 'system_b' 4/5 (778963 KB)...
OKAY [ 25.291s]
writing 'system_b' 4/5...
OKAY [ 0.003s]
sending sparse 'system_b' 5/5 (444941 KB)...
OKAY [ 26.169s]
writing 'system_b' 5/5...
OKAY [ 0.005s]
finished. total time: 130.843s
you should now be able to get into the stock recovery, from there, you can either use ADB sideload to flash back to the stock firmware, or you can put it on an SD card and flash it from there, which is what i did. Hope this was helpful.
---------- Post added at 08:21 PM ---------- Previous post was at 08:01 PM ----------
i posted how i fixed mine in detail
Click to expand...
Click to collapse
"file size", basically our system.img is not being downloaded by the phone due to the large (3.6G) filesize
"fastboot flash system_a ./system.img
Sending 'system_a' (3670016 KB) FAILED (remote: 'requested download size Is more then the max allowed')
feastboot error: command failed