Hi there,
Something very strange has appears to my Nexus S.
It's been more than one year that my phone works perfectly with ICS 4.04 flashed by recovery and ROM stock, I've never reflashed my phone since this day.
Then two days ago, no more GSM network, can't pass any call or text, but data in WCDMA works perfectly.
I've tried :
- Factory reset
- Cyanogen Mod last ROM
- Tried my SIM card on the Nexus S of a friend --> works perfectly
- Tried my friend SIM card on my phone --> same issues, no GSM but data works in WCDMA
I've search a lot on google and XDA, and I've discovered what was IMEI and /efs.
But it's too late for me, my IMEI is the cursed generic IMEI, not the one written behind my battery.
I've tried to flash with stock ROM Stock Android 2.3.6 (GRK39F) with Odin because I've read that it could retrieve my original IMEI. There was no .md5 file inside so I can't flash it with Odin, else I've flash it with ADB / Fastboot.
Phone start and GSM mobile works !
But I got generic IMEI yet, and data is stuck on edge, no WCDMA.
I was thinking it was caused by the old ROM radio flashed with ROM Stock Android 2.3.6 (GRK39F).
So I've flash using recovery the latest Cyanogen and ROM radio KB3 (which was working great in WCDMA for me before all this mess).
No change, GSM works, but data network is stuck in Edge, even if I force WCDMA in *#*#4636#*#* menu, it keep staying in edge.
I don't understand all of this, but I think this is again link to this generic IMEI.
My /efs folder is not empty, I have nv_data.bin but file is dated from yesterday and I can't find any backup like ".nv_data.bin" or "nv_data.bin.bak".
This story seems to be classic in XDA forum, but it's really difficult for me to find a solution, especially for a Nexus S.
This phone is pretty old, you guys are experienced with it and I really need your help, I like this phone and I don't want to change it =(
Is there any way to regenerate my original IMEI ?
Maybe I'll try a flash with Odin and 2.3.4 GRJ22, I never tried Odin, but it seems sometimes to solve the problem. Do you think it could work ?
I really need your help guys, I'm so sad : /
Thanks for reading this, and thanks again if your reply.
hey man,
sorry to hear that...
have you tried to use your sim on another phone? the phone is 2 years old and possibly the problem is from the simcard\network.
another option is to check weather your APN's are as supposed to be.
you can check online or via customer service.
sheeen said:
Hi there,
Something very strange has appears to my Nexus S.
It's been more than one year that my phone works perfectly with ICS 4.04 flashed by recovery and ROM stock, I've never reflashed my phone since this day.
Then two days ago, no more GSM network, can't pass any call or text, but data in WCDMA works perfectly.
I've tried :
- Factory reset
- Cyanogen Mod last ROM
- Tried my SIM card on the Nexus S of a friend --> works perfectly
- Tried my friend SIM card on my phone --> same issues, no GSM but data works in WCDMA
I've search a lot on google and XDA, and I've discovered what was IMEI and /efs.
But it's too late for me, my IMEI is the cursed generic IMEI, not the one written behind my battery.
I've tried to flash with stock ROM Stock Android 2.3.6 (GRK39F) with Odin because I've read that it could retrieve my original IMEI. There was no .md5 file inside so I can't flash it with Odin, else I've flash it with ADB / Fastboot.
Phone start and GSM mobile works !
But I got generic IMEI yet, and data is stuck on edge, no WCDMA.
I was thinking it was caused by the old ROM radio flashed with ROM Stock Android 2.3.6 (GRK39F).
So I've flash using recovery the latest Cyanogen and ROM radio KB3 (which was working great in WCDMA for me before all this mess).
No change, GSM works, but data network is stuck in Edge, even if I force WCDMA in *#*#4636#*#* menu, it keep staying in edge.
I don't understand all of this, but I think this is again link to this generic IMEI.
My /efs folder is not empty, I have nv_data.bin but file is dated from yesterday and I can't find any backup like ".nv_data.bin" or "nv_data.bin.bak".
This story seems to be classic in XDA forum, but it's really difficult for me to find a solution, especially for a Nexus S.
This phone is pretty old, you guys are experienced with it and I really need your help, I like this phone and I don't want to change it =(
Is there any way to regenerate my original IMEI ?
Maybe I'll try a flash with Odin and 2.3.4 GRJ22, I never tried Odin, but it seems sometimes to solve the problem. Do you think it could work ?
I really need your help guys, I'm so sad : /
Thanks for reading this, and thanks again if your reply.
Click to expand...
Click to collapse
Still nothing,.. Sorry you haven't got this resolved yet.. Hopefully some fresh eyes here can make short work of it..
Thanks for your reply guys.
I've tried the sim in another phone and it works great, the real problem is generic IMEI I guess.
Thanks for your help and your link in PM Setting Out, I think I'll try the second one.... the first can't work with me because my /esf and /data/radio does not have an old backup of nv_data.bin.
I have two questions please :
- How the holy s*** this thing can happen randomly after ONE YEAR of fully founctional phone ? (not a single flash since one year)
- How can it be so ramdom ? I mean, before rom stock flash, GSM does not work but I was having Data (WCDMA). Now, After rom stock flash, GSM is working but Data is stuck in Edge. I can't understand how IMEI can impact such randomly issues.
Well, as you know the IMEI is sent to your operator as long as you have signal.
if the operator doesn't get a valid one problems may occur.
In order to find out if this really is a EFS problem go into /data/radio/log and cat the nv.log, find a line like this:
MD5 fail. orignal md5 '84373eddf2a1617f795b1c1af650f8a784373eddf2a1617f795b1c1af650f8a7' computed md5
'3eddf2a1617f795b1c1af650f8a7' (rild)
put the phone in airplane mode then use a unix text editor and manualy edit nv_data.bin.m5d and make sure the string of numbers is equal to the string after "computed md5" (in this case 3eddf2a1617f795b1c1af650f8a7) save the file take the phone out of airplane mode then reboot check the IMEI with the *#06#
Thanks a lot for your reply.
I have /data/radio/log/nv.log file.
But I have no checksum in this file, only text like "/data/radio/nv_data.bin does not exist."
This is strange because /data/radio/nv_data.bin file exist.
But in /efs folder, I have a nv.log file too, and in this file I have some checksum.
Any way to do something with this one ?
EDIT : I've tried the manipulation with /efs folder, it does not change my generic IMEI =(
Sure, I verified permissions and owner of file.
sheeen said:
Thanks a lot for your reply.
I have /data/radio/log/nv.log file.
But I have no checksum in this file, only text like "/data/radio/nv_data.bin does not exist."
This is strange because /data/radio/nv_data.bin file exist.
But in /efs folder, I have a nv.log file too, and in this file I have some checksum.
Any way to do something with this one ?
EDIT : I've tried the manipulation with /efs folder, it does not change my generic IMEI =(
Sure, I verified permissions and owner of file.
Click to expand...
Click to collapse
Here are some detailed steps
Ensure you have one good copy of nv_data.bin somewhere on the phone. it could be located in either /efs or /data/radio
Ensure you have a nv.log with at least one line that looks somewhat like this:
MD5 fail. orignal md5 'XXXXXXXXXXXXXXXXXXXXXX' computed md5 'XXXXXXXXXXXXXXXXXXXXXXXXX' (rild)
where the X's are a bunch of number and letters.
Copy the good nv_data.bin, nv_data.bin.md5 and nv.log to both the sdcard and then via usb put them on your hard drive in a folder called efsbackup
(use either rootexpoler or adb shell to copy the files to the sdcard first)
Open the nv.log and look for the second sting of lines. after the words computed md5 (the first string is the md5 the phone found and the second string is the md5 it was expecting for. if the md5 it was expecting can't be found, it uses the default IMEI 004999010640000
Open nv_data.bin.m5d with a proper unix text editor (I suggest Notepad++ or jedit) and remove the sting of numbers and letters and replace it with the string from the nv.log (the second string after computed md5) and save the file
Go back to the phone and put the phone into Airplane Mode (this turns off the radio)
Copy the files nv_data.bin and nv_data.bin.m5d back to the sdcard overwirting them
Using either rootexplorer or adb shell copy the nv_data.bin and nv_data.bin.md5 back to the original folder (either /efs or /data/radio (for me it was /data/radio that did the trick))
Using either rootexplorer or adb shell ensure both files have the following attributes Owner:radio Group:radio Owner:RWX Group:R Other:R
Using adb shell type ps (this lists all the running processes) find the one that end with rild and remember the pid
Using adb shell type kill pid# where pid# is the rild process (this restarts the radio)
Go back to the phone and take the phone out of Airplane mode
Reboot the phone
Open up the dialer and dial *#06# (the universal way to get your IMEI it SHOULD be equal to the one written under the battery)
Thanks for the reply, but it can't work.
Ensure you have one good copy of nv_data.bin somewhere on the phone. it could be located in either /efs or /data/radio
Click to expand...
Click to collapse
I have no good copy of nv_data.bin, date shows that all have been generated last week.
So, I'd like to flash the phone with Odin rom stock 2.3.4 AND re-partition with the .pit file.
I've already flash it without the .pit, but my IMEI is still generic, I need the .pit file.
But the .pit file is nowhere, even on samfirmware : /
If somebody got this file, plz send it to me.
sheeen said:
Thanks for the reply, but it can't work.
I have no good copy of nv_data.bin, date shows that all have been generated last week.
So, I'd like to flash the phone with Odin rom stock 2.3.4 AND re-partition with the .pit file.
I've already flash it without the .pit, but my IMEI is still generic, I need the .pit file.
But the .pit file is nowhere, even on samfirmware : /
If somebody got this file, plz send it to me.
Click to expand...
Click to collapse
-I too have looked high and low for the Odin file since the Nexus S can be put in download mode holding the volume button while pluging in the micro USB. I did find some odin files but any one who tired them ened up perm bricking their phone.
-If you have a good backup it should restore the EFS partition as well as the RADIO.
-The only other way that I know of, I am afraid is to get the phone JTAGed by Samsung.
Good Luck
After two weeks of trying everything, I gave up and used a Z3X.
Now my IMEI is restored, and backup on my PC, my laptop, my sdcard and on cloud...
Thanks all for trying to help me.
Related
This Guide is for any user that has a Rom installed. This will back-up almost everything the user has put on the phone.
So, here are some things you need.
Heimdall One Click KB2 - http://forum.xda-developers.com/showthread.php?t=1266172 (thanks to AdamOutler)
1) First, make a nandroid backup.
2) Make an /efs backup (adb pull /efs) (also can use an app called nitrality available in market)
3) Now, you will need to Plug in your phone to the computer. Take ALL the folders on your SD card and copy them to your laptop. (Mine was user/android/sdcardbackup)
4) Remove Micro-sd card, and SIM card
5) Open up your dialer and dial this code *2767*3855# THIS WILL WIPE YOUR SD CARD and /DATA
6) Reboot the Phone
7) put your Phone in download mode, open heimdall One Click and insert the phone and make sure that heimdall recognizes it
8) Flash the new firmware Bootloaders not required
9) Have the Phone Boot up Completely (takes a long time)
10) Check to see if your /efs has been edited. Use this thread http://forum.xda-developers.com/showthread.php?t=881162 (and your efs backup) to get it back.
11) You might want to dial *2767*3855# Just in case if there is anything left.
12) You should be running KB2, have your SD cleared, and ready to be turned into samsung.
Post Questions and comments below!
i decided to save this one, no clue why, just wanted to feel important...
Better include this or your phone might come back with a voided warranty.
http://forum.xda-developers.com/showthread.php?t=881162
bigbooty said:
Better include this or your phone might come back with a voided warranty.
http://forum.xda-developers.com/showthread.php?t=881162
Click to expand...
Click to collapse
It isnt supposed to erase the /efs but ill include it, thanks!
sepherian said:
It isnt supposed to erase the /efs but ill include it, thanks!
Click to expand...
Click to collapse
No. Flashing different roms jacks with your efs. A while back I decided to clean up my phone. Internal storage was a cluster. Just for the hell of it I decided to odin back to stock and master clear, then try the 2.2 kies update. Never had tried it. Well got the unregistered device thing and kies wouldn't update it. Found the thread above and downloaded hex editor and followed the instructions, edited my NV_DATA.BIN and reloaded stock jf6 and this time kies upgraded with no problems.
Flashing many different roms changes your product code even though SG tools said I had a sgh-I897, NV_DATA.BIN said I had something else.
When my cappy messed up, my imei got corrupted. Luckily I messed with around with sgs unlock a few months before and still had my back up and was able to restore it before turning it in. first thing I did with new cappy was back up efs. Product code was different also. Flash enough roms and it can mess up something as someone might be a novice coder and mess your device up.
Sent from my SAMSUNG-SGH-I897 using XDA App
Edit: fixed Imei
Nucleartx said:
When my cappy messed up, my meid got corrupted. Luckily I messed with around with sgs unlock a few months before and still had my back up and was able to restore it before turning it in. first thing I did with new cappy was back up efs.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
meid? i think you mean imei?
bigbooty said:
No. Flashing different roms jacks with your efs. A while back I decided to clean up my phone. Internal storage was a cluster. Just for the hell of it I decided to odin back to stock and master clear, then try the 2.2 kies update. Never had tried it. Well got the unregistered device thing and kies wouldn't update it. Found the thread above and downloaded hex editor and followed the instructions, edited my NV_DATA.BIN and reloaded stock jf6 and this time kies upgraded with no problems.
Flashing many different roms changes your product code even though SG tools said I had a sgh-I897, NV_DATA.BIN said I had something else.
Click to expand...
Click to collapse
Yes, I know. This Flash is not intended to mess with the /efs AT ALL, i have checked the package and it has no reference to /efs in the scripting. The post including the package also says this:
This package does not wipe:
EFS(Where your serial number and carrier information is stored)
Data(where your market apps are stored)
SDCard (where your pictures are stored)
Click to expand...
Click to collapse
So as you can see the number i have them call wipes the data and SD but they have their nandroid and SD backups. The number i have them call also doesnt touch the /efs. Trust me, I tested this method before i posted it and i didnt make an efs backup and my IMEI was perfectly fine afterward. I assume that nothing here messed with my /efs at all.
The only thing that would change the NVdata.bin would be an unlock tool. And i doubt that it even changes it.
OP was updated with more accurate steps.
Hi everyone,
I just picked up a GS4G and want it to work with my Tmobile web2go account but am having some trouble. Some people simply delete the EFS folder but that doesnt work and I have been able to reset the IMEI to all 0's but that gives me problems too.
I have read some people that have a generic IMEI number (004999010640000) or something like that and was wondering how can I get that on my phone. From what I have seen, it is due to flashing a certain rom or messing with the nv_data file. So which rom can I flash to get a generic IMEI or anything else I can do?
Thanks for any help anyone can offer as I would really like to save a few bucks and keep my data plan as it is. Thanks again
the generic actually doesn't work. It won't give you service.
Ive been playing around with it but after 2 days, I am still able to make calls and connect to tmobiles 4g service with the all zero imei.
For anyone wondering, I first deleted the efs folder (dont recommend unless you have 2 backups), restarted and then it came back with a weird imei of weird characters. I was able to make calls but couldnt connect to 4g which is my primary reason of doing this. So I edited my original bin file with microsoft word and changed a few numbers around, replaced it into my efs folder, then got the all zeroes imei. Then I flashed it back to stock via odin and after this, is connected with my internet plan just fine and could make calls fine as well. I thought about leaving it like this but then flashed it with valhalla black edition and it still connects just fine with an all zero IMEI. I still would like to try it with a bin file that gives an IMEI of 004999010640000 but for now, it works for me just fine.
I pay $5 a month for data from Tmobile (Web2go/Tzones) and didnt want to upgrade and am glad I finally got it to work after a few hours of messing around. If anyone has any questions, let me know. I look forward to poking around the SGS4 threads for awhile until my next phone.
Hi mendezj666,
I just got my SGS4G today and I also have the $5 a month data plan from tmobile. Can you please share where to change on the nv_data.bin to do the trick? I appreciate that.
Thanks
pwong9 said:
Hi mendezj666,
I just got my SGS4G today and I also have the $5 a month data plan from tmobile. Can you please share where to change on the nv_data.bin to do the trick? I appreciate that.
Thanks
Click to expand...
Click to collapse
Have you read up on this phone and know how to root and install roms and know how to use odin? (All very easy to do) I just dont want to get blamed if you mess up your phone and want to make sure you have at least two back ups of your nv_data.bin file (preferably on your computer as well as your sd card).
Also, just to make sure, it asks you to upgrade everytime you access the internet on 4g, right?
mendezj666 said:
Have you read up on this phone and know how to root and install roms and know how to use odin? (All very easy to do) I just dont want to get blamed if you mess up your phone and want to make sure you have at least two back ups of your nv_data.bin file (preferably on your computer as well as your sd card).
Also, just to make sure, it asks you to upgrade everytime you access the internet on 4g, right?
Click to expand...
Click to collapse
Thanks for the quick response. I use EFS_Pro_1.4.7 to backup and restore the efs folder. I just upgraded the phone to SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click. I do have two backups of EPS folder on my PC and my sd card. I also made a CWM backup.
Correct. It asks me to upgrade my data plan which I want to stick as long as I can. It works great on 3g on my rooted ICS HD2, but I want the 4G speed.
pwong9 said:
Thanks for the quick response. I use EFS_Pro_1.4.7 to backup and restore the efs folder. I just upgrade the phone to SMS-KJ6-beta2d_Stock-Rom_with_Bootloaders-One-Click. I do have two backups of EPS folder on my PC and my sd card.
Correct. It asks me to upgrade my data plan which I want to stick as long as I can. It works great on 3g on my rooted ICS HD2, but I want the 4G speed.
Click to expand...
Click to collapse
K, just want to make sure. You shouldnt have any concern of bricking your phone since you're just editing one file and can always replace it but as with all flashing, just doublecheck everything. Delete the entire efs folder on your phone (you may have already done this), restart and should have a weird imei number of characters. On one of your backuped efs folders, find the nav bin file and open it with a hex editor. Then I just changed around a few of the numbers in the first lines randomly and saved it. I might have used Microsoft word to edit the bin file but both should work. then i put that nav file in the efs folder on my phone and rebooted it and put it back to stock via odin. Then when it restarted it still had the IMEI of all zeroes but could connect just fine on 4g.
This worked for me and hopefully works for me. If not, I MIGHT be willing to send you my own nav bin file that I personally use (which I wish I had at the start since it would have been much easier from the start) as long as you arent in my city. But thats a big risk since it might make my 4g stop working which would really suck
Thanks mendezj666. Please check your PM. Thanks.
airfluip1 said:
the generic actually doesn't work. It won't give you service.
Click to expand...
Click to collapse
i have a Galaxy Nexus, i have this generic IMEi number for my phone 004999010640000 i changed using a root app called doCOMO or something...i changed it frim my normal one so i could unlock the phone to any network after rooting. Now it has locked me out of every network! Is there anyway way to change it back? i really need help on this im a noob!!! please help me
thanks
Garry
This is the galaxy s4g forum. You might post your problem in the nexus forums. I have the bin file for the sgs4 that gives a working imei and works on tzones.
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
It works perfect for me even without the .nv_data file. Before this i only get simbols instead the imei number. You save my phone!
recovered IMEI by just flashing the CM10 base
I dunno if it's just me or what. I lost my IMEI on Slim Bean.. so I had this thought. I hadn't had this issue with the CM10 rom, so I decided to do the standard flashing procedure. Once CM10 was installed my IMEI came back. I had full signal and all is good. I decided to go back to Slim Bean to see if it would fix the IMEI issue. I flashed it just like the OP stated and walah! I had my IMEI back and everything worked without having to go back to GB, ICS and then JB again. I don't know if this will help anyone, but just wanted to note other people about it. Why did this work for me?
will this mess up my phone more?
I am running froyo 2.2.1 ,I guess it is stock, as I pick this phone up in pawn shop, and it was already rooted. I was doing the command line argument dd and a bunch of stuff, to get some file to get my unlock code. I didn't get no bak file copy, gave up put my sim card back in and that's when I noticed my imei was gone, then I had go launcher installed, so my screen goes blank I end up having to do the three finger data wipe, then I see I got no wifi either. Then I get this phone, DL some apk files, try to reinstall busy box, no go, teller me it don't think it has su permission after I gave it through that super user program, then it say it cant install into /dev/sh/ what ever, so all I got is a really nice looking video player.
So now that I got all that out of me.
2 questions, will flashing gingerbread overtop of froyo, will not make it worse?
Why do one have to flash in the first place, why can't one just copy over the old-time files, or someone find which file goods the imei number then just to in isinglass a file manager open that file, as it should be just what is caller a flat file, meaning no special formating like a Word file.
Then just save it. I am not an expert at android wse (whatsoever) but I have played with copying over top of files, or deleting the old-time one then replacing it with a new one. Why Doesn't that work, has anyone player around just opening there files to see what they look like and figure out where they stick the imei number?
Seems to me should be an easy manner of doing, but now that I don't have an individual showing I am not even sure which file I should try to type that number in to to see what will happen as I don't want to make this phone completely useless.
Any commentary, ideas, anything?
Thanks
MikieD
mikied12 said:
I am running froyo 2.2.1 ,I guess it is stock, as I pick this phone up in pawn shop, and it was already rooted. I was doing the command line argument dd and a bunch of stuff, to get some file to get my unlock code. I didn't get no bak file copy, gave up put my sim card back in and that's when I noticed my imei was gone, then I had go launcher installed, so my screen goes blank I end up having to do the three finger data wipe, then I see I got no wifi either. Then I get this phone, DL some apk files, try to reinstall busy box, no go, teller me it don't think it has su permission after I gave it through that super user program, then it say it cant install into /dev/sh/ what ever, so all I got is a really nice looking video player.
So now that I got all that out of me.
2 questions, will flashing gingerbread overtop of froyo, will not make it worse?
Why do one have to flash in the first place, why can't one just copy over the old-time files, or someone find which file goods the imei number then just to in isinglass a file manager open that file, as it should be just what is caller a flat file, meaning no special formating like a Word file.
Then just save it. I am not an expert at android wse (whatsoever) but I have played with copying over top of files, or deleting the old-time one then replacing it with a new one. Why Doesn't that work, has anyone player around just opening there files to see what they look like and figure out where they stick the imei number?
Seems to me should be an easy manner of doing, but now that I don't have an individual showing I am not even sure which file I should try to type that number in to to see what will happen as I don't want to make this phone completely useless.
Any commentary, ideas, anything?
Thanks
MikieD
Click to expand...
Click to collapse
This is either a joke or a joke.
Many Thanks
zackdjones said:
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
Click to expand...
Click to collapse
I just wanted to thank all of you who have contributed your brain power to the xda forums. This advise worked great and after a lot of self doubt I now consider myself a semi-noob. Thanks again.
A J
Thanks on this. I had a backup of my EFS folder, but the tool I used to create it made a .img file and once I got it into JB, the tool didnt work. UGH.
Just want to say thank you for posting this. I have a friend who had her Infuse stop getting calls, texts, etc. Turns out her IMEI was all question marks and other invalid characters. ATT wouldn't help her at all and either did a full reset.
thank you, this method really works!! finally my imei is back...no more symbols, now is time for a efs back up
Since when do phones lose their imei's? That's a new one on me.
sholsten said:
Since when do phones lose their imei's? That's a new one on me.
Click to expand...
Click to collapse
It happened for me twice on two separate phones when using MIUI. Basically the ROM managed to corrupt the system partition, specifically the efs folder.
I don't know the specifics of why, but it happens to a lot of people. That's why I always now make sure I have a backup of the efs just in case.
Sent from my SAMSUNG-SGH-I717 using xda premium
zackdjones said:
It happened for me twice on two separate phones when using MIUI. Basically the ROM managed to corrupt the system partition, specifically the efs folder.
I don't know the specifics of why, but it happens to a lot of people. That's why I always now make sure I have a backup of the efs just in case.
Sent from my SAMSUNG-SGH-I717 using xda premium
Click to expand...
Click to collapse
This method didn't work for me :\ Any other ways to solve this issue?
can i use this Efs on galaxy R to repair unknown baseband & Blank imei????
Thank you very much. This is what I need
worked great. thank you.
zackdjones said:
I can't really take credit for this, but I just restored my IMEI without a backup of the efs folder. Keep in mind that I actually deleted my efs folder by accident, so I didn't even have the original efs folder.
The original thread I referenced is here:
http://forum.xda-developers.com/showthread.php?p=31771228#post31771228
FYI, this method will restore your phone to stock Gingerbread.
Here is what you do:
1.)
A) Download and unzip the Gingerbread unbrick package here from (http://forum.xda-developers.com/showthread.php?p=27286083#post27286083):
w/ root - http://d-h.st/ewu
w/o root - http://d-h.st/G6g
B)
Download and unzip the efs zip here:
http://forum.xda-developers.com/attachment.php?attachmentid=1152914&d=1340558510
2.) Place phone in download mode.
3.) If needed, install latest Samsung USB drivers by installing Samsung Kies from HERE.
4.) Open the included Odin exe.
5.) If phone is detected, the window under ID:COM will turn yellow.
6.) Click on "PIT" to browse to and select infuse_gb.pit. Make sure that Re-Partition is selected.
7.) Click on "PDA" to browse to and select PDA_UCLB3.tar.md5.
8.) Click on "PHONE" to browse to and select PHONE_UCLB3.tar.md5.
9.) Click on "CSC" to browse to the efs.tar
10.) Click the Phone EFS Clear checkbox
11.) Click on "Start", and allow Odin to flash the phone. Do not unplug or power off the phone until Odin is finished.
12.) When the Odin dialogue reads "PASS!", the phone should reboot into the stock UCLB3 Setup Wizard. For me this step just proceeded to install an update and the reboot the phone.
Once the phone reboots, if your SIM card is installed you should be good to go, otherwise you will get an alert about your SIM card which means you need to power off and pop in the SIM card.
Thanks to the original thread author for this one.
Click to expand...
Click to collapse
1stly thanks a lot for this thread. Really millions of thanks.
Now one silly question:- I unzipped the efs file attached and it says "efs.rfs" but your instructions above says "efs.tar" needs to be selected under CSC option. Am I missing something?
Punnyabrata said:
1stly thanks a lot for this thread. Really millions of thanks.
Now one silly question:- I unzipped the efs file attached and it says "efs.rfs" but your instructions above says "efs.tar" needs to be selected under CSC option. Am I missing something?
Click to expand...
Click to collapse
Strange things are happening to me.
About 2 weeks back this problem started and today when I reconnected the SIM and restarted the phone everything was back to normal. Phone is picking up signal/3G etc.
Surprised is the word. Leads me to believe some app must be responsible for all of this.
Thanks,
PC
It is showing invalid mds sum...what I do?
At the end of the task odin shows blue screen and show fail.
Now my phone doesnt get start..what I do?
sachinppatel16 said:
At the end of the task odin shows blue screen and show fail.
Now my phone doesnt get start..what I do?
Click to expand...
Click to collapse
Have you tried Odin as administrator ? that's might be the problem
LESSON LEARNT (for everyone): Please make sure to do a complete EFS backup before you do anything or you will end up like me!!!
So yeah I flashed Deodex_LF2_Cwm.zip yesterday, trying to deodex my DDFL2.
And following that I experienced total loss of mobile signal, baseband, IMEI, IMEI SV, and phone (*#1234#).
And I haven't been seeing this kinda thing to come, I did not back up EFS. (Yeah brilliant me)
So I tried a few of these:
[GUIDE] Recover your IMEI in 9 steps
Repair IMEI using EFS Pro
Reflashing from latona.pit then XXKPE; for a few times
Flashing stock ROM for Malaysia region (Froyo and GB)
Flashing various Modem.tar (DDLE1, DXKP7, etc) via Odin3 at different ROM levels (XXKPE, DDLF2, even CM10A4)
Restoring Nandroid backup from other SL user (Thanks Rich'Dawg')
But nothing worked so far yet.
Now that I checked the /efs folder is empty and there is only a folder named lost+found.
Some websites said about fixing IMEI for small fees but in cases of blank IMEI (*#06#), chances are only 30%.
And my last resort would be getting it replaced in Samsung service centre or any repair shop, which I suspect that the motherboard would be more expensive than some simple new Android phones.
Leaving this forum for the moment as to collect more money to get a new phone . . . :crying:
Lastly, thanks for all the input. Greatly appreciated.
Do you able to call anyone. ? if yes then no need to change anything. if no then you should search for imei solution on xda. there is some tutorial for fake imei.
nicsptl said:
Do you able to call anyone. ? if yes then no need to change anything. if no then you should search for imei solution on xda. there is some tutorial for fake imei.
Click to expand...
Click to collapse
Nope. I totally lost signal and mobile network.
cheeyeen said:
Nope. I totally lost signal and mobile network.
Click to expand...
Click to collapse
do you flash b4 CM10? if yes, search your sd card and External sd card for the installation backup of efs folder
chongns said:
do you flash b4 CM10? if yes, search your sd card and External sd card for the installation backup of efs folder
Click to expand...
Click to collapse
Yes I did but nope I couldn't find. sucks.
It is in a folder name backup
Sent from my GT-I9003 using Tapatalk 2
chongns said:
It is in a folder name backup
Sent from my GT-I9003 using Tapatalk 2
Click to expand...
Click to collapse
Sad enough this folder does not exist in my phone....
Have you had any idea if Samsung would fix this in Malaysia..? Or how much would that be.
I spent like 10 hours trying to look for a solution but >"<
cheeyeen said:
Sad enough this folder does not exist in my phone....
Have you had any idea if Samsung would fix this in Malaysia..? Or how much would that be.
I spent like 10 hours trying to look for a solution but >"<
Click to expand...
Click to collapse
no idea of how much it should be.
but a idea to help you,
1st idea:
go in recovery and fix permission.
2nd idea:
you said you flash Deodex LF2 in CWM, it should not touch efs folder. so, very high change of your nv_data.bin file backup still good.
OK. use any file browser look in the efs folder, see if the below file still exiting, (they are hidden file)
check on the file date. is the date older than the date you flash the zip, if yes, this is the one original from your phone.
the file name start with a dot
.nv_data.bak - ( this is your imei backup file) copy and rename the .nv_data.bak to nv_data.bin and set permission and change owner.
.nv_data.bak.md5 - (delete this file first)
chongns said:
no idea of how much it should be.
but a idea to help you,
1st idea:
go in recovery and fix permission.
2nd idea:
you said you flash Deodex LF2 in CWM, it should not touch efs folder. so, very high change of your nv_data.bin file backup still good.
OK. use any file browser look in the efs folder, see if the below file still exiting, (they are hidden file)
check on the file date. is the date older than the date you flash the zip, if yes, this is the one original from your phone.
the file name start with a dot
.nv_data.bak - ( this is your imei backup file) copy and rename the .nv_data.bak to nv_data.bin and set permission and change owner.
.nv_data.bak.md5 - (delete this file first)
Click to expand...
Click to collapse
Fixed permission.
I found one .nv_data.bak dated year 1994 , which I think came in when I was trying to flash some efs fixes i found in XDA.
Without much hope I tried what you said, but still nothing happened. IMEI blank, baseband unknown.
Is it possible to have the mobile phone repair shop with RIFF or Jtag or some box thingy to have this done?
i think you must change the motherboard
cheeyeen said:
[Request] Is it possible if anyone could send me a Nandroid backup of a working rom, so I could restore it via CWM? (It is a way I found in the XDA forum).
...
So yeah I flashed Deodex_LF2_Cwm.zip yesterday, trying to deodex my DDFL2.
And following that I experienced total loss of mobile signal, baseband, IMEI, IMEI SV, and phone (*#1234#).
And I haven't been seeing this kinda thing to come, I did not back up EFS. (Yeah brilliant me)
So I tried a few of these:
[GUIDE] Recover your IMEI in 9 steps
EFS Pro
Reflashing from latona.pit then XXKPE; for a few times
Flashing various Modem.tar (DDLE1, DXKP7, etc) via Odin3 at different ROM levels (XXKPE, DDLF2, even CM10A4)
But nothing worked so far yet.
Now that I checked the /efs folder is empty and there is only a folder named lost+found.
And my last resort would be getting it replaced in Samsung service centre??
I don't know how much would it cost in Malaysia to change the motherboard but I'm sure it will be stupidly high...
Or.. does that mean my time in i9003 forum is up..? :crying:
Please help me because I don't want to buy a new phone yet! :crying:
Click to expand...
Click to collapse
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Rich'Dawg' said:
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Click to expand...
Click to collapse
I would try anything as long as it works! Please do!
Best of Luck
a friend of mine ran through the same same problem and i think he did some sort of repair from a shop but later we came to know that the backup can do the task not sure whether that work or not but u can give it a try,, BEST of Luck with that..... Hopit Fix the Issue
Good luck sir! As far as I know, if you would choose to replace the motherboard from repair center, it would cost you more or less 80% of the original price of the phone. So it would seem that you have to buy a new one. I hope that a nandroid backup (as stated above) would solve the problem. God bless you! Think positive
i have the same problem and tried those solution the TS tested and still no luck, i wan't to try those nandroid backup but can't find any.
Rich'Dawg' said:
Mate, do you like JellyBam V.1.3.0? Because that's the only Nandroid backup i have in my phone. I was thinking to upload it to my Box account for Emergency Backup if i don't have my computer. If you like, i can upload it for you, but the size of the backup would be nuts, it's 850 MB. It's up to you.
Click to expand...
Click to collapse
Bro,pls upload... let me try it... if imei is changed to 043xxxxxxx then we can fix with z3x box
Xperia.IN said:
Bro,pls upload... let me try it... if imei is changed to 043xxxxxxx then we can fix with z3x box
Click to expand...
Click to collapse
can you share it with me if you have nandroid backup, i will try to fix it with z3x and asansam
never thought deodexing gonna brick the phone.. ive deodex once without any problem.. without any doing backup before that.. lucky me.. huhu
try other people's nandroid and see.. i dont think it needs a specific emei or what so ever.. as long as its a backup.. goodluck..
the problem is we can't find someone to lend us their nandroid backup.
I did it!
Bro, try use Efs Pro, http://forum.xda-developers.com/showthread.php?t=1308546
Try the new version, you can choise Qualcom version, write you IMEI number, go back to initial and do NV Restore.
My SG Fit go back to life (after maybe 4 months with 0000000000000 Imei). :good:
I´m very happy
Hope it work for you! Good luck!
Hi,
I have a note 3 neo, 7505 and i updated the firmware. It was all working good for a week then i was listening to soundcloud to sleep and the phone restarted, since then the phone doesn't have an imei and says to insert sim card, and of course unknown modem..
Anyway, i created a backup of the efs using twrp, i have tried gazillion ways to restore the backup and gazillion manual ways too. Going to stock recovery... trying to copy manually the nvdata and all but it doesnt resolve. The files are placed there, i can see it in the shell but the thing just wont work!
i don't know how to proceed to this, i don't know if its a hardware fault, had it been that, shouldnt have i gotten the efs corrupted or some issue? could it be that the hardware itself is damaged all of a sudden? i dont think so, i pretty much think its the efs and yet i cant restore it?
should i attach my efs folder if someone can look through hex editor or logs to suggest a possible solution?
Thanks a lot and also i have search through and proceeded with many solutions and after that created a thread. hope someone can help.
P.S. I just noticed the serial number can be seen in phone status, so apparently its reading NVdata? or is it getting it from elsewhere? how to test if its a hardware fault?
penandweb said:
Hi,
I have a note 3 neo, 7505 and i updated the firmware. It was all working good for a week then i was listening to soundcloud to sleep and the phone restarted, since then the phone doesn't have an imei and says to insert sim card, and of course unknown modem..
Anyway, i created a backup of the efs using twrp, i have tried gazillion ways to restore the backup and gazillion manual ways too. Going to stock recovery... trying to copy manually the nvdata and all but it doesnt resolve. The files are placed there, i can see it in the shell but the thing just wont work!
i don't know how to proceed to this, i don't know if its a hardware fault, had it been that, shouldnt have i gotten the efs corrupted or some issue? could it be that the hardware itself is damaged all of a sudden? i dont think so, i pretty much think its the efs and yet i cant restore it?
should i attach my efs folder if someone can look through hex editor or logs to suggest a possible solution?
Thanks a lot and also i have search through and proceeded with many solutions and after that created a thread. hope someone can help.
P.S. I just noticed the serial number can be seen in phone status, so apparently its reading NVdata? or is it getting it from elsewhere? how to test if its a hardware fault?
Click to expand...
Click to collapse
The point is that TWRP creates faulty EFS backups on many devices which can't be restored properly.
There are different backup solutions (e.g. EFS Pro) confirmed working which may help you prevent future issues. I prefer the manual backup using adb shell or terminal emulator:
dd if=/dev/block/mmcblk0pXX of=/storage/SdCard/efs.img bs=4096
(XX needs to be replaced with the model specific partition number as they use different partition tables)
Restore:
dd if=/storage/SdCard/efs.img of=/dev/block/mmcblk0pXX bs=4096
thanks LS.xd, but i guess i have a pretty solid backup as i did create backup various ways, some were corrupt, but one that i working with has nvdata and every other file along with imei pretty intact....
i can open it up with winrar, and open the nvdata with hexeditor, i was wondering if i could confirm some way that the back up is actually 100% solid?
wondering if the partition's aren't aligned. I don't know for sure if EFS folder in the root directory is the same as being pointed by /mmcblkp03/platform/by-name/EFS ?
i mean they should be the same thing, its just a redirection right?
what should i be doing now? the baseband is unknown and the imei wont just work, waste the phone? or it could be done via some boxes or some other process?
there must be a starting point? isn't there some way i could use a generic imei and just any modem? then i could replace nvdata may be? right now, i'm installing various versions of stock firmware and repeatedly placing old efs data in various ways and i kind of turning hopeless. first i lost a nexus then i bought a g4 last month, gave me a bootloop just a week after, gone dead. then i bought the n3n and now this..... i mean 3 phones in a row..... i really hope this could work..
penandweb said:
there must be a starting point? isn't there some way i could use a generic imei and just any modem? then i could replace nvdata may be? right now, i'm installing various versions of stock firmware and repeatedly placing old efs data in various ways and i kind of turning hopeless. first i lost a nexus then i bought a g4 last month, gave me a bootloop just a week after, gone dead. then i bought the n3n and now this..... i mean 3 phones in a row..... i really hope this could work..
Click to expand...
Click to collapse
So you got some non TWRP made EFS backup, too? You can list your partitions using shell:
[email protected]:/ # cat /proc/emmc
You can use the dd command once you know the layout. Backups not generated manually may only be restored with the specific app/version and are probably not compatible using other restore methods. For my OnePlus 3 EFS backup can generated fine using TWRP but restoring it screws up the partition. Manually created image works fine. As I don't have a Note 3 Neo I don't know how it behaves for your device.
any idea how would i go on about inspecting the nvdata.bin? i'm in hex editor trying to see something resembling imei but its just so much garbage except a few lines.
i can't be sure whether its corrupt or not...
in efs -> imei -> a file called mps_code.dat i open it up in hex editor, and it has only 3 characters.....
is it possible i could initially use a generic imei and modem and later on populate it with actual somehow or just keep using generic one for now until i find a better solution, using hex editor or something...?
there are some tutorials on qualcom.. none for exynos but it should happen the same way, somewhere in nvdata, you place the imei ... and it would be generic method for most exynos devices...
i wish someone could guide me to that...
also can it be restored via "boxes"?
penandweb said:
any idea how would i go on about inspecting the nvdata.bin? i'm in hex editor trying to see something resembling imei but its just so much garbage except a few lines.
i can't be sure whether its corrupt or not...
in efs -> imei -> a file called mps_code.dat i open it up in hex editor, and it has only 3 characters.....
is it possible i could initially use a generic imei and modem and later on populate it with actual somehow or just keep using generic one for now until i find a better solution, using hex editor or something...?
there are some tutorials on qualcom.. none for exynos but it should happen the same way, somewhere in nvdata, you place the imei ... and it would be generic method for most exynos devices...
i wish someone could guide me to that...
also can it be restored via "boxes"?
Click to expand...
Click to collapse
After 3 years I had to retire my HTC One S. I flashed roms and firmwares up to 3-4 times a week without having any issues. One sunny day some update bricked then nvdata. I spent a bunch of hours trying to restore it in different ways, extracted data from stock firmware as well as using dumps from other user's phones, as some users reported this error fixed doing so. Even when the files was identical it just did not work for me. Changing the mainboard was the only possible solution so I decided to get a new device.
All I want to say is try to restore a valid backup in a way confirmed working. If you don't have a usable backup ask in your device's forum for somebody may upload it. Or spend 100 hours messing around with hex editors until you reach then point where you realize its cheaper to switch the device as wasting a year's holidays browsing the internet for some solution.