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?

arom RA recovery probelm

when i try to boot into recovery
i get a weird error.
E:Can't mount CACHE:recovery/command
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
i have Arom RA 2.3
Any help would be great.

sorry guys i made i mistake when posting this.
I am very sorry about posting here can you please remove this thread or move it to the right section.

Try reflashing recovery via rom manager.
Sent from my PC36100 using xda premium

i have tried that and it didnt work.

hobo2424 said:
when i try to boot into recovery
i get a weird error.
E:Can't mount CACHE:recovery/command
E:Can't mount CACHE:recovery/log
E:Can't open CACHE:recovery/log
i have Arom RA 2.3
Any help would be great.
Click to expand...
Click to collapse
I had the similar problem when I was using godmode stuff. Reflashing the recovery normally fixed that for me so give that a shot. Idk what's going on with that but it must have something to do with the way it mounts the system within recovery between the two. Recoveries aren't exactly my specialty

Reinstall the recovery manually, that always fixes it for me.
http://forum.xda-developers.com/showthread.php?t=705026

[Q] HELP- Nexus S bootloop, cache not mounting.

Hi, I was trying to install an ICS ROM on my Nexus S i9020a last night, and I must have messed something up. The ROM installed but it just hung on the google logo. So I went back into recovery (CWM 3.0.0.5) to restore my nandroid backup but I got:
E:format_volume: no MTD partition "boot"
Error while formatting BOOT : !
E:Failed to find "cache" partition to mount at " /cache"
E:Can't mount /cache/recovery/last_log
E:Can't mount /cache/recovery/last_log
E:Can't find misc
E:failed to find "cache" partiton to mount at " /cache"
I don't know much about what these things, but I imagine the seemingly missing cache is the problem. I cannot mount or format the cache either. I get similar errors. Flashing roms seems to 'work', but I still get the bootloop. Flashing img's does not work. "Installation aborted".
I have no idea what I can do to reverse this. At this point, I want to restore to stock. I hope I haven't done permanent damage. Can anyone please help me with this?

First try to upgrade to the latesy cwm. It had very much bugs fixed
Sent from my Nexus S using xda premium

Computer doesn't seem to recognize the phone in fastboot mode, can you link me to the a newer CWM zip so I can flash it in recovery?

error after flashing from Odin

I tried to flash a latest firmware(5800XWJPI and with the apollo_0531.ops) with odin 4.252 after hard reseting, everything was ok but after the rebooting the phone stuck on "--delete App data... delete files, please wait"
how do I get to hard reset again somehow from any recovery? The phone cannot boot. I tried to flash another rom but the problem is the same.

kampinas said:
I tried to flash a latest firmware(5800XWJPI and with the apollo_0531.ops) with odin 4.252 after hard reseting, everything was ok but after the rebooting the phone stuck on "--delete App data... delete files, please wait"
how do I get to hard reset again somehow from any recovery? The phone cannot boot. I tried to flash another rom but the problem is the same.
Click to expand...
Click to collapse
Hold vol up, vol down, home and power button to go into recovery.

it shows me the g3mod kernel non-oc because I have flashed it before just to go to recovery to enter cmd but it was futile...
now stucks on that logo
update: I suceeded in booting into recovery mode which was cwm. I flashed afterwards CyanogenMod 7.2.0-RC3 (Alpha8.2) and the gapps after having wiped everthing but the phone still stucks this time on the gt-5800i (with the black backround) and not the regular cm7 blue logo. So it does not boot again.

any ideas?

kampinas said:
any ideas?
Click to expand...
Click to collapse
flash zerofill.tar...(in my mediafire-sig)...than flash full rom.tar over it
Sent from my SGS-II powered by CM9

ok, I ll flash your zerofill. After that, I flash that "full rom.tar "? where can I find it?
thanks for helping me

kampinas said:
ok, I ll flash your zerofill. After that, I flash that "full rom.tar "? where can I find it?
thanks for helping me
Click to expand...
Click to collapse
^By full rom.tar, I think he meant was to flash any other ROM via Odin (preferably a Stock one!)

ok I flashed zerofill and after that G3MOD-2.5-OC-zImage and then I tried to enter recovery. From there I see many errors like
Code:
E: unknown volume for path [/cache/recovery/log]
E: Can't mount /cache/recovery/log
E: Can't open/cache/recovery/log
E: unknown volume for path [/cache/recovery/last_log]
E: Can't mount /cache/recovery/last_log
E: Can't open/cache/recovery/last_log
E: unknown volume for path [/cache/recovery/command]
E: Can't mount /cache/recovery/command
E: Can't open/cache/recovery/command
and maybe more but I cant see them because of the screen
I wiped all and then flashed from zip CyanogenMod 7.2.0-RC3 Alpha8.2 and the Gapps-06-07-12-signed and everything went fine until I reboot. When I reboot, rom is behaving like it does wipe all and everything is from the begining. Plus I see available internal memory 0mb!!! And I cant install anything. Have I combined something wrong? I have 2 gb sd card. I am afraid to reboot cuz I will have to do and setup everything from the start!

lol....do: fire up odin....now...find a fullrom.tar(e.g. Kyrillos rom 9.x...or my Hercolubus rom)...boot in download mode....flash it....when in cwm...wipe data....now reboot.....if u wanna cm7.2 based....i made a full rom for odin flash & i think kyrillos13 did aswell.....
Sent from my SGS-II powered by CM9

thanks for reply but will this solve the 0 available internal memory?

Search '0kb internal memory'. You will find a thread with a tar file that will fix the issue.
Sent from my GT-I5800 using xda app-developers app

Smonic said:
Search '0kb internal memory'. You will find a thread with a tar file that will fix the issue.
Sent from my GT-I5800 using xda app-developers app
Click to expand...
Click to collapse
the only closest result was this post here and after I have downloaded a rom with the proper file inside I can't delete all the other files so I keep only the datafs (I use winrar). Unfortunately I couldn't find a thread with the file attached.

kampinas said:
the only closest result was this post here and after I have downloaded a rom with the proper file inside I can't delete all the other files so I keep only the datafs (I use winrar). Unfortunately I couldn't find a thread with the file attached.
Click to expand...
Click to collapse
do: download total commander for pc...(google it it's free)...now open a "whateverromuhave".tar....delete all except datafs.rfs....and boot ur g3 in download mode....now flash that .tar with odin....reboot...if u boot to recovery after flash...wipe data again....reboot....done.....enjoy
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
Sent from my SGS-II powered by CM9
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

you are awesome, I will try it thanks

the 0 internal memory is gone and now says total193, available 179 but still displays error on instaling an apk with the message insufficient internal space. Another thing. To sd card says total space 0.89gb, availabe 0.89gb! (I partitioned 1gb through cwm). These messages on cwm still remain:
Code:
E: unknown volume for path [/cache/recovery/log]
E: Can't mount /cache/recovery/log
E: Can't open/cache/recovery/log
E: unknown volume for path [/cache/recovery/last_log]
E: Can't mount /cache/recovery/last_log
E: Can't open/cache/recovery/last_log
E: unknown volume for path [/cache/recovery/command]
E: Can't mount /cache/recovery/command
E: Can't open/cache/recovery/command
and maybe more but I cant see them because of the screen
is this a problem for the phone's functionality? How do I repair it? Does it have to do something with the sd?
At the cyanogen's application settings, the options "use internal storage" cannot be ticked (is grey). any clues?

kampinas said:
the 0 internal memory is gone and now says total193, available 179 but still displays error on instaling an apk with the message insufficient internal space. Another thing. To sd card says total space 0.89gb, availabe 0.89gb! (I partitioned 1gb through cwm). These messages on cwm still remain:
Code:
E: unknown volume for path [/cache/recovery/log]
E: Can't mount /cache/recovery/log
E: Can't open/cache/recovery/log
E: unknown volume for path [/cache/recovery/last_log]
E: Can't mount /cache/recovery/last_log
E: Can't open/cache/recovery/last_log
E: unknown volume for path [/cache/recovery/command]
E: Can't mount /cache/recovery/command
E: Can't open/cache/recovery/command
and maybe more but I cant see them because of the screen
is this a problem for the phone's functionality? How do I repair it? Does it have to do something with the sd?
At the cyanogen's application settings, the options "use internal storage" cannot be ticked (is grey). any clues?
Click to expand...
Click to collapse
^Maybe try re-partitioning your sd card?

rkoby13 said:
lol....do: fire up odin....now...find a fullrom.tar(e.g. Kyrillos rom 9.x...or my Hercolubus rom)...boot in download mode....flash it....when in cwm...wipe data....now reboot.....if u wanna cm7.2 based....i made a full rom for odin flash & i think kyrillos13 did aswell.....
Sent from my SGS-II powered by CM9
Click to expand...
Click to collapse
yes..rkoby13 is right..i faced similar problem before..flashing as one package fixed it..:

rudranilg said:
yes..rkoby13 is right..i faced similar problem before..flashing as one package fixed it..:
Click to expand...
Click to collapse
yup....i have had same situation...and solved it this way
Sent from my SGS-II powered by CM9

Nexus 5 cache and system flashing problem

Hello people of XDA developers,
One fine day, my nexus 5 started hanging up while booting. After the google Logo, the Marshmallow animation would show up and then it would hang and power off. I have no problem in doing a factory reset/wipe of my phone. But the only thing i want to save is my contacts. I have tried erasing and re-flashing system, cache, boot and boot-loader. Using ADB, flashing the cache always fails........ However, i have not touched userdata as i think it would affect the contacts too. I have even tried using different custom recoveries such as CWM, TWRP and even Philz Touch to use adb to pull my SD card files to my PC. Even flashing the system is not working now.... (atleast that's what my results were) .
Philz touch error messages....
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 mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Driven to the point of desperation now........ Thanx a lot in advance... BTW, i'm a complete noob, so plz bear with me and my questions

A223D said:
Hello people of XDA developers,
One fine day, my nexus 5 started hanging up while booting. After the google Logo, the Marshmallow animation would show up and then it would hang and power off. I have no problem in doing a factory reset/wipe of my phone. But the only thing i want to save is my contacts. I have tried erasing and re-flashing system, cache, boot and boot-loader. Using ADB, flashing the cache always fails........ However, i have not touched userdata as i think it would affect the contacts too. I have even tried using different custom recoveries such as CWM, TWRP and even Philz Touch to use adb to pull my SD card files to my PC. Even flashing the system is not working now.... (atleast that's what my results were) .
Philz touch error messages....
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 mount /cache/recovery/last_install
E: Can't open /cache/recovery/last_install
Driven to the point of desperation now........ Thanx a lot in advance... BTW, i'm a complete noob, so plz bear with me and my questions
Click to expand...
Click to collapse
Greetings,
Thank you for using XDA Assist. To get you the best possible help for your issue, I'm going to move this thread to your device's Q&A forum. Good luck!

Did you check your Google or gmail account to see if the contacts have been synced?