Database Develop

[Solved] Xposed installed but not enabled, 5.0.1 ROM

Hello everyone,
I had Xposed Framework installed and working on my 5.0.1 ROM, everything was working perfeclty, but today, I noticed that none of my modules were working.
After a short search I figured out that Xposed wasn't active anymore despite beeing installed.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I tried to reinstall it by flashing the zip file via the recovery, but no success so far, the framework is still inactive.
Unfortunately, the xposed log is empty.
Any advice on how to get everything working again ?
Thank you in advance.
Regards,
Azsde.

bump, i have the same problem(

Have you tried using something like http://www.xda-developers.com/easily-change-your-android-selinux-mode/
Also verify that the Xposed app has root access.

uodii said:
Have you tried using something like http://www.xda-developers.com/easily-change-your-android-selinux-mode/
Also verify that the Xposed app has root access.
Click to expand...
Click to collapse
I have changed from permissive to enforcive, I'm not sure which one it was set to when everything was working, but switching worked perfectly for me !
Thank you very much :good:

I need to update my Xposed Install - need a little help

Hey peps, I'm on a Nexus 5 running Android OS 4.4.4 (Kitkat, bought from the Google Play Store) and today I get this error from the module called "AndroPlusMod" (see picture). It was working fine yesterday and the past few months.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
What version of the Xposed Installer do I need for KitKat and to make this module work again and where can I download it from?
This is the current version that I have installed...
Thanks in Advance peps!

Screen Shots?
Hummm? The pictures didn't link right for some reason, here they are as attachments.

Screen Shots... not working, I tested these and they seem to work
Ok... Let's see if this works... Grrrr
https://images2.imgbox.com/d7/5c/BNJSsmoz_o.jpg
https://images2.imgbox.com/80/28/29gy2yzi_o.png

No one can help me?
I have this apk "XposedInstaller_by_dvdandroid_31_10_17"... I guess I'l just have to try this version...

Zander_Sig said:
Ok... Let's see if this works... Grrrr
Click to expand...
Click to collapse
Ah, do you have other methods for it ?

Well I installed the "XposedInstaller_by_dvdandroid_31_10_17.apk" and I'm still getting the error for the module called "AndroPlusMod"... It's saying that "This Model requires a newer Xposed version (60) and thus can not be activated"...
Ughhh

Glase and Magisk

I want to use TAP & PAY with Glase. But every time it comes, no use because Root and customROM. I have one plus one with lineage-14.1-20180503 and magisk v 16.0. SafetyNet-Test true/true. Did somebody know whats happend?

Have you tried adding Glase to the (active) Magisk Hide list (tick it in the MH list), then hiding Magisk Manager with the appropriate function (you have to repackage it from the settings? What it will do is it will create a new APK file with a random package name but same icon, content and friendly name, install it and uninstall itself. An issue I noticed with this is that you have to repeat the procedure after every Manager (not SU binary) update, but it's not hard. Try and let me know if it worked
Edit: also remember to erase Glase cache, full-restart the device and - if needed - wipe Glase data

Anyone had any luck with this? Completely removed Glase, then proceeded to repackage Magisk, reinstalled Glase, selected it on Magisk Hide (while rebooting at every step) but it still recognizes the root :/
PS: on Oneplus 6.

This is Stock ROM on my S8+
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my SM-G955F using Tapatalk

Magisk 19 breaks OP5T camera app

Today I got around to updating my OnePlus 5T to OxygenOS 9.0.5; I think I was a couple updates behind, so probably on 9.0.3 before. I re-rooted afterward by flashing Magisk 19.2 with TWRP, and my camera app turned into a grey square with CC on it, and wouldn't open (crashed immediately).
After wrangling with it for a while, I learned:
Reflashing Magisk 18.1 fixes the camera
I saw some people had luck changing build.prop's permissions to RW-R--R--, but this didn't help in my case
I also saw someone had luck installing the ElementalX kernel, but this also didn't help in my case
I'm pretty sure I was on Magisk 19.2 before updating OxygenOS, so this must be something new in the last couple versions
Any idea what the problem could be?

I've also got a broken camera app due to magisk. No answer as to why this happens though. I'm running magisk 19.2 in Oreo 8.1 on a Samsung Galaxy Tab A 8.0 (2017).

Problem still exists with Magisk 19.3, FWIW.

Problem still exists with Magisk 19.4 and OxygenOS 9.0.8...
Screenshot attached. Any idea what this icon is?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

[Help] SU binary detected on magisk core mode

Hello everybody,
I realized that on my phone the SU binary is not hidden from the magisk hide apps even with magisk core mode and root mode disabled
I did the test with rootbeer fresh and here is the result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have the latest version of magisk and manage, my log is nearly empty and SafetyNet is passing...
I am running a Galaxy S5 klte on official LineageOS 16 (latest version, rooted only with Magisk) and on terminal (also checked in magisk hide) when I do
Code:
which su
I have
Code:
/sbin/su
Thanks for your answers

Core Only Mode and disabling Superuser access has nothing to do with hiding Magisk... Only MagiskHide and repackaging the Manager with a random name (but you seem to have that covered).
Test the Canary debug build (possibly improved and better logs). Also take a look here for tips and tricks:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps

Thanks, for your answer, it seems to work with the canary version !! Do you know why this is the case ?

jojo58400 said:
Do you know why this is the case ?
Click to expand...
Click to collapse
Nope...