09/06/2016, 10:01 PM
If you Google "tpdebrick open multi failed" you'll see that the general concensus in the Android community is that this indicates some kind of flash memory failure. It can't be written to, so tpdebrick will never work, at least no one has been able to get it to work.
And to my understanding, if you can get tpdebrick to start at all, that means the battery is charging just fine.
When the flash drive is corrupted, the TouchPad can't load webOS or bootie the bootloader, it can't display any of the "charge battery" icons - nothing. The screen is completely dark, even though the device is on. It's on and the CPU by default is in a mode where it's waiting to download firmware to write to the flash drive. But there is no visual indication on the screen that it's in this mode.
If you plug it into a USB port, it will appear on the PC as some kind of device named qdl-dload or something. Or, when you follow the instructions for tpdebrick, the script detects when you reset the TouchPad and manually put it in this mode, the script proceeds with feeding the TouchPad the firmware files to write to the flash, and the script logs this to the screen.
Maybe one day, we'll be able to do a flash transplant and rescue a TouchPad in this condition, but we can't do it yet.