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....

Zenfone 3 (ZE553KL) Magisk 16.0 only core mode after Xposed crash, 16.4 bootloop[upd]

I have ZE553KL international version and install the Magisk via the boot.img method (didn't want to touch the recovery for upgrade reasons). Below is what I did after Magisk has successfully after installed:
1. I install Systemless Xposed, but give me the error "Xposed is installed, but not active".
2. After reading around on Xposed git issue, some user were having SELinux issue, so, I load the Systemless SELinux changer and change to permissive - Xposed worked after that.
3. I installed "Roaming Control" and "Smart Network" from Xposed Repo
4. After enable the Xposed module, the phone crashed on restart (would give me warning on Android UI, keyboard crash, and among others. I would stuck at unlock screen with no way of unlock the phone), I restart the phone and hit the power and volume key and it started and seems to work. Including the two Xposed module.
5. After that I enable systemless host file and install Ad-away, and some Magisk module - CloudflareDNS and Sony Music module.
6. Restart the phone, and the phone crash hard, non stop. Took me many restart and pressing the button around to get the phone started. After which I uninstall the two Xposed module, the phone still crashing. So I decide to uninstall Systemless Xposed totally.
7. After that, it seems the system is restarting normal, but still crash randomly. Decide to install Systemless Greenify, restart, phone started crash heavily like when sytemless Xposed was installed.
8. I remove the all Magisk module, thinking it would clear the systemless partition. Restart.
9. Decide to install something simple, install Magisk Cloudflare DNS module, restart phone, start crashing again.
So now, it at the point if I have any Magisk module installed, the phone would crash hard and stays at lock screen. So I enable Core mode, which pretty much is what is the same as what I can do to make the phone stable. I have attached what I can extract from the logcat, hope it will help some debugging.

[2018-07-01] Thought I would like to update. after running safely in core mode for awhile, the urge of play around on getting Xposed running came up again. I change the update channel into Beta, and Magisk Manger immediately prompt for 16.4 version available and whether I want to install it. Choose, yes, and use direct install (as it the recommended method). Quickly, it prompt for me to restart, and this is where the horror comes. After the usual warning about unlock bootloader, Asus logo then it got a new message indicate the system are corrupt, and it would restart by itself again, warning on unlock bootloader, Asus logo - froze.
- Have tried, flash back the stock boot image
- I have tried flash patched boot image via 16.0
Still not working.
Than I was forced to flash TWRP (@shakalaca, thanks you the man), pretty much defeat my purpose of keeping the original recovery of intend easier upgrade for Oreo.
- Tried to flash the original WW-71.60.139.30 rom I was on using TWRP
- Use the Magisk-uninstaller-20180627.zip
Still not working.
It was among some other useless stupid thing that I tried also didn't help, eventually I believe this two step made the phone boot again:
1) Flash the original boot.img at fastboot
2) Flash Magisk 16.0 zip file via TWRP
Wolla, phone booted, no data lost, so far all okay. Hope this may help some people.

magisk modules the Pixel stop in Google logo

Hi All. After I installing magisk modules I restart the phone to activate the module the Pixel not boot and stop in Google logo I have to hold the power button for like 17 a second for force restart then boot again perfect.
The question is that normal or i have done something wrong
Sent from my Pixel 2 using Tapatalk

DinarQ8 said:
Hi All. After I installing magisk modules I restart the phone to activate the module the Pixel not boot and stop in Google logo I have to hold the power button for like 17 a second for force restart then boot again perfect.
The question is that normal or i have done something wrong
Click to expand...
Click to collapse
Interestingly I am having a similar issue. Whenever I add or remove a module through magisk and then reboot, It freezes up right after login and I need to hard boot it again then all is fine. Are you running the custom kernel or is it the stock one? Also are you using Edge Sense Plus??

@CyberpodS2
I don't know if this normal with everyone or not. Everything is Stock and i don't use Edge sense plus
Sent from my Pixel 2 using Tapatalk

Don't reboot through magisk when the module installs, instead restart using the power button after you finish the install of the module.

DinarQ8 said:
I don't know if this normal with everyone or not. Everything is Stock and i don't use Edge sense plus
Click to expand...
Click to collapse
Well it's not "normal" but it might be harmless. Maybe something that the Magisk folks need to work on. We are barely out of release and already it's rooted, custom kernel, themes, mods, xposed. There are bound to be bugs at this early point. Lol
---------- Post added at 10:18 PM ---------- Previous post was at 10:17 PM ----------
wgrant said:
Don't reboot through magisk when the module installs, instead restart using the power button after you finish the install of the module.
Click to expand...
Click to collapse
I'll give that a run. Thanks.

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.

Question Phone randomly reboot

so i've been experience miui randomly reboot ̶4̶ ̶̶t̶i̶m̶e̶s̶ 5 times on today. i always use my phone for daily like social media, music, reading etc, but i've do little modified system
19.12.2021 rooted phone V12.5.1.0.RKSIDXM using magisk 22.1
11.01.2022 install LSposed + Core Patch
what i experience is my phone randomly reboot, it show POCO logo and Unlocked logo. then phone turn off and reboot again, before it show poco logo there a vibration came from phone. i also tried to force into fastboot mode but it keep turn off in fastboot mode.
so how i can boot to homescreen ? ̶a̶f̶t̶e̶r̶ ̶p̶o̶c̶o̶ ̶l̶o̶g̶o̶,̶ ̶w̶h̶e̶n̶ ̶p̶h̶o̶n̶e̶ ̶t̶u̶r̶n̶ ̶o̶f̶f̶ ̶i̶ ̶h̶o̶l̶d̶ ̶p̶o̶w̶e̶r̶ ̶b̶u̶t̶t̶o̶n̶ ̶t̶i̶l̶l̶ ̶i̶t̶'̶s̶ ̶s̶h̶o̶w̶ ̶m̶i̶u̶i̶ ̶t̶e̶x̶t̶ ̶a̶n̶i̶m̶a̶t̶i̶o̶n̶,̶ ̶a̶n̶d̶ ̶e̶v̶e̶r̶y̶t̶h̶i̶n̶g̶ ̶i̶s̶ ̶f̶i̶n̶e̶.̶ it's not work, just hope it can boot to home screen
i wonder if everyone who used this phone have this kind experience, i might going to service center if this happend again

U can try Disable magisk modules via adb
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com

wetito said:
U can try Disable magisk modules via adb
How to Fix Bootloops caused by Magisk Modules (Using TWRP Recovery or ADB)
Has your Android device entered a bootloop after installing a Magisk Module? Then this guide can help you fix that. In this guide, I will show you how to fix bootloops caused by Magisk Modules using…
www.thecustomdroid.com
Click to expand...
Click to collapse
okay so everything was fine till i write this reply, there no random reboot anymore. in case if random reboot happend again, i will try your advice. anyway thanks

This was happening to me any time the Xbox app tried to send a notification. Phone would just reboot.
Still happens even with latest version. Have disabled notifications for that app and it's fine now. Those notifications weren't important anyway.
Strange one but could be similar for you if you are getting a vibrate before reboot like a notification trying to come through?

AnUrbanPenguin said:
This was happening to me any time the Xbox app tried to send a notification. Phone would just reboot.
Still happens even with latest version. Have disabled notifications for that app and it's fine now. Those notifications weren't important anyway.
Strange one but could be similar for you if you are getting a vibrate before reboot like a notification trying to come through?
Click to expand...
Click to collapse
vibrate sign on my phone simillar in condition where phone in off and turn on the phone will have vibrate sign before show poco boot up. when it happend i dont see any strange my notification beside download, social media, and games notification