HELP! SM-N9208 Failed to mount /Efs (invalid argument) - Galaxy Note5 Q&A, Help & Troubleshooting

I deleted my efs folder and now it says error. I have tried other fixes from xda like this using twrp and adb
Code:
adb shell
Code:
mke2fs /dev/block/mmcblk0p3
Code:
mount -w -t ext4 /dev/block/mmcblk0p3
Code:
reboot
but everytime i input the first line it says could not stat /dev/block/mmcblk0p3 --- No such file or directory.
And when i try to flash stock firmware using odin whenever i finish flashing it is stuck on samsung logo. Anyone know how to solve this problem and fix? Thanks

dukesterology said:
I deleted my efs folder and now it says error. I have tried other fixes from xda like this using twrp and adb
Code:
adb shell
Code:
mke2fs /dev/block/mmcblk0p3
Code:
mount -w -t ext4 /dev/block/mmcblk0p3
Code:
reboot
but everytime i input the first line it says could not stat /dev/block/mmcblk0p3 --- No such file or directory.
And when i try to flash stock firmware using odin whenever i finish flashing it is stuck on samsung logo. Anyone know how to solve this problem and fix? Thanks
Click to expand...
Click to collapse
If you have taken a back up of your efs through twrp then you can restore it in twrp.
Or
Download latest firmware of your device & reflash it through Odin.

Related

factory.zip to mmcblk0p3

I am pretty sure my factory.zip is corrupt or nonexistant from my mmcblk0p3. How do i move the factory.zip file over there from this thread http://forum.xda-developers.com/showthread.php?t=919353
Thanks
I just did this last night. First I booted into clockwork recovery and hooked up the nook to my computer and started up adb. I tried doing this when it was booted normally but I could not mount mmcblk0p3. Anyways once you are in recovery mode go to where adb is installed. Then these were the commands I did
Code:
adb shell mount /dev/block/mmcblk0p3 /emmc
adb pull /emmc/factory.zip factory-1.0.0.zip
adb push factory.zip /emmc/
The second line is me backing up my old 1.0.0 factory zip, just in case things went bad. Then I did the 8 failed boot reset and then reset /data
Thank You! I had something like that except i was missing emmc in the first line and i couldn't figure out why i couldnt mount mmcblk0p3. I want to make a how to once i reach 10 posts on this.
Hate to bring back an old thread, but, no matter how I have tried, I cannot mount /dev/block/mmcblk0p3... I always get invalid argument error... any help is appreciated.
>adb shell mount /dev/block/mmcblk0p3 /emmc
mount: mounting /dev/block/mmcblk0p3 on /emmc failed: Invalid argument
I have yet to be able to mount mmcblk0p3 to copy factory.zip to it.... hoping this would fix my install failed error on the 8 failed boot install.
NM.... fixed it... had to mke2fs /dev/block/mmcblk0p3 before I could mount it... got it fixed... the 8 failed boots works as it should again.

[Q]: Read-only filesystem

Hi!
I have rooted my phone (LG Optimus 2X) and mistakenly deleted some files.
I have these files, and want to push them back using adb, put my problem is, that when i try to mount the system in read / write mode using "adb remount" i get this error: "remount faileded: Operation not permitted".
I can't figure out how to fix it, i can pull files etc.
I have also tried to use the adb shell, and copy the files from the internal sdcard, but i'm getting the same error.
Only read-mode.. :/
Anybody who can help, fixing this problem?
If you want to mount /system just write:
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Then you're good to go
How to unmount into read-mode only?
Thank! - You saved my day
mrhtml said:
How to unmount into read-mode only?
Thank! - You saved my day
Click to expand...
Click to collapse
A little easier to type...
Mount r/w
Code:
busybox mount -o,remount -rw /system
Mount r/only
Code:
busybox mount -o,remount -r /system
Edit: You shouldn't post stuff like this in dev

[Q] CWR Error: Can't mount /cache

I get this error in CWR (3.2.0.1), I have a nook with a blue sticker:
Code:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/command
Nothing, and I mean Nothing I have found in this forum solved this error, including the repartition-boot-stock+factory rest.
Any help guys? I am desperate!
adb is working but shell is not
This is what I got, anyone has an idea how to recover from this?
Code:
C:\Users\Barak>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
reifba said:
This is what I got, anyone has an idea how to recover from this?
Code:
C:\Users\Barak>adb shell
- exec '/system/bin/sh' failed: No such file or directory (2) -
Click to expand...
Click to collapse
Nothing, and I mean Nothing I have found in this forum solved this error, including the repartition-boot-stock+factory rest.
Click to expand...
Click to collapse
If you repartitioned, that may be the reason the adb command is not working....
patruns said:
If you repartitioned, that may be the reason the adb command is not working....
Click to expand...
Click to collapse
So I have 2 two problems in which the solution to one causes the other...
In the mean time I manged to run both the Froyo and HoneyComb from the sd card, but not the CM7 (which is the one I am trying to install on the internal memory)
using ADB to restore
I tried to use the methods described in:
:http://forum.xda-developers.com/showthread.php?t=919353
However it is not clear where should the factory.zip go?
for some reason it also says that the /dev partition is only 244MB so I cannot flash the system.img, it is probably the partition in the SD card and not the memory, so not much advancement here either. I also think that because it gives me 11223344556677 as the S/N and not the real one.
The quest to restore the nook continues...
Is there a way to manually repartition through ADB?
or anything? cause nothing solves the first error posted in this thread
reifba said:
I tried to use the methods described in:
:http://forum.xda-developers.com/showthread.php?t=919353
However it is not clear where should the factory.zip go?
for some reason it also says that the /dev partition is only 244MB so I cannot flash the system.img, it is probably the partition in the SD card and not the memory, so not much advancement here either. I also think that because it gives me 11223344556677 as the S/N and not the real one.
The quest to restore the nook continues...
Click to expand...
Click to collapse
factory.zip and rombackup.zip should be located on /dev/block/mmcblk0p3
system should be written to /dev/block/mmcblk0p5
1123344556677 is normal for the device listing when adb'ing in when running CWM on the uSD
to write the img files you need to use:
dd if=(IMG FILE ON SD) of=(PARTITION ON /dev... i.e. /dev/block/mmcblk0p1)
to help you out...here's a list of what goes where:
mmcblk0p1-boot.img
mmcblk0p2-rom.img
mmcblk0p3-factory.img
mmcblk0p4-logical.img
mmcblk0p5-system.img
mmcblk0p6-data.img
mmcblk0p7-cache.img
mmcblk0p8-media.img
problem:
thanks for the reply, I am studying more about andriod and adb now than during all my bachelor's.
just
adb push factory.zip /dev/block/mmcblk0p3 ??
and
adb shell dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
(in some places I saw they didn't write "/block")
and where is rombackup.zip from?
the problem is that for some reason /dev/ is only 244MB so I can't dd system.img, only the boot.img.
I wish that somewhere in the world would exist something that solves it from CWR, just some zip I would install to fix boot+factory+system in one stroke...
reifba said:
thanks for the reply, I am studying more about andriod and adb now than during all my bachelor's.
just
adb push factory.zip /dev/block/mmcblk0p3 ??
and
adb shell dd if=/sdcard/boot.img of=/dev/block/mmcblk0p1
(in some places I saw they didn't write "/block")
and where is rombackup.zip from?
the problem is that for some reason /dev/ is only 244MB so I can't dd system.img, only the boot.img.
I wish that somewhere in the world would exist something that solves it from CWR, just some zip I would install to fix boot+factory+system in one stroke...
Click to expand...
Click to collapse
to get factory and rombackup zip files on mmcblk0p3...
adb shell mkdir /sdcard/tmp3
adb shell mount /dev/block/mmcblk0p3 /sdcard/tmp3
adb push factory.zip /sdcard/tmp3
adb push rombackup.zip /sdcard/tmp3
more problems (desperation is looming)
DizzyDen said:
adb shell mount /dev/block/mmcblk0p3 /sdcard/tmp3
Click to expand...
Click to collapse
when I type the above I get
Code:
[email protected]:/ # mount /dev/block/mmcblk0p3 /sdcard/tmp3
Usage: mount [-r] [-w] [-o options] [-t type] device directory
I had to do it in the shell in order to su.
reifba said:
when I type the above I get
Code:
[email protected]:/ # mount /dev/block/mmcblk0p3 /sdcard/tmp3
Usage: mount [-r] [-w] [-o options] [-t type] device directory
I had to do it in the shell in order to su.
Click to expand...
Click to collapse
then I would use
mount rw /dev/block/mmcblk0p3 /sdcard/tmp3
If that doesn't work:
mount rw -o remout /dev/bloc/mmcblk0p3 /sdcard/tmp3
but it would appear something else is amiss... since it even shows the command should have worked... since everything other than the command (mount) the device (/dev/block/mmcblk0p3) and directory (/sdcard/tmp3) are optional parameters

[Question] Samsung GS3 mini (I8190) EFS script

I have device with IMEI NULL that I want to mount (or replace the efs into generic) in adb in similar with this script:
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
Click to expand...
Click to collapse
I tried the above script but unfortunately it brokes the partition because I think that code is not for i8190, but no worry about that because I already managed to fix it with pit file.
Anybody can share it with me?especially developers please.
Thanks in advance.
cz4r3n said:
I have device with IMEI NULL that I want to mount (or replace the efs into generic) in adb in similar with this script:
I tried the above script but unfortunately it brokes the partition because I think that code is not for i8190, but no worry about that because I already managed to fix it with pit file.
Anybody can share it with me?especially developers please.
Thanks in advance.
Click to expand...
Click to collapse
0p3 is PIT partition. mmcblk0p11 is EFS, but i'm not sure what you're trying to do here.
tys0n said:
0p3 is PIT partition. mmcblk0p11 is EFS, but i'm not sure what you're trying to do here.
Click to expand...
Click to collapse
I'm trying to mount the efs to create generic efs.tnx for the reply
EDIT: Is this the proper way of mounting or formatting efs?
Can I used this command in general?
adb shell
mke2fs -T ext4 /dev/block/mmcblk0p11
mkdir /efs
mount -w -t ext4 /dev/block/mmcblk0p11 /efs
Click to expand...
Click to collapse
cz4r3n said:
I'm trying to mount the efs to create generic efs.tnx for the reply
EDIT: Is this the proper way of mounting or formatting efs?
Can I used this command in general?
Click to expand...
Click to collapse
I think it could work. Otherwise try
Code:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p11 /efs
tys0n said:
I think it could work. Otherwise try
Code:
mount -o rw,remount -t ext4 /dev/block/mmcblk0p11 /efs
Click to expand...
Click to collapse
I tried and here is the log:
D:\adbsdk\sdk\platform-tools>adb shell
~ # ←[6nmke2fs -T ext4 /dev/block/mmcblk0p11
mke2fs -T ext4 /dev/block/mmcblk0p11
mke2fs 1.41.11 (14-Mar-2010)
/dev/block/mmcblk0p11 is apparently in use by the
stem here!
~ # ←[6nmkdir /efs
mkdir /efs
mkdir: can't create directory '/efs': File exists
Click to expand...
Click to collapse
cz4r3n said:
I tried and here is the log:
Click to expand...
Click to collapse
Ok. Only thing I can think of is to do it from recovery and try to unmount it first.
tys0n said:
Ok. Only thing I can think of is to do it from recovery and try to unmount it first.
Click to expand...
Click to collapse
I'm doing it in recovery mode.Im using Team Win Recovery Project v2.6.0.0.
here is the log after unmounting efs from recovery:
D:\adbsdk\sdk\platform-tools>adb shell
~ # ←[6nmke2fs -T ext4 /dev/block/mmcblk0p11
mke2fs -T ext4 /dev/block/mmcblk0p11
mke2fs 1.41.11 (14-Mar-2010)
Filesystem label=
OS type: Linux
Block size=4096 (log=2)
Fragment size=4096 (log=2)
Stride=0 blocks, Stripe width=0 blocks
1024 inodes, 4096 blocks
204 blocks (4.98%) reserved for the super user
First data block=0
1 block group
32768 blocks per group, 32768 fragments per group
1024 inodes per group
Writing inode tables: done
Creating journal (1024 blocks): done
Writing superblocks and filesystem accounting information: done
This filesystem will be automatically checked every 35 mounts or
180 days, whichever comes first. Use tune2fs -c or -i to override.
~ # ←[6nmkdir /efs
mkdir /efs
mkdir: can't create directory '/efs': File exists
~ # ←[6nmount -w -t ext4 /dev/block/mmcblk0p11 /efs
mount -w -t ext4 /dev/block/mmcblk0p11 /efs
~ # ←[6n
Click to expand...
Click to collapse
cz4r3n said:
I'm doing it in recovery mode.Im using Team Win Recovery Project v2.6.0.0.
here is the log after unmounting efs from recovery:
Click to expand...
Click to collapse
Yeah, your /efs dir is still in root directory, but it looks like you got it formated and remounted.
double post (deleted)
ah ok, ya I think so, because it shows factory mode in the screen already.I am expecting that the imei will be converted to 004 but it still shows null.
Anyway, tnx for a big hand.Now then, I'll try to use special box to re-write the original imei.tnx tnx...really appreciate it
cz4r3n said:
ah ok, ya I think so, because it shows factory mode in the screen already.I am expecting that the imei will be converted to 004 but it still shows null.
Anyway, tnx for a big hand.Now then, I'll try to use special box to re-write the original imei.tnx tnx...really appreciate it
Click to expand...
Click to collapse
You got any files in your /efs now?
tys0n said:
You got any files in your /efs now?
Click to expand...
Click to collapse
I used Root Explorer to check the folder and my imei is empty.Unfortunately I have no efs backup.
Any recommendation sir?tnx
cz4r3n said:
I used Root Explorer to check the folder and my imei is empty.Unfortunately I have no efs backup.
Any recommendation sir?tnx
Click to expand...
Click to collapse
Any "FactoryApp" folder in /efs? If so, try
Code:
adb shell
su
echo -n ON > /efs/FactoryApp/factorymode
to get out of factory mode. Then reboot.
Use dialpad and enter *#*#0011#, use menu button and choose "back" , menubutton and "back" again. There you should have an option to rebuild/restore NV. Doubt it will bring back IMEI tho :/
tys0n said:
Any "FactoryApp" folder in /efs? If so, try
Code:
adb shell
su
echo -n ON > /efs/FactoryApp/factorymode
to get out of factory mode. Then reboot.
Use dialpad and enter *#*#0011#, use menu button and choose "back" , menubutton and "back" again. There you should have an option to rebuild/restore NV. Doubt it will bring back IMEI tho :/
Click to expand...
Click to collapse
It's not working, I dialed *#*#0011# and pressed menu or home button (am I right?) there is no option in choosing "back".
cz4r3n said:
It's not working, I dialed *#*#0011# and pressed menu or home button (am I right?) there is no option in choosing "back".
Click to expand...
Click to collapse
After *#*#0011# you should get to factoryapp settings. When you push menubutton you will get a menu where you can choose back.
Btw, are you on stock rom?
tys0n said:
After *#*#0011# you should get to factoryapp settings. When you push menubutton you will get a menu where you can choose back.
Btw, are you on stock rom?
Click to expand...
Click to collapse
Yes I'm on stock rom.Btw, I used this *#0011# and it prompt me in Service Menu and I used below method also but it's not working:
1. Dial *#0011#
2. press Menu then tap BACK
3. press the Menu again the tap KEY INPUT then enter 1, (wait a few seconds) it auto jumped into service menu.
4. press Menu then tap BACK
Your are now in the SERVICE MODE MAIN MENU
Click to expand...
Click to collapse
Service Menu still blank
cz4r3n said:
Yes I'm on stock rom.Btw, I used this *#0011# and it prompt me in Service Menu and I used below method also but it's not working:
Service Menu still blank
Click to expand...
Click to collapse
Not sure why that is :/ Try to reflash stock in odin.
tys0n said:
Not sure why that is :/ Try to reflash stock in odin.
Click to expand...
Click to collapse
I already did.before I'm on 4.1.2 but i downgraded to 4.1.1 to make sure.but still no luck...
I think because of the absence of nv_data.
cz4r3n said:
I already did.before I'm on 4.1.2 but i downgraded to 4.1.1 to make sure.but still no luck...
Click to expand...
Click to collapse
Ok. I'll send you a pm. Let's see if we can work this out.

Merlin /system RW, is this possible ? magisk & adb_root installed

Hi, can't have full access to /system folder with adb
Installed magisk OK
Installed magisk extension module 'adb_root' OK
Code:
adb root
adbd is already running as root
but when I try to delete :
Code:
adb shell rm - f /system/app/CloudService/CloudService.apk
receive Read-only file system
any help ?
Code:
adb shell
mount -o rw,remount /
/dev/block/dm-1 is read-only
Code:
adb disable-verity
verity cannot be disabled/enabled - USER build
tried 'systemrw_1.32' and 'systemrw_1.32_modded' with no success, the installation seems to have been just fine
then flashed the only file I found into /img folder with command :
Code:
fastboot flash super super_fixed.bin
but at the end, even if all is gone fine, the command give always same answer as read-only :
Code:
mount -o rw,remount /
/dev/block/dm-1 is read-only
is there a way to make MERLIN as /system RW ???
matteo555 said:
tried 'systemrw_1.32' and 'systemrw_1.32_modded' with no success, the installation seems to have been just fine
then flashed the only file I found into /img folder with command :
Code:
fastboot flash super super_fixed.bin
but at the end, even if all is gone fine, the command give always same answer as read-only :
Code:
mount -o rw,remount /
/dev/block/dm-1 is read-only
is there a way to make MERLIN as /system RW ???
Click to expand...
Click to collapse
With PixelExperienceRecovery. Mount system then with adb remuont it rw. It is mounted in mnt/system/system.

Categories

Resources