Database Info

Xposed Issue/Question

Hello all. I'll try to explain my issue with as much detail and hopefully somebody can help me.
Anyways I picked this phone up on sale on amazon and I have already unlocked the bootloader and am successfully rooted. Now I want to use Xposed. I have been trying to get it to work for 2 days now and I am fed up.
I downloaded the correct Xposed installer(SDK 24 v88.2) and it will somewhat work but then after a reboot It says it's installed but not active and it tells me to check the logs of which are blank. I am rooted the supersu way and have twrp installed.
I've read about some script I can put in the init.d folder or something like that but I cannot seem to get it to work.
I am on emui 5.0 with android 7.0.
Can someone please for the life of me help me get this to work?
I'm simply trying to use a module for my Snapchat called snaptools.
I know it's a lot to ask but can someone please help with a tutorial or a fix/instructions?

Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.

RedSkull23 said:
Unluckily I'm facing the same issue on my phone without having found a solution yet, both by official or systemless Xposed versions, the result is always the same as yours; Xposed framework looks installed but deactivated after some reboots, and it stays like that until i completely remove it and reinstall it again. Then, after other 2 reboots or something like that, it gets deactivated again and again. I already tried to look for a fix on official systemless Xposed thread as you can see here from an old post of mine https://forum.xda-developers.com/showpost.php?p=74439953&postcount=5740 but even trying other Xposed Installer versions (official, topjohnwu's, dvdandroid's one...) or without using Greenify4Magisk module, the issue persists. I thought I was the only one facing this lol. I'm rooted with Magisk, so the issue must be something else than the SU manager used. Can i ask you if you have Greenify installed on your device? I have to tighten the circle of possible causes of this, because it's getting me mad.
Click to expand...
Click to collapse
I do not have greenify installed unfortunately. I literally got this phone 2 days ago and I've never had this issue before.
I just uninstalled the SuperSU version and Installed the magisk version for root and then installed Xposed through the magisk manager and installed the modified Xposed installer apk that can see the systemless install. Xposed has survived a couple reboots and my modules are working but I fear that it will stop working as you stated before randomly. Have you tried it my way?
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.

patrick8996 said:
Flash magisk v14 through TWRP and then install Xposed SDK 24 systemless through the magisk manager. And then installed the modified APK for Xposed installer. It's at least made it further than the normal Xposed install.
Edit: Since I've posted this I have survived 2 more restarts. I feel like I'm playing Russian roulette Everytime I restart it but so far so good.
Click to expand...
Click to collapse
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...

RedSkull23 said:
Ok so greenify isn't a cause of this issue... yes i tried it already, read my post above... Both by official by rovo89, and systemless by topjohnwu (with related installer obviously) the issue persists. It works, like the other one, but after some reboots (i reboot my phone once a day, at least) i find it deactivated. Yeah you said well, it's a Russian roulette ahahah i tried every version of Xposed practically...
Click to expand...
Click to collapse
Hmm I'm still active but I haven't restarted since I posted. I'm wondering why there isn't a more detailed thread regarding this as it seems a lot of people use this phone.
Maybe you can try fresh with magisk and the modified Xposed installer for straight systemless. I've had a hell of a lot more luck this way than I have through the regular install. It's survived 5 reboots so far. Have you tried just a soft reboot inside the Xposed installer? I mean I know it's not a full restart but it may maintain Xposed and keep it active.

Maybe because only a limited set of people are facing this. And maybe only some devices suffer this. I tried both, fresh installations of normal Xposed / systemless Xposed, both didn't survived after 2 or 3 normal reboots. Yes I always rebooted by Xposed Installer when it was installed, even because i can preserve on/off button the longest i can this way, but sometimes a soft reboot isn't sufficient to apply some modifications, so i rarely used them. I daily rebooted with normal reboots. I'll try when new versions will be available at this point, i tried actual builds for 2 weeks encountering always this error so I'm not motivated on trying them again

Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future

RedSkull23 said:
Hey @patrick8996 did you tried latest systemless Xposed, V89? It surely works much better than previous one, V88.2, it has already survived 5 reboots while activating various modules compatibility is definitely increased with this update, I hope the issue won't represent in future
Click to expand...
Click to collapse
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.

patrick8996 said:
I just installed it last night and so far so good.
My lasts posts regarding v88.2 were proved incorrect because once I rebooted one more time it went back to not working. But this new update to v89 seems to be working. Hopefully all goes well.
Click to expand...
Click to collapse
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:

RedSkull23 said:
Yeah this build survives always reboots, even after recovery boots... I'd declare this issue solved :victory:
Click to expand...
Click to collapse
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.

patrick8996 said:
I've had a weird issue that my module's randomly stopped working. I had to disable them all in the Xposed app and restart and then enable them and restart again. Not sure if you've had this issue. But it's not that big of an issue because as long as Xposed stays active after a reboot it's a simple fix.
Click to expand...
Click to collapse
Never faced this. The framework keeps staying active actually

RedSkull23 said:
Never faced this. The framework keeps staying active actually
Click to expand...
Click to collapse
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.

patrick8996 said:
My Xposed stays active it's just my modules randomly stop working inside Xposed. So I have to disable all my modules reboot and then reenable them and reboot again.
I had issues last night with updating magisk. When I updated to v15 it took all my sound away on my device. I had to uninstall it and reflash v14 and everything went back to normal.
Click to expand...
Click to collapse
V15.1 should fix everything. V15.0 was messing up thousands of phones

RedSkull23 said:
V15.1 should fix everything. V15.0 was messing up thousands of phones
Click to expand...
Click to collapse
Ya I installed 15.1 and no longer have any issues. I'm happy all has been working for this long
Sent from my BLN-L24 using Tapatalk

Viper4android - not processing

Hey all,
Sorry if this has been covered elsewhere - I've searched a fair bit but found no definitive explanation..
Anyways I've installed viper4android 2.5.0.5 via magisk and it works initially. But soon enough it stops (processing=no)
I think I may need to flash it via twrp but I'm not sure ?
Has anyone got viper4android working on OP6 OOS 5.1.8? If so how?
Thanks!

Viper4Android works very good for me. Sometimes I have to reestablish a Bluetooth connection again as at the first connection no processing is active but in general viper works good.
I use the original Magisk module in the current version 1.6.9 and in addition "Audio Compatibility Patch"-Module in version 1.4.4.
I think this is all you need.

Just reboot.

hurray said:
Viper4Android works very good for me. Sometimes I have to reestablish a Bluetooth connection again as at the first connection no processing is active but in general viper works good.
I use the original Magisk module in the current version 1.6.9 and in addition "Audio Compatibility Patch"-Module in version 1.4.4.
I think this is all you need.
Click to expand...
Click to collapse
Thanks! I've installed this module and reinstalled viper4android afterwards. It's working again, but it always does after reinstalling. Hopefully it continues too. I'll update you guys!

I think the order of installation is important:
first viper and afterwards the audio compatibility module.
If your flash viper two times in a row it deinstalls itself (if I remember it correctly).
But I think you get it.

hurray said:
I think the order of installation is important:
first viper and afterwards the audio compatibility module.
If your flash viper two times in a row it deinstalls itself (if I remember it correctly).
But I think you get it.
Click to expand...
Click to collapse
Viper (as magisk module) works flawlessly also without the audio compatibility module for me; on spotify, soundcloud, power amp. Don´t know exactly, what the module is needed for. If "processing" says "no", clearing app data (and maybe reboot) helps - in worst case reinstalling the viper module.

Flying Fox said:
Viper (as magisk module) works flawlessly also without the audio compatibility module for me; on spotify, soundcloud, power amp. Don´t know exactly, what the module is needed for. If "processing" says "no", clearing app data (and maybe reboot) helps - in worst case reinstalling the viper module.
Click to expand...
Click to collapse
Which viper version and options are you using in magisk?
I've tried audio compatibility module but no help there. I turned on fx compatible mode in viper and that gets it to work and stay working!
However it silences my alarms. Which isn't ideal ?

debatingrooster said:
Thanks! I've installed this module and reinstalled viper4android afterwards. It's working again, but it always does after reinstalling. Hopefully it continues too. I'll update you guys!
Click to expand...
Click to collapse
Glad it worked for you if you find any issues in future please try it by turning off the Audio Tuner in Sounds & Vibration setting.

KrabKoyal said:
Glad it worked for you if you find any issues in future please try it by turning off the Audio Tuner in Sounds & Vibration setting.
Click to expand...
Click to collapse
It's stopped working again unfortunately. I might try flashing it in TWRP instead and see if that fixes it...

I am on 5.1.8 with viper I am running the no limits rom patch. No problems with viper on speaker and Bluetooth m

bassbounce said:
I am on 5.1.8 with viper I am running the no limits rom patch. No problems with viper on speaker and Bluetooth m
Click to expand...
Click to collapse
I suppose a custom rom is one way to solve it. I'd prefer OOS but...
Can anyone who's managed to get it working on stock OOS share with me the steps they took?

Hey man - I have it going on stock 5.1.8, I had problems with one of the modules in magisk, am using this one now after removing the old one - works well.

I am on OOS5.18 and used the version "Viper4Android FC Magisk V15", and I flashed it via TWRP.
But the "Proccesing" mode switches to "Off" after a while (5-10 min.). It is not consistent, you have to reboot, which makes no sense for me to reboot 10 times per day. There must be a different way to install it.....?????!!!!

Vivasanti said:
Hey man - I have it going on stock 5.1.8, I had problems with one of the modules in magisk, am using this one now after removing the old one - works well.
Click to expand...
Click to collapse
Thanks for the suggestion - still same problem as @mlara.particular unfortunately
mlara.particular said:
... the "Proccesing" mode switches to "Off" after a while (5-10 min.). It is not consistent...
Click to expand...
Click to collapse
This is weird... I don't understand why it would work for some people and not others...

I've been using the v4a material version from magisk, and it works great. I had to install the audio compatibility patch along with the audio modification library in order to get certain streaming apps to work correctly. You need to install the audio modification library if you install v4a and the audio compatibility patch.

debatingrooster said:
I suppose a custom rom is one way to solve it. I'd prefer OOS but...
Can anyone who's managed to get it working on stock OOS share with me the steps they took?
Click to expand...
Click to collapse
XXX no limits is no custom rom .. just a module in magisk and viper works great.

sakerhetz said:
XXX no limits is no custom rom .. just a module in magisk and viper works great.
Click to expand...
Click to collapse
I've xXx installed too and viper won't work for me. Starts ok but stopped processing and won't start again.
Sent from my ONEPLUS A6003 using Tapatalk

mossief1965 said:
I've xXx installed too and viper won't work for me. Starts ok but stopped processing and won't start again.
Click to expand...
Click to collapse
Experiencing the exact same issues here. Feel like I've tried everything, and now it wont even work after reboot :crying:

@Siggi and mossief.... you have installed magisk ???

sakerhetz said:
@Siggi and mossief.... you have installed magisk ???
Click to expand...
Click to collapse
Yes, of course.
Sent from my ONEPLUS A6003 using Tapatalk

OnePlus 6 Android 10 Beta 1:all sensor dead after root

Hi guys,
I have installed Android 10 Beta 1 on my op6, all the sensors stop working after the phone rooted.
I tried uninstall magisk,and all the sensors go back normal after a reboot.
Both magisk V19.4 and V20.0 had been tried.
Any idea?
Thank you very much.

You should reboot twice or a factory reset if the First solution doesnt work.

Q has sensors off feature, it might have been turned on by some mistake,
Go to developer options, quick settings developer tiles, tick "Sensors off" option, you'll see new unremovable tile, change it's status several times & see.
Good luck

Thank you all guys.
I reseted everything in twrp.
Root and sensors are all working now.
Thank you.

For me, also all sensors are not working after updating to Android 10 open beta 1, even without root.
I already tried flashing it again and cleared cache, but it didn't help.
Is there anything else I can try to get sensors working again without resetting everything?

Bleuzen said:
For me, also all sensors are not working after updating to Android 10 open beta 1, even without root.
I already tried flashing it again and cleared cache, but it didn't help.
Is there anything else I can try to get sensors working again without resetting everything?
Click to expand...
Click to collapse
For me, I have to reboot few times ( lost count of how many times I have rebooted ) until the sensor is working again.
It's not permanent fix though, another reboot could make the sensors stop working.

I've another problem that a smiley in the Notification only appears as "?". Is happens also in Chrome with some symbols

I fixed it by uninstalling Magisk via TWRP (there's now an easy guide to install it in Android 10), rebooting to system, check if the sensors are working again, and then reinstalling Magisk through TWRP again. If this happens again just re-do the procedure, an update will probably fix this.

How weird ô.O
Magisk v20, rebooted multiple times, nothing worked :|
I just reboot one more time while reading this post ... it works ...

Martuzki said:
I've another problem that a smiley in the Notification only appears as "?". Is happens also in Chrome with some symbols
Click to expand...
Click to collapse
The fonts problem.
The size of some fonts became 0 byte.
Try to reinstall the fonts or reinstall the rom .

stormPremier said:
How weird ô.O
Magisk v20, rebooted multiple times, nothing worked :|
I just reboot one more time while reading this post ... it works ...
Click to expand...
Click to collapse
It seems that the V20 is not compatible with android 10.
I installed v19.4 instead.

Kluxe Nobody said:
I fixed it by uninstalling Magisk via TWRP (there's now an easy guide to install it in Android 10), rebooting to system, check if the sensors are working again, and then reinstalling Magisk through TWRP again. If this happens again just re-do the procedure, an update will probably fix this.
Click to expand...
Click to collapse
Yes,after uninstall magisk all sensors are working again.
I need both root and sensor. So I try to reset the phone .

For all you people with the sensors issue. Install magisk 20.1 that'll fix this issue

thewhitehathacker said:
For all you people with the sensors issue. Install magisk 20.1 that'll fix this issue
Click to expand...
Click to collapse
Updated but not working here...

marcioafoliveira said:
Updated but not working here...
Click to expand...
Click to collapse
Try installing the rom again and try

Question Safetynet fix for Android 12?

So the latest 31.0810.1226.77-1.1.138-2203 update has introduced Android 12..and killed Safetynet bypass. The kdragon Safetynet fix 2.2.1 no longer works and the device doesn't pass basic attestation either. Is there a workaround that doesn't involve unrooting it or are we ****ed for the time being? Goddamn Magisk had to deprecate their Magiskhide and safetynet bypass features. /rant

Just re-flash magisk should be enough. Else re-flash safetynet-fix-v2.2.1.zip after magisk.
course if you havent got TWRP installed you would have to re-flash the boot.img to get magisk working again.

I usually do that after every firmware update, reflashing the patched boot.img, and I already had the latest kdrag0n safetynet fix (2.2.1 as of now). This time after restarting on android 12, safety net failed and the Google pay app reported that my device is no longer certified. Guess I'll try again. Wait..is there finally now a TWRP for ROG 5? I miss using it from my old 1+3.
Edit - didn't work.

There is no TWRP for A12.
You will have to make a new patched boot image for A12. Go to Magisk and patch boot.img taken from Payload.bin (Payload dunper required) and flash it. That will get you root back.
Then you can use the universal safety net fix zip inside magisk.

BakaValen said:
Then you can use the universal safety net fix zip inside magisk.
Click to expand...
Click to collapse
Getting root on 12 is not the problem. The kdrag0n safetynet fix stopped working after upgrading to 12. I have the latest Zygisk version 2.2.1 that was updated last December.

I am on A12 latest. Rooted with safetynet passed using the fix. You must be doing something wrong.
Explain your process

Did the same process I've followed for every system update - patch boot.img with the payload dumper and patch script as described in this forum before applying the update, and flash it afterwards. The safetynet fix that had already been installed and working under 11 stopped, and removing and reapplying it does nothing.

Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)

BakaValen said:
Flash version 2.2.1.
I'm telling you. There is a process not being done correctly.
I'm on the latest A12 for the 5s with safetynet pass.
Send screenshots of install process (magisk black screen bit)
Click to expand...
Click to collapse
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.

KaiserSnorezay said:
Yes, I'm using 2.2.1. The flashing process appears to have worked, as shown -
It's the latest Magisk with zygisk enabled. FWIW here's the result of running safetynet test also.
Click to expand...
Click to collapse
Are you running Shamiko withLSPosed/Xprivacy + blocking tracking for Goog Play Services and the relevant apps? Safetynetfix 2.2.1 alone is no longer a full solution whether you're on A11 or A12 and regardless of your Magisk version...

If you mean adding play services to the deny list, then yes. Got rid of xprivacylua as it didn't help. Used it to block reading identifiers and tracking for play services and other components, to no avail. Right now even the basic integrity test is failing.
Update - Installed Shamiko, disabled the 'enforce denylist' in Magisk so that it takes over the job and rebooted..and nothing different.

Passed here just fine... all you need is a clean magisk install, then...
hide the magisk app itself.
enable zygisk, reboot.
flash zygisk version of usf https://github.com/kdrag0n/safetynet-fix/releases/tag/v2.2.1
optionally: flash shamiko, reboot, then select play store and play service in deny list without enabling it.
check again in YASNAC, should pass now.

Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.

KaiserSnorezay said:
Don't know WTF is wrong this time, compared to every previous time it would just simply upgrade with no problems.
Installed this month's system update.
Uninstalled Magisk.
Patched the boot.img with Magisk, flashed it.
Reinstalled the Magisk apk. It was rooted, all my settings and modules showed up as usual.
Toggled zygisk to off, just to be sure, restarted, turned it back on, restarted.
NOTHING. Again the ****ing Safetynet fails.
Click to expand...
Click to collapse
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.

Strephon Alkhalikoi said:
Google changed something today, as Google Pay now detects root when I had used it just yesterday without issue. It appears the safetynet fix needs fixing.
Click to expand...
Click to collapse
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..

I noticed that if I add Google play services (all components) to the Magisk deny list, it doesn't persist after reboot. Could that be it? Is it unable to modify the system partition? I'm using Shamiko, with Magisk enforce deny list option disabled.

Andrologic said:
Re-check that all GPay sub components are added to your Shamiko deny list and Shamiko configured properly (i.e with Magisk's own deny disabled). Also check and ensure that tracking is blocked for Gpay in Xprivacy.
If you don't have any one of those installed - you need it to be completely covered. Even if you pass Saftynet. Safetynet Fix and Magisk hide alone won't cut it, at least not currently. Tough apps like banking and payment apps will detect you.
Many people skip one or more of these and run into frustration with root detection..
Click to expand...
Click to collapse
It may be a glitch, as GPay is currently not complaining about root when I pull up one of my stored cards. Regardless, I don't have Shamiko installed, but will look into it so long as it doesn't require Xposed or any of its derivatives.
EDIT: Confirmed to be a glitch. Not more than five minutes prior to this edit I used GPay without trouble.

Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.

KaiserSnorezay said:
Did some more testing, given I had to install the latest June firmware anyway. Fully removed Magisk (I hadn't done this earlier) and reinstalled, it passes. The culprit for failure turned out to be LSPosed. When enabled, it fails SafetyNet. I can manage without it but if anyone knows a workaround please do tell.
Click to expand...
Click to collapse
Same boat here. I got safetynet fix passed literally right after I disabled LSPosed. I glimpsed through the issues in LSPosed Github repo but they don't seem to be working on this.

I dont have any issues with safetynet.

Question Camera App crashing after installing magisk

After installing magisk on the phone using the boot.img patch method, the camera app crashes. Flashing the stock boot.img file fixes it though. I also noticed that the phone takes longer to boot now.

Never mind, it was a module that was causing the problem

Entity_909 said:
Never mind, it was a module that was causing the problem
Click to expand...
Click to collapse
Which module it is? Actually I am running AOSP 13 in my xiaomi phone and recently its camera is crashing. I have installed multiple modules lately.

The Rysul said:
Which module it is? Actually I am running AOSP 13 in my xiaomi phone and recently its camera is crashing. I have installed multiple modules lately.
Click to expand...
Click to collapse
I think the problem is that the module I installed actually changed the device model, so it showed up as another phone. This caused the camera app to crash