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
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
I had my cappy rooted and upgraded to cyanogen mod 10. Everything was running fine for a few days when my cell crashed and rebooted. After it rebooted the IMEI went to the stock IMEI. I tried to run my back up but no luck. Went back to stock but since the EFS file is gone all I get is the stock IMEI. Is it a way to get the file from another cappy and edit it with the right IMEI and other info so it will work on mine? or any other ideas? maybe some Tech who is willing to play with my cappy for a fee? Any help will be appreciated. Thanks guys.
Can you tell me what is ur imei number rite now??
Sent from my SGH-I897 using xda premium
I think you will find the help you need if you read this thread, (you are not the first one to not have a good backup of your efs folder.)
http://forum.xda-developers.com/showthread.php?p=35225094
Stupidly, I have been trying to install ROMs that aren't compatible with the I9305T which caused mine to stop functioning properly.
I have flashed it back to the stock Telstra ROM and 2 problems have come up. The first being that it doesn't detect a sim card in it at all and the second being that it won't connect to my PC at all (although I can still use Odin to flash it).
Does anyone know what might have gone wrong to make it suddenly act like this?
The reason it's acting like this is because you flashed ROMS not intended for i9305. What did you flash?
You will most probably have no efs partition now as a result and that's why your sim isn't recognised.
If you didn't make a backup, I think the only thing you can do is take it for repair.
Sent from my GT-I9305 using XDA Premium HD app
Obagleyfreer said:
The reason it's acting like this is because you flashed ROMS not intended for i9305. What did you flash?
You will most probably have no efs partition now as a result and that's why your sim isn't recognised.
If you didn't make a backup, I think the only thing you can do is take it for repair.
Sent from my GT-I9305 using XDA Premium HD app
Click to expand...
Click to collapse
I made a backup before I flashed with TWRP would I be able to restore that?
Hi,
You have to restore your IMEI (backup folder "efs")
Else there's a way for GT-I9305,
but not sure the Param_Bin_I9305.zip - 612.14 KB file is good for I9305T
Anyway, you can ask in the thread for your problem