[Help][SOLVED] is my moto z dead? (Brick) - Moto Z Questions & Answers

My moto z got stucked in the famous Qualcomm 9008 Emergency mode. How i bricked my moto z? Or maybe would be better say, how Motorola did brick my moto z?
Yes I'm blaming motorola for this, and i have some good motivations for this.
I'll tell you the complete story of my brick.
I was having some trouble on oreo due to a failed root, so just came back to 7.1.1 and i was trying to go to oreo again by installing ota after ota. Actually i was able to install something about 4 or 5 otas before the boom. After the last ota the phone just turned off and after a couple of hours I noticed that the phone was detected as Qualcomm 9008 in Windows device manager.
Here the story get very interesting.
In fact i firstly tried to flash many blankflash files without success, seems like my moto z wasn't happy with them.
After some searching I discovered those QFIL files wich should help me out with completely reflash my moto z.
There was only one problem, Motorola didn't release the complete QFIL rom (for economic motivations i think).
So my situation is this
I have the .elf file releated to the moto z but I can't generate the rawprogram0.xml and the patch0.xml files (both contains infos about partitions).
But why I can't generate those files?
Simply because thos files are extracted from the GPTmain0.bin files (or something like that) contained in the QFIL rom, that isn't released by motorola.
You see why I'm blaming motorola now?
1)No direct factory for oreo (or at least i didn't find it)
2)this seems like a common moto z family (moto z play too have got this) problem, I've seen other people around here with the same problem, some of them have fixed this mess but some other like me no.
3)No QFIL rom, i mean, come on guys...EVEN XIAOMI RELEASES them. I understand that if a company releases this kind of files then all the fixing center would have less crying people with broken/bricked devices but come on, it's a shame.
I'm trying to get my moto z back to live from 2 weeks now, I think it's time to stop and ask for help.
If I've said something wrong and motorola have released the QFIL rom then I'm asking sorry but i didn't find them (in this case please post a link to it below)
If someone know how to extract rawprogram0.xml and patch0.xml files from the normal 7.1.1 factory then write how here please.
EDIT(MOTO Z IS BACK):
i've restored my phone thanks to an oreo based blankflash (and thanks to @The Marionette)
here is the link and the short guide on how to do that: https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
BUT, right after the blank flash flash your phone will have the bootloader locked, and you will not be able to unlock it since there is no partition table inside it.
so how can you restore your moto z?
dowload the factory in the link and then in the terminal use this command
fastboot flash partition gpt.bin
ok now you are ready for RSD lite, flash everything trough it.
Hope your moto z is back as mine

---

this files?

---

eLaDiio said:
this files?
Click to expand...
Click to collapse
I've never noticed them. Actually I've never checked in the ota packages, so thanks maybe those files can help me even if normally there should be only one gpt main 0.bin, so i don't know how can i merge them and if it's possible

---

I had pretty much the same brick cause and I posted what I did to fix it on the top brick-related thread.
You should check your bootloader version and if it's below version 92.09 or something, you are fine.
And if blankflash won't flash things, it's either your cable, your PC or the fact that the bootloader in the blankflash you used has an older bootloader and you can't flash an older bootloader over the newer one.

---

The Marionette said:
I had pretty much the same brick cause and I posted what I did to fix it on the top brick-related thread.
You should check your bootloader version and if it's below version 92.09 or something, you are fine.
And if blankflash won't flash things, it's either your cable, your PC or the fact that the bootloader in the blankflash you used has an older bootloader and you can't flash an older bootloader over the newer one.
Click to expand...
Click to collapse
Probably i have a newer bootloader then the blank flash one, i want to make a try with the QFIL method, but do you know what should i do to build a blank flash? I mean a blank flash with a newer bootloader (the oreo one)

---

MasterJack1697 said:
Probably i have a newer bootloader then the blank flash one, i want to make a try with the QFIL method, but do you know what should i do to build a blank flash? I mean a blank flash with a newer bootloader (the oreo one)
Click to expand...
Click to collapse
The blankflash mentioned in my post has an Oreo bl as far as I can see.
You need the Oreo firmware( mentioned in my post) and the Oreo OTA ( link available in the Oreo thread ).

---

The Marionette said:
The blankflash mentioned in my post has an Oreo bl as far as I can see.
You need the Oreo firmware( mentioned in my post) and the Oreo OTA ( link available in the Oreo thread ).
Click to expand...
Click to collapse
Can you please give me te link to this blank flash? I can't find the oreo based one

---

MasterJack1697 said:
Can you please give me te link to this blank flash? I can't find the oreo based one
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222

---

The Marionette said:
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
Click to expand...
Click to collapse
i'll try as soon as possible thanks

---

eLaDiio said:
this files?
Click to expand...
Click to collapse
anyway those file are totally useless to me, or at least i don't know how to merge them in one file so i can't use them

---

The Marionette said:
https://forum.xda-developers.com/showpost.php?p=76453284&postcount=222
Click to expand...
Click to collapse
oh god this worked, i'll edit the thread and i'll ad the link to this blank flash

---

MasterJack1697 said:
oh god this worked, i'll edit the thread and i'll ad the link to this blank flash
Click to expand...
Click to collapse
Yeah, you're welcome.

---

Issue with partition table
Thanks for the blankflash, it did work on Moto Z. I was able to get my phone back to recovery mode.
But now i get the below message when i run "fastboot flash partition gpt.bin"
C:\adb>fastboot flash partition gpt.bin
target reported max download size of 536870912 bytes
sending 'partition' (142 KB)...
OKAY [ 0.031s]
writing 'partition'...
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.218s
My phone is still locked and i am using official stock firmware - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
If i try to run other commands, below is the error:
C:\adb>fastboot flash bootloader bootloader.img
target reported max download size of 536870912 bytes
sending 'bootloader' (7792 KB)...
OKAY [ 0.187s]
writing 'bootloader'...
(bootloader) Validating 'bootloader.default.xml'
(bootloader) Invalid partition name xbl
(bootloader) Invalid partition name cmnlib
(bootloader) Invalid partition name cmnlib64
(bootloader) Invalid partition name prov
(bootloader) Invalid partition name aboot
(bootloader) Invalid partition name keymaster
(bootloader) Invalid partition name rpm
(bootloader) Invalid partition name pmic
(bootloader) Invalid partition name hyp
(bootloader) Invalid partition name tz
(bootloader) Invalid partition name devcfg
(bootloader) Cancelling 'bootloader.default.xml'
FAILED (remote failure)
finished. total time: 0.281s
Please see if you can help me to overcome these errors.
Thanks.
MasterJack1697 said:
My moto z got stucked in the famous Qualcomm 9008 Emergency mode. How i bricked my moto z? Or maybe would be better say, how Motorola did brick my moto z?
Yes I'm blaming motorola for this, and i have some good motivations for this.
I'll tell you the complete story of my brick.
I was having some trouble on oreo due to a failed root, so just came back to 7.1.1 and i was trying to go to oreo again by installing ota after ota. Actually i was able to install something about 4 or 5 otas before the boom. After the last ota the phone just turned off and after a couple of hours I noticed that the phone was detected as Qualcomm 9008 in Windows device manager.
Here the story get very interesting.
In fact i firstly tried to flash many blankflash files without success, seems like my moto z wasn't happy with them.
After some searching I discovered those QFIL files wich should help me out with completely reflash my moto z.
There was only one problem, Motorola didn't release the complete QFIL rom (for economic motivations i think).
So my situation is this
I have the .elf file releated to the moto z but I can't generate the rawprogram0.xml and the patch0.xml files (both contains infos about partitions).
But why I can't generate those files?
Simply because thos files are extracted from the GPTmain0.bin files (or something like that) contained in the QFIL rom, that isn't released by motorola.
You see why I'm blaming motorola now?
1)No direct factory for oreo (or at least i didn't find it)
2)this seems like a common moto z family (moto z play too have got this) problem, I've seen other people around here with the same problem, some of them have fixed this mess but some other like me no.
3)No QFIL rom, i mean, come on guys...EVEN XIAOMI RELEASES them. I understand that if a company releases this kind of files then all the fixing center would have less crying people with broken/bricked devices but come on, it's a shame.
I'm trying to get my moto z back to live from 2 weeks now, I think it's time to stop and ask for help.
If I've said something wrong and motorola have released the QFIL rom then I'm asking sorry but i didn't find them (in this case please post a link to it below)
If someone know how to extract rawprogram0.xml and patch0.xml files from the normal 7.1.1 factory then write how here please.
EDIT(MOTO Z IS BACK):
i've restored my phone thanks to an oreo based blankflash (and thanks to @The Marionette)
here is the link and the short guide on how to do that: https://forum.xda-developers.com/showpost.php?p=76310273&postcount=183
BUT, right after the blank flash flash your phone will have the bootloader locked, and you will not be able to unlock it since there is no partition table inside it.
so how can you restore your moto z?
dowload the factory in the link and then in the terminal use this command
fastboot flash partition gpt.bin
ok now you are ready for RSD lite, flash everything trough it.
Hope your moto z is back as mine
Click to expand...
Click to collapse

---

bmskartik said:
(bootloader) Validating 'gpt.default.xml'
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Security version downgrade
(bootloader) Image primary_gpt failed validation
(bootloader) Preflash validation failed
(bootloader) Cancelling 'gpt.default.xml'
FAILED (remote failure)
finished. total time: 0.218s
My phone is still locked and i am using official stock firmware - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml.
Please see if you can help me to overcome these errors.
Thanks.
Click to expand...
Click to collapse
Did you try deducing the output? I think I even mentioned this.

---

Sorry didnt get you. Can you come again.
If you were looking for output from getvar, here it is:
C:\Downloads\XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsi
dy-DEFAULT_regulatory-DEFAULT_CFC.xml>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: moto-msm8996-91.09(*)
(bootloader) product: sheridan
(bootloader) board: sheridan
(bootloader) secure: yes
(bootloader) hwrev: P3B
(bootloader) radio: 2
(bootloader) storage-type: ufs
(bootloader) ufs: 64GB SAMSUNG KLUCG4J1CB-B0B1 FV=0800
(bootloader) ram: 4GB SAMSUNG LP4 DIE=8Gb M5=01 M6=05 M7=00 M8=08
(bootloader) cpu: MSM8996
(bootloader) serialno: 5552ed0g
(bootloader) cid: 0x0000
(bootloader) channelid: 0x00
(bootloader) uid: E778AC6200000000000000000000
(bootloader) securestate: oem_locked
(bootloader) iswarrantyvoid: no
(bootloader) max-download-size: 536870912
(bootloader) reason: Failed to initialize partition table
(bootloader) imei: 000000000000000
(bootloader) meid:
(bootloader) date: 01-01-1970
(bootloader) sku: 000000000000000
(bootloader) battid:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time:
(bootloader) ro.build.fingerprint:
(bootloader) poweroffalarm: 0
(bootloader) ro.build.version.full:
(bootloader) ro.build.version.qcom:
(bootloader) version-baseband:
(bootloader) kernel.version:
(bootloader) xbl.git: xbl.git
(bootloader) rpm.git: rpm.git
(bootloader) tz.git: tz.git
(bootloader) hyp.git: hyp.git
(bootloader) devcfg.git: devcfg.git
(bootloader) keymaster.git: keymaster.git
(bootloader) cmnlib.git: cmnlib.git
(bootloader) cmnlib64.git: cmnlib64.git
(bootloader) prov.git: prov.git
(bootloader) pmic.git: pmic.git
(bootloader) aboot.git: git=MBM-NG-V91.09-0-g7de07a7
(bootloader) qe:
(bootloader) frp-state: no protection (err)
(bootloader) ro.carrier:
all: listed above
finished. total time: 0.140s
The Marionette said:
Did you try deducing the output? I think I even mentioned this.
Click to expand...
Click to collapse

---

bmskartik said:
Sorry didnt get you. Can you come again.
If you were looking for output from getvar, here it is:
Click to expand...
Click to collapse
https://www.merriam-webster.com/dictionary/deduce
You are trying to flash an older bootloader over your current one.

---

Thanks, few questions:
1. How do I find out the bootloader version of the downloaded factory image? In getvar command on my phone, I see 91.09 as my version.
(bootloader) version-bootloader: moto-msm8996-91.09(*)
2. where can I find the latest bootloader version as I have searched a lot and this is the latest image I found for moto z - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
The Marionette said:
You are trying to flash an older bootloader over your current one.
Click to expand...
Click to collapse

---

bmskartik said:
Thanks, few questions:
1. How do I find out the bootloader version of the downloaded factory image? In getvar command on my phone, I see 91.09 as my version.
(bootloader) version-bootloader: moto-msm8996-91.09(*)
2. where can I find the latest bootloader version as I have searched a lot and this is the latest image I found for moto z - XT1650-03_GRIFFIN_RETUS_8.0.0_OPL27.76-51_cid50_subsidy-DEFAULT_regulatory-DEFAULT_CFC.xml
Click to expand...
Click to collapse
One page backwards, I put a link to my post, where I explained everything I did. The OTA or the whole update zip should have the newest bootloader.
Again, I mentioned everything I did there.

---

I did try all the 4 GPT files in the OTA - Blur_Version.27.211.6.griffin.retail.en.US but it failed at gpt_main2.bin installation. Looks like its not accepting the image:
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
FAILED <remote failure>
May be I have to wait for OPLS27.76.51-5 Stock Rom since the phone is still locked.

---

bmskartik said:
I did try all the 4 GPT files in the OTA - Blur_Version.27.211.6.griffin.retail.en.US but it failed at gpt_main2.bin installation. Looks like its not accepting the image:
(bootloader) Flashing primary GPT image...
(bootloader) Flashing backup GPT image...
FAILED <remote failure>
May be I have to wait for OPLS27.76.51-5 Stock Rom since the phone is still locked.
Click to expand...
Click to collapse
Mine did the same, now try flashing the gpt.bin from the whole Oreo firmware, not the OTA.