Database Develop

HELP! - Insert SIM card :(

Two days back I flashed the JPC firmware through Kies and everything was fine. Then I noticed that my Product code has been changed, so I rooted my phone and restored the nv_data.bin and nv_data.bin.md5 from the backup.
Today using registry hacks, I downgraded to an older stock firmware through Kies. My phone is not rooted anymore after I downgraded. Now though my phone boots, but there is no network. When I go to Wireless and network->Mobile networks it says "Insert SIM card to access network services" and activates Flight mode. Mine is an Indian Galaxy S. It's not sim-locked. I checked the IMEI to see if it has been corrupted, but nothing. The IMEI is intact, same as original. Product code, Sales code everything is right.
What did I do wrong here? Why don't I have network now? What am I missing here? Please help

Maybe you didn't install your sim card correctly. The corner with the rectangle "removed " should be in the top down when you face the back of the phone
Sent from my GT-I9000 using XDA App

I flashed JPC again with Odin. Everything's back to normal now. But... how do I go back to the stock rom and get it working? I have the stock rom, but when I flash it I don't get network. Does this mean that I'm stuck with JPC forever?
Thanks to the above poster. The sim is inserted properly. I'm a programmer so I have a good knowledge of what I'm saying, but unforunately not so good with linux kernels.

I faced the same problem, days back... when i was testing with JPC... you cannot move to any of the 2.1 foirmware
The JPC changes the file permissions and few of the properties of NV_data in efs...
Leter i found a way to fix, it... now i am back to 2.1

I had a sam issue, so I just restored nv_data file from backup file and I m good to go. I deleted md5 file as well. Back up file has creation date of before I flashef with 2.2. Hope this will help
Sent from my GT-I9000 using XDA App

I know this is an old post but I just had the same problem after restoring a backup through clockwork mod and I couldn't find a decent answer anywhere.
I fixed it just by re installing the kernal, in my case it was hardcores speedmod kernal.
Obviously this is a better option as you don't have to wipe your phone.

whobeit said:
I know this is an old post but I just had the same problem after restoring a backup through clockwork mod and I couldn't find a decent answer anywhere.
I fixed it just by re installing the kernal, in my case it was hardcores speedmod kernal.
Obviously this is a better option as you don't have to wipe your phone.
Click to expand...
Click to collapse
Someone needs to add this to the OP. Worked like a charm.

[Q] Will i9000 rom cause a relock?

I am wanting to flash the perception build. I was wondering if I flash it will I lose my unlock? Im currently on cognition 2.3b6.
Thanks

Probably. I was unlocked and lost mine... if worried, back up your /efs folder - especially nv_data.bin. It takes some work, but it is possible to unlock again.

Wait so if I backup my /efs folder (on 2.2 right now), then I update, can I just replace the nv_data.bin on the i9000 firmware?

probably, I have not tried. But if you roll back, you have the original mv_data.bin (and md5) files to get you back where you were. If you don't have the /efs files, and your original unlock code, you can be stuck with no onluck, even on 2.1.

michael.seltzer said:
I am wanting to flash the perception build. I was wondering if I flash it will I lose my unlock? Im currently on cognition 2.3b6.
Thanks
Click to expand...
Click to collapse
Yes you will lose your unlock but if you have your codes saved then just re-enter them and it will be good to go...if you don't have your codes there are methods to unlock again posted in the Dev forum...

So I have flashed a bunch of regular cognition builds and not lost my unlock , but since this is an i9000 rom its different.
Do I have that right?

Never lost my unlock after flashing any cappy/i9000 roms.

Have you flashed perception?

No but it makes no difference, flashing to stock jf6 and installing any rom won't make you loose your unlock, why would you think that would happen?
Get the sgs unlock app from the market, it'll show you your codes and save them on the sdcard just in case you still think you'll get locked.

already on 2.2 so i can't get my codes. I have flashed many roms not sure why i9000 roms would be different thats why i asked

michael.seltzer said:
already on 2.2 so i can't get my codes
Click to expand...
Click to collapse
Flash back to jp6 http://forum.xda-developers.com/showthread.php?t=731989

Im not sure you understand once u go to 2.2 the codes are encrypted. going back does nothing, still encrypted somehow.

peachpuff said:
No but it makes no difference, flashing to stock jf6 and installing any rom won't make you loose your unlock, why would you think that would happen?
Get the sgs unlock app from the market, it'll show you your codes and save them on the sdcard just in case you still think you'll get locked.
Click to expand...
Click to collapse
It has happened to many of us, so don;t tell people it can't happen.
Some combination of firmwares encrypts the data in the nv_data.bin and the result is that the unlock code that was saved no longer works.
The only solution is to replace or rebuild the nv_data.bin file so that the phone will accept an unlock code. Saving the /efs partition files before flashing is the only way to recover the original files, as flashing back to stock will not restore the /efs partition.
This issue affects all galaxy S phones, but no one has determined the exact cause other then flashing ROMs.
Oh, and SGS unlock just looks in the nv_data.bin for the codes, if the files are encrypted SGS fails, just like manually looking at the files with a hex editor fails.

michael.seltzer said:
Im not sure you understand once u go to 2.2 the codes are encrypted. going back does nothing, still encrypted somehow.
Click to expand...
Click to collapse
There is a thread in the development section about unlocking 2.2 after the nv_data.bin is encrypted. This method works for 2.1 in the same situation:
http://forum.xda-developers.com/showthread.php?t=831569
There are tools that will rebuild your nv_data.bin file for you, I did mine manually (before the tools) but it worked. I was re-unlocked.

alphadog00 said:
It has happened to many of us, so don;t tell people it can't happen.
Click to expand...
Click to collapse
I guess i was lucky, never happened to me, thanks for the info.

I was just thinking, is there a chance that the phones that AT&T sells without a contract are factory unlocked and this is the reason some of us don't get relocked after this procedures?
At least it would be a good explanation

So i'm still a little confused on this subject. Is it the i9000 rom that can cause relocks or it just roms in general?

rastanthology said:
I was just thinking, is there a chance that the phones that AT&T sells without a contract are factory unlocked and this is the reason some of us don't get relocked after this procedures?
At least it would be a good explanation
Click to expand...
Click to collapse
No, there is only one model of the captivate and AT&T will not unlock the phone even if you buy it off contract. There have been a few exceptions, but not many.
If they were factory unlocked, no one would need to unlock to start with.

michael.seltzer said:
So i'm still a little confused on this subject. Is it the i9000 rom that can cause relocks or it just roms in general?
Click to expand...
Click to collapse
Again,
I don't think anyone has determined the exact cause. No one has taken an unlocked phone and methodically flashed ROMs to see what order of events causes it to relock.
Many of us experimented with many different ROMs and at some point realized we were relocked.

i wnat relock my i9000
i want relock (carrier lock) my samsung i9000 any solution??

[Q] No network/service over Onecosmic ICS 4.2

Hi,
I am on Onecosmic 3.1, I tried flashing 4.2, after flashing 4.2 I lost phone signal, it is saying No Service. Again I went back to old 3.1 version, no problem with signal.
So, Please help what should I do to flash 4.2 version on my phone.
Edited: Thanks everyone, I made it work flashing different modem.
Thanks in Advance,
Ajay

Check imei number. Version 4.1 & 4.2 have been corrupting imei number which causes no network
Sent from my GT-P7500 using xda premium

Hmm, for me, in ICSSGS 4.2, I do have phone signal and full service, however, when I pull down my Notification bar, it displays "No service.", which, fortunately, is a lie

Thanks for reply,
So is there any solution for this?
Thanks,
Ajay

I'm a semi noob at the technical stuff, but I seem to remember that this issue can be solved by restoring the backup you have surely made of your EFS folder . This folder contains all the info about your carrier and such.
If you don't have a backup of your EFS folder, I cannot help you with my limited knowledge

Follow these at your own risk or search the forums for a more thorough explanation.
If you have made a backup use something like root explorer to look for the EFS folder in the backup & copy the two files nv_data.bin & nv_data.bin.md5. Now go to the EFS folder on the phone & paste over these to files replacing them with your backups. You can then delete nv.log, .nv_data.bak & nv_data.bak.md5. Or that is what I did and it worked.
If you did not make a backup then you would need to flash a stock rom which usually does the trick (all three files). As your IMEI appears to be fine in v3.1 I would make a backup of 3.1 & use those files. You could also copy the two files out of the efs folder and place them in your root directory then after installing 4.2 just replace the files with the ones you copied.

ajay_lanki said:
Hi,
I am on Onecosmic 3.1, I tried flashing 4.2, after flashing 4.2 I lost phone signal, it is saying No Service. Again I went back to old 3.1 version, no problem with signal.
So, Please help what should I do to flash 4.2 version on my phone.
Thanks in Advance,
Ajay
Click to expand...
Click to collapse
Many pepole who flashed RC4.1 experienced this problem, its due to the IMEI being changed to some default value. this can be fixed if you had backed up your efs folder, if not you have to reflash the official gingerbread then copy the efs folder using ROOT EXPLORER, this will fix the corrupted IMEI issue. This issue has been fixed in RC4.2 so after you get your IMEI fixed, flash RC4.2.
Sent from my GT-I9000 using xda premium

Thanks for your reply.
I will try this and let you know the result. Thanks once again.
-Ajay

I seem to have the same problem, sometimes my phone reboots, and radio is gone. When I check, IMEI-N° isn't displayed, but after some reboots its back.
I did back up the EFS Folder, but how can I stop this from happening on a regular basis?
Regards

lemalsaint said:
I seem to have the same problem, sometimes my phone reboots, and radio is gone. When I check, IMEI-N° isn't displayed, but after some reboots its back.
I did back up the EFS Folder, but how can I stop this from happening on a regular basis?
Regards
Click to expand...
Click to collapse
If you restored your EFS backup it should be ok...but since is happening many times...you can reflash a stock firmware and then flash again your current ROM.

BoBoGrEy said:
If you restored your EFS backup it should be ok...but since is happening many times...you can reflash a stock firmware and then flash again your current ROM.
Click to expand...
Click to collapse
By "backing up" you mean just copy/paste it to the respective folder?

Hello guys. This happened to me as well with onecosmic ICS RC4.2. Will be lashing back stock GB fw as I do not have an efs backup

Hi,
I have tried flashing 4.2 again and checked IEMI number, no change in IEMI number but no Network. It is saying Emergency Calls.
My phone works only in Rc1 or 3.1.
Please help me what should I do, I dont have efs backup.
Thanks,
Ajay

Hi ajay_lanki
the latest Team ICSSGS Build has a script to fix efs folder permission, which should solve the problem. Threat:
http://forum.xda-developers.com/showthread.php?t=1398223
I didn't read through the comments though, can't tell if it works!
Cheers

scubadude said:
Follow these at your own risk or search the forums for a more thorough explanation.
If you have made a backup use something like root explorer to look for the EFS folder in the backup & copy the two files nv_data.bin & nv_data.bin.md5. Now go to the EFS folder on the phone & paste over these to files replacing them with your backups. You can then delete nv.log, .nv_data.bak & nv_data.bak.md5. Or that is what I did and it worked.
If you did not make a backup then you would need to flash a stock rom which usually does the trick (all three files). As your IMEI appears to be fine in v3.1 I would make a backup of 3.1 & use those files. You could also copy the two files out of the efs folder and place them in your root directory then after installing 4.2 just replace the files with the ones you copied.
Click to expand...
Click to collapse
I have tried this, but no luck. Please help me if there is any other way.
Thanks,
Ajay

Sorry fairly new to all of this. If what I did doesn't work for you I can't help. Hopefully someone else can
The next best thing would be to flash a stock Rom of gingerbread and start again
Sent from my GT-P7500 using xda premium

First: RC4.2 doesn't solve IMEI issue, i had it with 4.1, resotred efs, it worked, flashed 4.2, and issue again.
Second: The best way to restore /efs backup is going into /efs BACKUP (not original), multiselect every file, copy, and paste in ACTUAL /efs folder. Then reboot and that's it. If no /efs backup was ever made, the only way to solve imei loss is to go back to a stock rom (wich makes your imei come back), backup /efs from there and go ahead with ICSSGS again.

fps249 said:
First: RC4.2 doesn't solve IMEI issue, i had it with 4.1, resotred efs, it worked, flashed 4.2, and issue again.
Second: The best way to restore /efs backup is going into /efs BACKUP (not original), multiselect every file, copy, and paste in ACTUAL /efs folder. Then reboot and that's it. If no /efs backup was ever made, the only way to solve imei loss is to go back to a stock rom (wich makes your imei come back), backup /efs from there and go ahead with ICSSGS again.
Click to expand...
Click to collapse
scubadude said:
Sorry fairly new to all of this. If what I did doesn't work for you I can't help. Hopefully someone else can
The next best thing would be to flash a stock Rom of gingerbread and start again
Sent from my GT-P7500 using xda premium
Click to expand...
Click to collapse
ajay_lanki said:
I have tried this, but no luck. Please help me if there is any other way.
Thanks,
Ajay
Click to expand...
Click to collapse
ajay_lanki said:
Hi,
I am on Onecosmic 3.1, I tried flashing 4.2, after flashing 4.2 I lost phone signal, it is saying No Service. Again I went back to old 3.1 version, no problem with signal.
So, Please help what should I do to flash 4.2 version on my phone.
Edited: Thanks everyone, I made it work flashing different modem.
Thanks in Advance,
Ajay
Click to expand...
Click to collapse
I've had the same issue. No matter how many times you re-flash the ROM and do FULL wipe, I wont change anything, because FULL wipe is not really "FULL", neither is Factory reset etc. For some reason it needs a "real-FULL-wipe" (Just something I made lol). Anyway you can do it following these steps:
1. Flash an NONE ICS based ROM, say JVU stock ROM .(Download it from Sammobile.com, go into download mode, and flash it using Odin 1.85 with 512 pit file)
(You are on a Stock JVU ROM now)
2. ROOT you JVU ROM. (Any method is fine but I prefer flashing Semphore kernel using Odin, just download the kernel from here, go into download mode, and put the kernel in PDA section and flash, no pit files needed for this).
(You are on a ROOTed Stock JVU ROM now)
3. Flash CM7 stock ROM. (Download CM7 stable version not a nightly version from their website, copy it to your INTERNAL SD Card, go into CWM and flash. If you had issues there just re-flash).
(You are on a stable version of CM7 that is already Pre-rooted)
4. Flash Onecosmic 4.2. (Download it, copy it to INTERNAL SD Card, go into CWM and flash, sometimes it gets stuck on a boot loop or on logo screen, go into CWM using the three buttons combo :Volume up button + Power + Home key. Once you're in CWM re-flash it again.
Do this and I will guarantee that it will solve ANY problem you or anyone else have with Onecosmic ICS 4.2.
Only problem you may encounter with the ROM is External SD card issues, which is caused by either the ROM itself or your own SD card.
A >> "thank you" would be nice . Have a good one.

Struggling With ICS EFS/IMEI Restore

Hey all,
I should mention first that I have a DesireHD and have never worked with a Sammy before today.
I went about looking to root and upgrade my friends SGS.
Followed this guide and all went swimmingly.
I got my head around what ODIN is and does, what files are what and how the procedures work for Samsung phones.
ICS booted and performed exceedingly well apart from the IMEI problems.
Now, over the past few hours Ive tried everything from as many guides I could find about backing up and restoring /efs. Nothing is working.
Ive tried all flavours of ICS ROMS but they all end up with a completely blank IMEI and unknown details in the phone status menu.
If I flash back to stock GB located in the kit from the guide all is well, phone works. ICS - no IMEI.
I took several backups of /efs using RootExplorer, Nitrality and taring through ADB. The restore just not work.
I also manually fixed permissions through RE and also using ADB shell.
The only common thing is that the IMEI through *#06# is completely blank, not 0's or 049 etc, just blank.
What would be my next step from here to get it working with ICS? Have I missed something? Is it just not going to work with this particular device?
I probably wont have the phone again till next week as I left it on rooted stock GB for now so have plenty of time to dig a little deeper into the issue ut would appreciate any help.
Thanks

Hello.Ive been on ics since the beggining and at first i had no problems at all.Last couple of weeks i started to have problems with phone signal and imei.Kinda lost baseband,huge battery drain,phone shutdowns and when restarted no imei or baseband unknown.Went back to Gingerbread and all was ok despite some battery usage but my phone has 2 years and i cant ask too much of my old battery.Was kinda disapointed but today i flashed Elite rom http://forum.xda-developers.com/showthread.php?t=1621976 and for my surprise the phone handle well without loosing imei or baseband.
So my advice is to get chainfires recovery for gingerbread and then flash Elite rom.It will give you a bootloop when restarting so you have to remove the battery,get to recovery and flash the rom again. Good luck
PS- Dont forget to wipe data,cache,dalvik and system before you flash

Dude360 said:
I probably wont have the phone again till next week as I left it on rooted stock GB for now so have plenty of time to dig a little deeper into the issue ut would appreciate any help. Thanks
Click to expand...
Click to collapse
Check this out
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"

what to do next
Dude360 said:
Hey all,
What would be my next step from here to get it working with ICS? Have I missed something? Is it just not going to work with this particular device?
download nitrality from market restore efs then reboot worked for me
Click to expand...
Click to collapse

hullfc27 said:
download nitrality from market restore efs then reboot worked for me
Click to expand...
Click to collapse
Already tried that with no luck.
xsenman said:
Check this out
http://forum.xda-developers.com/showpost.php?p=26827676&postcount=4512"
Click to expand...
Click to collapse
Coolio, theres a couple of apps in there that I hadnt come across so Ill defo give them a try at the weekend!

*sigh*
Still no luck with any of those apps.
Im gonna try everything from scratch tomorrow using the original CWM backup I did rather than from the rooted stock I flashed from the guide.
Am I missing something here? It seems that no matter what I try it will always give me a blank IMEI.

It wouldn't be by any chance be a I9000m or b? Probably a stupid question, but you never know.
Using GT-I9000 my sent Tapatalk 2 from.

Did you backup the efs before your first flash, the procedure I have always used is root stock rom copy efs and flash custom rom. Not sure if cwm backs up efs in a nandroid
Sent from my Nexus S using XDA

adytum said:
It wouldn't be by any chance be a I9000m or b? Probably a stupid question, but you never know. .
Click to expand...
Click to collapse
I pretty sure its just a standard I9000, it was Vodafone UK branded before I got my grubby mits on it and I read a guide specifically for the M which lead me to believe it wasnt anything special. When on official GB its just says I9000 still?
thecoogster said:
Did you backup the efs before your first flash, the procedure I have always used is root stock rom copy efs and flash custom rom. Not sure if cwm backs up efs in a nandroid.
Click to expand...
Click to collapse
I only really went of this from the guide:
THIS ROM AUTOMATICALLY SAVES YOUR IMEI FOR RESTORING IN CASE YOU LOSE IT!
after seeing that I took a manual backup of it the /efs as well and every time I flashed with ODIN using the GB flash kit from the guide I checked that the phone side was working then took another backup of it then.
I have several copies of it made from the GB kit, tared in adb and several apps used to back it up.
Your right with the CWM backup though, I read a post that said /efs is a separate partition that doesn't get backup up with CWM
My thinking at the minute is that either Ive missed something related to the branding side of it. I know one DHD I did needed things like a goldcard etc as it was Orange branded or the /efs backups I have have somehow been corrupted.
Now, Im still getting used to the versioning of Samsung FWs. Its currently on
Code:
GT_I9000_XWJW5_XDJV1_OXXJVC_Sbl
is this newer or older than
Code:
CWM ValuePack XXJVU Odex/Deodexed 2.3.6 [06-01-2012]
? It works fine on the first GB one.
Im thinking of flashing the second one today with odin then trying the stock AOKP rom as it doesnt install a kernal but flash Semaphore seperately. All the other ICS roms I tried flash a kernal before hand if that could make a difference?
Man, gotta say this /efs has proper knocked me over. Im not great with non-HTC products lol

Have you tried flashing semaphore.tar from the semaphore ics thread before anything else? It's kind of an all around wonder medicine for flashing issues.
Using GT-I9000 my sent Tapatalk 2 from.

Dude360 said:
Man, gotta say this /efs has proper knocked me over. Im not great with non-HTC products lol
Click to expand...
Click to collapse
remount the EFS folder as read write
Have a look here from one of my earlier posts. It should help.
I can remember that i did have some issues in writing to the EFS folder because it was mounted as read only

still got same problem i keep losig my imei after each reboot...
it comes back if i plugin the charger...
this thing doesnt happend to me when to GB...
i went back to stock and slimICS and this still happends...
every ICS rom gives me same results...

Try this
http://forum.xda-developers.com/showthread.php?t=859914
[HOW TO] /efs Folder backup + Restore NV_DATA.BIN
How I restored the IMEI is in the penultimate post. It workes for me without no problems.

Hello
This is a guide to show you how to restore your 0 IMEI with DFS.
It has worked fine with my IDEOS X5 U8800.
1. Tools
a. Drivers for U800
http://www.sendspace.com/file/9t8no8
ttp://www.sendspace.com/delete/9t8no8/14e9692a8bd3daa4f69e0e738090d4ee
b. Software for restore
http://www.sendspace.com/file/g6thp8
http://www.sendspace.com/delete/g6th...29440decadcf6a
2. Enable debugging by USB in the settings.
In call type * # * # 2846579 # * # * http://postimage.org/image/tnj4s2dyj/
3. Go to ProjectMenu -> Background settings -> Usb port settings put the Manufacture mode and corfim.
4. Go again to ProjectMenu -> Background settings -> Qualcomm backround open settings put the background open. Password 0 and corfim.
5. Go again to ProjectMenu -> Background settings -> Log setting -> Log switch put log on and corfim.
6. Now conect your phone to pc and install the drivers.
You must see this at your device manager http://postimage.org/image/5lrm61agd/
7. Instal DFS and run.
8. Click Ports, select the port with the signature DBAdapter Reserved Interface (double click) to close.
http://postimage.org/image/3l3bmfyzr/
9. In the DM select Qualcomm.
http://postimage.org/image/6bmt1908z/
10) Press the SPC, the bottom will Device Unlocked.
11) Select Programming and in the IMEI write yours and press Write.
http://postimage.org/image/dmbp29q35/
13) Check Imei, may appear after a reboot, if not try a few more times to try to set the port speed to 115200 (box to the left of DM)
Check IMEI *#06#
As soon as the IMEI restored change:
* # * # 2846579 # * # * -> ProjectMenu -> Background settings -> Usb port settings to put on the Manufacture mode google mode (or normal if you do not get up google)
* # * # 2846579 # * # * -> ProjectMenu - > Background settings -> Qualcomm backround open settings put close
Good luck..

OK mate I know this is redundant but flash back to GB if you have efs back it up flash cm9 only cm9 not other ICS ROM then check imei is still right if not restore backup you should now be in the clear to flash other ICS and jb roms this is an issue so many people have
Sent via that ninja standing right behind you

just flash cyanogenmod 9.1.0 stable ...

restore imei Samsung Galaxy S i9000, m110s
Restore only!
Samsung Galaxy S i9000, m110s
(& may be others Galaxy S)
What you need:
1. root access
2. the ability to copy, move files to the phone.
3. about 1-2 days.
4. $ 20
INSTRUCTIONS:
1. Make quality photo sticker under the battery (with the correct imei), as well as photo of incorrect IMEI number on the screen.
Do not use Photoshop. Thus you can damage the gadget )
Short comment how you lose imei.
2. Copy the / efs from the root to sd card or other safe place.
3. From the same folder gat nv_data.bin (with broken imei) and send to [email protected].
4. After recieving corrected copy of nv_data.bin place it in the root /efs
5. Reboot your phone, check the *#06# (If something does not work, you have a backup / efs)
6. Pay $ 20 for z298613675777
7. DO NOT share your corrected nv_data.bin.

EFS folder/IMEI problem

Hi everyone,this is my first post here on xda but i have been observing and following XDA forum for quite a while now,
Now recently I tried to install Origional CM10.2,
Steps i followed were
I had 2.3.4 ( i did installed CM9 almost an year back but then odin back to stock for reasons i dont remember now)
First i Flashed Speedmod kernel via odin 1.7, and then flashed glitch kernel zip using the recovery that came the speedmod kernel,
Wiped devlik cache and went on to install CM10.2,
Everything went fine till i noticed that i was not getting any reception and after googling a bit,identified the problem as efs folder corruption!
I immedietly flashed back to 2.3.4 using oddin and that solved the problem, and my fone was getting the signals on stock 2.3.4,
Following instructions from google, I used EFS recovery softwere to backup my EFS folder,
and then followed the same sequence to flash again to 10.2CM, but here come the tricky part, EFS pro didnt seem to work on CM10.2, i have everything installed perfectly, debugging mode is on, still cant get to restore the efs folder!
I even tried manually copying the backed up EFS folder and putting it in system folder using root explorer etc,but that didnt seem to work, I changed the permission to Read/write aswell, still it says operation failed!
EFS pro was my best hope but it just doesnt work, tried a newer verison of it(newer than the one that i used to backup the efc on GB),that opened but didnt have my device in supported list,and neither was showing any backup!!
This is what i have been doing for past two days
Now I am back to 2.3.4,and IMEI is working fine now.
and additionally just to check whether this happens only on cm10.2 or other versions as well, I flashed Cm10.1 aswell as cm9, same problem there aswell
(As far as i remember ,last year when i flashed CM9,it worked fine but was laggy so i flashed back,only thing i did differently was that i didnt install any kernel)
So any ideas how i should proceed now?
I would thankful if someone can help me ,
and sorry for the long story,i wanted to give as much precise info abt problem as possible!

MUBASHIR888 said:
Hi everyone,this is my first post here on xda but i have been observing and following XDA forum for quite a while now,
Now recently I tried to install Origional CM10.2,
Steps i followed were
I had 2.3.4 ( i did installed CM9 almost an year back but then odin back to stock for reasons i dont remember now)
First i Flashed Speedmod kernel via odin 1.7, and then flashed glitch kernel zip using the recovery that came the speedmod kernel,
Wiped devlik cache and went on to install CM10.2,
Everything went fine till i noticed that i was not getting any reception and after googling a bit,identified the problem as efs folder corruption!
I immedietly flashed back to 2.3.4 using oddin and that solved the problem, and my fone was getting the signals on stock 2.3.4,
Following instructions from google, I used EFS recovery softwere to backup my EFS folder,
and then followed the same sequence to flash again to 10.2CM, but here come the tricky part, EFS pro didnt seem to work on CM10.2, i have everything installed perfectly, debugging mode is on, still cant get to restore the efs folder!
I even tried manually copying the backed up EFS folder and putting it in system folder using root explorer etc,but that didnt seem to work, I changed the permission to Read/write aswell, still it says operation failed!
EFS pro was my best hope but it just doesnt work, tried a newer verison of it(newer than the one that i used to backup the efc on GB),that opened but didnt have my device in supported list,and neither was showing any backup!!
This is what i have been doing for past two days
Now I am back to 2.3.4,and IMEI is working fine now.
and additionally just to check whether this happens only on cm10.2 or other versions as well, I flashed Cm10.1 aswell as cm9, same problem there aswell
(As far as i remember ,last year when i flashed CM9,it worked fine but was laggy so i flashed back,only thing i did differently was that i didnt install any kernel)
So any ideas how i should proceed now?
I would thankful if someone can help me ,
and sorry for the long story,i wanted to give as much precise info abt problem as possible!
Click to expand...
Click to collapse
Were you rooted when you tried to manually restore your efs folder? It should let you change it if you have the right permissions.
I would try to make a manual backup of your efs folder while you're on stock GB and try it again on the ROM you wanna use if you lose your IMEI again. Perhaps try another ROM as well, see if you get the same issue.

I have had problems with losing my imei after flashing to cm10 variants as well. In the steps that I took in this video I didn't lose it and I haven't had anybody else report that they have in the comments.
https://www.youtube.com/watch?v=_hmck9ES6jM

BWolf56 said:
Were you rooted when you tried to manually restore your efs folder? It should let you change it if you have the right permissions.
I would try to make a manual backup of your efs folder while you're on stock GB and try it again on the ROM you wanna use if you lose your IMEI again. Perhaps try another ROM as well, see if you get the same issue.
Click to expand...
Click to collapse
Arent Cyanogen Mods are already rooted?
I used the File explorer that was included in CM10'.2 and in settings i changed its permissions to ROOT ACCES.
Still i cant copy anything to EFS folder.
To be on the safe side,i tried Rooting Cm10..2 with Vroot,one click softwere and it showed that my phone had root Permissions!
Still I CANT WRITE ANYTHING WITHIN SYSTEM FOLDER,root explorer says that I dont have Root permissions, even after i rooted with Vroot!
I am confused

MUBASHIR888 said:
Arent Cyanogen Mods are already rooted?
I used the File explorer that was included in CM10'.2 and in settings i changed its permissions to ROOT ACCES.
Still i cant copy anything to EFS folder.
To be on the safe side,i tried Rooting Cm10..2 with Vroot,one click softwere and it showed that my phone had root Permissions!
Still I CANT WRITE ANYTHING WITHIN SYSTEM FOLDER,root explorer says that I dont have Root permissions, even after i rooted with Vroot!
I am confused
Click to expand...
Click to collapse
I would suggest trying with another file explorer. There are many on the Play Store (I personally like Root Explorer but there are free options).