Hi everyone, I rooted my Sprint S5 with Towelroot and it did not trip knox. I then installed Xposed Framework and a couple of modules and noticed a lot of lag and the heart rate monitor stopped working (not a big issue though). Is this a known issue with our S5's when it comes to lag as my LG G2 does not have this issue. I am on a stock rom in case you are wondering. Thanks in advance.
UCLA1 said:
Hi everyone, I rooted my Sprint S5 with Towelroot and it did not trip knox. I then installed Xposed Framework and a couple of modules and noticed a lot of lag and the heart rate monitor stopped working (not a big issue though). Is this a know issue with our S5's when it comes lag as my LG G2 does not have this issue. I am on a stock rom in case you are wondering. Thanks in advance.
Click to expand...
Click to collapse
This post will show you how to fix your prob, read it carefully from the beginning to the end
UCLA1 said:
Hi everyone, I rooted my Sprint S5 with Towelroot and it did not trip knox. I then installed Xposed Framework and a couple of modules and noticed a lot of lag and the heart rate monitor stopped working (not a big issue though). Is this a know issue with our S5's when it comes lag as my LG G2 does not have this issue. I am on a stock rom in case you are wondering. Thanks in advance.
Click to expand...
Click to collapse
if you have root , go to system , set rw , go to buil.prop and change in : ro.securestorage.support=true( change to false ) like: ro.securestorage.support=false ! restart and done !
ManDone.vRs said:
if you have root , go to system , set rw , go to buil.prop and change in : ro.securestorage.support=true( change to false ) like: ro.securestorage.support=false ! restart and done !
Click to expand...
Click to collapse
Thanks
Related
I'm a newbie, and I have a couple of questions about Xposed on the AT&T GS5 Active.
A) Does it mess with the bootloader?
B) Will it trip the Knox efuse?
C) Has anyone had any problems with xposed on the Galaxy S5?
D) And on a side note, from what I've read it seems that the S5 and S5 Active are the same except for the form factor. Is this correct?
Xposed crashes the S-health & private mode..
Otherwise no problem with the bootloader.
Masum56k said:
Xposed crashes the S-health & private mode..
Otherwise no problem with the bootloader.
Click to expand...
Click to collapse
thanks
Masum56k said:
Xposed crashes the S-health & private mode..
Otherwise no problem with the bootloader.
Click to expand...
Click to collapse
I found this fix on other site that stops S Health from crashing when Xposed Framework is installed.
Fix Xposed Framework and S Health issue on Galaxy S5
I just installed the xposed framework and xposed wanam today as recommended by another user. It works fine with my s5 and didnt have the s health crashing problem either. Im using 2.6.1 on a sprint s5. Im still new so im not really sure what k ox efuse is but I do think the knox should be disabled when you root your device anyways.
defied123 said:
I just installed the xposed framework and xposed wanam today as recommended by another user. It works fine with my s5 and didnt have the s health crashing problem either. Im using 2.6.1 on a sprint s5. Im still new so im not really sure what k ox efuse is but I do think the knox should be disabled when you root your device anyways.
Click to expand...
Click to collapse
It's sort of like a rom flash counter, but I've read that its actually a hardware thing in the cpu that is physically impossible to reset once tripped. I assume that means no triangle-away.
steve3758 said:
It's sort of like a rom flash counter, but I've read that its actually a hardware thing in the cpu that is physically impossible to reset once tripped. I assume that means no triangle-away.
Click to expand...
Click to collapse
Knox is definitely not an efuse. If it were, there would be no way to reset it besides replacing the whole Qualcomm System chip. Since the Samsung guys(the ones that repair your phone) can reset Knox(I've experienced it myself with my old S4) without replacing the whole SoC, it can't be an efuse. sadly, there is no known way to reset it though.
Also, I've never had an problems with Xposed on my International S5. As long as you have backups and a custom recovery, (almost) nothing can go wrong anyway.
guetzli32 said:
Knox is definitely not an efuse. If it were, there would be no way to reset it besides replacing the whole Qualcomm System chip. Since the Samsung guys(the ones that repair your phone) can reset Knox(I've experienced it myself with my old S4) without replacing the whole SoC, it can't be an efuse. sadly, there is no known way to reset it though.
Also, I've never had an problems with Xposed on my International S5. As long as you have backups and a custom recovery, (almost) nothing can go wrong anyway.
Click to expand...
Click to collapse
Well, anyway I managed to root my SM-G870A, install Busybox, and Xposed, all without tripping Knox, and I want to keep it that way, at least for now.
Shout-out to geohot for finding a root exploit that doesn't trip Knox
I have never experienced s health crashing due to xposed
Sent from my SM-G900F using XDA Free mobile app
steve3758 said:
I'm a newbie, and I have a couple of questions about Xposed on the AT&T GS5 Active.
A) Does it mess with the bootloader?
B) Will it trip the Knox efuse?
C) Has anyone had any problems with xposed on the Galaxy S5?
D) And on a side note, from what I've read it seems that the S5 and S5 Active are the same except for the form factor. Is this correct?
Click to expand...
Click to collapse
Well I can tell that you didn't search the forum or you would have tripped over all of the existing threads discussing this. The bootloader isn't an issue, but lots of people have issues with xposed /shealth since they don't configure it properly. You need to edit the secure storage system attribute for the two apps to peacefully coexist. You'll find details in the forum.
Not much will trip Knox other than a custom kernel, custom recovery or certain root exploits. And perhaps partition corruption e.g. from trying to downgrade the bootloader to JB.
@guetzli32
You are correct that Samsung's assertion that the Knox flag is an "efuse" (standard terminology would be OTP) is not true. However you are out of date in saying that there is no known way to reset it. You can find forum threads detailing otherwise.
To date it has only been reset in controlled circumstances, so don't expect to revert Knox on your handset anytime soon. But it does explain the observation that many Samsung repairs have reverted the Knox flag.
.
Have a bad problem with S-Health, I rooted using Towel root, then installed Xposed, S-health crashed, so i removed xposed and s-health persisted to crash, so i then performed a factory reset, and s-health continued to crash.
The only way it'll work is if it's not updated, I personally don't want root no more i just want it to work.
Stock rom 4.4.2
Any help would be greatly appreciated.
Did you remove the framework for xposed first? Anyways since you wiped the data partition, you may as well flash your ROM back and start from scratch. S health works when rooted with towel root but xposed still bugs it.
Sent from my SM-G900F using XDA Free mobile app
russ18uk said:
Did you remove the framework for xposed first? Anyways since you wiped the data partition, you may as well flash your ROM back and start from scratch. S health works when rooted with towel root but xposed still bugs it.
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
Crap no I didn't, I have wiped from the recovery though wouldn't that eliminate it ? I've now updated, was trying to avoid losing warranty. But now it never works. Phone isn't rooted no more and I'm not able to root with towel root either.
I'm guessing I'd have to flash a prior ROM via Odin and then re root, install xposed and then remove the framework if it's still somehow there.
Any ideas ? Thanks
dladz said:
Crap no I didn't, I have wiped from the recovery though wouldn't that eliminate it ? I've now updated, was trying to avoid losing warranty. But now it never works. Phone isn't rooted no more and I'm not able to root with towel root either.
I'm guessing I'd have to flash a prior ROM via Odin and then re root, install xposed and then remove the framework if it's still somehow there.
Any ideas ? Thanks
Click to expand...
Click to collapse
Same thing happened to me, you need to reflash the phone for it to work, never touching exposed again
juDGEY2k10 said:
Same thing happened to me, you need to reflash the phone for it to work, never touching exposed again
Click to expand...
Click to collapse
If I do that will I trip knox? As that's something I'd like to avoid.
Thanks by the way .
dladz said:
If I do that will I trip knox? As that's something I'd like to avoid.
Thanks by the way .
Click to expand...
Click to collapse
Not sure larr, i dont care myself best ask about before you jump in
Try this...
1. Uninstall Xposed framework if not already.
2. Go in /system and open build.prop in a text editor
3. go to the line ( “ro.securestorage.support=true” ) and change it to false
4. Install the xposed framework
5. Clear the app data for S-Health and HealthService
6. Reboot
solution..
dladz said:
Have a bad problem with S-Health, I rooted using Towel root, then installed Xposed, S-health crashed, so i removed xposed and s-health persisted to crash, so i then performed a factory reset, and s-health continued to crash.
The only way it'll work is if it's not updated, I personally don't want root no more i just want it to work.
Stock rom 4.4.2
Any help would be greatly appreciated.
Click to expand...
Click to collapse
i had the same issue and it got solved.. activate samsung apps/galaxy apps if u disabled it from the app manger in settings. and ur s health will be working fine for sure.. reply if it works or not ....
hope it help
There are numerous threads about this issue. If you read some of them, you will see the details of what consistently works as a solution.
.
juDGEY2k10 said:
Not sure larr, i dont care myself best ask about before you jump in
Click to expand...
Click to collapse
Haha, first time i've seen a laaa on xda Cheers m8, i do miss being back home.
fffft said:
There are numerous threads about this issue. If you read some of them, you will see the details of what consistently works as a solution.
.
Click to expand...
Click to collapse
Dude are you going to post on every thread i make? Just to tell me to search? You're offering nothing in the way of a solution, more to the point, both the threads i've created were for unique questions, not all my questions are answered in other threads.
Please stop just commenting to say search.
yash kariya said:
i had the same issue and it got solved.. activate samsung apps/galaxy apps if u disabled it from the app manger in settings. and ur s health will be working fine for sure.. reply if it works or not ....
hope it help
Click to expand...
Click to collapse
My Galaxy app's application hasn't been deactivated m8, it's always been on, the second i turn on S-Health it crashes, it's because my system says custom when in download mode i believe, problem is i've now updated my OS so i'd need to reflash a stock rom via odin and then re-root if i wanted to have access to the location that the user before you mentioned. Been away from home for a few days so not had the chance, might do it tomorrow.
Thanks for the suggestion, but if I turn on S-Health now i know it'll begin crashing again.
aguarello said:
1. Uninstall Xposed framework if not already.
2. Go in /system and open build.prop in a text editor
3. go to the line ( “ro.securestorage.support=true” ) and change it to false
4. Install the xposed framework
5. Clear the app data for S-Health and HealthService
6. Reboot
Click to expand...
Click to collapse
Will need root access for that, need to downgrade the OS back to a prior version. Will do it tomorrow.
Thanks for your help and to anyone else who offered something constructive.
dladz said:
Haha, first time i've seen a laaa on xda Cheers m8, i do miss being back home.
Click to expand...
Click to collapse
awww why aint u home?
Im over the water love looking out over to liverpool really good skyline at night.
Hope you get it sorted mate
juDGEY2k10 said:
awww why aint u home?
Im over the water love looking out over to liverpool really good skyline at night.
Hope you get it sorted mate
Click to expand...
Click to collapse
Cheers fella, an I moved to London about 7 years ago, met a girl in London, was in Liverpool last saturday for my Stag night, dressed up like a bee gee with an afro and silver stacks, had a boss night m8, well until i fell on some stairs an near ripped my leg out of my hip joint, just spent 4 hours in the hospital getting X-rays. Worth it though
An yea Liverpool is a gorgeous City, night life is amazing we smashed it the other night
Hi, I'm about to root my n910f 4.4.4 btu but I just need to know what the root "breaks".
I already know S Health is one of the things which stop working but what else (if anything)
Next question, how do you "fix" the apps so they work again while the phone is rooted?
Thank you.
Chiller.
Chillerhippie said:
Hi, I'm about to root my n910f 4.4.4 btu but I just need to know what the root "breaks".
I already know S Health is one of the things which stop working but what else (if anything)
Next question, how do you "fix" the apps so they work again while the phone is rooted?
Thank you.
Chiller.
Click to expand...
Click to collapse
S Health works perfectly fine after rooting. The only thing that it breaks is Knox (you won't ever be able to use knox anymore).
Shealth works of cours it breaks 2 things warranty XD and OTA ...well Knox works for me I rooted via towel root ....u can still get updates by disabling root temporary by using app on play store like root triangle away or something like that...and when u go to download mod ur Knox will trip and u can't fix that ...it won't affect u by any mean ...
sent from my GT I9505 5.0.1
navi dl said:
Shealth works of cours it breaks 2 things warranty XD and OTA ...well Knox works for me I rooted via towel root ....u can still get updates by disabling root temporary by using app on play store like root triangle away or something like that...and when u go to download mod ur Knox will trip and u can't fix that ...it won't affect u by any mean ...
sent from my GT I9505 5.0.1
Click to expand...
Click to collapse
How on earth did you root via towelroot on a note4?
Eh!I did to my s4 d s5..for note 4 u got to wait anyway I gave answer according to ur question press thanks if it helped may be u can try mobogenie one click root...I m not sure about triping Knox....did u try towelroot on note 4 is it supported ? Get the app and check it out..
sent from my GT I9505 5.0.1
Everything works except knox wich for the vast majority is not a problem. Warranty is a question of luck, some repair centers doesn't care about knox triped but others refuse to repair in that condition.
navi dl said:
Eh!I did to my s4 d s5..for note 4 u got to wait anyway I gave answer according to ur question press thanks if it helped may be u can try mobogenie one click root...I m not sure about triping Knox....did u try towelroot on note 4 is it supported ? Get the app and check it out..
sent from my GT I9505 5.0.1
Click to expand...
Click to collapse
Why would you even suggest towelroot on the note 4 forum? This is not S4 and it may cause bricks.
Dont u get what I m saying....I answered the question then he askd for the method ...so i told him what was the way I did...man read properly before coming to an conclusion
sent from my GT I9505 5.0.1
I rooted my first Note 4 and indeed after it was rooted S Health stopped working. Because the Note 4 had more issues I returned it to the shop and they exchanged it with a new one. My new Note 4 isn't rooted because of the S Health issue.
Dude, Root doesn't break S Health. I have it rooted since the fist day I owned it and tracks my fitness perfectly. Xposed is known to break S Health and Private mode but a Module fixes it. Right now I'm running the lastest Lollipop build and everything works perfectly fine.
The only thing that breaks is Knox. So if Samsung Pay comes to our device (right now is on S6) you couldnt use it as it requires a non triggered Knox. But, In my country, i doubt Samsung/Apple/Android pay will come to my near market.
S Health working fine on my rooted Note 4 too.
Root does NOT break S-Health. Something else did that, 100% sure. Most prolly Xposed or system bug. S-Health & Private Mode should work rooted for 99.99% of the time. the other times it's just individual phones thats the cause
Chillerhippie said:
Hi, I'm about to root my n910f 4.4.4 btu but I just need to know what the root "breaks".
Chiller.
Click to expand...
Click to collapse
Toss3 said:
S Health works perfectly fine after rooting. The only thing that it breaks is Knox (you won't ever be able to use knox anymore).
Click to expand...
Click to collapse
You loose Knox which is a very handy feature if you like to have multiple identities / accounts (facebook, instagram etc) Or if you have multiple relations with girlfriends (no spying woman) and you also loose payments with fingerprint verification (FIDO) Actually you loose anything that uses the FIDO API This is not fixable anymore when rooted
Hi guys!
As some of you will know, Samsung have no longer allowed S-Health to work on devices where Knox has been tripped.*
This guide will show you how to get the latest version of S-Health to run without this block.
Some members and also me reported s-health for knox doesnt work on khongloi Roms but if you follow this ways you can solve this problem and deknoxed problem.
After install Rom install this zip in TWPR to change buid.prop.
I tested it only on my n920cd device on khongloi nougat s7edge ported Rom.
If you have problem tell to check it.
And also thanks to @CuBz90 (S7 edge developer)
After flashing this swiftkey gives me a constant error even after uninstalling and reinstalling. It did fix s health though.lol
tgamble160 said:
After flashing this swiftkey gives me a constant error even after uninstalling and reinstalling. It did fix s health though.lol
Click to expand...
Click to collapse
Obviously it is s7 build.prop it is rather smart to edit it in the Rom build.prop
KatariaMax said:
Obviously it is s7 build.prop it is rather smart to edit it in the Rom build.prop
Click to expand...
Click to collapse
If it were obvious to me I wouldn't have needed to post anything. I'm not new at this, but I'm not overly educated on it either. I always appreciate when sometime helps me out, and I try to help others when I'm able. So I'm not sure what you thought being a smartass would accomplish, but thank you anyway, I figured it out a week ago. Considering I posted that 8 days ago .
Hi guys!
As some of you will know, Samsung have no longer allowed S-Health to work on devices where Knox has been tripped.*
This guide will show you how to get the latest version of S-Health to run without this block.
Some members and also me reported s-health for knox doesnt work on khongloi Roms but if you follow this ways you can solve this problem and deknoxed problem.
After install Rom install this zip in TWPR to change buid.prop.
I tested it only on my n920cd device on khongloi nougat s7edge ported Rom.
If you have problem tell to check it.
And also thanks to @CuBz90 (S7 edge developer)
hamidrezatata said:
Hi guys!
As some of you will know, Samsung have no longer allowed S-Health to work on devices where Knox has been tripped.*
This guide will show you how to get the latest version of S-Health to run without this block.
Some members and also me reported s-health for knox doesnt work on khongloi Roms but if you follow this ways you can solve this problem and deknoxed problem.
After install Rom install this zip in TWPR to change buid.prop.
I tested it only on my n920cd device on khongloi nougat s7edge ported Rom.
If you have problem tell to check it.
And also thanks to @CuBz90 (S7 edge developer)
Click to expand...
Click to collapse
Well Good one
Sent from my SM-G950F using Tapatalk
hamidrezatata said:
Hi guys!
As some of you will know, Samsung have no longer allowed S-Health to work on devices where Knox has been tripped.*
This guide will show you how to get the latest version of S-Health to run without this block.
Some members and also me reported s-health for knox doesnt work on khongloi Roms but if you follow this ways you can solve this problem and deknoxed problem.
After install Rom install this zip in TWPR to change buid.prop.
I tested it only on my n920cd device on khongloi nougat s7edge ported Rom.
If you have problem tell to check it.
And also thanks to @CuBz90 (S7 edge developer)
Click to expand...
Click to collapse
Probably not a good idea for prople to flash a build.prop file to other device variants(or Roms in case anyone's thinking of doing that). Could really mess things up. Not sure about Khongloi ROM either, but to fix S Health(easily), I think all you have to do is:
1) Download "build Prop Editor” from the Play Store.
2) Locate "ro.config.tima" and see if it's set to "1". If so, then just set it to "0".
Worked for Me at least. Anyhow, hope this helps. Good luck!
hamidrezatata said:
Hi guys!
As some of you will know, Samsung have no longer allowed S-Health to work on devices where Knox has been tripped.*
Click to expand...
Click to collapse
That's simply not correct as the solution is easy and the mistake to be fixed by rom builder -> see post beneath
bogarty said:
Probably not a good idea for prople to flash a build.prop file to other device variants(or Roms in case anyone's thinking of doing that). Could really mess things up. Not sure about Khongloi ROM either, but to fix S Health(easily), I think all you have to do is:
1) Download "build Prop Editor” from the Play Store.
2) Locate "ro.config.tima" and see if it's set to "1". If so, then just set it to "0".
Worked for Me at least. Anyhow, hope this helps. Good luck!
Click to expand...
Click to collapse
:good: should be given in rom thread if it isn't already there
I dont know about others but my S health is working fine without the fix, and my knox is also tripped.
P.S I am on Nougat.
sunny1119 said:
I dont know about others but my S health is working fine without the fix, and my knox is also tripped.
P.S I am on Nougat.
Click to expand...
Click to collapse
It works fine on some Roms. My current one, for instance, I didn't need to tweak anything to get it to work. My last one I had to do the build.prop fix I mentioned above.
bogarty said:
It works fine on some Roms. My current one, for instance, I didn't need to tweak anything to get it to work. My last one I had to do the build.prop fix I mentioned above.
Click to expand...
Click to collapse
Ah ok, I think it would be something with the roms, I am on official nougat.