Hello i need help.
I have galaxy mega GT i9200, Now i have updated it to 4.4.2 and my efs is deleted i dont know how.
Not phone have no imei and signals.
I followed youtube video about touch not working it worked but signal not coming .
I updated to megafires downloaded from this site.
pls tell me what to do for signal?
Did you have any previous backups of the system?
Did you try flashing the full stock ROM via PC Odin?
Sent from my GT-I9205 using Tapatalk
Yes
AndroidSlave said:
Did you have any previous backups of the system?
Did you try flashing the full stock ROM via PC Odin?
Sent from my GT-I9205 using Tapatalk
Click to expand...
Click to collapse
No i dont have any backup.
I installed ROM from sammobil 4.4.2 after that install touch was not working then i follow youtube video, now touch works but no signals..
An EFS backup is required , I guess!
I've restored a friend's efs, but it's a bit tricky and I don't know if it will work for you.
Note that you need to be rooted.
I guess you can't mount the efs folder while in recovery?
It happens sometimes when one changes ROM, the efs partition gets corrupted and changes from ext4 to swap.
The following works for Mega I9200 running JB, on KK you may have to change all the fields with mmcblk0p10 with whatever mount point efs has on KK.
To find out about it go to dev/block/platform/msm_sdcc.1/by-name and check which number efs has, or type in adb:
su
ls -al /dev/block/platform/msm_sdcc.1/by-name
Now you are ready to repair efs, let's go!
I - Connect you phone through adb, then type:
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.img
mke2fs /dev/block/mmcblk0p10
mkdir /efs
mount -t ext4 /dev/block/mmcblk0p10 /efs
DO NOT REBOOT YOUR PHONE
Now your efs is mounted and don't unmount it.
Check what's inside your efs and remember it for later in case you need to go to step II:
cd /efs
Reboot, your efs is fixed.
If everything works you are done, if it doesn't it means that some files inside the efs folder are missing or corrupted so now proceed to part II to rebuild it.
II - Type the following to recreate efs content (order may change depending the case, and for example if you /efs is empty you don't need the 2 first commands):
rm /efs/FactoryApp/keystr (this will erase keystr)
rm /efs/FactoryApp/factorymode (this will erase factorymode)
mkdir /efs/FactoryApp (this will recreate the FactoryApp folder in case you don't have any it anymore, if you still have it ignore this command)
echo -n ON >> /efs/FactoryApp/keystr (this recreates keystr)
echo -n ON >> /efs/FactoryApp/factorymode (this recreates factorymode)
chown 1000.1000 /efs/FactoryApp/keystr
chown 1000.1000 /efs/FactoryApp/factorymode
chmod 0744 /efs/FactoryApp/keystr
chmod 0744 /efs/FactoryApp/factorymode
reboot
Once everything works make an efs backup:
su
dd if=/dev/block/mmcblk0p10 of=/sdcard/efs.img
To restore efs:
su
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p10
Good luck!
Related
Original question post below...
IF YOU DO NOT HAVE THIS PROBLEM PLEASE BACKUP YOUR /EFS NOW!!! this will save you pain in the future.
One of the things I see over and over in the DEV forum for different ROM's is I flashed this ROM and I do not have any cell service. This seemed common enough that I wanted to put what I found in one place. I am not an expert on this and I will credit the posts and users that helped me. I am actually looking for help in creating a fool proof way to fix a broken /efs, product code (Vibrant is SGH-T959ZKBT), and IMEI.
It seems that the issue here is a corrupt /efs partition/folder (/dev/block/spl3)
You can check this a couple ways first look at your /efs folder in Root Explorer (show hidden files) or via "adb shell ls -a -l /efs". As many of you know this is where you find the nv_data.bin file used for unlocking and stores your product code (needed to be accurate for Kies to work). It is also where the phone stores your IMEI. My good /efs looks like this:
Code:
adb shell ls -a -l /efs
drwxrwxrwx root root 2009-12-31 23:00 .android
-rwx------ radio radio 2097152 2011-05-30 00:44 nv_data.bin
-rw-rw-rw- radio radio 15 2011-05-28 17:46 .imei
drwxrwxrwx radio radio 2010-09-12 03:29 imei
-rwx------ radio radio 2097152 2011-05-07 18:24 .nv_data.bak
-rwx------ radio radio 32 2011-05-07 18:24 .nv_data.bak.md5
-rwx------ radio radio 32 2011-05-30 00:44 nv_data.bin.md5
-rw-rw-rw- radio radio 801 2011-05-07 18:24 nv.log
-rw-rw-rw- radio radio 1 2011-05-07 18:24 .nv_state
-rwx------ radio radio 1048576 2011-05-07 18:24 .nv2.bak
-rwx------ radio radio 32 2011-05-07 18:24 .nv2.bak.md5
The .imei file holds your IMEI in hex format.
You can also check your IMEI by pressing *#06#. You should check that against your IMEI printed on the back of your phone under the battery.
To get your radio working again with correct IMEI you will need a good backup of your /efs folder or partition. You may have a backup and not know it, some ROM porters have added a script to backup your /efs to /sdcard/backup/efs you should look for it. If you are not lucky enough to have one then find a ROM where you see the generic IMEI number (004999010640000) when you press *#06# in the dialer. I used an old Galaxy S 4G port by Eugene373 (he has removed it) to get the generic IMEI.
There are disadvantages to using the generic IMEI as some services will not work (i.e. security on corporate email)
Now that all that is out of the way let's get to the steps for getting you cell service back:
STANDARD DISCLAIMER APPLIES!!! I cannot be responsible for bad things that could happen playing with your /efs folder/partition
Create a copy of your current /efs partition (/dev/block/stl3) with this command: (Thanks Candanga http://forum.xda-developers.com/showthread.php?t=859914)
Code:
# busybox cat /dev/block/stl3 > /sdcard/efs-stl3-backup.img
Mount this file to another location like /testefs:
Code:
# mkdir /testefs
# busybox mount /sdcard/efs-stl3-backup.img /testefs
Now we can fix it up from your /efs backup if you have one:
Copy all the files from your backup into /testefs and overwrite them
Set all the files and directories (except .android should be root) to the owner and group radio:
Code:
# busybox chown 1001:1001 nv_data.bin
# busybox chown 1001:1001 .imei
# busybox chown -R 1001:1001 imei
# busybox chown 1001:1001 .nv_data.bak
# busybox chown 1001:1001 .nv_data.bak.md5
# busybox chown 1001:1001 nv_data.bin.md5
# busybox chown 1001:1001 nv.log
# busybox chown 1001:1001 .nv_state
# busybox chown 1001:1001 .nv2.bak
# busybox chown 1001:1001 .nv2.bak.md5
Set the file permissions as follows:
Code:
# busybox chmod 700 nv_data.bin
# busybox chmod 666 .imei
# busybox chmod 700 .nv_data.bak
# busybox chmod 700 .nv_data.bak.md5
# busybox chmod 700 nv_data.bin.md5
# busybox chmod 666 nv.log
# busybox chmod 666 .nv_state
# busybox chmod 700 .nv2.bak
# busybox chmod 700 .nv2.bak.md5
Unmount /testefs
Code:
# busybox umount /testefs
Now your /sdcard/efs-stl3-backup.img should be all fixed. If you have the generic IMEI you can try editing the .imei file with a hex editor of your choice and change it to your IMEI it is just the hex representation of your IMEI and nothing else in the file. (I did not test this as I had the files backed up.
Next we are going to create an odin tar to flash to the phone: (Thanks cellgeek http://forum.xda-developers.com/showpost.php?p=10622481&postcount=12)
Code:
# cd /sdcard/
# busybox cat efs-stl3-backup.img > /sdcard/efs.rfs (this is the key step!!)
# tar -cf efs.tar efs.rfs
# exit
Now your back at your PC. Do the following step to get the .tar file off your phone.
Code:
c:\Android\tools> adb pull /sdcard/efs.tar
This tar file can be put in the PDA section of Odin and flashed in download mode.
If all worked you should not have a repaired /efs that should work on most/all ROMs.
What I did not cover here was how to fix the Product code but this post from bames explains how to do that for a Captivate and should work the same for our Vibrants. Difference is our Product Code is SGH-T959ZKBT and you may need to be on Stock JI6 to do the steps in the post.
http://forum.xda-developers.com/showthread.php?t=881162
I hope this helps some and feel free to let me know if I missed something or if it does not work or if there are easier ways.
Original Question:
philow said:
I have been flashing ROMs on my Vibrant for a while and all has worked OK. I never really bothered to look at my IMEI number but I am sure somewhere along the line it changed and probably my Product Code. I just decided to go back to stock and clean up the phone a bit before I continue now that CM7 is officially supported
I Odin back to JFD with the 512.pit and partition. After the reboot the phone will only stay on for a short time then reboot or turn off and I have no signal.
I then Odin to JI6 w/o repartitioning and it will boot and is stable. I root the phone then I look in the /efs folder and all that is there is a .android folder. I have no signal at this point. I can copy a backup of my /efs or just mount as r/w with root explorer and I will get the nv_data files that I need and get signal. If I copy my backup first then I will also have the correct IMEI for my phone. If I do not restore from my backup my IMEI is null/null.
My problem is that if I reboot my phone I again have no files in /efs just the .android folder.
I have tried to change permissions and ownership on the files to radio (1001) but no matter what I do the files disappear.
Anyone else having this problem? Does anyone have a solution?
Thanks
Click to expand...
Click to collapse
what rom did you came from?
Sent from my SGH-T959 using XDA App
iynfynity said:
what rom did you came from?
Click to expand...
Click to collapse
It was my Son's phone so I am not sure what all he has had on it or when it started having a problem but the latest was the 5/7/2011 MIUI rom.
MIUI worked fine on reboot as far as signal is concerned. Not sure what IMEI it had.
Thnaks
You still have your eds backup right?
http://forum.xda-developers.com/showthread.php?t=859914
It's a little complicated but I hope you fix it. Or if not, try to ask tmobile.
Sent from my SGH-T959 using XDA App
iynfynity said:
You still have your eds backup right?
http://forum.xda-developers.com/showthread.php?t=859914
It's a little complicated but I hope you fix it. Or if not, try to ask tmobile.
Click to expand...
Click to collapse
I have tried that post and this one from the Captivate forum.
http://forum.xda-developers.com/showthread.php?t=881162
And it still deletes the files when I reboot. I have actually contacted Tmobile and they have sent a new phone but I am trying to see what has happened in case it happens again.
Also, I just flashed an old GalaxyS4G ROM my son had on it and it seems to work OK as well but with a generic IMEI and the 4G Product code.
strange!!!
Thanks for your quick reply
Added possible Solve
I added what I did to solve my issue in the OP! Hope it helps someone!
Thanks
No EFS backup and EFS got currupted| How to recover Vibrant
philow said:
Original question post below...
Code:
# mkdir /testefs
# busybox mount /sdcard/efs-stl3-backup.img /testefs
Now we can fix it up from your /efs backup if you have one:
Original Question:
Click to expand...
Click to collapse
How to repair IMEI and get back signal If you dont have efs back up or NV_data.bin backup?
I am in big trouble.
Flash to stock using ODIN and it should be fixed, check your IMEI with the one in the back of your phone.
The easiest way to do it is using this http://forum.xda-developers.com/showthread.php?t=954509, as it comes with the pit and pda files you need. (Many thanks to bay_wofl)
how if I don't have the stl3, in fact my /dev/block is empty !!!
do I still have chance to restore my phone with only the efs backup ?
NO Signal ** no /efs folder
I have a similar problem on my gooapple phone.
I have no /efs folder anywhere but my IMEI address after struggling appears. I modifyed the /data/nvram/md/NVRAM/NVD_IMEI MP0B_001 file without any luck.
What finally did the trick was executing :
adb shell
su
echo 'AT +EGMR=1,7,"IMEI_1"'> /dev/pttycmd1
echo 'AT +EGMR=1,10,"IMEI_2"'> /dev/pttycmd1
I still have the No Signal problem.
can this help me?
has anybody found a solution to this issue?
regards,
Sergio G
serginhog said:
I have a similar problem on my gooapple phone.
I have no /efs folder anywhere but my IMEI address after struggling appears. I modifyed the /data/nvram/md/NVRAM/NVD_IMEI MP0B_001 file without any luck.
What finally did the trick was executing :
adb shell
su
echo 'AT +EGMR=1,7,"IMEI_1"'> /dev/pttycmd1
echo 'AT +EGMR=1,10,"IMEI_2"'> /dev/pttycmd1
I still have the No Signal problem.
can this help me?
has anybody found a solution to this issue?
regards,
Sergio G
Click to expand...
Click to collapse
Did you find a solution? I just received my goophone i5 and have no service
You almost made me cry !!! Followed about 90% of all the guides to restore my backed up efs. Went from no signal to bootloop and back. Spend 6 days trying to fix my phone and you were my last resort. If your guide wouldn't work I would've given up. I did push the Thanks button but wanted to say thank you too
[FIXED] Urgent help, how to restore \efs to get lost IMEI ? "Input/output error"
Greeting,
Tonight I flashed a custom kernel to my phone, just\ lost the Singal and my phone show no sim card inserted!.
anyway, i figure it out that... the IMEI lost.
in \efs there's no nv_data.bin file!!
So i went to restore the \efs.
but something not right here!
Hope someone can help here.
i tried these commands but no chance tel now!.
here to restore nv_data.bin
Code:
su
# cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/nv_data.bin
[COLOR="red"]cp: can't stat '/efs/nv_data.bin': Input/output error[/COLOR]
and here to restore \efs
Code:
# busybox tar zxvf /sdcard/efs/efs-backup.tar.gz -C /
busybox tar zxvf /sdcard/efs/efs-backup.tar.gz -C /
efs/
efs/cryptprop_rebootMode
[COLOR="Red"]tar: can't remove old file efs/cryptprop_rebootMode: Read-only file system[/COLOR]
#
tried to flash back to many FW but no chance,
now i'm in KF1 rooted.
tried root explorer to copy the files but \efs is read only can can't not be changed!.
Hi.
Sounds like your /efs is mounted read-only, try re-mounting for rw access:
Code:
su
mount -o rw,remount /dev/block/mmcblk0p1 /efs
(either via adb or terminal app running on the phone itself)
and then try to copy the files back again.
If it doesn't want to work from a running system, you can also try it in recovery mode (given you have a recovery that allows you a root shell) - you have to use adb in that case ("adb shell", get a root shell ("rootsh" when you're using CF-Root) and then the above).
Maybe the actual FS on the EFS partition is corrupted, so as a very last resort maybe formatting it and then restoring the full backup might work.
here's what i got
Code:
su
# mount -o rw,remount /dev/block/mmcblk0p1 /efs
mount -o rw,remount /dev/block/mmcblk0p1 /efs
# cp /sdcard/nv_data.bin /efs/nv_data.bin
cp /sdcard/nv_data.bin /efs/nv_data.bin
cp: can't stat '/efs/nv_data.bin': Input/output error
will trey via recovery,
but,, how to format it ?
It's one of the mkfs commands, but at first glance I could only find the ext2 version of it - /efs is (like everything else of the internal partitions on the SGS2) ext4....
Maybe someone else can shed some light if either mkfs.ext2 can be used, or how else to format it ext4.
Also, you should use tar to write back your backup, to keep the proper permissions.
Now i see no nv_data.bin in the /efs
and I couldn't copy the file, it's read only, even with the mount!
I think this is the only solution for me.
Some have restored efs/IMEI by flashing a stock firmware .
jje
Ah, also found this command:
Code:
make_ext4fs
but I have no idea about its parameters....
Yeah, try flashing a stock FW, maybe one of the "_user_low" ones, AFAIK they clean out a bit more stuff....
I got this
Code:
su
# ls
ls
acct fota.rc res
app-cache init sbin
cache init.goldfish.rc sdcard
config init.rc sys
d init.smdkc210.rc system
data init_kernel_only.rc tmp
dbdata lib ueventd.goldfish.rc
default.prop lpm.rc ueventd.rc
dev mnt ueventd.smdkc210.rc
efs proc vendor
etc recovery.rc
# cd efs
cd efs
# ls
ls
[COLOR="Red"]ls: ./nv_data.bin: I/O error
ls: ./nv.log: I/O error
ls: ./nv_data.bin.md5: I/O error
ls: ./dmp: I/O error[/COLOR]
cryptprop_applied_result cryptprop_securewipedata
cryptprop_onetimeboot edk_p
cryptprop_persist.sys.language imei
cryptprop_persist.sys.timezone redata.bin
cryptprop_rebootMode
#
hope this help ?
FIXED...
here's the full Solution http://forum.xda-developers.com/showthread.php?p=15666725#post15666725
Hello, long story short:
My Android-ID was different (according to titanium backup) so I decided to restore my efs folder because I've read that the ID is stored in there.. I made it with mobile terminal but it didnt work and from there my Phone rebootet and Bootloop
-> I flashed stock (didnt work)
-> I flashed stock 3 parts with .pit and re-partitioned (still didnt work)
-> in stock recovery the line /efs cant mount(invalid argument)
So then I followed this Tutorial to mount my /efs:
[Q] Failed to mount /efs (Invalide argument) and not Start
-> my phone booted but was in factory mode and my IMEI was 0049.. and my SN was 0000..
[I made a efs-backup long ago with Efs Pro 1.4.7 (a .tar file and .img file)]
-> because no program worked I restored the efs by deleting the efs folder from my phone and it generated a new one
- then I deleted everything in the folder from my phone and copied everything from my backup and put it in there -> reboot
Now my IMEI is correct and my Serial too but i still dont have signal (with a working sim)
So now what can and should i do next to fix it?
((Im from germany and I have a International GT-I9300, my baseband is ...EMG4))
Thanks
*EDIT: solved my problem with
I'm stuck in factorymode, is this related?
Yes, factorymode is caused by corrupt efs. It is possible to fix it with root and a terminal emulator.
Firstly try these commands (case sensitive)
Code:
su
echo -n ON >> /efs/FactoryApp/factorymode
If they fail, use the more detailed commands:
Code:
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
This should hopefully return you to user mode. If not, the last thing you can try, which reportedly works is to delete /efs/FactoryApp/ folder, then factory reset from recovery. This *should* regenerate the folder. Your factory mode will still need "echo -n ON >> /efs/FactoryApp/factorymode" doing though, which can be done as described above or opening the file in a text editor and changing the content of the file to "ON"
Click to expand...
Click to collapse
from: http://forum.xda-developers.com/showthread.php?t=2393289
Hi,
I have the Galaxy Player 4.0 YP-G1
I followed the description on this thread :
http://forum.xda-developers.com/showthread.php?t=2386992
But unfortunatly, after flash, my efs directory was empty (only "lost+found" directory inside)
I search in the forum and find that it was better to flash from 2.3.6 to CM9 and after CM10.2, so too late for me !!
I found also that I should simply copy my backup of efs directory to /efs so I do this :
adb shell
su
umount /efs
mount -o remount,rw rootfs /
cd /sdcard/backup/efs
cp -r * /efs
dd if=/sdcard/backup/efs.rfs of=/dev/block/mmcblk0p1
mount -o remount,ro rootfs /
The files were successfully copied but when I reboot, the directory /efs was again empty !!!
Of course, I make some backup :
Nandroid backup of my 2.3.6 before flash to CM10.2
backup of efs directory in /sdcard/backup/efs/ (automatically when I flash CM10.2)
backup of efs directory in a file efs.rfs (when I was on 2.3.6)
What do you recommand me to recover my efs directory ?
Restore my nandroid backup 2.3.6
Re-flash to 2.3.6 with Odin according to this thread (is my efs directory will be regenerated ?):
http://forum.xda-developers.com/showthread.php?t=1531850
Or other things ?
Thank you very much for your precious help !
I like this forum, very helpful
I moved my request here :
http://forum.xda-developers.com/showpost.php?p=50035359&postcount=231
Thanks for your help.
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)
then i flash cwm recovery but in that recovery i can't make a backup of efs folder.
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)
Backup / Restore EFS Partition
@Kevin95ME
FYI: EFS partition is an encrypted one.
Assumed the path to EFS is /dev/block/mmcblk0p3. Note: This may not be correct path. It's on you to find the correct path.
You can backup EFS to internal storage running command
Code:
dd if=/dev/block/mmcblk0p3 of=/storage/sdcard/efs.img bs=4096
or you can backup EFS to external storage running command
Code:
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096
in a Terminal Window what creates file efs.img
To restore the EFS partition you run either command
Code:
dd if=/storage/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096
or command
Code:
dd if=/storage/extSdCard/efs.img of=/dev/block/mmcblk0p3 bs=4096
in a Terminal Window what depends where you saved it.
jwoegerbauer said:
@Kevin95ME
FYI: EFS partition is an encrypted one.
Assumed the path to EFS is /dev/block/mmcblk0p3. Note: This may not be correct path. It's on you to find the correct path.
You can backup EFS to internal storage running command
Code:
dd if=/dev/block/mmcblk0p3 of=/storage/sdcard/efs.img bs=4096
or you can backup EFS to external storage running command
Code:
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096
in a Terminal Window what creates file efs.img
To restore the EFS partition you run either command
Code:
dd if=/storage/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096
or command
Code:
dd if=/storage/extSdCard/efs.img of=/dev/block/mmcblk0p3 bs=4096
in a Terminal Window what depends where you saved it.
Click to expand...
Click to collapse
Hi thanks for answer,
excuse me for the newbie question, but, do i run terminal window on the TWRP recovery or adb shell?
Kevin95ME said:
Hi thanks for answer,
excuse me for the newbie question, but, do i run terminal window on the TWRP recovery or adb shell?
Click to expand...
Click to collapse
Terminal Emulator is an Android app you can get off Google Play Store.
jwoegerbauer said:
Terminal Emulator is an Android app you can get off Google Play Store.
Click to expand...
Click to collapse
ok lets me try. later i tell you the result. thanks
jwoegerbauer said:
Terminal Emulator is an Android app you can get off Google Play Store.
Click to expand...
Click to collapse
my friend thanks for you support i solve the problem doing this things in this order
first
i follow your step doing backup of my efs folder , but i modify the command
dd if=/dev/block/mmcblk0p3 of=/storage/extSdCard/efs.img bs=4096 ( your command)
dd if=/dev/block/mmcblk0p3 of=/sdcard1/efs.img bs=4096 (then i wrote this) ( with your command the terminal told me " no exist such file or directory")
(sdcard1 is ExtSdCard in S6792L)
then i save that efs file in my pc
second
i use the information on this post https://forum.xda-developers.com/showthread.php?t=2204960
this line of command
su
mke2fs /dev/block/mmcblk0p3
mount -w -t ext4 /dev/block/mmcblk0p3
reboot
third
i restore efs folder following your step, but modifying the command
dd if=/sdcard1/efs.img of=/dev/block/mmcblk0p3 bs=4096
the device is now on and pass the boot logo, right now i am deactivating the factory mode because show a yellow box showing ROM information.
i will use this information for deactivate that https://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
Remove factory mode:
There are different methods that we can use to remove factory mode
In my case
1. Installed custom ROM to get root access
2. Instaled kTool
3. Copy the backup of my efs into sdcard (you can use .img or tar file)
4. Open kTool and restore the efs
5. Reboot the phone
* This method is the easiest and safest method because when you are getting the efs mount error there is a chance of loosing your IMEI and some other files, in that situation the following methods will not work.
OR
1. Root your phone (Either root manually or install a custom ROM)
2. Install ES File Explorer
3. Open ES File Explorer and turn on Root Explorer
4. Navigate to /efs folder
5. Open factorymode as txt in ES Note Editor
6. Change it from OFF to ON and save
7. Reboot your phone
OR
1. Root your phone (Either root manually or install a custom ROM)
2. Install Terminal Emulator
3. Run the following commands
Code:
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
thnaks so much for your support.
excuse formy bad english ,i do my best for improve it.
by the way i do all in the Terminal Command of the TWRP recovery.