[Q] Hard Bricked (qhsusb_bulk) XT1072 (Moto G - 4G LTE 2nd gen )

Hi everyone,
My brother has a Motorola XT1072 (Moto G - 4G LTE 2nd Gen) and he has bricked the device. He was playing with fastboot...
So, currently he has a totally dead phone (can't boot, no LED when charging, etc.)
When I plug the device to my computer, the only thing I see is that it's detected as qhusb_bulk (under windows and before the driver installation) and as Bus 001 Device 014: ID 05c6:9008 Qualcomm, Inc. Gobi Wireless Modem (QDL mode) (under linux with a lsusb).

I finally found a solution to a similar problem : http://forum.xda-developers.com/moto...oto-g-t2833798
So I tried qboot on Linux and Windows, and always failed with the same error : FAILED (blank-flash:greet-device:unexpected packet).

Qboot is detecting my device :

Code:

---

[root@rincevent blankflash]# ./qboot devices
/dev/ttyUSB0        "QCOM emergency download"

---

But when I try a blank flash, it doesn't work :

Code:

---

[root@rincevent blankflash]# ./qboot blank-flash --debug=2
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - No data from serial, retrying...
D - No data from serial, retrying...
D - No data from serial, retrying...
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - No data from serial, retrying...
D - No data from serial, retrying...
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - No data from serial, retrying...
D - No data from serial, retrying...
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
I - opening device: /dev/ttyUSB0
I - OKAY [  0.000s]
I - greeting device for command mode
D - Receiving HELLO packet
D - No data from serial, retrying...
D - No data from serial, retrying...
D - Dumping 16 bytes read
D - 00000000  04 00 00 00 10 00 00 00  0d 00 00 00 01 00 00 00  |................|
E - Unexpected packet: 4. Was expecting: 1
FAILED (blank-flash:greet-device:unexpected packet)

---

And my qboot.ini :

Code:

---

# MSM8626
[config 0x801]
  programmer=programmer_8626.mbn
  singleimage=singleimage_8626.bin
[config 0x805]
  programmer=programmer_8926.mbn
  singleimage=singleimage_8926.bin

[diag error.0x0001090D]
  count=5
  message="blank-flash:greet-device:error reading packet"
  last-seen="Sat Oct 24 16:48:18 2015, CEST"
  first-seen="Sat Oct 24 16:15:24 2015, CEST"
  chip=
  chip.sn=0x0
  chip.id=0x0
  chip.rev=0
  chip.sv-sbl=0
  qboot.version=2.4
  hostname=rincevent
[diag blank-flash]
  fail=5
  pass=0
  yield=0.00%
  dphu=100.00

---

Conclusion : qboot is detecting my device but can't flash it. They don't speak the same language :'(

My Goal : Reinstall Flashboot on my device

Now, I'm only guessing, and will take any advice which could help me.

--> I suppose that I need a newer version of qboot, or at least a newer version of programmer.mbn and singleimage.bin

--> I've found this repository, which aims to ease qboot usage : https://gitlab.com/Negan1911/motofla...er/MotoFlasher
There is a repository inside, with many qboot version : https://gitlab.com/Negan1911/motofla...sher/Component
I don't understand what are falcon and ghost, how this guy found this files, etc.

I'm a bit lost, here are some question :

• I can't find any other qboot version. Is it a leak ? or community made ?


• What are falcon_444, falcon_50, ghost, ... ? What is the code name of my phone ?


• How do I know which version of programmer.mbn and singleimage.bin I need ? And what is the number : programmer_8926.mbn; programmer_8626.mbn


• Can someone with a XT1072 can rip programmer.mbn and singleimage.bin for me ?


• Are programmer.mbn and singleimage.bin are community made ? Or is it a leak ?


• Can I use another tool (other than qboot) to communicate with my device (this "QCOM emergency download") ? Is there a specification somewhere to understand how it works ?


• Is my previous android version important ? Why ? Fastboot is changing between android version ? I read somewhere that's encrypted, isn't it ?


• Could I use a tool like emmc_recover[y] and how ? http://forum.xda-developers.com/show...&postcount=249 or https://github.com/Fuses/emmc_recover

Thanks by advance for your help,
Please be comprehensive if I've forgotten a rule of this board, I'll do my best to correct this post if necessary.