Post Reply

Towelrooted, tripping Knox editing Build.prop?

OP xmguy

1st August 2014, 05:26 AM   |  #1  
xmguy's Avatar
OP Senior Member
Flag McMinnville, TN
Thanks Meter: 19
 
259 posts
Join Date:Joined: Sep 2009
More
I'm not new to Android or rooting. I am new to Knox with my S5. If I edit the build prop for S Health fix or edit anything with Root Explorer does that trip Knox (it's frozen in Titanium Backup), or is it only installing custom recovery and roms? I've installed Nandroid online backup..but this Knox stuff has made me anxious on that too.
1st August 2014, 10:35 AM   |  #2  
fffft's Avatar
Senior Member
Thanks Meter: 538
 
1,823 posts
Join Date:Joined: Jul 2013
Quote:
Originally Posted by xmguy

If I edit the build prop for S Health fix or edit anything with Root Explorer does that trip Knox (it's frozen in Titanium Backup), or is it only installing custom recovery and roms?


You have not, nor can you freeze the important part of Knox because it's located in the bootloader. The bootloader checks the kernel & recovery signatures and so forth on boot. Failing the signature check there is what increments the Knox flag 99/100 times.

So custom kernels or recovery, some rooting exploits or perhaps attempting to downgrade to a JellyBean bootloader will change your Knox flag. And in rare cases, just splendidly bad luck e.g. having a bad kernel crash at just the wrong time or say from the corruption resulting from a power interruption during a firmware write.

Note that you do not need to edit build.prop to make S Health work and any unsound edits there may render your device unbootable until you remedy them. But we wouldn't expect edits there to increment Knox. Not that it's impossible, but it would be a rare thing where an edit spun a fatal error during the actual signature check or something of that nature.

.
The Following User Says Thank You to fffft For This Useful Post: [ View ]
1st August 2014, 01:52 PM   |  #3  
xmguy's Avatar
OP Senior Member
Flag McMinnville, TN
Thanks Meter: 19
 
259 posts
Join Date:Joined: Sep 2009
More
Quote:
Originally Posted by fffft

You have not, nor can you freeze the important part of Knox because it's located in the bootloader. The bootloader checks the kernel & recovery signatures and so forth on boot. Failing the signature check there is what increments the Knox flag 99/100 times.

So custom kernels or recovery, some rooting exploits or perhaps attempting to downgrade to a JellyBean bootloader will change your Knox flag. And in rare cases, just splendidly bad luck e.g. having a bad kernel crash at just the wrong time or say from the corruption resulting from a power interruption during a firmware write.

Note that you do not need to edit build.prop to make S Health work and any unsound edits there may render your device unbootable until you remedy them. But we wouldn't expect edits there to increment Knox. Not that it's impossible, but it would be a rare thing where an edit spun a fatal error during the actual signature check or something of that nature.

.

Thanks.

How can I make S Health work without using the build.prop edit, other than disabling or removing Xposed?

Sent from my SM-G900V using XDA Free mobile app
1st August 2014, 06:48 PM   |  #4  
fffft's Avatar
Senior Member
Thanks Meter: 538
 
1,823 posts
Join Date:Joined: Jul 2013
Quote:
Originally Posted by xmguy

How can I make S Health work without using the build.prop edit, other than disabling or removing Xposed?


You forgot to mention your requirement for Xposed framework earlier, you only mentioned S health.
Xposed is not a stock component. Using both on the S5 is a new theme importuning the antithetical ro.securestorage flag.

.
1st August 2014, 08:15 PM   |  #5  
xmguy's Avatar
OP Senior Member
Flag McMinnville, TN
Thanks Meter: 19
 
259 posts
Join Date:Joined: Sep 2009
More
Quote:
Originally Posted by fffft

You forgot to mention your requirement for Xposed framework earlier, you only mentioned S health.
Xposed is not a stock component. Using both on the S5 is a new theme importuning the antithetical ro.securestorage flag.

.

My mistake, sorry. If I edit that ro.securestorage area will that trip Knox? So I can use Xposed and S Health?

Sent from my SM-G900V using XDA Free mobile app
1st August 2014, 08:34 PM   |  #6  
fffft's Avatar
Senior Member
Thanks Meter: 538
 
1,823 posts
Join Date:Joined: Jul 2013
Quote:
Originally Posted by xmguy

If I edit that ro.securestorage area will that trip Knox? So I can use Xposed and S Health?


Lots of people have done that edit and it hasn't changed their Knox flag. Nor can I think of a rationale why it would, unless you have a bad crash. But then it wouldn't be the edit per se that increments Knox. It would be the crash.

.
The Following User Says Thank You to fffft For This Useful Post: [ View ]
1st August 2014, 09:45 PM   |  #7  
xmguy's Avatar
OP Senior Member
Flag McMinnville, TN
Thanks Meter: 19
 
259 posts
Join Date:Joined: Sep 2009
More
Quote:
Originally Posted by fffft

Lots of people have done that edit and it hasn't changed their Knox flag. Nor can I think of a rationale why it would, unless you have a bad crash. But then it wouldn't be the edit per se that increments Knox. It would be the crash.

.

So as long as I don't flash a custom rom or a recovery then I'm ok? All other edits are free without worrying about Knox?

Sent from my SM-G900V using XDA Free mobile app
1st August 2014, 10:05 PM   |  #8  
Repulsa's Avatar
Recognized Contributor
Your Mom's crib
Thanks Meter: 2,049
 
1,865 posts
Join Date:Joined: Nov 2010
Donate to Me
Quote:
Originally Posted by xmguy

So as long as I don't flash a custom rom or a recovery then I'm ok? All other edits are free without worrying about Knox?

Sent from my SM-G900V using XDA Free mobile app

Yup that's correct .

Sent from my SM-G900F using Tapatalk

The Following User Says Thank You to Repulsa For This Useful Post: [ View ]
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Galaxy S 5 Q&A, Help & Troubleshooting by ThreadRank