Database Info

failed to mount /efs

Hello there guys. i have an "E: failed to mount /efs (invalid argument)" problem to my s7 G930F Exynos.
The phone is NOT rooted. Had NOT activated OEM unlock or USB debbuging.
I tried to flash the stock rom and i succeeded but the problem is still there.
I dled and flash the G930F_FD_Factory_Binary and i succeeded but the problem is still there.
I tried to flash a custom recovery like TWRP but Odin fails every time on both stock rom and Factory Binary (i guess the lack of OEM unlock or USB debbuging causing that).
I managed to access ADB command while on Factory Binary only but still didn't manage anything at all.
I cannt do a factory/wipe reset cause of the "E: failed to mount /efs (invalid argument)" problem.
I am out of ideas. I sent the phone to Samsung Service but cause of a small damage in the down right corner they ask me 250 euros to fix the damage and the /efs problem. They told me that they cannot fix the /efs problem alone.... Why ? Do not ask me.. It's their procedure
So... i need your help :/

I had this problem also on my samsung tablet and seems that i got it fixed by fxing it from the twrp recovery. There is a option in the settings to fix permissions and guess this is the problem you are having it also. It cant be mounted because it has no rights.

RiTCHiE007 said:
I had this problem also on my samsung tablet and seems that i got it fixed by fxing it from the twrp recovery. There is a option in the settings to fix permissions and guess this is the problem you are having it also. It cant be mounted because it has no rights.
Click to expand...
Click to collapse
i cannt install TWRP

soulremover said:
I cannt do a factory/wipe reset cause of the "E: failed to mount /efs (invalid argument)" problem.
Click to expand...
Click to collapse
Can you do a factory reset from the stock recovery? It may be worth a try, but I think it won't help.
Likely, the EFS partition got corrupted for some reason. And as far as I know, this isn't easily fixable. This partition contains the IMEI and other information, and is encrypted + secured by certificates. One can't just copy the EFS from another phone.
Maybe the Samsung service is the only option .

Or try to root it so you have system access and then you can see if you can get to the efs folder and then try the permissions. But its weird that you get this by just flashing stock with odin. Only thing i would do is use kies to revert back to stock rom and see what happens

I'm having the same problem
I'm having the same problem, have you solved it yet?
Thx!

same problem here. can't load in TWRP and don't know how to root form recovery screen? The load screen is block by custom load. FRP locked

Can you use adb ?

SrKag said:
can't load in TWRP and don't know how to root form recovery screen? The load screen is block by custom load. FRP locked
Click to expand...
Click to collapse
If flashing the stock ROM (maybe try different versions) and doing a factory reset doesn't solve it, send it in for warranty.
Don't try flashing TWRP or rooting - it won't work if you didn't enable OEM unlocking (= disable the FRP) in the developer options before. With FRP enabled, the device runs only stock software.
And as I stated before: Even if you would have full access to the phone's memory (via a debug interface of the CPU) and therefore could flash whatever you want, there is no known way to repair the EFS. It is encrypted and device specific to prevent "bad guys" from changing the IMEI.
But still, I find it really bad that flashing stock firmware via Odin can damage the EFS partition.

Yea try to flash a stockrom with the samsung KIES tool and if that doesn't work then send it back.

Nothing will work I no I had the efs problem can u use adb?
Sent from my Samsung Galaxy S7 using XDA Labs

Hi I hope you can help......I have this ERROR & I tried several ways to fix it Running the EFS Professional.exe as Administrator.....& it keeps telling me I don't have enough storage & I deleted a bunch of apps & data from phone /sd but I keep getting this error unable to back up certain partitions
dd:writing'/sdcarrd efsprobackup/temp/userdata no space left on device
887462+0records in
887461+0records out
363504025 btes (3.4gb) copied,94,239635 seconds,36.8 MB/s
exitcode=1
now I tried odin method & it says invalid binary,......plz assist.......I tried flashing firmware N910TUVS2EQB1_N910TTMB2EQB1_N910TU VS2EQB1_HOME.tar.md5 bl/cp but it didn't work

Same issue here. My phone entered a bootloop after an OTA update about a month ago. It was 100% stock, not rooted, not even OEM unlocked i was just using it as is.
It goes in download mode , goes in recovery also. In recovery is giving the following error >
No Support SINGLE-SKU
Supported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity error
I tried sending it for warranty ... they refused - it has marks of falling, but no cracks or damage 100% perfect condition.
Then I tried using KIES recovery , goes 100% , phone restarts ... same, bootloop, and same error in recovery.
Same thing with SmartSwitch.
Same thing with Odin.
never rooted, not even developer options enabled ... used it "as is" and just "OK"-ed the OTA updates when they arrived ... only issue i ever had was a few days before the bootloop , i tried to take a picture, the screen went black and no response from the device ... my pictures were saved by default to the SD Card (class 10, Adata), so i powered it off - vol up + power + home , the phone booted, then i switched it off, and took the sd card out and no issues for 2 days, then the OTA update (already was at 7.0) which was a small one ~300mb ... installed, the phone worked till the next morning and the screen froze while i was using Gmaps ... powered it off as before ... and the bootloop was evident
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT: SM-G930F
CURRENT status: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 0(0x0000)
RP SWREV: B:1 K:0 S:0
Recovery >
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing COMBINATION ROM does go 100% , but still bootloop
_____________________________________
Can not send for warranty - has marks of falling , the service shop refused warranty - 3 repair shops gave up and said they don't know how to repair the device. Can not load custom recovery FRP is ON, KIES and SMARTSWITCH emergency firmware recovery goes 100% , again bootloop.

thehost said:
Same issue here. My phone entered a bootloop after an OTA update about a month ago. It was 100% stock, not rooted, not even OEM unlocked i was just using it as is.
It goes in download mode , goes in recovery also. In recovery is giving the following error >
No Support SINGLE-SKU
Supported API: 3
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
E: failed to mount /efs (Invalid argument)
dm-verity error
I tried sending it for warranty ... they refused - it has marks of falling, but no cracks or damage 100% perfect condition.
Then I tried using KIES recovery , goes 100% , phone restarts ... same, bootloop, and same error in recovery.
Same thing with SmartSwitch.
Same thing with Odin.
never rooted, not even developer options enabled ... used it "as is" and just "OK"-ed the OTA updates when they arrived ... only issue i ever had was a few days before the bootloop , i tried to take a picture, the screen went black and no response from the device ... my pictures were saved by default to the SD Card (class 10, Adata), so i powered it off - vol up + power + home , the phone booted, then i switched it off, and took the sd card out and no issues for 2 days, then the OTA update (already was at 7.0) which was a small one ~300mb ... installed, the phone worked till the next morning and the screen froze while i was using Gmaps ... powered it off as before ... and the bootloop was evident
ODIN MODE
DOWNLOAD SPEED: FAST
PRODUCT: SM-G930F
CURRENT status: Custom
FRP LOCK: ON
Secure Download : Enabled
WARRANTY VOID: 0(0x0000)
RP SWREV: B:1 K:0 S:0
Recovery >
Flashing COMBINATION ROM does go 100% , but still bootloop
_____________________________________
Can not send for warranty - has marks of falling , the service shop refused warranty - 3 repair shops gave up and said they don't know how to repair the device. Can not load custom recovery FRP is ON, KIES and SMARTSWITCH emergency firmware recovery goes 100% , again bootloop.
Click to expand...
Click to collapse
hi
Unfortunately, your device's efs partition has been compromised.
Try to write a rom of 4files on the phone if it does not answer, you need to restore the efs file on your phone
This is a backup of my s7 g930f efs.
http://efs.firmware.ir/g930fds/
If you use this efs file, your device will be changed or deleted imei number.
Try to solve with a combination or other ways. If you do not solve your problem, you can use the efs placed
good luck

asgharSo said:
hi
Unfortunately, your device's efs partition has been compromised.
Try to write a rom of 4files on the phone if it does not answer, you need to restore the efs file on your phone
This is a backup of my s7 g930f efs.
.................................................................................................
If you use this efs file, your device will be changed or deleted imei number.
Try to solve with a combination or other ways. If you do not solve your problem, you can use the efs placed
good luck
Click to expand...
Click to collapse
what do you mean write a rom ? i don't understand ... please elaborate ... i downloaded your backup but you say i need TWRP to use it, right ? or it should be flashed with Odin ?

thehost said:
what do you mean write a rom ? i don't understand ... please elaborate ... i downloaded your backup but you say i need TWRP to use it, right ? or it should be flashed with Odin ?
Click to expand...
Click to collapse
For your flash you should use this ROM.
And you need twrp to restore the efs file.
Requirements and how to use efs in the posted efs post.

I tried the rom you posted, no effect, then tried TWRP ... FRP ON blocks the install ? can not install it

hi . . how to fix sm-n935f note 7 fe .. failed to mount efs , failed to find misc partition . . rmm state : prenormal .. stuck at boot logo .. any solution to fix it ?

i am also having same problem. I am unable to resolve the issue. i had tried all the solutions, which are posted here nothing worked. At last i gave in service center, to flash the stock rom. The mentioned it can't be done and there is a problem with board. Board has to replaced.
Kindly suggest the solution for it. Thanks in advance.:fingers-crossed::laugh:

maybe try this:
https://forum.xda-developers.com/ga...covery-official-twrp-herolte-t3333770/page125

Installing system update fail after Odin flash. Boot into recovery mode.

Hi,
My phone (S7) got into a boot loop for no apparent reason. I noticed it was a bit hot and it froze a couple of times so I rebooted it and after that it was stuck in a boot loop no matter what. I then tried "flashing" the latest firmware with Odin3 to fix it. Everything was fine in Odin but after the phone rebooted, it couldn't finish installing the patch... It showed an "error!' screen then booted into Android Recovery with these logs:
#fail to open recovery_cause(No such file or directory)#
#Reboot Recovery Cause is UNKNOWN
No Support SINGLE-SKU
File-Based OTA
E:failed to mount /efs (Invalid argument)
supported API: 3
E:failed to mount /efs (Invalid argument)
E:failed to mount /efs (Invalid argument)
dm-verity verification failed...
E:failed to clear BCB message: failed to fin /misc partition
Click to expand...
Click to collapse
At this point I'm not sure what I can do... I would really like to avoid a factory reset as I have a lot of data on my phone I would like to keep.
Thanks!

normsrayn said:
Hi,
My phone (S7) got into a boot loop for no apparent reason. I noticed it was a bit hot and it froze a couple of times so I rebooted it and after that it was stuck in a boot loop no matter what. I then tried "flashing" the latest firmware with Odin3 to fix it. Everything was fine in Odin but after the phone rebooted, it couldn't finish installing the patch... It showed an "error!' screen then booted into Android Recovery with these logs:
At this point I'm not sure what I can do... I would really like to avoid a factory reset as I have a lot of data on my phone I would like to keep.
Thanks!
Click to expand...
Click to collapse
Hello, this problem is very common for people that root their phones if you get drk error then there are 2 methods to solve this
Method one : easy
Just flash cf autoroot with odin download the file for your phone and flash it in ap
You may get stuck or get bootloops in splash screen or red errors just wait patiently until rom boots
Method 2 : for if you want no root (ota still impossible)
Flash twrp with odin, then download the no verity file
And move it to your phone, in twrp tap on install and select the file
https://build.nethunter.com/android-tools/no-verity-opt-encrypt/
Just download the latest version of the file (6.0)
Now wait until rom boots
-----------------------------------------------------------------------------------
Please donate and like if you think i deserved it,
If it didnt work you don't have to do it
Happy flashing and good luck
Dont forget to update me after following the steps

I'm a total newbie when it comes to phone flashing, I have a few questions. If I decide to use autoroot, is there a chance for a brick? What could go wrong? I think there's no turning back from rooting a device, right? I don't want to lose my data.
Also, I can't seem to make TWRP work because when I plug the phone to the pc it doesn't recognize it and I can't access it whatsoever to put the files in there, even after installing the drivers.
Thanks!

normsrayn said:
I'm a total newbie when it comes to phone flashing, I have a few questions. If I decide to use autoroot, is there a chance for a brick? What could go wrong? I think there's no turning back from rooting a device, right? I don't want to lose my data.
Also, I can't seem to make TWRP work because when I plug the phone to the pc it doesn't recognize it and I can't access it whatsoever to put the files in there, even after installing the drivers.
Thanks!
Click to expand...
Click to collapse
Flash the stock firmware again but from download the firmware from Samfirm application. Please use the HOME_CSC too or your device is wiped. If you need the firmware just post modelnumber or name idk and CSC code and i can post a link with the firmware for you. TWRP can't mount /data and you will need to format your phone with means you lose everything.

getting dark error in galaxy j4 smj400F after system update failing
Picklewickle said:
Hello, this problem is very common for people that root their phones if you get drk error then there are 2 methods to solve this
Method one : easy
Just flash cf autoroot with odin download the file for your phone and flash it in ap
You may get stuck or get bootloops in splash screen or red errors just wait patiently until rom boots
Method 2 : for if you want no root (ota still impossible)
Flash twrp with odin, then download the no verity file
And move it to your phone, in twrp tap on install and select the file
but i have done factory reset so how to enable oem /unlock bootloader to flash via odin
HELP
-----------------------------------------------------------------------------------
Click to expand...
Click to collapse

Same issue
I have the same issue. I cant boot into download mode at all to even attempt to flash anything

E:Failed to mount EFS ( Invalid Argument)

Hello friends, when I flash Combination file, or stock file , my phone boots and hang at start up logo, while I restart to recovery I see this error (E:Failed to mount efs, Invalid Argument)?
Can anyone help?

What have you done ? Trying to root and lost your IMEI ?
If so, then go to recovery and do all of the wipes and format Data. Once done, then just flash the exact same ROM as the one which is already installed on your phone.

TheRealKeyserSoze said:
What have you done ? Trying to root and lost your IMEI ?
If so, then go to recovery and do all of the wipes and format Data. Once done, then just flash the exact same ROM as the one which is already installed on your phone.
Click to expand...
Click to collapse
This steps does not work, I need EFS for A8 2018.

I'm having the same problem, I've tried everything. z3x, Odin , won't even let me flash from sd card. Won't load into Oreo just keeps rebooting. I can get into recovery but does nothing as well as boot loader. I did have a utility im pretty sure was made by FACTORY BINARY that was it's own little OS with a bunch of little tools. I have a sm-a530w flashed with boot loader 4 ugggg. If anyone can help find that utility that will wipe the whole thing and let me flash from scratch that would be awesome. I've tryed miracle, Uni-Android, samsung tools 29.5 and flashing with odin. Lets me flash factory FIRMWARE but still error's out on the "Failed to mount EFS" HELPPLEASE

A quick suggestion you probably tried, but i've had failure at boot in the past after returning to stock via odin if i used home_csc. So, if you haven't already tried, use just csc. No home. On home it does system.img until the end, no user_data . Not sure at all what the deal is but it's all i can suggest. Get 'er goin'!

:Failed to mount EFS
Yes I think I tried that, but at this point, I try again. Any more suggestions would be greatly appreciated. An A8 in mint shape just hurts LOL.

Unable to keep flashed recovery or rom. Device restores everything after reboot

I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz

FSCK check on /data returned this:
Code:
~ # e2fsck /dev/block/platform/dw_mmc/by-name/USERDATA
e2fsck 1.41.14 (22-Dec-2010)
/dev/block/platform/dw_mmc/by-name/USERDATA: recovering journal
Superblock needs_recovery flag is clear, but journal has data.
Run journal anyway<y>? y
yes
e2fsck: unable to set superblock flags on /dev/block/platform/dw_mmc/by-name/USERDATA
And Odin mode: NAND ERASE ALL returns
Code:
<ID:0/006> Complete(Write) operation failed.
It seems like my Note 10.1 tablet is suffering from the emmc brick bug.

niquedegraaff said:
I've got an old Samsung Galaxy Note 10.1 (N8010) which was flashed to a custom ROM (Cyanogenmod) in 2016. I'm not sure what version because I'm unable to boot it. A few weeks ago, the tablet rebooted without reason and got stuck on the Cyanogenmod bootscreen forever. I've let it run for 24 hours without result.
So this is what I tried:
Reboot into recovery mode (TWRP 2.8.6.0) and wipe everything. Then I tried to flash a different ROM, but when the device reboots, everything seems to be reset and it tries to boot the old corrupted ROM again. I also tried a newer version of LineageOS. But for that, I need a newer TWRP version. So I download and put the newest TWRP version on it using ODIN mode. Flash Passes says ODIN, but after reboot, TWRP 2.8.6.0 is still being loaded. I tried it again without 'reboot' checked so I can reboot directly back into recovery manually, but this also, didn't worked. (by the way, ADB works when loading TWRP, FASTBOOT doesn't work when loading ODIN mode, fastboot doesn't recognize the device)
I tried to flash stockrom back onto the device, also using ODIN mode. Flash passes, no errors. Device reboots and.. nope! It still tries to load the old Cyanogenmod forever.
I'm basically stuck here. I can't update to a newer Recovery and I cant flash the rom because everytime I reboot the device, everything change i made is gone.
I noticed that when I list files in /data the folder seems to be empty.
I also tried to reformat /data to fat and back to ext4 but formatting to fat fails and formatting to ext4 succeeds, however, after a reboot, everything i did seems to be undone by the device. Even the time and date is reset.
Is there a way I can bring back my tablet back to life? Thank you!
I have pulled the recovery.log file and uploaded it to pastebin.
I can't post a link to it because I do not have made 10 posts yet.. (very anoying). So i put the adress here:
https://pastebin.com/3muqPMzz
Click to expand...
Click to collapse
Some of what you describe seems to suggest that your internal sdcard is corrupted, but, you still have TWRP booting. I would think that TWRP wouldn't boot if the internal was damaged.
Sent from my LGL84VL using Tapatalk

I can boot twrp but anything I do in there is temporary. I can't write to the internal SD. Only read. Seems like the emmc brick bug to me. I wish there was a way to check if this is absolutely true.

e: failed to mount /efs (invalid argument) on Samsung Galaxy NOTE 4 MODEL: N910H

Hi Geniuses!
Please save a soul!
At first, i was trying to fix my Samsung sm-N910H imei and baseband version.
I downloaded and flashed all sort of Samsung official firmwares of N910H of different versions including 5.0.1, 5.1.1 and latest 6.0.1 still to no avail.
I came across efs repair file online flashed it to my rom BOOM!!! that is the beginning of the end.
Now i try installing official ROM it fails on hidden.img.
I sorted it out by extract and removing the hidden.img file.
It flashed successfully. But guess what? it stocks on samsung boot logo before then, see attached d recovery mode log before attempting to boot.
DOWNLOAD MODE, samsung firmware: official, system status: custom
e: failed to mount /efs (invalid argument)
have installed CWM Custom recovery tried all sort nothing positive.
Please i need help as i want to boot to my system even without the imei and baseband saga, i would just use the phone as phablet with just wifi connection.
Your response is anticipated with much thanks!!

Seems /EFS partition where IMEI and all network related stuff is stored, doesn't no longer exist or got corruped.
Because original Android OS got tampered DM-Verity check must fail.

jwoegerbauer said:
Seems /EFS partition where IMEI and all network related stuff is stored, doesn't no longer exist or got corruped.
Because original Android OS got tampered DM-Verity check must fail.
Click to expand...
Click to collapse
Exactly, i agree with you.
It has a solution or the phone is permanently damaged!?