yashsingh1/xdaforums huggingface dataset:
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Follow the guide in the second post of this thread. There are two adb commands to run. After that, you may need to install factory images again.
[Nexus 6P Q&A, Help & Troubleshooting] ranbd0:
Hi !

To enter the recovey mode I should first install TWRP HOWEVER I dont have Rooted 6p.

How I can intall TWRP and run those commands ?

Thank you very much for your help !
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Please use the search function. There are several guides to get you safely where you need to be.
[Nexus 6P Q&A, Help & Troubleshooting] ranbd0:
Sorry I just don't get it. what should I do from here ? wich search function ? :confused:
[Nexus 6P Q&A, Help & Troubleshooting] :
Google search. Example: How to root Nexus 6p xda (enter)

I always slap XDA on the end of whatever I'm searching for so I know it will show me results first for what's here which is always the best. ;)

If you use a computer with Windows here is a 15 second adb and fastboot installer. VERY useful!! https://xdaforums.com/showthread.php?t=2588979

Unlock bootloader first (which wipes your entire phone)

Install TWRP 3.0.3-0 via fastboot

Make a backup of system, data, boot in TWRP recovery

Flash whatever you want (after reading alot so you know what your doing...) and if something gets messed up restore your backup. :)

You can also use a toolkit but I always like to know exactly how to operate on these and toolkits remind me too much of what I used to use, Samsung phones. Yuck. Lol. Good luck to you. Just search h and read up. Everything is here on XDA and that is the rules here. Cheers.

Edit
[Nexus 6P Q&A, Help & Troubleshooting] mfractal:
So was there ANYONE who successfully restored from this boot loop on bone Stock phone? I skimmed through the thread but haven't found the answer.
[Nexus 6P Q&A, Help & Troubleshooting] darkriff:
I just tried with Android O and it is not bootlooping, just stays i the splash screen.
[Nexus 6P Q&A, Help & Troubleshooting] mikeygeer:
How did you get an RMA if you were rooted with an unlocked bootloader? I
[Nexus 6P Q&A, Help & Troubleshooting] CyberpodS2:
Because with a real BLOD, the root is no longer accessible. As far as the unlocked boot loader goes, it's a stock capability. My RMA went without a hitch.
[Nexus 6P Q&A, Help & Troubleshooting] mikeygeer:
Could you send me an email at mikeygeer@gmail.com about how you approached the conversation. I'm about to call to hopefully get mine replaced
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
Hello... This is no rocket science...

Call Google or Huawei. Explain your problem and how it surfaced. Since you only have bootloader access, there's​ not much they can ask you to do to troubleshoot the issue. They clearly know about it, don't worry... :good:

Let us know ow how it goes!

Good luck...
[Nexus 6P Q&A, Help & Troubleshooting] Ben_Hurley:
Ok I am not alone on this issue.

Phone specs: Nexus 6p bought in US 32gb h1511, never rooted. No modifications software and hardware.

Issue: Sudden shutdown while charging, and can't be turned on anymore.

Workarounds: Power + any volume combination - nothing happened. Flashing wih QFIL only getting errors such as, sahara unable to read packet header or sometimes device not in firehose mode. Charge overnight nothing happened. Let it sit for a week without charging and charge it back still nothing happened on the screen. Nothing means zero!

Last Workaround: Send the phone for RMA but phone was sent back by DHL because it is already forbidden to send now via courier gadgets with batteries. I am sending it from Germany btw to USA . Now hopeless because warranty will expire in May 2017.

Phone status: When connected to Laptop device manager shows Qualcomm QDLoader 9008

Flashfiles used: Tenfars nexus6p brick file using different versions of QFIL.

Sitting here, waiting for miracle to happen.
[Nexus 6P Q&A, Help & Troubleshooting] csjneek:
Did you try keeping power button pressed for more than 90 seconds or so?

Trimis de pe al meu Nexus 6P folosind Tapatalk
[Nexus 6P Q&A, Help & Troubleshooting] Ben_Hurley:
Yes I did, i even put a rubber band to it lol
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
Hello... You're stock in EDL. Unfortunately not the proper one that should let you flash with qfil. It won't fix itself or with the power button. You have to figure how to get in the proper state and reflash your device with qfil...

Good luck...
[Nexus 6P Q&A, Help & Troubleshooting] Ben_Hurley:
Yeah that is what I suspect already. in EDL mode but not the right one. No clue how to make it right :(
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
Hello... I found a post that could likely help you. I'm not saying it will work. Just try and see:

https://xdaforums.com/showpost.php?p=70946864&postcount=6

I see you have posted in this thread. Just not sure if you have already read this post...

Good luck :good:
[Nexus 6P Q&A, Help & Troubleshooting] Ben_Hurley:
Hey Thanks but I did that already. What tenfar said is actually what is going on in my phone, getting packet error since my phone is not in correct EDL mode. Meaning I am in QLoader 9008 but not the right one that is why the flash failed all the time.
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
He advised another trick here:

https://xdaforums.com/showpost.php?p=71053962&postcount=33

tried that as well..?

If this one doesn't work either. I have no other idea, sorry... :(

Good luck...
[Nexus 6P Q&A, Help & Troubleshooting] Ben_Hurley:
Thank you but I did that Already. Phone at QPST is already at Download Status. That is what I don't understand. I will try to download a new flash file, maybe the ones I have is corrupted. Appreciate the help man.
[Nexus 6P Q&A, Help & Troubleshooting] Ben_Hurley:
so i decided to uninstall all drivers again hoping it would resolved the issue. And when i plugged in the USB the Nexus appeared as USB descriptor failed in the device manager, and then I long pressed the power button long enough to hear the beep sound and it shows again as QDLoader 9008. Is it an expected behaviour that the 6p installs itself? Even if it is dead already? Anyway i proceeded to flash it again using QFIL but still getting same result. PLease see logs. Thanks!

Process Index:0

Programmer Path:C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked\prog_emmc_firehose.mbn

Image Search Path:C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked

Please select the XML file

Start Download

Program Path:C:\Program Files (x86)\Qualcomm\QPST\bin\nexus6p_fix_bricked\prog_emmc_firehose.mbn

COM Port number:3

Sahara Connecting ...

Sahara Version:2

Start Sending Programmer

Sending Programmer Finished

Switch To FireHose

Max Payload Size to Target:49152 Bytes

Device Type:eMMC

Platform:8x26

Disable Ack Raw Data Every N Packets

Ack Raw Data:False

Skip Write:False

Always Validate:False

Use Verbose:False

COM Port number:3

Sending NOP

NOP: Fail Code: 10

Unable to send FireHose NOP, Device is not in Firehose mode !

Download Fail:System.Exception: Failed to send Firehose NOP to the phone.

at QC.QMSLPhone.Phone.QPHONEMS_FireHoseNOP()

at QC.SwDownloadDLL.SwDownload.FireHoseDownloadImage(Boolean bResetPhone, List`1 rawprogramFilesList, List`1 patchFilesList, Single& fImageSizeInMB, Single& fThroughput)

Download Fail:FireHose Fail FireHose Fail

Finish Download
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
Hello... What qpst version did you install?

Google for 2.7.453 and retry...

Also, those who successfully resurrected their device, used firmware + driver from the OP here: https://xdaforums.com/nexus-6p/general/howtos-debrick-nexus-6p-stuck-edl-9008-t3552838

The log is clear:

Unable to send FireHose NOP, Device is not in Firehose mode !

Unfortunately, I don't know what to do. :(

Good luck...
[Nexus 6P Q&A, Help & Troubleshooting] Ben_Hurley:
It is ok Man, could have been way much easier if DHL allowed phones to be shipped in US. I already have RMA and ticket number and every hope i have exploded when it was returned back to me by the courier. I will just be on standby here waiting for workarounds and if I can solve it i will share it to you guys. Ciao!
[Nexus 6P Q&A, Help & Troubleshooting] kaoskilo:
My device is

Bootloader - 3.64

Baseband - 3.79

Variant - VN1

CPU - 0x20001

eMMC: 32GB Samsung

DRAM: 3072 HYNIX LPDDR4

Console - NULL

Qfuse status - Enabled

Download Mode - Disabled

Manufacture data - 11-15-2015

Methods tried - 1-4, 10 - Removed in factory image flash and relocked flashing in desperation (don't do this!) and now cannot unlock due to developer switch not being flipped in settings...
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
Isn't there an option to select the proper port in qfil? In your previous log, the phone was connected to COM 3, but in this one it seems to try reaching COM 4...

Good luck...
[Nexus 6P Q&A, Help & Troubleshooting] Ben_Hurley:
I just tried other USB slot that's why it was COM4. One thing for sure is, if I am uninstalling all qualcomm drivers I am getting this one. I am using the latest QPST btw.
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
If I remember well, [MENTION=540283]tenfar[/MENTION] advised using his driver to get qfil working...

Again, I have no clue... :(

Good luck...
[Nexus 6P Q&A, Help & Troubleshooting] darkriff:
Have you guys read this?

http://www.androidpolice.com/2017/0...-beta-testers-final-7-1-2-build-ota-download/
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
This has nothing to do with what's discussed in this thread. Read the whole article from the link you provided...

Some people who updated to final 7.1.2 kept receiving 7.1.2 beta OTA notification... :)

The article only says this has been fixed now!

Cheers...
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
Hello... Someone suggested holding volume up and plugging USB cord in the computer and launch qfil flash still holding volume up until the flash ends...

You may try this :good:

Good luck...
[Nexus 6P Q&A, Help & Troubleshooting] vladniko:
Bootloader - angler-3.64

Baseband - angler-3.79

Variant - ANGLER-VN2

CPU - MSM8994 0x20001

EMMC - 64GB Samsung

DRAM - 3072MB SAMSUNG LPDDR4

Console - NULL

Qfuse status - Enabled

Download Mode - Disabled

Manufacture date - 01-18-2016

Brief description of where the bootlooping started - I got it from a friend who gave up on it.

I have tried methods - 1-3 & 9. It will not boot into TWRP, it just keeps bootlooping after a factory reset and twrp flash. However it does boot into stock recovery, but all i see is the NO COMMAND message

Edit: I've gone into stock recovery to try to flash something from the sd card, but it spits out

E:unknown volume for path [/sdcard]

Couldn't mount /scdcard

Installation aborted
[Nexus 6P Q&A, Help & Troubleshooting] Ben_Hurley:
I will try this, Thanks Man and Happy easter!
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
Hello... Since your bootloader is unlocked, flash TWRP... Boot directly I to TWRP and install SuperSU: https://download.chainfire.eu/1021/SuperSU/SR3-SuperSU-v2.79-SR3-20170114223742.zip

Otherwise TWRP will vanish after a reboot.

Try to install a custom ROM...

Also, did you try to flash stock firmware with flash-all script?

Latest 7.1.2 is said to have an issue since it doesn't contain cache.img...

So, download 7.1.2, reboot into bootloader and flash:

Bootloader

Reboot bootloader

Radio

Reboot bootloader

System

Vendor

Userdata

From here, you can either fastboot flash TWRP.img or just fastboot boot TWRP.img

Reboot into TWRP and wipe cache, dalvik/art cache.

Reboot

If you want to have TWRP, don't forget to install SuperSU after you flash the TWRP.img

Let me know if it works..!

Good luck...

Thanks dude, you too :good:
[Nexus 6P Q&A, Help & Troubleshooting] vladniko:
It seems to be booting up to the logo, but just crashes and trys to boot again
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
You.follwed the steps mentioned in my previous post? Flashed TWRP or just booted into it? Did you wipe cache and art/dalvik in advanced wipe?

You installed SuperSU from TWRP? In this case,, the behavior is normal. It will reboot a few times.

Otherwise, I'm not sure what more you can do...

Good luck...
[Nexus 6P Q&A, Help & Troubleshooting] tokenbest:
Guys.. can't believe i just got the bootloop of death as well. I am trying very hard just to get into recovery.. When i go into recovery, usually it will prompt me for password but now i just enter recovery. Any help here or steps that i can follow?
[Nexus 6P Q&A, Help & Troubleshooting] vladniko:
Yea I did your steps, also tried a custom ROM. Both time flashed TWRP, then wiped cache and dalvik, then reboot. Not working still
[Nexus 6P Q&A, Help & Troubleshooting] 5.1:
Hello... What ROM are you using currently? What mods? How did it start bootlooping? Did you install something and started to bootloop?

Give as much infos as you can, otherwise we can't help you much. Also if you have recovery access you don't have bootloop of death. There is also a scenario of some users having recovery access but unrecoverable. Especially after a failed OTA...

Hello...

Boot into bootloader and issue:

fastboot erase cache

fastboot format userdata

Reboot

I don't know what else to say... :(

Good luck...
[Nexus 6P Q&A, Help & Troubleshooting] amcferrin90:
Someone asked about the OP Nexus6p_fix_bricked.zip file. I have it. Trying to upload it to my Google Drive. Internet at work is going dead again and limiting me ATM. Once done I can post a link. Don't know how many downloads they'll let happen.
[Nexus 6P Q&A, Help & Troubleshooting] orisha1905:
Pleaseee!! I need this ROM...

---------- Post added at 09:09 PM ---------- Previous post was at 09:07 PM ----------

Pleaseee!! I need this rom
[Nexus 6P Q&A, Help & Troubleshooting] arielaco:
Could you please upload Nexus6p_fix_bricked.zip? I can't find it on the net. Thank you
[Nexus 6P Q&A, Help & Troubleshooting] amcferrin90:
https://drive.google.com/open?id=1S_HWDVGDyG5MdNHtkhnUauH3BehTF0qr

Don't know how many downloads Google will allow. So get at it.
[Nexus 6P Q&A, Help & Troubleshooting] orisha1905:
very thanks sir, its my last hope for unbrick my nexus 6p
[Nexus 6P Q&A, Help & Troubleshooting] orisha1905:
After several tests I have managed to flash the Nexus, but it is still in the same state, indicating that it is in edl mode, I think I'm going to give up ..
[Nexus 6P Q&A, Help & Troubleshooting] hjmrox:
I too face the same. I manage to flash through QFIL successfully few times.

2018-08-13 21:40:09.720 21:40:09: INFO: {All Finished Successfully}

2018-08-13 21:40:09.720 21:40:09: INFO: FILE ACCESS SLOW!! 0.00 B in 0.015 seconds ( 0.00 Bps) --- Overall to target 0.094 seconds (0.00 Bps)

.

.

2018-08-13 21:40:09.727 Waiting for reset done...

2018-08-13 21:40:10.821 Download Succeed

2018-08-13 21:40:10.821 Finish Download

The reset is done after QFIL completes. The phone disconnects but connects back as QDloader still :(

The sad part is, I had intermittent access to bootloader, but after all these steps to try fix the phone, I cannot boot the phone to bootloader at all
[Nexus 6P Q&A, Help & Troubleshooting] orisha1905:
I have the same problem...

Enviado desde mi ONEPLUS A3003 mediante Tapatalk
[Nexus 6P Q&A, Help & Troubleshooting] skullzhunter:
After reading around a bit, here's my theory:

The bootloop is caused by the "big" cluster - the 4 Cortex-A57 cores. I have no idea exactly how it's causing it, but considering that by disabling them, you can recover the phone, I'm pretty sure that's the problem.

Now, how do we fix it? As far as I know, the only fix is to simply disable them, but that seems like a big compromise to me.

I recently bought a 6P, manufactured in Nov 2015, and it's still going strong (especially after replacing the battery). It's pretty weird to me that this device is not bricked yet, after almost 3 years and plenty of updates and security patches (it's running 8.1 and latest security patch). So after a little bit of research, I discovered that the A57 cores in my phone were running at 1.56 GHz, instead of 2.0 GHz. I hope you understand what I'm talking about now. The only reason my phone is not bricked yet, after so much heavy usage, is that the big cluster is undercloked, therefore, this is the solution. Regarding the implementation of this, I have no idea, but maybe instead of disabling the cores, you could just underclock them (IF they're still functional).

I have no idea how or why they're underclocked in my phone. I bought the phone unrooted, running stock everything, so I'm pretty sure no one messed with it. Maybe it was some kind of over-the-air thing, being "adjusted" silently by an update.
[Nexus 6P Q&A, Help & Troubleshooting] mode_ss:
Hi there! wold you be so kind to share it again? I'm looking for this file a lot! without luck. Please! you could directly share it with me to mode.ss at gmail, in case you dont want to post it publicly. please!
[Nexus 6P Q&A, Help & Troubleshooting] amcferrin90:
Yeah. Give me until this evening. I have to upload it again.
[Nexus 6P Q&A, Help & Troubleshooting] amcferrin90:
Here you go: https://drive.google.com/open?id=1Vf883MXGSYIFY-C6f1j8AC6AU-QI_rSH

I'll leave that up a couple months. Just a FYI, I just updated and wiped my 6P to prep for sale before you sent this. The case has some dings, no scratches on the front glass, a few scuffs on the back glass but doesn't affect pictures. It does need the battery replaced, it has the original battery. I haven't decided if I was gonna put it on Swappa or Ebay. Older phones on Swappa don't seem to sell.
[Nexus 6P Q&A, Help & Troubleshooting] mode_ss:
Thanks!!

Thanks a lot! a big Kudos for your kindness on sharing this. Lets see now if it works for this dead ol' Nexus 6p I have. Wish me luck!! I'll post here if it worked.
[Nexus 6P Q&A, Help & Troubleshooting] ciocu:
I sideloaded the Nougat OTA couple of days before the bootloop.. in the STOCK recovery, using ADB sideload
[Nexus 6P Q&A, Help & Troubleshooting] mbutandola01:
Then why not flash the nougat vendor?

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P Q&A, Help & Troubleshooting] BakedTator:
I have my new Nexus 6p and have sideloaded the OTA onto it with the newest twrp and have it rooted and such...not doing anything else with it until a factory image is released. Going to see what happens with it

---------- Post added at 08:08 PM ---------- Previous post was at 08:07 PM ----------

Because then you bootloop
[Nexus 6P Q&A, Help & Troubleshooting] busbeepbeep:
Friday: OTA notification. Downloaded it, then it prompted to install. I hit install, then came back to my phone after like 30 minutes. It was prompting for my security pattern. I entered it, but it booted back in 6.0.1, then displayed a message that OTA Update had failed, please try again. The OTA then prompted to download again. Didn't feel like spending the time downloading 1+ GB again, so I figured I'd try later.

Sunday: Browsing chrome. Freezes. After 10 seconds or so, reboots itself. Bootloop. Shows white google logo for 10 seconds, then 2 seconds of black, then back to google logo.

I think whatever happened during that attempted OTA update killed my phone.
[Nexus 6P Q&A, Help & Troubleshooting] ciocu:
i'm not taking sides, but I think it may be easier to say that the OTA has something wrong in it?!? rather than TWRP..

or OTA & chrome ?!? as it was the same chrome freezing for me as well :cyclops::cyclops::cyclops::cyclops::cyclops:
[Nexus 6P Q&A, Help & Troubleshooting] BakedTator:
Could this have something to do with direct boot? Or whatever it's called that nougat does with OTAs and the system partition
[Nexus 6P Q&A, Help & Troubleshooting] busbeepbeep:
Not sure, but I'll just add that the Google rep who I was on the phone with put my on hold for a few minutes, and came back and told me he spoke with a supervisor and they've gotten several support requests like mine the past few days.
[Nexus 6P Q&A, Help & Troubleshooting] mbutandola01:
Before or after flashing system? Did you do a full wipe first?

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P Q&A, Help & Troubleshooting] BakedTator:
Both before and after and yes I wiped everything on the device...trust me, it's not my first time flashing ;)
[Nexus 6P Q&A, Help & Troubleshooting] mbutandola01:
I don't think it's the first time. But we all make mistakes. Especially if we're so used to doing something. Experienced drivers have accidents too ☺️

Got a question, what partition is twrp most likely to mess up with? Maybe flashing that part first before anything could make the difference. But you might have done that already.

Envoyé de mon Nexus 6P en utilisant Tapatalk
[Nexus 6P Q&A, Help & Troubleshooting] BakedTator:
First off, I was joking with you.

Second, I flashed everything in different orders.

I have tried everything a user can try man
[Nexus 6P Q&A, Help & Troubleshooting] Jammol:
Because the Vendor image needs to correspond with the version software being installed. Problem is, restoring Vendor causes bootloops. Not sure if that's still the case though.
[Nexus 6P Q&A, Help & Troubleshooting] Eric214:
Right I know that, but if I flashed stock images from pure Nexus, then took the OTA through the system update option (enrolled in the beta program) then for a week ran stock Nougat rooted with TWRP 3.0.2-1 and supersu 2.76 flawlessly. I backed up the stock Nougat with TWRP wiped phone with FDR and restored the stock Nougat backup......

Why would I need to flash the vendor if I'm on the same version of Android the backup is of??? I never even tried to go back to MM until the bootloop after restoring the backup of Nougat when I was on Nougat?

The only thing that saved me was not the vendor image but the original EFS backup from when I bought the phone in Feb
[Nexus 6P Q&A, Help & Troubleshooting] tr4nqui1i7y:
Can everyone answer the first post, please.
[Nexus 6P Q&A, Help & Troubleshooting] chevycam94:
Ive had the stupid bootloop issue when downgrading from Nougat. Been trying EVERYTHING I can think of. Here is what I have basically figured out so far.

* After the bootloop, installing ANY Nougat ROM (bootloader, radio, and vendor included), will continue to bootloop. However, installing ANY previous 6.0.x VENDOR image allows the system to boot up (with Nougat base).

* Restoring 6.0.x OR 7.0.x EFS partition doesnt seem to do anything, regardless of vendor/base versions.

* Recovery version doesnt seem to matter, except when installing a Nougat-based ROM.

* Nougat base/vendor with a custom Nougat KERNEL doesnt fix the bootloop, it STILL requires a 6.0.x vendor (any).

* Flashing the MTC20F factory image then taking the unofficial Nougat OTA (via sideload) STILL results in a bootloop.

I have my replacement 6P arriving tomorrow after work. Im just throwing everything I can think of at this phone, and it still wont give in.

I DID notice something though. After the MTC20F factory flash, then Nougat OTA, upon FIRST boot, the Google logo started to morph into the bootanimation. it froze before all the letters disappeared, then proceeded into the bootloop. However, EVERY time after that (unless I do the flash cycle again), it shows the Google logo, but never gets to any part of the animation before rebooting again. Im guessing here, but if it made it through to where it could animate the bootanimation, would that now be a kernel problem? Something between the kernel and the vendor?

One theory, is to try to make a "hybrid" vendor image that blends MTC20F and drivers from Nougat, so that things like the camera and rotation work again. At least it would be a temp fix.