[DISCUSSION] Xposed for Lollipop

Search This thread

xjhayar09

Member
Apr 8, 2015
12
2
Sounds like the right one. I believe the installation does checks anyway so it wouldn't/shouldn't flash if you had the wrong sdk or architecture zip.
On my Lollipop ROMs I stick with v87.

Maybe give the UNITY installer package a try. Couldn't hurt. Just make sure to uninstall your current Xposed first to start fresh.

http://forum.xda-developers.com/showthread.php?t=3697756

Xposed Framework [UNITY]


ZTE Axon 7 A2017U, Project New World, Multiboot, Tapatalk 4.9.5

thank you..It works now :D
 
  • Like
Reactions: zomer331 and marcdw

Holasoycris22

Member
Oct 16, 2018
23
0
One question, install a rom on my samsung j5 2015 j500m android 6 (stock), install a rom of android 7, which version of xposed should install ?, the android 6 or the android 7?
 

lanztotot

Member
Feb 26, 2018
7
0
hi and hello all . i just want to ask if im in right section ? if yes thank god . firstly , my phone is oppo f1s 5.1 lollipop . so i flash sdk22 . but i got stock in logo . so i restore again to original state . any suggestions to make xposed successful in my device ? thankyou !
 

marcdw

Senior Member
Sep 24, 2014
5,750
2,894
58
Baldwin Park
hi and hello all . i just want to ask if im in right section ? if yes thank god . firstly , my phone is oppo f1s 5.1 lollipop . so i flash sdk22 . but i got stock in logo . so i restore again to original state . any suggestions to make xposed successful in my device ? thankyou !
Just a little more info. Is the ROM stock or are you running AOSP/LOS-based ROM. Using SuperSU or Magisk. And exactly what file did you flash.
I know that on some stock ROMs people will think the phone is stuck but it actually takes a really really long time to boot. Ten, 15 minutes or even longer. I remember restarting my Moto (Nougat stock) several times because I thought it was stuck but it really wasn't.


LG G3 D851, LiquidRemix v9.1.3 Oreo ROM, microG (NoGapps), MultiROM, XDA Legacy
 
Just an FYI...

I had just uploaded the Rovo89's XposedInstaller 2.6 & 2.6.1 app with the Repo URL Fix on the following link.

It's located within the "Android 4.X and Below" Directory.

https://www.androidfilehost.com/?w=files&flid=284172

Everything should be good to go now (hopefully). :)


~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my SM-G900T device.
 

lenoid

Senior Member
Dec 10, 2013
54
8
Germany
@Ibuprophen
I tried to install your 2.6.1 URL fix on 2 devices with Android 4.0 and 4.4. Upgrading was not possible, so I uninstalled the "old" 2.6.1 version and made a reboot. Then I tried to install your fixed 2.6.1 version again and it fails. Installing the old 2.6.1 ran without any problem.
 

marcdw

Senior Member
Sep 24, 2014
5,750
2,894
58
Baldwin Park
@Ibuprophen
I tried to install your 2.6.1 URL fix on 2 devices with Android 4.0 and 4.4. Upgrading was not possible, so I uninstalled the "old" 2.6.1 version and made a reboot. Then I tried to install your fixed 2.6.1 version again and it fails. Installing the old 2.6.1 ran without any problem.
The fixed 2.6.1 worked for me on Mahdi KitKat. What kind of error are you getting?


LG G3 D851, PAC-ROM 6.0.1, MultiROM, XDA Legacy
 

lenoid

Senior Member
Dec 10, 2013
54
8
Germany

Attachments

  • Screenshot_2018-12-15-14-26-00.png
    Screenshot_2018-12-15-14-26-00.png
    23.8 KB · Views: 318

bidh

Member
Oct 11, 2013
7
4
That the app hasn't been installed:

I got the same error but SolarWarez Modded Installer is working for me.
https://www.androidfilehost.com/?w=files&flid=284177

Nope the framewrok is now giving me this error:
Xposed is not compatible with Android SDK version 16 or your processor's architecture (armeabiv6l).
redoc-library[1331] 2218 cannot locate'__sprintf_chk'
CANNOT LINK EXECUTABLE


No can do, I guess I will have to wait for an official update/fix.
 
Last edited:
  • Like
Reactions: lenoid

lenoid

Senior Member
Dec 10, 2013
54
8
Germany
@bidh
Thanks, works fine now.
P.S.: it's very important to delete the old app and make a restart. Upgrading and deleting data and cache doesn't work.
 

uncinogb

Member
Apr 3, 2018
19
1
Has anybody had any success installing the frmework on a Samsung Galaxy Note 3 running stock Rom lollipop 5.0? I have tried with various versions and each time the phone got stuck during the boot process after showing the Samsung logo :(. I tried the following:
xposed-v71-sdk21-arm-arter97-V6-snapdragon.zip
xposed-uninstaller-arter97.zip
xposed-v75-sdk21-arm-arter97-snapdragon.zip
xposed-v89-sdk21-arm.zip
My configuration is in the file attached.
I have read dire warnings that exposed does not work with stock Samsung lollipop but then I see options to download versions for Samsung lollipop. I am confused.
I also thought I might have to deodex my stock rom, but I don't have a clue how to do this. Any pointer much appreciated.
Thanks guys
 

marcdw

Senior Member
Sep 24, 2014
5,750
2,894
58
Baldwin Park
@uncinogb, it's been awhile since I flashed Xposed against stock LP or MM. Don't remember if there was a long wait as I had on stock Nougat ROMs but after flashing Xposed it takes a really really long time on first boot. I thought the ROMs were stuck or in a bootloop but no. Can take upwards of ten to 15 minutes.
Can't say that's the case on your phone and ROM but try to wait it out. Uncomfortable to do as one doesn't know how long to wait.


Moto G5S Plus XT1806, OmniROM, microG (NoGapps), MultiROM, XDA Legacy
 
  • Like
Reactions: Zaraza325632

roscos

Senior Member
Dec 24, 2015
66
9
Good morning, I have updated to Magisk 18.1
Now xposed does not appear in the Magisk modules but works well
xposed Version 89
Android 5.1 (lollipot, API 22)
Doogee F5 arm64
Can it be a problem?
 
Last edited:

doubtfire1

Member
Oct 22, 2017
15
2
i have oppo f1s, downloaded the correct module and have the installer apk installed onto my phone.
flashed xposed in twrp, it installed properly but it just gets stuck booting. ive read that it can take some time. but ihve had my phone sitting here on the logo screen for about half an hour.
something wrong with this? should i just remove it and not bother with xposed, ive been messing around with it all day trying to get it to work but this is all it ever does.
 
  • Like
Reactions: Pyrolectic13

doubtfire1

Member
Oct 22, 2017
15
2
@doubtfire1, flash the Xposed uninstaller zip and reboot, to make sure ROM is okay. Then try the UNITY installer for one last attempt. Hopefully it'll work.

https://forum.xda-developers.com/showthread.php?t=3697756

Xposed Framework [UNITY]


LG G3 D851, AOSPA-L ROM, Nebula Rev9.3 Kernel, microG (NoGapps), MultiROM, XDA Legacy

hey, just tried this and it did the same thing. keeps trying to boot, left my phone for 40 minutes and no deal. so restarted in recovery and used the xposed uninstaller, but this time its still stuck booting?
did you mean for me to download from that page Xposed Framework UNITY or the Unity installer by itself? cuz i got the xposed framework. should i try just the unity installer? if i can get my phone back working properly again that is.

EDIT: its good turns out xposed uninstaller just doesnt work for some reason, luckily had recovery mode for magisk module and could uninstall from there

im confused as to why it wont work for me at all, its been really frustrating,
 
Last edited:

Top Liked Posts

  • There are no posts matching your filters.
  • 1268
    It seems that many people have waited for this moment, and here we are:


    Xposed for Lollipop is finally here!


    You can use this thread for discussions. Please check the read-only thread for the download links and official updates.




    Edit by @Darth.

    Rovo89 has been kind enough to let us add a few things to help stop the repeated questions that are asked here.... And thanks to RootSU, we'll be able to add a FAQ........ So...

    Please read post 2 below.... Very carefully before posting a question here.
    726
    This thread was just started an already it had to be cleaned from pointless posts. Use the thanks button. Do not make pointless posts in the thread.

    I understand You guys are excited but really? Come on.

    If you dont have something constructive to post then dont. Do not clutter this thread Or it will be closed and only opened when the OP has something to post.
    444
    Unofficial Q&A

    PLEASE READ:

    If you have questions about which Xposed version to use, read this post and use the table to identify the correct version for your device.

    If you encounter any issue or things are still unclear, try to search this thread by using the Search function before posting anything. Lots of issues/questions have already being asked and/or solved. If this doesn't work, please include information about your device, its current Android version, the files you tried to flash/install and steps to reproduce the issue in your post. This way other members are able to help you in a timely manner.



    Hey everyone,

    Since the primary thread information was taken to a read-only thread, the regulars here have been answering the same questions with even mor frequency, so here we hope to address some of those basic questions in brief:

    Q: What does "Alpha" mean?
    A:
    Software goes through several stages before final release. Alpha and Beta are a couple. Beta is usually released strategically to experienced testers to get feedback and find bugs. Alpha is less mature than Beta and is often not released outside the company that produced it. We're very lucky to get alpha releases, but beware, it is expected to be buggy and you should be experienced in Android usage before taking on Alpha testing.


    Q: What do I need to do BEFORE flashing Xposed?
    A:
    A full Nandroid Backup of your system (preferrably by using your recovery). If something goes horribly wrong during flashing/installation, you can revert all changes made to your system quite easily.


    Q: What recovery can I use?
    A:
    The latest zips provided by @rovo89 are now signed, so any recovery should work now (including cyanogen recovery) however, Philz recovery struggles to mount system correctly and detects the recovery sdk 19 instead of the ROM recovery. You can try manually mounting system in recovery first (instructions are lower down this thread) though, you should probably move over to TWRP now.

    Some of the unofficial versions are not signed zips, so you'll need a recovery that can turn off signature verification. TWRP is probably the best bet all round, as cyanogen recovery doesn't allow this.


    Q: Which is the right Xposed for me?
    A:
    It's all getting rather confusing.

    Here's what you need to know...

    Almost all android devices have an ARM based CPU. A small handful of those are 64 bit (ARM64), released this year. Obviously the ones that are not 64 bit are 32 bit.

    All ARM version 7 CPUs are 32 bit. Although all ARM version 8 CPUs were designed as 64 bit, some only operate in a 32 bit mode.

    A small set of android devices now run 32 bit Intel CPUs, referred to as x86.

    What you first need to do is find out what CPU your phone has. If its intel x86, that's quite easy to find out by reading the specs.

    For others, try this:

    Google "your phone CPU? “ to get the CPU name.
    Google "your CPU ARM Version?“ to get the ARM version.

    Example...

    Google "Nexus 6 CPU" - answer Snapdragon 805
    Google "snapdragon 805 ARM version?" - answer ARMv7

    NOTE: For Snapdragon CPU's, check this Wikipedia article.

    You can also use AIDA64 from the Google Play Store or apkmirror.com, which will tell you what ARM version you have (look for Instruction Set). Quite easy way.

    Then use that information to use the table below to find the right version for your device (The second table is for users with a TouchWiz-based ROM, so mostly Samsung users. The first one is for all other users.) Links to the Xposed versions are given below the image.


    EDIT: the flow chart, which was used in the past to identify the correct Xposed version one needs has been replaced by a table, which should be easier to read.

    How to read the table:
    If you do not know how to read the table, it is very easy. If you have a Samsung device (either with stock ROM or TouchWiz-based custom ROM), use the second table ("TouchWiz-based ROMs (Samsung users)"). If not, use the first table. Then identify your CPU ARM version as described above as well as your Android version. With those information available, go to the corresponding field in the table and that's it, you have just identified the required Xposed version for your device.


    attachment.php


    Download threads:


    Q: Does this work on my rom/device?
    A:
    It should work. You can search the thread to see if anyone else got it to work, or you can do what everyone else does - backup and try it for yourself.


    Q: What files do I need?
    A:
    The Xposed installer (.apk) and the flashable Framework (.zip)


    Q: Error in Xposed app "xposed not yet compatible with SDK 22 or your processor architecture (armeabi-v7a)" and may also refer to libdvm.so
    A:
    This happens if you are using the legacy KitKat Xposed app (Xposed Installer v2.7 or below). Uninstall it and ensure you are running the latest alpha (currently: XposedInstaller_3.0_alpha4.apk) from the official rovo89 thread.


    Q: Error in recovery, "wrong sdk version / wrong arm version". How to solve?
    A:
    Read this error very carefully.

    If it says "Wrong SDK version: 22, expected 21 - 21", it means you're flashing the SDK 21 version on an SDK 22 based ROM.

    Similarly, if it says "Wrong SDK version: 21, expected 22 - 22", it means you're flashing the SDK 22 version on an SDK 21 based ROM*

    You're flashing the wrong zip for your ROM. Use the table above to identify the correct zip for you.

    *Note, All 5.0.x ROMs are SDK21 based. All 5.1.x ROMs are SDK22 based. You're flashing the r

    There is a similar, but slightly different error. If it says "Wrong SDK version: , expected 22 - 22" or it says If it says "Wrong SDK version: , expected 21 - 21" , then something else is wrong. Note the blank space after "version:"? This means it cannot determine your SDK version from the /system/build.prop.

    Withing the flashable zip is an updater-binary that reads your build.prop before flashing. The line of code looking for that is below:
    Code:
    ui_print "! Wrong SDK version: $API, expected $XMINSDK - $XMAXSDK"
    See how where the blank space is, here, it says "$API"? That is a variable that is defined below:
    Code:
    API=$(cat /system/build.prop | grep "ro.build.version.sdk=" | dd bs=1 skip=21 count=2)
    ...Which basically says:

    Look for "ro.build.version.sdk=" in build prop, then save next 2 characters as API$

    If $API is blank, it means it cannot find "ro.build.version.sdk=21" or "ro.build.version.sdk=22" in your build.prop.

    One of two reasons cause this.

    1) It's not in your build.prop (well that is extremely unlikely)
    2) The updater-binary cannot mount /system properly.

    So to troubleshoot, check that "ro.build.version.sdk=" exists exactly in build.prop and that there are 2 characters after it. If there are, then API should NOT be blank and probably means system is not mounting, in which case, you can try mounting system via the recovery menu. If that still doesn't work, open a terminal emulator at the root folder (in TWRP) and type the following 2 commands:
    Code:
    mount -o ro /system 
    mount -o rw,remount /system

    Please also note that if this gives an error such as "cannot find system" then you may need a different recovery.

    The same as above can also happen with the arm version, so if you know you're flashing the correct arm version for your device, then it's probably a system mounting issue.


    Q: I can't find the latest Alpha, help!
    A:
    There are 2 parts of Xposed. There is the app (.apk) and the framework (a flashable .zip) and you need both.

    The latest version of the app so far is alpha 3. When we talk about alpha 4 etc, these updates are just to the framework (zip). The zips are not named "alpha" though. The zips have a date in the file name instead. Read rovo89's posts clearly as he gives you that date when there is an update announcement.


    Q: What is Armv7? Will it support my CPU? What about Armv8 / 64 Bit / Intel CPUs
    A:
    Armv7 is a CPU architecture. If you have a mainstream phone released since 2010, you most likely have Armv7. All Qualcomm and Exynos CPUs since then have been based on Armv7. Armv8 however is the architecture used in the new 64bit CPUs.

    Intel CPUs are x86. They are not officially supported.


    Q: Does this work on Android JellyBean/KitKat/Marshmallow?
    A:
    No. It's only for Lollipop.


    Q: Where can I find the uninstaller?
    A:
    In the link found in post #1 or - in case you use wanam or arter97's version - in the corresponding threads.


    Q: What's this red error about not being able to install the framework within the Xposed Installer app?
    A:
    It's not an error. It simply states that the framework can only be installed by recovery - which we know as we have already done it.


    Q: Xposed won't work. All the files are present and correct. What to do?
    A:
    Check the logs in the app. If you see a line that says "found /data/data/de.robv.android.xposed.installer/config/disabled" then delete that "disabled" file and reboot. It should work.

    If it doesn't work, try to do a soft reboot from within Xposed Installer app (Xposed Installer -> Framework -> Soft Reboot). Root permission has to be granted to the Xposed Installer app to do so (will be asked when clicking on the Soft Reboot button for the first time).


    Q: I get in a bootloop, what to do?
    A:
    The first thing to try is wiping "dalvik" and cache via recovery. If this doesn't work, ensure you have flashed the correct Xposed version (this applies for Samsung users mostly). Else you can provide a log file which you can grab via ADB (search for "How to logcat" if you don't know how) and upload it either here (don't forget to link rovo89 in your post) or to rovo89's github repo (better option)


    Q: TWRP states "not enough space in system". What is this about?
    A:.
    Not really related to Xposed, it just means that your system partition doesn't have enough free space to install Xposed. Maybe create some space by deleting Google related-apps from system that you don't need or that can be downloaded from Play Store. Ask in your device forum if you need specific advice.


    Q: How do I update the Xposed framework to a newer version?
    A:
    You can dirty flash it through recovery (don't uninstall/wipe anything before flashing). Afterwards, wipe cache/dalvik and reboot. That's it.


    Device Specific

    Q: My LG device has Weather and Smartcover force closes. What to do?
    A:
    Those issues are fixed with Xposed framework v80 and later. If you encounter such issue, update the Xposed framework to version v80 or higher. If you are unable to update to v80 or later, you need to disable these apps before flashing. You can disable them afterwards, please see this post: http://forum.xda-developers.com/showpost.php?p=59929667&postcount=5122.


    Q: I get a low on space error on my Moto. What to do?
    A:
    The first thing to try is wiping "dalvik" and cache via recovery.


    Q: It does not work on my Huawei/Xiaomi device. What to do?
    A:
    Chinese OEMs change a lot of the original Android code base, so most likely Xposed is not compatible with those devices (yet). There might be some compatibility in the future, but don't expect it in the next few days.


    Q: It does not work on my MIUI device. What to do?
    A:
    There is an XDA thread by SolarWarez dedicated to Xposed for MIUI-based devices.

    Xposed MIUI
    141
    Look I already posted a warning. And people dont want to listen so let me make this very clear. The next pointless post will have this thread closed and only opened for the OP.


    If you are posting a bug then you better have a logcat to go along with it. If it doesnt work because you didnt read the OP then too bad.
    100
    I just did a quick clean up for the last few pages and removed around fifty posts. I'm keeping this thread closed for a bit so that everyone gets this message. (Thread reopened.)

    Please remember the following -- it takes less than five minutes and avoids frustration for you and everyone subscribed to the thread:
    • Read the first post and try to search the thread (there's a handy search button which usually does an alright job). Many of your questions are already answered.
    • Do not ask about supported modules here. Check the module's thread instead. If a module isn't working, post in its thread -- not here.
    • Telling people to search/complaining about the noise only adds to the noise. Please, either provide them with an answer (and let them know they could've found it if they searched), or report the post and don't reply. If it's answered in the OP, just report it and move on.
    • If you're reporting a bug, include a logcat if the device isn't booting or a log from the Xposed Installer if the framework isn't activating (do check the OP first, as some issues are mentioned there).

    Cheers.