Related
TO MINIMIZE THE CHANCE YOU LOSE YOUR IMEI, BE SURE AND ROOT/CWM USING THIS METHOD:
http://forum.xda-developers.com/showthread.php?t=1739426
AND ONLY FLASH ROMS INTENDED FOR USE ON YOUR MODEL
**UPDATED 7/16/12**
questions we are trying to answer:
- what versions of clockworkmod, if any, are prone to causing IMEI problems?
- what rooting methods, if any, are prone to causing IMEI problems?
- what ROMs are causing imei issues, and on which models? is the rooting/cwm method related?
- where is the IMEI stored on the phone, and most importantly
- is it possible to back it up, and restore it once corrupt?
RESTORING AN /EFS BACKUP DOES NOT APPEAR TO RESTORE AN IMEI AT THIS TIME.
TO BE SAFE, USE THIS GREAT SCRIPT BROUGHT TO YOU BY DROTHENBERGER AND SFERNANDEZ:
http://forum.xda-developers.com/showpost.php?p=28528532&postcount=38
You will need Cygwin (http://www.cygwin.com/) for the script.
Original post by sfernandez detailing the partitions: http://forum.xda-developers.com/showpost.php?p=28519596&postcount=39
IF YOU HAVE THIS ISSUE, PLEASE FILL THIS OUT AND POST. THANKS PINOYMUTT:
1. CARRIER VERSION:
(ATT, TMo, Sprint, Verizon, Bell, etc.)
2. ROOT METHOD:
Exact method you used to root, please link to the thread if possible
3. CWM INSTALLATION METHOD:
Again, please be specific. Examples include the ADB/DD method, flashing via ODIN, etc.
4. CWM VERSION:
Which CWM are you using -- the Sprint version or one of the Clockwork ones?
5. ROM(s) FLASHED:
Did you flash any ROMs after the above, and how did you flash it?
6. WHEN DID YOU FIRST NOTICE IMEI WAS GONE?:
It helps if you know which step may have caused the issue
7. OTHER NOTES:
RULES
1. Please READ THE ENTIRE THREAD BEFORE POSTING. There is way too much info in here for me to summarize.
2. ALWAYS READ THE THREAD BEFORE POSTING
3. If your phone is working properly and your IMEI is intact, and the method you used to root and install CWM has already been detailed by another member, WE DO NOT NEED TO KNOW IT ALSO WORKED FOR YOU. LET'S TRY AND KEEP THE THREAD CLUTTER DOWN
4. No arguing or bickering over stupid crap. Keep that to PMs.
5. READ THE THREAD BEFORE POSTING. THANK YOU.
original post:
If you have flashed a new ROM on your phone recently and have found difficulty or impossibility in getting cellular or data service, chances are you have corrupted or deleted the file that stores your IMEI. i'll try to answer a couple of common questions and detail methods i used, and why i think they failed
What is an IMEI?
your network identifies your phone by its IMEI. once i had "lost" mine, AT&T's network would not provide service to my device, even after getting a new sim card.
How can I check if mine is corrupted?
your IMEI is a 15-digit number under your battery. dialing *#06# should display the same number under your battery. if you get a different number or something like 0 / 00, you have corrupted your IMEI.
Changing the APNs
marginally effective at best. your phone is not registering on AT&T's network as a device it should send data to, so it doesn't matter what APN you use.
flashing to stock rom
did not work for me. probably because this probably doesn't effect the /efs partition, where the IMEI is stored.
use CWM / nandroid restore
from what I can tell, a standard backup does not back up the EFS partition. you need to use something like EFS pro to backup your /efs directory (where the IMEI is stored). restoring my phone to a previously stable and working save did not restore my IMEI
editing nv_data.bin
no one has been able to find this file on the SGH-i747
using a terminal / AT interface
it looks like the IMEI is encrypted and causes a stack overflow when you try to query it. notice how i can query my IMSI (edited) fine, but querying the IMEI causes a stack overflow. pic:
http://imgur.com/uZxZL
i probably tried a few more things i can't think of right now. moral of the story is... approach unstable roms with caution, and BACK UP YOUR EFS PARTITION!!!
anyone had any luck restoring a busted IMEI? :highfive:
EFS pro has not been updated to the correct partition for i747, so currently that method to backup/restore will not work.
Sent from my HTC One X using xda app-developers app
thanks for the info. will copying the entire /efs directory to my extsd using root explorer work?
It's not the EFS folder but the correct block partition in the dev folder.
Sent from my HTC One X using xda app-developers app
thanks for filling me in on this, still an android nub compared to you guys... did some digging and found this:
http://forum.xda-developers.com/archive/index.php/t-1689623.html
is that info still relevant/correct?
Not sure but cant hurt to do a full backup of all the blocks until someone can confirm that it's the same with the s4 version of the galaxy s3.
Sent from my HTC One X using xda app-developers app
can anyone confirm if using root explorer to backup /dev safely backs up your IMEI?
how can you do a backup of all the blocks on the phone?
I have not used this yet but you should read this thread and give it a try.
http://forum.xda-developers.com/showthread.php?t=1746665
nunyabiziz said:
I have not used this yet but you should read this thread and give it a try.
http://forum.xda-developers.com/showthread.php?t=1746665
Click to expand...
Click to collapse
thanks ill check it out
On my older captivate backing up the efs folder worked. Then if you loose the imei, restoring the folder or nvdata file fixed it. I'd backup the efs folder just in case.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
EFS Pro DO work with the S3. (I haven't try restoring my EFS, but backup went fine)
http://forum.xda-developers.com/showthread.php?t=1308546
What did you to loose IMEI? What ROM did you flash or what did you do wrong to cause this? Better to learn from somebody's else mistakes then your own.
When I had the problem on my Samsung Captivate, the EFS was wiped out when I converted from a CyangonMod rom to a standard Captivate based ROM. I didn't actually lock down what caused the issue (since I could easily fix it by restoring the nvdata.bin file - which I just kept handy on my external SD card and PC as well). I think it might have been when I ran a one-click ODIN to restore back to the RFS file system to install one of the custom Captivate ROMS. The only issue I ran into was the IMEI was different than what it should have been, but no usability issues at all. So moral of the story is, it's possible it can happen any time you flash a new ROM, backup your EFS folder and keep it in a safe place (I believe it's just the NVDATA.BIN file you need because that's all I restored), and enjoy the variety of custom ROMs these developers are building (because they are great!).
That's my $.02
EDIT: Oh and the Nandroid backups don't backup the EFS folder, so don't think a CWM backup will save you.
to those of you suggesting to back up nv_data.bin... just tell me where it is and i'll be glad to. i was no able to find it anywhere in /efs or /dev
artisticcheese said:
What did you to loose IMEI? What ROM did you f
flash or what did you do wrong to cause this? Better to learn from somebody's else mistakes then your own.
Click to expand...
Click to collapse
i am pretty use it happened when i flashed redruM onto my phone like a dumbass thinking [GSM Universal] meant it would work for my device
On the Captivate flashing a 1-click ROM would fix the issue. I have the issue too, but I really do not know what to do about it, I have looked all around the /efs partition, and I'm not sure where it could be.
DemonWav said:
On the Captivate flashing a 1-click ROM would fix the issue. I have the issue too, but I really do not know what to do about it, I have looked all around the /efs partition, and I'm not sure where it could be.
Click to expand...
Click to collapse
don't mean to discourage you, but i had to get a new device.
one thing that i wanted to try but could not was to take a stable EFS backup from an SGH-i747, locate the IMEI and change it to my own, and restore my /efs folder with those files. i'm not sure if decrypting the IMEI is possible, or if even getting to that point is possible.
if anyone has any ideas on how to extract an IMEI from an EFS backup feel free to PM me. i'm interested in experimenting on my personal backup (from my second device)
Ultimately if anyone should lose their IMEI or bork the EFS partition...these guys can fix it. They are very reputable and have fixed my Captivate back in the day....they now offer fixes for this device now. Its only 30 bucks and keep them in mind instead of paying 200 for insurance claims.
NO SPRINT OR CDMA models.
http://mobiletechvideos.mybigcommerce.com/
Well I will be getting a new phone on the 10th, but until then I would really like to figure out how to restore the IMEI. Who knows, it might not be possible at this point. When I get the new phone I will definitely be backing up my /efs directory, first thing. I completely forgot to do it, and it cost me.
How are you guys backing up the efs partition? Just a simple folder copy? Or a complete cwm backup?
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
I am really hoping that someone can help me. I lost my IMEI on my ATT GSIII. I used the IMEI restore methods supplied by Geek & Peoplesarmy to help correct the problem. My phone was already corrupt before I found their repair methods, so I didnt back anything up. I started off with the "IMEI Injection" process. I was able to inject the IMEI back into the phone succesfully, however I am still stuck on 2G/ Edge. I did as much troubleshooting as I could before posting this question. So far I have flashed stock ATT ROM, Wiped & Factory Reset, pulled battery & SIM card, etc. DOn't know what else to do.
Im hoping that somone with more experience can help me. I can not post directly to the IMEI Fix Tool Forum at this time, so hopefully I can get some help here.
Thank you very much in advance!!!
Too bad nobody knows cause I have the same issue!!!
You need to download the App in post #3. This will let you connect to data fully. The IMEI injection only does what it says. You'll need to use this tool to restore full data. I have used to fully restore everything.
Looking for answer.
I have the same exact problem with my Galaxy S3. I came across this forum and was excited too actually got excited! Except when you click on the link in Bam1789 replay it leads too a dead forum. Do one of you have the correct link?
pilotstiles said:
I have the same exact problem with my Galaxy S3. I came across this forum and was excited too actually got excited! Except when you click on the link in Bam1789 replay it leads too a dead forum. Do one of you have the correct link?
Click to expand...
Click to collapse
No,
but you can try what is suggested in this post by umar4u.
http://forum.xda-developers.com/showthread.php?p=44619879
Sent from my SAMSUNG-SGH-I747 using xda premium
So I just got a S4 from T-mobile yesterday, and am planning on putting some roms onto it some time down the road. I'm familiar with the actual installation process, but am just wondering if there's anything I should do before, on the stock rom. I'm aware that (correct me if I'm wrong) you could always return to it later with odin, but I'd like to take care of it first. Things like backing up your efs folder in case your imei changes (happened on my old AT&T captivate), unlocking, etc.
Thanks for your help.
The only way your imei number would change is you get a new phone or a new motherboard. My suggestions is read, read and read before doing anything.
☞Sent from here☜
Root it. Turn off everything you dont use (gestures, etc. ) and use titanium backup to freeze unused apps. Or use google to backup contacts before flashing.
Sent from my SGH-M919 using Tapatalk 4 Beta
baseballfanz said:
The only way your imei number would change is you get a new phone or a new motherboard. My suggestions is read, read and read before doing anything.
☞Sent from here☜
Click to expand...
Click to collapse
My Captivate's imei changed solely from flashing custom roms though...
Food for thought. You can also use samsung keis to restore the stock firmware also tried and true. Just in case odin fail its always good to have two restore method's
Sent from my SGH-M919 using XDA Premium HD app
I don't know how that's possible. For the imei to change from flashing roms. The imei changes when you get a new phones or a new motherboard when you get a replacement or a repair
Sent from my SGH-M919 using XDA Premium HD app
Altair4 said:
So I just got a S4 from T-mobile yesterday, and am planning on putting some roms onto it some time down the road. I'm familiar with the actual installation process, but am just wondering if there's anything I should do before, on the stock rom. I'm aware that (correct me if I'm wrong) you could always return to it later with odin, but I'd like to take care of it first. Things like backing up your efs folder in case your imei changes (happened on my old AT&T captivate), unlocking, etc.
Thanks for your help.
Click to expand...
Click to collapse
One of the few things that can only be done on the stock ROM is SIM unlock. So, that probably wouldn't be a bad idea to do before you go swapping ROMs whether you'd need it or not. It's definitely not required and I think can be done on the custom TouchWiz ROMs as well; just a thought.
Hi Guys,
Some time ago my SGH-i927 turned off and refused to come back on, it was sent to a couple of repair specialists who confirmed it was dead; an ex SGH-i927; it was no more, it had shuffled off it's mortal coil......e.t.c.
....now I have splashed out on a 'for spares showing extreme wear' handset from a well know auction site, supposedly it switches on but because of a broken screen is otherwise unusable. My hope is to swap the innards of the spares into my old phone which has a decent screen in a desperate attempt to achieve a single working handset.
I have backups both NANDROID and EFS from my old phone before it passed away. I've searched on restoring the NANDROID and this would seem to be a workable proposition, however, I have found little on restoring EFS to a 'repaired' phone. There were hints that this might over write the IMEI of the donor with the IMEI of my old phone. The legalities of this would appear to be somewhat dubious. As I presumably own the rights to both IMEI's and there will still only be one phone with it, what are your thoughts ?
My old phone was network unlocked using an unlocking code based on it's IMEI - which of the 'Backups' contains this setting (I'm guessing EFS) ?,
If I just restore the NANDROID would the unlocked status be preserved or would I need the EFS too?
What other issues might I encounter if I try to restore the EFS ?
Your help with these questions would be gratefully received.
requiem_mortis said:
Hi Guys,
Some time ago my SGH-i927 turned off and refused to come back on, it was sent to a couple of repair specialists who confirmed it was dead; an ex SGH-i927; it was no more, it had shuffled off it's mortal coil......e.t.c.
....now I have splashed out on a 'for spares showing extreme wear' handset from a well know auction site, supposedly it switches on but because of a broken screen is otherwise unusable. My hope is to swap the innards of the spares into my old phone which has a decent screen in a desperate attempt to achieve a single working handset.
I have backups both NANDROID and EFS from my old phone before it passed away. I've searched on restoring the NANDROID and this would seem to be a workable proposition, however, I have found little on restoring EFS to a 'repaired' phone. There were hints that this might over write the IMEI of the donor with the IMEI of my old phone. The legalities of this would appear to be somewhat dubious. As I presumably own the rights to both IMEI's and there will still only be one phone with it, what are your thoughts ?
My old phone was network unlocked using an unlocking code based on it's IMEI - which of the 'Backups' contains this setting (I'm guessing EFS) ?,
If I just restore the NANDROID would the unlocked status be preserved or would I need the EFS too?
What other issues might I encounter if I try to restore the EFS ?
Your help with these questions would be gratefully received.
Click to expand...
Click to collapse
AS i know it would preserv. if not, you wil lbe able to use old unlock code with old imei.
Be sure to backup OLD and NEW efs.
Laws here perevent to mess with radio things, and that means you are forbidden to change your imei.
Manipulating the efs may brick your phone. I would start backup efs, and restore old one, and see what happens.
bubor thankyou for your response, may I ask for clarification
Laws here perevent to mess with radio things, and that means you are forbidden to change your imei.
Click to expand...
Click to collapse
Would restoring my Old 'EFS' to the transplanted / replacement motherboard constitute 'messing with radio things' ?
I ask so as to avoid breaking the law ...UK LAW
Please PM me if you do not wish to publish an answer
Further research would indicate that the WiFi MAC address may also be stored in the EFS folder, if I overwrite the EFS of the donor MOBO with my backup file would the WiFi still work ?
Can anyone confirm if the WiFi component would still work with a transplanted EFS ?
All thoughts gratefully received.
Hey all!
I have a Canadian S4 (SGH-M919V) from WIND Mobile that my friend gave to me, broken.
I have already tried just about everything I can think of, and everything I read online to repair it.
It has a NULL IMEI (as verified by doing *#06#), and when I enter the Service Mode menu via *#0011#, the menu screen comes up but is just black and blank. The Baseband version displays as "Unknown".
I have tried flashing a few different stock roms (via Odin) for that particular phone, and have even tried AOSP roms (via TWRP), to no avail.
I have followed guides for restoring a blank IMEI, however, all the methods I tried required a working Service Mode, which I do not have.
At this point I'm thinking the problem is either hardware, or, it needs to have the IMEI reset via the JTAG, and I don't have the stuff to do that.
Any suggestions would be greatly appreciated!
Thanks in advance!
ess.boyer said:
Hey all!
I have a Canadian S4 (SGH-M919V) from WIND Mobile that my friend gave to me, broken.
I have already tried just about everything I can think of, and everything I read online to repair it.
It has a NULL IMEI (as verified by doing *#06#), and when I enter the Service Mode menu via *#0011#, the menu screen comes up but is just black and blank. The Baseband version displays as "Unknown".
I have tried flashing a few different stock roms (via Odin) for that particular phone, and have even tried AOSP roms (via TWRP), to no avail.
I have followed guides for restoring a blank IMEI, however, all the methods I tried required a working Service Mode, which I do not have.
At this point I'm thinking the problem is either hardware, or, it needs to have the IMEI reset via the JTAG, and I don't have the stuff to do that.
Any suggestions would be greatly appreciated!
Thanks in advance!
Click to expand...
Click to collapse
Unfortunately you are going to have to get your information on fixing this elsewhere.
Discussion about changing the IMEI (even from 0 to a working value) are forbidden on XDA as making changes to an IMEI is illegal in most places in the world. And people use that info to make it easier to steal phones, so we don't discuss it here.
The only thing that I can advise you on is to restore the EFS backup, which includes that devices original IMEI, if one was made and saved to the device. If not, that's no help at all.
I can say that you're on the right track though as far as fixing it. But you need to find your answers somewhere else.
Skipjacks said:
Unfortunately you are going to have to get your information on fixing this elsewhere.
Discussion about changing the IMEI (even from 0 to a working value) are forbidden on XDA as making changes to an IMEI is illegal in most places in the world. And people use that info to make it easier to steal phones, so we don't discuss it here.
The only thing that I can advise you on is to restore the EFS backup, which includes that devices original IMEI, if one was made and saved to the device. If not, that's no help at all.
I can say that you're on the right track though as far as fixing it. But you need to find your answers somewhere else.
Click to expand...
Click to collapse
Thanks for the reply. I realize the issues surrounding changing the IMEI, so I wasn't looking for help with that necessarily (though I would be open to doing so as the phone does have it's own perfectly legal and valid IMEI which I would be using).
I was hoping that perhaps all that was wrong was a corrupt modem, or something along those lines. I have tried to do an EFS restore, but to no avail. Some guides suggest doing a backup of the presumably corrupt EFS and then restoring it, but that didn't help either.
I am probably just going to have to chalk this up to "unfixable", as it most likely is indeed hardware damage.
So unless anyone else has any ideas...
ess.boyer said:
Thanks for the reply. I realize the issues surrounding changing the IMEI, so I wasn't looking for help with that necessarily (though I would be open to doing so as the phone does have it's own perfectly legal and valid IMEI which I would be using).
I was hoping that perhaps all that was wrong was a corrupt modem, or something along those lines. I have tried to do an EFS restore, but to no avail. Some guides suggest doing a backup of the presumably corrupt EFS and then restoring it, but that didn't help either.
I am probably just going to have to chalk this up to "unfixable", as it most likely is indeed hardware damage.
So unless anyone else has any ideas...
Click to expand...
Click to collapse
If you have the valid IMEI that is confirmed good it is fixable. But it just can't be discussed here. I wouldn't throw the phone out. (If nothing else it's a GREAT tiny tablet for wifi use.)
Google will help you out.
Skipjacks said:
If you have the valid IMEI that is confirmed good it is fixable. But it just can't be discussed here. I wouldn't throw the phone out. (If nothing else it's a GREAT tiny tablet for wifi use.)
Google will help you out.
Click to expand...
Click to collapse
Thanks again. I have an authorized Samsung repair place in town, so I will bring it by there first and see if they can handle it. If not, I'll ask my old buddy Google where to take it from there.