Hi,
I have managed to lose my IMEI and empty my /efs folder. I was using the Gingerbread Beta 2 ROM provided by Whitehawkx on my Samsung Vibrant. Everything was great for me, I was loving it and was using it as daily driver. Until one day, my cell was in my pocket and I realized it was overheated. I removed it from my pocket and saw that it was frozen and had the double rainbow screen. I removed the battery to switch it off and restarted.
Since that moment, I lost all the files under my /efs folder and also lost my IMEI. As a result my phone does not recognize any SIM card. I can use all other functions like wifi, bluetooth, etc. but cannot use any phone functions like calling, sms, etc.
Please please please help me out to resolve this problem. I do not have backup of my /efs folder. I do have nandroid backups of my JFD, JI6 and KA6 ROMs. (if that helps in any way)
I have already tried going back to Stock JFD with clear efs checkbox checked using odin but no luck...
Please Help & Very Thanks in advance...
P.S. Let me know if you need any more details...
This is tricky, but it can be done, I am not sure how much your phone is jacked up. But here is a link explaining how to do this, read carefully a few times before you proceed:
http://forum.xda-developers.com/showthread.php?t=881162
Good luck
oka1 said:
This is tricky, but it can be done, I am not sure how much your phone is jacked up. But here is a link explaining how to do this, read carefully a few times before you proceed:
http://forum.xda-developers.com/showthread.php?t=881162
Good luck
Click to expand...
Click to collapse
Thanks oka1,
But before your reply I did something because of which I am screwed even more
While trying out everything, I flashed my Vibrant with the International Samsung Galaxy S ROM - 'I9000DDJF2'. I also used the CSC file that came with it.
This did not solve my IMEI problem but then now I can't go into Download mode or recovery mode as we do not have the home key that International Galaxy S has.
Please help me get in Download mode or Recovery mode so that I can get back to Vibrant ROM.
we do have a home button. use that to go to DL mode.
how come did that messed up your eds? was it told that you need to backup your efs folder?
Sent from my SGH-T959 using XDA App
Got lucky, managed to get into Download mode. Found this post 'http://forum.xda-developers.com/showthread.php?t=728698', the key was - "If you still can't enter download mode, you may want to try holding down the volume key + the power button. Plugging in your USB cable may also aid your efforts to enter download mode."
But this does not solve my lost IMEI and /efs problem. I did not know about backing up the /efs folder :-(
I am trying my hardest to try and restore my IMEI...
just get a replacement. that's the easiest way I think.
is your phone unlocked?
Sent from my SGH-T959 using XDA App
Hey Im looking now through some old threads, might have a fix.
I did that too, but luckily, after that, i bricked.
Backing up /efs will avoid any problems like this?
Potential Fix
I attached a screenshot of the files that should be in your efs folder. When I unlocked my phone, it required deleting all of the nv files besides the log, which leaves -
The .android folder is empty
The .imei file contains your imei number (found under your battery - put it in without slashes)
The imei folder which contains bt.text with your bluetooth mac address and a code file with the word XEN
I would recommend ODIN back to stock, root, set up this file structure (leaving out the nv files), then download the sgs unlock tool, and run it. People have reported success using the unlock tool to rebuild nv_data.
If this fails try reading through this thread - http://forum.xda-developers.com/showthread.php?t=879189&page=3
Thanks guys for helping out...
@iynfynity - My phone is unlocked. I can't get replacement since I am not in US. I bought it from ebay.com.
@pvspencer22 - I will try the way that you have mentioned. I thought since I am not in US, I can request someone from US to share their /efs folder contents. A nice guy from xda was ready to do that but then he was not comfortable :-(
Ya I wasn't to comfortable with it. It just doesn't seem safe for me to give someone else my IMEI. And plus I dont think it would work on your phone anyways, because the efs file wouldn't match your phone
Sent from my SGH-T959 using XDA App
pvspencer22 said:
I attached a screenshot of the files that should be in your efs folder. When I unlocked my phone, it required deleting all of the nv files besides the log, which leaves -
The .android folder is empty
The .imei file contains your imei number (found under your battery - put it in without slashes)
The imei folder which contains bt.text with your bluetooth mac address and a code file with the word XEN
I would recommend ODIN back to stock, root, set up this file structure (leaving out the nv files), then download the sgs unlock tool, and run it. People have reported success using the unlock tool to rebuild nv_data.
If this fails try reading through this thread - http://forum.xda-developers.com/showthread.php?t=879189&page=3
Click to expand...
Click to collapse
I tried these ways, no luck :-( Seems that the only possible way to resolve this is if someone agrees to share the contents of /efs folder of a working spare vibrant phone. But then no one is ready to do this...
Wonder if it could be possible for YOU to give your information from your phone & battery to someone on here that could make edits to their files with your info and send it to you??
jmcghee1973 said:
Wonder if it could be possible for YOU to give your information from your phone & battery to someone on here that could make edits to their files with your info and send it to you??
Click to expand...
Click to collapse
Not a bad idea
Sent from my GT-I9000 using XDA App
My original IMEI was 351801041232857.
My phone model is TMo Samsung Vibrant, I bought it from ebay.com.
Not sure what other details would be required as the only thing different is the IMEI, rest would be just as any other Vibrant phone.
Currently I am on stock JFD (downloaded from xda) and my /efs folder is completely empty.
Guys, please let me know if any other information is needed. I would be more than obliged to provide it. I am just trying out all possible ways to resolve the problem and I deeply appreciated each and every message coming my way... This is what makes xda so special...
As I have said, my handicap is that I am not in US, else I could have easily asked T-Mobile to solve this problem for me...
FATEOWNZYOU said:
Ya I wasn't to comfortable with it. It just doesn't seem safe for me to give someone else my IMEI. And plus I dont think it would work on your phone anyways, because the efs file wouldn't match your phone
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
I have nothing against you mate, you were just trying to help... I have completely understood your concern...
About the second part whether it would work or not, we need to try it first to figure out whether it works out or not. That is why we are here... trying to help each other out...
Guys, someone please help me out with /efs folder contents of a spare Vibrant phone...
kisfit2000 said:
Guys, someone please help me out with /efs folder contents of a spare Vibrant phone...
Click to expand...
Click to collapse
reply if you still need help. I got a solution as long as you have the backup efs folder.
iynfynity said:
reply if you still need help. I got a solution as long as you have the backup efs folder.
Click to expand...
Click to collapse
Thats the main problem, i do not have backup of my efs folder. My efs folder is empty and hence I am requesting someone to share their efs folder contents :-(
I need a vounteer helper who can share his efs folder contents...
Please...
Sorry for noob question..
what's the best way to edit a build prob in a rom before you install it? plus would the zip then need to be resigned in anyway before you could install it?
any help much appreciated, cheers
open zip, copy the file, open with wordpad, edit, paste into zip
thanks. does that then need to be signed to load properly without sending into bootloop?
u only need a rooted phone and a file manager with root(superuser) accesss. edit the file as a normal text file. be careful while u do it though. u can brick ur device if u arent!
Hi guys i know there are other so many solutions and threads out there but i could not get any of those to work, i have my efs folder backup .nv_data.bak, .nv_core.bak, .nv_data.bak.md5. Nothing i have tried has so far works ill attach the backed up efs folder here so someone can have a look at it. If anyone out there can give me some help i would give a very generous donation for their work. I have tried (9 step, hcktool, sgsII_repair) you name it. thank you for any contributions.
mrpsycho said:
Hi guys i know there are other so many solutions and threads out there but i could not get any of those to work, i have my efs folder backup .nv_data.bak, .nv_core.bak, .nv_data.bak.md5. Nothing i have tried has so far works ill attach the backed up efs folder here so someone can have a look at it. If anyone out there can give me some help i would give a very generous donation for their work. I have tried (9 step, hcktool, sgsII_repair) you name it. thank you for any contributions.
Click to expand...
Click to collapse
First of all take down the efs... its not safe to share I believe... second for hcktool what did you do?
You tried with this?
https://play.google.com/store/apps/details?id=net.hellcat.droiddev.ktool
Sent from my GT-I9100 using Tapatalk 2
mrpsycho said:
Hi guys i know there are other so many solutions and threads out there but i could not get any of those to work, i have my efs folder backup .nv_data.bak, .nv_core.bak, .nv_data.bak.md5. Nothing i have tried has so far works ill attach the backed up efs folder here so someone can have a look at it. If anyone out there can give me some help i would give a very generous donation for their work. I have tried (9 step, hcktool, sgsII_repair) you name it. thank you for any contributions.
Click to expand...
Click to collapse
As stormtroopercs said, remove your efs backup from the forum, not coo!l
You've obviosly tried most tools available to rectify your problem!
1: Backup your original efs folder to somewhere safe!
2: Then try using root explorer from the market, ( a bit like the 9 step repair but a slight variation! )
3: Open it & navigate to your original efs folder!
4: Delete your "nv_data.bin" & "nv_data.bin.md5" files!
5: Then ( WHILST STILL IN YOUR ORIGINAL EFS FOLDER!! ) rename your "nv_data.bak" & "nv_data.bak.md5 to -> "nv_data.bin" & "nv_data.bin.md5"
Reboot & hopefully problem solved!
But if not, then at this stage you really have nothing else to lose! :good:
Here's another similar guide: http://www.youtube.com/watch?v=JqLK_2I-SBM
The method I gave you has worked for me in the past on my older Nexus S, but can also be used for the Galaxy S2!!
Ive tried to use all the guides interms of renaming files as you suggested it didnt work out quite so well. Also that video was for galaxy S and not S2 ;( s2 still not functional. Also i have tried HCKtool to restore it, that didnt work either. Using the efs files that are in there now.
I have taken down my efs as you suggested too.
Hi,
I'd like to edit a dictionary - add much more words. I know where is the user dictionary (data/data/com.android.providers.userdictionary/databases/user_dict.db) and I've tried to edit it with SQLite Manager (Addon for firefox - couldn't find something better while searching google for 5 seconds) but with no effect - when I tried to export it as a .db and open again, it shows database is corrupted :crying:
Can anyone tell me step by step how to and with which program may I edit dictionary?
Thanks in advance :cyclops:
@refresh
I dont think manually editing that db would be possible so easiest thing, create a blank Dictionary, add the words you want from Rom, then copy over the .db file
from Rom
Click to expand...
Click to collapse
You mean writing it by phone? It may take to much time :x
Sorry mate Im afraid my previous response was wrong ;( As it turns out, the db file is encrpyted with the rom. If you install another rom, I believe it wont work again Not sure, If someone could confirm, could be nice