Develop Bugs

Xposed Framework Modules- Boot Stuck- Precautions! ( compatible list coming)

Greetings all..
I am working on the Not e 4 and run a large collection of Xposed mods
I have a Sprint Note 2, Note 3 and Note 4 and the 2&3 have never given me any issues with Xposed Framework Modules.
The frame work
Several are causing boot loops upon reboot.
The device will not boot into safemode- which is a huge pain if you did not do a backup in recovery.
I just wanted to remind everyone that if you install Xposed ( and ignore all of the "make sure you nandroid/ backup first messages) this time REALLY MAKE SURE YOU BACK UP /System at least before you activate mods.
I will post a list of the ones giving me issues shortly as I work out process of elimination.

Do you have an idea why my phone says "updating" after I install Xposed?
It's not stuck or anything but in the status bar it has a logo with a checkmark and I have no service. Am I supposed to freeze something?

I don't use many xposed modules and don't have boot loop issues with the ones I use. My problem is not all options in Wanam works. Like disabling sound waning when putting the volume too high. Hopefully the Wanam devs will fix that.

gfp11289 said:
Do you have an idea why my phone says "updating" after I install Xposed?
It's not stuck or anything but in the status bar it has a logo with a checkmark and I have no service. Am I supposed to freeze something?
Click to expand...
Click to collapse
If you turn off Software Updates from the ApplicationsManager you wont see it anymore.

xxSTARBUCKSxx said:
If you turn off Software Updates from the ApplicationsManager you wont see it anymore.
Click to expand...
Click to collapse
I turned off Software Uodates and it still comes up in the notification bar
I don't get any service either upon installing and restarting with xposed

When you installed xposed installer (assuming this was not from a titanium backup), it should have saved a zip file called, Xposed-Disabler-Recovery.zip to your sdcard or internal memory.
Install it in recovery and it will disable xposed framework so you can figure out which module is not working.
Here's a link:
http://www.datafilehost.com/d/ccb18d00

Deleted. Thanks. ^^^^^^^^

hermeticist said:
When you installed xposed installer (assuming this was not from a titanium backup), it should have saved a zip file called, Xposed-Disabler-Recovery.zip to your sdcard or internal memory.
Install it in recovery and it will disable xposed framework so you can figure out which module is not working.
Here's a link:
http://www.datafilehost.com/d/ccb18d00
Click to expand...
Click to collapse
I'll try it when I get home
I just install this in TWRP?

gfp11289 said:
I'll try it when I get home
I just install this in TWRP?
Click to expand...
Click to collapse
Yes. It removes xposed framework without uninstalling anything.
This way you can use the process of elimination add to which xposed module is screwing up your system:
Reinstall framework, turn one module on at a time, reboot, repeat.
If you are sure individual modules are not messing up, don't bother turning them off.

hermeticist said:
Yes. It removes xposed framework without uninstalling anything.
This way you can use the process of elimination add to which xposed module is screwing up your system:
Reinstall framework, turn one module on at a time, reboot, repeat.
If you are sure individual modules are not messing up, don't bother turning them off.
Click to expand...
Click to collapse
The thing is that I didn't have any modules on. I just installed it, updated it, rebooted, and I'm stuck with no service until after I uninstall it

Weird

Maybe I could try to flash Xposed in TWRP? If that's even possible..

gfp11289 said:
Maybe I could try to flash Xposed in TWRP? If that's even possible..
Click to expand...
Click to collapse
All you have to do is install the apk. Then once in Xposed, install the framework.
Id try uninstalling the framework, deleting the apk and download a fresh apk of xposed and start fresh. Dont associate TWRP with installing Xposed.

I think its working now. For some reason the update stays on my status bar for awhile before it turns off by itself. I tried to send myself some text messages last night and they took a long time to send, or just never sent at all. I have some decent status by my house so that wasn't an issue. I might've not given my phone enough time to boot up xposed or something, but regardless it's working now.
Being connected to wifi, does in anyway affect sending text messages while I'm on xposed? I barely had enough time to test it out when I was at home but driving around my city I was sending myself text messages and they seemed to go through okay.

Wanam Xposed
11/5/14 Wanam Xposed Module update available.

Drama!!! It is just Xposed Framework.

Xposed For A7 2017 nougat

Hello ! Is there a way to install xposed framework on A7 2017 nougat ?

Using the Magisk module with the Material Design XPSD worked perfectly on my A7(2017)
dudedude420 said:
Hello ! Is there a way to install xposed framework on A7 2017 nougat ?
Click to expand...
Click to collapse
Hello! I've never posted on XDA before but since I spent 6 hours yesterday trying to figure out a proper way to do just that so I might as well help.
This worked perfectly for my A720F/DS but it should also work with any A series nougat device. Notice that the MOST important part for this to work in other devices is choosing the correct xposed SDK according to your android system and CPU. Magisk is universal, no need to worry about download one specific for your device.
I'll start with a short summary in case you know a lot about the topic and then proceed to a step-by-step process.
Only the "systemless" AKA Magisk way works flawlessly, it's pretty simple when using the correct files. If you already have Magisk properly installed all you have to do is download the latest "Material Design Xposed Installer" and have active the 24 SDK module from the Magisk Manager app.
STEP 1
ROOT WITH MAGISK AND USE VERITY PATCH TO AVOID KNOX PROBLEMS
1. Put magisk v14.0 and dm-verity patch onto the sdcard in the phone.
Download the latest magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download the Verity Patch from here: https://forum.xda-developers.com/samsung-a-series-2017/help/how-to-install-magisk-v12-0-root-enable-t3611527 You might need this link later to use S Health...
2. Flash TWRP using Odin - You cand download both here https://forum.xda-developers.com/samsung-a-series-2017/development/xcc-t3591448
Important Note for Installing TWRP on A7 2017: Disable auto-reboot in Odin so that after flashing TWRP it says PASSED but instead of rebooting and Knox un-doing what you just did, you will now attempt to go to download mode again (Vol Down + Home + Power Button) but as soon as the screen goes black (meaning the phone is off) you will instead go to Recovery mode, simply pressing the Vol Up + Home + Power Button.
3. In recovery mode, allow modifications. and under wipe there should be a button to format data. You will need to do this to flash Magisk and dm verity, if not your cellphone will be stuck on a bootloop.
4. Flash Magisk, when the process is done simply go back and flash dm verity. (this order is important)
5. Boot the phone normally, it shouldn't take long but don't worry if it takes up to 5 minutes. (In my case, when only the SAMSUNG logo showed up it would always keep going to a normal boot, but when it said A7 and the other info it would be stuck on a boot loop).
6. Open Magisk Manager app and check if you can download and install modules (it needs storage permission first). It you manage to install modules properly then skip to the next step. If it says Process Error and you can't seem to install modules then make sure you give the app the proper permissions and then on the home page of the app select Install Directly (Recommended), I guess this installs Magisk again or somethins.. This seemed to finally make it work for me. A reboot is necessary.
STEP 2
INSTALL SYSTEMLESS XPOSED FRAMEWORK SDK24 MODULE FROM MAGISK ALONG WITH MATERIAL DESIGN XPOSED INSTALLER APK
1. Get the latest "Material Design Xposed Installer" from here, it shouldn't matter if you immediately install it or install it later (like I did)https://forum.xda-developers.com/xposed/material-design-xposed-installer-t3137758 (I'm 90% sure thats the one I used, if it doesn't work, try the one by Sr.CyanDroid)
2. In the Magisk Manager app, download and install the module XPOSED FRAMEWORK SDK24... It will tell you it installed correctly and reboot, you can double check by going into your Modules section after rebooting and seeing if it show up there... its a weird feeling but if it does show up that already means you successfully installed the xposed framework through Magisk.
3. Install (or just open if you previously installed it) the "Material Design Xposed Installer", it will either tell you it failed to detect Xposed or it will say its all perfect and you will be able to use Xposed normally. In case it says it failed, like it did to me, simply update the xposed app within itself. In my case, there was a notice at the bottom suggesting me to install the newest "Material Design Xposed Installer" and the problem was fixed immediately as I did it.
DONE
Keep in mind that by using this Magisk Method you are avoiding modifying the system partition, meaning its a lot less likely for you to brick your phone while trying different xposed files (apks are the only xposed files you need anyway). I hope this helps you and anyone else with this problem, keep in mind its 4am, and I'm really sleep so somethings MIGHT not be perfect. I also have a busy week coming up so I might not be able to respond any messages any time soon. Cheers!

Was looking exactly for this. Gonna try this in a day. Gonna post on the progress once done. Thanks!

If i did this, am i going to lose my warranty?
Sent from my [device_name] using XDA-Developers Legacy app

mido_many2000 said:
If i did this, am i going to lose my warranty?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Yes.

Will i lose my data ?

Specific Variant of Xposed works on Qualcomm's Perry ( APK Link in OP)

https://www.google.com/amp/s/forum....ed/unofficial-systemless-xposed-t3388268/amp/
The thing is.... I went to the app to get the program and Magisk wouldn't install the program on it's end. Took a shot and installed the apk (SDK 25), then installed the 88.1 version shown in the picture (now 88.2) rebooted and waited to "upgrade" itself.... But here it is plain as day. I'm not saying you may get it running on yours but it worked for me. Happy testing y'all,
SykkNyzz

And apparently Gravity Box for Nougat just came out 2 days ago at the time of this post.

Just ticked to center the time. Perfecto.

Reboot and such work as well

Nav Bar as well (note swapped buttons and added menu)

Even the Expanded Desktop works.

I can't get any modules to install in magisk on this phone. Tried systemless Xposed and nothing. How did you install it?
That looks like system install. Systemless usually says it like in this screenshot.
Did you install magisk with the zip in recovery, or modified boot.img? Systemless Xposed would be nice, hoping to get working on mine.

madbat99 said:
I can't get any modules to install in magisk on this phone. Tried systemless Xposed and nothing. How did you install it?
That looks like system install. Systemless usually says it like in this screenshot.
Did you install magisk with the zip in recovery, or modified boot.img? Systemless Xposed would be nice, hoping to get working on mine.
Click to expand...
Click to collapse
I couldn't use the Magisk even to this moment. I just used the apk listed above and did it that way

SykkNyzz said:
I couldn't use the Magisk even to this moment. I just used the apk listed above and did it that way
Click to expand...
Click to collapse
OK. I got system install working on mine too. Yours looks like system install too, not systemless. The xposed app downloads normal system install. You should change the name of the thread since it's not actually systemless. Just to avoid confusion.

madbat99 said:
OK. I got system install working on mine too. Yours looks like system install too, not systemless. The xposed app downloads normal system install. You should change the name of the thread since it's not actually systemless. Just to avoid confusion.
Click to expand...
Click to collapse
Well, the app itself from the website is stated as such. As where I can see where you are coming from. Thank you for the heads up.

SykkNyzz said:
Well, the app itself from the website is stated as such. As where I can see where you are coming from. Thank you for the heads up.
Click to expand...
Click to collapse
I can't get any magisk modules to work either, I was genuinely hoping you had it here. I've noticed you're pretty active in the forums for this phone.
Glad you showed xposed working, it helped me decide to try it.

Pixel 2 XL Rooted - Viper4Android v4.1, Magisk 19

Sorry for the noob question.
Running a Pixel 2XL - Pie April '19 Security Build, Magisk v19.0. When trying to install Viper4Android FX v4.1, I have tried seemingly every combination of options, but cannot get the 2.5.0.5 driver to install.
Both the material and regular app install and as a system or user app. Just the driver never gets installed?
Please advise if I've missed something obvious - thanks in advance!

Try flashing in TWRP.

miked2332 said:
Try flashing in TWRP.
Click to expand...
Click to collapse
working with magisk v 18.1 without problems

Latest Canary working also.

Google always tries to disable the root

@pepins: It's not that Google always tries to disable root, Play Protect always tries to disable the Material Design version of the V4A app.
@Switch Blade: When you tried updating it hung for a while on the prompt to update, then it threw up a message to reboot? After rebooting, did it prompt to install the driver again? I encountered that and it's probably a bug in the install script for the module. You need to head to the Magisk thread for the module and bring this up. That said, installing through TWRP, as recommended in the first reply to your post, is the way to go here.

Strephon Alkhalikoi said:
@pepins: It's not that Google always tries to disable root, Play Protect always tries to disable the Material Design version of the V4A app.
@Switch Blade: When you tried updating it hung for a while on the prompt to update, then it threw up a message to reboot? After rebooting, did it prompt to install the driver again? I encountered that and it's probably a bug in the install script for the module. You need to head to the Magisk thread for the module and bring this up. That said, installing through TWRP, as recommended in the first reply to your post, is the way to go here.
Click to expand...
Click to collapse
I get the update driver everytime on first install when if I have reset phone or reinstall Magisk and have to use recovery. After that I can update or reinstall in Magisk.
Sent from my Pixel 2 XL using XDA Labs

miked2332 said:
Try flashing in TWRP.
Click to expand...
Click to collapse
Tried flashing from TWRP - same issue, upon openning Viper4android app, tells me the driver isn't installed - then fails on IO.
Weird

Check Magisk see if viper is in SU. If not Go-to viper app info clear data and turn storage off. Sometimes this make Magisk ask for SU for viper. Makes it work sometimes.
I had to use this method for a while to get it to work. Also I have musicfx disabled in apps. Had to do that on my Nexus 6 and just kept on doing it. Uninstall Viper reboot.
Install Viperfx don't reboot
Install audio modification reboot.
It can be done in TWRP also. If you reflash either of those a second time it uninstalls them if you didn't know.
I'm not a developer I pretty much just mess with these things until they work for me.
Sent from my Pixel 2 XL using XDA Labs

miked2332 said:
I get the update driver everytime on first install when if I have reset phone or reinstall Magisk and have to use recovery. After that I can update or reinstall in Magisk.
Click to expand...
Click to collapse
Of the three devices I installed V4A on the P2XL was the only one to have an issue. Normally it's not an issue, so what changed this time I don't know. Anyway, the other two devices, a Moto X Pure and a Galaxy S4, installed the driver through Magisk without difficulty. As mentioned, flashing V4A in TWRP on the P2XL resolved things.

Strephon Alkhalikoi said:
Of the three devices I installed V4A on the P2XL was the only one to have an issue. Normally it's not an issue, so what changed this time I don't know. Anyway, the other two devices, a Moto X Pure and a Galaxy S4, installed the driver through Magisk without difficulty. As mentioned, flashing V4A in TWRP on the P2XL resolved things.
Click to expand...
Click to collapse
I tried just installing opposite features today didn't work. On my phone it goes 2.5.0.5. Old Style, System App, and after the update I have to choose no on the last. It's my 1 reason for using root.
Sent from my Pixel 2 XL using XDA Labs

Try SeLinux Permissive apk

This happens every now and then for me; especially if I'm updating V4A after being on an older version for a long time...
I've forgotten where I've seen/read it, but many times you can't simply update it and/or install the driver from the app. What I end up doing (forced to do) is to uninstall the app (from within Magisk), reboot, and re-download/re-install it (searching for module from within Magisk app) and it should (usually) install the driver again...I usually install it by selecting the 2.5.0.5 and "material" version and as a "system app"...
I dunno why...but this seems to do the trick, but I have to do it frequently now and then...

I use Magisk module that works for speakers, but not with headset.It happens only to me?

miked2332 said:
Check Magisk see if viper is in SU. If not Go-to viper app info clear data and turn storage off. Sometimes this make Magisk ask for SU for viper. Makes it work sometimes.
I had to use this method for a while to get it to work. Also I have musicfx disabled in apps. Had to do that on my Nexus 6 and just kept on doing it. Uninstall Viper reboot.
Install Viperfx don't reboot
Install audio modification reboot.
It can be done in TWRP also. If you reflash either of those a second time it uninstalls them if you didn't know.
I'm not a developer I pretty much just mess with these things until they work for me.
Sent from my Pixel 2 XL using XDA Labs
Click to expand...
Click to collapse
These steps allowed me to install the driver!!!! Thank you!

Installed fine for me. Using Magisk 18.1 though.
Here are more instructions (if some continue to have problems) and a Viper profile for XDA members to try out. Works very well to make the phone speakers sound good.
https://forum.xda-developers.com/pixel-2-xl/how-to/viper4android-pixel-2-xl-stereo-speaker-t3919285

Viper4Android not processing

Anyone able to get Viper4Android to process? I have it installed through Magisk and it works when first installed but eventually stops. Only way to get it working again is to reboot.

I think it stops when changing output forms. Instead of rebooting fully, try hitting the 3 dots on the top right of the app and hitting exit and then relaunching the app.

I tried that and force closing it. Didn't work but what seems to have fixed it was uninstalling the driver...it then asked for root permission to do that. After a restart everything is working even when changing apps. We'll see if it's permanent or not. Thanks for the reply though.

Try this: uninstall your current module, reboot, and install this apk. It's an unofficial material design 2 viper that auto generates a magisk module when you install it for your device. I got mine working properly.

Thanks, I'll try that. Been having to reboot again.

Well along with the acp and aml modules that method worked. Hopefully this sticks. Thank you for your help!

TENN3R said:
Try this: uninstall your current module, reboot, and install this apk.
Click to expand...
Click to collapse
That's what I have, and it worked at first but not any longer on Pixel 3a.
Are there other modules that should be installed, or can't be, as well?
-G

ggibby said:
That's what I have, and it worked at first but not any longer on Pixel 3a.
Are there other modules that should be installed, or can't be, as well?
Click to expand...
Click to collapse
I only know about that module, and the one from ahrion and Zackptg5 (here).
Have you tried in this module enabling the compatibility mode and reboot?

TENN3R said:
Have you tried in this module enabling the compatibility mode and reboot?
Click to expand...
Click to collapse
Compatibility mode was enabled, so I disabled it and now it seems to be working.
Thanks for the hint!