Last Friday I tried to flash android 5 lolipop to my Nexus 5. It froze in the erasing part.
Eventualy switched the phone off and on. There was a loop where you could only see the droid, even in recovery mode.
I got around that loop by flashing TWRP to the recovery partition.
Al recovery ROM's however all state that they can't mount /cache.
I formatted the hell out of it but sadly it didn't solve the problem.
So using adb shell I removed the cache partition, recreated it and formatted it.
So here is my partition table:
Code:
Number Start End Size File system Name Flags
1 524kB 67.6MB 67.1MB fat16 modem
2 67.6MB 68.7MB 1049kB sbl1
3 68.7MB 69.2MB 524kB rpm
4 69.2MB 69.7MB 524kB tz
5 69.7MB 70.3MB 524kB sdi
6 70.3MB 70.8MB 524kB aboot
7 70.8MB 72.9MB 2097kB pad
8 72.9MB 73.9MB 1049kB sbl1b
9 73.9MB 74.4MB 524kB tzb
10 74.4MB 75.0MB 524kB rpmb
11 75.0MB 75.5MB 524kB abootb
12 75.5MB 78.6MB 3146kB modemst1
13 78.6MB 81.8MB 3146kB modemst2
14 81.8MB 82.3MB 524kB metadata
15 82.3MB 99.1MB 16.8MB misc
16 99.1MB 116MB 16.8MB ext4 persist
17 116MB 119MB 3146kB imgdata
18 119MB 142MB 23.1MB laf
19 142MB 165MB 23.1MB boot
20 165MB 188MB 23.1MB recovery
21 188MB 191MB 3146kB fsg
22 191MB 192MB 524kB fsc
23 192MB 192MB 524kB ssd
24 192MB 193MB 524kB DDR
25 193MB 1267MB 1074MB ext4 system
26 1267MB 1298MB 31.5MB crypto
27 1298MB 2032MB 734MB cache
28 2032MB 15.8GB 13.7GB ext4 userdata
29 15.8GB 15.8GB 5632B grow
Notice the missing ext4 for partition 27. After deleting and recreating the partition I formatted it with the following command:
Code:
mke2fs -t ext4 /dev/block/mmcblk0p27
this resulted in:
Code:
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
44832 inodes, 179200 blocks
8960 blocks (5.00%) reserved for the super user
First data block=0
Maximum filesystem blocks=184549376
6 block groups
32768 blocks per group, 32768 fragments per group
7472 inodes per group
Superblock backups stored on blocks:
32768, 98304, 163840
Writing inode tables: done
Creating journal (4096 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 29 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override
So at this point I wanted to check the my partition table again, but this time i got an error message:
Code:
Error: /dev/block/mmcblk0: unrecognised disk label
Mounting results in:
Code:
mount /cache
mount: mounting /dev/block/platform/msm_sdcc.1/by-name/cache on /cache failed: Invalid argument
Did I make any mistakes here? I did not rooted the phone (yet). Is this necessary?
The re partitioning part comes from a guide here originally for the kindle.
Current status is that I re flashed stock droid 4.4.4. It starts, but all Google applications crash and I have no cellular network .
Guess they all depend on the cache directory.
Any help on making the cache partition work again would be much appreciated!
Oh jeez. I guess by now you know what you've done wrong. In case you don't, you should have just flashed the stock cache.img via fastboot as the very first step.
When you say you flashed stock, how?
What is the output of fastboot flash cache cache.img?
Sent from my Nexus 5 using Tapatalk
My bad! I should have mentioned that I had tried all the basic steps.
So I flashed the original cache.img many times. Because some say it takes more then 1 try to fix a corrupt cache.
Also tried a manual erase and a format of the cache partition.
Flashing the cache is somewhat strange, I have 2 variants. One is done in a heartbeat saying everything went well:
Code:
D:\Downloads\hammerhead 4.4.4\image-hammerhead-ktu84p>fastboot flash cache cache.img
erasing 'cache'...
OKAY [ 0.511s]
sending 'cache' (13348 KB)...
OKAY [ 0.627s]
writing 'cache'...
OKAY [ 1.026s]
finished. total time: 2.169s
And then if I run it again it gets stuck at erasing:
Code:
D:\Downloads\hammerhead 4.4.4\image-hammerhead-ktu84p>fastboot flash cache cache.img
erasing 'cache'...
I once left it overnight but the following morning it was still erasing...
All the time the result is the same. A phone with crashing apps and no cellular network.
To answer your other question. I used fastboot to do a flash-all from the stock image from Google (image-hammerhead-ktu84p (4.4.4)).
Also did the manual version where I manual erase the partitions and flash them.
After this I get a working 4.4.4 with the exception that all Google apps crash (including Play etc, so the basic needs) and I have no cellular network.
Resulting in a useless phone.
The first output looks normal. Try and get it to that stage again so there is a successful flash, then try And fix persist partition as that has similar symptoms. Guide linked in my signature
Sent from my Nexus 5 using Tapatalk
Thank you so much for your reply.
I followed this guide.
The repair did nothing so I entered:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist
Since my dev/block/platform/msm_sdcc.1/by-name directory was empty is also did that same command for the cache:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
initially that looked like a good thing. The mounting error's where gone after i rebooted the phone.
But things took a turn for the worst. Where before i had a 50% chance on failing to erase the cache. I now have gained a 50% chance to fail at the writing stage.
Resulting in the device not being flash-able because there is more than one part that needs to be flashed.
Also, Philz is not usable. Although flashing states successful, It just won't boot into it. TWRP is the only thing that still works.
Did I do this myself by creating that cache bit? Or is corruption more likely?
Its hard to say. But I think it needs a professional repair now.
Sent from my Nexus 5 using Tapatalk
I'm afraid you are right.
From what I'm reading on the internet, I'm very unfortunate. It seems that in almost all cases you can recover from a flash that has gone south.
Anyway, I'll give it one or two more tries and if it fails I will look if I can claim it under warranty.
Can you answer one more question. Was it a mistake to enter:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
Could this break things even further?
Thank you for all your help. It is much appreciated.
Dujinga said:
I'm afraid you are right.
From what I'm reading on the internet, I'm very unfortunate. It seems that in almost all cases you can recover from a flash that has gone south.
Anyway, I'll give it one or two more tries and if it fails I will look if I can claim it under warranty.
Can you answer one more question. Was it a mistake to enter:
Code:
make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/cache
Could this break things even further?
Thank you for all your help. It is much appreciated.
Click to expand...
Click to collapse
It cannot break things further. Have you tried dd zero out cache? If there is an I/O problem then that most certainly will break the dd command. You can also try to read back the cache partition with dd command to /data or to / if have enough space on / to confirm there are no I/O errors. If you havent find any I/O errors then I can imagine two things. Something got messed up in the gpt partition or the mmc is fauilty.
I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>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.476s
Dujinga said:
I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>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.476s
Click to expand...
Click to collapse
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p27
Sent from my Nexus 5 using Tapatalk
Thank you for your reply. But running this command wil be a problem as it requiers Philz and ADB.
I can still flash Philz in the recovery, but it won't boot into the recovey afterwards
Guys, I want to thank you for all the help, but I'm giving up.
Gonna contact the supplier with the question how to resolve this issue.
Can't flash TWRP either?
What about
fastboot boot recovery.img
Where you don't flash but boot the recovery image from computer?
Sent from my Nexus 5 using Tapatalk
Dujinga said:
I'm a rookie, can you please explain how to "dd zero out" the cache?
P.S. I now have problems on other parts as well:
Code:
D:\Downloads\hammerhead 4.4.4>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.476s
Click to expand...
Click to collapse
rootSU said:
Can't flash TWRP either?
What about
fastboot boot recovery.img
Where you don't flash but boot the recovery image from computer?
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Pretty sure "FAILED (remote: flash write failure)" error means that the emmc is hosed.
It's best you claim warranty/insurance.
-Sent from a Lollipop'd Hammerhead!
Ok, so I flashed Philz again (btw TWRP always kept working but that one has a strange shell (limited)).
This time instead of booting straight into recovery after I flashed it, I turned it off and on again.
Now I could get into Philz.
So I ran:
Code:
dd if=/dev/zero of=/dev/block/mmcblk0p27
Expecting it to fail, but this was the result:
Code:
dd: writing '/dev/block/mmcblk0p27': No space left on device
1433601+0 records in
1433600+0 records out
734003200 bytes (700.0MB) copied, 41.996465 seconds, 16.7MB/s
That seems OK to me
So I'm going to try a bit more. I already openend a case with the reseller though.
One way or another this will get resolved
I didn't see that error. Yes, hosed.
Sent from my Nexus 5 using Tapatalk
The first time always failes, if I rerun command after a fail it succeeds (or it says it does).
Anayway this happens to all sections, but I start with the bootloader. Can't mess much around there because without the bootloader you are defenatly toast
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.477s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.473s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
So I tried to get into Philz again, but it is FUBAR again. I give up ...... can't stand it ..... argggghh
Dujinga said:
The first time always failes, if I rerun command after a fail it succeeds (or it says it does).
Anayway this happens to all sections, but I start with the bootloader. Can't mess much around there because without the bootloader you are defenatly toast
Code:
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.477s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.287s]
writing 'bootloader'...
FAILED (remote: flash write failure)
finished. total time: 43.473s
D:\Downloads\hammerhead 4.4.4>fastboot flash bootloader bootloader-hammerhead-hh
z11k.img
sending 'bootloader' (2508 KB)...
OKAY [ 0.286s]
writing 'bootloader'...
OKAY [ 0.398s]
finished. total time: 0.692s
So I tried to get into Philz again, but it is FUBAR again. I give up ...... can't stand it ..... argggghh
Click to expand...
Click to collapse
It's a wild goose chase mate. Do you even know what the error stands for? "Flash write failure" means the emmc is toast and hence nothing can be written on it. It's kinda become read only now. Even if the flash is successful, a quick reboot will roll everything back.
It's best you take it up with your seller and claim warranty. There;s nothing you can do.
Good luck!
I got the return instructions. Gonna mail it tommorow.
Once again a huge thanks to all of you guys. :good:
Related
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.
Hi everyone,
So I got a nexus 5 from a friend that he said was broken. He told me that he was doing and update and was taking too long so he rebooted his phone. Now the phone is stuck in a boot loop. Everything is stock on the phone and he said he never rooted it. I followed the steps on this thread(method 2 manually flashing each img) http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701 Here is the output from the CMD window:
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash bootloader bootloader.img
target reported max download size of 1073741824 bytes
sending 'bootloader' (2579 KB)...
OKAY [ 0.298s]
writing 'bootloader'...
OKAY [ 0.515s]
finished. total time: 0.813s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot reboot bootloader
usage: fastboot [ <option> ] <command>
commands:
update <filename> reflash device from update.zip
flashall flash boot + recovery + system
flash <partition> [ <filename> ] write a file to a flash partition
erase <partition> erase a flash partition
format <partition> format a flash partition
getvar <variable> display a bootloader variable
boot <kernel> [ <ramdisk> ] download and boot kernel
flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it
devices list all connected devices
continue continue with autoboot
reboot reboot device normally
reboot-bootloader reboot device into bootloader
help show this help message
options:
-w erase userdata and cache (and format
if supported by partition type)
-u do not first erase partition before
formatting
-s <specific device> specify device serial number
or path to device port
-l with "devices", lists device paths
-p <product> specify product name
-c <cmdline> override kernel commandline
-i <vendor id> specify a custom USB vendor id
-b <base_addr> specify a custom kernel base address.
default: 0x10000000
-n <page size> specify the nand page size. default:
2048
-S <size>[K|M|G] automatically sparse files greater th
an
size. 0 to disable
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.016s]
finished. total time: 0.016s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash radio radio.img
target reported max download size of 1073741824 bytes
sending 'radio' (45521 KB)...
OKAY [ 1.622s]
writing 'radio'...
OKAY [ 3.120s]
finished. total time: 4.743s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.000s]
finished. total time: 0.016s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash system system.img
target reported max download size of 1073741824 bytes
erasing 'system'...
OKAY [ 1.065s]
sending 'system' (981472 KB)...
OKAY [ 31.005s]
writing 'system'...
OKAY [ 66.272s]
finished. total time: 98.341s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 13.676s]
sending 'userdata' (137318 KB)...
OKAY [ 4.514s]
writing 'userdata'...
OKAY [ 9.179s]
finished. total time: 27.369s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash boot boot.img
target reported max download size of 1073741824 bytes
sending 'boot' (8852 KB)...
OKAY [ 0.485s]
writing 'boot'...
OKAY [ 0.749s]
finished. total time: 1.233s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash recovery recovery.img
target reported max download size of 1073741824 bytes
sending 'recovery' (9552 KB)...
OKAY [ 0.517s]
writing 'recovery'...
OKAY [ 0.782s]
finished. total time: 1.299s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.452s]
finished. total time: 0.452s
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>
Now when I select recovery after I flashed everything the phone turns off and doesn't come back on until I push the power button. Is that normal?(Not sure if this matters as well but sometimes when I push the power button + volume up and down the phone won't turn on. I have to just push the power button and let it boot loop, turn if off with the power button and try getting into fast boot again.) So I pushed the power button and load back into fastboot go into recovery and get the droid with the red exclamation mark. Push power + volume up and get into the options.
At the bottom of the screen it says:
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
E:failed to mount / cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
When I try wipe data/factory reset I get:
--Wiping data...
Formatting /data...
E:failed to mount /cache (Invalid argument)
Formatting /cache...
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
E:failed to mount / cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
Data wipe complete.
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery / log
E:Can't open /cache/recovery / log
E:failed to mount / cache (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /cache/recovery/last_install
E:Can't open /cache/recovery/last_install
E:failed to mount /cache (Invalid argument)
So I tried to wipe cache partition command and basically get the same thing as above the only string that is different is:
E:Failed closing /dev/block/platform/msm_sdcc.1/by-name/mis(I/O error)
Anyone know where I can go from here?
From what I can see you erased cache partition but didn't flash it back.
You need to flash cache partition also.
Code:
fastboot flash cache cache.img
varuntis1993 said:
From what I can see you erased cache partition but didn't flash it back.
You need to flash cache partition also.
Code:
fastboot flash cache cache.img
Click to expand...
Click to collapse
Yeah. My mistake. Doing that right now but now it's stuck.....
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
Been like this for about 20 minutes.
workonyou said:
Yeah. My mistake. Doing that right now but now it's stuck.....
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot flash cache cache.img
target reported max download size of 1073741824 bytes
erasing 'cache'...
Been like this for about 20 minutes.
Click to expand...
Click to collapse
20min, it should only take seconds to flash it.
I hope you are using usb 2.0 ports.
varuntis1993 said:
20min, it should only take seconds to flash it.
I hope you are using usb 2.0 ports.
Click to expand...
Click to collapse
Yes I am.
workonyou said:
Yes I am.
Click to expand...
Click to collapse
Have you tried disconnecting and connecting again?
I am not sure whether you should do that or not, but you have no other choice right now.
varuntis1993 said:
Have you tried disconnecting and connecting again?
I am not sure whether you should do that or not.
Click to expand...
Click to collapse
I tried something else. I flashed the 4.4.4 stock img using flash-all. Phone booted into android but now camera, google play and gallery are constantly crashing. As well when I try to do a software update it won't download. So I tried to download a random file using chrome and when I did it said "NO SD CARD." What can I do now?
workonyou said:
I tried something else. I flashed the 4.4.4 stock img using flash-all. Phone booted into android but now camera, google play and gallery are constantly crashing. As well when I try to do a software update it won't download. So I tried to download a random file using chrome and when I did it said "NO SD CARD." What can I do now?
Click to expand...
Click to collapse
Try factory reset from stock recovery.
Are you able to lock the bootloader? lock it, reboot and check whether it got locked or not.
Code:
fastboot oem lock
varuntis1993 said:
Try factory reset from stock recovery.
Are you able to lock the bootloader? lock it, reboot and check whether it got locked or not.
Code:
fastboot oem lock
Click to expand...
Click to collapse
When you say factory reset from stock recovery do you mean going into fastboot>recovery>factory/data reset?
I'll try locking the bootloader now.
Not sure if this helps. But when I flashed the 4.4.4 cache IMG it worked fine. Why doesn't the 5.01 work? See output for 4.4.4:
OKAY [ 14.446s]
erasing 'cache'...
OKAY [ 0.525s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.862s]
****
EDIT
I am able to lock the bootloader
workonyou said:
When you say factory reset from stock recovery do you mean going into fastboot>recovery>factory/data reset?
I'll try locking the bootloader now.
Not sure if this helps. But when I flashed the 4.4.4 cache IMG it worked fine. Why doesn't the 5.01 work? See output for 4.4.4:
OKAY [ 14.446s]
erasing 'cache'...
OKAY [ 0.525s]
formatting 'cache' partition...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7472
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44832 inodes and 5813/179200 blocks
sending 'cache' (13348 KB)...
writing 'cache'...
OKAY [ 1.862s]
****
EDIT
I am able to lock the bootloader
Click to expand...
Click to collapse
Since you are able to lock the bootloader, there should not be any issue with nand.
yep I meant that.
how did you install fastboot? you have latest files? Replace them with these
https://www.androidfilehost.com/?fid=95784891001607611
varuntis1993 said:
Since you are able to lock the bootloader, there should not be any issue with nand.
yep I meant that.
how did you install fastboot? you have latest files? Replace them with these
https://www.androidfilehost.com/?fid=95784891001607611
Click to expand...
Click to collapse
Hmmm. I think I was using an older version of fastboot. I was going to try and re-flash everything so I went ahead and unlocked the bootloader and now it's stuck erasing again.
workonyou said:
Hmmm. I think I was using an older version of fastboot. I was going to try and re-flash everything so I went ahead and unlocked the bootloader and now it's stuck erasing again.
Click to expand...
Click to collapse
It takes quite some time to erase when unlocking the bootloader.
varuntis1993 said:
It takes quite some time to erase when unlocking the bootloader.
Click to expand...
Click to collapse
I was still erasing after 1hr+ so I powered off the phone went back into fastboot(unlocked) and flashed 5.01 images using the fastboot you linked. Output:
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>fastb
oot devices
04a9c8e213afcb97 fastboot
C:\Users\brad\Desktop\hammerhead-lrx22c-factory-0f9eda1b\hammerhead-lrx22c>flash
-all
sending 'bootloader' (2579 KB)...
OKAY [ 0.299s]
writing 'bootloader'...
OKAY [ 0.463s]
finished. total time: 0.765s
rebooting into bootloader...
OKAY [ 0.122s]
finished. total time: 0.123s
target reported max download size of 1073741824 bytes
sending 'radio' (45521 KB)...
OKAY [ 1.618s]
writing 'radio'...
OKAY [ 3.124s]
finished. total time: 4.743s
rebooting into bootloader...
OKAY [ 0.120s]
finished. total time: 0.120s
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...: HHZ12d
Baseband Version.....: M8974A-2.0.50.2.22
Serial Number........: 04a9c8e213afcb97
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.099s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8852 KB)...
OKAY [ 0.489s]
writing 'boot'...
OKAY [ 0.753s]
sending 'recovery' (9552 KB)...
OKAY [ 0.545s]
writing 'recovery'...
OKAY [ 0.797s]
erasing 'system'...
OKAY [ 0.950s]
sending 'system' (981472 KB)...
OKAY [ 30.993s]
writing 'system'...
OKAY [ 66.258s]
erasing 'userdata'...
OKAY [ 11.154s]
erasing 'cache'...
OKAY [ 0.449s]
sending 'cache' (13348 KB)...
OKAY [ 0.629s]
writing 'cache'...
OKAY [ 1.029s]
rebooting...
finished. total time: 114.872s
Press any key to exit...
Now when the phone restarted I get the android and gear, it stays on for about 2 minutes and reboots and does the same thing again. Boot loop again.
Just do factory reset from stock recovery.
varuntis1993 said:
Just do factory reset from stock recovery.
Click to expand...
Click to collapse
When I go into recovery I get the same thing now. Sigh
workonyou said:
When I go into recovery I get the same thing now. Sigh
Click to expand...
Click to collapse
You mean those same cache errors?
varuntis1993 said:
You mean those same cache errors?
Click to expand...
Click to collapse
No I get the android with the gear just spinning.
workonyou said:
No I get the android with the gear just spinning.
Click to expand...
Click to collapse
Sorry mate, I am out of ideas now. Hope @abaaaabbbb63 or someone else can help you.
varuntis1993 said:
Sorry mate, I am out of ideas now. Hope @abaaaabbbb63 or someone else can help you.
Click to expand...
Click to collapse
Darn. Thanks for trying. Really appreciate it. I did the oem unlock again and it's still hanging.
C:\Users\brad\Desktop\hammerhead-ktu84p-factory-35ea0277\hammerhead-ktu84p>fastb
oot oem unlock
...
Is what I get and the phone says erasing.... Going to leave it for 2hrs+ this time.
If anyone has more ideas please let me know!
workonyou said:
Darn. Thanks for trying. Really appreciate it. I did the oem unlock again and it's still hanging.
C:\Users\brad\Desktop\hammerhead-ktu84p-factory-35ea0277\hammerhead-ktu84p>fastb
oot oem unlock
...
Is what I get and the phone says erasing.... Going to leave it for 2hrs+ this time.
If anyone has more ideas please let me know!
Click to expand...
Click to collapse
Just came to my mind, how about flashing custom recovery, flash twrp, check how much internal storage it shows. If its 0MB.
Then try this
http://forum.xda-developers.com/google-nexus-5/general/guide-to-fix-persist-partition-t2821576
Also how much time are u waiting for it to boot?
Hi,
A friend asked me to look at his Nexus 5.
It seemed as though his son was trying to flash a custom rom but somewhere along the way things went wrong and it got stuck on the boot animation.
I tried resetting it to factory using this thread.
Followed method 2 and finished it up with "Wipe data/factory data" reset. I did not however relock the boot loader.
I used the factory image 6.0.1 (MMB29S).
Everything went well, no errors, but even after doing all that the phone is still stuck on the boot animation. I tried redoing the "Wipe data/factory data" reset, but the phone is still stuck on boot animation.
I left for around 20 minutes with no change.
All the other threads I have read seem to indicate doing the "wipe data/factory data" reset should correct this issue but it hasn't seemed to help.
I also found this thread. The last post could possibly be another option.
Is there anything I can try? or is there a log I can look?
Any suggestions would be greatly appreciated.
Cheers
Boot the phone into fastboot and flash the userdata.img from the stock rom to the phone using the following command: fastboot flash userdata userdata.img. After flashing, boot into stock recovery using the volume and power button, wipe data and cache, reboot.
audit13 said:
Boot the phone into fastboot and flash the userdata.img from the stock rom to the phone using the following command: fastboot flash userdata userdata.img. After flashing, boot into stock recovery using the volume and power button, wipe data and cache, reboot.
Click to expand...
Click to collapse
Thanks for the reply.
I did as you suggested, unfortunately I am still stuck on boot animation.
Output from command
Code:
c:\image-hammerhead-mmb29s>fastboot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 8.014s]
sending 'userdata' (137318 KB)...
OKAY [ 4.510s]
writing 'userdata'...
OKAY [ 9.149s]
finished. total time: 21.673s
I was just looking at the contents of the zip I downloaded from the developer site. The data stamps on the images seem old. Most date back to 2009. Perhaps I have downloaded the wrong files?
Did the userdata.img file come from the mmb29s ROM? After flashing, did you immediately boot into recovery and perform a factory wipe?
audit13 said:
Did the userdata.img file come from the mmb29s ROM? After flashing, did you immediately boot into recovery and perform a factory wipe?
Click to expand...
Click to collapse
Yes the userdata.img did come from the mmb29s ROM. I have no other ROM files downloaded.
Yes I did I believe, if I recall correctly, these were my steps:
Booted phone into fastboot by pressing the power and down volume key
flashed the userdata.img using the command provided
Used the volume rocket to select "Recovery"
When the dead Android appeared I pressed the power button and up volume rocker to display the menu
Proceeded to the option to wipe and reset data
Rebooted the phone
I am pretty sure those were the steps I used.
Should I have rebooted first before going directly into Recovery?
Yup, those are the proper steps.
When you wiped in recovery, did you see a line at the bottom that said something like "invalid format" or "could not mount" just before the data and cache partitions were formatted?
audit13 said:
Yup, those are the proper steps.
When you wiped in recovery, did you see a line at the bottom that said something like "invalid format" or "could not mount" just before the data and cache partitions were formatted?
Click to expand...
Click to collapse
No I didn't notice any error messages unfortunately.
And I don't recall seeing any error messages during any of the other steps I have performed.
The commands all seem to successfully execute with no errors.
Does it at all make sense for me to go back and completely redo all the steps from the tutorial in my first post?
I can post the outputs from all the commands if you think that would at all be helpful?
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
audit13 said:
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
Click to expand...
Click to collapse
Okay perfect. I will give method 1 a try tonight (I am unfortunately at work right now).
I will report back tonight... hopefully with good news
audit13 said:
I personally use method 1. Method 1 will cause the phone to reboot after flashing each partition and will probably cause the phone to be stuck at the boot logo. Press and hold the power button to force the phone to shut down. After finishing method 1, boot into fastboot mode and type these fastboot commands:
fastboot erase cache
fastboot erase userdata
fastboot flash userdata userdata.img
Boot into recovery. At the bottom of the screen, you should see the statement "E: failed to mount /cache (Invalid argument)". Choose the wipe data/factory reset option, then select wipe cache partition, and reboot.
Click to expand...
Click to collapse
Sorry for the late reply on this.
I got around to doing the steps above.
Unfortunately I am still stuck on the boot animation screen.
Here is the output from the commands I ran
Code:
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.297s]
writing 'bootloader'...
OKAY [ 0.500s]
finished. total time: 0.797s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.078s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.540s]
writing 'radio'...
OKAY [ 3.125s]
finished. total time: 4.665s
rebooting into bootloader...
OKAY [ 0.063s]
finished. total time: 0.063s
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.28
Serial Number........:
--------------------------------------------
checking product...
OKAY [ 0.094s]
checking version-bootloader...
OKAY [ 0.109s]
checking version-baseband...
OKAY [ 0.094s]
sending 'boot' (9154 KB)...
OKAY [ 0.500s]
writing 'boot'...
OKAY [ 0.781s]
sending 'recovery' (10012 KB)...
OKAY [ 0.562s]
writing 'recovery'...
OKAY [ 0.828s]
erasing 'system'...
OKAY [ 1.297s]
sending 'system' (1020413 KB)...
OKAY [ 32.163s]
writing 'system'...
OKAY [ 69.508s]
erasing 'userdata'...
OKAY [ 8.326s]
sending 'userdata' (137318 KB)...
OKAY [ 4.500s]
writing 'userdata'...
OKAY [ 9.138s]
erasing 'cache'...
OKAY [ 0.672s]
sending 'cache' (13348 KB)...
OKAY [ 0.625s]
writing 'cache'...
OKAY [ 1.078s]
rebooting...
finished. total time: 130.775s
Press any key to exit...
////// -------- AFTER COMPLETE POWER OFF AND REBOOT -------- \\\\\\\\
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.625s]
finished. total time: 0.641s
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot erase userdata
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 8.384s]
finished. total time: 8.399s
C:\Temp\hammerhead-mmb29s-factory-6bfcdfa4\hammerhead-mmb29s\image-hammerhead-mmb29s>fastboot flash userdata userdata.img
target reported max download size of 1073741824 bytes
erasing 'userdata'...
OKAY [ 8.220s]
sending 'userdata' (137318 KB)...
OKAY [ 4.516s]
writing 'userdata'...
OKAY [ 9.156s]
finished. total time: 21.892s
Everything seemed to go okay.
Does everything in the output above look okay?
Everything looks fine. Did you boot into recovery and perform a factory wipe after flashing userdata.img?
audit13 said:
Everything looks fine. Did you boot into recovery and perform a factory wipe after flashing userdata.img?
Click to expand...
Click to collapse
Yes I did do that and did the clear of the cache as well since it posted that error message like you said it would.
So I did both as you explained.
I took a picture of the phone itself after the userdata wipe.
https://www.dropbox.com/s/k05s06avrha1lfv/IMG_20160206_153435.jpg?dl=0
Hmm, I'm not sure what is wrong because you did exactly what I do every time I need to fix a bootloop.
audit13 said:
Hmm, I'm not sure what is wrong because you did exactly what I do every time I need to fix a bootloop.
Click to expand...
Click to collapse
Well that sucks!
I had read that in some cases this can be caused by a hardware issue. Any chance it could be that?
Btw, the links I provided to the stock Google images, were they the correct images?
These are the stock images: https://developers.google.com/android/nexus/images#hammerhead
Did you try flashing a stock 4.4.2 or 5.01 image too?
audit13 said:
These are the stock images: https://developers.google.com/android/nexus/images#hammerhead
Did you try flashing a stock 4.4.2 or 5.01 image too?
Click to expand...
Click to collapse
hi,
sorry for my late reply. I got sick and just didn't have it in me to try anything new.
I tried flashing 5.0.1 tonight and unfortunately wound up in another boot loop. I will have to try the steps again where you manually reflash userdata. Hopefully I will have time tomorrow!
Hi
My phone has the exact same problem as stated by OP. I even tried flashing kitkat and lollipop but the problem persist. The phone still stuck at boot animation screen. PLS help.
Boot into ffastboot, relock the bootloader, and then reboot into fastboot. Does the bootloader remain unlocked?
audit13 said:
Boot into ffastboot, relock the bootloader, and then reboot into fastboot. Does the bootloader remain unlocked?
Click to expand...
Click to collapse
The bootloader is now locked. Still, I can't boot the phone completely. stuck at Google boot animation.
At this point, I would conclude that something is wrong with the memory chip.
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
Hi there, i have spent hours trying to recover my Moto G XT1032 using this forum and I have mad progress but my phone is still dead.
Phone:
Motorola XT1032 - it was the latest stock ROM, always updated to the newest version. (Very probably a non-branded EU retail, 5.1 ROM)
Problem:
Battery got drained. When put on charger, it was 'optimising cache app x of y' for a long time, sometimes it does this anyway.
Then it went into bootloop, stuck at the Motorola logo. It doesn't restart and the logo doesn't starts animating like it normally does.
Fastboot (Power + vol down) worked, but going into recovery failed, leaving me stuck with the same M logo.
Solutions tried:
1. Connection to computer: didn't work. Seen as 'fastboot device' when in fastboot but that's it.
2. Using Android recovery software. Useless because of the above and useless pieces of software anyway.
3. Re-flashing stock ROM. After installing Motorola drivers and mfastboot, I tried to flash FALCON_RETEU_5.1_LPBS23.13-56-2_cid7_CFC, and according to the phone it was successful, but it still left me stuck at the bootloop. Even after manually flashing everything from partition tables to system images.
4. I unlocked the phone to install a custom TWRP recovery. The unlock was successful.
5. Tried to install TWRP recovery - to recover my files at least -, the command line says success, the phone says
Code:
Mismatched partition size (recovery)
Many have said in this forum to ignore this message - well, I can't since it can't write the recovery partition.
6. At this point the factory recovery started working ('no command' screen, then pressing 'vol up + power')
7. I have been able to boot into TWRP with
Code:
mfastboot boot twrp-3.0.0.0_2-falcon.img
What a workaround! Well, I have at least been able to access my files over MTP. Yay! :fingers-crossed:
8. Here comes the problem: I can't wipe the device. I can't copy anything over MTP. I can't delete files over mtp: it looks like the files are deleted but they reappear after restarting the device.
Note: I can access a simple
Code:
adb shell
in recovery.
So once again, I'm unable to install a custom recovery via mfastboot, and it looks like the whole device was write-protected for whatever reason. At least I've been able to save my data thanks to the useful resources here! Any ideas about what else I could possibly try?
Any help is much appreciated!
Hey you can boot into fastboot which means that your phone is not hard bricked thats is a great news.
You can try wiping the partitions in the fastboot if the bootloader is unlocked
Try this in fastboot mode:
(Use mfastboot) :- http://forum.xda-developers.com/attachment.php?attachmentid=3476163&stc=1&d=1442444179
Code:
mfastboot erase system
mfastboot erase cache
mfastboot erase userdata
mfastboot erase recovery
mfastboot erase modemst1
mfastboot erase modemst2
Then install the stock rom or flash recovery then install a custom ROM.
Hit thanks if it worked..!
Stay Crazy
Paradox♀ said:
Hey you can boot into fastboot which means that your phone is not hard bricked thats is a great news.
You can try wiping the partitions in the fastboot if the bootloader is unlocked
Try this in fastboot mode:
(Use mfastboot) :- http://forum.xda-developers.com/attachment.php?attachmentid=3476163&stc=1&d=1442444179
Code:
mfastboot erase system
mfastboot erase cache
mfastboot erase userdata
mfastboot erase recovery
mfastboot erase modemst1
mfastboot erase modemst2
Then install the stock rom or flash recovery then install a custom ROM.
Hit thanks if it worked..!
Stay Crazy
Click to expand...
Click to collapse
Thanks!
It erased everything OK, at least no error messages.
Fun fact: it still boots into factory recovery after erasing the recovery partition!
Fun fact 2: I still can't flash custom recoveries like TWRP. ('Partition mismatch' error and then boots into factory recovery as if nothing changed. If I manually 'mfastboot boot twrp....img' into the image, then the internal storage shows up intact as before the phone was broken!
Then I flashed new stock ROMs, all returned OK, but still bootloop:
Code:
mfastboot flash partition gpt.bin
mfastboot flash motoboot motoboot.img
mfastboot flash logo logo.bin
mfastboot flash boot boot.img
mfastboot flash recovery recovery.img
mfastboot flash system system.img_sparsechunk.0
mfastboot flash system system.img_sparsechunk.1
mfastboot flash system system.img_sparsechunk.2
mfastboot flash system system.img_sparsechunk.3
mfastboot flash modem NON-HLOS.bin
mfastboot erase modemst1
mfastboot erase modemst2
mfastboot flash fsg fsg.mbn
mfastboot erase cache
mfastboot erase userdata
mfastboot reboot
Here's the complete output:
Code:
D:\tmp>mfastboot erase system
erasing 'system'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.023s]
finished. total time: 0.025s
D:\tmp>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.017s]
finished. total time: 0.018s
D:\tmp>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.026s]
finished. total time: 0.028s
D:\tmp>mfastboot erase recovery
erasing 'recovery'...
(bootloader) Erase allowed in unlocked state
OKAY [ 0.037s]
finished. total time: 0.037s
D:\tmp>mfastboot erase modemst1
erasing 'modemst1'...
OKAY [ 0.012s]
finished. total time: 0.013s
D:\tmp>mfastboot erase modemst2
erasing 'modemst2'...
OKAY [ 0.012s]
finished. total time: 0.013s
D:\tmp>mfastboot flash partition gpt.bin
target max-sparse-size: 256MB
sending 'partition' (32 KB)...
OKAY [ 0.025s]
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.303s]
finished. total time: 0.330s
D:\tmp>mfastboot flash motoboot motoboot.img
target max-sparse-size: 256MB
sending 'motoboot' (1953 KB)...
OKAY [ 0.084s]
writing 'motoboot'...
(bootloader) flashing tz ...
(bootloader) flashing rpm ...
(bootloader) flashing sdi ...
(bootloader) flashing aboot ...
(bootloader) flashing sbl1 ...
OKAY [ 0.930s]
finished. total time: 1.018s
D:\tmp>mfastboot flash logo logo.bin
target max-sparse-size: 256MB
sending 'logo' (295 KB)...
OKAY [ 0.055s]
writing 'logo'...
OKAY [ 0.036s]
finished. total time: 0.095s
D:\tmp>mfastboot flash boot boot.img
target max-sparse-size: 256MB
sending 'boot' (10240 KB)...
OKAY [ 0.360s]
writing 'boot'...
OKAY [ 0.585s]
finished. total time: 0.948s
D:\tmp>mfastboot flash recovery recovery.img
target max-sparse-size: 256MB
sending 'recovery' (10240 KB)...
OKAY [ 0.363s]
writing 'recovery'...
OKAY [ 0.591s]
finished. total time: 0.958s
D:\tmp>mfastboot flash system system.img_sparsechunk.0
target max-sparse-size: 256MB
sending 'system' (257755 KB)...
OKAY [ 8.153s]
writing 'system'...
OKAY [ 7.753s]
finished. total time: 15.907s
D:\tmp>mfastboot flash system system.img_sparsechunk.1
target max-sparse-size: 256MB
sending 'system' (256953 KB)...
OKAY [ 8.132s]
writing 'system'...
OKAY [ 7.910s]
finished. total time: 16.044s
D:\tmp>mfastboot flash system system.img_sparsechunk.2
target max-sparse-size: 256MB
sending 'system' (260396 KB)...
OKAY [ 8.234s]
writing 'system'...
OKAY [ 7.899s]
finished. total time: 16.137s
D:\tmp>mfastboot flash system system.img_sparsechunk.3
target max-sparse-size: 256MB
sending 'system' (166176 KB)...
OKAY [ 5.274s]
writing 'system'...
OKAY [ 6.251s]
finished. total time: 11.528s
D:\tmp>mfastboot flash modem NON-HLOS.bin
target max-sparse-size: 256MB
sending 'modem' (49376 KB)...
OKAY [ 1.599s]
writing 'modem'...
OKAY [ 0.763s]
finished. total time: 2.365s
D:\tmp>mfastboot flash fsg fsg.mbn
target max-sparse-size: 256MB
sending 'fsg' (103 KB)...
OKAY [ 0.088s]
writing 'fsg'...
OKAY [ 3.177s]
finished. total time: 3.268s
D:\tmp>mfastboot erase cache
erasing 'cache'...
OKAY [ 0.015s]
finished. total time: 0.017s
D:\tmp>mfastboot erase userdata
erasing 'userdata'...
OKAY [ 0.019s]
finished. total time: 0.024s
D:\tmp>mfastboot reboot
rebooting...
finished. total time: 0.002s
D:\tmp>
I think I have the same symptoms as this user.
Maybe the file system is corrupted? Or the bootloader?
Or just the flash memory in the phone stopped working properly.
Let's recap:
Erasing partitions doesn't actually erase them but it returns OK
Can't erase userdata
Can't install custom recoveries
Flashing stock ROM returns OK but still can't boot.
I'm pretty sure the eMMC (internal memory chip) has been damaged. Goodbye, phone...
Fortunately I still had my good ol' ZTE Blade sitting in the drawer.
Sorry for the late reply,
If the data partition is corrupt then you can try wiping data partition under Wipe-->Format Data in TWRP that should do the trick.
Paradox♀ said:
Sorry for the late reply,
If the data partition is corrupt then you can try wiping data partition under Wipe-->Format Data in TWRP that should do the trick.
Click to expand...
Click to collapse
tl;dr: can't fsck, can't format, can't mfastboot erase, can't twrp erase.
Thanks! I've tried it, it doesn't work. Looks like it's wiped, then after restart it doesn't.
But doesn't the command you have suggested before
Code:
mfastboot erase userdata
erase the data partition?
I'm concerned that the eMMC is damaged and my phone can't be put to life again - if a complete erase & flash (including partition table, see my previous post) doesn't work then what does?
Here's a df output from TWRP:
Code:
/data # df -h
df -h
Filesystem Size Used Available Use% Mounted on
tmpfs 435.3M 20.0K 435.3M 0% /dev
tmpfs 435.3M 20.0K 435.3M 0% /tmp
/dev/block/mmcblk0p33
651.7M 11.6M 640.0M 2% /cache
/dev/block/mmcblk0p36
5.5G 4.6G 927.0M 83% /data
/dev/block/mmcblk0p36
5.5G 4.6G 927.0M 83% /sdcard
/dev/block/mmcblk0p1 62.4M 46.5M 15.9M 75% /firmware
/dev/block/mmcblk0p34
960.6M 938.1M 22.6M 98% /system
Here's a worrisome FSCK output on the data partition:
Code:
/sbin # fsck.f2fs /dev/block/mmcblk0p36
fsck.f2fs /dev/block/mmcblk0p36
Info: sector size = 512
Info: total sectors = 11583232 (in 512 bytes)
Info: MKFS version
""
Info: FSCK version
from "Linux version 3.4.42-g89906d6 ([email protected]) (gcc version 4.8 (GCC) ) #1 SMP PREEMPT Fri Feb 26 06:48:18 CST 2016"
to "Linux version 3.4.42-g661f6ff ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Feb 15 19:02:51 PST 2016"
[FIX] (fsck_chk_orphan_node: 926) --> Discard orphan inodes: ino [0x31040]
[FIX] (fsck_chk_orphan_node: 926) --> Discard orphan inodes: ino [0x315d9]
NID[0x31040] is unreachable
NID[0x315d9] is unreachable
NID[0x315da] is unreachable
NID[0x315e2] is unreachable
NID[0x315e6] is unreachable
NID[0x315ec] is unreachable
NID[0x315ef] is unreachable
NID[0x315f1] is unreachable
NID[0x315f4] is unreachable
NID[0x315f9] is unreachable
NID[0x31600] is unreachable
[FSCK] Unreachable nat entries [Fail] [0xb]
[FSCK] SIT valid block bitmap checking [Fail]
[FSCK] Hard link checking for regular file [Ok..] [0x0]
[FSCK] valid_block_count matching with CP [Fail] [0xfd3d3]
[FSCK] valid_node_count matcing with CP (de lookup) [Fail] [0x78ea]
[FSCK] valid_node_count matcing with CP (nat lookup) [Ok..] [0x78f5]
[FSCK] valid_inode_count matched with CP [Fail] [0x75ed]
[FSCK] free segment_count matched with CP [Ok..] [0x15a]
[FSCK] next block offset is free [Ok..]
[FSCK] fixing SIT types
[FSCK] other corrupted bugs [Fail]
Error: Could not conduct fsync!!!
Done.
And what happens when I try to format the data partition? This:
Code:
/sbin # mkfs.f2fs /dev/block/mmcblk0p36
mkfs.f2fs /dev/block/mmcblk0p36
F2FS-tools: mkfs.f2fs Ver: 1.4.0 (2014-10-18) [modified by Motorola to reserve space]
Info: sector size = 512
Info: total sectors = 11583232 (in 512 bytes)
Info: zone aligned segment0 blkaddr: 512
Info: format version with
"Linux version 3.4.42-g661f6ff ([email protected]) (gcc version 4.9.x-google 20140827 (prerelease) (GCC) ) #1 SMP PREEMPT Mon Feb 15 19:02:51 PST 2016"
Error: Could not conduct fsync!!!
Info: format successful
Exact same error as for example here.
Hey is there any chance that you have a backup image that could be used to restore the partitions?
Paradox♀ said:
Hey is there any chance that you have a backup image that could be used to restore the partitions?
Click to expand...
Click to collapse
Well, I don't, but I used stock ROM images from this forum. It's the same stuff that was installed before failure.
If I can't run a simple fsck, then I'm 90% sure it's some hardware issue. Based on how many people are having the same problem, maybe the eMMC chips are reaching the end of their (short) lifetime.
Yeah it seems so.