Database Info

[Q] Can't Update Moto Xoom Verizon 3g from 3.1 to 3.2

I have had the xoom Verizon 3g for the last 3 months and rooted + unlocked long ago - applied 3.1 with no problem; now that i received from Xoom to update to 3.2 (Verizon pushed it OFC), every time i click update it restarts and ur usual Android with Exclamation Mark is there. and when i try to update MANUALLY i get this (Basically check the LAST part in BOLD)
Starting recovery on Fri Aug 12 22:17:12 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
ClockworkMod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
2 /system ext4 /dev/block/mmcblk1p8 (null)
3 /cache ext4 /dev/block/mmcblk1p9 (null)
4 /data ext4 /dev/block/mmcblk1p10 (null)
5 /misc emmc /dev/block/mmcblk1p3 (null)
6 /boot emmc /dev/block/mmcblk1p7 (null)
7 /recovery emmc /dev/block/mmcblk1p6 (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.version.incremental=eng.chris.20110610.115222
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Fri Jun 10 11:52:40 NZST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=chris
ro.build.host=upsilon
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_stingray
ro.product.device=stingray
ro.product.board=stingray
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=stingray
ro.build.description=full_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.fingerprint=Android/full_stingray/stingray:2.3.4/GINGERBREAD/eng.chris.20110610.115222:eng/test-keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=02885045434042d7
ro.bootmode=unknown
ro.baseband=N_02.0F.00R
ro.carrier=unknown
ro.bootloader=1045
ro.hardware=stingray
ro.revision=33536
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Install from sdcard...
Finding update package...
I:Update location: /sdcard/update.zip
W:failed to mount /dev/block/mmcblk0p1 (No such file or directory)
Opening update package...
Installing update...
installing moto updater extensions
script aborted:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.

TheKicKer69 said:
I have had the xoom Verizon 3g for the last 3 months and rooted + unlocked long ago - applied 3.1 with no problem; now that i received from Xoom to update to 3.2 (Verizon pushed it OFC), every time i click update it restarts and ur usual Android with Exclamation Mark is there. and when i try to update MANUALLY i get this (Basically check the LAST part in BOLD)
Starting recovery on Fri Aug 12 22:17:12 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
ClockworkMod Recovery v3.2.0.0 (solarnz-R4c-100611-1150)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
2 /system ext4 /dev/block/mmcblk1p8 (null)
3 /cache ext4 /dev/block/mmcblk1p9 (null)
4 /data ext4 /dev/block/mmcblk1p10 (null)
5 /misc emmc /dev/block/mmcblk1p3 (null)
6 /boot emmc /dev/block/mmcblk1p7 (null)
7 /recovery emmc /dev/block/mmcblk1p6 (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GINGERBREAD
ro.build.display.id=full_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.version.incremental=eng.chris.20110610.115222
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.4
ro.build.date=Fri Jun 10 11:52:40 NZST 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=chris
ro.build.host=upsilon
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_stingray
ro.product.device=stingray
ro.product.board=stingray
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=stingray
ro.build.description=full_stingray-eng 2.3.4 GINGERBREAD eng.chris.20110610.115222 test-keys
ro.build.fingerprint=Android/full_stingray/stingray:2.3.4/GINGERBREAD/eng.chris.20110610.115222:eng/test-keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=02885045434042d7
ro.bootmode=unknown
ro.baseband=N_02.0F.00R
ro.carrier=unknown
ro.bootloader=1045
ro.hardware=stingray
ro.revision=33536
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Install from sdcard...
Finding update package...
I:Update location: /sdcard/update.zip
W:failed to mount /dev/block/mmcblk0p1 (No such file or directory)
Opening update package...
Installing update...
installing moto updater extensions
script aborted:
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.1/HMJ37/124251:user/release-keys" || file_getprop("/system/build.prop", "ro.build.fingerprint") == "verizon/trygon/stingray:3.2/HTJ85B/140714:user/release-keys"
E:Error in /sdcard/update.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
If you are rooted you can't update OTA.There is an update thread in Development to update rooted 3.1 to 3.2 rooted stock. I think its by stachre. Or you could just flash the Hammerhead Rom and get the update to 3.2, preserve your root and enjoy the new Rom-works with 3G too.

Thanks for the response
I have a similar challenge
Verizon 3g Motorola Xoom
Android version 3.0.1
Kernel version 2.6.36.3Tiamat_Xoom-v1.3.0-g5019ece-dirty [email protected]_PC #3
Build number HR166
Device has been re-configured for another 3g network and is working well, except that I am unable to upgrade. I like to get my tablet to version 3.2 and later to 4.0.3 and without losing data
Will “flash the Hammerhead Rom and get the update to 3.2” option work for me? If yes, please help with instructions and required software links

Tf700 blocked in 4.4.20

Hi guys,
i'm french, so sorry for my english!
I will try to explain what big problem i have with my tf700,
I was root with Bootloader LOCKED, and when i received last OTA update (4.4.23) I had a droid green belly open with an exclamation point above!
This is what i've got with the last_log:
Starting recovery on Mon Dec 10 19:22:26 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /misc emmc /dev/block/mmcblk0p3 (null) 0
4 /boot emmc boot (null) 0
5 /recovery emmc recovery (null) 0
6 /staging emmc /dev/block/mmcblk0p4 (null) 0
7 /btmac vfat /dev/block/mmcblk0p5 (null) 0
8 /data ext4 /dev/block/mmcblk0p8 (null) -32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
10 /cra emmc /dev/block/mmcblk0p7 (null) 0
I:Got arguments from /cache/recovery/command
Command: "/sbin/recovery" "--update_package=/cache/dlpkgfile"
ro.boot.serialno=015d2a508a4c280b
ro.boot.commchip_id=0
ro.boot.productid=0x04
ro.boot.carrier=wifi-only
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp,adb
ro.build.id=JRO03C
ro.build.display.id=JRO03C.WW_epad-10.4.4.20-20121026
ro.build.version.incremental=WW_epad-10.4.4.20-20121026
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Oct 26 17:49:57 CST 2012
ro.build.date.utc=1351244997
ro.build.type=user
ro.build.user=android
ro.build.host=Makemake
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=EeePad
ro.build.description=WW_epad-user 4.1.1 JRO03C WW_epad-10.4.4.20-20121026 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.4.20-20121026:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
windowsmgr.max_events_per_sec=200
webkit.canvas.ganesh=disable
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.version.driver=V7.0.62
gps.version.driver=V7.9.11
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.kernel.qemu=
ro.sf.lcd_density=160
bt.version.driver=V10.33
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.1_r2
ro.com.google.clientidbase=android-asus
ro.com.google.mcc_fallback=262
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
init.svc.ueventd=running
ro.serialno=C7OKAS091097
ro.boot_reason=rebooting
ro.epad.model_id=04
ro.epad.model=TF700T
persist.sys.NV_DISPXRES=1920
persist.sys.NV_DISPYRES=1200
persist.sys.NV_STEREOCTRL=0
persist.tegra.NV_FPSLIMIT=0
persist.sys.NV_FPSLIMIT=0
persist.sys.NV_POWERMODE=1
persist.sys.profiler_ms=0
persist.sys.NV_STEREOSEP=20
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_PROFVER=16
persist.sys.fw.camera.status=1
persist.sys.language=fr
persist.sys.country=FR
persist.sys.localevar=
persist.sys.Nvidia.didim=0
persist.sys.timezone=Europe/Brussels
persist.sys.NV_STEREOAPP=0
init.svc.recovery=running
init.svc.adbd=running
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Check : blob size = 13573093
Verifying current system...
file "/system/app/Browser.apk" 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/app/Browser.apk", "7c1edf8f1c8ab01fa91d6759b5c57e735b67e994", "918666bebf19c0a37ceb1e6de7a24e5ab01afcd4")
assert failed: apply_patch_check("/system/app/Browser.apk", "7c1edf8f1c8ab01fa91d6759b5c57e735b67e994", "918666bebf19c0a37ceb1e6de7a24e5ab01afcd4")
E:Error in /cache/dlpkgfile
(Status 7)
Installation aborted.
I:result_code: 410
Check and format /storage to vfat if needed...
Done.
and next i would try to downgrade in ICS maj and again I had a droid green belly open with an exclamation point above!
I am helpless!
Just give me some help please! :/

BinaryLover said:
script aborted: assert failed: apply_patch_check("/system/app/Browser.apk", "7c1edf8f1c8ab01fa91d6759b5c57e735b67e994", "918666bebf19c0a37ceb1e6de7a24e5ab01afcd4")
Click to expand...
Click to collapse
Did you somehow modify your Browser.apk?

_that said:
Did you somehow modify your Browser.apk?
Click to expand...
Click to collapse
no i did not modify my browser.apk
if i instal a new original apk of browser.apk do you think this will affect my problem?

BinaryLover said:
no i did not modify my browser.apk
if i instal a new original apk of browser.apk do you think this will affect my problem?
Click to expand...
Click to collapse
Yes, if you restore the original Browser.apk from 10.4.4.20 you will definitely either get a different error message for another file (you already know what to do then), or the update will go through.

_that said:
Yes, if you restore the original Browser.apk from 10.4.4.20 you will definitely either get a different error message for another file (you already know what to do then), or the update will go through.
Click to expand...
Click to collapse
ok, thank you , but where can i find the original Browser.apk from 10.4.4.20 ?
If you have this, can you upload this? :/

BinaryLover said:
ok, thank you , but where can i find the original Browser.apk from 10.4.4.20 ?
If you have this, can you upload this? :/
Click to expand...
Click to collapse
If you have some Linux knowledge, you can do the following:
- download the full 10.4.4.20 firmware from the firmware thread
- unzip twice
- get blobtools from https://github.com/AndroidRoot/BlobTools and compile
- run blobunpack on the blob
- mount -o loop blob.APP /mnt/some/dir
- copy whatever you need from the mounted directory.
If you only need Browser.apk, download this and unzip:
View attachment Browser.zip

Thank you so much but i need to install this apk or replace this in folder?
I try to install and i can't replace application system! And if i try to copy in folder "/system/app/Browser.apk" i can't replace apk.
How can i do this? :/

BinaryLover said:
Thank you so much but i need to install this apk or replace this in folder?
I try to install and i can't replace application system! And if i try to copy in folder "/system/app/Browser.apk" i can't replace apk.
How can i do this? :/
Click to expand...
Click to collapse
You cannot install this apk (it's a system app and also missing the odex file), you need to replace the existing file. To do that, become root and remount the system partition writable - either with your preferred root file manager, or with the command "mount -o remount,rw /system".

Thnak you i success to remplace apk
and now when i try to downgrade, bug... with droid again
last_log:
Starting recovery on Fri Dec 28 18:42:59 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /misc emmc /dev/block/mmcblk0p3 (null) 0
4 /boot emmc boot (null) 0
5 /recovery emmc recovery (null) 0
6 /staging emmc /dev/block/mmcblk0p4 (null) 0
7 /btmac vfat /dev/block/mmcblk0p5 (null) 0
8 /data ext4 /dev/block/mmcblk0p8 (null) -32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
10 /cra emmc /dev/block/mmcblk0p7 (null) 0
I:Boot command: launcher-boot-recovery
I:Got arguments from boot message
Command: "recovery" "--update_zip=/sdcard/ASUS_BUNDLE.zip"
ro.boot.serialno=015d2a508a4c280b
ro.boot.commchip_id=0
ro.boot.productid=0x04
ro.boot.carrier=wifi-only
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=JRO03C
ro.build.display.id=JRO03C.WW_epad-10.4.4.20-20121026
ro.build.version.incremental=WW_epad-10.4.4.20-20121026
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Oct 26 17:49:57 CST 2012
ro.build.date.utc=1351244997
ro.build.type=user
ro.build.user=android
ro.build.host=Makemake
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=EeePad
ro.build.description=WW_epad-user 4.1.1 JRO03C WW_epad-10.4.4.20-20121026 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.4.20-20121026:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
windowsmgr.max_events_per_sec=200
webkit.canvas.ganesh=disable
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.version.driver=V7.0.62
gps.version.driver=V7.9.11
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.kernel.qemu=
ro.sf.lcd_density=160
bt.version.driver=V10.33
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.1_r2
ro.com.google.clientidbase=android-asus
ro.com.google.mcc_fallback=262
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
init.svc.ueventd=running
ro.serialno=C7OKAS091097
ro.boot_reason=rebooting
ro.epad.model_id=04
ro.epad.model=TF700T
persist.sys.NV_STEREOCTRL=0
persist.sys.NV_DISPXRES=1920
persist.sys.NV_DISPYRES=1200
persist.tegra.NV_FPSLIMIT=0
persist.sys.NV_FPSLIMIT=0
persist.sys.NV_POWERMODE=1
persist.sys.profiler_ms=0
persist.sys.NV_STEREOSEP=20
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_PROFVER=16
persist.sys.language=fr
persist.sys.country=FR
persist.sys.localevar=
init.svc.recovery=running
init.svc.adbd=running
I:Enable RSA key verification.
Finding update package...
I:Update location: /sdcard/ASUS_BUNDLE.zip
Opening update package...
E:Can't open /sdcard/ASUS_BUNDLE.zip
(No such file or directory)
Installation aborted.
I:result_code: 80000002
Check and format /storage to vfat if needed...
Done.

BinaryLover said:
and now when i try to downgrade, bug... with droid again
Click to expand...
Click to collapse
I thought you wanted to upgrade, not downgrade? The Browser.apk was intended to enable upgrading to 10.4.4.23 using the dlgpkgfile that should still be in your /cache directory.
BinaryLover said:
I:Got arguments from boot message
Command: "recovery" "--update_zip=/sdcard/ASUS_BUNDLE.zip"
Click to expand...
Click to collapse
Looks like the recovery is looking for this file and doesn't find it. How did you start the recovery, and what are you actually trying to do?

_that said:
I thought you wanted to upgrade, not downgrade? The Browser.apk was intended to enable upgrading to 10.4.4.23 using the dlgpkgfile that should still be in your /cache directory.
Looks like the recovery is looking for this file and doesn't find it. How did you start the recovery, and what are you actually trying to do?
Click to expand...
Click to collapse
i want to be in 10.4.4.23 root.
ok now i tryed to upgrade with dlpkgfile to 4.4.23 and.. droid belly open with an exclamation point above!
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Installing update...
Check : blob size = 13573093
Verifying current system...
file "/system/lib/libwebrtc_audio_preprocessing.so" 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/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
assert failed: apply_patch_check("/system/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
E:Error in /cache/dlpkgfile
(Status 7)
Installation aborted.
I:result_code: 410
Check and format /storage to vfat if needed...
Done.
Yes it's not the Browser.apk who make bug! we move forward!!

BinaryLover said:
script aborted: assert failed: apply_patch_check("/system/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
assert failed: apply_patch_check("/system/lib/libwebrtc_audio_preprocessing.so", "7bf0da762f93aa61f616c4b9476453f74e513a51", "61ca4883a6ea5bbce87601ab11769f8b7cb5dd7c")
Click to expand...
Click to collapse
OK. You know the drill ... replace your file with the one in the attached zip: View attachment libwebrtc_audio_preprocessing.zip
This is the 5th last file that is checked by the dlpkgfile, so in the worst case we must do it with 4 more files.

_that said:
OK. You know the drill ... replace your file with the one in the attached zip: View attachment 1598826
This is the 5th last file that is checked by the dlpkgfile, so in the worst case we must do it with 4 more files.
Click to expand...
Click to collapse
Ho God you are the best!!!
It's work!!! I'm in 4.4.23!! Thank you very much!!
I ask myself the question why were corrupted apk!But now it's work!!!
Bravo tu m'as bien aidé pour mon problème!, je te remercie!

installing rom without uninstalling anti-theft program

Let me start telling that i forgot to uninstall an anti theft program before flashing` cm-10.1-20121228-UNOFFICIAL-gio.zip`.on my SAMSUNG GALAXY GIO GT-S5660
So i had my phone rooted with a program from the android marked,
II had installed ` signed_cwm-5.0.2.7-flashablezip-ext4+rfs.zip` .
I had installed rom manager from android marked as in xda- guide .
installing went ok,but after manualy rebooting the phone it stayed with a blue circling logo on the screen...
has that anything to do with the uninstalled anti theft program?
thanks for some advice.

devrieshh said:
Let me start telling that i forgot to uninstall an anti theft program before flashing` cm-10.1-20121228-UNOFFICIAL-gio.zip`.on my SAMSUNG GALAXY GIO GT-S5660
So i had my phone rooted with a program from the android marked,
II had installed ` signed_cwm-5.0.2.7-flashablezip-ext4+rfs.zip` .
I had installed rom manager from android marked as in xda- guide .
installing went ok,but after manualy rebooting the phone it stayed with a blue circling logo on the screen...
has that anything to do with the uninstalled anti theft program?
thanks for some advice.
Click to expand...
Click to collapse
Did you do a factory reset in recovery before flashing your ROM?
Sent from my SGH-I317 using xda premium

devoureddreams said:
Did you do a factory reset in recovery before flashing your ROM?
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
No,i dont think so

That's y go into recovery and factory reset also wipe cache and dalvik cache and reflash your ROM it'll boot fine after that.
Sent from my SGH-I317 using xda premium

devoureddreams said:
That's y go into recovery and factory reset also wipe cache and dalvik cache and reflash your ROM it'll boot fine after that.
Sent from my SGH-I317 using xda premium
Click to expand...
Click to collapse
Whell yesterday i brought my phone away,when i get my phone bag at the end of the week i try it.
thanks for the help

Whell today i tryed it,first removed sdcard(otherwise rom also formatted) than factory reset,wipe dalvik cache,wipe battery stats,wipe cache partition,than put sdcard in,installed zip from sdcard,put sdcard out,factory reset,sdcard in, reboot...
and again the blue circling cyanogenMod circle...
Than i tryed to restore my backedup system from recovery mode but i got an error saying` E:format_volume: format_rfs_device failed on /dev/block/st112 Error while formatting /system!
Has this anything to do with that installed anty theft program?how to handle when that is the case.
What did i do wrong?
thanks for some advice
(i put recovery log in Quick Reply.)

Starting recovery on Tue Nov 27 03:54:50 2012
framebuffer: fd 4 (320 x 480)
CWM-based Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot bml boot (null)
2 /recovery bml recovery (null)
3 /cache rfs /dev/block/stl14 (null)
4 /data rfs /dev/block/stl13 (null)
5 /system rfs /dev/block/stl12 (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /sd-ext ext2 /dev/block/mmcblk0p2 (null)
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRWK74
ro.build.display.id=GWK74
ro.build.version.incremental=eng.dhiika.20120101.003357
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Sun Jan 1 00:34:23 WIT 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=dhiika
ro.build.host=
ro.build.tags=test-keys
ro.product.model=GT-S5660
ro.product.brand=samsung
ro.product.name=gio
ro.product.device=gio
ro.product.board=gio
ro.product.cpu.abi=armeabi-v6l
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=gio
ro.build.description=GT-S5660-user 2.3.5 GINGERBREAD XXKS2 test-keys
ro.build.fingerprint=samsung/GT-S5660/GT-S5660:2.3.5/GINGERBREAD/XXKS2:user/test-keys
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
ro.sf.lcd_density=160
keyguard.no_require_sim=true
ro.com.android.dateformat=dd-MM-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.media.dec.jpeg.memcap=10000000
mobiledata.interfaces=pdp0,wlan0,gprs,ppp0
ro.telephony.ril_class=samsung
wifi.interface=wlan0
wifi.supplicant_scan_interval=60
ro.com.android.dataroaming=false
qemu.sf.lcd_density=160
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.setupwizard.enable_bypass=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit
dalvik.vm.dexopt-data-only=1
ro.opengles.version=131072
ro.compcache.default=0
ro.rommanager.developerid=cyanogenmod
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.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.2.0-RC0-gio-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=gt-s5660
ro.revision=10
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Checking MD5 sums...
boot.img: OK
cache.rfs.tar: OK
data.rfs.tar: OK
recovery.img: OK
system.rfs.tar: OK
.android_secure.vfat.tar: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2012-12-28-20.01.13//system.rfs.tar
Restoring system...
10+0 records in
10+0 records out
40960 bytes (40.0KB) copied, 0.028768 seconds, 1.4MB/s
sh: /sbin/fat.format: not found
failure while running fat.format
E:format_volume: format_rfs_device failed on /dev/block/stl12
Error while formatting /system!
Checking MD5 sums...
boot.img: OK
cache.rfs.tar: OK
data.rfs.tar: OK
recovery.img: OK
system.rfs.tar: OK
.android_secure.vfat.tar: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2012-12-28-20.01.13//system.rfs.tar
Restoring system...
10+0 records in
10+0 records out
40960 bytes (40.0KB) copied, 0.028418 seconds, 1.4MB/s
sh: /sbin/fat.format: not found
failure while running fat.format
E:format_volume: format_rfs_device failed on /dev/block/stl12
Error while formatting /system!
Is there an other way to format the phone?

Also after installing [4.2.1] CyanogenMod 10.1 [STABLE][15.01.13 same problem
devrieshh said:
Starting recovery on Tue Nov 27 03:54:50 2012
Still the same problem,booting up doesnt come forther than blue CyanogenMod circle...
steps; 1 factory reset
2 installing rom 10.1
3 factory reset
4 reboot...
Is this of the maybe not errased anty theft softwere?
(see the log beneath)
please some advice
framebuffer: fd 4 (320 x 480)
CWM-based Recovery v5.0.2.7
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot bml boot (null)
2 /recovery bml recovery (null)
3 /cache rfs /dev/block/stl14 (null)
4 /data rfs /dev/block/stl13 (null)
5 /system rfs /dev/block/stl12 (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /sd-ext ext2 /dev/block/mmcblk0p2 (null)
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRWK74
ro.build.display.id=GWK74
ro.build.version.incremental=eng.dhiika.20120101.003357
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Sun Jan 1 00:34:23 WIT 2012
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=dhiika
ro.build.host=
ro.build.tags=test-keys
ro.product.model=GT-S5660
ro.product.brand=samsung
ro.product.name=gio
ro.product.device=gio
ro.product.board=gio
ro.product.cpu.abi=armeabi-v6l
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=gio
ro.build.description=GT-S5660-user 2.3.5 GINGERBREAD XXKS2 test-keys
ro.build.fingerprint=samsung/GT-S5660/GT-S5660:2.3.5/GINGERBREAD/XXKS2:user/test-keys
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
ro.sf.lcd_density=160
keyguard.no_require_sim=true
ro.com.android.dateformat=dd-MM-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.media.dec.jpeg.memcap=10000000
mobiledata.interfaces=pdp0,wlan0,gprs,ppp0
ro.telephony.ril_class=samsung
wifi.interface=wlan0
wifi.supplicant_scan_interval=60
ro.com.android.dataroaming=false
qemu.sf.lcd_density=160
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.setupwizard.enable_bypass=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit
dalvik.vm.dexopt-data-only=1
ro.opengles.version=131072
ro.compcache.default=0
ro.rommanager.developerid=cyanogenmod
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.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.2.0-RC0-gio-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=gt-s5660
ro.revision=10
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Checking MD5 sums...
boot.img: OK
cache.rfs.tar: OK
data.rfs.tar: OK
recovery.img: OK
system.rfs.tar: OK
.android_secure.vfat.tar: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2012-12-28-20.01.13//system.rfs.tar
Restoring system...
10+0 records in
10+0 records out
40960 bytes (40.0KB) copied, 0.028768 seconds, 1.4MB/s
sh: /sbin/fat.format: not found
failure while running fat.format
E:format_volume: format_rfs_device failed on /dev/block/stl12
Error while formatting /system!
Checking MD5 sums...
boot.img: OK
cache.rfs.tar: OK
data.rfs.tar: OK
recovery.img: OK
system.rfs.tar: OK
.android_secure.vfat.tar: OK
couldn't find default
Found new backup image: /sdcard/clockworkmod/backup/2012-12-28-20.01.13//system.rfs.tar
Restoring system...
10+0 records in
10+0 records out
40960 bytes (40.0KB) copied, 0.028418 seconds, 1.4MB/s
sh: /sbin/fat.format: not found
failure while running fat.format
E:format_volume: format_rfs_device failed on /dev/block/stl12
Error while formatting /system!
Thanks for some advise
Click to expand...
Click to collapse

devrieshh said:
Whell yesterday i brought my phone away,when i get my phone bag at the end of the week i try it.
thanks for the help
Click to expand...
Click to collapse
whell i fixed it ,1 factory reset
2 ( download and put on sdcard) ext4formatter.zip
3flash ext4formatter.zip
4flash rom
5reboot
when things are wrong do factory reset and than reboot (again)

You have tot format to ext4 that is why you flash ext4-format.zip.after that you
can flash any rom without problems.
-factoryreset
-flash ext4-format.zip
-flash Rom
-factoryreset
-reboot
Sent from my GT-S5660 using xda app-developers app

[Q] (OTA failed) automatic update can it be fixed??

Hi there everyone
Yes, unfortunately , as it is said in the movie when I was registering, a NOOB here. I was looking for a solution all over there forum and still nothing, it may be also some skills lack in installing or flashing etc.
But as in topic. Can it be fixed?
Today I received a message about new firmware update to Jelly Bean 4.2. I was over the moon when I saw it!!
When everything downloaded and I taped to start the update. TF turned off, started , the green android showed up with tha blue ball and the he fell with red triangle... [email protected]/#!!!
So i restarted it and now the message doesn't show up.
Here is what i tried:
- forcing to shut down and clearing data of DMClinet , CMClient, Google service framework - result nothing
- Multiple hard resets - result nothing
- downgrade to ICS - result nothing
- updating to JB 4.1.1 from ICS with dlpkgfile - result nothing
As far as I know there is one option that worked for me and it is sending to ASUS - result they made it and when I got my TF back Automatic updates were back ( I didn't send it just because of updates . there was problem with a mobile dock )
I don't want to do manual updates all the time, because as far as I know there are much more automatic updates and it is much simpler and quicker than flashing everything again and again.
Some more info about my TF700:
Rom: 4.1.1.
Rooted on ICS and kept the root even with manual flashing.
This may be helpful i use Pimp my rom, Seeder and automatic task killer
So people please:
Short answers do I have to sand it back to Asus again so they can fix it or anyone can show me the way step by step to repair this and get back automatic updates?
Thanks

benihussan said:
Hi there everyone
Yes, unfortunately , as it is said in the movie when I was registering, a NOOB here. I was looking for a solution all over there forum and still nothing, it may be also some skills lack in installing or flashing etc.
But as in topic. Can it be fixed?
Today I received a message about new firmware update to Jelly Bean 4.2. I was over the moon when I saw it!!
When everything downloaded and I taped to start the update. TF turned off, started , the green android showed up with tha blue ball and the he fell with red triangle... [email protected]/#!!!
So i restarted it and now the message doesn't show up.
Here is what i tried:
- forcing to shut down and clearing data of DMClinet , CMClient, Google service framework - result nothing
- Multiple hard resets - result nothing
- downgrade to ICS - result nothing
- updating to JB 4.1.1 from ICS with dlpkgfile - result nothing
As far as I know there is one option that worked for me and it is sending to ASUS - result they made it and when I got my TF back Automatic updates were back ( I didn't send it just because of updates . there was problem with a mobile dock )
I don't want to do manual updates all the time, because as far as I know there are much more automatic updates and it is much simpler and quicker than flashing everything again and again.
Some more info about my TF700:
Rom: 4.1.1.
Rooted on ICS and kept the root even with manual flashing.
This may be helpful i use Pimp my rom, Seeder and automatic task killer
So people please:
Short answers do I have to sand it back to Asus again so they can fix it or anyone can show me the way step by step to repair this and get back automatic updates?
Thanks
Click to expand...
Click to collapse
Can you check the "last_install" file located in /cache/recovery? is there anything in that file or empty? also the "last_log", please post the files here.

So as I tried to repair it by downgrading few minutes ago now I'm on ICS
last _install :
/sdcard/EP201_768_SDUPDATE.zip
1
and Last_log :
Starting recovery on Thu Apr 4 19:55:49 2013
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /misc emmc /dev/block/mmcblk0p3 (null) 0
4 /boot emmc boot (null) 0
5 /recovery emmc recovery (null) 0
6 /staging emmc /dev/block/mmcblk0p4 (null) 0
7 /btmac vfat /dev/block/mmcblk0p5 (null) 0
8 /data ext4 /dev/block/mmcblk0p8 (null) -32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
10 /cra emmc /dev/block/mmcblk0p7 (null) 0
Command: "/sbin/recovery"
ro.boot.serialno=015d2ea06d400607
ro.boot.commchip_id=0
ro.boot.productid=0x04
ro.boot.carrier=wifi-only
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp
ro.build.id=JRO03C
ro.build.display.id=JRO03C.WW_epad-10.4.4.25-20121228
ro.build.version.incremental=WW_epad-10.4.4.25-20121228
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.1
ro.build.date=Fri Dec 28 18:53:10 CST 2012
ro.build.date.utc=1356691990
ro.build.type=user
ro.build.user=android
ro.build.host=Uranus
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=EeePad
ro.build.description=WW_epad-user 4.1.1 JRO03C WW_epad-10.4.4.25-20121228 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.1.1/JRO03C/WW_epad-10.4.4.25-20121228:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
ro.sf.override_null_lcd_density=1
keyguard.no_require_sim=true
windowsmgr.max_events_per_sec=200
webkit.canvas.ganesh=disable
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.carrier=wifi-only
ro.config.alarm_alert=Alarm_Classic.ogg
wifi.version.driver=V7.0.65
gps.version.driver=V7.9.11
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.kernel.qemu=
ro.sf.lcd_density=160
bt.version.driver=V10.33
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.1_r2
ro.com.google.clientidbase=android-asus-rev
ro.com.google.clientidbase.ms=android-asus-rev
ro.com.google.clientidbase.am=android-asus-rev
ro.com.google.clientidbase.gmm=android-asus-rev
ro.com.google.clientidbase.yt=android-asus-rev
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.dns2
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
init.svc.ueventd=running
ro.serialno=C8OKASO29554
ro.boot_reason=normal
ro.epad.model_id=04
ro.epad.model=TF700T
wifi.supplicant_scan_interval=98
persist.wifi_scan_interval=98
ro.mot.eri.losalert.delay=900
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
net.dns1=8.8.8.8
net.dns2=8.8.4.4
ro.FOREGROUND_APP_MEM=6400
ro.VISIBLE_APP_MEM=8960
ro.SECONDARY_SERVER_MEM=19200
ro.BACKUP_APP_MEM=23040
ro.HOME_APP_MEM=3200
ro.HIDDEN_APP_MEM=23040
ro.EMPTY_APP_MEM=64000
ro.PERCEPTIBLE_APP_MEM=3200
ro.HEAVY_WEIGHT_APP_MEM=19200
ro.CONTENT_PROVIDER_MEM=38400
ro.FOREGROUND_APP_ADJ=25
ro.VISIBLE_APP_ADJ=35
ro.SECONDARY_SERVER_ADJ=75
ro.BACKUP_APP_ADJ=76
ro.HOME_APP_ADJ=26
ro.EMPTY_APP_ADJ=89
ro.HIDDEN_APP_MIN_ADJ=250
ro.PERCEPTIBLE_APP_ADJ=27
ro.HEAVY_WEIGHT_APP_ADJ=36
ro.CONTENT_PROVIDER_ADJ=90
ENFORCE_PROCESS_LIMIT=false
MAX_SERVICE_INACTIVITY=false
MIN_HIDDEN_APPS=false
MAX_HIDDEN_APPS=false
CONTENT_APP_IDLE_OFFSET=false
EMPTY_APP_IDLE_OFFSET=false
MAX_ACTIVITIES=false
ACTIVITY_INACTIVE_RESET_TIME=false
MAX_RECENT_TASKS=false
MIN_RECENT_TASKS=false
APP_SWITCH_DELAY_TIME=false
MAX_PROCESSES=false
PROC_START_TIMEOUT=false
CPU_MIN_CHECK_DURATION=false
GC_TIMEOUT=false
SERVICE_TIMEOUT=false
MIN_CRASH_INTERVAL=false
video.accelerate.hw=1
debug.sf.hw=0
debug.egl.profiler=0
debug.egl.hw=0
debug.composition.type=cpu
persist.sys.use_dithering=1
persist.sys.purgeable_assets=1
persist.sys.use_16bpp_alpha=1
ro.gsm.2nd_data_retries=null
ro.ril.enable.amr.wideband=0
ro.media.dec.jpeg.memcap=8000000
ro.media.enc.hprof.vid.bps=8000000
ro.media.capture.maxres=8m
ro.media.panorama.defres=3264x1840
ro.media.panorama.frameres=1280x720
ro.camcorder.videoModes=true
ro.media.enc.hprof.vid.fps=65
ro.media.enc.jpeg.quality=100
ro.media.capture.flash=led
ro.media.capture.flashMinV=3300000
ro.media.capture.torchIntensity=65
ro.media.capture.flashIntensity=70
ro.config.hw_quickpoweron=true
persist.sys.NV_STEREOCTRL=0
persist.sys.NV_DISPXRES=1920
persist.sys.NV_DISPYRES=1200
persist.tegra.NV_FPSLIMIT=0
persist.sys.NV_FPSLIMIT=0
persist.sys.NV_POWERMODE=1
persist.sys.profiler_ms=0
persist.sys.NV_STEREOSEP=20
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_PROFVER=16
persist.sys.language=pl
persist.sys.country=PL
persist.sys.localevar=
persist.sys.timezone=Europe/Brussels
init.svc.recovery=running
init.svc.adbd=running
Finding update package...
I:Update location: /sdcard/ASUS_BUNDLE.zip
W:failed to mount /dev/block/mmcblk1p1 (No such file or directory); trying /dev/block/mmcblk1
Opening update package...
E:Can't open /sdcard/ASUS_BUNDLE.zip
(No such file or directory)
I:No factory bundle package.
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /sdcard/EP201_768_SDUPDATE.zip
Opening update package...
I:1 key(s) loaded from /res/keys
I:comment is 1682 bytes; signature 1664 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
I:SKU token:WW_epad
Iroperty get:WW_epad
I:token f:n
I:ro.build.version.incremental:WW_epad-10.4.4.25-20121228
I:device version: 10.4.4.25
I:rule version: 9.4.5.30
I:i:2 token:4
I:i:3 token:4
I:i:4 token:25
I:rule i:2 token:4
I:rule i:3 token:5
I:rule i:4 token:30
I:dec_rule: 9 4 5 30 0
I:dec_version: 10 4 4 25 0
I:downgrade version.
I:check downgrade version pass
Installing update...
Check : blob size = 817556103
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /system ext4 /dev/block/mmcblk0p1 (null)
2 /cache ext4 /dev/block/mmcblk0p2 (null)
3 /misc emmc /dev/block/mmcblk0p3 (null)
4 /boot emmc boot (null)
5 /recovery emmc recovery (null)
6 /staging emmc /dev/block/mmcblk0p4 (null)
7 /btmac vfat /dev/block/mmcblk0p5 (null)
8 /data ext4 /dev/block/mmcblk0p8 length=-32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
10 /cra emmc /dev/block/mmcblk0p7 (null)
volume path for /staging:/dev/block/mmcblk0p4
wrote staging partition from staging
script result was []
Check and format /storage to vfat if needed...
Done.
Formatting /data...
Creating filesystem with parameters:
Size: 61415587840
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 14994040
Block groups: 458
Reserved block group size: 1024
Created filesystem with 11/3751936 inodes and 281560/14994040 blocks
Formatting /cache...
Creating filesystem with parameters:
Size: 448790528
Block size: 4096
Blocks per group: 32768
Inodes per group: 6848
Inode size: 256
Journal blocks: 1712
Label:
Blocks: 109568
Block groups: 4
Reserved block group size: 31
Created filesystem with 11/27392 inodes and 3534/109568 blocks
Here you are

As I need my Tf to work I'm back on JB 4.1.1 rooted . Flashed manually from asus website.
Ohh! I almost forgot.
there is also a useful thing to mention, when i make the combination of keys on start-up Power up and Vol down, and it gets to kernel or recovery( I'm not sure how it's called) I can;t do nothing or choose to wipe data etc. the only thing that work is Vol up in 5/10 seconds to flash an update.
I hope this is valuable. Maybe I just do something wrong.

Exactly same problem and attempted solutions here.

So as I can't wait too long i decided to send my TF700 to Asus service center so they can solve this problem.
Nevertheless I think this problem is worth solving, so everybody can do it on their own. So i really encourage everyone who got any ideas to get involved. The same problem was on Nexus 7 as i have read somewhere. And there is some solution with special program, maybe that will help a bit.
Please type in google : "Nexus 7 OTA fix", I can't post outside links so far.

benihussan said:
So as I can't wait too long i decided to send my TF700 to Asus service center so they can solve this problem.
Nevertheless I think this problem is worth solving, so everybody can do it on their own. So i really encourage everyone who got any ideas to get involved. The same problem was on Nexus 7 as i have read somewhere. And there is some solution with special program, maybe that will help a bit.
Please type in google : "Nexus 7 OTA fix", I can't post outside links so far.
Click to expand...
Click to collapse
I had the same problem with my tf700. Did you manage to find a solution or Asus fixed your problem?
Sent from my GT-I9300 using xda app-developers app

Yes, they fixed it somehow. I tried to ask them how to solve it by my own , but I didnt get any answer so the best solution is to have luck and dont have this problem or send it to Asus with some bigger problem also mentioing it.

benihussan said:
Yes, they fixed it somehow. I tried to ask them how to solve it by my own , but I didnt get any answer so the best solution is to have luck and dont have this problem or send it to Asus with some bigger problem also mentioing it.
Click to expand...
Click to collapse
I had my fixed last night via dlpkgfile. It turned out I'd previously had a wrong version of dlpkgfile.

[Q] How to fix My Devices Stuck At animation Boot Alcatel One Touch 4011x

Devices One Touch 4011x MT6575
Flashing CMW V5.5.0.4 and do nandroid backup for safety....im wrong edit some word in build.prop ,restart devices then got stuck at animations boots,im trying restore but still stuck at animations boots..btw the backup has work before..how to fix this problem in cmw?btw my devices still can go cwm..
PHP:
Starting recovery on Sun Jan 1 01:24:30 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 24.07.2013 04:48:02
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/misc (null) 0
2 /data ext4 /dev/block/mmcblk0p7 (null) 0
3 /system ext4 /dev/block/mmcblk0p5 (null) 0
4 /cache ext4 /dev/block/mmcblk0p6 (null) 0
5 /boot emmc /dev/bootimg (null) 0
6 /recovery emmc /dev/recovery (null) 0
7 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
8 /sd-ext auto /dev/block/mmcblk1p2 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=IMM76L
ro.build.display.id=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.version.incremental=eng.rua1.20130129.114933
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Вто Янв 29 11:51:46 MSK 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=rua1
ro.build.host=rua1-desktop
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_MTK
ro.product.device=MTK
ro.product.board=MTK
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=MTK
ro.build.description=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.fingerprint=Android/full_MTK/MTK:4.0.4/IMM76L/eng.rua1.20130129.114933:eng/test-keys
ro.build.characteristics=default
ro.cm.device=MTK
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6575
ro.revision=1710983680
ro.emmc=0
sys.usb.vid=0BB4
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...

hello someone please help

techpowering said:
hello someone please help
Click to expand...
Click to collapse
you can't go to cwm?

thank for replying...im really need help? my devices still can in cwm..did you know what cause problem about my devices? trying restore still stuck at boot animation...btw backup was working before.. please help

techpowering said:
thank for replying...im really need help? my devices still can in cwm..did you know what cause problem about my devices? trying restore still stuck at boot animation...btw backup was working before.. please help
Click to expand...
Click to collapse
1. Go to CWM
2. Do a Factory Reset
3. Clear cache and dalvik-cache
3. Restore your backup
3. Clear cache and dalvik-cache (again)
4. Reboot and wait. (may take some time to start)
If it still does not, you have to install adb shell on pc and replace the original file build.prop
I hope it was usefull
greetings

FSadino said:
1. Go to CWM
2. Do a Factory Reset
3. Clear cache and dalvik-cache
3. Restore your backup
3. Clear cache and dalvik-cache (again)
4. Reboot and wait. (may take some time to start)
If it still does not, you have to install adb shell on pc and replace the original file build.prop
I hope it was usefull
greetings
Click to expand...
Click to collapse
Thank for Reply i have a question can we replace the original file build.prop in update.zip?because my devices has damage usb port ( some small damage on board i/c ) so my devices cant be detected anymore at computer..it because im plug charger usb on car.. btw i was doing factory reset,clean cache,davlik,restore ,clean again now reboot and wait..i will update how it work...uuh i hope build.prop can replace with zip file

seems not work how to replace build.prop zip file?

i believe there is not much you can do without usb connection. you have to get your usb working again before you can fix the phone.
Sent from my ONE TOUCH 4011X using XDA Free mobile app

techpowering said:
seems not work how to replace build.prop zip file?
Click to expand...
Click to collapse
I agree with @HadpeH, without USB we can not do anything. First fix this problem then it will be easier to help you

im request the stock build.prop for devices One Touch 4011x ( alcatel )..my usb devices cannot repair because the small i/c board has broken

you can try to extract the file you need from the stock rom here - sourceforge(dot)net/projects/alcatel/files-
i think you can replace build.prop using updater script.
Sent from my ONE TOUCH 4011X using XDA Free mobile app

hey
HadpeH said:
you can try to extract the file you need from the stock rom here - sourceforge(dot)net/projects/alcatel/files-
i think you can replace build.prop using updater script.
Sent from my ONE TOUCH 4011X using XDA Free mobile app
Click to expand...
Click to collapse
if you have an sdcard remove it put in card reader connect card reader to pc, download aromafm to card and the build.prop
replacement put card back into device, boot into cwm, install aromafm.zip start file manager nav to proper build.prop and copy,
nav to /system and paste, long pres on newly pasted build prop and set perm to 644. reboot.
m

moonbutt74 said:
if you have an sdcard remove it put in card reader connect card reader to pc, download aromafm to card and the build.prop
replacement put card back into device, boot into cwm, install aromafm.zip start file manager nav to proper build.prop and copy,
nav to /system and paste, long pres on newly pasted build prop and set perm to 644. reboot.
m
Click to expand...
Click to collapse
Thank you i will try as soon...and will update how works

Bump! already replace with new build.prop using Aroma file manager...and set to rw-r--r-- still not work..stuck at animation boots..tried nandroid restore..and reboot still stuck on animations boots what the problem of this? can someone help read this log what cause problem on my devices
HTML:
Starting recovery on Sun Jan 1 01:00:47 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 24.07.2013 04:48:02
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/misc (null) 0
2 /data ext4 /dev/block/mmcblk0p7 (null) 0
3 /system ext4 /dev/block/mmcblk0p5 (null) 0
4 /cache ext4 /dev/block/mmcblk0p6 (null) 0
5 /boot emmc /dev/bootimg (null) 0
6 /recovery emmc /dev/recovery (null) 0
7 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
8 /sd-ext auto /dev/block/mmcblk1p2 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=IMM76L
ro.build.display.id=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.version.incremental=eng.rua1.20130129.114933
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Вто Янв 29 11:51:46 MSK 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=rua1
ro.build.host=rua1-desktop
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_MTK
ro.product.device=MTK
ro.product.board=MTK
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=MTK
ro.build.description=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.fingerprint=Android/full_MTK/MTK:4.0.4/IMM76L/eng.rua1.20130129.114933:eng/test-keys
ro.build.characteristics=default
ro.cm.device=MTK
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6575
ro.revision=1710983680
ro.emmc=0
sys.usb.vid=0BB4
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...

bump for help