[Discussion] Magisk - The Age of Zygisk.

Search This thread
By:
Advanced…
zgfg

zgfg

Senior Member
Oct 10, 2016
8,986
6,725
Redmi K20 / Xiaomi Mi 9T
Xiaomi Mi 11 Ultra
koberulz said:
How do I uninstall? I can't access the app to uninstall it, and the uninstallation instructions just say that if you can't do that, "flash it like any flashable zip", and I have no idea how to do that. I know TWRP stopped working, is that back? The TWRP thread in the Pixel 3 forum hasn't been updated in years. Or can I just flash it with fastboot?
Click to expand...
Click to collapse
Sorry, I do not know the situation with TWRP for your Pixel device. But check to TWRP.me (official TWRP site), do they have TWRP for your model and your Android version

In the worst case (no TWRP or other custom Recovery) and you cannot open Magisk app, you can always (I know, it's pain in the ass) reinstall your ROM with Factory resetting. That would also fully uninstall Magisk by also deleting all its stuff (modules, database, etc)

---

If you are good with using the Terminal emulator and shell commands, you can avoid Factory resetting

To see if that apply, open your Terminal emulator and execute:
su
magisk -c

If it prints your version of Magisk installed, we can go for

But if it cannot find su, whatever - then sorry, I will not second in that direction further (even if it is 'just' about which Terminal emulator to use or how)
 
J

J.Michael

Recognized Contributor
Jan 20, 2018
1,827
2,084
Samsung Galaxy Tab A series
koberulz said:
How do I uninstall? I can't access the app to uninstall it, and the uninstallation instructions just say that if you can't do that, "flash it like any flashable zip", and I have no idea how to do that. I know TWRP stopped working, is that back? The TWRP thread in the Pixel 3 forum hasn't been updated in years. Or can I just flash it with fastboot?
Click to expand...
Click to collapse
You have to have some idea of what you have done, and how you did it.

For these mysterious Magisk manager apps you cannot run: long press on whatever you are tapping to try to run it, Android should provide a context menu including an item "App info". Choose that, then "Force stop" and "Uninstall". Go through your app drawer carefully, looking for other, renamed, instances of Magisk manager app.

From a command prompt (on the phone; open a terminal window; if you don't have a terminal emulator app, download one) try typing "magisk --help" -- that might give you an indication of whether you have Magisk installed.

You have to know whether you installed Magisk by patching the boot partition or by patching the recovery partition. Whichever, if you have a working fastboot, you should be able to restore the patched partition (by which I mean restore it to its unpatched state) by using fastboot.

Did you ever have TWRP? What do you mean "TWRP stopped working"? Just because someone stopped producing new versions of TWRP, that would have no effect on your device having TWRP.

I have lost track, did you ever try PixelFlasher? It still requires that you have adb and fastboot, but the interface might be more to your liking.
 
  • Like
Reactions: jons99
koberulz

koberulz

Senior Member
Oct 4, 2012
231
26
Perth
PixelFlasher requires Magisk, which brings us back to square one.

I think TWRP was incompatible with an Android update for, like, a year at least? Or maybe it just couldn't be installed, could only be booted? Not sure.

Anyway, booted into TWRP, ran the Magisk uninstaller, ran the most recent Magisk installer, and we have working Magisk! Don't have root, though, so that's the next step. Will give PixelFlasher a go.

EDIT: Now I can't boot at all, it just goes to fastboot after the Google logo. Balls.
 
koberulz

koberulz

Senior Member
Oct 4, 2012
231
26
Perth
jons99 said:
yeah no dude you have a bigger problem I just looked at the support thing you submitted in the pixel flasher page it sims you tried to flash your rom using the latest platform tools which has a problem with fastbootd so you need to use an older platform tools to flash your rom again
Click to expand...
Click to collapse
Well as I said in that thread, I don't know where to get the older versions.
 
J

J.Michael

Recognized Contributor
Jan 20, 2018
1,827
2,084
Samsung Galaxy Tab A series
koberulz said:
PixelFlasher requires Magisk, which brings us back to square one.

I think TWRP was incompatible with an Android update for, like, a year at least? Or maybe it just couldn't be installed, could only be booted? Not sure.

Anyway, booted into TWRP, ran the Magisk uninstaller, ran the most recent Magisk installer, and we have working Magisk! Don't have root, though, so that's the next step. Will give PixelFlasher a go.

EDIT: Now I can't boot at all, it just goes to fastboot after the Google logo. Balls.
Click to expand...
Click to collapse
Can you explain "have working Magisk" at the same time as "Don't have root"?

Do you understand the two parts of "Magisk"? The part that gets injected; i.e., the part that requires that you patch an image. And the part that is just an Android app, formerly officially known as Magisk Manager.
 
  • Like
Reactions: pndwal, Lughnasadh and jons99
Lughnasadh

Lughnasadh

Senior Member
Mar 23, 2015
5,173
6,062
Google Nexus 5
Huawei Nexus 6P
For those that don't know, Platform Tools versions 34.0.0 & 34.0.1 have a problem booting into fastbootd. There have been several users who have ended up with unresponsive phones while flashing factory images on Pixels. Version 33.0.3 is the last correctly working version. Google is aware of this and is working on a fix.

Here is a link to a link to 33.0.3.
 
  • Like
Reactions: beeshyams, dcarvil, J.Michael and 4 others
koberulz

koberulz

Senior Member
Oct 4, 2012
231
26
Perth
J.Michael said:
Can you explain "have working Magisk" at the same time as "Don't have root"?

Do you understand the two parts of "Magisk"? The part that gets injected; i.e., the part that requires that you patch an image. And the part that is just an Android app, formerly officially known as Magisk Manager.
Click to expand...
Click to collapse
When I click on "Magisk" in the app drawer, it opens the app. As opposed to previously, where it did nothing, or threw a "this app keeps stopping" error.
 
  • Like
Reactions: J.Michael
You must log in or register to reply here.

Similar threads

T
  • Sticky
Magisk General Support / Discussion
Replies
56K
Views
6M
U
Unspec
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
yochananmarqos
  • Sticky
Collection of Magisk Modules v2
Replies
1K
Views
1M
J
jacomail95
Heisenberg
[Discussion] PokeMon Go Magisk Discussion Thread
Replies
5K
Views
636K
djkrish5610
djkrish5610

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 10
    P
    pndwal
    hemfreitas11 said:
    Well yeah, i wouldn't mind a company using something like that in their apps. Bank apps are made by banks, there is a name behind them, there's someone accountable, and most important of all they dont have the kind of access that either Magisk or Xposed do, so in my opinion it is pretty much safe to trust them
    Click to expand...
    Click to collapse
    Sure... So you can vote with your feet in any case, but remember this is not about vv's Alpha fork where Appcenter implementation is simply vv's decision... She's free to implement test and debug it in her fork... The objections discussed were to her PR for telemetry in official Canary Magisk which, of course, you'll always have source for.

    Microsoft can ensure private data isn't compromised/abused with Appcenter as it uses their back end, but Magisk is also open to scrutiny by coders in general anyway... Bank apps will need skilled reversers to prove that they're acting honourably.

    So would Jorrit's (chainfire's) SuperSU for that matter, but most rooters in that era wouldn't have given a second thought to the possible (very serious) security breaches they were permitting with closed source root!

    As for Alpha fork, vv has always used it as a test bed for experimental fixes and never promoted it as an alternative Magisk for daily use; it was only ever for those wanting to test innovations or fixes, or as a stop-gap solution until her fixes are merged in Magisk... It seems apparent to me that, with telemetry data continuously coming in, she no longer needs many testers and may be actively discouraging Alpha takeup as a 1100+ Chinese userbase delivers ample data for her prolific contributions to Magisk.

    FWIW, vvb2060's Magisk commit production has been second only to John's (who merges most commits including those of others) for several years now... Just in recent months Shana has been at the top of the leaderboard however, but there's clearly much collaboration also:
    IMG_20230517_193901.jpg


    vv's fixes, and her changes have been at the forefront of Magisk development for some years now... So many major innovations in official Magisk have been developed in vv's Alpha fork and her experimental branches.

    Just to mention a sampling I posted more than a year ago: MTK compatibility, single package delivery, support for 64bit, sepolicy fixes, several isolated process fixes, fixes for UID, MicroG, process names, file based encryption, mount rules for Samsung, auto-close issues bot, reboot menu, multi-user and shared user id compatibility fixes, hidden apps, Chinese doc translations, offline restore app, unsupported environment checking, fix for apex path (a big one), permission fixes, module Installation fixes, Kotlin code cleanup, MagiskHide stopping fix, Renamable App / single package Magisk archive (developed in cooperation with John).... And countless more recent commits for various devices/compatibility, new functionality and major refactoring of magiskinit injection, sepolicy rules and so on.

    Alpha is thus no rogue fork, much less a vehicle for stealing data or scamming any of us and many members here know that the evidence of vv's beneficent motivation is more than anecdotal...

    Whether I choose to do early testing of upcoming Magisk innovations with Alpha or not, I'm certainly not suspicious, rather I'm happy it exists as I am that other test forks and Magisk benefactors are contributing so much to this essential staple modding solution. 😋 PW
    View
    8
    J
    J.Michael
    hemfreitas11 said:
    Sorry if i sound rude or condescending, but do you think using a piece of software with full control over your phone made by a developer with an anime profile picture and who doesn't bother to translate anything they say to English is a very good idea?
    Click to expand...
    Click to collapse
    From what I've read in the Magisk threads, Yes, it's an excellent idea.

    It's not for everyone. The people who know what they are doing can identify which situations make Alpha or Delta worth trying. The "full control over your phone" is no greater than that possessed by the "regular" Magisk.

    As for not bothering to provide English translations, why should she? She has a big enough fan base that I keep seeing references to her releases. Use it or don't. She doesn't charge anything, and you get your money's worth.
    View
    7
    shoey63
    shoey63
    hemfreitas11 said:
    Sorry if i sound rude or condescending, but do you think using a piece of software with full control over your phone made by a developer with an anime profile picture and who doesn't bother to translate anything they say to English is a very good idea?
    Click to expand...
    Click to collapse
    Screenshot_20230516-130542_1.jpg
    See the devs below @topjohnwu down the bottom?
    They are the Alpha devs. Also massive contributors to the main Magisk branch.
    You can trust their software.
    View
    6
    HippoMan
    HippoMan
    pndwal said:
    Of course they understand... Seems those that don't are the paranoid... And nobody's saying you can't be paranoid if you want!... 🤪

    [ ... etc. ... ]
    Click to expand...
    Click to collapse

    Irrespective of the fact that most of them probably have valid, understandable reasons for wanting to keep their source closed and to be difficult to communicate with in their TG channel, the fact that this is the current reality of Alpha is enough to motivate me not to use it.

    I don't hold it against those developers personally, and I respect their feelings and priorities and decisions about this.

    It's just that if I have a choice (and in this case, I do), I prefer not to use this kind of software that is provided under those constraints.

    As for telemetry, given the way that the current Chinese government utilizes similar telemetry aganst not only their own citizens, but also against others in other countries, I have more fear than usual about this particular telemetry. Even if none of the developers are knowingly working with the Chinese government, it's still possible that people from that government might be able to access the fruits of this telemetry.

    I have as much right to be paranoid about this telemetry as do any of the Alpha developers have a right to be paranoid about discussion-group participants.
    View
    6
    P
    pndwal
    J.Michael said:
    As I understand it, Alpha is not meant for widespread use. Its developers are not looking for lots of users. Its a testbed, meant to be used by a few of their friends, and even then only to address specific problems.

    The rest of the world should wait for the changes to bubble into the official Magisk release.
    Click to expand...
    Click to collapse
    Well put...

    This discussion began because we mentioned that Alpha allows Volkswagen app to run and a member wondered if Alpha is trustworthy...

    Alpha solves the issue because it builds Shana's test branch commits and she's got native bridge Zygisk loading working to the point where it's quite useable (but still unfinished)
    IMG_20230506_090803.jpg

    over the last few months...

    The test branches for vv (Nangong Xueshan, @vvb2060), Shana (LoveSyKun, @yujincheng08), Canyie (@canyie) and others are open source, so you could easily build any of their experimental fixes yourself (it's not hard using a GitHub action run), or simply run one of the test branch CI (continuous integration) builds...

    For example, the last collaborative published Refactor zygisk to use native bridge to inject commit was authored by Shana and committed in LSPosed/Metagisk Zygisk branch by 3 weeks ago, and an associated CI build is here:
    Refactor zygisk to use native bridge to inject Magisk Build #61 pushed by yuijincheng08

    That might work fine but many CI builds don't; they're simply test runs with varying usefulness and even successful functioning... Alpha release builds on the other hand, are built using selected commits and have been checked at least for basic functionality by vv, so there's a greater level of reliability despite being bleeding edge stuff.

    I personally haven't used Alpha since John was producing viable Zygisk but not releasing any Canary builds (vv's Alpha served as a Zygisk testbed and POC for many months at the time) due to his mandatory period of restriction on creating/contributing to personal open source projects and Google review of his Magisk Android mod project... The new Zygisk refactoring that is native bridge loading simply made current Alpha builds too tempting for me! 😜... I'll be back to TJW Canary just as soon as we have N/B Zygisk, which Canyie has indicated should arrive with public 27.0 (or perhaps in an earlier Canary build).

    I may be tempted by some other off-the-chart innovation LSP Devs introduce in future and hop on the Alpha bandwagon again, but I'm really eager to see what official Magisk delivers...
    -----------
    ​
    FYI: For anyone interested in what changes / innovations are in the works for Magisk or just being tested,

    vv's test branches currently include:
    Shana / LSP project have:
    Canyie has:
    In TJW (official), @osm0sis has:
    🤠 PW
    View
  • 137
    ipdev
    ipdev
    This is a discussion and help thread for the newer versions of Magisk.​

    The main goal of this thread is to help users migrate to Magisk v24+
    • SafetyNet
      Basic integrity Pass
      CTS profile match Pass​
    • Play Protect certification
      Device is certified​

    Feel free to discuss or give links to other Magisk related issues.
    Fixes for gPay, banking apps and/or other apps and games that detect a 'compromised' Android system.
    Please try to restrain from discussing alternative (unofficial) Magisk builds that include changes that were removed or can not be included in the official Magisk builds. 🙃​

    Please read John's State of Magisk (medium.com)

    Starting with the Magisk 23 (23010) canary builds.
    • MagiskHide is removed.
      MagiskHide masked the sensitive properties of the device to hide it from SafetyNet.
      Renaming (repackaging) the Magisk app is/was not part of MagiskHide.
      You still have the option to Hide the Magisk app under setting.​
    • Magisk Module online Repo is removed.
      The Magisk Module online Repo is still available and can be accessed outside of the Magisk app.​
    • Everything SafetyNet is removed.
      This includes the SafetyNet check that was incorporated into the Magisk app.​
    • Zygisk is introduced.
      Zygote + Magisk = Zygisk​
    • The Deny list replaces the Hide list.
      The Hide list (more or less) hid Magisk from the process on the list.
      The Deny list is similar but instead of hiding Magisk from the process, Magisk is unloaded so there is nothing to hide.​

    Starting with the Magisk 23 (23017) canary builds.
    • Magisk supports update channels per module.
      Each module can include it's own update link.​
    • Hide Magisk offline.
      You do not need internet connection to rename (repackage) the Magisk app.​

    What does this mean?
    Not much.
    It is just the next step in Magisk's development.
    Zygisk is a big step forward. ;)​

    Even before these changes in Magisk, the xda family and the Android community have always been active and willing to share. :D

    Jump to Post​


    This is post will be updated once Magisk v24 is released.​
    View
    72
    ipdev
    ipdev
    Magisk​
    The Magic Mask for Android.​

    Magisk Links:
    GitHub
    Release Notes

    Download Links:
    Stable and Beta releases.
    Canary
    • GitHub
      The notes.md file is the change log.
      The app-debug.apk is Magisk canary.
      Click on app-debug.apk and choose View Raw or click on the Download option.​

    Credits:
    topjohnwu
    All who contribute and support this project.
    View
    62
    ipdev
    ipdev
    Modules​

    MagiskHide Props Config
    This module allows you to add, change and adjust prop values systemlessly using Magisk.​

    MagiskHide Props Config Links:

    Download Links:

    Credits:
    Didgeridoohan
    All who contribute and support this project.


    Universal SafetyNet Fix
    It has been a year now since kdrag0n figured out how to 'trick' SafetyNet.
    This 'trick' has been implemented properly into quite a few custom roms.
    For custom roms that do not include it and/or stock roms, he turned it into a module.​

    Universal SafetyNet Fix Links:

    Download Links:

    Credits:
    kdrag0n
    All who contribute and support this project.
    View
    58
    ipdev
    ipdev
    Apps​

    Fox's Magisk Module Manager
    This app allows you to manage and install Magisk modules.
    Including from an online repo.​

    Fox's Magisk Module Manager Links:

    Download Links:

    Credits:
    Fox2Code
    All who contribute and support this project.

    Play Intergrity API Checker
    This app shows info about your device integrity as reported by Google Play Services.
    If any of this fails could mean your device is rooted or tampered in a way (for example you have an unlocked bootloader).​

    Development:

    Download Links:

    Credits:
    1nikolas
    All who contribute and support this project.

    YASNAC - Yet Another SafetyNet Attestation Checker
    YASNAC (short for Yet Another SafetyNet Attestation Checker) is an Android app that demonstrates SafetyNet Attestation API.​

    YASNAC Links:

    Download Links:

    Credits:
    RikkaW
    All who contribute and support this project.
    View
    48
    ipdev
    ipdev
    Force Basic Attestation​

    Newer devices are designed to support hardware attestation.
    Currently there is no way to hide the sensitive device properties when checked using hardware attestation.​

    To get around this, kdrag0n figured out how trick SafetyNet that the device does not support hardware attestation.
    SafetyNet will then fall back to check using basic attestation.

    Note:
    This method will work for devices that support hardware attestation and devices that do not.
    • Enable Zygisk.
    • Install the USNF module.
    • Reboot

    To keep posts short, the instructions are hid by spoiler tags.
    If you have not installed Magisk.
    Follow the installation link in the Magisk post.​

    Download the Universal SafetyNet Fix module.
    Download link is in the Modules post.​

    1. Enable Zygisk
      • Open the Magisk app.
      • Go to Settings.
      • Scroll down to the Magisk section.
      • Toggle Zygisk on.
      • Go back to the Magisk Home screen.
    2. Go to Modules.
      • Select Install from storage.
      • Navigate to the Universal SafetyNet Fix module zip file and select it.
    3. Reboot.

    The USNF module will adjust the sensitive props that are needed to pass SafetyNet.
    Depending on the device and system (ROM) configuration, you might need to adjust a few more.
    See the Adjust Prop values post.​
    View

New posts