General :: Unbrick Via ADB - Recovery Fails

I believe I have bricked an Alcatel 990 after flashing "cm-7-20121221-UNOFFICIAL-brandy.zip" via CWM.

Here are reasons why I believe it's bricked good and proper ;-P

1/ device boot loops when charging only via usb connection to PC
- 1.1 - device shows android logo - then "Alcatel One Touch Cyanogenmod 7" text/logo
- 1.2 - this loops continuous and never fully boots - output of adb logcat below

2/ when power-up off charge, only "menu", "search" and "back" soft keys illuminate - the screen+backlight stay completely off
- 2.1 - this remains constant until battery pull
- 2.2 - recovery mode via key combos do not work. Period. (no user error - assured!)

3/ when connected via usb during point 2 - there is not feedback from adb logcat - dead as a doorknob
- 3.1 - when boot looping (1.1 above) I get ~2seconds of adb connectivity then device reboots.
- 3.2 - fastboot <options> <commands> does nothing - device stays as "waiting forr device" this is contstant
- 3.3 - adb has better luck - I can invoke adb logcat and this captures log info as below
- 3.4 - adb recovery options fail and device reboots and hangs as on point 2 above
- 3.5 - adb shell shows rooted prompt for 2 seconds when <up/previous command+enter> very quickly repeated keyboard bashing style
- 3.6 - I have invoked "adb shell rm -r /cache/*" and "adb shell recovery --wipe_data - all to no avail in context of unbricking device

Code:
david@1000H:~/Downloads/src/adt-bundle-linux-x86/sdk/platform-tools$ adb logcat
- waiting for device -
--------- beginning of /dev/log/main
I/cm ( 105): Welcome to Android 2.3.7 / CyanogenMod-7-20121221-UNOFFICIAL-brandy
I/cm ( 106): _

[Code] .....

This is replicated on command and is constant. Replicated under slackware/linux and under win7-32bit-ultimate.

Recovery fails to boot so I need some sort of usb 'bridge' to interrupt the boot loop and invoke recovery - or flashall back onto device - but fastboot fails to identify the device/connectivity.