I appreciate your reply. I cant find an apk for this, or any links, other than some stuff I don't trust on youtube. I did not find any links on how how install this. Github frustrates me, I don't understand it. Can someone point me to how to install this?
Magisk General Support / Discussion
- Thread starter topjohnwu
- Start date
Lord Sithek
Senior Member
Release Release 0.2.1 · Fox2Code/FoxMagiskModuleManager
Use androidx emoji2 as the default emoji provider (Emojis should be the same on any devices with GMS) Add brotli encoding support for https requests Update libraries
github.com
Thank You
Release Release 0.2.1 · Fox2Code/FoxMagiskModuleManager
Use androidx emoji2 as the default emoji provider (Emojis should be the same on any devices with GMS) Add brotli encoding support for https requests Update libraries
Type
Type this search term: github fox magisk modules manager in either google search or as I use, duckduckgo in firefox.
But he was also frustrated with Github (read his post)
I assume you updated with Magisk app hidden, and you renamed to 'magic mask' when hiding? This is supposed to work, appart from going from pre ver 22 to 22 or later as per 22.0 Changelog which says "
RESTORE THE EXISTING MAGISK MANAGER BACK TO NORMAL BEFORE UPGRADING IF HIDDEN!"
In practice the same / similar issues updating w/ hidden app often occur. (I'd say 50% success rate only)... Result is hidden app has partial control / other cannot see root etc.Solution is simple. Locate and uninstall hidden app (may need to uninstall unhidden app also) from device settings, apps, app info list, then reinstall apk. Nb. Your settings / modules won't be affected as they are stored in /data/adb, not app storage. PW
This flag in Momo App is related to using a DeOdexed Rom ( your and all the xiaomi.eu roms are deodexed ).
Most of the stock roms are odexed BUT if someone decide to deodex even one file in his device rom for example: using the SmaliPatcher Module ( Which it will deodexing and patching the services.jar file in the "/system/framework/services.jar" ) then he will get that flag.
Attachments
Last edited:
I really do not get it.!
Why should anyone search and check the logs.
Pictures tell a thousand words.
Well to be fair, the bug was already fixed (not while sleepingNot that I 'sorted out' but they fixed Shamiko - with (42) three other users reported the same problem on TG channel, but when you woke up
)... You were in fact replying to my post re. new version:I had naturally assumed that you were actually using v0.1.2-47, not old initial build therefore.Nb. New Alpha Magisk has Xhook fix merged...
New Shadow Mistress Yuko is also available. Shamiko-v0.1.2-47-release zip
PW
Thanks for other useful analysis though.
PW
Last edited:
I'd stop being polite here, but honestly:I really do not get it.!
Why should anyone search and check the logs.
Pictures tell a thousand words.
Why should anybody ask questions here and expect the others to waste time answering him, if he was too lazy to follow the conversation on time to be informed from the ongoing posts (talking already two or thee months about.the changes rolling out), and in the first place, too lazy to read the ChangeLog while updating his Magisk installation
Last edited:
If I can still count on my short-term memory how I downloaded and tested just 24h ago:Well to be fair, the bug was already fixed (not while sleeping
I had naturally assumed that you were actually using v0.1.2-47, not old initial build therefore.
Thanks for other useful analysis though.
I downloaded Shamiko from the main Alpha channel, assuming it was the right/latest version to test with
When complaining to the TG channel I saw couple of similar reports with the same error.
ThenI got response to use the latest version and I realized that download for (42) was replaced by (47) - otherwise I don't understand where else would I stumped first to download (42) if not from that same TG channel, where I was posting/responding to (and under the same Shamiko 'topic')
Last edited:
Thank you for that explanation, I knew that Xiaomi.eu ROMs are deodexed but didn't know that for Momo it means that 'Restriction on non-SDK interfaces is not working"
Thank you for being a great contributer to xda.
I have been checking in on this thread since day one.
My problem with this thread is that no one at least tries reading the basics before any modding.
The same questions are ask every day and answered with no improvement to this thread to keep the clutter down.
Remember the Bozos with the Pokémon go BS....
I suppose that the same reasoning applies to stock OnePlus ROMs [OOS].
Ok, I saw your exchange later. It was in less known Alpha channel (~ 700 members) where init release was posted. Assume you found that after my first posts... Only updated 47 version was posted in main Alpha feed (6.2k subscribers) before you tried with Alpha as I said. These posts and comments are also mirrored in the 700 member feed however... PW
You need to search (find Telegram channel links in LSPosed GitHub) for new Zygisk-LSPosed. Zygisk and Riru are incompatible now. PW
Thanks. Do you maybe know also about the flag/detection:
- Partition mounted abnormally
Realme 7 pro, No custom rom
I have a problem:
I enabled the stuff in the Google Play Services (and do everything else).
But when i reboot my phone The Google Play Services seems to be untouched like i neved changed anything with it in Deny List...
Screens show Before and After Reboot.
I did this multiple times.
Attachments
You can't see anything in Google Play Services
But try with SafetyNet Checker like YASNAC
If it doesn't pass, try with installing Universal SafetyNet Fix 2.2.0 (XDA USNF thread)
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
5
Your phone isn't rooted! The top section of your screenshot shows Magisk "Installed N/A".
Installing the Magisk app isn't enough to root your phone.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'd
4
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
Just open another with "version code: 27002" somewhere in first post, explain you tested both but issue is with Canary only, not Debug... Supply logs from broken build and wait for further instructions from Devs... Template requires the version code (or bot closes) + logs (or Devs will often close with comment like "no log no fix")...
PW
Edit: Someone opened proper issue following template just now:
https://github.com/topjohnwu/Magisk/issues/7921
Looks to me like this commit has issues:
Always update stub APK when upgrade
committed5 days ago -
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
