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!

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] 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

[Q] Help, Phone just bricked itself.

I was using phone normally, and installed an app from app store, and tried to run it, and force closed, and then google play force closed. So I decide to reboot phone, and it just gets stuck at boot screen. I let it wait for like 10mins then I turn off and boot into recovery, where I get errors that can't find /cache and /data. Anyway I can recover without losing my /data like rebuild partitions? Any idea what happened? I am using CM11 M7, and don't have it overclocked or anything.
Thanks,
CP

What app was it. Did you make a nandroid recently? Can you boot into recovery?
Sent from my Nexus 5 using XDA Free mobile app

Factory reset should fix it, as for recovering data it's gonna be difficult if the phone can't mount the partitions. If you have unlocked bootloader you could possibly use adb shell to dd the partition and then try to recover data from that, but without external memory I can't think how you'd do it.

jd1639 said:
What app was it. Did you make a nandroid recently? Can you boot into recovery?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
The app was just a clock app from store, nothing exciting. And no I hadn't run a nandroid recently, but woudn't have helped anyway, since /sdcard is missing also which is where CWM stores backups, though I can get into recovery.

I'm home now and got onto adb, and see these errors:
mmcblk0: timed out sending r/w cmd command, card status 0x400940
Click to expand...
Click to collapse
Anyway to rebuild phone?

CptanPanic said:
I'm home now and got onto adb, and see these errors:
Anyway to rebuild phone?
Click to expand...
Click to collapse
Sounds like you should flash the factory image in fastboot.
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Sounds like you should flash the factory image in fastboot.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So I tried that now, but I get
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.079s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.461s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.465s
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........: 0038cfc45846559d
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
FAILED

CptanPanic said:
So I tried that now, but I get
Code:
sending 'bootloader' (2203 KB)...
OKAY [ 0.077s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.079s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
sending 'radio' (45537 KB)...
OKAY [ 1.461s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 1.465s
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........: 0038cfc45846559d
--------------------------------------------
checking product...
OKAY [ 0.002s]
checking version-bootloader...
OKAY [ 0.002s]
checking version-baseband...
FAILED
Click to expand...
Click to collapse
Not good. I think you're emmc had failed. What happens if you try to lock the bootloader and then reboot. Is it still locked?
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app

jd1639 said:
Not good. I think you're emmc had failed. What happens if you try to lock the bootloader and then reboot. Is it still locked?
fastboot oem lock
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
So I lock bootloader, and reboot and it is unlocked again.

CptanPanic said:
So I lock bootloader, and reboot and it is unlocked again.
Click to expand...
Click to collapse
You can try just flashing the cache.img but I think you're going to have to rma it
Sent from my Nexus 5 using XDA Free mobile app

Flashing to stock failed and I fear my old N7 2012 is gone..

So I began the process being able to see the device via terminal in linux. Downloaded the firmware and proceeded to begin the flash process.
Well.... I think it is safe to say it hasnt gone as well as I had hoped.
...
(bootloader) Bootloader is already unlocked
OKAY \[ 0.015s\]
finished. total time: 0.015s
erasing 'boot'...
OKAY \[ 0.017s\]
finished. total time: 0.017s
\*\*\*\*\*\*\*\* Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY \[ 0.084s\]
finished. total time: 0.084s
erasing 'recovery'...
OKAY \[ 0.017s\]
finished. total time: 0.017s
\*\*\*\*\*\*\*\* Did you mean to fastboot format this ext4 partition?
erasing 'system'...
OKAY \[ 0.109s\]
finished. total time: 0.109s
\*\*\*\*\*\*\*\* Did you mean to fastboot format this ext4 partition?
erasing 'userdata'...
OKAY \[ 4.950s\]
finished. total time: 4.950s
target didn't report max-download-size
sending 'bootloader' (2100 KB)...
OKAY \[ 0.265s\]
writing 'bootloader'...
OKAY \[ 1.207s\]
finished. total time: 1.472s
rebooting into bootloader...
OKAY \[ 0.015s\]
finished. total time: 0.065s
target didn't report max-download-size
sending 'radio' (16384 KB)...
OKAY \[ 1.965s\]
writing 'radio'...
FAILED (remote: (BadParameter))
finished. total time: 1.986s
rebooting into bootloader...
OKAY \[ 0.015s\]
finished. total time: 0.065s
extracting android-info.txt (0 MB)...
extracting boot.img (4 MB)...
target didn't report max-download-size
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
extracting recovery.img (5 MB)...
archive does not contain 'recovery.sig'
extracting system.img (629 MB)...
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
archive does not contain 'vendor.img'
wiping userdata...
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (command write failed (Success))
\--------------------------------------------
getvar:version-bootloader FAILED (command write failed (Success))
finished. total time: 0.000s
​
I had gotten to the point where all I could do was restart bootloader in the download mode.. on the device as it no longer had anything to boot in to.
The thing is now I get no life from the tablet whatsover! So before it was a flashing of the image issue and now I have no life in the tablet at all
Have I rendered this tablet as more of a paperweight as before?
Sent from my SM-N960F using Tapatalk

Boot into bootloader and try reflashing

Chinmay2006 said:
Boot into bootloader and try reflashing
Click to expand...
Click to collapse
Thats the problem now. There is no life from it whatsoever
Sent from my SM-N960F using Tapatalk

jr866gooner said:
Thats the problem now. There is no life from it whatsoever
Sent from my SM-N960F using Tapatalk
Click to expand...
Click to collapse
Is it charging

Chinmay2006 said:
Is it charging
Click to expand...
Click to collapse
Sadly no indication on screen however can feel its warm when charging.
I have taken off the back to disconnect and reconnect the battery but that hasn't worked.
Sent from my SM-N960F using Tapatalk

@jr866gooner what device do you have and which firmware did you try to flash?
If I remember well, there were some Google firmwares which contained a defective bootloader ...

AndDiSa said:
@jr866gooner what device do you have and which firmware did you try to flash?
If I remember well, there were some Google firmwares which contained a defective bootloader ...
Click to expand...
Click to collapse
Hey! Sorry I thought I had mentioned it.. I have a Nexus 7 2012 (Grouper) model. The Google firmware I tried to flash was the 4.4.4 version labled nakasi-ktu84p.
I was looking to downgrade to get some performance back as it couldnt even cope with the app drawer being opened lol

Hmm ... looking here there is a chance that you really took one of the defective firmware versions.
If this is the case then you probably would like to have a look here or at this Github Project

AndDiSa said:
Hmm ... looking here there is a chance that you really took one of the defective firmware versions.
If this is the case then you probably would like to have a look here or at this Github Project
Click to expand...
Click to collapse
Thanks for the info. I have and intend to leave the device with its battery disconnected overnight but looking at this its a goner. Thanks Google!! I wish I'd noticed the bootloader information sooner! I sadly don't have another Nexus to massage it back to life.
I kind of wanted just a mess about tablet so I might either grab one second hand but get the 2013 model or do an insurance claim query. Not sure if that would be covered but it cant hurt to speak to someone for advice.
Sent from my SM-N960F using Tapatalk

@jr866gooner well, if you get your SBK @enderzip for sure will provide you with the blob.bin needed to unbrick your device.