yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
http://xdaforums.com/showthread.php?t=1494114

Yes it is compatible with our phone. But with the new jb update not 100% effective anymore. Read the last few pages for more info on that.
[T-Mobile, Samsung Galaxy SIII] titaneds73:
thanks for the quick reply DOC,i did go into d/l mode just to make sure everything was official luckily for me the counter is at 0 and everything is official ,so is it safe to say im fine?.i do have twrp and root and it still worked.thanks again for your time DOC
[T-Mobile, Samsung Galaxy SIII] jay661972:
tried this and guess what i already have 1 count (custom binary). how many counts are in there. did not pay attention to counter thing. new to sgs3 as well, came from Gnex (still have it). will you loose imei or something if you reach certain counts?
[T-Mobile, Samsung Galaxy SIII] scifan:
The thing is... if you're on LJA, having twrp loaded should trigger a counter increment on boot... (at least that's what I and others have experienced).

Interesting.
[T-Mobile, Samsung Galaxy SIII] celeox:
Even with CWM Recovery it trigers it. I did this method thinking it won't trip but it actually does since JB update. Worked great before the JB update but not now. Only thing it breaks and gives me issues with is Allshare Cast. Other than that works fine.
[T-Mobile, Samsung Galaxy SIII] titaneds73:
no nothing like that,the count should be at 0 and everything else should say official if your counter says more than 0 and you need to send it in to samsung or your carrier for warranty its there way of knowing you flashed different firmware than stock and they will not honor the warranty,

and yes i rebooted the phone and checked the flash counter just now and yeah it went back to 1 not a big deal for me just interesting though.i think chainfire is looking into it .
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
If you are running pure stock, just rooted with custom recovery, remove SysScope.apk and reboot. This should stop the counter being tripped by recovery or kernel.

However, if youve made any other mod to your system, even just deodexing, itll trip the counter again. Im trying to figure out whats causing it, but for now thats all we can do....

Its different from ICS. Sammys updated their detection again it seems. Not sure if Chainfires gonna try to update Triangle Away to counter it though.

Read what he has to say about it here.

http://www.chainfire.eu/articles/118/Triangle_Away_vs_Samsung/

I would agree with his reasoning, except that its now gone beyond warrany issues. Now if your counter is tripped things like media hub and all share cast, and even some drm stuff may not work at all. Hopefully he will change his mind on this, and hopefully we can figure out another work around as well.

Its one thing to deny a warranty claim based on rooting/modding. But imo its just downright wrong to break services when people have paid good money for them, especially when they pay for extra equipment in order to use these services! (I think its the All Share Cast Hub that no longer works due to this). I think its $100 for this thing and afaik Sammy doesn't even warn people that if you're rooted/modded, it may not work! (Though I may just not have seen it if they do)

If anyone has any extra info on what other processes are used to detect system mods, please pm with the info.

Im thinking ill probably start a separate thread for all of this since it seems to be becoming a bigger problem for people...
[T-Mobile, Samsung Galaxy SIII] jay661972:
thanks doc. i guess i will be staying with odexed stock rooted rom for now. i think it trigger the counter when i flash morfic kernel and switch to stock kernel after few hours. i should have wait and get N4 but i dont have patience for waiting lol.
[T-Mobile, Samsung Galaxy SIII] titaneds73:
interesting read thanks for the link DOC and yes i have to agree with you,not replacing a phone with warranty is one thing but deliberately breaking apps by the oem because you put a custom software is quit another.that is down right malicious and makes me think twice about samsung and where there headed in the future.we pay for phones so there for we own them well technically anyway according to them or the other fruit company so shouldn't we be able to do what we want with them,man i need to learn coding,well just my 2 cents and my mini rant.
[T-Mobile, Samsung Galaxy SIII] scifan:
The only reason this matters to me on a regular basis is I want the "bloat" that gets fubar'd when it's triggered to work.

If you Odin down to LJ4 and flash a deodexed JB (LJA) rom on the box, it works, and if you zero the flash counter, it stay's zeroed...

That points to something happening boot time with some of those "other" file systems in LJA... I don't know... Leaves some level of concern about buying Samsung devices moving forward... that or going exclusively to Nexus devices..
[T-Mobile, Samsung Galaxy SIII] Towle:
Since they want to be a**holes, I guess one "work around" would be to say screw the flash counter and flash a tar file from a different phone before doing a warranty exchange.
[T-Mobile, Samsung Galaxy SIII] titaneds73:
yes i was just thinking that.
[T-Mobile, Samsung Galaxy SIII] widto08:
I've tried this + every other method to go back to ICS and every attempt has shown the counter tripped even going all the way back to VLEM. Prior to loading up LJA Official via ODIN my counter has never been tripped from the day I got my GS3 new, always showed 0 Official Samsung.

I've removed SysScope.apk from the system and doing just a normal reboot does not trip the counter. Entering in either Recovery or Download mode and doing nothing while there will trip the counter every time.

I don't know if its possible (not knowledgeable enough to know for sure) but my thought is that the tripping mechanism may be buried somehow in the way the new partitioning is written. The reason I believe this is because my ram stays at 1.56GB and never returns to 1.62 or 1.59 as it did before.

Interesting note, when I loaded up LJA Official it wiped my internal storage, most every post I've read stated that this would not happen, thank god I backed up first.
[T-Mobile, Samsung Galaxy SIII] scifan:
Zero it before you reboot into download mode and then flash the root66 LJ4 file... then load goomanager and install twrp, then boot into twrp and install your LJA modem, and then install one of the LJA based roms... and you should be cooking with gas... no tripped counter, etc.

(that's how my phone's currently installed, and my counter's at zero... I know Media Hub works... I don't have an allshare device to test that with...)

We've probably hijacked this thread enough though...
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Sysscope does its detection post-boot, but yeah something else is running preboot that looks for certain mods. It may be kernel related....I kinda hope it is because maybe we can do something about it then. If its written into the sbl or other partition, itll be much more difficult to deal with.

Ugh, and here ive spent all this time recommending people Odin flash the update!

I do agree, I will start that thread ive been talking about here shortly. Prob needs to go in General....
[T-Mobile, Samsung Galaxy SIII] scifan:
Sorry... just saying what I know works... sadly, it goes against conventional wisdom.

*sigh*
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
maybe something in the new bootloader... wish att would come out with update so i can test myself.
[T-Mobile, Samsung Galaxy SIII] scifan:
That's my guess...
[T-Mobile, Samsung Galaxy SIII] HTC-187:
Has anybody noticed a decrease in battery life with the newest root_66 (...LJA)? My battery seems to be discharging faster than normal. Any ideas?
[T-Mobile, Samsung Galaxy SIII] jjlean:
Root, keep insurance and flash all you want. My 2 cents.
[T-Mobile, Samsung Galaxy SIII] scifan:
The real issue lies in software that's disabled when the flash counter is triggered...
[T-Mobile, Samsung Galaxy SIII] jjlean:


Yea, total BS if u ask me.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thread is up in General section, just fyi.

Sorry bout getting so off topic mrRobinson!
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Its kind of on topic, so I don't mind.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Just got my S3 this morning, for $.96, st Sam's Club, hahah. Glad I kept waiting and waiting. I came from a G2, which I rooted and am looking to root this 1. I was wondering is it better to root it while ICS sandwich is still on it, or to update to JB and then root it? I have the update waiting already. Somebody let me know, please? Thanks.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Id say root with the root66 jb firmware. Then you get root and update in one step.
[T-Mobile, Samsung Galaxy SIII] dmarco:
Hello all, quick question...I haven't rooted my phone thus far as I have been impatiently waiting for the JB version to be released and now that I've updated, can I just root phone through methods previously used for our phones or must it be rooted in a different way now???
[T-Mobile, Samsung Galaxy SIII] reapur:
The best way is to follow the first post. very easy and reliable.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
So root without installing the official JB then? I can't believe you can't move apps to sd without it. Well I'm not seeing it
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Yes. The root66 versions are identical to the official fw, except that they are pre-rooted.

No apps to sd without root and mod.
[T-Mobile, Samsung Galaxy SIII] lccl97:
Would this method work with Jelly Bean?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
??

Yes. Op. root66 JB firmware.
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
I've been searching both xda and Google for any mention of screen flicker on JB. Can't find it although I remember seeing it either in this thread or Wicked V8. I'm only getting it in the email app. Anyone else? Seeing synching error too.
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Do I need adb to compete this root method?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Still no flicker for me! Not even a little wannabe flicker!

Nope. Just samsung usb drivers, odin, firmware, and your phone!
[T-Mobile, Samsung Galaxy SIII] alex_mib:
file corrupted?

I'm trying to download root66_TMO_T999UVDLJA.7z from the op but all mirrors get me corrupted file and md5 don't match???
[T-Mobile, Samsung Galaxy SIII] EhdisChris:
So i have a questions guys. (Yes i've been reading and searching but I just want to make sure)

This is what i did:

-Odin'd the root66 tar file

-installed ROM Manager on Play Store

-Installed CMW through Rom Manager

Checked with Download mode:

(In descending order):

Binary: Official

Samsung Official

Custom

Theres no number "1" anywhere in download mode, but there is the word "Custom."

Have I voided warranty? or Tripped my Flash Count?

But when I run TriangleAway apk, it says Count is at 0 and everything is official.

Just confused.

Thanks in advance
[T-Mobile, Samsung Galaxy SIII] titaneds73:
triangle away doesnt work entirely at the moment after reboot counter goes up,i believe DOC is working on a fix.
[T-Mobile, Samsung Galaxy SIII] EhdisChris:
Thanks for your reply.

But to correct myself, i haven't really ran the triangleaway app, just launched it. and got : Count 0, and Official Everything else.

Does this mean i voided my warranty?

This is kinda confusing. Sorry all in advance.
[T-Mobile, Samsung Galaxy SIII] tdizzle404:
I can confirm this is true :silly:
[T-Mobile, Samsung Galaxy SIII] jjlean:
I can just Odin back to ICS right?
[T-Mobile, Samsung Galaxy SIII] neim81094:
Yes

Sent from my SGH-T999
[T-Mobile, Samsung Galaxy SIII] scifan:
From Samsung's perspective, you voided your warranty the moment you loaded/flashed something other than their code... I think most would still try and address things if the phone develops a physical issue... unless of course your over clocking and have burned up your CPU...
[T-Mobile, Samsung Galaxy SIII] Wicked68:
Ok, and do all the files, Odin, etc. Have to be on the phone, computer, our both? Let me know. Thanks
[T-Mobile, Samsung Galaxy SIII] DsturbD:
ok, we'll hold your hand, since this is so complicated

download Odin to your PC, extract the exe from the zip file, put it in whatever folder you want

download the rooted image file. it is a 7z file format, extract the tar file and put it in the same folder you put the Odin exe file. leave the tar image file name alone, it ends with .md5

put phone into download mode (with phone off, hold vol. down + home + power), connect your phone to your pc with a usb cable

run the Odin exe

once in Odin click the PDA field and select the root66 tar you downloaded. leave Auto Reboot and F. Reset Time checked

click start and when done let phone reboot

now where have i seen these instructions before....oh yeah in the OP
[T-Mobile, Samsung Galaxy SIII] Wicked68:
No need for the sarcasm. The original post didn't specify location to put the files. I like to get all the facts, so I don't end up with a brick. My previous rooting experience was done a different way. Thanks anyway.
[T-Mobile, Samsung Galaxy SIII] pnyboy27:
I'm coming from Xquizit xD v40 which is a JB ROM, but based on JB prior to the official JB release from T-Mobile. I plan on switching to another ROM, Wicked JB v2.1, and I read that I should ODIN back to stock to get the update to official JB and re-root my phone, then flash that ROM? So after reading quite a bit of posts from all over, I found this and was wondering if, since I am rooted, is it still recommended I ODIN the stock update root66_TMO_T999UVDLJA.7z?

I also read lower in that post, if I am coming from CWM I could just flash the OTA via the update flashable zip created. So since I am coming from UVALJ4, could I just flash that via CWM and skip the whole ODIN thing and connecting my computer? Will it still create the necessary and new partitions found on the OTA? Or should I still flash back to stock then get the update?

I'm sorry, I've been reading so many things, and I'm a little confused on how to go about this correctly. If someone could help clarify this, it would be greatly appreciated! Thanks in advance!
[T-Mobile, Samsung Galaxy SIII] rookiegenius:
thanks to this method, rooting my S3 is so easy now. almost as easy as jailbreak the ipad. :)
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
You are going to need to use the full odin root66_TMO_T999UVDLJA.7z.

since you have xquizit the cwm won't work as it patches stock files and checks their md5sums before proceeding. this will fail with your xquizit base.
[T-Mobile, Samsung Galaxy SIII] DsturbD:
you're right, i didn't need to be sarcastic, please accept my apology. i hope you got what you needed and were able to get the rooted image on your phone. i hope you wont let a bad day on my end keep you from asking for help here in the future when you need it. we are all here to learn and help and i should not have responded as i did
[T-Mobile, Samsung Galaxy SIII] redh0rse:
I've updated to JB and rooted without any problems.Thanks OP for your hard work and contributions.

However I want to find a way to go back to ICS bec tething does not work with JB.

Can I just put the root66 ICS file in Odin?
[T-Mobile, Samsung Galaxy SIII] DsturbD:
wifi tethering? that has always worked for me. this is like the third or fourth time i've seen where someone said it doesn't work. what isn't working?

to go back to ICS, im sure there is an Odin stock ICS download here, i looked but didnt see one right off, but it will be just as easy i'm sure. or flash CWM or TWRP and flash one that way
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
yes you can use the last root66 ics image posted in the OP. You might need to do a factory reset though and then restore apps with titanium backup.
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
Who let this rational, reasonable, mature adult in here??? Are you sure this is XDA, lol?:silly::silly::silly:

---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------

Not entirely sure, but I think what isn't working is tethering on T-Mobs unlimited data plan without getting that cease and desist notification, lol! AFAIK, tethering works fine if you are on a 5g or lower plan. It's no longer allowed on unlimited data unless you sign up for the service at extra charge.:D
[T-Mobile, Samsung Galaxy SIII] DsturbD:
LOL i'm trying to make this the new gentler, kinder XDA.....NOT!!!!

---------- Post added at 04:45 PM ---------- Previous post was at 04:41 PM ----------

that makes sense, im on a 5gb with tethering plan so i dont have any issues, could be it
[T-Mobile, Samsung Galaxy SIII] EhdisChris:
I just want a deoxed, unbloated!, and long life battery rom WITHOUT tripping the flash counter.

Anyways,mi just wanna thank everyone who helped me out and especially the OP.:good:
[T-Mobile, Samsung Galaxy SIII] pnyboy27:
Thanks mrRobinson. So to clarify what I need to do exactly, I can take my rooted S3 and ODIN it using the same directions found in the OP? Then since I'm rooted, for the OTA part, will I just use the non-stock recovery method? Or will ODIN remove all that from my phone? Will I still need to follow with step 3 to get CWM again on my phone? Thank again!
[T-Mobile, Samsung Galaxy SIII] xenin:
i got the latest 4.1.1 update from tmobile. but i'm thinking about reverting back to 4.0.4 cuz 4.1.1 has issues. if i do, which file will i need to root my S3 with?? TMO_T999UVDLJA.7z or with T999UVALH2 ? or will it not matter which one to use?
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Use the uvalj4
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
You won't need to worry about the Ota part. To get cwm once rooted just get rom manager from play store and install from there.
[T-Mobile, Samsung Galaxy SIII] pnyboy27:
Thanks! I can't wait to get started running the official JB and a new ROM!
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
Yeah, the hack to work around it for those on unlimited data plan is not working anymore on the latest update according to several users. Changing the apn's and even changing the user agent isn't working anymore. I think the only thing that does is using the latest hack with the Opera browser, but I'm not sure. Anyway, back on topic!
[T-Mobile, Samsung Galaxy SIII] Cobra281:
just curious; what issues are there, besides the flash counter tripping?
[T-Mobile, Samsung Galaxy SIII] xenin:
the issues with the new JB are:

- slower webpage loading

- battery drain

- dialpad is dead when using dialing rules
[T-Mobile, Samsung Galaxy SIII] Wicked68:
I'm getting an error page, when I try to download the drivers from Samsung's site. Is there somewhere else to get them? Or should I just try again later?

Edit: Never mind, waited 15 mins, tried again, and it worked. Its the EXE file, right?
[T-Mobile, Samsung Galaxy SIII] xenin:
hey mrRobinson.. i got 3 questions:

1) theres an xda page showing a list of firmwares and OTAs for T999. and theres a heading named "root66 - Pre Rooted Firmware". are these firmwares for rooted or unrooted phones?

2) is it possible to OTA a previous firmware (ICS)?

3) I got JB but i'm unrooted. i want an older firmware (ICS) and be rooted.. can i use the ICS firmware on the 1st page of this thread and get root at the same time? if so, will all my personal settings and apps be lost?
[T-Mobile, Samsung Galaxy SIII] jjlean:
Root 66 is prerooted.

Question 2: yes. Odin it.
[T-Mobile, Samsung Galaxy SIII] Cobra281:
to answer your 3rd question; yes, you can obtain root by using the appropriate, newest version of the ICS image on the first page of this thread. and no, it will not erase your personal settings and apps, since you'll be doing it from within Odin.
[T-Mobile, Samsung Galaxy SIII] xenin:
wow! thanks jjlean and cobra. so just to make sure, i got unrooted JB and want to revert back to ICS. and i can do so thru odin. and my personal settings and apps will remain. can you guys tell me what steps are needed to do this?
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
same procedure in the OP. You flash anything with ODIN the same way. Just grab the ICS file from the OP instead of the latest JB image and put in the pda field in ODIN.

Please backup before downgrading from JB to ICS. Although the flash itself will not wipe your data, I'd imagine you have a good chance of getting errors once you boot back up and you may need to do a factory wipe to get rid of them which would clear your data.
[T-Mobile, Samsung Galaxy SIII] k8108:
After spending most of last night in Odin hell, I am going to post my problems and solutions in case it might help someone else in the future.

I followed the steps in the OP exactly, but got a fail each time I tried to load the root 66. I tried loading rooted ICS which Odin said was successful but left my phone stuck at the Samsung logo the first time, then failed each time after that.

I could never get into recovery on the phone. I restarted my laptop many times, ran the process as admistrator and still epic failure.

After hours of searching and trying, it finally came to me to try a different computer. My laptop was WinVista 64 bit. I loaded all the files onto my husband's laptop running Win7 64bit. That was it! Root 66 loaded successfully at the first try.

Don't know why Odin doesn't like my computer, but am so relieved that the fix was as simple as using another laptop.
[T-Mobile, Samsung Galaxy SIII] xenin:
when you say that i might have to do a 'factory wipe' if i encounter errors, is this the same thing as a 'factory reset'? if its not the same, then how do i do a factory wipe? and will a factory wipe remove all personal settings and apps?

also, on the side of odin are options. the options 'auto reboot' and 'f. reset time' are checked. do i keep them checked? do i enable other options?
[T-Mobile, Samsung Galaxy SIII] etawful:
I'm having an odd issue with the latest ROM posted.

I've flashed it and although I've made no other changes, the device status on my S3 says "modified" which means I can't get any OTA updates.

Any idea why this would be?

Thanks!
[T-Mobile, Samsung Galaxy SIII] DsturbD:
yes, they are the same thing and will wipe your google account off the phone as well as any apps you have installed

yes, leave them checked

it says modified because it's rooted (i think that is why) so if you want OTAs then you can get the stock image and use Odin to put that back on the phone, but there are other ways to get updates, like this one, so really why worry about OTAs? just sayin
[T-Mobile, Samsung Galaxy SIII] etawful:
Nope. With the other versions of the "root66" ROM, the status says "Normal", after going back to a prior ROM with ODIN, then back to ICS from there, it reads "Normal" again.

I must have made some other change and since forgotten that I did.

Note: I received the OTA for ICS originally while having a prior version of "root66" installed.
[T-Mobile, Samsung Galaxy SIII] DsturbD:
ahh ok, my mistake, ive been flashing a bunch of other roms lately and have forgotten exactly what state the phone is left in after each one :)
[T-Mobile, Samsung Galaxy SIII] etawful:
And just to prove how exhausted I've been lately . . . everywhere I typed ICS should say JB :)
[T-Mobile, Samsung Galaxy SIII] redh0rse:
I'm on the 5GB plan as well but I only pay $20 for it as oppose to the $35 plan that includes tethering.

My SSID is not broadcasting with JB but works fine in ICS.
[T-Mobile, Samsung Galaxy SIII] ddanc1984:
Android ID

I may have run across something totally by accident. I was previously on the rooted stock ICS and updated to JB a couple of weeks ago. I did a factory reset on my GS3 yesterday and went through the setup and put my apps back. I checked the OTA update this morning in settings again out of curiosity and I did NOT get the message about "Your device has been modified..." message. I started TiB and it gave me the message about my Android ID changing so I told it to revert it. Once it rebooted I checked the OTA update again and this time I DID get the "Your device has been modified message....". May be something, may be nothing but I'm not a dev so I don't completely understand how that would be. Are they flagging the android ID at Samsung as having been modified?