yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] Jfelips:
How's your battery on Oreo 8.1? I was on it and it was very terrible, I don't know if the problem is the 4core fix or my battery that was some months without use... I barely got 2:30 hours of SoT
[Nexus 6P General] bballs91:
Okay so that's about the battery life I had BEFORE I upgraded to 8.1.

Ever since I've been on 8.1 though my battery life has improved immensely tbh..

I'm totally on stock too, idk what else could be influencing it. I have all animations turned off and my display set to "smallest". Otherwise I haven't changed any settings much.
[Nexus 6P General] Jfelips:
I'm on paranoid andriod lastest and my sot is around 3hrs now, maybe i need to replace the battery idk :/
[Nexus 6P General] bballs91:
Yeah I mean our batteries are all getting old now. They're simply just not going to hold a full charge for very long anymore..

That's why I'm content with my current battery life, which is around 3.5hrs SoT I'd guess.

It's either time for a new phone in general or new battery specifically after about 1.5-2yrs with modern phones I've found. Planned obselesence and what not haha. At least the manufacturer doesn't slow down our cpu clock speeds with age ?
[Nexus 6P General] Jfelips:
Lol ? yeah, at least that... I think i'll replace the battery soon
[Nexus 6P General] jimbomodder:
I had same thing with a nexus 6 but couldn't get out of it either, might be time to upgrade or find another motherboard
[Nexus 6P General] Senater_Cache:
Hi guys, im on my replacement 6P already, and after just about a year, it bootlooped again.

Only thing this time is that my bootloader is locked since I was on stock ROM unrooted....

Is there any hope for a device without USB debugging, OEM unlocking, and with a locked bootloader??

Any help is appreciated!
[Nexus 6P General] bnorontako:
hi, is somebody have 4coreboot patch for angler opm3.171019.013?, wich is out now from google
[Nexus 6P General] orangeworx:
Spent the last couple of days trying to do exactly that...

What seems to have worked for me was waiting till the battery was near depleted. I left it bootlooping all night tonight, woke up to a dead device... tried starting it, a few bootloops and got the spinning crap logo. Yay you might think but just as I was trying to rush to enable usb debug it died... forgot to plug charger!!! :mad: :mad: :mad:

So I plugged it back in and left it bootlooping till I eventually got back in... no dice doing that without wiping the phone unfortunately, I tried! Anyways, unlocking bootloader was going to wipe it.

Now it's fully charged and I was just about to get cracking when I realized, fken google released OPM3.171019.013

So I'm not sure if I should go ahead with it, since the the 4core boot patch released by [MENTION=4752144]squabbi[/MENTION] here is for the previous update. Not sure it would work and not really interested in spending another day stuck with this heap of junk!

Edit1:

Well it seems not wanting to unlock the bootloader

running "fastboot oem unlock" or "fastboot flashing unlock" commands yield this:

fastboot flashing unlock

...

FAILED (command write failed (Unknown error))

finished. total time: 5.006s

anyone knows what's that about?

---------- Post added at 05:20 PM ---------- Previous post was at 04:48 PM ----------

Sorry buddy, you need to be able to get into the OS, unlock dev options > enable oem unlocking and usb debugging

try to drain your battery as much as you can, this did it for me when all the other options mentioned in this thread failed i.e. freezing it, yes it was -30 outside yesterday! and I put it in the freezer as a 2nd attempt. Heating it didn't do the job either, sat on that sucker for a while! the battery drain seems to be having the most success as I've personally witnessed (only 2 times it booted was this way) and I've read across this thread...

My issue now is that I can't unlock bootloader... I have the google drivers, I tried with cmd and [MENTION=4752144]squabbi[/MENTION]'s toolkit

through cmd, fastboot devices shows me the device but fails to unlock

through the toolkit, well it's not even detecting the devices in BL mode "You need to be in the bootloader to unlock the bootloader".

Maybe you'll have better luck!

Edit2:

Mysteriously, it's worked now with the fastboot flashing unlock command as per google's instructions on the releases page... but why now... bizarre!

---------- Post added at 05:27 PM ---------- Previous post was at 05:20 PM ----------

I'm not sure if the patch for the previous opm1.17... would work since it's a small incremental upgrade

not sure if I want to try it lol
[Nexus 6P General] bnorontako:
i try 4core-patch-boot-opm1 for newest update opm3 it works like a charm, and i rooted via twrp supersu v2.82 sr5, everything work like a charm
[Nexus 6P General] orangeworx:
Thanks for the info.

I just flashed opm1 and let the phone reboot itself... I didn't flash anything else on the phone and it didn't boot loop. I'm wondering if I should still go ahead and do that...

I didn't get the OTA notification for opm3... also wondering if I should download that and fastboot flash it
[Nexus 6P General] SlimSnoopOS:
See below:

https://xdaforums.com/showthread.php?t=3716330
[Nexus 6P General] orangeworx:
Ok so the boot patch has been released, good! thanks for the link

Just a question, would you have an idea about the possibility of the bootloop returning if the android update went through and the phone booted alright... what are the chances that it will come back? I should just do it and not break my head?
[Nexus 6P General] Steveon:
I am still using 7.1.2.. anyone kind soul here willing to make elementalx 4.14 with both 4 cores + CPU optimization version of that kernel? Thanks
[Nexus 6P General] SlimSnoopOS:
You're welcome. The phone can bootloop again even with the 4 core fix installed. There are numerous people who have reported this here and in the 5X thread.
[Nexus 6P General] orangeworx:
So what's the dang issue with this device? Is it a hardware or software issue since Huawei and Google won't own up and blame each other... Are we supposed to just give up on the 6P and look elsewhere?
[Nexus 6P General] SlimSnoopOS:
I wouldn't recommend keeping it. I've already gone through one RMA last summer for this issue. I'd be using a Pixel 1/2 if I had the extra cash.
[Nexus 6P General] orangeworx:
Thanks man, appreciate the input! Considering there's no real solution, this thing is as good as an expensive paper weight
[Nexus 6P General] SlimSnoopOS:
Anytime. Unfortunately, that's the best long term advice I can give. Just make sure to backup anything important regularly off the device and hope for the best. It's good that we at least have a temporary solution of course.
[Nexus 6P General] sinsobrenombre:
Meltdown & Spectre flaw update

Google released Jan 5, 2018 OTA update... did anyone updated over the fixed kernel? did you get "looped" again?
[Nexus 6P General] Sharfuddin Ahmed:
Hello... My 6p gets stuck on Google logo for few seconds then it again turns on and the process continues... Plz help me. I don't have access to computer.. But I can go into twrp recovery..

Thanks!
[Nexus 6P General] orangeworx:
Start from the top man... everything that you can try is posted in here... it takes time, I know, I had to do all of it.

After all the trouble this device put me through, I went ahead and sold it...
[Nexus 6P General] sirxdroid:
Just got hit by the bootloop problem on my 6P that I've owned for 26 months. Too bad because I really liked this phone and never had problems with it, battery has been fine, etc. I was planning on keeping it until the next gen Pixels come out.

I got it to boot with the EX kernel from the first post (lucky the bootloader was unlocked already), very grateful to the devs who made this possible. But TWRP can't decrypt storage, though otherwise the phone works OK during normal boot it gets decrypted.

At this point, what choices do I have? Has anybody gotten the hardware fixed either from Huawei or some other 3rd party? What's the cost? Worth fixing it or just throw it in the drawer and look for a different phone? I assume Google doesn't care about us anymore.
[Nexus 6P General] terryyyn:
I followed the steps and reboot it but it says "device software cannot be checked for corruption. Please lock the bootloader". What should I do thanks?
[Nexus 6P General] mdfarazb2:
Ignore that.. That's just the indication that your bootloader has been successfully unlocked. Move on.
[Nexus 6P General] terryyyn:
but it was booting forever since then
[Nexus 6P General] mdfarazb2:
Oh.. That means your device has got affected with BLOD.. Follow this thread's OP properly and you'll probably come out of it.
[Nexus 6P General] nihar1024:
Hi, I've been patching the boot.img of the stock ROM to only use the 4 small cores instead of the default 8 (4 small, 4 big). Now, I was wondering if it is possible to maybe make it use (for eg.) 4 small and 1 big core or 4 small and 2 big cores. Being able to use even 1 or 2 big cores might significantly improve the performance of the device and reduce the load on the small cores. Has anyone tried this? And what were the results if you did?
[Nexus 6P General] Bobbaloo:
With all due respect to others that have answered you - 1. Is your bootloader up to date & 2. Did you flash anything new? If so, did you do it all carefully and in the right order? Recommend gapps? - PS, I always watch the boot time when flashing. Anything more than 7 minutes usually means there is something wrong
[Nexus 6P General] sirxdroid:
Any chance to get a patched version of ElementalX-N6P-4.14 to pair with the last 7.1.2 PureNexus ROM release?
[Nexus 6P General] csurana3008:
Unable to Unlock OEM

hi,

my nexus 6P is in bootloop mode and as i cannot start the phone i am unable to enable usb debugging coz of which i am unable to perform any of the above said methods.. ANyone have solution to this... i really need help on this urgently...
[Nexus 6P General] ricbaez:
Did you oem unlock the phone in developer options
[Nexus 6P General] maccicruz:
Hi All, I have the same problem in my nexus 6P. The problem is that previous to my phone dead, I do not have selected the developers option (OEM). Please, could you help me? Do you know if exist something that I allow active this option with my phone off.
[Nexus 6P General] sirxdroid:
From what I read you have to warm up the phone with a hair dryer which may allow it to boot for a bit so you can enable the dev option.
[Nexus 6P General] kvbir:
Can anyone post the modded boot image for 8.1?
[Nexus 6P General] osm0sis:
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://xdaforums.com/nexus-6p/general/bootloop-death-blod-workaround-zip-t3819515
[Nexus 6P General] mdfarazb2:
That's working Awesome Sir!! You are Brilliant.! Flashed your FBE twrp over my old twrp (yes from the recovery itself).then booted to the new recovery.. I was frightened of whether it would ask to format internal storage but it didn't:laugh: ..then Clean flashed the latest AquariOS build.(Yeah I didn't have it's modified boot image).. Then Gapps, Magisk, EX Kernel 4-core, then your AK2 zip and then my other stuffs.. And rebooted and Bang! The ROM booted.. Now we don't need to patch the ROM's boot image every time before flashing the new ROM.. You are Saviour..

Cheers Man!!! :laugh::svetius:
[Nexus 6P General] osm0sis:
You should be good with unmodified EX Kernel too, no need that I can see for specific mods for each kernel build anymore. :good::)

If I'd known the fix for BLOD was just in the cmdline and/or ramdisk I would have done this ages ago. It's the perfect application of AK2!
[Nexus 6P General] mdfarazb2:
WoW! If we can flash the normal version of EX kernel, then I think probably we could flash the others kernels too...:cyclops:.. That would be great.. Now no need to look for 4core kernels:angel:.. Great Sir! you now made this fixing BLOD thing so easy like that it didn't even exist..

You're great!:highfive::good:
[Nexus 6P General] Momotani-Hitoshi:
flashed Android 8.1, twrp-fde, ak2-zip and booted to setup screen. Then convert to FBE in dev option. Things seemed fine up to this point.

However, I tried adding magisk-15.3 & elementalx-6.01 zip via twrp-fde and now stuck at google animation. Any advice?
[Nexus 6P General] shuli81:
thanks for doing this!! this will make life much easier.

two questions:

1. does this require your twrp-fbe to work?

2. where in the flashing queue is correct placement for it? i assume after rom and kernel. how about magisk? before or after magisk?
[Nexus 6P General] mdfarazb2:
Don't flash root and kernel after flashing AK2 zip...flash them before it...
[Nexus 6P General] osm0sis:
Try flashing my 4core AK2 again, it should be done last after any kernel mods.

My next thought is Magisk used to be pretty temperamental with the N5X FBE, and flashing from recovery would break it unless you had KEEPFORCEENCRYPT=true in /data/.magisk

Maybe try that, or if that fails, try SuperSU SR5. It's what I use on my N5X.

Nope, as I said in my post, it can be sideloaded in any TWRP. I also emphasized that it should be flashed after everything else, i.e. last.

The correct order is as I said: ROM -> root -> custom kernel -> 4core AK2. I'm personally on stock still with Franco Kernel on my 5X. Bumped up the min freq on the low perf cores and working great.
[Nexus 6P General] Momotani-Hitoshi:
Thinking Magisk was having issues with FBE I tried not using it.

Fresh 8.1 + AK2, boot to setup screen, converted FBE, reboot back to recovery to add only elementalx then AK2 again, but stuck at boot animation.

Maybe both Magisk & elementalx is finicky with FBE. Resorted to FDE instead as it works without issue.
[Nexus 6P General] osm0sis:
Duplicate post.
[Nexus 6P General] osm0sis:
Oh yeah, EX botches the fstab flag we need for FBE on this device. Magisk used to do that too but I think it's fixed there now, so yeah, try everything but EX.

And report the issue to [MENTION=4684315]flar2[/MENTION], I thought he would have fixed it by now as well. Basically you can't switch forcefdeorfbe to encryptable like he does and have FBE work on these devices. That stuff is better left up to root zips, not kernel zips.
[Nexus 6P General] Gho5t z:
XCnathan32

Cannot bypass this google bootloop screen.. tried hot air blower and battery drain trick, still no luck to start android so that I can enable OEM and USB debug.. kindly suggest
[Nexus 6P General] mdfarazb2:
Plz don't quote the whole OP.

Thanks:)

---------- Post added at 05:52 AM ---------- Previous post was at 05:50 AM ----------

Update:- Tried stock EX kernel (non modified for 4 core)... working absolutely fine!

Again great work osm0sis!!
[Nexus 6P General] kemistry01:
Wait so you're telling us to flash the non modified EX Kernel before the .zip and it will work? That's great! But I wonder why the modified won't since it was "modified to work ".
[Nexus 6P General] osm0sis:
Only report of EX not working is with File-Based Encryption, which is really just an issue with the ramdisk mods that EX's installer does. That's any EX zip, not just the 4core mods. Hopefully [MENTION=4684315]flar2[/MENTION] will fix it at some point.
[Nexus 6P General] kemistry01:
I asked because [MENTION=6801297]mdfarazb2[/MENTION] said stock EX kernel worked. So I am curious how he did that.
[Nexus 6P General] osm0sis:
He did what my posts have all said: flash whatever you want, then flash my BLOD Workaround Injector AK2 zip. Done.
[Nexus 6P General] mdfarazb2:
Yeah now it doesn't matter whether you flash the modified one or stock one..(obv. if stock is working so better go with that coz of no modifications:silly:).. Just remember to flash all the stuffs in this correct manner and you should boot any ROM..

(for a clean flash):-

1st:- Latest Vendor.Img

2nd:- ROM.zip

3rd:- Gapps(if you want. *This step is not compulsary*)

4th:- Root (Magisk/SuperSu)

5th:- Any kernel (If you want . *This step is not compulsary* )

6th:- Osm0sis's AK2.zip (Most imp. Step)

7th:- other stuffs like fonts (if you want as *This step is not compulsary*)

Then reboot and have Profit!!!:):good:

Btw since yesterday I've tried nitrogen, crdroid,aquariOS and screwd:D and they all worked fine.(yeah I'm a flashaholic:silly:)

Thanks to the great [MENTION=4544860]osm0sis[/MENTION]!!!:angel:?
[Nexus 6P General] Gho5t z:
Guys any suggestions for OEM and USB debug would be appreciated

Thanks
[Nexus 6P General] sirxdroid:
Yikes. Sorry to hear about your 5X problems, osm0sis. Glad that you provided the fix though. I own both the 5X and 6P. My 6P fell victim of the BLOD a couple of weeks ago. I won't be surprised to see the 5X follow soon :(

What really went wrong with these phones? I can see one manufacturer having quality issues, but both LG and Huawei? Problems with the Qualcomm SoC that year?
[Nexus 6P General] osm0sis:
It's crazy, I wasn't doing anything intense, I had just switched tasks from a game, was on the home screen and was going into a folder to open Facebook Lite and boom, reboots forever and unable to boot into recovery. Battery was at about the 1/3 mark by the evening, which was normal for my usage,

I guess it's just the SoC in use on these devices. [MENTION=3292224]franciscofranco[/MENTION] was telling me that apparently it's pretty much the same issue that Apple got in trouble for throttling with, but at least they patched their kernel to throttle and avoid it, where Google just left it in there like a timebomb for when the battery gets too old, the voltage to the CPUs gets wonky and it fries the performance cores.

I didn't realize it was like that or I probably would have gone ahead and gotten a new battery on ebay before this happened. :eek:

So that's my recommendation if the BLOD hasn't happened to your 5X yet: go pick up a new battery.
[Nexus 6P General] squabbi:
This is fantastic! As you said, all this time you had something that was perfect for this hahah! Right under our noses. :victory:
[Nexus 6P General] QadirAliKhan:
Can't able to flash superxe from Twrp .. Aroma installer stopped at message "this is for angler and your device is "" .

But thanks for your work other ROM wrork great.
[Nexus 6P General] osm0sis:
What? Sounds like you're using the wrong TWRP or the wrong zip.
[Nexus 6P General] QadirAliKhan:
I am currently on Twrp 3.2.1.0 fbe.. Today I flash this before this I am using twrp 4core

And by using that able to flash super XE ROM successfully..
[Nexus 6P General] MikiGry:
How can a low battery voltage made perfornance core unsolder itself ? If it would get higher, then yes.

I keep tracking battery degradation on my 6P and i can clearly see thats its getting lower and lower. Not higher.
[Nexus 6P General] osm0sis:
Just relaying what I was told. Perhaps the voltage is overall lower but spikes from time to time?

I just tried to look it up myself and I honestly can't find anything definitive about the cause of the performance cores not working anymore. Any links you can share?
[Nexus 6P General] MikiGry:
[MENTION=4544860]osm0sis[/MENTION]

I dont think worn batteries act like that. And even if, there has to be voltage stabilizer soldiered to the mother board

I dont think there is any connection beetween BLOD and fast battery wear. To me its more that people who use their phone a lot get both of these issues at the same time (first battery degadation and shortly after BLOD)
[Nexus 6P General] Momotani-Hitoshi:
My understanding is there are multiple reasons why the big cores become faulty over time, but seems to boil down to QC issues.

Battery degradation can't supply the right amount of voltage needed to keep the hungry big cores stable. Kind of like overclocking a PC cpu too much; over time it degrades to a point where more voltage is needed or down clocking required.

Solder or connection joints inside the chip gets broken due to overheating, overuse or physical trauma. I've read reports of people baking the chip inside the kitchen oven much like what people do with PC GPU to revive it. Sometimes freezing it would get it working temporarily.
[Nexus 6P General] mzobe7:
Which ak2.zip do we flash?

The one titled N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed?

Thanks
[Nexus 6P General] shuli81:
Yes. That's the one
[Nexus 6P General] athuljays:
I had pretty much left the scene for a couple of months. Can anyone make a quick TL;DR for this AK2 fix?
[Nexus 6P General] htfwp:
Yesterday I installed the fix on a stock kernel 8.1 over osm0sis recovery 3.2.1-fbe and looking on active cores in cpuz I could see that only low power cores are working so the fix worked but this morning it started bootlooping again did I make a mistake somewhere? Thanks in advance

PS. If heating method or cooling didn't work and you tried everything else disassemble the phone and remove the back heat shield(and thermal paste don't forget to apply new one later) then connect only the battery and the LCD and leave the motherboard to hang by the LCD connector... in a couple of minutes you should boot into OS.
[Nexus 6P General] SlimSnoopOS:
Added Osmosis' post in case you haven't read it. Install this file last when flashing roms then boot into the rom: N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip.
[Nexus 6P General] logic88:
So unfortunately my 6P started to boot loop today. Was hopeful for a fix since this thread popped up in a search.

But I had a question. I never got around to updating to Android 7 so I'm still using Android 6.0.1 (MTC20L).

There doesn't seem to be a download for Android 6 so not sure what my options would be. Should I try flashing the Android 7 image first before flashing the modified boot.img for Android 7?

My concern with updating to 7 is that my 6P was rooted and modified with various things like Xposed for Android 6, which was one of the reasons that I never got around to updating.

Any tips would appreciated. Thanks!
[Nexus 6P General] SlimSnoopOS:
Read the last post if you want to stick with Marshmallow. Just know that these 4 core fixes are not permanent.
[Nexus 6P General] logic88:
Ah, thanks for the pointer. I didn't read the last few posts carefully enough.

So to apply the patches to my Marshmallow 6P, I would flash "twrp-3.2.1-0-fbe-4core-angler.img" as recovery (I was already using TWRP as recovery but wasn't able to boot into it) and then once I'm able to boot into recovery, install the "N5X-6P_BLOD_Workaround_Injector_Addon-AK2-signed.zip" kernel file?

Thanks!
[Nexus 6P General] SlimSnoopOS:
Correct. If it works, cool. But immediately back up your data to a computer. If it doesn't work, you'll probably have to upgrade to Oreo through the thread below and try again:

https://xdaforums.com/showthread.php?t=3716330
[Nexus 6P General] Skull2candy:
This specific rom is for 5x or 6p coz I see some people posting 5x issues here too and can you provide me link for the rom or this one is available on xda?
[Nexus 6P General] Skull2candy:
Oreo is not working after flashing boot.img and custom rom.. Can anyone please post step by step process to make it work.

Pure nexus 7.1.2 is working fine by this fix need help and which roms are currently supporting other then PN and PA?

---------- Post added at 09:30 AM ---------- Previous post was at 08:40 AM ----------

Done step by step but my device stuck on rom booting logo.. Any advice?
[Nexus 6P General] ivan leo:
with which rom Oreo or have you tried? To me it worked well with two different ROMs
[Nexus 6P General] Skull2candy:
Tried Nitrogen and AquariOS