[TOOL][HOW-TO] [Nexus 6P] Bootloop of Death (BLOD) Workaround [Flashable Zip]
- Thread starter osm0sis
- Start date
From the OP:
- If no 4core recovery boots for you then you definitely have more components than just the performance cores separated, sorry but your device is a brick.
Guys i was using my phone since 3 years with 4core fix but yesterday i messed up. Now 4 core fixes doesnt work. always bootloop screen. Any help ? i tried all core fixes :/
what is 'factory' on bootloader menu ? my phone works with is but its liitle different. can i do something from here to fix ?
what is 'factory' on bootloader menu ? my phone works with is but its liitle different. can i do something from here to fix ?
If you tried all the fixes, then unfortunately it might be that time...
Thanks, this works!
However, when I try to update apps through google play store, my phone reboots when it's "installing" the update. Same thing happens when I install any new app from the play store.
Does anyone else have this issue?
However, when I try to update apps through google play store, my phone reboots when it's "installing" the update. Same thing happens when I install any new app from the play store.
Does anyone else have this issue?
see i literally devoted myself for fixing this situation in my nexus6p.....but as per as our conditions, we can do nothing about it ......it's the time to let it go
Unsubscribing now since the Nexus 5X (my afflicted device) scene is near death, and the last fully working ROM for it was PE Plus Android 10.
Final zip for the workaround still works well enough on even the latest broken Android 12L ROMs, and will remain available here, on my AFH and on GitHub.
Feel free to mention me in your post if you need something here.
Final zip for the workaround still works well enough on even the latest broken Android 12L ROMs, and will remain available here, on my AFH and on GitHub.
Feel free to mention me in your post if you need something here.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
33Bootloop of Death (BLOD) Workaround AnyKernel3 zip for Nexus 6P
Original thread posts: Nexus 5X, Nexus 6PGuys.. bad news.. my Nexus 5X just got hit with the BLOD.
Good news for everyone is I spent a bit of time tonight to first patch TWRP 3.2.1-0-FBE (File-Based Encryption support) image to be 4core, then made an AnyKernel2 zip which will patch the existing boot and recovery partitions on-device to add all the 4core fixes from @XCnathan32.
Should work over any ROM, any custom kernel, recovery, etc., can be added in queue after ROM, root zip + custom kernel to patch it from TWRP or FlashFire (so good for OTAs), and simplifies the initial process greatly since you can now fastboot boot any 4core recovery.img and then adb sideload my AK3 zip to fix the likely newer recovery you already had on your device.
Now updated to an AnyKernel3 zip to support the SAR (system-as-root) and 2SI (2 stage init) ROMs that have popped up for Pie and Android 10+!
General Information
If you've found this thread then I'm sure you probably already know what the Bootloop of Death is - separation of the performance (perf) CPU cores - and that the only way to recover from it is to unlock your bootloader and patch to disable the faulty cluster. If you have not enabled unlocking your bootloader yet, the known methods to get it to boot long enough so you can go to System, then Developer Options and toggle "OEM unlocking" are:
- super cooling the device in a freezer in a ziplock bag to keep out moisture,
- super heating around the camera, and
- letting the battery run all the way down before trying to boot.
Some important notes before going any further:
- Freezing at the Google logo likely points to it being perf cluster separation, but this could also be caused by other components separating.
- Freezing at the boot animation suggests ROM/ROM data problem or could also potentially be a BLOD with other components now beginning to separate and that's what people have reported when the 4core mods suddenly stop working with no configuration changes - if you've tried the default boot.img for your ROM, patched with the BLOD AK3 and it still doesn't work, sorry but your device is a brick.
- If no 4core recovery boots for you then you definitely have more components than just the performance cores separated, sorry but your device is a brick.
- I haven't seen anyone say their devices only worked using a "1core" modification who had tried a proper 4core patched setup; 4core makes sense because it's the separate perf cores cluster becoming unsoldered, but if the 4 low power cores cluster also starts to come unsoldered logically not even a single core would work.. I think that's where the "Green Screen Of Death" comes into it.
- DemiGod = Green Screen Of Death; unfortunately this (more components separating given more time - maybe the flash memory chip?) is why many call the 4core workaround only temporary.. there's not much that can be done after that from what I've read.
- EX Kernel does not support FBE on these devices because the EX zip patches the fstab forcefdeorfbe flag to encryptable.
- Android 10 does not appear to support FBE on these devices but the 4core FBE TWRP build can be used to BLOD patch the latest TWRP (see instructions in next post).
On Oreo, I was personally on stock ROM still, FBE enabled, rooted with SuperSU v2.82 SR5 + suhide and the latest Franco Kernel on my 5X. Then I bumped up the min freq on the low perf cores and it's working great - totally fine for general use, just anything creating a bit of heat like games maxing the low power cores for awhile, or charging, will make it pretty painfully laggy and risk further solder deterioration.
Even though SuperSU development is ostensibly dead, I still strongly recommend it on BLOD-affected devices using stock ROM for reasons I'll explain below.
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!
Step-By-Step Installation Instructions
- Any quoted commands should be entered without quotes
2) Navigate to https://androidfilehost.com/?w=files&flid=312881 (also mirrored below) and download N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip to your platform-tools folder as well as
2a) twrp-3.2.1-0-fbe-4core-bullhead.img (Nexus 5X), or2b) twrp-3.2.1-0-fbe-4core-angler.img (Nexus 6P)3) Hold Shift + right-click on your platform-tools folder and
3a) Open a command window here (Windows <10), or3b) Open a PowerShell window here, then enter "cmd" at the Windows PowerShell prompt (Windows 10+)4) Reboot your phone to bootloader and connect it to your PC with a USB cable
5) Enter "fastboot flash recovery twrp-3.2.1-0-fbe-4core-angler.img" into the cmd prompt
6) Reboot your phone to recovery and tap Advanced, then ADB Sideload
7) Enter "adb sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip" into the cmd prompt
8) Reboot and cross your fingers that it works
For information how to seamlessly update to stock and custom ROM OTAs, see the following post
Source Code: https://github.com/osm0sis/N5X-6P-BLOD-Workaround-Injector
Status: No Longer Updated
Thanks:
- @XCnathan32 for researching and developing the 4core workarounds for both the Nexus 5X and Nexus 6P
- chetgurevitch (GitHub) for the original FBE supporting TWRP builds
- @Aukaminator for the original step-by-step write-up15Update Flashing Instructions
- Keep N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip on your device sdcard, henceforth referred to as BLOD AK3 zip
Always flash the BLOD AK3 zip last!
Reflashing the BLOD AK3 zip will likely be required after anything that could modify the boot.img or recovery.img, including (but not limited to): ROM updates, custom kernel updates, custom recovery updates.
ROMs:
- On custom ROMs with built-in Flash After Update (i.e. OmniROM-based), place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/OpenDelta/FlashAfterUpdate/ ensuring the BLOD AK3 is last in the directory listing so that they will be flashed after each update.
- On custom ROMs that do not have built-in Flash After Update (i.e. LineageOS-based), you may add my FlashAfterUpdate addon.d script to /system/addon.d/ and then place your root (if using SuperSU), custom kernel and BLOD AK3 zip in /sdcard/FlashAfterUpdate/ ensuring the BLOD AK3 is last for the same effect: flashed after every OTA.
- On stock ROM rooted with SuperSU (SuperSU v2.82-SR5 recommended) instead of tapping "Reboot & Install" once the OTA is downloaded you should use @Chainfire's excellent FlashFire app to queue the OTA from /data/ota_package/update_s.zip then queue the SuperSU zip, custom kernel and BLOD AK3 zip, ensuring the BLOD AK3 is last. This is how I have mine set up, since this is by far the most seamless. Be sure to disable EverRoot since SuperSU v2.82-SR5 is newer than the SuperSU included in FlashFire.
- On stock ROM rooted with Magisk you must uninstall Magisk from within Magisk Manager to restore your stock boot.img, reboot the ROM to restore your stock recovery partition, tap "Reboot & Install" once the OTA is downloaded, then go through the steps above to flash the 4core TWRP and BLOD AK3 zip again. I definitely recommend SuperSU on this device to avoid the hassle of unrooting and/or messing with factory images.
Kernels:
- Custom kernels can be flashed from an app like Franco Kernel Manager & Updater, which can be set to flash without reboot for Franco Kernel updates, or "Flash only" can be chosen in the manual flasher. The FK app supports all types of AnyKernel3 zip so the BLOD AK3 zip may then be flashed after the custom kernel zip to repatch the new kernel's ramdisk.
- For other kernel managers that don't support AK3 zips, simply reboot to recovery and flash the BLOD AK3 zip from there to repatch before attempting to boot the ROM again. Also see above under "stock ROM rooted with SuperSU", since FlashFire also works perfectly for this use-case, queuing the custom kernel zip and then the BLOD AK3 zip, with FlashFire's EverRoot option disabled since the device is already rooted.
Recoveries:
- Download the updated custom recovery .img and, without flashing it, reboot to recovery, use TWRP's flash image feature to flash the new recovery.img, then without rebooting immediately flash the BLOD AK3 zip to patch it. You can then dump/backup the recovery partition if you want it as a recovery.img. Custom recovery updates can also be done from FlashFire, queuing the BLOD AK3 zip afterward, but the "Preserve recovery" feature must be disabled.
- If you prefer to stay on stock recovery for some reason, you can still use TWRP to do the above without flashing TWRP to the device by using "fastboot boot twrp-3.2.1-0-fbe-4core-angler.img".
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!
Changelog
2018-01-15 - Original post in other BLOD threads.
2018-07-21 - Update AK2 Core+Backend files to latest, add searching of all init.*.rc files for problematic cpuset commands which were popularized by Franco Kernel and are now used by multiple custom kernels. (6758 downloads)
2019-10-30 - Update to AnyKernel3, add support for SAR and 2SI Treblized ROMs. (1720 downloads)
2020-01-16 - Update AK3 Core+Backend files to latest to fix AVBv1 signing in recovery on Android 10, update boot_signer-dexed.jar. (570 downloads)
2020-02-17 - Update AK3 Core+Backend files to latest to fix SAR mount support in fragmented TWRP and Lineage 16+17 Recovery. (1412 downloads)
2020-05-25 - Update AK3 Core+Backend files to latest to improve SAR mount support in Lineage 17 Recovery and AVBv1 signing. (1789 downloads)
2021-07-21 - Update AK3 Core+Backend files to latest to support Lineage 18.1 recovery and Android 11 ROMs.
Good luck and enjoy!12
The time has come! I've uploaded the new AnyKernel3-powered BLOD Workaround zip to the OP, and it should be working on both the system-as-root (SAR) and 2 stage init (2SI) ROMs that maintainers for these devices have switched to in order to support Android 10 (and in some cases have done so on Pie as well)! :victory:
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!
I'm going to leave the AK2 zip up for posterity, so note the new zip's naming: N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip
A source repo for the updated zip is also available going forward: https://github.com/osm0sis/N5X-6P-BLOD-Workaround-Injector
Note that in my testing on my N5X FBE didn't seem to be supported on Android 10 for us so far (I had to format data instead and opted to stay unencrypted), so I've added a note about just using the old 4core FBE recovery to update to the latest official TWRP as well.
Sorry again for the wait, but I had to go get married and go on my honeymoon first.76
I also have this "Unknown ramdisk compression" thing when installing BLOD patch over latest Pixel Experience and Bootleggers rom
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.
