[afjaymo]

I never thought I wouldn't be able to save my TP.... So, this is the first time I've ever requested help to get it back.
About 3 weeks ago I plugged the TP in after a couple of days of no use. I received the (Weak.tga)

I plugged it in to the wall charger as soon as I recieved the message however my cable wasn't making good contact...I never got the normal battery charging symbol (Charging.tga)

I guess the battery didn't want to charge....I ordered new USB cables and plugged it in and then I only got the (NoBatt.tga)

I've left it plugged in with the factory barrel wall charger for days to no avail...
I've tried every button combination. The only button combination that works is HOME+POWER, and it always pops up with the no battery "Question mark of Death" and that only works with the device not plugged into anything.
On a windows box the Home+VolUp+Power button combination, it makes the dinging noise that a device has been added in device manager, but then says the device is not recognizable.
If I attach the device to a linux machine, there is no sign of life when Home+VolUp+Power button combination. I run lsusb and the TP is never displayed in the list.
I've tried running tpdebrick-v004 in 12.04LTS LiveCD from thumdrive. I always get QDL mode not found
Aborting. This of course after Home+VolDown+Power button combination for 30 seconds. I've tried in running tpdebrick-v004 in 13.04 installed on my machine and get the same error.
I have read just about every forum, every post, and I just can't seem to get this stinking TP out of the "Question mark of Death" state.

If anyone out there has any other ideas, please feel free to share them with me.

 

[guard0g]

I never thought I wouldn't be able to save my TP.... So, this is the first time I've ever requested help to get it back.
About 3 weeks ago I plugged the TP in after a couple of days of no use. I received the (Weak.tga)

I plugged it in to the wall charger as soon as I recieved the message however my cable wasn't making good contact...I never got the normal battery charging symbol (Charging.tga)

I guess the battery didn't want to charge....I ordered new USB cables and plugged it in and then I only got the (NoBatt.tga)

I've left it plugged in with the factory barrel wall charger for days to no avail...
I've tried every button combination. The only button combination that works is HOME+POWER, and it always pops up with the no battery "Question mark of Death" and that only works with the device not plugged into anything.
On a windows box the Home+VolUp+Power button combination, it makes the dinging noise that a device has been added in device manager, but then says the device is not recognizable.
If I attach the device to a linux machine, there is no sign of life when Home+VolUp+Power button combination. I run lsusb and the TP is never displayed in the list.
I've tried running tpdebrick-v004 in 12.04LTS LiveCD from thumdrive. I always get QDL mode not found
Aborting. This of course after Home+VolDown+Power button combination for 30 seconds. I've tried in running tpdebrick-v004 in 13.04 installed on my machine and get the same error.
I have read just about every forum, every post, and I just can't seem to get this stinking TP out of the "Question mark of Death" state.

If anyone out there has any other ideas, please feel free to share them with me.

Did you try just running the script with the TP unplugged, and then plugging it in and following the instructions?

Did you test your barrel charger?

 

[Ardegberts]

First I have to say THANKS FOR THIS SOLLUTION!!!

yesterday I debricked my thouchpad 16gb with this tutorial. I already ordered a new battery.

my HP T did not response any more, even after loading for 3 day's it was dead. only when I put it on a usb in a pc the pc say new hardware!

So I take the tutorial and yes you have to click with in the terminal window, and if you have to type cd Download, D= a CAPITAL D! (I realize after 10 minutes)

the hole script run trough my pc-screen till the end (ALL DONE) and then I put the HP T into power. after 15 minutes it Awakes!!!!!!!!!, with the big battery in the middle of the screen I let it on, and wait more. after 30 minutes, my boot screen came on. I select Android, and yes it boots!!!!

still the battery was 1% so I left it loading. after 1 hour my bricked HP T. was back in business!

I already opened the screen for a new battery, but when you did this, your home button does NOT work!! because it is not connected (little pins)

Sorry for my bad English, but I think you understands it

MANY THANKS :emoji_u1f603:

 

[gusleglandeur]

Hi everybody

i'm new in the forum and i never post because my english is very bad

and my level on linuw is very low

i'm looking for a solution for my brick touchpad

i can't use tp debrick i'm think i'm do something wrong

i have a computer on ubuntu 12.04

i 'have install dfu and fast boot

but i have an error :

" Invalid Response: 0e 57 72 69 74 65 20 75 6e 73 75 63 63 65 73 73 66 75 6c 0a
Cannot write file appsboot-moboot.mbn"

i have look in the you web site and i haven't find the answer yet

if you can help me it will be wonderfull

thanks you

poste1@poste1-System-Product-Name:~/Téléchargements/tpdebrick-v004$ sudo ./tpdebrick 64
checking doc files ...
Requesting SoftwareVersion...
Version: PBL_DloadVER1.0
Requesting Params...
Params: 06 01 01 00 90 00 00
Uploading file 'emmcbld.bin' to QDLOAD...
Writing 1024 bytes to 0x2a000000; 164996 bytes left.
Writing 1024 bytes to 0x2a000400; 163972 bytes left.
Writing 1024 bytes to 0x2a000800; 162948 bytes left.
Writing 1024 bytes to 0x2a000c00; 161924 bytes left.
Writing 1024 bytes to 0x2a001000; 160900 bytes left.
Writing 1024 bytes to 0x2a001400; 159876 bytes left.
Writing 1024 bytes to 0x2a001800; 158852 bytes left.
Writing 1024 bytes to 0x2a001c00; 157828 bytes left.
Writing 1024 bytes to 0x2a002000; 156804 bytes left.
Writing 1024 bytes to 0x2a002400; 155780 bytes left.
Writing 1024 bytes to 0x2a002800; 154756 bytes left.
Writing 1024 bytes to 0x2a002c00; 153732 bytes left.
Writing 1024 bytes to 0x2a003000; 152708 bytes left.
Writing 1024 bytes to 0x2a003400; 151684 bytes left.
Writing 1024 bytes to 0x2a003800; 150660 bytes left.
Writing 1024 bytes to 0x2a003c00; 149636 bytes left.
Writing 1024 bytes to 0x2a004000; 148612 bytes left.
Writing 1024 bytes to 0x2a004400; 147588 bytes left.
Writing 1024 bytes to 0x2a004800; 146564 bytes left.
Writing 1024 bytes to 0x2a004c00; 145540 bytes left.
Writing 1024 bytes to 0x2a005000; 144516 bytes left.
Writing 1024 bytes to 0x2a005400; 143492 bytes left.
Writing 1024 bytes to 0x2a005800; 142468 bytes left.
Writing 1024 bytes to 0x2a005c00; 141444 bytes left.
Writing 1024 bytes to 0x2a006000; 140420 bytes left.
Writing 1024 bytes to 0x2a006400; 139396 bytes left.
Writing 1024 bytes to 0x2a006800; 138372 bytes left.
Writing 1024 bytes to 0x2a006c00; 137348 bytes left.
Writing 1024 bytes to 0x2a007000; 136324 bytes left.
Writing 1024 bytes to 0x2a007400; 135300 bytes left.
Writing 1024 bytes to 0x2a007800; 134276 bytes left.
Writing 1024 bytes to 0x2a007c00; 133252 bytes left.
Writing 1024 bytes to 0x2a008000; 132228 bytes left.
Writing 1024 bytes to 0x2a008400; 131204 bytes left.
Writing 1024 bytes to 0x2a008800; 130180 bytes left.
Writing 1024 bytes to 0x2a008c00; 129156 bytes left.
Writing 1024 bytes to 0x2a009000; 128132 bytes left.
Writing 1024 bytes to 0x2a009400; 127108 bytes left.
Writing 1024 bytes to 0x2a009800; 126084 bytes left.
Writing 1024 bytes to 0x2a009c00; 125060 bytes left.
Writing 1024 bytes to 0x2a00a000; 124036 bytes left.
Writing 1024 bytes to 0x2a00a400; 123012 bytes left.
Writing 1024 bytes to 0x2a00a800; 121988 bytes left.
Writing 1024 bytes to 0x2a00ac00; 120964 bytes left.
Writing 1024 bytes to 0x2a00b000; 119940 bytes left.
Writing 1024 bytes to 0x2a00b400; 118916 bytes left.
Writing 1024 bytes to 0x2a00b800; 117892 bytes left.
Writing 1024 bytes to 0x2a00bc00; 116868 bytes left.
Writing 1024 bytes to 0x2a00c000; 115844 bytes left.
Writing 1024 bytes to 0x2a00c400; 114820 bytes left.
Writing 1024 bytes to 0x2a00c800; 113796 bytes left.
Writing 1024 bytes to 0x2a00cc00; 112772 bytes left.
Writing 1024 bytes to 0x2a00d000; 111748 bytes left.
Writing 1024 bytes to 0x2a00d400; 110724 bytes left.
Writing 1024 bytes to 0x2a00d800; 109700 bytes left.
Writing 1024 bytes to 0x2a00dc00; 108676 bytes left.
Writing 1024 bytes to 0x2a00e000; 107652 bytes left.
Writing 1024 bytes to 0x2a00e400; 106628 bytes left.
Writing 1024 bytes to 0x2a00e800; 105604 bytes left.
Writing 1024 bytes to 0x2a00ec00; 104580 bytes left.
Writing 1024 bytes to 0x2a00f000; 103556 bytes left.
Writing 1024 bytes to 0x2a00f400; 102532 bytes left.
Writing 1024 bytes to 0x2a00f800; 101508 bytes left.
Writing 1024 bytes to 0x2a00fc00; 100484 bytes left.
Writing 1024 bytes to 0x2a010000; 99460 bytes left.
Writing 1024 bytes to 0x2a010400; 98436 bytes left.
Writing 1024 bytes to 0x2a010800; 97412 bytes left.
Writing 1024 bytes to 0x2a010c00; 96388 bytes left.
Writing 1024 bytes to 0x2a011000; 95364 bytes left.
Writing 1024 bytes to 0x2a011400; 94340 bytes left.
Writing 1024 bytes to 0x2a011800; 93316 bytes left.
Writing 1024 bytes to 0x2a011c00; 92292 bytes left.
Writing 1024 bytes to 0x2a012000; 91268 bytes left.
Writing 1024 bytes to 0x2a012400; 90244 bytes left.
Writing 1024 bytes to 0x2a012800; 89220 bytes left.
Writing 1024 bytes to 0x2a012c00; 88196 bytes left.
Writing 1024 bytes to 0x2a013000; 87172 bytes left.
Writing 1024 bytes to 0x2a013400; 86148 bytes left.
Writing 1024 bytes to 0x2a013800; 85124 bytes left.
Writing 1024 bytes to 0x2a013c00; 84100 bytes left.
Writing 1024 bytes to 0x2a014000; 83076 bytes left.
Writing 1024 bytes to 0x2a014400; 82052 bytes left.
Writing 1024 bytes to 0x2a014800; 81028 bytes left.
Writing 1024 bytes to 0x2a014c00; 80004 bytes left.
Writing 1024 bytes to 0x2a015000; 78980 bytes left.
Writing 1024 bytes to 0x2a015400; 77956 bytes left.
Writing 1024 bytes to 0x2a015800; 76932 bytes left.
Writing 1024 bytes to 0x2a015c00; 75908 bytes left.
Writing 1024 bytes to 0x2a016000; 74884 bytes left.
Writing 1024 bytes to 0x2a016400; 73860 bytes left.
Writing 1024 bytes to 0x2a016800; 72836 bytes left.
Writing 1024 bytes to 0x2a016c00; 71812 bytes left.
Writing 1024 bytes to 0x2a017000; 70788 bytes left.
Writing 1024 bytes to 0x2a017400; 69764 bytes left.
Writing 1024 bytes to 0x2a017800; 68740 bytes left.
Writing 1024 bytes to 0x2a017c00; 67716 bytes left.
Writing 1024 bytes to 0x2a018000; 66692 bytes left.
Writing 1024 bytes to 0x2a018400; 65668 bytes left.
Writing 1024 bytes to 0x2a018800; 64644 bytes left.
Writing 1024 bytes to 0x2a018c00; 63620 bytes left.
Writing 1024 bytes to 0x2a019000; 62596 bytes left.
Writing 1024 bytes to 0x2a019400; 61572 bytes left.
Writing 1024 bytes to 0x2a019800; 60548 bytes left.
Writing 1024 bytes to 0x2a019c00; 59524 bytes left.
Writing 1024 bytes to 0x2a01a000; 58500 bytes left.
Writing 1024 bytes to 0x2a01a400; 57476 bytes left.
Writing 1024 bytes to 0x2a01a800; 56452 bytes left.
Writing 1024 bytes to 0x2a01ac00; 55428 bytes left.
Writing 1024 bytes to 0x2a01b000; 54404 bytes left.
Writing 1024 bytes to 0x2a01b400; 53380 bytes left.
Writing 1024 bytes to 0x2a01b800; 52356 bytes left.
Writing 1024 bytes to 0x2a01bc00; 51332 bytes left.
Writing 1024 bytes to 0x2a01c000; 50308 bytes left.
Writing 1024 bytes to 0x2a01c400; 49284 bytes left.
Writing 1024 bytes to 0x2a01c800; 48260 bytes left.
Writing 1024 bytes to 0x2a01cc00; 47236 bytes left.
Writing 1024 bytes to 0x2a01d000; 46212 bytes left.
Writing 1024 bytes to 0x2a01d400; 45188 bytes left.
Writing 1024 bytes to 0x2a01d800; 44164 bytes left.
Writing 1024 bytes to 0x2a01dc00; 43140 bytes left.
Writing 1024 bytes to 0x2a01e000; 42116 bytes left.
Writing 1024 bytes to 0x2a01e400; 41092 bytes left.
Writing 1024 bytes to 0x2a01e800; 40068 bytes left.
Writing 1024 bytes to 0x2a01ec00; 39044 bytes left.
Writing 1024 bytes to 0x2a01f000; 38020 bytes left.
Writing 1024 bytes to 0x2a01f400; 36996 bytes left.
Writing 1024 bytes to 0x2a01f800; 35972 bytes left.
Writing 1024 bytes to 0x2a01fc00; 34948 bytes left.
Writing 1024 bytes to 0x2a020000; 33924 bytes left.
Writing 1024 bytes to 0x2a020400; 32900 bytes left.
Writing 1024 bytes to 0x2a020800; 31876 bytes left.
Writing 1024 bytes to 0x2a020c00; 30852 bytes left.
Writing 1024 bytes to 0x2a021000; 29828 bytes left.
Writing 1024 bytes to 0x2a021400; 28804 bytes left.
Writing 1024 bytes to 0x2a021800; 27780 bytes left.
Writing 1024 bytes to 0x2a021c00; 26756 bytes left.
Writing 1024 bytes to 0x2a022000; 25732 bytes left.
Writing 1024 bytes to 0x2a022400; 24708 bytes left.
Writing 1024 bytes to 0x2a022800; 23684 bytes left.
Writing 1024 bytes to 0x2a022c00; 22660 bytes left.
Writing 1024 bytes to 0x2a023000; 21636 bytes left.
Writing 1024 bytes to 0x2a023400; 20612 bytes left.
Writing 1024 bytes to 0x2a023800; 19588 bytes left.
Writing 1024 bytes to 0x2a023c00; 18564 bytes left.
Writing 1024 bytes to 0x2a024000; 17540 bytes left.
Writing 1024 bytes to 0x2a024400; 16516 bytes left.
Writing 1024 bytes to 0x2a024800; 15492 bytes left.
Writing 1024 bytes to 0x2a024c00; 14468 bytes left.
Writing 1024 bytes to 0x2a025000; 13444 bytes left.
Writing 1024 bytes to 0x2a025400; 12420 bytes left.
Writing 1024 bytes to 0x2a025800; 11396 bytes left.
Writing 1024 bytes to 0x2a025c00; 10372 bytes left.
Writing 1024 bytes to 0x2a026000; 9348 bytes left.
Writing 1024 bytes to 0x2a026400; 8324 bytes left.
Writing 1024 bytes to 0x2a026800; 7300 bytes left.
Writing 1024 bytes to 0x2a026c00; 6276 bytes left.
Writing 1024 bytes to 0x2a027000; 5252 bytes left.
Writing 1024 bytes to 0x2a027400; 4228 bytes left.
Writing 1024 bytes to 0x2a027800; 3204 bytes left.
Writing 1024 bytes to 0x2a027c00; 2180 bytes left.
Writing 1024 bytes to 0x2a028000; 1156 bytes left.
Writing 1024 bytes to 0x2a028400; 132 bytes left.
Writing 132 bytes to 0x2a028800; 0 bytes left.
Executing file...
Checking QDL mode...
Writing file tz.mbn ...
Sending MAGIC...
MSG: Qfprom Fuse List: Blowing FAILED
MSG: Failed Fuse addr:
MSG: 0x00000000
MSG: Error Status:
MSG: 0x00000000
Sending secureMode...
Sending openMulti ...
Uploading file 'tz.mbn'...
Writing 1024 bytes to 0x18000000; 97896 bytes left.
Response: ACK 0x18000000 (outstanding: 0)
Writing 1024 bytes to 0x18000400; 96872 bytes left.
Response: ACK 0x18000400 (outstanding: 0)
Writing 1024 bytes to 0x18000800; 95848 bytes left.
Response: ACK 0x18000800 (outstanding: 0)
Writing 1024 bytes to 0x18000c00; 94824 bytes left.
Response: ACK 0x18000c00 (outstanding: 0)
Writing 1024 bytes to 0x18001000; 93800 bytes left.
Response: ACK 0x18001000 (outstanding: 0)
Writing 1024 bytes to 0x18001400; 92776 bytes left.
Response: ACK 0x18001400 (outstanding: 0)
Writing 1024 bytes to 0x18001800; 91752 bytes left.
Response: ACK 0x18001800 (outstanding: 0)
Writing 1024 bytes to 0x18001c00; 90728 bytes left.
Response: ACK 0x18001c00 (outstanding: 0)
Writing 1024 bytes to 0x18002000; 89704 bytes left.
Response: ACK 0x18002000 (outstanding: 0)
Writing 1024 bytes to 0x18002400; 88680 bytes left.
Response: ACK 0x18002400 (outstanding: 0)
Writing 1024 bytes to 0x18002800; 87656 bytes left.
Response: ACK 0x18002800 (outstanding: 0)
Writing 1024 bytes to 0x18002c00; 86632 bytes left.
Response: ACK 0x18002c00 (outstanding: 0)
Writing 1024 bytes to 0x18003000; 85608 bytes left.
Response: ACK 0x18003000 (outstanding: 0)
Writing 1024 bytes to 0x18003400; 84584 bytes left.
Response: ACK 0x18003400 (outstanding: 0)
Writing 1024 bytes to 0x18003800; 83560 bytes left.
Response: ACK 0x18003800 (outstanding: 0)
Writing 1024 bytes to 0x18003c00; 82536 bytes left.
Response: ACK 0x18003c00 (outstanding: 0)
Writing 1024 bytes to 0x18004000; 81512 bytes left.
Response: ACK 0x18004000 (outstanding: 0)
Writing 1024 bytes to 0x18004400; 80488 bytes left.
Response: ACK 0x18004400 (outstanding: 0)
Writing 1024 bytes to 0x18004800; 79464 bytes left.
Response: ACK 0x18004800 (outstanding: 0)
Writing 1024 bytes to 0x18004c00; 78440 bytes left.
Response: ACK 0x18004c00 (outstanding: 0)
Writing 1024 bytes to 0x18005000; 77416 bytes left.
Response: ACK 0x18005000 (outstanding: 0)
Writing 1024 bytes to 0x18005400; 76392 bytes left.
Response: ACK 0x18005400 (outstanding: 0)
Writing 1024 bytes to 0x18005800; 75368 bytes left.
Response: ACK 0x18005800 (outstanding: 0)
Writing 1024 bytes to 0x18005c00; 74344 bytes left.
Response: ACK 0x18005c00 (outstanding: 0)
Writing 1024 bytes to 0x18006000; 73320 bytes left.
Response: ACK 0x18006000 (outstanding: 0)
Writing 1024 bytes to 0x18006400; 72296 bytes left.
Response: ACK 0x18006400 (outstanding: 0)
Writing 1024 bytes to 0x18006800; 71272 bytes left.
Response: ACK 0x18006800 (outstanding: 0)
Writing 1024 bytes to 0x18006c00; 70248 bytes left.
Response: ACK 0x18006c00 (outstanding: 0)
Writing 1024 bytes to 0x18007000; 69224 bytes left.
Response: ACK 0x18007000 (outstanding: 0)
Writing 1024 bytes to 0x18007400; 68200 bytes left.
Response: ACK 0x18007400 (outstanding: 0)
Writing 1024 bytes to 0x18007800; 67176 bytes left.
Response: ACK 0x18007800 (outstanding: 0)
Writing 1024 bytes to 0x18007c00; 66152 bytes left.
Response: ACK 0x18007c00 (outstanding: 0)
Writing 1024 bytes to 0x18008000; 65128 bytes left.
Response: ACK 0x18008000 (outstanding: 0)
Writing 1024 bytes to 0x18008400; 64104 bytes left.
Response: ACK 0x18008400 (outstanding: 0)
Writing 1024 bytes to 0x18008800; 63080 bytes left.
Response: ACK 0x18008800 (outstanding: 0)
Writing 1024 bytes to 0x18008c00; 62056 bytes left.
Response: ACK 0x18008c00 (outstanding: 0)
Writing 1024 bytes to 0x18009000; 61032 bytes left.
Response: ACK 0x18009000 (outstanding: 0)
Writing 1024 bytes to 0x18009400; 60008 bytes left.
Response: ACK 0x18009400 (outstanding: 0)
Writing 1024 bytes to 0x18009800; 58984 bytes left.
Response: ACK 0x18009800 (outstanding: 0)
Writing 1024 bytes to 0x18009c00; 57960 bytes left.
Response: ACK 0x18009c00 (outstanding: 0)
Writing 1024 bytes to 0x1800a000; 56936 bytes left.
Response: ACK 0x1800a000 (outstanding: 0)
Writing 1024 bytes to 0x1800a400; 55912 bytes left.
Response: ACK 0x1800a400 (outstanding: 0)
Writing 1024 bytes to 0x1800a800; 54888 bytes left.
Response: ACK 0x1800a800 (outstanding: 0)
Writing 1024 bytes to 0x1800ac00; 53864 bytes left.
Response: ACK 0x1800ac00 (outstanding: 0)
Writing 1024 bytes to 0x1800b000; 52840 bytes left.
Response: ACK 0x1800b000 (outstanding: 0)
Writing 1024 bytes to 0x1800b400; 51816 bytes left.
Response: ACK 0x1800b400 (outstanding: 0)
Writing 1024 bytes to 0x1800b800; 50792 bytes left.
Response: ACK 0x1800b800 (outstanding: 0)
Writing 1024 bytes to 0x1800bc00; 49768 bytes left.
Response: ACK 0x1800bc00 (outstanding: 0)
Writing 1024 bytes to 0x1800c000; 48744 bytes left.
Response: ACK 0x1800c000 (outstanding: 0)
Writing 1024 bytes to 0x1800c400; 47720 bytes left.
Response: ACK 0x1800c400 (outstanding: 0)
Writing 1024 bytes to 0x1800c800; 46696 bytes left.
Response: ACK 0x1800c800 (outstanding: 0)
Writing 1024 bytes to 0x1800cc00; 45672 bytes left.
Response: ACK 0x1800cc00 (outstanding: 0)
Writing 1024 bytes to 0x1800d000; 44648 bytes left.
Response: ACK 0x1800d000 (outstanding: 0)
Writing 1024 bytes to 0x1800d400; 43624 bytes left.
Response: ACK 0x1800d400 (outstanding: 0)
Writing 1024 bytes to 0x1800d800; 42600 bytes left.
Response: ACK 0x1800d800 (outstanding: 0)
Writing 1024 bytes to 0x1800dc00; 41576 bytes left.
Response: ACK 0x1800dc00 (outstanding: 0)
Writing 1024 bytes to 0x1800e000; 40552 bytes left.
Response: ACK 0x1800e000 (outstanding: 0)
Writing 1024 bytes to 0x1800e400; 39528 bytes left.
Response: ACK 0x1800e400 (outstanding: 0)
Writing 1024 bytes to 0x1800e800; 38504 bytes left.
Response: ACK 0x1800e800 (outstanding: 0)
Writing 1024 bytes to 0x1800ec00; 37480 bytes left.
Response: ACK 0x1800ec00 (outstanding: 0)
Writing 1024 bytes to 0x1800f000; 36456 bytes left.
Response: ACK 0x1800f000 (outstanding: 0)
Writing 1024 bytes to 0x1800f400; 35432 bytes left.
Response: ACK 0x1800f400 (outstanding: 0)
Writing 1024 bytes to 0x1800f800; 34408 bytes left.
Response: ACK 0x1800f800 (outstanding: 0)
Writing 1024 bytes to 0x1800fc00; 33384 bytes left.
Response: ACK 0x1800fc00 (outstanding: 0)
Writing 1024 bytes to 0x18010000; 32360 bytes left.
Response: ACK 0x18010000 (outstanding: 0)
Writing 1024 bytes to 0x18010400; 31336 bytes left.
Response: ACK 0x18010400 (outstanding: 0)
Writing 1024 bytes to 0x18010800; 30312 bytes left.
Response: ACK 0x18010800 (outstanding: 0)
Writing 1024 bytes to 0x18010c00; 29288 bytes left.
Response: ACK 0x18010c00 (outstanding: 0)
Writing 1024 bytes to 0x18011000; 28264 bytes left.
Response: ACK 0x18011000 (outstanding: 0)
Writing 1024 bytes to 0x18011400; 27240 bytes left.
Response: ACK 0x18011400 (outstanding: 0)
Writing 1024 bytes to 0x18011800; 26216 bytes left.
Response: ACK 0x18011800 (outstanding: 0)
Writing 1024 bytes to 0x18011c00; 25192 bytes left.
Response: ACK 0x18011c00 (outstanding: 0)
Writing 1024 bytes to 0x18012000; 24168 bytes left.
Response: ACK 0x18012000 (outstanding: 0)
Writing 1024 bytes to 0x18012400; 23144 bytes left.
Response: ACK 0x18012400 (outstanding: 0)
Writing 1024 bytes to 0x18012800; 22120 bytes left.
Response: ACK 0x18012800 (outstanding: 0)
Writing 1024 bytes to 0x18012c00; 21096 bytes left.
Response: ACK 0x18012c00 (outstanding: 0)
Writing 1024 bytes to 0x18013000; 20072 bytes left.
Response: ACK 0x18013000 (outstanding: 0)
Writing 1024 bytes to 0x18013400; 19048 bytes left.
Response: ACK 0x18013400 (outstanding: 0)
Writing 1024 bytes to 0x18013800; 18024 bytes left.
Response: ACK 0x18013800 (outstanding: 0)
Writing 1024 bytes to 0x18013c00; 17000 bytes left.
Response: ACK 0x18013c00 (outstanding: 0)
Writing 1024 bytes to 0x18014000; 15976 bytes left.
Response: ACK 0x18014000 (outstanding: 0)
Writing 1024 bytes to 0x18014400; 14952 bytes left.
Response: ACK 0x18014400 (outstanding: 0)
Writing 1024 bytes to 0x18014800; 13928 bytes left.
Response: ACK 0x18014800 (outstanding: 0)
Writing 1024 bytes to 0x18014c00; 12904 bytes left.
Response: ACK 0x18014c00 (outstanding: 0)
Writing 1024 bytes to 0x18015000; 11880 bytes left.
Response: ACK 0x18015000 (outstanding: 0)
Writing 1024 bytes to 0x18015400; 10856 bytes left.
Response: ACK 0x18015400 (outstanding: 0)
Writing 1024 bytes to 0x18015800; 9832 bytes left.
Response: ACK 0x18015800 (outstanding: 0)
Writing 1024 bytes to 0x18015c00; 8808 bytes left.
Response: ACK 0x18015c00 (outstanding: 0)
Writing 1024 bytes to 0x18016000; 7784 bytes left.
Response: ACK 0x18016000 (outstanding: 0)
Writing 1024 bytes to 0x18016400; 6760 bytes left.
Response: ACK 0x18016400 (outstanding: 0)
Writing 1024 bytes to 0x18016800; 5736 bytes left.
Response: ACK 0x18016800 (outstanding: 0)
Writing 1024 bytes to 0x18016c00; 4712 bytes left.
Response: ACK 0x18016c00 (outstanding: 0)
Writing 1024 bytes to 0x18017000; 3688 bytes left.
Response: ACK 0x18017000 (outstanding: 0)
Writing 1024 bytes to 0x18017400; 2664 bytes left.
Response: ACK 0x18017400 (outstanding: 0)
Writing 1024 bytes to 0x18017800; 1640 bytes left.
Response: ACK 0x18017800 (outstanding: 0)
Writing 1024 bytes to 0x18017c00; 616 bytes left.
Response: ACK 0x18017c00 (outstanding: 0)
Writing 616 bytes to 0x18018000; 0 bytes left.
Response: ACK 0x18018000 (outstanding: 0)
Sending CloseFlush...
Writing file appsboot-moboot.mbn ...
Sending MAGIC...
Sending secureMode...
Sending openMulti ...
Uploading file 'appsboot-moboot.mbn'...
Writing 1024 bytes to 0x10000000; 77944 bytes left.
Response: ACK 0x10000000 (outstanding: 0)
Writing 1024 bytes to 0x10000400; 76920 bytes left.
Response: ACK 0x10000400 (outstanding: 0)
Writing 1024 bytes to 0x10000800; 75896 bytes left.
Response: ACK 0x10000800 (outstanding: 0)
Writing 1024 bytes to 0x10000c00; 74872 bytes left.
Response: ACK 0x10000c00 (outstanding: 0)
Writing 1024 bytes to 0x10001000; 73848 bytes left.
Response: ACK 0x10001000 (outstanding: 0)
Writing 1024 bytes to 0x10001400; 72824 bytes left.
Response: ACK 0x10001400 (outstanding: 0)
Writing 1024 bytes to 0x10001800; 71800 bytes left.
Response: ACK 0x10001800 (outstanding: 0)
Writing 1024 bytes to 0x10001c00; 70776 bytes left.
Response: ACK 0x10001c00 (outstanding: 0)
Writing 1024 bytes to 0x10002000; 69752 bytes left.
Invalid Response: 0e 57 72 69 74 65 20 75 6e 73 75 63 63 65 73 73 66 75 6c 0a
Cannot write file appsboot-moboot.mbn
Aborted.

Thank you for your help and idea

 

[ElGuache]

Ok, I went through all the steps and it worked all the way through. I place the tablet to charge and the home botton light up. Then the battery picture with the lighting came up later. After that the "hp" sign came up and stay like that for the rest of the time that I had it charge, 24 hours so far. I unpluged it and tried to reset it, because the "hp" sign is still on and it doesn't turn off. I did the power+home+down bottons for 30 second and it reseted, but it went back to the "hp" sign again. My android start up doesn't show up, just the "hp" sign and it hangs there.

Some help please.

 

[topher67]

Ok, I went through all the steps and it worked all the way through. I place the tablet to charge and the home botton light up. Then the battery picture with the lighting came up later. After that the "hp" sign came up and stay like that for the rest of the time that I had it charge, 24 hours so far. I unpluged it and tried to reset it, because the "hp" sign is still on and it doesn't turn off. I did the power+home+down bottons for 30 second and it reseted, but it went back to the "hp" sign again. My android start up doesn't show up, just the "hp" sign and it hangs there.

Some help please.

Hi, follow the instructions on this page http://forum.xda-developers.com/showthread.php?t=1426244 and you'll be fine.

Cheers

 

[Dryphter]

I believe my Touchpad is beyond hope. Tried everything I could find online - even ripped it apart and took the battery out. DEAD.

Doesn't even try to turn on, just a black screen. Tpdebrick always returns 'QDL mode not found'

So I think the battery is completely fried and its honestly not worth the cost of a new battery. Guess it'll be parts for the other TP incase one of the kids cracks the screen or something. Off to Samsung Galaxy Tab land for me, or an iPad...

 

[guard0g]

I believe my Touchpad is beyond hope. Tried everything I could find online - even ripped it apart and took the battery out. DEAD.

Doesn't even try to turn on, just a black screen. Tpdebrick always returns 'QDL mode not found'

So I think the battery is completely fried and its honestly not worth the cost of a new battery. Guess it'll be parts for the other TP incase one of the kids cracks the screen or something. Off to Samsung Galaxy Tab land for me, or an iPad...

Plug the TP into Ubuntu, and then enter the "lsusb" command in an xterm window. Then hold Pwr-Home-Vol down at the same time for 35 sec and type the "lsusb" command again in the xterm window. Do you see an entry with "Qualcomm, Inc. Gobi Wireless Model (QDL mode)"? "Palm, Inc."?

 

[Dryphter]

Hi guard0g -

Tried the above suggestion and the only things listed are a webcam (which is built into the laptop), Kingston Technology (which is the thumb drive I am running Linux off of ) and 4 entries for Linux Foundation root hub.

 

[DebbyW]

Thank you for all your work on this problem! My Touchpad was down for about 4 weeks. Finally got up enough guts to create a Ubuntu LiveCD and try this process. It worked for me, and I have never used linux before. I joined this forum just to say thank you and let you know it solved my problem.

 

[nevertells]

Thank you for all your work on this problem! My Touchpad was down for about 4 weeks. Finally got up enough guts to create a Ubuntu LiveCD and try this process. It worked for me, and I have never used linux before. I joined this forum just to say thank you and let you know it solved my problem.

Now learn how to flash the A6 firmware, pay attention to your battery levels and practice good battery housekeeping.

 

[AndroidLover]

NT, does one really need to flash A6 firmware again after successfully running the TPDebrick script?

 

[petur]

Since I'm stuck at the multi error (together with many others), I was thinking of poking the flash chip a bit with a long stick, aka trying to hack emmcbld.bin to do slightly other things []

I've already discovered

http://pastebin.com/GiaNnufE

(emmcbld.h)

and the fact that the binary isn't protected (I can alter a string with hex editor and it just runs fine).

Is this a route that has been tried before?

 

[Dvigilante1]

Since I'm stuck at the multi error (together with many others), I was thinking of poking the flash chip a bit with a long stick, aka trying to hack emmcbld.bin to do slightly other things []I've already discovered http://pastebin.com/GiaNnufE(emmcbld.h)and the fact that the binary isn't protected (I can alter a string with hex editor and it just runs fine).Is this a route that has been tried before?

Youre the first I heard attempting to do that. So did changing emmcbld get tpdebrick to get past multi error?

 

[petur]

So did changing emmcbld get tpdebrick to get past multi error?

No not at all... right now I just checked that an altered binary runs fine (changed some strings), and attempted to RE the binary (but not much of a success and I hardly spent time on it).

But my idea was that maybe we could alter this file to do more its best to open/program the flash chip. This binary is actually just a flash programmer which is fed files, and the multi error is just telling us that it failed to open the flash device. So a bit of diagnostics and other tricks might help us

I was surprised to find the header file, would be even better if I could find the rest of the sources

 

[freecicero]

Please give us some hope Petur! As you know, there are many multi-error owners who are otherwise hopeless!!

 

[Dryphter]

Holy crapola!

Previously I couldn't get past 'QDL not found' so I ordered a new battery and slapped it into my wife's dead TP. Question Mark Battery!! Ran tbdebrick and....

BINGO was his name-o! TP now turns on, but I think the digitizer came unplugged while re-assembling as the touchscreen doesn't work. But at least it booted into CM.

Take apart one more time, fix the digitzer and we are back in business.

I added Automateit with a rule to shut down at 20% to hopefully keep it from happening again.

jcsullins is truly a wizard when it comes to this stuff.

 

[nevertells]

NT, does one really need to flash A6 firmware again after successfully running the TPDebrick script?

If one's A6 firmware becomes corrupted once, what to say it can't become corrupted again? Are you willing to risk bricking your TouchPad over something as simple is flashing the A6 firmware once in a while? I'm not!

 

[AndroidLover]

NT, maybe you misunderstood me...

Of course it will not damage the Touchpad to flash it over and over again (until you don't do it several thousand times). But in my opinion bricking the Touchpad is an effect of - lets call it - "bad" circumstances like low batt or anything else. It's NOT an effect of "aging" bits and bytes which can or have to be refreshed by flashing over and over again.

So the only thing one should remind himself of is to avoid getting the low bat situation as one main reason for corrupting the flash. As you said: Pay attention to your battery level. As long as you do that, I think - and never had the need for flashing again - you will not get a corrupt flash again. At least I can confirm to not have to flash the firmware more than once after having bricked a Touchpad (and debricked them with TPdebrick 0.4). Statistically 0 of 12 Touchpads were bricked again when keeping an eye on the battery level not going lower than 15%.

Only my 2 cents and experience of the last 2 years...

 

[petur]

Please give us some hope Petur! As you know, there are many multi-error owners who are otherwise hopeless!!

I wish! I wish...

Meanwhile, I also found a header file related to the protocol here: http://pastebin.com/UASWJWyw