yashsingh1/xdaforums huggingface dataset:
[Xposed General] fabietto081086:
Hi guys, I have flash last version of this xposed framework on my lg g6 (stock version v20c).

Flash are ok but my g6 are full of lag.

Any solutions?
[Xposed General] HamidZaeri:
Hi

Where can I get older versions of systemless Xposed? Like 90 b1 or b2

---------- Post added at 09:33 ---------- Previous post was at 09:33 ----------

Hi

Where can I get older versions of systemless Xposed? Like 90 b1 or b2
[Xposed General] ravijot:
Thanks. It worked fine of H8P

---------- Post added at 02:47 AM ---------- Previous post was at 02:41 AM ----------

Thanks. It worked fine of H8P
[Xposed General] z4ck1n:
Bootloop on MiUI 10 (sdk 27) with v90.2-beta3

log -> https://www.pastiebin.com/5bdb1fec26b56
[Xposed General] NTWarrior:
I have the Magisk version of Xposed at the moment but I can live without SafetyNet; is the normal version any more or less stable than the Magisk version, particularly for Facebook Messenger crashes?
[Xposed General] zoel.fahmi:
Type it correctly
[Xposed General] orangzeb:
Hey, I have D6603 xperia Z3 which has carbon rom 8.1 installed.. alongwith Magisk manager. I'm having problems with my proximity sensor and would like to disable it via xposed module but it's not just working, What am I missing?

Plz help. Thanks
[Xposed General] amg314:
I am Chuwi Hi9 Air tablet user. It work under Oreo, have root from Magisk 17.1 and I use Xposed as well.

All is fine, except nonworking TWRP 3.2.2 due to data encryption in the latest firmware installed(((

Is there any method to decrypt data using Magisk (or any other instruments)?
[Xposed General] firemaker911:
Hi Users/Developers

Have This Firmware Installed

(Screenshot-Picture)

On My Lenovo K3-Note And I

Try A Lot Of Xposed-Framework-Modules.

But Nothing Works, My

Cellphone Stay In The Bootloop

And A Lot Of Xposed-Uninstallers

Doesn't Work & I Have To

Install This Firmware From The

Beginning....!!!

Can Someone Help Me With

A Solution?

Thanks
[Xposed General] KevinX8:
You need to use the sdk 22 version also xposed Uninstaller won't work on systemless xposed as it is stored on kernel not system, you can simply flash the stock kernel over again to uninstall or any custom kernel
[Xposed General] Portgas D. Ace:
To uninstall systemless Xposed, delete xposed.img under /data via recovery.

Quite confused, what are you talking about? Since when does Xposed has anything to do with kernel?
[Xposed General] KevinX8:
Um dude this is the systemless xposed thread, it has everything to do with it. It installs itself to your boot image which is a combo of your ram disk and kernel so yeah, you kind of need to install a new kernel to truly get rid of it
[Xposed General] Portgas D. Ace:
*self-facepalm*

Of course, totally forget about the patched boot.img :silly:
[Xposed General] firemaker911:
Thanks For Your Support But

My Problem Is To Get The

Xposed Framework Work With

This Firmware Without Bootloop After The Install From The Recovery....

Xmaster24, I Try The sdk22-Version Of The Xposed Framework But With The Same Result....

I Don't No Why....
[Xposed General] KevinX8:
K did some googling and yeah the stock rom for K3 note DOES NOT work with any xposed, you will have to get a custom Rom to run xposed
[Xposed General] firemaker911:
Xmaster24, You Are Wrong,

I Don't Use A Stock Rom....!!!

It Is A CustomROM, Calling

"Pekk3nDroid K3 1.0" With Lolipop 5.1 Inside!!!

Can You View Pictures?!

Here I Go Again&Again&Again:
[Xposed General] KevinX8:
Bro your rom has been dead for a year I recommend upgrading to 6.0 it's been out for ages I have no idea why it thosent work with your rom as it says it is AOSP but really using a dead rom is an awful idea for security and support reasons
[Xposed General] pbanj:
am i blind or is there not an arm 64 ver of the .7 release
[Xposed General] Darke5tShad0w:
As stated in the OP its now an all in one zip, it will automatically install what it needs.

You only need to know what version of android you have.
[Xposed General] pbanj:
yup im deff blind as i looked in the op for something like that -_-
[Xposed General] crysen:
If I have the normal Xposed v85 ARM64 installed already, do I have to uninstall it first or wipe something before installing systemless Xposed?

Thanks in advance!
[Xposed General] Ja_som:
Read:
[Xposed General] crysen:
I did, but I was wondering if it's possible to dirty flash since it's only a recommendation.

And if yes...see above
[Xposed General] Ja_som:
If you want OTAs in the future, you need to have untouched system... Also you need to uninstall system Xposed if you want to use systemless version. You can't use both...
[Xposed General] Portgas D. Ace:
Restoring your stock system seems a bit overkill IMO. Flash the Xposed uninstaller.zip through recovery, wipe cache&dalvik, reboot your device and let apps optimize, then boot again into recovery and flash systemless SuperSU (if you haven't already done it), then flash systemless Xposed. Reboot without wiping cache&dalvik.

This way has always worked for me (even without rebooting between uninstalling old framework and flashing systemless one).
[Xposed General] Ja_som:
Did this work also with OTA? Because it does not matter if you use Xposed uninstaller, system will be still modified, so OTA should not install...
[Xposed General] crysen:
So to be clear:

When I uninstall my current modules + system Xposed and afterwards flash systemless Xposed, it wouldn't work?

So it's not a recommendation to revert back to stock?

Then the "(Recommendation)" in the OP would be false?

---------- Post added at 12:35 PM ---------- Previous post was at 12:33 PM ----------

Thanks, that's exactly what I wanted to know! Cheers! :)
[Xposed General] Portgas D. Ace:
To be honest, I don't know as I don't use OTA updates at all. Flashing-addicted :p

But I guess you are right when it comes to OTA and unmodified system, a clean flash of the ROM will be neccessary to make it work when coming from "normal" Xposed.

You are welcome, but see my reply above for further information.
[Xposed General] The Analog Kid:
https://xdaforums.com/android/software/universal-dm-verity-forceencrypt-t3817389/page14

---------- Post added at 09:07 AM ---------- Previous post was at 08:51 AM ----------

Back then (when on 5.1) I've just pressed on "install update" and Xposed installer found the right version and installed it for me. That's what I mean. I can remember as well, that I did the same on my former G4 Plus under 6.0 MM.... Now on 8.0, systemless version installed with Magisk didn't even work for me, so I've uninstalled it, and installed official Xposed with TWRP. That is working. Yes, it won't pass "SafetyNet", but I don't really care about it.
[Xposed General] :
The Xposed installer apk link from first post is broken. It reopens the thread instead of downloading a file.
[Xposed General] DeebWeb:
Good day everyone! Please tell me how I can fix the error ?

Can module ISA µg NanoDroid to be a mistake ?
[Xposed General] jain2098:
I am using Redmi Note 3 SD with MIUI 8 (V9.6.3)

I successfully Flashed Magisk but every time when I flashes Xposed it Cause Bootloop.

I tried 3-4 times and same Happenning.

Please Help If anybody knows the Solution.
[Xposed General] himanshujain0052:
Redmi Note 3 (MIUI9) V9.6.3.0

I successfully Flashed Magisk but everytime I try to flash Systemless Xposed from the magisk manager it causes me BOOTLOOP. Even I tried to flash lazy Flasher but ididn't work as bootloop still remains. I had to reflsh stock rom to get back. :crying:

Please Give the Solution to install Magisk Xposed.

Thank You
[Xposed General] Zentenario:
Ho guys, same here. I'm on a Galaxy Note 4 (SM-N910F) with stock Samsung ROM 6.0.1. I've read about specific issue on this platform. However:

1. When I try direct Xposed installation through Magisk (Xposed 89.3 SDK 23) it seems to be correctly installed. When I then press reboot button it appears the aforementioned bootloop. Well, actually it doesn't look like a typical bootloop; it's like if it gets stuck at the initial sparkling Samsung screen. I've been waiting even for hours but it never starts. Then I have to start with TWRP, go to the file manager and erase /data/adb/magisk.img for it to start adequately.

2. When I search for Xposed 87.3 (SDK 23, wanam-based version) zip into the Magisk modules it doesn't appear in the list. Then I have to download it from this thread. I try to flash it through TWRP and it fails. It appears that "Magisk is not properly installed or simply missing, just because it searches for magisk.img in /data, but my Magisk installation is on /data/adb.

Could someone on a Samsung Galaxy Note 4 give me some light on this?

Other workaround that could help me too, if not possible to install Xposed framework: are there similar Magisk modules to Xposed All My... and Firefds? Basically what I want to get with these Xposed modules is overpassing Samsung restriction to be able to use the fingerprint from the initial boot and to see SSID name in the WiFi and BT quicksetting tiles when connected.

Thanks in advanced.

Enviado desde mi SM-N910F mediante Tapatalk
[Xposed General] IT_Fan:
Bootloop on MIUI 9.6.10.0 (ODGCNFD) Android 8.0.0 :(
[Xposed General] Ibuprophen:
If needed, I've got an Unmodified copy of the Official Magisk XposedInstaller v3.1.5 app on the following link.

https://www.androidfilehost.com/?fid=11410932744536986734

_____

The following link has the same app but, with the Repo URL Fix made.

~DELETED (DEEMED AS UNABLE TO FIX THE REPO URL~​

I was previously asked by a few members if I could fix the Repo URL for the Magisk XposedInstaller app (as I had done with Rovo89's app).

Though there's many members who are able to get the Repo Error going (Magisk, Rovo89's and DVDandroid's too) but, there's many who just couldn't get it to stop reflecting the Repo Errors 301/302. So I got them going for those who want them.

I'm just trying to help out here the best I can... :)

Enjoy!

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
[Xposed General] turb1te:
I have bootloop after installing latest systemless xposed (sd25) on my Nokia 6 (TA-1033).

I'm using Magisk 16.1.

Any ideas ?
[Xposed General] amg314:
I suppose you did not install Magisk systemless Xposed over common system Xposed?

To remove Xposed module you need to flash Magisk-Xposed-Uninstaller

[https://xdaforums.com/showpost.php?p=72542167&postcount=242]

If it does not solve the problem, try to flash Magisk Folder Mount magisk-foldermount-v0.8.7.1.zip

https://xdaforums.com/apps/magisk/module-magisk-foldermount-v0-8-t3591215

https://www.androidfilehost.com/?fid=889764386195917003

Then open TWRP file manager and manually remove /Xposed directory inside /magisk directory.

Reboot to system.
[Xposed General] turb1te:
After removing the magisk systemless xposed module via uninmod, I no longer have a bootloop. This is not problem. But I want to make xposed to work normally without a bootloop.

Latest xposed cause bootloop, and latest systemless xposed cause bootloop.
[Xposed General] Izzysoft:
Have you considered updating Magisk itself? 16.1 is far from being the latest version; IIRC it's much older than the latest Xposed mod you want to use. Might help, though I cannot tell for sure. I'm running Magisk 17.1 with Xposed and have no such issues (but neither I have your device).
[Xposed General] miss_p1nky:
Hello I'm using Samsung A5 2017, Oreo 8.0, newest Magisk, and Xposed v90.2-beta3. When trying to update my Download list, I always get: Downloading http:dl.xposed.info/ bla bla failed:302 (moved temporarily). How to resolve this please? Thanks!
[Xposed General] spawnlives:
You could try clearing cache and data of the installer app check modules/settings and reboot

Or if that does not work:

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/post78123269
[Xposed General] turb1te:
I don't know why but latest magisk also cause bootloop on my device... :(
[Xposed General] IT_Fan:
Hello,

I am using Magisk 17.1 on my Mi Mix2s with MIUI 9.6.10.0 stable (ODGCNFD) Android 8.0.0. I've tried both beta 2 and beta 3 of Xposed Systemless SDK 26 but all caused bootloop. Am I missing something ?
[Xposed General] Graddy01:
Messenger keeps crashing while having Xposed installed, using SDK27 version
[Xposed General] Nergal di Cuthah:
Are you using a xposed ad blocker. If so white list messenger in it. This worked for me and another who had this. If not please list all your modules.
[Xposed General] Graddy01:
I don't use it, only thing I was using was Gravitybox and Greenify modules
[Xposed General] Ibuprophen:
I just wanted to apologize to anyone who tried to install the Magisk XposedInstaller v3.1.5 app (that has the Repo URL Fix applied to it) and was unsuccessful due to a Signature Mismatch. :(

I had accidentally uploaded the incorrect app to the file host location I had provided. I'm deeply sorry about this mistake as it does happen even to the best of them.

I had ended up just scrapping it and started from scratch. Now I've got 2 members that's going to just test it out (since I can't use any PC till tomorrow to double check the signature).

I'm just providing the Magisk XposedInstaller app in response to some members asking me to perform the fix as I had successfully done with the ones from Rovo89.

I actually don't use Magisk myself (yet) to test on a device but, I do have to keep a certain working knowledge of it for other reasons.

I'll get back to you as soon as I receive a confirmation from those members testing it out.

Thank you very much for your time, patience and understanding with this accidental mixup. :)

EDIT: Deemed as unable to fix the Repo URL specifically for the Magisk XposedInstaller.

~~~~~~~~~~~~~~~

UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
[Xposed General] Graddy01:
Every version of Messenger above v189 is crashing with xposed installed for me
[Xposed General] Segelflugpilot:
I have a problem with xposed systemless too. Android 8 installed on my Samsung S7 with Superman Rom, TGP Kernel, before Superkernel (both same crashes apps like K-9 Mail, Pinterest sometimes). Xposed Modules are Xprivacy and Youtube Adaway. I have installed AdAway too (disabled and restart...same problem)
[Xposed General] The Analog Kid:
Thank you for sharing this process, but just to clarify: First thing to do is uninstall Xposed, right? Now, "classic mode" reboot means "system" reboot, isn't it? Also, which "last uninstaller zip for Magisk" would you recommend? There's a number of them, I guess... ?
[Xposed General] The Analog Kid:
I must confess I did something wrong from the beginning: due to (well, I say. Loudly) massive information overload, I completely dismissed the use of Xposed Magisk installer 3.1.5, so Xposed systemless appeared "not installed" in rovo89's Xposed installer; then I went straight to uninstall Xposed systemless with rovo89's uninstaller (the wrong part). After that, installed rovo89's Xposed over Xposed systemless, totally unaware that it was still in there. So far (ten days now) this apparently is not causing any freakin' issues aside from the "usual", apps occasionally stopping (don't know how frequent this behavior is considered "normal" these days") Point is, I should get rid of one Xposed. For peace of mind at least. I'm assuming Xposed systemless can be easily uninstalled by means of the trash can button in Magisk module section; am I right? Or should I go and use the flashable uninstaller, which I guess is mostly required for bootloop events?
[Xposed General] Rom:
Right :good:

Right :good:

From the official URL: https://dl-xda.xposed.info/framework/ , in the uninstaller section, take the latest one corresponds to the CPU architecture of your phone.

I understand your concern, and this may be justified in some way.

Basically, it is complicated to run the Xposed module delivered by John on a ROM setup with an old Xposed setup.

Add to that the cache and dalvik that must be removed for the user verification to be consistent, needless to say that the assembly of the whole thing can become quite complex. :rolleyes:

Now, regarding crashes in applications, since you are reporting this bug, i assume you have Android Oreo installed on your phone.

If so, that's why you're experiencing these application crash problems.

How can rovo help to correct these problems?

Report your bugs here with as much troubleshooting information as possible: https://github.com/rovo89/Xposed/issues

Don't hesitate to ask if u have another question(s).
[Xposed General] The Analog Kid:
Thanks for your kindness and prompt response. Yes, I'm under Oreo; but this apps stopping/force closing thing is actually not new; one way or another, I've been experiencing those since my very first rooted smartphone under Froyo, so I don't get caught by surprise, indeed...

Now, you're pointing me to the Xposed repo, for the Xposed uninstaller download; but I was referring to the dedicated "Magisk systemless Xposed uninstaller", which I could use just in case Xposed systemless can't be uninstalled through Magisk Manager by means of the button shown in the attachment. I think pressing that button should be enough since I'm not in a bootloop event...
[Xposed General] Rom:
I was referring to ZIP for uninstalling Xposed, because myself when i reinstall my entire phone, to get the Xposed module working again, i first install it hard, the old method via TWRP. I do this in order to save time to install in parallel the Magisk module created by John for the Android version i use.

I do this in such a way that the Xposed daemon files that are launched at phone startup are always present before Magisk even starts all the folder mounting work.

Indeed, it may seem a bit barbaric as a method, but would say the other one: "no arms, no chocolate".

And yeah, if you want to delete the Xposed module for Magisk, you can use the Manager as u show it in your screenshoot, it's make for this task, and yeah naturaly it works.
[Xposed General] The Analog Kid:
Interesting... In fact, we're all kinda "barbaric" just by rooting the phone; but you just have to go that way in order to get whatever your stuff doing what you want, I guess...

Alright; actually I'm unstalling both Xposed versions and start all over again as I should have... By the way, judging by the provided attachment, would you say that I'm actually ready to "go for Magisk' modules since data partition is already mounted read/write?... or I should install "F2fs fix"

by VR25 anyways beforehand...?
[Xposed General] Rom:
In principle Magisk should be able to manage even with F2FS. It's been a long time since i've used this format.
[Xposed General] don_dolarson:
Is there any improvement of uninstalling TWRP .zip version of Xposed and installing systemless Magisk? If yes, is there a some simple way to backup and all modules and load them all to systemless version? With all apps settings. Safety net does not pass.
[Xposed General] The Analog Kid:
Apparently the main benefits lie on the fact that Topjohnwoo's Xposed is also systemless (i.e. non system invasive) and it can be dissabled as a Magisk module from Magisk Manager in order to pass SafetyNet. On the other hand, I assume modules can be backed up with Titanium backup, or something similar, then reinstalled from there easily...
[Xposed General] don_dolarson:
Alright so it pass SafetyNet... because on the first page you can read that it can't pass it.
[Xposed General] The Analog Kid:
Yes, it actually won't... Unless you disable it in the Magisk manager and reboot, kind of an Xposed module. That's one reason for Xposed systemless as a Magisk module itself. Now, I haven't even tried, so I'm pointing you to what those interested in SafetyNet (me, I'm not) had tested.
[Xposed General] don_dolarson:
Alright, now I understand. That's a good point of having it systemless and disable if needed than uninstalled through TWRP with all modules gone if there's no copy.

How can I then copy all my Xposed modules and import them in Magisk? Just use Titanium Backup? How to restore them later?
[Xposed General] spawnlives:
Turning off/uninstalling exposed framework/installer does not delete or remove modules or it's data they just won't work.

If you uninstall then reinstall exposed it's just a matter of turning on/activating your modules in exposed installer and rebooting.

Exposed modules are like any other app on your phone so any app/or PC program that can backup/restore apps and data will work.

I'm using rovo's exposed version (not magisk) and turning off/disable (not uninstaling) exposed does pass safety net for me.

With exposed active the best I get is cts profile match true(pass) and basic integrety false(fail).
[Xposed General] Eleo:
From what I recall, turning off system xposed framework should start app optimization page which takes about 20 min average to boot and heating phone as hell (you need to reboot after disabling xposed for safetynet to pass)... And same for after enabling system xposed framework.On the contrary, when using systemless, the reboot takes as long as normal reboot takes.

What is your device model and android firmware/version?
[Xposed General] papuruth:
Any future update for pie users?
[Xposed General] Eleo:
Wait for rovo89 as always
[Xposed General] HsHTCsen:
Clearing data and cache worked for me, thanks! HTC m9 Lineage 15.1
[Xposed General] spawnlives:
For me the booting time only took a few minutes longer than normal and the phone didn't heat up much more than normal(only slightly).

Device:

Samsung S8(SM-G950f) - 64Gb storage, 4Gb memory

Stock nougat rom 7.0

Magisk 17.3/6.0.1 - 0 modules ,14 root apps

Rovo's exposed version 89/3.1.5 - 9 active/1 inactive modules.
[Xposed General] Ubay17:
Help

I want to download XposedInstaller who modified by topjhonwu, but it's fail.

I think maybe it's broken link:confused:, so anyone can help me to download that file please.
[Xposed General] Eleo:
Try this:

https://xdaforums.com/xposed/unofficial-systemless-xposed-t3388268/post77818423
[Xposed General] Ubay17:
Did'nt work
[Xposed General] BetaPix:
Hello guys, I'm on the latest stock 8.1 rom on my Xiaomi Mi A1 and somehow Franco Kernel is interfering with systemless Xposed. It is installed in the modules, but it doesn't get recognized in the Xposed installer (it says it's not active). Switching SeLinux to permissive fixes the issue apparently, but I don't want to fix it this way. Is there another solution?
[Xposed General] DallasBelt:
It's fixed now.

Xposed Installer 3.1.5 by topjohnwu.

I moved it to a new folder, sorry for the inconvenience.
[Xposed General] hh85:
Upd: Found a trick to keep the newest version of framework itself.

For those who suffered from 'error 302' in topjohnwu's module. The temporary solution is switching to rovo89's installer.

How to do it:

0. Some modules settings can be lost, so use smth. like Titanium Backup to save data.

1. Search 'xposed framework' in Magisks' 'Download' section.

2. Install that one which doesn't contain '(SDKxx)' in its name. Don't remove currently installed version, it would be replaced preserving your settings.

3. Download zip from http://dl-xda.xposed.info/framework/. Choose the latest one for your SDK version and architecture.

4. Now you need full featured filemanager e.g. Root Explorer. Go to /sbin/.core/img/xposed/system/framework. Rename existing XposedBridge.jar to smth. like *.bak. Extract system/framework/XposedBridge.jar from downloaded zip archive and move it to the path above.

5. Reboot device.

6. Run xposed installer app.

7. If it shows 'installed but not activated' status, toggle the switch to off then back to on and reboot again.

8. When everything is ok, delete renamed jar file.

When topjohnwu updates his installer we can switch back to it just by installing it to Magisk.
[Xposed General] The Analog Kid:
It's a rule for Xposed (system) uninstaller to leave behind file traces of the Xposed framework?... or this uninstaller I've used just did the greatest of jobs by actually leaving no traces of (system) Xposed to deal with manually?...

... Or perhaps there are some hidden files still in there that someone here can kindly point me out in order to get rid of?