• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root How to fix 'E: Can't Mount Cache' in CWM

RetroDelete

RetroDelete

Android Enthusiast
This happens when you wipe the cache, but it does not mean anything is wrong with your phone.

E: Can't mount /cache/recovery/log and the other five errors are similar to this.

PERFORM A BACKUP PRIOR TO THIS

I AM NOT RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR PHONE.

Start by going into your recovery..

If you want to keep the ROM you have, then follow these directions. When flashing a new ROM follow the next set of directions.

KEEPING YOUR CURRENT ROM

1) Go into your recovery
2) Go to mounts and storage
3) Format /cache x3
4) Go to advanced in the main menu
5) Reboot recovery

If it is not working, repeat the steps.

FLASHING A NEW ROM

1) Go into your recovery
2) Format /system /data /cache x3 (Like any normal flashing of a ROM)
3) Install the ROM you want to use
4) Go to mounts and storage
5) Format /cache
6) Go to advanced in the main menu
7) Reboot recovery
8) Boot into your newly flashed ROM


I made this thread because some people still have this error show up even though it doesn't affect the way you flash a ROM.. It's just annoying to see that come up every time you hit the back button in CWM.

This is for New and Experienced Admire users.

Oh, and thanks to all the people who made CWM happen ^__^
 
Look Guys Read what the warnings say ...
there looking for files on a partision you just formated.
Basic o/s says format = no files will be created.
and its a cashe drive at that its used by the file system
over and over again..

end note its not a relevent problem.

Viperdink
ABCindicate / Provost
 
this is a the same error alot are experiencing after they flash a rom with 5.0.2.8 and then flash odin and go back to stock 5.0.2.6 > x.x.x.7 and try to format the partition with that. just update to x.x.x.8 and you will be able to wipe, get rid of the warnings and flash roms in a hertbeat.

5.0.2.8 formats the phone to ext4, this is why u get mount errors trying to wipe an ext4 partition with 5.0.2.7.

cant install the roms that need an ext4 partition with 5.0.2.7 simply because they wont be formatted right and will cause you to bootloop.

5.0.2.8 recovery link

flash this through cwm, reboot recovery, wipe and install your roms :)

cheers. you know what button to click.
 
Everyone here, even Retro, is wrong. Sorry to say it, but Spz0 has said on several occasions that you simply reflash the rom and it goes away. I have confirmed this works. I would even say that it has nothing to do with the CWM version because I have been on x.x.x.8 since I got my phone and have seen this error numerous times, at different times, all depending on what rom I installed. Sometimes its not even there and then I boot into CWM later on and it comes up again. I think there is something else going on but like Viperdink said, its an irrelevant problem. Only thing I know for certain is that it coincides with the 492 error in the Play Store.

In short, deal with it, its not a real problem :)
 
SacredBloodlin said:
Everyone here, even Retro, is wrong. Sorry to say it, but Spz0 has said on several occasions that you simply reflash the rom and it goes away. I have confirmed this works. I would even say that it has nothing to do with the CWM version because I have been on x.x.x.8 since I got my phone and have seen this error numerous times, at different times, all depending on what rom I installed. Sometimes its not even there and then I boot into CWM later on and it comes up again. I think there is something else going on but like Viperdink said, its an irrelevant problem. Only thing I know for certain is that it coincides with the 492 error in the Play Store.

In short, deal with it, its not a real problem :)
Click to expand...

Agreed reflashing works....every time!
 
SacredBloodlin said:
Everyone here, even Retro, is wrong. Sorry to say it, but Spz0 has said on several occasions that you simply reflash the rom and it goes away. I have confirmed this works. I would even say that it has nothing to do with the CWM version because I have been on x.x.x.8 since I got my phone and have seen this error numerous times, at different times, all depending on what rom I installed. Sometimes its not even there and then I boot into CWM later on and it comes up again. I think there is something else going on but like Viperdink said, its an irrelevant problem. Only thing I know for certain is that it coincides with the 492 error in the Play Store.

In short, deal with it, its not a real problem :)
Click to expand...
I'm not wrong. I know reflashing fixes this problem, but for those that already have a ROM setup to where they like it, this is used so that you won't have to reflash. I stated in OP that this doesn't affect anything because the cache is RECOVERY RELATED, not PLAYSTORE RELATED -.- This happens after formatting the cache partition, then rebooting and not letting the recovery rebuild the cache. The reason that the playstore does it, is because flashing most ROMs formats everything anyway, and people don't let the ROM sit to rebuild it's cache after turning it on.
 
RetroDelete said:
I'm not wrong. I know reflashing fixes this problem, but for those that already have a ROM setup to where they like it, this is used so that you won't have to reflash. I stated in OP that this doesn't affect anything because the cache is RECOVERY RELATED, not PLAYSTORE RELATED -.- This happens after formatting the cache partition, then rebooting and not letting the recovery rebuild the cache. The reason that the playstore does it, is because flashing most ROMs formats everything anyway, and people don't let the ROM sit to rebuild it's cache after turning it on.
Click to expand...

its only common sense and to the person saying it doesnt matter about cwm version is definitely wrong, go try and flash a stock efs rom on 5.0.2.8.
go ahead, i'll wait.
you cant.
so youd ned to downgrade to flash the working data rom before reflashing ur rom and gapps.
the reason for the downgrade is to fix data and format partitions to the original efs filesystem to get a working clean rom install.
+
?????
PROFIT.

@retro is completely right everyone probably flies through the initial setup after a new flash and is too impatient to let the phone start from a clean base.

hence the 492 errors.
 
nasstyrome said:
its only common sense and to the person saying it doesnt matter about cwm version is definitely wrong, go try and flash a stock efs rom on 5.0.2.8.
go ahead, i'll wait.
you cant.
so youd ned to downgrade to flash the working data rom before reflashing ur rom and gapps.
the reason for the downgrade is to fix data and format partitions to the original efs filesystem to get a working clean rom install.
+
?????
PROFIT.

@retro is completely right everyone probably flies through the initial setup after a new flash and is too impatient to let the phone start from a clean base.

hence the 492 errors.
Click to expand...

I can remember a time or two that I have flashed a rom and got the cache error, reflashed and rebooted recovery, no more error, reboot system and fly straight through to Play Store to download apps, and never got the 492 error. I have also NEVER downgraded to 5.0.2.7 for any reason at all, I have been on 5.0.2.8 since day one when I was playing with CM7 as it was progressing in its early days. Of course, I have always made sure that any rom I flashed was meant for 5.0.2.8 in the first place.
 
SacredBloodlin said:
I can remember a time or two that I have flashed a rom and got the cache error, reflashed and rebooted recovery, no more error, reboot system and fly straight through to Play Store to download apps, and never got the 492 error. I have also NEVER downgraded to 5.0.2.7 for any reason at all, I have been on 5.0.2.8 since day one when I was playing with CM7 as it was progressing in its early days. Of course, I have always made sure that any rom I flashed was meant for 5.0.2.8 in the first place.
Click to expand...

True that. Y downgrade? Oc as well as ext 4 no point to downgrade...
 
blaze420916 said:
True that. Y downgrade? Oc as well as ext 4 no point to downgrade...
Click to expand...

Well, some people might want to downgrade to try out new throms from ABC or something, but also because some people apparently can't handle the OC kernel. There are even some that have tried using it, experienced boot loops and FCs and even tried to underclock it without success. So yeah, some might have to rely on .7 but I agree, .8 FTW :)
 
i have a android tablet superpad 6 10'' 1GHz and 512 ram.
i have the same error message after installing CWM by flashing tool. the after every rom i tried the tablet freezes after 1-2 minutes after the home page comes.
i have tried to format the cache partition and then seems it fix the error messages but not the freezing problem,,, the programe is not responding.. and then completely freezes.
when i restarted and go to the recovery menu the cache error showed up again

any idea or suggestion please...
 
fasiol said:
i have a android tablet superpad 6 10'' 1GHz and 512 ram.
i have the same error message after installing CWM by flashing tool. the after every rom i tried the tablet freezes after 1-2 minutes after the home page comes.
i have tried to format the cache partition and then seems it fix the error messages but not the freezing problem,,, the programe is not responding.. and then completely freezes.
when i restarted and go to the recovery menu the cache error showed up again

any idea or suggestion please...
Click to expand...

You're in the wrong section...
 
You must log in or register to reply here.
Back
Top Bottom