yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] calexchelse:
It will trip the counter if you flash a custom recovery
[T-Mobile, Samsung Galaxy SIII] Perseus:
Flashing Custom Recovery is most likely trip the counter at each boot.
[T-Mobile, Samsung Galaxy SIII] karipay:
Anybody knows if treve's wifi tether will still work with the new root66?
[T-Mobile, Samsung Galaxy SIII] flip3601:
I just got this phone about a week ago from a friend cuz the screen is shattered lol. But I updated to 4.3 already and haven't rooted it yet. Atm the warranty bit counter is at 0. I'll do the root66 process n check the warranty bit when I get home in a couple hrs. Just so I understand this correctly if I want cwm and not trip the counter I should get ROM manager and install cwm from there instead of flashing it? I was delaying all of this cuz I'm getting the glass repaired but oh well.

Sent from my CM10.1 SGH-T599
[T-Mobile, Samsung Galaxy SIII] ppgregory:
Just wondering... Why all the fuss about the warranty counter? Aren't the majority of T999s outside the 1 year warranty anyway?
[T-Mobile, Samsung Galaxy SIII] truckerdewd:
My wife still has 2 months left on the one year warranty. But yes, I'd say the majority are close to or passed the warranty

Sent from my wickedly awesome Galaxy Note 2 using my fingers. Duh!!!
[T-Mobile, Samsung Galaxy SIII] ortind200:
is it true that if u want CWM and not trip the counter that u should get ROM manager and install CWM from it?
[T-Mobile, Samsung Galaxy SIII] ThC23:
Haha, you beat me to it. I wanna gonna mention the same thing. My phone is out of warranty, but because I have insurance Tmobile will just swap it out and I don't think it will matter if the counter is tripped.

It's not like we have the Note 3.

Lol

Powered by the SGSIII
[T-Mobile, Samsung Galaxy SIII] flip3601:
So to let u guys know what my bit result was I updated my s3 to 4.3 then odin'd root66 and the warranty bit went from 0 to 1.

Sent from my CM10.1 SGH-T599
[T-Mobile, Samsung Galaxy SIII] bwb8771:
I am NOT happy with the Kies-loaded stock 4.3 from T-Mobile. Calling it buggy is being polite.

By "do NOT flash back to an older version", mrRobinson, do mean ANY older version of *any* ROM, or just older versions of root66 ROMs?

I ask because I seriously want to put 4.1.2 back on my SGH-T999 - the bugs I'm suffering actually get in the way of using my GS3 as a **phone**
[T-Mobile, Samsung Galaxy SIII] yeeahnick:
can we expect a T999VVLUEMK5 release soon?
[T-Mobile, Samsung Galaxy SIII] Perseus:
I believe he meant Root66 of Previous Stock Roms. In particular the Tarballs of stock that include the older Bootloader. The point is, never flash previous bootloader (or anything that has one) from now on. If you did, you will get instant hard brick. You can however flash a custom Rom and that will be ok. But that's likely to trip your Efuse Counter so bye bye warranty.
[T-Mobile, Samsung Galaxy SIII] DJAlik:
Kinda of a n00b question. So I originally rooted with root66 4.1.2 image and then installed CM 10.2. Is there any reason I should install root66 4.3 followed by CM 10.2? What advantages does it give me other than a new bootloader?
[T-Mobile, Samsung Galaxy SIII] joselamar:
Busybox Installer

Hey guys, is it necessary to install Busybox Installer and Voodoo OTA Rootkeeper with this new 4.3?
[T-Mobile, Samsung Galaxy SIII] Perseus:
The new Bootloader is not an advantage. If I were you, I'd stick with CM 10.2 if that's what I like. If anything you can flash the latest Modem.

No OTA Rootkeeper is not. Busybox, may be but depends on what you are going to do next.
[T-Mobile, Samsung Galaxy SIII] joselamar:
So, is it 100% needed? Would rooted phones be affected in anyway (i.e. performance, apps not working, etc...) if Busybox is not installed?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Well any app that needs it, is likely to install it on its own. Others like Titanium will give you a laundry list of prerequisites for them to work. If you really wish, get STEricsson Busybox installer from Google Play or here on XDA. Install it then let it do smart install of Busybox. I don't think that's mandatory though.

The only caveat is the case of MODs or tweaks. Those may need it so you want to install in case you are going to try any.
[T-Mobile, Samsung Galaxy SIII] DJAlik:
Please forgive my ignorance, but how do I only install the new modem?
[T-Mobile, Samsung Galaxy SIII] Perseus:
You visit this thread, then read first 5 posts patiently and then choose the modem from 1st post.
[T-Mobile, Samsung Galaxy SIII] ortind200:
MrRobinson! i read that samsung will be releasing an update to 4.3 soon.. have u read abt this?
[T-Mobile, Samsung Galaxy SIII] tower_gilead:
This may be off topic but.....

I am a huge fan of doc holiday getting a new t999(l)

......and lemon meringue pie .

:beer:
[T-Mobile, Samsung Galaxy SIII] ortind200:
anyway, does anyone kno when 4.3.1 will come out for tmo?
[T-Mobile, Samsung Galaxy SIII] Perseus:
[MENTION=3355398]mrRobinson[/MENTION] has already posted a Root66 for the Samsung 4.3 update for T-Mobile S3. Official rollout is backtracked after several users reported hard bricking from official updates.

[MENTION=411699]Docholiday[/MENTION] too hardbricked his S3 trying to bring the leaked 4.3 Rooted.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Lol! Just to clarify though, I bricked by testing while trying to find a fix for wifi not working on the stock kernel. Had nothing to do with the official update and Im betting the chances of anyone doing exactly what I did are quite slim! :silly:

I do not know where you are getting the 4.3.1 stuff. From what I see you are the only one talking about it and unless I missed it, I have not yet seen a link where you are basing your information from. Besides, even if they already are making plans for it, you are getting waaay too impatient! At the earliest, maybe in a month. More likely a little longer. If at all. Continuing to ask about it won't magically make us know more than the last time asked. When it is time, it is time and discussion will take place then.

Current rollout status:

ALL T999 variants (EXCEPT T999N) have now been updated to 4.3. OTA's are still rolling out though.

To be clear: T999, T999L, T999V (Mobilicity, Wind, Videotron and Eastlink) are now officially on 4.3. You can find the stock firmware in my firmware thread for a much faster download.

If and/or when mrRobinson makes root66 versions for these, you will find links in this thread, and I will link to his downloads in the firmware thread as well.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Well I seemed to have missed some drama... Luckily we have mods who are on the ball :)

Back to business, I'll throw up some T999L and the other variants, Doc had mentioned people were asking about them. Give it a day or two.

Thanks.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Appreciate if you could Link the T999 Root66 in the OP.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
It's been there... should i make it red or something to stand out? I think i've done that for new images in the past.

Edit: Just added "New!" in red.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
I have been following this thread and want to update to the latest firmware. I am running the previous Root66 injected from this thread and I have Odin Pro and TWRP recovery. All this discussion of bricking has me concerned. I also am out of warranty so no longer concerned about bootloader counter.

What is the best way for me to proceed. Should I just get the new version off this thread and install?

Thanks all, again and as usual,for all the great work and help!
[T-Mobile, Samsung Galaxy SIII] ortind200:
well i too was worried abt bricking. i successfully flashed the latest root66 on my couzin's phone. im waiting to flash my own phone but need to replace my laptop soon. u shouldnt worry. just odin it as long as u got a T999. but if ur still hesitant, just wait for others to flash theirs. no rush. and ur really not missing anything with 4.3. believe it or not, its a battery drainer and has ram probs. hopefully 4.3.1 will correct these issues soon. hope this helps.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
That does help. I think I will just wait for 4.3.1. Thanks
[T-Mobile, Samsung Galaxy SIII] ortind200:
sounds like a smart move! good choice, my man.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
As far as I am aware the only people who have bricked are those who tried to flash back to an older firmware after updating to 4.3. And the only way to do that is to try flashing the firmware in recovery. (There is a thread that provides a recovery flashable package). If you try to Odin flash back to an older firmware, it will just fail before actually doing anything, meaning it won't brick.

The only real thing you should consider is that if you update to 4.3, there is no going back to an older build. You can still flash older roms, just not the firmware.

There is also a new Warranty Bit in the 4.3 bootloader that matters to some people. Once tripped, it cannot be reset.

If you want to decide for yourself if you want to update, why not give one of our 4.3 roms a try. For many they have been very stable and run very well. Only a small percentage have had problems, most of which are solved by flashing clean.

Its a very good way to decide if you want to take the plunge and fully update. Or if you like how things run, you can just stay on the rom and not worry about the firmware for now. But this way, you can easily go back to a previous setup if you don't like it.

Its your call of course. But there are alternatives.
[T-Mobile, Samsung Galaxy SIII] lanzero:
Hey ortind200, when you flashed your cousin's phone, did the warranty counter blip to 1? I ask because my friend flashed his with the latest root66 and his counter showed up as 1. Very strange.
[T-Mobile, Samsung Galaxy SIII] calexchelse:
When I flashed mine, the flash counter tripped but not warranty. The warranty counter tripped when I odined cwm.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
That is great info and advice. When I have the time I will Nan backup and try a 4.3 ROM.

Thanks!
[T-Mobile, Samsung Galaxy SIII] Woody:
Gentlemen. This thread has thoroughly been cleaned now. If you do not have anything to put forth regarding the development of Root66, then do not post in here. I have either edited or deleted your posts entirely to preserve continuity of the work that is being done.

If you have an issue with each other, take it to PM or put each other on Ignore. If you have an issue with a Moderator, then bring it to me, but it surely better not be some bull-squat with no justification behind it.

Thank you and have a nice day.
[T-Mobile, Samsung Galaxy SIII] ppgregory:
I flashed the latest root66 coming from Docs Official deodexed rom on the 4.1.2 firmware and the ATT unsecured kernel. Everything works great except for wifi won't turn on. If I flash the ATT kernel again all is well. Any ideas as to how to run wifi with the included root66 kernel?
[T-Mobile, Samsung Galaxy SIII] uvt_novice:
Question to the OP whether Root66 is upcoming to Wind 4.3 Firmware? Thanks.

Confirmed brick when tried to flash Root66 WindJB2 after applied OTA update to Android 4.3. Odin fails, verification fails. Phone is not booting, stuck at firmware error.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Wifi won't work unless you flash the full firmware update. If you're running the 4.3 rom on older firmware you will need the ATT kernel. No other way right now.

Pretty sure he's working on it. Once you update to 4.3, you cannot flash back to older firmware again.
[T-Mobile, Samsung Galaxy SIII] sonwon:
Call me curious, what will it take to get WiFi working without the ATT kernel?
[T-Mobile, Samsung Galaxy SIII] ppgregory:
Thanks. I'm getting confused on what's rom and what's firmware. Thought the root66 in op was the latter.
[T-Mobile, Samsung Galaxy SIII] uvt_novice:
Yeah, noticed that. Phone was bricked, soft unbrick didn't work out. Flashed last OTA (4.3 Firmware) Update through ODIN, thanks God, returned to my Stock ROM.

Decided to to void warranty - flashed TWRP recovery in ODIN, then flashed stock based custom ROM, everything is ok.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Someone would have to decompile the T-Mo stock kernel and then go through the code. High chances of Brick there as Doc said.

Technically Firmware typically includes a Bootloader and Modem. Here in this case it also includes Rom making it a complete package. Root66 is a Firmware package all in one.

One easy criteria to distinguish is that firmwares are mostly .tar.md5 files. Roms are .zip files.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
From what I can tell, the wifi modules are being built into a different partition now, so if you don't flash the firmware, you won't have the correct ones for that kernel. Either this is just a T-Mobile thing, or Samsung had not yet started this on the MJ2 kernel, and we were just lucky enough to get it. I think the goal was to force everyone to fully update.
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
OP Updated, all images.
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
So as I see with the 4.3 rom notes, the warranty bit will still read 1 after using this method? I appreciate all the hard work you guys do to root these ROMs for us, just trying to get a clear understanding of this whole Knox situation, and whether or not i want to deliberately void my warranty.
[T-Mobile, Samsung Galaxy SIII] red rocket:
I flashed the new file for t999l and se is still enforcing. I flashed the file then did a factory reset. Su binaries are not installed.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
There is no way to reset the warranty bit.

I don't think he usually does anything to the kernel.

Ooen SuperSU and hopefully itkk uodate the binary.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Nice work, as always!

Thank you for continuing to do this for all of us!
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
So to clarify, I am on 4.1.2, And the only way to get 4.3, rooted, is to flash your Rom, mk4 modem, and at&t kernel and keep 4.1.2 firmware?

Otherwise we get the warrant bit tripped?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Thst is correct.
[T-Mobile, Samsung Galaxy SIII] lanzero:
Ok now i'm confused. Are you saying that this is the ONLY way to get doc's rom?
[T-Mobile, Samsung Galaxy SIII] masondoctorjt:
There are many other ways to get doc's rom. I am trying to figure out how to get a rooted 4.3 Rom WITHOUT tripping the warranty bit in knox since my gs3 is only 2 month old. And as far as i can tell from reading about the new firmware, is that this is the only way. Sorry if i am confusing anyone.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
The ONLY way to flash any 4.3 custom rom and not trip the Warranty Bit

is to do as he had stated a few posts back and not update to 4.3 firmware to begin with. Keep your base firmware as 4.1.2, and flash the rom from recovery. Modem and kernel too if needed.

If you fully update to 4.3 firmware, you will trip the warranty bit when you install cwm or twrp.

You can try to use Mobile Odin so you don't have to flash recovery, but I'm willing to bet if you flash a custom rom or kernel, it will likely trip it as soon as you boot up anyway. Mobile Odin may trip it on its own anyway.

its a trade off and there's no way around it. Either fully update to 4.3 an accept losing warranty and thst you can never flash older firmware. Or just flash the roms and accept that you may have a few bugs (maybe) and you may be more restricted in your current and future options (such as the kernel).

Some stuff may get worked around as we go, but other things such as warranty bit will likely never be solved.
[T-Mobile, Samsung Galaxy SIII] DenisGuy:
Hi! I have a bit of an issue, here.

I have a t999v on Videotron. I'm trying to install cm10.2.

I installed MrRobinson's route66 firmware version root66_VTR_T999VVLUEMK5.7z (which I thought would give me root). However my phone keeps saying that I have "root privileges" but not "root", and I suspect that it's because it loses root when I install CWM. He does suggest a couple of paths on how to keep root but I get the same error whatever I do in CWM: status 7. It gives me status 7 in CWM if I try to flash either of MrRobinson's OTA updates or if I try to flash cm10.2. Also, when I ask CWM to reboot, it always asks me if I want to "fix root". I accept, but it comes back every time.

Lastly, I don't have root on the phone even right after flashing MrRobinson's root66 with Odin.

What am I doing wrong?
[T-Mobile, Samsung Galaxy SIII] skewty:
Did you go Settings - About and click on build number 7x to enable Developer Settings and then find the Root option and set it to apps and adb?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Update CWM to latest version for the Status 7 errors.

+1
[T-Mobile, Samsung Galaxy SIII] lanzero:
Ok, let me get this right. I updated to 4.3 but I'm not rooted yet. So, in order to get root and be able to flash custom ROMs without tripping the warranty is to install root66?
[T-Mobile, Samsung Galaxy SIII] Perseus:
Yes that is correct. Make sure to use ONLY the 4.3 Version of Root66. Do not try older versions as they will Hard Brick your phone.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
Flashing 4.3 root66 could give you root without tripping warranty bit but once you flash custom recovery it will trip.

Also once on 4.3 bootloader, using odin to flash an older rom that has an older bootloader in it will brick the device.

If you don't care about warranty. After rooted you can flash custom recovery then from recovery flash custom roms new or old as long as they don't have the bootloader in it(most don't). One limitation is The older roms updater script may have an assert check that won't allow it to install because it doesn't know the new bootloader is a valid one.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Since I am out of warranty I no longer care about the tripping the flash counter. I am running the injected 4.1.2 UVDMD5 ROM from this thread. I would like to try Kitkat. I tried flashing the "Gummy" version of CM from this forum via TWRP. I ended up with a soft brick and no root privelages. I could not mount my USB flash drive with my Nandroid but fortunately had an older Nan on the internal memory so was able to recover.

I would like to try again with either the same ROM or the CM11 unofficial RLS5 kitkat rom. I am a little gun shy now.

Any recommendations? Is this just a bad idea? Did I screw up the first time? Do I need to update bootloader? Should I flash with Mobile Odin or in recovery. I have read that Odin reads the partition info from the image and might cause a brick if it makes changes.

Edit- Just tried flashing the Gummy CM 11 4.4 again but I it failed again. Any suggestions? Do I need to move to a 4.2 or 4.3 Rom first?

Thanks.
[T-Mobile, Samsung Galaxy SIII] lanzero:
hi athlonxp.. thanks for the reply. so after i'm rooted i can flash old or new custom roms thru CWM as long as they dont have a bootloader older than 4.3... is this also right?
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
That is right. Once on a 4.3 bootloader you cannot use Odin to flash something with an older bootloader.
[T-Mobile, Samsung Galaxy SIII] marcmarshall:
Could you just uncheck the bootoadder in Odin mobile or flash from recovery? I read a problem with Odin mobile was that it writes the partitions from the image and could mess you up that way though I don't understand why.
[T-Mobile, Samsung Galaxy SIII] lanzero:
Something here doesnt make sense. Older custom roms by nature have older bootloaders. So how can I install older custom roms and not brick my phone when they got older bootloaders? Can you explain this?
[T-Mobile, Samsung Galaxy SIII] Perseus:
The newest 4.3 Bootloader specifically prevents you from installing older Bootloader. It will blow the eFuse to keep you from doing so. Once the efuse is blown your device is hardbricked.
[T-Mobile, Samsung Galaxy SIII] sonwon:
Why would Samsung purposely hard bricked phones? Do they hate downgrades that much? Rhetoric questions, no reply needed. My next phone may not be a Samsung. They seem intent on going down the same path as HTC, not listening to their customers.
[T-Mobile, Samsung Galaxy SIII] athlonxp2300:
Most custom roms that you flash from recovery do not include the bootloader or modem. They just have the system and kernel.

Firmwares that you flash with odin are mostly complete and have the bootloader, modem, kernel, and system.
[T-Mobile, Samsung Galaxy SIII] Perseus:
Who knows ? Your guess is as good as mine. I suspect 3 reasons. Prevent Rooting, Prevent Network Unlock & Enforce Non-Circumventing Flash Counter.
[T-Mobile, Samsung Galaxy SIII] belly1026:
Thanks for the quick reply! :good:
[T-Mobile, Samsung Galaxy SIII] darkdelusions:
This work great for me I check my counter and it still 0

On a side note is there a wi-fi tethering app that work on this build. I tried Barnacle but it doesn't seem to be working.
[T-Mobile, Samsung Galaxy SIII] WackyJoe:
Hmm...

Sorry if this was already resolved, but is there a way to go back to stock to "reset" the counter to 0 and then put this on?

I already jumped the gun and have 1 counter and I don't want to worry if I have a warranty issue...this is the first release so there might be problems in the near future for me or for any one of us.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
There's no way to reset the counter so far. Not sure if there will be one soon. It looks like the developer of triangle away (app to reset counter) don't want to spend time working on his app to support GS3. I will donate $40 if he does, tho.
[T-Mobile, Samsung Galaxy SIII] darren.wlsn1:
wifi tether from market works 3.1-beta 14 and in settings/device profile i changed mine to "samsung galaxy nexus gsm"
[T-Mobile, Samsung Galaxy SIII] WackyJoe:
???!!!

Doesn't want to spend the time? :eek:

It's only one of the most popular phones to hit the market...and there's literally millions sold...though not all would be rooted (I wonder what the % is of phones being rooted?) There's gotta be a market for it, no? :confused:
[T-Mobile, Samsung Galaxy SIII] :
Because he has the international one. He made it for that, but doesn't care about these ones since he don't own them.
[T-Mobile, Samsung Galaxy SIII] WackyJoe:
Hmm...

I remembered Zedomax sending out and posting a link for a petition, how does one go about doing that? I would think that if someone could start a petition to get the US S3 supported, he would...especially if he sees people pledging something towards it. What does everyone think of this idea? :confused:
[T-Mobile, Samsung Galaxy SIII] :
I guess a thread with supporters would work. Then show the dev. I'm sure with a hefty amount of money offered, he'd do something.
[T-Mobile, Samsung Galaxy SIII] fireboypr:
I tried starting a bounty thread with some $ i would love to see more people joining

EDIT: Donated!
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
Ahhh, we can use terminal emulator! Somehow I missed that one. Too tired to safely do anything tonight. Bound to screw something up so I'll wait until I'm fully awake tomorrow. I thought my flashing days were done but I miss being able to do so much more with my phone.
[T-Mobile, Samsung Galaxy SIII] mike216:
Hi guys I downloaded and ran busy box from the market on stock with this root method. Should I be find or is there anything I need too do or look out for?

Thanks for all your help
[T-Mobile, Samsung Galaxy SIII] jaliscojorge:
Don't forget you can use rom manager as well.

typed from my white sgs3 hungry for some Zen
[T-Mobile, Samsung Galaxy SIII] mrRobinson:
Nothing bad will happen. Your phone will feel a little happier on the inside though.
[T-Mobile, Samsung Galaxy SIII] RaymondPJR:
I haven't. I reading up on the EFS issue to make sure I understand it first. I feel like my fingers are tied together on this unrooted phone. I really can't go back to not being rooted. First order of bussiness will be to install some of my favorite notifications. I know it's subjective, but I don't like any of the stock ones. I'm all happy and giddy again now that I have an unmarred replacement for the one I dropped.:D