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
Related
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
Hi all!
I would be pleased if someone could help me to find out, what this error message can be.
Code:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log/last_log
Untill now I have tried:
1. I did a cache wipe
2. dalvic cache wipe
But after I'm booting into recovery again, I get the same errors.
If it is possible, I wouldn't like to make a factory reset without restoring my NAND backup because the ROM I'm using now is twaked for my taste, and it would be so hard to make all the setting again.
Another issue I'm facing now is that applications can no modify setting related to files in /system partition even if the ROM is rooted.
For example if I'm setting a new CPU governor in SetCPU, after a reboot, it is set back to the default.
I don't know if this is related to the previous problem, but I'm thinking the there could be some mounting problem with the partitions.
I'm using CWM 5.0.2.6, Tytung's r14 kernel with Dorimanx's 2.9.3 ROM, but when I have the rom flashed, there were no issues like the above ones.
Thanks!
only time iget that is when i repartition and wipe the system for a new rom
is it causing you any issues other than seeing an error?
Richy99 said:
only time iget that is when i repartition and wipe the system for a new rom
is it causing you any issues other than seeing an error?
Click to expand...
Click to collapse
Not really. Except for thet wich I wrote about in the first post, but I don't know if it is related to this.
Meanwhile I have flashed a new ROM, and the error message is gone, but I still have the issue with SetCPU, but at least I know, thet the two thigs has no connection.
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.
Hello,
i got my root access running yesterday and backed up my apps with Titanium Backup.
Then it was time to flash cm 10.2. I backed up my stock rom and then wiped the data and cache partition.
Then I tried to flash cm, but it gave me an error. Now if I start cwm, the following errors appear:
Clockworkmod Recovery v6.0.3.2
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /chace recovery/log
E: Can't mount cache/recovery/last_log
E: Can't open /cache/recovery/last_log
When I try to flash CM also errors occur.
I also can't restore my backup, the following error appears: MD5 mismatch!
Please help me, it is quite urgent
Thanks A LOT in advance.....
Best regards, Simon
E: I have the I9505, if I forgot something else, please tell me, my start in that day was so terrible and it's only 7o'clock
E2: when I try to flash CM 10.2, the following messages appear:
-- Installing: /external_sd/AROOT/cm-10.2-jfltexx.zip
E: can't mount /cache/recovery/last_install
E: failed to open last_install: Invalid argument
Finding update package....
Opening Update package....
Installing Update....
Install from sdcard complete
Then when I try rebooting it doesn't go further then the CM Logo, which spins...
re: MD5
cH33zBurGer said:
Hello,
i got my root access running yesterday and backed up my apps with Titanium Backup.
Then it was time to flash cm 10.2. I backed up my stock rom and then wiped the data and cache partition.
Then I tried to flash cm, but it gave me an error. Now if I start cwm, the following errors appear:
Clockworkmod Recovery v6.0.3.2
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /chace recovery/log
E: Can't mount cache/recovery/last_log
E: Can't open /cache/recovery/last_log
When I try to flash CM also errors occur.
I also can't restore my backup, the following error appears: MD5 mismatch!
Please help me, it is quite urgent
Thanks A LOT in advance.....
Best regards, Simon
E: I have the I9505, if I forgot something else, please tell me, my start in that day was so terrible and it's only 7o'clock
E2: when I try to flash CM 10.2, the following messages appear:
-- Installing: /external_sd/AROOT/cm-10.2-jfltexx.zip
E: can't mount /cache/recovery/last_install
E: failed to open last_install: Invalid argument
Finding update package....
Opening Update package....
Installing Update....
Install from sdcard complete
Then when I try rebooting it doesn't go further then the CM Logo, which spins...
Click to expand...
Click to collapse
Go into CWM and or Rom Manger and find the option where it says "Ignore MD5"
or something to that effect and try restoring your nandroid backup with MD5 disabled.
The best thing you can do is download TWRP custom recovery for your specific phone's
model (i9505) and restore your nandroid backup using that, it's a lot better than cwm or
rom manager, and its also all "touch" and has large tabs to click on.
TWRP has the MD5 checking as an option which you cannot miss when you are creating
a nandroid backup or restoring one.
Good luck!
I am not 100% sure if cwm/rom manager has that MD5 option which
you can enable or disable. (I forgot, been so long since I used it).
I checked and I couldn't find an option to ignore MD5. Then I looked for it in google (for cwm). There I found, that a backup can be truly corrupted which could seriously harm the phone. Therefore I don't dare trying to restore my backup with another recovery...
Is there a way to fix the problem that cwm has? With beeing unable to mount or open the stuff I mentioned in my first post and therefore somehow hindering my system to start.
Thanks so far!
Wow, this is all really strange. I now formated chache (only works when cwm is rebootet in cwm). Then the errors do not occur again. Then I formated my data again, got stuck, shut my device on and tried again, then it worked. The same thing for installing cm. First try it gets stuck, second try it works....wtf..?
Well now it runs, but I am really not content with how it worked out...
So guys, I downloaded the latest CM nightly through the CMupdater app, I rebooted into recovery TWRP 2.6.3.0 at that moment I think, when I tried to flash my update it said "Unable to mount /system" and just stood there, I rebooted into recovery again and tried to mount it from the mounts menu without result.
Next I updated to the latest TWRP but the problem persisted, changed to the latest CWM and that too, is unable to mount /system displaying the message "Error mounting /system!"
I seriously don't want to lose my data as this was a simple update so I didn't make a backup but I don't know what the hell else I'm supposed to do.
Oh and BTW, trying to boot to system leaves me at the Google screen for an indefinite amount of time.
Thanks in advance
Edit:Turns out formatting system doesn't delete my data, I got impatient and did that, problem solved.
Fidelator said:
So guys, I downloaded the latest CM nightly through the CMupdater app, I rebooted into recovery TWRP 2.6.3.0 at that moment I think, when I tried to flash my update it said "Unable to mount /system" and just stood there, I rebooted into recovery again and tried to mount it from the mounts menu without result.
Next I updated to the latest TWRP but the problem persisted, changed to the latest CWM and that too, is unable to mount /system displaying the message "Error mounting /system!"
I seriously don't want to lose my data as this was a simple update so I didn't make a backup but I don't know what the hell else I'm supposed to do.
Oh and BTW, trying to boot to system leaves me at the Google screen for an indefinite amount of time.
Thanks in advance
Turns out formatting system doesn't delete my data, I got impatient and did that, problem solved.
Click to expand...
Click to collapse
Can you add SOLVED to the thread title..
Glad to see everything is ok :good:
Thx Josh
So, i just started getting this same error after updating to TWRP 2.8.2.0, I tried wiping the system and still got the error? I downgraded to TWRP 2.8.1.0 and wiped system again, and that seemed to fix the issue. Not sure if it was my own bug or 2.8.2.0 but just wanted to leave feedback for the next person who may be searching for help.