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.
Related
Hi, I was using cyanogenmod 10.1 with encryption. After I updated to 10.2 nigthly build, the camera app says that could not access storage, f-droid stopped to work and every other app had the same problem.
I read a lot of topics here and did this:
- Flashed new CMW,
- Flashed new rom (cm 10.1, android 4.2.1);
- Tried other sd card;
- In CMW tried to mount & format emmc (error)
It still doesn't recognize my internal sd. And now I don't know what to do... :crying:
Here's my fstab
Code:
[email protected]:/ # cat fstab.smdk4210
cat fstab.smdk4210
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
# data partition must be located at the bottom for supporting device encryption
/dev/block/mmcblk0p9 /system ext4 ro,noatime wait
/dev/block/mmcblk0p7 /cache ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p1 /efs ext4 noatime,nosuid,nodev,journal_async_commit,errors=panic wait,check_spo
/dev/block/mmcblk0p10 /data ext4 noatime,nosuid,nodev,discard,noauto_da_alloc,journal_async_commit,errors=panic wait,check_spo,encryptable=/efs/metadata
/dev/block/mmcblk0p12 /preload ext4 noatime,nosuid,nodev,journal_async_commit wait
# vold-managed volumes ("block device" is actually a sysfs devpath)
/devices/platform/dw_mmc/mmc_host/mmc0/mmc0 /storage/sdcard0 auto defaults voldmanaged=sdcard0:11,nonremovable
/devices/platform/s3c-sdhci.2/mmc_host/mmc1 /storage/sdcard1 auto defaults voldmanaged=sdcard1:auto
/devices/platform/s3c_otghcd/usb /storage/usbdisk0 auto defaults voldmanaged=usbdisk0:auto
# recovery
/dev/block/mmcblk0p5 /boot emmc defaults recoveryonly
/dev/block/mmcblk0p6 /recovery emmc defaults recoveryonly
/dev/block/mmcblk0p11 /emmc auto defaults recoveryonly
/dev/block/mmcblk1p1 /sdcard auto defaults recoveryonly
Code:
[email protected]:/ # cat fstab.goldfish
cat fstab.goldfish
# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK
/dev/block/mtdblock0 /system ext4 ro,barrier=1 wait
/dev/block/mtdblock1 /data ext4 noatime,nosuid,nodev,barrier=1,nomblk_io_submit wait,check
/dev/block/mtdblock2 /cache ext4 noatime,nosuid,nodev,nomblk_io_submit,errors=panic wait,check
/devices/platform/goldfish_mmc.0 /storage/sdcard vfat defaults voldmanaged=sdcard:auto
[email protected]:/ #
Code:
[email protected]:/ # df
df
Filesystem Size Used Free Blksize
/dev 395.3M 48.0K 395.2M 4096
/storage 395.3M 0.0K 395.3M 4096
/mnt/secure 395.3M 0.0K 395.3M 4096
/mnt/asec 395.3M 0.0K 395.3M 4096
/mnt/obb 395.3M 0.0K 395.3M 4096
/mnt/fuse 395.3M 0.0K 395.3M 4096
/system 503.9M 287.4M 216.5M 4096
/cache 98.4M 53.5M 44.9M 4096
/efs 19.7M 8.2M 11.5M 4096
/data 2.0G 41.6M 1.9G 4096
/preload 503.9M 8.4M 495.6M 4096
/storage/sdcard1 14.6G 1.2G 13.4G 8192
Hello, i'm getting error when i try to install new zip file from CWM, infact recovery logs write that the SDCard partition is unmounted.
When i try to mount the SDCard partition i get this log:
Code:
__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 Wed Jan 15 19:05:13 2014
framebuffer: fd 4 (480 x 800)
CWM-based Recovery v6.0.4.5
recovery filesystem table
=========================
0 /boot emmc /dev/block/mmcblk0p11 0
1 /recovery emmc /dev/block/mmcblk0p12 0
2 /vendor ext4 /dev/block/mmcblk0p14 0
3 /sdcard vfat /dev/block/mmcblk0p17 0
4 /external_sd vfat /dev/block/mmcblk1p1 0
5 /system ext4 /dev/block/mmcblk0p13 0
6 /system/vendor ext4 /dev/block/mmcblk0p14 0
7 /cache ext4 /dev/block/mmcblk0p15 0
8 /data ext4 /dev/block/mmcblk0p16 0
9 /storage/sdcard0 auto /devices/platform/s3c-sdhci.0/mmc_host/mmc0 0
10 /storage/sdcard1 auto /devices/platform/s3c-sdhci.2/mmc_host/mmc1 0
11 /storage/usbdisk auto /devices/platform/s3c-usbgadget 0
12 /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 /sd-ext during fstab generation!
I:Completed outputting fstab.
I:Connected to Vold..
I:110 0 sdcard0 /storage/sdcard0 1
I:110 0 sdcard1 /storage/sdcard1 1
I:110 0 usbdisk /storage/usbdisk 0
I:200 0 Volumes listed.
I:Processing arguments.
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.serialno=c0890a09e2418be
ro.serialno=c0890a09e2418be
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=venturi
ro.revision=0
ro.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.adb.secure=0
persist.sys.root_access=1
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=mass_storage,adb
ro.vold.switchablepair=/storage/sdcard0,/storage/sdcard1
persist.sys.vold.switchexternal=0
ro.bq.gpu_to_cpu_unsupported=1
ro.build.id=JLS36I
ro.build.display.id=pac_venturi-userdebug 4.3.1 JLS36I eng..20131128.092037 test-keys
ro.build.version.incremental=eng..20131128.092037
ro.build.version.sdk=18
ro.build.version.codename=REL
ro.build.version.release=4.3.1
ro.build.date=Thu Nov 28 09:22:18 EST 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=YP-G70
ro.product.brand=Samsung
ro.product.name=YP-G70
ro.product.device=YP-G70
ro.product.board=s5pc110
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Samsung
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=s5pc110
ro.build.product=YP-G70
ro.build.description=YP-G70-user 2.3.5 GINGERBREAD UEKI8 release-keys
ro.build.fingerprint=samsung/YP-G70/YP-G70:2.3.5/GINGERBREAD/UEKI8:user/release-keys
ro.build.characteristics=tablet
ro.cm.device=venturi
ro.sf.lcd_density=240
ro.config.ringtone=Themos.ogg
ro.config.notification_sound=Proxima.ogg
ro.config.alarm_alert=Cesium.ogg
ro.pac.version=4.3.Build-1
ro.pacrom.version=pac_venturi_4.3.Build-1_20131128-092037
ro.modversion=pa_venturi-3.99-RC2-28NOV2013-092037
ro.pa.family=pa_hdpi
ro.pa.version=3.99-RC2
ro.papref.revision=1
ro.aokp.version=venturi_jb-mr2
ro.pacstats.url=http://stats.pac-rom.com
ro.pacstats.name=PAC-man
ro.pacstats.version=4.3.Build-1
ro.pacstats.tframe=1
ro.rommanager.developerid=cyanogenmod
ro.com.google.clientidbase=android-google
keyguard.no_require_sim=true
ro.url.legal=http://www.google.com/intl/%s/mobile/android/basic/phone-legal.html
ro.url.legal.android_privacy=http://www.google.com/intl/%s/mobile/android/basic/privacy.html
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.build.selinux=1
ro.cm.version=10.2-20131128-UNOFFICIAL-venturi
ro.carrier=unknown
ro.opengles.version=131072
wifi.interface=wlan0
ro.com.google.locationfeatures=1
ro.com.google.networklocation=1
ro.kernel.android.checkjni=0
dalvik.vm.checkjni=false
ro.vold.umsdirtyratio=20
dalvik.vm.dexopt-data-only=1
dalvik.vm.heapstartsize=5m
dalvik.vm.heapgrowthlimit=48m
dalvik.vm.heapsize=128m
dalvik.vm.heaptargetutilization=0.25
dalvik.vm.heapminfree=512k
dalvik.vm.heapmaxfree=2m
ro.hwui.disable_scissor_opt=true
dalvik.vm.lockprof.threshold=500
dalvik.vm.dexopt-flags=m=y
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
init.svc.ueventd=running
init.svc.recovery=running
init.svc.setup_adbd=stopped
init.svc.vold=running
sys.usb.config=mass_storage,adb
init.svc.adbd=running
sys.usb.state=mass_storage,adb
service.adb.root=1
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mmcblk0p17 (No such file or directory)
Error mounting /sdcard!
I:Can't partition non mmcblk device: /devices/platform/s3c-sdhci.0/mmc_host/mmc0
I:Can't partition non-vfat: /external_sd (vfat)
I:Can't partition non mmcblk device: /devices/platform/s3c-sdhci.2/mmc_host/mmc1
I:605 Volume sdcard0 /storage/sdcard0 state changed from 1 (Idle-Unmounted) to 3 (Checking)
I:/storage/sdcard0: Checking
I:605 Volume sdcard0 /storage/sdcard0 state changed from 3 (Checking) to 4 (Mounted)
I:/storage/sdcard0: Mounted
I:200 0 volume operation succeeded
Can someone help me?
Looks like your sd card isnt be recognized properly. Have you tried directly putting it into your computer to see if it is recognized? You might also want to try formatting your sd card from your computer.
iurnait said:
Looks like your sd card isnt be recognized properly. Have you tried directly putting it into your computer to see if it is recognized? You might also want to try formatting your sd card from your computer.
Click to expand...
Click to collapse
When i told about SDCard partition i mean Internal Memory of the phone, anyway the Computer can recognize properly the Internal Memory and the ExtSDCard. I formatted both of them with the format utility of windows and after the Panasonic SDCard Formatter.
The CWM can't wipe/format them.
My bad. Try sideloading another rom like the latest pac nightly or cm11 and restart into recovery.
iurnait said:
My bad. Try sideloading another rom like the latest pac nightly or cm11 and restart into recovery.
Click to expand...
Click to collapse
what do you mean with sideloading?
Hello. I need some help with installing custom ROM on my phone please. I am using QMobile Noir A500. You see, I rooted it some time ago and installed a custom ROM which ran just fine but then I again wanted to flash another ROM so I downloaded it and alongwith it a .zip which was supposed tto change the boot logo of my phon. Since i flashed this file I haven't been able to flash any ROM whatsoever. I was able to generate a report of it using ROM Manager which is as follows.
Starting recovery on Wed Aug 20 15:28:17 2014
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 854)
ioctl(): blank: Invalid argument
ioctl(): blank: Invalid argument
CWM automade 17.08.2013 21:03:08
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 /emmc vfat /dev/block/mmcblk0p8 (null) 0
8 /sdcard vfat /dev/block/mmcblk1p1 (null) 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.114 933
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=mt6589
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=restarting
sys.usb.state=mass_storage,adb
I:Checking for extendedcommand...
I:Running extendedcommand...
Waiting for SD Card to mount (20s)
SD Card mounted...
Verifying SD Card marker...
I:Running script:
I:
run_program("/sbin/cp", "-R", "/cache/recovery", "/tmp/recovery");
ui_print("ROM Manager Version 5.5.3.7");
ui_print("August 20, 2014");
ui_print("Preparing to install ROM...");
run_program("/cache/dowipedalvikcache.sh");
mount("/system");
run_program("/sbin/chmod", "+x", "/tmp/recovery/11-rommanager.sh");
run_program("/tmp/recovery/11-rommanager.sh", "place");
run_program("/sbin/umount", "/system");
assert(install_zip("/sdcard/note3rom.zip"));
parse returned 0; 0 errors encountered
about to run program [/sbin/cp] with 4 args
ROM Manager Version 5.5.3.7
August 20, 2014
Preparing to install ROM...
about to run program [/cache/dowipedalvikcache.sh] with 1 args
mount: mounting /dev/block/mmcblk0p6 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk1p2 on /sd-ext failed: No such file or directory
umount: can't umount /sd-ext: Invalid argument
run_program: child exited with status 1
about to run program [/sbin/chmod] with 3 args
about to run program [/tmp/recovery/11-rommanager.sh] with 2 args
mount: mounting /dev/block/mmcblk0p5 on /system failed: Device or resource busy
about to run program [/sbin/umount] with 2 args
-- Installing: /sdcard/note3rom.zip
Finding update package...
I:Update location: /sdcard/note3rom.zip
Opening update package...
minzip: Invalid entries=2080 offset=452264
Please I need the help.
Phone = HTC Wildfire S
Rooted = yes
CWM version = v5.0.2.6
Phone Status = screen broken but display working. USB debugging not enabled in fast boot. OTG mouse not supported. Volume buttons and power button working. Screen does not respond to any finger gestures. Pattern lock enabled upon booting.
Need Help = Enable USB debugging to remove lock. Need to extract all data from phone, in particular SMS messages, phone calls, contacts.
Notes = Google accounts do not have the contacts backed up.
ADB working in Recovery Mode only at the moment with Andriod Studio v.1.0.1
Tried to edit default.prop, build.prop and settings.db to enable USB debugging for ADB.
Checked premissions and ownership of those files before and after pulling/editing/pushing.
Unclear if those are the exact files and paths as I mounted all available files.
Copied SD card contents but cannot find contacts, SMS etc. Only recovered photos, videos, music. etc.
----------------------------------------------------------------------------
BEFORE and AFTER mounting in ADB Recovery Mode:
Code:
~ # mount | grep a
mount | grep a
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nodev,noatime,nodiratime)
Code:
~ # mount -a
mount -a
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
Code:
~ # mount | grep a
mount | grep a
tmpfs on /dev type tmpfs (rw,relatime,mode=755)
devpts on /dev/pts type devpts (rw,relatime,mode=600)
proc on /proc type proc (rw,relatime)
sysfs on /sys type sysfs (rw,relatime)
/dev/block/mtdblock4 on /cache type yaffs2 (rw,nodev,noatime,nodiratime)
/dev/block/mtdblock5 on /data type yaffs2 (rw,relatime)
/dev/block/mtdblock3 on /system type yaffs2 (rw,relatime)
/dev/block/mmcblk0p1 on /sdcard type vfat (rw,relatime,fmask=0000,dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=mixed,errors=remount-ro)
----------------------------------------------------------------------------
Already deleted /data/system/gesture.key file.
Droid at screen works in ADB Recovery only.
Android Control works in ADB Recovery only.
Some settings that I have edited (including some persists) have been changed back upon rebooting while others "persist" as they should.
For example in the settings.db file, under the secure group, I have switched:
adb_enabled from 0 to 1
htc_error_report_setting from 1 to 0
Saved it, pushed the file, corrected permissions, but after rebooting:
adb_enabled = 0
htc_error_report_setting = 0
I have tried
Code:
persist.service.adb.enable=1
persist.service.debuggable=1
in default.prop and build.prop
So some things can be changed while others are over-written.
I managed to get bluetooth enabled this way, fully shown by the little bluetooth icon on the phone screen upon booting up. I do have a bluetooth dongle plugged into the PC. Can I somehow use this usb dongle on the PC to control the phone screen? Not sure how to pair or even if the wired keyboard and mouse will "use" the bluetooth dongle.
I feel like I am missing one or two things just to get this phone booted up with USB Debugging ON.
PLEASE HELP!
Information Update of Recovery CWM log.
To prevent spam on the XDA forums, ALL new users prevented from posting outside links in their messages. After approximately 10 posts, you will be able to post outside links. Thank you for understanding!
Click to expand...
Click to collapse
Code:
Starting recovery on Sun Jan 6 13:10:18 1980
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (320 x 480)
CWM-based Recovery v5.0.2.6
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /boot mtd boot (null)
2 /cache yaffs2 cache (null)
3 /data yaffs2 userdata (null)
4 /misc mtd misc (null)
5 /recovery mtd recovery (null)
6 /sdcard vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0
7 /system yaffs2 system (null)
8 /sd-ext auto /dev/block/mmcblk0p2 (null)
I:Completed outputting fstab.
I:Processing arguments.
Fixing execute permissions for /cache
mtd: successfully wrote block at c6de400000000
I:Set boot command "boot-recovery"
I:Checking arguments.
I:device_recovery_start()
Command: "/sbin/recovery"
ro.secure=0
ro.allow.mock.location=1
ro.debuggable=1
persist.service.adb.enable=1
ro.build.id=GRI40
ro.build.display.id=GRJ90
ro.build.version.incremental=eng.alquez.20111010.014632
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.7
ro.build.date=pon, 10 paź 2011, 01:47:33 CEST
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=alquez
ro.build.host=Gear2ng
ro.build.tags=test-keys
ro.product.model=HTC Wildfire S
ro.product.brand=htc_wwe
ro.product.name=htc_marvel
ro.product.device=marvel
ro.product.board=marvel
ro.product.cpu.abi=armeabi-v6j
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=mdpi
ro.product.locale.region=
ro.wifi.channels=
ro.board.platform=msm7k
ro.build.product=marvel
ro.build.description=passion-user 2.3.3 GRI40 102588 release-keys
ro.build.fingerprint=google/passion/passion:2.3.3/GRI40/102588:user/release-keys
ro.sf.lcd_density=160
view.fading_edge_length=8
view.touch_slop=15
view.minimum_fling_velocity=25
view.scroll_friction=0.008
rild.libpath=/system/lib/libhtc_ril.so
ro.ril.hep=1
ro.ril.enable.dtm=0
ro.ril.ecc.HTC-WWE=999
ro.ril.ecc.HTC-ELL=92,93,94
ro.ril.enable.a52.HTC-ITA=1
ro.ril.enable.a53.HTC-ITA=1
ro.ril.enable.a52=0
ro.ril.enable.a53=1
ro.ril.vmail.23415=1571,BT
ro.ril.hsdpa.category=8
ro.ril.htcmaskw1.bitmask=4294967295
ro.ril.htcmaskw1=14449
ro.ril.def.agps.mode=2
ro.ril.gprsclass=12
ro.ril.disable.power.collapse=1
ro.gsm.2nd_data_retry_config=max_retries=3, 2000, 2000, 2000
wifi.interface=eth0
wifi.supplicant_scan_interval=15
mobiledata.interfaces=rmnet0,rmnet1,rmnet2,gprs,ppp0
ro.tether.denied=false
ro.telephony.default_network=0
ro.com.google.locationfeatures=1
ro.opengles.version=131072
sys.checkfs.fat=false
dalvik.vm.execution-mode=int:jit
dalvik.vm.heapsize=24m
persist.sys.use_dithering=1
persist.sys.purgeable_assets=0
htc.audio.alc.enable=true
ro.product.processor=600MHz
ro.product.ram=512MB
ro.product.display_resolution=3.2 inch HVGA resolution
ro.product.main_camera=5M
ro.product.front_camera=NA
ro.product.bluetooth=3.0
ro.product.wifi=802.11 b/g/n
ro.ril.update.acoustic.table=1
ro.media.dec.jpeg.memcap=20000000
ro.ril.hsupa.category=5
ro.ril.disable.fd.plmn.prefix=23402,23410,23411
ro.ril.hsxpa=2
keyguard.no_require_sim=true
ro.rommanager.developerid=cyanogenmod
ro.url.legal=*/phone-legal.html
ro.url.legal.android_privacy=*/basic/privacy.html
ro.com.google.clientidbase=android-google
ro.com.android.wifi-watchlist=GoogleGuest
ro.setupwizard.enterprise_mode=1
ro.com.android.dateformat=MM-dd-yyyy
ro.com.android.dataroaming=false
ro.config.ringtone=Playa.ogg
ro.config.notification_sound=regulus.ogg
ro.config.alarm_alert=Alarm_Beep_03.ogg
ro.modversion=CyanogenMod-7.1.0-RC1-marvel-KANG
ro.kernel.android.checkjni=1
ro.setupwizard.mode=OPTIONAL
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.factorytest=0
ro.serialno=SH19LTR14632
ro.bootmode=recovery
ro.baseband=7.57.39.15M
ro.carrier=VODA-UK
ro.bootloader=1.09.0099
ro.hardware=marvel
ro.revision=128
init.svc.recovery=running
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
Location of last text messages sent :
Code:
adb pull /data/data/com.android.providers.telephony/databases/mmssms.db
Using DB Browser for Sqlite to view database.
I can see the final messages sent or received but where is the full history of messages from each contact located?
Where is the location of contacts?
This is odd: switched phone on this morning and it was stuck at the boot logo. I did a bit of digging around and it looks like the internal memory is corrupt because it is refusing to mount /data or /system.
I am ok doing a kies or odin recovery but before i do it would be nice (not essential) to recover some data. I can get into download and recovery and have tried to mount them manually but it didn't work.
Before I go for the full reset, an ideas on mounting /data?
cheers
m
ps. "boot" not "boo"!
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)
/dev/block/mmcblk0p8 on /cache type ext4 (rw,seclabel,relatime,user_xattr,barrier=1,data=ordered)
ls /dev/block
loop0
loop1
loop2
loop3
loop4
loop5
loop6
loop7
mmcblk0
mmcblk0p1
mmcblk0p10
mmcblk0p11
mmcblk0p12
mmcblk0p2
mmcblk0p3
mmcblk0p4
mmcblk0p5
mmcblk0p6
mmcblk0p7
mmcblk0p8
mmcblk0p9
platform
ram0
ram1
ram10
ram11
ram12
ram13
ram14
ram15
ram2
ram3
ram4
ram5
ram6
ram7
ram8
ram9
cat fstab
/dev/block/mmcblk0p3 /efs ext4 rw
/dev/block/mmcblk0p8 /cache ext4 rw
/dev/block/mmcblk0p9 /system ext4 rw
/dev/block/mmcblk0p12 /data ext4 rw
/dev/block/mmcblk0p10 /preload ext4 rw
/external_sd vfat rw
/usb-otg vfat rw
mount -a
mount: mounting /dev/block/mmcblk0p3 on /efs failed: Invalid argument
mount: mounting /dev/block/mmcblk0p9 on /system failed: Invalid argument
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
mount: mounting /external_sd on vfat failed: No such file or directory
mount: mounting /usb-otg on vfat failed: No such file or directory
mount -o rw,remount /dev/block/mmcblk0p12 /data
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
mount -t ext4 -o rw,remount /dev/block/mmcblk0p12 /data
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
mount -t ext4 -o rw /dev/block/mmcblk0p12 /data
mount: mounting /dev/block/mmcblk0p12 on /data failed: Invalid argument
Try this: http://forum.xda-developers.com/showpost.php?p=30087735&postcount=6
Already have plenty of emergency firmwares as per OP - just wondering if it's possible to mount the partitions some other way. However, no worries: gave up and just reloaded one using odin. worked fine.