Page 2 of 13 FirstFirst 123456712 ... LastLast
Results 21 to 40 of 253
Like Tree15Likes
  1. #21  
    Also, I finally figured out how to dump the entire java output to a text file... can I have the Pre 2 version again so I can generate you a complete output? Maybe we can get somewhere?

    This is the V3 output error.
    Attached Files Attached Files
    Palm IIIc -> Sony CLI T650C -> Sony TJ-37 -> Palm TX -> Palm Centro -> Palm Pre Bell -> Palm Pre Plus Bell/Verizon Hybrid -> HP Veer -> HP Pre 3 NA -> BlackBerry Classic -> BlackBerry Priv

    It's a Late Goodbye, such a Late Goodbye.

    Need OEM Palm Pre parts? See here
  2.    #22  
    Quote Originally Posted by ToniCipriani View Post
    No no, that's the actual doctor process when flashing, not Meta-Doctor. I create the JAR files on my Ubuntu VM then run the resulting doctor in Windows. I don't trust the VMWare USB driver...

    I definitely know the resulting doctors will work properly in Windows because I converted a few Pre Pluses back then and all worked fine.
    Without understanding what it can not parse, I am at a loss to know what to do or where to go...

    If I had the command line during the build maybe it failed to sed the xml file right, maybe your xml file is corrupt somehow? I am trying to figure out why the XML file works fine in the Pre2 build, but fails in the Pre3 build?

    If it is not Windows 7 trashing the doctor (which also might be the case), then maybe it is the Ubuntu during build. Not sure...

    As I do not have a device at this time I can not test it, besides building a doctor and running it until it wants a device.
  3.    #23  
    Quote Originally Posted by ToniCipriani View Post
    Also, I finally figured out how to dump the entire java output to a text file... can I have the Pre 2 version again so I can generate you a complete output? Maybe we can get somewhere?

    This is the V3 output error.
    Not sure if this is an issue:
    "G6-GTP","Microsoft Windows 7 ∫Xƒ•™ ","6.1.7601 Service Pack 1 ≤’ 7601","Microsoft Corporation","W•flu@∏","Multiprocessor Free","Calvin","","00426-OEM-8992662-00015","17/10/2009, W 12:16:45","10/4/2012, U 06:04:19","System manufacturer","System Product Name","x64-based PC","ww∏ 1 ≥B≤zπC,[01]: AMD64 Family 16 Model 2 Stepping 3 AuthenticAMD ~2411 Mhz","Phoenix Technologies, LTD ASUS M2N-E ACPI BIOS Revision 1701, 30/10/2008","C:\Windows","C:\Windows\system32","\Device\HarddiskVolume3","zh-tw; (•x∆W)","zh-hk; (≠‰SOʨF∞œ)","(UTC-05:00) ™F≥

    You are on windows, I have had several discussion with Rod, concerning the meta-doctor process and it not working under Windows...

    Is it possible for you to go under a Linux variant or Mac OS?

    Here is a copy of the V2 build, it was removed, as I do not want it public if it does not work...

    Also if you could give me the command line output during the base build?
    Last edited by John Steffes; 04/10/2012 at 08:40 PM.
  4. #24  
    Quote Originally Posted by John Steffes View Post
    Not sure if this is an issue:
    "G6-GTP","Microsoft Windows 7 ∫Xƒ•™ ","6.1.7601 Service Pack 1 ≤’ 7601","Microsoft Corporation","W•flu@∏","Multiprocessor Free","Calvin","","00426-OEM-8992662-00015","17/10/2009, W 12:16:45","10/4/2012, U 06:04:19","System manufacturer","System Product Name","x64-based PC","ww∏ 1 ≥B≤zπC,[01]: AMD64 Family 16 Model 2 Stepping 3 AuthenticAMD ~2411 Mhz","Phoenix Technologies, LTD ASUS M2N-E ACPI BIOS Revision 1701, 30/10/2008","C:\Windows","C:\Windows\system32","\Device\HarddiskVolume3","zh-tw; (•x∆W)","zh-hk; (≠‰SOʨF∞œ)","(UTC-05:00) ™F≥

    You are on windows, I have had several discussion with Rod, concerning the meta-doctor process and it not working under Windows...

    Is it possible for you to go under a Linux variant or Mac OS?

    Here is a copy of the V2 build, it will be removed later tonight... (as I do not want it public if if does not work)...
    No no, that's the actual doctor process when flashing, not Meta-Doctor. I create the JAR files on my Ubuntu VM then run the resulting doctor in Windows. I don't trust the VMWare USB driver...

    I definitely know the resulting doctors will work properly in Windows because I converted a few Pre Pluses back then and all worked fine.
    Palm IIIc -> Sony CLI T650C -> Sony TJ-37 -> Palm TX -> Palm Centro -> Palm Pre Bell -> Palm Pre Plus Bell/Verizon Hybrid -> HP Veer -> HP Pre 3 NA -> BlackBerry Classic -> BlackBerry Priv

    It's a Late Goodbye, such a Late Goodbye.

    Need OEM Palm Pre parts? See here
  5. #25  
    John, any updates, need any other testing from me?
    Palm IIIc -> Sony CLI T650C -> Sony TJ-37 -> Palm TX -> Palm Centro -> Palm Pre Bell -> Palm Pre Plus Bell/Verizon Hybrid -> HP Veer -> HP Pre 3 NA -> BlackBerry Classic -> BlackBerry Priv

    It's a Late Goodbye, such a Late Goodbye.

    Need OEM Palm Pre parts? See here
  6.    #26  
    Quote Originally Posted by ToniCipriani View Post
    John, any updates, need any other testing from me?
    Sorry, been busy, with life, looked at script... Updated first post...
    Last edited by John Steffes; 04/14/2012 at 01:44 AM.
  7. #27  
    Gonna try the V4 now... it's building as we speak.
    Palm IIIc -> Sony CLI T650C -> Sony TJ-37 -> Palm TX -> Palm Centro -> Palm Pre Bell -> Palm Pre Plus Bell/Verizon Hybrid -> HP Veer -> HP Pre 3 NA -> BlackBerry Classic -> BlackBerry Priv

    It's a Late Goodbye, such a Late Goodbye.

    Need OEM Palm Pre parts? See here
  8. #28  
    Didn't work, we're back to square one, with the Trenchcoat loop.

    In particular, the log at 10:11 is of interest:

    INFO: Trenchcoat: <ERROR> CPU-specific initialization failed
    Attached Files Attached Files
    Palm IIIc -> Sony CLI T650C -> Sony TJ-37 -> Palm TX -> Palm Centro -> Palm Pre Bell -> Palm Pre Plus Bell/Verizon Hybrid -> HP Veer -> HP Pre 3 NA -> BlackBerry Classic -> BlackBerry Priv

    It's a Late Goodbye, such a Late Goodbye.

    Need OEM Palm Pre parts? See here
  9.    #29  
    Quote Originally Posted by ToniCipriani View Post
    Didn't work, we're back to square one, with the Trenchcoat loop.

    In particular, the log at 10:11 is of interest:

    INFO: Trenchcoat: <ERROR> CPU-specific initialization failed
    Toni,

    I see this each time with a log:

    10:07:54 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "resizefat -r /dev/mapper/store-media"

    10:07:56 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: dosfsck 2.11, 12 Mar 2005, FAT32, LFN

    10:07:56 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: There are differences between boot sector and its backup.

    10:07:56 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Differences: (offsetriginal/backup)

    10:07:56 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: 71:48/20, 72:50/20, 74:56/20, 75:45/20, 76:45/20, 77:52/20

    10:07:56 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Not automatically fixing this.

    Your /media/internal disk is corrupt and needs to be fixed, to fix this use this post:
    FYI this post is about the Touchpad but you should be able to fix this during the build...

    WebOS Doctor - 12% Issue - Fixed!!!


    I do see the error:

    10:11:00 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <ERROR> CPU-specific initialization failed

    Will attempt to see what Java Class file was running and compare these (might have to swap more from webOS 2.1.x Java Class files to get it to use the correct CPU info).

    Also if you ignore the failed card message and reboot the Veer, what happens?
    Last edited by John Steffes; 04/15/2012 at 09:28 AM.
  10. #30  
    Thing is, I don't get that error when I use the 2.1.2 doctor. I use it again every time after the doctor fails, and it works just fine. I can go back into Dev Mode and see all my files that are on /media internal/

    Here's a completed 2.1.2. for your reference.
    Attached Files Attached Files
    Palm IIIc -> Sony CLI T650C -> Sony TJ-37 -> Palm TX -> Palm Centro -> Palm Pre Bell -> Palm Pre Plus Bell/Verizon Hybrid -> HP Veer -> HP Pre 3 NA -> BlackBerry Classic -> BlackBerry Priv

    It's a Late Goodbye, such a Late Goodbye.

    Need OEM Palm Pre parts? See here
  11.    #31  
    Quote Originally Posted by ToniCipriani View Post
    Thing is, I don't get that error when I use the 2.1.2 doctor. I use it again every time after the doctor fails, and it works just fine. I can go back into Dev Mode and see all my files that are on /media internal/

    Here's a completed 2.1.2. for your reference.
    Look at these lines (2162-2182) in your doc212.txt file:

    <INFO> Running "resizefat -r /dev/mapper/store-media"
    2012~414 U10:24:27 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: dosfsck 2.11, 12 Mar 2005, FAT32, LFN

    dosfsck 2.11, 12 Mar 2005, FAT32, LFN
    2012~414 U10:24:27 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: There are differences between boot sector and its backup.

    There are differences between boot sector and its backup.
    2012~414 U10:24:27 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Differences: (offsetriginal/backup)

    Differences: (offsetriginal/backup)
    2012~414 U10:24:27 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: 71:48/20, 72:50/20, 74:56/20, 75:45/20, 76:45/20, 77:52/20

    71:48/20, 72:50/20, 74:56/20, 75:45/20, 76:45/20, 77:52/20
    2012~414 U10:24:27 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Not automatically fixing this.
  12. #32  
    Then in that case, I think that's not what's stopping the doctor in the 2.2.4? We can safely ignore that?
    Palm IIIc -> Sony CLI T650C -> Sony TJ-37 -> Palm TX -> Palm Centro -> Palm Pre Bell -> Palm Pre Plus Bell/Verizon Hybrid -> HP Veer -> HP Pre 3 NA -> BlackBerry Classic -> BlackBerry Priv

    It's a Late Goodbye, such a Late Goodbye.

    Need OEM Palm Pre parts? See here
  13.    #33  
    Quote Originally Posted by ToniCipriani View Post
    Then in that case, I think that's not what's stopping the doctor in the 2.2.4? We can safely ignore that?
    As this could lead to further issues with your USB data, I recommend that you fix it...

    I can not say one way or the other if this is the issue causing the script to fail at this point that is not an alarm.

    But as I know the logic behind the RecoveryTool has changed from webOS 2.1.x to webOS 2.2.4 to webOS 3.0.x, and that it can cause an issues with the Touchpad and Pre2/3 devices now that they are webOS 2.2.4, it should be fixed for your sake.

    I would hate for you to keep testing these scripts and to loose all your data...
  14. #34  
    Quote Originally Posted by John Steffes View Post
    Look at these lines (2162-2182) in your doc212.txt file:

    <INFO> Running "resizefat -r /dev/mapper/store-media"
    2012~414 U10:24:27 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: dosfsck 2.11, 12 Mar 2005, FAT32, LFN

    dosfsck 2.11, 12 Mar 2005, FAT32, LFN
    2012~414 U10:24:27 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: There are differences between boot sector and its backup.

    There are differences between boot sector and its backup.
    2012~414 U10:24:27 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Differences: (offsetriginal/backup)

    Differences: (offsetriginal/backup)
    2012~414 U10:24:27 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: 71:48/20, 72:50/20, 74:56/20, 75:45/20, 76:45/20, 77:52/20

    71:48/20, 72:50/20, 74:56/20, 75:45/20, 76:45/20, 77:52/20
    2012~414 U10:24:27 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Not automatically fixing this.
    I get this as well.
    Last edited by GuyFromNam; 05/06/2012 at 03:22 PM.
  15. #35  
    Quote Originally Posted by ToniCipriani View Post
    Didn't work, we're back to square one, with the Trenchcoat loop.

    In particular, the log at 10:11 is of interest:

    INFO: Trenchcoat: <ERROR> CPU-specific initialization failed
    Same.
    is this what you need regarding output?
    Attached Files Attached Files
    Last edited by GuyFromNam; 05/06/2012 at 03:19 PM.
  16.    #36  
    Quote Originally Posted by GuyFromNam View Post
    Same.
    is this what you need regarding output?
    Back to basics, Modified V1 build, removed XML conversion so the disk structure will be webOS 2.1.0, see what the webOS 2.2.4 rootfs does once untared. Look on first post...

    I assume we will fail ROM verification because of FSTAB?
    Last edited by John Steffes; 04/15/2012 at 04:44 PM.
  17. #37  
    Quote Originally Posted by John Steffes View Post
    As this could lead to further issues with your USB data, I recommend that you fix it...

    I can not say one way or the other if this is the issue causing the script to fail at this point that is not an alarm.

    But as I know the logic behind the RecoveryTool has changed from webOS 2.1.x to webOS 2.2.4 to webOS 3.0.x, and that it can cause an issues with the Touchpad and Pre2/3 devices now that they are webOS 2.2.4, it should be fixed for your sake.

    I would hate for you to keep testing these scripts and to loose all your data...
    Actually it's OK. All my stuff still on the Veer actually has been migrated to my Pre 3 already, so it's OK to destroy it. If anything it acts as a good control so we know if there's any mal-effects.

    I'm happy to do the community a service.
    Palm IIIc -> Sony CLI T650C -> Sony TJ-37 -> Palm TX -> Palm Centro -> Palm Pre Bell -> Palm Pre Plus Bell/Verizon Hybrid -> HP Veer -> HP Pre 3 NA -> BlackBerry Classic -> BlackBerry Priv

    It's a Late Goodbye, such a Late Goodbye.

    Need OEM Palm Pre parts? See here
  18. #38  
    V5 run. Still a Trenchcoat loop.

    I also tried what you said and just do a reboot, but all it does is show the HP logo, then reboot again.
    Attached Files Attached Files
    Palm IIIc -> Sony CLI T650C -> Sony TJ-37 -> Palm TX -> Palm Centro -> Palm Pre Bell -> Palm Pre Plus Bell/Verizon Hybrid -> HP Veer -> HP Pre 3 NA -> BlackBerry Classic -> BlackBerry Priv

    It's a Late Goodbye, such a Late Goodbye.

    Need OEM Palm Pre parts? See here
  19.    #39  
    Quote Originally Posted by ToniCipriani View Post
    V5 run. Still a Trenchcoat loop.

    I also tried what you said and just do a reboot, but all it does is show the HP logo, then reboot again.
    Updated first post...

    Removed lib boot files...

    Tech Info....

    When I brought over the boot files from PixiPlus the webOS Doctor did not build the boot lib files (that was webOS 1.4.x.x to webOS 2.1.0)...

    Maybe I do not need them with webOS 2.1.0 to webOS 2.2.4?
  20. #40  
    Nope... still the same error. Standby for full log...

    <INFO> Untarring complete, syncing file systems
    2012年4月15日 下午09:50:59 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "rm -rf /tmp/tcmnt_1721//etc/fstab"

    <INFO> Running "rm -rf /tmp/tcmnt_1721//etc/fstab"
    2012年4月15日 下午09:50:59 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <ERROR> Unable to create directory /tmp/tcmnt_1721/etc/fs.d

    <ERROR> Unable to create directory /tmp/tcmnt_1721/etc/fs.d
    2012年4月15日 下午09:51:01 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "rm -rf /tmp/tcmnt_1721"

    <INFO> Running "rm -rf /tmp/tcmnt_1721"
    2012年4月15日 下午09:51:01 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "lvm.static vgchange -an --ignorelockingfailure store 2> /dev/null"

    <INFO> Running "lvm.static vgchange -an --ignorelockingfailure store 2> /dev/null"
    2012年4月15日 下午09:51:03 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: 0 logical volume(s) in volume group "store" now active

    0 logical volume(s) in volume group "store" now active
    2012年4月15日 下午09:51:03 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <ERROR> CPU-specific initialization failed

    <ERROR> CPU-specific initialization failed
    2012年4月15日 下午09:51:03 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Finished!

    2012年4月15日 下午09:51:03 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat returned failure error code 1

    2012年4月15日 下午09:51:03 com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: retrying trenchcoat
    Palm IIIc -> Sony CLI T650C -> Sony TJ-37 -> Palm TX -> Palm Centro -> Palm Pre Bell -> Palm Pre Plus Bell/Verizon Hybrid -> HP Veer -> HP Pre 3 NA -> BlackBerry Classic -> BlackBerry Priv

    It's a Late Goodbye, such a Late Goodbye.

    Need OEM Palm Pre parts? See here
Page 2 of 13 FirstFirst 123456712 ... LastLast

Posting Permissions