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
[HOWTO] Manually updating firmware using "dlpkgfile" download via Asus FOTA server
FOTA UPDATE version 9.4.5.26-20120720 is known to provide improvements and fixes to address I/O issues, and MicroSD U-1 card compatibility.
Based on the original post here:
http://forum.xda-developers.com/showpost.php?p=29485094&postcount=58
Thanks to Lufterfischer for discovery, and jtrosky for testing it!
Here's the summary of what's needed to manually update using the patch file "dlpkgfile".
This is merely a documentation to help TF700 users to over come their IO problems by manually updating to FOTA version 9.4.5.26-20120720.
A short history of: OTA update happened briefly on 28/7/2012 and became unavailable to owners of TF700 tablet.
Before you start make sure your tablet is charged fully.
Disclaimer: I'm not responsible for whatever you are going to do or did to your tablet.
For those who have unlocked bootloader and custom recovery you can try this method of restoring your stock recovery by copying the blob image back to /staging on device /dev/block/mmcblk0p4
Follow the howto in the following link.
http://forum.xda-developers.com/showthread.php?t=1492887
Prerequisite
1. root
2. a copy of dlpkgfile for correct firmware version
3. a correct firmware installed on the device (9.4.5.22-20120615) for patching
4. unmodified build.prop as some has reported it was the cause for update failure.
5. make sure you don't have any of the existing files under /system modified
Here are the steps:
1. use root explorer to copy "dlpkgfile" into /cache/ directory.
Alternatively you could save the "dlpkgfile" in a microSD then open up a adb shell session.
Type:
su
cat /Removable/MicroSD/dlpkgfile > /cache/dlpkgfile
2. create the file called "command" under /cache/recovery/ directory.
3. write this statement in the file /cache/recovery/command (without qoutes) "--update_package=/cache/dlpkgfile"
Or you can just use the attached file "command" and
cat /Removable/MicroSD/command > /cache/recovery/command
Note: remove MicroSD before this last step.
4. finally reboot into recovery kernel by shutting down first, then press and hold "Volume down" + "Power" once it vibrates release "Power" keep holding "Volume down" until there are some text shown on the boot logo screen. Then press "Volume up" within 5 seconds after releasing "Volume down".
The update process should start... wait for it to complete.
Once it completes, you should have the updated firmware installed on your tablet.
Reference:
US version patch "dlpkgfile" can be found here -> http://forum.xda-developers.com/showthread.php?t=1801756
md5sum for this file is 2ff06463b57226ac910ac642781c5290
If you have received the FOTA update already and haven't updated the firmware and you have root access to your WW, JP, TW, CN version TF700 tablet.
Could you please pull or copy the /cache/dlpkgfile and upload it to your dropbox for backup and please do provide a link for other users to download, Thanks!
********************************************************************************************************
For whatever reason: eg, you disliked the updated firmware
To revert back to firmware version 9.4.5.22-20120615
Extract the blob file from zip within "**epad_user_9_4_5_22_UpdateLauncher.zip" and save
it to a MicroSD
Simply launch the following command under adb shell as root:
Code:
dd if=/Removable/MicroSD/blob of=/dev/block/mmcblk0p4
Then wait patiently for the process to complete once it finish you will see some output as
follows and it returns to the root shell prompt:
1596712+1 records in
1596712+1 records out
817516935 bytes transferred in 383.960 secs (2129172 bytes/sec)
[email protected]:/ #
Click to expand...
Click to collapse
Now reboot the device, the downgrade process should automatically start!
Just do a factory reset after that !!
Note: Camera and Touch panel firmware can't be downgraded and will stay up-to-date.
********************************************************************************************************
would this work if I have a custom recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
tbogunro said:
would this work if I have a custom recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
No... I'm waiting too.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
tbogunro said:
would this work if I have a custom recovery?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
It's best to flash recovery back to stock, no point having customer recovery installed right now as there isn't any custom ROM available for TF700 yet.
You're right, but how would I do that?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
tbogunro said:
You're right, but how would I do that?
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
What is the firmware version (US?) of your tablet ?
Maybe you can try this -> http://forum.xda-developers.com/showthread.php?t=1492887
Don't do it if you aren't confident enough otherwise you'll risk bricking your device.
It was originally a US based firmware, but I patched it to a now currently WW 9.4.5.22
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
When it says tocreate thecommand file, is it a text file what is the file extension?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
teknomanelvis said:
When it says tocreate thecommand file, is it a text file what is the file extension?
Sent from my ASUS Transformer Pad TF700T using xda app-developers app
Click to expand...
Click to collapse
it's just a file named "command" without any extension.
Redefined301 said:
What is the firmware version (US?) of your tablet ?
Maybe you can try this -> http://forum.xda-developers.com/showthread.php?t=1492887
Don't do it if you aren't confident enough otherwise you'll risk bricking your device.
Click to expand...
Click to collapse
Thanks for your help, but I'm not going to risk it lol
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Redefined301 said:
It's best to flash recovery back to stock, no point having customer recovery installed right now as there isn't any custom ROM available for TF700 yet.
Click to expand...
Click to collapse
To my knowledge u can't go back to stock recovery.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
As far as I know from TF201, you can't flash the stock OTA if you unlocked your bootloader.
Althoug I must confess, that I've forgotten the background & reasons for that
newellj79 said:
To my knowledge u can't go back to stock recovery.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
OK, I took the risk...
Using the info here: http://forum.xda-developers.com/showthread.php?t=1492887
I was able to grab the blob from the .22 update and restore the stock recovery. My device is still unlocked, but has the stock recovery reinstalled. Using the info from the OP, I was able to successfully apply the OTA to .26
I'll write up a quick how to from start to finish.
newellj79 said:
To my knowledge u can't go back to stock recovery.
Sent from my ASUS Transformer Pad TF700T using Tapatalk 2
Click to expand...
Click to collapse
Someone just reverted back to stock recovery.
eoh7678 said:
OK, I took the risk...
Using the info here: http://forum.xda-developers.com/showthread.php?t=1492887
I was able to grab the blob from the .22 update and restore the stock recovery. My device is still unlocked, but has the stock recovery reinstalled. Using the info from the OP, I was able to successfully apply the OTA to .26
I'll write up a quick how to from start to finish.
Click to expand...
Click to collapse
Yeah it will definitely work as long as you don't make a typo doing dd..
So that's interesting ... Did you flashed to stock recovery from customer recovery? Or was it simply unlocked?
Does anyone have a stock build.prop file, here is mine?
Code:
127|[email protected]:/system $ cat build.prop
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.US_epad-9.4.5.22-20120615
ro.build.version.incremental=US_epad-9.4.5.22-20120615
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jun 15 19:13:51 CST 2012
ro.build.date.utc=1339758831
ro.build.type=user
ro.build.user=
ro.build.host=Mercury
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=US_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=EeePad
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.4.5.22-20120615 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
persist.tegra.nvmmlite = 1
#NFC
debug.nfc.fw_download=false
debug.nfc.se=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
wifi.version.driver=V6.1.38
gps.version.driver=V6.9.18
keyguard.no_require_sim=true
ro.kernel.qemu=
bt.version.driver=V9.32
windowsmgr.max_events_per_sec=200
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r2
ro.com.google.clientidbase=android-asus
ro.wifi.country=US
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
I have tried doing this and still get the dead android with the following last_log:
Code:
[email protected]:/cache/recovery # cat last_log
Starting recovery on Sun Jul 29 12:13:20 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1920 x 1200)
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /system ext4 /dev/block/mmcblk0p1 (null) 0
2 /cache ext4 /dev/block/mmcblk0p2 (null) 0
3 /misc emmc /dev/block/mmcblk0p3 (null) 0
4 /boot emmc boot (null) 0
5 /recovery emmc recovery (null) 0
6 /staging ext3 /dev/block/mmcblk0p4 (null) 0
7 /btmac vfat /dev/block/mmcblk0p5 (null) 0
8 /data ext4 /dev/block/mmcblk0p8 (null) -32768
9 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
I:Got arguments from /cache/recovery/command
Command: "/sbin/recovery" "--update_package=/cache/dlpkgfile"
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=0
persist.sys.usb.config=mtp,adb
ro.build.id=IML74K
ro.build.display.id=IML74K.US_epad-9.4.5.22-20120615
ro.build.version.incremental=US_epad-9.4.5.22-20120615
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jun 15 19:13:51 CST 2012
ro.build.date.utc=1339758831
ro.build.type=user
ro.build.user=
ro.build.host=Mercury
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=US_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
ro.build.product=EeePad
ro.build.description=US_epad-user 4.0.3 IML74K US_epad-9.4.5.22-20120615 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.0.3/IML74K/US_epad-9.4.5.22-20120615:user/release-keys
ro.build.characteristics=tablet
ro.opengles.version=131072
wifi.interface=wlan0
persist.tegra.nvmmlite=1
debug.nfc.fw_download=false
debug.nfc.se=false
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=64m
dalvik.vm.heapsize=256m
wifi.version.driver=V6.1.38
gps.version.driver=V6.9.18
keyguard.no_require_sim=true
ro.kernel.qemu=
bt.version.driver=V9.32
windowsmgr.max_events_per_sec=200
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r2
ro.com.google.clientidbase=android-asus
ro.wifi.country=US
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
ro.factorytest=0
ro.serialno=C6OKAS105604
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=wifi-only
ro.bootloader=unknown
ro.hardware=cardhu
ro.revision=0
ro.boot_reason=normal
ro.crypto.fs_type=ext4
ro.crypto.fs_real_blkdev=/dev/block/mmcblk0p8
ro.crypto.fs_mnt_point=/data
ro.crypto.fs_flags=0x00000006
ro.crypto.state=unencrypted
ro.epad.model_id=04
ro.epad.model=TF700T
ro.sf.lcd_density=240
persist.sys.NV_DISPXRES=1920
persist.sys.NV_DISPYRES=1200
persist.sys.NV_STEREOCTRL=0
persist.tegra.NV_FPSLIMIT=0
persist.sys.NV_FPSLIMIT=35
persist.sys.NV_POWERMODE=1
persist.sys.profiler_ms=0
persist.sys.NV_STEREOSEP=20
persist.sys.NV_STEREOSEPCHG=0
persist.sys.NV_PROFVER=20
persist.sys.fw.camera.status=1
persist.sys.language=en
persist.sys.country=US
persist.sys.localevar=
persist.sys.timezone=America/New_York
persist.sys.ui.hw=true
init.svc.recovery=running
init.svc.adbd=running
I:Enable RSA key verification.
Installing update...
Finding update package...
I:Update location: /cache/dlpkgfile
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1682 bytes; signature 1664 bytes from end
E:failed to verify whole-file signature
I:verify_file returned 1
E:signature verification failed
Installation aborted.
I:result_code: 405
Check and format /storage to vfat if needed...
Mount /btmac successfully
Done.
currently trying to get to stock recovery.
I never unlocked, but did run v6 supercharger, and have since many times factory reset and gone though recovery and manually flashed the .22, and then will try this again...
Stock build.prop on .26 WW, same number of lines as on .22, haven't diff'ed it yet:
Code:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.display.id=IML74K.WW_epad-9.4.5.26-20120720
ro.build.version.incremental=WW_epad-9.4.5.26-20120720
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Fri Jul 20 19:32:57 CST 2012
ro.build.date.utc=1342783977
ro.build.type=user
ro.build.user=
ro.build.host=Mercury
ro.build.tags=release-keys
ro.product.model=EPAD
ro.product.brand=asus
ro.product.name=WW_epad
ro.product.device=EeePad
ro.product.board=EeePad
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=asus
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=tegra
# ro.build.product is obsolete; use ro.product.device
ro.build.product=EeePad
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=WW_epad-user 4.0.3 IML74K WW_epad-9.4.5.26-20120720 release-keys
ro.build.fingerprint=asus/WW_epad/EeePad:4.0.3/IML74K/WW_epad-9.4.5.26-20120720:user/release-keys
ro.build.characteristics=tablet
# end build properties
ro.opengles.version = 131072
wifi.interface=wlan0
persist.tegra.nvmmlite = 1
#NFC
debug.nfc.fw_download=false
debug.nfc.se=false
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.config.notification_sound=NewMessage.ogg
persist.sys.ringermode=2
ro.config.bootsound=PowerOn.ogg
drm.service.enabled=1
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
wifi.version.driver=V6.1.40
gps.version.driver=V6.9.18
keyguard.no_require_sim=true
ro.kernel.qemu=
bt.version.driver=V9.37
windowsmgr.max_events_per_sec=200
ro.setupwizard.mode=OPTIONAL
ro.com.google.gmsversion=4.0_r3
ro.com.google.clientidbase=android-asus
ro.com.google.mcc_fallback=262
ro.wifi.country=GB
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
tf.enable=y
Edit: OK, I've just compared build.prop from WW .26 with the one from WW .21, no changes apart from the version numbers (which is actually a little disappointing, as they haven't touched it).
GrimSage said:
Does anyone have a stock build.prop file?
I have tried doing this and still get the dead android
currently trying to get to stock recovery.
I never unlocked, but did run v6 supercharger, and have since many times factory reset and gone though recovery and manually flashed the .22, and then will try this again...
Click to expand...
Click to collapse
It seems you have a corrupted dlpkgfile
the correct md5sum for dlpkgfile should be
2ff06463b57226ac910ac642781c5290
Your build.prop is stock. Just got to download "dlpkgfile" again because it won't verify on your tablet.
I posted a write up of the process I followed to restore the system image, build.prop, and stock recovery, then update to .26 using dlpkgfile if anyone's interested.
It's here: http://forum.xda-developers.com/showthread.php?t=1803343
Redefined301 said:
It seems you have a corrupted dlpkgfile
the correct md5sum for dlpkgfile should be
2ff06463b57226ac910ac642781c5290
Your build.prop is stock. Just got to download "dlpkgfile" again because it won't verify on your tablet.
Click to expand...
Click to collapse
looks like somewhere between restoring the stock recovery and redownloading the dlpkgfile, this has worked.
Currently have
Android is upgrading...
Optimizing application XX of XX.
Thank you to everyone!
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
Devices One Touch 4011x MT6575
Flashing CMW V5.5.0.4 and do nandroid backup for safety....im wrong edit some word in build.prop ,restart devices then got stuck at animations boots,im trying restore but still stuck at animations boots..btw the backup has work before..how to fix this problem in cmw?btw my devices still can go cwm..
PHP:
Starting recovery on Sun Jan 1 01:24:30 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 24.07.2013 04:48:02
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/misc (null) 0
2 /data ext4 /dev/block/mmcblk0p7 (null) 0
3 /system ext4 /dev/block/mmcblk0p5 (null) 0
4 /cache ext4 /dev/block/mmcblk0p6 (null) 0
5 /boot emmc /dev/bootimg (null) 0
6 /recovery emmc /dev/recovery (null) 0
7 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
8 /sd-ext auto /dev/block/mmcblk1p2 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=IMM76L
ro.build.display.id=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.version.incremental=eng.rua1.20130129.114933
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Вто Янв 29 11:51:46 MSK 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=rua1
ro.build.host=rua1-desktop
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_MTK
ro.product.device=MTK
ro.product.board=MTK
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=MTK
ro.build.description=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.fingerprint=Android/full_MTK/MTK:4.0.4/IMM76L/eng.rua1.20130129.114933:eng/test-keys
ro.build.characteristics=default
ro.cm.device=MTK
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6575
ro.revision=1710983680
ro.emmc=0
sys.usb.vid=0BB4
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
hello someone please help
techpowering said:
hello someone please help
Click to expand...
Click to collapse
you can't go to cwm?
thank for replying...im really need help? my devices still can in cwm..did you know what cause problem about my devices? trying restore still stuck at boot animation...btw backup was working before.. please help
techpowering said:
thank for replying...im really need help? my devices still can in cwm..did you know what cause problem about my devices? trying restore still stuck at boot animation...btw backup was working before.. please help
Click to expand...
Click to collapse
1. Go to CWM
2. Do a Factory Reset
3. Clear cache and dalvik-cache
3. Restore your backup
3. Clear cache and dalvik-cache (again)
4. Reboot and wait. (may take some time to start)
If it still does not, you have to install adb shell on pc and replace the original file build.prop
I hope it was usefull
greetings
FSadino said:
1. Go to CWM
2. Do a Factory Reset
3. Clear cache and dalvik-cache
3. Restore your backup
3. Clear cache and dalvik-cache (again)
4. Reboot and wait. (may take some time to start)
If it still does not, you have to install adb shell on pc and replace the original file build.prop
I hope it was usefull
greetings
Click to expand...
Click to collapse
Thank for Reply i have a question can we replace the original file build.prop in update.zip?because my devices has damage usb port ( some small damage on board i/c ) so my devices cant be detected anymore at computer..it because im plug charger usb on car.. btw i was doing factory reset,clean cache,davlik,restore ,clean again now reboot and wait..i will update how it work...uuh i hope build.prop can replace with zip file
seems not work how to replace build.prop zip file?
i believe there is not much you can do without usb connection. you have to get your usb working again before you can fix the phone.
Sent from my ONE TOUCH 4011X using XDA Free mobile app
techpowering said:
seems not work how to replace build.prop zip file?
Click to expand...
Click to collapse
I agree with @HadpeH, without USB we can not do anything. First fix this problem then it will be easier to help you
im request the stock build.prop for devices One Touch 4011x ( alcatel )..my usb devices cannot repair because the small i/c board has broken
you can try to extract the file you need from the stock rom here - sourceforge(dot)net/projects/alcatel/files-
i think you can replace build.prop using updater script.
Sent from my ONE TOUCH 4011X using XDA Free mobile app
hey
HadpeH said:
you can try to extract the file you need from the stock rom here - sourceforge(dot)net/projects/alcatel/files-
i think you can replace build.prop using updater script.
Sent from my ONE TOUCH 4011X using XDA Free mobile app
Click to expand...
Click to collapse
if you have an sdcard remove it put in card reader connect card reader to pc, download aromafm to card and the build.prop
replacement put card back into device, boot into cwm, install aromafm.zip start file manager nav to proper build.prop and copy,
nav to /system and paste, long pres on newly pasted build prop and set perm to 644. reboot.
m
moonbutt74 said:
if you have an sdcard remove it put in card reader connect card reader to pc, download aromafm to card and the build.prop
replacement put card back into device, boot into cwm, install aromafm.zip start file manager nav to proper build.prop and copy,
nav to /system and paste, long pres on newly pasted build prop and set perm to 644. reboot.
m
Click to expand...
Click to collapse
Thank you i will try as soon...and will update how works
Bump! already replace with new build.prop using Aroma file manager...and set to rw-r--r-- still not work..stuck at animation boots..tried nandroid restore..and reboot still stuck on animations boots what the problem of this? can someone help read this log what cause problem on my devices
HTML:
Starting recovery on Sun Jan 1 01:00:47 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 24.07.2013 04:48:02
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/misc (null) 0
2 /data ext4 /dev/block/mmcblk0p7 (null) 0
3 /system ext4 /dev/block/mmcblk0p5 (null) 0
4 /cache ext4 /dev/block/mmcblk0p6 (null) 0
5 /boot emmc /dev/bootimg (null) 0
6 /recovery emmc /dev/recovery (null) 0
7 /sdcard vfat /dev/block/mmcblk1p1 (null) 0
8 /sd-ext auto /dev/block/mmcblk1p2 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.build.id=IMM76L
ro.build.display.id=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.version.incremental=eng.rua1.20130129.114933
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.4
ro.build.date=Вто Янв 29 11:51:46 MSK 2013
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=rua1
ro.build.host=rua1-desktop
ro.build.tags=test-keys
ro.product.model=Full Android on Emulator
ro.product.brand=Android
ro.product.name=full_MTK
ro.product.device=MTK
ro.product.board=MTK
ro.product.cpu.abi=armeabi
ro.product.manufacturer=unknown
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=unknown
ro.build.product=MTK
ro.build.description=full_MTK-eng 4.0.4 IMM76L eng.rua1.20130129.114933 test-keys
ro.build.fingerprint=Android/full_MTK/MTK:4.0.4/IMM76L/eng.rua1.20130129.114933:eng/test-keys
ro.build.characteristics=default
ro.cm.device=MTK
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.adb.qemud=1
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=mt6575
ro.revision=1710983680
ro.emmc=0
sys.usb.vid=0BB4
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=restarting
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
bump for help
Hello! I've got this tablet Captiva Pad 8 (captiva-power.de/captiva-pad-8-en.htm)
I've installed Clockwork on it but it seems it's for the wrong type of tablet as it won't mount the sdcard.
Luckily I got by that by adb shell and mounting nandi partition to get stuff going from there.
Before that I did a sideload of a Cyanogenmod 9 which seems to kind of work but that too doesn't mount everything and I do it by adb shell. Also it shows me that the device is a Nexus 7 and my camera and wifi won't work. I can get wpa_supplicant compiled for arm and all of that but I would love to have a clean environment.
Does anyone know which image I should flash for clockwork so that I get stuff running from there? Maybe even a good CyanogenMod?
My initial goal was to flash an ubuntu touch or debian onto it but I failed repeatedly.
If nothing goes well I'll just to tests by dd in the nand boot and system partitions and see where that leaves me. As long as I got this Clockwork Recovery I can get shell and rewrite the backups I make by dd.
Thank you!
The build.prop in nanda:
# begin build properties
# autogenerated by buildinfo.sh
ro.build.id=IML74K
ro.build.version.incremental=20120630
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Sat Jun 30 18:34:04 CST 2012
ro.build.date.utc=1341052444
ro.build.type=eng
ro.build.user=paco
ro.build.host=inet
ro.build.tags=test-keys
ro.product.model=CAPTIVA PAD 8
ro.product.brand=iNet
ro.product.name=crane_evb
ro.product.device=crane-evb
ro.product.board=crane
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.wifi.channels=
ro.board.platform=exDroid
# ro.build.product is obsolete; use ro.product.device
ro.build.product=crane-evb
# Do not try to parse ro.build.description or .fingerprint
ro.build.description=crane_evb-eng 4.0.3 IML74K 20120630 test-keys
ro.build.fingerprint=iNet/crane_evb/crane-evb:4.0.3/IML74K/20120630:eng/test-keys
ro.build.characteristics=tablet
# end build properties
#
# ADDITIONAL_BUILD_PROPERTIES
#
ro.com.android.dateformat=MM-dd-yyyy
ro.config.ringtone=Ring_Synth_04.ogg
ro.config.notification_sound=pixiedust.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=256m
ro.kernel.android.checkjni=0
persist.sys.timezone=Europe/London
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
debug.egl.hw=1
ro.display.switch=1
ro.opengles.version=131072
persist.sys.strictmode.visual=0
persist.sys.strictmode.disable=1
hwui.render_dirty_regions=false
persist.sampling_profiler=1
persist.sys.usb.config=mass_storage,adb
ro.product.firmware=1.1
persist.sys.language=de
persist.sys.country=DE
ro.sf.lcd_density=120
ro.build.display.id=18F3-R1-H2-M01-2337.20120630
ro.config.3ginformation.path=/system/etc/3ginfo.gz
ro.setupwizard.mode=DISABLED
net.bt.name=Android
dalvik.vm.stack-trace-file=/data/anr/traces.txt
Technical Details:
Product name CAPTIVA Pad 8 Manufacturer CAPTIVA Display 20,3 cm (8") capacitive 5 Punkt (800x600 px, 4:3) Processors Cortex A8, 1.2 GHz Operating system Android 4.04 RAM 1 GB DDR3 Internal memory 8 GB Nand Flash Connections 1x mini USB, 1x mini HDMI, 3.5mm Stereo Headphone jack Card reader max. 32 GB Audio built-in speaker Webcams Front 0,3 MPixel, Back 2,0 MPixel WLAN 802.11 b/g/n UMTS/ 3G supports external 3G USB Dongle G-/position sensor included Rechargeable battery 4.000mAh Li-Polymer, up to 5h run time Dimensions 210 x 160 x 14,5mm
Seems to be of no interest for anyone. That's a real pity.
No alternative software ?
I own the same Tablet but it seems that there is no alternative operating system than the original old android 4.0.3
:crying: