Database Develop

Xposed Framework Disabler/Enabler (incase of bootloop)

There are a lot of Modules which may cause a bootloop on Android L (especially on Android 5.1). And since Xposed does not come with a disabler zip for Android L, you cannot disable it from recovery in case of bootloop. For this reason, I created a flashable Xposed Disabler that can disable Xposed from recovery, in case of a bootloop. I also created an enabler in case if you disabled it using the disabler zip.
Any problems with the zip files, please inform me.

Well it Does disable it ( I am on 5.0 )
But ... How I can re enable it back? I tried reflashing exposed again No affect

exposed
To reenable xposed after using the zip, just delete the disable file in /data/data/de.robv.xposed.installer/config

Just use a root explorer and delete disabled from data/data/de.robv.xposed.installer/config

Is this only work for Android L? I'm still on stock jellybean. Would like to have a diabler for my version to.

Samsung roms?
AK1149 said:
There are a lot of Modules which may cause a bootloop on Android L (especially on Android 5.1). And since Xposed does not come with a disabler zip for Android L, you cannot disable it from recovery in case of bootloop. For this reason, I created a flashable Xposed Disabler that can disable Xposed from recovery, in case of a bootloop. I also created an enabler in case if you disabled it using the disabler zip.
Any problems with the zip files, please inform me.
Click to expand...
Click to collapse
Is working on Samsung ROMS like the s6 one?

Can't guarantee, but it should work.

Thank you
Such posts are supposed to be everywhere on xda about everything ..
Thank you ..
I found this post because Marcel ; M66B had posted a link for it in response to a user of Xprivacy .. this is how much important is your post .

AK1149 said:
There are a lot of Modules which may cause a bootloop on Android L (especially on Android 5.1). And since Xposed does not come with a disabler zip for Android L, you cannot disable it from recovery in case of bootloop. For this reason, I created a flashable Xposed Disabler that can disable Xposed from recovery, in case of a bootloop. I also created an enabler in case if you disabled it using the disabler zip.
Any problems with the zip files, please inform me.
Click to expand...
Click to collapse
How does this work? Does it remove the Xposed stuff or temporarily block access to it unless you use the re-enabler?

It creates a empty "disabled" file in "\data\data\de.robv.android.xposed.installer\conf" which disables the Xposed module until the file is deleted either by the flashable zip or manually deleting the file.

Thanks! Works like a charm on 5.1!
Saved a couple of hours of flashing and restoring data!

Is there a way to disable it using root explorer?

AzrulHisyam said:
Is there a way to disable it using root explorer?
Click to expand...
Click to collapse
as long as you can create a file at correct path and name it correctly, it should work.

Hi there!
Does these work on last Xposed alpha4 by rovo89?
I have a Samsung TouchWiz deodexed rom and I'm using alpha 4 with arter97's Krait V5 and everything is fine, but as rovo89's uninstallers does not work on this combination, the only easy to get out a bootloop is to use a disabler/enabler solution.
Can you confirm that these also work on last rovo89's release?
Tnx.
Sent from my Samsung Galaxy S5 SM-G906K using TapaTalk

How do you flash this? PLEASE HELP!!

Handy!
Saves time of going into recovery and do it manually.

Bliste said:
How do you flash this? PLEASE HELP!!
Click to expand...
Click to collapse
Flash it using CWM recovery

flashed disable zip and no more bootloop.
haven't tried the enable one yet, but should be good, thanks

Hi,
I use Xposed V85 for MIUI (on Redmi Note 2) bad this solution doesn't work for me. I need for temporary disabled xposed because Horizon Go (UPC) have problem with framework. Can you have any solution without permanetly uninstall xposed ?

Is there a way to use it without custom recovery? I'm stuck in bootloop with stock recovery, please help

[GUIDE] Xposed on P9 Lite

[WILL NOT WORK ON ANDROID N]
There is no functional Xposed for Nougat (yet)
Hey everyone!
Since there is no dedicated thread for how to install Xposed for the P9 Lite yet, I thought I quickly provide the method how I made it work for future users.
What you need?
- Unlocked BL
- TWRP Installer
- Root
So you want to get the version of Xposed provided by Wanam. Version 86 for arm64 is what you are looking for! You can get it here.
UPDATE: I experienced extreme battery drain and crashing settings with version 86. I am now using version 84 and all is fine again.
Don't worry that it says Samsung devices in the thread.
Download the zip package that you need and place it somewhere. Then download the Xposed installer apk.
For example here in the first post attached.
Install the apk.
Now it's time to fire up TWRP and make a backup!
Then flash the zip you have downloaded before. If you downloaded the right version, it should flash without errors.
Now reboot. BE PATIENT. It can take several minutes for the first boot.
That's it. You should now be able to use Xposed modules like enabling background play on official YoutTube app :victory:
Sidenote: some people mentioned that you may need to switch your SELinux mode to permissive. Since I had it on permissive in the first place I don't know if it's really the case.
PS: leave a like for the guys providing these awesome Xposed frameworks if you download them :good:

Hey man, some days ago i tried to install this on my p9 lite. I got bootloop caused by "not enough space" (with more than 6GB of free space) error during the installation of the framework. Any suggetion? Maybe we need a new partition system?

Zeph1990 said:
Hey man, some days ago i tried to install this on my p9 lite. I got bootloop caused by "not enough space" (with more than 6GB of free space) error during the installation of the framework. Any suggetion? Maybe we need a new partition system?
Click to expand...
Click to collapse
Hmm I did not encounter something like this. However, I did receive some errors earlier with backups in TWRP. Maybe there is a bug in this TWRP version for this device.
Afaik it is ported from the Chinese version of the P9 Lite so I don't really know who is working on this.
But it is strange. Have you tried to flash it a second time? Maybe just a weird bug?
Since I was able to install it just fine...

Uhm, i'm bit afraid cause i have done a full reset after that problem. I think i will wait before doing it again

just installed ,xposed-v85.1-sdk23-arm64-custom ,on L21 and works fine for now
thanks

what modules are you running?

l31
guys does this package works on l31 phones because I got already a bootloop with the l21 guide mentioned above..ty

Yes, i've done it like mentioned above and its working perfectly on my l31. As you see on my Screenshots. Authentication Info with the xposed Flat Style bar indicators and coloured Bars. But after flashing the Framework the Bootlogo showed up for around for 15minutes before booting up. I thought I got stuck in Boot. An started thinking of reflash my Backup. But it booted and its working.

Also getting bootloop on my L31 - complains about not enough space on device when trying to flash.

Hello all just have a quick question which better to use the xposed-v86.0-sdk23-arm64-custom-build-by-wanam-20160709 or xposed-v86-sdk23-arm64 version or does it matter? Thanks..

lilbrat said:
Hello all just have a quick question which better to use the xposed-v86.0-sdk23-arm64-custom-build-by-wanam-20160709 or xposed-v86-sdk23-arm64 version or does it matter? Thanks..
Click to expand...
Click to collapse
You need the version by Wanam.

Psierra117 said:
Yes, i've done it like mentioned above and its working perfectly on my l31. As you see on my Screenshots. Authentication Info with the xposed Flat Style bar indicators and coloured Bars. But after flashing the Framework the Bootlogo showed up for around for 15minutes before booting up. I thought I got stuck in Boot. An started thinking of reflash my Backup. But it booted and its working.
Click to expand...
Click to collapse
I can't get Flat Style Colored Bar on the navigation bar no matter what I do. Does it work for you?

Memovic said:
I can't get Flat Style Colored Bar on the navigation bar no matter what I do. Does it work for you?
Click to expand...
Click to collapse
I'm using Xstana for status bar and navigation buttons and working fine for me

As far as I know the official and latest version of Xposed works in Huawei, You just have to disable themes in build.prop
Check this out:
http://forum.xda-developers.com/showpost.php?p=66380010&postcount=30

The flatstyle colored Bars is working without problems. Version 2.1.0 its changing Statusbar color like orange on xda and red on YouTube. An the navbar changes between white Grey and black or transparent depending on Main brightness of the whole window. I've had installed xposed-v86.0-sdk23-arm64-custom-build-by-wanam-20160709 like mentioned above. And I first thought I got stuck in Boot loop But it run for around 15 minutes before the system booted up. Let it settle and before booting clean Cache and Dalvik.

Schlengge said:
Hey everyone!
Since there is no dedicated thread for how to install Xposed for the P9 Lite yet, I thought I quickly provide the method how I made it work for future users.
What you need?
- Unlocked BL
- TWRP Installer
- Root
So you want to get the version of Xposed provided by Wanam. Version 86 for arm64 is what you are looking for! You can get it here.
Don't worry that it says Samsung devices in the thread.
Download the zip package that you need and place it somewhere. Then download the Xposed installer apk.
For example here in the first post attached.
Install the apk.
Now it's time to fire up TWRP and make a backup!
Then flash the zip you have downloaded before. If you downloaded the right version, it should flash without errors.
Now reboot. BE PATIENT. It can take several minutes for the first boot.
That's it. You should now be able to use Xposed modules like enabling background play on official YoutTube app :victory:
Sidenote: some people mentioned that you may need to switch your SELinux mode to permissive. Since I had it on permissive in the first place I don't know if it's really the case.
PS: leave a like for the guys providing these awesome Xposed frameworks if you download them :good:
Click to expand...
Click to collapse
Thank you! For me works fine. Some modules for Xposed, please!

adifa said:
Thank you! For me works fine. Some modules for Xposed, please!
Click to expand...
Click to collapse
I don't use a lot of modules... What I do use and highly appreciate is Xprivacy, Greenify and DoubeTapToSleep.

Schlengge said:
I don't use a lot of modules... What I do use and highly appreciate is Xprivacy, Greenify and DoubeTapToSleep.
Click to expand...
Click to collapse
Thank you very much!
Trimis de pe al meu HUAWEI VNS-L21 folosind Tapatalk

I've installed the official version and it's working like a charm.

Hi, my phone version is VNS-L31/ B105 (Wind branded).
I can confirm everithing is working just fine after installing official xposed apk from the official thread
(http://forum.xda-developers.com/showthread.php?t=3034811) and flashing the last framework "xposed-v86-sdk23-arm64.zip" from the link in the same thread.
No errors reported during flashing, albeit i just have to wait 5-10 minutes during rebooting before the UI to appear.
I'll give you some tips on some issues i dealt with and some modules i've installed:
1) "DoubleTapToSleep - working
2)GravityBox - not everything is working, i've just set the hardware keys actions to run some applications, but the recents key isn't working as default setting. Power tweaks section isn't working too. QuickSettings aren't working even disabling the two strings in build.prop file.
3)If you want an advanced reboot menu then try the module "NeoPowerMenu". in order to make it working you have to go in advanced settings and enable the function "ExperimentalPhoneWindowManager hook" then reboot and it should be working.
4) XPrivacy - working
5) i experienced problems with some apps that need to stay in background like ZDcalendar for if I close the app from the Recent apps window, the alarms or notifications scheduled are not notified. I suppose it's due to battery saving settings. I solved going to the app section--->then the app I want to manage--->battery--->enabling "keep running after screen off".
i had the same problem with the app Twilight, in fact when i closed the recent apps from the recents window, the app just shut down.
enabling the function mentioned above will prevent the app from closing unless you kill it manually.
Hope this will help, bye!

YouTube background playback not working.

I downloaded a few xposed modules, of which, YouTube background playback is not working. Any help is really appreciated.

AngelinaWhite said:
You need to restart you phone。
Click to expand...
Click to collapse
I did restart my phone. It's not working.

you need to have the specific version of Youtube that works for your xposed module.

You have to activate the beta updates on this module and download the latest version. Worked for me.

CANT reboot My OnePlus 3 after installing any Xposed module
My OnePlus 3 doesnt reboot after installing any Xposed module. The framework arm64 v86 was zip installed properly but my Modules dont work. they get downloaded but after that during reboot my onplus gets stuck at reboot loading screen The tow dots
any modules be it YouTube Background Playback or GM or YouTube AdAway
PLZ HELP !
i have tried uninstalling reinstalling
reflashing and then re rooting and then reinstallation has also been tried
aint working
:crying:
plz help.

soulcandy17 said:
My OnePlus 3 doesnt reboot after installing any Xposed module. The framework arm64 v86 was zip installed properly but my Modules dont work. they get downloaded but after that during reboot my onplus gets stuck at reboot loading screen The tow dots
any modules be it YouTube Background Playback or GM or YouTube AdAway
PLZ HELP !
i have tried uninstalling reinstalling
reflashing and then re rooting and then reinstallation has also been tried
aint working
:crying:
plz help.
Click to expand...
Click to collapse
Which OS are you on?
Also, did you enable root access?

did you enable the module in xposed before the reboot? Try switch to magisk if you're using cf su. mine works flawlessly on oos 3.5.4 w/magisk

sriharshasv said:
I downloaded a few xposed modules, of which, YouTube background playback is not working. Any help is really appreciated.
Click to expand...
Click to collapse
Use Firefox.
Sent from my BTV-W09 using Tapatalk

sriharshasv said:
Which OS are you on?
Also, did you enable root access?
Click to expand...
Click to collapse
stock OS
yes Root access is enalbed obviously
---------- Post added at 06:05 AM ---------- Previous post was at 06:03 AM ----------
g96818 said:
did you enable the module in xposed before the reboot? Try switch to magisk if you're using cf su. mine works flawlessly on oos 3.5.4 w/magisk
Click to expand...
Click to collapse
magisk?
so this Magisk has systemless root right?
should i really try it dlting SU?
Is it worth
coz i dont think its SU problem !
tell me what you think about this.

soulcandy17 said:
stock OS
yes Root access is enalbed obviously
---------- Post added at 06:05 AM ---------- Previous post was at 06:03 AM ----------
magisk?
so this Magisk has systemless root right?
should i really try it dlting SU?
Is it worth
coz i dont think its SU problem !
tell me what you think about this.
Click to expand...
Click to collapse
I like magisk with phh su better than supersu. I can play pogo and use android pay with root, as long as I disable xposed and restart before using it. Aside from that, I see no significant difference, except the extra 1 time step to flash dm-verity bypass.
If you think it's a SU issue then maybe somewhere along the way you messed up the binaries. You could try flashing the latest supersu and if that doesn't work then go into the settings tab in supersu and select full unroot, then reflash supersu or magisk in twrp. don't know if you need to flash dm-verity bypass or not if you've already installed supersu before. I just flashed magisk after unboxing. You might want to ask or search here https://forum.xda-developers.com/oneplus-3t/development/recovery-twrp-oneplus-3t-t3507308

looks like with the new magisk update you can just flash magisk and it will remove your old supersu and root with phh su.
https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

For me working fine, but when I listen in background for 20min, I can't back to normal play. There is only sound, no video - black. I must restert phone...
To admin:
Please move the post to the main thread (https://forum.xda-developers.com/xposed/modules/xposed-youtube-background-playback-t3023284/page2) or delete.

[ROOT] [Magisk] [Galaxy S6] - Magisk-root uninstalls automatically?

Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
(I don't want to install a Custom ROM!)
Thank you
Larry

larrythil said:
Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
Thank you
Larry
Click to expand...
Click to collapse
I had the same problem with my Nexus 6P.
I was on stock ROM and stock kernel and it happened twice.
Now I'm on stock ROM and EX Kernel and problems seemed go away.
Inviato dal mio Nexus 6P utilizzando Tapatalk

CyberZeus1977 said:
I had the same problem with my Nexus 6P.
I was on stock ROM and stock kernel and it happened twice.
Now I'm on stock ROM and EX Kernel and problems seemed go away.
Inviato dal mio Nexus 6P utilizzando Tapatalk
Click to expand...
Click to collapse
Tell me somthing about "stock kernel" and "EX Kernel" what is that and how can i install that? or change that?

I have the same problem, galaxy S6.

I noticed losing root randomly and fixed it by going install patch boot img then you flash the boot img in recovery. So far it's been a day no root loss
Lineage 14.1 for lg stylo 2 plus

Hi ! I have sale problem with my S8+ with custom rom and Custom kernel

Hello.
I am having the same issue with my S6. I have tried all of the advice from previous threads with regard to different versions of Magisk.. (Removing Busy Box / Not using the Magisk Hide feature... etc etc..). I have also been through as many extra options as I can think of, getting all of the "Update" patches from the other developers who have helped with the Magisk project.
Each time, I have run through all of the aditional scripts to make sure SU and Magisk have been completely removed prior, and then used Odin to do a recovery back to my Original ROM (a complete system backup image I previously saved).
The other interesting observation i have at the moment is that i can not get to the Log cat files to post them anywhere. I can see where they are supposed to be but the directory is empty "no files". I have even been as far as downloading one of the many "Mobile Forensic" software kits to try and see if there is anything wrong with my phone.
There is only one observation to report. It seems that after installing Magisk (even if you just install the main ROM and not the manager). Google play starts to download straight away... I am not sure what it is downloading as it doesn't ever seem to complete and all of my versions of the apps are up to date.
I hope I will be able to get some more usefull information for you soon (LogCat etc etc.). If any one has an answer or suggested options it would be good. I am particularly interested in getting the Busy Box feature to work with Root as I am working on an app for my job that needs both options (I work offshore and am trying to adapt a piece of Seismic QC software (unix based) to run on phones / tab's - Android).
I will sign up properly and start to follow the threads more closely.
Cheers... Andy
-Samsung S6 - Full Magisk Module (with recommended zeroflte TWRP).

AndyQVT said:
Hello.
I am having the same issue with my S6. I have tried all of the advice from previous threads with regard to different versions of Magisk.. (Removing Busy Box / Not using the Magisk Hide feature... etc etc..). I have also been through as many extra options as I can think of, getting all of the "Update" patches from the other developers who have helped with the Magisk project.
Each time, I have run through all of the aditional scripts to make sure SU and Magisk have been completely removed prior, and then used Odin to do a recovery back to my Original ROM (a complete system backup image I previously saved).
The other interesting observation i have at the moment is that i can not get to the Log cat files to post them anywhere. I can see where they are supposed to be but the directory is empty "no files". I have even been as far as downloading one of the many "Mobile Forensic" software kits to try and see if there is anything wrong with my phone.
There is only one observation to report. It seems that after installing Magisk (even if you just install the main ROM and not the manager). Google play starts to download straight away... I am not sure what it is downloading as it doesn't ever seem to complete and all of my versions of the apps are up to date.
Click to expand...
Click to collapse
So long story short, there's no definitive solution to the problem. Im using a g920p with a custom kernel built by a genius dev, and i still lose root once a day.
Basically what it comes down to is modules. If you have zero modules, you'll have better luck... But that's not the point of magisk, so you need to be picky with modules. Use osmosis's busybox from the magisk repo, but other than that, install modules 1 at a time and see if it affects root.
Another tip: uninstall all updates of the "device maintenance" app, and find it in Google play and turn off automatic updates. Then go to device maintenance > battery > unmonitored apps and magisk manager to the list of unmonitored apps... Then go back the battery screen, battery usage > 3 dots in top right > optimize battery usage, and make sure magisk manager is not optimized... That should help some. (Note: some models don't have device maintenance, but you'll still have the "optimize battery usage" option some where.)
The Google play thing you're seeing is likely "instant apps" updating. I believe that should be unrelated to all this, but some aspects of instant apps is a mystery.
As for the logcat thing, i believe you're getting logcat confused with the magisk_debug.log located in /data ? If that's the case, you need to be using the beta version of magisk. Go to magisk and set the update channel to beta, you'll get a notification to update magisk, download it and flash. (Or if the recommended native install is an option, use that)
I recommend just using he normal 14.3 magisk... You'll have issues, but they will be predictable and easy to solve with a simple reboot. There's really no final solution for us unfortunately, just making it as stable as possible.
Lastly, it helps if once every once in a while you fully uninstall magisk with the uninstall.zip, reboot (you might not get a bootloop, in which case hold volume up +power+ home to boot into recovery), reflash magisk 14.3, and then wipe cache and art/davik.
---------- Post added at 04:12 PM ---------- Previous post was at 04:12 PM ----------
larrythil said:
Hello,
I'm using a Samsung Galaxy S6(64GB, Exynos) with Magisk-root. But I have the issue that it automatically uninstalls. And suddenly it’s unroot. Then I have to reinstall the Magisk-vXX.X.zip with TWRP (X.XX is the version, for example: 14.0 or 13.3). But after some hours it is uninstalled again and I lost the root access.
Then I have to repeat this...
Does someone have the same problem? Or does someone know how to fix this?
I don't want to reinstall the Magisk-package everytime i need root-access.. And I don't want to switch to another root because I like the Magisk-hide-function.
Or are there other roots with hide function?
(I don't want to install a Custom ROM!)
Thank you
Larry
Click to expand...
Click to collapse
See above

Thanks to all for the help
Nye-uhls said:
So long story short, there's no definitive solution to the problem. Im using a g920p with a custom kernel built by a genius dev, and i still lose root once a day.
Basically what it comes down to is modules. If you have zero modules, you'll have better luck... But that's not the point of magisk, so you need to be picky with modules. Use osmosis's busybox from the magisk repo, but other than that, install modules 1 at a time and see if it affects root.
Another tip: uninstall all updates of the "device maintenance" app, and find it in Google play and turn off automatic updates. Then go to device maintenance > battery > unmonitored apps and magisk manager to the list of unmonitored apps... Then go back the battery screen, battery usage > 3 dots in top right > optimize battery usage, and make sure magisk manager is not optimized... That should help some. (Note: some models don't have device maintenance, but you'll still have the "optimize battery usage" option some where.)
The Google play thing you're seeing is likely "instant apps" updating. I believe that should be unrelated to all this, but some aspects of instant apps is a mystery.
As for the logcat thing, i believe you're getting logcat confused with the magisk_debug.log located in /data ? If that's the case, you need to be using the beta version of magisk. Go to magisk and set the update channel to beta, you'll get a notification to update magisk, download it and flash. (Or if the recommended native install is an option, use that)
I recommend just using he normal 14.3 magisk... You'll have issues, but they will be predictable and easy to solve with a simple reboot. There's really no final solution for us unfortunately, just making it as stable as possible.
Lastly, it helps if once every once in a while you fully uninstall magisk with the uninstall.zip, reboot (you might not get a bootloop, in which case hold volume up +power+ home to boot into recovery), reflash magisk 14.3, and then wipe cache and art/davik.
---------- Post added at 04:12 PM ---------- Previous post was at 04:12 PM ----------
See above
Click to expand...
Click to collapse
Hello again.
So in response.
I followed the advice given... (just as a note previously the root issue would happen within an hour of restarting the device). I have been to the beta thread and read through all advice. Before jumping to the Magisk 14.3, I started with Magisk 14.2, there was a post recommending this as a critical update to Magisk 14.0.
I had no issues with this install (I had once again used my backup to revert the phone back to all original).
I then added any of the modules i wanted one at a time waiting over an hour before looking at adding any additional modules.
So far, I have not lost root and the phone is working as expected (alot better infact). I have all the Busybox modules +add-on's running, still no issues.
The upgrade to v14.2 seems to have fixed all for my uses.
Thanks to all for help and advice.
Andy

AndyQVT said:
Hello again.
So in response.
I followed the advice given... (just as a note previously the root issue would happen within an hour of restarting the device). I have been to the beta thread and read through all advice. Before jumping to the Magisk 14.3, I started with Magisk 14.2, there was a post recommending this as a critical update to Magisk 14.0.
I had no issues with this install (I had once again used my backup to revert the phone back to all original).
I then added any of the modules i wanted one at a time waiting over an hour before looking at adding any additional modules.
So far, I have not lost root and the phone is working as expected (alot better infact). I have all the Busybox modules +add-on's running, still no issues.
The upgrade to v14.2 seems to have fixed all for my uses.
Thanks to all for help and advice.
Andy
Click to expand...
Click to collapse
Glad everything is good! Sometimes magisk will get messed up, so just updating or even reinstalling will fix things.
Just keep in mind, its very likely you'll have problems again down the road... Samsung phones do a lot of weird stuff under the hood, and eventually symlinks will get broken, files deleted etc... So when that does happen, the best you can do is uninstall, reflash, update, and watch your modules.

Today updated to 15.3 and install James DSP root losed...When open magisk ask for installation reboot to recovery twrp install latest zip reboot open magisk it close it self and root lost again ?! Any advice from @topjohnwu

Do you guys mind posting a resource that shows how to root the S6 using magisk? I'm very rusty, last time I dealt with rooting was 8 years ago. Any help is appreciated. Thanks

Modules not working, can't return to old version, wipe needed on Galaxy S8 / Nougat

Hi,
I was running stock ROM with stock recovery plus Magisk v16 and MagiskManager v5.9.1 on my Galaxy S8 and Nougat. As far as I remember I did install MagiskManager using adb, pushed, patched and pulled the boot.img, flashed it using Heimdall. Both apk and patched_boot.img are available on my hard disk...
I then updated MagiskManager using the in app update. Afterwards I used the "direct install" to update Magisk. That took me to 20.4 / 8.0.2. I don't remember if it asked to install the runtime.
I installed modules busybox, sqlite3 and movecertificates, but with no effect (e.g. there is no /system/bin/sqlite3, no nc in my path, user certs remain user certs). I also can't find any indication in MagiskManager that modules are installed.
I didn't have time to figure out what's wrong and tried to revert back to my old versions.
That's what I did: Full uninstall from MagiskManager 8.0.2. Reboot without Magisk, adb push MagiskManager-v5.9.1.apk. Flash my old patched_boot with Magisk v16 using Heimdall. But unfortunately that gives me Magisk Manager stuck on the splash sceen. No applet can get root access, e.g. su on adb shell blocks (needs ctrl+c). Ok, uninstalled MM.
I installed the stock boot img in the intention to load MM 8.0.2 before I flash M 20.4. That didn't accept my pattern for the "your device is encrypted" screen. Well... I flashed M 20.4 patched boot.img again. After first try it shows an integrity issue and offers to wipe the phone.
* Anyway to go from here besides wipe?
* What residuals might be blocking when returning to the old versions?
* Why are modules not working on current version?
Thank you

urbancubb said:
* Why are modules not working on current version?
Click to expand...
Click to collapse
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
* What residuals might be blocking when returning to the old versions?
Click to expand...
Click to collapse
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
* Anyway to go from here besides wipe?
Click to expand...
Click to collapse
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.

Didgeridoohan said:
Are they current module zips, or ones that you had laying around from before updating? The modules might be using outdated installation scripts (that's my prime suspect at least).
Click to expand...
Click to collapse
I installed them from within Magisk Manager from the online repo.
I noticed that this might be the case, but as there was updates this year I think on at least two of them and none worked, I think its a general problem and not caused by the module itself. Any module I could use to test wich works for sure?
Didgeridoohan said:
Magisk v16 is soooo old. It's gonna be almost impossible to give any kind of help with that. Better to update to a current Magisk release.
Click to expand...
Click to collapse
Which didn't work... We'll see.
Didgeridoohan said:
I have no idea, you'd wan't someone who knows Samsung for that. Your device's forum might be a good place to start.
Click to expand...
Click to collapse
Good hint, I started a new thread.
Thank you!

For the modules issue, the only way to know for sure what happened is to look at the install logs and the Magisk log for the following reboot.
So if you get things up and running again, and the issue still persists, make sure to provide those.

One thing I didn't think of before: I recently tried the SafatyNet check (which failed), maybe the failed reboot was the first one after checking, I don't remember exactly.