5T would rooting gain access to Samsung gear and control Gear 2 (R280) & Gear 360?
I've looked all over for a tutorial.
TIA.
Yes it should. I assume your problem is these apps don't show up for you in the app store or they say they aren't compatible with your device? I had that issue with my 6T and my Gear S3. If that is indeed the case you just need to root with Magisk and use:
Magisk Hide Props Module
That module will let you change your device fingerprint to a certified one or something else if necessary. I can test this theory tonight on a rooted 5T with this module if you know what apps you are looking for. (I know what apps are needed for my Gear S3)
Both Magisk and that Module are installed in TWRP. However that module is activated and run from a terminal emulator on the phone. Personally I use this one:
Terminal Emulator
Once running that type:
su <--Hit enter, hit ok when Magisk asks, this will give terminal emulator root.
Now type:
props <--This runs the module you will now get menus choose pick certified fingerprint. It should be pretty self explanatory from here. Any questions ask.
Normal Magsik stuff I recommend hiding Google stuff from Magisk and renaming it with a random name.
Yea, Tried using Wear but doesn't find the R-280 or Gear 360. I remember a modded Gear apk a while back but it didn't work non-root.
So I should root. Is there a good tutorial link that incorporates this props list in the process? Or what rom would be good for this?
I've fairly familiar with the rooting process but it's been a bit.
Thanks for your help.
I've found on several devices now, that sometimes, my cars, headsets, watches, may not pair if the device has been on for some time. A restart and all the sudden everything connects no issue. My Gear S3 is no exception. Restart the phone and my watch and all the sudden it finds it. Your location can be off (my is always off except when using navigation), but those apps do need location permission.
Your best bet is to use FunkWizard's Guide. It doesn't have the props module stuff in it, however once TWRP is installed and you flash magisk, it's just reboot once so magisk will be installed, fully, and then go back to recovery. Then flash the module, then flash busy box. You'll be good to go. (I did realize I left out an important piece of information, that module needs BusyBox to work. You can get that here at the bottom of this post. <-- That BusyBox installer is also installed in TWRP. )
As for ROMs I use Lineage on everything. The privacy guard is the big seller for LOS for me. However that props module works in OOS, on the 5T I used it until LOS came out, back when it was first released. Also used it on my 6T until LOS was fully working with my watch. So all this stuff should work fine in OOS if you want to stay "stock".
Hmm. Got a Havoc installed and Magisk 19. "props not found" when typed in terminal after giving SU permissions. Any ideas?
Also, Anyone know where to download the older Samsung Gear apks or what apps to use for pairing the devices I mentioned?
Thanks again!
djphooka said:
Hmm. Got a Havoc installed and Magisk 19. "props not found" when typed in terminal after giving SU permissions. Any ideas?
Also, Anyone know where to download the older Samsung Gear apks or what apps to use for pairing the devices I mentioned?
Thanks again!
Click to expand...
Click to collapse
When you go into Magisk go to Modules in the menu, does the MagiskHide PropsConfig and BusyBox appear under Modules? I would guess they do not if "props" does not work.
Have you ever used APK Mirror ? It is a very handy site sometimes. It's from Android Police, so at least it's not a completely unknown source. That's not to say you shouldn't use direct sources whenever possible.
OhioYJ said:
Yes it should. I assume your problem is these apps don't show up for you in the app store or they say they aren't compatible with your device?
Click to expand...
Click to collapse
What do I do now? I have Magisk running busybox and props.
Galaxy Wear doesn't find my watch. Isn't there an older version available that might?
djphooka said:
What do I do now? I have Magisk running busybox and props.
Galaxy Wear doesn't find my watch. Isn't there an older version available that might?
Click to expand...
Click to collapse
I don't know that version would help, but you can try other versions on ApkMirror if you want. I know even in stock form connecting my watch sometimes takes some persistence. Sometimes it takes rebooting both devices to get it recognized, sometimes it just a matter of going back and forth and scanning multiple times. It basically never finds it the first time. Been through it many of times, as you can't just reconnect a the watch after a clean install, it's always completely reset the watch and reconnect as a new device.
Related
Pixel 2 XL on 9.0
Bootloader Unlocked
TWRP Recovery
Rooted via Magisk 17.1
The Uconnect app for my Jeep no longer functions because the new version for Android 9.0 checks for an unlocked bootloader or root. When trying to login to the Uconnect app, I receive a popup that states I'm using an unapproved device. When contacting the developer, they claim that it's because my device is a security threat. I've tried Magisk Hide to no avail.
Any suggestions?
Same thing here too. I have an older S6 Edge + running a rooted Android 7.0 with Magisk 17.1. Magisk Hide doesnt fix it as well.
having this issue as well with the latest uConnect app. Pixel 2XL is rooted and unlocked. I loaded the latest stock firmware 9.0 and tried the uConnect app prior to rooting and it works on my end, but still a no-go once Magisk is installed. I even tried the magisk hide and the module that can alter prop to further hide magisk and no go. I think it may be that it is looking for root and is awfully good at finding it. If anyone can get this to work, would be great! I dont get why FCA is so worried about root. One would think that since we have to go through a VERY specific sequence to get root and unlock the bootloader, that we would have quite a grip on what goes on with our phones. Anyways, if someone comes up with something......
Uconnect is detecting Magisk Manager. You have to uninstall it in order for Uconnect to work.
Well that sucks
I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.
TechnovationLLC said:
I ran into something like this, but it was because I had an old version of the app. I uninstalled Uconnect completely and re-installed. After the re-install it was a new blue colored logo instead of the black one and has a different layout.
Not sure if this is the same problem, but figured I'd mention it.
Click to expand...
Click to collapse
And you are rooted?
CyberpodS2 said:
And you are rooted?
Click to expand...
Click to collapse
I tested root and non rooted. Both seemed to function fine for me. I initially thought rooted might be the issue for me, but it ended up being the old app.
Fresh install from play store gets me this.
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
Sadly, if I install an older version it prompts to update with no way around it... If anyone knows a version that works please post here.
Wondering if a logcat would help to pinpoint the issue and assist the magisk developer with a fix.
MrWhite0429 said:
Perhaps see if you can hunt down an older version apk and sideload that. That happens to me from time to time. Always has. Across different devices.
Click to expand...
Click to collapse
The old (black) version of the app doesn't work with 9.0
Very discouraging
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.
Viol8ter said:
I am using black version for now this is very discouraging though. The new app version would be nice working because the black looks as though they won't be updating it anymore.
Click to expand...
Click to collapse
Which version of Android are you on and which app version? Thanks!
lu270bro said:
Which version of Android are you on and which app version? Thanks!
Click to expand...
Click to collapse
I am on 8.0. Though I read somewhere someone said to hide the magisc manger with random name and it worked after clearing app cache. I'm happy and thankyou.
Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.
Machine318 said:
Same issue on my OnePlus 5T, the Black Icon version cannot connect to the network on Pie and the new Blue Icon is detecting something. I think it detects the unlocked bootloader, I tried to repackage Magisk Manager and it had no effect.
Click to expand...
Click to collapse
I have never been able to get it working on this phone since the blue icon change. Sucks...
why does a car/radio company care what a joke glad i dont have a car with unconnect
OK boys and girls. I think I found a fix. might not work for all of you, but I got the App to load and let me in.
I'm running the latest Pie version, Magisk 18.1 (Riru - Core v16, Riru - Ed Xposed) and XPrivacyLua (xposed module)
in XPrivacyLua for the Uconnect App, I restricted, Get Applications. Uconnect Logs in.
FIX:
1. Add Google Services to Magisk Hide (if you're on Magisk 18.1 use "su magiskhide --add com.google.android.gms" in terminal)
2. Add Google Pay and Google Services Framework to Magisk Hide
3. Go to data/data and rename com.google.android.gms to com.google.android.gms.bak for example (or delete it altogether, but backing up seems safer)
Reboot and do whatever you like in GPay, it should work now. That's all I've done. I don't think you need to reinstall Magisk.
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??
mine is fine
try re flash your rom
i42o said:
cts profile - true
basicintegrity - true
" couldnt finish setup to pay in stores
this phone can't be used to pay in stores. This is because it is rooted or altered in some way "
i dont get it... it passes but fails?????
can someone help me understand??
Click to expand...
Click to collapse
Long thread and a lot of moving parts, so work backwards on the thread. Personally, I am just waiting until a final and formal fix is found on stable Magisk and up to date Play apps.
https://forum.xda-developers.com/app...ssion-t3906703
My experience with this issue is I run GPay, go back to Magisk, safetynet fails on both.. So I force close Magisk, clear cache and data.. reboot. Open Magisk back up, Safetynet passes.. Gpay sets up fine. Sometimes you have to do this several times and it's a real pain but it's always worked for me..
this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
dipstik said:
this thread has info: https://forum.xda-developers.com/pixel-3-xl/how-to/march-security-update-t3907281
this worked for me:
1. Disable Google Pay/Find My Device as Device Administrators in Settings > Security & location > Device Administrators.
2. Search "Google Play services" in the Settings search bar.
3. Press the three dots and press "Uninstall previous updates".
4. Download this update - https://www.apkmirror.com/apk/google...-7-99-release/
Pick your needed edition (arm or arm64, etc.), download it and install it.
5. Disable Background data access for Google Play Services and Google Play in their respective App Info pages.
6. Download Google Pay from the Play Store.
7. Set up your cards. Enjoy!
Click to expand...
Click to collapse
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?
jbarcus81 said:
My way of fixing this issue is no longer working.. The second I start Gpay it breaks and detects root.. The link you gave for apkmirror .. I think it's missing info?
Click to expand...
Click to collapse
Get a 2.83 build. Xda shortens links and you lose them on copy text
dipstik said:
Get a 2.83 build. Xda shortens links and you lose them on copy text
Click to expand...
Click to collapse
I know.. it's ridiculous, appreciate the clarification!
I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.
rob42ert said:
I have the same problem, Gpay detects root.
After I've gained root using extracted boot.img from January's update and Magisk, it's impossible to hide the root.
Natwest bank app won't let me use fingerprint because it detects root, even Zoho mail detect root.
I am going to unroot, install march's update, then re-root using the same method, and if still doesn't work I will try what you described "dipstik"
I will let you know once it's done.
Click to expand...
Click to collapse
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.
This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
TonikJDK said:
I update this way:
Copy 18.1 Magisk to the phone.
Flash the factory image after editing out the -w so data is saved.
Boot to TWRP, but I do not install it.
Install the Magisk zip with TWRP.
That's it. I have never had a problem with GPay. I also have it hidden in Magisk, perhaps because I have always had it hidden I am ok.....dunno.
Click to expand...
Click to collapse
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.
sliding_billy said:
TonikJDK,
Have you added a card and actually used GPay at the terminal since this all started? I am in the same boat as you.
GPay is installed and opens fine on my wife's Pixel 3. Her device is running stock/rooted March rooted with 18.1 and has no TWRP. The only two things hidden are GPay and Play Store. The catch is that the card was already there. The new version of GPay showed up after clearing data/cache for Play Store and was loaded right after March install which decertified the design in Play Store forcing the data/cache clear. The card was always there. I have been hesitant to try loading a card or using this one at the terminal due to all of this.
My Pixel 3 XL also opens GPay fine, but like hers I have been hesitant to add a card or use it at the terminal. I am running dotOS (based on February), rooted with 18.1 with TWRP 3.2.3-3 fully installed. Same two relevant aps hidden, but in my case I didn't have to do anything to get the new version of GPay to show up since I didn't install March.
Click to expand...
Click to collapse
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.
TonikJDK said:
My cards were already in there before anyone started having all these problems and before the March update.. I use it all the time, it has never failed to work. I used it yesterday several times.
Click to expand...
Click to collapse
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.
sliding_billy said:
Thanks. That gives me some comfort in using the already loaded cards at least. I am not planning on loading any new cards or having to start from scratch any time soon. Seems like an already working GPay with a previously loaded card is OK.
Click to expand...
Click to collapse
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.
Bogega said:
It depends. My Gpay was opening fine and cards were loaded but payments didn't work, was getting error message that said I can't use payments because phone is rooted or altered in some other way.
Click to expand...
Click to collapse
And the doubt kicks back in, LOL. Luckily, I just carry a real card until this is formally solved (hopefully).
Bogega said:
This workaround worked for me with magisk 18.2 Canary build.
GPS 14.8.49
Google pay 2.82.231680166
Make sure to hide Google play services and Google services framework in Magisk hide.
https://forum.xda-developers.com/showpost.php?p=79028818&postcount=5
Click to expand...
Click to collapse
Sadly this method only works for a limited time.
Overnight GPS updates to version 15 by its own self and GP stops working.
I'm not sure I'm ready to to this procedure daily just for Google pay. For the time being I'll use my card until Magisk developer finds solution to this problem.
Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.
yeah nothing worked for me even when I uninstalled magisk and tried the steps above on stock. Ended up factory resetting. but thats the last move to do
TonikJDK said:
Well, I jinxed it a few posts back saying I was ok. It just told me no more when I used it.
Click to expand...
Click to collapse
Google Pay is a real asshole and doesn't let you know something is wrong until you actually tap to pay.
It's happened to me a couple of throughout my ownership of Pixels.
Hey folks, I have a note 10+ n975f and used to root all my older phones in past for freedom and a bit of a change to customising etc... Anyhow tried using magisk to disguised my banking apps before on other phones but them and a few others still won't work, the apps crash, tried a few rooms and all do the se thing, restored phone to factory and they all work. As its been years since I used to root my phones am I missing something? I've followed as many guided here as I can but can't seem to get around this issue.
possible the apps have learnt to detect it better, security is a cat and mouse game and firms are getting better at stopping people using their stuff on devices they don't want them to, you may have to look into certain apps for specific ways to bypass the detection. but chances are a lot of apps are now designed to detect the things blocking the detection of the phone being unlocked.
sad fact is if you want to use secure stuff on your phone the only really bulletproof option is to keep the phone locked.
Yea I know what you mean. Aww I used to have oneplus 6 and it's software was amazing but love the note for its size and camera etc but software just seems so bloated and it's got double the ram like
I know what you mean, but for me personally I just disable the stuff I don't need and use Lawnchair launcher to get the phone running like a Pixel device, but on the other hand the Samsung software can often give extra features that havent gone into base Android yet.
I had apps that wouldn't work because it detected root. So I did this: Magisk/Settings/Hide Magisk Manager. My apps worked after that.
Eagle 3 said:
I had apps that wouldn't work because it detected root. So I did this: Magisk/Settings/Hide Magisk Manager. My apps worked after that.
Click to expand...
Click to collapse
Thanks for the reply however not meaning to be rude, I stated I already tried Magisk in the original post. It doesn't work for some apps like banking apps etc.
cruisinbeatz said:
Thanks for the reply however not meaning to be rude, I stated I already tried Magisk in the original post. It doesn't work for some apps like banking apps etc.
Click to expand...
Click to collapse
You were very unclear about what you did in Magisk. Did you use Magisk Hide or Hide Magisk Manager?
Eagle 3 said:
You were very unclear about what you did in Magisk. Did you use Magisk Hide or Hide Magisk Manager?
Click to expand...
Click to collapse
I used Magisk Hide from what I recall. Opened it up, safenet etc was all green and good to go, it worked for snapchat etc but would not work on 3 of my banking apps, those are the only ones it wouldn't work on. From memory, I when I opened Magisk, I checked safety net was goo, it was. so went and hid root from each app I knew would look for safety net. The apps in question are Co-Operative Bank, Ulsterbank and Dansk (Mobile Bank in store) They will not open, they try, a quick flash on the screen and it returns back to home screen. Tried 3 different roms and they all done same thing.
cruisinbeatz said:
I used Magisk Hide from what I recall. Opened it up, safenet etc was all green and good to go, it worked for snapchat etc but would not work on 3 of my banking apps, those are the only ones it wouldn't work on. From memory, I when I opened Magisk, I checked safety net was goo, it was. so went and hid root from each app I knew would look for safety net. The apps in question are Co-Operative Bank, Ulsterbank and Dansk (Mobile Bank in store) They will not open, they try, a quick flash on the screen and it returns back to home screen. Tried 3 different roms and they all done same thing.
Click to expand...
Click to collapse
As I stated in my first reply to you, you need to Hide Magisk Manager. This is different than Magisk Hide. Go to Settings and select Hide Magisk Manager. You will get a popup for new name, leave it as Manager, tap OK.
Then open Manager, you will get a message to update Magisk Manager, tap OK.
Restart the phone. Your banking apps should work now.
I had the same problem as you in that the apps didn't work by just selecting the apps in Magisk Hide. They did after Hide Magisk Manager. So you have to do both.
Hi guys, so I heard the news and looks like the ECG is only enabled on Samsung phone.
I was wondering if in the near future you believe there will be a way to bypass it (unable to sideload with tizen 5) and sideload to a non samsung phone.
I just bought my active 2 and I wonder if there is a point to keep it and wait or return.
Thank you.
ShayMagen said:
Hi guys, so I heard the news and looks like the ECG is only enabled on Samsung phone.
I was wondering if in the near future you believe there will be a way to bypass it (unable to sideload with tizen 5) and sideload to a non samsung phone.
I just bought my active 2 and I wonder if there is a point to keep it and wait or return.
Thank you.
Click to expand...
Click to collapse
I just sent a nice long tweet to Samsung because of this. Thats kinda shady.
Can't say I'm surprised really... not gonna buy any samsung stuff from now on. I guess well have to wait and see.
Hopefully someone (probably addfree) will figure out a way to bypass that. For now, no dice. Really upsetting
Same old Samsung...?
Works on my Pixel 4a
I got this to work on my Pixel 4a. This is more difficult due to the usual sideloading methods not working...
Here is my post from the other thread about it. That thread was a bit hard to navigate for me (newcomer to the forum, hundreds of pages, and easier to follow with a Samsung device), so let me know if I missed anything key there. In summary you need to install a modified Samsung Health Monitor app since we can't access the galaxy app store. Similarly, you need to install a modified ECG app. With this method (I couldn't use the standard sdb install ecg.tpk) you need to generate a certificate specifically for your watch through the Tizen Studio application, and then use the Tizen Device Manager to push the install.
Here's a reddit thread with detailed steps and screenshots to install the necessary tools to generate a certificate, sign your ecg.tpk file with the new certificate, and install it to the watch.
Here's the link to the tool that will sign your certificate. It has instructions there, but you basically put an unsigned ecg.tpk into the "sign_me" folder, run the sign.bat file, and a signed ecg.tpk will be in your "install_me" folder. You then use the device manager (steps and pictures are part of the reddit post above) to connect to your watch, and install the ecg.tpk file.
I used this ECG.tpk from adfree: https://ufile.io/pzd1qmw0
I used this SHM .apk file from Caravana: https://ufile.io/d9yxknv1
Edit: to clarify to someone reading this, it doesn't work for blood pressure. It shows up in the samsung monitoring app on the phone but I can't get it installed on the watch. I believe this is because it isn't approved in the US.1
xgeetx said:
I got this to work on my Pixel 4a. This is more difficult due to the usual sideloading methods not working...
Here is my post from the other thread about it. That thread was a bit hard to navigate for me (newcomer to the forum, hundreds of pages, and easier to follow with a Samsung device), so let me know if I missed anything key there. In summary you need to install a modified Samsung Health Monitor app since we can't access the galaxy app store. Similarly, you need to install a modified ECG app. With this method (I couldn't use the standard sdb install ecg.tpk) you need to generate a certificate specifically for your watch through the Tizen Studio application, and then use the Tizen Device Manager to push the install.
Here's a reddit thread with detailed steps and screenshots to install the necessary tools to generate a certificate, sign your ecg.tpk file with the new certificate, and install it to the watch.
Here's the link to the tool that will sign your certificate. It has instructions there, but you basically put an unsigned ecg.tpk into the "sign_me" folder, run the sign.bat file, and a signed ecg.tpk will be in your "install_me" folder. You then use the device manager (steps and pictures are part of the reddit post above) to connect to your watch, and install the ecg.tpk file.
I used this ECG.tpk from adfree: https://ufile.io/pzd1qmw0
I used this SHM .apk file from Caravana: https://ufile.io/d9yxknv1
Edit: to clarify to someone reading this, it doesn't work for blood pressure. It shows up in the samsung monitoring app on the phone but I can't get it installed on the watch. I believe this is because it isn't approved in the US.1
Click to expand...
Click to collapse
Is there any risk of voiding warranty of the watch with this? And is there any risk of bricking the watch? Will it work for GW3 as well?
Thank you!
I think there is always some inherent risk in bricking devices or voiding warranties when you do this stuff, but it's not on the same level as doing something like a firmware flash.
So I was able to get the app on the watch. The only issue is that when I run the app on my rooted phone (S9 running lineage) I get an error saying it cant run on rooted phones (even though I have magisk hide enabled). Anyone know a way around this? Samsung health works just fine though (had to change my fingerprints to that of a oneplus to get it to work)
g33gz said:
So I was able to get the app on the watch. The only issue is that when I run the app on my rooted phone (S9 running lineage) I get an error saying it cant run on rooted phones (even though I have magisk hide enabled). Anyone know a way around this? Samsung health works just fine though (had to change my fingerprints to that of a oneplus to get it to work)
Click to expand...
Click to collapse
I have magisk hide enabled and it works well, try to uncheck and recheck the app in magisk hide.
ShayMagen said:
I have magisk hide enabled and it works well, try to uncheck and recheck the app in magisk hide.
Click to expand...
Click to collapse
Just gave it a go and I still have the same issue. I also have magisk hide enabled for the wearable plugin and the wearable app
g33gz said:
Just gave it a go and I still have the same issue. I also have magisk hide enabled for the wearable plugin and the wearable app
Click to expand...
Click to collapse
I have it enabled for Galaxy wearable, Samsung accessory service, samsung health, samsung health monitor, watch 2 active plugin.
ShayMagen said:
I have it enabled for Galaxy wearable, Samsung accessory service, samsung health, samsung health monitor, watch 2 active plugin.
Click to expand...
Click to collapse
Just did made sure to do all of these (was missing the active plugin and accessory service). Reinstalled magisk too. Same thing
g33gz said:
Just did made sure to do all of these (was missing the active plugin and accessory service). Reinstalled magisk too. Same thing
Click to expand...
Click to collapse
Magisk hide works fine for other apps? latest version? 20.4?
In magisk settings is Magisk Hide enabled?
ShayMagen said:
Magisk hide works fine for other apps? latest version? 20.4?
In magisk settings is Magisk Hide enabled?
Click to expand...
Click to collapse
Yup, it works for Samsung Health and other apps just fine. Also passes SafetyNet check
g33gz said:
Yup, it works for Samsung Health and other apps just fine. Also passes SafetyNet check
Click to expand...
Click to collapse
Not sure why is that, you using SHM1.1.0.175.mod4.apk (Located here https://ufile.io/d9yxknv1)? Maybe try to uncheck Magisk hide delete the app, reinstall the app and before you open it check magisk hide again and open app..
ShayMagen said:
Not sure why is that, you using SHM1.1.0.175.mod4.apk (Located here https://ufile.io/d9yxknv1)? Maybe try to uncheck Magisk hide delete the app, reinstall the app and before you open it check magisk hide again and open app..
Click to expand...
Click to collapse
Yup, thats the one I'm using. I went ahead and did the above and same thing IDK wtf...
NOTE: I wonder if Iineagos has anything to do with it?
g33gz said:
Yup, thats the one I'm using. I went ahead and did the above and same thing IDK wtf...
Click to expand...
Click to collapse
Ran out of ideas here. Try to uncheck and check and restart phone
ShayMagen said:
Ran out of ideas here. Try to uncheck and check and restart phone
Click to expand...
Click to collapse
Same thing. Looks like some people on reddit are having the same issue too
g33gz said:
Same thing. Looks like some people on reddit are having the same issue too
Click to expand...
Click to collapse
What version of magisk? Do you use custom rom? any other magisk modules installed? custom kernel?
Hi I rooted my tab s7+ sm-t970 but when I use magisk it give me a SafetyNetApi error it never passes can someone help me fix this. Thank you
I have the same exact issue.
Maybe could be our root?
homogamez said:
Maybe could be our root?
Click to expand...
Click to collapse
I guess its possible. It's been a long time since I've rooted something. When I open the Magisk app it says install next to magisk and the same for app. I hit install and it goes through the processes but nothing happens. There's no other area to add modules or anything. Can we go start over and do it again without breaking something? I'm lost. lol
It also happens on One Ace and N10
Hopefully next version will fix it
I can use banking app but not netflix. I get the red warning at boot up so I figure I gotta be rooted. Maybe I'll try adding TWRP
EDIT:
Went to backup using TWRP and said my device isn't rooted. I give up. lol
There's a discussion about this issue. There's an error on API key.
You can get Safety net check from play store and see the actual results
Let me look for this thread because I don’t see a way to fix
Safetynet api error
Hello looking for help as I can't figure out what's wrong. I've tried downloading the code on only wifi and only mobile data and I still get the api error. I'm not running any add blockers. Using magisk canary.
forum.xda-developers.com
I'm about to become your favorite person ever, everyone! I am currently passing SafetyNet after flashing the kdrag0n safetynet-fix to my Samsung Galaxy Tab S7+ SM-T970 and enabling the MagiskHide Props Config module in Magisk.
HOWEVER, as was the case with literally all of the stock-based ROMs for the Galaxy S8, it appears that there will still be issues with a select few apps. For example, you will get soft-banned from Snapchat every few days. Also, certain healthcare apps will still be able to detect root (likely all related to Knox, since a Pixel 5 rooted via the same methods will launch the same apps without issue).
All the best from your fellow tinkerer - Godless1
(P.S. I'm going to copy and paste this into its own thread for better visibility.)