• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[DISCUSSION] Xposed for Lollipop

Search This thread

Portgas D. Ace

Recognized Contributor
Jun 12, 2014
4,348
3,144
Bergisches Land
Only one version of xposed framework is working for my device ... Which is xposes sdk21 (v70) arm ..... Other versions not working and cause bootloop ...so kindly provide me xposed sdk21 (v70) arm ...i shall be very thankful to you ...

What device and what Android version do you have?

Did you wipe cache&dalvik after flashing Xposed?
 

ehtisham ali

Senior Member
Jul 12, 2015
155
13
I m waiting orville87

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

Rovo89 only version is working for my device is xposed sdk21 (v70) .plz provide me that version .
 

kpoopa

New member
Feb 28, 2016
1
0
Hi I have an Honor 7 (5.0.2 lollipop, x64) and after flashing xposed-v80-sdk21-arm64.zips it just bootloops.

I wiped cache and dalvik after flashing but still bootloop or stuck on the logo Honor.
Does anyone can help me please ?
 

Portgas D. Ace

Recognized Contributor
Jun 12, 2014
4,348
3,144
Bergisches Land
I m waiting orville87

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

Rovo89 only version is working for my device is xposed sdk21 (v70) .plz provide me that version .

You could help rovo89 to make latest Xposed compatible with your device. How to do this? Quite easy:

1. Flash Xposed-sdk21-arm v80, wipe cache&dalvik and reboot
2. Capture a log file of the bootloop via ADB (if you don't know how to do so, search for "How to logcat" here on XDA)
3. Post the log file either here or on rovo89's github page

I am using v80 without any issue and don't have v70 any more.
 

jake3317

Senior Member
Feb 24, 2014
240
44
Wifi and or bluetooth can't be turned on random

I am on AICP11 on a Samsung S4-mini (GT-I9195)
Xposed SDK22V80 installed
xPrivacy is the only Module installed

Sometimes Bluetooth and or Wifi can't be turned on. The switch goes to ON, stays there for a while and switches back OFF. Sometimes this even ends up in a reboot.
After disabling xPrivacy (the only module) this behavior can' t be repeated anymore. I checked the log's of XPrivacy, but it doesn't show any blocked items that could cause this behavior.

I made a logcat while turning on/off Bluetooth until it got the described behavior. Therefore, please have a look at the last part of the attached logcat, there I try to enable Bluetooth a couple of times.
 

Attachments

  • logcat_and_device_info.zip
    95.1 KB · Views: 10

tau.gi.mo

Senior Member
Dec 21, 2014
251
92
I am on AICP11 on a Samsung S4-mini (GT-I9195)
Xposed SDK22V80 installed
xPrivacy is the only Module installed

Sometimes Bluetooth and or Wifi can't be turned on. The switch goes to ON, stays there for a while and switches back OFF. Sometimes this even ends up in a reboot.
After disabling xPrivacy (the only module) this behavior can' t be repeated anymore. I checked the log's of XPrivacy, but it doesn't show any blocked items that could cause this behavior.

I made a logcat while turning on/off Bluetooth until it got the described behavior. Therefore, please have a look at the last part of the attached logcat, there I try to enable Bluetooth a couple of times.
Then it is related to xPrivacy please ASK in its theard!

Gesendet von meinem Redmi Note 2 mit Tapatalk
 

jake3317

Senior Member
Feb 24, 2014
240
44
Then it is related to xPrivacy please ASK in its theard!

I did that already and this is what the developer says:
"There are quite some bluetooth errors in the logcat, strict mode violations and even a stack overflow, but I don't think this is directly caused by XPrivacy. It could be a bug in Xposed or it could be that the little overhead of Xposed and/or XPrivacy triggers a problem. Anyway, I don't see a fix for this from the perspective of XPrivacy. "
 

bryangb

Senior Member
My mobile is Galaxy Grand Prime and I have the lollipop 5.0.2
And that's what I did :
I downloaded the flashable framework arter97 ARM sdk21 version.
I turned off ny mobile
I entered the recovery mode
Install
I choose the flashable framework
then it loaded -not sure what did it exactly
I rebooted anyway
And then ta da it got stuck on the logo :(
I'd be grateful If someone helped me
How long did you leave it "stuck at the logo"? It was someone else saying that sometimes Galaxys need 20-30 minutes to sort themselves out that impelled me to give my iNew L4 another chance.

So instead of giving up and rebooting after seeing the logo for 15-20 minutes, I left it alone. And despite looking like it had hung, after 30 minutes or so it started up properly with Xposed working.

Maybe yours just needs a bit more time. :fingers-crossed:
 

Dark-Coder

Senior Member
Jun 14, 2015
289
43
Xposed Framework Crashing , Which causing my Phone to Reboot Itself ...
i am using CYanogenMod 12.1 (Lollipop 5.1 )
Log File is Attached..
Thanks...
 

Attachments

  • xposed_error_20160302_003109.log
    6.9 KB · Views: 40

jacohell

Member
Sep 4, 2007
16
4
benghazi
Xposed installed but not active :(

See the pictures in the attachment
 

Attachments

  • Screenshot_20160302-031014.png
    Screenshot_20160302-031014.png
    43.8 KB · Views: 600
  • Screenshot_20160302-031024.png
    Screenshot_20160302-031024.png
    53.4 KB · Views: 620

cognitivedissonance

Senior Member
Jan 11, 2012
622
194
Hi there, I have the xposed-v80-sdk21-arm.zip and the XposedInstaller_3.0_alpha4.apk flashed, installed, and working flawlessly on my AOSP 5.0.1 based ROM on my GS4 (custom recovery, etc.)


I believe that the xposed-uninstaller-20150831-arm.zip is the correct uninstaller for the Xposed version that I'm using, but can someone please confirm that?
 

jkeuclid

Senior Member
Mar 19, 2014
508
112
Finally got around to putting 5.02 LP on my wife's ATT D800 G2, haven't got Xposed to work as of yet, had it working fine previously with KK. Any help would be appreciated.
 

Portgas D. Ace

Recognized Contributor
Jun 12, 2014
4,348
3,144
Bergisches Land
Finally got around to putting 5.02 LP on my wife's ATT D800 G2, haven't got Xposed to work as of yet, had it working fine previously with KK. Any help would be appreciated.

And any detailed information about what you tried to install Xposed would be appreciated, too.

Post #2 contains all the required information to identify the correct Xposed framework version by yourself.
 

CalculatedRisk

Senior Member
Jan 20, 2013
578
97
Hello,

I recently clean flashed stock 5.1.1 lollipop on my nexus 4, installed xposed and re-installed all my modules, set them all up, etc. And noticed that at the end of it all I experience boot loops on approximately every other boot.

I uninstalled and re-installed xposed, wiped dalvik and cache, and disabled all my modules and enabled them one by one to see if I could catch the culprit, but it seems to happen completely random.. I can't find anything online about it, so I'm not sure if anyone knows the cause for this or how to fix it.

I managed to pull the logs. A bunch of errors pop up near the end, unfortunately I don't know what they mean. Any help would be appreciated, thanks.

Log: http://pastebin.com/kdLFw9uf
 

shranav

Senior Member
Oct 29, 2010
209
23
India
Hello. I am having HTC One A9 running 6.0 odexed rom. Rooted/twrp installed. when i am trying to install v80 sdk23 arm 64, it is leaves my phone on boot screen. I waited for 15-20 mins but Nothing happened. i ever cleared dalvik cache after the install. Need help solving this issue. Thanks
 

jkeuclid

Senior Member
Mar 19, 2014
508
112
And any detailed information about what you tried to install Xposed would be appreciated, too.

Post #2 contains all the required information to identify the correct Xposed framework version by yourself.
Yes of course, it was late when I posted after having rooted LP, normally I have more detail my appologies. I am in fact using ARM SDK21 from #2 FYI. I've started over and updated to 30g but I'm having some difficulty installing TWRP atm so once done with that I'll post back up.

btw, good job on your Ad blocking thread :good:
 
Last edited:

Top Liked Posts

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