Related
Last night I decided to install ClockworkMod Touch Recovery 5.8.0.2. I downloaded the image file from this link:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-shooter.img
I then used Flash Image GUI from the Play store to install the recovery. Everything seemed to work just fine. I was able to boot into recovery and the touch features worked.
Today, I created a backup using ROM Manager and it appeared to complete properly. However, now when I boot into Recovery, I get these errors:
E: Can't mount /cache/recovery/command
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
I've tried re-flashing the regular (non-touch) Recovery using ROM Manager and it installs, but I'm still getting the same errors when I boot into Recovery.
I can boot my phone normally and everything works just fine. I just can't do anything with Recovery anymore so I'm stuck on this ROM until I find a solution.
Does anyone know how I can fix this?
Try this
http://forum.xda-developers.com/showpost.php?p=10878511&postcount=8311
And see if it helps.
#Root-Hack_Mod*Always\
So based on that post, you're saying my issues lie on the SD Card, and not the internal memory?
Yup
#Root-Hack_Mod*Always\
I ended up fixing this by following the steps outlined here to return to 100% stock:
http://forum.xda-developers.com/showthread.php?t=1193540
I then ran the Revolutionary tool to get S-OFF and manually flashed ClockworkMod Recovery via Fastboot.
I'm now back in business!
Glad you got back up and running.
#Root-Hack_Mod*Always\
hii
WillJitsu said:
Last night I decided to install ClockworkMod Touch Recovery 5.8.0.2. I downloaded the image file from this link:
http://download.clockworkmod.com/recoveries/recovery-clockwork-touch-5.8.0.2-shooter.img
I then used Flash Image GUI from the Play store to install the recovery. Everything seemed to work just fine. I was able to boot into recovery and the touch features worked.
Today, I created a backup using ROM Manager and it appeared to complete properly. However, now when I boot into Recovery, I get these errors:
E: Can't mount /cache/recovery/command
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
I've tried re-flashing the regular (non-touch) Recovery using ROM Manager and it installs, but I'm still getting the same errors when I boot into Recovery.
I can boot my phone normally and everything works just fine. I just can't do anything with Recovery anymore so I'm stuck on this ROM until I find a solution.
Does anyone know how I can fix this?
Click to expand...
Click to collapse
Hi friends
I solved my problem of CWM recovry error, shows same messages given above.
use this link it will help you definetly
http://forum.xda-developers.com/showthread.php?t=1052813
Thankx
errors
I have the same problem with errors but I´m unable to boot normaly it freeze on start logo... All what I can is go to CWM but here I Can´t flash new rom or restore my backup... It is brick
Errors in clockworkmode recovery
hi everyone
i did a terrible thing and bought a china tablet !
anyway, i installed a new clockworkmod v6.0.2.8 on the device and since then every time i turn on the device, i got these Errors :
E:can't mount /cache/recovery/command
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
i tried these : wipe data/factory reset, wipe cache patition, backup and restore, install update.zip, install zip from sdcard, flashtools, odin (which doesn't work because phone don't have any home button !), heimdall, wiping and installing multiple roms .
i even tried to open the clockworkmod .img file from the trick i find in xda forum and put the extract files into a update.zip and fix the problem !!!
but unfortunately the .img file can't be extracted with :ext4_unpacker and ext2explore . it says : unknown file format !
i know the tablet is not bricked . because if it was, should not turned on and went to clockworkmod instantly and stuck in the errors i just typed !
if anyone knows how can i fix the problem, please help !
i will be Appreciated !
thank u .
laie1472 said:
Try this
http://forum.xda-developers.com/showpost.php?p=10878511&postcount=8311
And see if it helps.
#Root-Hack_Mod*Always\
Click to expand...
Click to collapse
what do i do if i have this problem with CWM root but its the internal card?
Hi guys, I have this problem too after following this guide: http://www.youtube.com/watch?v=0zdhyDky2MI
I've also read this issue is present on stock roms only, but I'm wondering if this could be a potential issue for mounting the /sdcard and use it.
i cant installl custom rom in my xolo q1010i through cwm recovery. every time its says E: cant open/cache/recovery. plz tell me how to solve this errors?
[email protected] said:
i cant installl custom rom in my xolo q1010i through cwm recovery. every time its says E: cant open/cache/recovery. plz tell me how to solve this errors?
Click to expand...
Click to collapse
follow my thread, maybe it's your problem too.
please help me to fix my phone
my micromax A106 phone is not staring.In cwm recovry mod it's showing the comand below.plz give me a solution.
E: Can't mount /cache/recovery/command
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
Install TWRP recovery , Select wipe > Advanced Wipe > Select System/Cache/Data (one at a time) > Repair or change file system > select FAT and swipe .
Hi,
am using lenovo a6000 plus. it was stuck at boot logo, so itried to format wit the help of "wipe data"....now its showing up E: cant mount recovery...
could some help to solve the issue?
Hello,
I just unlocked my rooted prime and flashed the newest CWM via Rom Manager.
Now I can't backup my existing rom. Also I can't install any custom rom.
When I hit backup in CWM, it sais "Can't mount backup path"
When I hit install zip from SD, there is another error "Can't mount /sdcard/
I also tried TWRP Recovery, with no success.
Code:
E:failed to mount /data (Invalid argument)
-- Could not mount: /sdcard.
-- Aborting
Screenshots:
ttp://img37.imageshack.us/img37/561/img20120616114555.jpg
ttp://img801.imageshack.us/img801/2844/img20120616112128.jpg
Just for info: My device is still running stock rom and is encrypted.
Has anyone a solution for this?
Thank you for your help.
With best regards,
B-Paul
Restore is borked in the latest version of CWM. Push 5.8.2.0 and everything will be OK.
Just tried, still the same error message
Brausepaul said:
Code:
E:failed to mount /data (Invalid argument)
-- Could not mount: /sdcard.
-- Aborting
Click to expand...
Click to collapse
You can't mount /sdcard/ (which is a symlink to /data/media/) when device is encrypted, cwm/twrp do not know how to handle this.
edit: Looking at my Nexus, only way to step out of encryption is to use fastboot. It should work like this for the Prime as well.
Hi!
I used to run CyanogenMod 9.1 with device encryption on my Galaxy S3, and decided today that I wanted to try a CM 10 nightly.
A problem with device encryption that I didn't know about before is that it's impossible to turn off. ClockworkMod Recovery (5.8.4.3) can't mount the /data partition (and, by extension, /sdcard). This means that I can't use CWM to factory reset or install a new update.zip, since the update.zip must lie on the internal sdcard.
Trying "choose zip from sdcard" gives "E:Can't mount /sdcard/" and choosing "apply /sdcard/update.zip" gives "E:Can't mount /sdcard/update.zip". This happens even if I've used adb to put the update.zip in the /sdcard mountpoint.
Factory resetting from CWM gives these two errors: "Error mounting /data!" and "Error mounting /sdcard/.android_secure!". Factory resetting from CM9 didn't work. I've since tried to flash CM10 with MobileOdin, which didn't work, and now I can only boot to CWM.
Does anyone have any idea about how I could mount /data or otherwise get a working ROM? I've taken backups of everything.
TL;DR: S3 only boots to CWM, but CWM won't mount /data and so can't flash zips.
I have the exact smae problem. i hope someone knows how to fix!!
I have a ZOPO C2 (http://www.zopomobileshop.com/en/18...tk6589t-5-inch-fhdg-screen-android-phone.html) and it's stuck at the boot image.
I know what went wrong: I tried to move some of the memory of my internal sdcard memory(32GB) to my internal memory(2GB) using this apk: http://forum.xda-developers.com/showthread.php?t=2240954
After rebooting it just got stuck at the boot image, and the button combination to get into recovery doesn't work (it never did work so no change there)
Through adb I managed to get into TWRP recovery. I cannot wipe anything (except the external sd-card):
Updating partition details...
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/emmc'
E:Unable to mount '/emmc'
E:Unable to mount '/system'
E:Unable to mount '/emmc'
Formatting emmc using mkdosf's...
E:Unable to mount '/cache'
E:Unable to mount '/data'
E:Unable to mount '/emmc'
E:Unable to mount '/emmc'
E:Unable to mount '/system'
E:Unable to mount '/emmc'
Click to expand...
Click to collapse
I tried installing a custom ROM, which doesn't fail, but I do get a screen full of the same error message:
E:A render request has failed.
Click to expand...
Click to collapse
It also gives 1 line of this error message every second while the screen locks due to timeout.
After installing the custom ROM, I try to reboot, but the TWRP warns me "No OS installed, reboot?". After reboot again stuck at boot image.
I tried 2 custom ROM's, both of which worked earlier.
I also cannot use adb shell:
- exec '/system/bin/sh' failed: No such file or directory (2) nRet(-1) -
Click to expand...
Click to collapse
However, I can use the Terminal Command within recovery
Within TWRP recovery I can also use the file manager, where the /system/bin/ folder is empty.
My guess is my filesystem is corrupted. Any idea on how to fix this without adb shell?
Edit: Nevermind, flashed the device using latest stock ROM with manufacturer flasher:
http://www.zopomobileshop.com/content/9-download-zopo-mobile-latest-rom
Fixed
same problem
I have the same problem for the same reason, have tried flashing with the latest stock rom, but does not connect to my phone, how was you able to connect thought adb
thanks
henkienl said:
I have a ZOPO C2 (http://www.zopomobileshop.com/en/18...tk6589t-5-inch-fhdg-screen-android-phone.html) and it's stuck at the boot image.
I know what went wrong: I tried to move some of the memory of my internal sdcard memory(32GB) to my internal memory(2GB) using this apk: http://forum.xda-developers.com/showthread.php?t=2240954
After rebooting it just got stuck at the boot image, and the button combination to get into recovery doesn't work (it never did work so no change there)
Through adb I managed to get into TWRP recovery. I cannot wipe anything (except the external sd-card):
I tried installing a custom ROM, which doesn't fail, but I do get a screen full of the same error message:
It also gives 1 line of this error message every second while the screen locks due to timeout.
After installing the custom ROM, I try to reboot, but the TWRP warns me "No OS installed, reboot?". After reboot again stuck at boot image.
I tried 2 custom ROM's, both of which worked earlier.
I also cannot use adb shell:
However, I can use the Terminal Command within recovery
Within TWRP recovery I can also use the file manager, where the /system/bin/ folder is empty.
My guess is my filesystem is corrupted. Any idea on how to fix this without adb shell?
Edit: Nevermind, flashed the device using latest stock ROM with manufacturer flasher:
http://www.zopomobileshop.com/content/9-download-zopo-mobile-latest-rom
Fixed
Click to expand...
Click to collapse
degogar said:
I have the same problem for the same reason, have tried flashing with the latest stock rom, but does not connect to my phone, how was you able to connect thought adb
thanks
Click to expand...
Click to collapse
With the flasher I used all I had to do was remove the battery, plug in the usb and let the flasher do its work.
Hi Guys,
I'm pretty new here and hoping you can all help me with unbricking my phone.
So I have a Samsung S3 I9300, with CM 13.0 installed, I am using CW recovery v2.7.0.0
I've installed many custom ROMS to this device over the past few years without a problem, each time formatting and wiping Dalvik cache etc..
Today my phone randomly rebooted and a message came up that my phone failed to encrypt and it wiped all my data and that I had to reboot into recovery to perform a factory reset.
A bit random I thought.. So I rebooted into recovery and did a "reset to default" in CW.. this was successful, however I noticed some issues on the terminal screen...
Code:
E: Unable to find partition size for /boot
E: Unable to find partition size for /recovery
E: Primary block device /dev/block/mmcblk0p12 for mount point is not present!
E: Unable to mount internal storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /cache
Full SELinux support is present
E: Unable to mount /cache
E: Unable to mount /cache
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E: Unable to mount /data
Updating Partition details...
E: Unable to mount /efs
E: Unable to mount /data
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /preload
E: Unable to mount internal storage
I've tried to format but it shows failed.
I cannot install another ROM as both the internal memory and SD card both show 0MB
I've plugged the SD card into my computer and there are still files on the card.
I've had a look online and found that typing in a command into the terminal should fix it, however nothing happens..
I get an error that mmcblk0p12 does not exist.
Code:
mke2fs /dev/block/mmcblk0p12
Any help would be great! Although i'm pretty sure it's bricked
Cheers Guys!
Chris
Gizzy00360 said:
Hi Guys,
I'm pretty new here and hoping you can all help me with unbricking my phone.
So I have a Samsung S3 I9300, with CM 13.0 installed, I am using CW recovery v2.7.0.0
I've installed many custom ROMS to this device over the past few years without a problem, each time formatting and wiping Dalvik cache etc..
Today my phone randomly rebooted and a message came up that my phone failed to encrypt and it wiped all my data and that I had to reboot into recovery to perform a factory reset.
A bit random I thought.. So I rebooted into recovery and did a "reset to default" in CW.. this was successful, however I noticed some issues on the terminal screen...
Code:
E: Unable to find partition size for /boot
E: Unable to find partition size for /recovery
E: Primary block device /dev/block/mmcblk0p12 for mount point is not present!
E: Unable to mount internal storage
E: Unable to mount /data/media during GUI startup
E: Unable to mount /cache
Full SELinux support is present
E: Unable to mount /cache
E: Unable to mount /cache
E: Unable to mount /data/media/TWRP/.twrps when trying to read settings file
E: Unable to mount /data
Updating Partition details...
E: Unable to mount /efs
E: Unable to mount /data
E: Unable to mount /data
E: Unable to mount /cache
E: Unable to mount /system
E: Unable to mount /data
E: Unable to mount /preload
E: Unable to mount internal storage
I've tried to format but it shows failed.
I cannot install another ROM as both the internal memory and SD card both show 0MB
I've plugged the SD card into my computer and there are still files on the card.
I've had a look online and found that typing in a command into the terminal should fix it, however nothing happens..
I get an error that mmcblk0p12 does not exist.
Code:
mke2fs /dev/block/mmcblk0p12
Any help would be great! Although i'm pretty sure it's bricked
Cheers Guys!
Chris
Click to expand...
Click to collapse
Did you have any success with this, Chris?
This sounds like what happened to my I9300 on CM12.1. It just froze and only rebooted to Samsung logo and stayed there.
When in TWRP recovery, there's just no access to internal memory or SD card.
The terminal mentions a lot of "E: unable to mount /data", /cache, /system, storage, etc
Most TWRP options fail to do anything, because of not being able to access partitions.
No factory reset, no wipes, no installing img's. When rebooting to system, it warns about no OS being installed.
Downloading a stock firmware now to see if it flashes via ODIN, but I don't have high hopes for it.
Does anybody know what would cause this? Or is it just bricked now?
petitgregory said:
Did you have any success with this, Chris?
This sounds like what happened to my I9300 on CM12.1. It just froze and only rebooted to Samsung logo and stayed there.
When in TWRP recovery, there's just no access to internal memory or SD card.
The terminal mentions a lot of "E: unable to mount /data", /cache, /system, storage, etc
Most TWRP options fail to do anything, because of not being able to access partitions.
No factory reset, no wipes, no installing img's. When rebooting to system, it warns about no OS being installed.
Downloading a stock firmware now to see if it flashes via ODIN, but I don't have high hopes for it.
Does anybody know what would cause this? Or is it just bricked now?
Click to expand...
Click to collapse
Hey there,
Nope the cmd I found on-line I found (above) didn't work.
Its currently just stuck on the Samsung splash screen and fails to do anything.
Gizzy00360 said:
Hey there,
Nope the cmd I found on-line I found (above) didn't work.
Its currently just stuck on the Samsung splash screen and fails to do anything.
Click to expand...
Click to collapse
Ah well, mine seems dead too. The recovery doesn't work anymore, only download mode, but ODIN can't get anything on it...
I think the main storage just died.
petitgregory said:
Ah well, mine seems dead too. The recovery doesn't work anymore, only download mode, but ODIN can't get anything on it...
I think the main storage just died.
Click to expand...
Click to collapse
Damn, I dunno what happened.. My CM was a nightly though, SO I can only assume it was unstable.
Just bizarre how my phone rebooted and gave the message that it was unable to encrypt the device and needed to be factory reset.
Gizzy00360 said:
Damn, I dunno what happened.. My CM was a nightly though, SO I can only assume it was unstable.
Just bizarre how my phone rebooted and gave the message that it was unable to encrypt the device and needed to be factory reset.
Click to expand...
Click to collapse
I was running a quite stable CM12.1 version for a couple of months now. Only had two reboots all this time.
petitgregory said:
I was running a quite stable CM12.1 version for a couple of months now. Only had two reboots all this time.
Click to expand...
Click to collapse
I had a few reboots when it was working, then it just suddenly bricked my phone
Sounds like the eMMC brickbug. You need to get the eMMC replaced. All of you that face the problems.
Well, after four years my S3 was getting very slow. It was bearable with CM, but I decided to say farewell now.
Also, my microphone was busted when I dropped it at some point, so I could only call with a headset anyway.
It's not worth replacing I think, time to move on
The same happened to my Beelink GT1 S912 9377 TV-box (after failed OTA update). Will check eMMC brickbug (from TWRP) ...