May 19, 2015 - How to Install Xposed Framework on Android 5.0 & Android 5.1. For 32 bit and 'xposed-sdk22-arm4.zip' for 64 bit architecture. Mar 11, 2015 Android 5.1 (SDK 22) is now out, xposed-arm-20150308.zip is compiled against SDK 21 and won't install. Rovo89 changed the title please recompile with SDK 22 Support for Android 5.1 Mar 11, 2015. Rovo89 added the enhancement label Mar 11, 2015. This comment has been minimized.
Issue description:
I require to get droidmon operating on a specific android picture with predefined guidelines. Xposed framework displays an mistake on installation, that it demands root access.
Atmosphere:
Search engines Google android Emulator running a custom made rooted Google android 4.4.2 times86 picture with kernel edition 3.4.67+ (but i possess the same issue with 3.10+)Utilized guidelines (+ extra params that have nothing at all to perform with android itslef):
- -avd
- -kernel
- -ramdisk
- -no-cache
- -selinux permissive
- -no-snapstorage
- -verbose
- -show-kernel
SDK-Tools-Version: 25.2.2
SDK-Platform-Tools: 24.0.3
Android is set up to allow unkown resources for apks
Already attempted:
- Remounting /program RW
- Using -selinux handicapped (xposed however requires -selinux permissive)
- Removing the update-binary from xposed and run the script with su
Current Status:
If i test installing Xposed i obtain the following log messages from the emulator:
Status-Update:
As i know for right now, the picture was not rooted properly. I rerooted the Picture using the packaged su binary from SuperSU-2.78. I manipulated the system.img by increasing it to a folder on my linux machine and added su and daemonsu (essentially su duplicated and renamed) to /program/xbin/ and changed permissions to 6755 for both documents. In addition for today i added 2 outlines to the end of /etc/init.goldfish.sh
After installing both Superuser.apk from SuperSU and a suitable Xposed-Version, Xposed primarily installs but after reboot it leads to segfaults in libdvm.therefore
ltkatana
ltkatanaltkatana
1 Reply
Finally maintained to get this functioning (needs older sdk edition (pre Nov 2016)
SuperSU nevertheless required as told in the question above
Kernel Picture lower than version 3.10 (kernel-qemu or engine classic)
- Start emulator in verbose-mode
- note the short-term document which will be utilized to install /system inside qemu
- Install Xposed but Stop reboot
- Copy temporary program.img from /tmp/android-username/emulator-random chars to permits say your house listing
- Shutdown emulator
- Overwrite present program.img with the one from your home listing
- Start Emulator again
- Xposed should now be operating
Kernel Edition 3.10+ (kernel-ranchu or true sandboxed emulator)
Unfortunatly there is definitely currently no identified method of changing the program.img from within the ranchu-emulator, ranchu seems to prevent every write-operation.The blocked operations let the program believe, that the partition is certainly broken, so the program remounts the partition readonly as a safty fallback.
Two found work-arounds:
1.) Make use of parameter -motor common when starting the emulator (as a result forcing kernel-qemu) you can make use of the actions above to perform your modifications
2.) Use a kernel-image lower edition 3.10 to prevent emulator ranchu. You can use the steps above and after your adjustments have been used use the earlier kernel-image once again
ltkatanaltkatana