Android OS Forum banner

TPDebrick v004

833K views 2K replies 483 participants last post by  Woodvale 
#1 · (Edited by Moderator)
tpdebrick v004 by jcsullins
===========================
TPDebrick is a suite of programs and files used to "debrick"
HP Touchpads. This process should allow the revival of Touchpads
that cannot boot due to corrupted raw partitions, corrupted bootloaders
or corrupted A6 firmware. Note that this should allow you to get
into bootie (webOS) recovery mode. Additional steps may be needed
after to restore the bootie configuration or OS (i.e. webOS doctor).

NOTE: If you can hold Power+Home+VolUP for 30 seconds and see a big USB symbol,
then you SHOULD NOT do the following.

NOTE: Before attempting the following,
you should make sure that the failure to boot isn't due to
a faulty USB cable or charger.

NOTE: The following should be considered a LAST RESORT.
If the Touchpad isn't already "bricked",
then the following may very well "brick" it.

NOTE: USE AT YOUR OWN RISK!!!!

TPDebrick has been designed and tested to work with an
Ubuntu 12.04 32-bit livecd (or liveusb). The instructions that follow
assume that you are booting an Ubuntu 12.04 32-bit livecd (or liveusb).

1. Click "Try Ubuntu"
2. Click the Wifi icon in top right of screen
3. Click on your Wifi AP name to establish network connection
4. Enter wifi password, if needed
5. Click Firefox icon on left of screen
6. Download the webOS 3.0.5 doctor from the URL:
http://downloads.codefi.re/jcsullins/webos/doctors/original/webosdoctorp305hstnhwifi.jar
7. Select "Save File"
8. Click OK
9. Download tpdebrick-v004 from the URL:
http://downloads.codefi.re/jcsullins/tpdebrick/tpdebrick-v004.zip
10. Select "Save File"
11. Click OK
12. Wait for downloads to complete
13. Click "Dash Home" (icon in top left corner of screen)
14. Type in "Terminal"
15. Click on the "Terminal" icon
16. Click in the "Terminal" window
17. Run "cd Downloads"
18. Run "unzip tpdebrick-v004"
19. Run "cd tpdebrick-v004"
20. Connect touchpad
21. Hold Power+Home+VolDown buttons on Touchpad for 30 seconds
22. Run "script" (this will capture the output of the tpdebrick process)
23. Run "sudo ./tpdebrick XX" (where XX is the size of the TP: 16, 32 or 64)

The tpdebrick process can take from 5 to 10 minutes (or even more
if you have very slow network connection). It should end with "ALL DONE."
If the process hangs for more than 5 minutes, you can abort the process
by pressing Ctrl-\ (Ctrl key and key with '|' above '\').

24. Run "exit" (this will stop the output capture started with 'script')

25. If the 'tpdebrick' process did not end with "ALL DONE." you should
upload the "typescript" file (the output capture) so that the cause
of failure can be diagnosed. Regardless, it's a good idea to save
this file somewhere for future analysis, if needed.

26. Click icon in far right corner of screen
27. Select "shutdown"
28. Select "shutdown" or "reboot"

29. Connect Touchpad to stock HP AC charger and allow to charge for
several hours
 
See less See more
#3 ·
I get an error right after "writing file tz.mbn..."
./tpdebrick: line 255: 786432 \* 512 =: syntax error: invalid arithmetic operator (error token is "\* 512")

Is the \* intentional? I'm not on Ubuntu (running Arch on my laptop), would that be the cause of the problem, nothing else in the output looks suspicious or wrong.

Thanks.
 
#5 ·
Dear sir, thank you very much for your great efforts.

However, I have encountered the following problem on this step:

[background=rgb(245, 245, 245)]23. Run "sudo ./tpdebrick XX" (where XX is the size of the TP: 16, 32 or 64)[/background]
[background=rgb(245, 245, 245)]The terminal comes back with a message says:[/background]

[background=rgb(245, 245, 245)]dfu-until not installed[/background]
[background=rgb(245, 245, 245)]fastboot not installed[/background]
[background=rgb(245, 245, 245)]Aborted.[/background]

[background=rgb(245, 245, 245)]How can i overcome this? Thank you so much in advance![/background]
 
#6 ·

Attachments

#23 ·
Correct, there is no need for the QPST process with the latest version(s) of tpdebrick. That is now handled by the tpdebrick and helper programs.

The current tpdebrick is designed to work (if it can) regardless of the current state of your Touchpad.

So, just follow the instructions in the OP.
 
#14 ·
After getting through the initial byte writing I receive this

Code:
Executing file...<br />
Checking QDL mode...<br />
Writing file tz.mbn ...<br />
Sending MAGIC...<br />
MSG: Qfprom Fuse List: Blowing FAILED	<br />
MSG: Failed Fuse addr:  <br />
MSG: 0x00000000<br />
MSG:	Error Status:  <br />
MSG: 0x00000000<br />
Sending secureMode...<br />
Sending openMulti ...<br />
MSG: Open multi failed, unknown error<br />
ERROR: Open multi failed, unknown error<br />
Invalid openMulti response.<br />
Cannot write file tz.mbn<br />
Aborted.
Anything I can do?
 
#15 ·
tpdebrick v004 by jcsullins

TPDebrick has been designed and tested to work with an
Ubuntu 11.04 32-bit livecd. The instructions that follow
assume that you are booting an Ubuntu 11.04 32-bit livecd.
I'm using a live USB stick with persistence, made from Canonical's own ISO of 11.04. Some minor issues with the tpdebrick script that I've hit so far.

Code:
<br />
--- .tpdebrick_2013-01-30 2013-01-31 03:36:06.000000000 +0000<br />
+++ tpdebrick 2013-01-31 08:50:18.000000000 +0000<br />
@@ -67,7 +67,7 @@<br />
   echo "Aborted."<br />
   exit 1<br />
  fi<br />
- add-apt-repository --yes ppa:nilarimogard/webupd8<br />
+ add-apt-repository ppa:nilarimogard/webupd8<br />
  if [ $? -ne 0 ];<br />
  then<br />
   echo "add-apt-repository failed"<br />
@@ -81,14 +81,14 @@<br />
   echo "Aborted."<br />
   exit 1<br />
  fi<br />
- apt-get --yes install dfu-util<br />
+ apt-get -y install dfu-util<br />
  if [ $? -ne 0 ];<br />
  then<br />
   echo "install dfu-util failed"<br />
   echo "Aborted."<br />
   exit 1<br />
  fi<br />
- apt-get --yes install android-tools-fastboot<br />
+ apt-get -y install android-tools-fastboot<br />
  if [ $? -ne 0 ];<br />
  then<br />
   echo "install fastboot failed"<br />
It appears that either the apt tools don't accept "yes" as an argument at all, or only the abbreviated form.

I believe I am stuck in the same place as under QPST on Windows. Is there anything more verbose that can be output in the Linux version to help diagnose this issue? Or are you folks pretty sure that it's a hardware failure in this situation?

Code:
<br />
.<br />
.<br />
.<br />
Writing 1024 bytes to 0x2a028000; 1156 bytes left.<br />
Writing 1024 bytes to 0x2a028400; 132 bytes left.<br />
Writing 132 bytes to 0x2a028800; 0 bytes left.<br />
Executing file...<br />
Checking QDL mode...<br />
Writing file tz.mbn ...<br />
Sending MAGIC...<br />
MSG: Qfprom Fuse List: Blowing FAILED  <br />
MSG: Failed Fuse addr:<br />
MSG: 0x00000000<br />
MSG:	Error Status:<br />
MSG: 0x00000000<br />
Sending secureMode...<br />
Sending openMulti ...<br />
MSG: Open multi failed, unknown error<br />
ERROR: Open multi failed, unknown error<br />
Invalid openMulti response.<br />
Cannot write file tz.mbn<br />
Aborted.<br />
Thanks jcsullins, darkspr1te, et. al.,
nido
 

Attachments

#25 · (Edited by Moderator)
I'm using a live USB stick with persistence, made from Canonical's own ISO of 11.04. Some minor issues with the tpdebrick script that I've hit so far.

[ ... ]

It appears that either the apt tools don't accept "yes" as an argument at all, or only the abbreviated form.
Oops! The testing that was done was on 12.04 (not 11.04 as was stated in the OP). I have corrected the OP to state 12.04 not 11.04.

I will also be uploading a new version that properly supports 11.04 sometime soon, but for now, please use 12.04 instead.
 
#18 ·
@jcsullins
not sure if you would see this in the old post so ...
http://rootzwiki.com...30#entry1093372
I followed TPDebrick-v004 and finished the process as instructed and got ALL DONE on Terminal.

After ALL DONE, the home button started flashing, I let it plugged with original A/C Charger for about 10 mins and got the battery symbol with a lightning inside the battery symbol.

I think it's a good because I was unable to power it on.

At this point, should I just keep charging it until it reboots automatically? Do I have to install WebOS myself? Please advice. Thanks!
 
#28 ·
That is the same exact error that I am getting. Not sure what else to do.

Some background: TP locked up while charging with screen on. I remember seeing on the locked screen the battery was at 100%. Did the usual Power+Home button to restart it but the screen went black and nothing ever happened since. All that occured on 10/4/12 and I have tried all button combinations found online but to no avail. I never thought it was the usual battery issue because I knew it was fully charged. Finding this thread gave me some hope after searching for QDload drivers/solution.

Lastly, as stated I do get the QDload device using Win XP, although I was not successful with loading the drivers up. Holding Power+Home, I can hear the disconnect chime in windows, although when I try this in Ubuntu 11.04, it does not seem to do anything. Is Ubuntu supposed to recognize it as a device first before following the instructions in the OP?

Thanks for any help in advance for taking the time to answer this.

ubuntu@ubuntu:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
dfu-util not installed
fastboot not installed
Installing dfu-util/fastboot ...
Usage: add-apt-repository <sourceline>

add-apt-repository is a script for adding apt sources.list entries.
It can be used to add any repository and also provides a shorthand
syntax for adding a Launchpad PPA (Personal Package Archive)
repository.

<sourceline> - The apt repository source line to add. This is one of:
a complete apt line in quotes,
a repo url and areas in quotes (areas defaults to 'main')
a PPA shortcut.

Examples:
apt-add-repository 'deb http://myserver/path/to/repo stable myrepo'
apt-add-repository 'http://myserver/path/to/repo myrepo'
apt-add-repository 'https://packages.medibuntu.org free non-free'
apt-add-repository http://extras.ubuntu.com/ubuntu
apt-add-repository ppa:user/repository

If --remove is given the tool will remove the given sourceline from your
sources.list

add-apt-repository: error: no such option: --yes
add-apt-repository failed
Aborted.
 
#27 ·
Has anyone tried this with a TouchPad with the frozen memory issue? Where the changes to the rom are not saved after reboot.

Sent from my cm_tenderloin using RootzWiki
 
#33 · (Edited by Moderator)
Amazing! I got my TouchPad to get to the point where it now has a flashing home button while sitting on the stock charger. I cannot explain just how excited I am by this!

Aside: I was able to get this to work with VirtualBox (Mac OS X host, Ubuntu 12.10 guest) by creating filters at the various stages of the tpdebrick process.

NOTE: I am not recommending that anyone else do this, as there could be all kinds of things that go wrong in the process. But I thought it was worth mentioning.

Attached is a screenshot of the USB filters that I setup during the tpdebrick process.


Edit: I donated to jcsullins for helping to bring this device back from the dead. Thank you again!
 
#35 ·
Ok guys, worked on this this morning but I'm getting stuck at what seems to be the very beginning... the only ouput I have in terminal after waiting for 20 minutes is

checking doc files
extracting doc files
Requesting SoftwareVersion

and that's it, the cursor is just blinking on the line below Requesting SoftwareVersion

and sorry for asking this, I have no clue about anything in Linux... even getting stuck there am I supposed to have this typescript somewhere because can't find it... thanks for any extra help and advice
 
#37 ·
Hopefully this is a stupid question, but after couple minutes I am getting this

ubuntu@ubuntu:~/Downloads/tpdebrick-v004$ sudo ./tpdebrick 32
checking doc files ...
extracting doc files ...
Connect Touchpad then hold Power+Home+VolumeDown for 30 seconds ...

QDL mode not found
Aborting.

Any ideas?
 
#38 ·
Check USB cable and connections (maybe try another USB cable).

Make sure you are holding Power+Home+VolumeDown (VolumeDown is the one farthest away from the Power button)
all at the same time (without releasing any of them) for a full 30 seconds.

Don't try to run linux under a VM.
 
#44 ·
I can confirm this also works with ubuntu 12.10

For the first time in months my touchpad has the flashing symbol and its charging cant stop watching that little white light flick side to side i dont have a mains charfger but have it on a touchstone hope its back soon

To the dudes with cookie errors ive had cookie errors and it found flashing with qpst on another machine worked for me see my other post on v001 thread this process failed for me first time d/c reconnected and re ran v004 after it failed with the same error as the typescript on page 1 second worked successfully and its now charging!

Cheers again mate where can i donate when i get paid? 22nd feb lol!

Sent from my cm_tenderloin using RootzWiki
 
#49 ·
Can you upload your qpst log files from when you had the cookie error? I'm curious if it fails where mine does. No matter what computer I try this on, I still get the equivalent of the cookie failure. Of course, the only computers I have access to are Dells. I've tried windows xp, 7, 2008r2, ubuntu, and am currently looking at win8 hoping that I can get it to go through, but I am curious about your logs when it failed.

Thanks,
 
#53 ·
Just wanted to say thank you for this! I've had a bricked Touchpad for a few weeks and tried all sorts of things to wake it up, but nothing worked. I could get it to the point where the button would light up, and if I held down some buttons, the screen would come up with the battery with the question mark. This did the trick!!!!

I did have to try it a few times. Evidently, holding home, power and volume down didn't register correctly the first couple times. It's almost like it was some sort of toggle, and I had it the wrong way. The time it worked, I typed the sudo command, and the program prompted to me hold down the buttons, and then told me when to release. Then it worked

Here is an expert from the script:

v004ubuntu@ubuntu:~/Downloads/tpdebrick-v004$ sudio ./tpdebrick 16
checking doc files ...
extracting doc files ...
Connect Touchpad then hold Power+Home+VolumeDown for 30 seconds ...
Release buttons now
Requesting SoftwareVersion...

After this was done I charged it, and in about a half hour I got the battery icon, but not the question. About 20 minutes later, it booted up right to Android.
 
#55 ·
That's similar what happened to me... it didn't want to recognize the TP was connected so I ran the command and once it prompted me to connect it with the button configuration the process went through without a hitch.

Since then it has booted to Android but VERY slow to charge so I shut it down and got the battery symbol because after an hour of charging in Android I still only had 1% battery... so I sat there and waited for it to start to boot and chose webOS... once in webOS charging was much much faster

Sent from my cm_tenderloin using Tapatalk 2
 
#54 ·
THANK YOU! THANK YOU! THANK YOU!

This weekend I picked up a touchpad off of craigslist that was listed "for parts only" by the seller, they claimed it just didn't turn on anymore. 50 bucks for the TP, case, charger and touchstone charger. I had already started reading up on the problems before the purchase, after searching for a while I came across this forum. I started off with the tpdebrick v01 and ended up running into problems on this step: sudo ./tpdebrick tp16/dev/sdb (mine showed up as sdb after ls dev/sd?). Anyhow, today I saw the new v004, downloaded it and tried it out. I am running a Ubuntu partition on my win7 machine. Success within 10 minutes. I first saw the big battery and lightning bolt, quickly switched over to the original power supply and let it sit, 4 or 5 minutes later it started booting into cyanogenmod 7. I suspected that the previous owner installed android and I was right. Letting the TP charge right now, tomorrow I will begin wiping it clean.

JCSULLINS - THANK YOU! This was really easy. Mad respect for your skills, keep up the epic work.
 
#56 · (Edited by Moderator)
@jcsulins

Here we go..... ! you are really great ! just followed your instructions....got "ALL DONE" with few warning ! but home button is blinking...now......that suggest heart started.....pumping back....going to keep full night on oxygen .............hope for the best !

Thanks again for your help......after 2/3 months I am seeing HOME BUTTON blinking ! ...

Update - Its worked....thank you Jcsulins.....you are great ! TP back to Normal ...(used LiveUSB)
 
This is an older thread, you may not receive a response, and could be reviving an old thread. Please consider creating a new thread.
Top