06/12/2011, 05:46 PM
I've had a devil of a time taking my Verizon Pre 2 from 2.0.1 to 2.1.0 using the Meta-Doctor and the meta-verizon-pre2-2.1.0 script, but it looks like the fault was mine. Just to save others the pain, here's what I found:
The doctor kept failing in the middle leaving the phone at the palm.com/ROM screen. It died at the point where it's loaded the ramdisk, saved/flushed the logs, cleaned up, and was just getting going with Trenchcoat. It would load the tokens and then just choke (output edited somewhat for brevity):
This was followed by some Java error messages and "WARNING: flashing failed, move to failed card".
INFO: Trenchcoat: <INFO> Running "mke2fs -q -j -b4096 -m0 -L /boot /dev/mmcblk0p2 > /dev/null"
INFO: Trenchcoat: <INFO> Running "tune2fs -i 0 /dev/mmcblk0p2 > /dev/null 2> /dev/null"
INFO: Trenchcoat: <INFO> Running "lvm.static vgchange -ay --ignorelockingfailure 2> /dev/null"
INFO: Trenchcoat: File descriptor 3 (/dev/mmcblk0) leaked on lvm.static invocation. Parent PID 1243: sh
INFO: Trenchcoat: <INFO> Current LVM configuration, 0 volume groups:
INFO: Trenchcoat: <ERROR> Volume group store not found in existing configuration.
<ERROR> Volume group store not found in existing configuration.
INFO: Trenchcoat: <INFO> Current configuration: 0 volume groups.
INFO: Trenchcoat: <ERROR> CPU-specific initialization failed
<ERROR> CPU-specific initialization failed
INFO: Trenchcoat: Broken pipe
WARNING: SocketException Cmd: file:///sbin/trenchcoat
I initially thought it might be because I'd edited the user options in the Meta-Doctor Makefile to install Preware and testing feeds, but rebuilding the script without that didn't help.
I'd also replaced the boot logo graphic so I tried again (third time's the charm, right?) with a completely fresh download of everything. And it worked. Looking at the output in the section right before failure I noticed this:
I'm guessing here, but I bet that because my logo was a different size than the original one that the offset and length for logo-boot were incorrect in memory and it couldn't mount the filesystems. Or something like that. It was a slightly smaller file than the webos-internals.tga, but different is different.
INFO: Trenchcoat: <INFO> nvram section 'logo-boot' offset 24576 len 98721
Moral of the story: don't change the boot logo graphic, even if you have something really cool to use.