Database Develop

xposed framework not working tried EVERYTHING

Ok So.. I am using my HTC One for almost a year now, when I came across this xposed frame work and xblast module, and I got so so excited after reading this, that trust me the sole reason for Rooting my HTC One was to be able to use xblast.
I rooted my HTC One, successfully, and installed xposed framework successfully as well, Installed xblast and did all sorts of modifications like, changing carrier text, wifi signal color, battery color, mobile signal color and couple of others and did a reboot, and to my surprised and much to the anticlimax to my excitement NOTHING worked not even one change happened ... ... I was like in tears ... ..... well check and re checked everything, and tried a hard re boot and still nothing.
I then noticed if I go in to xposed framework, it says the latest version of xposed is not active and I have like red "42" in front of app_process.
Searched xda and came to conclusion that you have to manually or automatically (what ever works) have to install the xposed framework file.
I tried the below files from THIS thread
cwm-Xposed.Framework.Installer.v2.3.1.zip
cwm-Xposed.Framework.Installer.v2.4.1.zip
Version 2.4.1 if I install by going in to recovery mode, the phone does not boot at all and gets stuck at HTC Logo screen, I have to then go to recovery and load the " Xposed-Disabler-Recovery.zip " to be able to boot.
Version 2.3.1 if I install I am able to boot BUT it still says the latest version of xposed is not installed. and its all red in front of app_process.
Searched XDA AGAIN and some post suggested that do a manual install and when in recover install the xposed-installer-recovery.zip from Android/data/de.robv.android.xposed.installer/files BUT doing this again does not let my phone boot and I am stuck at HTC Logo till the time I re boot to recovery and run the Xposed-Disabler-Recovery.zip
I am using a rooted HTC One M7 with Android 4.4.2 and HTC sense 6 with Nova Launcher ..
Friends as you can see I have done every part of my own trouble shooting and have read like gazillions thread on XDA and tried out every possible thing I can think off.
I believe I now have the right to start a thread and ask for help officially ....SO PLEASE HELP ...:crying:

Hi Friends, any one on this, I could really use some help and guidance here ....

Have you tried to reinstall xposed? Deinstall the app and reinstall everything? What about root access? Have you granted xposed root access?

Use the latest version (2.6.1) and flash Xposed from the recovery. We can't help you if you're using an old version (2.4.1).
(FYI, the installer would've told you to do exactly that if you just used the latest version.)

OK OK wait I did some more reading, mean time I was waiting for a reply here, and did some troubleshooting, it seems the S-On was the culprit ....... I had to use firewater to get S-OFF even that was not straight as I was getting some error. I then had to flash kernal Bulletproof and then use firewater to have S-OFF.
Anyway with S-OFF I finally was able ti have Xposed framework all green. BUT BUT xblast which was the sole purpose of the entire saga, messed up my phone like anything. I loaded Xblast module and again did all sorts of changes, and re booted, ...
Here goes my experience ...
1. It took a truck load of time to boot,
2. Then when I finally saw the desktop screen, my carrier signal was off, No signal what so ever ...
2.1 BTW I was able to see few xblase changes like my name on the status bar.
2.2 Crashed few apps like DS Audio and lastfm
3. Even before I could think to proceed I started getting this message "com.android.phone has stopped unexpectedly" repeatedly, again n again. I kept on pressing Dont send but the message would not go.
4. I rebooted again and same behavior the message simply would not go, plus no signal.
5. What I finally did was somehow go in to xposed framework and uncheck xblast and rebooted
6. Finally I was able to boot with everything back.
Good new is atleast Xposed Framework is working with all Green. Xblast didnt and is checkedoff
BTW xblast version is latest (AFAIK) ...1.8.7
Any suggestions steps the gurus here can recommend to have xblast working.
Mean time will try some other modules like BubbleUPnP (Audio cast) , sense 6 tools etc and report ...
Thanks for all the help and guidance

This is the wrong place for module specific support, you should post in the modules' threads instead.

could have atleast point me in the right direction .... anyway thanks for all help here ....

sam9s said:
could have atleast point me in the right direction .... anyway thanks for all help here ....
Click to expand...
Click to collapse
I did: I told you to post in the modules' threads. Those are usually linked from inside the module itself or from the module's repo page, but I'm not going to search for the links myself and paste them for you.

SuperSU Me Please !!! (Updated 01/28/2017)

Super-SuMe Pro:
Disclaimer:
We nor XDA are responsible for anything that you choose to do with this program to your device or others. Modifying our code or redistributing it is not allowed without prior approval from us.
Donations:
"If this application helps you out, please consider a small monetary donation to further improve development of this application. You can Donate by clicking the "Donate to Me" button on your left, underneath my Profile picture. (The Team will divide it up..)
Developers / Contributors:
@Tomsgt (RootJunky)
@hsbadr
@Surge1223
@gatesjunior
Tester / Buddy:
@freddy0872
Background:
So after we gained root on the Note 4 everyone was excited, except that we all didn't like the KingRoot applications running
on our device and were not sure what it all was collecting. Also, many of our favorite programs we know work with SuperSU and
some even look for it. So we decided as a team to take on the challenge and come out with this script that will completely remove all of the KingRoot applications and put SuperSU on our device.
Requirements:
• KingRoot application on your device (There are known issues with certain versions of Kingroot, below is the version I use and know works well..)
Don't even try to run this if you have not just done a clean reboot and then rooted with KingRoot. Yes, you must do
this, otherwise you risk a reboot in the middle of the process and will have to do it anyway..
What does it do?:
• Removes KingRoot / Kingo Root applications
• Disables Knox
• Installs SuperSU
• It does NOT give you permanent root on the Note 4 (Update: The Pro version includes root protection, you will be surprised at how long you can retain root now.
What audience of device does it support?:
• AT&T Note 4
• Verizon Note 4
• Many, many other devices
It also will work on pretty much any other device that has KingRoot installed and you are looking at getting over to SuperSU..
This will work on any Android OS as long as you are rooted with KingRoot first.
Process if your device reboots / you lose root:
Uninstall Super-Sume Pro
Reboot
Root with KingRoot 5.x or newer
Install and run Super-Sume Pro
Here is a nice video that ours truly, RootJunky put together:
Download Link:
APK now available to do all of this for you without a PC..
https://play.google.com/store/apps/...ore&pcampaignid=APPU_1_uzPDVbGyFcGNyATHrqmoCA

Thank you Gates @ Team!! Awesome work you guys! Thank you very much your work is greatly appreciated!

Thanks
Been waiting on this for soooo long thanks so much

gatesjunior said:
SuperSUMe:
Disclaimer:
We nor XDA are responsible for anything that you choose to do with this program to your device or others. Modifying our code or redistributing it is not allowed without prior approval from us.
Donations:
"If this application helps you out, please consider a small monetary donation to further improve development of this application. You can Donate by clicking the "Donate to Me" button on your left, underneath my Profile picture. (The Team will divide it up..)
Developers / Contributors:
@Tomsgt (RootJunky)
@hsbadr
@Surge1223
@gatesjunior
Tester / Buddy:
@freddy0872
Background:
So after we gained root on the Note 4 everyone was excited, except that we all didn't like the KingRoot applications running
on our device and were not sure what it all was collecting. Also, many of our favorite programs we know work with SuperSU and
some even look for it. So we decided as a team to take on the challenge and come out with this script that will completely remove
all of the KingRoot applications and put SuperSU on our device.
Requirements:
The program requires that your manufacturer USB drivers are installed for your specific device as well as the following:
• Windows Operating System
• USB Debugging turned on for your device
• KingRoot application on your device
The process in the beginning will ask you to hard reboot your device and re-root the device with KingRoot. Yes, you must do
this, otherwise you risk a reboot in the middle of the process and will have to do it anyway..
We are also currently finishing up an on-device script for you as well as possibly an apk you could install to do the same thing. We are also
fine with anyone who wants to take this on and use our script as a guide. Just be fair and give us credit in the post..
What does it do?:
• Removes KingRoot applications
• Disables Knox
• Installs SuperSU
• Soft Reboot at the end
What audience of device does it support?:
• AT&T Note 4
• Verizon Note 4
All of the above require you to be running KitKat on the device as well. There currently is no root method available for the Lollipop release.
Here is a nice video that ours truly, RootJunky put together:
Download Link(s):
http://rootjunkysdl.com/?device=Galaxy Note 4&folder=Kitkat Root
Enjoy guys, we hope you like it..
Click to expand...
Click to collapse
Nice Work !!! Looking forward to DisableWriteProtection followed by custom ROMs

custom stock rom
I know this won't allow custom roms but is it possible to have a modified stock rom? Awesome work will try this later today

As far as root is concerned is this method permanent, I know kingroot isn't and this just seems to replace kingroot jazz with supersu, which is awesome by the way, but I saw no mention of permanent root or temp root.

thanitos said:
As far as root is concerned is this method permanent, I know kingroot isn't and this just seems to replace kingroot jazz with supersu, which is awesome by the way, but I saw no mention of permanent root or temp root.
Click to expand...
Click to collapse
OP updated, no it does not yet. We are currently working on this.

note edge work! thank you!

gatesjunior said:
OP updated, no it does not yet. We are currently working on this.
Click to expand...
Click to collapse
彩色的风 said:
note edge work! thank you!
Click to expand...
Click to collapse
Nice going gates! And u got it rolling on note edge from the looks of it! Top notch as always!

So this is not working for me.
I have used odin to succesfully downgrade from lollipop to 4.4.4 via the Stock_Restore_NJ5.zip file. Everything upon reboot of that shows the phone is running fine.
I have enable USB Debugging. I have no versions of SuperSU installed previously. I have the usb drivers installed and running your script seems to work fine. Kingroot apps are cleaned out during the script and SuperSU is installed. I run it and update the binary but after a 10+ second wait I get an installation failed.
I have factory reset the phone and tried it all once again but still the same outcome. I have verified that NJ5 is my current build.
Any ideas?

made me check box in developer options "mock locations". is that normal? i dont remember seeing that in video. took me forever to figure out what it wanted me to check off
Edit: Root is on ATT variant. took a number of tries doing the whole process to get it to work

dccoh said:
So this is not working for me.
I have used odin to succesfully downgrade from lollipop to 4.4.4 via the Stock_Restore_NJ5.zip file. Everything upon reboot of that shows the phone is running fine.
I have enable USB Debugging. I have no versions of SuperSU installed previously. I have the usb drivers installed and running your script seems to work fine. Kingroot apps are cleaned out during the script and SuperSU is installed. I run it and update the binary but after a 10+ second wait I get an installation failed.
I have factory reset the phone and tried it all once again but still the same outcome. I have verified that NJ5 is my current build.
Any ideas?
Click to expand...
Click to collapse
Whenever I downgrade I use the full firmware zip. Never had great success with the other variants.

bug report! super user ask me to update su files again, but it fails this time so I can't give privilege to my app anymore, any advice?

彩色的风 said:
bug report! super user ask me to update su files again, but it fails this time so I can't give privilege to my app anymore, any advice?
Click to expand...
Click to collapse
Which apps did you grant su to?
---------- Post added at 12:34 PM ---------- Previous post was at 12:32 PM ----------
I'm going to be out and about. Had a wedding yesterday and got some running around to do. If some of you need help or anything hit me up on hangouts if you need to. [email protected]
Help you out as best as I can!

freddy0872 said:
Which apps did you grant su to?
Click to expand...
Click to collapse
just xpose and greenify. looks like we should be hurry when we root it before the su vanish

I got it to work, but when I went into SuperSU after the reboot, it said it had to update su again. In the process of updating, the phone rebooted and I'm currently doing it all over again.

彩色的风 said:
just xpose and greenify. looks like we should be hurry when we root it before the su vanish
Click to expand...
Click to collapse
When you install exposed. It has you reboot. You will lose root. Re apply root and you should be able to function inside of xposed but remember any time you make a change that requires a reboot you will have to re root as well
---------- Post added at 12:37 PM ---------- Previous post was at 12:37 PM ----------
Sizzlechest said:
I got it to work, but when I went into SuperSU after the reboot, it said it had to update su again. In the process of updating, the phone rebooted and I'm currently doing it all over again.
Click to expand...
Click to collapse
See post about rebooting sir

Guys, I updated the build. Download the new file from the OP and try that..
Reboot your device, root with Kingroot and then run this new build..

freddy0872 said:
When you install exposed. It has you reboot. You will lose root. Re apply root and you should be able to function inside of xposed but remember any time you make a change that requires a reboot you will have to re root as well
---------- Post added at 12:37 PM ---------- Previous post was at 12:37 PM ----------
See post about rebooting sir
Click to expand...
Click to collapse
I know that, so I installed the exposed before the tips in cmd ask me to push the key to restart my device, everythings looks fine in the first minute. but then the super user crash
it asked me to update the su again, I believe it's still WP

彩色的风 said:
I know that, so I installed the exposed before the tips in cmd ask me to push the key to restart my device, everythings looks fine in the first minute. but then the super user crash
it asked me to update the su again, I believe it's still WP
Click to expand...
Click to collapse
Download the new build in the OP and try that one..

[ROOT] [Magisk] [Galaxy S6] - Magisk-root uninstalls automatically?

Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
(I don't want to install a Custom ROM!)
Thank you
Larry

larrythil said:
Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
Thank you
Larry
Click to expand...
Click to collapse
I had the same problem with my Nexus 6P.
I was on stock ROM and stock kernel and it happened twice.
Now I'm on stock ROM and EX Kernel and problems seemed go away.
Inviato dal mio Nexus 6P utilizzando Tapatalk

CyberZeus1977 said:
I had the same problem with my Nexus 6P.
I was on stock ROM and stock kernel and it happened twice.
Now I'm on stock ROM and EX Kernel and problems seemed go away.
Inviato dal mio Nexus 6P utilizzando Tapatalk
Click to expand...
Click to collapse
Tell me somthing about "stock kernel" and "EX Kernel" what is that and how can i install that? or change that?

I have the same problem, galaxy S6.

I noticed losing root randomly and fixed it by going install patch boot img then you flash the boot img in recovery. So far it's been a day no root loss
Lineage 14.1 for lg stylo 2 plus

Hi ! I have sale problem with my S8+ with custom rom and Custom kernel

Hello.
I am having the same issue with my S6. I have tried all of the advice from previous threads with regard to different versions of Magisk.. (Removing Busy Box / Not using the Magisk Hide feature... etc etc..). I have also been through as many extra options as I can think of, getting all of the "Update" patches from the other developers who have helped with the Magisk project.
Each time, I have run through all of the aditional scripts to make sure SU and Magisk have been completely removed prior, and then used Odin to do a recovery back to my Original ROM (a complete system backup image I previously saved).
The other interesting observation i have at the moment is that i can not get to the Log cat files to post them anywhere. I can see where they are supposed to be but the directory is empty "no files". I have even been as far as downloading one of the many "Mobile Forensic" software kits to try and see if there is anything wrong with my phone.
There is only one observation to report. It seems that after installing Magisk (even if you just install the main ROM and not the manager). Google play starts to download straight away... I am not sure what it is downloading as it doesn't ever seem to complete and all of my versions of the apps are up to date.
I hope I will be able to get some more usefull information for you soon (LogCat etc etc.). If any one has an answer or suggested options it would be good. I am particularly interested in getting the Busy Box feature to work with Root as I am working on an app for my job that needs both options (I work offshore and am trying to adapt a piece of Seismic QC software (unix based) to run on phones / tab's - Android).
I will sign up properly and start to follow the threads more closely.
Cheers... Andy
-Samsung S6 - Full Magisk Module (with recommended zeroflte TWRP).

AndyQVT said:
Hello.
I am having the same issue with my S6. I have tried all of the advice from previous threads with regard to different versions of Magisk.. (Removing Busy Box / Not using the Magisk Hide feature... etc etc..). I have also been through as many extra options as I can think of, getting all of the "Update" patches from the other developers who have helped with the Magisk project.
Each time, I have run through all of the aditional scripts to make sure SU and Magisk have been completely removed prior, and then used Odin to do a recovery back to my Original ROM (a complete system backup image I previously saved).
The other interesting observation i have at the moment is that i can not get to the Log cat files to post them anywhere. I can see where they are supposed to be but the directory is empty "no files". I have even been as far as downloading one of the many "Mobile Forensic" software kits to try and see if there is anything wrong with my phone.
There is only one observation to report. It seems that after installing Magisk (even if you just install the main ROM and not the manager). Google play starts to download straight away... I am not sure what it is downloading as it doesn't ever seem to complete and all of my versions of the apps are up to date.
Click to expand...
Click to collapse
So long story short, there's no definitive solution to the problem. Im using a g920p with a custom kernel built by a genius dev, and i still lose root once a day.
Basically what it comes down to is modules. If you have zero modules, you'll have better luck... But that's not the point of magisk, so you need to be picky with modules. Use osmosis's busybox from the magisk repo, but other than that, install modules 1 at a time and see if it affects root.
Another tip: uninstall all updates of the "device maintenance" app, and find it in Google play and turn off automatic updates. Then go to device maintenance > battery > unmonitored apps and magisk manager to the list of unmonitored apps... Then go back the battery screen, battery usage > 3 dots in top right > optimize battery usage, and make sure magisk manager is not optimized... That should help some. (Note: some models don't have device maintenance, but you'll still have the "optimize battery usage" option some where.)
The Google play thing you're seeing is likely "instant apps" updating. I believe that should be unrelated to all this, but some aspects of instant apps is a mystery.
As for the logcat thing, i believe you're getting logcat confused with the magisk_debug.log located in /data ? If that's the case, you need to be using the beta version of magisk. Go to magisk and set the update channel to beta, you'll get a notification to update magisk, download it and flash. (Or if the recommended native install is an option, use that)
I recommend just using he normal 14.3 magisk... You'll have issues, but they will be predictable and easy to solve with a simple reboot. There's really no final solution for us unfortunately, just making it as stable as possible.
Lastly, it helps if once every once in a while you fully uninstall magisk with the uninstall.zip, reboot (you might not get a bootloop, in which case hold volume up +power+ home to boot into recovery), reflash magisk 14.3, and then wipe cache and art/davik.
---------- Post added at 04:12 PM ---------- Previous post was at 04:12 PM ----------
larrythil said:
Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
(I don't want to install a Custom ROM!)
Thank you
Larry
Click to expand...
Click to collapse
See above

Thanks to all for the help
Nye-uhls said:
So long story short, there's no definitive solution to the problem. Im using a g920p with a custom kernel built by a genius dev, and i still lose root once a day.
Basically what it comes down to is modules. If you have zero modules, you'll have better luck... But that's not the point of magisk, so you need to be picky with modules. Use osmosis's busybox from the magisk repo, but other than that, install modules 1 at a time and see if it affects root.
Another tip: uninstall all updates of the "device maintenance" app, and find it in Google play and turn off automatic updates. Then go to device maintenance > battery > unmonitored apps and magisk manager to the list of unmonitored apps... Then go back the battery screen, battery usage > 3 dots in top right > optimize battery usage, and make sure magisk manager is not optimized... That should help some. (Note: some models don't have device maintenance, but you'll still have the "optimize battery usage" option some where.)
The Google play thing you're seeing is likely "instant apps" updating. I believe that should be unrelated to all this, but some aspects of instant apps is a mystery.
As for the logcat thing, i believe you're getting logcat confused with the magisk_debug.log located in /data ? If that's the case, you need to be using the beta version of magisk. Go to magisk and set the update channel to beta, you'll get a notification to update magisk, download it and flash. (Or if the recommended native install is an option, use that)
I recommend just using he normal 14.3 magisk... You'll have issues, but they will be predictable and easy to solve with a simple reboot. There's really no final solution for us unfortunately, just making it as stable as possible.
Lastly, it helps if once every once in a while you fully uninstall magisk with the uninstall.zip, reboot (you might not get a bootloop, in which case hold volume up +power+ home to boot into recovery), reflash magisk 14.3, and then wipe cache and art/davik.
---------- Post added at 04:12 PM ---------- Previous post was at 04:12 PM ----------
See above
Click to expand...
Click to collapse
Hello again.
So in response.
I followed the advice given... (just as a note previously the root issue would happen within an hour of restarting the device). I have been to the beta thread and read through all advice. Before jumping to the Magisk 14.3, I started with Magisk 14.2, there was a post recommending this as a critical update to Magisk 14.0.
I had no issues with this install (I had once again used my backup to revert the phone back to all original).
I then added any of the modules i wanted one at a time waiting over an hour before looking at adding any additional modules.
So far, I have not lost root and the phone is working as expected (alot better infact). I have all the Busybox modules +add-on's running, still no issues.
The upgrade to v14.2 seems to have fixed all for my uses.
Thanks to all for help and advice.
Andy

AndyQVT said:
Hello again.
So in response.
I followed the advice given... (just as a note previously the root issue would happen within an hour of restarting the device). I have been to the beta thread and read through all advice. Before jumping to the Magisk 14.3, I started with Magisk 14.2, there was a post recommending this as a critical update to Magisk 14.0.
I had no issues with this install (I had once again used my backup to revert the phone back to all original).
I then added any of the modules i wanted one at a time waiting over an hour before looking at adding any additional modules.
So far, I have not lost root and the phone is working as expected (alot better infact). I have all the Busybox modules +add-on's running, still no issues.
The upgrade to v14.2 seems to have fixed all for my uses.
Thanks to all for help and advice.
Andy
Click to expand...
Click to collapse
Glad everything is good! Sometimes magisk will get messed up, so just updating or even reinstalling will fix things.
Just keep in mind, its very likely you'll have problems again down the road... Samsung phones do a lot of weird stuff under the hood, and eventually symlinks will get broken, files deleted etc... So when that does happen, the best you can do is uninstall, reflash, update, and watch your modules.

Today updated to 15.3 and install James DSP root losed...When open magisk ask for installation reboot to recovery twrp install latest zip reboot open magisk it close it self and root lost again ?! Any advice from @topjohnwu

Do you guys mind posting a resource that shows how to root the S6 using magisk? I'm very rusty, last time I dealt with rooting was 8 years ago. Any help is appreciated. Thanks

Phone stuck on booting screen after install

Hello,
first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8. Yes, i've read now that it doesn't work with the official ROM, but now it's a bit to late.
So. After rooting my S8 today (using TWRP) i wanted to install Xposed. I downloaded an installer from this site because.. umm, i had a brain fart. For some reason my brain took that site as the official website, so i downloaded it from a 3rd Party site instead of the actual website.
I installed the apk and granted root access. After that i clicked on install and Xposed installed successfully. After that it obviously asked me to reboot my device, which i did. But now i am stuck on the Samsung screen of the boot progress. I know i could technically just wipe the phone (again) and start anew, but i'd like to avoid that if possible. I can access TWRP, but if i try to access the system files in the file browser, it shows "0MB" and i can't access them.
I tried downloading an uninstaller linked in this thread, but i don't know which one i should download.
Sorry again for me being so stupid and not reading into it and downloading from some weird 3rd Party site.
Thanks in advance for the help!
EDIT: And yea, of course i didn't create a backup before installing Xposed. So if there is no way to properly uninstall it, i gotta wipe everything once again

Emilia-Chan said:
Hello, first off, sorry. I was stupid and didn't read into it before installing (or trying to install) Xposed to my Samsung S8.......
Click to expand...
Click to collapse
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
http://dl-xda.xposed.info/framework/uninstaller/
If necessary, you can always try to obtain some additional member guidance and support from the following Q&A thread that's specific to your device and variants.
https://forum.xda-developers.com/showthread.php?t=3582142
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Sent from my Samsung Galaxy S8 using XDA Labs

Ibuprophen said:
I don't have this device but, I believe that you should be able to flash (via TWRP) the Framework Uninstaller located on the following Official XPosed link. Just select the correct ARCH (ARM, ARM64, etc...) for your device.
Click to expand...
Click to collapse
I tried that before, unfortunately without success. It also may be noteworthy that my brain turned off and downloaded the XPosed installer off some 3rd Party site. I know. Stupid. But it happened.
spawnlives said:
In the link provided by @lbuprophen use the arm64 zip uninstaller (latest version) to uninstall exposed.
Just curious how long did you let it try to boot for,mine took 10-15 minutes for it to do it's thing and boot up.
Click to expand...
Click to collapse
I waited over an hour for my phone to boot, before and after flashing the uninstaller. I also tried wiping it and even completely formatting the data, everything without any success. It kept on not passing the Samsung screen and eventually bootlooping.
I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now.
Thanks for the advice anyways!

Emilia-Chan said:
.... I fixed the issue by just flashing the stock rom with odin and then reinstalling TWRP and rooting my device again. Will stay away from XPosed with this phone for now. Thanks for the advice anyways!
Click to expand...
Click to collapse
You did what I would have probably done myself in this situation by starting from scratch.
I just wanted to let you know that I believe that I had saw somewhere (within the dedicated area of the forum for your device) that individuals were successful with Magisk XPosed.
Though I do understand if you want to stay away from XPosed until your ready again and I'm happy to see that your at least up and running again.
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT provide support via PM unless asked/requested by myself. PLEASE keep it in the threads where everyone can share.

I got the same even just after the installation of the apk for Systemless Xposed on an Xperia (XposedInstaller_3.1.5-Magisk.apk) found here: https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268
I made a reboot as I like to isolate the issues while they happen. That was it: bootloop..

Stuck in Bootloop after installing some Modules

Hello everyone,
I used Xposed for some days and I didn't have any issues. Yesterday I tried out some new modules and now I'm stuck with my rooted Galaxy S6 in a bootloop.
In most Solutions it is said that you have to remove "modules.list" form /data/data/de.robv.android.xposed.installer/conf/
but I don't have a /conf folder.

S4drazam said:
Hello everyone, I used Xposed for some days and I didn't have any issues.........
Click to expand...
Click to collapse
There's a few other possibilities you can try...
The following thread is specific to the "Xposed Modules Desactivator".
https://forum.xda-developers.com/showthread.php?t=3372942
I can't endorse that myself since I've never personally tried it before but, it seems to work for some members.
You can also go to the bottom of the following threads OP and use its attachment...
https://forum.xda-developers.com/showthread.php?p=24267797
... that's named the "Xposed-Disabler-Recovery".
It's a Recovery Flashable zip file aimed at just disabling XPosed itself and the modules won't load if it's disabled.
In addition regarding the disabler zip, it basically does the same thing via recovery as if you had opened up the XPosed Installer app and selected to turn it off. Then if you wanted to Enable XPosed, just open up the app and select to turn it back on again (of course you'll have to reboot the device to complete the Enabling of XPosed).
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900V device.

S4drazam said:
it is said that you have to remove "modules.list" form /data/data/de.robv.android.xposed.installer/conf/
but I don't have a /conf folder.
Click to expand...
Click to collapse
Or from /data/user_de/0/de.robv.android.xposed.installer/conf/ depending on your Android version.

Unfortunately none of it worked for me. I ended up doing a nandroid backup and flashing a random stable rom without doing no wipe before. Afterwards everything was fine again