• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Q] Failed to mount /efs (Invalide argument) and not Start

Search This thread

Michael833

Senior Member
Jun 29, 2008
95
8
The Hague
My Samsung galaxy note 10.1 was stuck at the logo and could not boot...the stock recovery mode displayed E:failed to mount /efs (invalid argument) so I took it to a Samsung Service Centre that said the only way to fix it is to change mother board.

Thanks to you I now have a fully functioning tablet. Thank you very much and keep up the good work.

1. Flash CF-Auto root
2. Flash CWM recovery
3. Install Minimal ADB and fastboot (if you do not have Android tools sdk) this a small file.
4. Connect the device to the computer
5. Boot the device into CWM recovery
6. Choose Mount storage/mount system
7. Open Minimal ADB or command prompt
8. type: adb shell
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
9. When you reboot you will see your screen with a yellow text..to get rid of it, install
root explorer (paid)
10. Navigate to /efs/factorymode and open as text
11. Change the (OFF) and replace with (ON) and save the file
12. Reboot

All done.

When I type:
D:\Users\Misho\AppData\Local\Android\sdk\platform-tools>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
D:\Users\Misho\AppData\Local\Android\sdk\platform-tools>

Also, when I try to skip forward to the mke2fs step, nothing seems to happen there either. Am I doing something wrong? Any help anyone can provide will be greatly appreciated.
 

Michael833

Senior Member
Jun 29, 2008
95
8
The Hague
Not at all sure what I've done to the thing

Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system



2 on computer Shift+Ctrl +right click to open command window
command window type

cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
mount -w -t ext4 /dev/block/mmcblk0p3
reboot

this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it

root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done

factorymode

Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal

Folks,
I'm sorry to ask so many questions, but I'm totally defeated here. Basically it seems that I lost my /efs directory. I wasn't doing anything. Tablet had been on the nightstand for ~15 hours. OS had been on there for 3 months, etc. I wasn't flashing anything.

At first I tried to reboot and clear caches. That didn't work, so I formatted /system and /data, etc. I tinkered again for a while, eventually trying to put a new recovery on. That's when I think things went really wrong.

OK, fast forward to now. I have CWM 6.0.1.1 on there. I have no idea what firmware is on the tablet, but I'm guessing it would be useful to find out. Since getting CWM loaded, I tried to run adb shell and got:
exec '/system/bin/sh' failed: No such file or directory

so evidently I'm missing something. I tried to inject root, but I think I'm using the wrong file. Or, maybe it's the emmc. I can't tell if maybe my emmc is somehow corrupt or something. Again, if anyone has suggestions on what I should do I'd really appreciate it.

I was most recently running Gnabo v7 (4.4.2) I believe. I'm not entirely sure, as it had been a while since I had loaded it.

I really am desperate. Complicating this is the problem with goo.im being down, so I can't really get the files I'm supposed to. I have searched dozens of different threads at each stage of these problems, but I'm striking out. I'm getting to the point with this situation where I'm seriously contemplating buy a new tablet, but there isn't anything out there that interests me. I'm happy to donate for help.

Lastly, I can't even figure out how to turn this thing off. It's all all the time. Freaking relentless. Suggestions?

I'm running a Win7 and a Win 8.1, both x64.
 
Last edited:

dovedescent7

Senior Member
Jun 18, 2011
263
12
Please help I was running android revolution hd on n8000 got messed up folloeedbthese directions back at stock 4.0 Portugal ..


Finally followed directions get inside root explorer and there is no factory ANYTHING inside folder... when tabletc reboots it is In factory mode please help
 

dovedescent7

Senior Member
Jun 18, 2011
263
12
Must odin back to original ICS rom to work
Assuming you have CWM installed on device and have androidsdk store on computer C: drive
device must be rooted
1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system



2 on computer Shift+Ctrl +right click to open command window
command window type

cd c:/androidsdk/tools
adb shell
su
mke2fs /dev/block/mmcblk0p3 ( skip to next step if faill
mount -w -t ext4 /dev/block/mmcblk0p3
reboot

this will create a generic EFS files on device
when you reboot you will see your screen with a yellow text..now time to get rid of it

root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
reboot in recovery wipedata factory reset...done

factorymode

Now you can back up your efs.tar(for 8000 user only)
Reboot and everthing should be back to normal


C:\Minimal ADB and Fastboot>adb shell
error: more than one device and emulator

C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # su
su
[email protected]:/ # mke2fs /dev/block/mmcblk0p3
mke2fs /dev/block/mmcblk0p3
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
5136 inodes, 20480 blocks
1024 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=20971520
3 block groups
8192 blocks per group, 8192 fragments per group
1712 inodes per group
Superblock backups stored on blocks:
8193

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 28 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
mount: can't find /dev/block/mmcblk0p3 in /etc/fstab
1|[email protected]:/ # mke2fs /dev/block/mmcblk0p3
mke2fs /dev/block/mmcblk0p3
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
5136 inodes, 20480 blocks
1024 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=20971520
3 block groups
8192 blocks per group, 8192 fragments per group
1712 inodes per group
Superblock backups stored on blocks:
8193

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
mount: can't find /dev/block/mmcblk0p3 in /etc/fstab
1|[email protected]:/ # REBOOT
REBOOT
sh: REBOOT: not found
127|[email protected]:/ # REBOOT
REBOOT
sh: REBOOT: not found
127|[email protected]:/ # reboot
reboot





and this is what i have on the screen!!! ALSO FACTORY MODE error when android boots

2015_08_29_21_27_04.png
 

tanker32

Senior Member
Factory mode

C:\Minimal ADB and Fastboot>adb shell
error: more than one device and emulator

C:\Minimal ADB and Fastboot>adb shell
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
~ # su
su
[email protected]:/ # mke2fs /dev/block/mmcblk0p3
mke2fs /dev/block/mmcblk0p3
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
5136 inodes, 20480 blocks
1024 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=20971520
3 block groups
8192 blocks per group, 8192 fragments per group
1712 inodes per group
Superblock backups stored on blocks:
8193

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 28 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
mount: can't find /dev/block/mmcblk0p3 in /etc/fstab
1|[email protected]:/ # mke2fs /dev/block/mmcblk0p3
mke2fs /dev/block/mmcblk0p3
mke2fs 1.41.14 (22-Dec-2010)
Filesystem label=
OS type: Linux
Block size=1024 (log=0)
Fragment size=1024 (log=0)
Stride=0 blocks, Stripe width=0 blocks
5136 inodes, 20480 blocks
1024 blocks (5.00%) reserved for the super user
First data block=1
Maximum filesystem blocks=20971520
3 block groups
8192 blocks per group, 8192 fragments per group
1712 inodes per group
Superblock backups stored on blocks:
8193

Writing inode tables: done
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 38 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
[email protected]:/ # mount -w -t ext4 /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
mount: can't find /dev/block/mmcblk0p3 in /etc/fstab
1|[email protected]:/ # REBOOT
REBOOT
sh: REBOOT: not found
127|[email protected]:/ # REBOOT
REBOOT
sh: REBOOT: not found
127|[email protected]:/ # reboot
reboot





and this is what i have on the screen!!! ALSO FACTORY MODE error when android boots

2015_08_29_21_27_04.png

Just create new file named factory mode in directory EFS. And in this file just write OFF
Should be work!
 

dovedescent7

Senior Member
Jun 18, 2011
263
12
Just create new file named factory mode in directory EFS. And in this file just write OFF
Should be work!


so in efs create a text file named FACTORY MODE?

Then Inside FACTORY MODE, Make NEW file and name this file OFF? ...or make text file inside factory mode filke, and inside Text file write the words "OFF"?

i am confusion

also, i never made backup of efs. efs file exists because i had to create a new one.....

please advise
 

dovedescent7

Senior Member
Jun 18, 2011
263
12
Just create new file named factory mode in directory EFS. And in this file just write OFF
Should be work!

so i tried your solution.. i opened up the file and it says ON already!!!

So i did this solution...

Now its working ! wow... i was very skeptical.. And we have fixed our N8000


Apparently it was messed up because of android revolution hd





THIS BELOW IS THE SOLUTION THAT FIXED MY N8000

Here is the exact solution for this problem which i have recently had!

You have to root your phone and install Terminal Emulator from Google Play.

Open terminal emulator and type as ;

su
rm /efs/FactoryApp/keystr
rm /efs/FactoryApp/factorymode
echo -n ON >> /efs/FactoryApp/keystr
echo -n ON >> /efs/FactoryApp/factorymode
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot

You now should not see the that message anymore. Its because of an EFS corruption. ( Thanks to yesilcin*com) for exact solution.
Hope it helps!!!
 

vitortakeda

Member
Nov 30, 2015
14
0
so i tried your solution.. i opened up the file and it says ON already!!!

So i did this solution...

Now its working ! wow... i was very skeptical.. And we have fixed our N8000


Apparently it was messed up because of android revolution hd





THIS BELOW IS THE SOLUTION THAT FIXED MY N8000


I'm gonna try this and the above solutions to see which one will work on my N8000 as well. Thanks for sharing the information. I'll be back soon with new feedback about it.
 

vitortakeda

Member
Nov 30, 2015
14
0
Ok, i'v installed androidsdk 3Gb files. O_O. Then, its updates and bla bla bla. My device is rooted with an 4.0 stock rom, german version. But something I didn't unsderstand. "2 on computer Shift+Ctrl +right click to open command window
command window type"
...Excuse me?? hahaha. I didn't get that! Can someone elaborate this any better to me please? So I can move on and revive my N8000. I have also downloaded Minimal ADB and Fastboot as well in case of need. I just need to recover my /efs that is either corrupted or was deleted somehow when I flashed/formated the tablet. So please explain me more from the step 2 that I'm still confused about how to proceed.
 

vitortakeda

Member
Nov 30, 2015
14
0
so i tried your solution.. i opened up the file and it says ON already!!!

So i did this solution...

Now its working ! wow... i was very skeptical.. And we have fixed our N8000


Apparently it was messed up because of android revolution hd





THIS BELOW IS THE SOLUTION THAT FIXED MY N8000



WONDERFULLY WORKED!! Although my tablet is not showing my phone card. Is like the IMEI is wrong, or something that I don't know. Everytihng works fine, but the phone card for phone calls and stuff.
 

rohit1521

Senior Member
Oct 1, 2015
86
46
kerala
forum.xda-developers.com
1. Run Odin with Administrator Privileges. Hope everyone is familiar with using Odin or See this
2.Connect your device inn Download Mode (HOLD Volume Down+Home Button+Power if you are on samsung) and see phone gets detected by Odin.
3. Click on the PIT Button in Odin and select the .pit file you have downloaded.
4. Click on PDA, and Browse for the original Stock Firmware File of Samsung Galaxy Grand I9082.
5. Ensure that The Checkboxes Auto Reboot, Re-Partition, F. Reset Time are checked.

you ca n get .pit file from google...
 

Kevin95ME

Member
Jun 25, 2020
6
1
26
Los Teques
HELP Samsung S6792L Can´t open E:/efs/log/boot_cause

Hi , i'm new in XDA , first i want to say, excuse me if i am posting in a wrong place, i can't find the right place for make a new thread.
i have a samsung S6792L fame lite, is stuck in samsung logo i make flash of stock rom via odin , stock rom (home.tar)1 file and flash stock rom of 4 files (Boot, Pda, phone , csc); then i flash a custom recovery (TWRP 2.8.6.0 for S6790) i mount efs partition but when i try open efs folder , the phone shut down and vibrate for 3- 4 seconds. also cannot do backup of efs folder because happen the same thing (shut down)

i can't find the PIT file for this model , and i don't know what can i do for solve this. please help.

thanks for your time.

(excuse me for my bad english)
 

emreaydin41

New member
Oct 23, 2021
3
0
Hi;
there is a problem with my Samsung GT-N8005 Tablet.
"Samsung GT-N8005 Failed to mount /efs (invalid argument)"
I'm getting an error can you help me?
 

emreaydin41

New member
Oct 23, 2021
3
0
gT-N8005 tabletim hiç açılmıyor, görünüşe göre herhangi bir şey yüklemem mümkün değil.

Translated by GT: My gT-N8005 tablet won't boot at all, apparently I'm not able to install anything.
 
Last edited by a moderator:

emreaydin41

New member
Oct 23, 2021
3
0
Konuyu en başından sonuna kadar okudum ve sorunuma bir çözüm bulamadım. Failed to mount /efs (Geçersiz argüman) sorununa çözüm bulan biri detaylı bir açıklama yazabilir mi?

Translated by GT: I read the thread from beginning to end and couldn't find a solution to my problem. Can someone who has found a solution to Failed to mount /efs (Invalid argument) issue a detailed explanation?
 
Last edited by a moderator:

Top Liked Posts

  • There are no posts matching your filters.
  • 27
    Must odin back to original ICS rom to work
    Assuming you have CWM installed on device and have androidsdk store on computer C: drive
    device must be rooted
    1..Plug Device to Computer.. Reboot Device in CWM recovery/ mount storage/ mount system



    2 on computer Shift+Ctrl +right click to open command window
    command window type

    cd c:/androidsdk/tools
    adb shell
    su
    mke2fs /dev/block/mmcblk0p3 ( skip to next step if fail)
    mount -w -t ext4 /dev/block/mmcblk0p3
    reboot

    this will create a generic EFS files on device
    when you reboot you will see your screen with a yellow text..now time to get rid of it

    root explorer/efs and delete factorymode(OFF) and replace with factorymode(ON)
    reboot in recovery wipedata factory reset...done

    factorymode

    Now you can back up your efs.tar(for 8000 user only)
    Reboot and everthing should be back to normal
    2
    for the poeple who need the stock ICS 4.0.4

    http://www.hotfile.com/dl/165813833/f958ae4/N8000XXALGA_N8000OXXALG5_PHN.zip.html

    P.S. if all Poeple who recover his System, Will post Some Useful links here, he had used .
    So I Can I make a good guide for the users with the same problems .
    i fill tonight more links,mk now Go to my work .


    Rongogo

    Sent from my GT-N8000 using XDA Premium HD app