Nexus 7 boot.img flash fails with FileWriteFailed - Nexus 7 Q&A, Help & Troubleshooting

Device: Nexus 7 (2012) WIFI only
After 4.3 update device started locking up and had to repeatedly long-press power to reboot. Factory defaut fixed first time, Second time (because it started happening again) could not recover from factory default. boot.img will not install and returns a (remote: FileWriteFailed) error.
I've tried multiple cables, PCs, and toolkits with no luck.
I can load bootloaders without issue.
I can format and load system, userdata, recovery (have loaded stock, TWRP, CWM recoveries) all appear to load without issue and work fine but haven't been able to fix this issue.
Once the boot.img flash is attempted, the device locks up hard and a long-press of power is needed to bring it back.
I can boot to Google screen with (Start, Power off, Recovery mode, Restart bootloader options) or directly to bootloader without issue.
First tried restoring 4.3 factory, but have since been trying 4.2.2 factory using Nexus Root Toolkit, Nexus 7 Toolkit, and a lot of SDK command line of fastboot commands. I can run ADB commands if I first get into recovery.
Is there a option I can tickle or something else anyone knows I can try? I'm beginning to think the boot sector of the flash is defective (if this makes sense).
Here's an example of a fastboot update. It hasn't mattered the method, the outcome is always identical. It fails at boot.img flash write failure.
>fastboot devices
015d490651281e0e fastboot
>fastboot erase boot
erasing 'boot'...
OKAY [ 1.186s]
finished. total time: 1.186s
>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.998s]
finished. total time: 0.998s
>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.796s]
finished. total time: 0.796s
>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 4.649s]
finished. total time: 4.649s
>fastboot flash bootloader bootloader-grouper-4.18.img
sending 'bootloader' (2096 KB)...
OKAY [ 0.312s]
writing 'bootloader'...
OKAY [ 9.875s]
finished. total time: 10.202s
>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.031s]
finished. total time: 0.031s
>fastboot -w update image-nakasi-jdq39.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.18
Baseband Version.....: N/A
Serial Number........: 015d490651281e0e
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4944 KB)...
OKAY [ 0.686s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 5.210s
>

This issue has been resolved. The Nexus 7 was returned to Asus support and the motherboard was replaced under warranty.

Related

[Q] Can't escape fastboot

I am trying to flash my Nexus 7 entirely back to stock 4.3. I was following the guide that is sticky'd in this thread to flash the Google image. This is these are the errors I get:
Code:
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 2.532s]
finished. total time: 2.535s
C:\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.033s
C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.266s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.415s
Also the bootloader keeps freezing on me after I attempt this. I also am unable to restart bootloader by command or the selection, it just goes to a black screen and "fastboot devices" gives me ????????????? instead of my device ID. I can fix this by turning it off and booting back into the bootloader and it will properly display my device ID.
It is unlocked and on 4.23 that's listed there. What else can I do?
engagedtosmile - You should post this question in comminus' stickied thread. I read all 54 pages of it and he's very good at diagnosing the problem and helping to get it resolved.
engagedtosmile said:
I am trying to flash my Nexus 7 entirely back to stock 4.3. I was following the guide that is sticky'd in this thread to flash the Google image. This is these are the errors I get:
Code:
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
OKAY [ 2.532s]
finished. total time: 2.535s
C:\android-sdk\platform-tools>fastboot erase cache
erasing 'cache'...
OKAY [ 0.032s]
finished. total time: 0.033s
C:\android-sdk\platform-tools>fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase system
erasing 'system'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot erase userdata
erasing 'userdata'...
OKAY [ 0.021s]
finished. total time: 0.022s
C:\android-sdk\platform-tools>fastboot flash bootloader bootloader-grouper-4.23.
img
sending 'bootloader' (2100 KB)...
OKAY [ 0.266s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.415s
Also the bootloader keeps freezing on me after I attempt this. I also am unable to restart bootloader by command or the selection, it just goes to a black screen and "fastboot devices" gives me ????????????? instead of my device ID. I can fix this by turning it off and booting back into the bootloader and it will properly display my device ID.
It is unlocked and on 4.23 that's listed there. What else can I do?
Click to expand...
Click to collapse
Hi, engagedtosmile...
Yeah.. there is a known issue with the v4.23 bootloader.
Your problem could be the bootloader v4.23 from build JWR66Y.... try flashing the bootloader v4.23 from build JWR66V.
See this thread for details (a couple of people have uploaded the bootloader v4.23 from build JWR66V, for both 'grouper' and 'tilapia' Nexus 7's on this thread - when I find the time, I'm going to upload them myself... so I don't have to keep hunting out the link).
Hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, engagedtosmile...
Yeah.. there is a known issue with the v4.23 bootloader.
Your problem could be the bootloader v4.23 from build JWR66Y.... try flashing the bootloader v4.23 from build JWR66V.
See this thread for details (a couple of people have uploaded the bootloader v4.23 from build JWR66V, for both 'grouper' and 'tilapia' Nexus 7's on this thread - when I find the time, I'm going to upload them myself... so I don't have to keep hunting out the link).
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Thanks but I have done that as instructed in the sticky post (I ran into the error before but was able to flash it fine). I thought I would try to Lock the bootloader and unlock it again, it locked fine but now errors out when unlocking.
I am back to step 1 it seems.:crying:
engagedtosmile said:
Thanks but I have done that as instructed in the sticky post (I ran into the error before but was able to flash it fine). I thought I would try to Lock the bootloader and unlock it again, it locked fine but now errors out when unlocking.
I am back to step 1 it seems.:crying:
Click to expand...
Click to collapse
Have you tried changing to a different USB port on your PC... or a different USB cable, or even a different PC.
I know I've had difficulties, when trying to send/write to 'system', and changing to a different USB port usually resolves the problem... so it might be worth a shot.
Gotta be really careful when flashing bootloaders, as one false move can cause hardbrick, which is pretty grim.
Rgrds,
Ged.
GedBlake said:
Have you tried changing to a different USB port on your PC... or a different USB cable, or even a different PC.
I know I've had difficulties, when trying to send/write to 'system', and changing to a different USB port usually resolves the problem... so it might be worth a shot.
Gotta be really careful when flashing bootloaders, as one false move can cause hardbrick, which is pretty grim.
Rgrds,
Ged.
Click to expand...
Click to collapse
I will have to try it on my home PC later. I have tried different cables and ports on my work PC to no avail. It just won't unlock at all now.

Help with update via PC

I i started to "re-update" my phone because of issues of OTA. I did everuthing fine but now after i made the all the "fastboot erases" i cant instal the android.
I was with stock rom unrooted, so following a video i went to bootloader like i saw , i connected the phone on my pc, and double-click on "flash-all" buit i'm getting a problem with images of 4.4 and 4.3
...
FAILED (remote: Already Unlocked)
finished. total time: 0.006s
erasing 'boot'...
OKAY [ 0.006s]
finished. total time: 0.008s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.021s]
finished. total time: 0.022s
erasing 'recovery'...
OKAY [ 0.005s]
finished. total time: 0.006s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.031s]
finished. total time: 0.033s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.191s]
finished. total time: 0.193s
sending 'bootloader' (2100 KB)...
OKAY [ 0.073s]
writing 'bootloader'...
FAILED (remote: invalid bootloader image
)
finished. total time: 0.086s
rebooting into bootloader...
OKAY [ 0.003s]
finished. total time: 0.005s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30d
Baseband Version.....: M9615A-CEFWMAZM-2.0.1700.97
Serial Number........: 01cd03df4b0e7962
--------------------------------------------
checking product...
FAILED
Device product is 'mako'.
Update requires 'grouper'.
finished. total time: 0.030s
Press any key to exit...
my phone doesnt even turn on anymore, what should i do
alan966 said:
Device product is 'mako'.
Update requires 'grouper'.
Click to expand...
Click to collapse
Well, that seems to be your problem. Looks like you flashed the nexus 7 images on your nexus 4...not a good thing.
I would first try downloading the CORRECT images and flashing those.
Chromium_ said:
Well, that seems to be your problem. Looks like you flashed the nexus 7 images on your nexus 4...not a good thing.
I would first try downloading the CORRECT images and flashing those.
Click to expand...
Click to collapse
wtf ? i downloaded this image from the google and only now i saw that everytime i clicked on the nexus 4 images it brings me to nexus 7 images
I'll try again with the correct images and report
UPDATE: i did it, kit kat is running in my phone but now google services does not work anymore with my wifi only with my 3g, cant download any app, acess any kind of google app like youtube, gmail, maps...

Bootloop and can't fastboot flash image

I've been having issues with my Nexus 7. The first time it was stuck in a boot loop not making it past the Google logo. I booted into the bootloader, flashed a new factory image, and I was off.
Then a few weeks later the same thing happened. Only this time, I can't get a factory image to flash. Any ideas?
I think my flash memory is gone bad.
carlowahlstedt said:
I've been having issues with my Nexus 7. The first time it was stuck in a boot loop not making it past the Google logo. I booted into the bootloader, flashed a new factory image, and I was off.
Then a few weeks later the same thing happened. Only this time, I can't get a factory image to flash. Any ideas?
I think my flash memory is gone bad.
Click to expand...
Click to collapse
Possibly... or possibly not.
Hi, carlowahlstedt...
carlowahlstedt said:
...Only this time, I can't get a factory image to flash...
Click to expand...
Click to collapse
It might be helpful if you could be more specific... like, what errors did you encounter?... how did you go about flashing a factory image?... did you use a toolkit, like Wugs?... or just regular fastboot?
For somebody to assist you in diagnosing a given problem, in the hope of fixing it... they need all the facts available... no matter how seemingly innocuous or irrelevant.
The 'devil', as it is said, resides very much in the 'detail'.
Rgrds,
Ged.
Thanks Ged. I guess I was kinda hoping for a tool that could some how test the memory.
Here's the output from the toolkit:
********************************************************************************
* Universal Nexus Linux Toolkit v2.4.2 by tatelucas *
********************************************************************************
Flash Google Factory Image
Before starting the process your device must be in Bootloader Mode.
In the following instructions you will learn how to do it:
1. Power off the device.
2. Press and hold Volume Down, then press and hold Power.
3. Your device screen should show an image of an opened android.
You're now in the Bootloader Mode! If you don't see the image,
you must follow the instructions again.
4. Please connect the device to your PC via USB.
5. Do you want to start the process? [Y/N]: Y
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.015s
erasing 'recovery'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
finished. total time: 0.015s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 0.019s]
finished. total time: 0.019s
sending 'bootloader' (2100 KB)...
OKAY [ 0.276s]
writing 'bootloader'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.247s
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting into bootloader...​
You'll notice that it doesn't have anything past the "rebooting into bootloader". The screen is locked up on the device and nothing is happening. After sometime I manually reboot into bootloader and get:
ERROR: usb_write failed with status e00002ed
FAILED (command write failed (No such file or directory))
finished. total time: 174.893s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 0## (removed this)
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.020s]
sending 'boot' (4990 KB)...
OKAY [ 0.682s]
writing 'boot'...
FAILED (remote: (AccessDenied))
finished. total time: 2.378s​
I also seems to have lost recovery mode? If I click on Recovery Mode in the bootloader it just flashes the text and that's it.
Not sure what else would be helpful to see/know. Thanks for the help.
Google search
android factory images
Grab the latest for your device
Extract all
fastboot flash bootloader nameofbootloader.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now either click the flashall.bat or, as I would recommend, do it manually
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash data userdata.img
fastboot flash recovery recovery.img
(Feel free to use twrp or cwm if you don't want stock)
Now reboot
Side note, stay away from toolkits whenever possible
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Google search
android factory images
Grab the latest for your device
Extract all
fastboot flash bootloader nameofbootloader.img
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
Now either click the flashall.bat or, as I would recommend, do it manually
fastboot flash system system.img
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash data userdata.img
fastboot flash recovery recovery.img
(Feel free to use twrp or cwm if you don't want stock)
Now reboot
Side note, stay away from toolkits whenever possible
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks for the help. I downloaded the latest image for the Nexus 7 Wifi (NOT 2013) and attempted to flash the bootloader but I get this:
sending 'bootloader' (2100 KB)...
OKAY [ 0.333s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.466s​
I found this thread, which I took to mean to download the bootloader from the 4.3 image. I did that but get the same result.
Also, it shows that I already have 4.23 so it seems like I wouldn't need to flash this in the first place?
Thanks again for the help.
Then skip the bootloader but do the rest of the steps
And you are just using fastboot right? No toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Then skip the bootloader but do the rest of the steps
And you are just using fastboot right? No toolkits
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Nope, no toolkits.
Looks like the erase system command is having issues writing as well. Included the reference to the command so you could see that as well:
platform-tools carlo.wahlstedt$ ./fastboot erase system -w
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.015s]
erasing 'userdata'...
OKAY [ 0.024s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 6453985280
Block size: 4096
Blocks per group: 32768
Inodes per group: 8048
Inode size: 256
Journal blocks: 24620
Label:
Blocks: 1575680
Block groups: 49
Reserved block group size: 391
Created filesystem with 11/394352 inodes and 52512/1575680 blocks
sending 'userdata' (102525 KB)...
writing 'userdata'...
FAILED (remote: (FileWriteFailed))
finished. total time: 81.408s​
Looks like data partition is corrupt, hopefully fixable but you will need adb shell. So continue on with the steps above and hopefully you can get into either recovery or os, then you can use dd or fsck or something to format, well hopefully so long as it is not too corrupt
Sent from my Nexus 4 using XDA Premium 4 mobile app
demkantor said:
Looks like data partition is corrupt, hopefully fixable but you will need adb shell. So continue on with the steps above and hopefully you can get into either recovery or os, then you can use dd or fsck or something to format, well hopefully so long as it is not too corrupt
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I don't think it's looking good:
platform-tools carlo.wahlstedt$ ./fastboot erase boot
erasing 'boot'...
OKAY [ 0.015s]
finished. total time: 0.015s
platform-tools carlo.wahlstedt$ ./fastboot erase recovery
erasing 'recovery'...
OKAY [ 0.015s]
finished. total time: 0.015s
platform-tools carlo.wahlstedt$ ./fastboot flash system nakasi-kot49h/image-nakasi-kot49h/system.img
erasing 'system'...
OKAY [ 0.011s]
sending 'system' (625382 KB)...
OKAY [ 86.819s]
writing 'system'...
FAILED (remote: (FileWriteFailed))
finished. total time: 152.721s
platform-tools carlo.wahlstedt$ ./fastboot flash boot nakasi-kot49h/image-nakasi-kot49h/boot.img
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
^C (I forced a reboot here after waiting a long time)
platform-tools carlo.wahlstedt$ ./fastboot flash boot nakasi-kot49h/image-nakasi-kot49h/boot.img
sending 'boot' (4992 KB)...
OKAY [ 0.818s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.374s
platform-tools carlo.wahlstedt$ ./fastboot flash data nakasi-kot49h/image-nakasi-kot49h/userdata.img
sending 'data' (104289 KB)...
OKAY [ 14.212s]
writing 'data'...
FAILED (remote: Invalid Partition Name.)
finished. total time: 14.227s
platform-tools carlo.wahlstedt$ ./fastboot flash recovery nakasi-kot49h/image-nakasi-kot49h/recovery.img
sending 'recovery' (5532 KB)...
OKAY [ 0.893s]
writing 'recovery'...
FAILED (remote: (FileWriteFailed))
finished. total time: 2.448s
platform-tools carlo.wahlstedt$ ./fastboot reboot
ERROR: could not clear input pipe; result e00002ed, ignoring...
ERROR: could not clear output pipe; result e00002ed, ignoring....
rebooting... (I forced a reboot here)
ERROR: usb_write failed with status e00002ed
finished. total time: 106.130s​
It's also "locking up" on most every command that I send. By that I mean, you can't move through the bootloader menu.
Any other thoughts?
Sorry to say but I feel your nand is fried... If you still have warranty you should claim it but as of now I would give it 50/50 that even JTAG would work to resurrect you tab
Sorry for the bad news, best of luck
Sent from my Nexus 7 using XDA Premium 4 mobile app
Well that sucks. Thanks for the help.

[Q]Restore android to nexus 7 (grouper) issues

[email protected]:/home/zarkpafilis/Desktop/razor-kot49h# bash flash-all.sh
sending 'bootloader' (3911 KB)...
OKAY [ 0.751s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.990s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: 4.23
Baseband Version.....: N/A
Serial Number........: 015d4a5f0020180c
--------------------------------------------
checking product...
FAILED
Device product is 'grouper'.
Update requires 'flo'.
finished. total time: 0.177s
[email protected]:/home/zarkpafilis/Desktop/razor-kot49h#
The device is nexus 7 32 gb wifi (grouper). I cant find any grouper image here , so I downloaded the latest razor one. I bought the tablet in 2013(xmas)
[email protected]:/home/zarkpafilis/Desktop/razor-kot49h# ls
bootloader-flo-flo-04.02.img flash-all.sh image-razor-kot49h.zip
flash-all.bat flash-base.sh
[email protected]:/home/zarkpafilis/Desktop/razor-kot49h#
Im trying to boot nagasig latest. It seems it may work
It did not: - Now im stuck with a bootloader mode device that fails to boot!
[email protected]:/home/zarkpafilis/Desktop# cd nakasig-kot49h
[email protected]:/home/zarkpafilis/Desktop/nakasig-kot49h# bash flash-all.sh
\...
(bootloader) Bootloader is already unlocked
OKAY [ 0.591s]
finished. total time: 0.591s
erasing 'boot'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.132s]
finished. total time: 0.133s
erasing 'recovery'...
OKAY [ 0.032s]
finished. total time: 0.032s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.193s]
finished. total time: 0.194s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.616s]
finished. total time: 8.616s
sending 'bootloader' (3911 KB)...
OKAY [ 0.760s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.987s
rebooting into bootloader...
OKAY [ 0.021s]
finished. total time: 0.021s
sending 'radio' (16384 KB)...
FAILED (command write failed (Bad file descriptor))
finished. total time: 0.000s
rebooting into bootloader...
archive does not contain 'boot.sig' - it stayed there
Now the tablet is not recognized with adb devices!
Fastboot recognizes it as blah blah
I managed to get it working again , but it misses flo and tiltapia (or something) - I downloaded the wifi versions of the image , the latest versions.
Downloading nakasi earliest version - It is sending system , it should work.
I couldnt do adb reboot-fastboot so I manually refreshed the fastboot again and then it got detected
It finisehn , my tablet is back on life - I will leave this thread so others can see it. Thanks people for doing nothing!
I dont know why but I keep solving stuff myself without help on forums
Sorry couldnt post links
I used nakasi-jzo54k

Nexus 7 (2013 Mobile) fails to boot; can't enter Recovery mode; flash write failure

My Nexus 7 (2013 Mobile) was rooted and updated to stock Android 6.0 a year ago, no 3rd party ROM/recovery is installed. Last week while checking emails, it rebooted suddenly then remained at Google letters and unlock icon, I can enter fastboot mode by pressing power and volume- buttons together, the last line shows status unlocked; then if select "Recovery mode", it reboots then shows a dead robot with an exclamation mark only. I downloaded the latest factory image "razorg-mob30x", connect it to my PC and enter adb command "flash-all.bat" (I modified the bat file by removing -w, so it won't wipe the user data), then it shows: FAILED (remote: flash write failure)
sending 'bootloader' (3915 KB)...
OKAY [ 0.135s]
writing 'bootloader' ...
FAILED (remote: flash write failure)
finished. total time 90.811s
rebooting into bootloader...
OKAY [ 0.010s]
finished. total time 0.012s
sending 'radio' (76038 KB)...
OKAY [ 2.393s]
writing 'radio' ...
FAILED (remote: flash write failure)
finished. total time 92.549s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time 0.013s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
----------------------------------------------------
Bootloader Version...: FLO-04.08
Basedband Version...: DEB-Z00_2.44.0_0213
Serial Number................: 0879222a
----------------------------------------------------
checking product...
OKAY [ 0.005s]
checking version-bootloader...
OKAY [ 0.006s]
checking version-baseband...
OKAY [ 0.006s]
sending 'boot' (7422 KB)
OKAY [ 0.243s]
writing 'boot' ...
FAILED (remote: flash write failure)
finished. total time 90.151s
Press any key to exit...
Click to expand...
Click to collapse
What else I can do to resuce my pad? Does this mean the memory is physically damaged?
Please advise. Your help is much appreciated.

Categories

Resources