Database Info

Bricked N5 needs to be fixed! Update: RMA

Update 11/19/13: I contacted Google and as they sent me a new n5, my old one is now on it's way "home".
I'll update again in case they don't accept it bc of my unlocked bootloader and custom recovery.
Thanks for everyone who tried to help!
What I know so far:
- Flashing Google's factory image does not change anything
- I have access to ADB and fastboot
- fastboot oem lock will be reverted after reboot
- fastboot flash recovery recovery.img succeeds, but as I boot to recovery there will always be twrp 2.6.3.0
- twrp keeps asking me for a password
- I can pull and push files, however all changes made seem to revert as I reboot
- I can't flash zip or factory reset through recovery
- I can't mount internal storage, cache, persist (only system)
- My phone will somehow boot to the welcome screen, but give me permanent fc's, I reached the settings once
- The guides on going back to stock etc succeed (in cmd), but actually it feels like no changes are beeing made
I will provide you any information you need, as long as you tell me how to get it.
Hey, when I woke up this morning, my nexus was stuck on a boot loop.
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2513701 but it didn't fix my issue. Also, my device would still have TWRP instead of stock recovery (even tried to flash cwm). TWRP can't mount data or cache, can't factory reset and keeps asking me for a password.
When I boot my device (to the welcome, choose language screen) it will only show me all kinds of force closes.
As I set it up, it will tell me my storage is full (at 0mb).
Edit: SuperSU was running after setting up.
I hope that someone has an idea on how to fix my issue..
Click to expand...
Click to collapse

here is my dmesg
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

If at least I could get rid of TWRP in order to RMA..
fastboot flash recovery recovery.img succeeds, but as I start recovery, it still is twrp

George_Mn said:
If at least I could get rid of TWRP in order to RMA..
fastboot flash recovery recovery.img succeeds, but as I start recovery, it still is twrp
Click to expand...
Click to collapse
Is the recovery.img the stock recovery or it's It twrp?

jd1639 said:
Is the recovery.img the stock recovery or it's It twrp?
Click to expand...
Click to collapse
it is the stock recovery.

I really don't like it when ppl push their own threads, but as mine went to page 3 without any attempt to help me, I feel like pushing.
Something messed up my partitions and i have no clue how to solve it. Could it be twrp? When I try to decrypt data it asks me for a password I dont have!

Try cwm twrp has done that to the nexus 7 a few times since 2.5 or so
Sent from my Nexus 5 using Tapatalk

George_Mn said:
Hey, when I woke up this morning, my nexus was stuck on a boot loop.
I followed this guide: http://forum.xda-developers.com/showthread.php?t=2513701 but it didn't fix my issue. Also, my device would still have TWRP instead of stock recovery (even tried to flash cwm). TWRP can't mount data or cache, can't factory reset and keeps asking me for a password.
When I boot my device (to the welcome, choose language screen) it will only show me all kinds of force closes.
As I set it up, it will tell me my storage is full (at 0mb).
Edit: SuperSU was running after setting up.
I hope that someone has an idea on how to fix my issue..
Click to expand...
Click to collapse
I had the same issue.
I fixed it by booting into fastboot, doing a bootloader lock and then a bootloader unlock. All your data gets wiped and the storage gets formated.
But it worked for me and was worth the data loss

Harry GT-S5830 said:
Try cwm twrp has done that to the nexus 7 a few times since 2.5 or so
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I can't. When flashing any other then twrp, upon booting recovery it still shows twrp.

maaximal said:
I had the same issue.
I fixed it by booting into fastboot, doing a bootloader lock and then a bootloader unlock. All your data gets wiped and the storage gets formated.
But it worked for me and was worth the data loss
Click to expand...
Click to collapse
I already locked and unlocked once, but I will try again.

George_Mn said:
I already locked and unlocked once, but I will try again.
Click to expand...
Click to collapse
After that use the stock image flash-all.bat/.sh from the google factory tgz (https://developers.google.com/android/nexus/images?hl=us#hammerhead)

bump

Try this. Download the factory image if you haven't done so already: https://developers.google.com/android/nexus/images#hammerhead and extract it down to the images.
Boot into the bootloader and use these commands:
Code:
fastboot format boot
fastboot format cache
fastboot format recovery
fastboot format system
fastboot format userdata
Then run the flash-all.bat
Report back.

El Daddy said:
Try this. Download the factory image if you haven't done so already: https://developers.google.com/android/nexus/images#hammerhead and extract it down to the images.
Boot into the bootloader and use these commands:
Code:
fastboot format boot
fastboot format cache
fastboot format recovery
fastboot format system
fastboot format userdata
Then run the flash-all.bat
Report back.
Click to expand...
Click to collapse
Unfortunately this didn't change anything, also still on twrp. edit: internal storage also still at 0mb.
Code:
E:\Users\George_Mn\Desktop\tools>fastboot format boot
formatting 'boot' partition...
Formatting is not supported for filesystem with type 'emmc'.
FAILED ()
finished. total time: 0.101s
E:\Users\George_Mn\Desktop\tools>fastboot format cache
erasing 'cache'...
OKAY [ 0.217s]
formatting 'cache' partition...
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
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.883s]
finished. total time: 2.103s
E:\Users\George_Mn\Desktop\tools>fastboot format recovery
formatting 'recovery' partition...
Formatting is not supported for filesystem with type 'emmc'.
FAILED ()
finished. total time: 0.105s
E:\Users\George_Mn\Desktop\tools>fastboot format system
erasing 'system'...
OKAY [ 0.213s]
formatting 'system' partition...
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
sending 'system' (18800 KB)...
writing 'system'...
OKAY [ 2.400s]
finished. total time: 2.616s
E:\Users\George_Mn\Desktop\tools>fastboot format userdata
erasing 'userdata'...
OKAY [ 0.491s]
formatting 'userdata' partition...
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
sending 'userdata' (137318 KB)...
writing 'userdata'...
OKAY [ 14.469s]
finished. total time: 14.964s
Code:
sending 'bootloader' (2506 KB)...
OKAY [ 0.283s]
writing 'bootloader'...
OKAY [ 0.401s]
finished. total time: 0.688s
rebooting into bootloader...
OKAY [ 0.094s]
finished. total time: 0.096s
sending 'radio' (42033 KB)...
OKAY [ 1.467s]
writing 'radio'...
OKAY [ 2.847s]
finished. total time: 4.317s
rebooting into bootloader...
OKAY [ 0.089s]
finished. total time: 0.090s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11d
Baseband Version.....: M8974A-1.0.25.0.17
Serial Number........: 032ac31c08e6b033
--------------------------------------------
checking product...
OKAY [ 0.101s]
checking version-bootloader...
OKAY [ 0.098s]
checking version-baseband...
OKAY [ 0.098s]
sending 'boot' (8620 KB)...
OKAY [ 0.488s]
writing 'boot'...
OKAY [ 0.726s]
sending 'recovery' (9202 KB)...
OKAY [ 0.541s]
writing 'recovery'...
OKAY [ 0.763s]
erasing 'system'...
OKAY [ 0.254s]
sending 'system' (692940 KB)...
OKAY [ 22.651s]
writing 'system'...
OKAY [ 44.442s]
erasing 'userdata'...
OKAY [ 0.509s]
formatting 'userdata' partition...
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
sending 'userdata' (137318 KB)...
writing 'userdata'...
OKAY [ 14.418s]
erasing 'cache'...
OKAY [ 0.241s]
formatting 'cache' partition...
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
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.871s]
rebooting...
finished. total time: 87.765s
Press any key to exit...

Hmmmm. Alright try 'fastboot erase recovery' instead.
Then just flash the recovery.img.
'fastboot flash recovery recovery.img'
Sent from my Nexus 5 using Tapatalk

El Daddy said:
Hmmmm. Alright try 'fastboot erase recovery' instead.
Then just flash the recovery.img.
'fastboot flash recovery recovery.img'
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
actually tried that right after the first attempt. no luck.

I've found some similar cases around xda. Specifically with the N7. When twrp asks for a password can you hit "back" to get to the menu where you are able to factory reset?
Maybe @efrant has an idea. He's pretty good with this stuff.
Sent from my Nexus 5 using Tapatalk

El Daddy said:
I've found some similar cases around xda. Specifically with the N7. When twrp asks for a password can you hit "back" to get to the menu where you are able to factory reset?
Maybe @efrant has an idea. He's pretty good with this stuff.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I can hit cancel but factory reset fails.
Code:
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Formatting Cache using make_ext4fs function.
E:Unable to mount '/cache'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
also, on the mount menu, there is an option to decrypt data which asks me for the password.

You didn't happen to flash a recovery or boot image that was for a device other than the N5 did you? I think that would be one cause of what you are seeing.
There is still a way to recover the device by flash the stock TOT file in download mode.
Let me see if I can find the right DLL for the N5, and I'll post in this thread.

George_Mn said:
I can hit cancel but factory reset fails.
Code:
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
E:Unable to mount '/cache'
E:Unable to mount '/cache'
Formatting Cache using make_ext4fs function.
E:Unable to mount '/cache'
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/persist'
E:Unable to mount storage.
also, on the mount menu, there is an option to decrypt data which asks me for the password.
Click to expand...
Click to collapse
It's asking you for a password because you didn't boot into android after flashing TWRP. For some reason, you cannot boot directly into TWRP right after any wipe (of userdata) without booting into Android first. It causes issues.

[Q] Nexus 5 CM just spins, will not boot, adp push to phone, device not recognized

I installed CM on my Nexus 3 and 10 without incident.
I unlocked and installed CM and clockwork recovery on my Nexus 5 but when I booted into CM, nothing happened except that the CM logo just spun until I turned the phone back off. I wanted to go back to the factory image but despite sudo fastboot devices showing that it was connected, sudo adb push [image].zip /sdcard/ I just got device not found.
I removed android-tools-adp and android-tools-fastboot and reinstalled thinking there might be a driver issue but that has not resolved the problem.
Looking for a way to get either the stock 4.4 or CM 11 working.
from fastboot screen:
Code:
FASTBOOT MODE
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D820 32GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11d
BASEBAND VERSION - M8974A-1.0.25.0.17
CARRIER INFO -None
SERIAL NUMBER - []
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked

iconoclasthero said:
I installed CM on my Nexus 3 and 10 without incident.
I unlocked and installed CM and clockwork recovery on my Nexus 5 but when I booted into CM, nothing happened except that the CM logo just spun until I turned the phone back off. I wanted to go back to the factory image but despite sudo fastboot devices showing that it was connected, sudo adb push [image].zip /sdcard/ I just got device not found.
I removed android-tools-adp and android-tools-fastboot and reinstalled thinking there might be a driver issue but that has not resolved the problem.
Looking for a way to get either the stock 4.4 or CM 11 working.
from fastboot screen:
Code:
FASTBOOT MODE
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D820 32GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11d
BASEBAND VERSION - M8974A-1.0.25.0.17
CARRIER INFO -None
SERIAL NUMBER - []
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
Click to expand...
Click to collapse
I had the same exact problem... Download Factory IMG file and re-flash to stock. Re-install you're drivers

dia_naji said:
I had the same exact problem... Download Factory IMG file and re-flash to stock. Re-install you're drivers
Click to expand...
Click to collapse
Unzip the stock image and use fastboot to flash each part individually.

fastboot flash worked.
iPWNtehNOOB said:
Unzip the stock image and use fastboot to flash each part individually.
Click to expand...
Click to collapse
I downloaded hammerhead-krt16m-factory-bd9c39de.tgz (md5sum: 3a7b6cb66f8ec20edf661aee2d73d3a4) from hammerhead-krt16m-factory-bd9c39de.tgz, which I assume is the download site from developers dot google dot com images#hammerheadkrt16m.
When I tried to send the files with fastboot yesterday, it just hung.
I downloaded everything again this morning and got a different md5sum (36aa82ab2d7d05ee144d18546565cd5f) and instead of trying to manually fastboot the files over I executed the script
Code:
sudo ./flash-all.sh
sending 'bootloader' (2506 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
OKAY [ 0.471s]
finished. total time: 0.760s
rebooting into bootloader...
OKAY [ 0.136s]
finished. total time: 0.136s
sending 'radio' (42033 KB)...
OKAY [ 1.508s]
writing 'radio'...
OKAY [ 2.899s]
finished. total time: 4.407s
rebooting into bootloader...
OKAY [ 0.125s]
finished. total time: 0.125s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11d
Baseband Version.....: M8974A-1.0.25.0.17
Serial Number........: []
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8620 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.744s]
sending 'recovery' (9202 KB)...
OKAY [ 0.536s]
writing 'recovery'...
OKAY [ 0.778s]
erasing 'system'...
OKAY [ 1.323s]
sending 'system' (692940 KB)...
OKAY [ 21.913s]
writing 'system'...
OKAY [ 47.401s]
erasing 'userdata'...
OKAY [ 19.268s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
sending 'userdata' (139109 KB)...
writing 'userdata'...
OKAY [ 14.185s]
erasing 'cache'...
OKAY [ 0.669s]
formatting 'cache' partition...
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
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.907s]
rebooting...
finished. total time: 110.048s
I guess I had a corrupt download then. Thanks for the help.
Any idea why I could boot into Clockwork but CM just hung? Any additional things to try? Will CM boot without a SIM card?
On the plus side while messing around with trying to get this fixed, I stumbled on a way to get my new nvidia drivers working for the EVGA GTX650 I bought to power my twin 27" displays, so I guess that is also a plus!

same but now works
I just reinstalled recovery again and cm 11.

Problem with eMMC

Hello,
I have got a D820 16GB with CM13.
Yesterday it start to reboot constantly, today I solve it replacing the power buttom... But my problem was beginning. CM doesn't boot, it loop in the CM logo.
I entered in recovery to wipe everything but it fail with two partitions, persist and data.
I assumed the lost of my data, but I want my phone again!!!
I started with this tutorial:
http://forum.xda-developers.com/goo...o-repairing-corrupted-data-partition-t2577447
Not luck...
I can't enter in download mode (vol + and conect usb cable), but I entered in other similar mode, vol + vol - and power, the I tryed with this:
http://forum.xda-developers.com/goo...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
Is finished but nothing change. Obviusly I can't use LG flashtool...
If I try to flash factory image I get this:
Code:
[email protected]:/home/juan/hammerhead-mmb29k# ./flash-all.sh
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.309s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.510s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.625s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.849s
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.050s
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.26
Serial Number........: xxxxxxxxxxxxxxxx
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
FAILED
Device version-baseband is 'M8974A-2.0.50.2.26'.
Update requires 'M8974A-2.0.50.2.28'.
finished. total time: 0.691s
The latest test to was write zeros in both partition but don't work.
I guess is the eMMC broken, but I really like my Nexus 5!!!! I would,t buy another phone :crying:
Ideas?
Thanks!

If the memory is damaged, try and buy a cheap Nexus 5 with a smashed screen. I did this for two different phones with bad emmc.

audit13 said:
If the memory is damaged, try and buy a cheap Nexus 5 with a smashed screen. I did this for two different phones with bad emmc.
Click to expand...
Click to collapse
I purchased a new SDIN8DE4-16G, I will replace it!

Not able to access Recovery Mode menu

Some time ago the power button of my Nexus5 was stucking once in a while, and kept rebooting.
So I bought a new power button and asked an assistance center to replace it.
This apparently resolved the power button issue, since it does not reboot anymore.
BUT, when i power on my Nexus5 it doesn't goes over the animation of the google logo (the colored one).
It keeps showing the moving dots animation looping forever.
I would like to try to do a soft or hard reset but I can't reach the recovery mode menu.
I can enter the bootloader, then I select the "Recovery mode" and press the power button.
After that it shows the screen with the robot, the exclamation mark and the "No command" message.
From this screen I've tried to press the Volume Up once with Power Button, but it does nothing; it just reboot.
Actually from this screen, even without doing anything, after a few second it automatically reboot without showing the Wipe/Reset menu.
Then i've tried to unlock the bootloader (in order to flash the google stock rom), but I'm not able to get it unlocked permanently:
After running "fastboot oem unlock" on the phone it actually tells the phone is unlocked, but a soon as I let it Power on or Reboot, the phone get back to the locked state.
Indeed, if I unlock the bootloader and, without rebooting it, I try to flash the google nexus 5 factory image (command "sh flash-all.sh"), I get the output I'm copying further down.
Anyone knows how to handle this issue?
------------------------------------------------------------------------------------
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$ bash flash-all
bash: flash-all: No such file or directory
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$ sh flash-all.sh
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.307s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.507s
rebooting into bootloader...
OKAY [ 0.099s]
finished. total time: 0.099s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.608s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.708s
rebooting into bootloader...
OKAY [ 0.055s]
finished. total time: 0.055s
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: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 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.27
Serial Number........: 039e4cbc2518d798
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
FAILED
Device version-baseband is 'M8974A-2.0.50.2.27'.
Update requires 'M8974A-2.0.50.2.28'.
finished. total time: 0.600s
You have new mail in /var/mail/marcello
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$

Since the bootloader is relocking itself at reboot, the emmc chip is defective and the problem cannot be resolved with software. This will require a motherboard swap.

gufo84 said:
Some time ago the power button of my Nexus5 was stucking once in a while, and kept rebooting.
So I bought a new power button and asked an assistance center to replace it.
This apparently resolved the power button issue, since it does not reboot anymore.
BUT, when i power on my Nexus5 it doesn't goes over the animation of the google logo (the colored one).
It keeps showing the moving dots animation looping forever.
I would like to try to do a soft or hard reset but I can't reach the recovery mode menu.
I can enter the bootloader, then I select the "Recovery mode" and press the power button.
After that it shows the screen with the robot, the exclamation mark and the "No command" message.
From this screen I've tried to press the Volume Up once with Power Button, but it does nothing; it just reboot.
Actually from this screen, even without doing anything, after a few second it automatically reboot without showing the Wipe/Reset menu.
Then i've tried to unlock the bootloader (in order to flash the google stock rom), but I'm not able to get it unlocked permanently:
After running "fastboot oem unlock" on the phone it actually tells the phone is unlocked, but a soon as I let it Power on or Reboot, the phone get back to the locked state.
Indeed, if I unlock the bootloader and, without rebooting it, I try to flash the google nexus 5 factory image (command "sh flash-all.sh"), I get the output I'm copying further down.
Anyone knows how to handle this issue?
------------------------------------------------------------------------------------
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$ bash flash-all
bash: flash-all: No such file or directory
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$ sh flash-all.sh
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.307s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.507s
rebooting into bootloader...
OKAY [ 0.099s]
finished. total time: 0.099s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.608s]
writing 'radio'...
FAILED (remote: not supported in locked device)
finished. total time: 1.708s
rebooting into bootloader...
OKAY [ 0.055s]
finished. total time: 0.055s
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: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 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.27
Serial Number........: 039e4cbc2518d798
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
FAILED
Device version-baseband is 'M8974A-2.0.50.2.27'.
Update requires 'M8974A-2.0.50.2.28'.
finished. total time: 0.600s
You have new mail in /var/mail/marcello
MacBook-Pro-di-Marcello-2:hammerhead-mmb29s marcello$
Click to expand...
Click to collapse
I have a motherboard for sale, all u nerd to do is swap it out, did the device work at all when u got it back from the shop, maybe they didn't remove the battery and shorted ur emmc chip out, anyway, u can pm me if you wanna talk about the motherboard, its from my old device, works fine, only about 5mths of useage on it
Sent from my XT1526 using Tapatalk

PC?
Have you tried to access the bootloader menu through pc?like cmd?

Hi siddu,
you mean from a pc instead of a mac?
what command would you run?

I am having the same problem and my phone freezes at the animation dots then reboot back to GOOGLE logo. Is it really motherboard problem? Every time I reboot the phone, it will be locked again even though I have OEM unlocked it previously. My recovery mode is the same as you where there's a dead robot with exclamation mark in a triangle. I tried pressing volume up button with power button many times but it doesn't show the menu and after a while it will automatically reboot again. Anyone please help meee!!!

If the bootloader relocks itself after a reboot, the motherboard needs to be replaced.

NVidia K1: flashboot fails on InvalidSize error when flashing 'system'

Hi, Following the recent problems with battery life and the latest version of android for NVidia K1 tablets, a friend of mine tried to restore the stock image. Sadly, we're encountering some issue with fastboot, and I haven't been able to find anything on internet that could explain what is happening.
Following the instructions from (hxxp://nvidiashieldzone.com/index.php/shield-tablet/shield-tablet-k1/shield-tablet-restore-to-stock-recovery) we are stuck when flashing the system.img:
Code:
$ fastboot flash system system.img
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.549s]
sending sparse 'system' (545106 KB)...
OKAY [ 21.143s]
writing 'system'...
OKAY [ 19.928s]
sending sparse 'system' (552714 KB)...
OKAY [ 21.482s]
writing 'system'...
OKAY [ 20.861s]
sending sparse 'system' (118407 KB)...
OKAY [ 4.622s]
writing 'system'...
FAILED (remote: (InvalidSize))
finished. total time: 93.270s
When doing a 'fastboot erase system', we don't have any issue:
Code:
fastboot erase system -w
Creating filesystem with parameters:
Size: 13176406016
Block size: 4096
Blocks per group: 32768
Inodes per group: 8128
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 3216896
Block groups: 99
Reserved block group size: 791
Created filesystem with 11/804672 inodes and 91191/3216896 blocks
Creating filesystem with parameters:
Size: 1073741824
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 4096
Label:
Blocks: 262144
Block groups: 8
Reserved block group size: 63
Created filesystem with 11/65536 inodes and 8536/262144 blocks
******** Did you mean to fastboot format this partition?
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.252s]
erasing 'userdata'...
OKAY [ 1.720s]
sending 'userdata' (137154 KB)...
OKAY [ 5.025s]
writing 'userdata'...
OKAY [ 4.666s]
erasing 'cache'...
OKAY [ 0.208s]
sending 'cache' (18800 KB)...
OKAY [ 0.696s]
writing 'cache'...
OKAY [ 0.710s]
finished. total time: 13.278s
Note that when doing 'fastboot format system', it seems to be returning something a little different (bigger partition, more nodes?), and I don't know if this is expected:
Code:
$ fastboot format system
Creating filesystem with parameters:
Size: 1342177280
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 5120
Label:
Blocks: 327680
Block groups: 10
Reserved block group size: 79
Created filesystem with 11/81920 inodes and 10749/327680 blocks
target reported max download size of 570425344 bytes
erasing 'system'...
OKAY [ 0.204s]
sending 'system' (22984 KB)...
OKAY [ 0.847s]
writing 'system'...
OKAY [ 0.873s]
finished. total time: 1.924s
I did check that the image had the proper md5, so I'm really stuck at why it doesn't work. The stock image is the same one as on (hxxps://developer.nvidia.com/shield-open-source#tablet-k1)
Interestingly (or worryingly), if I try to erase system too many times in a row, the command will fail with TimeOut, but restarting the tablet fixes it everytime, and I'm able to erase / format / write again, until I get the InvalidSize error.
The tablet is currently stuck on the NVidia logo startup screen (although we can get the bootloader to start everytime).
Do you have any idea what could be happening?
Thanks!
-- tanyiachaos

I'm having this same 'InvalidSize' problem with every recovery image I can lay my hands on, including the original factory full image. The error happens equally using fastboot for Ununtu 16.04 and Windows 10.
Device: Nvidia Shield K1
Has anybody seen this 'InvalidSize' error before? If it didn't work for most people I would say there is a bug in fastboot calculating the last data chunk size. Could this be a hardware problem?

Hi I had the same issue with my shield tablet K1. I finally got my tablet working again by flashing the last TWRP and installing lineage os 14.1.
I can't post the link as i am a newbie but you can google : "How to install LineageOS on the Nvidia Shield Tablet ".
Hope that can help someone.