Related
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
Hey everybody
After applying the Changes in the Build.prop in this thread http://forum.xda-developers.com/showthread.php?t=1758160 and restarted the transformer, I got a Bootloop.
I tried to cold boot it up (holding both volume buttons), but it just shows me an opened Android Figure with a red warning sign.
EDIT: https://www.dropbox.com/s/ryoee7a6irjtn76/2012-07-09 14.19.38.jpg
What can I do now to boot up my Tablet.
Thank you for any helping advice.
Here is my build.prop:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.WW_epad-9.4.5.21-20120601
ro.build.version.incremental=WW_epad-9.4.5.21-20120601
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jun 1 16:39:06 CST 2012
ro.build.date.utc=1338539946
ro.build.type=user
ro.build.user=
ro.build.host=Mars
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.21-20120601 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.0.3/IML74K/WW_epad-9.4.5.21-20120601: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=300
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r1
ro.com.google.clientidbase=android-asus
ro.com.google.mcc_fallback=262
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=v,o=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
#Added Lines
debug.sf.hw=1
persist.sys.ui.hw=1
ro.ril.disable.power.collapse=1
pm.sleep_mode=1
wifi.supplicant_scan_interval=180
debug.performance.tuning=1
video.accelerate.hw=1
ro.max.fling_velocity=12000
ro.min.fling_velocity=8000
media.stagefright.enable-player=true
media.stagefright.enable-meta=true
media.stagefright.enable-scan=false
media.stagefright.enable-http=true
net.tcp.buffersize.default=4096,87380,256960,4096, 16384,256960
net.tcp.buffersize.wifi=4096,87380,256960,4096,163 84,256960
ro.config.nocheckin=1
persist.adb.notify=0
ro.kernel.android.checkjni=0
ro.kernel.checkjni=0
ro.HOME_APP_ADJ=1
Sorry to hear that, the tweaks worked fine for me. You can try pushing files through adb, try getting your old build.prop to work. If not, factory reset the device.
This might be helpful (follow carefully): http://droidmodderx.com/prime/?page_id=74
Thanks for your answer.
I managed it now to use adb to connect to my device.
But I can't change the /system to r/w.
Here's the console log of the commands su and mount.
Code:
[email protected]:/system $ chmod 777 build.prop
chmod 777 build.prop
Unable to chmod build.prop: Read-only file system
10|[email protected]:/system $ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /
system
ffs2 /dev/block/mtdblock3 /system <
mount: Operation not permitted
255|[email protected]:/system $ su
su
Segmentation fault
139|[email protected]:/system $ mount -o rw,remount -t yaffs2 /dev/block/mtdblock3
/system
affs2 /dev/block/mtdblock3 /system <
mount: Operation not permitted
255|[email protected]:/system $
EDIT: I just found out with the adb that my build.prop was empty.
Now I try to Download via adb my data and afterwards I will try to factory reset the device.
EDIT2: I heard with busybox I can use my root rights with adb. Could I just install the busybox app?
Or can I use the Bootloader unlock tool for the asus transformer prime to unlock my root rights on the adb?
Perhaps you missed something while replacing the files? It shouldn't be empty even if something didn't work.
The unlocking tool probably won't work.
I'm not sure why remounting it R/W didn't work either. Try again any of these:
adb shell mount -o remount,rw /system
or
mount -o rw,remount /dev/block/mmcblk0p1 /system
(I'm not sure why you've inserted /dev/block/mtdblock3 there? adb guide for a different device maybe?)
and then push your desired build.prop
I tried both, but it showed me "Operation not permitted"
Any other Ideas?
Nahakiole said:
I tried both, but it showed me "Operation not permitted"
Any other Ideas?
Click to expand...
Click to collapse
None. Hard reset it and be sure not to place an empty or faulty build.prop directly on /system partition next time! Now you know what it leads to
How can I do that?
I don't find anything when searching for a hard reset for the infinity.
Is it as the same, as on the prime? (Holding the Power on and Low Audio Button)?
Somehow I do experience problems with turning the infinity on, sometimes it doesn't turns on after pushing the power button.
Nahakiole said:
How can I do that?
I don't find anything when searching for a hard reset for the infinity.
Is it as the same, as on the prime? (Holding the Power on and Low Audio Button)?
Somehow I do experience problems with turning the infinity on, sometimes it doesn't turns on after pushing the power button.
Click to expand...
Click to collapse
1. Hold volume down & power button.
2. Release power button after it starts booting.
3. Release power down and press volume up after seeing some white text in the top left corner of the screen.
4. Press power button and you'll have the options you can navigate through by pressing volume buttons (volume down x2 + power button = factory reset).
Good luck! And hope you'll be able to do these tweaks next time.
Tell us how it went.
I did now the Factory reset, but my transformer still won't boot up.
Any other chance of recovery?
Or do I have to send it in?
EDIT: Could I somehow flash the Original Firmware? Or something alike that?
Do I still have root rights after doing a factory reset?
When I connect to the transformer via adb and try to use su or sudo it doesn't work?
Code:
255|[email protected]:/system $ su
su
Segmentation fault
EDIT2:
Now I can't even connect via adb to the transformer.
My Windows 7 64 Bit PC tries to install the drivers and gives me "error 10 can't start the device".
I am no specialist in adb, so not sure about the su results there (try to Google it @xda), but after doing the factory reset you should not have root anymore, so sending it back should be safer than before the reset.
I don't think there's already original firmware out there to download, apart from the source code being available at ASUS's website.
Sorry it didn't work for you, I'm not sure why. You can try sending it to ASUS.
If adb did work, I would consider installing an update from a zip file consisting of the old build.prop, but it will be safer for you to send it back I guess (we can't even be sure this was the original reason it didn't boot).
Okay thanks for your Help. I will go today to the shop where I bought it and will try to get a new one or a refound.
I will update this post as soon as I will be back from the Shop.
EDIT: I will get a new one without the Dock in about two Days and the Dock will be shipped in mid july.
Thank you for your Help d14b0ll0s.
EDIT2: For the next time, how could I make use of root on adb? Is there a Programm within I could activate this? So I could simply put in my Backup from my Computer?
--> For future reference see firmware update method from http://forum.xda-developers.com/showpost.php?p=28597763&postcount=17
Hi Guys,
I need someone who can build or compile TWRP 2.4.3.0 Recovery For Funbook P275.
Please Tell me All the Files You Need, I can provide you...
Any developer who wants to help me, please leave a comment here or PM me...
Device Details:
Name : Funbook Infinity P275 (7" Tablet)
Type : Allwinner A13 Based Device
Resolution : 800 x 480
ClockWorkMod Recovery Image : http://www.mediafire.com/?5ppe0tgxkgiqi1x
recovery.fstab
Code:
mount point fstype device
/boot emmc /dev/block/nandc
/cache ext4 /dev/block/nandh
/data ext4 /dev/block/nande
/emmc auto /dev/block/nandi /dev/block/nandi1
/sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
/sd-ext auto /dev/block/mmcblk0p2
/system ext4 /dev/block/nandd
/recovery emmc /dev/block/nandg
Build.prop
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IMM76D
ro.build.display.id=Infinite Rom
ro.build.version.incremental=20120910
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Tue Aug 14 14:30:02 CST 2012
ro.build.date.utc=1344925802
ro.build.type=user
ro.build.user=root
ro.build.host=
ro.build.tags=test-keys
ro.product.model=Micromax P275
ro.product.brand=softwinners
ro.product.name=P275
ro.product.device=nuclear-t03
ro.product.board=nuclear
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.board.platform=exDroid
# ro.build.product is obsolete; use ro.product.device
ro.build.product=nuclear-t03
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=nuclear_t03-user 4.0.4 IMM76D 20120907 test-keys
ro.build.fingerprint=softwinners/nuclear_t03/nuclear-t03:4.0.4/IMM76D/20120907:user/test-keys
ro.build.characteristics=tablet
# end build properties
Please inform if anything else is needed for building/compiling TWRP Reocery...
I want to help u, well i have funbook pro but still!!!!!
funbook infinity works with all modems
---------- Post added at 08:32 PM ---------- Previous post was at 08:28 PM ----------
download ppp widget app for dongle support
Built recovery
Hey guys I have Lyf wind 3 and no official custom recovery is available for my device can u built one for me
Bro in xda developer any person is willing to teach how to create twrp recovery for beginners and don't know how to do like me
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
Hello
Is it possible that technipad (of technisat) to root? It is built a rockchip.
Thank you
Philip
Me too
Also trying to root this device. Tried many ways but cannot get through.
ADB root does not work - adbd cannot run as root in production builds
though adb shell get similar message as uid 2000 - cannot change to 0
Cannot use psneuter either.
Going round and round in circles, anyone with some help it would be appreciated.
Thanks,
Root checker results
Root Access is not properly configured or was not granted.
Super User Application Status:
SuperSU application - version 1.51 - is installed!
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: -rwsr-sr-x root root 62932 2013-05-10 12:41 su
Analysis: Setuid attribute is present and root user ownership is present. Root access is correctly configured for this file! Executing this file can grant root access!
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
Results provided on your TechniPad 8 device by Root Checker Pro version 1.3.4 from joeykrim in the Android Market
Hello,
Have you found anything?
mfG
Philip
philidinator said:
Hello,
Have you found anything?
mfG
Philip
Click to expand...
Click to collapse
Nothing yet am afraid. It's a bit confusing at the device seems to think it is already rooted, but it isn't when you check for root capability. Am going to try something today - but it might end up making it a lovely paperweight. Will keep you posted.
Nothing new?
mfG
Philip
Rooted Technipad 8
philidinator said:
Nothing new?
mfG
Philip
Click to expand...
Click to collapse
SUCCESS!!
FOLLOW THE INSTRUCTIONS HERE AND ROOT ACCESS IS GRANTED - NOW TO FIND A CUSTOM ROM AND UPGRADE TO JB 4.2
JUST ROOTED MY TECHNIPAD 8 SO IF YOU NEED ANY HELP JUST ASK BUT THE INTRSUCTIONS WERE PRETTY SIMPLE TO FOLLOW.
GOOD LUCK! :good:
http://forum.xda-developers.com/showthread.php?t=2414994
I have a Technipad 10 and the rooting instructions mentioned above did not work unfortunately. Is anybody out there who know a possibilty to root this tablet?
For a little help, I would be very grateful.
Try this one:
https://github.com/Lostech/Root_Box/tree/V1.0
https://github.com/Lostech/Root_Box/archive/V1.0.zip
I made this based on other RK30 root´s for the TechniPad 10G with Android version 4.1.1 and build version GE.Technisat.S10_g.V107.
Calibaan said:
I made this based on other RK30 root´s for the TechniPad 10G with Android version 4.1.1 and build version GE.Technisat.S10_g.V107.
Click to expand...
Click to collapse
Hello Calibaan,
I’m thrilled, your program did work really well.
Thank you very much and have a nice weekend!
Technipad 7T
Hi,
i own a Technipad 7T and try to root it with Rootbox V1.1, but it wont work.
It has Android V4.2.2.
Any ideas why it wont work?
At which point does the root process fail?
I found Version 1.6 of root_box. but still no luck.
I use WinXp. Driver installation failed inside of root_box, so I installed the seperatly.
I failed doing the root.
Su was transfered to the root-dir.
After that I got a lot of "system/bin/su: rksu: not found" and "system/bin/su: suu: not found" and the Technipad is doing a reset.
But there is still no root-access or superuser installed.
Android-Info:
================
AndroidInfo V1.1
================
build.prop Inhalt:
------------------
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=JDQ39
ro.build.display.id=GE.TechniPad.V1.07
ro.build.version.incremental=20140514
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Wed May 14 10:36:07 CST 2014
ro.build.date.utc=1400034967
ro.build.type=user
ro.build.user=liuyang
ro.build.host=swubuntu
ro.build.tags=test-keys
ro.product.model=TechniPad_7T
ro.product.brand=MID
ro.product.name=TPad_7T
ro.product.device=TechniPad_7T
ro.product.board=TPad_7T
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=TechniSat
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=13
ro.board.platform=meson6
# ro.build.product is obsolete; use ro.product.device
ro.build.product=TPad_7T
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=g17refm170m-user 4.2.2 JDQ39 20140514 test-keys
ro.build.fingerprint=MID/g17refm170m/g17refm170m:4.2.2/JDQ39/20140514:user/test-keys
ro.build.characteristics=tablet,nosdcard
# end build properties
ro.sf.lcd_density=160
keyguard.no_require_sim=1
#set keyguard.enable=false to disable keyguard
keyguard.enable=true
ro.statusbar.widget=true
ro.statusbar.button=true
ro.statusbar.yearmonthdayweek=true
# Time between scans in seconds. Keep it high to minimize battery drain.
# This only affects the case in which there are remembered access points,
# but none are in range.
#wifi.supplicant_scan_interval = 60
#alsa.mixer.playback.master=DAC2 Analog
#alsa.mixer.capture.master=Analog
hwui.render_dirty_regions=false
# Disable un-supported Android feature
hw.nopm=false
hw.nobattery=false
hw.nophone=false
hw.novibrate=true
hw.hasethernet=true
#hw.hasdata=true
ro.platform.has.touch=true
#set to 0 temporarily so touch works without other changes
ro.sf.hwrotation=0
# Use OSD2 mouse patch
ro.ui.cursor=osd2
ro.hardware=amlogic
sys.fb.bits=32
# Disable GPS
gps.enable=true
# Enable player buildin
media.amsuperplayer.enable=true
media.amplayer.enable-acodecs=ape,flac,dts
media.amplayer.enable=true
media.amsuperplayer.m4aplayer=STAGEFRIGHT_PLAYER
media.amsuperplayer.defplayer=PV_PLAYER
media.amplayer.thumbnail=true
#media.amplayer.widevineenable=true
media.amplayer.startmode=true
media.arm.audio.decoder=ape,ac3,eac3
# Nand write need force sync when gadget
gadget.nand.force_sync=true
# Status bar customization
ro.statusbar.widget.power=true
ro.statusbar.yearmonthdayweek=true
#support rotation btn for apk compatibility,set true btn useful
sys.rotation.settings=false
# HDMI
ro.hdmi480p.enable=false
#rw.fb.need2xscale=ok
#media.amplayer.osd2xenable=true
#Configure the dtv standard, can only be DVB,ATSC
dtv.standard=DVB
dtv.deinterlace.disable=true
dtv.transmission=3
audio.policy.digital.fixed=false
# App optimization
ro.app.optimization=true
#Dual display
ro.vout.dualdisplay3=true
ro.vout.player.exit=false
# CPU settings
ro.has.cpu.setting=true
# CPU freq customized in setting menu
# normal, performance, powersaving
ro.cpumode.maxfreq=1200000,1512000,800000
# when usbstorage, CPU mode and freq
ro.usbstorage.cpumode=performance
ro.usbstorage.maxfreq=600000
#ro.bootanimation.rotation=180
persist.service.adb.enable=0
#used to set default surface size, set 1 when hwrotation is 270, set 3 when hwrotation is 90;need set ro.bootanimation.rotation 0;
#debug.default.dimention=1
#support media poll uevent,can use sd cardread on usb port
#has.media.poll=false
has.media.poll=true
#used forward seek for libplayer
media.libplayer.seek.fwdsearch=1
#enable address bar cover issue fixing
ro.flashplayer.surfacehack=1
#fix hls sync
libplayer.livets.softdemux=1
libplayer.netts.recalcpts=1
#map volume
ro.audio.mapvalue=0,0,0,0
ro.media.partition.label=TechniPad7T
hw.has.bluetooth=true
#screenshot icon in status bar
ro.statusbar.screenshot=true
#vol + - icon in status bar
ro.statusbar.volume=true
#set HDMI ratation
#hdmi.hdmirotation=2
#systemui interval
rw.systemui.interval=40
media.libplayer.modules=vhls_mod
#for tabletui display
#ro.ui.tabletui=true
#skyworth Modify default language/country/timezone.
persist.sys.timezone=Europe/Berlin
persist.sys.language=de
persist.sys.country=De
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.carrier=unknown
ro.opengles.version=131072
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=384m
dalvik.vm.heaptargetutilization=0.75
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=8m
wifi.interface=wlan0
gps.enable=false
hw.cameras=2
ro.camera.orientation.front=270
ro.camera.orientation.back=90
rw.sensors.gsensor.installdir=0110
ro.app.optimization=true
drm.service.enable=true
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
/bin Verzeichnis:
------------------------
/bin//bin: No such file or directory
/sbin Verzeichnis:
-------------------------
/sbin/opendir failed, Permission denied
/xbin Verzeichnis:
------------------------
/xbin//xbin: No such file or directory
/system/bin Verzeichnis:
------------------------
/system/bin/AmlHostsTool
/system/bin/abcc
/system/bin/adb
/system/bin/am
/system/bin/app_process
/system/bin/applypatch
/system/bin/atrace
/system/bin/bmgr
/system/bin/bootanimation
/system/bin/bu
/system/bin/bugreport
/system/bin/cat
/system/bin/chat
/system/bin/chmod
/system/bin/chown
/system/bin/cmp
/system/bin/content
/system/bin/cp
/system/bin/curl
/system/bin/dalvikvm
/system/bin/date
/system/bin/dbus-daemon
/system/bin/dd
/system/bin/debuggerd
/system/bin/dexopt
/system/bin/df
/system/bin/dhcpcd
/system/bin/dhd
/system/bin/dig
/system/bin/dmesg
/system/bin/dnsmasq
/system/bin/drmserver
/system/bin/du
/system/bin/dumpstate
/system/bin/dumpsys
/system/bin/fsck.exfat
/system/bin/fsck_msdos
/system/bin/getevent
/system/bin/getprop
/system/bin/glgps
/system/bin/grep
/system/bin/gzip
/system/bin/hd
/system/bin/hostapd
/system/bin/id
/system/bin/ifconfig
/system/bin/iftop
/system/bin/ime
/system/bin/init-pppd.sh
/system/bin/input
/system/bin/insmod
/system/bin/installd
/system/bin/ioctl
/system/bin/ionice
/system/bin/ip
/system/bin/ip6tables
/system/bin/iptables
/system/bin/keystore
/system/bin/kill
/system/bin/linker
/system/bin/ln
/system/bin/log
/system/bin/logcat
/system/bin/logwrapper
/system/bin/ls
/system/bin/lsmod
/system/bin/lsof
/system/bin/make_ext4fs
/system/bin/md5
/system/bin/mdnsd
/system/bin/mediaserver
/system/bin/mkdir
/system/bin/mksh
/system/bin/monkey
/system/bin/mount
/system/bin/mount.exfat
/system/bin/mtpd
/system/bin/mv
/system/bin/nandread
/system/bin/ndc
/system/bin/netcfg
/system/bin/netd
/system/bin/netstat
/system/bin/newfs_msdos
/system/bin/notify
/system/bin/ntfs-3g
/system/bin/ping
/system/bin/pm
/system/bin/pppd
/system/bin/printenv
/system/bin/ps
/system/bin/racoon
/system/bin/reboot
/system/bin/renice
/system/bin/requestsync
/system/bin/rild
/system/bin/rm
/system/bin/rmdir
/system/bin/rmmod
/system/bin/route
/system/bin/run-as
/system/bin/schedtest
/system/bin/schedtop
/system/bin/screencap
/system/bin/screenshot
/system/bin/sdcard
/system/bin/sendevent
/system/bin/sensorcalibrate
/system/bin/sensorservice
/system/bin/service
/system/bin/servicemanager
/system/bin/set_display_mode.sh
/system/bin/setconsole
/system/bin/setprop
/system/bin/settings
/system/bin/setup_fs
/system/bin/sh
/system/bin/sky_remount
/system/bin/sky_sudo
/system/bin/sleep
/system/bin/smd
/system/bin/start
/system/bin/stop
/system/bin/surfaceflinger
/system/bin/svc
/system/bin/sync
/system/bin/system_key_server
/system/bin/system_server
/system/bin/tc
/system/bin/tinycap
/system/bin/tinymix
/system/bin/tinyplay
/system/bin/toolbox
/system/bin/top
/system/bin/touch
/system/bin/uiautomator
/system/bin/umount
/system/bin/uptime
/system/bin/usb_modeswitch
/system/bin/usbpower
/system/bin/usbtestpm
/system/bin/vdc
/system/bin/vmstat
/system/bin/vold
/system/bin/watchprops
/system/bin/wififix.sh
/system/bin/wipe
/system/bin/wl
/system/bin/wpa_supplicant
/system/sbin Verzeichnis:
-------------------------
/system/sbin//system/sbin: No such file or directory
/system/xbin Verzeichnis:
------------------------
/system/xbin/[
/system/xbin/[[
/system/xbin/adjtimex
/system/xbin/arp
/system/xbin/ash
/system/xbin/awk
/system/xbin/base64
/system/xbin/basename
/system/xbin/bbconfig
/system/xbin/blkid
/system/xbin/blockdev
/system/xbin/brctl
/system/xbin/bunzip2
/system/xbin/busybox
/system/xbin/bzcat
/system/xbin/bzip2
/system/xbin/cal
/system/xbin/cat
/system/xbin/catv
/system/xbin/chattr
/system/xbin/chgrp
/system/xbin/chmod
/system/xbin/chown
/system/xbin/chroot
/system/xbin/clear
/system/xbin/cmp
/system/xbin/comm
/system/xbin/cp
/system/xbin/cpio
/system/xbin/crond
/system/xbin/crontab
/system/xbin/cut
/system/xbin/date
/system/xbin/dc
/system/xbin/dd
/system/xbin/depmod
/system/xbin/devmem
/system/xbin/dexdump
/system/xbin/df
/system/xbin/diff
/system/xbin/dirname
/system/xbin/dmesg
/system/xbin/dnsd
/system/xbin/dos2unix
/system/xbin/du
/system/xbin/echo
/system/xbin/ed
/system/xbin/egrep
/system/xbin/env
/system/xbin/expand
/system/xbin/expr
/system/xbin/false
/system/xbin/fbset
/system/xbin/fbsplash
/system/xbin/fdisk
/system/xbin/fgrep
/system/xbin/find
/system/xbin/flash_lock
/system/xbin/flash_unlock
/system/xbin/flashcp
/system/xbin/flock
/system/xbin/fold
/system/xbin/free
/system/xbin/freeramdisk
/system/xbin/fstrim
/system/xbin/fsync
/system/xbin/ftpget
/system/xbin/ftpput
/system/xbin/fuser
/system/xbin/getopt
/system/xbin/grep
/system/xbin/groups
/system/xbin/gunzip
/system/xbin/gzip
/system/xbin/halt
/system/xbin/head
/system/xbin/hexdump
/system/xbin/id
/system/xbin/ifconfig
/system/xbin/inetd
/system/xbin/insmod
/system/xbin/install
/system/xbin/ionice
/system/xbin/iostat
/system/xbin/ip
/system/xbin/kill
/system/xbin/killall
/system/xbin/killall5
/system/xbin/less
/system/xbin/ln
/system/xbin/losetup
/system/xbin/ls
/system/xbin/lsattr
/system/xbin/lsmod
/system/xbin/lsof
/system/xbin/lsusb
/system/xbin/lzcat
/system/xbin/lzma
/system/xbin/lzop
/system/xbin/lzopcat
/system/xbin/man
/system/xbin/md5sum
/system/xbin/mesg
/system/xbin/mkdir
/system/xbin/mkdosfs
/system/xbin/mke2fs
/system/xbin/mkfifo
/system/xbin/mkfs.ext2
/system/xbin/mkfs.vfat
/system/xbin/mknod
/system/xbin/mkswap
/system/xbin/mktemp
/system/xbin/modinfo
/system/xbin/modprobe
/system/xbin/more
/system/xbin/mount
/system/xbin/mountpoint
/system/xbin/mpstat
/system/xbin/mv
/system/xbin/nanddump
/system/xbin/nandwrite
/system/xbin/nbd-client
/system/xbin/netstat
/system/xbin/nice
/system/xbin/nohup
/system/xbin/nslookup
/system/xbin/ntpd
/system/xbin/od
/system/xbin/patch
/system/xbin/pgrep
/system/xbin/pidof
/system/xbin/ping
/system/xbin/pipe_progress
/system/xbin/pkill
/system/xbin/pmap
/system/xbin/poweroff
/system/xbin/printenv
/system/xbin/printf
/system/xbin/ps
/system/xbin/pstree
/system/xbin/pwd
/system/xbin/pwdx
/system/xbin/rdev
/system/xbin/readlink
/system/xbin/realpath
/system/xbin/reboot
/system/xbin/renice
/system/xbin/reset
/system/xbin/resize
/system/xbin/rev
/system/xbin/rm
/system/xbin/rmdir
/system/xbin/rmmod
/system/xbin/route
/system/xbin/run-parts
/system/xbin/rx
/system/xbin/sed
/system/xbin/seq
/system/xbin/setconsole
/system/xbin/setserial
/system/xbin/setsid
/system/xbin/sh
/system/xbin/sha1sum
/system/xbin/sha256sum
/system/xbin/sha3sum
/system/xbin/sha512sum
/system/xbin/sleep
/system/xbin/sort
/system/xbin/split
/system/xbin/stat
/system/xbin/strings
/system/xbin/stty
/system/xbin/sum
/system/xbin/swapoff
/system/xbin/swapon
/system/xbin/sync
/system/xbin/sysctl
/system/xbin/tac
/system/xbin/tail
/system/xbin/tar
/system/xbin/taskset
/system/xbin/tee
/system/xbin/telnet
/system/xbin/telnetd
/system/xbin/test
/system/xbin/tftp
/system/xbin/tftpd
/system/xbin/time
/system/xbin/timeout
/system/xbin/top
/system/xbin/touch
/system/xbin/tr
/system/xbin/traceroute
/system/xbin/true
/system/xbin/ttysize
/system/xbin/tune2fs
/system/xbin/umount
/system/xbin/uname
/system/xbin/uncompress
/system/xbin/unexpand
/system/xbin/uniq
/system/xbin/unix2dos
/system/xbin/unlzma
/system/xbin/unlzop
/system/xbin/unxz
/system/xbin/unzip
/system/xbin/uptime
/system/xbin/usleep
/system/xbin/uudecode
/system/xbin/uuencode
/system/xbin/vi
/system/xbin/watch
/system/xbin/wc
/system/xbin/wget
/system/xbin/whoami
/system/xbin/xargs
/system/xbin/xz
/system/xbin/xzcat
/system/xbin/yes
/system/xbin/zcat
Potentielle SuperUser Dateien:
------------------------------
/system/bin/surfaceflinger -> (su)rfaceflinger
/system/xbin/sum -> (su)m
You´re using the "T" Variant of the TechniPad which is different to the regular TechniPad´s. I didn´t have one of these but it seems that the regular Rockchip root for Android 4.1/4.2 does not work on this variant like on the other TechniPads. But since you do have Android V4.2.2 installed there is still the chance that rooting is possible with the TowelRoot method (menu entry 3 within the RootBox 1.6 or take the APK from the original TowelRoot creator GeoHot @ https://towelroot.com/). So I assume to give TowelRoot a try.
I tried Towelroot but still no luck. Startet it, make it rain and it shows "this phone isnt currently supported".
It seems that this TechniPad model is very different to the other models and I have no clue what could work for it. So in this case I can´t help you any further, sorry.
Thanx for your help.