Fix Nexus 6P Bootloop Issue

How to Fix Nexus 6P/5X Bootloop Issue or Bootloop of Death (BLOD)

Is your Nexus 6P not booting at all? It might be more than just a soft brick. This tutorial will try and help you fix the Nexus 6P/5X bootloop issue. If your device is affected too, then we have some good news for you. You can finally bid goodbye to the bootloop of death because XDA member XCnathan32 has come up with a solution to fix the dreaded bootloop problem on both the Nexus 6P and 5X.


Table of Contents

What is Bootloop of Death?

The dreaded “bootloop of death” or “BLOD” has cursed a notable amount of device owners using the Nexus 6P and Nexus 5X. The issue first came to notice during the fall of 2016, when users started reporting that their device abruptly entered a bootloop state and refused to boot at all. The affected users immediately rushed to online portals including Reddit and XDA for help but came around no possible solution.

Fix Nexus 6P Bootloop Issue

It wasn’t much later, that Google finally recognized the problem and made a statement on Reddit regarding the problem. The Google representative clearly mentioned that “For those of you that are currently experiencing this, please contact your place of purchase for warranty or repair options.”, which was definitely good news for those who had their devices covered under warranty.

Unfortunately, others were left in despair and had no choice but to use their expensive piece of technology as a mere paperweight. The problem was also escalated to the Google Issue Tracker but has since been tagged as “Assigned” and hasn’t received the deserved attention till now. The issue is not a minor one and has led the customers to doubt Google’s quality and customer support.

Fixing the Nexus 5X and Nexus 6P Bootloop Issue

While Google still fails to address the issue, XDA member XCnathan32, along with the help of another fellow member rchtk, has finally found a solution to fix Nexus 6P bootloop issue. While it won’t help you to fix the hardware issue itself but would help you bypass the BLOD and allow you to boot your ROM and Recovery again, at the expense of bit lost performance. Don’t worry, you will still be able to use the device as is.


Later on, XDA senior member squabbi improvised the solution and provided an easier method that would allow you to simply patch the current boot/kernel with the fix. The workaround injector was provided by XDA Recognized Developer/Contributor osm0sis. We highly appreciate their contribution.

What the fix does is, it disables the A57 cores of the SoC, which are the reason for the BLOD. So your device now will run on only the A53 cores, which may force you to compromise on the performance part (a bit!). It consists of a modified kernel file, that will boot your phone with only the dedicated A53 cores and thus fix Nexus 6P bootloop issue. If you further plan on flashing a ROM/kernel/root package, you can also flash the modified TWRP recovery image.

The solution will also work for any 5X suffering from the same problem. Make sure to use only the files for your device.


Make sure to fulfill all the requirements stated below before you head to the instructions to fix Nexus 6P bootloop issue.

  • Make sure that your phone is sufficiently charged.
  • Download and set up ADB and Fastboot tools on the PC.
  • Install appropriate USB drivers for your device. You can find them here.
  • Make sure that you have enabled OEM Unlock in ‘Settings’ > ‘System’ > ‘Developer options’. If you haven’t been able to enable the OEM Unlock toggle, then below are a few workarounds to give you enough time to boot the phone so that you can enable it.
    1. Supercooling the device in a freezer in a ziplock bag to keep out moisture,
    2. Superheating around the camera, and
    3. Letting the battery run all the way down before trying to boot



  1. Download the modified TWRP for your Nexus 6P or 5X, as well as the workaround injector ZIP file.
  2. Copy both the files to the folder on your PC where the Android SDK platform-tools are installed (e.g. C:\platform-tools).
  3. Open a PowerShell window in the same location. To do this, hold the SHIFT key on the keyboard and right-click on an empty space inside the folder.
  4. Select the ‘Open PowerShell window here’ option from the contextual menu.Open PowerShell on Windows
  5. Boot Nexus 6P/5X into the Bootloader Mode.
  6. Simply, press and hold the Volume Down and Power keys until you see the designated screen.Nexus 6P Bootloader Mode
  7. Connect the phone to the PC using a USB cable.
  8. Enter the command below to make sure that your device is being recognized by fastboot:
    fastboot devicesFastboot devices command
  9. The command should return a device ID. In case it doesn’t, make sure that you download and install the USB drivers properly.
  10. Your device’s bootloader must be unlocked in order for this method to work. If you already have it unlocked, then skip to step #14.
  11. Unlock your phone’s bootloader using the following command:
    fastboot flashing unlock
  12. As soon as you enter the command, your device will prompt with a message. Press either of the Volume keys to highlight “Yes” and then the power button to confirm bootloader unlocking.
    Bootloader unlock warning
  13. Flash the modified TWRP recovery:
    • Nexus 6P:
      fastboot flash recovery twrp-3.2.1-0-fbe-4core-angler.img
    • Nexus 5X:
      fastboot flash recovery twrp-3.2.1-0-fbe-4core-bullhead.img
  14. Do not disconnect the phone from the PC yet.
  15. Once flashed, tap the Volume keys until ‘Recovery mode’ appears on the bootloader screen.
  16. Press the Power button to confirm and boot into TWRP recovery.
  17. In TWRP, go to ‘Advanced’ > ‘ADB Sideload’ and swipe the button on the screen.
  18. Finally, enter the following command to install the workaround injector and fix Nexus 6P bootloop issue:
    adb sideload
  19. When flashed, reboot the phone by tapping the ‘Reboot System’ button.

Important Note: Always make sure to flash the BLOD fix (workaround injector) zip file at last if you install a custom ROM/kernel, re-install the stock firmware, or root packages like Magisk. That is because, in most of these cases, the boot image will be replaced and thus the applied fix too.

The first boot might take some time, so be patient. The Nexus 6P/5X should boot back to normal and you would be able to use it like before. That was easy and evenly satisfying, right? It feels so good that your money didn’t go in vain, after all. We sincerely hope that Google addresses the issue officially and gives it the attention it deserves. But until then, the exquisite XDA community has got your back.

For any help or questions, drop a comment below. Don’t forget to share this article on your social media and help others to fix Nexus 6P bootloop issue too.

//Source: 12


  1. Thank You very much for the instruction. My Nexus 5X was also a mere paperweight – now I have a cellphone again. Thank also to all mentioned XDA members. Great work.

    1. Peter, I am glad this guide worked out and allowed you to fix the issue on your Nexus 5X. Of course, the whole credit goes to the respective developers over at XDA.

  2. Hey Dhananjay,

    I have followed all of the above steps and they seem to work in theory but once I try rebooting it just keeps looping through the “Tour device software can’t be checked for corruption. Please lock the bootloader.” screen. How do I fix this or get around it? Thanks!

    1. Hi PM. If you performed the process correctly, your phone should be working again. Unless it’s beyond recovery anymore. Take a look at this comment of mine and go through more info regarding the BLOD.

  3. Hi Dhananjay, after flashing twrp I try to enter in the recovery, I see the teamwin screen, then I see this:

    Running OpenRecoveryScript

    Could not mount /data and unable to find crypto footer.
    Failed to mount ‘/data’ (Invalid agrument)
    Unable to recreate /data/media folder.

    Updating partition details…
    Failed to mount ‘/data’ (invalid agruments)

    Unable to mount storage
    Failed to mount ‘/data’ (invalid agruments)

    Full SELinux support is present.
    Unable to mount /data/media/TWRP/.twrps

    Running Recovery Commands
    Failed to mount ‘/data’ (invalid agruments)

    Formatting cache using make_ext4fs…
    Done processing script file
    Renamed stock recovery file in /system to prevent replacing.

    then the device reboots.

    (On boot, when bootloader is locked, I see “your device is corrupt. It can’t be trusted and and may not work properly” message, than stuck on Google logo)

    1. Hi Nicoo. First of all, please let me know if your phone’s bootloader is locked or unlocked?

    2. Hi Dhan, Thank you for the reply.
      The bootloader is unlocked as you explain in step #12
      (I enabled OEM Unlock just minutes before the device rebooted for the last time)

    3. Great! Keep it enabled, or none of the flashing will work.

      Now, here’s what I want you to do:

      1) Boot your phone into TWRP. Go to the ‘Wipe’ section and tap on ‘Format Data’. Then enter ‘Yes’ in the provided field to wipe the /data partition. Note that this will erase all the data on the phone, so make sure that you have a backup.

      2) Go to TWRP > Reboot and tap on ‘Recovery’. This will reboot your phone back into TWRP.

      3) Download the BLOD fix zip from above.

      4) Connect your phone to the PC while it’s in TWRP. Then go to the ‘Mount’ section and tap on the ‘Enable MTP’ button (if it’s disabled).

      5) Transfer the BLOD fix zip to the phone’s storage.

      6) Disconnect the phone and flash the BLOD fix zip file using the ‘Install’ menu of TWRP.

      Finally, reboot your phone into the OS and see if it successfully boots.

  4. Hie…Dhananjay
    tried fixing my nexus 6p using Nougat 4 cores images from using XDA tutorial….bt the device wldnt reboot…then i turned to your TWRP tutorial followed all steps…bt the phone wldnt go past the Google logo screen n tried wiping data in the TWRP recovery bt it ddnt change anything
    1)Wat is the way foward to go past the Google screen
    2)Upon flashing wth TWRP , does it mean the Nougat image was removed/overwritten during the process of TWRP flashing
    3)On entering into TWRP mode m asked of a password wth the top left corner written “mount decrypted data”……is this passwrd important as i always avoid it by clicking cancel button n then i move to the nxt page wth the Advance option……

    1. Hi Diamond. No, flashing TWRP doesn’t overwrite the Nougat OS. It only replaces the recovery partition.

      Were you able to successfully flash the BLOD fix zip via ADB sideload?

    2. Hie Dhanajay…The BLOD was succesful…how can u help me to get past the ‘Google’ logo stuck up????????

    3. Hi Diamond. In that case, I think the phone is beyond recovery.

      There are several stages of this bootloop issue and it can only be recovered to an extent. Please read this comment for more info.

      BTW, I accidentally stumbled upon your old comment and would like to ask a question. When you mentioned “tried wiping data in the TWRP recovery”, did you mean that you went to the ‘Wipe’ menu and wiped the ‘data’ partition individually. Or did you go to ‘Wipe’ > ‘Format Data’ and then entered ‘Yes’ to wipe the /data partition?

    4. I formatted data….bt i ddnt inject BLoD zip again…shld i d inject zip once more

  5. HI, my phone just went in a bootloop on its own few days ago, ever time I flash the BLOD it workd fine that day , but the next day its in a bootloop again, now I even tried the android 10 pixel, same thing it works fine the same day and next day its in a bootloop, the new problem today is it does not start in recovery no matter how many times I flashed it in fastboot , I did a clean install factory image and all, and then installed the twrp and BLod for both times old (Andr.9)and new blod (Andr.10), it just will not boot in recovery, it works fine in bootloader, but recovery I tried 4 different twrp FDE & FBE 3.2 or 3.3 nothing it just will not boot in recovery, is my phone dead ?

    1. Hi Samad. I am afraid, the device might be completely bricked. I am quoting a section of osm0sis’s BLOD XDA thread below, please go through it. I believe it will be more explanatory.

      Some important notes before going any further:
      1) Freezing at the Google logo likely points to it being perf cluster separation, but this could also be caused by other components separating.
      2) 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 AK2 and it still doesn’t work, sorry but your device is a brick.
      3) 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.
      4) 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 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.
      5) 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.
      6) EX Kernel does not support FBE on these devices because the EX zip patches the fstab forcefdeorfbe flag to encryptable.

  6. hi dhananjay,
    your download link is not working, please fix it so we can download the required software.

    thank you

    1. Hi Ejaz. I have mirrored the files and updated the links. For some reason, the BasketBuild servers are not reachable at all. You can also download the files from the device-specific XDA threads as well, links to which could be found at the bottom of this post.

  7. Your number 6 says to turn on nexus 6p in bootloader mode, it won’t come on, any suggestion. phone completely dead except when the red light comes on to charge it.

    1. Hi Joe. It may not be a BLOD after all. It’s a rare case of negative charge, that I have faced once on my Nexus 6P too. Try performing the steps mentioned here, it has helped others as well. You might need to do a couple of retries.

  8. Hi,

    I am not able to download the binaries from links. Is there any direct URL to download?

    Modified TWRP for Nexus 6P: twrp-3.2.1-0-fbe-4core-angler.img

    Workaround Injector:

    Thanks in advance.

    1. Hi Subrat! I have re-checked the download links and they are working fine. These are the direct links.

      Please try using a PC to download the files, if you are currently trying on the mobile.

  9. I followed a similar procedure with an extra step.
    1. recovery flash twrp-3.2.1-0-fbe-4core-bullhead
    2. Google stock image (bullhead-opm7.181105.004-factory-37df0288) installation
    3. Side load N5X-6P_BLOD

    Now I can see that animation of boot (4 circles with Google colors) on N5X. This animation is there for more than 40 minutes. Phone seems stuck in the animation loop. Not sure if I have to wait any longer.

    1. Hi Ramesh. I’ll quote my own reply that I did to another user with a similar problem.

      Hi, here’s what you should try.

      1) Go to the bootloader mode and connect the phone to the PC.
      2) Flash the factory image, but make sure to not let the phone boot into the OS.
      3) Flash the TWRP image and sideload the injector as stated above.

      Make sure that you don’t boot your phone into the OS until all the instructions are complete. The reason: As soon as the phone starts to boot, it will start to encrypt the /data partition.

      Once you do this, let me know if it works.

    2. Hi Joe. If you’re not able to enter Bootloader Mode on your phone, then it probably means that the hardware damage is beyond recovery (By using this method).

      The first few paragraphs of this post, you will get to know the reason behind my answer.

    1. Hi Jonathan. That depends on a few things:

      1) DM-Verity was triggered when you flashed the injector (You can try formatting data in TWRP and then flashing the injector again)
      2) The bootloop is beyond recovery (Very slight chance of this)

      In most cases, the first point is the reason. So, please give that a try.

  10. STEP 12 not working for me.
    PS C:\adb\platform-tools> .\fastboot flashing unlock
    FAILED (Write to device failed (Unknown error))
    Finished. Total time: 5.006s

    The previous step 10 does work as I know I can communicate to the phone, 6P in this case.

    I see contradictory comments to step 12 that says to unlock first you have to get the phone booted up(hair dryer). I cannot get mine to boot. The furthest I can get is pick your language screen so its not an option.
    So does the “fastboot flashing unlock” command work or not on a locked device?

    1. Hi. The method will only work if your 6P’s bootloader is unlocked. If you have ‘OEM Unlocking’ enabled in device settings, then use the ‘fastboot flashing unlock’ command to unlock the bootloader.

    2. Hi Dhananjay! You are doing great work! I have followed your advice but my phone is not booting to twrp recovery and instaed its showing message “your device cant be checked for software corruption. Please lock the bootloader”. I am able to establish connection between my PC and phone and was able to write recovery.

      Can you please tell me why I am not able to go to TWRP recovery mode with bootlocker unlocked?

      I am now flashing latest factory image available on XDA developer site and will try again.

      Thanks for your effort.

    3. Hi Varun. That situation is scary, I mean the “not able to enter recovery mode” thing. Please flash the factory image and try booting into the stock recovery first. See if it succeeds.

    4. I think there is no way left to recover this phone. Its not going to recovery. I have already decrypted my phone too but no success. It just dont go to recovery.

    5. before i was able to enter recovery mode, i think when i flashed first anlgler factory image, after that the phone stopped going to recovery mode.

  11. Best advice ever, thank you very much! Now my nexus is no longer a door clamp..
    I installed latest stock rom, then added your tips above, and voila!
    Finally, it’s alive!

    1. You’re welcome. I am glad that this guide is being more helpful to people than I ever thought.

  12. Thanks for the tip, I just followed and looks like it worked, I need a couple days to use it to tell though.

    One question, can I relock bootloader after this process, will the fix work then?

    and how can I relock bootloader?

    thank you.

    1. DON’T! Do not relock the bootloader. People who have their bootloaders locked have no way to recover their device if it goes into bootloop again.

    2. thanks a lot, it is running as is :), I am getting a new sim card for it to see how it goes throughout the day of normal use.

      the chance of bootloop happens again is 10%?

    3. I’m not into much of this stuff but i do it when it’s needed , just like my nexus 6p went to bootloop today and i first did flash it but it gave me the ” please relock the bootloader screen” now this time i tried to flash it with your files but it’s still not going away , even after doing the stock image flash

    4. Hi Danish. That could probably be because of the encryption. When you enter TWRP, go to ‘Wipe’ > ‘Format Data’ and enter ‘yes’ in the given field. Once formatted, simply flash the injector zip.

      Make sure that the phone doesn’t have a chance to boot into the OS until you flash the injector.

    5. the thing is i can’t go to recovery mode , after stock flashing it started showing me the screen where it asks to lock the device for checking of corruption and after locking the device it’s still bootlooping , no luck , i’m going to unlock it and use your files again for flashing and keep you updated

    6. after flashing the device numerous times , and locking it , it says your device is corrupt and can’t be trusted and gives me the link “”

      Did i do something wrong , should i or shouldn’t i have done the locking of the bootloader? Are there any chances

    7. I did try the hair dryer thingy and it worked but sadly i just made sure about the data being backed up and the “USB Debugging Enabled” and “Oem Unlocking permission ” , i wasn’t able to format it , i’m going to try the hair dryer thingy again after stock flashing , because it won’t let me go to any where without the stock flash , it just takes me to the “lock the bootloader” screen and “device is corrupt” screen

    8. Hi again. Make sure that you’re using the latest version of SDK tools (ADB and Fastboot) and then retry.

    9. from what i know i was using the latest SKD tools , but i’ll make sure once again and update you

    10. I have tried every thing numerous times now and I don’t think there’s a way now to fix my phone , is it?

    11. Until the phone turns on, even to the Google logo, I wouldn’t give up hope.

      Is your phone’s bootloader locked or unlocked?

    12. i wouldn’t either , it’s unlocked right now , but it shows “please lock the bootloader for checking of corruption” but when i lock the bootloader it says that your device is corrupted .

      when i stock flashed with latest file , and locked the bootloader , everything was gone but the bootloop itself , after that i flashed from your files the TWRP but it won’t let me go to the recovery mode on any condition , the “checking for corruption and the corrupted” screen goes away after the stock image flashing but as soon as i flash your custom TWRP for 6p , it shows the “please lock the bootloader for checking of corruption screen”

      i haven’t lost hope either , it’s currently unlocked

    13. as once after trying the hair dryer thing , it turned on but i think it should’ve been a lot better if i formatted the device and turn on the “OEM unlocking” and “USB Debugging” and tried your steps , still putting up theories , i hope even if i can get the device to turn on and keep it as my back up device , i wouldn’t be more happier , specially the camera and the speakers of that beast.. i don’t wanna lose this device

    14. I recently got home , and normally powered on my phone

      1st) It showed me the screen where it asks for “Please lock the bootloader for corruption checking.

      2nd) It went to google logo

      3rd) The screen went black and the notification led gave one blink of red light and it shut itself off.

      is that a new thing , what is this red light , i noticed that it was giving this red light yesterday as well , after this problem the red light blinked for like 4 times as well but now it’s not bootloaping but shutting itself off with red blink

    15. Hi. First off, do not lock the bootloader. The “please lock the bootloader for checking of corruption” message is normal. It will show up for everybody who has unlocked the bootloader and is there only for letting you know about it.

      Secondly, the files provided here will only work on a device with an unlocked bootloader. There’s no way to get it done on a locked bootloader.

    16. i meant , like i unlocked and locked bootloader few times

      So , what to do now , please help

    17. Okay. Do one thing, get in touch with me via our Facebook page, I will try and assist you personally.

  13. I have a question. My main issue is I have important days that it on the phone and not backed up anywhere else. I need that more than anything even the phone itself. I have the infinite bootloop and a locked bootloader. Can I still get my information?

    1. Sophia, although there’s no direct way to fix it. But you can use a hairdryer to heat up the phone (As suggested by a few readers here) to be able to boot it up for enough time to enable ‘OEM Unlocking’ in the settings. Once enabled, you can use the method provided here.

      Make sure that you do this in a controlled manner and ONLY if you’re comfortable with it. I or any of the users here will not be responsible if anything goes wrong while heating up the phone using a hairdryer.

  14. Thank you so much! I’ve tried other forums including the XDA one with no luck. Luckily I found this page and followed your steps and my Nexus 6P has been restored and works well so far. Hopefully the problem won’t pop up again. What are the chances of the problem recurring? Has anyone had the problem come back after successfully applying the fix?

    1. Hi Tom! Thanks for your kind words and I am glad it all worked out for you.

      As for your questions, there’s really no way to know if the problem to reoccur by itself. 90% it won’t unless you change the boot img (kernel). And even if it does, you can simply boot into the modified TWRP and flash the injector again.

    2. Thanks it WORKED!!!!! ReFlashing before adding the recovery file & adb sideload changed everything for me! the TWRP interface also really looks cool!

  15. i can’t install the workaround injector. when i do the adb sideload say to me that no device connected.

    1. Hi Pablo. There could be a few things that might have gone wrong here:

      1) You do not have the latest version of ADB on your PC.
      2) Your phone is not in Sideload mode in TWRP. You need to go to the ‘Advanced’ menu in TWRP and tap on ‘ADB Sideload’. Then swipe the button on the screen, connect the phone to the PC, and finally issue the command.

    2. C:\adb>adb sideload
      adb: sideload connection failed: no devices/emulators found
      adb: trying pre-KitKat sideload method…
      adb: pre-KitKat sideload connection failed: no devices/emulators found

      i download the adb and all the files from this page and do all the step indicated above.

  16. i need some help here…

    C:\adb>adb sideload
    adb: sideload connection failed: no devices/emulators found
    adb: trying pre-KitKat sideload method…
    adb: pre-KitKat sideload connection failed: no devices/emulators found

  17. Thanks so much! It looks like it worked! Thought I my phone sometimes automatically reboots every now and then.

    1. You’re welcome Abhineet! Yes, since this is a workaround, you might just expect some side effects. I am glad you were able to revive your phone.

  18. This is one of the best articles!! Thank you for writing it and updating it! Very much appreciated!! Got my 6p working again this weekend! Other than a crappy battery, it works like a charm!!

  19. Hi thanks for the great info but the problem is my Nexus 6 won’t unlock bootloader as oem unlock is not enabled what to do now help

    1. Hi Waqas. It is imperative to enable OEM unlocking and then unlock the bootloader to make this work. Please refer to the comment below by “SteveO”. He had the same situation and was able to boot his phone into the OS for just enough time to enable OEM unlocking. He did it by heating the phone.

      Of course, it is risking and I wouldn’t recommend it if you’re not comfortable with it.

  20. Hi, I flashed factory image of Nougat, the TWRP 4 core, and sideload the BLOD injector, so how do I know it’s working and running 4 cores not 8 cores? Where can I check? Thanks again, the BLOD resolved so far (after 3 days). I noticed that Google pay won’t allow me to set it up. It indicates I have a rooted or modified OS. Is this normal, otherwise, I have no issue on other apps that I installed.

    1. Hi Jason. If the phone turned on and is running, it means that it is running 4 cores. If you further wanna verify, then please use an app called ‘CPU Z’.

      As for Google Pay, simply use Magisk to hide root from Google Pay. I am currently using it myself on my rooted Pixel 2 XL.

    2. hello dhananjay, i followed your steps and every thing works again but only untill i reboot the phone and then it goes into BLOD again but if i apply the fix again it works also untill i restart the phone or it loses power.
      so i have to apply the fix every time i reboot the phone or it is out of charge, is there a way i can fix this for good ?

    3. Hi Salem, please try reflashing the factory image, then flash the given BLOD TWRP, post that Magisk (For root) and finally the BLOD patcher zip in that order.

    4. Same problem. I reached step 17 then bootloop again. My question is if I do factory image do I lose all data on y phone. I want the data more than anything

    5. Hi Ian. Yes, you’d lose all the data. But there’s a way to prevent it. Extract the downloaded factory image, then open the “Flash-all.bat” file via a text editor (E.g Notepad++). Then remove the “-w” flag from the “fastboot -w update” command. Save the file and then run it.

  21. Hi Dhananjay,
    SOrry to bug u again. I was going through the comments and i saw that there is one comment in particular that is having the same issue as mine. The guy with the name Andres . My phone is behaving in a similar manner. Plz suggest something if u get time.
    Thanks again.

  22. Dhananjay,

    Just wanted to thank you for the excellent article. There are numerous BLOD articles out there, but yours was by far the clearest and most helpful (not to mention the most up-to-date, as most of the others were devoted to previous Android versions).

    Here are a few comments that may help other users:

    * Like many Nexus 6P users, mine was quite stock when the BLOD hit. This meant my bootloader was locked and “OEM unlocking” in Developer Options was not toggled. I was able to get my phone temporarily booted by using a heat gun on the back of the phone for a few minutes (keeping it far enough away to make sure it didn’t get too hot) until it booted and I was able to toggle “OEM unlocked” and “USB debugging” in Developer Options. After that I shutdown and followed your steps exactly.
    * I had the same issue that MMK had where it initially said “Decryption Unsuccesful” and wouldn’t boot. I followed your advice and used TWRP to Wipe->Format Data, but I did NOT flash the ElementalX kernal. I believe my data is still encrypted (though could potentially be accessed due to the unlocked bootloader), but the phone has worked fine since.
    * I’ve disabled Automatic Updates (also in Developer Options), as I assume we want to avoid automatic security updates? I wasn’t sure if one of these would screw with the workaround injector. The 6P won’t be receiving these updates much longer anyway. The first (and only) time I tried to allow the system update, it took me to TWRP and I wasn’t sure where to proceed from there. Please let me know if I’m wrong here.

    Anyway, hope these help. Thanks again for saving my phone.

    1. Hey SteveO. Thank you for two things – (1) For the appreciation, means a lot, and helps me keep going, and (2) For providing your insight on how the method worked for you. I believe it will aid several readers looking for the answer to their questions.

  23. Hi Dhananjay
    I am having the same issue as IST. I am also just reaching till step 17 but then it does not go into twrp. I have even emailed u. Plz help

    1. Hi Dhananjay,
      I tried this command as well but it did boot into TWRP mode. All i see is “Your device software can’t be checked for corruption. Please lock the bootloader” and then below that it says “Press Power to pause boot”. and this keeps showing followed by the gooegle screen with black background. Plz helpme in this.

    2. Hi again. Please flash the factory image again, then repeat the TWRP booting command as I stated in the previous comment.

    3. Hi Dhananjay,
      I have repeated the steps more than once, but it does not help. All I see is the screen with that message and the Google sign. I have done the steps for like 3 to 4 to but all in vain. What could be the issue? Am I missing something?

    4. And just to make myself clear, when u say bootloader screen u mean reboot bootloader screen right? And flash the factory image again means the step number 14 right? If that is what j meant I have tried that also. But with no results. 🙁

    5. Hi again. What I mean is, you should first flash the factory image (stock firmware) on the device again. Once installed, you can start following the steps in this tutorial.

      But only this time, use the following command in step #14 instead of the one mentioned above:

      For Nexus 6P: fastboot boot twrp-3.2.1-0-fbe-4core-angler.img

      For Nexus 5X: fastboot boot twrp-3.2.1-0-fbe-4core-bullhead.img

      After flashing the stock firmware (factory image) and executing the commands, let me know if your phone enters TWRP recovery.

      P.S. By ‘bootloader screen’, I mean this: Click to view image

    6. Thanks a ton for Ur patience and quick response. I will do that. Do u have any commands for flashing the stock one? Will be very helpful .

    7. I downloaded a 7 ver and did flash-all. It showed that it’s reeboting the bootloader. And then used the command given by u. But still in the same loop. I don’t think my issue is gonna be fixed:( if possible if u have any stock flash command u suggest that. I can not use such an amazing phone except for a paper weight:(

  24. Hello, Dhananjay, I managed to proceed to step 17, after confirm the “Recovery Mode” with the power button, I pressed the power button and “UP” volume button trying to reboot into the TWRP mode but the phone went back to its deadly bootloop. I should mention that I have done all these back in Oct 2017 successfully and the phone revived, until this morning, suddenly the loop came back again. What would you be able to suggest me to try from here? Many thanks in advance for the help.

    1. Hi. Okay, so the first thing we need to try is booting into TWRP. Put the phone in Bootloader Mode and try using the following command:

      fastboot boot twrp-3.2.1-0-fbe-4core-angler.img

      See if it boots the phone into TWRP right away.

  25. Hi Dhananjay I have gone through the process 3 months for my nexus 6p and its working fine and it became too slow and iam not even able to use some of the features. Is there any possibility of making my processor turn to 8 core back?? And switching btwn the apps became a huge trouble …. Do u have any suggestions how to go through the flaws that iam facing…

    1. Switching back to 8 cores will simply be the start of the problem again, the phone won’t boot. To deal with performance issues, I suggest that you flash Franco’s kernel on your phone.

  26. Greetings,

    Thank you for your steps, they seem to be promising for me. I tried to follow your steps, and you mentioned that the start up (booting) after this takes a while. I just see a “Google” on my screen with an “unlock” icon in the bottom. I waited for 15 -20 minutes, nothing happened. How long can this take? Thanks1

    1. Hi, in most cases, this could be an encryption issue. Please see my reply below for “MMK”. Try that and please get back after it.

    2. I just followed the following step during the initial setup
      “In TWRP, go to ‘Wipe’ -> ‘Format Data’ and enter ‘yes’ in the provided field. This will format the /data partition.”

      But I didn’t follow the remaining, just because I didn’t know what those meant, or what I needed to do. Do I need to do do anything for those steps?

    3. Safder,

      I did the same thing you did (followed all of Dhananjay’s steps in the article, then formatted my data through TWRP). However I also stopped there and did NOT flash the ElementalX kernal. Everything has been working great for me so far (~3 weeks or so).

      Thanks again, Dhananjay, for the excellent article! There are numerous “fix your BLOD Nexus 6P” articles out there, but yours was by far the clearest (and most up-to-date, as most of the others were for previous Android versions).


  27. Hi,

    Thanks for the tutorial. I followed it to the letter up to the last step.

    However, when I reboot, I get this message

    ‘Decryption Unsuccessful

    The password that you entered is correct, but unfortunately your data is corrupt.

    To resume using your phone, you need to perform a factory reset, you’ll have an opportunity to restore any data that was backed up to your Google account.’

    When I click RESET PHONE button, it boots back to TWRP recovery.

    Please help

    1. Hello,

      In TWRP, go to ‘Wipe’ -> ‘Format Data’ and enter ‘yes’ in the provided field. This will format the /data partition.

      To maintain it, you will need to flash 4-core version of ElementalX kernel:

      NOTE: Make sure to perform all this before booting into Android, or else the phone will be encrypted again.

      Do let me know of the results. Good luck!

  28. Hi there! Firstly, thanks a lot for your detailed explanation – easy to read, easy to follow. 🙂

    I have a Nexus 5x, on Android 8.1.0, and installed security patch 5 today. Shortly after that, I got the dreaded BLOD. Now, I followed all the instructions up to step 20, reboot. And now I’m stuck on the colored circles Android boot animation – first time for 30+ minutes, I did the process again after that, and now I’m stuck there again – just to be clear, not another bootloop, but instead stuck on the boot animation!

    I’m suspecting it might be due to encryption – TWRP is notifiying me that my data is encrypted and asks me for a passwort. I can’t remember ever setting one though?

    I tried going through the comments and your replies, but I’m not sure if you gave any specific instructions for this situation. Can you help?

    Best regards and keep up the good work!

    1. Hi Dhananjay,

      I am facing similar issue what Jones mentioned about. I flashed my Nexus 5X with “8.1.0 (OPM3.171019.013, Jan 2018)” and executed all steps mentioned by you to fix bootloop. After reboot, my ph is stuck in Google animation. Is your fix target any specific build version of Android? Can you please suggest anyway to fix this issue? Thanks

    2. Hi Nishank. Please follow the instructions below, as I am quoting them from my own reply to another user.

      Hi, here’s what you should try.

      1) Go to the bootloader mode and connect the phone to the PC.
      2) Flash the factory image, but make sure to not let the phone boot into the OS.
      3) Flash the TWRP image and sideload the injector as stated above.

      Make sure that you don’t boot your phone into the OS until all the instructions are complete. The reason: As soon as the phone starts to boot, it will start to encrypt the /data partition.

      Do let me know the result.

  29. Bro i did everything as you mentioned above, but got no success in starting the phone…when heated, phone went in twrp recovery mode, also sideloaded BLOD Injector. But still my phone bootloops, help me bro..

    1. See my reply to user – “lalithsaikumar” below. Follow the same and let me know of the result.

  30. hello sir. i followed the above steps.
    1) my device was visible when i did fastboot
    2) i unlocked the boot loader.
    3)i used those images twrp and sideloaded the injector in twrp as mentioned. everything went successfully.
    previously the google image used to blink but now it got stuck there and nothing is happening. please help me. im bit poor in this software terminology. i want my nexus 6p back 🙁

    1. Hi, here’s what you should try.

      1) Go to the bootloader mode and connect the phone to the PC.
      2) Use the following two commands without inverted commas: “fastboot format userdata” and “fastboot format cache”
      3) Once done, reboot the bootloader: fastboot reboot-bootloader
      4) Flash the TWRP and sideload the injector as stated above.

      Make sure that you don’t boot your phone into the OS until all the instructions are complete. The reason: As soon as the phone starts to boot, it will start to encrypt the /data partition.

      Do let me know the result.

  31. Hi, first of all, thank you for all the time you have invested in helping us fixing the devices.

    The satus is the following, the pohone enters the boot loop, then the bootloader says this:

    BL: angler-03.74
    Baseband: angler -03.84
    Product/variant: Angler-VN2
    Serial Number: #device serial number
    CPU:MSM8994 0x20001
    eMMC: 32 GB Samsung
    DRAM: 3072MB Micron LPDDR4
    Console: NULL
    Battery: OK
    Device is: UNLOCKED
    Qfuse status: ENABLED
    Off-mode charged: Enabled
    Download mode: Enabled.

    I followed these steps.

    1) Download this modified TWRP and boot into it using:

    fastboot boot twrp-3.2.1-0-fbe-4core-angler.img

    but the phone didn’t manage to boot into TWRP mode, instead it went to “your device software can’t be checked for corruption..” message and then loop.

    because of that I haven’t been able to flash the second step file since I can’t acces the TWRP to side load or flash the second file

    2) Then flash the following ZIP file using TWRP:

    -I’m downloading the google factory Image that you recommended on a previous comment, flash it and see if these steps work after that.

    -Its curious that at the bootloader, when I choose to power off the device it turns off normally, but after a few seconds …it turns on again and then goes into boot loop again.

    I’ll see what happens after I have flashed the factory zip and let you know what happens.

    Thank you again for all your help Dhananjay

    1. Hi Andres, In the last few days, I had a word with one other user who has had a similar experience. At first, he was not able to boot the device into TWRP. Then some heating did the trick for him and he was able to carry out the full process.

      His phone booted fine as normal, worked for a few hours, but when into the bootloop again.

      Now, this is what worries me – Is the damage only recoverable to a certain limit? I just hope that the situation is not worsening within the hardware.

      I have been busy for the last couple of days. I will try and take out some time off and research through the XDA forums, to see if I can find a solution. I will keep you posted via the comments.

      As for the factory images, please let me know of the result.

  32. You rock! My Nexus 5X started bootlooping after a year. I re-flashed stock ROM, but nothing was working–until this!

    I couldn’t get ADB sideload to work in TWRP, but I just flashed the workaround using TWRP’s install feature and all’s well. Thank you so much!

  33. Hi Dhananjay,
    Yes the custom ROM worked perfectly.
    My A57 cores are turned off and the phone is working as intended. Thanks a lot for the patch and steps.

    Only problem I noticed is that phone is getting little warmer after decent usage, is that intended to happen ? Or some issue with my phone ?

    I still not evaluated the battery performance, is it improved after this for you ?
    Battery discharge is very rapid, 5% loss in 5 minutes of screen usage.

    1. Hi Naresh! First off, I am happy that it worked for you too.

      Please let me know which custom ROM you’re using. You can simply try a custom kernel such as Franco’s and see if it improves.

      Also, make sure to use an app to detect any kernel or app wakelocks that may be causing high drain. You can use Wakeblock for this.

    2. Hello Dhanunjay,
      The device suddenly crashed. May be i might have touched the security update in notification.
      It was bit hot, but when i reboot it the device stops at boot logo.

      I again tried to sideload the patch, which was successful but the device is still stuck at the boot logo as initial.
      I again followed all the steps, All are showing success but device does not go beyond boot.
      What could be the reason? Any way to fix this ?

    3. I couldn’t conclude anything If I don’t know exactly what happened. I would say, simply repeat the process. Only this time, install a custom kernel such as Franco Kernel and then patch it using the injector. Let me know of the results. Best of luck!

    4. Hello Dhanujay,

      1. I repeated the process after flashing Factory image.
      But it did not help, and the device stuck on the dots.

      2. i even installed Frankel Kernel but after the device stopped booting. So that did not help.

      3. In the below comments you have suggested for Magisk 16.4 ZIP for controlling bootloops due to dm verify.

      So once again i flashed the factory image.
      Then installed TWRP recovery.
      sideload Magisk
      Then sideload injector.
      These steps also did not work, and the device stuck on dots and reboots itself.

      One fine time after a day long rest i restarted the device, it was on for few seconds and then bootloop repeated.

      My query is,
      1. Is the bootloop still due to power failure to A57 cores, or is this a new bootloop ?
      2. Is there any way to check the cause for this ?
      3. Any more suggestions to get back the device from this stage ?


  34. Hello!

    The bootloop of death(BLOD) hit my phone and it’s been hard to tell if my phone is goint to survive.
    I tried all this stuff like flashing to factory configurations and installing the TWRP and so on…

    The thing is that my phone keeps rebooting and showing the unlocked bootloop warning. No matter how many times I try to go over this process, it just keeps on the BLOD.

    Please, help me to get my phone working again.
    I can provide videos and screenshots of what I´m doing.

    Matheus Esteves

  35. Thank you, Dhananjay, for helping me bring my Nexus 5X back from the dead.

    Given the cause of my difficulty, you may want to consider adding a note somewhere in your already excellent instructions about the initial state the phone must be in before starting, being sure the user data and cache aren’t encrypted before trying to do the twrp boot and injector sideload, and how to deal with it if they are encrypted, as mine was.

    Thanks, again, for your help.

  36. this really helped me, the cpu z shows that 4 of 8 cores are not working, but i can’t see much differents.
    Thank you very very much for help, you are the best 😀

    1. I am happy that it worked! The developer modified the rest of the 4 cores for optimal performance, so you shouldn’t notice much difference.

  37. My problem is that i can’t get into recovery, it just goes into bootloop again. Is there a solution

    1. Please try booting into TWRP first. Use the following command:

      For Nexus 6P: fastboot boot twrp-3.2.1-0-fbe-4core-angler.img

      For Nexus 5X: fastboot boot twrp-3.2.1-0-fbe-4core-bullhead.img

    2. after flashing the image file and then flashing the recovery, it wont boot into TWRP. any solution

  38. Hello Dhananjay,

    My Nexus 6P has also entered into bootloop issue.
    Look at the success rates in the comments, i would love to try this.

    But before proceeding i have an query, after doing this can i install the regular security patches that google delivers every month ?

    Does this fix only works with 8.1 or Can i upgarde my device to next android version when released ?

    Thanks in advance

    1. Hi Naresh. The patch works on monthly updates as well as custom ROMs.

      Yes, you will be able to update to the next monthly patch when released. All you will need to do is, manually install the OTA using “Flashfire” and simply flash the injector ZIP that is provided here. So basically, every time you update, you need to repeat the process.

    2. Hi Dhananjay,
      Yes the custom ROM worked perfectly.
      My A57 cores are turned off and the phone is working as intended. Thanks a lot for the patch and steps.

      Only problem I noticed is that phone is getting little warmer after decent usage, is that intended to happen ? Or some issue with my phone ?

      I still not evaluated the battery performance, is it improved after this for you ?

  39. My Nexus 5X suddenly developed the BLOD and I found your instructions for fixing it. I first used the “fastboot flash recovery”​ command to flash the bullhead TWRP image and then I used ADB to sideload the injector. They all completed successfully. But when I rebooted the system, it seemed to get stuck at the four-balls animation, which just kept going forever.

    Then, while reading the comments section, I saw you had suggested to someone with the same issue that they use the “fastboot boot” command with the TWRP image instead of flashing it, and then sideloading the injector. I tried this next, but had the same result when rebooting.

    Do I need to do something else to perhaps “undo” the initial use of the “fastboot flash recovery”​ command with the TWRP image?

    I am feeling quite over my head with most of this, but I am generally good at following direction, and have made it this far. I look forward to any suggestions you may have.

    Thank you for your help.

    1. Hi, I would suggest that you first take your phone to its factory state. That could be easily done via the factory image. Once flashed, use the fastboot boot command for TWRP and sideload the injector. Also, sideload the Magisk 16.4 ZIP after that, just to make sure that dm-verity doesn’t cause any bootloops.

  40. hi! i tried the steps you provided it worked for a couple of minutes then it freezes and start bootlooping again.. my device is nexus 6p. thanks

    1. Hi Miracle. Could you please explain what exactly happened? In detail perhaps?

      Several people here have got it to work by heating the phone around a specific point. However, that is not something I would personally recommend. Of course, I don’t want you to damage your device through that. If you’re comfortable, you can try, but note that I or any member/user of this site will not be held responsible.

    2. Hi sorry for the late response,,

      i did factory reset via stock recovery and i flashed this factory image via fastboot 8.1.0 (OPM2.171019.029.A1, May 2018).. and i also did the “fastboot flash recovery twrp-3.2.1-0-fbe-4core-angler”. and i did the sideload for nexus 6p injector. it booted up but after a couple of minutes it freezes up then went to bootloop again.i did a factory reset again and flashed the factory image. then i tried “fastboot boot twrp-3.2.1-0-fbe-4core-angler”. and sideloaded the injector for 6p again it booted up and after a couple of minutes it freezes up again then bootloop…

      thank you..

  41. mil gracias hermano hahahah, me funciono al 2do intento tuve que flashear la imagen original del 8.1, para mi nexus 5x, pero por le momento todo funciona a la perfección, inclusive su rendimiento es excelente

  42. Sometimes hard for me to follow all the details of this thread, so please bear with me and my question:

    My Nexus 5X went belly up yesterday, just keep displaying Google over and over. I can get into the bootloader, but OEM unlocking is not permitted and I am not able now to get into the OS to change the developer setting.

    I have not yet tried the hairdryer trick, but if that does not work and I am otherwise not able to get Android working long enough to change the locked setting, am I basically stuck with a non-functioning phone? No alternative work-around?


  43. I have a boot loop problem in my nexus 6p. I do not understand how to fix it. Actually i am unaware of above process i have no knowlegde to fix the issue. Can any one help me remotely over team viewer or webex.

    1. Hi Adnan, please reach out to me via the Facebook page. I will be glad to help you out personally if that’s the case.

  44. Hello Dhanajy.
    I’ve followed your guide carefully after getting the BLOD issue on my nexus 6P.
    Im having a problem going into recovery mode as it just get back to the reboot lop, therefore denying me form applying the 4cores workaround.
    Steps I’ve taken:
    Flash the first twrp image ( twrp-3.2.1-0-fbe-4core-angler.img ) – worked.
    afterwards trying to get into recovery mode to flash the workaround failed, because the recovery mode simply wont work. (not even by manually going there by holding power and vol up keys.) it just keeps on doing the BLOD.

    Noticeable mention: I was using a custom rom, and not the stock one, an O 8.0 custom rom.

  45. Hello, I’ve followed your step carefully after having my nexus 6P get the BLOD issue.
    i flash the first image for 6P fine ( twrp-3.2.1-0-fbe-4core-angler.img )
    this flashes fine, the next method is the tricky one as when trying to enter recovery mode through the bootloader (basically pressing the power button when recoery mode shows by using the arrows key) , I get the same BLOD effect.
    I simply cant get into the recovery mode in order to flash the workaround as it just take me back to the screen saying my oem is unlocked, followed by the google logo, then loops again.

  46. Thanks for this fix. Did it yesterday and everything is working great now.

    Nexus 6P Running Magisk

  47. I had a problem, my phone after google logo rebooting into twrp. Thank you Dhananjay.
    Phone: Nexus 6p, PC: Windows 7.
    Dowload links:
    1. Factory images – for my phone “angler” for Nexus 6P latest version 8.1.0 (OPM2.171019.029.A1, May 2018).
    2.Recovery – from above
    3. Workaround Injector – From above
    4. Magisk 16.4 –

    In post above show how unlock phone using fastboot.

    Step 1. Enter to the bootload on phone, connect to PC. In archive “angler-opm2.171019.029.a1-factory-bf17e552” using file flash-all.bat.
    Step 2. In cmd: fastboot flash recovery twrp-3.2.1-0-fbe-4core-angler.img
    Step 3. Enter to the Recovery->Advanced->ADB Sideload.
    Step 4. In cmd: adb sideload
    Step 5. In cmd: adb sideload
    Step 6. At the finish in recovery remove marks from proposed system and other files. Reboot phone. This should help 🙂

  48. Hi Dhananjay, thanks for this awesome tutorial. Sadly i have tried TONS of tutorials and i have experimented with my Nexus 6P but still i can’t fix it!

    I did everything what you said and it just didn’t work. I booted the last oreo 8.1 image and then TWRP, everything went fine but it didn’t work. My problem is that i can’t get into recovery, it just goes into bootloop again. So no TWRP and Magisk or anything.

    Help me please, or i’ll think i will bite this thing until it breaks haha.

    Also, only Fastboot recognizes my device, ADB has never recognized it. I don’t think it’s a problem because everything has worked anyway.

    1. Hi! I first followed your exact tutorial. And it didnt work. Then i installed the last oreo rom and then booted the TWRP image you provided with “fastboot boot xxx” and it didn’t work.

    2. Hi. So in your case, let us try otherwise. So, instead of simply booting TWRP, flash it using:

      fastboot flash recovery twrp-3.2.1-0-fbe-4core-angler.img

      Then see if you’re able to boot the phone into TWRP recovery. If it does, then let me know so that I can help you further.

    3. Thanks Dhananay. Your original post had the same command, nevertheless i did the same thing again and flashed TWRP as recovery but it didn’t work 🙁

    4. Hi again. Could you please share the screenshot for when the TWRP flash command is entered and the result that it shows?

    5. Are you sure that you’re using the latest version of the ADB/Fastboot tools?

    6. Hi! I downloaded the platform_tools you provided us, and after it didnt work i also downloaded SDK. So yeah 🙂

  49. I have bootloop and y had tried revive my phone. After several manual incuding this post my nexus 6p try to start google logo and reboot into twrp. Pls help 🙂

    1. Hi Rostislav, did you flash any mod (ZIP file) before the bootloop happened?

    2. No, this is not the first time the phone has rebooted after a few photos taken and the last will fatal.

    3. Yes please, write it down so that I can have a better idea of your current situation.

      Do you have a backup of all your data on the phone? Also the internal storage?

    4. Unfortunately, i have not backup.
      First what i did it’s hard reset.
      After hard reset i tried this guide video to step 6 where are flashing N2G48B_4Cores.img, at this moment my phone stuck on google logo for an hour.
      Next my turn is used this and your’s post, and a both try my phone rebooting into twrp after trying load.
      P.S. I’m from Ukraine and sorry if I bad explain 🙂

    5. Hi, both the tutorials you linked above were later discontinued by XCnathan32. The development was further carried over by squabbi.

      The files I have provided in this post are the latest one, so it shall work. Now, here’s what I want you to do:

      1) Flash Android 8.1 Oreo factory image (Latest one)
      2) Temporarily boot modified TWRP using: fastboot boot twrp-3.2.1-0-fbe-4core-angler.img
      3) Sideload “Magisk 16.4 ZIP” and “” files in TWRP recovery (Advanced > ADB Sideload).

    6. Hello, i followed your’s instruction and after two hours later still looking marshmallow boot animation, it’s normal? 😀

    7. Awesome!! After second try my nexus revive. Thx you for helping, good man 😀

    8. I am glad that it finally got resolved. Could you please state the exact steps that you followed? It seems like many other people have found themselves in the same situation.

  50. Hi Dhananjay,
    I’m facing some issues with my Nexus 5X.
    Actually the only way I’m able to boot correctly is:
    – Flash stock image 7.1.2 N2G48C
    – Flash TWRP version 3.1.1
    – Flash 3.10.73-ElementalX-N5X-5.03

    In this situation Android asks if I want to go with Android 8.0 but during its setup, the phone restarts and the setup fails. So I’m wondering If I can run Android 8.1 as well.
    If I flash latest stock image + twrp + ElementalX, it bootloops :/
    The odd thing is that if I only flash stock image, I cannot get into stock recovery.
    Following your guide I tried to flash “twrp-3.2.1-0-fbe-4core-angler.img” (link found in the comments), flashing succeded, but if I go to Recovery Mode from bootloop, it goes into the “Your device software cannot be checked for corruption” screen and it gets stuck there. To solve it I reflashed twrp 3.1.1…
    How to solve it?


    Bootloader UNLOCKED
    Android 7.1.2
    Kernel: 3.10.73-ElementalX-N5X-5.03 aaron@bella #1
    Build: N2G48C

    Bootloader info:
    Variant: bullhead LGH791 32GB
    Hw version: rev 1.0
    Bootloader version: BHZ11m

    1. Hi Davide, you will first need to start off by flashing the latest Android 8.1 Oreo factory image on the phone. You can grab it from the official Google page here. Once you have flashed it and booted your device, please let me know here so that I can guide you with further steps.

    2. Hi Dhananjay ,
      I followed your suggestion (starting with 8.1 and twrp + N5X-6P_BLOD_Workaround) and it WORKED like a charm!
      I think the original mistake was due to your comment here:
      I got TWRP there thinking that it was a common TWRP for 5X and 6P but it’s not! I found you linked a dedicated TWRP version for 5X in the topic and it worked.

      Thank you very much!

    3. Hi Davide, I am glad that everything’s working fine now. And you’re welcome! Enjoy your device now.

  51. May I say thank you for the above guide, after getting lost for a couple of days looking at other guides I found this and its nice and easy to follow. I had my phone on OEM lock but blasting the phone with a hairdryer and starting it from fully off broke bootloop for 10 mins allowing me to get to the developer options and switch off OEM lock. The rest is simple, thank you once again!

    1. You’re welcome, Luke! I can see that the hairdryer trick is working for many out here.

      I am glad that it worked for you! Thanks for your kind words.

  52. Hey man!

    So I have been at lost for the past week trying to fix my nexus.

    Originally I was using the 4 core modified boot.img stuff. It worked for a like a day or so (with random restarts), then it started bootlooping again.

    Ok so now I did your guide, and I get stuck at the 4 circles animation.

    This is the -exact- process I did.

    – Flash angler-opr6.170623.013 thru the Hesienberg guide from XDA (meaning instead of just running flash-all, I did each .img file in the order from his guide on flashing to stock).

    – Go into the STOCK recovery and do a wipe cache/factory reset (just to make sure there was NOTHING third party on it)

    – Flash Recovery TWRP_3.2.1.0-4Cores-ANGLER (now this is a different one that I grabbed from that XDA bootloop fix thread, it isnt the same one as the one you just posted. Well, in name at least.)

    – ADB sideload N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed

    And I am still bootlooping, up to the circle animation, freeze, and re start the boot.

    I am so confused as it seems to work for everyone BUT me.

    Any ideas?

    1. I have a trick, that might help.

      Repeat the complete process again, and this time, instead of flashing the modified TWRP, boot it temporarily using: fastboot boot twrp-3.2.1-0-fbe-4core-angler.img

      Make sure to enter the command correctly. Once in TWRP, make sure to NOT ALLOW MODIFICATIONS. Simply keep the it READ-ONLY.

      Then, go to “Advanced” > “ADB Sideload” and use the following command on the PC to sideload the BLOD patcher ZIP: adb sideload

      Actually, what we are trying to do here is to avoid any chances of dm-verity causing the bootloop.

  53. Hello !

    My Nexus 5X was stuck on bootloop. I followed your instructions and I am now stuck on the little color dots animation.

    Do you have a solution to this problem ?

    Thanks so much.

    1. Please make sure that you temporarily boot TWRP (as mentioned in the post above) rather than permanently flashing it.

      Then simply sideload the BLOD patcher ZIP.

  54. Hello,

    My Nexus 5X started to bootloop yesterday. I tried to save it by following the steps of the Unblod method, it didn’t work.

    So I found your method, which kinda worked, my phone doesn’t bootloop anymore, but now when I boot it, it stay stuck on the little colored dots animation for hours.

    Do you know what I can do ? I saw some people had the same problem in the comments, but all of them had a Nexus 6P.

    Thanks for your help

  55. Thank you so much for this bit. I was scouring through the internet to find a fix for Android O 8.1. Managed to somehow boot into the device to turn on OEM unlocking, post which I flashed the 8.1 May 2018 factory image, applied the TWRP and then sideloaded the boot patch.
    Carrying on from the original thread where this all started ( ), just wanted to know if the patch not only disables the BIG cluster, but also optimizes the LITTLE cluster that all the remaining 4 are used by the CPU i.e. instead of using 1 core for all foreground tasks, does the patch modify the ramdisk to utilize all 4 cores more effectively? Really appreciate if you could clarify or let me know if there is another patch down the line to do so
    Also, any idea how OTA updates work after this? Would OTA updates come down? And if updated, would I need to repeat the process all over again?

    1. Hi Prasanna. First off, I am glad that you got to fix your device with this. From what I have seen only a few people were able to boot into the OS for enabling OEM unlocking. If you don’t mind, could you please share how you did it? Is there any specific trick that did it? It would be really helpful for other users here.

      Over to your question. The injector ZIP does the same patches as implemented by XCnathan32. Which means, all the 4 cores are used efficiently. But just in case you want to tweak it by yourself or want to improve performance, you can simply install a custom kernel via TWRP and flash this patch over it.

      Next, the OTA. If your phone is completely stock, without root, custom kernel, TWRP, etc, then yes you shall be able to take OTAs normally. But then again the device wouldn’t boot after that. Which means, you will need to flash the custom kernel (optional) and BLOD patched again after installing the OTA.

      What I would recommend is, make use of apps like Flashfire. You can simply download the OTA ZIP, Magisk ZIP (optional), custom kernel (optional), and BLOD patcher (Mandatory) and add them to the flashing queue in Flashfire. This will automate everything for you.

    2. Hey, I just used a hair dryer under the optical zoom area for 5 minutes and i was able to boot it up somehow to unlock the bootloader

      It’s been a month since I applied the TWRP and Injector. But now, I am stuck in a bootloop AGAIN! I have used both the fasboot flash recovery twrp-3.2.1-0-fbe-4core-angler.img and fastboot boot twrp-3.2.1-0-fbe-4core-angler.img and I CANNOT get into TWRP! Can you please help? Is there a newer TWRP that I would need to flash?

    3. Nothing happens really. I just see the bootloader unlocked warning message, followed by the Google logo – and repeat. It’s the same as the normal bootloop. I am unable to get into TWRP to apply Magisk or the injector again. I am also using the latest June 2018 ADB and fastboots btw


    1. Thank you so much Renish, for such a big and nice comment. I am glad that the tutorial was able to help you revive your phone.

  57. Hi Dhananjay!
    thanks for your help……
    but one question: does this method delete all data (apps and media) from my phone?

  58. Hi Dhananjay,

    My nexus 6p went into bootloop in Jan 18 and since then I have been looking for a reliable solution so that I can save the pictures on the device at least, mostly from my baby’s first birthday. Developer option is locked on my phone so would the flashing erase the data on the device? Is sideloading to a higher version when it’s available a solution? Think the problem started when I updated 8.1.1. I will be really thankful for your advice as the pictures have a lot of emotional significance for me. Thanks.

    1. Then, I don’t think it would be possible for you to try this method. But I do have a suggestion, and there’s a slight chance that it may help. Download the full OTA from here and try sideloading it using the stock recovery.

  59. My Nexus 5x Bootlooped on August,2017. I followed the XDA solution but after doing so it didn’t fix rather shown a message that says” Your phone cant be checked for corruption, please lock the bootloader” Its been dead since. Is there anything I can do about that? Thanks.

    1. Hi, the error you’re talking about is just a prompt and shouldn’t disable the phone from booting. That error is for everyone who has an unlocked bootloader.

      Now, here are a few things that I want to know first:

      1) Does your phone get stuck on the boot animation?
      2) Are you able to boot your device into bootloader mode? (Power off, and then use the Volume Down + Power button)

      Let me know so that I can help you further.

  60. hello broo and thank you for this usfull work ,
    i have problem my phone keep boot to recovery mode by its self i did all the instrection but nothing happend

    1. Hi, benaissa. Are you sure that it is the widespread bootloop issue due to the hardware failure, or are you talking about a regular bootloop?

  61. HI
    I downloaded the twrp file and moved to the adb folder, then entered the above mentioned command.
    I got google logo after that red color dot on the screen and device rebooting again and again.
    Unable to enter into twrp.

    1. Hi again, kindly let me know what it shows in the PowerShell/CMD window when you enter the command.

    2. HI
      Sorry for the delay.
      please find the below mentioned data.
      cmd : fastboot boot twrp-3.2.1-0-fbe-4core-angler.img
      downloading ‘boot.img’…
      OKAY [ 0.459s]
      OKAY [ 0.686s]
      finished. total time: 1.145s

    3. The command is fine. Please try a different port on the PC or try an alternate PC/laptop for the purpose.

      I have faced this as well while trying to temporarily boot TWRP on my Pixel 2 XL. For me, a couple of more tries work just fine.

      Are you sure that the phone’s bootloader is unlocked?

    4. Yes, unlocked
      I tried different ports and from other computer as well. Didn’t work.
      Can i download and install a fresh 8.1 factory image from google developer site?
      or can you recommend me any factory image which you know that worked for others.

    5. Just download the latest one from the official developers portal and flash it.

    6. Finally i got the phone working.
      I tried multiple times by using different ports and different pc/laptop – Didn’t worked for me. Unable to boot in twrp.

      Then i heated the phone by using hairdryer, and i tried to boot into twrp- finally i can enter into twrp. Next i flashed the blod zip file then reboot.

      Finally booted into android 8.1 .

      Thanks you for your help

  62. Hi Dhananjay
    It was really nice of you helping other. I appreciate that.
    I tried your steps, i am unable to boot into twrp. Still stuck with bootloop.
    BL : angler-03.79
    Baseband : angular-03.85
    Product : ANGLER-ROW-VN1
    Device is unlocked.
    Please guide me.

    1. Hi, kindly download the modified TWRP from here.

      Then put your Nexus 6P in bootloader mode and execute the following command to temporarily boot the modified TWRP image:

      fastboot boot twrp-3.2.1-0-fbe-4core-angler.img

      As soon as you execute the command, the phone shall reboot into TWRP recovery. Once it does, please revert back here and I will help you further with the instructions.

  63. i followed your steps for my nexus 6p..and it was struck on boot animation…the animation keep on running from 40 mins… what to do bro

    1. Hi Anudeep, kindly check the method I mentioned above to the user ‘sarah’. Let me know how that works out for you.

    2. MY Nexus6p was got struck in boot animation…its been in it for 2 hrs. I would like to know reason wts the matter …and it worked fine for one hour and came back to same position

    3. I followed your steps for my nexus 6p..and it was struck on boot animation…the animation keep on running from 40 mins… what to do bro

    4. What I did is
      -I downloaded the 8.1 version angler zip for nexus 6p file from google developer downloads.
      -I flashed it using fastboot method including system and vendor images.
      -After that I followed ur process of flashing TWRP and ADBsideloading the file that you gave.
      -I even checked the version of the file that 4core patch and angler file version.
      -After the whole process do we need to flash with any rom??
      -Please mention the complete process to get rid of this problem…

      Thank you

    5. Hi Anudeep, did you make sure that the injector ZIP was correctly flashed without any errors? Kindly cross check. The injector ZIP does all the job, it takes your current boot.img and patches it for 4 cores.

    6. Updating partition details…
      Unable to mount storage
      Full SELinux support is present.
      Starting ADB sideload feature…
      Installing zip file ‘/sideload/’

      N5X/6p BLOD Workaround Injector Add-on

      AnyKernel2 by osm0sis @ xda-developers

      Checking device…

      Installing kernel…

      Patching boot partition…
      Patching recovery partition…

      Formatting Cache using make_ext4fs…


      This is the log that I got after sideloading … it was succesfull naa…?

    7. Yes, that seems to be successful. Okay, so here’s what I would suggest. First, reboot into stock recovery and perform a factory data reset. Then temporarily boot TWRP (Do not flash permanently, see the command below) and then sideload the injector ZIP.

      fastboot boot twrp-3.2.1-0-fbe-4core-angler.img

    8. I need a small suggestion … should I continue using this amazing phone or should i exchange it….are we sure that we will not get any problems later again…
      And thank you very much for you suggestions…

    9. Hi again. First of all, I am glad that it worked out for you. P Beta is not officially available for the device. I am not sure of any unofficial build though. If there is, then kindly point me to it.

      Next, it depends what you’re planning to exchange it with. The 6P is undoubtedly a great phone, I still have it as my secondary. So, if possible, kindly let me know which device are you exactly planning to exchange it with?

  64. Hello Dhananjay,

    I’ve tried all you fixes and sadly doesn’t work. I can’t go to TWRP after flash or boot recovery? I have unlocked bootloader and adb conected, but cannot boot modded recovery?


    1. Hi Milos, what exactly do you get when you execute the command in the PowerShell/CMD window?

      1) Put your device into Bootloader mode
      2) Connect it to the PC
      3) Open the PowerShell/CMD window in C:\adb directory (Or in whichever folder the ADB/Fastboot binaries are present).
      4) Execute the following command: fastboot devices

      Does that return a device ID?

  65. doesn’t work for me.
    Nexus 6p
    BL: angler-03.77
    Baseband: angler-03.84
    Product/variant : ANGLER-ROW-VN1

    any suggestion?

    1. Hello Schnieder,

      Kindly have a look at the comments above. In one of them, I have mentioned an easier revised version of the fix. Try that and please let me know so that I can update the post as well.

    1. Not really Shubham. I have seen people who were able to power on their device for just enough time to enable ‘OEM unlocking’ in the settings.

    2. Hello, same issue with mine. unfortunately it cannot power on for me to enable OEM unlocking. Is there any way to work around this?
      Please help.

    3. I am afraid not. The only way is to first enable OEM unlocking by getting into the OS.

    4. I was able to get my phone out of the bootloop just temporarily, by placing a hair dryer next to the right side of the phone while it was bootlooping. It finally started booting up after about 10 minutes, and gave me enough time to get into Developer Options to allow OEM Unlock

    5. Thank you for the tip jayzim! I believe it will come handy to the readers here.

  66. I’m still not getting a device ID back, even though I downloaded the adb and made sure to get the drivers, even going so far as to download the android maker studio. Not sure what I’m doing wrong.

    1. Hello Conrad, where exactly did you place the extracted Android SDK tools package?

    1. Brilliant, thankyou!
      I havemanaged to boot with the twrp and am through to the Team Win Recvoery Project system.
      Can you explain to me how to Flash using the workaround injector addon from the interface menu please?
      Is it an ADB sideload I need to use?
      Many thanks for your help!!

    2. Hi. Yes, you can simply use ADB sideload option in TWRP and sideload the file using command-line. I hope you know how to use it? If not, then please reply back.

    3. Thanks so much. I have been trying to sideload for a while now and it keeps failing to start. I’m not sure why

    4. What error does it show exactly? Kindly share a screenshot via imgur[dot]com.

    5. Can I do this method if I’m running a custom ROM? (Lineage 15.1 which is Android Oreo 8.1)

    6. Hi Nikunj, yes it should work without any problems. Kindly refer to the method mentioned 4-5 comments above this one. Let me know if it works, so that I can update the post as well.

    7. I installed both the modified TWRP and the workaround injector and it booted up on the first go. I’ll let you know if the phone stays in a working mode and for how long. Thanks for your help and your reply, it is very much appreciated.

    8. Thanks Nikunj. I am soon going to update this post with the latest method (Which I feel is also the easiest one). Good luck with your phone.

  67. I have no way to screengrab it, but have copied it in below:

    “Data successfully decrypted, new block device: ‘/dev/block/dm-0’
    Updating partition details…
    Successfully decrypted with default password.
    Updating partition details…
    Full SELinux support is present.
    MTP Enabled
    Starting ADB sideload feature…
    Installing zip file ‘/sideload/[’

    N5X/6p BLOD Workaround Injector Add-on

    Any Kernel12 by osmosis @xda-developers

    Installing kernel…
    Recovery busybox setup failed. Aborting…
    Updater process ended with ERROR: 1”

    1. UPDATE: After several attempts it finally worked and I then went on to install Copperhead OS.
      Thankyou so much for your help!!!

    2. Sorry for the delayed comment. I am glad it worked out for you. I will update this post with the new links and steps.

    3. Hi,

      It does not work for me since it shows me that OEM unlock is not allowed.

      Any idea of what to do?

    4. In that case, you will not be able to unlock the bootloader. Thus you cannot flash any of the workaround files.

      Do you have TWRP installed on your device by any chance?

  68. Hi, It doesn’t work for me either on my Nexus 6p. I previously used Copperhead OS. Followed your steps including TWRP and nothing worked, so I then prepared to try it all over again and install Copperhead over the top, but still stuck in bootload.
    Would be so grateful if you could help me!
    Many thanks

  69. doesn’t work for me.
    Nexus 6p
    BL: angler-03.79
    Baseband: angler-03.85
    Product/variant : ANGLER-VN2

    any suggestion?

    1. Hi, please share your device name and firmware version that is installed on it.

  70. Damn! thank you so much… I love you <3 you save my life, as we can say in spanish; mil gracias!
    thank you thank you thank you thank you a lot

    1. I am glad you got it to work Rodrigo! I will update the link right now. Thank you for sharing.

    2. I have thus oroblem google, google, google akways. I do not have any idea how to do the above procedure. Can anyone help me remotely over team viewer or webex

Leave a Reply

Your email address will not be published. Required fields are marked *