i have successfully managed to install xposed framework and reboot my phone without any errors. But after i activate one module andm then reboot, my phone stucks on a boot logo forever until i wipe all data via recovery mode. What might be the cause of this, and how can i solve it?
phillipjack said:
i have successfully managed to install xposed framework and reboot my phone without any errors. But after i activate one module andm then reboot, my phone stucks on a boot logo forever until i wipe all data via recovery mode. What might be the cause of this, and how can i solve it?
Click to expand...
Click to collapse
We cannot help you at all.
We do not know what phone you have. We do not know what ROM your phone has. We do not know what version of Xposed you tried to install. We do not know what method you tried to install it with. We do not know what module you are trying to activate. We do not know what mistakes you made, what error messages were generated, or what was recorded in your log files.
We do not know why you didn't create a backup before installing Xposed, or why you don't restore that backup now.
Without all of this information, we cannot help you.
Related
after installing the xposed framework i was stuck in a bootloop,
the safemode saved me, it worked and now i booted successfully into android.
do i have to delete or deinstall now something before i reboot the device again?
schlunk said:
after installing the xposed framework i was stuck in a bootloop,
the safemode saved me, it worked and now i booted successfully into android.
do i have to delete or deinstall now something before i reboot the device again?
Click to expand...
Click to collapse
You carefully avoided to mention any detail, so I can't help with the bootloop.
If you want to remove Xposed completely, press the "uninstall" button in the app, then uninstall the Xposed Installer app and any modules.
sry,
i am on an alcatel 6012d
android 4.2.2 kernel 3.4.5
after installing couldnt get pass the logo.
i did a cache & data swipe in the boot recovery via vol+ power.
after that the xposed safemode still worked and it finally booted.
do i have a clean factory android now or are there some files left?
i dont see xposed in the applications anymore.
btw. no idea if i did something wrong when installing, but with the phone xposed doesnt work it seems..
So, I have an old droid x with the CM 11 rom on it and for some reason I can't get xposed to work now. I had to flash my rom again cause I got soft bricked after trying some status bar mod and now it won't work at all. I had it installed the first time and it was working with the snapshare module, but now all I get is the "framework not installed." I've tried installing but whenever i reboot I get soft bricked so I have to flash the rom again.
1Koncept said:
So, I have an old droid x with the CM 11 rom on it and for some reason I can't get xposed to work now. I had to flash my rom again cause I got soft bricked after trying some status bar mod and now it won't work at all. I had it installed the first time and it was working with the snapshare module, but now all I get is the "framework not installed." I've tried installing but whenever i reboot I get soft bricked so I have to flash the rom again.
Click to expand...
Click to collapse
Try choose other installation type in Settings.
pyler said:
Try choose other installation type in Settings.
Click to expand...
Click to collapse
Tried that, it installs but when I reboot I get soft bricked. I'm out of ideas other than to completely SBF back to original rom and flash all over again. I feel something may be corrupt. Is there an xposed folder somewhere on my phone that may be causing an error?
1Koncept said:
Tried that, it installs but when I reboot I get soft bricked. I'm out of ideas other than to completely SBF back to original rom and flash all over again. I feel something may be corrupt. Is there an xposed folder somewhere on my phone that may be causing an error?
Click to expand...
Click to collapse
I only attempted to load Xposed on my DX for the first time today and couldn't get it to install, but I worked past the soft brick by booting into recovery and re-flashing my system ROM and gapps. (cwm-11-2014-0817-UNOFFICIAL-shadow.zip)
I tried flashing from TWRP and received the following message:
E:Error executing updater binary in zip '/sdcard/cwm-Xposed.Framework.Installer.v.2.4.1.zip'
I made a backup this time and I'll see if I can figure out what's wrong.
Scott
1Koncept said:
So, I have an old droid x with the CM 11 rom on it and for some reason I can't get xposed to work now. I had to flash my rom again cause I got soft bricked after trying some status bar mod and now it won't work at all. I had it installed the first time and it was working with the snapshare module, but now all I get is the "framework not installed." I've tried installing but whenever i reboot I get soft bricked so I have to flash the rom again.
Click to expand...
Click to collapse
I spent some time troubleshooting this evening, checked logs while attempting to flash, and found that the main issue was that the installer script thought that /system/ was at 100% capacity (0MB free). I disabled USB debugging (menu, settings, developer options, USB debugging) and was able to flash through TWRP. After rebooting, the Xposed Installer showed a newer version was available, so I used the app to install it without any problems. I installed a few modules and rebooted. Titanium Backup wanted me to switch USB debugging back on, so I did. Everything seems to be working (including XPrivacy).
Reminder: Make a full backup from recovery before *AND* after you get it working. Make sure you copy the backup to your computer in case you have to wipe the phone.
I hope this helps!
Scott
0xScott said:
I spent some time troubleshooting this evening, checked logs while attempting to flash, and found that the main issue was that the installer script thought that /system/ was at 100% capacity (0MB free). I disabled USB debugging (menu, settings, developer options, USB debugging) and was able to flash through TWRP. After rebooting, the Xposed Installer showed a newer version was available, so I used the app to install it without any problems. I installed a few modules and rebooted. Titanium Backup wanted me to switch USB debugging back on, so I did. Everything seems to be working (including XPrivacy).
Reminder: Make a full backup from recovery before *AND* after you get it working. Make sure you copy the backup to your computer in case you have to wipe the phone.
I hope this helps!
Scott
Click to expand...
Click to collapse
Thanks, I got it to work finally.. I've been trying for 2 weeks now so it feels quite rewarding.
[Q] >> I've Installed Xposed & Installed Modules, and Now I'm STUCK! Please Help? <<
Hello, I have a Galaxy S5 G900T and I installed Xposed and it was interesting as I thought it was a "Cydia" equivalent to the Android. And I installed modules that could help "tweak" my S5, and after I have finished installing them and I rebooted, now I CAN'T SEE OR ACCESS MY LOCKSCREEN PASSWORD! The one that is the Pattern Lock where you can do a square or Z pattern.. but it just disappeared and it's not even showing up, even if I tapped a lot. You can see my picture attachment below which even the Emergency Button and even the Camera in the corner was gone in the lockscreen
Although I can still receive Calls, Messages and even Alarm Notifications, my real suspicion is that I've installed an Xposed Module, that Disabled my entire lockscreen or something that I haven't fully checked out yet, that caused this without me knowing it
Now I know I have options to do Factory Reset and etc.. however, I know there is still a way I can AT LEAST access my Home Screen or Have a Lockscreen reset itself to show up so I can figure out which of the apps or modules that made my lockscreen disappeared
Does anyone know a way in which we can reset the Lockscreen for it to show up? Or a way to be able to access the Home Screen? Or be able to uninstall Xposed and its modules remotely?
Boot into custom recovery, mount data partition and delete /data/data/de.robv.android.xposed.installer/conf/modules.list
C3C076 said:
Boot into custom recovery, mount data partition and delete /data/data/de.robv.android.xposed.installer/conf/modules.list
Click to expand...
Click to collapse
OR he could just flash this http://forum.xda-developers.com/showpost.php?p=60468815&postcount=18
A few fix tips
A few things you could try.
1) Flash the xposed framework disabler zip file via your recovery. Find out how to do that here
2) Use ADB to disable the pattern. Find out how to do so here
3) As a last resort, completely factory reset your phone. A google search will point you in the right direction.
Hope this helps, don't forget to thank if it does.
@C3C076 @Agent-Droid @Kris the wizz 15 Thank you for your replies! I tried doing flash a lot of times and even put the Zip files in my SD card and even tried out the methods in http://forum.xda-developers.com/showthread.php?t=2620456 but now the next problem is I keep getting this error "E: footer signature is wrong, E: signature verification failed", and even if it says "Applying Update Complete'' it just reboots it and does nothing
How can we go through that?
EDIT: I haven't did the ADB procedure as I'm still trying to understand all of this, I would really appreciate any help given
You have to use custom recovery since only they can be set to ignore signature verification of zip files to be flashed. If it is a custom recovery, check its options.
Finally it's fixed now! IT WAS A MIRACLE! I suddenly remembered and I actually used AndroidLost in my computer and it helped "unlocked" the screen, but the funny thing was it didnt fully unlock the screen but it just opened Google Speech, and by that time, MultiWindow was opened so I was scared to death and just backed up everything, removed the lockscreen, and uninstalled Xposed and the modules that messed up.. I was scared as hell but now its working lol
But what I found out about my recovery is that, It's pretty much "broken" seeing that even USB debugging wont work in my computer, Kies and Odin can't read my phone being plugged in, and My Recovery can't even Flash zip files anymore therefore kinda rendering it useless not unless, I fully factory reset my phone
Now for people who don't wanna go through this experience, I fully recommend you download "AndroidLost" or any of those apps that help you unlock your phone when your phone is lost.. and to also read http://forum.xda-developers.com/showthread.php?t=2620456 so you can be prepared and have a better Recovery so you don't have to go through this
Take note of that
Just to clarify
MoRTiZz3 said:
@C3C076 @Agent-Droid @Kris the wizz 15 Thank you for your replies! I tried doing flash a lot of times and even put the Zip files in my SD card and even tried out the methods in http://forum.xda-developers.com/showthread.php?t=2620456 but now the next problem is I keep getting this error "E: footer signature is wrong, E: signature verification failed", and even if it says "Applying Update Complete'' it just reboots it and does nothing
How can we go through that?
EDIT: I haven't did the ADB procedure as I'm still trying to understand all of this, I would really appreciate any help given
Click to expand...
Click to collapse
Well, the xposed disabler zip counts on you having a custom recovery installed. You (correct me if I'm wrong) seem to be running stock samsung recovery, which won't flash the zip properly due to certain signatures that the recovery needs.
Since you've already rooted, any warranty you may have had is probably null and void anyway, so you may as well go the whole nine yards and install a custom recovery. You can find out how to do so here or here
Not only will this enable you to flash the xposed disabler zip file, it will also open you up to a world of custom Roms.
The ADB procedure basically uses root access to reset the pattern in your phone so as to enable you to use any pattern you please. That should help you access the xposed app to disable all the modules, and re-enable them as needed.
None the less, here's a few informative links:
1) What is ADB?
2) What's fastboot?
3) Easily intall ADB and Fastboot
4) What is a custom recovery?
5) What is a custom ROM?
Read through these, and then we can make a comprehensive decision.
Sorry for assuming you don't already know this stuff.
I have rooted my device (Samsung S7 Edge) with the help of odin without taking any backups
Then I tried to install xposed 3.0.1 and in the framework I just selected 87. I didn't use the recovery mode on Marshmallow, and tried to install exposed directly by running apk. After I clicked reboot, the fone is unable to boot again. It is stuck on the first screen with Samsung Galaxy S7 Edge written.
I tried to factory reset, I did, even then I couldn't get luck to get it booted.
I think uninstalling xposed may be the solution, but I dont have any backup recorvery file.
Please help and let me know how to get my device booted.
I was using my phone normally and closing the browser while suddenly the phone restated and went to download mode. I am not able to do anything except going into recovery mode. The normal restart, power off/on goes to download mode. This happened all of a sudden. I have not dropped my phone or anything. I’m my phone is rooted and do have magisk installed. What should I do to make the phone work again? Also, is there any way to save the data?
This happens also to my phone (going to Recovery mode instead of going to system upon reboot) when I installed an Xposed module which is not compatible with the current Rom. Instead of going to bootloop, it just goes to Recovery.
To fix this, I just disable/delete this module from Recovery - File Manager/data/adb/modules and delete the module.
You can try deleting the module that you think causes this or worst scenario deleting the magisk itself. But you can always flash back the magisk zip after rebooting normally.
XTrail02 said:
This happens also to my phone (going to Recovery mode instead of going to system upon reboot) when I installed an Xposed module which is not compatible with the current Rom. Instead of going to bootloop, it just goes to Recovery.
To fix this, I just disable/delete this module from Recovery - File Manager/data/adb/modules and delete the module.
You can try deleting the module that you think causes this or worst scenario deleting the magisk itself. But you can always flash back the magisk zip after rebooting normally.
Click to expand...
Click to collapse
I didn’t install any module and also my phone isn’t going into recovery mode. It goes into download mode automatically. I can go into recovery mode but the recovery mode is the basic one not something like TWRP so it does not have that file manager you are talking about.
zaidbaby said:
I didn’t install any module and also my phone isn’t going into recovery mode. It goes into download mode automatically. I can go into recovery mode but the recovery mode is the basic one not something like TWRP so it does not have that file manager you are talking about.
Click to expand...
Click to collapse
Sorry to hear that. I can only think of flashing your stock Rom to make your phone run again, but to do this will most prabably wipe your data.
XTrail02 said:
This happens also to my phone (going to Recovery mode instead of going to system upon reboot) when I installed an Xposed module which is not compatible with the current Rom. Instead of going to bootloop, it just goes to Recovery.
To fix this, I just disable/delete this module from Recovery - File Manager/data/adb/modules and delete the module.
You can try deleting the module that you think causes this or worst scenario deleting the magisk itself. But you can always flash back the magisk zip after rebooting normally.
Click to expand...
Click to collapse
Is there a way to install TWRP in this state? So I can at least copy over my files to the SD Card?
zaidbaby said:
Is there a way to install TWRP in this state? So I can at least copy over my files to the SD Card?
Click to expand...
Click to collapse
Yes, twrp is installed in download mode via Odin, on my device, Samsung Galaxy. I don't know about your phone unit. Follow the instructions on your phone's twrp forum.