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

Search This thread

athuljays

Member
Jun 29, 2012
29
3
Same Issue

[/COLOR]
Alright, been at this for hours with no luck. Maybe I'm just missing something obvious. I bootloop at the Google logo like basically everyone else. I can get to the dead Android screen but cannot access recovery. Adb devices shows nothing, but fastboot devices shows the proper serial. I had the proper settings checked, so I was able to unlock my bootloader with the fastboot command. My problem seems to be the same as this post (https://forum.xda-developers.com/showpost.php?p=73946100&postcount=1330) except that I've been avoiding Oreo to reduce variables.

This is where I must be having some kind of issue. At first, I simply tried flashing TWRP. The fastboot commands act as I expect and everything is successful, no errors. I try to reboot the device into recovery and it looks identical to before. Dead Android screen, recovery option just restarts the bootloop.

Since TWRP didn't seem to work (so I can't flash the zip) I tried flashing the 6p48C boot image. Reboot and no change. Tried flashing each of these files in different orders along with the B version even though I was fairly certain I was on 48C. No luck.

Next I downloaded the 48C factory image and extracted bootloader, recovery, system and vendor images and flashed them following the instructions someone outlined a few pages before this post. All flashed successfully according to the command prompt. I followed that up with the 6p48C boot image and TWRP. Powered down the phone, turned on and the bootloop was still there, pull up the dead Android and still can't get into any kind of recovery.

Hopefully I'm just missing some simple syrup and I can kick myself when someone points it out. Any help would be appreciated. I've got 2 bootlooping 6Ps and I'm typing this on a potential 3rd victim lol

Same issue here too. I also have a problem where when I plugin the charger, the device boots itself automatically and goes into bootloop. Are you facing this too?
 

jassun16

Member
Dec 16, 2013
45
6
Alright, been at this for hours with no luck. Maybe I'm just missing something obvious. I bootloop at the Google logo like basically everyone else. I can get to the dead Android screen but cannot access recovery. Adb devices shows nothing, but fastboot devices shows the proper serial. I had the proper settings checked, so I was able to unlock my bootloader with the fastboot command. My problem seems to be the same as this post (https://forum.xda-developers.com/showpost.php?p=73946100&postcount=1330) except that I've been avoiding Oreo to reduce variables.

This is where I must be having some kind of issue. At first, I simply tried flashing TWRP. The fastboot commands act as I expect and everything is successful, no errors. I try to reboot the device into recovery and it looks identical to before. Dead Android screen, recovery option just restarts the bootloop.

Since TWRP didn't seem to work (so I can't flash the zip) I tried flashing the 6p48C boot image. Reboot and no change. Tried flashing each of these files in different orders along with the B version even though I was fairly certain I was on 48C. No luck.

Next I downloaded the 48C factory image and extracted bootloader, recovery, system and vendor images and flashed them following the instructions someone outlined a few pages before this post. All flashed successfully according to the command prompt. I followed that up with the 6p48C boot image and TWRP. Powered down the phone, turned on and the bootloop was still there, pull up the dead Android and still can't get into any kind of recovery.

Hopefully I'm just missing some simple syrup and I can kick myself when someone points it out. Any help would be appreciated. I've got 2 bootlooping 6Ps and I'm typing this on a potential 3rd victim lol
I am also in the same state couldn't get past the bootloop with trying with different factory images and the appropriate mod images from the OP. I couldn't get into the recovery and the phone just bootloops. Hope somebody would help us with a smart solution.
 

Symber

Member
Jan 31, 2011
21
2
Same issue here too. I also have a problem where when I plugin the charger, the device boots itself automatically and goes into bootloop. Are you facing this too?

Yeah. Forces me to charge the phone in the dead android screen, but at least I can work around that issue. I'm glad to at least not be alone; this way I know I'm not just crazy and it actually probably is flashing the phone properly like it appears. Hopefully we can get some help.
 

widermargins

Member
Jun 15, 2017
5
3
Alright, been at this for hours with no luck. Maybe I'm just missing something obvious. I bootloop at the Google logo like basically everyone else. I can get to the dead Android screen but cannot access recovery. Adb devices shows nothing, but fastboot devices shows the proper serial. I had the proper settings checked, so I was able to unlock my bootloader with the fastboot command. My problem seems to be the same as this post (https://forum.xda-developers.com/showpost.php?p=73946100&postcount=1330) except that I've been avoiding Oreo to reduce variables.

This is where I must be having some kind of issue. At first, I simply tried flashing TWRP. The fastboot commands act as I expect and everything is successful, no errors. I try to reboot the device into recovery and it looks identical to before. Dead Android screen, recovery option just restarts the bootloop.

Since TWRP didn't seem to work (so I can't flash the zip) I tried flashing the 6p48C boot image. Reboot and no change. Tried flashing each of these files in different orders along with the B version even though I was fairly certain I was on 48C. No luck.

Next I downloaded the 48C factory image and extracted bootloader, recovery, system and vendor images and flashed them following the instructions someone outlined a few pages before this post. All flashed successfully according to the command prompt. I followed that up with the 6p48C boot image and TWRP. Powered down the phone, turned on and the bootloop was still there, pull up the dead Android and still can't get into any kind of recovery.

Hopefully I'm just missing some simple syrup and I can kick myself when someone points it out. Any help would be appreciated. I've got 2 bootlooping 6Ps and I'm typing this on a potential 3rd victim lol

I was in the same situation for days and it drove me CRAZY. Finally tried wiping the EFS and it worked for me! Might be worth a try?
1. Using fastboot, flash the stock ROM (7.1.2 or 8.0, whichever you prefer--I used 8.0), then flash TWRP.
2. Try to reboot into recovery. Chances are, you'll be stuck in bootloop again. At this point, I used a hairdryer to overheat the device; after about 15 minutes or so (getting it up to 45 Celcius), it reboots into TWRP! (I read that some people put the device into a freezer; I didn't try this.)
3. At this point, connect device to your laptop. Open command prompt and check that the 6P is connected with "adb devices". The serial number should show.
4. Then here's the crucial part: using the command line, type in the following commands one by one:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
adb reboot
5. Your 6P might reboot just fine! (Might take a few minutes though.)

**You should also be able to wipe EFS via fastboot, but when I tried the commands given in other sites, I got "permission denied". Using ADB worked.

Hope this helps!
 

gizmik

Member
May 25, 2011
8
1
How to detect revived phone with this method?

I'm suspecting that some guy sold me Nexus 6p revived after bootloop with this trick, I see only 1.56ghz for both clusters in CPU Z and 4-8 cores never go beyond 1.4ghz under load.
How else I can prove this theory?

I just don't want to be scammed.
 

SlimSnoopOS

Senior Member
Jan 29, 2011
8,052
3,348
I'm suspecting that some guy sold me Nexus 6p revived after bootloop with this trick, I see only 1.56ghz for both clusters in CPU Z and 4-8 cores never go beyond 1.4ghz under load.
How else I can prove this theory?

I just don't want to be scammed.

CPU Z does not display the speeds for both clusters, only the small cluster. I'm on a 5X that does not have a modified boot image installed and CPU Z clocks both clusters at 1.44 ghz lol Download an app like Kernel Adiutor (free), ElementalX Kernel Manager (paid), Franco Kernel manager (paid) that will display both cluster stats.

I'm sure there's an ADB command to identify this as well. Idk if any do these commands will help, I'm on mobile away from a computer:

https://stackoverflow.com/questions/6630386/how-to-find-arm-processor-version-on-android-device

Edit: also, if you have installed a custom rom or flashed a factory image since you received the device, then you are not using this mod. The boot image gets wiped away when you install either over it.

Sent from my Nexus 5X using Tapatalk
 

Eddie_Brock

Senior Member
Nov 8, 2010
243
28
I am also in the same state couldn't get past the bootloop with trying with different factory images and the appropriate mod images from the OP. I couldn't get into the recovery and the phone just bootloops. Hope somebody would help us with a smart solution.

Hold down the 'volume down' button as it reboots, you should eventually end up in 'Download Mode', where you can then boot into TWRP, recovery, or flash files thru Fastboot.
 

jassun16

Member
Dec 16, 2013
45
6
Hold down the 'volume down' button as it reboots, you should eventually end up in 'Download Mode', where you can then boot into TWRP, recovery, or flash files thru Fastboot.

When I hold down the volume down button while rebooting, it ends up in 'Bootloader Mode' not the 'Download Mode' that you mentioned. From there I tried to boot into recovery and the phone again bootloops. I couldn't get into the recovey. Anyways thanks for suggesting me something.
 

NoobInToto

Senior Member
Dec 4, 2013
856
246
Coimbatore
When I hold down the volume down button while rebooting, it ends up in 'Bootloader Mode' not the 'Download Mode' that you mentioned. From there I tried to boot into recovery and the phone again bootloops. I couldn't get into the recovey. Anyways thanks for suggesting me something.

Bootloader mode and download mode are the same.
You will see a screen with an Android and some options. That is your fastboot/download/bootloader mode.
 

sharpz811

Senior Member
Mar 6, 2012
333
95
brampton
I was in the same situation for days and it drove me CRAZY. Finally tried wiping the EFS and it worked for me! Might be worth a try?
1. Using fastboot, flash the stock ROM (7.1.2 or 8.0, whichever you prefer--I used 8.0), then flash TWRP.
2. Try to reboot into recovery. Chances are, you'll be stuck in bootloop again. At this point, I used a hairdryer to overheat the device; after about 15 minutes or so (getting it up to 45 Celcius), it reboots into TWRP! (I read that some people put the device into a freezer; I didn't try this.)
3. At this point, connect device to your laptop. Open command prompt and check that the 6P is connected with "adb devices". The serial number should show.
4. Then here's the crucial part: using the command line, type in the following commands one by one:
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'
adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'
adb reboot
5. Your 6P might reboot just fine! (Might take a few minutes though.)

**You should also be able to wipe EFS via fastboot, but when I tried the commands given in other sites, I got "permission denied". Using ADB worked.

Hope this helps!

So let me get this straight you never had to use the modified twrp and boot? Just flashed stock then twrp then wipe efs partition?
 

boeder9

Senior Member
Dec 19, 2011
145
20
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.

I'm trying to do this for MTC20L (6.01), I unpacked the stock boot.img in Windows using QURepack and found a file called bootinfo.txt, it contains:

base:0x0
ramdisk_addr:0x2000000
second_addr:0xf00000
tags_addr:0x1e00000
page_size:0x1000
name:
cmdline:androidboot.hardware=angler androidboot.console=ttyHSL0 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 boot_cpus=0-3
padding_size:0x1000


so the change I make is add: maxcpus=4

making it:

base:0x0
ramdisk_addr:0x2000000
second_addr:0xf00000
tags_addr:0x1e00000
page_size:0x1000
name:
cmdline:androidboot.hardware=angler androidboot.console=ttyHSL0 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 boot_cpus=0-3 maxcpus=4
padding_size:0x1000

Is this correct? Is the file I'm editing the right one?

Please help
 
  • Like
Reactions: aoaleman

Sliver1979

New member
Sep 30, 2017
1
0
Hope someone might have an idea for a complete noob here. I've followed the steps in the original post using the original Oreo img file and also the 4 core TWRP. When rebooting the phone it says your data can't be checked for corruption and then gets stuck on the Google logo with no animations. But I can access TWRP ok. I then tried the modified Oreo4Cores-oldfstab.img file from C4ndy. This got me a little further on boot, past the animations to a screen asking for a password. Doesn't matter what password I enter, it says "decryption unsuccessful - the password you entered is correct but data is corrupt......factory reset required..." After resetting the phone it eventually goes back to TWRP. And round and round I go.

I'm at a complete loss of where to go from here. Any advice would be greatly appreciated! Thank you in advance
 

widermargins

Member
Jun 15, 2017
5
3
So let me get this straight you never had to use the modified twrp and boot? Just flashed stock then twrp then wipe efs partition?

Sorry, I should have clarified. I used the modified 4-core TWRP here, but I had to flash stock boot.img as the modified 4-core one (Oreo4Cores) couldn't get my phone past the boot-up animation. The only way I could get past that was with the stock boot.img, so I've been sticking to that. As such, my phone is still running on 8 cores (according to CPU-Z at least), but hasn't had any problems since the EFS wipe (fingers crossed).
 

kennyloy

Member
Jul 8, 2010
11
0
singapore

For those who are locked device, can try to use this trick:-
Using water boiler to boil full of water, after water fully boiled, restart the device and put the device close to the boiler( middle of device, beside finger print scanner ), do this trick about 10 minutes. It will finish bootloop and go into os.
After enter, quickly open developer option and tick the oem unlock. The device will go into bootloop again around half an hour. Use Nexus Root toolkit to unlock oem, then flash recovery and flash boot image then done!!
Good Luck!!
 

ART

Senior Member
Nov 3, 2016
254
43
For those who are locked device, can try to use this trick:-
Using water boiler to boil full of water, after water fully boiled, restart the device and put the device close to the boiler( middle of device, beside finger print scanner ), do this trick about 10 minutes. It will finish bootloop and go into os.
After enter, quickly open developer option and tick the oem unlock. The device will go into bootloop again around half an hour. Use Nexus Root toolkit to unlock oem, then flash recovery and flash boot image then done!!
Good Luck!!

I tried a similar thing by using a hair dryer and pointing it in the middle of the device and it became hot. But didn't work. However, I then tried putting the phone in the freezer for an hour (battery was fully drained) , then charging it. It restarted properly after about ten minutes of bootloop.
 

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. :crying:

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


    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.