Problem with Xposed Installer.
Scenario:
Device Status before problem:
Prior to rooting with Towelroot, installed SuperSU first.
Rooted with Towelroot
Opened SuperSU APK and installed binary via the normal method.
Installed Titanium Backup
Backed up some apps and APKs.
Rebooted device several times and works great.
Android version: 4.3
Baseband: P605XXUBMJ4
Build number: JSS15J.P605XXUBMJ9
Steps to produce problem:
1) Download Xposed Installer from Xposed website, I assume it is the latest.
(de.robv.android.xposed.installer_v32_de4f0d.apk)
2) Installed the said Xposed Installer APK.
3) Tap on Install/Update, prompted that device will restart in a few seconds.
4) Device rebooted.
5) Reached lockscreen:
- Entered gesture 3 x 3 security swipe prompt.
- Touchwiz started to force close.
- Then everything else starts to force close as well.
Steps to recover from problem.
1) Hold capacitive menu button and went to S Finder screen.
2) Search for something random.
- Internet is not working even though I have 3G/Mobile internet enabled.
3) Continue search using Google, select a browser. (I used Firefox)
4) Navigate to Xposed installer APK using Firefox (file:///) which resides in my external SD card.
5) Click on the APK and install as usual, then open the installed APK.
6) Uninstall Xposed framework.
7) Reboot.
8) Everything works fine again.
Dared myself to try Xposed again. Got into the same problem. Trying to reinstall Xposed Installer but it is taking so much time. Still installing as
we speak.
Now I am trying to find out where does Xposed APK reside in, so I can launch the app manually.
UPDATE: Managed to uninstall Xposed framework after a LONNNNGGGGG wait. I am not daring enough to try it again. =_=!
Questions:
1) How to run Xposed without everything force closing?
2) What can I do to fix this?
3) Where does Xposed APK reside in the system folder?
Hi
Suggest you unroot your device and reinstall stock firmware via odin. Clear cache/dalvik and factory reset device. Then root again with towel root, install latest chainfire su to disable knox and install Xposed. This should clear your issues. I don't have similar problems on my p605 with Xposed.
Sent from my SM-N9005 using xda app-developers app
tonycfc said:
Problem with Xposed Installer.
Click to expand...
Click to collapse
Sure it is not the rooting method? No problems here with Xposed Installer...Rooted with chainfire's auto root (I don't give a sh**t about crappy Knox), 4.4.2, MagazineUX Rom
sphuyal said:
Sure it is not the rooting method? No problems here with Xposed Installer...Rooted with chainfire's auto root (I don't give a sh**t about crappy Knox), 4.4.2, MagazineUX Rom
Click to expand...
Click to collapse
No, it's not the rooting method. I used towelroot for my P605 + Xposed. I have no problem.
Sent from my SM-N9005 using xda app-developers app
Hi all. I did not manage to solve this problem but I took the plunge and flashed P605XXUCNE2 4.4.2 and rooted it with towel root, installed SuperSU and everything went well. No wipe as well.
I also flashed TWRP and did a nandroid backup. I don't really care about Knox anymore. ^_^
shayind4 said:
Hi
Suggest you unroot your device and reinstall stock firmware via odin. Clear cache/dalvik and factory reset device. Then root again with towel root, install latest chainfire su to disable knox and install Xposed. This should clear your issues. I don't have similar problems on my p605 with Xposed.
Sent from my SM-N9005 using xda app-developers app
Click to expand...
Click to collapse
This helped now phone Is fixed on stock firmware
Related
Hi All.
Apologies if this is in the wrong forum, I am unable to post to the development board due to lack of posts.
I was wondering if anyone has installed the Xposed framework on the International HTC One M8 yet? I know this requires root, and a method for obtaining root has been laid out on this forum
http://forum.xda-developers.com/showthread.php?t=2694564
but some of the posts state that installation of Xposed when using this root method has not been possible due to the /system folder still being write protected.
It seems others have had some success in installing the Xposed framework when using this method (WeakSauce)
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=139157680
but this method does not work on international versions, only Verizon.
Basically I want to install Xposed in as simple a way as possible, with the end goal being to install the Immerse Me module so as all apps will run in immersive mode.
Any help/info would be very much appreciated.
Cheers.
I have it installed and working. You have to install it as a zip thru twrp.
In for an answer to this. I need Xposed before I can root with Weaksauce.
pettsium said:
Hi All.
Apologies if this is in the wrong forum, I am unable to post to the development board due to lack of posts.
I was wondering if anyone has installed the Xposed framework on the International HTC One M8 yet? I know this requires root, and a method for obtaining root has been laid out on this forum
http://forum.xda-developers.com/showthread.php?t=2694564
but some of the posts state that installation of Xposed when using this root method has not been possible due to the /system folder still being write protected.
It seems others have had some success in installing the Xposed framework when using this method (WeakSauce)
http://forum.xda-developers.com/sho...mctr=(not provided)&__utmv=-&__utmk=139157680
but this method does not work on international versions, only Verizon.
Basically I want to install Xposed in as simple a way as possible, with the end goal being to install the Immerse Me module so as all apps will run in immersive mode.
Any help/info would be very much appreciated.
Cheers.
Click to expand...
Click to collapse
Just installed immerse me too and it works well.
skoobee said:
I have it installed and working. You have to install it as a zip thru twrp.
Click to expand...
Click to collapse
Sorry, what do you need to install as a zip through twrp?
My understanding of the method is
1) flash twrp
2) install the root.zip through twrp.
3) install SuperSu from play store
4) install Xposed installer from play store
5) install framework through xposed app
Did you get the xposed framework installed a different way?
I'm on ATT but I had to flash the xposed installer in recovery. It wouldn't install any other way
Sent from my HTC One_M8 using Tapatalk
pettsium said:
Sorry, what do you need to install as a zip through twrp?
My understanding of the method is
1) flash twrp
2) install the root.zip through twrp.
3) install SuperSu from play store
4) install Xposed installer from play store
5) install framework through xposed app
Did you get the xposed framework installed a different way?
Click to expand...
Click to collapse
If u go into the xposed installer》framework》installation mode and choose recovery (write zip to sd card, flash manually). Then go into recovery (twrp) and install the file u just created it works fine.
skoobee said:
If u go into the xposed installer》framework》installation mode and choose recovery (write zip to sd card, flash manually). Then go into recovery (twrp) and install the file u just created it works fine.
Click to expand...
Click to collapse
Great. Worked perfectly. You were right, manual install was what was needed.
Are you finding the immersive mode stable? For me the black bar sometimes "sticks" after making it appear
pettsium said:
Great. Worked perfectly. You were right, manual install was what was needed.
Are you finding the immersive mode stable? For me the black bar sometimes "sticks" after making it appear
Click to expand...
Click to collapse
I switched immersive mode off as it made texting difficult - the bottom row would be cut off so couldnt see what I was typing.
I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
cv91913 said:
I used the CF-Auto-Root package, which contained Odin3-v3.07.exe and CF-Auto-Root-lt01wifi-lt01wifixx-smt310.tar.md5, to root my Samsung Galaxy Tab 3 8.0 (SM T310) running Android 4.4.2 stock. This root installed some version of SuperSu and no custom recovery. I was able to run SuperSU and installed a couple of root apps like Greenify and Titanium BU. No problem. Then, after I purchased the Pro version and rebooted, SuperSU started requesting a binary update. The Normal update failed. No custom recovery was included with the root but I tried that option but it also failed with a signature verification error. After the signature error SuperSU did run and I was able to go into settings and did the uninstall/reinstall. Uninstalled the pro key and then reinstalled SuperSU from Play Store. This time when it asked to update binary, I chose Normal and it succeeded! I did not reinstall Pro. That lasted until I did the first power off. When it came back up, it asked to update binary. It still seems to function, as I did install another root app and it granted access. Any ideas where I go from here?
Click to expand...
Click to collapse
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
gr8nole said:
Use Odin to install a custom recovery; then flash the latest SuperSu zip in recovery.
Sent from my SM-T310 using Tapatalk
Click to expand...
Click to collapse
Will that work if the tablet is already rooted and SuperSU is already installed? SuperSU is working as long as I don't run the UI. Sorry, I am new to this rooting stuff. Thanks for the response.
I have P5210 Tab3 10 Wifi
We used chainfire=> http://download.chainfire.eu/452/SuperSU/UPDATE-SuperSU-v2.02.zip
And in our model yes we even write over old not working su. KK 4.4.2 does not like to be rooted and kills it. As gr8nole said. we too are force to install UPDATE-SuperSU-v2.02.zip on recovery. This one does survive KK attacks. Clearly this one, you installed from Recovery. But you can go to
http://forum.xda-developers.com/showthread.php?t=1538053
For other installation methods
I am losing root when I restart my phone sgh-t999l luvubmk4 4.3 superSU pro app and cwm touch recovery I have root SU binary installed in the xbin folder use titanium backup fine but if I turn off or restart my phone I lose root I have been restarting phone to recovery and using the fix root on restart option in CWM to get back root but sometimes I have to restart and try it again 5-6 times anyone know why im losing root
laniclamoore said:
I am losing root when I restart my phone sgh-t999l luvubmk4 4.3 superSU pro app and cwm touch recovery I have root SU binary installed in the xbin folder use titanium backup fine but if I turn off or restart my phone I lose root I have been restarting phone to recovery and using the fix root on restart option in CWM to get back root but sometimes I
have to restart and try it again 5-6 times anyone know why im losing root
Click to expand...
Click to collapse
Please reply if need more info let me know what ya need im realy hoping for some suggestions
I had this happened to me a while ago it actually ended up either being an app or an xposed module. Do you use xposed?
I had this problem with Cyanogen mod 11 and running exposed framework.
I switched ROMs and now I have no problems.
losing root
I don't use xposed im just using the root66 stock 4.3 rom I have tried different super user apps no help. Im currently using superSU 2.0 (not the one from market) so far its no longer losing root. I uninstalled the superSU app from the market and used the one I found on a different thread in the Q&A forum. thanks for asking about it I will post if it stops working or anything else goes skiddy wumpus.
Thanks guys.
I remember now. It was the Xposed module BootManager that was causing the issue for me. If you don't use that specific module then it might be a module or app that functions similarly to control startup permissions of apps at boot time.
Philosuffer said:
I remember now. It was the Xposed module BootManager that was causing the issue for me. If you don't use that specific module then it might be a module or app that functions similarly to control startup permissions of apps at boot time.
Click to expand...
Click to collapse
Yes I agree I set the SU request during boot to grant superSU root access so the superSU app would protect SU binary from being deleted during boot.
well crap
Crap im once again losing root on restart/boot I've tried using different root methods to no avail. Could it be the SE for Android still says enforcing maybe my bootloader is locked but I don't know how to check if it is. I have not tried custom roms because I don't know which ones work for the t999l lte.
All of the roms are safe to try. They work fine for most people, but if you have problems you can always flash back to what you have now. (Don't forget to make a nandroid backup).
And the bootloader is not locked btw.
Might also help to flash your stock firmware Via Odin. Have you tried the root66 firmware?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
su binary present in xbin but on reboot not executing
Ok im still having the same problem.
I have the su binary installed in the /system/xbin folder but when rebooting from recovery su binary is not detected by superSU but its still in the xbin folder.
This jpeg is when I have full root access is the setuid not present a problem? See errors on second jpeg.
I don't know what info is needed to find problem will someone tell me what info I should gather to help solve problem with su binary (like logcat/busybox version,) thanks
Did you try v1.94 or 2.00? I guess 2.13 didn't solve the problem.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
thread closed use thread "keep losing root access"
There are 2 threads on the same issue. Please use Keep losing root access.
I just flashed the latest twrp and the SuperSU 5.0 image coming from stock 5.0.2 last night and was having trouble with granting permissions, it would just get stuck and wouldn't let me choose anything. I went ahead and backed up in twrp and flashed a custom rom and all went well. Although I still have the sticking on the permission windows and the SuperSU app isn't showing up in the app tray and won't allow me to open it from the play store. I was recommended to flash the SuperSU 2.45 update which I did successfully in twrp and I'm still getting stuck on the permission window, any help or suggestions I would be very much appreciate. Thanks!
Edit: fixed it, just needed to uninstall and reinstall SuperSU! Thanks y'all
whmgreen said:
I just flashed the latest twrp and the SuperSU 5.0 image coming from stock 5.0.2 last night and was having trouble with granting permissions, it would just get stuck and wouldn't let me choose anything. I went ahead and backed up in twrp and flashed a custom rom and all went well. Although I still have the sticking on the permission windows and the SuperSU app isn't showing up in the app tray and won't allow me to open it from the play store. I was recommended to flash the SuperSU 2.45 update which I did successfully in twrp and I'm still getting stuck on the permission window, any help or suggestions I would be very much appreciate. Thanks!
Click to expand...
Click to collapse
I am using stock L 5.0.2, and used Chainfire Auto Root to flash it on 5.0/.1/.2 without issue. I am running SuperSU 2.40 currently, and it does not appear to have an update pending on the Play store.
Did you try using 2.45 on a clean install that had not previously used 5.0? Wondering if something is getting gummed up from that, and sticking around on the older version.
Maybe try a fresh clean install on stock or whatever ROM you want and try 2.40/2.45 first before 5.0.
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Erosa13 said:
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Click to expand...
Click to collapse
You ALREADY HAVE root with CM-SU. To enable it, just go to developer option and give root permissions to app. Some SuperSU's versions are incompatible afaik. CM-SU preinstalled is just fine.
Erosa13 said:
Hey all. I just flash that ROM. Works really nice. But I can't find SuperSu installed. Also apps which needs root permission didn't worked. I just go do download SuperSu from market and the program shows me an error told me to reboot and try again. Can you please help me? Thanks in advance.
Click to expand...
Click to collapse
SuperSU is an issue for itself. Installing 2.74 using TWRP on my G3 lead to boot problems because of a boot image patch that SuperSU installs. If I restore boot partition before rebooting, SuperSU doesn't install. Using Play Store version fails to install su binaries.
Conclusion: use CM own root. It works nicely, just lost FolderMount but, well, I prefer that instead of losing phone.
Mnldr/D855/16G/CM13
Meneldur said:
SuperSU is an issue for itself. Installing 2.74 using TWRP on my G3 lead to boot problems because of a boot image patch that SuperSU installs. If I restore boot partition before rebooting, SuperSU doesn't install. Using Play Store version fails to install su binaries.
Conclusion: use CM own root. It works nicely, just lost FolderMount but, well, I prefer that instead of losing phone.
Mnldr/D855/16G/CM13
Click to expand...
Click to collapse
Have you try this method http://forum.xda-developers.com/lg-g2/general/bump-supersu-t3273251
CustomPatcherScript_Bump.zip + UPDATE-SuperSU-v2.65-20151226141550.zip
But it's also can cause reboot loop
Do backup before doing flash that script
That worked fine with my D855 32Gb + CM13