wah... that Mssg and all UI at Kit-Kat

I'm getting used s4.. Can any present s4 users here tell me the easiest way to differentiate the original and clone s4? Kinda worried since the fake s4 is flooded in d market..

may i know how to check the imei..

if the box matches the imei in the phone. that means the phone is original? in other words clone samsung s4 imei is diffrent from the box?

nani? your's SELINUX status still at Enforcing arh

waseh... now i still at jungle park liao
haha... anyway.. i'll flash and TA it to Stock 1st then update the shit...

No..last time when I root the phone..it still permissive.
Unfortunately I got problem till it bricked the phone.
Went to service centre and they reflash back to full stock BMG5 firmware. Still not root the phone till now..lolz

And i just receive notification ask me to update the firmware.

Maybe you can put on first page.
Warning..DMH6 update will change the SELinux status..!!
Those who don't want to have enforcing status better not do an update.

Android’s initial SELinux implementation is launching in permissive mode - rather than the non-functional disabled mode or the most stringent enforcing mode - to act as a reference and facilitate testing and development.

Android strongly encourages OEMs to test their SELinux implementations thoroughly. As manufacturers implement SELinux, they should initially release their own policies in permissive mode. If possible, apply the new policy to devices of employees first as a test.

Once applied, make sure SELinux is running in the correct mode on the device by issuing the command:
getenforce

This will print the SELinux mode: either Disabled, Enforcing, or Permissive. If permissive, you are compliant. Enforcing is explicitly not compliant in Android 4.3. (Because of its risk, enforcing mode comes with a much heavier testing burden.)

By default, we will be shipping with SELinux capabilities enabled in the kernel, but in a Permissive mode. What this means is that your phone will behave exactly as it currently does, with no noticeable change to the user.

There are 3 modes in total, Enforcing, Permissive and Disabled. While in Enforcing mode, SELinux policies are enforced, preventing whatever causes a violation (ie su). Permissive mode logs policy violations, but does not prevent the activity that caused it. Disabled turns SELinux off.

We are using Permissive mode as our default so we can come up with sensible policies. If you submit a log for us to analyze (via JIRA) for SELinux policy improvements, the logged exceptions will be of high value.

This will be an ongoing process as we work to incorporate sensible policies for each device repo. As always our source is available on Github and patches will be peer reviewed via gerrit. For those more attuned to personal data security, you are welcome to watch and audit our efforts. For the rest of you, sit back and relax – no need for pitchforks.

yeap.. is useful info... will be add on later

damn it....

S4 Security Policy Update

<insert die hard S4 user>
ahodil,waveweaver,fkinmeng,edwincodec

oh so that's what enforcing means, well for me i just wanna stay stock anyway.

Conclusions and Facts about KNOX-enabled firmwares

Not possible to downgrade to KNOX-disabled firmwares/bootloaders (An attempt sets 0x1) (even though some people state, downgrade is possible when omitting the bootloader file in a firmware package: see http://forum.xda-developers.com/show....php?t=2444671, not confirmed)
Even if you flash a KNOX-enabled firmware via odin (e.g. the latest fw) knox will be set to 0x1
Flashing unsigned or modified images via odin will set knox to 0x1
Samsung stated, resetting the flag is impossible
KNOX is mandatory and can not be completely removed
Warranty Void is no counter, it is a flag (0,1) it was never seen 0x2 or so
Mirroring all partitions from a clean 0x0-Device to a 0x1-Device via JTAG produces an unfunctional device (reversible by restoring the 0x1 partitions on the phone)
KNOX bootloader verifies signatures of kernels and recoveries. No custom ones possible without voiding the knox warranty

My Knox warranty flag now is 0x30..!! :
Even after reflashing at service centre cannot teset that flag.
In fact the flag increase after service centre technician flash back full stock firmware.

ahodil  what is your flag count now..?

you can check by going into download mode.

Ehh..!!?
Enter download mode
- three button combo (vol down + home + power button)
- then vol up

Exit from download mode
- long press power button

Press vol up to continue. ..lolz 

wulalala...
need next week get back my phone for checking flags
during my GF used it for photography..
sien... all of them's SELINUX status on Enforcing..
haizzz

This Saturday I gonna root the phone again then manually flash the latest DMH firmware...see if the SELinux status change or not.

Btw..your phone have enforcing status while come out from box or after firmware update. ??