yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] Symber:
Alright, been at this for hours with no luck. Maybe I'm just missing something obvious. I bootloop at the Google logo like basically everyone else. I can get to the dead Android screen but cannot access recovery. Adb devices shows nothing, but fastboot devices shows the proper serial. I had the proper settings checked, so I was able to unlock my bootloader with the fastboot command. My problem seems to be the same as this post (https://xdaforums.com/showpost.php?p=73946100&postcount=1330) except that I've been avoiding Oreo to reduce variables.

This is where I must be having some kind of issue. At first, I simply tried flashing TWRP. The fastboot commands act as I expect and everything is successful, no errors. I try to reboot the device into recovery and it looks identical to before. Dead Android screen, recovery option just restarts the bootloop.

Since TWRP didn't seem to work (so I can't flash the zip) I tried flashing the 6p48C boot image. Reboot and no change. Tried flashing each of these files in different orders along with the B version even though I was fairly certain I was on 48C. No luck.

Next I downloaded the 48C factory image and extracted bootloader, recovery, system and vendor images and flashed them following the instructions someone outlined a few pages before this post. All flashed successfully according to the command prompt. I followed that up with the 6p48C boot image and TWRP. Powered down the phone, turned on and the bootloop was still there, pull up the dead Android and still can't get into any kind of recovery.

Hopefully I'm just missing some simple syrup and I can kick myself when someone points it out. Any help would be appreciated. I've got 2 bootlooping 6Ps and I'm typing this on a potential 3rd victim lol
[Nexus 6P General] athuljays:
Same Issue

[/COLOR]

Same issue here too. I also have a problem where when I plugin the charger, the device boots itself automatically and goes into bootloop. Are you facing this too?
[Nexus 6P General] jassun16:
I am also in the same state couldn't get past the bootloop with trying with different factory images and the appropriate mod images from the OP. I couldn't get into the recovery and the phone just bootloops. Hope somebody would help us with a smart solution.
[Nexus 6P General] Symber:
Yeah. Forces me to charge the phone in the dead android screen, but at least I can work around that issue. I'm glad to at least not be alone; this way I know I'm not just crazy and it actually probably is flashing the phone properly like it appears. Hopefully we can get some help.
[Nexus 6P General] widermargins:
I was in the same situation for days and it drove me CRAZY. Finally tried wiping the EFS and it worked for me! Might be worth a try?

1. Using fastboot, flash the stock ROM (7.1.2 or 8.0, whichever you prefer--I used 8.0), then flash TWRP.

2. Try to reboot into recovery. Chances are, you'll be stuck in bootloop again. At this point, I used a hairdryer to overheat the device; after about 15 minutes or so (getting it up to 45 Celcius), it reboots into TWRP! (I read that some people put the device into a freezer; I didn't try this.)

3. At this point, connect device to your laptop. Open command prompt and check that the 6P is connected with "adb devices". The serial number should show.

4. Then here's the crucial part: using the command line, type in the following commands one by one:

adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1'

adb shell 'dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2'

adb reboot

5. Your 6P might reboot just fine! (Might take a few minutes though.)

**You should also be able to wipe EFS via fastboot, but when I tried the commands given in other sites, I got "permission denied". Using ADB worked.

Hope this helps!
[Nexus 6P General] gizmik:
How to detect revived phone with this method?

I'm suspecting that some guy sold me Nexus 6p revived after bootloop with this trick, I see only 1.56ghz for both clusters in CPU Z and 4-8 cores never go beyond 1.4ghz under load.

How else I can prove this theory?

I just don't want to be scammed.
[Nexus 6P General] SlimSnoopOS:
CPU Z does not display the speeds for both clusters, only the small cluster. I'm on a 5X that does not have a modified boot image installed and CPU Z clocks both clusters at 1.44 ghz lol Download an app like Kernel Adiutor (free), ElementalX Kernel Manager (paid), Franco Kernel manager (paid) that will display both cluster stats.

I'm sure there's an ADB command to identify this as well. Idk if any do these commands will help, I'm on mobile away from a computer:

https://stackoverflow.com/questions/6630386/how-to-find-arm-processor-version-on-android-device

Edit: also, if you have installed a custom rom or flashed a factory image since you received the device, then you are not using this mod. The boot image gets wiped away when you install either over it.
[Nexus 6P General] Symber:
Thanks! I haven't had a chance to try yet, but very happy to have another thing to try. I'll be sure to post of it works out!
[Nexus 6P General] Eddie_Brock:
Hold down the 'volume down' button as it reboots, you should eventually end up in 'Download Mode', where you can then boot into TWRP, recovery, or flash files thru Fastboot.
[Nexus 6P General] aheeejd:
Omg, just found this while I was searching through my bookmarks for the possible lawsuit web page. Will be trying this soon. Wow
[Nexus 6P General] jassun16:
When I hold down the volume down button while rebooting, it ends up in 'Bootloader Mode' not the 'Download Mode' that you mentioned. From there I tried to boot into recovery and the phone again bootloops. I couldn't get into the recovey. Anyways thanks for suggesting me something.
[Nexus 6P General] NoobInToto:
Bootloader mode and download mode are the same.

You will see a screen with an Android and some options. That is your fastboot/download/bootloader mode.
[Nexus 6P General] sharpz811:
So let me get this straight you never had to use the modified twrp and boot? Just flashed stock then twrp then wipe efs partition?
[Nexus 6P General] boeder9:
I'm trying to do this for MTC20L (6.01), I unpacked the stock boot.img in Windows using QURepack and found a file called bootinfo.txt, it contains:

so the change I make is add: maxcpus=4

making it:

Is this correct? Is the file I'm editing the right one?

Please help
[Nexus 6P General] darkriff:
Has anybody tried using the modified IMG from P.A with the latest paranoid android version?
[Nexus 6P General] Sliver1979:
Hope someone might have an idea for a complete noob here. I've followed the steps in the original post using the original Oreo img file and also the 4 core TWRP. When rebooting the phone it says your data can't be checked for corruption and then gets stuck on the Google logo with no animations. But I can access TWRP ok. I then tried the modified Oreo4Cores-oldfstab.img file from C4ndy. This got me a little further on boot, past the animations to a screen asking for a password. Doesn't matter what password I enter, it says "decryption unsuccessful - the password you entered is correct but data is corrupt......factory reset required..." After resetting the phone it eventually goes back to TWRP. And round and round I go.

I'm at a complete loss of where to go from here. Any advice would be greatly appreciated! Thank you in advance
[Nexus 6P General] widermargins:
Sorry, I should have clarified. I used the modified 4-core TWRP here, but I had to flash stock boot.img as the modified 4-core one (Oreo4Cores) couldn't get my phone past the boot-up animation. The only way I could get past that was with the stock boot.img, so I've been sticking to that. As such, my phone is still running on 8 cores (according to CPU-Z at least), but hasn't had any problems since the EFS wipe (fingers crossed).
[Nexus 6P General] kennyloy:
For those who are locked device, can try to use this trick:-

Using water boiler to boil full of water, after water fully boiled, restart the device and put the device close to the boiler( middle of device, beside finger print scanner ), do this trick about 10 minutes. It will finish bootloop and go into os.

After enter, quickly open developer option and tick the oem unlock. The device will go into bootloop again around half an hour. Use Nexus Root toolkit to unlock oem, then flash recovery and flash boot image then done!!

Good Luck!!
[Nexus 6P General] javitomen:
Hello I have the Franco kernel on 8.0 I disable all the animations and my battery drain so quickly any recommendations?
[Nexus 6P General] ady437121:
yea

thats just spat on face and nothing more,.. no exchange or anything for the loyal users.
[Nexus 6P General] ART:
I tried a similar thing by using a hair dryer and pointing it in the middle of the device and it became hot. But didn't work. However, I then tried putting the phone in the freezer for an hour (battery was fully drained) , then charging it. It restarted properly after about ten minutes of bootloop.
[Nexus 6P General] SerpentEagle:
Have you tried using the Nexus root toolkit? Use it to return your phone to a factory state and then try it again.
[Nexus 6P General] nachman11:
Hello, this afternoon I appeared the boot of death, I have read several tutorials and guides. Root Toolkit and nothing... I have done what it says in this, I have flashed the Oreo and TWRP boot but on reboot, follow the Loop ... What can I do? > <
[Nexus 6P General] NoobInToto:
I believe the right way to do it is to flash a stock rom build, flash twrp, flash the corresponding boot.img ( there is one image for 2 Oreo builds, and different ones for different nougat builds), and then finally doing a factory reset in twrp.
[Nexus 6P General] nachman11:
I have done all that and nothing happened... I can´t boot in TWRP, continues the loop.

Thanks for answer. I´ll keep Trying
[Nexus 6P General] NoobInToto:
There is a modified twrp that uses 4 cores posted in the first post of this thread. Are you using that or the official one?
[Nexus 6P General] nachman11:
I think I've tried all ...

After installing the official rom I should put the modified recovery right?, and then the modified image?
[Nexus 6P General] NoobInToto:
Yeah. What official ROM build are you using and what boot image?
[Nexus 6P General] nachman11:
This one "8.0.0 (OPR6.170623.019, Sep 2017)" The official, with this modified image " Boot.img from stock 6.17, 8.0 firmware:"
[Nexus 6P General] NoobInToto:
Well, if those didn't work, then the phone is probably dead....sorry for that.
[Nexus 6P General] nachman11:
Thanks for that. Is the motherboard ?Do you know if is replaceable?
[Nexus 6P General] NoobInToto:
Yes, you are right. If you take it to an official service centre, they will ask you to replace the motherboard for a price that's more than half of the total price of the phone. ( For some, it's about half the price. However I am speaking only from my experience in India).

The exact problem is with the cpu, but the official guys would not tamper with the cpu. One guy got his n6p fixed from China by getting his cpu replaced.

If you have bought your phone from Google store, you are lucky. You might get your phone replaced for free even if out of warranty.

If you have not bought it from Google store, and the phone is out of warranty, then you are screwed.

However if the phone is still under warranty, rush it to Huawei service centre (if you have not bought it directly from Google store).
[Nexus 6P General] Symber:
I finally was able to try again. First I did all the fastboot commands to flash Oreo manually. Successful as far as I could tell just like the last time. Finished up with TWRP then the 4 core Oreo boot.img. Exactly the same as trying it with the 7.1.2 stuff (bootloop on Google screen, bootloader screen doesn't let me into recovery, just loops if I select anything, powering off and plugging it in restarts the phone and also bootloops, etc).

So, I heated the device up HOT, hotter than most here it seems, as it wasn't having any effect at ~130F. Around 150F I was able to adb the device and it finally booted into TWRP. Plugged the phone into my PC, entered the adb commands, but unfortunately no luck. They executed successfully, but no change overall after reboot, still looping (really appreciate something new to try though!)

After bootlooping I was again stuck on the dead android bootloader screen and couldn't get into TWRP (phone had cooled). Heated the phone again, keeping it between 150F and 190F. I was able to get back into TWRP but ran into the encryption issue. Cancelled, went into Advanced and tried to adb sideload. Successfully had the EX5 kernel launch and install (side note: I left everything at default, but it asked for big core clocking speed, I thought this should only enable 4 cores?). Rebooted and... Success! Kind of...

I was able to get past the bootlooping now, but I'm now currently stuck on the 4 colorful balls that keep spinning. Each of the 3 boots I have tried so far (10-30mins each) loads past the Google logo now and to those colored balls, seemingly forever. Also, when I power off the device it no longer turns itself on and bootloops. It stays of which is a huge help for charging. The device is also not visible for adb devices nor fastboot devices while at the colored ball screen (no idea if thats normal or not).

Just wanted to give an update for anyone else in a similar situation. Its not fixed yet, but Ill take anything different for now. Hopefully someone has a quick tip for getting past this next hurdle. Til then I'll see if maybe I'm just too impatient and let it try to boot for a few hours.
[Nexus 6P General] widermargins:
I think this is progress, actually! I ran into the same issue after wiping the EFS--stuck at the colored balls.

My problem was solved by doing this: reboot into bootloader, then using fastboot, erase the modified 4-core boot.img and re-flash the factory boot.img (which fires up all 8 cores). Counter-intuitive, I know, since the solution here is precisely based on the phone running on 4-cores. But every time I tried to flash the 4-core boot.img, I got stuck at the colored balls. The only thing that got me into a normal boot was the factory version of boot.img.

Since that time, my phone has been rebooting without any problems. Hope this is the same for you!
[Nexus 6P General] Alsen Lea:
Did u flash the 4cores kernel as well after flashing the boot.img?
[Nexus 6P General] Symber:
Bingo! Back in action! Thanks for that last step. Not sure how much tinkering I'd have to do before I tried that one. Chalk up another one for the good guys!
[Nexus 6P General] athuljays:
Is wiping the EFS partition safe?

Should do a backup of the folder before right?
[Nexus 6P General] Vince0202:
If anyone can help me I have a quick nooby question. I've followed instructions on another website and got my phone to work again but was wondering if I could still update to android 8.0 after doing this. I believe I used the boot.img from 48B if that matters at all.
[Nexus 6P General] Symber:
I don't find any of this particularly safe as it's really not common practice outside of normal flashing routines. That said, it's always smart to back things up and I was personally more concerned about heating a sensitive electronic device up to nearly the boiling point of water.
[Nexus 6P General] LuciferDurden:
Respect

Thanks man, it saved my phone. I did all the things to try and improve the performance too, but is there a way to actually use all the cores or something to improve the performance even more, coz the phone has slowed down drastically?
[Nexus 6P General] maximusmullivan:
Wut
[Nexus 6P General] arafsheikh:
Hey, I have a Xiaomi Mi4i with Snapdragon 615 which is a 64-bit octacore SoC made with the 20nm process. I believe it is suffering from a similar issue (bootloop every 4-5 secs). However this didn't fix it for me.

My question is does the above method ensure that the big cluster is the one that is disabled for every device? Is there any other method that I can use to disable the 4 big CPUs?
[Nexus 6P General] gaganchohan:
Didn't worked

I installed android 7.1.2 (July image) and then installed the given file by you , it is still in bootloop
[Nexus 6P General] MrMarques01:
You, Sir, are a savior and a scholar. This fixed my 6p which started to bootloop around 2 months ago! Thank you very much.

The question is, would it be possible to manually re-enable some of the big cores after booting into the OS? This way one could identify which core causes the bootloop. Plus it could be possible to run the big cluster with 3 cores enabled. I tried enabling them using EX Kernel manager, but they remain turned off
[Nexus 6P General] mnhs1010:
i have this build n2g48b 7.1.2

factory image
[Nexus 6P General] krisyarno:
Very interested to see how this works for you. I was lucky enough to have the the battery issue to the extreme (it would die under 75% if i used certain apps. I got like 20-30 minutes of battery life) and now have the bootloop.
[Nexus 6P General] RyomaEchizen:
Yes

Just read this. Works for me

Enviado desde mi ONEPLUS A3000 mediante Tapatalk
[Nexus 6P General] kaustubhb:
on stock it goes down at 40% where as on purenexus it goes down at 20/15% even though I switched to battery saver at 25%..very excited to see how this mod works .. if it works then great .. I love n6p but just because of battery issue it forced me to opt op5

---------- Post added at 08:26 AM ---------- Previous post was at 08:22 AM ----------

Try decrypting your data partition .. by using command fastboot format userdata .. make sure you backup your imp data before formatting user data ..
[Nexus 6P General] vip57:
Really appreciated !!

When you want PM me

I have lg v10 H960A version which has bootloader unlocked and can be rooted
[Nexus 6P General] Aswin08:
Describe elaborately if you want help, are you sure you did all the steps?

You didnt even mention whether you can boot to the new twrp ..
[Nexus 6P General] kaustubhb:
Can anybody post short screen record video showing their 6p running on 4 core ??( that is this mod ) ..
[Nexus 6P General] NeoS:
A friendly warning people: try to keep this topic clean and uncluttered. Posts like: "Me too" and My Samsung has it too" don't really help, so don't post that.

Thank you.
[Nexus 6P General] DGT79:
From what I can tell the following takes place:

* By heating the phone up to fairly hot temps you are forcing it to use the little cores during boot, this is what allows it to work or boot back up

* By letting the battery drain and getting it below 10% it also disabled the big cores and boots up with the little cores, but you have a much smaller window to make changes if your battery is cactus

* The battery is a big issue for this as well, so if you really want it to work right you have to replace the battery as well as that messes with the governor as well

I have brought to life 3 other nexuses by replacing the battery with a generic one (Note the Huawei OEM one) but not all of them come back to life, so the problems that this phone faces can be more than one item, and by disabling the big cores we are just masking the real problem, both Huawei and Google wont comment on it, the best I got have Huawei was that the motherboard needs to be replaced.

If this method works for you, then it might be an alternative phone or even one for your kids, that way it is not entirely a paper weight.

Cheers,

David.
[Nexus 6P General] mivec1756:
increase performance

what can i do to speed up performance a bit? i'm getting alot of lag just using facebook, youtube etc. i overclocked to 1632Mhz and selected performance in ex manager. anything else i can do for a little extra speed? thanks
[Nexus 6P General] sylforae:
It's worked the first time, but because I'm idiot I tried to flash with the official image and now, after the second install of EX with your boot.img my phone stuck on the google logo...
[Nexus 6P General] burduli:
My phone is VERY hot right now but it's still bootlooping to the Google logo.
[Nexus 6P General] mercado79:
Poll?

Would love to see a poll added. Think it'd be useful.

This fix didn't work for me. I flashed the latest 7.1.2 image, then the modified boot image. No go. Tried the modified recovery image. Still bootloops. I'd gotten my hopes up! Still great work on the OPs front. I'm sure plenty of people appreciate it.
[Nexus 6P General] Ashutosh Sundresh:
My Sony heats up to 70°C and never succeeds, just burns my hands. Not that it is related to this in anyway but yeah
[Nexus 6P General] sohilj23:
I know it's not the place to ask but G3 had same bootloop problem which is mostly related to the hardware, Is there any way for you to try same kind of methods for G3 ?
[Nexus 6P General] XCnathan32:
I was looking at some logs last night, and I saw the error "Kernel Panic - not syncing: fatal exception" a quick Google search showed that Linux users had that problem after updating to a new version of something, earlier in the log, I also saw "kernel BUG at driver/(path)" my guess is that the developer preview just has some bugs that need to be ironed out, I'll try modifying a previous Developer Preview, as the bug could have been introduced in a newer preview, if that doesn't work, I think we'll have to wait for the official release.
[Nexus 6P General] NoobInToto:
Can anyone give me the original boot.img for september build? I wanna get ready to update to the upcoming October security patch.

---------- Post added at 05:19 AM ---------- Previous post was at 04:57 AM ----------

Not only can you update, you can do so without factory or ota images. You can update via the inbuilt ota system. Search this thread for my post on 'updating without losing data' .

Edit: speak of the devil, the update is here!
[Nexus 6P General] dolphin77:
boot.img for October update

Following instructions from the OP and using git source code, I modified boot.img for the October Oreo update. Here it is. https://drive.google.com/open?id=0Bz-QKvufSA2-MDZtOFkteS1YNjg

and step by step, what I did:

abootimg -x ../boot.img
vi bootimg.cfg
-androidboot.hardware=angler androidboot.console=ttyHSL0 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 boot_cpus=0-3 no_console_suspend loop.max_part=7 buildvariant=user
+androidboot.hardware=angler androidboot.console=ttyHSL0 msm_rtb.filter=0x37 ehci-hcd.park=3 lpm_levels.sleep_disabled=1 boot_cpus=0-3 maxcpus=4 no_console_suspend loop.max_part=7 buildvariant=user
mkdir initrd
cd initrd
cat ../initrd.img | gunzip | cpio -vid
vi fstab.angler
-/dev/block/platform/soc.0/f9824900.sdhci/by-name/system /system ext4 ro,barrier=1,inode_readahead_blks=8 wait,verify=/dev/block/platform/soc.0/f9824900.sdhci/by-name/metadata
-/dev/block/platform/soc.0/f9824900.sdhci/by-name/vendor /vendor ext4 ro,barrier=1,inode_readahead_blks=8 wait,verify=/dev/block/platform/soc.0/f9824900.sdhci/by-name/metadata
-/dev/block/platform/soc.0/f9824900.sdhci/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic,inode_readahead_blks=8 wait,check,forcefdeorfbe=/dev/block/platform/soc.0/f9824900.sdhci/by-name/metadata
+/dev/block/platform/soc.0/f9824900.sdhci/by-name/system /system ext4 ro,barrier=1,inode_readahead_blks=8 wait
+/dev/block/platform/soc.0/f9824900.sdhci/by-name/vendor /vendor ext4 ro,barrier=1,inode_readahead_blks=8 wait
+/dev/block/platform/soc.0/f9824900.sdhci/by-name/userdata /data ext4 noatime,nosuid,nodev,barrier=1,data=ordered,nomblk_io_submit,noauto_da_alloc,errors=panic,inode_readahead_blks=8 wait,check
vi init.angler.rc
- write /dev/cpuset/foreground/cpus 0-2,4-7
- write /dev/cpuset/foreground/boost/cpus 4-7
- write /dev/cpuset/background/cpus 0
- write /dev/cpuset/system-background/cpus 0-2
- write /dev/cpuset/top-app/cpus 0-7
+ 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
find . |cpio --create --format='newc' | gzip > ../modinitrd.img
abootimg --create modboot.img -f bootimg.cfg -k zImage -r modinitrd.img

All the credits goes to Mr XCnathan32.