Hi guys,
I have searched high and low for this issue. I have found a lot of forums on how to fix the problem but none of them pertain to my circumstances. I installed Omega ICS ROM v 13.1 a week or two ago. I then decided to install Omega JB v18. I then upgraded to Omega JB v21 as well. In preparation for the official Samsung JB ROM, I went back to ICS. I started by downgrading to Omega v13.1 ICS followed by stock Samsung ICS ROM I9300XXALE8. A couple of days after doing this, all of a sudden, whilst on a call, I lost signal and then the stop sign icon appeared in the top toolbar. I have no radio, no wifi, no bluetooth and no lock screen & power menu. After all of the reading I have done, I have managed to discover that my EFS has disappeared. I have rooted the phone and installed ES File explorer and have looked inside the EFS folder only to find that it is blank. I did have a Nandbackup but managed to delete it in my attempts to recover my phone (yes I know im stupid but I didnt realise the significance of the backup until I realised what was missing!!). So, no EFS backup. Seemingly nothing in the EFS folder on the phones root. Any help would be greatly appreciated. One thing I did notice, which I am sure is significant in some way, is that when I put Omega JB on it, my sdcard mounted as "sdcard0" or something along those lines. Again, because I am fairly new to the custom ROM world, I didnt realise the significance of this until I had down graded back to ICS.
Please help!!!!
Thanks again.
EFS
http://forum.xda-developers.com/showthread.php?t=1308546
No fix then its a paid for repair .
jje
Have you tried to flash back to stock
JJEgan said:
EFS
http://forum.xda-developers.com/showthread.php?t=1308546
No fix then its a paid for repair .
jje
Click to expand...
Click to collapse
this description:
http://forum.xda-developers.com/showthread.php?t=1264021
should be tried before repair as well...
marcedli said:
this description:
http://forum.xda-developers.com/showthread.php?t=1264021
should be tried before repair as well...
Click to expand...
Click to collapse
Thanks guys...I have tried this one. Didnt work. Just wondering if anyone knows how or if I might be able to restore from sdcard0, if it still exists. I assume not, but I guess it might be something. Does anyone know why Omega JB did that in the first place ?
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
rosshwalker said:
Thanks guys...I have tried this one. Didnt work. Just wondering if anyone knows how or if I might be able to restore from sdcard0, if it still exists. I assume not, but I guess it might be something. Does anyone know why Omega JB did that in the first place ?
Click to expand...
Click to collapse
If you do not have backup of efs folder. You have no chance of getting imei back.
You can go to service centre for rebuilding efs folder.
rosshwalker said:
Thanks guys...I have tried this one. Didnt work. Just wondering if anyone knows how or if I might be able to restore from sdcard0, if it still exists. I assume not, but I guess it might be something. Does anyone know why Omega JB did that in the first place ?
Click to expand...
Click to collapse
Flashing any roms can destroy the EFS thats why its always rule one to backup EFS folder . Multiple flashing up down up down increases the risk .
Did not Omega backup your EFS .
You say
have no radio, no wifi, no bluetooth and no lock screen & power menu
Thats not the signs of IMEI corruption as it plays no part in power menu or lockscreen .
jje
JJEgan said:
Flashing any roms can destroy the EFS thats why its always rule one to backup EFS folder . Multiple flashing up down up down increases the risk .
Did not Omega backup your EFS .
You say
have no radio, no wifi, no bluetooth and no lock screen & power menu
Thats not the signs of IMEI corruption as it plays no part in power menu or lockscreen .
jje
Click to expand...
Click to collapse
I think that S3 has some problem in securing it's EFS folder.
I flashed my S2 with hundred's of roms and never faced this issue.
Secondly in my experience lock screen and power menu is efs folder issue.
muhammad.ali123 said:
I think that S3 has some problem in securing it's EFS folder.
I flashed my S2 with hundred's of roms and never faced this issue.
Secondly in my experience lock screen and power menu is efs folder issue.
Click to expand...
Click to collapse
Read all the SGS2 and one help IMEI /EFS posts i suggest .
lock screen and power menu is efs folder issue >>> If it was a continual factor in the posts regarding EFS/IMEI then i would have agreed .
jje
A reminder about 2 things:
1) swapping/changing/etc IMEI's is illegal
2) giving someone else your EFS folder wont work, your phone will just default to the generic IMEI which is normally no better.
https://play.google.com/store/apps/...GwsMSwxLDEsImNvbS5oZWxyb3ouR1NJSV9SZXBhaXIiXQ..
try this out mate might b it'll help yu...cuz once i rescue cuz of diz app,,,
I wouldn't do that : in gs3 efs is not in the same block as gs2. It'll be worse than before.
Send me your efs partition backup using efs backup pro. I'll tell you if something can be done or not to restore your data.
Sent from my GT-I9300 using xda app-developers app
I had the same issue with my SGS1, the solution was flashing a stock rom with odin.
spocky12 said:
I wouldn't do that : in gs3 efs is not in the same block as gs2. It'll be worse than before.
Send me your efs partition backup using efs backup pro. I'll tell you if something can be done or not to restore your data.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hey. This is one of the things I had read about and tried and it came back with nothing. I don't recall the error message but I think it said it couldn't find the partition or folder or something. I am certain that it has to do with Omega Jb and the fact that it installed and mounted sdcard as sdcard0 and somehow, when going back to omega ics, this has occurred. Another thing I have just now remembered is that I had also setup a swap partition on my ext sdcard and had it mounted. This was all working fine for a few days though so I don't see how that caused it. Was really odd. Anyways, thanks for all the help, but I am going to pay for it to be repaired.
veyka said:
A reminder about 2 things:
1) swapping/changing/etc IMEI's is illegal
2) giving someone else your EFS folder wont work, your phone will just default to the generic IMEI which is normally no better.
Click to expand...
Click to collapse
hmmmm what if he has the IMEI number written somewhere? (phones box or license purchase note), can't he copy the EFS folder from someone else and just edit the IMEI??? >.>
Cruzaders said:
hmmmm what if he has the IMEI number written somewhere? (phones box or license purchase note), can't he copy the EFS folder from someone else and just edit the IMEI??? >.>
Click to expand...
Click to collapse
thats a working solution, he just need someone who shares his efs....
Kies
Have you tried the Kies Restore????? i't worked for me!
marcedli said:
thats a working solution, he just need someone who shares his efs....
Click to expand...
Click to collapse
if it is so easy to edit, it won't have an "e" in the name, would it?
Imei NULL/NULL - EFS Folder Lost.
Hi, I have a i9300 which lost efs folder, already tried restoring it through the box octopus, but at the time of writing the imei, it reports the error. (Write imei fail). Anyone have any idea what I can do?
Hi there.
Hope someone can guide me on this. I've been reading all the posts related to unknown imei, lost efs folder, etc and tried several things to solve the problem, but anything worked out.
The phone got wet with some raindrops (very few raindrops). Warranty was lost because they told me the motherboard was damaged by water. At first the battery exhausted in no time and it didn't charged properly, but a couple of months later everything seems to be all right except that it tells there's no IMEI, and the SIM card isn't read by the phone. Later on I've brought it to another technical service where they've told me the motherboard wasn't damaged, but the SIM connector. They wanted me to pay a big amount of euros for such a little piece. I picked up the phone and decided to investigate by myself.
The actions done to the phone: I fisically opened it and applied a connector cleaning spray; then I upgraded it to ICS and finally rooted it. Then I tried lots of solutions that are posted in the forum, like the GSII_repair, busybox, backup of the efs folder via android-sdk, efs pro, etc.
The only thing about efs that I can read in the phone are two files: an efs.tar.gz and an efs.img.
The efs.tar.gz seems to contain everything needed to restore EFS folder: nv_data.bin, nv_data.bin.md5, etc.
I have no idea how to tidy all this mess up. I know that it's possible that the phone won't work again because of the rain, but I want to sold all the possibilities out before using it only as an ipod galaxy, and I resist thinking that if it was damaged by water the phone woulnd't work ok like it does.
What do I want? Trying to give it its IMEI number again and seeing whether it catches signal. Any idea on how to do that with the files efs.tar or efs.img.
Thank you so much.
Since you have some kind of an EFS backup, then you can use kTool, in the Google Play Store, to restore that backup.
kTool requires root.
Hi and thank you for the reply.
I've downloaded this hc-ktool and tried to restore EFS from backup via efs.tar.gz and via efs.img but anyone worked out. It still says "unknown IMEI". Any idea about why it didn't work?
lespou said:
Hi and thank you for the reply.
I've downloaded this hc-ktool and tried to restore EFS from backup via efs.tar.gz and via efs.img but anyone worked out. It still says "unknown IMEI". Any idea about why it didn't work?
Click to expand...
Click to collapse
Not really, I am still a noob in Android.
Do you have unknown baseband problem? If yes, then try flashing another modem via Odin.
przemcio510 said:
Do you have unknown baseband problem? If yes, then try flashing another modem via Odin.
Click to expand...
Click to collapse
In the baseband section it tells UNKNOWN, as well as the telephone number, IMEI, IMEISW and Bluetooth. D'you think changing the modem will change all the other unknown stuff? I'll try it anyway, thanks.
lespou said:
In the baseband section it tells UNKNOWN, as well as the telephone number, IMEI, IMEISW and Bluetooth. D'you think changing the modem will change all the other unknown stuff? I'll try it anyway, thanks.
Click to expand...
Click to collapse
Nothing to do with the modem. I changed it and everything's still the same.
Still rounding the problem... I installed root explorer and I saw there is an original efs folder in the root of the memory, not in the internal sdcard of the phone. So, what can the problem be? Is the phone really damaged? Or do someone think is only a software matter (is the efs folder corrupted?). Anyone can help?
http://forum.gsmhosting.com/vbb/f258/galaxy-s6-edge-imei-null-null-1960154/
Hi guys,
After dumping the NV data of the i9305 with QPST, i wanted to make sure that i had a valid backup. Like the pessimist i am i took 3 backups to be safe.
I opened a backup in a hex editor and found item 550 (IMEI) changed a value up one digit and re flashed the modified QPST file back to the phone, all went well and the phone rebooted. Dialed *#06# and the change i had made had not "stuck".
Now im concerned that if i do run into any issues down the line i wont be able to fully write back my backup...
Looking around the web it seems the i9305 does store imei and other data elsewhere on the phone, im guessing the modem but have not seem anyone specifically say.
Can anyone shed some light on this please, ive seen some scary stories about null imei's and invalid imeis generated during the use of custom roms and dont want to be banging my head off the wall if faced with these issues myself.
Thanks
You want the I9305 Q&A forum and I9305 Development forum .
jje
Hi
I have searched many threads with regards to missing IMEI and Baseband unknown.
There are many solutions including the 9 step guide and also the app called S2 Repair. I had this problem and i used S2 Repair and it worked a treat. I then used Galaxy S Unlock and that also worked a treat.
However I did a software update via kies and on phone (i wish i never did now) and I am back to no IMEI and Baseband Unknown and S2 Repair no longer works ? After lots of reading i think S2 repair is tring to repair the wrong files ???
My question is this ....... I did not make a back up of my EFS folder before using S2 Repair or Galaxy S Unlock BUT i have got all the files in the EFS folder in the root of the phone EXCEPT (dot).nv_data I DO HAVE nv_dat and (dot).nv_data.bak files
I also have folders in the sd card named S2Repair which has "efs_save.tar" and "efs_save.tar.gz"
WILL I BE ABLE TO USE the files in the S2Unlock folder ?? . In this folder there is the efs folder and these files
"efs_save_for_sgsII.tar"
"efs_save_for_sgsII.tar.gz"
"nv_data.bin"
"nv_data.bin.unlocked"
JUST TO CONFUSE THINGS EVEN MORE I have just found 2 more files on sd card called " efs.img" and efs.tar.gz"
GALAXY I9100, GINGERBREAD XWKI4, 2.3.4 BASEBAND VERSION UNKNOWN, BLANK IMEI
Any help appreciated !!
surferbum said:
JUST TO CONFUSE THINGS EVEN MORE I have just found 2 more files on sd card called " efs.img" and efs.tar.gz"
GALAXY I9100, GINGERBREAD XWKI4, 2.3.4 BASEBAND VERSION UNKNOWN, BLANK IMEI
Any help appreciated !!
Click to expand...
Click to collapse
First and Foremost you are posting this in the wrong forum, so not many can advise you about it, ( will ask MOD to move you to S2 Forum)
But not to worry as long as you have so many backups, you can use them to overwrite your current efs folder or use restore function in S2 Repair and restore the backup. Just for your guidance read this
In fact KIES will auto repair this problem, when you connect to it for updates as ( in most cases) 2.3.4 is old firmwares and have further updates.
Check this out! Links to useful Guides and " Banned " Documentaries
xsenman said:
First and Foremost you are posting this in the wrong forum, so not many can advise you about it, ( will ask MOD to move you to S2 Forum)
But not to worry as long as you have so many backups, you can use them to overwrite your current efs folder or use restore function in S2 Repair and restore the backup. Just for your guidance read this
In fact KIES will auto repair this problem, when you connect to it for updates as ( in most cases) 2.3.4 is old firmwares and have further updates.
Check this out! Links to useful Guides and " Banned " Documentaries
Click to expand...
Click to collapse
Hi
Thanks for the reply and I am sorry for posting in the wrong place.
I did use S2 repair at first and it worked. I also unlocked to tesco PAYG using Galaxy S Unlock. When i did software update and it went blank again S2 repair did not work ?? After reading about efs back up I am worried that if i keep trying s2 repair the old files might be lost forever ??
I am not sure what method to take next !! with been a noob and all !!
I had some major issues after flashing a new rom with latest version of philz advanced recovery...I lost my efs data and all data connectivity... After doing some reading I saw posts saying that flashing stock in Odin would fix my problem quickly and easily...went through that whole process and it fixed my connection...I was then stuck in factory mode and did more reading...according to everything I read I could fix this easily with a file edit...it stated That all I needed to do was navigate with a root explorer app to efs/FactoryApp/factory mode and change off to on...and then to efs/FactoryApp/keystr and also change off to on...easy right...wrong...my efs folder was completely empty...I searched and searched for an answer to my problems for 2 weeks...no luck...I came across many people with jflte and same issue...none ever found successful fix or just never posted it...I did try backing up my efs when I first rooted...but the app I used backed up mmcblk0p3...our efs is located at mmcblk0p10...so my backup was actually for sbl1...awesome...after countless hours of tinkering and reading I came across an old post from a gs2 forum and it did lead me to believe that my efs partition had been formatted to the wrong format to be mountable...after trying every tool I could find to reformat it to ext4...I gave up...I called a Samsung service center and was sending it in to be fixed...they said it would be updated when I got it back...I'm on mdk and was heartbroken to hear this...got a case of the f its and started tinkering more...went back to gs2 thread and someone has posted about an app on play store called gs2_repair...it works...it mounts the partition correctly in ext4 and from there I had to fix permissions or it would unmount on reboot...just following the 2 file edits I talked about previously got me out of factory mode and I was good to go...hope this helps somebody else!
jamesd1085 said:
I had some major issues after flashing a new rom with latest version of philz advanced recovery...I lost my efs data and all data connectivity... After doing some reading I saw posts saying that flashing stock in Odin would fix my problem quickly and easily...went through that whole process and it fixed my connection...I was then stuck in factory mode and did more reading...according to everything I read I could fix this easily with a file edit...it stated That all I needed to do was navigate with a root explorer app to efs/FactoryApp/factory mode and change off to on...and then to efs/FactoryApp/keystr and also change off to on...easy right...wrong...my efs folder was completely empty...I searched and searched for an answer to my problems for 2 weeks...no luck...I came across many people with jflte and same issue...none ever found successful fix or just never posted it...I did try backing up my efs when I first rooted...but the app I used backed up mmcblk0p3...our efs is located at mmcblk0p10...so my backup was actually for sbl1...awesome...after countless hours of tinkering and reading I came across an old post from a gs2 forum and it did lead me to believe that my efs partition had been formatted to the wrong format to be mountable...after trying every tool I could find to reformat it to ext4...I gave up...I called a Samsung service center and was sending it in to be fixed...they said it would be updated when I got it back...I'm on mdk and was heartbroken to hear this...got a case of the f its and started tinkering more...went back to gs2 thread and someone has posted about an app on play store called gs2_repair...it works...it mounts the partition correctly in ext4 and from there I had to fix permissions or it would unmount on reboot...just following the 2 file edits I talked about previously got me out of factory mode and I was good to go...hope this helps somebody else!
Click to expand...
Click to collapse
This is actually really useful information. Im glad you figured this out, a lot of people have this issue and they usually dont ever find a solution (or post it if they did). Using the info you provided perhaps one of us on xda can create an all-in-one solution for this? If I have time ill explore doing this. Good to see people posting things that actually help the community for once.
Surge1223 said:
This is actually really useful information. Im glad you figured this out, a lot of people have this issue and they usually dont ever find a solution (or post it if they did). Using the info you provided perhaps one of us on xda can create an all-in-one solution for this? If I have time ill explore doing this. Good to see people posting things that actually help the community for once.
Click to expand...
Click to collapse
Great!...I had hoped so...that's why I posted because it took two weeks of searching to figure out because there was no fix for our s4 so I tried a combo of many different fixes and lucked into something that actually worked...lol
didn't work for me