Database Info

Can't mount /cache/recovery/

Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4

Eisken said:
Hi there,
I used Cyanogenmod 1.1 beta for a while and while I was pretty happy about it, it did have some issues i wasn't very fond of. So I decided to to perform a nandroid restore of my stock rom and succeeded. My stock rom kept crashing when trying to use internet (synchronising, browsing etc). While messing a little with the settings (like no account syncing etc) my phone crashed and it went into an infinite bootloop. I went into recovery, did the neccesary wipes and performed a nandroid recovery to my Cyanogenmod again. It errored while doing so (can't remember exactly what the line was, but was something like unable to format...something).
Now when I boot into recovery it displays the following information:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
Any idea's? I know there is a lot to find about this on the internet and this forum but they're all guides from other devices and don't know if it would be wise to follow them
Help would be appreciated!
Clockworkmod v4.0.1.4
Click to expand...
Click to collapse
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?

ben_pyett said:
What happens when you attempt to enter RECOVERY and format CACHE?
Did you at any point in this boot loop process pull the battery?
Click to expand...
Click to collapse
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.

Eisken said:
When doing cache wipe:
Formatting /cache...
Cache wipe complete.
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I did not pull the battery out except for the infinite bootloop I mentioned earlier.
Click to expand...
Click to collapse
Sorry, I'm afraid that I must be the bearer of bad news ....I believe that by pulling out the battery you have ruined the eMMC chip in the device, this appears to be a flaw or defect with a selection of recent HTC devices.
I believe that the only thing you can do is to return the device for warranty or to attempt to get the chip replaced.
Here are a selection of similar threads, within this forum which also cover this problem and I believe that you should be able to find others......
http://forum.xda-developers.com/showthread.php?t=1165304
http://forum.xda-developers.com/showthread.php?t=1150917
http://forum.xda-developers.com/showthread.php?t=1226849

Thanks for your reply!
Too bad there is nothing to do about it. I'll just send it in for repair then.

having the same problem.. so should i try to wipe the cache and see what happens?

I fixed that by going into recovery and wiping the cache. It still says that it is unable to mount but re-flashing the ROM fixed all that.

I've tried that quite a few times, but it always failed to flash the rom. Did you get errors when flashing the rom?

What errors do you get when you're installing the ROM?
If you are still able to go into recovery then....
Do you have EXT4 recovery installed?
If not 1) Download this FILE which is EXT4 recovery 2) then copy it onto your SD card 3) enter recovery and flash the EXT4 ZIP file 4) Reboot Recovery
Then look at what format the existing CACHE partition is in?

OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers

EbiEre said:
OK i seem to be the next one with this Problem.
But for now it isn't a real problem, the following happended:
Used Hydrogen for some weeks, but wanted to try the new Virtuous Unity. So i did a backup of my apps with titanium, booted into recovery, flashed the Virtuous Rom, Install was complete and after that it says the known E: cant't mount ... and so on.
After that i pressed restart now in ext4 recovery and the Rom booted as it should. I restored my apps, everything is ok. But now i'm a little scared what will happen next
So is this the normal "way" it goes, or did i just have luck? I'm thinking about going back to s-on and stock, if this is possible.
Btw i didn't pull out the battery ever, cause i knew this could brick my ds, and i never had a bootloop or something like that.
Hope someone can give me some tips.
Cheers
Click to expand...
Click to collapse
The good news here is that you recovered from this problem and also that you didn't pull battery, so we can rule that out as being the cause in your case.
Between the Installation/flashing of the second ROM did you perform the necessary WIPES?
You may well have done, but, just in case, I'd always recommend that you take a full Nandroid backup of an existing system ROM before moving and flashing another (just to have a fall back position in case)?

@ EbiEre
I got scared after reading those lines too. Nothing to worry about. Just keep flashing roms as usual . Just a cache error. If you didnt pull out the battery, and if the rom booted, then everything is ok.

Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers

EbiEre said:
Yeah but I'm scared because I think it could brick "really".
I don't think it is sure that it only happen if i pull out the battery isn't it?
For now I'm back at the stock tom, it's OK but to be honest I love to root my phone and flash rims, and so maybe I will root again
Thx for your answers
Click to expand...
Click to collapse
Can only echo the comments of @.sh4d0w.
We all take a minor risk of bricking our devices with the majority of commands and flashes that we do.....but we still do them because that's half the fun...
Did you ever examine the format types ie EXT3/EXT4 of each partition using the EXT4 recovery?

[Q] think i have bricked my device

I have been using my desire s with cm9 alpha builds and recently flashed the latest version.
my phone froze so i rebooted but it jsut kept looping, i went into recovery and tried to re install thr rom.
however i get the following errors in recovery:
cant mount /cache/recovery/command
cant mount /cache/recovery/log
cant open /cache/recovry/log
cant mount /cache/recovery/last_log
cant open /cache/recovery/last_log
the loading bar just stopps and nothing happens if i try to:
install rom
factory reset
wipe cache
wipe dalvik
so i currently have a completely useless phone and im not saure how to fix it!
somebody please please help me!

i think you didn't seen the BIG INDEX on the development area?
FRIED eMMC CHIP?
I've not tried any of these actions myself as I haven't yet experienced this issue, I'd recommend that great care should be taken before following any of the advice given, I suggest that you at least read and attempt to understand first, if you don't understand then create a new post detailing your own issue and experiences so that others can assist you and point you in the right direction.
The errors below don't necessarily mean that you've a fried eMMC chip, so don't panic just yet. Many users have experienced the exact errors below and have gone on to simply resolve the issue and use their devices again normally.
Code:
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
Click to expand...
Click to collapse
try to read the end of the first post http://forum.xda-developers.com/showthread.php?t=1146601
hope you didn't brick your device. Good luck!

ive read it all but really struggling to make sense of it all :s
i have the revoloutionary fastboot drivers installed but i cant seem to get any tools to pick up my phone!

spitfire12 said:
ive read it all but really struggling to make sense of it all :s
i have the revoloutionary fastboot drivers installed but i cant seem to get any tools to pick up my phone!
Click to expand...
Click to collapse
Check my sig about the emmc problem

i had the same problem like you...
http://forum.xda-developers.com/showthread.php?t=1525100 this tutorial has helped me good luck
BUT REMEMBER DONT REMOVE THE BATTERY DURING ALL THE PROCESS
sorry for my english

When i reboot my phone it wipe all that i saved

Hey guys, i didn't found my problem in other topics, so i opened a new .
So here is the deal, i have the Kisadworx ROM installed now in my Samsung galaxy 3 i5800, and already tried the Kyrillos and both of them have this same issue. When the phone shutdown for low battery, i put it to recharge and when i boot it, it wiped all i have saved. Apps, configs, widgets....just everything. i have no clue why...some one have faced this issue before?
Note: when i enter in recovery mode and try to wipe data/factory reset it shows a message:
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 don't know if this error is related but ok ....
Plz someone could help me?

I had this issue days ago, and it happened to me while I simply only turned off and on my phone.
This is probably caused by bad data and cache(?) partition or by bad (wrong) filesystem used. Try re-flashing STOCK rom eg. XXJPQ and over it custom rom of your choice. If the problem persists, try flashing custom kernel (g3mod) and convert file systems like this:
stl6 - ext4
stl7 - ext4
stl8 - ext2
I never had any issues with g3mod kernel's recovery with theese filesystems.
In gingerbread ROMs I had never issues with data or recovery.

bielmontes said:
Hey guys, i didn't found my problem in other topics, so i opened a new .
So here is the deal, i have the Kisadworx ROM installed now in my Samsung galaxy 3 i5800, and already tried the Kyrillos and both of them have this same issue. When the phone shutdown for low battery, i put it to recharge and when i boot it, it wiped all i have saved. Apps, configs, widgets....just everything. i have no clue why...some one have faced this issue before?
Note: when i enter in recovery mode and try to wipe data/factory reset it shows a message:
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 don't know if this error is related but ok ....
Plz someone could help me?
Click to expand...
Click to collapse
Do you have an ext partition on your phone?
I got into similar problems with the scripts related to ext partition long ago
I too get the recovery error and it is not of any problem to us . This is solved by using g3mod kernel

hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys

bielmontes said:
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
Click to expand...
Click to collapse
If u checked ur available memory when u had the problem, u probably had 0.00kb available. Just saying.
Sent from my GT-I9003 using xda app-developers app

bielmontes said:
hey guys, i followed as twinky444 said and it apparently worked. I reinstalled the stock ROM but a got the samsung bootloop, then a tried again and i made it, after, i installed the kyrillos 10.5 and it''s currently working, with no problems of data lost. I think it was some corrupted data problem. Thank you very much guys
Click to expand...
Click to collapse
If youre going from ROM that uses other filesystems than stock samsung's RFS filesystem such as ext2, ext4, so by flashing the stock ROM causes the bootloop WILL be there. (because the stock kernel doesn't support other filesystems than RFS) You need after flashing stock ROM pull the battery, reinsert it, reboot into recovery by pressing 3-keys combo and then "wipe data - factory reset" in recovery and then "wipe cache partition".
After this, the /data and /cache partition gets either mounted again or reformatted (not sure) with the rfs filesystem and the system will be able to boot.
BTW/little hint: You can see for couple of seconds after flashing the stock rom the phone boots into recovery, shows a couple of lines and there are 2 lines that are RED and say something like
DATA: blablabla... !
CACHE: blablabla... !
This process applies to the ROMs such as Purumod, Kyrillos and maybe others what have other filesystems used than the one used by the stock ROM (RFS).
Thats the description of the "bootloop" problem.
BTW... glad we could help and this has been fixed!

Unique problem with flashing namely lollipop!

Hello, I faced unique problem. Device Nexus 5 D820. I've read a lot of topics on how to flash stock dactory image, clean, and did everything the same as described there.
Problem is that I am not able to flash lollipop (Android 5+) factory images. I mean everything goes fine, but when it comes to final start of the system it stucks on flying dots (dots are moving) over 12-24 hours and won't open. However the KitKat (Android 4+) factory images flashes properly, the system loads in 10 minutes. I also tried to update from Android 4.4.4 by google update (Android 5+) notification, but it also gets stuck on the same flying dots. The problem began when my device running Android 5.1 several months suddenly rebooted and system asked me to enter password (I do not use any passwords on phone), I entered my google account password, then it stated that the data was corrupted and needed factory reset. In order to avoid this I just turned it off and on and it stucked in flying dots. When I tried to wipe cache first the following errors appeared:
E:failed to mount /cache (Invalid argument)
E:can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (Invalid argument)
Then, after several flash things these errors do not appear already, but problem still remains. I already delete all data, so no need to bother keeping data. Any Ideas what causes this problem?

When I boot from TWRP and do operations the following string appears during operations (wipe cache, etc.):
Updating partition details...
E: Unable to mount '/persist'

I had a similar problem.
Make sure you wipe dalvik and cache in recovery before rebooting.
Finally, nothing worked until I did a factory reset after flashing.
Be sure to first backup photos, documents, etc. in addition to nandroid and titanium backup.

Update: problem SOLVED
maybeme2 said:
I had a similar problem.
Make sure you wipe dalvik and cache in recovery before rebooting.
Finally, nothing worked until I did a factory reset after flashing.
Be sure to first backup photos, documents, etc. in addition to nandroid and titanium backup.
Click to expand...
Click to collapse
Thank you mate. But my problem is apparently more specific.
I find a solution which is exactly suits for my problem. Greatest thanks to @bitdomo :good::good::good::good::good::good::highfive:highfive:
Here is his topic
[GUIDE][FIX] Boot loop on Lollipop 5.0 and above (fix persist partition)

[Completed] Myphone Uno E:failed to mount /cache (Invalid argument)

Please help me. I am trying my best but I cant do this anymore.
In the past my phone was always updating. I don;t know how it happened. But it started when I updated my android. I just saw that my device was taking too long to boot. I was on the four concentric circles logo of android 6. I used it for quiet a time. Then it ended up to bootloop. That time I don't know that I need to wipe data/factory reset and wipe cache/ wipe cache partition. I search this on youtube after experiencing the error bellow.
E: Can't open /cache/recovery/last_install
E: Can't mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache/recovery/last_log
-and then all of the lines just jumbled again
same as the one on this thread:
http://forum.xda-developers.com/google-nexus-5/help/help-nexus-5-bricked-clearing-cache-t2564509
I tried to follow the advice by typing the code "fastboot flash cache cache.img"
unfortunantely I was not able to find any cache.img that is suitable for my Android. I am running on 6.0.1 MMB29Q.
I was looking for any sprout 4 stock rom here for my uno but i can't find anything. I even tried to fastboot flash another rom but it failed. I also tried to flash using an sd card but its not working.
when I am trying to adb sideload on the other hand, it would only take about a minute or two then it would go back to bootloader mode.
PLEASE HELP ME REGARDING THIS MATTER. PLEASE POST LINKS where i can find cache.img for android 6.0.1 MMB29Q. for MYPHONE UNO If ever there were other solutions please post. I really need your help guys.

tjtenedero said:
Please help me. I am trying my best but I cant do this anymore.
In the past my phone was always updating. I don;t know how it happened. But it started when I updated my android. I just saw that my device was taking too long to boot. I was on the four concentric circles logo of android 6. I used it for quiet a time. Then it ended up to bootloop. That time I don't know that I need to wipe data/factory reset and wipe cache/ wipe cache partition. I search this on youtube after experiencing the error bellow.
E: Can't open /cache/recovery/last_install
E: Can't mount /cache (Invalid argument)
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: failed to mount /cache/recovery/last_log
-and then all of the lines just jumbled again
same as the one on this thread:
http://forum.xda-developers.com/google-nexus-5/help/help-nexus-5-bricked-clearing-cache-t2564509
I tried to follow the advice by typing the code "fastboot flash cache cache.img"
unfortunantely I was not able to find any cache.img that is suitable for my Android. I am running on 6.0.1 MMB29Q.
I was looking for any sprout 4 stock rom here for my uno but i can't find anything. I even tried to fastboot flash another rom but it failed. I also tried to flash using an sd card but its not working.
when I am trying to adb sideload on the other hand, it would only take about a minute or two then it would go back to bootloader mode.
PLEASE HELP ME REGARDING THIS MATTER. PLEASE POST LINKS where i can find cache.img for android 6.0.1 MMB29Q. for MYPHONE UNO If ever there were other solutions please post. I really need your help guys.
Click to expand...
Click to collapse
Hi,
There's no dedicated forum for your device here. This thread seems to be the most relevant for your issue:
> Bricked my myphone uno using Android One Toolkit
Try posting your query there. Hopefully other UNO users can help you.
Good luck