Unable to flash to restock - Nexus 7 (2013) Q&A

I softbricked my N7. Can still get to flashboot. However, I have tried following so many guides to flash back to stock to recover from this that I'm going a little manic about it. I just recently tried the Nexus Root Toolkit and it's method. But I get this:
*******Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [6.617s]
finished. total time: 6.617s
sending 'bootloader' <2100 KB>...
OKAY [0.070s]
writing 'bootloader'...
FAILED <remote: SIgnature mismatched!!!>
finished. total time: 0.090s
rebooting into bootloader...
OKAY [0.010s]
finished. total time: 0.010s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
______________________________
Bootloader version...: FLO-03.14
Baseband Version...: none
Serial Number...: 0584c016
______________________________
checking product...
FAILED
Device product is 'flo'/
Update requires 'grouper'.
finished. total time: 0.020s
Booting up your freshly flashed stock device...
_______________________________
and a paragraph about what to do if it doesnt work. i did what it requested and the same thing. Please help me.

usefuladjective said:
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
______________________________
Bootloader version...: FLO-03.14
Baseband Version...: none
Serial Number...: 0584c016
______________________________
checking product...
FAILED
Device product is 'flo'/
Update requires 'grouper'..
Click to expand...
Click to collapse
You are trying to flash grouper files on a flo. Get the flo files.

meekrawb said:
You are trying to flash grouper files on a flo. Get the flo files.
Click to expand...
Click to collapse
I've tried flashing just about every image that is available. Each attempt says the same thing.

I'm still having issues.
I've flashed every image that the toolkit gives me a prompt for and it still won't do anything.
Please help me. I'm desperate.

Download the 4.4.2 image from Google site for flo, boot into recovery mode and side load the image.
Sent from my Nexus 7 using XDA Premium 4 mobile app

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] Any way around "FAILED (remote: flash write failure)" ??

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

(Q) Think I got a damaged Internal SD Card; how to replace it?

My device is soft bricked I think (SD Card damaged, bootloader is fine; can't write anything on it; bootloader, etc etc); so anyone knows of a guide on how to replace your internal SD Card? If there's any help about it I would appreciate it. Thanks.
ReDXfiRe said:
My device is soft bricked I think (SD Card damaged, bootloader is fine; can't write anything on it; bootloader, etc etc); so anyone knows of a guide on how to replace your internal SD Card? If there's any help about it I would appreciate it. Thanks.
Click to expand...
Click to collapse
I'll try to sort this out. Soft bricked essentially means your device won't boot. At that point you should revert to a current backup. I wouldn't go so far as replacing your internal memory as i would adb'ing the factory images. Do some more reading the answers are there!
Beezer80 said:
I'll try to sort this out. Soft bricked essentially means your device won't boot. At that point you should revert to a current backup. I wouldn't go so far as replacing your internal memory as i would adb'ing the factory images. Do some more reading the answers are there!
Click to expand...
Click to collapse
Already did try factory image won't let it write; seems something wrong with hardware already big contributors have told me its hardware.
Can you unlock the bootloader, or is it unlocked already?
ReDXfiRe said:
Already did try factory image won't let it write; seems something wrong with hardware already big contributors have told me its hardware.
Click to expand...
Click to collapse
Replace the motherboard or warranty.
ReDXfiRe said:
Already did try factory image won't let it write; seems something wrong with hardware already big contributors have told me its hardware.
Click to expand...
Click to collapse
What are you using to try to flash it, Wug's?
Pandae said:
Can you unlock the bootloader, or is it unlocked already?
Click to expand...
Click to collapse
It's unlocked already. Been in many forums they say its hardware :\
skrypj said:
What are you using to try to flash it, Wug's?
Click to expand...
Click to collapse
C:\ADB>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.912s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.15
Baseband Version.....: none
Serial Number........: 05fa05a1
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-03.15'.
Update requires 'FLO-04.02'.
finished. total time: 0.046s
Press any key to exit...
No just regular fastboot flash bootloader method; done with .bat and manually and nothing
ReDXfiRe said:
C:\ADB>flash-all.bat
sending 'bootloader' (3911 KB)...
OKAY [ 0.130s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 90.912s
rebooting into bootloader...
OKAY [ 0.009s]
finished. total time: 0.010s
< waiting for device >
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: FLO-03.15
Baseband Version.....: none
Serial Number........: 05fa05a1
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-03.15'.
Update requires 'FLO-04.02'.
finished. total time: 0.046s
Press any key to exit...
No just regular fastboot flash bootloader method; done with .bat and manually and nothing
Click to expand...
Click to collapse
Try wugs program, but go to Options Menu>Flash Stock Tab>Check "Enable 'Force Flash Mode' . . . " Then try to flash stock + unroot again with the soft-bricked option selected. This basically makes Wug's ignore the check process at the beginning of the flash. It almost sounds like it was not passing the check. This will erase your entire tablet though.
I also had an issue with my fastboot drivers where it wouldn't work properly with my n7 but were fine with my nexus 5. I had a bunch of failures similar to yours. I full uninstalled all android associated drivers, whether they were Samsung, lg, asus , whatever and reinstalled. This worked.
ReDXfiRe said:
My device is soft bricked I think (SD Card damaged, bootloader is fine; can't write anything on it; bootloader, etc etc); so anyone knows of a guide on how to replace your internal SD Card? If there's any help about it I would appreciate it. Thanks.
Click to expand...
Click to collapse
Better hope that one of those suggestions would work for you, 'cause the internal nand is not replaceable, unless you have some quite hi-tech equipment. If need be, you have to replace the whole motherboard. True, when the nand cannot be physically written on anymore, it would show those symptoms. Yet imputing fault to hardware is a guess in most cases. Because I don't hear people complaining about the Nexus 7's NAND being a dud much(compared to the Acer A500, for instance). You should try every solution you can dig up from forums first.

cannot unlock bootloader, cache partition probably corrupted

Hello all,
My Nexus 7 (2013) was bricked about a year ago by a google update, like many other. I just got around looking into it now. I'm having some trouble as you may have guessed.
Here's the current state of affairs :
Cannot get past the white Google logo
Can boot into fastboot
fastboot is locked
bootloader version is FLO-04.02
Can boot into recovery mode
factory reset fails on mounting /cache
Here's what I've tried so far, from several sources here and there
Download Official Android image and run a flash-all.sh
unlock the bootloader with `fastboot oem unlock`
factory reset from recovery mode
All of these end up failing because bootloader is locked or because it freezes (most often at some kind of wiping data step).
This is the output of the `.flash-all.sh` command.
Code:
floby $ ./flash-all.sh
sending 'bootloader' (3911 KB)...
FAILED (remote: Bootloader is locked.)
finished. total time: 0.005s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
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........: 07cd6455
--------------------------------------------
checking product...
OKAY [ 0.003s]
checking version-bootloader...
FAILED
Device version-bootloader is 'FLO-04.02'.
Update requires 'FLO-04.05'.
finished. total time: 0.019s
I cannot post links but here is what it looks like:
image svRKQ5g on imgur
image y5Pa3br on imgur
Do you have any idea how I can unbrick this ?
Thank you all in advance.
Hello,
does anyone have any idea to help me ?
Floby said:
Hello,
does anyone have any idea to help me ?
Click to expand...
Click to collapse
It looks like bootloader 4.02 wasn't written correctly. Get bootloader 4.05 and push it to see if that fixes the issue. IIRC, bootloader 4.05 is part of android 5.1.1. I'm not sure which factory image you're trying to install, but start by addressing the error and push bootloader 4.05 before anything else.
quickdraw86 said:
It looks like bootloader 4.02 wasn't written correctly. Get bootloader 4.05 and push it to see if that fixes the issue. IIRC, bootloader 4.05 is part of android 5.1.1. I'm not sure which factory image you're trying to install, but start by addressing the error and push bootloader 4.05 before anything else.
Click to expand...
Click to collapse
Thanks for your reply, I was indeed getting new binaries from the latest 5.x release. I'll try and push the new bootloader and post updates.

BRICKED?. Can't figure out how to update bootloader. Can't flash flash-all.bat

I have a google Pixel Xl running android Pie. I am trying to flash it back to stock. I am getting this error after flashing flash-all.bat.
This what I get after running the batch file:
fastboot: error: cannot load 'bootloader-marlin-8996-012001-1811131534.img': No such file or directory
rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.000s
Sending 'radio_a' (57140 KB) OKAY [ 1.698s]
Writing 'radio_a' OKAY [ 0.500s]
Finished. Total time: 2.338s
rebooting into bootloader OKAY [ 0.016s]
Finished. Total time: 0.016s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: 8996-012001-1808030001
Baseband Version.....: 8996-130181-1808270817
Serial Number........: HT76L0200289
--------------------------------------------
Checking product OKAY [ 0.059s]
Checking version-bootloader FAILED
Device version-bootloader is '8996-012001-1808030001'.
Update requires '8996-012001-1811131534'.
fastboot: error: requirements not met!
Press any key to exit...
I am Unlocked and my bootloader version is 8996-012001-1808030001. How can I update the bootloader?I did the flash wipe (fastboot -w) and think I wiped the os and internal SD. . When I flash boot into twrp I cannot see any of my files. Nothing is on the SD card. Even after mounting system nothing shows up in twrp after clicking install.
tl ;dr
All zips and roms dissapeared off my SD card. Can't boot into OS or revert to stock.....Need to somehow update bootloader
Any suggestions?!
glachance0 said:
I have a google Pixel Xl running android Pie. I am trying to flash it back to stock. I am getting this error after flashing flash-all.bat...
Click to expand...
Click to collapse
Deleted
Figured it out.
glachance0 said:
Figured it out.
Click to expand...
Click to collapse
I have the same issue, less or more, my bootloader is locked. but how did you update your bootloader? Thanks.
glachance0 said:
Figured it out.
Click to expand...
Click to collapse
What did you do to fix it?

Categories

Resources