Page 173 of 217 FirstFirst ... 73123163168169170171172173174175176177178183 ... LastLast
Results 3,441 to 3,460 of 4324
Like Tree19Likes
  1. #3441  
    ok sorry , I'm really not a computer genius but would love to know what software do you guys use to create a log or the to take pictures of the screen tks and i will post them tks.
  2. #3442  
    Quote Originally Posted by toaste View Post
    WARNING: Unable to connect to NovaCOMd -- is it running???
    This is the problem.


    M.
  3. #3443  
    Quote Originally Posted by Xanadu73 View Post
    This is the problem.


    M.
    Even if Win7 shows a message box saying Novacom is being configured when Meta-doctor is running? I've restarted Novacom manually before at the "connect your phone screen" to make sure it's running and I get the "just charge" screen and hear the connect beep. If I choose USB Drive, the computer sees the Pre+.

    All that being said, options? I've again gone to the How to Recover page and followed those steps and still no luck.

    latest log and I made sure I saw the windows message about Novacom being configured:

    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:13 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:14 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:15 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:16 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:17 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:18 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:19 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:20 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:21 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:22 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:23 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:24 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:25 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:26 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:27 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:28 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:29 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:30 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:31 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:32 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:33 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:34 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:35 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:36 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 7:23:37 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 7:23:38 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)

    Jade@Jade-PC ~/meta-doctor
    $
  4. #3444  
    I would liek to thank Rod for his advice on running the meta-sprint-pre-2.1.0 script from a source other than widnows. i used ubuntu and now have my spritn pre+ running webos 2.1.0. Thank you again very much. I will be giving my donation in about 5 minutes.
  5. #3445  
    Quote Originally Posted by flipmode007 View Post
    ok sorry , I'm really not a computer genius but would love to know what software do you guys use to create a log or the to take pictures of the screen tks and i will post them tks.
    I've been using Cygwin and in the upper left corner is an icon, click on it and choose Edit then Select All, reclick the icon and choose Edit then Copy and you can paste into your message here. I've not been able to get the whole log of actions for some reason, but am able to get some when I do this process.

    Hope that helps some.
  6.    #3446  
    Quote Originally Posted by toaste View Post
    As far as I know, running the meta-doctor directly from the folder it makes (not in Cygwin) does not create a log, but I fully know I could be wrong and just not know where to find it. It would be nice for the first page to either say how to get such a log, to give a link on how to do it, or say the log has to come from Cygwin or such programs.

    So, off to run Cygwin and see if I can figure out how to get a log and post it here. Thanks for your patience.
    Don't click on the jar file, run it from the command line.

    java -jar <doctor-file>

    then you get the full console output.

    -- 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
  7. #3447  
    Quote Originally Posted by rwhitby View Post
    Don't click on the jar file, run it from the command line.

    java -jar <doctor-file>

    then you get the full console output.

    -- Rod
    I did as you instructed (thanks for the hint on doing it this way) and got the below log before I had to close meta-doctor as it would not see the Pre+:

    Your group is currently "mkgroup". This indicates that neither
    your gid nor your pgsid (primary group associated with your SID)
    is in /etc/group.

    The /etc/group (and possibly /etc/passwd) files should be rebuilt.
    See the man pages for mkpasswd and mkgroup then, for example, run

    mkpasswd -l [-d] > /etc/passwd
    mkgroup -l [-d] > /etc/group

    Note that the -d switch is necessary for domain users.

    Jade@Jade-PC ~
    $ cd meta-doctor

    Jade@Jade-PC ~/meta-doctor
    $ java -jar build/meta-verizon-preplus-2.1.0/webosdoctorp101ueu-wr-2.1.0.jar
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: baseBuild webOS.tar
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: customizationBuild wr-castle-plus.tar
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: prevBaseBuild null
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: prevCustomizationBuild null
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: DeviceType: castle
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: WcpSubmssion: 18
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: ForceModemUpdate: true
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: RomBuildNumber: 285
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: BaseBuild: webOS.tar
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: RecoveryToolBuildNumber: 297
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: AppSubmssion: 81
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: RecoveryToolBuildTime: 03/03/11 01:55
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: VersionStr: HP webOS 2.1.0
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: ApprovalMikeHash: H4sIAIUkdEwAA+3OPQ6CQBCG4a09BSfAmWVhD2BsjZWUhoQNIZElQfw5
    vkhpbCzA5n2aL5lM8abbrq/D5Xw47dLxOZolyKRw7r3qc5nWZs7KfJ+pGFXrnea28NaI5pl6k8giNR9u
    17EaksQM4d6GR12Fro/f/kJs2hjC0MZmjay1HFV0X5abf3cAAAAAAAAAAAAAAAAAAH7zAgtCP3UAKAAA

    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: CustomizationBuild: wr-castle-plus.tar
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: ApprovalBuildName: H4sIACX1bk0AA+3OuQoCQRBF0Y79ig41GXorB1MxEww0Mmy0kIFZZMb
    l910iBVM1uSd5UFRwj0NxzHVzHYpd15jvcHfTlB7rS3H3DTEF97w/STDeS4xShpTEOC8hlca6L/W8OQ+
    n3Ftrer1Uet1nbbr205+2h6pV7av28IusX1lrrXlQOz9X9d6ucqPWF7EIdrxZLGdRluvtLCaRyejfpQA
    AAAAAAAAAAAAAAACAVzcxwkwtACgAAA==
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: LibCoreSubmssion: 122
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.ConfigFileMgr loadCo
    nfiguration
    INFO: ApprovalCharlieHash: H4sIALO0Ek0AA+3RPQrCQBCG4a09RU4Q9ycmt7CwsA2L2WILd2FMY
    vD0GrSwEFRSiPA+zVfMBzMw5frgRWKQdptH3+6DxEtO7S77ToaUgpT91Ktl9E1dVXOaZqOf885oZYxrt
    KutM1ZpO1OFXrj3I8Op91IUSsIYw7nz4ZjTq967+Z96PHz16zsAAAAAAAAAAAAAAAAAAN+5Am2DoIYAK
    AAA
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.CardController <init
    >
    INFO: +++++CardController
    Apr 3, 2011 8:09:12 PM com.palm.nova.installer.recoverytool.CardController <init
    >
    INFO: getLocale is : en_GB
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: +++++checkAndInstallDrivers
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: Java Os Name: WINDOWS 7
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: Java Os Arch: X86
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: Java Os version: 6.1
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: java version: 1.6.0_24
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: java home: C:\Program Files (x86)\Java\jre6
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: java tmp dir: C:\Users\Jade\
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: java vendor: Sun Microsystems Inc.
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: java vm version: 19.1-b02
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: java vm vendor: Sun Microsystems Inc.
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: user lang: null
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr is64bitWin
    dows
    INFO: +++++is64bitWindows
    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: Here is Std Error Stream output of the command:

    Apr 3, 2011 8:12:23 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: Here is Std Input Stream output of the command:

    Apr 3, 2011 8:12:31 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: "JADE-PC","Microsoft Windows 7 Home Premium ","6.1.7600 N/A Build 7600","M
    icrosoft Corporation","Standalone Workstation","Multiprocessor Free","Jade","","
    00359-OEM-8992687-00118","12/25/2010, 1:38:38 PM","4/3/2011, 5:43:14 PM","ASUSTe
    K Computer INC.","CG1330","x64-based PC","1 Processor(s) Installed.,[01]: AMD64
    Family 16 Model 10 Stepping 0 AuthenticAMD ~2700 Mhz","American Megatrends Inc.
    0403 , 6/21/2010","C:\Windows","C:\Windows\system32","\Device\HarddiskVolume2"
    ,"en-us;English (United States)","en-us;English (United States)","(UTC-07:00) Mo
    untain Time (US & Canada)","7,935 MB","5,298 MB","15,869 MB","12,768 MB","3,101
    MB","C:\pagefile.sys","WORKGROUP","\\JADE-PC","110 Hotfix(s) Installed.,[01]: KB
    971033,[02]: KB2032276,[03]: KB2079403,[04]: KB2120976,[05]: KB2207566,[06]: KB2
    249857,[07]: KB2281679,[08]: KB2284742,[09]: KB2286198,[10]: KB2296011,[11]: KB2
    296199,[12]: KB2305420,[13]: KB2345886,[14]: KB2347290,[15]: KB2378111,[16]: KB2
    385678,[17]: KB2387149,[18]: KB2387530,[19]: KB2388210,[20]: KB2393802,[21]: KB2
    416400,[22]: KB2416471,[23]: KB2419640,[24]: KB2423089,[25]: KB2425227,[26]: KB2
    436673,[27]: KB2442962,[28]: KB2443685,[29]: KB2447568,[30]: KB2454826,[31]: KB2
    467023,[32]: KB2467659,[33]: KB2475792,[34]: KB2479628,[35]: KB2479943,[36]: KB2
    482017,[37]: KB2483614,[38]: KB2484033,[39]: KB2485376,[40]: KB2487426,[41]: KB2
    505438,[42]: KB2524375,[43]: KB958488,[44]: KB971468,[45]: KB972270,[46]: KB9735
    25,[47]: KB973874,[48]: KB974332,[49]: KB974431,[50]: KB974455,[51]: KB974571,[5
    2]: KB975053,[53]: KB975364,[54]: KB975467,[55]: KB975496,[56]: KB975560,[57]: K
    B976092,[58]: KB976098,[59]: KB976264,[60]: KB976325,[61]: KB976422,[62]: KB9766
    62,[63]: KB976749,[64]: KB976902,[65]: KB976972,[66]: KB977074,[67]: KB977617,[6
    8]: KB977863,[69]: KB978207,[70]: KB978251,[71]: KB978262,[72]: KB978506,[73]: K
    B978542,[74]: KB978601,[75]: KB978637,[76]: KB978886,[77]: KB979099,[78]: KB9793
    06,[79]: KB979309,[80]: KB979482,[81]: KB979538,[82]: KB979559,[83]: KB979683,[8
    4]: KB979687,[85]: KB979688,[86]: KB979900,[87]: KB979916,[88]: KB980182,[89]: K
    B980195,[90]: KB980218,[91]: KB980232,[92]: KB980302,[93]: KB980408,[94]: KB9808
    46,[95]: KB981078,[96]: KB981332,[97]: KB981793,[98]: KB981852,[99]: KB981889,[1
    00]: KB981981,[101]: KB982110,[102]: KB982132,[103]: KB982214,[104]: KB982300,[1
    05]: KB982381,[106]: KB982519,[107]: KB982632,[108]: KB982665,[109]: KB982799,[1
    10]: KB983590","2 NIC(s) Installed.,[01]: Realtek PCIe GBE Family Controller,
    Connection Name: Local Area Connection, DHCP Enabled: Yes, DHCP
    Server: 192.168.2.1, IP address(es), [01]: 192.168.2.3, [02]:
    fe80::188b:aeb:46bc:3b8d,[02]: Bluetooth Device (Personal Area Network), C
    onnection Name: Bluetooth Network Connection, Status: Media discon
    nected"
    Apr 3, 2011 8:12:31 PM com.palm.nova.installer.core.DesktopDriversMgr is64bitWin
    dows
    INFO: systeminfo.exe query exited with: 0
    Apr 3, 2011 8:12:56 PM com.palm.nova.installer.core.DesktopDriversMgr is64bitWin
    dows
    INFO: Windows 64 Bit Support Available: true
    Apr 3, 2011 8:12:56 PM com.palm.nova.installer.core.DesktopDriversMgr is64bitWin
    dows
    INFO: -----is64bitWindows
    Apr 3, 2011 8:12:56 PM com.palm.nova.installer.core.DesktopDriversMgr installWin
    dowsDrivers
    INFO: +++++installWindowsDrivers
    Apr 3, 2011 8:12:56 PM com.palm.nova.installer.core.DesktopDriversMgr doesWindow
    sDriverNeedUpdating
    INFO: +++++doesWindowsDriverNeedUpdating
    Apr 3, 2011 8:12:56 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: Here is Std Error Stream output of the command:

    Apr 3, 2011 8:12:56 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: Here is Std Input Stream output of the command:

    Apr 3, 2011 8:12:56 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: ERROR: The system was unable to find the specified registry key or value.
    Apr 3, 2011 8:12:56 PM com.palm.nova.installer.core.DesktopDriversMgr doesWindow
    sDriverNeedUpdating
    INFO: reg.exe query exited with: 1
    Apr 3, 2011 8:12:56 PM com.palm.nova.installer.core.DesktopDriversMgr doesWindow
    sDriverNeedUpdating
    INFO: -----doesWindowsDriverNeedUpdating
    Apr 3, 2011 8:12:56 PM com.palm.nova.installer.core.DesktopDriversMgr installWin
    dowsDrivers
    INFO: reading in driver to stream
    Apr 3, 2011 8:12:57 PM com.palm.nova.installer.core.DesktopDriversMgr installWin
    dowsDrivers
    INFO: New Windows Driver Install
    Apr 3, 2011 8:12:57 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: Here is Std Error Stream output of the command:

    Apr 3, 2011 8:12:57 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: Here is Std Input Stream output of the command:

    Apr 3, 2011 8:18:01 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: Here is Std Input Stream output of the command:

    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: "JADE-PC","Microsoft Windows 7 Home Premium ","6.1.7600 N/A Build 7600","M
    icrosoft Corporation","Standalone Workstation","Multiprocessor Free","Jade","","
    00359-OEM-8992687-00118","12/25/2010, 1:38:38 PM","4/3/2011, 5:43:14 PM","ASUSTe
    K Computer INC.","CG1330","x64-based PC","1 Processor(s) Installed.,[01]: AMD64
    Family 16 Model 10 Stepping 0 AuthenticAMD ~2700 Mhz","American Megatrends Inc.
    0403 , 6/21/2010","C:\Windows","C:\Windows\system32","\Device\HarddiskVolume2"
    ,"en-us;English (United States)","en-us;English (United States)","(UTC-07:00) Mo
    untain Time (US & Canada)","7,935 MB","5,278 MB","15,869 MB","12,751 MB","3,118
    MB","C:\pagefile.sys","WORKGROUP","\\JADE-PC","110 Hotfix(s) Installed.,[01]: KB
    971033,[02]: KB2032276,[03]: KB2079403,[04]: KB2120976,[05]: KB2207566,[06]: KB2
    249857,[07]: KB2281679,[08]: KB2284742,[09]: KB2286198,[10]: KB2296011,[11]: KB2
    296199,[12]: KB2305420,[13]: KB2345886,[14]: KB2347290,[15]: KB2378111,[16]: KB2
    385678,[17]: KB2387149,[18]: KB2387530,[19]: KB2388210,[20]: KB2393802,[21]: KB2
    416400,[22]: KB2416471,[23]: KB2419640,[24]: KB2423089,[25]: KB2425227,[26]: KB2
    436673,[27]: KB2442962,[28]: KB2443685,[29]: KB2447568,[30]: KB2454826,[31]: KB2
    467023,[32]: KB2467659,[33]: KB2475792,[34]: KB2479628,[35]: KB2479943,[36]: KB2
    482017,[37]: KB2483614,[38]: KB2484033,[39]: KB2485376,[40]: KB2487426,[41]: KB2
    505438,[42]: KB2524375,[43]: KB958488,[44]: KB971468,[45]: KB972270,[46]: KB9735
    25,[47]: KB973874,[48]: KB974332,[49]: KB974431,[50]: KB974455,[51]: KB974571,[5
    2]: KB975053,[53]: KB975364,[54]: KB975467,[55]: KB975496,[56]: KB975560,[57]: K
    B976092,[58]: KB976098,[59]: KB976264,[60]: KB976325,[61]: KB976422,[62]: KB9766
    62,[63]: KB976749,[64]: KB976902,[65]: KB976972,[66]: KB977074,[67]: KB977617,[6
    8]: KB977863,[69]: KB978207,[70]: KB978251,[71]: KB978262,[72]: KB978506,[73]: K
    B978542,[74]: KB978601,[75]: KB978637,[76]: KB978886,[77]: KB979099,[78]: KB9793
    06,[79]: KB979309,[80]: KB979482,[81]: KB979538,[82]: KB979559,[83]: KB979683,[8
    4]: KB979687,[85]: KB979688,[86]: KB979900,[87]: KB979916,[88]: KB980182,[89]: K
    B980195,[90]: KB980218,[91]: KB980232,[92]: KB980302,[93]: KB980408,[94]: KB9808
    46,[95]: KB981078,[96]: KB981332,[97]: KB981793,[98]: KB981852,[99]: KB981889,[1
    00]: KB981981,[101]: KB982110,[102]: KB982132,[103]: KB982214,[104]: KB982300,[1
    05]: KB982381,[106]: KB982519,[107]: KB982632,[108]: KB982665,[109]: KB982799,[1
    10]: KB983590","2 NIC(s) Installed.,[01]: Realtek PCIe GBE Family Controller,
    Connection Name: Local Area Connection, DHCP Enabled: Yes, DHCP
    Server: 192.168.2.1, IP address(es), [01]: 192.168.2.3, [02]:
    fe80::188b:aeb:46bc:3b8d,[02]: Bluetooth Device (Personal Area Network), C
    onnection Name: Bluetooth Network Connection, Status: Media discon
    nected"
    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr is64bitWin
    dows
    INFO: systeminfo.exe query exited with: 0
    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr is64bitWin
    dows
    INFO: Windows 64 Bit Support Available: true
    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr is64bitWin
    dows
    INFO: -----is64bitWindows
    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr installWin
    dowsDrivers
    INFO: +++++installWindowsDrivers
    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr doesWindow
    sDriverNeedUpdating
    INFO: +++++doesWindowsDriverNeedUpdating
    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: Here is Std Error Stream output of the command:

    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: Here is Std Input Stream output of the command:

    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: ERROR: The system was unable to find the specified registry key or value.
    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr doesWindow
    sDriverNeedUpdating
    INFO: reg.exe query exited with: 1
    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr doesWindow
    sDriverNeedUpdating
    INFO: -----doesWindowsDriverNeedUpdating
    Apr 3, 2011 8:18:09 PM com.palm.nova.installer.core.DesktopDriversMgr installWin
    dowsDrivers
    INFO: reading in driver to stream
    Apr 3, 2011 8:18:10 PM com.palm.nova.installer.core.DesktopDriversMgr installWin
    dowsDrivers
    INFO: New Windows Driver Install
    Apr 3, 2011 8:18:10 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: Here is Std Error Stream output of the command:

    Apr 3, 2011 8:18:10 PM com.palm.nova.installer.core.DesktopDriversMgr$OffloadedS
    treamReader run
    INFO: Here is Std Input Stream output of the command:

    Apr 3, 2011 8:18:14 PM com.palm.nova.installer.core.DesktopDriversMgr execIgnore
    Output
    INFO: msiexec /i C:\Users\Jade\NovacomInstaller_x64.msi /passive exited with: 0
    Apr 3, 2011 8:18:16 PM com.palm.nova.installer.core.DesktopDriversMgr installWin
    dowsDrivers
    INFO: MSIEXED exited with: 0
    Apr 3, 2011 8:18:16 PM com.palm.nova.installer.core.DesktopDriversMgr installWin
    dowsDrivers
    INFO: -----installWindowsDrivers
    Apr 3, 2011 8:18:16 PM com.palm.nova.installer.core.DesktopDriversMgr checkAndIn
    stallDrivers
    INFO: -----checkAndInstallDrivers
    Apr 3, 2011 8:18:17 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 8:18:18 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 8:18:19 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 8:18:20 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 8:18:21 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 8:18:22 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 8:18:23 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 8:18:24 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 8:23:36 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 8:23:37 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)
    Apr 3, 2011 8:23:38 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Apr 3, 2011 8:23:39 PM com.palm.nova.installer.recoverytool.runner.DeviceDiscove
    ryRunner$DeviceDiscoveryThread run
    WARNING: Unable to connect to NovaCOMd -- is it running???
    java.net.ConnectException: Connection refused: connect
    at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.PlainSocketImpl.doConnect(Unknown Source)
    at java.net.PlainSocketImpl.connectToAddress(Unknown Source)
    at java.net.PlainSocketImpl.connect(Unknown Source)
    at java.net.SocksSocketImpl.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.connect(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at java.net.Socket.<init>(Unknown Source)
    at com.palm.novacom.internal.NovacomController.getDeviceList(NovacomCont
    roller.java:41)
    at com.palm.novacom.internal.NovacomController.getDeviceListOnUsb(Novaco
    mController.java:55)
    at com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$Dev
    iceDiscoveryThread.run(DeviceDiscoveryRunner.java:63)

    Jade@Jade-PC ~/meta-doctor
    $

    After I did this, I put the Pre into recovery mode and tried again, but got the same result. I still got the message that Novacom was being started for this and the previous attempt.
  8. #3448  
    I will say that if you can read the wiki's and follow directions very good then it is so much easier to use linux software to do this. I used ubuntu with the dual boot mode using wubi. And it was so much simpler using that then windows. I just find windows to mess things up more than it does make things easier. I'll be using ubuntu from now on with anything involving webos. Thanks you again Rod you are truelly a good man to help us out all the time. I know it has to get frustrating.

    Tony
  9. #3449  
    Quote Originally Posted by SprintPre-1983 View Post
    I will say that if you can read the wiki's and follow directions very good then it is so much easier to use linux software to do this. I used ubuntu with the dual boot mode using wubi. And it was so much simpler using that then windows. I just find windows to mess things up more than it does make things easier. I'll be using ubuntu from now on with anything involving webos. Thanks you again Rod you are truelly a good man to help us out all the time. I know it has to get frustrating.

    Tony
    Thanks. I think I'll try this route out as well and see what happens. Will be a few days till I have time to allocate for this task, so I'll just have to wait.
  10. #3450  
    No problem toaste if you have any question I will surelly try to help you if I can.
  11. #3451  
    I did eventually get this work. My issue in the end was with using the CygWin compiled Metadoctor. The Linux compiled version worked exactly as it needed to.
  12. #3452  
    Quote Originally Posted by brgruell View Post
    I did eventually get this work. My issue in the end was with using the CygWin compiled Metadoctor. The Linux compiled version worked exactly as it needed to.
    I vote to remove the cygwin instructions in the thread and the wiki and leave only MacOS and Linux (Virtual machine or Wubi install)

    Who's with me? hehehe
    Just remember: If I helped you, press the thanks button!

    Owner of: Pre Sprint, Pre Telcel, Pre Plus AT&T, Pre 2 Unlocked, Pixi Plus AT&T, and 2 TouchPads (my Pre3 was stolen so it won't appear again here).
    Needs: Veer (anyone?)
    Apps: Subnet Calculator, FreeCam, PhotoFun, NuttyPad (work in progress)
    HomeBrew: meta-doctor and Messaging Plugins collaborator
    Twitter: @cesarneg
  13. #3453  
    Quote Originally Posted by NuttyBunny View Post
    I vote to remove the cygwin instructions in the thread and the wiki and leave only MacOS and Linux (Virtual machine or Wubi install)

    Who's with me? hehehe
    I used the cygwin method 3-4 weeks ago to create about 8 or 10 Meta-doctors over a period of about 6 days. Worked perfectly every time (and I'd only previously created just one meta-doctor once back in December for my Sprint Pre+ conversion.)

    I have minimal linux experience and had never used Cygwin before December but it was as easy as pie for me. Don't know if something significant has changed in the Meta-Dr scripts since then, so I won't lobby to keep the Cygwin option, but just wanted to post my positive experiences as context.
  14. #3454  
    Quote Originally Posted by greenawayj View Post
    I used the cygwin method 3-4 weeks ago to create about 8 or 10 Meta-doctors over a period of about 6 days. Worked perfectly every time (and I'd only previously created just one meta-doctor once back in December for my Sprint Pre+ conversion.)

    I have minimal linux experience and had never used Cygwin before December but it was as easy as pie for me. Don't know if something significant has changed in the Meta-Dr scripts since then, so I won't lobby to keep the Cygwin option, but just wanted to post my positive experiences as context.
    The problem is that there are about 2 versions of Windows XP, 5 versions of Vista, 8 of Windows 7 (just throwing numbers), with different permissions settings, it's hard to support them all. On the other hand, the wiki mentions ubuntu, and it "just works" under that OS. I really don't support removing the windows/cygwin instructions, but if you read the thread, you'll find that most problems come from windows/cygwin builds, and the few remaining are for using linux on a virtual machine and having not been able to move the doctor to their main OS, or trying to run it directly on the VM.

    So, my position switches from "remove cygwin support" to "If you will use cygwin, please read the entire thread".

    Just remember: If I helped you, press the thanks button!

    Owner of: Pre Sprint, Pre Telcel, Pre Plus AT&T, Pre 2 Unlocked, Pixi Plus AT&T, and 2 TouchPads (my Pre3 was stolen so it won't appear again here).
    Needs: Veer (anyone?)
    Apps: Subnet Calculator, FreeCam, PhotoFun, NuttyPad (work in progress)
    HomeBrew: meta-doctor and Messaging Plugins collaborator
    Twitter: @cesarneg
  15. #3455  
    Quote Originally Posted by NuttyBunny View Post
    The problem is that there are about 2 versions of Windows XP, 5 versions of Vista, 8 of Windows 7 (just throwing numbers), with different permissions settings, it's hard to support them all. On the other hand, the wiki mentions ubuntu, and it "just works" under that OS. I really don't support removing the windows/cygwin instructions, but if you read the thread, you'll find that most problems come from windows/cygwin builds, and the few remaining are for using linux on a virtual machine and having not been able to move the doctor to their main OS, or trying to run it directly on the VM.

    So, my position switches from "remove cygwin support" to "If you will use cygwin, please read the entire thread".

    I tried using ubuntu couldn't get it to work, I then switched to cygwin and haven't had problem with it. I've used it on windows xp(home/pro)x86 Vista(Home basic/home premium)x86 windows 7(home premium/Ultimate)x86 and the only thing I had to do different was set the UAC to allow on both vista and 7 versions.

    But... I think my experience along with the others with using cygwin on windows is unique.

    so I like the "If you will use cygwin, please read the entire thread" recommendation from NuttyBunny
  16. #3456  
    Already up-to-date.
    rm -rf build
    fatal: destination path 'meta-doctor' already exists and is not an empty directo
    ry.
    DEVICE = preplus
    CARRIER = wr

    VERSION = 2.1.0
    ENABLE_DEVELOPER_MODE = 1
    DISABLE_UPLOAD_DAEMON = 1
    DISABLE_UPDATE_DAEMON = 1
    CUSTOM_WEBOS_TARBALL = webOS.tar
    CUSTOM_BUILD_INFO = palm-build-info
    CUSTOM_WEBOS_DMSET = 393
    CUSTOM_CARRIER_DMSET = 398
    CUSTOM_MODEL_LIST = P100EWW
    CUSTOM_CARRIER_LIST = bell
    CUSTOM_BOOTLOGO = scripts/WebOS-Internals.tga

    Your custom doctor file will be created at build/meta-bellmo-pre-2.1.0/webosdoct
    orp101ueu-wr-2.1.0.jar

    rm -rf build/pre-p100eww-bellmo-1.4.5
    mkdir -p build/pre-p100eww-bellmo-1.4.5
    cp downloads/webosdoctorp100ewwbellmo-1.4.5.jar build/pre-p100eww-bellmo-1.4.5/w
    ebosdoctorp100ewwbellmo-1.4.5.jar
    ( cd build/pre-p100eww-bellmo-1.4.5 ; \
    unzip -q webosdoctorp100ewwbellmo-1.4.5.jar META-INF/MANIFEST.MF
    com/* \
    resources/webOS.tar resources/recoverytool.config )
    ( cd build/pre-p100eww-bellmo-1.4.5 ; \
    unzip -q webosdoctorp100ewwbellmo-1.4.5.jar resources/bellmo.tar
    )
    mkdir -p build/pre-p100eww-bellmo-1.4.5/webOS
    tar -C build/pre-p100eww-bellmo-1.4.5/webOS \
    -f build/pre-p100eww-bellmo-1.4.5/resources/webOS.tar -x
    cp scripts/WebOS-Internals.tga build/pre-p100eww-bellmo-1.4.5/webOS/BootLogo.tga

    mkdir -p build/pre-p100eww-bellmo-1.4.5/carrier
    tar -f build/pre-p100eww-bellmo-1.4.5/resources/bellmo.tar -t \
    > build/pre-p100eww-bellmo-1.4.5/carrier/carrier-file-list.txt
    tar -C build/pre-p100eww-bellmo-1.4.5/carrier \
    -f build/pre-p100eww-bellmo-1.4.5/resources/bellmo.tar -x
    gunzip -f build/pre-p100eww-bellmo-1.4.5/webOS/nova-cust-image-castle.rootfs.tar
    .gz
    mkdir -p build/pre-p100eww-bellmo-1.4.5/rootfs
    tar -C build/pre-p100eww-bellmo-1.4.5/rootfs --wildcards \
    -f build/pre-p100eww-bellmo-1.4.5/webOS/nova-cust-image-castle.r
    ootfs.tar \
    -x ./usr/palm/applications/com.palm.app.firstuse ./usr/lib/ipkg/
    info ./etc/ssl ./usr/bin ./boot ./lib/modules ./etc/palm-build-info ./md5sums*
    touch build/pre-p100eww-bellmo-1.4.5/.unpacked
    rm -rf build/pre2-p102eww-verizonwireless-2.0.1
    mkdir -p build/pre2-p102eww-verizonwireless-2.0.1
    cp downloads/webosdoctorp102verizonwireless-2.0.1.jar build/pre2-p102eww-verizon
    wireless-2.0.1/webosdoctorp102verizonwireless-2.0.1.jar
    ( cd build/pre2-p102eww-verizonwireless-2.0.1 ; \
    unzip -q webosdoctorp102verizonwireless-2.0.1.jar META-INF/MANIF
    EST.MF com/* \
    resources/webOS.tar resources/recoverytool.config )
    ( cd build/pre2-p102eww-verizonwireless-2.0.1 ; \
    unzip -q webosdoctorp102verizonwireless-2.0.1.jar resources/veri
    zon.tar )
    mkdir -p build/pre2-p102eww-verizonwireless-2.0.1/webOS
    tar -C build/pre2-p102eww-verizonwireless-2.0.1/webOS \
    -f build/pre2-p102eww-verizonwireless-2.0.1/resources/webOS.tar
    -x
    cp scripts/WebOS-Internals.tga build/pre2-p102eww-verizonwireless-2.0.1/webOS/Bo
    otLogo.tga
    mkdir -p build/pre2-p102eww-verizonwireless-2.0.1/carrier
    tar -f build/pre2-p102eww-verizonwireless-2.0.1/resources/verizon.tar -t \
    > build/pre2-p102eww-verizonwireless-2.0.1/carrier/carrier-file-
    list.txt
    tar -C build/pre2-p102eww-verizonwireless-2.0.1/carrier \
    -f build/pre2-p102eww-verizonwireless-2.0.1/resources/verizon.ta
    r -x
    gunzip -f build/pre2-p102eww-verizonwireless-2.0.1/webOS/nova-cust-image-roadrun
    ner.rootfs.tar.gz
    mkdir -p build/pre2-p102eww-verizonwireless-2.0.1/rootfs
    tar -C build/pre2-p102eww-verizonwireless-2.0.1/rootfs --wildcards \
    -f build/pre2-p102eww-verizonwireless-2.0.1/webOS/nova-cust-imag
    e-roadrunner.rootfs.tar \
    -x ./usr/palm/applications/com.palm.app.firstuse ./usr/lib/ipkg/
    info ./etc/ssl ./usr/bin ./boot ./lib/modules ./etc/palm-build-info ./md5sums*
    touch build/pre2-p102eww-verizonwireless-2.0.1/.unpacked
    rm -rf build/preplus-p101ueu-wr-2.1.0
    mkdir -p build/preplus-p101ueu-wr-2.1.0
    cp downloads/webosdoctorp101ueu-wr-2.1.0.jar build/preplus-p101ueu-wr-2.1.0/webo
    sdoctorp101ueu-wr-2.1.0.jar
    ( cd build/preplus-p101ueu-wr-2.1.0 ; \
    unzip -q webosdoctorp101ueu-wr-2.1.0.jar META-INF/MANIFEST.MF co
    m/* \
    resources/webOS.tar resources/recoverytool.config )
    ( cd build/preplus-p101ueu-wr-2.1.0 ; \
    unzip -q webosdoctorp101ueu-wr-2.1.0.jar resources/wr-castle-plu
    s.tar )
    mkdir -p build/preplus-p101ueu-wr-2.1.0/webOS
    tar -C build/preplus-p101ueu-wr-2.1.0/webOS \
    -f build/preplus-p101ueu-wr-2.1.0/resources/webOS.tar -x
    cp scripts/WebOS-Internals.tga build/preplus-p101ueu-wr-2.1.0/webOS/BootLogo.tga

    mkdir -p build/preplus-p101ueu-wr-2.1.0/carrier
    tar -f build/preplus-p101ueu-wr-2.1.0/resources/wr-castle-plus.tar -t \
    > build/preplus-p101ueu-wr-2.1.0/carrier/carrier-file-list.txt
    tar -C build/preplus-p101ueu-wr-2.1.0/carrier \
    -f build/preplus-p101ueu-wr-2.1.0/resources/wr-castle-plus.tar -
    x
    gunzip -f build/preplus-p101ueu-wr-2.1.0/webOS/nova-cust-image-castle.rootfs.tar
    .gz
    mkdir -p build/preplus-p101ueu-wr-2.1.0/rootfs
    tar -C build/preplus-p101ueu-wr-2.1.0/rootfs --wildcards \
    -f build/preplus-p101ueu-wr-2.1.0/webOS/nova-cust-image-castle.r
    ootfs.tar \
    -x ./usr/palm/applications/com.palm.app.firstuse ./usr/lib/ipkg/
    info ./etc/ssl ./usr/bin ./boot ./lib/modules ./etc/palm-build-info ./md5sums*
    touch build/preplus-p101ueu-wr-2.1.0/.unpacked
    rm -rf build/meta-bellmo-pre-2.1.0
    make unpack patch pack
    make[1]: Entering directory `/home/Tupac/meta-doctor'
    rm -rf build/meta-bellmo-pre-2.1.0
    mkdir -p build/meta-bellmo-pre-2.1.0
    cp downloads/webosdoctorp101ueu-wr-2.1.0.jar build/meta-bellmo-pre-2.1.0/webosdo
    ctorp101ueu-wr-2.1.0.jar
    ( cd build/meta-bellmo-pre-2.1.0 ; \
    unzip -q webosdoctorp101ueu-wr-2.1.0.jar META-INF/MANIFEST.MF co
    m/* \
    resources/webOS.tar resources/recoverytool.config )
    ( cd build/meta-bellmo-pre-2.1.0 ; \
    unzip -q webosdoctorp101ueu-wr-2.1.0.jar resources/wr-castle-plu
    s.tar )
    cp webOS.tar build/meta-bellmo-pre-2.1.0/resources/webOS.tar
    mkdir -p build/meta-bellmo-pre-2.1.0/webOS
    tar -C build/meta-bellmo-pre-2.1.0/webOS \
    -f build/meta-bellmo-pre-2.1.0/resources/webOS.tar -x
    cp scripts/WebOS-Internals.tga build/meta-bellmo-pre-2.1.0/webOS/BootLogo.tga
    mkdir -p build/meta-bellmo-pre-2.1.0/carrier
    tar -f build/meta-bellmo-pre-2.1.0/resources/wr-castle-plus.tar -t \
    > build/meta-bellmo-pre-2.1.0/carrier/carrier-file-list.txt
    tar -C build/meta-bellmo-pre-2.1.0/carrier \
    -f build/meta-bellmo-pre-2.1.0/resources/wr-castle-plus.tar -x
    gunzip -f build/meta-bellmo-pre-2.1.0/webOS/nova-cust-image-castle.rootfs.tar.gz

    mkdir -p build/meta-bellmo-pre-2.1.0/rootfs
    tar -C build/meta-bellmo-pre-2.1.0/rootfs --wildcards \
    -f build/meta-bellmo-pre-2.1.0/webOS/nova-cust-image-castle.root
    fs.tar \
    -x ./usr/palm/applications/com.palm.app.firstuse ./usr/lib/ipkg/
    info ./etc/ssl ./usr/bin ./boot ./lib/modules ./etc/palm-build-info ./md5sums*
    cp palm-build-info build/meta-bellmo-pre-2.1.0/rootfs/etc/palm-build-info
    touch build/meta-bellmo-pre-2.1.0/.unpacked
    rm -f build/meta-bellmo-pre-2.1.0/.patched
    [ -d patches/webos-2.1.0 ]
    if [ -f build/meta-bellmo-pre-2.1.0/rootfs/md5sums.gz ] ; then \
    gunzip -c < build/meta-bellmo-pre-2.1.0/rootfs/md5sums.gz > build/meta
    -bellmo-pre-2.1.0/rootfs/md5sums ; \
    fi
    mv build/meta-bellmo-pre-2.1.0/rootfs/md5sums build/meta-bellmo-pre-2.1.0/rootfs
    /md5sums.old
    mkdir -p build/meta-bellmo-pre-2.1.0/rootfs/var/gadget
    touch build/meta-bellmo-pre-2.1.0/rootfs/var/gadget/novacom_enabled
    chmod -x build/meta-bellmo-pre-2.1.0/rootfs/usr/bin/UpdateDaemon
    chmod -x build/meta-bellmo-pre-2.1.0/rootfs/usr/bin/uploadd
    chmod -x build/meta-bellmo-pre-2.1.0/rootfs/usr/bin/contextupload
    chmod -x build/meta-bellmo-pre-2.1.0/rootfs/usr/bin/rdxd
    mv build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo.md5sums \
    build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildin
    fo.md5sums.old ; \
    ( cd build/meta-bellmo-pre-2.1.0/rootfs ; md5sum ./etc/palm-build-info )
    > \
    build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo.md5
    sums.new ; \
    ./scripts/replace-md5sums.py \
    build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo.md5
    sums.old \
    build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo.md5
    sums.new \
    > build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildin
    fo.md5sums
    Overwriting md5sum for ./etc/palm-build-info
    rm -f build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo.md5sums
    .old \
    build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo
    .md5sums.new
    for app in com.palm.app.firstuse ; do \
    ( cd build/meta-bellmo-pre-2.1.0/rootfs ; \
    find ./usr/palm/applications/$app -type f | xargs md5sum ) \
    > build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sum
    s.new ; \
    ./scripts/replace-md5sums.py \
    build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sums.ol
    d build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sums.new \
    > build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sum
    s ; \
    rm -f build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sum
    s.old build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sums.new ; \
    done
    ( cd build/meta-bellmo-pre-2.1.0/rootfs ; \
    find ./usr/palm/applications/com.palm.app.firstuse ./usr/lib/ipkg/info
    ./etc/ssl ./usr/bin ./boot ./lib/modules ./etc/palm-build-info -type f | xargs
    md5sum ) \
    > build/meta-bellmo-pre-2.1.0/rootfs/md5sums.new

    here what i have a palm pre from bell mobility in Canada version 1.4.5 model P100EWW

    Is it normal that it show in the device ID palm pre plus ? but my cell is palm pre only??? and the carrier doesnt look like its Bell?? (underline at the top)

    this is what i have so far before the batch.exe screen close on me.
    it is normal and it said that it is suppose to open automatically the webos doctor and continue the operation but so far im the one that has to open the application.

    inside the Cygwin folder i have bin-dev-etc-lib-tmp-usr-var after all the process in the same folder i have a subfolder called home inside is tupac meta-doctor with bashrc.inputrc-profile.

    inside meta-doctor i have git-build-download-hashes-patches-scripts and gitignore-castls..makefile.palm-build-webos.

    inside build i have 4 subfolder called
    meta-bellmo-pre-2.1.0
    pre2-p102eww-verizonwireless-2.0.1
    pre-p100eww-bellmo-1.4.5
    preplus-p101ueu-wr-2.1.0

    what i did is open the first one cuz it say 2.01 when, during the install it ask to connect the cell but after 10 min it said not able to reset the pc?

    now what am i doing wrong im sure im following the instruction well right Rob?
  17. #3457  
    Quote Originally Posted by rwhitby View Post
    Turn off backups to delete your profile data. Full erase. Re-doctor without skipping first use.

    ... and now *you* get to add that to the wiki.

    -- Rod
    So my steps are?

    1. Turn off Backups
    2. Full Erase
    3. Doctor using which file? i.e. anyone have a url link for the right doctor.jar?
    4. When phone restarts, create new palm profile?

    Thanks!
  18. #3458  
    Code:
    Quote Originally Posted by flipmode007 View Post
    Already up-to-date. rm -rf build fatal: destination path 'meta-doctor' already exists and is not an empty directo ry. DEVICE = preplus CARRIER = wr VERSION = 2.1.0 ENABLE_DEVELOPER_MODE = 1 DISABLE_UPLOAD_DAEMON = 1 DISABLE_UPDATE_DAEMON = 1 CUSTOM_WEBOS_TARBALL = webOS.tar CUSTOM_BUILD_INFO = palm-build-info CUSTOM_WEBOS_DMSET = 393 CUSTOM_CARRIER_DMSET = 398 CUSTOM_MODEL_LIST = P100EWW CUSTOM_CARRIER_LIST = bell CUSTOM_BOOTLOGO = scripts/WebOS-Internals.tga Your custom doctor file will be created at build/meta-bellmo-pre-2.1.0/webosdoct orp101ueu-wr-2.1.0.jar rm -rf build/pre-p100eww-bellmo-1.4.5 mkdir -p build/pre-p100eww-bellmo-1.4.5 cp downloads/webosdoctorp100ewwbellmo-1.4.5.jar build/pre-p100eww-bellmo-1.4.5/w ebosdoctorp100ewwbellmo-1.4.5.jar ( cd build/pre-p100eww-bellmo-1.4.5 ; \ unzip -q webosdoctorp100ewwbellmo-1.4.5.jar META-INF/MANIFEST.MF com/* \ resources/webOS.tar resources/recoverytool.config ) ( cd build/pre-p100eww-bellmo-1.4.5 ; \ unzip -q webosdoctorp100ewwbellmo-1.4.5.jar resources/bellmo.tar ) mkdir -p build/pre-p100eww-bellmo-1.4.5/webOS tar -C build/pre-p100eww-bellmo-1.4.5/webOS \ -f build/pre-p100eww-bellmo-1.4.5/resources/webOS.tar -x cp scripts/WebOS-Internals.tga build/pre-p100eww-bellmo-1.4.5/webOS/BootLogo.tga mkdir -p build/pre-p100eww-bellmo-1.4.5/carrier tar -f build/pre-p100eww-bellmo-1.4.5/resources/bellmo.tar -t \ > build/pre-p100eww-bellmo-1.4.5/carrier/carrier-file-list.txt tar -C build/pre-p100eww-bellmo-1.4.5/carrier \ -f build/pre-p100eww-bellmo-1.4.5/resources/bellmo.tar -x gunzip -f build/pre-p100eww-bellmo-1.4.5/webOS/nova-cust-image-castle.rootfs.tar .gz mkdir -p build/pre-p100eww-bellmo-1.4.5/rootfs tar -C build/pre-p100eww-bellmo-1.4.5/rootfs --wildcards \ -f build/pre-p100eww-bellmo-1.4.5/webOS/nova-cust-image-castle.r ootfs.tar \ -x ./usr/palm/applications/com.palm.app.firstuse ./usr/lib/ipkg/ info ./etc/ssl ./usr/bin ./boot ./lib/modules ./etc/palm-build-info ./md5sums* touch build/pre-p100eww-bellmo-1.4.5/.unpacked rm -rf build/pre2-p102eww-verizonwireless-2.0.1 mkdir -p build/pre2-p102eww-verizonwireless-2.0.1 cp downloads/webosdoctorp102verizonwireless-2.0.1.jar build/pre2-p102eww-verizon wireless-2.0.1/webosdoctorp102verizonwireless-2.0.1.jar ( cd build/pre2-p102eww-verizonwireless-2.0.1 ; \ unzip -q webosdoctorp102verizonwireless-2.0.1.jar META-INF/MANIF EST.MF com/* \ resources/webOS.tar resources/recoverytool.config ) ( cd build/pre2-p102eww-verizonwireless-2.0.1 ; \ unzip -q webosdoctorp102verizonwireless-2.0.1.jar resources/veri zon.tar ) mkdir -p build/pre2-p102eww-verizonwireless-2.0.1/webOS tar -C build/pre2-p102eww-verizonwireless-2.0.1/webOS \ -f build/pre2-p102eww-verizonwireless-2.0.1/resources/webOS.tar -x cp scripts/WebOS-Internals.tga build/pre2-p102eww-verizonwireless-2.0.1/webOS/Bo otLogo.tga mkdir -p build/pre2-p102eww-verizonwireless-2.0.1/carrier tar -f build/pre2-p102eww-verizonwireless-2.0.1/resources/verizon.tar -t \ > build/pre2-p102eww-verizonwireless-2.0.1/carrier/carrier-file- list.txt tar -C build/pre2-p102eww-verizonwireless-2.0.1/carrier \ -f build/pre2-p102eww-verizonwireless-2.0.1/resources/verizon.ta r -x gunzip -f build/pre2-p102eww-verizonwireless-2.0.1/webOS/nova-cust-image-roadrun ner.rootfs.tar.gz mkdir -p build/pre2-p102eww-verizonwireless-2.0.1/rootfs tar -C build/pre2-p102eww-verizonwireless-2.0.1/rootfs --wildcards \ -f build/pre2-p102eww-verizonwireless-2.0.1/webOS/nova-cust-imag e-roadrunner.rootfs.tar \ -x ./usr/palm/applications/com.palm.app.firstuse ./usr/lib/ipkg/ info ./etc/ssl ./usr/bin ./boot ./lib/modules ./etc/palm-build-info ./md5sums* touch build/pre2-p102eww-verizonwireless-2.0.1/.unpacked rm -rf build/preplus-p101ueu-wr-2.1.0 mkdir -p build/preplus-p101ueu-wr-2.1.0 cp downloads/webosdoctorp101ueu-wr-2.1.0.jar build/preplus-p101ueu-wr-2.1.0/webo sdoctorp101ueu-wr-2.1.0.jar ( cd build/preplus-p101ueu-wr-2.1.0 ; \ unzip -q webosdoctorp101ueu-wr-2.1.0.jar META-INF/MANIFEST.MF co m/* \ resources/webOS.tar resources/recoverytool.config ) ( cd build/preplus-p101ueu-wr-2.1.0 ; \ unzip -q webosdoctorp101ueu-wr-2.1.0.jar resources/wr-castle-plu s.tar ) mkdir -p build/preplus-p101ueu-wr-2.1.0/webOS tar -C build/preplus-p101ueu-wr-2.1.0/webOS \ -f build/preplus-p101ueu-wr-2.1.0/resources/webOS.tar -x cp scripts/WebOS-Internals.tga build/preplus-p101ueu-wr-2.1.0/webOS/BootLogo.tga mkdir -p build/preplus-p101ueu-wr-2.1.0/carrier tar -f build/preplus-p101ueu-wr-2.1.0/resources/wr-castle-plus.tar -t \ > build/preplus-p101ueu-wr-2.1.0/carrier/carrier-file-list.txt tar -C build/preplus-p101ueu-wr-2.1.0/carrier \ -f build/preplus-p101ueu-wr-2.1.0/resources/wr-castle-plus.tar - x gunzip -f build/preplus-p101ueu-wr-2.1.0/webOS/nova-cust-image-castle.rootfs.tar .gz mkdir -p build/preplus-p101ueu-wr-2.1.0/rootfs tar -C build/preplus-p101ueu-wr-2.1.0/rootfs --wildcards \ -f build/preplus-p101ueu-wr-2.1.0/webOS/nova-cust-image-castle.r ootfs.tar \ -x ./usr/palm/applications/com.palm.app.firstuse ./usr/lib/ipkg/ info ./etc/ssl ./usr/bin ./boot ./lib/modules ./etc/palm-build-info ./md5sums* touch build/preplus-p101ueu-wr-2.1.0/.unpacked rm -rf build/meta-bellmo-pre-2.1.0 make unpack patch pack make[1]: Entering directory `/home/Tupac/meta-doctor' rm -rf build/meta-bellmo-pre-2.1.0 mkdir -p build/meta-bellmo-pre-2.1.0 cp downloads/webosdoctorp101ueu-wr-2.1.0.jar build/meta-bellmo-pre-2.1.0/webosdo ctorp101ueu-wr-2.1.0.jar ( cd build/meta-bellmo-pre-2.1.0 ; \ unzip -q webosdoctorp101ueu-wr-2.1.0.jar META-INF/MANIFEST.MF co m/* \ resources/webOS.tar resources/recoverytool.config ) ( cd build/meta-bellmo-pre-2.1.0 ; \ unzip -q webosdoctorp101ueu-wr-2.1.0.jar resources/wr-castle-plu s.tar ) cp webOS.tar build/meta-bellmo-pre-2.1.0/resources/webOS.tar mkdir -p build/meta-bellmo-pre-2.1.0/webOS tar -C build/meta-bellmo-pre-2.1.0/webOS \ -f build/meta-bellmo-pre-2.1.0/resources/webOS.tar -x cp scripts/WebOS-Internals.tga build/meta-bellmo-pre-2.1.0/webOS/BootLogo.tga mkdir -p build/meta-bellmo-pre-2.1.0/carrier tar -f build/meta-bellmo-pre-2.1.0/resources/wr-castle-plus.tar -t \ > build/meta-bellmo-pre-2.1.0/carrier/carrier-file-list.txt tar -C build/meta-bellmo-pre-2.1.0/carrier \ -f build/meta-bellmo-pre-2.1.0/resources/wr-castle-plus.tar -x gunzip -f build/meta-bellmo-pre-2.1.0/webOS/nova-cust-image-castle.rootfs.tar.gz mkdir -p build/meta-bellmo-pre-2.1.0/rootfs tar -C build/meta-bellmo-pre-2.1.0/rootfs --wildcards \ -f build/meta-bellmo-pre-2.1.0/webOS/nova-cust-image-castle.root fs.tar \ -x ./usr/palm/applications/com.palm.app.firstuse ./usr/lib/ipkg/ info ./etc/ssl ./usr/bin ./boot ./lib/modules ./etc/palm-build-info ./md5sums* cp palm-build-info build/meta-bellmo-pre-2.1.0/rootfs/etc/palm-build-info touch build/meta-bellmo-pre-2.1.0/.unpacked rm -f build/meta-bellmo-pre-2.1.0/.patched [ -d patches/webos-2.1.0 ] if [ -f build/meta-bellmo-pre-2.1.0/rootfs/md5sums.gz ] ; then \ gunzip -c < build/meta-bellmo-pre-2.1.0/rootfs/md5sums.gz > build/meta -bellmo-pre-2.1.0/rootfs/md5sums ; \ fi mv build/meta-bellmo-pre-2.1.0/rootfs/md5sums build/meta-bellmo-pre-2.1.0/rootfs /md5sums.old mkdir -p build/meta-bellmo-pre-2.1.0/rootfs/var/gadget touch build/meta-bellmo-pre-2.1.0/rootfs/var/gadget/novacom_enabled chmod -x build/meta-bellmo-pre-2.1.0/rootfs/usr/bin/UpdateDaemon chmod -x build/meta-bellmo-pre-2.1.0/rootfs/usr/bin/uploadd chmod -x build/meta-bellmo-pre-2.1.0/rootfs/usr/bin/contextupload chmod -x build/meta-bellmo-pre-2.1.0/rootfs/usr/bin/rdxd mv build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo.md5sums \ build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildin fo.md5sums.old ; \ ( cd build/meta-bellmo-pre-2.1.0/rootfs ; md5sum ./etc/palm-build-info ) > \ build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo.md5 sums.new ; \ ./scripts/replace-md5sums.py \ build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo.md5 sums.old \ build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo.md5 sums.new \ > build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildin fo.md5sums Overwriting md5sum for ./etc/palm-build-info rm -f build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo.md5sums .old \ build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/palmbuildinfo .md5sums.new for app in com.palm.app.firstuse ; do \ ( cd build/meta-bellmo-pre-2.1.0/rootfs ; \ find ./usr/palm/applications/$app -type f | xargs md5sum ) \ > build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sum s.new ; \ ./scripts/replace-md5sums.py \ build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sums.ol d build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sums.new \ > build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sum s ; \ rm -f build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sum s.old build/meta-bellmo-pre-2.1.0/rootfs/usr/lib/ipkg/info/$app.md5sums.new ; \ done ( cd build/meta-bellmo-pre-2.1.0/rootfs ; \ find ./usr/palm/applications/com.palm.app.firstuse ./usr/lib/ipkg/info ./etc/ssl ./usr/bin ./boot ./lib/modules ./etc/palm-build-info -type f | xargs md5sum ) \ > build/meta-bellmo-pre-2.1.0/rootfs/md5sums.new
    Quote Originally Posted by flipmode007 View Post

    here what i have a palm pre from bell mobility in Canada version 1.4.5 model P100EWW

    Is it normal that it show in the device ID palm pre plus ? but my cell is palm pre only??? and the carrier doesnt look like its Bell?? (underline at the top)

    this is what i have so far before the batch.exe screen close on me.
    it is normal and it said that it is suppose to open automatically the webos doctor and continue the operation but so far im the one that has to open the application.

    inside the Cygwin folder i have bin-dev-etc-lib-tmp-usr-var after all the process in the same folder i have a subfolder called home inside is tupac meta-doctor with bashrc.inputrc-profile.

    inside meta-doctor i have git-build-download-hashes-patches-scripts and gitignore-castls..makefile.palm-build-webos.

    inside build i have 4 subfolder called
    meta-bellmo-pre-2.1.0
    pre2-p102eww-verizonwireless-2.0.1
    pre-p100eww-bellmo-1.4.5
    preplus-p101ueu-wr-2.1.0

    what i did is open the first one cuz it say 2.01 when, during the install it ask to connect the cell but after 10 min it said not able to reset the pc?

    now what am i doing wrong im sure im following the instruction well right Rob?
    Quote Originally Posted by rwhitby View Post
    Don't click on the jar file, run it from the command line.

    java -jar <doctor-file>

    then you get the full console output.

    -- Rod
    I would think this would apply to running a .jar file after it is compiled to.
  19. #3459  
    Quote Originally Posted by 6tr6tr View Post
    3. Doctor using which file? i.e. anyone have a url link for the right doctor.jar?

    Sure. It's here:

    WebOS 2 Upgrade - WebOS Internals


    M.
  20. #3460  
    Omg tks that is what i did for the past 4-5 days i run it via the meta-belmo-prr-2.1.0 folder and click on the weobosdoctorp101ueu-wr-2..1.0.jar, ok one thing how do i run it from the command line to get the full console?

    Do i have to open the semi-auto-bellmo-2.1.0.cmd again? or is it another process tks.

    Can i ask you something, a while back i open the third folder pre...bellmo1.4.5 and it install the 1.4.5 is that the process on how to go back if you don't like the 2.0.1 lol
    because it did work if it is.

Posting Permissions