Database Info

[Q] Unable to erase cache partition

Today I was facing a 4.4.3 issue so I've thought about doing a factory reset to see if this fixes it. So I've gone into Recovery and run a factory reset. Strangely this was taking so long, so after 2 hours I've decided to stop it. I know that stopping this process is not recommended, but I've considered it was getting out of the reasonable range. I've rerun it and same problem, so after 3 hours I've stopped it. And I've thought about restoring the factory image. Unfortunately the process get stuck in the "erasing cache" step:
Code:
# ./flash-all.sh
sending 'bootloader' (2508 KB)...
OKAY [ 0.296s]
writing 'bootloader'...
OKAY [ 0.452s]
finished. total time: 0.749s
rebooting into bootloader...
OKAY [ 0.131s]
finished. total time: 0.132s
sending 'radio' (45409 KB)...
OKAY [ 1.614s]
writing 'radio'...
OKAY [ 3.102s]
finished. total time: 4.716s
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...: HHZ11k
Baseband Version.....: M8974A-2.0.50.1.13
Serial Number........: 063b7fa3f0d88342
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8700 KB)...
OKAY [ 0.490s]
writing 'boot'...
OKAY [ 0.740s]
sending 'recovery' (9284 KB)...
OKAY [ 0.540s]
writing 'recovery'...
OKAY [ 0.776s]
erasing 'system'...
OKAY [ 1.074s]
sending 'system' (721400 KB)...
OKAY [ 23.132s]
writing 'system'...
OKAY [ 49.064s]
erasing 'userdata'...
OKAY [ 13.622s]
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 [ 13.895s]
erasing 'cache'...
I'm afraid that even if I let it work for hours it'll be stuck forever. What can I do? What could be happening? Any suggestions? Thank you!

Just fastboot flash the cache image manually without erasing it.
fastboot flash cache cache.img
Sent from my Nexus 5 using Tapatalk

Thank you, the command works well:
Code:
# fastboot flash cache image/cache.img
erasing 'cache'...
OKAY [ 0.513s]
sending 'cache' (13348 KB)...
OKAY [ 0.640s]
writing 'cache'...
OKAY [ 1.075s]
finished. total time: 2.228s
[email protected]:/home/jpabloae/Descargas/hammerhead-ktu84m# fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.000s
After that and following this tutorial for flashing the factory image (Method 2) I select "Recovery" and then press Power Button + Volume UP when the small Android appears. When I do that the small Android gets grey and it outputs "Formatting /data...", but it doesn't finish. I'm not sure what could be happening, any ideas?

What is your ultimate goal?
Sent from my Nexus 5 using Tapatalk

rootSU said:
What is your ultimate goal?
Click to expand...
Click to collapse
To boot a fresh stock 4.4.3.

To be unrooted forever?? What about bootloader?
Sent from my Nexus 5 using Tapatalk

rootSU said:
To be unrooted forever?? What about bootloader?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Well, as a first step I'd like to at least have the phone functional.
These are all the steps I've followed (the bootloader is unlocked):
Code:
fastboot flash bootloader bootloader-hammerhead-hhz11k.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-hammerhead-m8974a-2.0.50.1.13.img
fastboot reboot-bootloader
sleep 5
fastboot flash system image/system.img
fastboot flash userdata image/userdata.img
fastboot flash boot image/boot.img
fastboot flash recovery image/recovery.img
fastboot flash cache image/cache.img
And then what I said before: select "Recovery" and then press Power Button + Volume UP. And it get stuck on "Formatting /data...".

I don't know what the recovery is doing. Try and flash a custom recovery like philz or twrp. Then fast boot flash it
Then fastboot flash the system, boot, cache and userdata and then see what happens.. If it boots etc
By boot,, I mean kernel
Sent from my Nexus 5 using Tapatalk

I've been able to recover the phone back to stock with TWRP. You've been really helpful, thank you!
One last question: how does one manage to return to a stock image, stock recovery, locked and untampered device? Following these steps I'm able to do it all except for the recovery.

jpabloae said:
I've been able to recover the phone back to stock with TWRP. You've been really helpful, thank you!
One last question: how does one manage to return to a stock image, stock recovery, locked and untampered device? Following these steps I'm able to do it all except for the recovery.
Click to expand...
Click to collapse
Those steps are for someone who has returned to stock and forgotten to reset the tamper flag, so the recovery they are flashing is a custom one.
Full normal instructions are linked in my signature

rootSU said:
Full normal instructions are linked in my signature
Click to expand...
Click to collapse
I might be missing something, but on the signature's guide, in the last step (Locking your bootloader+ Resetting the tamper flag) it uses TWRP to install the zip file that resets the temper flag, and this process lockes the bootloader as well. I mean, after doing this you don't end up with the stock recovery but with TWRP.

jpabloae said:
I might be missing something, but on the signature's guide, in the last step (Locking your bootloader+ Resetting the tamper flag) it uses TWRP to install the zip file that resets the temper flag, and this process lockes the bootloader as well. I mean, after doing this you don't end up with the stock recovery but with TWRP.
Click to expand...
Click to collapse
In the steps he doesn't flash TWRP. He boots to it.
fastboot boot recovery.img
as opposed to
fastboot flash recovery recovery.img
That means you have stock recovery already installed at that point and you do not replace it.
There is also an app called BootUnlocker, which resets the taper flag from within android (With root) so you can just use that. I use that and mine is constantly showing as not tampered

rootSU said:
In the steps he doesn't flash TWRP. He boots to it.
Click to expand...
Click to collapse
You're absolutely right, I took it for granted it was necessary to flash it before using it. My phone is now 100% recovered, thank you so much!

jpabloae said:
You're absolutely right, I took it for granted it was necessary to flash it before using it. My phone is now 100% recovered, thank you so much!
Click to expand...
Click to collapse
No probs

[FIX] Downgrading from 4.4.4 bricked your phone? Possible fix here

So I don't have a procedure to fix it but the guys at #android on Freenode gave me a bunch of tips which eventually made my phone work. It loaded a custom rom (liquid smooth) and I can make calls.
Sorry if I can't give you a more precise solution... if someone can figure out the exact reason why I was able to install a custom rom properly, it would help us find a solution to fix the GPT.BIN error.
In a nutshell, I was getting errors when trying to install a custom rom via TWRP (bypassing the stock rom errors) but now I'm able to install a custom rom and run it fine. Please read the logs despite all the crap around it.
Here is the chat log... follow though and do what I did - the solution might be in some fastboot commands I tried:
[08:31] <Jonnyw2k> what does "fastboot oem unlock" say
[08:31] <asdfsdfsadf> (bootloader) Device already unlocked! FAILED (remote failure) finished. total time: 0.003s
[08:39] <asdfsdfsadf> writing 'partition'... Preflash validation failed FAILED (remote failure)
[08:39] <asdfsdfsadf> mfastboot
[08:40] <asdfsdfsadf> not sure what the error is.....
[08:40] <Khaytsus> Well that just looks vulgar at a glance
[08:42] <Jonnyw2k> asdfsdfsadf there is a "fastboot oem fb_mode_clear" command that apparently sometimes helps, but that seems to be more todo with a fastboot issue
[08:42] <asdfsdfsadf> ... OKAY [ 0.002s] finished. total time: 0.003s
[08:43] <asdfsdfsadf> same error when I flash gpt.bin
[08:43] <DrChandra> Perhaps the partition is damaged.
[08:43] <Jonnyw2k> try flashing the gpt now
[08:43] <Aevum> what phone is it ?
[08:43] <asdfsdfsadf> moto g xt1032
[08:44] <DrChandra> Consider the erase and format commands within fastboot
[08:45] <Aevum> motorola havehttp://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <asdfsdfsadf> just did -w
[08:45] <Aevum> motorola havehttp://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <Aevum> fdoijghfiodjhadt
[08:45] <Aevum> try this http://forum.xda-developers.com/showthread.php?t=2542219
[08:45] <asdfsdfsadf> formatting 'userdata' partition... Creating filesystem with parameters: Size: 6173884416 Block size: 4096 Blocks per group: 32768 Inodes per group: 8192 Inode size: 256 Journal blocks: 23551 Label: Blocks: 1507296 Block groups: 46 Reserved block group size: 367 Created filesystem with 11/376832 inodes and 50150/1507296 blocks sending 'userdata' (98165 KB)... writing 'userdata'... OKAY [ 9.953s] erasing 'cache'... OKAY [ 0.24
[08:46] <asdfsdfsadf> Aevum: tried that twice... to give you some insight, I upgraded to 4.4.4 GPE on a non-gpe device, many people got bricked when they tried to downgrade
[08:47] <asdfsdfsadf> After fastboot -w command, same error when trying to partition
[08:47] <Aevum> i dont know what flashing tools motorola uses, becuase theres usuayl the fastboot and ADB
[08:47] <Aevum> and also a proprietary tool from the manufacturer for bathc flashing
[08:48] <asdfsdfsadf> RSD Lite doesn't detect hte phone in fastboot
[08:49] <Aevum> theres usualy a fastboot and a flashing mode
[08:49] <DrChandra> RSD might be asking for a fastboot version and mismatching against whatever is being returned by the bootloader. It could e part of what Motorola uses to prevent anything but their own tool from being used.
[08:52] <Aevum> can you get ADB access ?
[08:52] <The0x539> y'know what
[08:52] <asdfsdfsadf> Aevum: yes ADB works
[08:52] <The0x539> I'll wait until I actually get it
[08:52] <DrChandra> I don't think he can boot, so he won't have adb
[08:53] <asdfsdfsadf> ADB works from stock and custom recovery
[08:53] <asdfsdfsadf> They both can get pushed files
[08:53] <asdfsdfsadf> But when it's time to install
[08:53] <asdfsdfsadf> they fail
[08:53] <DrChandra> asdf: So the main OS is what isn't booting?
[08:53] <asdfsdfsadf> Yes
[08:53] <asdfsdfsadf> But main os can't even get installed
[08:53] <DrChandra> Can you mount anything from recovery?
[08:53] <asdfsdfsadf> Anything I throw at it gives a partition error
[08:54] <asdfsdfsadf> Let me go to recovery and I'll give you the exact errors
[08:54] <Aevum> you are pre flashing the correct boot.img for every rom before, no ?
[08:54] <DrChandra> I wish fastboot could boot directly into recovery. I have to operate it from the screen to get there, or double boot.
[08:54] <asdfsdfsadf> Aevum: yes
[08:55] <Aevum> and the hboot versions coinside ?
[08:55] <DrChandra> Damaged flash memory
[08:55] <Jonnyw2k> you can "fastboot boot recovery.img"
[08:55] <asdfsdfsadf> Jonnyw2k: lfashes but nothing works after it finishes
[08:55] <Aevum> i would format the whole internal memory and start over with a stock image
[08:56] <DrChandra> Jonnyw2k: Yes, but you're not booting what's on the device, and transferring it takes forever.
[08:56] <Jonnyw2k> he's trying that its the partition table that is messed up but he cant flash a new one
[08:56] <asdfsdfsadf> >adb push Rom.zip /sdcard/
[08:56] <asdfsdfsadf> Let me transfer this
[08:56] <asdfsdfsadf> IT's a rom
[08:56] <asdfsdfsadf> And I'll give you the message in TWRP{
[08:56] <DrChandra> I use TWRP
[08:57] <asdfsdfsadf> TWRP works here... it just can't install ****
[08:57] <asdfsdfsadf> Let me get the message
[08:57] <asdfsdfsadf> 1 minute
[08:57] <Sloth514> how come i feel like this conversation should b in #android-root
[08:58] <DrChandra> Well, if the main OS partition (system) is messed up, you can't mount it, and/or you can't write it, so trying to get TWRP to install Rom.zip isn't going to work.
[08:58] <asdfsdfsadf> wow
[08:58] <asdfsdfsadf> mother****ers
[08:58] <asdfsdfsadf> rom booting :/
[08:58] <asdfsdfsadf> PC detecting phone during boot
[08:59] <DrChandra> ADB to main OS?
[08:59] <asdfsdfsadf> I adb'd liquidsmooth rom.zip
[08:59] <asdfsdfsadf> and ran it from TWRP
[08:59] <asdfsdfsadf> IT installed with no issue
[08:59] <asdfsdfsadf> Rebooted
[08:59] <DrChandra> Oh, ran it. YOu didn't install it.
[08:59] <asdfsdfsadf> Liquid smooth is now loading...
[09:00] <asdfsdfsadf> Still loading. I guess the first time is slow
[09:00] <Jonnyw2k> DrChandra he flashed the rom.zip from TWRP, and now is booting the rom
[09:00] <DrChandra> He didn't say he flashed it
[09:02] <DrChandra> asdfsdfsadf: Did you do an Install from TWRP, and select Rom.zip from the sdcard?
[09:02] <asdfsdfsadf> Yes DrChandra
[09:02] <asdfsdfsadf> After pushing it with ADB
[09:02] <DrChandra> OK, he flashed it
[09:02] <asdfsdfsadf> But I tried that before and got errors
[09:02] <asdfsdfsadf> Some command I typed in fastboot must have fixed it...
[09:03] <DrChandra> How is it that TWRP knows how to write the system partition and all the flash tools don't?
[09:03] <asdfsdfsadf> But right now the issue is that I'm stuck at the animated boot scren (never got this far)
[09:03] <asdfsdfsadf> normally it takes time, but not several minutes, right?
[09:03] <Jonnyw2k> you can try and reboot
[09:03] <Jonnyw2k> press and hold power till it turn off
[09:04] <Jonnyw2k> then turn it on again
[09:10] <DrChandra> Well, if the device is badly broken enough, even fastboot won't work.
[09:10] <Khaytsus> fastboot will _always_ work unless you somehow broke the bootloader
[09:10] <DrChandra> logcat is miles above that
[09:10] <asdfsdfsadf> fastboot works, it just won't flash gpt.bin... wait let me try that again now that liquidsmooth actually got flashed though TWRP
[09:10] <Khaytsus> logcat requires the system be at least in some normal condition, even if it's boot looping or something
[09:10] <Leeds> Khaytsus: it seems that - at least at one point - fastboot was working in the sense of responding, but not working because the partition table was so screwed that it couldn't read/write partitions
[09:11] <Khaytsus> Leeds: Heh. Interesting. I suppose if you break _partitions_, yeah....
[09:13] <Khaytsus> fastboot flash partition gpt.bin <-- looks like this is what you do
[09:13] <asdfsdfsadf> So: fastboot flash partition gpt.bin Gives me: writing 'partition'... (bootloader) Preflash validation failed FAILED (remote failure) finished. total time: 0.423s
[09:14] <asdfsdfsadf> Which is the original error
[09:14] <DrChandra> I've never seen fastboot write to "partition" before. It's always "system", "boot", "userdata", or "cache"
[09:15] <asdfsdfsadf> The only difference between now and then is that the rom actually boots but just stays stuck on the animation screen
[09:15] <Khaytsus> That error means unsigned or unrecognized img file
[09:15] <Khaytsus> You sure this file is valid?
[09:15] <asdfsdfsadf> Yes, tried 2 copies
[09:15] <asdfsdfsadf> Ok something just happened
[09:15] <asdfsdfsadf> Rom just loaded
[09:15] <asdfsdfsadf> I'm on the home screen
(Rebooted twice after it was stuck on loading screen)

Sorry for the long thread... Cleaning up the chat logs to make it more clear.

newklear85 said:
Sorry for the long thread... Cleaning up the chat logs to make it more clear.
Click to expand...
Click to collapse
don't get it xD

man, i have same problem on my xt1033 BR
i flash CM4.4.4
try flash restock 4.4.3
and it brinked..
long stuck on infinite bootload
or get multi FC on first boot
i read and try all method but no one work
i cant enter in any recovery..
twrp and cwm philz dnt work..
See:
Code:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.711.img
target reported max download size of 536870912 bytes
sending 'recovery' (7692 KB)...
OKAY [ 0.272s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.423s
C:\androidsdk\sdk\platform-tools>
it say ok, but on try go on recovert i stuck on black screen a
and every click on screen return a vibration for me.
i need long click (10seg) on power button to go away
and try again another version's.
:/
--------------------------------------------------------------------
same on 2.7.0.0:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.70.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [ 0.284s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.440s
black screen and every click on screen return a vibration.
---------------------------------------------------------------------
same on 2.6.3.3
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.63.img
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.307s]
writing 'recovery'...
OKAY [ 0.197s]
finished. total time: 0.506s
black screen and every click on screen return a vibration.
-------------------------------------------------------------------------
See:
C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw'.
i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report.
"i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report."

hansdepaula said:
man, i have same problem on my xt1033 BR
i flash CM4.4.4
try flash restock 4.4.3
and it brinked..
long stuck on infinite bootload
or get multi FC on first boot
i read and try all method but no one work
i cant enter in any recovery..
twrp and cwm philz dnt work..
See:
Code:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.711.img
target reported max download size of 536870912 bytes
sending 'recovery' (7692 KB)...
OKAY [ 0.272s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.423s
C:\androidsdk\sdk\platform-tools>
it say ok, but on try go on recovert i stuck on black screen a
and every click on screen return a vibration for me.
i need long click (10seg) on power button to go away
and try again another version's.
:/
--------------------------------------------------------------------
same on 2.7.0.0:
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.70.img
target reported max download size of 536870912 bytes
sending 'recovery' (7912 KB)...
OKAY [ 0.284s]
writing 'recovery'...
OKAY [ 0.154s]
finished. total time: 0.440s
black screen and every click on screen return a vibration.
---------------------------------------------------------------------
same on 2.6.3.3
C:\androidsdk\sdk\platform-tools>fastboot flash recovery twrp2.63.img
target reported max download size of 536870912 bytes
sending 'recovery' (8678 KB)...
OKAY [ 0.307s]
writing 'recovery'...
OKAY [ 0.197s]
finished. total time: 0.506s
black screen and every click on screen return a vibration.
-------------------------------------------------------------------------
See:
C:\androidsdk\sdk\platform-tools>fastboot format recovery
Formatting is not supported for filesystem with type 'raw'.
i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report.
"i really think fastboot dont write anything on my device..
bootlogo.img and recovery.img
dont change and i flash it 1000x with OK report."
Click to expand...
Click to collapse
I shortened the chat log. What are you getting when you do fastboot flash partition GPT.BIN from your stock rom?

gpt.bin for 4.4.3 stock dual sim + recovery twrp 2.6.3.3
Code:
C:\Users\Hans\Desktop\443>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.019s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.352s]
finished. total time: 0.373s
C:\Users\Hans\Desktop\443>mfastboot.exe flash recovery TWRP-2.6.3.3-falcon.img
target max-sparse-size: 256MB
sending 'recovery' (8678 KB)...
OKAY [ 0.302s]
writing 'recovery'...
OKAY [ 0.181s]
finished. total time: 0.485s
C:\Users\Hans\Desktop\443>
recovery give me a black screen and all touch return a vibration
i need press power for 10s to go away and try again
---------------------------------------------------------------------------
gpt.bin for 4.4.2 stock dual sim + recovery twrp 2.6.3.3
Code:
C:\Users\Hans\Desktop\442>mfastboot.exe flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.016s]
writing 'partition'...
(bootloader) Preflash validation failed
FAILED (remote failure)
finished. total time: 0.350s
C:\Users\Hans\Desktop\442>mfastboot.exe flash recovery TWRP-2.6.3.3-falcon.img
target max-sparse-size: 256MB
sending 'recovery' (8678 KB)...
OKAY [ 0.311s]
writing 'recovery'...
OKAY [ 0.165s]
finished. total time: 0.479s
C:\Users\Hans\Desktop\442>
same
recovery give me a black screen and all touch return a vibration
i need press power for 10s to go away and try again
-------------------------------------------------------------------------
my fastboot dnt write nothing,
i think, sone thing have format partitions to RAW system
and i cant white or format then..
see more logs about my case: http://forum.xda-developers.com/moto-g/help/help-downgrading-cm4-4-4-to-stock4-4-3-t2804228
maybe you can help..
thx..

newklear85 said:
I shortened the chat log. What are you getting when you do fastboot flash partition GPT.BIN from your stock rom?
Click to expand...
Click to collapse
it works for me THANk YOU
the only thing is i don't have mobile network any fix???
p.s. i use paranoid ANdroid neweset version

Fresroqir said:
it works for me THANk YOU
the only thing is i don't have mobile network any fix???
p.s. i use paranoid ANdroid neweset version
Click to expand...
Click to collapse
Only thread in here that can potentially make it work... almost no attention lol
For the mobile network, flash the radio that came with stock.

man, you can upload to me a new gpt.bin and motoboot.img ..
4.4.4 maybe
i only have 4.4.3 and lower versions, and it dont work..
:/

My Nexus 5 isn't bricked, but I can't seem to fix it. I can get into bootloader/recov

I seem to be having a ton of issues after getting my phone back from my wife. I can't get /data/ to mount unless I format it as FAT, but it won't format as ext4 or anything else. I tried flashing stock, but no dice. I did manage to get PA and CM up and running but I get a message telling me my storage is encrypted, and I definitley don't have a password. Factory resets dont help because if it tries to format /data/ it'll never finish. I let it run for hours even.
Is there any creative ideas I can try? I really can't afford a new phone, so I need to get this fixed, and I was defintley under the impression that if you can get into bootloader/recovery, then it is not bricked .

Zarilenth said:
I seem to be having a ton of issues after getting my phone back from my wife. I can't get /data/ to mount unless I format it as FAT, but it won't format as ext4 or anything else. I tried flashing stock, but no dice. I did manage to get PA and CM up and running but I get a message telling me my storage is encrypted, and I definitley don't have a password. Factory resets dont help because if it tries to format /data/ it'll never finish. I let it run for hours even.
Is there any creative ideas I can try? I really can't afford a new phone, so I need to get this fixed, and I was defintley under the impression that if you can get into bootloader/recovery, then it is not bricked .
Click to expand...
Click to collapse
fastboot flash userdata userdata.img
It'll wipe data and internal storage but it's the easiest way.

Lethargy said:
fastboot flash userdata userdata.img
It'll wipe data and internal storage but it's the easiest way.
Click to expand...
Click to collapse
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata.img
erasing 'userdata'...
OKAY [ 2.031s]
sending 'userdata' (137318 KB)...
OKAY [ 4.547s]
writing 'userdata'...
OKAY [ 8.884s]
finished. total time: 15.494s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I tried it and then tried fastboot update image-hammerhead-lpv79.zip and now it is hanging at erasing 'system'

Zarilenth said:
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot flash userdata userdata.img
erasing 'userdata'...
OKAY [ 2.031s]
sending 'userdata' (137318 KB)...
OKAY [ 4.547s]
writing 'userdata'...
OKAY [ 8.884s]
finished. total time: 15.494s
C:\Program Files (x86)\Minimal ADB and Fastboot>
I tried it and then tried fastboot update image-hammerhead-lpv79.zip and now it is hanging at erasing 'system'
Click to expand...
Click to collapse
Close and just try running flash-all.bat/sh

Lethargy said:
Close and just try running flash-all.bat/sh
Click to expand...
Click to collapse
Now it is hanging at erasing 'cache'
< waiting for device >
sending 'bootloader' (2508 KB)...
OKAY [ 0.281s]
writing 'bootloader'...
OKAY [ 0.484s]
finished. total time: 0.781s
rebooting into bootloader...
OKAY [ 0.078s]
finished. total time: 0.078s
sending 'radio' (45505 KB)...
OKAY [ 1.563s]
writing 'radio'...
OKAY [ 3.114s]
finished. total time: 4.693s
rebooting into bootloader...
OKAY [ 0.078s]
finished. total time: 0.078s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ11k
Baseband Version.....: M8974A-2.0.50.2.08
Serial Number........: 0651fd67006b5ff4
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
OKAY [ 0.094s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (8754 KB)...
OKAY [ 0.484s]
writing 'boot'...
OKAY [ 0.750s]
sending 'recovery' (9412 KB)...
OKAY [ 0.531s]
writing 'recovery'...
OKAY [ 0.781s]
erasing 'system'...
OKAY [ 1.250s]
sending 'system' (683564 KB)...
OKAY [ 21.820s]
writing 'system'...
OKAY [ 46.359s]
erasing 'userdata'...
OKAY [ 2.125s]
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.092s]
erasing 'cache'...

Zarilenth said:
Now it is hanging at erasing 'cache'
Click to expand...
Click to collapse
Try taking cache.img out of the zip and flash it separately?

Lethargy said:
Try taking cache.img out of the zip and flash it separately?
Click to expand...
Click to collapse
This sounded genius, I would have never thought to try this. I took it out and rezipped the folder, but it still tried to erase the cache and stopped there. Is there any way to stop it from trying to erase the cache?

Zarilenth said:
This sounded genius, I would have never thought to try this. I took it out and rezipped the folder, but it still tried to erase the cache and stopped there. Is there any way to stop it from trying to erase the cache?
Click to expand...
Click to collapse
When you flash something using fastboot it'll always erase. Try erasing cache without flashing, "fastboot erase cache"

Lethargy said:
When you flash something using fastboot it'll always erase. Try erasing cache without flashing, "fastboot erase cache"
Click to expand...
Click to collapse
I erased it and formatted it.
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot erase cache
< waiting for device >
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.637s]
finished. total time: 0.651s
C:\Program Files (x86)\Minimal ADB and Fastboot>fastboot format cache
erasing 'cache'...
OKAY [ 0.526s]
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 [ 2.118s]
finished. total time: 2.669s
C:\Program Files (x86)\Minimal ADB and Fastboot>

Zarilenth said:
I erased it and formatted it.
Click to expand...
Click to collapse
Reflash and see if it works?

Lethargy said:
Reflash and see if it works?
Click to expand...
Click to collapse
No still stuck at erasing 'cache'

Zarilenth said:
No still stuck at erasing 'cache'
Click to expand...
Click to collapse
Lg flashtool? Check my signature.

Zarilenth said:
No still stuck at erasing 'cache'
Click to expand...
Click to collapse
Weird then. Try using LG Flashtool. You can find it in the first link of my signature
---------- Post added at 07:28 AM ---------- Previous post was at 07:24 AM ----------
bitdomo said:
Lg flashtool? Check my signature.
Click to expand...
Click to collapse
Damn. xD

Lethargy said:
Weird then. Try using LG Flashtool. You can find it in the first link of my signature
---------- Post added at 07:28 AM ---------- Previous post was at 07:24 AM ----------
Damn. xD
Click to expand...
Click to collapse
I followed the steps very closely it got to 6% and then froze saying userdata erase fail

Zarilenth said:
I followed the steps very closely it got to 6% and then froze saying userdata erase fail
Click to expand...
Click to collapse
Try locking your bootloader:
fastboot oem lock
Then reboot it with:
fastboot reboot-bootloader
If it still shows as unlocked after the reboot, then your eMMC is dead/damaged and there isn't much you can do other than RMA or motherboard replacement

Lethargy said:
Try locking your bootloader:
fastboot oem lock
Then reboot it with:
fastboot reboot-bootloader
If it still shows as unlocked after the reboot, then your eMMC is dead/damaged and there isn't much you can do other than RMA or motherboard replacement
Click to expand...
Click to collapse
I am able to oem lock and unlock no problem. Should I be locked or unlocked for lg flashtool?

Zarilenth said:
I am able to oem lock and unlock no problem. Should I be locked or unlocked for lg flashtool?
Click to expand...
Click to collapse
I haven't had to use it myself yet so I'm not sure. Just go with unlocked anyways. Try it once more, if it doesn't work then I'm not sure whats up with your device.

Lethargy said:
I haven't had to use it myself yet so I'm not sure. Just go with unlocked anyways. Try it once more, if it doesn't work then I'm not sure whats up with your device.
Click to expand...
Click to collapse
I tried locked and unlocked and no go. I guess it's actually unfixable. What a waste of time.
I would ask Google for a replacement, but I am guessing that's not going to be free with all the tampering I did, and plus I live in Canada now, after buying it in the States.

Zarilenth said:
I tried locked and unlocked and no go. I guess it's actually unfixable. What a waste of time.
I would ask Google for a replacement, but I am guessing that's not going to be free with all the tampering I did, and plus I live in Canada now, after buying it in the States.
Click to expand...
Click to collapse
If you bought from the Play Store they'll replace it regardless any tampering, if its a real hardware fault. If you know anybody in the US you should be able to send it to them to RMA. Not sure if you can give Google a call from Canada if you bought it in the US, though

Wow. Google was so nice when I called. They're going to replace it for free and do shipping to and from Canada, because I did buy it from the US Play Store. Thanks for your help Lethargy. So glad to not have to try anything anymore.

MOTO G XT1032 black screen

I have a Moto G (XT1032) running Android 5.0.2 that went out of charge one day. It then decided to boot into a black screen - i.e. I can see the Motorola splash screen (animation) but all I get after that is a black (grey) screen, not responsive to touch.
I tried a few things and they didn't work -
Fastbooted and selected 'Recovery' option - The Motorola logo (first screen of startup splash screen) appears briefly. Then the device returns to fastboot menu saying 'Boot Up failed'
Fastbooted and selected 'Factory' - The Motorola splash screen appears, boots into same black (grey) screen again.
The fastboot menu says "Device is LOCKED. Status Code: 0". I did not enable USB debugging before my phone stopped working.
How do I get my phone working again?

You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795​
Is there important data on the phone? Then do not use the command: mfastboot erase userdata

lost101 said:
You do not need an unlocked Bootloader to flash one of the factory firmware images: (I suggest using only one of the 5.0.2 images)
http://forum.xda-developers.com/moto-g/general/index-moto-g-falcon-factory-firmware-t3110795​
Is there important data on the phone? Then do not use the command: mfastboot erase userdata
Click to expand...
Click to collapse
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".

Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
https://www.androidfilehost.com/?fid=23578570567719065​

C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash partition gpt.b
in
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.084s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
OKAY [ 0.330s]
finished. total time: 0.418s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash motoboot motobo
ot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.151s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.957s]
finished. total time: 1.112s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.095s]
writing 'logo'...
OKAY [ 0.035s]
finished. total time: 0.132s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.447s]
writing 'boot'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash recovery recove
ry.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.446s]
writing 'recovery'...
OKAY [ 0.599s]
finished. total time: 1.049s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257883 KB)...
OKAY [ 9.591s]
writing 'system'...
OKAY [ 7.728s]
finished. total time: 17.323s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256754 KB)...
OKAY [ 8.955s]
writing 'system'...
OKAY [ 8.082s]
finished. total time: 17.042s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260090 KB)...
OKAY [ 9.657s]
writing 'system'...
OKAY [ 8.179s]
finished. total time: 17.843s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash system system.i
mg_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (165316 KB)...
OKAY [ 6.347s]
writing 'system'...
OKAY [ 6.282s]
finished. total time: 12.635s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash modem NON-HLOS.
bin
target max-sparse-size: 256MB
sending 'modem' (49356 KB)...
OKAY [ 1.943s]
writing 'modem'...
OKAY [ 0.780s]
finished. total time: 2.727s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.015s]
finished. total time: 0.022s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.013s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (102 KB)...
OKAY [ 0.090s]
writing 'fsg'...
OKAY [ 3.185s]
finished. total time: 3.279s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.016s]
finished. total time: 0.017s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.020s]
finished. total time: 0.021s
C:\BRASIL_XT1032_5.0.2_LXB22.46-28_cid12_CFC.xml>mfastboot reboot
Click to expand...
Click to collapse
Thats all that i got... i don't know what else to do...

Joncillo said:
i do it, and nothing happend, just the black screen at the end of boot animation, also i unlock the bootloader and try to install a recovery (i try cwm, twrp and philz), but when i enter into recovery, only shows a android robot and says "No Command".
Click to expand...
Click to collapse
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2

pradeeppk said:
At this stage you should press power button for few seconds and tap vol +, it is the way to enter recovery in lollippp, correct me if I am wrong.
Sent from my XT1033 using Tapatalk 2
Click to expand...
Click to collapse
i do it, but i get the same message, "No Command"

lost101 said:
Please provide a log from mfastboot of those commands being performed. Make sure to actually use mfastboot.
Click to expand...
Click to collapse
I see something wierd now, looks like the memory of the phone dosent save anything... sometimes, when the boot animation stops, i see the message of "1 of 1 Updates, android its updating" and then go to the black screen again... but, if i flash the phone, i shouldn't see that message, rigth? so, why i can still see it? how can i erase all the memory for sure???

Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img

lost101 said:
Try flashing TWRP: https://www.androidfilehost.com/?fid=24052804347764184
Command: mfastboot flash recovery twrp-2.8.7.0.-falcon_STOCK.img - enter recovery afterwards.
If that fails to flash, try: mfastboot boot twrp-2.8.7.0.-falcon_STOCK.img
Click to expand...
Click to collapse
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja

Joncillo said:
flash recovery dosen't work, but with boot yes! now i'm on TWRP! so, what next?? tell me what to do, i don't wanna screw it!!! jajaja
Click to expand...
Click to collapse
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/

lost101 said:
Do you have anything you need to backup from the phone? Do you have ADB installed?
ADB Installer: http://forum.xda-developers.com/showthread.php?t=2588979
Backup command: ADB pull /sdcard c:/motog_backup/
Click to expand...
Click to collapse
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?

Joncillo said:
Done, i backup all that i need... so, what next??? wipe? or i try to install 5.0.2 again but as zip?
Click to expand...
Click to collapse
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip

lost101 said:
Wipe > Format Data. Wipe > Factory reset. ADB push or sideload ROM.zip
Click to expand...
Click to collapse
when i wipe the device, i get some errors.
E: MTP already enable
Formatting data using mkfs.f2fs...
Done
E: Unknown MTP message type 1:
You may need to reboot recovery to be able to use /data again.
Updating partition details...
E: Unable to stat '/data/data/com.google.android.gms/app_sslcache/www.googleapis.com.443'
E: Unable to stat '/data/data/com.google.android.calendar/databases/timelydata.db-shm'
...done
but don't wipe anything...
i try ADB Sideload but get an error too.
Starting ADB sideload feature... (After 10 minutes)
FAILED ADB Sideload complete.
and the CMD on windows says "Error: device not found"
also i try to install TWRP as zip, but when i restarted, enter into recovery and then i have the same android with error "No Command".

@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798

lost101 said:
@Joncillo - See the last post in this thread: http://forum.xda-developers.com/moto-g/help/moto-g-bootup-problem-recovery-mode-t3122492 - you are both in the same situation I believe.
It's a known issue; where battery is allowed to die and has resulted in Bootloader / Partition corruption.
Try what I have suggested there - if that does not solve it, you may have to wait for a working Lollipop hardbrick solution, which would allow you to repair the Bootloader: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
Click to expand...
Click to collapse
ahhhhhhhhh... i see... so, i have a dead phone... well, i'm going to try what you said in that post, thanks for all your help!!!

NEXUS 5 Stuck @ Boot Animation, Possible EMMC Failure?

Hi guys,
I woke up to find my Nexus off, still plugged in, which was strange. When i tried to turn it on, the Google Logo appeared, then the 4 Dots as per Marshmallow Boot animation...only they remained there 35 mins after I attempted to put on the phone.
I figured something was up with the boot, so I left it for a while after restarting, but and it was still stuck.
Since then I've tried reloading Stock Roms, (From KitKat to Marshmallow), installing custom recovery and trying anything I could find online to try to get this to work, but sadly I haven't been able to.
If i try to Reset, I get failed messages on some partitions.
I'll attach some logs showing the messages from some of these attempts.
Can anyone assist or help diagnose?
Attempt at Flashing KitKat with Nexus Root Toolkit
Flash Stock + Unroot [WugFresh Development]
------------------------------------------------------------------
target reported max download size of 1073741824 bytes
sending 'bootloader' (2508 KB)...
OKAY [ 0.285s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 0.487s
rebooting into bootloader...
OKAY [ 0.129s]
finished. total time: 0.130s
target reported max download size of 1073741824 bytes
sending 'radio' (45409 KB)...
OKAY [ 1.627s]
writing 'radio'...
FAILED (remote: flash write failure)
finished. total time: 2.854s
rebooting into bootloader...
OKAY [ 0.119s]
finished. total time: 0.120s
target reported max download size of 1073741824 bytes
sending 'boot' (8700 KB)...
OKAY [ 0.494s]
writing 'boot'...
OKAY [ 0.733s]
finished. total time: 1.230s
target reported max download size of 1073741824 bytes
erasing 'cache'...
OKAY [ 0.211s]
sending 'cache' (13348 KB)...
OKAY [ 0.629s]
writing 'cache'...
FAILED (remote: flash write failure)
finished. total time: 1.023s
target reported max download size of 1073741824 bytes
sending 'recovery' (9284 KB)...
OKAY [ 0.504s]
writing 'recovery'...
FAILED (remote: flash write failure)
finished. total time: 0.687s
target reported max download size of 1073741824 bytes
erasing 'system'...
FAILED (remote: failed to erase partition)
finished. total time: 0.115s
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
target reported max download size of 1073741824 bytes
erasing 'userdata'...
FAILED (remote: failed to erase partition)
finished. total time: 0.186s
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
target reported max download size of 1073741824 bytes
erasing 'cache'...
FAILED (remote: failed to erase partition)
finished. total time: 0.214s
rebooting...
finished. total time: 0.003s
If you require more information, ask and I will provide where I can.

did you try to flash the factory image?
Inviato dal mio P6000 Pro utilizzando Tapatalk

Terfysgol said:
did you try to flash the factory image?
Inviato dal mio P6000 Pro utilizzando Tapatalk
Click to expand...
Click to collapse
Yup, I tried flashing Stock Roms aka Factory Images for KitKat, Lollipop and Marshmallow as indicated in my original post.

Did you flash the userdata.img file and immediately boot to recovery to perform a factory wipe before booting the rom for the first time?

audit13 said:
Did you flash the userdata.img file and immediately boot to recovery to perform a factory wipe before booting the rom for the first time?
Click to expand...
Click to collapse
I did, and this also produces the Fails as before.

Could be a failed emmc issue.
If erasing the cachce, userdata, and factory reset don't work, it doesn't look good for the memory chip.

audit13 said:
Could be a failed emmc issue.
If erasing the cachce, userdata, and factory reset don't work, it doesn't look good for the memory chip.
Click to expand...
Click to collapse
I'm beginning to think this may be the case

Have you got an old nandroid that you know that works?
Inviato dal mio P6000 Pro utilizzando Tapatalk

I had similar issue but at least I could boot into bootloader to do this :
http://forum.xda-developers.com/showthread.php?t=2513701
I had the failed also then went to step 2 and did that:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader C:\image-hammerhead-krt16m\bootloader.img
fastboot reboot-bootloader
fastboot flash radio C:\image-hammerhead-krt16m\radio.img
fastboot reboot-bootloader
fastboot flash system C:\image-hammerhead-krt16m\system.img
fastboot flash userdata C:\image-hammerhead-krt16m\userdata.img
(Note: this command will wipe your device (including \sdcard), EVEN if your bootloader is already unlocked.)
fastboot flash boot C:\image-hammerhead-krt16m\boot.img
fastboot flash recovery C:\image-hammerhead-krt16m\recovery.img
*tip* Substitute lastest images by dragging and dropping them into cmd window, tip** hit arrow up on keypad to enter in last text to save a bunch of typing
It took FOREVER to boot but it did come back. BUT I have weird fc's and rando0m turn offs so I suspect new phone is coming.
I did phone the google and they connected me with LG for a repair option which will come back in max 9 days but I think even 100 bucks or whatever the cost ( they will phone with tally ) is more than the phone is worth.
Read the whole of the link I sent and Thank abaaaabbbb63 for his work
YMMV HTH
Zo0