The problem is I can't get my IMEI back after updating to JB, Phone was rooted successfully and after that I tried to found /EFS folder but there is no such folder at all.
Is there any way to restore the original IMEI/EFS-folder?
Thanks.
stbunny said:
The problem is I can't get my IMEI back after updating to JB, Phone was rooted successfully and after that I tried to found /EFS folder but there is no such folder at all.
Is there any way to restore the original IMEI/EFS-folder?
Thanks.
Click to expand...
Click to collapse
Have you tried *#60#?
Well it seems you're in a serious issue. Loosing IMEI would kill your network activities. Try restoring the original stock Firmware from LG. That should solve the problem.
Good luck.
Related
Hi,
I have a backup of my EFS folder which I did it with EFS Pro.
The problem is that on a ROM flash I've lost my IMEI, and now when I try to restore it it's not detecting the root on my phone, while a new version of EFS Pro finds it rooted, but does not see the backup.
I tried copying and overwriting the files manually but that didn't work.
'?
Thinking on not using my backup what alternative I have to make it work and recover back my IMEI?
I don't want to take it to Samsung, because in my country the tech support is a disaster and keeps your phone for a week and they are too expensive without sense (And I doubt their technical skills)
Thanks!
Flash the original stock rom
JJEgan said:
Flash the original stock rom
Click to expand...
Click to collapse
I tried that and it didn't work :S
The IMEI is still the generic one :S
follow link in my sig to sticky roll-up. Read imei / efs
Hi,
I used Android 4.1.2 and CM10.1 - on Samsung Galaxy S II model I9100.
During a phone conversation it was hanged up, and the phone could not connect to the network anymore.
I got an error when tried to manually search for network operator, which lead me, after a research in the net, to find out that the IMEI of the phone is empty. I see also that the Baseband version is 'unknown'.
I have a backup of the efs folder and tried to restore it by manual overwrite it - with no success.
I also followed the guide to recover manually the IMEI from here: http://forum.xda-developers.com/showthread.php?t=1264021 with no success.
I tried to get back to a backup of the original ROM I used before (this time using ODIN), and now I get NULL/NULL in the IMEI and I still get Baseband 'unknown'.
Also re-installing the radio did not help. now when looking for network operator the error is different - now it is telling me that there is no SIM card.
the NULl/NULL IMEI and Baseband version is 'unknown' are still here and I still can't connect to the network.
last input: after 2 days of phone being unused - it suddenly got back to work, the original IMEI got back in, and it connected to the network. this happened without me doing anything, and it held for half a day, then the phone got back to the non-functioning mode as described above, again in the middle of a phone conversation.
I am out of new ideas, all related threads in here did not help.
Can anybody help ?
Does anybody know the reason for this issue?
Can tell what is the thing that is probably corrupted, and in case that the problem is with the files in efs folder - why doesn't a restore of the efs folder (including chown for nv_data.bin to user radio) did not help?
Thanks !
-- Amit.
amita74 said:
Hi,
I used Android 4.1.2 and CM10.1 - on Samsung Galaxy S II model I9100.
During a phone conversation it was hanged up, and the phone could not connect to the network anymore.
I got an error when tried to manually search for network operator, which lead me, after a research in the net, to find out that the IMEI of the phone is empty. I see also that the Baseband version is 'unknown'.
I have a backup of the efs folder and tried to restore it by manual overwrite it - with no success.
I also followed the guide to recover manually the IMEI from here: http://forum.xda-developers.com/showthread.php?t=1264021 with no success.
I tried to get back to a backup of the original ROM I used before (this time using ODIN), and now I get NULL/NULL in the IMEI and I still get Baseband 'unknown'.
Also re-installing the radio did not help. now when looking for network operator the error is different - now it is telling me that there is no SIM card.
the NULl/NULL IMEI and Baseband version is 'unknown' are still here and I still can't connect to the network.
last input: after 2 days of phone being unused - it suddenly got back to work, the original IMEI got back in, and it connected to the network. this happened without me doing anything, and it held for half a day, then the phone got back to the non-functioning mode as described above, again in the middle of a phone conversation.
I am out of new ideas, all related threads in here did not help.
Can anybody help ?
Does anybody know the reason for this issue?
Can tell what is the thing that is probably corrupted, and in case that the problem is with the files in efs folder - why doesn't a restore of the efs folder (including chown for nv_data.bin to user radio) did not help?
Thanks !
-- Amit.
Click to expand...
Click to collapse
EFS is corrupt.This was a bomb waiting to explode.I suggest you to go back to stock JB 4.1.2 ROM (see my signature),and flash Apolo kernel.Go to recovery and restore backup.Do not overwrite it manually.Do it in Recovery.
New inputs
GamingDj said:
EFS is corrupt.This was a bomb waiting to explode.I suggest you to go back to stock JB 4.1.2 ROM (see my signature),and flash Apolo kernel.Go to recovery and restore backup.Do not overwrite it manually.Do it in Recovery.
Click to expand...
Click to collapse
Hi GamingDj,
First thanks for the reply.
I want to add more inputs and few questions:
Right now, after more then another day that the phone was not functioning - it got back to operate again, and again, without me doing anything that will cause that to happen.
During the last time that it happened, this held the pone in a working state for about half a day until it hanged up on me during a phone conversation I had - and the phone stopped working again, so I am not very optimistic about the phone getting back to work for good right now....
I have a bit more data that I forgot to mention before:
1. About a day before this problem happened, Avast anti virus offered me to update the Avast Anti theft software, this required root access and I don't know if it has something with the reported problem or not.
2. The efs folder was "handled" by GalaxSim Unlock, after the phone got locked due to official upgrade to JB. Originaly this was an O2 locked phone, then it was unlocked with a code, but due to the upgrade to JB it got SIM locked again and the codes did not work anymore, which caused me to use the GalaxSim Unlock application - that indeed unlocked my phone. I know that the GalaxSim Unlock application changed some data in the nv_data.bin in efs folder, but after it unlocked my phone it was working fine for about a month or more, so I can't tell that this is the cause for the suspected corruption in the efs folder.
I have both backup of the efs folder before and after the unlock operation by GalaxSim unlock application.
Can you explain in more details:
1. Why you suggest to flush Apolo kernel? is it in order to have the phone rooted? can you give a link for this kernel?
2. Restore backup from where? should I have a backup file that you point to? not sure what backups I have that may have data that I don't already use.
3. Does the new data help with debugging this issue?
Thanks again.
-- Amit.
amita74 said:
Hi GamingDj,
First thanks for the reply.
I want to add more inputs and few questions:
Right now, after more then another day that the phone was not functioning - it got back to operate again, and again, without me doing anything that will cause that to happen.
During the last time that it happened, this held the pone in a working state for about half a day until it hanged up on me during a phone conversation I had - and the phone stopped working again, so I am not very optimistic about the phone getting back to work for good right now....
I have a bit more data that I forgot to mention before:
1. About a day before this problem happened, Avast anti virus offered me to update the Avast Anti theft software, this required root access and I don't know if it has something with the reported problem or not.
2. The efs folder was "handled" by GalaxSim Unlock, after the phone got locked due to official upgrade to JB. Originaly this was an O2 locked phone, then it was unlocked with a code, but due to the upgrade to JB it got SIM locked again and the codes did not work anymore, which caused me to use the GalaxSim Unlock application - that indeed unlocked my phone. I know that the GalaxSim Unlock application changed some data in the nv_data.bin in efs folder, but after it unlocked my phone it was working fine for about a month or more, so I can't tell that this is the cause for the suspected corruption in the efs folder.
I have both backup of the efs folder before and after the unlock operation by GalaxSim unlock application.
Can you explain in more details:
1. Why you suggest to flush Apolo kernel? is it in order to have the phone rooted? can you give a link for this kernel?
2. Restore backup from where? should I have a backup file that you point to? not sure what backups I have that may have data that I don't already use.
3. Does the new data help with debugging this issue?
Thanks again.
-- Amit.
Click to expand...
Click to collapse
Follow my guide to flash ICS official.Then root and sim Unlock it(if needed).Then flash Apolo kernel via Recovery.In apolo kernel Recovery go to EFS menu,and click restore.Now restore your backup.
status update
GamingDj said:
Follow my guide to flash ICS official.Then root and sim Unlock it(if needed).Then flash Apolo kernel via Recovery.In apolo kernel Recovery go to EFS menu,and click restore.Now restore your backup.
Click to expand...
Click to collapse
Hi,
Just want to update that its been about a week that the phone works without me doing anything, therefore not proceeding with the recovery process you suggested.
I will update if the problem will be back.
Thanks.
Hi there I have a I9300 (International Version) of S3
So I'm just getting straight to the point
I had bought a s3 from a private seller from ebay and it was running 4.1.2.
I have a bit of experience in using Odin and I had downloaded some UK BTU android 4.3 version from sammobile.com which I usually use to update my phone.
But today if went wrong
I never did root because I never did like it and never made an efs backup
I had flashed I9300XXUGMK6_I9300OXAGMK6_I9300XXUGMK6_HOME.tar.md5 file to my phone and everything went perfectly fine
BUT THEN!
I tried calling some of my friends and I noticed that my sim wasn't being recognised
It didn't take long until I realised that my IMEI number had been to some random 0049***** number (I had found out that this was generic and was'nt my real IMEI Number)
I had then checked the IMEI number on the back of the phone and it did not match what was said in my phone settings
I have now clocked that it was the 4.3 android which was screwing me up
I have never installed any custom roms .etc and have only ever installed official ones from sammobile
So why would my phone's EFS get f***ed up and I also did'nt do any in Odin like phone efs clear
My phone had also ran out of warranty so I can't play dumb either
I have researched and found that it is possible to edit the nv_data file.etc like on http://forum.xda-developers.com/showthread.php?t=1804117
I have also tried downgrading but now odin wont allow but probably has something to do with samsung (downgrading policy)
I have also NOW made a backup of my efs folder and my phone is fully functional but my IMEI AND my SERIAL NUMBER was changed
Be honest do I have a realistic chance of recovering my phone or would I have to shell out of repairs and if so how much would it cost?
@mizzeeboy,
Try this?
~ RazorMC
Hey
U can try this too http://forum.xda-developers.com/showthread.php?t=2544109
RazorMC said:
@mizzeeboy,
Try this?
~ RazorMC
Click to expand...
Click to collapse
I have unfortunately tried this and I have realised that some of the phone data in the s2 is different compared to the s3
Also just one question if I could downgrade back to 4.1 would I get my IMEI back?
mizzeeboy said:
I have unfortunately tried this and I have realised that some of the phone data in the s2 is different compared to the s3
Also just one question if I could downgrade back to 4.1 would I get my IMEI back?
Click to expand...
Click to collapse
Sorry for the wrong link.
Maybe this?
- Try to reflash latest 4.3 for your country (this will most likely solve the issue if your efs is not broken)
- You can also try the methods in the link (there are many)
In my limited experience; downgrading to 4.1.2 after 4.3 gave me bootloop and it can't read efs2 (from 4.3)
~ RazorMC
Flash this modem through Odin (http://www.mediafire.com/download/s79zs955sok085h/modem.bin) it's MK6, it should fix the problem for you.
Saad_ said:
Flash this modem through Odin (http://www.mediafire.com/download/s79zs955sok085h/modem.bin) it's MK6, it should fix the problem for you.
Click to expand...
Click to collapse
Thanks I have tried this before and I have unfortunately failed along with your same file.
Hi
Im really hoping someone can help me here. I have a samsung GT-I9300 the battery has been failing and recently it stopped booting.
I couldnt do anything with it tried using KIES but it didnt recognise the device.
I couldnt not get into it at all so did not back up the EFS folder.
I then had it working with 4.3 after alot of trial and error regarding the PIT file and creating a new partition.
I then reverted to 4.1.2 to try to upgrade it via KIES again but it still doesnt get recognised.
I now have the actual phone working but it cannot make calls as the imei number is 004999010640000/01.
I have a note of the correct imei but cannot change it is there anything i can do to fix this,as i mentioned i do not have a backup of the efs folder.
Any help is much appreciated im pulling my hair out with this.
baldrat61 said:
Hi
Im really hoping someone can help me here. I have a samsung GT-I9300 the battery has been failing and recently it stopped booting.
I couldnt do anything with it tried using KIES but it didnt recognise the device.
I couldnt not get into it at all so did not back up the EFS folder.
I then had it working with 4.3 after alot of trial and error regarding the PIT file and creating a new partition.
I then reverted to 4.1.2 to try to upgrade it via KIES again but it still doesnt get recognised.
I now have the actual phone working but it cannot make calls as the imei number is 004999010640000/01.
I have a note of the correct imei but cannot change it is there anything i can do to fix this,as i mentioned i do not have a backup of the efs folder.
Any help is much appreciated im pulling my hair out with this.
Click to expand...
Click to collapse
What version android do you currently have on it? You basically need 4.3 or higher.
If that doesn't solve your issue you will need to take it to a repair center.
http://forum.xda-developers.com/showthread.php?t=2393289
I currently have 4.1.2 im on the ee service in the uk but am unsure which 4.3 i need
Since you upgraded your efs your early 4.1.2 cannot read it.
Read that link I gave you. Your need a 4.3 rom or modem XXEMG4or newer.
Here is a 4.3 rom for you.
http://www.sammobile.com/firmwares/1/?model=GT-I9300&pcode=EVR#firmware
No joy all works but i still have the stock imei number,i dont seem to be able to flash without a pit file using this each time make a difference?
baldrat61 said:
No joy all works but i still have the stock imei number,i dont seem to be able to flash without a pit file using this each time make a difference?
Click to expand...
Click to collapse
What does odin say when it fails?
It doesnt fail it installs it but the imei number remains the same
baldrat61 said:
It doesnt fail it installs it but the imei number remains the same
Click to expand...
Click to collapse
Opps It seems I didn't read it properly.
If the 4.3 flashed ok and you still have generic imei then you need to take it to a service center for repair.
A while back i decided to downgrade my stock 4.3 to 4.1.1 in order to try to unlock it from carrier... the thing is i lost my IMEI and Serial Number
The good news is i have a backup of my EFS folder (only copy-paste with "root explorer" app though... no ".img" file sadly), but I understood that the most important file is "nv_data.bin"
So... my problem seems to be like this: http://forum.xda-developers.com/gala...ackup-t2544109
but only the last step (put back the nv_data.bin, delete backups of bad nv_data.bin, reboot and magic)
The sad part: it doesn't resolve anything because everytime I reboot the phone it recreates the "nv_data.bin" even if I restore the original one (the one i had before downgrading)
Can anyone help me please ?
I have also tried as seen in other posts to change it's owner into radio:1001, unfortunately it still recreates the file after reboot.
I am currently trying to go back on 4.3 to try to restore the nv_data.bin on that verison (but i don't think it has anything to do with the android version)
Anyone encountered this problem or knows a solution ? Thank you ! :angel:
scratcher1337123 said:
A while back i decided to downgrade my stock 4.3 to 4.1.1 in order to try to unlock it from carrier... the thing is i lost my IMEI and Serial Number
The good news is i have a backup of my EFS folder (only copy-paste with "root explorer" app though... no ".img" file sadly), but I understood that the most important file is "nv_data.bin"
So... my problem seems to be like this: http://forum.xda-developers.com/gala...ackup-t2544109
but only the last step (put back the nv_data.bin, delete backups of bad nv_data.bin, reboot and magic)
The sad part: it doesn't resolve anything because everytime I reboot the phone it recreates the "nv_data.bin" even if I restore the original one (the one i had before downgrading)
Can anyone help me please ?
I have also tried as seen in other posts to change it's owner into radio:1001, unfortunately it still recreates the file after reboot.
I am currently trying to go back on 4.3 to try to restore the nv_data.bin on that verison (but i don't think it has anything to do with the android version)
Anyone encountered this problem or knows a solution ? Thank you ! :angel:
Click to expand...
Click to collapse
It as everything to do with the android version.On 4.3 your efs is v2 when you downgrade to below that your phone can't read anything because it is efs v1. Unless your backup was taken while you where on efsv1 then there is no way of restoring it you need to be on 4.3 and above. Also when restoring efs that are backed up via a root explorer you have to make sure every permission is correct when you paste the files back. Hope that helps.[emoji1]
will try it the next days, currently i am pretty busy, thank you, i will let you know how it went... didn't knew efs has versions
Thank you !
P.S. Yes i have backed up the EFS from 4.3, now i was trying it to repair it on 4.1.1, I will try to restore it on 4.3 again ! Hopefully it will work
scratcher1337123 said:
will try it the next days, currently i am pretty busy, thank you, i will let you know how it went... didn't knew efs has versions
Thank you !
P.S. Yes i have backed up the EFS from 4.3, now i was trying it to repair it on 4.1.1, I will try to restore it on 4.3 again ! Hopefully it will work
Click to expand...
Click to collapse
I have the same problema, but I dont have the backup , can you delivery the rom 4.1.1..
thanks ...
If you didn't backup the efs folder then take it to a repair centre, there is no other way to fix it.
Make sure it works on 4.3 before you pay them.
i flashed a friends CWM backup file on my s3 and i lost imei and network mine was 4.1.2 the backup was 4.3 now i reflashed the phone with a 4.3 firmware from sammobiles. i am getting the signal bars but the phone woudnt register on any network and when i take service mode (*#0011#) ath the bottom it says IMEI CERTI : FAIL, what should i do please help me
If flashing 4.3 firmware and factory reset didn't restore imei then take it to a repair centre.