Related
i have been lurking these forums for a while. but made an account for this. i have been flashing roms and what not for about 6 months. as i was fed up with waiting for updates. anyway straight to the question.
my IMEI has changed recently to the 004999010640000 generic one. does that mean is corrupted. what are the risks/problems that i will face if i leave it or try to restore? should i re flash stock and work my way back to custom roms again? or are there other methods that i can do? do these methods restore the original IMEI or a new one. is there a problem with that?
its been like that for about 2 months. i have no backups. it also makes my phone show up twice on marketplace on a desktop. i guess google can see the difference.
i found my old imei . fair sure i shouldn't tell you what it is. is there a way to change it back to that code? without to much hassle? i really dont want to flash back to froyo and start again. i would settle with a factory wipe and some instructions on preventing this from happening again
Please follow instructions at own risk. I am fairly new to all of this but below is what work for me.
If you have a backup, which I did, then you should have an efs folder inside your backup folder. This contains the files you need. (nv_data.bin.md5 & nv_data.bin)
The easiest is to place these to files in the root folder of your internal sd card. Then with something like Root Explorer copy these files & then go to the actual efs folder of your phone and paste them of the existing files in this folder.
Once you have done this delete the nv_data.bak.md5, nv_data.bak and nv_log files.
If you don't have a backup others have said the best is to flash a stock rom which should then restore your original IMEI number. I have not personally done this but it is mentioned a lot.
I don't know how to change the IMEI number any other way.
i was hoping there was an easyer way. i dont have a baack up but i guess i will have to make one when i get it back. ill try it when i get some free time. would any stock rom work or do i have to get a build thats froyo or ginger. would this idea work?
first make back up of files i need. and do a titanium backup and nand
second flash back to stock. check for restored imei
3rd make backup of efs.
4th follow steps to get custom rom working again
5th restore nand backup
6th if imei is lost again use backup.
I just wish there was an easy way to do it other than going back to old firmware
Sent from my GT-I9000 using XDA App
There is if you had made a backup. Unfortunately without a back, which you should always make, you need to take the long route...
I read that the app called Galaxy_S Unlock by Helroz can fix your problem. You need rooted phone.
I have flashed alot of roms and hav alot of efs backups bt all these are just logs. R they useful?
Sent from my GT-I9000 using xda premium
Sys81 said:
I have flashed alot of roms and hav alot of efs backups bt all these are just logs. R they useful?
Sent from my GT-I9000 using xda premium
Click to expand...
Click to collapse
if i had made some im sure i wouldnt be having a hassle right now lol. just need one working one
i think i just did find a backup. from one of the installs it actualy was in the tutorial
going to try it now.
scubadude said:
Please follow instructions at own risk. I am fairly new to all of this but below is what work for me.
If you have a backup, which I did, then you should have an efs folder inside your backup folder. This contains the files you need. (nv_data.bin.md5 & nv_data.bin)
The easiest is to place these to files in the root folder of your internal sd card. Then with something like Root Explorer copy these files & then go to the actual efs folder of your phone and paste them of the existing files in this folder.
Once you have done this delete the nv_data.bak.md5, nv_data.bak and nv_log files.
If you don't have a backup others have said the best is to flash a stock rom which should then restore your original IMEI number. I have not personally done this but it is mentioned a lot.
I don't know how to change the IMEI number any other way.
Click to expand...
Click to collapse
is there anything else i should do? like change permitions? wipe or restart anything????
ended up just flashing samfirmware 2.3.6 stock. then reflashed cm9. i have my imei back. is there an easy way to back it up and restore it around. most things i se involve some terminal or adb. terminal im a bit iffy with and adb i wont be able to do
SturmTyrann said:
ended up just flashing samfirmware 2.3.6 stock. then reflashed cm9. i have my imei back. is there an easy way to back it up and restore it around. most things i se involve some terminal or adb. terminal im a bit iffy with and adb i wont be able to do
Click to expand...
Click to collapse
Nitrality app.
I don't think that app works with ics/cm9. Its unusually fast for. Backup. Almost like it didn't do anything at all. At backup and restore. It says done as soon. As I click backup or restore.
sent from icecreamland where everything looks cyan....
Look at your sdcard insanity/backup
just go to any CWM recovery and in backup and restore option, backup efs or vice-versa !
i tried re-stocking my SGT P1000 from aokp build 40# via odin n it show fail bt somehow manage to boot.bt now my tab is not showing network n IMEI .
i tried recovering from EFS folder but thats empty too.
i dont have EFS backup only nandroid backup of stock rom.
Plz help
Efs folder is visible.
Sent from my GT-P1000 using xda app-developers app
how do you restock? Overcome's GB-stock-safe?
What ROM are you booting into now?
I restock via Odin.use gingerbread stock,pit file and then dbdata.Odin show fail but boot on gingerbread when I again tried flashing.it happen to me before too as once by mistake i restore stock nandroid over cm9.
so currently on gingerbread.right now downloading over come gb stock safe v5 ll try flashing it.
Sent from my GT-P1000 using xda app-developers app
baseband is unknown.i flash aokp again that may be that correct it bt didnt works.can i install gb stock safe directly over aokp 40# or again hv to restock.
Sent from my GT-P1000 using xda app-developers app
you have to restock when coming from MTD rom like AOKP or CM9.
even for nadroid restore you have to restock then restore.
when restock, it is best using GB-stock-safe.
use its pit file and it also has modem files.
Edit, are you referring to GB-stock-safe when you said "overcome rom"?
Overcome ROM is a different thing.
yes gb stock safe i was about to correct that.i install bml my mistake due to rom naming confusion
now ll gb stock safe help in getting baseband?
Sent from my GT-P1000 using xda app-developers app
honestly I don't know about efs.
I read of people losing /efs due to bad kernel, but got it back with good flash.
I don't get it because I thought /efs once is deleted it is gone unless there is backup.
Anyway, you have checked your sdcard, no backup?
and GB-stock-safe can be flashed coming from aokp.
that is how we restock.
i didnt create any backup bt there is auto back up one with name efs and another with efs-294 .
and where is modem file for gb stock safe.it is not in zip file i download.only rom,pit file and overcome kernel.
Sent from my GT-P1000 using xda app-developers app
Gb safe stock works.got my imei back.i think problem was related to modem file.thanks a ton man.
Sent from my GT-P1000 using xda app-developers app
priyana said:
honestly I don't know about efs.
I read of people losing /efs due to bad kernel, but got it back with good flash.
I don't get it because I thought /efs once is deleted it is gone unless there is backup.
Anyway, you have checked your sdcard, no backup?
and GB-stock-safe can be flashed coming from aokp.
that is how we restock.
Click to expand...
Click to collapse
even if you delete efs folder, android will generate a new one with a different imei, its a real problem because he will find a hard time with his apps (paid ones) i tried the new efs once and i can't use my Samsung paid apps anymore, when restored my old efs, it works again.
If I helped you, please press the thanks button
efs.img
Hello.i tryed to backup efs partition on tab p1000,and got the 2gb efs.img file.As i know now,its too big.Is it possible that image contains /efs folder in it?And if yes,how can i restore?
Restocking didn`t bring imei back.
What did you use to restock?
i haven't heard of a 2gb /efs backup before. sounds like you should restock using a proven method like Overcome. Maybe you should try this out:
http://forum.xda-developers.com/showthread.php?t=1881981
like many, i also lost imei once, and this rom brought it back.
filteringfields said:
What did you use to restock?
i haven't heard of a 2gb /efs backup before. sounds like you should restock using a proven method like Overcome. Maybe you should try this out:
http://forum.xda-developers.com/showthread.php?t=1881981
like many, i also lost imei once, and this rom brought it back.
Click to expand...
Click to collapse
I`m not sure,but i read this thread too.Will try again anyway,thanks.
Gb safe stock works.got my imei back.i think problem was related to modem file.thanks a ton man.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Could you show me step by step to get IMEI back, i am facing the same problem. Thanks a lot
Sent from my SGH-I777 using xda premium
It is exactly two post above you. Or look at my signature.
Sent from my GT-I9300 using xda app-developers app
I got IMEI back. My experience: PC on offline mode(no wifi, no LAN), end all Kies process then downloading mode, turn on Odin blah...blah...
Sent from my SGH-I777 using xda premium
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
My brother owns an AT&T cappy...n after some months of custom rom flashing, he gave me the phone asking me to repair it.
It has stopped reading the sim card, when i checked the imei of the device it gave me a popup of IMEI null/null..also the baseband version is also unknown..
I have many a times flashed the stock rom as every thread about my problem is telling me to do..
also used galaxy s unlock, app for factory unlocking GS devices..but know success
i seriously want to give it a last try before handing it over for a repair outside..
any help would be highly appreciated!!!!!:crying:
Yep, usually using Odin or Heimdall to return to stock firmware should restore the imei. Have u tried to flash to Stock KK4 firmware yet ? The Odin or Heimdall One Clicks for i897ucKK4 can be found here... http://forum.xda-developers.com/showpost.php?p=18370912&postcount=3.
yess!! many a times..but no success
I also wanted to add that :-
during the galaxy s unlock method..i usually get the busybox problem error...though i've installed and verified it many a times
With all the months of flashing that ur brother did...i would think there would be a backup of the efs folder on the sdcard?? Some roms and kernels, when flashed, will create the efs backup for u.
yess!! hopefully dere's an EFS folder.. but i was too bugged up when googling for the method for restoring it..
n also i'm not sure whether the folder is fine or corrupted/messed up..
also i'll be greatful if i'll get to know the easiest step by step process of restoring it.:good:
gautamchawla195 said:
yess!! hopefully dere's an EFS folder.. but i was too bugged up when googling for the method for restoring it..
n also i'm not sure whether the folder is fine or corrupted/messed up..
also i'll be greatful if i'll get to know the easiest step by step process of restoring it.:good:
Click to expand...
Click to collapse
Its as simple as replacing the current one with the backup one.
Sent from my SGH-I747 using xda app-developers app
??
Where to replace...in the root of the system or the SD card,???
busybox error!!!
Can anyone tell me about the BUSYBOX ERROR I'm receiving..??
gautamchawla195 said:
Where to replace...in the root of the system or the SD card,???
Click to expand...
Click to collapse
If you check on the internal sd, you'll see an efs folder. Should probably take a look for yourself before asking those questions
Sent from my SGH-I747 using xda app-developers app
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.