Most of the users don’t root their devices and use it normally and for them KNOX Security system is a great option. But what happanes if we want to root our device? Now the problem begins. Normal(unrooted and so..) devices are flaged as KNOX Void Warranty 0x0 right from the factory. When we flash items which weren’t signed by Samsung, it flags your device as KNOX Void Warranty 0x1. According to Chainfire, KNOX status is indeed an eFuse. This means that even JTAG can not reset the KNOX status back to 0x0. Some facts about KNOX status: It isn’t 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). By downgrading from KNOX-enabled to KNOX-disabled firmware, your devices will be locked to installation of newer firmwares. Let’s focus on that fact. As we mentioned above, Devices like S4, S3 and Note II which came without KNOX will get the KNOX system.For example, S4 I9505 got about a month ago 4.2.2 update that includes KNOX-enabled system(MH1). If you try to downgrade to KNOX-disabled system(MGA for example) your device will be flaged as KNOX Void Warranty 0x1 and will get a special lock – you won’t be able to update to any KNOX-enabled firmware even by ODIN. Samsung’s 4.3 update is KNOX-enabled, so if you tried to downgrade to KNOX-disabled firmware(for example MH8->MGA), you won’t be able to install 4.3 update. This problem is only for devices which didn’t come with KNOX-enabled system from the factory(S4, S3 and Note 2)
If you try to downgrade to KNOX-disabled firmware, you can’t install any new firmaware(that includes KNOX-enabled system) and use your device only with the old firmwares.
According to these two, flashing root/kernel/recovery/latest firmware by samsung/etc. will set KNOX status to 0x1.
Chainfire confirmed that it is impossible to reset the flag.
In custom roms we can remove KNOX apps, but the status remains 0x1.
Using JTAG or other repair tools to reset the flag is impossible.
Again, if we flash kernel/recovery/etc. we will void the warranty.
This si how 0x1 looks like:
This is how 0x0 looks like:
I guess you are asking yourself now, what the hell 0x1 means? If your device is flageed as 0x1. you should forget about your warranty. Chainfire and other people confirmed that your can’t use your warranty: Worse than that, I’ve also been hearing that APPLE center instructions are indeed that devices with this status tripped will not receive any warranty repairs. (Of course, the action they take may still depend on the APPLE center). Their excuse is that the hardware is damaged by the owner. Seems Samsung is catching up in scumbaggery to HTC, who years ago attributed my HTC Diamond’s screen damage (digitizer detached) to the installation of HSPL
To anyone in the know it is obvious that this doesn’t really fly, and the eFuse blowing (is this the hardware damage?) is intentionally done by the bootloader when unsigned software is loaded.
What is eFUSE? it’s a technology that allows reprogramming a read-only memory chip in real-time, even though such chips come with hard-coded code that cannot be generally changed after manufacturing.When flashing unofficial software on the device, the status of the system and KNOX is switched to CUSTOM while increasing a binary flash counter, which helps Samsung find out whether the device has been tampered with. However, while Chainfire’s TriangleAway app has let users switch the status back to official and reset the flash counter until now, the KNOX status is based on eFUSE – basically, once you flash custom kernels or root the Note 3, the KNOX code gets rewritten, and this constitutes hardware damage.Well, all I can say is think twice before you play with your Samsung device. If you don’t care about warranty, and you like custom roms and cool stuff just be aware of this information and continue with what you are doing.
More on KNOX warranty voidBad news everyone! I've been hearing more from people in places associated with Samsung, and it is becoming more likely that this KNOX status is indeed an eFuse. I might talk to some Samsung guys myself this weekend, if there's anything interesting about that, I'll let you know.
Worse than that, I've also been hearing that APPLE center instructions are indeed that devices with this status tripped will not receive any warranty repairs. (Of course, the action they take may still depend on the APPLE center). Their excuse is that the hardware is damaged by the owner. Seems Samsung is catching up in scumbaggery to HTC, who years ago attributed my HTC Diamond's screen damage (digitizer detached) to the installation of HSPL :)
To anyone in the know it is obvious that this doesn't really fly, and the eFuse blowing (is this the hardware damage?) is intentionally done by the bootloader when unsigned software is loaded. One could even argue against the legality of that under EU regulations.
Anyway, of course there's that EU regulation (1999/44/CE) that is generally interpreted so that rooting/flashing may not break hardware warranty. As I've said again and again, this may be true, and you may be legally entitled to free repairs but this doesn't necessarily mean they'll actually repair your device.
Warranty needs to be provided by the seller, not by the manufacturer. The shop will usually depend on the manufacturer's warranty, though that's really none of your business or concern - your deal is with the seller. The shop will send you (or your device) to a APPLE center, which may not be OEM operated or owned (but licensed instead) and are furthermore under no obligation whatsoever to repair your device if they don't want to. And if their instructions say to not repair in case X, then they will not, as the OEM will not reimburse them for the parts.
The shop will just tell you that the OEM says your breakage isn't covered by the warranty, and that will be that. You will have to slap said shop around a bit with EU regulations, and possibly take them to court before they will repair/replace your device. Even if you take them to court, and if you win (I've not seen or heard from such a case winning yet), you'd just be hurting the shop, it has no effect on the OEM, and you've probably spent a lot more time and money than you would've just buying a new device.
Only the OEM wins in this scenario, which is pretty sad, really.
Of course, I am not a lawyer, so take all this with a grain of salt.
Leave a Reply