yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] flipster64:
Yup.

It's an IMEI problem. :(

So ... now I have to figure out how to put it back. I've generated one using that SG3 IMEI program.

I wonder if there's a chance the previous owner backed it up. There's a folder I read it creates. Need to go find that again. Not holding my breath.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
I'm going to upload some tools with instructions that will help. I'll PM you the link when I'm done.

---------- Post added at 04:01 PM ---------- Previous post was at 03:44 PM ----------

Alright, PM sent. That should get you taken care of. Once you get it fixed, make sure to follow the instructions in my original post regarding IMEI backup. Following that procedure should prevent it from getting corrupted again.
[T-Mobile, Samsung Galaxy SIII] flipster64:
It is as if the phone has no modem.

Went into *#7284# and set the QUALCOMM USB Settings to RMNET + DM + MODEM

The device shows up on COM10

QPST RF Nav lets me pick COM10, but when I go to read it says it can't issue the command because there's no phone present.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
If you haven't already, try installing samsung kies. It might be a driver issue.
[T-Mobile, Samsung Galaxy SIII] flipster64:
I had uninstalled Kies and SnapPea, but left the driver. I'm re-installing the driver (it said it was already installed, but I'm doing it again).

Also just just flashed the modem version that came with the phone since I'm back on 4.1.2... just in case.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
If you still run into problems, you might want to try restarting your pc and try a different USB port.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Got called away on emergency babysitting stint, so didn't get much further. Just got back.

Kies won't connect to it. Going to flash the UC modem back, see if that helps. If not, I'll flash another rom onto it and try this recovery again tomorrow.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
I wish you luck. Talk about going head first into this hobby. Losing your IMEI first go... It reminds me of my first run rooting my old my touch 3g side.
[T-Mobile, Samsung Galaxy SIII] flipster64:
I have the older version of Samsung Kies installed supposedly for phones from before Sept 2013, which mine is. Used to work. Now it says the phone's incompatible. My guess is that it has something to do with my having flashed 4.3 onto the phone at one time.

RF NV manager just won't talk to the phone. The phone shows up in device manager on a com port (COM10 at home, COM7 here at the office) ... but you can't pick it from the SETTING dropdown for COMPORT (COM1 shows up, but nothing else). You can type it in, though, and it shows up at the bottom as COM7 being what I'm using.

But I can't read from the phone.

I am seeing in my network adaptors a SAMSUNG MOBILE USB RMNET Network Adapter Driver ... which says it's up to date but it can't start for some reason.

I have an XP machine at home ... I'm starting to think maybe I need to try it on that puppy. It hasn't had any other software installed on it, and has less of the gobldygook security hoops Windows 7 has.

You wouldn't happen to know if the EMEI tools are supposed to be compatible with 4.3, would you? I'm thinking of flashing back to a clean 4.3 since we know it's an EMIE problem anyway. But I'm torn. I've been fruitlessly hunting around for a 4.1.2 T-Mobile Stockmod ZIP for CM thinking more tools might be friendlier to 4.1.2. But I've about given up there.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Correction ... I do not have to start the application for the driver to go into failed mode in device manager, it just takes a minute or two after I connect the device.

If it doesn't work on my XP where no previous drivers for the phone have ever been installed (I'll try it ... hopefully soon) then I'll have to assume it's a problem with firmware on the phone, and I'll have to try to build the phone from the bottom up.

Is there a tutorial about that?
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
What ROM are you currently on? CM or the 4.3 touchwiz?
[T-Mobile, Samsung Galaxy SIII] flipster64:
The recovery program I'm using is PhilzTouch v 6.0.4.5.

The ROM that's currently flashed (with that recovery program) is the 4.1.2 zip I downloaded through this page

http://xdaforums.com/showthread.php?t=2276645

I think I'm still running the UVUEMJC modem -- the UVDMD5 modem didn't seem to make any difference, and I think you said either modem should work with the 4.1.2 OS.

I also downloaded the Samsung Drivers for XP directly to an old XP laptop I have at home that's never seen this phone or any other, installed it. It recognizes the phone as an SGH-T999, and loads the RMNET driver just like windows 7 does, and just like Windows 7, after a minute or so the device in device manager goes to an error state "This device cannot start".

So it's something in the phone firmware.

One thing I don't have completely reconciled is that the phone identifies itself in recovery as an SGH-i747, but it is labeled on the IMEI sticker and elsewhere and it was sold as an SGH-T999. I've seen it recognized as an i747 before installing drivers, and after installing drivers as a T999. From what I've been reading, this should not make a difference, but it does bug me a little.

So ... what I think I need to do is find a way to replace everything from the boot loader on up, if that's possible. I was once equating the boot loader with CM (or Philz) ... but I'm beginning to understand there's more to it than that.

If I flash a bootloader, will it overwrite/replace Philz? Or will Philz still be there?

I'm looking at this as a possible starting point.

http://xdaforums.com/showthread.php?t=2282603

Whatever handles RMNET needs to be replaced or I'll never be able to fix the EMEI with these tools. I read that RMNET interfaces with the modem, but I don't know if it's part of the modem flashes and I kind of doubt it. But I really need a crash course in Android architecture and what most CM flashable zips actually replace and what they don't, and how to replace some of the stuff they obviously don't. Like RMNET firmware, it seems.
[T-Mobile, Samsung Galaxy SIII] WhoWhere:
With you being on a ROM with a proper build.prop you should be able to Odin a root66 image. You can certainly give it a shot. Just remember not to use the latest 4.3 package.
[T-Mobile, Samsung Galaxy SIII] flipster64:
I *had* used CM to put a deknoxed version of 4.3 on it at one point ...

Well let's see if Odin will flash that now without derping out on sbl2 as it has been doing.

And by "that" I mean a 4.1.2 image.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Well, it's different, at least. Still failed.

<ID:0/006> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> root66_TMO_T999UVDMD5.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> aboot.mbn

<ID:0/006> NAND Write Start!!

<ID:0/006>

<ID:0/006> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Why do I have Jethro Tull's Thick as a Brick going through my head right now?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Silly question, was the phone in download mode when you tried that ? If yes then remove all drivers and reboot the pc. Next connect the phone to pc in download mode. Without running odin, let the drivers install and bypass the warning if needed.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Yes.

I haven't tried it, but I assume it wouldn't come up on a COM port in Odin if it wasn't, but yes.

I'm taking a good hard look at this thread

http://xdaforums.com/showthread.php?t=2282603

... but there's that warning about

DO NOT flash this if you are running latest 4.3 (*MJC) firmware. It WILL brick your device. Currently there is NO way to downgrade from MJC firmware without a brick due to the Knox security stuff added to that firmware release.

I did flash, a couple days ago, the 4.3. *MJC firmware ... but it said it had been de-knoxed. At any rate, I'm on *MD5 now, and running 4.1.2 ... I think. I haven't had the guts to see if it'll boot up since that last failed flash. So I'm not technically "running" *MJC.

I had installed Kies yesterday. Just uninstalled it and I'm trying to flash the root66 MD5 tar again now.

Oh, also using Odin 3.07 this time instead of 1.85.

Fingers crossed....
[T-Mobile, Samsung Galaxy SIII] flipster64:
Ok, less verbose this time, but....

<OSM> Leave CS..

<ID:0/006> Odin v.3 engine (ID:6)..

<ID:0/006> File analysis..

<ID:0/006> SetupConnection..

<ID:0/006> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)

Just rebooted and 4.1.2 still comes up ... so not technically bricked yet....

Let me try rebooting into download mode again ...

I *know* I can brick this thing yet! :cowboy:
[T-Mobile, Samsung Galaxy SIII] flipster64:
Went to control panel, uninstalled the residual samsung driver, rebooted, plugged in ... winders downloaded drivers.

Started Odin again ... now we're back to FAILED (Auth) as we were getting earlier this week, only on aboot instead of sbl2.

<ID:0/006> Initialzation..

<ID:0/006> Get PIT for mapping..

<ID:0/006> Firmware update start..

<ID:0/006> aboot.mbn

<ID:0/006> NAND Write Start!!

<ID:0/006> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1)

I have the drivers downloaded directly from Samsung's site now. Have not installed that package yet (I'm back on a windows 7 machine today). I still suspect it's something with the boot loader stuff on the phone itself.

The driver I uninstalled before I rebooted was v 1.5.33.0 ... which is the same version I downloaded just now.

I see the driver for the i747 is v 1.5.14.0

It still bugs me that the download mode screen identifies the phone as an i747.... Does yours do that?

Attached a photo of my sticker (blurred out the fccid and the imei)
[T-Mobile, Samsung Galaxy SIII] flipster64:
Hmmm ... check this out:

http://xdaforums.com/showthread.php?t=2088220

But it won't help me ... mine would be working had I backed up my IMEI ... need to figure out how to replace the firmware that makes it think it's an i747.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Well I briefly went through this thread. I am not sure I am completely up to speed. Do you care to summarize for me what you need to do ?
[T-Mobile, Samsung Galaxy SIII] flipster64:
Summary is, bought a "refurbished" t999, T-Mobile branded (on the outside). My carrier is T-Mobile.

It came with an modded ATT 4.1.2 build on it which didn't have wifi calling. So I went to find a T-Mobile build. Installed a new Philz Touch version of CM.

Tried to flash root66 tar.md5's with Odin, but Odin kept aborting at sbl2.mdn, (downloaded from here: http://xdaforums.com/showthread.php?t=1949687)

I noticed download mode in my phone said SGH-i747, and the build.prop file was ... very odd (though it did say it is an SGH-T999, it had att settings for Canada). Decided to try to get a good TMO 4.1.2 flashed on there, and found I could do it with CM and a zip file. It said to be sure to flash an UVUVMJ4 or UVUEMJC modem first. It had a link to an UVUVMJ4, so I flashed it, and then flashed a deknoxed 4.3 (http://xdaforums.com/showpost.php?p=46872485&postcount=2&nocache=1&z=69548066239804)

It came up, but the IMEI had been wiped.

Restored a CM Backup of the OS I made before I started all of this to make sure it was really an IMEI problem. It is. Still gone after that restore.

Tried going back to a UVDMD5 modem ... no help.

Tried a tool that is supposed to allow me to backup/restore IMEI's (in conjunction with a tool to generate one using the number on the sticker) ... but the backup/restore tools won't talk to the phone (couple of different NV items reader/writers) ... they apparently use RMNET, and the Windows Samsung RMNET driver dies after the phone's been hooked up for about a minute saying it can't start.

Then flashed a close-to-stock mod of 4.1.2 (wiped cache and user data first) -->http://xdaforums.com/showthread.php?t=2276645 ... still has the UVUEMJC modem on it. Still no luck. Odin gets farther on a root66 4.1.2 TMO tar.mdz ... stops at aboot now (tried this on two Windows 7 computers and a WinXP as well)

It's got something to do with some very low level, maybe boot-loader level files that Odin is cacking up on.

So ... what I need to do is find the "safest" way to rebuild this phone from the lowest level I can back up to a close-to-stock 4.1.2 TMO ROM, and see if I can THEN use the tools to re-generate and write my IMEI back to the phone. At that point I'll back everything up (assuming we get that far, including IMEI) and probably go to the root66 4.3 build.

I'm looking at this as a possible starting point:

http://xdaforums.com/showthread.php?t=2282603 <-- (originally posted wrong link. Fixed now.)

But I'm a bit leery because I don't really understand what does what in this architecture, but I see it replaces sbl2 and aboot. I'm concerned about the warning about bricking if you had 4.3 installed on it, but the warning concerned Knox, and the version I had installed was a de-Knoxed version ... so it may be fine.

I'm pretty much down to the problem being Odin and NV reader/writer not liking something they're seeing in the phone's firmware -- in files that obviously aren't replaced when you flash a zip style ROM with CM.

Am I making sense?
[T-Mobile, Samsung Galaxy SIII] flipster64:
After reading more, charging ahead.

I went ahead and tried to load the T999_UVDMD5_firmware.zip in the article above.

It fails on the assert in the first line of the script:

assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");

And yet, if I go to my /system/build.prop, both ro.product.device and ro.build.product are set to d2tmo.

So how is it failing? Does getprop read something other than build.prop?

# begin build properties

# autogenerated by buildinfo.sh

ro.build.id=JZO54K

ro.build.display.id=JZO54K.T999UVDMD5

ro.build.version.incremental=T999UVDMD5

ro.build.version.sdk=16

ro.build.version.codename=REL

ro.build.version.release=4.1.2

ro.build.date=Mon Apr 15 11:54:03 KST 2013

ro.build.date.utc=1365994443

ro.build.type=user

ro.build.user=se.infra

ro.build.host=SEP-128

ro.build.tags=release-keys

ro.product.model=SGH-T999

ro.product.brand=samsung

ro.product.name=d2tmo

ro.product.device=d2tmo

ro.product.board=MSM8960

ro.chipname=MSM8960

ro.product.cpu.abi=armeabi-v7a

ro.product.cpu.abi2=armeabi

ro.product_ship=true

ro.product.manufacturer=samsung

ro.product.locale.language=en

ro.product.locale.region=US

ro.wifi.channels=

ro.board.platform=msm8960

# ro.build.product is obsolete; use ro.product.device

ro.build.product=d2tmo

# Do not try to parse ro.build.description or .fingerprint

ro.build.description=d2tmo-user 4.1.2 JZO54K T999UVDMD5 release-keys

ro.build.fingerprint=samsung/d2tmo/d2tmo:4.1.2/JZO54K/T999UVDMD5:user/release-keys

ro.build.characteristics=tmo

# Samsung Specific Properties

ro.build.PDA=T999UVDMD5

ro.build.hidden_ver=T999UVDMD5

ro.build.changelist=1128078

# end build properties

#

# system.prop for surf

#
[T-Mobile, Samsung Galaxy SIII] Perseus:
Ok here's the thing. First flash UVDMD5 modem from this thread. Then do a factory reset. Next remove all samsung drivers from the PC. Reboot the PC. Put the phone in download mode. Connect it to the PC using original Samsung cable. Make sure Odin and KIES was not running. The drivers will install potentially with a bypassable warning.

Once the drivers are installed, reboot the pc again. Try Odin 3.07. This time find the correct PIT file for your phone. Use that as well as Root66 UVDMD5 file. Uncheck Auto-Reboot in Odin. Post the results.
[T-Mobile, Samsung Galaxy SIII] flipster64:
I've done most of this before ... with the exception of the PIT file ... I saw a PIT file ... I'll look and see if I can find wat you're talking about.

I imagine I can.

I get the feeling an Odin tar.MD5 flash is more "complete" than one you load via recovery with a zip? Is that the case?

I'll get on it. Probably tomorrow. I'll update when I try.

Thanks!
[T-Mobile, Samsung Galaxy SIII] flipster64:
Uninstalled everything having to do with Samsung

Found an SGH-999 PIT file here: http://d2tehp.chickenkiller.com:22222/android/pits/ (via thread which had a bad link, but I figured it out ... had to add /android http://xdaforums.com/showthread.php?t=1848267)

Flashed the UVDMD5 modem.

Launched Odin 3.07, unchecked auto reboot. Browsed for PIT file and root66 UVDMD5.

Tried to flash, but forgot to turn the phone on ... so ... turned it on, got it in download mode, did the flash, and here's the Odin log.

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> root66_TMO_T999UVDMD5.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<OSM> All threads completed. (succeed 0 / failed 0)

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> aboot.mbn

<ID:0/004> NAND Write Start!!

<ID:0/004> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1)

Dies at aboot.mdn again.

Download mode screen says

SECURE CHECK FAIL: PIT

SECURE CHECK FAIL: aboot
[T-Mobile, Samsung Galaxy SIII] flipster64:
Tried again to just partition with the PIT file and not flash the rt66 rom.

It won't repartition. Download screen says SECURE CHECK FAIL : PIT

Download screen also still says it's an i747, so wherever it's getting that hasn't been wiped/replaced with all the reformatting from factory resets, etc.

<ID:0/004> Added!!

<ID:0/004> Odin v.3 engine (ID:4)..

<ID:0/004> File analysis..

<ID:0/004> SetupConnection..

<ID:0/004> Initialzation..

<ID:0/004> Set PIT file..

<ID:0/004> DO NOT TURN OFF TARGET!!

<ID:0/004> Get PIT for mapping..

<ID:0/004> Firmware update start..

<ID:0/004> RQT_CLOSE !!

<ID:0/004> RES OK !!

Ok, this is interesting. I let it sit for a bit, and got this (but it might just be the time reset - can't ignore the FAIL on the PIT, but ...)

<ID:0/004> Remain Port .... 0

<OSM> All threads completed. (succeed 1 / failed 0)
[T-Mobile, Samsung Galaxy SIII] flipster64:
Something funky about the pits on that site ... when I click on them, they open in the browser. Binary gobbledygook, which isn't surprising. So I downloaded them with "Save Target As"... and it wants to download them as HTM (weird). I set the file type to "All Files" and then I have to add the .pit extension at the end ... so I might not be getting a valid PIT file. They're 4K. Have familiar filenames in them (such as aboot, etc) ...
[T-Mobile, Samsung Galaxy SIII] flipster64:
Got pit via DocHoliday collection here : http://www.androidfilehost.com/?w=files&flid=6471

MD5 checked, and same result. :-/
[T-Mobile, Samsung Galaxy SIII] Perseus:
You should have connected the phone in download mode before running Odin. I had specifically said that. Clearly that didn't happen. You have also not answered my question. If you wish to do research on your own, more power to you. Without additional information, I am not able to help further.
[T-Mobile, Samsung Galaxy SIII] flipster64:
True. And I was sure that I had it in download mode, too. But it wasn't this time, it was a derp on my part. I can go do it again. I'm assuming you're saying Windows will download different drivers if it sees the phone first in download mode than if it sees the phone booted into Android.

As to your question, the only question I saw from you was your first post from yesterday -- if I had the phone in download mode when I tried flashing with Odin, and I did answer it in the affirmative in my very next post.

Yes, it was in download mode.

I am doing research, of course -- there definitely seems to be a culture here of an expectation that a person asking a question do research and not just ask questions and expect someone to come fill someone in on everything without effort on their part. I am trying very hard to understand how all this works, and I'm looking for input as much as anything else.

I think it's pretty clear there is something abnormal about the state of this phone. I've read about a couple of T999's that showed up as i747's and one i747 that showed up as a T999 ... those cases were resolved by flashing ROMs. I can and have flashed ROMs that work fine, but my IMEI was wiped. Those other people didn't need to restore their IMEI's. If I didn't need to restore my IMEI, I'd be done now. I can't seem to flash a full tar.md5 rom with Odin -- though I flashed CM with Odin the first time. This is why I went to zips and Phiz ... I've tried on three different machines to flash full tar.MD5 ROMs with Odin, and they all fail. I flash zip ROMs with Philz. But I can't get the RMNET driver to work properly to use the tools to restore the IMEI, which is ultimately the goal here.

I will go again and remove any drivers I can find and plug it in in download mode and see if it behaves any differently.
[T-Mobile, Samsung Galaxy SIII] flipster64:
Ok, went through and uninstalled drivers via device manager, telling it to delete the driver file when it uninstalled. Then for good measure went and looked through the Windows\System32\Drivers folder and found and deleted the two driver files, since Windows neglected to do it. Rebooted.

Put the phone in download mode. Plugged it in to the USB port. It re-downloaded files (took a bit, but no warnings) It loaded Samsung Mobile USB Modem and USB Composite CDC device shows up under USB ports. -- both Driver version 2.11.7.0 dated 1/2/2014, Same ones that were running before, same two filenames I deleted after uninstalling and before rebooting. Same size. Same create date. Same version.

Nothing under ports. No Samsung Galaxy S3 device. Nothing under portable devices. So no additional drivers loading.

Same result.

<ID:0/003> Added!!

<OSM> Enter CS for MD5..

<OSM> Check MD5.. Do not unplug the cable..

<OSM> Please wait..

<OSM> root66_TMO_T999UVDMD5.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

<ID:0/003> Odin v.3 engine (ID:3)..

<ID:0/003> File analysis..

<ID:0/003> SetupConnection..

<ID:0/003> Initialzation..

<ID:0/003> Set PIT file..

<ID:0/003> DO NOT TURN OFF TARGET!!

<ID:0/003> Get PIT for mapping..

<ID:0/003> Firmware update start..

<ID:0/003> aboot.mbn

<ID:0/003> NAND Write Start!!

<ID:0/003> FAIL! (Auth)

<OSM> All threads completed. (succeed 0 / failed 1)
[T-Mobile, Samsung Galaxy SIII] flipster64:
Anything stick out at anyone here?
[T-Mobile, Samsung Galaxy SIII] Perseus:
It was other question I was referring to. The Part where you see I747. Can you take a photo of that and post here ?

As to Odin If the Re-partition checkbox came on when you selected the PIT file then let it be. But based on your error, I think the PIT file is bad. I will take another look at the thread you had linked. Here in the Q&A Forum, please search for PIT file related question. I recall I had someone else here little while back with partition issue. They had linked a corrected file that worked for them. Don't try this PIT file again. I need to see where you get I 747. Also your phone should be booting to UVDMD5. If so, please do so and look under Settings > About for Model Number.

As far as culture is concerned, you are right, it is an expectation of the users to do their own research. Afterall this is a developer forum not user forum.