Database Users

[Q] 5.0 not booting after factory image installation to lrx21t

Hi all,
I have just done a complete factory reset...which looked ok first...
Code:
mars:/tmp/google/occam-lrx21t# ./flash-all.sh
sending 'bootloader' (2264 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
sending 'radio' (45537 KB)... OKAY
writing 'radio'... OKAY
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.04
Serial Number........: 00254a42d4XXXXXX
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6348 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6892 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (809641 KB)... OKAY
writing 'system'... OKAY
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
rebooting...
mars:/tmp/google/occam-lrx21t
...but the bootlogo (flying balloons or whatever it is) stays there forever, waited 70 minutes on the first attempt, then did another factory reset ... and I am waiting again for more than 45 minutes ... what am I doing wrong? Any help is welcome.
Kind regards, mistersixt.

mistersixt said:
Hi all,
I have just done a complete factory reset...which looked ok first...
Code:
mars:/tmp/google/occam-lrx21t# ./flash-all.sh
sending 'bootloader' (2264 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
sending 'radio' (45537 KB)... OKAY
writing 'radio'... OKAY
rebooting into bootloader... OKAY
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: MAKOZ30f
Baseband Version.....: M9615A-CEFWMAZM-2.0.1701.04
Serial Number........: 00254a42d4XXXXXX
--------------------------------------------
checking product... OKAY
checking version-bootloader... OKAY
checking version-baseband... OKAY
sending 'boot' (6348 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6892 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (809641 KB)... OKAY
writing 'system'... OKAY
erasing 'userdata'... OKAY
erasing 'cache'... OKAY
rebooting...
mars:/tmp/google/occam-lrx21t
...but the bootlogo (flying balloons or whatever it is) stays there forever, waited 70 minutes on the first attempt, then did another factory reset ... and I am waiting again for more than 45 minutes ... what am I doing wrong? Any help is welcome.
Kind regards, mistersixt.
Click to expand...
Click to collapse
if possible, go to stock recovery or TWRP recovery and do factory data reset.
it does not work then, edit the flash-all.sh file and remove the last like which says fastboot -w update xxx...
Extract the zip file xxx... and move all the img files to current folder(flash-all.sh file folder).
add below lines
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
if you need userdata and cache add below lines
fastboot flash userdata userdata.img
fastboot flash cache cache.img
save the flash-all.sh file and try to boot now. it should boot with in 10 to 15mins.

moorthidaniel said:
if possible, go to stock recovery or TWRP recovery and do factory data reset.
it does not work then, edit the flash-all.sh file and remove the last like which says fastboot -w update xxx...
Extract the zip file xxx... and move all the img files to current folder(flash-all.sh file folder).
add below lines
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
if you need userdata and cache add below lines
fastboot flash userdata userdata.img
fastboot flash cache cache.img
save the flash-all.sh file and try to boot now. it should boot with in 10 to 15mins.
Click to expand...
Click to collapse
Tried that:
Code:
mars:/tmp/google/occam-lrx21t# ./flash-all.sh
sending 'bootloader' (2264 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
sending 'radio' (45537 KB)... OKAY
writing 'radio'... OKAY
rebooting into bootloader... OKAY
sending 'boot' (6348 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6892 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (809641 KB)... OKAY
writing 'system'... OKAY
sending 'userdata' (98413 KB)... OKAY
writing 'userdata'... OKAY
sending 'cache' (13424 KB)... OKAY
writing 'cache'... OKAY
mars:/tmp/google/occam-lrx21t#
I have still the same thing though, the boot logo with the jumping bubbles is there for 30 minutes ...
...damn, what is wrong with it?

mistersixt said:
Tried that:
Code:
mars:/tmp/google/occam-lrx21t# ./flash-all.sh
sending 'bootloader' (2264 KB)... OKAY
writing 'bootloader'... OKAY
rebooting into bootloader... OKAY
sending 'radio' (45537 KB)... OKAY
writing 'radio'... OKAY
rebooting into bootloader... OKAY
sending 'boot' (6348 KB)... OKAY
writing 'boot'... OKAY
sending 'recovery' (6892 KB)... OKAY
writing 'recovery'... OKAY
sending 'system' (809641 KB)... OKAY
writing 'system'... OKAY
sending 'userdata' (98413 KB)... OKAY
writing 'userdata'... OKAY
sending 'cache' (13424 KB)... OKAY
writing 'cache'... OKAY
mars:/tmp/google/occam-lrx21t#
I have still the same thing though, the boot logo with the jumping bubbles is there for 30 minutes ...
...damn, what is wrong with it?
Click to expand...
Click to collapse
It happened to me as well. After doing this way, i tried again factory data reset which worked for me.

I'm stuck with the bootloop over one hour now. Tried locking the bootloader, but didn't work. Is factory reset the only solution? Hate to lose the data...

mj56gt said:
I'm stuck with the bootloop over one hour now. Tried locking the bootloader, but didn't work. Is factory reset the only solution? Hate to lose the data...
Click to expand...
Click to collapse
Factory reset is the only solution to get out of bootloop. if you want to take backup before doing factory reset, try flashing twrp recovery and enable MTP. now take backup. Enabling lMTP does not help you, try flashing stock or any other kitkat rom and take backup and then install Lollypop.

pm_dsp_ra said:
Factory reset is the only solution to get out of bootloop. if you want to take backup before doing factory reset, try flashing twrp recovery and enable MTP. now take backup. Enabling lMTP does not help you, try flashing stock or any other kitkat rom and take backup and then install Lollypop.
Click to expand...
Click to collapse
I finally managed to get 5.0 on my Nexus-4 device by installing the latest twrp recovery and installed one of the stock stock-rom images via adb sideload.
Regards, mistersixt.

Stuck in a bootloop from restore

I've restored a back up through TWRP and now my phone is stuck in a bootloop. I can't get in TWRP either, as that bootloops too.
I think the issue is that I've restored a vendor image. How can I fix this if I can't get into recovery?
Can someone please help me here?

I would go into Heisenberg's guide which is stickied in the general section. Flash stock images and TWRP via fast boot. Read the guide in its entirety.

Random Barnics said:
I've restored a back up through TWRP and now my phone is stuck in a bootloop. I can't get in TWRP either, as that bootloops too.
I think the issue is that I've restored a vendor image. How can I fix this if I can't get into recovery?
Can someone please help me here?
Click to expand...
Click to collapse
Your phone shouldn't loop from restoring a vendor image, as long as it's the right vendor image that was backed up with the ROM. Exactly what did you backup/restore? You haven't really given enough information here.

I was running Dirty Unicorns 6.0.1. When I backed it up, I checked all of the extra parts to back up. I restored everything.

Random Barnics said:
I was running Dirty Unicorns 6.0.1. When I backed it up, I checked all of the extra parts to back up. I restored everything.
Click to expand...
Click to collapse
When I asked exactly what you backed up, I did mean exactly. When you say you checked all of the extra parts, what do you mean? That isn't very specific. Do you mean you checked every box? If so, you don't need to do that, you only need to select system, data, boot, and vendor. So restoring your backup and only selecting to restore those.

Heisenberg said:
When I asked exactly what you backed up, I did mean exactly. When you say you checked all of the extra parts, what do you mean? That isn't very specific. Do you mean you checked every box? If so, you don't need to do that, you only need to select system, data, boot, and vendor. So restoring your backup and only selecting to restore those.
Click to expand...
Click to collapse
Yeah. I checked every box, and restored everything I backed up. I think we're on the same page now

Random Barnics said:
Yeah. I checked every box, and restored everything I backed up. I think we're on the same page now
Click to expand...
Click to collapse
Alright, do what I said and only restore system, data, boot, and vendor.

Heisenberg said:
Alright, do what I said and only restore system, data, boot, and vendor.
Click to expand...
Click to collapse
As noted in the initial post, I can't do anything as neither the rom nor the recovery load,

I went with the dude's advice about flashing the rom and recovery through fastboot, and they're not working.
This is the terminal output I get when trying to flash the recovery.
[email protected]-3-11:~/Android/Sdk/platform-tools$ fastboot flash recovery twrp-3.0.0-1-angler.imgtarget reported max download size of 494927872 bytes
sending 'recovery' (16904 KB)...
OKAY [ 0.510s]
writing 'recovery'...
OKAY [ 0.246s]
finished. total time: 0.756s
It still freezes and doesn't load when I try and access it.
The following results are what I get when trying to flash a rom in fastboot
[email protected]-3-11:~/Android/Sdk/platform-tools$ fastboot flash zip DU_angler_6.0.1_20160301-2335.v10.0-OFFICIAL.zip
target reported max download size of 494927872 bytes
sending 'zip' (432013 KB)...
OKAY [ 11.485s]
writing 'zip'...
FAILED (remote: Permission denied!)
finished. total time: 11.491s

Don't flash a ROM flash Stock Images and go from there.

dratsablive said:
Don't flash a ROM flash Stock Images and go from there.
Click to expand...
Click to collapse
Ok. Why though? Not doubting your advice. Just wondering.

Random Barnics said:
Ok. Why though? Not doubting your advice. Just wondering.
Click to expand...
Click to collapse
Because you want to get your phone to boot normally. Once you can boot to stock, you can then flash TWRP, then custom rom and then only restore the /data portion of your backup.

My mistake, I missed the part where your recovery won't boot. Flash the factory images as the other fella said, that'll get your phone booting at least. Don't restore the data portion of your backup over the stock ROM though, that'll cause major problems.
PS. You can't flash ROM zips with fastboot.

Ok, cheers guys.
I've tried to flash the stock rom. It's not working. Here's the terminal results:
[email protected]-3-11:~/Android/Sdk/platform-tools$ ./flash-all.sh
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.120s]
writing 'bootloader'...
OKAY [ 0.207s]
finished. total time: 0.327s
rebooting into bootloader...
OKAY [ 0.080s]
finished. total time: 0.080s
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.265s]
writing 'radio'...
OKAY [ 2.174s]
finished. total time: 3.439s
rebooting into bootloader...
OKAY [ 0.011s]
finished. total time: 0.011s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: angler-03.51
Baseband Version.....: angler-03.61
Serial Number........: CVH7N15A25000202
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.021s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (12045 KB)...
OKAY [ 0.319s]
writing 'boot'...
OKAY [ 0.181s]
sending 'recovery' (12977 KB)...
OKAY [ 0.359s]
writing 'recovery'...
OKAY [ 0.194s]
erasing 'system'...
OKAY [ 0.046s]
sending 'system' (1966888 KB)...
FAILED (remote: data too large)
finished. total time: 1.232s
[email protected]-3-11:~/Android/Sdk/platform-tools$ reboot fastboot
reboot: Need to be root
[email protected]-3-11:~/Android/Sdk/platform-tools$ ./flash-all.sh
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.117s]
writing 'bootloader'...
OKAY [ 0.208s]
finished. total time: 0.325s
rebooting into bootloader...
OKAY [ 0.080s]
finished. total time: 0.080s
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.328s]
writing 'radio'...
OKAY [ 2.174s]
finished. total time: 3.502s
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.013s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: angler-03.51
Baseband Version.....: angler-03.61
Serial Number........: CVH7N15A25000202
--------------------------------------------
checking product...
OKAY [ 0.004s]
checking version-bootloader...
OKAY [ 0.021s]
checking version-baseband...
OKAY [ 0.020s]
sending 'boot' (12045 KB)...
OKAY [ 1.109s]
writing 'boot'...
OKAY [ 0.190s]
sending 'recovery' (12977 KB)...
OKAY [ 0.829s]
writing 'recovery'...
OKAY [ 0.194s]
erasing 'system'...
OKAY [ 0.312s]
sending 'system' (1966888 KB)...
FAILED (remote: data too large)
finished. total time: 2.823s

Random Barnics said:
Ok, cheers guys.
I've tried to flash the stock rom. It's not working. Here's the terminal results:
*snipped
Click to expand...
Click to collapse
Instead of using the flash-all script flash the images manually. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Heisenberg said:
Instead of using the flash-all script flash the images manually. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks.
I'll try again when I get up, as it's almost 2.30am here.

Heisenberg said:
Instead of using the flash-all script flash the images manually. I have instructions in my guide:
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
Thanks for your help Heisenberg. That last piece of advice got everything working perfectly

Random Barnics said:
Thanks for your help Heisenberg. That last piece of advice got everything working perfectly
Click to expand...
Click to collapse
Excellent, great to know

He probably restored boot system system image vendor vendor image data efs recovery......

dontbeweakvato said:
He probably restored boot system system image vendor vendor image data efs recovery......
Click to expand...
Click to collapse
Yeah we already established that.

Botched Nougat install; phone in boot loop

So as mentioned in the title, I am stuck in a boot loop after botching the OTA upgrade.
Here's the sequence of events thus far...
Current ROM Pure Nexus (not exactly sure which version, 6.01 something I think, but I hadn't updated it in a bit)
Backed up my ROM with TWRP
Due to the fact that I didn't read anything and got over zealous, I dirty flashed the N OTA over Pure Nexus
After dirty flashing it, N booted up and seemed to work ok until apps started crashing like crazy.
Reflashed TWRP
Restored the backup I previously made
Phone has not been working since; it just boot loops
Wiped data; still boot loops
Attempted flashing older bootloaders, radios, and vendor images back to it to no avail; still boot loops
Finally, I backed up everything on internal storage and flashed the latest factory image (MTC20F) straight from Google
STILL BOOT LOOPS
Reinstalled TWRP, wiped data a few more times... still boot loops
I am officially at a loss here. I can get into fastboot and twrp no problem, but the device won't start.
Current info:
BL: angler-03.54
Baseband: angler-03.61
Device is UNLOCKED.
Qfuse Status: Enabled
Any thoughts would be appreciated! I just want to get it into ANY working state at this point.

Do a full wipe system and vendor and everything, except efs maybe. Flash the twrp 3.0.2 then fastboot flash the factory images of that doesn't work then try to ask Heisenberg.

Done, done, and done, to no avail. Same issue, just a boot loop.

Funkwheat said:
Done, done, and done, to no avail. Same issue, just a boot loop.
Click to expand...
Click to collapse
Just put the phone back to full stock. Follow Heisenberg's guide.
Sent from my Nexus 6P using Tapatalk

Jammol said:
Just put the phone back to full stock. Follow Heisenberg's guide.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
Tried that earlier. Did it again just now following his precise instructions and still nothing. Maybe worth noting, though, that I got an error when trying to flash vendor.img. Everything else went fine. Currently not boot looping, but have been at the "Google" screen for about ten minutes.

Funkwheat said:
Tried that earlier. Did it again just now following his precise instructions and still nothing. Maybe worth noting, though, that I got an error when trying to flash vendor.img. Everything else went fine. Currently not boot looping, but have been at the "Google" screen for about ten minutes.
Click to expand...
Click to collapse
Did you wipe data with TWRP?

Heisenberg said:
Did you wipe data with TWRP?
Click to expand...
Click to collapse
I wiped it with factory recovery. I'll try again now with TWRP.

I tried..
Jammol said:
Just put the phone back to full stock. Follow Heisenberg's guide.
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I followed the guide to do full stock and I am still getting a loop between the google screen and the can't check this software for corruption screen... HELP!
Should I try locking the boot loader?

ArminasAnarion said:
I followed the guide to do full stock and I am still getting a loop between the google screen and the can't check this software for corruption screen... HELP!
Should I try locking the boot loader?
Click to expand...
Click to collapse
Noooooo! Don't lock the bootloader. If you do that you'll have no way to flash anything and will be royally screwed.

Heisenberg said:
Noooooo! Don't lock the bootloader.
Click to expand...
Click to collapse
I didnt! I realized that would probably brick it
What should i do then? I did the complete back to stock guide and still a loop :C

Heisenberg said:
Did you wipe data with TWRP?
Click to expand...
Click to collapse
I've now flashed TWRP and wiped data with it. Still no luck. Interestingly, though, I'm now getting stuck on the Google screen and not actually technically boot looping.
ArminasAnarion said:
I followed the guide to do full stock and I am still getting a loop between the google screen and the can't check this software for corruption screen... HELP!
Should I try locking the boot loader?
Click to expand...
Click to collapse
Had you flashed Nougat at any point? Not sure if you're having the same issue or not.

ArminasAnarion said:
I didnt! I realized that would probably brick it
What should i do then? I did the complete back to stock guide and still a loop :C
Click to expand...
Click to collapse
Funkwheat said:
I've now flashed TWRP and wiped data with it. Still no luck. Interestingly, though, I'm now getting stuck on the Google screen and not actually technically boot looping.
Click to expand...
Click to collapse
I really don't know what either of you should do. Wiping and flashing the factory images should fix anything on a Nexus.

Funkwheat said:
I've now flashed TWRP and wiped data with it. Still no luck. Interestingly, though, I'm now getting stuck on the Google screen and not actually technically boot looping.
Had you flashed Nougat at any point? Not sure if you're having the same issue or not.
Click to expand...
Click to collapse
Yeah I had flashed Nougat and gotten it to work. But where some root issues so I was going to go back to Pure Nexus, I wiped everything and flash MTC20F boot and radio and vendor and on reboot started having the loop

Heisenberg said:
I really don't know what either of you should do. Wiping and flashing the factory images should fix anything on a Nexus.
Click to expand...
Click to collapse
Agreed! I just went through your guide again, verbatim, this time with a TWRP data wipe beforehand and still no luck. This time everything flashed fine with the latest MTC20F images. Here's a command line transcript...
Code:
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash bootloader bootlo
ader-angler-angler-03.54.img
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.105s]
writing 'bootloader'...
OKAY [ 0.209s]
finished. total time: 0.316s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash radio radio-angle
r-angler-03.61.img
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.082s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.255s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.014s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash boot boot.img
target reported max download size of 494927872 bytes
sending 'boot' (12201 KB)...
OKAY [ 0.302s]
writing 'boot'...
OKAY [ 0.182s]
finished. total time: 0.487s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.030s]
finished. total time: 0.031s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash cache cache.img
target reported max download size of 494927872 bytes
erasing 'cache'...
OKAY [ 0.023s]
sending 'cache' (5752 KB)...
OKAY [ 0.150s]
writing 'cache'...
OKAY [ 0.106s]
finished. total time: 0.282s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash recovery recovery
.img
target reported max download size of 494927872 bytes
sending 'recovery' (13133 KB)...
OKAY [ 0.321s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.517s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash system system.img
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.397s]
sending sparse 'system' 1/5 (478162 KB)...
OKAY [ 11.178s]
writing 'system' 1/5...
OKAY [ 6.861s]
sending sparse 'system' 2/5 (482961 KB)...
OKAY [ 11.220s]
writing 'system' 2/5...
OKAY [ 7.044s]
sending sparse 'system' 3/5 (480085 KB)...
OKAY [ 11.236s]
writing 'system' 3/5...
OKAY [ 7.268s]
sending sparse 'system' 4/5 (470078 KB)...
OKAY [ 10.822s]
writing 'system' 4/5...
OKAY [ 6.593s]
sending sparse 'system' 5/5 (55832 KB)...
OKAY [ 1.353s]
writing 'system' 5/5...
OKAY [ 0.808s]
finished. total time: 74.788s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash vendor vendor.img
target reported max download size of 494927872 bytes
sending 'vendor' (185181 KB)...
OKAY [ 4.125s]
writing 'vendor'...
OKAY [ 2.974s]
finished. total time: 7.100s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>
Btw, how long at the "Google" boot screen should I be waiting before I give up on it ever booting? I've been waiting about ten minutes. I have heard 20 elsewhere, but that sounds excessive.

Well I am doing a complete wipe back to 6.0.0 (MDA89D) I will let you know if it works...

Funkwheat said:
Agreed! I just went through your guide again, verbatim, this time with a TWRP data wipe beforehand and still no luck. This time everything flashed fine with the latest MTC20F images. Here's a command line transcript...
Code:
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash bootloader bootlo
ader-angler-angler-03.54.img
target reported max download size of 494927872 bytes
sending 'bootloader' (3526 KB)...
OKAY [ 0.105s]
writing 'bootloader'...
OKAY [ 0.209s]
finished. total time: 0.316s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.007s]
finished. total time: 0.008s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash radio radio-angle
r-angler-03.61.img
target reported max download size of 494927872 bytes
sending 'radio' (48600 KB)...
OKAY [ 1.082s]
writing 'radio'...
OKAY [ 2.172s]
finished. total time: 3.255s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot reboot-bootloader
rebooting into bootloader...
OKAY [ 0.013s]
finished. total time: 0.014s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash boot boot.img
target reported max download size of 494927872 bytes
sending 'boot' (12201 KB)...
OKAY [ 0.302s]
writing 'boot'...
OKAY [ 0.182s]
finished. total time: 0.487s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot erase cache
******** Did you mean to fastboot format this ext4 partition?
erasing 'cache'...
OKAY [ 0.030s]
finished. total time: 0.031s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash cache cache.img
target reported max download size of 494927872 bytes
erasing 'cache'...
OKAY [ 0.023s]
sending 'cache' (5752 KB)...
OKAY [ 0.150s]
writing 'cache'...
OKAY [ 0.106s]
finished. total time: 0.282s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash recovery recovery
.img
target reported max download size of 494927872 bytes
sending 'recovery' (13133 KB)...
OKAY [ 0.321s]
writing 'recovery'...
OKAY [ 0.195s]
finished. total time: 0.517s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash system system.img
target reported max download size of 494927872 bytes
erasing 'system'...
OKAY [ 0.397s]
sending sparse 'system' 1/5 (478162 KB)...
OKAY [ 11.178s]
writing 'system' 1/5...
OKAY [ 6.861s]
sending sparse 'system' 2/5 (482961 KB)...
OKAY [ 11.220s]
writing 'system' 2/5...
OKAY [ 7.044s]
sending sparse 'system' 3/5 (480085 KB)...
OKAY [ 11.236s]
writing 'system' 3/5...
OKAY [ 7.268s]
sending sparse 'system' 4/5 (470078 KB)...
OKAY [ 10.822s]
writing 'system' 4/5...
OKAY [ 6.593s]
sending sparse 'system' 5/5 (55832 KB)...
OKAY [ 1.353s]
writing 'system' 5/5...
OKAY [ 0.808s]
finished. total time: 74.788s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>fastboot flash vendor vendor.img
target reported max download size of 494927872 bytes
sending 'vendor' (185181 KB)...
OKAY [ 4.125s]
writing 'vendor'...
OKAY [ 2.974s]
finished. total time: 7.100s
E:\angler-mtc20f-factory-d62de11e\angler-mtc20f>
Btw, how long at the "Google" boot screen should I be waiting before I give up on it ever booting? I've been waiting about ten minutes. I have heard 20 elsewhere, but that sounds excessive.
Click to expand...
Click to collapse
It should have booted after 10 minutes, normally. But, if is trying to encrypt it could take a very long time. Were you previously decrypted?

Just did you guide back to 6.0.0 (MDA89D) and the phone is still looping between the google screen and the "cant check for corruption screen"... Am I just bricked?? I have no idea what to even try...

I don't think so, unless that's something that happened automatically. I was on PureNexus (unsure which build).

ArminasAnarion said:
Just did you guide back to 6.0.0 (MDA89D) and the phone is still looping between the google screen and the "cant check for corruption screen"... Am I just bricked?? I have no idea what to even try...
Click to expand...
Click to collapse
Looks like you and I are having the exact same issue... We both went to today's OTA, both ended up attempting to go back, and are both in boot loop states now.... Wonder if this is an actual issue. Hope we can figure it out, cause until then I'm without a phone entirely.

so I am on pure nexus the latest build running xposed and ex kernel. How would I flash android 7..0 and not get this bootloop, if I format completely wipe my phone in twrp would that do it before I flash the ota.zip?

April update available

Changes here
https://source.android.com/security/bulletin/pixel/2018-04-01

Really stupid question here, although I'm not a total noob -> No chance to somehow flash the OTA on Android P, right? I guess P users have to wait for the DP2 for the next security update?

RichRatsch said:
Really stupid question here, although I'm not a total noob -> No chance to somehow flash the OTA on Android P, right?
Click to expand...
Click to collapse
right, no chance

Flashed it! A lot of fixes, also on battery life, especially the radio part interrests me, i got the feeling the standby on LTE was not optimal. Hope this beast will last a little longer. Can't imagine the performance got any higher with this update, this thing is blazing fast! Can find any other changes, according to the changelog there are some changes in the settings icons, but I don't see the difference with the March update.

psychomaniac82 said:
Flashed it! A lot of fixes, also on battery life, especially the radio part interrests me, i got the feeling the standby on LTE was not optimal. Hope this beast will last a little longer. Can't imagine the performance got any higher with this update, this thing is blazing fast! Can find any other changes, according to the changelog there are some changes in the settings icons, but I don't see the difference with the March update.
Click to expand...
Click to collapse
Any word on whether or not TWRP works (decrypts) with this update?

JAYNO20 said:
Any word on whether or not TWRP works (decrypts) with this update?
Click to expand...
Click to collapse
twrp and magisk are both still working.

JAYNO20 said:
Any word on whether or not TWRP works (decrypts) with this update?
Click to expand...
Click to collapse
I only booted one time with TWRP to flash ElementalX,worked fine. I rooted manually via magisk, adb, fastboot.

I can confirm decrypt in TWRP is still working for the April update as well as Magisk and even the Minit battery mod.

Anybody else have a weird issue after dirty flashing this update with an app called "0.0dip" keeps closing and making the phone completely unusable?

enzyne said:
Anybody else have a weird issue after dirty flashing this update with an app called "0.0dip" keeps closing and making the phone completely unusable?
Click to expand...
Click to collapse
Nope, everything fine and stable here. Sounds like one of your apps didn't like the update. Try booting in safe mode (hope it's still there in 8.1, never used it in 8.1 Oreo. If the problem goes away, it's one of your apps that didn't like the update. Try Google on 0.0dip and if possible remove it in safe mode.
Hope this helps to get in the right direction.

Any word on the multi touch issue being adressed yet?
Cheers
Beans

bbeanss said:
Any word on the multi touch issue being adressed yet?
Cheers
Beans
Click to expand...
Click to collapse
The word is, no fix.

bbeanss said:
Any word on the multi touch issue being adressed yet?
Cheers
Beans
Click to expand...
Click to collapse
What is the multi touch issue? I don't think I have it

Error installing April update
Anyone have an issue installing the April update? Bootloader and radio images flash fine, but get the error below when updating the image. Had to revert to the March image which installed just fine. Anyone know what the problem could be?
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.037s]
writing 'system_a' 1/4...
OKAY [ 0.002s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 15.485s]
writing 'system_a' 2/4...
OKAY [ 0.002s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 15.436s]
writing 'system_a' 3/4...
OKAY [ 0.002s]
sending sparse 'system_a' 4/4 (394220 KB)...
OKAY [ 13.486s]
writing 'system_a' 4/4...
OKAY [ 0.002s]
erasing 'system_b'...
FAILED (command write failed (Unknown error))
finished. total time: 64.115s
Thanks!

joeybobo said:
Anyone have an issue installing the April update? Bootloader and radio images flash fine, but get the error below when updating the image. Had to revert to the March image which installed just fine. Anyone know what the problem could be?
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.037s]
writing 'system_a' 1/4...
OKAY [ 0.002s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 15.485s]
writing 'system_a' 2/4...
OKAY [ 0.002s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 15.436s]
writing 'system_a' 3/4...
OKAY [ 0.002s]
sending sparse 'system_a' 4/4 (394220 KB)...
OKAY [ 13.486s]
writing 'system_a' 4/4...
OKAY [ 0.002s]
erasing 'system_b'...
FAILED (command write failed (Unknown error))
finished. total time: 64.115s
Thanks!
Click to expand...
Click to collapse
The issue seems to be that the flashing script changes from flashing to the a_slot to the b_slot.
Have you modified the flash-all script or so..?

I haven't modified anything. Downloaded the full update zip. Also made sure SDK platform tools were up to date. Reverting back to March update worked just fine.

joeybobo said:
Anyone have an issue installing the April update? Bootloader and radio images flash fine, but get the error below when updating the image. Had to revert to the March image which installed just fine. Anyone know what the problem could be?
sending sparse 'system_a' 1/4 (524284 KB)...
OKAY [ 13.037s]
writing 'system_a' 1/4...
OKAY [ 0.002s]
sending sparse 'system_a' 2/4 (524284 KB)...
OKAY [ 15.485s]
writing 'system_a' 2/4...
OKAY [ 0.002s]
sending sparse 'system_a' 3/4 (524284 KB)...
OKAY [ 15.436s]
writing 'system_a' 3/4...
OKAY [ 0.002s]
sending sparse 'system_a' 4/4 (394220 KB)...
OKAY [ 13.486s]
writing 'system_a' 4/4...
OKAY [ 0.002s]
erasing 'system_b'...
FAILED (command write failed (Unknown error))
finished. total time: 64.115s
Thanks!
Click to expand...
Click to collapse
Are you certain that you tried to flash the factory image and not the OTA? Also, are you certain that you downloaded the correct image for the Walleye, not Taimen?

DuckRuckus said:
Are you certain that you tried to flash the factory image and not the OTA? Also, are you certain that you downloaded the correct image for the Walleye, not Taimen?
Click to expand...
Click to collapse
Yep, double checked. I deleted the factory image and re downloaded it from google and it worked fine this morning. Thanks for the responses!

Can anyone provide an update on battery life? I plan on using this coupled with ElementalX kernal.
Thanks!

Is it just me, or do all of these "bug fixes" seem to only apply to the Pixel 2XL? Not just April, but nearly every month. I feel like the Pixel 2 in general has fewer flaws that need to be addressed through software updates and haven't noticed any real improvements because of it.

Recovery not support flash

Hey all,
I currently have a Sony Xperia E4g (E2003) with an unlocked bootloader, but without root. I am trying to flash twrp recovery with fastboot, However get the following:
sending 'recovery' (12108 KB)...
OKAY [ 0.391s]
writing 'recovery'...
FAILED (remote:
partition 'recovery' not support flash)
finished. total time: 0.399s
Click to expand...
Click to collapse
I know that it is possible to flash twrp on the e4g, because I did it earlier.
Thanks

Would you mind pointing me in the direction of the resources for the e4g?