Magisk General Support / Discussion

Search This thread

pndwal

Senior Member
Jun 23, 2016
2,397
1,683
Sydney
Xiaomi Redmi Note 7
hi folks,
i made a magiskhide and the icon disapeared from screen for whatever reason. so i installed magisk v23. i'm not asked for root access if i request it by any app. two apps have root access so far, but i'm not able to add more now. i made some attempts to remove magiskhide from my phone, but all not succeeded.
1. flash stock boot.img
2. upgrade stock firmware to newer version
3. install magisk v23, flashed new boot.img, magisk app working but at magisk start screen there's still "n/a" at installed info.
4. magiskhide is still there, because my two apps have still root access (qick disable & qick boot app)
5. i have no root access to terminal/shell or filemenager (that's what i wanted to add)
so how can i get rid of magiskhide? or get access to old magiskhide?
Are you now trying to remove Magisk root? (MagiskHide is just a cloaking feature).

Or do you mean trying to UnHide (restore) Magisk Manager / App to remove conflicts? (This is different from MagiskHide also.)

I'm guessing you mean the latter, but I'm confused by 3) '... flashed new boot.img'. Did you mean Magisk-patched boot image?

Still, sounds like this is your problem:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85024493

Nb. If by icon that has 'disappeared from screen' you mean hidden / renamed Magisk Manager and you can't locate it, go to Settings, Manage apps, and go through whole list till you remember assigned name / find it / delete it.

If this is not the problem, please describe it properly, and give Model / OS details, and Ramdisk / SAR / A/B status. PW
 
Last edited:

Danny94

Senior Member
Feb 11, 2012
792
158
Merano
Please confirm that you have wiped bank App's data (AFTER selecting it in MagiskHide list and rebooting), to clear any cached flags for various indicators of 'modified environment'.

Nb. You'll need to do wipe each time you test, both to allow for successful detection bypass, and to ensure error results are current - not cached flags from previous triggers.

You could try this w/ cache only, but likely data wipe is needed, and you will need to restore any lost settings.

Also, you may want to try removing Magisk App as suggested (you can uninstall / Install this at will without losing any settings or modules) if detection triggers errors again, but clearing data first will ensure result will be current with that also.

Lesson here is you may actually solve the basic problem and never know it if you fail to wipe apps data with each new attempt! PW
Thanks, yeah the problem is i need to go physically to my bank each time i wipe data and restoring data from titanium does not work.

I aswell tried to clone the app with island, did not work.

I gona change my bank anyway now, no sense messing around with those. Other people in comment section have reported they got problems aswell and werent rooted and my dad had to buy a new phone because the old one didnt worked. Im sure they lost already a lot customers because they lock people to this app which doesnt work properly.
 
  • Like
Reactions: J.Michael

pndwal

Senior Member
Jun 23, 2016
2,397
1,683
Sydney
Xiaomi Redmi Note 7
Thanks, yeah the problem is i need to go physically to my bank each time i wipe data and restoring data from titanium does not work.

I aswell tried to clone the app with island, did not work.

I gona change my bank anyway now, no sense messing around with those.
Sure, but caching flags for detected 'root' (really means any 'modified environment') seems to be standard fare for bank apps even when no methods other than checking SafetyNet result (ie. Play Protect certification status - check PlayStore, Settings, About, Play Protect certification says 'Device is certified') are employed.

This means that when ANYTHING goes wrong, and a future bank app detects root, you will still need to be prepared to clear it's data to reset flags before any solution will work, and unless you do, you can't be sure if a fix works or not!
Other people in comment section have reported they got problems aswell and werent rooted and my dad had to buy a new phone because the old one didnt worked. Im sure they lost already a lot customers because they lock people to this app which doesnt work properly.
For those having root however, i's all part of the thrill of the chase using MagiskHide with security centric apps ... You will not always win!

John's been playing the game of Cat and Mouse for some time now. The mouse is still alive, but tiring fast... And we're mere fleas in the equation. 😁 PW
 
Last edited:
  • Like
Reactions: BillGoss

dlewando

Senior Member
Jan 4, 2011
331
108
Are you now trying to remove Magisk root? (MagiskHide is just a cloaking feature).

Or do you mean trying to UnHide (restore) Magisk Manager / App to remove conflicts? (This is different from MagiskHide also.)

I'm guessing you mean the latter, but I'm confused by 3) '... flashed new boot.img'. Did you mean Magisk-patched boot image?

Still, sounds like this is your problem:
https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85024493

Nb. If by icon that has 'disappeared from screen' you mean hidden / renamed Magisk Manager and you can't locate it, go to Settings, Manage apps, and go through whole list till you remember assigned name / find it / delete it.

If this is not the problem, please describe it properly, and give Model / OS details, and Ramdisk / SAR / A/B status. PW
yea, 3) is confusing :) i tried both. removing modified magisk .img by installing stock boot.img, which removes root. and also flashing modified magisk boot.img which gives me root back for both apps. also magiskhide is working for two apps (security token generating apps). these were only ideas to get back to a running magisk app.
after installing magisk app, the flashed magisk .img is not recordnized in magisk app (n/a). also i can not find any magiskhide app in settings/manage_apps (i'm also not remembering the hidden name, but scrolling slowly through all apps, there's no app with random characters). my goal is to get magisk app running that i'm able to use root for more apps.
thx fo your fast help btw!
device: google pixel 4a 5g
 
Last edited:
  • Like
Reactions: J.Michael

pndwal

Senior Member
Jun 23, 2016
2,397
1,683
Sydney
Xiaomi Redmi Note 7
yea, 3) is confusing :) i tried both. removing modified magisk .img by installing stock boot.img, which removes root. and also flashing modified magisk boot.img which gives me root back for both apps.
Ah, that's exactly as expected, not confusing. But you had only said you flashed new boot.img and still had root!
also magiskhide is working for two apps (security token generating apps). these were only ideas to get back to a running magisk app.
after installing magisk app, the flashed magisk .img is not recordnized in magisk app (n/a). also i can not find any magiskhide app in settings/manage_apps (i'm also not remembering the hidden name, but scrolling slowly through all apps, there's no app with random characters). my goal is to get magisk app running that i'm able to use root for more apps.
thx fo your fast help btw!
device: google pixel 4a 5g
My hunch is that you still have hidden Manager (I'm assuming issue started w/ move up from pre 22 series Magisk?) as all symptoms indicate this. Manager app will be what you named it, not random characters.

If not, aside from the known issue mentioned in my linked post, you could have this:
https://github.com/topjohnwu/Magisk/issues/4319
But you seem to have working SU... Have a look and compare symptoms anyway. Also possible you have a new edge case. PW
 
  • Like
Reactions: J.Michael

martyfender

Senior Member
Mar 9, 2017
3,158
1,675
Indianapolis, IN
yea, 3) is confusing :) i tried both. removing modified magisk .img by installing stock boot.img, which removes root. and also flashing modified magisk boot.img which gives me root back for both apps. also magiskhide is working for two apps (security token generating apps). these were only ideas to get back to a running magisk app.
after installing magisk app, the flashed magisk .img is not recordnized in magisk app (n/a). also i can not find any magiskhide app in settings/manage_apps (i'm also not remembering the hidden name, but scrolling slowly through all apps, there's no app with random characters). my goal is to get magisk app running that i'm able to use root for more apps.
thx fo your fast help btw!
device: google pixel 4a 5g
On both my Andrioid 6 and 9 devices, the hidden Magisk Manager is named Settings, with the generic Android icon, as I don't change its name when hiding it. In older versions of Magisk it was named Manager when hidden, I believe.
 

dlewando

Senior Member
Jan 4, 2011
331
108
On both my Andrioid 6 and 9 devices, the hidden Magisk Manager is named Settings, with the generic Android icon, as I don't change its name when hiding it. In older versions of Magisk it was named Manager when hidden, I believe.
thx 4 the hint. there's a "settings" with generic android-icon. i disabled it, but still root is hidden. maybe on android 11 it's renamed different? i'm thinking about installing lineage over my pixel stock. this should remove all system modifications.
 

HippoMan

Senior Member
May 5, 2009
1,714
550
Hippoland
From what I can see it's detecting the Magisk app, even when repackaged and hidden. Seems to be more and more common... Solution, for now: freeze or uninstall the Magisk app when you need to use Raiffeisen.

Edit: if freezing uninstalling works you can very likely use an app like Island or Shelter (open source, yay) to put the app in a work profile to prevent it from detecting other apps.

I am having a similar problem with the Chase banking app. I tried running it in Shelter, but the app still manages to detect root. Even when running inside of Shelter, the app says the following when I try to access a number of features:
For your security, this feature is unavailable on devices that have been "rooted" or contain malware. Read our Security FAQ to use this feature.

Magisk is not running in the shelter. And outside of the shelter, the Chase app is hidden in Magisk 23.0

Chase and some other banks are going beyond SafetyNet and other tests. Luckily, the Chase IT people are not very smart, and all of the features that I cannot access via the Chase Android app are available when I access my account via the Chase web site from my Android device. This renders all of their so-called "security" useless.

The following is what I did, and it might work for some other banks, as well:
* Install a browser besides the standard Android browser (I chose Dolphin)
* Configure it so that its user agent string is the same one as the one that is used by your desktop browser (not all Android browsers allow this)
* Also configure it so that the start page for that browser is that bank's normal web site

This allows me to log into my bank's web site without all the Android-root-related restrictions.

PS: I used my "Home app" (Nova, in my case) to set the icon of this browser app to be the Chase app's icon, and I changed the title of that app on the screen to "Chase Alternate".
 
Last edited:

J.Michael

Senior Member
Jan 20, 2018
701
491
Samsung Galaxy Tab A series
thx 4 the hint. there's a "settings" with generic android-icon. i disabled it, but still root is hidden. maybe on android 11 it's renamed different? i'm thinking about installing lineage over my pixel stock. this should remove all system modifications.
If you "disabled" it, then it wasn't Magisk: system apps have a "Disable" option, non-system apps have an "Uninstall" option. (I assume you went to "App info" from the app icon in the Apps drawer. Is there an entry in App info for "details"?)
 

ipdev

Recognized Contributor
  • Feb 14, 2016
    1,362
    1
    1,532
    Google Nexus 10
    Nexus 7 (2013)
    thx 4 the hint. there's a "settings" with generic android-icon. i disabled it, but still root is hidden. maybe on android 11 it's renamed different? i'm thinking about installing lineage over my pixel stock. this should remove all system modifications.
    Just checked on my Pixel 3aXL (Android 11)
    Default name to Hide the Magisk app is Settings

    Take a look at the app info. (package name)
    com.android.settings is the device settings app.
    In my case, ziqfexf.wfukfetecw is the hidden Magisk app.

    Cheers. :cowboy:
     

    Attachments

    • Screenshot_20210516-151123_Settings.png
      Screenshot_20210516-151123_Settings.png
      134.5 KB · Views: 42
    • Screenshot_20210516-151110_Settings.png
      Screenshot_20210516-151110_Settings.png
      126.4 KB · Views: 43
    • Like
    Reactions: pndwal and HippoMan

    pndwal

    Senior Member
    Jun 23, 2016
    2,397
    1,683
    Sydney
    Xiaomi Redmi Note 7
    ... also i can not find any magiskhide app in settings/manage_apps (i'm also not remembering the hidden name, but scrolling slowly through all apps, there's no app with random characters)...
    Just checked on my Pixel 3aXL (Android 11)
    Default name to Hide the Magisk app is Settings

    Take a look at the app info. (package name)
    com.android.settings is the device settings app.
    In my case, ziqfexf.wfukfetecw is the hidden Magisk app.
    Ah yes; nice way to make distinction!

    App names are not random; they're what user sees generally.

    APK names are generally logical names too; android, com.android.xxx, com.miui.xxx, vendor.qti.xxx

    Magisk hidden app APK name IS random however; oor.xuuzw.xfa.j PW
     
    • Like
    Reactions: ipdev

    olexiiy

    Member
    Jun 1, 2016
    23
    5
    Hello.

    The situation happened with my mi 9t.
    Steps :
    Updated crDroid official from 21.4.12 to 21.5.10.
    Updated the firmware to 21.5.12
    Magisk 22005 to 23001
    Nikgapps to 21.5.14
    Cleared the cache

    Turned on the system, everything is ok.
    I made an android patches, I don't use magisk modules.
    Everything works well.

    After a few hours, without reboots, without other manipulations, gpay broken.

    I thought that I do mistake.

    Installed clean via miui from fastboot. The result is the same.
    I set up everything, it works. After a couple of hours, gpay brokes again, there is no certification, ctsProfile does not work.

    There is another phone with crDroid 6.17
    (Not k20 / mi9t), the software is the same. Magisk is the same. All OK.

    Which way to fix?
    Or are there any tips?
     
    • Like
    Reactions: J.Michael

    pndwal

    Senior Member
    Jun 23, 2016
    2,397
    1,683
    Sydney
    Xiaomi Redmi Note 7
    Hello.

    The situation happened with my mi 9t.
    Steps :
    Updated crDroid official from 21.4.12 to 21.5.10.
    Updated the firmware to 21.5.12
    Magisk 22005 to 23001
    Nikgapps to 21.5.14
    Cleared the cache

    Turned on the system, everything is ok.
    I made an android patches, I don't use magisk modules.
    Everything works well.

    After a few hours, without reboots, without other manipulations, gpay broken.

    I thought that I do mistake.

    Installed clean via miui from fastboot. The result is the same.
    I set up everything, it works. After a couple of hours, gpay brokes again, there is no certification, ctsProfile does not work.

    There is another phone with crDroid 6.17
    (Not k20 / mi9t), the software is the same. Magisk is the same. All OK.

    Which way to fix?
    Or are there any tips?
    I'm assuming you have full SafetyNet pass and Device is Certified PlayProtect result (check PlayStore, Settings, About) once again, and have cleared data in GPay to wipe cached flags before setting up cards etc again, especially if you had MagiskHide off at all, Uncertified device PlayProtect result, or root / insecure environment was detected by GPay.

    Also, have you "Set up a screen lock to use the Google Pay app" since updating OS? It's required by Google.

    Data / card info is also cleared by Google when screenlock is removed, even without opening Google Pay!
    https://forum.xda-developers.com/t/...agisk-discussion-thread.3906703/post-84758885

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

    olexiiy

    Member
    Jun 1, 2016
    23
    5
    I'm assuming you have full SafetyNet pass and Device is Certified PlayProtect result (check PlayStore, Settings, About) once again, and have cleared data in GPay to wipe cached flags before setting up cards etc again, especially if you had MagiskHide off at all, Uncertified device PlayProtect result, or root / insecure environment was detected by GPay.

    Also, have you "Set up a screen lock to use the Google Pay app" since updating OS? It's required...
    https://forum.xda-developers.com/t/...agisk-discussion-thread.3906703/post-84758885

    Hope it helps. PW
    Now I have clean instaled rom.

    Step:
    Install Rom
    Install Magisk 23001
    Install Gapps
    Turn on rom
    First setup and Set up a screen lock with pin
    Reboot phone
    Open magisk and hide
    Clean data for Google service and Play Market.
    Reboot phone.
    Everything worked, Gpay worked, SafetyNet passed.

    After a few hours SafetyNet and Gpay failed.
    With Gpay fails cetrification.

    There are screenshots with actual status.

    Also I can grab the log with adb.

    photo_2021-05-17_13-06-49.jpg
    photo_2021-05-17_13-03-37.jpg
    photo_2021-05-17_13-03-33 (2).jpg
    photo_2021-05-17_13-03-33.jpg
     
    Last edited:
    • Like
    Reactions: J.Michael

    pndwal

    Senior Member
    Jun 23, 2016
    2,397
    1,683
    Sydney
    Xiaomi Redmi Note 7
    Now I have clean instaled rom.

    Step:
    Install Rom
    Install Magisk 23001
    Install Gapps
    Turn on rom
    First setup and Set up a screen lock with pin
    Reboot phone
    Open magisk and hide
    Clean data for Google service and Play Market.
    Reboot phone.
    Everything worked, Gpay worked, SafetyNet passed.

    After a few hours SafetyNet and Gpay failed.
    With Gpay fails cetrification.

    There are screenshots with actual status.

    Also I can grab the log with adb.

    OK... Not sure why you hide root from PlayStore... Who does that? (Google Play Services only is default for GApps) Likely this is causing your issues.
    www.twitter.com/topjohnwu/status/1039528958289760256 PW
     
    • Like
    Reactions: J.Michael

    olexiiy

    Member
    Jun 1, 2016
    23
    5
    OK... Not sure why you hide root from PlayStore... Who does that? (Google Play Services only is default for GApps) Likely this is causing your issues.
    www.twitter.com/topjohnwu/status/1039528958289760256 PW
    I changed MagiskHide.
    Clean PlayMarket data.
    Reboot phone....
    and nothing changes.
    Trying to fix this last 3 day.
    Tricks and modules only repairs part of the functions.

    There is no complex solution to the problem. Everything used to work out of the box.
    And now dancing with a tambourine. No information on which side is causing the issues.
    In other forums people write about the same problem.


    photo_2021-05-17_15-37-42 (3).jpg
    photo_2021-05-17_15-37-42 (2).jpg
    photo_2021-05-17_15-37-42.jpg
     
    Last edited:

    Didgeridoohan

    Senior Moderator / Dev Committee / Dev Relations
    Staff member
    May 31, 2012
    11,643
    12,414
    Gothenburg
    Google Nexus 4
    Nexus 6
    • Like
    Reactions: J.Michael

    Top Liked Posts

    • 2
      Yeah sure in retrospect it was stupid..
      Thank you for your very detailed answer.

      I uninstalled the new installed Magisk manager from setttings -> ok
      In settings under all apps I can see the 'old' App which is just called 'Manager' and is stated as disabled -> ok

      One point is still not clear for me:
      What do do now? If I uninstall the 'Manager' App will I automatically get the old Magisk manager back? OR should I better use the adb command to reenable the renamed app?
      You can do either one

      If you uninstall, then just install again the newest Magisk app - you will not loose anything (modules, etc), just make sure that you enable MagiskHide again.
      You can also repackage then the newly installed Magisk app

      Otherwise, use the adb command to re-enable your old repackaged Magisk App or Mngr (depending how old it was)

      In the first case you assure that you would have the latest Magisk app.
      In the second case you may need to update (upon being re-enabled)!your Magisk app/mngr if you want (and that could possibly fail if you try to update from the repackaged app/mngr)

      I would go for the first option, and then also update the Magisk itself (unless you have some old device where Magisk update/installation might fail)

      Edit - maybe you have an option in Settings/Apps to enable the disabled/frozen old Magisk mngr/app, in that case you don't need to use adb command for the option (2)
      2
      You can do either one

      If you uninstall, then just install again the newest Magisk app - you will not loose anything (modules, etc), just make sure that you enable MagiskHide again.
      You can also repackage then the newly installed Magisk app

      Otherwise, use the adb command to re-enable your old repackaged Magisk App or Mngr (depending how old it was)

      In the first case you assure that you would have the latest Magisk app.
      In the second case you may need to update (upon being re-enabled)!your Magisk app/mngr if you want (and that could possibly fail if you try to update from the repackaged app/mngr)

      I would go for the first option, and then also update the Magisk itself (unless you have some old device where Magisk update/installation might fail)

      Edit - maybe you have an option in Settings/Apps to enable the disabled/frozen old Magisk mngr/app, in that case you don't need to use adb command for the option (2)
      I went for the first option. I uninstalled the renamed package and installed the newest App.
      It detects magisk again, thank you!
      So it says the Magisk version is 21.1, if I want to update with the direct installation method it says "unable to detect target image". Any hints on this one?
      2
      I went for the first option. I uninstalled the renamed package and installed the newest App.
      It detects magisk again, thank you!
      So it says the Magisk version is 21.1, if I want to update with the direct installation method it says "unable to detect target image". Any hints on this one?
      Can you post the screenshot showing your Magisk main window to see the versions

      Are you on Stable?
      And sorry, you probably posted but what is your phone and ROM?

      You could try patching your image but maybe it would also fail (might be that v23 does not install to your phone)
      2
      Can you post the screenshot showing your Magisk main window to see the versions

      Are you on Stable?
      And sorry, you probably posted but what is your phone and ROM?

      You could try patching your image but maybe it would also fail (might be that v23 does not install to your phone)
      Magisk:
      Installed: 21.1 (21100), A/B: Yes, Ramdisk: No, SAR: Yes
      App:
      Newest: 23.0(23000)
      Installed: 23.0 (23000)

      I am using an PH-1 with an Android 11 Rom (Build: RQ1A.201205.010)

      The main 'problem' I had is solved. I have Magisk back and so far everything is working.
      If I get some sparetime I will have a look on patching the boot.img. Until then I will go with the actual setup. So once again thank you for the great support!
      1
      Will this show updates within the app itself? Or do we have to manually download and install new Alpha branch?

      Over-joyed that someone is continuing on with the work. I thought we were done with magisk honestly. Has been Anxiety-inducing
      Yes, it should with Alpha Channel set. This commit:
      https://github.com/vvb2060/Magisk/commit/f2c6ee7bc2f5be6456a91e85424069e6da16a667

      Not really new; @vvb2060's been a main colaborator and contributor of new functionality on (John Wu's) Magisk for some time now. 🙂

      His 'Alpha' experimental builds have been available since Dec 2020, and he also has many test / experimental 'Lite' and 'MTK' builds going back to May 2020.
      https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85127113 PW
    • 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
      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
      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.
      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
      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...
    • 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