[TOOL][HOW-TO] [Nexus 6P] Bootloop of Death (BLOD) Workaround [Flashable Zip]

[dudikaz]

this saved my phone! thanks. do i have to reflash it when upgrading magisk?

 

[osm0sis]

this saved my phone! thanks. do i have to reflash it when upgrading magisk?

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.

 

[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).

 

[osm0sis]

Newest TWRP for sure. Instructions for updating TWRP and BLOD repatching are in the second post.

 

[arnax1]

Newest TWRP for sure. Instructions for updating TWRP and BLOD repatching are in the second post.

Thanks for reply, i tried with newest but its the same issue i get "failed" when i try to ADB sideload.

 

[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?

 

[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?

You likely just need to use a newer TWRP. Follow the TWRP upgrade instructions in the second post.

 

[arnax1]

You likely just need to use a newer TWRP. Follow the TWRP upgrade instructions in the second post.

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 ?

 

[Lughnasadh]

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 ?

Have you tried deleting your lockscreen password and then seeing if the files in TWRP are decrypted?

 

[osm0sis]

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 ?

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:

 

[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

 

[[email protected]]

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

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.

 

[ttocs99]

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

Need to ask. You still own a 6p.

 

[osm0sis]

Need to ask. You still own a 6p.

Never did. BLOD'd Nexus 5X sitting in a drawer still though.

 

[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)....

 

[Lughnasadh]

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)....

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.

 

[GitManMatt]

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.

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.

 

[osm0sis]

Just for reference adb only works in recovery or booting/booted, not in bootloader. So don't focus on that part. :good:

 

[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..

 

[juancapo1]

dude

Just for reference adb only works in recovery or booting/booted, not in bootloader. So don't focus on that part. :good:

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 ??