yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] joshyzacariya:
Flash in the below order and it worked for me:

1. Flash factory image

2. Flash modified boot image for the one flashed in step-1

3. Flash TWRP

4. Ex kernal version

Thanks,
[Nexus 6P General] NoobInToto:
True cause? Hardware failure. When small cores fail in the same way as big ones, then you run out of cores to run on. No fix can save that.
[Nexus 6P General] zhangla:
OK. Explain why heat gun can bring back either small or big cores then? So first I applied 4core fix. It works for a couple months. Then bootloop again - is this because small core also failed? Then I used heat gun, and it works now - 2 days so far. If it's hardware failure with small/big cores, why heat gun works?
[Nexus 6P General] NoobInToto:
Idk what exactly the heating does. Whatever it does, it makes the cpu work properly,but temporarily. The surefire fix for this has been stated by multiple people: replacing/resoldering the cpu, or replacing the motherboard along with the SoC in it.

Some plausible theory by XDA users: heating up the phone connects solder joints, temporarily, perhaps by expansion of the metal.

So I conclude that the fault is with the cpu. The nature of the fault may be unknown, but the fault with the cpu is apparent. I would like to hear other plausible explanations, but I have not seen any other than this one.
[Nexus 6P General] Bobbaloo:
I thought it was more of a trigger that shut down the large core. If I look on my Ex kernel manager, when it gets above a certain temperature, the masheen only runs on the small core, shuts down large core till it cools down a bit. I'm not negating or supporting the solder theory though.
[Nexus 6P General] zhangla:
Still does not make sense... if it's a soldering issue, why 4core boot image works, at least for the first time for me, and maybe for a long time for others? I cannot imagine the soldering within the CPU clusters can be fixed by a repairman, because that requires special precision equipment, mostly robotics with nano-meter precision. If you were talking about the human-eye visible soldering, 4core boot image should not have any impact on those.

Of course, it can be a combination of multiple failure points, including big and small cluster failures, and soldering problems. It's not that likely but possible.

---------- Post added at 02:01 PM ---------- Previous post was at 01:58 PM ----------

I have seen some users claiming elemental X or EX kernel fixes the issue, but is that a temporary fix or a permanent one? Does the issue recur in a few week/months?
[Nexus 6P General] Bobbaloo:
I don't know. Been using my phone for about 14 months, purchased as a best buy refurb - I hope I never have to find out. I love this phone. I read through these threads in case I am faced with what seems to be the inevitable....
[Nexus 6P General] fuadhdmini:
Tried, not booting. Just stuck at Google logo.

Tried another bootimage made by other user modboot-oreo-oct-4-cores.img and this one booted fine.

Oh ya, I didn't flashed factory image, I flashed CortexRom
[Nexus 6P General] FlyOnTheWall43:
Any chance you'd be willing to create modified boot images for factory images a few months older than what you already have? My wife's 6P just started this bootloop, and she had to keep her phone a handful of versions behind current (not exactly sure which month she is on) in order to be able to keep her fitness watch connected to her phone (TomTom does some weird stuff with Bluetooth and isn't the fastest at staying up-to-date).

Completely understand if you don't, but would be greatly thankful if you did.
[Nexus 6P General] THERAJ12:
Has anyone been able to use the Benzo Rom 8.0? I get it running just really slow, all other 8.0 roms run fine just curious if anyone else has tried. I use the modified boot img for 8.0 along with the EX kernel and it's been great on all other 8.0 roms but Benzo. Thanks
[Nexus 6P General] joshyzacariya:
Hi,

I've created a 4cores boot image for Cortex rom v15.10; please download a give a try here.

Thanks,
[Nexus 6P General] fuadhdmini:
Yup. Saw his replied. Thanks for tagging him for quicker response.
[Nexus 6P General] NoobInToto:
The boot image fix shuts down the big cores completely. As far as I have seen, EX kernel manager shows big cores as offline and small cores fluctuating in tandem (same numbers on all 4 small cores).

---------- Post added at 01:45 AM ---------- Previous post was at 01:41 AM ----------

The theory is that the big cores fail first. Shutting them down makes the phone work for a while, until the small cores start failing too.

About the EX kernel, are you talking about the modified EX kernel in this thread or the original kernel by flar2?

---------- Post added at 01:48 AM ---------- Previous post was at 01:45 AM ----------

I doubted if he understood your request, so i rephrased the request.
[Nexus 6P General] zhangla:
So big and small cores both fail. Then heat gun brings them back? Trying to understand this...

I was talking about the Ex kernel app you can install and turn off big cores. I assume it does the same as the 4core boot image in this thread. That's why I am interested to know if Ex kernel app works as a permanent fix, while the 4core boot image still can fail.
[Nexus 6P General] NoobInToto:
The heat gun trick can bring both the big and small core online. The duration depends on individual devices.

The heating method is usually suggested for people who have their bootloader locked and need few seconds to boot in and toggle on OEM unlocking. During the initial stages, the failing big cores respond to heat( or cold, as some suggest). Now I don't have a theory why it responds to cold, but the thing is that the failing big cores respond to cold/heat, and so do the small cores when they begin to fail(that's my hypothesis).

I will tell you my experience.

My phone started bootlooping appx 1 year 2 months after the date of purchase. A fix (probably the first known software fix) involved letting the phone boot in (not by heating, but just allowing it to bootloop for as long as it gets in). Then EXKM was to be bought and installed, and power saving mode to be turned on. The power saving mode probably shuts down the bigger cores, I didn't bother to confirm that.

My phone ran well with this fix. After a while, I thought to take some risk and turn off the power saving mode in exkm. The phone lasted appx 2 days before bootlooping again. After this, I repeated the experiment (allowing the phone to run in power saving mode and then turning the power saving mode off, after a day or so). The phone didn't last long this time.

I concluded that my phone will never run without some fix, and have been using this fix since it appeared.

So as you can see, during the initial period, the phone did run without any fix for some time. I can only guess that it got worse after that.

I cannot generalize this behaviour to all phones. Plenty who have attempted cannot simply boot in by just letting it bootloop for a while (4-5 hours). I initially could do that, but I can't now.

My associate's n6p wouldn't boot in unless heated. Plenty others in this thread have observed the same. Their phones probably started looping at a later worse stage. Now, my associate's n6p is dead. It will not respond to the 4 core fix either. Other users have been at this stage too.

The n6p is probably the most expensive phone I have owned so far. I feel I have been cheated, seeing that it failed magically after warranty period. I've given up hope on this. Gotta move on. Those who are lucky enough to have bought it from google, can go on.The rest should start looking for other alternatives.
[Nexus 6P General] zhangla:
OK. My n6p is working now for the past 2 days after I used the heat gun. I also reapplied the 4core boot image yesterday.

However, I noticed that my root is gone after the 4core boot image... Using Ex kernel needs root. I wonder if I re-root and install the EX kernel to turn off big cores, will that be a more permanent solution, or nothing can save the n6p at this point but just waiting for the next failure...
[Nexus 6P General] alfred_chung:
Sorry to disturb you, after I unlocked my device, I tried to flash both normal fix and 4 -core fix img > flash TWRP recovery, but I still cannot get into recovery mode, is my procedure wrong?

1) Flash 4 core fix boot img.

2) Flash TWRP recovery.

3) Boot to recovery.

4) Bootloop.

Thank you.
[Nexus 6P General] KAEDE_RL:
repost
[Nexus 6P General] KAEDE_RL:
I've got response from the repairman today; it seems my nexus 6p is back to work from the pic he sent me. The phone is under delivery back to me now.

It seems my problem is not only with hardware. He re-soldered the CPU first so my cell phone wouldn't stuck at the rolling balls; but instead it rebooted immediately after reaching the home screen. The repairman said this means problem on OS. (I got this bootloop problem immediately after OTA upgrading to Oreo. Maybe the CPU failed in the upgrading process then the OS was messed up).

Then he managed to downgrade the OS version to that before my upgrading, without need to unlock the bootloader. According to my possibly inaccurate understanding, he has some special firmware tools to import some boot files of older version android into the phone through special port, so that the phone recognize the OS as older version. Then he sideloaded android 6.0 to make the phone work, then upgraded to 8.0 again.

There still are some minor problems though. He suggested to backup all data and factory reset the phone when I get the phone.

Most of data are still there expect that the contacts files corrupted. But since they're always synced with google account it's not bad.

Swipe down on home screen is not working.

The battery and RAM are upgraded.

I'll shoot a video when I receive and check the phone.

Regarding how to reach the repairman - maybe you should find someone in China you can trust to help you contact and pay to the repairman. I can also help if you feel you can trust me. I'm still not permitted to paste link here; maybe i can send link through private message.

And by the way - you can wiki for Ball Grid Array which is how CPU are soldered on the motherboard to make it easier to understand why simple heat gun could work to improve soldering. It's quite different from my impression of soldering... I learned this term from the repairman.
[Nexus 6P General] NoobInToto:
Like many of us here, I do not have any contacts from China. Can you pm me the details and the approximate cost of the repair? Thank you.
[Nexus 6P General] aoaleman:
Yep, tried both the latest and previous build. Slows down really bad.
[Nexus 6P General] jcdgarcia:
Thank you so much for this!! I revived my 6p!
[Nexus 6P General] zhangla:
1 month ago, my 6p had bootloop issue. I used the 4core image here, and it worked.

1 week ago, my 6p got into bootloop issue again... I did not do any kind of upgrade since I applied the 4core image

3 days ago, I used heat gun trick, and my 6p booted up again. I then applied the 4core image right after that.

Today, my 6p became total brick after working for 3 days flawlessly... It is now just a hard cold brick, does not respond to any kind of key press/combo, charging or anything. The only thing shows it's still alive is when I plug it on a PC and press power key for 1 min, the PC recognizes a USB device but could not install the driver. Under Device Manager, it says "QHSUSB_BULK".

What a horrible product Google/Huawei has made!
[Nexus 6P General] arepmanap:
Bootloop

I've follow all the steps to flash the img file but my nexus 6p stuck on google logo with unlock icon at the bottom, what should i do ? :( i'm on oreo btw but i flashed with N2G48B one

---------- Post added at 03:52 AM ---------- Previous post was at 03:40 AM ----------

Can you pm me the details ?
[Nexus 6P General] SombraDu:
The Best way to solve the problem thoroughly is to replace a new same Soc which I just did.
[Nexus 6P General] c4ndy:
Mine is totally not booting now at all and doesn't respond to charging, even after I used my Oreo4Cores-oldfstab.img. It briefly gave a flash of the red LED a few days ago when pressing the power button. Not sure what to do, but probably going to take it to a shop and see if they know any tricks.
[Nexus 6P General] 3l1k:
You can try to go to nearest repair shop and ask them to heat cpu - it can solve problem (like on old graphic cards) by resoldering/expanding cpu/solder points.

I will do it if my phone will go to bootloop with 4 cores.
[Nexus 6P General] NoobInToto:
Perhaps [MENTION=8636134]KAEDE_RL[/MENTION] can ask his repairman the nature of the problem, why the cpu responds to heat and some possible homemade fix ( by opening the back panel and doing some simple operation).
[Nexus 6P General] Leorreia:
So suddenly my phone got working again that same day I wrote the last message here. I used the phone normaly for a week and yesterday It started to restart again. While I had my phone working I turned the OEM unlocking on. But, my phone is still Locked. Why is that? I tried to run the commands in the powershell and I only get errors:

"

PS C:\Users\Usuario\Desktop\Leo\nxs\flash oreo> fastboot flash boot Oreo4Cores

fastboot : O termo 'fastboot' não é reconhecido como nome de cmdlet, função, arquivo de script ou programa operável.

Verifique a grafia do nome ou, se um caminho tiver sido incluído, veja se o caminho está correto e tente novamente.

No linha:1 caractere:1

+ fastboot flash boot Oreo4Cores

+ ~~~~~~~~

+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\Usuario\Desktop\Leo\nxs\flash oreo> fastboot flash boot Oreo4Cores.img

fastboot : O termo 'fastboot' não é reconhecido como nome de cmdlet, função, arquivo de script ou programa operável.

Verifique a grafia do nome ou, se um caminho tiver sido incluído, veja se o caminho está correto e tente novamente.

No linha:1 caractere:1

+ fastboot flash boot Oreo4Cores.img

+ ~~~~~~~~

+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\Usuario\Desktop\Leo\nxs\flash oreo> fastboot flash boot [Oreo4Cores]

fastboot : O termo 'fastboot' não é reconhecido como nome de cmdlet, função, arquivo de script ou programa operável.

Verifique a grafia do nome ou, se um caminho tiver sido incluído, veja se o caminho está correto e tente novamente.

No linha:1 caractere:1

+ fastboot flash boot [Oreo4Cores]

+ ~~~~~~~~

+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\Usuario\Desktop\Leo\nxs\flash oreo> fastboot flash boot [Oreo4Cores.img]

fastboot : O termo 'fastboot' não é reconhecido como nome de cmdlet, função, arquivo de script ou programa operável.

Verifique a grafia do nome ou, se um caminho tiver sido incluído, veja se o caminho está correto e tente novamente.

No linha:1 caractere:1

+ fastboot flash boot [Oreo4Cores.img]

+ ~~~~~~~~

+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

PS C:\Users\Usuario\Desktop\Leo\nxs\flash oreo>

"

What should I do?
[Nexus 6P General] 3l1k:
There is no way to open the phone without unsticking lcd at least. So it is better to go to repairshop. Otherwise you can broke your lcd
[Nexus 6P General] NoobInToto:
The video for replacing battery showed the strip I think. Opening the phone involves removing the camera bar and the bar at the bottom. Other than these 2 parts, I don't think one can damage any other components by just opening the phone.

After my phone is really dead, I think I will attempt opening it as an experiment lol.

Anyways, if the exact procedure is known, atleast some local unofficial repair centre could attempt it.
[Nexus 6P General] zhangla:
This is what I will do. Just bought the battery replacement + tool on Ebay. Since my phone is completely dead, won't even go into bootloop, at this point, this will be my last resort.

I plan to open it up, replace the battery, then heat gun on the CPU area for 2 min. Then I will try again see if it can come back.
[Nexus 6P General] NoobInToto:
Good luck. Be careful when dealing with the display connector strip(or whatever that part is, related to the display). I read it breaks easily. Failure rate is pretty high.....as per a YouTube video comments.
[Nexus 6P General] NoobInToto:
Does your phone show up when the following command is used?

fastboot devices

If this command yields some error, then you are probably not running the command prompt from the platform-tools folder
[Nexus 6P General] El Niche:
Thank you for this fix. Bootlooped yesterday and was able to save it using the EX kernel. At least for now I saved my files.

So whats the general consensus here. should I start to look for a replacement? Is it a matter of weeks before the other cores luck out on me? I really like this phone, but Id rather look for a replacement so when (or if it dies) I have something already
[Nexus 6P General] c4ndy:
A new update on my situation.

I used an iron to heat up the entire back cover of the phone. It started booting, but this time bootlooping even though my previous Oreo4Cores-oldfstab.img worked before it had gone completely dead. Can't get to the recovery mode. Now it just randomnly alternates between 4 scenarios:

1) Bootloop to the Google logo

2) Charging screen with battery containing a lightning bolt and no charging animation

3) Red LED flashes once

4) Red LED flashes multiple times for some period of time

I'm inclined to think it's a battery issue. But still not sure if it's a problem with the entire SoC.
[Nexus 6P General] zhangla:
How much does it cost to have entire SoC replaced? Do the regular cell phone repair shops do that?
[Nexus 6P General] NoobInToto:
No , the regular shops will just offer to replace the motherboard (usually they will redirect to official service centre, unless they have somehow procured motherboards). Only the people in China operate on soldered SoCs, as far as I have heard.
[Nexus 6P General] SlimSnoopOS:
Yes. Multiple people in this thread and the 5X thread have had their device bootloop again even when using this fix for weeks or months.
[Nexus 6P General] Leorreia:
I wasnt really running the command from platform-tools folder, I didn't know that. I tought I just needed to run the Powershell from the folder where I put the Oreo4Cores.img in. But I just tried to run the Powershell from the platform-tools folder and I got exactly the same error message I posted before. So I also tried to run the "fastboot devices" from the Powershell (from the platform-tools folder) and got this error:

PS C:\Users\Usuario\Desktop\Leo\nxs\platform-tools> fastboot devices

fastboot : O termo 'fastboot' não é reconhecido como nome de cmdlet, função, arquivo de script ou programa operável.

Verifique a grafia do nome ou, se um caminho tiver sido incluído, veja se o caminho está correto e tente novamente.

No linha:1 caractere:1

+ fastboot devices

+ ~~~~~~~~

+ CategoryInfo : ObjectNotFound: (fastboot:String) [], CommandNotFoundException

+ FullyQualifiedErrorId : CommandNotFoundException

Suggestion [3,General]: O comando fastboot não foi encontrado, mas existe no local atual. Por padrão, o Windows PowerShell não carrega comandos do local atual. Se você confia nesse comando, digite: ".\fastboot". Consulte "get-help about_Command_Precedence" para obter mais detalhes.

PS C:\Users\Usuario\Desktop\Leo\nxs\platform-tools>

~~~~~~

Should I install something from the platform-tools folder? I just have this folder sitting in my computer with some files and folders in it but I did not install anything. I also just copied the Oreo4Cores.img to the platform-tools folder (it was in another folder).

So, everyone is doing it, getting their phones back again, just mine is not working, but, probably I am doing something wrong. I just can't figure it out because I am really bad at I.T. stuff.

Also, when I turn on my phone and that screen with the options "start, reboot, poweroff, etc" appears, it says: "Device is LOCKED" does that have something to do with it? I sure activated the developer mode and turned on the OEM unlocking.

Please help me :(
[Nexus 6P General] shadowcore:
Damn, this thread is the first thread on xda that hurts me to read it. Its so painful to imagine losing a premium device for little more than a year of use. No support from the OEM.

Im a nexus 6 user, and when the 6p came around and it was from huawei, i was skeptical. Same for the 5x.

I had a similar experience with LG with a failing baseband(LG 4X HD) but at least the device was able to open.

What i wonder though is: Did huawei/google know about this?

In my case with LG, they knew and sold a defective product.

Edit:

The 5x has the same issues?
[Nexus 6P General] KAEDE_RL:
It's just the problem of CPU soldering. As I wrote in last post you can wiki for Ball Grid Array which is how CPU are soldered on the motherboard to make it easier to understand why simple heat gun could work to improve soldering temporarily. The soldering contact seems sophisticated and not as "hard" as I'd thought [MENTION=2867550]3l1k[/MENTION]
[Nexus 6P General] Bobbaloo:
As long as the thousands of consumers that keep sending the message that: 1. They can make these devices & charge outrageous $ for them & 2. A two year or less life expectancy is ok. AND 3. You don't have to be accountable because we'll keep lining up to buy more.... This situation will just continue to get worse. Hey, EVERYONE has one in his pocket. Who could have foreseen such an industry?
[Nexus 6P General] KAEDE_RL:
My repairman said he can replace SoC; but due to some encryption mechanism envolving SoC and eMMC all data will be lost after replacement of SoC.

He recommends re-soldering SoC, as in most cases it's just the soldering problem. [MENTION=5737694]zhangla[/MENTION]
[Nexus 6P General] setitandforgetit:
Confirming checklist in attempt to recover photos

Hi folks:

I've got a 6P that started boot looping in July, and I want to try to pull down photos from my phone. I unfortunately didn't auto sync them. If I'm able blow dry my phone back to life, I'm assuming I'll have a limited window of time to download my data. I would truly appreciate any advice or feedback on my checklist to maximize my chances:

Use a blow dryer and aim between fingerprint sensor and camera glass. Hope phone finally boots up

The moment phone is on, go to Developer Options, and turn both OEM unlock and USB debugging on

Use ./adb pull /sdcard/DCIM/Camera to begin downloading photos

Turn on battery saver in attempt to keep phone functional for longer

Turn on Google Photos sync as a secondary method for backup? Maybe?

Questions for the community:

Should I keep the phone on while blow drying it? Do I need to buy a heat gun instead?

Would you recommend opening the phone up for blow drying or keeping it intact? I don't mind ruining the phone if it means I can get my photos, but I'd be worried about accidentally damaging board/chip/whatever.

Are all my photos truly just located at /sdcard/DCIM/Camera? Are there any other folders I should try pulling down?

Do I need TWRP for anything else?

After turning on "OEM unlock" via Developer Options, does "adb fastboot unlock" still completely wipe my phone?

Anything else I should consider or change? Appreciate the help!