[GUIDE] Unbrick hard bricked Moto Z

[Manish54]

.
.
.
.
HOW TO UNBRICK A HARD BRICKED MOTO Z XT1650-03
Note: This is only for Moto Z XT1650-03. Don't use this for any other device, i'm not responsible if anything happens to your device.​

My Moto Z died in January because of flashing a wrong file and it wont power on or charge. And the service center wont help because Motorola voids your warranty the moment you get the unlock code from their website. So i kept digging for 3 months and finally my phone is back from the dead. And i'd like to help other people who are struggling with the same problem.

So, things you'll need:
-A dead Moto Z with no boot/charging at all
-Drivers
-Blankflash file
-Stock Rom/Custom Rom

How To Unbrick:
Step 1: If your PC detecta the phone as QUSB_BULK device, install the drivers provided. If it detects it as qualcomm device 9008 or something, then move directly to step 2.
(If your PC is not detecting your phone then try removing the battery and then plugging it back on. Connect to the PC and press the power+volume down button for 2 minutes. Keep trying this this with different USB ports until the PC detects it.)

Step 2: Now extract the blank flash file and run the 'blank-flash.bat' file. Your phone should boot into fastboot now.

Step 3: Now you can flash your stock ROM or any custom ROM. I suggest you flash TWRP and boot into recovery and flash a custom ROM first. And then flash the Stock ROM later if you want to because flashing stock rom is very tricky in Moto devices and you can end up screwing your device even more during the hardbrick phase.

Cheers :highfive:

 

[martonto]

Thanks, dude, but it didn't work.

My phone is listed in device manager as qualcomm hs-usb qdloader 9008, but when I try to run the batch script it fails.

Here's the log, if it helps:

**** Log buffer [000001] 2017-04-15_15:21:57 ****

[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 3.001] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 3.001] Check qboot_log.txt for more details
[ 3.001] Total time: 3.016s
[ 3.001]
[ 3.001] qboot version 3.37
[ 3.001]
[ 3.001] DEVICE {
[ 3.001] name = "\\.\COM4",
[ 3.001] flags = "0x64",
[ 3.001] addr = "0x61FE5C",
[ 3.001] api.bnr = "0x8E2C38",
[ 3.001] }
[ 3.001]
[ 3.001]
[ 3.001] Backup & Restore {
[ 3.001] num_entries = 0,
[ 3.001] restoring = "false",
[ 3.001] backup_error = "not started",
[ 3.001] restore_error = "not started",
[ 3.001] }
[ 3.001]

 

[Manish54]

Thanks, dude, but it didn't work.

My phone is listed in device manager as qualcomm hs-usb qdloader 9008, but when I try to run the batch script it fails.

Here's the log, if it helps:

**** Log buffer [000001] 2017-04-15_15:21:57 ****

[ 0.000] Opening device: \\.\COM4
[ 0.000] Detecting device
[ 3.001] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 3.001] Check qboot_log.txt for more details
[ 3.001] Total time: 3.016s
[ 3.001]
[ 3.001] qboot version 3.37
[ 3.001]
[ 3.001] DEVICE {
[ 3.001] name = "\\.\COM4",
[ 3.001] flags = "0x64",
[ 3.001] addr = "0x61FE5C",
[ 3.001] api.bnr = "0x8E2C38",
[ 3.001] }
[ 3.001]
[ 3.001]
[ 3.001] Backup & Restore {
[ 3.001] num_entries = 0,
[ 3.001] restoring = "false",
[ 3.001] backup_error = "not started",
[ 3.001] restore_error = "not started",
[ 3.001] }
[ 3.001]

Try a different port. And avoid USB 3.0 ports

 

[martonto]

Still no go. I've been looking for another solution, but I'm yet to have any luck.
It seems there's a qualcomm utility to fix this called BordDiag, but I haven't found one that supports the msm8996 chipset.
Thanks, anyway!

 

[martonto]

Solved!

It finally worked! I've managed to boot into fastboot mode and flash my ROM. My moto Z is now working again!

If anyone ever happens to come across the same error I mentioned in my previous post, there's a trick to solve it that I found in another thread:

Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.

source: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

Thank you again, Manish54! I wouldn't have done it so soon without your help.

 

[Manish54]

It finally worked! I've managed to boot into fastboot mode and flash my ROM. My moto Z is now working again!

If anyone ever happens to come across the same error I mentioned in my previous post, there's a trick to solve it that I found in another thread:

Keep your mobile connected using USB, obviously.
2. using one hand keep power button and volume down button pressed at same time and using other hand click blank-flash.bat file.
3. It might be possible that blank-flash.bat scritps get finished earlier, in that case, keep clicking .bat file continuously, you don't need to close previous cmd window. For me it took 5-6 run to get script detect/communicate with device. Here idea is that your mobile should get detected when you press power button+volume button while blank-flash.bat file is still executing.

source: https://forum.xda-developers.com/moto-g4-plus/help/solved-unbrick-hard-bricked-dead-t3585016

Thank you again, Manish54! I wouldn't have done it so soon without your help.

You're welcome

 

[twitchfidelis]

.
.
.
.
HOW TO UNBRICK A HARD BRICKED MOTO Z XT1650-03
Note: This is only for Moto Z XT1650-03. Don't use this for any other device, i'm not responsible if anything happens to your device.​

My Moto Z died in January because of flashing a wrong file and it wont power on or charge. And the service center wont help because Motorola voids your warranty the moment you get the unlock code from their website. So i kept digging for 3 months and finally my phone is back from the dead. And i'd like to help other people who are struggling with the same problem.

So, things you'll need:
-Drivers
-Blankflash file
-Stock Rom/Custom Rom

How To Unbrick:
Step 1: If your PC detecta the phone as QUSB_BULK device, install the drivers provided. If it detects it as qualcomm device 9008 or something, then move directly to step 2.
(If your PC is not detecting your phone then try removing the battery and then plugging it back on. Connect to the PC and press the power+volume down button for 2 minutes. Keep trying this this with different USB ports until the PC detects it.)

Step 2: Now extract the blank flash file and run the 'blank-flash.bat' file. Your phone should boot into fastboot now.

Step 3: Now you can flash your stock ROM or any custom ROM. I suggest you flash TWRP and boot into recovery and flash a custom ROM first. And then flash the Stock ROM later if you want to because flashing stock rom is very tricky in Moto devices and you can end up screwing your device even more during the hardbrick phase.

Cheers :highfive:

Hello. I have a Sheridan XT1650-03 that I cannot get your fix to work for. I had the Motorola drivers installed so my phone appeared as a "Motorola ADB Interface" in the device manager. When I ran your batch file it hung on "waiting for device" and no matter what USB port I plugged into, 2.0 or 3.0, it's stuck at "waiting for device". So I manually uninstalled the Motorola drivers and forced the install of the drivers you provided so that my phone appears in device manager as "Qualcomm HS-USB QDLoader 9008". Same problem no matter where is plug it in. I have tried this on two different computers with the same result. Can you help me get past "waiting for device"?

 

[Manish54]

Hello. I have a Sheridan XT1650-03 that I cannot get your fix to work for. I had the Motorola drivers installed so my phone appeared as a "Motorola ADB Interface" in the device manager. When I ran your batch file it hung on "waiting for device" and no matter what USB port I plugged into, 2.0 or 3.0, it's stuck at "waiting for device". So I manually uninstalled the Motorola drivers and forced the install of the drivers you provided so that my phone appears in device manager as "Qualcomm HS-USB QDLoader 9008". Same problem no matter where is plug it in. I have tried this on two different computers with the same result. Can you help me get past "waiting for device"?

Are you getting the same "waiting for device error even are it's on Qualcomm..9008 mode?
Do you have universal adb drivers installed?

 

[twitchfidelis]

Are you getting the same "waiting for device error even are it's on Qualcomm..9008 mode?
Do you have universal adb drivers installed?

I am unclear on what you mean by Qualcomm..9008 mode. I have installed the drivers you provided and the phone appears as Qualcomm HS-USB QDLoader 9008 in Device Manager, but still the batch script hangs on waiting for device. The phone is in fastboot bootloader mode, is there a seperate Qaulcomm..9008 mode or is this just a misunderstanding?

I do not know if I have the universal adb drivers you are talking about. Do you have a link? I installed minimal adb and fastboot from here.

https://forum.xda-developers.com/showthread.php?t=2317790

 

[Manish54]

I am unclear on what you mean by Qualcomm..9008 mode. I have installed the drivers you provided and the phone appears as Qualcomm HS-USB QDLoader 9008 in Device Manager, but still the batch script hangs on waiting for device. The phone is in fastboot bootloader mode, is there a seperate Qaulcomm..9008 mode or is this just a misunderstanding?

I do not know if I have the universal adb drivers you are talking about. Do you have a link? I installed minimal adb and fastboot from here.

https://forum.xda-developers.com/showthread.php?t=2317790

It's the same. I skipped the middle portion. Qualcomm HS-USB QDLoader 9008.

And you said the batch file says waiting for device and then you said the phone is in fastboot bootloader mode. Please confirm if you're phone is dead or not. If it's booting into bootloader then you should flash your rom normally.

Here is the adb driver: http://adbdriver.com/downloads/

 

[twitchfidelis]

It's the same. I skipped the middle portion. Qualcomm HS-USB QDLoader 9008.

And you said the batch file says waiting for device and then you said the phone is in fastboot bootloader mode. Please confirm if you're phone is dead or not. If it's booting into bootloader then you should flash your rom normally.

Here is the adb driver:

Yes the batch file says waiting for device. If I open a command prompt and type "fastboot devices" my device is listed. My phone is not dead the screen is clearly on with the icon of the Android lying on its back with a chest panel open and the first line of text says "AP Fastboot Flash Mode (Secure)".

 

[Manish54]

Yes the batch file says waiting for device. If I open a command prompt and type "fastboot devices" my device is listed. My phone is not dead the screen is clearly on with the icon of the Android lying on its back with a chest panel open and the first line of text says "AP Fastboot Flash Mode (Secure)".

Well man... Then this thread is not for you. It is for a dead phone with no boot/charging at all. If you're already on the bootloader then what's stopping you from flashing a rom?

 

[twitchfidelis]

I managed to flash it with a different set of instructions. There is an issue it appears with Windows 10 and RSD Lite maybe it's related to this but who knows. Thanks for your help anyway!

 

[The Unknown123]

hello i have a hard bricked moto z and i can't get it detected on the pc. i have tried on multiple different pc's ALOT of times but it never shows up. any advice?

 

[randomthots]

MOTO Z Hardbricked

Hellow everyone,
my moto z also got hard brick.Tried manish's tutorial and I was successful till the end.But my phone even now dead.I will paste the command lines and the responses I got. Thanks

C:\Users\pterion\Desktop\blankflash\blankflash>.\qboot.exe blank-flash
Motorola qboot utility version 3.37
[  0.000] Opening device: \\.\COM4
[  0.000] Detecting device
[  0.000] ...cpu.id  = 2375 (0x947)
[  0.000] ...cpu.sn  = 43926045 (0x29e421d)
[  0.000] Opening singleimage
[  0.016] Loading package
[  0.016] ...filename = singleimage.pkg.xml
[  0.016] Loading programmer
[  0.016] ...filename = programmer.elf
[  0.016] Sending programmer
[  0.094] Handling things over to programmer
[  0.094] Identifying storage type
[  0.094] Waiting for firehose to get ready
[  3.141] ...UFS
[  3.141] Identifying CPU version
[  3.156] ...MSM8996 3.1
[  3.156] Determining target secure state
[  3.156] ...secure = yes
[  3.266] Configuring device...
[  3.297] Skipping UFS provsioning as target is secure
[  3.297] Configuring device...
[  3.594] Skipping 'setbootablestoragedrive' as target is secure
[  3.594] Flashing GPT...
[  3.594] Flashing partition:0 with gpt_main0.bin
[  3.594] Initializing storage
[  3.828] ...blksz = 4096
[  3.828] ...part  = "SAMSUNG KLUBG4G1CE-B0B1 0800 "
[  4.641] Flashing partition:1 with gpt_main1.bin
[  4.672] Flashing partition:2 with gpt_main2.bin
[  4.703] Flashing partition:3 with gpt_main3.bin
[  4.750] Re-initializing storage...
[  4.750] Initializing storage
[  5.781] Flashing bootloader...
[  5.797] Flashing xbl with xbl.elf
[  5.938] Flashing cmnlib with cmnlib.mbn
[  5.985] Flashing cmnlib64 with cmnlib64.mbn
[  6.047] Flashing prov with prov64.mbn
[  6.094] Flashing aboot with emmc_appsboot.mbn
[  6.188] Flashing keymaster with keymaster.mbn
[  6.250] Flashing rpm with rpm.mbn
[  6.281] Flashing pmic with pmic.elf
[  6.313] Flashing hyp with hyp.mbn
[  6.360] Flashing tz with tz.mbn
[  6.485] Flashing devcfg with devcfg.mbn
[  6.512] Rebooting to fastboot
[  6.528] Waiting for device to disconnect
[  8.535] Total time: 8.535s

 

[benzinerwin]

Hellow everyone,
my moto z also got hard brick.Tried manish's tutorial and I was successful till the end.But my phone even now dead.I will paste the command lines and the responses I got. Thanks

If you had Nougat on before, your bootloader was updated to v91.05. However, the currently available unbrick files contain bootloader files of v91.03. The downgraded bootloader detects that and skips right back into the "9008"-download mode.
I've assembled a package with the current v91.05 bootloader and the most recent partition layout I had at hand, see attachment.

unbrick package with bootloader 91.05 files (timestamp: 2017-01-06 02:58:48, build id: git=MBM-NG-V91.05-0-gd081b7e)

 

[randomthots]

If you had Nougat on before, your bootloader was updated to v91.05. However, the currently available unbrick files contain bootloader files of v91.03. The downgraded bootloader detects that and skips right back into the "9008"-download mode.
I've assembled a package with the current v91.05 bootloader and the most recent partition layout I had at hand, see attachment.

unbrick package with bootloader 91.05 files (timestamp: 2017-01-06 02:58:48, build id: git=MBM-NG-V91.05-0-gd081b7e)

Thanks a lot.
Much appreciated

 

[benzinerwin]

Thanks a lot.
Much appreciated

In case anyone had a more recent stock rom OTA runnning you'd been updated to bootloader version 91.07, requiring the following unbrick files...
unbrick package with bootloader 91.07 files from 25.221.12 OTA,
GPT seq#0008 (timestamp: 2017-03-30 04:41:31, build id: git=MBM-NG-V91.07-0-gd081b7e)

The package was built from the 25.221.12 OTA update package. Not updated items were taken from when last supplied (i.e. 25.11.14). The GPT sequence counter reached #0008.

 

[lanyao1920]

Will this work on z play? I have a XT1635-02 bricked now and I tried with v91.03, v91.05 and v91.07, they all give me output like below.
Do I need specific blankflash file on different phone models / bootloader versions?

From the cmd:

Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 4.006] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.006] Check qboot_log.txt for more details
[ 4.006] Total time: 4.008s
FAILED: qb_flash_singleimage()->sahara_greet_device()->change_mode()->do_hello()->IO error​

In the log:

[ -0.000] Opening device: \\.\COM5
[ 0.002] Detecting device
[ 4.006] ERROR: sahara_greet_device()->change_mode()->do_hello()->IO error
[ 4.006] Check qboot_log.txt for more details
[ 4.006] Total time: 4.008s
[ 4.007]
[ 4.007] qboot version 3.40
[ 4.007]
[ 4.007] DEVICE {
[ 4.007] name = "\\.\COM5",
[ 4.007] flags = "0x64",
[ 4.007] addr = "0x61FE5C",
[ 4.007] api.bnr = "0xFB2920",
[ 4.007] }
[ 4.007]
[ 4.007]
[ 4.007] Backup & Restore {
[ 4.007] num_entries = 0,
[ 4.007] restoring = "false",
[ 4.007] backup_error = "not started",
[ 4.007] restore_error = "not started",
[ 4.007] }
[ 4.007] ​

 

[lozada81]

Hard Brick Moto Z Play
Fellows, I hope you can help me with the Blankflash file for the MZP.

I left it in full brick, I was locating MM and Nougat going down with the script Downgrade and going up with adb sideload and it happened when installing Nougat again.

It should be mentioned that I was with the April patch, I downgraded to MM Brazil patch November, restart and install the apps as always and personalize, then by adb add patch December, restart and reinstalled N but when finished instead of reboot , I chose to boot bootloader and alli brickeo.

All this only with the Bootloader open, no Root or any modification, now it does not turn on anything and if I connect it to the charger or pc only the charging led flashes, when connecting the pc I recognize it as ¨Qualcomm hs-usb qdloader 9008 COM5¨ I used e Blankflash for the bike z and did not finish the process and the 1,2 and 3 dce XDA and neither.

If someone can pass me the Blankflash will thank you, please.

I arrived here:
Blur_Version.25.211.10.addison.retail.en.US - Security April 2017
NPN 25.137-24-1-9

Download here:
Blur_Version.24.221.12.addison.retail.en.US - Security November 2016
MPNS24.104-44-10

Install this:
Blur_Version.24.231.19.addison.retail.en.US - Security December 2016
MPNS24.104-44-16

Then bricke it at the end of the process:
Blur_Version.25.21.2.addison.retail.en.US - Android 7.0 Nougat January 2017
NPN25.137-15.2

By the way a colleague Ali Guzman from the face group I passed this compilation NPN25.137-24-1 with the included blankflash but in the middle of the process notifies me of package error.

I pass the link in case someone serves:
Https://mega.nz/#!nMdEFLxY!4x0BZWr45...anoX16JZv5B5-E

Http://lenovo-forums.ru/files/category/140-moto-z-play/

Here are two archives with blankflash available so far


ATT Channel Software


thank you very much.