yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
I'm sorry, let me clarify my statement, will you ever be able to have true LTE on th T999 no, you are right the hardware isn't there, however when I said we will be looking at patching this I meant patching the auto revert apn settings, you will be able to get a comparable speed on the T999 through apn auto revert patching, and build.prop mods, as i have experience with just that, the motorola defy you see in my signature was build.prop modded for network speed and I consistently got up and down speeds as fast and even faster than my friends who had HSPA+ devices I was running between 6-10Mb down and 2-4Mb up.

---------- Post added at 05:08 PM ---------- Previous post was at 05:04 PM ----------

Did you download the new update tmo pushed a couple of days ago, that may be why you have the lte apn, if so then an apn patch and possibly a build.prop update was part of the new update
[T-Mobile, Samsung Galaxy SIII] djtheraven:
Ok tried this with md5 modem and it won't stay...do I need the lte modem for this to work?and I don't have a mms protocol tab either
[T-Mobile, Samsung Galaxy SIII] critofur:
FWIW I installed UVAMB7 and it worked. I have not yet been able to get faster speeds.

The only problem for me so far is that after installing this I could not install Liquid Smooth v2.4 because: "...you need to be on latest bootloader of d2tmo: T999UVDLJA, T999UVDLJC, T999UVDMD5 & T999VVLDLL1"

:P
[T-Mobile, Samsung Galaxy SIII] :
Now this is interesting...just to throw some more fuel on the fire (or a wrench in the mix)...

I found this post (Bing is my new friend :silly:) that had a list of APN settings for T-Mobile LTE. Here's the site: http://www.4gtricks.com/2013/04/t-mobile-4g-apn-t-mobile-4g-apn-settings.html.

Now, I used my Nandroid backup and reverted back to before I started playing with modems. So, I'm back on the T999UVDMD5 baseband. However, I updated my APN settings to what's below.

I'm now downloading at approx 20,000kbps! Upload was at 3,134kbps.

The settings the site recommends using are:

Name: T-Mobile US

APN: epc.tmobile.com

Proxy: blank

Port: blank

Username:	blank

Password: blank

Server: wap.voicestream.com (this setting concerns me, as I haven't seen this before. So, I blanked it out and still got blazing speed.)

MMSC: http://mms.msg.eng.t-mobile.com/mms/wapenc

MMS Proxy: 216.155.165.50 (this is a new setting too)

MMS Port : blank

MCC: 310

MNC: 260

Authentication type: not set

APN Type: default

APN protocol: IPv4

Bearer: Unspecified
[T-Mobile, Samsung Galaxy SIII] :
Here's my speed test screenshot.
[T-Mobile, Samsung Galaxy SIII] Alpha_wolf:
this is a slower one ill do another one
[T-Mobile, Samsung Galaxy SIII] :
How did you get this result?
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Voice stream was t mobiles original carrier name like 9 10 years ago, its not wrong its just weird
[T-Mobile, Samsung Galaxy SIII] Alpha_wolf:
used the apn needed for it
[T-Mobile, Samsung Galaxy SIII] 81pony:
Not sure what all the hype is for. I have received 23-28 mbps alot in the town next to mine. Although in my town I only get 3-5 mbps. Is 23-25 extremely out of the norm?
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
What town are you getting those speeds in, houston, tx washington dc and a few others already have LTE and a few places have thier HSPA+ set up right, the rest of us aren't getting close to that.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
I got that speed once in akron,oh. I am goofing with settings now. My apn settings are static after editing .xml files. More in a few

---------- Post added at 07:40 PM ---------- Previous post was at 07:39 PM ----------

274 apps take a few to upgrade
[T-Mobile, Samsung Galaxy SIII] 81pony:
Amherst,Ohio
[T-Mobile, Samsung Galaxy SIII] Romcrazguy:
Strange I changed the apn settings and im not gettings these speeds whats even stranger is that lte is my area
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
Hmmm... modem flashed but getprop and about settings still say base uvl18. But am still using uvldc bootloader. Wonder if moving to newer bootloader would change anything. Hmmmm.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
You are heading into jtag territory. Lol

---------- Post added at 06:57 PM ---------- Previous post was at 06:56 PM ----------

That's it, I'm moving to Amherst!
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
Been there already motomoto. Just snooping around some and i hear stories of an updated bootloader with newer ota.

:p

---------- Post added at 08:03 PM ---------- Previous post was at 08:01 PM ----------

If you have a 999 you can't get lte speeds. We're just speculating a bit. And dancing with the jtag demons

---------- Post added at 08:07 PM ---------- Previous post was at 08:03 PM ----------

Flashing md5 modem......
[T-Mobile, Samsung Galaxy SIII] Adreaver:
If I didn't depend on my phone working I would. Even with depending on my phone I still probably would. But since MotoDefier has a second device he is about to send back, I'll wait for his results.

I did try the sim unlock. Flashed Dandroid 3.9, with the MB7 modem I was able to see the menus, didn't have the option required in the last step. I rebooted recovery and flashed the LJC modem. Tried the dialer code and went to the config menu, but couldn't see any options. Menu and Back still worked, so I did menu>input and then typed the number for each command in succession. Don't have another sim to test at the moment, but I will report back.
[T-Mobile, Samsung Galaxy SIII] jmcoffey:
Downloading now. Using my moms computer to test. :good:

---------- Post added at 10:54 PM ---------- Previous post was at 10:47 PM ----------

Thankfully I'm in great standing with T-Mobile as long time customers so I can get either a warranty or insurance replacement easily and almost always overnight if something goes wrong.

EDIT:

The first one (the one without the v) Failed. I'm downloading the second now.

Odin Log:

<ID:0/012> Added!!

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> MB7_FULL_Firmware.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

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

<ID:0/012> File analysis..

<ID:0/012> SetupConnection..

<ID:0/012> Initialzation..

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

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

<ID:0/012> aboot.mbn

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

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

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

EDIT2:

Aaaaaaaaaaaaaaaaaaaand, the second one failed also.

Odin Log:

<ID:0/012> Added!!

<OSM> Enter CS for MD5..

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

<OSM> Please wait..

<OSM> MB7_FULL_Firmware_V.tar.md5 is valid.

<OSM> Checking MD5 finished Sucessfully..

<OSM> Leave CS..

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

<ID:0/012> File analysis..

<ID:0/012> SetupConnection..

<ID:0/012> Initialzation..

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

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

<ID:0/012> sbl2.mbn

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

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

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

Hope I helped out! :)
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thank you for testing both of those out! I really do appreciate it!

Back to work I guess!

Im going to re-tar firmware for my device in a different order and test Moto's theory that it must be in a certain order or it wont work. I am still skeptical about this as Odin should be able to use the PIT to know where each part goes....... One would think this to be just plain common sense when they created Odin! I guess we shall see!

Any other ideas?
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Update: confirming that the dialer code unlock method DOES NOT WORK on the t999L. Just tested with an at&t sim and was asked for an unlock code upon booting the phone. At least it didn't work with ljc modem and md5 base ROM.

I'll try again with a 4.1.1 ROM and modem when I'm out of work.

Sent from my T999L on PACman
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Hmmmm.... thanks for reporting back on that....

If you didn't see it though, in the Q&A thread, [MENTION=4716203]AquaWater[/MENTION] claimed he did get it to work. I sent him a pm asking for more details yesterday, but haven't heard anything.

I wonder if there'd be a way to use the apps from the S4 to make this work. I know they're on 4.2.2, but they have a similar unlock method if I'm not mistaken.

Either way, I'd definitely like to hear from others trying to unlock using the T999 modem.

Thanks again.
[T-Mobile, Samsung Galaxy SIII] mehyderabadi:
I have T999L phone and I flashed my T999L, from this thread, Post #3 Method 1...like this

Reboot into CWM or TWRP Recovery

Flash PureStock Rom

Flash the unmodified, Secure UVAMB7 Kernel

Flash Stock UVAMB7 Recovery

then after that i permanently unrooted by SuperSU...

but i didnt run the Traingle away....

and now when i go in downloading mode

it says Product name : SGH T999L

....

Current Binary : Custom

System Status : Custom..

why is it showing custom..when i flashed the stock rom..it should say Official

if i run traingly away...will it help...
[T-Mobile, Samsung Galaxy SIII] Adreaver:
It will say custom unless you run triangle away before unrooting. Also, don't forget to factory reset, as mentioned in the original revert to stock instructions.

Sent from my T999L on PACman
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
That's why the last thing before unrooting should be T.A. I put the reminder there for that reason.

Just going back to stock won't change any if that info. The only thing it'll change is System Status from modified to normal. Even then you have to do it the right way.
[T-Mobile, Samsung Galaxy SIII] MAFU21:
This rom has tethering hack?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Nope. Just a basic base to create a rom from. Only what I listed is added.
[T-Mobile, Samsung Galaxy SIII] 1milenia:
are there any custom roms for the lte t999l
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Not specific to the device, you can flash kernel and system for the T999 just stay away from the modem
[T-Mobile, Samsung Galaxy SIII] lncoln:
I flashed the UVAMB7 in the op, everything works just fine. Thank you. Oh, the model was the T999L w/ 4.1.2.

this.......is...my BOOM stick!!!
[T-Mobile, Samsung Galaxy SIII] imblessed68:
Mr Doc if I put the first Odin recovery you have listed is that all I need? I'm so frustrated with mms I'm just going to go back to stock
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You have a few options actually. Personally I would recommend keeping your twrp or cwm recovery and use it to flash either the Pure Stock rom or the deodexed rom in recovery. (Id go with the deodexed version in case you ever want to try any mods or anything. ) Either should suffice though. Flash the MB7 kernel as well.

If you want to use Odin though, just flash the Stock System and kernel and youll be good to go. Flash stock recovery if you choose, but I dont think its necessary unless youre returning the phone
[T-Mobile, Samsung Galaxy SIII] imblessed68:
Will the phone still be rooted
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yup. Everything in the op is rooted! I did this so people have a "last chance" to triangle away if returning the ohone under warranty. But its also just good for everyone else too!
[T-Mobile, Samsung Galaxy SIII] imblessed68:
Thank you
[T-Mobile, Samsung Galaxy SIII] NIR_Goober:
flashing stock tmobile rom to at&t S3

Ok first i feel like a complete noob asking this question. I have an at&t S3 my wife is with tmobile and really wants the stock rom is it safe to flash the tmobile rom on the at&t S3? I'm guessing that yes it is safe but i dont want to brick my phone! Thanks in advance for the help

P.S. im not new to flashing iv flashed my old HD2 many times iv just never tried flashing cross providers roms
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
It should be fine. Just dont try anything but the rom and kernel. (Maybe the modem, but thats entirely at your own risk, though it should be safe to try it). And flash in recovery, not odin.
[T-Mobile, Samsung Galaxy SIII] NIR_Goober:
All right so I need (T999L PureSTOCK + Root) - (UVAMB7+ (kernel + modules) - (Stock UVAMB7 LTE Modem)?
[T-Mobile, Samsung Galaxy SIII] NIR_Goober:
OK So turns out i am a noob and my head is about to explode "AADD" trying to do this you said not to use odin, so what do i use to flash it?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
That should do it. Before trying the modem, double check that yours is on mmcblk0p1 first. If it's not, don't flash this one!

Using a root capable browser go to /dev/block/platform/msm_sdcc.1/by-name/

Look for modem. It may tell you the partition it's on right there, or you may need to long press and choose properties, depending on your file browser app.

If it is on mmcblk0p1, it should be safe to flash. Have a known good one for your phone handy though. If you have no connectivity, just flash the one you know is for your phone.

As I said before though, do that at your own risk as I have no way of guaranteeing it won't brick. (I highly doubt it would, but consider yourself warned of the possibility)

If you do try it, let us know how it goes. If it works it'll mean you have more options and T999L owners will most likely be able to use your modems as well!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Flash in TWRP or CWM recovery. Odin flashable are at the top of the op, recovery flashable are further down. If it's in zip format, you have the recovery ones. 7z or tar.md5 are the ones for Odin.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
FIRMWARE!

Hey guys,

Well after all of that research, work and testing we did for the T999L firmware, it would appear that it is no longer required that we continue.

The OFFICIAL firmware, build UVAMB7, was just released today.

I have already downloaded it from the super slow hotfile site and have also uploaded to my AFH account. If you want to have a copy of the official firmware, i suggest you download it from my link as it can be more than 4 times as fast! I have done nothing to this firmware. It is 100% stock, and if flashed will restore your phone to its original OOB state.

I will make the root66 version available shortly. Its pretty much already done with the Stock System in the OP.

I will update the OP with all info later on. But for now, here is the link.

T999L_UVAMB7 Official Firmware
[T-Mobile, Samsung Galaxy SIII] NIR_Goober:
Flashing tmo to an att phone

The the Tmo rom flashed with no problems but when i flashed the Tmo radio it would not recognize the SIM so FYI the tmo radio does not work on the att phone
[T-Mobile, Samsung Galaxy SIII] jmcoffey:
Hey doc, have you checked the differences between your failed Odin flashables and the official? I know it doesn't help now but if you could find what happened you could share that info with people who don't have a Odin file.
[T-Mobile, Samsung Galaxy SIII] darkynk:
Is there a cwm recovery zip out there for the t999l?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I think there is, but if you use it instead of the d2tmo recovery, some things will not flash because of it.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
No I haven't, and not sure if I will or not. Just been to busy...
[T-Mobile, Samsung Galaxy SIII] darkynk:
Wait d2tmo recovery would work for the T999L? Where's the link?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Links to that and more in my signature. Just press the button!
[T-Mobile, Samsung Galaxy SIII] darkynk:
Yeah I got it, if I flash that would it root the phone? Or is there a custom kernel or so that would be able to root and install su busy box...etc?

I've done that method to my exhibit and it rooted for Me.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Without the SuperSU app and su binary you're not rooted. You can also flash an insecure kernel but that will not root the device.

The easiest way to root is to flash the Stock System in the op. Flash in odin and that's it.

Hoping to have a root66 based on the official firmware tonight or tomorrow. But that'll do the same thing.

Go to the thread in Q&A and I have instructions on how to root there btw.
[T-Mobile, Samsung Galaxy SIII] darkynk:
It's there any other way other than using a computer for rooting?

Like if I flash the cwm recovery then flash your pure stock+ root?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Nope. You must use odin on a computer to gain root. There are several methods but all have those requirements, sorry.
[T-Mobile, Samsung Galaxy SIII] darkynk:
In not sure if all recoverys are the same but Phil said it

can ...

Quote:

Originally Posted by Phil3759

Recovery can root phone, at least cwm

When you flash CWM on a stock non rooted ROM, reboot o

main system. It will prompt you to root phone

After that, just go to market and install superuser app from

Koush, open it and it will complete the root process

but his recovery doesn't work on t999l?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
It should work fine on the T999L. But unless you're already rooted the only way to get any custom recovery on your phone (including his) is to flash it via Odin from your computer. Once on the phone, yes, TWRP, CWM, Philz, can all flash the SuperSU package and root the phone. But again, unless you are already rooted, the only way to flash a recovery is in Odin.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
This is one of the 3 methods I have a guide for in the Q&A thread btw.
[T-Mobile, Samsung Galaxy SIII] lost_:
Thanks Doc! Took just a few minutes to root with everything linked on your sig. To recap for others:

1. Install Samsung driver

2. Install ODIN

3. Odin TWRP 2.6.0.0 (or any of the recovery tar files ) into PDA slot

4. After reboot, shutdown then go to recovery: Vol Down + Home + Power

5. From PC: adb push UPDATE-SuperSU-v1.45.zip /sdcard

6. From recovery: install UPDATE-SuperSU-v1.45.zip

Done.

Doing step 5 with the phone is in recovery mode saves the step of having to turn ADB on (but you may want to do it anyway).

Next steps:

7. Backup IMEI

8. Make Nandroid backup

9. Flash custom ROMS

I waded through the thread just to make sure I didn't miss anything. Lots of side-discussion about LTE. Doc, it might be helpful for others to have those simple rooting steps on one of your first few posts.
[T-Mobile, Samsung Galaxy SIII] darkynk:
Then why have a .zip extension for the cwm recovery if u can just simply flash it?

And where do I get the supersu package to flash?
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
[MENTION=222916]doc[/MENTION], I haven't tried it because I used motochopper, but you can flash twrp with goo.manager, and twrp prompts you to install su, is it just refering to the app, not the binary?
[T-Mobile, Samsung Galaxy SIII] Adreaver:
Goo manager requires root/recovery preinstalled in order to flash anything.

Sent from my T999L on PACman
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
I should have known that, good call:thumbup:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
This is actually much more complex than it needs to be. I have listed how to root steps in both this thread and the Q&A thread. (Check the posts directly above yours). Q&A is best because this is more of a development thread for project related discussion. This was not intended for general users so much as the q&a.

Much here is now depreciated with the release of the official firmware. I'm trying to get a root66 version out, hopefully later today?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Either search xda for supersu, or click it in my sig.

The recoveries with zip extensiions are flashable, if you already have cwm or twrp installed. Sometimes they update and there's no reason I see to take old ones down, plus some may wish to go back a version if something new doesn't work right. There should be .tar versions as well for flashing in odin.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Need Testing!

Hey guys!

I have created a root66 firmware using the official release. Basically, I just replaced the official system.img with the one that has been verified working in the Stock System from the OP. So it is basically the same that we have been using, but now with everything else included in the official firmware.

As usual, if it is going to fail, I believe it will do so right away without flashing anything. But I have very high hopes that this will now work! But as always, you must understand that you are doing this at your own risk!

If you want to give it a shot, just download the file below and extract it using 7-zip. Then flash the resulting .tar.md5 file in Odin as you would any other firmware (i.e. the same way you would flash with the Stock System). There are detailed instructions in the

T999L Q&A thread

.

root66_T999L_UVAMB7.tar.md5.7z
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Hey doc, I will test it out when I get home tonight, I will swing by my brother in laws house and pick up my jigg just in case, I can always flash the stock firmware back if it does fail

EDIT: didn't go by my brother in laws and pick up my jigg, gonna try it out anyway, its gonna be pretty late though. I will post my results when I get it done.:thumbup:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thanks! I'm pretty sure we are good though. I'd flash it in a heartbeat if I could!
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Somebody send doc a T999L, lol
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
ROOT66 Update

@ DocHoliday, odin called out an md5 hash invalid error, root66 needs to be re-hashed, drop the md5 and lets see if it will flash that way.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
May be a bad download. Check the md5 of yhe file against the one on the download page. If different, redownload. If not, let me know.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Sounds good

Update: [MENTION=222916]doc[/MENTION] I redownloaded on my desktop, haven't checked it yet, but here's the funny thing I checked the checksum with es file explorer on the original download to my phone, its correct when the file stays zipped, unzipped it shows the md5 to be aboot.mbn(048547396749604) the numbers in parentheses are not correct but it starts with the aboot.mbn when unzipped I know odin v3+ will decompress the .7z so I will try to flash it without first unzipping and see what happens, probably will be tomorrow.
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Here's what I get with es file explorer in the differing checksums, however this time around you can see a real checksum instead of what I described, not sure why it is showing a real checksum this time, but they still differ between the two.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
The md5 on the download page is for the download, in .7z format, only. As soon as you extract it it will have a different md5. It will be this way with any archived file. Zip a document. The md5 on the zip will be different than on the document.

If the md5 on the .7z file matches the download page, then the download itself is good.

When you extract and flash in odin, if it doesn't pass the md5 check, then something went wrong with either the upload or the creation of the tarball.

And Odin will not flash anything but a tar file.

So all I need to know btw, is did the md5 match for the download? If so, does it still fail the md5 check in odin?

Ill take a look in a few min on my end anyway though, its probably something went wrong on my end.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Oh, and if it EVER fails the md5 check in Odin, do not force the flash by removing the md5 extension! !! Danger of bricking!
[T-Mobile, Samsung Galaxy SIII] MotoDefier:
Yeah, both md5s match both on the phone and on the desktop
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ok, thanks. Looking it over now.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You know, I think I'm going to go a different route on this one. I'm going to try a completely different approach, but I'm also going to ask mrRobinson if he will go ahead and make up the root66 fw like he always does. Ill let you know more later, for now, I need a short break!