If the only thing that changed is your ROM then why do you think it's a Magisk problem?
Magisk General Support / Discussion
- Thread starter topjohnwu
- Start date
i try uninstall magisk. my phone boot again. and i try install magisk v 18.1 my phone boot and no problem
So that is additional information that would make helping you a lot easier. The more information you give the higher the chance somebody can help you.
And like always logs would increase your chances to get help a lot too.
Anyone have a workaround for RBC WM ONLINE SERVICES not working on rooted devices? Magisk latest beta and manager with magisk hide doesn't do it. I pass safety net on LG V30 PLUS.
Did you hide MagiskManager by repacking it? Settings > Hide Magisk Manager
Did you try MagiskHide props conf module?
You should also follow the advice and try the suggestions in this great guide by @Didgeridoohan : https://www.didgeridoohan.com/magisk/MagiskHide
Last edited:
Have you tried everything here https://www.didgeridoohan.com/magisk/MagiskHideHidingRoot
Quick test: can you pass rootbeerfresh?
https://play.google.com/store/apps/details?id=com.kimchangyoun.rootbeerFresh.sample
Short version:
Enter app into Magisk hide
Hide Magisk Manager
Create boot script containing
chmod 440 /proc/net/unix &>/dev/null
Stop your app, clear data and cache
Reboot
I'm trying to install Magisk through TWRP but the zip file isn't showing up anywhere. I downloaded the zip using the Magisk Manager apk and it put the file in the download folder of my internal storage. To be sure I also copied it to the root of my internal storage. But the zip is nowhere to be seen. I also tried mounting storage but that didn't work.
Use a version of twrp lower than the 1 your doing it with for your device.
TWRP failed to mount my storage using latest.
Perhaps your TWRP is looking for an img file (instead of a zip file). There is a toggle in the lower right corner to switch from .img to .zip (and vice versa).
You are looking in the right place, correct? /sdcard/Download/ or, since you copied it to root of internal storage, just /sdcard/
If it's there when you start the phone it's there in TWRP. Unless TWRP can't decrypt data for some reason (which is possible in some cases). What phone? What version of Android?
How do I unroot my OS? I am using this https://xdaforums.com/redmi-note-5-pro/development/rom-pixel-experience-t3830197 OS
Magisk uninstaller didn't unroot the device
After uninstall Magisk I also can't use Supersu because I get binary occupied message (even after installing the supersu.img
Magisk uninstaller didn't unroot the device
After uninstall Magisk I also can't use Supersu because I get binary occupied message (even after installing the supersu.img
Last edited:
Make sure you're using the latest uninstaller from https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Flash the unrooted boot image from your ROM after flashing the uninstaller. If that still doesn't work flash @osm0sis's unsu zip https://xdaforums.com/apps/supersu/2014-09-02-supersu-v2-05-t2868133/post63615067
SuperSU won't work in any case. It's too old for that ROM, which is Pie based.
To be clear, did you use the install, select storage option, in TWRP to choose internal storage, instead of external storage?
Last edited:
You should post your logs in the Canary thread. Depending on the problem a catlog, a debug log (install Canary debug version), twrp install log and/or a boot log might be required.
MobilePASS checks for root now
Info / Warning for users of the MobilePASS app:
Since the recent 8.4.3 (84300) upgrade, MobilePASS now includes a check whether your device is rooted, which wasn't the case before.
As usual, just adding MobilePASS to your Magisk hidelist is sufficient to prevent that it detects your device is rooted.
Although easy to bypass, I would highly recommend to add MobilePASS to your hidelist before the upgrade to 8.4.3 is installed at your device. This because when MobilePASS is upgraded to 8.4.3 and not yet hided, your device token will be blocked so current token has to be revoked and the whole device registration / enrollment process must be repeated.
Just added this info to prevent waste of your time...
Info / Warning for users of the MobilePASS app:
Since the recent 8.4.3 (84300) upgrade, MobilePASS now includes a check whether your device is rooted, which wasn't the case before.
As usual, just adding MobilePASS to your Magisk hidelist is sufficient to prevent that it detects your device is rooted.
Although easy to bypass, I would highly recommend to add MobilePASS to your hidelist before the upgrade to 8.4.3 is installed at your device. This because when MobilePASS is upgraded to 8.4.3 and not yet hided, your device token will be blocked so current token has to be revoked and the whole device registration / enrollment process must be repeated.
Just added this info to prevent waste of your time...
Cant pass safetyNet, Magisk modules show up but dont work
Hi guys can you help? For a few days now I have been trying to pass the safetyNet on Magisk without a success. I manags to pass the bascIntegity test but the ctsProfile is still false. I wanted to change the devices fingerprint but when trying to do it in terminal emulator nothing happens. On top of that it says that the magisk is not working. I installed few modules on Magisk, they do show up but dont work :/ dont know what to do. please help. I attached the log from Magisk.
Hi guys can you help? For a few days now I have been trying to pass the safetyNet on Magisk without a success. I manags to pass the bascIntegity test but the ctsProfile is still false. I wanted to change the devices fingerprint but when trying to do it in terminal emulator nothing happens. On top of that it says that the magisk is not working. I installed few modules on Magisk, they do show up but dont work :/ dont know what to do. please help. I attached the log from Magisk.
Why are you hiding this:
com.google.android.gms/com.google.android.gms:snet
If I am not mistaken, I believe that is needed for the snet check to work properly.
The Magisk default is to only have this hidden in Play Services:
com.google.android.gms/com.google.android.gms.unstable.
I believe it automatically adds the one for microg, also:
org.microg.gms.droidguard/com.google.android.gms.unstable
Last edited:
Everything looks fine in your log (except for the Hide list containing a bunch of unnecessary entries, to pass SafetyNet you don't need to add anything to the list at all). You need to be more detailed about what it is that isn't working. And it might be a good idea to install the Magisk Canary debug build to get better logs.
Similar threads
Top Liked Posts
-
2
Translation: "Can android15 beta be used?"
I'm not aware of specific compatibility fixes for A15 yet, but just try it and let us know... It may work...
BTW, please post in English here.
PW2
Ah, then you may have a separate or related issue... (Did you have HyperOS originally or update from MIUI?... Never set another user or guest profile in MIUI prior to upgrading?)I have hyper os im mi10 As far as I remember, I didn't set it, I don't even know where to find it
If in owner profile, any Multiuser Mode should work anyway... Set in Magisk App Settings BTW.
PW2
No idea if you're using an owner profile... Why not try changing Multiuser Mode in Magisk App to Device Owner Managed or User Independent just to be sure?...
If not that, do you have a way to wipe /data/adb/magisk folder and magisk.db file?... Doing that and rebooting will rebuild Magisk configuration in case it just got corrupted...
PW1
Didn't work out. Odin just stopped right before passing stage. I rebooted the phone manualy, baseband is still unknown as long as EMEI.1
Mmm. Not sure that will help either... You can open a GitHub issue if you're prepared to install Debug Magisk build and supply logs; Devs might help further. PW -
5
Known issue. A fix has been merged. You can use the Debug app, revert back to 27001 or wait until 27003 is released.
EDIT: Ninja'd4
Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about it4
Not pushed yet... Looks like recent Android Gradle plugin upgrade just didn't build properly... Guess a new build may come once Upgrade AGP is reverted but may not happen till AGP upgrade is redone.
PW4
Not pushed yet according to my magisk app.
Luckily i don't hide or need to hide; this is a sad bug and i hope, for others' sake, it's pushed as soon as the developers can. But that's also why it's canary and not beta or release, it's why (or should be why) we use canary, to squash bugs before the rest experience them.4
Only v27000 is Stable. (and Beta). v27001 and v27002 are Canary or Debug
Set your Update Channel to Stable and you will see (just like you can see also on GitHub) that latest Stable is v27000, there was never Stable v27001 or v27002
Generally, Stable is always Nx100
So, you cannot downgrade to Stable v27001 but Canary v27001 should be just like Stable v27000 (same codebase). That's also the general policy, whenever Nx100 Stable is released, then immediately comes Canary Nx100 +1, on the same code-base
Therefore, downgrade to Stable v27000 instead -
1103This is the place for general support and discussion regarding "Public Releases", which includes both stable and beta releases.
All information, including troubleshoot guides and notes, are in the Announcement Thread156Hello, I haven't given much support on XDA lately. It can be resulted from
- University started and I have limited free time. In fact, I mostly develop during midnight
- I live in Taiwan, which has large time zone differences between my European/American contributors/testers, which usually forces me to stay up late at night to discuss/test stuffs.
- The new version is about to come, I don't want to spend effort on supporting old releases
New Forum!
As you might have already discovered, Magisk got its own subforum on XDA! Many thanks to all the support you gave me, and much more information/features/support is about to come!
**For developers supporting all the devices that are not using standard Android boot format, feel free to create threads in this section (actually, PLEASE do so) for your favorite devices after v7 is out. As I currently know, Asus devices require signing the boot image before flashing, and is model dependant; Sony devices seems to use ELF kernel that is unpatchable, or some has two ramdisks (inner + outer), both requires different workarounds; LG bootloader locked devices has to manually "BUMP" the boot image after flashing Magisk..... and there may be lots of other crazy boot image formats that haven't come up to my attention yet.
It is impossible for me to support all these non-standard boot images, and I hope the community can collaborate to make Magisk running across all the devices. Overall, community collaboration is what XDA about
The Pixel Phone
Some of you might already know this news, that the next Pixel Phone right around the corner seems like it does not have ramdisk in boot image, which pretty much wrecked Magisk in all ways. However, it pretty much doomed root itself too. Kernel modifications is inevitable IMO, so I'll try to migrate my scripts to C programs that could possibly be included into the kernel itself. Note that I'm not familiar with linux kernel, I'm not even sure if my idea and concept is correct or not. But once the device is available, I think developers will find a way to bypass all the difficulties, and I'll do my best to learn things
Current Progress
In the past month, I've spent quite some time learning SELinux, so that I can avoid using SuperSU's sepolicy patches. Thanks to the helps and tips from @phhusson and @Chainfire, I finally have a much clearer understanding of how SELinux works. The Magisk core parts (the scripts, boot image patches, new features, more supports) are actually done some time ago. What is causing all the delays is the Magisk Manager.
To be completely honest, although I can code in Java without much issues, Magisk Manager is actually my first Android application, I had to reach out for assistance, and fortunately awesome developers like @DVDandroid and @digitalhigh contributed a lot, which makes the current Manager awesome.
After the repo system and module management is mostly done, I was about to do some adjustments and release, but what we really done is decided to add another feature: auto-unroot with per-app settings. I decided to wait for it to be finished, and then do my adjustments. Due to reasons that'll be mentioned later, this feature will likely not be available for the next release (should come in future updates)
Safety Net Disaster
Those who are using Magisk for Safety Net bypass purposes must have known that Google recently updated the detection method of my Systemless Xposed. I still have no idea what Safety Net is detecting, so currently I cannot fix it on my side (also because I'm busy working on the next update). However, suhide developed by @Chainfire is able to hide Xposed and worked fine.
However, only my Systemless Xposed v86.2, which is based on SuperSU's su.d, is supported using that method. v86.2 and v86.5 (latest, Magisk based) have nearly identical binaries, and the only difference is the path where the binaries are stored.
I'm still not sure what's the real issue for it not being supported, I just hope it is not done intentionally.
Conclusion
Due to the fact that my Safety Net bypass is not 100% perfect now, I do not want to spend any more time waiting for auto-unroot to be polished. What I'm doing now is finishing up all the things I'd like to change in Magisk Manager (it has been a while since I last contributed to Manager, my fellow developers are doing all the heavy job), which might take a little more time, after that, packed with tons of information to be announced in Magisk Section, I'll release the long awaited update.
Hope this lengthy post gives you the idea of the whole situation, and again thanks for all your support!!121Ah, some Chainfire bashing, I hope it is not too late for me to exercise additional villainy.
First, let me make clear I have nothing against @topjohnwu, nor against Magisk. Magisk is an interesting project and it certainly displays @topjohnwu ingenuity and persistence. I don't doubt we will see more interesting things from his hands.
-------------------------
What has happened here is not all that dark and complicated, from either end. I returned from holidays, and someone pointed me at Magisk. My first thought: interesting!
Among other things, the thread lists some issues with SuperSU, which in combination with the phrase The developer also requests users to not bug Chainfire with compatibility requests for SuperSU with Magisk from the portal article, raised my left eyebrow by nigh half an inch. The popular systemless xposed mod is apparently now based on it, and apparently it now no longer works with SuperSU, and apparently I'm not supposed to fix that, nor any of the other found issues. I found that a bit weird. So yes, I have told @topjohnwu that I was a bit surprised he was posting about issues with SuperSU without notifying me about them (I can't fix or help fix issues I'm not aware of, after all).
He's also spreading a modified version of the SuperSU package, which is not all that uncommon, nor necessarily a problem. I have not looked into what he modified, I only ran a few quick tests on one of my devices, and found some commonly used commands run as root to be broken. I have informed him of this as well.
It appears the tool of choice for Magisk is phh's Superuser, because of some of the mentioned issues with SuperSU. That's fine by itself, but fixing issues in that superuser by incorporating SuperSU's binaries into it is a somewhat questionable practise. After all, SuperSU is a commercial closed-source package that helps pay for my dinner, and superuser is a direct competitor. I have informed him that I was surprised he did this without asking for permission. I have expressed similar surprise on him spreading a modified version of LiveBoot (which helps pay for a snack now and then).
@topjohnwu has also stated that Magisk's scripts are largely influenced by mine (I have not checked). Scripts based on mine are used all over the place on XDA, some people have crafted amazing things based on them, I have never made an issue of this (otherwise I would have just made them binaries). But yes, I have also stated to him that I don't think it's very nice to base something on one program, and then using that to (almost exclusively) push something directly competing with that program.
tl;dr Towards @topjohnwu, I have:
- expressed surprise he has issues getting Magisk to work with SuperSU, and has chosen not to inform me about those
- expressed surprise he is using SuperSU binaries in a competing superuser without permission
- expressed surprise he is posting a modified LiveBoot without permission
- informed him of issues with the modified SuperSU he has posted
- let him know I thought it wasn't very nice to be applying my scripts to benefit seemingly exclusively that same competing superuser
To be crystal clear:
- I have not asked for an apology
- I have not asked for Magisk to be abandoned, neither the root hiding nor systemless module parts, and certainly not systemless xposed
- I have not made an issue of any of this anywhere, until this post
- I have not even specifically asked for anything to be taken down (though obviously in my opinion the other superuser package mixed with SuperSU's binaries, as well as the LiveBoot package, should go)
- I have not reported this thread to XDA moderators for copyright violations or otherwise
While my conversation with @topjohnwu may not win any awards for being friendly (though it may win some for brevity), I think all things considered my response has been rather mild. To be perfectly honest, until the apology post, I thought this was over with already. I think the apology post was triggered because I haven't replied to his last PM for a while - I was in the zone, it happens.
To emphasize again, I have nothing against @topjohnwu, Magisk, or systemless xposed, and it is certainly not my goal to see any of them go. If it can be made to work together with SuperSU, great.
I get it though: you think of something, you want to see if you can make it work, you finally get it to work, you publish it, it takes off - enthusiasm gets the better of you. Maybe in the rush some mistakes are made. That doesn't mean you have to just drop it and run. None of my stuff would make it past 0.1 if I stopped at the first big mistake
Aside from said being in the zone coding, I usually regret actually responding to these sort of things the day after, which has made me hesitant to reply. Surprise me.76Thread temporarily closed so everyone sees this.
The flood of "SafetyNet isn't working for me either!" posts are not helpful, at all. Please refrain from posting further, it will be looked into. Please do not forget that not passing SafetyNet is 100% NORMAL AND INTENDED when you have an unlocked booloader or running custom firmware. These are workarounds and they will be worked around in turn.
The Flash
Forum Moderator
EDIT: Thread is reopened... I will be cleaning any SafetyNet posts for a while to keep the thread clean for real issues.75Hello everyone!
I am aware that Google has updated Safety Net that makes Magisk itself a no go for Android Pay. In fact, I witnessed the change live while I am developing the new magiskhide, which should hide all Magisk modules and Magisk installed root.
Google is serious about Safety Net now, clearly hunting down all possibility to run Xposed with Safety Net passed. I spend quite some time examining the new security measures last midnight, and fortunately it seems that it is possible to run Magisk and root along with Safety Net if no Xposed is running. I'm glad I removed the old root toggle at the right time lol, that is no longer feasible with the latest detection.
So stay tuned for the next update, it will come with bug fixes, along with the new magiskhide to bypass that Safety Net.
Google, how will a few systemless mods do any harm
New posts
-
Junsun V1 Plus 8GB-256GB - Britghtness settings by night too strong
- Latest: Alex-Le-Zombiz
-
-
