I dont know what to do help amaze
Starting recovery on Sat Jan 21 17:49:16 2012
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (540 x 960)
CWM Recovery v5.5.0.4 Xboarders Ruby Source
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot emmc /dev/block/mmcblk0p22 (null) 0
2 /cache ext4 /dev/block/mmcblk0p30 (null) 0
3 /data ext4 /dev/block/mmcblk0p31 (null) 0
4 /misc emmc /dev/block/mmcblk0p24 (null) 0
5 /recovery emmc /dev/block/mmcblk0p23 (null) 0
6 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk0p36 0
7 /system ext4 /dev/block/mmcblk0p29 (null) 0
8 /devlog ext4 /dev/block/mmcblk0p32 (null) 0
9 /internal_sdcard vfat /dev/block/mmcblk0p36 (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!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Boot command: T-MOB010
I:Boot status: DeviceWarmBoot
W:failed to mount /dev/block/mmcblk0p30 (No such file or directory)
E:Can't mount /cache/recovery/command
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
persist.service.adb.enable=1
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=MR1
ro.build.display.id=full_ruby-eng 4.0.3 MR1 eng.xboarder56.20120118.201719 test-keys
ro.build.version.incremental=eng.xboarder56.20120118.201719
ro.build.version.sdk=15
ro.build.version.codename=REL
ro.build.version.release=4.0.3
ro.build.date=Wed Jan 18 20:17:46 PST 2012
ro.build.date.utc=1326946666
ro.build.type=eng
ro.build.user=xboarder56
ro.build.host=xboarder56-desktop
ro.build.tags=test-keys
ro.product.model=HTC Amaze 4g
ro.product.brand=generic
ro.product.name=full_ruby
ro.product.device=ruby
ro.product.board=ruby
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.wifi.channels=
ro.board.platform=msm8660
ro.build.product=ruby
ro.build.description=full_ruby-eng 4.0.3 MR1 eng.xboarder56.20120118.201719 test-keys
ro.build.fingerprint=generic/full_ruby/ruby:4.0.3/MR1/eng.xboarder56.20120118.201719:eng/test-keys
ro.build.characteristics=default
ro.cm.device=ruby
rild.libargs=-d /dev/smd0
telephony.lteOnCdmaDevice=0
ro.sf.lcd_density=240
ro.gsm.2nd_data_retry_config=max_retries=3, 2000, 2000, 2000
rild.libpath=/system/lib/libril-qc-qmi-1.so
persist.rild.nitz_plmn=
persist.rild.nitz_long_ons_0=
persist.rild.nitz_long_ons_1=
persist.rild.nitz_long_ons_2=
persist.rild.nitz_long_ons_3=
persist.rild.nitz_short_ons_0=
persist.rild.nitz_short_ons_1=
persist.rild.nitz_short_ons_2=
persist.rild.nitz_short_ons_3=
persist.rild.ril.ltedr=0
persist.rild.ril.ltedrtable=max_retries=infinite,10000
DEVICE_PROVISIONED=1
persist.cne.UseCne=false
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.be.ge.sqi.min=0
persist.cne.be.ge.sqi.max=100
persist.cne.be.umts.sqi.min=0
persist.cne.be.umts.sqi.max=100
persist.cne.be.hspa.sqi.min=0
persist.cne.be.hspa.sqi.max=100
persist.cne.be.1x.sqi.min=0
persist.cne.be.1x.sqi.max=100
persist.cne.be.do.sqi.min=0
persist.cne.be.do.sqi.max=100
persist.cne.be.wlan.sqi.min=0
persist.cne.be.wlan.sqi.max=100
ro.use_data_netmgrd=true
persist.data_netmgrd_nint=11
ro.config.lte=true
ro.ril.enable.dtm=0
ro.ril.gprsclass=12
ro.ril.hsdpa.category=10
ro.ril.hsupa.category=6
ro.ril.hsxpa=3
ro.telephony.default_network=0
wifi.interface=tiwlan0
wifi.supplicant_scan_interval=100
ro.opengles.version=131072
dalvik.vm.heapsize=32m
ro.ril.def.agps.mode=2
ro.config.disable_hw_accel=true
ro.com.google.clientidbase=android-htc
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.com.google.gmsversion=2.3_r5
ro.setupwizard.enable_bypass=1
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
ro.com.google.clientidbase.yt=android-htc
ro.com.google.clientidbase.am=android-tmobile-us
ro.com.google.clientidbase.vs=android-hms-tmobile-us
ro.com.google.clientidbase.gmm=android-htc
ro.com.google.clientidbase.ms=android-hms-tmobile-us
ro.phone.min_match=7
gsm.sim.operator.alpha=tmobile
gsm.operator.alpha=tmobile
ro.cdma.home.operator.numeric=310120
gsm.sim.operator.numeric=310120
gsm.operator.numeric=310120
gsm.sim.operator.iso-country=us
gsm.operator.iso-country=us
ro.media.dec.jpeg.memcap=20000000
media.a1026.nsForVoiceRec=0
media.a1026.enableA1026=0
htc.audio.alt.enable=0
htc.audio.hac.enable=0
keyguard.no_require_sim=true
ro.com.android.dataroaming=true
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
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=HT19VVP07279
ro.bootmode=recovery
ro.baseband=N/A
ro.carrier=TMUS
ro.bootloader=1.90.0008
ro.hardware=ruby
ro.revision=4
ro.emmc=1
init.svc.choice_fn=stopped
init.svc.htcbatt=running
init.svc.adbd=running
ro.9kramdump=0
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p30 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p30 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p30 (No such file or directory)
W:Can't unlink /cache/recovery/command
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
W:failed to mount /dev/block/mmcblk0p30 (No such file or directory)
Error mounting /cache!
failed to open /sys/class/android_usb/android0/state: No such file or directory
W:failed to mount /dev/block/mmcblk0p30 (No such file or directory)
Error mounting /cache!
failed to open /sys/class/android_usb/android0/state: No such file or directory
W:failed to mount /dev/block/mmcblk0p30 (No such file or directory)
Error mounting /cache!
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
W:failed to mount /dev/block/mmcblk0p30 (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p30 (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p30 (No such file or directory)
W:Can't unlink /cache/recovery/command
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
failed to open /sys/class/android_usb/android0/state: No such file or directory
I had this same exact problem yesterday. I would suggest going back to stock completely. I tried all kinds of different solutions but there were times I couldn't even get back into recovery! But now I'm running bulletproof again with no issues so far.
Sent from my HTC_Amaze_4G using XDA Premium App
ohhh man i think i messed up .. it automaticlly flashed the ph85 img before i relocked . now i cant get recovery but i can do hboot
lol nevermind did it in fastboot thanks love this site
Good to hear it worked! If you can get into fastboot your phone is okay most of the time.
Sent from my HTC_Amaze_4G using XDA Premium App
As of right now I'm still on THS Build 2. That part of the process is ok, but as far as flashing MIUI V4 goes, I can't get that rom to flash properly. I've followed the instructions precisely and for some reason no matter which build of MIUI I try to flash, the installation always is aborted due to the file being bad.
It aborts and at the end of the line in clockwork it says (bad).
I'm using the same download from goo-inside. Is anyone else having problems with this rom.
I got the same problem.
When I first tried it, it messed up and I had to flash a new stock rom. So I used this "CR20_EC01_NUTSx_SHARK.tar.md5". It's working fine. It comes already rooted as well. So then I downloaded ROM Manager by Clockworkmod and flashed the CMR from the app. Once that was done, I clicked on reboot into recovery mode. Then I wiped all data, wiped cache, and wiped Delvik cache. Then I tried to install the rom from my SDcard through CMR. I tried both version 2.3.23 and the new 2.3.30 and they both said at the end...
Code:
-- Installing: /sdcard/MIUI.us_fascinatemtd_2.3.23_4.0_Eng_Deo_ZipA_Signed_weblexa-gpsfix.zip
Finding update package...
I:Update location: /sdcard/MIUI.us_fascinatemtd_2.3.23_4.0_Eng_Deo_ZipA_Signed_weblexa-gpsfix.zip
Opening update package...
minzip: Could not find end-of-central-directory in Zip
E:Can't open /sdcard/MIUI.us_fascinatemtd_2.3.23_4.0_Eng_Deo_ZipA_Signed_weblexa-gpsfix.zip
(bad)
Installation aborted.
It asked if I wanted to send an error report so I did and this is what it sent to the rommanager guys... (Not sure if this will help you guys but who knows.)
Code:
Starting recovery on Sat Mar 31 06:25:28 2012
[initialize ui and event]
get_framebuffer -> fd 7
get_framebuffer -> fscreen : base 0x4fc00000
get_framebuffer -> fscreen : len 3072000
get_framebuffer -> vscreen : xres 480
get_framebuffer -> vscreen : yres 800
get_framebuffer -> mmap 0x40009000
get_framebuffer -> fb->data 1 0x40009000
get_framebuffer -> fb->data 1 0x400c4800
framebuffer: fd 7 (480 x 800)
[collecting command]
Got arguments from CACHE:recovery/command
wipedata: null
PATH: /data/fota
idev_increase_numRecovery(--started--)
idev_get_numRecovery(--started--)
fopen error(DATA:fota/ipth_num_recovery.txt)
final string=numRecovery=1
idev_get_updateStatus(--started--)
fopen error(DATA:fota/ipth_config_dfs.txt)
upStatus=-1
No update set
Command: "/sbin/recovery" "--update_package=CACHE:update.zip"
[property list]
ro.secure=0
ro.allow.mock.location=0
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=SMDKC110
ro.revision=32
dpm.allowcamera=1
ro.debugable=1
rild.libpath=/system/lib/libsec-ril40.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.telephony.call_ring.multiple=0
A2DP_INCALL=0
init.svc.recovery=running
init.svc.adbd=running
[install package]
I:Update location: CACHE:update.zip
I:Update file path: /cache/update.zip
I:1 key(s) loaded from /res/keys
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified
I:verify_file returned 0
minzip: Opening archive '/cache/update.zip' 0xbeb24b04
minzip: numEntries=28 cdOffset=1346714
I:+ try_update_binary
minzip: +++ reading 32768 bytes (128407 left)
minzip: +++ processing 32768 bytes
minzip: +++ reading 32768 bytes (95639 left)
minzip: +++ processing 32768 bytes
minzip: +++ processing 32768 bytes
minzip: +++ reading 32768 bytes (62871 left)
minzip: +++ processing 32768 bytes
minzip: +++ reading 30103 bytes (30103 left)
minzip: +++ processing 32768 bytes
minzip: +++ processing 32768 bytes
minzip: +++ processing 2084 bytes
I:try_update_binary -> Extract binary (/tmp/update_binary)
try_update_binary -> argv[0] : /tmp/update_binary
try_update_binary -> argv[1] : 2
try_update_binary -> argv[2] : 16
try_update_binary -> argv[3] : /cache/update.zip
try_update_binary -> argv[4] : (null)
I:try_update_binary -> ui_print(Replacing stock recovery with ClockworkMod recovery...)
about to run program [/sbin/busybox] with 4 args
I:try_update_binary -> ui_print((null))
about to run program [/sbin/busybox] with 4 args
sh: bad pid 'root'
sh: can't kill pid 3288: No such process
sh: bad pid 'S'
sh: bad pid '/sbin/adbd'
sh: can't kill pid 2332: No such process
sh: bad pid 'root'
sh: can't kill pid 1516: No such process
sh: bad pid 'S'
sh: bad pid 'grep'
sh: bad pid '/sbin/adbd'
sh: bad pid 'root'
sh: can't kill pid 8372: No such process
sh: bad pid 'S'
sh: bad pid '/sbin/recovery'
sh: can't kill pid 2337: No such process
sh: bad pid 'root'
sh: can't kill pid 1516: No such process
sh: bad pid 'S'
sh: bad pid 'grep'
sh: bad pid '/sbin/recovery'
run_program: child exited with status 1
script result was [256]
rm: /etc: is a directory
chmod: /sbin/su: No such file or directory
Starting recovery on Sat Mar 31 06:25:33 2012
framebuffer: fd 18 (480 x 800)
ClockworkMod Recovery v3.0.0.8
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot bml boot (null)
2 /cache rfs /dev/block/stl11 (null)
3 /data rfs /dev/block/mmcblk0p1 (null)
4 /datadata rfs /dev/block/stl10 (null)
5 /recovery bml recovery (null)
6 /sdcard vfat /dev/block/mmcblk1p1 (null)
7 /system rfs /dev/block/stl9 (null)
W:Unable to get recovery.fstab info for /sd-ext 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=0
ro.debuggable=1
persist.service.adb.enable=1
ro.factorytest=0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=SMDKC110
ro.revision=32
dpm.allowcamera=1
ro.debugable=1
rild.libpath=/system/lib/libsec-ril40.so
rild.libargs=-d /dev/ttyS0
ro.sf.lcd_density=240
ro.telephony.call_ring.multiple=0
A2DP_INCALL=0
init.svc.recovery=stopped
init.svc.adbd=running
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
I:Running script:
I:
ui_print("ROM Manager Version 5.0.0.6");
ui_print("March 31, 2012");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
format("/cache");
format("/data");
format("/sd-ext");
assert(install_zip("/sdcard/MIUI.us_fascinatemtd_2.3.23_4.0_Eng_Deo_ZipA_Signed_weblexa-gpsfix.zip"));
parse returned 0; 0 errors encountered
ROM Manager Version 5.0.0.6
March 31, 2012
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk0p1 on /data failed: Device or resource busy
mount: mounting /dev/block/stl11 on /cache failed: Device or resource busy
mount: mounting /dev/block/stl9 on /system failed: Invalid argument
mount: can't find /sd-ext in /etc/fstab
umount: can't umount /data: Device or resource busy
umount: can't umount /system: Invalid argument
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
Formatting /cache...
E:format_volume failed to unmount "/cache"
Formatting /data...
E:format_volume failed to unmount "/data"
Formatting /sd-ext...
-- Installing: /sdcard/MIUI.us_fascinatemtd_2.3.23_4.0_Eng_Deo_ZipA_Signed_weblexa-gpsfix.zip
Finding update package...
I:Update location: /sdcard/MIUI.us_fascinatemtd_2.3.23_4.0_Eng_Deo_ZipA_Signed_weblexa-gpsfix.zip
Opening update package...
minzip: Could not find end-of-central-directory in Zip
E:Can't open /sdcard/MIUI.us_fascinatemtd_2.3.23_4.0_Eng_Deo_ZipA_Signed_weblexa-gpsfix.zip
(bad)
Installation aborted.
result was NULL, message is: assert failed: install_zip("/sdcard/MIUI.us_fascinatemtd_2.3.23_4.0_Eng_Deo_ZipA_Signed_weblexa-gpsfix.zip")
If you need more information just ask.
^^^your in the wrong recovery....look up section 4 of my guide in general section for flashing anything ICS based. oh and there is no need to wipe both caches after wiping data....the data wipe itself formats all three...read the log in recovery after wiping data and you shall see.
droidstyle said:
^^^your in the wrong recovery....look up section 4 of my guide in general section for flashing anything ICS based. oh and there is no need to wipe both caches after wiping data....the data wipe itself formats all three...read the log in recovery after wiping data and you shall see.
Click to expand...
Click to collapse
I followed yours and after I installed the ICS rom I tried to install the MIUI rom but it still says that it's "(bad)". What do I do?
Edit: I tried following section 3 of your guide where it says how to flash MIUI. Still got the same result of saying it's "(bad)". =/
Edit 2: I found out that I'm getting the (bad) because the .zip has an error in it. You can test of this by trying to open the .zip and if you get an error, it won't work. That's so good to know now. xD I'll have to download it again and hope I get no errors in the file. x.x
Edit 3: Ok so I got one that didn't give me an error and when I installed it following the instructions from section 3 of your guide, it just keeps saying "SAMSUNG" over and over again between black screens. What's wrong now? =(
Edit 4: FINALLY GOT IT WORKING! I flashed Gingerbread, then installed from sdcard ICS Build2, then installed from sdcard MIUI and it worked this time! =D
Dear all,
I hope someone can help me.
I have a chinese phone called BML S55-W (alsp detected as ALPS S55-w)
Device recognized as: hct72_wet_jb3
Android 4.2.2
I rooted it and installed CWM with MTK Droid Tools. So far, so good..
However, I can't flash any roms I build with Android Kitchen (even if I just take my stock rom (from dump with mtk droid tools) and build a zip out of it).
Error seems to be this:
minzip: Extracted file "/system/app/GoogleFeedback.apk"
minzip: Error writing 32768 bytes from zip file from 0xbedba36c: Read-only file system
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/app/GoogleLoginService.apk"
It "randomly" happens with one of the apks in /system/app, after which it fails at doing anything.
Does anyone have any idea what I can do to fix it? Thank you in advance.
-Emile
Log:
Starting recovery on Thu Aug 28 13:29:59 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 21.08.2014 20:20:14
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /misc emmc /dev/misc (null) 0
2 /data ext4 /dev/block/mmcblk0p6 (null) 0
3 /system ext4 /dev/block/mmcblk0p4 (null) 0
4 /cache ext4 /dev/block/mmcblk0p5 (null) 0
5 /boot emmc /dev/bootimg (null) 0
6 /recovery emmc /dev/recovery (null) 0
7 /emmc vfat /dev/block/mmcblk0p7 (null) 0
8 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1 0
9 /sd-ext auto /dev/block/mmcblk1p2 (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.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=mt6572
ro.revision=0
ro.emmc=0
sys.usb.vid=0BB4
init.svc.recovery=running
sys.usb.config=mass_storage,adb
service.adb.root=1
init.svc.adbd=stopping
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
-- Installing: /emmc/Download/hct72_wet_jb3_signed_082814_121052.zip
Finding update package...
I:Update location: /emmc/Download/hct72_wet_jb3_signed_082814_121052.zip
Opening update package...
Installing update...
Creating filesystem with parameters:
Size: 734003200
Block size: 4096
Blocks per group: 32768
Inodes per group: 7467
Inode size: 256
Journal blocks: 2800
Label:
Blocks: 179200
Block groups: 6
Reserved block group size: 47
Created filesystem with 11/44802 inodes and 5813/179200 blocks
minzip: Extracted file "/system/S90zipalign"
minzip: Extracted file "/system/app/.restore_list"
minzip: Extracted file "/system/app/ApplicationGuide.apk"
minzip: Extracted file "/system/app/ApplicationGuide.odex"
minzip: Extracted file "/system/app/ApplicationsProvider.apk"
minzip: Extracted file "/system/app/ApplicationsProvider.odex"
minzip: Extracted file "/system/app/BackupRestoreConfirmation.apk"
minzip: Extracted file "/system/app/BackupRestoreConfirmation.odex"
minzip: Extracted file "/system/app/BasicDreams.apk"
minzip: Extracted file "/system/app/BasicDreams.odex"
minzip: Extracted file "/system/app/BatteryWarning.apk"
minzip: Extracted file "/system/app/BatteryWarning.odex"
minzip: Extracted file "/system/app/Calculator.apk"
minzip: Extracted file "/system/app/Calculator.odex"
minzip: Extracted file "/system/app/Calendar.apk"
minzip: Extracted file "/system/app/Calendar.odex"
minzip: Extracted file "/system/app/CalendarImporter.apk"
minzip: Extracted file "/system/app/CalendarImporter.odex"
minzip: Extracted file "/system/app/CalendarProvider.apk"
minzip: Extracted file "/system/app/CalendarProvider.odex"
minzip: Extracted file "/system/app/CellConnService.apk"
minzip: Extracted file "/system/app/CellConnService.odex"
minzip: Extracted file "/system/app/CertInstaller.apk"
minzip: Extracted file "/system/app/CertInstaller.odex"
minzip: Extracted file "/system/app/ContactsProvider.apk"
minzip: Extracted file "/system/app/ContactsProvider.odex"
minzip: Extracted file "/system/app/DefaultContainerService.apk"
minzip: Extracted file "/system/app/DefaultContainerService.odex"
minzip: Extracted file "/system/app/DeskClock.apk"
minzip: Extracted file "/system/app/DeskClock.odex"
minzip: Extracted file "/system/app/DownloadProvider.apk"
minzip: Extracted file "/system/app/DownloadProvider.odex"
minzip: Extracted file "/system/app/DrmProvider.apk"
minzip: Extracted file "/system/app/DrmProvider.odex"
minzip: Extracted file "/system/app/Email.apk"
minzip: Extracted file "/system/app/Email.odex"
minzip: Extracted file "/system/app/EngineerMode.apk"
minzip: Extracted file "/system/app/EngineerMode.odex"
minzip: Extracted file "/system/app/EngineerModeSim.apk"
minzip: Extracted file "/system/app/EngineerModeSim.odex"
minzip: Extracted file "/system/app/Exchange2.apk"
minzip: Extracted file "/system/app/Exchange2.odex"
minzip: Extracted file "/system/app/FMRadio.apk"
minzip: Extracted file "/system/app/FMRadio.odex"
minzip: Extracted file "/system/app/FactoryMode.apk"
minzip: Extracted file "/system/app/FactoryMode.odex"
minzip: Extracted file "/system/app/FactoryMode2.apk"
minzip: Extracted file "/system/app/FactoryMode2.odex"
minzip: Extracted file "/system/app/FileManager.apk"
minzip: Extracted file "/system/app/FileManager.odex"
minzip: Extracted file "/system/app/FusedLocation.apk"
minzip: Extracted file "/system/app/FusedLocation.odex"
minzip: Extracted file "/system/app/GMS_Maps.apk"
minzip: Extracted file "/system/app/Galaxy4.apk"
minzip: Extracted file "/system/app/Galaxy4.odex"
minzip: Extracted file "/system/app/Gallery2.apk"
minzip: Extracted file "/system/app/Gallery2.odex"
minzip: Extracted file "/system/app/GenieWidget.apk"
minzip: Extracted file "/system/app/Gmail2.apk"
minzip: Extracted file "/system/app/GoogleBackupTransport.apk"
minzip: Extracted file "/system/app/GoogleCalendarSyncAdapter.apk"
minzip: Extracted file "/system/app/GoogleContactsSyncAdapter.apk"
minzip: Extracted file "/system/app/GoogleFeedback.apk"
minzip: Error writing 32768 bytes from zip file from 0xbedba36c: Read-only file system
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/app/GoogleLoginService.apk"
symlink: failed to symlink /system/bin/dumpcrash to dumpstate: No such file or directory
symlink: failed to symlink /system/bin/cat to toolbox: No such file or directory
symlink: failed to symlink /system/bin/chmod to toolbox: No such file or directory
symlink: failed to symlink /system/bin/chown to toolbox: No such file or directory
symlink: failed to symlink /system/bin/cmp to toolbox: No such file or directory
symlink: failed to symlink /system/bin/date to toolbox: No such file or directory
symlink: failed to symlink /system/bin/dd to toolbox: No such file or directory
symlink: failed to symlink /system/bin/df to toolbox: No such file or directory
symlink: failed to symlink /system/bin/dmesg to toolbox: No such file or directory
symlink: failed to symlink /system/bin/getevent to toolbox: No such file or directory
symlink: failed to symlink /system/bin/getprop to toolbox: No such file or directory
symlink: failed to symlink /system/bin/hd to toolbox: No such file or directory
symlink: failed to symlink /system/bin/id to toolbox: No such file or directory
symlink: failed to symlink /system/bin/ifconfig to toolbox: No such file or directory
symlink: failed to symlink /system/bin/iftop to toolbox: No such file or directory
symlink: failed to symlink /system/bin/insmod to toolbox: No such file or directory
symlink: failed to symlink /system/bin/ioctl to toolbox: No such file or directory
symlink: failed to symlink /system/bin/ionice to toolbox: No such file or directory
symlink: failed to symlink /system/bin/kill to toolbox: No such file or directory
symlink: failed to symlink /system/bin/ln to toolbox: No such file or directory
symlink: failed to symlink /system/bin/log to toolbox: No such file or directory
symlink: failed to symlink /system/bin/ls to toolbox: No such file or directory
symlink: failed to symlink /system/bin/lsmod to toolbox: No such file or directory
symlink: failed to symlink /system/bin/lsof to toolbox: No such file or directory
symlink: failed to symlink /system/bin/mkdir to toolbox: No such file or directory
symlink: failed to symlink /system/bin/mount to toolbox: No such file or directory
symlink: failed to symlink /system/bin/mv to toolbox: No such file or directory
symlink: failed to symlink /system/bin/nandread to toolbox: No such file or directory
symlink: failed to symlink /system/bin/netstat to toolbox: No such file or directory
symlink: failed to symlink /system/bin/newfs_msdos to toolbox: No such file or directory
symlink: failed to symlink /system/bin/notify to toolbox: No such file or directory
symlink: failed to symlink /system/bin/printenv to toolbox: No such file or directory
symlink: failed to symlink /system/bin/ps to toolbox: No such file or directory
symlink: failed to symlink /system/bin/reboot to toolbox: No such file or directory
symlink: failed to symlink /system/bin/renice to toolbox: No such file or directory
symlink: failed to symlink /system/bin/rm to toolbox: No such file or directory
symlink: failed to symlink /system/bin/rmdir to toolbox: No such file or directory
symlink: failed to symlink /system/bin/rmmod to toolbox: No such file or directory
symlink: failed to symlink /system/bin/route to toolbox: No such file or directory
symlink: failed to symlink /system/bin/schedtop to toolbox: No such file or directory
symlink: failed to symlink /system/bin/sendevent to toolbox: No such file or directory
symlink: failed to symlink /system/bin/setconsole to toolbox: No such file or directory
symlink: failed to symlink /system/bin/setprop to toolbox: No such file or directory
symlink: failed to symlink /system/bin/sh to mksh: No such file or directory
symlink: failed to symlink /system/bin/sleep to toolbox: No such file or directory
symlink: failed to symlink /system/bin/smd to toolbox: No such file or directory
symlink: failed to symlink /system/bin/start to toolbox: No such file or directory
symlink: failed to symlink /system/bin/stop to toolbox: No such file or directory
symlink: failed to symlink /system/bin/sync to toolbox: No such file or directory
symlink: failed to symlink /system/bin/top to toolbox: No such file or directory
symlink: failed to symlink /system/bin/touch to toolbox: No such file or directory
symlink: failed to symlink /system/bin/umount to toolbox: No such file or directory
symlink: failed to symlink /system/bin/uptime to toolbox: No such file or directory
symlink: failed to symlink /system/bin/vmstat to toolbox: No such file or directory
symlink: failed to symlink /system/bin/watchprops to toolbox: No such file or directory
symlink: failed to symlink /system/bin/wipe to toolbox: No such file or directory
symlink: failed to symlink /system/bin/chcon to toolbox: No such file or directory
symlink: failed to symlink /system/bin/setenforce to toolbox: No such file or directory
symlink: failed to symlink /system/bin/grep to toolbox: No such file or directory
symlink: failed to symlink /system/bin/runcon to toolbox: No such file or directory
symlink: failed to symlink /system/bin/touchinput to toolbox: No such file or directory
symlink: failed to symlink /system/bin/md5 to toolbox: No such file or directory
symlink: failed to symlink /system/bin/getsebool to toolbox: No such file or directory
symlink: failed to symlink /system/bin/setsebool to toolbox: No such file or directory
symlink: failed to symlink /system/bin/restorecon to toolbox: No such file or directory
symlink: failed to symlink /system/bin/getenforce to toolbox: No such file or directory
symlink: failed to symlink /system/bin/load_policy to toolbox: No such file or directory
symlink: failed to symlink /system/bin/cp to toolbox: No such file or directory
symlink: failed to symlink /system/bin/playback to toolbox: No such file or directory
symlink: failed to symlink /system/bin/du to toolbox: No such file or directory
set_perm: chown of /system/bin/ip to 0 3003 failed: No such file or directory
set_perm: chmod of /system/bin/ip to 6755 failed: No such file or directory
set_perm: chown of /system/bin/netcfg to 0 3003 failed: No such file or directory
set_perm: chmod of /system/bin/netcfg to 2750 failed: No such file or directory
set_perm: chown of /system/bin/ping to 0 3004 failed: No such file or directory
set_perm: chmod of /system/bin/ping to 2755 failed: No such file or directory
set_perm: chown of /system/bin/run-as to 0 2000 failed: No such file or directory
set_perm: chmod of /system/bin/run-as to 6750 failed: No such file or directory
set_perm: chown of /system/etc/bluetooth to 0 0 failed: No such file or directory
set_perm: chmod of /system/etc/bluetooth to 755 failed: No such file or directory
set_perm: chown of /system/etc/bluetooth/auto_pairing.conf to 1000 1000 failed: No such file or directory
set_perm: chmod of /system/etc/bluetooth/auto_pairing.conf to 640 failed: No such file or directory
set_perm: chown of /system/etc/bluetooth/blacklist.conf to 3002 3002 failed: No such file or directory
set_perm: chmod of /system/etc/bluetooth/blacklist.conf to 444 failed: No such file or directory
set_perm: chown of /system/etc/dbus.conf to 1002 1002 failed: No such file or directory
set_perm: chmod of /system/etc/dbus.conf to 440 failed: No such file or directory
set_perm: chown of /system/etc/dhcpcd/dhcpcd-run-hooks to 1014 2000 failed: No such file or directory
set_perm: chmod of /system/etc/dhcpcd/dhcpcd-run-hooks to 550 failed: No such file or directory
set_perm: chown of /system/etc/init.goldfish.sh to 0 2000 failed: No such file or directory
set_perm: chmod of /system/etc/init.goldfish.sh to 550 failed: No such file or directory
set_perm: chown of /system/vendor/lib to 0 2000 failed: No such file or directory
set_perm: chmod of /system/vendor/lib to 755 failed: No such file or directory
set_perm: chown of /system/xbin/busybox to 0 1000 failed: No such file or directory
set_perm: chmod of /system/xbin/busybox to 755 failed: No such file or directory
symlink: failed to symlink /system/bin/busybox to /system/xbin/busybox: No such file or directory
about to run program [/system/xbin/busybox] with 4 args
run_program: execv failed: No such file or directory
run_program: child exited with status 1
set_perm: chown of /system/xbin/su to 0 0 failed: No such file or directory
set_perm: chmod of /system/xbin/su to 6755 failed: No such file or directory
symlink: failed to symlink /system/bin/su to /system/xbin/su: No such file or directory
script result was [/system]
Install from sdcard complete.
Click to expand...
Click to collapse
Emileh said:
Dear all,
I hope someone can help me.
I have a chinese phone called BML S55-W (alsp detected as ALPS S55-w)
Device recognized as: hct72_wet_jb3
Android 4.2.2
I rooted it and installed CWM with MTK Droid Tools. So far, so good..
However, I can't flash any roms I build with Android Kitchen (even if I just take my stock rom (from dump with mtk droid tools) and build a zip out of it).
Error seems to be this:
minzip: Extracted file "/system/app/GoogleFeedback.apk"
minzip: Error writing 32768 bytes from zip file from 0xbedba36c: Read-only file system
minzip: Process function elected to fail (in inflate)
minzip: Can't extract entry to file.
minzip: Error extracting "/system/app/GoogleLoginService.apk"
It "randomly" happens with one of the apks in /system/app, after which it fails at doing anything.
Does anyone have any idea what I can do to fix it? Thank you in advance.
-Emile
Log:
Click to expand...
Click to collapse
building rom isn't easy ! Watch tutorials on building roms than build it :good:
Hell_X said:
building rom isn't easy ! Watch tutorials on building roms than build it :good:
Click to expand...
Click to collapse
Yep you're right, but this ROM was actually build using a tutorial
I would be happy to read more about it/watch videos explaining it, but I do not feel that would explain the error message CWM is giving me...
Thank you for your reply tho!
-Emile
Hello,
I think I've bricked my TF201... I've installed androwook, as it was continueously rebooting, so I tried from CWM wipe user data.. It never finished.
Now my pad always start in recovery mode. Just de green droid with a rotating shape, no text. Fastboot don't work but adb work so I can see /tmp/recovery.log.
I tried the unbrick method 1a and 1b but no effect ...
When I do :
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter] => No answer from terminal, wainting for something ...
Could you please give me some advices ... Thank you very much.
Some test I made :
~ # mount -o remount,rw /system
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,seclabel,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=orde
~ # cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p2 /cache ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p1 /system ext4 rw
/dev/block/mmcblk1p1 /external_sd auto rw
~ # mount system
mount system (hangs)
-----------------------
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 31039488 mmcblk0
179 1 524288 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 546304 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 29475840 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
~ # uname -a
uname -a
Linux localhost 3.1.10-g46990e1-dirty #1 SMP PREEMPT Mon Aug 25 17:58:29 EST 2014 armv7l GNU/Linux
---------------------------------------------------
Here is my log file :
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Tue Oct 21 07:53:33 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
CWM-based Recovery v6.0.5.0
Swipe up/down to change selections.
Swipe to the right for enter.
Swipe to the left for back.
recovery filesystem table
=========================
0 /system ext4 /dev/block/mmcblk0p1 0
1 /cache ext4 /dev/block/mmcblk0p2 0
2 /data ext4 /dev/block/mmcblk0p8 0
3 /storage/sdcard1 auto /devices/platform/sdhci-tegra.0/mmc_host/mmc2 0
4 /storage/usbdisk0 auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1.2 0
5 /storage/usbdisk0 auto /devices/platform/tegra-ehci.2/usb2/2-1/2-1.2 0
6 /storage/usbdisk1 auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1.1 0
7 /storage/usbdisk1 auto /devices/platform/tegra-ehci.2/usb2/2-1/2-1.1 0
8 /storage/usbdisk1 auto /devices/platform/tegra-ehci.2/usb2/2-1/2-1:1 0
9 /storage/usbdisk1 auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1:1 0
10 /storage/sdcard2 auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1.3 0
11 /storage/sdcard2 auto /devices/platform/tegra-ehci.2/usb2/2-1/2-1.3 0
12 /external_sd auto /dev/block/mmcblk1p1 0
13 /misc emmc /dev/block/mmcblk0p3 0
14 /staging ext3 /dev/block/mmcblk0p4 0
15 /recovery emmc /dev/block/mmcblk0p9 0
16 /boot emmc /dev/block/mmcblk0p10 0
17 /tmp ramdisk ramdisk 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!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard1 /storage/sdcard1 0 -
I:110 0 usbdisk0 /storage/usbdisk0 0 -
I:110 0 usbdisk0 /storage/usbdisk0 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 sdcard2 /storage/sdcard2 0 -
I:110 0 sdcard2 /storage/sdcard2 0 -
I:200 0 Volumes listed.
Irocessing arguments.
I:Boot command: boot-recovery
I:Got arguments from boot message
I:Checking arguments.
I:device_recovery_start()
Command: "recovery" "--wipe_data"
ro.bq.gpu_to_cpu_unsupported=1
ro.cm.device=tf201
ro.cm.display.version=11-20140825-UNOFFICIAL-tf201
ro.cm.version=11-20140825-UNOFFICIAL-tf201
ro.cm.releasetype=UNOFFICIAL
ro.sf.lcd_density=160
ro.com.google.clientidbase=android-google
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.boot.emmc=0
ro.boot.carrier=wifi-only
ro.boot.selinux=permissive
ro.boot.serialno=015d0787792bf816
ro.boot.productid=0x00
ro.boot.commchip_id=0
ro.emmc=0
ro.epad.model=TF201
ro.epad.model_id=00
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=tegra
ro.build.id=KTU84Q
ro.build.date=Mon Aug 25 17:12:34 EST 2014
ro.build.date.utc=0
ro.build.host=tsunemori
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=akane
ro.build.display.id=cm_tf201-userdebug 4.4.4 KTU84Q 61a46606a4 test-keys
ro.build.product=tf201
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.4
ro.build.version.codename=REL
ro.build.version.incremental=61a46606a4
ro.build.description=US_epad-user 4.1.1 JRO03C US_epad-10.4.2.18-20121122 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.1.1/JRO03C/US_epad-10.4.2.18-20121122:user/release-keys
ro.build.characteristics=tablet
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.secure=1
ro.zygote.disable_gl_preload=true
ro.carrier=wifi-only
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=EeePad
ro.product.board=cardhu
ro.product.brand=asus
ro.product.model=EPAD
ro.product.device=tf201
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=asus
ro.baseband=unknown
ro.bootmode=unknown
ro.hardware=cardhu
ro.opengles.version=131072
ro.revision=0
ro.serialno=015d0787792bf816
ro.bootloader=unknown
ro.debuggable=1
ro.modversion=11-20140825-UNOFFICIAL-tf201
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
tf.enable=y
net.bt.name=Android
net.change=net.bt.name
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.mischelp=restarting
init.svc.recovery=running
init.svc.setup_adbd=stopped
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
dalvik.vm.heapsize=256m
dalvik.vm.lockprof.threshold=500
dalvik.vm.heapmaxfree=2m
dalvik.vm.heapminfree=512k
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.75
persist.sys.dun.override=0
persist.sys.usb.config=mtp,adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.dalvik.multithread=false
persist.sys.root_access=1
persist.sys.recovery_update=false
persist.tegra.didim.video=5
persist.tegra.nvmmlite=1
service.adb.root=1
keyguard.no_require_sim=true
Formatting /data...
Creating filesystem with parameters:
Size: 30183260160
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7368960
Block groups: 225
Reserved block group size: 1024
Created filesystem with 11/1843200 inodes and 159718/7368960 blocks
dondipietro said:
Hello,
I think I've bricked my TF201... I've installed androwook, as it was continueously rebooting, so I tried from CWM wipe user data.. It never finished.
Now my pad always start in recovery mode. Just de green droid with a rotating shape, no text. Fastboot don't work but adb work so I can see /tmp/recovery.log.
I tried the unbrick method 1a and 1b but no effect ...
When I do :
dd if=/dev/zero of=/dev/block/mmcblk0p4 bs=100 count=1 and press [Enter] => No answer from terminal, wainting for something ...
Could you please give me some advices ... Thank you very much.
Some test I made :
~ # mount -o remount,rw /system
mount -o remount,rw /system
mount: can't find /system in /proc/mounts
~ # mount
mount
rootfs on / type rootfs (rw)
tmpfs on /dev type tmpfs (rw,seclabel,nosuid,relatime,mode=755)
devpts on /dev/pts type devpts (rw,seclabel,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,seclabel,relatime)
selinuxfs on /sys/fs/selinux type selinuxfs (rw,relatime)
tmpfs on /tmp type tmpfs (rw,seclabel,relatime)
tmpfs on /storage type tmpfs (rw,seclabel,relatime,mode=050,gid=1028)
tmpfs on /mnt/secure type tmpfs (rw,seclabel,relatime,mode=700)
tmpfs on /mnt/fuse type tmpfs (rw,seclabel,relatime,mode=775,gid=1000)
/dev/block/mmcblk0p2 on /cache type ext4 (rw,seclabel,nosuid,nodev,relatime,user_xattr,acl,barrier=1,data=orde
~ # cat /etc/fstab
cat /etc/fstab
/dev/block/mmcblk0p2 /cache ext4 rw
/dev/block/mmcblk0p8 /data ext4 rw
/dev/block/mmcblk0p1 /system ext4 rw
/dev/block/mmcblk1p1 /external_sd auto rw
~ # mount system
mount system (hangs)
-----------------------
~ # cat /proc/partitions
cat /proc/partitions
major minor #blocks name
179 0 31039488 mmcblk0
179 1 524288 mmcblk0p1
179 2 438272 mmcblk0p2
179 3 2048 mmcblk0p3
179 4 546304 mmcblk0p4
179 5 5120 mmcblk0p5
179 6 512 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 29475840 mmcblk0p8
179 9 8192 mmcblk0p9
179 10 8192 mmcblk0p10
179 32 2048 mmcblk0boot1
179 16 2048 mmcblk0boot0
~ # uname -a
uname -a
Linux localhost 3.1.10-g46990e1-dirty #1 SMP PREEMPT Mon Aug 25 17:58:29 EST 2014 armv7l GNU/Linux
---------------------------------------------------
Here is my log file :
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Tue Oct 21 07:53:33 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (1280 x 800)
CWM-based Recovery v6.0.5.0
Swipe up/down to change selections.
Swipe to the right for enter.
Swipe to the left for back.
recovery filesystem table
=========================
0 /system ext4 /dev/block/mmcblk0p1 0
1 /cache ext4 /dev/block/mmcblk0p2 0
2 /data ext4 /dev/block/mmcblk0p8 0
3 /storage/sdcard1 auto /devices/platform/sdhci-tegra.0/mmc_host/mmc2 0
4 /storage/usbdisk0 auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1.2 0
5 /storage/usbdisk0 auto /devices/platform/tegra-ehci.2/usb2/2-1/2-1.2 0
6 /storage/usbdisk1 auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1.1 0
7 /storage/usbdisk1 auto /devices/platform/tegra-ehci.2/usb2/2-1/2-1.1 0
8 /storage/usbdisk1 auto /devices/platform/tegra-ehci.2/usb2/2-1/2-1:1 0
9 /storage/usbdisk1 auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1:1 0
10 /storage/sdcard2 auto /devices/platform/tegra-ehci.2/usb1/1-1/1-1.3 0
11 /storage/sdcard2 auto /devices/platform/tegra-ehci.2/usb2/2-1/2-1.3 0
12 /external_sd auto /dev/block/mmcblk1p1 0
13 /misc emmc /dev/block/mmcblk0p3 0
14 /staging ext3 /dev/block/mmcblk0p4 0
15 /recovery emmc /dev/block/mmcblk0p9 0
16 /boot emmc /dev/block/mmcblk0p10 0
17 /tmp ramdisk ramdisk 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!
W:Unable to get recovery.fstab info for /sdcard during fstab generation!
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard1 /storage/sdcard1 0 -
I:110 0 usbdisk0 /storage/usbdisk0 0 -
I:110 0 usbdisk0 /storage/usbdisk0 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 usbdisk1 /storage/usbdisk1 0 -
I:110 0 sdcard2 /storage/sdcard2 0 -
I:110 0 sdcard2 /storage/sdcard2 0 -
I:200 0 Volumes listed.
Irocessing arguments.
I:Boot command: boot-recovery
I:Got arguments from boot message
I:Checking arguments.
I:device_recovery_start()
Command: "recovery" "--wipe_data"
ro.bq.gpu_to_cpu_unsupported=1
ro.cm.device=tf201
ro.cm.display.version=11-20140825-UNOFFICIAL-tf201
ro.cm.version=11-20140825-UNOFFICIAL-tf201
ro.cm.releasetype=UNOFFICIAL
ro.sf.lcd_density=160
ro.com.google.clientidbase=android-google
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.android.wifi-watchlist=GoogleGuest
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.boot.emmc=0
ro.boot.carrier=wifi-only
ro.boot.selinux=permissive
ro.boot.serialno=015d0787792bf816
ro.boot.productid=0x00
ro.boot.commchip_id=0
ro.emmc=0
ro.epad.model=TF201
ro.epad.model_id=00
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=tegra
ro.build.id=KTU84Q
ro.build.date=Mon Aug 25 17:12:34 EST 2014
ro.build.date.utc=0
ro.build.host=tsunemori
ro.build.tags=test-keys
ro.build.type=userdebug
ro.build.user=akane
ro.build.display.id=cm_tf201-userdebug 4.4.4 KTU84Q 61a46606a4 test-keys
ro.build.product=tf201
ro.build.selinux=1
ro.build.version.sdk=19
ro.build.version.release=4.4.4
ro.build.version.codename=REL
ro.build.version.incremental=61a46606a4
ro.build.description=US_epad-user 4.1.1 JRO03C US_epad-10.4.2.18-20121122 release-keys
ro.build.fingerprint=asus/US_epad/EeePad:4.1.1/JRO03C/US_epad-10.4.2.18-20121122:user/release-keys
ro.build.characteristics=tablet
ro.config.alarm_alert=Hassium.ogg
ro.config.notification_sound=Argon.ogg
ro.secure=1
ro.zygote.disable_gl_preload=true
ro.carrier=wifi-only
ro.cmlegal.url=http://www.cyanogenmod.org/docs/privacy
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.name=EeePad
ro.product.board=cardhu
ro.product.brand=asus
ro.product.model=EPAD
ro.product.device=tf201
ro.product.locale.region=US
ro.product.locale.language=en
ro.product.manufacturer=asus
ro.baseband=unknown
ro.bootmode=unknown
ro.hardware=cardhu
ro.opengles.version=131072
ro.revision=0
ro.serialno=015d0787792bf816
ro.bootloader=unknown
ro.debuggable=1
ro.modversion=11-20140825-UNOFFICIAL-tf201
ro.rommanager.developerid=cyanogenmod
ro.factorytest=0
ro.setupwizard.enterprise_mode=1
tf.enable=y
net.bt.name=Android
net.change=net.bt.name
init.svc.adbd=running
init.svc.vold=running
init.svc.healthd=running
init.svc.ueventd=running
init.svc.mischelp=restarting
init.svc.recovery=running
init.svc.setup_adbd=stopped
wifi.interface=wlan0
wifi.supplicant_scan_interval=15
dalvik.vm.heapsize=256m
dalvik.vm.lockprof.threshold=500
dalvik.vm.heapmaxfree=2m
dalvik.vm.heapminfree=512k
dalvik.vm.dexopt-flags=m=y
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.75
persist.sys.dun.override=0
persist.sys.usb.config=mtp,adb
persist.sys.dalvik.vm.lib=libdvm.so
persist.sys.dalvik.multithread=false
persist.sys.root_access=1
persist.sys.recovery_update=false
persist.tegra.didim.video=5
persist.tegra.nvmmlite=1
service.adb.root=1
keyguard.no_require_sim=true
Formatting /data...
Creating filesystem with parameters:
Size: 30183260160
Block size: 4096
Blocks per group: 32768
Inodes per group: 8192
Inode size: 256
Journal blocks: 32768
Label:
Blocks: 7368960
Block groups: 225
Reserved block group size: 1024
Created filesystem with 11/1843200 inodes and 159718/7368960 blocks
Click to expand...
Click to collapse
Sounds like to me that if you see a droid with a spinning wheel or such that is doing a factory reset..
Plug it into power and leave it for as long as it takes, could take hours ...
Thx Josh
I have the similar problem with my tf201
I have bricked my tf201 after install twrp 2.6.8 and now, it boot only in twrp and i can't acces in the internal sdcard. I have adb and apx mode but no fastboot.
Have you a solution for me please?
jzato
jzato said:
I have bricked my tf201 after install twrp 2.6.8 and now, it boot only in twrp and i can't acces in the internal sdcard. I have adb and apx mode but no fastboot.
Have you a solution for me please?
jzato
Click to expand...
Click to collapse
You can get to fastboot by typing adb reboot bootloader while in recovery with adb access.
Then follow these instructions but substitute the tf300 rom for the tf201 one.
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
flumpster said:
You can get to fastboot by typing adb reboot bootloader while in recovery with adb access.
Then follow these instructions but substitute the tf300 rom for the tf201 one.
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
Click to expand...
Click to collapse
When i type adb reboot bootloader, the tablet reboot in black screen but I can't access fastboot mode.
jzato said:
When i type adb reboot bootloader, the tablet reboot in black screen but I can't access fastboot mode.
Click to expand...
Click to collapse
Maybe this thread will help ?
http://forum.xda-developers.com/transformer-prime/help/guide-t2864946
Thx Josh
lj50036 said:
Maybe this thread will help ?
http://forum.xda-developers.com/transformer-prime/help/guide-t2864946
Thx Josh
Click to expand...
Click to collapse
I already apply this tuto but it doesn't work for me. I'm still un this case : apx ans adb OK, no fastboot mode and un recovery twrp can't do anything because it can't mount the internal storage.
jzato said:
I already apply this tuto but it doesn't work for me. I'm still un this case : apx ans adb OK, no fastboot mode and recovery twrp can't do anything because it can't mount the internal storage.
Click to expand...
Click to collapse
Here is my recovery log file
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP [email protected] on Sun May 17 15:09:31 2015
(pid 118)
BOARD_HAS_NO_REAL_SDCARD := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/platform/usb_mass_storage/lun0/file' does not exist, USB storage mode disabled
TW_INCLUDE_CRYPTO := true
I:Found brightness file at '/sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
Starting the UI...Pixel format: 1280x800 @ 16bpp
Pixel format: BGR_565
Not using qualcomm overlay, 'tegra_fb'
framebuffer: fd 4 (1280 x 800)
I:Scaling the curtain width 0.666667x and height 0.666667x
=> Linking mtab
Renaming regular /etc/recovery.fstab -> /etc/recovery.fstab.bak
Moving /etc/twrp.fstab -> /etc/recovery.fstab
=> Processing recovery.fstab
Irocessing '/system'
Irocessing '/cache'
I:Recreating /cache/recovery folder.
Irocessing '/misc'
Irocessing '/staging'
Irocessing '/data'
I:Setting up '/data' as data/media emulated storage.
I:Created '/sdcard' folder.
I:Can't probe device /dev/block/mmcblk0p8
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p8', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p8
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p8', current file system: 'ext4'
get_crypt_ftr_info crypto key location: 'footer'
Cannot read real block device footer
E:Could not mount /data and unable to find crypto footer.
I:Can't probe device /dev/block/mmcblk0p8
E:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p8', current file system: 'ext4'
E:Unable to recreate /data/media folder.
Irocessing '/recovery'
Irocessing '/boot'
Irocessing '/external_sdcard'
I:Created '/external_sdcard' folder.
Irocessing '/external_data'
I:Created '/external_data' folder.
Irocessing '/external_system'
I:Created '/external_system' folder.
Irocessing '/dock_sdcard'
I:Created '/dock_sdcard' folder.
I:Backup folder set to '/data/media/TWRP/BACKUPS/015c7b47c6540e04'
I:Settings storage is '/data/media'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p1
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p1', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p8
jzato said:
Here is my recovery log file
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting TWRP [email protected] on Sun May 17 15:09:31 2015
(pid 118)
BOARD_HAS_NO_REAL_SDCARD := true
RECOVERY_SDCARD_ON_DATA := true
I:Lun file '/sys/devices/platform/usb_mass_storage/lun0/file' does not exist, USB storage mode disabled
TW_INCLUDE_CRYPTO := true
I:Found brightness file at '/sys/devices/platform/pwm-backlight/backlight/pwm-backlight/brightness'
I:TWFunc::Set_Brightness: Setting brightness control to 255
Starting the UI...Pixel format: 1280x800 @ 16bpp
Pixel format: BGR_565
Not using qualcomm overlay, 'tegra_fb'
framebuffer: fd 4 (1280 x 800)
I:Scaling the curtain width 0.666667x and height 0.666667x
=> Linking mtab
Renaming regular /etc/recovery.fstab -> /etc/recovery.fstab.bak
Moving /etc/twrp.fstab -> /etc/recovery.fstab
=> Processing recovery.fstab
Irocessing '/system'
Irocessing '/cache'
I:Recreating /cache/recovery folder.
Irocessing '/misc'
Irocessing '/staging'
Irocessing '/data'
I:Setting up '/data' as data/media emulated storage.
I:Created '/sdcard' folder.
I:Can't probe device /dev/block/mmcblk0p8
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p8', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p8
I:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p8', current file system: 'ext4'
get_crypt_ftr_info crypto key location: 'footer'
Cannot read real block device footer
E:Could not mount /data and unable to find crypto footer.
I:Can't probe device /dev/block/mmcblk0p8
E:Unable to mount '/data'
I:Actual block device: '/dev/block/mmcblk0p8', current file system: 'ext4'
E:Unable to recreate /data/media folder.
Irocessing '/recovery'
Irocessing '/boot'
Irocessing '/external_sdcard'
I:Created '/external_sdcard' folder.
Irocessing '/external_data'
I:Created '/external_data' folder.
Irocessing '/external_system'
I:Created '/external_system' folder.
Irocessing '/dock_sdcard'
I:Created '/dock_sdcard' folder.
I:Backup folder set to '/data/media/TWRP/BACKUPS/015c7b47c6540e04'
I:Settings storage is '/data/media'
Updating partition details...
I:Can't probe device /dev/block/mmcblk0p1
E:Unable to mount '/system'
I:Actual block device: '/dev/block/mmcblk0p1', current file system: 'ext4'
I:Can't probe device /dev/block/mmcblk0p8
Click to expand...
Click to collapse
Well that is no good at all ....
Shoot me a hangouts at [email protected]
If you would like to look into this a bit more....
Thx Josh
lj50036 said:
Well that is no good at all ....
Shoot me a hangouts at [email protected]
If you would like to look into this a bit more....
Thx Josh
Click to expand...
Click to collapse
Cheers mate, I don't even have this device any more so troubleshooting is a nightmare for me. People just keep flashing random recoveries that are not compatible with the bootloader and I don't think it will ever end. lol. Looking at that log tho is this anything to do with the new filesystem in katkiss being incompatible with whatever twrp he has installed?
Swap Internal and External sdcard of ANY Android phone.
After many hours searching information to unbrick my asus TF201, I found this :
http://forum.xda-developers.com/showthread.php?t=2346389 (Swap Internal SD card and External SD card of most of the Android™ device)
Is it possible to do that for the TF201?
My tf201 boot only in twrp recovery mode and i can't access to the internal storage : can't flash anymore.
I can access apx and adb mode only, no fastboot.
If you can help me...
Jzato.
jzato said:
After many hours searching information to unbrick my asus TF201, I found this :
http://forum.xda-developers.com/showthread.php?t=2346389 (Swap Internal SD card and External SD card of most of the Android™ device)
Is it possible to do that for the TF201?
My tf201 boot only in twrp recovery mode and i can't access to the internal storage : can't flash anymore.
I can access apx and adb mode only, no fastboot.
If you can help me...
Jzato.
Click to expand...
Click to collapse
Did I already try to help you ?
Thx Josh
lj50036 said:
Did I already try to help you ?
Thx Josh
Click to expand...
Click to collapse
Yes you have already helped me and your verdict: probably defective internal storage.
I thought maybe it was possible to replace the internal storage by the sdcard.
Thank you again for the time you have given me.
HI
I'm try to build CWM for my ASUS Fonepad 7 real name is "K00E"
It's a Intel Atom based device
but not supported by cm yet
I followed some guild with only shows you very sample commands that for arm cpu
there is no guild for K00E yet
but I believe I must do the following
1. setup the device files for cm source. or I have to create one BUT HOW????
or I can modify another intel atom device? is there any guide for that?
2. find the partition for boot and recovery but I can't
here is the only info I've found
Code:
lrwxrwxrwx root root 2014-12-26 00:40 APD -> /dev/block/mmcblk0p7
lrwxrwxrwx root root 2014-12-26 00:40 cache -> /dev/block/mmcblk0p6
lrwxrwxrwx root root 2014-12-26 00:40 config -> /dev/block/mmcblk0p5
lrwxrwxrwx root root 2014-12-26 00:40 data -> /dev/block/mmcblk0p9
lrwxrwxrwx root root 2014-12-26 00:40 factory -> /dev/block/mmcblk0p3
lrwxrwxrwx root root 2014-12-26 00:40 panic -> /dev/block/mmcblk0p2
lrwxrwxrwx root root 2014-12-26 00:40 reserved -> /dev/block/mmcblk0p1
lrwxrwxrwx root root 2014-12-26 00:40 spare -> /dev/block/mmcblk0p4
lrwxrwxrwx root root 2014-12-26 00:40 system -> /dev/block/mmcblk0p8
mount
Code:
[email protected]:/proc # cat /cache/recovery/last_log
__bionic_open_tzdata: couldn't find any tzdata when looking for localtime!
__bionic_open_tzdata: couldn't find any tzdata when looking for GMT!
__bionic_open_tzdata: couldn't find any tzdata when looking for posixrules!
Starting recovery on Thu Dec 25 15:17:16 2014
recovery filesystem table
=========================
0 /reserved hidden /dev/block/mmcblk0p1 0
1 /panic raw /dev/block/mmcblk0p2 0
2 /factory ext4 /dev/block/mmcblk0p3 0
3 /spare ext4 /dev/block/mmcblk0p4 0
4 /config ext4 /dev/block/mmcblk0p5 0
5 /cache ext4 /dev/block/mmcblk0p6 0
6 /APD ext4 /dev/block/mmcblk0p7 0
7 /system ext4 /dev/block/mmcblk0p8 0
8 /data ext4 /dev/block/mmcblk0p9 -16384
9 /sdcard vfat /dev/block/mmcblk1p1 0
10 /tmp ramdisk ramdisk 0
E:Cannot load volume /misc!
I:Got arguments from /cache/recovery/command
E:Cannot load volume /misc!
locale is [zh_CN]
failed to read font: res=-1
framebuffer: fd 4 (800 x 1280)
installing_text: zh_CN (240 x 38 @ 1818)
erasing_text: zh_CN (128 x 38 @ 1521)
no_command_text: zh_CN (92 x 38 @ 1521)
error_text: zh_CN (98 x 38 @ 1521)
Command: "/sbin/recovery" "--update_package=/cache/update.zip"
bt.version.driver=V18.22.38.2.0
ro.sf.lcd_density=213
ro.adb.secure=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.com.widevine.cachesize=16777216
ro.ime.lowmemory=true
ro.ril.status.polling.enable=0
ro.asus.ui=1.0
ro.boot.mode=fota
ro.boot.spid=0000:0000:0000:0002:0000:000e
ro.boot.wakesrc=05
ro.boot.hardware=redhookbay
ro.boot.serialno=Medfield871F1A54
ro.boot.bootmedia=sdcard
ro.epad.model=K00E
ro.hwui.texture_cache_size=20.0f
ro.hwui.text_large_cache_width=2048
ro.hwui.text_small_cache_width=1024
ro.hwui.text_large_cache_height=256
ro.hwui.text_small_cache_height=256
ro.hwui.texture_cache_flushrate=0.75f
ro.spid.gps.pmm=enabled
ro.spid.gps.tty=ttyMFD3
ro.wifi.channels=
ro.allow.mock.location=0
ro.board.platform=clovertrail
ro.build.id=KVT49L
ro.build.app.version=044000263_201405210029
ro.build.csc.version=CN_ME372CG_V6.5.4
ro.build.asus.sku=CN
ro.build.asus.version=6.5.4.0
ro.build.asus.version.pensdk=1
ro.build.date=Wed Oct 29 14:26:06 CST 2014
ro.build.date.utc=1414563966
ro.build.host=mec13
ro.build.tags=release-keys
ro.build.type=user
ro.build.user=
ro.build.display.id=KVT49L.CN_epad-V6.5.4-20141029
ro.build.product=K00E
ro.build.version.sdk=19
ro.build.version.release=4.4.2
ro.build.version.codename=REL
ro.build.version.incremental=CN_epad-V6.5.4-20141029
ro.build.description=CN_epad-user 4.4.2 KVT49L CN_epad-V6.5.4-20141029 release-keys
ro.build.fingerprint=asus/CN_epad/K00E:4.4.2/KVT49L/CN_epad-V6.5.4-20141029:user/release-keys
ro.build.characteristics=tablet
ro.config.hwrlib=T9_x86
ro.config.xt9ime.max_subtype=7
ro.config.ringtone=Festival.ogg
ro.config.alarm_alert=BusyBugs.ogg
ro.config.personality=compat_layout
ro.config.newmail_sound=NewMail.ogg
ro.config.sentmail_sound=SentMail.ogg
ro.config.notification_sound=NewMessage.ogg
ro.config.calendaralert_sound=CalendarEvent.ogg
ro.secure=1
ro.system.id=2
ro.system.simtype=1
ro.tether.denied=
ro.carrier=unknown
ro.contact.simtype=1
ro.product.cpu.abi=x86
ro.product.cpu.abi2=armeabi-v7a
ro.product.oem=ASUS
ro.product.asus=K00E
ro.product.name=CN_epad
ro.product.board=EeePad
ro.product.brand=asus
ro.product.model=K00E
ro.product.device=K00E
ro.product.locale.region=CN
ro.product.locale.language=zh
ro.product.carrier=CN-K00E-CN_epad
ro.product.manufacturer=asus
ro.sensors.mapper=scale-pr1
ro.withISP=1
ro.baseband=unknown
ro.bootmode=fota
ro.hardware=redhookbay
ro.opengles.version=131072
ro.revision=0
ro.bluetooth.le=0
ro.flashless=0
ro.streaming.video.drs=true
ro.bootloader=unknown
ro.debuggable=0
ro.factorytest=0
ro.factory_mode=0
ro.blankphone_id=1
ro.additionalbutton.operation=0
rs.gpu.rsIntrinsic=0
rs.gpu.filterscript=0
rs.gpu.renderscript=0
drm.service.enabled=true
gps.version.driver=17.19.13.194641
gsm.net.interface=rmnet0
net.bt.name=Android
net.change=net.bt.name
ril.agpschannel=/dev/gsmtty7
sys.scu.version=20.3E
sys.usb.config=adb
sys.asus.ota.partition=1
sys.ia32.version=00.57
sys.ifwi.version=54.53
sys.punit.version=A1.40
sys.suppia32.version=00.57
sys.valhooks.version=54.52
init.svc.adbd=running
init.svc.ueventd=running
init.svc.partlink=stopped
init.svc.recovery=running
init.svc.thermald=running
init.svc.watchdogd=running
panel.physicalWidthmm=94
panel.physicalHeightmm=151
dalvik.vm.heapsize=256m
dalvik.vm.heapmaxfree=8m
dalvik.vm.heapminfree=4m
dalvik.vm.heapstartsize=8m
dalvik.vm.heapgrowthlimit=96m
dalvik.vm.stack-trace-file=/data/anr/traces.txt
dalvik.vm.heaptargetutilization=0.75
dalvik.jit.code_cache_size=1048576
persist.gps.ignore_rom_alm=0
persist.sys.usb.config=mtp
persist.sys.dalvik.vm.lib=libdvm.so
persist.tcs.config_name=XMM6360_CONF_1
persist.tel.hot_swap.support=true
persist.asus.cb.gcf.mode=0
persist.asus.message.gcf.mode=0
persist.asus.message.debug=0
persist.asus.mupload.enable=0
persist.asus.autoupload.enable=0
persist.radio.ril_modem_state=1
persist.system.at-proxy.mode=0
persist.logtool.cos.logging=0
persist.logtool.gps.loglv=0
persist.logtool.pos.logging=0
persist.logtool.ros.logging=0
persist.logtool.upi.loglv=0
persist.logtool.usb.switch=0
persist.logtool.uart=0
persist.logtool.audio.logging=0
persist.logtool.modem.cd=0
persist.logtool.modem.num=5
persist.logtool.modem.level=3
persist.logtool.modem.logging=0
persist.logtool.modem.bplogsize=0
persist.logtool.touch.logrd=0
persist.logtool.touch.logging=0
persist.logtool.logging=0
persist.logtool.storage.type=0
persist.logtool.crashlogd.en=0
persist.logtool.maxcrashlog=13
persist.dual_sim=0
persist.ril-daemon.disable=0
persist.telproviders.debug=0
persist.dynamic-data-sim=reboot
keyguard.no_require_sim=true
I:Install package /cache/update.zip
Finding update package...
I:Update package location: /cache/update.zip
Opening update package...
I:read key e=3 hash=20
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1738 bytes; signature 1720 bytes from end
I:whole-file signature verified against key 0 for /cache/update.zip
I:verify_file returned 0
Installing update...
I:Installing update /cache/update.zip...
I:Extract and run update-binary
Mounting system...
Copying files...
Setting permissions...
Cleaning up...
script succeeded: result was [/system]I:Saving locale "zh_CN"
AND I downloaded the kernel source from ASUS would that help?
the boot.img from stock rom can't be unpacked.
hi there
do u fine any thing??
for k00e
A.Rahman.A said:
hi there
do u fine any thing??
for k00e
Click to expand...
Click to collapse
you don't have to build for your own now
try here
http://forum.xda-developers.com/android/development/root-asus-fonepad-7-k00e-me372cg-t2977796