32GB HP Touchpad will not turn on

[doncapo]

my touch pad was fully charged when I turned it off now it will not turn on. Before I turned it off I lost all e-mail and pictures too. What do I do now ?

[imfallen_angel]

plug it in?

but seriously, just have a look in the forum, there's multiple threads about dead Touchpads, and all have various approaches to try to revive it.

[Remy X]

I remember seeing this happen to someone else, but sadly, not the solution. Considering that you've already lost all your data, you might as well put it into recovery mode now and Doctor it.

Sorry that I'm not being specific, but I'm on a Touchpad myself, and all of the links i usually post are saved on my laptop. The links to Doctor images are in the webOS Internals wiki (google it), and recovery mode is the vol up key + power...

[Mutoidi]

(Or throw it away!)

But if none of that works because it's truly 'bricked' - you could try going here:

TPDebrick v004 - HP Touchpad - RootzWiki instead.

[Remy X]

Originally Posted by Mutoidi

(Or throw it away!)

[...]

Bad suggestion IMHO...

There's always room for it in someone's parts bin.. even the screen alone, if you don't count the other usable parts. But i see how you feel.. we all get emotional at times

[Mutoidi]

Originally Posted by Remy X

Bad suggestion IMHO...

There's always room for it in someone's parts bin.. even the screen alone, if you don't count the other usable parts. But i see how you feel.. we all get emotional at times

Dude.. it was a 'JOKE'! (Or at least it was meant to be - as a 'follow-on' from 'Plug in it?').. sorry I couldn't resist it in answer to the OP's plaintive 'What do I do now?'

I never throw ANYthing away!

And 'Parts' will eventually also be really vital to this legacy, I agree!

[Remy X]

+1

i also wonder if the "power + vol + home" combination will get it to boot.. But Doctoring at this point would be a good idea in any case, as the USB/media partition (which holds photos, etc) has somehow failed, and that may mean other corrupted files that will act up later. Doctoring should also reflash the NVRAM, which should hopefully clear up the reason for the original problem...