[FIX] fix hard brick / qhsub_bulk after bad flash / cm12 flash from 5.1

[cam30era]

Please can someone help me?

I am stuck in the bootloader, which is locked. I can't boot the phone up. I am trying to flash stock images but nothing is happening. Just booting to the bootloader every time.

I can detect my device using fastboot devices, but every time I try and write an img it fails, because the bootloader's locked! Argh!

Thanks in advance,

Tom

Look at the end of post #14.

Edit: meant 14

 

[tommydeaks]

Look at the end of post #14.

Edit: meant 14

Bugger. Need to see if Giffgaff will accept a return, as the device code is 0...

 

[serdaj]

First, fastboot flash partition gpt.bin
Then, fastboot reboot-bootloader

Then flash the other images.

If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.

This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.

-Chris

I tried that command to no avail. Where would the gpt.bin file be located?

fastboot flash partition gpt.bin
error: cannot load 'gpt.bin'
​

Does anything look off or wrong with the Bootloader screen? It reads as follows:

AP Fastboot Flash Mode (Secure)
BL: moto-apq8084-71.08(*) (sha-32b8854, 2014-12-09 14:00:26)
Baseband:
Product/Variant: shamu XT11103 64GB P3A0
Serial Number: 3c0a6014
CPU: APQ8084 ES1.1
eMMC: 64GB Sandisk RV=07 PV=01 TY=57
DRAM: 3072MB Samsung S8 SDRAM DIE=6Gb
Console [NULL]: null
Battery OK (Charging)
Device is LOCKED. Status Code 0
Transfer Mode: USB Cnnected​

 

[ccfries]

I tried that command to no avail. Where would the gpt.bin file be located?

fastboot flash partition gpt.bin
error: cannot load 'gpt.bin'
​

gpt.bin is a component inside the bootloader.img, otherwise it's split out here for convenience, android-review.googlesource.com/#/c/143010/

 

[serdaj]

gpt.bin is a component inside the bootloader.img, otherwise it's split out here for convenience, android-review.googlesource.com/#/c/143010/

Thanks for the help in advance. I hope I can figure this out. Poor N6 is sitting there dead staring at me. I didn't see the .bin file at that link but I"m not entirely certain what I'm looking for?

Is no one else having this issue following this fix? I followed all the steps listed in OP but no fix. I guess I made a mistake somewhere. Any ideas or further instructions would be greatly appreciated. I have to leave for a bit. Hopefully someone can reply and provide some further insight and assistance. Tank god for this community and the senior members.

[edit] I followed all the steps above on my Windows 7 laptop before running into the <waiting for device> issue. I noticed today that although Windows is recognizing the device (as "fastboot shame S") on the device screen it still shows "Connect USB Data Cable". I plugged it into all USB ports with no change. I plugged it into my Macbook (where I normally do all my flashing) and it recognizes the device and reads "Transfer Mode USB Connected". On the Macbook is where I am getting all these errors and copying from terminal for this post as I only get <waiting for device> on Windows.

 

[brando56894]

You need to have gpt.bin in the same directory as the fastboot command, I'm assuming you would download it from the first post. I'm just reading this for future reference.

Glad to know that this phone is almost becoming truly unbrickable!

 

[serdaj]

You need to have gpt.bin in the same directory as the fastboot command, I'm assuming you would download it from the first post. I'm just reading this for future reference.

Glad to know that this phone is almost becoming truly unbrickable!

Yeah I knew to make sure it was in the same folder as ADB and Fastboot. I just don't know where/how to locate the the file to flash it.

 

[opssemnik]

First, fastboot flash partition gpt.bin
Then, fastboot reboot-bootloader

Then flash the other images.

If you just bricked by downgrading bootloader, the persist and modem calibration should still be happily where it was when you started.

This won't help you if you're stuck with Allow OEM Unlock. Be careful locking on 5.1. There's accurate information elsewhere in the forum on that.

-Chris

Thanks added that. i added to the second post since i didn´t have to do that, maybe it happens if you have unticked allow oem unlock? idk

 

[opssemnik]

Yeah I knew to make sure it was in the same folder as ADB and Fastboot. I just don't know where/how to locate the the file to flash it.

the file gpt.bin is inside UnbrickStuff.rar, or you can directly download it from google source code(see patch review in OP)

 

[opssemnik]

Thanks for the help in advance. I hope I can figure this out. Poor N6 is sitting there dead staring at me. I didn't see the .bin file at that link but I"m not entirely certain what I'm looking for?

Is no one else having this issue following this fix? I followed all the steps listed in OP but no fix. I guess I made a mistake somewhere. Any ideas or further instructions would be greatly appreciated. I have to leave for a bit. Hopefully someone can reply and provide some further insight and assistance. Tank god for this community and the senior members.

[edit] I followed all the steps above on my Windows 7 laptop before running into the <waiting for device> issue. I noticed today that although Windows is recognizing the device (as "fastboot shame S") on the device screen it still shows "Connect USB Data Cable". I plugged it into all USB ports with no change. I plugged it into my Macbook (where I normally do all my flashing) and it recognizes the device and reads "Transfer Mode USB Connected". On the Macbook is where I am getting all these errors and copying from terminal for this post as I only get <waiting for device> on Windows.

what mode does your pc detects your n6 as? fastboot? adb? qpst ?

 

[opssemnik]

Erm, don't mind me asking one question.
How do you back up your efs if your phone is bricked?

i just added that if you happen to have problems with efs or persist, but those shouldn´t be necessary.
i have recovered 2 time´s my friend´s nexus 6 and i didnt have to do it

 

[opssemnik]

Looks good. Does this only help the CM12 people or does it override the "enable OEM Unlock" people too?

not if in 5.1

 

[ccfries]

Thanks added that. i added to the second post since i didn´t have to do that, maybe it happens if you have unticked allow oem unlock? idk

If you lock, it clears the setting by design, so you can't lock and unlock without booting up and checking the box.

 

[opssemnik]

If you lock, it clears the setting by design, so you can't lock and unlock without booting up and checking the box.

Thanked, added to op and post #2

 

[serdaj]

what mode does your pc detects your n6 as? fastboot? adb? qpst ?

PC isn't displaying the device with "fastboot devices" or "adb devices" commands. I don't know why but it the phone doesn't show that it is connected when plugged into the PC. If there is a test or command I can try to run to give anyone more information I'd be happy to do so.

 

[opssemnik]

PC isn't displaying the device with "fastboot devices" or "adb devices" commands. I don't know why but it the phone doesn't show that it is connected when plugged into the PC. If there is a test or command I can try to run to give anyone more information I'd be happy to do so.

Look in the device manager, see what device gets added when you plug your nexus 6

 

[serdaj]

Look in the device manager, see what device gets added when you plug your nexus 6

Yes in there it is showing as "Fastboot shamu S"

 

[opssemnik]

Yes in there it is showing as "Fastboot shamu S"

do you have Fastboot set on your PATH enviroment, or are you running it from a folder?

 

[serdaj]

do you have Fastboot set on your PATH enviroment, or are you running it from a folder?

PATH Environment

 

[opssemnik]

PATH Environment

put gpt.bin in the root of your local disk and then run
fastboot flash partition c:\gpt.bin (or whatever your local disk´s letter is)