So I have twrp and rooted, running Xposed gravity box. I did not backup ROM when I started. Can I do a factory data wipe and not loose twrp and just reflash supersu? Or will I loose everything? My goal is to get the phone back to when I opened up the box new but keep twrp, bootloader unlocked and rooted.
How did you get Xposed to working, after installing Xposed and the apk my phone booted fine, but if I install any module I get a bootloop
Luminis1987 said:
How did you get Xposed to working, after installing Xposed and the apk my phone booted fine, but if I install any module I get a bootloop
Click to expand...
Click to collapse
You have to use v87 of Xposed Framework as it has a workaround for an issue caused by Android November Security Update.
Any earlier version will bootloop as soon as you enable any module.
Related
Hi, I'm pretty sure I flashed the correct Xposed, but then it started to bootloop and I had the option to "Download and recovery",
So now I'm downloading.
Any other solution?
Boot to recovery and flash Xposed uninstaller. If you try to install Xposed again make sure you choose correct version. You need "xposed-v85.1-sdk23-arm64-custom-build-by-wanam-20160530".
yiftach said:
Hi, I'm pretty sure I flashed the correct Xposed, but then it started to bootloop and I had the option to "Download and recovery",
So now I'm downloading.
Any other solution?
Click to expand...
Click to collapse
I bought this phone yesterday. I could never start using a device unless I unlock bootloader, root and install xposed. I managed to unlock bootloader, flashed TWRP and also flashed systemless SuperSu (2.74-2). Also, I installed systemless xposed (i have shared link below). Phone took sometime and making me to think it is stuck in bootloader. I switched off and start in TWRP. Wiped art/dalvik and cache. Restarted normally. Everything worked fine.
Someone suggested here how to install official xposed (http://newesc.com/es/instalar-xposed-huawei-p9/).
But I installed systemless xposed (see here: http://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268) which works fine without the need of any changes in /system/emui/base/prop/local.pro with this line "ro.config.hwtheme=1" as mentioned in the link I shared above.
Thank you guys!
Hi, I have an HTC one m7 with stock firmware, 5.0.2.
I have installed superSU, and afterwards xposed. All working, modules too, but now I need to uninstall it because come apps won't work. I downloaded the uninstaller zip from the xposed thread, installed it via twrp, but when I reboot the phone it gets stuck on booting with the HTC one logo.
I removed all the modules before uninstalling xposed.
When I install again xposed the phone boots normally.
How can I solve this?
Davicode said:
Hi, I have an HTC one m7 with stock firmware, 5.0.2.
I have installed superSU, and afterwards xposed. All working, modules too, but now I need to uninstall it because come apps won't work. I downloaded the uninstaller zip from the xposed thread, installed it via twrp, but when I reboot the phone it gets stuck on booting with the HTC one logo.
I removed all the modules before uninstalling xposed.
When I install again xposed the phone boots normally.
How can I solve this?
Click to expand...
Click to collapse
Did you disable the framwork in the xposed installer app before you tried to uninstall it?
In on marshmallow, anyone can't do it, can't even press remove
Davicode said:
Hi, I have an HTC one m7 with stock firmware, 5.0.2.
I have installed superSU, and afterwards xposed. All working, modules too, but now I need to uninstall it because come apps won't work. I downloaded the uninstaller zip from the xposed thread, installed it via twrp, but when I reboot the phone it gets stuck on booting with the HTC one logo.
I removed all the modules before uninstalling xposed.
When I install again xposed the phone boots normally.
How can I solve this?
Click to expand...
Click to collapse
Restore your /system nandroid backup you (should) have made before flashing Xposed. Worst case, you'll have to re-flash your rom.
Solved it by wiping dalvik, thank you!
Hi folks,
i hope i im the right Forum as it seams more a xposed as supersu problem.
I have a Moto X Style rooted with System-less SuperSU 2.78 and Xposed "xposed-v86.1-sdk23" by romracer, Stock ROM 6.0.
Just got a notification that there is a security update available, proceeded but won´t flash. Stops with Error Code 7.
I thought OTA would work with system-less.
Tried also with disable Xposed. Same result. By the way when the phone reboots for flashing it goes into The Recover TWRP 3.0.2 GUI. Anyway i saw the error when switching to the log view.
Any idea whats wrong or i miss?
May i have to restore custom recovery, and if so can i flash the stock recovery with the existing TWRP or do i have to go ADB?
Thanks
Thomas
You have to flash stock recovery image (and probably also boot image) for OTA to work.
Simply use fastboot to flash those. Leave system intact.
Thanks, will do so.
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
6opuc said:
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
Click to expand...
Click to collapse
https://github.com/rovo89/XposedBridge/wiki/Bugs#how-can-i-get-logs
Get a adb logcat on boot stuck with xposed installed, put it on pastebin and link here to see why isn't booting.
dcastro172 said:
https://github.com/rovo89/XposedBridge/wiki/Bugs#how-can-i-get-logs
Get a adb logcat on boot stuck with xposed installed, put it on pastebin and link here to see why isn't booting.
Click to expand...
Click to collapse
Hi dcastro172,
Unfortunately adb logcat does not give any info. At this boot stage the device is not detected yet by adb, hence no logcat possible. Is there anything I can collect differently?
Here are two logs from /data/data/de.robv.android.xposed.installer/log/
Perhaps this helps?
6opuc said:
Hi dcastro172,
Unfortunately adb logcat does not give any info. At this boot stage the device is not detected yet by adb, hence no logcat possible. Is there anything I can collect differently?
Click to expand...
Click to collapse
You see bootanimation or only splash logo?
Enviado de meu SM-G900M usando Tapatalk
6opuc said:
Hi all,
I just received an update to my OnePlus 2 - Oxygenos 3.5.5. The update removed the the recovery, root, Magisk and Xposed so I went ahead and flashed the TWRP again and then installed Magisk + phh's SuperUser.
All went fine, the phone booted OK. Then I decided to put back the Xposed and installed it via Magisk Manager and rebooted the phone. The phone got stuck at booting. I suspect that the new OxygenOS update + Xposed are the reason. I am able to uninstall the Magisk using the uninstaller and then can get back to the Magisk + root, but whenever I try to install Xposed the phone gets stuck when booting.
Any idea how to fix this?
Click to expand...
Click to collapse
Xposed v87?
I guess it is boot animation. It it like a clock with moving hands....
Yes. 87
6opuc said:
Yes. 87
Click to expand...
Click to collapse
Looks like update break Xposed, bunch of errors in log, open a issue at Xposed github.
I just decided to get rid of my root, so i uninstalled Magisk with the uninstaller .zip. Then i went on to try to flash the Xposed Uninstaller but it says that i need magisk to uninstall Xposed for some reason. Did i flash the wrong .zip or did i do anything else wrong. I also unrooted with the SuperSu app but i still cant pass the safety net check. Can anyone help with either of these issues? Plz reply
-Me
Try deleting Xposed.img under /data, and if you need to unroot, do not use the super su app, use the unsu signed zip instead, search it up on XDA
If you were using Magisk systemless Xposed it was uninstalled together with Magisk.
And if you were using Magisk, you don't need to do anything else to unroot.
Easiest way to make sure you get back to a clean slate would be to dirty flash your system and then lock your bootloader (be real careful though so you don't brick your device). SafetyNet triggers by more things than just root, among other things an unlocked bootloader...
LordIndigo said:
I just decided to get rid of my root, so i uninstalled Magisk with the uninstaller .zip. Then i went on to try to flash the Xposed Uninstaller but it says that i need magisk to uninstall Xposed for some reason. Did i flash the wrong .zip or did i do anything else wrong. I also unrooted with the SuperSu app but i still cant pass the safety net check. Can anyone help with either of these issues? Plz reply
-Me
Click to expand...
Click to collapse
i was facing the same issues with my Moto X Play Stock firmware 7.1.1 (squid kernel) rooted using magisk and systemless xposed installed.... it was working fine until i installed some xposed modules( iFont, perAppFont, xinsta etc.) and somehow it screwed my phone and bootlooped . after searching for long, this thread https://forum.xda-developers.com/showpost.php?p=76064855&postcount=12 works like a charm !
other xposed disabling method ( Power button combination on booting ) didn't worked for me , maybe i was using systemless xposed module that's why.