• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

Magisk General Support / Discussion

Search This thread

jerrycbrowne

Member
Nov 28, 2019
26
1
When you are trying to "delete a system app", I am assuming you are simply talking about stopping it from running, and not necessarily physically removing the files?

I normally Hibernate, Freeze and then Hide the app. All three are standard android methods. If you wish for a point-and-shoot UI, you can try the app I built: TeMeFI

You can find the feature under:
Code:
►  Application Info / Manage
     ►  State
         ►  Hibernate-Freeze-Hide *


It also has the ability to de-systemise the app using Magisk. Requires a reboot, and this feature can be found under:
Code:
 ►  Magisk
     ►  Modules
         ►  TeMeFI Hide System Apps
             ››►  Add or Remove - Hide System Aps using a TeMeFI Module *
But I personally prefer the first method.

Let me know how you go.

I really appreciate your help. I suppose it's a philosophical question. I should be able to have anything I want on my phone and remove anything I don't want. I can, of course, 'freeze' the apps but there's still that nagging feeling that I'm being tracked/watched. (Plus, there's nothing Google offers that I want or need. I don't trust or like Google. (And I get the irony of having an android phone to get rid of Google!)
 

J.Michael

Senior Member
Jan 20, 2018
756
568
Samsung Galaxy Tab A series
With the original recovery, it worked to boot into recovery with Method 1, after patching the recovery, not anymore

When Magisk is not installed, is it hard to get to recovery? Is it important to release buttons at just the right time?

On my tablet (Samsung SM-T290), you can get to recovery by holding Power and Volume Up until you get to recovery. When Magisk is installed (in recovery), you have to let go of the buttons at the first sign of life to signal Magisk that you are trying to boot Android, not recovery. It is hard for me to get the timing right. But it is easy to get to recovery: I just keep holding the buttons. (Maybe I really have to let go of the Power button, but keep holding the Volume Up. I don't do it often.)

My point is: If you have Magisk installed in recovery, you have to hold the buttons longer to tell Magisk that you really want recovery.
 

Philnicolls89

Senior Member
Jun 28, 2019
604
244
32
A.C.T
When Magisk is not installed, is it hard to get to recovery? Is it important to release buttons at just the right time?

On my tablet (Samsung SM-T290), you can get to recovery by holding Power and Volume Up until you get to recovery. When Magisk is installed (in recovery), you have to let go of the buttons at the first sign of life to signal Magisk that you are trying to boot Android, not recovery. It is hard for me to get the timing right. But it is easy to get to recovery: I just keep holding the buttons. (Maybe I really have to let go of the Power button, but keep holding the Volume Up. I don't do it often.)

My point is: If you have Magisk installed in recovery, you have to hold the buttons longer to tell Magisk that you really want recovery.
I guess the short answer is yes, you do need to do the right button combo/release at the right time. But it is device specific for the button combo. For example with my s10+, to boot to recovery I need to hold down power volume up and bixby for 5-10 seconds then release. But to get to twrp I need to do the same thing but release the bixby button and keep holding the other 2 until twrp logo appears.
I also use power menu apps that have reboot to recovery options so I only need to use the button combo when booting to twrp or powering off the device completely. To boot normally and not to rexovery i simply power on without a button combo. Im not sure about booting to recovery without magisk installed though as I have never tried, but again it would be device specific.
 
Last edited:

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,717
12,690
Gothenburg
Google Nexus 4
Nexus 6
No matter what I try I can't delete any system app. Magisk is installed. I use the awesome Amaze file manager which neatly lists all system apps. However, after removing an app and 'Done' being displayed it remains there clearly still installed. I'm probably doing something wrong but I have no idea what. Preserve dm-verity is enabled. Any tips or tricks to try?

Do you have any Magisk module that is magic mounting an app? You might be trying to alter Magisk's systemless mask rather than the actual /system...

And of course, Android is making it more and more difficult to edit system partitions:
https://www.didgeridoohan.com/magisk/Magisk#hn_Cant_edit_system_files
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,397
5,102
Sydney
I really appreciate your help. I suppose it's a philosophical question. I should be able to have anything I want on my phone and remove anything I don't want
There are some components and apps that are part of the system and should not be removed.

I can, of course, 'freeze' the apps but there's still that nagging feeling that I'm being tracked/watched. (Plus, there's nothing Google offers that I want or need. I don't trust or like Google. (And I get the irony of having an android phone to get rid of Google!)
I would be cautious of freezing. A while back, I used to simply freeze apps, but one day I saw that a frozen app was actually still in memory:eek: And hence i created the hibernate-freeze-hide method in the above app.

The best way is to use a build of android specifically made to take google out of the picture. I forgot its name, but its out there.
 

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,397
5,102
Sydney
Last edited:
  • Like
Reactions: guhvanoh

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
11,717
12,690
Gothenburg
Google Nexus 4
Nexus 6
guys
im facing app cannot be opened after magisk hide turned on (still same even after its disabled)
latest magisk canary, and canary magisk manager
heres the log
https://del.dog/ijaqulykil

You mean this app?

I had no issues opening it once added to the Hide list and with the Manager repackaged with a random name. On Canary 20419.

If you have the app on the Hide list and the Magisk Manager repackaged but it's still complaining about root it might be detecting something else on your device. Take a look here for tips:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
 

bunklung

Senior Member
Mar 20, 2011
519
105
Okay, how about this solution to SafetyNet HW attestation:

App Mirror.

App Mirror would allow you to configure apps which create shortcuts right on your phone that look just like real apps. Call them what you want with what ever icon you want. Lets use McDonald's as an example. Once your create a mirror app with icon, you then configure a remote phone that's not rooted. When you launch the newly created McDonald's shortcut it's really a remote view to the second phone's McDonald's app.

This would allow you to seamlessly use apps on your rooted local phone, because SafetyNet is passing on the remote phone. Ideally notifications would forward/respond like Pushbullet too.

This is a better solution than having two phones in your pocket and who doesn't have an extra old Android phone laying around. You could just leave it on at home, plugged in, and on WiFi.

The main hangup would be NFC, but perhaps your old android, is so old and not longer on monthly security updates that it's rooted via unpatched exploit with the bootloader still locked. I would think they you could get into some really cool NFC one way stuff? I just don't know enough. Sorry for the long post. Perhaps someone will do a better job of explaining/improving my idea or already knows of a solution similar or better.

*edit* games would be the main hangup due to latency and graphics/video encoding issues :(
 
Last edited:
  • Like
Reactions: HippoMan

knpk13

Senior Member
Dec 11, 2015
2,115
1,231
OnePlus 3
OnePlus 3T
The one I was thinking of had "copper" somewhere in the name
https://en.wikipedia.org/wiki/CopperheadOS

Maybe its more security focused than explicitly removing google. But I would guess it would be removing the more questionable google components.

Edit: Their web site says its google free: https://copperhead.co/android/

That's weird, why is copperheadOS still up?

I thought that had been discontinued due to some legal complications and the founder left the organization. I remember he rebranded his work as GrapheneOS and it's primarily focused on hardening and security more than degoogling (which is a part of it). They have EXTREMELY limited device support (only a handful of pixel devices, which I don't own). Someone else, anupritaisno1 on XDA is working on GlassROM with similar goals, but trying to bring hardening features to more devices, OnePlus devices in particular. Projects whose main focus is degoogling are microg, the e foundation, and alternative mobile OS's (or app stores like fdroid) like ubuntu touch.

I am not sure if using these projects offers any specific benefits in degoogling over a "normal" less hardened custom ROM without gapps. I would do more research before using CopperheadOS over GrapheneOS, and find out why it's still up and who's behind it, because they tried to make it commercial and there were conflicts about the direction the project was heading in.

https://en.m.wikipedia.org/wiki/GrapheneOS
 
Last edited:

swieder711

Senior Member
I am still struggling to get EdXposed working. It's log file shows:

07-10 08:44:28.997 1673 1673 E EdXposed-Bridge: Cannot load any modules because /data/user_de/0/org.meowcat.edxposed.manager/conf/modules.list was not found
07-10 08:44:29.287 1862 1862 E EdXposed: mmap failed, errno = Permission denied

When this problem appeared before. I saw that a change to Magisk with SEpolicy fixed it.

I just saw that there is no Magisk folder (with its sepolicy.rules) under /persist on my Pixel 3 XL running the July update of Android 10! I think this may be related to my "permission denied" issue.

Any suggestions on how to get Magisk to install its sepolicy.rules on my phone? I am running the Canary release of Magisk (20419) along with .4.6.2 of Riru-EdXposed and 21.3 of RiRu-Core

I submitted the issue about "permission denied" on the Magisk Github repository. @topjohnwu suggested that it is an EdXposed problem.

Today is my 60th birthday! If I can get this fixed, that would be a nice present from the XDA community!

Any suggestions?
 
Last edited:

DiamondJohn

Recognized Contributor
Aug 31, 2013
5,397
5,102
Sydney
When this problem appeared before. I saw that a change to Magisk with SEpolicy fixed it.
not a solution, but it may be informative to test if it works while running in permissive mode.

Also, running a logcat filtering just for the selinux denials may be helpful. If that's all it is, then writing your own selinux adjustments to run on boot may get you up and running while waiting for the actual fix.
 
  • Like
Reactions: swieder711

Hafiz0091

Senior Member
Jul 9, 2017
120
35
You mean this app?

I had no issues opening it once added to the Hide list and with the Manager repackaged with a random name. On Canary 20419.

If you have the app on the Hide list and the Magisk Manager repackaged but it's still complaining about root it might be detecting something else on your device. Take a look here for tips:
https://www.didgeridoohan.com/magisk/MagiskHide#hn_Hiding_root_from_apps
nono
i mean, all app that not in recent cannot be opened with magisk hide on, and still same after switching it off
 

swieder711

Senior Member
not a solution, but it may be informative to test if it works while running in permissive mode.



Also, running a logcat filtering just for the selinux denials may be helpful. If that's all it is, then writing your own selinux adjustments to run on boot may get you up and running while waiting for the actual fix.
I installed the SElinux switch and have it set to Permissive. No change. I will reinstall Magisk manager while set to permissive.

I will also check the log for denials

UPDATE: The Magisk log shows the following
07-11 14:46:51.638 809 810 E Magisk : mkdirs /sbin/.magisk/mirror/persist/magisk/riru-core failed with 28: No space left on device
07-11 14:46:51.638 809 810 E Magisk : open: /sbin/.magisk/mirror/persist/magisk/riru-core/sepolicy.rule failed with 2: No such file or directory
07-11 14:46:51.638 809 810 E Magisk : sendfile failed with 9: Bad file descriptor

Oddly, The /sbin/.magisk/mirror folder shows 1.7GB free, but the persist folder under it shows 0 free! Maybe I have store problem and need to reform it. Not sure how to do that without TWRP or if there might be a less drastic fix.

UPDATE2: I was just about ready to reformat my phone, when I found this https://forum.xda-developers.com/showpost.php?p=81758921&postcount=1093
I deleted some old TWRP log file (not sure why they were there since I did a full wipe install of the OS) and then reinstalled GravityBox and it worked!
 

Attachments

  • Screenshot_20200711-105153.png
    Screenshot_20200711-105153.png
    159.2 KB · Views: 1,049
  • Screenshot_20200711-105205.png
    Screenshot_20200711-105205.png
    240.9 KB · Views: 1,025
Last edited:

HippoMan

Senior Member
May 5, 2009
1,723
559
Hippoland
...
The best way is to use a build of android specifically made to take google out of the picture. I forgot its name, but its out there.

The main Google-less software project is microG: https://microg.org/

There are also ROMs that are built specifically to use microG.
Lineage offers a number of them: see https://lineage.microg.org/ and https://download.lineage.microg.org/

Also, e.foundation (mentioned above) offers ROMs as well as specialized phones.


---------- Post added at 11:42 ---------- Previous post was at 11:16 ----------

Okay, how about this solution to SafetyNet HW attestation:

App Mirror.

App Mirror would allow you to configure apps which create shortcuts right on your phone that look just like real apps. Call them what you want with what ever icon you want. Lets use McDonald's as an example. Once your create a mirror app with icon, you then configure a remote phone that's not rooted. When you launch the newly created McDonald's shortcut it's really a remote view to the second phone's McDonald's app.

This would allow you to seamlessly use apps on your rooted local phone, because SafetyNet is passing on the remote phone. Ideally notifications would forward/respond like Pushbullet too.

This is a better solution than having two phones in your pocket and who doesn't have an extra old Android phone laying around. You could just leave it on at home, plugged in, and on WiFi.

The main hangup would be NFC, but perhaps your old android, is so old and not longer on monthly security updates that it's rooted via unpatched exploit with the bootloader still locked. I would think they you could get into some really cool NFC one way stuff? I just don't know enough. Sorry for the long post. Perhaps someone will do a better job of explaining/improving my idea or already knows of a solution similar or better.

*edit* games would be the main hangup due to latency and graphics/video encoding issues :(

I like this "App Mirror" idea! And here's another one of my "pigs might fly" proposals that could go along with it:

Some manufacturer makes a "Dual Phone". It will be two, complete pieces of Android-enabled hardware in one device case sharing the same screen, buttons, cameras, etc. Each one could be booted up and run separately and concurrently, controlled by a hardware switch on the device (and maybe via some sort of software, as well). One of them would use a pristine, boring, un-rooted stock ROM with a locked bootloader. The other could be unlocked, rooted, etc. All the apps that are affected by SafetyNet considerations would be running on the first, boring device. The apps that are set up via "App Mirror" as described above would run on the happy, rooted device and would delegate to the corresponding apps on the boring device.

We already have "A/B" bootable devices. Maybe some manufacturer would be willing to take this next "Dual Phone" step some time before pigs are flying around my neighborhood.

UPDATE: And here's another possibility: run Android via a device emulator on a desktop machine. Run the SafetyNet-sensitive apps via that emulator and use the "App Mirror" concept to delegate to those apps from the rooted device we carry around. Perhaps some sort of VPN or other specialized network connection could be set up between the mobile device and the desktop to make this work more efficiently.

.​
 
Last edited:
D

Deleted member 8425317

Guest
As Philnicolls89 said. Magisk Hide is disabled by default now.

That's really odd. Because on my device it's enabled and working with PayPal, My Transport app, and more.
So, I reject your reality and substitute my own ;)

I enabled user independent in the settings of magiisk.
Not sure if that did the trick, but I assure you it's working on my Samsung A70 droid10 with a downgraded Google and Assistant. !!
 

Lughnasadh

Senior Member
Mar 23, 2015
2,054
1,345
Google Nexus 5
Huawei Nexus 6P
That's really odd. Because on my device it's enabled and working with PayPal, My Transport app, and more.
So, I reject your reality and substitute my own ;)

I enabled user independent in the settings of magiisk.
Not sure if that did the trick, but I assure you it's working on my Samsung A70 droid10 with a downgraded Google and Assistant. !!
I don't doubt it's working, but Magisk Hide is disabled by default as of 20.4 . ;)

https://github.com/topjohnwu/magisk_files/blob/598fee44ab7528205b7088716d1197dd8e38532d/notes.md
 
  • Like
Reactions: pndwal

Top Liked Posts

  • 3
    Great! I was going to say sounded like nothing seemed wrong with Magisk mask itself, but likely reset corrupted Magisk data in /data/adb which should be fixed by reinstalling Magisk. (Sometimes needs deletion of files in /data/adb.)

    Happy update worked; should be able to use latest 23.0 or 23001 now.

    Do you need to restart after changing OEM root switch? Not sure what that enables exactly... guess you disabled after update. I was wondering about conflicting SU in boot ramdisk... I guess OEM could have used Magisk SU anyway... A root detection app may have given info.

    In case you haven't read it, @Didgeridoohan has great (comprehensive) overview of issues / fixes here:
    https://www.didgeridoohan.com/magisk/HomePage
    (Time to 'Updatefor Magisk v23.0(23000)'? 😛 ) PW
    regarding root switch, yeah once I've got magisk installed I turn it off which does reboot the box.
    I might just stick with things the way they are now.

    this TV box and similar boxes don't get updates from the so called manufacturers. one company produces the allwinner SoC board and ships it out to other companies who put a case and a kanged, limited OS on to it and call android TV (which it isn't).

    right now it's running better than it ever has and I'm not gonna jinx it further.

    thanks for what you guys do here!
    2
    When you had Magisk 20.4 installed, did you use MagiskHide? Did you rename the Manager?

    Have you re-enabled the OEM root?
    all is well now with @Didgeridoohan and @pndwal's help...

    I hadn't used magisk hide previously no. I managed to fix the issue by updating magisk manager.
    first I tried to flash a magisk uninstall zip via Ex Kernel manager as that sounded safest if it didn't work.
    it said it had completed the script with success but upon reboot the manager was showing 20.4 still installed.
    I reactivated the OEM root switch and updated the manager app to v22.01 I think, then I updated magisk itself and that has worked completely. I have a couple of modules installed already...

    many thanks gents
    2
    all is well now with @Didgeridoohan and @pndwal's help...

    I hadn't used magisk hide previously no. I managed to fix the issue by updating magisk manager.
    first I tried to flash a magisk uninstall zip via Ex Kernel manager as that sounded safest if it didn't work.
    it said it had completed the script with success but upon reboot the manager was showing 20.4 still installed.
    I reactivated the OEM root switch and updated the manager app to v22.01 I think, then I updated magisk itself and that has worked completely. I have a couple of modules installed already...

    many thanks gents
    Great! I was going to say sounded like nothing seemed wrong with Magisk mask itself, but likely reset corrupted Magisk data in /data/adb which should be fixed by reinstalling Magisk. (Sometimes needs deletion of files in /data/adb.)

    Happy update worked; should be able to use latest 23.0 or 23001 now.

    Do you need to restart after changing OEM root switch? Not sure what that enables exactly... guess you disabled after update. I was wondering about conflicting SU in boot ramdisk... I guess OEM could have used Magisk SU anyway... A root detection app may have given info.

    In case you haven't read it, @Didgeridoohan has great (comprehensive) overview of issues / fixes here:
    https://www.didgeridoohan.com/magisk/HomePage
    (Time to 'Updatefor Magisk v23.0(23000)'? 😛 ) PW
    1
    @Didgeridoohan @pndwal thanks for the suggestions, just to be more clear on what happened...

    I flashed magisk via magisk manager first time around because I had janky OEM root. after a recent reset most of what was flashed from v20.4 still remained. installing magisk manager showed 20.4 as installed and SU was working for granting apps permission but the module side was non functional. it would download modules and try to install them and then tell me I needed to flash 20.4...
    some parts of that 1st manager flash survived the reset, others seemingly not so. trying to uninstall via the manager didn't take me back to a blank slate like I hoped (so I could repeat that 1st flash again). I'm in limbo, rooted for root access but not for magisk modules. every time I open the manager it asks for the download of additional setup files that never work. so I need to reflash somehow.
    flashify installs and reviews say it still works for android 10 users but I've no idea how it would cope with a more complicated (presumably) script. I have Ex Kernel manager that has a script manager and a flasher. I just don't know if these are good gambles worth considering.
    When you had Magisk 20.4 installed, did you use MagiskHide? Did you rename the Manager?

    Have you re-enabled the OEM root?
  • 9

    Latest @vvb2060 Magisk Alpha build (July 18, 2021) changelog:​

    Chinese Translated:

    alpha update log​

    Magisk (1eb83ad8-alpha-19)​

    • 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
    • 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 a modal waiting pop-up window when hiding/restore the Magisk application
    Edit: The following are new commits:
    • App adapted to Android 12
    • Android 12+ super user hides the screen overlay when the window pops up
    https://github.com/vvb2060/Magisk/b...73bce50fe5e/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:

    magisk_files repo is now updated! Check 'earlier notes' for installation method / details.

    Alpha build users won't yet see Update button notice in Magisk App for this build as VersionCode has (again) NOT changed from 23001.

    I'm not sure if this behaviour will be addressed, but users will observe the 'Latest' version (1eb83ad8-alpha-19) now differs from 'Installed' (1eb83ad8-alpha).

    Package is now also uploaded to Telegram group.
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85229385

    Interestingly, in Magisk Documentation, @vvb2060 has updated "Internal Details" and "Deployment" since John did.
    https://github.com/vvb2060/Magisk/tree/alpha/docs

    😛 PW
    8
    reddit link shared by John Wu:
    reddit post

    Especially interesting a comment by the leader of the Android Security team:
    (I lead the Android Hardware-backed security team, so while this response isn't official, it's informed. Do keep in mind that I am a programmer, not a lawyer, and I have not consulted with legal, so don't rely on this as any sort of legal advice. Nor did I run this by PR, so if I put my foot in my mouth, it's totally on me. This is not an official Google communication, and I may get my hand slapped for it. Probably not, but it's happened to me in the past :) ).

    I know of no legal issues here. AFAIK, you're free to do what you like with your device. Doing these sorts of things may invalidate your warranty, depending on the details, but I'm guessing you already know that and have decided you're fine with it.

    What I do know is that if you've found a vulnerability, Google would not only like to hear about it, Google may pay you for it. If you're compromising the TEE or kernel on a Pixel device, the reward could be up to $250,000. If you're compromising the Titan M, up to $1,000,000. Even if your current exploit isn't on a Pixel device, if you can make it work on a Pixel you would qualify. Alternatively, your device manufacturer may have their own bug bounty program and you should look.

    Obviously, if you report the vuln, what we're going to do is to fix it, so you'll lose your SafetyNet bypass. The same will happen if you publish it for others to use. Vulnerabilities that allow SafetyNet bypass typically compromise far more than just SafetyNet, which is why Google is willing to pay so much money to identify and fix them. Also, we really believe that app developers should be able to find out if they're running on a "stock" device, with all of the security and functionality guarantees that implies, so fixing SafetyNet bypasses is important in and of itself.

    It's not that we don't like custom ROMs or rooting, in fact we find a lot of the innovation that takes place in the community very interesting and eagerly adopt good ideas we find there, but our primary focus is on protecting the 99.9% of Android users who run stock Android, and the developers who serve them. It's an unfortunate but unavoidable reality that this sometimes disadvantages ROM users. I, personally, have been holding regular meetings with various leaders in the modding community for seven years now, to get their feedback and to give them a heads up on security features we implement that might pose problems for them. My goals are to both serve the main Android userbase of some 3B people and to avoid harming the modding community. Sadly, sometimes those goals conflict, and the modders obviously lose in those cases.

    I also want to address the comments about John Wu joining Google. He is perfectly capable of communicating his own intentions and goals so I won't try to do that. I'll just say that I have no interest in shutting down Magisk. To the degree that it enables people to bypass Android security guarantees, that just shows that we have work to do, indeed it helps us to identify where we need to do that work. It's not like Magisk can somehow create vulnerabilities (it's not magic). If vulns exist, they're certain to be found and exploited by people with nefarious goals, so it's better for everyone if there's a healthy "white hat" community focused on finding problems and reporting or publishing them. I see the Magisk community as part of that white hat community, and John as a valuable contributor to Android security even before he started working for Google.
    8
    @pndwal and @ipdev

    I saw you guys did some testing on the mysterious reinstallation of an uninstalled Magisk app on a reboot. I present you with the changelog for Magisk v16.6:
    [Daemon] Check whether a valid Magisk Manager is installed on boot, if not, install stub APK embedded in magiskinit
    :p
    7

    Early Notice:​

    Latest @vvb2060 Magisk Alpha build (July 23, 2021) changelog:​

    Skipped a few due to rapid-fire! (This guy's a bit like Jorrit!)

    Chinese Translated:

    alpha update log​

    Magisk (1eb83ad8-alpha-23)​

    • 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
    • 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
    • App adapted to Android 12
    • Android 12+ super user hides the screen overlay when the window pops up
    Edit: New changes since 1eb83ad8-alpha-19
    • For devices supported by the kernel, MagiskSU uses proprietary devpts to bypass some application detection
    • Rewrite MagiskSU's pty opening logic, no additional sepolicy rules are needed
    • Fix incorrect signal sending in MagiskHide
    • Add untrusted_app_30
    https://github.com/vvb2060/Magisk/b...e147e578c92/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:

    Check 'earlier notes' for installation method / details.

    Alpha build users won't yet see Update button notice in Magisk App for this build as VersionCode has (again) NOT changed from 23001.

    I'm not sure if this behaviour will be addressed, but users will observe the 'Latest' and 'Installed' version suffix now differs.

    This build has not been uploaded at the time of this post. Watch this space!

    Latest in GitHub magisk_files repo is 1eb83ad8-alpha-20

    Latest available from Telegram group is
    1eb83ad8-alpha-22
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85229385

    Interestingly, in Magisk Documentation, @vvb2060 has updated "Internal Details" and "Deployment" since John did.
    https://github.com/vvb2060/Magisk/tree/alpha/docs

    🤠 PW
    7
    Tried using https://raw.githubusercontent.com/topjohnwu/magisk_files/canary/app-debug.apk after it was already rooted with Magisk, but adb said [INSTALL_FAILED_VERSION_DOWNGRADE]
    Just use Magisk/Canary button on Magisk GitHub home page to get app. Opens
    This is latest 23001

    Nb. Your link (where did you get that??) is to latest Canary in old archived magisk_files repo (note '_', not '-') so it's fetching 22003, ie. you would be trying to downgrade from 23000, and to downgrade you need to uninstall 23000 first, as with any app downgrade. 😜

    Nb. Regular app installation from device should work fine, then Direct install to update (or downgrade) Magisk should be available / work.
    Well golly, the whole reason I was trying to use canary was to file a bug report, but if nobody is maintaining it, then there's no point. Thanks for letting me know!
    Wouldn't say no point however.

    Magisk contributors (there are 201) like @osmosis (especially) and @vvb2060 are still distilling / fixing issues, and responding to many issues, as are other informed / experienced users. Many workarounds / non-integrated solutions have been supplied.

    Further, as has been noted, many fixes from topjohnwu Magisk Issues have been incorporated in vvb2060's Alpha builds (seems these go back at least to Dec 2018. Archived builds from Dec 2020 are available on his GitHub & Telegram) before merging in John Wu's.

    I doubt this will change, and vvb2060 has produced several builds since John's last ones already! This is the beauty of such an open source project. Links, latest etc:
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85226785

    It would be a misunderstanding to say only John is supplying fixes for Magisk Issues, just as he is not (any longer at least) its sole developer!
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-85127113

    Nb. John already pretty much turned over current App design / fixes to @diareuse so he could concentrate on Magisk Mask itself:
    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-83637567

    https://forum.xda-developers.com/t/magisk-general-support-discussion.3432382/post-83771409

    Clearly the issue of official builds continuing (in present form or other) is up-in-the-air atm, but a healthy / active / interested community still exists. 🙂 PW
  • 1057
    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