+- Sinisterly (https://sinister.ly)
+-- Forum: Computers (https://sinister.ly/Forum-Computers)
+--- Forum: Mobile & Tablets (https://sinister.ly/Forum-Mobile-Tablets)
+--- Thread: Tutorial Fixing a bootloop caused by xposed (/Thread-Tutorial-Fixing-a-bootloop-caused-by-xposed)
Pages:
1
2
Fixing a bootloop caused by xposed - pvnk - 02-21-2016
This is a thread for people who are already in the state of "bootloop" or "softbricked" and want to be able to fix their device without 1.) uninstalling xposed framework or 2.) reflash their ROM because they 1.) forgot to make a back-up, 2.) forgot to flash xposed Recovery's zip [everyone], and 3.) really need help because they're desperate and you need your phone right this moment. Feel free to scroll down to Solution portion of the guide if all you need is the directory to fix the issue.
*Prerequisite*
*Custom Recovery (TWRP for me/this tutorial) - You don't have to flash the recovery onto your phone if you don't want to. I didn't flash a custom recovery onto my phone. I fastboot my custom recoveries so I can easily reflash unmodified, vanilla, OEM ROMS without mismatch errors (by way of flashing with stock recovery.)
*USB Cable (For fastboot) [No USB needed if your custom recovery is already flashed]
ADB
USB Debugging enabled
Since we're on a tech forum, I will assume that many of you own a smartphone. It would be to no surprise to me that if you do own a smartphone, you own an Android device and that it's rooted.
There is a framework called xposed framework, which allows you to install custom modules that affect functionality of your phone. (Usually modules improve functionality or fixes certain functionality without a system update.)
Modules are kept updated by choice of the developers and sometimes that leads to no update at all. Experts or tech enthusiasts are attracted to a disgusting word. Experimental.
Experimental modules. Usually modules that have either been developed as an alpha or beta stage and has known to cause issues on certain devices, but too early to identify which devices so it's up to the user to experiment with. Other times, modules are simply outdated for a newer ROM, which makes it overall incompatible. Some modules are outdated, but since they run on barebones (https://wiki.cyanogenmod.org/w/Barebones), they either 1.) will not work or 2.) work. Simple term exchange.
Non-functioning modules are fine, but non-functioning, conflicting, incompatible, outdated motherfking modules are a pain.
Let's get to it.
Let's simulate a scenario.
Background
I installed XBlastTools on my Android device running Lollipop 5.1.1/OxygenOS 2.2.0.
http://repo.xposed.info/module/ind.fem.black.xposed.mods
Module description implied compatibility with my ROM.
Module description was inaccurate.
I soft reboot my phone and encounter a bootloop due to an incompatibility issue.
Solution
Boot into recovery by holding the volume down button while booting.
If recovery is custom recovery, move on to the next step.
If recovery is not custom recovery, reboot into fastboot mode by holding the volume UP button during boot.
Run in adb command
Code:
fastboot boot "customrecoveryfilename.img"Now that you're in TWRP, go to Advanced > File Manager
1.) Browse to /date/data/de.robv.android.xposed.installer/conf/modules.list
2.) Copy the modules.list and (I) put it in your SD card directory via swiping on TWRP recovery
*This is essential if you want to keep your current xposed modules*
3.) Go back to /date/data/de.robv.android.xposed.installer/conf/modules.list and delete the modules.list
4.) Reboot into System
5.) You should be able to access your phone now (effectively fixing the boot loop)
6.) Remove the module that you installed through xposed framework or uninstall the module if it came packaged in a .apk.
*If that's all you wanted for this tutorial, you can take your leave. Further instructions are for the recovering of you current xposed module.
7.) Since you're going to reboot anyway, I recommend booting once again into TWRP. (If you have a file manager on your Android device, you can use it as well.
8.) Go to your SD card and copy the modules.list file that you had.
9.) Go back to /date/data/de.robv.android.xposed.installer/conf/ and re-add the modules.list
10.) Reboot into System
!!!!!!!!!!!!!!!!!!!!!!!!!!
congratulations on fixing your device~
have a nice day
RE: Fixing a bootloop caused by xposed - pvnk - 02-22-2016
is this thread overly high quality?
RE: Fixing a bootloop caused by xposed - pvnk - 02-22-2016
(02-22-2016, 12:23 AM)Yoko Wrote: I think it's just right. Good tutorial.
Thank you!
RE: Fixing a bootloop caused by xposed - Dean Winchester - 02-22-2016
Good tutorial. I'm glad xposed didn't bootloop my device. And how to fix devices that don't have a TWRP out for them yet.
RE: Fixing a bootloop caused by xposed - pvnk - 02-22-2016
(02-22-2016, 02:13 PM)Jimmy Wrote: Good tutorial. I'm glad xposed didn't bootloop my device. And how to fix devices that don't have a TWRP out for them yet.
If your device doesn't have a TWRP out, I am very curious as to how you rooted it and got xposed in the first place. Xposed framework itself doesn't cause bootloops either. It's just a framework.
RE: Fixing a bootloop caused by xposed - Dean Winchester - 02-27-2016
(02-22-2016, 04:11 PM)primitiv Wrote: If your device doesn't have a TWRP out, I am very curious as to how you rooted it and got xposed in the first place. Xposed framework itself doesn't cause bootloops either. It's just a framework.I rooted it using KingRoot. It doesn't need a recovery to flash.
RE: Fixing a bootloop caused by xposed - zorrophreak - 02-27-2016
(02-27-2016, 06:39 AM)Jimmy Wrote: I rooted it using KingRoot. It doesn't need a recovery to flash.
What device do you have. The method that root software uses is incredibly hacked together and likes to break itself. I'm pretty sure it uses an ancient su binary, but regardless.
And primitiv, congratulations on this very HQ thread. I peruse the Android scene of this and always thought of Xposed as the Cydia of Android (I use this analogy as I come from iOS Jailbreaking [which started my "hacking" infatuation]). But it is a very good thread and I am sure it will be helpful to many users!
RE: Fixing a bootloop caused by xposed - Dean Winchester - 02-27-2016
(02-27-2016, 06:44 AM)zorrophreak Wrote: What device do you have. The method that root software uses is incredibly hacked together and likes to break itself. I'm pretty sure it uses an ancient su binary, but regardless.
And primitiv, congratulations on this very HQ thread. I peruse the Android scene of this and always thought of Xposed as the Cydia of Android (I use this analogy as I come from iOS Jailbreaking [which started my "hacking" infatuation]). But it is a very good thread and I am sure it will be helpful to many users!
HP Slate 7 VoiceTab.
RE: Fixing a bootloop caused by xposed - zorrophreak - 02-27-2016
Gonna lead you here if you re-root http://forum.xda-developers.com/showthread.php?t=2422353. Seeing as there was an alternative that wasn't horrible, you should've used it
RE: Fixing a bootloop caused by xposed - pvnk - 02-27-2016
(02-27-2016, 06:39 AM)Jimmy Wrote: I rooted it using KingRoot. It doesn't need a recovery to flash.
It was a trust issue with me. Chainfire is respected and well represented. Kingroot has had many complaints from their userbase.