yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] JoeyLe:
But still, why is it possible to bypass Knox on the Note 3 and not on the S4? http://www.sammobile.com/2013/10/14...-released-doesnt-affect-knox-security-status/
[Galaxy S 4 General] Michal Z.:
Tripping or not tripping this flag... I don't really care about it. The thing is that even if you could root it without tripping knox to 0x1, you will still have SELinux on your phone and this bootloader's code will still be there. What I would like to do is to completely remove this mess from MY device. I don't want to have any code on my phone that nobody (not counting samsung here) knows what it does. And Samsung claims that it's not possible, they can't downgrade your system :|

It's irritating that they keep telling that it's for safety etc. I don't believe it. It sould be like cryptography algorithms. I mean everybody can see the source of RSA for example, algorithm is not a secret but it's still safe. If samsung must hide something that means for me that it's not safe. I think that samsung can't tell us what really happens under the hoods because they are afraid that someone could take advantage of this and break it. So saying that it's for safety of my data does not convince me at all...
[Galaxy S 4 General] meatmeat:
Samsung is selling to much phones

Enviado do meu GT-N7105 através de Tapatalk
[Galaxy S 4 General] Orange213:
That's true, but after that knox thingy they lost as a customer.
[Galaxy S 4 General] rgshah3:
I guess using JTAG resets the knox counter
[Galaxy S 4 General] Absolon:
Thank you those who don't think I'm totally crazy! It warms my heart reading that :)

I will prepare a list of questions to be sent to Samsung. Lets all send it!

They will be the questions we DEMAND answers on. The more that send that the better.

If they can have a pre-fab mail, so can we. Just need to do that insane, last minute shopping today.

I will make a list of questions and provide the link where that little popup they call contact is.

The more we are that send that the more they see that we are not one crazy Swede but more that demands answers on what they have messed up

on our phones.

But as always, it's up to you to whine about warranty or see the big picture not having an iNdroid in a few years. Because that will be the case.

If they succeed, other will follow and we can just say bye to this platform we all love. The choice to act if yours. I've done mine. I do not accept this.

The people here, the ones that has messed me, thank you!

And for the ones that think I wear a folio hat and are seeing an conspiracy, Well, keep thinking that, cause I don't care what you think.

After being "in contact" or ignored because it's uncomfortable for them to answer, makes it even stronger to think that you don't invest this to prevent

"Triangle away". I had my own company. Investments should return value, else it's charity. Here I don't believe it's the case of caring about users.

If that is so hard to understand, just skip it, but I'm guessing that the "blog post" would never happen if people didn't ask.

And for you that never worked in a group on the net. I did one thing that went viral once, a complaint. The governmental branch that is looking out that

companies doesn't break against the EU Article 29 are in all EU countries with their implementation of the law and that law is STRONG.

The right for privacy is central. And that is one of the many issues that I question.

But I will prepare it when I have just have some time because I want it to be crystal clear what answers we need, ok?

All the best,

Absie

---------- Post added at 11:15 AM ---------- Previous post was at 11:12 AM ----------

That is one of the questions I will bring up. I have that as well. Got better after I did an Odin because they attached code to the Knox that is

making your phone unusable.

But even after Odin, I see it's not as before.

/Abs

--

Just want to say that "Permissions Denied" (https://play.google.com/store/apps/details?id=com.stericson.permissions.donate)

is a nice program to keep the way too much permissions to apps. Especially when it comes to the use of camera, internet etc.

Just take one and look on the programs and decide like "Why do my filemanager want to use my camera?" etc.

Very handy. Rooot needed.
[Galaxy S 4 General] AndreiSGS2:
Ok so i took an hour and read 20 pages..i dont care about the warranty since i got insurance..im on stock4.3 i f****** hate it..if i go and root it and install another rom..other custom 4.3 or 4.4 beside my warranty void what can happen..??other issues??
[Galaxy S 4 General] jonboyuk:
It's better if you don't ask the same question repeatedly in a thread as that's a violation of the XDA rules.

Anyway, Samsung left a flaw in the bootloader which allowed root. In the MJ7+ bootloaders they patched it and the Note 3 can no longer have root without triggering KNOX.
[Galaxy S 4 General] JoeyLe:
I see, so the chance that root will be achieved without triggering Knox in the near future is very small?
[Galaxy S 4 General] jonboyuk:
I think that is the question that thousands of people are asking!

DesignGears has done some great work in making it happen to the older bootloader. There's something called SafeStrap over at rootzwiki, but I'm not sure if it's of any help...

I want it as much as the next rooter, but I can't help but feel that the only solution will be for those who haven't already tripped KNOX. I've only had it a month and I'm gagging to root it....but warranty 'n all. :(
[Galaxy S 4 General] Absolon:
On Note 3 they had a bug in their secretive SELinux rules (the one they can hide processes etc).

It was fixed by "Rules update #16".

So no it's not perfect, far from.

/Abs
[Galaxy S 4 General] DobaKung:
The Galaxy S4 is fun to flash custom ROMs! Why Samsung did this!!! :crying:
[Galaxy S 4 General] maanz "L":
When [MENTION=2348906]designgears[/MENTION] successfully rooted the old bootloader, Samsung fix the "hole" in their new firmwares (i.e MJ7) through SELinux rules update #16, as Absolon mentioned.

Submitted by Peng Ning (VP, Enterprise Security Group)

Here is the original artical: https://www.samsungknox.com/en/blog/about-root-de-la-vega

Like I said in my previous post, the

Spies are here on the lookout for any major "flaws" in their newest firmwares.

And they will do every possible way to prevent devs from "breaking their codings" for their next firmware release.

Beware guys (devs)......

In the next Galaxy S and Note Series (probably S5 or Note 4 onwards), Samsung will face a major upset in it's sales worldwide because consumers will be looking at other brands like HTC or Sony as they find that Samsung has become a dull device and it's not up to the consumer NEEDS, especially to us and devs on this forums (there are millions of members here, think about it..).

If the situation doesn't change otherwise, I will be looking at LG G3 or Xperia Z2 or even the HTC TWO (probably if they made it) in the next year or so..

---------- Post added at 08:26 PM ---------- Previous post was at 08:17 PM ----------

because Samsung don't allow "their" device to get rooted/hacked (this is what they thought, "theirs" not "ours")...

So, do u think u wanna get the next Galaxy line series??
[Galaxy S 4 General] DobaKung:
I don't like the way they did. But after my warranty gets void as it expires, I'll start flashing the ROMs! :D
[Galaxy S 4 General] bungadudu:
By then we'll all switch to something better and more user-oriented devices.

I really dig project ara.

Open hardware, open software.

Go Moto!

Phuck Shamesung!

(and I really wanted the s5..)

Guess this is the beginning of the end..
[Galaxy S 4 General] Orange213:
Well Samsung are on the top right now and they think they can do anything, but this will backfire at some point for sure. After all we all buy these phones to customize and this is pretty much a **** move by Samsung....
[Galaxy S 4 General] jasons1004:
m919 ROOT does NOT trip knox

i posted this a while ago..cant find it to put link

in case some havent found about this yet.

just follow instructions in video bc its chinese

https://www.youtube.com/watch?v=UE5K8B2mTV0

works on m919 stock after ota MK2 update...

and t-mobile note 3 stock after latest OTA
[Galaxy S 4 General] Hagster:
This metod is vRoot.I Dont Know, why he collect imei? For S4 clone?
[Galaxy S 4 General] Brooklynsour:
http://xdaforums.com/showthread.php?t=2581758

would I able to reset Knox count and unlock boot if id need repairs within 30 days?

Rooted mf3 SHOstock
[Galaxy S 4 General] borillion_star:
Personally as the owner of my phone ( bought it full price outright ) this pisses me off, what right do they have to modify the hardware of the phone? I wasn't warned about it in a EULA or anything. Complete asshattery on Samsung's part. They are so arrogant. I had to have a lawyer threaten them to fix my phone under their own warranty before.
[Galaxy S 4 General] frostmore:
Samdung is trying an apple stun here...ala here's steve job telling you how to hold a iphone 4 properly to get better reception.

no one appreciates having some dumbnut telling us how to use our phones.knox,an enterprise solution is something none of us wants.if we want it,we will choose to install it.if we dun want it,we wun install it.simple as that.

telling us it a security solution for the masses????

samdung might as well say pray for unicorns to rain S5 from its behind.

samdung lost a long time customer of their phone and i sure as hell will start spreading the news about knox pox and how insecure it is for the ppl if they do not provide a removal toll for this crap called knox!
[Galaxy S 4 General] SeaFargo:
In my experience, I've never had any issue from my fragged knox 0x1.

I've installed all stock TW 4.2.2 (before) and now TW 4.3, than installed Cynogenmod 10.2 (also 4.3) but I love MIUI so now I'm back on MIUI AOSP based version (4.2.2).

I'm on bootloader version I9505XXUEMJ7, and baseband also I9505XXUEMJ7. Many users have wi-fi problems because of baseband-firmware compatibility issue.

Of course I can not use Knox based app anymore (never been interested on it).

I also have a 3.4.66-ChronicKernel installed, and it works perfectly. I use the TWRP 2.6 - Samsung Galaxy S4 (i9505).
[Galaxy S 4 General] arleybarros:
Thank you! WiFi never worked again. Even if i restore back to stock. My phone is availiable for any kind of test.
[Galaxy S 4 General] Irwenzhao:
Somebody should just trip all Knox in all phones to teach Samsung a lesson.

Smack that thanks button If I helped!

Always make a nandroid backup before trying anything risky.

I do respond to questions (most) via PM.

Sent from my fabulous N7105 powered by Illusion ROM and Plasma Kernel.

Sent from dat small country called Singapore.

P.S. Quote my post for replies ASAP.
[Galaxy S 4 General] Rockafilly:
warranty lost by recovery

i tried to update my note 3 with kies. unfortunatly this try failed and i had to use the recovery function. after the recovery was succsessfull i took a look to the download mode and saw that die knox counter was set to 0x1

thank you samsung!!!
[Galaxy S 4 General] oxfordmark:
SO, if you went from a network branded rom to a generic version. You couldnt change back to the network branded until it was the same version or newer?
[Galaxy S 4 General] KALI2000:
That's what I intend to do, but I've also read that when using odin, knox detects her use.
[Galaxy S 4 General] spinky360:
why this, how to do that when.. Etc

This are for FAQ page.

:thumbdown::thumbdown::thumbdown:

PLEAS LET IT BE A RESEARCH SECTION!!! THANK YOU

:thumbup::thumbup::thumbup:
[Galaxy S 4 General] s_vohra:
My two cents..

When on XDA.. stop worrying about warranty..

Earlier we had the upper hand..thanks to some awesome Devs.. who I am sure can come up with a solution..

For the time being Samsung has the upper hand.. and they are well within their right to not give warranty services on devices that have been tinkered with..

For absolute control on your Android.. go for Nexus
[Galaxy S 4 General] lozohcum:
Maybe finally some devs will focus on other devices. Not only SGS4. SGS3 etc. - only a very high-end devices.

I like Knox.
[Galaxy S 4 General] Obagleyfreer:
I get what you're saying, and agree to some extent. The thing is that installing custom software on a device can only mess up internals and/or software.

Samsung will refuse warranty on physical damage ie power button failing, sim tray breaking, USB port not working properly. These are all common, physical issues that Samsung phones have suffered from.

I don't think it's fair that Samsung can refuse warranty on a broken part (that they should of made properly) because we have installed custom software on our device.
[Galaxy S 4 General] malakagr:
Whats that? Can we edit it??
[Galaxy S 4 General] Beefheart:
Fair or not, it's never been a secret that rooting your phone or flashing non-stock firmware results in voided warranty. Why do you think applications like Triangle Away exist? The difference is that, before now, there has always been a way to get your phone back to factory state.

If you want a guaranteed warranty, this isn't the forum to be visiting.
[Galaxy S 4 General] joecool666:
okay witch forum do you suggest us to be visiting ?
[Galaxy S 4 General] liorbal:
do i have this knox on my I9500 phone?
[Galaxy S 4 General] kiran.savadatti:
MH8 stock to MI1 pre-rooted stock

[MENTION=4398524]DjeMBeY[/MENTION]

I have a stock MH8 with the secure bootloader with knox status 0x0.

If I flash your pre-rooted MI1 firmware, which has the latest bootloader as well, using Odin,

-would it increase the knox counter to 0x1

-would it change the binary status and other status in download mode to custom

-would the device status still remain official

-would the knox apks that are within the firmware alert of root access warnings and make the phone laggy or unstable

thanks in advance
[Galaxy S 4 General] 00raq00:
In HEXEditor in bootloader you can see

KNOX WARRANTY VOID: 0x%x (4b 4e 4f 58 20 57 41 52 52 41 4e 54 59 20 56 4f 49 44 3a 20 30 78 25 78)

, so my question is if is possible change

KNOX WARRANTY VOID: 0x%x

to

KNOX WARRANTY VOID: 0x0 (4b 4e 4f 58 20 57 41 52 52 41 4e 54 59 20 56 4f 49 44 3a 20 30 78 30 20)

or

KNOX WARRANTY VOID: 0x0 (4b 4e 4f 58 20 57 41 52 52 41 4e 54 59 20 56 4f 49 44 3a 20 30 78 30 00)

and next flash it ?
[Galaxy S 4 General] Beefheart:
http://www.pcadvisor.co.uk/forums/24/mobile-phone-help/ ;)

But, being serious for a minute, I suspect you're missing my point deliberately. XDA Devs is primarily about improving smartphones by means not approved by the manufacturer, or certainly in Samsung's case. Every modification on here, be them custom roms, non-stock recoveries or simple rooting methods, come with a disclaimer that your warranty will be void should you return the handset for repair with the modification on it. But, like I said in the previous post, that didn't really matter before now because you could nearly always return your handset to factory state with Triangle Away and a simple flash of the original firmware with Odin. However, with the suspected use of an e-fuse, Samsung has changed the rules of the game unfortunately and it's bad luck for the people who didn't realise this before an official update changed their bootloader.

No, because changing that would be no different than a DD copy of the bootloader partition from a non-knox phone (or a knox phone with the flag at 0x0) to one with the flag activated at 0x1. And this has been shown to result in a non-functioning phone until the original partition is copied back. This is why an e-fuse is suspected.

As far as I'm aware, yes it would, or certainly in the case of the 0x1 Knox flag. Because the phone being rooted would activate it.
[Galaxy S 4 General] miloytyn:
Actually that non-booting has nothing to do with the e-fuse, instead it indicates that secure boot is being used with the bootloader and any modifications to it causes hash fail during the secure boot and thus the phone will not boot.
[Galaxy S 4 General] ewok666:
That does not make it legal but for an individual it's hard to enforce that point. However, I bought the S4 because of Samsung's liberal take on flashing etc. If they now choose to not honor warranty on clearly physical issues then I'll be happy to buy another product next time. Fyi, my bootloader unlocked One X had a screen fault and HTC UK replaced the screen no questions asked. I'm happy for the warranty to be limited as that makes sense but they can't deny all warranty claims......well they can but then I'll have to move on ;)
[Galaxy S 4 General] yuriman1:
Oh God, I just rooted my S4 and now i have that 0x1 flag on knox :/

Will there be a way to reset it one day? What features am I missing now?
[Galaxy S 4 General] themissionimpossible:
This patching will affect only the value shown on the screen (%x), not the value itself internally stored, that will remain 1.
[Galaxy S 4 General] 00raq00:
Yeah I know but it'll look good :)
[Galaxy S 4 General] Shiryu:
Do we need anything more? ;)
[Galaxy S 4 General] UnknownEdition:
Exist a method to force and go back to a 4.2.2 firmware? So counter will be 0x0.
[Galaxy S 4 General] JoeyLe:
No.
[Galaxy S 4 General] arleybarros:
http://9to5google.com/2013/12/24/sa...o5Google+(9to5+Google+-+Beyond+Good+and+Evil)
[Galaxy S 4 General] paysen:
I just bought it because I was so satisfied with my Galaxy Nexus. But today I sold my Galaxy S4 and I will not buy any Samsung product again. Thanks for making the decision so easy for me, Samsung. Looking for a Nexus 5 / LG G2 now.
[Galaxy S 4 General] xclub_101:
Sorry if I am little blunt but this looks more like a long useless rant from a clueless guy that missed the incredibly obvious checkbox in Settings / Security = Auto update security.

On versions where the bootloader is not truly locked NOTHING can stop you from installing your custom recovery and custom kernel (with SELinux disabled if you want so) and custom ROM.
[Galaxy S 4 General] UnknownEdition:
I think the solution is forceing reset to 4.2.2, but how???
[Galaxy S 4 General] gazdajezda:
Great to get here to read about that knox ****... I really was tempted to buy a S4 after S2 get hardbricked last week, but now i can just show them a middle finger... ignorants...
[Galaxy S 4 General] Absolon:
You are 100% right Xblub!

I'm a totally clueless. Hey, I'm even

crazy

if you read the whole thread :)

I just sit here and rant rant rant because that is all I want to do and I really have nothing else to do like sitting and answering your really

insightful findings about me and I have no substance whatsoever in what I write. Actually I'm working at Samsung and are just trolling you all!

I'm so clueless that I even didn't KNEW about the totally uninformed and unknown platform "Knox" that was put into one update without any

information or warning!

Damn, n00b I am. Stoopid me.

/Abs, the "nobody AND CLUELESS crazy Swede" ;)
[Galaxy S 4 General] .NetRolller 3D:
A quick update with some actual (if early-stage) research: at least on the I9305, Knox definitely appears to be an EMMC RPMB field. I have yet to acquire bootloader images for the I9505.

I wonder if flashing/jtagging just tz.img or just sboot.bin (rather than both) from a pre-Knox firmware also causes a brick...
[Galaxy S 4 General] GravuTrad:
Knox security hole

http://www.latimes.com/business/tec...lnerability-security-20131224,0,2270518.story
[Galaxy S 4 General] .NetRolller 3D:
Suggested research direction:

-Determine how the RPMB authentication key is being generated. (RPMB uses a symmetric key, so to read/write RPMB fields, the bootloader must either contain the key in some form, or generate it from some device/chip serial number.)

-Implement RPMB reading/writing in an Android kernel. This functionality is present in the upstream Linux kernel, so it's a matter of porting.

At least on the I9305, it appears to be possible to get the bootloader to dump the RPMB key on what appears to be a serial line! If anyone knows how this serial line can be accessed (the one with the SBoot prompt), please investigate. (I still don't have I9505 or Note 3 bootloader images, so can't analyze those.)
[Galaxy S 4 General] bungadudu:
Tell us what you need.

Full system dumps before/after knox?

You guys who have an idea about this should organize on irc and talk/work together.
[Galaxy S 4 General] obrobrio2000:
In ODIN there is "bootloader" option. It's possible to remain on 4.3 stock but change the bootloader to 4.2.2?

I know, that's a stupid idea and I'm so noob...sorry in advance :C

PS: I've 0x1 warranty void.

Sorry for my poor english.
[Galaxy S 4 General] Michal Z.:
It will brick your device.
[Galaxy S 4 General] !crazy:
No it doesn't have to. He can use mobile Odin. If he removes bootloader and kernel it should be fine. It works like that on Note 3 at least. See no reason why it wouldn't with S4.

Edit

I'm sorry, I just read his post again, and now I see he actually wants to go backwards. I was stupid and thought he wants to stay on older version, without reading properly. Sorry about that.
[Galaxy S 4 General] yahyoh:
here's KNOX bootloader from MK9 rom for Note 2 , hope it helps :)
[Galaxy S 4 General] mikejones13:
OK finally got the devices from Samsung, but no instructions from them yet. Both devices are not activated. Both are from AT&T I got an S4 and Note 3 and both have knox activated already. If you guys want me to dump anything or pull anything let me know in pm just incase Samsung or my mdm developers are watching xda. I did find out I am flying to Toronto in mid Jan to the mdm hq and meet face to face with the knox developers. It's now time to play.
[Galaxy S 4 General] frostmore:
it would be nice if we can have an idea on how to remove knox.

i am not so much of a fan of resetting it.that would mean major security loophole to a really good enterprise idea.

rather,i'd prefer knox removal and unlocked bootloaders so that we can root the phone and install a superior custom recovery.

leave knox to the DoD and let them do whatever they want,jus leave us ordinary folks alone.
[Galaxy S 4 General] rgshah3:
Collect as much info as you can regarding removing knox! Cheers ?
[Galaxy S 4 General] Surge1223:
So I haven't read this thread and I assume what I'm posting below is already common knowledge. But just in case...

SECURE: SECURE MAGIC failure (recovery.img)
SECURE: SECURE MAGIC failure (boot.img)
SECURE magic check passed...
[TIMA trusted boot]: SEAndroid MAGIC failure (recovery.img)
RECOVERY IS NOT SEANDROID ENFORCING
[TIMA trusted boot]: SEAndroid MAGIC failure (boot.img)
KERNEL IS NOT SEANDROID ENFORCING
SEAndroid magic check passed...
SECURE: signature check fail. (recovery.img)
SECURE: signature check fail. (boot.img)
SECURE : Signature verification...
SECURE : Signature verification succeed
SECURE : Signature verification failed
SECURE CHECK FAIL : %s
SW REV. CHECK FAIL : fused : %d , Binary ::%d
KNOX KERNEL LOCK: 0x%x
KNOX WARRANTY VOID: 0x%x
[TIMA trusted boot]: SMC call to set the warranty violation fuse failed
[TIMA trusted boot]: SMC call to set the warranty violation fuse succeeded
[TIMA trusted boot]: Boot-time measurement successful
[TIMA trusted boot]: failed to obtain measurements %d ERROR: Cannot read ramdisk image
[TIMA boot measurement] : kernel secure check fail
[TIMA boot measurement] : Old/non-CL device - KNOX warranty void
kernel secure check fail.
Set Warranty Bit : %s
Secure check fail : %s
[Galaxy S 4 General] Absolon:
This feels secure...

http://online.wsj.com/news/articles/SB10001424052702304244904579276191788427198

How nice that we can USE our antivirus to avoid malicious code to protect us!

Wonder how Samsungs's own malicious code will compete for resources with external NSA code?

Oh, sorry Samsung's IS the NSA code. Russian then? ;)

/Abs
[Galaxy S 4 General] maanz "L":
Full article from WSJ

Israeli Researchers Point to Alleged Vulnerability in Galaxy S4

Samsung is "working very well" with the Pentagon and NSA...

Then Snowden says “the mission's already accomplished”.
[Galaxy S 4 General] .NetRolller 3D:
The Note II is too similar to the S3 to be useful at this point - I am primarily interested in S4 (i9505 and i9506) pre- and post-Knox bootloader and TZ images.