Database Develop

[Q] efs mount error

Hello,
I flashed MIUI and it was very buggy for me, all apps were crashing and so on. Then i decided to flash Darky 10.1.
Followed the tutorial without any issues, but after this i got no signal. Snooped around the OS and found out it did not see my sdcard. After booting in recovery mode I saw that it could not mount the efs partition.
If i try to mount it via shell i get:
Code:
# mount /dev/block/stl4 /efs
mount: mounting /dev/block/stl4 on /efs failed: Invalid argument
I unfortunetly have no backup of the efs partition.
Did anyone else experience this problem or has a fix for this?

Push. I have that problem too... I was on Darkys ROM for some months without any flashing problems. Now i wanted to change from Darkys ROM 10.1 (Gingerbread 2.3.4) to Galnet MIUI. I had to downgrade to Froyo and then install the CWM zip in CWM. This was NOT succesful. It always says "Installation aborted (Status 7)". Then i tried to install CyanogenMod 7.1. Upgraded to Gingerbread Stock with CWM 3 and when i first flashed it via ODIN the phone first booted in the standart Android CWM display (dont know the name sry). The phone automatically formated cache etc. but then it showed me 2 times "/efs is not mounted". I was able to boot and to open CWM but ALWAYS when i want to install ANY CWM ROM it shows me the message with Status 7 ...
How can i mount /efs again and make CWM ROM Flashing able again?
Thank you.

[Q] Can't mount /data!

When I backup or restore by CWM, I can backup system but data it said "Can't mount /data!"
I'm using cm-9-20120610-NIGHTLY-galaxysmtd
Try to flash many rom but didn't work T_T

Sounds like you could do with installing a stock ROM with.pit as well, hopefully that will sort your partitions out

If you're restoring and get the can't mount /data! message, do the restore again. It usually happens for me especially if I'm restoring to a rom with a different kernel that uses a different cwm recovery

[Q] [HELP] Error mounting /system & /cache in stock recovery

Guys need your attention & a consoling solution for my bricked phone, that can go in recovery & download mode. But the stock recovery mode says
--Applying multi CSC--
E:failed to mount/system(Invalid arguement)
E:failed to mount/cache(Invalid arguement)
E:cant open /cache/recovery/log
The troubled began when i added internet tweaks to build.prop.
When i reboot, phone got stuck at samsung logo.
Then when i opened cwm their i found error mounting system, & was unable to restore backups but when i used Rafael's "FORMAT ALL EXT4.ZIP" i was able to mount /system in cmw but these errors got shifted to stock recovery
now i'm able to flash zips & restore backups but of no use. still phone stuck at logo
Do i need to take my phone to Service center or any other advices?

nayser said:
Guys need your attention & a consoling solution for my bricked phone, that can go in recovery & download mode. But the stock recovery mode says
--Applying multi CSC--
E:failed to mount/system(Invalid arguement)
E:failed to mount/cache(Invalid arguement)
E:cant open /cache/recovery/log
The troubled began when i added internet tweaks to build.prop.
When i reboot, phone got stuck at samsung logo.
Then when i opened cwm their i found error mounting system, & was unable to restore backups but when i used Rafael's "FORMAT ALL EXT4.ZIP" i was able to mount /system in cmw but these errors got shifted to stock recovery
now i'm able to flash zips & restore backups but of no use. still phone stuck at logo
Do i need to take my phone to Service center or any other advices?
Click to expand...
Click to collapse
The reason you are getting those errors is that stock recovery cannot handle ext4, that's normal.
Probably the simplest thing to do would be to follow the unbrick tutorial:
http://forum.xda-developers.com/showthread.php?t=1840645

thanks for specifying the Ext4 problem...
can i get back to Ext3 by flashing any zip through cmw recovery?

Well rfs is the default file system format, not ext3. If you use this version of CWM then you can go to mounts and storage > format /cache, /system and /data back to rfs. However you will obviously now have no ROM on your phone so will still need to either restore a backup or flash a zip of a ROM that includes the entire /system folder, which is most, if not all. I've never tried this technique by the way, so no guarantees here.
Also try to restore only Nandroid backups made with the same version of CWM that you are using to avoid problems.

E:Unable to stat - Internal storage corrupt - can't wipe or restore in TWRP

E:Unable to stat. Followed by file names when updating partition details.
Following a recent flash I started to notice I have files which are throwing an error and its meaning I can't cleanly wipe or restore meaning the phone in a bad way. Typical error at start of thread title.
Anyone any extra ideas? I'm ready to face losing /data/media if I can somehow get this to function.
I'm using a moto X 2014 on TWRP 2.8.7 but I think the issue is device agnostic. I am seeking out the stock images now. Presume if I flash complete stock images I can overwrite the corrupt partitions?
I can get it to flash an OS with a bit of media process crashing at first. If I can get back to a clean state I'm confident I have a nandroid ready to go (fingers crossed uncorrupted).
Thanks for any guidance!

I have the exact same problem, when I reflashed TWRP it seemed to fix it until I restored my data partition from a nandroid backup where the issue came back.

TWRP - unable to mount /system after restore TWRP backup

Hi every1
Like in title - I have TWRP 3.3.1.0. Flashed Revenge OS, installed & setuped everything what I need. Done the TWRP backup. Tried other ROMs but want to go back to Revenge. When I try to restore that backup in the end of a process TWRP informs me that "Failed to mount '/system/ (invalid argument)" and ofcoz phone didn't boot. Tried to go back to TWRP 3.2.3.0, change the system partition to ext2 and back to ext4 - no luck. Any suggestions?