I am unable to run apps like "tez" , "bhim" on pixel experience rom installed in redmi note 3. Apps say that my phone is rooted but its not. I confirmed it by installing"root checker" app. My device is not rooted. is there any solution for this problem? is it because of permissive Selinux?
Magisk
arnabbandopadhyay said:
I am unable to run apps like "tez" , "bhim" on pixel experience rom installed in redmi note 3. Apps say that my phone is rooted but its not. I confirmed it by installing"root checker" app. My device is not rooted. is there any solution for this problem? is it because of permissive Selinux?
Click to expand...
Click to collapse
Install magisk 15.3 or whichever is latest and hide all the apps that don't require root in magisk hide, after that clear data of playstore and apps like tez etc. I used this method, it is working perfectly fine.
Hit thanks if a solution works. it will encourage us to answer queries.
yachandra said:
Install magisk 15.3 or whichever is latest and hide all the apps that don't require root in magisk hide, after that clear data of playstore and apps like tez etc. I used this method, it is working perfectly fine.
Hit thanks if a solution works. it will encourage us to answer queries.
Click to expand...
Click to collapse
I dont want to root my phone. Will magisk root my phone?
Easy & fast track method is just flash Magisk.zip and enjoy any app in any custom rom.
...but it will root your device!
arnabbandopadhyay said:
I dont want to root my phone. Will magisk root my phone?
Click to expand...
Click to collapse
Yes it will root your phone. But there won't be any root detection problems. I use snapchat, Tez etc on my phone
yachandra said:
Yes it will root your phone. But there won't be any root detection problems. I use snapchat, Tez etc on my phone
Click to expand...
Click to collapse
Is it safe to use banking apps on rooted device?
Yes it is safe to use banking apps on rooted device , if you're concerned about safety just don't install cracked apks or apps from outside other than playstore and use jio security or any such antivirus app
Simple method: you don't have to root the device. turn off play protect and find my device. You will get the OTP and you will be logged in. Then turn play protect and find my device on. (Tested only on Google pay. Don't know about BHIM).
May be because of unlocked bootloader
arnabbandopadhyay said:
i am unable to run apps like "tez" , "bhim" on pixel experience rom installed in redmi note 3. Apps say that my phone is rooted but its not. I confirmed it by installing"root checker" app. My device is not rooted. Is there any solution for this problem? Is it because of permissive selinux?
Click to expand...
Click to collapse
hi friend i was also faced the same issue , on my asus zenfone max pro m1 with pixel experience 10 plus and lineage os 16 and 17, using magisk couldnot help.
Related
It looks like it should with Magisk, but I can't seem to get it to work. I have pay hidden, using magisk 17.1 and passing safety net. It sticks at card verification. It says "verifying with bank", then kicks me to the payment screen where it says "verification needed". Clicking on that gives me a momentary waiting circle, but nothing else happens. I've tried it with 2 different cards. US998, RR oreo 8.1.
nola mike said:
It looks like it should with Magisk, but I can't seem to get it to work. I have pay hidden, using magisk 17.1 and passing safety net. It sticks at card verification. It says "verifying with bank", then kicks me to the payment screen where it says "verification needed". Clicking on that gives me a momentary waiting circle, but nothing else happens. I've tried it with 2 different cards. US998, RR oreo 8.1.
Click to expand...
Click to collapse
That's not an issue with Pay. If Magisk was being blocked by root/unlocked bootloader, you would get a message when you first fire up Pay that your phone can't be verified so "Google Pay can't run on this device".
Have you contacted your bank to make sure they support it? If it's not being verified with your bank, sounds like you need to call them. For the last few years, my bank didn't. It wasn't until this past year that they actually allowed it.
I'm not sure what the issue was. It wasn't with the bank(s). I was having the same issue with all the cards I tried. Eventually did a wipe and it worked.
nola mike said:
I'm not sure what the issue was. It wasn't with the bank(s). I was having the same issue with all the cards I tried. Eventually did a wipe and it worked.
Click to expand...
Click to collapse
Well that's weird. Glad it's working though! :good:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
If we want to reuse root features should we give phone permissions again ?
If we want to use Google pay again later should we re hide magisk and permissions ?
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Sent from my Moto G (4) using Tapatalk
Click to expand...
Click to collapse
Sent from my Redmi 4 using Tapatalk
Yes and No
cneeli78 said:
If we want to reuse root features should we give phone permissions again ?
If we want to use Google pay again later should we re hide magisk and permissions ?
Sent from my Redmi 4 using Tapatalk
Click to expand...
Click to collapse
Phone permissions have nothing to do with root features, I didn't exactly understand what do you mean by reuse root features but I don't recall any root solution app or framework asking for Phone Permission. If you are asking about granting phone permission to Google Play Services after Google Pay registration, you should do it, it's not recommended to deny phone permission to Google Play Services. And once you hide Magisk you don't need to change it's state as Magisk will continue to work as expected whether it's hidden or not.
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Click to expand...
Click to collapse
Yes it's working
JackFrost said:
After installing Google Pay, hide it using Magisk Hide, and Hide Magisk Manager in Magisk Settings. Then remove phone permission from Google Play Services and Play Store. Now you can register Pay on your rooted phone. After registration is complete, you should allow phone permission to Play Services and Play Store. This trick works always, I've tested with multiple custom roms with and without selinux enforcing.
Click to expand...
Click to collapse
thanks.its working
You are welcome
Arokia said:
Yes it's working
Click to expand...
Click to collapse
Karthik Arun said:
thanks.its working
Click to expand...
Click to collapse
There is a thanks button you can press if I could help you
JackFrost said:
There is a thanks button you can press if I could help you
Click to expand...
Click to collapse
Am I doing something wrong? I did everything but when I deny phone permissions I get a pop up saying its required to open google pay and cannot get passed that
raguilera510 said:
Am I doing something wrong? I did everything but when I deny phone permissions I get a pop up saying its required to open google pay and cannot get passed that
Click to expand...
Click to collapse
Did you by any chance remove phone permission from Google Pay app? You need to turn off telephone permission from Google Play Services and Google Play Store. Google Pay app needs phone permission to verify the phone number, don't turn off phone permission from Pay, do it for only play store and play services. Hope that helped.
Does not work
Once I renable telephone permission for Google Play Services, googlepay does not work anymore. Asks me to register and then I cannot register as I dont pass the security test. I am on lineage os 15.1
Non rooted lineageOS
I am a real newbie but i do use google pay a lot.
Will google pay just work on lineageOS that wasnt rooted or with magisk install, only with an unlocked bootloader. Or will i need extra work to do before i can use it?
kekekelasomot said:
I am a real newbie but i do use google pay a lot.
Will google pay just work on lineageOS that wasnt rooted or with magisk install, only with an unlocked bootloader. Or will i need extra work to do before i can use it?
Click to expand...
Click to collapse
Extra work? There's no extra work to install Magisk. It's part of the instructions when unlocking the bootloader and installing TWRP. Magisk Hide (part of Magisk Manager) lets Google Pay work.
When you unlock the bootloader and install TWRP (which you need to install ROMs), the next steps in the process include flashing three files IN TWRP: the no root checker, the no encryption and Magisk. I'm not clear why you would just stop short of finishing the process.
Unless you use Magisk Hide, simply unlocking the bootloader will cause Google Pay to then fail -- even without installing TWRP or a ROM.
Unlocked bootloader by itself -- without Magisk Hide (a part of Magisk) -- will cause Safety Net to fail. Google Pay will not work.
Why do you want Lineage OS without root? That's like owning a car with internal combustion engine, but refusing to put in gasoline. (or refusing to charge a Tesla.) You can do it, but to me it doesn't make sense.
You might as well stay on stock unrooted firmware.
I have stock rooted firmware. I'm not using any custom ROMs -- but at least I have root and my Magisk mods.
ChazzMatt said:
Extra work? There's no extra work to install Magisk. It's part of the instructions when unlocking the bootloader and installing TWRP. Magisk Hide (part of Magisk Manager) lets Google Pay work.
When you unlock the bootloader and install TWRP (which you need to install ROMs), the next steps in the process include flashing three files IN TWRP: the no root checker, the no encryption and Magisk. I'm not clear why you would just stop short of finishing the process.
Unless you use Magisk Hide, simply unlocking the bootloader will cause Google Pay to then fail -- even without installing TWRP or a ROM.
Unlocked bootloader by itself -- without Magisk Hide (a part of Magisk) -- will cause Safety Net to fail. Google Pay will not work.
Why do you want Lineage OS without root? That's like owning a car with internal combustion engine, but refusing to put in gasoline. (or refusing to charge a Tesla.) You can do it, but to me it doesn't make sense.
You might as well stay on stock unrooted firmware.
I have stock rooted firmware. I'm not using any custom ROMs -- but at least I have root and my Magisk mods.
Click to expand...
Click to collapse
Thank you. Just flash magisk and hide google pay using it. From what i under stand is i have root access+ unlocked bootloader+ google pay functionalities. And the reason not to root is just because i want the feel of stock android+some nice modification
Recently had this problem with G Pay also. Found where some just deleted 'cache' and 'data' from Google Play and Play Services. That worked for me too. Of course hide Magisk etc first.
AsItLies said:
Recently had this problem with G Pay also. Found where some just deleted 'cache' and 'data' from Google Play and Play Services. That worked for me too. Of course hide Magisk etc first.
Click to expand...
Click to collapse
Thank you. That's all I had to do to get it working for me.
Hi, I'm not able to get Google Pay working on my rooted V30. I unlocked bootloader and flashed TWRP, no checker, no encryption, using chazzdave's WTF tutorial. Now have Havoc installed. I have hidden root from play, play services, and pay. I've hidden magisk by scrambling APK. I've cleared cache and data of play, play services, and pay. I've revoked telephone permission for play services and play store, although I had to re-enable play services telephone permission during card setup because pay wouldn't go any further. But nothing. Just error message that root is enabled and cannot proceed.
One of my banking apps which didn't work on root is working after hiding from magisk, but no Google pay. Has something updated and a loophole been closed?
Thanks
Forsh said:
Hi, I'm not able to get Google Pay working on my rooted V30. I unlocked bootloader and flashed TWRP, no checker, no encryption, using chazzdave's WTF tutorial. Now have Havoc installed. I have hidden root from play, play services, and pay. I've hidden magisk by scrambling APK. I've cleared cache and data of play, play services, and pay. I've revoked telephone permission for play services and play store, although I had to re-enable play services telephone permission during card setup because pay wouldn't go any further. But nothing. Just error message that root is enabled and cannot proceed.
One of my banking apps which didn't work on root is working after hiding from magisk, but no Google pay. Has something updated and a loophole been closed?
Thanks
Click to expand...
Click to collapse
Use Magisk v19. I believe it's a beta at the moment
I've been struggling for a while now with getting a Romanian internet banking app (eToken BCR) to work on my Samsung Galaxy J3(2016) running RR-OS 5.8.5 // Magisk 17.1
I tried using several apps to hide the root and to uninstall magisk / remove root.
Basically the app tells me it can't run on rotted devices. I can't use it with or without root since custom rom :/
I guess there is one file containing the root check but the problem is I'm not even close to understanding coding and how the app works, I have no programing knowledge.
Can someone help me bypass this check? Or recreate the app without the root warning?
Thank you.
WaNt3D1012 said:
I've been struggling for a while now with getting a Romanian internet banking app (eToken BCR) to work on my Samsung Galaxy J3(2016) running RR-OS 5.8.5 // Magisk 17.1
I tried using several apps to hide the root and to uninstall magisk / remove root.
Basically the app tells me it can't run on rotted devices. I can't use it with or without root since custom rom :/
I guess there is one file containing the root check but the problem is I'm not even close to understanding coding and how the app works, I have no programing knowledge.
Can someone help me bypass this check? Or recreate the app without the root warning?
Thank you.
Click to expand...
Click to collapse
Magisk mask can be used to hide root
Alternatively, Xposed module "Root cloak" may also be helpful
Try one of these
Regards,
milkyway3
milkyway3 said:
Magisk mask can be used to hide root
Alternatively, Xposed module "Root cloak" may also be helpful
Try one of these
Regards,
milkyway3
Click to expand...
Click to collapse
I tried that
Doesn't work
WaNt3D1012 said:
I tried that
Doesn't work
Click to expand...
Click to collapse
Instead of installing the app on phone
Try installing on parallel space, 2 accounts, Dual space etc.
These all apps are available on play store
Do tell me if it works
Regards,
milkyway3
With latest Magisk (20.0) eToken doesn't detect root if you use Magisk Hide
I recently unlocked my bootloader and flashed the latest xiaomi.eu MIUI 12 stable rom for my pocophone and flashed magisk for root access as well. Everything was fine and dandy untill i attempted to open my banking app, it greeted me with a messege saying that i don't have minimum security even though my phone passes all safetynet tests, i don't know where the problem is and i wish to solve it without having to switch back to stock.
Please help.
Have u tried renaming magisk manager and hiding it from banking apps. Worked for me.
ScarAss**** said:
I recently unlocked my bootloader and flashed the latest xiaomi.eu MIUI 12 stable rom for my pocophone and flashed magisk for root access as well. Everything was fine and dandy untill i attempted to open my banking app, it greeted me with a messege saying that i don't have minimum security even though my phone passes all safetynet tests, i don't know where the problem is and i wish to solve it without having to switch back to stock.
Please help.
Click to expand...
Click to collapse
Use magisk hide and hide it from your banking apps. If that doesn't work, hide it from google apps too.
mecoromeo said:
Use magisk hide and hide it from your banking apps. If that doesn't work, hide it from google apps too.
Click to expand...
Click to collapse
Tried it but no luck, I even uninstalled magisk but it still didn't work.
sanjay0501 said:
Have u tried renaming magisk manager and hiding it from banking apps. Worked for me.
Click to expand...
Click to collapse
How do i rename magisk?
https://forum.xda-developers.com/7t-pro/help/10-3-2-device-meet-minimum-security-t4084467/page2
Try this. He downloaded shelter to setup a working space for his bank apps
Use island app
Apparently, my bank updated the app with a new feature that doesn't let me access it anymore, it says that the operating system is not supported, i use a custom rom(AEX) in my Redmi 4x, i believe that the rom is the problem, the root is being hidden with MagiskHide and i have no problems with SafetyNet, maybe i can change some parameter in build.prop to make it work? i did something similar to try to run Fortnite in my phone a while ago, any ideas on what parameters may be relevant to that?
It's a brazilian bank(Banco Inter)
Need Solution for this Problem as Well
I have the same problem.
The new app version 8.4.6 is not working while up till version 8.4.5 it was working just fine.
Their support is absolutely clueless on how to help, but as @Levyks said, apparently they are blocking custom roms now.
Is it possible to make the custom rom look as an original rom from manufacturer?
Same problem.
I'm with the same problem...
IMHO has nothing to do with fact whether it's a Custom ROM or a Stock ROM. Any app ( banking apps included ) easily can find out whether present Android OS got tampered or not.
Same problem any help? Can't use my bank app... WhatsApp also can detect I have a custom ROM, any solution?
Incomtus said:
Same problem any help? Can't use my bank app... WhatsApp also can detect I have a custom ROM, any solution?
Click to expand...
Click to collapse
Many apps like banking / payment apps today detect whether Android is got rooted or not: it's an easy for them to do so.
Same problem here in Lineage OS 18.1. My non-rooted device pass safetynet and CTS by default. But many Banking application had started detecting that I am using custom rom and don't open at all. Then I rooted my device with magisk and enabled 'magisk hide' but no success.
Hi! A solution that worked for me: use the renaming function in Magisk (you can find it in the Settings).
I had the same problem on a Redmi 4X, LOS 16, no working banking app even with Magisk hide. After renaming Magisk, I was able to log in and use it as intended. Also I left Magisk hide turned on.
My guess is that these kind of apps are looking specially for Magisk, and if it's detected, they just won't let you use them.
hi need help on dbs banking app detecting root starting from December 2021, i am unable to hide root from dbs digibank app tried magisk hide, xprivacylua. But gpay is working fine . Device htc u11 rooted with magisk 24.1
One more thing if I unroot my device dbs bank app works fine but gpay detecting unlocked bootloader and stopped working
Solved - zygisk and shamiko do the thing
raokashan said:
hi need help on dbs banking app detecting root starting from December 2021, i am unable to hide root from dbs digibank app tried magisk hide, xprivacylua. But gpay is working fine . Device htc u11 rooted with magisk 24.1
One more thing if I unroot my device dbs bank app works fine but gpay detecting unlocked bootloader and stopped working
Click to expand...
Click to collapse
Just try using Magisk brother or you can also try with Magisk 23.0, and just hide the app fully.. and also just change the name of Magisk app.
Already did that no use
raokashan said:
Already did that no use
Click to expand...
Click to collapse
Bypass DBS banking App
Resently BDS banking app(India) is updated.is there any modules to make that work...:rolleyes:
forum.xda-developers.com
Check this out
Tried every version of magisk from 20 to 24.1 no luck, someone got working for this help me
After June update Kotak Bank app also stopped working. It is detecting root even after Universal Safetynet Fix + Shamiko.
abhinavkumar842 said:
After June update Kotak Bank app also stopped working. It is detecting root even after Universal Safetynet Fix + Shamiko.
Click to expand...
Click to collapse
Yeah, cant say what they did within app or server side detecting root, but safety net is passed
raokashan said:
Yeah, cant say what they did within app or server side detecting root, but safety net is passed
Click to expand...
Click to collapse
They did something within the app, nothing server side to detect root. I am able to use older version of Kotak app and disabled auto update.
Can you share apk
raokashan said:
Can you share apk
Click to expand...
Click to collapse
Extracted using another app from older device, most likely it wont work but you can try after renaming it ofcourse. If it doesnt work you can always use net-banking instead of mobile-banking using phone browser, it is also quite secured with OTP codes & password.
[Discussion] Magisk - The Age of Zygisk.
This is a discussion and help thread for the newer versions of Magisk. The main goal of this thread is to help users migrate to Magisk v24+ SafetyNet Basic integrity Pass CTS profile match Pass Play Protect certification Device is certified...
forum.xda-developers.com
Tech = Spy-Biz said:
Extracted using another app from older device, most likely it wont work but you can try after renaming it ofcourse. If it doesnt work you can always use net-banking instead of mobile-banking.
Click to expand...
Click to collapse
Not working
raokashan said:
Not working
Click to expand...
Click to collapse
now check and see,
In my old phone J2 2018 A7 using Magisk 23 version 5.3.3 is working but under magisk hide the service [ (isolated) BlaBlaBla ] does not show as [ (isolated) Detect Root BlaBlaBla ] so when I install the same version 5.3.3 on A11 it shows [ (isolated) Detect Root BlaBlaBla ] under magisk hide. What that could mean is KB 5.3.3 version bank app is OPTIMIZING itself depending on android version installed in the device.
Version 534 working fine on my device after updating to 536 started detecting root, and i don't have a backup too, if anyone have 534 version share it
L
raokashan said:
Version 534 working fine on my device after updating to 536 started detecting root, and i don't have a backup too, if anyone have 534 version share it
Click to expand...
Click to collapse
Look by apkmirror
@Tech = Spy-Biz kbank-811 v537 got working with usnf modded version
raokashan said:
@Tech = Spy-Biz kbank-811 v537 got working with usnf modded version
Click to expand...
Click to collapse
Yup v537 working.
( FYI, I used Android 11 GSI + USNF MOD Version + Signature Spoofing Enabled + microG Gapps Module with microG-GooglePlayStore frozen + 6 Services from v537 disabled + I installed v537 from aurora ) So thats either a miracle or the KB app Dev had mercy on KB clients
ICICI iMobile from Aurora is working too .
RBL Mobank detects Developer Mode ON & also detects Aurora download & installed using package installer, so wont work unless google Account present which means have to keep that peeemp-azz playstore app inside the phone with a peemped-azz gmail account on the phone, I find all this unnecessary on part of the bank bcoz i know one of the older versions of KB App was working with Superuser permission from Magisk app .
If a bank app asks for SU permissions to work then thats a tradeoff the bank customers wouldnt really mind much bcoz there are plenty other possibly shady apps like SeFix App (malware flagged by Malwarebytes) using root privileges as well (I uninstalled it ofcourse).
I just wish the bank acts more maturedly with its customers coz its relation with its customers is a financial one not to spy on its customers which thankfully its not doing uptill now. By the word "Maturedly" I meant the banks should allow their customers to use rooted devices and should rather focus on other means to find out if security breach is happening real-time or offline remotely from a cloned SIM Card etc. For example -The banks can have some kind of software to check with their customers Mobile Carrier if there are multiple SIM cards registered under the same phone number, that would be better than to cause incovenience to its customers by not allowing them to use their bank app on rooted devices. It doesnt make any business sense unless google is paying/forcing the banks to make their customers use google accounts and Gapps. Thats really sick man! They can just create 2-step Verification or maybe 3 or 4 step verification for their banking apps instead of forcing clients to use google. Absolutely sold-out garbage peemping going on between the banks and google admob. I'm sick to the point of vomit looking at how LOW google is ready to stoop just to secure mainly one presumably sweet corner of the world and to make ships full of spy-money! What a PEEEEMP!
Will it work if you download an un-rooted version of VM's like VMOS, Virtual Android, etc.?