[Moto G General] DigitalRegen:
Moto G Stuck in Boot Loop! Help

When I flash the stock firmware I keep getting these error messages

(bootloader) Invalid signed image

(bootloader) Preflash validation failed

(bootloader) Failed to validate sparse image

and these all end with

FAILED (remote failure)

target reported max download size of 536870912 bytes

sending 'partition' (32 KB)...

OKAY [ 0.035s]

writing 'partition'...

(bootloader) This may take a few seconds, if a

(bootloader) different partition table is being

(bootloader) flashed since we need to backup

(bootloader) and restore a few partitions

(bootloader) Flashing primary GPT image...

(bootloader) Flashing backup GPT image...

OKAY [ 0.448s]

finished. total time: 0.486s

target reported max download size of 536870912 bytes

sending 'motoboot' (1940 KB)...

OKAY [ 0.111s]

writing 'motoboot'...

(bootloader) flashing tz ...

(bootloader) flashing rpm ...

(bootloader) flashing sdi ...

(bootloader) flashing aboot ...

(bootloader) flashing sbl1 ...

OKAY [ 1.490s]

finished. total time: 1.603s

rebooting into bootloader...

OKAY [ 0.004s]

finished. total time: 0.005s

target reported max download size of 536870912 bytes

sending 'boot' (10240 KB)...

OKAY [ 0.361s]

writing 'boot'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.915s

target reported max download size of 536870912 bytes

sending 'recovery' (10240 KB)...

OKAY [ 0.372s]

writing 'recovery'...

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 0.948s

target reported max download size of 536870912 bytes

sending 'system' (260606 KB)...

OKAY [ 8.415s]

writing 'system'...

(bootloader) Invalid signed image

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 8.950s

target reported max download size of 536870912 bytes

sending 'system' (239692 KB)...

OKAY [ 7.770s]

writing 'system'...

OKAY [ 9.293s]

finished. total time: 17.065s

target reported max download size of 536870912 bytes

sending 'system' (222205 KB)...

OKAY [ 7.165s]

writing 'system'...

(bootloader) Failed to validate sparse image

(bootloader) Preflash validation failed

FAILED (remote failure)

finished. total time: 19.684s

target reported max download size of 536870912 bytes

sending 'modem' (47484 KB)...

OKAY [ 1.583s]

writing 'modem'...

OKAY [ 1.304s]

finished. total time: 2.890s

erasing 'modemst1'...

OKAY [ 0.066s]

finished. total time: 0.067s

erasing 'modemst2'...

OKAY [ 0.067s]

finished. total time: 0.068s

target reported max download size of 536870912 bytes

sending 'fsg' (721 KB)...

OKAY [ 0.125s]

writing 'fsg'...

OKAY [ 0.104s]

finished. total time: 0.231s

erasing 'cache'...

OKAY [ 0.362s]

finished. total time: 0.364s

erasing 'userdata'...

OKAY [ 2.560s]

finished. total time: 2.562s

I have tried to flash many different firmwares on it to get it out of the boot loop like "US Retail" (4.3 and 4.4.2), "Boost US" (4.3 and 4.4.2), and "Verizon US" (4.3 and 4.4.2). This always results in one of the 3 error messages or more. I have found the one that works with the least error messages is the Boost US firmware for 4.4.2 and it gives only the error message (bootloader) Failed to validate sparse image on the 3rd system file. Whenever I try to install the firmware it doesn't seem to work, and it results in the phone turning on with the Motorola logo then the phone vibrates once then turns off and repeats, or the phone shows the android logo on its back with the exclamation point after the single vibration and sits like that until it turns off a few minutes later repeating the process. I have tried everything including trying to boot normally, resetting to factory, going into recovery and wiping cache and deleting all data, and even attempting to install from ADB. I have actually successfully done this process before a few hours before trying it on this one where it ended up like this. I looked this up and apparently you can still fix the phone if it can reach the boot loader screen, but when I was working with the phone I forgot to put it in developer mode and turn on USB debugging so that might be an issue. If there is a way I could fix it that would be very helpful, but if it doesn't I can still return the phone in the next 4 days.

Thanks for the help!

Extra Info:

The phone's bootloader is locked and because it is new I do not have any backups.

Also I already have these following programs

Minimal ADB and Fastboot

RSD Lite

DFS

Mfastboot v2

r1-motog-modifiedrecoveryroot.zip

adt-bundle-windows-x86_64-20140321.zip

platform-tools.zip

Fastboot+ADB(20926).zip

adbfix.zip

These are all from other threads that have explained this issue but the fix they provided did not work.

Thanks Again!