The is an incredibly powerful tool. But because of this power, there's a chance that something could go wrong when installing a broken or incompatible module, which can cause or even your phone. Depending on how bad the situation is, the only way to get things back up and running might be to disable the Xposed Framework itself, which renders any broken modules powerless. There are two ways to disable Xposed — either using a safe mode button combination, or by flashing the Xposed disabler ZIP.

Regardless of which method you use, you should be able to recover from a bootloop long enough to uninstall the broken module. Once you've done that, you can re-enable Xposed to get all of your old modules back the way they were, and your phone should have no problem booting up again. Don't Miss: Method 1: Use the Button Combination As I mentioned, there are two methods to temporarily disable Xposed. This first method is by far the easiest, so you should try this before doing anything else if you suspect that an Xposed module is causing your phone to bootloop. This doesn't work with every phone, but it works with the vast majority of devices. The short version of these instructions is simple: Press any hardware button repeatedly while your phone is booting to disable Xposed. But in case you need more details, I'll outline the whole process.

Don't Miss: To start, press and hold your phone's power button for ten seconds, which will trigger a hard reboot. As soon as the screen goes black (before any pre-boot splash screens appear), start clicking any hardware button on your phone repeatedly. Any physical button should work, but we recommend pressing the power button repeatedly in case your phone uses other button combinations to boot into recovery mode, for example. Eventually, you'll feel two short buzzes from your phone's vibration motor — this is Xposed acknowledging that you're trying to enter safe mode. From there, press the same button four more times in quick succession, and with each press, you'll feel another vibration. After the fourth button press is acknowledged, you'll feel a long vibration — at this point, you can stop pressing the button, because your phone will now boot up with the Xposed Framework disabled. When your phone boots up, open your Xposed Installer app and you'll notice that the framework is disabled.

From here, just head to the Modules section, then long-press the broken module and choose 'Uninstall' on the popup to remove it. Next, you'll probably want to re-enable Xposed. To do that, open your favorite root file browser and navigate to the following directory: /data/data/de.robv.android.xposed.installer/conf/ Once you've found this folder, locate the file named 'disabled' and delete it. After you've done that, just restart your phone, and when you get back up, Xposed will be enabled again.

All of your modules will still be enabled (with the exception of the broken one you uninstalled), so it'll be like nothing ever happened. Method 2: Sideload the Xposed Disabler ZIP If the above method didn't work, you'll have to sideload the Xposed Disabler ZIP using. If you don't already have TWRP recovery installed, a last resort option is to factory reset your phone.

But to start with this second method, make sure you have on your computer. From there, you'll need to boot your phone into recovery mode, which is a process that will vary depending on your device. So if you don't know the button combo for entering recovery mode on your model, we suggest googling 'boot into recovery mode ' and following one of the instructional videos. Almond Verba Civic Culture Pdf Viewer.

Once you've put your phone into recovery mode, tap the 'Advanced' button on TWRP's main menu, then select 'ADB Sideload.' From there, swipe the slider at the bottom of the screen to initiate the sideload process. When that's finished, tap 'Reboot System' on your phone, and when you get back up, Xposed will be disabled. So, again, just uninstall the broken module from the Modules section in your Xposed Installer app, then delete the disabler file as depicted at the end of Method 1 above. Which of these two methods ultimately got you back up and running? What module did you install that soft-bricked your device in the first place? Tell us all about it in the comment section below, and don't hesitate to ask any questions you might have!