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

[syedsaab]

Same here. Any luck since?

 

[ashish308775]

hi bro need your help

hi bro can you sent me your contact number so i can easley contact you via facebook whatsapp

email me at [email protected] gmail.com

thanks

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.



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..

 

[ncc8uetou5et]

I dont see any report here if the howto have helped to recover a phone WITHOUT any data loss. My phone suddenly turned off under heavy load and now its stuck in this EDL 9008 mode for days. I have read someone telling that you have to let the battery drain by letting it connected to usb because it were not charging in EDL mode. Now it stay connected since about a week and no change.
Have you recovered it without any data loss?

How to do the fix with linux?

 

[ncc8uetou5et]

Anyone? I really need my data

 

[joshyzacariya]

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.

Can you please explain a bit more as my Nexus 6p also in the same situation.
I tried QFIL many times but no luck!

 

[publicwifihotspot]

The file has been moved to your trash...any chance you could resurrect the file?

 

[omi_omi]

Could you make file available via drive again, please?

Could you make file available via drive again, please? I am having the same problem.

 

[RobBlakemore]

Hi - the files are now apparently in your GOOGLE DRIVE BIN! Please can you remove them from the bin before the are fully deleted/make them available again! https://drive.google.com/file/d/0By19rrbnQfVUVFZEVUZqQzY1RWs/view

Thanks!

 

[DocGoneWild]

Hi - the files are now apparently in your GOOGLE DRIVE BIN! Please can you remove them from the bin before the are fully deleted/make them available again!

Thanks!

Any luck? first my screen cracked, then the phone bootlooped, and now its bricked...Lifes great ....Anyways where you at @Lw00d

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

hi bro can you sent me your contact number so i can easley contact you via facebook whatsapp

email me at [email protected] gmail.com

thanks

hmm....if u got his contact, do u mind sending it to me through a private message? would really appreciate it, thanks.