View Single Post
Old October 10th, 2013, 06:49 AM   #78 (permalink)
Screech
AF Contributor
 
Screech's Avatar
 
Join Date: Jun 2011
Location: Eastern NC
Posts: 236
 
Device(s): Samsung I9500,Samsung P3113,Samsung I9300 (wife),Samsung I9100 (kid 1),Motorola Defy+ (kid 2)
Carrier: Straight Talk

Thanks: 7
Thanked 19 Times in 18 Posts
Default

First, sorry for my PC terms like BIOS while referring to a phone. Not completely schooled up on the current names, but I think you'll understand my thought.

I know this may be a slightly off topic, while related. Where would you think the code to pop the efuse is. Would it be in the BIOS level, possibly requiring a JTAG interface to replace with code that will not pop the efuse? Maybe I'm way off track, but I think this type of security would have to be supported to the BIOS level.

If at BIOS level I think you may be able to flash a new bios that will not pop the efuse regardless of the recovery or ROM being used. I understand that a JTAG interface with these phones is beyond what most of the ROM users would be capable on there own and that most devices would have a physical trail from being JTAGed since soldering on the board is often required so a warranty would be out of the question. But, it could allow for you use the device in a corporate level is you corporation has a BYOD program and on the weekends or such play with other ROMs/rooting without having the KNOX system report the device as "compromised" or by a second device to toy with.
Screech is offline  
Reply With Quote
The Following User Says Thank You to Screech For This Useful Post:
EarlyMon (October 10th, 2013)