Database Develop

Back to Stock Rom but S-Health Not Working

Hello Good People,
I'm using a Exynos version of Note 8. Few month back I installed custom ROM into it but was having difficulty in using Banking Apps as it all says I'm using a rooted phone and can't use the app.
That's why I came back to Stock Rom , flashed stock rom using Odin and everything is fine even OTA updates but S health isn't working.
Please tell me how can I make S health Working without root.
* or use the banking apps with custom rom.
Thank you all.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

You will need root to fix Shealth.
Your banking apps will still probably detect root now as you have tripped Knox. Did you root with Magisk? and your bank apps still detect root?

I believe S Health is based off Knox, and once the Flag is tripped, you can not get Samsung Pay and S Health back.
Google fit will work

nubie said:
I believe S Health is based off Knox, and once the Flag is tripped, you can not get Samsung Pay and S Health back.
Google fit will work
Click to expand...
Click to collapse
Shealth can be fixed by editing the build.prob.

You need root to fix s health. If the banking app is working after you flash the stock rom, it probably detected the rooting app on your phone or detected the safely net failure before. Try using a custom ROM and rooting with magisk and hide it in the settings

shadow_hunter104 said:
You need root to fix s health. If the banking app is working after you flash the stock rom, it probably detected the rooting app on your phone or detected the safely net failure before. Try using a custom ROM and rooting with magisk and hide it in the settings
Click to expand...
Click to collapse
Thank you for replying. I rooted last time with magisk and used magisk hide still most of the banking apps detected root only one app worked.

stonedpsycho said:
Shealth can be fixed by editing the build.prob.
Click to expand...
Click to collapse
But for that, I need to root and with root, banking apps don't work. Finding a solution with what both I can use.
Thank you for your reply.

avi018 said:
Thank you for replying. I rooted last time with magisk and used magisk hide still most of the banking apps detected root only one app worked.
Click to expand...
Click to collapse
There's a module you can download to better hide magisk. It actually helped me. Use "MagiskHide Props Config" module

Finally working Both.
Installed TeamExyKings Rom and rooted with latest Magisk 17.1.
S health works great plus with magisk hide banking apps too.
Thank you all.

Magisk Hide

Magisk Hide doesn't seem to be working when it comes to my automobile's app, Uconnect. I'm rooted and now the Uconnect app states that I'm using an unsupported device. It worked before rooting.View attachment magisk_log_20181022_153305.log
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

tried clearing apps data?

kamilmirza said:
tried clearing apps data?
Click to expand...
Click to collapse
Yes. I even uninstalled, then reinstalled the Uconnect app.

destiple said:
Yes. I even uninstalled, then reinstalled the Uconnect app.
Click to expand...
Click to collapse
THIS great module might help :fingers-crossed:

Destiple, can you confirm whether MagiskHide Props Config, which kamilmirza referred you to, worked?
Alternately, did you find another solution to get Uconnect working?

If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).

Didgeridoohan said:
If you haven't already you're probably better off testing the brand new MagiskHide (rewritten from scratch) in the Canary builds (currently at build 18110).
Click to expand...
Click to collapse
That's very good to know. I'm nervous about running a Canary build on my normal phone, but I'll see if I can find a spare to test it on.
Will the new MagiskHide be on the next Magisk update, or is it several versions away from being in the stable build?

Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.

Coop9 said:
Try using the "Hide Magisk Manager" option in the settings. I was having the same problem, but after doing that and restarting I can use the Uconnect app again.
Click to expand...
Click to collapse
Good to know! I tried it - hiding the manager by itself wasn't enough. But once I added Uconnect to the apps being hidden, *then* the app finally loaded.
Of course, upon trying to log in, the app immediately crashes. Would that have anything to do with it being added to the MagiskHide list?

RootBeer library detects Magisk

I tried opening the Mastercard Pay with Rewards app, even with Magisk Hide, and it detected root.
In logcat I can see the following :
08-05 10:14:19.881 E/RootBeer(9758): b: a() [239] - com.topjohnwu.magisk ROOT management app detected!
So it seems that the app is using the RootBeer library which determines that the presence of the Magisk app is evidence enough of root. Is there anything I can do to avoid this? Could Magisk Hide be improved so the app can't tell Magisk itself is installed?

Have you looked in the Manager settings? There's an option to hide the Manager right there...

Download this script: https://github.com/Ingan121/UDSBypass/raw/master/bootudsbypass.sh
Put it in /data/adb/service.d
Give it permissions like:
0755
And uds detection is bypassed. Make sure you hide the rootbeer app in magisk hide and magisk manager is with a random name too. Here is a screenshot of how rootbeer won't detect root:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

And while we're at it, a whole bunch of other root hiding tips:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Didgeridoohan said:
Have you looked in the Manager settings? There's an option to hide the Manager right there...
Click to expand...
Click to collapse
Thanks! I was not aware of that option, and it was enough to bypass detection.

latest ianmacd magisk build passed rootbeerfresh detection out of the box.

Dims_Camper said:
latest ianmacd magisk build passed rootbeerfresh detection out of the box.
Click to expand...
Click to collapse
Just want to point out that it's safer to use the official Canary builds (that also pass all Rootbeer checks), since the unofficial snapshots are built from code that's possibly not ready for release.

Didgeridoohan said:
Just want to point out that it's safer to use the official Canary builds (that also pass all Rootbeer checks), since the unofficial snapshots are built from code that's possibly not ready for release.
Click to expand...
Click to collapse
I see, I thought only unofficial snapshots are the only one passed rootbeer checks. Thanks!

If I hide Magisk manager, will I be able to enter this application? And will the applications have access to the root?
Ok, work ok hide Magisk manager.

Question How to gain root access PLUS pass Safety Net

Hi All,
Received this phone a couple of weeks ago and have successfully unlocked the bootloader. I've also obtained root access, but have never been able to pass SafetyNet. The traditional methods do nothing. Have made various attempts using suggestions here on XDA, as well as searching Google, but each and every one results in an "Attestation Failed" message.
Some posts state to use the Magisk canary build and then hide Magisk as well as verifying SafetyNet. Unfortunately, the canary build doesn't provide an option to check the SafetyNet, nor is there any way to hide Magisk, nor hide any Google services/apps. The MagiskHide Props Config also has never worked for me either. Even when selecting Pixel 3A which supposedly was passing the old SafetyNet attestation method.
So, does anyone have or know of any root method that actually works correctly for the Redmi Note 10 Pro?
Cheers and Happy New Year,
Amy

AmyS9 said:
Hi All,
Received this phone a couple of weeks ago and have successfully unlocked the bootloader. I've also obtained root access, but have never been able to pass SafetyNet. The traditional methods do nothing. Have made various attempts using suggestions here on XDA, as well as searching Google, but each and every one results in an "Attestation Failed" message.
Some posts state to use the Magisk canary build and then hide Magisk as well as verifying SafetyNet. Unfortunately, the canary build doesn't provide an option to check the SafetyNet, nor is there any way to hide Magisk, nor hide any Google services/apps. The MagiskHide Props Config also has never worked for me either. Even when selecting Pixel 3A which supposedly was passing the old SafetyNet attestation method.
So, does anyone have or know of any root method that actually works correctly for the Redmi Note 10 Pro?
Cheers and Happy New Year,
Amy
Click to expand...
Click to collapse
Canary with zygisk and deny list additional flash magisks safetynefix (Google it) is still working
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Question Can’t make any google pay or wallet pay as unable to attach my card to it

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
any body facing such issue as can’t make any payment or after u try to attach your bank’s information, hereby it shows up in this scenario.
Any solution for this? Thanks guys!

Hi if you have unlocked bootloader.
Then root with magisk and flash saftynet fix and shamiko.
Open magisk setting and enable zygisk and add to black list:
GM's (Google play services), Google play, Google pay/wallet then wipe the data from all these apps and restart

MrScarl3t said:
Hi if you have unlocked bootloader.
Then root with magisk and flash saftynet fix and shamiko.
Open magisk setting and enable zygisk and add to black list:
GM's (Google play services), Google play, Google pay/wallet then wipe the data from all these apps and restart
Click to expand...
Click to collapse
Really don't need to do half of that. Just magisk, zygote, enforce list and add the universal safety net fix module.

That did not work for me. So ya

MrScarl3t said:
That did not work for me. So ya
Click to expand...
Click to collapse
clear the data from google pay

I suppose Google has changed their safetynet pass
You could find fix in this thread https://forum.xda-developers.com/t/discussion-google-pay-magisk-discussion-thread.3906703/page-139

helgi1507 said:
I suppose Google has changed their safetynet pass
You could find fix in this thread https://forum.xda-developers.com/t/discussion-google-pay-magisk-discussion-thread.3906703/page-139
Click to expand...
Click to collapse
I'm using this version and it's fine.
Zygisk and safety net fix applied..reboot after both fixes are applied then install gpay

MrScarl3t said:
But just as if we don’t do any root on it, shall I still by pass through the magisk? Because this are just ordinary use as never had any root before.
Unless kind of CN set which been flushed to global Rom also consider as rooting.
Hi if you have unlocked bootloader.
Then root with magisk and flash saftynet fix and shamiko.
Open magisk setting and enable zygisk and add to black list:
GM's (Google play services), Google play, Google pay/wallet then wipe the data from all these apps and restart
Click to expand...
Click to collapse

helgi1507 said:
I suppose Google has changed their safetynet pass
You could find fix in this thread https://forum.xda-developers.com/t/discussion-google-pay-magisk-discussion-thread.3906703/page-139
Click to expand...
Click to collapse
Seconded - that thread will be the best resource for finding help.