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

[Lughnasadh]

Thank you Lughnasadh for your response.

Is there anything else I can try ? A possible solution which does not require me to enter recovery ?

Is there a possibility to root the phone while it is stuck in the bootloop and install a custom ROM ?

Not really much else you can do, unfortunately.

 

[MrSpies]

My Nexus 6P with BLOD was also saved from the waste heap with this guide. Thanks to all involved! However I was saddened a bit to find that Google Pay no longer works. Being a total noob at this sort of thing anyone know of a simple way and can provide step by step instructions on how to get Google Pay working again as well as keeping the BLOD patch in place? Cheers!

 

[Lughnasadh]

My Nexus 6P with BLOD was also saved from the waste heap with this guide. Thanks to all involved! However I was saddened a bit to find that Google Pay no longer works. Being a total noob at this sort of thing anyone know of a simple way and can provide step by step instructions on how to get Google Pay working again as well as keeping the BLOD patch in place? Cheers!

I don't believe this BLOD fix affects Google Pay in any way. Something else is interfering with it.

 

[osm0sis]

Unlocking the bootloader would trip SafetyNet. Magisk should get it working again though.

 

[MrSpies]

Unlocking the bootloader would trip SafetyNet. Magisk should get it working again though.

Thanks for the quick replies and pointing me towards Magisk. I had feeling it would not be as simple as just relocking the bootloader.

 

[PraneethMv]

Hey, I've tried this method and successfully booted to system and set up the device. But when I first boot into recovery and it is asking password to decrypt data, and even after I flashed the BLOD fix and rebooted, it is asking pwd to decrpt data. Can I know is there any pwd like that or am I missing something?

 

[osm0sis]

Hey, I've tried this method and successfully booted to system and set up the device. But when I first boot into recovery and it is asking password to decrypt data, and even after I flashed the BLOD fix and rebooted, it is asking pwd to decrpt data. Can I know is there any pwd like that or am I missing something?

As long as you're not using FBE you should probably update to the newest TWRP .img and flash the BLOD zip over it to patch it. Detailed instructions are in the OP.

 

[PraneethMv]

As long as you're not using FBE you should probably update to the newest TWRP .img and flash the BLOD zip over it to patch it. Detailed instructions are in the OP.

Thank you! Missed that point. Will do that.

 

[nicholasknicks]

Anyone who managed to replace the battery can you please link me to where i can buy a good battery

 

[bilatche]

For me I did the replacement in a shop.
And it last two weeks before coming a serious BLOD.

 

[zhxhwyzh14]

Hi, dear developer. I use pixel experience ROM in my blod nexus 6p. In the newest update, it has enabled system-as-root. So when i flash blod patch in twrp, it showed "Unknown ramdisk compression". What can i do？ Could you help me？ Thank you very much.

 

[igylan]

Hi, dear developer. I use pixel experience ROM in my blod nexus 6p. In the newest update, it has enabled system-as-root. So when i flash blod patch in twrp, it showed "Unknown ramdisk compression". What can i do？ Could you help me？ Thank you very much.

I tried Crdroid and Carbon also. Somehow it comes through with an error when flashing the patch though the ROM has no problem. Hope someone can shed a light on this.

 

[[email protected]]

I also have this "Unknown ramdisk compression" thing when installing BLOD patch over latest Pixel Experience and Bootleggers rom

 

[paulfadiv]

Developer, Hello! Please help. Blog blog Nexus 6P displays this error when updating Pixel Experience ROM. "Unknown ramdisk compression".

 

[jarpco8484]

Hi:

Well, one more with "Unknown ramdisk compression" after flashing the patch during the installation of the newest versions of almost all the pie roms available for the nexus 6p, so sad.... Any help will be very appreciated.:good:

 

[osm0sis]

Hi, dear developer. I use pixel experience ROM in my blod nexus 6p. In the newest update, it has enabled system-as-root. So when i flash blod patch in twrp, it showed "Unknown ramdisk compression". What can i do？ Could you help me？ Thank you very much.

I tried Crdroid and Carbon also. Somehow it comes through with an error when flashing the patch though the ROM has no problem. Hope someone can shed a light on this.

I also have this "Unknown ramdisk compression" thing when installing BLOD patch over latest Pixel Experience and Bootleggers rom

Developer, Hello! Please help. Blog blog Nexus 6P displays this error when updating Pixel Experience ROM. "Unknown ramdisk compression".

Well, one more with "Unknown ramdisk compression" after flashing the patch during the installation of the newest versions of almost all the pie roms available for the nexus 6p, so sad.... Any help will be very appreciated.:good:

Wow, super annoying that a ROM would change something fundamental like system-as-root so late in a device's life.

Basically what happened is this: someone in control of the device trees all these ROMs are based on decided to make the Nexus 6P an A-only system-as-root device, resulting in there being literally no ramdisk in the boot.img anymore. See here: https://source.android.com/devices/bootloader/system-as-root

So, since all the boot-up root / directory stuff is now in the system partition, or possibly even vendor, I'll have to mount at least /system as read-write in recovery as well and patch the init.*.rc files there.

I don't have a lot of time right now, but I do have it on my list to fix. I'll get to it as soon as I can, and if you're frustrated in the meantime you should take your complaints to the ROM developers who should have known this would affect all BLOD devices still in use.

 

[igylan]

Wow, super annoying that a ROM would change something fundamental like system-as-root so late in a device's life.

Basically what happened is this: someone in control of the device trees all these ROMs are based on decided to make the Nexus 6P an A-only system-as-root device, resulting in there being literally no ramdisk in the boot.img anymore. See here: https://source.android.com/devices/bootloader/system-as-root

So, since all the boot-up root / directory stuff is now in the system partition, or possibly even vendor, I'll have to mount at least /system as read-write in recovery as well and patch the init.*.rc files there.

I don't have a lot of time right now, but I do have it on my list to fix. I'll get to it as soon as I can, and if you're frustrated in the meantime you should take your complaints to the ROM developers who should have known this would affect all BLOD devices still in use.

I had a hunch it had something to do with the rom devs than with the patch. Oh well, thanks for keeping our old devices running.

 

[zhxhwyzh14]

Thank you for your work.

 

[Lughnasadh]

Wow, super annoying that a ROM would change something fundamental like system-as-root so late in a device's life.

Basically what happened is this: someone in control of the device trees all these ROMs are based on decided to make the Nexus 6P an A-only system-as-root device, resulting in there being literally no ramdisk in the boot.img anymore. See here: https://source.android.com/devices/bootloader/system-as-root

So, since all the boot-up root / directory stuff is now in the system partition, or possibly even vendor, I'll have to mount at least /system as read-write in recovery as well and patch the init.*.rc files there.

I don't have a lot of time right now, but I do have it on my list to fix. I'll get to it as soon as I can, and if you're frustrated in the meantime you should take your complaints to the ROM developers who should have known this would affect all BLOD devices still in use.

Thank you very much for letting everyone know what is going on. The Angler rom threads are full of posts describing this problem and not one developer or maintainer (to my knowledge) has even responded to these posts. But here you are, someone who doesn't even have a working 5X (or 6P for that matter) anymore, has a ton of other projects going on and a life to live as well, letting everyone know the cause of the problem. For that alone, I'm very grateful. So....thank you.

 

[eladr1dj]

Hi, hello XDA developers and users. I have found this thread and I have read it completely, including the comments, since I am a user of a Nexus 6P.
My phone STILL does not have BLOD, but from what I have read it is a matter of time that is affected and finally dies, so I was interested to know the temporary solutions. I already have the Bootloader unlocked and the OEM has been active for some time, so that when the BLOD occurs, I have part of the work done. Now, I have some doubts that I hope you can answer. I am using compilation OPM. 181205.001, security patch December 5, 2018.

1 - With the compilation I currently have, is the solution of flashing with TWRP 4core the file `` N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip´´?

2 - Is there any pre-patched Boot.img image for the OPM compilation. 181205.001? Link please

3 - Can I downgrade to a lower version like OPM3.171019.013, of which I already have a pre-patched Boot image, without any brick risk for downgrade?

I hope you can answer my questions, and I apologize if the answer to any of them is in the thread, after having read so many pages, I may have missed something. Oh, and forgive my lousy English.