[Q] imei problem in ROM][IMM76I][4.0.4][AOSP] ICS333 RC4 - Galaxy S I9000 Q&A, Help & Troubleshooting

hello,
i flashed ROM][IMM76I][4.0.4][AOSP] ICS333 RC4 from GB 2.3.5 AND my imei disapeard.
i flashed back to stock rom and the celular service worked .
then i flashed back to ROM][IMM76I][4.0.4][AOSP] ICS333 RC4 and now i have a imie and everything works fine execpt of the face that the imei is not the one listed on the phone (behind the battery. is that o.k ?

shmhazan said:
hello,
i flashed ROM][IMM76I][4.0.4][AOSP] ICS333 RC4 from GB 2.3.5 AND my imei disapeard.
i flashed back to stock rom and the celular service worked .
then i flashed back to ROM][IMM76I][4.0.4][AOSP] ICS333 RC4 and now i have a imie and everything works fine execpt of the face that the imei is not the one listed on the phone (behind the battery. is that o.k ?
Click to expand...
Click to collapse
Flash back to stock and backup your EFS folder this includes the nv_data.bin file that contains your IMEI
Google search will be you friend or alterntively search the forum as this question has been asked before and answered by myself for other users

just reflash your stock rom....

I found there was an autobackup in /sdcard/efs/IMEI so backed up /efs and then copied /sdcard/efs/IMEI to /efs ...bit scary though for a simple ROM flash

jago25_98 said:
I found there was an autobackup in /sdcard/efs/IMEI so backed up /efs and then copied /sdcard/efs/IMEI to /efs ...bit scary though for a simple ROM flash
Click to expand...
Click to collapse
read the disclaimer that all DEVs post on the OP They all say the same thing
"Flash at your own risk"
Remember these are not the Factory ROMs and things may go wrong.
Read the whole thread for a ROM makes for a very informed decision before flashing

I guess what I'm dying to know is why some rooms blank the efs folder and why some don't. I read about losing the efs folder but after doing gummy and black from without needing to restore I figured the backup had to be just a precaution. hope the restore instructions get added to instructions.
is is that some rooms have the efs folder in their tar all and others don't? if so might it be better to not have it in the tar all so restore isn't needed. if you do a cp and get the order wrong you might blank your only backup (should have another backup of course but its nice to be nice to people of course

jago25_98 said:
is is that some rooms have the efs folder in their tar all and others don't?
Click to expand...
Click to collapse
EFS folder is a STATIC folder ie it will NEVER be included in a ROM stock or custom.
The nv_data.bin file located in the EFS folder contains data unique to each handset therefore it will not be included in any ROM.
Some ICS ROMs will cause issues with the permissions on the EFS folder and the files within causing the IMEI to display incorrectly or to have none at all

Lexrsk said:
EFS folder is a STATIC folder ie it will NEVER be included in a ROM stock or custom.
The nv_data.bin file located in the EFS folder contains data unique to each handset therefore it will not be included in any ROM.
Some ICS ROMs will cause issues with the permissions on the EFS folder and the files within causing the IMEI to display incorrectly or to have none at all
Click to expand...
Click to collapse
Well that's the thing you see. As far as I can tell ICS333 doesn't have the /efs folder so whatever is on there before the ROM is loaded should be there after unpacking. But unlike the Black ROM it isn't and I don't understand why.

jago25_98 said:
Well that's the thing you see. As far as I can tell ICS333 doesn't have the /efs folder so whatever is on there before the ROM is loaded should be there after unpacking. But unlike the Black ROM it isn't and I don't understand why.
Click to expand...
Click to collapse
If it it is not there then post in the ICS333 thread.
Include the output of "df" from either terminal emulator or ADB
ie
cd /
df >>/sdcard/phonedir.txt

thanks,
i copied the backuped nv data from stock rom and got my imie back.
maybe it's somthing in the permissions ilke said here.
thanks a lot .

Related

[Q] I think I deleted the contents of my /efs folder. Help!!!!

Hi all,
I recently upgraded to JPM version of froyo, and wanted to change back the product code to the original. After restoring from the .bak files, I got back the original product codes. However, while copying to another location for backup, I deleted the contents of the /efs folder by mistake (atleast I think I did).
The /efs folder is empty, but the phone still works fine. Haven't rebooted the phone for fear of bricking it. Is there a way to recover deleted files? Or are those files just hidden from view?
Someone please help
Update:
Managed to get of copy of nv_data.bin from a folder used by sgstoolbox. Rebooted the phone and phone works fine. Checked the folder contents, has nv_data.bin, nv_data.bin.md5, .nv_state and a folder named .android. Is there anything else which should be there? How to restore?
Do you have a backup of your /efs folder?
Woah same happened to me just some Hours ago !
If you used SGS Toolbox to check, you are lucky because it automatically creates a backup.
-> I think SUFBS Explorer deleted the efs because i am sure i checked "copy" ... anyway !
If you have any backup file, you are lucky.
One question by the way:
I´ve also lost the "IMEI" Folder, but my IMEI is still correct. Is that because ne nv_bin is just enough for the system checks ?
EDIT: Go and check with SGS Toolbox, if it displays your code, it is still there + it creates a backup file on your sdcard (you should double-check that anyway)
I'd say that the best and easiest way of restoring your product code is by using this: http://forum.xda-developers.com/showthread.php?t=787163
messing around with /efs folder is not a good idea, especially if you don't have a back up.
Just remembered that I have a titanium batch backup of system + apps taken a while ago when I was on stock firmware. Any way to restore the /efs folder from that? The shock of losing the /efs folder was enough to jolt me out of a beer induced haze ;-)
The phone still works, which is good news. But anyway to restore from Titanium backup?
fullerms said:
Just remembered that I have a titanium batch backup of system + apps taken a while ago when I was on stock firmware. Any way to restore the /efs folder from that? The shock of losing the /efs folder was enough to jolt me out of a beer induced haze ;-)
The phone still works, which is good news. But anyway to restore from Titanium backup?
Click to expand...
Click to collapse
Titanium does not backup /efs.. If you don't have a backup, you're basically screwed! Sorry to be the bearer of bad news
Like I said, the phone works fine after I restored the nv_data.bin file. I listed the files which were rebuilt by the system. Is there anything else missing? Can someone post a screen shot of the contents of your efs folder?
Sent from my GT-I9000 using XDA App
fullerms said:
Like I said, the phone works fine after I restored the nv_data.bin file. I listed the files which were rebuilt by the system. Is there anything else missing? Can someone post a screen shot of the contents of your efs folder?
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
Oh, so you DID have a backup? Nice! Besides what you lited in the first post, there are the following things:
.imei (file)
imei (folder)
- .nvmac.info
- bt.txt
- mps_code.dat
Any idea what those files are for? Possible to check what they contain?
Sent from my GT-I9000 using XDA App
Like i said, my imei folder was deleted aswell...
No problems so far with that !
Use rootexplorer, dont use ASTRO. It's crap and does not show all files, including the whole /efs
My EFS folder is empty too...and I don't know why, I have only flashed a couple of time with odin and JM9....
But SGS Toolbox report my csc correctly as ITV....even if I used the HUI csc from my operator with odin....
Could it be a problem if the efs folder is empty? The phone is working well...the only problem is that it loses very often the wifi connection...but I don't think that it is csc related...

[Q] IEMI & CyanogenMod 7 problem

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!

[Q] URGENT! IMEI screwed, need help to restore!

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.

HELP - CM10 upgrade and lost IMEI

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.

Flash from cm9 to cm10.x without lost of efs

Hi,
i have a problem that is new to me. I flashed a lot of roms without problems and was on cm10.2. I went back to cm9 and wanted back to cm10.2.
I lost my efs folder and had to flash a stock rom. Now i am on cm9 (mackay rom with gear kernel) and when i flash cm10.2 mackay rom a lost the efs folder everytime.
So now the question:
How can i flash a cm10.2 rom without losing the efs folder?
Kind regards
Srkonus
Sent from my GT-I9000 using xda app-developers app
Its odd that you lose the IMEI from flashing from CM9 to CM10.2, although that happened to me today as well
Two ways to do this,
1.) Go back to stock, then flash in pure CM9, let it boot, then go to CM10.2
2.) Just flash in CM10.2 anyway, you should have backups of your efs (on my phone at least its /sdcard/backup and there's a few folders all beginning with efs). Inside those folders there should be a whole list of files, two of which are nv_data.bin and nv_data.bin.md5.
Download Root Browser/Root Explorer and copy nv_data.bin and nv_data.bin.md5 to /efs, overwrite the existing files. Reboot and it should be solved (I did this today so it worked for me).
Sent from my GT-P7510 using Tapatalk HD
Soryuu said:
Its odd that you lose the IMEI from flashing from CM9 to CM10.2, although that happened to me today as well
Two ways to do this,
1.) Go back to stock, then flash in pure CM9, let it boot, then go to CM10.2
2.) Just flash in CM10.2 anyway, you should have backups of your efs (on my phone at least its /sdcard/backup and there's a few folders all beginning with efs). Inside those folders there should be a whole list of files, two of which are nv_data.bin and nv_data.bin.md5.
Download Root Browser/Root Explorer and copy nv_data.bin and nv_data.bin.md5 to /efs, overwrite the existing files. Reboot and it should be solved (I did this today so it worked for me).
Sent from my GT-P7510 using Tapatalk HD
Click to expand...
Click to collapse
Hi,
thanks for your answer. Unfortionally it works not for me. Replacing the efs folder does not work and also flashing to cm10.x. i would stay at cm9.
srkonus said:
Hi,
thanks for your answer. Unfortionally it works not for me. Replacing the efs folder does not work and also flashing to cm10.x. i would stay at cm9.
Click to expand...
Click to collapse
Possibly this thread could help?
http://forum.xda-developers.com/showthread.php?t=859914
BTW: one can do it either by using ADB or within the app "Terminal Emulator" (by Jack Palevich) with same commands.

Categories

Resources