Okay I've messed up really bad... My imei has got wiped tried all the possible methods to get but it aint working i got a back up of the efs folder and also a nandroid back up
Is there any other way i can get it back
Sent from my GT-I9100 using XDA App
even though ive got imei back in cm7 when i use odin to go back to stock the imei changes to the fake 00499.....
any help?
i need to sell this phone to pay for my s2
Sent from my GT-I9100 using XDA App
Related
How i can fix when my phone is no emei?
There's a tutorial in the forums to restore your IMEI if you made a backup of your efs folder. You can also try going back to stock (I know its inconvenient, but worked for me when my imei messed up and started with 004).
Sent from my SGH-I897 using XDA App
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
It's all unknown.
First off, I'm running Dark Knight 5.5 ICS, and have no service on the phone. I keep it in Airplane Mode all the time to conserve battery life. Today I decided to actually get service on it so I started looking at Sim Cards. I had everything ready to go, all I had to do was check out(to order the SIM from Net10 as they have SIMS for AT&T smart phones) so I decided to turn Airplane Mode off and check on things, the IMEI and all other values are Unknown. I did unlock the phone using an app called SGS Unlock by Clarke Hackworth. I vaguely remember the IMEI still being there after the unlock but I did restore the efs backup I made. Rebooted the phone and still no IMEI. I tried http://forum.xda-developers.com/showthread.php?t=1862928 and it did nothing.
Is it stuck in Airplane Mode or do I have to completely start over with ODIN?
Thanks for the help
If restoring the efs backup u made did not work, then yes, i have read multiple times of others Odin'ng back to Stock GB and recovering from this issue.
Sent from my SGH-I897 using xda premium
If you don't have efs folder backup or restoring the backup doesn't work i think you should Odin back to stock which should work most of the time
Sent from my SGH-I897 using xda app-developers app
Sorry I've not posted back till now. Been busy. Thanks for the help! I odined back to stock, then to stock Gingerbread, then flashed a modem, then flashed ICS and had my IMEI.
Sent from my SGH-I897 using xda app-developers app
Hi people I got a N7000 and it says no sim card, I repaired the sim tray, but it still says the same, i checked the IMEI and it says one that it's not similiar as the one on the back, how do I change the IMEI on the phone so I can have the original one?
why did it get changed, is original a stolen one? All interesting questions.
Sent from my GT-N7000 using Tapatalk 2
If the imei is corrupt, the only way to restore it is to restore from a backup or get the motherboard replaced.
Sent from my GT-N7000 using xda premium
SpyderTracks said:
If the imei is corrupt, the only way to restore it is to restore from a backup or get the motherboard replaced.
Sent from my GT-N7000 using xda premium
Click to expand...
Click to collapse
i have a restroed efs but i dont know how to restroe it wihch program or 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.