Google has recently launched the Tez app for India, which supports payments from banks using UPI.
I tried installing it on my OnePlus X, rooted with xposed framework, Oxygen OS. It gives the message -
Tez can't be used on this device.
Click to expand...
Click to collapse
We've detected software running on your device that may not be secure.
Click to expand...
Click to collapse
I tried searching for solutions which generally end up with - Unroot your phone.
I tried RootCloak, doesn't help.
I don't want to unroot my phone, but I want to install this app.. it's getting quite popular among my friends.
So is there any other way to truly hide my root status for installing this app?
Root ur phone using magiskSU and hide root to tez by magisk hide.
Your device have to pass the safety net check for TEZ to work ,install safety net checker from playstore and test
On OOS it should work with Magisk SuHide option activated.
Remove Xposed forever. And would be better never ever use your rooted device for banking activity.
Unrooting or removing Xposed framework does not gives excuse to run Tez app. I have experienced. As your phone has the custom ROM, you cannot use Tez on your device. You have to completely install vendor's Official firmware on your device
i have no issue with magsik
On my OPO running COS 13.1.2, this is how I got it to work:
• Install Tez from PlayStore
•Disable the Xposed module within the Magisk Manager
•Goto Magisk Hide in Magisk Manager and select Tez to hide
•Disable the Xposed framework within the Xposed app
•Reboot phone
•Open Tez
I have found that once I successfully opened Tez and linked my profile and Bank Account, I could re-enable Xposed and still use Tez after rebooting
If the above process doesn't work for you, unroot your phone, and root it again with Magisk Manager, instead of flashing Chainfire's SuperSu
Follow simple steps -
1. Just uninstall xposed framework (No need to remove exposed installer)
2. Register tez / BHIM (dismiss root notifications)
3. Reinstall / update xposed framework.
I was facing issues during registration process only and im not using any third party app to hide root.
Now both are working fine.
Run Tez or any other secured apps on rooted device:-
I had the same problem with my rooted phone and magisk didn't do their part or we can say unsuccessful.
So I tried this and it works...?
Caution:- Follow step-by-step.
1. First download these three apps(in external card):- (Download all in recovery bootable zip )
1(a). SuperSu v2.82 RS3 (Recovery Flashable) :-
1(b). SuHide v1.09 Lite (Recovery Flashable) :-
1(c). SuperSu Config Aroma File v1.00 (Recovery Flashable) :-
2.Now root your device in TWRP mode
2(a). Select supersu config file and install it in "systemless SBIN mode" (modes showed when you start installation) and then leave all the other options default.
2(b). Install SuperSu into twrp boot mode.
2(c). Reboot once into android (or main screen) then again reboot it in recovery mode.
2(d). Install SuHide into twrp boot mode.
3. Reboot your device normally.
4. Open SuHide find the app which you want to use in rooted device and press right button (front of that app) till it changes to slash(/?️) eye or pirated eye.
5. Now use that app.
Note:- Succesfully Tested on MOTO G4 PLUS with given versions (if lastest version does not work use this versions only).
Kindly Check This Thread https://forum.xda-developers.com/apps/magisk/module-tez-hider-t3796567
Related
Right now,banking apps get clever and implemented more rigid security(they check this package name com.topjohnwu.magisk) even after you enable magisk hide...
But @topjohnwu, again helped...
if you are facing so, follow these steps:
1. clean flash/dirty flash ROM(works well with it otherwise also working)...
2. install magisk... and again install magisk from magisk app...
3. go to magisk hide and hide only banking apps otherwise magisk hide feature bricks.... please hide only those apps like - gpay(tez), phonepe, paytm and banking apps...
4. Tricky Part - go to magisk->settings -> replace Magisk manager (Replaces Magisk Manager with random package ) and wait till magisk do it... and it'll reboot app...
5. Voila... u did it...
6. for gpay - disable telephony(because using custom ROM) and register...
phonepe and all - normal way...
Source - https://forum.xda-developers.com/showpost.php?p=77014053&postcount=43
and remember deny root access if the app wants like paytm...
Bro thanks for the info ,it worked
Hi,
Even following this doesn't work with PhonePe, It simply shows white screen after I have put it in magisk hide and repackaged Magisk name. Any other alternatives? Also the 'Check SafetyNet' says the response is invalid when i try to check.
senthilrameshjv said:
Hi,
Even following this doesn't work with PhonePe, It simply shows white screen after I have put it in magisk hide and repackaged Magisk name. Any other alternatives? Also the 'Check SafetyNet' says the response is invalid when i try to check.
Click to expand...
Click to collapse
flash magisk using the app again...
happened to me once... i fixed by installing the magisk again...
I have the root with Magisk in Android 8.0. At first, the warning always came out asking if you wanted to grant root rights to the application that you just opened. However, this warning is no longer displayed, even though the configuration of Magisk Manager is configured in this way.
In the Magus Superuser section, I do not see any trace of the applications that I can not 'root'.
I have updated Magisk Manager, but the error continues. I also removed BusyBox, but the error continues.
I can not give root permission to any other application. But the mobile is rooted, since the first applications that I installed that require root continue to function normally. I can even deactivate the root and then activate it again.
Reinstalling the applications is not solved. With Dalvik and Caché wipe either.
That could be happening? How is it solved?
____
Magisk Manager has all the permissions of everything (memory, background, manual battery mode). I have tried to reinstall Magisk Manager and nothing.
Deactivating BusyBox (Magisk module) and Xposed and restarting still does not work.
Returning to install the Magisk image by TWRP or Fastboot is not fixed either.
I have removed all the fret that I had done to the phone (BusyBox, Xposed, root Magisk and boot modified for the root) and the problem has not been solved. I do not know what may be happening. I do not have other rare applications.
I have installed Device Control and the TWRP application. I have not gotten the root request to skip (although it has activated that option in Magisk Manager).
Definitely, it is not the fault of the new applications, which was the first question I wanted to solve.
Magisk version:
19.3 (19300)
And from Manager 7.2.0 (213), although I have also tried 7.3.2 (224).
The root is done with patching (via Magisk) of RAMDISK.IMG.
I understand that some applications are not compatible with systemless. But I'm not going any of the new ones that I'm trying. Interestingly, other applications compatible with Magisk (except those that installed the first days of the mobile) do not work either.
I have installed Magisk Manager 7.0.0 (and also 6.1.0), but the bug is still there. It seems that it does not depend on the APK.
As my Magisk file to root consists of a patch of RAMDISK.IMG created directly from Magisk Manager I do not know how to create one based on a lower version (for example, version 18.1). It only gives me the option to patch with the latest Magisk Manager version (if I have a lower one, it asks me to update the APK).
Whenever I generate the IMG of my patched RAMDISK.img it is based on 19.3.
How could I generate a patched IMG based on a lower version?
I have microG, not the GApps. Could that influence? Does Magisk need them?
Hi.
I have Xiaomi Redmi 4X and I want to control which contacts what app can access and hide/fake WiFi SSID/name.
I have found that XPrivacy can do that. ( android.stackexchange.com/questions/61318/is-there-a-contact-book-that-allows-partial-access-for-apps )
So now I got unlocked bootloader, TWRP, LineageOS (with google apps and root)
- Then I found that XPrivacy replaced by XPrivacyLua
-- To install XPrivacyLua I need Xposed framework which is replaced by EdXposed
--- To intsall EdXposed ( github.com/ElderDrivers/EdXposed ) I need Magisk v19.0+ (INSTALLED!)
Then it says on page (for latest EdXposed or Huawei devices, use our custom Magisk: Change Magisk update channel to this)
This is when everything went wrong. I have changed repo link and installed Magistik 20.3 using TWRP.
But after reboot Magistik Manager said last version is 20.1 (I assume repo was not updated when I installed 20.3)
So I attempt to install 20.1 using TWRP and there is no errors. But Magistik Manager keep saying that Magistik is not installed.
Also it says that Magistik Manager installed version is 7.5.1 but latest is 7.5.0 and when I try to install it android asks if I want to update it, I press install and after some loading it shows gray triangle with exclamation mark in it and says that app is not installed.
On which step I messed up or is there better way to choose which contacts which app can read and fake WiFi name/SSID?
Switched "Change Magisk update channel to this" back to default and successfully installed XPrivacyLua.
Problem solved.
Not sure how to add [SOLVED] to thread title.
Hola Amigos,
I have A Mido (2GB RAM) device with Superior OS (Phoniex,Android Q) Installed.I installed Magisk and whenever I flash any modules,
Magisk Crashes(Not Magisk Manager).Here's what I mean:The wallpaper I apply using Magisk get reset to default one.
Many Automatic Modules(Modules that start woring on boot) stop for 5-10 seconds and then work. App that I was using before the
crash also crashes.
It happens pretty frequently.
I installed Magisk like this:
Booted to TWRP
Wiped System,Dalvik,Vendor,Data,Cache
Formatted Data
Flashed Superior OS,Open Gapps Pico A10
Rebooted to System
After setting up Google
Rebooted to TWRP
Flashed Magisk 24.3.zip
Rebooted to System.
Installed Each Module one at a time and Rebooted,Then installed second module.....
Sometimes even of I don't install any module the Magisk Manager crashes.
The Modules that I use:
Google Sans Font System Lessly : https://www.pling.com/p/1457664/
MIUI Wallpaper and Akira Wallpaper(Live) : https://www.pling.com/p/1423749/
JamesDSP : https://zackptg5.com/downloads/jdsp_v4.4.zip
XDA Thread of (JamesDSP) (This is not a module): https://forum.xda-developers.com/android/apps-games/app-reformed-dsp-manager-t3607970
Naruto Sharingan BootAnimation for all devices : https://www.pling.com/p/1595951/
Godspeed Mode V X7 All devices : https://www.pling.com/p/1596710/
I am on stock kernel and TWRP 3.5.1
How can I fix these Crashes??
Also Fingerprint and auto rotate sensor are not working even if I uninstall Magisk,Whereas it works if I use UBPorts
Alpha V 1.1
Thanks for help!!!
I have same problem since I updated magisk to 26.1 and when I downgrade it to 25 or 24 stell same problem I tried to change magisk to kernel su the new root app and when I try to add one module at least It makes my app crash but it work only to give root access to any app I want and it is hidden from any app can detect root like bank apps this is crash log of one app of though apps https://bin.kv2.dev/~645360ede599576ea02c5490
And the screen shot the tree apps that crash when use modules
Mady_H said:
I have same problem since I updated magisk to 26.1 and when I downgrade it to 25 or 24 stell same problem I tried to change magisk to kernel su the new root app and when I try to add one module at least It makes my app crash but it work only to give root access to any app I want and it is hidden from any app can detect root like bank apps this is crash log of one app of though apps https://bin.kv2.dev/~645360ede599576ea02c5490
And the screen shot the tree apps that crash when use modules
Click to expand...
Click to collapse
Turns out James dsp and boot animation modules caused the crashes . Safety Net fix and shamiko did not cause the crash . Maybe you could try uninstalling unnecessary modules , btw which modules do you use ?
LolFlasherNoob said:
Turns out James dsp and boot animation modules caused the crashes . Safety Net fix and shamiko did not cause the crash . Maybe you could try uninstalling unnecessary modules , btw which modules do you use ?
Click to expand...
Click to collapse
Iam using ahamiko and safety net fix and hide my app list and ls posed I tried to add zygisk on kernelsu and when I did that it made my apps crash again and I tried to add module to install metrolla dailer phone to record calls it made my apps crash and ls posed zygisk didn't make any thing
So what is common with zygisk for kernelsu and jsp and boot animation
+
I will try to clean install the rom and root again to see what is going on and try to flash new rom to see if it is common in another rom or not
Mady_H said:
Iam using ahamiko and safety net fix and hide my app list and ls posed I tried to add zygisk on kernelsu and when I did that it made my apps crash again and I tried to add module to install metrolla dailer phone to record calls it made my apps crash and ls posed zygisk didn't make any thing
So what is common with zygisk for kernelsu and jsp and boot animation
+
I will try to clean install the rom and root again to see what is going on and try to flash new rom to see if it is common in another rom or not
Click to expand...
Click to collapse
Consider this guide .
Although it's for redmi note 11 , the rom flashing part is universally applicable to all devices.
[GUIDE] LATEST/UNIVERSAL FLASHING GUIDE FOR TWRP,OTHER RECOVERY AND ALL ROMS [Spes/Spesn] Redmi Note 11
: Combined four How To Guide threads into one. Post #2 - LATEST FLASHING GUIDE FOR TWRP AND OTHER RECOVERY [Spes/Spesn] Redmi Note 11[WINDOWS-Only] Post #3 - LATEST FLASHING GUIDE FOR TWRP AND OTHER RECOVERY [Spes/Spesn] Redmi...
forum.xda-developers.com
--->This is a working method as of May 2023 to have root on any rom version for redmi k20pro.
--->This will help you root and keep root hidden along with using lsposed modules.
--->These steps work on any device and any rom
You can find extra guides for the steps you dont understand by searching on xda forums. Some of these guides are linked to at the bottom of this post
Your bootloader needs to be unlocked to follow this guide. See link at bottom for guides to do the same.
****************************
I am not responsible for any data loss or damage. Follow at your own Risk
****************************
1. Install twrp or orangefox recovery on your phone.
2. Flash Magisk 25.2 (Version 26 has many issues. This version is better to use)
3. Reboot, install magisk apk(rename magisk.zip file to magisk.apk and install)
4. In magisk modules, install shamiko
5. In magisk modules, install safetynet 2.4.0
6. Add any app you want to hide root from in denylist of magisk. Additionally add Google play Services, Google play store, google services framework and google play protect to denylist(enable show system apps option in menu available on top right of denylist)
(IMP: Do not enable enforce denylist, Shamiko does this function)
7. If you have already logged into google play store and it shows device not certified in about section of play store -remove google account from phone and clear data of play store, play services, google services framework. Reboot amd try again. It will show certified status after about 10 minutes of logging in
8. Some custom roms may have device fingerprints which will get detected as custom rom. If that happens, use hide user debug and lineage props magisk module. Note: This version from github can only be flashed in Androidacy Fox Module Manager due to issue in zip packaging. Download this file which is just a properly repackaged version that can be flashed in any magisk manager.
Next install Reset Sensitive props magisk module. A combination of simply installing these modules will fix custom rom detection on any custom rom.(Example on opening whatsapp or GPay for first time)
Additional step(not necessary): Your rom may have additional build.prop entries that indicate a custom rom. Look for such build properties by opening build.prop in root browser on your device, then change any that have a custom rom name in them using magiskhideprops(Refer instructions to use magiskhideprops in the link)
9. Now, hide the magisk app in magisk app settings(set name to something like setting or app)
10. Freeze magisk manager app using link2sd/swift backup/ airfrozen or any other similar app. You can enable app when you need to install or disable modules or grant superuser access to new apps. You can also use Androidacy Fox MMM manager to find, install and remove magisk modules
_____________________________________________________________________________
Done, you can stop at this stage if you dont need lsposed.
Be warned that youw ill need to re-add any app you uninstall and reinstall in denylist.
If you want to use lsposed, continue with below steps after skipping step 10.
_____________________________________________________________________________
11. Install lsposed module 1.8.6 zygisk version
12. Install hide my appslist. Follow instructions in this link to learn how to correctly configure and hide magisk manager, lsposed and any other root apps you have.
You will need dataisolation enable magisk module if using android 10 and below for hidemyapplist to fully work.
13. Install Ruru and 'Play Integirty API Checker'.
Run Ruru and watch it pass all tests.(almost no banking app uses the level of detection used by ruru) Use play integrity api checker to check safetynet status - should pass basic integrity and cts profile.
Momo shows some messages like abnormal environement and TEE but that is ok.
Remember that you should enable denylist and Hide my applist for Ruru/Momo similar to how you enable for banking apps to hide.
Your root access is perfectly hidden now.
_____________________________________________________________________________
If you want to hide Developer Options_____________________________________________________________________________
You have a few options for this.
1. I personally turn usb debugging off in settings and use WADB app to enable wireless adb. I am using this on android 11 as other options dont fully hide or trigger xposed hook detection(which does not cause issues with the banking apps I have tested so far)This is not detected by any apps.
2. If on android 10 or lower, you can use hide user debug magisk module by huskydg which you can get from this telegram channel. I dont know if it can be linked here .
This effectively hides user debug without trigerring any root/xposed detection. Ruru may show 1 entry for usb debugging enabled but that is fine. If it doesnt work, it will show 2-3 detected entries for debugging mode.
I have uploaded the file here but dont know if it will last
3. If above options dont work,use devoptshide app, enable it in lsposed for apps you want to hide user debug from.This method will trigger xposed hook detection in Ruru but none of the banking apps i tested so far have an issue with that. Ruru may show 1 entry for usb debugging enabled but that is fine. If it doesnt work, it will show 2-3 detected entries for debugging mode.
4. I have not personally tested this but this module is an updated version of hide userdebug module by huskydg and it might help hide usb debugging on android 11 and up.You will have to try it yourself for now.I expect it to work.
GitHub - Magisk-Modules-Alt-Repo/ezme-nodebug: Change some props and "remove" LineageOS ones.
Change some props and "remove" LineageOS ones. Contribute to Magisk-Modules-Alt-Repo/ezme-nodebug development by creating an account on GitHub.
github.com
_____________________________________________________________________________
If an app detects root accidentally and refuses to run on your device again even if root is not detected again/ Spoof device ID for apps_____________________________________________________________________________
1. Now you need to use android faker lsposed module to randomize imei, max adress, android device id,hardware id.
Enable android faker in lsposed only for the app you want to change id for. Dont enable it for android system or android framework(Goal is to change id for a single app).Before doing these steps you need to clear data of play store, play services and google services framework, remove your google account from device settings and reboot. This will reset your gsf id.
This will give xposed hook detection in butbank apps dont seem to look for it.
2. If the above method does not work, use Xprivacylua. Enable for the app you want to change id, only use setting for device identifiers,use tracking, telephony data, analytics, get applications. Xprivacylua is not properly hidden even by Hide My Applist but apps dont look for it.So use this if above options does not work.
_____________________________________________________________________________
If you need to disable Widevine L1 DRM protection to use scrcpy screen mirroring etc
_____________________________________________________________________________
Install the liboemcryptodisabler module in magisk.Do note that widevine will drop to L3 but uninstallation brings it back to L1.
NOTE: Drm content cannot be mirrored on scrcpy if you are using android 12 or 13. Use roms with android version upto 11 if you need to watch drm protected content through scrcpy.(at your own risk. I do not advise illegal activity.)
Spoiler: liboemcryptodisabler
Magisk Modules Repository By Androidacy - Androidacy
This is the Androidacy Magisk Modules Repository, where you can search, browse, and download your favorite Magisk modules right now.
www.androidacy.com
Enjoy your properly hidden rooted device with all functionalities.
___________________________________________________________________________________________________________________________________
___________________________________________________________________________________________________________________________________
I have added a few useful posts by other members if you dont know how to do any of the above mentioned steps. Any others steps can be learned with guides from XDA -Use search
1. Simple guide to flashing on K20 Pro
His advice on not using orangefox for custom roms other than stock miui/ xiaomi.eu roms may be right, I have not tried it. Orangefox personally works best for me.
2. Guide to flashing custom roms, changing between miui and custom roms
3. Bootloader unlock, twrp, root instructions and rom links
4. Common issues with Redmi K20 Pro | fingerprint unlock | ghost touch | Dim display | sensor issues | bluetooth and calling
Confirmed working in May 2023.
Guide will be eventually updated with Magisk Delta which is better for root hiding
I am amazed how smoothly my update went from old magisk version that started having issues. I followed first part of this tutorial (without lsposed), I downloaded newest versions of everything (magisk 26.1 - had to directly install magisk in magisk too, Shamiko-v0.7.1-166-release, rest same as in tutorial) and it just worked. No more problems with old magisk. Deny list is working flawlessly!, safetynet is passing, Google Play Store says that device is certified. Thank you so much for this tutorial!
czacha994 said:
I am amazed how smoothly my update went from old magisk version that started having issues. I followed first part of this tutorial (without lsposed), I downloaded newest versions of everything (magisk 26.1 - had to directly install magisk in magisk too, Shamiko-v0.7.1-166-release, rest same as in tutorial) and it just worked. No more problems with old magisk. Deny list is working flawlessly!, safetynet is passing, Google Play Store says that device is certified. Thank you so much for this tutorial!
Click to expand...
Click to collapse
As of right now, magisk 25.2 works much better than magisk 26.1. You can continue to use it if you dont face any issues.
I believe I followed all the steps correctly including downgrading to magisk 25.2, the only step that I might not have followed correctly would be using hidemyapplist, but I'm getting CTS profile mismatch in microG safetynet attestation test. I have an LE2115 with lineageos 20 (specifically lineage-20.0-20230514-nightly-lemonade-signed.zip). I do get the "orange state" warning when I turn on my phone, I could make that go away by flashing an older version something (I forgot what but I've done it before) in TWRP but I wanted to avoid that since the only APPARENT effect is the orange state warning and I don't know if it will break later in LOS as they keep updating. I'd appreciate any help you could give me to fix this.
EDIT: just used magiskhidepropsconf and edit fingerprint and set it to htc exodus and now I pass all tests.