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

Search This thread

osm0sis

Senior Recognized Developer / Recognized Contribut
  • Mar 14, 2012
    14,538
    32,753
    Halifax
    GT-i9250
    Nexus 7 (2013)
    Bootloop of Death (BLOD) Workaround AnyKernel3 zip for Nexus 5X

    Guys.. bad news.. my Nexus 5X just got hit with the BLOD. :crying:

    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. :good:
    Original thread posts: Nexus 5X, Nexus 6P

    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.
    For further details on these methods check out the original threads by @XCnathan32, linked in the "Thanks" section.

    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
    1) Download and unzip platform-tools for your PC from https://developer.android.com/studio/releases/platform-tools.html
    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), or​
    2b) 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), or​
    3b) 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

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

    Attachments

    • twrp-3.2.1-0-fbe-4core-bullhead.img
      19.5 MB · Views: 9,430
    • N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip
      1.8 MB · Views: 1,151
    Last edited:

    osm0sis

    Senior Recognized Developer / Recognized Contribut
  • Mar 14, 2012
    14,538
    32,753
    Halifax
    GT-i9250
    Nexus 7 (2013)
    Update Flashing Instructions
    • Keep N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip on your device sdcard, henceforth referred to as BLOD AK3 zip
    The correct manual order for a clean flash is: ROM -> root -> custom kernel -> BLOD AK3

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

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

    Good luck and enjoy!
     
    Last edited:

    en_jo

    New member
    Jul 27, 2018
    1
    0
    hey,

    my nexus 5x unfortunately started having the bootloop issue yesterday.
    i tried fixing it using your instructions, now it's stuck in the colored boot animation. it's not frozen, but just stays in the animation forever (i waited already more than 1.5 hrs).

    do you have any suggestions what i could try?

    thanks in advance!
     

    osm0sis

    Senior Recognized Developer / Recognized Contribut
  • Mar 14, 2012
    14,538
    32,753
    Halifax
    GT-i9250
    Nexus 7 (2013)
    hey,

    my nexus 5x unfortunately started having the bootloop issue yesterday.
    i tried fixing it using your instructions, now it's stuck in the colored boot animation. it's not frozen, but just stays in the animation forever (i waited already more than 1.5 hrs).

    do you have any suggestions what i could try?

    thanks in advance!

    Does the 4core recovery work? If so, try flashing the lastest factory image, then the BLOD AK2 zip again and see if that helps. If not, you're out of luck. :(
     

    Jatsu

    New member
    Jul 29, 2018
    1
    0
    Hey! Thanks for your instructions, im unbold my nexus 5x! But now my wifi doesn't work. Can it be problem with your img? Bluetooth works by the way.
     

    osm0sis

    Senior Recognized Developer / Recognized Contribut
  • Mar 14, 2012
    14,538
    32,753
    Halifax
    GT-i9250
    Nexus 7 (2013)
    Hey! Thanks for your instructions, im unbold my nexus 5x! But now my wifi doesn't work. Can it be problem with your img? Bluetooth works by the way.

    I don't have an img, I patch whatever's there. What ROM are you using?

    Dirty flash your ROM, rename the BLOD AK2 zip to test-debugging.zip, flash and upload the debug.tgz it creates and I'll take a look.
     
    Last edited:

    ediofelipe

    New member
    Jul 7, 2016
    1
    0
    Hey! Thanks for your instructions.

    In my the error appears:
    adb: sideload connection failed: closed
    adb: trying pre-KitKat sideload method...
    adb: pre-KitKat sideload connection failed: closed

    Do you have a solution?
     

    osm0sis

    Senior Recognized Developer / Recognized Contribut
  • Mar 14, 2012
    14,538
    32,753
    Halifax
    GT-i9250
    Nexus 7 (2013)
    Hey! Thanks for your instructions.

    In my the error appears:
    adb: sideload connection failed: closed
    adb: trying pre-KitKat sideload method...
    adb: pre-KitKat sideload connection failed: closed

    Do you have a solution?

    Are you booted into 4core TWRP? Did you go to the Advanced | ADB Sideload page and swipe to start the sideload mode? Make sure your PC has adb sideload drivers installed? Try a different USB cable? Try adb pushing the file to your device and flashing it from there instead?


    Side note to all: BasketBuild is having some down time so I've mirrored the uploads in the OP. :good:

    Edit: And BasketBuild is back! :)
     
    Last edited:

    Chiwidude

    Member
    Oct 17, 2014
    5
    1
    Thanks

    So, first of all i would like to tell u that, I thank u a lot for your amazing work, i finally got my nexus 5x out of bootloop after a year:D:D
    Got to say i thought i would never get it back from there. Also i would like to get some advice:
    Currently im running 7.1.2, i wanna download the OTA for oreo, my question is:
    As i dont have it rooted, what i should do is download and install it. then make this:
    "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-AK2-signed.zip" into the cmd prompt"

    Or what do u suggest??
    Also it would be better if i get root and then get the OTA? in that case, if i root it should i flash again your patch? or is not necesary.
    So Thanks again, for all your work.
     
    • Like
    Reactions: tuhinxp04

    Lossyx

    Senior Member
    Jan 14, 2014
    1,443
    588
    OnePlus 7T Pro
    I can't seem to boot into recovery or normally boot(black screen but fastboot mode works fine), with or without the 4core fix (recovery + boot img). Also, to enter fastboot I have to hold power down and volume for a minute or so. Does this mean I'm out of luck?
     
    Last edited:

    andQlimax

    Senior Member
    Jul 29, 2010
    2,559
    1,003
    Rome
    With stock kernel it doesn't work right? Only custom kernel?
    I'm trying to resurrect an old 5X. So i Should:
    - fash latest factory image on fastboot
    - flash suggested twrp on fastboot
    - flash custom kernel, like Franco
    - adb sideload in recovery the fix
    - reboot and hope ? :)


    Thanks

    EDIT: I'm stuck at Google logo, when I reboot to suggested recovery above. It's stuck at Google logo and rebooting also when it is switched off and I plug the wall-charger. Only bootloader mode works! What to do?
    EDIT 2: at the end everything works now and boots! Let's see if it stays like this!
     
    Last edited:

    andQlimax

    Senior Member
    Jul 29, 2010
    2,559
    1,003
    Rome
    Everything worked for couple hours without issues, then it bootloop again. The strange thing is that it doesn't power on anymore after some reboot, tried everything, long press for 10 seconds, 30 seconds, either power only and power + volume buttons.. It switch on only if I disconnect and reconnect the battery by opening the device,it starts but bootloops and then again no sign of life after some bootloops. I remember it happened the same when it died the first time almost 1 year ago I believe. Not even the bootloader come up when it is in this strange state, unless I disconnect the battery.
    With the fix I thought it would keep staying alive.. But no luck seems
     

    fricco1983

    New member
    Aug 10, 2018
    2
    0
    ok, perfect, everything work....but if I check cpu I see 4 CPU* 1.44GHZ + 2CPU stopped, instead 4 CPU* 1.82GHZ + 2CPU*1.44GHz. Why Did u change frequency of 4 cpu, lowering them?
     

    osm0sis

    Senior Recognized Developer / Recognized Contribut
  • Mar 14, 2012
    14,538
    32,753
    Halifax
    GT-i9250
    Nexus 7 (2013)
    ok, perfect, everything work....but if I check cpu I see 4 CPU* 1.44GHZ + 2CPU stopped, instead 4 CPU* 1.82GHZ + 2CPU*1.44GHz. Why Did u change frequency of 4 cpu, lowering them?

    I didn't and it doesn't.

    Oh and as a general FYI to everyone, if I don't respond to your question/post it's because it's already answered in the OPs.
     
    • Like
    Reactions: ok_then_so

    Srjrn

    Member
    Apr 5, 2017
    9
    3
    Thank you very much for your work. My phone went into a bootloop today and flashing stock rom didn't work. Your guide was well-written, easy to follow and most importantly worked like a charm!
     

    Tabs78

    Senior Member
    Dec 8, 2007
    638
    23
    Hi when i make the 7th point of guide my PC open the zip file.
    Which is my error?


    Inviato dal mio iPhone utilizzando Tapatalk
     

    Gazza2907

    Member
    Jan 31, 2013
    5
    1
    It's alive!

    Thanks, man. It worked great and was really easy. I will happily make a donation!

    Initially my 5X was booting to the Google logo and then rebooting, forever.

    I am hoping this will last me until the end of the year when I will get a OP6T or Pixel 3 maybe.

    Is there any advice for maintaining the device in this state? For example doing a factory reset, flashing a custom ROM?
     
    • Like
    Reactions: ok_then_so

    CLPose

    Senior Member
    Jan 7, 2015
    726
    376
    Buenos Aires
    Thanks, man. It worked great and was really easy. I will happily make a donation!

    Initially my 5X was booting to the Google logo and then rebooting, forever.

    I am hoping this will last me until the end of the year when I will get a OP6T or Pixel 3 maybe.

    Is there any advice for maintaining the device in this state? For example doing a factory reset, flashing a custom ROM?

    Hi! Use some kernel manager to make sure your N5X doesn't turn big cores on, and keep it as cool as possible. Good luck!
     
    • Like
    Reactions: Gazza2907

    Top Liked Posts

    • There are no posts matching your filters.
    • 51
      Bootloop of Death (BLOD) Workaround AnyKernel3 zip for Nexus 5X

      Guys.. bad news.. my Nexus 5X just got hit with the BLOD. :crying:

      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. :good:
      Original thread posts: Nexus 5X, Nexus 6P

      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.
      For further details on these methods check out the original threads by @XCnathan32, linked in the "Thanks" section.

      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
      1) Download and unzip platform-tools for your PC from https://developer.android.com/studio/releases/platform-tools.html
      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), or​
      2b) 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), or​
      3b) 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

      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-up
      23
      Update Flashing Instructions
      • Keep N5X-6P_BLOD_Workaround_Injector_Addon-AK3-signed.zip on your device sdcard, henceforth referred to as BLOD AK3 zip
      The correct manual order for a clean flash is: ROM -> root -> custom kernel -> BLOD AK3

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

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

      Good luck and enjoy!
      9
      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. :D
      6
      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
      5
      New 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
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone