Hey Mike, thanks for the log files--those are indeed very helpful and informative!
I'm not sure that the issue is necessarily with your PicoTts.apk file since I'm guessing it's simply the last file in the list of files on your /system partition that CWM is backing up.
I'm more concerned about the "
....solibjni_latinime.solibmvs.solibnetlink.sotar: read error: I/O error" portion of the text you separated-out (thank you--made it very easy to see the issue :thumbup
.
Since I don't have an Admire, I can't necessarily match-up the list of files above just prior to the "read error: I/O error" portion, but since the library files typically have .so extensions, I'm guessing that the list of files just before the error is actually (in the "5-18 last_log.txt" file):
libdevicescape-jni.so
libOmxAmrRtpDec.so
libjni_latinime.so
libmvs.so
libnetlink.so
tar: read error: I/O error
and this for the "5-19 last_log.txt" file:
libquramgifmovie.so
libdevicescape-jni.so
libOmxAmrRtpDec.so
tar: read error: I/O error
which does seem to point in the same general vicinity of your /system partition as possibly having bad blocks
.
I would think your next step might be to try to see if running fsck or e2fsck (depending on the type of filesystem your device has--again, I don't know because I don't have your device) to see if that file system checking utility can find and possibly repair (re-chain any bad blocks, etc.) any issues it might find. Note: you can't run those utilities while the device is booted-up in Android or otherwise mounted--you'd typically run those from an adb shell while/when your custom recovery is booted-up and your /system partition is not (yet) mounted.
We're kind of at the place where I'd think you might be better off soliciting further advice from the Admire gurus in this area since I can't provide you any direct experience or knowledge with your particular device and would hate to have your try something that might leave you in the lurch.
Thanks,
-SA