yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] Jalhmz:
could you please uplaod N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip because i can't access basketbuild website
[Nexus 6P General] osm0sis:
It's attached in the OP..
[Nexus 6P General] Jalhmz:
thanks my bad

Edited
[Nexus 6P General] osm0sis:
New year, new AK3 and BLOD Workaround fixes. :)

APEX mounting is added for recovery (thanks to [MENTION=6037748]Zackptg5[/MENTION]), which allowed me to fully fix AVBv1 signing from recovery on Android 10. I've also updated to a more recent compile of BootSignature_Android.jar (thanks to [MENTION=6376476]fawazahmed0[/MENTION]), which should be more futureproof in case any ROM developers try to switch to bootimg hdr v1 or hdr v2 while keeping AVBv1 signing. :highfive::good:

My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!

Be aware Magisk doesn't yet have the fixes for AVBv1 in recovery added yet (so rooting will unsign your boot.img), but I'm working on it!

See the related commits here: https://github.com/osm0sis/N5X-6P-BLOD-Workaround-Injector
[Nexus 6P General] dudikaz:
this saved my phone! thanks. do i have to reflash it when upgrading magisk?
[Nexus 6P General] osm0sis:
It should stick through a Magisk flash, but I still recommend you always flash the BLOD fix last after anything that modifies the device just to be safe.
[Nexus 6P General] arnax1:
Hi,

I am running out of ideas now so i am seeking help here (which i rarely do as most of the time i manage to fix my device myself). Basically my 6P is bootlooping (Google loading, then restarts and Google loading again and again).

I would be happy with getting data off of it and reflashing or bricking it, but when i try to get the data off while in TWRP, all the folders are in gibberish. thus i assume data is encrypted. When i turn on TWRP, it asks for password to decrypt data. Usually it was my lockscreen PIN but even this doesnt work. So my first question is how do i get my data back? Why is it encrypted and what could the password be?

Since i cant get my data off TWRP, i tried to boot my phone and i stumbled across this thread. My main problem is that i get stuck when doing adb sideload. TWRP just keeps loading and then says ADB sideload failed. What are my options? Do i need newer TWRP maybe? Or update my Android tools?

Attaching some images for better understanding what am i seeing.

If i remember correctly i was running 8.1.0 (OPM7.181105.004, Nov 2018) image (if i can somehow check to confirm please tell me how to).
[Nexus 6P General] osm0sis:
Newest TWRP for sure. Instructions for updating TWRP and BLOD repatching are in the second post.
[Nexus 6P General] arnax1:
Thanks for reply, i tried with newest but its the same issue i get "failed" when i try to ADB sideload.
[Nexus 6P General] arnax1:
Hey osm0sis,

I still don't give up. But i have a question. When i flash twrp-3.2.1-0-fbe-4core-angler to my Nexus 6P and boot into recovery, it asks me for password. It doesn't take my PIN which i set on my phone. This is probably the thing that encrypted data on my phone when i try to view it with built in file manager. Maybe you know what is the password?
[Nexus 6P General] osm0sis:
You likely just need to use a newer TWRP. Follow the TWRP upgrade instructions in the second post.
[Nexus 6P General] arnax1:
Thanks for replying once again. I actually did that, i installed twrp-3.3.1-0-angler but it is still showing folders in gibberish. I assume once i installed 4cores TWRP, it asked me for password (which i never set nor i know what it is) and once i clicked cancel, it encrypted all the files.

osm0sis, do you think my data is lost and i should forget about it? Or is there anything i can do ?
[Nexus 6P General] Lughnasadh:
Have you tried deleting your lockscreen password and then seeing if the files in TWRP are decrypted?
[Nexus 6P General] osm0sis:
I think some custom ROM has a newer twrp for angler, that might even have FBE support at this point, so give updating to that a try using those update instructions from the second post. I recall seeing mention of the TWRP .img being in the ROM thread's OP. :good:
[Nexus 6P General] osm0sis:
Here's another BLOD zip update to add some important recent changes to the AK3 Core+Backend files, fixing SAR mount support in fragmented TWRP and Lineage 16+17 Recovery, which has been a bit of a pain in the ass lately! ;)

My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!

The latest Magisk Canary builds now have my fixes for AVBv1 in recovery added, so all should be good from here if your ROM signs their boot images! :good:

See the related commits here: https://github.com/osm0sis/N5X-6P-BLOD-Workaround-Injector
[Nexus 6P General] D@rekills4:
Oh wow, thank you. I was not expecting anyone working so deeply with the Nexus 6P at this point.

Well, I am not on the BLOD patch but that **** can show up any time so it's nice knowing you are around.
[Nexus 6P General] ttocs99:
Need to ask. You still own a 6p.
[Nexus 6P General] osm0sis:
Never did. BLOD'd Nexus 5X sitting in a drawer still though. ;)
[Nexus 6P General] GitManMatt:
BLOD?

Alright guys, I'm just feeling my way with a Nexus 6P I've just inherited - so far I have:

- booted successfully into bootloader

- checked that device is recognised by fastboot devices (it is, number and state present). Doesn't work with ADB. Not sure why...

- tried to reboot using keys into recovery - bootloops

- tried to unlock bootloader - fastboot OEM unlock returns FAILED (remore:unknown command). Fastboot Flashing Unlock does nothing (just shows menu items).

- fastboot oem device-info returns:

(bootloader) Device tampered: false

(bootloader) Device unlocked: false

(bootloader) Charger screen enabled: false

(bootloader) Display panel:

OKAY [ 0.050s]

- device shows LOCKED in bootloader but also weirdly download mode DISABLED (not sure I've seen that before).

I'm guessing I probably need to super-heat/super-cool in order to get device on and OEM unlock ticked on developer options, correct? or is this just a brick and I'm wasting my time....

Help appreciated (and sorry if this is a tired and old request)....
[Nexus 6P General] Lughnasadh:
The first thing I would do is make sure your Platform Tools are up to date... https://developer.android.com/studio/releases/platform-tools

Then try the fastboot flashing unlock command again. Also, try another cable if that doesn't work.

Addendum: If you are successful I would then fastboot flash the latest factory image. If it boots you don't have the BLOD. If it doesn't you likely do.
[Nexus 6P General] GitManMatt:
Ah, OK makes sense - might be a cable issue rather than BLOD. I'll try some different ports or maybe a different PC also. I do have the most up to date Platform Tools, so not sure that it's that. I think I've been having ADB issues with a couple of other phones I was messing with, which suggests it might actually be PC-related - hmmm, lots to look at.

I was going to flash the stock back again as per Google firmware page and see what happened - figuring as you point out a failed flash probably means BLOD - just couldn't get passed the unlocking bootloader stage....

Thanks, I'll report back.
[Nexus 6P General] osm0sis:
Just for reference adb only works in recovery or booting/booted, not in bootloader. So don't focus on that part. :good:
[Nexus 6P General] arnax1:
I think i am giving up... i realise i won't get my data back and i need phone.. Tried almost everything. Wanted to try adb pull but once i am in recovery and try 'adb devices' it gives me this error :

C:\platform-tools>adb devices

adb server version (31) doesn't match this client (41); killing...

could not read ok from ADB Server

* failed to start daemon

adb.exe: failed to check server version: cannot connect to daemon

Nothing seems to work. Whatever ill just wipe my phone and hope it boots up..
[Nexus 6P General] juancapo1:
dude

hello osmosis. My nexus 6p worked fine, with twp 3.1.1 4cores and it will stop working for a month, enter the loop

I already installed twrp-3.2.1-0-fbe-4core-angler.img without errors, but I cannot enter recovery. When I want to enter, it restarts and returns to the loop.

What can i do ??
[Nexus 6P General] osm0sis:
Oh hey, we made the news again! ;)

https://www.ifixit.com/News/36821/d...death-loop-and-how-to-fix-it-with-a-hairdryer
[Nexus 6P General] Lughnasadh:
Very nice.

Roughly 1 year 9 months since applying your fix and still going :good:
[Nexus 6P General] JHSNE:
BLOD fix withouth TWRP installed on phone

Hi osm0sis!

Here in 2020 and still clinging on to my good ol' Nexus 6P. This bootloop fix seems to be everything I wish for, it's just that I haven't been able to get TWRP to work on my phone. Can I use this fix without it?

My phone is:

- Bootlooping (obviously)

- OEM unlocked

- Possible to reach recoverymode (after a few minutes of hairdrying on the side)

Also I have arranged the adb fastboot on my computer, and done a full backup via the cmd. But not sure if I can use this backup after I've flashed it to 4core.

Last, I dont mind if my phone gets a full wipe from data, since photos and so on already are backed up on the cloud.

Thanks!
[Nexus 6P General] osm0sis:
You can try to temp boot TWRP to install it, but you're better off keeping it installed. If 4core TWRP doesn't boot at all then your hardware is beyond the help of this workaround. Instructions are all in the OPs.
[Nexus 6P General] JHSNE:
Maybe I have missunderstood the process. The TWRP app doesn't work when I try to open it on my phone. But is the app necessary or not to do this?
[Nexus 6P General] osm0sis:
Nope. Read the OPs please. Read them twice. All the information you need is there, step by step.
[Nexus 6P General] juancapo1:
help

hello osmosis. My nexus 6p worked fine, with twp 3.1.1 4cores and it will stop working for a month, enter the loop

I already installed twrp-3.2.1-0-fbe-4core-angler.img without errors, but I cannot enter recovery. When I want to enter, it restarts and returns to the loop.

What can i do ??
[Nexus 6P General] osm0sis:
You can read. Either the OP or 3 posts before yours, both have your answer. Buy a new device.

I am sympathetic that people are hopeful they can revive their devices forever, but I lose sympathy when those people seem too ignorant or lazy to read the simple information and instructions laid out here.

It was always clearly pointed out that this is a temporary workaround and if it works for you then your device is on borrowed time so you should get your **** together and look at getting a new one sooner than later.
[Nexus 6P General] juancapo1:
okay

I liked you too

no longer

thanks for the help that gave me your solution 1 year ago

hurt your sympathy

greetings from Argentina
[Nexus 6P General] osm0sis:
You're welcome for that extra year I bought you, it's not my fault you didn't use it to get a new device and transfer your data.
[Nexus 6P General] juancapo1:
osmosis, yes

you saved me!! Take advantage of the nexus 6p, buy another phone

I only used the nexus as a music player and to take pictures

it was an excellent phone

thanks really for your help !!!!

regards
[Nexus 6P General] osm0sis:
Here's a new BLOD zip update to further improve SAR mount support in Lineage 17 Recovery, plus add my own dexed build of AOSP's boot_signer.jar (formerly incorrectly named BootSignature_Android.jar) for AVBv1 signing.

My development work on my many projects comes out of my free time, so if you enjoy this project or anything else I've done on xda, please consider sponsoring my ongoing work using my GitHub Sponsors profile. For a one-time donation you can hit the donate link from my profile. Thank you for your support!

See the related commits here: https://github.com/osm0sis/N5X-6P-BLOD-Workaround-Injector

Edit

: Just uploaded a slightly tweaked zip to clean up the flash output after recent AK3 updates made it more noisy. :good:
[Nexus 6P General] Lughnasadh:
Amazing that after almost 2 years and long after your Bullhead died you are still giving this some love. Thank you :)

Side note: After roughly 1 yr., 9 months my BLODed Angler still going strong with your fix (knock on wood) :good:
[Nexus 6P General] JeanH:
Hi, I did the fix on my nexus 6p but then after a couple of months it died again and went into the same loop, any ideas? should i try and do the process all over again?
[Nexus 6P General] osm0sis:
If you didn't update or change anything and it just spontaneously died then it's dead, Jean.

That's all explained in the FAQ in the OP, by the way. :silly:
[Nexus 6P General] JeanH:
"if you've tried the default boot.img for your ROM, patched with the BLOD AK3 and it still doesn't work"

I haven't try that yet, so you think is not worth it?
[Nexus 6P General] osm0sis:
Try it. It's easy and would have taken less time than it took to ask these questions. :p

If 4core TWRP doesn't boot at all anymore then it's of course for sure dead.
[Nexus 6P General] Lenox11312:
Hi. I'm very new to all of this, so if there is something obvious that I haven't tried, please know that it's due to lack of understanding of what I'm reading (and re-reading) and not lack of trying. I have spent 20+ hours researching and troubleshooting this issue. Can anyone suggest where I go from here?

This is what I most recently used:

https://www.xda-developers.com/nexus-6p-bootloop-fix/

After trying it with both N2G48B_4Cores.img and twrp3_1_1_4Cores.img, I reached the same result.

[IMG="Nexus 6P 1"]https://i.imgur.com/BTMlIgK.jpg[/IMG]

And if I go back and lock it by using fastboot flashing lock, I receive this:

[IMG="Nexus 6P 2"]https://i.imgur.com/Uoma3Eu.jpg[/IMG]
[Nexus 6P General] Lughnasadh:
The first message is normal for an unlocked bootloader and you could have safely ignored it.

You should not lock the bootloader.

I'm not sure what state your phone is in since you didn't mention it, but go back and unlock your bootloader with fastboot if you can. Then follow the directions in the OP, starting with the General Information section (specifically toggling OEM unlocking in the Developers Options). If you can do this then continue to follow the directions in the OP.

You may end up having to flash the last factory image depending on what all you did to your phone beforehand as well.
[Nexus 6P General] Lenox11312:
Thanks for your quick reply.

Months ago before reaching persistent boot loop, I did OEM unlocking in Developers Options. Otherwise, I think I'd be in a bad place right now.

I haven't seen my phone's desktop in 3+ months.

I've followed those directions and just reached consistent bootlooping.
[Nexus 6P General] Lughnasadh:
My suggestion would be to start fresh. Make sure your bootloader is unlocked using fastboot since it sounds like you locked it again. Then fastboot flash the last factory image and follow the instructions in the OP. If it doesn't boot after that your phone is likely dead.
[Nexus 6P General] Lenox11312:
Lughnasadh,

Thanks for your help. What are your thoughts on the below?

Lenox

I unlocked it again using:

9) Start the process to unlock your phone’s bootloader by entering the following command: fastboot flashing unlock

Here are the results:

[IMG="Nexus 6P A"]https://i.imgur.com/EmdAOtY.jpg[/IMG]

[IMG="Nexus 6P B"]https://i.imgur.com/XI5xs50.jpg[/IMG]

[IMG="Nexus 6P C"]https://i.imgur.com/BbDao3k.jpg[/IMG]

[IMG="Nexus 6P D"]https://i.imgur.com/NS19Yh0.jpg[/IMG]

---------- Post added at 03:13 AM ---------- Previous post was at 03:07 AM ----------

Also, is it worth posting in this other thread or no? I don't want to double post if it's against the rules.

https://xdaforums.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279/page270
[Nexus 6P General] Lughnasadh:
Did you flash the latest factory image beforehand like I suggested? If not, it's really hard to tell if the reason it's not booting is because your phone is dead or because of something else you've done, like flashing those other images you mentioned or something else you may have done.

If so and you are starting from a clean slate and it's not booting after flashing the workaround zip then your phone may be dead. Really need more specific details to be sure.

That other method in that other thread is outdated so no use posting there.
[Nexus 6P General] Lenox11312:
What are the steps for this? I'm not sure if I've done this.
[Nexus 6P General] osm0sis:
The fact that you've got 4core TWRP booting suggests it should be able to work if you can get your ROM sorted out.

I'd probably just use the TWRP you've got there to flash and patch the newest TWRP "near-release" build run: https://build.twrp.me/twrp-3.4.0-0-angler.img

Then use fastboot to flash the final stock factory image and format userdata, then boot into patched 3.4.0 again to flash latest Pixel Experience Plus and BLOD patch the ROM.

There are lots (and lots) of threads on how to flash a stock factory image to a Nexus device, so that shouldn't be hard for you to find.
[Nexus 6P General] Lughnasadh:
https://developers.google.com/android/images#angler

Follow the flashing instructions in the link above but do not lock your bootloader at the end. If you have the BLOD, once you execute the flash-all command your phone will try to reboot but won't because of the BLOD. Then just follow the directions in this thread to apply the custom recovery and workaround.zip so it will boot.

If it doesn't boot after all this, your phone is likely dead.

Edit: Ninja'd :)
[Nexus 6P General] Lenox11312:
OK. Going to try.

---------- Post added at 06:08 PM ---------- Previous post was at 05:16 PM ----------

Results of flash-all on:

angler-opm7.181205.001-factory-b75ce068

angler-opm7.181205.001

8.1.0 (OPM7.181205.001, Dec 2018)

[IMG="flash-all"]https://i.imgur.com/jiQY9sP.png[/IMG]
[Nexus 6P General] Lughnasadh:
Use flash-all (not flash-all.bat) for command

Also make sure the 6 files in my screenshot below are in the folder you are flashing from.
[Nexus 6P General] Lenox11312:
I highlighted the 6 files. Can you see them OK?

[IMG="platform-tools folder"]https://i.imgur.com/WsEZV3o.png[/IMG]

I had actually done flash-all the 1st time but tried flash-all.bat the 2nd time to see if it made a difference.

[IMG="flash-all"]https://i.imgur.com/mj79NZU.png[/IMG]

Are the failed messages significant?
[Nexus 6P General] osm0sis:
Weird, but, what's the command that's failing? Can you upload the .bat to pastebin real quick?

I wouldn't be super worried yet. I'd probably just flash the partitions manually.
[Nexus 6P General] Lenox11312:
I'm not sure what's failing. I'm new to all this stuff. Really just following steps and hoping for the best.

I've never heard or used Pastebin, but I pasted the contents of the batch file in there and it came up with this:

https://pastebin.com/KLrWkACF

Is that what you wanted to see?

To flash the partitions manually, is that where I do these steps?

get your ROM sorted out

use the TWRP you've got there to flash and patch the newest TWRP "near-release" build run: https://build.twrp.me/twrp-3.4.0-0-angler.img

use fastboot to flash the final stock factory image and format userdata

boot into patched 3.4.0 again to flash latest Pixel Experience Plus and BLOD patch the ROM
[Nexus 6P General] osm0sis:
Yeah, so from your screenshot the radio and bootloader flashed fine so just extract the contents of image-angler-opm7.181205.001.zip into your current directory, download https://build.twrp.me/twrp-3.4.0-0-angler.img then do this:

fastboot flash boot boot.img
fastboot flash recovery twrp-3.4.0-0-angler.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot format userdata

Then:

fastboot boot twrp-3.2.1-0-fbe-4core-angler.img

And flash the BLOD zip, then reboot to recovery and you should be in TWRP 3.4.0 but patched for 4core. :good:

Then you might want to format userdata one more time from fastboot since I wouldn't trust TWRP to handle the empty one correctly, then try to just boot up normally from the bootloader directly after.
[Nexus 6P General] Lenox11312:
Not done yet, but wanted to document the results of the first 5 steps you provided.

[IMG="flash five"]https://i.imgur.com/TJEd5oq.png[/IMG]

[IMG="flash 6"]https://i.imgur.com/pkQG2vL.png[/IMG]

[IMG="Unmodified System Partition"]https://i.imgur.com/EmdAOtY.jpg[/IMG]

I remember being on this Unmodified System Partition screen yesterday.

What do I do from here?

How do I flash the BLOD zip?

How do I reboot to recovery?

Is being in TWRP 3.4.0 4core back on my phone's desktop, or not yet?
[Nexus 6P General] Lughnasadh:
That last screenshot is normal. Just swipe to allow modifications.

For flashing the BLOD zip, see the last part of Step 6 & Step 7 (not 8 just yet) in the Step-by-Step instructions in the OP (adb sideloading)(make sure the BLOD zip is in you platform tools folder).

There is a reboot button in TWRP and when you tap that it will give you options of where to reboot. Tap recovery to reboot into it.

Then follow the remaining instructions from osm0sis in his earlier post (i.e. formatting user data again via fastboot and booting up normally from bootloader directly afterwards).
[Nexus 6P General] Lenox11312:
This is similar to what I did last night, but now have a different FAILED result. Two photos below:

[IMG="sideload 5"]https://i.imgur.com/URUq2I2.png[/IMG]

[IMG="sideload 5-CMD"]https://i.imgur.com/6qaapwb.png[/IMG]

Additionally, when I try to repeat Swipe to Start Sideload, my phone goes back to cycling between these two screens again:

[IMG="Nexus 6P D"]https://i.imgur.com/NS19Yh0.jpg[/IMG]

[IMG="Nexus 6P 1"]https://i.imgur.com/BTMlIgK.jpg[/IMG]
[Nexus 6P General] osm0sis:
Sometimes sideload won't work, especially if your drivers or PC are being idiotic. You must have rebooted to get out of sideload mode somehow, hence the bootloop, so you need to go back to the bootloader and fastboot boot the 4core recovery again.

Then just `adb push N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip /tmp/` and flash it from there.
[Nexus 6P General] Lenox11312:
It's possible my phone ran out of battery. I'm not sure how that happened when it's been plugged into my PC via a USB-to-C cable.

After the failure and repeated cycling screens, I noticed a single-red blinking light in the upper-left corner. I plugged my phone into my wall charger for a bit, then repeated steps, and then saw TWRP report 3% in the upper-right corner. So maybe the failure was due to reaching 0% battery? Odd that it was still able to reach the boot loader and cycle through the two aforementioned screens with no battery life.

Below are 4 images of what appears to be a more successful attempt.

[IMG="ADB Sideload Complete"]https://i.imgur.com/FcSxZmc.jpg[/IMG]

[IMG="Reboot to Recovery"]https://i.imgur.com/sndqbfp.jpg[/IMG]

[IMG="Do Not Install TWRP App"]https://i.imgur.com/HnR9XlS.jpg[/IMG]

[IMG="TWRP 3.4.0-0"]https://i.imgur.com/9HY2eMA.jpg[/IMG]

Is it safe to assume that the heading showing Team Win Recovery Project 3.4.0-0 instead of 3.2.1.0-FBE is progress?!

What do I do now?
[Nexus 6P General] Lughnasadh:
Do not install TWRP app for future purposes.

Plug your phone in and let it charge a bit.

Format user data from fastboot one more time as osm0sis suggested.

Boot up normally from bootloader and cross your fingers.
[Nexus 6P General] Lenox11312:
OK, thanks. It's at 21% now. I may wait until it's at 100%.

Format user data from fastboot

Sorry, which step is this? I saw him write this but did not understand 100% what to do. I want to make sure I do this correctly. Do I stay on this screen and fire up CMD again? Or exit or...?
[Nexus 6P General] Lughnasadh:
No need to wait until 100%.

Reboot to bootloader and in command line type fastboot format userdata (just like you did earlier when you fastboot flashed all the other things in Post # 292).

Then reboot from bootloader