yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] klr.b:
I can't test this now, but will probably update my sister's T999 S3 next time I see her. Last time, I flashed mrRobinson's Root66 4.3 EMJC via Mobile Odin and it kept her on the 4.1.2 DMD5 bootloader (Knox free). Then I had to install TWRP and flash the EMJC modem and the AT&T insecure kernal.

If anybody is still on the 4.1.2 DMD5 bootloader and flashes this Root66 ENC2, could you post results? My plan is to flash this Root66 ENC2 via Mobile Odin, then flash Synthetic.Nightmare's ENC2 modem, and finally flash enewman17's ENC2 kernal.

Does that sound right, or should I go some other route?
[T-Mobile, Samsung Galaxy SIII] if6was9:
I installed 'root66_TMO_T999UVUENC2' this morning. So far, so good. Thanks [MENTION=3355398]mrRobinson[/MENTION].
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thanks for testing man! If I can ill give it a go tonight and second it. As always, many thanks to [MENTION=3355398]mrRobinson[/MENTION]! Great work!
[T-Mobile, Samsung Galaxy SIII] karipay:
Currently installing the new root66 file. Will update in a few.

Thanks Mr. Robinson!
[T-Mobile, Samsung Galaxy SIII] karipay:
Perfect!
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
Any chance you'll be putting up a UVUBNC1 Rom for the T999L?
[T-Mobile, Samsung Galaxy SIII] fdecker:
Problems with the mirror host?

I've tried several of the mirrors on the link and it always slows down and then stops completely at some point. Are any of you having trouble downloading?

Nevermind. I just kept trying and resetting my own time warner connection. Finally got it after a few hours
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Don't forget, AFH has many mirrors of their own. I downloaded from one of the TX mirrors last night and it was surprisingly fast.
[T-Mobile, Samsung Galaxy SIII] MCoolU:
I downloaded root66_TMO_T999UVUENC2.7z and when I try to open it i get an error message saying the archive is either in unknown format or damaged.
[T-Mobile, Samsung Galaxy SIII] zhinkk:
Thanks mrRobinson for the files. I have a question:

I was really dumb and while I was reading the instructions I read "Leave Auto Reboot and F. Reset Time checked." and I thought it said UNCHECK. So I unchecked those when flashing. The auto reboot wasn't an issue, I just rebooted manually. What about the F. Reset Time? I researched and its the "flash time counter"?

My device is fine, root works fine, its all good. Just curious as to what happened/didn't happen to my device since I unchecked F. Reset Time. Sould I reflash?
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Check the OP, prob tmr.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Just use Triangle Away to reset your flash counter.
[T-Mobile, Samsung Galaxy SIII] fdecker:
file managers won't see root

I also just tried the UENC2 version to root my SGH-T999 which was previously on the OTA stock 4.3. Done in 10 minutes, seems to work great. I installed SuperSU from Chainfire and Root Checker. They seem to work fine. However, I tried ES File Explorer and File Manager from Rythm Software. Neither can access root. When I try to enable the feature on either one of them, I get their message that they can't enable the feature, make sure the device is rooted.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Go to SuperSU and update the Binaries from inside the app.
[T-Mobile, Samsung Galaxy SIII] zhinkk:
I don't think I have a flash counter (yet). Is that what the F. Restart Time does? Reset the flash counter?

Product name: SGH-T999

Custom Binary Download; No

Current Binary: Samsung Official

System Status: Custom

Qualcom Secureboot: enabled

Warranty Bit: 1 (tripped knox)

Bootloader RP SWREV: 1
[T-Mobile, Samsung Galaxy SIII] fdecker:
How to update binaries?

Sorry for being dense, but how do I do this? Are you talking about the SuperSU binaries or the file explorer ones? I have had ES File Explorer and File Explore installed from before rooting. After I just rooted, I installed SuperSU from the play store. It is the latest version, 1.94. Maybe I have to uninstall and re-install the file explorers?
[T-Mobile, Samsung Galaxy SIII] MCoolU:
NVM got it to work. I disabled anti-virus and now I can open it. I think it was interfering with it. Thanks
[T-Mobile, Samsung Galaxy SIII] netfortius:
+1 for latest (NC2) rooted image, courtesy of [MENTION=3355398]mrRobinson[/MENTION]. Installed flawlessly "on top" of previously, similarly installed UVUEMJC, and running so far w/out problems.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Worked great! Thank again for all your hard work and continued support for our device!

Download 7zip and use that to extract the file. Did you check the md5sum to make sure it's a good download?

I don't think it really matters much. They are checked by default usually which I think is why we all say to leave it, just to play it safe. I don't think you have anything to worry bout though.
[T-Mobile, Samsung Galaxy SIII] fdecker:
Installing custom recovery?

Now that the 4.3 root works, how can I install TWRP? Do I have to manually rename the files that put the stock recovery back on reboot, or does Goomanager and installing TWRP work? I was reluctant to try Goomanager since there were a lot of negative comments in the play store in the last year. So I wanted to know if someone tried it with this rom.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Those files should only be there if you updated via ota. It's how they update the recovery. If you've flashed root66 via odin, you shouldn't need to worry bout them.

I used goo manager last night on MJC and it worked just fine.

Or get the .tar file and flash via Odin.
[T-Mobile, Samsung Galaxy SIII] Perseus:
On that count you are right though. Goo hasn't been very effective on flashing TWRP on 4.3 and 4.4. It downloads fine but after reboot you still have stock recovery.

But Doc's point regarding Root66 is perfectly applicable.
[T-Mobile, Samsung Galaxy SIII] fdecker:
JRummy Rom Installer

Have you guys tried JRummy's ROM Installer? Looks like nice work. Starting to get confusing with Rom Manager, Goo Manager and now ROM Installer. But the installer seems to have some kind of support in it for Goo manager, or at least finding things on the goo.im site. Opinions?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I just installed twrp using GooManager on my S3 that I had flashed NC2 root66 onto earlier. Worked perfectly.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Oh Ok. Thanks Doc for letting me know.
[T-Mobile, Samsung Galaxy SIII] fdecker:
Works like a charm

And thanks Doc and Persius, for the record, everything is working great. Couldn't be much simpler:

1. Use Odin to install the root66 stock rooted ROM for SGH-T999 v4.3 (UENC2)

2. Install SuperSU from the play store

3. Install Goo Manager from the play store and flash TWRP recovery v2.7

So just have to test a few more things, make some Nandroid backups, and figure out why ES File Manager and File Manager both don't seem to see the phone is rooted. Probably will just uninstall and re-install them both and see what happens.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Don't forget to backup of EFS partition if not done already.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
this is up.
[T-Mobile, Samsung Galaxy SIII] csaket:
I was running CM11 for a while on my T999 and wanted to go to stock to use WiFi calling.

So followed the instructions in the OP and got Odin to flash without any errors.

The phone boots up but stays on the SAMSUNG logo forever.

Then I rebooted into recovery and formatted/factory reset as the OP says.

Still stuck at the SAMSUNG logo.

Appreciate any help.

---------- Post added at 10:13 PM ---------- Previous post was at 10:12 PM ----------

And I spoke too soon.

The phone finally came up, phew!
[T-Mobile, Samsung Galaxy SIII] Johnnyy9262:
Currently installing this on sgh-t999l hope it doesnt void the warranty :rolleyes:
[T-Mobile, Samsung Galaxy SIII] sonwon:
This worked perfectly on my TMO SG3. Warranity bit was tripped when I went to install TWRP. I mean before I did anything it was tripped. Phone works perfectly with root, didn't even have to wipe anything. All my data was still there on internal SD; don't know about SD card since I replaced with a larger one.

Thank you very much for this thread!

Disregard this was for this forum not here. Sorry for the noise.
[T-Mobile, Samsung Galaxy SIII] Johnnyy9262:
Well this did trip the knox counter :( should have re-read the 4.3 notes
[T-Mobile, Samsung Galaxy SIII] omaral:
I'm still not rooted yet. But I installed the official UENC2. That being the case, how do I root and install TWRP without tripping Knox?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You cant.

---------- Post added at 12:24 AM ---------- Previous post was at 12:19 AM ----------

Let me rephrase, if you flash a custom recovery or kernel it'll trip the Warranty Bit.

I just updated from 4.1.2 to 4.3 using Root66 and this alone did NOT trip the Warranty Bit.
[T-Mobile, Samsung Galaxy SIII] sonwon:
Hey DOC, all I did was updated 4.3 with Root66 and when I went to install TWRP the bit was set before I started the install, maybe because I was already on unrooted 4.3 and not 4.1.2? I don't really care about the warranity flag just trying to help others out when they read the forum. Wait, that was the other forum, sorry for the noise.
[T-Mobile, Samsung Galaxy SIII] omaral:
At this point I dont care if I trip Knox. I got 2 questions:

1) Once Knox is tripped, what can be done to untrip it while retaining root?

2) Is it possible to install ClockWorkMod even if it trips Knox?
[T-Mobile, Samsung Galaxy SIII] sonwon:
There is no way to untripp the warranty flag. The flash counter is fair game.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Did you update via mobile odin? Or It may have been something else installed that caused it to trip. I know ive seen several people say root66 tripped the warranty bit, and expected it to do so for me too. But I rebooted download mode 3 times to make sure and it stayed at zero till I flashed a rom using Mobile Odin. Ive no idea what you and others may have done differently, all I know is it didnt happen to me.
[T-Mobile, Samsung Galaxy SIII] sonwon:
odin on windows. I don't what we did either.
[T-Mobile, Samsung Galaxy SIII] mrmako777:
i flashed root66 -mjc and it did not trip the warranty bit, but the most recent one root66 -nc2 did. not sure what was different from one version to the next but oh well, ive had this phone almost 2 years so its not like i can get warranty service on it anyways. to those that can, heads up that the most recent root66 version WILL trip the warranty bit
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
So much for sidestepping 7zip. It'll go alright.
[T-Mobile, Samsung Galaxy SIII] neotoky:
Seems like the ATT and Sprint were successful with testing but don't see T-mobile. Chainfire also mentions that he needs to release these quick since he will be away for a month.
[T-Mobile, Samsung Galaxy SIII] stevessvt:
Thanks to MrRobinson, Im still at 0, but I think someone in the thread I linked to was trying to get the app to try on his TMo phone.
[T-Mobile, Samsung Galaxy SIII] neotoky:
No doubt thanks to MrRobinson but people can always make a mistake to tripping the counter. Traingleaway will be very good to have especially those who already tripped it a long while ago.
[T-Mobile, Samsung Galaxy SIII] stevessvt:
No doubt, a little extra insurance never hurt anyone.....
[T-Mobile, Samsung Galaxy SIII] moonfire711:
I could sure use a working triangle away.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
Me too, I feel bad because I just tripped it before reading. and I'm a long xda user so I know that I HAVE to read (5 times) before doing anything..
[T-Mobile, Samsung Galaxy SIII] neotoky:
Once it becomes successful, all that's left is the dreaded IMEI issue.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
What about that?? Darn I didn't read that either. Any links?
[T-Mobile, Samsung Galaxy SIII] stevessvt:
1.70 is available for all USA gs3!

http://xdaforums.com/showthread.php?t=1494114
[T-Mobile, Samsung Galaxy SIII] fireboypr:
Will it reset counter to GS3?
[T-Mobile, Samsung Galaxy SIII] neotoky:
http://xdaforums.com/showthread.php?t=1777915

Issue where your IMEI gets deleted when flashing either custom recovery or roms. Non one knows for sure what is causing it. Also there is no way of backing up or restoring your IMEI.
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
Whew, I never knew I could hold my breath for so long! That took a great while for the progress bar to finish and get a "Pass". So I created a file called "System Backup", selected everything from "/system" and am pasting everything in there. Then I'll transfer that to my laptop and wait for the devs to identify just where the IMEI information is. Maybe a little too cautious but I already busted one phone, lol.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
One question. I used odin to root and tripped flash counter.. but triangle away was just released and now I have counter 0 and binary official. Now if I install this stock with root thing, will I get original on ROM? or I will still the custom?
[T-Mobile, Samsung Galaxy SIII] moonfire711:
If you want it to say original for warranty, just flash the unrooted stock rom.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
Got it! Will flashing the unrooted stock rom increase the counter? I guess not obviously but want to make sure
[T-Mobile, Samsung Galaxy SIII] moonfire711:
Only custom roms trip the counter. The stock one will not.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
Thanks!!!!
[T-Mobile, Samsung Galaxy SIII] moonfire711:
No worries. If we couldn't flash the stock firmware after using triangle away, there would be no point...am I right?
[T-Mobile, Samsung Galaxy SIII] jjlean:
doesn't really matter what method we use to root now right? .... with triangle away working now...
[T-Mobile, Samsung Galaxy SIII] sonwon:
Maybe is has something to do with hardware revisions?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
I used the latest and it did not trip mine. Very odd...

I guess that might be possible, but it seems kind of unlikely to me.
[T-Mobile, Samsung Galaxy SIII] mrmako777:
one thing i did differently this time was to factory reset before flashing the new image. if it didnt trip yours, and you didnt reset before you flashed, theres the culprit...interesting
[T-Mobile, Samsung Galaxy SIII] sonwon:
I didn't factory reset before or after and the phone works great.
[T-Mobile, Samsung Galaxy SIII] mrmako777:
Yeah, mine works great too. No issues...but, pointing out whether or not factory reset prior is what tripped the warranty bit...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Might be that I was already rooted on 4.1.2 and by not wiping it retained some data that prevented it from tripping. So by wiping data first, it had to rebuild everything and then saw something that triggered it. If that makes sense....

Probably left over sysscope data if I had to guess.

Afterwards I did factory reset, but it still did not trip the bit. Stayed zero till mobile odin.

Funny thing here is that on the Note3 people are using MobileOdin to flash from 4.3 to 4.4.2 and it does not trip it!
[T-Mobile, Samsung Galaxy SIII] Johnnyy9262:
What you did different was flash from 4.1.2 to 4.3 knox is removed from root66 to maintain root, therefor people on 4.3 that updated OTA had knox registered to their system and as it says in the 4.3 notes removal from knox = knox counter 0x1

---------- Post added at 01:03 AM ---------- Previous post was at 01:00 AM ----------

Now that sure is wierd
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
The thing that sucks the most here is we cant go back and try again to figure it out!

Everyone gets one shot at testing any theory we might come up with!
[T-Mobile, Samsung Galaxy SIII] sonwon:
Agreed, my next phone will likely not be a Samsung.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Agreed and +1 to ^^^^^
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Yep. Why I've been on nexus 5 since it came out.
[T-Mobile, Samsung Galaxy SIII] sherp71:
I have a Galaxy S3 on the Canadian Wind network and used Mark Skippen's Samsung Galaxy S3 Toolkit V7.0.0 to root my phone. I am running Android Version 4.1.1 and with Build JRO03L T999VVlDLL1. I am looking to take advantage of the pre-rooted stock firmware offered by mrRobinson. My hesitation is due to the caution posted at the start of this thread - " Flashing a prior bootloader can hard/soft brick your device." Can some kind soul tell me whether I can take advantage of these new ROMs without bricking my phone? Many thanks in advance. <Peter>
[T-Mobile, Samsung Galaxy SIII] Perseus:
You certainly can flash the subsequent versions for Android version 4.2 or 4.3. You will do fine. But remember if you flash 4.3 version, you CAN NOT ever try to flash your existing 4.1.1 or 4.2 version. If you do, you will get a hard brick.

This is due to the fact that the 4.3 Bootloader is locked and it prevents you from flashing older unlocked bootloaders.

Best if you use Mobile Odin for flashing Root66. It flashes the firmware but not the Bootloader.
[T-Mobile, Samsung Galaxy SIII] sonwon:
I'll add the stock 4.3 build is a nice build. I still need to debloat, haven't had time to research for the best tool. And I miss the weather on the lock screen from 4.1.2. Also using xposed.
[T-Mobile, Samsung Galaxy SIII] omaral:
I was thinking of installing ICS from the first page of this thread since it drains the battery far less than UENC2. Do you guys think its a good idea?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
You can flash any of the older roms, just when it comes to the full firmware only flash your current or newer build.

---------- Post added at 03:13 PM ---------- Previous post was at 03:10 PM ----------

And I wouldnt use the toolkit. Its not supported and has caused people to hardbrick. Just a word of caution is all.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Best tool for debloat is in OP. At least my favorite. But I'm biased.
[T-Mobile, Samsung Galaxy SIII] sonwon:
Never could figure out how it worked so today I spent time tinkering and learned the zip is unsigned, had to turn checking off and then it worked great, so now I am debloated. Well I think it worked, it currently says, Android is upgrading, optimizing app xxx of 198. I'll edit when done.

Debloat worked, no problems, thank you!
[T-Mobile, Samsung Galaxy SIII] omaral:
Hey mrRobinsom, I'm currently not rooted. But lets say I root with root66 UENC2. And later on I decide to try ICS. Will I have to install your root66 for ICS or do I just install a custom ICS rom?

Also, do you agree that ICS drains far less battery than UENC2?
[T-Mobile, Samsung Galaxy SIII] addictedhacks:
used T999UVUENC2 and i don't know if none of the cm roms support that bootloader or what... I keep getting ro.bootloader error.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
A little OT but try a newer rom.
[T-Mobile, Samsung Galaxy SIII] addictedhacks:
I actually tried cm11 as well no go. I appreciate the contributions but a warning about the latest firmware would have helped.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If a rom doesnt support the latest firmware, it on the devs if that rom to make it so. Theres just no way anyone can keep up with everything thats been updated and what hasnt.

Its usually a simple edit of the updater script anyway. Search these forums for delete assert lines and you should find instructions.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Nope its a one way journey. If you tried to flash ICS Root66 on top of NC2 Root66, you will hard Brick your phone.

Battery consumption is a relative scenario. Difficult to say one does or does not.
[T-Mobile, Samsung Galaxy SIII] omaral:
Hi perseus71. Well, since I got the official NC2 installed, is it possible to install ICS root66 instead of NC2 root66? Will this brick my phone sine ICS is an older firmware?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I tried flashing the latest root66 on Tmo yesterday using Odin mobile. I've been running the rooted stock ROM JSS15J.T999UVEMJC. I'm sure that I enabled all the partitions available in mobile Odin. I lost wifi and then read that firmware requires the correct kernel. I ended up with a soft brick that I fixed with Odin on my PC flash my Nandroid backup :)

What is the proper way for me to flash the new firmware? Can I use mobile Odin? Do I need to DL the correct kernel and flash it separately?

Thanks............mm
[T-Mobile, Samsung Galaxy SIII] Perseus:
Download and flash the correct kernel via custom Recovery. This should be done after Odin Flashing the firmware. It does not matter weather you use Mobile or PC Odin.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you flash with pc odin it will flash all included partitions, so everything should work. Of it doesnt you may need to factory reset.

Mobile odin only flashes system, kernel, modem, and cache. If you select the .tar.md5 file it will flash all of these unless you deselect one or more manually. If wifi is not working here you may need to try the old MJ2 kernel from ATT. Havent heard of this happening in a while though. (Did you originally update to MJC using Mobile Odin?)
[T-Mobile, Samsung Galaxy SIII] sonwon:
Not sure if this is relevant anyway here goes, I am on a completely stock 4.3 TMO ROM root66 no ATT stuff and WiFi works and debloated.
[T-Mobile, Samsung Galaxy SIII] omaral:
Hi perseus and mrRobinson.. I got 2 questions...

Perseus, you replied 'yes' to my 2 questions so I'm not sure which question you said 'yes' to. Just to make sure, are you saying I cant install ICS root66 instead of EUNC2 root66 given that I got official UENC2 because it will brick my phone?

I got the official UENC2 installed and am unrooted as I said before. Just to make sure, is it possible to root66 to the previous version, UEMJC?
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Sounds easy enough. Once again, thanks for the advice and all your effort to help us all here.Perseus.
[T-Mobile, Samsung Galaxy SIII] sherp71:
Perseus71... appreciate your confidence in me but time and lack of self-confidence have held me back from actually doing the flash. Grateful if you can advise on:

a. what should I backup before proceeding with the flash? (i.e., should I have a recovery image somewhere should anything go wrong?) and

b. once the firmware is flashed, will all my apps need to be re-installed? What else is in danger of being wiped?

Thanks in advance. <Peter>
[T-Mobile, Samsung Galaxy SIII] Perseus:
You do not want to flash the ICS version as you already have NC2 version. Flash NC2 version alone via Odin.

a, Typically Root66 flash won't disrupt user Apps or their data. So you should be ok. Take titanium backup if needed. As to Nandroid, well you will loose Custom Recovery after Root66. So you will have to flash that again before the nandroid is usable. So be ready to use Nandroid Manager app if you take Nandroid before hand. Remember, System Apps data will be wiped out. So any Samsung Apps you might be using might loose data. Best if you take their backup. titanium might not help as it requires Root. But give it a try.

b. Don't think so. Once you log in with your Gmail ID, typically Goole restores user apps if you had enabled backup and restore before.
[T-Mobile, Samsung Galaxy SIII] sherp71:
Flashed root66_GLW_T999VVLUEMK5.7z for my Canadian Wind model using Mobile Odin as recommended. Everything seems to have gone well EXCEPT that I cannot get WiFi turned on. Any ideas or help in troubleshooting/solving this problem would be greatly appreciated.
[T-Mobile, Samsung Galaxy SIII] Perseus:
For the US Variants, there was an ATT Insecure Kernel that fixed this issue. can't be sure what will work for you. Please find a way to set SELINUX to Permissive.

Do you have Knox on there ? If so run the De-Knox script posted in this forum.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Root66 shouldnt have knox. And if you flash the firmware via Odin, I bet wifi will turn on. That will update your bootloader to 4.3 with the warranty bit though.