Page 2 of 6 FirstFirst 123456 LastLast
Results 21 to 40 of 109
Like Tree12Likes
  1. mbudden's Avatar
    Posts
    50 Posts
    Global Posts
    957 Global Posts
       #21  
    Your issue is very different than mine.

    Quote Originally Posted by limitbreak View Post
    I bricked mine too, it wont turn on aand I just got it in the mail! The chat tech specialist (I was trying to fix the autoload flash issue) told me to install webos dcotor and whne I connected it to the pc it showed usb icon but the next botton wasnt coming so i thought it wasnt recognized so i unplugged the usb and the device was working fine went back to regular, I turned it of and then it wouldn't turn on again at all
    You can at least get into Recovery Mode, mine can't. Like I mentioned, mine doesn't even turn on. I have held the button for 10 seconds to over 3 mins and nothing happened. Some how or another. It just completely died. So that ends the thought of the HP TouchPad "not being brickable"
  2. Jace985's Avatar
    Posts
    46 Posts
    Global Posts
    119 Global Posts
    #22  
    Quote Originally Posted by mbudden View Post
    WebOS Dr failed at 12%. Sat there for over an hour.
    Now the computer doesn't recognize the device. Looks for driver, then fails.
    Plug it into the wall charger, and nothing happens. No LED, no nothing.
    No button combos work etc.

    Looks like I'm not the only one.
    http://forums.precentral.net/hp-touc...-touchpad.html
    http://forums.precentral.net/hp-touc...-touchpad.html

    How disappointing.


    This just happened to me too Going to Call HP in the morning
  3. #23  
    Quote Originally Posted by mbudden View Post
    WebOS Dr failed at 12%. Sat there for over an hour.
    Now the computer doesn't recognize the device. Looks for driver, then fails.
    Plug it into the wall charger, and nothing happens. No LED, no nothing.
    No button combos work etc.

    Looks like I'm not the only one.
    http://forums.precentral.net/hp-touc...-touchpad.html
    http://forums.precentral.net/hp-touc...-touchpad.html

    How disappointing.
    Try doctoring on another computer.
    You do realize that the first one you posted was solved and the second one I guess it was solved since the OP never replied back.
    No bricked history yet.
  4. #24  
    Unless HP drastically changed something about webOS, a bad flash won't brick your device. How I know? I've had bad doctoring experiences as well (accidentally pulled out cable once, had a broken cable that spontaneously stopped working another time, a few times where the doctor just stopped after certain points) and both my Pre and Pre+ still work fine.

    It's unlikely your TP is actually bricked as in BRICKED.
    Soorma likes this.
  5. Jace985's Avatar
    Posts
    46 Posts
    Global Posts
    119 Global Posts
    #25  
    Aug 27, 2011 7:33:37 AM com.palm.nova.installer.recoverytool.CardController logP
    rint
    INFO: Trenchcoat: <INFO> Volume group 'store' current configuration: 9 logical v
    olumes

    Aug 27, 2011 7:33:37 AM com.palm.nova.installer.recoverytool.CardController logP
    rint
    INFO: Trenchcoat: <INFO> Volume group 'store' new configuration: 8 logical v
    olumes

    Aug 27, 2011 7:33:37 AM com.palm.nova.installer.recoverytool.CardController logP
    rint
    INFO: Trenchcoat: <INFO> LVM configuration changed

    Aug 27, 2011 7:33:37 AM com.palm.nova.installer.recoverytool.CardController logP
    rint
    INFO: Trenchcoat: <INFO> Adjusting LVM logical volumes

    Aug 27, 2011 7:33:37 AM com.palm.nova.installer.recoverytool.CardController logP
    rint
    INFO: Trenchcoat: <INFO> Reduce volume 'media' filesystem from 13690208256 to 13
    572767744 bytes

    Aug 27, 2011 7:33:37 AM com.palm.nova.installer.recoverytool.CardController logP
    rint
    INFO: Trenchcoat: <INFO> About to call: resizefat /dev/mapper/store-media 135727
    67744B

    Aug 27, 2011 7:33:37 AM com.palm.nova.installer.recoverytool.CardController logP
    rint
    INFO: Trenchcoat: <INFO> Running "resizefat /dev/mapper/store-media 13572767744B
    "

    that'ts where mine is getting stuck at.. any tips?
  6. #26  
    Quote Originally Posted by Tapiozona View Post
    I still think it's a smoking deal at $100 even with my bad luck. By "Butler" service you mean you called Tech Support and they're going to send you a box to mail it to repairs (in Texas)?

    That's what I have to do and they said about 2 days to get the box and then 10 days after that to get it back.
    Yeah. When I was on the HP website for support, it was called "WebOS Butler Service". Something that comes free for 90 days or something. I guess I'm waiting on the box, too. I was told I would get instructions via e-mail. I haven't received those yet, though.

    Quote Originally Posted by mbudden View Post
    Yeah, it seems that I'm not the only one in this...
    I'm glad they put a warning in the "Get Started" guide that's stickied.

    Wasn't able to do anything with another computer.
    The drivers would just fail when plugged in.

    It's worth the 100$ no doubt. But it's just unfortunate that this happened.
    I opened my other one and it came out of the box in Recovery Mode and had to use WebOS Dr to install the OS. Worked fine.

    But I just got off the phone with them as well, but through the HP # and they're sending a box for repair. 7-10 days. But it sucks that box won't come till almost Monday and then wait for it to be repaired and then waiting for it to come back... Better than getting a Refurb. I don't like the fact that the repair facility isn't close...
    The extra week doesn't bother me too much. I was without a Touchpad for 29 years before this. What is another 10 days?

    If I get a working one for, say, 6 months, then it will have been worth the $100. I'm just a little concerned about a device that crashes when using its own software. I feel bad for the people that bought them full price.
  7. #27  
    Quote Originally Posted by bvbull200 View Post
    Yeah. When I was on the HP website for support, it was called "WebOS Butler Service". Something that comes free for 90 days or something. I guess I'm waiting on the box, too. I was told I would get instructions via e-mail. I haven't received those yet, though.



    The extra week doesn't bother me too much. I was without a Touchpad for 29 years before this. What is another 10 days?

    If I get a working one for, say, 6 months, then it will have been worth the $100. I'm just a little concerned about a device that crashes when using its own software. I feel bad for the people that bought them full price.
    Did you try doctoring on another computer?
  8. #28  
    Quote Originally Posted by viper151 View Post
    Did you try doctoring on another computer?
    I did, but I shouldn't have to.

    I have an HP laptop running regular old 32-bit Windows Vista. A solution that only works on some computers (with no clear reason why) isn't much of a solution at all.

    I rooted my HTC Evo 4G and did all sorts of crazy stuff to it that was outside of HTC and Android's recommendations. I have been stuck in bootloops plenty of times on that phone, but there was always a way out of it.

    Plug my Touchpad in and use THEIR provided software? I end up having to send it back to HP for repair. Comical.

    I'm not going to be the expert on the board, by any means, but I'm far from being the clueless tech ignorant person as well. If I'm already having to concede defeat, think how the casual user must feel.
  9. #29  
    Quote Originally Posted by viper151 View Post
    Try doctoring on another computer.
    You do realize that the first one you posted was solved and the second one I guess it was solved since the OP never replied back.
    No bricked history yet.
    btw that first thread is mine and problem isnt fixed. its funny that you refuse to believe that you cant brick a touchpad when numerous people have reported the exact same issue.
    I think there should be a warning in the getting started thread about using webos dr to upgrade the firmware. if i hadnt of used that method i might still have a working touchpad.
  10. #30  
    If it turns on, it's not bricked.
    Quote Originally Posted by rwhitby View Post
    We always prefer that people donate in response to tangible items they can use today, rather than for intangible promises about the future that may or may not be possible to achieve.
  11. #31  
    Mine seems bricked too. hp on the screen stays on but no buttons do anything. I'm a newby so what is the "home" button?
  12. #32  
    Quote Originally Posted by rminor View Post
    Mine seems bricked too. hp on the screen stays on but no buttons do anything. I'm a newby so what is the "home" button?
    In portrait orientation, the headphone jack is on the top left, the power button is on the top right, the microUSB port is on center bottom. The home button is on the center bottom of the front face (above the microUSB port). The volume buttons are on the upper right side.

    First, try a hard reset by pressing the power button and home button at the same time and holding them for about 15 seconds. When you see the HP logo in center screen you can let go.
  13. Jace985's Avatar
    Posts
    46 Posts
    Global Posts
    119 Global Posts
    #33  
    Quote Originally Posted by rminor View Post
    Mine seems bricked too. hp on the screen stays on but no buttons do anything. I'm a newby so what is the "home" button?

    ya that's what happened to me and then I tried doctoring it for the last 5 hours and nothing used it on several different computers too still nothing so called hp and there sending me a box to get a replacement.
  14. mbudden's Avatar
    Posts
    50 Posts
    Global Posts
    957 Global Posts
       #34  
    Quote Originally Posted by jace985 View Post
    This just happened to me too Going to Call HP in the morning
    I talked to them via Online Chat first, and the guy told me to take it back where I got it from. So I ended up just calling them and they just took me through the whole key combos etc and then ended up escalating it to a repair.

    Quote Originally Posted by viper151 View Post
    Try doctoring on another computer.
    You do realize that the first one you posted was solved and the second one I guess it was solved since the OP never replied back.
    No bricked history yet.
    A. I tried it with 2 computers. Linux and Windows bro. Nada. B. Need to read those threads again.

    Quote Originally Posted by GodShapedHole View Post
    Unless HP drastically changed something about webOS, a bad flash won't brick your device. How I know? I've had bad doctoring experiences as well (accidentally pulled out cable once, had a broken cable that spontaneously stopped working another time, a few times where the doctor just stopped after certain points) and both my Pre and Pre+ still work fine.

    It's unlikely your TP is actually bricked as in BRICKED.
    Well you are correct that it isn't fully a dead brick, it does show up via USB cable on Windows and Linux. But novacom can't talk to it.



    Quote Originally Posted by jace985 View Post
    that'ts where mine is getting stuck at.. any tips?
    And what % is that stuck at?

    Quote Originally Posted by bvbull200 View Post
    Yeah. When I was on the HP website for support, it was called "WebOS Butler Service". Something that comes free for 90 days or something. I guess I'm waiting on the box, too. I was told I would get instructions via e-mail. I haven't received those yet, though.

    The extra week doesn't bother me too much. I was without a Touchpad for 29 years before this. What is another 10 days?

    If I get a working one for, say, 6 months, then it will have been worth the $100. I'm just a little concerned about a device that crashes when using its own software. I feel bad for the people that bought them full price.
    The lady on the phone said I would receive the instructions as well in a few hours after the call. Nothing yet, I assume once it processes through the Repairs or whatever it will be sent.

    Quote Originally Posted by zakos12 View Post
    btw that first thread is mine and problem isnt fixed. its funny that you refuse to believe that you cant brick a touchpad when numerous people have reported the exact same issue.
    I think there should be a warning in the getting started thread about using webos dr to upgrade the firmware. if i hadnt of used that method i might still have a working touchpad.
    Well, that's the thing. I bought two, first one updated fine. The second one didn't.

    Quote Originally Posted by Jakeeeee View Post
    If it turns on, it's not bricked.
    Bro. Read the thread. Nothing turns on.

    Quote Originally Posted by rminor View Post
    Mine seems bricked too. hp on the screen stays on but no buttons do anything. I'm a newby so what is the "home" button?
    Home button is the little oval button with the light in the middle near the USB charging port.
  15. #35  
    ok, the hp info called that a "Center" button. The hp logo stays lite on mine. Tried it and it reset. Don't know weather to try the doctor again or wait and see if the regular update will start working. Thanks very much for the info.
  16. #36  
    Quote Originally Posted by rminor View Post
    ok, the hp info called that a "Center" button. The hp logo stays lite on mine. Tried it and it reset. Don't know weather to try the doctor again or wait and see if the regular update will start working. Thanks very much for the info.
    Try the over-the-air update to 3.0.2 first. I know that the HP servers have been slammed with all the new owners who are trying to update. You might want to try it in an off peak time. Let us know how it goes.
  17. Jace985's Avatar
    Posts
    46 Posts
    Global Posts
    119 Global Posts
    #37  
    It get's stuck at 12%
  18. #38  
    I would say there's a difference between a defective device and a 'bricked' by using homebrew or the doctor. Remember that HP provides the doctor so it's not a "non covered use"

    If it won't turn on at all, no lights or anything, then it's defective. It was going to fail. Let them 'repair/replace it'

    Who said there's never been a hardware failure? This IMHO is!
    IIIXE>Clie:N710C>N760C>NX60>Treo[600>650>700]>Centro>Pre+>Pre2&Touchpad 32GB
    webOS Themes: star-trek-universe star-trek-future Future Trek for Tpad

    My CV: http://visualcv.com/egadgetguy
    viper151 and Cantaffordit like this.
  19. 27scoob's Avatar
    Posts
    169 Posts
    Global Posts
    334 Global Posts
    #39  
    Yeah "bricked" has nothing to do with being defective , So to try and lable it that way is very misleading . Especially to those that are new to WebOs . However hardware failure happens in all electronics.
    Cantaffordit and Soorma like this.
  20. #40  
    Mine is doing the same damn thing now. I woke up to it stuck at the HP boot logo, when I try to restore using WebOS Doctor it gets stuck at 12%.

    I had previously used WebOS Doctor without issues to update it.
Page 2 of 6 FirstFirst 123456 LastLast

Posting Permissions