Magisk General Support / Discussion

Search This thread
By:
Advanced…
m0han

m0han

Senior Member
Apr 30, 2012
6,020
3,068
Asus ZenFone Max Pro M1
Xiaomi Poco X3 NFC
topjohnwu said:
....Magisk Is A Magic Mask to Alter System Systemless-ly.
  • If you are running custom roms, dirty flash the rom again to remove all possible issues. If the rom includes SuperSU, unzip the boot image from the rom zip, and flash it through TWRP, flashify, fastboot etc. to restore to stock ramdisk......
  • ....... you can now download Magisk and flash to your device.
  • To remove Magisk, restore your boot image back (Magisk will backup your boot image automatically in /data/stock_boot(md5).img.gz), then delete /data/magisk.img.
Click to expand...
Click to collapse
is the following still applicable in the case of custom roms?
smohanv said:
1. Boot in to TWRP
2. go to Advanced / File Manager and delete folder named supersu
3. go to Advanced / Terminal and enter these two commands
echo SYSTEMLESS=true>>/data/.supersu
echo BINDSYSTEMXBIN=false>>/data/.supersu​
The first one forces systemless, the second prevents /su/xbin_bind from existing.​
4. Flashed Beta SuperSu 2.74-2 (we can notice while flashing this zip after the above script, we will not see the line saying "Disabling OTA". Also, end of flashing it warns that it takes longer time to boot.
5. Reboot device and enjoy systemless
6. To check if we have achieved systemless root, go to system/xbin folder and we should not see the file named "su".
7. I rebooted in to TWRP and flashed xposed 85.1 (also updated with 85.2 later) and installed the apk (Material design apk from this thread)
8. All done and my xposed works.....
Click to expand...
Click to collapse
 
Last edited:
  • Like
Reactions: maria1., -scryptic-, lyong1390 and 20 others
S

swipp3r

Member
Sep 22, 2014
10
4
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?
 
  • Like
Reactions: maria1. and driftr31
grep_i

grep_i

Senior Member
Sep 19, 2015
1,551
621
swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ?
Click to expand...
Click to collapse
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.

Sent from my Nexus 5 using XDA-Developers mobile app
 
  • Like
Reactions: harrymason37, Bintang Krisna, it0rrent and 2 others
S

swipp3r

Member
Sep 22, 2014
10
4
grep_i said:
Sure you probably did something wrong.
For starters you gave way to little information.
Did you follow the procedure from the OP exactly ?
What rom do you have, custom recovery if any, custom kernel if any ?
How did you flash ?
Come on people give this information by yourself please, don't let us pull it out of you everytime.
You know you are the one needing help than please try to give detailed information about your problem.

Sent from my Nexus 5 using XDA-Developers mobile app
Click to expand...
Click to collapse
Stock marshmallow, flashed via twrp, and yes i followed the op correctly. No custom kernel.
 
  • Like
Reactions: it0rrent
Nezorflame

Nezorflame

Senior Member
Sep 7, 2009
990
2,752
Yerevan
github.com
Google Nexus 5
Google Pixel 6
swipp3r said:
Stuck at boot screen on the S7 Exynos variant, is this just for stock Android or did i do something wrong? I flashed the Magisk v1 then the phh root zip now im stuck at the boot screen ��
Click to expand...
Click to collapse

Did you flash phh's root zip from this thread's Downloads section or from original phh's thread? If the latter, then that's probably the culprit.
 
  • Like
Reactions: Scandiz
S

ShapeShifter499

Senior Member
Sep 13, 2009
474
160
@topjohnwu this new "magisk" method. It doesn't allow Android Pay to work on custom roms like CyanogenMod does it? If I remove SU from CyanogenMod and use your root.
 
ghbuur

ghbuur

Senior Member
May 24, 2013
717
764
great work, will try it out soon! one little thing i noticed in the thread title...i guess it should be 2016 ;)
 
You must log in or register to reply here.

Similar threads

T
  • Locked
  • Sticky
Magisk - The Magic Mask for Android
Replies
56
Views
6M
T
topjohnwu
T
  • Locked
[CLOSED][BETA][2018.7.19] Magisk v16.7 (1671)
Replies
7K
Views
3M
T
topjohnwu
Heisenberg
[Discussion] PokeMon Go Magisk Discussion Thread
Replies
5K
Views
649K
beneditodragon
beneditodragon
Didgeridoohan
[Discussion] Google Pay Magisk Discussion Thread
Replies
3K
Views
571K
I
ihavenolifee
yochananmarqos
Collection of Magisk Modules v2
Replies
1K
Views
1M
あなたの
あなたの

Top Liked Posts

24 Hours 30 Days All time
  • 1
    J
    J.Michael
    Elvara said:
    I can't find anything anywhere about it but I have a oneplus Nord 2T, I was using it with android 13 (oxygen) without problem to install the app and root the phone.
    I finally upgraded to android 14 through the OTA, my root was gone of course I was able to patch the file and get root again after the reboot, the magisk app was gone.
    When I try to install it I have no problem but when I open it the screen change to black for a second then comes back to the menu with the app gone.
    I have an app called App Manager that can use root to install/remove or freeze all type of apps, it has a log of the removed app and I can see there it was removed.
    I don't understand how or why only magisk seems to be a problem when I have other apps installed from unknown sources that are still there.
    Any idea?
    Click to expand...
    Click to collapse
    Are you sure 5hat the version of Magisk app you used to patch is the same version you are installing after flashing the patched file?

    I have heard that Magisk will not tolerate an out-of-date app, but if you installed the Magisk app once, then patched, flashed, and rebooted, I don't see why there would be a conflict.

    Of course, there are lots of reports of problems with lots of versions of Magisk. Maybe you're trying to use a bad one.

    Say what version of Magisk you are trying to use.
    View
  • 5
    Lughnasadh
    Lughnasadh
    HippoMan said:
    I'm now having a problem hiding the TJW Magisk 27002 app ...

    I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.

    The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:

    (1) Unhide Magisk
    (2) Update Magisk (27002 was listed)
    (3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
    (4) Magisk 27002 indeed came up properly after reboot.
    (5) Tried to perform Hide The Magisk App.

    I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.

    I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.

    I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.

    What am I missing?
    Click to expand...
    Click to collapse
    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 🙃
    View
    4
    zgfg
    zgfg
    Jaitsu said:
    Is the Magisk 27001 APK/zip still available anywhere? I'd like to downgrade, but I can only find 27000 on Github and 27002 via update. I don't want to go to Canary in case the mounting changes break anything, or Debug as I hear the extra logging etc. causes performance issues (correct me if I'm wrong).
    Click to expand...
    Click to collapse
    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
    View
    4
    bombadier
    bombadier
    HippoMan said:
    I'm now having a problem hiding the TJW Magisk 27002 app ...

    I finally was able to resurrect my old Pixel 5. It's running stock A11 and was running TJW Magisk 26004 with no problem.

    The Magisk manager was showing that the upgrade to 27002 was ready for installation, and so I did the following:

    (1) Unhide Magisk
    (2) Update Magisk (27002 was listed)
    (3) After Magisk manager restarted, I did Direct Update to 27002, including reboot
    (4) Magisk 27002 indeed came up properly after reboot.
    (5) Tried to perform Hide The Magisk App.

    I entered the arbitrary name for hiding, and I clicked "OK". But the hiding never took place.

    I rebooted again, to see if perhaps that's necessary, and I repeated the hiding attempt by adding the same arbitrary name, and I again clicked "OK". But the hiding still didn't take place.

    I searched my device, and there is no app nor shortcut with that arbitrary name. I also tried other, different arbitrary names, but after clicking "OK", the hiding still didn't take place for any name I chose.

    What am I missing?
    Click to expand...
    Click to collapse
    Known problem with 27002, the debug version doesn't have the problem with hiding, read back to see the discussion about it
    View
    4
    P
    pndwal
    forserg said:
    Direct Install with recovery mode checked worked for me. You were right.

    After I flashed wrong CSC firmware my baseband and EMEIs disappeared. Now I have updated bootloader and I cant to flash original CSC firmware anymore. Any ideas how to restore baseband, EMEIs or it is too late?
    Click to expand...
    Click to collapse
    Yep, I told you several times that you need Recovery mode (selected) for your Ramdisk=No device; instructions for this are also clear in official Installation Instruction page too, but apparently you have not been trying to follow official instructions, so it's no real surprise you've messed up firmware too... Please take *extra* care when modding as there are simply so many variables and pitfalls! 😬

    Are you flashing patched AP (Application Processor binary) along with all the other package binaries (X4?) for your S10+ (also in Magisk Installation page, Samsung section)??

    CP is Cellular Processor (Nb. Oft repeated references to CP as 'core processor' may be misleading) binary package (also referred to as Baseband Modem) so that should have fixed mismatched baseband etc... correct CSC (Consumer Software Customization; region, APN and carrier specific software packages/settings) and even BL (Bootloader) are most likely also important...

    Nb. BL doesn't always update bootloader version, but if later firmware has been flashed be aware that these can also cause anti-roll back version for bootloader to be incremented (in the event that an update patches serious vulns) so you original firmware may be blocked and you may need to use later packages only...

    If flashing latest complete firmware package via Odin doesn't fix your IMEI / baseband issues it may be that you've messed with partitions that contain unique device values in the past... You may need to ask in Galaxy, S10 or S10+ XDA forums for that. 🤠 PW
    View
    3
    P
    pndwal
    waldmax said:
    Sorry to bother with maybe a stupid question.

    I am using Magisk and root for a long time on my Poco F2 Pro with latest xiaomi.eu ROM and XiamiEUModule App for NFC payment.

    Everything was working fine with Magisk 26.4
    A few days ago I updatet to Magisk 27.0 since then my normal banking app of an Austrian bank gives me a warning, but is still working. No problem witih NFC payment.
    Would be nice to get rid of this warning again, have you any idea how to do so, or how to find out the reason.

    *******************

    On my new phone, Xiaomi 14 Ultra Global Edition FW 1.0.4 I applied for unlocking bootloader, did the unlock yesterday, which caused factory reset.

    I patched init_boot.img after installing Magisk 27.0, enabled Zygisk, hide Magisk, installed PlayIntegrityFix_v15.9.6, Enforced Deny List, Added necessary services to deny list, in Developer Options of Google Play I meet Basic and Device Integrity. Banking App Works, but also the warning about root detected.

    So I flashed FW 1.0.2 via Fastboot with Clean_All Option, made update to 1.0.4 with the updater app (flashing 1.0.4. with fastboot failed, so I made safe bet with flashing 1.0.2. what I have already done successful this morning).
    Then agan the same procedure but with Magisk 26.4, enabled Zygisk, hide Magisk, installed PlayIntegrityFix_v15.9.6, Enforced Deny List, Added necessary services to deny list, in Developer Options of Google Play I meet Basic and Device Integrity. Banking App works without any warning.

    Can you tell me why this behaviour with older Magisk or how to find out?

    **************

    Bonus info- NFC Payment with the app of my bank (not Google Wallet) does not work on Xiami 14 Ultra, but it did also not work as long bootloader was locked. Hoping for xiaomi.eu ROM for Aurora, and working NFC...
    Click to expand...
    Click to collapse
    Difference may be related to new "atomic mount" I mentioned above, not sure, but be aware that DenyList is NOT designed for (proper) root hiding... I'd be trying with Shamiko which just hijacks list from DenyList but runs in hidelist mode. Nb. The same Devs responsible for most recent major refactoring in Magisk also maintain Shamiko.

    Also, Hide the Magisk app (ie. Magisk in stub) is broken in 27.0... You may need that. 🤠 PW
    View
  • 1103
    T
    topjohnwu
    This 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 Thread
    View
    156
    T
    topjohnwu
    Hello, 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
    The planned update is delayed again and again, to some point I think I'll shed some light about what has been happening lately, also along with some announcements.

    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 :D

    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!!
    View
    121
    Chainfire
    Chainfire
    Ah, 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.
    View
    76
    nathanchance
    nathanchance
    Thread 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.
    View
    75
    T
    topjohnwu
    Hello 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 :p:p
    View

New posts