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.
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
Okay so I seem to be bricked in some way. I've tried fastboot flash a couple times using OEM images "MZ600-HRI39" I have the MZ600 so that should be correct. Attached is my log of what I did, I eventually tried erasing each partition and rebooting to see if that changes anything, theoretically I thought I should be stuck since everything should be erased. However, I still get the Encryption Unsuccessful screen. Went back to recovery and tried wipe/user data and cache get BP fail with user data wipe and tried e: dev a few times before it stops. Then reboot and same. Any help or suggestions would be great. Thanks in advance.
P.S. I just want to get a stock IMG in so I can OTA to current; trying to keep stock so I can exchange at BB for newer tablet.
I just kept the log short only showing I erased each partition, but pretty much same result with flashes. All performed and got OKAY.
I think I got it. So you erased all the partitions... No problems when erasing data and cache, but the worst error you did was erasing "boot" and "recovery", so what I recommend you to do is:
1 - (easier way) download LordAIOTool for LINUX! (Windows is outdated...) and use Stock Install tool
2 - (harder way) follow this guide:
- Open cmd
- Plug your Xoom on fastboot
- go to Stock Files folder
- type fastboot flash (not sure if it's flash or install, anyway, I think it's flash ) boot boot.img (if downloaded from Motorola)
- type fastboot flash system system.img
- type fastboot continue
- Pray lol
Now all I wish to you is Good Luck
Sent from my 3g JB Xoom - By the 1st Xoom RC
XxLordxX said:
I think I got it. So you erased all the partitions... No problems when erasing data and cache, but the worst error you did was erasing "boot" and "recovery", so what I recommend you to do is:
1 - (easier way) download LordAIOTool for LINUX! (Windows is outdated...) and use Stock Install tool
2 - (harder way) follow this guide:
- Open cmd
- Plug your Xoom on fastboot
- go to Stock Files folder
- type fastboot flash (not sure if it's flash or install, anyway, I think it's flash ) boot boot.img (if downloaded from Motorola)
- type fastboot flash system system.img
- type fastboot continue
- Pray lol
Now all I wish to you is Good Luck
Sent from my 3g JB Xoom - By the 1st Xoom RC
Click to expand...
Click to collapse
Okay I used CMD since I have more experience with DOS than Linux:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\>fastboot devices
161c10c9434122d7 fastboot
C:\>fastboot flash boot boot.img
sending 'boot' (8192 KB)...
OKAY [ 0.731s]
writing 'boot'...
OKAY [ 0.587s]
finished. total time: 1.323s
C:\>fastboot flash system system.img
sending 'system' (262144 KB)...
OKAY [ 19.190s]
writing 'system'...
OKAY [ 6.427s]
finished. total time: 25.621s
C:\>fastboot continue
resuming boot...
FAILED (remote: (00120000))
finished. total time: 0.126s
C:\>fastboot continue
resuming boot...
FAILED (remote: (00120000))
finished. total time: 0.120s
C:\>fastboot reboot
rebooting...
finished. total time: 0.117s
***I still get to Encryption Unsuccessful screen.....my thing is I don't even feel like it's flashing over anything, but not sure if that's possible. Almost like some write protection to the partitions.
Any other suggestions or does anyone need a paper weight?
not sure if this means anything either or gives a better ideal of the state of the device, but when I try wipes i get.."E:format_volume: make_extf4fs failed on /dev/block/platform/sdhci-tegra.3/by-name/cache" yet it states cache wipe complete. Then a bunch of failed to mount and can't open.
Try reflashing a custom recovery and with it try formating everything... Then try again everything from my other post again good luck
Sent from my 3g JB Xoom - By the 1st Xoom RC
I've tried custom recovery, via fastboot flash recovery "recovery".img with no luck. It doesn't stick. Do you have any experience with RSD?
g14life said:
I've tried custom recovery, via fastboot flash recovery "recovery".img with no luck. It doesn't stick. Do you have any experience with RSD?
Click to expand...
Click to collapse
What do you mean with It doesn't stick?
Can you get into the recovery menu?
You could also do a oem lock and oem ulock again.
Then reflash everything again (boot, system, recovery if needed).
I go to flash with fastboot and when I try to access via power button, then volume down button I just back to OEM recovery. Was thinking if I try to rebuild system from bottom up that should clear everything out (bootloader, then IMG files). Was wondering if RSD would do that?
just noticed this in recovery when I perform wipe cache partition I get this message "E: format_volume: make_extf4fs failed on /dev/block/platform/sdhci-tegra.3/by-name/cache cache wipe complete".
So frustrated right now.....REALLY appreciate all the help!
Lord do you know how to enable USB debugging from fastboot, RSD, or OEM recovery? Found a forum mentioning a lock if OTA updates performed.
http://www.arvydas.co.uk/2012/05/installing-android-4-0-3-ice-cream-sandwich-ics-on-motorola-xoom/
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
Hi all
I finally received my Nexus 5 back from LG, which said that they replaced the battery and other parts to address my issue (the original thread can be found at the link below).
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-various-issues-t3212261
This being said, I now want to flash Android 6.0 on my Nexus 5 and start fresh. This is the tutorial that I'm following, and that I followed when flashing Android 6.0 on my Nexus 5 prior to sending it to LG.
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
However it looks like it's not working anymore. On Step 8, the fastboot erase boot command returns me the following:
Code:
c:\adb>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
Anyone knows what that means? I used the ADB Installer 1.3, like I did back then, and even reinstalled it just in case, but to no avail.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
If anyone knows what's happening and can assist me, I would be really grateful! If you need more information, let me know.
Thank you!
Aura. said:
Hi all
I finally received my Nexus 5 back from LG, which said that they replaced the battery and other parts to address my issue (the original thread can be found at the link below).
http://forum.xda-developers.com/google-nexus-5/help/nexus-5-various-issues-t3212261
This being said, I now want to flash Android 6.0 on my Nexus 5 and start fresh. This is the tutorial that I'm following, and that I followed when flashing Android 6.0 on my Nexus 5 prior to sending it to LG.
http://androidforums.com/threads/guide-how-to-flash-a-nexus-factory-image-manually.706533/
However it looks like it's not working anymore. On Step 8, the fastboot erase boot command returns me the following:
Code:
c:\adb>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: -0.000s
Anyone knows what that means? I used the ADB Installer 1.3, like I did back then, and even reinstalled it just in case, but to no avail.
http://forum.xda-developers.com/showthread.php?p=48915118#post48915118
If anyone knows what's happening and can assist me, I would be really grateful! If you need more information, let me know.
Thank you!
Click to expand...
Click to collapse
Is your bootloader unlock? That is the first thing that comes to mind when ADB fails to write.
Sent from my SAMSUNG-SM-N910A using Tapatalk
It is, here's the output of the fastboot oem unlock command.
Code:
c:\adb>fastboot oem unlock
...
FAILED (remote: Already Unlocked)
finished. total time: 0.002s
Also I can see on my phone LOCK STATE - unlocked
Alright so I restarted my phone in fastboot mode, and the command went through. Weird, now I'm at the step where I need to flash system, recovery, boot, cache, etc. manually, but I keep on getting this message:
Code:
c:\adb>fastboot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 0.578s]
sending 'system' (1019257 KB)...
FAILED (command write failed (Too many links))
finished. total time: 0.625s
Restarted multiple times, also changed USB port (from USB 3.0 to USB 2.0) but the error persists. Any ideas?
Issue most likely solved. Changed my USB cable for a 2.0 one (I was using the 3.0 that came with the Nexus 5, but it started to be a bit loose), plugged it in a USB 2.0 port, and all the commands went through successfully. If I see that my Nexus behaves weirdly, I'll fastboot it again using the same setup to make sure that everything goes through properly.
This being said, issue solved, you can close this thread if you wish
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