It includes it? Can you link to where you saw this? In any case flash it none the less
[TOOL][HOW-TO] [Nexus 5X] Bootloop of Death (BLOD) Workaround [Flashable Zip]
- Thread starter osm0sis
- Start date
It includes it? Can you link to where you saw this? In any case flash it none the less
I'm not sure what that's all about. I would imagine it just patches TWRP like the one in the OP but you would still need to flash the workaround zip. osm0sis would be the one who could tell us.
Last edited:
Sorry for replying to an old post but I believe the BLOD-related changelog items on that page relate to making TWRP bootable on Nexus 5Xs with only 4 cores (not 6), it does not include the workaround patch.
Mainly replying to this thread to thank @osm0sis for his work, I managed to resurrect my dad's Nexus 5X by hairdrying the area between the fingerprint + camera until it stopped bootlooping and let me in to enable OEM unlocking. That was the hardest part, and the flashing was straightforward
Just uploaded a new BLOD zip update with the latest AK3 support for multipartition patching, Lineage 18.1 Recovery, TWRP, Android 11 ROMs, and updated my dexed build of AOSP's boot_signer.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
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
Last edited:
So after many years of service, my phone reached its end too.
I can't bring it back to life with these workarounds so if anybody could help me, this is what I did.
My phone setup was:
-This LineageOS
-This Kernel
-Phone was encrypted
What I did after BLOD (at Google Logo):
Followed this thread and installed:
-Boot.img from Android O DP6
-TWRP version 3.1.1 linked there
-EX kernel version 5.03
Didn't solve. So I followed your thread and installed your twrp and the Workaround_Injector. Now the phone reaches the LineageOS loading logo but never ends (waited more than 20 mins).
Note that it's the loading before asking the decryption, so I think it's not able to find it. Twrp is able to decrypt correctly.
Any idea other than trying to flash the stock rom?
I can't bring it back to life with these workarounds so if anybody could help me, this is what I did.
My phone setup was:
-This LineageOS
-This Kernel
-Phone was encrypted
What I did after BLOD (at Google Logo):
Followed this thread and installed:
-Boot.img from Android O DP6
-TWRP version 3.1.1 linked there
-EX kernel version 5.03
Didn't solve. So I followed your thread and installed your twrp and the Workaround_Injector. Now the phone reaches the LineageOS loading logo but never ends (waited more than 20 mins).
Note that it's the loading before asking the decryption, so I think it's not able to find it. Twrp is able to decrypt correctly.
Any idea other than trying to flash the stock rom?
If you're able to boot twrp then it's not BLOD, so I'd probably do a format to see if that gets it booting the rest of the way.
Reapplyed the same LineageOS image that was already installed, reinstalled the Workaround_Injector and now it boots correctly.
For some reason some data got lost (eg contacts) but the phone is working smoothly.
Thanks!
For some reason some data got lost (eg contacts) but the phone is working smoothly.
Thanks!
Not worked for me, i tried everything, wipe, format, used last twrp.
Stock rom: Stop at boot logo
Pixel experience: Stop at boot logo
2 years ago, i download some files (i think march factory image and two more files) and i could pass the boot logo and use my phone, now i tried to upgrading to last stock rom or android 10 pixel experience but patch is not working
Stock rom: Stop at boot logo
Pixel experience: Stop at boot logo
2 years ago, i download some files (i think march factory image and two more files) and i could pass the boot logo and use my phone, now i tried to upgrading to last stock rom or android 10 pixel experience but patch is not working
Last edited:
I have a peculiar issue. so my device is bootlooping obviously so i try this patch. i follow the exact instructions of rom, kernel then blod fix but it still bootloops, twrp boots fine and doesnt ever freeze and i boot it direct off nand, what am i doing wrong?
the other fix with premade boot files no longer works as the file was pulled from mega so i cant perform it. any help?
the other fix with premade boot files no longer works as the file was pulled from mega so i cant perform it. any help?
If the patched TWRP boots and the latest official doesn't (when unpatched) then you must be suffering from BLOD.
The next question would then be if ROMs have changed their partition setups again on this device, and if so what ROM and kernel are you using?
Should I do this to prevent a BLOD? My 5x is working fine for now, but I want it to last as long as possible.
Thanks for your hard work!
Thanks for your hard work!
the best thing to prevent an irecoverable BLOD is to unlock bootloader so that if it happens, you can flash the fix. another good idea is to monitor temps so it doesnt get above anything like 50
Sorry for not getting back to you sooner but yes this is possible with the ElementalX kernel, just leave little cores as is and underclock big cores a little
You shouldn't flash the BLOD fix to prevent a BLOD. If anything it's worse because you put more strain on the little cores and you could kill them. So for now do this
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.
-
52Bootloop of Death (BLOD) Workaround AnyKernel3 zip for Nexus 5X
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-bullhead.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-up24Update 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-bullhead.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. (6734 downloads)
2019-10-30 - Update to AnyKernel3, add support for SAR and 2SI Treblized ROMs. (886 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. (428 downloads)
2020-02-17 - Update AK3 Core+Backend files to latest to fix SAR mount support in fragmented TWRP and Lineage 16+17 Recovery. (1188 downloads)
2020-05-25 - Update AK3 Core+Backend files to latest to improve SAR mount support in Lineage 17 Recovery and AVBv1 signing. (1276 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!9The 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.6Here'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-Injector5New year, new AK3 and BLOD Workaround fixes.
APEX mounting is added for recovery (thanks to @Zackptg5), 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 @fawazahmed0), 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
