[General Questions and Answers] Droidriven:
Is the device recognized by PC? If not, what is device manager labeling the device as?

If it connects to PC and is recognized you can.........

Use adb to clear cache and dalvik/ART cache, then see if the device will boot to recovery or fastboot, if not then power the device off and remove the battery then reinsert the battery(if it has a removable battery). Then leave the device off and connect it to PC then open a adb terminal and type:

adb reboot bootloader (press enter, sometimes the deamon has to start, if nothing happens then type adb reboot bootloader a second time, some devices can be booted from a powered off state with adb)

If that doesn't work try typing:

adb reboot fastboot (press enter).

If none of that works to boot fastboot then try turning the device on, when it gets to the logo, connect the device to PC, open a adb terminal and type:

adb devices (press enter, if it returns a serial number the device is recognized)

Then type:

adb reboot bootloader (press enter and it may boot to fastboot)

Or type:

adb reboot fastboot (press enter)

Or type:

reboot fastboot (press enter)

If none of that gets you to fastboot and you can't boot it manually with the buttons then you're bricked, its not hardbricked though because it boots to logo so that means bootloader is at least there even if it is corrupted and whether anything else is there or works or not.

Whatever you flashed must have had some differences in partitions that flashed over your partitions in places that weren't correct for your device, its more than just the software not being for your device, it is structured completely different than your device.

You've got to get to fastboot someway to flash the stock firmware, that's the only thing I see being able to correct your partitions and put the .imgs in the places they are meant to go.

There is also the possibility that you can download your stock firmware, then extract the kernel(Zimage, its sometimes bundled with/called boot.img or recovery.img, depending on device and android version), the boot.img, the recovery.img and the system.img and then do some research on your device model number and find out which partition(mmcblk0) each of those imgs go in(I could tell you how to use adb to find the partitions but that wouldn't help if flashing the wrong things has screwed up their placements). Then, if adb is working with the device you can use the dd command to manually push the boot.img to its mmcblk0, the recovery.img to its mmcblk0 and the system.img to its mmcblk0.

I would start with dd-ing the recovery, then seeing if it will boot to recovery, if the recovery is a custom recovery and you have a nandroid backup or a correct ROM zip, try restoring or flashing. If it doesn't then dd the boot.img to its mmcblk0 and see if it boots to recovery, if not, dd the system.img to its mmcblk0, you can repeat this process with each of the .imgs in your stock firmware. Maybe if you can push enough to the device it will restore some functionality that will allow you to get booted to a state will allow you to completely reflash the device.

If the confused you then I might have confused myself typing it, lol.