[Q] E: Can't mount /cache/... - Verizon Droid Charge

After attempting to revert back to stock from Gummycharged 1.8.1 PBJT nonOC kernel using the ED1.zip stock rom, I obtained the following 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
Even with these errors i was able to revert back to stock BUT I never received an OTA update, i tried to force an update but nothing happened. WiFi would get stuck on obtaining IP address. And no app would download from any app store.
Then I tried to do the Odin flash bundle with gummycharge 1.75 and PBJT OCkernel and it worked fine. But again, same errors and nothing will download. This time WiFi does work.
I've searched this website and found others with this error, but not with this phone. Any advice would be appreciated.
Note: I made sure to disable voodoo lagfix and I wiped factory, cache, and dalvik between flashes

This should be in the General forum. Development is for releases only for new threads, not questions.
Flash one of the All-in-one odin packages if you want to go back to stock. It should also fix your errors in the process.

Related

[Q] Weird Recovery Stuff

I have some weird stuff going on and I was wondering if maybe someone could tell me what it means. My phone is running fine, in fact better than ever. But when I reboot into recovery mode, and before I apply update.zip and I am in stock recovery (blue), I get the follow message below all of the recovery options (error message is in red):
E: Can't mount /dev/block/st111
(Invalid Argument)
E Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
# MANUAL MODE #
E: Can't mount /dev/block/st111
(Invalid Argument)
E: Can't mount /dev/block/st111
(Invalid Argument)
Then, when I do a backup through CWM, everything goes through fine and then I get this message:
Back complete!
E: Can't open /cache/recovery/log
E: Can't open CACHE:recovery/log
When I go into CWM recovery, I do see a backup labeled with the correct date and everything, so I guess it is backing up correctly? Not quite sure what to make of it.
Ignore it.
Sent from my SCH-I500 using XDA App
JayRHamlin said:
I have some weird stuff going on and I was wondering if maybe someone could tell me what it means. My phone is running fine, in fact better than ever. But when I reboot into recovery mode, and before I apply update.zip and I am in stock recovery (blue), I get the follow message below all of the recovery options (error message is in red):
E: Can't mount /dev/block/st111
(Invalid Argument)
E Can't mount /dev/block/mmcblk0p1
(Invalid Argument)
# MANUAL MODE #
E: Can't mount /dev/block/st111
(Invalid Argument)
E: Can't mount /dev/block/st111
(Invalid Argument)
Then, when I do a backup through CWM, everything goes through fine and then I get this message:
Back complete!
E: Can't open /cache/recovery/log
E: Can't open CACHE:recovery/log
When I go into CWM recovery, I do see a backup labeled with the correct date and everything, so I guess it is backing up correctly? Not quite sure what to make of it.
Click to expand...
Click to collapse
I've had this happen and it happens when you have lagfix enabled and try to revert/odin back to a stock kernel (non voodoo) you'll need to follow the manual disabling procedure (of lagfix) by injecting an empty file named "disable lagfix" into the clockwork folder on your SD card then reboot. After that you should be clear to do a clean flash to get everything working properly. If you tried restoring right now it would probably give you an MD5 mismatch, and trying to flash from recovery would probably give you dev/block errors and it would cancel installation until you get your file system back in order.
bdemartino said:
I've had this happen and it happens when you have lagfix enabled and try to revert/odin back to a stock kernel (non voodoo) you'll need to follow the manual disabling procedure (of lagfix) by injecting an empty file named "disable lagfix" into the clockwork folder on your SD card then reboot. After that you should be clear to do a clean flash to get everything working properly. If you tried restoring right now it would probably give you an MD5 mismatch, and trying to flash from recovery would probably give you dev/block errors and it would cancel installation until you get your file system back in order.
Click to expand...
Click to collapse
OK that makes sense. I was flashing all over the place trying to fix that radio issue. Although I liked Add's answer better. Much more convenient
Sent from my SCH-I500 using XDA App
JayRHamlin said:
OK that makes sense. I was flashing all over the place trying to fix that radio issue. Although I liked Add's answer better. Much more convenient
Sent from my SCH-I500 using XDA App
Click to expand...
Click to collapse
Lol yea, I tried that too when I buggered mine up, but since I couldn't flash anything in recovery I decided to find out how to fix it

Need help [g2x]

I installed cyanogenmod.. didnt like how it handled sdcard and internal memory.
Then I tried doing some stupid fixes that I found on these forums..(http://forum.xda-developers.com/showpost.php?p=14879012&postcount=48)
They didn't work so I decided to try to flash the leaked gingerbread rom.
Now my phone is stuck starting in clockworkmod recovery and I can't do anything because I'm getting these stupid errors:
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
And no, I can't wipe, that's the first thing I tried.
Can't restore to stock. It won't let me format /cache, /system, and /data
Tried reinstalling clockworkmod recovery, that didn't work.
Someone suggested flashing a rom with nvflash, but I don't know how to do that.
Any help would be super appreciated. Thanks

[Q] CWM Can't Mount Error

As I cannot post in the thread most probably relevant to this: http://forum.xda-developers.com/showthread.php?t=1590523, I will post here. After running this cleaner, I now receive the following error in CWM:
E:Can't mount /cache/recovery/command
E:Cant 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 had not had this issue before. I am still able to operate CWM with no issues, besides these messages spamming my screen. If anyone can be of assistance?
I am running ICS AOKP 31, with Harsh 1104 kernel. I have flashed 3 different recoveries, 5.0.2.0, 5.0.2.8, and 5.8.1.3. On the 5.8.1.3, because I cannot post in that thread either, I must say it works very well, no issues to report, besides the error above.
Jakkumn
I got the this error too since just getting a new phone cause my previous phone I got off craigslist had a small crack in the corner of the screen so I nullified the phone then flashed the stock recovery back on the phone and told them my phone wasn't starting and ever since I got my new phone I get this message and never got it with my old phone.
So far... the only progress I've managed to make, and it seems to be temporary, is just formatting the /cache partition in CWM. It fixed it for a while, and by a while I mean like 5 minutes. It then returned. So far I haven't run into it again. I'll keep you posted on any progress I make.

huawei u8815 g300 bricked?

Hi guys,
Had a thread open on modaco for this issue but had no joy. I'm having exactly the same issues as the thread starter in the link below, you guys have helped me before and wondered if you had any suggestions on a way forward?
http://www.modaco.com/topic/358071-phone-near-bricked-help-needed/
Basically I've had ics updated on the phone with the boot loader unlocked and of course the phone rooted. The update went through fine and I've been using the phone for a couple of days until it crashed and stuck on the splash screen since then it will only go into recovery mode with the following 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
Have tried wiping cache, formatting cache and numerous other things as per the thread on modaco but no joy. I've literally had the phone a few days and think it's unlikely to be a hardware fault unless it's exactly the same as the OP had.
Willing to try anything!
Thanks

[Q] E:Cant mount cache

I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages
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
and say "Installation Aborted" and restart phone.
When i wipe data/factory reset, format cache it would just show me these errors.
I have also tried Flashing back to the Stock ROM via odin and repeated all of the procedures: 1.Framaroot(To ROOT) 2:CWM(Flash via odin)
Still no success it just keeps giving me these stupid errors when i try flashing a custom ROM,SO BASICALLY I CANT FLASH A CUSTOM ROM
Please Find a FIX.
THANKS.:good:
dima234 said:
I am Using PhilZ CWM 6.49.2. I cant even Flash A Custom ROM Because of this problem it would just show me these error messages
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
and say "Installation Aborted" and restart phone.
When i wipe data/factory reset, format cache it would just show me these errors.
I have also tried Flashing back to the Stock ROM via odin and repeated all of the procedures: 1.Framaroot(To ROOT) 2:CWM(Flash via odin)
Still no success it just keeps giving me these stupid errors when i try flashing a custom ROM,SO BASICALLY I CANT FLASH A CUSTOM ROM
Please Find a FIX.
THANKS.:good:
Click to expand...
Click to collapse
just exactly the same problem here brother...
solution
all you need to do apparently is to go to samMobile,find your device,your country,download the rom,extract it,and flash it with odin.i think it need it to be the same rom as the one installed but not sure about it.it worked perfectly for me,it fixed my recovery back to its stock one without the errors.message me if you still have a problem.
Use TWRP Recovery,And as previously someone said,Try to download Stock Rom file again from Sammobile,After that may h it'll work!

Categories

Resources