So... I have an interesting situation here
So I have the 1TB Rog Phone 2 WW model. I went through the process of installing magisk, everything worked fine. I installed edXposed as my xposed solution, installing the required magisk modules which also seemed to work just fine. At some point, I would swear the last change I made was to edXposed which caused a bootloop scenario, possibly a module, I wasn't able to isolate the specific cause. However given the nature of the issue, I haven't ruled out some conflicting magisk module as the culprit. I used the fix bootloop recovery option in TWRP (probably a mistake), which did allow me to boot back into the system, but it disabled magisk. Reinstalling magisk causes the boot loop.
And here I am.
Flashing magisk will fully prevent the system from booting normally. I can no longer root it using magisk without it bootlooping.
"did you remove the offending modules"
Well, I used two guides which basically walk you through the magisk recovery manager, adb alternative, and list module paths, (since I can't post the actual links)
to no avail. The magisk recovery manager failed to install and I was unable to locate any modules in any of the specified paths
(/data/media/mm and /sdcard/mm (I am concerned I do not have the correct module path, but the recovery manager also fails to install, so I'm not necessarily sure what is going on other than it can't find any modules either).
Now yes, I do realize I can flash the stock firmware and start again, but this can be a pain in the neck (I assume the VoLTE trick doesn't survive that process not that its a super difficult process), and ideally I'd rather learn more about the system because that was the point of all this.
If anyone has any input or direction as to an alternative solution to a full on factory restore, I would be most humbly appreciative. I like tinkering with my devices, and this seems like something that can be repeated pretty easily, so I'd like to be better prepared.
Hi , sorry if i can't help you.. since i was also having the same problem although not using any modules from xposed.
flashing magisk via twrp or using patched.img will always yield to bootlop but flashing stock.img will fix it.. but ofcourse we want to root but can't seem to pass this barrier..
i hope someone could help and tell us why is this happening
Related
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
@topjohnwu
I'm sure you've read the google+ message or the post on the front page in regards to Chainfire stopping development on all current root-related apps. This includes thus SuperSU (which was sold to CCMT a long time ago and they did absolutely nothing with) and FlashFire (which i use to flash an OTA and keep root intact.
Now with that in mind, magisk is pretty much the only root solution now and i'm starting to look into it. I've already installed the manager and will flash the stock rom at a later point. First a question.
What would be the proper way to flash an OTA (on my 6P, for as long as it will get them) and keep magisk root intact? (i know my way around ADB a bit and twrp, usually i ADB BOOT the latter, not install it). Has anyone tried the latest magisk with flashfire on a 6?
I'll appreciate your input.
Regards,
Ch3vr0n
I'm also interested in getting OTAs installed while preserving root and magisk, on my Pixel XL. I can't get it working properly using the suggested method from @topjohnwu
May i suggest you make your own topic then? It will do neither of us any good of replies to our issue get lost in replies to the other
I did already.
I just showed that I am interested in a proper solution as well. I have not asked specifically about my issue, but wanted to tell you that the "official" way (which is well documented) doesn't work for some users (it's not only me).
yeah but you have a completely different device. So what's not working for you, isn't even relevant in case. Thanks for the interest though
and a quick bump.
Ch3vr0n said:
Has anyone tried the latest magisk with flashfire on a 6?
Click to expand...
Click to collapse
Hopefully you're aware that you can no longer even purchase FlashFire on the Google Play Store, so it's not a solution going forward...
Who said that was a problem. I've been using pro since day 1. Pro users don't have the time issue and it works just fine.
Sent from my Nexus 6P with Tapatalk
OTA installation tips (from the official Magisk docs):
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
I know that A/B device users have been reporting negative results with the documented method, but fortunately it's not applicable in this case.
Have seen a bunch of reports of Flashfire not working properly with later release of Magisk, but can't confirm since I've never used it.
That leaves the last described method. Should always work, but by then I usually feel it's a lot easier to just use fastboot to flash the latest factory image...
I have some phones with Magisk, and are not A/B devices. Magisk gets lost after the OTA, I just reflash it, reinstall the 4 Magisk modules I use, and open each app that requires root so I can grant root access to them again. Of course, add to Hide the banking and other apps that need it. Not too much trouble for me, even if I usually receive weekly OTAs. Wish I could save the Superuser and module settings of Magisk before flashing, then I can just restore it.
Hi all, i'm using a stock rom, rooted with magisk and debloated (manually). I always faced this problem, the 90% of the modules i try to install ends with something like that:
See Screen below
However i've never asked help because i tought it was a Magisk problem resolvible with an update...but every update ended always in the same way for me when trying to install some modules. I've also attached some logs here of when i tried to update xposed systemless if someone could help me it will be really apprecciated!
P.s Anyone facing the same problem? I've read somewhere that a similar problem is common with Motorola devices but idk if this is the case
Giuskiller said:
Hi all, i'm using a stock rom, rooted with magisk and debloated (manually). I always faced this problem, the 90% of the modules i try to install ends with something like that:
See Screen below
However i've never asked help because i tought it was a Magisk problem resolvible with an update...but every update ended always in the same way for me when trying to install some modules. I've also attached some logs here of when i tried to update xposed systemless if someone could help me it will be really apprecciated!
P.s Anyone facing the same problem? I've read somewhere that a similar problem is common with Motorola devices but idk if this is the case
Click to expand...
Click to collapse
Is this via Magisk manager?
ashyx said:
Is this via Magisk manager?
Click to expand...
Click to collapse
Yes this is via Magisk Manager, however the same error (could not mount something) appears also when i try to install a module via twrp. The "best" thing is that some module just works both way (Busybox NDK for example) while other fails both ways. No module work in a way and doesn't work in another. So basically if a module work in magisk can be installed also via twrp otherwise it cannot be installed, no matter what i try
I have the same problem. Trying to install viper4a.
I have no clue how to fix it
Giuskiller said:
Yes this is via Magisk Manager, however the same error (could not mount something) appears also when i try to install a module via twrp. The "best" thing is that some module just works both way (Busybox NDK for example) while other fails both ways. No module work in a way and doesn't work in another. So basically if a module work in magisk can be installed also via twrp otherwise it cannot be installed, no matter what i try
Click to expand...
Click to collapse
I think this is a bug in Magisk with the way some modules attempt to install and mount, which is why some work.
I'm surprised though that they don't install in TWRP. Is your device encrypted, can you mount /data in recovery?
ashyx said:
I think this is a bug in Magisk with the way some modules attempt to install and mount, which is why some work.
I'm surprised though that they don't install in TWRP. Is your device encrypted, can you mount /data in recovery?
Click to expand...
Click to collapse
Actually i'm at university, but when i come back home i will try and let you know. What i can say for now is that every zip i've flashed so far worked just flawlessy (well, apart magisk's ones)
Downloaded atmos dolby only module for nougat....rebooted snd stucked on samsung logo. Ohhhh.... How to get rid of this module, is anyway to do it?
Please help
Edit:
installed module uninstaller and followed it - > https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
working now.
Looking for info how to install viper4Android....
netgar said:
Downloaded atmos dolby only module for nougat....rebooted snd stucked on samsung logo. Ohhhh.... How to get rid of this module, is anyway to do it?
Please help
Edit:
installed module uninstaller and followed it - > https://forum.xda-developers.com/showpost.php?p=72542167&postcount=242
working now.
Looking for info how to install viper4Android....
Click to expand...
Click to collapse
Well as far as i know, if you're on stock rom you won't be able to install audio mods because they're in conflict with something in the Rom. You should use a custom rom instead. However not sure 100% about this, maybe some audio mods can work, but you should ask someone else, i'm not so informed
Hi everyone,
I am pretty new to rooting, flashing, modding etc.
My problem is as follows:
I am on Pie 10.0.1.0PDIMIFJ, upgraded to it thanks to a guide in this forum.
After upgrading (bootloader has been unlocked beforehand of course) I got root through patched boot.img and Magisk Manager.
I did this in order to be able to gain some everyday treats such as Youtube background playing and especially V4A.
I could install these modules via Magisk, but they do not seem to work.
V4A is asking for driver installation everytime I reboot my phone, and I have to reboot after every driver installation.
This happens independently from the version of Viper I am trying to install.
After installing Youtube Vanced nothing changes. Playing stops when closing the app while a video is turned on.
I also tried a couple of other modules but none seems to be working.
I read somewhere that this could be connected to "SELinux permissive" something . I am sorry, I do not really know what that's about but maybe someone out there could give me a hint as to where I have to look.
I do not need a guide or anything, don't mind learning something on the way
Help would be greatly appreciated.
Thank you guys in advance
Anyone?
Same/similar issue
I am also experiencing the same issue, was able to install Viper and pixel Camera mod, then after no matter what module I install it does not show up in the app drawer atleast, I tried App systemizer , Cloudfare DNS and SF font.. nothing seems to work than the first installed two modules. Tried to install and remove them multiple times.
Cleared magisk cache
installed M<agisk from TWRP multiple times.
tried to install modules from TWRP as well.
I am so new to all these, please dont mind any mistakes.
Thanks.
The same problem I got.How to do to enable camera 2api.
The latest OTA update made my phone bootloop if i re-flash magisk patched init_boot image...
After I asked Stock users, it looks like it's a GrapheneOS june update + Magisk specific issue.
Do someone else also have this issue?
Phone boots normally, then reboot to recovery instead of reaching lock screen.
For now, I re-flashed panther-factory-2023061402 init_boot.
Have you tried Magisk canary version? or maybe GrapheneOS doesn't like june update and newest Magisk and you need to either go back down to stable Magisk or an older version of Magisk?
Actually, after re-reading your OP, a module might be the cause of the bootloop -- I've recently seen similar behavior from other members where device bootloops or crashes during/right-after loading & starting up -- if you were on the stock ROM I would suggest you loading up in Safe Mode to see if it is a module issue; I don't know anything about GrapheneOS so I don't know if it offers anything similar. I wonder if the adb command to remove modules at boot would work....
mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/
Albirew said:
mhh, right, i don't have a lot of modules aside hosts, fdroid and busybox, but it may be module-related.
Until now, I did everything with TWRP, but now, well, let's say it's a little more difficult =)
... safe mode works with GrapheneOS, good =)
re-enabling modules one by one until i find the culprit.
... and the failing module was... Magisk built-in Busybox 1.0.5 \o/
Click to expand...
Click to collapse
knew it....
glad I helped get you there!