yashsingh1/xdaforums huggingface dataset:
[Nexus 6P General] apples1678:
I was able to get a few (3) successful downloads among many, many attempts by holding down the power button while the phone is connected via usb until you hear the windows 'device connected' sound and the device manager refreshes, and then immediately pressing download as soon as QFIL recognizes the port. I've also swapped drivers on the QDLoader 9008 device (update driver > have disk > pick one of the files in the qualcomm folder from the installed bundled with tenfar's files.) Try swapping USB cables and ports as well. I've noticed that if you receive the 'Download Fail: Sahara Fail:QSaharaSaharaServer Fail: Process fail' message, you need to 'restart' - as in, hold power, or unplug the phone and plug it back in, or update the driver. Once you receive that message it will not work on any subsequent attempts until you 'refresh' the port.

My device is now occasionally reverting to a normal bootloop instead of the EDL mode where the device doesn't respond to anything except the QFIL tool. I was able to boot into recovery, flash TWRP, and attempt the 'core downgrade' method. I flashed a few of those modified images, the EX kernel, and actually booted into android twice! I signed in both times and actually started downloading apps/receiving text messages, but then the phone froze and returned to the EDL state. I have not been able to get it to boot back into recovery (I want to try to flash different images from the other fix thread) for 48 hours now, leaving it plugged in the entire time, attempting every 12 hours or so.

It seems like, for me anyway, when the device is in this state it needs to stay plugged in and untouched for about 24 hours, and then you might get one or two attempts at booting into recovery to try adb/fastboot/twrp commands. If you can get QFIL to flash files one time, you should be able to get back into a regular bootloop state, at which point you can flash the modified factory images to use less cores. I don't think your device is a lost cause yet - keep trying different combos of USB drivers, cables, ports, plug/unplug the device, hold power while plugged in.

If you did not enable developer mode/unlock bootloader before your phone bricked itself, you are kind of screwed unless you can get very lucky and boot into android once, unlock it, then let it crash again.
[Nexus 6P General] apples1678:
A bit of progress/interesting discovery I made (I've received my new phone - but I'm determined to bring this one back to life, even though I'm wildly inexperienced in this arena) - I think the MiFlash utility does not function because the phone is not in 'sahara mode' (or 'sahara protocol'), which is enabled by executing this command (QFIL calls this internally):

"C:\Program Files (x86)\Qualcomm\QPST\bin\QSaharaServer.exe" -p \\.\COM5 -s 13:prog_emmc_firehose.mbn

(Replace COM5 with whatever port shows in device manager)

you need to execute this from cmd prompt or powershell (in powershell prepend with an & character) while in the directory of the recovery images, notably the 'prog_emmc_firehose.mbn'

If you get this to succeed, you'll see this message:

NOTE: Target requested image 13 which is DeviceProgrammer. Forcing QUIT. This is by design, ** All is well ** SUCCESS!!

If it fails with another message, hold down power for ~10-20 seconds while plugged in until the port refreshes in device manager, then quickly try again.

Once you get into 'sahara mode' (this might be totally incorrect terminology), you can either execute this, which is what QFIL runs next:

"C:\Program Files (x86)\Qualcomm\QPST\bin\fh_loader.exe" --port=\\.\COM5 --sendxml=rawprogram0.xml --search_path="D:\Android\Nexus 6p Repair\nexus6p_fix_bricked" --noprompt --showpercentagecomplete --verbose --zlpawarehost=1 --memoryname=emmc

(same rules as the last command apply)

OR, you can refresh in the MiFlash utility, and attempt to flash through there. I believe these two commands fail in the same manner when they fail, and I believe I will get a MiFlash success here soon if I keep trying:

MiFlash Fail: 'error: The write timed out.'

QFIL (fh_loader) Fail: '{ERROR: It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}'

I think these are both failures for the same reason. After encountering this failure, you must start over by refreshing the phone (hold power) and then re-running the sahara command before attempting MiFlash or the FHLoader command.
[Nexus 6P General] abhishekmaity:
First of all, thanks a bunch! I followed your instruction in cmd prompt and finally was able to see some progress! Unfortunately it didn't end well, and file transfer was done till 69.77%, at which point the command prompt was stuck for a long time and finally threw out this message:

{ERROR: Could not write to '\\.\COM3', Windows API WriteFile failed! Your device is probably *not* on this port, attempted 100 times}

Any idea what could result in device not being detected in COM3 after all these time? I tried holding down power button till I hear the device disconnected sound, followed by device connected sound, and ran the commands again, this time there was no progress and I got this message:

{ERROR: It took 10.00000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable}

PS: I never touched the bootloader, but developer mode was enabled in my phone as I use it to develop and test android apps.

PPS: Probably a silly thought, but do you think my phone ran out of charge at 69.77% of the process?
[Nexus 6P General] apples1678:
I'm not sure about the failure mid-way through. In the 4 times I've had a download succeed (3 times with QFIL, 1 time using the commands directly), if it started at all (i.e. showed progresss rather than the 'it took 10.000000 etc'), then it would go all the way to 100%. I haven't been able to get my phone to boot into recovery since the last successful download.

I have seen the Windows API fail message when using the commands directly, but I never saw that message in QFIL. It happened to me before the download even began, though. I would imagine while the phone is plugged in via USB there is some power going to the device - otherwise how would windows recognize it? I'm really not sure, though. After my phone was dead for 2 weeks, the first time I booted into TWRP It showed battery at 66%+, so I think it does charge while plugged in even if there is no indication. At one point I left the phone frozen on the google logo until it shut off on its own - so I assume I completely drained the battery at that point and then it charged again.

Good luck on your device - let us know if you figure anything out. I'm still trying to get it to boot back into recovery every 1-2 days, but I haven't had much luck... I want to try to get a download success with the MiFlash tool as well. I think it is just random luck if you can get a download to succeed, which then gets the phone into a normal bootloop (or perhaps just back to normal operations), and then you can flash the bootloop fix files from recovery.
[Nexus 6P General] :
[MENTION=8468327]apples1678[/MENTION] I tried again today, and after a few tries, I was able to get the file transfer done 100%. Yay!! :o

However, the device is still not turning on and gets detected as Qualcomm HS-USB QDLoader 9008 (COM 3). :confused:

Edit: I tried disconnecting and reconnecting device, and now it is getting detected as Unknown USB Device under USB controllers in device manager.
[Nexus 6P General] :
Your experience matches mine. I had another successful download today as well. Try leaving it plugged in overnight and attempting to boot directly into recovery after it has been plugged in for a while. I've only been able to get into recovery after the phone has sat idle and plugged in for an extended period of time.

I'm not quite sure where to go from this point - we probably need someone like [MENTION=540283]tenfar[/MENTION] or [MENTION=5288606]XCnathan32[/MENTION] to tell us what exactly these tools (MiFlash/QFIL) are doing and what the expected outcome after a successful transfer of the files onto the device should be. Should it immediately be bootable? Is there some other command to run? Are there any other steps we can take?

I feel like the solution must be close since we are able to get these tools to recognize the device and even transfer files, I'm just not quite sure what else to try.
[Nexus 6P General] tenfar:
if you have successfully downloaded(100%） all the file with qfil or miflash, but you cant boot the phone .try press power key with 30 seconds. if it still dont boot ,that means your phone is hardware brick.it is a hardware problem.

this firmware or method is meant to fix software problem. at least you need to boot into bootloader or recovery.
[Nexus 6P General] mintminty59:
I get this issue

[00001FA8]CreateManagedObject(1261): Unspecified error(0x80131604)

[00001FA8]GetFactoryObject(1305): Unspecified error(0x80131604)

[00001FA8]CreateManagedObject(1261): Unspecified error(0x80131604)

[00001FA8]GetFactoryObject(1305): Unspecified error(0x80131604)

[00001FA8]GetFactoryObject(1326): The specified service does not exist.(0x800704db)

[00001FA8]GetSearchPath(1381): The specified service does not exist.(0x800704db)

[00001324]CEmergencyFlasher::IsQPSTServer(634): Not implemented(0x80004001)

[00001324]COM15	0.22	Open serial port "\\.\COM15"

[00001324]COM15	0.23	Load programmer "c:\back\MPRG*.*"

[00001324]DownloadFlashProgrammerDMSS(483): An attempt was made to load a program with an incorrect format.(0x8007000b)

[00001324]DownloadFlashProgrammerAndMiniKernel(936): An attempt was made to load a program with an incorrect format.(0x8007000b)

[00001324]COM15	0.23	Open programmer "c:\back\MPRG*.*"

[00001324]CreateSharedFileMapping(446): The filename, directory name, or volume label syntax is incorrect.(0x8007007b)

[00001324]DownloadFlashProgrammerSahara(598): The filename, directory name, or volume label syntax is incorrect.(0x8007007b)

[00001324]DownloadFlashProgrammerAndMiniKernel(939): The filename, directory name, or volume label syntax is incorrect.(0x8007007b)

[00001324]CSoftwareDownload::DownloadBySettings(2161): The filename, directory name, or volume label syntax is incorrect.(0x8007007b)

[00001324]CEmergencyFlasher::DoWork(611): The filename, directory name, or volume label syntax is incorrect.(0x8007007b)

[00001324]GetFactoryObject(1326): The specified service does not exist.(0x800704db)

[00001324]SaveFlashResult(1347): The specified service does not exist.(0x800704db)

---------- Post added at 02:49 PM ---------- Previous post was at 02:16 PM ----------

Now I get

saraha_RX data 194: unable to read packet header data only read 0 bytes

sarah_main 894 : Protocool error
[Nexus 6P General] Rafael-57:
Would this work if the phone is not charging and is not detected by Windwos Device Manager?

My 6P freezed while it was running Facebook, I tried to reset it with the hardware buttons and it stopped responding in any way ever since
[Nexus 6P General] jassun16:
EDL mode drivers link is not working, saying : Yeah, you come late, share the file has been canceled, next time to be yo.

Please change the link and I really need help as my nexus 6p isn't booting
[Nexus 6P General] apples1678:
thanks for replying.

I've given up - I haven't been able to get the phone to boot up at all for two weeks now. I left it plugged in for about a week and unplugged for about a week and haven't been able to do anything at all. It still shows up as QDLoader 9008 (COMX), but I think you are right, it is a hardware issue that I'm not equipped to debug or repair.

I might try to solder reflow method with a hair dryer.
[Nexus 6P General] BlackPseudicide:
Phone wouldn't boot this morning, having the same problems as others, dead, black screen, no boot, no lights, no windows noises, shows up as COM3. No luck with ADB, Miflash is either "Object reference not set" or can't read hello, QPST sometimes shows sahara download, QFIL gives error. Any chances of reviving this device?
[Nexus 6P General] BadBoy2K7:
WTF that is what happen to me too....
[Nexus 6P General] coremania:
could somebody be so kind and give me a working link to the edl mode drivers ??
[Nexus 6P General] appuserprime:
im getting errors like everyone else but i found the drivers and installed the QDL interface. u still want it?
[Nexus 6P General] coremania:
Thanks, but i took older qualcomm drivers 2012 or 13 and everythings fine.

I unbricked my phone successfully.

I only had a timing error, which cost me an hour to find it out. I used qfil and had to immediately hit

download after plugging in the USB cabel otherwise it always ended up in errors.

Edit: and I did it with a drained battery, first I thought my phone won't boot after successful writing the image, only the red blinking led, but after a little bit loading and pressing vol- and power several times I got back to bootloader. Flashed latest stock and all is good now.
[Nexus 6P General] appuserprime:
QFIL and hitting download immediately. OK. I always got SIERRA errors from QFIL.

I am currently using the MiFlash(2016.04.01) with the advanced menu and getting results by supplying each file path manually. Also supplying the flash-all.bat from the stock image. Finally got "CATASTROPHIC FAILURE" error message, but got past the "hello" errors after using this advanced menu miflash. I found success with getting it into the correct EDL state by holding down the power button and when it reconnects to windows it is ready.

I will try your QFIL method with my current drivers (from MiFlash 2016.04.01) and QFIL, but can you please advise me how you unbricked your phone? My Qfil is 2.0.0.5 and I am using the fastboot from from the OP. Like I said my 9008 drivers are from the Miflash version.

---------- Post added at 07:53 PM ---------- Previous post was at 07:42 PM ----------

EDIT: Ok. Your method worked partially. I got all the way to the QFIL error where it took longer than 3.00 seconds to open my COM port. Should I keep trying?

EDIT: I also used the command line method with Qsierraserver like a member said in earlier posts near page 11. However it appears that it is never able to open my port. Is this because the bootloader is unlocked?
[Nexus 6P General] coremania:
OK, i try to remember what i did exactly.

I used usbdeview and deleted all old usbdrivers, because

my n6p wasn't recognized as 9008(comx). I used old Qualcomm drivers and it worked. I had no success by using miflash, I used latest qfil and the firmware files from first post here. Loaded the files in qfil and now I'm not sure if I pressed only power or vol- or both while I was connecting the phone via USB. But you said you find out the edl mode already. But I had to immediately press the download on qfil as the 9008 (comx) message shows up while connecting the phone. If I waited only a second to long it ended in error messages.

Edit: ask the guy above for the driver, he friendly offers me the file. May it's just a driver issue. I tested several because I was not able to get the driver file from the op.
[Nexus 6P General] karlj38:
Had similar problems today :( I was performing a backup in twrp recovery when it just turned off. No light, no bootloader, no vibration, nada. After some googling and random button pressing, I managed to get it to show up in Device Manager as 9008(COM4). Eventually, using QFIL (2.0.1.1) I was able to successfully flash OP's service rom with the Flat Build option. The blue bar went all the way to the right and it said successful. But still, it would not turn on! I even found a Turkish site with a different service rom (http://www.androidbrick.com/download/unbrick-nexus-6p-angler/) and it wouldn't boot anything either. HELP?

To be clear, it did not say in the QFIL log, "Reset phone. Waiting for reset done...", like others have claimed. I can't remember exactly what it said but it said successful.

For reference, I have previously replaced the battery myself, so it might be a hardware issue. But if it was, why would it even be recognised by the pc at all?
[Nexus 6P General] coremania:
Yes, I had the same issue after reviving the phone, battery was completely zero. I left it connected to the PC USB port and tried random button combination for minutes and it booted back to life. But your story sounds more like motherboard issue or you didn't connected your battery replacement right. May you just have a loose connection ???
[Nexus 6P General] psychomaniac189:
do you still have the links? I just found this thread and want to try to unbrick my phone. hope i can get something out of it. I just need the EDL mode drivers

edit: i have the device showing up at 9008 but i cant get it to show up in MiFlash. any ideas?
[Nexus 6P General] karray:
I also have the phone in QDLoader 9008 mode. It happend after a usual reboot. I have the latest firmware (Oreo 8.1) and the bootloader has been never unlocked.

Now I'm stuck in qfil at the following error

Sahara mappings:
2: amss.mbn
6: apps.mbn
8: dsp1.mbn
10: dbl.mbn
11: osbl.mbn
12: dsp2.mbn
16: efs1.mbn
17: efs2.mbn
20: efs3.mbn
21: sbl1.mbn
22: sbl2.mbn
23: rpm.mbn
25: tz.mbn
28: dsp3.mbn
29: acdb.mbn
30: wdt.mbn
31: mba.mbn
13: prog_emmc_firehose.mbn
19:51:51: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
19:51:51: ERROR: function: sahara_main:924 Sahara protocol error
19:51:51: ERROR: function: main:303 Uploading Image using Sahara protocol failed

Does anyone have any ideas?

UPDATE: I managed to flash the phone successfully using qfil but the phone still doesn't respond. So I'm going to throw it away
[Nexus 6P General] chuckywang:
Hello, I have this same issue. My phone only detects as "Qualcomm HS-USB QDLoader 9008 (COM3)" when plugged into my Windows computer.

My question is this - If I follow this guide to attempt to unbrick it, will I lose all my data? Things like photos and downloads?
[Nexus 6P General] aleph23:
:crying: This times out after 199 seconds with error "Failed to get Hello Packet"...
[Nexus 6P General] gustavocaa:
So it happend same thing to me, left the phone charging, came back a few minutes later, and found the phone turned off and couldnt turn it on.

im on 8.1

Tried many stuff from this thread and others, but still nothing.

I left the phone "charging" the whole night and now just trying to normally turn it on.... and it worked!!, i enter to bootleader to format stock again.

I see that my battery was at 2% after setting up my phone again...

I was having issues with my phone shutting down at 20% before this happend

Does that imply is just the battery?, now while im setting all up, i see that the battery is charging normally

why before wouldnt charge at all, and now it charges normally. Ive been using the same cable and didnt have issue of trying to put the cable on a different angle because the phone wouldnt charge
[Nexus 6P General] ramindersk:
Hi

How you managed to get your phone to download. Please help me if you still remember. I got the same message as you and don't know what to do next.
[Nexus 6P General] ramindersk:
Not working for me

I have done everything, flash provided files with miflash and qfil. Both flashes were successful but my phone is still dead, no red light blinking no vibration nothing. Is something is wrong with my phone?

Edit: Red light blinking started but no bootloader or recovery mode.
[Nexus 6P General] Kzpogyzp:
Hi when i try to flash the firmware, it shows :

[10.01 COM3]:[COM3]:start flash.

[12.03 COM3]:cannot receive hello packet,MiFlash is trying to reset status!

[14.55 COM3]:cannot receive hello packet,MiFlash is trying to reset status!

[17.06 COM3]:try to reset status.

[19.08 COM3]:Switch mode back

[20.08 COM3]:write time out try agian 96

[21.58 COM3]:write time out try agian 97

[23.09 COM3]:write time out try agian 98

[24.60 COM3]:write time out try agian 99

[26.10 COM3]:write time out try agian 100

[26.61 COM3]:error:The write timed out.

[26.61 COM3]:error:The write timed out.

Is there a solution to this? Thanks.
[Nexus 6P General] vikkyv:
Bricked Device

I am facing the same issue my nexus 6p showing as qualcomm hs-usb qdloader 9008(com3).

After applying your method am getting same error over and over again when am trying to flash usning QFIL. The error is( ERROR: OpenPort:5214 It took 10.000000 seconds to open port. Which is longer than 3.000. This indicates your target is not stable) some time it took 179.9800000 seconds

can anyone please help me
[Nexus 6P General] javidp:
Hello

I have the same problem. I want to follow this guide, however the files aren't available anymore.

Can someone share them with me?

Thanks.
[Nexus 6P General] gamer06:
hi, i'm with the same probleme here. My N6P wont turn on, blackscreen always...

There is a way to put the links on? i can´t download the file "nexus6p_fix_bricked.zip ".

Thanks a lot
[Nexus 6P General] harjeet85:
Same problem here. But now link for custom rom is not working. Can someone please share that rom?
[Nexus 6P General] Silverdace:
Anybody able to provide a link to the rescue rom nexus6p_fix_bricked.zip ??
[Nexus 6P General] caiejay:
still no working rescue rom link?
[Nexus 6P General] Holymsophy:
First off, thanks tenfar and everyone who has been able to try this and get it to work successfully. With that said, could someone please be kind enough to post working links to the factory firmware recommended and the nexus6p_fix_bricked.zip please? This links are no longer active.

Thanks.
[Nexus 6P General] burakcuhadaroglu:
Pls new upload link for nexus6p_fix_bricked.zip???
[Nexus 6P General] hjmrox:
any kind soul who have previously downloaded nexus6p_fix_bricked.zip from the OP, can you please share it ?

My experience and steps taken here - https://xdaforums.com/showpost.php?p=77238876&postcount=494
[Nexus 6P General] hjmrox:
Hi, I'm also facing the same issue as you.

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 (need to set an option in configuration menu for the reset). 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

Did you manage to find any fix for your phone at all ?
[Nexus 6P General] Vaseag:
Anybody able to provide a link to the rescue rom nexus6p_fix_bricked.zip ??
[Nexus 6P General] olmos2:
Delete Thread here pls. WHERE IS F... FILE

nexus6p_fix_bricked.zip

CU
[Nexus 6P General] rais.asif786:
you should upload the new links