Database Develop

Xposed Installed, Modules Turned On... Nothing Happens

I'm new to Xposed but I've tried to read everything I can about it before posting.
I've Installed the Framework, hard reboot, installed Modules and hard reboot.
Yet Still nothing happens.
I've tried XPrivacy and GravityBox. XPrivacy Will tell me that the module isn't activated when it is. Gravity Box will tell me the frameworkit's self isn't installed.
I'm at a loss of what to do. Thanks to anyone in advance for any and all help.

When you install the frame work do a soft reboot instead of a regular reboot it will work then.
Sent from my XT1058 using Tapatalk 4

Install and activate in the recovery system write mode. Then it should stick

Keller_psycho said:
When you install the frame work do a soft reboot instead of a regular reboot it will work then.
Sent from my XT1058 using Tapatalk 4
Click to expand...
Click to collapse
Thanks this worked. But now I have this strange Icon in the top right hand corner that looks like an SD card with a red circle with a line through it and it over lapse my Wifi icon in the notification bar.
Also do you know how to reorder things in quicksettings with gravitybox?

Icon000 said:
Thanks this worked. But now I have this strange Icon in the top right hand corner that looks like an SD card with a red circle with a line through it and it over lapse my Wifi icon in the notification bar.
Also do you know how to reorder things in quicksettings with gravitybox?
Click to expand...
Click to collapse
If you installed the MotoXposed app and activated it, it defaults to having the gap between the WiFi icon and the Provider network icons, but unfortunately, it doesn't fix the gap, but instead overlaps them. The icon that looks like an sd card with a red circle is your sim card saying it isn't working. The phone seems to boot faster than the sim card can initialize and shows the sim not working for a moment, then finds the signal.

Xposed isn't Holding After Reboot
I know I was told earlier that I should be doing a soft boot but does that mean that I will have to reinstall Xposed every time I do a reboot?
Also it seem since I have installed Xposed that I've had a few apps consistently go non responsive at same point in using them. Example: I have the premium app for these forums but when ever I try to view any particular thread the app will go non responsive and need to restart.

Icon000 said:
I know I was told earlier that I should be doing a soft boot but does that mean that I will have to reinstall Xposed every time I do a reboot?
Also it seem since I have installed Xposed that I've had a few apps consistently go non responsive at same point in using them. Example: I have the premium app for these forums but when ever I try to view any particular thread the app will go non responsive and need to restart.
Click to expand...
Click to collapse
The soft reboot was mentioned as it allows you to stay booted with the root privileges, Once you have everything set the way you would like it, then just do a normal reboot. If for some reason you want to make a change or try a new module you will have to reboot to recovery to use root. I have not had any apps have issues with being non responsive. You can try uninstall/reinstall of the app, clearing it's data/cache, or going and seeing what is all running at the time on your phone, then disable or uninstall programs you don't want running all the time.

When you say rebooting to recovery odd that an option in the Xposed framework installer or am I doing this during the boot process?
Sent from my XT1058 using XDA Premium 4 mobile app

Icon000 said:
When you say rebooting to recovery odd that an option in the Xposed framework installer or am I doing this during the boot process?
Sent from my XT1058 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You would just turn off the phone, then hold Power+Vol down then press Vol down to get to recovery, then press Vol up to select it. This will boot your phone with root.

stillthisguy said:
You would just turn off the phone, then hold Power+Vol down then press Vol down to get to recovery, then press Vol up to select it. This will boot your phone with root.
Click to expand...
Click to collapse
Thanks

stillthisguy said:
You would just turn off the phone, then hold Power+Vol down then press Vol down to get to recovery, then press Vol up to select it. This will boot your phone with root.
Click to expand...
Click to collapse
I know this seems obvious but I wasn't quite getting how the X works. Thanks for the comment. Makes sense now
So I have it working while in recovery but if I reboot, everything goes away. From reading, this should not be the case. Am I reading the comments incorrectly?

sankyou said:
I know this seems obvious but I wasn't quite getting how the X works. Thanks for the comment. Makes sense now
So I have it working while in recovery but if I reboot, everything goes away. From reading, this should not be the case. Am I reading the comments incorrectly?
Click to expand...
Click to collapse
When setup xposed, any time I make a change, I reboot with write protection off and make sure everything is still working, then boot normally. Never had any issues when doing it that way.

stillthisguy said:
When setup xposed, any time I make a change, I reboot with write protection off and make sure everything is still working, then boot normally. Never had any issues when doing it that way.
Click to expand...
Click to collapse
Yes I redid everything and did that and it stuck. Thanks for the advice - it worked perfectly! Man this phone rocks now and I don't even have to mess with roms....

Phone wont start after installing xposed framework.

Hello,
I installed xposed framework on my galaxy s6 tmobile on 6.0.1 marshmallow. I installed it through twrp and after i rebooted the phone wont boot up. The screen is black, but the blue led in the top left corner stays lit. I cant boot into twrp but i can put it in download mode. I also cant turn it off. I watched a video about installing xposed and the guy said that it can take up to 20 minutes to boot the first time after installing xposed. I installed it around 40 minutes ago and it still has not booted up. Does the phone just need more time, or have i bricked my phone? If it is bricked would i be able to put it in download mode and flash stock through odin? Thanks in advance.
update: After some time the phone screen turned on and it is now stuck at the tmobile boot screen.

What's your TWRP verison/ Xposed version that you flashed?

vince.p said:
Hello,
I installed xposed framework on my galaxy s6 tmobile on 6.0.1 marshmallow. I installed it through twrp and after i rebooted the phone wont boot up. The screen is black, but the blue led in the top left corner stays lit. I cant boot into twrp but i can put it in download mode. I also cant turn it off. I watched a video about installing xposed and the guy said that it can take up to 20 minutes to boot the first time after installing xposed. I installed it around 40 minutes ago and it still has not booted up. Does the phone just need more time, or have i bricked my phone? If it is bricked would i be able to put it in download mode and flash stock through odin? Thanks in advance.
update: After some time the phone screen turned on and it is now stuck at the tmobile boot screen.
Click to expand...
Click to collapse
Not sure what version of Xposed you flashed but I've got the same phone and I flashed teh following:
twrp-3.0.2-1-zeroflte.tar.md5
xposed-v81.0-sdk23-arm64-custom-build-by-wanam-20160411.zip
If you still are having problems, you should be able to boot to download mode and try flashing the original firmware via Odin as you suggested. Remember, that if you strike out using Odin, you can also download the original firmware from Samsung Kies or Samsung Smartswitch (once you've booted your phone to download mode which at present you are able to do).

Hey guys,
Shortly after I posted the thread I flashed stock through odin and that fixed it. The version of xposed that i tried flashing was xposed-v83-sdk23-arm64. I will try v81 like cwhiatt suggested. Thank you for the responses.

Do not try until Wanam releases the new xposed module.
Samsung s6 will get into bootloop if u install xposed module now.

VAbaker said:
Do not try until Wanam releases the new xposed module.
Samsung s6 will get into bootloop if u install xposed module now.
Click to expand...
Click to collapse
Wanam does not work with MM (I tried to add screenshot to power menu and it's a no go). I have not had any issues with the Xposed module v81 however.

OK! So i was having the exact same problem.. I dirty flashed MM which went fine. BUT... I previously was running xposed on 5.1 which seems to be the problem, how i don't know but after doing a back up of my important apps then a full wipe.. Installed xposed 81.vers and everything's is good.. After 2 hours of not booting and reading other success stories I knew this was something small to fix... Full wipe if you were running xposed on 5.1 and dirty flashed..

Good to hear v81 works. I gotta try ~
---------- Post added at 01:44 PM ---------- Previous post was at 01:42 PM ----------
How about viper4android ?
Anyone using it without problem ?
I could not make it work.

I installe ver 86 first but phone went to bootloop, then read this guy's comment and tried v81 by directly booting into twrp and flashing the v81 and apparently seems to have fixed it, atleast the phone moved ahead from the 'US Cellular' Boot screen and is now 'optimizing apps' .
Fingers crossed (Y) .
Thanks for suggesting v81 man

Can't turn off the phone normally

After I installed Magisk 16.0 on my OnePlus 3T with OOS Open Beta 23, when I long press the power button, it instantly leads me to the OOS boot animation, I don't get the 1+ and powered by android screen nor I get the unlocked bootloader warning. Thus I can't boot to fastboot or recovery when rebooting via power button. I can turn off the phone by pressing the power button for a very long time while the phone is loading though. What should I do?

No problem here. Have you got Substratum and installed some themes?

przemcio510 said:
No problem here. Have you got Substratum and installed some themes?
Click to expand...
Click to collapse
No I don't, I use the following modules: Adaptive Icons Round Mask, Busybox for Android NDK, Magisk Google DNS, OP3T Front Camera Fix and YouTube Vanced Black.

NeoMember said:
No I don't, I use the following modules: Adaptive Icons Round Mask, Busybox for Android NDK, Magisk Google DNS, OP3T Front Camera Fix and YouTube Vanced Black.
Click to expand...
Click to collapse
I would uninstall Magisk and see if the problem goes away then reinstall Magisk only and check that all is well. The do the modules one at a time checking that you can reboot normally.
Sent from my OnePlus3T using XDA Labs

BillGoss said:
I would uninstall Magisk and see if the problem goes away then reinstall Magisk only and check that all is well. The do the modules one at a time checking that you can reboot normally.
Sent from my OnePlus3T using XDA Labs
Click to expand...
Click to collapse
Well, for some reason my device was unable to boot to system, so I started fresh with Magisk and problem is gone now. Still don't know the reason though.

Can't install magisk, after adding wrong module

Hi, I wanted to try the debloater module, so i installed it on my Oneplus 7 Pro. After the installisation and reboot, the device always stayed on the bootlocker warning screen really long. After that it always startet to fastboot.
My first try was to flash the module uninstaller: https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242.
-> Flash was sucessfull, but it did not work at all.
Second try was to delete the modules via TWRP File explorer, so i deleted the folder of the module.
-> Still same problem, boots from bootloader unlocked warning screen directly to fastboot.
My next try was to flash the magisk uninstaller.
-> Flash sucessful, phone running again.
After that i reflashed magisk.
-> Problem started again.
Next step was flashing the uninstaller and then booting to android, to delete the magisk Manager. After that reflashing magisk.
->Same Problem as in the beginning. But there is no module when i have a look at /data/adb
Right now my device is running, but i have no idea how to reinstall magisk. Is there anybody who could help me?
I'd like to get magisk back and would prefer not to factory reset or wipe any sd data...

If there are no modules installed, there's likely something else going on...
Examples of things to do/try:
Don't install TWRP. Leave the boot image untouched and just boot TWRP to install Magisk (there's been instances where Magisk and TWRP conflict).
Reflash just the system images and leave data untouched.
Ask for advice in your device's forum. That's usually where you'll get the best device specific help.

Thank you for the advice!
So you mean i should flash the stock recovery again? And then sideload TWRP, or simply patch my boot image and flash it via ADB?
But why did i not have any problem with TWRP and magisk all the time before? Everything startet with the reboot after installing a new module?
I will also post my question in the OP 7 Pro forum!

Download Magisk 20.1
fastboot boot twrp (I'm using .72 but some say they have issues with it, try .70 or .74)
adb sideload twrp.zip (or flash it, if it is on your device)
reboot twrp
adb sideload magisk 20.1 (or flash it, if it is on your device)
Reboot.
Not sure what you are trying to debloat but I also have a 7pro and I used xxxnolimits magisk rom which has some debloating in it, I recommend trying it.

GeekMcLeod said:
Download Magisk 20.1
fastboot boot twrp (I'm using .72 but some say they have issues with it, try .70 or .74)
adb sideload twrp.zip (or flash it, if it is on your device)
reboot twrp
adb sideload magisk 20.1 (or flash it, if it is on your device)
Reboot.
Not sure what you are trying to debloat but I also have a 7pro and I used xxxnolimits magisk rom which has some debloating in it, I recommend trying it.
Click to expand...
Click to collapse
Worked finde for me! Only problem was with twrp 74, data was not decrypted, so i had to fastboot twrp 70.
Thankyou very much! I also combined it with updating from 10.0.1 to 10.0.2.
I just wanted to debloat the oneplus galerie, so i could install an older version from apk mirror, that still has the never settle stamp.

6nchris said:
Worked finde for me! Only problem was with twrp 74, data was not decrypted, so i had to fastboot twrp 70.
Thankyou very much! I also combined it with updating from 10.0.1 to 10.0.2.
Click to expand...
Click to collapse
Glad to have helped out! I love the 7pro. Only had it for like two weeks? Maybe only 1. Came from The 6t and I have everything as it was on my 6t. So much easier too.

GeekMcLeod said:
Glad to have helped out! I love the 7pro. Only had it for like two weeks? Maybe only 1. Came from The 6t and I have everything as it was on my 6t. So much easier too.
Click to expand...
Click to collapse
You really did help out. I love it to, there is only one big problem i think. The proximity sensor does not work good at all, so sometimes in calls screen turns on and your ear touches something... I really hope they will find a solution. Even turning the screen of with the power button and wake it up by pressing the power button again would be okay, but when you turn the screen of by pressing the button the proximitx sensor sometimes turns it on again..
i came from 3T to the essential phone. I Think modding the OP 3T or the OP 7Pro is much easier than the essential PH1...

6nchris said:
You really did help out. I love it to, there is only one big problem i think. The proximity sensor does not work good at all, so sometimes in calls screen turns on and your ear touches something... I really hope they will find a solution. Even turning the screen of with the power button and wake it up by pressing the power button again would be okay, but when you turn the screen of by pressing the button the proximitx sensor sometimes turns it on again..
Click to expand...
Click to collapse
Ahh, sad too say but I can't help with that. I don't take calls often so never noticed anything like that.

Does installing any modules is actually safe?

Hi there!
Just a quick question. Finally afer so much time since the actual update to emui 9.1 (Psmart Fig-lx1) Ive finally managed to get that **** done - i mean rooting that mother****er
From what I gathered if I want to reboot the phone I have to hold that power vol + button 'n 'stuff. So question remains simple.
**So if i would instal a magisk module and it reboots my phone - do I need to just hold that vol + button and the planet wont go boom, or is ther aleoso some specific stuff You need to co?
**Also - what does 'recovery mode option in Magisk Manager means?
Cheers!

Why would you have to hold the vol + button to reboot at all? That's not normal.
Sent from my LG-US998 using Tapatalk

kenbo111 said:
Why would you have to hold the vol + button to reboot at all? That's not normal.
Sent from my LG-US998 using Tapatalk
Click to expand...
Click to collapse
A recent method on installing magisk trough a patched recovery image require exacly that. And it's not the end. When You boot normally no buttons - You've got non rooted system (without magisk)
When You keep Vol+ till splash screen You've got system with magisk (full root)
And when You keep that VoL allll the way - You suppose to boot into recovery.
I too don't know how they pulled this off but just in case something wouild go wronga after instalation of the meodules I'd like to know in advence

That's wierd! I've never heard of that before
Sent from my LG-US998 using Tapatalk

kenbo111 said:
That's wierd! I've never heard of that before.
Click to expand...
Click to collapse
It's uncommon, but not unheard of. Rebooting that way be needed for devices where a Magisk patched boot image is swapped with the recovery image (since the modified boot image couldn't be put in place of the original, untampered one for some reason). In such cases, if you reboot to recovery, the Magisk modified boot image will be loaded instead of the recovery, which will lead to booting into a rooted ROM. This is how root also works for Samsung S9 and Note 9.

shadowstep said:
It's uncommon, but not unheard of. Rebooting that way be needed for devices where a Magisk patched boot image is swapped with the recovery image (since the modified boot image couldn't be put in place of the original, untampered one for some reason). In such cases, if you reboot to recovery, the Magisk modified boot image will be loaded instead of the recovery, which will lead to booting into a rooted ROM. This is how root also works for Samsung S9 and Note 9.
Click to expand...
Click to collapse
That sounds both incredibly annoying and tedious but also quite handy when it comes to recovering from bootloops when you aren't near a PC ?
Sent from my Pixel 3a XL using XDA Labs

Skittles9823 said:
That sounds both incredibly annoying and tedious but also quite handy when it comes to recovering from bootloops when you aren't near a PC ?
Click to expand...
Click to collapse
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.

shadowstep said:
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.
Click to expand...
Click to collapse
Ahh my brain hurts lmao.
I thought it would boot into an unrooted system if not using the recovery shortcut. Yea that does sound irritating.

Skittles9823 said:
Ahh my brain hurts lmao.
I thought it would boot into an unrooted system if not using the recovery shortcut. Yea that does sound irritating.
Click to expand...
Click to collapse
I am sure, lol. Also, if it boots to an unrooted system if not using the recovery shortcut and to a rooted system if using that recovery shortcut, how do you access recovery? Be glad you have a much more root-friendly device.

shadowstep said:
Also, if it boots to an unrooted system if not using the recovery shortcut and to a rooted system if using that recovery shortcut, how do you access recovery? Be glad you have a much more root-friendly device.
Click to expand...
Click to collapse
Haha yea, that's true.
Sent from my Pixel 3a XL using XDA Labs

shadowstep said:
Yet, it is. That's why I'll never buy devices that can't be easily rooted. I forgot to add, since the images are swapped (original boot becomes recovery and recovery becomes Magisk patched boot), a normal reboot would lead to booting to recovery everytime and rebooting to recovery (either by a key combo or from the ROM itself) is needed to boot to system. Good times.
Click to expand...
Click to collapse
In fact, the images are not swapped (at least on S10). If you hold the Vol key long enough, the recovery kernel will boot the recovery system, and if you release it, it'll boot android. So, a rooted system runs on the recovery kernel.

Keule-T said:
In fact, the images are not swapped (at least on S10). If you hold the Vol key long enough, the recovery kernel will boot the recovery system, and if you release it, it'll boot android. So, a rooted system runs on the recovery kernel.
Click to expand...
Click to collapse
Not sure about the S10, but they are definitely swapped for S9. More information can be taken from this XDA article (and the thread links referenced in it). :good:

given nice contidions, any phone can break just by using magisk modules that do tricky stuff to ur image. and since that applies on any magisk module for a varius of reasons, wellp there is no "safe" module. under certain circumstances every module can break **** down.