yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] stevessvt:
So I used root explorer to make a copy of the efs folder and put it on my extsdcard. Is this something I can use if I need to if I lose my imei?
[T-Mobile, Samsung Galaxy SIII] jgalan14:
Damn dude the sucks , I seen you around specially on cm threads, I remebr cause of the real Madrid logo
[T-Mobile, Samsung Galaxy SIII] strikeoutss:
Just an fyi. I lost imei on a launch day tmo branded Sg3 after rooting. Not everyone who has had this happen has had it happen in the same manner. I've been a member of this forum since I had my HTC wizard and rarely post. Suffice it to say I've learned to read instructions carefully and not need to post asking a bunch of silly questions. I think it is a bit premature to blanket label everyone who has had this imei problem as someone who flashed the wrong whatever. The issue is we don't have a clue as to where the nv_data.bin file is to back it up on these. I have no intentions of scaring anyone away from rooting or Rom flashing either, however I will echo the op and say read the post and get educated on atleast understanding the risks and fails other people have had.
[T-Mobile, Samsung Galaxy SIII] :
Wonder if it matters if its a 32gb or 16 gb that's losing the imei?

I know there's not many 32 gb out there though.
[T-Mobile, Samsung Galaxy SIII] dvize:
So basically, you can lose imei from rooting and not just flashing a rom. I think I read early on that a lot of users were using Oden tars for different branded phones (That had wrong paths/mounts), before there was actually development being done for their version of the phone. Of course, they would probably have lost IMEI immediately as in your case instead of when flashing CM.

Could it be rooting without tripping the flash counter ?

Just throwing ideas out there for you all.
[T-Mobile, Samsung Galaxy SIII] id_twin:
Are you two typing 'SU' before entering the commands? I'm on CM10 and was able to back up my IMEI without any issues.
[T-Mobile, Samsung Galaxy SIII] drksilenc:
the first release of cm10 wasnt rooted.
[T-Mobile, Samsung Galaxy SIII] mt3g:
What I'm reading more and more is its possibly the fact people are using the wrong recovery, the "hacked version" for sprint not for t-mobile. Can anyone elaborate or confirm that they were on a different recovery then the proper ones, in which I don't even know is the proper one lol...

SGS III on T-Mobile
[T-Mobile, Samsung Galaxy SIII] MacTheRipperr:
I was on the hacked version of the Sprint. Then flashed the appropriate version via Rom manager. But that version wouldn't allow me to restore back ups or create nandroids. So I messed with the mounts and then flashed aokp. Then I was stuck on edge. Then I bought cwmtr and tried to restore a back up. By then I was already ****ed. The efs file was fully intact though. Btw I'm T-Mobile
[T-Mobile, Samsung Galaxy SIII] sabre31:
This is an interesting point. Can someone who lost their imei report if they tripped the counter? I rooted and applied clockwork recovery and triped my counter but my imei is still fine thank God however I have not flashed roms yet because of this issue.
[T-Mobile, Samsung Galaxy SIII] johnhazelwood:
It does seem like the serial number is in the same file/location as the imei, as I'm assuming everyone with a missing imei also has a 0'd out serial number. I've rooted , installed sprint flavor of cwm, flashed stock deodexed rom, flashed new kernel, changed cwm to AT&T flavor, flashed back to stock, applied user created update, all without loosing imei. It does seem like it has something to do with either custom roms, busy box, or some combination that wipes it out.

It seems like this has been happening for a while now (wiping imei) since even the Captivate was out, and I'm unaware of a solution. I'm thinking finding a solution might be a moot point, but being able to restore that stupid file is the key...once we find it.

I'm now starting to watch the Verizon forum, as they have locked bootloaders and are putting more memory level work on resolving. I'm hoping they stumble on the imei location.
[T-Mobile, Samsung Galaxy SIII] MacTheRipperr:
I did trip my counter when I rooted.
[T-Mobile, Samsung Galaxy SIII] cwalker0906:
Has anyone lost imei he got their phone on launch day. This whole epidemic seems to be recent so I was just curious maybe a bad batch you know under the rush
[T-Mobile, Samsung Galaxy SIII] johnhazelwood:
Chainfire updated his Triangle away app, search for it and it will clear your counter.
[T-Mobile, Samsung Galaxy SIII] XpediencY:
Like cwalker asked... preorder phones vs post launch day phones?

I believe I am the only one that this happened to so far... but a weird thing that happened with my phone after rooted with clockwork was that I completely lost LTE signal over the weekend and it never came back. It would only use HSPA and oscillate with no signal every no and then. Flashing back to original stock didn't fix it either. I exchanged it yesterday for a new one and now LTE is back. I haven't flashed anything since.
[T-Mobile, Samsung Galaxy SIII] mobilehavoc:
We still haven't seen a person who lost IMEI that has been using the CWM for d2att have we ? Seems everyone that's lost it used the Sprint one or some other version but not the one specifically for the att phone ? Please let me know because I've read every page and don't see this.
[T-Mobile, Samsung Galaxy SIII] Markdental:
Agree about the people using the wrong recovery.

Check out the Tmobile Development threads with the ROMS built there. There are over 500 replies in a lot of those threads and I pulled a search and not one on imei loss.

This could mean it was the original launch day hardware or it was before people were using the jacked up Sprint recoveries on their Tmobile phones.
[T-Mobile, Samsung Galaxy SIII] mrmako777:
ive rooted twice using the sprint recovery and still have my imei
[T-Mobile, Samsung Galaxy SIII] stevessvt:
Anyone?
[T-Mobile, Samsung Galaxy SIII] unleashed12:
Nope, currently it appears as restoring the efs does not restore your imei, thats the whole issue people are trying to figure out, what causes it and ultimately how to restore it. though you should always have your efs backed up anyway, its good in practice :good:
[T-Mobile, Samsung Galaxy SIII] Markdental:
Maybe it's original hardware then...Is there a way we can figure out serial numbers of those that have jacked up IMEI, and those that have not?

We have to figure this thing out...Or at least figure out how to backup/restore it if it is lost.
[T-Mobile, Samsung Galaxy SIII] mrmako777:
its unsettling to say the least. i was under the impression that the sprint/tmobile variants had the same recovery partition block and this is why we were able to root using the sprint method. if thats the case, i find it unlikely just flashing recovery would cause this to happen. i am admittedly a n00b when it comes to samsung phones, so there may be more to that than im aware
[T-Mobile, Samsung Galaxy SIII] stevessvt:
Curious, any confirmed people using TWRP and losing there imei?
[T-Mobile, Samsung Galaxy SIII] Markdental:
Yeah, but it happened on a new phone, right, not launch day...

Maybe we can get a database of Serial numbers of borked IMEI and compare them to those that flash correctly. Maybe there is a correlation.

I mean, look in TMobile development. at least 2 ROM thread with 100's of replies, NONE of which have had IMEI problems. Maybe it's the ROM?
[T-Mobile, Samsung Galaxy SIII] es7241:
Question do you by any chance know the imeisv on the phone that lost the imei
[T-Mobile, Samsung Galaxy SIII] cwalker0906:
Did you reboot between flashing touch recovery and cm10?
[T-Mobile, Samsung Galaxy SIII] mobilehavoc:
Which CWM touch did you use. I think it might be using Odin to flash CWM. A lot of people used adb and that seems to be safer.
[T-Mobile, Samsung Galaxy SIII] id_twin:
Untrue. I've used ADB, Terminal Emulator, and Odin to flash different recoveries on my phone without any issues. I've flashed CWM three separate times, all different versions, and had TWRP on my phone for about a week, IMEI for me is still alive and kicking.
[T-Mobile, Samsung Galaxy SIII] mobilehavoc:
Well then by what logic it must be CM10 because that's the only thing left the poster above me did before losing IMEI.

All I know is there is no such thing as random in computers unless you program them to be random. So there is a pattern we just haven't figured it out yet. :D
[T-Mobile, Samsung Galaxy SIII] fireboypr:
+1
[T-Mobile, Samsung Galaxy SIII] wildcard30:
I have installed CWM through ODIN and ADB I have used both the team epic CWM and the Touch CWM then back to team epic CWM v4 which I am currently using I have been flashing between 3 roms AOKP, Ultimatum and DietICS and still have my IMEI intact. Doesn't mean I am not concerned about this issue though. I read another post today from someone who had flashed from CM10 and lost their IMEI on Rogers.
[T-Mobile, Samsung Galaxy SIII] stevessvt:
Curious, any confirmed people using TWRP (and never had CWM on their phone) and losing there imei?
[T-Mobile, Samsung Galaxy SIII] swa2k4:
yes I did reboot and im really thinking the difference in things I did between these two phones was that I did not flash a based stock rom and install busybox on the 2nd(lost imei) phone ...sending it in to samsung today for warranty repair thanks to chainfire for triangle away! they give you 2nd day air ups each way so hopefully wont take more than a week. will i still flash when i get it back.. yes maybe this time i will install a 1. stock based rom and 2. busybox before going into cwm touch again and flashing cm10, other theory is 3. hardware based differences of some sort.
[T-Mobile, Samsung Galaxy SIII] zmore:
FWIW, I dd'd the first sprint cwm-recovery-lte-sgs3-v5.img to partition 18 (from the no-counter-trip root method), but used it only to do an initial nandroid backup and didn't actually flash anything with it before dd'ing the official d2att CWM touch 5.8.4.7, which I *DID* successfully use to do another nandroid backup (but no restore), and to flash a few small mods, but no full ROMs yet.

Just another datapoint (for whoever's keeping score).

EDIT: And I haven't lost my IMEI (forgot to mention)
[T-Mobile, Samsung Galaxy SIII] lyriquidperfection:
Has anyone tried reflashing a stock firmware through odin and using a pit file to repartition to see if it reinstates imei.

Worth a go as ive not seen anyone else suggest it.
[T-Mobile, Samsung Galaxy SIII] Markdental:
The only threads in TMobile that have had people lose their IMEI are CM9 and CM10 and the ROM Deodeox by ProTekk. I did a full search in development.

Maybe it is a ROM thing?
[T-Mobile, Samsung Galaxy SIII] johnhazelwood:
Have you installed Busybox? I'm going to assume no.
[T-Mobile, Samsung Galaxy SIII] swa2k4:
My imei was fine after rooting using the no trip root Odin. After that I installed cwm touch via Odin. I feel like if coming from stock root and installing this in order to flash a different ROM you should install recovery using adb only if coming from a stock ROM. Did anyone have similar track?
[T-Mobile, Samsung Galaxy SIII] Product F(RED):
Quick question, why do those same one or two people write "d2att" instead of "AT&T version"? I don't get what "d2att" means.
[T-Mobile, Samsung Galaxy SIII] MyronJ906:
Doesn't TitaniumBackup use BusyBox/come with a version of it? If so, then yes. I have BusyBox but have not gone out of my way to install it.

I forgot to mention I have been Titanium Backup restoring apps + data (not system apps or data) from my AT&T One X after every wipe. I have also updated the backups before every wipe so I have a mixture of market apps originally installed/updated on One X and S3. Sounds like a recipe for disaster right?

All running fine

Edit: just checked Titanium. Busy box 1.18.4
[T-Mobile, Samsung Galaxy SIII] drksilenc:
i dont think tb needs a seperate full install of it anymore.
[T-Mobile, Samsung Galaxy SIII] johnhazelwood:
It's the label/build version of CM9 and CM10 for AT&T Galaxy S3 devices. So you'd download the CM9 or CM10 d2att version for our AT&T phones.
[T-Mobile, Samsung Galaxy SIII] MyronJ906:
It doesn't. I edited my post. Titanium does have it included at 1.18.4 but I haven't gone out of my way to install or update busybox any other way
[T-Mobile, Samsung Galaxy SIII] johnhazelwood:
I was thinking TB used to install it, and just checked it does to some extent (1.18.4) for me as well. It sounds like people with IMEI issues are downloading BusyBox separately (outside of TB), which is I guess what I'm asking. Did anyone loose IMEI without installing BusyBox app (not including TB)? More curious speculation as of now.
[T-Mobile, Samsung Galaxy SIII] Igotsanevo4g:
We're really just shooting in the dark we need:

1. A expert developer to research it through his knowledge. (Or wizardry)

2. Standardize rooting method and recovery use until we can, through process of elimination, determine what is causing it.

My .02 cents.
[T-Mobile, Samsung Galaxy SIII] stevessvt:
I installed busybox through the app store, then uninstalled it. On stock rom.
[T-Mobile, Samsung Galaxy SIII] lyriquidperfection:
Here is one way to standardise rooting, install an insecure kernel then use my Samsung Quick Root application:

http://xdaforums.com/showthread.php?p=14754431
[T-Mobile, Samsung Galaxy SIII] Igotsanevo4g:
Has anyone lost IMEI by using your method only? Others have lost simply by rooting, not even flashing anything yet.
[T-Mobile, Samsung Galaxy SIII] lyriquidperfection:
Not been mentioned by anyone which is why I thought it was worth posting.
[T-Mobile, Samsung Galaxy SIII] Igotsanevo4g:
That's a good sign, in hoping for some insight on using your method to root and then using TWRP recovery. Seems those two things haven't been responsible for any imei loss.

Then again, maybe its in the rom? Update binary? Doubt it.
[T-Mobile, Samsung Galaxy SIII] sabre31:
I had my phone on release day and rooted and did clockwork recovery via Odin. I did download and install busy box from play store. I also have rom manager and have flashed through rom manager latest recovery updates for AT& T and still have my imei thank God. However I have not flashed any roms yet because of this thread.
[T-Mobile, Samsung Galaxy SIII] Android_Monsters:
And that's the problem. It's safe to flash. A couple of people who want to know where the imei is stored are fxxcking it up for everybody. There are 2 reasons to want to know where the file is. I like stealing phones, too and I suck at flashing.
[T-Mobile, Samsung Galaxy SIII] johnhazelwood:
I think the people who have lost their IMEI numbers would disagree with you. But feel free to flash away.
[T-Mobile, Samsung Galaxy SIII] ingenious247:
That crossed my mind as well. Hope that's not what's going on here...

Sent from the current Heavy Weight champ GALAXY SIII
[T-Mobile, Samsung Galaxy SIII] Android_Monsters:
Show me how many people
[T-Mobile, Samsung Galaxy SIII] djkinetic:
Personally I haven't experienced this issue and I pray to God that I don't have to, but I've always went back to stock with root when needed by installing the Stock Odin Tar from http://xdaforums.com/showthread.php?t=1739426 then I flash CWM with adb. I've used Sprint CWM, official CWM/CWM Touch, right now running 5.8.4.5 since it has External SD support...I've flashed ROMs from my external and internal SD, done backups and restored backups from my external SD, Flashed CM9 AOKP CM10 DietICS Kyan Rom all without issue, the one time I had a data issue was on AOKP before Task put in the default PTA APN for ATT...Without any official work from Samsung its gonna be pretty hard to pinpoint what the issue is since theres so many different variables at work...GL to you guys, I hope you find a solution soon.
[T-Mobile, Samsung Galaxy SIII] johnhazelwood:
I've personally lost mine on my Captivate (not on this phone yet), and if you look at this thread and the one in the AT&T Android Developer forum you'll see a list of people. Apparently you haven't read the threads and just posted, or overlooked the reported cases. It's definitely possible to wipe it out by just simply flashing something.

Since you do seem pretty darn certain it's not possible, flash away and prove everyone wrong. I'd rather the numerous threads be bogus so I can safely flash CM10 (which I'm dying to do). I personally don't care if I loose my IMEI, but want to be able to restore it like I did on my Captivate.
[T-Mobile, Samsung Galaxy SIII] Android_Monsters:
I read the threads
[T-Mobile, Samsung Galaxy SIII] Android_Monsters:
whoops I flashed super wipe on a phone it wasn't intended for?
[T-Mobile, Samsung Galaxy SIII] mt3g:
Never read anyone report that. Have read plenty from those have experience, and some how screwed up the imei...

T-Mobile SGS III
[T-Mobile, Samsung Galaxy SIII] johnhazelwood:
Definitely a possibility. Especially since the AT&T phone is "similar" to the Tmobile phone and the Verizon Phone and the Sprint phone. Could be that's what's causing the problem. Most people are claiming they are flashing supported ROM's though. They could be lying, they could have walked through a gigantic magnet, anything is possible still (thus the thread). If you search, you'll see loosing the IMEI isn't new. It's happened on the Captivate, Galaxy S2, and now this one. If you've never lost your IMEI before, I could see how you might blame stupidity.
[T-Mobile, Samsung Galaxy SIII] mrmako777:
what is the cause(s) for losing the imei on these devices? if we had a common denominator across past devices, it could be a good starting point for determining what is going on here
[T-Mobile, Samsung Galaxy SIII] freakboy13:
I wouldn't call it stupidity I would say its user error. 9x out ten it usually is.

It doesn't mean your stupid. Like forgetting to turn usb debugging, or disabling fastboot, or even Dl a corrupted file... yes these are considered user error, its not about fault.

Computers are computers are computers...even when they are a mobile device. A computer only does what you tell it to even when you inadvertently do so. Like people who mass-click links or commands when the computer is not responding.

I rooted my phone via Odin. The non trip method, yet my phone says modified. I don't know if it was supposed to or not...and this is user error. I did not read fully, why, and that's most people's problems: not reading fully, skipping steps.

I guessed the basis of my point is why isn't it happening to everyone...

Somehow somewhere there must be some kind of variable causing this.

If you take the imei off your box, you can't put it back manually ?

There has to be a work around for this.

Think I'm gonna hold of on the recovery flashing ....:o
[T-Mobile, Samsung Galaxy SIII] zmore:
It's probably busybox. There's a service on the stock rom that periodically scans for "bad" things like /system/bin/busybox, then flags it modified. Uninstalling busybox and waiting for another rescan (or rebooting) will return the status to normal.

Because the variables are... variable. :) It'll eventually get narrowed down.
[T-Mobile, Samsung Galaxy SIII] modest_mandroid:
Never owned an S2, but it basically boiled down to corruption of the /efs partition on the Captivate. This could happen for a variety of reasons - bad rom flash that dicked around with a partition it wasn't supposed to (CM9 touches /efs, to my recollection), faulty sim-unlock (sim-unlocking also required modifying the contents of /efs), etc. Fortunately, fixing the problem was as simple as backing up a working /efs and restoring it in the event of a problem. That doesn't appear to be an option with the GS3.

I'm a bit out of the loop as far as technical details go with this new phone - having kids does that to a guy :/ Since, from what little I've read, it appears that backing up/restoring /efs does not restore the correct IMEI, I would assume that it's either being read from somewhere else or that the contents of /efs are being restored from a different location on boot. I would assume that flashing roms that only modify the /system partition are fairly safe. As a general safety rule, I don't flash any roms that include their own bootloaders, their own /efs, or anything else that isn't necessary, and you shouldn't either. You can easily check yourself what the rom package includes by extracting the zip archive, looking at the files it includes and reading the edify script that tells the phone what to flash.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
Why would someone want this to say official or unmodified or whatever? If its for warranty you can just triangle away, then flash stock and it will say official... Also you should not have root anyways if you're going to warranty so you should flash stock anyways..
[T-Mobile, Samsung Galaxy SIII] johnhazelwood:
I only had a Captivate, not GS2 (but saw people complain about the same for those phones). I didn't put a lot of troubleshooting into the issue once I realized I could just copy back my nvdata file if it went missing. I want to say it was when I flashed a custom rom, then stupidly went back to stock (usually a custom already rooted version via a one-click odin), and at that point in time it was messed up.
[T-Mobile, Samsung Galaxy SIII] swa2k4:
Everyone can read my previous posts on this and I am going to advise people NOT to flash cwm touch via Odin tar because I have had two phones now mine is working fine been on CM10 for 3 days installed cwm touch via adb. The other one yesterday sadly cwm touch was installed via Odin tar and after CM10 installed lost imei. You can check my signature I have owned and rooted almost every phone experience with Odin and cwm and both Samsung DL mode and HTC bootloaders.

I'm not saying this is the only cause but it was a cause on a brand new phone that is now headed to Samsung for repair!
[T-Mobile, Samsung Galaxy SIII] mobilehavoc:
I think using DD is safest way because you are literally piping data from one location to another. DD is a Unix system binary and used in Unix environments including desktops and servers. So I agree using DD is safe as long as you know what you're doing.
[T-Mobile, Samsung Galaxy SIII] johnhazelwood:
Good point, stupidity was a little overkill.
[T-Mobile, Samsung Galaxy SIII] mrmako777:
youre the 3rd person ive seen who lost their imei that mentioned cm10. not saying thats whats causing all this, but just an observation
[T-Mobile, Samsung Galaxy SIII] SiNJiN76:
Maybe a Poll should be made...that way we can kind of keep track of How many people this has affected so far. Along with the recovery they used. Version number as well. And How long they've been using that recovery before the zap.
[T-Mobile, Samsung Galaxy SIII] modest_mandroid:
Just putting this out there because I haven't seen it mentioned in this thread yet and because I've seen people mentioning mps_code.dat:

/efs/imei/mps_code.dat doesn't contain anything useful. Issuing 'cat /ets/imei/mps_code.dat' outputs 'ATTapp_18'. The IMEI is stored somewhere else.
[T-Mobile, Samsung Galaxy SIII] androholic:
I have an off topic question for you. I know busy box performs a number of Linux commands and background processes, but why do we install it. I always install it, I'm not so much interested in all its functions because I know there are many, but the hy do we install it as soon as we root? I more or less do it blindly out of habit & I'm rather unclear on what it needs to be there for.
[T-Mobile, Samsung Galaxy SIII] modest_mandroid:
Some like it because it provides a lot of the functionality you typically get with bash on a full linux machine. There are also a few useful apps that require it to run properly, like Titanium Backup.
[T-Mobile, Samsung Galaxy SIII] zmore:
We install it because quite a few root apps require, or just work more simply, when the extra powerful tools are there, so they don't have to reinvent the wheel in java.

That reason aside, *I* install it mainly because I use the adb shell all the time and can't live without many common utils like find, grep, wc, less, etc.

edit: and md5sum, sha256sum, head, tail, vi, and others... (type "busybox" for a full list of supported utils)