A question about bricked phone (moto g xt1032)
Well okay instead of using recovery, I just followed the command line instructions in the rom zip file which goes as

 &lt;step operation="getvar" var="max-sparse-size" /&gt;
&lt;step operation="oem" var="fb_mode_set" /&gt;
&lt;step operation="flash" partition="aboot" filename="emmc_appsboot.mbn" MD5="7ab4571da9966ecbe0455984ebe5d277" /&gt;
&lt;step operation="reboot-bootloader" /&gt;
&lt;step operation="flash" partition="partition" filename="gpt.bin" MD5="7778bf62e78dd8ed152e2234ba818fb1" /&gt;
&lt;step operation="flash" partition="motoboot" filename="motoboot.img" MD5="b4cb31c6b875dbb13ae2a155ae44e305" /&gt;
&lt;step operation="flash" partition="logo" filename="logo.bin" MD5="187908e994f5b42710d13dbb5126d6d2" /&gt;
&lt;step operation="flash" partition="boot" filename="boot.img" MD5="2a0134f7dca00ab28ca3644febbe6bc7" /&gt;
&lt;step operation="flash" partition="recovery" filename="recovery.img" MD5="25989942e94890fa2ab6e48fc488d569" /&gt;
&lt;step operation="flash" partition="system" filename="" MD5="f6ea25745eab9f8368d5b276811ffa82" /&gt;
&lt;step operation="flash" partition="system" filename="system.img_sparsechunk.1" MD5="d776d764c00627bcb7d0313657297ab4" /&gt;
&lt;step operation="flash" partition="system" filename="system.img_sparsechunk.2" MD5="a17ebd36c45389a139e8f30e56241fa2" /&gt;
&lt;step operation="flash" partition="modem" filename="NON-HLOS.bin" MD5="a964128abc6fa5ac4a253bd105ed6748" /&gt;
&lt;step operation="erase" partition="modemst1" /&gt;
&lt;step operation="erase" partition="modemst2" /&gt;
&lt;step operation="flash" partition="fsg" filename="fsg.mbn" MD5="03d822a8e01a8edee85e12286dcc81ed" /&gt;
&lt;step operation="erase" partition="cache" /&gt;
&lt;step operation="erase" partition="userdata" /&gt;
&lt;step operation="oem" var="fb_mode_clear" /&gt;
&lt;step operation="reboot-bootloader" /&gt;


And the new system was installed suprisingly.