[UNOFFICIAL] Systemless Xposed for Android 5.1/6.0 - v86.1 / 20160928 / SDK22/SDK23

Search This thread

moubba

New member
Sep 29, 2016
3
0
For the icon you still need to install the installer apk on your phone this is the very basics of Xposed, please go study this some more because it's dangerous stuff to toy with.
It is accustomed here that you at least the first post OP were you could have found this information.
Please make sure you get acquainted with this before doing anything else.
Hey don't mind me... I already installed it
I didn't read everything :good: thanks
 

Rush94

Senior Member
Mar 7, 2016
352
64
Nokia X5 (5.1 Plus)
OnePlus Nord
Need Help ASAP currently on cm13 device:condor deleted SU files and got success for safetynet was ROOTED and then unrooted oblivious but the xposed framework was working then no framework was active after reboot , then re flashed framework and safetynet failed ,This is what i want : I want to install Systemless Xposed but that will require Super Su , but if i install Super Su it gets stuck on either boot-loop or flashed via recovery then the network fails to detect i need a workaround soon

Edit:sorry for my bad english
 
Last edited:

grep_i

Senior Member
Sep 19, 2015
1,551
621
Need Help ASAP currently on cm13 device:condor deleted SU files and got success for safetynet was ROOTED and then unrooted oblivious but the xposed framework was working then no framework was active after reboot , then re flashed framework and safetynet failed ,This is what i want : I want to install Systemless Xposed but that will require Super Su , but if i install Super Su it gets stuck on either boot-loop or flashed via recovery then the network fails to detect i need a workaround soon

Edit:sorry for my bad english

Yes your English is very broken.
What I guess if I'm reading it right is you still got build in root with your rom.
For that I have a cleanup script.
Flash it before flashing SuperSU.

follow link here to SU cleanup script
 

Rush94

Senior Member
Mar 7, 2016
352
64
Nokia X5 (5.1 Plus)
OnePlus Nord
Yes your English is very broken.
What I guess if I'm reading it right is you still got build in root with your rom.
For that I have a cleanup script.
Flash it before flashing SuperSU.

follow link here to SU cleanup script

Sorry for that English
I'll explain in detail now
My device - condor
Recovery - twrp-3.0.2
My android version -6.0.1 cyanogen 13
Root access - developer option not installed super su
Our device are facing issue if i try to install from google play the device hai binary issue so says to update binary and if i press yes update the device gets stuck in bootloop , if i flash su via recovery our network of cellular connection doesnt work , so can't flash super su anyways , i wanted to use some banking apps and my sister wanted to play Pokemon go , both the apps are not accessible due to root which is unable to hide ( i think need help here in depth )
Also using xposed xinternal to save obb to sd card since we just have 1 gb for apps as internal storage
I tried to move su files from bin and xbin to other sd folder and safetynet helper check was success then xposed stopped working said framework not installed so i flashed framework v86 in recovery and rebooted with a custom kernel i used and the safetynet helper said failed to retrieve and the banking app stopped working even the root is not working now since the su files are not there i can understand if i move back su files back to original place then the developer root access gets active as expected , i need some workaround for using both root and xposed along with banking apps and Pokemon go , need help
U send me a link of su binary clean up what will that do ?

Thanks for support and again sorry for bad English :D
 

grep_i

Senior Member
Sep 19, 2015
1,551
621
Sorry for that English
I'll explain in detail now
My device - condor
Recovery - twrp-3.0.2
My android version -6.0.1 cyanogen 13
Root access - developer option not installed super su
Our device are facing issue if i try to install from google play the device hai binary issue so says to update binary and if i press yes update the device gets stuck in bootloop , if i flash su via recovery our network of cellular connection doesnt work , so can't flash super su anyways , i wanted to use some banking apps and my sister wanted to play Pokemon go , both the apps are not accessible due to root which is unable to hide ( i think need help here in depth )
Also using xposed xinternal to save obb to sd card since we just have 1 gb for apps as internal storage
I tried to move su files from bin and xbin to other sd folder and safetynet helper check was success then xposed stopped working said framework not installed so i flashed framework v86 in recovery and rebooted with a custom kernel i used and the safetynet helper said failed to retrieve and the banking app stopped working even the root is not working now since the su files are not there i can understand if i move back su files back to original place then the developer root access gets active as expected , i need some workaround for using both root and xposed along with banking apps and Pokemon go , need help
U send me a link of su binary clean up what will that do ?

Thanks for support and again sorry for bad English :D
It will clean up all remnants of older or other SuperSU install as I guess that's most probably your problem right now.
Flash this in TWRP custom recovery before flashing latest SuperSU in TWRP custom recovery.
Try it and report back here if it helps you with your problem others have tried and it helped them.
If you don't fully trust me you could also look for a similar tool created by osm0sis.
Maybe you trust him better.

Sent from my Nexus 5 using XDA-Developers mobile app
 

Rush94

Senior Member
Mar 7, 2016
352
64
Nokia X5 (5.1 Plus)
OnePlus Nord
It will clean up all remnants of older or other SuperSU install as I guess that's most probably your problem right now.
Flash this in TWRP custom recovery before flashing latest SuperSU in TWRP custom recovery.
Try it and report back here if it helps you with your problem others have tried and it helped them.
If you don't fully trust me you could also look for a similar tool created by osm0sis.
Maybe you trust him better.

I trust u totally if this worked then i can su hide ?

Also i won't face any network issue on next super su flash ?
 

grep_i

Senior Member
Sep 19, 2015
1,551
621
I trust u totally if this worked then i can su hide ?

Also i won't face any network issue on next super su flash ?
If suhide even works on your device than yes.
With this cleanup you can start over and flash superSU and after that suhide if it works on your device.
Keep in mind that suhide is unsupported and experimental software.
I've got it working but other people following saying they followed my exact instructions on same device did not succeed.
Even though it works for me all the time if I follow my own instructions I did it like 80 times already and always succeeded.
But as said before there are no guarantees.


Also i won't face any network issue on next super su flash ?

This question is unclear to me I totally do not understand what you are meaning with this can you please elaborate on this ?
 

Rush94

Senior Member
Mar 7, 2016
352
64
Nokia X5 (5.1 Plus)
OnePlus Nord
If suhide even works on your device than yes.
With this cleanup you can start over and flash superSU and after that suhide if it works on your device.
Keep in mind that suhide is unsupported and experimental software.
I've got it working but other people following saying they followed my exact instructions on same device did not succeed.
Even though it works for me all the time if I follow my own instructions I did it like 80 times already and always succeeded.
But as said before there are no guarantees.


Also i won't face any network issue on next super su flash ?

This question is unclear to me I totally do not understand what you are meaning with this can you please elaborate on this ?


Yes sure if i flash super su via recovery then i don't the developer says it creates conflict that leads to no simcard detection till i reflash the whole rom , i tried once and the simcard detection failed , one cannot live without cellular network

so will i face this issue ?
 

grep_i

Senior Member
Sep 19, 2015
1,551
621
Yes sure if i flash super su via recovery then i don't the developer says it creates conflict that leads to no simcard detection till i reflash the whole rom , i tried once and the simcard detection failed , one cannot live without cellular network

so will i face this issue ?
If the developer of the rom says so.
I guess he knows better than me what will happen with the rom he created.
Ask the developer of there's a work-a-round or if he is going to fix the issue, if not you're on your own.
Maybe you start looking for another rom which is compatible with Xposed.
 

sansnil

Senior Member
Dec 6, 2007
529
257
@romracer Do you think there's any way to make your last systemless version for MM compatible with Google's recent November security updates? Seems like the changes Google introduced break Xposed.
 
  • Like
Reactions: 124chase

meiser

Senior Member
Nov 6, 2010
401
166
I'm also very interested in an update to v87.0 as your systemless Xposed is the only one left which doesn't depend on Magisk (which I don't want to install).
 
  • Like
Reactions: sansnil

Top Liked Posts

  • There are no posts matching your filters.
  • 1930
    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


    .
    513
    THIS EXPERIMENTAL UNOFFICIAL VERSION IS OBSOLETE. USE OFFICIAL XPOSED FRAMEWORK INSTEAD.

    Intro
    Here comes another unofficial Xposed Framework super alpha release targeted for Lollipop 5.1.0 and 5.1.1.
    My version is based on @romracer 's initial version so credits go to him for doing
    the initial job to get the framework running on LP 5.1; as well as @rovo89 for all of his original work.
    Make sure to read the first post of this thread to learn basic info about unofficial Xposed Framework super alpha before proceeding any further.

    As you may already know, many modules don't work on initial version of super alpha due to changes in ART between LP 5.0 - 5.1.
    I took an effort to go through all the changes in ART to find out what could be done to improve the framework
    for better 5.1 compatibility, and managed to identify areas where adjustments had to be made.

    This means, this version should have better support for all those modules that were previously causing boot loops
    or other unexpected system/app crashes. But please note, that even if modules that previously didn't work start to work again,
    it is still necessary for them to be updated for Lollipop 5.1 compatibility - and that's a task for a particular module dev.
    Please, do not spam this thread with issues related to modules themselves. Use dedicated modules' thread instead.

    THIS VERSION DOES NOT TARGET ANY SAMSUNG TOUCHWIZ RELATED ISSUES

    USE AT YOUR OWN RISK AND MAKE SURE YOU MAKE A NANDROID BACKUP BEFORE FLASHING

    Compatibility
    If previous super alpha worked on your device, new one will most likely work as well.

    Files
    I have built two version of the framework, one for LP 5.1.0 and one for LP 5.1.1, even if there are no significant differences between 5.1.0 and 5.1.1.
    Both are for ARM 32bit platform. Make sure you choose the correct one for your system.
    - xposed-sdk22-5.1.0-arm-20150514 - tested on Nexus 5 running stock 5.1.0 (LMY47I)
    - xposed-sdk22-5.1.1-arm-20150514 - tested on Nexus 5 running 5.1.1 built from AOSP source (LMY47V)
    Files are attached at the end of this post.

    Install
    - flash in custom recovery
    - make sure to wipe dalvik cache after flashing.

    Source
    ART source code containing my changes is available at
    https://github.com/C3C0/android_art
    It's a fork of rovo89's original repository, with romracer's and my commits on top.

    @romracer
    Please, consider updating info and downloads in the OP when you have time. Thanks.

    ----
    Regarding GravityBox; to avoid further confusion/speculations.
    Current version of GB is not fully compatible with Lollipop 5.1, yet. It will refuse to start on 5.1 even after
    xposed framework is updated to this new super alpha. I need some time to make GB compatible for 5.1 so please be patient and
    keep track of discussion within dedicated GravityBox module thread.
    376
    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.
    159
    Yet another version of unofficial Xposed Framework for LP 5.1

    This version is in sync with the latest official xposed framework for 5.0 recently released by @rovo89.

    REQUIRES XPOSED INSTALLER APP ALPHA4 THAT CAN BE OBTAINED FROM ROVO'S OFFICIAL XPOSED THREAD FOR LOLLIPOP

    AS ALWAYS, MAKE SURE YOU HAVE A NANDROID BACKUP BEFORE YOU START MESSING WITH YOUR DEVICE
    142
    Freshly compiled version containing some fixes, mostly taken from rovo89's official xposed repositories.

    Changelog
    - Xposed: fixed xposed not writing to log on some devices (useful mainly for module developers)
    - ART: potential fix for debugger crash when debugging hooked methods
    - ART: fixed modules crashing on launch right after they get updated
    - ART: ignore unknown arguments passed to dex2oat,oatdump,patchoat and runtime (potentially improves compatibility with OEM ROMs)
    - ART: added gzip support to patchoat to potentially improve compatibility with CM-based ROMs (cherry-picked from CyanogenMod version of ART)

    ARM version has been tested on Nexus 5 running stock 5.1.1
    ARM64 version reported to be working fine on Nexus 9 running CM12.1

    Use at your own risk and make sure to have a ROM backup ready.

    @romracer : FYI