Database Users

[Q] E:Can't open /cache/recovery/log

Can't install Roms using the Rom Manager due to it just stopping at the recovery. I would have to install it manually. Even then the rom doesn't install correctly. Also having issues with Android Market. I think my cache is screwed up on the phone because any settings I do, when the phone reboots it loses everything. Any help would be appreciated.
This is for Samsung Fascinate by Verizon
Recovery: ClockworkMod 2.5.1.0

sortos said:
Can't install Roms using the Rom Manager due to it just stopping at the recovery. I would have to install it manually. Even then the rom doesn't install correctly. Also having issues with Android Market. I think my cache is screwed up on the phone because any settings I do, when the phone reboots it loses everything. Any help would be appreciated.
This is for Samsung Fascinate by Verizon
Recovery: ClockworkMod 2.5.1.0
Click to expand...
Click to collapse
I am getting the same thing. I can't restore a backup I did an hour earlier because of this error. When I try to wipe the data I am getting:
Data wipe complete.
E:Can't open /cache/recovery/log
Then when I try to restore my backup it freezes at
Restoring cache...
fota_pipe.log
I was able to successfully wipe the cache some how on a fluke and my restore finished successfully but then I was in a loop with the recovery bootloader and I couldn't get Android to boot up.
Any help would be greatly appreciated.
fota_pipe.log

Firedog7881 said:
I am getting the same thing. I can't restore a backup I did an hour earlier because of this error. When I try to wipe the data I am getting:
Data wipe complete.
E:Can't open /cache/recovery/log
Then when I try to restore my backup it freezes at
Restoring cache...
fota_pipe.log
I was able to successfully wipe the cache some how on a fluke and my restore finished successfully but then I was in a loop with the recovery bootloader and I couldn't get Android to boot up.
Any help would be greatly appreciated.
fota_pipe.log
Click to expand...
Click to collapse
Ok, having a different issue. I was able to cleanly clear the cache and restore my backup successfully but now I am in a loop with the Voodoo Lagfix Recovery. I choose Reboot System Now and it keeps rebooting into Recovery. I also cannot disable the lagfix which I should be able to do within the menu.

sortos said:
Can't install Roms using the Rom Manager due to it just stopping at the recovery. I would have to install it manually. Even then the rom doesn't install correctly. Also having issues with Android Market. I think my cache is screwed up on the phone because any settings I do, when the phone reboots it loses everything. Any help would be appreciated.
This is for Samsung Fascinate by Verizon
Recovery: ClockworkMod 2.5.1.0
Click to expand...
Click to collapse
Thanks to phidelt82 I was able to use Odin to reflash stock ROM on my phone and it is all working now.
FYI, flashing with Odin, use setting that it starts up with and put the PIT file in the PIT area and the tar.md5 file in the PDA box. Took 2:46 and I was up and running again.

E: Cant open cache recovery last log....cwm
Was on Calkulins 2.8.1 E4GT rom with Hitman kernel and flashed Strongsteve's Blue odexed rom ...I did a nandroid backup using cwm touch, had no issues doing this, but when I booted back into cwm it was no longer touch cwm, it was back on 5.0.2.7 and it gave me this error right from the start: E: cant open cache recovery last log, cant open cache recovery log.....Said this 4 or 6 times before I ever did anything... Any info on this would be very appreciated...
Epic 4G Touch
Calkulin E4GT rom
Rogue Gunslinger kernel
Cwm 5.0.2.7

[Q] Can't install Frankenclean 2.8nv

Hello all,
I'm having trouble flashing frankenclean 2.8nv. it gets part way through copying files and ends with: E:Can't chown/mod /system/ (Too many open files) E: Failure at line 294: installation aborted. I'm currently on 2.5nv, but I am unable to flash 2.6 or 2.8. I'm using CwM Voodoo Lagfix Recovery v2.5.1.x Red. I can restore to my last backup, but can't flash anything new.
Anyone have any suggestions or tips to get 2.8 flashed?

gremnocht said:
Hello all,
I'm having trouble flashing frankenclean 2.8nv. it gets part way through copying files and ends with: E:Can't chown/mod /system/ (Too many open files) E: Failure at line 294: installation aborted. I'm currently on 2.5nv, but I am unable to flash 2.6 or 2.8. I'm using CwM Voodoo Lagfix Recovery v2.5.1.x Red. I can restore to my last backup, but can't flash anything new.
Anyone have any suggestions or tips to get 2.8 flashed?
Click to expand...
Click to collapse
did you wipe everything??

doctorj1 said:
did you wipe everything??
Click to expand...
Click to collapse
Yes, Wiped cache, and did a factory reset, the result was the same.

Q&A... i know its useless to try, it will never happen

[SOLVED] Galaxy S I9000B not booting, no recovery mode

I rooted and installed CM7 on my SGS i9000B about 1 month ago. Everything was going fine and I was in love with my phone.
This afternoon, suddenly and with no apparent reason, it started giving me infinite "Force Close" messages to all apps I tried to open, making the phone pretty useless. Whe this happened I tried repairing permission from within Rom Maanger but the problem persisted. So I booted in recovery mode (Clockwork Mod Recovery) and tried fixing permissions there, but force closing problem was still there.
I had an Nand backup from the day I installed CM7. So I went to recovery mode again and tried restoring the backup, but it gave me an error (I believe it was somwthing related to disk space, but I'm not sure about that). So I did another backup (just in case) and tried to reboot the phone to try restoring backup again.
The problem is, now I can't get to recovery mode again. When I rebooted I was not able to go back to recovery mode anymore. I am still able to get to Download mode though. So I was thinking about flashing some rom/bootloader or something back in from Odin, but as I have no experience doing this, I believe it's safer to ask for help here before doing anything to the phone.
I believe it's not bricked yet, since I can still get to download mode.
Can anyone give me some detailed info about what I should do?

Do flash Kernel one more and,
Do root again and try that working.
If it happend again, wipe dalvik-cache and after your device is rebooted, try again in CWM.

evernet21 said:
Do flash Kernel one more and,
Do root again and try that working.
If it happend again, wipe dalvik-cache and after your device is rebooted, try again in CWM.
Click to expand...
Click to collapse
Sorry but I have very little experience with this and I want to be sure about what I'm supposed to do. What do you mean by flash kernel again? Is it flashing CyanogenMod 7 again via Odin?

I flashed the kernel again using Odin. Used the same file that I used before (when I fisrt rooted the phone a month ago - speedmod k13C). Now I can get into Recovery Mode.
But now I have a different problem. I tried to do a nandroid restore (backup and restore - restore ALL) but I have some errors related to mounting errors:
Code:
Checking MD5 sums...
Restoring system...
E:Can't mount /dev/block/st19 to /system with parameters auto llw.check=no
(File exists)
Error mounting /system/!
Skipping format...
E:Can't mount /dev/block/st19 to /system with parameters auto llw.check=no
(File exists)
Can't mount /system/!
I have no idea what that means.
Any help?

While searching for help on this error I found some people saying that flashing stock rom back intro phone could solve the problem. So this was what I did. Flashed stock samsung rom back i using Odin but when phone rebooted the following error appeared:
Android system recovery <3e>
Samsung Recovery Utils
- for BML -
[some recovery options]
update media, please wait
E:Can't mount /dev/block/st110
(Invalid argument)
E:copy_dbdata_media:Can't mount DBDATA:
So I have a very similar error - "can't mount /dev/block/SOMEFILE". It looks to me like a problem with the internal sd card. What do you guys think?

Solved
I could solve the problem using the method described in this thread.
http://forum.xda-developers.com/showthread.php?p=14732179#post14732179

[Q] E:Can't mount /cache/recovery/last_log

I used to have cm10-nightly up until last night (CM_Kernel-signed).
Today i wiped it all and switched to Slim Beans 3.1 to try it out - didn't like it, so i figured i'd go back to the cm10 version i had.
After the cm10 was installed once again, it started crashing after 2-3 minutes while roaming the menus.
Then i tried another wipe and clean install - same problem occurs.
Now, whenever i'm in recovery and trying to wipe - i get these errors:
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't mount /cache/recovery/log
I've been looking around for a while now and i know this kind of question has been asked before, BUT all of the threads seem to deal with other phones, not a Defy, so i don't wanna use some other phone's solution and mess it up even further.
I'll appreciate any help whatsoever.
Thank you.

I'm having the same problem and can not find a solution for this.
The problem came into existence after flash CM10.1.

More details about what happened:
I used to have this CM10-20120912-NIGHTLY-mb525 - working flawlessly on my device.
Then, i changed to Slim Beans after a full wipe (including cache/dalvik wipe).
Wiped again and switched back to a newer version of cm10 - CM10-20120924-NIGHTLY-mb525 (but same gapps file - gapps-jb-20120726-minimal).
And now after flashing any cm10 rom it just gets stuck/resets after 2-3 minutes of use.
btw,
1. I can still access recovery (custom/stable/stock) and bootmenu.
2. My PC does recognize my phone (recovery->share sd card).
Please help :crying:

AW: [Q] E:Can't mount /cache/recovery/last_log
Did you tried to reformat the cache partition from the bootmenu?
bootmenu -> tools -> file system tools-> format /data and /cache

I fixed it!
It turns out that flashing Slim Bean changes your cache to ext4, as opposed to CM10 which uses ext3.
This is what i did:
1. Reflashed Slim Bean
2. Entered bootmenu right after flashing (without reebooting) and chose: tools-->file system tools-->format to ext3
(takes about 1 minute)
3. Went back to recovery and flashed CM10 without a wipe (if you wipe it - it would reformat the cache to ext4)
Thanks anyway t0mte, you were on the money with this :good:

Thanks a lot
Thanks a lot man.. You saved my life ..

Cm10 builds have been using ext4 since a long time...
Sent from my MB526 using xda premium

Same problem but on MB526
My device was running on CM10-20121102-NIGHTLY-mb526 which was working like a charm until yesterday when I decided to upgrade to CM10-20120217-NIGHTLY-mb526.I did a full wipe before I flashed the newer build and it all went smooth.But after 10-12 hours of using the rom I felt it was less responsive and was freezing sometimes so I decided to revert to the 2012-11-02
build again.But when I got into the recovery menu it showed this error:
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't mount /cache/recovery/log
I did'nt pay heed to it to much and went on with flashing after a full wipe.But when I started using it I got the same problem which the TS got.Random reboots,fc,could'nt d/l any apps from play and other stuff.
Would appreciate it if someone provides a solution to my problem.
__________________________________________________________
Edit: Solved the problem.Wiping data & cache from stock recovery did it for me Flashed the 2012-11-02 build again and everything seems alright as of now.

[Q] Error Mounting Cache

Hey guys.
Got a GT-I9505 and was trying to look at some custom ROMs to install, even thinking of giving the beta AOKP a go, but I ran into an issue.
I was first able to gain root access without much issue from the pre-installed firmware, worked through Odin like a treat, but after I went to install the CyanogenMod Nightly through CWM Recovery, the ROM wouldn't install. I noticed the Factory Reset through CWM and that there was an Error mounting the cache partition. I checked the mounts and only the system partition was mounted, I couldn't mount anything else.
So,after essentially bricking the phone, I used Odin and flashed the Stock Firmware back on and followed on as instructed. but the same thing happened again.
Any suggestions would be great. I have been looking at other devices to see if there had been any problems with mounting cache through CWM and to check if they had solutions, but I was coming up pretty thin with explanations. I was thinking if I format through Odin while flashing the firmware back on, that might help?
Thanks in advance, hopefully.

Tried a few more times.
third time clearing cache, the entire screen started to go more and more green.
fourth time made it reboot
fifth time just cant factory reset at all. its ridiculous.
I honestly cant say im doing something different.
Is there a way to break and actually force the cache to be wiped?

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
Argh. I don't understand why I cant access/wipe my cache. is this a recovery problem?

Okay, there may be a problem with the CWM recovery. I have been looking through a few of the threads and comments in particular with Philz touch CWM recovery, and It now works. but there stillseems to be a few problems popping up with installing aosp/aokp roms. backup and restore is working fine. cache/data wipe also working. but it's quite a pain for the whole process to get it to work.
ill post the threads in a bit.

here is the AOKP rom i was referring too
http://forum.xda-developers.com/showthread.php?t=2276722
and the recovery thread that helped solves some issues
http://forum.xda-developers.com/showthread.php?t=2281367&page=18