Nexus 5X bootloop of death fix (BLOD) | 7/30 Huge performance update!

Search This thread

nookin

Senior Member
Mar 24, 2012
258
11
Yes. My 2nd 5X has BLOD and is running with the latest November 2018 stuff with Osm0sis's solution.

I tried flashing the official Nov 2018 image then follow Osm0sis's steps and flashed twrp and adb sideload. The first time adb sideload failed at 58%. And I get a green screen on phone. The 2nd time the sideloads seems to have succeed but still on reboot I get bootloop. Any ideas?
 

nirogu325

Senior Member
Oct 15, 2010
3,739
1,939
I tried flashing the official Nov 2018 image then follow Osm0sis's steps and flashed twrp and adb sideload. The first time adb sideload failed at 58%. And I get a green screen on phone. The 2nd time the sideloads seems to have succeed but still on reboot I get bootloop. Any ideas?
I've never had to use adb sideload. Are you sure you're following his thread's instructions to the letter? You'd do yourself a favor by posting any other questions in his thread. That way we won't keep bumping up this old thread.
 

Deborah_Gilbert

New member
Dec 12, 2018
4
1
Stuck with just recovery menu

Apologies nirogu325

I put a post in here and realised that you want people to use the other link.
 
Last edited:

DarkXShadowX21

Senior Member
Mar 21, 2010
127
6
FL
Hey guys,

I have a Nexus 5X.

[Asked this question awhile back too at this thread]
https://forum.xda-developers.com/nexus-5x/help/nexus-5x-stuck-bootloop-recognized-adb-t3663764

1. The volume up button does not work at all. Volume down does work which allows for me to get into download mode which shows the Firmware Update screen.

The screen at this point stays at 0%. My phone when attempted to boot is in a constant bootloop on the Google logo. It just repeats the splash screen over and over until it dies.

At some point, I personally unzipped the wrong file in twrp and that's what caused it. I didn't mean to have it selected at the time. With that being said, after it was flashed, my phone has not booted up since and this happened almost 2 years ago.

Currently, I have a computer to be able to work on this. I was able to make it to the download screen and when I plug it in, my computer makes a sound that it recognizes the device however, the device doesn't actually show up for me to see on my PC?

Since I'm not able to see it on the PC, I can't access the file structure. Also, fastboot (adb) is not able to recognize the device. I have tried countless hours trying to get the device to be recognized but it simply won't boot far enough for it to be recognized.

I've tried every option in the Nexus Root Tool Kit. I've YouTubed every damn video I can find and one of my biggest issues is that I am lacking the volume up button which makes it easier for recovery.

I can't seem to find a way to boot into recovery because fastboot doesn't recognize the device for me to sideload or flash onto the device. Since flahsing and sideloading won't work without the recognition of the device, I don't know what to do from this point forward to fix my Nexus 5X.
 
Last edited:

JJamesC

Member
Jun 23, 2018
12
3
Yes. My 2nd 5X has BLOD and is running with the latest November 2018 stuff with Osm0sis's solution.

Yes, Nexus 5Xs no matter what you do... are going to bootloop again. You need to sent it for a proccesor rework that is not worth the price, but so you know:
LG is covering warranty in this phone (only in the US) and you can sent it to them even if 1 year warranty has expired! So you all people should give it a try. (Don't sent water damaged phones or devices with the screen shattered, they will tell you that you need to fix that first and will charge a fee for reparations before bootloop fix) And if phone has water damage, they will charge you 20 fee just to sent your phone back if you don't accept to fix it.
 

nirogu325

Senior Member
Oct 15, 2010
3,739
1,939
Yes, Nexus 5Xs no matter what you do... are going to bootloop again. You need to sent it for a proccesor rework that is not worth the price, but so you know:
LG is covering warranty in this phone (only in the US) and you can sent it to them even if 1 year warranty has expired! So you all people should give it a try. (Don't sent water damaged phones or devices with the screen shattered, they will tell you that you need to fix that first and will charge a fee for reparations before bootloop fix) And if phone has water damage, they will charge you 20 fee just to sent your phone back if you don't accept to fix it.
I already knew (as most here) and it's not worth the hassle. It will bootloop again down the line as told by several people that went through LG repairs. It's also not viable for users living in a tropical setting because humidity will quickly turn that dumb sticker red. Many months ago I chose to move on from LG altogether. I just keep the 5X as a backup.
 

le286

New member
Jan 3, 2019
1
0
Hey guys, sadly my Nexus5X also got the same problems, therefore i tried the newest image and boot- and recover-fixed img, but I cannot boot it. I always get stuck in the "no command" screen, sometimes I also get to see the "Your Device is corrupted Screen". Any tips?:confused:
 

mrc.toader

New member
Jan 17, 2019
2
0
This is neat :D

Hey, so, thanks for all the info and updates. Awesome work. :D

I found a really cheap bootlooping 5x, managed to get it working, but not with either of the custom kernels. I am however running the latest lineageos build, instead of the google firmware.
I was actually wondering if anyone can point me towards the source code and some build guide for the kernel, I'd like to try and 4core patch it myself, most likely also some undervolt/underclock.
But all I found was the git repo for EX 5X and premade binaries randomly hosted.

Are there some threads, groups or documentation about these?
 

nirogu325

Senior Member
Oct 15, 2010
3,739
1,939
Hey, so, thanks for all the info and updates. Awesome work. :D

I found a really cheap bootlooping 5x, managed to get it working, but not with either of the custom kernels. I am however running the latest lineageos build, instead of the google firmware.
I was actually wondering if anyone can point me towards the source code and some build guide for the kernel, I'd like to try and 4core patch it myself, most likely also some undervolt/underclock.
But all I found was the git repo for EX 5X and premade binaries randomly hosted.

Are there some threads, groups or documentation about these?
Check the linked thread 6 posts above yours. An universal flashable patcher exists.
 

Carball0

Member
May 1, 2018
38
25
I've used the latest option for my Nexus 5X 16GB and it enters bootloop again.
I was able to power it up and enable OEM unlocking and I flashed the 4CoreOreo.img, then a message saying "Erasing" appeared and now it's bootlooping ?
 

klpgh

New member
Mar 10, 2019
1
0
Pittsburgh
I have done exactly what you have said. but when it boot display "your device software can't be checked for corruption. please lock the bootloader visit g.co/ABH "


C:\adb>fastboot flash boot 4CoreOreo.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'boot' (12508 KB)...
OKAY [ 0.470s]
writing 'boot'...
OKAY [ 0.235s]
finished. total time: 0.705s

I saw the same reference to "g.co/ABH". Did you ever find a way to resolve this?
 

Sereseli97

Member
Aug 30, 2015
31
3
Hello everyone, I just bought an Lg Nexus 5X and in my first day, I just love the phone! (However, I did know about the Bootloop issue just when my phone was already shipped overseas). My phone works perfect and is like new, just a little of heat, but normal heat to me. I wonder if I should just enjoy my phone as it is or should I flash this fix before it began? I'm stick to this phone for a little bit as it's not easy to switch devices in my country (Venezuela), so I must make it work any longer it can.

EDIT: for security, I already unlocked the Bootloader XDD
 
Last edited:

CLPose

Senior Member
Jan 7, 2015
726
380
Buenos Aires
Hello everyone, I just bought an Lg Nexus 5X and in my first day, I just love the phone! (However, I did know about the Bootloop issue just when my phone was already shipped overseas). My phone works perfect and is like new, just a little of heat, but normal heat to me. I wonder if I should just enjoy my phone as it is or should I flash this fix before it began? I'm stick to this phone for a little bit as it's not easy to switch devices in my country (Venezuela), so I must make it work any longer it can.

EDIT: for security, I already unlocked the Bootloader XDD

Hi! Opinions about disabling the BIG cores for avoiding BLOD are different. But I can understand what you're talking about since I live in Argentina. I can tell you that I disabled BIG cores with kernel manager at first, but then flashed osm0sis' ZIP (https://forum.xda-developers.com/nexus-5x/general/tool-bootloop-death-blod-workaround-t3819497) because BIG core would turn on with no apparent reason when disabled with a KM. I bought my N5X in December 2016 and it's still alive and kicking, working with only the four little cores. Good luck!
 
  • Like
Reactions: Sereseli97

Top Liked Posts

  • There are no posts matching your filters.
  • 239
    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 7/30: On my 6P, I found that the original kernel with this mod was using pretty much 1.5 cores, instead of all 4. People with the 5X were also reporting this, so I modified the images to utilize all 4 cores better. It helps performance a lot (able to beat stock 6P in some Antutu marks now, and play intensive games), try it out if you haven't yet!

    *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/26 - EX kernel for Android O uploaded.
    • 8/22 - Android O working, boot.img and source uploaded.
    • 8/08, 2nd Change - Added boot.img for 48C firmware (August security patch).
    • 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 for 1 core, just to see if it would work for devices that didn't work with the 4 core image.
    • 7/30, 2nd Change - 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/30 - 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, and added Marshmallow images.
    • 7/23- Created this fix, stock boot.img, twrp, and EX kernel added.


    *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 5X 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 universal EX zip, you don't have to flash the modified boot.img now, you can just flash TWRP, and then flash the EX zip, and everything should work.
    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 Android O DP6: Download | Mirror. This Image is the from the first official release of Android O, and is modified to use 4 cores. As a bonus, it also disables forced encryption. Thank you to @xls654 for figuring out how to get Android O to work.
    • Boot.img from stock 48C, 7.1.2 firmware (August security patch): 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 on the 6p 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 47Z, 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 on the 6p 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, for Android O: Download | Mirror. EX kernel for Android Oreo, modified to use 4 cores. You must flash it over the 4 core boot.img for it to work.
    • EX kernel version 4.12, universal zip: Download | Mirror. This zip is modified to use only 4 cores, and it will also apply the speed fix. Flash this in TWRP. I highly recommend you flash this, as it improves device performance notably, and disables forced encryption. This kernel should work with almost any other ROM, and it applies the core utilization mod from the first image, thanks to AnyKernel.
    • 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. Here it is: Download | Mirror

    For Marshmallow:
    • Boot.img from the latest 6.0.1 20K firmware: Download | Mirror. This boot.img is modified to use only 4 cores, and is modified to utilize those 4 cores more effectively. Untested as of now.
    • Ex kernel version 1.2.0 for Marshmallow: Download | Mirror. This is the latest EX kernel for marshmallow, it will keep the core utilization mod from the above image, and should work on almost any other ROM, thanks to any kernel. Untested as of now.


    *Source Code:

    • Source for 4 core Android O DP6: Source.


    *Tested custom ROMS/kernels

    you should be able to use almost any ROM with a stock based kernel, just flash the EX zip over it.

    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 people request more, so stay tuned.
    • Flash a custom ROM. Once again, I will upload more as people request 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.


    *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.
    @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 you have a different problem.
    • Does EX kernel have the new speed fix? - Yep, the EX kernel zip should apply the 4 core fix, and the speed fix. It should also work with almost any ROM, including stock.


    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 :)
    48
    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 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-5x/general/tool-bootloop-death-blod-workaround-t3819497
    12
    Update: I added a universal EX zip, this zip should make your device only use 4 cores, and utilize all 4 cores, so there's no need for flashing a separate boot.img before you flash EX. Also, with this zip, you should be able to flash EX over almost any ROM, and it should work.

    I also added a donation URL to my profile, donations keep me motivated to keep going, and they will be used to help me fund equipment and devices to further advance my android development. Every single donation is appreciated :)
    11
    i tryed all your .img file but noone works with it the 8.0 android oreo version, we are waiting the big update for boot.img cores :) nice work bro :good:

    p.s. im in bootloop

    I'm working on 8.0 right now. Unfortunately it is a challenge due to the changes in android O, but I will try to get it working as fast as I can.
    9
    Update: Welp, for me, school is starting in a couple weeks :( Which means I have to do all my summer assignments (that I had the whole summer to do), in two weeks. Cross Country race season is also starting for me, so I will be less active as a result of those two things. I will try my best to keep maintaining this and helping you guys though.

    Also, I am working on an application to make this process easy for beginners. I wanted to learn C#, so I figured this was a good way to help me learn it. Expect that to come later this week/next week (depending on how lazy I am).

    P.S: HUGE thank you to everyone who donated!! The support of this community is mind-blowing, and it means a lot to me that people appreciate my work enough to donate. Once again, thank you so much :)