Magisk General Support / Discussion

Search This thread

C5Longhorn

Senior Member
Jan 1, 2012
354
50
Amazon Fire HD 8 and HD 10
For going back to an older version of Stable or Beta Magisk versions, you must use:
- Magisk Manager Settings, switch Update Channel to Custom
- Open Custom Channel and paste in the URL for json file for coresponding to that older version of Magisk

Generaly, it does not matrer which Magisk Mamager version you use (don't use Canary Manager because the latest is integrated with Magisk and it has different architecture)

Switching to the old Manager 7.5.1 or so will not help you to install the old version of Magisk. Only the Custom channel will do

To obtain the URL for the json file corresponding to the old, Magisk, e.g. v20.3, follow through the attached screenshots:
- Open in browser: (mobile phone, I use Chrome):
- It will show you the latest stable.json
- Click on History
- Scroll down to e.g. Magisk v20.3 and open
- It will show you the difference in stable.json between Magisk v20.2 (preceeding) and that v20.3
- Click on three dots and take View file for that second stable.jsom correspinding to the 'new' v20.3
- Now you are looking to the stable.json for v20.3, long press on Raw and take Copy link address

Then paste that URL to the Custom Channel field in Magisk Manager Settings, go back and on the main screen Magisk Manager will now show that you e.g. have Magisk v21 installed (or Magisk not installed) but that 'latest available' is v20.3, following the json file you just have put to the Custom channel

And Install Magisk will install (e.g. will Patch) that old v20.3, not the really/currently latest Magisk

Later if/when you want to switch to the up-to-date Magisk version, switch Custom Channel back to Stable and Install that newest Magisk version



This worked. Thank you for taking the time to post. I learned something new and copied it for later.
 
  • Like
Reactions: galaxys and zgfg

zgfg

Senior Member
  • Oct 10, 2016
    5,322
    2,627
    This worked. Thank you for taking the time to post. I learned something new and copied it for later.
    Sorry, I didn't follow all your story, can you please summarize:

    - You have Huawei (some model)
    - EMUI 5.1 firmware (even if you use custom ROM, you patch boot/ramdisk/recoveey image corresponding to your last stock version because custom ROM affects only system)
    - Latest Stable and Canary Magisk does not work (no root or bootloop?)
    - Which older version of Magisk worked for you?
     

    2_i

    Member
    May 22, 2013
    30
    3
    I do not know who yo turn to with this, but I have second Moto Z2 Play phone that does not boot after the last update to Magisk. Both phones worked for several years rooted. The symptom is that the phone just does not start with the Power Button pressed. The boot into Bootloader/recovery still works, but the boot into the system goes to nowhere. One of the phones had Nandroid backups, so I seem to be getting to somewhere there, but the other is now destined for trash. The system was Android 7.1.1 in my memory.
     

    C5Longhorn

    Senior Member
    Jan 1, 2012
    354
    50
    Amazon Fire HD 8 and HD 10
    Sorry, I didn't follow all your story, can you please summarize:

    - You have Huawei (some model) Mediapad m5 Tablet, came out in 2018
    - EMUI 5.1 firmware (even if you use custom ROM, you patch boot/ramdisk/recoveey image corresponding to your last stock version because custom ROM affects only system) EMUI Version 8 (Android 8.0); USA model tablets never received the Upgrade to 9 or 9.1
    - Latest Stable and Canary Magisk does not work (no root or bootloop?) Latest stable 21.4 does not achieve root on the tablet, no issues other than no root.
    - Which older version of Magisk worked for you? I used 20.4
     
    • Like
    Reactions: zgfg

    2_i

    Member
    May 22, 2013
    30
    3
    I do not know who yo turn to with this, but I have second Moto Z2 Play phone that does not boot after the last update to Magisk. Both phones worked for several years rooted. The symptom is that the phone just does not start with the Power Button pressed. The boot into Bootloader/recovery still works, but the boot into the system goes to nowhere. One of the phones had Nandroid backups, so I seem to be getting to somewhere there, but the other is now destined for trash. The system was Android 7.1.1 in my memory.

    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.
     

    IlConsiglieri

    Member
    Nov 21, 2013
    11
    2
    Den Bosch
    Could be a bug... You'd need to collect more info to say for sure though:
    https://www.didgeridoohan.com/magisk/MagiskHelp


    Might be that the app in question doesn't properly ask for root permission and needs an update.


    Perfectly normal. You have the option to install/patch an image again, if needed. If there's an update to Magisk or the app, those buttons will change to "Update".

    Hello,

    I have sent the dev of the app my magisk log. I will update his findings here. It concerns the mobile tracker free app.

    mobile-tracker-free.com
     

    Didgeridoohan

    Senior Moderator / Dev Committee / Dev Relations
    Staff member
    May 31, 2012
    11,665
    12,478
    Gothenburg
    Google Nexus 4
    Nexus 6
    Does it do something other then described on the website?

    Apart from the shady nature of tracking apps, there's just no way to know what it does once it has full access to the device (without some serious analysing)... But this is getting off-topic, so if this is something you'd like to discuss further you can open a new thread in an appropriate forum or contact me in a private conversation.
     
    • Like
    Reactions: galaxys and ipdev

    vinokirk

    Senior Member
  • Mar 30, 2008
    2,196
    240
    England
    Hi all, i've just updated Magisk on my Note 10+ 5G, now it wont boot. It gest stuck on the 'Samsung Note 10+ 5G' screen.
    HELP!
    I can get it into TWRP. Has Magisk written a bad bootloader or something?
     

    Didgeridoohan

    Senior Moderator / Dev Committee / Dev Relations
    Staff member
    May 31, 2012
    11,665
    12,478
    Gothenburg
    Google Nexus 4
    Nexus 6
    Hi all, i've just updated Magisk on my Note 10+ 5G, now it wont boot. It gest stuck on the 'Samsung Note 10+ 5G' screen.
    HELP!
    I can get it into TWRP. Has Magisk written a bad bootloader or something?

    Magisk does not touch the booloader, only the boot/recovery image.

    You've got TWRP, so in theory you should be able to fix things. Restoring the stock boot image, either manually or by using the Magisk uninstaller (you can find it on Github), would be a first step. After that you can try installing the same Magisk version again (sometimes updating Magisk to a newer version can cause issues, possibly caused by Magisk internals or modules, that you can fix by doing a clean installation). If that still doesn't work, you can always try with a previous release of Magisk (again, found on Github).

    If you've still got issues after all that it's usually a good idea to take a look in your devices forum. That's where you find the most amount of people that know your devices particular ins and outs.

    Lastly, if it turns out to be an incompatibility between your device and current releases of Magisk, it's always appreciated if relevant information regarding hunting this down is provided in the proper manner as a Github issue.
     
    • Like
    Reactions: vinokirk

    Bobby_Turboto

    New member
    Feb 1, 2021
    3
    1
    Hey there,

    I'm rooting with Magisk for the first time and I followed this guide for the OnePlus Nord:

    I do not have wifi, I can't call, my phone is crashing and restarting after every 2 min use.

    I thought that I needed to restore it back to OxygenOS and I used this guide:

    After it didn't work I simply tried https://www.xda-developers.com/how-to-root-unlock-bootloader-oneplus-nord-magisk/ (the first guide) in order to root again but without any result.

    Is there a way to restore my phone without any problems?

    Model AC2003
    Oxygen OS 10.5.10.AC01BA
     
    Last edited:

    Uluru25

    Senior Member
    Nov 27, 2016
    105
    30
    Samsung Galaxy A6
    Redmi Note 8
    Switching to the older version of Magisk


    For going back to an older version of Stable or Beta Magisk versions, you must use:
    - Magisk Manager Settings, switch Update Channel to Custom
    - Open Custom Channel and paste in the URL for json file for coresponding to that older version of Magisk

    Generaly, it does not matrer which Magisk Mamager version you use (don't use Canary Manager because the latest is integrated with Magisk and it has different architecture)

    Switching to the old Manager 7.5.1 or so will not help you to install the old version of Magisk. Only the Custom channel will do

    To obtain the URL for the json file corresponding to the old, Magisk, e.g. v20.3, follow through the attached screenshots:
    - Open in browser: (mobile phone, I use Chrome):
    - It will show you the latest stable.json
    - Click on History
    - Scroll down to e.g. Magisk v20.3 and open
    - It will show you the difference in stable.json between Magisk v20.2 (preceeding) and that v20.3
    - Click on three dots and take View file for that second stable.jsom correspinding to the 'new' v20.3
    - Now you are looking to the stable.json for v20.3, long press on Raw and take Copy link address

    Then paste that URL to the Custom Channel field in Magisk Manager Settings, go back and on the main screen Magisk Manager will now show that you e.g. have Magisk v21 installed (or Magisk not installed) but that 'latest available' is v20.3, following the json file you just have put to the Custom channel

    And Install Magisk will install (e.g. will Patch) that old v20.3, not the really/currently latest Magisk

    Later if/when you want to switch to the up-to-date Magisk version, switch Custom Channel back to Stable and Install that newest Magisk version
    Dear ZGFG, fortunately not having needed to follow your valuable guidance, I nevertheless assume it could be very helpful for a plenty of guys. But it might be hard to find this guidance within this very very big thread. Maybe it is possible that you open a new thread for this issue and put a link to the postings here?
     
    • Like
    Reactions: deserted and zgfg

    zgfg

    Senior Member
  • Oct 10, 2016
    5,322
    2,627
    Dear ZGFG, fortunately not having needed to follow your valuable guidance, I nevertheless assume it could be very helpful for a plenty of guys. But it might b
    Dear ZGFG, fortunately not having needed to follow your valuable guide. But it might be hard to find this guidance within this very very big thread. Maybe it is possible that you open a new thread for this issue and put a link to the postings here?
    Thanks. That special thread might also get 'lost'.
    I'd suggest if @Didgeridoohan could add a section to the Magisk Wiki 🤓
     
    • Like
    Reactions: Uluru25

    Taranis01

    Senior Member
    May 22, 2012
    88
    23
    Xiaomi Poco X3 NFC
    Hey, I am missing the SafetyNet Check button in Magisk Manager. Can't find any information about why that would be the case. Do you have any idea?

    ByjZW9t.png


    I am using an old Samsung Galaxy S6 with LineageOS 17 (Android 10). Installed Magisk by flashing in TWRP.
     

    Didgeridoohan

    Senior Moderator / Dev Committee / Dev Relations
    Staff member
    May 31, 2012
    11,665
    12,478
    Gothenburg
    Google Nexus 4
    Nexus 6
    Hey, I am missing the SafetyNet Check button in Magisk Manager. Can't find any information about why that would be the case. Do you have any idea?

    ByjZW9t.png


    I am using an old Samsung Galaxy S6 with LineageOS 17 (Android 10). Installed Magisk by flashing in TWRP.

    My first guess is that you don't have any Gapps installed. SafetyNet is Google's and need their infrastructure...
     
    • Like
    Reactions: Taranis01

    Top Liked Posts

    • 5
      Some early news

      Latest @vvb2060 Magisk Alpha build (June 23, 2021) change log:​

      Chinese Translated:

      alpha update log​

      Magisk (1eb83ad8-alpha)​

      • Based on 1eb83ad8, please refer to the upstream update log for related modifications
      • Properly process any data from magiskd
      • Support SharedUserId
      • Delete the backup file after restoring the boot image
      • Built-in current version update log
      • Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline
      • Support bootimg v4 format
      • Support bootconfig
      • Detect /data/adb/magisk/ not updated and prompt to repair
      Edit:
      Following are new commits:
      • Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting
      • Fix that it cannot be flashed in some TWRP
      • Modify the search order of the module sepolicy location and fix the problem that some devices do not load the module sepolicy
      • Listen to the PACKAGE_FULLY_REMOVED broadcast to remove completely uninstalled apps from magiskhide
      • Display the modal waiting pop-up window when hiding/restore the Magisk application
      https://github.com/vvb2060/Magisk/b...af4f3d37e69/app/src/main/res/raw/changelog.md

      My earlier notes:
      https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85098469

      Current notes:

      It seems this build is only partially rolled out 3hrs ago, and magisk_files repo is not yet updated with package files.

      I am not expecting Alpha build users will see Update button notice in Magisk App for this build (as with last build) as Version has (again) NOT been changed from "1eb83ad8-alpha". Again, I'm not sure if this is intended.

      I'll be sure to update here when package files have been uploaded.

      Edit: Package already available on Telegram:
      https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85229385

      Interestingly, in Magisk Documentation, @vvb2060 has updated "Internal Details" (Delete wrong info) and "Deployment"
      (Add exploit conditions).
      https://github.com/vvb2060/Magisk/tree/alpha/docs

      😛 PW
      5
      Some early news

      Nb. It seems Lite builds will likely be of interest only to those wanting basic superuser privileges, and a way to hide root from bank apps that detect isolated processes, at least at this stage:

      Latest @vvb2060 Magisk Lite build (June 23, 2021) change log:​

      Chinese Translated:

      Magisk Lite​

      In Magisk in the whitelist mode, all applications are hidden by default, and only the applications ticked in Hide can obtain super user permissions. adb shell automatically has super user privileges. Module function is not available.

      'magiskhide add UID package name' to add super-user application
      'magiskhide rm UID package name' to remove super-user application
      'magiskhide ls' lists the super-user applications

      Magisk (1eb83ad8-lite)​

      • Based on 1eb83ad8, please refer to the upstream update log for related modifications
      • Properly process any data from magiskd
      • Support SharedUserId
      • Delete the backup file after restoring the boot image
      • Built-in current version update log
      • Use the local version when the stub cannot be downloaded, now Magisk can be used completely offline
      • Support bootimg v4 format
      • Support bootconfig
      • Detect /data/adb/magisk/ not updated and prompt to repair
      Edit:
      Following are new commits:
      • Remove the disabled and pending deletion marks when upgrading the module, and it is not allowed to mark as pending deletion before restarting
      • Fix that it cannot be flashed in some TWRP
      • Modify the search order of the module sepolicy location and fix the problem that some devices do not load the module sepolicy
      • Display the modal waiting pop-up window when hiding/restore the Magisk application
      https://github.com/vvb2060/Magisk/blob/lite/app/src/main/res/raw/changelog.md

      My earlier notes:
      https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85082149

      Current notes:

      This seems to be only partially rolled out 1hr ago, and magisk_files repo is not yet updated with package files.

      I'll be sure to update here when package files have been uploaded.

      😛 PW
      2
      Magisk Alpha

      Ok, I've updated mine.

      All went fine for me.

      Don't expect 'Update' notice in App as mentioned, even for Magisk (mask) after App update as version has (again) NOT been changed from "1eb83ad8-alpha". Again, I'm not sure if this is intended.

      After App update, you will notice different Release Notes Changelog in Chinese for Install Magisk (mask) and Install App. Expect Install App Changelog to be updated when release package (plus json) is pushed to GitHub repository.

      At present, package file is still not pushed to GitHub repository.

      I now understand this is often released earlier to Magisk Alpha Telegram group, and sure enough it's there! (It seems Chinese community here are more aware / informed of these builds than XDA community):
      https://t.me/magiskalpha
      Web based preview:
      https://t.me/s/magiskalpha

      Nb. See this for Devs notes also.

      Nb.2. In Chrome, web based preview can be translated into English.

      Magisk Lite

      For anyone interested in this (those wanting basic superuser privileges, and a way to hide root from bank apps that detect isolated processes), this is released to Magisk Lite Telegram group also, but is unavailable as yet. 😕 :
      https://t.me/magisklite
      Web based preview:
      https://t.me/s/magisklite

      Nb. See this for Devs notes / working theory / difference with respect to standard Alpha / technical details re use, functionality etc.

      Eg. Dec 4 build "restores the module function and can install a separate lite module.
      Requirement: After the boot is complete, zygote and its child processes will no longer read any files mounted by the module.
      (Otherwise, the mobile phone will have various inexplicable problems.)"

      👍 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
      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
      That is the most wrong statement. If Google didn't has no issues with having root, there would not magsikhide. Just that statement alone conflicts with itself. MagiskHide hides root... Google has a problem with hiding root and not root, then why hide it? Why is there basic attention and cts profile check? Now a hardware check? Root, on Android is what they don't want, or else there would be no need for a modified kernel, we would all have root like on Linux desktop... Any terminal on desktop has root instantly, Android doesn't.. They did pretty damn good job of taking something away they wanted to have all along right? Wow.
      This whole discussion took a bit of a turn, and I'm not gonna get further into that. But, you might want to reread what I said again: "Google has no interest in preventing root". That statement doesn't say anything on how Google think about root in security terms (and I'm talking about the Google security team here, which John now is a part of).

      We're talking about different things, I believe...

      You're talking about the security aspect, which Google cracks down on (since generally, rooting a device compromises the systems security), and I'm talking about just being able to root your device regardless of if SafetyNet triggers or not.

      If they wanted to, Google could make it so much harder (impossible?) to root your Android device... From statements I've seen from Google security team members, that's not on their agenda. But of course, beefing up the security on Android in general might have the unfortunate side effect of accomplishing the same thing.
      7
      Oh that wasn't the only thing said. Other tweets are deleted too. You really think there isn't a conflict of interest now? You don't think Google knew what they were doing? Think about it. They hire the one guy that still has an app bypassing their security, you dont think they did this without knowing they were gonna shutdown Magisk? I think John thought he was going to be able to, right when I saw that I knew. Guarantee when they hired him he signed work agreements that stop him from working on magisk. Also his Twitter no anything since being hired. I know he has said more behind the scenes, but the end is near, Google will put it like this, paycheck or Magisk? Which do you think he will choose? Tank a possible career for a huge company, or save magisk for a couple thousand people for free? It isn't rocket science.

      The only conflict of interest would be with MagiskHide. Google have stated several times that they have no interest in preventing root...

      And the future of MagiskHide would have been with zygote injection anyway, so it would be perfectly suited for an Xposed/EdXposed/LSposed project if it no longer can be a part of Magisk.

      But all of this is speculation before we hear anything from John...
      7
      FWIW, as there is no news of updated Magisk from John Wu, I'm now running Alpha Magisk and Magisk App from dev @vvb2060 (Nangong Xueshan).

      Seems his App maintains connection to standard Stable / Beta / Canary channels from topjohnwu, but adds his Alpha (Bleeding edge) channel:
      https://github.com/vvb2060/magisk_files/tree/alpha

      Click View code, Download / install app-release.apk 👍

      Screenshot_2021-05-29-17-24-43-651_com.topjohnwu.magisk.jpg


      No problems running this Alpha so far. 👍

      - Nb. Unhide Magisk App if changing to this. Conflict with hidden Apps are still occurring.

      Alpha adds new / experimental commits. Some of these already have pull requests in John's Magisk GitHub.

      Nb. John Wu recently changed his description of debug Canary builds from 'Bleeding Edge' to 'Cutting Edge'...

      WARNING

      If you move to Nangong Xueshan's Alpha, my advice is to consider yourself on the Bleeding Edge again... and to understand what this means!

      Changelog for Alpha, next post. 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