yashsingh1/xdaforums huggingface dataset:
[T-Mobile Samsung Galaxy S 4] itzik_man:
Don't confuse Knox the application vs Knox coding...

Knox coding is possible imbedded in the 4.3 kernel or (make more sense) in the hardware itself (for enabling when you need the app).

What you install or remove, its the application only & not the source code of the Knox security system.
[T-Mobile Samsung Galaxy S 4] RiverCity.45:
Hoping my favorite ROM developers come up with a functional ROM without Knox e-fuse.

Sent telepathically
[T-Mobile Samsung Galaxy S 4] dcd1182:
uhhh, this is the same behavior that every rom on every device has had for a very long time. you can stop the stock rom from overwriting recovery the same way you could have done so in MDL, so its not a "new protection" or a "locked bootloader" or anything changed from previous instructions.

how come i didnt have any issues with it?

---------- Post added at 12:29 PM ---------- Previous post was at 12:28 PM ----------

its in the bootloader and cannot be removed (downgraded) without mfg tools. there is an accompanying apk which he downloaded and then later uninstalled via app manager
[T-Mobile Samsung Galaxy S 4] RiverCity.45:
Jovy's ROM removed the Knox apps, but the e-fuse remains. If you load it, you'll still trip 0x1 status.

Sent telepathically
[T-Mobile Samsung Galaxy S 4] dcd1182:
so can you please expand on exactly what makes this procedure a "heart ache" as compared to precisely the identical procedure that users had to follow to install custom rom/recovery on previous MDL?
[T-Mobile Samsung Galaxy S 4] lgkahn:
what the heck are you talking about I am running mdl and I HAVE a custom recovery philz. and I don't have to flash it everytime I want to boot into it.
[T-Mobile Samsung Galaxy S 4] mgbotoe:
"I booted into the os and I got a notification about an app trying to get unauthorized access"

That :P . I don't want to see, do not want to look at it, and surely do not want samsung blocking something I am trying to do. You get that message, 95% of the time that means the blocked w.e was trying to access your device without being authorized. Think of it as an anti virus.

All matter of perspective:P
[T-Mobile Samsung Galaxy S 4] lgkahn:
I'd wait longer both roms out so far still show selinux set to enforcing on boot up.. so don't think know is completely removed in those yet.. In my mdl selinux shows permissive is status.
[T-Mobile Samsung Galaxy S 4] mgbotoe:
Ya I am not sure what he is talking about either. What he is considering as a normal behavior, I never encounter....and I got the GS4 in its immature days, where a stable recovery was still being made.

Lol, matter of perspective?
[T-Mobile Samsung Galaxy S 4] dcd1182:
dude, you asserted that knox is preventing certain recovery/rom from being installed.

that is dead wrong but fueling a fire of rumor in these jf forums.

you the user failed to follow the same directions you clearly followed on MDL to disable this behavior, which has absolutely nothing to do with knox or MK2, assumed that knox was to blame rather than your own error, and you still want to argue that no, samsung is preventing you from doing what you want to do!

you notice how the note3 has had knox since release and those guys arent running around saying their note3 can only run samsung roms? no, this craziness is only happenning in jf

---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------

so the "heart ache" for you to install a custom rom is the error message you got in the STOCK ROM after you failed?

LOL
[T-Mobile Samsung Galaxy S 4] mgbotoe:
You got it my friend. Since you know, I never fail :P
[T-Mobile Samsung Galaxy S 4] itzik_man:
Can someone explain this:

In Downloading screen:

Current binary: Samsung Official

System Status: Official

Knox Kernel Lock: 0x0

Knox warranty Void: 0x1

What does it all mean ?
[T-Mobile Samsung Galaxy S 4] mgbotoe:
I believe it means your warrantee is voided ,
[T-Mobile Samsung Galaxy S 4] lgkahn:
I didn't follow any special procedures on mdl to disable this behavior you are wrong. I am on stock mdl I rooted it myself and flashed recovery myself and debloated it myself, and do NOT loose recovery on every boot. The knox bootloader on MK2 DOES prevent running certain roms because you cannot go back to an older rom say 4.2.2 once you have the 4.3 knox bootloader. I never said it lets you only run Samsung roms, I said it prevents you from running CERTAIN roms.

The true fact is that mdl had a knox bootloader but it was set to non enforcing.. The new MK2 also has a knox bootloader but it is set to ENFORCING thus the issues. You cannot reasoneably say the MK2 is exactly like MDL because it isn't!!!

Samsung should have a way just to configure knox off completely and not restrict us at all .. But no... they know better what we need!!!

Also I have not flashed MK2 and am just warning people to be cautious and not jump at the first opportunity to flash to everything shakes out. I am not misleading anyone at all.

I also have know on my note but again it is not enforcing and restricting me from flashing anything.. But the newer knox releases are different.
[T-Mobile Samsung Galaxy S 4] gdmlaz:
This those not have a not have a locked bootloader it was a big Confusion from one of the devs.... We are still able to flash a custom recovery like cwm and root like usual that's what I did..... However u will trip the Knox counter and void ur warranty...... If u don't care about it warranty like I didn't since I didn't have any u could go ahead and flash this
[T-Mobile Samsung Galaxy S 4] itzik_man:
Is there a way to reverse the Knox counter ?

The triangle away does not work on S4 M919V. Not that I care much about the warranty, just for personal knowledge...
[T-Mobile Samsung Galaxy S 4] gdmlaz:
Yea that's why I'm saying it will void your warranty at least for now...... But is deff not a locked bootloader like thought when this came out
[T-Mobile Samsung Galaxy S 4] itzik_man:
Is it reversible, if yes, how ?
[T-Mobile Samsung Galaxy S 4] Stangpwr71:
Worry about warrenty

I am trying to understand something here with all the concern about losing your warranty.

I know it is a apples to oranges comparison.

I previously had a samsung Exhibit 4g. I rooted and screwed up and removed some system files, i then unrooted it started a cascade effect of system shutdown and force closes, along with random reboots and dropped calls.

I called samsung to se how much to flash the stock firmware so i can start from scratch, I explained the problem told them a special needs person rooted it and deleted too much stuff. they said the re-flash was free if i pay shipping to them.

they got it re-flashed the firmware, and then proceeded to tell me the main pcb boards was bad along with the microphone. i asked how much and they said since i sent it in a few weeks before my 1 year warranty was void. they said free.

I was amazed but they said if it is a hardware issue they will still honor the warranty, Again i said it was fine before i screwed with it and they said maybe maybe not.

Did they completely change there warranty process or am i just that sweet a talker on the phone?
[T-Mobile Samsung Galaxy S 4] egren58:
What if you trip your knox. If you were to reverse to 4.2 bootloader wouldnt knox be gone?..
[T-Mobile Samsung Galaxy S 4] tbhall77:
I have not tried this, but according to helake_az there is a way to reset the knox flag. http://xdaforums.com/showthread.php?t=2546016
[T-Mobile Samsung Galaxy S 4] RiverCity.45:
I am really skeptical that merely reverting to 4.2.2 gets Knox back to 0x0. I have repeatedly read that the opposite is true: that reverting leaves you at 0x1. I need hard proof before I believe this assertion.

For those of you confident in this method, please give it a try and report the results. That would be very helpful.
[T-Mobile Samsung Galaxy S 4] egren58:
I wouldnt doubt this will work.
[T-Mobile Samsung Galaxy S 4] richardmkovach:
It doesn't look like he's is reverting to 4.2.2 just reflashing MK2 through odin, unless I am missing something. I am skeptical as well, would love to see it tested and confirmed though.
[T-Mobile Samsung Galaxy S 4] RiverCity.45:
You're right. I got distracted by one of the posts in that thread. I still am skeptical that this method keeps 4.3 and resets Knox to 0x0. :silly:
[T-Mobile Samsung Galaxy S 4] Hoggles:
As far as I know...once the KNOX flag is tripped 0x1... There is no way of reseting it to 0x0.

You guys who don't know should check out DJ's thread in the International forums. That is the KNOX info capital of the world.... ;)

http://xdaforums.com/showthread.php?t=2250824

and the KNOX Q&A section...

http://xdaforums.com/showthread.php?t=2470635

If I could throw in my 2 cents.... There really is no need to mess with KNOX... You can have any 4.3 ROM you want, KNOX free, as long as you flash the GSM Modem from yesterdays release and flash any of the many 4.3 KNOX free ROM's out there. Simple. Clean. 100% working 4.3 ROM's from the International forum.

The absolute ONLY reason I can see somebody needing to flash the stock Tmo 4.3 firmware, is if you absolutely must have WiFi calling & 4.3... and can't wait for a Tmo dev to strip it of KNOX, just like what was done in the 9505 forums.

Just a tiny, itty bitty bit of patience and you'll never have to worry about KNOX or voiding your warranty.

Of course...in a few months(for most of us)...tripping the KNOX flag won't matter....as Sammy's limited warranty is only for a year. Then...who cares if it's tripped :highfive:

If any of you are looking for the winning combo... I'm running GoldenEye version "14" 4.3 MK9 w/KT's TW Tmo 4.3 kernel.

It's perfect. Not a single bug. 12900+ on Quadrant...no OC.

Cheers

---------- Post added at 03:37 PM ---------- Previous post was at 03:35 PM ----------

NO
[T-Mobile Samsung Galaxy S 4] Tunasty:
Hopefully y'all don't brick your phone in trying different things. Just make sure y'all read and search before doing anything.

S4 is poppin!
[T-Mobile Samsung Galaxy S 4] egren58:
i agree im running 4.3 rom perfectly fine AND HAVE NO ISSUES AT ALL with ktonezkernal. im glad i dint jump straigh to odin the ota now i dont have to worry about it. :cyclops:
[T-Mobile Samsung Galaxy S 4] dcd1182:
im tired of arguing and im fine with you believing that evil samsung locked you down, just stop repeating that nonsense here.

i can install 4.2.2 or any rom i want, have you actually tried or are you just repeating what you read somebody else repeating? why does everything work fine for me??

how was i able to correctly take a wild guess that the stock rom was overwriting your recovery without ever running the stock rom? could it possibly because of the thousands of documented instances of that occurring on other roms here???? could it be from my own working around that on a samsung intercept in 2011? no no, knox did it!
[T-Mobile Samsung Galaxy S 4] jason4962:
How do one person get bootloader locked by upgrading to 4.3? Is it if you upgrade via ota your locked and if you flash with twrp you wont be locked? or is it built into the rom where when you flash a 4.3 rom you are locked. I havent done anything yet ans im waiting to see about this 4.3 bootloader lock
[T-Mobile Samsung Galaxy S 4] Skipjacks:
The flashable versions have the bootloaded removed by a developer. The ota version doesnt give ypu that option.

Sent from your phone. You should be more careful where you leave that thing.
[T-Mobile Samsung Galaxy S 4] gypsy214:
Voiding the samsung warranty with knox but we need to find out if tmobile will also be checking into this... I have jnsurance and sometimes in the past I had sent them a rooted phone for a warranty exchanged. They have never said a word about it. So since a lot of us will be dealing with carrier instead of samsung. I wonder if carriers will take this to know if you're void or not
[T-Mobile Samsung Galaxy S 4] xmanbob:
4.3 root victim Void Warranty? help!

I did this root after a 4.3 update, and now I am sick. I was wondering what I can do now that my warranty is probably voided?

It was my fault. I have an APP that would only run on a rooted device. Now I have this BRICK.

If there is a GEEK that can walk me through getting this thing to be a phone for thanksgiving, please contact me.

I read the thread and POSTED this request because I am new to rooting, and it's too complicated.
[T-Mobile Samsung Galaxy S 4] flarbear:
FWIW, I'm totally 100% stock and unrooted since I got the device directly from a T-Mobile store. After I took this OTA I also got a "some app is trying to get unauthorized access" notification so this may not be related to your rooting efforts.

It happened right after I tried to run a game from a major developer (unlikely to have malware) that locked up on startup. I home-keyed out of the game, saw the notice, it told me it wanted to update "the Samsung security definition somethings", I clicked "continue" to update, the update was successful, and I was then able to run the game with no hitches.

I'm guessing they shipped their security software with a very limited set of overly restrictive security rules and are relying on a dynamic download to install the ones that do their job right. I don't know if this was related to Knox or not, but it probably was. If that is the case, then the reason they may ship it with a dummy set of security policies could be that they want to give an employer/management organization the option to install their own first and they only download the standard policies if no custom policies were installed...?
[T-Mobile Samsung Galaxy S 4] driodman98:
So let me get this straight. Tripping the Knox flag is the equivalent of popping your phones cherry? So you can never get it back? :crying:
[T-Mobile Samsung Galaxy S 4] jcbofkc:
There is no reason to trip it. Read all of jovys thread in development. Add the modem via odin and flash his rom that has the knox and the new bootloader removed.
[T-Mobile Samsung Galaxy S 4] omnifarious:
http://xdaforums.com/showthread.php?t=2532714

My rom also has KNOX/bootloader removed. Odexed for now, but deodexed is coming soon. Last apk is being optimized as we speak and then I deodex. =]

Aroma coming soon.
[T-Mobile Samsung Galaxy S 4] driodman98:
I'm actually looking for an all in one solution for this in one rom.
[T-Mobile Samsung Galaxy S 4] Hoggles:
Please tell us a little more about what is going on.

Is your S4 totally bricked? Does anything come up on the screen after a battery pull and power on?

Please provide a bit more detail, as your post is confusing. Are you bricked or did you just trip the KNOX flag?
[T-Mobile Samsung Galaxy S 4] Shortbus-Driver:
Im hoping my replacement which should be delivered in the morning since its turkey day today is 4.2......keeping my fingers crossed.

If its shipped with 4.3 already on it,is there a cure?
[T-Mobile Samsung Galaxy S 4] jcbofkc:
You will be waiting forever. Custom roms do not have the modem. You must use odin to update the modem.
[T-Mobile Samsung Galaxy S 4] elesbb:
Not true, currently working on including the modem in my ROM zip.
[T-Mobile Samsung Galaxy S 4] Shortbus-Driver:
A 4.3 WarpDrive? :)
[T-Mobile Samsung Galaxy S 4] jcbofkc:
Very nice! But that is not typical, is it?
[T-Mobile Samsung Galaxy S 4] elesbb:
Yep :) prolly already have a beta released today if I wasn't being stupid yesterday. Numerous issues. Ugh xD now I'm not sure when I'll have it done. Got a 2000 word paper to write and a group project and a written in class final due in the next coming up week. -.- plus work. So hopefully I'll have time to work on it. Got native tethering working, got hold menu to kill working. And double click home button. Whole bunch of other features to add yet too ha.

Btw happy Thanksgiving everyone!

---------- Post added at 09:36 PM ---------- Previous post was at 08:57 PM ----------

What do you mean by typical? It's all a matter of what you wanna do in the install script.
[T-Mobile Samsung Galaxy S 4] j_r0dd:
I would never flash a rom that contained a modem/radio. The modem only ever needs to be flashed 1 time. Not every time the rom gets flashed. Not trying to sound like a d!Ck. Just trying to save you getting blamed for potential bricks if something goes wrong.

To those complaining about not being able to use a custom recovery, there is a script that executes on boot in almost every stock android rom. This must be removed because when the phone boots up it will over-write the custom recovery. It's /system/etc/install-recovery.sh and this needs to be removed.
[T-Mobile Samsung Galaxy S 4] tygerchylde:
My phone is rooted stock 4.2.2 with Xposed framework and a few modules. The phone runs the way I want it to, looks the way I want it to (via Xposed modules), and I don't have enough apps that I keep on my phone to worry about running out of space. 32 gig SD card, everything caches to SD.

Tldr: I have my phone the way I want it. Why do I need to update?
[T-Mobile Samsung Galaxy S 4] elesbb:
If anyone bricks their device from flashing a file its their own fault. Obviously i will state that i include a radio so only flash on M919 devices...

And secondly, i can check what radio version is currently on the device before telling it to flash anything.

Its install-recovery.sh found under etc directory.
[T-Mobile Samsung Galaxy S 4] driodman98:
Given the level of customization these roms have this could easily be set to either check for the radio or make it an optional thing to select during the install.
[T-Mobile Samsung Galaxy S 4] Guatiao:
So I guess I got a bit unlucky with the 4.3 update today. My phone basically almost updated by itself when I was using it earlier today and clicked on the Play Store icon. I had been postponing the update for the last few days, and today upon opening the Play Store, it just went into reboot/ download/ install method. The update itself went fine, I DO have 4.3 AND know (I did not install the app itself), and have been seeing the security notifications others have talked about here.

I am positive, completely sure I did NOT choose to update. As I mentioned, opening the Play Store was the last thing I did before the phone automatically did the upgrade.Maybe the update had some timer or counter that did not allow for a perennial delay or postponing of the upgrade.

Yeah, go me, and hooray for 4.3 and Knox...
[T-Mobile Samsung Galaxy S 4] gaww:
If you get it all working with the radio, if a different ROM is flashed latter without a radio, should it work ok or will it be marched to a particular ROM only (yours) ?
[T-Mobile Samsung Galaxy S 4] elesbb:
Once a radio is flashed its there forever, i might actually include it as a separate zip for users.
[T-Mobile Samsung Galaxy S 4] iJuleguy:
Hopefully we can find a way around this too. I had mine unlocked from the day I bought it. My partner however, stayed on TW rom till it OTA'd to 4.3....
[T-Mobile Samsung Galaxy S 4] xdapowerapps:
I'm the same as you. I have absolutely 0 problems with my 4.2.2 debloated and Xposed modules. No need to upgrade. The 4.3 update is so insignificant that the hassle isn't worth it. I've tried other 4.3+ roms but came back to 4.2.2. Nothing Xposed and a little kernel tweaking won't do ;)
[T-Mobile Samsung Galaxy S 4] gruuvin:
Had you already downloaded the update and were postponing the install of it? Or had you not downloaded it and it even downloaded the update without your consent? I wonder how the rest of us might avoid this.
[T-Mobile Samsung Galaxy S 4] gaww:
That would be great, but will also be interested in tryung the ROM.

Will this then be a de-knoxed fully functional radio that is no longer tied to the locked bootloader.?
[T-Mobile Samsung Galaxy S 4] Guatiao:
I already had downloaded the update, but postponed it believing I could so until I, not my phone or carrier, decided to install it. It seems there was a limit of times or days I could do so.

The update itself went well and the phone is working properly BTW.
[T-Mobile Samsung Galaxy S 4] southsidexz:
Upgraded to 4.3 with Knox -_-

I apologize if this has been asked before, I kept going through threads but really couldn't find a direct answer.

So my "smart" brain decided to flash via ODIN the Official T-Mobile 4.3 image. I suddenly found out it wasn't the smartest way due to Knox appearing left and right with notifications.

Luckily I was able to root again with the CF-Root method and I was able to get a recovery. Also thanks to SuperSU it worked fine with Knox and I was able to get root and have it disable Knox. However I soon discovered that certain root apps didn't work properly anymore. Example: "SystemApp Remover", "Rooted AnyConnect", "Multi Window Manager", Titanium Backup, & WiFi Tether. However, Root Explorer, Terminal Emulator, Xposed Installer worked fine with root access.

I am wondering if this is due to the SELinux being set to Enforce (SEPF_SGH-M919_4.3_0010) or Knox.

My main question is since I got the official 4.3 is it possible to flash any of the 4.3 Roms with Knox removed and SELinux set to permissive without having to change the MK2 bootloader or do anything else? I really don't care about tripping Knox, I had sent this phone for repair at Samsung and they returned it, the only thing not working was the Micro SD Slot, which I fixed it. (Samsung didn't bother even calling or anything, same day received, same day they shipped it back).

Hopefully someone could help answering my question.

Thanks.:good:
[T-Mobile Samsung Galaxy S 4] southsidexz:
Success

I answered my own question :D

I flashed jovy23 Stock Modified ROM and flashed KT Kernel (Thanks jovy23 & ktoonsez) and now it works perfectly. I got calling going, wi-fi calling, wi-fi to work. No other issue.

Sweet! Now I have full Permissive SELinux and no KNOX to bug me, even though KNOX bootloader has been tripped, doesn't matter.
[T-Mobile Samsung Galaxy S 4] ashwinmudigonda:
Alright guys, I need your help. I have the M919UVUEMK2 baseband version running 4.3 on a SGH-M919 model.

I followed this link - http://true-android.blogspot.com/201...xy-s4-sgh.html - and was able to achieve root. I confirmed it with a couple of apps.

Next I tried to install clockwork mod recovery using ROM Manager. After it flashed, and when I booted into recovery, I got a message saying that root privileges have been lost. Fix? I chose yes. After rebooting, when I launched SU app, it said that there was no su binaries installed and that I should manually root again.

What is happening? What do I do if I want to flash a new ROM?

Update: I redid the rooting procedure. Odin showed PASS, but there was no Su app in the apps list. I am unable to obtain root privileges for any of the apps. I am able to get to CWM. Would it help if I flashed this ROM (http://xdaforums.com/showthread.php?t=2532714)?

Could someone please help?
[T-Mobile Samsung Galaxy S 4] ermmanuel:
I rooted using cf-autoroot by chaimfire and it worked perfectly no problems.
[T-Mobile Samsung Galaxy S 4] ashwinmudigonda:
I ended up flashing the SU zip and that worked.
[T-Mobile Samsung Galaxy S 4] ermmanuel:
I'm still wondering if I can flash any cm ROMs though ..jump the boat too quick on that update ×D
[T-Mobile Samsung Galaxy S 4] Tunasty:
Yes you can

S4 is poppin!
[T-Mobile Samsung Galaxy S 4] ermmanuel:
I though since the bootloaders were lock on 4.3 which I updated ...that it could brick the phone ..I'm new to lock bootloaders lol
[T-Mobile Samsung Galaxy S 4] rkrasny:
I'm pretty certain you can load a custom recovery (which you have) and a new ROM but your KNOX counter will trip. In fact, it should have already tripped with the custom recovery - when you boot do you get the yellow triangle and something to the effect that "your device has been modified..."

If so, that is the KNOX counter and that is the big deal with the MK2/locked bootloader - it technically voids your warranty and nobody is certain if Samsung/your carrier will provide you technical support or a replacement device under those circumstances. I'm pretty sure you're already in that situation though so a custom ROM load should not be a problem. You can always ODIN back to MK2 stock (but as always, no guarantees, your mileage may vary and you could own an expensive paperweight).