Results 1 to 9 of 9
  1. diomark's Avatar
    Posts
    752 Posts
    Global Posts
    770 Global Posts
       #1  
    I found out the hard way that running /usr/bin/PmUpdater bricks your phone

    root@castle:/etc/init.d# /usr/bin/PmUpdater
    [ReadRetryCount: 1314]: Could not open /var/lib/software/updating




    Broadcast message from mhr@castle
    (/dev/pts/0) at 14:39 ...

    The system is going down for reboot NOW!

    Broadcast message from mhr@castle
    (/dev/pts/0) at 14:39 ...

    The system is going down for reboot NOW!
    root@castle:/etc/init.d#


    After autoamtically rebooting, I'm getting the palm.com/ROM message

    Any way to recover from this short of running webos dr?

    ..and I guess while I'm at it, where is the 1.2 webos Dr?
    -mark
  2. diomark's Avatar
    Posts
    752 Posts
    Global Posts
    770 Global Posts
       #2  
    OK - found 1.2.. and I guess despite the warnings I'm going to go to it (I can always restore old version later if I re-brick.) - for those of you that need it, it's here - MEGAUPLOAD - The leading online storage and file delivery service

    Before running this though, any tips on recovering without re-installing?

    -mark
  3. awrnsmn's Avatar
    Posts
    646 Posts
    Global Posts
    689 Global Posts
    #3  
    Can you unzip webosdoc 1.1 and grab the files you need to replace/fix? I do this all the time do to bricking/breaking trying to tweek.
  4. #4  
    Quote Originally Posted by diomark View Post
    I found out the hard way that running /usr/bin/PmUpdater bricks your phone
    If you were able to recover it using the webOS Doctor, then technically it is not bricked, just "temporarily unresponsive"

    -- Rod
    WebOS Internals and Preware Founder and Developer
    You may wish to donate by Paypal to donations @ webos-internals.org if you find our work useful.
    All donations go back into development.
    www.webos-internals.org twitter.com/webosinternals facebook.com/webosinternals
  5. acydlord's Avatar
    Posts
    67 Posts
    Global Posts
    72 Global Posts
    #5  
    Sounds more like a reboot loop than a brick to me. As mentioned above, extract WebOS Dr to get files needed, or just Dr it. Looks to me like the problem stemmed because the device wasn't in RW mode so it threw an exception.
  6. ird
    ird is offline
    ird's Avatar
    Posts
    156 Posts
    Global Posts
    167 Global Posts
    #6  
    Bricked = No chance of recovery. That's why it's called bricked.
  7. #7  
    To brick.......or not to brick..... That is the question ?! Ha!
    ĦṔ-Ḷṫ-Ŧḯη
    Here is a direct link to webOS Doc for all carriers
    http://www.webos-internals.org/wiki/...octor_Versions
    P.S. if i have helped you and you are thankful please hit the thanks button to the right---->
  8. #8  
    the REAL question would have been if he could get into the phone with novatem.

    If so, then it was only unresponsive inthe mojo gui... and then it UTTERLY was fixable.

    But command line intimidates so many people
  9. diomark's Avatar
    Posts
    752 Posts
    Global Posts
    770 Global Posts
       #9  
    Quote Originally Posted by rboatright View Post
    the REAL question would have been if he could get into the phone with novatem.

    If so, then it was only unresponsive inthe mojo gui... and then it UTTERLY was fixable.

    But command line intimidates so many people

    Novaterm wasn't responding.. It was immediately coming up w/ the palm.com/rom message

    I've re-built using webos 1.2 now (It's FAST btw) - but having exchange issue my exchange email account that worked perfectly fine before is refusing to work now I posted about it here - http://forums.precentral.net/palm-pr...nnect-eas.html - anyone seen this?
    -mark

Posting Permissions