yashsingh1/xdaforums huggingface dataset:
[Xposed General] KickerTom:
Using Cm13 on i9100 with Xposed for a while and no problems. Was it a clean flash?
[Xposed General] stylemessiah:
Hahaha i figured it out, my phone switches off with Deep Sleep Battery Saver, which disables connectivity.

When i manually re-enabled connectivity and loaded xposed app, no issues

Disabled connectivity and opened app..error

Its just down to the app checking online for framework version and/or module updates

Sheesh!

Perhaps they should amend the error to point out its connectivity based...."error loading xposed zip frameworks...check your connection"

Looking back i should have realised that the "loading zip" in "error loading xposed zip frameworks"

related to not being able to check online, but its late :)

Anyways, if some other tired person, or newbie has the error, this will be there in the search results :)
[Xposed General] cyarlos:
"the latest version of Xposed is currently not active.did u install the framework and reboot ?" i tried sdk22arm64 and sdk23arm 64. what do i try now ?
[Xposed General] ch3mn3y:
Which version of Android and what device do You have?

Sent using C6833 - AICP/GreatDevs
[Xposed General] phpbb3:
The op doesn't have much current information. Could someone explain to me the difference between rovo89's arm v80 sdk23 and [MENTION=2476451]romracer[/MENTION]'s?
[Xposed General] kerpert:
Hello, which v80 version I have to install for my galaxy nexus?
[Xposed General] Portgas D. Ace:
Most likely xposed_v80_sdkXY_arm.zip

where XY is

21 for Android 5.0.x

22 for Android 5.1.x

23 for Android 6.0.x
[Xposed General] kerpert:
Thanks for clarify.

I flashed the 22 but can't active it.

I have zmod 5.1.1.

I had a previous version of xposed and it worked well, now this v80 won't be enabled.

Any suggestions?
[Xposed General] Portgas D. Ace:
What do you mean by "can't active it"? Any error/notification within the Xposed Installer app?
[Xposed General] grep_i:
Screenshots of log files are appreciated at this moment or else it will be very confusing to anyone
[Xposed General] jason504:
It seems just when we get xposed and all of the modules working. They come out with another version of Android. Already on N....... ETA? Ha ha just joking.
[Xposed General] kerpert:
Hello, I have solved with a clean install: disabled all module of course, deleted xposed "interface" app and applied xposed uninstaller from twrp, then restart to system, then again in twrp for install new xposed, restart in system for install the app "interface", all work but all to resetting [emoji6].
[Xposed General] grep_i:
Good to hear that you succeeded in resolving the issue, great work man
[Xposed General] RellyABadBoyz:
I using Sky A 850 and rom cook RR 5.1.1. and give me xposed version can work on my phone. Tks
[Xposed General] PereGR:
did you flash sdk22 or sdk23??
[Xposed General] jeemer:
anyone know if this works on 6.0.1? i've got a sm-g935f.
[Xposed General] Darke5tShad0w:
Yes it does.
[Xposed General] DjDiabolik:
wait for v81 sdk22 and unistall by romracer.... (i have ever use it whitout problems... because change? :) )
[Xposed General] 13695ty:
Could you send me the version of v73 sdk22?Thanks!:)
[Xposed General] grep_i:
If you followed the forum rules you could easily have found this yourself.

You could have read the first post which links to the official thread with download links to the files

http://dl-xda.xposed.info/framework/

Another option was using a search engine like Google it really gave a lot of hits on this search it really is not hard to find.
[Xposed General] maxxxz:
Sorry, I read a lot, I'm on Omega Rom 5.0, I know it says this framework don't work on it, but my xposed says installed but not active, other user give me this answer http://xdaforums.com/showpost.php?p=66460747&postcount=11589, should I install this framework? The log is in the link. Thank you.
[Xposed General] xringo:
I downloaded this "xposed-v67-sdk22-arm-by-romracer-20150716.zip" and flashed it on a stock, rooted with twrp recovery on a note 4 n910c. It's stuck on bootloop. Anyways which uninstaller do I use? I am guessing its this one "xposed-uninstaller-20151218-arm.zip"
[Xposed General] Portgas D. Ace:
Correct.

By the way, what Android version are you currently running? 5.1.x?

Did you try the latest version v80 instead of v67?
[Xposed General] xringo:
5.1.1 tried the , 67. Will flash the uninstaller and see
[Xposed General] grep_i:
Is a note 4 not a Samsung device, therefore you need a specialized Xposed version.

Wanam Xposed from developer arter97 search the forum for the right thread. Your now in the generic section
[Xposed General] Friedensfurz:
I'm using Sdk22 v.80 on my s5 mini g800f android 5.1.1 without any problems :)
[Xposed General] Scientist07:
It's up to version 82 now. You might need to upgrade to get it working properly.
[Xposed General] xringo:
Will do. Thanks.
[Xposed General] robot_head:
I really need sdk19 arm. Searched everywhere and i can't find it. Anyone have a copy or a link?
[Xposed General] Portgas D. Ace:
SDK19 = Android KitKat.

This thread is for Android Lollipop and above. Check this thread instead.
[Xposed General] robot_head:
I know, searched everywhere, forgot that kk is just an app, had to use older apk for install. Sorry for wrong thread.
[Xposed General] garrett69:
How does one go about getting xposed framework on their system without a custom recovery. Just curious if its possible.
[Xposed General] Portgas D. Ace:
FlashFire or Flashify might be possibilities.
[Xposed General] xXCoolGuYXx:
Where the xposed 82 link ?
[Xposed General] Portgas D. Ace:
Not available yet. You could try to install the official Xposed version by rovo89, which will most likely work on your device.
[Xposed General] xXCoolGuYXx:
Thanks do you know where that link would be? Am on the lg g4 h811 mm 6.0.1
[Xposed General] RASTAVIPER:
At my Chinese device it's very easy to install it just by running a script.

I don't have a custom recovery.

Unleashed by my M1 NOTE
[Xposed General] Portgas D. Ace:
Sure, check this thread, especially post #1.

LG G4 = ARM64 (the LG G4 has a Snapdragon 808 CPU, which is ARMv8-A = ARM64 according to this webpage)

Android 6.0.1 = SDK23
[Xposed General] grep_i:
Yes it's possible just use script manager for it
[Xposed General] tsrajput:
it's happens when some times xposed log file deleted by it self or gained wrong permission again very easy solution

open root explorer and goto

root/data/data/de.robv.android.xposed.installer/log

now create a text file here with name error.log and give permission rw-rw-rw and save it now reboot and done
[Xposed General] soosoolhastam:
Romracer, will you update xposed 84?
[Xposed General] grep_i:
Is there a special reason for this question ? You can install official version v84 from [MENTION=4419114]rovo89[/MENTION]
[Xposed General] soosoolhastam:
I installed it. now my devices doesn't load android ; (
[Xposed General] erzherzog:
I also got this problem and could solve it by installing the uninstaller first. That means: remove v83, wipe cache, install v84.
[Xposed General] grep_i:
Can you tell specifically which .zip you installed and which method you used ?

Is it also possible for you to upload Xposed error.log ?
[Xposed General] magas123.6:
How can I check my device ARM?

Στάλθηκε από το Lenovo K50-t5 μου χρησιμοποιώντας Tapatalk
[Xposed General] marcdw:
Install any system info app and you'll get all the info you need.

LG G3 D851, PAC-MAN ROM, Tapatalk 4.9.5
[Xposed General] Laurcenfosi:
Framework version

I'm running cm12. 1 Samsung Galaxy Note 3, does the expose version specific for certain devices? For example xposed v72-v84 still under sdk22. Thanks
[Xposed General] grep_i:
It's more like specific Android version

SDK21 Android 5.0.x

SDK22 Android 5.1.x

SDK23 Android 6.0.x
[Xposed General] maybeme2:
I have a new rooted nexus 5 running stock 5.1.1 and twrp recovery.

I downloaded sdk22 for arm and installed it through twrp install.

The phone took a long time booting (optimizing apps) and then booted into 5.1.1.

Problem: How do I start xposed so I can download modules. I cannot find an app icon for xposed.
[Xposed General] dragoi90:
Have you installed the xposed apk from XPOSED official thread?Install that,then reboot from the apk and give root permission.Then you can install modules.
[Xposed General] joy_fun_man:
After flashing through twrp install you must install XposedInstaller_3.0_alpha4.apk by normal mode

Tap & Talk Nexus 7
[Xposed General] Lamarckk:
Anyone knows a method to stop Google Play Services FC in Lenovo Vibe K5 after installing Xposed?

Note:

Issue on every gapps

Wiping cache won't solved

It's impossible to use the smart cuz it keeps spawming FC
[Xposed General] romracer:
New update!

Systemless support has been added to Xposed and XposedTools. This means Xposed can be built from source (and open source components) now by XposedTools.

Details on the support can be found in this commit. Huge props to [MENTION=4470081]topjohnwu[/MENTION] for pioneering this!

Head to the OP (or HERE) for downloads!
[Xposed General] grep_i:
Just flashed it without any problem, great work
[Xposed General] soosoolhastam:
Could we get the uninstall package again?
[Xposed General] topjohnwu:
Nice work romracer :), happy to see people contributing to the systemless business.

Actually I have planned to compile Systemless Xposed from source, but I'm stuck with school finals and cannot find time to dig into XposedTools.

I briefly checked your commit, and immediately found a small issue:

It seems that you didn't include the service "xposed_cache" into init.xposed.rc. This extra step might look meaningless and redundant, since the "mount_xposed.sh" looks like it can handle the cache merging process without issues, but actually I did this for some reason.

The trigger "post-fs-data" will be triggered twice on an encrypted phone. The first time will be triggered on late-init, the second time will be triggered after vold decrypted the data partition (on property:vold.decrypt=trigger_post_fs_data).

In the mount_xposed.sh you included, when script is executed in the first post-fs-data, it will never merge the two images; instead it will always move /cache/xposed.img to /data/xposed.img because data has not been decrypted yet.

What's even worse is that since data is not prepared properly, moving xposed.img into data will result in a failure and cause the device stuck at boot.

There is actually a way to overcome this: detect the property "vold.decrypt" before the merging process.

This will cause another issue: un-encrypted devices will not be supported. Those with data un-encrypted will not have the property "vold.decrypt" set.

However, this is actually minor and trivial since un-encrypted data "should" always be mountable in TWRP. But to prevent any /data mounting failures in recoveries, I simply just separated the merging process into a service which will be called on "late_start" (the same time SuperSU will be started).

The merging process is not as time-critical as the bind_mounts are, so we can take our time :)

Regarding the the flashable zip part, I have a few things to say:

I don't see the point in creating different zips for each individual architectures. The result zips are relatively small (< 20MB), so size is not an issue.

Actually, the flash script already have a very precise platform detection, so creating an combined package shouldn't be an issue too.

I guess rovo might have decided to do this for some recovery compatibility concerns: an updater-binary (which is platform dependent) is included in the package.

But Chainfire has handled "all in one platform" releases for his SuperSU all the time, and it has been flashed across all kinds of devices for millions of times.

Since CF doesn't bother to include an update-binary, I think it is safe to say this concern should be unnecessary.

Well since mentioning the installation of Xposed, I have some thoughts:

Systemless installed Xposed will not mess with system files, so it is safe to install it through an app now (just like the pre-lollipop days).

Maybe we can add this feature back to the installer :p, it might be nice
[Xposed General] romracer:
I had already written systemless support into Xposed (easy to do) but I never found the post-fs-data in init and eventually ran out of time to mess with it. That is really the key to getting /xposed mounted soon enough to replace the Zygote. Great find by yourself.

Awesome explanation! I had wondered what that service was for but TWRP can decrypt my /data and I haven't had time to run through the other various test scenarios. I added it back in this commit.

Version 85.1 zips are available with this change.

I don't disagree with you here :) I was just trying to not deviate too far from what [MENTION=4419114]rovo89[/MENTION] has already released. In my opinion, one way to approach this might be to add support to XposedTools to build an "all in one" version. Then an AIO version could be built and used by those people with no problems using it, and individual versions could also be built for those who have trouble with the AIO.

I do think there is real value in using the custom BusyBox. Since all of the commands used in the flash script are either applets in BusyBox or provided binaries, it reduces a lot of the complexity in the scripting (ex. see all the various permutations to calling chcon in SuperSU).

update-binary is just BusyBox as I'm sure you noticed :) In an AIO version, I think update-binary could be a simple shell script as you have done that extracts the platform bits and just calls "busybox ash" with flash-script.sh.

I think you're right. It might be a little messy messing with boot while booted on some devices, but maybe not.

I did want to add the support for systemless into [MENTION=4419114]rovo89[/MENTION]'s installer. I prefer the material one, but official support would definitely need it in the official installer.
[Xposed General] d.casper.b:
Thanks for all your work.

I've just updated my phone and think that this time round I'd better go systemless to avoid all that hassle...hopefully.

Do I just flash the systemless zip or must I do something first?

For SuperSU (BETA-SuperSU-v2.67-20160121175247) I went into the terminal in TWRP and typed this before flashing the zip (on my first try with supersu, when I just got my phone, I just flashed and then I couldn't boot into the system):

"echo SYSTEMLESS=true>>/data/.supersu <enter>

echo BINDSYSTEMXBIN=false>>/data/.supersu <enter>"

While this is still a WIP, I may as well ask now: for updating, is it safe to just install the update over the old installation (as per pending instructions)?
[Xposed General] rovo89:
I won't release all-in-one ZIPs, I don't think it makes sense to make people download a file that is much bigger than what they need. It would also increase the traffic and number of simultaneous connections on the download server that XDA provides. It's simply a waste of resources for everyone. I understand the motivation though, an easier (official) way to find out and download what you need would be good.

Oh yes, that really made a big difference. It makes the flash script much more reliable and cleaner.

Even extracting can be a problem sometimes though... I couldn't release signed ZIPs for the first versions before migrating to the custom BusyBox because some recoveries' unzip command couldn't handle signed ZIPs.

That said, I'm all for official systemless support - but not if it involves modifying the boot image or things like that. Getting this work on the variety of devices and ROMs which are out there is just too complex. Chainfire already does that work, so I see no reason to duplicate his work or reinvent the wheel. If/once SuperSU supports calling su.d scripts in post-fs-data, I will look into it again, but the approach taken in the unofficial versions isn't supportable from my point of view.
[Xposed General] romracer:
Just flash the zip. You don't even need SuperSU, but it won't hurt either.

No such commands necessary for Xposed. For updating, it is safe to simply flash one systemless installer over the next. No need to restore anything first.
[Xposed General] romracer:
Fair enough. I run my own server farm with unlimited bandwidth (just metered) so perhaps I don't think about that. Perhaps a website that let's you pick your device, or your SoC in the case its some obscure device. I suck at web design. Maybe an extremely small zip that simply detects your architecture and tells you what to download? Its a two step process if you don't already know but it sort of goes with your "small and fast download" mantra :)

Oh I remember. In fact, some TWRP builds were "OEM" builds or something and didn't even have unzip, so you couldn't even get that far. But to be fair, that broke SuperSU too (and probably a hundred other things).

Fair point, and correct me if I'm wrong, but I believe sukernel still only handles Android boot images. And using su.d at post-fs-data just introduces a dependency on SuperSU that not's really necessary. Personally, I'd wish sukernel was open source, and then we all could use it a lot more comfortably. Absent that, the tools I use still only support Android boot images. And its still entirely possible to build non-systemless versions (as I have done) when device compatibility is missing.
[Xposed General] d.casper.b:
Don't the modules need SuperSU (root) or is xposed giving them all the permissions needed? Or I assume, you're just stating that it will install without SuperSU, which I do understand.

Flashed perfectly and apps are almost done optimizing! EDIT: Hmmm, after installing the xposed apk 3.0_alpha4 it tells me the framework is not installed...

Quick, sort-of off-topic question, if I may:

I'm trying to understand the benefit of systemless when it comes to OTA. If the boot image is patched, then that means...we must flash the original boot image before accepting an OTA (and I assume also the original recovery since we are using TWRP)? Just trying to grasp the exact benefit of systemless when it comes to OTA. I just did an update with a non-systemless xposed so with this update I had to start fresh with a stock firmware and then update - I guess I'm looking to avoid this scenario in the future.

Thank you so much [MENTION=2476451]romracer[/MENTION]. You've been doing a good job. I first used your work when you brought xposed to 5.1.1 on my old RAZR.
[Xposed General] romracer:
Not every module needs root access. But yes, my statement was meant at "SuperSU it not required for installation". If you use modules that need root access, you'll still need a su implementation.

Sorry I haven't had time to patch the official installer. Probably today. Use the material installer from here instead (I like it better anyway, but that's my own opinion).

It probably depends on your vendor/ROM manufacturer. But the AOSP implementation for an update and those based on it do not perform boot partition verification. They simply flash a new boot image over it (and often use that to patch a new recovery too if you were just a regular user). There are checks for the /system partition (often at the block level) which is where the benefit in an OTA comes in with systemless Xposed/anything.

Additionally, Android Pay uses SafetyNet which in turn uses parts of the compatibility test suite and there are checks related to /system there, too. The material installer has an option to disable Xposed (or you can disable Xposed with the "disabled" file), which if used prevents Xposed from being loaded on reboot (app_process32/64 is not bind mounted). This might allow you to use Android Pay, since the systemless Xposed has not touched /system. If you use SuperSU, you would need to toggle it off via its app as well (I don't think you have to reboot for it though).
[Xposed General] topjohnwu:
I'm afraid even if SuperSU is moved to post-fs-data, the mounting should fail too. It is still not early enough.

I've tried not to use the exec command in init. If I bind mount the files in a new service started on post-fs-data, the results will be a hit-or-miss.

Services can be run simultaneously with other services. This is why it got random results: even if the mounting service is started before zygote inits, sometimes the bind mount happens first, sometimes zygote initializes first; there is no guarantee.

On the other hand, the exec command will block everything before it finishes. So exec serves the mounting purpose really well: nothing will continue unless the bind mounts are done.

Unless Chainfire pauses the boot process until all su.d scripts are done in future SuperSU releases (I doubt he will do so, because it can lead to devices stuck at boot if scripts without special handling are placed there), the bind mount still won't kick in soon enough.
[Xposed General] romracer:
I uploaded the installers that used to be in the OP to the uninstaller folder on the download site.
[Xposed General] soosoolhastam:
I see

Thanks buddy!
[Xposed General] romracer:
I added a patched installer to the OP if you prefer the original. Should work with system or systemless Xposed.
[Xposed General] HorstiG:
[MENTION=2476451]romracer[/MENTION]

Great, realy great.

So quickly my phone has never been online after reboot. (10 Modules)

LG G4 H815 Stock M with root SuperSU and Xposed.

Thank you!!!

I don´t believe it anyway. :D
[Xposed General] AnonVendetta:
@ romracer: Why did you completely remove all the files for 5.1.1/SDK22 (LP)? The only files I can find are the ones for MM. Do you plan to re-add them later?
[Xposed General] mayank22:
this thread is only for systemless xposed that works only on MM, for normal xposed there is a different thread that has both LP and MM files
[Xposed General] dinkss86:
OnePlus 3 Support

Hi there, will xposed work for OnePlus 3? Is it straight forward to install or do I have to go through some steps?
[Xposed General] romracer:
The SDK22 versions offered little over the official release except in the rare case your /system partition had very little free space. They were no longer updated and the OP only had uninstallers for many months.

I've had a little time today to build and upload SDK22 versions of my new release. These might (should) work systemless on Android 5.1. I would be glad if people could tell me. This is a great alternative to the "very little free space" problem.

There are also non-systemless versions available, but these really aren't any different than the official release. I just build them all to test the tools.

OP3 should be arm64 SDK23. Give it a shot. You'll need a custom recovery. Think that's about it.
[Xposed General] g2uzer:
Thanks for the hard work! I'm getting ready to clean flash this as soon as PureNexus update gets released but my question is if uninstaller 2015831 still works for the systemless xopsed
[Xposed General] romracer:
The uninstallers have not been updated to remove systemless yet. Deleting xposed.img from data should be enough or just flash one systemless over the next. The uninstallers will remove a system install, but so will flashing a new ROM.
[Xposed General] Hamidreza_4u:
I have a Xperia C3-Dual on stock rooted room.

I very tried to install and use xposed on it but I can't do it.

Anyone can help me plz

sent from my Xperia C3-Dual
[Xposed General] Minanapil13:
Sm-g361h

Hi every one i need to know what version of framwork i should to download for samsung core prime dues

ARMv7

Sdk22

Armeabi-v7a

For model : SM-G361H
[Xposed General] grep_i:
I heard Sony xperia devices are special devices so there must be a specialized thread around here use the search function on the forum to find it.

There will be other people with Sony experia devices with device specific knowledge

---------- Post added at 10:25 AM ---------- Previous post was at 10:21 AM ----------

For stock rom touchwiz you could try [MENTION=3562083]wanam[/MENTION] version.

Custom rom CM / AOSP you could try original [MENTION=4419114]rovo89[/MENTION] version

---------- Post added at 10:31 AM ---------- Previous post was at 10:25 AM ----------

Thanks for updating it, used the material design version for some time but like this one better.

It's cleaner in my opinion and does not come with bells and whistles I will never use.