Significant advances have been made in the last week. Access to a TP GO 's eMMC partitions and its filesystem data has been acheived by installing a temporary bootloader using QPST. Previously, the device appeared to be dead, couldn't be booted into recovery mode, wouldn't load and connect using novacom, novaterm ,WOSQI or or anything. It would only connect in qualcomm download mode (QHUSB_DLOAD)
There's more work to be done. A basic (minimum) understanding of linux storage device configuration, linux commands, webOS and windows is necessary. One incorrect keystroke or missed step could render the device inaccessable and / or truly bricked, useful only as the paperweight you previously thought it was.
- Here is a link to a webOSnation thread located in the Pre 3 forum here where members have also been collaberating and working on a fix for this.
Dead Pre 3 (QHUSB-DLOAD mode)
- The post and thread the next link points to is located on xda and there's documents and files you can use to install a temporary bootloader onto a MSM8660 device in order to gain access to its sdcard (filesystems) for partition recreation and restoral of backups and/or factory provided eMMC images. I advise reading through the thread. There's some links scattered throughout it pointing to a few other threads on xda where people have been independently working on fixing this problem too. The MSM8660 is a widely used chipset fouind in many devices.
[JTAG,BRICK]SHV-E160L Korean model - Page 9 - xda-developers
For our dead webOS devices, the process after we install a temporary bootloader is to boot the device from it, then recreate the rest of the partition table / partition information.
After that we'd restore data to the the bootie partition and to the two other partitions bootie uses to chain boot the device.
In theory, once those three partitions are restored and readable , it should be possible to boot the device into recovery mode for doctoring.