Hello,
Today I made an attempt to update my Nexus 5 to Android 6, manually.
So I put it into USB debugging mode, connected to my PC, and run "flash-all.bat" from firmware archive.
For some reason it ended up with message FAILED, but Android 6 was installed on my phone.
I wonder, what has failed, and should I worry about it, should I do something about it?
Update log:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
e:\Software\Android-SDK-Unlock\Android_v6>flash-all.bat
target reported max download size of 1073741824 bytes
sending 'bootloader' (3120 KB)...
OKAY [ 0.313s]
writing 'bootloader'...
OKAY [ 0.567s]
finished. total time: 0.880s
rebooting into bootloader...
OKAY [ 0.117s]
finished. total time: 0.117s
target reported max download size of 1073741824 bytes
sending 'radio' (45425 KB)...
OKAY [ 1.812s]
writing 'radio'...
OKAY [ 3.183s]
finished. total time: 4.995s
rebooting into bootloader...
OKAY [ 0.102s]
finished. total time: 0.102s
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'
--------------------------------------------
Bootloader Version...: HHZ12k
Baseband Version.....: M8974A-2.0.50.2.27
Serial Number........: 0......................8
--------------------------------------------
checking product...
OKAY [ 0.092s]
checking version-bootloader...
OKAY [ 0.101s]
checking version-baseband...
OKAY [ 0.107s]
sending 'boot' (9156 KB)...
OKAY [ 0.541s]
writing 'boot'...
OKAY [ 0.781s]
sending 'recovery' (10016 KB)...
OKAY [ 0.603s]
writing 'recovery'...
OKAY [ 0.849s]
erasing 'system'...
OKAY [ 2.142s]
sending 'system' (1019261 KB)...
OKAY [ 37.004s]
writing 'system'...
OKAY [ 86.957s]
erasing 'userdata'...
OKAY [ 38.990s]
formatting 'userdata' partition...
Creating filesystem with parameters:
Size: 29236371456
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7137786
Block groups: 218
Reserved block group size: 1024
Created filesystem with 11/1785856 inodes and 156120/7137786 blocks
malloc: Not enough space
Cannot generate image.
FAILED ()
finished. total time: 170.121s
Press any key to exit...
Click to expand...
Click to collapse
I'm wondering if you didn't flash the img meant for the 64 and you have a 32GB? If it booted up and the system, bootloader, and radios are all updated, then nothing to be concerned about.
Can you guys please help me with this. I trying to install the system image via fastboot then i got errors like this. What did I wrong? please help
C:\Android\sdk\platform-tools>fastboot flash system C:\dell\system.img.gz
target reported max download size of 589144064 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 256451059 is not a multiple of the block size 4096
sending sparse 'system' 1/2 (575332 KB)...
error: write_sparse_skip_chunk: don't care size 256451059 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 256451059 is not a multiple of the block size 4096
OKAY [ 48.160s]
writing 'system' 1/2...
FAILED (remote: flash_cmds error!
)
finished. total time: 74.487s
Hey Guys,
i'm having a big Problem. I hard bricked a OP x.
I think there is a problem with the partitions.
I can flash recoverys. I can't flash or wipe anything in TWRP because "Failed to mount '/system' (invalid argument)".
And flashing stock OOS via fastboot is not working too.
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 280657212 is not a multiple of the block size 4096
erasing 'system'...
OKAY [ 0.172s]
sending sparse 'system' 1/2 (524284 KB)...
error: write_sparse_skip_chunk: don't care size 280657212 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 280657212 is not a multiple of the block size 4096
OKAY [ 16.890s]
writing 'system' 1/2...
FAILED (remote: buffer overreads occured due to invalid sparse header)
finished. total time: 23.014s
Any way to get it working again?
cat /proc/partitions
echoes an empty list :/
=> Mega Unbrick Guide
My Nexus 6P got stuck on a boot loop in the middle of a resource-intensive game. It was on the angler-opm6.171019.030.e1 firmware with a recent-ish version of Lineage OS.
In this state, I can get into the bootloader by keeping the volume down key pressed. However, I can't get into recovery from the bootloader, or do a factory reset, or do anything else. Choosing any option in the bootloader simply causes the phone to reboot.
However, while the bootloader is open, I am able to connect the phone to my computer via USB and run fastboot. At first I tried reflashing individual partitions like the bootloader, the vendor image, the recovery (TWRP) and eventually boot, in the hopes that reflashing one of them would fix the issue. Eventually, I downloaded the latest stock image from Google and reflashed the entire thing using the vendor-provided script:
Code:
fastboot flash bootloader bootloader-angler-angler-03.79.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-angler-angler-03.87.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-angler-opm6.171019.030.k1.zip
It was very thorough. As you can see by the mkfs, it even reformatted my storage (RIP dog pics):
Code:
$ ./flash-all.sh
Sending 'bootloader' (3552 KB) OKAY [ 0.128s]
Writing 'bootloader' OKAY [ 0.209s]
Finished. Total time: 0.366s
rebooting into bootloader OKAY [ 0.125s]
Finished. Total time: 0.126s
< waiting for any device >
Sending 'radio' (48728 KB) OKAY [ 1.303s]
Writing 'radio' OKAY [ 2.178s]
Finished. Total time: 3.512s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: angler-03.79
Baseband Version.....: angler-03.87
Serial Number........: 84B7N15A04004581
--------------------------------------------
Checking product OKAY [ 0.021s]
Checking version-bootloader OKAY [ 0.020s]
Checking version-baseband OKAY [ 0.020s]
extracting boot.img (11 MB) to disk... took 0.122s
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting recovery.img (18 MB) to disk... took 0.084s
archive does not contain 'recovery.sig'
extracting system.img (1912 MB) to disk... took 11.444s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (188 MB) to disk... took 1.259s
archive does not contain 'vendor.sig'
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6694270 4k blocks and 1676080 inodes
Filesystem UUID: b506d1ce-64e3-40fc-a7ed-cb63d08a0704
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 25600 4k blocks and 25600 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot' (12089 KB) OKAY [ 0.338s]
Writing 'boot' OKAY [ 0.181s]
Sending 'recovery' (18961 KB) OKAY [ 0.510s]
Writing 'recovery' OKAY [ 0.275s]
Sending sparse 'system' 1/5 (482664 KB) OKAY [ 12.736s]
Writing sparse 'system' 1/5 OKAY [ 7.243s]
Sending sparse 'system' 2/5 (475570 KB) OKAY [ 12.729s]
Writing sparse 'system' 2/5 OKAY [ 6.745s]
Sending sparse 'system' 3/5 (474890 KB) OKAY [ 13.047s]
Writing sparse 'system' 3/5 OKAY [ 7.821s]
Sending sparse 'system' 4/5 (476548 KB) OKAY [ 12.622s]
Writing sparse 'system' 4/5 OKAY [ 6.947s]
Sending sparse 'system' 5/5 (49108 KB) OKAY [ 1.259s]
Writing sparse 'system' 5/5 OKAY [ 0.712s]
Sending 'vendor' (192565 KB) OKAY [ 5.124s]
Writing 'vendor' OKAY [ 3.262s]
Erasing 'userdata' OKAY [ 0.326s]
Sending 'userdata' (4412 KB) OKAY [ 0.163s]
Writing 'userdata' OKAY [ 0.095s]
Erasing 'cache' OKAY [ 0.024s]
Sending 'cache' (96 KB) OKAY [ 0.032s]
Writing 'cache' OKAY [ 0.030s]
Rebooting
Finished. Total time: 106.097s
Suffice to say this didn't fix the issue. The phone is still on a boot loop.
What else is there to try?
I suspect a hardware issue but I can't run any diagnostics since fastboot doesn't give me shell access.
Thanks in advance!
Bug In Rom
joeymallone said:
My Nexus 6P got stuck on a boot loop in the middle of a resource-intensive game. It was on the angler-opm6.171019.030.e1 firmware with a recent-ish version of Lineage OS.
In this state, I can get into the bootloader by keeping the volume down key pressed. However, I can't get into recovery from the bootloader, or do a factory reset, or do anything else. Choosing any option in the bootloader simply causes the phone to reboot.
However, while the bootloader is open, I am able to connect the phone to my computer via USB and run fastboot. At first I tried reflashing individual partitions like the bootloader, the vendor image, the recovery (TWRP) and eventually boot, in the hopes that reflashing one of them would fix the issue. Eventually, I downloaded the latest stock image from Google and reflashed the entire thing using the vendor-provided script:
Code:
fastboot flash bootloader bootloader-angler-angler-03.79.img
fastboot reboot-bootloader
sleep 5
fastboot flash radio radio-angler-angler-03.87.img
fastboot reboot-bootloader
sleep 5
fastboot -w update image-angler-opm6.171019.030.k1.zip
It was very thorough. As you can see by the mkfs, it even reformatted my storage (RIP dog pics):
Code:
$ ./flash-all.sh
Sending 'bootloader' (3552 KB) OKAY [ 0.128s]
Writing 'bootloader' OKAY [ 0.209s]
Finished. Total time: 0.366s
rebooting into bootloader OKAY [ 0.125s]
Finished. Total time: 0.126s
< waiting for any device >
Sending 'radio' (48728 KB) OKAY [ 1.303s]
Writing 'radio' OKAY [ 2.178s]
Finished. Total time: 3.512s
rebooting into bootloader OKAY [ 0.005s]
Finished. Total time: 0.006s
extracting android-info.txt (0 MB) to RAM...
--------------------------------------------
Bootloader Version...: angler-03.79
Baseband Version.....: angler-03.87
Serial Number........: 84B7N15A04004581
--------------------------------------------
Checking product OKAY [ 0.021s]
Checking version-bootloader OKAY [ 0.020s]
Checking version-baseband OKAY [ 0.020s]
extracting boot.img (11 MB) to disk... took 0.122s
archive does not contain 'boot.sig'
archive does not contain 'dtbo.img'
archive does not contain 'dt.img'
archive does not contain 'odm.img'
archive does not contain 'product.img'
extracting recovery.img (18 MB) to disk... took 0.084s
archive does not contain 'recovery.sig'
extracting system.img (1912 MB) to disk... took 11.444s
archive does not contain 'system.sig'
archive does not contain 'vbmeta.img'
extracting vendor.img (188 MB) to disk... took 1.259s
archive does not contain 'vendor.sig'
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 6694270 4k blocks and 1676080 inodes
Filesystem UUID: b506d1ce-64e3-40fc-a7ed-cb63d08a0704
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000
Allocating group tables: done
Writing inode tables: done
Creating journal (32768 blocks): done
Writing superblocks and filesystem accounting information: done
mke2fs 1.43.3 (04-Sep-2016)
Creating filesystem with 25600 4k blocks and 25600 inodes
Allocating group tables: done
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
Sending 'boot' (12089 KB) OKAY [ 0.338s]
Writing 'boot' OKAY [ 0.181s]
Sending 'recovery' (18961 KB) OKAY [ 0.510s]
Writing 'recovery' OKAY [ 0.275s]
Sending sparse 'system' 1/5 (482664 KB) OKAY [ 12.736s]
Writing sparse 'system' 1/5 OKAY [ 7.243s]
Sending sparse 'system' 2/5 (475570 KB) OKAY [ 12.729s]
Writing sparse 'system' 2/5 OKAY [ 6.745s]
Sending sparse 'system' 3/5 (474890 KB) OKAY [ 13.047s]
Writing sparse 'system' 3/5 OKAY [ 7.821s]
Sending sparse 'system' 4/5 (476548 KB) OKAY [ 12.622s]
Writing sparse 'system' 4/5 OKAY [ 6.947s]
Sending sparse 'system' 5/5 (49108 KB) OKAY [ 1.259s]
Writing sparse 'system' 5/5 OKAY [ 0.712s]
Sending 'vendor' (192565 KB) OKAY [ 5.124s]
Writing 'vendor' OKAY [ 3.262s]
Erasing 'userdata' OKAY [ 0.326s]
Sending 'userdata' (4412 KB) OKAY [ 0.163s]
Writing 'userdata' OKAY [ 0.095s]
Erasing 'cache' OKAY [ 0.024s]
Sending 'cache' (96 KB) OKAY [ 0.032s]
Writing 'cache' OKAY [ 0.030s]
Rebooting
Finished. Total time: 106.097s
Suffice to say this didn't fix the issue. The phone is still on a boot loop.
What else is there to try?
I suspect a hardware issue but I can't run any diagnostics since fastboot doesn't give me shell access.
Thanks in advance!
Click to expand...
Click to collapse
Hi there,
Well since it's a recent firmware there might be a slight chance that it's a bug that caused your bootloop.
I think you're better of installing another custom ROM without any bugs.
If there are BUGS do tell the developers of that ROM so they will be able to fix it.
And I am 50% sure that it might not be a Hardware Issue that you are able to connect the phone onto your PC and thus the PC recognises it. But keep trying different stock versions of that phone.
If that didn't work install a updated TWRP and then load your another custom ROM on to your SD card or use ADB and flash the ROM. See if that works.
It's try install adb with Stock Rom and not completed, may be have some problem. Can you tell me how to dissolve?
unknown partition 'tz.img\tz.img'
error: cannot determine image filename for 'tz.img\tz.img'
target reported max download size of 268435456 bytes
Invalid sparse file format at header magi
erasing 'system'...
OKAY [ 1.408s]
Thank you.