Hello, my galaxy S is running on generic imei. Currently i am on darkyrom
1. I have efs folder backup,everytime i boot my phone i have to copy that backuped efs folder to the phones folder, and when i do this i get network signals. Once i reboot the phone i have to do all that again. Any solution to get away with doing it everytime?
2. If i get a efs folder of a working imei phone,can i use that to fix mine imei?
3. While flashing few roms, i get this error in cwm
Assert failed 'is_mounted' (efs) .
Why is that?
if you try to flash another NV_data on your SGS you will end up with either No IMEI number or The generic one 004999 bla bla
To get your original back you need to restore the contents of the backed up efs to the efs on the phone.
If that fails, you will need to flash back to an older firmware, froyo worked for me, Some people say eclair. But try and see for yourself.
I have tried to change the IMEI many many times, it just resulted in the generic one. I cant find any help regarding it as it is illegal and no one will comment.
I did try all the methods but failed. Now question is that does having generic imei affect while installing roms? And why do i need to copy paste the efs folder everytime i boot the device :-\
Oh no you shouldnt need to do this on every boot, something is wrong there. Maybe the backup efs is also corrupt.
The generic IMEI can cause apps to not work properly, Market apps to not download, and signal / call / sms issues.
I have generic IMEI on one of my SGS's and its been fine for weeks.
Delete the current nv_data.bin / nv_data.bin.md5 / nv_data.bak and then reboot.
Related
Unlike other cases posted previously...
All files in efs were deleted, including all hidden .bak files
Now, kies displayed my phone have a product code of XXXXXXXXX and a fake IMEI...
Is it possible to restore the nv_data.bin and other files??
Please help! Thanks....
I have the same problem, is there a solution for that?? Please answer!
Did you install sgs toolbox and used it's check product code function before you deleted your efs? If yes, there is still a chance. If no, there are currently no public fix available yet.
Sent from my GT-I9000 using XDA App
We are on the same boat, as what francis posted. No public fix yet but pretty sure there will be.. its just a matter of time.
the same thing happened to me yesterday when i flashed Cyanogenmod 7, got fake imei but everything worked just fine (call, data, market).
today i deleted everything from efs folder using Root Explorer then installed i9000XWJS5 then, surprise, i got my original imei back.
do not know how and do not know if it will work on you but it worth a try
The same thing happened to me.
If I dial *#06# no imei appears.
In order to use the phone everytime I boot up I have to give r/w permission to system folder. Otherwise it doesn't recognize the sim card.
It seems to me that that the device is not anymore able to recognize itself.
If I try to install CM or other AOSP rom I have status 7 error.
In Rom manager I have a window where I should select wich kind of device it is.
In fastweb installer there is a list of devices and I have to choose wich of them I am using.
I know that there is nothing to do with warranty. But is it possible to go back to a stage where it is possible to install AOSP rom?
Thanks
don't know it may work or not, but some custom roms make a backup of the efs folder on sdcard under /sdcard/backup/efs or /sdcard/backup/efs-XXX
(XXX= some numbers). you can try to restore it from there.
again don't know for sure...
Normallary Not
hellboy2703 said:
don't know it may work or not, but some custom roms make a backup of the efs folder on sdcard under /sdcard/backup/efs or /sdcard/backup/efs-XXX
(XXX= some numbers). you can try to restore it from there.
again don't know for sure...
Click to expand...
Click to collapse
Thanks.
I have checked, but there is no backup.
I know the only one to blame it's me.
Do you think that there is anyway to make possible installing AOSP rom?
Watch out! That guy below me is spam! (User @yankee86)
Hey folks. I'm having a hell of a time here - I noticed that after the (fresh) installation of cm7 and updating to the latest nightly, my imei changed to 004999010640000.
Now, I have two backups, and went ahead and copied nv_data.bin, from when I originally got the phone, to /efs and changed the permissions to 1001:1001. After a reboot, imei is still 004999010640000.
I went ahead and flashed back to JL2, at which point my iemi was showing correctly, so I flashed speedmod, flashed cm7-kernel, rebooted, installed the cm7 update, and now my iemi is back to 004999010640000.
It doesn't seem to have any negative effects, my phone works as it usually does, but it is driving me nuts why my iemi is buggered up under cm7, and why restoring the original doesn't fix it. Is this a cm7 issue?
TIA
CM7 copies the efs folder and reads it from somewhere else. That's why restoring it to original place didn't do anything. Don't know why it changed it.
Yeah I started poking around the initial flash zip and noticed that all efsbackup.sh does it copy the contents of /efs to /sdcard/backup/efs.
I figured that they were keeping /efs because of
Code:
/dev/block/mtdblock4 on /efs type yaffs2 (rw,relatime)
showing up when viewing mounts...
Still having the problem... im hoping someone here can offer up some suggestions.
Sent from my GT-I9000 using XDA App
EFS backup post somewhere on the forum its a topic thats been well covered.
Due to flashing wiping efs .
One post is .
http://forum.xda-developers.com/showthread.php?t=881162
jje
JJEgan said:
EFS backup post somewhere on the forum its a topic thats been well covered.
Due to flashing wiping efs .
One post is .
http://forum.xda-developers.com/showthread.php?t=881162
jje
Click to expand...
Click to collapse
Thanks for the link, but it doesn't relate to my problem. The edits to nv_data.bin in that thread relate to changing the product code back to a proper AT&T product code on the captivate. I have a BMC i9000m, and an original (and proper) nv_data.bin from my stock phone when purchased.
The issue is when I copy my proper nv_data.bin to /efs, set proper permissions and reboot, it reverts back to a buggered IEMI according to settings -> status in CM7. I'm looking to find how how exactly CM7 handles /efs, and if it is CM7 specifically that is overwriting my nv_data.bin or if something else is at work.
Ah, finally figured it out. After seeing what nv.log was saying and thanks to zacharias over on the cm forums for tipping me off that just restoring nv_data might not work without everything else in /efs. I transferred my efs backup from windows to my ubuntu vm, set the permissions and made a tarball. Transferred that to my device, extracted the tarball, rebooted and poof, it worked. As this was a complete /efs backup and not just nv_data.bin, I'm guessing there was another file that the phone needed, despite what some of the guides say.
I still wish I knew what caused the phone to reject the nv_data.bin (as per nv.log)... I did delete the nv_data.bin.md5 because I read elsewhere that the phone would simply rebuild a new hash on boot, but it obviously didn't work. I wonder if it had something to do with that.
Oh well, it works now... thanks everyone!
Hey, I got some problems. Posted in another forum, but it's very urgent so I post it here to. Just quoting what I previously posted.
Hey, flashed the JVS modem on top of the Chameleon Final. Didn't get any signal and the baseband version in settings stated "unknown". Tried another modem, JVO and flashed back to Chameleon modem, still not fixed. Also tried to wipe everything and install rom again... did not help either. Odin didn't report any errors whatsoever.
Desperate for some help her guys!
Click to expand...
Click to collapse
Got reply that my IMEI was screwed, and replied:
[quote author=bahafeld link=topic=1931.msg13081#msg13081 date=1316107492]
Okey, I have backup of my original EFS folder. Isn't it there the IMEI is saved? can I just copy it over again with Root Explorer?
Please help me out here. All the guides I've found have the EFS saved in a .tar format. However I just backed up the EFS folder with root explorer. Anyone know I can recover my EFS, tried just copying it back, but that did not work.
Its kinda urgent!
[/quote]
So I hope you guys at XDA can help me a bit faster.
Thx
bahafeld
if you have a .tar version of your EFS. Unzip it. Copy all the contents of it, And paste them to the /EFS on the phone. Making sure they overwrite the current contents.
Once that has done, Restart the phone without backing out of root explorer (or what ever app you are using to copy/paste these files).
If that fails, Repeat the above step but ONLY copy / paste the NV_data.bin & NV_data.bin.md5
And finally if that fails. Backup all your stuff using Titanium Backup (or similar) And re flash a stock Froyo ROM. Maybe older, its upto you.
That will Definitely restore the IMEI, Then re-root and go back to whatever ROM you wish.
Good luck.
Need some help here, hopefully without having to go back to JF6 (that is a little scary at this point). Was pretty happy with CM9 and updated through most nightlies. Just today I upgraded to CM10. All seemed to be working well except that I received a warning of invalid IMEI. I pushed through it and had the phone working on CM10 (with low memory /data isses - that could later be rectfied) then realized that the IMEI issue would mean AT&T would likely shut my phone down. The invalid IMEI is generic and has been flagged as invalid. I also ran into a few issues where I could not download from the Play Market App and think this was the reason.
I nandroid backed up CM10 and restored CM9 but still no dice. As I learned later it doesn't touch the efs folder which somehow the CM10 upgrade modified or had the effect to change it. Uuughh. many others were having the issue.
Anyway, I have verified that there are no /efs backups anywhere on my phone or SC or emmc cards. There are no backups within the efs folder. So, I am hosed. Any way to edit the nv_data.bin file a la this process for either CM9 or CM10?
http://forum.xda-developers.com/showthread.php?t=881162&highlight=restore+imei
This seems to be the only way I can see that would get me back with no IMEI EFS backup. But, going back to Android 2.1 Eclair or 2.3.5 Gingerbread would be a time killer and have to go through rerouting (?), upgrading, etc.
Any thoughts or direction?
tonyo123 said:
Need some help here, hopefully without having to go back to JF6 (that is a little scary at this point). Was pretty happy with CM9 and updated through most nightlies. Just tpday I upgraded to CM10. All seemed to be working well except that I received a warming of invalid IMEI. I pushed through it and had the phone working well then realized that this is an issue where AT&T will likely shut my phone down. The invalid IMEI is generic and has been flagged as invalid. I've also run into a few issues where I cannot download from the Play Market App although not sure if this is the reason.
I backed up jCM10 and restored (CEM NANDROID) CM9 but still no dice. As I learned it doesn;t tough the efs folder which somehow the CM10 upgrade modified or had the effect to change it - although I understadn the ROM is not supposed to do this but I see many having the issue.
Anyway, I have verified that there are no efs backups anywhere on my phone or SC or emmc cards. There are no backups within the efs folder. So, I am hosed. Any way to edit the nv_data.bin file a la this process for either CM9 or CM10:
http://forum.xda-developers.com/showthread.php?t=881162&highlight=restore+imei
This seems to be the only way I can see that would get me back with no IMEI EFS backup. But, going back to Android 2.1 Eclair would be a killer and have to go through rerouting (?), upgrading, etc.
Any thoughts or direction?
Click to expand...
Click to collapse
Go Stock with rooted KK4 and flash what ever rom you want after.
http://forum.xda-developers.com/showthread.php?t=1358180
Okay
silvertag said:
Go Stock with rooted KK4 and flash what ever rom you want after.
http://forum.xda-developers.com/showthread.php?t=1358180
Click to expand...
Click to collapse
All right it was a long painful night and day. Found and downloaded Heimdall One Click .jar with UCKK4 GB. Ran it and it restored the correct IMEI. It was unrooted and stock.
Then what was previously easy became an adventure to root and and load a kernel with CWM. I must have bricked the phone 10 times havimg to redo the Heimdall to Gingerbread 2.3.5 numerous times including reloading samsung pc drivers. Eventually with Odin, I found the right sequence using Corn Kernel for UCKK4 703 injected with CWM (not 705 or 706 versions which kept failing) which allowed me to get CWM loaded onto the phone.
I still could not restore my CM9 nandroid backups as the /data restore kept failing having to redo things from scratch. So, then I copied the latest CM9 nightly .zip onto the internal SD then loaded it from the Corn-CWM restore. CM9 booted and things were better but phone nad none of the settings and things still not right. Then rebooted into CWM recovery and restored the last CM9 nandroid backup. Now things worked and everything was back to normal with the correct IMEI.
Man that was a long stressing and scary day...
Made multiple copied of EFS for the future.
Will hold off on CM10 until the /efs issue is resolved as well as the memory management is better understood (while on CM10 I immediately ran into /data out of memory problems (I know I needed to move things to SD but never got around to it once the IMEI issue came up).
So, all is back to CM9 and finally working fine
odin to stock, then you will get imei back, backup efs folder, and flash back to cm10.
I have the same problem, but i'm om Rogers and 5 days now and no problems yet. I have a backup of my efs folder can I just copy paste?
master2828 said:
I have the same problem, but i'm om Rogers and 5 days now and no problems yet. I have a backup of my efs folder can I just copy paste?
Click to expand...
Click to collapse
Yes just make sure you set the correct permissions on the files. BTW You won't have a problem on Rogers. Canadian providers have all their black listed (lost/stolen) imei separated. They don't share it so a black listed imei on Rogers will work on Bell or Telus and vice versa. Only thing is that your phone can no longer be tracked by imei in case of emergency since its not the correct information but E911 will still locate you via GPS if you ever place a call.
silvertag said:
Yes just make sure you set the correct permissions on the files. BTW You won't have a problem on Rogers. Canadian providers have all their black listed (lost/stolen) imei separated. They don't share it so a black listed imei on Rogers will work on Bell or Telus and vice versa. Only thing is that your phone can no longer be tracked by imei in case of emergency since its not the correct information but E911 will still locate you via GPS if you ever place a call.
Click to expand...
Click to collapse
Cool, thanks, what are the correct permissions? if i run fix permissions from kernel will that do the trick?
master2828 said:
Cool, thanks, what are the correct permissions? if i run fix permissions from kernel will that do the trick?
Click to expand...
Click to collapse
That should do
EDIT: Checked my settings on nv_data.bin and its 777 (everything checked in RootExplorer)
silvertag said:
That should do
EDIT: Checked my settings on nv_data.bin and its 777 (everything checked in RootExplorer)
Click to expand...
Click to collapse
So where exactly do i put the efs folder? I looked on the root of my phone and i dont see a efs folder currently, i tried to put the backup i have there but it didnt work still go the error. i dont even know how i got the backup i have actually lol, i just copied my whole phone contents to my pc before i wiped just in case and there is an folder /backup/efs...lucky i guess
master2828 said:
So where exactly do i put the efs folder? I looked on the root of my phone and i dont see a efs folder currently, i tried to put the backup i have there but it didnt work still go the error. i dont even know how i got the backup i have actually lol, i just copied my whole phone contents to my pc before i wiped just in case and there is an folder /backup/efs...lucky i guess
Click to expand...
Click to collapse
It sounds like you have the backup that is sometimes made in the /sdcard (or /mnt/sdcard) folder, which is the internal storage you see when it's connected to your machine.
To see the /efs folder (assuming it exists), you would need to use either shell commands from inside ADB, or a root file explorer. If it's not there, you should just be able to dump the contents of that backup folder to a directory called /efs and go from there.
Hello guys, a friend of mine just gave me his phone because "it has got a problem" he said. He just flashed a ROM from CMW, but he noticed that there was no service. the problem is that, if I dial *#06# there is the CORRECT IMEI, but if I search for the EFS folder, there is no trace of it. how is this possible? the IMEI shown in the phone also corresponds to the IMEI wrote on the back of the phone... so it's clearly correct. how this could be possible? I tried adding manually the EFS folder using root explorer (and mounting it as R/W), but after the reboot the phone automatically delete the folder I created.. any idea? thank you!
blak24 said:
Hello guys, a friend of mine just gave me his phone because "it has got a problem" he said. He just flashed a ROM from CMW, but he noticed that there was no service. the problem is that, if I dial *#06# there is the CORRECT IMEI, but if I search for the EFS folder, there is no trace of it. how is this possible? the IMEI shown in the phone also corresponds to the IMEI wrote on the back of the phone... so it's clearly correct. how this could be possible? I tried adding manually the EFS folder using root explorer (and mounting it as R/W), but after the reboot the phone automatically delete the folder I created.. any idea? thank you!
Click to expand...
Click to collapse
Look in My Android Solutions
But First powerdown, pull out Battery, SIM CARD, and EXT.SD card, press power button for a minute, than powerup without SIM and Ext.SD Card, after flashing and reboot , insert them back
Tips before Flashing:-
Backup all your important files, contacts, SMS, game data, images etc to PC or Ext SD card. or make Nanadroid Backup If you have CWM
Backup your EFS Folder to PC or Ext SD card
Enable USB Debugging on Phone. Touch menu> Settings> Applications> Development>
Charge your battery to more than 50% before you attempt any sort of flashing.
Disable Samsung KIES when using Odin. Kill Kies.exe, KiesTrayAgent.exe, & KiesPDLR.exe using Task Manager on PC
Use only ROM and solution for your model and Wipe x3
nothing worked for me.. I tried to flash an earlier version of android, gingerbread, and the EFS folder was recreated but was incomplete. there were no "imei" folder into efs folder, and also there were no nv_core.back files, ecc... despite this, the IMEI number was shown correctly in the phone, but no signal/data... :S
blak24 said:
nothing worked for me.. I tried to flash an earlier version of android, gingerbread, and the EFS folder was recreated but was incomplete. there were no "imei" folder into efs folder, and also there were no nv_core.back files, ecc... despite this, the IMEI number was shown correctly in the phone, but no signal/data... :S
Click to expand...
Click to collapse
Have you tried restoring the original firmware and checked? If not you should do that.
http://forum.xda-developers.com/showthread.php?t=1102881
:fingers-crossed:
no network service issue with jelly bean
I have a similar issue here.
First of all I flashed usin this guide:
thehelptimes.com/install-jelly-bean-on-galaxy-s-i9000-how-to-official-rom-android-4-1
provider is congstar (T-Mobile reseller)
*#06# gives me the correct IMEI
/efs folder exist
/efs/imei too
I tried killing the nv_data.bin in order to have the phone recreate it. That happened, now the phone asked for a pin at reboot but the pin doesn´t get
accepted. It also doesn´t get locked after 3 attempts. It just doesn´t get accepted.
Then I noticed that the rights of the nv_data.bin are different than the other files. I changed that but it got changed back after reboot and the pin still isn´t accepted.
I have no idea whats wrong. Next attempt back to gingerbread :-/
EMnEL said:
Have you tried restoring the original firmware and checked? If not you should do that.
http://forum.xda-developers.com/showthread.php?t=1102881
:fingers-crossed:
Click to expand...
Click to collapse
yep I tried restoring gingerbread, and, as I said, the phone created the efs folder, but it was incomplete... there were no IMEI folder, other folders were missing, and there were NO nv_data.bin files. I tried reflashing jelly bean and the efs folder was, again, completely missing...
Alright, I am gone back to XJVP but this wasn´t much help.
No signal either.
IMEI still shown by dialing *#06#
as of forum.xda-developers.com/showpost.php?p=26827676&postcount=4512
I need to get into root to kill the efs folder.
So I am back to XXJVU (gingerbread) now to get it rooted.
Before root there is still no network yet but I still can display the IMEI 3547.... (which is listed in the settings too).
Alright now I am going to root it. Hope this helps somehow.
I have the strong feeling that this phone ends up as a mp3/mp4 player
UPDATE....
- Alright, according to this I better not kill the efs by ODIN ? I didn´t yet. forum.xda-developers.com/showthread.php?t=1114958
- I checked the efs folder and noticed it is pretty much holding the same content as
in an efs offered for download "i9000 358001043596739 efs.rar" at 199.91.153.60/pa6q9c9bboog/eyyse638dh3kncn/i9000++358001043596739+efs.rar
So it looks pretty much like it should, I can see my perfect IMEI but it still doesn´t work. I am lost. No clue.
Back in my I9003 the SIM just works perfect so it is obviously not an issue of the SIM
UPDATE 2...
- flashed back to XXJP1 Froyo which was a bad idea now the IMEI is empty - F**K!
- going back to XXJVU now
UPDATE 3...
- Back to XXJVU still no signal however it detected at least T-Mobile at boot and gave me a radio box to select T-Mobile.
Sometimes the signal strength shows one bar (two bars when I am going to the window that points in direction of the sender)
though it should be fairly more here as other phones proof. No matter what that means anyway it says there is no service.
UPDATE 4...
- Compared the mobile settings with the i9003 and noticed that the i9003 shows EDGE, the i9000 GPRS
Alright, I got it back to GT_I9000_XXJQ3_XXJPY_DBTJS2 and made an official upgrade to the latest stock via KIES then. Nothing better.
I assume thise phone got a hardware defect then. Even though it doesn´t seem too logical