Database Users

[Q] Bricked? No Bootloader and no Sytem

Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
- Wiped everything
- Forgot to copy the .zip files - so thats the point where everything went wrong
- Tried to upload it via adb push - failed when I wanted to install the zip
- Startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!

hd21337 said:
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
Wiped everything
forgot to copy the .zip files - so thats the point where everything went wrong
tried to upload it via adb push - failed when I wanted to install the zip
startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
Click to expand...
Click to collapse
Hi, hd21337...
What happens when you (from a fully shut down state) press VOL-DOWN, hold.. whilst holding, press POWER-ON?
What do you see when you plug the Nexus 7 into the wall charger? Do you see the WHITE-ON-BLACK battery charging animation?
Have you tried pressing, and holding for 30 seconds, the POWER ON button? (Your tablet could just be stuck in APX mode).
Rgrds,
Ged.

hd21337 said:
Hi,
I just wanted to install a new ROM but I ended without any Bootloader and System.
What I did:
Wiped everything
forgot to copy the .zip files - so thats the point where everything went wrong
tried to upload it via adb push - failed when I wanted to install the zip
startet the flash-all.sh to install the factory image - went wrong -> no system.ing etc found
So what can I do now?
Its a Nexus Wifi (2012).
Thanks!
Click to expand...
Click to collapse
Blessed are the backup makers, for they hath made Nandroids.
Exasperations, 3:16
I didn't know you could wipe out the bootloader. You should still be able to push recovery from PC via adb - fastboot. Then if pc recognizes the device transfer the zips from the pc.
Other than that, just don't know atp.
Someone more knowledgeable than I will need to chime in.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4

GedBlake said:
Hi, hd21337...
What happens when you (from a fully shut down state) press VOL-DOWN, hold.. whilst holding, press POWER-ON?
What do you see when you plug the Nexus 7 into the wall charger? Do you see the WHITE-ON-BLACK battery charging animation?
Have you tried pressing, and holding for 30 seconds, the POWER ON button? (Your tablet could just be stuck in APX mode).
Rgrds,
Ged.
Click to expand...
Click to collapse
VOL-DOWN + Power On = Bootload appears but when I click on "Recovery mode" I see the Google logo with a notification in the top (Booting failed) in red. The same notification appears when I click on "Start".
I see the charging animation and holding the power button for 30 second didnt help.

wtherrell said:
Blessed are the backup makers, for they hath made Nandroids.
Exasperations, 3:16
I didn't know you could wipe out the bootloader. You should still be able to push recovery from PC via adb - fastboot. Then if pc recognizes the device transfer the zips from the pc.
Other than that, just don't know atp.
Someone more knowledgeable than I will need to chime in.
Sent from my Hyperdriven Dev Edition Vzw SCH-I545 with KT kernel using Tapatalk 4
Click to expand...
Click to collapse
Nah I think that i corrupted/deleted it with the factory image script from google!
And when I enter the bootloader, I dont see my device via "adb devices" :>
Downloads/nakasi-jwr66y » sudo ./flash-all.sh
Password:
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.577s]
finished. total time: 0.577s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 1.026s]
finished. total time: 1.026s
erasing 'recovery'...
OKAY [ 0.852s]
finished. total time: 0.852s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.488s]
finished. total time: 0.488s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.493s]
finished. total time: 6.493s
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
OKAY [ 0.019s]
finished. total time: 0.020s
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........: XXXXXXXXXXXXXXXX
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
FAILED
Device version-bootloader is '4.18'.
Update requires '4.23'.
finished. total time: 0.139s
Click to expand...
Click to collapse

hd21337 said:
Nah I think that i corrupted/deleted it with the factory image script from google!
And when I enter the bootloader, I dont see my device via "adb devices" :>
Click to expand...
Click to collapse
Maybe not... the v4.23 bootloader from Jellybean 4.3 build JWR66Y is known to cause issues when fastboot flashing back to factory stock. For this reason, it is recommended you replace that version of the bootloader with the one from build JWR66V. It's still, ostensibly, the same bootloader, but seems to fastboot flash OK.
As build JWR66V is now no longer available on the Google Developers website, somebody has extracted and uploaded the old bootloader from build JWR66V here. (You might have to scroll down a little for the link).
Oh.... and ADB devices doesn't work when you're in the bootloader... it requires a fully booted Android OS to work.
The command I think you're looking for is fastboot devices
Rgrds,
Ged.

hd21337 said:
VOL-DOWN + Power On = Bootload appears but when I click on "Recovery mode" I see the Google logo with a notification in the top (Booting failed) in red. The same notification appears when I click on "Start".
Click to expand...
Click to collapse
You are in bootloader (fastboot ) mode so when you wiped everything except bootloader it is normal state. Now check if computer know your nexus (if not install driver ) and run from factory image flash-all.bat and wait for restart. That's all. Adb and fastboot are two different things...

jkkk88 said:
You are in bootloader (fastboot ) mode so when you wiped everything except bootloader it is normal state. Now check if computer know your nexus (if not install driver ) and run from factory image flash-all.bat and wait for restart. That's all. Adb and fastboot are two different things...
Click to expand...
Click to collapse
Erm... yeah... I think the OP has probably done this already.
It was his fastboot output...
writing bootloader...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
...that suggested to me, the known issue with the bootloader from build JWR66Y as detailed here (in red letters, at the very top of the first post in the thread), and discussed here... as being the likely cause of the problem.
So, to reiterate @hd21337... fastboot flash the bootloader from build JWR66V, instead of the one from build JWR66Y... and it just might get your Nexus 7 back up and running again.
Good luck.
Rgrds,
Ged.

GedBlake said:
Erm... yeah... I think the OP has probably done this already.
It was his fastboot output...
writing bootloader...
FAILED (remote: (InvalidState))
finished. total time: 0.412s
rebooting into bootloader...
...
So, to reiterate @hd21337... fastboot flash the bootloader from build JWR66V, instead of the one from build JWR66Y... and it just might get your Nexus 7 back up and running again.
Click to expand...
Click to collapse
My concern was that OP could not start (deleted ) recovery from bootloader menu. He should look into stickies. Nexus is still alive and should get new bootloader as you recommended from another build.

Hi guys (@GedBlake and @jkkk88),
sorry for the late answer.
I just tried to run the flash-all.sh with the other bootloader image... but its worse than before.
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.580s]
finished. total time: 0.580s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.769s]
finished. total time: 0.769s
erasing 'recovery'...
OKAY [ 0.854s]
finished. total time: 0.854s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.489s]
finished. total time: 0.489s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 6.494s]
finished. total time: 6.495s
sending 'bootloader' (2100 KB)...
OKAY [ 0.267s]
writing 'bootloader'...
OKAY [ 9.376s]
finished. total time: 9.643s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for device >
Click to expand...
Click to collapse
So and at this point, he stuck for about 20 minutes - I aborted it because he didnt move on. And now the N7 is dead. No power charging icon and animation and I cant turn it on (30 seconds holding power button etc.).
So I think I just killed it
Any ideas if there is an another reset trick etc.?
Thanks!

Nexus 7 boot.img flash fails with FileWriteFailed

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.

[Q] Failed KitKat 4.4 Fastboot

Hi All,
I'm using Mac Terminal, have latest SDK, adb and fastboot installed. I have Nexus 7 (2012) Wifi - Nakasi
I followed the pinned post to upgrade my 4.3 (JWR66Y) to KitKat 4.4. I rebooted into fastboot and started ./flash-all.sh
Mid way through the process had stalled so I 'control C' out of the process.
$ ./flash-all.sh
...
(bootloader) Bootloader is already unlocked
OKAY [ 0.020s]
finished. total time: 0.020s
erasing 'boot'...
OKAY [ 0.993s]
finished. total time: 0.994s
erasing 'cache'...
OKAY [ 1.059s]
finished. total time: 1.059s
erasing 'recovery'...
OKAY [ 0.854s]
finished. total time: 0.855s
erasing 'system'...
OKAY [ 0.490s]
finished. total time: 0.490s
erasing 'userdata'...
OKAY [ 6.154s]
finished. total time: 6.154s
sending 'bootloader' (2100 KB)...
OKAY [ 0.302s]
writing 'bootloader'...
OKAY [ 9.666s]
finished. total time: 9.969s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
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........: 015d2d4226501005
--------------------------------------------
checking product...
OKAY [ 0.030s]
checking version-bootloader...
OKAY [ 0.024s]
sending 'boot' (4990 KB)...
OKAY [ 1.045s]
writing 'boot'...
OKAY [ 1.047s]
sending 'recovery' (5530 KB)...
OKAY [ 3.340s]
writing 'recovery'...
OKAY [ 1.381s]
sending 'system' (611878 KB)...
^C
Click to expand...
Click to collapse
I ran same process and it was hanging again at the same spot. I exited the same way. Now terminal cannot find device in adb devices. I can still boot into recovery mode.
$ ./adb devices
List of devices attached
Click to expand...
Click to collapse
$ ./flash-all.sh
< waiting for device >
Click to expand...
Click to collapse
I'm not sure what to do now!!! any help would be...helpful. Please.

You need to wait a but, because the system image us about 630MB, which may take round about two minutes to get transferred and flashed.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
You need to wait a but, because the system image us about 630MB, which may take round about two minutes to get transferred and flashed.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I waited 20 minutes the first time and 15 minutes the second time.
I tried flashing using different method from fastboot (http://forum.xda-developers.com/showthread.php?t=2010312). Problems happen when flashing system.img (~600MB).
Has anyone else found out the checksums aren't working? I get an error "E:signature verification failed" when using "flash-all.sh" from recovery mode (different method i've tried)
Note: no problems updating my nexus 4

Just wanted to update you on a solution if anyone has a similar problem.
I erased the system image through fastboot.
./fastboot erase system
Click to expand...
Click to collapse
Flashed the system image for old stock 4.3
./fastboot flash system system.img
Click to expand...
Click to collapse
Ran the flash-all script
./flash-all.sh
Click to expand...
Click to collapse
System was updated and worked! I back-dated to android 4.3, then did a second flash-all script to update to the current version of android 4.4. I believe that the original factory image for 4.4 was not working. The factory image was updated a day later - this is the file i used.
Thanks to everyone in xda. The many posts I read - even not directly related to my problem - provided a solution.
I hope my next post isn't so noob

whitext said:
I waited 20 minutes the first time and 15 minutes the second time.
I tried flashing using different method from fastboot (http://forum.xda-developers.com/showthread.php?t=2010312). Problems happen when flashing system.img (~600MB).
Has anyone else found out the checksums aren't working? I get an error "E:signature verification failed" when using "flash-all.sh" from recovery mode (different method i've tried)
Note: no problems updating my nexus 4
Click to expand...
Click to collapse
Well,I got the similar problem the other day on my Nakasig when I was flashing factory images through Fastboot.
Not only did I try the "flash-all.bat" command, but I also manually inputted each command line one after another.
However, I still encountered the same issue and waited for more 30 minutes during the "sending system" process.
Even worse was that I unplugged my N7 and tried to boot it,which led me to be stuck with the Google logo.:crying:
After removing the battery and booting it into Fastboot again,this time I decided to use Wug's toolkit to flash it.:good:
And thankfully,it worked and I can grab the delicious Kitkat now.
BTW, my N7 still failed to pass Hashcheck while using Wug's automatic method, therefore I just downloaded the Factory images and used Wug's tool to navigate to the .tgz file and then flash it.It spent me around 2 minutes to complete the "sending system" process this time.

[Q] writing 'bootloader'... FAILED (remote: (Unknown error code))

My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
Flash Stock + Unroot...
------------------------------------------------------------------
erasing 'boot'...
OKAY [ 2.526s]
finished. total time: 2.526s
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.200s]
finished. total time: 0.200s
erasing 'recovery'...
OKAY [ 0.016s]
finished. total time: 0.016s
******** 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.015s]
finished. total time: 0.015s
sending 'bootloader' (2100 KB)...
OKAY [ 0.264s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 0.402s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.021s
< waiting for device >​
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.

Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?

brad3626 said:
My N7 "2012" kept freezing, so I put it in bootloader and tried to do a recovery mode reset to stock. It froze during the process.
Now, the only thing I can do is get it into bootloader mode manually by holding the buttons. It frezes if I choose any of the options from the bootloader screen including restarting the bootloader from the bootloader screen without holding power and volume.
I have tried the Nexus Root Toolkit a bunch of times with the "flash stock + unroot (soft bricked)" feature, testing different factory builds and the best results are below:
PLEASE HELP! Keep in mind that I am a newb to messing with this stuff.
I have read forums and tried things that people suggested to others in similar situations, but I am pretty lost at this point. Keep in mind that my device is almost certainly wiped and definitely will not boot the OS.
Click to expand...
Click to collapse
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.

adomol said:
After doing a bit of research, I've found out that there is a BAD version of the N7 2012 bootloader 4.23 floating around. The unsettling thing is that it's being supplied with a couple of the factory images that come straight from from the Google android devolpers page online. Anyway to make a long story short, I would try flashing the working version of the bootloader first off, then go from there with a factory reset. You can download the the working bootloader (bootloader-grouper-4.23.img) HERE --> h t t p : / / g o o . g l / q A D S A z (sorry about the spaces in the url, I'm new to the forum and can't post links yet, just delete the spaces)
BTW, its the same bootloader for N7 wifi OR 3G. md5 = df53028033c9eccf4fe5ba7bc198ce24
Here's how to install using fastboot:
1. Reboot To Your Bootloader On You Nexus 7 (Power off power button and volume down until you see bootloader screen)
2. Connect Your Nexus 7 To Your Computer
3. Open Up Command Prompt or terminal window (not sure if you are using windows/mac/linux)
4. CD to where you downloaded bootloader-grouper-4.23.img
5. Then type:
fastboot devices (to see if your N7 is connected correctly)
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
Then try the factory reset again.
If you don't have fastboot installed your computer you need it. Makes flashing your N7 a breeze... lock/unlock, custom recovery installs, going back to factory stock, all much more easy with fastboot.
You can get it from the android devolper site, h t t p : / / g o o . g l / 2 q p r for windows/mac/linux. All you need is the SDK tools, not the ADT bundle.
Click to expand...
Click to collapse
Thank you for the help, unfortunately, it did not work.
I followed the instructions above, but the Nexus displayed "neither up nor cac partitions found" over and over
While cmd displayed:
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.213s
C:\Users\Brad>fastboot devices
XXX fastboot
C:\Users\Brad>fastboot flash bootloader bootloader-grouper-4.23.img
sending 'bootloader' (2100 KB)...
OKAY [ 0.271s]
writing 'bootloader'...
FAILED (remote: (Unknown error code))
finished. total time: 3.205s​

Erovia said:
Is your N7 the Wi-Fi or the 3G variant?
What was the name of the factory image you were trying to flash?
Click to expand...
Click to collapse
Wi-Fi
I have tried every one that the NRT offered.

Just read this guide and download the latest factory image from here.
Good luck.

Erovia said:
Just read this guide and download the latest factory image from here.
Good luck.
Click to expand...
Click to collapse
I read that guide.
But that guide seems to be written with the assumption that the device can boot into the OS
No ADB device is found because I can only boot into bootloader.

That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.

Erovia said:
That part is only for the driver installation. You can skip to the "Extract the Factory Image" part and follow it from there.
Click to expand...
Click to collapse
Following from "Extract the Factory Image" part, this is what I am getting:
C:\Users\Brad>cd \Users\brad\AppData\Local\Android\android-sdk\platform-tools
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot devices
XXX fastboot
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>adb reboot-bootlo
ader
error: device not found
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot oem unlo
ck
...
FAILED (command write failed (Unknown error))
finished. total time: 0.590s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase bo
ot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase ca
che
erasing 'cache'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase re
covery
erasing 'recovery'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.022s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase sy
stem
erasing 'system'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot erase us
erdata
erasing 'userdata'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.018s
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot flash bo
otloader bootloader-grouper-4.23.img
error: cannot load 'bootloader-grouper-4.23.img': Invalid argument​

On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?

Erovia said:
On the bootloader screen is your bootloader shown as "locked" or "unlocked" ?
Click to expand...
Click to collapse
lock state - unlocked

What's the output of fastboot -w update image-nakasi-kot49h.zip ?

Erovia said:
What's the output of fastboot -w update image-nakasi-kot49h.zip ?
Click to expand...
Click to collapse
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
error: out of memory​

I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.

Erovia said:
I have no idea what this "out of memory" error is. If I were you I would restart my computer, run fastboot from a cmd opened as Admin and try out different usb ports.
Click to expand...
Click to collapse
I restarted, ran cmd as admin and tried every USB port and got this as the result each time:
C:\Users\Brad\AppData\Local\Android\android-sdk\platform-tools>fastboot -w updat
e image-nakasi-kot49h.zip
< waiting for device >
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........: XXX
--------------------------------------------
checking product...
OKAY [ 0.031s]
checking version-bootloader...
OKAY [ 0.016s]
sending 'boot' (4992 KB)...
OKAY [ 5.460s]
writing 'boot'...
FAILED (remote: (FileWriteFailed))
finished. total time: 8.518s​
The Nexus was frozen at this point and had to be manually forced to restart bootloader.

Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.

Erovia said:
Do you have a valid warranty for the N7? I'm asking because it seems that your N7's internal memory got corrupted. I might not be right, but that's my best guess.
Click to expand...
Click to collapse
Thanks for your help
I bought it 13 months ago (perfect timing, coincidentally, right?), so if I could find the receipt I would still be screwed.

I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)

Erovia said:
I would still try to send it to Asus or Google. Maybe they repair it for a reasonable price.
(But if you plan to do that try to relock you bootloader with fastboot oem lock)
Click to expand...
Click to collapse
fastboot oem lock
...
(bootloader) Bootloader is locked now.
OKAY [ 36.032s]
finished. total time: 36.032s​
But then the N7 freezes and after manually restarting in bootloader it is still unlocked.

Then send is as it is. You can't do any more about it.
Good luck.

[Q] Stuck on boot animation stock and custom roms

Hi all, first off, yes I have read quite a bit and I am completely stumped on this one.
A buddy from work dropped off his Nexus 4 and asked about the "bootloop" it is stuck in. Looking at it, this is not a boot loop as far as I can tell. He said he used the http://www.wugfresh.com/nrt/ to do a root, but it apparently went wrong (he said it reported successful completion).
What I have done thus far:
Download Google stock rom and flashed that following their instructions in the "flash-all.sh" file for Kit-Kat. Tried to go into recovery, but the recovery just gives the android with the red triangle above it and hangs. On boot the screen shows the "Google" logo with the unlocked symbol and then shows the kit-kat boot animation but just sits there and never finishes. I gave it about 30 minutes but no luck.
I can get into bootloader and then flash a recovery (CWM for Mako), which then allows me to get into CWM and either flash a custom ROM (tried latest PA beta) with the same hang on boot.
Tried to custom erase system, boot, recovery with the instructions below:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-clockwork-6.0.4.7-mako.img
boot to recovery
set up for sideload in CWM
adb sideload pa_mako-4.1-BETA2-20140310.zip
reboot
Same result, just hangs on reboot with animation for boot.
I tried flashing the radio and bootloader back to 4.3 and then flashing the stock rom for the Google ROM occam-jwr66y-factory-74b1deab.tgz which is where I am at now with it just sitting at animation if the X lighting up.
I just noticed that when I plug it in to my workstation it recognizes the device sort of and shows that it is mountable, but then just hangs and never loads the directory structure like normal.
Another thing to note, when I mount /system and /data in CWM and "adb shell" into the phone, the /sdcard/0 location shows empty, which as far as I know this should be populated with the usual sdcard user directories, maybe??
Any help would be appreciated. I noticed that if I hold both the volume up and volume down buttons it says it is in "Download" mode, didn't know that was a thing outside of Samsung devices.
Ouput from flashing with Google stock 4.4.2 ROM:
sudo ./flash-all.sh
[sudo] password for jscott:
sending 'bootloader' (2203 KB)...
OKAY [ 0.089s]
writing 'bootloader'...
OKAY [ 0.311s]
finished. total time: 0.401s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.790s]
writing 'radio'...
OKAY [ 2.541s]
finished. total time: 4.332s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
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.98
Serial Number........: 0221a297d9d67206
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.253s]
writing 'boot'...
OKAY [ 0.356s]
sending 'recovery' (6888 KB)...
OKAY [ 0.287s]
writing 'recovery'...
OKAY [ 0.398s]
erasing 'system'...
OKAY [ 0.579s]
sending 'system' (713960 KB)...
OKAY [ 26.844s]
writing 'system'...
OKAY [ 40.883s]
rebooting...
finished. total time: 69.615s
Recovery was broken again.
Had to flash recovery again to get in but I can "adb shell" the phone no problems.
If more information is needed or someone has a sure fire way to fix this same problem please hit me up, but at this point I am at a loss.
Just found out that the phone may have died when the "wugfresh" script was running, but he said that it died afterwards, since I wasn't there I don't know for sure how this all played out.

Oops, I just posted the same problem a few minutes ago. In my defense to the moderators, your thread wasn't posted when I started writing mine.
Anyhow, have you tried flashing the 4.2.2 factory image? That is the only one I manage to boot, but my IMEI and network are gone...

MtG92 said:
Oops, I just posted the same problem a few minutes ago. In my defense to the moderators, your thread wasn't posted when I started writing mine.
Anyhow, have you tried flashing the 4.2.2 factory image? That is the only one I manage to boot, but my IMEI and network are gone...
Click to expand...
Click to collapse
Same thing on my side with the 4.2.2 ROM. Loads fine, but no IMEI or anything like that. Not sure what the deal is with it.
Allowed OTA update and now I get the android bot with the red triangle when trying to go into recovery, but it says "no command" under it. On boot the device just hangs at "starting apps." and doesn't move past that.
Sideloaded PA 3.99 mako for the phone and it just hangs on boot animation as it has done previously before successfully flashing the 4.2 factory image. Not sure what the deal is but a solution for this would be awesome as I am totally stumped.

I have been dealing with this for a few months, and what I have done to get it to work is let it sit for a few hours. Then give it a shot. About half the time my phone boots up. Once it's booted up everything works, but if I need to reboot for any reason your screwed for a few hours.
It started happening for me once the 4.4 update rolled out, and ever since it has been doing this. I asked on here a few time and got no responses.
Sent from my Nexus 4 using Tapatalk

NeCr0mStR said:
Same thing on my side with the 4.2.2 ROM. Loads fine, but no IMEI or anything like that. Not sure what the deal is with it.
Allowed OTA update and now I get the android bot with the red triangle when trying to go into recovery, but it says "no command" under it. On boot the device just hangs at "starting apps." and doesn't move past that.
Sideloaded PA 3.99 mako for the phone and it just hangs on boot animation as it has done previously before successfully flashing the 4.2 factory image. Not sure what the deal is but a solution for this would be awesome as I am totally stumped.
Click to expand...
Click to collapse
I met the same problem. My nexus 4 met this problem about 4 or 5 times. at first time, I tried restarting the phone and sometimes it might boot successfully, then everything works fine. Second time the reboot doesn't work any more, but flash stock with the newest factory ROM works fine(4.3 at that time), at this time I backup all my data. After I met this more, I found this problem arose only when the phone automatically shutting down because of the dead battery. Yesterday I met this problem again because of the dead battery, and at this time only reboot the phone with 4.2.0. I tried all other factory stocks from 4.2.0 to 4.4.2. Hope you can solve this early. And ask me any information you need.

NeCr0mStR said:
Hi all, first off, yes I have read quite a bit and I am completely stumped on this one.
A buddy from work dropped off his Nexus 4 and asked about the "bootloop" it is stuck in. Looking at it, this is not a boot loop as far as I can tell. He said he used the http://www.wugfresh.com/nrt/ to do a root, but it apparently went wrong (he said it reported successful completion).
What I have done thus far:
Download Google stock rom and flashed that following their instructions in the "flash-all.sh" file for Kit-Kat. Tried to go into recovery, but the recovery just gives the android with the red triangle above it and hangs. On boot the screen shows the "Google" logo with the unlocked symbol and then shows the kit-kat boot animation but just sits there and never finishes. I gave it about 30 minutes but no luck.
I can get into bootloader and then flash a recovery (CWM for Mako), which then allows me to get into CWM and either flash a custom ROM (tried latest PA beta) with the same hang on boot.
Tried to custom erase system, boot, recovery with the instructions below:
fastboot erase system -w
fastboot erase boot
fastboot erase recovery
fastboot flash recovery recovery-clockwork-6.0.4.7-mako.img
boot to recovery
set up for sideload in CWM
adb sideload pa_mako-4.1-BETA2-20140310.zip
reboot
Same result, just hangs on reboot with animation for boot.
I tried flashing the radio and bootloader back to 4.3 and then flashing the stock rom for the Google ROM occam-jwr66y-factory-74b1deab.tgz which is where I am at now with it just sitting at animation if the X lighting up.
I just noticed that when I plug it in to my workstation it recognizes the device sort of and shows that it is mountable, but then just hangs and never loads the directory structure like normal.
Another thing to note, when I mount /system and /data in CWM and "adb shell" into the phone, the /sdcard/0 location shows empty, which as far as I know this should be populated with the usual sdcard user directories, maybe??
Any help would be appreciated. I noticed that if I hold both the volume up and volume down buttons it says it is in "Download" mode, didn't know that was a thing outside of Samsung devices.
Ouput from flashing with Google stock 4.4.2 ROM:
sudo ./flash-all.sh
[sudo] password for jscott:
sending 'bootloader' (2203 KB)...
OKAY [ 0.089s]
writing 'bootloader'...
OKAY [ 0.311s]
finished. total time: 0.401s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.790s]
writing 'radio'...
OKAY [ 2.541s]
finished. total time: 4.332s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
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.98
Serial Number........: 0221a297d9d67206
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
OKAY [ 0.002s]
sending 'boot' (6340 KB)...
OKAY [ 0.253s]
writing 'boot'...
OKAY [ 0.356s]
sending 'recovery' (6888 KB)...
OKAY [ 0.287s]
writing 'recovery'...
OKAY [ 0.398s]
erasing 'system'...
OKAY [ 0.579s]
sending 'system' (713960 KB)...
OKAY [ 26.844s]
writing 'system'...
OKAY [ 40.883s]
rebooting...
finished. total time: 69.615s
Recovery was broken again.
Had to flash recovery again to get in but I can "adb shell" the phone no problems.
If more information is needed or someone has a sure fire way to fix this same problem please hit me up, but at this point I am at a loss.
Just found out that the phone may have died when the "wugfresh" script was running, but he said that it died afterwards, since I wasn't there I don't know for sure how this all played out.
Click to expand...
Click to collapse
You have to keep flashing the Stock ROM...that's what saved me
Sent from my Moto G

GameAware said:
You have to keep flashing the Stock ROM...that's what saved me
Sent from my Moto G
Click to expand...
Click to collapse
So you had the same problem and managed to solve it by flashing the stock rom multiple times? How many times did you have to do it, and have you had that problem since?

MtG92 said:
So you had the same problem and managed to solve it by flashing the stock rom multiple times? How many times did you have to do it, and have you had that problem since?
Click to expand...
Click to collapse
Yes I had the same problem and flashed the ROM the first time, but still nothing. I then flashed it again and it booted up as normal. No problems since.
Sent from my Moto G