Remove All Ads from XDA
Honor View 10

[DISCUSSION] Xposed for Lollipop

2,581 posts
Thanks Meter: 79,237
 
By rovo89, Senior Recognized Developer on 13th February 2015, 09:48 PM
Post Reply Email Thread
31st December 2017, 11:20 PM |#12511  
Member
Flag Ankara
Thanks Meter: 2
 
More
Wrong place sorry.
 
 
8th January 2018, 09:18 PM |#12512  
Junior Member
Thanks Meter: 1
 
More
Xposed install but Not active
Lava Iris Fuel F1
Flash with TWRP recovery
Log Is empty
i tried :
create a boot scripts in init.d still not Working

Delete some system apps
No disable file
Tried everything But Not working
Is is because of sd card?
9th January 2018, 10:09 AM |#12513  
marcdw's Avatar
Senior Member
Flag Baldwin Park
Thanks Meter: 1,924
 
More
@abu13, sometimes a reboot will fix the not active thing. If not try this tip that worked for one user. Choose to reboot the system from within the Xposed Installer app. The app will prompt for root and then it'll reboot.
After that the framework _should_ be active. Hopefully.

EDIT: In another thread someone with the same issue also fixed it by changing the language to English (the installer or his ROM, not sure).


LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5
9th January 2018, 06:48 PM |#12514  
PiggyFlooper's Avatar
Senior Member
Thanks Meter: 289
 
More
Quote:
Originally Posted by doubledragon5

I have had that name for about 15ys. Took martial arts class, that is were I got the name. It's a hand strike.

I see, now I'm informed
Bro, if you're on Nougat, Xposed is available here - https://www.xda-developers.com/offic...id-nougat/amp/

Edit- more specifically:
http://dl-xda.xposed.info/framework/

I'm on Galaxy J7 7.0N and it's working, make sure you have Xposed Installer v.3.1.4 or it won't show Xposed as being active, gl
9th January 2018, 11:43 PM |#12515  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by marcdw

@abu13, sometimes a reboot will fix the not active thing. If not try this tip that worked for one user. Choose to reboot the system from within the Xposed Installer app. The app will prompt for root and then it'll reboot.
After that the framework _should_ be active. Hopefully.

EDIT: In another thread someone with the same issue also fixed it by changing the language to English (the installer or his ROM, not sure).


LG G3 D851, PAC-MAN LP ROM, MultiROM, Tapatalk 4.9.5


i have tried that one Too..
I cant even save my Error log to sd card..why?
10th January 2018, 11:03 AM |#12516  
marcdw's Avatar
Senior Member
Flag Baldwin Park
Thanks Meter: 1,924
 
More
Quote:
Originally Posted by abu13

i have tried that one Too..
I cant even save my Error log to sd card..why?

I just saw another tip. Try toggling the Xposed Status switch on and off. Maybe it needs a kick sometimes.

ZTE Axon 7 A2017U, Dark ROM, Llama Sweet Kernel, microG (NoGAPPS),, Multiboot, Tapatalk 4.9.5
11th January 2018, 12:51 PM |#12517  
marcdw's Avatar
Senior Member
Flag Baldwin Park
Thanks Meter: 1,924
 
More
@abu13, on my G3 I've been messing around with Lollipop ROMs looking for something to replace my LiquidSmooth (for some reason I keep losing root on most of them).
Anyway, I hit the same problem as you. No matter what the Xposed framework would not activate. Went back to v87 and all was good.
I forgot what version you were trying.


ZTE Axon 7 A2017U, Dark ROM, Llama Sweet Kernel, microG (NoGAPPS),, Multiboot, Tapatalk 4.9.5
11th January 2018, 12:59 PM |#12518  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by marcdw

@abu13, on my G3 I've been messing around with Lollipop ROMs looking for something to replace my LiquidSmooth (for some reason I keep losing root on most of them).
Anyway, I hit the same problem as you. No matter what the Xposed framework would not activate. Went back to v87 and all was good.
I forgot what version you were trying.


ZTE Axon 7 A2017U, Dark ROM, Llama Sweet Kernel, microG (NoGAPPS),, Multiboot, Tapatalk 4.9.5


ok thanks Leme Try v 87

---------- Post added at 12:59 PM ---------- Previous post was at 12:55 PM ----------

Quote:
Originally Posted by marcdw

@abu13, on my G3 I've been messing around with Lollipop ROMs looking for something to replace my LiquidSmooth (for some reason I keep losing root on most of them).
Anyway, I hit the same problem as you. No matter what the Xposed framework would not activate. Went back to v87 and all was good.
I forgot what version you were trying.


ZTE Axon 7 A2017U, Dark ROM, Llama Sweet Kernel, microG (NoGAPPS),, Multiboot, Tapatalk 4.9.5


And One Thing In my data/user folder
There Is extra 0 folder and all the internal data Goes to that folder How To moved my folder to data user and what (permission)?
11th January 2018, 01:01 PM |#12519  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by marcdw

@abu13, on my G3 I've been messing around with Lollipop ROMs looking for something to replace my LiquidSmooth (for some reason I keep losing root on most of them).
Anyway, I hit the same problem as you. No matter what the Xposed framework would not activate. Went back to v87 and all was good.
I forgot what version you were trying.


ZTE Axon 7 A2017U, Dark ROM, Llama Sweet Kernel, microG (NoGAPPS),, Multiboot, Tapatalk 4.9.5

can u show me ur data /user folder once
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2018-01-11-17-30-39.png
Views:	158
Size:	39.1 KB
ID:	4386074  
12th January 2018, 11:44 AM |#12520  
marcdw's Avatar
Senior Member
Flag Baldwin Park
Thanks Meter: 1,924
 
More
Quote:
Originally Posted by abu13


And One Thing In my data/user folder
There Is extra 0 folder and all the internal data Goes to that folder How To moved my folder to data user and what (permission)?

No need to move anything.
/data/user/0/ is a link to /data/data/.
Everything is normal.

On Nougat you'll also have /data/user_de/.


Samsung Galaxy Light SGH-T399, CyanogenMod CM12 ROM, microG (NoGAPPS), Tapatalk 4.9.5
17th January 2018, 08:01 AM |#12521  
Junior Member
Thanks Meter: 1
 
More
Quote:
Originally Posted by marcdw

No need to move anything.
/data/user/0/ is a link to /data/data/.
Everything is normal.

On Nougat you'll also have /data/user_de/.


Samsung Galaxy Light SGH-T399, CyanogenMod CM12 ROM, microG (NoGAPPS), Tapatalk 4.9.5


i got an error log ..file is 1.7MB .too big to upload it here
please check i ll drop it in my gdrive

https://drive.google.com/file/d/1C_9...w?usp=drivesdk

---------- Post added at 08:01 AM ---------- Previous post was at 07:52 AM ----------

Quote:
Originally Posted by Portgas D. Ace

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.




Download threads:
@rovo89 version, see post 1

@arter97 version: http://forum.xda-developers.com/xpos...lipop-t3113463

FOR ODEXED SAMSUNG STOCK ROM (LOLLIPOP 5.0.2) USE THIS VERSION.

@wanam version: http://forum.xda-developers.com/xpos...lipop-t3180960

@SolarWarez version for MIUI-based devices: http://forum.xda-developers.com/xpos...-miui-t3367634



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:

See how where the blank space is, here, it says "$API"? That is a variable that is defined below:

...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:


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/show...ostcount=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



please check my error log and solve for please..File is 1.7mb too big to upload it here ..

https://drive.google.com/file/d/1C_9...w?usp=drivesdk
Post Reply Subscribe to Thread

Tags
lollipop, xposed

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes