Develop Bugs

Any way to hide root from specific apps?

Since rooting my 3XL, I've found several apps that detect root and will no longer work. I can live without them and work around it, but it's annoying. Does anyone know if there is a way to hide my root status from these apps? I've found mentions of some xposed modules that do this, but I'm apprehensive about trying them out quite yet.

kos26 said:
Since rooting my 3XL, I've found several apps that detect root and will no longer work. I can live without them and work around it, but it's annoying. Does anyone know if there is a way to hide my root status from these apps? I've found mentions of some xposed modules that do this, but I'm apprehensive about trying them out quite yet.
Click to expand...
Click to collapse
In Magisk look for Magic Hide. Open it up and check the box next to the app. You have to be on a newer canary bild for it to work.

TonikJDK said:
In Magisk look for Magic Hide. Open it up and check the box next to the app. You have to be on a newer canary bild for it to work.
Click to expand...
Click to collapse
Thanks. I'm not sure how to tell which build I'm using, I'm using whatever was in the Root thread https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
I'm assuming im not using the Canary build since I didn't see that module. Mind telling me how to check or update?

kos26 said:
Thanks. I'm not sure how to tell which build I'm using, I'm using whatever was in the Root thread https://www.xda-developers.com/google-pixel-3-unlock-bootloader-root-magisk/
I'm assuming im not using the Canary build since I didn't see that module. Mind telling me how to check or update?
Click to expand...
Click to collapse
You should be ok on that version. Give a try.

TonikJDK said:
You should be ok on that version. Give a try.
Click to expand...
Click to collapse
I don't see the module you referenced. There is Shellhide that says it's an alternative to Magisk Hide. In Magisk settings there is Magisk hide but it's just on or off, and was already on. So if that's it, it doesn't work for my purpose.

There are some apps that Magisk cannot hide from. This is my first Android phone that I have decided not to unlock the Bootloader on it. I am fine with stock, and don't need what root has to offer. Besides I like being able to use Android Pay and not have to play Cat and Mouse upgrading Magisk every time Android catches up to it.

kos26 said:
I don't see the module you referenced. There is Shellhide that says it's an alternative to Magisk Hide. In Magisk settings there is Magisk hide but it's just on or off, and was already on. So if that's it, it doesn't work for my purpose.
Click to expand...
Click to collapse
Yes, I meant inside Magisk. If you have the check box next to the app checked and it is still finding it you are probably out of luck. Some apps are not fixable.
You can also go in settings and hit hide Magisk manager. That sometimes helps.

TonikJDK said:
Yes, I meant inside Magisk. If you have the check box next to the app checked and it is still finding it you are probably out of luck. Some apps are not fixable.
You can also go in settings and hit hide Magisk manager. That sometimes helps.
Click to expand...
Click to collapse
Thanks for the info

GPay Can tell root now???

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.

5T would rooting gain access to Samsung gear and control Gear 2 (R280) & Gear 360?

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.

Google pay / etc

After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?

Magisk Hide is useless for Google Pay it'll still detect your phone if its still rooted. There's a magisk module called GPay SQlite it pretty much patches the part where google tries to detect if the device is rooted. I've been using this module for a long time and hasn't failed once on me, its definitely worth your time installing this one.
Here's the link to the forum which has the download on there.
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176

xSpartacusx said:
After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?
Click to expand...
Click to collapse
I have a Gear S3 and it seems to work well ONLY if you hide Magisk Manager and then use Magisk hide Samsung Pay. This is as of a couple weeks ago when all the bootloader unlock detection was happening. I haven't tried since then. You can fail CTS/Safetynet, but still get Samsung Pay to work.

Knxed_ said:
Magisk Hide is useless for Google Pay it'll still detect your phone if its still rooted. There's a magisk module called GPay SQlite it pretty much patches the part where google tries to detect if the device is rooted. I've been using this module for a long time and hasn't failed once on me, its definitely worth your time installing this one.
Here's the link to the forum which has the download on there.
https://forum.xda-developers.com/showpost.php?p=79643248&postcount=176
Click to expand...
Click to collapse
There's like 50 links. There which do I download?

xSpartacusx said:
After finally getting a ROM installed, I found out that Google pay won't work, along with Samsung pay in the Galaxy watches.
They know the system is rooted and what not I even tried to use magisk hide but it doesn't seem to work for these apps. Is there anyway I can restore this functionality?
Click to expand...
Click to collapse
Only reason why I have yet to root my Pixel 2 XL.

Ya im not sure how to fix GPay on this device!

xSpartacusx said:
There's like 50 links. There which do I download?
Click to expand...
Click to collapse
This link here is the most up to date version of the GPay patch, this will link you the download. You gotta flash it through recovery to get it working.
https://github.com/stylemessiah/GPay-SQLite-Fix/releases/download/v2.0/GPay.SQLite.Fix.v2.0.zip

Issues bypassing apps on rooted rom

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.