Magisk General Support / Discussion

Search This thread

2_i

Member
May 22, 2013
30
3
Update: It appears that Magisk was not updated for a while on both phones, so the problem could be tied to an earlier Magisk update than just the very recent. Since I have access to TWRP on both phones, I guess I should flash an earlier version of Magisk from a zip, right? It seems that the version 1y back ran fine.

OK, one more update even though I am conversing with myself. However, someone may run into the post while trying to solve similar problems. Advice to go to device specific forums does not work for older less popular devices as such forums dry out with time. I managed to resurrect both Z2 Play phones that quit booting after the Magisk update. One got resurrected from a TWRP backup. Magisk will not be updated there from the version that worked. The other phone had no backup, but I managed to uninstall Magisk there using the Magisk-uninstaller-20210117.zip. Surprisingly just flashing the file removed Magisk. It is easy to run into instructions for uninstalling that are outdated and do not work, but this file did it for me. The experience of the near loss of the phone was so traumatic for the owner of that phone, that I was asked not to install Magisk ever again not just on the particular phone but any future one that the person might own.
 
  • Like
Reactions: J.Michael

AquilaDroid

Senior Member
Oct 11, 2012
677
626
Raleigh, NC
Pixel 5 on January update here. Is it still necessary to uninstall Magisk or remove installed modules before flashing February factory image? I've run into issues in the past if I didn't do that step. Currently on Magisk Manager 8.0.7 (4834) and Magisk 21.4 (21400). TIA!
 

Homeboy76

Senior Member
  • Aug 24, 2012
    2,574
    1,248
    Pixel 5 on January update here. Is it still necessary to uninstall Magisk or remove installed modules before flashing February factory image? I've run into issues in the past if I didn't do that step. Currently on Magisk Manager 8.0.7 (4834) and Magisk 21.4 (21400). TIA!
    Yes.
    Why? Sometimes Google makes changes to the firmware that breaks some modules. This causes bootloops. So, it is better to be safe than sorry.
     

    Boggle247

    Member
    Dec 12, 2017
    14
    1
    I'm having an issue where magisk no longer provides root and the module selection appears to be missing. I've got a pixel 1 running lineageos 17.1 without any gapps flashed nor micro g. This seems to have happened after I updated to magisk 21.4. I've uploaded a screenshot of my magisk maganger app. How can i fix this ?
    Screenshot_20210203-131232_Magisk_Manager.png
     

    Homeboy76

    Senior Member
  • Aug 24, 2012
    2,574
    1,248
    I'm having an issue where magisk no longer provides root and the module selection appears to be missing. I've got a pixel 1 running lineageos 17.1 without any gapps flashed nor micro g. This seems to have happened after I updated to magisk 21.4. I've uploaded a screenshot of my magisk maganger app. How can i fix this ?View attachment 5208827
    @Boggle247
    <Edited for clarification>
    1. Download the latest LOS zip, LOS recovery, GApps zip (pico/nano) and Magisk Canary (magisk-debug.apk) to your platform-tools folder on your computer.
    2. (rename magisk-debug.apk - magisk-debug.zip
    3. Install LOS Recovery/Boot LOS Recovery
      • Boot bootloader
      • Attach phone to computer via USB cable
      • Open a Command prompt in the Platform-tools folder on your computer.
      • Type fastboot flash boot lineage-17.1-20219999-recovery-marlin.img
    4. ADB Sideload, LOS zip file:
      • On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
      • On the host machine, sideload the package using:
        adb sideload lineage-17.1-20219999-nightly-marlin-signed.zip
    5. Reboot to Recovery
      • DO NOT reboot the phone.
      • Reboot to recovery makes the other slot active LOS was installed on the other slot.
    6. ADB Sideload Gapps zip:
      • On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
      • On the host machine, sideload the package using:
        adb sideload open_gapps-arm64-10.0-nano-20219999.zip
        If prompted that signature doesn't match, select Yes to continue.
    7. ADB Sideload magisk-debug apk.
      • On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
      • On the host machine, sideload the package using:
        adb sideload magisk-debug.zip
        If prompted that signature doesn't match, select Yes to continue.
    8. Reboot
    9. These should be installed: LOS, Gapps and Magisk
     
    Last edited:

    zgfg

    Senior Member
  • Oct 10, 2016
    5,289
    2,593
    Did anybody with Magisk Canary 21407 tryt to Hide Magisk Manager (btw, why is the option still named that way, whereas Magisk Manager is now merged with Magisk and renamed?!) and then to patch the image?

    Seems that it fails (at least) on A11 - it does for me (Xiaomi Mi 9T, Xiaomi.eu A11) and I found the same comment on Github:

    Seems that Storage permission is missing (but in Settings /Apps I cannot give it to my hidden/renamed app)
     

    Attachments

    • Screenshot_2021-02-03-21-31-04-191_v.vpccbdwfmto.jpg
      Screenshot_2021-02-03-21-31-04-191_v.vpccbdwfmto.jpg
      112.1 KB · Views: 24
    • Screenshot_2021-02-03-21-49-09-817_com.mixplorer.beta.jpg
      Screenshot_2021-02-03-21-49-09-817_com.mixplorer.beta.jpg
      359.3 KB · Views: 21
    Last edited:

    Boggle247

    Member
    Dec 12, 2017
    14
    1
    @Boggle247
    1. Download the latest LOS zip, LOS recovery, GApps zip (pico/nano) and Magisk Canary (magisk-debug.apk) to your platform-tools folder on your computer.
    2. (rename magisk-debug.apk - magisk-debug.zip
    3. Boot your phone to LOS recovery
      • Boot bootloader
      • Attach phone to computer via USB cable
      • Open a Command prompt in the Platform-tools folder on your computer.
      • Type fastboot boot lineage-17.1-20219999-recovery-marlin.img
    4. Using ADB Sideload, flash LOS zip file. Sideload the LOS.zip package:
      • On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
      • On the host machine, sideload the package using:
        adb sideload lineage-17.1-20219999-nightly-marlin-signed.zip
    5. Reboot to Recovery (don't reboot the phone before installing GApps or you may have to Factory Reset). Reboot to recovery basically makes the other slot active (LOS was installed on that other slot).
    6. Now ADB Sideload Gapps zip:
      • On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
      • On the host machine, sideload the package using:
        adb sideload open_gapps-arm64-10.0-nano-20219999.zip
        On the phone, select 'Yes' to continue if prompted that signature doesn't match.
    7. Now ADB Sideload Magisk zip.
      • On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.
      • On the host machine, sideload the package using:
        adb sideload magisk-debug.zip
        On the phone, select 'Yes' to continue if prompted that signature doesn't match.
    8. reboot the phone
      You should have the new version of LOS along with all your gapps and root intact.

    Just to be clear I don't have gapps installed. So I'd follow this minus the bits about gapps I assume.

    I was planning on just extracting the boot.IMG from the Los version and release I am running, then patching it with magisk as outlined on the magisk github. Then adb fastboot flash boot patched.IMG, would that work?

    Would either method preserve magisk so this doesn't happen again? Or do I have to do one of these every time there is a LOS or magisk update?
     
    • Like
    Reactions: Homeboy76

    zgfg

    Senior Member
  • Oct 10, 2016
    5,289
    2,593
    Also, what is the use of (changing) the Update channel in Canary 21407?

    I changed the Update chanmel to Stable and it showed as the latest Manager version was then 21400 (which is not quite correct - 21400 is the last Magisk but not Magisk Manager version for Stable)

    When I tried to install Manager - it failed with package parsing error (frankly, I didn't expect that downgrading the app could work)

    But more important, image can be patched, but instead of patching with 21400 (Stable) it still patches with 21407 Canary

    Before that merge of Magisk and Manager it was perfectly possible to patch from e.g. Canary Manager app with an older Stable Magisk (or vice versa), etc
     

    Attachments

    • IMG_20210203_221036.jpg
      IMG_20210203_221036.jpg
      305.2 KB · Views: 33
    • Screenshot_2021-02-03-22-12-32-409_com.miui.packageinstaller.jpg
      Screenshot_2021-02-03-22-12-32-409_com.miui.packageinstaller.jpg
      122.8 KB · Views: 33
    • IMG_20210203_220924.jpg
      IMG_20210203_220924.jpg
      196.7 KB · Views: 23
    Last edited:
    • Like
    Reactions: Homeboy76

    Homeboy76

    Senior Member
  • Aug 24, 2012
    2,574
    1,248
    Just to be clear I don't have gapps installed. So I'd follow this minus the bits about gapps I assume.

    I was planning on just extracting the boot.IMG from the Los version and release I am running, then patching it with magisk as outlined on the magisk github. Then adb fastboot flash boot patched.IMG, would that work?

    Would either method preserve magisk so this doesn't happen again? Or do I have to do one of these every time there is a LOS or magisk update?
    Yes, skip. The Gapps section.
    The method I posted works. I do it every time I update LOS. If @zgfg is commeting on my post, you have two options. The method I suggested or his method. Choose one.
     
    Last edited:

    Homeboy76

    Senior Member
  • Aug 24, 2012
    2,574
    1,248
    is there a solution so I don't have to redo this with every LOS nightly update? Seems a bit ridiculous....
    I use that method because it works, it takes 5 minutes max. I do not update every time there is a new nightly build.
    There may be another solution to your problem: You could try posting your question on the lineage 17-1 thread or google for solutions.
     
    Last edited:

    zgfg

    Senior Member
  • Oct 10, 2016
    5,289
    2,593
    Also, what is the use of (changing) the Update channel in Canary 21407?

    I changed the Update chanmel to Stable and it showed as the latest Manager version was then 21400 (which is not quite correct - 21400 is the last Magisk but not Magisk Manager version for Stable)

    But when I tried to install Manager - it failed with package parsing error (frankly, I didn't even expect that could work)

    But more important, image can be patched, but instead of to patch with 21400 (Stable) it still patches with 21407 Canary

    Btw, before that merge of Magisk and Manager it was perfectly possible to patch from e.g. Canary Manager app with an older Stable Magisk (or vice versa), etc
    Sorry, this post here was my wrong experiment with the Custom channel in v21407, hence I deleted the post

    There is the same problem with Custom Channel as when setting the Update channel to e.g. Stable (no additional issues for Custom), as in the quoted post above
     
    Last edited:
    • Like
    Reactions: Homeboy76

    Didgeridoohan

    Senior Moderator / Dev Committee / Dev Relations
    Staff member
    May 31, 2012
    11,633
    12,378
    Gothenburg
    Google Nexus 4
    Nexus 6
    @zgfg That boot patching with a hidden app fails is known and there's a PR available with a fix already.

    And the "Manager" in settings will surely be changed in future releases...

    And since the merge of Magisk and Manager is quite a big change I would not expect that patching with old releases work. Until this change has been pushed to stable/beta it's not strange that the update channels on the Canary app are a bit wonky.

    Although, I do not see the behaviour you describe with the custom channel. Using that link I get v21.4 (21400).
     
    • Like
    Reactions: Homeboy76

    zgfg

    Senior Member
  • Oct 10, 2016
    5,289
    2,593
    @zgfg That boot patching with a hidden app fails is known and there's a PR available with a fix already.

    And the "Manager" in settings will surely be changed in future releases...

    And since the merge of Magisk and Manager is quite a big change I would not expect that patching with old releases work. Until this change has been pushed to stable/beta it's not strange that the update channels on the Canary app are a bit wonky.

    Although, I do not see the behaviour you describe with the custom channel. Using that link I get v21.4 (21400).
    But suppose generally, one day when Stable also goes to the merged Manager app and Magisk

    Canary is usually higher version than Stable - hence you could not install older Stable Magisk (Manager) app from the newer Canary app

    And if patching (and direct update) is tight with your installed Magisk app version, then you could also not go to an older Magisk (service) by playing with the Update channel, so I wonder should that option be removed
     
    Last edited:
    • Like
    Reactions: Homeboy76

    Didgeridoohan

    Senior Moderator / Dev Committee / Dev Relations
    Staff member
    May 31, 2012
    11,633
    12,378
    Gothenburg
    Google Nexus 4
    Nexus 6
    But suppose generally, one day when Stable also goes to the merged Manager app and Magisk

    Shouldn't be a problem, because then the update infrastructure should be compatible.

    Canary is usually higher version than Stable - hence you could not install older Stable Magisk (Manager) app from the newer Canary app

    If you need an older stable apk release they're all available on Github...

    And if patching (and direct update) is tight with your installed version, then you could also not go to an older Magisk by playing with Update channel, so I wonder should that be removed

    Why should it be removed? The update channels (even a custom one) will still be valid, just with the new infrastructure. If you need older releases, see my answer above. For current and future releases there will be no problem.
     
    • Like
    Reactions: Homeboy76

    zgfg

    Senior Member
  • Oct 10, 2016
    5,289
    2,593
    Shouldn't be a problem, because then the update infrastructure should be compatible.



    If you need an older stable apk release they're all available on Github...



    Why should it be removed? The update channels (even a custom one) will still be valid, just with the new infrastructure. If you need older releases, see my answer above. For current and future releases there will be no problem.
    I know very well how to go with older releases (with the old infrastructure) but I'm talking about the new infrastructure, 'updating' to an older merged Magisk app + Magisk (even inside the Canary - try yourself from v21407 to v21406)

    But we'll see when things stabilize
     
    • Like
    Reactions: Homeboy76

    Didgeridoohan

    Senior Moderator / Dev Committee / Dev Relations
    Staff member
    May 31, 2012
    11,633
    12,378
    Gothenburg
    Google Nexus 4
    Nexus 6
    I know very well how to go with older releases (with the old infrastructure) but I'm talking about the new infrastructure, 'updating' to an older merged Magisk app + Magisk (even inside the Canary - try yourself from v21407 to v21406)

    But we'll see when things stabilize

    Ah... Now I see what you mean. The issue is that the new Magisk/app setup installs the Magisk internals from what's included in the app. If the update channels are to be preserved for future releases then it would be expected that those take precedence over what's available in the app and downloads the matching internals. You might want to update your GitHub issue to make that clearer. And maybe do something about the size of those screenshots (they're massive and makes it hard to find the text)...
     

    zgfg

    Senior Member
  • Oct 10, 2016
    5,289
    2,593
    Ah... Now I see what you mean. The issue is that the new Magisk/app setup installs the Magisk internals from what's included in the app. If the update channels are to be preserved for future releases then it would be expected that those take precedence over what's available in the app and downloads the matching internals.

    You might want to update your GitHub issue to make that clearer. And maybe do something about the size of those screenshots (they're massive and makes it hard to find the text)...
    Yeah - that was my point what should drive the patching/direct installing target version, Update channel or the installed Magisk app version

    Btw, I deleted the part about Custom channel (also that post here), I had pasted the wrong URL causing the strange effect with v20.3

    Screenshots were edited in Github issue to mark the point, but ok I also cut them off now to get them smaller:
     
    Last edited:

    Top Liked Posts

    • 3
      The files are replaced but logs keep showing actions.
      Please, help me.
      My experience with init.rc files was a couple of years back when I was building ROMs and the source for the device (built and maintained by someone else) had a bootloop. I went through it and basically reordered the load sequence. And from memory, the one I looked at mostly controlled the boot sequence (ie starting services) and setting mounts and folder permissions to enable the ROM to run as expected.

      Now, your screenshots appear to be that you are trying to replace your RC's with empty files? ie delete them.

      When I was looking at the RC file I dealt with, a lot of it looked like it could of been done after the boot had completed. For example, set the write permissions on the file that controls brightness, so that when you slide the brightness UI controller, it could write to the file.

      Anyway, getting back to your actual issue, I would guess that magisk would not be able to replace your init.rc files in time, as its way to early in the boot process, (as I found with replacing the boot animation which I think is started by an init.rc file) and possibly magisk itself depends on some of that, and even is part of the boot img modifications it does. ie it actually changes the boot image, to be able to do what you wish to do. But remember, its a guess.

      Are you certain you cannot achieve the actual changes you are trying to achieve, post boot? I REALLY don't think it would work in your case, but maybe give the reboot trick above a go. And maybe it will be a different level / service to kill to catch it after it has been changed, but keep it changed, but make it re-run the init files, but as I am typing, that just sounds like a path for duplication (ie retsart services that are already running), that just isnt going to succeed.

      If its a custom ROM, maybe get your builder to change the build.
      1
      Yep, then that's what did it! 😜

      Seems ADB command "adb wait-for-device shell magisk --remove-modules" to remove all modules is actually a good alternative, and would have worked even w/ bootlooping setup.

      In your case though, since you flashed unpatched boot image, booting to Safe mode could succeed or at least became less difficult / key combo timing started working normally ... And holding vol down 'at boot animation' occurring as you did, happens to be precisely the way to do this!
      https://support.google.com/pixelphone/answer/2852139?hl=en#zippy=,if-your-phone-is-off

      So modules were already disabled at this point (no need for "adb wait-for-device shell magisk --remove-modules" command). 😛

      I'm still mystified regarding safe mode, or safe mode key combo at least, being broken / difficult w/ Magisk patched boot image on Pixels however... Perhaps it's broken on other devices w/ Magisk root too. (?)

      Anyway, as they say in the business, the rest my friend is history. 🙂 PW
      I tried "adb wait-for-device shell magisk --remove-modules" with patched boot.img in regular mode and it didn't work. Phone shut down as soon as Google animation was passed.
    • 14
      Before anyone freaks out, Google has given John the ok to keep working on Magisk.

      Edit: hmm... John has deleted the tweet stating that he's got the green light from Google in regards to Magisk. Maybe bad news, maybe no news. We'll just have to wait and see...

      Ref:
      https://www.xda-developers.com/magisk-developer-topjohnwu-leaves-apple-joins-google/

      12
      The man needs a break.

      He certainly deserves one in my book. Not a lynch mob.
      John Wu, 2h

      I understand that being the developer of a popular open source project, people are *longing* for an explanation.

      However, the speculation and conspiracy theories are getting out of hand, there are even attempts to sabotage my employment in the name of "saving the community"...

      This is putting extreme strain on me mentally, so let me get the facts straight: nobody really knows exactly how things will go in the future.

      I tweeted an assumption caused by miscommunication; I was informed it to be non factual; I deleted the tweet. That's all, really.

      So please, PLEASE, put down your tinfoil hats and pitchforks, and allow me to handle the situation privately. I will update you once there is a conclusion.

      Nobody is hired to kill off a project.
      I did not join Google for money.
      And of course, I have not betrayed the community.
      www.twitter.com/topjohnwu/status/1394835335096406023

      PW
      8
      Just want to point out that sharing screenshots of a private conversation isn't cool. The damage is already done and it's out there, but let John himself be the one to break the news.
      8
      From what John has said on Reddit and behind the scenes, recanting on some made statements, he can not touch magisk at all not speak on it anymore.
      Most here are aware of that quote, and as has been pointed out, it was private, he didn't 'say it on Reddit', it was only part of a much longer communication and the 'leak' was not appreciated, but my guess is that many colaborators will be in the loop.
      Since he does own the repositories for magisk so we could see them just disappear. He can't push an update which only he can do, so it's either fork it and go that route, which he knows all the ins and outs of magisk and now works for Google(2+2 says he will spilling the beans on the background to block it), I believe they have him on a gag because conflict of interest with magisk sidestepping their security system.
      I don't think G needs him to spill the beans on 'blocking' Magisk; they're quite aware of how it works. It's source is open, after all...

      But if you meant blocking attestation spoofing / bypassing (MagiskHide, some modules, and other), they already know how to make this foolproof. It does require compliant hardware to implement however, and it seems that when some target percentage of devices have launched with tee, a switch will be flipped, and spoofing attestation, and hence MagiskHide at least outside of userspace (ie bootloader Unlocked / verified boot, will become impossible for practical purposes for most users.

      MagiskHide will still be able to hide root from apps within userspace, but these can still check secure boot status through tee attestation, and will likely report 'root/jailbreak' but actually mean 'insecure boot environment'.

      Expect the pool of those still able to hide bootloader status to be reduced, for practical purposes, to those running custom OSs with inbuilt spoofing or Magisk on devices with launch version < or = to Android 7 (last version without requisite keymaster 3) overnight. (Nb. Hardware-backed Keystore began to be hardened from Android 6)
      https://source.android.com/security/keystore

      Hardware TEE of course, stands for Trusted Execution Environment, and it is not just implemented by Google.

      It actually facilities security in RISC, IBM, AMD, Intel, Apple, as well as Qualcomm, MediaTek, Samsung and Huawei SOCs running various systems. Here's an article focussing on ARM implementation:
      https://embeddedbits.org/introduction-to-trusted-execution-environment-tee-arm-trustzone/

      Interestingly, it states:
      TEE is not the solution to all of our security problems. It is just another layer to make it harder to exploit a vulnerability in the operating system. But nothing is 100% secure.
      You can't work for somewhere and have an ap they completely bypasses their OS without a amjor conflict of interest.
      Well, it doesn't bypass it; it gives superuser access as well as ways to overlay mods on an OS, and both things are certainly allowed by design if bootloader is unlocked.

      There are ways to prevent such unlocking, but Google doesn't do that. That's not to say they don't know how however. That would be laughable; It is their system (both open source Android framework and proprietary apps). They simply leave that to OEMs to implement, and, of course, a number take such measures.
      https://support.google.com/accounts/answer/9211246?hl=en
      Google doesn't even want you using a "modified system" to access your Google account. Google has major issue with root.
      They NEVER said that.

      They have protected their proprietary apps by forbidding bundling GApps with custom ROMs, originally ordering Steve Kondik to 'cease and desist' bundling with CyanogenMod, but offered an olive branch in quick succession when he assumed project was dead, allowing individual users to sideload the same, and sites like OpenGApps to host them.

      They have also expressly stated they DON'T oppose either root or custom ROMs, even recently. Eg from Tech Lead for Android hardware-backed security subsystems:
      Shawn Willden, May 19

      The Platform Security team has never been opposed to modding/rooting (and most of us are firm believers in users' right to own their devices), but remains firmly focused on maximizing security for the 99.99% of users who don't. Root weakens the security model.
      www.twitter.com/shawnwillden/status/1394665579076743175

      In line with the above, they state clearly that if you choose to mod your device, "you lose some of the security protection provided by Google", and they do have recommendations, including "Use a different device for important accounts & sensitive data"
      https://support.google.com/accounts...s-with-modified-rooted-android-versions?hl=en

      Also, rather than prevent their own proprietary apps from running in custom modded systems, they allow these to appear on PlayStore and be used freely. Very few are restricted at all, unless for good (security, corporate partners requirements etc) reason. GPay comes to mind here.

      They could, of course, prevent this (especially when HKA is fully functional), simply by requiring PlayProtect Certified Device, but so far they have PURPOSELY allowed custom modders even with uncertified (Chinese etc) devices to add their devices to their online White List that allows them to run the very GApps (without spoofing) that they were prevented from using w/ stock ROMs.

      This sets an example to others (wish likes of Maccas would wake up), but SafetyNet API and PlayProtect certification are available for apps / code deemed a security risk... Of course, SafetyNet Implementation can be abused, but Google's stance is that the code's author has the right to be informed about the execution environments status and make such decisions.

      Interestingly, it seems not only that Google is unopposed to custom ROMs, but they are not averse to the idea of certifying these / issuing appropriate signing keys so bootloader can be locked to allow full SafetyNet pass (with no spoofing), and GApps can be included legitimately. Of course, this solution evidently precludes root.

      The spiritual successor of CyanogenMod, LineageOS, is in a good position to get such an agreement as they already take pains not to 'subvert Google's security model', never bundling GApps, pre-root, signature spoofing (MicroG would come unstuck here 😉) or any other spoofing mods or techniques. Note this conversation between Shawn and Luca Stefani ('Director for LineageAndroid & Developer'):
      www.twitter.com/shawnwillden/status/1238161446200127488

      That ones been a while (time of initial Google Hardware Key Attestation testing), but I hope we see more on the front. 😛

      In short, Google is against subverting their security model, which includes SafetyNet implementation which ALLOWS code to run in insecure environments (even with superuser privileges) WITHOUT subverting it, by making TEE attestation results available to interested parties. Hardware TEE just ensures that the attestation is accurate... And Google didn't invent it either!

      Here's a bit I posted re. mainstream influence on Google's decision to implement Hardware backed attestation for for verified boot and Trusted Execution Environment:
      https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-83280363

      I don't want to take sides in this; only to give perspective. There's certainly room for many viewpoints. Take what John said on the subject just 4 months ago:
      https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-84398495

      ... I wonder what he's thinking now! 😜 PW
      8
      there is no access via terminal

      i installed my fave module, debloat, but of course cant access it...they were serious about the lite part :)

      As for the install of lite...i installed the apk and patched a boot img, had no errors

      v4a/vanced youtube doesnt work either, now i really want to die :)

      going to bed finally, in disgust
      Installation of modules works in Magisk Lite but with some additional tricks:

      1) When you install a module from Magisk Lite app, it creates its folder in:
      /data/adb/modules_update

      When you reboot, Lite will not read that folder and the module(s) will not really be installed/updated (instead, they would be next time when you boot to Stable/Beta/Canary/Alpha, because they do read from /data/adb/modules_update)

      Hence:
      - Install one or more modules you need
      - Use MiXplorer (or another root explorer), or terminal and mv command, or rename it by TWRP:
      /data/adb/modules_update
      to:
      /data/adb/lite_modules_update
      -Reboot, Magisk Lite will properly finish installation of your modules and you will find them in:
      /data/adb/lite_modules

      2) MHPC: I successfully installed but in terminal it doesn't recognize the props command.
      Something is wrong with the path

      You can still use MHPC by invoking instead:
      /system/xbin/props

      3) Similarly for BusyBox NDK. It was installed to /system/xbin

      Indeed, you can list all its commands by:
      ls /system/xbin

      4) I have successfully installed Vanced YouTube root (latest v16.16.38) as a module:

      No ads, background playing, all ok

      5) Smali patcher - Safe Screenhot Mode (allowing to screenshot from apps otherwise not allowing the screenshots)

      E.g., I can make screenshots from Chrome Incognito window

      6) If your debloater uses terminal and installs to /system/xbin, you should be able to exploit as explained above for MHPC and BB

      However, I use my own Systemless Debloater that does not use command line interface (terminal):

      and I have successfully debloated all the same 32 system apps as I do with Magisk Stable/Canary/Alpha

      7) I have manually copied hosts folder from:
      /data/adb/modules/
      to:
      /data/adb/lite_modules/

      and got the adblocking work.
      However, Adaway does not know for that folder and if you update/change anything in AdAway, it will write to its regular modules/hosts folder (but you can always copy again the same folder or just its etc/hosts file)

      9) I didn't try with Viper4Android (I'm already back to Magisk Beta with 'regular' modules) but I believe the installation should work the same way I always install it to Stable/Canary:

      And Lite should similarly work for other modules


      I have some issues with MixPlorer though in Magisk Lite (although I completely uninstalled and reinstalled MiXplorer):

      9) MiXploree was granted root and it works but AFTERWARDS Magisk Lite app shows that Magisk is not installed and I simply have to reboot to get Lite properly working again

      10) MiXplorer can only see the stock content in /system/xbin, i e. without props and BusyBox commands (btw, ls from terminal works fine)

      Same for all other folders being overlaid by Magisk systemless mounting - MiXplorer always shows their stock content while terminal su commands work with the Magisk overlaid content


      But altogether, it would be possible to live with Magisk Lite - even the modules work


      Edit:
      I have Magisk apps Canary, Alpha and Lite downloaded and renamed like:
      Magisk-Lite-7717f0a6(23001).apk

      I have also my boot.ing patched by Magisk Canary, Alpha and Lite and renamed like:
      boot-Magisk_Alpha_23001-xiaomi.eu_multi_HMK20MI9T_21.5.20_v12-11.img

      When I want to switch, I simply install the right Magisk apk, flash the corresponding img from TWRP (or Fastboot) and reboot

      When going from Stable/Canary to Aplha/Lite (or vice versa), that previous Magisk app must be uninstalled because of different signatures

      When installing the Alpha or Lite apk I was asked by Play Protect to send the report - I ignored and upon rebooting with Magisk and MagiskHide properly back on, Play Protect was always ok
    • 1050
      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
      156
      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!!
      121
      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.
      76
      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.
      75
      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
    Our Apps
    Get our official app!
    The best way to access XDA on your phone
    Nav Gestures
    Add swipe gestures to any Android
    One Handed Mode
    Eases uses one hand with your phone