Database Info

[9001][Recovery] Fixed FeaMod V1.4 [FINAL PROPER] [No BootLoops] [NonOC] [NonUV]

This is a fixed version of manveru0's FeaMod recovery V1.4 (aka CWM recovery v 5.5.0.4) so all credits go to him.
Disclaimer: this piece of software is not for the unexperienced and might bring you in a situation you can't resolve yourself. So don't use it if you fear the potential danger of bricking your device. I am responsible for nothing related to this piece of software and therefore won't help. If you decide to use it anyway you agree to be ultimately responsible for all consequences that may occur. So you have been warned !
Terms of use: Remember the power of reading ! If you can't find some particular information on the first page use the search function, it is your best friend.
Besides there are even guides and tutorials all over the forum and in most cases your question was already answered.
If you take a moment and read through the WHOLE post below and a few more moments to read some of all the stuff in other device related threads of this forum, you will find ALL you need just there.
It's not invisible so you CAN find it. And forum rules and good manners tell you to do it exactly like this. And I WILL ignore every question that is already answered here.
Obey the rules !
Recovery feature list
- the internally used kernel to boot CWM recovery is not overclocked and not undervolted and uses Samsung's stock kernel settings so it should work on any i9001 phone (it's different from manveru0's release and I already released this fix in January in the original FeaMod thread)
- reworked the integrated script in recovery startup sequence that takes care about the recovery reboot issue automatically so no more rebooting into recovery again and again once and for all (reported to work finally by wintel_mac, thanks for testing all releases)
- the CWM 5.5.0.4 recovery itself remains totally untouched and is the very same as in FeaMod V1.4; for any more information on that please refer to the original FeaMod thread here:
http://forum.xda-developers.com/showthread.php?t=1331164
- the package includes only the recovery image so anything else on your phone remains untouched including your boot kernel; the recovery partition has its own kernel integrated which is only used for booting CWM recovery, in all other cases your original kernel in the boot partition is used - primarily for booting android that is
​
This version is meant for use with ANY i9001 ROM including stock ROMs, custom ROMs and even AOSP ROMs as well (as soon as the latter are actually available)
Install instructions:
1. If you don't have already any CWM version (FeaMod Recovery) install V1.2 via Odin first. If you never heard of that learn all about it here:
http://forum.xda-developers.com/showthread.php?t=1331164
2. Now make a complete nandroid backup of your phone with CWM
3. Download the attached CWM zip package
4. Copy it to your internal sdcard
5. In CWM choose "install zip from sdcard", then "choose zip from internal sdcard"
6. Select the downloaded file "FeaModV1.4_Fixed_NoBootLoop_NonOC_NonUV.zip"
7. Confirm install with "Yes"
8. Wait till you see the message "Reboot to use Fixed FeaMod V1.4 !"
9. Do so like the message says.
10. On first reboot the fix to cure the recovery reboot wasn't yet executed so you will end up in recovery once again (if your phone is affected with that issue) !
11. So you have to reboot into system once again and from now on everything will be fine, promised That is if you installed it properly and exactly like described above.
​
If anything went wrong during install just try again.
If you can't boot into recovery anymore just install FeaMod 1.2 via Odin again.
If you want to install Fixed FeaMod V1.4 directly via odin just extract the recovery.img only from the zip file and tar it. Then flash it via Odin in one package mode. If you don't know how to do that refer to the flash guides in this i9001 subforum or use the above described method only. If you still can't handle anything of that don't use FeaMod/CWM at all, you will most probably brick your phone with it.
The experienced users (ONLY !!!) can also use dd of course to flash the recovery.img directly to the appropriate partition
If you got severe errors AND didn't make a backup because you knew better than the developer don't even dare to beg for help.
If you encounter any other errors report them here but be sure that this is no feature or problem that was already described above.

reserved...

reserved ...

Sorry, but I'm the show stopper... the phone still boots into recovery.
Still need to wipe mmcblk0p14 to get out of this loop

Thanks ! Works perfect for me
I dded the img

wintel_mac said:
Sorry, but I'm the show stopper... the phone still boots into recovery.
Still need to wipe mmcblk0p14 to get out of this loop
Click to expand...
Click to collapse
Ooops, this means the script isn't actually executed. Couldn't test it properly since my phone isn't affected by the issue. Will review that immediately.

Looks like im the wrong person to test this out
It always worked fine for me

nail16 said:
Thanks ! Works perfect for me
I dded the img
Click to expand...
Click to collapse
Which would mean the script works but the CWM install routine doesn't.
@wintelmac: can you please attach the default.prop file that shows up when you boot into recovery ?
Code:
adb shell "cat /default.prop" > default.prop

nail16 said:
Looks like im the wrong person to test this out
It always worked fine for me
Click to expand...
Click to collapse
Funny, couldn't you say that earlier ?

couldn't you refresh your page earlier ?
Should i post my last_log of the recovery ?

nail16 said:
couldn't you refresh your page earlier ?
Click to expand...
Click to collapse
no, because I was already in posting mode
nail16 said:
Should i post my last_log of the recovery ?
Click to expand...
Click to collapse
Won't help since you are not affected by the issue anyway. New version already uploaded, wintel_mac can test it now.

It's kinda funny your's and my phone are not effected by the recovery bug,
but you'r kernel still managed to screw up my sdcard

nail16 said:
It's kinda funny your's and my phone are not effected by the recovery bug,
but you'r kernel still managed to screw up my sdcard
Click to expand...
Click to collapse
Which only proves what I said: no two phones are exactly the same

Yep, here it is
Code:
C:\Users\User>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # cat /default.prop
cat /default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.035
237 test-keys
ro.build.version.incremental=eng.root.20120216.035237
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Thu Feb 16 04:20:00 CET 2012
ro.build.date.utc=1329362400
ro.build.type=eng
ro.build.user=root
ro.build.host=ANKObian
ro.build.tags=test-keys
ro.product.model=GT-I9001
ro.product.brand=Samsung
ro.product.name=full_galaxysplus
ro.product.device=galaxysplus
ro.product.board=qcom
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galaxysplus
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.03
5237 test-keys
ro.build.fingerprint=Samsung/full_galaxysplus/galaxysplus:2.3.7/GINGERBREAD/eng.
root.20120216.035237:eng/test-keys
ro.cm.device=galaxysplus
# end build properties
#
# system.prop for galaxysplus
#
# from init.rc
#service.brcm.bt.srv_active=0
#service.brcm.bt.hcid_active=0
#service.brcm.fm.activation=0
#ro.rfkilldisabled=0
# from build.prop
#
# system.prop for surf
#
debug.sf.hw=1
dalvik.vm.heapsize=64m
ro.sf.lcd_density=240
#ro.dev.dmm=1
#dev.dmm.dpd.trigger_delay=30
#
# system props for the cne module
#
#persist.cne.UseCne=vendor
#persist.cne.bat.range.low.med=30
#persist.cne.bat.range.med.high=60
#persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
#persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
#persist.cne.bwbased.rat.sel=false
#persist.cne.snsr.based.rat.mgt=false
#persist.cne.bat.based.rat.mgt=false
#persist.cne.rat.acq.time.out=30000
#persist.cne.rat.acq.retry.tout=0
#
#lpa.decode=false
#ro.hdmi.enable=true
#
# system props for the data modules
#
#ro.use_data_netmgrd=true
#
# system props for SD card emulation of emmc partition
#
ro.emmc.sdcard.partition=16
#
# system props for the MM modules
#
#media.stagefright.enable-player=true
#media.stagefright.enable-meta=false
#media.stagefright.enable-scan=false
#media.stagefright.enable-http=true
#media.stagefright.enable-rtsp=false
# Samsung USB default mode
#persist.service.usb.setting=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.supplicant_scan_interval=15
#ro.secdevenc=true
dalvik.vm.dexopt-flags=m=y
#
# ADDITIONAL_BUILD_PROPERTIES
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d/dev/ttyS0
wifi.interface=eth0
ro.opengles.version=131072
ro.config.ehrpd=true
ro.telephony.ril_class=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
mobiledata.interfaces=pdp0,gprs,ppp0
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
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
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
~ #

I'm still using you'r kernel with a dead sdcard inside my phone

nail16 said:
I'm still using you'r kernel with a dead sdcard inside my phone
Click to expand...
Click to collapse
Please, don't crosspost^^ It's about the recovery (which uses not even the skyhigh kernel), and not the kernel so it's simply uuuuuuseless here

wintel_mac said:
Yep, here it is
Click to expand...
Click to collapse
OK, that's the right one, so the install routine works. Which is actually the only part that I could test on my own phone and it worked properly
A new version is already online, can you test that please ?

nail16 said:
I'm still using you'r kernel with a dead sdcard inside my phone
Click to expand...
Click to collapse
Did you read this already ?
http://forum.xda-developers.com/showpost.php?p=24307493&postcount=213

Code:
V:\Downloads>adb push sky-new-recovery.img /emmc/flash-backup/
2174 KB/s (5083136 bytes in 2.283s)
V:\Downloads>adb shell
~ # mount /emmc
mount /emmc
~ # dd if=/emmc/flash-backup/sky-new-recovery.img of=/dev/block/mmcblk0p13
dd if=/emmc/flash-backup/sky-new-recovery.img of=/dev/block/mmcblk0p13
9928+0 records in
9928+0 records out
5083136 bytes (4.8MB) copied, 2.363983 seconds, 2.0MB/s
~ #
Rebootet... went back into CWM. Rebooted once more... CWM. And just another reboot (you may guess...) CWM.
Code:
~ # cat /default.prop
cat /default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.035
237 test-keys
ro.build.version.incremental=eng.root.20120216.035237
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Thu Feb 16 04:20:00 CET 2012
ro.build.date.utc=1329362400
ro.build.type=eng
ro.build.user=root
ro.build.host=ANKObian
ro.build.tags=test-keys
ro.product.model=GT-I9001
ro.product.brand=Samsung
ro.product.name=full_galaxysplus
ro.product.device=galaxysplus
ro.product.board=qcom
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galaxysplus
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.03
5237 test-keys
ro.build.fingerprint=Samsung/full_galaxysplus/galaxysplus:2.3.7/GINGERBREAD/eng.
root.20120216.035237:eng/test-keys
ro.cm.device=galaxysplus
# end build properties
#
# system.prop for galaxysplus
#
# from init.rc
#service.brcm.bt.srv_active=0
#service.brcm.bt.hcid_active=0
#service.brcm.fm.activation=0
#ro.rfkilldisabled=0
# from build.prop
#
# system.prop for surf
#
debug.sf.hw=1
dalvik.vm.heapsize=64m
ro.sf.lcd_density=240
#ro.dev.dmm=1
#dev.dmm.dpd.trigger_delay=30
#
# system props for the cne module
#
#persist.cne.UseCne=vendor
#persist.cne.bat.range.low.med=30
#persist.cne.bat.range.med.high=60
#persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
#persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
#persist.cne.bwbased.rat.sel=false
#persist.cne.snsr.based.rat.mgt=false
#persist.cne.bat.based.rat.mgt=false
#persist.cne.rat.acq.time.out=30000
#persist.cne.rat.acq.retry.tout=0
#
#lpa.decode=false
#ro.hdmi.enable=true
#
# system props for the data modules
#
#ro.use_data_netmgrd=true
#
# system props for SD card emulation of emmc partition
#
ro.emmc.sdcard.partition=16
#
# system props for the MM modules
#
#media.stagefright.enable-player=true
#media.stagefright.enable-meta=false
#media.stagefright.enable-scan=false
#media.stagefright.enable-http=true
#media.stagefright.enable-rtsp=false
# Samsung USB default mode
#persist.service.usb.setting=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.supplicant_scan_interval=15
#ro.secdevenc=true
dalvik.vm.dexopt-flags=m=y
#
# ADDITIONAL_BUILD_PROPERTIES
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d/dev/ttyS0
wifi.interface=eth0
ro.opengles.version=131072
ro.config.ehrpd=true
ro.telephony.ril_class=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
mobiledata.interfaces=pdp0,gprs,ppp0
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
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
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
~ #

wintel_mac said:
Code:
V:\Downloads>adb push sky-new-recovery.img /emmc/flash-backup/
2174 KB/s (5083136 bytes in 2.283s)
V:\Downloads>adb shell
~ # mount /emmc
mount /emmc
~ # dd if=/emmc/flash-backup/sky-new-recovery.img of=/dev/block/mmcblk0p13
dd if=/emmc/flash-backup/sky-new-recovery.img of=/dev/block/mmcblk0p13
9928+0 records in
9928+0 records out
5083136 bytes (4.8MB) copied, 2.363983 seconds, 2.0MB/s
~ #
Rebootet... went back into CWM. Rebooted once more... CWM. And just another reboot (you may guess...) CWM.
Code:
~ # cat /default.prop
cat /default.prop
#
# ADDITIONAL_DEFAULT_PROPERTIES
#
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=GINGERBREAD
ro.build.display.id=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.035
237 test-keys
ro.build.version.incremental=eng.root.20120216.035237
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=Thu Feb 16 04:20:00 CET 2012
ro.build.date.utc=1329362400
ro.build.type=eng
ro.build.user=root
ro.build.host=ANKObian
ro.build.tags=test-keys
ro.product.model=GT-I9001
ro.product.brand=Samsung
ro.product.name=full_galaxysplus
ro.product.device=galaxysplus
ro.product.board=qcom
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=hdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7x30
# ro.build.product is obsolete; use ro.product.device
ro.build.product=galaxysplus
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=full_galaxysplus-eng 2.3.7 GINGERBREAD eng.root.20120216.03
5237 test-keys
ro.build.fingerprint=Samsung/full_galaxysplus/galaxysplus:2.3.7/GINGERBREAD/eng.
root.20120216.035237:eng/test-keys
ro.cm.device=galaxysplus
# end build properties
#
# system.prop for galaxysplus
#
# from init.rc
#service.brcm.bt.srv_active=0
#service.brcm.bt.hcid_active=0
#service.brcm.fm.activation=0
#ro.rfkilldisabled=0
# from build.prop
#
# system.prop for surf
#
debug.sf.hw=1
dalvik.vm.heapsize=64m
ro.sf.lcd_density=240
#ro.dev.dmm=1
#dev.dmm.dpd.trigger_delay=30
#
# system props for the cne module
#
#persist.cne.UseCne=vendor
#persist.cne.bat.range.low.med=30
#persist.cne.bat.range.med.high=60
#persist.cne.loc.policy.op=/system/etc/OperatorPolicy.xml
#persist.cne.loc.policy.user=/system/etc/UserPolicy.xml
#persist.cne.bwbased.rat.sel=false
#persist.cne.snsr.based.rat.mgt=false
#persist.cne.bat.based.rat.mgt=false
#persist.cne.rat.acq.time.out=30000
#persist.cne.rat.acq.retry.tout=0
#
#lpa.decode=false
#ro.hdmi.enable=true
#
# system props for the data modules
#
#ro.use_data_netmgrd=true
#
# system props for SD card emulation of emmc partition
#
ro.emmc.sdcard.partition=16
#
# system props for the MM modules
#
#media.stagefright.enable-player=true
#media.stagefright.enable-meta=false
#media.stagefright.enable-scan=false
#media.stagefright.enable-http=true
#media.stagefright.enable-rtsp=false
# Samsung USB default mode
#persist.service.usb.setting=0
#
# ADDITIONAL_BUILD_PROPERTIES
#
wifi.supplicant_scan_interval=15
#ro.secdevenc=true
dalvik.vm.dexopt-flags=m=y
#
# ADDITIONAL_BUILD_PROPERTIES
#
rild.libpath=/system/lib/libsec-ril.so
rild.libargs=-d/dev/ttyS0
wifi.interface=eth0
ro.opengles.version=131072
ro.config.ehrpd=true
ro.telephony.ril_class=samsung
ro.product.locale.language=en
ro.product.locale.region=GB
mobiledata.interfaces=pdp0,gprs,ppp0
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
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
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
~ #
Click to expand...
Click to collapse
Hm, this puzzles me a little bit and will become quite a challenge more than I thought. But I'm still confident that I will work it out soon

unable to nandroid sk4g,

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

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

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

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

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

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

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

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

Tf700 blocked in 4.4.20

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

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

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

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

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

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

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

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

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

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

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

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

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

installing rom without uninstalling anti-theft program

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

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

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

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

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

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

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

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

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

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

SM-T210R Dump // Root solved!

I m uploading a dump for the SM-T210R so we can get this thing rooted. Here is the build.prop for anyone wanting to look. Dump - http://d-h.st/zmN
Root thread in development section
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=JZO54K.T210RUEAMF1
ro.build.version.incremental=T210RUEAMF1
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Sun Jun 2 21:57:39 KST 2013
ro.build.date.utc=1370177859
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-63
ro.build.tags=release-keys
ro.product.model=SM-T210R
ro.product.brand=samsung
ro.product.name=lt02wifiue
ro.product.device=lt02wifi
ro.product.board=PXA986
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=mrvl
ro.build.PDA=T210RUEAMF1
ro.bootloader=T210RUEAMF1
ril.sw_ver=
ril.official_cscver=I8268CHNALK2
ro.build.changelist=1219080
ro.build.modelname=SM-T210R
# ro.build.product is obsolete; use ro.product.device
ro.build.product=lt02wifi
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=lt02wifiue-user 4.1.2 JZO54K T210RUEAMF1 release-keys
ro.build.fingerprint=samsung/lt02wifiue/lt02wifi:4.1.2/JZO54K/T210RUEAMF1:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# system.prop for nevocmcc
#
# System property for Default Brightness
ro.lcd_brightness=195
ro.sf.lcd_density=160
# minimum brightness value
ro.lcd_min_brightness=20
# rotation setting in potrait mode.
ro.sf.hwrotation=270
ro.kernel.qemu=0
ro.carrier=wifi-only
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=1
persist.service.blcr.enable=0
persist.sys.tools.enable=0
ro.wifi.active_roaming.enable=true
ro.tel.config.path=/system/etc/tel/
ro.sf.lcd_density=240
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.sec.fle.encryption=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.config.voip_dvfs_freq=3
ro.error.receiver.default=com.samsung.receiver.error
ro.tvout.enable=false
ro.setupwizard.mode=DISABLED
ro.com.google.apphider=off
ro.com.google.gmsversion=4.1_r5
boot.fps=9
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt

Jamison904 said:
I m uploading a dump for the SM-T210R so we can get this thing rooted. Anyone know the command to pull the recovery? I can make a CWM recovery if I can get the stock recovery. Here is the build.prop for anyone wanting to look.
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JZO54K
ro.build.display.id=JZO54K.T210RUEAMF1
ro.build.version.incremental=T210RUEAMF1
ro.build.version.sdk=16
ro.build.version.codename=REL
ro.build.version.release=4.1.2
ro.build.date=Sun Jun 2 21:57:39 KST 2013
ro.build.date.utc=1370177859
ro.build.type=user
ro.build.user=se.infra
ro.build.host=SEP-63
ro.build.tags=release-keys
ro.product.model=SM-T210R
ro.product.brand=samsung
ro.product.name=lt02wifiue
ro.product.device=lt02wifi
ro.product.board=PXA986
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product_ship=true
ro.product.manufacturer=samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=mrvl
ro.build.PDA=T210RUEAMF1
ro.bootloader=T210RUEAMF1
ril.sw_ver=
ril.official_cscver=I8268CHNALK2
ro.build.changelist=1219080
ro.build.modelname=SM-T210R
# ro.build.product is obsolete; use ro.product.device
ro.build.product=lt02wifi
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=lt02wifiue-user 4.1.2 JZO54K T210RUEAMF1 release-keys
ro.build.fingerprint=samsung/lt02wifiue/lt02wifi:4.1.2/JZO54K/T210RUEAMF1:user/release-keys
ro.build.characteristics=tablet
# end build properties
#
# system.prop for nevocmcc
#
# System property for Default Brightness
ro.lcd_brightness=195
ro.sf.lcd_density=160
# minimum brightness value
ro.lcd_min_brightness=20
# rotation setting in potrait mode.
ro.sf.hwrotation=270
ro.kernel.qemu=0
ro.carrier=wifi-only
#
# ADDITIONAL_BUILD_PROPERTIES
#
keyguard.no_require_sim=1
persist.service.blcr.enable=0
persist.sys.tools.enable=0
ro.wifi.active_roaming.enable=true
ro.tel.config.path=/system/etc/tel/
ro.sf.lcd_density=240
ro.carrier=unknown
ro.com.google.clientidbase=android-samsung
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
ro.sec.fle.encryption=true
ro.config.ringtone=S_Over_the_horizon.ogg
ro.config.notification_sound=S_Whistle.ogg
ro.config.alarm_alert=Walk_in_the_forest.ogg
ro.config.media_sound=Media_preview_Touch_the_light.ogg
ro.config.voip_dvfs_freq=3
ro.error.receiver.default=com.samsung.receiver.error
ro.tvout.enable=false
ro.setupwizard.mode=DISABLED
ro.com.google.apphider=off
ro.com.google.gmsversion=4.1_r5
boot.fps=9
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Click to expand...
Click to collapse
Could you dump the boot IMG please so that I can root it what the heck Samsung why don't you realise sources fast
Sent from my Sensation using xda app-developers app

Brain fart. What is the command line?
Dump - http://d-h.st/zmN
Code:
/system ext4 /dev/block/mmcblk0p14
/cache ext4 /dev/block/mmcblk0p15
/data ext4 /dev/block/mmcblk0p17 length=-16384
/efs ext4 /dev/block/mmcblk0p6
/misc emmc misc
/boot emmc /dev/block/mmcblk0p9
/recovery emmc /dev/block/mmcblk0p10
/bootloader emmc /dev/block/mmcblk0p5
/modem emmc /dev/block/mmcblk0p8
/sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1e
/preload ext4 /dev/block/mmcblk0p16
Code:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p10
Info for me. This is how to install a recovery through terminal straight from the tab (odin not needed.) BE VERY CAREFUL! This can really jack you up!

I just started a pull for the same thing for system. I couldn't get it out of my wife's hands until now.
Sent from my HTCONE using xda app-developers app

Yeah I am going through with draw here....lol. I can't wait to get a hold of the source so I can build my kernel. Heck I am about to build a ROM from the dump

Jamison904 said:
Yeah I am going through with draw here....lol. I can't wait to get a hold of the source so I can build my kernel. Heck I am about to build a ROM from the dump
Click to expand...
Click to collapse
I just bricked my Tab 3 installing the wrong 4.2.2 firmware... anyone know where I can download the original official Tab 3 7.0 SM-T210R firmware?

eggert82 said:
I just bricked my Tab 3 installing the wrong 4.2.2 firmware... anyone know where I can download the original official Tab 3 7.0 SM-T210R firmware?
Click to expand...
Click to collapse
umm there is no right 4.2.2 firmware yet the 7 shipped with 4.1.2 the 8 and 10 got 4.2.2 as far as a factory firmware not released yet and unless a rom can be made from the system dump your stuck waiting till the factory image gets released.

mirrin said:
umm there is no right 4.2.2 firmware yet the 7 shipped with 4.1.2 the 8 and 10 got 4.2.2 as far as a factory firmware not released yet and unless a rom can be made from the system dump your stuck waiting till the factory image gets released.
Click to expand...
Click to collapse
I'm attempting to download and install 4.1.2 australian version... if that doesn't work then I'm sure I can return it to Wal-Mart tomorrow lol

Jamison904 said:
Brain fart. What is the command line?
Dump - http://d-h.st/zmN
Click to expand...
Click to collapse
Does it include the boot.img

Lol, I won't ask if you knew the command line to pull the boot.img if it did now would I?

Jamison904 said:
Lol, I won't ask if you knew the command line to pull the boot.img if it did now would I?
Click to expand...
Click to collapse
actually the kernel source has been realsed check it here press ctrl+F and search for SM-T210
if you want to dump the boot.img it is impossible with out root sorry

Sweet. Looks like I am building a kernel before we have root

Here for those who don't want to download the source - https://github.com/jamison904/SM-T210_kernel

Jamison904 said:
Here for those who don't want to download the source - https://github.com/jamison904/SM-T210_kernel
Click to expand...
Click to collapse
Could you compile a boot.img from the source code and i will make an odin flashble file to flash a rooted rom so we can get a better idea for how the system works and define the mount points.

We still need the ram disk for the boot.img. All the source will allow for is the zimage.

Jamison904 said:
We still need the ram disk for the boot.img. All the source will allow for is the zimage.
Click to expand...
Click to collapse
Then how would we root this thing there must be an expliot ore something
---------- Post added at 06:40 PM ---------- Previous post was at 06:22 PM ----------
i actually noticed spomething in the build build.prop what is it??
Code:
ro.sec.fle.encryption=true

as far as i remember you need root to dump anything except /system. so, this wont work until you have root.
get the partition you want:
Code:
cat /proc/mounts
to pull partition:
Code:
dd if=[partition point here] of=/sdcard/[partition name here]

emwno said:
as far as i remember you need root to dump anything except /system. so, this wont work until you have root.
get the partition you want:
Code:
cat /proc/mounts
to pull partition:
Code:
dd if=[partition point here] of=/sdcard/[partition name here]
Click to expand...
Click to collapse
Yeah you are right but we need the boot img at least the recovery.img ???

mythi said:
Yeah you are right but we need the boot img at least the recovery.img ???
Click to expand...
Click to collapse
Im getting it for the tab 7.0 and 8.0 (recovery and ramdisks), as well as im working on root for it. will post, when i have something.
---------- Post added at 07:01 PM ---------- Previous post was at 06:44 PM ----------
Anyone have a galaxy tab 8.0 (SM-T310 just to be safe), i may have a working root solution for it.

emwno said:
Im getting it for the tab 7.0 and 8.0 (recovery and ramdisks), as well as im working on root for it. will post, when i have something.
---------- Post added at 07:01 PM ---------- Previous post was at 06:44 PM ----------
Anyone have a galaxy tab 8.0 (SM-T310 just to be safe), i may have a working root solution for it.
Click to expand...
Click to collapse
Well actually no we are trying to root the 7.0 version i think no one intrested in 8.0 and 10.1