I installed the xLoud mod from pimp my ROM, and now I want to remove it so I can install KingBeatZ mod, so I disabled it and replaced the build.prop to the stock one for my ROM, caused boot loop so I restored to the modded one. How can I completely uninstall it? I tried the rescue package as well.
NEXUS 7:
Unlock/Root
Prime D
M-Kernel
PimpMyROM
Related
Hi
I am using miui v5 4.3.x
Since it still does not have a multirom supported kernel, I decided to install ubuntu touch by their official dual boot method. Everything went fine but it installed supersu. Since miui already has a btter superuser manager, I decided to remove it. So I went to settings in supersu app and then chose the option that removes supersu so that we can install some other superuser manager.
Now I removed supersu, but it seems like miui su app is no more in use. Even though I have enabled root in that app, apps still say no root.
Please tell me how to fix this and get back to default miui su manager.
have you tried re-rooting via the app?, its in the android market,there are usually conflicts if you have two root apps, disable/ remove one and clear the data and start from scratch.
or just restore to the backup you made before you installed ubuntu,
Hi guys, so recently I flashed the latest factory image MMB29P afresh, and was looking to flash Xposed v79 immediately after rooting my phone. So I flash TWRP, flashed SuperSu v2.66, rebooted to system and installed the Xposed Installer apk then flashed xposed-v79-sdk23-arm64.zip via TWRP. However after that, immediately after booting it up, all my apps started going into a meltdown, with both user and system apps crashing on a loop. I already had the Xposed Installer apk installed beforehand, and I tried enabling SU upon boot, but all my apps still continued crashing. Only after uninstalling Xposed then it went back to normal. Is there something wrong with what I am doing? Or is this new update screwing Xposed up? I didn't have this problem with MMB29M, does any MMB29P Nexus 6P users experience this issue?
Try flashing the xposed uninstaller to remove xposed from your device. Wipe all of the data with titanium backup on all xposed modules you have installed and remove them. Wipe the data to the Xposed installer app and delete that as well. Reflash the Xposed installer script through TWRP. After flashing it then try installing the Xposed installer APK. Do not try to install Xposed through the App, you have to flash the installer script through TWRP. I would try that and report back.
FYI I am running xposed successfully on the latest 29P build.
Might be a issue with the latest factory image. Did you check the xposed forum to see if other 6P users were having issues after updating to the latest factory image?
hello2ew said:
Hi guys, so recently I flashed the latest factory image MMB29P afresh, and was looking to flash Xposed v79 immediately after rooting my phone. So I flash TWRP, flashed SuperSu v2.66, rebooted to system and installed the Xposed Installer apk then flashed xposed-v79-sdk23-arm64.zip via TWRP. However after that, immediately after booting it up, all my apps started going into a meltdown, with both user and system apps crashing on a loop. I already had the Xposed Installer apk installed beforehand, and I tried enabling SU upon boot, but all my apps still continued crashing. Only after uninstalling Xposed then it went back to normal. Is there something wrong with what I am doing? Or is this new update screwing Xposed up? I didn't have this problem with MMB29M, does any MMB29P Nexus 6P users experience this issue?
Click to expand...
Click to collapse
If you had the xposed.apk already installed, I'd try uninstalling it. Boot to recovery and use the xPosed uninstall. Reinstall with xPosed zip. Reboot and install the apk. I had an issue when I updated to MMB29P and realized I had titanium restored the apk before I had the zip installed.
Now it works great
Hi everyone,
I have a s4 Active sgh i537. I want to have Lollipop and Xposed installed. To this end I flashed it back to Kitkat, towelroot'd it, flashed the I537_OC7_Stock_Rooted_Deodexed_ROM to preserve the root. I've tried to use the recovery option that comes with the rom to flash the Xposed framework and install the apk but Xposed said that the framework wasn't installed. Figured that the rom doesn't come with a custom recovery. Then I tried afterwards to flash the framework using flashfire the same way I flashed lollipop. The att splash screen load and got stuck for over 6 hours.
I'm going to try reflashing kitkat and starting over but I was wondering if I'm doing something wrong.
rom: http://forum.xda-developers.com/galaxy-s4-active/general/how-to-update-to-i537oc6-5-0-1-t3089355
Xposed framework SDK21 arm v86: http://dl-xda.xposed.info/framework/sdk21/arm/
Edit 1: went through again and I learned I needed the touchwiz Xposed Framework. Installed and my phone now can run Lollipop and install Xposed
New question regarding adb. I'm trying to install MicroG and I can't seem to connect adb and my phone together to remove the /system/priv-app/ and /system/app/ prerequisites any help with this would be extremely helpful
I have a sm-n910v rooted on a fully stock 6.0.1 ROM and I can't seem to install xpossed framework I've tried installing the custom build version for Samsung but it just makes my phone go into a boot loop. And the original versions do the same. When ever I was on jasmine ROM it was already installed on the rom so I never had to install it manually.
Never mind I've figured it out, I was using the xpossed app to install it instead of downloading it and manually installing through recovery. Must of been the way the app installed it that messed it up
Hello! I want to install Extreme Kernel on stock ROM, but I want to backup stock kernel in order to get OTAs (everytime I received an update, I would install/restore stock kernel). How can I do that? Thanks!
The easiest way is to use Magisk Manager.
Stock system -> install Magisk (it automatically creates backup of currently flashed kernel) -> install custom kernel. When OTA arrives, restore stock boot.img from withing Magisk Manager, install OTA, reboot, install Magisk, install custom kernel.
Doublecheck if custom kernel uses only stock Wifi drivers. Some kernels install custom driver in system partition, breaking OTA.
_mysiak_ said:
The easiest way is to use Magisk Manager.
Stock system -> install Magisk (it automatically creates backup of currently flashed kernel) -> install custom kernel. When OTA arrives, restore stock boot.img from withing Magisk Manager, install OTA, reboot, install Magisk, install custom kernel.
Doublecheck if custom kernel uses only stock Wifi drivers. Some kernels install custom driver in system partition, breaking OTA.
Click to expand...
Click to collapse
Does it work in all custom kernels except Void which indicated it won't? If I remember correctly it only works with Franco.
whrynox said:
Does it work in all custom kernels except Void which indicated it won't? If I remember correctly it only works with Franco.
Click to expand...
Click to collapse
I've been using it personally with Franco kernel, but in theory should be fine with any kernel. But I didn't try other kernels, because most of them break OTA..