Related
running galaxy s5 here on rogers G900W8 all info in my signature.
rooted with twrp recovery installed ,
when I install Xposed framework and reboot my S Health app crashes " unfortunately S health has stopped"
I don't have any moduals installed , I think another post back in this thread said it had to do with the multi window but mine is off and nothing enabled on it. I attached my logs not much there but I have also uninstalled s health app cleared data and reinstalled it and xposed a few times to no avail
someone reported it had to do with the multi window but I don't use that feature and never turned it on.
just trying to make it so I am able to use an xposed or wanam and still be able to use s health without it crashing.
ex-28 said:
running galaxy s5 here on rogers G900W8 all info in my signature.
rooted with twrp recovery installed ,
when I install Xposed framework and reboot my S Health app crashes " unfortunately S health has stopped"
I don't have any moduals installed , I think another post back in this thread said it had to do with the multi window but mine is off and nothing enabled on it. I attached my logs not much there but I have also uninstalled s health app cleared data and reinstalled it and xposed a few times to no avail
someone reported it had to do with the multi window but I don't use that feature and never turned it on.
just trying to make it so I am able to use an xposed or wanam and still be able to use s health without it crashing.
Click to expand...
Click to collapse
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
jawmail said:
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
Click to expand...
Click to collapse
ok so its not just me , I need to figure out how to correct this I really need xposed.
I asked the same q on another thread , response was the following . but I don't understand it , as I don't use multi window at all hoping and preying someone else comes along to shed some light on this matter.
@rovo89
It seems that this module still tries to activate itself by manipulating the modules.list with root permissions. I just installed it myself and indeed that happened. I wasn't asked, not even informed, and it wasn't reflected in the Xposed UI. So it's basically operating like a root kit. That's especially bad when users suspect a bug in the framework because they seemingly didn't have any active modules.
Please solve this bug (or feature) as soon as possible. You can open the Xposed Installer directly in the modules section, but manipulating its files is not acceptable.
FYI, on my stock AT&T S5 I had S Health "go bad" a little bit, finishing building a Samsung ID and updating it from their store fixed it.
Don't know if that helps or not, just a data point.
ex-28 said:
ok so its not just me , I need to figure out how to correct this I really need xposed.
I asked the same q on another thread , response was the following . but I don't understand it , as I don't use multi window at all hoping and preying someone else comes along to shed some light on this matter.
rovo89
It seems that this module still tries to activate itself by manipulating the modules.list with root permissions. I just installed it myself and indeed that happened. I wasn't asked, not even informed, and it wasn't reflected in the Xposed UI. So it's basically operating like a root kit. That's especially bad when users suspect a bug in the framework because they seemingly didn't have any active modules.
Please solve this bug (or feature) as soon as possible. You can open the Xposed Installer directly in the modules section, but manipulating its files is not acceptable.
Click to expand...
Click to collapse
You forgot to use the @ to mention @rovo89.
Good to hear I'm not the only one either. S Health stopped opening from the exact same steps as OP.
I tried disabling and enabling the app, re-downloading the updates from Samsung but that didn't fix it.
Any information on why S Health crashes would be helpful.
Have you tried uninstalling the updates for s health? I'm stuck with the g900a for now so i don't have xposed yet, but when s health updated it would constantly error out until i got rid of the update.
Greycloak42 said:
Have you tried uninstalling the updates for s health? I'm stuck with the g900a for now so i don't have xposed yet, but when s health updated it would constantly error out until i got rid of the update.
Click to expand...
Click to collapse
I used TitaniumBackup to merge the update into the system. It didn't like that, caused my wifi to go haywire.
Moving the health app out to a user app fixed it though.
jawmail said:
Mine does the same. S Health crashes and does not work at all. No heart beat monitor for me. The only way to get S health back is to uninstall xposed then restore a backup and reinstall S Health
Click to expand...
Click to collapse
Xeio said:
I used TitaniumBackup to merge the update into the system. It didn't like that, caused my wifi to go haywire.
Moving the health app out to a user app fixed it though.
Click to expand...
Click to collapse
so you have s health running with xposed or wanam installed ?
i did not install Xposed framework but root the phone, after that the S health stopped running and popped up a failure notice, it might be due to root, I guess.
siyue78 said:
i did not install Xposed framework but root the phone, after that the S health stopped running and popped up a failure notice, it might be due to root, I guess.
Click to expand...
Click to collapse
I don't think root is the problem , as my phone and many others arerooted with twrp installed and shealth was working 100 % something to do with the xposed and / or wanam
divineiniquity said:
Good to hear I'm not the only one either. S Health stopped opening from the exact same steps as OP.
I tried disabling and enabling the app, re-downloading the updates from Samsung but that didn't fix it.
Any information on why S Health crashes would be helpful.
Click to expand...
Click to collapse
I had the same issue after installing xposed. I had to uninstall it and then convert s health to a user app and completely uninstall it (clearing data and/or removing updates didn't work for me). Also I removed updates from HealthService. After that I install S health again from Samsung store and is working again.
S Health is bugged as hell right now though.
Sent from my SM-G900H using XDA Premium 4 mobile app
mindol81 said:
I had the same issue after installing xposed. I had to uninstall it and then convert s health to a user app and completely uninstall it (clearing data and/or removing updates didn't work for me). Also I removed updates from HealthService. After that I install S health again from Samsung store and is working again.
S Health is bugged as hell right now though.
Sent from my SM-G900H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
after you reinstalled s health is it running ok now with xposed installed ? if so could you please give more details on the steps you took and it is just xposed or wanam you have
I haven't reinstall xposed yet... Getting SHealth to work again has been a pain. Better to wait for a fix.
Sent from my SM-G900H using XDA Premium 4 mobile app
mindol81 said:
I haven't reinstall xposed yet... Getting SHealth to work again has been a pain. Better to wait for a fix.
Sent from my SM-G900H using XDA Premium 4 mobile app
Click to expand...
Click to collapse
yah it took me a while to get s health working again as well , hoping for a fix soon.
Can confirm this on a Sprint S5. Rooted with chainfire autoroot and installed xposed and TWRP 2.7 and had S Health and Healthservices crashing like a drunk teenager. Uninstalled xposed and rebooted, S health now works. Guess I have to sit through Youtube ads for a while.
Ahh... Thought the problem was only for me. Hope @rovo89 could fix it soon.
may be can help to find the problem
hi everybody, i am a noob in android ect, BUT maybe it can help you : i am on i9500 omegaV20 perseus18, i modded my phones with root explorer, i add libs, perms, framework ect, modify my build prop /SM-G900F/kltexx/jfltexx , i did a lot of upgrade in samsung app store, AND I GOT S5 APPs WORK perfect, health widget work ect all works, and i got xposed ...
so to resume : i got S5 healths WORKING perfectly with xposed. hope it can help you.
Yup I also installed a different rom all working great now
Sent from my Sm-G900W8 using Tapatalk
I had the same concern, and after installing a new firmware on the SM-G900f .
I took the opportunity to not do the update shealth and securestorage..I can enjoy and wanam, Xposed
no problems with health
Hi,
Recently upgraded from the Note 3 to the S5 and have rooted.
I know their are loads of threads as to how to "fix" and run the Barclays App, i have tried and not suceeded.
Most recently i have tried the RootCloak which failed, and the nearest i have gotten to this was to uninstall the Barclays app and re-run. This was the steps given by Faz1980 on the HOW TO guide but for the s3.
Just thought their has to be someone out their that has the knowledge of root and to get a way around this?
Big high five if i can get this working as im sick and tired of logging in via a browser.
Cheers
If it helps;
S5
SM-G900F
4.4.2
hi all upgraded to lollipop and rooted was expecting banking app not to work but for some reason it still functioned., it then updated and stopped working so i reverted back to older one and was working again, was having issues with smart manager and have since updated android with the update to fix smart manager, now banking app wont work with any version, can i hide root on lollipop seems to be difficult.
nokiaman1978 said:
hi all upgraded to lollipop and rooted was expecting banking app not to work but for some reason it still functioned., it then updated and stopped working so i reverted back to older one and was working again, was having issues with smart manager and have since updated android with the update to fix smart manager, now banking app wont work with any version, can i hide root on lollipop seems to be difficult.
Click to expand...
Click to collapse
You can by using XPosed. There was some root hiding module available.
seem to have found a working solution, uninstall banking app, install hide my root, from the app hide su binary, install banking app set up banking app then go back into hide my root restore su binary restart phone and on mine at least now have working banking app.
short lived only worked for a short while.
What about the Temporary Unroot function in SuperSU?
That works for most other apps that have a form of root protection.
Sent From My Samsung Galaxy Note 3 N9005 Using Tapatalk
Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k
databoy2k said:
Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k
Click to expand...
Click to collapse
I've read this:
Downgraded to 6.0.1. stock. Started SHealth, and again upgraded to Nougat.
databoy2k said:
Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=70712537&postcount=16
databoy2k said:
Hey All:
I'm looking to splice various questions together.
I just reset my S7 to fully stock. Of course, I've tripped the e-fuse (Knox 0x1). My goal in resetting was to be able to use the newly-available (in Canada) Android Pay, which does in fact work. At least Google's fine with us resetting.
...but of course Samsung isn't, so now I can't use Samsung Health. Obviously I don't want to root, but it seems that I do need to edit build.prop (it looks like that is still a viable workaround, correct?). I also see @NilayNoob 's Superstock kernel method, but I'm almost convinced that this will trip SafetyNet and therefore I won't have Android Pay.
Is there any way to get Samsung Health AND Android Pay working at the same time on a Knox 0x1 device, with the knowledge that root is unimportant (i.e. if I can install and then uninstall it, same goes with TWRP, I'm fine with that)? What modifications can I make to my phone (e.g. TWRP) that won't trip SafetyNet?
Thanks.
--Databoy2k
Click to expand...
Click to collapse
You could flash a custom ROM with Magisk installed to have everything working including AndroidPay
Magisk Bypasses Safteynet
Im currently using Superstock Rom and its great ... Playing PokemonGo, using banking apps and AndroidPay on a daily basis.
(and yes Shealth works)
EasyAndroidPro said:
You could flash a custom ROM with Magisk installed to have everything working including AndroidPay
Magisk Bypasses Safteynet
Im currently using Superstock Rom and its great ... Playing PokemonGo, using banking apps and AndroidPay on a daily basis.
(and yes Shealth works)
Click to expand...
Click to collapse
I've had exactly zero luck with Magisk in the past, albeit that was before the proper W8 firmware came out so I was also fighting through issues of using improper firmwares (which have just never worked quite right for me; it seems our Canadian W8's aren't just a CSC change from the F). I was also having problems accessing my carrier's resources, etc. Maybe it's fixed, but my goal was to go back to 100% stock (or as close to as possible). I guess I'm just finally giving up my flashing addiction for the time being.
mashardpro said:
I've read this:
Downgraded to 6.0.1. stock. Started SHealth, and again upgraded to Nougat.
Click to expand...
Click to collapse
Yep worked. Thanks; anyone looking for the updated solution this is certainly one. It did suck to not be able to use Google's app restore function though (as my Nougat backup didn't register as usable on Marshmallow). But I'm up and running and SHealth is happily purring away.
webjunky said:
https://forum.xda-developers.com/showpost.php?p=70712537&postcount=16
Click to expand...
Click to collapse
Thanks, but this had to be crossed with the recommendation above. I was mostly looking to see if there had been an update that I missed.
I tried using Google Pay yesterday, but apparently my S7 Edge doesn't pass the Safetynet tests. Running stock is not an option because my tripped Knox breaks Samsung Health and I can't use my Gear S3. Safetynet is currently failing at CTSProfile.
Is there an app, kernel or rom that can fix these issues? I don't really need Knox to work (though SPay would be nice to have), I just want my Gear and GPay to work. Im running GalaxyRom, which is TouchWiz with some modifications to fix some Knox issues. Magisk is only used for root browser. Would rather not flash another ROM, but if there is one that fixes these issues its better than nothing.
Thanks
Magisk + Custom ROM
magisk v17.1
I'm using stock ROM with Magisk v17.1, and passing all safetynet checks. have you tried safetynet bypass apps?
vinegarr said:
I tried using Google Pay yesterday, but apparently my S7 Edge doesn't pass the Safetynet tests. Running stock is not an option because my tripped Knox breaks Samsung Health and I can't use my Gear S3. Safetynet is currently failing at CTSProfile.
Is there an app, kernel or rom that can fix these issues? I don't really need Knox to work (though SPay would be nice to have), I just want my Gear and GPay to work. Im running GalaxyRom, which is TouchWiz with some modifications to fix some Knox issues. Magisk is only used for root browser. Would rather not flash another ROM, but if there is one that fixes these issues its better than nothing.
Thanks
Click to expand...
Click to collapse
painx said:
Magisk + Custom ROM
Click to expand...
Click to collapse
"Custom ROM" is pretty vague. I have a custom TouchWiz ROM that doesn't work.
Try ' SecurityLogAgent Disable' on the Google Play store. I am using a stock ROM with the latest version of Magisk and passing all safety checks. I'm also using android pay and banking apps without an issue.
I was having the same problem. Bounced from one ROM to the next, but ultimately found my solution back where I started. I got SafetyNet passing with Samsung Health working on Sac23's s9 port. Unfortunately, he took down the rom so you can't download it from his thread. If you still wanna try it though, you can PM me and I'll share more info.
Rehvix said:
I was having the same problem. Bounced from one ROM to the next, but ultimately found my solution back where I started. I got SafetyNet passing with Samsung Health working on Sac23's s9 port. Unfortunately, he took down the rom so you can't download it from his thread. If you still wanna try it though, you can PM me and I'll share more info.
Click to expand...
Click to collapse
Thanks for the suggestion. I used Sac´s ROM before so I think I still have the ROM on my PC. I did flash back to stock, though. If I recall correctly, it had some weird issues (since its a port). Thanks, tho.
Rehvix said:
I was having the same problem. Bounced from one ROM to the next, but ultimately found my solution back where I started. I got SafetyNet passing with Samsung Health working on Sac23's s9 port. Unfortunately, he took down the rom so you can't download it from his thread. If you still wanna try it though, you can PM me and I'll share more info.
Click to expand...
Click to collapse
Thanks for the suggestion. I ended up flashing the BlackPearl S9 Port and Safetynet passes just fine. No issues with Knox either.