Hi all,
I just got my brand new LG N5 (hammerhead d820(h) 32gb HHZ11K)... and after a week of using it i was sending a chat to a friend and the screen shoock a little then the whole machine froze. I had to reboot, but when I did, it froze when the colored balls appeared. After many attempts I decided to just reflash the whole thing with the hammerhead-kot49h factory image.
But when I do that, it never succeeds
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.288s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.475s
fastboot flash radio radio-hammerhead-m8974a-1.0.25.0.23.img
sending 'radio' (42049 KB)...
OKAY [ 1.505s]
writing 'radio'...
OKAY [ 2.849s]
finished. total time: 4.355s
and to just test, i tried
fastboot flash boot boot.img (succeeds)
fastboot flash recovery recovery.img (succeeds)
fastboot flash system system.img (fails - device freezes on 'erasing...'))
fastboot flash userdata userdata.img (succeeds)
fastboot flash cache cache.img (fails - device freezes on 'erasing...')
I read somewhere that it is best to use the manufacturers tools, so I downloaded the LG Nexus Root Kit, but that was a mess.. still trying)
To me it seems like the internal memory just blew up!
so, my questions are:
Is this bricked?
Can i reformat and somehow mark bad section of memory off limits? like e2fsck/mkfs does?
Can i replace the internal memory myself somehow? (I live in Argentina, and to get this RMA'd, fixed and returned will take many many months and cost $$$ in import fees, assuming it doesn't get 'lost' in customs, like half my stuff)?
Any ideas?
It seems rather bizarre that a brand new N5 justs bricks itself for no reason... but, here I am.
Thanks for any advice
Related
Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?
romka7 said:
Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?
Click to expand...
Click to collapse
If I remember right, it's actually EXT4 and android uses FUSE to make it look like a FAT32 partition to a connected machine.
I would have suggested RUU, but it seems like that's not an option for you. Good luck with your phone, man.
If worst comes to worst just go to att and say it broke randomly, I don't think they can tell it's rooted if you messed it up that badly
Sent from my One X using xda premium
Did you try just running the RUU ?
Ok, I beat it to death.... got it working. Somewhere in my trial and error process I ended up flashing to CWM recovery, which did nothing new for me, then I pushed TWRP again but the 2.1.8, was on 2.2 when the problem started.... all of the sudden ADB started working, not sure what happened on the newer version. I still did not see my SDcard, but I was able to push a version of cleanrom to the system partition. The install did not go, but the the process it formated the sdcard to the proper format.... or it restored some setting. I was then able to mount SD in TWRP and installed newest version of CleanRom.. All good now.... its all a learning process I guess
my nexus 5 is almost dead. not pass the logo of the bootloader. I have tried to install custom rom, stock rom, factory reset, but the device does not allow it shows an error so disk write.
C: \>
C: \> fastboot flash boot C :/ nexus / boot.img
sending 'boot' (8700 KB) ...
OKAY [0.481s]
writing 'boot' ...
FAILED (remote: flash write failure)
finished. Total time: 0.664s
C: \>
******************************************
--------------------------------------------
Bootloader Version ...: HHZ11k
Baseband Version .....: M8974A-2.0.50.1.13
Serial Number ........: 04b5a293438497a3
--------------------------------------------
checking product ...
OKAY [0.101s]
checking version-bootloader ...
OKAY [0.097s]
checking version-baseband ...
OKAY [0.097s]
sending 'boot' (8700 KB) ...
OKAY [0.488s]
writing 'boot' ...
OKAY [0.730s]
sending 'recovery' (9284 KB) ...
OKAY [0.546s]
writing 'recovery' ...
FAILED (remote: flash write failure)
finished. Total time: 2.649s
************************************************** *********
sending 'recovery' (13586 KB) ...
OKAY [0.542s]
writing 'recovery' ...
FAILED (remote: flash write failure)
finished. Total time: 0.727s
Have TWRP installed but do not allow any action from this. team allowed to enter boot mode and download mode, but when entering TWRP does not allow any action or file copy .. A technician has reviewed and tells me that the memory can be corrupted uyno allows rewrite.
and try some of the usual methods for restauralr but nothing has worked.
any suggestions to recover and repair my nexus 5.??
please your help urgent
arroyave76 said:
-
Click to expand...
Click to collapse
Try relocking your bootloader with fastboot oem lock, then reboot into bootloader again. If the lock state doesn't stick goes back to being unlocked after the reboot then it might be bad eMMC and you'll have to RMA your device. If it does stay locked afterwards, try using LG Flashtool: http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
My Nexus 5 is dying
Lethargy said:
Try relocking your bootloader with fastboot oem lock, then reboot into bootloader again. If the lock state doesn't stick goes back to being unlocked after the reboot then it might be bad eMMC and you'll have to RMA your device. If it does stay locked afterwards, try using LG Flashtool: http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Click to expand...
Click to collapse
does google will receive the device even when I rooteed and changed the sw?
arroyave76 said:
does google will receive the device even when I rooteed and changed the sw?
Click to expand...
Click to collapse
If you bought it from the Play Store from Google they don't care if you unlocked the bootloader or have a custom ROM or whatever. As long as it's a real manufacturing defect. If you bought it elsewhere you'll have to go straight to LG and they'll probably charge you or maybe even refuse.
What was the result of trying to relock the bootloader?
arroyave76 said:
does google will receive the device even when I rooteed and changed the sw?
Click to expand...
Click to collapse
Google does not care about root or custom rom.
Can you please reboot to fastboot and post the "VARIANT" line here. Thanks.
@Lethargy you have asked why there are two type of memory brand. I think this is how google managed to rise the production of nexus 5 to avoid that all nexus 5s are being sold on the first day and there will be no more until next month like what happend with nexus 4.
bitdomo said:
@Lethargy you have asked why there are two type of memory brand. I think this is how google managed to rise the production of nexus 5 to avoid that all nexus 5s are being sold on the first day and there will be no more until next month like what happend with nexus 4.
Click to expand...
Click to collapse
Ah, that would make sense then :good:
Hello everyone,
today I had very unpleasant surprise with my nexus 5. Let me tell the whole story from the beginning.
At first, I've never played with my nexus in any way (custom roms, root, etc.), it's all default from the beginning.
Few days ago I upgraded to 5.1 using android default upgrader. Next day I did a factory reset (from the settings menu) and then I encrypted the device. Since the flow of turning on the encrypted Android sucks, I did the factory reset again. Then I installed all the apps etc. and I was happily using the phone for 2 days until today's evening. I plugged my nexus into charging, it had 5% battery and was turned on. An hour or two later, I've noticed that the phone restarted and stucked on "Google" screen.
I tried booting several times. Then I googled how to boot into recovery mode. I hold volume and power buttons for a while, from the screen I chose "Recovery mode" and hit the power button again. Unfortunately I am getting the black screen...
Please, help me to make it working again, I found a lot of Google screen loop problems on the web as well as black screen recovery mode but happening not together and not with stock android.
I would like to have stock 5.1 back, possibly to backup some data before erasing.
Thanks,
alatar
alatar- said:
Hello everyone,
today I had very unpleasant surprise with my nexus 5. Let me tell the whole story from the beginning.
At first, I've never played with my nexus in any way (custom roms, root, etc.), it's all default from the beginning.
Few days ago I upgraded to 5.1 using android default upgrader. Next day I did a factory reset (from the settings menu) and then I encrypted the device. Since the flow of turning on the encrypted Android sucks, I did the factory reset again. Then I installed all the apps etc. and I was happily using the phone for 2 days until today's evening. I plugged my nexus into charging, it had 5% battery and was turned on. An hour or two later, I've noticed that the phone restarted and stucked on "Google" screen.
I tried booting several times. Then I googled how to boot into recovery mode. I hold volume and power buttons for a while, from the screen I chose "Recovery mode" and hit the power button again. Unfortunately I am getting the black screen...
Please, help me to make it working again, I found a lot of Google screen loop problems on the web as well as black screen recovery mode but happening not together and not with stock android.
I would like to have stock 5.1 back, possibly to backup some data before erasing.
Thanks,
alatar
Click to expand...
Click to collapse
Well you have two options:
Reflash stock rom with fastboot http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
Or
Reflash stock rom with LG flashtool http://forum.xda-developers.com/goo...orial-how-to-flash-factory-images-lg-t2713833
Both method will wipe your phone.
Use fastboot to reflash stock rom, but you may need to wipe data too. I've had this randomly happen before, luckily for me tho I had twrp and a backup, but even after re-installing the rom it'd still not load, i assume data had just got corrupted somehow unluckily, wiped data and all was fine and has been ever since
Sent via tapatalk from my cataclysm'd Lollipooop Nexus 5
Thank you @bitdomo and @Ben36.
So I tried reflashing with fastboot. I connected n5 to my notebook (running Ubuntu 14.04) and I turned on the device into fastboot mode. I ended up with "FAILED (remote: flash write failure)".
Here is what I did:
Code:
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot devices
[I]XXXXXXXXXXXX[/I] fastboot
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot oem unlock
...
OKAY [ 48.373s]
finished. total time: 48.374s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.292s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.472s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.476s
I wanted to try with another cable and usb port but I didn't manage n5 to be recognized in fastboot lately (fastboot devices list is empty, lsusb is blind as well). I did a lot of attempts both on linux and windows 8 but it worked only twice on linux.
I will try again later. Perhaps you have some advise for this problem?
PS What is strange, after few minutes I plug n5 intro charging , it starts booting by itself... What the hell?
PS2 The phone keeps restarting whole the time... The battery seemed empty so I was charging it. It starts charging, after a minute it starts booting and then after 3 minutes it goes off. All over again and again.
alatar- said:
Thank you @bitdomo and @Ben36.
So I tried reflashing with fastboot. I connected n5 to my notebook (running Ubuntu 14.04) and I turned on the device into fastboot mode. I ended up with "FAILED (remote: flash write failure)".
Here is what I did:
Code:
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot devices
[I]XXXXXXXXXXXX[/I] fastboot
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot oem unlock
...
OKAY [ 48.373s]
finished. total time: 48.374s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.292s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.472s
/opt/eclipse-adt/sdk/platform-tools$ sudo ./fastboot flash bootloader bootloader-hammerhead-hhz12f.img
sending 'bootloader' (2579 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.476s
I wanted to try with another cable and usb port but I didn't manage n5 to be recognized in fastboot lately (fastboot devices list is empty, lsusb is blind as well). I did a lot of attempts both on linux and windows 8 but it worked only twice on linux.
I will try again later. Perhaps you have some advise for this problem?
PS What is strange, after few minutes I plug n5 intro charging , it starts booting by itself... What the hell?
Click to expand...
Click to collapse
That error message you get means that the emmc of the phone is fauilty.
Do you have warranty?
bitdomo said:
That error message you get means that the emmc of the phone is fauilty.
Do you have warranty?
Click to expand...
Click to collapse
Yes, I do. I have the phone just since few months. Are you sure about that? Cannot it be a failure of my usb port or poor cable quality?
alatar- said:
Yes, I do. I have the phone just since few months. Are you sure about that? Cannot it be a failure of my usb port or poor cable quality?
Click to expand...
Click to collapse
I am sure about that, there plenty of other people having the same problem. Only solution is to buy a new motherboard.
Hi. I can't get passed the google splash screen on a Nexus 5 D821 and could use some help.
Here are the facts:
* The owner of the device told me it bricked after an update.
* The Bootloader is unlocked. When i tried to lock i got the following message:
Code:
fastboot oem lock
...
OKAY [ 0.041s]
finished. total time: 0.041s
But it wasnt persistent. When given reboot comand the phone switched OFF instead. I turned it on to bootloader again and it was still unlocked.
* I tried flashing stock rom LRX22c manually after a failed attempt with the flash-all script. I got the following error for bootloader, radio, boot and recovery:
Code:
FAILED (remote: flash write failure)
* I tried erasing cache and flashing userdata but the after over 60 minutes waiting i came to the conclusion that i wasnt going anywhere and just rebooted the phone.
*The only thing im actually able to flash without an error message is system.img:
Code:
fastboot flash system ~/Downloads/hammerhead-lrx22c/image-hammerhead-lrx22c/system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.127s]
sending 'system' (981472 KB)...
OKAY [ 30.934s]
writing 'system'...
OKAY [ 62.705s]
finished. total time: 93.767s
* I tried booting TWRP, but i was unable to mount the file system (perhaps because i wasnt able to flash it. i used "fastboot boot twrp.img").
Are phones technically able to get to splash screen or bootloader with a damaged NAND or EEMC chip? Im starting to consider the possibility of a hardbrick. Why would i be able to write system.img if that was the case though? Any help is welcome
===============================================
alright so im pretty sure its a hard brick. The emmc is dead. its a shame :/ guess ill just try to sell it for parts. I would delete this thread because its pretty useless, but i have created my account a few days ago, and i ddont know how to.
You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk
Ben36 said:
You've only flashed the system img?
Do all the img's one by one. Recovery, boot, system, radio, userdata. Then fastboot reboot
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I have tried all of the imgs in their respective order. they all failed. i got the error
Code:
FAILED (remote: flash write failure)
. system.img was the only .img i was able to write, and i was wondering why. Also, when i try fastboot reboot the phone switches off. It doesnt reboot.
Hi everyone,
Long time Lurker, first time poster.
I have a D821 (Red Nexus 5) that appears to have eMMC issues, but I just need another opinion before I give up;
I have a bootloop and I can't remember how I got into it as I replaced this Nexus 5 with another Nexus 5 18months ago. The bootloop looks like the android-cogs-wiggly-antennae updating/installing screen.
Here's the current firmware stats:
PRODUCT_NAME - hammerhead
VARIANT - hammerhead D821(E) 32GB
HW VERSION - rev_11
BOOTLOADER VERSION - HHZ11k
BASEBANDVERSION - M8974A-2.0.50.2.30
CARRIER INFO - None (from Play Store, but missed RMA opportunity)
SERIAL NUMBER - 06e[XXX]85d[XXXX]917 -> maybe I shouldn't post this? I've ommited chars.
SIGNING - production
SECURE BOOT - enabled
LOCK STATE - unlocked
So, I try to use fastboot to reflash stock using the flashall batch file, and this is how it goes:
Code:
sending 'bootloader' (3124 KB)...
OKAY [ 0.226s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.394s
rebooting into bootloader...
OKAY [ 0.104s]
finished. total time: 0.104s
< waiting for device >
It then restarts into a different bootloop, where it restarts by showing the "Google" & the unlocked padlock a few times. It then turns off and shows the charging icon, indicating the device is off.
When I restart by holding Power + Volume down, I get further through the FlashAll.bat.
Code:
sending 'radio' (45489 KB)...
OKAY [ 1.612s]
writing 'radio'...
OKAY [ 3.123s]
finished. total time: 4.735s
rebooting into bootloader...
OKAY [ 0.122s]
finished. total time: 0.122s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
Okay. So, I'm not sure if this is consistent with internal memory failure.
Here's the capability of the phone right now:
I can flash radio, TWRP custom recovery & userdata.
I can erase bootloader & cache.
I can send almost anything through fastboot flash [whatever] [whatever.img].
But I can't erase system. I also can't write a system, boot or cache.
Lastly, I can boot into TWRP recovery 3.0.2-0 (and get recognized on adb), however I get a whole range of mounting issues.
For instance, I can't mount anything, "Internal Storage" shows (0MB), but using the ADVANCED->FILE MANAGER, I can view all the files still on the eMMC, including signs that my flashing has actually written to the system. When going into the WIPE-ADVANCED->REPAIR-OR-CHANGE-FILESYSTEM section, I can see SYSTEM uses 1009MB, with 50MB free. I can see cache uses 689MB. The Dalbik / ART cache & internal memory show "Invalid partition selection", and /data shows "0MB".
Also, when I "Reboot to Recovery", I get stuck in the bootloop.
Is this dead? Or do I just need to use fastboot in a particular way to get out of the deep, bricked trench of a bootloop? It's no longer even showing the Android updating bootloop.
On TWRP, go to Wipe -> Format Data. I got the problem fixed that way.
KAGE-008 said:
On TWRP, go to Wipe -> Format Data. I got the problem fixed that way.
Click to expand...
Click to collapse
Unfortunately, I can't wipe Data. It fails to mount /Data, and cannot wipe data.
The simplest solution IMHO is to find a used Nexus 5 with a smashed screen and working motherboard to perform a motherboard swap.
Have you tried dling again, could be a bad dl. Also, try flashing each partition in fastboot separately.
EXACTO
I have exaclty the same issue [email protected][email protected] hope you found a solution !
https://forum.xda-developers.com/go...-unbrick-nexus-5-stucked-qualcomm-hs-t3043301
if it still available .. but beware , pay attention to the instructions