Magisk General Support / Discussion

Search This thread

zgfg

Senior Member
  • Oct 10, 2016
    5,291
    2,594
    @zgfg @pndwal

    Just a quick update

    Magisk Lite continues to keep root detection at bay for both my current bank (WestPac), and my new one (ANZ) and my Samsung Wearables continue to work

    Sadly the one only issue is that the only modules i can use without tripping Magisk Detector are:
    • Swap Torpedo (disables swap, recommended if you have 3Gb+ of RAM and dont play games - if anyone reads this and wants to try, note dont use the one in the OP of its thread (its not in repo), use this one instead, its been updated)
    • Universal GMZ Doze
    Normally im running 8 or 9 modules :)

    What wont work:
    • V4A - it installs two apps and neither will work
    • Font modules - all trigger Magisk system file detection
    • Terminal Debloater - one module i really use on every ROM i flash to debloat them - i really miss this. Ive had to use a system app remover while on Magisk Lite.

    Im about to try clean flashing and using Alpha again with new bank app, also noticed a few posts about installing Magisk (including 23/Canary), loading modules and then uninstalling Magisk app is allowing some to use their finicky banking apps in other threads
    Systemless debloatig works perfectly, however there is maybe a problem with your debloater and its command line interface

    The following one has IMHO even easier interface, you just give a list of the system apps you want to debloat in a text file. From the log file you can see all the other system apps, you make a new list and apply again until you are satisfied with the debloated system

    Working with Stable, Canary, Alpha and Lite:

    PS: I did but only one dirty test with V4A and it didn't work (didn't repeat with the proper uninstalling and reinstalling the module). Maybe the Lite does not support SEPolicy rules
     

    73sydney

    Senior Member
    Jul 21, 2018
    1,521
    1,241
    Sydney
    Google Pixel 2 XL
    Systemless debloatig works perfectly, however there is maybe a problem with your debloater and its command line interface

    The following one has IMHO even easier interface, you just give a list of the system apps you want to debloat in a text file. From the log file you can see all the other system apps, you make a new list and apply again until you are satisfied with the debloated system

    Working with Stable, Canary, Alpha and Lite:

    PS: I did but only one dirty test with V4A and it didn't work (didn't repeat with the proper uninstalling and reinstalling the module). Maybe the Lite does not support SEPolicy rules

    Does your debloater also work for apps under vendor etc?
     

    klemi71

    Senior Member
    Jun 6, 2018
    159
    40
    Google Pixel 3
    Flash stock boot image. Make sure device boots normally.

    Flash Magisk-patched boot image. Boot to Safe Mode. Reboot. See if boots normally.

    Depending on how you boot to safe mode, it might be easier to "say" you want Safe Mode as you are shutting down stock system; then flash patched image; then have first boot be Safe Mode. Or it might be that you should boot stock to Safe Mode before flashing patched image. I do not know your options.
    Thanks, but it didn't work.
     
    • Like
    Reactions: J.Michael

    klemi71

    Senior Member
    Jun 6, 2018
    159
    40
    Google Pixel 3
    This issue?:
    https://github.com/topjohnwu/Magisk/issues/4319
    Some have been able to flash 21.4 w/ this problem.

    I'd give @vvb2060's latest Alpha Magisk a go too. He's merged a number of fixed since John Wu's last builds that may (possibly)have solved this:
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85103975
    Please let us know if you try.

    To try either build, I wouldn't worry about complete Uninstall; Magisk (mask) itself is uninstalled completely by flashing unpatched boot image. App settings (MagiskHide list selections, SuperUser selections) and Modules remain after Magisk App uninstall (they are in /data/adb). Only modules are generally a potential problem, but your issue wasn't caused by a new module. See note below.

    With system booted from unpatched boot image, simply uninstall current Magisk App and Install older 21.4 or newer Alpha Magisk App, check Settings channel is correctly set to Stable or Alpha, patch boot.img extracted from current ROM archive, copy to PC using ADB pull (not MTP as per John's Installation Instruction page), flash it using ADB Fastboot.

    Nb. If you suspect a module (previously installed) may be preventing system booting with Magisk, easiest way is probably to boot to safe mode (google method for your device), then immediately reboot normally. This disables all modules, and you can re-enable later.

    Hope it helps! 🤠 PW
    It isn't the issue you mentioned. After flashing patched boot.omg the device doesn't boot to system. It shuts down.
    I tried alpha build, same behaviour.
    Finally I booted to a TWRP Testbuild for Android 10. Data is encrypted though I removed Lockscreen before doing this. I was able to flash v21.4 from there. Same behaviour.
    I set active slot after flashing just in case... nothing changes. Matlog isn't available, adb commands work, but before I can do anything, phone shuts down.
    After flashing stock boot.img to both slots again everything works fine... unrooted, Magisk is not available if course.
    Thank you very much do far, but issue isn't solved.
     
    • Like
    Reactions: J.Michael

    DiamondJohn

    Recognized Contributor
  • Aug 31, 2013
    5,214
    4,806
    Sydney
    ...snip
    • V4A - it installs two apps and neither will work
    • ...snip...
    • Terminal Debloater - one module i really use on every ROM i flash to debloat them - i really miss this. Ive had to use a system app remover while on Magisk Lite.
    ...snip...
    I havent tested it on the new Magisk lite. I thought the module location had changed so would of assumed it would not work; but talk that the others may or were expected to work makes me think it might. However, the app TeMeFI has a built in Magisk debloater module builder. It can be found at Magisk>Modules>TeMeFI Hide System Apps>Add or Remove - Hide System Apps using a TeMeFI Module>Add One>* One thing that is clear, I really need to shorten some of those menu items...

    If it is simply a case of a moved module location, if you let me know what that is and how to detect when to use/switch to it (eg if statement based on Magisk version), it would probably be pretty simple to modify the path it is built into. And I am working on new release right now.

    Systemless debloatig works perfectly, however there is maybe a problem with your debloater and its command line interface

    The following one has IMHO even easier interface, you just give a list of the system apps you want to debloat in a text file. From the log file you can see all the other system apps, you make a new list and apply again until you are satisfied with the debloated system

    Working with Stable, Canary, Alpha and Lite:

    PS: I did but only one dirty test with V4A and it didn't work (didn't repeat with the proper uninstalling and reinstalling the module). Maybe the Lite does not support SEPolicy rules
    My app above, uses a GUI, so it is pretty easy apart from having to use the GUI again if you clean flash your ROMS. But you can save off the scripts to automate it if you do it repeatedly and dont like to click.

    Regarding Viper, if its the SEPolicy changes that are questionable, then switching to permissive should make that irrelevant (ie test the theory); for testing only of course. There are many methods used to install viper. I have had the best luck on A11 using the attached Magisk zip; note, I did not build it, and it defaults to boot permissive, which can be easily changed with a delay in the service script. It also has a few other very minor things not quite neat, but it has worked for me and others.

    Does your debloater also work for apps under vendor etc?
    TeMeFI does. It looks under (all under system) app, priv-app, product, product/priv-app, vendor, vendor/priv-app
     

    Attachments

    • ViperFX_Android11.zip
      5.7 MB · Views: 2

    ascendant512

    Member
  • Aug 22, 2013
    7
    1
    Thanks, it worked.
    The same on all older Xperias:-(
    You have to do a small and simple patch:

    This is a patch from dev bleckdeth and it works perfect even with Magisk_23001.
    Main thread was https://github.com/topjohnwu/Magisk/issues/3636
    I couldn't figure out how to apply the patch to the phone without root so I followed the build instructions. The project doesn't open in current android-studio but it does build so hey!
     

    Attachments

    • Screenshot_20210610-212904_Magisk.png
      Screenshot_20210610-212904_Magisk.png
      88.4 KB · Views: 26
    • Like
    Reactions: J.Michael

    zgfg

    Senior Member
  • Oct 10, 2016
    5,291
    2,594

    I havent tested it on the new Magisk lite. I thought the module location had changed so would of assumed it would not work; but talk that the others may or were expected to work makes me think it might. However, the app TeMeFI has a built in Magisk debloater module builder. It can be found at Magisk>Modules>TeMeFI Hide System Apps>Add or Remove - Hide System Apps using a TeMeFI Module>Add One>* One thing that is clear, I really need to shorten some of those menu items...

    If it is simply a case of a moved module location, if you let me know what that is and how to detect when to use/switch to it (eg if statement based on Magisk version), it would probably be pretty simple to modify the path it is built into. And I am working on new release right now.


    My app above, uses a GUI, so it is pretty easy apart from having to use the GUI again if you clean flash your ROMS. But you can save off the scripts to automate it if you do it repeatedly and dont like to click.

    Regarding Viper, if its the SEPolicy changes that are questionable, then switching to permissive should make that irrelevant (ie test the theory); for testing only of course. There are many methods used to install viper. I have had the best luck on A11 using the attached Magisk zip; note, I did not build it, and it defaults to boot permissive, which can be easily changed with a delay in the service script. It also has a few other very minor things not quite neat, but it has worked for me and others.


    TeMeFI does. It looks under (all under system) app, priv-app, product, product/priv-app, vendor, vendor/priv-app

    I havent tested it on the new Magisk lite. I thought the module location had changed so would of assumed it would not work; but talk that the others may or were expected to work makes me think it might. However, the app TeMeFI has a built in Magisk debloater module builder. It can be found at Magisk>Modules>TeMeFI Hide System Apps>Add or Remove - Hide System Apps using a TeMeFI Module>Add One>* One thing that is clear, I really need to shorten some of those menu items...

    If it is simply a case of a moved module location, if you let me know what that is and how to detect when to use/switch to it (eg if statement based on Magisk version), it would probably be pretty simple to modify the path it is built into. And I am working on new release right now.


    My app above, uses a GUI, so it is pretty easy apart from having to use the GUI again if you clean flash your ROMS. But you can save off the scripts to automate it if you do it repeatedly and dont like to click.

    Regarding Viper, if its the SEPolicy changes that are questionable, then switching to permissive should make that irrelevant (ie test the theory); for testing only of course. There are many methods used to install viper. I have had the best luck on A11 using the attached Magisk zip; note, I did not build it, and it defaults to boot permissive, which can be easily changed with a delay in the service script. It also has a few other very minor things not quite neat, but it has worked for me and others.


    TeMeFI does. It looks under (all under system) app, priv-app, product, product/priv-app, vendor, vendor/priv-app
    About the Magisk Lite and its /data/adb/lite_modules folder and the needed manual renaming of /data/adb/modules_update to/data/adb/lite_modules_update (when installing a module) please see my previous post:
    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
     
    • Like
    Reactions: J.Michael

    73sydney

    Senior Member
    Jul 21, 2018
    1,521
    1,241
    Sydney
    Google Pixel 2 XL
    I havent tested it on the new Magisk lite. I thought the module location had changed so would of assumed it would not work; but talk that the others may or were expected to work makes me think it might. However, the app TeMeFI has a built in Magisk debloater module builder. It can be found at Magisk>Modules>TeMeFI Hide System Apps>Add or Remove - Hide System Apps using a TeMeFI Module>Add One>* One thing that is clear, I really need to shorten some of those menu items...

    If it is simply a case of a moved module location, if you let me know what that is and how to detect when to use/switch to it (eg if statement based on Magisk version), it would probably be pretty simple to modify the path it is built into. And I am working on new release right now.


    My app above, uses a GUI, so it is pretty easy apart from having to use the GUI again if you clean flash your ROMS. But you can save off the scripts to automate it if you do it repeatedly and dont like to click.

    Regarding Viper, if its the SEPolicy changes that are questionable, then switching to permissive should make that irrelevant (ie test the theory); for testing only of course. There are many methods used to install viper. I have had the best luck on A11 using the attached Magisk zip; note, I did not build it, and it defaults to boot permissive, which can be easily changed with a delay in the service script. It also has a few other very minor things not quite neat, but it has worked for me and others.


    TeMeFI does. It looks under (all under system) app, priv-app, product, product/priv-app, vendor, vendor/priv-app

    Im back on full magisk (Alpha) again (with riru_momohider & config settings) and back on my favourite ROM which allows my banking apps, Google Pay AND Samsung Pay to work...i just needed sanity again :) Its still weird to me that switching ROM's no matter what you do with magisk/riru etc, the ROM itself can sometimes give you up to root checking apps via build.props or kernel, or not executing magisk properly...i have one ROM thats safe and lets me use everything...

    Next time im fiddling with magisk lite ill give TeMeFi a crack for the debloat function - you just know im slowly finding my way around it, even after a year of pokery...and you just keep adding stuff ...though not a chorus line of bananas :) I regularly use your Doze setting btw, and the graphs youve added are killer

    I use the same viper zip for 11....it doesnt work on magisk lite at all :(

    About the Magisk Lite and its /data/adb/lite_modules folder and the needed manual renaming of /data/adb/modules_update to/data/adb/lite_modules_update (when installing a module) please see my previous post:

    Yeah that doesnt apply for viper under magisk lite for the viper zip i use (as DiamondJohn has also linked above)


    Basically im happy for the moment, all my bank apps, GPay and SPay are working (for the moment)
     
    Last edited:

    J.Michael

    Senior Member
    Jan 20, 2018
    698
    480
    Samsung Galaxy Tab A series
    Of course I already did so. Issue persists. Flashing Magisk patched boot.img leads to a non booting device.
    Once you flash stock firmware, I do not think you need to worry about "Magisk" still being installed. I think you *do* need to worry about having one or more copies of "Magisk Manager app" installed. Make sure you uninstall all Magisk Manager apps, by any name, before installing a new version of Magisk Manager.

    Have you been making a new patched boot image after each time you installed a new Magisk Manager app?
     

    klemi71

    Senior Member
    Jun 6, 2018
    159
    40
    Google Pixel 3
    Once you flash stock firmware, I do not think you need to worry about "Magisk" still being installed. I think you *do* need to worry about having one or more copies of "Magisk Manager app" installed. Make sure you uninstall all Magisk Manager apps, by any name, before installing a new version of Magisk Manager.

    Have you been making a new patched boot image after each time you installed a new Magisk Manager app?
    There was only one version (canary) installed. I used "settings" and Magisk hide in daily use, but reverted this before updating. Modules were disabled. Only thing that may be tricky is pixeltweakshelper-module as it modifies systemUI. Though I used safe mode to disable modules. When Magisk Manager was updated, I updated Magisk in place as recommended. After monthly ROM updates I patch the according boot.imp and flash it. This is the first time this doesn't work.
    Nevertheless I'd really like to flash renamed (APK to zip) apkdebug.apk as uninstaller and begin from scratch without remains of settings, ...
    But root is gone and there's no working custom recovery for Pixel 3 Android 11. Can this be done using fastboot flash?
     
    Last edited:

    J.Michael

    Senior Member
    Jan 20, 2018
    698
    480
    Samsung Galaxy Tab A series
    There was only one version (canary) installed. I used "settings" and Magisk hide in daily use, but reverted this before updating. Modules were disabled. Only thing that may be tricky is pixeltweakshelper-module as it modifies systemUI. Though I used safe mode to disable modules. When Magisk Manager was updated, I updated Magisk in place as recommended. After monthly ROM updates I patch the according boot.imp and flash it. This is the first time this doesn't work.
    Nevertheless I'd really like to flash renamed (APK to zip) apkdebug.apk as uninstaller and begin from scratch without remains of settings, ...
    But root is gone and there's no working custom recovery for Pixel 3 Android 11. Can this be done using fastboot flash?
    I'm confused about the order of these steps. With a patched boot image flashed, when you cannot boot normally, are you able to boot to Safe Mode?

    I don't think you can flash a zip file other than with TWRP. You can look into the zip file and maybe make sense of what it does, but you probably won't be able to manually reproduce the steps of the uninstall script without root privilege.
     

    klemi71

    Senior Member
    Jun 6, 2018
    159
    40
    Google Pixel 3
    I'm confused about the order of these steps. With a patched boot image flashed, when you cannot boot normally, are you able to boot to Safe Mode?

    I don't think you can flash a zip file other than with TWRP. You can look into the zip file and maybe make sense of what it does, but you probably won't be able to manually reproduce the steps of the uninstall script without root privilege.
    I described it in detail earlier, sorry.
    What could be really helpful is a working url for creating a user defined channel for Magisk 20.4 inside Magisk Manager. I can download the zip but there is no way to flash it. Next time I'll keep working Magisk_patched.img for sure, but at the moment I have to create one.
     

    pndwal

    Senior Member
    Jun 23, 2016
    2,393
    1,675
    Sydney
    Xiaomi Redmi Note 7
    I described it in detail earlier, sorry.
    What could be really helpful is a working url for creating a user defined channel for Magisk 20.4 inside Magisk Manager. I can download the zip but there is no way to flash it. Next time I'll keep working Magisk_patched.img for sure, but at the moment I have to create one.
    Stable json for 20.4 is here:
    https://github.com/topjohnwu/magisk_files/tree/63555595ffa9b079f3a411dd2c00a80a3d985ccc

    Need address for raw file:
    https://raw.githubusercontent.com/t...5ffa9b079f3a411dd2c00a80a3d985ccc/stable.json

    This address and path should work in custom Channel, but I'd assume newer App does not have full backward compatibility with older Magisk in any case. (I'm fairly sure you'll need to enter json path in old Manager Custom Channel setting; newer App only uses channel setting to update/change App). I do know 'Hide The Magisk App' option is incompatible with older method for instance.

    Incidentally, issue with duplicated App/Manager arises from failing to Unhide/Restore App/Manager in App settings before updating, NOT reverting MagiskHide which is something quite different.

    If you didn't and you had hidden app (often named simply "Settings", etc), you will necessarily see Magisk Installed: N/A, and have other issues. You'll likely need to find it in device settings App list, and uninstall.

    Nb. This is expected coming from incompatible pre 21406, but in practice it is an issue even with current builds:
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85078241

    Hope it helps. 🤠 PW
     
    Last edited:
    • Like
    Reactions: J.Michael

    pndwal

    Senior Member
    Jun 23, 2016
    2,393
    1,675
    Sydney
    Xiaomi Redmi Note 7
    Nevertheless I'd really like to flash renamed (APK to zip) apkdebug.apk as uninstaller and begin from scratch without remains of settings, ...
    But root is gone and there's no working custom recovery for Pixel 3 Android 11. Can this be done using fastboot flash?
    Uninstall zip and uninstall from app are practically identical, an if inaccessible (no TWRP, no root, etc), are not entirely necessary anyway.

    Flashing clean boot image completely removes Magisk (mask).

    Settings, modules etc are all stored in /data/adb, and boot image copies at /data/magisk_backup_xxx. (Modules etc are only overlayed over system at boot time).

    These can be removed manually for full cleanup, but do no harm without root, and are accessible / can be modified when root is restored in any case.

    Nb. Neither Manual removal or App/zip Uninstall methods ensure complete reversal of changes made by modules. These should be properly uninstalled from Modules list (and any apps they set up uninstalled) prior to Magisk un-installation.

    Without installed TWRP or root, you may be able to load a TWRP in memory (fastboot boot only), or use ADB to remove these files, or full data wipe (Factory Reset) / Clean ROM flash will do it. PW
     

    J.Michael

    Senior Member
    Jan 20, 2018
    698
    480
    Samsung Galaxy Tab A series
    I described it in detail earlier, sorry.
    What could be really helpful is a working url for creating a user defined channel for Magisk 20.4 inside Magisk Manager. I can download the zip but there is no way to flash it. Next time I'll keep working Magisk_patched.img for sure, but at the moment I have to create one.
    If the zip you downloaded was https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip, there is a "magisk.apk" under "common". That might be the apk you should install under Android. Then, maybe if you set it to use the Custom update channel, but do not give it a working URL, it will be willing to patch an image for you. (All of this is conjecture, with no basis in personal experience.)
     

    klemi71

    Senior Member
    Jun 6, 2018
    159
    40
    Google Pixel 3
    If the zip you downloaded was https://github.com/topjohnwu/Magisk/releases/download/v20.4/Magisk-v20.4.zip, there is a "magisk.apk" under "common". That might be the apk you should install under Android. Then, maybe if you set it to use the Custom update channel, but do not give it a working URL, it will be willing to patch an image for you. (All of this is conjecture, with no basis in personal experience.)
    I already did so, but in this case installation (to patch a file) isn't available. The only option without valid url seems to be updating manager and using v22.1 that doesn't work. In this thread is described how to create user defined URLs by yourself, but I didn't manage this.
     

    J.Michael

    Senior Member
    Jan 20, 2018
    698
    480
    Samsung Galaxy Tab A series
    I already did so, but in this case installation (to patch a file) isn't available. The only option without valid url seems to be updating manager and using v22.1 that doesn't work. In this thread is described how to create user defined URLs by yourself, but I didn't manage this.
    Maybe if you post details of how you tried to provide a custom channel URL, and how it failed, someone could help.

    Did you copy a JSON file, edit the URLs in it, and put it on a web server?
     

    Top Liked Posts

    • 1
      Is there an advantage in utilizing Magisk Lite versus other versions of Magisk?
      Not for most: It breaks normal use of modules for example. Seems its sole purpose / only advantage is for those desperate to pass SafetyNet for bank apps detecting "root" through isolated processes, or interested in testing MagiskHide with this ability.
      https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85103873

      Alpha Magisk from same dev is best bet for those simply wanting newer updates / fixed at present:
      https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85103975 PW
      1
      Is there an advantage in utilizing Magisk Lite versus other versions of Magisk?
      I have never installed it nor used it or even followed what the heck it is. However, it looks like the direction Magisk will be heading in, in the future. The advantage in my eyes is best to find any roadblocks and soln now, before they become a sticking point.
      1
      The lastest magisk zip or boot.img patch ia not working on samsung TAB A SM-T285 (Lollipop)
      I flash the correct zip file so many time and it flash the success on TWRP but after reboot the manager showes Installed : N/A. Then I read the magisk blog instructions and patch the boot img file but the result is same. The only thing is working the older version of magisk but I want to up to date so please fix this bug or announce a new method for samsung lollipop version.
      I dont know your device, however, I have owned older devices, and on those devices, I cannot run the latest software. Maybe your device running lollipop is just not ready for running the latest of software in other regards. Lollipop is getting old.
    • 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
      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
      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
    • 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