S health Fix on khongloi Nougat Rom s7 edge port v3 - Galaxy Note5 General

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 .

Related

[Q] rooting and device encryption sm-n900

Greetings,
Yesterday I decided to root my Note 3 (sm-n900) mainly to remove samsung's bloatware and install afwall.
Just after I rooted my phone with Odin + "CF-Auto-Root-ha3g-ha3gxx-smn900" and went for the first reboot, I noticed that my phone wouldn't boot anymore. After some hair pulling, I decided to wipe the device and after that it booted fine.
Finally I managed to remove %[email protected]! Flipboard and My magazine (a lot of crashes with sms and regular email, but worth removing!). Total happiness and a faster phone!
When I tried to enable encryption on the device, the phone just crashed again (with the same droid logo that appeared on the boot before the wipe). I came here and found some other users talking about rooting + encryption with sm-n900 saying that it's not working. (some reported that kingo method would work, but I really don't feel comfortable with king).
Now I'm downloading the stock rom, and planning to flash the note3 back to original since I have the recipe for T virus on my phone and couldn't allow it to fall on wrong hands :laugh:
Is this a bug on cf-auto-root or encryption doesn't work with rooting at all? If it's a bug, any ideas of when a fix should be around?
Thanks!
Hi eduardogsilva,
I don't know your device, but I encountered a problem activating encryption on a rooted SM-P900. I'm not sure, but I think it's a general problem with Samsung KitKat devices. I described, how I got it solved for my device here. If you still have issues, please have a look at my thread and let me know, if it works for you...
Cheers!
bruzzy said:
Hi eduardogsilva,
I don't know your device, but I encountered a problem activating encryption on a rooted SM-P900. I'm not sure, but I think it's a general problem with Samsung KitKat devices. I described, how I got it solved for my device here. If you still have issues, please have a look at my thread and let me know, if it works for you...
Cheers!
Click to expand...
Click to collapse
Thanks again bruzzy
Encryption doesn't work (properly) on rooted Samsung devices.
radicalisto said:
Encryption doesn't work (properly) on rooted Samsung devices.
Click to expand...
Click to collapse
Hello radicalisto, following the guide that bruzzy wrote, I managed to activate the encryption on a rooted note3.
So I guess that it should be fine now... Or is there any other issues besides activating encryption?
thanks
eduardogsilva said:
Hello radicalisto, following the guide that bruzzy wrote, I managed to activate the encryption on a rooted note3.
So I guess that it should be fine now... Or is there any other issues besides activating encryption?
thanks
Click to expand...
Click to collapse
It'll work, just not 100% - don't be surprised if one day it freaks out on you and doesn't let you unlock it. Happens sometimes, Although, it may be that it'll stay fine for you (luck of the draw) - with root being an exploit, the system is designed to look out for changes and freak out if it spots them.
radicalisto said:
It'll work, just not 100% - don't be surprised if one day it freaks out on you and doesn't let you unlock it. Happens sometimes, Although, it may be that it'll stay fine for you (luck of the draw) - with root being an exploit, the system is designed to look out for changes and freak out if it spots them.
Click to expand...
Click to collapse
Well, the important information that I have on my mobile is in sync, the only bad thing would be reinstalling and reconfiguring everything again, so not a big problem in loosing my phone data.
I would love to use a custom rom and completely say goodbye to touchwiz and to the huge bloatware that comes with my phone, but unfortunately, CM for note3 exynos is not available yet.
thanks

S health Fix on khongloi Nougat Rom s7 edge port v3

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.

[Q] how to fix samsung s health after unroot

Hi i rooted my samsung s8 (sm-g950fd) and after i wile i didnt need root any more so i falshed it with his stok rom and i get this eroor on s health & secure folder & ...
cant opened on a rotted device !!!
i want know how can i fix this ?? (samsung knox is not runnig too)
Cocoadownload said:
Hi i rooted my samsung s8 (sm-g950fd) and after i wile i didnt need root any more so i falshed it with his stok rom and i get this eroor on s health & secure folder & ...
cant opened on a rotted device !!!
i want know how can i fix this ?? (samsung knox is not runnig too)
Click to expand...
Click to collapse
Once you root you trip Knox. Afaik you can't reset it so certain apps like Samsung pay and s health will stop working. In the future there may or may not be a way to reset it.
You have to root it again and install build prop from playstore, search of a line like this ro. Config tima=1 and turn the 1 to 0 and save reboot your device and it will work
bouyhy01 said:
You have to root it again and install build prop from playstore, search of a line like this ro. Config tima=1 and turn the 1 to 0 and save reboot your device and it will work
Click to expand...
Click to collapse
i cant root agian becuse i done unroot becase some apps i have (business app) they dont work at rooted device and also there is a chance i give the phone to my brother and he is anti root persion and he heat root !!!!
if i root device then do it then unroot and after that do a factory rest this will be ok ??? app still work??? or not?
Cocoadownload said:
i cant root agian becuse i done unroot becase some apps i have (business app) they dont work at rooted device and also there is a chance i give the phone to my brother and he is anti root persion and he heat root !!!!
if i root device then do it then unroot and after that do a factory rest this will be ok ??? app still work??? or not?
Click to expand...
Click to collapse
Nope, it won't.
Even if you factory reset your phone, the Samsung Knox trip will still be there, so you'll unable to use it.
Another option would be installing custom ROM that "tricks" apps into thinking that the knox is still on, but again, some apps might not work. In my case, when I still use a S7, my samsung gift app doesn't work anymore.
Well, if you really need to get S Health, I think this is the only option.
You should have done your learning before rooting. On ALL Samsung devices for the past 3-4 years, rooting was a one-way trip to trip Knox, and the only solution around that is patching the system so it thinks you still have Knox at 0x0.
Since Knox is a single eFuse that can only be written ONCE, you can NOT undo it. And you probably just lost your warranty.
I have downgraded my S Health version to 4.8 and now it works again - with knox tripped.
I used that version: http://www.apkmirror.com/apk/samsun...ase/s-health-4-8-0-0085-android-apk-download/
Good luck
fonix232 said:
You should have done your learning before rooting. On ALL Samsung devices for the past 3-4 years, rooting was a one-way trip to trip Knox, and the only solution around that is patching the system so it thinks you still have Knox at 0x0.
Since Knox is a single eFuse that can only be written ONCE, you can NOT undo it. And you probably just lost your warranty.
Click to expand...
Click to collapse
i know a lot of thing about rooting and i always rooted all of my devices for example my last devise was samsung s7 edge (fd series) i rooted and when i want to sell it i can do unroot and enable knox agian after that every thing was working but that way dont work on my samsung s8 and my problem is after last week update my phone will restart time to time and i search about that and the solution is enable knox agian and i dont know how to do it
fonix232 said:
You should have done your learning before rooting. On ALL Samsung devices for the past 3-4 years, rooting was a one-way trip to trip Knox, and the only solution around that is patching the system so it thinks you still have Knox at 0x0.
Since Knox is a single eFuse that can only be written ONCE, you can NOT undo it. And you probably just lost your warranty.
Click to expand...
Click to collapse
i know a lot of thing about rooting and i always rooted all of my devices for example my last devise was samsung s7 edge (fd series) i rooted and when i want to sell it i can do unroot and enable knox agian after that every thing was working but that way dont work on my samsung s8 and my problem is after last week update my phone will restart time to time and i search about that and the solution is enable knox agian and i dont know how to do it
Cocoadownload said:
i know a lot of thing about rooting and i always rooted all of my devices for example my last devise was samsung s7 edge (fd series) i rooted and when i want to sell it i can do unroot and enable knox agian after that every thing was working but that way dont work on my samsung s8 and my problem is after last week update my phone will restart time to time and i search about that and the solution is enable knox agian and i dont know how to do it
Click to expand...
Click to collapse
any body know how we must do it??
Great solution
Fusseldieb said:
I have downgraded my S Health version to 4.8 and now it works again - with knox tripped.
I used that version:
Good luck
Click to expand...
Click to collapse
great solution my friend. you saved my day. thanks a lot. i installed that version started it up and even then got my update to 5.xx and still it is working great. i just bought s3 frontier and want it to work with gear. so thank you really much :good::good::good::good::good:
So the fix is to set ro.config.tima to 0. And install older version of shealth
KoalaKinG said:
great solution my friend. you saved my day. thanks a lot. i installed that version started it up and even then got my update to 5.xx and still it is working great. i just bought s3 frontier and want it to work with gear. so thank you really much :good::good::good::good::good:
Click to expand...
Click to collapse
I am not able to install 4.8 on android 7 on a note 5.
Package is damaged error message!
Help please.
Thanks!!!
G.
https://forum.xda-developers.com/s7-edge/how-to/guide-how-to-s-health-devices-knox-t3543306
---------- Post added at 04:02 PM ---------- Previous post was at 04:01 PM ----------
i used the guide installing the old apk activating it and then updating it... it's working 100%
Octoplus for samsung repair
for now, i would rather choose octoplus to repair the corresponding fault, another octoplus is a nice dealing way for samsung fault. thanks for the vipfixphone team.
fix S-Health and Apps Knox After Knox 1 trip
How To Fix S-Health And Apps Konx After Root OR Knox 1
Root Device
Install root Exloper Or any file exloper file system
Go To system
serach Buli.prob
open with editor or notpad++
serach for
ro.config.tima=1/2
change to
ro.config.tima=0
and save and repalce bulid
reboot device
I updated with odin to Oreo UK Fw .
All works well except S-Healt which claims that the phone is rooted (but I did not root and knox is 0/0) and does not start.
I tried to update S-Health but it does not work, and I can not install version 4.8 because I have this message: not installed
Unfortunately it is installed as a system app and I can only disable it and delete updates, but even so it works.
Tips?
I am having S8 G950F, my device is rooted with Magisk .. curently my phone is running renovate ice , i am using almost every day S health application without hiding the app from magisk, might because the rom is custom because on stock roms i think i couldnt open the app . But as the other guy said you can install a past version of S health
StonebridgeGr said:
.... But as the other guy said you can install a past version of S health...
Click to expand...
Click to collapse
I can't install an older S-healt version, if I try the result is: "app not installed".
I can only install a newer version.
I try Knox status checker also, and it shows 0x0.
Is very frustrating this thing.
blekmacigno said:
I can't install an older S-healt version, if I try the result is: "app not installed".
I can only install a newer version.
I try Knox status checker also, and it shows 0x0.
Is very frustrating this thing.
Click to expand...
Click to collapse
then try this guide .
http://www.**********.com/use-s-health-app-on-rooted-samsung-devices-with-tripped-knox/

Xposed?

In case you haven't seen the homepage there has been an updated Xposed framework for nougat.... Could we root and use flashfire??? PLEASE LET THIS WORK
RileyIssKing said:
In case you haven't seen the homepage there has been an updated Xposed framework for nougat.... Could we root and use flashfire??? PLEASE LET THIS WORK
Click to expand...
Click to collapse
Link me to homepage?
This would be pretty great
GroovinChip said:
This would be pretty great
Click to expand...
Click to collapse
Sorry it's the news page https://www.xda-developers.com/flashable-xposed-framework-android-nougat/
RileyIssKing said:
In case you haven't seen the homepage there has been an updated Xposed framework for nougat.... Could we root and use flashfire??? PLEASE LET THIS WORK
Click to expand...
Click to collapse
Sorry for the off topic question but can you or anyone else please link me to your root method (if in fact we can root with Nougat) I cant seem to find a definite answer. Im unlocked G935U, my carrier is AT&T. Currently on G935UUEU4BQF3
Thanks
KLit75 said:
Sorry for the off topic question but can you or anyone else please link me to your root method (if in fact we can root with Nougat) I cant seem to find a definite answer. Im unlocked G935U, my carrier is AT&T. Currently on G935UUEU4BQF3
Thanks
Click to expand...
Click to collapse
This is the only one that I know of that will root the Nougat version of the S7 Edge. It is a very long thread, and there is a lot of information that can help. I know it works as I tried it on my G935U at one time.
Anyway here's the link: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
freeop said:
This is the only one that I know of that will root the Nougat version of the S7 Edge. It is a very long thread, and there is a lot of information that can help. I know it works as I tried it on my G935U at one time.
Anyway here's the link: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Click to expand...
Click to collapse
Excellent! I wanted some confirmation from someone with the same phone (unlocked AT&T on N.)
Have you remained rooted since? I'm hearing mixed reports about performance and things stop working.) My primary concern though is our locked bootloaders. If we make changes that cause problems can we undo it? Like flashing the stock firmware? Thanks
KLit75 said:
Excellent! I wanted some confirmation from someone with the same phone (unlocked AT&T on N.)
Have you remained rooted since? I'm hearing mixed reports about performance and things stop working.) My primary concern though is our locked bootloaders. If we make changes that cause problems can we undo it? Like flashing the stock firmware? Thanks
Click to expand...
Click to collapse
Yes, I have remained rooted, but I ended up going back to stock G935A and then rooting again with that procedure. Personally, I was not getting the performance I was used to with the G935U as I was with the G935A with the root procedure.
Yes, there are some things that do not work with these eng.imgs that are being used to root the phones. There is NO Xposed for this one, Samsung Pay does not work, but I have been using Android Pay and it works just fine. As for the Bootloader, it is still LOCKED. There has not been any Unlocked bootloaders for the G935 or G930 so far and I don't think we will see it anytime soon.
As for Undoing, yes. There is a very simple way to go back to stock with Odin. In fact, about once a month, I return to stock just so I can get the latest security patch and then re-root my phone back to this way. I know it is somewhat of a pain, but with Titanium Back up I can get my phone back to running normally in a couple of hours.
Hope this helps...
It's not quite as fast, but if you are backing up and restoring to the same device, you can just use ADB. I still have a TiBu license, and use it on my Tab S2, but I have largely adapted to not having root on my S7 by taking advantage of basic ADB features.
jshamlet said:
It's not quite as fast, but if you are backing up and restoring to the same device, you can just use ADB. I still have a TiBu license, and use it on my Tab S2, but I have largely adapted to not having root on my S7 by taking advantage of basic ADB features.
Click to expand...
Click to collapse
Thanks will have to look into that...
Sent from my SAMSUNG-SM-G935A using Tapatalk
freeop said:
Thanks will have to look into that...
Sent from my SAMSUNG-SM-G935A using Tapatalk
Click to expand...
Click to collapse
freeop said:
Yes, I have remained rooted, but I ended up going back to stock G935A and then rooting again with that procedure. Personally, I was not getting the performance I was used to with the G935U as I was with the G935A with the root procedure.
Yes, there are some things that do not work with these eng.imgs that are being used to root the phones. There is NO Xposed for this one, Samsung Pay does not work, but I have been using Android Pay and it works just fine. As for the Bootloader, it is still LOCKED. There has not been any Unlocked bootloaders for the G935 or G930 so far and I don't think we will see it anytime soon.
As for Undoing, yes. There is a very simple way to go back to stock with Odin. In fact, about once a month, I return to stock just so I can get the latest security patch and then re-root my phone back to this way. I know it is somewhat of a pain, but with Titanium Back up I can get my phone back to running normally in a couple of hours.
Hope this helps...
Click to expand...
Click to collapse
Great info. Thanks!
One followup--when you say Xposed doesn't work, do you mean you tried the newest Nougat version that just got released? Or it never worked, not even on M?
KLit75 said:
Great info. Thanks!
One followup--when you say Xposed doesn't work, do you mean you tried the newest Nougat version that just got released? Or it never worked, not even on M?
Click to expand...
Click to collapse
What I meant was Xposed doesn't work on the current version of root using the eng.img. I have not tried using the NEW Xposed that is in THIS thread. I have looked at it but have not had a chance to run the zipped file and installing it. I know it works with MM as I had it working GREAT with MM and the eng.img with that version. I love Xposed and wish that was available for Nougat and N's root. I am keeping my fingers crossed that it will be fully implemented soon.
freeop said:
This is the only one that I know of that will root the Nougat version of the S7 Edge. It is a very long thread, and there is a lot of information that can help. I know it works as I tried it on my G935U at one time.
Anyway here's the link: https://forum.xda-developers.com/tm...eres-how-rooted-nougat-s7-edge-g935t-t3567502
Click to expand...
Click to collapse
I tried this 4 times and failed. The problem is it just keeps rebooting (about every 45 to 60 seconds) after I flash the eng boot img. Im never able to run adb commands. If I start from a clean slate I can't even make it past the setup screens to enable debugging.
I'm reaching out to you because you succeeded with the same model SM-G935U
So I'm just seeing if you have any insights. My phone should be the same as yours. Only difference is mine came with 7.0 preinstalled. Maybe an earlier firmware? But that doesn't make sense because people are, to my understanding, using the eng boot with recent firmware.
I'll repost in the root thread if I need to but thought I'd see if you have anything to offer. Thanks
KLit75 said:
I tried this 4 times and failed. The problem is it just keeps rebooting (about every 45 to 60 seconds) after I flash the eng boot img. Im never able to run adb commands. If I start from a clean slate I can't even make it past the setup screens to enable debugging.
I'm reaching out to you because you succeeded with the same model SM-G935U
So I'm just seeing if you have any insights. My phone should be the same as yours. Only difference is mine came with 7.0 preinstalled. Maybe an earlier firmware? But that doesn't make sense because people are, to my understanding, using the eng boot with recent firmware.
I'll repost in the root thread if I need to but thought I'd see if you have anything to offer. Thanks
Click to expand...
Click to collapse
I seem to remember the constant rebooting on the U-Firmware also. I too kept trying and it finally took. I think I would take the OTA from the server and try to install the eng.img with Odin. When you do this, does Odin give you any errors? Or does it succeed at the installation?
It has been a few months since I rooted the U-Firmware so not for sure what fixed the rooting process. Sorry I couldn't be more help...
freeop said:
I seem to remember the constant rebooting on the U-Firmware also. I too kept trying and it finally took. I think I would take the OTA from the server and try to install the eng.img with Odin. When you do this, does Odin give you any errors? Or does it succeed at the installation?
It has been a few months since I rooted the U-Firmware so not for sure what fixed the rooting process. Sorry I couldn't be more help...
Click to expand...
Click to collapse
Thanks. No Odin works perfectly whether I flash eng boot or stock.
I looked at the root guide for Sprint and the process is a lot more involved. I believe he boots to recovery twice and wipes cache plus factory reset twice. He also stresses to get the root.bat run quickly to avoid bootloop.
Might be worth a shot but the process of running Odin, getting back to stock and restoring all my data winds up being close to a few hours so It'd be very helpful to find someone with the same issue as me who was able to resolve it.

Need some help to fix 2 small problems after root

This isn't my first time rooting my Android device, I have done it multiple times and I know what to expect and what not to. I recently rooted my S7 Edge Tmo Nougat and I am having problems with the fingerprint sensor. It simply won't work and says there's been an error in the fingerprint sensor. I tried wiping the cache partition and I got not luck. Second of all, I knew this before I rooted, but is there anyway at all for me to be able to use Android Pay or Samsung pay again after rooting? It's probably impossible and I was expecting that, but I thought I ask anyway in case there's a way I haven't heard of. Obviously, Xposed and RootCloak isn't an option seeing how there isn't Xposed for Nougat yet.
Any help with my problems is highly appreciated. Thanks a lot guys.
About.. sensors.. i don't know.. about that apps.. if you change system to Official.. or you will just hide knox.. to 0x0.. it will work
ManXXXX said:
About.. sensors.. i don't know.. about that apps.. if you change system to Official.. or you will just hide knox.. to 0x0.. it will work
Click to expand...
Click to collapse
Lmao what. Care to clarify, please? I am not sure I understand.
Bumping this. I only need help with getting my fingerprint to work now. I was able to get AndroidPay to work by disabling super user in SuperSU before using it. Only AndroidPay though, not Samsung pay.
Try jrkruse root.bat Part of the script has fingerprint fix your able to choose from.

Categories

Resources