I've flashed shipped rom back but nothing happens only a error message on first boot saying that i don't have /efs folder.
I have an original copy of my efs.img backuped with ktool, but don't know how to restore, since Ktool doesn't work for me when i tried to restore using ktool.
When i type *#1234# i see this:
Version
PDA: I9100UHKI1
PHONE: I9100UHKI1
CSC: I9100ZTOKI1
Build Info: Mon Sep 5 08:49:12 KST 2011
EDIT:
I restored my phone but, it only work with 1 carrier Vivo (Brazil), but when i take a look at Personalization Status:
Network Lock
[off]
Network Subset Lock
[off]
SP Lock
[off]
CP Lock
[off]
My SIM is from TIM and the Original FW from the phone is VIVO, but wasn't Network Lock and don't display this. But it only accept VIVO SIM's to make calls. And data works with my TIM Sim, but doesn't make calls
My IMEI changed to 004999010640000
Please help!!!
What exactely doesn't work?
There's a new v1.10 of kTool ready with tweaked EFS backup/restore that'll be "thrown into the wild" tomorrow or so, with a new build of the kernel it comes from.
Anyways to restore the efs.img "by hand", open a shell (either terminal app or via adb) and type these commands:
Code:
su
umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
reboot
HellcatDroid's code should do the trick and restore your \efs folder.
Good Luck.
HellcatDroid said:
What exactely doesn't work?
There's a new v1.10 of kTool ready with tweaked EFS backup/restore that'll be "thrown into the wild" tomorrow or so, with a new build of the kernel it comes from.
Anyways to restore the efs.img "by hand", open a shell (either terminal app or via adb) and type these commands:
Code:
su
umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
reboot
Click to expand...
Click to collapse
I'll ry this now.
My phone have no IMEI number. Haven't signal. I'm unable to make a call or use internet, only Bluetooth and wifi.
My Baseband is displayed as unknow.
HellcatDroid said:
Code:
su
umount /efs
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
reboot
Click to expand...
Click to collapse
what i do:
Code:
c:\ADB>adb shell
# su
su
# umount /efs
umount /efs
umount: can't umount /efs: Invalid argument
# dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p1 bs=4096
5120+0 records in
5120+0 records out
20971520 bytes (20.0MB) copied, 3.426703 seconds, 5.8MB/s
# reboot
reboot
Don't understant why umount /efs always display: umount: can't umount /efs: Invalid argument
After reboot the folder /efs only show this file: cryptprop_essiv
Inside /efs there's no other file like nv_data.bin and/or nv_data.bin.md5
I can't understand why i'm still no IMEI and no Signal and other infos like BB
When i type *#1234# i see this:
Version
PDA: I9100UHKI1
PHONE: Unknow
CSC: I9100ZTOKI1
Build Info: Mon Sep 5 08:49:12 KST 2011
When it gives you the "invalid argument" error, check if it's mounted in the first place.
Just type a "mount" (w/o any parameters) as command, it'll give a list of all mounted devices, see if /efs is listed there.
HellcatDroid said:
When it gives you the "invalid argument" error, check if it's mounted in the first place.
Just type a "mount" (w/o any parameters) as command, it'll give a list of all mounted devices, see if /efs is listed there.
Click to expand...
Click to collapse
Ok, now my Phone is working but acept only native carrier that have the fw shipped.
My phone only acept carrier Vivo and i can make calls and sens sms with this carrier.
When i try to use TIM, i only can use data, not calls or sms.
I verified and my phone is Sim Unlocked, but don't know whats happening.
I get false IMEI now (0049).
My doubt is the efs.img file is from FW UHKE4 using the update OTA to 2.3.4 and backep up using your's KTool.
If i return to KE4 2.3.3 (since KE4 2.3.4 is only avaible via OTA), can this work? Thanks
marcelotorres said:
If i return to KE4 2.3.3 (since KE4 2.3.4 is only avaible via OTA), can this work? Thanks
Click to expand...
Click to collapse
It's worth a try, but I don't know if it'll really solve the issue.
AFAIK the EFS is not dependand on any specific FW version, but then again one never knows....
Hi,
for now my phone is working but w/ fake IMEI 0049...
Any way to solve this?
My nv_data.bin and nv_data.bin.md5 are w/ fake IMEI too. My last tentative is a efs.img that i have in my PC and Filesonic VHD.
Any app that i can edit this efs.img or a tutorial that help me to do this?
how did ur imei changed?
http://www.cvxcvx.pl/podstrona-0?lang=en
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
Hi! I installed Toolbox Rom, I wanted to change the boot animation (animation I've successfully changed) but I noticed that I have access to the network. I found some instructions for repair, but none helped. whenever I want to copy the backup of the EFS system have their own copies. when I delete the EFS there now appears old EFS system has generated. Can you please somehow fix it? Thank you. (sorry for my English, I do not know good English and translate through Google traslator)
Try this:
in adb shell, i ran
Code:
su
busybox tar zcvf /sdcard/efs/efs-backup.tar.gz /efs
i then downloaded 7-zip, used it to open the .tar file
i deleted the corrupt files;
nv_data.bin
nv_data.bin.md5
i then renamed;
.nv_data.bak > nv_data.bin
.nv_data.bak.md5 > nv_data.bin.md5
after closing and saving the changes, i then went back to adb shell and ran
Code:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/efs-backup.tar.gz -C /
reboot
and voila! i was prompted to select my network provider, check status and all my IMEI, IMEI SV and other info was back to normal!
Thanks to @dickie2007
how to use adb shell? you do not have any instructions on how to proceed step by step? sorry.. i am a lame..
http://forum.xda-developers.com/showthread.php?t=502010
Thank you. I made it through the terminal emulator. network to find me, to be called from the can. IMEI 004999010640000 I and my IMEI SV 01 Does it matter?
sorry I do not understand you
phone is ok, but my imei is: 004999010640000. is this okay?
i dont know your imei, possible it is
i have original IMEI on the box: 358XXX...
repeat the procedure, may help you.
I had the same problem, this link is me helped
http://forum.xda-developers.com/showthread.php?t=1300071
I am trying to restore an efs back up using a command line however when I run it I get /system/bin/sh: suumount: not found. What do I do to rectify this
1Chef said:
I am trying to restore an efs back up using a command line however when I run it I get /system/bin/sh: suumount: not found. What do I do to rectify this
Click to expand...
Click to collapse
Hi,
according to what Sale adviced you:
- every line constitutes a separated command
- it's not "sumount" but "su" [enter], "unmount /efs" [enter] etc.
Regards
Yay thank you so much except now I have a new problem I can't unmount efs as it is busy how do I stop efs
1Chef said:
Yay thank you so much except now I have a new problem I can't unmount efs as it is busy how do I stop efs
Click to expand...
Click to collapse
Ok, try "umount /efs" and see what happens.
Many40 said:
Ok, try "umount /efs" and see what happens.
Click to expand...
Click to collapse
Yes I type in in terminal emulator unmount/efs and the replie is umount: can't umount /efs: device or resource busy I am trying to do it in aroma file manager in recovery but that doesnt work either
This is what happens
oh dude there is a space in between umount and /efs like this
umount /efs
there is a space in between
1Chef said:
This is what happens
Click to expand...
Click to collapse
But from you screenshot I see that you didn't put [space] between "umount" and "/efs" so try again with "umount /efs" with space between.
If i am using a terminal emulator in recovery I won't need to type in adb shell or su I'll just start with umount /efs??? edit I need su
In recovery in terminal I'm getting
~#adb shell
error device not found
~# su
[email protected]:/ # umount efs
umount efs: can't umount efs: invalid argument
busybox tar zxvf /sdcard/efs-backup.tar.gz -C / for this line to work were would i need to save my efs.tar.gz
Ok I'm nearly there ON the last line see above I get tar: invalid tar magic
I"ve given up as I get stuck on the last line and after alot of googling there is no clear answer on how to fix the tar magic problem I can go back to the standard neat rom with not mods and it doesnt appear to lose its IMIE:laugh:
Efs partition on my tablet Samsung GT-P7100 (Tab 10.1v) damaged. Now I have IMEI - Unknown and Baseband - Unknown. I too have a file backup efs_backup.tar.gz, which made early in the program GalaxSimUnlock. I restored my efs partition perfectly using this backup file efs_backup.tar.gz and program GalaxSimUnlock. I see correct IMEI and Baseband values. But after reboot my tablet efs folder is empty again and I have again my IMEI - Unknown and Baseband - Unknown. Can anyone help me with this problem please?
Problem solved. I restored efs partition from backup manually using programs Android Terminal Emulator and BusyBox and my old backup file efs_backup.tar.gz which I put previously in a tablet on sdcard in the GalaxSimUnloclk folder:
su
umount /efs
mke2fs /dev/block/mmcblk0p1
mount -w -t ext4 /dev/block/mmcblk0p1 /efs
busybox tar zxvf /sdcard/GalaxSimUnlock/efs_backup.tar.gz -C
After that I see correct IMEI and Baseband values and it does not get lost anymore after reboot the tablet.
Thanks