Database Develop

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] IMEI Problem. Lost my original back up!

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

[Q] IMEI NULL/NULL Baseband UNKNOWN

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

Help! Unknown imei on N900a. Can't root, so how to fix?

OK this is beginning to annoy me greatly. I have the note 3 n900aucueoc1. My boss gave me this phone because it all of the sudden "broke". OK cool, a free phone I thought. Wrong. Not cool.
I figured out the problem has to be a screwed up efs folder because the phone won't read a sims card. The broadband version and imei are "unknown" and the Version is custom. Heres the weird part though. It isn't always custom. Once in a while when it's restarted it will load and it's version Will be official and everything seems to work.
The problem I am having is apperently, this phone cannot be rooted. I have no way to access and edit the efs folder. If it can be rooted please enlighten me because I've tried everything.
Any answers?? Help is GREATLY apprecitated!!

Hello. Your only choice for root would be a downgrade to 4.4.2, Install Towelroot, SuperSU, Safestrap & Busy box. If you want rooted 5.0 you'll need to flash Walter Whites rooted 5.0 OC1 using Safestrap.

OK awesome.. thank you.. I'm guessing the problem is the efs folder then? Now I just need to figure out how to downgrade. I'm sure there's a post on here somewhere about that lol.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

Are there any other downloads for the firmware? Sam mobiles not working for me.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app

crob65775 said:
Are there any other downloads for the firmware? Sam mobiles not working for me.
Sent from my SAMSUNG-SM-N900A using XDA Free mobile app
Click to expand...
Click to collapse
In the general section there is a thread called "NC2 Odin files" or something like that... Download those.
Also, you don't need root to edit the efs... Download qpst and qdxm... I can't post a link but just google it

Awesome thank you. I found the downloads but it says it's for the galaxy s3. . Will it still work? Also why does my device switch from custom to official randomly.. like I said sometimes it works, or appears to anyways. Like right now the mode is in custom but everything appears fine.. is this a problem with the efs? Or something else entirely?
EDIT: OK wow I downloaded both of those but have no idea how to use them.. Google here I come. Answers to my other questions much appreciated.. I would think if my efs folder was messed up it would never work but why does it work sometimes and other times I get all unknowns?? Help please.