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)
Related
[HOWTO] Manually updating firmware using "dlpkgfile" download via Asus FOTA server
FOTA UPDATE version 9.4.5.26-20120720 is known to provide improvements and fixes to address I/O issues, and MicroSD U-1 card compatibility.
Based on the original post here:
http://forum.xda-developers.com/showpost.php?p=29485094&postcount=58
Thanks to Lufterfischer for discovery, and jtrosky for testing it!
Here's the summary of what's needed to manually update using the patch file "dlpkgfile".
This is merely a documentation to help TF700 users to over come their IO problems by manually updating to FOTA version 9.4.5.26-20120720.
A short history of: OTA update happened briefly on 28/7/2012 and became unavailable to owners of TF700 tablet.
Before you start make sure your tablet is charged fully.
Disclaimer: I'm not responsible for whatever you are going to do or did to your tablet.
For those who have unlocked bootloader and custom recovery you can try this method of restoring your stock recovery by copying the blob image back to /staging on device /dev/block/mmcblk0p4
Follow the howto in the following link.
http://forum.xda-developers.com/showthread.php?t=1492887
Prerequisite
1. root
2. a copy of dlpkgfile for correct firmware version
3. a correct firmware installed on the device (9.4.5.22-20120615) for patching
4. unmodified build.prop as some has reported it was the cause for update failure.
5. make sure you don't have any of the existing files under /system modified
Here are the steps:
1. use root explorer to copy "dlpkgfile" into /cache/ directory.
Alternatively you could save the "dlpkgfile" in a microSD then open up a adb shell session.
Type:
su
cat /Removable/MicroSD/dlpkgfile > /cache/dlpkgfile
2. create the file called "command" under /cache/recovery/ directory.
3. write this statement in the file /cache/recovery/command (without qoutes) "--update_package=/cache/dlpkgfile"
Or you can just use the attached file "command" and
cat /Removable/MicroSD/command > /cache/recovery/command
Note: remove MicroSD before this last step.
4. finally reboot into recovery kernel by shutting down first, then press and hold "Volume down" + "Power" once it vibrates release "Power" keep holding "Volume down" until there are some text shown on the boot logo screen. Then press "Volume up" within 5 seconds after releasing "Volume down".
The update process should start... wait for it to complete.
Once it completes, you should have the updated firmware installed on your tablet.
Reference:
US version patch "dlpkgfile" can be found here -> http://forum.xda-developers.com/showthread.php?t=1801756
md5sum for this file is 2ff06463b57226ac910ac642781c5290
If you have received the FOTA update already and haven't updated the firmware and you have root access to your WW, JP, TW, CN version TF700 tablet.
Could you please pull or copy the /cache/dlpkgfile and upload it to your dropbox for backup and please do provide a link for other users to download, Thanks!
********************************************************************************************************
For whatever reason: eg, you disliked the updated firmware
To revert back to firmware version 9.4.5.22-20120615
Extract the blob file from zip within "**epad_user_9_4_5_22_UpdateLauncher.zip" and save
it to a MicroSD
Simply launch the following command under adb shell as root:
Code:
dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
Then wait patiently for the process to complete once it finish you will see some output as
follows and it returns to the root shell prompt:
1596712+1 records in
1596712+1 records out
817516935 bytes transferred in 383.960 secs (2129172 bytes/sec)
[email protected]:/ #
Click to expand...
Click to collapse
Now reboot the device, the downgrade process should automatically start!
Just do a factory reset after that !!
Note: Camera and Touch panel firmware can't be downgraded and will stay up-to-date.
********************************************************************************************************
would this work if I have a custom recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
tbogunro said:
would this work if I have a custom recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No... I'm waiting too.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
tbogunro said:
would this work if I have a custom recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
It's best to flash recovery back to stock, no point having customer recovery installed right now as there isn't any custom ROM available for TF700 yet.
You're right, but how would I do that?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
tbogunro said:
You're right, but how would I do that?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
What is the firmware version (US?) of your tablet ?
Maybe you can try this -> http://forum.xda-developers.com/showthread.php?t=1492887
Don't do it if you aren't confident enough otherwise you'll risk bricking your device.
It was originally a US based firmware, but I patched it to a now currently WW 9.4.5.22
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
When it says tocreate thecommand file, is it a text file what is the file extension?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
teknomanelvis said:
When it says tocreate thecommand file, is it a text file what is the file extension?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
it's just a file named "command" without any extension.
Redefined301 said:
What is the firmware version (US?) of your tablet ?
Maybe you can try this -> http://forum.xda-developers.com/showthread.php?t=1492887
Don't do it if you aren't confident enough otherwise you'll risk bricking your device.
Click to expand...
Click to collapse
Thanks for your help, but I'm not going to risk it lol
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Redefined301 said:
It's best to flash recovery back to stock, no point having customer recovery installed right now as there isn't any custom ROM available for TF700 yet.
Click to expand...
Click to collapse
To my knowledge u can't go back to stock recovery.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
As far as I know from TF201, you can't flash the stock OTA if you unlocked your bootloader.
Althoug I must confess, that I've forgotten the background & reasons for that
newellj79 said:
To my knowledge u can't go back to stock recovery.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
OK, I took the risk...
Using the info here: http://forum.xda-developers.com/showthread.php?t=1492887
I was able to grab the blob from the .22 update and restore the stock recovery. My device is still unlocked, but has the stock recovery reinstalled. Using the info from the OP, I was able to successfully apply the OTA to .26
I'll write up a quick how to from start to finish.
newellj79 said:
To my knowledge u can't go back to stock recovery.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Someone just reverted back to stock recovery.
eoh7678 said:
OK, I took the risk...
Using the info here: http://forum.xda-developers.com/showthread.php?t=1492887
I was able to grab the blob from the .22 update and restore the stock recovery. My device is still unlocked, but has the stock recovery reinstalled. Using the info from the OP, I was able to successfully apply the OTA to .26
I'll write up a quick how to from start to finish.
Click to expand...
Click to collapse
Yeah it will definitely work as long as you don't make a typo doing dd..
So that's interesting ... Did you flashed to stock recovery from customer recovery? Or was it simply unlocked?
Does anyone have a stock build.prop file, here is mine?
Code:
127|[email protected]:/system $ cat build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.US_epad-9.4.5.22-20120615
ro.build.version.incremental=US_epad-9.4.5.22-20120615
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jun 15 19:13:51 CST 2012
ro.build.date.utc=1339758831
ro.build.type=user
ro.build.user=
ro.build.host=Mercury
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=US_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=EeePad
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.4.5.22-20120615 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
persist.tegra.nvmmlite = 1
#NFC
debug.nfc.fw_download=false
debug.nfc.se=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
wifi.version.driver=V6.1.38
gps.version.driver=V6.9.18
keyguard.no_require_sim=true
ro.kernel.qemu=
bt.version.driver=V9.32
windowsmgr.max_events_per_sec=200
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r2
ro.com.google.clientidbase=android-asus
ro.wifi.country=US
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
I have tried doing this and still get the dead android with the following last_log:
Code:
[email protected]:/cache/recovery # cat last_log
Starting recovery on Sun Jul 29 12:13:20 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /misc emmc /dev/block/mmcblk0p3 (null) 0
4 /boot emmc boot (null) 0
5 /recovery emmc recovery (null) 0
6 /staging ext3 /dev/block/mmcblk0p4 (null) 0
7 /btmac vfat /dev/block/mmcblk0p5 (null) 0
8 /data ext4 /dev/block/mmcblk0p8 (null) -32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
I:Got arguments from /cache/recovery/command
Command: "/sbin/recovery" "--update_package=/cache/dlpkgfile"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp,adb
ro.build.id=IML74K
ro.build.display.id=IML74K.US_epad-9.4.5.22-20120615
ro.build.version.incremental=US_epad-9.4.5.22-20120615
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jun 15 19:13:51 CST 2012
ro.build.date.utc=1339758831
ro.build.type=user
ro.build.user=
ro.build.host=Mercury
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=US_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=EeePad
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.4.5.22-20120615 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
debug.nfc.fw_download=false
debug.nfc.se=false
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
wifi.version.driver=V6.1.38
gps.version.driver=V6.9.18
keyguard.no_require_sim=true
ro.kernel.qemu=
bt.version.driver=V9.32
windowsmgr.max_events_per_sec=200
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r2
ro.com.google.clientidbase=android-asus
ro.wifi.country=US
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
ro.factorytest=0
ro.serialno=C6OKAS105604
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=wifi-only
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.boot_reason=normal
ro.crypto.fs_type=ext4
ro.crypto.fs_real_blkdev=/dev/block/mmcblk0p8
ro.crypto.fs_mnt_point=/data
ro.crypto.fs_flags=0x00000006
ro.crypto.state=unencrypted
ro.epad.model_id=04
ro.epad.model=TF700T
ro.sf.lcd_density=240
persist.sys.NV_DISPXRES=1920
persist.sys.NV_DISPYRES=1200
persist.sys.NV_STEREOCTRL=0
persist.tegra.NV_FPSLIMIT=0
persist.sys.NV_FPSLIMIT=35
persist.sys.NV_POWERMODE=1
persist.sys.profiler_ms=0
persist.sys.NV_STEREOSEP=20
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_PROFVER=20
persist.sys.fw.camera.status=1
persist.sys.language=en
persist.sys.country=US
persist.sys.localevar=
persist.sys.timezone=America/New_York
persist.sys.ui.hw=true
init.svc.recovery=running
init.svc.adbd=running
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
E:failed to verify whole-file signature
I:verify_file returned 1
E:signature verification failed
Installation aborted.
I:result_code: 405
Check and format /storage to vfat if needed...
Mount /btmac successfully
Done.
currently trying to get to stock recovery.
I never unlocked, but did run v6 supercharger, and have since many times factory reset and gone though recovery and manually flashed the .22, and then will try this again...
Stock build.prop on .26 WW, same number of lines as on .22, haven't diff'ed it yet:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.WW_epad-9.4.5.26-20120720
ro.build.version.incremental=WW_epad-9.4.5.26-20120720
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jul 20 19:32:57 CST 2012
ro.build.date.utc=1342783977
ro.build.type=user
ro.build.user=
ro.build.host=Mercury
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=EeePad
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=WW_epad-user 4.0.3 IML74K WW_epad-9.4.5.26-20120720 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.0.3/IML74K/WW_epad-9.4.5.26-20120720:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
persist.tegra.nvmmlite = 1
#NFC
debug.nfc.fw_download=false
debug.nfc.se=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
wifi.version.driver=V6.1.40
gps.version.driver=V6.9.18
keyguard.no_require_sim=true
ro.kernel.qemu=
bt.version.driver=V9.37
windowsmgr.max_events_per_sec=200
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r3
ro.com.google.clientidbase=android-asus
ro.com.google.mcc_fallback=262
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
Edit: OK, I've just compared build.prop from WW .26 with the one from WW .21, no changes apart from the version numbers (which is actually a little disappointing, as they haven't touched it).
GrimSage said:
Does anyone have a stock build.prop file?
I have tried doing this and still get the dead android
currently trying to get to stock recovery.
I never unlocked, but did run v6 supercharger, and have since many times factory reset and gone though recovery and manually flashed the .22, and then will try this again...
Click to expand...
Click to collapse
It seems you have a corrupted dlpkgfile
the correct md5sum for dlpkgfile should be
2ff06463b57226ac910ac642781c5290
Your build.prop is stock. Just got to download "dlpkgfile" again because it won't verify on your tablet.
I posted a write up of the process I followed to restore the system image, build.prop, and stock recovery, then update to .26 using dlpkgfile if anyone's interested.
It's here: http://forum.xda-developers.com/showthread.php?t=1803343
Redefined301 said:
It seems you have a corrupted dlpkgfile
the correct md5sum for dlpkgfile should be
2ff06463b57226ac910ac642781c5290
Your build.prop is stock. Just got to download "dlpkgfile" again because it won't verify on your tablet.
Click to expand...
Click to collapse
looks like somewhere between restoring the stock recovery and redownloading the dlpkgfile, this has worked.
Currently have
Android is upgrading...
Optimizing application XX of XX.
Thank you to everyone!
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.
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
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
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