https://www.xda-developers.com/official-xposed-framework-android-nougat/
https://forum.xda-developers.com/showthread.php?t=3034811
https://forum.xda-developers.com/xposed/discussion-xposed-nougat-t3685687
Let's share what does/doesn't work
Since I made the post, it's only fair I go first.
On A2017G, stock and updated via OTA to 7.1, the flash was successful. The first boot took ~10 minutes. I will now start testing modules and update this post with what does/doesn't work.
Modules I tried so far:
LP: Works
Amplify Battery Extender: Works
Greenify: Does NOT work - The module is active, however, the app does not seem to be aware that it is.
-I'm looking for the old Youtube Background Playback module. It seems to have been pulled from the download list inside xposed manager. If anyone has a copy of it, it would be great to see if it's still working. The LP patch for background play stopped working for me on 3 different devices about 2 weeks ago.
Great!
Maybe a stupid question, but will installing xposed still break safetynet checks? That was the only benefit of running.g without xposed; aps like horizon / Ziggo Go worked, hate to have to do without it.
TIA,
Cheers,
/Cacti
Sent from my ZTE A2017G using XDA-Developers Legacy app
Amplify can't see wakelock or service...greenfy continue to tell me to activate the module. (I just set on the module and reboot many times)
UPDATE: other users with different device have the same problem, I think we need an update of these apps for working with the new version of exposed.
https://forum.xda-developers.com/xposed/discussion-xposed-nougat-t3685687
Running A2017UV1.1.0B32 (android 7.1.1) rooted by Magisk Version 14.0.
all was good but when installed xposed (SDK 25/API 25) something is wrong;
SafetyNet is faild at check and in Magisk , when pressing Menu->Superuser I get "Magisk Manager has stopped"
but root is working and Xposed modules are working.
mb0 said:
Running A2017UV1.1.0B32 (android 7.1.1) rooted by Magisk Version 14.0.
all was good but when installed xposed (SDK 25/API 25) something is wrong;
SafetyNet is faild at check and in Magisk , when pressing Menu->Superuser I get "Magisk Manager has stopped"
but root is working and Xposed modules are working.
Click to expand...
Click to collapse
I had the magisk FC too. Fixed it by switching to stable channel reinstalling both the zip and the launcher. Safety net is broken with magisk hide setting and the "universal safety net fix" module.
rzarectha said:
I had the magisk FC too. Fixed it by switching to stable channel reinstalling both the zip and the launcher. Safety net is broken with magisk hide setting and the "universal safety net fix" module.
Click to expand...
Click to collapse
Thanks. Not what I wanted to hear but still [emoji4]
Cheers,
/Cacti
Sent from my ZTE A2017G using XDA-Developers Legacy app
@rzarectha thank you, but it didn't help. even tried install beta version;
tried to complete uninstall and install again the zip and apk - it worked and no more FC.
Im also on B32 with Magisk, but currently running the official Xposed for Magisk. Should I use the Xposed uninstaller or just remove and uninstall the Magisk Xposed module before starting with the official Xposed process?
Regarding YouTube background play:
I found the .apk on their github page, it's in the first thread that mentions it being removed from the repo. I tested it and it works!
For whatever reason, I cannot get past a bootloop after installing via TWRP. Interestingly, I can install the unofficial module from back in August. I can uninstall that just fine, but reinstalling the proper one does nothing but bootloop. Anyone else having this problerm?
Could anyone try running Fate Grand Order?
After update to V88 the boot time is longer for 45-50 second on my A2017G with Stock 7.1.1B06. With inofficial V87 boots better
This is what I have setup so far. Crappalinks, YouTube Adaway, XInsta, all work. Greenify doesn't and neither did Amplify, not properly anyway. Also it does break Safety net. We'll have to wait for the Magisk Module
rzarectha said:
Since I made the post, it's only fair I go first.
On A2017G, stock and updated via OTA to 7.1, the flash was successful. The first boot took ~10 minutes. I will now start testing modules and update this post with what does/doesn't work.
Modules I tried so far:
LP: Works
Amplify Battery Extender: Works
Greenify: Does NOT work - The module is active, however, the app does not seem to be aware that it is.
-I'm looking for the old Youtube Background Playback module. It seems to have been pulled from the download list inside xposed manager. If anyone has a copy of it, it would be great to see if it's still working. The LP patch for background play stopped working for me on 3 different devices about 2 weeks ago.
Click to expand...
Click to collapse
why use Xposed for youtube adaway and background player when they make a separate app for that over here https://forum.xda-developers.com/android/apps-games/app-iytbp-injected-youtube-background-t3560900 I have been using this for a while now and it is great
reV17 said:
This is what I have setup so far. Crappalinks, YouTube Adaway, XInsta, all work. Greenify doesn't and neither did Amplify, not properly anyway. Also it does break Safety net. We'll have to wait for the Magisk Module
Click to expand...
Click to collapse
There is a magisk module on the repo but to my knowledge it still breaks safetynet
For those with issues with magisk and xposed, you can't use them both together, if you want to then you have to use the specific xposed magisk module here https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268 also flashing xposed regardless magisk or not its going to break safetynet no matter what. Will explain in that magisk xposed thread.
If someone got problems like me, heres my way i installed it successfully and get everything to work (Magisk!):
- disable xposed modules
- restart to recovery
- install Xposed v88.2 by topjohnwho (from xposed thread) via recovery
- reboot to system (first boot took ~9min)
- install Xposed Installer 3.1.2 for Magisk
- activate modules in xposed installer
- reboot phone and its done.
If you dont deactivate the xposed modules before flashing xposed, you maybe have to reinstall them and maybe set up everything new, if you cant save the settings for the modules. This was happening in my first try. In my second try i disabled them before and activated after flashing and dont have do setup every xposed module again.
A2017G with B06 and Magisk v14.2.
Can you use gravity box module on the stock rom? Is miflavor "close enough" to aosp to be compatible with mods made for that?
rzarectha said:
Can you use gravity box module on the stock rom? Is miflavor "close enough" to aosp to be compatible with mods made for that?
Click to expand...
Click to collapse
Yes. Not all is working, but center clock, battery mod in statusbar, RAM usage in recents, down-/uploadspeed in statusbar and some other things ... enough for me.
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?
Newest Magisk, I installthe module, reboot and is not being activated. Thus, adaware not working and getting a ton of ads in everything (apps and browser). Am I the only one?
Picture attached is after installing the module and rebooting.Tried removing, re-enabling, must have restarted a hundred times!
dreamdrake said:
Newest Magisk, I installthe module, reboot and is not being activated. Thus, adaware not working and getting a ton of ads in everything (apps and browser). Am I the only one?
Picture attached is after installing the module and rebooting.Tried removing, re-enabling, must have restarted a hundred times!
Click to expand...
Click to collapse
working fine for me on 11.0.4 havoc os 3.2
Thank you for the information..
Anyone else on the global stable rom? It was working before the update to the new rom and Magisk. What might have broken it?
Working fine on 11.0.4. miui and magisk canary 20,4
SOLVED
I set Magisk Core only to off in settings and everything works now. Thanks to all for your help and input.
Hi,
I love using Naptime app by Franco cause it installs a magisk module called GMS doze which enables battery optimization for Google Play Services.
Problem is this module only comes with Naptime app. So I want to have this module as a flashable zip, which would allow me to install without Naptime app.
I like the app but it doesn't work properly with my Android 11 device.
I know magisk modules are stored in data/adb/modules but they're not stored a zip there. So I can't get it out.
How can I get a magisk module out of magisk manager to have it as a flashable zip?
Thank you
By means of ADB you copy the module in question onto your desktop computer, where you then can insert it into a flashable ZIP it.
Alright Im new to XDA but not new to rooting. I'm hoping to get some answers with a glitch I have found. I have passed safety net no problems (I am rocking a oneplus 8 pro and its been rooted since I got it!) Until now! Magisk say api error , and other safety-net apps fail too! The weird thing is Netflix and my baking apps work no problems so I'm not to worried but it bugs the crap out of me! The troubleshooting steps I took was, I factory reset and rerooted (after hours of trying to find out what change) I went back to stock ROM and rerooted the phone and still cannot figure it out! I went ahead and put lineage 18.1 back on and hope I can find some answers later. Maybe I can get someone to check there safety net through magisk and see if its a me problem or a magisk problem. Thanks guy!
Hello!
I'm trying to make the eToken app from BCR work, but I can't find a solution.
Right now I am running Magisk 21.4 with Manager 8.0.7 with LineageOS 17.1 I have to specify that I am using an Xiaomi Mi A2.
If anyone has a solution for this, would youmind helping me.
Thank you!
Hey @HellFire_Wolf ,
Just fixed today try and follow below steps.
1.restore magisk manager with original package.
2.disable hide app.
3.reboot.
4.rehide magisk manager.
5.rehide app.
6.reboot.
It works for me now, OnePlus7T Pro
Now I see the comment.
But do you have a custom rom?
Atm I'm using dotOS
No, the stock one, rooted, and Magisk as a SU
Dh magisk hide works to hide the root on a strock android but for etoken to work it says you cant use root, unlock bootloader and use custom roms. So I hide bottloader and magisk, but what about the othwrs
I haven't used custom rom's, so can't help you more.
I sugest to get the RootBeerSample app from playstore then hide root in Magisk, then check what is detected.
Also double check that you hid magisk from system, not only root from apps.
It changes the app package to a random one and hides some specific checks that most apps use to check for Magisk.
Ik about magisk hide but didnt know about the app. I'll try it Thanks!