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

[Q] HELP NEEDED galaxy s2 (i9100g),cannot mount emmc

when i try to install a rom with cwm,installation is aborted , and when i go to mount and storage menu,and try to mount emmc storage then it says :error cant mount emmc,the log file of error during flashing a rom was :
Starting recovery on Sat Apr 21 16:28:46 2012
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v5.0.2.3
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot emmc /dev/block/mmcblk0p5 (null)
2 /recovery emmc /dev/block/mmcblk0p6 (null)
3 /efs ext4 /dev/block/mmcblk0p1 (null)
4 /cache ext4 /dev/block/mmcblk0p7 (null)
5 /system ext4 /dev/block/mmcblk0p9 (null)
6 /data ext4 /dev/block/mmcblk0p10 (null)
7 /sdcard vfat /dev/block/mmcblk0p11 (null)
8 /emmc vfat /dev/block/mmcblk1p1 (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=0NAL_DEFAULT_PROPERTIES
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=cff1930417fc1ae
ro.bootmode=reboot_recovery
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=t1
ro.revision=7
ro.emmc=0
dpm.allowpolicy=1
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
ro.build.id=GINGERBREAD
ro.build.display.id=juffo.v2.DZKJ2
ro.build.version.incremental=DZKJ2
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.6
ro.build.date=Fri Oct 21 19:47:33 KST 2011
ro.build.date.utc=1319194053
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEI-30
ro.build.tags=release-keys
ro.product.model=GT-I9100G
ro.product.brand=samsung
ro.product.name=GT-I9100G
ro.product.device=GT-I9100G
ro.product.board=omap4sdp
ro.product.cpu.abi=armeabi-v7a
ro.build.PDA=I9100GDZKJ2
ro.build.hidden_ver=I9100GDZKJ2
ro.build.changelist=679669
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
ro.wifi.channels=
ro.board.platform=omap4
ro.build.product=GT-I9100G
ro.build.description=GT-I9100G-user 2.3.6 GINGERBREAD DZKJ2 release-keys
ro.build.fingerprint=samsung/GT-I9100G/GT-I9100G:2.3.6/GINGERBREAD/DZKJ2:user/release-keys
ro.tether.denied=false
ro.flash.resolution=1080
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=250
dalvik.vm.heapsize=64m
persist.service.usb.setting=0
com.ti.omap_enhancement=true
media.camerahal.test-esd1=false
media.camerahal.test-esd2=false
media.overlay.cloneStatic=false
media.overlay.cloneDynamic=false
persist.sys.HDMICableConnected=no
persist.sys.GfxRotation=0
opencore.asmd=1
wifi.interface=tiwlan0
debug.video.rotateoverlay=0
omap.audio.mic.main=AMic0
omap.audio.mic.sub=AMic1
omap.audio.power=PingPong
ro.com.google.locationfeatures=1
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=2.3_r7
media.stagefright.enable-player=false
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=false
media.stagefright.enable-rtsp=false
dev.sfbootcomplete=0
ro.com.google.clientidbase=android-samsung
keyguard.no_require_sim=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=01_Sherbet.ogg
ro.config.alarm_alert=Good_Morning.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.opengles.version=131072
ro.secdevenc=true
ro.wtldatapassword=true
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tv.hdmi.uicloning.enable=true
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
init.svc.pvrsrvinit=stopped
init.svc.geomagneticd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Wiping cache...
Formatting /cache...
Creating filesystem with parameters:
Size: 104857600
Block size: 4096
Blocks per group: 32768
Inodes per group: 6400
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 25600
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/6400 inodes and 1438/25600 blocks
Cache wipe complete.
E:unknown volume for path [/sd-ext]
rm: can't remove '/cache/dalvik-cache': No such file or directory
rm: can't remove '/sd-ext/dalvik-cache': No such file or directory
Dalvik Cache wiped.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
-- Installing: /emmc/LOST.DIR/SuperROM_v3.0.zip
Finding update package...
I:Update location: /emmc/LOST.DIR/SuperROM_v3.0.zip
Opening update package...
Installing update...
Installation aborted.
Script Asserts: Enabled
-- Installing: /emmc/LOST.DIR/SuperROM_v3.0.zip
Finding update package...
I:Update location: /emmc/LOST.DIR/SuperROM_v3.0.zip
Opening update package...
Installing update...
Installation aborted.
-- Installing: /sdcard/LOST.DIR/SuperROM_v3.0.zip
Finding update package...
I:Update location: /sdcard/LOST.DIR/SuperROM_v3.0.zip
Opening update package...
Installing update...
Installation aborted.
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
also i had wiped cache partition by mistake , i am new to xda and flashing roms,so i am a bit inexperienced any help would appreciated

Format emmc from inside cwm. Copy roms u wish to install to external SD card and install from there. Never install from internal memory

Emmc
Ok will try and reply thanks for help though

not able to install?!!
Still instalation is aborted but i noticed that when formated emmc it formated my external sd not internal memory ! Which could be the problem but still i dont know wha[YOUTUBE][/YOUTt to do to fix it it is giving same error during flashing

same problem !!!
I am having the same problem i cant flash a rom and stuck with incompatable ics theme help plzz anyone

Dragon Hunter @666 said:
Still instalation is aborted but i noticed that when formated emmc it formated my external sd not internal memory ! Which could be the problem but still i dont know wha[YOUTUBE][/YOUTt to do to fix it it is giving same error during flashing
Click to expand...
Click to collapse
this is the solution for your device: http://forum.xda-developers.com/gal...-pit-files-creating-larger-partition-t2552738

unable to nandroid sk4g,

Hi there i'm having issues doing a nandroid backup, i get and error on cwm.
what could i do to fix it, This is what is in the error log from cwm.
thanks in advance.
Starting recovery on Tue Nov 27 01:00:09 2012
framebuffer: fd 20 (480 x 800)
ClockworkMod Recovery v4.0.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot bml boot (null)
2 /recovery bml recovery (null)
3 /cache rfs /dev/block/stl11 (null)
4 /data rfs /dev/block/stl10 (null)
5 /sdcard vfat /dev/block/mmcblk0p1 (null)
6 /sd-ext ext4 /dev/block/mmcblk0p2 (null)
7 /system rfs /dev/block/stl9 (null)
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdkc110
ro.revision=48
ro.debugable=1
ro.build.id=FROYO
ro.build.display.id=FROYO.UVKD1
ro.build.version.incremental=UVKD1
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=2011. 04. 02. (토) 21:54:55 KST
ro.build.date.utc=1301748895
ro.build.type=user
ro.build.user=jwcris.park
ro.build.host=SEP-19
ro.build.tags=release-keys
ro.product.model=SGH-T839
ro.product.brand=samsung
ro.product.name=SGH-T839
ro.product.device=SGH-T839
ro.product.board=SGH-T839
ro.product.cpu.abi=armeabi-v7a
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=s5pc110
ro.build.product=SGH-T839
ro.build.description=SGH-T839-user 2.2.1 FROYO UVKD1 release-keys
ro.build.fingerprint=samsung/SGH-T839/SGH-T839/SGH-T839:2.2.1/FROYO/UVKD1:user/release-keys
ro.build.PDA=T839UVKD1
ro.build.hidden_ver=T839UVKD1
ro.build.changelist=976424
ro.tether.denied=false
rild.libpath=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libsec-ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit
persist.sys.timezone=America/New_York
ro.com.android.dataroaming=true
ro.opengles.version=131072
dalvik.vm.startheapsize=8m
windowsmgr.max_events_per_sec=55
windowsmgr.support_rotation_270=true
keyinputqueue.use_finger_id=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
keyguard.no_require_sim=true
ro.config.ringtone=TMO_Jingle.ogg
ro.config.notification_sound=Alert_galactica_1.ogg
ro.config.alarm_alert=Good_Morning.ogg
net.bt.name=Android
net.change=net.tcp.buffersize.gprs
dalvik.vm.stack-trace-file=/data/anr/traces.txt
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.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-hms-tmobile-us
ro.com.google.clientidbase.am=android-tmobile-us
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.gmsversion=2.2_r9
ro.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=1
ro.SECONDARY_SERVER_ADJ=2
ro.BACKUP_APP_ADJ=2
ro.HOME_APP_ADJ=4
ro.HIDDEN_APP_MIN_ADJ=7
ro.CONTENT_PROVIDER_ADJ=14
ro.EMPTY_APP_ADJ=15
ro.FOREGROUND_APP_MEM=1536
ro.VISIBLE_APP_MEM=2048
ro.SECONDARY_SERVER_MEM=4096
ro.BACKUP_APP_MEM=4096
ro.HOME_APP_MEM=4096
ro.HIDDEN_APP_MEM=5120
ro.CONTENT_PROVIDER_MEM=5632
ro.EMPTY_APP_MEM=6144
wifi.interface=eth0
ro.bt.bdaddr_path=/data/misc/bluetooth/bt_addr
net.tcp.buffersize.default=4096,87380,110208,4096,16384,110208
net.tcp.buffersize.wifi=4095,87380,110208,4096,16384,110208
net.tcp.buffersize.umts=4094,87380,110208,4096,16384,110208
net.tcp.buffersize.edge=4093,26280,35040,4096,16384,35040
net.tcp.buffersize.gprs=4092,8760,11680,4096,8760,11680
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
ro.radio.noril=yes
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
I:Running script:
I:
run_program("/sbin/cp", "-R", "/cache/recovery", "/tmp/recovery");
ui_print("ROM Manager Version 5.0.2.4");
ui_print("November 26, 2012");
assert(backup_rom("/sdcard/clockworkmod/backup/Stocksk4g"));
parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.0.2.4
November 26, 2012
SD Card space free: 8986MB
Backing up boot image...
Error while backing up boot image!result was NULL, message is: assert failed: backup_rom("/sdcard/clockworkmod/backup/Stocksk4g")

ecuajosh said:
Hi there i'm having issues doing a nandroid backup, i get and error on cwm.
what could i do to fix it, This is what is in the error log from cwm.
thanks in advance.
Starting recovery on Tue Nov 27 00:43:15 2012
framebuffer: fd 20 (480 x 800)
ClockworkMod Recovery v4.0.0.2
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot bml boot (null)
2 /recovery bml recovery (null)
3 /cache rfs /dev/block/stl11 (null)
4 /data rfs /dev/block/stl10 (null)
5 /sdcard vfat /dev/block/mmcblk0p1 (null)
6 /sd-ext ext4 /dev/block/mmcblk0p2 (null)
7 /system rfs /dev/block/stl9 (null)
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=smdkc110
ro.revision=48
ro.debugable=1
ro.build.id=FROYO
ro.build.display.id=FROYO.UVKD1
ro.build.version.incremental=UVKD1
ro.build.version.sdk=8
ro.build.version.codename=REL
ro.build.version.release=2.2.1
ro.build.date=2011. 04. 02. (토) 21:54:55 KST
ro.build.date.utc=1301748895
ro.build.type=user
ro.build.user=jwcris.park
ro.build.host=SEP-19
ro.build.tags=release-keys
ro.product.model=SGH-T839
ro.product.brand=samsung
ro.product.name=SGH-T839
ro.product.device=SGH-T839
ro.product.board=SGH-T839
ro.product.cpu.abi=armeabi-v7a
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=s5pc110
ro.build.product=SGH-T839
ro.build.description=SGH-T839-user 2.2.1 FROYO UVKD1 release-keys
ro.build.fingerprint=samsung/SGH-T839/SGH-T839/SGH-T839:2.2.1/FROYO/UVKD1:user/release-keys
ro.build.PDA=T839UVKD1
ro.build.hidden_ver=T839UVKD1
ro.build.changelist=976424
ro.tether.denied=false
rild.libpath=/system/lib/librilswitch.so
rilswitch.vendorlibpath=/system/lib/libsec-ril.so
rilswitch.ganlibpath=/system/lib/libganril.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
dalvik.vm.heapsize=48m
dalvik.vm.execution-mode=int:jit
persist.sys.timezone=America/New_York
ro.com.android.dataroaming=true
ro.opengles.version=131072
dalvik.vm.startheapsize=8m
windowsmgr.max_events_per_sec=55
windowsmgr.support_rotation_270=true
keyinputqueue.use_finger_id=true
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=true
media.stagefright.enable-http=true
keyguard.no_require_sim=true
ro.config.ringtone=TMO_Jingle.ogg
ro.config.notification_sound=Alert_galactica_1.ogg
ro.config.alarm_alert=Good_Morning.ogg
net.bt.name=Android
net.change=net.tcp.buffersize.gprs
dalvik.vm.stack-trace-file=/data/anr/traces.txt
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.locationfeatures=1
ro.setupwizard.mode=DISABLED
ro.com.google.clientidbase=android-samsung
ro.com.google.clientidbase.ms=android-hms-tmobile-us
ro.com.google.clientidbase.am=android-tmobile-us
ro.com.google.clientidbase.gmm=android-samsung
ro.com.google.clientidbase.yt=android-samsung
ro.com.google.gmsversion=2.2_r9
ro.FOREGROUND_APP_ADJ=0
ro.VISIBLE_APP_ADJ=1
ro.SECONDARY_SERVER_ADJ=2
ro.BACKUP_APP_ADJ=2
ro.HOME_APP_ADJ=4
ro.HIDDEN_APP_MIN_ADJ=7
ro.CONTENT_PROVIDER_ADJ=14
ro.EMPTY_APP_ADJ=15
ro.FOREGROUND_APP_MEM=1536
ro.VISIBLE_APP_MEM=2048
ro.SECONDARY_SERVER_MEM=4096
ro.BACKUP_APP_MEM=4096
ro.HOME_APP_MEM=4096
ro.HIDDEN_APP_MEM=5120
ro.CONTENT_PROVIDER_MEM=5632
ro.EMPTY_APP_MEM=6144
wifi.interface=eth0
ro.bt.bdaddr_path=/data/misc/bluetooth/bt_addr
net.tcp.buffersize.default=4096,87380,110208,4096, 16384,110208
net.tcp.buffersize.wifi=4095,87380,110208,4096,163 84,110208
net.tcp.buffersize.umts=4094,87380,110208,4096,163 84,110208
net.tcp.buffersize.edge=4093,26280,35040,4096,1638 4,35040
net.tcp.buffersize.gprs=4092,8760,11680,4096,8760, 11680
init.svc.console=running
init.svc.recovery=running
init.svc.adbd=running
ro.radio.noril=yes
status.battery.state=Slow
status.battery.level=5
status.battery.level_raw=50
status.battery.level_scale=9
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
I:Running script:
I:
run_program("/sbin/cp", "-R", "/cache/recovery", "/tmp/recovery");
ui_print("ROM Manager Version 5.0.2.4");
ui_print("November 26, 2012");
assert(restore_rom("/sdcard/clockworkmod/backup/11_12sk4gstock", "boot", "system", "data", "cache", "sd-ext"));
parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.0.2.4
November 26, 2012
Checking MD5 sums...
boot.img: OK
cache.img: OK
data.img: OK
recovery.img: OK
system.img: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Error while flashing boot image!result was NULL, message is: assert failed: restore_rom("/sdcard/clockworkmod/backup/11_12sk4gstock", "boot", "system", "data", "cache", "sd-ext")
Click to expand...
Click to collapse
This is new to me 0.0 I know there are big issues with the Rom Manager version of CWM. Did you use that recovery image??? Just a pre-question. Or do you have a Voodoo Recovery?

Zydrate_blue said:
This is new to me 0.0 I know there are big issues with the Rom Manager version of CWM. Did you use that recovery image??? Just a pre-question. Or do you have a Voodoo Recovery?
Click to expand...
Click to collapse
i used CWM (orange). i change the mount orders as it's always it's been suggested for when flashing different ROM but i get the same message. I will try a different sd card just in case.

ecuajosh said:
i used CWM (orange). i change the mount orders as it's always it's been suggested for when flashing different ROM but i get the same message. I will try a different sd card just in case.
Click to expand...
Click to collapse
That's a good idea. Never know sometimes with SD cards.
What I mean't by which recovery though, was which version is it? Because there are 2 versions:
-the one uploaded for download on Rom Manager is broken, it does not work correctly, and will not(likely) ever. The bad copy is version [4.0.0.2]
-Then there is the one made by Krylon360, and is the version 3.0.2.8 I believe? Did you use this one?

i couldn't find another sd. i'll probably get one tomorrow, and yeah the vesion i have is 4.0.0.2. i'll odin and start from scratch, thanks tho i didn't know 4.0.0.2 was a bad update

what had happen was i had bumped in to a script that roots and install cwm somewhere here, and it installs 4.0.0.2.
well finally got it to work hours of reading and more reading leading to dead links and more dead links to file.
so the steps are 1)odin to get a stock rom, 2) root with oneclick, 3) use the script and click run.bat to get the cwm 3.0.2.8 (since that recovery file isn't available) and VOILA!.
thanks guys

ecuajosh said:
what had happen was i had bumped in to a script that roots and install cwm somewhere here, and it installs 4.0.0.2.
well finally got it to work hours of reading and more reading leading to dead links and more dead links to file.
so the steps are 1)odin to get a stock rom, 2) root with oneclick, 3) use the script and click run.bat to get the cwm 3.0.2.8 (since that recovery file isn't available) and VOILA!.
thanks guys
Click to expand...
Click to collapse
That's great I had a feeling that was the problem, Rom Manager has a messed up file to distribute. Pretty useless.
And I apologize for not getting back sooner, I had to get going somewhere yesterday. But still I'm glad to help by the way, I have the recovery file if you'd like it. Or actually, I think I know where there is a link.
Try this and you can have a backup of it now (this was OP by user "Kediil") ---> http://db.androidspin.com/Developer_Display.asp?DeveloperID=248
**EDIT** Look a little towards the bottom and the files should be available ^-^

Now that you have recovery, get Bali or Platypus Egg and put an end to the silliness.

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] 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