yashsingh1/xdaforums huggingface dataset:
[TouchPad General] deafasheck:
I had the same thing, I went and downloaded the Studio thingy but Ubuntu said I ran out of disk.. space.. I am using 29 gig usb to boot Ubuntu, I have even figured out >mostly the commands but I must be doing something wrong? dio I unzip the studio? or just download it to Ubuntu and command prompt run it?

---------- Post added at 10:27 PM ---------- Previous post was at 09:33 PM ----------

Yes Please explain how you did # 6 thank you
[TouchPad General] deafasheck:
Cracking open the tp script

Hi if I'm using Unbuntu how can I crack the script? can I down load it on windows and open it via Ubuntu ?
[TouchPad General] deafasheck:
Same thing with mine except fail to load fastboot as wel.. I'm racking my brains out for a solution, nothing happening here, post in doa. this helped a little, http://finallystart.blogspot.com/2013/05/reviveunbrick-your-dead-hp-touchpad.html

but I'm back to trying to get Ubuntu to do it. I just learned a few more commands from that other link.. best of luck to you.. I'm currently working on mine...
[TouchPad General] deafasheck:
Trying my darndest to learn this stuff. lol, how do I add this to the tpdebrick-v004 folder, copy paste? or ??

I have tried several days now, each ends with either no fastboot or various errors.. if I could learn how to save the script inside the terminal it would help.. I've about drove everyone else nuts in my stupidity on these things.. no tech by a long shot.. can install thanks to JC Sullins and Shumash, and various others.. lol
[TouchPad General] shumash:
Create a new file with an editor, probably gedit. Copy the shell commands below into it:

#!/bin/sh
while !(sudo ./tpdebrick 16)
do
sudo perl qdload.pl --lreset
sleep 1
done

﻿ubuntu@ubuntu:~/Downloads/tpdebrick-v004$ cat > tpauto
#!/bin/sh
max=999
for i in 'seq 1 $max'
do
echo "Try #$i"
sudo ./tpdebrick 16
sudo perl qdload.pl --lreset
sleep 1
done

Save the file as tplup in the tpdebrick-v004 folder. Open a terminal session in the tpdebrick-v004 folder and type each command Webosfan gave in the previous post one line at time followed by the <enter> key, i.e.

chmod +x tplup <enter>
sudo ./tplup <enter>

XDA is not a training ground. You really need to learn this stuff yourself.
[TouchPad General] deafasheck:
You always make it seem so easy.. lol.. get this I have gotten past that last error from fastboot failure now Im cannot write file TZ.mbn

I'm leeting them charge for a couple days, I think is just gonna be my parts/ trainer tablet..

Yeah, I've got to learn this. I'm suprised at how far I got today on it, one thing I'm gonna try is using a 64 bit Unbutu... that being said, could I use a 64 bit USB Ubuntu on a 32 bit PC?

thanks for the explanation.. I bought these TP's for just this, to learn all I can.... Have a great weekend man...
[TouchPad General] shumash:
Don't. There's tons of posts that indicate it ONLY works on Ubuntu 12.04 32-bit
[TouchPad General] deafasheck:
Thanks, I'm seeing posts only works for 64 but they're not XDA.. found a few in other sites, and all are using JC Sullins tp debrick..

I'm gonna go at it again this evening, I thank you for your help. I can pull it off on one of these, I'm certain. The other is gonna be Dissasembled thanks for that link as well.. I'm a toying Boy! :)

have a great weekend...

PS: I'm done with TP's :laugh:
[TouchPad General] Jnbourdet:
Hi Everyone, its seems this thread still alive. I´ve done all the procedure told and wen it get to: ALL DONDE.

Well.. I get this a weird and extrange red pattern on restart, and nothing else. No Usb icon, No Hp logo, No Recovery. Juast a really weird red pattern screen.

Any suggestion?

Or

RIP?
[TouchPad General] jmdesai:
I am all smiling now. Nothing worked in my case afetr I got A6 files copy failure.

I followed this procedure step by step, and now my TP seems to be charging. I think it will boot well after charging.

We survive in this world because of xda and people like jcsullins, Emba4, and asiliat. Thanks a lot.
[TouchPad General] markheat:
hi, following the steps from asiliant - look above - a few mistakes in his text let the experiment with an 4 years bricked touchpad stop... but now... after one night of noob ubuntu search in this famous internet did it...

step Get the environment ready:

3. sudo getit sshd_config did not work... instead sudo gedit ssh_config worked

step Ready to start debrick:

4. Hold Power+Home+VolDown buttons on Touchpad for 30 seconds i had to repeat the script several times until all files for the fastboot were written... but then fastboot did nothing.... so at the point the script wanted the touchpad to fastboot, i hold Power+Home+VolUp buttons and then fastboot started the touchpad and everything worked fine...

now i see the blinking of the homebutton for the first time in years on the white tp 64... i hope the battery did not die over the years...
[TouchPad General] HP_TOUCHPAD:
If you do not see any liquid spots on the screen, then the battery did not expand.

Charge the battery completely, it could take a couple of days, depending on the temperature where is at.

You should have a working tablet for many years to come, if the battery is maintain properly!
[TouchPad General] larrywilson:
thanks i am going to verify i have three with interogation sign i should have something special for these cases automated for chip A5
[TouchPad General] ZeroZorro:
One question...you didn't have any problems installing openjdk-7-jre on this 16.04.2 Kyle Ubuntu? I read this was not very easy to accomplish at this date?
[TouchPad General] HP_TOUCHPAD:
If anyone is expecting any device to turn on instantaneously after been unused for years. Something is brick, but no the device.

The only thing that can communicate with the HP Touchpad is the novacom driver and the tablet has to be set into webOS Recovery. (big USB symbol )

You can run any version of Linux from many years ago using a Virtual Machine on any OS and install the novacom driver and do everything like in 2011.

A dead uncharged battery from not been used for years is not a brick device, is called a discharge battery and a careless user.
[TouchPad General] ZeroZorro:
Thanks for your info, but I am not a total noob and yes, I read the thread(s).

Problem is I want to found out if the

'Qfprom Fuse List: Blowing FAILED'

error is showing because of hardware failure or bad 'ubuntu' setup (or even using obsolete scripts).

Thing I like to add that my black screen started while changing/flashing ROM's and not cause it's left in a dark corner for a long time.

Setting up an old Ubuntu version, even a live USB, with new(er) hardware (in my case a Nvidia graphics card ) can be difficult sometimes.

EDIT: In the end i went for the VMWare-option, fingers crossed ;)
[TouchPad General] HP_TOUCHPAD:
Any Device that needs to communicate with a Computer needs a driver. This will allow the Computer to identify the gadget and play with it.

Is the only way to get both devices to communicate to each other, it has always been that way. There is no other work around or magic.

I am using Ubuntu 18.04x64 with the Palm novacom driver install and it works perfectly, I followed this instructions to get it working.

https://forums.webosnation.com/hp-touchpad/331153-novacom-drivers-ubuntu-64bits.html

After you have successfully install the novacom driver and is working properly then the next step is to set the TP into recovery mode.

The TP battery needs to have some charge to be able to boot. There should not be any blinking light, that will indicate is charging normally.

No USB cable should be attached to the tablet to start recovery.

Press simultaneously the power and left volume key (closer to power)

Once you see the big USB white symbol on the screen, connect the USB cable on TP and PC.

Rename this file in the tptoolbox_v42 directory.

TPToolbox-2015-01-08-v42.bin to uImage.Toolbox

Open a terminal in that directory and paste

novacom boot mem:// <uImage.Toolbox

novacom driver will communicate with TP and load the Toolbox into memory and boot.

Once you have done all you need to do there (Do not use it to install any ROM)

Use complete data reset (if you do not want WebOS)

Create Android volume and resize then reboot.

You will have a boot menu.

Select WebOS recovery

Unzip the latest TWRP ( FLINTMAN-TWRP-touch-data_media-SELINUX-f2fs-3.1.0-0-5-09-17.zip

Open a terminal in that directory and paste

novacom boot mem:// <uImage.TWRP

Once TWRP is loaded the TP will be recognized by PC and you can transfer the TWRP zip file and any ROM to install.

You will need to install TWRP to make it permanent as is running from memory the first time.

If you have any issues then post it on here.

Also Read this to understand what the ToolBox is:

https://xdaforums.com/hp-touchpad/general/touchpad-toolbox-how-to-unpack-repack-t3888242
[TouchPad General] deafasheck:
Novice Attempt

Gonna give it a whirl.. I have one TP that is savable maybe two? gotta try and I will update as go, thanks to JC Sullins and yourself for all the info and links..
[TouchPad General] Droid_JD:
Can anyone help me revive my TP?

I've tried all the steps above (about a 1/2 dozen times) with minor variations:

1. I used TPDebrick v 4 and 5;

2. I was unable to perform Part 1, step 1b ("sudo apt-get install openjdk-7-jre"") as that version is no longer supported, so I did "sudo apt-get install openjdk-

8

-jre"" (emphasis added);

3. Part 2, step 3 "sudo getit sshd_config" didn't work, as recommended, I ran "sudo gedit ssh_config" and it worked fine;

4. part 2, step 6 "ssh-keygan -A" didn't seem to work either, so I ran "sudo ssh-keygen -A" and it worked fine.

I went through the rest of the steps, and everything started to go well, until I got to the A6 drivers. That's where the procedure has consistently failed.

These are the last few lines of the output from tpdebrick:

Waiting for netchip mode... (may take 3+ mins)
Waiting for ping check... (may take 1-2 mins)
Checking/updating known_hosts...
Copying A6 files...
/etc/ssh/ssh_config line 54: Bad SSH2 cipher spec '3des-cbc,blowfish-cbc,aes128-cbc,aes128-ctr,aes256-ctr'.
lost connection
A6 files copy failed.
Aborted.
ubuntu@ubuntu:~/tpdebrick-v004$

I'm assuming this has to do with changes to the ssh_config file?

Can someone help me out?
[TouchPad General] HP_TOUCHPAD:
This is the Ubuntu version that Jcsullins used and you can find all files also on this site:

http://downloads.codefi.re/jcsullins/misc/ubuntu

http://downloads.codefi.re/jcsullins

I have never come across a Tablet that is brick and never had to do the TPDebrick.

Why do you think that the Tablet is brick?

What is doing, or not doing?
[TouchPad General] Droid_JD:
Hi there,

It's not charging, not blinking, not showing the USB screen. In fact, the only thing it's been doing is sitting in a drawer for 2-3 years collecting dust :D

I lost the original charging plug and cable long ago, and I've used a number of other plugs and cables with no luck. I thought this was the best approach to try and bring it back to life, but I'm certainly open to any and all suggestions.
[TouchPad General] HP_TOUCHPAD:
The battery needs to be charge properly, and must have enough charge to start and shows any graphics on the screen.
[TouchPad General] Droid_JD:
Thanks. I've tried with a number of 5V2A chargers, not sure if I have a 5.3 lying around. If not, I guess that's what Amazon's for...

I'll see what I have lying around at home and report back.
[TouchPad General] HP_TOUCHPAD:
It must be specifically and exactly Output: 5.3volts, 2.0amps

Get authentic original HP TP charger.

It could takes days to even a light to blink.
[TouchPad General] Lister Of Smeg:
Hi [MENTION=2863435]Droid_JD[/MENTION],

Trust me, [MENTION=8005714]HP_TOUCHPAD[/MENTION] is correct..... I thought my HP Touchpad had died too, I'd not used it for a matter of months, maybe even a year.... and just assumed it would work once I plugged it in. I tried for days, weeks.... I tried all kinds of chargers, adapters, connecting to PC. Fast charge, hard charge, low trickle charge... everything !!! There was no life in it what-so-ever. I even read about the official Wireless charging stand, and bought one of those off eBay. (Beauty in buying that, I got a Wireless Charger, Case and another practically BRAND NEW Touchpad.... for £30).

Anyway, I used the Wireless charging stand, and still no joy... :( (apart from another Tablet).

But then, I plugged the original Touchpad into my brothers Linux PC, and followed the commands/instructions, and all of sudden.... BINGO... It sprung back into life !!! :D

I then followed the instructions in Toolbox to reflash the A6 firmware, and been charging the Touchpad ever since and it's not faulted since, it holds it charge perfectly. :good:

Then check out a lot of [MENTION=8005714]HP_TOUCHPAD[/MENTION]" posts, they are an incredible source of knowledge. He explains it in amazing in depth detail, yet are really easy to follow... He's done wonders into bringing new life to our ageing devices... :good:

Cheers, Lister
[TouchPad General] calca28:
Tablet does not turn on even when charged

I tried to unbrick my HP Touchpad with the tools tpdebrick-v005 under Ubuntu. I carried out the manipulations described. The Touchpad is well recognized under Ubuntu. But I have an error message at the end of the process. Suddenly, my tablet remains off.

Error code:

A6 files copy failed.

Aborted.

Can you help me solve my problem?

Here is the result file I get.

ubuntu@ubuntu:~/Téléchargements/tpdebrick-v005$ sudo ./tpdebrick 32
Checking doc files ...
Connect Touchpad then hold Power+Home+VolumeDown for 30 seconds ...
Release buttons now
Requesting SoftwareVersion...
Version: PBL_DloadVER1.0
Requesting Params...
Params: 06 01 01 00 90 00 00
Uploading file 'emmcbld.bin' to QDLOAD...
.......
Writing 552 bytes to 0x06411600; 0 bytes left.
Response: ACK 0x06411600 (outstanding: 0)
Sending CloseFlush...
Writing file mbr32.bin ...
Sending MAGIC...
Sending secureMode...
Sending openMulti ...
Uploading file 'mbr32.bin'...
Writing 512 bytes to 0x00000000; 0 bytes left.
Response: ACK 0x00000000 (outstanding: 0)
Sending CloseFlush...
Done writing files.
Reseting device...
Requesting Reset...
Waiting for fastboot mode...
Loading TPToolbox-Headless ...
sending 'bootmem' (13200 KB)...
OKAY [ 0.830s]
writing 'bootmem'...
OKAY [ 2.917s]
finished. total time: 3.747s
Waiting for netchip mode... (may take 3+ mins)
Waiting for ping check...
Checking/updating known_hosts...
Copying A6 files...
Unable to negotiate with 192.168.7.7 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1
lost connection
A6 files copy failed.
Aborted.
[TouchPad General] golfnut22:
Hello,

This may be a dead thread as these tablets are getting pretty old, but I like the challenge, plus it is/was a good table. Anyway, I have the same problem. I had revived my TP a couple of years ago using the tpdebrick method. It just died this week and trying to revive it I get the same message. Searching thru this thread, I had tried the various SSH changes suggested to no avail. If you have found a solution I would appreciate how you managed to fix it. Thanks

Copying A6 files...

Unable to negotiate with 192.168.7.7 port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1

lost connection

A6 files copy failed.
[TouchPad General] pepebuho:
Help! I cannot get past the USB icon.

I can talk, to the tablet, but no matter what I do it will not reboot past the USB icon.

I can talk to it via novacom, the recovery iso work, webdoctor works, tptoolbox work, all of them find the tablet and do their magic but when it is time to reboot, the tablet goes back to the usb icon.

What is happening? How can I revive my Touchpad?
[TouchPad General] pumacorp:
worked for me

Ok,,

I tried everything from phone chargers and god knows everything else ...What worked for me what I hooked it up to my computers usb port ..The old school USB port on my old imac from 2009 ...In any event I put it on for a few hours ,,nothing really happened ...I grabbed my booster pack to jump cars and put it in my USB port cause I figured it wasnt as strong as a USB port in a computer and it worked ...I left it on a few hours held the power button while pounding on the home button about 20xs. ...Stopped and about 15 seconds went by and boom it lit up and shut right off,,,so put it on the original charger and it took a charge no problem...Now why this worked is u have to fool the battery ....All motorcycle batteries that are either AGM or lithium ion will never take a charge if it falls below 6 volts ....So I take another battery and jump it to the dead one and it fools the charger ..The charger then charges the batteries right up...So I took the same approach trying to fool the charger on the HP and it worked like a charm...My HP has never been on til the other day ..It was still sealed in the box ...So do the math on how long that unit has sat ....So if i can get mine working I cant see anyone else having an issue ...I have another I just took out of the box and will try the same routine and lets see if it works ...
[TouchPad General] Droid_JD:
Any luck with Tablet No. 2?

I too have a usb Car-Jump charger and I hooked it up to that. I believe the touchpad took a charge (the jumper is now at about 25% capacity) but the tablet won't turn on.

Now that I'm typing this out, I realized that AFTER taking the charge from the jumper-pack, I did not try to connect it to the stock wall charger, so I'll try that now and report back if there is any progress. If there's no "edits" in the next 5-10 minutes, it likely didn't work for me.
[TouchPad General] HP_TOUCHPAD:
To revive any lithium battery that was completely drain:

Using ONLY the original HP charger or equivalent.

Room temperature must be warm arond ( 80 F )

1 Plug in charger to tablet.

2. Plug charger to wall, or better an extension with a reset on and off switch.

2. Do intermittent ( on and off ) about 10 seconds ON, 10 second off.

It could take very long time, until the Home LED start moving from side to side, then it will take more time to get into the battery symbol, then more time to boot.

Every time the charger is connected to the outlet, it allows just a little bit of extra electricity forcing the battery to wake up and take charge.
[TouchPad General] Droid_JD:
Please! Step by step would be appreciated.
[TouchPad General] ZeroZorro:
+1

Verstuurd vanaf mijn Z2_PRO met Tapatalk
[TouchPad General] jaycee147:
RE. Failed to open multi error !! possible fix

i have bought another 4 of these not working and dead. so i am just waiting for them to arrive to see if any of these wont go past the OPEN MULTI ERROR fail. hopefully this will give more indication of what i did gets past it. AS soon as i can verify i will go through it step by step.. i want to start fresh and if i do it now with the terminal i have open running in the background i wont get same errors as some parts will be running.
[TouchPad General] jaycee147:
Multi Error possible fix

Update:-

The 4 Non working touchpads i bought ( all had been opened and messed around with internally.) are all up and running, a further one of these had the fail at Multi Open Error. So i will attempt to go through an updated version of running TP Debrick. Hopefully this will lead to some of those hidden in the back of wardrobes being brought back to life. Every one of them booted back into the way they had lost power.
[TouchPad General] ZeroZorro:
Big thanks for this all, only want to mention that the 2 codefi.re links are not working for webOS doctor and tpdebrick5

Those seems to work for me:

http://downloads.codefi.re/jcsullins/tpdebrick/tpdebrick-v005.zip

http://downloads.codefi.re/jcsullins/webos/doctors/original/webosdoctorp305hstnhwifi.jar

Verstuurd vanaf mijn Z2_PRO met Tapatalk
[TouchPad General] jaycee147:
Links

Glad you found working links. And posted them for others.. I only downloaded from what i got a couple of days ago.. just shows how quickly things can change. Let me know if you have any luck.
[TouchPad General] ZeroZorro:
The links are the same but in your post there have been ending up some dots/periods in the URLs.

So credits are yours ;)

Verstuurd vanaf mijn Z2_PRO met Tapatalk
[TouchPad General] jaycee147:
Updated Debrick with possible Open Multi Error fix links now work

Thanks for letting me know about links original post now updated with working links.
[TouchPad General] HP_TOUCHPAD:
The HP Touchpad is not "bricked"

The HP Touchpad is a WebOS device and will always be regardless of what OS has install.

Bootie is the stage3 bootloader of webOS devices. ( HP Touchpad )

Click HERE for Information about the Bootie

If bootie on the flash disk has been damaged or corrupted in such a way that booting into recovery mode is not possible, the " HP Touchpad" is still not "bricked" as the OMAP3430 processor in the " HP Touchpad" provides for a mechanism to boot code from its USB interface. ( The Pre and the Touchpad use the same bootie )

Clicke HERE for Last Resort Emergency BootLoader Recovery

The TPDebrick does all that and is pack the same way as the Toolbox:

Click HERE Touchpad Toolbox, How to unpack and repack

In a way the Bootie is similar to the Bios on a PC.

If the Bios on a PC is corrupted or damage the PC will turn on to ( nothing ). On the Hp Touchpad there is no way to know if is on as there is no fans or light indicator.

The Tablet is on but Bootie can not make the internal hardware communicate to each other to display anything on the screen.

Replacing the battery will not solve the issue. The same as replacing the power supply on a PC will not fix the bios.

Most of the Tablets out there have a dead battery which can be revive, but not using the de-brick method.

I need to figure out how to intentionally damage the bootie and the repair it, that will be the only way I could test the TPDebrick.
[TouchPad General] jaycee147:
Correct .. even when i put a fully charged battery into one of the tablets that had the Open Multi Error it still stopped with that error. It wasnt until i ran the loop script with the heater on the back of the tablet that it would go past the error as explained above.. This just wasnt a one off lucky repair with the Multi Error.. it has revived 3 tablets. I bought 4 extra tablets to further test and 2 had the same problem .. now working with the heater.. As i explained i am no techno genius.. i have just put out here my findings in the hope that it may help others.. it does however seem to me that when a Touchpad gets below a certain level of battery it prevents itself in different ways for re setting.. And i have now used this Tpdebrick to recover 7 tablets. . All the Tablets recovered were completely dead.. Not possible to get to the USB screen .. no amount of charging would bring them back to life.. No heat from the barrel chargers when plugged in..
[TouchPad General] dilrat:
I have decided to dust off my old HP Touchpad and see if i could get it to work again. It has been sitting for several years untouched.

Initially it wouldn't charge, but I got it to do the home button light from left to right.

Now it actually shows the Red Line charger picture, but doesn't seem to move from there.

At this stage, should i try running the TPDebrick process, or is this still a matter of it not having enough charge? I don't have the original charger anymore so i'm used a wall charger to charge it.
[TouchPad General] HP_TOUCHPAD:
Is not having enough charge that's all. If the bootie was damage nothing will show on the screen at all, not even the home button then the TPDebrick will be need it to reflash the bootie.

Make sure the charger output is 5.3 volts 2.0 amps, same as the original.
[TouchPad General] jaycee147:
charging

it is definitely best with the original Barrel Charger,,, whilst the flashing lights are going side to side it seems to me it is taking a trickle charge, Then when all is ok the Barrel charger get quite warm and thats when i noticed the flashing lights go out and full charging is taking place. Its difficult to know if youre getting enough charge with a third party charger.