Samsung Clarifies That CF-Root Will Trip Knox Efuse On The Note 3

[DroidModderX]

​

Samsung posted a blog on their SamsungKnox website earlier that directly addresses the CF-Autoroot Root method by developer "ChainfireXDA". They didn't really tell us anything that we didn't already know. They explained the CF-AutoRoot process and how it flashes a modified recovery.img and cache.img, then boots into the modified recovery to flash SuperSU, before flashing the stock image, and cleaning the cache. They then go on to explain that since the root method uses a custom recovery.img it will burn the efuse and permanently mark the device as modified. The reason given is to protect enterprise data while a phone is rooted. While they don't say the root method is "The Devil", they also don't sing it's praises. What surprised me the most is that Samsung decided to include links to CF-AutoRoot. It would be nice to see a reversible efuse for root users. An efuse that would repair itself when a device is unrooted, or atleast a knox status of unmodified. For the full blog post head to the link below.

SamsungKnox.com

 

[johnomaz]

xda-developers - View Single Post - Root de la Vega [KNOX 0x0 Root - Lots of Versions - No Exynos]

You can still root without tripping Knox. you don't get a custom recovery or the ability to flash ROMs unless you trip Knox but with XPosed Framwork, you can still do a ton.

 

[KZIWarrior]

It would be nice to see a reversible efuse for root users. An efuse that would repair itself when a device is unrooted, or atleast a knox status of unmodified. For the full blog post head to the link below.

SamsungKnox.com

This would defeat the purpose of the eFuse to begin with and not protect enterprise data (i.e. someone could root the device, do what the needed to, then un-root it and no-one would know). In all honesty for the average user and even most power users this means very little, but for enterprise users and IT professionals that need to secure data it is huge.