Nexus 6P Bootloop Issue, There’s Finally A Fix

In 2016, many folks reported of a software issue where the Huawei Nexus 6P entered a bootloop stage where the device wouldn’t proceed past the “Google” Logo upon firing up the device. Not even factory resetting the device would fix the issue.

An unofficial fix has come from XDA members: XCnathan32 and rchtk. The fix required you to download and flash a few modified system image files which circumvent the bootloop by disabling the larger CPU cluster. For some reason (which is still unknown), the larger CPU cluster isn’t let the phone function properly, so the modified boot.img file only lets the phone use four of its eight CPU cores, which means you’ll notice much lower performance.

Regarding the bootloop issue, Google never issued an official fix but instead stated that customers should RMA their bootlooping devices for a replacement. Of course, those who were out of warranty or were in an unserviceable area can at least revive their dusty paperweights using this workaround.


  1. Download the latest ADB and Fastboot binaries and extract them to an easily accessible folder on your computer. You can download the latest ADB and Fastboot binaries using these links. These download links will remain static, but Google will periodically update the referenced file with the latest binaries as they go live.
  2. Download and install the Google USB Driver if you are running Windows.
  3. Download N2G48B_4Cores.img and save it to the same directory where you saved the ADB and Fastboot binaries.
    • Optional: If you want to use TWRP recovery on your fixed Nexus 6P, you will need to use a modified version. Download twrp3_1_1_4Cores.img and save it to the directory where you saved the ADB and Fastboot binaries.
    • Optional: If you want to speed up your fixed Nexus 6P, you can flash a modified version of XDA Recognized Developer flar2‘s Elemental X Kernel. Download and save it to your downloads directory.
  4. Plug your phone in to your computer.
  5. Open up a command prompt or terminal in the same directory where you saved the ADB and Fastboot binaries. On Windows, you can easily do this by holding shift and right-clicking, then selecting “open command prompt here.”
  6. Enter the following command: fastboot devices
  7. If you see your device’s serial number, you are ready to move on. If not, you will need to try re-installing the drivers.
  8. Important: your phone’s bootloader MUST be unlocked in order to flash these modified images. If your bootloader is already unlocked, skip the following 2 steps.
  9. Start the process to unlock your phone’s bootloader by entering the following command: fastboot flashing unlock
  10. Using the volume and power keys, confirm that you want to unlock the bootloader. THIS WILL WIPE EVERYTHING ON YOUR PHONE’S INTERNAL STORAGE. But it’s either this or deal with a multi-hundred dollar brick. Your choice!
  11. Now enter the following command to flash the modified boot image: fastboot flash boot N2G48B_4Cores.img
    • Optional: If you want to flash TWRP, then enter: fastboot flash recovery twrp3_1_1_4Cores.img
  12. Reboot your phone by typing: fastboot reboot
  13. After some minutes (it may take awhile), you should see your phone’s boot animation and eventually the lockscreen. Congrats, you’ve saved your phone!
  14. Optional: If you want to improve the performance and you flashed TWRP, copy the modified Elemental X kernel over to your phone’s storage, boot into TWRP, and flash the custom kernel. You can choose to overclock the little cluster during setup to squeeze a bit more performance out of your phone as well.

XCnathan32 does note that root works by flashing SuperSU in TWRP. He also offered a few suggestions to get more performance out of your device, such as disabling animations or changing the CPU governor to an aggressive one. While he tested the modified boot.img on a stock ROM, other ROMs such as PureNexus should be able to work as well. You just need to make sure you are running a kernel that’s modified to use the four little cores.

This is an impressive development and Nexus 6P owners are now able to revive their excellent device, even if there are compromises to this solution. Given there are many users who were unable to get their units replaced under warranty, they can now put the phone to good use instead of having it sit dead in a corner or drawer.

Check out the Via link for more context about the bootloop issue on XDA-Developers or hit up the Source link for the full tutorial.

To Top