MOTO G XT1032 Unable to Flash Any ROM >> Bricked

[bill010]

MOTO G XT1032 hab check errorrs
Hi,

Iam facing a difficulty flashing any ROM on my Moto G
Soft Bricked
XT1032
Unable to get into Recovery(Gets stuck at Motorola Boot Logo if recovery is selected, same happens when any rom is flashed) however able to access fastboot
RSD Lite does not work
Tried a few roms
i get habcheck errors for boot and recovery while entering the commands
eventually phone gets to the motorola logo and goes into a blank blue screen >>BRICKED
Can anybody help me

Commands where i encounter habcheck errors are>>

mfastboot flash boot boot.img
mfastboot flash recovery recovery.img

GETVAR ALL RESULTS >>
F:\G\mfastboot-v2\mfastboot-v2>mfastboot.exe getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 4113
(bootloader) product: falcon
(bootloader) secure: yes
(bootloader) hwrev: 0x83C0
(bootloader) radio: 0x1
(bootloader) emmc: 16GB Sandisk REV=06 PRV=07 TYPE=17
(bootloader) ram: 1024MB Hynix S4 SDRAM DIE=4Gb
(bootloader) cpu: MSM8226 CS
(bootloader) serialno: TA89003TA0
(bootloader) cid: 0x0007
(bootloader) channelid: 0x00
(bootloader) uid: 129CEC010F000000000000000000
(bootloader) unlocked: yes
(bootloader) iswarrantyvoid: yes
(bootloader) mot_sst: 3
(bootloader) max-download-size: 536870912
(bootloader) reason: Volume down key pressed
(bootloader) imei:
(bootloader) meid:
(bootloader) date:
(bootloader) sku:
(bootloader) iccid:
(bootloader) cust_md5:
(bootloader) max-sparse-size: 268435456
(bootloader) current-time: "Tue Jun 14 2:56:12 UTC 2016"
(bootloader) ro.build.fingerprint[0]: motorola/falcon_vffrsl/falcon_umts
(bootloader) ro.build.fingerprint[1]: :4.4.4/KXB21.14-L1.40/36:user/rele
(bootloader) ro.build.fingerprint[2]: ase-keys
(bootloader) ro.build.version.full[0]: Blur_Version.210.12.40.falcon_umt
(bootloader) ro.build.version.full[1]: s.SFRSL.en.FR
(bootloader) ro.build.version.qcom[0]: AU_LINUX_ANDROID_LNX.LA.3.5.1_RB1
(bootloader) ro.build.version.qcom[1]: .04.04.02.048.020
(bootloader) version-baseband:
(bootloader) kernel.version[0]: Linux version 3.4.42-gb89c9dd ([email protected]
(bootloader) kernel.version[1]: ilclbld32) (gcc version 4.7 (GCC) ) #1 S
(bootloader) kernel.version[2]: MP PREEMPT Fri Jun 20 02:19:14 CDT 2014
(bootloader) sdi.git: git=MBM-NG-V41.13-0-gdc5aeaf
(bootloader) sbl1.git: git=MBM-NG-V41.13-0-g683cb0c
(bootloader) rpm.git: git=MBM-NG-V41.13-0-g71b1aae
(bootloader) tz.git: git=MBM-NG-V41.13-0-ga27c415
(bootloader) aboot.git: git=MBM-NG-V41.13-0-g7dc8e78
(bootloader) qe: qe 0/1
(bootloader) ro.carrier: unknown
all: listed above
finished. total time: 0.061s

 

[_3psilon_]

As you can see my issue is very similar, but if you look around in recent topics, you see several phones having the same symptoms.

I'm 90% sure that it's hardware failure in my case and maybe the memory chips are reaching the end of their (short) lifetime these months...