The Nexus 6P is a pretty good smartphone that was released back in September 2015. Unfortunately, late-last year many users have reported that their Huawei Nexus 6P has entered into a bootloop stage where the device was not able to pass the “Google” Logo that appears after turning it on.
Reports were suggesting that this was caused by a software issue, which you couldn’t fix even after factory resetting the device. Unfortunately, Google has never released a fix for the bootloop issue and instead it stated that customers should “RMA” their devices for a replacement.
However, if the warranty has expired for your device you’ve come to the right place. It seems that XCnathan32 and rchtk from XDA Developers have managed to release a fix for this problem.
In order to install it on your device, you will first need to download and flash a few modified system image files, which were causing the bootloop issue by disabling the larger CPU cluster. It is not yet known why the larger CPU cluster was not allowing the device to function properly, but the modified boot.img file will allow the device to use only four of its eight CPU cores. With that being said, your device will finally function, but you will notice a decrease in performance.
Nexus 6P: Specifications
- Dimensions: 159.3×77.8×7.3mm;
- Weight: 178 grams;
- Display: 5.7-inch AMOLED that supports a resolution of 2560×1440 pixels at 518 ppi;
- Chipset: Qualcomm MSM8994 Snapdragon 810;
- Processor: quad-core Cortex A53 CPU clocked at 1.55GHz and a quad-core Cortex A57 CPU clocked at 2.0GHz;
- RAM: 3GB of RAM;
- Graphics card: Adreno 430;
- Internal storage: 32GB, 64GB or 128GB;
- Cameras: 12.3MP (primary – rear side) and 8MP (secondary – front side);
- Battery: 3450 mAh (non-removable).
What are your thoughts about the Nexus 6P bootloop fix that has just been released by the developers from XDA Developers?
Get more stuff like this
in your inbox
Subscribe to our mailing list and get interesting products and updates to your email inbox.
Thank you for subscribing.
Something went wrong.