[Defy Q&A, Help & Troubleshooting] Proverbs2:
I'm trying to restore a Defy that was hard-bricked by a failed installation of CM11. As I described in this post, the phone shows absolutely no signs of life; neither the screen nor the led light turn on at all, even though I've tried several different fully-charged batteries. The phone will not go into bootloader mode, even if I try to force it by holding power and volume+ while inserting the battery, so I cannot flash an sbf in RSD Lite.

[MENTION=4487948]skeevydude[/MENTION] and [MENTION=4148153]TJKV[/MENTION] suggested that I try using this sbf_flash tool in a Linux environment instead of using RSD Lite in Windows. I gave that a try, and unfortunately the phone still is not detected by the PC. Here's the output from sbf_flash:

ubuntu@ubuntu:~$ chmod +x sbf_flash
ubuntu@ubuntu:~$ ./sbf_flash firmware.sbf
SBF FLASH 1.23 (mbm)
http://opticaldelusion.org

=== firmware.sbf ===
Index[1]: Unexpected chip 32
Index[2]: Unexpected chip 32
Index[3]: Unexpected chip 32
Index[4]: Unexpected chip 32
Index[5]: Unexpected chip 32
Index[6]: Unexpected chip 32
Index[7]: Unexpected chip 32
Index[8]: Unexpected chip 32
Index[9]: Unexpected chip 32
Index[10]: Unexpected chip 32
Index[11]: Unexpected chip 32
Index[12]: Unexpected chip 32
Index[13]: Unexpected chip 32
00: RDL03 0x82000000-0x8204CFFF 4035 AP
01: CG31 0xB0280000-0xB02847FF 9A68 AP
02: CG32 0xC7A00000-0xC7A207FF 4805 AP
03: CG33 0xB2000000-0xB2DC07FF 8BAC AP
04: CG34 0xB0700000-0xB07047FF AB80 AP
05: CG35 0xB1000000-0xB17FFFFF 100C AP
06: CG39 0xB3300000-0xC79C07FF C7E6 AP
07: CG42 0xB0800000-0xB0842FFF 4BB7 AP
08: CG45 0xB0C00000-0xB0F007FF 738D AP
09: CG47 0xB1800000-0xB1FFFFFF 45F0 AP
10: CG53 0xB2F00000-0xB2F007FF FDFF AP
11: CG61 0xB0B00000-0xB0B7FFFF 4A7C AP
12: CG64 0xB0000000-0xB00047FF 85D0 AP
13: CG65 0xB0180000-0xB01847FF 2409 AP

>> waiting for phone:

It just stays on "waiting for phone" forever.

Here's how the brick happened:

After doing a clean install of [MENTION=513620]Quarx[/MENTION]'s February 2nd CM11 build (one of the "autobot" builds), I was no longer able to mount the sdcard, so I tried mounting it in TWRP, but that didn't work. I rebooted and tried again, still without success. Then I removed the original sd card and put in another sd card to see if that would mount. Still no. Then I tried partitioning the sdcard from TWRP. (I had read on some other forum that doing so might help TWRP to mount the sdcard.) When I tried to partition the sdcard, TWRP gave a "failed" message, and I later confirmed on my PC that the files on the sdcard had not been erased. After my attempt to partition the sdcard from TWRP, I was suddenly unable to mount any of the partitions! I powered off the phone (perhaps unwisely), and now it is completely dead: no led light, and nothing on the screen, no matter what I do.

I haven't been able to get the phone into bootloader mode, so I can't flash an sbf with RSD Lite in Windows, nor with sbf_flash in Linux.

When I type "lsusb" in the Linux terminal to see what usb devices are connected, the phone is not listed.

However, when I used USBDeview in Windows to see if anything shows up there, I found something interesting. When I try to force bootloader mode (by removing the battery, then replacing it while holding power and volume+), a device called "Motorola Flash Interface" shows up briefly in USBDeview, then disconnects after about a second. So maybe the phone isn't completely dead after all. Does anyone have any ideas how I can get it to stay connected to the PC (in either Windows or Linux) so I can flash an sbf?

Thanks in advance for any help.