Magisk General Support / Discussion

Search This thread

zputnyq

Senior Member
Apr 19, 2013
619
278
Why should you build debug for yourself?!

Isn't it more simple to follow the link from Magisk app (no matter which version) to go to the Magisk official GitHub page

Scroll down there to find Downloads - see the screenshot

You can download app-debug.apk (Debug) or app-release.apk (Canary)

To switch, you need to download and install the right APK and then to patch the img and flash (or you can flash the renamed APK to zip from TWRP).
Installation is also described in details on the Magisk GitHub page
He didn't mention the debug release on the commit, like stable version or canary.
 

Attachments

  • _20220525_022332.JPG
    _20220525_022332.JPG
    75.5 KB · Views: 30

pndwal

Senior Member
He didn't mention the debug release on the commit, like stable version or canary.
Since Debug and Canary builds are basically functionally identical, they are produced in tandem and appear in https://github.com/topjohnwu/magisk-files/tree/canary (repo/branch).

Debug will produce a performance hit on old devices due to new debug tools integrated, but the difference is otherwise just build type. Canary is now smaller than it was as verbose debug logging is removed and it is built as release. Debug is built as debug. Both are built at the same time from same commit...

John posted this recently:
John Wu, May 15

An update to future Magisk releases: the "Canary" channel will start shipping release builds, and a new "Debug" channel will be shipping debug builds. Both channels will be updated at the same time from the same source code, the only difference is the build flag.

Debug builds should only be used if you are actively developing Magisk, or if you want to submit bug reports. An upcoming change will start enforcing APK signature verifications on release builds to combat fraudulent/modded/hacked Magisk app APKs.

We also plan to start adding symbols (and maybe some sanitizers) and enabling core dumps on debug executables for better debugging and auditing. All these changes can be an issue on older device, and could significant effect performance, which is why it should not be used daily.

John Wu, May 24 (8h)

I just pushed out a new Canary build that enforces Magisk app signature verification directly in the root daemon. I have also updated the README on GitHub with guidance for developers working on Magisk itself and distributing your own builds signed with your own keys.

👀 PW
 
Last edited:

dohanin

Senior Member
Mar 26, 2011
225
126
Sony Xperia X Compact
Xiaomi Mi Pad 4
good morning all.

latest 5.0.5519 of Intune Portal (Microsoft) detects root !

On top of common/standard guideline (100& working till yesterday),

a) I hided xposed modules (HMA)
b) XprivacyLUA is set as well (tracking and analytics)

No way to circumvent root detection. I suspect Intune Portal needs to get the list of installed applications as - when I also set this flag in XPrivacy + complete app's data reset - the account cannot be addedd and app loops.....

I also froze (renamed) Magisk app --> no luck

any further suggestion from you?
my intune company portal is updated to latest version and it is still fine, i.e. root not detected. i only have usnf and shamiko modules

you have to make sure ALL activities under intune are ticked in denylist (default is not)
 

traversone

Senior Member
Feb 18, 2019
188
63
my intune company portal is updated to latest version and it is still fine, i.e. root not detected. i only have usnf and shamiko modules

you have to make sure ALL activities under intune are ticked in denylist (default is not)
ok, many thanks! I will select all the activities as per your suggestion (in last but noe version that was not needed).

But which ANdroid version do you use?
 

dohanin

Senior Member
Mar 26, 2011
225
126
Sony Xperia X Compact
Xiaomi Mi Pad 4
ok, many thanks! I will select all the activities as per your suggestion (in last but noe version that was not needed).

But which ANdroid version do you use?
Actually, someone in this post also reported the need to check all activities for intune company portal:


I am using Android 12.
 

traversone

Senior Member
Feb 18, 2019
188
63
Actually, someone in this post also reported the need to check all activities for intune company portal:


I am using Android 12.
in Android 11 (it is supposed to deny access to applist) I have also added Outlook in Denylist (standard selection for IntunePortal too, non all activities) and it WORKS !

of course Manager must be repacked with random name,

In android 10 this trick does not work though, or I am not able to make it working
 

lindsaysxda

Member
May 14, 2022
20
3
Xiaomi Mi A1
Can someone please help with my issue?
I'm trying to install Magisk to inactive slot as per this guide but no success.

I uninstalled Magisk (restore images option) successfully, downloaded and installed OTA, went back to install Magisk but there is no "install to inactive slot" anymore (screenshot), only select patch a file. It used to be on older versions when I was on LOS 17 a few months ago. I'm on 18 now. Magisk latest.
Screenshot_20220524-154117_Magisk.png
 

zgfg

Senior Member
Oct 10, 2016
7,595
4,998
Can someone please help with my issue?
I'm trying to install Magisk to inactive slot as per this guide but no success.

I uninstalled Magisk (restore images option) successfully, downloaded and installed OTA, went back to install Magisk but there is no "install to inactive slot" anymore (screenshot), only select patch a file. It used to be on older versions when I was on LOS 17 a few months ago. I'm on 18 now. Magisk latest.
View attachment 5622367
Don't know regarding your ROM, on my Xiaomi, stock ROM the option is present

If you are on 24.3 Stable, have you tried with the latest Canary 24313.
Btw, if you want to report to Magisk GitHub, you will need (Canary) Debug version
 
  • Like
Reactions: ipdev

zgfg

Senior Member
Oct 10, 2016
7,595
4,998
There is no canary in the options. Only Stable, Beta, Custom.
I switched to beta. Clicked install on magisk app and it installed same version 24.3.
Magisk install still no inactive slot option
Only Canary is the latest.
Beta is old as Stable (I wrote 24313, Beta almost for sure is not that version)

You should go to the Magisk GitHub and download

And (for everybody else) - there is a direct link to GitHub from the Magisk app (no matter which version you use)
 

pndwal

Senior Member
There is no canary in the options. Only Stable, Beta, Custom.
I switched to beta. Clicked install on magisk app and it installed same version 24.3.
Magisk install still no inactive slot option
View attachment 5622389View attachment 5622391
You won't get Direct Install option without root; I believe option for Install to inactive slot on A/B devices likewise is only available with root... Seems you have rebooted after taking Uninstall, Restore images, so have lost root.

John says:
Do not reboot or you will have Magisk uninstalled...
...do not press the "Restart now" or "Reboot" button!


Whole update process (incl. Installing Magisk to inactive slot) requires root retained in active system... Ie. You can Uninstall / Restore images and Magisk is still loaded, but not if you reboot. 😬 PW
 

lindsaysxda

Member
May 14, 2022
20
3
Xiaomi Mi A1
You won't get Direct Install option without root; I believe option for Install to inactive slot on A/B devices likewise is only available with root... Seems you have rebooted after taking Uninstall, Restore images, so have lost root.
No I haven't. I have done this process multiple times as per the guide I linked in my original post.
The option is just simply on new versions.
 

Top Liked Posts

  • 4
    By the way, there is another thread with detailed OP instructions for the new Magisk v24/v25:

    And a thread that was opened for hiding root with the new Magisk:

    Those new threads were opened because of this old and cluttered thread.
    Unfortunately, people still report/ask here (and in parallel complain that thread is too big to read☹️)
    3
    As always, 'The Masturbate Girl' - Mad donno
    Why do you continue this theme... I never read where John Wu said it either; just hearsay...

    I don't need to keep hearing such remarks about anyone helping with Magisk etc, but confess I prefer polite company... And this is impolite (at best) at least among English speakers... 🙄 PW
    2
    I have a issue in magisk where i cant activate mobile data and make calls anymore, it also says no imei, please fix it in the next update. I use the A32 (a325f) where i flashed magisk through boot.img
    More about this here:
    Who will fix it?!

    Developer(s) don't read this thread

    To report issues, you need to go to Magisk GitHub 🤣
    1
    I too never use her/their injected telemetry releases, i was just referring to her wording 'R.I.P MagiskHide' as you quoted and tested her newest Magisk Detector v3.0 with said, but no prove that MagiskHide detected as promoted

    Edited: Added the link to the source of the apk (it's inside the artifact file)
    I don't doubt that the R.I.P. comment was a nostalgic reference, but I don't think it was a comment on or promotion of detection by MagiskDetector or other! 🤪

    MagiskDetector release is cleary only due to it sharing code used in Momo and the 'momo' methods made public relating specifically to MagiskDetector...

    The R.I.P. comment came immediately after the latest Alpha release with the release note
    1735a713-alpha
    The original MagiskHide has been removed
    and the remark
    The MagiskHide detection method and code used by momo have been made public

    In this context it's obviously just an expected and logical update to these previous notes about pending removal of MagiskHide in Alpha specifically:
    Chinese translated:

    Jan 15
    "Alpha will remove magiskhide once all popular Riru modules have released zygisk version and magisk stable version has officially released zygisk."
    https://t.me/magiskalpha/406

    Latest:
    June 18
    "According to telemetry data, the number of zygisk users has reached 78.3%, and after more than 85%, alpha will remove magiskhide."
    https://t.me/magiskalpha/511
    😅 PW
    1
    This is still intriguing me... I see this is OnePlus 7T, and it happens on rebooting...

    Just wondering if you have ever patched / flashed recovery image on this device?... Or is device swapping between A/B system slots somehow? (Do you have working systems on both?... Perhaps Magisk in boot_a and boot_b?)... PW
    I am just confused. 🙃
    More "What The ???"​
    ___

    It kind of works now, but I have to choose if I want Zygisk on (=No Mobile Network) or Zygisk off (=Older version of Magisk).
    I did flash the recovery image to get Magisk onto the device to begin with, everything else is "direct install (recommended)".
    No A/B stuff..
    - Did you patch the recovery image with Magisk.
    - Replace the recovery image with the Magisk patched version and boot into system from Recovery
    or..
    Did you you use recovery to install Magisk (patch the boot image)?

    I have only had a 7T for a few weeks.
    Since OnePlus has switched their release/updates to OTA only, it took me a little while to find a boot image.
    Once I found it, I patched it with Magisk and ...​

    Currently my (new-to-me) 7T is on the a12 beta.
    I was testing the fingerprint scanner.​

    I was planning on restoring to stable/stock OOS this weekend.
    If you are running a custom ROM or kernel, let me know.
    I am willing to test. 🙂
    ___

    Very interesting...

    So can I assume 7T has recovery_a/_b partitions as I believe 8T does, and that you also patched either recovery_a or _b in Magisk App some time back?

    If this is correct, I'm guessing Zygisk-off somehow causes device to reboot to system via recovery, and you thus have old Magisk since you patched recovery image (which is also a boot image containing ramdisk of course) with that some time ago...

    Note: Magisk in recovery and customised protocol for reboot via recovery to system w/o special adapted recovery key combo was designed for A-only legacy SAR devices specifically as these require Magisk in recovery partition as they have no ramdisk in boot... You seem to have used it on your 2SI device and there is no reason it shouldn't work apart from the fact that Magisk in boot partion is far more desirable / convenient...

    If I'm correct about a/b partitioning in 7T, your modern 2SI boot type device will of course have ramdisk in 4 partitions, recovery_a and _b, also boot_a and _b... This is fairly unique as most 2SI devices use recovery in boot partition (w/ a hybrid ramdisk) and have no actual recovery partitions.

    Again, if I'm right you can test theory by booting from powered down state using recovery key combo with this adjustment: As soon as you press the key combo and the device vibrates with a splash screen, release all buttons to boot into Magisk. (If you wanted to boot into the actual recovery mode, you would long press volume up until you see the recovery screen.)
    https://topjohnwu.github.io/Magisk/install.html#magisk-in-recovery

    Please reply to confirm (or correct) this! 😛 PW

    OnePlus 7T partitions.
    Code:
    OnePlus7T:/ # ls -la dev/block/by-name/
    total 0
    drwxr-xr-x 2 root root 2520 1972-09-19 21:06 .
    drwxr-xr-x 6 root root 4280 1972-09-19 21:06 ..
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ALIGN_TO_128K_1 -> /dev/block/sdd1
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ALIGN_TO_128K_2 -> /dev/block/sdf1
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 LOGO_a -> /dev/block/sde21
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 LOGO_b -> /dev/block/sde47
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 abl_a -> /dev/block/sde8
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 abl_b -> /dev/block/sde35
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aging -> /dev/block/sde54
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aging_mod -> /dev/block/sde55
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 aop_a -> /dev/block/sde1
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 aop_b -> /dev/block/sde28
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 apdp -> /dev/block/sde59
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 bluetooth_a -> /dev/block/sde5
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 bluetooth_b -> /dev/block/sde32
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 boot_a -> /dev/block/sde11
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 boot_b -> /dev/block/sde38
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 carrier -> /dev/block/sda15
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 catecontentfv -> /dev/block/sde72
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 catefv -> /dev/block/sde71
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cateloader -> /dev/block/sde66
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 cdt -> /dev/block/sdd2
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib64_a -> /dev/block/sde13
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib64_b -> /dev/block/sde40
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib_a -> /dev/block/sde12
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 cmnlib_b -> /dev/block/sde39
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 config -> /dev/block/sda12
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 core_nhlos -> /dev/block/sde20
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ddr -> /dev/block/sdd3
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devcfg_a -> /dev/block/sde14
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devcfg_b -> /dev/block/sde41
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 devinfo -> /dev/block/sde57
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dip -> /dev/block/sde58
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 dsp_a -> /dev/block/sde9
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dsp_b -> /dev/block/sde36
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dtbo_a -> /dev/block/sde17
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 dtbo_b -> /dev/block/sde44
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 frp -> /dev/block/sda6
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 fsc -> /dev/block/sdf5
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 fsg -> /dev/block/sdf4
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs1_a -> /dev/block/sde22
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs1_b -> /dev/block/sde48
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs2_a -> /dev/block/sde23
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs2_b -> /dev/block/sde49
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs3_a -> /dev/block/sde24
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs3_b -> /dev/block/sde50
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs4_a -> /dev/block/sde25
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs4_b -> /dev/block/sde51
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs5_a -> /dev/block/sde26
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 fw_ufs5_b -> /dev/block/sde52
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 hyp_a -> /dev/block/sde3
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 hyp_b -> /dev/block/sde30
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 imagefv_a -> /dev/block/sde19
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 imagefv_b -> /dev/block/sde46
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 keymaster_a -> /dev/block/sde10
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 keymaster_b -> /dev/block/sde37
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 keystore -> /dev/block/sda5
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 limits -> /dev/block/sde63
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 logdump -> /dev/block/sde67
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 logfs -> /dev/block/sde65
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs1 -> /dev/block/sdf7
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs2 -> /dev/block/sdf8
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefs3 -> /dev/block/sdf6
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdm1m9kefsc -> /dev/block/sdf9
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm1oemnvbktmp -> /dev/block/sde77
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm_oem_dycnvbk -> /dev/block/sda10
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdm_oem_stanvbk -> /dev/block/sda11
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdmddr -> /dev/block/sdd4
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdtp_a -> /dev/block/sde7
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdtp_b -> /dev/block/sde34
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 mdtpsecapp_a -> /dev/block/sde6
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 mdtpsecapp_b -> /dev/block/sde33
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 metadata -> /dev/block/sda21
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 misc -> /dev/block/sda3
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modem_a -> /dev/block/sde4
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 modem_b -> /dev/block/sde31
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modemst1 -> /dev/block/sdf2
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 modemst2 -> /dev/block/sdf3
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 msadp -> /dev/block/sde60
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 multiimgoem_a -> /dev/block/sde27
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 multiimgoem_b -> /dev/block/sde53
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 oem_dycnvbk -> /dev/block/sda8
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 oem_stanvbk -> /dev/block/sda9
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 op1 -> /dev/block/sde56
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 op2 -> /dev/block/sda7
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 opproduct_a -> /dev/block/sda13
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 opproduct_b -> /dev/block/sda14
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 param -> /dev/block/sda4
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 persist -> /dev/block/sda2
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 qupfw_a -> /dev/block/sde15
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 qupfw_b -> /dev/block/sde42
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 rawdump -> /dev/block/sda22
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 recovery_a -> /dev/block/sda17
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 recovery_b -> /dev/block/sda18
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve1 -> /dev/block/sde73
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve2 -> /dev/block/sde74
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve3 -> /dev/block/sde75
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 reserve4 -> /dev/block/sde76
    lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sda -> /dev/block/sda
    lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdb -> /dev/block/sdb
    lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdc -> /dev/block/sdc
    lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdd -> /dev/block/sdd
    lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sde -> /dev/block/sde
    lrwxrwxrwx 1 root root   14 1972-09-19 21:06 sdf -> /dev/block/sdf
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 secdata -> /dev/block/sde70
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 splash -> /dev/block/sde62
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 spunvm -> /dev/block/sde61
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 ssd -> /dev/block/sda1
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 storsec_a -> /dev/block/sde68
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 storsec_b -> /dev/block/sde78
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 super -> /dev/block/sda16
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 toolsfv -> /dev/block/sde64
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 tz_a -> /dev/block/sde2
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 tz_b -> /dev/block/sde29
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefisecapp_a -> /dev/block/sde18
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefisecapp_b -> /dev/block/sde45
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 uefivarstore -> /dev/block/sde69
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 userdata -> /dev/block/sda23
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_a -> /dev/block/sde16
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_b -> /dev/block/sde43
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_system_a -> /dev/block/sda19
    lrwxrwxrwx 1 root root   16 1972-09-19 21:06 vbmeta_system_b -> /dev/block/sda20
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_a -> /dev/block/sdb1
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_b -> /dev/block/sdc1
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_config_a -> /dev/block/sdb2
    lrwxrwxrwx 1 root root   15 1972-09-19 21:06 xbl_config_b -> /dev/block/sdc2
    OnePlus7T:/ #

    Cheers. :cowboy:
  • 6
    Its trivial to sniff or even MITM a desktop, or even just run WinPE and reset admin password and use the users own saved passwords in their browser, heck even export their passwords....

    In any event the biggest risk vector is social engineering

    Chasing root phone users only gives them a "feelgood", it does nothing to stop genuine misuse and fraud, at all.....

    I dont see Google or a bank sending out a representative every time someone makes a transaction to see if theyre genuine....trying to control the device is attacking the wrong end of the transaction and is ultimately pointless
    They're not chasing root users. They just want a guarantee that the device is secure, and they have good reason to. Rooting by nature compromises device security.

    I'm not saying your opinion is invalid; in this context however, it is irrelevant, because regardless of how you may feel about the situation, it's not going to change.
    5
    @pndwal You can build Magisk app with custom name and label as you want
    MagiskHide is still effective to hide root from banking apps. It's not dead if you don't care about safetynet stuff.


    Shamiko is taking off your panties on the basic of MagiskHide. So MagiskHide is still better.
    You believe Shamiko too much, It can't really hide zygisk, only fix the zygisk detection of Momo. However, I can't blame it because that was the nature of zygisk and it will never be fixed.
    Still not sure what you're trying to tell me...

    I think we agree on most of this stuff (except your apparent impression that Shamiko Devs have some sort of sexual agenda, or that it's users are somehow prone to 'self abuse'... I won't use the other term either...).

    If you think I have misrepresented any facts regarding Magisk, Shamiko or other, please say it plainly... I think what I provided for the sake of clarity was accurate... 🙁 PW
    5
    Latest Official TJW public Stable (release) Magisk build:

    Magisk

    2022.7.20 Magisk v25.2​

    Maintenance release fixing various issues.
    • [MagiskInit] Fix a potential issue when stub cpio is used
    • [MagiskInit] Fix reboot to recovery when stub cpio is used
    • [MagiskInit] Fix sepolicy.rules symlink for rootfs devices
    • [General] Better data encryption detection
    • [General] Move the whole logging infrastructure into Rust

    Full Changelog: here

    https://topjohnwu.github.io/Magisk/releases/25200.html

    🎉🎊 PW
    5
    And I solved it. Thanks to everybody that helped me. @zgfg idea of working on data/adb/magisk.db prompted me to investigate how to reach there. MiXplorer did not have root access granted forever, so it wasn't working. Ended up using adb and, through commandline removed everything releated to Magisk in there. Uninstalled the app, flashed the standard boot.img, installed the app, flashed the patched boot.img, rebooted and... success! 🙃

    It only took me six hours or however much it's been. Now let's hope I can reactivate hiding features, etc.
    5
    I'm also done with this conversation, because you seem to be going out of your way to be obtuse about it. You specifically mentioned that rooted users are a microscopic minority. None of these corporations enacting the security measures are going to go out of their way to make security exceptions for the tiny fraction of android users that are rooted users.
    Let's not forget the security issues that rooted devices present. App developers for the aforementioned banks, etc are extremely concerned with operating in a secure environment. You wouldn't want a third party to be able to view, let alone manipulate, your financial transactions, but a rogue process with root permissions could potentially do exactly that - read account numbers, command unauthorized transactions, and worse. Think of it like a malware browser extension that could give a remote party access to your bank account.

    From the developer perspective, every single rooted device is a compromised security environment, and this is 100% true. There is no easy way to determine whether the end user is using root carefully with vetted applications, or if the device has been hijacked by a malicious rootkit. So, developers use methods such as SafetyNet, Play Protect Certification, and the new Play Integrity API as a means to try to verify the security environment of the device.

    Try to look beyond your own inconvenience as a rooted user and understand this concept. The end answer is simple: If you want an app to work correctly on your device, do not modify your device or software.
  • 1084
    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