• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

Magisk General Support / Discussion

Search This thread

pndwal

Senior Member
As you wrote earlier, that release is (no more) available in Telegram

63cfe7b4-alpha is the last on Telegram and the Alpha app itself still declares b6298f86-alpha as the latest released
Some installed it. Most comments gone with withdrawn thread. One or two comment in last build thread available...

b6298f86-alpha is of course just the last build uploaded to GitHub repo. PW
 

pndwal

Senior Member
I have magisk version 1eb83ad8-alpha-31 (23001)

I see the notice "requires additional setup. Do you want to proceed and reboot". After the reboot I see the same notice every time. What's wrong?

I don't see any modules except "systemless hosts". I updated the list by pressing the icon in the right top corner. Where is the modules? How to turn it on?
Yup, as mentioned, Alpha merges TJW commits that have already disabled repo access.

You have one version of Magisk Alpha app and completely different (few versions older) Magisk - observe the differences in version strings of "Installed" on your first screenshot

And btw, you probably have wrong Update Channel (Canary, while you are running Alpha?!)
Just looking back at missed posts...

Actually, App Latest indicates Update Channel set to Beta or Stable.

- Inspect Update Channel in the Magisk apk Settings, and make sure you switch to Alpha (bcs you have both Magisk and Magisk apk from Aplha), not Canary or Stable
- Then take Magisk Install from the main Magisk app window, you can use Direct Install or Patch and Flash
Just to avoid confusion, since single package builds (public 22.0), channel is only relevant to updating App; Direct Install or Patch Image will always be updated to match App Installed (as Magisk is no longer sourced from server, but now packaged / 'synced' with App), and works offline.

As shown it will install b6298f86-alpha Magisk (mask) regardless of channel.
If you want instead Stable and Canary, you have to install the old Stable or Canary Magisk apk, then patch and flash your img
To be clear, this is the only reason to change Update Channel in post 22.0 builds; The App (now complete package) can be updated from within currently installed App (from server). App Installed will match App Latest shown from Update Channel set and requires internet access.

As shown, it will install 23.0 Beta / Stable.

Of course, this may initially fail due to downgrading (most systems won't allow Installation of older app versions without first uninstalling the current app), or app signature varying (eg. moving between TJW and vvb2060 builds when app is un-hidden).

Where App install fails, downloaded .apk is still in folder set in settings, Download path. Simply uninstall current App, locate the new .apk and it will now install.

Interestingly, if app is hidden initially (custom signing) moving between different dev's builds doesn't result in such failed installation, but in practice I've found it works flawlessly only 50% of the time. Another 50% of attempts have resulted in dual conflicting apps coexisting due to incompatibiliies despite the fact it's supposed to work. I therefore recommend always un-hiding / restoring App before up or downgrading.

🤠 PW
 
Last edited:
  • Like
Reactions: ipdev and duttyend

Stillhard

Senior Member
Sep 25, 2016
64
40
Yup!... But if vvb2060 can't ... That leaves John ... Think he'll try?

Perhaps canyie? PW
TJW once said Riru will get merge into Magisk if i'm not mistakenly recalled my memory, perhaps Riru's Hide can helps

Edited for this:
John Wu:
基本上 Magisk 這邊跟 riru 合併手續差不多了 (Basically, the merger of Magisk and riru is almost complete.)

Deleted Account:
那以后合并后,刷完magisk就自带riru了吗(So after the merge, magisk will be installed with riru?)

John Wu:
yes, MagiskHide will depend on riru
 
Last edited:
  • Like
Reactions: pndwal

Chandru123

Member
Dec 6, 2013
20
19
Chennai
OnePlus 8 Pro
Some installed it. Most comments gone with withdrawn thread. One or two comment in last build thread available...

b6298f86-alpha is of course just the last build uploaded to GitHub repo. PW
That build is luckily the most stable out of the other recent ones. The latest builds are starting to crash applications after some time and the magisk app tries to restore itself. Not sure the problem is with me doing a direct install over the previous versions.

Do I need to install it afresh with all the modules removed first. Kindly advise the steps needed to install the latest magisk alpha properly.
 

HippoMan

Senior Member
May 5, 2009
1,737
587
Hippoland
[Reserved]

Just took this space to say I really hope we get official TJW Magisk build before 50000 posts... It just might cheer me up.

However, lets see if post 48000 proves auspicious... I'm so depressed... and I already have a headache just thinking about it ... I need a coffee.

[The only source of hot drinks on this entire ship is a benighted piece of equipment produced by the Sirius Cybernetics Corporation called a NutriMatic Drinks Synthesizer. It claims to produce the widest possible range of drinks personally matched to the tastes and metabolism of whoever cares to use it. When put to the test, it invariably produces a plastic cup filled with a liquid almost, but not quite, entirely unlike coffee. 😕

"Share and Enjoy," drones the drinks machine.

"Share and Enjoy" is of course the company motto of the hugely successful Sirius Cybernetics Corporation Complaints division. Their marketing division also defines 'android' as "Your Plastic Pal Who's Fun To Be With."... I can only pull off that feat by employing a magiskal mask and several spoofing modifications... No wonder the Complaints division alone now covers the major land masses of three medium sized planets and is the only part of the Corporation to have shown a consistent profit in recent years.]

Marvin
Life ... don't talk to me about life.
 

73sydney

Senior Member
Jul 21, 2018
1,990
1,775
Sydney
Google Pixel 2 XL
That build is luckily the most stable out of the other recent ones. The latest builds are starting to crash applications after some time and the magisk app tries to restore itself. Not sure the problem is with me doing a direct install over the previous versions.

Do I need to install it afresh with all the modules removed first. Kindly advise the steps needed to install the latest magisk alpha properly.

i had some issues with downgrading that borked my install completely, only removing /data/adb solved it when downgrading at least...but i did wipe that after doing a complete uninstall form my previously stable one (and one i went back to - alpha 31), in case there was any change in the magisk.db format, on the upgrade too (doesnt seem so as others just upgraded with it in place). Downgrading was more drama...definitely solved by removing /data/adb

(i normally keep my magisk.db across ROM's to lazily apply hidden apps before i restore them...handy with banking and pay apps..install magisk, reboot, copy magisk.db to /data/adb, enable magiskhide, reboot, restore apps - no need to tick anything and no sensitive apps detect root and bork)

Im staying put on alpha 31 again for a while after the recent alpha borkage

If you want a failsafe alpha, my favourite before the latest major changes is attached to this post, one is a zip for TWRP, the other is an APK for install in Android.


TWRP (and APK) method:

1) Flash the ZIP via TWRP (this will automatically patch the boot image)
2) Reboot
3) Install the APK
4) Enable MagiskHide in Settings (and Rename Magisk App if preferred or for most banking apps)
5) Test SafetyNet - if no pass seek help

APK Method:

1) Find or extract the boot.img for your current ROM, copy to device
2) Install the APK
3) Open Magisk, click Install, locate the boot.img, patch it
4) Copy it off device to PC
5) At command prompt and with platform-tools (fastboot and and installed), use command (substitute magisk patched_boot.img)

fastboot flash boot magisk_patched_boot.img

OR

fastboot boot magisk_patched_boot.img - if you want to test it will boot first before using the previous command to flash (commit) to it

6) Reboot
7) Enable MagiskHide in Settings (and Rename Magisk App if preferred or for most banking apps)
8) Test SafetyNet - if no pass seek help

You know which method i use, being a lazy bugger and with TWRP for my device...

Note: Same method can be used with current/latest alphas...up to enabling MagiskHide..as its been removed/replaced by Zygote and Deny toggles

So the only downside to using the safe or older alphas/officials is that the bleeding edgers here will now be using new terms like Deny List and Zygote, for the earlier alphas/officials its the traditional Magiskhide...
 
Last edited:

Compass Linux

Senior Member
Apr 24, 2011
407
170
i had some issues with downgrading that borked my install completely, only removing /data/adb solved it when downgrading at least...but i did wipe that after doing a complete uninstall form my previously stable one (and one i went back to - alpha 31), in case there was any change in the magisk.db format, on the upgrade too (doesnt seem so as others just upgraded with it in place). Downgrading was more drama...definitely solved by removing /data/adb

(i normally keep my magisk.db across ROM's to lazily apply hidden apps before i restore them...handy with banking and pay apps..install magisk reboot, copy magisk.db to /data/adb, enable magiskhide reboot, restore apps - no need to tick anything and no sensitive apps detect root and bork)

Im staying put on alpha 31 again for a while after the recent alpha borkage

If you want a failsafe alpha, my favourite before the latest major changes is attached to this post, one is a zip for TWRP, the other is an APK for install in Android.


TWRP (and APK) method:

1) Flash the ZIP (this will automatically patch the boot image)
2) Reboot
3) Install the APK
4) Enable MagiskHide in Settings (and Rename Magisk App if preferred or for most banking apps)
5) Test SafetyNet - if no pass seek help

APK Method:

1) Find or extract the boot.img for your current ROM, copy to device
2) Install the APK
3) Open Magisk, click Install, locate the boot.img, patch it
4) Copy it off device to PC
5) At command prompt and with platform-tools (fastboot and and installed), use command (substitute magisk patched_boot.img)

fastboot flash boot magisk_patched_boot.img

OR

fastboot boot magisk_patched_boot.img - if you want to test it will boot first before using the previous command to flash (commit) to it

6) Reboot
7) Enable MagiskHide in Settings (and Rename Magisk App if preferred or for most banking apps)
8) Test SafetyNet - if no pass seek help

You know which method i use, being a lazy bugger and with TWRP for my device...

Note: Same method can be used with current/latest alphas...up to enabling MagiskHide..as its been removed/replaced by Zygote and Deny toggles

So the only downside to using the safe or older alphas/officials is that the bleeding edgers here will now be using new terms like Deny List and Zygote, for the earlier alphas/officials its the traditional Magiskhide...
Many thanks for this (saving the file for safekeeping).

I've been browsing the Magisk Alpha GitHub and it seems the older releases aren't available.

Are they removed or I'm mistaken?

Compass.
 

pndwal

Senior Member
That build is luckily the most stable out of the other recent ones. The latest builds are starting to crash applications after some time and the magisk app tries to restore itself. Not sure the problem is with me doing a direct install over the previous versions.

Do I need to install it afresh with all the modules removed first. Kindly advise the steps needed to install the latest magisk alpha properly.
Consecutive builds should install properly over previous. Modules shouldn't cause issues unless system itself is updated (disable modules for major OTA's etc).

I generally reserve remedial action for when things go wrong (and as pointed out, this is more common in practice when downgrading).

But fair warning; Late Alphas are clearly far from stable, really only for serious testing, currently especially fraught due to early (highly experimental) Zygisk introduction not to mention denylist and MagiskHide component removal, and may even be enough to make you chew your own foot off... PW
 
  • Like
Reactions: 73sydney

pndwal

Senior Member
Last edited:

pndwal

Senior Member
i had some issues with downgrading that borked my install completely, only removing /data/adb solved it when downgrading at least...but i did wipe that after doing a complete uninstall form my previously stable one (and one i went back to - alpha 31), in case there was any change in the magisk.db format, on the upgrade too (doesnt seem so as others just upgraded with it in place). Downgrading was more drama...definitely solved by removing /data/adb

(i normally keep my magisk.db across ROM's to lazily apply hidden apps before i restore them...handy with banking and pay apps..install magisk reboot, copy magisk.db to /data/adb, enable magiskhide reboot, restore apps - no need to tick anything and no sensitive apps detect root and bork)

Im staying put on alpha 31 again for a while after the recent alpha borkage

If you want a failsafe alpha, my favourite before the latest major changes is attached to this post, one is a zip for TWRP, the other is an APK for install in Android.


TWRP (and APK) method:

1) Flash the ZIP (this will automatically patch the boot image)
2) Reboot
3) Install the APK
4) Enable MagiskHide in Settings (and Rename Magisk App if preferred or for most banking apps)
5) Test SafetyNet - if no pass seek help

APK Method:

1) Find or extract the boot.img for your current ROM, copy to device
2) Install the APK
3) Open Magisk, click Install, locate the boot.img, patch it
4) Copy it off device to PC
5) At command prompt and with platform-tools (fastboot and and installed), use command (substitute magisk patched_boot.img)

fastboot flash boot magisk_patched_boot.img

OR

fastboot boot magisk_patched_boot.img - if you want to test it will boot first before using the previous command to flash (commit) to it

6) Reboot
7) Enable MagiskHide in Settings (and Rename Magisk App if preferred or for most banking apps)
8) Test SafetyNet - if no pass seek help

You know which method i use, being a lazy bugger and with TWRP for my device...

Note: Same method can be used with current/latest alphas...up to enabling MagiskHide..as its been removed/replaced by Zygote and Deny toggles

So the only downside to using the safe or older alphas/officials is that the bleeding edgers here will now be using new terms like Deny List and Zygote, for the earlier alphas/officials its the traditional Magiskhide...
Good tips Nigel!

I just reverted to b6298f86-alpha due to issues w/ app seeing Magisk, and nothing I do will restore Zygisk toggle despite Zygisk being active... I'll remove db in ADB / use Complete Uninstall soon...

“The best-laid schemes o' mice an' men gang aft a-gley [ - go often astray].”
To a Mouse (1786), Robert Burns

... But you can count on mice... 😀 PW
 
  • Like
Reactions: 73sydney

zgfg

Senior Member
Oct 10, 2016
6,079
3,580
I just reverted to b6298f86-alpha due to issues w/ app seeing Magisk, and nothing I do will restore Zygisk toggle despite Zygisk being active... I'll remove db in ADB / use Complete Uninstall soon...

“The best-laid schemes o' mice an' men gang aft a-gley [ - go often astray].”
To a Mouse (1786), Robert Burns

... But you can count on mice... 😀 PW
I reverted today morning simply from 63cfe7b4 to b6298f86 in few minutes by:
- disabling Zygisk
- installing Alpha b6298f86 apk (didn't need to uninstall 63cfe7b4 apk)
- flashing my boot img that was previously patched by b6298f86 (I always save and keep my patched images for some time, you never knew previously with Canary and specially now with Alpha which bugs could be camouflaged in the release)

I checked with Zygisk detector and from XDA app (it uses WebView and I had problems with 63cfe7b4) and everything was fine.
I checked also DenyList and SafetyNet (and Device certification) - all was also ok
 
Last edited:

hfam

Senior Member
Aug 13, 2010
116
102
Man, I've been gone for quite a while, last Magisk I installed was v20 on my Pixel 2!! Coming back is like being dropped in the middle of a foreign land, and I could sure use a bit of encouragement and a small assist!

I purchased 2 of the unlocked Pixel 5a 5G devices and they'll be here in a few days. M8 died and P2 battery is just useless at this point! :)

That said, I've spent an hour or so reading the thread backwards from today and I see Magisk Alpha, zygote, MagiskHide is replaced with Deny List, etc...I am having trouble wrapping my head around some of this. I don't want to blow it with the install, so can someone point me in the right direction to get started? Magisk or Magisk Alpha? No TWRP, I just keep it super stock, no OTAs, just updates using full images (remove -w) and flash-all. Anything to look out for in the Pixel 5a that is a major change affecting root, etc?

I'm happy to read until I bleed to get it right, so even a few links on which Magisk to install, where to get it (if it's not on TJW's Magisk github), how to make sure I can hide apps (Deny List replaced MagiskHide?) and pass SafetyNet?

Thanks, and glad to see a lot of the folks who've been here forever still here helpin' out! Any assistance would be appreciated as always.
 
  • Like
Reactions: jcmm11 and ipdev

Didgeridoohan

Senior Moderator / Dev Committee / Dev Relations
Staff member
May 31, 2012
12,256
1
14,475
Gothenburg
Google Nexus 4
Nexus 6
@hfam I would suggest going with the latest stable release for now, since the Alpha releases are highly experimental and @topjohnwu will create an official release whenever he deems those changes to be a bit more mature.

The official installation instructions is always a good place to start:
https://topjohnwu.github.io/Magisk/install.html

But I see that there are a few threads on this in the 5a threads as well:
https://forum.xda-developers.com/t/magisk-root-procedure-for-5a-5g.4327361/

It should be pretty straightforward, since it's a Pixel device. Just patch the boot image and flash it to your device.

To pass SafetyNet you'll need to use the new Universal SafetyNet Fix as well (as long as you stay stock you shouldn't need anything else):
https://github.com/kdrag0n/safetynet-fix

Android 12 is gonna need some updates on the Magisk side, but that'll be taken care of in good time...

Everything that's being discussed in this thread over the past weeks/months will probably be made much more clear once John releases his next build.
 

pndwal

Senior Member
Welcome back!
Man, I've been gone for quite a while, last Magisk I installed was v20 on my Pixel 2!! Coming back is like being dropped in the middle of a foreign land, and I could sure use a bit of encouragement and a small assist!

I purchased 2 of the unlocked Pixel 5a 5G devices and they'll be here in a few days. M8 died and P2 battery is just useless at this point! :)

That said, I've spent an hour or so reading the thread backwards from today and I see Magisk Alpha, zygote, MagiskHide is replaced with Deny List, etc...I am having trouble wrapping my head around some of this.
Good start. If I were you:

- I'd read John's Release Notes from your 20.x (?) version for best / official summary of changes. Major changes in 21.0 & 22.0:
https://topjohnwu.github.io/Magisk/releases/
I don't want to blow it with the install, so can someone point me in the right direction to get started? Magisk or Magisk Alpha?
- I'd avoid Alpha, especially now that John has returned from limbo (with blessing of big G).

Alpha's are Bleeding Edge test builds, bleeding more than usual presently and especially ATM are only for mavericks keeping pace with all TJW commits / willing to test w/ untold bugs and regressions, and not disposed to chewing off a foot when things go pear-shaped.
No TWRP, I just keep it super stock, no OTAs, just updates using full images (remove -w) and flash-all. Anything to look out for in the Pixel 5a that is a major change affecting root, etc?

I'm happy to read until I bleed to get it right, so even a few links on which Magisk to install, where to get it (if it's not on TJW's Magisk github), how to make sure I can hide apps (Deny List replaced MagiskHide?) and pass SafetyNet?
- Install latest Stable or Canary from main GitHub page (these are synced / essentially identical currently). If taking direct install / update on old device, be sure to restore (unhide) Manager / App first, and disable modules especially after OTA's.

No Zygisk, Denylist etc. in current TJW builds; (It'll be a big leap when it arrives), so no worries with that stuff till next Beta, and John usually updates documentation at the same time...

- Familiarise yourself with changes to Installation Instruction:
https://topjohnwu.github.io/Magisk/install.html
and FAQs re. fixing issues (new Safe Mode fix for modules causing bootloop etc).
https://topjohnwu.github.io/Magisk/faq.html

For Stock certified ROM, enabling MagiskHide and installing latest Universal SafetyNet Fix module 2.1.1 + Riru should be enough to pass SafetyNet at present. USNF:
https://forum.xda-developers.com/t/magisk-module-universal-safetynet-fix-1-1-0.4217823/post-84286769

Many changes in @Didgeridoohan's wiki regarding other issues too. First port of call if having problems:
https://www.didgeridoohan.com/magisk/HomePage
Thanks, and glad to see a lot of the folks who've been here forever still here helpin' out! Any assistance would be appreciated as always.
All best. 🙂 PW

Edit: I see there's some repetition here, but shouldn't hurt. 😛
 
Last edited:

Top Liked Posts

  • 3
    Hi guys

    Any idea why i Got zygisk : no

    even if it is enabled into magisk settings ?

    I'm on latest Canary 23015 with magisk manager repacked name

    View attachment 5473395View attachment 5473397
    Looks like you didn't reboot the phone (the Zigisk setting is telling you that you should reboot)
    1
    Anyone seen Happy Momo before?

    Hiding Zygisk may be possible! 😀 ...

    View attachment 5472595

    Translated:
    "The environment is normal, no changes to the environment have been found"

    Seems Shamico may be the answer, but early days... (according to this user / dev: nu11ptr)

    I know nothing about anime, Manga, demon-girl characters etc, and this may or may not be relavent:


    https://machikado-mazoku.fandom.com/wiki/Momo_Chiyoda

    Anyway, looks like a genuine POC FWIW.

    🤪 😝 PW 😋

    ... So we now have proper hide-for-Zygisk test released to public!

    It's Shamiko-v0.1.1-40-debug.zip

    Translated;
    LSPosed:

    Shamiko Preview

    Simple hide based on zygisk.

    Configure inheritance denylist. After installing Shamiko, configure denylist and close denylist, Shamiko will automatically take over and hide.

    Theory supports Android 8.1+, but only tested on 11

    You need to use the version of magisk after this pr: https://github.com/topjohnwu/Magisk/pull/5010

    So need to wait for that PR to be merged, or build Magisk from
    https://github.com/LSPosed/Magisk/tree/xhookclear
    to try. PW
  • 33
    I've been following the thread for a long time now, and I think some users are still confused regarding the differences between the different variants of Magisk that are available for use. I'm going to try and summarize them here, which should be helpful for everyone:

    Magisk Variant​
    Stable​
    Canary​
    Alpha​
    Custom​
    Release
    Official​
    Official​
    Unofficial​
    Unofficial​
    Maintainer
    topjohnwu​
    topjohnwu​
    vvb2060​
    TheHitMan7​
    Project Link
    Zygisk
    No​
    Yes​
    Yes​
    Yes​
    DenyList
    No​
    Yes​
    Yes​
    No​
    MagiskHide
    Yes​
    No​
    Yes*​
    Yes​
    Modules Repo
    Yes​
    No​
    No​
    Yes​
    Download Link

    *If you turn off Zygisk in Alpha, then DenyList will act like MagiskHide. So essentially, you can have Zygisk On + DenyList or Zygisk Off + DenyList running as MagiskHide.

    In case I've gotten something wrong, or can add more information, please let me know. :) Cheers!
    14
    For those who use Alpha or new Canary and miss the old Modules Repo:

    Download and install their root app that will act like the old Modules tab with the integrated connection to the Repo

    Actually, two Repositories - the old 'official' one plus the alternative new Repo (the old/original TJW's Repo is closed for submission of any new modules - only the modules that were admitted previously could still be updated to the old 'official' Repo)
    13
    Great guide, thanks... I think I followed a similar guide from you a while back, but forgot full path requirement... Pinged you as I thought you'd come through! 👍

    I didn't say MagiskBoot was part of Magisk binary however... I clearly said 'magiskboot * binary * isn't working for me'. 😜 ...

    Thanks for the method. PW
    This one might be a bit more confusing. ;)

    Not sure I can operate Magiskboot before I flash it to the device. Once I flash Magisk, I have access to fastboot through recovery, and that's it.
    While catching up last night, I missed that you are not rooted. :oops:

    ---

    Without root, you need a directory with heightened permissions that you can access.

    You should be able to use the /data/local/tmp/ directory.

    Unzip the Magisk apk file and push the appropriate architecture to the device.
    Then set the permissions to be executable.

    Linux/Mac command line example.
    Make the appropriate changes if you use Windows.​
    • Unpack the lib directory from the Magisk apk file.
      unzip app-debug.apk lib*
    • Push the matching Magisk architecture to the device.
      adb push lib/YourDeviceArchitecture/* /data/local/tmp/
    • Push the boot image you want to modify to the device.
      adb push boot.img /data/local/tmp/
    • Set permissions.
      adb shell chmod 0755 /data/local/tmp/*.so
    • Enter adb shell and change directories.
      adb shell
      cd /data/local/tmp/
    • Run the commands using the ./ prefix.
      ./libmagiskboot.so

    Make the changes you want, exit the shell and pull the new-boot image to the computer.
    Reboot into bootloader and boot the new-boot image.

    Note:
    /data/local/tmp/ should be an empty directory.
    You should clear the directory after you are done using it. ;)


    Quick example just unpacking and repacking a boot image without root.
    Magiskboot Example - Pastebin - Link

    Hope it helps more than confuse. 🙃

    Cheers. :cowboy:
    12
    Hi all. :D

    I do not use twitter so, I am out of the loop at times. :confused:
    Links to a few tweets were noted in an issue on USNF github earlier today.

    Seemed to be appropriate to mention here.

    From John Wu.
    PSA: MagiskHide of Magisk v23.0 no longer passes SafetyNet, even with BASIC evalType. Tested on my Pixel 4 XL running stock Android 12 with vanilla Magisk v23.0.

    MagiskHide is *officially* dead. If you need any kind of root hiding, it's the perfect time to find alternatives.
    There are already plenty of "root hiding" modules out there that I'm aware of, some even utilizing the latest features of Magisk canary.

    I'm obligated to distance myself from any tamper detection circumvention, so I will not assist/promote any modules. Do your own research 🙃

    From osm0sis
    *Cough* @kdrag0n's Universal SafetyNet Fix (USNF) *Cough* 😘
    To be specific, Magisk Canary, Zygisk and DenyList enabled, and USNF v2.2.0+ is the way forward. 🤘

    Cheers all. :cowboy:
    10
    Gents, as grateful I am for all above substantial contributions I hope you allow me to express my "wonder"... As you all know off-topic posts (unless violating forum rules) are only removed on request of the threadowner, I'm just surprised that extremely experienced and knowledgable XDA users allow this thread to deviate from its subject.
    Just as an idea for similar "occasions" in future, hadn't it been better to simply point somebody to the well known subject matter related ad blocker threads? Okay, unexperienced members should certainly question themselves why they post off-topic in a thread. After the initial serious problems with the in-XDA-search, I meanwhile must say it's working excellent for me.

    And by the way: I've removed the link to paid applications as not being accepted on XDA. Please don't mind.

    Regards
    Oswald Boelcke
    Senior Moderator
  • 1070
    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