[EOL] Nexus 5X Bootloop of Death (BLOD) - Andorid Oreo Monthly Security patches & fix

[rehoni]

a

As a person that has been using his "fixed" Nexus for nearly a year, I want to express my thanks for the effort to all that contribute to the BLOD recovery effort. I realize the phone is not as good as new but is so much better, even degraded, than a non working one, I'm happy. Not having the latest/greatest is just part of my being retired. :good:

so die u s oth september version is not wrkng for me too and still in bootloop google logo and restart

 

[DaveRandom]

So using the unpackimg.bat and repackimg.bat that came with Unblod (saved me having to figure out Android Kitchen), I've been experimenting with changes to the ramdisk, using xcnathan32 github page as a reference.

To ensure I was starting from scratch I did a flash-all.bat from the factory image (and confirmed BLOD was present). I then unpacked the stock boot.img, and made the same changes to boot.img-cmdline and init.bullhead.rc from xcnathan32's github page, however I did not make any changes to fstab.bullhead (as when I unpacked the Unblod boot.img it didn't have this change). I repacked the files and flashed the new boot.img.

My phone no longer got stuck on the boot animation and successfully booted to the OS. I was extremely happy, until I noticed the wifi wasn't working. And that is where I am at, a Nexus 5X with no wifi, which is not ideal. This was the same result I had using the Unblod tool directly.

Has anyone who has suffered the wifi not working, managed to get it working?

I found this post - https://xdaforums.com/showpost.php?p=76907941&postcount=152 - on another thread. It worked like a charm. Phone now has Nov'18 update and wifi is working.

After following the instructions my phone did boot into the "Enter your Android password" screen, and I entered "default_password", and it said that the encryption was corrupted and it would factory reset (which was not a problem for me). I guess clearing the cache before rebooting might have prevented that screen, but the factory reset didn't stop anything from working.

Glad to have finally found the correct incantation to get the phone working again after about 3 weeks of trial and error. Massive thanks to all who have helped give hope to those who have suffered this problem.

 

[ritchea]

Is LG still taking returns on these phones?

If your 5X is within the extended 30 month warranty for boot loop, then, yes. I wish mine would actually boot loop again. I had it "fixed" in June but returned it within a month as it was boot lopping again. I've had the phone for 25 months. Since it was returned the second time, it is so slow to respond. I frequently get "App is not responding messages," and even though I can see my screen touches, it may take 5-10 seconds to respond. I've factory reset 4 times since August. It's rooted and running Franco kernel. I tried it unrooted and stock several times but no improvement. I wish I had seen the issue right away rather than a month later as I would have returned it. I loved this phone, but it's really grating on my nerves. I guess it's time to find a new phone.

 

[rehoni]

November patch coming in the weekend.

is there any pathc for H791?

 

[Deleted member 7280252]

is there any pathc for H791?

Don't these patches work on every model? Or what do you mean?

 

[rehoni]

Don't these patches work on every model? Or what do you mean?

soo idk.. on my nexus i tryed no chance i contact the LG gave them my IMEI and they said its the version 1 not the H970 but on my motherboard its H970..

 

[Zanzaras]

Will the patched boot image work with LineageOS?

 

[Deleted member 7280252]

Will the patched boot image work with LineageOS?

They should work, but I can't say for sure if Lineage made changes in ramdisk.

 

[craftyguy]

Will the patched boot image work with LineageOS?

No, this does not work on LineageOS (at on the latest 15.1 nightlies).

Here are the steps I took to build a working boot.img for LineageOS. The boot.img I start with is from the LineageOS zip file (use same version you have flashed to your device), you can get it here: https://download.lineageos.org/bullhead

This is the tool I for unpacking/packing boot.img and recovery.img. It includes a binary for mkbootimg, and I highly recommend not using it and using your own built from source since running arbitrary binaries from random people on the internet is never a good idea. mkbootimg's source is in the AOSP tree, and I think some folks mirror it on github somewhere. The bash script mkboot in this repo is incredibly useful though.
https://github.com/xiaolu/mkbootimg_tools

# boot.img
## Extract boot.img:

~/src/mkbootimg_tools/mkboot boot.img boot

## Edit boot/img_info, change boot_cpus=0-3 and add maxcpus=4:

cmd_line='console=ttyHSL0,115200,n8 androidboot.hardware=bullhead boot_cpus=0-3 maxcpus=4 lpm_levels.sleep_disabled=1 msm_poweroff.download_mode=0 loop.max_part=7 buildvariant=userdebug'

## Edit ramdisk/init.bullhead.rc:111:

    write /dev/cpuset/foreground/cpus 0-3
    write /dev/cpuset/foreground/boost/cpus 0-3
    write /dev/cpuset/background/cpus 3
    write /dev/cpuset/system-background/cpus 2-3
    write /dev/cpuset/top-app/cpus 0-3

## Pack new boot.img:

~/src/mkbootimg_tools/mkboot boot boot_4cpus.img

You can actually use the same process to patch the kernel cmdline used in TWRP to get a working recovery again:

## Unpack recovery:

~/src/mkbootimg_tools/mkboot twrp-3.2.3-0-bullhead.img twrp

## Edit twrp/img_info insert into cmd_line (boot_cpus already exists, so change it):

boot_cpus=0-3 maxcpus=4

## Pack recovery and flash:

~/src/mkbootimg_tools/mkboot twrp twrp-3.2.3-0-bullhead_4cpu.img
fastboot flash recovery twrp-3.2.3-0-bullhead_4cpu.img

 

[thanasisglt]

Hi,
I have a bootlooped phone fixed with that method having the 8.1 Jan oreo.
I want to go back to 7.1.2 as my phone has become sluggish.
Is it possible?

 

[Deleted member 7280252]

Hi,
I have a bootlooped phone fixed with that method having the 8.1 Jan oreo.
I want to go back to 7.1.2 as my phone has become sluggish.
Is it possible?

It propably will not fix anything but it is possible by flashing the 7.1.2 images from Google. You may need to factory reset.

 

[mhrussell1]

Update to this issue.
Used September files in same manner and USB issue is resolved. Not sure what is is with my N5X. Tried November files a second time and still had USB problems so I am sticking with September update for now.

---------- Post added at 01:54 AM ---------- Previous post was at 01:49 AM ----------



I contacted Google on this phone in January when this issue began as some people suggested there was some assistance being offered. Since the phone was out of warranty there was not help and their advice was to return to LG for PAID repair.

---------- Post added at 01:58 AM ---------- Previous post was at 01:54 AM ----------



I contacted Google on this phone in January when this issue began as some people suggested there was some assistance being offered. Since the phone was out of warranty there was not help and their advice was to return to LG for PAID repair.

I contacted LG after I confirmed that this patch worked for my phone. They gave me an RMA number and I paid for shipping but they fixed it for no extra cost and it shipped back to me last Friday. They tell you to wipe the phone and remove the SIM. I also restored the latest factory update with the flash-all.bat to make sure the phone is boot-looping when LG receives it.

As for another phone, so far, I am happy with my Pixel 3 which I got for the Black Friday discount of $150 off. I will keep the Nexus as a backup and to try LineageOS ROM.

Mark

 

[pc-jedi]

@T1mb3 Plans for December security update? I would highly appreciate this

 

[wlad0]

@T1mb3 Plans for December security update? I would highly appreciate this

You can try these files https://www.dropbox.com/sh/bt1uwxci28qjsp8/AADvjTiQM7RbSEsvOvOLV7dba?dl=0

 

[tofan8]

@T1mb3 , Can we expected signed boot-fix for December 2018 update ?

 

[Deleted member 7280252]

@T1mb3 , Can we expected signed boot-fix for December 2018 update ?

I can make one in the weekend

 

[tofan8]

I can make one in the weekend

Thanks,
After flashing, would it be possible to lock bootloader again?

 

[Deleted member 7280252]

Thanks,
After flashing, would it be possible to lock bootloader again?

It is, but I don't suggest it. It will be much harder to flash new images if some issues occur.

 

[tofan8]

It is, but I don't suggest it. It will be much harder to flash new images if some issues occur.

Even if OEM unlocking in developer options be enabled?

 

[smoke_007]

I can make one in the weekend

Thanks T1mb3! Do you know of any Nexus 5X roms out there that incorporate your BLOD fix? If not, how easy would it be to add your fix to a rom? Was wondering if there's any good Android Pie roms out there for this phone. Thanks!