Hi everyone,
I was hoping that I might be able to get a bit of help here. I think, I have a bit of a doozie of a problem. For me it is a doozie anyway, as I'm a bit unfamiliar with with android o/s and have patchy tech knowledge at the best of times. I have some giant gaping holes where someone with my level of experience (a bit above beginner, but hardly advanced) should understand things better.
Anyway, I have a rooted XT910. I bought it rooted, and haven't really played with it much apart from appreciating the fact that I can disable bloatware.
I have been unable to update to JB via the OTA updates since they were rolled out, but hadn't really taken the time to look into why. Pulling out the logfile for the last attempted OTA update, I get the following (sorry for posting the full thing, I just don't want to have missed anything):
Looking at /system/bin/ there is a /system/bin/logwrapper.bak along with the logwrapper file. The modification date on both files is from before I got the phone.
If logwrapper has an incorrect sha1sum, I presume that means it's been corrupted or changed and that's what's interrupting the update? I also presume that logwrapper.bak is a backup of the original logwrapper file (pre-corruption).
I'm loathe to do a factory reset if I can avoid it and would rather fix it this way if possible.
I have Voodoo OTA RootKeeper so I don't lose root in the process of updating.
Finally, I have copied the OTA update file so I don't have to re-download it for the twentieth time, if I whack it and the crc file back in /cache/recovery will that shortcut me have to re-re-re-download, or can I only manually update by factory resetting?
Any help would be massively, massively appreciated. I had a search of the forums and didn't find anything.
Thanks,
Tim
I was hoping that I might be able to get a bit of help here. I think, I have a bit of a doozie of a problem. For me it is a doozie anyway, as I'm a bit unfamiliar with with android o/s and have patchy tech knowledge at the best of times. I have some giant gaping holes where someone with my level of experience (a bit above beginner, but hardly advanced) should understand things better.
Anyway, I have a rooted XT910. I bought it rooted, and haven't really played with it much apart from appreciating the fact that I can disable bloatware.
I have been unable to update to JB via the OTA updates since they were rolled out, but hadn't really taken the time to look into why. Pulling out the logfile for the last attempted OTA update, I get the following (sorry for posting the full thing, I just don't want to have missed anything):
Code:
Starting recovery on Fri May 17 11:17:29 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /emstorage vfat /dev/block/mmcblk1p25 (null) 0
2 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
3 /system ext3 system (null) 0
4 /cache ext3 cache (null) 0
5 /data ext3 userdata (null) 0
6 /misc mtd misc (null) 0
7 /boot mtd boot (null) 0
8 /recovery mtd recovery (null) 0
9 /pds ext3 pds (null) 0
10 /preinstall ext3 preinstall (null) 0
11 /webtop ext3 webtop (null) 0
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
Fixing execute permissions for /cache
I:Got arguments from /cache/recovery/command
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
blk: partition "emstorage" size 8603435008 not a multiple of io_buffer_size 524288
qe 2/1
Command: "/sbin/recovery" "--update_package=/cache/Blur_Version.672.180.41.XT910.Retail.en.EU.zip"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
ro.build.id=6.7.2-180_SPU-19-TA-11.6
ro.build.display.id=6.7.2-180_SPU-19-TA-11.6
ro.build.version.incremental=123456
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Mon Jul 16 11:15:45 CST 2012
ro.build.date.utc=1342408545
ro.build.type=user
ro.build.user=rwxg47
ro.build.host=zch45lnxdroid51
ro.build.tags=release-keys
ro.product.model=XT910
ro.product.brand=MOTO
ro.product.name=spyder_umts
ro.product.device=umts_spyder
ro.product.board=spyder
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=motorola
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=omap4
ro.build.product=spyder_umts
ro.build.description=umts_spyder-user 4.0.4 6.7.2-180_SPU-19-TA-11.6 123456 release-keys
ro.build.fingerprint=MOTO/spyder_umts/umts_spyder:4.0.4/6.7.2-180_SPU-19-TA-11.6/123456:user/release-keys
ro.build.characteristics=default
ro.sf.lcd_density=240
ro.mot.ril.danlist=611,*611,#611
persist.ril.modem.mode=2
windowsmgr.max_events_per_sec=90
ro.ngp_available=1
ro.modem_available=0
ro.telephony.default_network=3
ro.com.google.clientidbase=android-motorola
ro.com.google.clientidbase.am=android-motorola
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.config.vc_call_vol_steps=7
wifi.interface=wlan0
softap.interface=wlan1
wifi.supplicant_scan_interval=45
ro.cdma.otaspnumschema=SELC,1,80,99
ro.cdma.home.operator.numeric=310004
ro.opengles.version=131072
dalvik.vm.heapsize=128m
ro.mot.hw.HAC=1
persist.mot.proximity.touch=1
ro.mot.hw.calibratedImager=1
persist.mot.usb.mediasync=1
ro.service.start.smc=1
mot.proximity.delay=450
mot.proximity.distance=60
ro.kernel.android.ril=yes
persist.ril.mux.noofchannels=10
persist.ril.mux.ttydevice=/dev/ttyO0
persist.ril.features=0x102
persist.ril.mux.retries=500
persist.ril.mux.sleep=2
persist.ril.qmi.overspi=no
ro.telephony.call_ring.multiple=false
ro.telephony.call_ring.delay=3000
ro.setupwizard.enable_bypass=1
ro.cdma.data_retry_config=default_randomization=2000,0,0,120000,180000,540000,960000
ro.mot.phonemode.vzwglobalphone=0
ro.telephony.gsm-routes-us-smsc=0
ro.cdma.home.operator.isnan=1
ro.mot.dpmext=true
keyguard.no_require_sim=true
persist.radio.ap.phonetype=1
sys.mot.ui.launched=false
ro.mot.bindervm.config=120
ro.mot.mynet=true
ro.HorizontalBUA=false
ro.mot.eri=0
ro.cdma.nbpcd=1
persist.mot.gps.smart_battery=1
ro.mot.deep.sleep.supported=true
persist.dbg.kwdt.report=0
ro.hdcp.support=2
ro.mot.ds.fastdormancy.disable=false
persist.ril.event.report=0
com.motorola.cg.lowres=1
com.motorola.cg.tnWidth=160
com.motorola.cg.tnHeight=160
com.motorola.cg.tndisplay=1
ro.mot.hw.navkeyboard.devname=cy8c201xx
ro.camera.sound.forced=1
radio.mtu.size=1500
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=42m
drm.service.enabled=true
persist.ril.modem.ttydevice=/dev/usb/tty2-1:1.4
persist.ril.tcmd.ttydevice=/dev/usb/tty2-1:1.3
persist.ril.diag.ttydevice=/dev/usb/tty2-1:1.0
rild.libpath=/system/lib/moto-ril-multimode.so
gsm.sim.mot.simswap=1
ro.com.google.clientidbase.ms=android-motorola
ro.com.google.clientidbase.gmm=android-motorola
ro.com.google.clientidbase.yt=android-motorola
persist.sys.usb.config=mtp
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.com.google.gmsversion=4.0_r2
ro.crypto.state=unencrypted
ro.media.enc.aud.fileformat=amr
ro.media.enc.aud.codec=amrnb
ro.mot.phonemode.vzw4gphone=0
cdma_ril.libpath=/system/lib/libmoto_ril.so
ro.media.camcorder.1080p=mp4,h264,30,15000000,aac,128000,44100,2
ro.media.camcorder.720p=mp4,h264,30,10000000,aac,128000,44100,2
ro.media.camcorder.d1NTSC=mp4,h264,30,6000000,aac,128000,44100,2
ro.media.camcorder.vga=mp4,h264,30,4000000,aac,128000,44100,2
ro.media.camcorder.cif=mp4,h264,30,1500000,aac,128000,44100,2
ro.media.camcorder.qvga=mp4,h264,15,500000,aac,64000,44100,2
ro.media.camcorder.mms=3gp,h264,15,128000,amrnb,12200,8000,1
ro.media.camcorder.mmsres=qvga
ro.camcorder.zoom=true
ro.media.capture.maxres=5m
ro.media.capture.fast.fps=4
ro.media.capture.slow.fps=120
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=40
ro.media.capture.flashIntensity=100
ro.media.capture.classification=classF
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.mot.setuptype=2
ro.mot.internalsdcard=1
ro.setupwizard.mode=DISABLED
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.com.google.clientid=android-motorola
ro.build.version.full=Blur_Version.672.180.41.XT910.Retail.en.EU
ro.mot.hidden_keyboards=evfwd
ro.mot.build.version.sdk_int=6
ro.factorytest=0
ro.usb_mode=normal
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mapphone_cdma
ro.revision=0
init.svc.recovery=running
persist.qe=qe 2/1
Entered auto suspedn function
Parsing the directoryd_name: .
Parsing the directoryd_name: ..
Parsing the directoryd_name: usb1
Driverlink: /sys/bus/usb/devices/usb1
Link: ../../../devices/platform/omap/usbhs_omap/ehci-omap.0/usb1
Found /sys/bus/usb/devices/../../../devices/platform/omap/usbhs_omap/ehci-omap.0/usb1/power/control
Parsing the directoryd_name: 1-0:1.0
Parsing the directoryd_name: usb2
Driverlink: /sys/bus/usb/devices/usb2
Link: ../../../devices/platform/omap/usbhs_omap/ohci-omap3.0/usb2
Found /sys/bus/usb/devices/../../../devices/platform/omap/usbhs_omap/ohci-omap3.0/usb2/power/control
Parsing the directoryd_name: 2-0:1.0
Parsing the directoryd_name: usb3
Driverlink: /sys/bus/usb/devices/usb3
Link: ../../../devices/platform/omap/musb-omap2430/musb-hdrc/usb3
Found /sys/bus/usb/devices/../../../devices/platform/omap/musb-omap2430/musb-hdrc/usb3/power/control
Parsing the directoryd_name: 3-0:1.0
Parsing the directoryd_name: 2-1
Parsing the directoryd_name: 2-1:1.0
Finding update package...
I:Update location: /cache/Blur_Version.672.180.41.XT910.Retail.en.EU.zip
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1461 bytes; signature 1438 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Installing configureflex....
installing motoflash extensions
installing NV updater extensions
installing omapdevtype updater extension
is_dir_empty(/system/multiconfig/ap)=0In get_config for file [/system/multiconfig/config-id]
Value read from pds is 7116
In get_config for file [/system/multiconfig/master-config-id]
Value read from pds is 7116
From config id 7116 .... To config id 7116
Nothing to do .. return success
Verifying current system...
file "/system/bin/logwrapper" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
script aborted: assert failed: apply_patch_check("/system/bin/logwrapper", "23d23abf573e78e4bfe692fedf631ad1faa3179e", "4a63fec78956def045b442910a754fa640db8f5a")
assert failed: apply_patch_check("/system/bin/logwrapper", "23d23abf573e78e4bfe692fedf631ad1faa3179e", "4a63fec78956def045b442910a754fa640db8f5a")
E:Error in /cache/Blur_Version.672.180.41.XT910.Retail.en.EU.zip
(Status 7)
restoring configuration START..
In get_config for file [/system/multiconfig/config-id]
Value read from pds is 7116
In get_config for file [/system/multiconfig/master-config-id]
Value read from pds is 7116
From config id 7116 .... To config id 7116
Nothing to do .. return success
restoring configuration END..
Installation aborted.Looking at /system/bin/ there is a /system/bin/logwrapper.bak along with the logwrapper file. The modification date on both files is from before I got the phone.
If logwrapper has an incorrect sha1sum, I presume that means it's been corrupted or changed and that's what's interrupting the update? I also presume that logwrapper.bak is a backup of the original logwrapper file (pre-corruption).
- If I rename logwrapper to logwrapper.broken and rename logwrapper.bak to logwrapper, might this fix the problem? Might this cause more problems?
- Alternately, is there somewhere I can get a clean version of logwrapper to replace my corrupted version?
- If logwrapper is corrupted, does this mean that umpteen other things are likely to be corrupted as well?
I'm loathe to do a factory reset if I can avoid it and would rather fix it this way if possible.
I have Voodoo OTA RootKeeper so I don't lose root in the process of updating.
Finally, I have copied the OTA update file so I don't have to re-download it for the twentieth time, if I whack it and the crc file back in /cache/recovery will that shortcut me have to re-re-re-download, or can I only manually update by factory resetting?
Any help would be massively, massively appreciated. I had a search of the forums and didn't find anything.
Thanks,
Tim
