• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[Guide] Fix for Nexus 6P Bootloop of death | 8/22 - Android O Working

Search This thread

SlimSnoopOS

Senior Member
Jan 29, 2011
8,052
3,348
So I think my 6p is totally wiped because my stepson tried flashing via adb fastboot stock rom several times. To no avail. And reading the op here, it says booting from. So what does that mean for someone who's phone is wiped? I mean do I just follow the op, flash boot IMG, then twrp & then kernel? What about the vender IMG? I guess I've probably confused myself more then needed. My bootloader is unlocked. Thanks for help

Sent from my LG-ls990 using Tapatalk

Flash every partition using fastboot. Now fastboot flash the Oreo 4 core boot image that matches your OS.

Sent from my Nexus 5X using Tapatalk
 
  • Like
Reactions: aheeejd

aheeejd

Senior Member
Jan 5, 2012
4,362
1,960
off the coast o the kontiki!
Flash every partition using fastboot. Now fastboot flash the Oreo 4 core boot image that matches your OS.

Sent from my Nexus 5X using Tapatalk
Sorry, I'm an old man who wishes his stepson was home from college. Let me see if I've got this, go to Google & dl a 7.1.2 stock img, then dl the proper vender img, & then get latest twrp & flash those via adb fastboot? Then flash the modded boot img from here (12.55 mb, is that correct?) the 1st dl in the list in op? Then flash modded twrp? Then try & boot up? Again sorry, I read op a few times & have read the 1st 10 pages. Thank you for your help

Sent from my LG-ls990 using Tapatalk
 

SlimSnoopOS

Senior Member
Jan 29, 2011
8,052
3,348
Sorry, I'm an old man who wishes his stepson was home from college. Let me see if I've got this, go to Google & dl a 7.1.2 stock img, then dl the proper vender img, & then get latest twrp & flash those via adb fastboot? Then flash the modded boot img from here (12.55 mb, is that correct?) the 1st dl in the list in op? Then flash modded twrp? Then try & boot up? Again sorry, I read op a few times & have read the 1st 10 pages. Thank you for your help

Sent from my LG-ls990 using Tapatalk

It's ok. Personally, I think the OP needs to be fleshed out with more info. Yes, do exactly that. If it's easier, follow section 9 of this guide below:

https://forum.xda-developers.com/showthread.php?t=3206928

Use the 4 core boot image and 4 core TWRP recovery for their respective partitions. Then try booting up or boot directly into the modified TWRP.

Sent from my Nexus 5X using Tapatalk
 
  • Like
Reactions: aheeejd

NoobInToto

Senior Member
Dec 4, 2013
856
246
Coimbatore
So I think my 6p is totally wiped because my stepson tried flashing via adb fastboot stock rom several times. To no avail. And reading the op here, it says booting from. So what does that mean for someone who's phone is wiped? I mean do I just follow the op, flash boot IMG, then twrp & then kernel? What about the vender IMG? I guess I've probably confused myself more then needed. My bootloader is unlocked. Thanks for help

Sent from my LG-ls990 using Tapatalk

Um, is the phone bootlooping? I believe you did not mention if it is bootlooping. Anyways, since the data is gone, you can try the following (assuming you have a windows pc) if your n6p is bootlooping:
1. Download factory image (android oreo can be used) from : https://developers.google.com/android/images
2. Download platform-tools from : https://developer.android.com/studio/releases/platform-tools.html
3. Download the modified boot.img from first post in this thread ( you can try the image for oreo)
4. Unzip the platform tools.
5. Unzip the factory image in the folder of platform tools containing adb.exe , fastboot.exe etc
6. Connect the phone in fastboot mode to your windows pc and double click on the flash-all.bat script in the unzipped folder.
7. Connect the phone in fastboot again. With the modified boot.img in the same folder as flash-all.bat script, adb.exe etc... open a command prompt in this location (shift +right click or open cmd prompt and navigate to directory)
8. Flash the boot.img using the command prompt. If the modified boot image is named Oreo4Cores.img, then the respective fastboot command is
Code:
fastboot flash boot Oreo4Cores.img
9. The phone should boot up on rebooting if the fix works.

You still have not said if your n6p is bootlooping or you just have a corrupted phone. If your phone aint bootlooping and you just need to clean flash, then follow steps 1-6.
 
Last edited:

koxx.dta

Member
Jan 11, 2011
23
0
37
cen-cal
getting an error when trying to install oct security update, is it because i am using Oreo4Cores.img?
 

Attachments

  • securityfail.png
    securityfail.png
    109.7 KB · Views: 86
Last edited:

draroraab

Member
Dec 1, 2014
5
3
Upgrading to Android 8.0

Hi, I've been using the modified EX-kernel for 4 cores version 4.11 on stock 7.1.2 47W build. I've TWRP recovery installed. I just flashed the Ex Kernel 5.03 successfully. Is it safe to directly flash the Android 8.0 boot.img(modified, as provided by you) over the 47W build? I ask since there's 48B and C builds in between. Also, thanks again for working on this. Really appreciate it.
 

aheeejd

Senior Member
Jan 5, 2012
4,362
1,960
off the coast o the kontiki!
Um, is the phone bootlooping? I believe you did not mention if it is bootlooping. Anyways, since the data is gone, you can try the following (assuming you have a windows pc) if your n6p is bootlooping:
1. Download factory image (android oreo can be used) from : https://developers.google.com/android/images
2. Download platform-tools from : https://developer.android.com/studio/releases/platform-tools.html
3. Download the modified boot.img from first post in this thread ( you can try the image for oreo)
4. Unzip the platform tools.
5. Unzip the factory image in the folder of platform tools containing adb.exe , fastboot.exe etc
6. Connect the phone in fastboot mode to your windows pc and double click on the flash-all.bat script in the unzipped folder.
7. Connect the phone in fastboot again. With the modified boot.img in the same folder as flash-all.bat script, adb.exe etc... open a command prompt in this location (shift +right click or open cmd prompt and navigate to directory)
8. Flash the boot.img using the command prompt. If the modified boot image is named Oreo4Cores.img, then the respective fastboot command is
Code:
fastboot flash boot Oreo4Cores.img
9. The phone should boot up on rebooting if the fix works.

You still have not said if your n6p is bootlooping or you just have a corrupted phone. If your phone aint bootlooping and you just need to clean flash, then follow steps 1-6.
Yes the phone is bootlooping, does nothing but Google screen with lock on bottom (unlocked) & loops to the screen saying your data can't be checked or something like that. I can boot to dl mode.

So thank you so much for spelling this out for me. I managed to get fastboot & adb on windows PC today. Not sure when I'll have time to sit down & do this but will for sure report back on how everything goes. Thank you again sir

Sent from my LG-ls990 using Tapatalk
 
  • Like
Reactions: NoobInToto

NoobInToto

Senior Member
Dec 4, 2013
856
246
Coimbatore
getting an error when trying to install oct security update, is it because i am using Oreo4Cores.img?

That, and also because you probably used twrp.
Find the proper way to update using ota by searching this thread for my post on 'updating without losing data'.

---------- Post added at 06:40 AM ---------- Previous post was at 06:40 AM ----------

Yes the phone is bootlooping, does nothing but Google screen with lock on bottom (unlocked) & loops to the screen saying your data can't be checked or something like that. I can boot to dl mode.

So thank you so much for spelling this out for me. I managed to get fastboot & adb on windows PC today. Not sure when I'll have time to sit down & do this but will for sure report back on how everything goes. Thank you again sir

Sent from my LG-ls990 using Tapatalk
You are welcome. Tell me how it goes.
 
  • Like
Reactions: aheeejd

koxx.dta

Member
Jan 11, 2011
23
0
37
cen-cal
If you read the error message, it would be self explanatory. It would read something along these lines: unexpected contents found in ..... /boot
And that is because of the modified boot partition
there is no error message just says "error" above open android, thanks though.

your method requires root? im trying to avoid root
https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279/post73829233#post73829233
 
Last edited:

NoobInToto

Senior Member
Dec 4, 2013
856
246
Coimbatore
there is no error message just says "error" above open android, thanks though.

your method requires root? im trying to avoid root
https://forum.xda-developers.com/nexus-6p/general/guide-fix-nexus-6p-bootloop-death-blod-t3640279/post73829233#post73829233

Initially it requires root. You can untick reroot in flashfire to get unrooted boot image and system after the update(systemless SuperSU sits in boot partition. My method requires you to flash original boot partition, thus wiping root)
Tip: you can extract the boot image of any current build completely online using offcloud, google drive and cloudconvert(inside gdrive)
 
Last edited:
  • Like
Reactions: koxx.dta

sunil1982

Senior Member
Oct 1, 2012
218
45
Kalyan
Hi al
Can anyone help my with this I tried everything to boot phone atleast once but no luck yet as my bootloader is locked but sometime I am able to go to system recovery so if I downloaded OTA files and replace the boot.img with modified one will i be able to apply OTA via ADB sideload..
 

nopulse76

New member
Oct 5, 2017
2
1
After updating to the new Oreo update, my phone was in the constant Google logo loop. I was ****ting bricks. After finding this site, I can't believe I managed to fix it through trial and error. Here's what I did.

Since I couldn't get my phone past the Google logo loop, I grabbed a hair dryer and heat my phone when the phone was looping. Eventually my phone went past the Google logo and started the Android animation. It finally booted up and I could log in, but not for very long so you have to be quick. If the phone crashes and loops again, heat it up again.
Once you're about to boot into your phone, IMMEDIATELY go to Settings then System, then click About Phone and tap on Build Number 7 times. Once you have unlocked the Dev mode, go back and go into the Developer Options and unlock both OEM unlocking and USB debugging.

At this time while you're in your phone, backup what you can or sync everything!

Then reboot your phone, when you see the Google logo, hold down the power button and decrease volume button. This should boot you into the bootloader screen etc.

Next go to https://redirect.viglink.com/?format=go&jsonp=vglnk_150722508560622&key=f0a7f91912ae2b52e0700f73990eb321&libId=j8eoox2p01000n4o000DA2tibhbwi&loc=https%3A%2F%2Fforum.xda-developers.com%2Fshowpost.php%3Fp%3D74041226%26postcount%3D1408&v=1&out=https%3A%2F%2Fdeveloper.android.com%2Fstudio%2Freleases%2Fplatform-tools.html&ref=https%3A%2F%2Fforum.xda-developers.com%2Fnexus-6p%2Fgeneral%2Fguide-fix-nexus-6p-bootloop-death-blod-t3640279%2Fpage141&title=%5BGuide%5D%20Fix%20for%20Nexus%206P%20Bootloop%20of%20death%20%7C%208%2F22%20-%20Android%20O%20Working%20-%20Post%20%231408&txt=https%3A%2F%2Fdeveloper.android.com%2Fstudio...orm-tools.html and download the tools. Make a folder under your C: called adb. Extract the platform-tools-latest-windows.zip into the adb folder.

Next Press the windows key button your keyboard, under search, type command prompt and open command prompt. In command prompt make sure you're in the C:\adb directory you made.

In the C:\adb directory, type fastboot flashing unlock. It should give you a msg on your phone asking if you want to unlock it. Using your volume buttons, select yes and press the power button on your phone. Your phone should be now unlocked.

Next go to Go to https://redirect.viglink.com/?format=go&jsonp=vglnk_150722358296214&key=f0a7f91912ae2b52e0700f73990eb321&libId=j8eoox2p01000n4o000DA2tibhbwi&loc=https%3A%2F%2Fforum.xda-developers.com%2Fshowpost.php%3Fp%3D74041226%26postcount%3D1408&v=1&out=https%3A%2F%2Fdevelopers.google.com%2Fandroid%2Fimages&ref=https%3A%2F%2Fforum.xda-developers.com%2Fnexus-6p%2Fgeneral%2Fguide-fix-nexus-6p-bootloop-death-blod-t3640279%2Fpage141&title=%5BGuide%5D%20Fix%20for%20Nexus%206P%20Bootloop%20of%20death%20%7C%208%2F22%20-%20Android%20O%20Working%20-%20Post%20%231408&txt=https%3A%2F%2Fdevelopers.google.com%2Fandroid%2Fimages and download 8.0.0 (OPR6.170623.019, Sep 2017) image which is called angler-opr6.170623.019-factory-9fd72ad6.zip When its downloaded, extract the angler-opr6.170623.019-factory-9fd72ad6 into your adb folder. Right click on flash-all and click open. It should now be flashing the image to your phone. Once its done, the window should say press any button to close the window.

Next go to https://redirect.viglink.com/?format=go&jsonp=vglnk_150722328747813&key=f0a7f91912ae2b52e0700f73990eb321&libId=j8eptfpd01000n4o000DA2tibhbwi&loc=https%3A%2F%2Fforum.xda-developers.com%2Fnexus-6p%2Fgeneral%2Fguide-fix-nexus-6p-bootloop-death-blod-t3640279&v=1&out=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D0B7TP6GXR0wAVWVlvckU5LUtkYkE&ref=https%3A%2F%2Fforum.xda-developers.com%2Fnexus-6p%2Fgeneral%2Fguide-fix-nexus-6p-bootloop-death-blod-t3640279%2Fpage141&title=%5BGuide%5D%20Fix%20for%20Nexus%206P%20Bootloop%20of%20death%20%7C%E2%80%A6%20%7C%20Huawei%20Nexus%206P&txt=Download and download the Oreo4Cores.image Copy the Oreo4Cores.image to your adb folder.

Press the windows key button your keyboard, under search, type command prompt and open command prompt. In command prompt make sure you're in the C:\adb directory you made.

In the C:\adb directory, type fastboot flash boot Oreo4Cores.img.

Once done, type fastboot reboot and your phone should boot up without any issues.

I just want to thank all those that made the fix to the brutal google loop. You guys are heroes!
 
Last edited:
  • Like
Reactions: ShadowVlican

NoobInToto

Senior Member
Dec 4, 2013
856
246
Coimbatore
The TWRP image linked above, for 4 cores, prompts me for a password upon loading. Yes my device is encrypted, however my pw did not work.

What gives?

Only a factory reset worked for me. Sadly, that is the only fix I know when twrp asks for a password that is not the same as encryption password.

---------- Post added at 06:03 AM ---------- Previous post was at 05:59 AM ----------

Hi al
Can anyone help my with this I tried everything to boot phone atleast once but no luck yet as my bootloader is locked but sometime I am able to go to system recovery so if I downloaded OTA files and replace the boot.img with modified one will i be able to apply OTA via ADB sideload..

You will need to heat up the phone to boot in. Try targeting the spot between fp sensor and camera using a hair dryer for upto 10 minutes, or using an electric heating pad (the one used for medical purposes, to be applied to body for relief from muscle spasms and whatnot) for up to 25 minutes.

Once you are in, activate developer options (if not already done) by tapping few times on build number in about phone section. Then in Dev options, toggle on OEM unlocking.
 

dvdvrhs

Member
May 31, 2012
15
1
Saint Louis
After updating to the new Oreo update, my phone was in the constant Google logo loop. I was ****ting bricks. After finding this site, I can't believe I managed to fix it through trial and error. Here's what I did.

Since I couldn't get my phone past the Google logo loop, I grabbed a hair dryer and heat my phone when the phone was looping. Eventually my phone went past the Google logo and started the Android animation. It finally booted up and I could log in, but not for very long so you have to be quick. If the phone crashes and loops again, heat it up again.
Once you're about to boot into your phone, IMMEDIATELY go to Settings then System, then click About Phone and tap on Build Number 7 times. Once you have unlocked the Dev mode, go back and go into the Developer Options and unlock both OEM unlocking and USB debugging.

At this time while you're in your phone, backup what you can or sync everything!

Then reboot your phone, when you see the Google logo, hold down the power button and decrease volume button. This should boot you into the recovery screen etc.

Next go to https://redirect.viglink.com/?format=go&jsonp=vglnk_150722508560622&key=f0a7f91912ae2b52e0700f73990eb321&libId=j8eoox2p01000n4o000DA2tibhbwi&loc=https%3A%2F%2Fforum.xda-developers.com%2Fshowpost.php%3Fp%3D74041226%26postcount%3D1408&v=1&out=https%3A%2F%2Fdeveloper.android.com%2Fstudio%2Freleases%2Fplatform-tools.html&ref=https%3A%2F%2Fforum.xda-developers.com%2Fnexus-6p%2Fgeneral%2Fguide-fix-nexus-6p-bootloop-death-blod-t3640279%2Fpage141&title=%5BGuide%5D%20Fix%20for%20Nexus%206P%20Bootloop%20of%20death%20%7C%208%2F22%20-%20Android%20O%20Working%20-%20Post%20%231408&txt=https%3A%2F%2Fdeveloper.android.com%2Fstudio...orm-tools.html and download the tools. Make a folder under your C: called adb. Extract the platform-tools-latest-windows.zip into the adb folder.

Next Press the windows key button your keyboard, under search, type command prompt and open command prompt. In command prompt make sure you're in the C:\adb directory you made.

In the C:\adb directory, type fastboot flashing unlock. It should give you a msg on your phone asking if you want to unlock it. Using your volume buttons, select yes and press the power button on your phone. Your phone should be now unlocked.

Next go to Go to https://redirect.viglink.com/?format=go&jsonp=vglnk_150722358296214&key=f0a7f91912ae2b52e0700f73990eb321&libId=j8eoox2p01000n4o000DA2tibhbwi&loc=https%3A%2F%2Fforum.xda-developers.com%2Fshowpost.php%3Fp%3D74041226%26postcount%3D1408&v=1&out=https%3A%2F%2Fdevelopers.google.com%2Fandroid%2Fimages&ref=https%3A%2F%2Fforum.xda-developers.com%2Fnexus-6p%2Fgeneral%2Fguide-fix-nexus-6p-bootloop-death-blod-t3640279%2Fpage141&title=%5BGuide%5D%20Fix%20for%20Nexus%206P%20Bootloop%20of%20death%20%7C%208%2F22%20-%20Android%20O%20Working%20-%20Post%20%231408&txt=https%3A%2F%2Fdevelopers.google.com%2Fandroid%2Fimages and download 8.0.0 (OPR6.170623.019, Sep 2017) image which is called angler-opr6.170623.019-factory-9fd72ad6.zip When its downloaded, extract the angler-opr6.170623.019-factory-9fd72ad6 into your adb folder. Right click on flash-all and click open. It should now be flashing the image to your phone. Once its done, the window should say press any button to close the window.

Next go to https://redirect.viglink.com/?format=go&jsonp=vglnk_150722328747813&key=f0a7f91912ae2b52e0700f73990eb321&libId=j8eptfpd01000n4o000DA2tibhbwi&loc=https%3A%2F%2Fforum.xda-developers.com%2Fnexus-6p%2Fgeneral%2Fguide-fix-nexus-6p-bootloop-death-blod-t3640279&v=1&out=https%3A%2F%2Fdrive.google.com%2Fopen%3Fid%3D0B7TP6GXR0wAVWVlvckU5LUtkYkE&ref=https%3A%2F%2Fforum.xda-developers.com%2Fnexus-6p%2Fgeneral%2Fguide-fix-nexus-6p-bootloop-death-blod-t3640279%2Fpage141&title=%5BGuide%5D%20Fix%20for%20Nexus%206P%20Bootloop%20of%20death%20%7C%E2%80%A6%20%7C%20Huawei%20Nexus%206P&txt=Download and download the Oreo4Cores.image Copy the Oreo4Cores.image to your adb folder.

Press the windows key button your keyboard, under search, type command prompt and open command prompt. In command prompt make sure you're in the C:\adb directory you made.

In the C:\adb directory, type fastboot flash boot Oreo4Cores.img.

Once done, type fastboot reboot and your phone should boot up without any issues.

I just want to thank all those that made the fix to the brutal google loop. You guys are heroes!

I battled with a head gun to get the OEM unlocked successfully. Since I have tried flashing the Oreo files(OPR6.170623.019, Oreo4Cores.img) and the files for 7.1.2(N2G48C, 6p48C.img) . Unfortunately my 6p continues to bootloop in spite of trying this.

I wonder if I am the lottery winner facing a different reason for the boot loop?
 

johnnyphive

Senior Member
Mar 25, 2010
91
0
Update to Oreo?

So, I've tried searching the thread, and i could have totally overlooked it, so if someone wants to link me to an answer, that would be great.

Here is my setup.

Have a STOCK 6P that just started doing this yesterday. I'd basically given up hope then i came across this thread. I was able to get booted back in to my phone by wrapping it in a blanket while it was trying to boot and it eventually got in. I was able to turn on developer tools and enable unlocking.

Installed TWRP and EX4.1.2 (using all the default values). Phone is currently restoring from a cloud backup and all seems to be good...time will tell.

Now that I've gotten this far, i figured "why not update to Oreo while I'm at it".

What would be the best path to do so?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 264
    Read First: This method is relatively drastic, and will hurt device performance some. You should only use this as a last resort, if the more basic methods of fixing a soft brick didn't work (e.g, factory reset, flash stock firmware, etc.)​

    *Update 8/22: Android O is working with 4 Cores now! Big thank you to @xls654 for finding out how to get Android O to work.

    *Petition:
    I made a petition for Google to officially release and sign modified boot.imgs, so that people with locked bootloaders can fix their devices too. Check it out here. (I apologize for dumbing it down so much, I wanted to make sure everyone could understand it)

    *Changelog:

    • 8/25 - EX kernel for Android O added.
    • 8/22 - Android O DPR6 boot.img and source added.
    • 8/16 - Started making this fix open-source, source code section added in OP. Also uploaded modified Franco and Flash kernel & source.
    • 8/10 - Added PA 7.2.2 and DarkROM boot images.
    • 8/08, 2nd change - Uploaded modified boot.img for firmware 48C.
    • 8/08 - Updated EX kernel to version 4.1.2. This updated zip adds the CPU utilization patch to the init.elemntalx.rc, instead of removing the old init.angler.rc and copying the new init over. That should mean more compatibility with Roms/kernels that modify the init.angler.rc. I also modified the camera-daemon to use cpus 0-3 instead of 0-2, so hopefully this should make the a camera bit faster too.
    • 8/07 - Added boot.img that only uses 1 core. Someone suggested I make a boot.img that only uses 1 core, just to see if it works for devices that didn't work with the 4 Core fix.
    • 7/30 - Added universal EX zip, this zip should modify your kernel to use only 4 cores, and it should modify it to utilize all 4 cores. You can flash this over most ROMs and it should work. Also added a donation url, and this changelog.
    • 7/29, 2nd change - Added Pure Nexus and PA dev version boot images, modified to use 4 cores, and utilize all 4.
    • 7/29 - Updated this fix to greatly improve performance. Before this fix, the device was only using 1 core for foreground tasks, now it will use all 4 cores. Also revamped OP.
    • 7/21 - Fix created, stock boot.img, TWRP image, and EX kernel modified to use 4 cores.


    *What this fix does, and how to apply it:

    The problem:
    The problem with most of the devices in a BLOD, is that a hardware failure related to the BIG cluster has occurred. This fix remedies the problem by disabling the BIG cores. Unfortunately, this does mean that you will take a performance hit. However, I am continually working on ways to improve the device's performance.

    The update: If anyone remembers device performance with the first fix, it was hurt a lot, however, after finding out that the device was only using 1 core for all foreground tasks, I modified the ramdisk to utilize all 4 cores more effectively, and it helps a lot.

    Requirements: For this fix to work, you need:
    • A brain
    • A computer
    • A bootlooping 6P with an unlocked bootloader/OEM unlocking enabled
    • The modified files of your choice
    • Fastboot on your computer (preferably installed system wide). If you do not know what this is, or do not have it, look at this post. Answer yes to all of the prompts to install it.

    How to apply the fix:
    1. Boot your phone into bootloader (hold power and volume down).
    2. Connect your phone to the computer.
    3. Go to the folder where you have the modified files, then hold shift and right click in a blank space, click on "open command prompt here" in the menu that pops up.
    4. In the command prompt: type "fastboot flash boot [name of the file here]" and then press enter. If you're flashing TWRP, replace boot with recovery. (Linux users, make sure you're running as root)
      Edit: With the new EX zip, you shouldn't need to flash the boot.img anymore, you can just flash twrp, and then flash EX in twrp.
    5. Boot up your phone, and hopefully it should work!


    *If your phone is bootloader locked/OEM locked:

    You can try to get your phone to boot long enough to enable OEM unlocking. Some users have reported success by freezing their phone for a bit, then booting it. Others have let their battery drain all the way, and then tried to boot their phone, but the most successful method seems to be heating up your phone (a lot).
    If you do attempt any of these methods, make sure you have time and patience, as it will take a long time.

    To enable OEM unlocking and unlock bootloader:
    1. Go to settings.
    2. Go to developer options, if you do not see that, go to "about phone", scroll to build number, and then tap it 7 times. You should now see developer options in settings.
    3. Once you're in developer options, click on "OEM unlocking" and accept the prompt.
    4. Now reboot your phone to bootloader, connect your phone to the computer, and type "fastboot flashing unlock" Your bootloader should now be unlocked.

    *Downloads:

    • Boot.img from stock 6.17, 8.0 firmware: Download | Mirror. This Image is the from the first official release of Android O, and is modified to use 4 cores. It also disables forced encryption as a bonus. Thank you to @xls654 for figuring out how to get Android O to work.
    • Boot.img from stock 48C, 7.1.2 firmware: Download | Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
    • Boot.img from stock 48B, 7.1.2 firmware: Download |Mirror. This Image is modified to use only 4 cores, and is modified to utilize the 4 cores more effectively. I have had multiple people say that first boot takes a while after flashing this, so just wait about 20 minutes before you declare something is wrong with it.
    • TWRP version 3.1.1: Download | Mirror. This TWRP image is modified to use only 4 cores.
    • EX kernel version 5.03: Download | Mirror. EX kernel 5.03 works with android 8.0.0. This zip applies the 4 cores patch, but you will need to flash it over an already modified boot.img to work.
    • Elemental X kernel version 4.12, universal zip: Download | Mirror. This zip is EX kernel, modified to use only 4 cores. Update: I modified it to apply the CPU utilization patch too, so now this is a universal zip, flash it over almost any ROM, and you should now have the BIG cores disabled fix, and the little core utilization fix.
    • Flash kernel version 2.5: Download | Mirror. This zip is modified to use only 4 cores, and utilize all 4. Works with android 7.1.2. You can flash this over almost any ROM, including stock, and it should boot again.
    • Franco kernel r55: Download | Mirror. This zip is modified to use only 4 cores, and utilize all 4. Works with android 7.1.2. You can flash this over almost any ROM, including stock, and it should boot again.

    You will most likely not need these images. It will be much easier, and much more universal to flash one of the custom kernel zips above ^^^
    • PA boot.img from PA version 7.2.2, build 8/10: Download | Mirror. Uses only 4 cores, and has core utilization patch.
    • PA boot.img from PA version 7.2.1: Download | Mirror. Boot.img from PA dev preview 7.2.1, uses only 4 cores, and is modified to utilize 4 cores more effectively. Flash it after you flash the PA zip, either with fastboot, or TWRP image flash.
    • Pure Nexus boot.img from Pure Nexus 7/25 build Download | Mirror. This image is modified to use only 4 cores, and it has a tweak to utilize the 4 cores more effectively. Flash it after you flash Pure Nexus, either with fastboot, or TWRP image flash.
    • DarkROM boot.img from 7/21 build: Download | Mirror. This image is modified to use only 4 cores, and has the utilization patch.
    • Boot.img modified to use only 1 Core. Some people were reporting that the 4 core images weren't working for them, someone suggested that I make a 1 core version to see if that helps at all. Edit: seems not to help unfortunately. Here it is: Download | Mirror


    Unfortunately, I have not been able to get Android O working yet, but I am working on it right now.
    If you have a favorite custom ROM or kernel you want to ported over to use 4 cores, let me know, and I'll put it up.


    *Source code:



    p-0000000000000000000000000000007 (sorry that was my kitten)

    *Tested custom ROMS/kernels

    I have used Pure Nexus by flashing the modified EX zip over it, it has notably better performance than the stock ROM, and very good battery life. It's a clean, stable ROM, with plenty of good features that are actually useful.
    I have also used Paranoid android dev preview, very good performance, definitely my favorite as of now. Battery life leaves something to be desired, but I have not tried a custom kernel yet. Also, 7.2.1 seemed smoother to me than 7.2.2.

    If you have a custom ROM/kernel that worked for you, let me know and I'll put it up here.


    *To improve performance slightly:

    • Flash a custom kernel. I will upload more kernels as I test more, so stay tuned.
    • Overclock the little cores. It can slightly help offset the lost performance, on my 6P, I have mine overclocked to 1632MHz, and it works perfectly for me. Edit: I actually recommend not overclocking. Many people have reported their Little cores failing, so I would go for longevity on this device, and keep it at stock clocks, or even underclock it. The speed difference you get from overclocking is negligible anyways.
    • Disable animations in developer options. Seriously, as soon as I found out about this tweak, I've used it on ever single device I've owned, it helps a ton.
    • Turn resolution down to 1080p. On a small screen, the difference in between 1080p and 1440p is not very noticable. To do this, first get root access, then download a terminal emulator. In the terminal, type "su" and grant it root access, then type "wm size 1080x1920", and finally, change the density "wm density 400". Personally, I like my density at 400, but you can expieriment with it. Lower density=Smaller items and text, Higher density=Bigger items and text. Also @Adithya FRK mentioned that you also want to put density in build.prop so apps display correctly. Change ro.sf.lcd_density=560 to your density, if you changed it.


    *Credits:

    @rchtk, His post here gave me the idea for how to modify the images.
    @flar2, He built the Elemental X kernel for this device, I merely made a small modification to his kernel to use 4 cores. In no way am I trying to steal and/or discredit his work.
    The TWRP development team, they built the TWRP recovery for this device, I merely made a small modification to their recovery to use 4 cores. In no way am I trying to steal and/or discredit their work.
    @tr1gg3r.man, He made the the PA kernel, I just added a couple modifications. In no way am I trying to steal and/or discredit his work.
    @BeansTown106, He made the Pure Nexus kernel, I just added a couple modifications. In no way am I trying to steal and/or discredit his work.
    @Dark_Eyes_, He made the DarkROM kernel, I just added a couple modifications to it. In no way am I trying to steal and/or discredit his work.
    @[U][COLOR="Purple"]The Flash[/COLOR][/U], He made The Flash kernel, I just made a couple modifications to it. In no way am I trying to steal and/or discredit his work. His posts have also helped me a lot with learning how to build a kernel from source, understanding how to use git more, etc. I recommend you check them out if you are interested in getting started with android development.
    @[B]franciscofranco[/B], He made Franco kernel, I just made a couple modifications to it. In no way am I trying to steal and/or discredit his work.
    @xls654, He found out how to get Android O working with 4 cores.


    FAQs

    • What's the password for TWRP/Why is TWRP asking for a password? - In android 7.0, Google added forced encryption to the data partition. To get around this, click cancel when TWRP asks you for a password, and then factory reset the device. Then you can flash EX kernel/Magisk to disable forced encryption.
    • Why am I getting an error when I try to flash the images? - Your bootloader is probably not unlocked, try running the command "fastboot flashing unlock", If you get an error there too, then you will have to enable OEM unlocking before you can continue.
    • It's not working for me, how do I fix it? - My only advice for that is: "Flash the stock firmware for whatever version image you're trying to flash, then reflash the images again" If you're stuck on the boot animation, wait at least 20 minutes before you declare it's not working. If none of that works, chances are your device may have a different problem.
    • Does EX kernel have the new speed fix? - Yep, you can flash this over just about any ROM, and it should patch it to use only 4 cores, and use them well.


    I would like to help as many people as I can, however, I am much more likely to be able to easily help you/reply to your post if you clearly state your problem and the steps you attempted to fix it. I will be much less likely to reply to posts such as "omggg i flashed the image and my phone won't boot helppp" Please read through post first, I did not spend time typing up this OP for no one to read it. If I can see that you read through the OP and have attempted all the steps, then I will be much more willing to help you.

    I set up donations on my profile, for those of you who want to donate. I have spent countless hours modifying, flashing, testing, and helping, don't get me wrong, I love doing this and helping y'all out, but donations really keep me motivated to keep going, and donations also will help me fund new equipment and devices that will help further my android development. Every single donation is appreciated :) Donate to me here!

    If this guide helped you, please click thanks, it means a lot to me :)
    25
    Guys.. bad news.. my Nexus 5X just got hit with the BLOD. 😢

    Good news for everyone is I spent a bit of time tonight to first patch the latest 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 AK2 zip to fix the likely newer recovery you already had on your device. 👍


    Edit: See my new thread for updated files + step-by-step instructions: https://forum.xda-developers.com/nexus-6p/general/bootloop-death-blod-workaround-zip-t3819515
    17
    How the fuuuuuuuu man you save me, how do you make this.
    Really work for my Nexus 6p thank you man, is there any way to send a cup of coffe.

    To anyone who wants to make a boot.img with 4 cores: It's actually fairly simple, you need to get abootimg tools on linux. Then unpack the boot.img with abootimg -x (name of your boot.img) Once the image is extracted, there should be a file named bootimg.cfg, edit that file and put in maxcpus=4 in the line that starts with cmdline =. Then repack the image with abootimg --create myboot.img -f bootimg.cfg -k zImage -r initrd.img And viola! You have a (half) working kernel.
    17
    Update: Just found out that the kernel is setting foreground tasks to only run on CPU 0, I would assume this is because that foreground tasks only ran on BIG cores, but since the kernel can't access them, it pushes all foreground tasks to CPU 0, and only CPU 0, obviously, this would slow device performance down a lot, so I'm working on building a modified init script to fix this. Up to this point, our devices have basically been running on 1 core, so this fix will help performance a ton.

    I uploaded a screenshot of core usage on device startup, to show just how bad the problem is. (Keep in mind this is on my device with all the tweaks as well)
    16
    Big Update: Got the kernel to start utilizing all 4 of the cores instead of just 1, will update OP with links shortly! I haven't tested it much, as I just got it working, however, I expect a drastic increase in performance.
    Also, does anyone know how to add spoilers? I seriously need to clean up my OP.

    Edit: Yep, even from just a couple minutes of testing, device runs smooth AF now, and that was at startup too, when it's typically extremely laggy.

    I attached a screenshot of all cores being used down below.