yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Just read the entire OP please. All of this should be clear once you do. As in each of the questions youve asked couldve been answered just by reading it in the first place.

I'm not trying to come down hard on you, but it should be relatively easy to figure this stuff out. IF you read the whole op, you would see a heading for the Canadian variants along with information regarding them.

If you are still confused you need to stop and do some research so you know what you are doing and why. If you don't know what something is, search the thread, google the term, read the beginner guides here on xda.

Though I don't explicitly state every little detail, I do post in such a way that it should be easy enough to determine what I have posted.

These tips will help you in the future if you heed them. Always read the entire OP if you want to use something from it. Then before asking a question, try to answer it for yourself.

I truly mean no offense to you, but if you need someone to walk you through each and every step like this, you are in the wrong place. While most of us are happy to help, we do expect people to try to help themselves first. And then we prefer to help you help yourself as opposed to just doing something for you.

Anyway, like I said, read the Op and I highly recommend you also read the following few posts, and then search the thread for your questions, followed by searching xda and then google if you still have unanswered questions. Then, ask us if you still can't find it.

Sorry for the long post, as I said, my intent was not to offend, but to help.

Good luck!
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
:thumbdown:

Sent while sleeping in chair.
[T-Mobile, Samsung Galaxy SIII] shenry1307:
+2
[T-Mobile, Samsung Galaxy SIII] Ditamae:
Thanks for this thread, Doc! It's been super helpful.

I recently changed ROMs, moving from SlimBean 4.1 to the latest build 4.2.2. I've stuck with the LJA bootloader and experimented with the LJC and MD5 modems. But since making the jump to 4.2.2 my speeds appear to have been reduced by half. Previously I was getting about 20 Mb/s down and 5 Mb/s upload - with some fluctuation, obviously. But since moving to 4.2.2 I'm lucky if I see anything over 10 Mb/s and 2 Mb/s. I've edited my build.prop with the same values found in this thread (just as I had on 4.1). I'm not sure what could be at play here...

Do I need to update my bootloader? I was hoping to avoid that hassle...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Maybe not. I would first make a nandroid of your current setup. Then flash back to your previous and test speeds there. If they stay low its probably a network issue (tower maintenance, congestion, recent upgrade, etc).

If your speeds go back up, then go ahead and try the MD5 firmware just to see. If that doesn't help I suggest going back to LJC or LJA even. Its actually quite easy to switch around as there's a dev thread with recovery flashable firmware. Ill post a link in a few.

While you're at all of this, you may want to flash another rom or two to test them out. Thisll help you determine if its actually a problem with your current rom or not.

If you still don't get anywhere, let me know and ill see if I can think of anything else.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
http://xdaforums.com/showthread.php?t=2282603

Firmware thread
[T-Mobile, Samsung Galaxy SIII] Ditamae:
Thanks so much for all the great suggestions. I wasn't aware there was a flashable zip for firmware that didn't require returning to stock first. Perfect! Great ideas...

One more quick question... when I flash back to my 4.1 nandroid and then again to 4.2, will my internal storage stay in its present location? It sounds like the latest Recoveries remedied this issue, but I have a feeling you know for certain... ;)

Thanks again!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Tbh, I'm not certain. I want to say yes, the latest recoveries addressed this, but I'm not positive as I don't use any of the 4.2.2 roms much.
[T-Mobile, Samsung Galaxy SIII] Ditamae:
Oh really... mind if I ask why? I waited a good 6 months before deciding to give Slim's latest stable release a shot. Many of my reasons were minor aesthetic preferences and a lack of interest in new changes/additions.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Mostly just personal preference. But also, I often don't use any roms. I'm always messing with my own, just learning what I can.

But I will also say that in my experience I always seem to get better performance, battery, stability and overall usability out of stock based roms. I'm just more into the overall functionality.

To each their own....
[T-Mobile, Samsung Galaxy SIII] Ditamae:
For sure. :) Thanks for sharing... and again, many thanks for maintaining this thread.
[T-Mobile, Samsung Galaxy SIII] nafeasonto:
Guys weird question.

I normally live in New Jersey and the UVMD5 works fine for me. However I am vacationing in Province town, MA and my signal is extremely crappy and bad. I don't really care about data, just to at least make a decent phone call..

Anyone recommend a radio for this area even if it's OLD.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I know its a bit of a mess, but poke around in the map to see uf anyone reported for that area.
[T-Mobile, Samsung Galaxy SIII] RoxAbout:
Idea to try....

Sorry Doc I've had a rought 3-4 weeks since my last post! between work taking me out of town and my RL interfereing ...LOL

Any ways In the time since testing all of the modems...I came across a thread that gave out an interesting code to dial in for the SGS3.

This code allows you to pick the right band/freq that works for you from the availible bands [edge - 2g - 3g - 4g - Lte! After playing with the various freq's [as opposed to changing modems] I've had the best luck on 4g 1900.

DISCLAIMER: DO NOT BLAME ME IF YOU SCREW UP YOUR PHONE!

Open the dialer and enter *#2263#

When you enter the last# you will get a menu Write down your settings! Use the menu button for more options, the back button will exit!

There is no need to reboot before testing on speedtest.net app.

Update:

On a trip away from the city ...I went to call someone that I could normally get signal and call from the spot I was at...I had no signal! so I quick punched in the code...hit auto [default setting] and bingo got signal.

Now if someone knows of a way to know what band/freq your currently [the phone] on that would be an awesome tool with this code!

:laugh::good::fingers-crossed:
[T-Mobile, Samsung Galaxy SIII] kpraytor:
I hope this isnt considered a necro post... I attempted to do this on my phone running SlimBean Build 8 (4.2.2) and it says "Connection Problem or Invalid MMI code". Did I do something wrong or does it just not work on my phone. I, obviously, have a TMO S3 on the TMO network.

Also, I hope this isn't a noob question: can I use radios listed as "4.1.1" or "4.1.2" with my 4.2.2 ROM? I would like to try a new radio or two but I have no interest in soft bricking or otherwise.

Thanks again!
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
Error message because you are on AOSP. Those are TW commands.

Any modem, any ROM.
[T-Mobile, Samsung Galaxy SIII] kpraytor:
Are you aware of any commands equivalent in AOSP?
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
They don't exist.
[T-Mobile, Samsung Galaxy SIII] thompsd:
Just a quick follow up on this thread, I also moved to SB 4.2.2 and saw a drastic reduction in modem performance, typically at work it's 4g pretty much where ever I go in the building, with 4.2.2 rom it dropped to edge if at all, I'm currently using UVDLJC. Just to check I restored the 4.1.2 rom (Wicked) and speed and connectivity where right where I left them. Also noticed that the battery drain was much greater with SB 4.2.2, everything else worked well and no issues on wifi. I didn't mess with flashing any other radio's, not enough time to play with this.
[T-Mobile, Samsung Galaxy SIII] Ditamae:
For what it's worth, I ended up flashing back to my original modem (DLJA) with the matching bootloader (I never changed firmware). After 24 hours my speed tests jumped way back up to 25 Mb/s downstream. They're not consistently that high, but they are better. Upstream is another story. :\ Battery life has been excellent for me on SB 4.2.2 build 7. Almost better than 4.1. Good luck.
[T-Mobile, Samsung Galaxy SIII] xenine:
my s3's battery gets drained a lot from the modem.. which modem do u guys recommend saves battery the most?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Whichever one gives you the strongest signal, probably.
[T-Mobile, Samsung Galaxy SIII] xenine:
anyone who really knows?

my s3's battery gets drained a lot from the modem.. which modem do u guys recommend saves battery the most?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
It's going to be different for everyone. Only thing we know for sure is the md5 modem doesn't always play well if it's mixed with other builds. Aside from that it's really up to you to test.

What makes you suspect the modem is the cause of your drain?
[T-Mobile, Samsung Galaxy SIII] tzvblsm:
Can someone help me I am using my phone with Att what modem should I use
[T-Mobile, Samsung Galaxy SIII] Ksunnyv1011:
As long as you have the T-Mobile version I recommend using the latest.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Only use modems specifically for your model device. No way for anyone to tell you which is best. It's different for everyone. The best one for me, may be the worst for you.

Some people have reported battery drain issues with the latest modem, MD5. This usually occurs if you are running a Rom from a different build, or if you're using mixed firmware. If you are on a stock Rom based on the md5 build, and also are using md5 firmware, then this shouldn't affect you.

Not everyone reported those issues btw. And the extent of the drain seemed to vary from person to person.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Well for what its worth, actually MD5 has been also reported to heat the phone pretty well. Even when everything is stock. This seems to be the case especially when you are on Data more than Calls. a little spot of undervolting seems to make it go away. Of course depends on your kernel.
[T-Mobile, Samsung Galaxy SIII] ronnyhawks:
I'm getting mixed inputs here. I have a t999 T-Mobile Galaxy S III and every time I update my Cyanogenmod ROM (which I've been doing for years) everything goes smooth but when the device boots up, it says "unknown" for the baseband version. If I flash the UVDMD5 radio it goes back to normal. But every single time I flash a new nightly this happens. Just wondering if this is a fix for that or if there I no fix. I rooted with the stock root injected .tar file just like I've done 3 separate times. This is the only one of my 3 S3's that has done this. I confirmed that it was NOT a t999L model before anything. Is there a possibility that this device could be a non t999 without saying it is? Or is it possible that this is a t999L model without showing that it is? I'm very lost here. Nobody seems to have the same issue as me. I've searched through hundreds of thread pages to no avail. Help please somebody?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Quiet possibly it may not be a T999. It could be T999L or the ATT Version 747 or even worse the International version i9300. I'd go back to the stock rom it came with and then check the build ids. If it does show up that its a T999, then either the CM build is wiping your modem or it could be

a bad antenna on the phone. Contact the seller for replacement.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I already replied in the other thread you posted in. This is why you should only post a question once. Only repost like this if it's been a day or more w/o a response.

I'm copying my reply here though because your problem is more related to this threads broader scope than the others more specific topic. I suggest that the discussion only be continued here, unless otherwise determined it should be posted elsewhere.

I've no idea why it would do that. Sounds like some sort of Rom issue maybe? If it was anything but a T999, the md5 modem would not work btw. But I've never heard of thus before, so it could be some sort of unknown corruption somewhere in another partition. Purely a guess on that though.

If you Odin back to the LJA, or any other build does it still do this? Does it happen when you flash any Rom? Or just cm? If it's only cm, then I'd ask in the Rom thread as well. What about other kinds of flashes, such as kernels, recoveries and mods have you done? Did the same happen when flashing those? Have you tried a different recovery?
[T-Mobile, Samsung Galaxy SIII] ronnyhawks:
Thank you both for your responses. Originally the device came from Asurion as a replacement for my T999. I verified that it was currently on the newest modem and build before searching for the corresponding root injected stock .tar file. As this device was no different from the last ones I had, I used the same file that I did for the previous devices since I already had the huge file on my computer. It booted up to stock with root and I downloaded Goomanager from the Play Store and flashed TWRP. I then downloaded the d2tmo latest nightly and the 4.3 GApps package from the goo.im website. I booted TWRP and made a backup. I then boot back up and back to recovery before I go wiping everything. (to make sure Root Explorer actually has the file and I can find it. Long Story) I then booted to recovery and wiped data/factory reset, wiped cache and dalvik, then flashed the ROM and then the GApps then wiped cache/dalvik then rebooted. No other ROM or kernel or modifications have ever been made to the device. Only CyanogenMod and the GApps have ever been flashed besides the modem that I have to flash every single time the device gets a new nightly flashed. And I only flash the nightly not the GApps. So I'm lost. Other than this issue the device works properly. I even flashed the new TWRP 2.6.3.0 and it still does it
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I honestly have no clue why it would be doing that. But the best advice I have for you is to Odin flash the Stock/root66 firmware. Test to see if it still happens. And at this point, if you haven't, back up your NVBACKUP data!!! (Make sure IMEI, network data, GPS, etc all seem to be working first)

Install Terminal Emulator and enter this:

su

reboot nvbackup

It'll reboot and create the on device backup.

After this try a different Rom and see if it happens there. If not try cm again. If it only occurs on CM, then the only solution is to report/ask about it in the thread, and find a different Rom for now.
[T-Mobile, Samsung Galaxy SIII] RoxAbout:
Signal issues

Guys Where I live the service sucks and when we got "new 3g" phones 3 1/2 yrs ago the retention dept sent us the 3g [rs1] signal boosters...

skip to now..

Service still sucks and I happened to be on the complaint line regarding a different issue... and mentioned that the signal was crap and did they have a 4g signal booster as all we had was an old 3g booster and new 4g phones. The lady said yes and sent me the new booster [rs2] ...

Tech support ended up putting in a trouble ticket for someone to go look at the tower as the new booster didnt fix it!

So if you live in a single family house...they can send you a booster...just complain!

I will find out next week [the tower people are super busy apperantly] how things improve if at all and let you know the results.

Oh and the tech let slip [not sure I believe him] but he said that the sgh-999 has lte built in and that they have not sent out the software to turn it on yet...unlike the note 2 that they did send out a software patch to turn on the lte!

Will report back on improvements if any...Has anybody heard that about our phones sgh-999?

rs1/rs2 = cel-fi part numbers, google tmobile signal boosters.

hope this is in the right place to post...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
T999......LTE??....T999??....LTE...........................NO! Sorry man, but this has been extensively covered several times! I personally spent quite a few hours on research into this and have made several detailed posts about it. It is not going to happen. It could not happen. It would not happen. The proper place for this is in the LTE discussion thread Stickied in General. But mind you, its an old thread, and for the vast majority of people, the subject is dead!

And for those of you who may read this and have an overwhelming urge to post your points again, trying to convince people of something that is not true. Dont! There is a place for that, and it is not in the Baseband thread!

Thank you for mentioning the signal boosters though! Someone had been saying a while back that T-Mobile was no longer going to allow this. I was skeptical, but its good to know for sure! Looking forward to hearing your experience with it.

But if you are having network issues, try some of the modems. They probably wont give you any fantastic improvements, but you could probably find a couple that do better than what you have now. As stated in the OP though, it is up to you to test for yourself. No one else can tell you what the best one for you will be.

My best advice for you, try some modems, and forget you ever heard anything about the T999 having LTE! It is impossible. And even if it were, it would be illegal!
[T-Mobile, Samsung Galaxy SIII] fornoggg:
I read the instructions, especially about only using this on my own model, but I'm going to ask about this anyway.

I have a I747m model galaxy s3 on a Rogers network. I want my modem to pick up the t mobile frequency so I can bring my phone to the States and buy a temporary SIM for use when I'm over there on business. Now I know I'm not supposed to flash this modem or anything on this forum, but hear me out first.

I'm using a custom non-touch wiz Rom which has essentially blocked me from using ussd dialer codes so I can't change the frequencies my radio picks up in the DIAG menu. I don't want to flash a stock Rom every time I go to the States so I can access the ussd codes. I'm contemplating trying to flash one of the 999 modems, because it has the frequency that'll work.

Can someone suggest a workaround before I test this potentially unsafe way?
[T-Mobile, Samsung Galaxy SIII] RoxAbout:
Possible fix [depends on your rom though...]

open settings select more settings...

under more options look for mobile networks

network mode this will give you a 3 option menu lte/gsm/wcdma or gsm only or wcdma only picking the gsm or wcdma will do the same as the *#2263# code..just not all the freq' options.

give that a try.

good luck!

====####====####====####

sorry doc didnt relize it had been hashed over....I didnt believe him because if that was the case it wouldve been turned on already!
[T-Mobile, Samsung Galaxy SIII] fornoggg:
Thank you for the advice, I tried all of the options in that menu and it still didn't pick up the 1700 frequency.
[T-Mobile, Samsung Galaxy SIII] armkreuz:
I'm currently on CM 10.2 with baseband version T999VVDLL1. Is it possible to update to VLDMF2 just by flashing the zip file from CWM ?

Or I need to flash the complete OS from Odin, and re-install CM10.2 ?
[T-Mobile, Samsung Galaxy SIII] RoxAbout:
You can always update or flash a new[er] modem from recovery....

do a nandroid backup first!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
First, it probably won't brick, and you'd just have to reflash

your modem. But I would be EXTREMELY surprised if you got any kind of signal at all.

As far as I know, it never has between any of these devices. If your partition layout is different though, you will most likely brick the device.

I'm not aware of any kind of workaround. They were built different for use on different networks. If it were this simple, I believe we wouldnt have the need for so many different models.

not a problem. Every now and then we will see a thread or post pop up with someone saying they've proven it works. Then when evidence is requested they almost always resort to flaming and name calling. Just gets annoying tbh, so I decided to respond to hopefully keep this thread from going down that road. No worries though. Sorry if I came off as a little rude!

That's pretty much what this thread is for. Flashing modems on their own. Have at it!
[T-Mobile, Samsung Galaxy SIII] armkreuz:
Great. Thanks for you help.

I change my rom very frequently, but not the radio. That why I wasn't so sure. It work great. Just not see any difference for the moment.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Some will be to close to call, while others may be worlds apart in either direction. All I can tell anyone is you just have to take your time and try them all. Just remember to take notes!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
OP Updated!!!

Updated OP to include the T999L and T999N modems. Also cleaned things up and updated some text. Reorganized to make things easier to use.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Seems like now T999(v) will be included here. What happens to the other thread ?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Not sure I understand the question. T999 and T999V modems have always been here. I just updated to add the T999L and T999N modems too. The other thread is strictly firmware. Nothing happens to it. Recently updated it as well.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Apologies I linked wrong thread. There was the SGH-T999(v) all modems which was separate from the T999L thread. So Did you happen to rename that thread so this is the new title ? Or this was/is the T999L thread ? My apology if I am confusing myself.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
No, it's not replacing anything. It's the same modem thread as before, just added the latest ones and renamed to make it more clear what's here. Reorganized to make it easier to find the correct ones too. Just seems to be a better format when including multiple devices.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Ok Thanks. That explains it.
[T-Mobile, Samsung Galaxy SIII] thetolsonator:
I've found that the stock modem for the tmo T999L gives the best overall coverage, not necessarily the fastest, but definitely most stable...

My question is:

Can I flash the stock modem from this thread into any custom ROM I pick up from here? Some of them I've really liked in terms of stability and speed as well as battery life, but the signal has been poor most times. I've been in some areas where I have had zero signal on custom ROM's and end up having to flash back to my stock build while I'm out and about, which is detrimental to battery life...

Thoughts?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes you can. Just so you choose correct mode for your specific device. FWIW, Custom roms rarely (if at all) replace the modem. If you already have a modem and you flash a custom rom, most likely the modem won't get replaced.
[T-Mobile, Samsung Galaxy SIII] thetolsonator:
I've seen some ROM's such as S3Rx and Dandroid that say they're based off of UVDMD5 which is the modem in the T999 (non LTE model) and figured maybe since that's a slightly older model that it may not be as "up to par" as the newer one in the T999L.
[T-Mobile, Samsung Galaxy SIII] Perseus:
They might be referring to the Stock Rom Version with the Modem version since that's what T-Mo does. I seriously doubt the Rom developer would intend to knowingly flash a Non-LTE modem to LTE Phone.
[T-Mobile, Samsung Galaxy SIII] thetolsonator:
Understandable, but when you say "Stock Rom Version," are you referring to the stock rom of the T999 which most are based off of? I again raise my question about putting the stock T999L modem on them to maybe boost/better my signal. Think that would make a difference?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes I am referring to the Stock Rom of the T999.

As to the second part, It comes with large risks. Flashing T999 Modem to a T999L has a potential to physically burn off the LTE Antenna upon powering on. I wouldn't do that. If you have signal issues, there are other settings that can be done in buildprop or such as Enabling AWS band.

On the flip side, I am sure there are others who did it by accident and had no ill effects.