i keep getting this error. it dosent let me change the mounts on cmw.
It gives me
Error Mounting /cache!
E:Can't mount/cache/recovery.log
E:Can't open/cache/recovery/last_log
i also tryed formating and it didnt work.
Please help it dosent let me restore
edit: got it to mount but now its getting stuck on resotoring .android secure when trying to flash or restore?
Don't worry about the last part b/c when flash new rom it take of it for u
Sent from my SGH-T959V
rickyy00 said:
i keep getting this error. it dosent let me change the mounts on cmw.
It gives me
Error Mounting /cache!
E:Can't mount/cache/recovery.log
E:Can't open/cache/recovery/last_log
i also tryed formating and it didnt work.
Please help it dosent let me restore
edit: got it to mount but now its getting stuck on resotoring .android secure when trying to flash or restore?
Click to expand...
Click to collapse
The getting stuck on /.android_secure is a byproduct of our rom manager/cwm issues. The only way to fix that ostensibly to odin back to stock/stock+root and redo the recovery. Its all in my flashing guide.
sent from the pits of hell (from an sgs4g)
I did that replaced recovery then reinstall packages
Sent from my SGH-T959V using XDA Premium App
Getting the following message when booting into stock recovery via quickboot (threebutton combo no longer works)
E:Cant' mount /dev/block/st11
(invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
--Appling MULTI-CSC...
Installing MULTI-CSC
E:Cant' mount /dev/block/st11
(invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/stl11
(invalid Argument)
When i resinstall packages i get :
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recover/log
E: Can't open /cache/recover/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Im receiving this error after odining kd1, after trying to ext4 the latest blackice rom
zenofsong said:
Getting the following message when booting into stock recovery via quickboot (threebutton combo no longer works)
E:Cant' mount /dev/block/st11
(invalid argument)
E:Can't mount CACHE:recovery/command
# MANUAL MODE #
--Appling MULTI-CSC...
Installing MULTI-CSC
E:Cant' mount /dev/block/st11
(invalid argument)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/stl11
(invalid Argument)
When i resinstall packages i get :
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recover/log
E: Can't open /cache/recover/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Im receiving this error after odining kd1, after trying to ext4 the latest blackice rom
Click to expand...
Click to collapse
It OK just ignore it I'm getting the same problem to. It did go away for awhile but it came back when I tried the GB leak and after I reverted back to bionix with ext4 and the error came back. Trust me your phone is fine.
Sent from my SGH-T959V using XDA Premium App
your partitions are messed up. you will need a pit file to fix this.
Yeah I lost the three button trick to get to cwm once I flashed the Gingerbread ROM and reverted back to KD1. the only thing we still have is Download mode. and the mounting errors I got in cwm althought they are not a big deal I just didn't wanna see them there anymore so I flashed the update.zip for cwm again. I rebooted the recovery after that and I no longer have those red letter in the recovery page.
Ill follow your.suggestions guys. I also cannot mount cache with cam though other mounts work fine. Is this apart of the same problem?
Sent from my SGH-T959V using XDA App
zenofsong said:
Ill follow your.suggestions guys. I also cannot mount cache with cam though other mounts work fine. Is this apart of the same problem?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Everytime I clicked on mount or unmount and didnt work. I rebooted the recovery from the advanced section and thats how I was able to mount or unmount after that.
Sent from my SGH-T959V using XDA App
zenofsong said:
Ill follow your.suggestions guys. I also cannot mount cache with cam though other mounts work fine. Is this apart of the same problem?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
I got it to go away by odining a fresh kd1. But everytime you use the ext4 converter you will get that error.
Sent from my SGH-T959V using XDA Premium App
After odining kd1 mounts are still acting funny, backup wont flash cache
Sent from my SGH-T959V using XDA App
ssmokey727 said:
Everytime I clicked on mount or unmount and didnt work. I rebooted the recovery from the advanced section and thats how I was able to mount or unmount after that
Click to expand...
Click to collapse
Flashed the update, rebooted recovery, still getting error mounting cache
Sent from my SGH-T959V using XDA App
flash the KF1 leak rom again including pit file in the zip file. then flash back to KD1.
Will do after six hours of sleep. Thank gawds I can still use blackice.
Sent from my SGH-T959V using XDA App
zenofsong said:
Will do after six hours of sleep. Thank gawds I can still use blackice.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
If you have terminal emulator open it an type these two commands
SU <enter>
Mount <enter>
This will bring up alot of text but if you will read a little at the top it will tell you what mounts are what(ext4 or rfs) notice my system and data are ext4 but my cache is rfs that is the reason you see the error, give it time and a couple cache wipes in cwm and it should go away. On my last cwm session is when I formatted my cache and it went back to rfs as you can also see in the pic. So when your cache is ext4 you will receive this error till your cache returns to normal
Sent from my SGH-T959V using XDA Premium App
GDofWR420 said:
If you have terminal emulator open it an type these two commands
SU <enter>
Mount <enter>
This will bring up alot of text but if you will read a little at the top it will tell you what mounts are what(ext4 or rfs) notice my system and data are ext4 but my cache is rfs that is the reason you see the error, give it time and a couple cache wipes in cwm and it should go away. On my last cwm session is when I formatted my cache and it went back to rfs as you can also see in the pic. So when your cache is ext4 you will receive this error till your cache returns to normal
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Cache is not listed. System and data are rfs right now in black ice.
Sent from my SGH-T959V using XDA App
zenofsong said:
Cache is not listed. System and data are rfs right now in black ice.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Can you post a screen shot? Also cache is listed, it should be right below the data and system.
Sent from my SGH-T959V using XDA Premium App
GDofWR420 said:
Can you post a screen shot? Also cache is listed, it should be right below the data and system.
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Sent from my SGH-T959V using XDA App
Sent from my SGH-T959V using XDA App
When I odind gb I used the pit. I don't know if that has any bearing on the situation. When I try to ext4 this room I get bootloops which must have something to do with my funky mounts.
Sent from my SGH-T959V using XDA App
zenofsong said:
When I odind gb I used the pit. I don't know if that has any bearing on the situation. When I try to ext4 this room I get bootloops which must have something to do with my funky mounts.
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
Damn it looks like you have no cache. Try re-odining and if that doesn't help then you will have to do what chadster suggested and grab the pit for flashing kd1. BEFORE YOU DO THAT THOUGH HAVE YOU TRIED MOUNTING THE CACHE AND REBOOTING.(REMEMBER MOUNT MEANS UNMOUNT AND VICE VERSA)
Sent from my SGH-T959V using XDA Premium App
GDofWR420 said:
Damn it looks like you have no cache. Try re-odining and if that doesn't help then you will have to do what chadster suggested and grab the pit for flashing kd1. BEFORE YOU DO THAT THOUGH HAVE YOU TRIED MOUNTING THE CACHE AND REBOOTING.(REMEMBER MOUNT MEANS UNMOUNT AND VICE VERSA)
Sent from my SGH-T959V using XDA Premium App
Click to expand...
Click to collapse
Cache will not mount period. Ill try the gb pit. Where can I grab the kd1 pit?
Sent from my SGH-T959V using XDA App
zenofsong said:
Cache will not mount period. Ill try the gb pit. Where can I grab the kd1 pit?
Sent from my SGH-T959V using XDA App
Click to expand...
Click to collapse
If you look in the sgs4g bible there is a .pit there but you might want to pm a more knowledgeable person than me(like dsexton702 or mad_fitter)because I haven't had to use a pit. Just pm them and tell them your situation and I'm sure they will help you. Hope you get things going again and sorry I couldn't be of more assistance.
Sent from my SGH-T959V using XDA Premium App
I get a message saying "E: unknown volume for path [/sd-ext]" everytime I open up clockwork recovery and when I try to wipe dalvik.
anyone know this problem??
It means nothing for your device
Sent from my MB860
Pirateghost said:
It means nothing for your device
Sent from my MB860
Click to expand...
Click to collapse
now i get this 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
What are you trying to do in clockwork?
Sent from my Inspire 4G using XDA Premium App
You dont have your SD card in do you?
Sent from my Desire HD using XDA Premium App
Hi guys ! I try to come back from JB to UCBL 3 end stuck on the message "
e: failed to mount /dbdata ( File exist)
e: copy_ dbdata_media:Can't mount /dbdata
your storage not prepared yet,please use UI menu for format and reboot action. "
Meybe somebody can help me . im nooby , please help me .
Use qkster's Heimdall.
Sent from my GT-I9300 using xda premium
Left my phone to charge over night and woke it up finding it turned off. (You can imagine the shock!!)
I turned it on back and it has been stuck on the boot screen with the flying dots since then. (Annoyed!!)
When I go into recovery mode and try deleting cache or wipe data I get a lot of error messages saying can't mount cache/recovery/log
Can't unlock boatloader to flash stock. It keeps relocking upon each restart.
Each time I wipe I get these error messages.
Wiping data...
Formatting/data...
- hide quoted text -
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)
E: Can't mount /cache/ recovery/last_log
E: Can't open/cache/ recovery /last_log
E: Failed to mount/cache (Invalid argument)
E: Can't mount /cache/ recovery/last_install
E: Can't open/cache/ recovery/ last_install
Data wipe complete
- hide quoted text -
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)
E: Can't mount /cache/ recovery/last_log
E: Can't open/cache/ recovery /last_log
E: Failed to mount/cache (Invalid argument)
E: Can't mount /cache/ recovery/last_install
E: Can't open/cache/ recovery/ last_install
E: Failed to mount/cache (Invalid argument)
Can someone please help me. I am really frustrated. Please don't tell me it's a hardware problem....
Um this sounds like a hardware problem. Sorry
Sent from my Nexus 5 using Tapatalk
Your NAND is fried. Definitely a hardware issue. RMA in you only option.
theesotericone said:
Your NAND is fried. Definitely a hardware issue. RMA in you only option.
Click to expand...
Click to collapse
I feel like crying right now. My phone does not have any warranty.
I've been compiling NAND failures for the last few months - am I right to assume your phone was 100 % stock?
So far, my WAG is related to the ftrim. We do know they've improved the way it works in the last couple of updates - and made it more aggressive as well.
That does track well with the emmc casualties I'm seeing. But it could be a red herring as well - wear and NAND quality being the most obvious factors.
I wonder, how many of the failures occurred after a night-long charging ( which triggers ftrim) ?
Sent from my Nexus 5 using XDA Free mobile app
Niflheimer said:
I've been compiling NAND failures for the last few months - am I right to assume your phone was 100 % stock?
So far, my WAG is related to the ftrim. We do know they've improved the way it works in the last couple of updates - and made it more aggressive as well.
That does track well with the emmc casualties I'm seeing. But it could be a red herring as well - wear and NAND quality being the most obvious factors.
I wonder, how many of the failures occurred after a night-long charging ( which triggers ftrim) ?
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
Yes 100% stock and unrooted.
I don't know. I woke up and found it turned off. Then I got a bunch of error messages when I tried wiping cache and data.
Is it by some chance possible to save my phone??? I really need to know. I've been up searching the web. I realize I'm not alone now.
Phone_evolution said:
Is it by some chance possible to save my phone???
Click to expand...
Click to collapse
No. The memory is bad. Sorry man those are the facts.
By normal means? A straight and categoric no. In theory we could try reformat it externally, maybe even read it but... It's not gonna happen - at least not affordable.
Buying the emmc chip and replacing it is doable - but again probably not affordable if u don't already have the tools.
Sent from my Nexus 5 using XDA Free mobile app
Niflheimer said:
By normal means? A straight and categoric no. In theory we could try reformat it externally, maybe even read it but... It's not gonna happen - at least not affordable.
Buying the emmc chip and replacing it is doable - but again probably not affordable if u don't already have the tools.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
In a recovery there is an option which is apply update from ADB. Neither that can help me???
Instead of buying parts to fix the device, you should look into getting a new replacement