yashsingh1/xdaforums huggingface dataset:
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
knox is easily removed. see our 4.3 rom threads in development. they may have added something hw in the Note3, but i havent heard about it. if youre referring to the knox counter, that is irrelevant to us it appears. its the warrany bit screwing us up.

dont forget, tge s3 was not built with seLinux or Knox in mind, which in the end may prove an advantage for us. Even now, I am convinced that knox was never intended for the S3. The counter being absent is a big deal considering how imoirtant it is to knox on newer models.

---------- Post added at 11:52 AM ---------- Previous post was at 11:46 AM ----------

@all

for the time being if you want to try out the new 4.3 release, i recommend downloading my deodexed, knox free Rom. You can gain all the benefits, without being screwed by this warranty bit. ill post links and update my op there shortly, but for now, the leaked rom is in the op, and the official is on the last page or two.

i do not suggest flashing the ota or the firmware.

can someone please try to grab a copy of the OTA for me? downlosd it, but then choose to postpone install. then you can copy it, if rooted of course.
[T-Mobile, Samsung Galaxy SIII] jim45:
Does the act of rooting (via root66, not insecure kernel exploits) and replacing system APKs trip the counter? I don't use custom roms, kernels, or recoveries anyway.

Can you please clarify whether it's the inability to flash older versions or the inability to flash anything? The latter somewhat scares me...
[T-Mobile, Samsung Galaxy SIII] tamasrepus:
Voodoo OTA Rootkeeper?

Has anyone verified that Voodoo OTA Rootkeeper is able to preserve root after updating?

Supposedly, it does not work on 4.3 ROMs. Anyone who has root on their 4.1 ROM will lose it on the upgrade to 4.3.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
all i know is you can flash the 4.3 firmware again. older firmware aparently not. no idea about recoveries.
[T-Mobile, Samsung Galaxy SIII] jim45:
Well that helps a lot. Is it possible that flashing older firmware is disabled since there were so many changes between 4.1 and 4.3, that downgrading would introduce incompatibilities and cause bricking?
[T-Mobile, Samsung Galaxy SIII] loserskater:
Did your leaks have aboot, sbl2, etc. or were they only system, boot.img, and modem?
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
i have no idea if this would work, but i dont see why it wouldnt. if any of you have thoughts to add, please do so.

if youve found yourself stuck on the MJC firmware this could possibly allow flashing backwards to older versions.

Note, this is just a brainstorm and i cannot test it myself, so no guarantees, and i cant say it wouldnt cause more problems. In theory though, it seems to me that this would work.

flash cwm/twrp

flash the MD5 firmware in recovery, from this thread: http://xdaforums.com/showthread.php?t=2282603

reboot download mode and flash the firmware of your choice via Odin.

Rememer, anytime you go backwards you will have to factory reset if it hangs at bootup.

I am not suggesting anyone try this. i am just putting it out there for critique and perhaps spark more thoughts and ideas on the issue.
[T-Mobile, Samsung Galaxy SIII] 4Orr:
After flashing the new firmware and before setting up the phone I immediately went back to the download mode and flashed the latest TWRP recovery. I then restored a 4.1.2 nandroid and flashed the LJC modem, but I lost 4g and cell reception. All attempts to flash old official firmware and route66 files failed in Odin. After re-flashing the new firmware, I was lucky to have both 4g and cell reception restored.

Looking back on it now, perhaps I should not have flashed the older modem.
[T-Mobile, Samsung Galaxy SIII] Vigz:
This is exactly what I did that caused the brick. I had CWM and I flashed the MD5 Firmware/Bootloader. Once you exit out of CWM, it results in a hard brick with QHSUSB_DLOAD. I don't think there is an option in CWM to directly reboot to Download mode. However, TWRP does.
[T-Mobile, Samsung Galaxy SIII] 4Orr:
Yikes. Decisions, decisions! :)

I noticed there is an option for wiping the NAND in Odin. Had anyone ever attempted this before flashing?
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
I agree that the S3 wasn't designed with KNOX in mind. Looking over at my S3 the only thing I can say now is don't update and stick to AOSP ROMs and 4.1.2...consider the fact 4.3 doesn't exist and if you need 4.3 use Doc's leak..its essentially the exact same thing. That being said if you haven't upgraded yet and you plan to, advance upon it with extreme caution. And back up all important files and data first of course.
[T-Mobile, Samsung Galaxy SIII] Woody:
^^^ See it came in the mail today like you were expecting. My guess is under 15 minutes before you rooted.

I agree. If someone wants to use the 4.3, they should just use Doc's (or anyone else's) leak ROM without all this crazy KNOX and Warranty Bit. They should have called this the Official Point of No Return update.
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Its like you know me entirely..lmao. 10 mins to be exact. SIM was activated after rooting but s3 is gonna be my CM11 testing device etc before I sell it. Cm11 kang still coming tonight..just wrapping it up. Have been super busy.

Also, you heard the man. If a mod, and at least 3 RCs are saying to NOT UPDATE, don't do it unless you an iPhone running Touchwiz.
[T-Mobile, Samsung Galaxy SIII] scifan:
At this point, I have zero interest in this particular update... and will probably ONLY install it if I've taken my S3 back to dead stock... (I think I know a pattern to follow that would zero my flash counter before upgrading to 4.3...)
[T-Mobile, Samsung Galaxy SIII] almighty bob:
the notifications i found to be from a mail setting (my work exchange account that I had checked off "download all attachments") once i unchecked that, no moe notifications. i had that unchecked for all my other accounts (didn't trust them) but did for uncle splam...

people who updated and still getting the notification spam should check that setting in mail and remove it if checked..

working great for me, i'm sure there'll be a work around by the time the next update comes around for the warranty bit bizness.
[T-Mobile, Samsung Galaxy SIII] mrmako777:
ugh...this thread is disappointing. i cant ever remember a time downloading a new firmware and not being rooted within minutes. samsung has gone bonkers with all this and i used to hate htc for the same thing. seems like the only thing left to do is to stick with a GED. hopefully you guys figure out something soon (waiting patiently) :)
[T-Mobile, Samsung Galaxy SIII] scifan:
That was how Doc bricked his S3... he was writing the individual partitions and after writing sbl3 (I think) his phone became a brick... and his attempts to recover it have not gone well... :(
[T-Mobile, Samsung Galaxy SIII] nsxalwayz:
so other than the Warranty Bit and KNOX, how is 4.3 running? Smoother? faster? Better battery life?
[T-Mobile, Samsung Galaxy SIII] Jay Rock:
I gave in and went stock OTA update. It's really the same as the leak. Obviously a lot smoother, but it has its hiccups which were present in the leaked one as well, including, but possibly not limited to, the recent apps taking it's sweet time to go away when trying to exit it and the weather/clock widget on the homescreen redrawing a couple times.
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
This if anything is a job for the mystical Chainfire haha since rooting is his speciality and he developed TriangleAway.

And for those who are already stock OTA and you're getting launcher redraws often try checking your RAM usage. It doesn't always redraw. But theres a tweak that causes it stay in memory..but you unfortunately require root access to utilize the build.prop tweaks...

​
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Well, I have everything but aboot (the one i believe i needed the most at the time), but i did not include them in the roms, nor publicly release any of it if thats

what you were wondering.

Rom includes system and kernel only. I left tge modem as a separate flashable pkg since we have two to choose from, and more importantly, i personally dont feel any rom should include a modem by default. It only needs to be flashed once, not every time someone wants to reflash the rom.

ok, i wonder why though. it doesnt make sense since once its flashed the MD5 data is now fully written. Once booting up agsin it would only have MD5 available to load. if that makes any sense to you guys....

---------- Post added at 03:31 AM ---------- Previous post was at 03:12 AM ----------

I left HTC for exsctly the same reasons (plus no sd or user accessible battery).

Instantly loved the S3 and Samsung due to the hardware and dev friendliness! Almost feels personal now that they are going the way of htc, and dare i say, apple! I know everyone says to just go Nexus, but i will admit, i just really prefer the offerings of TW, and the features of Sammy phones. For someone like me, its starting to feel like theres not much left!

Yup. Sbl2 flashed fine, no prob. Sbl3 flashed fine, booted perfectly normal, then entered reboot recovery in terminal and it has never turned back on since.....

:eek: :mad: :confused: :banghead: :( :thumbdown:

Check our rom threads. Flash one and give it a whirl. Highly doubt youd be dissapointed!

If you decide to root and flash any roms, will you let me know? And consider answering some questions about your experience doing so?

There may be some graphics options in Dev Options that coukd help.

As for chainfire, who knows. He has been warning us this was coming since before the S3 released! Has always said it will get to a point where he can no longer do anything to get around Sammy. Hope this isnt that point....
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
I recall him saying this. A wise prophet tells no lies. This played a huge role in getting the Nexus 5 for me. So far, I'm ecstatic about the N5. Sell your S3's for 300, and buy a 32GB Nexus 5 for 400$ lol

But yessss, Force GPU Rendering in Developer Options may help with it a bit. But the problem is not with the GPU or CPU, it's because the launcher is being killed and reloaded back into memory.
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Really appreciate the effort your are putting in for the 4.3 update. So if we flash the 4.3 update flashable zip file you have posted, can we revert to older 4.1.2 through ODIN?
[T-Mobile, Samsung Galaxy SIII] arnoldkevin:
is there a difference between this firmware and saranhai's leak? :D
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Let's rephrase this..

No noticeable differences in this release and Doc's original leak release. Saranhai and I's ROM are based off of Doc's base. Though because this is a full dump (it's official) there are some differences between that and Doc's official leak release. That being said if you wish to keep root and the ability to use AOSP and downgrade, stick to Doc's/Saranhai's releases and don't go official through OTA or ODIN.
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Right, the big difference being thst you should not flash the official firmware or take the OTA update, if you havent already. You should flash either my or saranhai's roms! :thumbup::cool:

A few people did hsve some issues, but i believe most were really quite happy and rather surprised by how good the roms work. If i ever get another phone i am hoping to build a more customized Rom using the current one as a base!
[T-Mobile, Samsung Galaxy SIII] matrixzone:
Stupid question: But your ROM is still based on leak and not the official version. I have seen 4.3 official update zip which you have posted in some thread, but think will make downgrading impossible
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Actually, I had posted a Rom based on the official released firmware earlier. Updated op with a link to that post, plus added info in a new post to the thread.

Flashing the Roms will NOT bring any of the issues you have seen about downgrading and the Warranty bit and all of that stuff.

Flash the Rom, not the firmware. And it doesnt matter if you use the leak or official rom...they are the same. Read my OP where I had predicted this would happen when i first released it.
[T-Mobile, Samsung Galaxy SIII] scifan:
Look at th leak#2 thread...
[T-Mobile, Samsung Galaxy SIII] uoY_redruM:
Gave the phone to my wife when I bought my G2. She updated it while I was at work :/

Hopefully I never want to root it again, lol.
[T-Mobile, Samsung Galaxy SIII] HoustonsBirdman:
Definitely disappointing to see Samsung do this.. I (unfortunately) in recent months bought my S3 instead of going with the S4 because I figured the S3 would have way more Devs support and options for ROM's .. Now this!.. Definitely won't be updating to the new Firmware! They gotta be crazy! Its a big WTF moment for them, for sure! I'm running Doc's "Leak #2" and love it.. So I guess I'll be loving it even more now since I can actually still downgrade, change ROM's, etc! Thanks for everything you've contributed .. Ain't nobody gonna hold it against you if you can't get another S3! If I bricked a smashed up S3 like you said yours was, I wouldn't be going back to the same phone either when there are newer, more appealing models out now! Just let us know what you decide to venture in next (and I'm sure some of us will follow you to a new device once our funds are right to purchase it :D)
[T-Mobile, Samsung Galaxy SIII] pyrorob:
just thought id post some news about this knox/warranty bit business.. i fell victim to it after blindly wanting to go test the new 4.3 update, but have been doing some reading regarding it.. thought id share some links..

apparently this can let you get root without tripping the bit: Universal Root de la Vega v0.2 - Public Preview [KNOX 0x0 Root] (look at the last post for mirrord files) and heres a guide regarding this method: Warranty Safe Root for KNOX-installed Samsung Galaxy S4, S3, Note 3, Note 2 and other Samsung devices

also theres kingo and vroot mentioned here: [Q] One click Root keep KNOX WARRANTY VOID: 0x0 without losing data for android 4.3 but both those tools have been deemed suspicious.

heres a thread where there actively trying to reset the bit and have a bounty: [Bounty] Reset KNOX counter to 0x0 (UPDATE- $2142) from the info they have received it appears that the bit could be reset and that samsung doesnt admit it publicly, they do have a tool to do just that, so theres hope!

also the att 4.3 update just pushed out adds the warranty bit as well.

well i hope this info helps anyone, i havent tried any of the root methods... yet.. but if someone would like to bite the bullet and test it, please report!
[T-Mobile, Samsung Galaxy SIII] scrim:
Long press one of the download notifications, choose the App Info thing that pops up, then you'll be in App Info for the download manager, now press Clear Data. This fixed it for me.
[T-Mobile, Samsung Galaxy SIII] ruskastud:
Didn't work for me....................
[T-Mobile, Samsung Galaxy SIII] ramkumar19890:
Guys, I have installed 4.3 update via odin , that removed root and updated my system to 4.3! I don't know whether I had triggered the warranty counter or the counter that knox has! But I just wanted to know whether any of you guys are having a problem with the inbuilt gallery app crashes when an image is clicked to share! I had performed a factory reset when the installation has been completed with 4.3! If you have any relevant issues please let me know!
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
first ive heard of it.
[T-Mobile, Samsung Galaxy SIII] someonenewhere:
I did that and nothing, that's why I did a hard reset...

I'm back to normal though
[T-Mobile, Samsung Galaxy SIII] ramkumar19890:
I fixed it , when disabling the "paper artist" ,the gallery would crash! So I have to keep this dumb app hidden, so that my gallery would work properly :)
[T-Mobile, Samsung Galaxy SIII] Fr0stbyteX:
I've been following along with this thread and I understand that once you Odin to the new release that you can no longer Odin back to an old release, but I guess I don't understand why that's such a big deal. I Odin'ed to the new release and was able to get root, run that release for a little while, and then go back to running CM11 just fine, which I've been running ever since. My warranty bit is set to 1 just like everyone else's. Other than not being able to flash back to MD5 or reset my warranty bit, what am I not able to do at this point?
[T-Mobile, Samsung Galaxy SIII] TheLastSidekick:
Assuming you're able to root, nothing. The problem is if you can't go back to 4.1.2 you're forced to stay on 4.3 which isn't as stable. And if you can't root that means no AOSP based ROMs.

​
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
Actually id have to slightly disagree with this. It really only matters if you care about warranty, or flashing older modems. True you cant go back to old firmware, but you can flash cwm/twrp and from there you should be able to flash a 4.1.2 rom.

Now, if the underlying f/w is causing some bugs i dont know. cant run it myself and have seen no reports either way.
[T-Mobile, Samsung Galaxy SIII] SovPanda:
they don't have wifi calling though? :(
[T-Mobile, Samsung Galaxy SIII] Fr0stbyteX:
Ok, thanks. I wrote off my warranty a long time ago so I guess it's not a big deal for me but I can understand why this will annoy many people.
[T-Mobile, Samsung Galaxy SIII] mrmako777:
So we can actually get root the old fashion way with this update? I was under the impression the warranty bit and/or knox prevented this. I'm not real worried about going back or warranty status as long as I can get root
[T-Mobile, Samsung Galaxy SIII] DocHoliday77:
yes they do. fully functional last

i checked

you can root, but yes seLinux snd knox together will defeat you at every turn. but technically youre rooted. If you want root, just flash a rom, problem solved. seLinux msy still cause dome issues, but nothing compared to adding knox to it.
[T-Mobile, Samsung Galaxy SIII] kingston73:
Might be a stupid question but what is " the old fashion way"?
[T-Mobile, Samsung Galaxy SIII] Vigz:
[MENTION=4081205]DocHoliday77[/MENTION]

The files that were in the zip that I flashed were:

sbl2

rpm

tz

sbl3

dd

aboot

NON-HLOS
[T-Mobile, Samsung Galaxy SIII] mrmako777:
Ah so it cripples su basically making it useless? Isn't knox optional on this update?

Flash recovery, flash su.
[T-Mobile, Samsung Galaxy SIII] 4Orr:
I Odin flashed the newly released firmware and while I was able to Odin flash TWRP recovery, my restore from a 4.1.2 nandroid resulted in a loss of IMEI. When I re-flashed the new firmware my IMEI was restored. I then flashed the TWRP recovery and flashed the z999 UVDMD5 (Modified) Stock TouchWiz ROM in recovery and did not lose IMEI.

While I'm a little upset Samsung's implementation of SELinux and KNOX in the new release, Doc and others will release modified versions. I am pleased with the new modem and the ability to flash older custom ROMS that have support for such things as Google Wallet.
[T-Mobile, Samsung Galaxy SIII] scifan:
I'm still coming to grips with the ramifications of their changes... this feels alot like when Sony decided to make it so Playstation 3's could no longer run Linux... give something, then alter the hardware/software agreement after it's been released... (in this case, downgrading if you don't like the way it's performing...)

Tomorrow I should have my wife's new phone... which isn't Samsung... I'm pretty certain when I'm ready to move on my next phone won't be Samsung... we'll see if they decide to right their wrong's on this one...
[T-Mobile, Samsung Galaxy SIII] ramkumar19890:
Did anyone sign the agreement that came with Knox ? If not ,is it possible to rolled back to 4.1.2 with ease without signing it?
[T-Mobile, Samsung Galaxy SIII] Aerowinder:
If you took the OTA update, you aren't going anywhere. You can install custom ROMs again, but do not attempt to downgrade the firmware.
[T-Mobile, Samsung Galaxy SIII] SovPanda:
oh whoa, didn't think the leaks would have wifi calling with them, ty!
[T-Mobile, Samsung Galaxy SIII] Jay Rock:
Wait wait wait, I just skimmed over a few posts, and from what I read, I can flash a custom recovery and then a custom ROM??
[T-Mobile, Samsung Galaxy SIII] allendj81:
So there is no way to root this update yet? I want to flash the official update with all its securities and what not, but I'm hesitant to do so because I haven't seen a trust worthy way to root correctly without any issues. I bet if Doc or Sidekick still had S3's, this update would've been their ***** already :D Now all the dedicated devs are mostly gone :(
[T-Mobile, Samsung Galaxy SIII] ramkumar19890:
I think ,I made a blunder of myself by flashing 4.3! I thought Knox is secured for its selinux, but I never realized that NSA.created selinux for snooping around Samsung phones! By they way I didn't sign the agreement...
[T-Mobile, Samsung Galaxy SIII] calexchelse:
What is this agreement that I keep hearing about.

TW 4.3 WITH A TOUCH OF KITT KATT
[T-Mobile, Samsung Galaxy SIII] Vigz:
The security Samsung created such as the Knox Counter (apparently renamed to Warranty Bit for 4.3 on Download mode) is activated regardless if you accepted the agreement that is shown when you open the Samsung KNOX app on the phone. Knox Counter: 0x1 is the exact same thing as Warranty Bit: 1. If you flash any images that are not signed by Samsung (aka CWM, TWRP, CF Auto-Root, etc.) or any official firmware image that doesn't have Knox (ex. UVDMD5 and older), the counter will be tripped.
[T-Mobile, Samsung Galaxy SIII] ramkumar19890:
I have had installed the latest CWM for the official firmware (4.1.2 rooted), to get rid of all the t-mobile bloatware! When I received the news that, the new firmware 4.3 had arrived with many complications such as KNOX and Warranty issues, I didn't bother to try...

So, I downloaded the official firmware from Sam Firmware , flashed it via Odin 3.07 Successfully! Then the OS started to update at startup! After that , I performed a factory reset and once again I factory reset the phone in the recovery mode!

As you have mentioned that Warranty Bit:1 would appear if I had a custom firmware before, but for me it shows Warranty Bit: 0
[T-Mobile, Samsung Galaxy SIII] ramkumar19890:
This is what I get in "Download Mode"
[T-Mobile, Samsung Galaxy SIII] zer0trip:
Unless Samsung fixes this quickly I will not purchase another Samsung product.
[T-Mobile, Samsung Galaxy SIII] Adryanxxx:
I managed to downgrade my sgh-t999 from 4.3 to 4.1.2 with TWRP, I was lucky to have a TWRP backup on my sd card. :laugh:
[T-Mobile, Samsung Galaxy SIII] rcsrich:
Well, just took the 4.3 OTA, we'll see how things go. I'm not too worried about root- have yet to root my S3 anyway.

Quick question- does anyone know if Knox is active if you never install? I selected the shortcut because I was going to uninstall it (saw directions for uninstalling from Note 3), but when it opened, it asked me if I wanted to install Knox & I just backed out.

I did get the annoying download notifications for past downloads, went into download app & cleared out lists, so we'll see if that does the trick.

I'm going to keep my eye on general functioning & battery usage and may to a factory reset if I don't like what I see...

Something else simple I wanted to mention that I picked up from my past life of ROM tinkering- after doing any kind of upgrade, let the phone do its initial reboot, let it settle for a few minutes, then do a second reboot before you really start doing anything. Doing this has helped get rid of some of the little quirks that pop up after a major system change...
[T-Mobile, Samsung Galaxy SIII] thetolsonator:
If it weren't for the lack of wifi calling on the N5 I'd have done that in a heartbeat. That's the big deal breaker on any device since I moved from Sprint to Tmo.
[T-Mobile, Samsung Galaxy SIII] rcsrich:
Speaking of, hows the battery life on the new N5 comparing to the S3? I'm thinking I could deal with it if it is at least no worse...