yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] guest_2011:
I odin flashed this file (TMO T999LUVUBNC1) a week ago in brand new T999L and all went well. Today i did the same to another new T999L. No errors, rebooted. Installed Rom Manager - no root. Root checker also doesn't have root access.

update: had to flash again. rooted!
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Could someone please post a link to the ATT kernel required for the latest root66? For some reason I having a hard time dinging it.

Thanks
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
The included kernel should work fine. The att one isnt required. Only if you flash a rom an wifi stops working. But then that shouldn't be an issue if youve updated with root66. I think there may be a link in Saranhai's StockMod OP though.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I already flashed once and most WiFi. I used a backup to get back to stockmod. I'll search the thread.

Trying to make a new nan back but for some reason it keeps failing after awhile even though there is enough space. Damn annoying!

Thanks
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Did you update the firmware with Odin, or Mobile Odin? If you used MO, that may explain the wifi.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
You got it, I used Mobile. I try with the PC next.

Thanks
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yup, makes sense to me. In case you didnt already know, MO doesnt flash the full firmware. Only system, kernel, modem and recovery. It cannot flash the rest.

We found early on that the later 4.3 builds seemed to put the wifi drivers/modules elsewhere (this is what I suspected anyway. Someones probably found out for sure by now but I havent seen it confirmed or debunked personally). Anyway, I believe they used to be built into the kernel, but then they moved to another partition that MO cannot flash meaning they would be missing and wifi wont work. The AT&T kernel is from a very early 4.3 leak before whatever changes were made, which is why wifi still works with it. We got lucky on that one!

So your choices are to remain using your older base firmware and bootloader, but you will need that kernel, or, fully update to 4.3 which includes the warranty bit and prevents you from flashing any previous firmware.

If you are out of warranty or dont care about it, and dont think youll need to flash older firmware in the future, id say go to full 4.3. Its your choice though.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Assuming they have a 1 year warranty it has lapsed. I also assume the new bolt has some advantages. I will flash it.

Thanks again
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I am running 4.3 stockmod now. Does the new root66 firmware warrant the change?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Well there's supposedly a bug fix that's important. Other than that, not very much to my knowledge. your call.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
What's the bug? If it hasn't been affecting me I won't bother with the update.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Its one of behind the scene. Not readily apparent. Google for more.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I personally felt it was worth it. May have been a security related issue in MJC. If youve gone to MJC before I see no reason to not go all the way to NC2. I youre still on pre 4 3 firmware its just the issues I laid out before with warranty and downgrading. Not enough imo to not update. (I have never had to downgrade due to bugs, so I felt the chances of this are minimal.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I'll try it.
[T-Mobile, Samsung Galaxy SIII] KunoMochi:
Hey guys, I've been out of the loop for a while so I'm just trying to get caught up with everything here, so I hope you can bear with me if I end up repeating some already answered questions that I may have missed.

To start off, ever since I received my replacement phone, I've stuck with the stock ROM and had (stupidly) updated to 4.3. I've been stuck on it for a good while now but I've decided to finally get it rooted again.

From what I could gleam of the threads here, it seems that I may be stuck with the 4.3 bootloader.

I take it from the first post, I won't be able to downgrade to an older bootloader without the risk of bricking. Does this also mean that it'll prevent me from flashing a pre-4.3 ROM as well, due to that warranty bit?

And would this also prevent me from flashing non-TouchWiz-based ROMs?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You can still flash roms. I do suggest going back about 4-6 pages though. We actually just covered a lot of this stuff again.
[T-Mobile, Samsung Galaxy SIII] KunoMochi:
Thanks Doc! I did just that. :)

I noted that the warranty bit was not tripped when updating from 4.1.2 -> 4.3 and 4.3 -> 4.4.2... I'm just speculating here but maybe the warranty bit wouldn't be affected when upgrading to a newer version?

For example, maybe upgrading from 4.2 -> 4.3 would not trip the warranty bit either? [Not certain this would work in the same manner.]
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
The warranty bit is not supposed to trip unless flashing a non stock kernel or recovery. Just updating firmware shouldnt trip it. No idea why it did on several people here. Im not pursuing it tbh though. Itd just take too much time and effort and would require a bunch of people willing to test on a device that has not yet been tripped.

Thanks for the report though, I do still follow it here and am interested in others results.
[T-Mobile, Samsung Galaxy SIII] omaral:
When I go to the link to the newest UENC2, I cant find any link to dwonload. Is there something wrong with the download page? Is there an alternative link?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Its been working fine for me all day.
[T-Mobile, Samsung Galaxy SIII] klr.b:
I forgot to post an update to this, but this didn't work out as planned. Wifi didn't work.

Synthetic.Nightmare's modem worked, but the enewman17's kernel didn't. As some have already found out, the 4.3 kernel doesn't work without the 4.3 bootloader. To keep the 4.1.2 bootloader, I used TWRP to flash the ktoonsez

KT747-TW-JB-4.3-ATT-01-18-2014 kernel

. Everything worked fine after that.
[T-Mobile, Samsung Galaxy SIII] verysick:
Do I have to remove that ".md5" at the end?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
No. Thats what Odin uses to verify the file is good. You can delete it, but its not recommended.
[T-Mobile, Samsung Galaxy SIII] verysick:
Do you know what can be the reason to "FAIL"? It's my 1st time using Samsung & odin.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Did you put the phone in Download AKA HOTBOOT mode ?
[T-Mobile, Samsung Galaxy SIII] verysick:
Yes
[T-Mobile, Samsung Galaxy SIII] Perseus:
Assuming the Cable and Phone USB port is ok, please post a log that Odin had when you tried.

Are you able to access the phone via windows Explorer otherwise ?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you have kies installed on your computer, uninstall it. Its been known to interfere with Odin.

---------- Post added at 03:32 PM ---------- Previous post was at 03:31 PM ----------

Also try different usb ports on the computer. If it still fails, uninstall drivers through device manager and reinstall.
[T-Mobile, Samsung Galaxy SIII] omaral:
1) After I root66 with UENC2, can I install a kitkat custom rom without tripping the flash counter?

2) Is it also possible to install a past ICS custom rom?
[T-Mobile, Samsung Galaxy SIII] Perseus:
1. No. Not possible. Custom Roms require Custom Recovery. The Flash counter will update the moment you flash that way.

2. You can install a custom ICS Rom. So long you make sure that it is in zip format and does not include a bootloader. Typically they do not include one.
[T-Mobile, Samsung Galaxy SIII] verysick:
I tried with a different cable & it worked.
[T-Mobile, Samsung Galaxy SIII] omaral:
Hi perseus.. So just to make sure, I can still install a Kitkat custom rom as long as it doesnt include a bootloader. Is this also correct?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes that's correct.
[T-Mobile, Samsung Galaxy SIII] omaral:
Thanks man.. I hope the official Kitkat for galaxy S3 T999 comes out, though I highly doubt it will given the I GB of ram limitation on the phone.
[T-Mobile, Samsung Galaxy SIII] Perseus:
What do you mean 1 GB ? I have been using KK since January without even trace of issues.
[T-Mobile, Samsung Galaxy SIII] omaral:
What I mean is, Samsung implied that it wont release Kitkat for the S3 because you need 2 GB of ram. The S3 only has 1 GB. Thats why they wont release the official Kitkat for it.

But it seems that the custom Kitkat rom does work in the S3. It looks like the rom needed to be tweaked in order for it to operate well in the phone
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thats only the I9300 model. Check the kk thread in General for info on our rumored release date.
[T-Mobile, Samsung Galaxy SIII] Perseus:
There are KK Roms for the international Model for some time now. The developers have tackled the memory issue in the Kernel management.

So in short, I don't know about Samsung's excuses, we do have KK for international version.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
As I understand it, the kk roms based on cm and aosp are just fine to run on the 1gb of memory. The problem is when Samsung incorporates all of the extra features it no longer can reliably run. So their choices are to either release a build which does not perform very well, or start removing many of the features we have long been accustomed to having. (Face detection, multi window, smart stay, to name a few).
[T-Mobile, Samsung Galaxy SIII] omaral:
I read the the CM version of kitkat for the S3 has problems like the camera.

I'd like a custom rom with no problems. But if the custom rom has issues then I'd prefer the official rom any day.
[T-Mobile, Samsung Galaxy SIII] Perseus:
I have been using CM base Rom since early last year. Have been using Kitkat since beginning of the year. Zero problems noticed.
[T-Mobile, Samsung Galaxy SIII] omaral:
I dont like nor trust CM.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thats why I always try to emphasize that its a personal preference issue more than anything. I personally stock with touchwiz. Perseus71 and a great many others prefer cm and others...

Its also a big reason why "whats the best rom" questions are not allowed. Many will defend their preferred base to the point of infractions or worse! You sometimes might think it sounds familiar too....Apple anyone?! Lol!
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes it is one of the better and safe ones. It is less prone to error for a first timer to root. I wouldn't call it best way as there are other ways, and we will have a debate on our hands that will derail this thread.
[T-Mobile, Samsung Galaxy SIII] Perseus:
It depends on how and what apps you intend to use. Battery life is dependent on several different factors.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yup. Nc2 has been great on battery for many people.
[T-Mobile, Samsung Galaxy SIII] Perseus:
My answer was specific to Custom Roms. Weather they turn out to be better Battery savers or not depends on usage.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I updated recently but have not noticed any additional battery drain.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Different people have complained about battery on every official release and pretty much every rom out there. 95% of the time its not the build or rom. Youll find users of every kk rom tgat say battery is great. But you find some that say it isnt. This just isnt a question that can be effectively answered imo.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I did. It is fine for me.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Im not sure whats wrong with your device then. As I stated though, you will find people who have problems with battery on every single rom out there. I have never had any issues on this device, regardless of what build I was on. When my battery was still good and strong I could easily get over 24 hours between charges with heavy use and 5-7 hours screen time. Even now, with a much weaker battery I can get nearly all day with moderate use.

This has gone waaay off topic for this thread though. If you need further help, id suggest opening a new thread in q&a. Dont take it the wrong way, but it does sound like youve already made up your mind about this so im not sure theres much anyone will be able to to help though.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Kitkat is coming to every s3 except the i9300. Ours should be released in another week or two.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Happy to hear that!
[T-Mobile, Samsung Galaxy SIII] Perseus:
I believe Root66 does not have Knox as it is. That Link has a Knox remover Script as part of its steps. That's the one which will remove it for you.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Root66 has knox already removed. So you really only have one step, flash in odin, done!
[T-Mobile, Samsung Galaxy SIII] revwillie:
The t999's ram has been misreported in a couple of articles I've seen but mine has 2 geebees.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thats your available memory. You have 2gb. Only the i9300 has 1gb.
[T-Mobile, Samsung Galaxy SIII] scorpio_bpl86:
thanks for the info

hope the update come out soon
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If the information I got was exactly correct, we would get it by tomorrow. However, keep in mind this was a month ago that I found out about their speculated release date. Things change and bugs can be found which can delay it. In the case of T-Mobile, one of the big things that makes it take longer is WiFi calling. Until recently, T-mobile was the only carrier that offered this and it had to be specially coded for them. I hear that Sprint is now adding it as well (although much more restrictive), so I hope that 2 carriers getting it will make updates happen a little quicker.

Anyway, at this point, I am not expecting a release tomorrow. I figure if it were ready we probably would have got it in the last few days. Regardless, I am certain it is close! The Note2 just got its update, and with other S3's getting it as well, plus the info I got before, all point to an update very soon!

Sorry for going OT in this thread.........Again! :p
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Awesome. I held off flashing UVUENC2 from UVUEMJC when you mentioned this previously. Now I can just go directly to Kit Kat. It should come right about the same time as my final payment on the thing!
[T-Mobile, Samsung Galaxy SIII] awesome71717:
So, I have flashed the T999LUVUBNC1 rom and the twrp recovery through odin with sucess but twrp is unable to mount any of the partitions. I have tried reflashing both but I get the same result (along with cwm). I am rooted and posting from the phone, but recovery is not recognizing the OS.

Any thoughts?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
What version of recovery? If using the latest 2.7.1.0, try going back to 2.7.0.0. If using anything else try both of those.
[T-Mobile, Samsung Galaxy SIII] awesome71717:
Nope. 2.7.0.0 / 2.7.1.0 / 2.6.3.1 all cannot mount the partitions. I am going to try a factory reset with kies and then go from there

CWM Touch recovery works (6.0.4.5) used dd in terminal emulator.

errors:
[T-Mobile, Samsung Galaxy SIII] Nyckrs:
I just got my dad a s3 for fathers day and it already came with 4.3 nc2 firmware. Do i just use root66 latest to root? Will i run into problems such as tripping counter, knox, or brick? Thanks
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Answered in firmware thread.
[T-Mobile, Samsung Galaxy SIII] TechShui:
I used the root66 Odin tar for T999L it passed the phone booted, everything is working. No KNOX, but root is broken.

SuperSu says there is no Such Binary installed.

Has anyone else had this problem with the T999L.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
First ive heard of that, but you can either try flashing again, or just use Towelroot.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Have you tried updating SUPERSU app from play store ? Inside the app, did it prompt you to update the binary ?
[T-Mobile, Samsung Galaxy SIII] bscaine:
Hi, for some reason I can't acces androidfilehost.com from my country. I'm trying to root a T999L on 4.3. Could you please uploaded to anoether server? THanx for your useful post. BR
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I assume you want build NC1? Can you download from dev-host? Http://d-h.st
[T-Mobile, Samsung Galaxy SIII] yahanna:
Hello. I'm thinking of rooting my S3 with the latest root66. But lets say I root66 based on root66's android version 4.3. Then I install a custom kitkat rom. Are there any kitkat roms that can offer wifi calling? If not, then why is it so hatd for a dev to install wifi calling on a kitkat rom?
[T-Mobile, Samsung Galaxy SIII] fdecker:
DocHoliday77. Can you point me to the t-mobile sgh-t999 4.3 UENC2 completely stock version from t-mobile? No root. Just the stock rom in case I have to send my phone back. Thanks.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
No. And I gave a detailed answer in the thread you created asking about this.

Its in my firmware thread. Its stickied so you should have no problem finding it. (But it is also linked in my sig!)

You can also get it at http://sammobile.com/firmwares, but downloading from me will usually be a good bit faster.
[T-Mobile, Samsung Galaxy SIII] yahanna:
Ok cool. Just trying to cover all my bases. Appreciate it.
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
Hi boys! I am reading thread after a long departure and am preparing for my triumphant return. Stupid s3 with 43....
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Welcome Back!
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
Thanks The Doctor!

Now to de-knoxify this s3 and move on. ...
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I just now got a push for Samsung Update Service but got a "your phone has been modified" message. Can this be the kitkat update?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Doubtful. Probably the update for the Samsung apps. The kk update will come from Tmobile and probably won't use the Samsung push service.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
That makes sense :(
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yup. I read somewhere yesterday that Samsung was about to start updating its apps, and would rename them to Galaxy Apps on all Galaxy devices.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I should debloat anyway
[T-Mobile, Samsung Galaxy SIII] johnathanamber:
So, the KNOX Counter Will Still Trip

So, from the sounds of it, we still have not figured a way to not trip the KNOX counter:

"4.3 Image Notes: With 4.3 images, KNOX is removed in order for root to stick. This will flag the Knox counter. Once you flash one of these 4.3 images you now have the latest factory stock bootloader, radio, etc. Flashing a prior bootloader can hard/soft brick your device. Please read and understand what you are doing."

Thanks guys,

Johnathan
[T-Mobile, Samsung Galaxy SIII] sonwon:
KNOX / warranty flag to Samsung, my next phone will not be a Samsung.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you check the last few pages you'll see it does not always trip the counter. Mine stayed at 0. As did several other people. Doesn't really matter imo though. There are tons of reports on many different devices stating the warranty was honored regardless.

---------- Post added at 02:16 PM ---------- Previous post was at 02:14 PM ----------

Leaving Samsung won't get you away from Knox anymore. Google is going to begin using it in ALL android builds. Probably starting with Android"L".
[T-Mobile, Samsung Galaxy SIII] Perseus:
Good Lord Doc! You sure are full of Cheer aren't you ? :D
[T-Mobile, Samsung Galaxy SIII] sonwon:
Sigh, can hope for Ubuntu then. Google is locking the phone up to much to only work with their infrastructure.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Since doc's so full of Cheer, I might as well add to the tune. Please see [DEV|APPv14] CIQ / HTC & Google Checkin / HTC loggers / Tell HTC Info & Removal

If you thought, that's HTC and not for me, install the app from its post #109 and then see what it has to say.
[T-Mobile, Samsung Galaxy SIII] sonwon:
It is a pity this hasn't been updated since, 16th October 2012 at 01:33 PM.
[T-Mobile, Samsung Galaxy SIII] yahanna:
Yeah but at least its still got a KK port. So consider that.
[T-Mobile, Samsung Galaxy SIII] johnathanamber:
So, are there any specific steps that some have done that others have not? Or are the steps all the same and 'sometimes' it doesn't trip. If the steps are the same, which post is the best at displaying these steps? Just curious if there's anything different, etc.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Probably because it still works just fine. Works on 4.3 and 4.4.2.

Nope. No one knows why. And most likely no one ever will.

This isn't the only method of rooting though. Search around each section of our forums and you will find several.
[T-Mobile, Samsung Galaxy SIII] mad_a_22:
[MENTION=4081205]DocHoliday77[/MENTION] [MENTION=3355398]mrRobinson[/MENTION]

This root serve me well for many months now. But recently their are times when i reboot my Tmobile S3, superSU cannot be opened. It says "no SU binary installed" and need to re-root. It can be opened if i reboot my phone several times.

Are their any solution to this? I cant use xblast after this incident since i need to reboot before xblast functions well. But after reboot error occurs like my phone is not rooted.

How to re-root? Am i just going to do your procedure again in this thread?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You can try Towelroot, or root66 if ypu prefer. Have you updated supersu?

If none of that helps you may need to factory reset.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Have you tried the option for a different installation location?
[T-Mobile, Samsung Galaxy SIII] Perseus:
From within the SuperSU app, you are required to update the binaries. Once that is done, please reboot.
[T-Mobile, Samsung Galaxy SIII] mad_a_22:
yes i have updated it from google play.

how about re-root? how to do this?

how to update this binaries?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Its automatic when you open the app.
[T-Mobile, Samsung Galaxy SIII] Ditamae:
Hey there. Appreciate the ongoing support here. While attempting to restore a nandroid this evening (to help diagnose another issue) I encountered "E: error opening 'data/lost+found' - this was followed by an inability to mount /data. I also can't delete any of the five 'lost+found'" files with EF File Explorer. My backups fail, and /data cannot be properly wiped. Long story short, I'm interested in restoring to stock - hoping this will remedy my issues. I'm currently running Slim 4.2 with TWRP 2.7.1.0. As I've only used a few Slim ROMs in the past couple years, I just wanted to confirm that I can use ODIN to flash back to the UVDLJA pre-rooted stock firmware from my current set-up. It's my understanding my custom recovery will persist after ODIN flashing back to stock and I can flash back to Slim or whatever from there. I guess I'm also concerned the /data error might prevent me from flashing with ODIN. And I couldn't seem to find any info about this particular error in our forum (if I missed it, I apologize!) Honestly, this is the first problem I've experienced with the S3 in almost 2 years. I haven't used ODIN since I first rooted.

I was considering upgrading the S3 recently, but I really still like this device and I'd love to continue with it for a while longer! And for this reason, I love your ongoing support [MENTION=4081205]DocHoliday77[/MENTION] and [MENTION=3639717]Perseus71[/MENTION].