Database Info

Hard Bricked Moto G Dual SIM (XT1033)

I recently flashing AOSP kernel from Nexus 5 experience, and suddenly when i go to fastboot it hard bricked (does not boot anymore). But it detected at PC.
Unforunately, i cant get it work with unbrick tool,
it says :
i get this weird error and cant find it anywhere
Code:
D:\Desktop\MBM-CI_4.4.4>qboot.exe blank-flash
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM10
opening device: \\.\COM10
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
OKAY [ 0.004s]
identifying device
Unexpected packet: 4. Was expecting: 14
FAILED (blank-flash:sahara-chip-stat:unexpected packet)
D:\Desktop\MBM-CI_4.4.4>
sometimes it show this
Code:
D:\Desktop\MBM-CI_4.4.4>qboot.exe blank-flash
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.005s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM10
OKAY [ 0.005s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
and i cant find that error message (sahara / greet-device) in this forum. anyone can help me?

anyone can help me? :crying:

same problem
i have the same problem but with moto g, did you found a solution?

do you solve it, i just met the same problem.
http://forum.xda-developers.com/moto-g/help/hard-bricked-trying-to-update-to-4-4-4-t2926071

[Q] hard bricked after trying to update to 4.4.4 and can't get into fastboot

My phone is xt1032 in us retail 4.4.3, rooted and installed cwm & xposed, then i try to update to 4.4.4 yesterday, after restart i remember it shows "invalid ..." and in the end it looks like finished and let me choose reinstall su yes or no, i clicked Yes, then it's totally broken.
I read http://forum.xda-developers.com/showthread.php?t=2623587, http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798, and tried all the methods mentioned in these posts, just can't get into fastboot, fail at blank-flash every time.
These are error logs:
Code:
C:\Users\Administrator\Desktop\a\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.016s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
C:\Users\Administrator\Desktop\a\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM4
OKAY [ 0.062s]
greeting device for command mode
ReadFile() failed, error=995
opening device: \\.\COM4
OKAY [ 0.016s]
greeting device for command mode
ReadFile() failed, error=995
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.109s]
identifying device
Unexpected packet: 4. Was expecting: 14
FAILED (blank-flash:sahara-chip-stat:unexpected packet)
Help please & thanks in advance

megayu said:
My phone is xt1032 in us retail 4.4.3, rooted and installed cwm & xposed, then i try to update to 4.4.4 yesterday, after restart i remember it shows "invalid ..." and in the end it looks like finished and let me choose reinstall su yes or no, i clicked Yes, then it's totally broken.
I read http://forum.xda-developers.com/showthread.php?t=2623587, http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798, and tried all the methods mentioned in these posts, just can't get into fastboot, fail at blank-flash every time.
These are error logs:
Code:
C:\Users\Administrator\Desktop\a\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.016s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
C:\Users\Administrator\Desktop\a\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM4
OKAY [ 0.062s]
greeting device for command mode
ReadFile() failed, error=995
opening device: \\.\COM4
OKAY [ 0.016s]
greeting device for command mode
ReadFile() failed, error=995
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.109s]
identifying device
Unexpected packet: 4. Was expecting: 14
FAILED (blank-flash:sahara-chip-stat:unexpected packet)
Help please & thanks in advance
Click to expand...
Click to collapse
A common problem by a lot of people here... You need to use 4.4.3 blankflash.. But Yeah that one isn't available. If 4.4.4 doens't work also I suggest you to wait for the Android 5.0 blankflash

megayu said:
My phone is xt1032 in us retail 4.4.3, rooted and installed cwm & xposed, then i try to update to 4.4.4 yesterday, after restart i remember it shows "invalid ..." and in the end it looks like finished and let me choose reinstall su yes or no, i clicked Yes, then it's totally broken.
I read http://forum.xda-developers.com/showthread.php?t=2623587, http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798, and tried all the methods mentioned in these posts, just can't get into fastboot, fail at blank-flash every time.
These are error logs:
Code:
C:\Users\Administrator\Desktop\a\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.016s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
C:\Users\Administrator\Desktop\a\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM4
OKAY [ 0.062s]
greeting device for command mode
ReadFile() failed, error=995
opening device: \\.\COM4
OKAY [ 0.016s]
greeting device for command mode
ReadFile() failed, error=995
opening device: \\.\COM4
OKAY [ -0.000s]
greeting device for command mode
opening device: \\.\COM4
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.109s]
identifying device
Unexpected packet: 4. Was expecting: 14
FAILED (blank-flash:sahara-chip-stat:unexpected packet)
Help please & thanks in advance
Click to expand...
Click to collapse
I have identical problem and identical blank-flash errors

same problem here also

Some solution? Please
binom-music said:
I have identical problem and identical blank-flash errors
Click to expand...
Click to collapse
I have this problem pls help.
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM11
OKAY [ 0.001s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM11
OKAY [ 0.001s]
greeting device for command mode
ReadFile() failed, error=31
opening device: \\.\COM11
OKAY [ 0.001s]
greeting device for command mode
ReadFile() failed, error=31
FAILED (blank-flash:greet-device:error reading packet)

[Q] Blank flash problems.

Hi, hope somebody can help me.
First, I am no expert, so this will have to be help for dummies!
I have flashed lots of phones and unbricked a few following instructions on this site, but this has me beaten. A friend just got into flashing and tried to flash his moto G XT1032 to lollipop, very unsuccessfully. He wanted to do it himself
so I pointed him in the direction of this excellent site. Note his phone could enter fastboot at the time, unlocked (code 3 etc). He downloaded all the stuff, including Oversleeper's tools and...ran them including the bootloader refresher!! There is now no fastboot and the phone is bricked. I have managed to get to the stage where the phone is recognised as Qualcomm MS-USB QDLoader 9008 (COM8), but when I try to blank flash, the end line says "Error reading packet" and fails. I have looked all over on XDA for a solution but can't seem to find one. I know there are some absolute wizards on this site, so please somebody help? I can't give up. I don't know the meaning of the word!
Thank you all so much.
Gareth J

According to oversleeper's post, it says "The bricker should be used very carefully and only on Android 4.4.4 with 41.13 bootloader. DO NOT use it on higher versions, unless you wanna kill your phone definitively."
Is it possible that the phone has a 41.18 bootloader?

audit13 said:
According to oversleeper's post, it says "The bricker should be used very carefully and only on Android 4.4.4 with 41.13 bootloader. DO NOT use it on higher versions, unless you wanna kill your phone definitively."
Is it possible that the phone has a 41.18 bootloader?
Click to expand...
Click to collapse
It is possible but I really don't know. I got it in a very sorry state. I suppose there is hope in the fact that it can still be detected and seen as Qualcomm etc. Does there need to be an unpacked firmware in the same folder as the batch file or something? I can't understand the "error reading packet" statement. The only tool that he said he ran was the refresher tool. Goodness knows why, when he had the phone in fastboot mode ready for flashing a ROM.

garethjames said:
It is possible but I really don't know. I got it in a very sorry state. I suppose there is hope in the fact that it can still be detected and seen as Qualcomm etc. Does there need to be an unpacked firmware in the same folder as the batch file or something? I can't understand the "error reading packet" statement. The only tool that he said he ran was the refresher tool. Goodness knows why, when he had the phone in fastboot mode ready for flashing a ROM.
Click to expand...
Click to collapse
have you used motoflasher???

motorola.lover1998 said:
have you used motoflasher???
Click to expand...
Click to collapse
I haven't, no. Do you think it will work? Ah I think you need bootloader which this device does not have now. That's why I was trying to use blank flash.

garethjames said:
I haven't, no. Do you think it will work? Ah I think you need bootloader which this device does not have now. That's why I was trying to use blank flash.
Click to expand...
Click to collapse
you should use it its the same thing as blankflash but it also has 4.4.2,4.3 options

motorola.lover1998 said:
you should use it its the same thing as blankflash but it also has 4.4.2,4.3 options
Click to expand...
Click to collapse
I'll give it a try. Thanks. Will post back.

garethjames said:
I'll give it a try. Thanks. Will post back.
Click to expand...
Click to collapse
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.006s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: FAILED (blank-flash:greet-device:error reading packet)
OUTPUT:
OUTPUT:
This is the problem I have. Absolutely no idea what it means! "your MBM-CI dont match with your bootloader version, use another MBM-CI version."
Thanks

garethjames said:
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.006s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: FAILED (blank-flash:greet-device:error reading packet)
OUTPUT:
OUTPUT:
This is the problem I have. Absolutely no idea what it means! "your MBM-CI dont match with your bootloader version, use another MBM-CI version."
Thanks
Click to expand...
Click to collapse
hold the power button until the notification light blinks then post back
---------- Post added at 06:41 AM ---------- Previous post was at 06:37 AM ----------
use it with other versions if your using motoflasher

I think you are in the same boat as me my friend. If you have attempted, or your friend has attempted to flash lollipop, then your bootloader will now be 41.18, so there is currently no fix. As I understand it, and I may be wrong, the current blankflash will not work to run a singleimage.bin on the 41.18 bootoader and a newer blankflash version is required to get us out of this fix. It's a waiting game currently. I am following the progress of another thread waiting to see when this occurs.

Same with me
garethjames said:
SYSTEM: Device Selected: Moto G v1, Android 4.4.4
**** BOOTLOADER FLASHING STARTED: ****
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.006s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.001s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: opening device: \\.\COM8
OUTPUT: OKAY [ 0.002s]
OUTPUT: greeting device for command mode
OUTPUT: FAILED (blank-flash:greet-device:error reading packet)
OUTPUT:
OUTPUT:
This is the problem I have. Absolutely no idea what it means! "your MBM-CI dont match with your bootloader version, use another MBM-CI version."
Thanks
Click to expand...
Click to collapse
Same with me .Pl.help .

debakumarc2 said:
Same with me .Pl.help .
Click to expand...
Click to collapse
We cant help at the moment because there isnt a newer blankflash so we have to wait until leaked 5.0.1 firmwares come.. my device is also bricked i know what you feel bro :'(

Thanks.
I will wait. Pl.inform , if any hope ASAP. Thanks.

disconnect battery
I had similiar Problem inspite of correct bootloader 41.13. I could indeed blank flash only with disconnected battery.
1) Disconnect battery
2) Start blankflash.bat and quickly! insert usb cable - If you are not quick enough the batch process has finished before connection is established. Just retry!
3) After successful completed blankflash process, reconnect battery
4) Now the smartphone should be in fastboot mode.
5) If fastboot shows "low battery" disconnect and reconnect usb cable.

iacklink said:
I had similiar Problem inspite of correct bootloader 41.13. I could indeed blank flash only with disconnected battery.
1) Disconnect battery
2) Start blankflash.bat and quickly! insert usb cable - If you are not quick enough the batch process has finished before connection is established. Just retry!
3) After successful completed blankflash process, reconnect battery
4) Now the smartphone should be in fastboot mode.
5) If fastboot shows "low battery" disconnect and reconnect usb cable.
Click to expand...
Click to collapse
Why you had to use the bankflash tool? Because of upgrade from kitkat to lolipop?

disconnect battery
No, it was because of an interrupted flash process. My computer crashed during flashing stock rom. Thereafter the phone could not started anymore (even no LED when connected to power supply or PC).

Blank-flash
iacklink said:
No, it was because of an interrupted flash process. My computer crashed during flashing stock rom. Thereafter the phone could not started anymore (even no LED when connected to power supply or PC).
Click to expand...
Click to collapse
Came back to see if any new developments anywhere with regard to this problem. Read this, but unfortunately the battery can't be removed.

Same problem, any news please?

Same Problem
Hi all,
I was Flash my Moto G 1033 to Stock Firmware Android 4.4.4 Kitkat by Ushing ADB Recovery from Stock recovery.
it was Completed Installation. but when i Select Reboot System Now. Then After it will not Boot system as well as Not Boot Into boot-loader.
Please Brothers Help me.
i also Tried Blank-Flash tool but getting same problem as Above.
Please Give me Only idea to Install Only Boot-Loader Then After i will Install Full System only need Boot-loader.
Please help me all I m Very Sad About it. and i have only one phone, and That is Bricked, Now what can i do ?

I read This problem somewhere before thats why i never downgrade to kitkat, hope someone came with good news
Ps from what i read its safe to downgrade to 5.0 or 5.1

[Q] Moto G shown as Qualcomm HS-USB QDLoader 9008 (COM6)

Hey,
I have a huge problem with my phone right now. When I made a software update from 4.4.2 to 4.4.4 my phone shutted down while being in recovery and installing the new software. It shutted down, because the battery was low.
So now if I connect my phone to my computer, my computer detects it as Qualcomm HS-USB QDLoader 9008 (COM6).
I already tried this: http://forum.xda-developers.com/moto-g/help/how-to-revive-hard-bricked-moto-g-t2833798
But when I open the flash-blank.bat I get this message: FAILED (blank-flash:greet-device:error reading packet)
The whole log:
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.002s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
opening device: \\.\COM6
OKAY [ 0.001s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
Is there any hope to get it back to life?

Did you try This
Hit THANKS if I helped you!

@LasseWolpmann00 after you blank-flash you should be able to flash Stock ROM via fastboot

I'm having the same problems,. I think it has something to do with the MBM-CI of Lollipop.

I flash XT1032 Firmware on my XT1031 device,and It's on 9008 mode(QHSUSB_BULK),and i try this,It failed!
Code:
C:\Users\Andy\Desktop\blankflash\blankflash>qboot.exe blank-flash
opening device: \\.\COM10
OKAY [ 0.000s]
greeting device for command mode
OKAY [ 0.016s]
identifying device
...serial = 0x34F16F6
...chip-id = 0x801 (MSM8626)
...chip-rev = 0x0
...sv-sbl = 0x0
OKAY [ 0.016s]
finding files
...programmer = programmer_8626.mbn
...singleimage = singleimage_8626.bin
OKAY [ -0.000s]
validating files
OKAY [ 0.016s]
switching to download mode
OKAY [ -0.000s]
greeting device for image downloading
OKAY [ -0.000s]
sending programmer
OKAY [ 0.016s]
flashing singleimage
FAILED (blank-flash:sdl-transfer-image:sdl-hello:invalid HDLC frame)
:crying::crying::crying:.Who can help me?

My phone XT1033 bricked(showing as RELINK HS QDLOADER 9008 (COM11) in device manager

:crying::crying::crying::crying:
I have moto g 1st Gen XT1033 and it got hard bricked when I tried to reinstall Lolipop 5.1 (Now understood a wrong file for this phone). From then the device wont start, wont boot into boot loader mode, wont do anything. I tried many things which are suggested on internet but nothing worked. For now, if I long press power on button, LED flashes and nothing after that. Please help me in getting back my device into life. I tried doing a blank flash but getting below message
F:\sanjay phone\blankflash\blankflash>.\qboot.exe blank-flash
opening device: \\.\COM11
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.004s]
greeting device for command mode
opening device: \\.\COM11
OKAY [ 0.003s]
greeting device for command mode
FAILED (blank-flash:greet-device:error reading packet)
F:\sanjay phone\blankflash\blankflash>pause
Press any key to continue . . .
I TRIED DISCONNECTING THE BATTERY AND CHARGING AND TRYING TO RE CONNECT AGAIN BUT THAT DIDN'T WORK TOO.
PLEASE HELP :crying::crying::crying::crying::crying:

please reply
can someone please reply. If this cant be repaired, I will stop looking for solution at least.
:crying::crying::crying::crying:

sanjayuv said:
can someone please reply. If this cant be repaired, I will stop looking for solution at least.
:crying::crying::crying::crying:
Click to expand...
Click to collapse
replacing the motherboard(which costs more than the cost of a smartphone currently) of your device is the solution other than that nothing can be done

sanjayuv said:
can someone please reply. If this cant be repaired, I will stop looking for solution at least.
:crying::crying::crying::crying:
Click to expand...
Click to collapse
no solution yet founf for for the bootloader of android 5.0 ..... I am facing same error and have been waiting for 1 month

wellcome in moto g hardbricked club
sign here
https://secure.avaaz.org/es/petitio..._completo_de_Android_5_para_Moto_G_2013/?copy

Reply
I have kept my moto g safe in locker and got xiomi note 3. If anyone find solution to this, do let me know