[Q] Any way around "FAILED (remote: flash write failure)" ?? - Nexus 7 (2013) Q&A

I'm stuck at the Google logo and can't flash anything. Anyone know why, or something I can try?
-------------------------
fastboot -w update image-razor-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.02
Baseband Version.....: none
Serial Number........: 084813df
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7018 KB)...
OKAY [ 0.233s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 90.118s

I'm pretty sure this is a hardware related error...
Sent from my Nexus 7 using Tapatalk

Try installing the full factory image instead of an ota update.
https://dl.google.com/dl/android/aosp/razor-kot49h-factory-ebb4918e.tgz
You could try adb sideload instead also
adb sideload update.zip

And if you can't find a fix for it you could always donate it
Sent from my Nexus 7 using Tapatalk

Related

[Q] Getting back to stock

Hey!
So I finally managed to install this rom:
http://forum.xda-developers.com/showthread.php?p=22487053#post22487053
But I actually prefer stock for now, so I am wondering if someone can help me get back to stock rom? I have a GSM version.
I have tried the guides, but they result in a bootloop, also my recovery mode just goes into an android with a red "!" above it's chest.
Please help
I followed the "Get back to stock" instructions from here (http://forum.xda-developers.com/showthread.php?p=22492630#post22492630) to the letter, and I always end up in a bootloop What am I doing wrong?
This is my cmd log:
C:\Users\Sebz4n>fastboot-windows devices
---Took away my device ID--- fastboot
C:\Users\Sebz4n>fastboot-windows flash bootloader bootloader-maguro-primekj10.im
g
sending 'bootloader' (2308 KB)... OKAY
writing 'bootloader'... OKAY
C:\Users\Sebz4n>fastboot-windows reboot-bootloader
rebooting into bootloader... OKAY
C:\Users\Sebz4n>fastboot-windows flash radio radio-maguro-i9250xxkk1.img
sending 'radio' (12288 KB)... OKAY
writing 'radio'... OKAY
C:\Users\Sebz4n>fastboot-windows reboot-bootloader
rebooting into bootloader... OKAY
C:\Users\Sebz4n>fastboot-windows -w update image-yakju-itl41f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...:
getvar:version-baseband FAILED (command write failed (Unknown error))
C:\Users\Sebz4n>fastboot-windows -w update image-yakju-itl41f.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: PRIMEKJ10
Baseband Version.....: I9250XXKK1
Serial Number........: 0149AE7C11021010
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (4054 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (4386 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (317798 KB)... OKAY
writing 'system'... OKAY
erasing 'userdata'... FAILED (unknown status code)
C:\Users\Sebz4n>
Click to expand...
Click to collapse
Please can someone help me, I really want to get back to stock so I can start using my brand new phone!
Make sure that your .zip isn't corrupted - if possible, verify the MD5 hash against the site you downloaded the zip from.
Edit, also try extracting the .img files from your zip and flashing those individually.
Code:
fastboot flash system system.img
Maybe this thread can help? http://forum.xda-developers.com/showthread.php?t=1391881
http://forum.xda-developers.com/showthread.php?p=22102956
Hope it's helpful. I'm on yakju (dont know if it works for people that were yakju variants and then converted, just saying, since there is a thread for converting, i guess i should read it sometime)
Edit: i did not see OP was using windows. Nevertheless, i agree with previous poster procedure.

[Q] Trying to restore, stuck at 'erasing system'

I'm trying to flash the KRT16S factory image onto my flo in adb/fastboot. I got the image from the repository thread in the flo general forum here, unzipped with 7-Zip, etc etc.
I ran
Code:
fastboot -w update image-razor-krt16s.zip
And I get to:
Code:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-04.01
Baseband Version.....: none
Serial Number........: [hidden for this post]
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
OKAY [ 0.004s]
sending 'boot' (7014 KB)...
OKAY [ 0.228s]
writing 'boot'...
OKAY [ 0.377s]
sending 'recovery' (7560 KB)...
OKAY [ 0.244s]
writing 'recovery'...
OKAY [ 0.291s]
erasing 'system'...
...and it's been hanging on 'erasing 'system' for about 15-20 minutes now. I know the sig missing stuff is typical because it's the wi-fi version and not the LTE. Tablet's still on the bootloader screen, and shows the bootloader is the proper version. Should I retry it and do flash-all bat script instead? All my stock image files were extracted to my platform-tools where they should be, including the flash all bat and sh.
Edit: Solved. I think! Touch and go for a moment there when I thought ADB couldn't 'see' my Flo.

Problems flashing system images for the Pixel XL

So I'm pretty accustomed to flashing system images and sideloading OTAs, but for some reason things are just not working for me on my Pixel XL.
Every time I run the "flash-all.bat" script (with the -w removed to preserve data) I can never seem to update properly, I get the following:
Code:
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.776s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.064s]
finished. total time: 1.844s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.356s]
writing 'radioa'...
OKAY [ 0.952s]
finished. total time: 2.322s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: [removed]
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26405 KB)...
OKAY [ 0.680s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.139s
Press any key to exit...
I am on the original stock NDE63L, and I have had failures trying to flash both NDE63P (a few weeks ago) and NDE63X (today's build).
Additionally, ever since this process has failed for me, I am unable to boot into recovery, I just get the picture of the dead Android guy. So because of this I can't adb sideload the OTA as an alternative.
My bootloader is unlocked and I have rooted just fine, boot_a is listed as my active boot slot, but I have no idea why the system flash keeps failing.
Any thoughts as to why this is happening? Alternatively, is there a way to restore my recovery so I can try adb sideloading the OTA?
ChrisG683 said:
So I'm pretty accustomed to flashing system images and sideloading OTAs, but for some reason things are just not working for me on my Pixel XL.
Every time I run the "flash-all.bat" script (with the -w removed to preserve data) I can never seem to update properly, I get the following:
Code:
target reported max download size of 536870912 bytes
sending 'bootloadera' (32820 KB)...
OKAY [ 0.776s]
writing 'bootloadera'...
(bootloader) Valid bootloader version.
OKAY [ 1.064s]
finished. total time: 1.844s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 5.009s
target reported max download size of 536870912 bytes
sending 'radioa' (57048 KB)...
OKAY [ 1.356s]
writing 'radioa'...
OKAY [ 0.952s]
finished. total time: 2.322s
rebooting into bootloader...
OKAY [ 0.014s]
finished. total time: 0.015s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
--------------------------------------------
Bootloader Version...: 8996-012001-1608281716
Baseband Version.....: 8996-012511-1609191801
Serial Number........: [removed]
--------------------------------------------
checking product...
OKAY [ 0.050s]
checking version-bootloader...
OKAY [ 0.049s]
checking version-baseband...
OKAY [ 0.048s]
sending 'boota' (26405 KB)...
OKAY [ 0.680s]
writing 'boota'...
(bootloader) Flashing active slot "_a"
FAILED (remote: partition [boota] doesn't exist)
finished. total time: 1.139s
Press any key to exit...
I am on the original stock NDE63L, and I have had failures trying to flash both NDE63P (a few weeks ago) and NDE63X (today's build).
Additionally, ever since this process has failed for me, I am unable to boot into recovery, I just get the picture of the dead Android guy. So because of this I can't adb sideload the OTA as an alternative.
My bootloader is unlocked and I have rooted just fine, boot_a is listed as my active boot slot, but I have no idea why the system flash keeps failing.
Any thoughts as to why this is happening? Alternatively, is there a way to restore my recovery so I can try adb sideloading the OTA?
Click to expand...
Click to collapse
update ADB and Fastboot to latest version 1.0.3.6 release
Try the steps in my restore-to-stock thread?
I've used these steps twice for "L" and once for "V" builds.
No issues yet.
http://forum.xda-developers.com/pix...stock-soft-t3494478/post69476498#post69476498
---------- Post added at 03:09 PM ---------- Previous post was at 03:07 PM ----------
Oh, I remember getting that "boota does not exist".
I think I edited the script file somehow to fix that.
Can't remember what it was just now.
---------- Post added at 03:10 PM ---------- Previous post was at 03:09 PM ----------
Yours says "sending 'bootloadera'"
But mine that work says "sending 'bootloader_a'".
That may be the edit I did at one point.
But I have not had to edit anything while using the steps listed in my thread I linked to.
Taebom said:
update ADB and Fastboot to latest version 1.0.3.6 release
Click to expand...
Click to collapse
That seems to have done the trick, thank you so much!

Nexus 7 2013 LTE bootloop, can't enter Recovery mode; flash write failure

My Nexus 7 2013 LTE 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.
Bad motherboard, just had to replace mine with exact issue.

Can't flash DP4 (Another bootloader required)

Hey there,
I'm trying to install DP4 on my rooted P2XL but I'm stuck because I don't have the required Bootloader Version installed:
Code:
Sending 'bootloader_a' (36364 KB) OKAY [ 0.096s]
Writing 'bootloader_a' FAILED (remote: Flashing is not allowed for Critical Partitions
)
Finished. Total time: 0.103s
rebooting into bootloader OKAY [ 0.001s]
Finished. Total time: 0.002s
Sending 'radio_a' (60388 KB) OKAY [ 0.158s]
Writing 'radio_a' OKAY [ 0.575s]
Finished. Total time: 0.737s
rebooting into bootloader OKAY [ 0.002s]
Finished. Total time: 0.003s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: TMZ12bb
Baseband Version.....: g8998-00253-1805232234
Serial Number........: 712KPSL1232430
--------------------------------------------
Checking product OKAY [ 0.003s]
Checking version-bootloader FAILED
Device version-bootloader is 'TMZ12bb'.
Update requires 'TMZ20j'.
fastboot: error: requirements not met!
Press any key to exit...
I thought it flashes the Bootloader anyways tbh? Is there maybe a flashable .zip of DP4 that I just can't seem to find?
If not what can I do to fix this problem? If I google "TMZ20j bootloader" or whatever I can't find anything.
Thanks in advance!
Greetings
rest0ck said:
Hey there,
I'm trying to install DP4 on my rooted P2XL but I'm stuck because I don't have the required Bootloader Version installed:
I thought it flashes the Bootloader anyways tbh? Is there maybe a flashable .zip of DP4 that I just can't seem to find?
If not what can I do to fix this problem? If I google "TMZ20j bootloader" or whatever I can't find anything.
Thanks in advance!
Greetings
Click to expand...
Click to collapse
Did you unlock your critical partition when you unlocked your bootloader?
Run....fastboot oem device-info...
That'll tell you if your fully unlocked.
Darn, oh. My bad. Thanks!
I guess that will wipe user data right?
/e Working now, thanks a lot!

Categories

Resources