[Q] Unable to mount /efs? Please help! - Galaxy S 4 Q&A, Help & Troubleshooting

So the story goes like this. I flashed cm10.2 on my galaxy s4 i9505. Days later, there was an update. I was hoping that the new update might have some battery improvements so I went ahead and updated it. After updating, I realised there was a bug with the back button, so I tried to restore my old cm10.2. But there was a 'unable to mount system, unable to mount cache and unable to mount efs' error. I fixed the first 2 by wiping system and cache, but I could not fix efs. I had to flash a new cm10.2 because I couldn't restore it. Now my efs file is empty but I can call and sms. The only issue is that the mobile carriers appear as numbers(e.g. at&t appears as '52575'), but it doesn't bother me as I've remembered which number is my carrier. I have a backed up stock rom but again, I can't restore it because of the unable to mount /efs error... Any similar experiences/ solutions?
THANKS A LOT!

anyone??

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

[solved] E:/error opening '/data/lost+found' after Factory Reset

Hi, today i wanted to do a factory reset and clean install my phone
im using TWRP 2.3.3.3
after factory reset in the wipe menu, at the end i see a line E:/error opening '/data/lost+found'
basically i know what does lost+found folder does in linux, but i forgot whether i have seen such error line before when i do factory resets.
in the file manager of TWRP i then see /media and /lost+found in the /data partition. when pressing into /lost+found, TWRP cannot open it
after this, wiping /system will also give me the same message at the end even it is "Done", as well as cache and dalvik, etc
then i go on flash rom, gapps, kernel, after 1 or 2 boots i go back to recovery and wipe cache, there are no such line anymore
however there is now TWO /lost+found folder in my /data partition
is this a normal behaviour? i didnt pay attention but are there 2 lost+found folders in /data partition for everyone else too?
i have backed up my sdcard and is ready for a /data wipe, any advice is appreciated. thanks in advance!
update: well really hasnt seen it anywhere tried very hard searching on google
maybe just **** happens sometime as i rushed updating the su binary together with restoring android ID in titanium backup altogether without carefully rebooting etc.
factory reset, formating every partition for N times didnt help. returned to completely stock (unlocked bootloader ofcourse), flash twrp 2.3.3.3 clean and no more that line anymore after factory reset. hell gonna start my sdcard restore now...
Miasmic said:
update: well really hasnt seen it anywhere tried very hard searching on google
maybe just **** happens sometime as i rushed updating the su binary together with restoring android ID in titanium backup altogether without carefully rebooting etc.
factory reset, formating every partition for N times didnt help. returned to completely stock (unlocked bootloader ofcourse), flash twrp 2.3.3.3 clean and no more that line anymore after factory reset. hell gonna start my sdcard restore now...
Click to expand...
Click to collapse
I was researching google for this same exact error message, when I came across your thread. I doubt you are still having this issue, but I wanted to reply with the solution in case anyone else comes across this post. I was able to solve this error message by installing a new ROM. It doesn't matter which one you install, any will do. Then open your file manager of choice, of course one which can go up to root level. Browse to /data, and then you should notice that you do not have a lost+found folder. However, you should see a lost+found file, all the way at the bottom. I renamed this file to lost+foundOLD, and then created a new folder called lost+found. Next, reboot into recovery and once again wipe both caches, system and factory reset. You should no longer get the lost+found error. Make sure to fix permissions as well to make sure.
just had this issue and was solved by dropping back to twrp 2.4.x.x and doing data format.
misspost
mitchallica said:
I was researching google for this same exact error message, when I came across your thread. I doubt you are still having this issue, but I wanted to reply with the solution in case anyone else comes across this post. I was able to solve this error message by installing a new ROM. It doesn't matter which one you install, any will do. Then open your file manager of choice, of course one which can go up to root level. Browse to /data, and then you should notice that you do not have a lost+found folder. However, you should see a lost+found file, all the way at the bottom. I renamed this file to lost+foundOLD, and then created a new folder called lost+found. Next, reboot into recovery and once again wipe both caches, system and factory reset. You should no longer get the lost+found error. Make sure to fix permissions as well to make sure.
Click to expand...
Click to collapse
No his error and mine are different. We have two lost+found dir and no file. If i delete them and make new lost+found folder. It automatically makes 2.
I am having this same problem. I just did a restore to my last backup, but it in TWRP it says mentions the error over and over again. I looked in /data and I found about 10 files called lost+found, but I do not have any folders. Any suggestions?
Full Format data worked for me
NVijapura said:
I am having this same problem. I just did a restore to my last backup, but it in TWRP it says mentions the error over and over again. I looked in /data and I found about 10 files called lost+found, but I do not have any folders. Any suggestions?
Click to expand...
Click to collapse
I just encountered this problem after updating a CM nightly and it bricked my phone. Restoring from a nandroid backup would ultimately fail and I was getting all kinds of weird problems (stuck in boot loop, graphics appearing garbled, etc). After looking closer at the logs during restore, I noticed E:/error opening '/data/lost+found' appearing several times, an then it would indicate 'done' and restart but would end up with the same problems.
Even after doing a factory reset, I had no luck in restoring my phone. So I did a factory reset again and installed a CM stable release thinking maybe my ROM / backup was messed up but noticed the same E:/error opening '/data/lost+found' message. However, this time around I managed to get booted far enough where I could connect via USB and backup files from my internal memory to my computer.
At this point I booted into recovery (TWRP 2.5.0.0) and did a full wipe including internal SD using the Format Data option, whereupon I was able to install the CM stable release without issue - no more lost+found error! I then upgraded to the nightly version of my backup and restored with success. Long and stressful night...
szurheal said:
I just encountered this problem after updating a CM nightly and it bricked my phone. Restoring from a nandroid backup would ultimately fail and I was getting all kinds of weird problems (stuck in boot loop, graphics appearing garbled, etc). After looking closer at the logs during restore, I noticed E:/error opening '/data/lost+found' appearing several times, an then it would indicate 'done' and restart but would end up with the same problems.
Even after doing a factory reset, I had no luck in restoring my phone. So I did a factory reset again and installed a CM stable release thinking maybe my ROM / backup was messed up but noticed the same E:/error opening '/data/lost+found' message. However, this time around I managed to get booted far enough where I could connect via USB and backup files from my internal memory to my computer.
At this point I booted into recovery (TWRP 2.5.0.0) and did a full wipe including internal SD using the Format Data option, whereupon I was able to install the CM stable release without issue - no more lost+found error! I then upgraded to the nightly version of my backup and restored with success. Long and stressful night...
Click to expand...
Click to collapse
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
scwied17 said:
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
Click to expand...
Click to collapse
That worked perfectly. Thanks!!!
scwied17 said:
All you simply have to do when this happens, is format data ( the one where you type yes ). After this, everything SHOULD be back to normal, for the most part.
Click to expand...
Click to collapse
Worked perfect for me. Very easy to miss that simple "Format Data" button in TWRP. Simply type 'yes' and problem solved.
I think I got this error when I flashed SlimKAT 4.4 over on my P880 and I had the USB cable plugged in and the partitions mounted (as I had just transferred the install.zip to my phone)
leijonasisu said:
Worked perfect for me. Very easy to miss that simple "Format Data" button in TWRP. Simply type 'yes' and problem solved.
I think I got this error when I flashed SlimKAT 4.4 over on my P880 and I had the USB cable plugged in and the partitions mounted (as I had just transferred the install.zip to my phone)
Click to expand...
Click to collapse
Can i get some help please. I cant format data via TWRP, it says "E: unable to wipe data, unknow fle system, auto, unable to format to remove encryption". I did not put any encryption. What to do?

Unbrick

Hey guys,
I think I just bricked my S4 big times. I neither can mount /system nor /cache nor /efs. (I did a efs backup a while ago so I'm not concerned about that) But my phone doesn't boot, TWRP doesn't recognize any OS etc. It happened after I flashed the Domination Theme over Omega 10 (MH8). I have a working backup. Any way to get system, cache and efs to mount again? I really have to have a working phone tomorrow.
No need for help anymore. Fixed it by wiping system and cache manually through advanced wipe options in twrp. After that I was able to restore from my backup
Send from my flying Galaxy S4

Unable to mount /system, Error mounting /system!

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.

Failed to mount /cache in stock recovery

I'm using a Asus Zenfone 5 LTE T00P (A500KL) that has been upgraded to the latest official 5.0 ROM for a few months. Phone has not been rooted & is completely stock.
Suddenly out of the blue today, a series of forced stop error messages started appearing and I was unable to cancel all of them without rebooting the phone.
I decided to reboot into the recovery mode and that's when I saw a string of error messages that the cache partition cannot be mounted.
I have not seen this before previously.
Even when I tried to clear the cache partition, the same error message appears.
Is there a way to recover from this error without factory resetting the whole device?
I have not backed up all the data since upgrading so I'm somewhat hesitant to proceed with the FR.
I have been able to run a ADB Backup but I'm not sure if the backup.ab would be useful after the FR.
Any advise from anyone familiar with this situation?
Try to flash the actual ROM again, it shouldn't erase anything but it could help.
have you fixed this issue?
I can not flash anything in my phone anymore

Categories

Resources