Develop Bugs

[Q] Cannot get out of boot animation nor flash by odin or fastboot - Help please

Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!

jhonnyx said:
Hi everyone, I'm new here and I have a GNex on my hands.
While I received it to fix; I could not get it past a bootloop from the nexus 4.0.4 Boot.
Problem is I cannot seem to get past the boot animation screen nor upgrade it.
Tried flashing another bootloader via fastboot, and the bootloader does not change, stays in same version.
HW Version : 9
Bootloader version : PRIMEKK15
Baseband version : I9250XXKK6
I proceed doing a fastboot erase bootloader and trying another bootloader, rebooting into another bootloader but no luck
Tried also ODIN flash but no luck; stays into the same
Booting into recovery mode goes into stock recovery and tries to flash a file from /cache
By trying to flash CWM via fastboot flash recovery <cwm image> flashes image but no luck on booting into CWM.
Anbody can lend a hand please?
Thanks!
Click to expand...
Click to collapse
You can flash a custom recovery like cwm or twrp. Then you can acces the custom recovery and adb push your ROM and gapps. Then you do the wipes and flash the ROM and gapps. If you dont understand anything you just have to tell me
Sent from my Galaxy Nexus using XDA Premium HD app

Thanks mrgnex. I've tried flashing TWRP, but the only thing it does is boot into stock recovery and tries to flash a file from /cache/, which file is: 5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip; pretty weird. Issue is the same as this thread: http://forum.xda-developers.com/showthread.php?t=1909331&page=4

use: fastboot boot recovery.img

and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?

doesnt matter. whichever.

jhonnyx said:
and "recovery.img" which recovery do you suggest? twrp or a CWM in particular?
Click to expand...
Click to collapse
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?

TheMysteriousOne said:
I suggest the latest TWRP.
http://www.teamw.in/project/twrp2
Edit: Have you read this?
Click to expand...
Click to collapse
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.

jhonnyx said:
While now I'm trying to install latest TWRP (already did and no luck) I'm downloading the pack from the "Have you read this?".
The things that I'm seeing right now that seem to be wrong are:
1 - everytime I reboot the phone, the "fastboot oem unlock" seems to be gone and phone re-locks again (weird!)
2 - every change I make to the filesystem, seems to be non-persistent I/E: push something via adb push and on reboot it's gone! :/
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Can you elaborate on why exactly you were not able to install TWRP?

TheMysteriousOne said:
Can you elaborate on why exactly you were not able to install TWRP?
Click to expand...
Click to collapse
Surely:
1 - Unlock via fastboot oem unlock
2 - fastboot erase recovery (exits with ok)
3 - fastboot flash recovery twrp_versiondoesnotmatter.img (exits with ok)
4 - reboot w/power+vlup+voldown and select reboot recovery
5 - stock recovery appears
an alternate method that i've tried:
1 - Unlock via fastboot oem unlock
2 - fastboot boot twrp_versiondoesnotmatter.img (exits with ok)
3 - TWRP boots and flashes a zipfile from /cache/ then reboots automatically
That's what happens. A mistery, huh?
Also I've tried OMAP Flash, and; the same issue happens over and over again

Have you tried doing a factory reset using the stock recovery?

TheMysteriousOne said:
Have you tried doing a factory reset using the stock recovery?
Click to expand...
Click to collapse
AFAIK, Yes
What happens once I start the stock recovery; as I've already stated; starts flashing a zip file located into /cache/ (5a81769b6d01.signed-yakju-IMM76I-from-ICL53F.5a81769b.zip); then bleh, starts the bootloop again.
I've tried the power+volup then selected wipe cache and wipe system and it's the same.

Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app

$Parker said:
Did you try flash google's stock images (all of them) ?
Also try flashing TWRP in the boot (kennel) partition by :-
Code:
fastboot flash boot <path to twrp>.img
This will force the phone into Recovery (But you will have recovery bootloop , can be solved by flashing a kernel) .
when you boot into recovery install a Kernel and ROM . also you will lose the recovery after that .
You can flash the TWRP from the TWRP itself (to put it in the right partition) by (in the build in terminal) :-
Code:
dd if=/<path to twrp in SD>.img of=/dev/block/mmcblk0p8
Good Luck .
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
fastboot flash boot <path to twrp>.img does not boot the recovery . I mean; still boots the normal Kernel.
Actually I'm trying what TheMysteriousOne told me by downloading the stock Gnex zip (250Mb) to flash via Odin.

Ohh, bad luck strikes again:
<ID:0/011> system.img
<ID:0/011> Complete(Write) operation failed.
cannot write system.img :/
Any ideas?

Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.

beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?

beekay201 said:
Unlock your bootloader with omapflash. Although even if it does unlock, Your emmc/board probably has died.
a manta wrote this.
Click to expand...
Click to collapse
Pardon me, if EMMC/Board is dead; why does it boot or get into bootloop? There is something that reflashes itself; it even overrides odin or heimdall...

Have you tried going back to completely stock using the method outlined here? http://forum.xda-developers.com/showthread.php?t=1626895

jhonnyx said:
can you please me guide how to do the omapflash?
I've downloaded a file called OMAPFlash_tuna.zip.
- Set battery of the device aside
- Plug device into USB, let it detect the device and flash the SBF I think.
That'd be all?
Click to expand...
Click to collapse
Read this thread
http://forum.xda-developers.com/showthread.php?t=2016628
a manta wrote this.

[Q] HELP! Stuck in TWRP boot loop!

Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!

Try flashing the recovery again. Download it from the link provided here and confirm the md5 checksum for the zip file.
http://forum.xda-developers.com/showthread.php?t=2694564
Sent from my HTC One_M8 using XDA Premium 4 mobile app

PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
some reason doing twrp from terminal on hte m8 gets us stuck (it did for me at least.)
just reflash the insecure boot image.. fastboot flash boot blah.img
that should get you back up

PirateP3t3 said:
Howdy Everyone,
So just tried rooting my new m8 and now I'm stuck endlessly booting into TWRP. I thought I did everything correctly: Unlocked the bootloader, installed the USB drivers, installed the ADB fastboot drivers and then flashed twrp 2.7.0.3. I get to the the htc logo screen/warning and, bam, back to twrp everytime.
Does anyone know how to fix this??? The last time i was rooting and installing custom mods was back in samsung galaxy s2 days, so my knowledge is a little dated. Please help!!
Click to expand...
Click to collapse
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having

darll said:
I encountered this issue as well. I'm almost certain that when you were flashing recovery, you used this command "fastboot flash boot recovery.img".
The right command should be "fastboot flash recovery recovery.img".
To rectify the issue look for a tread that has the boot.img for your specific M8 model and flash boot back using " fastboot flash boot boot.img".
This should fix the issue you are having
Click to expand...
Click to collapse
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!

PirateP3t3 said:
Forgot to come back and update this thread, but this is exactly what I did and it worked!!! Now happily rooted and running.
Thanks for the help!
Click to expand...
Click to collapse
I followed the instructions on the TWRP site:
Download the above file. Save it to the root of your /sdcard directly (internal memory only) and rename it to twrp.img
Launch terminal emulator or connect to your computer and open an adb shell, then type the following:
su
dd if=/sdcard/twrp.img of=/dev/block/mmcblk0p43
Then reboot to complete installation.
But that left me in a TWRP bootloop. Can you please give me step by step instructions on how to get out of this bootloop?
Thanks!

First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, then swipe for a factory reset (Advanced wipe cannot properly wipe cache and dalvik after fastboot erase cache)
then go to advanced, select cache, dalvik and system and swipe to wipe those partitions.
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.

exad said:
First off, being a noob and using dd without even knowing what partiton you're writing to is extremely dangerous.
Just use fastboot.
plug phone into PC in fastboot mode.
Code:
fastboot flash recovery twrpfilename.img
fastboot erase cache
on phone go back to hboot, select, recovery
In TWRP go to wipe, advanced, select cache, dalvik and system
then go to install, select the rom on your phone and flash. follow on screen instructions.
If you don't have the rom on your phone for whatever reason,
connect your phone, while in TWRP to your PC then, using adb on your PC
Code:
adb push romfilename.zip /sdcard/
Wait until it completes with bytes sent.
Then flash using method listed above.
Be careful if you want to keep your phone. I stress this, if you don't know what a command you are issuing does, exactly, DO NOT DO IT until you look it up and understand what you are doing. There is great risk even when you know what you're doing. There's a LOT more when you don't.
Click to expand...
Click to collapse
Thanks for the detailed instructions. I opened fastboot on my PC with phone plugged in and entered the code but the cmd prompt just says <waiting for device>

Do you have the HTC drivers installed on your PC with HTC sync uninstalled?
Does it say fastboot USB on your phone?
Sent from my HTC One_M8 using xda app-developers app

Update: I ended up just installing the Viper ROM and the system rebooted fine. It's strange that I couldn't reboot the device to get out of recovery without having to install a custom ROM.
Sent from my HTC6525LVW using Tapatalk

No it's not. You flashed recovery to the boot partition.
Sent from my HTC One_M8 using xda app-developers app

How do i fix TWRP Bootloop on my HTC explorer a310e... ?
How do i fix TWRP Bootloop on my HTC explorer a310e... ?
I hav custom cm11 Kitkat ROM installed on it...
but after I installed the rom, and again tried to reboot
into TWRP recovery, it is just stuck on the blue color
TEAMWIN screen... Please help how to fix it...!

HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.

Maxxour said:
HELP PLEASE
I pressed factory reset on my cm13 rom htc one m8 with twrp and now its just stuck flashing the teamwin logo and i cant do anything, i tried using fastboot but it cant see the device.
Click to expand...
Click to collapse
You need cwm recovery to factory reset from cm roms.
Also you need to be in FASTBOOT mode for it to detect your device.
Boot to fastboot, erase cache, reinstall twrp.
Next time reset/wipe from recovery.

ashyx said:
You need cwm recovery to factory reset from cm roms.
Click to expand...
Click to collapse
cwm recovery or cm recovery?

Soft bricked

Hello everyone, today I installed TWRP recovery, it went fine and I am not new to install custom roms, custom recoveries, etc. but this got my phone messed up. It was working perfectly fine and then I turned it off in the night and in the morning, it just got stuck in a bootloop, and knowing me of course, I forgot to create a backup as I installed TWRp. So, is there any kind fellow out there that has a TWRP backup at hand for the ZE551ML?

Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?

Harfainx said:
Just to get the order correct...
Flashed TWRP - No problem
Rebooted to system - No problem
System worked?
Turned off phone
Bootloop on power on?
Is this a bootloop, or does it just sit on the Asus screen? Does it get to the actual boot animation, or are you on the splash screen?
Click to expand...
Click to collapse
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.

Lurkingintheshadows said:
I am getting to the boot animation with the gears turning and then error comes up and boots me into TWRP. The problem is, the Bootloader will not come up so I can do the fastboot flashing, TWRP comes up instead. It comes up and I didn't overwrite the bootloader with TWRP. Problem is I can't access fastboot commands.
Click to expand...
Click to collapse
Give me a few minutes. I'll get you a TWRP flashable boot.img zip.

Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.

Harfainx said:
Try flashing this in TWRP. You might need to sideload it onto your phone if you can't boot into system.
Click to expand...
Click to collapse
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.

Lurkingintheshadows said:
Thank you. But, it won't flash, I've tried about every option now. I think I'm just going to see if I can get a replacement. 2.19 was always causing me problems to install and then now that I finally got it on my phone, I couldn't install another 2.19 on top of it or downgrade. Guess this phone is done for until CM12 gets released. Thanks for the help but it seems it can't be recovered at this point.
Click to expand...
Click to collapse
If you lurk on these forums, there are some Intel flashing tools I've seen that can help you recover from a soft brick.

I am stuck too!
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied

I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting. It got stuck on bootloop. phone is asus zenfone 2 Z00A. It is intel chipset. please help me out.
the worst part is that i cant get into fastboot or recovery modes so i am completely stuck! please help me out.
when i try to get into fastboot mode with vol up+ power key it vibrates but nothing is displayed.
if i just power it on its stuck on bootloop.
i can't get into recovery and fastboot bcoz its at the same place.
can i use adb commands or fastboot commands somehow?
i can maybe use adb reboot recovery to get into recovery and then i can do a wipe and flash new stuff.
please help me out.
UPDATE: I found out u can use adb reboot recovery while on the asus bootanimation.
i tried adb reboot recovery and now getting a flashing android sleeping bot with error!
can't use adb or fastboot commands now though
now in even bigger mess. after using adb reboot recovery, i can't get to bootanimation either.
just stuck at flashing android sleeping bot with error.
can't get to bootloader or fastboot or anything!
Please any suggestions. I'm dying here to fix it.
I have a adb backup.
i couldn't take a nandroid backup. i just entred recovery and wiped cache first. after doing that i was going to flash twrp and then using twrp take a nandroid backup and flash a custom rom. but it got stuck at cache wipe and i powered it off and the whole mess.:
Finally entered bootloader with fastboot now working!
Content and satisfied
Click to expand...
Click to collapse
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"

I_am_sid said:
I was in stock recovery and did a cache wipe. It took forever and wouldn't come out of it so i powered it off and tried booting.
Click to expand...
Click to collapse
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:

I shut mine down because it took too long. Wouldn't start up again. Had to send it in for RMA. Asus Canada reset the OS. I'll never do that again.
Sent from my ASUS_Z00AD using XDA-Developers mobile app

ikkuy said:
how did you get fastboot working? I can get into bootloader, but cant get my pc to connect with my zenfone2. can't use any adb cmd it would just say "error: can't find devices"
Click to expand...
Click to collapse
Dude you can never use adb when in bootloader.
That's why you have fastboot.
just type
fastboot devices
you will get your device.
if you don't then download intel drivers. You will get them in asus website.
if you are stuck without custom recovery i would suggest you to download system image (~1.5Gb) from asus website.
just search for asus zenfone 2 and go to official asus site. in downloads tab you should find both drivers and system image.
download the latest one.
See if you can get into stock recovery.
when in bootloader press vol down and go to recovery mode.
you will see a sleeping android bot with error.
press power key + vol down you will get a list.
choose factory reset and then after wipe is complete choose sideload from adb.
connect your phone and then in adb type
adb sideload filename.zip
obviously place file in your platform-tools folder and replace filename with whatever its name is.
it will take a while and you will get back your system.
---------- Post added at 07:37 PM ---------- Previous post was at 07:21 PM ----------
Marteicos said:
Just a reminder to everyone, never force shutdown the Phone during a cache wipe procedure, it takes a long time but it finishes.
When I did it on my ZF2, I thought it was taking too long, but I did a search here and found out about it taking long before it was too late.
I'm glad you could recover yours. :good:
Click to expand...
Click to collapse
Thanks!
It took a lot of time though.
For anyone stuck,
I first got fastboot working. and then i flashed stock recovery and boot.
got into stock recovery and sideloaded system img into it.
After it booted back into asus stock rom i unlocked bootloader, placed twrp in sdcard and got straight into fastboot again installed twrp and then did a wipe and went ahead and flashed ROM and Gapps. Working fine.
Update:
To get to bootloader:
i was stuck in a bootloop.
When at asus boot animation i connected USB cable and quickly typed
adb reboot bootloader
which seemed to work for me. Though i couldn't get into recovery.
So i had to flash stock recovery again.

android nougat update

I am waiting for android nougat update for a long day... When i will get it? Please answer me because i have permission to get updates for two years.. Please help me about this..

Yaaa Google had promised us to give 2 years of update.Bro wait till 4th of October if on that day the OTA will come then OK if no then theres no chance of update after that

Thank you so much..ok i will wait untill 4 otcober has come

Can't flash twrp via fastboot mode.
Actually I flash recovery twrp successfully but when I try to boot in recovery after ''fastboot reboot''' command (reboot my phone normally) and boot in recovery via fastboot mode it load stock recovery,
I tried lots of time.
Any help?
Sent from my Moto G 2014 using XDA-Developers mobile app

neeraj.lambaa said:
Can't flash twrp via fastboot mode.
Actually I flash recovery twrp successfully but when I try to boot in recovery after ''fastboot reboot''' command (reboot my phone normally) and boot in recovery via fastboot mode it load stock recovery,
I tried lots of time.
Any help?
Click to expand...
Click to collapse
I think u should use All in one tool inspite of using fastboot method.
Link http://forum.xda-developers.com/cro...-master-tool-unlock-bootloader-t2997696/page1

Bootloader - No Command Error [solved]

Here are the steps that got me to where I am.
1. Stock Pixel XL March 2017
2. Installed TWRP
3. Installed SU
4. All worked correctly for the last month
5. Saw that there was a new April release
a. It would not install as I was rooted
b. I installed the April OTA using TWRP
c. Rebooted
6. Saw that I was no longer rooted
7. Tried to go to Bootloader
8. Got dead droid with no command error
9. Went to recovery (Power + up vol) to enter sideload
10. Sideloaded the April updated
11. Rebooted
a. Same no command error
b. Went to recovery (Power + up vol) to enter factory restore
c. Rebooted
12. Tried to go into boot loader
a. Same no command error
13. Problem is that twrp was not asking for pattern And would not install correctly with image file. Solution was to keep loading the twrp image file until it asks for pattern. Then follow standard twrp /su instructions.
Thanks.

Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk

This should be posted under Q&A not development

wyrdtrtle said:
Power device off, use key combo (power+voldown) to boot bootloader. Fastboot flash stock boot.img to both slot a and b. Then reboot, take the OTA, or sideload it. Reboot. Now reboot to bootloader, fastboot boot TWRP, then reboot to twrp. Now you can flash TWRP to keep it as the recovery, or just su then reboot. Should be good.
Sent from my Pixel XL using Tapatalk
Click to expand...
Click to collapse
Bootloader does not load.

When you get the dead Droid just hit vol up, no power button.
Sent from my Pixel XL using Tapatalk

Then what?

bschatzow said:
Then what?
Click to expand...
Click to collapse
I think I know where you went wrong you installed an incremental OTA with TW RP. If I'm not mistaken that new firmware had an updated bootloader and I believe that's dangerous to do. You may be out of luck

Why would the built in factory restore fix it?

bschatzow said:
Why would the built in factory restore fix it?
Click to expand...
Click to collapse
Can you get into fastboot?

So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?

To use fastboot you need to be in bootloader mode.

mikaole said:
So no bootloader.
Just my thoughts. I don't know if that's even possible.
Isn't it possible to edit the ota script to flash a bootloader?
Or even make a full factory update like this?
Click to expand...
Click to collapse
If it is, I don't know how. I would need it to be able to load from Sideload.

Does phone boot at all? To OS?

Yes it does. Only thing not working is bootloader. Without out this I can't root.

bschatzow said:
Yes it does. Only thing not working is bootloader. Without out this I can't root.
Click to expand...
Click to collapse
Ok..if phone boots ur bootloader is still there. Phone wouldnt boot without it. You on stock rom? Hit me up on hangouts and I will try to help you if you want. For the sake of time. Im sure you wanna get this resolved ASAP.

Sent you a pm requesting contact info.

Moderator Close
Worked for a long time with BDogg718. He generously spent a great deal of his time with me and opened several Chats with Developers and No one had a solution. He is very knowledgeable and really did not want to give up. For now the solutions seems to be send it back to Google and get a replacement. It would be nice if someone could talk to Google, as a phone that has a recovery built in firmware should be able to restore itself. The dual slots seems to be a problem for them as well.

I think I had the same thing happen with me! I installed the update via TWRP. The update installation seemed to crash at the end, resulting in a reboot. The phone did install 7.1.2 successfully, but I lost root and the ability to successfully boot into any recovery. I tried flashing TWRP again, but it failed "FAILED (remote: partition recovery doesn't exist). It appeared to attempt to flash it into slot "_b", if that means anything.

TWRP will not boot on 7.1.2. At least that's the conclusion formed last night in #twrp while the devs were working with someone else with this issue. I don't think they know why yet, but I doubt it will be overly long til they figure it out.
Sent from my Pixel XL using Tapatalk

Glad to hear someone is on the case. I will be sure to send a few shekels their way for my clumsiness.