A less-extreme approach is to disable the Xposed module but not remove it. Head over to data directory of Xposed FrameworkInstaller /data/data/de.robv.android.xposed.installer
, go inside conf
, and remove the entry for your module from modules.list
. It is up to you how you remove the line.
When uncertain about whichthe exact module is causing the boot issue
Go to to data directory of Xposed Installer /data/data/de.robv.android.xposed.installer
, go inside conf
, and remove or rename or revoke read permission from modules.list
.
Alternatively, create a blank file named disabled
(not disable
) inside conf
directory. This would cause Xposed Framework to not activate any module during boot. You can create the file using command-line
adb shell touch /data/data/de.robv.android.xposed.installer/conf/disabled
Another alternative, per the framework's developer rovo89 is
[It is] possible to disable Xposed by repeatedly pressing one of the hardware buttons during early startup. The phone will vibrate twice when the first key press has been detected. Then you have five seconds to press the same button four more times. Each key press will be confirmed with a short vibration; the final one with a long vibration. It creates /data/data/de.robv.android.xposed.installer/conf/disabled
, which prevents most of Xposed's actions (e.g. ... no modules are loaded). There's no 100% guarantee that this will get you out of a bootloop, but in most cases it should.
Go to to data directory of Xposed Framework /data/data/de.robv.android.xposed.installer
, go inside conf
, and remove or rename or revoke read permission from modules.list
.(Emphasis mine)
Alternatively, create a blank file named disabled
(not disable
) inside conf
directory. This would cause#Remove Xposed Framework to not activate any module during boot. You can create the file using command-lineas a last resort
adb shell touch /data/data/de.robv.android.xposed.installer/conf/disabled
Another alternative, if you're running Android###Android 4.x, is to use
Use the file Xposed-Disabler-Recovery.zip
located at /sdcard/Android/data/de.robv.android.xposed.installer/files
. Flash that file from recovery mode to disable (not remove) Xposed Xposed Framework. It doesn't delete the Installer app.
That ZIPDownload the file from official thread, if you don't have one.
That archive, in essence, changes /system/bin/app_process.orig
to /system/bin/app_process
. You can make those changes on your own toousing adb in recovery mode.
###Android 5.x
The official thread hosts an uninstaller file. Download the one relevant to your CPU's architecture and flash it from recovery mode.
If you're not using the official Xposed Framework then the uninstaller may not work for you. It may even cause unforeseen issues. Best is to search the web for the uninstaller.