magisk modules install after popup restart - Android Q&A, Help & Troubleshooting

I get a reboot message after installing the Majisk module, is it okay to reboot all the apps I want at once after installing them?

Related

Xposed Installer problem/issue

Hi,
I have root acces, busybox installed and custom kernel with stock jellybean on my HOX+. I have installed Xposed Installer 2.4.1 and i have tried install/update framework button but app freezes and closes after some time. I can't install framework so I can't install any modules. What should I do?
EDIT: I have tried many times and after some time supersu popup showed and sked me to grant acces and then it worked but when I try to reboot from Xposed Installer it says that I don't have Access to do that.

How to run Tez App on rooted devices?

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

Xposed (v88) with Magisk

just install xposed latest version (v88) , installation done. boot up successful.
Modules enable in xposed but not working at all.
greenify and gravity tools keeps saying i did not enable modules in xposed.
Anyone have same problems?

The root permission request is no longer displayed [Magisk]

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?

Magisk Module not working (no /data/adb folder)

Hi guys,
I just rooted my bv9500 pro and am happy so far. One thing thou, if I instal modules in Magisk I get no error, after reboot they look activated but the modules have no effect on the system what so ever. For example Youtube Vanced didn't change anything, but when I installed it in TWRP it works.
The settings are, Magisk hide, and noCore only mode. When I looked up the drectory where he should load the modules (/data/adb/...) it doesn't exist. Anybody know where he loads the module and how to fix it?
Or can I install MagiskHide in TWRP as well?
Thaks for help!

Categories

Resources