yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] federalreserve:
I followed your steps above and I have a couple questions. Is there a specific sequence to flashing the above files? In order, I flashed the 1) bootloader, 2) radio, 3) oreo4cores.img, 4) twrp, 5) system image (image-angler-opr6.170623.017).zip.

My phone initially booted fine and then I tried to set it up and it went back into the bootloop of death. Is there something I did wrong? Does the modified oreo4cores.img work with all versions of Oreo system images? Thanks in advance for your help.
[Nexus 6P General] sharpz811:
Ok bro first i forgot to tell you about one step which was to flash vendor after you've flashed twrp, boot, bootloader, radio then continue the rest of the steps but that's exactly what i did in a matter of 10 minutes max but i wouldn't know what your issue is as it worked for me and many others. I guess you can try to just flash the whole thing via flashing the flashall.bat but i believe right after that you'll need to flash the modified boot.img. if that don't work try doing the same steps but reverting to nougat and if that don't work then maybe your hardware is screwed unfortunately. I'm still waiting for mine to do the same thing like yours because apparently this ain't a permanent fix.
[Nexus 6P General] federalreserve:
Cool, thanks for all your help sharpz811! I didn't know to flash the vendor.img as well. I will try that and see if it works. I'm hoping I can save my 6P for a little while...
[Nexus 6P General] rachitup:
OEM Locked/ Phone is locked

How do you wish me to get into settings and then developer option when my phone is stuck in bootloop?

Numerous attempt to start the phone only fora minute..but failed...what to do now?
[Nexus 6P General] DodoGTA:
Heat your phone up or let it go to battery saver mode
[Nexus 6P General] NoobInToto:
2 working methods for the same trick:

Try heating the the area between camera bar and fp sensor with:

1. Hairdryer for upto 10 minutes.

2. If that didn't work, use an electric heating pad(the one we use to apply heat to our body for medical purposes) for upto 25 minutes. The heating pad trick worked for a friend I know.

All the while you have to keep it bootlooping. With some luck, you will get in for enough time to turn on that stupid OEM unlock option.
[Nexus 6P General] darkriff:
Did you perform a format data in TWRP?

---------- Post added at 08:12 PM ---------- Previous post was at 08:10 PM ----------

Maybe you did something wrong with the flashing, did you flash everything as stated?

---------- Post added at 08:14 PM ---------- Previous post was at 08:12 PM ----------

I replaced the battery of mine and know its running smooth with excellent battery life as before.
[Nexus 6P General] bm23:
I'm having the same bootloop issue. I understand that there is a fix but it will erase all data on my phone? I've come across many apps and software that are able to recover data from wiped/reformated phones. I was wondering if I could apply the bootloop fix and then use data recovery software to retrieve my photos?

I'm running the latest stock android, unrooted. Thanks in advance for any help! :)
[Nexus 6P General] XCnathan32:
I always like to flash from a fresh system, it eliminates a lot of possibilities for error, also, I flashed the zip normally in twrp, I didn't side load it, not sure if that would make a difference
[Nexus 6P General] outbackpaul:
What did you do, boot to system and then back to recovery?

My recovery still asks for a password. Was hoping to sideload the kernel to avoid having to do a factory reset.

I'm going to have to continue tomorrow after work. Time for bed.
[Nexus 6P General] SGT:
Unfortunately it's still not working on mine. Just hangs on the Google logo.

Even tried re-flashing stock android, robooting the bootloader, then flashing the 4 cores IMG. No success.
[Nexus 6P General] symbiance:
sadly i think mine has a locked bootloader still, and dont think mine can be fixed because of that :(
[Nexus 6P General] kaustubhb:
I had never experienced bootloop on my nexus6p .. but I am having early shutdown issue .. will this solve that issue as well ??

Just curious to know .. thanks in advance .. ignore if I am asking too much .. ?
[Nexus 6P General] smoysauce:
FWIW, I placed mine over a wax scent warmer while it was plugged in and allowed it to bootloop. After about 10 or 15 minutes, it finally booted and I could enable OEM unlock. (It was just slightly above the heating back, not touching it.)

Just flashed the IMG file and it's currently booting.
[Nexus 6P General] XCnathan32:
Are you sure you flashed Android 7.1.2? That happened to me when I accidentally flashed the wrong image version. And will the twrp image work for you?
[Nexus 6P General] XCnathan32:
It might, there's only one way to find out. If you do flash these images, could you please report if it fixed the solution? It would be awesome to kill 2 birds with one stone here.
[Nexus 6P General] kaustubhb:
Will try this once I reach home & I will let you know ..
[Nexus 6P General] dray:
How long does it take to boot after flashing? I am stuck at the animation screen. Prior to flashing, it would not get past google screen so there is improvement. TIA
[Nexus 6P General] Bubba_:
same here

same here. I'm a little mad I got hasty and wiped my device
[Nexus 6P General] stevemw:
Tried to thank you after reading this on the Google feed article (https://www.xda-developers.com/nexus-6p-bootloop-fix/amp/ ) but apparently the numbnuts can't get their oauth link to disqus to work. Good work!
[Nexus 6P General] Jmahoneyy:
No dice for me. I got so excited to have my phone back after 5 months.

Flashed factory 7.1.2

Flashed boot.

Reboot sends into loop.

Flashed boot + modified twrp.

Reboot & reboot into recovery sends into loop.
[Nexus 6P General] AgentBEATS:
Flashed the boot and it has stopped the loop but now my phone just sits on the Google boot image. It's progress at least. Any ideas what I should do next?
[Nexus 6P General] javitomen:
Hello man, do you have any succes with the Android O?
[Nexus 6P General] stricker:
After flashing twrp i cant see folders in my internal storage to flash ex. Any help?
[Nexus 6P General] gaganchohan:
So it works for marshmallow too or I need to install 7.1.2?
[Nexus 6P General] XeniX_Force:
Sir can you please please try a fix like this for LG G4 TMobile variant (h811) please?

im eagerly waiting for a reply
[Nexus 6P General] kronflux:
[MENTION=5288606]XCnathan32[/MENTION], could you detail the modifications you made to the boot image?

would like to incorporate this into a custom rom build, but don't even know where to start. Even if I had to modify the resulting built boot.img rather than having it build that way, I'd like to know what exactly was done.

Thanks!
[Nexus 6P General] headcreepz:
Same as me
[Nexus 6P General] c4ndy:
Hi. No, I did not format data with TWRP. I had the original TWRP flashed, not the 4 cores patched version (couldn't boot into recovery). I tried the 4-cores TWRP image also and it can boot into this recovery mode, but I don't know what I should do (shows storage as 0mb, I guess because it's encrypted).
[Nexus 6P General] datrmon:
Thanks for the solution...it worked like a charm...

I want to know if there is a solution to installing OTA after applying the fix to the rom.

I just got the Android 8.0 OTA but having Verification issues.

Anybody with the fix?
[Nexus 6P General] darkriff:
Yes, thats why you need to format it using twrp, make the format and try again
[Nexus 6P General] xian2380:
please update latest ex kernel
[Nexus 6P General] c4ndy:
Will the format remove all user data? ie, total wipe? Isn't there a way to make the phone boot with just 4cores/1 core without formatting? It seems a bit excessive since I know the pattern lock and any credentials required to access the data. Maybe there's a way to store it all then do this 'format data'?
[Nexus 6P General] darkriff:
Up to my knowledge the only way is to format because of the encryption used by Android O. If you had sensitive data you would have rescued it before attempting the upgrade to oreo.

When I did the upgrade I had the same problem phone freezes on the dot. I did the format and problem solved.
[Nexus 6P General] T_Squared451:
Instead of re-hashing the background, I'll just re-quote it...

So... To get around the TWRP password/forced encryption issue I followed the instructions in this video...

https://www.youtube.com/watch?v=zpYVDJgusLo

So after doing the Wipe Data/Format Data in TWRP it was important to note not to allow it to do a system reboot because it would re-encrypt the data. Simply reboot recovery in TWRP to verify that TWRP was no longer asking for the password etc. Once back in TWRP, and with the USB cable connected, you should see phone on the PC and be able to copy the zip files to the phone. Once done you should be able to see the files in TWRP when you go to install them.

So great... I got through the process...

Now the new questions....

First, what's the process for keeping the phone updated? You got the montly OTA security/etc. updates. I suppose you don't want to mess with them because of the 4 core issue etc. So you have to deal with them manually I suppose. What about operating system updates? What's the process for that?

Since the EX kernel and SuperSU was flashed, data is now encrypted. There is an option in setting to encrypt the data. I suppose you would want to do that. But do you have to make a backup, go through the TWRP password/encryption workaround (see video), each time you want to do an update?
[Nexus 6P General] c4ndy:
So you were able to follow these instructions and access your data (music, photos, etc)?
[Nexus 6P General] T_Squared451:
The first step in that video was wiping data - so the data is gone. However, once the wipe/format was done then the encryption was removed and you could proceed to copy the zip files to the phone from the PC. Again, since data was longer encrypted, you could see the zip files in TWRP and install them. If I had done a backup (which I didn't) with TWRP before I started, I suppose I could have restored it after I was done installing the EX Kernel and SuperSU zips.
[Nexus 6P General] SlimSnoopOS:
Fastboot! Follow section 9 of this guide. Use the modified 4 core boot image instead of the one included in the factory image.

https://xdaforums.com/showthread.php?t=3206928

The phone will encrypt on boot if you use a stock boot image. Custom kernels and SuperSU do not forceencrypt. Your phone will maintain its present encryption status after flashing: if encrypted/not encrypted before flash, it will be exactly the same after flashing.
[Nexus 6P General] c4ndy:
Damn that really sucks =/
[Nexus 6P General] Shemploo:
So I can't get this fix to work, here's my setup:

- Flashed latest Oreo release.

- Flashed Oreo4Cores.img (boot)

- Flashed twrp3_1_1_4Cores.img (recovery)

1. Rebooting, leaving the phone be for over an hour, the phone just loops between Google image and orange "can't verify" over and over.

2. Trying to boot into TWRP recovery via bootloader menu, same thing Google/Orange msg

3. Trying to tell bootloader to boot recovery "fastboot boot twrp3_1_1_4Cores.img" same thing, Google/Orange msg over and over.

Next, I will try on Nougat, but I doubt I'll have any luck with that either.

Any thoughts? Ideas?
[Nexus 6P General] NoobInToto:
You must also consider the possibility that the phone is dead... If you read this thread, you'll find that the fix hasn't worked for some people. I'm afraid the phone is dead for them.
[Nexus 6P General] bm23:
Friendly bump :) Any help would be greatly appreciated!
[Nexus 6P General] c4ndy:
I don't think that's a reasonable assumption however. If you can get a bootloop or something on the screen then there is a CPU running. Therefore it can work.
[Nexus 6P General] SlimSnoopOS:
True. However, it doesn't help how some folks have had this 4 core boot image running and then that too begins bootlooping.
[Nexus 6P General] c4ndy:
Hey guys, just an update. I just modified the image from [MENTION=5288606]XCnathan32[/MENTION] (Boot.img from stock 6.17, 8.0 firmware. This Image is the from the first official release of Android O, and is modified to use 4 cores) with the old fstab that has the encryption line in fstab.angler. Basically if you have an encrypted phone (asks for pattern at boot) then you can use this without wiping user data:

https://nofile.io/f/ZVZwhoaRPdA/Oreo4Cores-oldfstab.img

Would be good if [MENTION=5288606]XCnathan32[/MENTION] could post it alongside his no-encryption version.
[Nexus 6P General] frootloop:
Hey, new member. Just thought I'd share what worked for me.

I was browsing google maps and google keep last night around 10pm, after setting my phone aside I noticed it was stuck in the boot loop sequence. I was dismayed because my girlfriend and I are going on a trip for 2 weeks tomorrow and not having my phone would be a real PITA.

Unfortunately my phone was OEM locked. The hair-drier method worked on my phone pretty reliably, although the window of time I had before it would loop again would get shorter the more I did it. At first it gave me about 20 minutes or so, and then down to 5, and then less. So I would recommend if you need to unlock your phone, do it immediately.

I tried installing the two 7.1.2 firmware boot images, and after following the steps on the first page it did allow my phone to move past the loop, but I was stuck in another loop. It couldn't check for corruption, and wouldn't log me in unless the phone was locked again.

Afterward I thought that maybe if I did a hard update to 8.0 firmware, the OEM one, and restored my phone to factory I may regain control of it. I downloaded the firmware from their page and after installing successfully, it gave me the old boot loop I had before. At this point it was almost 2 in the morning and I was losing hope.

Luckily I was able to unlock the phone again without booting it up as I had the drivers and connection already established. I installed the modified 8.0 firmware that [MENTION=2004880]xls654[/MENTION] generously provided. This overwrote the current 8.0 install on my phone and after booting it up, I was given the 'unable to check for corruption' message, but after it booted up normally and allowed me to start from scratch on the updated OS.

Although I didn't retain any of my files, I am happy that my phone is working again. Although I'm not using all 8 cores, its better than having an expensive paperweight on a trip that I'll definitely need a working phone for. I think I could have kept my files had I been accustomed to this process, but I had never flashed a phone before or done anything to them, so I didn't know the process.

Thank you for your kind help guys!
[Nexus 6P General] maity-iman-2015:
Will it work on September Update? (on 15th Sept, 2017 google released this 8.0.0 (OPR6.170623.017, Sep 2017) factory image)
[Nexus 6P General] T_Squared451:
Ok... So section 9...

So I would need to go out and get the latest build etc. as indicated in the instructions. I would need to follow the instruction in sequence and would do all the flashing as shown in the code window on that post with the exception of 2 things. First, the erase and flash cache would not be necessary. Secondly, I would substitute for the boot image flash (fastboot flash boot C:\angler\images\boot.img) one of the boot images listed on the OP's initial post (for example: 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 [MENTION=2004880]xls654[/MENTION] for figuring out how to get Android O to work.). Does this sound right so far?

After I do all the flashing shown in section 9, I would have to wipe cache/dalvik cache, re-install EX Kernel and reinstall SuperSU. That sound right?

So in my previous post, my fat fingers may have caused confusion. Here is what I meant to say:

Which got the following response:

Ok... Since I would have re-installed EX Kernel in the above process, the phone would remain unencrypted after it boots back up. But when all finished I would want the phone encrypted, no? So what to do? Go into Setting/Security and select Encrypt Phone? If I do that, then what? What happens when I need to do the next update? Can I go back into Settings/Security and unencrypt the phone or is it a once and done thing that can't be reversed? If it can't be reversed, will I have to wipe and re-format in TWRP (which would require that I do a backup before and restore after, no?) I noted in the image information mentioned above:

What's that mean exactly? Installing EX Kernel and SuperSU seems to eliminate the forced encryption issue also. Wouldn't I still need to encrypt the phone after installing the new build?

So somebody is going to keep the 4 core configure boot images on the OP's initial post up to date for the foreseeable future? We would continue to come to this post for our continuing (boot image) update needs?
[Nexus 6P General] SlimSnoopOS:
Yes, but you must flash the modified 4 core stock boot image in order to move to a 4 core custom kernel.

Now you would flash SuperSU then 4 core EX.

From what I gather from reading, the 4 core TWRP in the OP does not recognize internal storage if you are encrypted. If this is wrong, someone let me know. Normal TWRP doesn't have this issue so I'm sure the OP could sync it so that encrypted partitions do not present an issue unless being encrypted and other dependencies interfere with the need for 4 cores. I cannot answer this for you.

See above reply.

Sure, if someone is willing and OP is unable to.
[Nexus 6P General] c4ndy:
I believe it should, but don't take my word for it as I'm not that familiar with Android and how it works.
[Nexus 6P General] T_Squared451:
The modified 4 core stock boot image being what I indicated in my question or others listed in the OP's initial post. I.e.

Any of those correct? Presumably the latest and greatest preferably? So either stock 48C, 7.1.2 or stock 6.17, 8.0 firmware, depending if you wanted to make the jump to Oreo or not. Right?

Presumably in that order?

That's what I experienced. If data was encrypted, then TWRP could not see it.

So I'm guessing.... If I encrypted the phone after an update... I would have to 1) do a NANDroid backup - using TWRP - of at least the Data partition (copy the backup to the PC before wiping Data partition). 2) follow the steps in section 9 of the guide noted previously. 3) Do the wipe and format to remove the encryption. 4) Restore the Data partition using TWRP (copy the Data partition backup back to the phone first). 5) Reinstall SuperSU and EX Kernel.

That sound right?

Edit: 6) re-encrypt the phone from phone Settings/Security if desired?
[Nexus 6P General] c4ndy:
See my most recent posts with an image that can get around this without having to format user data.
[Nexus 6P General] SlimSnoopOS:
Correct to all the above.

I've never done all that so try and see.
[Nexus 6P General] zlobby:
I am able to flash stock 48C, 7.1.2 firmware, but when i attempt to flash stock 6.17, 8.0 firmware, it gets stuck on the google logo. Any advice?
[Nexus 6P General] SlimSnoopOS:
Do you have the endless bootloop issue? Cuz your post doesn't seem to belong here.
[Nexus 6P General] T_Squared451:
Not sure what that will do for me...
[Nexus 6P General] swapavi:
So I flashed the Oreo modded boot img on a clean flash of the Oreo factory image just so that I would stay decrypted.

Once I set up my phone I flashed Franco kernel and magisk root

Only problem is that the 4 big cores are still offline.... I thought flashing a different kernel would overwrite the modded boot img?
[Nexus 6P General] SlimSnoopOS:
Do you bootloop when using stock software? If so, you really shouldn't be flashing any kernel images from outside of this thread.

Franco and some other custom kernels will use the same ramdisk as what was previously available so it may not enable the big cluster. The other explanation is that the big cluster is offline in this terrible CPU due to excessive heat.
[Nexus 6P General] c4ndy:
Well yeah, you've already formatted so it won't help you I guess.
[Nexus 6P General] swapavi:
Nope, no bootloop. (Not yet at least...)

But I just cleaned flashed the factory image, this time without the modded boot img and then installed Franco and magisk again.

4 big cores still offline and my phone is lagging bad. I just don't understand it
[Nexus 6P General] SlimSnoopOS:
Please don't post here then. Your post is entirely irrelevant here and will be misleading for people who read this later.

You're likely just being thermal throttled. The big cluster will come online after the phone cools down. This happens anytime you flash something or the phone is in a warm environment.
[Nexus 6P General] ApoelEllhnwn:
Today I faced bootloop of death.

Can someone share for me latest Franco kernel for 4-cores on androd oreo?

Thank you very much
[Nexus 6P General] draxz:
How to upgrade

Hello everyone,

I had a Nexus 6P running Nougat when it was in boot loop and I had applied the previous fix, but my phone is still severely slow. Could I update it to Andriod O using the above? Also, I am a complete NOOB, do I download all the above files? or just the 8.0 version. Is there a step by step.

Thank you in advance.
[Nexus 6P General] swapavi:
Don't tell me where to post. This is completely relevant because I flashed the modded img provided here and I couldn't get my big cores back online because of it. (Which is a good thing for everyone in this thread who is bootlooping btw)

And I fail to see how this is misleading anyone. It was a pretty clear post.

It wasn't thermal throttling either, phone was cool to the touch.

Anyway, apologies for this OT post.
[Nexus 6P General] SlimSnoopOS:
It just doesn't make sense to me why you would flash any 4 core boot image from here if you are not bootlooping. Just flash the factory image, wipe the entire device and you'll be fine.
[Nexus 6P General] maity-iman-2015:
Yes, it worked. The same 8/22 fix worked on Android O September update.

One I just faced TWRP not opening (though flashed), I did a complete power off, went to bootloader, flashed TWRP again. And worked.
[Nexus 6P General] swapavi:
First time I did it was for preventative measure and just wanted to see if it crippled performance at all.

This time it was to keep my phone decrypted when I flashed factory image.
[Nexus 6P General] c4ndy:
You're welcome :)
[Nexus 6P General] NoobInToto:
Is it possible to update from August build to September build without losing data?

If so, what is the exact procedure?
[Nexus 6P General] rob_tuna:
how to start over

I know i messed up somehow, i have twrp installed I did everything in step 9 then super su then the ex kernel. It still wont boot, it stays at the google logo, ive done the same thing 3 times already. Every time I start at step 3, doing the fastboot format userdata and such. is there a better way to wipe everything, maybe even twrp?
[Nexus 6P General] c4ndy:
I was already on Oreo but was offered an update (maybe September update? I don't know it didn't say anything). I tried updating it, started getting the bootloop again. So I flashed a modified boot.img from OPR6.170623.017, Sep 2017 (https://dl.google.com/dl/android/aosp/angler-opr6.170623.017-factory-9070766c.zip) after other boot.imgs I tried didn't work either (still got bootloop). I did all this with the encrypted string still intact in fstab.angular (wait,check,forcefdeorfbe=/dev/block/platform/soc.0/f9824900.sdhci/by-name/metadata).

This still didn't work so I tried flashing the recovery image twrp3_1_1_4Cores.img again as suggested by [MENTION=7421097]maity-iman-2015[/MENTION]. Then I finally got it to boot again, but it showed that the update failed. See the attachments.

I think perhaps if you flash SuperSu again, download the update and use Flashfire to install it and then flash another boot.img you would probably get 'the update' without formatting user data.