arm64 is now officially supported: See here
Old OP
Hello Everyone,
I have successfully compiled Xposed for android 5.1.x for arm64 devices.
I have so far tested this on my Nexus 9 running a custom CyanogenMod based Android 5.1 ROM with SELinux disabled (It may work on ROM's with SELinux enabled but testing has to be conducted.).
Install zip is attached to this post. (The SDK 22 one) This will only install Xposed framework for Android 5.1 for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
I compiled this based off of @romracer's source code for Xposed on Android 5.1.x.
So far I have tested the module Lolistat, It seems to be working well.
Please be patient during boot, let your device boot 10 minutes before reporting that it is "bootlooping"
====================
For Android 5.0.x
I have also compiled Xposed for Android 5.0.x for arm64 devices. I have had mixed results from testers so far. The install zip is also attached to this OP (The SDK 21 one). Many HTC M9 users have reported this caused a boot-loop for them. This will only install Xposed framework for Android 5.0.x for arm64 devices. Please see the original Lollipop post to get the other files you need. (Hint: you only need the Xposed APK from that post.)
Remember to always backup all data before using. Use at your own risk.
Please note: There will most likely be arm64 related bugs with both of these. See this post for more information.
Please be patient during boot, let your device boot for 10 minutes before reporting that it is "bootlooping"
just in case...
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
I could also compile Xposed arm64 for android 5.0 if there is enough interest.
Sim-X said:
I got a new m9 in the box, thinking about waiting to activate it since xposed wouldn't work on it yet.
Click to expand...
Click to collapse
Somebody would need to be willing to test, but I could try to compile Xposed for it.
Well, if you're willing to test and support it, you can post unofficial files for testing...
I have a Nexus 9 with Android 5.0 myself and it's running fairly well. I haven't used any complex modules though.
Be aware that 64-bit ROMs need different handling in a couple of places and break some expectations. For example, initZygote() will be executed twice, as there are two app_processXX processes now. Modules might not expect this. I also didn't succeed to enforce a certain startup order of the processes (app_process64 before app_process32) yet, so results might be a bit random. There are probably more differences like this and it's generally more complex than on 32-bit ROMs. That's why I have only posted files for ARM so far. On the other hand, if you're willing to look into issues that come up (e.g. installation problems, crashes, things that are not working) and do some pre-analysis, that's fine and could bring the project forward. If nothing to major comes up, I can then also include official files with the next version. Additional support would be very welcome anyway.
Framework installation zip attached to OP.
good
Only for 5.1?
auggie246 said:
Only for 5.1?
Click to expand...
Click to collapse
I made a version for android 5.0 but I would need somebody to test it before I release it.
5.0 for samsung galaxy s6 ?
koko115 said:
5.0 for samsung galaxy s6 ?
Click to expand...
Click to collapse
Are you kidding? Move along!
subscribed.
Feel free to post any problems you have with this here. (arm64 related problems)
Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo
YouTube adaway works fine
For me
Guitarboarder28 said:
Rastapop 5.1 on n9 with selinux on. I can install xposed fine but rebooting after enabling YouTube adaway and gravitybox causes a never ending boot logo
Click to expand...
Click to collapse
From my understanding, gravitybox is not compatible with Android 5.1 at all.
joshuabg said:
From my understanding, gravitybox is not compatible with Android 5.1 at all.
Click to expand...
Click to collapse
Ohhh didn't even think about that. Would make sense
Thanks for taking this on, joshuabg. I couldn't believe it when I saw this thread. I thought that 5.1 jumped the arm64 shark and we'd never see xposed for N9.
Anyway, I flashed on AICP 4/6 with FireIce K8.3, SELinux disabled and it booted just fine. Tried the following modules, and I see what rovo meant in his post above. It's really hit or miss with the modules just like the [SUPER ALPHA] xposed for 32 bit arm devices. Thanks again for rolling this out to test.
YouTube Adaway - seemed to work, jumped to dozens of random videos and no ads
Minmin Guard - app opened and seemed to operate normally but I think it may have blocked ads across the board without my telling it to do so. I think it also caused an XDA Free force close on opening that wouldn't go away
Swype Tweaks - caused Swype to FC anytime the keyboard should have launched
Yup my bad. Gravitybox says right in the description it'll cause a boot loop on 5.1. Everything is working perfectly. Thanks!
Related
I want to start this post off with a couple of very clear points:
@rovo89 is the creator of the Xposed framework
This is a derivative work posted with his permission
This also means the following statements are true:
I have only worked to bring the Xposed framework to Android 5.1
I have only worked to bring systemless support to Xposed on Android 5.1 and 6.0
I have not rewritten the framework from scratch
With that said, I present to you my first unofficial release of Xposed for Android 5.1/6.0. It is my hope that ultimately my changes can be reviewed and an official release posted. But first, the bugs must be squashed! I've written a few Xposed modules that work fine but by posting this unofficial release, I hope to expand my audience of module writers and testers.
How To Test
You must be on Android 5.1/6.0. It will NOT work on Android 5.0 (too many changes to ART).
You should have a working recovery.
If you left the Xposed app installed from Android 5.0, you should disable all modules before installing this framework. Busted modules may keep you from booting after installation otherwise.
I will need Xposed logs (and possibly logcats) to debug any issues. Remember, if your device won't boot after installation, its likely you can reboot to recovery and still grab the Xposed log (assuming Zygote started). It will be in /data/data/de.robv.android.xposed.installer/log as error.log or error.log.old.
Known Issues
Devices with very little free space on /system may have trouble installing. Systemless installations are recommended if your device is supported. Non-systemless installs should be a last resort.
Downloads
First, I'm going to shamelessly point you to the original Xposed for Lollipop thread. Why? Because I want you to read it. This release hardly differs from that one. And maybe, just maybe, it'll save some unnecessary private messages.
Did you read the original Xposed for Lollipop/Marshmallow thread?
xposed-v??-sdk2?-*.zip - Must be flashed with a custom recovery to install the framework.
xposed-uninstaller-*.zip - Can be flashed with a custom recovery to uninstall the framework.
XposedInstaller_3.0-alpha*.apk - Must be installed to manage installed modules.
Use the correct platform and SDK version for your device. Google your device or look in build.prop if you're not sure.
Can't find some of the downloads? Surprise! They're in the original Xposed for Lollipop thread. They're unchanged, so there's no need to post them here too.
Module Developers
It would be incredibly useful to me for people to test the framework in the smallest "units" possible at first. By "unit" I mean things such as "resource replacement", "method replacement", "before method hooks", "after method hooks", etc. It doesn't do me a lot of good to know that some huge, complicated module causes system_server to crash without understanding at what level that's happening. This is actually what held me back from releasing. I have some test modules to use, but I don't have infinite time to write test modules, test the framework, etc.
For discussions, please use this thread or another matching one in this subforum. For historical discussion, please search this thread.
Downloads available here:
Download Here
.
Changelog
20160928
suhide compatibility. See this post for details.
20160709
Updated to v86. See @rovo89's post here for details.
Experimental - Systemless bug fixes for devices that can't mount /data in recovery.
Experimental - Systemless builds for Android 5.1 (SDK22).
NOTE - You must use the installer in post #1 or the Material Design Xposed installer if you use systemless Xposed. The default installer will not detect /xposed/xposed.prop.
20160620
Updated to v85. See @rovo89's post here for details.
Experimental - Systemless bug fixes for devices that can't mount /data in recovery.
June 20th - Experimental - Systemless builds for Android 5.1 (SDK22). No changes to SDK23.
NOTE - You must use the installer in post #1 or the Material Design Xposed installer if you use systemless Xposed. The default installer will not detect /xposed/xposed.prop.
20160617
Updated to v85. See @rovo89's post here for details.
Experimental - Systemless support for SDK23 (Android 6.0). This should work similar to @topjohnwu's though there are some significant differences. The uninstaller has not been updated yet.
NOTE - You must use the installer in post #1 or the Material Design Xposed installer if you use systemless Xposed. The default installer will not detect /xposed/xposed.prop.
20150911 - Never Forget.
Updated to v74. See @rovo89's post here for details.
If the official release works for you, there is no need to install this version, unless you want to test LZMA2 compression.
Experimental - Use LZMA2 compression for our backups. If you get errors while trying to install Xposed, this may help.
Experimental - Uninstaller supports LZMA2 compressed backups. Its also backward compatible with official and my previous unofficial releases.
20150816
Disable resource hooking in Sygic
Disable fast access to TypedArray subclasses
Ensure system content providers are compiled before they are needed
See @rovo89's post here for details.
20150808
Merge @rovo89's changes from upstream to support LG encrypted odex files. See his post here for details.
I do not have an LG phone to test. Please report back any problems. Be sure to clear dalvik cache after installing!
20150804
Merge @rovo89's changes from upstream to support LG encrypted apps. See his post here for details.
I do not have an LG phone to test. Please report back any problems. Be sure to clear dalvik cache after installing!
20150727
Include @rovo89's changes from upstream. See his post here for details.
20150716
Include @rovo89's changes from upstream. There are no changes to the framework. If previous versions installed fine, then there is no need to update to this version unless you just really want to.
20150702
Updated installer and bundled busybox. Should resolve issues with mounting /system during install in some cases and incorrectly detecting recovery's value for ro.build.version.sdk instead of the system's.
20150701
Updated installer and uninstaller again. Installer is now less complex but still works on devices with low /system space. If you had no problems installing previous releases, then there's no need to update to this version. Uninstaller is backward compatible. See this commit for details.
20150630
Updated installer and uninstaller. Installer is now a bit more intelligent in creating your backups. Uninstaller is backward compatible. If you had no problems installing 20150629, then there's no need to update to this version. See this commit for details.
20150629
Update to v65 from @rovo89
Note: If the Xposed installer app (not zip) indicates the framework is not installed, then make sure you are using alpha4 of the installer app. This is a bug in alpha3 of the installer app.
20150514
Updated to include @C3C076's commits here. Buy the man a beer!
For details, see commits #1 and #2.
FAQ
Unofficial FAQ maintained by the community is available here
Miscellaneous
Working and non-working modules can be found here. This is not an official list. Your mileage may vary.
If you get "low space warnings" after installation, make sure you wiped Dalvik cache in recovery. If they persist, your ROM may have modified build.prop. See this post for one way on how to fix it. This seems most common with Chroma ROMs.
If your ROM gzip's (compresses) the .odex files in /system, then Xposed will not work and you will bootloop. This is due to patchoat handling the gzipped odex files, but not correctly patching them for Xposed. This causes Xposed to trigger continuous re-dexopt'ing of the compressed odex file.
Awesome! Been waiting for this since you announced on Github! Thanks so much for bringing it public!
Edit: apologies, got a little ahead of myself when I saw the first post in discussion deleted, missed the end of this post in my excitement.
This is incredible! Thank you
Sent from my Nexus 5 using Tapatalk
Wrong footer and signature verification failed. How do I fix this?
I'm on CM12.1 Unofficial, XT 1033
EDIT: Flashed another recovery (TWRP) and it worked.
Thank you soooooo much, for your hard work!!
Bootloop after installing gravitybox [LP]......My wrong , i forgot to make a NANdroid. I'll check it out again with a Nandroid backup.
Works good on my Nexus 5, but not all the modules. For example RootCloak working but after installing GravityBox I'm getting bootloop...
Just thought I share it, to save some tome to others.
BTW... All worked fine for me on 5.0.1
dmatik said:
Works good on my Nexus 5, but not all the modules. For example RootCloak working but after installing GravityBox I'm getting bootloop...
Just thought I share it, to save some tome to others.
BTW... All worked fine for me on 5.0.1
Click to expand...
Click to collapse
Same here with gravity box and it seems with CpuTemp in status bar
Nice job would test it asap
Great work! MinMinGuard is working like a charm with this!
blackzigong said:
Great work! MinMinGuard is working like a charm with this!
Click to expand...
Click to collapse
Is busybox working?
So this may seem like a stupid question but where do we download the xposed-installer-alpha from? Original xposed thread alpha-2??
EDIT: All good, original thread it is
Bootloop on my Nexus 5
Can this thread be locked & use this one forum.xda-developers.com/xposed/discussion-xposed-android-5-1-t3072982 instead?
Has anybody tried Amplify if it's working ???
Powered by ET!
Thanks for your effort
advanced power menu is working fine
nexus 5 stock thanks
- Lolistat - Not working
- Youtube Adaway - Not working
- OGXposes (To login with ogyoutube) - Not working
- AcDisplay - Not working
- Advanced power menu - Working
Does greenify work?
Hey,
My N5 recently got updated to 6.0 M, and I tried various version of Xposed installer and none of them will work.
It just keep telling : xposed is not compatible with android sdk version 23 or your cpu (armeabi-v7a)
Maybe some one knows the answer?
Thanks in advance.
XMP LTU said:
Hey,
My N5 recently got updated to 6.0 M, and I tried various version of Xposed installer and none of them will work.
It just keep telling : xposed is not compatible with android sdk version 23 or your cpu (armeabi-v7a)
Maybe some one knows the answer?
Thanks in advance.
Click to expand...
Click to collapse
Xposed for M is under development right now by @rovo89.
http://forum.xda-developers.com/showpost.php?p=63188361&postcount=21
My Nexus 9 is running on stock AOSP 6.0 already and the sources are synced to the build server (thanks to XDA for providing it). I assume that integrating the hooking mechanism should work relatively smoothless (although there were some bigger architectural changes). However, there are some new things, e.g. JIT and the optimizing compiler that need more attention to ensure that methods which could potentially be hooked are really called instead of being optimized away.
I can't give any timeline for this, it's done when it's done
Click to expand...
Click to collapse
It's hard to find NULL, I understand you failed.
Be patients, rovo's working on it..
Can anyone update xposed to work with the new security fixes applied to newer android 4.4.4 builds ?
New fix: Install the apk file found here:
Http://forum.xda-developers.com/showpost.php?p=64063168&postcount=62
edit: old fix:
read the attachment txt file and copy two files from an older build for your device to those folders (/system/lib & (/system/bin)
http://forum.xda-developers.com/showpost.php?p=63864337&postcount=35
@rovo89 : can you update it please?
robuser007 said:
Can anyone update xposed for the new security fixes found in newer android 4.4.4 builds ?
Click to expand...
Click to collapse
Black_Focus_X said:
@rovo89 : can you update it please?
Click to expand...
Click to collapse
What devices and ROMs are you using that have these problems, and what is in the error logs and logcat?
Without this information, no one can help you, not even rovo89 himself.
Also, have you searched the forum to see if others have this issue and what's been learned about it?
It's Samsung Galaxy S3 with Cyanogenmod 11 official! I searched the forum but couldn't find an answer. Maybe my english isn't good enough
My device is Motorola RAZR XT910, with a TI OMAP4 ARMv7-A SoC.
Right now, I am on an Unofficial CyanogenMod 11 (Android 4.4.4) ROM which contains the latest security fixes for the Stagefright vulnerability and was built on November 15. When I try to install Xposed framework, using the latest official stable installer from Xposed Repo, I get an the following error: "Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)".
When I was on the latest Official CyanogenMod 11 ROM for my device, that was built back on September 1st, Xposed would install and work properly on it, withour any troubles / warnings / errors. Now, I just want to use the latest build that has me protected against Stagefright but I can not install Xposed framework on it at all.
@rovo89 Is there / will there be any fix for this issue?
Having the same problem with the latest build of CM11 (2015.11.15).
unknownsoldierx said:
Having the same problem with the latest build of CM11 (2015.11.15).
Click to expand...
Click to collapse
Same on XT910 on 15.11 CM11 build!
from XT910 or XT925 using Tapatalk
me 2
samsung n5120, just update the new cm11 then show the error message
Yes, i got the same error message when I updated my Redmi 1S to the newest CM11.
I tried to search in MIUI forum but the answer only for MIUI OS.
I tried the patch for my Redmi 1S, it gave me bootloop.
Are there any explanation for this?
Thanks
Same issue here...Redmi 1s..CM 11 4.4.4 ...xposed not working...any solution ??
FYI, I believe this commit is causing the problems:
http://review.cyanogenmod.org/#/c/118800/
Replacing /system/bin/app_process and /system/lib/libandroid_runtime.so from previous CM builds will allow the framework to be installed without problems.
Ok, i'll try
But it can't be a right solution
Well, of course it's meant to be a temporary workaround, until (hopefully) rovo89 will have the time to fix this, if possible. If you heavily rely on Xposed it's better than nothing.
With the link to the commit, I just wanted to help to point out where the problem comes from in order to maybe get a permanent solution.
derf elot said:
Well, of course it's meant to be a temporary workaround, until (hopefully) rovo89 will have the time to fix this, if possible. If you heavily rely on Xposed it's better than nothing.
With the link to the commit, I just wanted to help to point out where the problem comes from in order to maybe get a permanent solution.
Click to expand...
Click to collapse
rovo it's not going to fix anything on kk, it's been done, too old. He's working on M and somewhat supporting L, so no luck with older builds.
Thank you. I tried it and. Yes it works. Xposed working
---------- Post added at 16:36 ---------- Previous post was at 16:34 ----------
ldeveraux said:
rovo it's not going to fix anything on kk, it's been done, too old. He's working on M and somewhat supporting L, so no luck with older builds.
Click to expand...
Click to collapse
Can you look into his head or what?
LG Optimus 4X HD Nightly 15112015 Xposed not working.
View attachment 3544451
Sorry about the pic being in spanish but is my girlfriend phone and i was giving her instructions via skype. It says "Xposed is not (yet) compatible with Android SDK version 19 or your processor architecture (armeabi-v7a)".
derf elot said:
FYI, I believe this commit is causing the problems:
http://review.cyanogenmod.org/#/c/118800/
Replacing /system/bin/app_process and /system/lib/libandroid_runtime.so from previous CM builds will allow the framework to be installed without problems.
Click to expand...
Click to collapse
Can someone make an update.zip for recovery ?
Feel free to try the zip I posted here. Make a backup first. Normally re-flashing your ROM should solve any issues, but you never know.
Xposed dead in latest CM11 *Unofficial* rom
Same thing with cm11 latest release with security patches for stage fright. Although the rom is listed as "Unofficial", it comes from THE Official cm11 OMAP 4 developer. Only listed unofficial because CM has not caught up with the developer. Xposed Framework does not work anymore on Android 4.4.4 See attached screenshots.
Ohmster said:
Same thing with cm11 latest release with security patches for stage fright. Although the rom is listed as "Unofficial", it comes from THE Official cm11 OMAP 4 developer. Only listed unofficial because CM has not caught up with the developer. Xposed Framework does not work anymore on Android 4.4.4 See attached screenshots.
Click to expand...
Click to collapse
You just posted what some other guys posted before you...
And if you would read the thread then you would know there is an update.zip for this problem! With this, Xposed is working without problems!
Are there any major differences between these two firmwares respecitvely are there any specific strengths or weaknesses?
oliman99 said:
Are there any major differences between these two firmwares respecitvely are there any specific strengths or weaknesses?
Click to expand...
Click to collapse
I think it is personal preference tbh, however I prefer SlimLP since I have messed around with custom ROMs for a while and currently run SlimLP on my phone as well. Also I like the customization that comes with SlimLP more than the plainness of ordinary CM.
The SlimLP rom developers don't recommend using xposed due to some ART optimizations. If anyone really wants xposed someone did suggest trying wanams modified xposed version.
rjmxtech said:
I think it is personal preference tbh, however I prefer SlimLP since I have messed around with custom ROMs for a while and currently run SlimLP on my phone as well. Also I like the customization that comes with SlimLP more than the plainness of ordinary CM.
Click to expand...
Click to collapse
I have been considering switching from cm 12.1 to slim lp on my fire. When you say additional customization what does that elude to? Theming and visual, or performance customization?
blueberry.sky said:
The SlimLP rom developers don't recommend using xposed due to some ART optimizations. If anyone really wants xposed someone did suggest trying wanams modified xposed version.
Click to expand...
Click to collapse
I've got xposed on the cm 12.1 rom. Haven't tried yet on SlimLP though.
If you do try it on SlimLP go for wanams xposed. And of course let us know if it you get any problems.
blueberry.sky said:
If you do try it on SlimLP go for wanams xposed. And of course let us know if it you get any problems.
Click to expand...
Click to collapse
I successfully flashed v2.1 of SlimLP, and then I tried v75 and v78 of wanams xposed (preceded with the mandatory installation apk). Both versions led to bootloop; I was able to remove the bootloop by using the uninstallation apk.
Since I want/needed xprivacy I switched to CM12.1 but gapps has stopped working. When there's a new version of SlimLP I might try again.
EDIT: I fixed the gapps in CM12.1 (12/04 built) by (1) doing a factory reset and (2) uninstalling the Playpermissionfix module in xposed. In retrospect I probably could skip (1) and do (2) only. Play store is still slightly wonky but it mostly works, and youtube definitely works 100%.
Damn, it's really a pain that SlimLP doesn't support xposed. I want xprivacy as well.
I just had to uninstall SlimLP and go to CM12.1 because of no support for Xposed from the developers. It's upsetting that with their (or ezio's) modifications that they should want to control something so big rather than let us decide for ourselves.
Because any reasoning such as "it's too big of a security risk" is absolutely ridiculous as it's our choice rather to expose ourselves and at the same time, most people installing modules and Xposed Framework at this point should know what we are installing to by now.
misticalx said:
I just had to uninstall SlimLP and go to CM12.1 because of no support for Xposed from the developers. It's upsetting that with their (or ezio's) modifications that they should want to control something so big rather than let us decide for ourselves.
Because any reasoning such as "it's too big of a security risk" is absolutely ridiculous as it's our choice rather to expose ourselves and at the same time, most people installing modules and Xposed Framework at this point should know what we are installing to by now.
Click to expand...
Click to collapse
The decision to decide for yourself is always in your hands. It is their rom to develop it how they want. If you do not like it, don't use it (as you have indiciated), but don't throw blame on a dev for not including support for something.
***For those users who are Unaware***
The PurifyOS Team have slightly modified the Xposed Nougat source of @ABForce and XposedTool of Rovo collector to allow the creation of rapid zips to install Xposed on Nougat
Flash installer.zip via TWRP/Custom Recovery
If any problems/bootloops flash uninstaller.
Only flash on SDK 25
Might work on custom roms
Enjoy Xposed on op3
xXXXXx Unstable xXXXXx
Download: (Use Files in attachments for no confusion)
http://xposed.purifyos.it
(For now don't use magisk module contain in magisk folder!!!)
Source:
https://forum.xda-developers.com/xposed/xposed-android-nougat-sdk-25-arm64-t3639221
Git:
https://github.com/abforce/xposed_art_n
You should also mention cons, that it's unstable and not 100% working.
Is amplify working?
SpartaKurd said:
Is amplify working?
Click to expand...
Click to collapse
According to some users, Amplify starts running but after sometime stops collecting stats.
tnsmani said:
According to some users, Amplify starts running but after sometime stops collecting stats.
Click to expand...
Click to collapse
Thanks mate. I hope a stable version will be released before Android O
Just wanting to link this here. @rovo89 specifically talks about why this method is dangerous - i.e. flashing "Xposed for Nougat" on an already existing ROM.
The best way is to wait for a ROM developer to compile the patch by abforce directly into AOSP, then build on that. This method will be very unstable, most modules won't work, etc.
it was too beautiful to be true, xposed kept me from upgrading to N for a long time, i can wait some time for rovo's stable release
Sent From the Grey Stuff Inside My Skull
This bricked OP3 with Resurrection Rom 5.4.8
Have anyone succeeded with Magisk Hide and systemless xposed? Share your ROM details.