Database Info

[NvFlash] [Recovery] With [Generated Blobs][TF-700-T]

This is a general users guide to unbricking your tf700t...
This is only what I did, It was successfull for me.
I did this on linux mint 32 bit, so thats what I can help with. Im sure it can be done on windows but who would want to!!!!!!LOL
I will help anyone that needs it of course... No matter the os... Just let me know!!!!
What you need
Your device specific nvflash backup files generated while enabling nvflash.
!!!!!!!!If you dont have them there is no help for you!!!!!!
blob.bin
bootloader.ebt
unlock-token.img
factory-config.img
bricksafe.img
Also needed
A tf700t (Its bad now, but all will be ok)
Fully charged tf700t (Just plug it in, it will charge no matter what...If not you dont need my help!!!!)
Asus data cable
Linux Mint 32bit PC
Super user permission
Stock firmware blob (from asus's web site, make sure you get the right one)
nvflash and wheelie
And fastboot for your PC
Downloads
nvflash/wheelie-Linux
click me
nvflash/wheelie-Windows
click me
Asus Stock firmware---MAKE SURE YOU GET THE CORRECT SKU FOR YOUR 700
click me
INSTRUCTIONS
Extract wheelie and nvflash to your home folder...
Extract your stock firmware in your downloads folder twice...You will see a blob file rename it boot.blob and move it to your home folder...
Move the above mentioned device specific files to your home folder...
In your home folder you should have
blob.bin
unlock-token.img
factory-config.img
bricksafe.img
bootloader.ebt
nvflash
wheelie
boot.blob (we renamed it in the last step)
Start your device in APX mode [Power On + Volume Up]. Your tablet screen will remain blank in APX mode....
Bootstrap your device (enter nvFlash mode) while your device is in APX mode using wheelie....
I am going to show you the outputs of my process ....
If you are running windows drop the 'sudo ./' and make sure your CMD window is opened as admin
Code:
sudo ./wheelie --blob blob.bin
[email protected]:~ > sudo ./wheelie --blob blob.bin
OUTPUT
Wheelie 0.1 - Preflight for nvflash.
Copyright (c) 2011-2012 androidroot.mobi
========================================
Waiting for device in APX mode...
[=] Chip UID: 0x15d2bbce2501405
[=] RCM Version: 0x30001
[=] CPU Model: Tegra 3
[+] Sending bootloader...
Sending file: 100 %
[!] Done - your device should now be ready for nvflash
It may shutdown after each command, get back into nvflash with the above steps.....
Code:
sudo ./nvflash -r --download 7 unlock-token.img
[email protected]:~ > sudo ./nvflash -r --download 7 unlock-token.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: unlock-token.img
/ 8388608/8388608 bytes sent
unlock-token.img sent successfully
Code:
sudo ./nvflash -r --download 14 factory-config.img
[email protected]:~ > sudo ./nvflash -r --download 14 factory-config.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: factory-config.img
/ 5242880/5242880 bytes sent
factory-config.img sent successfully
Code:
sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
[email protected]:~ > sudo ./nvflash -r --rawdevicewrite 0 2944 bricksafe.img
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
sending file: bricksafe.img
/ 12058624/12058624 bytes sent
bricksafe.img sent successfully
Code:
sudo ./nvflash -r --go
[email protected]:~ > sudo ./nvflash -r --go
OUTPUT
Nvflash v1.13.87205 started
[resume mode]
At this point if it will not reboot or shut down do this
hold power button and volume down to boot into fastboot...You will now have fastboot.
We are not done yet!!! Getting close now!!!!!!
Run these command in fastboot in this order
The next command is to just verify your computer can see your device
Code:
fastboot devices
INPUT
[email protected]:~ > fastboot devices
OUTPUT
015d2bbce2501405 fastboot
Code:
fastboot erase system
INPUT
[email protected]:~ > fastboot erase system
OUTPUT
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 2.954s]
finished. total time: 2.954s
Code:
fastboot erase recovery
INPUT
[email protected]:~ > fastboot erase recovery
OUTPUT
erasing 'recovery'...
OKAY [ 1.945s]
finished. total time: 1.945s
Code:
fastboot -w
INPUT
[email protected]:~ > fastboot -w
OUTPUT
erasing 'userdata'...
OKAY [ 23.188s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29618601984
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7231104
Block groups: 221
Reserved block group size: 1024
Created filesystem with 11/1810432 inodes and 157662/7231104 blocks
sending 'userdata' (139133 KB)...
writing 'userdata'...
OKAY [ 26.358s]
erasing 'cache'...
At this point it just hangs on erasing 'cache'
I just close terminal and open new one, and run the next command
If your tablet hangs just reboot back into fastboot again
Code:
fastboot erase boot
INPUT
[email protected]:~ > fastboot erase boot
OUTPUT
erasing 'boot'...
OKAY [ 1.209s]
finished. total time: 1.209s
Code:
fastboot erase misc
INPUT
[email protected]:~ > fastboot erase misc
OUTPUT
erasing 'misc'...
OKAY [ 0.978s]
finished. total time: 0.978s
Code:
fastboot erase cache
INPUT
[email protected]:~ > fastboot erase cache
OUTPUT
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 2.843s]
finished. total time: 2.843s
Code:
fastboot -i 0x0b05 flash system boot.blob
During the sending/writing process of this step you will get the blue bar on your screen.....
INPUT
[email protected]:~ > fastboot -i 0x0B05 flash system boot.blob
OUTPUT
erasing 'system'...
OKAY [ 2.339s]
sending 'system' (800927 KB)...
OKAY [133.094s]
writing 'system'...
[OKAY [178.036s]
finished. total time: 313.469s
Code:
fastboot -i 0x0B05 reboot
[email protected]:~ > fastboot -i 0x0B05 reboot
OUTPUT
rebooting...
finished. total time: 0.020s
You will now be back to stock rom stock bootloader but still unlocked!!!!!!!!!!!!!
Boot fully into rom than you can do whatever you would like!!!!!!!!!!!

Feedback
I am here to help just ask..... We will get you on the right path!!!!!

Mine

thanks
will be bookmarking this page! i hope to never have to do this but will have step by step instruction if something would ever go terribly wrong. i hope this helps people out before they totaly give up on there device just remember the TF700T is 99.5% unbreakable

First off, thanks for the walk through. I unfortunately had to use this due to a bad rom flash. Everything works like a charm up until the user data wipe. This is what I get:
c:\peri>fastboot -w
erasing 'userdata'...
OKAY [ 22.643s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.003s]
erasing 'cache'...
OKAY [ 1.277s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.001s]
finished. total time: 23.925s
After restoring nvflash the device shows up in fastboot but labeled as ?. The system recognizes it and interacts with it though. Everything else goes well until flashing the boot.blob (9.4.5.30). The file uploads like it is supposed to but when it goes to install I get the red text on the screen saying "signature mismatch" or "failed to process command flash: system error(0x170003)." Tried with all tf700 us updates with the same result. I am doing this from a windows 7 machine and all my drivers are up to date. Any thoughts or ideas?

Chazzfazzle said:
First off, thanks for the walk through. I unfortunately had to use this due to a bad rom flash.
Click to expand...
Click to collapse
?? A bad ROM flash is usually easily recoverable using the recovery, as it does not touch your bootloader. How did you manage to break fastboot and your recovery with a bad ROM flash?
Chazzfazzle said:
I am doing this from a windows 7 machine and all my drivers are up to date. Any thoughts or ideas?
Click to expand...
Click to collapse
Try it under Linux - there were several reports about problems with nvflash under Windows.

Fastboot
Chazzfazzle said:
First off, thanks for the walk through. I unfortunately had to use this due to a bad rom flash. Everything works like a charm up until the user data wipe. This is what I get:
After restoring nvflash the device shows up in fastboot but labeled as ?. The system recognizes it and interacts with it though. Everything else goes well until flashing the boot.blob (9.4.5.30). The file uploads like it is supposed to but when it goes to install I get the red text on the screen saying "signature mismatch" or "failed to process command flash: system error(0x170003)." Tried with all tf700 us updates with the same result. I am doing this from a windows 7 machine and all my drivers are up to date. Any thoughts or ideas?
Click to expand...
Click to collapse
Make sure that you open your CMD window as administrator... There is a hole about 2 cm below the sd card slot. I have heard some people needing to push this... Here is what they are doing seems some have to do this and some dont... Dont know if it will help any worth a shot...
Reset your device with a paperclip/needle (about 2 cm down from your sdcard slot) and hold vol-down to enter fastboot
If thats not it than... Im going to have to go with _that... Linux is what you need for your next step!!!!!! Let me know and as always thx lj

Sorry for the delay. I am having to learn how to dual boot linux and windows and learning how the system works. I will say this is wicked fast compared to windows 7. If this is successful I may consider converting. But I digress. I will give it a shot and let you know how it worked out. I will also try the reset switch. And once again thanks for all the info. You guys are awesome.

So I got Ubuntu up and running and I have the adb and fastboot drivers installed. I also dl'ed the linux wheelie and nvflash files. The computer can see my device when I run fastboot devices command but it won't run wheelie from the directory I created for it. Where do I put my files so the terminal can run them?

Chazzfazzle said:
So I got Ubuntu up and running and I have the adb and fastboot drivers installed. I also dl'ed the linux wheelie and nvflash files. The computer can see my device when I run fastboot devices command but it won't run wheelie from the directory I created for it. Where do I put my files so the terminal can run them?
Click to expand...
Click to collapse
Linux does not run programs in your current directory by default, for security reasons. To run wheelie from your current directory, type "./wheelie".

I think it's either replacement or service time. I got everything running on ubuntu finally and I get the same bunk about the file system not being recognised. Maybe the internal card is bad or something. I tried reformatting the internal card with flatline and it completes but it doesn't change anything. Unless there is a way to format it with ubuntu. Problem is it does not show as a device. Regardless, thank you all for your help and I learned a lot more than I expected to through this process. Definitely a win in my book.
Edit: You sir/madame are a god/goddess. For once my stubborness is a good thing. It took a few trys and I had to assemble the tools from a few different sources other than the obvious but I am back in business. Turns out the nvflash from androidroot.mobi is not compatible for me. But the developer version from nvidia sure is. Had to install adb/fastboot from lifehacker. Am now looking at ICS start screen and it is beautiful. A million thanks you are owed and you have earned every one.

Great!!
Chazzfazzle said:
I think it's either replacement or service time. I got everything running on ubuntu finally and I get the same bunk about the file system not being recognised. Maybe the internal card is bad or something. I tried reformatting the internal card with flatline and it completes but it doesn't change anything. Unless there is a way to format it with ubuntu. Problem is it does not show as a device. Regardless, thank you all for your help and I learned a lot more than I expected to through this process. Definitely a win in my book.
Edit: You sir/madame are a god/goddess. For once my stubborness is a good thing. It took a few trys and I had to assemble the tools from a few different sources other than the obvious but I am back in business. Turns out the nvflash from androidroot.mobi is not compatible for me. But the developer version from nvidia sure is. Had to install adb/fastboot from lifehacker. Am now looking at ICS start screen and it is beautiful. A million thanks you are owed and you have earned every one.
Click to expand...
Click to collapse
Hey thats great news, would you email me those links and I will integrate them into the process!!! Thx lj

Chazzfazzle said:
I think it's either replacement or service time. I got everything running on ubuntu finally and I get the same bunk about the file system not being recognised. Maybe the internal card is bad or something. I tried reformatting the internal card with flatline and it completes but it doesn't change anything. Unless there is a way to format it with ubuntu. Problem is it does not show as a device. Regardless, thank you all for your help and I learned a lot more than I expected to through this process. Definitely a win in my book.
Edit: You sir/madame are a god/goddess. For once my stubborness is a good thing. It took a few trys and I had to assemble the tools from a few different sources other than the obvious but I am back in business. Turns out the nvflash from androidroot.mobi is not compatible for me. But the developer version from nvidia sure is. Had to install adb/fastboot from lifehacker. Am now looking at ICS start screen and it is beautiful. A million thanks you are owed and you have earned every one.
Click to expand...
Click to collapse
Hi Chazzfazzle,
I have exactly the same problem you've had.
I'm stuck at "Failed to process command flash:system error(0x170003)"
Could you please explain me what you did to fix it?
Thank you
---------- Post added at 04:29 PM ---------- Previous post was at 04:16 PM ----------
@lj50036
Like Chazzfazzle, at the "sudo ./fastboot -w" step, i got :
Code:
$ sudo ./fastboot -w
erasing 'userdata'...
OKAY [ 10.358s]
formatting 'userdata' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
erasing 'cache'...
OKAY [ 2.089s]
formatting 'cache' partition...
Erase successful, but not automatically formatting.
File system type not supported.
OKAY [ 0.000s]
finished. total time: 12.448s
And a "sudo ./fastboot devices" gives me :
Code:
$ sudo ./fastboot devices
???????????? fastboot
Did I miss something?

Fastboot Install
How are you installing fastboot??
What Linux are you running??

I've downloaded the sdk from the Android website
dl.google.com/android/adt/adt-bundle-linux-x86_64-20131030.zip
I've tried with the fastboot package in the saucy universe repository too : android-tools-fastboot

samheg said:
I've downloaded the sdk from the Android website
dl.google.com/android/adt/adt-bundle-linux-x86_64-20131030.zip
I've tried with the fastboot package in the saucy universe repository too : android-tools-fastboot
Click to expand...
Click to collapse
I'm running Ubuntu gnome 13.10

An additional question :
I've generated the blobs and the bricksafe.img when the tablet was still on ICS.
After that, I've updated it to JB and so to a version 10.6.1.14.x of the bootloader.
Could it be the cause of my problems with nvflash/fastboot ?
Sent from my Nexus 4 using xda app-developers app

Feedback/Fastboot
samheg said:
An additional question :
I've generated the blobs and the bricksafe.img when the tablet was still on ICS.
After that, I've updated it to JB and so to a version 10.6.1.14.x of the bootloader.
Could it be the cause of my problems with nvflash/fastboot ?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
No, that should not affect fastboot... I am digging for more info about your issue, I have some solid leads, just need a little more time, have not forgot about you... as always thx lj

My problem ended up being the nvflash distro from androidroot.mobi. I don't know if it is broken or just incompatible with my system. I ended up finding a working (worked for me anyway) version from nvidia directly. It's part of the Linux Developer Kit.
Get it here: https://developer.nvidia.com/linux-tegra
Make sure you only, and I can't stress this enough, make doubly sure you only get the Cardhu Driver Pack. NvFlash is located in the bootloader folder of the archive. I replaced androidroot.mobi's version with this and the rest is history. Hope this helps.
Also I did this on Ubuntu 12.04.3. I see you are on the latest release. I seriuosly doubt that makes any difference but, the more you know...

Unfortunately that didn't solve my problem.
I'm still stuck with fastboot not recognizing my tf700t.
Code:
$ sudo ./fastboot devices
???????????? fastboot
I'm open to any suggestion.

Stuck on boot animation after resetting to stock

Hi,
A friend asked me to look at his Nexus 5.
It seemed as though his son was trying to flash a custom rom but somewhere along the way things went wrong and it got stuck on the boot animation.
I tried resetting it to factory using this thread.
Followed method 2 and finished it up with "Wipe data/factory data" reset. I did not however relock the boot loader.
I used the factory image 6.0.1 (MMB29S).
Everything went well, no errors, but even after doing all that the phone is still stuck on the boot animation. I tried redoing the "Wipe data/factory data" reset, but the phone is still stuck on boot animation.
I left for around 20 minutes with no change.
All the other threads I have read seem to indicate doing the "wipe data/factory data" reset should correct this issue but it hasn't seemed to help.
I also found this thread. The last post could possibly be another option.
Is there anything I can try? or is there a log I can look?
Any suggestions would be greatly appreciated.
Cheers

Boot the phone into fastboot and flash the userdata.img from the stock rom to the phone using the following command: fastboot flash userdata userdata.img. After flashing, boot into stock recovery using the volume and power button, wipe data and cache, reboot.

audit13 said:
Boot the phone into fastboot and flash the userdata.img from the stock rom to the phone using the following command: fastboot flash userdata userdata.img. After flashing, boot into stock recovery using the volume and power button, wipe data and cache, reboot.
Click to expand...
Click to collapse
Thanks for the reply.
I did as you suggested, unfortunately I am still stuck on boot animation.
Output from command
Code:
c:\image-hammerhead-mmb29s>fastboot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 8.014s]
sending 'userdata' (137318 KB)...
OKAY [ 4.510s]
writing 'userdata'...
OKAY [ 9.149s]
finished. total time: 21.673s
I was just looking at the contents of the zip I downloaded from the developer site. The data stamps on the images seem old. Most date back to 2009. Perhaps I have downloaded the wrong files?

Did the userdata.img file come from the mmb29s ROM? After flashing, did you immediately boot into recovery and perform a factory wipe?

audit13 said:
Did the userdata.img file come from the mmb29s ROM? After flashing, did you immediately boot into recovery and perform a factory wipe?
Click to expand...
Click to collapse
Yes the userdata.img did come from the mmb29s ROM. I have no other ROM files downloaded.
Yes I did I believe, if I recall correctly, these were my steps:
Booted phone into fastboot by pressing the power and down volume key
flashed the userdata.img using the command provided
Used the volume rocket to select "Recovery"
When the dead Android appeared I pressed the power button and up volume rocker to display the menu
Proceeded to the option to wipe and reset data
Rebooted the phone
I am pretty sure those were the steps I used.
Should I have rebooted first before going directly into Recovery?

Yup, those are the proper steps.
When you wiped in recovery, did you see a line at the bottom that said something like "invalid format" or "could not mount" just before the data and cache partitions were formatted?

audit13 said:
Yup, those are the proper steps.
When you wiped in recovery, did you see a line at the bottom that said something like "invalid format" or "could not mount" just before the data and cache partitions were formatted?
Click to expand...
Click to collapse
No I didn't notice any error messages unfortunately.
And I don't recall seeing any error messages during any of the other steps I have performed.
The commands all seem to successfully execute with no errors.
Does it at all make sense for me to go back and completely redo all the steps from the tutorial in my first post?
I can post the outputs from all the commands if you think that would at all be helpful?

I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.

audit13 said:
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
Click to expand...
Click to collapse
Okay perfect. I will give method 1 a try tonight (I am unfortunately at work right now).
I will report back tonight... hopefully with good news

audit13 said:
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
Click to expand...
Click to collapse
Sorry for the late reply on this.
I got around to doing the steps above.
Unfortunately I am still stuck on the boot animation screen.
Here is the output from the commands I ran
Code:
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.297s]
writing 'bootloader'...
OKAY [ 0.500s]
finished. total time: 0.797s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.078s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.540s]
writing 'radio'...
OKAY [ 3.125s]
finished. total time: 4.665s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.063s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.28
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
OKAY [ 0.109s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.781s]
sending 'recovery' (10012 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.828s]
erasing 'system'...
OKAY [ 1.297s]
sending 'system' (1020413 KB)...
OKAY [ 32.163s]
writing 'system'...
OKAY [ 69.508s]
erasing 'userdata'...
OKAY [ 8.326s]
sending 'userdata' (137318 KB)...
OKAY [ 4.500s]
writing 'userdata'...
OKAY [ 9.138s]
erasing 'cache'...
OKAY [ 0.672s]
sending 'cache' (13348 KB)...
OKAY [ 0.625s]
writing 'cache'...
OKAY [ 1.078s]
rebooting...
finished. total time: 130.775s
Press any key to exit...
////// -------- AFTER COMPLETE POWER OFF AND REBOOT -------- \\\\\\\\
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.625s]
finished. total time: 0.641s
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.384s]
finished. total time: 8.399s
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 8.220s]
sending 'userdata' (137318 KB)...
OKAY [ 4.516s]
writing 'userdata'...
OKAY [ 9.156s]
finished. total time: 21.892s
Everything seemed to go okay.
Does everything in the output above look okay?

Everything looks fine. Did you boot into recovery and perform a factory wipe after flashing userdata.img?

audit13 said:
Everything looks fine. Did you boot into recovery and perform a factory wipe after flashing userdata.img?
Click to expand...
Click to collapse
Yes I did do that and did the clear of the cache as well since it posted that error message like you said it would.
So I did both as you explained.
I took a picture of the phone itself after the userdata wipe.
https://www.dropbox.com/s/k05s06avrha1lfv/IMG_20160206_153435.jpg?dl=0

Hmm, I'm not sure what is wrong because you did exactly what I do every time I need to fix a bootloop.

audit13 said:
Hmm, I'm not sure what is wrong because you did exactly what I do every time I need to fix a bootloop.
Click to expand...
Click to collapse
Well that sucks!
I had read that in some cases this can be caused by a hardware issue. Any chance it could be that?
Btw, the links I provided to the stock Google images, were they the correct images?

These are the stock images: https://developers.google.com/android/nexus/images#hammerhead
Did you try flashing a stock 4.4.2 or 5.01 image too?

audit13 said:
These are the stock images: https://developers.google.com/android/nexus/images#hammerhead
Did you try flashing a stock 4.4.2 or 5.01 image too?
Click to expand...
Click to collapse
hi,
sorry for my late reply. I got sick and just didn't have it in me to try anything new.
I tried flashing 5.0.1 tonight and unfortunately wound up in another boot loop. I will have to try the steps again where you manually reflash userdata. Hopefully I will have time tomorrow!

Hi
My phone has the exact same problem as stated by OP. I even tried flashing kitkat and lollipop but the problem persist. The phone still stuck at boot animation screen. PLS help.

Boot into ffastboot, relock the bootloader, and then reboot into fastboot. Does the bootloader remain unlocked?

audit13 said:
Boot into ffastboot, relock the bootloader, and then reboot into fastboot. Does the bootloader remain unlocked?
Click to expand...
Click to collapse
The bootloader is now locked. Still, I can't boot the phone completely. stuck at Google boot animation.

At this point, I would conclude that something is wrong with the memory chip.

no command & no drivers

hello
my phone stuck on the circles dots that spins i gave it like 30 mints and nothing, when i try to plug it in the PC i dont have the drivers and when i try to get in the recovery mode i get the no command massage
i really dont know what to do now...
ty for your help

When you boot to recovery, you don't see the dead android on his back?

when i try to get to recovery i see the dead android with no command
but i have access to boot loader (not really helping)

When you see the dead android, press and hold power button, then press volume up.

audit13 said:
When you see the dead android, press and hold power button, then press volume up.
Click to expand...
Click to collapse
together or one after another?
what i should see?

One after the other and it will take you I to stock recovery.

ok got to there
when i try to make wipe i get stuck and the the died android get flashing(same as cache)

What happens when you factory wipe? How do you get back to the android?

when i factory wipe i see the dead android flashing like every 5 sec for 1 mili sec
and if i want to get back to boot loader or something else i press power button and up\down
i think its the cache that doing the problem becuas when i do the factory rest its saying:
--Wiping data...
formatting \data...(1-2 minuts wait)
formatting \cache...
after 5 sec flashing of dead android
and if i do wipe of cache i get the flashing like 5 sec after...

Try flashing a stock rom via fastboot. Make sure to perform a factory wipe before booting the rom for the first time.

audit13 said:
Try flashing a stock rom via fastboot. Make sure to perform a factory wipe before booting the rom for the first time.
Click to expand...
Click to collapse
how can i flash a rom if i dont have any drivers and the Pc dont recognize the phone when i press on "update from ADB"...?

Did you install the drivers before connecting the phone? You can't use stock recovery to flash a stock rom, you use fastboot mode.
Have you tried different USB cables, USB ports, computers, and operating systems? Is the bootloader unlocked?

ok so this is the deal with the phone.
i didn't touch this phone for the last 3 mounts and now i am thinking to buy new one or to fix this(prefer to fix).
the pc that i am using dont have the driver and the phone wont start(stuck in loop-dots circle) so i cant really install the drivers properly.
the phone is unlock-root dont remember if it have superuser and i cant think of a way to fix it
i dont have fast boot mode
thank you for your help i realy need him alive

Not sure how the phone can't have fastboot mode. What happens when you try to boot into fastboot mode?

i got the driver on the PC and tryed to install the factory rom
after he finished the phone starts to go up but still stuck on the circle dots(waited all day)
after that tried to wipe again and nothing..

After flashing the stock ROM, boot back into fastboot mode, flash userdata.img file, immediately boot into recovery from fastboot mode, perform a factory wipe, reboot.

"flash userdata.img file, immediately boot into recovery from fast boot mode"
need more info for that please its new to me...
how i can flash it if i dont have recovery mode?
i am using nrt program to install the images, if you have any other why i would like to know

just tried Flashing the factory images using method 1 from here:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
but no success. got this error in the cmd line, GOT any suggestions?
target reported max download size of 1073741824 bytes
sending 'bootloader' (2506 KB)...
OKAY [ 0.284s]
writing 'bootloader'...
FAILED (remote flash write failure)
finished. total time 0.490s
rebooting into bootloader...
OKAY [ 0.106s]
finished. total time 0.109s
target reported max download size of 1073741824 bytes
sending 'radio' (42033 KB)...
OKAY [ 1.496s]
writing 'radio'...
FAILED (remote flash write failure)
finished. total time 2.725s
rebooting into bootloader...
OKAY [ 0.102s]
finished. total time 0.104s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
Creating filesystem with parameters
Size 13725835264
Block size 4096
Blocks per group 32768
Inodes per group 8144
Inode size 256
Journal blocks 32768
Label
Blocks 3351034
Block groups 103
Reserved block group size 823
Created filesystem with 11838832 inodes and 936543351034 blocks
Creating filesystem with parameters
Size 734003200
Block size 4096
Blocks per group 32768
Inodes per group 7472
Inode size 256
Journal blocks 2800
Label
Blocks 179200
Block groups 6
Reserved block group size 47
Created filesystem with 1144832 inodes and 5813179200 blocks
--------------------------------------------
Bootloader Version... HHZ12h
Baseband Version..... M8974A-2.0.50.2.26
Serial Number........ 04b3d59122d76e25
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ12h'.
Update requires 'HHZ11d'.
finished. total time 0.547s
Press any key to exit...

Is the bootloader unlocked before the flashed process starts?

the phone is ulocked and if i try to get in bootloader i get the died android, in the prosses of the flash of the factory imege the phone stayes in the same state(in fastboot) after its finished i get all the failers and then the phone restarts and stuck on the dots spin

Nexus 5 - Restore to default without bootloader being unlocked?

I have a nexus 5 that is stuck in a reboot loop. It shows the google logo and then reboots. Trying to enter recovery mode does the same thing.
The phone is not rooted and does not have USB debugging turned on and the option to allow oem unlock in the menu was never turned on.
Because the OEM Unlock option is not enabled i cannot unlock the bootloader with fastboot. The device also does not show up in the 'adb devices' list.
Any ideas would be much appreciated. I have looked all over the place for a solution. (probably missed something, so thanks in advance)

Can you get to the bootloader screen? Nexus 5 does not have OEM unlock. You don't need adb (or unlocked bl) to run fastboot commands. You do need a computer with adb/fastboot drivers set up. If you can get to fastboot, you have options.
Sent from my Nexus 9 using Tapatalk

ritchea said:
Can you get to the bootloader screen? Nexus 5 does not have OEM unlock. You don't need adb (or unlocked bl) to run fastboot commands. You do need a computer with adb/fastboot drivers set up. If you can get to fastboot, you have options.
Sent from my Nexus 9 using Tapatalk
Click to expand...
Click to collapse
I can get to the bootloader and can run adb and fastboot and have tried flashing with the stock image but get "device is locked" error.
Code:
~/Downloads/bullhead-nbd90w $ ./flash-all.sh
target reported max download size of 536870912 bytes
sending 'bootloader' (4603 KB)...
OKAY [ 0.175s]
writing 'bootloader'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.185s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
sending 'radio' (56758 KB)...
OKAY [ 1.367s]
writing 'radio'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.382s
rebooting into bootloader...
OKAY [ 0.001s]
finished. total time: 0.001s
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 11773390848
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 2874363
Block groups: 88
Reserved block group size: 703
Created filesystem with 11/719488 inodes and 84965/2874363 blocks
wiping cache...
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
--------------------------------------------
Bootloader Version...: BHZ11f
Baseband Version.....: M8994F-2.6.33.2.14
Serial Number........: 0121b75a65522deb
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.020s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (12061 KB)...
OKAY [ 0.350s]
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.495s
But yet the image is there and
Here are the outputs of the the adb/fastboot commands for listing the device and unlocking as well.
Code:
$ adb devices
List of devices attached
$ fastboot flashing unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.001s

Does the phone reboot in fastboot mode?

audit13 said:
Does the phone reboot in fastboot mode?
Click to expand...
Click to collapse
Can you explain what you mean by that?

With the phone in fastboot mode, does the phone stay on the screen or does it reboot by itself?

audit13 said:
With the phone in fastboot mode, does the phone stay on the screen or does it reboot by itself?
Click to expand...
Click to collapse
When the phone is in the bootloader screen it stays on the screen.

I thought the phone may have a power button issue but it doesn't sound like it does.

I may be mixing up adb sideload load (from recovery) and fastboot. Some of my devices are locked and some not. Can you run fastboot oem unlock either directly or through a toolkit? Wug's NRT works at times with bootloop. It will wipe your device.
Sent from my Nexus 5X using Tapatalk

ritchea said:
I may be mixing up adb sideload load (from recovery) and fastboot. Some of my devices are locked and some not. Can you run fastboot oem unlock either directly or through the toolkit? It will wipe your device.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Code:
$ fastboot devices
0121b75a65522deb fastboot
Code:
$ fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.009s

See my edit about Wug's toolkit. Are you on PC or mac? Looks like PC, but I don't remember the remote term.
Sent from my Nexus 5X using Tapatalk
---------- Post added at 03:00 PM ---------- Previous post was at 02:47 PM ----------
And this is a nexus 5 not nexus 5x? Sorry to ask but cannot find any references to that error on nexus 5.
Sent from my Nexus 5X using Tapatalk
---------- Post added at 03:03 PM ---------- Previous post was at 03:00 PM ----------
I looked at your cmd text. It is a 5x. That's why you cannot unlock it. The 5x has the unlock switch in developer options.
Sent from my Nexus 5X using Tapatalk
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
If you can't get to recovery from bootloader screen, I would contact google. You may need a replacement. You will find this problem in the nexus 5x thread. It's in the General thread:[GUIDE] unlock/Root/Flash for Nexus 5X.
Sent from my Nexus 5X using Tapatalk

ritchea said:
See my edit about Wug's toolkit. Are you on PC or mac? Looks like PC, but I don't remember the remote term.
Sent from my Nexus 5X using Tapatalk
---------- Post added at 03:00 PM ---------- Previous post was at 02:47 PM ----------
And this is a nexus 5 not nexus 5x? Sorry to ask but cannot find any references to that error on nexus 5.
Sent from my Nexus 5X using Tapatalk
---------- Post added at 03:03 PM ---------- Previous post was at 03:00 PM ----------
I looked at your cmd text. It is a 5x. That's why you cannot unlock it. The 5x has the unlock switch in developer options.
Sent from my Nexus 5X using Tapatalk
---------- Post added at 03:04 PM ---------- Previous post was at 03:03 PM ----------
If you can't get to recovery from bootloader screen, I would contact google. You may need a replacement. You will find this problem in the nexus 5x thread. It's in the General thread:[GUIDE] unlock/Root/Flash for Nexus 5X.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
You are right. Forgot this is a 5X. I will follow up there.

Nexus 5 stuck in boot animation?

Hi,
my Nexus 5 was plugged on my laptop.
After a while I saw, that my phone rebooted. I saw the google logo.
I pressed and hold the "Power Button".
My phone booted again and stuck in the booting animation.
This happened three days ago.
I tried so many things. It's not working.
Maybe I messed up the partition.
The first thing I tried was to flash the android factory image like this (Flashing instructions - don't forget to press the button "ACKNOWLEDGE"):
https://developers.google.com/android/images
I first thought, that maybe the eMMC is fried.
I checked this like this ( https://forum.xda-developers.com/showthread.php?t=1284196 ):
Code:
adb shell
dmesg | grep mmc0
I didn't get a message like this:
Code:
mmc0: failed to get card ready
mmc0: reinit card
mmc0: Starting deferred resume
mmc0: Deferred resume failed
I read, that I should change to usb 2.0 port and the usb cable.
I've also a Galaxy nexus. I've tried to flash a new stock with WugFresh. Everything worked with the usb 2.0 port and the usb cable.
When I tried to do that with my nexus 5 nothing works. I get this failure messages:
FAILED (remote: flash write failure)
I used TWRP (twrp-3.0.3-0-hammerhead.img) and clockwork mod (recovery-clockwork-touch-6.0.4.4-hammerhead.img).
The main errors I get:
Can't mount /data
...
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovers/log
E: Can't open /cache/recovers/log
...
I really don't know what to do.
Is there a method to build the partition new? Or what else can I do?
Thank you for any help.

Does the bootloader relock when rebooted after being unlocked? Have you tried flashing the stock KK ROM?

Yes. It relocks when rebooted.

Do you mean Kit Kat? No, I didn't. I've tried only the new versions like 6.0.1 (MOB31E), 6.0.1 (M4B30Z, Dec 2016).
I will try KK Rom later.

I've downloaded this factory image:
"hammerhead" for Nexus 5 (GSM/LTE)
4.4.4 (KTU84P)
from here: https://developers.google.com/android/images
This is the original "flash-all.bat" file:
Code:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip
echo Press any key to exit...
pause >nul
exit
I've changed the "flash-all.bat" a little bit. I added this line "fastboot oem unlock". When I not add "fastboot oem unlock", I get a message like "not unlocked":
Code:
@ECHO OFF
PATH=%PATH%;"%SYSTEMROOT%\System32"
[B]fastboot oem unlock[/B]
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.16.img
fastboot reboot-bootloader
[B]fastboot oem unlock[/B]
ping -n 5 127.0.0.1 >nul
fastboot -w update image-hammerhead-ktu84p.zip
echo Press any key to exit...
pause >nul
exit
I've started the "flash-all.bat". This is the output:
Code:
target reported max download size of 1073741824 bytes
sending 'bootloader' (2508 KB)...
OKAY [ 0.203s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.406s
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.094s
< waiting for any device >
...
OKAY [ 4.109s]
finished. total time: 4.109s
target reported max download size of 1073741824 bytes
sending 'radio' (45409 KB)...
OKAY [ 1.625s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.844s
rebooting into bootloader...
OKAY [ 0.109s]
finished. total time: 0.109s
< waiting for any device >
...
OKAY [ 6.250s]
finished. total time: 6.250s
target reported max download size of 1073741824 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.img'
wiping userdata...
Creating filesystem with parameters:
Size: 13725835264
Block size: 4096
Blocks per group: 32768
Inodes per group: 8144
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3351034
Block groups: 103
Reserved block group size: 823
Created filesystem with 11/838832 inodes and 93654/3351034 blocks
wiping cache...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
--------------------------------------------
Bootloader Version...: HHZ20f
Baseband Version.....: M8974A-2.0.50.2.29
Serial Number........: 04ae306b2524b05b
--------------------------------------------
checking product...
OKAY [ 0.109s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ20f'.
Update requires 'HHZ11k'.
finished. total time: 0.594s
Press any key to exit...

Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.

audit13 said:
Before flashing again, unlock the bootloader and immediately reboot the phone into fastboot. Does the bootloader relock when the phone is rebooted? If yes, the memory chip is damaged.
Click to expand...
Click to collapse
I have the same problem and after doing that I can see that my eMMC is in fact fried since the bootloader relocks. I was wondering, where is the bootloader/fastboot stored on the device? On the CPU/GPU/RAM stack or on the eMMC. If I swap out the eMMC chip, will I still be able to access it (the bootloader) with a blank eMMC or is it on the eMMC as well? I'm trying to find out what are the steps to format and partition the eMMC after a new one is installed...

I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.

audit13 said:
I don't know where the bootloader is located. When I determine that there is a problem with the memory chip, I just replace the motherboard.
Click to expand...
Click to collapse
Thank you very much for sharing your experience!
I would assume that the bootloader is located on the eMMC since I can't write to the bootloader (or any other) partition from fastboot. I'll have to look into solutions during the weekend since I don't have much time until then, but replacing the MB is a no go for me because of the price.

I'm not sure where you are located but I live in a big city in Canada where I can find deals for people selling Nexus 5 phones with smashed screens and working internal components.
Good luck and please share your results. Thanks.

@audit13: When I unlock the bootloader and then reboot the phone into fastboot. The bootloader relocks.
Is the memory chip now really damaged? Can't I do nothing? My N5 is three years old. I don't want to pay a lot of money for a main board.

The cheapest solution for a damaged emmc chip may be to buy a used Nexus 5 with a smashed screen and working motherboard. This is what I had to do for 2 phones with self re-locking bootloaders.

I bought a display damaged nexus 5. It arrived today. Changed the main board. And Voila! It's working.
The other guy has installed this build:
"hammerhead" for Nexus 5 (GSM/LTE)
6.0.1 (MOB30H)
No my question: Which factory image should I install?
https://developers.google.com/android/images
"hammerhead" for Nexus 5 (GSM/LTE)
...
6.0.1 (MOB30H)
6.0.1 (MOB30M)
6.0.1 (MOB30P)
6.0.1 (MOB30Y)
6.0.1 (MOB31E)
6.0.1 (M4B30X, Oct 2016)
6.0.1 (M4B30Z, Dec 2016)
I'm not sure, because the last two has dates. Are they meaning something (I mean, are they special builds), because the other factory images don't have dates.

Or should I do this:
https://developers.google.com/android/ota
OTA binary image files that allow you to manually update your Nexus or Pixel device. This has the same effect of flashing the corresponding factory images, but without the need of wiping the device.
"hammerhead" for Nexus 5 (GSM/LTE)
6.0.1 (M4B30Z)
Is OTA better than factory images?

OK. I've installed this version 6.0.1 (M4B30Z, Dec 2016). Everything works.