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.
Related
[IOON] OPT RESET & Recovery Tool
Hi everyone,
I have created a Recovery Tool for the OPT. IOON is a OPEN SOURCE Project this mean that everyone can share ideas and develop. However if you have ideas please share.
IOON should be the (NON OFFICAL) OFFICAL Recovery Tool. It fix software bricks, wifi issues, fingerprint, imeu, simcard & bluetooth. And new features will follow.
Please note I’m a human if I do something wrong please tell me
I want that IOON should be a community Project developed for the Community by the Community
Note:
For Windows and Linux
IOON recover the partitions over fastboot
Fastboot is required !
Warning
You do this on your one risk. I’m not responsible for any damage. I’m also not responsible:
If your alarm clock is not working and you gets fired.
If you phone will get overheat
If the phone don’t turn on.
Features
1) Erase everything
2) Back to stock
2.1) Oxygen 2.1
2.2) Oxgen 3.0
3) [Auto] custom Recovery
4) Auto root
IOON erase:
Cache
Userdata & Userdata_64
System
Modem
Modemst1
Modemst2
And More
Instructions:
1) Download and install fastboot
2) Download the ZIP file
3) Extract the ZIP file
$ sudo unzip restore.zip
4) Move in the folder
$ cd restore
5) Type:
sudo chmod +x restore.sh
sudo ./restore
[now a Menu should pop up]
Select Erase
Select back to stock
Select custom recovery (please select costum recovery if something goes wrong you have access to your phone & and file storage )
Download the newest oxygen version
Reboot into recovery [Press volume button down and power button at the same time]
Connect your phone with PC
Drag and Drop the oxygen version on your phone
Go to flash
Select oxygen version and click on flash
Click on change recovery
Reboot
Done!
Solves:
Fingerprint BUG ( 50 % changes ) [If it is a software Brick]
Fix IMEU BUG
Wifi and simcard and bluetooth should now work
Fix crashes after flashing a android 6 ROM
Bugs:
Downloads
Version 1.0 Deleted
Version 1.1 :Mod Edit link removed.
Version 1.2 Uploaded soon!
Source Code
https://github.com/deltaxflux/IOON
I now my English is bad :angel:
Wrong Link....
Updated !
Or try this one http://www.mediafire.com/download/1jf67jsvlm1thr5/restore.zip
Yes it's work ! Thanks
@deltaxflux Instructions are more from linux POV.. need commands for windows..
@s_vohra I will add the Instruction soon, let me work on the windows version
Hello,
@deltaxflux
I would like to erase all partitions and recreate them from scratch.
Is it possible with this tool?
If so, how?
jukyO said:
Hello,
@deltaxflux
I would like to erase all partitions and recreate them from scratch.
Is it possible with this tool?
If so, how?
Click to expand...
Click to collapse
@deltaFlux,
used erase option.
Now my Internal storage is 9 Gb only. Solution?
jukyO said:
@deltaFlux,
used erase option.
Now my Internal storage is 9 Gb only. Solution?
Click to expand...
Click to collapse
What did u do ?
Notice: IOON will not longer developt because I'm to busy at the moement and there better reset tools out there
deltaxflux said:
What did u do ?
Notice: IOON will not longer developt because I'm to busy at the moement and there better reset tools out there
Click to expand...
Click to collapse
used Erase option.
recovered all partitions except EFS (modemst1, modemst2) - mmcblkop17 and mmcblk0p18.
I have backed up EFS through TWRP recovery, but it does not contain modemst1 and modemst2, but 'oem_stanvbk', which is mmcblk0p20.
Do you have an idea? Can I recreate mmcblkop17 and mmcblk0p18 again?
How does restore of EFS works?
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
deltaxflux said:
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
Click to expand...
Click to collapse
Link to OOS 2.2.1? Some special version or any?
Sent from my A0001 using XDA-Developers mobile app
deltaxflux said:
So u have root? Try the back to stock option -) root -) custom recovery modemst1 and modemst2 will be restored After reboot into recovery. Go to wipe -> advanced wipe -> select the partitions -> select recovery / repaire
to this twice !
After flash the oxygen 2.21 ROM. It should work if not contact me
Click to expand...
Click to collapse
Did that.
Output of tool:
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
Select your option
1) Back to stock
2) Root
3) Erase all
4) Custom recovery
5) Reboot
6) Exit
#> 1
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.048s]
finished. total time: 0.048s
******** Did you mean to fastboot format this partition?
erasing 'system'...
OKAY [ 0.490s]
finished. total time: 0.490s
erasing 'recovery'...
OKAY [ 0.028s]
finished. total time: 0.028s
******** Did you mean to fastboot format this partition?
erasing 'userdata'...
OKAY [ 1.477s]
finished. total time: 1.477s
erasing 'userdata_64'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.020s
erasing 'modem'...
OKAY [ 0.038s]
finished. total time: 0.038s
erasing 'modemst1'...
OKAY [ 0.032s]
finished. total time: 0.032s
erasing 'modemst2'...
OKAY [ 0.031s]
finished. total time: 0.031s
erasing 'recovery'...
OKAY [ 0.024s]
finished. total time: 0.024s
#########################################################
# #
# OPT [RECOVERY] 1.1 < Fluxion Is The Future > #
# by Deltax #
# #
#########################################################
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.057s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'aboot' (1024 KB)...
OKAY [ 0.057s]
writing 'aboot'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'apdp' (256 KB)...
OKAY [ 0.039s]
writing 'apdp'...
OKAY [ 0.024s]
finished. total time: 0.063s
target reported max download size of 536870912 bytes
sending 'bluetooth' (1024 KB)...
OKAY [ 0.057s]
writing 'bluetooth'...
OKAY [ 0.031s]
finished. total time: 0.087s
target reported max download size of 536870912 bytes
sending 'boot' (21165 KB)...
OKAY [ 0.531s]
writing 'boot'...
OKAY [ 0.179s]
finished. total time: 0.710s
target reported max download size of 536870912 bytes
erasing 'cache'...
OKAY [ 0.022s]
sending 'cache' (6248 KB)...
OKAY [ 0.186s]
writing 'cache'...
OKAY [ 0.072s]
finished. total time: 0.280s
target reported max download size of 536870912 bytes
sending 'config' (512 KB)...
OKAY [ 0.048s]
writing 'config'...
OKAY [ 0.026s]
finished. total time: 0.074s
target reported max download size of 536870912 bytes
sending 'ddr' (1024 KB)...
OKAY [ 0.057s]
writing 'ddr'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.077s
target reported max download size of 536870912 bytes
sending 'devinfo' (1 KB)...
OKAY [ 0.040s]
writing 'devinfo'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'dpo' (1 KB)...
OKAY [ 0.040s]
writing 'dpo'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'driver' (32768 KB)...
OKAY [ 0.800s]
writing 'driver'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.816s
target reported max download size of 536870912 bytes
sending 'fsc' (1 KB)...
OKAY [ 0.040s]
writing 'fsc'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'fsg' (1536 KB)...
OKAY [ 0.066s]
writing 'fsg'...
OKAY [ 0.034s]
finished. total time: 0.100s
target reported max download size of 536870912 bytes
sending 'hyp' (512 KB)...
OKAY [ 0.048s]
writing 'hyp'...
OKAY [ 0.028s]
finished. total time: 0.076s
target reported max download size of 536870912 bytes
sending 'hyp' (512 KB)...
OKAY [ 0.048s]
writing 'hyp'...
OKAY [ 0.027s]
finished. total time: 0.076s
target reported max download size of 536870912 bytes
sending 'keystore' (512 KB)...
OKAY [ 0.048s]
writing 'keystore'...
FAILED (remote: image is not a keystore file)
finished. total time: 0.072s
target reported max download size of 536870912 bytes
sending 'limits' (1 KB)...
OKAY [ 0.040s]
writing 'limits'...
OKAY [ 0.020s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'LOGO' (16384 KB)...
OKAY [ 0.409s]
writing 'LOGO'...
OKAY [ 0.144s]
finished. total time: 0.553s
target reported max download size of 536870912 bytes
sending 'misc' (1024 KB)...
OKAY [ 0.057s]
writing 'misc'...
OKAY [ 0.030s]
finished. total time: 0.087s
target reported max download size of 536870912 bytes
sending 'modem' (81920 KB)...
OKAY [ 1.983s]
writing 'modem'...
OKAY [ 0.626s]
finished. total time: 2.609s
target reported max download size of 536870912 bytes
sending 'msadp' (256 KB)...
OKAY [ 0.049s]
writing 'msadp'...
OKAY [ 0.026s]
finished. total time: 0.075s
target reported max download size of 536870912 bytes
sending 'oem_dycnvbk' (10240 KB)...
OKAY [ 0.268s]
writing 'oem_dycnvbk'...
OKAY [ 0.096s]
finished. total time: 0.364s
target reported max download size of 536870912 bytes
sending 'oem_stanvbk' (10240 KB)...
OKAY [ 0.269s]
writing 'oem_stanvbk'...
OKAY [ 0.098s]
finished. total time: 0.368s
target reported max download size of 536870912 bytes
sending 'param' (1024 KB)...
OKAY [ 0.057s]
writing 'param'...
OKAY [ 0.035s]
finished. total time: 0.092s
target reported max download size of 536870912 bytes
sending 'persist' (32768 KB)...
OKAY [ 0.800s]
writing 'persist'...
OKAY [ 0.261s]
finished. total time: 1.061s
target reported max download size of 536870912 bytes
sending 'pmic' (128 KB)...
OKAY [ 0.039s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'pmic' (128 KB)...
OKAY [ 0.039s]
writing 'pmic'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'reserve1' (8096 KB)...
OKAY [ 0.214s]
writing 'reserve1'...
OKAY [ 0.097s]
finished. total time: 0.311s
target reported max download size of 536870912 bytes
sending 'reserve2' (16192 KB)...
OKAY [ 0.410s]
writing 'reserve2'...
OKAY [ 0.138s]
finished. total time: 0.547s
target reported max download size of 536870912 bytes
sending 'rpm' (500 KB)...
OKAY [ 0.048s]
writing 'rpm'...
OKAY [ 0.027s]
finished. total time: 0.075s
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 0.688s]
writing 'recovery'...
OKAY [ 0.232s]
finished. total time: 0.921s
target reported max download size of 536870912 bytes
sending 'sbl1' (1024 KB)...
OKAY [ 0.057s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'sbl1' (1024 KB)...
OKAY [ 0.057s]
writing 'sbl1'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
error: cannot load 'sdi.img': No such file or directory
target reported max download size of 536870912 bytes
sending 'sec' (128 KB)...
OKAY [ 0.039s]
writing 'sec'...
OKAY [ 0.023s]
finished. total time: 0.062s
target reported max download size of 536870912 bytes
sending 'ssd' (8 KB)...
OKAY [ 0.040s]
writing 'ssd'...
OKAY [ 0.021s]
finished. total time: 0.060s
target reported max download size of 536870912 bytes
sending 'tz' (1024 KB)...
OKAY [ 0.057s]
writing 'tz'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
sending 'tz' (1024 KB)...
OKAY [ 0.057s]
writing 'tz'...
OKAY [ 0.031s]
finished. total time: 0.088s
target reported max download size of 536870912 bytes
erasing 'userdata'...
OKAY [ 0.223s]
sending 'userdata' (510526 KB)...
OKAY [ 12.347s]
writing 'userdata'...
OKAY [ 3.906s]
finished. total time: 16.477s
target reported max download size of 536870912 bytes
sending 'userdata_64' (515143 KB)...
OKAY [ 12.662s]
writing 'userdata_64'...
FAILED (remote: partition table doesn't exist)
finished. total time: 12.678s
So those 5 failed:
erasing 'userdata'...
OKAY [ 1.477s]
finished. total time: 1.477s
erasing 'userdata_64'...
FAILED (remote: Partition table doesn't exist
)
finished. total time: 0.020s
sending 'ddr' (1024 KB)...
OKAY [ 0.057s]
writing 'ddr'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.077s
target reported max download size of 536870912 bytes
writing 'driver'...
FAILED (remote: partition table doesn't exist)
finished. total time: 0.816s
target reported max download size of 536870912 bytes
writing 'keystore'...
FAILED (remote: image is not a keystore file)
finished. total time: 0.072s
target reported max download size of 536870912 bytes
writing 'userdata_64'...
FAILED (remote: partition table doesn't exist)
finished. total time: 12.678s
After reboot to recovery, under wipe-advance wipe there is:
Dalvik
System
Data
Internal Storage
Cache
If I try to mount system, cannot do it.
Internal storage shows 9 Gb.
Do you have another ideas?
Thanks!
Just reset it with Qualcomm tool
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
[
omrij said:
Just reset it with Qualcomm tool
http://forum.xda-developers.com/oneplus-2/general/guide-official-stock-reset-to-oos-2-2-0-t3290707
[
Click to expand...
Click to collapse
Did that 1st. Removed tampered bit before the procedure. No go.
Still
oem_nv_backup the nv partition is invalid
is shown.
Anyone knows how to check if modemst1 modemst2 blocks/partitions are created properly?
Will this erase internal storage too?
I want to use this tool because my FP sensor isnt working so i wanna give it a try
LOL9988 said:
Will this erase internal storage too?
I want to use this tool because my FP sensor isnt working so i wanna give it a try
Click to expand...
Click to collapse
It'll wipe everything, but I wouldn't use it because some of your partitions don't need to be wiped and some of the fastboot commands in the restore.sh file are wrong and will cause issues
For example:
sudo fastboot flash userdata userdata.img will flash the 16GB version's userdata.img even if you have a 64GB version of the phone.
sudo fastboot flash userdata_64 userdata_64G.img won't work because there is no userdata_64 partition - it's called userdata on both versions.
TBH, you're better off using advanced wipe in TWRP to wipe internal storage.
Waiting for the windows version to see if this app do the miracle fixing the second IMEI number on my phone, I tried everything already. Thanks for make this app.
Sent from my unknown using Tapatalk
iam newbie and want to try this solution to repair my fingerprint how to?
BEWARE, DO NOT SELECT ERASE OR IT WILL ERASE ALL YOUR MODEMS AND WONT BE ABLE TO GET THEM BACK. MY PHONE'S IMEIs ARE BROKEN. BOTH IMEI SHOW 0 AND CANNOT CONNECT MY PHONE TO ANY CELLPHONE COMPANY
Phone started to loop through booting, crashes at different points of booting. Preformed a wipe data/factory reset and is doing the same loop though booting. Last ditch effort i want to try flashing but looks like i can't as it's locked any ideas?
error = FAILED (remote: device is locked. Cannot flash images)
bullhead LGH791 16GB
HW Version - rev_1.0
Bootloader version BHZ11m
Baseband Version - M8994F-2.6.37.2.21
Carrier info - N/A
Signing - production
Secure boot - enabled
Device - State - locked
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'bootloader' (4616 KB)...
OKAY [ 0.180s]
writing 'bootloader'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.210s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'radio' (56630 KB)...
OKAY [ 1.300s]
writing 'radio'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.330s
rebooting into bootloader...
OKAY [ 0.020s]
finished. total time: 0.020s
< waiting for any device >
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
wiping userdata...
Creating filesystem with parameters:
Size: 11773390848
Block size: 4096
Blocks per group: 32768
Inodes per group: 8176
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 2874363
Block groups: 88
Reserved block group size: 703
Created filesystem with 11/719488 inodes and 84965/2874363 blocks
wiping cache...
Creating filesystem with parameters:
Size: 100663296
Block size: 4096
Blocks per group: 32768
Inodes per group: 6144
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 24576
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6144 inodes and 1422/24576 blocks
--------------------------------------------
Bootloader Version...: BHZ11m
Baseband Version.....: M8994F-2.6.37.2.21
Serial Number........: 00bf02fa89e421b5
--------------------------------------------
checking product...
OKAY [ 0.020s]
checking version-bootloader...
OKAY [ 0.010s]
checking version-baseband...
OKAY [ 0.010s]
sending 'boot' (12045 KB)...
OKAY [ 0.341s]
writing 'boot'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.501s
Press any key to exit...
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.
Meant to say bootloader said recovery big difference LOL I have the same issue with Pixel experience,Lineage,omni rom there are no errors in terminal or on phone here is the output from my terminal window i just find it odd any answers would be much appreciated thanks.
fastboot flash boot /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-20
200918-0058-UNOFFICIAL/boot.img *
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ *1.795s]
writing 'boot_a'...
OKAY [ *0.506s]
finished. total time: 2.301s
fastboot flash system /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-
20200918-0058-UNOFFICIAL/system.img *
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 14.571s]
writing 'system_a' 1/2...
OKAY [ *2.775s]
sending sparse 'system_a' 2/2 (473856 KB)...
OKAY [ 12.986s]
writing 'system_a' 2/2...
OKAY [ *2.572s]
finished. total time: 32.905s
fastboot flash product /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0
-20200918-0058-UNOFFICIAL/product.img *
target reported max download size of 536870912 bytes
sending sparse 'product_a' 1/3 (524284 KB)...
OKAY [ 14.380s]
writing 'product_a' 1/3...
OKAY [ *2.776s]
sending sparse 'product_a' 2/3 (524284 KB)...
OKAY [ 14.388s]
writing 'product_a' 2/3...
OKAY [ *2.841s]
sending sparse 'product_a' 3/3 (167696 KB)...
OKAY [ *4.603s]
writing 'product_a' 3/3...
OKAY [ *1.170s]
finished. total time: 40.157s
fastboot flash vbmeta /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-
20200918-0058-UNOFFICIAL/vbmeta.img *
target reported max download size of 536870912 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ *0.001s]
writing 'vbmeta_a'...
OKAY [ *0.058s]
finished. total time: 0.058s
fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ *0.069s]
finished. total time: 0.069s
Weeaboodesu said:
Meant to say bootloader said recovery big difference LOL I have the same issue with Pixel experience,Lineage,omni rom there are no errors in terminal or on phone here is the output from my terminal window i just find it odd any answers would be much appreciated thanks.
fastboot flash boot /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-20
200918-0058-UNOFFICIAL/boot.img *
target reported max download size of 536870912 bytes
sending 'boot_a' (65536 KB)...
OKAY [ *1.795s]
writing 'boot_a'...
OKAY [ *0.506s]
finished. total time: 2.301s
fastboot flash system /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-
20200918-0058-UNOFFICIAL/system.img *
target reported max download size of 536870912 bytes
sending sparse 'system_a' 1/2 (524284 KB)...
OKAY [ 14.571s]
writing 'system_a' 1/2...
OKAY [ *2.775s]
sending sparse 'system_a' 2/2 (473856 KB)...
OKAY [ 12.986s]
writing 'system_a' 2/2...
OKAY [ *2.572s]
finished. total time: 32.905s
fastboot flash product /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0
-20200918-0058-UNOFFICIAL/product.img *
target reported max download size of 536870912 bytes
sending sparse 'product_a' 1/3 (524284 KB)...
OKAY [ 14.380s]
writing 'product_a' 1/3...
OKAY [ *2.776s]
sending sparse 'product_a' 2/3 (524284 KB)...
OKAY [ 14.388s]
writing 'product_a' 2/3...
OKAY [ *2.841s]
sending sparse 'product_a' 3/3 (167696 KB)...
OKAY [ *4.603s]
writing 'product_a' 3/3...
OKAY [ *1.170s]
finished. total time: 40.157s
fastboot flash vbmeta /home/no/pixelimages/PixelExperience_Plus_sofiar-10.0-
20200918-0058-UNOFFICIAL/vbmeta.img *
target reported max download size of 536870912 bytes
sending 'vbmeta_a' (4 KB)...
OKAY [ *0.001s]
writing 'vbmeta_a'...
OKAY [ *0.058s]
finished. total time: 0.058s
fastboot -w
wiping userdata...
Erase successful, but not automatically formatting.
File system type raw not supported.
erasing 'userdata'...
OKAY [ *0.069s]
finished. total time: 0.069s
Click to expand...
Click to collapse
mine is doing the same thing, ever figure out what the cause is?
CorporalCactus said:
mine is doing the same thing, ever figure out what the cause is?
Click to expand...
Click to collapse
No i found a custom rom that worked keep trying roms till you find one that works havoc os worked for me and make sure you are flashing in fastbootd
Hllo, friends. This new RAW Firmware Android 11,
WW_ZS661KS_18.0410.2108.158_M3.35.19.17-ASUS_1.1.5_Phone-user.raw.zip
Thanks
rn777 said:
Hllo, friends. This new RAW Firmware Android 11,
WW_ZS661KS_18.0410.2108.158_M3.35.19.17-ASUS_1.1.5_Phone-user.raw.zip
Click to expand...
Click to collapse
so is this a full rom adb sideloadable with GAPPS ??
rn777 said:
Hllo, friends. This new RAW Firmware Android 11,
WW_ZS661KS_18.0410.2108.158_M3.35.19.17-ASUS_1.1.5_Phone-user.raw.zip
Click to expand...
Click to collapse
stuck in bootloop now, how can i get a working phone again ?
./zs661ks_raw_flashall.sh
mkdir: cannot create directory ‘f2fs_win’: File exists
mv: cannot stat 'make_f2fs.exe': No such file or directory
mv: cannot stat 'mke2fs.exe': No such file or directory
[FLASH_RAW] ==========================================
[FLASH_RAW] ZS661KS raw flashing program
[FLASH_RAW] Version 20210118
[FLASH_RAW] ==========================================
[FLASH_RAW] RAW file found: WW_ZS661KS_18.0410.2108.158_M3.35.19.17-ASUS_1.1.5_Phone-user.raw
[FLASH_RAW] Please connect device to host.
[FLASH_RAW][ERROR] Fail to get device information!
[ERROR] FAILED!
FAILED (remote: 'Command not supported in default implementation')
fastboot: error: Command failed
[ERROR] disable flashing!!!
Sending sparse 'super' 1/12 (476740 KB) OKAY [ 11.906s]
Writing 'super' OKAY [ 0.821s]
Sending sparse 'super' 2/12 (505048 KB) OKAY [ 12.536s]
Writing 'super' OKAY [ 0.865s]
Sending sparse 'super' 3/12 (460248 KB) OKAY [ 11.490s]
Writing 'super' OKAY [ 0.826s]
Sending sparse 'super' 4/12 (524184 KB) OKAY [ 13.062s]
Writing 'super' OKAY [ 0.885s]
Sending sparse 'super' 5/12 (524256 KB) OKAY [ 13.107s]
Writing 'super' OKAY [ 0.892s]
Sending sparse 'super' 6/12 (524256 KB) OKAY [ 13.000s]
Writing 'super' OKAY [ 0.880s]
Sending sparse 'super' 7/12 (521716 KB) OKAY [ 12.877s]
Writing 'super' OKAY [ 0.922s]
Sending sparse 'super' 8/12 (508516 KB) OKAY [ 12.614s]
Writing 'super' OKAY [ 0.888s]
Sending sparse 'super' 9/12 (524248 KB) OKAY [ 13.036s]
Writing 'super' OKAY [ 0.882s]
Sending sparse 'super' 10/12 (476844 KB) OKAY [ 11.881s]
Writing 'super' OKAY [ 0.856s]
Sending sparse 'super' 11/12 (511336 KB) OKAY [ 12.722s]
Writing 'super' OKAY [ 0.900s]
Sending sparse 'super' 12/12 (398572 KB) OKAY [ 9.933s]
Writing 'super' OKAY [ 0.722s]
Finished. Total time: 158.511s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.251s
(bootloader) bat vol = 3975
OKAY [ 0.001s]
Finished. Total time: 0.002s
Erasing 'metadata' OKAY [ 0.065s]
Finished. Total time: 0.072s
******** Did you mean to fastboot format this f2fs partition?
Erasing 'userdata' OKAY [ 0.199s]
Finished. Total time: 0.205s
Erasing 'userdata' OKAY [ 0.181s]
F2FS-tools: mkfs.f2fs Ver: 1.12.0 (2018-11-12)
Info: Disable heap-based policy
Info: Debug level = 1
Info: Trim is disabled
Info: Set conf for android
Info: No support kernel version!
Info: Segments per section = 1
Info: Sections per zone = 1
Info: sector size = 512
Info: total sectors = 217925272 (106408 MB)
Info: zone aligned segment0 blkaddr: 512
Info: add quota type = 0 => 4
Info: add quota type = 1 => 5
[f2fs_init_sit_area: 535] Filling sit area at offset 0x00600000
[f2fs_init_nat_area: 569] Filling nat area at offset 0x00e00000
[f2fs_write_root_inode:1147] Writing root inode (hot node), 1c600 0 200 at offset 0x00116224
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001cc01, 0001cc02
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c600 0 200 at offset 0x00116225
[f2fs_write_default_quota:1223] Writing quota data, at offset 0001cc03, 0001cc04
[f2fs_write_qf_inode:1318] Writing quota inode (hot node), 1c600 0 200 at offset 0x00116226
[f2fs_update_nat_root:1372] Writing nat root, at offset 0x00000e00
[f2fs_add_default_dentry_root:1567] Writing default dentry root, at offset 0x0001cc00
Info: Overprovision ratio = 0.610%
Info: Overprovision segments = 656 (GC reserved = 335)
[f2fs_write_check_point_pack: 713] Writing main segments, cp at offset 0x00000200
[f2fs_write_check_point_pack: 850] Writing Segment summary for HOT/WARM/COLD_DATA, at offset 0x00000201
[f2fs_write_check_point_pack: 877] Writing Segment summary for HOT_NODE, at offset 0x00000202
[f2fs_write_check_point_pack: 889] Writing Segment summary for WARM_NODE, at offset 0x00000203
[f2fs_write_check_point_pack: 900] Writing Segment summary for COLD_NODE, at offset 0x00000204
[f2fs_write_check_point_pack: 908] Writing cp page2, at offset 0x00000205
[f2fs_write_check_point_pack: 928] Writing NAT bits pages, at offset 0x000003fe
[f2fs_write_check_point_pack: 949] Writing cp page 1 of checkpoint pack 2, at offset 0x00000400
[f2fs_write_check_point_pack: 968] Writing cp page 2 of checkpoint pack 2, at offset 0x00000405
[f2fs_write_super_block:1001] Writing super block, at offset 0x00000000
Info: format successful
Sending 'userdata' (85 KB) OKAY [ 0.007s]
Writing 'userdata' OKAY [ 0.003s]
Erasing 'metadata' OKAY [ 0.057s]
Erase successful, but not automatically formatting.
File system type raw not supported.
Finished. Total time: 5.910s
Rebooting FAILED (Status read failed (No such device))
fastboot: error: Command failed
LOLZ nevermind, im an idiot.... its fixed