yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] Perseus:
In that case Flash your Device Root66 and you are all set.
[T-Mobile, Samsung Galaxy SIII] BenzE420:
I gave up, which is why the long delay. Today I went back, restarted the process from the beginning, and eventually got it to work. THANKS to everyone who posted. I had to turn off auto reboot, and manually reinstall Supersu, as it didn't show up after rebooting.

All that being said, I think I am rooted now. I downloaded Titanium backup, and am backing everything up before going any further. It looks like I have a LOT more reading to do before I actually try to flash a ROM or anything.
[T-Mobile, Samsung Galaxy SIII] HardDrive01:
Need Help!

When I try to attach the tar. file in Odin, all i can see is the zipped file and not the extracted file. I used the zipped file and followed your instructions. It then says RESET not PASS, then it reboots my phone. After reboot Odin status then switches to PASS but nothing has changed on my phone. I entered recovery mode and I cant install neither supersu nor knox removal. Are there steps I missed or perhaps steps you didnt list??
[T-Mobile, Samsung Galaxy SIII] mmxbass:
Will this work for the March 8th 2014 updated T999 T-Mobile stock firmware (T999UVUENC2) or is this only for the previous one that was out when this thread started?

Has this been checked?
[T-Mobile, Samsung Galaxy SIII] sonwon:
If I follow this guide will the flash counter be tripped? What about the warranty flag?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yup, anytime you flash a custom recovery and kernel, itll trip. Root66 is probably the best option now that its updated. Cant remember for sure if it trips the warranty bit. Been too long since I looked at that!
[T-Mobile, Samsung Galaxy SIII] 4Gevo:
Wanted to know if this would work for the sprint version?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Youd probably be better off checking the sprint forum. You have root66 firmware there too...amongst other options.
[T-Mobile, Samsung Galaxy SIII] iperez85:
Hey everyone, first post. I recently updated my SG3 to the UVUENC2 firmware and tried to reroot with method provided by Perseus21 in the General Board, but it didn't work, it stayed on the flashing SAMSUNG screen and wouldn't finish booting, and when I tried to go into recovery, it went back to stock recovery instead of the custom recovery. I decided to just try this method for the hell of it and IT WORKS! I am running 4.3 UVUENC2 Firmware FULLY ROOTED & DEKNOXED. Hopefully it works for others too as it did for me. I just made sure to download the latest version of TWRP (v2.7.0.0) and also SuperSU (v1.94), the KNOX REMOVAL zip worked just fine. Good luck and happy rooting.
[T-Mobile, Samsung Galaxy SIII] cLogic:
good to hear :good:

you said 4.3 ... but isnt NC2 the new sprint kitkat 4.4 update?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sprints 4.4.2 is ND8.

NC2 is our latest 4.3
[T-Mobile, Samsung Galaxy SIII] Track607:
Okay, am I the only one who doesn't understand how to install these zips?

I don't have any option to flash (install) anything in the recovery menu, and I don't have an SD card.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You have to have a custom recovery such as cwm or twrp to flash. Sounds like you are still on stock recovery.
[T-Mobile, Samsung Galaxy SIII] Track607:
Yeah, I figured. But I can't install either of them. I wrote so in my thread:

http://xdaforums.com/showthread.php?p=52607199
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thats in the Note2 forum. Are you having issues with that or an S3?
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
I just rooted and I cant seem to get CM10.2 to install. I'm running on android 4.3 and I'm new to the rooting scene here and flashing cm10.2 just gives me an error
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Any particular reason you dont want to use cm11? From most accounts that ive heard, it works a lot better.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
1. Its in the title and op.

2. Imo, no. But Its whatever youre more comfortable using. I suggest reading the information in both OP's and their threads and choose based on that.
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
Here's the thing. I'm on 4.3 and its a 4.4 ROM (I'm assuming incompatible) but I get errors when trying to flash the 10.2 cm to my sgh-t999 rooted in this thread. What's the most stable cm11 version?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Just because you have a 4.3 Bootloader and Modem, it shouldn't stop you from flashing CM 11. The only criteria is to have latest version of the recovery. Any of the D2LTE versions of CM 11 will be fine.
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
I cant flash any rom though, i get an error if i try to
[T-Mobile, Samsung Galaxy SIII] Perseus:
What error is that ? Can you post a photo of it ?
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
I attacted it. Same error on cwm aswell
[T-Mobile, Samsung Galaxy SIII] Perseus:
Please find the most recent version of CM 11. They had recently added the newer Bootloaders to their list.
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
Same error bro, even on the latest cm11 nightly build
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Try either twrp2.7.0.0 or Mobile Odin. If using twrp or cwm, are you certain its the d2tmo or d2lte one?
[T-Mobile, Samsung Galaxy SIII] Perseus:
First figure out your Bootloader version. If you had the most recent 4.3 update, then that would be UVUENC2. Now follow these steps.

1. Open the CM 11 Rom zip file on PC.

2. Navigate to /META-INF/com/google/android/

3. Open the updater-script file from inside the zip. Don't extract it. Ideally use wordpad not notepad. Notepad doesn't handle newline characters.

4. Within the file, you are looking for a bunch of Assert statements. These statements check for certain bootloaders. Your bootloader is not in there. That's the cause of the errors.

5. Now you have 2 choices. Either you can add one more assert for your Bootloader. Otherwise, get rid of them all.

6. Close the file. Wordpad will ask you to save the file. Click Yes. If everything goes right, winzip should prompt you to re-add the updated file to the Zip. Hit Yes.

7. Reopen the Updater-script just to make sure your changes did make it in.

8. Close the Zip and flash it.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Here's the link. All versions are listed there. Make sure to grab .TAR files not .IMG file.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Everything you need is in my sig.

---------- Post added at 01:07 PM ---------- Previous post was at 01:06 PM ----------

2.5 versions will most likely not work for any newer roms. Get 2.7.0.0
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
Im on sgh-t999 no lte. Im gonna try what perseus said after updating twrp and seeing if it works
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Just fyi, all the latest recoveries have been consolidated into d2lte. So instead of having d2tmo, d2tmolte, d2att, d2can, etc, etc, they are all now covered by d2lte.
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
just installed TWRP 2.7.0.0 and it gives the same error
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Then you probably need to odin flash the NC2 firmware and try again...
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
I get error status 6 on CWM

without doing the edit error status 7 on CWM

I don't get what my problem is, i just installed the latest 4.3 baseband (kies) and on the non kies 4.3 baseband it didn't work either
[T-Mobile, Samsung Galaxy SIII] Perseus:
When you edited the file, you probably deleted a semi colon that you shouldn't have.

Can you post all the Unedited Asserts here as text ?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
The baseband is just the modem. Im willing to bet you are running 4.1.1 firmware other than that modem. Again, try odin flashing the latest firmware, then your recovery, then try to flash the rom again. If your firmware is not updated you will run into these kind of issues on nearly every rom you try.
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
Could you post a link to download? I swear i just updated my phone through ODIN with the latest 4.3 firmware from kies. (T999UVUENC2_T999TMBENC2_T999UVUENC2_HOME.tar) the file

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

assert(getprop("ro.bootloader") == "T999UVDLJA" ||

getprop("ro.bootloader") == "T999UVDLJC" ||

getprop("ro.bootloader") == "T999UVDMD5" ||

getprop("ro.bootloader") == "T999UVUEMJC" ||

getprop("ro.bootloader") == "T999VVLDLL1" ||

getprop("ro.bootloader") == "T999LUVAMB7" ||

getprop("ro.bootloader") == "T999VVLDMF2" ||

getprop("ro.bootloader") == "T999VVLUEMK5");

im asuming you mean the one here: T999VVLUEMK5");
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Ahhhh.....well theres your problem! NC2 is NOT included in the asserts! Delete the top two "d2tmo" lines completely, then change any one of the others to "T999UVUENC2". Then save and try again.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Doc you'd think CM guys should have gotten this right by now. This is 16 or 18th case I have seen so far.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yeah, it seems they just dont have much interest in updating the script and reuploading....theyre not the only ones of course, but with such a large user base someone on the cm team shouldve made sure this was addressed long ago. We're about to get yet another official release making it even more outdated. I know things have slowed a lot around here but theres still enough people with all S3 variants that it should still matter.
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
Alright ill try that when i get home! Also just to make sure... delete this entire line?:

assert(getprop("ro.product.device") == "d2tmo" || getprop("ro.build.product") == "d2tmo");
[T-Mobile, Samsung Galaxy SIII] Perseus:
That depends upon whether in in Settings > About > Model, your phone shows up as SGH-T999 or something else.

If its shows up as T999, keep the line otherwise remove it. Its just there to make sure that only users of T999 flash this rom.
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
Yea i know about my phone model. Its just the NC2 firmware i was talking about, ill just replace one of the t999 (nc2 firmware number) with mine
[T-Mobile, Samsung Galaxy SIII] cLogic:
most US-based roms do Not include a getprop for My device, the T999V ... d2can ... which is almost identical to the d2tmo

altho ... that might be cuz samsung stupidly made BOTH the T999V and the I747M have same product/device d2can when actually the I747M is almost identical to the d2att I747

however, ironically, those same roms have THIS lower in the updater script which works perfectly and would solve the assert getprop issue

ifelse(is_substring("T999", getprop("ro.bootloader")), run_program("/sbin/sh", "-c", "busybox cp -R /system/blobs/gsm/* /system/"));

doh ... lol

psst ... hey [MENTION=4081205]DocHoliday77[/MENTION] and [MENTION=3639717]Perseus71[/MENTION] ... :cool:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Those are why ive always suggested that T999L/N/V should all just use the d2tmo recoveries.

And te reason I suggest deleting the two d2tmo getprop lines is because if you are using the newer d2lte recovery it may not want to flash. Doesnt hurt to remove them if you know youre on the right device.
[T-Mobile, Samsung Galaxy SIII] ALLEN2:
well i just installed the latest nightly build of CM11 from d2lte
[T-Mobile, Samsung Galaxy SIII] Jake1Jamie:
TWRP won't install

I tried this method about 3 times on my T999, and it boots into stock recovery
[T-Mobile, Samsung Galaxy SIII] Jake1Jamie:
I got it rooted with another guide with almost these steps, except this guide didn't inform me to uncheck autp reboot ans to manually shut off and boot into recovery before booting system -.- How I miss my Note 2 :(
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
This is most likely because you updated via ota. It includes a script that will rewrite stock recovery everytime you boot up (if a different one is there of course). It is like this on all sammy devices afaik. Been this was for the S3 since our very first update.
[T-Mobile, Samsung Galaxy SIII] panteralives4:
Hi Doc, I was wondering if there is a thread on root66 for sprint galaxy note 2 SPH- L900? I have a friend that wants to root

his phone. I tried CF auto root and it failed because of knox security is blocking the install. I`m looking into mskips toolkit

as a option over CF auto root do you know if there is a thread on sprint note 2 for root66?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Probably not, bit id steer clear of the toolkit. Its been known to brick devices and is given no support at all.

Ask in the note2 forums for options. They will be much more familiar with what does or does not work on that device.
[T-Mobile, Samsung Galaxy SIII] panteralives4:
Okay thanks I`ll check it out.
[T-Mobile, Samsung Galaxy SIII] panteralives4:
Hi Doc quick question is there a root 66 for samsung galaxy note 3 N900T T mobile version?

I have looked around on xda and can not find a guide for it can you help?

thanks.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
There wasn't when I last checked. If its changed it'll be in their development area.
[T-Mobile, Samsung Galaxy SIII] Masaker514:
I followed the OP and my Supersu is crashing it closes automatically any help please.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Which version of SuperSU are you using? Have you tried a different version? Did you remove Knox?

Why not just flash the root66 firmware anyway? I believe this was originally written because the root66 fw wasn't yet available for the latest builds.
[T-Mobile, Samsung Galaxy SIII] Masaker514:
I'm using everything from the op's post. I'll read through the pages and get the root66 thanks.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Oh ok, I bet thats why. That is a much older version of SuperSU. You should at least be using 1.94. You can get it from the link in my sig if you want to give it a try.
[T-Mobile, Samsung Galaxy SIII] BioDesigner48:
Stupid question, this will work on the T-Mobile LTE version right?

Oh and do I have to use Odin 3.07? Cuz I have 3.09 already downloaded, but downloading 3.07 won't be a problem.

Thanks in advance
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes it will work for T999L device. So long you pick the firmware for your device. Odin 3.09 will do fine.
[T-Mobile, Samsung Galaxy SIII] BioDesigner48:
Thanks! And correct me if I'm wrong, but once I finish this process, there is no need to unlock the boot loader in order to flash Roms?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Nope, bootloader is unlocked.
[T-Mobile, Samsung Galaxy SIII] jin512:
Hi, I just need to root my Galaxy S3 T999 T-Mobile in order to have Chinese as a system language. To my understanding, I can follow the instructions to root, but you can't root unless you have an unlocked bootloader? How do you unlock the bootloader? I haven't seen any instructions anywhere on how to do that. I am on 4.3. Thanks!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
The T999 bootloader never has been locked.

You can use this method, just understand it is a bit outdated. There are newer recoveries, knox removal may or may not be different now, etc.

The easiest way to root now is to use Towelroot. Not to take away from any other method, but it is by far the easiest and safest method we have now.

I created a thread about it in General section.
[T-Mobile, Samsung Galaxy SIII] yeeahnick:
is there a deodexed + deknoxed T999VVLUFNF1 firmware somewhere?
[T-Mobile, Samsung Galaxy SIII] ilavu:
Since doing this, my phone will be knox free. So is it posible to downgrade the firmware to 4.1.1?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Nope. Sorry. There is no way to downgrade firmware.
[T-Mobile, Samsung Galaxy SIII] serio22:
You still have Knox bootloader so you cannot.. You can flash a 4.1.1 ROM if you wish, however
[T-Mobile, Samsung Galaxy SIII] myxisme:
Man.. I had to go out of my way to thank the OP for compiling this information. I've been in a battle for blood against Knox and have spent the past few hours researching and trying to defeat it on my s3 t9999, all roads leading to the same dead end.

Many, many thanks to the author of knox killer and again the OP for sharing.

Cheers.
[T-Mobile, Samsung Galaxy SIII] berrywr:
I'm new to the Galaxy S3 but not new to flashing (HTC HD2, HTC Titan PI39100). It is a device my stepson is no longer using and I wanted to customize the moment I got my hands on it, but never in my wildest dreams did I think Android 4.3 would present the problems I have had and reading & reading as many threads as I could as those problems presented themselves concluding with this thing called Knox which I believe now is the source of every issue I've had with the device following what appeared to be successful replacement of the Android Recovery 3e with either Clockworkmod or TWRP only for the moment I reboot the device normally what awaits me is "Android is Upgrading" which I'm guessing restores Knox and I'm back to square one. I've disabled Auto-Reboot on Odin v3.09 but the bottom line is at some point it has to be rebooted normally; how do I stop this upgrade the moment I do so? Or at this point before doing so would it be wise to attempt to flash the device with a customized ROM via TWRP which was my last attempt; thank you!
[T-Mobile, Samsung Galaxy SIII] serio22:
It will only give you that message if dalvik cache was wiped.. What exactly was it that you did?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yup. Its rebuilding dalvik cache after updating (or as serio22 said, wiping it). Perfectly normal.
[T-Mobile, Samsung Galaxy SIII] berrywr:
When I started this "journey" I had no idea that rooting Android v4.3 would be like pulling teeth; I've had no success rooting 4.3 regardless of whether I use TWRP or CWM; every variation to root has failed. I successfully downgraded to a rooted v4.1.2 via flashing successfully TWRP 2.7 but struck out using CWM 6.0.4.5. Following successfully flashing the downgrade via recovery and a micro SD card I have found no version of the firmware with T-Mobile Wi-Fi calling...a must have. I had no success with Kies (not Kies 3) recognizing the device so I opted to use Odin v3.09 where I had some problems here too but eventually it did install the stock 4.3, so I'm back to where I'm started. Some observations...is it me or does the device save on some other partition the previous installation, whether it's 4.1.2 or 4.3 or whatever firmware is on the device. It didn't feel to me like everything is wiped upon each of the firmware installations. I've read on some threads and believe me, I've read a zillion of them in the past few days that to bypass what I know now is Knox, a script within the Rom has to be edited; I've never done this before. I find myself wondering about the bootloader and if it was upgraded with whatever Knox is which upon return to 4.3 I had an icon that upon tapping is 103 megabytes to install but yet for the moment any attempt to install SuperSU or ROM Manager has failed. I had no problems installing these programs on 4.1.2. I would really appreciate knowing if there is a ROM customized or stock, signed which exists the T-Mobile Wi-Fi Calling program is embedded; thanks everybody!
[T-Mobile, Samsung Galaxy SIII] serio22:
Use towelroot to root. And all the TouchWiz Roms that are based on T-Mobile firmware (nearly all) support WiFi calling. No aosp or CM
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
All roms that are based on the stock T-Mobile system have Wi-Fi calling. But only those roms have it. Nothing else does and nothing else will.

As for rooting, did you try root66 or Towelroot?
[T-Mobile, Samsung Galaxy SIII] sonwon:
Actually there was another ROM (non T-Mobile) that did have WiFi Calling, however I cannot mention it here and it was never released to the public that I know of. I guess since it was never released it doesn't matter which is a pity of course. So for released ROMs you are 100% correct.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If someone figured out how to port the feature into non T-Mobile roms I'm surprised they never posted it. If I'm not mistaken there have been some pretty decent sized bounties promised to whoever could figure it out. Im not trying to argue that you are wrong, but maybe it wasn't actually T-Mobile's WiFi Calling. There are other services that allow calling over WiFi, maybe it was a modded/baked in version of one of those.

Im just finding it a little hard to believe it was true T-Mobile wifi calling though. Not just because of the bounties, but out of all of XDA and the many very talented people who have tried, only one person was able to pull it off? And it just happened to be one of the few people that don't want to share with or give back to the community (or even get paid large amounts of money)?

Like I said, I'm not trying to start an argument, just stating that I have my doubts that it was the same wifi calling feature everyone wants.
[T-Mobile, Samsung Galaxy SIII] sonwon:
Doc, I'll send you a private message to show you where the discussion happened, keep in mind that the moderators deleted many of the messages. I would post the message here but maybe it violates some rule. :rolleyes: I no like censorship.
[T-Mobile, Samsung Galaxy SIII] cLogic:
latest official T999 firmware are here http://samsung-updates.com/device/?id=SGH-T999

they are 900MB zips

you unzip and inside is the official tar.md5

flash the tar.md5 via odin

it wipes out everything ... you'll see it all flash in top box (modem, boot, recovery, etc)

from that point you will be on stock, official t999 ...

since it is only 4.3 ... this thread method, or others, will work to de-knox and root

cheers
[T-Mobile, Samsung Galaxy SIII] berrywr:
Serio22 and DocHolliday77...thank you! I haven't tried Towelroot as of this typing but will get back with y'all when I make the attempt. I found and saved the link to root66's Roms, but I wasn't clear on whether these are stock all the way or minus "Knox". I flashed his most current Rom via Odin but nothing is root on this Rom. My main priority was making sure I had the TM Wifi calling and I do, but my God, the bloatware is just ridiculous. The device runs fine...and I'm not here to draw comparisons or take sides between Android and WP, but if this is the path Google is to go down, WP isn't going to be a bad option if this is only going make our lives harder. I remember having to flash my HTC Titan with the Goldcard method and that wasn't exactly what I call a fun few days. This was right up there on learning the nuances. I was happy to get back to 4.3 and knowing at the very least I won't brick my phone reverting to an earlier incarnation of Android. I will give the Towelroot a go tomorrow; thank you!

Update: I downloaded Towelroot....brought the rain, updated SuperSU, pulled Rom Manager up and next step is Titanium Backup...whew!!! Learned a lot in the past few days! Thanks again!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Don't forget, I host all of the firmware in a sticky thread in Development. Downloads should be much faster that way.

There is also sammobile.com.
[T-Mobile, Samsung Galaxy SIII] berrywr:
It took four days and a level of reading on these threads I haven't done since I deployed the goldcard method on a pair of HTC Titans PI39100s but until I can find a custom ROM with the T-Mobile Wi-Fi Calling App I installed root66's 4.3 "root" stock rom and for the moment philz CWM 6.0.4.5 is tucked away for recovery. I'm in the process of using a list of apps to safely remove courtesy of Titanium Backup Pro. I read as of this typing Congress passed a new bill in regards to making it legal to unlock our devices but I haven't read the details yet. I am by no means a developer; just an ordinary guy with grown kids and in college to become a math teacher. I knew nothing about this version of Android and this device until this past week. Another family member has the HTC One M7 Developer Edition which I bought; a very good decision. What a difference between it and this Galaxy S3 T999 variant. Thanks to all of you!