Database Info

[Q] Bricked? - HTC Desire S

Hi guys
I have a question - could someone please have a look at my clockwork recovery log and tell me if there is any chance of fixing my Desire S?
I can get to recovery but that's abou it.
It has been rooted and is s-off.
I frmatted system and cache then tried to install some mods - Cyanogen, LBC... to no availl - I get the message
E:Error in sdcard/Update/cm_saga_full-25.zip (Status 1)
Tried to update through PG88IMG.zip - that went through the motions and did nothing (although the parsing part was very short.
Tried restoring the backup but I get:
Error while formatting /system!
Factory reset does nothing.
Phone is stuck on HTC logo.
Help please !!!
Recovery Log:
"Starting recovery on Sun Oct 16 11:44:35 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
Revolutionary CWM v4.0.1.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext3 /dev/block/mmcblk0p25 (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
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=GRJ22
ro.build.version.incremental=eng.aria.20110801.185107
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Mon Aug 1 18:51:22 EDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=aria
ro.build.host=giovanni
ro.build.tags=test-keys
ro.product.model=Desire S
ro.product.brand=htc_wwe
ro.product.name=htc_saga
ro.product.device=saga
ro.product.board=saga
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7x30
ro.build.product=saga
ro.build.description=2.36.405.8 CL47853 release-keys
ro.build.fingerprint=htc_wwe/htc_saga/saga:2.3.3/GRI40/47853:user/release-keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rommanager.developerid=cyanogenmod
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.modversion=CyanogenMod-7.1.0-RC1-IncS-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=SH188TJ01555
ro.bootmode=recovery
ro.baseband=3805.06.02.03_M
ro.carrier=ORANGE-UK
ro.bootloader=6.98.1002
ro.hardware=saga
ro.revision=128
init.svc.choice_fn=stopped
init.svc.htcbatt=stopped
init.svc.adbd=running
ro.9kramdump=0
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
SD Card space free: 3531MB
Backing up boot image...
Error while backing up boot image!E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Checking MD5 sums...
boot.img: OK
cache.img: OK
data.img: OK
recovery.img: OK
system.img: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restoring system...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: 256-byte inodes not usable on older systems
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
/sbin/tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p25
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
Error while formatting /system!
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
-- Wiping cache...
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
Cache wipe complete.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p26 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p26 (Invalid argument)
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
W:failed to mount /dev/block/mmcblk0p25 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p26 (Invalid argument)
Fixing permissions...
sh: fix_permissions: not found
Done!
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:Can't unlink /cache/recovery/command
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: 256-byte inodes not usable on older systems
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
/sbin/tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p26
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p25 (Invalid argument)
Error mounting /system!
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
Error formatting /cache!
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
Error mounting /cache!
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:Can't unlink /cache/recovery/command "

Rabarbar said:
Hi guys
I have a question - could someone please have a look at my clockwork recovery log and tell me if there is any chance of fixing my Desire S?
I can get to recovery but that's abou it.
It has been rooted and is s-off.
I frmatted system and cache then tried to install some mods - Cyanogen, LBC... to no availl - I get the message
E:Error in sdcard/Update/cm_saga_full-25.zip (Status 1)
Tried to update through PG88IMG.zip - that went through the motions and did nothing (although the parsing part was very short.
Tried restoring the backup but I get:
Error while formatting /system!
Factory reset does nothing.
Phone is stuck on HTC logo.
Help please !!!
Recovery Log:
"Starting recovery on Sun Oct 16 11:44:35 2011
can't open /dev/tty0: No such file or directory
framebuffer: fd 3 (480 x 800)
Revolutionary CWM v4.0.1.4
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null)
1 /recovery emmc /dev/block/mmcblk0p21 (null)
2 /boot emmc /dev/block/mmcblk0p22 (null)
3 /cache ext3 /dev/block/mmcblk0p27 (null)
4 /data ext3 /dev/block/mmcblk0p26 (null)
5 /sdcard vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1
6 /system ext3 /dev/block/mmcblk0p25 (null)
W:Unable to get recovery.fstab info for /sd-ext during fstab generation!
I:Completed outputting fstab.
Irocessing arguments.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
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=GRJ22
ro.build.version.incremental=eng.aria.20110801.185107
ro.build.version.sdk=10
ro.build.version.codename=REL
ro.build.version.release=2.3.5
ro.build.date=Mon Aug 1 18:51:22 EDT 2011
ro.build.date.utc=0
ro.build.type=eng
ro.build.user=aria
ro.build.host=giovanni
ro.build.tags=test-keys
ro.product.model=Desire S
ro.product.brand=htc_wwe
ro.product.name=htc_saga
ro.product.device=saga
ro.product.board=saga
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=HTC
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=msm7x30
ro.build.product=saga
ro.build.description=2.36.405.8 CL47853 release-keys
ro.build.fingerprint=htc_wwe/htc_saga/saga:2.3.3/GRI40/47853:user/release-keys
keyguard.no_require_sim=true
ro.ril.hsxpa=1
ro.ril.gprsclass=10
ro.config.notification_sound=OnTheHunt.ogg
ro.config.alarm_alert=Alarm_Classic.ogg
ro.rommanager.developerid=cyanogenmod
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.modversion=CyanogenMod-7.1.0-RC1-IncS-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=SH188TJ01555
ro.bootmode=recovery
ro.baseband=3805.06.02.03_M
ro.carrier=ORANGE-UK
ro.bootloader=6.98.1002
ro.hardware=saga
ro.revision=128
init.svc.choice_fn=stopped
init.svc.htcbatt=stopped
init.svc.adbd=running
ro.9kramdump=0
init.svc.recovery=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
SD Card space free: 3531MB
Backing up boot image...
Error while backing up boot image!E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Checking MD5 sums...
boot.img: OK
cache.img: OK
data.img: OK
recovery.img: OK
system.img: OK
Erasing boot before restore...
I:Formatting unknown device.
Restoring boot image...
Restoring system...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: 256-byte inodes not usable on older systems
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
/sbin/tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p25
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
Error while formatting /system!
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
-- Wiping cache...
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
Cache wipe complete.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p26 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p26 (Invalid argument)
/tmp/recovery.log was copied to /sdcard/clockworkmod/recovery.log. Please open ROM Manager to report the issue.
W:failed to mount /dev/block/mmcblk0p25 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p26 (Invalid argument)
Fixing permissions...
sh: fix_permissions: not found
Done!
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:Can't unlink /cache/recovery/command
-- Wiping data...
Formatting /data...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: 256-byte inodes not usable on older systems
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
/sbin/tune2fs: Attempt to read block from filesystem resulted in short read while trying to open /dev/block/mmcblk0p26
Couldn't find valid filesystem superblock.
tune2fs 1.41.6 (30-May-2009)
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
Formatting /sd-ext...
Formatting /sdcard/.android_secure...
I:Formatting unknown device.
rm: can't remove '.' or '..'
rm: can't remove '.' or '..'
Data wipe complete.
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p25 (Invalid argument)
Error mounting /system!
Formatting /cache...
I:Formatting unknown device.
I:Formatting ext3 device.
Warning: could not read block 0: Attempt to read block from filesystem resulted in short read
ext2fs_mkdir: Attempt to read block from filesystem resulted in short read while creating root dir
Error formatting /cache!
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
Error mounting /cache!
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:failed to mount /dev/block/mmcblk0p27 (Invalid argument)
W:Can't unlink /cache/recovery/command "
Click to expand...
Click to collapse
Did you pull your battery but any chance...? When you got stuck at the boot screen did you pull your battery out...? Jus wanted to know so we can have a better idea of where to to from here...
Beamed from my HTC Desire S using xda premium.

maybe you can install 4EXT Recovery and reformat your partitions as ext4.
I had a <null> partition and this fixed it together with solution no.2 in the guide from my signature

To be honest I have been at it for the last 5 days so Im sure at some point I took the battery out when it was stuck at the boot screen.

I tried to install 4EXT Recovery from the Clockwork (install from zip on sdcard option) but that didnt work.

Rabarbar said:
I tried to install 4EXT Recovery from the Clockwork (install from zip on sdcard option) but that didnt work.
Click to expand...
Click to collapse
in the 4EXT Recovery thread there are some attachements (try the 2.0.1 OneClick one) Make sure that your device is detected by adb and run the runme file on your computer

ADB does not seem to work properly anymore - it does not detect the phone at all:
List of devices attached
Although fastboot seem to be reporting correctly:
SH188TJ01555 fastboot
Does it make any difference if I use fastboot instead of adb? (fastboot flash recovery recovery.img).
I also have the RUU_Saga_HTC_Europe_1.28.401.1 exe. Should I maybe try that as well?

Rabarbar said:
ADB does not seem to work properly anymore - it does not detect the phone at all:
List of devices attached
Although fastboot seem to be reporting correctly:
SH188TJ01555 fastboot
Does it make any difference if I use fastboot instead of adb? (fastboot flash recovery recovery.img).
I also have the RUU_Saga_HTC_Europe_1.28.401.1 exe. Should I maybe try that as well?
Click to expand...
Click to collapse
1) if your hboot version is Revolutionary 6.xx.xxxx RUU will not work
2) if not but your phone is branded search for the appropriate RUU
3) if 1 and 2 are not your case make sure that you are in bootloader (hboot) in FASBOOT USB mode and start RUU on your computer
if 3) is not working then give some info about 1 and 2 and we will see what comes next
P.S.: for status 1 error check here

My HBOOT info is as follows:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
RUU detects my image on the phone as 1.47.61.1 when I put it in fastboot usb.
So coming back to 4EXT Recovery - should I try fastboot flash recovery recovery.img to install it?
as for the status 1 error - I have tried factory reset but that just froze the phone.

Rabarbar said:
My HBOOT info is as follows:
-Revolutionary-
SAGA PVT SHIP S-OFF RL
HBOOT-6.98.1002
RADIO-3805.06.02.03_M
eMMC-boot
Mar 10 2011, 14:58:38
RUU detects my image on the phone as 1.47.61.1 when I put it in fastboot usb.
So coming back to 4EXT Recovery - should I try fastboot flash recovery recovery.img to install it?
as for the status 1 error - I have tried factory reset but that just froze the phone.
Click to expand...
Click to collapse
Sorry man you are "Orange UK" branded. I cannot help you further. From my experience the branded RUU components are slightly different (but I do not know the differences), so cannot provide solution.
For me you have the following options:
1) go to a repair centre
2) find RUU_Orange_UK_1.47.61.1 on the web and flash it, but even if you do succeed you will still have the Revolutionary hboot 6.xx.xxxx (but then you will be able to overwrite it via adb)
3) try to flash 4EXT Recovery from fastboot and repair your partitions
4) there is another option but it requires adb shell that you do not have currently (but you should have while in Recovery - check this)

Hi Guys,
Thanks for all your suggestions and help (specially amidabuddha).
Couldn't make it work with any method. Partitions were all screwed up. Couldn't format anything, couldn't mount anything, flashing from RUU, fastboot, recovery, adb didn't work.
Good thing is - I got a courier coming tomorrow from Orange to swap the phone

I keep getting this error when I try to flash a rom on my DS
This error came after that I tried to flash a new rom from within Rom Manger. It started of good but near the end it started putting out error. Then it froze.
So I had to pull the battery. When I started it the phone got stuck on bootlogo.
So I tried volum down+power to try and flash a rom from within recovery. Thats when I started to get these error
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
when I try to format /system I get "Error formating system"
when I try to format /data I get "Error formating data"
and so on and so forth
I use ClockworkMod Recovery 5.0.2.0
I have tried to flash 4EXT but all I get is error.
I have tried ADB, but it won't find the device. (might be something wrong with my ADB, since it won't find my Sony Tables S nor Sony Xperia Arc S)
When I try to flash a new rom from within CWM I get the following error.
E: Error in /sdcard/CoreDroid_Desire_S_GB_2.3.3_v1.3_RV.zip (status 1)
Just to point out. This CoreDroid used to work before.
I have tried to format my sd-card and download the files again and put "new and fresh" files on the card, but still the same.

Related

My phone somehow got stuck in a boot loop and I can't fix it. I don't know what to do. I cant get pass the start up animation no matter what I do.
I've tried the fast boot commands to flash and keep getting the error (i dont really know alot about flashing and never done it before but the that what i found suggested in the web..)
FAILED < remote: flash write failure >
I've tried the flash-all.bat file, but the lock state goes back to LOCKED when it reboots the device and I get the error
not supported on lock device
I can unlock the device when I type fastboot oem unlock, but if the device is restarted it goes back to LOCKED.
I've tried recovery mode and I see the below statements:
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/log
E:Can't open /ache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_log
E:Can't open /ache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_install
E:Can't open /ache/recovery/last_install
E:failed to mount /cache (Invalid argument)
I've tried wipe data/factory reset
--Wiping data...
Formatting /data...
E:failed to mount /cache (Invalid argument)
Formatting /cache...
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/log
E:Can't open /ache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_log
E:Can't open /ache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_install
E:Can't open /ache/recovery/last_install
Data wipe complete
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/log
E:Can't open /ache/recovery/log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_log
E:Can't open /ache/recovery/last_log
E:failed to mount /cache (Invalid argument)
E:Can't mount /ache/recovery/last_install
E:Can't open /ache/recovery/last_install
E:failed to mount /cache (Invalid argument)

It sounds like your emmc is fried. not being able to lock/unlock your bootloader is a classic symptom
Sent from my Nexus 5 using XDA Free mobile app

and what do i do with that?

yyelf said:
and what do i do with that?
Click to expand...
Click to collapse
Get a new device/motherboard swap

thanks....:crying::crying::crying:

but, in /etc/ there has two files i think are in conflict:
the first is fstab:
Code:
/dev/block/mtd/by-name/cache /cache ext4 rw
/dev/block/mtd/by-name/userdata /data ext4 rw
/dev/block/mtd/by-name/system /system ext4 rw
/dev/block/mtd/by-name/user /sdcard vfat rw
/dev/block/mmcblk0p2 /sd-ext auto rw
/dev/block/mmcblk0p1 /external_sd vfat rw
second is recovery.fstab:
Code:
/boot mtd boot
/cache ext4 /dev/block/mtd/by-name/cache
/data ext4 /dev/block/mtd/by-name/userdata
/kernel mtd kernel
/misc mtd misc
/recovery mtd recovery
/sdcard vfat /dev/block/mtd/by-name/user lun=/sys/class/android_usb/android0/f_mass_storage/lun/file
/external_sd vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 lun=/sys/class/android_usb/android0/f_mass_storage/lun1/file
/sd-ext auto /dev/block/mmcblk0p2
/system ext4 /dev/block/mtd/by-name/system
so, if there is 2 files that would to mount the paths, one of them are blocking other.
i say this cause i think "recovery.fstab" is the correct to mount in recovery mode.
but in this recovery mode isn't! /etc/fstab is mounting!
see like this.
i am in CWM and there a log in bottom with:
Code:
CWM-based Recovery modified by androtab.info v6.0.3.1
E:Can't find misc
E:Can't mount /cache/recovery/command
E:Can't find misc
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't find misc
and when i go to install zip from sdcard>choose zip from sdcard(internal storage, not is the removable sdcard):
E:Can't mount /sdcard/
but external sdcard (removable) it mount and open!
and when i go to mount /sdcard, or /cache, /data, /sd-ext, /system, it says: Error mounting /cache!, Error mounting /data!...
i don't know what can i do, cause, even sdcard can mount, /system cannot, and install a custom ROM cannot be done, even not backup the actual rom!
to finish, i say that i think is a conflict cause in ADB i go to mount /mnt (that is the path of sdcard, external_sd (...)) and it return:
mount: can't find /mnt in /etc/fstab
but if i am in recovery mode i would be in /etc/recovery.fstab
can someone help me?
my device is a DL 3003 (RK30x) is a brazilian product. and sorry for my bad english!

Hello everybody,
since I did a bad flashing, when I start the phone in recovery mode I get the following errors:
Code:
E: failed to mount /efs (No such file or directory)
E: failed to mount /system (No such file or directory)
# Manual Mode#
E: failed to mount system (No such file or directory)
E: Can´t mount /system
E: failed to mount /cache (No such file or directory)
E: Can´t mount /cache/recovery/last_recovery
E: failed to mount /data (No such file or directory)
E: Can´t mount /data/log/recovery:log.txt
E: failed to mount /system (No such file or directory)
E: failed to mount /cache (No such file or directory)
E: Can´t mount /cache/recovery/log
E: Can´t open /cache/recovery/log
E: failed to mount /cache (No such file or directory)
E: Can´t mount /cache/recovery/last_log
E: Can´t open /cache/recovery/last_log
E: failed to mount /cache (No such file or directory)
E: Can´t mount /cache/recovery/last_install
E: Can´t open /cache/recovery/last_install
E: failed to mount /cache (No such file or directory)
I have tried to wipe cache partition and do a data/factory reset, but without any luck.
When I try to do a data/factory reset it says:
-- Wiping data...
Formatting /data...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p12
Formatting /cache...
E:format_volume: make_extf4s failed on /dev/block/mmcblk0p8
Data wipe complete
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/log
E:Can´t open /cache/recovery/log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_log
E:Can´t open /cache/recovery/last_log
E:failed to mount /cache (Block device required)
E:Can´t mount /cache/recovery/last_install
E:Can´t open /cache/recovery/last_install
E:failed to mount /cache (Block device required)
I tried to flash again from the sdcard, same errors appear. Lauching a file manager from sdcard is impossible too.
Concerning ADB, the phone is detected, but flashing give an error. Odin doesn't detect the phone.
Anybody can help me ?
Thanks in advance

Helo guys, me again with this RK3066 again, but this time i am more accurate about the issue with the "E:can't mount " blá blá blá...
My device don't mount, in CWM, no one partition, except for itself and external-sd (removable).
Looking more for some reason, i think that i am in the right way, but first of all i need your help.
I get the recovery.log, in /tmp folder, and what you will see is excatly the issue i confront.
Code:
Starting recovery on Fri Jun 10 19:19:38 2016
can't open /dev/tty0: No such file or directory
framebuffer: bpp 16 r 11 g 5 b 0
framebuffer: fd 3 (800 x 480)
CWM-based Recovery modified by androtab.info v6.0.3.1
recovery filesystem table
=========================
0 /tmp ramdisk (null) (null) 0
1 /boot mtd boot (null) 0
2 /cache ext4 /dev/block/mtd/by-name/cache (null) 0
3 /data ext4 /dev/block/mtd/by-name/userdata (null) 0
4 /kernel mtd kernel (null) 0
5 /misc mtd misc (null) 0
6 /recovery mtd recovery (null) 0
7 /sdcard vfat /dev/block/mtd/by-name/user (null) 0
8 /external_sd vfat /dev/block/mmcblk0p1 /dev/block/mmcblk0 0
9 /sd-ext auto /dev/block/mmcblk0p2 (null) 0
10 /system ext4 /dev/block/mtd/by-name/system (null) 0
W:Unable to get recovery.fstab info for /datadata during fstab generation!
W:Unable to get recovery.fstab info for /emmc during fstab generation!
I:Completed outputting fstab.
I:Processing arguments.
E:Can't find misc
W:failed to mount /dev/block/mtd/by-name/cache (No such file or directory)
E:Can't mount /cache/recovery/command
E:Can't find misc
I:Checking arguments.
Warning: No file_contexts
I:device_recovery_start()
Command: "/sbin/recovery"
ro.boot.console=ttyFIQ0
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.bootloader=unknown
ro.hardware=rk30board
ro.revision=0
r
o.emmc=0
ro.boot.emmc=0
ro.factorytest=0
ro.secure=1
ro.allow.mock.location=0
ro.debuggable=1
persist.sys.usb.config=adb
ro.build.id=JDQ39E
ro.build.display.id=rk3066-userdebug 4.2.2 JDQ39E eng.fun.20130427.223241 test-keys
ro.build.version.incremental=eng.fun.20130427.223241
ro.build.version.sdk=17
ro.build.version.codename=REL
ro.build.version.release=4.2.2
ro.build.date=Sat Apr 27 22:33:53 JST 2013
ro.build.date.utc=0
ro.build.type=userdebug
ro.build.user=fun
ro.build.host=ubuntu
ro.build.tags=test-keys
ro.product.model=RK3066
ro.product.brand=rockchip
ro.product.name=rk3066
ro.product.device=rk3066
ro.product.board=rk30board
ro.product.cpu.abi=armeabi-v7a
ro.product.cpu.abi2=armeabi
ro.product.manufacturer=Rockchip
ro.product.locale.language=en
ro.product.locale.region=US
ro.wifi.channels=
ro.board.platform=rk30xx
ro.build.product=rk3066
ro.build.description=rk3066-userdebug 4.2.2 JDQ39E eng.fun.20130427.223241 test-keys
ro.build.fingerprint=rockchip/rk3066/rk3066:4.2.2/JDQ39E/eng.fun.20130427.223241:userdebug/test-keys
ro.build.characteristics=default
ro.cm.device=rk3066
keyguard.no_require_sim=true
ro.com.android.dateformat=MM-dd-yyyy
ro.carrier=unknown
dalvik.vm.lockprof.threshold=500
net.bt.name=Android
net.change=net.bt.name
dalvik.vm.stack-trace-file=/data/anr/traces.txt
ro.cwm.forbid_format=/misc,/kernel,/recovery
init.svc.ueventd=running
init.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/block/mtd/by-name/userdata (No such file or directory)
W:failed to mount /dev/block/mtd/by-name/cache (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/mtd/by-name/cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't find misc
W:failed to mount /dev/block/mtd/by-name/cache (No such file or directory)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mtd/by-name/user (No such file or directory)
E:Can't mount /sdcard/
W:failed to mount /dev/block/mtd/by-name/user (No such file or directory)
W:failed to mount /dev/block/mmcblk0p1 (No such file or directory)
W:failed to mount /dev/block/mmcblk0 (No such file or directory)
E:Can't mount /external_sd/
W:failed to mount /dev/block/mtd/by-name/cache (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/mtd/by-name/cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't find misc
W:failed to mount /dev/block/mtd/by-name/cache (No such file or directory)
W:Can't unlink /cache/recovery/command
W:failed to mount /dev/block/mtd/by-name/cache (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/mtd/by-name/cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't find misc
W:failed to mount /dev/block/mtd/by-name/cache (No such file or directory)
W:Can't unlink /cache/recovery/command
I:Trying /dev/block/mtd/by-name/user on LUN file /sys/class/android_usb/android0/f_mass_storage/lun/file
W:Unable to write to ums lunfile /sys/class/android_usb/android0/f_mass_storage/lun/file (No such file or directory)
I:Trying /dev/block/mmcblk0 on LUN file /sys/class/android_usb/android0/f_mass_storage/lun1/file
W:Unable to write to ums lunfile /sys/class/android_usb/android0/f_mass_storage/lun1/file (No such file or directory)
W:failed to mount /dev/block/mtd/by-name/cache (No such file or directory)
Error mounting /cache!
W:failed to mount /dev/block/mtd/by-name/userdata (No such file or directory)
Error mounting /data!
W:failed to mount /dev/block/mtd/by-name/user (No such file or directory)
Error mounting /sdcard!
mount: mounting /dev/block/mmcblk0p2 on /sd-ext failed: No such file or directory
Error mounting /sd-ext!
W:failed to mount /dev/block/mtd/by-name/system (No such file or directory)
Error mounting /system!
W:failed to mount /dev/block/mtd/by-name/cache (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/mtd/by-name/cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:Can't find misc
W:failed to mount /dev/block/mtd/by-name/cache (No such file or directory)
W:Can't unlink /cache/recovery/command
After you take a look, you can say what is the problem? my device?
I think, the problem is that this Modified CWM don't read ext4, cause my external_sd is in vfat and it mount.
even my internal_sd (not removable storage) is in vfat it can't read, and i don't know if this is the excatly problem.
All the /dev/block/... aren't mounting.
If i try to mount with adb every time return that message E:can't mount...
so, the last thing i can try to do is convert internal storage into vfat, fat or even ext2.
Note, my device is working perfectly when i turn it on, but in CWM or another recovery (stock, or different version of modified CWM - don't ask for TWRP, touch don't work) it return the same thing.
You can think "why you are trying to do with this?", can i test custom rom in it? how custom rom will be flashed if /system, /cache, /data, and others partitions don't mount?! even a restore is impossible to do this way.
"why you don't use RKtool to flash it?" - Volume up button broken, rsrsrs, i know, it's a lot of lucky.
For now, let me test if converting internal partition into ext2 or vfat/fat can solve.
So, i need you now, how can i convert internal storage (no removable - /data, /system, /cache) from ext4 into ext2 or lower?
Thanks a lot to those who help me, and thanks a lot to XDA.
The device name is DL 3003, 7".
Here is the developer firmware link:
http://downloads.dl.com.br
the serial is 3003.
(sorry for my bad english - Brazilian here)

using busybox fdisk /dev/block/mtdblockx(partitions that don't mount) i get:
by mtdblock(x)
(kernel)1: /dev/block/mtdblock1 doesn't contain a valid partition table; p command show nothing, no filesystem - but cwm work and device work.
(recovery)3: no contain a valid DOS partition table(...); p command show nothing, no filesystem.
(cache)5: no contain a valid DOS partition table(...); p command show nothing, no filesystem.
(data)6: /dev/block/mtdblock6 doesn't contain a valid partition table; p command show nothing, no filesystem - but /data is full with files.
(system)9: no contain a valid DOS partition table(...); p command show nothing, no filesystem. - again, device work fine!
(internal_sd): p command : device boot /dev/block/mtdblock11p1 | start 150 | end 150 | blocks 8032+ | id 83 | system Linux**.
**/proc/filesystems don't support Linux, not listed.
end of fdisk.
how you can see, the issue isn't in the internal filesystem type, except for internal_sd that is in Linux and /proc/ don't support it, all partitions haven't a file type in fdisk, i presume that this is the final cause.
what i need to do is: format all these partitions or cannot do that (nothing)? and i know (by my risk). later i put a log, now i'm at job/work.
i believe that after do this i will can do a backup and restore and use custom rom. again vol up is broken, so, no say abaut RKtool.
thanks who is interested for this - no replys at now :'( - but i know you will bring me the light this time.
good night all.

Hi to everyone,
I would like to ask for your help, i want to restore a motorola xoom tablet for my nephew. But trying to restarod i found an error with the TWRP Recovery 3.0.2 at the moment to wipe the /data & /cache partitions pops this errors.
Failed to mount "/data (invalid argument)
unable to recreate /data/media folder.
Updating partition details...
Failed to mount "/data (invalid argument)
Failed to mount "/cache (invalid argument)
...done
Unable to mount storage
Failed to mount "/data (invalid argument)
Failed to mount "/cache (invalid argument)
kernel does not have support for reading SELinux contexts.
Failed to mount "/data (invalid argument)
Failed to mount "/cache (invalid argument)
Unable to mount /data/media/TWRP/ . twrp
MTP Enable
Failed to mount "/data (invalid argument)
Failed to wipe dalvik
updating partition details...
Failed to mount "/data (invalid argument)
Failed to mount "/cache (invalid argument)
...done
unable to mount storage
I already try to install the rom.zip but i got stuck in the bootscreen logo. Looking in different blogs and forum i try the "Change file system" method to convert from ext4 to fat and go back to ext4 but it gave me the same error.
Thank you for the time to read me and to the incoming answers that i can get from all of you.