Xposed framework & Android corresponding version

.

Android4.3-4.4 — — — — — — — — — — — — — — — — — — XposedInstall2.7

Android5.0 — — — — — 6.0. — — — — — — — — — — — — — — — — — XposedInstall2.7

Android7. — — — — — x 8. X. — — — — — — — — — — — — — — — — — XposedInstall3.1.5


The Xposed framework is installed through recovery


Need to distinguish CPU model and Android system version,Xposed framework RECOVERY brush file. Such as:

  • Xposed-v79-sdk23-x86.zip
  • Xposed-v79-sdk23-arm64.zip
  • Xposed-v79-sdk23-arm.zip

 

Xposed framework uninstall

Through the Xposed framework installer installed will automatically generate xposed named. Zip file in the SD card root directory, recovery brush can be disabled and then uninstall;

Through recovery brush into the Xposed framework uninstall directly copy the following corresponding version. Zip file brush into the disablement can be: Xposed framework recovery uninstall disable file, uninstall disable Xposed framework such as:

  • xposed-uninstaller-20150931-x86.zip
  • xposed-uninstaller-20150931-arm64.zip
  • xposed-uninstaller-20150931-arm.zip


Xposedinstall.apk is recommended to install and uninstall the Xposedframework


The Xposed framework is brushed into xposedinstall.apk

http://androidwing.net/index.php/256

Github.com/rovo89/Xpos…

In the process of integrating the custom ROM, I found that the extracted flash-script.sh could run directly in recovery.

Brush into the Xposed can also put the zip package decompressed out, system into any folder, flash-script.sh into the same directory, execute flash-script.sh can brush into the operation.

According to flash-script.sh script content, it can be found that in fact, the operation of the xposed is just some replacement and links to the system file:

In fact, xposed’s brush into just replace the system folder under some content, so as long as there is a way to access the system folder.

In TWRP, you can enter the command whoami to find out why you can access the system:



In other words, under TWRP, it actually has root permission, so there is no need to brush into su.

The correct way to do this is to swipe xposed. Zip directly under recovery. Then boot restart, found that the mobile phone is not SU root permissions, but the Xposed is effective.

On the one hand, it is true that you need root permission to access the system, but recovery already has it, in fact, there is no extra brushing. On the other hand, if you use the Xposed installer to brush in or restart and so on, it is indeed necessary to su authorization.