Related
My brother has an LG G2 (verizon), I rooted his phone for him because he's not much of an android enthusiast himself. He wanted to get rid of some bloatware on stock rom so he downloaded a root unintaller, and in the process of it, he uninstalled something he wasn't supposed to. I don't know exactly what process/apk it was, but it was a system file. Now almost every system app force closes, (phone,mms,contacts,settings). I tried a factory reset, and the problem remains. He is still rooted, and I know the best workaround would be to flash a new rom (custom or stock, i dont really care), but that's where the problem comes in. I am trying to install this:http://forum.xda-developers.com/showthread.php?t=2715496 AutoRec to get a custom recovery, so I can flash a new rom, but because settings instantly force close, I cant enable to install from unknown sources. I tried to adb push the apk, but after about an hour of trying, adb doesn't recognize the device. I tried both a wired, and wireless adb attempt (idk if its even possible to adb push an apk via wireless, but I tried, and it says my device is unauthorized, so didn't work. Is there any workaround to my problem? I downloaded an app that enables usb debugging, but adb still doesn't recognize, even after i installed the driver. Been at this for hours with no luck, would be great if one of you knew a way to fix this dilemma.
FuzionRain said:
My brother has an LG G2 (verizon), I rooted his phone for him because he's not much of an android enthusiast himself. He wanted to get rid of some bloatware on stock rom so he downloaded a root unintaller, and in the process of it, he uninstalled something he wasn't supposed to. I don't know exactly what process/apk it was, but it was a system file. Now almost every system app force closes, (phone,mms,contacts,settings). I tried a factory reset, and the problem remains. He is still rooted, and I know the best workaround would be to flash a new rom (custom or stock, i dont really care), but that's where the problem comes in. I am trying to install this:http://forum.xda-developers.com/showthread.php?t=2715496 AutoRec to get a custom recovery, so I can flash a new rom, but because settings instantly force close, I cant enable to install from unknown sources. I tried to adb push the apk, but after about an hour of trying, adb doesn't recognize the device. I tried both a wired, and wireless adb attempt (idk if its even possible to adb push an apk via wireless, but I tried, and it says my device is unauthorized, so didn't work. Is there any workaround to my problem? I downloaded an app that enables usb debugging, but adb still doesn't recognize, even after i installed the driver. Been at this for hours with no luck, would be great if one of you knew a way to fix this dilemma.
Click to expand...
Click to collapse
Just return it to stock using the guide on the main page. You can disable apps via App Manager without having root. If he does root it again, tell him to rename files to .bak instead of deleting them...
I've decided to get my phone ready to accept the (hopefully soon) OTA update for my 2013 X. Right now it's on 4.4.4, bootloader unlocked (thanks Sunshine!), and rooted. I had it rooted to take advantage of Xposed and Secure Settings with Tasker integration. I also used TitaniumBackup to freeze the Verizon and some Moto apps I never used.
Currently, I have uninstalled every Xposed module I downloaded, then unistalled Xposed itself and finally the Xposed installer app. After that I went into Titanium and defrosted everything that was frozen. Now I have a fair amount of updates coming in from the Play store for all those apps that were frozen. Should I go ahead and update them?
From what I've read, there's been talk on whether or not I have to un-root my phone. I thought I just had to use the toolkit to flash back the stock recovery? That should be the only thing left to do? What about some apps that are device administrators like Cerberus? Do I need to remove them from that list?
Thank you for any advice. I plan on flashing stock recovery when I get home this evening.
Generally speaking an OTA will probably fail if apps it expects to be present are missing or modified in the /system partition. I don't know if having additional items (like Cerberus) will halt the OTA or not. Custom recovery may also interfere with the OTA.
It sounds like you already did all the work, but I personally wouldn't have done any of that until the OTA was actually rolling out. I know they said it will be soon, but it could still be weeks away. I wouldn't give up my phone that was setup how I like it, but that's just my preference.
When the OTA drops, if you try and install it will do all of the validation before it installs anything. If the validation fails, it will tell you it has an error and it won't work. Then you'll have to fix whatever was modified, or reflash the stock firmware to be compatible with the OTA.
I don't believe updating the apps is necessary. I don't even think they need to be active (you can use the Disable function in the App Info screen to hide them), they just need to be present in your /system folder with the correct signature, is how I understand it.
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Googling has led me t believe that this is an error related to the app detecting root. I tried both of these methods, but neither has worked. http://bit.ly/1LnwzAZ http://bit.ly/1LnwEog . I've tried each separately with rebooting in between as well as trying them together all to no avail.
Other than following the guide above the only root-related things I have modified on the phone are the removal of some verizon apps via titanium backup and adding the following xposed module: "NoSafeVolumeWarning".
One thing that I noted was when I uncheck "Enable Superuser" inside of SuperSu 2.46 it displays a message saying "Uninstall Failed !" It still displays the "Superuser is disabled and hidden" underneath the box and if i enable it again and disable it it does not pop up with the uninstall failed message. Does this have something to do with write protection?
Any help would be greatly appreciated!
Thanks,
Adam
johnnyboy239 said:
Hey Guys,
I have an original (2013) Moto X 1060 (Verizon) that I rooted using this method. http://forum.xda-developers.com/moto-x/general/moto-x-root-pogress-60-t3071602 It's been working great with no problems until today when my phone decided to update my google wallet app to the new android pay. Whenever I try to add a card to android pay I'm getting the error "Android Pay Cannot be used...... Google is unable to verify that your device or the software running on it is android compatible."
Click to expand...
Click to collapse
Having the exact same issue. Just upgraded to 5.1 today, xposed Rootcloak as well as No Device Check installed. Also tried Disable SU. Still get the same issue.
Same. I tried uninstalling SU, Hide My Root, and Rootcloak...nothing has worked. Found out today that the app updated when I went to buy something at Walgreen's. How ****ing embarrassing is that?
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Same problem, few apps frozen with TiBu and xposed installed. Any other work around? s
johnnyboy239 said:
So I have not yet found a solution to this and am still hoping someone has one. In the mean time, you can install this app http://www.apk4fun.com/share/7185/ (doesn't need to be from this site, it's just an old version of google wallet, and the one I used), go into settings>apps>google play services>manage data clear all data, and reboot. I just tried it at cub foods and it worked fine, but of course you do have to go into the app first, and I had to disconnect it from the app store with titanium backup so it wouldn't update to android pay again.
Click to expand...
Click to collapse
check to see if your phone allows pin codes to be deactivated at times. I have mine set to not be used at home work and if I am carrying the phone. It is quite useful feature in settings Lockscreen but I am on COS 12.1 OnePlus basically CM
I haven't tried it yet, but I think they only way we'll get this working on root is to install it on stock unrooted, back it up with TiB or Helium, root and then reinstall/restore.
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Ezekial said:
Lots of fail here as well. All the tricks you all listed + some others. It seems there is a lack of consistency for those that resolved. Some just say disabling root, uninstall busybox, uninstall xposed, rootcloak, device checker for play services, etc.
Nothing yet has worked for me. Luckily I backed up Wallet just before taking the update, so I may go back until the community has a solution.
Click to expand...
Click to collapse
I'm in the same boat. Couldn't get AP to work. Just loaded up the previous version of Wallet. Now have two wallet apps, but whatever. Both appear to be working.
Has anyone tried to get Android Pay working by re-locking the bootloader and temp unrooting on a Nexus device (say, a tablet), then getting AP up and running, and then checking to see if it was usable on your other device(s)??....I was curious if Android Pay would work on ALL of your devices once it was set up properly. Working with lock, unlocking, rooting, etc. is much easier on a Nexus than it would be to work on a Moto, or similar.
Does this make any sense?
KenNashua said:
Was able to get Amex card working after uninstalling Xposed. However, I think I'm going to pass on Android Pay until they allow pin codes on the app, not the phone.
Click to expand...
Click to collapse
Tried AP for the first time at Panera today and failed...seems even with Root Cloak on AP and Google Play Service as well as No Device Check, it still fails.
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
same thing happened to me just now.
not sure what to do, not sure if i have to reinstall everything again
fmkilo said:
Has anyone else had a problem where you no longer have root after about 3 reboots after using the sprint userdebug package to gain root?
After investigation, it seems that something changes permissions to /system/etc/init.sec.boot.sh
Or perhaps because nothing sets permissions on this file itself after setting up /system/etc/launch_daemonsu.sh the contents of this file and not the context or permissions are transferred to /system/etc/init.sec.boot.sh
I performed the operations that are done to launch_daemonsu.sh prior to its duplication to init.sec.boot.sh and executed it, I was then able to get a supersu prompt to grant root priveleges. I have to re-run this script every boot to get a prompt otherwise all root requests immediately fail.
I used adb root shell to make changes since it does not require supersu to manage its root privileges.
I am not sure if I needed to change permissions, but I doubt I'll be re-flashing the userdebug firmware to find out. (I was preparing to odin back to stock anyway.)
I do not know how to make this script execute during boot. I specialize in more desktop flavors of linux and Android is not quite that.
Click to expand...
Click to collapse
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
JokersWild0075 said:
Note 7 v2 Root Sticking
I exchanged my v1 for the v2 yesterday and did not insert my sim card. I brought it home and went through the OP steps. I inserted the sim after step 5. I was able to successfully root my Note 7 and ran Titanium to uninstall some apps but then I lost root after Samsung + updated. I don't know if it was a coincidence but I decided to retry all the steps and I immediately froze the Samsung + update then proceeded to uninstall the bloat I didn't want(including Samsung+) and my phone has maintained root since then. I have rebooted several times to test it and it has been successful every time. ROM is performing well and I have added Adaway and it too is working great.
Click to expand...
Click to collapse
Listen up folks. Do not and i repeat do not update any of samsungs apks. Until we can find out whats going on. It seems that samsung is now pushing updates thru their apks to check and get rid of SU. They are getting sneaky. So for now do not update any samsungs apk, not even thru google. Also do not update SU, this is another way to lose root. We are working on it. Please do not ask if we found anything, if a fix is found we will post our findings.
If you need shealth, iris scanner, samsung pay, android pay, or any other samsung apk, then you need to stay on stock firmware and not use root.
Also if anyone is having issue with files or odin not flashing, make sure you are not on the new PI4 stock ROM, if you are then odin will fail everytime and at this moment there is no way to root or down grade to the older firmware.
Otherwise Try to redownload all files as it seem that afh is/was having alot of issues with uploads and downloads. This not something that we can fix as we dont host or own that site.
Can you guys break down the steps to regain root without reinstalling the OS? Mine also lost root on v2.
It looks like my S-Health was automatically updated to the latest version, which has been reported to be a root of the cause.
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
elite-fusion said:
Make sure that once you do all tje steps to get root. Make sure you turn wifi off. Once you turn wifi on, it will start auto updating apps in the play store which includes s health and other saamsung apps. Install package disabler and disable all samsung apps. Samsung pay, samsung+, s health, and any others. Also make sire you go back to the play store and into settings and disable auto updating of apps, jist to be on the safe side.
What i would like to know is: am i able to still use samsung cloud? Themes? Etc... because i have been avoiding them since i had to reroot yesterday....please advise.
Click to expand...
Click to collapse
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
galaxyuser88 said:
Try them and see if you can use those services. If you lose root then you have your answer. Some of us dont use those stuff, so it is hard to answer. This is why you folks are here. Test things out. Try different things to see what works for you. Trying those things will not void your warranty. The only thing that might happen is that you might lose root.
Click to expand...
Click to collapse
I am currently logged into the Samsung account and have been for about 2 days now with no ill affects so far, downloaded a couple themes is all...that is with all the Sammy stuff froze and functional root.
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