[Q] error mounting /sdcard/.android_secure! - Optimus L3, L5, L7 Q&A, Help & Troubleshooting

Hello.I tryed overclock for e612.Then I rebooted phone.And phone started to not working. I found stock rom.When I make wipe data and I give this error 'error mounting /sdcard/.android_secure!' What can I do ? please help.

Try reinstall soft using KDZ and everything should work, then you can install custom soft CyanogenMod or other of course if you want and use OC.

Related

[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] i9505 TWRP Bootloop

I flashed the Team Win Recovery Project 2.5.0.3 on stock rom yesterday and now android begun to lag, so I tried to reboot It an now I'm stuck on the bootscreen with the Galaxy S4 logo...
Recovery and download mode still works. I also tried a full wipe but there I get this error:
Code:
E: error: opening /data/data
E: error: I/O error
Maybe caused by FolderMount or such apps, which I tested some days ago?
Does someone know a solution?
I'll try to flash the stock rom again with Odin, as soon as the rom is downloaded...1.6gb
Perhaps you deleted or edited something by accident. So if you boot into recovery and try wipe data/factory reset you get an error? Usually with a bootloop wiping the data and reflashing a stock ROM worked well. Try flash the stock ROM and then try wipe data/factory reset then see if you can boot fine.
Sent from my GT-I9505
one onlesVi
Well, I flashed now the stock rom and first I did a data wipe, which worked fine and then I tried to wipe the cache, but the process crashed with a dead droid(?). The phone has automaticly rebootet now and android seems to work fine. Is this a good or bad sign? ^^

Recovery error.. "E:Error opening..."

Don't know how I did this but I'm having an error in Recovery...comes up as
E:error opening '/data/data/com/instagram.andro
E:error: I/O error
This error is preventing me from restoring backups (they fail)..
Its also kept me from clean installing a new ROM (Rom will boot but I get the process stopped pop-up message repeatedly)...
I've done a total wipe of everything except for internal storage.. but the results are the same. Any help or insight would be appreciated. ***Error also occurs after wipe*** But wipe is "successful"
TIA
Got this issue sorted last night. Apparently, TWRP does a poor job of wiping so I had to switch to Philz recovery and wipe in order to remove that pesky error. From there I was able to perform a clean install of a new ROM, use Freegee to install TWRP and finally load one of my backups.
New issue...
Tap to wake no longer works ...
Any help for the new problem?

ERROR WHILE FLASHING CM 12 NIGHTLY ON Nexus 4 CANT MOUNT SYSTEM ERROR ...PLEASE HELP

Hey guys I am newbie and I need your help ... I was on stock lollipop 5.0 on my nexus 4 with stock recovery ...I wanted to install cm 12 nightly ... I followed the steps to root the device ... First I unlocked the boot loader and installed latest cm recovery and the I selected factory reset in wipe data as was mentioned in the steps to install the cm ROM ...then when I tried to flash the cm12 zip it doesn't complete and gives me unable to mount /system error and something invalid argument after that ..... Guys please help me I don't know what to do ... My phone is not opening up I can only go into recovery
Guys I tried to wipe the system and then I was able to mount the system I have wiped cache , dalvik cache, data as well... Then I tried to flash the ROM but the phone is stuck in flashing screen(see the screenshot) ...it doesn't complete .... Please guys help me ....
http://forum.xda-developers.com/nexus-4/general/tutorial-how-to-unbrick-n4-t2347060
try this...

Zenfone 5 a501cg soft bricked - can't mount /system /cache

Hello all,
I have a zenfone 5 which used to run on custom rom so i decided to revert it back to stock rom but when i wiped system, cache and dalvik, it didn't go well and now i cannot start phone unless going into recovery. Twrp tells me those errors : unable to mount cache unable to mount system.
Tried flashing custom rom again but it didn't work too. Any helps please :/
here is the error screen i get when i try wipe eksiup. com/p/8i2584483xo8
ps: my phone's usb is not working as a connector to pc i.e. pc cannot recognise the phone. please keep this in mind.
palviq said:
Hello all,
I have a zenfone 5 which used to run on custom rom so i decided to revert it back to stock rom but when i wiped system, cache and dalvik, it didn't go well and now i cannot start phone unless going into recovery. Twrp tells me those errors : unable to mount cache unable to mount system.
Tried flashing custom rom again but it didn't work too. Any helps please :/
here is the error screen i get when i try wipe eksiup. com/p/8i2584483xo8
ps: my phone's usb is not working as a connector to pc i.e. pc cannot recognise the phone. please keep this in mind.
Click to expand...
Click to collapse
I think we have the same problem. You need to solve the USB issue first. Remove all the adb drivers and reinstall from scratch.
You will know if you did it right because when you plug the phone in in bootloader, there is no yellow exclamation mark in device manager.

Categories

Resources