Android OS Forum banner
1 - 20 of 26 Posts

·
Developer
Joined
·
339 Posts
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
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #7 ·
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.
Yes, it was intentional. It's a habit I have of escaping '*' when used with cmds like "expr 10 \* 10" so the shell does not think it's a filename wildcard.
The '\*' construct worked fine in my testing with Ubuntu and LinuxMint. However, it seems that whatever Arch uses for /bin/sh does not like it.

Anyway, I have changed it to just use '*' and (as you said on IRC) it now works in Arch and I have tested it still works on Ubuntu.

The zip file on goo.im has been updated.
 

·
Developer
Joined
·
339 Posts
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]
If you were using Ubuntu versions 11.04, 11.10 or 12.04 it would automatically install them for you.

So, you could boot an Ubuntu 12.04 32-bit livecd (as mentioned in the OP).

Or, you could ask the google what you need to do for your OS to install them.

For the least amount of trouble, I suggest using an Ubuntu 12.04 32-bit livecd install.

EDIT: Oops, had 11.04 when it should have been 12.04 (also 11.04 install of those pgms won't work properly until next version).
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #10 ·
Thanks for your continued work on these issues. I am one of the ones that continued to get the cookie error, and it seems wiht this new method, I am still getting the same errors. I have attached my typescript for you.

Thanks, View attachment 36547
The opening of the emmc for writing is done with the 'openMulti' command.

So the "Open multi failed, unknown error" suggests to me an emmc (hardware) failure.
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #23 ·
So for v004, there is no need for QPST and the steps under Windows? I already did the Windows steps with the now deprecated TPDebrick v0.1. Then I was stuck somehow on the Linux steps. What can I do now?
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.
 

·
Developer
Joined
·
339 Posts
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.
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #29 ·
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 />
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 />
No, that is as verbose as it gets. We have spent several hours trying to find a way to get more useful info, but were were not able to do so.
I've exhausted everything I know to be able to diagnose it more, so unless someone else makes a discovery or there is some sort of leak/etc.
that looks like it's as good as it gets.

An emmc hardware failure is my best guess given the limited info we have. We know that the "openMulti" command is when it opens the emmc
for writing. Perhaps there is some other reason for that to fail, but I do not know what that would be or how to diagnose it.
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #30 ·
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.

[email protected]:~/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.
Ubuntu normally doesn't "chime" like windows when a device is connected/disconnect.
Just follow the instructions in the OP (with the changes noted below).

As for the errors you had, try using Ubuntu 12.04 instead of 11.04.
( see http://rootzwiki.com/topic/38786-tpdebrick-v004/page__st__20#entry1093474 )
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #36 ·
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
The typescript file should be in the current (tpdebrick-v004) directory if you followed the OP.

What version of Linux is this? Is it Ubuntu 12.04 as mentioned in the (revised) OP, or something else?
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #38 ·
Hopefully this is a stupid question, but after couple minutes I am getting this

[email protected]:~/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?
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.
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #71 ·
Thanks jc for quick reply... OK at first I was using Mint and having a hard time installing dfu util and fastboot so I went back to windows and created an Ubuntu 12.04 as in OP.

I was still getting stuck so I said to myself it seemed like when in windows and adb would say waiting for device... soooo I ran the commands with the TouchPad UNPLUGGED and then the terminal window asked me to connect the TouchPad and went on its merry way....

Got all the way through and got the All Done message at end. Then the command prompt tested for battery level and after its second try it then said to connect TP to original charger for several hours. It is now connected and the home button LED is blinking from side to side, BUT there was no typescript in the tpdebrick directory...

So should i run through the process again or just let it charge? Maybe I should mention that it bricked during an install of Android. The guy can't even tell me what version of Android, ACME or even moboot he was using

Sent from my cm_tenderloin using Tapatalk 2
If it gets to the "ALL DONE." just let it charge on the stock HP AC charger for several (usually 6-12, but maybe more) hours and see if it boots.
 

·
Developer
Joined
·
339 Posts
For those who get the openMulti error (i.e. the following):

Code:
<br />
Sending openMulti ...<br />
MSG: Open multi failed, unknown error<br />
ERROR: Open multi failed, unknown error<br />
Invalid openMulti response.<br />
[ ... ]<br />
Aborted.<br />
Let me know if you are able to get into DFU mode.

Check that by holding Power+Home+VolumeUP for 30 seconds.
Then check output of "lsusb" and see if there is an entry with "ID 0830:8070 Palm" (which means it's in DFU mode).
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #700 ·
Well, I think it's dead Jim - tried to run it again after what happened previously and now it won't even get past the screen saying to connect the TP and hold down the buttons. Ah well, worth a shot - this was already dead for months anyway.
Sounds like bad USB cable/connection.
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #717 ·
It has been charging for almost two weeks with no change in status. Does anyone know what the test pattern on the screen means?
Yes. It means that the bootie-config (bootloader configuration) partition is empty or corrupt.
Part of what is stored there is the images that bootie displays (like the USB symbol for webOS recovery mode, low battery symbol, etc.).
 

·
Developer
Joined
·
339 Posts
Discussion Starter · #853 ·
Cants seem to get the touchpad to shutoff from the battery question mark symbol. I tried power+vol-up+home and it goes black and then immediately turns back to the question mark. I was told that inorder to get it into qdl mode it must be booted from off with power+vol-down+home.
I have been getting the qdl mode not found and I am wondering if that is the reason.
Any help or ieas would be appreciated.
No, the Touchpad shouldn't need to be 'off' to get into QDL mode. Holding Power+Home+VolumeDown for 15-20 seconds with the touchpad in any state (on, off, whatever) should put it into QDL mode. Note that if the battery is dead, it will need to draw power from the USB cable, so make sure the USB cable is connected
first.

Check USB cable and connections.
 
1 - 20 of 26 Posts
Top