• 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
60
34
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
19
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,733
580
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,914
1,678
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
391
162
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
5,889
3,362
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
107
89
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,131
14,053
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

  • 5
    Yup, no 'must reason', but he has certainly explained / given heads-ups regarding his intention to do this as far back as old 20.4 Magisk...

    At that time he planned both to integrate overlayfs (already delivered and a real boon especially in the age of shared blocks filesystems as I think you appreciate), and to create the 'native zygote injection/hooking framework' now spawned as Zygisk.

    As for 'a decisive explanation about the reasonable advantage of Zygisk model', he said back in December, after some nine months as an apple engineer "I lost all interest in improving the current way of hiding" but native zygote injection/hooking framework would bring "proper ways to 'hide' root and Magisk Manager."

    Addressing the major issue introduced also, he said "standardizing code injection to something hidable is my goal."

    I'm not sure that there are many issues other than Riru replacement / initial hiding issues. (Reminds me a bit of XDA vBulletin to XenForo migration 😁 ), and I am optimistic that 'standardizing code injection to something hidable' may still be achieved. (I posted a little about Riru hide methods earlier today)...

    Here is John's 2020 Heads-Up in context:


    Aha! ... "I'd love to try out some new approaches." Well I'm all for that!

    To add an observation, it seems that as a (still very young) developer John always liked new challenges. Only five years ago (2016) he'd just learned C++ and knew little in programming but taught himself scripting (from "snippets of shell scripts throughout XDA"). He said SuperSU and Xposed installation scripts were the most prominent he referrenced.

    The same year he was first to release Systemless Xposed, then immediately started working on a general solution and in August 2016 released Magisk to the public. 😛...

    Personally, I think John loves the challenge / cares about custom Modding more than most of us... All power to him. 😁 PW
    Don't know did you observe (you were eager about Alpha but before the Canary was released) vvb2060 now took a SIGNIFICANT step back (better to say COMPROMISE) with his today's Alpha 43d11d87 (23010):

    - You can choose between Zygisk+Deny or MagiskHide
    (maybe you could enable Zygisk together with MagiskHide but I had no interest nor time to test that IMHO pointless combination)
    - "Configure Deny List" actually serves both for DenyList (I didn't try) and MagiskHide
    - I needed to reboot for MagiskHide to take the effect

    - If Zygisk is not enabled, you can install Riru
    - I also installed Riru-Momohider and successfully configured the isolated option to hide su from the path

    Screenshots attached

    Edit: Later also successfully tested with Riru-LSPosed and the modules: GravityBox-R, CustoMIUIzer, Hide My Applist
    5
    New Google Pixel 3 XL user. Upgraded to A12 via OTA. Rooted via ROOT GUIDE steps pinned in 3 XL forum and without deleting data. Had A12 running fine with 23000, even banking app and Google Pay. Testing Magisk Canary build from today. Rebooted and everything seems to run as expected. Toggled on Zygisk, rebooted, and again everything seems to be running smoothly - including banking app and Google Pay.
    4
    Don't know did you observe (you were eager about Alpha but before the Canary was released) vvb2060 now took a SIGNIFICANT step back (better to say COMPROMISE) with his today's Alpha 43d11d87 (23010):

    - You can choose between Zygisk+Deny or MagiskHide
    (maybe you could enable Zygisk together with MagiskHide but I had no interest nor time to test that IMHO pointless combination)
    - "Configure Deny List" actually serves both for DenyList (I didn't try) and MagiskHide
    - I needed to reboot for MagiskHide to take the effect

    - If Zygisk is not enabled, you can install Riru
    - I also installed Riru-Momohider and successfully configured the isolated option to hide su from the path
    (I didn't continue with Riru-LSPosed and the modules since it's time-consuming but Riru-Momohider proofs the concept)

    Screenshots attached
    To parrot someone 'Let me get this out of the way: since I have a full time job now, I don't have much time for Magisk; I need prioritization' ...

    I had meant to run / check it by now but priorities intervened / objected...

    Now that is keeping MHide alive, +Riru!

    This one might be more elegant than TheHitMans Custom M?

    Should be able to enable all MomoHider hide options again w/ that.

    Nb. setns is better / faster. Re isolated (only): "This feature is deprecated because it will unmount Magisk modified files for every isolated processes, and the unmounting time cannot be well controlled, which may cause some modules to not work." 👍 PW

    Edit:
    Many will like choice of traditional hide & Riru or Zygisk in up-to-date Magisk...

    Still haven't looked, but might do the translation thing for Alpha-with-deny/hide choice Changelog soon.

    Tempted Nigel? ... Just teasing ya. 🙄 🤪
    2
    To parrot someone 'Let me get this out of the way: since I have a full time job now, I don't have much time for Magisk; I need prioritization' ...

    I had meant to run / check it by now but priorities intervened / objected...

    Now that is keeping MHide alive, +Riru!

    This one might be more elegant than TheHitMans Custom M?

    Should be able to enable all MomoHider hide options again w/ that.

    Nb. setns is better / faster. Re isolated (only): "This feature is deprecated because it will unmount Magisk modified files for every isolated processes, and the unmounting time cannot be well controlled, which may cause some modules to not work." 👍 PW

    Edit:
    Many will like choice of traditional hide & Riru or Zygisk in up-to-date Magisk...

    Still haven't looked, but might do the translation thing for Alpha-with-deny/hide choice Changelog soon.

    Tempted Nigel? ... Just teasing ya. 🙄 🤪

    Nigel is tempted

    At some point (hopefully soonish) one fork will come out ahead and perhaps the other dev can join in and work together
    2
    The safetynet passed even without denylisted the google play services (gms).
  • 11
    Hey all,
    As promised, I wrote up a step-by-step tutorial for the Pixel 5a (though it applies to about all the Pixels, much of it I used on my Pixel 2 over the past 4+ years):


    I know it's a book, but I wanted to make sure I put it in everyday language and tried to make it so even a first timer could go through it and feel confident moving forward and getting root, passing SafetyNet, and update with system updates in the future with confidence.

    Anyhow, it's my attempt to give something back to the community I've gained so much from and leaned on so many times for help. If it helps even one person I'll be happy.

    Thanks again to the entire community, and particularly the folks who have been here helping tirelessly and without reserve to get everyone up and going. You all know who you are and I gave proper name attribution in the tutorial thread. I'm exhausted, so I'm gonna go grab some dinner, that took hours to write! hahahahaah!!

    Be well everyone, SO happy my P5a is fully functioning, you folks are just amazing.

    hfam
    11
    diareuse has been MIA for a bit. Pinged him a couple times on the GitHub Issues, but no answer. Hopefully he's okay. 😕

    Mmm. Nothing on his Twitter since February... That's concerning.

    Yeah and in a week it'll be 1 full year since his last commit to Magisk too. 😕

    Good news is diareuse just reached out and is indeed alive and well, just working on multiple paying jobs in real life. 🙂
    10
    cb4361b7-alpha report:
    w/ RN8T, Stock MIUI, Android 10

    Two reboots needed initially.

    Zygisk & Riru w/ Universal SafetyNet Fix 2.1.1, LSPosed, Un-Share all working fine.

    SafetyNet passing w/ SafetyNet Google Play Services process denied.

    ViPER4Android FX Neon driver status normal.

    With Zygisk enabled Riru-MomoHider causes instability / system crashes even when only app_zygote_magic hiding is configured. 😕

    Great progress! 👍 PW
    Some have been waiting..
    Some have been using vvb2060's alpha builds..

    I have been sneaking a peak by running personal builds from John's master branch. :sneaky:
    Magisk - GitHub - Building and Development - Link

    A few days ago (23.Sep.2021), I was surprised when my OnePlus 6T passed SafetyNet. o_O
    It has been about three or four weeks since it passed SafetyNet.

    Problems I have run into..
    Every now and then, something misfires on boot and Magisk is not active (Installed N/A).
    Normally a reboot is all that is needed, occasionally I have to re-install magisk.

    I ran into an old issue on my 6T (clean install) installing Magisk.
    I had to flash a magisk patched image to both the active and inactive boot slot.
    Need to test again with another clean install.​

    Currently I have a few devices running these (sneak peak) build(s) and passing SafetyNet.

    OnePlus 5T
    Older device, does not have the hardware for hardware attestation.
    • Stock OnePlus OS 10.0.1 (SDK29)
    • Magisk (snapshot build)
    • MagiskHidePropsConf (Magisk Module)
      • Enable Zygisk
      • Enable DenyList
      • add com.google.android.gms.unstable to the DenyList.
        Magisk is in /sbin so only needed to Deny .unstable
      • Enable the MagiskHide props. option in the MagiskHidePropsConf module.
    Reboot in between steps as needed.

    OnePlus 6T
    • Stock OnePlus OS 11.0.0 (SDK30)
    • Magisk (snapshot build)
    • Universal SafetyNet Fix (Magisk Module)
      • Enable Zygisk
      • Enable DenyList
      • add com.google.android.gms.unstable to the DenyList.
      • add com.google.android.gms to the DenyList.
    Reboot in between steps as needed.

    Pixel 3a
    Custom rom that passes SafetyNet on it own.
    Installing Magisk breaks SafetyNet.

    • ABC Rom 11 (SDK30)
    • Magisk (snapshot build)
      • Enable Zygisk
      • Enable DenyList
      • add com.google.android.gms.unstable to the DenyList.
      • add com.google.android.gms to the DenyList.
    Reboot in between steps as needed.

    Earlier today, I setup an update channel so I could test a few more things.
    • Install update from online.
    • Repack (Hide/Restore) the Magisk app.
    All worked. :)
    Note:
    I will have to wait until the next commit(s) to see if I can update while the Magisk app is hidden. 🙃

    ---

    So far The next step of growth and development of Magisk is looking great. :)

    I am excited and eagerly waiting for the next canary build for proper testing. :D

    Cheers all. :cowboy:

    PS.
    Some screenshots from my 6T. ;)


    Edit (5.Oct.2021):
    Please see my follow up post.
    Post 48,294 - Link
    9
    Hi all. :)

    Just a quick note for those using newer (test/unofficial) builds that have the online Module Repo removed.

    Magisk-Modules-Repo - GitHub - Link
    Magisk-Modules-Repo - Repositories - GitHub - Link

    If you keep an eye on the repo, you will see when the developer(s) push an update.
    Most of the modules have links to support threads and/or another spot that you can download the updated module.
    Didgeridoohan uses the GitHub releases option for MHPC. 🙃

    If no other option is available, you can clone or download the specific module repo and then zip it into a new Magisk module zip file. ;)

    ---

    I Hope the option of a custom module repo is not too far down the list. ;)
    Bye, Magisk-Module-Repo
    I wanted to do this for a long time, as I do not have the mental capacity and interest to moderate and curate what modules are allowed on the official repo. If I accept low quality modules, people complain; if I remove some modules, people also complain. So I made the decision to remove Magisk-Module-Repo from the Magisk app. The administration and maintenance of the GitHub organization will be transferred to trusted community members (candidates not final yet). Developers can still easily install modules using the magisk —-install-module ZIP command in its own apps; users can install modules by selecting zip files in the Magisk app.

    I do want to eventually enable users to set its own online Magisk module sources which the Magisk app can handle module downloading / installing / upgrading, but this isn’t high up on the list of things I want to do in the near future.
    State of Magisk: 2021 - WebSite - medium.com - Link


    I have been a little curious since I mentioned it in a prior post that Magisk was once on PlayStore.
    If I remember correctly, this was the main reason Magisk was booted from PlayStore. :unsure:

    Now that the module repo is removed, does Magisk now fit Google's criteria for PlayStore?

    Cheers all. :cowboy:
    9
    Latest Alpha Magisk Chinese Translated:
    (For mavericks only! 😬)

    alpha update journal Magisk (cb4361b7-alpha-2)

    • [General] Based on cb4361b7, the content that has been merged into the upstream will not be listed anymore
    • [App] Correctly process any data from magiskd
    • [App] Support SharedUserld
    • [App] Delete the backup file after adding a thick boot mirror
    • [App] Built-in current version update log
    • [App] Use the local version when you cannot download the stub, now it can be used completely offline
    • [App] Switch to Java 8 modern time API
    • [DenyList] Dealing with suspicious props
    • [App] Expand and update SafetyNet, update the snet.jar version to 18
    • [General] Add an outdated cgroup v2 path
    • [Sepolicy] Add execmem to allow hook in zygote and system_server
    • [MagiskSU] If necessary, fall back to /dev/pts
    • [Zygisk] Repair may not take effect
    • [Busybox] Cancel optimization based on undefined behavior
    • [General] No longer automatically unlock the device block
    • [Zygisk] There is no report to prove that zygisk is incompatible with riru, remove the restriction
    • [Resetprop] Completely erase the old content when modifying/deleting
    • [General] Fix the race condition of thread pool
    • [Magisklnit] Do not intervene when booting to DSU

    How to install ?

    To install and use Magisk through the Magisk application, the general relationship should be completed directly in the application. For special circumstances such as the first installation, the image should be patched and then flashed in with the fastboot/odin tool. Customizing Recovery is not a supported method.

    You update the journal
    From 23.0 to cb4361b7

    • [General] Support pure 64-bit devices
    • [Generall supports Android 12 emulator
    • [Zygisk] Code injection framework
    • [General] Remove MagiskHide
    • [General] Support Simulator to add modules
    • [MagiskBoot] Support zimage format
    • [MagiskBoot] Add zopfhi encoder
    • [MagiskInit] Support bootconfig
    • [App] The repair installation function will now check if the script under /data/adb/magisk/ has not been updated
    • [Magisklnit] Support some Meizu devices
    • [MagiskSU] If the kernel supports it, use isolated devpts
    • [MagiskSU] Fix the pts configuration code, now no additional sepolicy rules are needed
    • [MagiskBoot] Support v4 boot image header format
    • [Magisklnit] Support oplus.fstab for some OnePlus and Opal devices
    • [App] Restart and update modules, not allowed to be marked as pending deletion
    • [App] Delete online warehouses
    • [App] Add mounting information to the saved log file
    • [App] Suitable for Android 12 API level
    • [App] Display the waiting pop-up window that is running when hide/restore the original app
    • [Stub] Open source obfuscation function
    • [Script] Check and display the sepolicy rule folder of the module.
    • [App] When the window pops up, hide the screen helmet and add layer. Android 12+ is required.
    • [App] Delete the floating bottom bar and change it to the general bottom operation bar.
    • [General] Support compilation cache
    • [General] Add rejection list function
    • [App] Delete DoH
    • [App] Delete SafetyNet
    • [App] Allow the log page to be opened when Magisk is not installed
    • [App] Display the status of Zygisk, add a reminder that restart is effective
    • [Zygisk] Correctly handle the child zygote
    • [Zygisk] Disabled riru module
    • [Sepolicy] Fix Android 8 terminal cannot get root

    👍 Marvin.
  • 1067
    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