Page 2 of 2 FirstFirst 12
Results 21 to 36 of 36
Like Tree4Likes
  1. iDG
    iDG is offline
    iDG's Avatar
    Posts
    37 Posts
    #21  
    Quote Originally Posted by ssjcho View Post
    Sorry, but I think I'm going to need more instructions on how to do this. All I know how to do so far is to clone the git files.
    If you are interested in learning how to compile code for the webos based devices, there are a lot of sources you can look into. But I assume you're interested in the tool itself. So i built it for you and attached it to this post.
    Attached Files Attached Files
    Remy X likes this.
  2.    #22  
    Quote Originally Posted by iDG View Post
    If you are interested in learning how to compile code for the webos based devices, there are a lot of sources you can look into. But I assume you're interested in the tool itself. So i built it for you and attached it to this post.
    Thank you! You've been incredibly helpful so far. Let's see if this works...


    So, I transferred the bootie-config tool onto the phone through novaterm. Then I was able to add all of the minimum required tokens without a problem. Mounted them, reset, and tried the doctor again.

    This time, no exceptions and I was able to successfully run the doctor without any problems. It booted up fine all the way up to the choose your language screen! I chose English and let it configure... then I wasn't paying attention, but at some point, the phone reset and was on the palm loading screen. It seemed to be boot looping...

    so I run try running the doctor again, and this time, the device restarts in the middle of the doctor and says Phone Disconnected. Every time I run the doctor now, it gets disconnected (and I didn't pay close enough attention to exactly where) and I get no errors. It seems to reset by itself randomly and now is unable to boot.

    I tried novaterm again to check everything before running another doctor, and I get an error every time:
    Code:
     $ novaterm
    
     novacomd socket was closed prematurely
    novacom: unexpected EOF from server
    On the phone, a white triangle with an exclamation mark in the middle appears. Below it says, WebOS Doctor

    something must have gotten messed up because this last time I ran the doctor, it said "We were unable to reset your phone." the printout from the terminal...
    Code:
    May 26, 2013 12:57:51 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Sent 36673 bytes
    
    May 26, 2013 12:57:51 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Sending File: nova-cust-image-castle.rootfs.tar.gz
    
    May 26, 2013 12:57:51 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "lvm.static vgchange -an --ignorelockingfailure 2> /dev/null"
    
    May 26, 2013 12:57:51 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat:   0 logical volume(s) in volume group "store" now active
    
    May 26, 2013 12:57:51 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Re-enumerating partitions
    
    May 26, 2013 12:57:51 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Waiting for potential automounts to finish....
    
    May 26, 2013 12:57:56 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Unmounting everything again.
    
    May 26, 2013 12:57:57 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "lvm.static vgchange -an --ignorelockingfailure 2> /dev/null"
    
    May 26, 2013 12:57:57 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat:   0 logical volume(s) in volume group "store" now active
    
    May 26, 2013 12:57:57 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Bootloader Load Address: 0x40200000
    
    May 26, 2013 12:57:57 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Bootloader install complete
    
    May 26, 2013 12:57:57 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section offset 524288, size 4194304
    
    May 26, 2013 12:57:57 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> existing tokens 0x820f08
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'env' offset 4096 len 16384
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram found existing environment section, reusing
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> overwriting existing env var 'checkbatt'
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> env write_env_val: checkbatt = '1'
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> using old value of existing env var 'installer'
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> env write_env_val: installer = 'trenchcoat'
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'tokens' offset 20480 len 4096
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> overwriting existing token 'DMSETS'
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> not overwriting existing token 'installer'
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'PalmSN' to offset 0, gen 1, len 12
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'WIFIiADDR' to offset 48, gen 1, len 17
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'BToADDR' to offset 104, gen 1, len 17
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'PRODoID' to offset 160, gen 1, len 7
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'PN' to offset 204, gen 1, len 12
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'KEYoBRD' to offset 252, gen 1, len 1
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'HWoRev' to offset 292, gen 1, len 1
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'DMMODEL' to offset 332, gen 1, len 7
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'DMCARRIER' to offset 376, gen 1, len 7
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'DMSETS' to offset 420, gen 11, len 20
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'ProdSN' to offset 476, gen 1, len 14
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'installer' to offset 528, gen 1, len 10
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'token-backup' offset 4190208 len 4096
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'PalmSN' to offset 0, gen 1, len 12
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'WIFIiADDR' to offset 48, gen 1, len 17
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'BToADDR' to offset 104, gen 1, len 17
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'PRODoID' to offset 160, gen 1, len 7
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'PN' to offset 204, gen 1, len 12
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'KEYoBRD' to offset 252, gen 1, len 1
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'HWoRev' to offset 292, gen 1, len 1
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'DMMODEL' to offset 332, gen 1, len 7
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'DMCARRIER' to offset 376, gen 1, len 7
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'DMSETS' to offset 420, gen 11, len 20
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'ProdSN' to offset 476, gen 1, len 14
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'installer' to offset 528, gen 1, len 10
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-boot' offset 24576 len 15859
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-chg' offset 40960 len 92565
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-badchg' offset 135168 len 48178
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-nobatt' offset 184320 len 87835
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-badsys' offset 274432 len 26853
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-nosys' offset 303104 len 26853
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-sync' offset 331776 len 71862
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-panic' offset 405504 len 74779
    
    May 26, 2013 12:57:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-disk' offset 483328 len 36673
    
    May 26, 2013 12:57:59 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "mke2fs -j -b4096 -m0 -L /boot /dev/mmcblk0p2 > /dev/null 2> /dev/null"
    
    May 26, 2013 12:58:01 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "tune2fs -i 0 /dev/mmcblk0p2 > /dev/null 2> /dev/null"
    
    May 26, 2013 12:58:01 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "lvm.static vgchange -ay --ignorelockingfailure 2> /dev/null"
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat:   6 logical volume(s) in volume group "store" now active
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: File descriptor 3 (socket:[956]) leaked on lvm.static invocation. Parent PID 984: sh
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: File descriptor 4 (/dev/mmcblk0) leaked on lvm.static invocation. Parent PID 984: sh
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: File descriptor 3 (socket:[956]) leaked on lvm.static invocation. Parent PID 986: sh
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: File descriptor 4 (/dev/mmcblk0) leaked on lvm.static invocation. Parent PID 986: sh
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Current LVM configuration:
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Volume Group 0: name store physicalextentsize 8388608
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 0: name root size 478150656 stripes 1 stripesize 0 chunksize 0
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 1: name var size 268435456 stripes 1 stripesize 0 chunksize 0
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 2: name update size 58720256 stripes 1 stripesize 0 chunksize 0
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 3: name log size 41943040 stripes 1 stripesize 0 chunksize 0
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 4: name media size 14881390592 stripes 1 stripesize 0 chunksize 0
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 5: name swap size 134217728 stripes 1 stripesize 0 chunksize 0
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> LVM configuration not changed
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Using existing LVM configuration
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "lvm.static vgchange -ay --ignorelockingfailure store 2> /dev/null"
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat:   6 logical volume(s) in volume group "store" now active
    
    May 26, 2013 12:58:02 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "mke2fs -j -b4096 -m0 -L / /dev/mapper/store-root > /dev/null 2> /dev/null"
    
    May 26, 2013 12:58:11 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "tune2fs -i 0 /dev/mapper/store-root > /dev/null 2> /dev/null"
    
    May 26, 2013 12:58:11 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "mke2fs -j -b4096 -m0 -L /var /dev/mapper/store-var > /dev/null 2> /dev/null"
    
    May 26, 2013 12:58:21 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "tune2fs -i 0 /dev/mapper/store-var > /dev/null 2> /dev/null"
    
    May 26, 2013 12:58:21 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "mke2fs -j -b4096 -m0 -L /var/lib/update /dev/mapper/store-update > /dev/null 2> /dev/null"
    
    May 26, 2013 12:58:24 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "tune2fs -i 0 /dev/mapper/store-update > /dev/null 2> /dev/null"
    
    May 26, 2013 12:58:24 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "mke2fs -j -b4096 -m0 -L /var/log /dev/mapper/store-log > /dev/null 2> /dev/null"
    
    May 26, 2013 12:58:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "tune2fs -i 0 /dev/mapper/store-log > /dev/null 2> /dev/null"
    
    May 26, 2013 12:58:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> mount /dev/mapper/store-root on /tmp/tcmnt_919 as ext3
    
    May 26, 2013 12:58:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running mkdir -p /tmp/tcmnt_919/boot
    
    May 26, 2013 12:58:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> mount /dev/mmcblk0p2 on /tmp/tcmnt_919/boot as ext3
    
    May 26, 2013 12:58:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running mkdir -p /tmp/tcmnt_919/var
    
    May 26, 2013 12:58:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> mount /dev/mapper/store-var on /tmp/tcmnt_919/var as ext3
    
    May 26, 2013 12:58:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running mkdir -p /tmp/tcmnt_919/var/log
    
    May 26, 2013 12:58:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> mount /dev/mapper/store-log on /tmp/tcmnt_919/var/log as ext3
    
    May 26, 2013 12:58:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running mkdir -p /tmp/tcmnt_919/var/lib/update
    
    May 26, 2013 12:58:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> mount /dev/mapper/store-update on /tmp/tcmnt_919/var/lib/update as ext3
    
    May 26, 2013 12:58:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Starting feeder loop for tar subprocess
    
    May 26, 2013 12:58:36 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 5 percent complete
    
    May 26, 2013 12:58:45 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 10 percent complete
    
    May 26, 2013 12:58:58 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 15 percent complete
    
    May 26, 2013 12:59:07 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 20 percent complete
    
    May 26, 2013 12:59:22 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 25 percent complete
    
    May 26, 2013 12:59:34 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 30 percent complete
    
    May 26, 2013 12:59:40 AM com.palm.novacom.internal.NovacomSocketStream write
    WARNING: SocketException Cmd: file:///sbin/trenchcoat
    May 26, 2013 12:59:40 AM com.palm.nova.installer.recoverytool.CardController postFlashEvent
    WARNING: Flash Failure 
    java.net.SocketException: Broken pipe from file:///sbin/trenchcoat
    	at java.net.SocketOutputStream.socketWrite0(Native Method)
    	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
    	at java.net.SocketOutputStream.write(SocketOutputStream.java:141)
    	at com.palm.novacom.internal.PacketWriter.write(PacketWriter.java:30)
    	at com.palm.novacom.internal.NovacomSocketStream.write(NovacomSocketStream.java:181)
    	at com.palm.novacom.internal.NovacomBaseStream.write(NovacomBaseStream.java:21)
    	at com.palm.novacom.internal.NovacomBaseStream.write(NovacomBaseStream.java:69)
    	at com.palm.nova.installer.core.stages.TrenchcoatStage.run(TrenchcoatStage.java:81)
    	at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:243)
    	at java.lang.Thread.run(Thread.java:722)
    
    May 26, 2013 12:59:40 AM com.palm.nova.installer.recoverytool.CardController postFlashEvent
    INFO: Flash End time (Fail) 1369547980791
    May 26, 2013 12:59:42 AM com.palm.nova.installer.recoverytool.CardController handleFailCase
    INFO: something failed, query to see if device is plugged in
    May 26, 2013 12:59:42 AM com.palm.nova.installer.recoverytool.CardController handleFailCase
    INFO: exiting handleFailCase()
    java.net.SocketException: Broken pipe from file:///sbin/trenchcoat
    	at java.net.SocketOutputStream.socketWrite0(Native Method)
    	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:109)
    	at java.net.SocketOutputStream.write(SocketOutputStream.java:141)
    	at com.palm.novacom.internal.PacketWriter.write(PacketWriter.java:30)
    	at com.palm.novacom.internal.NovacomSocketStream.write(NovacomSocketStream.java:181)
    	at com.palm.novacom.internal.NovacomBaseStream.write(NovacomBaseStream.java:21)
    	at com.palm.novacom.internal.NovacomBaseStream.write(NovacomBaseStream.java:69)
    	at com.palm.nova.installer.core.stages.TrenchcoatStage.run(TrenchcoatStage.java:81)
    	at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:243)
    	at java.lang.Thread.run(Thread.java:722)
    May 26, 2013 12:59:43 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got controller
    May 26, 2013 12:59:43 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got devices 1
    May 26, 2013 12:59:43 AM com.palm.nova.installer.recoverytool.CardController runnerFinished
    INFO: device runner done
    May 26, 2013 12:59:43 AM com.palm.nova.installer.recoverytool.CardController runnerFinished
    WARNING: flashing failed, move to failed card
    Attached Files Attached Files
  3. #23  
    @iDG,

    Thank you for the incredibly detailed guide that this thread is turning into...

    @OP,

    That sounds like the phone has got some hardware damage, if it's back to displaying the same problem that caused the previous owner to sell it in the first place...

    Perhaps the flash has a "bad cluster" that holds something that is vital to the boot process, or the firmware of an unrelated chip (not ssd/flash) goes bad and is not responding during the boot sequence. But my guess is that it's the former and not the latter.

    If the flash memory's write-leveling algorithm somehow got screwed up, there might be a possibility that a portion the chip is burned-in from overuse..

    So if you ever get it to Doctor properly again and it resets after booting, it would be helpful to try to diagnose the problem instead of using the "one size fits all" solution that wipes the previous state of the device.
    Last edited by Remy X; 05/26/2013 at 02:27 AM.
  4.    #24  
    Quote Originally Posted by Remy X View Post
    That sounds like the phone has got some hardware damage, if it's back to displaying the same problem that caused the previous owner to sell it in the first place...

    So if you ever get it to Doctor properly again and it resets after booting, it would be helpful to try to diagnose the problem instead of using the "one size fits all" solution that wipes the previous state of the device.
    So it's probably really bricked then? That's a shame. Well, I'll keep trying to get it to doctor fully and update if it does. Then maybe we can figure out what's wrong.

    I wonder how it could be hardware damage... the phone looks like its barely used. Unless the previous owner swapped out the internals. Well, its not like I paid much for it.


    @iDG
    Thanks for all the help. Do you have a Paypal donate button somewhere? I don't have much to give but I'd like to give $5 or so.
  5. iDG
    iDG is offline
    iDG's Avatar
    Posts
    37 Posts
    #25  
    Quote Originally Posted by ssjcho View Post
    so I run try running the doctor again, and this time, the device restarts in the middle of the doctor and says Phone Disconnected. Every time I run the doctor now, it gets disconnected (and I didn't pay close enough attention to exactly where) and I get no errors. It seems to reset by itself randomly and now is unable to boot.
    There may be some kind of hardware damage to the device. If the damage is in the flash it may still be possible to allocate the bad sectors. The fact is that the flash is not a "naked" NAND device, but an embedded mmc, so it should do bad sector remaps on its own. User visible errors mean the device is more or less toast.

    If you're in for some more tests (that are more of scientific interest than anything else), while the doctor is running, the Pre is accessible via novaterm. The installer writes its (more or less detailed) logs to the /tmp device. You might retrieve them to see what's happening.
  6. iDG
    iDG is offline
    iDG's Avatar
    Posts
    37 Posts
    #26  
    Quote Originally Posted by ssjcho View Post
    @iDG
    Thanks for all the help. Do you have a Paypal donate button somewhere? I don't have much to give but I'd like to give $5 or so.
    I'm not really in the "donation" business .
    If I want to be paid to do something, I clearly state the price beforehand.

    And, as it stands, it appears we didn't actually fix anything.
  7. #27  
    Quote Originally Posted by ssjcho View Post
    So it's probably really bricked then? That's a shame. Well, I'll keep trying to get it to doctor fully and update if it does. Then maybe we can figure out what's wrong.

    I wonder how it could be hardware damage... the phone looks like its barely used. Unless the previous owner swapped out the internals. Well, its not like I paid much for it.


    @iDG
    Thanks for all the help. Do you have a Paypal donate button somewhere? I don't have much to give but I'd like to give $5 or so.
    If it looks barely used, i'd figure it was fried by a power surge. I have a router like that (WRT54G) that was given to me for free in its current condition, and the code that governs the WAN port (that connects to modem) always gets written to the bad sector somewhere, so remapping the WAN port to any other good port does nothing and it's unable to utilize the "idea" of having a WAN port... since every hardware port on it is good, the router has become a WiFi hub, and might even be usable as a repeater. I haven't tested that configuration, but when i bring it home from the storage unit, i might.

    I've also owned a nice little Gateway desktop with a DVD burner and everything, that i also got for free from another person. I was told that it was completely unbootable, but when i brought it home, it booted up right away and lasted for 5 hours. I thought i was in the clear, but then it reset and i could never get it to boot again. From the looks of it, the BIOS chip was bad, so the most successful start after the reset did not even display the Gateway logo, but a colorful checkerboard of ASCII characters, i think it was green, red and black backgrounds and things like the @, copyright symbol, the british pound, a few accented letters

    So don't feel bad, your Pre isn't the most valuable device i've seen to have gone bad this way
  8.    #28  
    Quote Originally Posted by iDG View Post
    I'm not really in the "donation" business .
    If I want to be paid to do something, I clearly state the price beforehand.

    And, as it stands, it appears we didn't actually fix anything.
    Haha very true. Still, appreciate the fact that you always replied and walked me through everything. Too bad it didn't turn out better. I was also trying to fix an iphone around the same time I posted here, and I posted to some apple specific forum for help. That thread is still unanswered so really appreciate the help I got here.


    Quote Originally Posted by iDG
    If you're in for some more tests (that are more of scientific interest than anything else), while the doctor is running, the Pre is accessible via novaterm. The installer writes its (more or less detailed) logs to the /tmp device. You might retrieve them to see what's happening.
    I tried novaterm while the doctor was running, but the doctor didn't run long enough for me to connect and do anything. When I checked after I closed the doctor, there was nothing in the /tmp folder. Is whatever logs stored there during the doctor gone after its closed?

    I was able to novaterm without a problem this time by membooting. Anything you guys suggest trying to figure out what's wrong here?
  9. iDG
    iDG is offline
    iDG's Avatar
    Posts
    37 Posts
    #29  
    Quote Originally Posted by ssjcho View Post
    I was also trying to fix an iphone around the same time I posted here, and I posted to some apple specific forum for help. That thread is still unanswered so really appreciate the help I got here
    Fixing an iPhone is far much difficult, due to the security features of the device.

    I tried novaterm while the doctor was running, but the doctor didn't run long enough for me to connect and do anything. When I checked after I closed the doctor, there was nothing in the /tmp folder. Is whatever logs stored there during the doctor gone after its closed?
    /tmp is either a tmpfs or in the ramdisk itself, so it goes away after reboot.
    So, The doctor now fails instantly?

    I was able to novaterm without a problem this time by membooting. Anything you guys suggest trying to figure out what's wrong here?
    You could memboot, and try to see if reading the complete flash generates an error:

    Code:
    dd if=/dev/mmcblk0 of=/dev/null bs=1M
    You could also try to see if writing to the flash causes an error:
    Code:
    dd if=/dev/zero of=/dev/mmcblk0p3 bs=1M
    After this, you will need to redo:
    Code:
    lvm.static pvcreate -v /dev/mmcblk0p3
    lvm.static vgcreate -s 8M store /dev/mmcblk0p3
    lvm.static vgscan --ignorelockingfailure
    lvm.static vgchange -ay --ignorelockingfailure
    lvm.static lvcreate -l 57 -i 1 -M y --major 254 --minor 0 -n root store
    lvm.static lvcreate -l 8 -i 1 -M y --major 254 --minor 1 -n var store
    lvm.static lvcreate -l 2 -i 1 -M y --major 254 --minor 2 -n update store
    lvm.static lvcreate -l 3 -i 1 -M y --major 254 --minor 3 -n log store
    lvm.static lvcreate -l 32 -i 1 -M y --major 254 --minor 4 -n mojodb store
    lvm.static lvcreate -l 24 -i 1 -M y --major 254 --minor 5 -n filecache store
    lvm.static lvcreate -l 1748 -i 1 -M y --major 254 --minor 6 -n media store
    lvm.static lvcreate -l 16 -i 1 -M y --major 254 --minor 7 -n swap store
    lvm.static vgscan --ignorelockingfailure
    lvm.static vgchange -ay --ignorelockingfailure
    mkdosfs -f 1 -s 64 /dev/store/media
    as the partition will be wiped.
  10.    #30  
    Quote Originally Posted by iDG View Post
    So, The doctor now fails instantly?
    Well, it fails somewhere in between 12% and 30% usually. Loses device connection.

    Quote Originally Posted by iDG View Post
    You could memboot, and try to see if reading the complete flash generates an error:
    This did not give an error. Took a while though which is probably normal.

    Quote Originally Posted by iDG View Post
    You could also try to see if writing to the flash causes an error:
    I tried this 3 times. First two times, it lost the connection after a few minutes, just like it does for the doctor. Third time, it's still running as I write this, and it has been almost an hour. This seems to be what the problem is, which makes sense since the doctor fails at some point while trying to write.

    Haven't tried redoing the partitions though it will probably run fine like it did last time. Is it possible to isolate the area of the disk that is not working and create partitions around it? I imagine it would be complicated.
  11.    #31  
    Okay so the third try did finish without errors, I think:
    Code:
    root@palm-webos-device:/# dd if=/dev/zero of=/dev/mmcblk0p3 bs=1M
    
    dd: writing '/dev/mmcblk0p3': No space left on device
    15153+0 records in
    15151+1 records out
    
    root@palm-webos-device:/# lvm.static pvcreate -v /dev/mmcblk0p3
    File descriptor 3 (socket:[925]) leaked on lvm.static invocation. Parent PID 762: /bin/sh
    
    Thu May 30 21:26:23 2013
     novacomd socket was closed prematurely
    novacom: unexpected EOF from server
    But the device disconnected right after I ran the first step of rebuilding the partitions. So maybe it was a fluke? or some part of it is just "starting" to fail.
  12. iDG
    iDG is offline
    iDG's Avatar
    Posts
    37 Posts
    #32  
    Quote Originally Posted by ssjcho View Post
    Okay so the third try did finish without errors, I think
    Yep.

    But the device disconnected right after I ran the first step of rebuilding the partitions. So maybe it was a fluke? or some part of it is just "starting" to fail.
    Now the fact is that the emmc inside the might not actually return an error during the write (it is quite likely it won't, as the error correction and wear level happen inside the emmc). but will start act in some weird way that causes the device to crash.

    We can't really "find" the damaged part of the flash, but we could try to create a smaller partition. This requires a custom webos doctor.

    The partition informations are in the "castle.xml" file:
    Code:
    	<Flash type="mmc" alignment="524288" device="/dev/mmcblk0">
    		<Entry type="mbr" size="512" align="false"/>
    		<Entry type="bootloader" size="192KB" file="${BOOTIE}"/>
    		<Entry type="nvram" size="4MB">
    			<Section name="env" type="env" size="16KB">
    				<Val name="installer" value="trenchcoat"/>
    				<Val name="autoboot" action="delete"/>
    				<Val name="bootfile" action="delete"/>
    			</Section>
    			<Section name="tokens" type="token" size="4KB">
    				<Val name="installer" value="trenchcoat"/>
    			</Section>
    			<Section name="logo-boot" type="image" file="BootLogo.tga"/>
    			<Section name="logo-chg" type="image" file="Charging.tga"/>
    			<Section name="logo-badchg" type="image" file="NoPower.tga"/>
    			<Section name="logo-nobatt" type="image" file="NoBatt.tga"/>
    			<Section name="logo-badsys" type="image" file="BadSys.tga"/>
    			<Section name="logo-nosys" type="image" file="NoSys.tga"/>
    			<Section name="logo-sync" type="image" file="Sync.tga"/>
    			<Section name="logo-panic" type="image" file="Panic.tga"/>
    			<Section name="logo-disk" type="image" file="Disk.tga"/>
    		</Entry>
    		<Entry type="ext3" size="32MB" mount="/boot"/>
    		<Entry type="lvm" id="pv" size="*" metadatasize="1532KB" metadatacopies="2"/>
    	</Flash>
    By changing that line to:
    Code:
    <Entry type="lvm" id="pv" size="8192MB" metadatasize="1532KB" metadatacopies="2"/>
    only half of the flash will be used and, if you're lucky, it might work.
  13.    #33  
    Quote Originally Posted by iDG View Post
    Yep.



    We can't really "find" the damaged part of the flash, but we could try to create a smaller partition. This requires a custom webos doctor.

    By changing that line to:
    Code:
    <Entry type="lvm" id="pv" size="8192MB" metadatasize="1532KB" metadatacopies="2"/>
    only half of the flash will be used and, if you're lucky, it might work.

    Hey, sorry for not posting for a few days but I've been busy lately. I got around to trying this today. Made a doctor with a reduced flash size and tried running it. It seems to run for longer than before. The progress bar on the Java applet goes up to 30-70% now but still runs into device disconnnected. Think it would work to try an even smaller partition?

    Here's the terminal output. Looks like it almost finished this time, but something happened.
    Code:
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'ProdSN' to offset 476, gen 1, len 14
    
    <INFO> write_tokens: writing token 'ProdSN' to offset 476, gen 1, len 14
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> write_tokens: writing token 'installer' to offset 528, gen 1, len 10
    
    <INFO> write_tokens: writing token 'installer' to offset 528, gen 1, len 10
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-boot' offset 24576 len 160044
    
    <INFO> nvram section 'logo-boot' offset 24576 len 160044
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-chg' offset 188416 len 92565
    
    <INFO> nvram section 'logo-chg' offset 188416 len 92565
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Sent 74779 bytes
    
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Sending File: Disk.tga
    
    ./
    ./castleumtsfw.tar
    ./installer.xml
    ./BootLogo.tga
    ./NoBatt.tga
    ./castlecdma_evt1_fw.tar
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-badchg' offset 282624 len 48178
    
    <INFO> nvram section 'logo-badchg' offset 282624 len 48178
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-nobatt' offset 331776 len 87835
    
    <INFO> nvram section 'logo-nobatt' offset 331776 len 87835
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-badsys' offset 421888 len 26853
    
    <INFO> nvram section 'logo-badsys' offset 421888 len 26853
    ./castle.xml
    ./Charging.tga
    ./BadSys.tga
    ./boot-castle.bin
    ./Disk.tga
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Sent 36673 bytes
    
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Sending File: nova-cust-image-castle.rootfs.tar.gz
    
    ./
    ./castleumtsfw.tar
    ./installer.xml
    ./BootLogo.tga
    ./NoBatt.tga
    ./castlecdma_evt1_fw.tar
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-nosys' offset 450560 len 26853
    
    <INFO> nvram section 'logo-nosys' offset 450560 len 26853
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-sync' offset 479232 len 71862
    
    <INFO> nvram section 'logo-sync' offset 479232 len 71862
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-panic' offset 552960 len 74779
    
    <INFO> nvram section 'logo-panic' offset 552960 len 74779
    Jun 06, 2013 11:30:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> nvram section 'logo-disk' offset 630784 len 36673
    
    <INFO> nvram section 'logo-disk' offset 630784 len 36673
    ./castle.xml
    ./Charging.tga
    ./BadSys.tga
    ./boot-castle.bin
    ./Disk.tga
    ./nova-cust-image-castle.rootfs.tar.gz
    Jun 06, 2013 11:30:20 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "mke2fs -j -b4096 -m0 -L /boot /dev/mmcblk0p2 > /dev/null 2> /dev/null"
    
    <INFO> Running "mke2fs -j -b4096 -m0 -L /boot /dev/mmcblk0p2 > /dev/null 2> /dev/null"
    Jun 06, 2013 11:30:22 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "tune2fs -i 0 /dev/mmcblk0p2 > /dev/null 2> /dev/null"
    
    <INFO> Running "tune2fs -i 0 /dev/mmcblk0p2 > /dev/null 2> /dev/null"
    Jun 06, 2013 11:30:22 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "lvm.static vgchange -ay --ignorelockingfailure 2> /dev/null"
    
    <INFO> Running "lvm.static vgchange -ay --ignorelockingfailure 2> /dev/null"
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat:   6 logical volume(s) in volume group "store" now active
    
      6 logical volume(s) in volume group "store" now active
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: File descriptor 3 (socket:[963]) leaked on lvm.static invocation. Parent PID 997: sh
    
    File descriptor 3 (socket:[963]) leaked on lvm.static invocation. Parent PID 997: sh
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: File descriptor 4 (/dev/mmcblk0) leaked on lvm.static invocation. Parent PID 997: sh
    
    File descriptor 4 (/dev/mmcblk0) leaked on lvm.static invocation. Parent PID 997: sh
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: File descriptor 3 (socket:[963]) leaked on lvm.static invocation. Parent PID 999: sh
    
    File descriptor 3 (socket:[963]) leaked on lvm.static invocation. Parent PID 999: sh
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: File descriptor 4 (/dev/mmcblk0) leaked on lvm.static invocation. Parent PID 999: sh
    
    File descriptor 4 (/dev/mmcblk0) leaked on lvm.static invocation. Parent PID 999: sh
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Current LVM configuration:
    
    <INFO> Current LVM configuration:
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Volume Group 0: name store physicalextentsize 8388608
    
    <INFO> Volume Group 0: name store physicalextentsize 8388608
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 0: name root size 478150656 stripes 1 stripesize 0 chunksize 0
    
    <INFO>   Logical Volume 0: name root size 478150656 stripes 1 stripesize 0 chunksize 0
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 1: name var size 268435456 stripes 1 stripesize 0 chunksize 0
    
    <INFO>   Logical Volume 1: name var size 268435456 stripes 1 stripesize 0 chunksize 0
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 2: name update size 58720256 stripes 1 stripesize 0 chunksize 0
    
    <INFO>   Logical Volume 2: name update size 58720256 stripes 1 stripesize 0 chunksize 0
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 3: name log size 41943040 stripes 1 stripesize 0 chunksize 0
    
    <INFO>   Logical Volume 3: name log size 41943040 stripes 1 stripesize 0 chunksize 0
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 4: name media size 7591690240 stripes 1 stripesize 0 chunksize 0
    
    <INFO>   Logical Volume 4: name media size 7591690240 stripes 1 stripesize 0 chunksize 0
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO>   Logical Volume 5: name swap size 134217728 stripes 1 stripesize 0 chunksize 0
    
    <INFO>   Logical Volume 5: name swap size 134217728 stripes 1 stripesize 0 chunksize 0
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> LVM configuration not changed
    
    <INFO> LVM configuration not changed
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Using existing LVM configuration
    
    <INFO> Using existing LVM configuration
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "lvm.static vgchange -ay --ignorelockingfailure store 2> /dev/null"
    
    <INFO> Running "lvm.static vgchange -ay --ignorelockingfailure store 2> /dev/null"
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat:   6 logical volume(s) in volume group "store" now active
    
      6 logical volume(s) in volume group "store" now active
    Jun 06, 2013 11:30:23 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "mke2fs -j -b4096 -m0 -L / /dev/mapper/store-root > /dev/null 2> /dev/null"
    
    <INFO> Running "mke2fs -j -b4096 -m0 -L / /dev/mapper/store-root > /dev/null 2> /dev/null"
    Jun 06, 2013 11:30:31 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "tune2fs -i 0 /dev/mapper/store-root > /dev/null 2> /dev/null"
    
    <INFO> Running "tune2fs -i 0 /dev/mapper/store-root > /dev/null 2> /dev/null"
    Jun 06, 2013 11:30:31 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "mke2fs -j -b4096 -m0 -L /var /dev/mapper/store-var > /dev/null 2> /dev/null"
    
    <INFO> Running "mke2fs -j -b4096 -m0 -L /var /dev/mapper/store-var > /dev/null 2> /dev/null"
    Jun 06, 2013 11:30:41 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "tune2fs -i 0 /dev/mapper/store-var > /dev/null 2> /dev/null"
    
    <INFO> Running "tune2fs -i 0 /dev/mapper/store-var > /dev/null 2> /dev/null"
    Jun 06, 2013 11:30:41 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "mke2fs -j -b4096 -m0 -L /var/lib/update /dev/mapper/store-update > /dev/null 2> /dev/null"
    
    <INFO> Running "mke2fs -j -b4096 -m0 -L /var/lib/update /dev/mapper/store-update > /dev/null 2> /dev/null"
    Jun 06, 2013 11:30:43 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "tune2fs -i 0 /dev/mapper/store-update > /dev/null 2> /dev/null"
    
    <INFO> Running "tune2fs -i 0 /dev/mapper/store-update > /dev/null 2> /dev/null"
    Jun 06, 2013 11:30:43 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "mke2fs -j -b4096 -m0 -L /var/log /dev/mapper/store-log > /dev/null 2> /dev/null"
    
    <INFO> Running "mke2fs -j -b4096 -m0 -L /var/log /dev/mapper/store-log > /dev/null 2> /dev/null"
    Jun 06, 2013 11:30:46 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running "tune2fs -i 0 /dev/mapper/store-log > /dev/null 2> /dev/null"
    
    <INFO> Running "tune2fs -i 0 /dev/mapper/store-log > /dev/null 2> /dev/null"
    Jun 06, 2013 11:30:46 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> mount /dev/mapper/store-root on /tmp/tcmnt_925 as ext3
    
    <INFO> mount /dev/mapper/store-root on /tmp/tcmnt_925 as ext3
    Jun 06, 2013 11:30:46 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running mkdir -p /tmp/tcmnt_925/boot
    
    <INFO> Running mkdir -p /tmp/tcmnt_925/boot
    Jun 06, 2013 11:30:46 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> mount /dev/mmcblk0p2 on /tmp/tcmnt_925/boot as ext3
    
    <INFO> mount /dev/mmcblk0p2 on /tmp/tcmnt_925/boot as ext3
    Jun 06, 2013 11:30:46 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running mkdir -p /tmp/tcmnt_925/var
    
    <INFO> Running mkdir -p /tmp/tcmnt_925/var
    Jun 06, 2013 11:30:46 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> mount /dev/mapper/store-var on /tmp/tcmnt_925/var as ext3
    
    <INFO> mount /dev/mapper/store-var on /tmp/tcmnt_925/var as ext3
    Jun 06, 2013 11:30:46 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running mkdir -p /tmp/tcmnt_925/var/log
    
    <INFO> Running mkdir -p /tmp/tcmnt_925/var/log
    Jun 06, 2013 11:30:46 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> mount /dev/mapper/store-log on /tmp/tcmnt_925/var/log as ext3
    
    <INFO> mount /dev/mapper/store-log on /tmp/tcmnt_925/var/log as ext3
    Jun 06, 2013 11:30:46 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Running mkdir -p /tmp/tcmnt_925/var/lib/update
    
    <INFO> Running mkdir -p /tmp/tcmnt_925/var/lib/update
    Jun 06, 2013 11:30:46 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> mount /dev/mapper/store-update on /tmp/tcmnt_925/var/lib/update as ext3
    
    <INFO> mount /dev/mapper/store-update on /tmp/tcmnt_925/var/lib/update as ext3
    Jun 06, 2013 11:30:46 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> Starting feeder loop for tar subprocess
    
    <INFO> Starting feeder loop for tar subprocess
    Jun 06, 2013 11:30:52 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 5 percent complete
    
    <INFO> 5 percent complete
    Jun 06, 2013 11:31:01 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 10 percent complete
    
    <INFO> 10 percent complete
    Jun 06, 2013 11:31:14 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 15 percent complete
    
    <INFO> 15 percent complete
    Jun 06, 2013 11:31:26 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 20 percent complete
    
    <INFO> 20 percent complete
    Jun 06, 2013 11:31:36 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 25 percent complete
    
    <INFO> 25 percent complete
    Jun 06, 2013 11:31:47 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 30 percent complete
    
    <INFO> 30 percent complete
    Jun 06, 2013 11:31:59 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 35 percent complete
    
    <INFO> 35 percent complete
    Jun 06, 2013 11:32:09 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 40 percent complete
    
    <INFO> 40 percent complete
    Jun 06, 2013 11:32:19 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 45 percent complete
    
    <INFO> 45 percent complete
    Jun 06, 2013 11:32:30 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 50 percent complete
    
    <INFO> 50 percent complete
    Jun 06, 2013 11:32:39 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 55 percent complete
    
    <INFO> 55 percent complete
    Jun 06, 2013 11:32:49 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 60 percent complete
    
    <INFO> 60 percent complete
    Jun 06, 2013 11:33:01 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 65 percent complete
    
    <INFO> 65 percent complete
    Jun 06, 2013 11:33:13 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 70 percent complete
    
    <INFO> 70 percent complete
    Jun 06, 2013 11:33:29 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 75 percent complete
    
    <INFO> 75 percent complete
    Jun 06, 2013 11:33:44 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 80 percent complete
    
    <INFO> 80 percent complete
    Jun 06, 2013 11:33:50 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 85 percent complete
    
    <INFO> 85 percent complete
    Jun 06, 2013 11:34:03 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 90 percent complete
    
    <INFO> 90 percent complete
    Jun 06, 2013 11:34:16 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: <INFO> 95 percent complete
    
    <INFO> 95 percent complete
    Jun 06, 2013 11:34:20 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Sent 160428781 bytes
    
    Jun 06, 2013 11:34:20 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Waiting....
    
    Jun 06, 2013 11:34:40 AM com.palm.nova.installer.recoverytool.CardController logPrint
    INFO: Trenchcoat: Finished!
    
    Jun 06, 2013 11:34:40 AM com.palm.novacom.internal.NovacomSocketStream waitForReturnCode
    WARNING: Throwing Exception Cmd: file:///sbin/trenchcoat
    java.io.IOException: No return code found in stream from file:///sbin/trenchcoat
    Jun 06, 2013 11:34:40 AM com.palm.nova.installer.recoverytool.CardController postFlashEvent
    WARNING: Flash Failure 
    java.io.IOException: No return code found in stream from file:///sbin/trenchcoat
    	at com.palm.novacom.internal.NovacomSocketStream.waitForReturnCode(NovacomSocketStream.java:90)
    	at com.palm.nova.installer.core.stages.TrenchcoatStage.run(TrenchcoatStage.java:98)
    	at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:243)
    	at java.lang.Thread.run(Thread.java:722)
    
    Jun 06, 2013 11:34:40 AM com.palm.nova.installer.recoverytool.CardController postFlashEvent
    INFO: Flash End time (Fail) 1370536480607
    from /tmp/PalmWebOsRecoveryToolLog0.log.2
    to /tmp/palmInstallerError0.log
    from /tmp/PalmWebOsRecoveryToolLog0.log.0.lck
    to /tmp/palmInstallerError1.log
    Jun 06, 2013 11:34:42 AM com.palm.nova.installer.recoverytool.CardController handleFailCase
    INFO: something failed, query to see if device is plugged in
    Jun 06, 2013 11:34:42 AM com.palm.nova.installer.recoverytool.CardController handleFailCase
    INFO: exiting handleFailCase()
    java.io.IOException: No return code found in stream from file:///sbin/trenchcoat
    	at com.palm.novacom.internal.NovacomSocketStream.waitForReturnCode(NovacomSocketStream.java:90)
    	at com.palm.nova.installer.core.stages.TrenchcoatStage.run(TrenchcoatStage.java:98)
    	at com.palm.nova.installer.core.FlasherThread.run(FlasherThread.java:243)
    	at java.lang.Thread.run(Thread.java:722)
    Jun 06, 2013 11:34:43 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Jun 06, 2013 11:34:43 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got devices 0
    Jun 06, 2013 11:34:44 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Jun 06, 2013 11:34:44 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got devices 0
    Jun 06, 2013 11:34:45 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Jun 06, 2013 11:34:45 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got devices 0
    Jun 06, 2013 11:34:46 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Jun 06, 2013 11:34:46 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got devices 0
    Jun 06, 2013 11:34:47 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got controller
    Jun 06, 2013 11:34:47 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: got devices 0
    Jun 06, 2013 11:34:47 AM com.palm.nova.installer.recoverytool.runner.DeviceDiscoveryRunner$DeviceDiscoveryThread run
    INFO: timed out looking for device
    Jun 06, 2013 11:34:47 AM com.palm.nova.installer.recoverytool.CardController runnerFinished
    INFO: device runner done
    Jun 06, 2013 11:34:47 AM com.palm.nova.installer.recoverytool.CardController runnerFinished
    WARNING: the device seems to have been unplugged, try again
  14. iDG
    iDG is offline
    iDG's Avatar
    Posts
    37 Posts
    #34  
    Quote Originally Posted by ssjcho View Post
    Hey, sorry for not posting for a few days but I've been busy lately. I got around to trying this today. Made a doctor with a reduced flash size and tried running it. It seems to run for longer than before. The progress bar on the Java applet goes up to 30-70% now but still runs into device disconnnected. Think it would work to try an even smaller partition?
    You can try. Another try would be to enlarge the (almost empty) boot partition (/dev/mmcblk0p1) to move the pv partition (/dev/mmcblk0p2) in a different spot:
    Code:
    <Entry type="ext3" size="8192MB" mount="/boot"/>
    and leaving the media partition as its default size:
    Code:
    <Entry type="lvm" id="pv" size="*" metadatasize="1532KB" metadatacopies="2"/>
    As I wrote before, I'm not completely sure if this will actually change something -- the emmc microcontroller behavior is unpredictable from the "outside".
  15. #35  
    I wonder if the flash memory chip can be de-soldered and replaced with one from a water-damaged board. Probably too much of a hassle, but it's something that's popped into my mind

    My thinking is that partitioning probably won't contain the emmc pointer in one partition nor keep it from eventually reaching the bad spot, but from my experience with a defective MicroSD card, keeping the damaged spot permanently overwritten can make the rest of the flash usable.

    If we could just partition the flash without writing anything , and then fill the whole flash with predictible "garbage" data in standard-sized blacks, then the blocks could be "interrogated" and report to commanline, which are reliably good and we would know at which point accessing the disc will crash the device

    Of course, in the worst case, there will be no way of overwriting the defect, and it will always remain "available" to new writes...
    Last edited by Remy X; 06/08/2013 at 03:05 PM.
  16. iDG
    iDG is offline
    iDG's Avatar
    Posts
    37 Posts
    #36  
    Quote Originally Posted by Remy X View Post
    I wonder if the flash memory chip can be de-soldered and replaced with one from a water-damaged board. Probably too much of a hassle, but it's something that's popped into my mind
    possible, yes. but it requires non trivial tools.

    Of course, in the worst case, there will be no way of overwriting the defect, and it will always remain "available" to new writes...
    problem is that there's no easy way to detect how the low-level wear levelling algorithm handles the physical media. from the outside, a mmc / sd memory only looks like a serie of 512 bytes block. Internally the microcontroller may have a fixed map of logical block groups to physical flash segments each one with its own overflow area, or it may simple have a logical to physical translation table that is built during each write. In the first case, avoiding a group of logical blocks actually skips a physical flash segment (so you may eventually go around the damaged part) whereas in the second case, the bad blocks are simply remapped on the fly, so if you use smaller physical partitions the number of blocks that will be relocated will decrease (allowing the emmc to behave correctly).

    it might even be that the flash works with a simple fixed spare map that was exhausted, so nothing will actually work unless it is preceded by a "low level format" of sorts, that erases the spare map. given there's not really much left to try, i could whip something out that sends a CMD38 the the emmc.
    Remy X likes this.
Page 2 of 2 FirstFirst 12

Similar Threads

  1. Verizon Pre 2 Sprint Franken Token Error
    By Longshotx in forum Palm Pre 2
    Replies: 4
    Last Post: 09/18/2012, 11:25 AM
  2. How to rebuild md5sums?
    By nodevel in forum webOS Development
    Replies: 1
    Last Post: 11/08/2011, 10:48 AM
  3. BRICKED PRE+ - If this is not a bricked one tell me why....
    By maxi_gmv in forum Palm Pre and Pre Plus
    Replies: 13
    Last Post: 04/20/2011, 11:19 AM
  4. Replies: 8
    Last Post: 09/10/2010, 05:19 AM
  5. calander colors lost on rebuild
    By gpshemi in forum Palm OS Devices & Apps
    Replies: 0
    Last Post: 10/15/2008, 07:48 AM

Tags for this Thread

Posting Permissions