[GUIDE] how to bring back to life dead nexus 6p , hard brick.

[Lw00d]

i hard brick my phone yesterday. trying to flash bootloader with flashfire. (the lazy way) thats what i get. anyways could not turn on n6p, tried charging it for a couple of hours, try holding power button for 30 seconds, try power + volume . tried holding all buttons. nothing work.. read some threads saying its done. look for new phone or send to get repair. then i found tenfar thread. long story short. i used some of tenfar info and rwj5279955.. so big thanks to these two users
here is what i did to get my N6p to turn back on.. brick by bootloader.. this is my first how to .. bear with me. please.

you will need the following https://drive.google.com/file/d/0By19rrbnQfVUVFZEVUZqQzY1RWs/view?usp=sharing

Qualcomm drivers
QFIL software
3 files, patch0, prog_emmc_firehose, rawprogram0 .. for this to work
1. install qualcomm drivers, Connect phone to pc, open Device Manager. if you see under com port Qualcomm USB loader or something along those lines. your good, go to step 2. if not disconnect phone hold power button for 10 seconds, wait for 5 seconds connect phone to pc. check if in com ports you see Qualcomm drives. if you can not get qualcom drivers on com port. just stop. its not going to work..
2. extract the three files. in a folder somewhere easy to remember.
3. install the QFIL software, . once install run QFIL.
4. in QFIL software
if qualcomm driver are found it will say on top of QFIL software Qualcom USB loader 9008
Select Build Type: click Meta Build
Select Build :: patch0 ... if for some reason patch0 doesnt work try rawprogram0
Select Programmer:: pro_emmc_firehose
hit download ...if the blue bar get to half way mark your golden. its going to always fail. the trick is to get the blue bar at least half ways. then you disconnect phone, hold power button, it should turn on.. then you ADB what ever you need to do.

for those that get the fail right away.. while phone connected to pc, hold power button until drivers disappear from device manager.. then disconnect phone, wait for 5 seconds, hold power button, for 10 second,.. wait for 5 seconds .. then connect phone back to pc, wait for device manager to see drivers.. then hit the download button . do this part over and over again ..until it works..

sorry for this horrible guide.. it work for me.. hope it works for you..

 

[DEVILOPS 007]

That's a lot to take in! Is this for windows only then not Linux? Bootloader and radio does have to be flashed via fastboot

 

[Lw00d]

That's a lot to take in! Is this for windows only then not Linux? Bootloader and radio does have to be flashed via fastboot

Windows

 

[DEVILOPS 007]

Windows

Luckily there's already alternative for linux

 

[Clarkeofcurtis]

Hello thank you so much for your guide, currently trying to unbrick my nexus 6P stuck in 9008 port, could you provide a link for your version of Qfil please? as I'm struggling to find your 2.0.0.2 version I either get 1.0.0 or 2.0.0.3 and they're not working

Update: I've found the version! However when I quick Meta build and attempt to locate XML there's nothing I can select? sorry if this is really simple just never done before thank you

 

[Lw00d]

Hello thank you so much for your guide, currently trying to unbrick my nexus 6P stuck in 9008 port, could you provide a link for your version of Qfil please? as I'm struggling to find your 2.0.0.2 version I either get 1.0.0 or 2.0.0.3 and they're not working

Update: I've found the version! However when I quick Meta build and attempt to locate XML there's nothing I can select? sorry if this is really simple just never done before thank you

place the files in a folder.
then in QFIL brows to the folder
need to select build path first.

 

[KLit75]

What type of brick does this fix? Is this for the big one " boot loop of death" that's been well covered?
I ask out of curiosity. My phone's unaffected (knock wood)

 

[Lw00d]

What type of brick does this fix? Is this for the big one " boot loop of death" that's been well covered?
I ask out of curiosity. My phone's unaffected (knock wood)

hard brick. phone does not turn on at all

 

[Clarkeofcurtis]

place the files in a folder.
then in QFIL brows to the folder
need to select build path first.

I have done as stated, however when attempting to select build after clicking META BUILD, I have to change the browsing options to ALL FILES from META BUILD CONFIGURATIONS otherwise I can't find anything?

Once selected Patch0, I proceed to select programmer path, but then my download content isn't clickable please?

 

[Lw00d]

Select build type click flat build. See if u could click on download

 

[Clarkeofcurtis]

Select build type click flat build. See if u could click on download

I can start it VIA flat build, however I get this error

 

[Lw00d]

Now try with meta build

 

[Clarkeofcurtis]

Now try with meta build

When trying with meta build this is the problem I'm faced with.

Can't select anything, am i using wrong version of Qfil perhaps or isn't that an issue as it's the newst?

I click load content and I can't view the files I'm supposed to be selecting

 

[Lw00d]

When trying with meta build this is the problem I'm faced with.

Can't select anything, am i using wrong version of Qfil perhaps or isn't that an issue as it's the newst?

I click load content and I can't view the files I'm supposed to be selecting

That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?

 

[Clarkeofcurtis]

Sorry, I've found it again. But this time - different error... :/ Any ideas?

That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?

Thank you for your help and replies, no blue bar when I click download on flat build, just gives me that port error about it taking 10 seconds to open when it should only be 3? I'll try it on your version and let you know bare with me

---------- Post added at 07:44 AM ---------- Previous post was at 07:32 AM ----------

That never happen to me.. Could be the version u have installed.
In flat build. When u hit download. Does the blue progress bar move?

Could you send me a link to your version please?

Sorry, I've found it again. But this time - different error... :/ Any ideas?

 

[Lw00d]

Sorry, I've found it again. But this time - different error... :/ Any ideas?



Thank you for your help and replies, no blue bar when I click download on flat build, just gives me that port error about it taking 10 seconds to open when it should only be 3? I'll try it on your version and let you know bare with me

---------- Post added at 07:44 AM ---------- Previous post was at 07:32 AM ----------



Could you send me a link to your version please?

Sorry, I've found it again. But this time - different error... :/ Any ideas?

It's on first post

 

[Clarkeofcurtis]

It's on first post

Getting this

 

[Lw00d]

Getting this

did you do this..

for those that get the fail right away.. while phone connected to pc, hold power button until drivers disappear from device manager.. then disconnect phone, wait for 5 seconds, hold power button, for 10 second,.. wait for 5 seconds .. then connect phone back to pc, wait for device manager to see drivers.. then hit the download button . do this part over and over again ..until it works..

also try extracting all these files into the folder you made .. this includes the three files .. https://drive.google.com/open?id=0By19rrbnQfVUbFZSc3A3VXhGRzQ

 

[Codename13]

Thank you so much! I messed up my 6P when I tried to flash a bootloader image via Flashfire. I hadn't been in a brick this bas since the good old days of Gingerbread and ROM Manager! For anyone else having similar issues, I got my dead 6P to be recognized as QHSUSB_bulk eventually in Windows 7. I then edited the rawprogram0.xml file (from OP's link) in a text editor. I removed the entries for all the other partitions I didn't want to overwrite (like system and vendor and userdata), leaving only the sbl1 (secondary bootloader, the part of the firmware that actually boots into the system/recovery/bootloader when the device is first powered on) partition entry - because that's what Flashfire said it had flashed the entire bootloader image to. Doing a bit of research, I found that our bootloader image is actually just many different small partitions all grouped together into a single image file. I couldn't figure out how to unpack the bootloader image, so I downloaded a full firmware OTA zip from Google, and lo and behold, there was a "bootloader.sbl1.img" (along with other small partitions) file in the OTA zip. I changed the sbl1.img entry in the rawprogram0.xml file so that it correlated with the filename "bootloader.sbl1.img", I moved the image file into the same folder as the rawprogram0.xml, and then I was able to restore my device to it's previous functionality using the "flat build" download configuration in QFil, though the whole process did take me like 3 hours. Lesson learned - screw using Flashfire for bootloader images.

 

[Bricked6p]

ERROR: Could not access "C:\temp\vendor.img" with access mode 'rb'

When I'm finally lucky, rebooting, replugging the phone, it looks like it might flash...

...then I see this.

I've given all permissions to all users for full control, on the file, I've run time program as administrator, I don't know what else to do. If it can't open the file, I can't flash my phone. I'm not a Windows administrator so I don't really know what to do to get this to work and I can't find any hints on the forums.