yashsingh1/xdaforums huggingface dataset:
[Galaxy S 4 General] rgbigel:
Please keep us up to date!

]Selfhate[ ---> I just ordered my I9506 1 hour ago, obviously before reading your post...

Can anyone confirm OTA update without being asked?

Maybe you should clarify what you did before things started to get weird. So you got an Update to V4.3 (coming from where? Rooted, KNOXtripped?) -- that's hard to believe. How can you get a leaked version to update without even being asked?!

Anyone who knows how to De-KNOX? -- What are the side effects? I don't give a damn for Warranty or any KNOX services, I want to own my phone.

In a later post you also mentioned you are using some warez. Are you really sure that they are not the culprit?

I heard about WiFi issues for the I9505 after using the wrong boot loader. Any news here for the I9506?

And please everybody join hands to make Samsung behave decently. It could well be illegal to do changes like this, at least in my country there is a law that prohibits unauthorized access to any IT component. If this is what's happening here, it's very close to terrorism,

Already pressed THANKS but here I go again! Thanks!
[Galaxy S 4 General] Absolon:
With that attitude if course they won't care. Do you think sitting at XDA will change something? At least TRY.

Dammit, how many times do I have to say to move you butts and start posting. One of you. Register in one forum. The other in the next. Spread it.

Tell people they destroys the phones, on purpose. They can install spyware. They can push out software.

The might have the ability you remove control your phone. No proof. Theories. Free world. DISPROVE ME SAMSUNG!

Let they disclose why it's so DAMN IMPORTANT??

WHY DO

YOU

need software that can hide processes, parts of storage, run own programs, chat with the net??

It's been in our phone from start. It's all there. WHY?

Don't give me security crap. If I work somewhere my company will give me a Note 3 with imitated leather with KNOX.

And I've worked with security and there is no KNOX in the world that can stop ANYTHING from leaking if someone would want that.

If NSA could not stop Snowden nor 300k documents leaking on a cd with the name "Celine Dion" on. Hell.

But it's splendid to know where you are! And what you say.

"In the "ol time" you put a mobile behind the curtain of the window on silence and called it. This is the same thing except you don't need to do that extra mile.

Ask yourself that WHY? And create friction. Because somehow we already managed to do that else they would have never disclosed this??

Are you on a contract with you cell provider? I am. As long as my contract goes it's not my cell. It's my providers. I will own it in 23 months.

But right now it's not mine. Do you think my provider was happy when I sent them this link where I explained what an e-fuse was?

Destroying hardware? THEIR hardware?

Uh oh....

Just simple things. When I called Samsung and they took my case # the tone changed. WHOHA. He almost threw the phone in my ear.

If ****ty little me, I AM NOTHING, can create so much irritation at Samsung in my country so can you. Mail if free? What parts to avoid? etc?

Use what they disclosed!

Use their OWN text!

https://www.samsungknox.com/en/blog/about-rooting-samsung-knox-enabled-devices-and-knox-warranty-void-bit

As final note, it is possible to damage the device if the system software is not written properly. For example, system software can potentially overwrite

the hardware configuration data stored in e-fuse and render the device completely irrecoverable.

What part? Where? Hardware error? So I can destroy HARDWARE with software??? Uh oh.

Where is it? I don't want to destroy my providers cell. Hardware errors are on warranty.

Need to call my provider! Warn them! A bug in Kies? Imagine?!

The only thing you have to do is:

1) CTRL-T -.> New windows

2) Get to a user forum. Register.

3) Confirm.

4) Post.

Don't know a user forum? Use google. Type in Android and you have 50!

Hell, let's make a prefab post?

Don't want to use your email? Get MaskMe. For FF and Chrome. Works splendid!

Don't resign. Don't accept. That is what they want. Get outside XDA!

Just do something!

/Abs that is happy that he created fuzz today. Wait until tomorrow ;)
[Galaxy S 4 General] MasterMerlin:
Thanks for your Input Absolon!

The I9506 is my first Samsung Smartphone, which I got with my new contract. (Have been HTC addicted from 2003). From what I see going on with KNOX it is clear for me that I will never own another Samsung Device and having learned from the past. Samsung ist just precisely doing the same mistake that HTC did before the One. It just starts getting to be a PITA to the community.

Epic fail Samsung. Never treat the community in being dumb!

1.) The community will show you otherwise!

2.) Without a neardish and well argumenting community you will soon se drop in sales.

3.) Let the user decide which quantum of freedom they want or they will get it elsewhere.

Yes Samsung is fu... us royally with KNOX and regarding to the articles from the past days, if they are really using an eFuse, I ask myself who allows Samsung to DESTROY a part of the Hardware I personally owned by paying money and use an open source based operating system for this?

I think the german "Verbraucherschutz" may have some interest in this issue too.
[Galaxy S 4 General] [opensys]:
I also subscribe that.

Samsung now It's on top, but this will not take forever, with this methods, it only lost customers.

Samsung forgets that is because Open Source software that he takes that place, now build crap like knox...

Please take more time to build better kernels, and better software, and release the all source code, not parts of it...

My next device will be a Nexus, Period.
[Galaxy S 4 General] Armazia:
Maybe I am a total noob, and this might sound stupid but;

Wouldn't there be a way to FAKE the 0x0 status? Instead of solving it, the first step could be to let the bootloader show a 0x0 state. I mean, if samsung does really want to know if the knox has been void, they can know it anyway(till now). But what if they don't check that deep.. would there be a way?
[Galaxy S 4 General] erkme73:
I don't have this model phone, but am following the discussions intently. I have the Note 2, and flashed the stock update to 4.3. I then rooted using CF's auto root, and flashed TWRP. Of course, I now sit with the Knox flagged.

But here's my question... If the previous bootloader didn't have Knox, and now the new secure one does, does that mean the eFuse theory still holds? I mean, wouldn't the imply that the eFuse has always been there (dormant) until they activated it with this new bootloader release? And if not, then the eFuse is software-based, which implies it could possibly be re-written (reset).
[Galaxy S 4 General] mahmoud007:
hello

im new in this site and i found it very helpful for me :good:

i've been interested in galaxy s4 posts recently because i have the same problem that im sure most of you have witch is KNOX

and i learned by bricking it so many times and fixing it by the official Firmware 4.3

it wont install any other official Firmware unless it has KNOX in there bootloader version

so if there is any way to trick it and making it believe that the new bootloader has KNOX while it doesn't .. in theory might work out

after all im new at Linux world so what do i know :silly: :eek:
[Galaxy S 4 General] [opensys]:
The boot loader may be the answer for that, and require reverse engineering on boot loader, to get the area that read knox, and do the way to pass over the knox read attribute flag. The problem is that knox also have a check sum for boot loader, so also require to put it right after that change, because bad bootloader = dead phone.
[Galaxy S 4 General] clonednull:
Dont want to disappoint you but this is not the first device using efuses on the european market. There are and have been a lot of them arround.

For example the Xbox360, it has allready used efuses for downgrade prevention and also to "cripple" the functions if it got manipulated.

So if you finished with samsung go ahead and sue microsoft but i'm afraid it will be a Don Quijote's fight againts windmills.. :silly:
[Galaxy S 4 General] TheEgonSpengler:
This because of the xbox service. No one dials your box up and makes it update, its update or stay off msonline. (which is this way to prevent cheating and force compatibility between units for equal gaming experience and predictability.)

I'm not using Samsung cell service. I should retain the right to downgrade upgrade and do as I please so long as I do not disrupt others.

I don't expect warranty for things I break but just because I have flashed something means nothing to on if my mods broke it. (especially physical issues)
[Galaxy S 4 General] ahoslc:
So I tripped knox and was wondering would that prevent me from going back to stock rom? Reason I ask is I can't seem to restore to stock image from odin keep complete write failed in odin and wondered if it was the knox that was causing it.
[Galaxy S 4 General] ranger4740:
If you have Knox you can only use 4.3 stock Roms, you cannot go back to older 4.2.2 with old boot loader, yet. Fingers crossed someone will crack it one day.
[Galaxy S 4 General] ahoslc:
So weird I can't even seem to restore stock mk2 without Odin failing. I am on a cm11 ROM with no voice or data restoring multiple Roms same issue.Something got very screwed up and at this point I'd be happy with 4.3 stock but can't even seem to get that.
[Galaxy S 4 General] Absolon:
I doubt it. I have Odin'ed my 'Knoxed device with stock-rom. As a matter of fact I have to do that, right now the 3rd time since Play and stuff stop working

after you had your phone going for a few days.

Have you checked that you Stock-package is ok? Contain all parts etc and what does Odin say?

/Abs

---------- Post added at 08:55 AM ---------- Previous post was at 08:43 AM ----------

You mean a Knox, not tripped? Do you mean that once you get into 4.3 you can't go back?

I think I went back and forth with the I9505 since some roms where 4.3 and some still 4.2.2 here (until I threw it in a wall twice and broke it in half).

But that must have been since I tripped Knox like the first thing I did since I was testing roms and couldn't decide what one I should stick with since

there where so many... all so nice... so I think I tripped Know like the same day it came out and since I did everything through the recovery I never saw

the flag until someone here started to wonder what this Knox was.

Besides since 4.3 has both SELinux and SEAndroid that REALLY virtualize you it's no way I'm going there with Samsungs versions.

It's like I want to give them MORE control over my phone. What they do to it is bad enough :P

Can someone check if you can't go back to 4.2.2 from 4.3 if you already got a blown, booby trapped device?

/Abs
[Galaxy S 4 General] LuigiBull23:
Once you've updated to 4.3 (KNOX-enabled bootloader) you can still flash ANY Android version of a ROM you desire. You just can't downgrade the bootloader. So in other words you can't downgrade your firmware. You can only jump between Android versions on a ROM to ROM basis.

There is this patch that some devs have implemented into their update zips in which reverts the end user's KNOX bootliader back to it's previous bootloader, even if the KNOX flag had already been tripped. That currently cannot be reset at this time but the idea behind the patch was to revert the bootloader to it's previous state to therefore remove KNOX entirely and gain back your warranty. This has only been accomplished on selected device models, such as the international and Sprint variants of the Note 2 but hopefully becomes more universal in time as this seems to be the only valid solution for those who have already suffered at the hands of KNOX and want to go back to doing whatever they wanted whist maintaining their warranty. The Galaxy S4 does not have such a patch yet AFAIK but I'm hoping Devs on these forums implement a similar patch soon, that is of course considering a solution to resetting the KNOX flag hasn't already been discovered by that time.
[Galaxy S 4 General] Michal Z.:
I'm pretty sure you can't. And I wouldn't ask anyone to try because it seems that it's easy to brick the device when you have knoxed bootloader and then try to flash the one without knox. Maybe you had this 4.2.2 with knox so you were able to flash it. But it seems that you can't downgrade to non-knoxed bootloader. Or maybe I'm wrong (I would like to be wrong here)...
[Galaxy S 4 General] BoonDawk:
reset flags

Everyone here blind? I've posted twice about resetting my counter.

The stock update blew my wifi and sound so I:

1. Used odin to flash stock 4.2.2 then rerooted my i337m using cwm manager unpaid ver from GP

2. Used paid version of triangle away and reset 0x1 and 0x30 to normal status.

Then updated to 4.3 without a problem.

I took my phone to koodo for warranty and it was covered. Iwas still rooted but the count was 0x0 so they fixed it. Got a new board.

Now No KNOX
[Galaxy S 4 General] tcntad:
TA doesnt reset Knox, it resets binary counter which increases due to flashing. Obviously you might know that already

Flash counter was 0, not knox. Wifi may not be broken by rooting/flashing. So therefore it was still under warranty.
[Galaxy S 4 General] BoonDawk:
uh huh

I'm sorry but isn't the whole point of them being able to tell if you have EVER flashed unofficial firmware so they can void warranty even if you go back to stock? And then there is this little post...

Quote:

Originally Posted by ahoslc View Post

***So I tripped knox and was wondering would that prevent me from going back to stock rom? Answer NO I went back to stock 4.2.2 Try a different version of odin

********Reason I ask is I can't seem to restore to stock image from odin keep complete write failed in odin and wondered if it was the knox that was causing it. I think this man would like Samsung to fix his phone. They fixed mine. After I used triangle away and my phone booted normal and I upgraded back to 4.3

**************If you have Knox you can only use 4.3 stock Roms, you cannot go back to older 4.2.2 with old boot loader, yet. Fingers crossed someone will crack it one day. I went back to 4.2.2 it still had KNOX but I was back to normal startups without the 0x1 and 0x30

Samsung sent me my phone with a new main board and 4.2.2 installed. I know that's not a solution to knox, but it got me my phone fixed. Or I could just have sat around with my thumb up my a** telling everyone knox hasn't been conquered yet there is no way to go back to stock 4.2.2

And then there is this

Default [RESEARCH] Samsung Knox: Warranty Void Behavior

As you may already know, the latest Samsung firmwares came with a new secured bootloader. You can recognize it in download mode easily. It states: Knox warranty void: 0x0 or 0x1.

As for now, there is no way to reset that flag from 0x1 to 0x0. <---I did with triangle away, If I didn't stupid Samsung would have just mailed me a brick and said thanks for you business
[Galaxy S 4 General] targsx:
Could this be applied to i9195 also? Anyone tried it?
[Galaxy S 4 General] RusherDude:
Well I just found this on the Note 3's KNOX thread:

http://xdaforums.com/showpost.php?p=48368021&postcount=432

Samsung confirming that e-fuse is involved, and talking about CF-root, Root de la vega, etc?? linking to XDA?? wtf?

If this was posted before I couldn't find it, sorry. But if this is true how is people getting around an e-fuse??
[Galaxy S 4 General] andyistic:
My Download info says:

ODIN MODE

PRODUCT NAME:SPH-L710

CUSTOM BINARY DOWNLOAD: Yes

CURRENT BINARY: Custom

SYSTEM STATUS: Custom

QUALCOMM SECUREBOOT: ENABLE

BOOTLOADER AP SWREV: 1

But I'm not using the International one, so I guess mine's not affected by Knox.

---------- Post added at 05:03 PM ---------- Previous post was at 04:47 PM ----------

So I checked my aboot.mbn from the 4.3 package.

No mention of Knox anywhere in that file.

---------- Post added at 05:11 PM ---------- Previous post was at 05:03 PM ----------

I don't think that's the reason.

I think it's because they're sick of people brick'ing their phone, then bringing it back into the store for a free (on warranty) replacement.

Their message is: If you're gonna take a risk and customize the phone, don't expect us to give you a new one for free.
[Galaxy S 4 General] dukhan:
a picture of your boot loader will be a proof.

Knox never ever trip to more than 1. How you could get your Knox to 0x30! it just trip to 0x1 not more.
[Galaxy S 4 General] rgshah3:
If there actually is an efuse, why didn't it get set off while we were on 4.2.2?
[Galaxy S 4 General] Absolon:
They armored/activated it in an update. Was there. Just waiting...
[Galaxy S 4 General] rgshah3:
One thing I don't understand is why do they have 'warranty bit' in the i9500 and 'knox warranty' in every other device?

There has to be some catch, else they would have the same download mode
[Galaxy S 4 General] yahyoh:
there is no e-fuse its big joke from Samsung :silly:

it can be reset within 10 minutes in Samsung service center :D

http://xdaforums.com/showthread.php?t=2504258
[Galaxy S 4 General] gazeddy:
Doesnt mean no efuse just means there is more than one
[Galaxy S 4 General] yahyoh:
On Exynos devices its called warranty bit for some weird reason (even on Note 2 )
[Galaxy S 4 General] Absolon:
Strange, since I've been in contact with "Fort Knox" several times to get more info and they do confirm that it's an efuse that will go off if you tamper

with the bootloader or any other partition?

And why should Samsung go out with saying it's an e-fuse when they open a can of worms here? All that got it tripped here BEFORE any info was released

was basically tricked into this trap, and probably more so I question their claims of warranty here since they deliberately damaged my property.

I also know it's not just a flag, since I talked to a tech and there is code that does things to the system as well. At least the first time. I think that you need to

Odin it after you tripped it.

A change if a removable part can be done pretty easy. Have you looked inside it if there is one?

I talked with the "Comsunet ministry" today and they told me I have a pretty good case since they didn't inform nor warned about it.

So they open a whole array of claims of entrapment and other claims we can do so they lose by saying it in the end because when I told the person

there and said "Electronic bomb" she was like "WHAT?". Bomb worked.

Then I tried the other one:

If you trim your car and break the engine it's your fault but if you trim your car and Volvo has placed something blowing it up?

When you put it like that, because it's basically how you need to explain it there is no way in hell that someone will agree that's ok.

And then we have the hardware problems that people do experience. Wifi problems. Out of space when there is plenty. Play give strange errors, Boot-loops.

So the have dcucked up something bad I want a phone with Knox removed. They can do it without any damn warranty. Just remove that crap from my phone!

Oh, and if it was so simple I'm sure the real wizzes that sit with JTags would have found out by now
[Galaxy S 4 General] SeaFargo:
Nope. The article says: "This is a mechanism to ensure that enterprise data will be protected as long as the rooting attempt is detected. "

AND NOTHING ELSE

!!

This is NOT a mechanism to break the warranty! This is just a mechanism to ensure that enterprise data ... and so on.

Come ON!! Do not be so afraid! :p
[Galaxy S 4 General] Mittaa:
<sarcasm> Fine ... now we just have to explain this to all Samsung service centers in the world claiming the opposit :cowboy: <sarcasm/>
[Galaxy S 4 General] bungadudu:
This is the original article in which they've said they're ok with rooting.

https://www.samsungknox.com/en/blog...ox-enabled-devices-and-knox-warranty-void-bit

Meanwhile they've edited the article, removed that part and added "*Always check your warranty coverage with your device reseller or mobile service operator.*Many will void your warranty if your device has been rooted."
[Galaxy S 4 General] MrC85:
I contacted Samsung via the Samsung KNOX site...

"Unfortunately, Samsung does not support downgrading of your device and we cannot downgrade your device to a non-KNOX bootloader. The “KNOX Warranty Void” bit (or simply KNOX bit) is used to detect if a non-KNOX kernel has been loaded on the device. It is a one-time programmable bit in e-fuse, which can only be turned from “0” to “1” (i.e. burned). If a non-KNOX boot loader or kernel has been put on the device, KNOX can no longer guarantee the security of the KNOX Container. As a result, this KNOX bit will be burned to “1”, indicating that this device can no longer use the KNOX Container service. There are two possible scenarios: first, a new KNOX Container can no longer be created on such a device; and second, the data encrypted and stored in an existing KNOX Container can no longer be retrieved.

In addition, with a non-approved bootloader you will not be able to upgrade your device to a newer firmware (e.g. 4.3). As for the hardware/device warranty, our policy is that if a custom binary is put on the device, then Samsung cannot guarantee the normal function of the hardware any longer. This means any malfunction of the device resulting from the rooting will not be covered under warranty.

I apologize our response couldn't be more favourable. Please let us know if you have any additional questions or concerns."
[Galaxy S 4 General] SeaFargo:
"malfunction of the device resulting from the rooting" ... That's the key.. How decide? Who and how can decide the connection? Off course if you burn your CPU, maybe they can conclude you've overcooked it. If they find a trace of rooting that's wont help. This kind of problem has happened.

An huge amount of phones, from several brands, have always been in condition to be rooted. And there is no brand that will ever like to declare officially that the do not care about rooting. You can really brake down you phone rooting and so on so they are right.

It depends of the warranty issue.

But this article give us much and much freedom than before. If one have fear, is always free not to burn the Knox flag. :good: Any complains :o
[Galaxy S 4 General] Mittaa:
Actually this answer is important because of this: "This means any malfunction of the device

resulting from the rooting

will not be covered under warranty."

So any kind of HW failure is still covered :good:
[Galaxy S 4 General] lowgitek:
Guys just 2 cents about this Knox flag fuss, this flag should be used only to know if there was any attempt to circumvent the knox and or tampering attempt to the device, so it warranty that the device still "virgin" and is not tampered in that level, so it still trustfull, which is something I should expect when using knox for securing my mobile devices. No worries about it if you don't intent to use it inside a knox enabled environment.

Regards,
[Galaxy S 4 General] bungadudu:
You misunderstood...

Knox counter shows custom binary (root, whatever).

"if a custom binary is put on the device, then Samsung cannot guarantee the normal function of the hardware any longer. This means any malfunction.. will not be covered under warranty."

The moment you rooted, etc, all warranty is voided.

Standard policy for all OEM's.
[Galaxy S 4 General] lowgitek:
Just like that! It has nothing to do with warranty itself but with warranty that device is not tampered in anyway and is still virgin and "trustful"

Regards,

---------- Post added at 04:22 PM ---------- Previous post was at 04:19 PM ----------

That is not true, I did went to repair my phone, I explicit said that phone had a 0x1 flag, and what was explained to me was that if I didn't want to use it on a secure enable knox environment there should be no problem and if I liked they could set it to 0x0 off course they didn't tell me how and how much it will cost me. By the way when you enable knox it explains you that is a one way route only.

Regards,