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
First: I have searched... alot.... seriously alot of searching
Second: I would have posted in the appropriate forum ( AT&T, Rogers, Bell, Telus Samsung Galaxy S III > AT&T Galaxy S III Android Development > [FIX/TOOL] Backup/Restore/Fix IMEI & Data Restore Tool v3.0 - Updated 11/01/2012!!!)
BUT I have less then ten posts so I guess I have to put it here.
I restored my IMEI via the instructions in the forum, that went ok, but when I try to load the .qcn backup file into SGS3 QCN Generator the .qcn backup cannot be found on my pc.
I made sure to put it in the correct bin folder and when I go into QPST Software Download the file shows up, but if you browse or even search for it outside of that application it cannot be found...
I'm sorry for posting this here I would rather posted this as a reply in the right forum but the ten posts thing, I guess I'm a noob but I have rooted and rom'd 4 phones now with 12 or 15 different roms and haven't had any issue like this.
any help would be much appreciated.
Phone is tmobile
SGH-T999
4.0.4
Baseband: T999UVLI6
Ok I flashed stock everything from odin, back to Baseband: T999UVLH2 and tried the whole process again and it worked, except I still don't have 4g data... so i could use some help if you know of a way to make my 4g come back pc also says it is unable to identify device when I connect via usb...
Only thing I can think of is when you restore your qcn backup, use the very first one you ever made. Dont know why, just that multiple members have reported that as working for them.
If it doesn't help, PM peoplearmy. I believe he has a file that should fix you right up. Or will at least know what to do.
Sent from my SGH-T999 using xda app-developers app
4G is back, apparently all it needed was another reboot and to sit about 10 min...
Thank you Doc for the reply, I didn't know what I was going to do if all of that didn't work.
If anyone has searched this problem and you have found this thread, please PM me and I will be glad to help you as best I can.
I forgot to backup my imei then i deleted somethings. And my phone can't use 3g, text or phone. Help me:crying:
My Imei is 004999010640000/01 right now.
How to take my old imei back. Thanks bro.
Give it back to service centre. No other way.
Sent from my GT-N7100 using xda premium
Yes you need to go to a service centre, unless you backed up your EFS partition.
Bit of a gravedig but what was the outcome? Have you managed to fix it or did you send it back to Samsung?
If you still have it, unfixed, here's my advice
Unfortunately it isn't good news - a corrupt EFS is one of the hardest things to fix - without a backup it probably can't be done.
It's unlikely but restoring to stock via odin is the first port of call. Probably won't do anything but worth a shot.
Otherwise, The galaxy S3 had a very similar issue though and there was some success at injecting the imei back into the phone - ask around and see if the note 2 has anything similar (or perhaps even identical) process.
http://forum.xda-developers.com/showthread.php?t=1801997
Commented on a few lost IMEI related threads but most of them seem to be unattended. So thought of trying my luck in a new thread :good:
IMEI and Samsung serial number on my unlocked note2 i317 dont match with back panel and so unable to connect to any network(phone's history is unknown so cant do much apart from fixing the phone). Phone's still in original firmware(refer attached snapshot for complete details). Tried to load original stock ROM from ODIN(KIES_HOME_I317UCALJ2_I317ATTALJ2.tar.md5 ) but still EFS remains the same. I could locate the serial_no file(which contains new Serial number) from root explorer but unable to find nv_data files in IMEI folder(IMEI folder only contains mps_code.dat file.
Questions:
- Does this indicate an incorrect ROM flash that might have corrupted EFS?
- Are nv_data bin and bak files visible from root explorer(rooted, of course)?
- Original stock ROM was loaded from a single tar.md5 file(838mb) through ODIN. Though ODIN confirmed it as ''PASS" at the end, all the data on the phone remained intact and the process consumed around 8-10 minutes. Is this acceptable?
Looking forward to quick and promising responses.
TIA,
Chaitanya.
Folks, can someone kindly respond!
I trying to reach couple of members who dealt with similar issues but havent heard back.
Not possible to do it legally.
stevenlong said:
Not possible to do it legally.
Click to expand...
Click to collapse
Im aware about that. I'm mainly trying to figure out the root cause. I'm not quite sure whether the issue is because of a wrong custom ROM or anything else, and hence require some guidance.Can you answer my questions please?
On a lighter note, changing IMEI is illegal but I guess retrieving is not :silly:
I've flashed many different ROMs on various phones and I've never had problems with the IMEI number changing.
Don't know about nv_data phone is still searched my Note II.
Don't know about the results of ODIN flash (sorry).
chaitanyapatwari said:
. . . changing IMEI is illegal but I guess retrieving is not :silly:
Click to expand...
Click to collapse
Having the software is illegal.
Guys,
Your advices are welcome but I would be glad if your responses actually address my problem rather than lecturing me on what is right or wrong. Sorry but,as a novice in troubleshooting android related problems and this being my first overseas phone, I thought senior members could share their experience in pointing to the actual problem with my phone.
In case it is the subject of this thread that is leading to this confusion, I apologize. I'm not really sure if it is an IMEI problem and that why mentioned all the details I thought are relevant to this issue. If it is still against the forum's rules to discuss my issue, please close this thread.
Changing you IMEI does not happen by accident. Flashing ROMs does not do it. Corrupting you EFS will not change you IMEI.
So from the sound of it you have a phone where someone in the past has deliberately changed the IMEI.
The IMEI that your phone currently has sound like it is not recognized by the network as being a valid IMEI.
Sorry but from you description you need to change your IMEI to a valid one.
As I have so patiently explained, you are asking people to give you advice on attempting an illegal action. That's why you aren't getting a solution. Check your xda user agreement - this discussion is breaking that.
Thanks guys.Please understand that I was not sure about the root cause. That's why posted the symptoms here and asked for confirmation. The phone physically looks so good that I couldn't believe that it was used before and got its IMEI and serial number tampered. Since I read some threads with users explaining IMEI related losses, I thought of sharing my issue as well. It was also getting tough to receiving help from India and xda is the best forum I heard about.
Appreciate your feedback. Please close my thread if it is strictly against your rules.
From the Moderator
The Other People who posted are correct software that's sole purpose is to modify the IMEI is not legal. So, it is not allowed in XDA to post such items....... Lic laws, etc.
It is possible to retrieve your original IMEI if you have a previous backup by restoring a nandroid (if you kept one) other than that, not sure how to do it.
That said
This is now .........CLOSED...........
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.