Database Develop

Lost IMEI

Hi,
My IMEI is 004999010640000.
I understood from reading on this forum that it is not a valid one.
However, my phone works.
I did back efs folder but I might had backed it up after too ma y past flashes.
1. How can I know if IMEI is fine?
2. Can IMEI or eds folder be restored from carrier/other if my backup is obsolete?
3. Can I find it in an old nandroid backup? How?
10x
Trumpy
Sent from my GT-I9000 using xda premium

If it starts 004999xxx then its been corrupted but you can always flash a stock samsung rom to get it back. Check this thread

Menvaihelv... said:
If it starts 004999xxx then its been corrupted but you can always flash a stock samsung rom to get it back. Check this thread
Click to expand...
Click to collapse
10x,
If it is corrupted, how can flashing a stock rom restore it?
I am on ICS. Should i simply flash a stock rom using cwm recovery?
I'd hate flashing back and forth, is there any alternative solution?
If my phone works, why do I need the imei for?
Regards,
Trumpy
Sent from my GT-I9000 using xda premium

y.trumper said:
10x,
If it is corrupted, how can flashing a stock rom restore it?
I am on ICS. Should i simply flash a stock rom using cwm recovery?
I'd hate flashing back and forth, is there any alternative solution?
If my phone works, why do I need the imei for?
Regards,
Trumpy
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
i am also having the same trouble. and took the plunge to flash via odin. now im having problems with that. if there was only an easy way to fix it. and easy wasys to back up and restore in future

Flashed CM10 Jelly bean No Service

So I'm going to assume that my IMEI is gone as the one that is listed under 'about phone>status' is different than the one printed on my phones manufacturer box. The one listed appears to start with 0049. I have verified the APN settings on my samsung galaxy s captivate are correct per my carrier - Straight Talk. Any help is appreciated, thanks.
I currently have flashed,
Kernel
Devil3-1.0.0-rc3-cappy-cfs-bln-cmc
ROM
CM10 JellyBean V2 with gapps + su

Try restoring your IMEI backup folder located in your Internal SD and see if you get service again.
Sent from my SGH-I897 using xda app-developers app

Nick0703 said:
Try restoring your IMEI backup folder located in your Internal SD and see if you get service again.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Sorry to ask but could you provide me with detailed steps on how to do this? I've already flashed back to an earlier version of android 2.x using odin3 one click but I'd like to know for future reference.

Check out this post. I've helped someone before with the same problem. http://forum.xda-developers.com/showpost.php?p=28936532&postcount=3
If it's still not clear, just ask me I'll make another one in detailed for you!
Sent from my SGH-I897 using xda app-developers app

Nick0703 said:
Check out this post. I've helped someone before with the same problem. http://forum.xda-developers.com/showpost.php?p=28936532&postcount=3
If it's still not clear, just ask me I'll make another one in detailed for you!
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the reply, I figured that was a possible solution but wasn't sure about copying entire folder. I had read posts about copying just the .nz_data.bin. I appreciate your help.

hmmm. Still seem to be having some trouble. I had flashed with odin one click to gingerbread 2.3.5 and made a copy of the efs folder to the internal storage using root browser. I've moved the nv_data.bin & imei folder & nv_data.bin.md5 over and now it's reporting the IMEI as unknown. I've played around with permissions setting the user:group to radio. and also tried 1001:radio w/ rwx---. I also tried clearing the dalvik cache afterwards in hopes that it would rebuild stuff. Not really sure what I am missing, anyways I'll probably flash to gingerbread again and make another backup to the internal storage with file manager in CWM, I'll then reflash to CM10 JellyBean and try to move again. Let me know if I am missing something.
Also do you have any idea why my efs partition is getting corrupt / overwritten when I am flashing? I've been following instructions in the thread for CM10 JellyBean 4.1.1 and It seems the 3 or 4 times I've flashed this devilkernel rc3 and then the cm10 jellybean v2 + apps + su package that my efs gets messed up. Thanks again.

Invalid IMEI prompt on bootup

Guys,
I just updated with the CM10 nightly and I am getting a prompt on bootup that my IMEI is not valid. The IMEI is not blank, and isnt something like 0123456789. Is this a big issue? My calling and texting are working fine, as is my mobile data.
Thanks

The same happens to me. I did an efs backup with root manager but is there any risk? Could someone explain please?

I backed up with cwm before loading cm10 0823. And did an imei restore from Nitrality and it says successful. However I still get an invalid imei on bootup
Sent from my GT-I9000 using xda premium

Updated to cm10 0824. Same issue. Should I do a full cwm restore?
Sent from my GT-I9000 using xda premium

Hey guys common issue if you want it back follow my guide http://forum.xda-developers.com/showthread.php?t=1845104 you might want to titanium backup your apps first then backup your sd
Sent from my GT-I9000 using xda premium

Restored cwm backup from before the issue started. No long have invalid imei. Update to latest cm 10 and invalid imei prompt on startup. However the imei screen under About has an imei number in it still.
Sent from my GT-I9000 using xda premium

Correct imei though as in the same as the one under the battery?
Sent from my GT-I9000 using xda premium

Nope. Its a different one.
Sent from my GT-I9000 using xda premium

webchaos said:
Nope. Its a different one.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
OK so its invalid try the link I previously posted if it works or not get back to me
Sent from my GT-I9000 using xda premium

After going back to stock GB, darky resurrection ROM, cm9 and finally cm10. IMEI is back and looking OK. Thanks.
Sent from my GT-I9000 using xda premium

That's good
Sent from my GT-I9000 using xda premium

Felt a bit of nostalgia going back through the last 2 years of ROMs lol. Thanks again.
Sent from my GT-I9000 using xda premium

webchaos said:
Felt a bit of nostalgia going back through the last 2 years of ROMs lol. Thanks again.
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
Well, in my case, my father's phone lost all efs backups, and nv_data.bin is corrupted (regenerated new one with default generic IMEI).
So, there is nothing to restore from. Reflashing to stock 2.3.6 JW5 firmware didn't help. So you think that I will have to reflash to 2.2.1? How so? I don't understand how older firmware may help restoring correct IMEI...and I don't own JTAG, z3w or SPT boxes...
And for morrons - no, there is no .nv_data.bin, no nv_data.bin.bak, or similiar...only new nv_data.bin(md5) with default, generic IMEI.
Is there any way to restore it? if somebody start to complain that I am thief, I can prove by photos of original phone box, and buying papers I have (my father gave them to me for this purpose).
And no, I don't have to steal anything, I own SGS3, SGS2, SGS, SGT10.1....so stealing another SGS is not an option for me
I just want to restore that phone to it's stock state (and then reflash again with CM10).
Anyone?

Virnik0 said:
I just want to restore that phone to it's stock state (and then reflash again with CM10). Anyone?
Click to expand...
Click to collapse
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
just flash a JVU and a PIT , should get you back your IMEI or look at My android solutions for details

xsenman said:
you can get a rescue kit from My Android Collections and or a solution from My Android Solutions
just flash a JVU and a PIT , should get you back your IMEI or look at My android solutions for details
Click to expand...
Click to collapse
Why are you so confident, that JVU will regenerate /efs?
as said before, my father was so genius, that he has wiped /efs partition out. I have restored some data, but without proper IMEI, so now I have generic one. I still do have old JVU package somewhere on my NAS, but I do not understand, how old firmware may help, because I am without any /efs backup anywhere... is that firmware customized so it checks and regenerates /efs if its damaged? If so, why is this feature missing from latest full JW5 firmare? Please understand that I know what I am doing, but right now, I have empty hands...without JTAG, z3w or similiar low-level gadget, it is really hard to restore proper /efs on my own...
But thank you for links, I will take a look on them...

More Clues On Fixing IMEI Issue (solved for me)
In my case I upgraded directly from Froyo to CM10.1 and got then same dreaded 'default' invalid/corrupt IMEI=004999010640000
On inspection of the /efs files present it was clear they had been created by the system in response to not being present.
Following advice in this thread and elsewhere I downgraded back to Froyo (XXJPU) and like magic my correct IMEI re-appeared but as soon as I upgraded up to CM9 it changed back to the invalid default of 004999010640000 again.
To cut a long story short I downgraded back to Froyo (XXJPU) again, flashed a recent CWM recovery and booted into the recovery. I then used ADB to get a (root) shell prompt and discovered that the correct /efs data was being mounted from the device /dev/stl3 and at this point I was able to tar up the contents of /efs and safely make a backup. I then upgraded to CM10.1, restored the correct /efs backup and rebooted.
Happy with correct IMEI now
I am not sure what is going on but I am speculating that the big jump from Froyo to CM10.1 bypasses come critical intermediate ROM build where the correct IMEI data is copied from /dev/stl3. CM10.1 assumes this step has taken place and makes no attempt to get the original IMEI data.
... Robert

robertrath said:
In my case I upgraded directly from Froyo to CM10.1 and got then same dreaded 'default' invalid/corrupt IMEI=004999010640000
On inspection of the /efs files present it was clear they had been created by the system in response to not being present.
Following advice in this thread and elsewhere I downgraded back to Froyo (XXJPU) and like magic my correct IMEI re-appeared but as soon as I upgraded up to CM9 it changed back to the invalid default of 004999010640000 again.
To cut a long story short I downgraded back to Froyo (XXJPU) again, flashed a recent CWM recovery and booted into the recovery. I then used ADB to get a (root) shell prompt and discovered that the correct /efs data was being mounted from the device /dev/stl3 and at this point I was able to tar up the contents of /efs and safely make a backup. I then upgraded to CM10.1, restored the correct /efs backup and rebooted.
Happy with correct IMEI now
I am not sure what is going on but I am speculating that the big jump from Froyo to CM10.1 bypasses come critical intermediate ROM build where the correct IMEI data is copied from /dev/stl3. CM10.1 assumes this step has taken place and makes no attempt to get the original IMEI data.
... Robert
Click to expand...
Click to collapse
Exactly that. Same goes with going from Gingerbread to Jelly Bean.
That critical intermediate rom... Is CM9
In other words, to safely preserve your IMEI,
Froyo/GB ---> CM9 ----> CM10/10.1/JB
Sent from my GT-P7510 using Tapatalk HD

[Q] SGH-t849 JB ROM Unknown Baseband?

Hey guys. I flashed a JB 4.2.2 ROM for the GSM tabs and all went well. Except when I flashed the T-Mobile modems JJB and JL3 it comes up as unknown baseband and I get absoultely no signal when I insert my SIM card. Am I missing something?

Perhaps your IMEI is bad due to corrupted EFS. Find the backup in sd card, and copy and paste back to /efs
Sent from my GT-N7100 using xda app-developers app

I managed to flash another rom and it works fine now

hey! can you post here what kind of ROM have you flashed? I'm currently running the SHW-M180S UC27 ROM (from original Korean version ROM) which is fine but I can't get EDGE! only GPRS and UMTS

quickbird144 said:
I managed to flash another rom and it works fine now
Click to expand...
Click to collapse
same problem here,
qucikbird can you tell me rom name so that I can get rid off this porblem?
mine is 4.2.2 cyongemod
baseband was "i9000ugjk3"
101-20131006-nightly p1
Only these information I have,
any help , specially Priyana
thanks

Is your IMEI OK?
If so, just unzip the modem zip, and copy the modem.bin to /radio
Sent from my GT-N7100 using xda app-developers app

priyana said:
Is your IMEI OK?
If so, just unzip the modem zip, and copy the modem.bin to /radio
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Sir thanks for quick support and reply,
There is no imei as well, tab came to me for no google store in it, after flashing "cm-9.0.0-p1.zip" from this link http://download.cyanogenmod.org/?device=p1
if I try to flash higher version than cm-9.0.0-p1.zip , error 7 occurs in cwm
its full details are as follow
Model "SGH-T894(converted to cyngonmod P1000)
4.2.2
Base band unkown( before flashing it was i9000ugjk3)
Kernel version: 3.0.86-g76a9412 [email protected]#1 Sun Oct 6 10:23DT2013
CPU ARMv7 Process rev 2 (v71)
cynogenmod version 10.1-20131006-Nightly P1
build number: cm_p1 -userdebug 4.2.2 JDQ39E ENG.JENKINS.20131006. 100422 TEST-KEYS
I hope this will help to solve my problem , you can't imagine my frustration,
Please suggest
thanks

Find in your internal or external sd card a backup folder.
See if there is an efs folder.
Copy the entire content to /efs replacing what you have in there. Reboot. See if IMEI reappear.
If not, you need to try to flash stock rom using odin.
Use overcome method found in my signature.
Sent from my GT-N7100 using xda app-developers app

priyana said:
Find in your internal or external sd card a backup folder.
See if there is an efs folder.
Copy the entire content to /efs replacing what you have in there. Reboot. See if IMEI reappear.
If not, you need to try to flash stock rom using odin.
Use overcome method found in my signature.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I made backup in cwm but there is no efs folder, I also restore from that backup but no luck
these are files in backup folder
boot.img
cahce.ext4.tar
cache.ext4.tar.a
data.ext4.tar
data.ext4.tar/a
nandroid.md5
recovery.img
recovery.log
system.yaffs2.img
stock rom for which model? SGH T849 or P1000

priyana said:
Find in your internal or external sd card a backup folder.
See if there is an efs folder.
Copy the entire content to /efs replacing what you have in there. Reboot. See if IMEI reappear.
If not, you need to try to flash stock rom using odin.
Use overcome method found in my signature.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
thanks Priyana Problem solved by your files and guide, Its now on gingerbread, baseband and imei have been restored,
no words to say thanks for your help
may you have success in your life one after the other,
thanks again and best regards,:good:

You are welcome.
You may want to try again with cm10.1 or any higher, as long as you know how to restock.
About efs backup, it isn't done by cwm.
When you flash cm9 or 10, it backs up your /efs to a safe place.
Usually in /sdcard/backup/
Or in /emmc/backup.
Sent from my GT-P1000 using xda app-developers app

[Ques] Lose the IMEI after up CM 10.2.1

I'm having trouble after flash cm 10.2.1 rom from stock KK4. Now,my IMEI is: 004999010640000. Starup phone the CM is warning Lose IMEI faild. Please help for me restore my original IMEI

Use one of these Odin or Heimdall One Clicks to get back to Stock KK4. That has proven to restore the imei for several. Then once u r back and have the # restored, back it up in a few places, just in case u run into this problem again.
http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
Sent from my SAMSUNG-SGH-I747 using Tapatalk

4-2ndtwin said:
Use one of these Odin or Heimdall One Clicks to get back to Stock KK4. That has proven to restore the imei for several. Then once u r back and have the # restored, back it up in a few places, just in case u run into this problem again.
http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
How to backup and restore the original IMEI while on Stock kk4?

hieuduc88 said:
How to backup and restore the original IMEI while on Stock kk4?
Click to expand...
Click to collapse
KK4 is stock GB, make a backup before you flash it using Titanium Backup.
Flashing KK4 should restore your IMEI. Once on it, make a backup (copy) of your efs folder before going back to CM. That way, if it happens again, you'll be able to restore it.
Sent from my SGH-I747 using xda app-developers app

BWolf56 said:
KK4 is stock GB, make a backup before you flash it using Titanium Backup.
Flashing KK4 should restore your IMEI. Once on it, make a backup (copy) of your efs folder before going back to CM. That way, if it happens again, you'll be able to restore it.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After going back to cm just copy efs folder again. need for set permission? Sorry for my English is bad

Once you are on Stock KK4, only then make a backup of the good efs folder. And after flashin cm or whatever rom, if you loose your imei, then you can restore the good backup from kk4.
There are some threads with tutorials somewhere in this forum and also apps on the Play Store that can be used as well.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

4-2ndtwin said:
Once you are on Stock KK4, only then make a backup of the good efs folder. And after flashin cm or whatever rom, if you loose your imei, then you can restore the good backup from kk4.
There are some threads with tutorials somewhere in this forum and also apps on the Play Store that can be used as well.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
There're a few as Slim rom after flash done no networks,no baseband, IMEI. Is the error due to EFS folder? and the problem is the same as mentioned above.

Yes. That is correct.
Sent from my SAMSUNG-SGH-I747 using Tapatalk

My phone have lost its IMEI since I bought it from my friend. I have bear the invalid IMEI notification for so long. Roll back to KK4 or even follow the hex editor topic doesn't work. Do you guys have any suggestion?

ngntuonghuy said:
My phone have lost its IMEI since I bought it from my friend. I have bear the invalid IMEI notification for so long. Roll back to KK4 or even follow the hex editor topic doesn't work. Do you guys have any suggestion?
Click to expand...
Click to collapse
Stolen phone?
If both those options don't restore it, I'm not sure you can without a jtag.
Sent from my SGH-I747 using xda app-developers app

BWolf56 said:
Stolen phone?
If both those options don't restore it, I'm not sure you can without a jtag.
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
He bought it brand new, and he did flash roms without backing up the /efs folder. I have the box with IMEI on it .
Is a jtag a tool that they use for hacking xbox 360?

ngntuonghuy said:
He bought it brand new, and he did flash roms without backing up the /efs folder. I have the box with IMEI on it .
Is a jtag a tool that they use for hacking xbox 360?
Click to expand...
Click to collapse
Jtag is used to push ROMs/bootloaders into devices but I'm not even sure that would fix your problem if flashing stock KK4 doesn't fix it.