For some reason my Nexus 5 suddenly stopped working. There was no trauma, it hasn't been dropped or anything, the screen just stopped working one day. The screen was already a replacement screen from when I did drop it about a year ago, and it had a bad bleed problem at the bottom of the screen so I didn't mind so much replacing it. While I was at it I also got a new USB charging port/dock connector, as the USB was beginning to be a bit dodgy, and a new battery as I was having it open anyway.
I'm no stranger to replacing parts in phones, laptops and other electronic equipment, and don't generally mess up, but this time, after having replaced all the bits, I'm no further. I've already taken everything apart several times and tried the old parts in all sorts of combinations. I'm sure all the connectors are clicked in good and none missing, but still nothing. When I hit power it gives a short buzz, and the screen gets very slightly lit up, so slightly it's hard to see, but by holding the phone at an angle it can be seen clearly. Nothing else on the screen, no text, graphics, animation, anything. I've also tried all sorts of combinations of up/down/power, also no cigar.
If I boot it in recovery (down+power), connect it to my pc, and do an adb devices it comes up blank. If I do an fastboot devices it comes up with what appears to be the right line.
H:\owncloud\Software\adb-tools>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
H:\owncloud\Software\adb-tools>fastboot devices
02b58059d0217f13 fastboot
Why the difference? The fact that it comes up with anything at all kinda suggest to me that the mainboard probably is ok, no? So in that case, what's left to try/replace?
I was thinking perhaps the boot partition somehow got corrupted, so I thought I'd try loading a fresh boot partition, but that throws an error:
H:\owncloud\Software\adb-tools>fastboot flash bootloader bootloader-hammerhead-hhz12h.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (3119 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.073s
So again at a dead end.
Any ideas?
Also tried a reflash of the latest stock, but still no cigar...
H:\owncloud\Software\adb-tools>fastboot -w update image-hammerhead-lmy48m.zip
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
Cannot read image.
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...: HHZ12h
Baseband Version.....: M8974A-2.0.50.2.26
Serial Number........: 02b58059d0217f13
--------------------------------------------
checking product...
OKAY [ 0.113s]
checking version-bootloader...
OKAY [ 0.098s]
checking version-baseband...
OKAY [ 0.098s]
sending 'boot' (8916 KB)...
FAILED (data transfer failure (Unknown error))
finished. total time: 0.758s
No suggestions?
Related
Got this error while flashing Android Lollipop final factory image that released hours ago.
Help please!
OKAY [ 30.945s]
writing 'system'...
OKAY [ 66.316s]
erasing 'userdata'...
OKAY [ 12.928s]
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
malloc: Not enough space
Cannot generate image.
FAILED ()
finished. total time: 116.020s
Press any key to exit...
HeyIamSmiley said:
Got this error while flashing Android Lollipop final factory image that released hours ago.
Help please!
OKAY [ 30.945s]
writing 'system'...
OKAY [ 66.316s]
erasing 'userdata'...
OKAY [ 12.928s]
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
malloc: Not enough space
Cannot generate image.
FAILED ()
finished. total time: 116.020s
Press any key to exit...
Click to expand...
Click to collapse
What method are you using to flash the stock image? Seen lots of different methods, but what worked for me was easy .. Nexus Root Toolkit. Looked like it hung for 5 minutes during install, then everything went smoothly. No issues. Give that a try?
Hi,
first: Wrong section
second: did you try the Work-around (flash file for file)
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!
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.
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.
Trying to flash stock, because of the boot loop.
Terminal log shown below
target reported max download size of 1073741824 bytes
sending 'bootloader' (3124 KB)...
OKAY [ 0.306s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.508s
rebooting into bootloader...
OKAY [ 0.127s]
finished. total time: 0.128s
target reported max download size of 1073741824 bytes
sending 'radio' (45489 KB)...
OKAY [ 1.616s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.841s
rebooting into bootloader...
OKAY [ 0.121s]
finished. total time: 0.121s
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
Cannot read image.
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........: 0b1323fd02b659ea
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
FAILED
Device version-bootloader is 'HHZ12k'.
Update requires 'HHZ20h'.
finished. total time: 0.577s
Press any key to exit...
Device has an unlocked bootloader? Tried flashing the oldest stock Google ROM for the phone?