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

Backup help for a working, though smashed, SK4g

Ok, so, long story short, my suicidal little sidekick decided to leap from my moving motorcycle. Of course I went back for the little bugger, only to be forced to stand by the highway on ramp watching his poor little frame get run over by no less than three separate vehicles. Unfortunately, in the tragic scene, his SD Card made its own escape, which means my Titanium backups are, to say the least, gone. However, I just plugged him in to the computer and low and behold, the computer detects him! Not only that, but for all that his face is smashed and detached, he turns on, makes all his appropriate sounds of the home screen and buttons, buzzes for notifications, and the keyboard lights up and beeps to its keys. So, I'm thinking his guts are still in working order.
What I'm looking for, is some way of accessing him to make a backup. I have a new sidekick on the way, and the prospect of saving *any* of my data is too sweet a thing to pass up. I plan to get a busted SK as well and swap out his guts to see if I can have a backup.
Any help would be immensely appreciated!

It's really easy to take the Sidekick apart. I suggest swapping the main boards between this and a working sidekick. If the mainboard is undamaged (And it sounds like it's in pretty good shape,) you should be able to fire it right up.
See http://forum.xda-developers.com/showthread.php?t=1466906 for disassembly instructions.

I inspected further earlier and from what I can tell, aside from the very popcorn screen (with its otherwise undamaged screen protector ;p), a keyboard plate that needs a little straightening and reinsertion, and a few scratches to the skin, everything else is looking good. I'm thinking I might just need to replace the screen. Or swap the board like you suggested if I can get a physically working SK for a decent price.
^..^

Also you could try rooting your new sk installing a rom with voodoo recovery booting both the new and the busted sk into recovery by pulling the battery, putting it back in and pressing vol up+vol down+power till the splash screen comes up and release the buttons. Then navigate in tandem to backup and restore and creating a nandroid backup on the busted sk then putting the sd card from the busted sk into the new one and doing a restore and boom you cloned your old sk
Sent from my SGH-T839 using XDA

That's definitely a good idea, so long at the new SK is fully functional. Only problem might be that I don't currently have nandroid on my busted SK. Hopefully I'll be able to figure it out though. ^..^ If I just end up swapping the guts, then doing a backup shouldn't be an issue.

Lol if you have cwm installed on it either red voodoo or orange you can do a nandroid backup. When you boot into recovery there's an option on the list called backup and restore that's what I'm talking about
Sent from my SGH-T839 using XDA

Ah, I gotcha! My bad. ;p

A smartacle type friend came over and we set up webkey so I have a virtual screen now. Made an adb backup and a titanium backup. Just have to find myself a phone to flip this brain into.
If anyone who happens by this has, or know someone who has, a spare SK4g sitting about in pieces or with a bad board or something, I'd much appreciate it. All I really must have is the full slide-screen assembly, but I'm having a touch time finding something for under $80.

azcledel said:
Lol if you have cwm installed on it either red voodoo or orange you can do a nandroid backup. When you boot into recovery there's an option on the list called backup and restore that's what I'm talking about
Sent from my SGH-T839 using XDA
Click to expand...
Click to collapse
hi there im 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.
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,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(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")
(i opened a new thread, so if you guys want to remove it is fine with me)

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

[KERNEL]elementaryKernel v1.4

This month I created a new kernel to compensate for the lost stability in Badass, and I thought it would be nice to share it with you.
Based on the original 2.6.35 source from Samsung OpenSource Software, this kernel is cleaner than Badass, without unnecessary hybrid updates and risky mods.
Features:
3-step Undervolted
Brain F*ck Scheduler 0.416 with O(1) complexity instead of O
UltraKSM 0.122
Sweep2Wake
DoubleTap2Wake (on the upper half of the screen)
DoubleTap2Play/Pause (on the lower half of the screen)
DoubleTap2Lock (on the StatusBar)
SwipeBack
Pocket Keyguard (to avoid accidental unlocks when the phone is inside the pocket)
SIOPlus I/O Scheduler
Optimized Wheatley CPU Governor
Fast Random Generator (frandom)
LowMemoryKiller 3.4
Entropy tweaks (haveged service, binfmt_elf.c code optimization)
Dynamic Readahead, cache pressure and writeback parameters
Adaptive Overclock
Changelog:
v1.4
New Adaptive Overclock feature
Fully functional LowMemoryKiller from 3.4 kernel
LZ4 compression for ZRam, kernel and ramdisk
v1.3
Fix multitouch
v1.2
Improve branch prediction for Fit drivers
Add Dynamic Overclock
Implement Dynamic cache pressure and writeback parameters
Global SwipeBack feature (swipe left from the right side of the action bar)
Disable kernel logs (printk)
Add modified Wheatley governor
Update Zram and ZsmAlloc drivers from androidarmv6 sources
Make most launcher unkillable
Use different minfree/adj configuration for improved multitasking
Add a NoSweep kernel version
v1.1
Add Landscape mode for DoubleTap2Lock
Update BFS to 0.416
Add AOKP build
Downloads​
What is Adaptive Overclock?
If the max frequency is higher then 600 MHz, the CPU will be allowed to use that frequency only in extreme cases, when it is actually needed. (e.g. gaming, surfing internet, heavy multitasking)
This feature works only with the Wheatley governor.
Sources: https://github.com/alin23/android_gio_stock_kernel
Don't use scripts/perfomance packs/Crossbreeder on this kernel.
XDA:DevDB Information
elementary Kernel, Kernel for the Samsung Galaxy Fit GT 5670
Contributors
alin.p
Kernel Special Features: Sweep2Wake, DoubleTap2Wake/Lock, Undervolting
Version Information
Status: Stable
Current Stable Version: 1.4
Created 2014-01-30
Last Updated 2014-07-11

wow! thanks for compiling for galaxy fit .
are all of them for ICS?

ehsan-black said:
wow! thanks for compiling for galaxy fit .
are all of them for ICS?
Click to expand...
Click to collapse
Yes, the kernel is ICS-exclusive for now

Thanks for your work, alin.p!
Hope this kernel will work in future for CM11 :fingers-crossed:

Installed it and working pretty good, what's the best ROM to use this with?

Mr GRiM said:
Installed it and working pretty good, what's the best ROM to use this with?
Click to expand...
Click to collapse
You can use it on any ICS ROM. The kernel performs the same in every ROM, so there's no "best ROM to use it with". Just pick a ROM that suits your needs.

KitKat/JellyBean builds
Uploaded CM11, CM10.2 and CM10.1 builds.

alin.p said:
Uploaded CM11, CM10.2 and CM10.1 builds.
Click to expand...
Click to collapse
Cm7 too ?

Solved
i tried elementaryAOSP-NoSweep.zip V1.4 and i got this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
i checked the MD5sum and it was the same as yours...
i had the same problem 1year ago and i think my phone is bricked again
Can i revive My phone? i haven't rebooted it yet.
------
i checked /boot/ with adb and it's completely empty!
@alin.p i think the image is too big for boot partition. anyway can i use e2fsck to fix badblocks in boot partition??
----------
recovery log:
Code:
Starting recovery on Tue Feb 4 01:12:17 2014
framebuffer: fd 4 (256 x 320)
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 ext4 /dev/block/stl14 (null)
4 /data ext4 /dev/block/stl13 (null)
5 /system ext4 /dev/block/stl12 (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /sd-ext ext4 /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.
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.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.tjstyle.20111116.000635
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Wed Nov 16 00:07:27 WIT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=tjstyle
ro.build.host=dev-pc
ro.build.tags=test-keys
ro.product.model=GT-S5670
ro.product.brand=samsung_beni
ro.product.name=GT-S5670
ro.product.device=beni
ro.product.board=beni
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=beni
ro.build.description=GT-S5670-user 2.3.4 GINGERBREAD XXKPI release-keys
ro.build.fingerprint=samsung/GT-S5670/GT-S5670:2.3.4/GINGERBREAD/XXKPI:user/release-keys
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
DEVICE_PROVISIONED=1
ro.sf.lcd_density=120
qemu.sf.lcd_density=120
ro.opengles.version=131072
wifi.interface=wlan0
ro.telephony.ril_class=samsung
mobiledata.interfaces=pdp0,gprs,ppp0,wlan0
ro.media.enc.vid.m4v.fps=5,15
ro.media.enc.vid.m4v.width=176,320
ro.media.enc.vid.m4v.height=144,240
ro.media.enc.vid.m4v.bps=90000,770000
ro.media.enc.vid.h264.fps=5,15
ro.media.enc.vid.h264.width=176,320
ro.media.enc.vid.h264.height=144,240
ro.media.enc.vid.h264.bps=90000,770000
ro.media.enc.vid.h263.fps=5,15
ro.media.enc.vid.h263.width=176,320
ro.media.enc.vid.h263.height=144,240
ro.media.enc.vid.h263.bps=90000,770000
ro.media.enc.vid.height.min=144
ro.media.enc.vid.height.max=240
ro.media.enc.vid.width.min=176
ro.media.enc.vid.width.max=320
ro.media.enc.vid.bps.min=90000
ro.media.enc.vid.bps.max=770000
ro.media.enc.vid.fps.min=5
ro.media.enc.vid.fps.max=15
keyguard.no_require_sim=true
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.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.1.0-GalaxyFit-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-s5670
ro.revision=3
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /sdcard/elementaryAOSP-NoSweep.zip
Finding update package...
I:Update location: /sdcard/elementaryAOSP-NoSweep.zip
Opening update package...
Installing update...
Installing elementaryKernel
script aborted: assert failed: write_raw_image("/tmp/boot.img", "boot")
assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Error in /sdcard/elementaryAOSP-NoSweep.zip
(Status 7)
Installation aborted.

I tried elementaryCM11-Sweep on CM11 and the results were not great, random restarts, freezing, applications closing, keyboard stops working and overall very slow, restored my backup.

ehsan-black said:
i tried elementaryAOSP-NoSweep.zip V1.4 and i got this:
i checked the MD5sum and it was the same as yours...
i had the same problem 1year ago and i think my phone is bricked again
Can i revive My phone? i haven't rebooted it yet.
------
i checked /boot/ with adb and it's completely empty!
@alin.p i think the image is too big for boot partition. anyway can i use e2fsck to fix badblocks in boot partition??
----------
recovery log:
Code:
Starting recovery on Tue Feb 4 01:12:17 2014
framebuffer: fd 4 (256 x 320)
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 ext4 /dev/block/stl14 (null)
4 /data ext4 /dev/block/stl13 (null)
5 /system ext4 /dev/block/stl12 (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /sd-ext ext4 /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.
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.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GWK74
ro.build.version.incremental=eng.tjstyle.20111116.000635
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Wed Nov 16 00:07:27 WIT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=tjstyle
ro.build.host=dev-pc
ro.build.tags=test-keys
ro.product.model=GT-S5670
ro.product.brand=samsung_beni
ro.product.name=GT-S5670
ro.product.device=beni
ro.product.board=beni
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=beni
ro.build.description=GT-S5670-user 2.3.4 GINGERBREAD XXKPI release-keys
ro.build.fingerprint=samsung/GT-S5670/GT-S5670:2.3.4/GINGERBREAD/XXKPI:user/release-keys
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d /dev/smd0
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
DEVICE_PROVISIONED=1
ro.sf.lcd_density=120
qemu.sf.lcd_density=120
ro.opengles.version=131072
wifi.interface=wlan0
ro.telephony.ril_class=samsung
mobiledata.interfaces=pdp0,gprs,ppp0,wlan0
ro.media.enc.vid.m4v.fps=5,15
ro.media.enc.vid.m4v.width=176,320
ro.media.enc.vid.m4v.height=144,240
ro.media.enc.vid.m4v.bps=90000,770000
ro.media.enc.vid.h264.fps=5,15
ro.media.enc.vid.h264.width=176,320
ro.media.enc.vid.h264.height=144,240
ro.media.enc.vid.h264.bps=90000,770000
ro.media.enc.vid.h263.fps=5,15
ro.media.enc.vid.h263.width=176,320
ro.media.enc.vid.h263.height=144,240
ro.media.enc.vid.h263.bps=90000,770000
ro.media.enc.vid.height.min=144
ro.media.enc.vid.height.max=240
ro.media.enc.vid.width.min=176
ro.media.enc.vid.width.max=320
ro.media.enc.vid.bps.min=90000
ro.media.enc.vid.bps.max=770000
ro.media.enc.vid.fps.min=5
ro.media.enc.vid.fps.max=15
keyguard.no_require_sim=true
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.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.1.0-GalaxyFit-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-s5670
ro.revision=3
ro.emmc=0
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /sdcard/elementaryAOSP-NoSweep.zip
Finding update package...
I:Update location: /sdcard/elementaryAOSP-NoSweep.zip
Opening update package...
Installing update...
Installing elementaryKernel
script aborted: assert failed: write_raw_image("/tmp/boot.img", "boot")
assert failed: write_raw_image("/tmp/boot.img", "boot")
E:Error in /sdcard/elementaryAOSP-NoSweep.zip
(Status 7)
Installation aborted.
Click to expand...
Click to collapse
Try flashing CWM 6.0.2.7 then reflash the kernel. The image is big because of the AOSP binaries. The original AOSP kernel is also big and is only 0.5MB smaller. I've never seen your problem before, but if you can boot in recovery then your phone is not bricked. You can't brick this phone, unless you flash a wrong bootloader with ODIN.

alin.p said:
Try flashing CWM 6.0.2.7 then reflash the kernel. The image is big because of the AOSP binaries. The original AOSP kernel is also big and is only 0.5MB smaller. I've never seen your problem before, but if you can boot in recovery then your phone is not bricked. You can't brick this phone, unless you flash a wrong bootloader with ODIN.
Click to expand...
Click to collapse
i don't know what happend last time that i saw this problem but this time my phone didn't brick :victory:

I tried the elementaryAOSP-NoSweep.zip with the AOSP ICS | Release #3 by #root .. I had a wifi bug which was solved with this kernel but i experienced performance degradation.. The ROM started lagging and the apps took a lot of time to load and at times there was a FC..
This is a great kernel and if the mentioned things are fixed, i dont think there will be any kernel like elementaryKernel.. :victory: :highfive: :laugh: :good:
P.S - As suggested by alin.p , no performance scripts were installed...

Bro, will you make this kernel for cm10 ?
I really need it
Thanks

He already did check the download links.

Rminsh said:
Bro, will you make this kernel for cm10 ?
I really need it
Thanks
Click to expand...
Click to collapse
I think he already has...
Here : http://d-h.st/users/alin/?fld_id=32374#files

Dhanesh95 said:
I think he already has...
Here : http://d-h.st/users/alin/?fld_id=32374#files
Click to expand...
Click to collapse
no dude!
thats cm10.1!
i need cm10

Dhanesh95 said:
I think he already has...
Here : http://d-h.st/users/alin/?fld_id=32374#files
Click to expand...
Click to collapse
@alin.p are those kernels compatible with fit?
EDIT: Disregard the question i didn't read the folder named kernel-beni

Rminsh said:
no dude!
thats cm10.1!
i need cm10
Click to expand...
Click to collapse
ooohh... I didnt realise that.. :silly: :silly:

Hi,
Some observations on lagginess.
1. I find the default 768MHz just a bit too much for my GT-S5670, I get random reboots. 748MHz is more stable, no random reboots.
2. I find the Wheatley governor very 'sticky'. I think it freezes my whole phone momentarily while it makes up it's mind if full CPU is required then sets full CPU. If I change to smartassv2 99% of the sticks disappear, this leads me to believe the stickiness is governor related.
Regards,
jemail

[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