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

[Ikkye]

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 send the file that you created to me ? My nexus is dead too, I wanna try to restore it

Thanks

 

[spanyam]

Is this guide still valid? I'm getting the non-responsive brick and getting the below two issues no matter which method I try. I do get the port showing up correctly, but the download always fails with the Sahara error.

 

[kydrio]

You are a real F...ng god, thank you so much man !

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.

You are a real F...ng god, thank you so much man !

I just follow your steps and now... its alive... its ALIVE MAN tnx :fingers-crossed:

 

[joongpark]

My Nexus 6P is stuck on GOOGLE logo with corrupt bootloader/ROM and phone is locked. Will this method work for my phone? I can't use any other tool because phone is locked and I can't boot to allow OEM unlocking.

 

[aleph23]

Is this guide still valid? I'm getting the non-responsive brick and getting the below two issues no matter which method I try. I do get the port showing up correctly, but the download always fails with the Sahara error.

Same error I'm getting. Did you ever get yours fixed?

Additionally, holding down the power button never causes a reboot/state-change.

Luckily there's already alternative for linux

Care to elaborate? I'm desperate to get my phone working again. I was able to complete only half of a fh_loader.exe (CLI) upload, but I still boot to HD-USB 9008 state. QFIL does nothing for me, only QSaharaServer.exe and fh_loader.exe, both command-line progs. QFIL always fails.

 

[chuckywang]

Can anyone provide an alternative way to reverse this hard brick? I can't seem to get QFIL working either, getting error "10 seconds to open port. Which is longer than 3. This indicates your target is not stable".

I did NOT brick my phone using the bootloader. It bricked by itself when I was browsing the web on Chrome for Android. It turned off and just wouldn't turn on again....

 

[aleph23]

Can anyone provide an alternative way to reverse this hard brick? I can't seem to get QFIL working either, getting error "10 seconds to open port. Which is longer than 3. This indicates your target is not stable".

I did NOT brick my phone using the bootloader. It bricked by itself when I was browsing the web on Chrome for Android. It turned off and just wouldn't turn on again....

I was able to successfully upload with the command line tools I lost in the past above yours. I still have a brick instead of a phone, but the CLIs were at least able to do something .

 

[chuckywang]

I was able to successfully upload with the command line tools I lost in the past above yours. I still have a brick instead of a phone, but the CLIs were at least able to do something .

Is this guide just for bringing a dead nexus 6p back to life due to a software or firmware issue? What if it's hardware issue, like cracked solder (I read in other places that cheap solder causes the bootloop issue, but that's not really my scenario. My phone is completely dead). Would this fix work for a hardware issue like that as well?

 

[aleph23]

Is this guide just for bringing a dead nexus 6p back to life due to a software or firmware issue? What if it's hardware issue, like cracked solder (I read in other places that cheap solder causes the bootloop issue, but that's not really my scenario. My phone is completely dead). Would this fix work for a hardware issue like that as well?

Totally depends on your specific hardware issue. Not to be a smartass, but generally speaking something intangible/that cannot be touched (in this case "software") cannot repair something physically broken as physical interaction is required (resoldiering, to use your example).

The only exception to this I can imagine here would be if you had some slightly physically damaged emmc (memory chip), reflashing the emmc could potentially restore functionality. It would depend on the extent and location of the damage.

 

[theburrus1]

Luckily there's already alternative for linux

Hi, I see your post about Linux alternative us a year old but I need to know specifically what is that equivalent, please? I have a hard bricked Huawei 6X that I could maybe fix, but I refuse to run Windows, and have not fixed the phone yet. I can get the OTA firmware okay, but the phone won't get past the initial "unlocked bootloader" warning screen, so can't get to fastboot or adb.

I distrohop on Linux so whatever may help, regardless of type of package, any help is appreciated!

 

[aleph23]

Hi, I see your post about Linux alternative us a year old but I need to know specifically what is that equivalent, please? I have a hard bricked Huawei 6X that I could maybe fix, but I refuse to run Windows, and have not fixed the phone yet. I can get the OTA firmware okay, but the phone won't get past the initial "unlocked bootloader" warning screen, so can't get to fastboot or adb.

I distrohop on Linux so whatever may help, regardless of type of package, any help is appreciated!

I asked also, but never got a response. The only thing I'm aware of its the ability of many distros to easily mount a device that's in Qualcomm 9006 mode...

Are you able to force 9008 or 9006 modes?

 

[ksaves2]

If I understand correctly, if one's phone is in a bootloop without OEM unlocking or Android Debugging selected prior to the startup anomaly, this method won't work? Got a blod phone and curious. Kurt

 

[aleph23]

If I understand correctly, if one's phone is in a bootloop without OEM unlocking or Android Debugging selected prior to the startup anomaly, this method won't work? Got a blod phone and curious. Kurt

That's my understanding. No personal experience w BLOD tho, or the two conditions.

 

[ksaves2]

That's my understanding. No personal experience w BLOD tho, or the two conditions.

Thanks! Gotta get a different phone if I want 128Gb. At least had battery change practice.
Kurt

 

[Kzpogyzp]

Hi, ive encountered an error:

ERROR: function: sahara_rx_data:194 Unable to read packet header. Only read 0 bytes.
ERROR: function: sahara_main:854 Sahara protocol error
01:47:56: ERROR: function: main:265 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Failrocess fail
Finish Download

is there a solution to this? thanks.

 

[javidp]

I am having the same exact issue. It stopped working on its own while it was charging, I got it to turn on a few times but it wouldn't last any longer than 2 minutes. I managed to put it in bootloader mode and wipe cache partition. But after a few times it just went off completely and now is on the 9008 mode.

I am trying to follow this guide, but always get the Sahara server error. I read it could be a driver issue, so later today I will be mounting a virtual machine with a clean Windows install and try and see what happens, I'll let you know. If you have any other ideas, please feel free to share.

 

[SkinlessMage006]

I am also getting this error it would be good if there was a fix since my Nexus is also dead
EDIT: Uninstalling my current QPST and installing this helped me at least start the process. Will let you know if my Nexus actually comes back to life and if this worked

 

[SkinlessMage006]

Okay, so I did this and it actually succeeded. But no life in the Nexus still - must be hardware

 

[caiejay]

Okay, so I did this and it actually succeeded. But no life in the Nexus still - must be hardware

How did you get it to work?

 

[orisha1905]

pleaseee, any have a rom unbrick?, the link is offline